|
|
This chapter presents SS7 interconnect troubleshooting tasks related to the Cisco ASAP Solution and the PSTN gateway solutions that are performed on elements of the Cisco Media Gateway Controller (MGC) node. The components of these solutions are discussed in "Operating and Maintaining SS7 Components."
The Cisco MGC node is made up of Cisco MGC host(s) and Cisco Signaling Link Terminals (SLTs) connected by a LAN switch. The Cisco MGC Node is used in two products: the Cisco SC2200 and the Cisco PGW 2200.
 |
Note The procedures in this chapter apply only to Cisco ASAP Solutions that use SS7 interconnect or Cisco SS7 Interconnect for Voice Gateways Solutions. |
This chapter presents the following major troubleshooting topics:
 |
Tip See also Task Summary. |
The tasks in this chapter address the following components of the Cisco ASAP Solution and the PSTN gateway solutions: components of the Cisco MGC node.
The Cisco ASAP Solution and Release 1.3 of the Cisco SS7 Interconnect for Voice Gateways uses Release 7 of the Cisco MGC software; Cisco PSTN Gateway Solution and Release 2.0 of the Cisco SS7 Interconnect for Voice Gateways Solution uses Release 9 of the Cisco MGC software. Some documentation such as the following can be used in both releases:
The respective references are provided below.
For the following procedures, refer to Cisco Media Gateway Controller Software Release 7 Operations, Maintenance, and Troubleshooting Guide at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel7/omts/
For the following procedures, refer to Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/omts/
The tasks in this chapter are listed below, grouped by major category.
Summary | You must retrieve all of the active alarms on the Cisco MGC node to identify SS7 interconnect problems. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) and Cisco SLT (Cisco 2611 or Cisco 2651) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To retrieve all active alarms:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Retrieving All Active Alarms.
Step 3 As appropriate, follow the steps in one or more of the following sections:
a. Acknowledging Alarms
b. Clearing Alarms
Summary | Viewing Cisco MGC system logs can provide additional information about system problems. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To view system logs:
Step 1 In the above reference, refer to Chapter 3, "Cisco MGC Node Operations."
Step 2 Read the section Using the Log Viewer and follow the instructions therein.
Step 3 Also refer to Chapter 8, "Troubleshooting the Cisco MGC Node,"and follow the instructions in the section Viewing System Logs.
Summary | Some Cisco MGC node alarms require that the user take corrective action to resolve the indicated problem. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) and Cisco SLT (Cisco 2611 or Cisco 2651) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To retrieve all active alarms:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Search for the alarm of interest in the Alarm Troubleshooting Procedures section.
Step 3 Perform the steps listed in the appropriate section.
If the alarm is not listed in the Alarm Troubleshooting Procedures section, refer to the Cisco Media Gateway Controller Software Release 7 System Messages Guide for information on the alarm. See References.
Summary | Use this procedure to resolve SS7 link problems. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) or Cisco SLT |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To restore an SS7 link to service:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section SS7 Link is Out of Service and follow the instructions therein.
Summary | Use this procedure to resolve SS7 load sharing problems. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To resolve an SS7 load sharing malfunction:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section SS7 Load Sharing Malfunction and follow the instructions therein.
Summary | Use this procedure to resolve physical layer problems in the Cisco MGC node. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) or Cisco SLT |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To resolve physical layer problems in the Cisco MGC node:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Physical Layer Failure and follow the instructions therein.
Summary | Use this procedure to correct a situation where SS7 links are "bouncing," or going in and out of service repeatedly. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) or Cisco SLT |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To correct bouncing SS7 links:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Bouncing SS7 Links and follow the instructions therein.
Summary | Use this procedure to restore an SS7 DPC (destination point code) to service. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To restore an SS7 destination to service:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section SS7 Destination is Out-of-Service and follow the instructions therein.
Summary | Use this procedure to restore an SS7 route to service. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) or Cisco SLT |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To restore an SS7 route to service:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section SS7 Route is Out-of-Service and follow the instructions therein.
Summary | Use this procedure to correct a situation where an SS7 DPC is unavailable. An SS7 DPC is unavailable when all of the routes to the destination are out-of-service. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) or Cisco SLT |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To make an SS7 DPC available:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section SS7 Destination is Unavailable and follow the instructions therein.
Summary | Troubleshooting SS7 network problems sometimes requires that you verify that your local message transfer part (MTP) timer settings match those being used on the far end. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) or Cisco SLT |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To verify the settings of your local MTP timers:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Verifying MTP Timer Settings.
Step 3 If necessary, modify your MTP timer settings as described in the Modifying MTP Timer Settings section.
Summary | Use this procedure to modify the settings of your local MTP timers. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) or Cisco SLT |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To modify the settings of the MTP timers:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Modifying MTP Timer Settings and follow the instructions therein.
Summary | Use this procedure to verify that a dial plan has loaded properly. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To verify that a dial plan has loaded properly:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Verifying Proper Loading of a Dial Plan and follow the instructions therein.
Summary | In the course of troubleshooting problems with your bearer channels, you may need to query the local and remote states of the related circuit identification codes (CICs), to verify that they match. This procedure contains steps to query local and remote CIC states. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To query the state of a local or remote CIC:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Querying Local and Remote CIC States.
Step 3 If the local and remote CIC states do not match, attempt to resolve the state mismatch using the steps in the Resolving Local and Remote CIC State Mismatch section.
Summary | When the local and remote states for CICs do not match and the problem lies with the local CIC states, you can attempt to resolve the mismatch by using this procedure. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To resolve a state mismatch between the local and remote CICs:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Resolving Local and Remote CIC State Mismatch and follow the instructions therein.
Summary | When performing initial turn-up of CICs or in troubleshooting certain problems with your bearer channels, you may want to perform a CIC validation test to verify that the properties defined in the Cisco MGC for the affected bearer channels match the associated properties defined in the far-end exchange. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To perform a CIC validation test:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Performing a CIC Validation Test and follow the instructions therein.
Summary | When there is a mismatch between the D-channels configured on the Cisco MGC and those configured on the associated media gateway, an ISDN log message is generated. To resolve the log message, use this procedure. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) and Cisco AS5000 series |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To resolve ISDN D-channel discrepancies:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Resolving ISDN D-Channel Discrepancies and follow the instructions therein.
Summary | Contains steps for unblocking CICs. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To unblock CICs:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Unblocking CICs and follow the instructions therein.
Step 3 If the CICs are still blocked, perform the steps in the Resetting CICs section.
Summary | Use this procedure to reset CICs. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To reset CICs:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Resetting CICs and follow the instructions therein.
Step 3 If the CICs did not reset properly, perform the steps in the Resolving Stuck CICs section.
Summary | A stuck or hung CIC occurs when one or more bearer channels associated with a single call instance refuses to return to the idle call state, despite attempts to clear it manually. Stuck CICs are generally caused when transient network glitches or configuration errors trigger protocol state-machine errors. Typically these conditions result in a mismatch between the CIC's call state on the Cisco MGC and the call state for the associated span and bearer channel (also known as the timeslot) on the media gateway. Stuck CICs are typically resolved automatically. This procedure is a manual method of resolving stuck CICs. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) and Cisco AS5000 series |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To resolve a state mismatch between the local and remote CICs:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Resolving Stuck CICs and follow the instructions therein.
Summary | Use this procedure to perform a continuity test (COT) manually. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To run a manual COT:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Running a Manual Continuity Test and follow the instructions therein.
Step 3 If the COT fails, perform the steps in the Verifying Continuity Test Settings section.
Summary | If a COT should fail, use this procedure to verify that your COT settings are correct. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) and Cisco AS5000 series |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To verify the COT settings:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Verifying Continuity Test Settings and follow the instructions therein.
Summary | Use this procedure to restore service to an IP link or destination associated with a media gateway. Note An IP destination to a media gateway is out-of-service when both IP links associated with the destination are out-of-service. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) and Cisco AS5000 series |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To restore service to an IP link or destination associated with a media gateway:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Media Gateway IP Destination/Link is Out-of-Service and follow the instructions therein.
Summary | If calls appear to be failing at the Cisco MGC, and the calls are not appearing on the associated media gateway, use this procedure. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To resolve a situation where calls are failing at the Cisco MGC:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Calls Fail at the Cisco MGC and follow the instructions therein.
Summary | Use this procedure to modify the redundant link manager (RLM) timers. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) and Cisco AS5000 series |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To modify the RLM timers:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Modifying Redundant Link Manager Timers and follow the instructions therein.
Summary | Use this procedure to perform a call trace on the Cisco MGC. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To perform a call trace:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Performing a Call Trace and follow the instructions therein.
Summary | When you need to perform a call trace to diagnose either a hung call or an abnormally terminated call, and do not want to reduce the performance of your system, use this procedure. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To perform an alternative call trace method:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Alternatives to Call Tracing and follow the instructions therein.
Summary | Use this procedure to perform a TCAP trace on the Cisco MGC. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To perform a TCAP trace on the Cisco MGC:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Resolving Performing a TCAP Trace and follow the instructions therein.
Summary | You may need to delete files from your Cisco MGC host(s) to ensure the proper functioning of your system. Use this procedure to delete unnecessary files. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To delete unnecessary files from the disk drives of your Cisco MGC host(s):
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Deleting Unnecessary Disk Files to Increase Available Space and follow the instructions therein.
Summary | Use this procedure to recover your Cisco MGC system from a switchover failure. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To recover from a switchover failure:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Recovering from a Switchover Failure and follow the instructions therein.
Summary | There are situations, such as a replacement of a failed disk drive, a natural or man-made disaster, or software corruption, that make it necessary for you to recover the software configuration data for a failed Cisco MGC host or hosts. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To recover from a failed Cisco MGC host or hosts:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Recovering from Cisco MGC Host(s) Failure and follow the instructions therein.
Summary | To resolve problems where the Cisco MGC is not functioning properly as a result of hardware failure, natural disaster, or software corruption, you will need to restore stored configuration data. The steps in this procedure assume that you have been performing regular software backup operations. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To restore stored configuration data:
 |
Caution To be able to perform this procedure, you must have been backing up the Cisco MGC software on a regular basis. For more information on backing up the Cisco MGC, refer to the Backing Up System Software section in Chapter 3 "Cisco MGC Node Operations" of the appropriate release of the Cisco Media Gateway Controller Software Operations, Maintenance, and Troubleshooting Guide. |
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Restoring Stored Configuration Data and follow the steps therein.
Summary | If calls are not being preserved when your system performs a switchover, use this procedure to verify that your system is properly configured to replicate call data. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To verify that replication has been configured correctly on your system:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Verification of Proper Configuration of Replication and follow the instructions therein.
Summary | If your Cisco MGC is not producing system measurements, use this procedure. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To configure your system to record system measurements:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Measurements Not Being Generated and follow the instructions therein.
Summary | If call detail records (CDRs) are not being generated by your system, use this procedure. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) |
Application | See Introduction |
Frequency | As needed. |
Depends on the solution and related release of the Cisco MGC software. See References.
To configure your system to produce CDRs:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Call Detail Records Not Being Generated and follow the instructions therein.
Summary | When you are modifying certain properties on the Cisco MGC, you must reboot your system as part of the modification process. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To reboot your Cisco MGC software to modify properties:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Rebooting Your System To Modify Properties and follow the instructions therein.
Summary | If you have lost connection to a peer component in your network, perform this procedure. |
Target Platform(s) | Cisco MGC (Cisco SC2200 or Cisco PGW 2200) |
Application | See Introduction |
Frequency | As needed |
Depends on the solution and related release of the Cisco MGC software. See References.
To resolve a failed connection to a peer:
Step 1 In the above reference, refer to Chapter 8, "Troubleshooting the Cisco MGC Node."
Step 2 Read the section Resolving a Failed Connection to a Peer and follow the instructions therein.
Posted: Wed Oct 2 12:33:36 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.