This section explains how to change the settings for the chassis and managed servers.
If collecting the system images and cloning images of the managed server, collect the backup and cloning images after completing changes in the managed server settings.
For details on how to perform a backup, refer to "8.2 Backing Up System Images" in the "ServerView Resource Coordinator VE Operation Guide".
For details on how to collect cloning mages, refer to "8.2 Collecting a Cloning Image".
Note
To change VM guest settings, use the management console of the server virtualization software used.
A managed server that has already been registered cannot be moved to a different slot.
To move a managed server to a different slot, first delete the managed server, then move it to the new slot and register it again.
This section explains how to change chassis names.
Use the following procedure to change the name of a registered chassis.
In the RC console server resource tree, right-click the target chassis and select [Modify]-[Registration Settings] from the popup menu.
The [Modify Chassis] dialog is displayed.
In the [Modify Chassis] dialog, set the following items.
Enter up to 10 characters, including alphanumeric characters and hyphens ("-"). This name should start with an alphabet character.
Click <OK>.
The chassis name is changed.
This section explains how to change physical server names.
Names of physical OS's, VM hosts and VM guests can be changed by a user with administrative authority. Once changed, new names are automatically reflected in the RC console.
Use the following procedure to change the name of a physical server.
In the RC console server resource tree, right-click the target server, and select [Modify]-[Registration Settings] from the popup menu.
The [Modify Server] dialog is displayed.
In the [Modify Server] dialog, set the following items.
Enter up to 15 characters, including alphanumeric characters and hyphens ("-"). This name should start with an alphabet character.
Click <OK>.
The server name is changed.
If the network parameter auto-configuration function is used in the deployment of the cloning images, the "physical server name" set in the definition file must also be changed.
For details on the network parameter auto-configuration function, refer to "8.6 Network Parameter Auto-Configuration for Cloning Images".
This section explains how to change admin IP addresses.
To change the IP addresses of remote management controllers, refer to "6.3.2.5 Changing Server Management Unit Configuration Settings".
Chassis
Use the following procedure to change the IP address of a chassis.
Change the IP address of the management blade.
In the RC console server resource tree, right-click the target chassis and select [Modify]-[Registration Settings] from the popup menu.
The [Modify Chassis] dialog is displayed.
In the [Modify Chassis] dialog, change the "Admin LAN (IP address)".
Click <OK>.
The chassis admin IP address is changed.
Managed servers
Use the following procedure to change the IP address of a managed server.
However, it is still required when using the same address for both the admin and public IP address. This procedure is not required when changing only the public IP address of a server.
Log in to the admin server with an OS administrator account.
Change the IP address set within the operating system.
Change the IP address according to the OS manual.
If the admin LAN has been made redundant, change the admin IP address set in the following tools or products.
Refer to the manual of each product for usage details.
[Windows]
PRIMECLUSTER GLS
BACS
Intel PROSet
[Linux/Solaris]
PRIMECLUSTER GLS: "NIC switching mode (Physical IP address takeover function)".
Restart the managed server.
In the RC console server resource tree, right-click the target server, and select [Modify]-[Registration Settings] from the popup menu.
The [Modify Server] dialog is displayed.
In the [Modify Chassis] dialog, change the "Admin LAN(IP address)".
Click <OK>.
The admin IP address of the managed server is changed.
Note
It is not possible to change IP address settings of a managed server (primary server) with a spare server configured to a different subnet from the spare server.
This section explains how to change SNMP community settings.
For blade servers, PRIMERGY Partition Model servers or SPARC Enterprise M4000/M5000/M8000/M9000 servers
Use the following procedure to change SNMP community used by chassis and managed servers.
Change the SNMP community set on the management blade, management board, or XSCF.
The new SNMP community should have Read-Write permission.
For details on changing SNMP communities, refer to the manual of the management blade, management board, or XSCF.
Change the SNMP community set on the managed server.
Use the same name for the SNMP community of the managed server on the management blade, the management board, and the XSCF.
Follow the instructions in the ServerView Agent's manual to change the SNMP community used by a managed server.
The new SNMP community should have Read-Write permission.
In the RC console server resource tree, right-click the target chassis and select [Modify]-[Registration Settings] from the popup menu.
The [Modify Chassis] dialog is displayed.
In the [Modify Chassis] dialog, change the "SNMP Community".
Click <OK>.
The SNMP community is changed.
For rack mount or tower servers
Use the following procedure to change the SNMP community used by PRIMERGY servers.
For servers other than PRIMERGY servers, changing SNMP communities does not require any configuration change in Resource Coordinator VE.
Change the SNMP community set on the managed server.
Follow the instructions in the ServerView Agent's manual to change the SNMP community used by a managed server.
In the RC console server resource tree, right-click the target server, and select [Modify]-[Registration Settings] from the popup menu.
The [Modify Server] dialog is displayed.
In the [Modify Server] dialog, change the "SNMP Community".
Click <OK>.
The SNMP community is changed.
For SPARC Enterprise servers
Use the following procedure to change SNMP community used by the Remote Management Controller.
Change the SNMP community set on the remote management controller (XSCF).
For details on changing SNMP communities, refer to the XSCF manuals.
In the RC console server resource tree, right-click the target chassis, and select [Modify]-[Registration Settings] from the popup menu.
The [Modify Chassis] dialog is displayed.
In the [Modify Chassis] dialog, change the "SNMP Community".
Click <OK>.
The SNMP community is changed.
This section explains how to modify server management unit settings.
For rack mount or tower servers
Use the following procedure to change remote management controller settings.
Change settings on the remote management controller.
If the user account is changed, it should still have administrator authority.
In the RC console server resource tree, right-click the target server, and select [Modify]-[Registration Settings] from the popup menu.
The [Modify Server] dialog is displayed.
In the [Modify Server] dialog, change the "Remote Management Controller IP Address". To modify user account information, select "Modify user account", and change the "User name" and "Password" of the "Remote management controller".
For SPARC Enterprise servers
Use the following procedure to change remote management controller settings.
Change settings on the remote management controller (XSCF).
If the user account is changed, it should still have administrator authority ("platadm" privileges).
In the RC console server resource tree, right-click the target server, and select [Modify]-[Registration Settings] from the popup menu.
The [Modify Server] dialog is displayed.
In the [Modify Server] dialog, change the "Remote Management Controller (XSCF)".
To modify user account settings, select "Modify user account", and change the "User name" and "Password" fields under "Remote management controller (XSCF)".
For PRIMERGY Partition Model servers
Use the following procedure to change remote server management settings.
Change the remote server management settings.
If the user account is changed, it should still have administrator authority.
In the RC console server resource tree, right-click the target chassis and select [Modify]-[Registration Settings] from the popup menu.
The [Modify Chassis] dialog is displayed.
In [Modify Chassis] dialog, select the "Login Account Information" checkbox. Then, change the "User name" and "Password" of "Remote Server Management".
For SPARC Enterprise M4000/M5000/M8000/M9000 servers
Use the following procedure to change remote management controller settings (XSCF).
Change settings on the remote management controller (XSCF).
If the user account is changed, it should still have administrator authority ("platadm" privileges).
In the RC console server resource tree, right-click the target chassis and select [Modify]-[Registration Settings] from the popup menu.
The [Modify Chassis] dialog is displayed.
In [Modify Chassis] dialog, select the "Login Account Information" checkbox. Then, change the "User name" and "Password" of "Remote server management(XSCF)".
This section explains how to change port numbers.
When changing port numbers of the agent, the "nfagent" port of the manger must also be changed. Change this according to information in "6.3.1.2 Changing Port Numbers".
For details on port numbers, refer to "Appendix C Port List".
Use the following procedure to change the port numbers for managed servers:
Change the port numbers.
[Windows/Hyper-V]
Use a text editor (such as Notepad) to change the following line in the Windows_system_folder\system32\drivers\etc\services file.
# service name port number/protocol name nfagent 23458/tcp |
[Linux/VMware/Xen]
Use a command such as vi to change the following line in the /etc/services file.
# service name port number/protocol name nfagent 23458/tcp |
[Solaris]
Use a command such as vi to change the following line in the /etc/services file.
# service name port number/protocol name rcvat 23458/tcp |
Restart the server on which the port number has been changed.
This section explains how to change VM host login account information.
If the login account information (user name and password) of the VM host entered when the VM host was registered is changed on the VM host, change the login account information of the VM host that was registered in Resource Coordinator VE.
The method for changing the VM host login account is shown below.
In the RC console server resource tree, right-click the target VM host, and select [Modify]-[VM host login information] from the popup menu.
The [Change Login Information] dialog is displayed.
In the [Change Login Information] dialog, enter the login account information which was changed on the VM host.
Enter the user name to log in to the VM host. Specify a user name that has VM host administrator authority.
Enter the password of the user to log in to the VM host.
Click <OK>.
VM host login information is changed.
This section explains how to change LAN switch VLAN settings.
The VLAN settings of the LAN switch blade ports connected to the physical servers can be reconfigured normally within Resource Coordinator VE.
Refer to "6.2.1.2 Configuring VLANs on internal ports" for details on how to configure these settings.
This section explains how to change the HBA address rename settings.
The WWNs and HBA ports that are set by HBA address rename can be reconfigured normally within Resource Coordinator VE.
For details on how to configure these settings, refer to "6.2.2 Configuring HBA address rename".
This section explains how to change boot option settings.
The boot options configured for PRIMERGY Partition Models can be changed by re-configuring them.
Use the following procedure to configure the boot option settings.
In the RC console server resource tree, right-click the target server, and select [Modify]-[Registration Settings] from the popup menu.
The [Modify Server] dialog is displayed.
In the [Modify Server] dialog, set the following items.
For UEFI
Select "UEFI".
For Legacy boot
Select "Legacy boot".
Note
Changing the boot option changes the information registered with Resource Coordinator VE.
As the actual boot option will not be changed, it is necessary to change the BIOS settings when performing the change.
