Solution when the host fails to connect to the array directly using a Brocade HBA card because the rate is modified or the host is restarted

0

1. Run chgportparam to set a latency of 500 μs for link setting.
You can run help -c chgportparam to query the usage.

2. Run chgfcmode to change the port mode of the disk array to P2P.

Other related questions:
Solution if LUNs fail to be detected after the host initiator or HBA card is changed
Solution if LUNs fail to be detected after the host initiator or HBA card is changed: 1. Description: What can I do if LUNs fail to be detected after the host initiator or HBA card is changed? a. The iSCSI Initiator Node Name value of the host is changed. b. The HBA card (Fibre Channel or SAS) of the host is replaced. 2. Solution: a. For the iSCSI connection in the front end, change the name of the host initiator to the changed iSCSI Initiator Node Name value. b. For the Fibre Channel or SAS connection in the front end, add the WWN of the current host's port to the storage array.

Solution if the host fails to detect LUNs
Solution if the host fails to detect LUNs: Determine the connection mode at the front end. If the Fibre Channel switch is connected, check whether the switch mode has been configured. If the front end uses the Fibre Channel switch, check with the customer that the switch has been correctly configured with zones and assign the storage system and the host to the same zone. If the port WWN is bonded during zone division, check whether the port binding is correct. Alternatively, use optical fibers to directly connect the storage system to the switch and re-scan for LUNs.

Problem and solution when a shared folder is lost on the LUN connected to iSCSI after the Windows host is restarted
You can perform the following operations when a shared folder is lost on the LUN connected to iSCSI after a Windows host is restarted: 1. Method The shared folder is created by the server service during startup. If the server service starts before the iSCSI initiator service during server startup, the server cannot create file sharing for the iSCSI disk. For temporary workaround, manually start the server service. 2. Solution Perform the following steps: a. Change the startup sequence of server services by using the iSCSI initiator server. Enter sc config lanmanserver depend= MSiSCSI on the CLI (note that there is a space after =). b. Add the disk volume list to the permanent binding list of Microsoft iSCSI initiator. Enter iscsicli Bindpersistentvolumes on the CLI.

Problem and solution when the heartbeat interfaces of the firewalls fail to be directly connected
Troubleshoot as follows: 1. Check whether the cable is properly connected. 2. Check whether the interface has been added to the security zone. 3. Check whether service-manage ping permit is configured under the interface.

Solution if a message indicating that the host needs to be restarted is displayed repeatedly when the multipathing software is being reinstalled on a Windows host after it is uninstalled
Solution if a message indicating that the host needs to be restarted is displayed repeatedly when the multipathing software is being reinstalled on a Windows host after it is uninstalled: Delete the Restart key value in the registry. The position where the key value of Restart is stored varies with Windows systems: 1. Windows x86 system: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run 2. Windows x64 system: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Run 3. Restart the host.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top