Completing the Upgrade

After installing the new software on the SC host, you must provision your configuration using MML or the TCM/CMM. If you added Cisco SLTs, you must provision these into the configuration. You should have the names of the components in your solution available. For more information, see the "Gathering Provisioning Data" section.

Note Although provisioning data is migrated from Software Release 4 to Software Release 7, it is likely that your old configuration will not work with the new software. You must provision your configuration again and commit or deploy it to the SC host.

For an overview of provisioning and instructions to assist you, see Cisco Media Gateway Controller Software Release 7 Provisioning Guide. For instructions on provisioning a sample Cisco SS7 Interconnect for Access Servers Solution, see Cisco SS7 Interconnect for Access Servers Solution Provisioning Guide.

TimeSaver To save time, you can use an MML batch file to provision your system. This requires that you enter all MML commands to provision your system into an ASCII text file and import the file. See the Cisco SS7 Interconnect for Access Servers Solution Provisioning Guide for more information and a sample batch file.

Tips The SC software must be running in order to provision the system. If you encounter problems, make sure the software is running. Refer to the "Starting the SC Software" section.

Terminating Signaling Links

The SS7 signaling links connect the SC host running Cisco SC software to an SS7 switch. These connections can be terminated in two ways:

SS7 signaling links are connected to the Cisco SLT, which connects to the SC host over IP (recommended).
ITK or PTI cards on the SC host terminate the links at the host itself.

Although Cisco currently supports both of these connections, using ITK or PTI cards in new 2.1 systems or upgraded 2.0 systems is not recommended. Terminating SS7 signaling links at the Cisco SLT enhances the switchover performance of the system and is the preferred method for new or upgraded systems.

Tips Depending on the type of cards, you might need a straight-through connector to terminate the links.

Connecting Signaling to the Cisco SLTs

If you are upgrading a standalone machine, you can remove the links from your machine and connect them to the Cisco SLTs now.

If you have a high-availability configuration, perform these steps:

Step 1 Log in as root to the second SC host that is currently processing calls.

Step 2 Enter the /etc/init.d/transpath stop command to shut down the software. Leave the SC software on the newly upgraded host running.

Caution When you remove the signaling links from the host and terminate them into the Cisco SLT, the host will stop processing calls. Your host will be down until you start the software on the newly upgraded host. You should plan to connect the signaling links during a maintenance window or a low traffic period to minimize call attempt losses.

Note You should coordinate with your SS7 link service provider to let them know that your links will go out of service. Your provider should have onsite support staff available to assist you should there be problems reestablishing the links.

The Cisco SLT requires the Cisco 2611 modular access router with T1 or E1 interfaces running a special release of Cisco IOS software. The Cisco SLT has the following restrictions:

Only the following Interface Cards are supported. No other cards, or Cisco 2600 or Cisco 3600 series network modules, are supported:
- 1-port T1 multiflex trunk interface (VWIC-1MFT-T1)
- 1-port E1 multiflex trunk interface (VWIC-1MFT-E1)
- 2-port T1 multiflex trunk interface (VWIC-2MFT-T1)
- 2-port E1 multiflex trunk interface (VWIC-2MFT-E1)
- 2-port T1 multiflex trunk interface with Drop and Insert (VWIC-2MFT-T1-DI)
- 2-port E1 multiflex trunk interface with Drop and Insert (VWIC-2MFT-E1-DI)
- 1-port high-speed serial interface (WIC-1T)
- 2-port high-speed serial interface (WIC-2T)
Only SS7 serial interfaces and protocols are supported. There is no support for HDLC, PPP, Frame Relay, ATM, X.25, or other non-SS7 serial WAN protocols.
Only two SS7 signaling links are supported per Cisco SLT.
Only one SS7 signaling link is supported per T1 or E1 port.

Moving the Signaling Links in a Standalone Configuration

To move the signaling links, follow these steps:

Step 1 Verify that the Cisco SLT has the WIC that matches your signaling links (either E1 or T1).

Step 2 Connect the Cisco SLT to the Ethernet interface. How you connect to the Cisco SLT will depend on how many SS7 signaling links you have.

If you have one SS7 signaling link, unplug the SS7 signaling link from the ITK card on the SC host and plug it into the WIC on the Cisco SLT.

If you have two SS7 signaling links, follow these steps:

a. Connect Cisco SLT-1 to Ethernet segment 1.

b. Connect Cisco SLT-2 to Ethernet segment 2.

c. Unplug SS7 signaling link #1 from the ITK card on the SC host, and plug it into the WIC on Cisco SLT-1.

d. Unplug SS7 signaling link #2 from the ITK card on the SC host, and plug it into the WIC on Cisco SLT-2.

Step 3 After plugging the links into the Cisco SLT, the carrier detect (CD) light on the back of the Cisco SLT should be green.

Moving the Signaling Links in a Continuous-Service Configuration

To move the signaling links, follow these steps:

Step 1 Verify that the Cisco SLT has the WIC that matches your signaling links (either E1 or T1).

Step 2 Connect the Cisco SLT to the Ethernet interface. How you connect to the Cisco SLT will depend on how many SS7 signaling links you have.

If you have one SS7 signaling link, unplug the SS7 signaling link from the ITK card on the SC host and plug it into the WIC on the Cisco SLT.

If you have two SS7 signaling links, follow these steps:

a. Connect Cisco SLT-1 to Ethernet segment 1.

b. Connect Cisco SLT-2 to Ethernet segment 2.

c. Unplug SS7 signaling link #1 from the ITK card on the SC host, and plug it into the WIC on Cisco SLT-1.

d. Unplug SS7 signaling link #2 from the ITK card on the SC host, and plug it into the WIC on Cisco SLT-2.

Tips If you have more than 1 link in a linkset, only move 1 link at first to test the functionality. If that link comes up, you can move the other links. If the test link does not come up, move it back to the machine that has not been upgraded and restart the SC software on that machine.

Step 3 After plugging the links into the Cisco SLT, the carrier detect (CD) light on the back of the Cisco SLT should be green.

Connecting Signaling to the ITK Cards

If you currently have ITK cards, you are not required to perform any additional action. You already added the drivers for these cards in the "Installing Drivers for ITK/PTI Signaling Cards" section. Skip to the "Restarting and Verifying the Newly Upgraded Host" section.

Restarting and Verifying the Newly Upgraded Host

After upgrading the host, provisioning the Cisco SLTs, and terminating the signaling links, you need to stop and start the host to make it active. To start the host:

Step 1 Log in to the SC host as root. The SC software should already be running.

Step 2 Stop the SC software by entering the following command:

/etc/init.d/transpath stop

Note If you have a high-availability configuration, you have not yet upgraded the standby host, so you will not see connectivity with the standby.

Note For Software Release 7.4(x), stop the SC software by entering the /etc/init.d/CiscoMGC stop command.

Step 3 Activate the signaling links using MML. Start MML by performing the following steps:

a. Change to any subdirectory under /opt/TransPath (for example, /opt/Transpath/bin).

Note For SC Software Release 7.4(x), change to any subdirectory under /opt/CiscoMGC (for example, /opt/CiscoMGC/bin).

b. Enter the following command:

mml

: If you receive an error message that sessions are already in use, enter the following command:

mml -s session number

: For session number, use any number from 2 to 12 and repeat until you find a vacant session. After successfully entering MML, the prompt changes to:

machine-name mml>

Step 4 Set the signaling links into service by entering the following MML command:

set-sc-state:linkname:IS

Linkname is the name you provisioned in the "Provisioning the Configuration" section. If you have ITK cards, it is the name of the TDM link in your configuration.

Step 5 Verify the SS7 links are active and the machine is processing calls. Enter the following MML command:

rtrv-ne

The system returns a message similar to the following showing the software version and platform state. Verify the platform state is active.

machine-name mml> rtrv-ne
   Virtual Switch Controller 1999-12-16 17:14:31
M  RTRV
   "Type:VSC"
   "Hardware platform:sun4u sparc SUNW,Ultra-30"
   "Vendor:"Cisco Systems, Inc.""
   "Location:Virtual Switch Controller"
   "Version:"7.3(8)""
   "Platform State:ACTIVE"
   ;

Step 6 Retrieve the status of all signaling channels and link sets by entering the following MML command:

rtrv-sc:all

Verify all links are IS.

Step 7 Check the status of all paths to the destination switch by entering:

rtrv-dest:all

The system returns information about the status of the paths. Verify all paths are in service (IS).

Step 8 Retrieve any alarms by entering the following MML command:

rtrv-alms

Verify the system has no major alarms. These will be noted as SEV=MJ.

For troubleshooting procedures, see Cisco Media Gateway Controller Software Release 7 Operations, Maintenance, and Troubleshooting Guide.

Backout Procedures

If you cannot bring the links up, perform the following steps:

Step 1 In a high-availability configuration, remove the signaling links from the Cisco SLTs. Terminate them back into the ITK cards in your standby SC host (that has not been upgraded).

Step 2 Log in as root to the standby SC host and restart the software by entering /etc/init.d/transpath start.

Step 3 In a simplex configuration, perform the following steps:

a. Uninstall the SC software.

b. Uninstall the Solaris 2.6 software.

c. Reinstall Solaris 2.5.

d. Reinstall the SC Software Release 4.

e. Restore your backed up files.

f. Remove the signaling links from the Cisco SLTs and terminate them into the SC host.

Upgrading Cisco IOS Software on the NAS

Determining Your Cisco IOS Version

To determine the version of Cisco IOS software running on your Cisco AS5X00, log in to the Cisco AS5X00 and enter the show version EXEC command:

router> show version
     Cisco Internetwork Operating System Software 
     IOS (tm) 12.1 Software c5300-i-mz, Version 12.1(2), RELEASE SOFTWARE

To determine which Cisco IOS version is necessary for the Cisco SS7 Interconnect for Access Servers Solution, refer to the latest version of the Release Notes for Cisco Telephony Controller Software Release 7.3(x) or Release Notes for Cisco Media Gateway Controller Software Release 7.4(x) (available from your Cisco representative).

Upgrading IOS

For general information about upgrading to a new software release, see Cisco IOS Upgrade Ordering Instructions located at the following URL:

http://www.cisco.com/warp/public/cc/cisco/mkt/ios/prodlit/957_pp.htm

For instructions on how to download portware to Cisco AS5200, Cisco AS5300, and Cisco AS5800 Universal Access Servers, see the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/mod_info/5238.htm

For more information about upgrading and configuring Cisco IOS software on the media gateway, see Cisco SS7 Interconnect for Access Servers and Voice Gateways Solutions Gateway Guide.

Where to Go Next

If you have a simplex configuration, you have completed the upgrade.

If you have a high-availability configuration, go to the "Upgrading and Verifying the Second Server" section.

Upgrading and Verifying the Second Server

After upgrading the standby server and making it active, you must upgrade the standby server that is running Software Release 4. To upgrade the standby server, perform the following steps:

Step 1 Back up existing software data files on the standby server. See "Backing Up and Restoring Your Data."

Step 2 Upgrade any hardware if necessary. See "Upgrading Hardware."

Step 3 Upgrade the Sun Solaris operating system. See "Installing the Sun Solaris 2.6 Operating System."

Step 4 Restore your SC host data. See "Backing Up and Restoring Your Data."

Step 5 Install the SC software. See "Installing and Configuring the SC Software."

Step 6 Edit the XECfgParm.dat file parameters. See the "Configuring the Execution Environment" section.

Note If you have a continuous-service or high-availability configuration, you can now change the pom.dataSync parameter to true. See the "Initializing the Provisioning Object Manager (POM)" section for more information.

Step 7 Reboot the standby SC host. It starts as the standby host in the pair.

Step 8 On the active host, start MML or the TCM/CMM and deploy the configuration to save it to the standby.

Step 9 Enable database replication between the two hosts. Refer to the "Replication in a Continuous-Service Configuration" section.

Step 10 On the active host, start MML and enter the following command:

sw-over::CONFIRM

This stops call processing on the active machine and transfers call processing actions to the standby, which becomes the active machine.

Note In order for a successful switchover, you must have deployed the configuration to the standby machine, and you must have set the pom.dataSync parameter to true.

Step 11 Log in to the active machine and verify the SS7 links are active and the machine is processing calls. Enter the following MML command:

rtrv-ne

The system returns a message similar to the following showing the software version and platform state. Verify the platform state is active.

machine-name mml> rtrv-ne
   Virtual Switch Controller 1999-12-16 17:14:31
M  RTRV
   "Type:VSC"
   "Hardware platform:sun4u sparc SUNW,Ultra-30"
   "Vendor:"Cisco Systems, Inc.""
   "Location:Virtual Switch Controller"
   "Version:"7.3(8)""
   "Platform State:ACTIVE"
   ;

Step 12 Retrieve the status of all signaling channels and link sets by entering the following MML command:

rtrv-sc:all

Verify all links are IS.

Step 13 Check the status of all paths to the destination switch by entering:

rtrv-dest:all

The system returns information about the status of the paths. Verify all paths are in service (IS).

Step 14 Retrieve any alarms by entering the following command:

rtrv-alms

Verify the system has no major alarms. These will be noted as SEV=MJ.

If the active host is processing calls, you have completed the upgrade. If you have problems, refer to Cisco Media Gateway Controller Software Release 7 Operations, Maintenance, and Troubleshooting Guide.

Migrating Additional Configurations

When installing the software, only the active configuration files (located in /opt/TransPath/etc) are migrated. You can use the migrate script to migrate old configurations to a new version. To use the migrate script:

Step 1 Log in to the SC host.

Step 2 Enter the following command:

migrate top-leveldirectory sourcedirectory destinationdirectory

Top-leveldirectory is the software directory. For Software Release 7.3(x), it is /opt/TransPath; for Software Release 7.4(x), it is /opt/CiscoMGC. Sourcedirectory is the relative path of the directory that you want to migrate. Destinationdirectory is the relative path of the directory into which the migrated files are copied. If the directory does not exist, the migrate script creates it. If the directory exists, you are prompted to overwrite it.

Table of Contents

Completing the Upgrade