11.1.2 Changing Operating Environment

Follow the procedure given below to change the IP address of a server node.

Changing the IP address of a server node for which Agent is installed
1. Change the system IP address on the server node.
2. Stop the server node Agent on the server node.
3. Execute the setagtip command on the server node to change the start IP of the server node Agent.
4. Restart the server node Agent on the server node.
5. Change the IP address of the server node from the Web Console.
Changing the IP address of a VM host for which Agent is not installed
1. Change the IP address of the VM host.
2. Change the IP address information of the VM host from the Web Console.
Changing the IP address of a guest OS for which Agent is not installed
1. Change the IP address of the guest OS.
2. Change the IP address information of the VM guest from the Web Console.

Point

Refer to "Changing IP Address of Managed Server" in the ETERNUS SF AdvancedCopy Manager Operation Guide when you install the AdvancedCopy Manager's agent in a server node.

11.1.2.3 Changing Server Name of Management Server

Refer to "Changing Server Name of Management Server Transaction or Managed Server Transaction" in the ETERNUS SF AdvancedCopy Manager Operation Guide.

11.1.2.4 Changing Name of Server Node

Follow the procedure given below to change the name of a server node.

Changing the name of a server node on which the Agent is installed
1. Change the server node name on the server node.
2. Stop the server node Agent on the server node.
3. Execute the setagtip command on the server node to change the setting of the server node Agent.
4. Restart the server node Agent on the server node.
5. Using the 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
1. Change the host name of the VM host.
2. Using the 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
1. Change the virtual machine name of the VM guest or the host name of a guest OS.
2. Using the 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 ETERNUS SF AdvancedCopy Manager Operation Guide when you install the AdvancedCopy Manager's agent in a server node.

11.1.2.5 Changing Port Numbers of Management Server

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 Solaris/Linux environments:
  /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 ETERNUS SF Express Operation Guide, and for Manager in Solaris/Linux environments, refer to "Changing Port Numbers (Linux)" in the ETERNUS SF Express Operation Guide.

In addition, Read "Express" as "Storage Cruiser".

11.1.2.6 Changing IP Address, SNMP Setting or Engine ID of Supported Device

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 the 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 ETERNUS SF 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 ETERNUS SF 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.

11.1.2.7 Changing Operation Management of Clustered System (Node Name Takeover)

Refer to "Changing IP Address of Management Server" in the ETERNUS SF AdvancedCopy Manager Operation Guide.

11.1.2.8 Changing Configuration of Supported Devices

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 ETERNUS DX60/DX60 S2/DX80/DX90, DX400 series, DX8000 series and firmware versions earlier than V10L40 of ETERNUS DX S2 series (excluding 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
Refer to "7.2.9 Updating Configuration Information" to update the configuration information of the performance management function. (Only when using the performance management function and "Partial" is specified for the scope of monitoring volumes)

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 Model Upgrade Options	After Applying Model Upgrade Options	Operation
ETERNUS DX60	ETERNUS DX80	Perform the procedure of "Operation on Model Upgrade for ETERNUS DX60 to DX80, for ETERNUS DX80 S2 to DX90 S2, for ETERNUS DX410 S2 to DX440 S2" in the ETERNUS SF Web Console Guide. When using the performance management function, update the configuration information of the performance management function in reference to "7.2.9 Updating Configuration Information" after performing the procedure above.
ETERNUS DX80 S2	ETERNUS DX90 S2
ETERNUS DX410 S2	ETERNUS DX440 S2
ETERNUS DX80 S2/DX90 S2	ETERNUS DX410 S2/DX440 S2	Perform the procedure of "Operation on Model Upgrade for ETERNUS DX80 S2/DX90 S2 to DX410 S2/DX440 S2" in the ETERNUS SF Web Console Guide.
ETERNUS DX100 S3	ETERNUS DX200 S3	Perform the procedure of "Operation on Model Upgrade for ETERNUS DX100 S3 to DX200 S3, for ETERNUS DX500 S3 to DX600 S3, for ETERNUS DX8700 S3 to DX8900 S3" in the ETERNUS SF Web Console Guide. When using the performance management function, update the configuration information of the performance management function in reference to "7.2.9 Updating Configuration Information" after performing the procedure above.
ETERNUS DX500 S3	ETERNUS DX600 S3
ETERNUS DX8700 S3	ETERNUS DX8900 S3

11.1.2.9 Changing Password of Supported Devices

Change the passwords for the following devices registered to this product to take the following conduction:

Objected Device	Conduction
ETERNUS SN200 series (Brocade) Fibre Channel switch PRIMERGY fibre channel switch blade	Change the account information for management of the device in the Web Console.
Brocade VDX series PRIMERGY BX Ethernet Fabric Switch
VMware vSphere 4 or later
ETERNUS DX series ETERNUS DX200F

Except for the devices described above, there is no necessary to do any deal with this software when change the device's password.

11.1.2.10 Changing SNMP Communication Protocol of Management Server

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 environment

Take the following steps to stop Storage Cruiser's manager.
1. Open the Services screen.
  - For Windows Server 2012
    Click Control Panel > System and Security > Administrative Tools > Services.
  - For Windows environment other than above
    Click Control Panel > Administrative Tools > Services.
2. Select the service "ETERNUS SF Manager Tomcat Service", and click Stop.
Take the following steps to stop the trap monitoring service.
1. Open the Services screen.
2. Select the service "SNMP Trap monitoring service", and click Stop.
Refer to either of the following sections in "When Monitoring Devices Using Only SNMPv3 Protocol or When Monitoring Devices Using SNMPv1 Protocol and SNMPv3 Protocol" in "SNMP Trap Setting (for Windows)" in "Setup of Storage Cruiser's Manager" in the ETERNUS SF 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 environment

Refer to the following section in "SNMP Trap Setting (for Linux)" in "Setup of Storage Cruiser's Manager" in the ETERNUS SF 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 environment

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.