Mike's PBX Cookbook

Upgrading a 4.5 E & T with SSC chassis to 5.5

Lets get rid of that T switch!

There are a couple of possible hardware options, so check your BOM before starting. Ideally, we will want to replace the SSC cards in each expansion cabinet with MGC's, although it is possible to keep the SSC's in service and only upgrade their firmware. If you only have a couple of MGC's in your BOM, they are intended for the T switch only. Prepare for a good few hours of down time, especially if you are keeping the SSC's.

1. Make sure you have everything:

2. Perform an EDD, and copy the backup folder to the 5.5 install flash disk (RMD) root.

3. On the inactive core:

4. Follow the on screen instructions!

5. When complete, issue the command: LD 135, CUTOVR - this will force the PBX to switch over to the new 5.5 core, and make it active.

6. The call server will reboot, and start loading the SSC's (MGC's) with new firmware. Be warned, this will take a while!

Alternatively, replace the SSC's with MGC's, pre-configured with the correct IP addresses, although you might not have this luxury - obviously, check your BOM before starting. If you only have a couple of MGC's, they are intended for the T switch.

7. Copy the newly saved database folder to the 5.5 install flash card. and repeat this procedure to install the software on the other (now inactive) core. This goes quite fast.

8. When the second core is ready, from the active core, issue the command: LD 135, STAT CPU, then JOIN. There will be some syncing, and the system will go redundant. When the activity is over, try a SCPU command to force a switch over. It should go smoothly, and the inactive side will INI.

Don't forget to load the patches!

We can remove the VGMC cards....

The next task is to incorporate the T switch into the E.

T, be gone!

  1. Replace the T switch SSC cards with MGC's, pre-programmed with a valid IP address and DSP daughter board(s).
    Follow the MGC Card Settings procedure to prepare the MGC's.
  2. You will need T-Lan and E-lan connections back to the Baystack, the T-Lan is new.
  3. Add the MGC's as new loops in Element Manager.
    They will load and, when registered, display the correct loop and shelf info on each display.
  4. Re-build the routes and trunks on the new loop, and make changes as necessary to the RLI's (LD 86) to enable outgoing calls. Routes with an access code will need to have the now redundant DSC (Distant Steering Code - LD 87) deleted first.
  5. The NRS routing tables can be deleted, they are no longer relevant.

Checking the Upgrade Status

The SSC upgrades take A LONG TIME, approximately 30 to 60 mins per SSC. Patience, grasshopper!
You can check the Upgrade Status with LD 143, and the UPGMG STAT command from time to time.

.upgmg stat
|            IPMG SOFTWARE UPGRADE STATUS         |
|  Auto Sequential Software Upgrade is Enabled    |
|      |        |                    |IPMG| NEEDS |
|  4 0 | SUCCESS| 2011/09/16 19:52:01| SSC|   NO  |
|  4 1 | SUCCESS| 2011/09/16 20:22:26| SSC|   NO  |
|  8 0 | SUCCESS| 2011/09/16 20:54:14| SSC|   NO  |
|  8 1 | RUNNING| 0000/00/00 00:00:00| SSC|   NO  |
| 12 0 | PENDING| 0000/00/00 00:00:00| SSC|  YES  |
| 12 1 | PENDING| 0000/00/00 00:00:00| SSC|  YES  |
| 16 0 | SUCCESS| 2011/09/16 19:19:23| SSC|   NO  |
| 16 1 | PENDING| 0000/00/00 00:00:00| SSC|  YES  |
| 20 0 | PENDING| 0000/00/00 00:00:00| SSC|  YES  |
SRPT077 Media Gateway/Expansion Cabinet 6: 0% of Centralized Software Upgrade complete.

SRPT077 Media Gateway/Expansion Cabinet 6: 6% of Centralized Software Upgrade complete.

When the upgrade process is complete, the SSC will restart and register, and the IPE cards will enable. Until this stage, you will not have dial-tone. This happens one shelf at a time.

SRPT177 STARTUP: IPMG [8 1] registration has been granted. IP [] and Serial No [40015348]

SRPT017 OMM: IP link is UP between Call Server and IPMG[8 1]

XMI002 8  1 1  XDLC

XMI002 8  1 2  XDLC

XMI002 8  1 9  XMLC

XMI002 8  1 10  XOPS

XMI002 8  1 3  XDLC

XMI002 8  1 7  EXUT

Upgrading the Signaling Server from 4.5 to 5.5

1. Upgrade the RAM: Hook up the rear panel TTY to a PC (19.2-8N1), boot up, and check that you have 1GB (1024KB) RAM installed. If not, you must upgrade the RAM before continuing. You'll need 2 of NTDU80CA Signaling Server Memory Upgrade Kit's per server as each kit provides a whopping 512KB (2x256KB DIMMs). Discard the old 128MB DIMMs.

2. Upgrade the software: Having checked and/or upgraded the RAM, put the "CS1000 Signaling Server Application Release 5.5" CDROM in the drive, and power on the server. When prompted, press C to boot from the CDROM. Follow the on screen instructions. From the install menu, pick option A to load everything. Note that the server configuration is preserved if upgrading from 4.5, so there is no need to worry about backups, or leader / follower settings.

3. Re-install the server: After its booted, you can check its software version and role by logging into the NRS (admin/admin). The Sig Server software release must match the Call Server software release version. It seems obvious, but otherwise nothing will register.

Upgrading the VGMC's from 4.5 to 5.5

  1. Find the "IPL55012.sa" file, its in the root directory of the 5.5 Sig Server Application CDROM. Copy it to your PC.

  2. Remove the VGMC, and remove the Flash card on it. Using a Flash to USB reader, mount the card on your PC.

  3. Rename the "IPL55012.sa" file to "exec", with no extension, and copy it to the VGMC Flash card, replacing the older/smaller version already there (you might want to back this file up first).

  4. Replace the VGMC, and watch it boot. Shortly after it responds to a Ping, it should register.

  5. Check the VGMC loadware in Element Manager: software -> Voice Gateway Media Card, click on the Node, the VGMC's are listed, click "LW Version" to check, and scroll down to see the results box......

Installed Image:     IPL IPL-5.50.12 (SMC) - Wed Feb  6 18:51:34 EST 2008
Additional Modules:
vxWorks.sym          VxWorks5.5.1


Tidy up the CEQU

Printing and STATing the CEQU might show some redundant programming which can be removed. You can delete any loops which are not responding, and tone / conference loops which don't exist. The CNI's are also not needed, and can be deleted - the syntax is a bit tricky for CNI's:

>ld 17
REQ chg
TYPE cequ

enter down to:

EXTO 3pe
CNI 10 0 x2            <---- outs group 2
CNI 10 1 x3            <---- outs group 3
CNI 11 0 x4            <---- outs group 4
CNI 11 1 x5            <---- outs group 5
CNI 12 0 x6            <---- outs group 6
CNI 12 0 x7            <---- outs group 7

EXT1 3pe
CNI 10 0 x2            <---- outs group 2
CNI 10 1 x3            <---- outs group 3
CNI 11 0 x4            <---- outs group 4
CNI 11 1 x5            <---- outs group 5
CNI 12 0 x6            <---- outs group 6
CNI 12 0 x7            <---- outs group 7

Also, don't forget to check ADAN, and re-build any TTY's you might need, such as for CDR. The CDR port can be built on the MGC in the new loop.

Home » Meridian » Install » 45to55up