NAME
stgcmmodnode - changes or displays Storage Management Server information
SYNOPSIS
/opt/FJSVswstf/bin/stgcmmodnode [-i IP-Address] [-p PORT-Number] [-n Server-Name]
DESCRIPTION
This command has the following two functions:
Displays Storage Management Server information specified on the Storage Server on which this command is currently executed
Changes Storage Management Server information.
This command changes the following information on a Storage Management Server:
IP address of a Storage Management Server
PORT number used by a communication daemon that runs on a Storage Management Server
Server name of a Storage Management Server
Refer to the following for the change procedure which uses this command:
OPTIONS
Displays the server information currently being managed.
Specifies the IP address of a Storage Management Server, to change the IP address of the Storage Management Server.
Specifies the port number of a Storage Management Server, to change the port number of the Storage Management Server.
Specifies the server name of a Storage Management Server to change the server name of the Storage Management Server. This option cannot be specified if this command is executed on a Storage Management Server.
EXIT STATUS
=0:Completed successfully
>0:Terminated abnormally
EXAMPLES
Display server information.
# /opt/FJSVswstf/bin/stgcmmodnode swstf2413 IP Address = 10.10.10.10 swstf2413 PORT Number = 1226 swstf2413 Storage Management Server's Name = fujitsu-storage-management-server #
Change the IP address of a Storage Management Server to 10.12.13.14.
# /opt/FJSVswstf/bin/stgcmmodnode -i 10.12.13.14 swstf2401 Storage Management Server registry updated. #
NOTES
This command can be executed only by root users.
For the PORT number of a Storage Management Server, you can specify a value between 1024 and 65535.
With this command, you must specify the same value as the one specified on a Storage Management Server. An error will occur in the operation if an invalid value is specified.
To execute this command, the AdvancedCopy Manager daemons must be stopped.
After successful execution, you must restart the AdvancedCopy Manager daemons.