When replacing a failed HBA with a new one on server, you need to update both the fabric and the storage system to ensure proper communication between the server and storage.
Steps to Update Fabric and Storage
1. Update the WWPN in the Fabric
1.1 Add the New WWPN to the Existing Alias
Use the following command to add the new WWPN to the alias:
aliadd "alias_name","new_wwpn"
1.2 Remove the Old WWPN from the Alias
After adding the new WWPN, remove the old one:
aliremove "alias_name","old_wwpn"
⚠️ Important: Always add the new WWPN first before removing the old one. If the old WWPN is removed first, the alias will be deleted from the fabric permanently.
1.3 Save and Apply the Updated Configuration
cfgsave
cfgenable
2. Update the WWPN on the Storage System
2.1 Add the New WWPN to the Storage Initiator Group (IG)
Depending on your storage vendor, use the appropriate command or GUI method:
- NetApp ONTAP:
igroup add igroup_name new_wwpn - Dell EMC PowerStore/Unity:
Add the new WWPN to the host in Unisphere. - IBM:
Add the new WWPN to the host in GUI.
2.2 Remove the Old WWPN from the Storage Initiator Group
- NetApp ONTAP: shellCopyEdit
igroup remove igroup_name old_wwpn - Dell EMC PowerStore/Unity:
Remove the old or failed WWPN to the host in Unisphere. - IBM:
Remove the Old WWPN to the host in GUI.
2.3 Verify Storage Access
- Check if the host can see the storage LUNs and paths.
- Validate that the new WWPN is active using
fcnsshow(Brocade) orshow flogi database(Cisco).
Final Validation
✅ Ensure the server detects the LUNs.
✅ Confirm multipathing is working correctly.
✅ Verify I/O performance after the change.
By following these steps, you ensure a smooth HBA replacement without disrupting storage connectivity. 🚀