User guide
5-41
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Chapter 5 Maintaining an Efficient Network
How Do I Modify the Network?
5.3.6 Changing the Server IP Address when Cisco MGM and Oracle Are on the
Same Server
Note You will need to update the configuration files after changing the server IP address, see 5.3.6.1 Updating
the Configuration Files after Changing the Cisco MGM Server IP Address.
To change the IP address of a standalone Cisco MGM server with a single IP interface when Cisco MGM
and Oracle are on the same server:
Step 1 Log into the Cisco MGM server as the root user.
Step 2 Enter the following command to shut down the Cisco MGM server:
mgms-stop
Step 3 Enter the following commands to shut down Oracle:
su - oracle
sqlplus ctmanager/mgm123!
SQL> connect sys/change_on_install as sysdba
SQL> shutdown immediate;
SQL>exit
Step 4 Complete the following:
a. Enter the following command to change the IP address in the /etc/netmasks file:
#vi /etc/netmasks
b. Enter the following command to change the IP address in the /etc/hosts file:
# vi /etc/hosts
Table 5-17 Recovery Properties—Session Recovery Tab
Field Description
Wait Time If disruption to the primary Cisco MGM server occurs, the Wait Time field
provides the number of seconds the client waits before attempting to log into the
backup server.
No. of Retries If the first backup Cisco MGM server is not available, this field provides the
number of times the client should retry logging in before moving to the next
server on the list.
Server List Lists the Cisco MGM servers that Cisco MGM clients will log into if access to
the primary Cisco MGM server is disrupted. The Add button adds a Cisco MGM
server to the Cisco MGM server list. The Remove button removes a Cisco MGM
server from the list.
If access to the primary Cisco MGM server is disrupted, the Cisco MGM client
tries to log back into the primary server by default. If the Cisco MGM client
cannot log back into the primary server, and if the server list contains server
names, the client tries to log into each backup server in the order listed until the
last server in the list is reached, or until the client successfully logs into a server.