During SRA workflow initiator group (iSCSI host node names) is created with WWN “14:96:xx:xx:xx:xx:86:6“ and it fails as it is invalid.
This information is passed from SRM to SRA.
<Initiator id="10:xx:xx:xx:xx:xx:1B:91" type="FC" /> <Initiator id="14:xx:xx:xx:xx:xx:86:6" type="FC" /> <Initiator id="10:xx:xx:xx:xx:xx:CE:AB" type="FC" /> <Initiator id="10:xx:xx:xx:xx:xx:CE:AC" type="FC" />--> 2024-10-16 07:48:44 Unable to online/map LUN. Failed with exception Caused by: AbstractController: id: 823e6dc9-69db-11e6-xxxx-00xxxxa21a67name: drsansvm01ip address: 10.xx.6.124 failed to add initiator 14:96:xx:xx:xx:xx:86:6 to the igroup testfailover_igroup_domain-c37127, specifically com.netapp.offtap3.ontap.ApiFailedException: Invalid initiator "14:96:70:79:xx:xx:86:6". An example of a valid WWN is "01:02:03:04:xx:xx:xx:0d". Examples of valid iSCSI names are "iqn.1995-08.com.example:string" and "eui.0123456789abcdef". (errno=13001)The GUI for the host shows the correct WWN details however when we check in the cli, we see the incomplete WWN details:
cat /storage/scsifw/adapters/vmhba66/fc/infoFC Adapter Details { Host Node Name:0xfbb40xxxx97587b4 Host Port Name:0x1496xxxxxxxx866------------> this should be reported as 01496xxxxxxx866 Link speed: 8 -> 40GBIT Port Type: 3 -> NPort Port State: 2 -> Online Adapter Status: 1 -> Onlinethe WWPN information reports correctly in localcli_storage-san-fc-list.txtFcDevice: Adapter: vmhba66 Port ID: FB5866 Node Name: fb:b4:09:xx:xx:75:87:b4 Port Name: 01:49:6x:xx:xx:xx:x8:66 -----------> this is how it should show up Speed: 40 Gbps Port Type: NPort Port State: ONLINE Model Description: DellEMC PowerFlex Storage Device Hardware Version: NA OptionROM Version: NA Firmware Version: NA Driver Name: DellEMC PowerFlex Storage Device
Checking in MOB page of the vCenter at path (Go to https://<vc-ip>/mob/?moid=<host-id>&doPath=config.storageDevice) will not reflect that incorrect WWN details.
Site Recovery Manager 8.7
Site Recovery Manager 9.x
The WWN details are hard coded in the HBA and cannot be modified.
The data structure used to store the portWorldWideName is a long instead of a string, which is why SRM ignores the leading 0.
This is a rare issue which occurs due to incorrect or incomplete WWN details hard coded in the Host bus adapter.
If the above symptoms and issue matches, please contact Broadcom Support to investigate the issue by opening a ticket (Creating and managing Broadcom support cases).