This section describes the procedure required for HBA replacement on the server nodes registered on this product.
Note
Before executing access path inheritance, select Network from the global navigation tab on Web Console, and verify that all Fibre Channel switches cascaded to the Fibre Channel switch related to access path setting are correctly recognized in the current status. Once an access path is changed in a state where a Fibre Channel switch is temporarily disconnected from the cascade connection, the old cascade connection cannot easily be recovered. In this event, execute cfgClear to delete the zoning information for the Fibre Channel temporarily disconnected from the cascade connection. This enables cascade reconnection.
The basic conditions under which this product can recognize HBA replacement on a server node are as follows:
The agent has been installed in the server nodes.
HBA is exchanged on a server node same slot (physical port number).
The server node is registered in this product.
Access path is set to the pre-replaced HBA.
When inheriting access path to HBA on this product, notice the following points:
Zoning configuration should be one-to-one WWPN zoning.
In the environment using the following zoning configuration, access path inheritance is not allowed:
Port zoning
World Wide Port Name (WWPN) zone setting not being one-to-one.
If the port zoning is used, change it to one-to-one WWPN zoning temporarily before inheriting the access path to HBA. Refer to "6.2.6 Managing Fibre Channel Switch That Has Already Set in Port Zoning" for information on the change procedure. Upon completion of the access path inheritance, configure the switch directly to return to the port zoning. After that, delete the WWPN zoning that was set temporarily and perform the Reload Conf. operation for the switches and the servers on Web Console.
The zoning configuration of the following devices is not allowed to be inherited:
Tape library unit
Other than ETERNUS Disk storage system
The host number of host registration information is not allowed to be inherited. Host name is allowed to be inherited.
If inheritance is done toward the access paths for which no zoning is configured, skip zoning creation and perform only host registration and host affinity configuration.
For access path inheritance in environments that use the FC routing functionality, the settings for the LSAN zone that is required in the FC routing functionality cannot be modified using this product.
Before using access path inheritance, manually modify the required LSAN zone settings on the server nodes, Fibre Channel switches, and storage devices.
For VMware vSphere, perform either of the following steps after access path inheritance:
Reboot the VM host
For the HBA in which the access path inheritance is performed, rescan from VMware vCenter Server or VMware vSphere Client.
When you log in to the device that is registered in this product, such as a switch or a server, and change the access path settings, after the Reload Conf. operation is performed for the device to reflect the settings to this product, replace the HBA.
For the ETERNUS DX S2 series, you must not be logged into ETERNUS Web GUI. Make sure you perform the operation after logging off from ETERNUS Web GUI.
When replacing HBA on a server node, do it according to the operating system.
When replacing HBA on a Solaris server node, take the following procedure.
HBA Replacement with Server Node Shut Down
For a server node that does not support the hot system replacement function, turn off the server node in order to replace the HBA. Do not restart or shut down the server node in reconfigure mode during replacement. (This is because the special file name is changed if the reboot -r command, boot -r command, or other such command is executed.)
Shutting down the server node.
Confirm that the /reconfigure file does not exist, and shut down the device.
# ls /reconfigure /reconfigure: No such file or directory
If the /reconfigure file exists, take the following procedure:
To delete the "reconfigure" file, enter the following command.
# rm /reconfigure
Execute the ls command to re-check the presence of the /reconfigure file.
Do not reconfigure but shut down.
# /usr/sbin/shutdown -y -i0 -g0
Re-create the/reconfigure file after replacement operation. Afterward, restart the server node.
Replacing the HBA
To replace a failed component, contact a Fujitsu customer engineer.
Activating the server node
Activate the server node.
No access path, however, is recovered here. This is because the zoning is based on old HBA information is defined on the storage system and Fibre Channel switch.
Perform the Reload Conf. operation for the server node from this product.
Inheriting access paths (resetting security)
Follow the process of "10.3.1.2 Access Path Inheritance after HBA Replacement" from this product, and define the zoning setting so that the method of access based on the new HBA information can be the same as that for the previous access path of the storage system and Fibre Channel switch.
Reactivating the server node
Reboot the server node without reconfiguration (reboot -r, boot -r, etc. are prohibited.)
# /usr/sbin/shutdown -i6
The access paths and the paths of Multipath Disk Control are recovered.
HBA Replacement without Shutting Down Server Node
On the server node that supports the hot system replacement function, HBA replacement is allowed without shutting down the server node. Refer to the appropriate device manuals for information on the hot system replacement.
HBA replacement without shutting the server node
Refer to the device manual to replace HBA without shutting the server node.
To replace a failed component, contact a Fujitsu customer engineer.
Perform the Reload Conf. operation for the server node from this product.
Inheriting access paths (resetting security)
Follow the process of "10.3.1.2 Access Path Inheritance after HBA Replacement" from this product, and define the zoning setting so that the method of access based on the new HBA information can be the same as that for the previous access path of the storage system and Fibre Channel switch.
When replacing HBA on a other than Solaris server node, take the following procedure.
HBA Replacement with Server Node Shut Down
For a server node that does not support the hot system replacement function, turn off the server node in order to replace the HBA.
Shutting down the server node
Replacing the HBA
Starting the server node
No access path is recovered here. This is because zoning based on old HBA information is defined on the storage and Fibre Channel switch.
Perform the Reload Conf. operation for the server node from this product.
Inheriting access paths (resetting security)
Follow the process of "10.3.1.2 Access Path Inheritance after HBA Replacement" from this product, and define the zoning setting so that the method of access based on the new HBA information can be the same as that for the previous access path of the storage system and Fibre Channel switch.
Reactivating the server node
HBA Replacement without Shutting Down Server Node
On the server node that supports the hot system replacement function, HBA replacement is allowed without shutting down the server node. Refer to the appropriate device manuals for information on the hot system replacement.
Replacing the HBA without shutting down the server node
Refer to the device manual to replace HBA without shutting the server node.
To replace a failed component, contact a Fujitsu customer engineer.
Perform the Reload Conf. operation for the server node from this product.
Inheriting access paths (resetting security)
Follow the process of "10.3.1.2 Access Path Inheritance after HBA Replacement" from this product, and define the zoning setting so that the method of access based on the new HBA information can be the same as that for the previous access path of the storage system and Fibre Channel switch.
Inheriting the HBA access path requires that all steps for the target operating system in "10.3.1.1 Host Bus Adapter (HBA) Replacement of Server Node" through "Perform the Reload Conf. operation for the server node from this product" be completed. Make sure that preparatory work has been done, and perform proper operation in accordance with the HBA status.
When the HBA status becomes "Changed"
Perform the operation mentioned in "10.3.1.2.1 Post-replaced HBA State Is "Changed"".
When the HBA status does not become "Changed"
Perform the operation mentioned in "10.3.1.2.2 Post-replaced HBA State Is "Unknown"".
Note
Whether the HBA status becomes "Changed" or not cannot be determined before the Reload Conf. operation is performed from Web Console after HBA replacement.
In this product, after HBA replacement on an agent installed server node, if the Reload Conf. operation is performed for the server node, it recognizes the HBA replacement and changes the HBA state displayed on the server detail screen of the Main pane to "Changed". This is detected when an HBA that has a different WWPN is installed in the same slot (physical port number) of the host.
The procedure for access path inheritance at this time is provided below.
Point
Before performing the procedures below, refer to the Notes in "10.3.1 Replacing Server Node Components".
Checking the inherited HBA state
On the global navigation tab, click Server.
On the Main pane, check the server.
On the Main pane, confirm that the HBA state is "Changed".
Inheriting access path
On the global navigation tab, click Server.
On the Main pane, click the target server name.
On the Main pane, select the checkbox of the HBA whose state is "Changed".
On the Action pane, click Inherit under Access Path.
Checking the access path inheritance
On the global navigation tab, click Server.
On the Server pane, click Access Path.
Using the HBA of replacement destination, check if the access path has been set.
This product may not be able to set the "Changed" state for an HBA. According to the following status, execute this procedure.
HBA Replacement on Manually Embedded Server Node
In Cases Other than Above
Change access path by following procedure provided below.
If the device requires server node-side settings, the settings must be defined manually.
Point
Before performing the procedures below, refer to the Notes in "10.3.1 Replacing Server Node Components".
Detecting the replaced destination HBA
Reload the configuration of the target server to detect the replaced destination HBA.
On the global navigation tab, click Server.
On the Main pane, select the target server checkbox.
On the Action pane, click Reload Conf. under Server.
Checking the replaced destination HBA
On the global navigation tab, click Server.
On the Main pane, click the server name.
On the Main pane, check that the HBAs of replacement source and replacement destination are displayed.
Changing the access path
On the global navigation tab, click Server.
On the Server pane, click Access Path.
On the Main pane, select the changed target access path checkbox.
On the Action pane, click Modify under Access Path.
Change the setting of access path.
Checking the access path changing
On the global navigation tab, click Server.
On the Server pane, click Access Path.
Using the replaced destination HBA, check whether access path has been set.
Subsequent operation
After configuration, restart the server node if it does not support active configuration.
