This post relates to the issue that FCoE storage cannot be detected via FusionCompute 6.3.0 on CH121 V5. Please see below for the solution.
【Problem description】
When FusionCompute 6.3.0 is deployed on the CH121 V5, the FCoE storage cannot be detected via FusionCompute.
【Problem analysis】
1. The driver is upgraded to 1.714.3 on the MZ522.
2. FCoE is manually configured on the CNA node of FusionCompute and the configuration is successful, as displayed.
3. FC storage is found on the CNA node and the backend storage is connected to the OceanStor Dorado V3 storage via the SNS2124 switch.
4. The storage fails to be scanned via FusionCompute.
The problem may be caused by the incompatible version. Therefore, you need to confirm whether a compatibility test is performed for FusionCompute 6.3.0 and the NIC of the MZ522.
Confirmation from the solution engineers:
The end-to-end compatibility test is not performed for FusionCompute 6.3.0 and the MZ522 and FusionCompute 6.3.0 is not listed in the released compatibility list.
【Solution description】
1. FusionCompute 6.3.0 scans FC SAN storage devices only when devices are found in the /sys/bus/pci/devices directory.
2. The MZ522 uses software to simulate the connection with the FC SAN. No real PCI device is available. Therefore, the FC SAN storage device cannot be detected.
Short-term measures: Mask the conditions for determining the fiber channel and restart the thread.
T-CNA6-3:~ # vim /usr/lib/python2.7/site-packages/vna/storage/backend/storageadapter.py
75 #if fc_adapter.paths:
76 # all_type_adapters.append(fc_adapter)
77 all_type_adapters.append(fc_adapter)
systemctl restart vna-worker.service;
systemctl restart vna-scheduler.service;
systemctl restart vna-backend.service;
systemctl restart vna-api.service
Long-term measures:
The compatibility problem of the MZ522 NIC is solved in FusionCompute 9.3.0.
