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:
- Data switches in PBX room
- Change any gateways to reflect the new networks - Call Server - ELAN
- LD 117, build and enable new hosts:new host E_PRIMARY,chg elnk active E_PRIMARY
- Change the gateway address:NEW ROUTE x 0.0.0.0 172.16.0.254(for example, see below) - Media Gateways - ELAN
- LD 97, change the superloop IPMG addresses. - Sig Servers - ELAN and TLAN
- Usebaseparamsconfigwith admin2 login, or re-install linux base.
- With 4.5/5.5, re-install, and enter the new IP addresses. Re-enter Sig Server (node) and NRS configs... - MGC Cards - ELAN and TLAN
- Direct connect TTY (ctrl-LDB):mgcIPCleardiskformat "all"reboot
- Use Element Manager to configure TLAN and DSP Daughterboards - MGC DSP Daughterboards - TLAN
- Do this in Element Manager - Call Pilot - ELAN
- Run config wizard: change ELAN and Call Server addresses, re-flash DSP's, and reboot.
Do this after all Call Server IP changes have been completed. - DHCP Server - TLAN
- for IP phones, if deployed. Change server address (Option 128), and check each DHCP scope.
Peripherals:
- Change IP Address of the management computers, and reboot.
- UPS, rectifiers, or other power devices often have a web GUI.
- Remember to change the MRV Terminal Server (if installed).
- Update web-browser bookmarks, and Putty shortcuts, etc.
- 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:
- Check MGC status in LD 117:
=> prt ipmg IPMG IP Address Zone Type 000 0 172.16.0.51 1 MGC 000 1 172.16.0.52 1 MGC => stat ipmg LAST REG LAST REG IPMG TYPE STATUS DATE TIME UPTIME 000 0 MGC REG 28/10/2015 17:27 0d,0h,31m 000 1 MGC REG 28/10/2015 17:27 0d,0h,31m - Check VGW DSP TNs show as registered in LD 32, for each MGC:
REQ: stat 0 0 0 Check cards: 0,11,12,13,14 for each MGC (if DSP DB fitted) 00 = UNIT 00 = UNEQ 01 = UNIT 01 = IDLE (TRK)(IPTN REG ) 02 = UNIT 02 = IDLE (TRK)(IPTN REG ) :
- Check MGTDS (LD 34) and MGCONF (LD 38) loops are enabled, print CEQU (LD 22) to find them.
>ld 34 MGTDS loops TDS000 .stat 100 00 DSBL 02 BUSY >ld 38 MGCONF loops CNF000 .stat 101 CNFC 00 DSBL 00 BUSY CHAN 00 DSBL 00 BUSY
- Check CallPilot is answering, check MOH is working.
- Check web-browser bookmarks, and Putty shortcuts, etc.
- Think of what you've forgotten, there's bound to be something!