Mike's PBX Cookbook

CS1K IP Address Change

Changing the IP scheme of a 'working system' can be a daunting task! Here are some things to remember.

➤ Use a network scanner such as Netscan or Angry IP before and after the change, on both the ELAN and TLAN.
➤ Print CS1000 common equipment (LD 22: PRT, CEQU) and media gateways (LD 117: PRT IPMG) before starting.

Tasks in order:

Call Server:

Peripherals:

  1. Change IP Address of the management computers, and reboot.
  2. UPS, rectifiers, or other power devices often have a web GUI.
  3. Remember to change the MRV Terminal Server (if installed).
  4. Update web-browser bookmarks, and Putty shortcuts, etc.
  5. MIRAN and/or Conference Bridge web interface address.

Call Server Address change:

Perform the following in LD 117:

=> prt host
Call Server 
 ID  Hostname         IP Address
  1  LOCAL_PPP_IF     137.135.192.4   
  2  REMOTE_PPP_IF    100.1.1.1       
  3  PRIMARY          192.168.0.5    
  4  SECONDARY        192.168.0.6           This system has 2 cores: High Availability (HA)

=> new host E_PRIMARY 172.16.0.5            IP address of CPU/CORE 1
INET Data Added

=> new host E_SECONDARY 172.16.0.6          IP address of CORE 2 (only if HA)
INET Data Added

=> prt route
Call Server 
 ID  Network          Gateway   
  1  0.0.0.0          192.168.0.254   
  
=> out route 1                              Remove old Gateway address
INET Data Removed

=> new route 0.0.0.0 172.16.0.254           Add new Gateway address
INET Data Added

=> chg elnk active E_PRIMARY                IP address of CORE 1
INET Database updated

=> chg elnk inactive E_SECONDARY            IP address of CORE 2 (only if HA)
INET Database updated

=> update dbs                               Update the 'INET' database 
OK

=> prt elnk
ACTIVE   ETHERNET: "E_PRIMARY" "172.16.0.5"
INACTIVE ETHERNET: "E_SECONDARY" "172.16.0.6"
OK

=> prt route
Call Server 
 ID  Network          Gateway   
  1  0.0.0.0          172.16.0.254   
  
=> enl route 1
LNK278  Enable ROUTE: "0.0.0.0" "172.16.0.254" failed.     Enable GW, ignore any warnings!
OK

Now do LD 43: edd, followed by a LD 135: sysload active and yes.
Yes, we have to sysload!

Post change: