This section explains how to change the settings for the chassis and the managed server. If collecting the system images and cloning images of the Admin Server, collect the backup and cloning images after completing changes in the managed server settings.
Refer to "8.2 Backing Up System Images" in the "ServerView Resource Coordinator VE Operation Guide" for details on how to perform a backup. Refer to "8.2 Collecting a Cloning Image" for details on how to collect cloning mages.
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 server, then move it to a different slot and register it again.
Use the following procedure to change the name of a registered chassis.
From the RC console, right-click the target chassis, select [Modify]-[Registration Settings] from the popup menu, and change the "chassis name" item.
The chassis name should start with a letter and can be up to 10 alphanumeric characters or hyphens ("-").
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.
From the RC console, right-click the target server, and select [Modify]-[Registration Settings] from the popup menu, and change the "physical server name".
In the physical server name, the first character must be a letter and can be up to 15 alphanumeric characters or hyphens ("-").
If the network parameter automatic setting function is used in the deployment of the cloning images, the "physical server name" set in the definition file must also be changed.
Refer to "8.6 Network Parameter Auto-Configuration for Cloning Images" for details on the network parameter automatic setting function.
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 Remote Management Controller Settings".
Chassis
Use the following procedure to change the IP address of a chassis.
Change the IP address of set on the management blade.
From the RC console, right-click the target chassis, select [Modify]-[Registration Settings] from the popup menu, and change the "Admin LAN (IP address)" item.
Managed servers
Use the following procedure to change the IP address of a managed server.
This procedure is not required when changing only the public IP address of a server. However, it is still required when using the same address for both the Admin and public IP address.
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]
PRIMECLUSTER GLS: "NIC switching mode (Physical IP address takeover function)".
Restart the managed server.
From the RC console, right-click the target server, select [Modify]-[Registration Settings] from the popup menu, and change the "Admin LAN (IP address)" item.
This section explains how to change SNMP community settings.
For blade servers
Use the following procedure to change SNMP community used by chassis and managed servers.
Change the SNMP community set on the management blade.
The new SNMP community should have Read-Write permission.
Change the SNMP community set on the managed server.
Use the same SNMP community for both the management blade and the managed servers. 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.
From the RC console, right-click the target server and select [Modify]-[Registration Settings] from the popup menu.
The [Modify Chassis Settings] dialog is displayed.
Modify the "SNMP community" item
Click the <OK> button.
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 doesn't 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.
From the RC console, right-click a managed server and select [Modify]-[Registration Settings] from the popup menu.
The [Modify Registration Settings] dialog is displayed.
Change the "SNMP community" item.
Click the <OK> button.
The SNMP community is changed.
This section explains how to change remote management controller settings.
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.
From the RC console, right-click the target server, select [Modify]-[Registration Settings] from the popup menu, and change the "IP address" of the "Remote management controller". To modify user account information, select "Modify user account", and change the "User name" and "Password" of the "Remote management controller".
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". Refer to "Appendix C Port List" for details on port numbers.
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 file Windows_system_ folder\system32\drivers\etc\services.
# service name port number/protocol name nfagent 23458/tcp |
[Linux/VMware]
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 |
Restart the server in 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 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.
Enter the login account information which was changed on the VM host.
Enter the user name to log in to the VM host. The user name is specified by a user who has VM host administrator authority.
Enter the password of the user to log in to the VM host.
Click the <OK> button.
VM host login information is changed.
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.
The WWNs and HBA ports that are set by HBA address rename can be reconfigured normally within Resource Coordinator VE.
Refer to "6.2.2 Configuring HBA address rename" for details on how to configure these settings.
