Use the following procedure to configure HBA address rename settings.
The HBA address rename function allows the Admin Server to control the WWNs set on a managed server's HBAs. During maintenance or switchover operations, a replacement server (or HBA) can inherit the WWN configuration set on a replaced server (or HBA). With this feature, the traditionally necessary re-configuration of storage devices is no longer required.
Use of the HBA address rename function requires registering specific settings for each server in advance.
Note
The HBA address rename function cannot be enabled for servers on which recovery settings were already configured. Cancel any existing recovery settings before enabling the HBA address rename function on a server.
1. Storage settings
Refer to "3.7 Configuring the Storage Environment" to configure storage devices.
When altering the configuration of a storage device already used by active servers, make sure to power off those servers before performing any configuration change.
2. Settings for the HBA address rename function
In the RC console resource tree, right-click the target server (or the physical OS or VM host on the server), and select [Modify]-[HBA Address Rename Settings] from the popup menu.
The [HBA Address rename settings] dialog is displayed.
In the [HBA Address rename settings] dialog, set the following items:
Specify the WWNN value provided by the "I/O virtualization (FC) Option", which is one of blade server option products.
The Admin Server generates WWPNs automatically from the values that are input into the WWNN and the number of HBA ports.
Specify the following values according to the system configuration.
To create a single-path configuration, specify "1".
Refer to "Figure 6.4 Procedures for single-path configurations" for details.
To create a multi-path configuration, specify "2".
However, it is necessary to specify "1" during installation of the operation system. Specify "2" and reconfigure HBA address rename settings after setting up the multi-path driver.
Refer to "Figure 6.5 Procedures for multi-path configurations" for details.
Figure 6.4 Procedures for single-path configurations
Figure 6.5 Procedures for multi-path configurations
Example
For a server with two HBA ports, use the HBA address rename function as follows.
WWNN value provided by "I/O Virtualization (FC) Option" in blade server options: 20:00:00:17:42:51:00:00
Values to set in the [HBA address rename settings] dialog
"WWNN" value 20:00:00:17:42:51:00:00
"HBA port number" on board: 2
Values actually set by the Admin Server on the HBA (WWPNs are generated automatically)
WWNN value for ports 1 and 2 of the HBA : 20:00:00:17:42:51:00:00 WWPN value for HBA port 1 : 21:00:00:17:42:51:00:00 WWPN value for HBA port 2 : 22:00:00:17:42:51:00:00
Information
WWN settings are applied to managed servers during server startup.
Check the server's restart checkbox if the server is to be restarted.
Information
Select server restart in the following cases.
When installing an operating system immediately after performing the above settings
Insert the operating system installation CD in the target server and select server restart. Once the server has been restarted, its WWN settings are applied and the operating system installation starts.
When an operating system is already running (if changing storage settings)
Click the <OK> button to restart the target server and apply its WWN settings.
The server restart is not required in other cases. The WWN that has been set is enabled at the next restart.
Click the <OK> button.
Restart HBA address rename setup service.
The HBA address rename setup service must be running to use the HBA address rename function. Refer to "6.2.2.1 Settings for the HBA address rename setup service" for details.
If the Admin Server and a managed sever cannot communicate due to errors such as the Admin Server crash or a failure in NIC1 that is connected to the Admin LAN, the HBA address rename setup service inherits the role from the Admin Server to set the WWN and restart the managed server.
The HBA address rename setup service must be running before the HBA address rename function can be used.
With this function, the Admin Server sets the WWN of managed servers during their startup sequence. This WWN is kept by the managed server until it is powered off.
If a managed server cannot communicate with the Admin Server (because of errors such as the Admin Server crash or the managed server's NIC1 failure), then the managed server HBAs WWN cannot be set up. In such case, the managed server cannot start up properly.
Such problems can be avoided by using the HBA address rename setup service.
This service, which must be run on a server other than the Admin Server, can set up managed servers HBAs WWNs in the same way the Admin Server does.
To verify that this service runs properly, power off the Admin Server and confirm that managed servers can still start up as usual.
Use the following procedure to configure the HBA address rename setup service.
Select [Start]-[All programs]-[Resource Coordinator VE]-[HBA address rename setup service].
The [HBA address rename setup service] dialog is displayed.
In the [Start and stop of HBA address rename setting service] dialog, enter the following items.
The status of the service is displayed. "Stopping" is displayed if the service is not running, and "Operating" is displayed if the service is running.
Enter the IP address of the Admin Server.
Enter the port number that is used to communicate with the Admin Server. The port number at installation time is 23461. If the "rcxweb" port number of the Admin Server is changed, specify the number that has been changed.
Displays the latest synchronization time.
This is the last time this service synchronized its data (managed server settings) with that of the Admin Server.
To start this service, click the <Start> button.
To stop this service, click the <Stop> button.
To cancel, click the <Cancel> button.
Note
This service should be kept running at all times.
Start this service on only one server for each Admin Server.
OS administrator privileges are required to start and stop this service.
This service does not operate on the server where the Manager is installed.
