Filter
Top Products
- Replacing and Adding Network Interfaces (Admin LAN, Public LAN)
The procedure used to replace and add network interfaces is the same as that described in "9.3.2 Replacing Servers".
For details, refer to "9.3.2 Replacing Servers".
When adding or removing network interfaces, if the target server is running Red Hat Enterprise Linux 5 or Citrix XenServer, after
completing the steps described in "9.3.2 Replacing Servers", log in with administrative privileges on the managed server and execute
the following command.
# /usr/local/sbin/macbindconfig create <RETURN>
[Xen]
When using Citrix XenServer, reinstall XenServer referring to the Citrix XenServer manual.
When using Red Hat Enterprise Linux 5 Virtualization (Xen-Based) and not using I/O Virtualization (VIOM), perform the following
procedure.
1. Execute the following command to temporally disable automatic startup of the xend daemon and then restart the managed
server.
# chkconfig xend off <RETURN>
2. Once the server has restarted, execute the following commands to update MAC address bindings, re-enable automatic startup
of the xend daemon, and restart the xend daemon itself.
# /usr/local/sbin/macbindconfig create <RETURN>
# chkconfig xend on <RETURN>
# service xend start <RETURN>
[Linux]
When the configuration of server components has been changed, check the configuration file of the OS, and make any necessary
corrections. For details, refer to "Configuration File Check" in "2.1.1.1 Software Preparation and Checks" in the "Setup Guide CE".
[Red Hat Enterprise Linux 6]
When adding or removing network interfaces, if the target server is running Red Hat Enterprise Linux 6, after completing the steps
described in "9.3.2 Replacing Servers", modify the configuration file.
For details, refer to "Configuration File Check" in "2.2.1.1 Software Preparation and Checks" in the "Setup Guide CE".
- Replacing a GSPB
The procedure used to replace a GSPB is the same as that described in "Replacing a network interface".
Replace NIC with GSPB in the procedure.
- Replacing an HBA
The procedure used to replace an HBA is the same as that described in "9.3.2 Replacing Servers".
- When using I/O virtualization, the replacement HBA will automatically inherit the WWN originally set on the replaced HBA.
Therefore, there is no need to re-configure access paths on the storage side.
- When configuring WWN information, it is necessary to change WWN information settings to the replaced HBA WWN values.
For details on how to change WWN information, refer to "9.1.12 Changing WWN Settings for ETERNUS SF Storage Cruiser
Integration" in the "User's Guide VE".
- Replacing a boot disk (in local boot environments)
Use the following procedure to replace a boot disk.
1. Replace the faulty boot disk with a new one.
2. If the boot disk's content was backed up, restore it.
- 59 -