Use the following procedure to actually apply the definition file's settings on the reference server and prepare a cloning image to be used for further server deployments. The definition file's settings applied from the definition file should be validated before image collection by checking the reference server's behavior and configuration.
Manually Execute the Network Parameter Setup Command
Execute the network parameter configuration command on the reference server holding the prepared definition file and check that the defined settings are applied correctly.
Before collecting the cloning image, run the following command to apply the definition file and verify that the defined settings are actually reflected on the reference server. This command also activates network parameter auto-configuration for any cloning image subsequently collected. Once this command has been executed, the network configuration that was described in the definition file will be perfumed automatically.
[Windows]
>"Installation_folder\Agent\bin\rcxadm" lanctl set <RETURN> |
[Linux]
# /opt/FJSVrcxat/bin/rcxadm lanctl set <RETURN> |
For details on this command, refer to "5.5 rcxadm lanctl" of the "ServerView Resource Coordinator VE Command Reference".
Use a command provided by the operating system ("ipconfig" for Windows and "ifconfig" for Linux) to confirm that network interface settings (without redundancy) were correctly applied.
Use the following commands to confirm that network interface settings (with redundancy) were correctly applied.
Using the /opt/FJSVhanet/usr/sbin/dsphanet command
# /opt/FJSVhanet/usr/sbin/dsphanet <RETURN>
[IPv4,Patrol]
Name Status Mode CL Device
+----------+--------+----+----+------------------------------------------------+
sha0 Active e OFF eth0(ON),eth1(OFF)
sha2 Active p OFF sha0(ON)
sha1 Active e OFF eth2(ON),eth3(OFF)
[IPv6]
Name Status Mode CL Device
+----------+--------+----+----+------------------------------------------------+ |
Items to confirm
- The status of the virtual interface must be "Active".
- When the standby patrol function is used ("p" mode), the status of the virtual interface set in standby patrol ("sha2" in the output example above) must be "Active".
Using the /opt/FJSVhanet/usr/sbin/dsppoll command
# /opt/FJSVhanet/usr/sbin/dsppoll <RETURN>
Polling Status = ON
interval(idle) = 5( 60)
times = 5
repair_time = 5
link detection = NO
FAILOVER Status = YES
Status Name Mode Primary Target/Secondary Target HUB-HUB
+------+------+----+-------------------------------------------+-------+
ON sha0 e 192.168.1.101(ON)/192.168.1.102(WAIT) ACTIVE
ON sha1 e 192.168.1.101(ON)/192.168.1.102(WAIT) ACTIVE |
Items to confirm
- The monitoring status (Polling Status) must be "ON" (monitoring in progress).
- If one monitoring destination is specified, the status of that destination (Primary Target) must be "ON" (monitoring in progress).
- If two monitoring destinations are specified, the status of the primary destination (Primary Target) must be "ON" (monitoring in progress) and the status of the secondary destination (Secondary Target) must be "WAIT" (on standby).
- When hub-to-hub monitoring is set to ON, the status (HUB-HUB) must be "Active" (monitoring in progress).
If the interface settings have not been configured correctly, clear the settings using the rcxadm lanctl unset command, and then correct the definition file before executing the rcxadm lanctl set command again.
If anything (including user-defined checks) does not turn out as expected even though the settings were applied correctly, check the network connections and the monitoring target, and take appropriate action.
Another test is to either deactivate the port on the LAN switch blade corresponding to the network interface where communications are actually being performed, or disconnect the cable from an external port on the LAN switch blade, to check whether the spare network interface automatically takes over communication. If the standby patrol function is enabled, check the port status or check that the status of the standby network interface changes to "WAIT" after reconnecting the cable.
Collecting a Cloning Image
Collect a cloning image from the managed server checked in step 1.
For details on how to collect a cloning image, refer to "8.2 Collecting a Cloning Image".
Note
[Linux]
When a cloning image is collected, any LAN redundancy settings on managed servers are canceled, and only network parameters for the public LAN are set up again when collection completes. If LAN redundancy has been set up for the admin LAN, set the LAN redundancy settings again manually.
