Refer to "Changing IP Address of Management Server" in the AdvancedCopy Manager Operation Guide.
Perform the procedure below to change the IP address of a server node.
Changing the IP address of a server node for which Agent is installed
Change the system IP address on the server node.
Stop the server node Agent on the server node.
Execute the setagtip command on the server node to change the start IP of the server node Agent.
Restart the server node Agent on the server node.
Change the IP address of the server node from Web Console.
Changing the IP address of a VM host for which Agent is not installed
Change the IP address of the VM host.
Change the IP address information of the VM host from Web Console.
Changing the IP address of a guest OS for which Agent is not installed
Change the IP address of the guest OS.
Change the IP address information of the VM guest from Web Console.
Point
Refer to "Changing IP Address of Managed Server" in the AdvancedCopy Manager Operation Guide when you install the AdvancedCopy Manager's agent in a server node.
Refer to "Changing Server Name of Management Server Transaction or Managed Server Transaction" in the AdvancedCopy Manager Operation Guide.
Perform the procedure below to change the name of a server node.
Changing the name of a server node on which the Agent is installed
Change the server node name on the server node.
Stop the server node Agent on the server node.
Execute the setagtip command on the server node to change the setting of the server node Agent.
Restart the server node Agent on the server node.
With Web Console, perform the Reload Conf. operation on the server node.
Changing the host name of a VM host on which an Agent is not installed
Change the host name of the VM host.
With Web Console, perform [Reload of setting] for the VM host.
Changing the virtual machine name of a VM guest or the host name of a guest OS, on which an Agent is not installed
Change the virtual machine name of the VM guest or the host name of a guest OS.
With Web Console, perform the Reload Conf. operation for the VM host that has the target VM guest.
Point
Refer to "Changing Server Name of Management Server Transaction or Managed Server Transaction" in the AdvancedCopy Manager Operation Guide when you install the AdvancedCopy Manager's agent in a server node.
Changing The Port Number of Sscruisera
sscruisera uses port number 4917 as standard.
Change the port number in the following steps:
Open the following files by a text editor or the like:
For Manager in a Windows environment
%SystemRoot%\system32\drivers\etc\services
For Manager in a Solaris or Linux environment
/etc/services
Change the port number.
Enter a port number between 1024 and 65535. When changing a port number, a number between 5001 and 32768 is recommended.
# <service name> <port number>/<protocol> [aliases...] [#<comment>] # sscruisera 4917/tcp
Save the file opened at Step 1 and close it.
Restart Manager.
Changing Port Numbers Other Than Those Above
For Manager in a Windows environment, refer to "Changing Port Numbers (Windows)" in the Express Operation Guide, and for Manager in a Solaris or Linux environment, refer to "Changing Port Numbers (Linux)" in the Express Operation Guide.
In addition, Read "Express" as "Storage Cruiser".
When changing the IP address, the SNMP setting or the engine ID of the support level A or B device that is registered in this product, perform the following procedure:
Changing IP Address of Supported Device
Change the IP address of each target device.
Record the settings of threshold monitoring. (if thresholds are monitored)
Change the IP address of the target device using Web Console. (If thresholds are being monitored, threshold monitoring is stopped by this operation.)
Based on the settings at step 2, start to monitor thresholds. (if thresholds are monitored)
Changing SNMP Setting of Supported Device
Change the SNMP setting of each target device.
Record the settings of threshold monitoring. (if thresholds are monitored)
Perform steps 1 - 6 in "Change SNMP Communication Settings" in the Web Console Guide. (If thresholds are being monitored, threshold monitoring is stopped by this operation.)
Based on the settings at step 2, start to monitor thresholds. (if thresholds are monitored)
Changing Engine ID of Supported Device
Change the engine ID of each target device.
Perform steps 1 - 4 in "Change SNMP Communication Settings" in the Web Console Guide, and click Modify. (This operation makes the engine ID of each target device available and reflected to this product.)
See
Refer to "Chapter 4 Environment Configuration" for the SNMP setting of each target device.
Note
To change the SNMP Trap community name at a Linux Manager, refer to "A.10 snmptrapd.conf Configuration File" and also change the snmptrapd.conf settings.
Refer to "Changing IP Address of Management Server" in the AdvancedCopy Manager Operation Guide.
For Changing Device Configuration
If the following change, the update of the set up information is needed in the support device:
Upgrade of firmware with support device
Configuration change by increase/decrease of hardware (in case of storage device, its CM, CA, CE, DE, disk, port)
Addition/deletion/change in composition (in the case of a disk storage system, its RAID Group, LogicalVolume, etc.) in device
Method of updating set up information is as follows:
For all firmware versions of the ETERNUS DX60 S2 and firmware versions earlier than V10L40 of the ETERNUS DX S2 series (excluding the ETERNUS DX60 S2)
Perform the Reload Conf. operation for the relevant device to update the information for the target device.
Refer to "7.2.9 Updating Configuration Information" to update the configuration information of the performance management function. (when using the performance management function)
For other devices
When using the performance management function and "Partial" is specified for the scope of monitoring volumes
Refer to "7.2.9 Updating Configuration Information" to update the configuration information of the performance management function.
When using the performance management function and "All" is specified for the scope of monitoring volumes
Because the configuration information of the performance management function is updated automatically, no action is required. However, when the firmware is being updated, the update may take some time to be completed. Refer to "7.2.9 Updating Configuration Information" for details.
When not using the performance management function
No action is required.
For Applying Model Upgrade Options for ETERNUS Disk Storage System
The device configuration is changed when applying Model upgrade options for ETERNUS Disk storage system.
Perform the following operation after applying Model upgrade options for ETERNUS Disk storage system.
Before Applying | After Applying | Operation |
|---|---|---|
ETERNUS DX60 S5 | ETERNUS DX100 S5 | Perform the procedure of "Operation on Model Upgrade from DX60 S5 to DX100 S5, from DX100 S5 to DX200 S5, from DX500 S5 to DX600 S5, from DX60 S4 to DX100 S4, from DX100 S4 to DX200 S4, from DX500 S4 to DX600 S4, from DX60 S3 to DX100 S3, from DX100 S3 to DX200 S3, from DX500 S3 to DX600 S3, from DX8700 S3 to DX8900 S3, from AF150 S3 to AF250 S3" of "Operation on Model Upgrade for ETERNUS Disk Storage System" in the Web Console Guide. |
ETERNUS DX100 S5 | ETERNUS DX200 S5 | |
ETERNUS DX500 S5 | ETERNUS DX600 S5 | |
ETERNUS DX60 S4 | ETERNUS DX100 S4 | |
ETERNUS DX100 S4 | ETERNUS DX200 S4 | |
ETERNUS DX500 S4 | ETERNUS DX600 S4 | |
ETERNUS DX60 S3 | ETERNUS DX100 S3 | |
ETERNUS DX100 S3 | ETERNUS DX200 S3 | |
ETERNUS DX500 S3 | ETERNUS DX600 S3 | |
ETERNUS DX8700 S3 | ETERNUS DX8900 S3 | |
ETERNUS AF150 S3 | ETERNUS AF250 S3 | |
ETERNUS DX200 S5 | ETERNUS DX500 S5 | Perform the procedure of "Operation on Model Upgrade from DX200 S5 to DX500 S5, from DX200 S4 to DX500 S4, from DX200 S3 to DX500 S3, from AF250 S3 to AF650 S3" of "Operation on Model Upgrade for ETERNUS Disk Storage System" in the Web Console Guide. |
ETERNUS DX200 S4 | ETERNUS DX500 S4 | |
ETERNUS DX200 S3 | ETERNUS DX500 S3 | |
ETERNUS AF250 S3 | ETERNUS AF650 S3 | |
ETERNUS DX80 S2 | ETERNUS DX90 S2 | Perform the procedure of "Operation on Model Upgrade from DX80 S2 to DX90 S2, from DX410 S2 to DX440 S2" of "Operation on Model Upgrade for ETERNUS Disk Storage System" in the Web Console Guide. |
ETERNUS DX410 S2 | ETERNUS DX440 S2 | |
ETERNUS DX80 S2/DX90 S2 | ETERNUS DX410 S2/DX440 S2 | Perform the procedure of "Operation on Model Upgrade from DX80 S2/DX90 S2 to DX410 S2/DX440 S2" of "Operation on Model Upgrade for ETERNUS Disk Storage System" in the Web Console Guide. |
Change the passwords for the following devices registered to this product to take the following conduction:
Objected Device | Conduction |
|---|---|
Brocade Fibre Channel switch | Change the account information for management of the device in Web Console. |
VDX series | |
VMware vSphere | |
ETERNUS DX series |
Except for the devices described above, there is no necessary to do any deal with this software when change the device's password.
On Management Server that executes fault monitoring on devices using SNMPv1 protocol alone, when making the following operational environment changes, it is required to change SNMP Trap daemon settings.
Add a device on which fault monitoring is executed with SNMPv3 protocol.
Change the communication protocol of a fault monitoring executed device from SNMPv1 to SNMPv3.
For Windows environments
Take the following steps to stop Storage Cruiser's manager.
Click Control Panel > System and Security > Administrative Tools > Services to open the Services screen.
Select the service "ETERNUS SF Manager Tomcat Service", and click Stop.
Take the following steps to stop the trap monitoring service.
Open the Services screen.
Select the service "SNMP Trap monitoring service", and click Stop.
Refer to either of the following sections in "When Using ETERNUS SF SNMP Trap Monitoring Service" in "SNMP Trap Setting (for Windows)" in "Setup of Storage Cruiser's Manager" in the Installation and Setup Guide to set up an environment.
Step 2 or later in "When Other Applications (Systemwalker Centric Manager, ServerView Resource Orchestrator, etc.) Using SNMP Traps Do Not Coexist".
Step 2 or later in "When Other Applications (Systemwalker Centric Manager, ServerView Resource Orchestrator, etc.) Using SNMP Traps Coexist".
After changing the SNMP Trap daemon settings, it is required to register SNMPv3 user information and set up SNMP v3 user to a managed device. Refer to "SNMPv3" in "3.1.2 SNMP Communication Authentication" for setting method.
For Linux environments
Refer to the following section in "SNMP Trap Setting (for Linux)" in "Setup of Storage Cruiser's Manager" in the Installation and Setup Guide to set up an environment. Also, if a monitored device uses IPv6 address, this setting is not required.
When Using ETERNUS SF SNMP Trap Monitoring Daemon
After changing the SNMP Trap daemon settings, it is required to register SNMPv3 user information and set up SNMP v3 user to a managed device. Refer to "SNMPv3" in "3.1.2 SNMP Communication Authentication" for setting method.
For Solaris environments
It is required to register SNMPv3 user information and set up SNMP v3 user to a managed device. Refer to "SNMPv3" in "3.1.2 SNMP Communication Authentication" for setting method.
It is not necessary to change the SNMP Trap daemon settings.
If you change the SSL version setting for communicating with the following devices that are registered for this product, restart the ETERNUS SF Manager if the protocol Maintenance-Secure TLSv1.2 is disabled, or TLSv1.2 and TLSv1.1 are disabled:
ETERNUS DX S5/S4/S3 series
ETERNUS AF All-Flash Arrays
ETERNUS DX200F
VM Host
When the hostname or IP address is changed
After changing the IP address or host name of the VM host, perform the Reload Conf. operation for the target device on Web Console.
When the user name or password is changed
After changing the user name or password, set the new username or password for this software using Web Console.
VM Guest
When the virtual machine name or host name of the guest OS is changed
After changing the virtual machine name of the VM guest or host name of the guest OS, perform the Reload Conf. operation for the VM host where the target device exists, on Web Console.
When the IP address of the guest OS is changed
After changing the IP address of the guest OS, perform the Modify operation for the target device on Web Console.
