Cisco PGW 2200 Softswitch Release 9.8 Operations, Maintenance, and Troubleshooting Guide March 7, 2011 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
C O N T E N T S Preface xvii Document Objectives Audience i-xvii i-xvii Related Documentation i-xvii Obtaining Documentation and Submitting a Service Request Document Change History CHAPTER 1 i-xviii i-xviii Cisco PGW 2200 Softswitch Platform Overview 1-1 Cisco PGW 2200 Softswitch Platform 1-1 Cisco PGW 2200 Softswitch 1-1 Sun UNIX Hosts 1-2 Cisco SS7 Interfaces 1-2 Cisco ITP-Ls 1-2 Cisco ITPs 1-2 Cisco Switches 1-2 Ethernet Connections 1-3 Cisco PGW 2200 Softswitch Software Architecture Input
Contents Shutting Down the Cisco PGW 2200 Softswitch Hardware Cisco SS7 Interface Shutdown Procedure Cisco Switch Shutdown Procedure CHAPTER 3 2-5 2-5 2-6 Cisco PGW 2200 Softswitch Platform Operations 3-1 Daily Tasks 3-1 Starting an MML Session 3-2 Verifying the Platform State of the Cisco PGW 2200 Softswitches 3-2 Verifying That Processes Are Running 3-4 Understanding Processes 3-5 Monitoring the Alarms Status 3-7 Understanding Alarms 3-7 An Alarm Example 3-8 Verifying the Status of all Signaling
Contents Ending an MML Session 3-42 Managing Signaling Channels 3-42 Retrieving Signaling Service States 3-45 Retrieving Service State of C7/SS7 Links or Linksets 3-45 Retrieving the Service State for IP Links 3-46 Retrieving the Service State for IP Routes 3-46 Retrieving the Service State of D-Channels 3-47 Retrieving the State of SS7 Signaling Services 3-48 Retrieving the State of SS7 Routes 3-49 Retrieving the State of All Local Subsystem Numbers 3-49 Retrieving the Service State for Associations 3-50
Contents Retrieving Measurements 3-105 Clearing Measurements 3-106 Retrieving Link or Linkset Measurements 3-106 Retrieving SS7 Signaling Point Measurements 3-108 Retrieving Measurement Thresholds 3-117 Modifying Measurement Thresholds 3-117 Managing Call Detail Records 3-118 Converting Individual CDR Files to ASCII Format 3-118 Converting Individual CDR Files to a Readable Format 3-118 Using the Cisco MGC Viewer Toolkit 3-119 Launching the Cisco MGC Toolbar 3-120 Using the Alarm Viewer 3-121 Using the Cal
Contents CHAPTER 5 Maintaining the Cisco PGW 2200 Softswitch 5-1 Checking Equipment Status 5-1 LEDs 5-2 Sun Netra T 1120/1400 and Sun Netra T 1125/1405 Sun Netra X4270 5-2 Sun Fire X4640 5-2 Maintaining Technical Support Staff 5-2 Skill Level of Personnel 5-2 Staff Software Troubleshooting Tools 5-2 5-3 Maintaining Components 5-3 Software Upgrades 5-3 CHAPTER 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Overview 6-1 Cisco ITP-L Failure 6-2 Cisco PGW 2200 Softswitch Fai
Contents ANAL: BTableFlt_DgtRangeError 6-16 ANAL: Cause_GetFail_CauseTbl 6-16 ANAL:Cause_GetFail_DigModTbl 6-17 ANAL: Cause_GetFail_InvldRsltType 6-17 ANAL:Cause_GetFail_LocTbl 6-17 ANAL:Cause_GetFail_RsltTbl 6-18 ANAL:Cause_InvldRslts_CauseTbl 6-18 ANAL: Cause_MdfyBFail_AnnounceID 6-19 ANAL: Cause_MdfyBFail_AppPtInvld 6-19 ANAL: Cause_Rte_LoopDetected 6-20 ANAL: CustId/StartIdx Missing 6-20 ANAL:DataBaseAccessFail 6-21 ANAL: Data Failure Rcvd 6-22 ANAL:dpselection_table_fail 6-22 ANAL:getDialplanBase_fail
Contents ANAL: TableFail_TNSTable 6-32 ANAL: TrunkGrpRsltCtrExceeded 6-32 Association Degraded 6-32 Association Fail 6-33 C7LNK ALGNMT LOST 6-33 C7DPC CONGESTION 6-33 C7LNK CONGESTION 6-34 C7LNK INHIBIT 6-34 C7SLTLnkCong 6-34 Call Back Feature Insertion Failure 6-35 Call Back Feature Deletion Failure 6-35 Charge Table Access Failure 6-35 Charge Table Load Failure 6-35 Comm Srvc Creation Error 6-36 Config Fail 6-37 CTI Connection Failed 6-37 CTI Version Mismatch 6-38 Dial Plan Loading Failed 6-38 DISK 6-38
Contents LIF LOS 6-51 LIF SES 6-52 LIF YELLOW 6-52 LIF: IDLE CHANGE 6-53 LIF: LOST CD 6-53 LIF: LOST CTS 6-54 M3UAKEY Ack Pending 6-54 MeterPulseTariff Table Load Failure 6-55 MMDB: Database unavailable 6-56 MMDB: Database cause switchover 6-56 MMDB: Database nearly full 6-56 NAS: AuditResponse Failure 6-56 NAS: CommsFailure 6-57 NAS: ResourceFailure 6-58 OLC: Leg1chanSeizedUnpackError 6-58 OLC: Leg1chanModifiedUnpackError 6-58 OLC: Leg1chanDeletedUnpackError 6-59 OLC: Leg1notifyUnpackError 6-59 OLC: Leg1d
Contents SC CONFIG FAIL 6-71 SC FAIL 6-71 SC M-OOS 6-72 SG Node Interface Fail 6-72 SG Pair Interface Fail 6-72 SIP: DNS CACHE NEARLY FULL 6-73 SIP: DNS SERVICE OOS 6-73 SIP: OOS 6-74 SIP Service Fail Over 6-74 Standby Warm Start 6-75 SS7 RTE KEY FAIL 6-76 SS7 SIG SRVC CONFIG FAIL 6-76 SS7 SIG SRVC UNAVAIL 6-77 SSN FAIL 6-78 SUAKEY Ack Pending 6-78 SUPPORT FAILED 6-79 SwitchoverFail 6-80 Tariff Table Access Failure 6-80 Tariff Table Load Failure 6-80 TLC: Leg2chanSeizedUnpackError 6-80 TLC: Leg2chanModifie
Contents SS7 Load Sharing Malfunction 6-97 Physical Layer Failures 6-98 Configuration Errors 6-98 Supporting Entity Failures 6-99 Incomplete Signaling 6-99 Changing Service States 6-99 Signaling Destination Problems 6-100 Bouncing SS7 Links 6-101 Configuration Errors 6-101 Traffic Restart 6-102 SS7 Destination is Out of Service 6-102 SS7 Route is Out of Service 6-102 SS7 Destination is Unavailable 6-103 Signaling Channel Troubleshooting Procedures 6-103 Setting the Service State of a Signaling Service 6-10
Contents Performing CIC Validation Tests 6-131 Resolving ISDN D-Channel Discrepancies 6-137 Unblocking CICs 6-139 Unblocking Locally Blocked CICs 6-139 Unblocking Remotely Blocked CICs 6-140 Resetting CICs 6-140 Resolving Stuck CICs 6-141 Manually Resolving Stuck CICs 6-142 Auditing Call States 6-144 Stopping Calls 6-144 Stopping Calls on a Cisco PGW 2200 Softswitch 6-145 Stopping Calls on a Media Gateway 6-145 Stopping Calls on a Trunk Group 6-145 Stopping Calls on a Signaling Service 6-145 Stopping Calls
Contents Platform Troubleshooting 6-169 Verifying Cisco PGW 2200 Softswitch Ethernet Operation 6-169 Deleting Unnecessary Files to Increase Available Disk Space 6-169 Recovering from a Switchover Failure 6-170 Recovering from Cisco PGW 2200 Softswitch Failure 6-172 Recovering from a Cisco PGW 2200 Softswitch Failure in a Simplex System 6-173 Recovering from a Single Cisco PGW 2200 Softswitch Failure in a Continuous Service System 6-175 Recovering from a Dual Cisco PGW 2200 Softswitch Failure in a Continuou
Contents PDU Verb Types B-2 Backhaul Message IDs B-3 Connection Management B-3 Backhaul Statistics B-4 Backhaul Congestion B-4 Link Status B-5 Troubleshooting SS7 Link Problems B-5 Checking Link Configuration Files B-5 Checking UDP Traffic Flows B-6 Checking Connection between Cisco PGW 2200 Softswitch and Cisco ITP-L Checking the T1/E1 Link State B-6 Verifying the Link Alignment Status B-6 Verifying Exchanged Point Codes B-7 Cross-Checking Configuration Files B-9 B-6 Troubleshooting Cisco ITP-L-to-STP S
Contents Cisco PGW 2200 Softswitch Release 9.
Preface Revised: March 7, 2011, OL-0800-14 This preface describes the objectives of this document and explains how to find additional information on related products and services.
Preface Obtaining Documentation and Submitting a Service Request You can also find the Cisco PGW 2200 Softswitch Documentation Map at the following URL: http://www.cisco.com/en/US/products/hw/vcallcon/ps2027/ products_documentation_roadmaps_list.html Other useful reference publications include: • Overviews of the related telephony solutions—Describe the Cisco telephony solutions with which the Cisco PGW 2200 Softswitch node is associated.
Preface Document Change History Release Number Document Number Change Date Change Summary 9.8(1) OL-0800-11 March 7, 2011 Corrected the description of the CallSuccess counter in Appendix D “Cisco PGW 2200 Softswitch Measurements.” 9.8(1) OL-0800-10 December 2008 Added new Cisco PGW 2200 Softswitch measurements in Release 9.8. 9.7(3) OL-0800-09 May 2008 Updated Cisco PGW 2200 Softswitch troubleshooting MML commands and system output in Release 9.7.
Preface Document Change History Cisco PGW 2200 Softswitch Release 9.
CH A P T E R 1 Cisco PGW 2200 Softswitch Platform Overview Revised: March 7, 2011, OL-0800-14 This chapter describes the components of the Cisco PGW 2200 Softswitch platform and presents the software architecture of the Cisco PGW 2200 Softswitch, Release 9.
Chapter 1 Cisco PGW 2200 Softswitch Platform Overview Cisco PGW 2200 Softswitch Platform • Providing Message Transfer Part (MTP) Level 3 (MTP3) functions • Providing advanced intelligent network (AIN) capabilities Sun UNIX Hosts The Cisco PGW 2200 Softswitch Release 9.8 Software Installation and Configuration Guide identifies the Sun UNIX hosts that support the releases of the Cisco PGW 2200 Softswitch software.
Chapter 1 Cisco PGW 2200 Softswitch Platform Overview Cisco PGW 2200 Softswitch Platform Table 1-1 shows the limitations of the WAN implementations. Table 1-1 Limitations on WAN Switches Within a Cisco PGW 2200 Softswitch Platform Condition Requirement Software release version Cisco PGW 2200 Softswitch software 9.3(2) or later (with associated operating system and hardware requirements). Total end-to-end delay, one way (the time Must be less than 150 milliseconds.
Chapter 1 Cisco PGW 2200 Softswitch Platform Overview Cisco PGW 2200 Softswitch Software Architecture Figure 1-1 Cisco PGW 2200 Softswitch Platform Connectivity Switch Fast Ethernet 100BT 100Base T 100Base T Active PGW Ethernet 10BT/100BT Supervisor engine Supervisor engine Standby PGW 100Base T 100Base T Switch Supervisor engine Cisco ITP Supervisor engine Fast Ethernet 100BT SS7 links to STP SS7 links to STP Cisco ITP-L SS7 links to STP Cisco ITP-L SS7 links to STP Ethernet active Ether
Chapter 1 Cisco PGW 2200 Softswitch Platform Overview Cisco PGW 2200 Softswitch Software Architecture Figure 1-2 Cisco PGW 2200 Softswitch Software System Diagram PGW I/O subsystem Event dispatcher queue INAP Replicator Failover daemon Fault tolerance TCAP/SCCP Call Engine IOCM TCAP SCCP XE/PXE Process Shell Data Manager Timers Signals IPC Log client Meas. client Alarm client Process Manager MML Fault Alarm Mgr Terminal Meas. Meas. Mgr Cisco MNM Cisco VSPT Config.
Chapter 1 Cisco PGW 2200 Softswitch Platform Overview Cisco PGW 2200 Softswitch Software Architecture Input/Output Subsystem The I/O subsystem consists of the I/O channel controllers (IOCC) and the I/O channel manager (IOCM), which manages the controllers. • IOCM manages all IOCCs. • IOCCs provide: – Protocol-specific, message-based interface that allows nodes and platforms that are external to the Cisco PGW 2200 Softswitch to communicate with the Cisco PGW 2200 Softswitch.
Chapter 1 Cisco PGW 2200 Softswitch Platform Overview Cisco PGW 2200 Softswitch Software Architecture Agent Management Subsystem The agent management subsystem (AMS) allows external client software or terminals to gain access to the data in the Cisco PGW 2200 Softswitch. This subsystem supports the following functions: • Configuration management—Enables you to add, delete, or modify parameters and resources on the Cisco PGW 200 Softswitch so that it can perform its switching function.
Chapter 1 Cisco PGW 2200 Softswitch Platform Overview Cisco PGW 2200 Softswitch Software Architecture – Rendezvous Routing Daemon (RVRD)—Used when the management system and the Cisco PGW 2200 Softswitches are not on the same network. You must configure the RVRD routing table and start RVRD manually before activating the interface on the Cisco PGW 2200 Softswitch. See the TIBCO user documentation for information on configuring the RVRD routing table.
Chapter 1 Cisco PGW 2200 Softswitch Platform Overview Cisco PGW 2200 Softswitch Software Architecture Execution Environment Process Shell The execution environment process shell is an operating system shell on the Cisco PGW 2200 Softswitch that enables it to access lower-level functionality. The low-level functions hold together the I/O, element management, and call engine subsystems on the Cisco PGW 2200 Softswitch.
Chapter 1 Cisco PGW 2200 Softswitch Platform Overview Cisco PGW 2200 Softswitch Software Architecture • Connection manager—Interfaces with the nodes and protocols external to the Cisco PGW 2200 Softswitch that are necessary to establish an IP (TCP, UDP, or RUDP) or PSTN connection that is managed by the Cisco PGW 2200 Softswitch. The types of nodes supported are: – VoIP/VoATM trunking gateways using MGCP. – Time Domain Multiplex (TDM) trunking gateways using MGCP.
Chapter 1 Cisco PGW 2200 Softswitch Platform Overview Cisco PGW 2200 Softswitch Software Directory Structure • linking the OCC and the terminating call control (TCC) • updating and retrieving the call context structures • interacting with other call engine components, such as the resource manager, connection manager, and call manager • managing bearer resources, such as trunking gateways • using the MGCP • keeping the call processing state machine.
Chapter 1 Cisco PGW 2200 Softswitch Platform Overview Cisco PGW 2200 Softswitch Software Directory Structure Table 1-2 utilizes the variable $BASEDIR to indicate the directory into which the Cisco PGW 2200 Softswitch software is installed. Table 1-2 Cisco PGW 2200 Softswitch Software Directory Structure Directory Description $BASEDIR/bin Cisco PGW 2200 Softswitch executable programs that cannot be customized. $BASEDIR/data MDL source files.
Chapter 1 Cisco PGW 2200 Softswitch Platform Overview Cisco PGW 2200 Softswitch Software Directory Structure Table 1-2 Cisco PGW 2200 Softswitch Software Directory Structure (continued) Directory Description $BASEDIR/var/spool Dumper Spool Area. This directory contains historic reports. See the “Understanding Logging Files” section on page A-1. $BASEDIR/var/trace Signal Path Trace area. This directory contains all MDL trace logs that are used for conversion analysis.
Chapter 1 Cisco PGW 2200 Softswitch Platform Overview Cisco PGW 2200 Softswitch Software Directory Structure Cisco PGW 2200 Softswitch Release 9.
CH A P T E R 2 Cisco PGW 2200 Softswitch Platform Component Startup and Shutdown Procedures Revised: March 7, 2011, OL-0800-14 This chapter describes how to start and shut down the individual components of the Cisco PGW 2200 Softswitch platform.
Chapter 2 Cisco PGW 2200 Softswitch Platform Component Startup and Shutdown Procedures Cisco PGW 2200 Softswitch Startup Procedures Cisco PGW 2200 Softswitch Startup Procedures This section contains the hardware and software startup procedures for the Cisco PGW 2200 Softswitch. Starting the Cisco PGW 2200 Softswitch Hardware The system switch of the Cisco PGW 2200 Softswitch is a rocker, momentary contact switch that functions as a standby device only.
Chapter 2 Cisco PGW 2200 Softswitch Platform Component Startup and Shutdown Procedures Cisco SS7 Interface Startup Procedure Note The Cisco PGW 2200 Softswitch includes license files that are stored in a directory from which the Cisco PGW 2200 Softswitch gets the required license information. The Cisco PGW 2200 Softswitch uses the license file to enforce the available features and capacity.
Chapter 2 Cisco PGW 2200 Softswitch Platform Component Startup and Shutdown Procedures Cisco Switch Startup Procedure Cisco Switch Startup Procedure This section contains the recommended startup procedure for the Cisco switches that internetwork with the elements of the Cisco PGW 2200 Softswitch platform. Note Ensure that the switch is installed and configured correctly and that the correct software version is installed.
Chapter 2 Cisco PGW 2200 Softswitch Platform Component Startup and Shutdown Procedures Cisco SS7 Interface Shutdown Procedure To manually stop the Cisco PGW 2200 Softswitch software, log into your active Cisco PGW 2200 Softswitch as root and enter the following command: # /etc/init.d/CiscoMGC stop This command disables the automated startup script. Shutting Down the Cisco PGW 2200 Softswitch Hardware To shut down the Cisco PGW 2200 Softswitch, remove power from the system.
Chapter 2 Cisco PGW 2200 Softswitch Platform Component Startup and Shutdown Procedures Cisco Switch Shutdown Procedure Cisco Switch Shutdown Procedure To shut down the Cisco switches, set the power switches to the OFF (0) position. When the power switches are in the OFF (0) position, the LEDs on the power supplies should be off and the fan assembly should not be operating. Cisco PGW 2200 Softswitch Release 9.
CH A P T E R 3 Cisco PGW 2200 Softswitch Platform Operations Revised: March 11, 2011, OL-0800-14 This chapter presents recommended operating procedures for the Cisco PGW 2200 Softswitch platform. Ensure that all components are correctly installed, configured, and provisioned according to the instructions provided in the relevant documentation. All components should have started successfully, as described in Chapter 2, “Cisco PGW 2200 Softswitch Platform Component Startup and Shutdown Procedures.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Daily Tasks • Verifying System Statistics, page 3-18 • Verifying the Number of Active Processes, page 3-19 • Verifying the Number of Users, page 3-21 • Verifying Available Virtual Memory, page 3-21 • Verifying Available Memory on the Cisco ITP-Ls, page 3-22 Starting an MML Session When a procedure requires that you start an MML session, you must perform the following steps: Note Step 1 You should run your MML sessions from the active Ci
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Daily Tasks "Hardware platform:sun4u sparc SUNW,Sun-Fire-V210" "Vendor:"Cisco Systems, Inc."" "Location:MGC-01 - Media Gateway Controller" "Version:"9.8(1)"" "Platform State:ACTIVE" The valid values for the Platform State field are ACTIVE, STANDBY, or OOS.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Daily Tasks Verifying That Processes Are Running To verify that the processes on your Cisco PGW 2200 Softswitch are running, perform the following steps: Step 1 Log in to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the following command: rtrv-softw:all The system returns a response like the following: Note The following sample output was generated by Cisco PGW 2200 Softswitch Release 9.7(3) Patch 14 software.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Daily Tasks If any of the processes stop, contact the Cisco TAC for assistance. See the “Obtaining Documentation and Submitting a Service Request” section on page xviii for more information on contacting the Cisco TAC. Understanding Processes The Cisco PGW 2200 Softswitch software contains processes and process groups that perform various functions.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Daily Tasks Table 3-1 Group Processes Controlled by the Process Manager (continued) Process Description ss7-i-1 SS7 protocol handler. It is a passive process. If it goes down, it causes a major out-of-service alarm. m3ua-1 M3UA protocol handler. It is a passive process. If it goes down, it causes a major out-of-service alarm. sua-1 SUA protocol handler. It is a passive process. If it goes down, it causes a major out-of-service alarm.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Daily Tasks Monitoring the Alarms Status If you monitor the alarm status of the Cisco PGW 2200 Softswitch continuously, you can determine how often a particular alarm occurs in a specific period.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Daily Tasks Component ID The first element of the alarm message identifies the system component that generated the alarm, using the customer-defined description of the component that is entered during system provisioning. In the example, these components are LPC-01, IOCM-01, MGC1alink2, and MGC1alink3. All system components are described in Cisco PGW 2200 Softswitch Release 9.8 Provisioning Guide.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Daily Tasks Output of rtrv-alms MML command MGC-01 - Media Gateway Controller 2008-4-21 03:14:42.733 EDT M RTRV "ss7svc1: 2008-4-21 03:12:15.563 EDT,ALM=\"SS7 SIG SRVC UNAVAIL\",SEV=MJ" In this example, the component that generates the alarm is ss7svc1. The timestamp for this alarm is 2008-4-21 03:12:15.563 EDT. The alarm category indicates that an SS7 signaling service is unavailable. The severity for this alarm is major.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Daily Tasks Note Step 2 If you enter the rtrv-dest:all MML command after a switchover has occurred, the state of some of the signaling services might be listed as undefined (UND). UND is the default state for a signaling service when the system starts. In this instance, UND indicates that the Cisco PGW 2200 Softswitch has not received a service state message for the associated signaling service since the switchover occurred.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Daily Tasks Primary Service State The PST field shows the current primary service state of the signaling service. In the example, all of the signaling services have a primary service state of IS. Table 3-2 lists the valid primary service state values: Table 3-2 Signaling Service Primary Service States Link State ID Link State Description AOOS Automatically out-of-service The system has taken the signaling service OOS1.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Daily Tasks • FLD—Failed. • FOOS—Forced out of service. • RST—Reset. • RSTO—Restored. • UND—Undefined. Note If you enter the rtrv-dest MML command after a switchover occurs, the state of some of the signaling services might be listed as undefined (UND). UND is the default state for a signaling service when the system starts.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Daily Tasks Understanding the SS7 Route State Information The following sections describe the information that is returned by the system when you enter the rtrv-rte command, as shown in the following example: "ss7srv1:linkset1,APC=apc-1,OPC=opc-1,PRIO=1,PST=IS,SST=NA" "ss7srv1:linkset2,APC=apc-2,OPC=opc-1,PRIO=1,PST=IS,SST=NA" "ss7srv2:linkset1,APC=apc-3,OPC=opc-2,PRIO=1,PST=IS,SST=NA" "ss7srv2:linkset2,APC=apc-3,OPC=opc-2,PRIO=1,PST=IS,SST=NA" Sign
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Daily Tasks Primary Service State The PST field shows the current primary service state of the destination. In the example, all of the SS7 routes have a primary service state of IS. Table 3-3 lists the valid primary service state values: Table 3-3 SS7 Route Primary Service States Link State ID Link State Description AOOS Automatically out-of-service System has taken the SS7 route OOS.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Daily Tasks • RINH—SS7 remote inhibit • RSTR—SS7 restricted • SERR—SS7 signal error • STBY—Cause standby • SUPPENT—Supporting entity • TPATH—Traffic path • UNK—Cause unknown Verifying CIC States You should verify the status of your circuit identification codes (CICs) in groups, to ensure that you have current state information. Retrieving the status of all of your CICs at once takes some time.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Daily Tasks "c7s-1:CIC=12,PST=IS,CALL=IDLE,GW_STAT=CXN_IS,BLK=NONE" "c7s-1:CIC=13,PST=IS,CALL=IDLE,GW_STAT=CXN_IS,BLK=NONE" "c7s-1:CIC=14,PST=IS,CALL=IDLE,GW_STAT=CXN_IS,BLK=NONE" "c7s-1:CIC=15,PST=IS,CALL=IDLE,GW_STAT=CXN_IS,BLK=NONE" Step 4 If the primary service state is not IS for any of the CICs, or if a CIC is blocked, check your alarms-retrieval MML session for bearer-related alarms.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Daily Tasks Media Gateway State The GW_STAT field identifies the current state of the media gateway that is associated with each CIC. Table 3-6 describes the various media gateway states. Table 3-6 Media Gateway States State Description CARRIER_FAILURE Individual CIC has failed. If this state is seen for all CICs associated with a T1 or E1, it indicates that the associated T1 or E1 has failed.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Daily Tasks Table 3-7 Note Circuit Block Types (continued) Type Description LOCMAN Blocked manually using an MML command, such as blk-cic. You can remove this block by issuing the unblk-cic or reset-cic MML commands. LOCUNK Locally blocked for unknown reasons. This block indicates that a software problem possibly blocked the CIC but the software did not track the cause of the block.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Daily Tasks "Platform State:ACTIVE" "0 critical, 0 major, 0 minor active alarms" "Machine Congestion Level = MCL 0 (No Congestion), Reason: not applicable" "Current in progress calls = 0, half calls = 0, full calls = 0, call attempts= 0 cps" "CPU 0 Utilization = 0 % CPU 1 Utilization = 0 %" "Memory (KB): 5131609 Free virtual, 5872025 Total virtual, 2097152 Total real, 0 Total Dial Plan" "Interval (minutes) 15 60 1440" "CALL: SuccCall TOT 0 0 0" "CALL
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Daily Tasks root 317 1 0 10:29:13 ? 0:00 /usr/sbin/rpc.bootparamd root 169 1 0 10:29:02 ? 0:00 /usr/sbin/syslogd root 173 1 0 10:29:02 ? 0:00 /sbin/sh /etc/rc2.d/S74xntpd start root 2867 141 0 10:05:23 ? 0:00 in.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Daily Tasks Verifying the Number of Users You should check the number of users on the Cisco PGW 2200 Softswitch on a daily basis. To check, log into the active Cisco PGW 2200 Softswitch and enter the following UNIX command: who The system returns a response like the following: mgcusr pts/0 mgcusr2 pts/1 May 29 11:07 May 30 10:05 (mgcusr-u5.somecompany.com) (mgcusr2-u6.somecompany.com) Only known login IDs should be listed in the response.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Daily Tasks Step 1 Log in to the active Cisco PGW 2200 Softswitch.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Periodic Maintenance Procedures Step 1 Log in to a Cisco ITP-L, and enter the following Cisco IOS command to check the amount of available memory: show mem The system returns a response like the following: Processor I/O Head 80CF71E0 1D00000 Total(b) 16813600 19922944 Used(b) 7885028 6975904 Free(b) 8928572 12947040 Lowest(b) Largest(b) 8900652 8891892 12938256 12937500 Ensure that the memory used is less than 90 percent of the total availabl
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Periodic Maintenance Procedures Automatic Disk Space Monitoring The Cisco PGW 2200 Softswitch software includes a script that is called disk monitor (diskmonitor.sh). Disk monitor periodically checks the amount of disk space that is used within the configurable set of disk partitions. Disk monitor ensures that there is sufficient disk space available in each disk partition for the system to continue to operate at peak performance.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Periodic Maintenance Procedures • diskmonitor.SoftLimit—Specifies the operation that the system performs when the system reaches the threshold number of days that is specified for the diskmonitor.Limit parameter. If this parameter is set to true, the disk monitor decrements the value in the diskmonitor.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Periodic Maintenance Procedures If any disk partition exceeds the configured usage threshold, the Cisco PGW 2200 Softswitch generates a DISK alarm (a major alarm). The DISK alarm warns of a disk partition overrun and of insufficient disk space. See the “DISK” section on page 6-38 for information about the corrective actions that are required to resolve a DISK alarm.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Periodic Maintenance Procedures Note Caution Disk monitor does not trim the files in these file systems. • diskmonitor.Threshold—Sets the percentage of disk usage. When disk usage exceeds the threshold, the system raises alarms and begins to trim files. The default value is 80. • diskmonitor.CdrRmFinished—Specifies how many days to keep completed CDR files. The default value is 0.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Periodic Maintenance Procedures Automatic System Log Rotation As the system operates, the Cisco PGW 2200 Softswitch software creates the system logs that are stored in a file in the /opt/CiscoMGC/var/log directory. The XECfgParm.dat file parameter sets the name of the system log file, logFileNamePrefix (the default value is platform).
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Periodic Maintenance Procedures Backing Up System Software Schedule regular system software backups on both the active and standby Cisco PGW 2200 Softswitches to protect critical system data such as configuration files, which are irreplaceable if lost. If a catastrophic failure occurs, it is easier to restore system information from backup data than to recreate it.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Periodic Maintenance Procedures The following section describes backup procedures: • Backup Procedures for Cisco PGW 2200 Softswitch Software, page 3-30 Backup Procedures for Cisco PGW 2200 Softswitch Software This backup method uses a script to back up the configuration data for the Cisco PGW 2200 Softswitch software, selected UNIX administrative files, and the Main Memory Database (MMDB). This script only performs complete backups.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Periodic Maintenance Procedures Note • retries—Number of times to check for an active provisioning session on the Cisco PGW 2200 Softswitch, before aborting the backup operation. The default value is 0, and the maximum value is 100. Note • If the path you enter is for a tape device, you must enter a new tape into the device for each backup. The backup data on a used tape is overwritten by this operation.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Periodic Maintenance Procedures Step 1 Enter the following UNIX command on the Cisco PGW 2200 Softswitch: mgcbackup -s The system returns a response like the following: Backup Schedule Menu -------------------1. 2. 3. 4. 5. Add a scheduled backup Delete a scheduled backup Delete all scheduled backups List scheduled backups Exit Selection: Note Step 2 To exit the script at anytime, press Ctrl-C.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Periodic Maintenance Procedures After you enter your directory path, the system returns a response like the following: Enter the number of retries (default=0): Step 5 Enter the number of times to check for an active provisioning session on the Cisco PGW 2200 Softswitch before aborting the backup operation. Note A backup operation cannot start while a provisioning session is active on the Cisco PGW 2200 Softswitch.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Periodic Maintenance Procedures Note Schedule your automatic backup operation for a time when your system is likely to have a minimum amount of call volume to minimize the effect of the backup on call processing.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Periodic Maintenance Procedures Step 2 Enter 2 to remove an automatic backup operation from the schedule. The system returns a response like the following: Delete a Scheduled Backup ------------------------NameRetriesTimeoutDayTimeDirectory Back15 60 everyday12:00/var/cisco Mybackup030 weekdays04:00/var/cisco Enter the name of the backup to be deleted: Step 3 Enter the name of the automatic backup operation to remove from the schedule.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Periodic Maintenance Procedures Step 2 Enter 3 to remove all automatic backup operations from the schedule.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Periodic Maintenance Procedures Step 2 Enter 4 to list the scheduled automatic backup operations. The system returns a response like the following: Scheduled Backups ----------------NameRetriesTimeoutDayTimeDirectory Back15 60 everyday12:00/var/cisco Mybackup030 weekdays04:00/var/cisco Press enter to continue: Step 3 Press enter to return to the backup schedule menu. You can either exit the utility or schedule another backup activity.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Note To install the Cisco PGW 2200 Softswitch software on a new machine, you must contact Cisco TAC for another license file. Processing a Core Dump File If a system crash occurs on the Cisco PGW 2200 Softswitch, the system might generate core dump files, which are stored in the $BASEDIR/var directory. You can review the core dump files as part of the diagnosis process, to determine what caused the system to crash.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Managing MML Sessions The following sections describe the operations that you can use to manage an MML session: • Displaying Previously Entered MML Commands, page 3-39 • Displaying Information About MML Commands, page 3-40 • Re-entering Previously Entered MML Commands, page 3-41 • Retrieving Active MML Sessions, page 3-42 • Ending an MML Session, page 3-42 Displaying Previously Entered MML Commands Use the h MML command t
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations /* command 5 */ "RTRV-SOFTW:ALL" /* command 4 */ "RTRV-TC:ALL" /* command 3 */ "STP-AUD" /* command 2 */ Displaying Information About MML Commands Use the help MML command to display information on all MML commands or detailed information on individual commands. To display information on a specific MML command, log in to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the help: command_name command.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations There are multiple targets/components for this command. To get target/component specific help select from one of the following targets/components.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations For example, to re-enter the 10th-most-recently entered MML command, enter the following command: r::10 The system returns a response appropriate to the previously entered command. Note You can also use the up arrow key to re-execute a previously entered MML command.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Signaling channel name The first field lists the MML name of the signaling channel. Parent Name The second field lists the MML name of the parent of the signaling channel or linkset. Link ID The LID field lists the associated link identification number. Subsystem Number The SSN field lists the associated subsystem number.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations • ACKD—SS7 Acknowledgement delay • BSNR—SS7 backward sequence number received (BSNR) • CIS—Commanded in service • CONF—Configuration failure • COOS—Commanded out of service • ENGR—Call engine reset • ISPEND—In service, pending • LCNG—Congestion, local • LINE—Line failure • LINH—SS7 local inhibit • LINK—Link failure • LINS—Linkset failure • NA—Cause not available • OOSPEND—Out of service, pending • PRHB
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations • Retrieving the State of SS7 Signaling Services, page 3-48 • Retrieving the State of SS7 Routes, page 3-49 • Retrieving the State of All Local Subsystem Numbers, page 3-49 • Retrieving the Service State for Associations, page 3-50 • Clearing TCAP Transactions, page 3-51 • Enabling Group Service Reset Messages, page 3-51 Retrieving Signaling Service States Retrieving state information about your signaling services is a
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations To retrieve service state for all of the SS7 links, log in to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the rtrv-c7lnk: all command: The system returns a message like the following: M Media Gateway Controller RTRV "c7link1:ls01,LID=0:IS" "c7link2:ls01,LID=1:IS" "c7link3:ls02,LID=0:IS" "c7link4:ls02,LID=1:IS" 2000-03-26 19:23:23 /* /* /* /* Link Link Link Link 1 2 1 2 in in in in Linkset Linkset Li
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations The system returns a message like the following: M Media Gateway Controller 2000-03-26 20:26:18 RTRV "iprte1:IS" To retrieve attributes for all of the IP routes, log in to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the rtrv-iproute:all command: The system returns a message like the following: M Media Gateway Controller 2000-03-26 19:23:23 RTRV "iprte1:IS "iprte2:IS The valid service states for an IP r
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations When the D-channel is associated with an FAS signaling path, the system returns a message like the following: M Media Gateway Controller 2000-03-26 20:26:18 RTRV "dchan-1:fas1,LID=0:IS" ; In this response, fas1 is the signaling path, or a logical grouping of D-channels (equivalent to a linkset). The LID is the line identifier, or the logical line ID of the D-channel within the signaling path (equivalent to the SLC in SS7).
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations The system returns a response like the following: MGC-01 - Media Gateway Controller 2001-06-12 16:04:59 M RTRV "ss7sigsrv1:DPC=244.001.045,DNW=2:OPC=244.001.004:IS" "ss7sigsrv2:DPC=244.018.030,DNW=2:OPC=244.001.004:IS" "ss7sigsrv3:DPC=244.018.031,DNW=2:OPC=244.001.004:IS" "ss7sigsrv4:DPC=244.018.032,DNW=2:OPC=244.001.004:IS" "ss7sigsrv5:DPC=244.018.033,DNW=2:OPC=244.001.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations The response indicates the name of the associated process, the SSN, and the state (either in-service or out-of-service). If any of the local SSNs are out of service, proceed to the “Setting the Service State of a Local Subsystem Number” section on page 6-107.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Association Secondary Service States The SST field shows the current secondary service state of the specified association. Table 3-12 lists the valid secondary service state values: Table 3-12 Association Secondary Service States Link State ID Link State Description CONF Configuration Association is OOS because of a configuration failure. COOS Commanded out-of-service Association has been set to OOS by the operator.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations To enable the sending of GSR messages, perform the following steps: Step 1 Start a provisioning session as described in the “Starting a Provisioning Session” section on page 3-64.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations When the Cisco PGW 2200 Softswitch software is configured for signaling, the system returns a response like the following: Media Gateway Controller - MGC-67 2000-04-05 08:08:12 M RTRV "c7s-1:CIC=1,PST=IS,CALL=IDLE,BLK=NONE" "c7s-1:CIC=2,PST=IS,CALL=IDLE,BLK=NONE" "c7s-1:CIC=3,PST=IS,CALL=IDLE,BLK=NONE" "c7s-1:CIC=4,PST=IS,CALL=IN,BLK=NONE" "c7s-1:CIC=5,PST=IS,CALL=IN,BLK=NONE" "c7s-1:CIC=6,PST=IS,CALL=IN,BLK=NONE" "c7s-1:CIC=7,PST=
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Where sig_dest is a logical signaling destination, such as an SS7 point code, FAS path, IP FAS path, or DPNSS path.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations "ss7svc2:CIC=18,PST=IS,CALL=IDLE,GW_STAT=CXN_IS,BLK=NONE" Blocking CICs You might need to block a CIC or a range of CICs on your Cisco PGW 2200 Softswitch. Blocking a single CIC sends a BLA message to the destination SSP. Blocking a range of CICs sends a CGB message to the destination SSP. The range option only can be used to block CICs within a given trunk (T1 or E1).
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations • If all circuits are in a locked state, the inferred target administrative state is locked. • If at least one circuit is in an unlocked state, the inferred target administrative state is unlocked. • If the circuits are in a mixture of the locked and shutdown states, the inferred target administrative state is shut down.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Where trkgrp is the MML name of the trunk group. Note This command can only be used for time-division multiplexing (TDM) trunk groups. Allow the corresponding MML name for component type “0020”.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations – For in-band TDM signaling up to the media gateway and then converted to NI2 and sent to the Cisco PGW 2200 Softswitch over IP (that is, FE box<-sig/tdm->media gateway<-NI2/IP-> Cisco PGW 2200 Softswitch). – Signaling service or routeset that is associated with a DPC. – EISUP signaling service. • x—16-bit value that identifies an ISDN/PRI physical cable.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Retrieving the Administrative State of CICs To retrieve the administrative state of a CIC or a range of CICs, log in to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the rtrv-admin-state:sig_srv,cic=number[,rng=range] command: Where: • sig_srv is the MML name of the signaling service.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations – MOOS—Manually taken out of service. – OOS—Out of service. – TRNS—Transient. The state is currently being changed. – UNK—Unknown. • BLK—Blocking state – NONE—There is no block on the CIC. DS0 is available for use. • TRANS—Number of active transactions.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations • null_string—An empty string (entered as “ “ in the command line). If you enter a null string in this command, the command in Step 4 displays the DNS IP addresses, size of the cache, percentage of the cache being used, and the local TTL value.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Retrieving SIP Call Information From Release 9.3(2) to Release 9.5(2) Starting in Release 9.3(2), you can use the rtrv-sip MML command to retrieve call information data, such as SIP call identification number, and the originating and terminating numbers, for any call that uses SIP for at least one end of the call. The following sections describe how to use the command to retrieve SIP call information.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations When you enter this command with the optional command to provide detailed call data, the system returns a response like the following: MGC-01 - Media Gateway Controller 2002-05-13 10:02:08.833 PST M RTRV "sip-sigpath:CID=10177b4e1aed3d8679b40d824a72e2e9@172.22.119.82," "sip-sigpath:CALL=OUT,MATE_FAMILY=SIP,FROM=2025553230,TO=4080000284" "sip-sigpath:CID=10177b4e1aed3d8679b40d824a72e2e9@172.22.119.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations When you enter this command with the optional command to provide detailed call data, the system returns a response like the following: MGC-01 - Media Gateway Controller 2002-05-13 10:02:08.833 PST M RTRV “sippath-sip-outbound:CALL=OUT,MATE_FAMILY=SIP,FROM=3330000,TO=sipp" "sippath-sip-outbound:CID=5248672-32474@10.0.120.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Note You can use new as the source configuration only when there is no existing, active set of provisioning data in the configuration library. Therefore, you cannot use new as the source configuration once a provisioning session has been saved and activated by using prov-cpy or prov-dply.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Note Caution To add new signaling links or CICs to the signaling links and CICs previously provisioned, enter the prov-cpy command. To save the new signaling links and CICs to the standby Cisco PGW 2200 Softswitch, enter the prov-sync command. The link and call state data are not synchronized.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Step 1 Start a provisioning session as described in the “Starting a Provisioning Session” section on page 3-64. Step 2 Enter the prov-ed or prov-dlt MML commands to change or delete a component. See Cisco PGW 2200 Softswitch Release 9.8 Provisioning Guide for more information on the specific structure of the command for the component type you want to reconfigure dynamically.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Table 3-13 lists the preconditions that you must establish for the component before you can perform any modification or deletion as part of dynamic reconfiguration. There are no preconditions for adding components as part of dynamic reconfiguration.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Provisioning or configuring by using any other means can cause errors during the dynamic reconfiguration process. Using these tools is required because the dynamic reconfiguration process relies on the provisioning tools to validate the data values and, more importantly, to cross check the dependencies of the objects.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations The system returns a response like the following: MGC-01 - Media Gateway Controller 2001-06-01 10:09:47 M RTRV "session=active:sigsvcprop" /* adjDestinations = 16 AlarmCarrier = 0 BOrigStartIndex = 0 BothwayWorking = 1 BTermStartIndex = 0 CctGrpCarrier = 2 CGBA2 = 0 CircHopCount = 0 CLIPEss = 0 CotInTone = 2010 CotOutTone = 2010 CotPercentage = 0 dialogRange = 0 ExtCOT = Loop ForwardCLIinIAM = 1 ForwardSegmentedNEED = 1 GLARE = 0
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Retrieving Data for Select Components You can retrieve data on selected components that are provisioned on your system. To retrieve data on selected components, log in to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the prov-rtrv:all command: Note This command returns data on all signaling components, except for signaling service and linkset properties.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations "ls1link1" va-2600-202" "ls2link1" va-2600-202" "ls1link2" va-2600-203" "ls2link2" va-2600-203" "lk-3" "stp1" "scp1" "scp2" "ss7subsys3" rte-ssn 254" "ss7subsys1" "ss7subsys2" cp1 rte-ssn 254" */ 001d0001 "ls1" C7IPLNK "link 1 of ls1 to 001d0002 "ls2" C7IPLNK "link 1 of ls2 to 001d0003 "ls1" C7IPLNK "link 2 of ls1 to 001d0004 "ls2" C7IPLNK "link 2 of ls2 to 001d0005 001e0001 001e0002 001e0003 001f0003 "ls-itu" "M
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations The system returns a response like the following: MGC-01 - Media Gateway Controller 2001-06-12 17:16:42 M RTRV "session=active:dpc" /* NAME NETADDR NETIND --------------dpc2 2.2.2 2 dpc1 1.1.1 2 */ Retrieving Data on the Current Provisioning Session You can retrieve provisioning data on the current provisioning session.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations ETS_300_356 SS7-ITU HKTA_2202 SS7-ITU ISUPV1_POLI SS7-ITU ISUPV2_32DIG SS7-ITU ISUPV2_CZECH SS7-ITU ISUPV2_FINNISH96 SS7-ITU ISUPV2_FRENCH SS7-ITU ISUPV2_GERMAN SS7-ITU ISUPV2_JAPAN SS7-Japan ISUPV2_KPNPB SS7-ITU ISUPV2_NTT SS7-Japan ISUPV2_SPANISH SS7-ITU ISUPV2_SWISS SS7-ITU ISUPV2_TELEFONICA SS7-ITU ISUPV2_VIETNAM SS7-ITU ISUPV3_UK SS7-UK ISUPV3_UK_AXE10 SS7-UK ISUPV3_UK_AXE10_BTNETCHAT SS7-UK ISUPV3_UK_BTNETCHAT SS7-UK Q721_BA
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations */ Provisioning a Dial Plan You can provision dial plans on the Cisco PGW 2200 Softswitch by using the following commands. For more information on provisioning and maintaining dial plans, see Cisco PGW 2200 Softswitch Release 9.8 Dial Plan Guide. Note • numan-add—Adds an element to a dial plan. • numan-dlt—Deletes an element from a dial plan. • numan-ed—Edits an existing element in a dial plan.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Exporting Provisioning Data You can use the prov-exp MML command to export the currently provisioned setup of the Cisco PGW 2200 Softswitch in MML-command form to a file or files. This export enables you to copy the provisioning data from one Cisco PGW 2200 Softswitch and set up another Cisco PGW 2200 Softswitch with that same provisioning data or to restore a Cisco PGW 2200 Softswitch to a baseline provisioning environment.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations • GLBL.ablack—Contains global screening data for A-number black lists. Introduced in Release 9.4(1). • GLBLbwhite—Contains global screening data for B-number white lists. Introduced in Release 9.4(1). • GLBLbblack—Contains global screening data for B-number black lists. Introduced in Release 9.4(1).
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Table 3-14 Machine Congestion Level Values Machine Congestion Level Description MCO No congestion present. MC1 Mild congestion. MC2 Moderate congestion. MC3 Severe congestion.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Modifying the MCL Call Reject Settings To modify the percentage of calls that are rejected for a particular MCL, perform the following steps: Note You can use the Cisco Voice Services Provisioning Tool (VSPT) to modify the MCL call release settings. For more information on using the Cisco VSPT, see Cisco Voice Services Provisioning Tool User Guide.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations The system returns a message like the following: MGC-01 - Media Gateway Controller 2001-02-23 14:13:40 M RTRV "session=accstuff:mclcallreject" /* MCLNAME = mcl1 CALLREJECT = 25 */ To retrieve the settings for every MCL on your system, log in to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the prov-rtrv:mclcallreject:“all” command.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Table 3-16 CANT and Skip Results Matrix CANT Skip Result Yes Yes CANT No Yes Skip No No None Yes No CANT CANT and skip percentages can be different depending on the type of traffic. Note • Direct routed—This trunk group is the first choice in a list of routes in a priority sequence coming from the adjacent signaling point.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations • Adding an ACC Response Category on a System Configured for Call Control, page 3-83 • Modifying an ACC Response Category on a System Configured for Signaling, page 3-85 • Modifying an ACC Response Category on a System Configured for Call Control, page 3-85 • Deleting an ACC Response Category on a System Configured for Signaling, page 3-87 • Deleting an ACC Response Category on a System Configured for Call Control, page 3
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Where: • comp_name—MML name for the SS7 signaling path to be associated with an ACCRC. Note • If you do not know the MML name of the SS7 signaling path, use the prov-rtrv:ss7path:”all” command to find the name. cat_name—MML name for the ACCRC.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations – acl2drskip—Specifies the percentage of calls that is defined in value. Calls are rerouted to an alternate trunk group when an adjacent signaling point sends an ACL indication of 2. – acl2arcant—Specifies the percentage of calls that is defined in value. Calls are released when an adjacent signaling point sends an ACL indication of 2 and this trunk group is configured as an alternate route from that signaling point.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Modifying an ACC Response Category on a System Configured for Signaling To modify an ACCRC on a system that is configured for signaling, perform the following steps: Note You can use the Cisco VSPT to modify an ACCRC. For more information on using the Cisco VSPT, see Cisco Voice Services Provisioning Tool Users Guide.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations • field_name—ACCRC field that specifies a percentage of calls that is released when an adjacent signaling point sends a congestion indication of a particular ACL level. You can modify the following fields: – acl1drcant—Specifies the percentage of calls that is defined in value.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Deleting an ACC Response Category on a System Configured for Signaling To delete an ACCRC on your system when it is configured for signaling, perform the following steps: Note You can also use the Cisco VSPT to delete an ACCRC. For more information on using the Cisco VSPT, see Cisco Voice Services Provisioning Tool Users Guide.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations For example, to delete a trunk group named access1, enter the prov-dlt:trnkgrp:name=“access1” command: Step 3 Enter the following command to delete an ACCRC: prov-dlt:accrespcat:name="cat_name" Where: cat_name—Name of the ACCRC to delete.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations The system responds with a message like the following.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Step 2 Enter the following command to modify the trunk group that is associated with an ACCRC: prov-ed:trnkgrpprop:name="comp_name",ACCRespCatName=”cat_name” Where: • comp_name—MML name for the trunk group to be associated with an ACCRC. Note • If you do not know the MML name of the trunk group, use the prov-rtrv:trnkgrp:”all” command to find the name. cat_name—MML name for the ACCRC.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations • comp_name—MML name for the SS7 signaling path or trunk group for which you modify the duration of the ACL timer. • num—Duration of the ACL timer, in seconds. The default is 5.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations • Retrieving MCL Threshold Values, page 3-94 Mapping Machine Congestion Level to the ANSI or ITU Congestion Standard When the Cisco PGW 2200 Softswitch is overloaded, it sends an ACL value to adjacent signaling points in an ISUP release message that is based on the MCL.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Table 3-18 MCL Mapping Values MaxACL Value Congestion Standard MCL Value 0 N/A MC0 through ACL is disabled MC3 2 ITU MC0 MC1 MC2 MC3 ACL is not present 1 2 2 3 ANSI MC0 MC1 MC2 MC3 ACL is not present 1 2 3 ACL Value in Release Message For example, to map the MCL on a trunk group named trunk1, which is next to a signaling point that uses the ITU congestion standard, enter the prov-ed:trnkgrpprop:name=“trunk1”,MaxACL
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations • field_name—MCL threshold field that specifies the onset and abatement values for the selected threshold type. Configure the following fields: – mcl1onset—Specifies the threshold, as defined in value, at which the Cisco PGW 2200 Softswitch enters MCL1. – mcl1abate—Specifies the threshold, as defined in value, at which the Cisco PGW 2200 Softswitch abates MCL1.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations The system responds lists the values for each of the fields that are associated with the MCL threshold type.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Performing a Manual Switchover In a continuous service configuration, you can swap the roles of the active Cisco PGW 2200 Softswitch and the standby Cisco PGW 2200 Softswitch by issuing the appropriate MML command from the management interface of the active Cisco PGW 2200 Softswitch.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Caution The next step forces a manual switchover to the standby Cisco PGW 2200 Softswitch. Ensure that the standby Cisco PGW 2200 Softswitch is fully operational and that debugging is turned off before taking the active Cisco PGW 2200 Softswitch OOS, or there might be a total interruption of service. A switchover can also cause call processing to fail if debugging is turned on.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Note If your system is a simplex configuration (a single Cisco PGW 2200 Softswitch), or is functioning in standalone mode (the standby Cisco PGW 2200 Softswitch is in the OOS service state), the system cannot perform a switchover. In these instances, the active Cisco PGW 2200 Softswitch remains in the active service state when a critical failure occurs. Switchovers can occur automatically when a critical alarm is generated.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations A critical event is typically a critical process dying or the failure of a subsystem or component that can critically affect call processing. A forced switchover occurs automatically when the conditions governing it are met; it is system-initiated and not user-initiated. When a critical event occurs, the alarm manager sends a specific message to the foverd process, indicating the occurrence of the critical event.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations that a bearer circuit is in use and discovers that the bearer device does not show that circuit is in use, the Cisco PGW 2200 Softswitch does not attempt to rebuild the call, but releases all associated resources. Although the Cisco PGW 2200 Softswitch is the controlling authority, when it discovers a discrepancy during a circuit audit, the Cisco PGW 2200 Softswitch releases all allocated resources and drops all calls.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations The system returns a response like the following: application application application system CSCOgp003 CSCOgp009 CSCOgs003 SUNWswmt Cisco Cisco Cisco Patch Media Gateway Controller Software Patch Package Media Gateway Controller Software Patch Package Media Gateway Controller Software Patch Package Utilities Look for the Cisco PGW 2200 Softswitch patch with the largest number to determine the current patch level.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Step 6 Review the utility results either on-screen or by opening the file. If the results indicate that there are no problems with the installation, the procedure is complete. Otherwise, proceed to Step 7. Caution The check inventory utility uses a 32-bit cyclic redundancy check (CRC) to verify your system software. A 32-bit CRC can have a value anywhere from 1 to over 4 billion.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations The system returns a response like the following: Media Gateway Controller M RTRV "ENG-01:INFO" Note - MGC-01 2000-01-16 09:38:03 The process manager (PM-01) is not included in the “all” parameter because this process requires special treatment. To retrieve the logging level of PM-01, you must specify it individually with the command, as shown in the preceding example.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations "Memory (KB): 5131609 Free virtual, 5872025 Total virtual, 2097152 Total real, 0 Total Dial Plan" "Interval (minutes) 15 60 1440" "CALL: SuccCall TOT 0 0 0" "CALL: FailCall TOT 0 0 0" "CALL: SIPLicRej TOT 0 0 0" "CALL: H323LicRej TOT 0 0 0" "CALL: TDMLicRej TOT 0 0 0" "CALL: TimesTenLicRej TOT 0 0 0" ; Note In a single instance, the number of in-progress calls does not reflect the actual number of active calls.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations If the response to the command indicates that the system is using 90 percent or more of its disk capacity, you must delete files from your disk drive, as described in the “Deleting Unnecessary Files to Increase Available Disk Space” section on page 6-169.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Clearing Measurements The measurement category and component identification number uniquely defines each measurement (or counter). Retrieve individual measurements using the following MML command from the active Cisco PGW 2200 Softswitch: clr-ctr:comp :"meas_cat" Where: • comp—MML name of the component. For a complete list of components, see the Cisco PGW 2200 Softswitch Release 9 MML Command Reference.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations To retrieve a list of system measurements for the links that make up a linkset, log in to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the rtrv-lnk-ctr:linkset command: Where: linkset is the MML name of the SS7 linkset.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations "ls1link2:CAT=\"SC: XMIT FRM TOT\",INT=3600,VAL=0" "ls1link2:CAT=\"SC: XMIT FRM TOT\",INT=86400,VAL=0" "ls1link2:CAT=\"SC: RCV BAD TOT\",INT=900,VAL=0" "ls1link2:CAT=\"SC: RCV BAD TOT\",INT=3600,VAL=0" "ls1link2:CAT=\"SC: RCV BAD TOT\",INT=86400,VAL=0" "ls2link1:CAT=\"SC: RCV FRM TOT\",INT=900,VAL=0" "ls2link1:CAT=\"SC: RCV FRM TOT\",INT=3600,VAL=0" "ls2link1:CAT=\"SC: RCV FRM TOT\",INT=86400,VAL=0" "ls2link1:CAT=\"SC: XMIT FRM TO
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dp
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "d
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations "dpc2:CAT=\"ISUP: XMIT INF TOT\",INT=300,VAL=0" "dpc2:CAT=\"ISUP: XMIT INF TOT\",INT=1800,VAL=0" "dpc2:CAT=\"ISUP: XMIT CQM TOT\",INT=300,VAL=0" "dpc2:CAT=\"ISUP: XMIT CQM TOT\",INT=1800,VAL=0" "dpc2:CAT=\"ISUP: RCV INF TOT\",INT=300,VAL=0" "dpc2:CAT=\"ISUP: RCV INF TOT\",INT=1800,VAL=0" "dpc2:CAT=\"ISUP: RCV BLO TOT\",INT=300,VAL=0" "dpc2:CAT=\"ISUP: RCV BLO TOT\",INT=1800,VAL=0" "dpc2:CAT=\"SP: cInit in\",INT=900,VAL=0" "dpc2:CAT
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "d
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dpc2:CAT=\"ISUP: "dp
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations "dpc2:CAT=\"ISUP: RCV INF TOT\",INT=1800,VAL=0" "dpc2:CAT=\"ISUP: RCV BLO TOT\",INT=300,VAL=0" "dpc2:CAT=\"ISUP: RCV BLO TOT\",INT=1800,VAL=0" "dpc2:CAT=\"SP: cInit in\",INT=900,VAL=0" "dpc2:CAT=\"SP: cInit in\",INT=3600,VAL=0" "dpc2:CAT=\"SP: cInit in\",INT=86400,VAL=17" "dpc2:CAT=\"ISUP: XMIT CPG TOT\",INT=300,VAL=0" "dpc2:CAT=\"ISUP: XMIT CPG TOT\",INT=1800,VAL=0" "dpc2:CAT=\"SP: PDU out\",INT=900,VAL=0" "dpc2:CAT=\"SP: PDU out
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dp
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations "dpc1:CAT=\"ISUP: XMIT FOT TOT\",INT=1800,VAL=0" "dpc1:CAT=\"ISUP: XMIT PAM TOT\",INT=300,VAL=0" "dpc1:CAT=\"ISUP: XMIT PAM TOT\",INT=1800,VAL=0" "dpc1:CAT=\"ISUP: RCV CGB TOT\",INT=300,VAL=0" "dpc1:CAT=\"ISUP: RCV CGB TOT\",INT=1800,VAL=0" "dpc1:CAT=\"ISUP: RCV RLC TOT\",INT=300,VAL=0" "dpc1:CAT=\"ISUP: RCV RLC TOT\",INT=1800,VAL=0" "dpc1:CAT=\"ISUP: RCV REL TOT\",INT=300,VAL=0" "dpc1:CAT=\"ISUP: RCV REL TOT\",INT=1800,VAL=0" "dp
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: "dpc1:CAT=\"ISUP: RCV CPG TOT\",INT=300,VAL=0" RCV CPG TOT\",INT=1800,VAL=0" XMIT INR TOT\",INT=300,VAL=0" XMIT INR TOT\",INT=1800,VAL=0" RCV CRA TOT\",INT=300,VAL=0" RCV CRA TOT\",INT=1800,VAL=0" Retrieving Measurement Thresholds Each measurement has a profile that contains information concerning the time intervals, or thresholds, for repor
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations set-thres::cat="SIP: RETX MSG TOT",interval=1800, thres=125 Managing Call Detail Records CDRs contain call billing records for your system. The Cisco PGW 2200 Softswitch stores the CDRs in log files. For more information on log files, see Appendix A, “Configuring Cisco PGW 2200 Softswitch Log Files.” For more information on CDRs, see Cisco PGW 2200 Softswitch Release 9 Billing Interface Guide.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations • filename—Name for the file that is output when this command executes, including the file path. • -outformat 2—Specifies that the output file should be in a readable format. • -follow—Used when you are converting the active CDR file. Processing of the active CDR file continues as CDR logs are created in the active file. Processing stops when you enter Control-C.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations • Using the File Options Viewer, page 3-140 • Using the MGC Backup Viewer, page 3-141 • Using the MGC Restore Viewer, page 3-141 The Cisco MGC toolbar (Figure 3-1) is a GUI application that is used to launch the various viewers in the toolkit. Each application runs independently of the others. The toolbar includes a button for launching each application in the toolkit.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Using the Alarm Viewer The alarm viewer enables you to view and search records that reside in the current and archived alarm record logs. The formats of the various alarm records are specified in the Cisco PGW 2200 Softswitch Release 9 Messages Reference. The alarm viewer includes a help file, which contains information about the viewer. To access this information, click the Help menu, then select ReadMe. The help text appears.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Step 3 Search for alarms that occurred between dates and times, by specifying month, day, year, hour, and minute settings. Choose a starting date and time from the Start Date/Time drop-down lists. Then choose a stop date and time from the Stop Date/Time drop-down lists.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Step 9 To save the displayed data, click Save. The contents of the field are saved to a file with the following directory path: /opt/CiscoMGC/etc/cust_specific/toolkit/alarmRec.log If you perform another search and save the content again, the contents of the field are added to the alarmRec.log file, after the previously saved data. To avoid adding the new search data to the previous data, change the name of the alarmRec.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations The CDR dumper (see Figure 1-2) provides logging capabilities on the Cisco PGW 2200 Softswitch for all CDRs. Also, the CDR dumper supports external user application programming interfaces (APIs). The APIs enable users to get a real-time feed of CDRs and call detail blocks (CDBs) from the Cisco PGW 2200 Softswitch. You can route the CDR and CDB data to a third-party mediation application for use in billing.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Figure 3-4 Config Tab Window Searching the CDR Files To search the various CDR files by component and category, complete the following steps: Step 1 To open the CDR viewer, click CDR Viewer on the Cisco MGC toolbar. A popup window displays. The window warns you that running this tool can affect system performance and asks you if you want to launch the tool. Click Yes to continue.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Figure 3-5 Query Tab Window The current date and time are the default values for both the start and stop values for the time period; however, using these default values results in a null search (no records). If you select the Use Current Time as Stop Time check box, you disable the Stop Date/Time drop-down lists and enable a search until the current date and time.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Step 5 Enter a search qualifier and a related string for each field value that you select. Choose a search qualifier for the search string from the drop-down list box that is located to the right of the field value you select. The following list presents the search qualifiers: • Equal to—The selected field in the CDB is equal to the value defined in the search string.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Figure 3-6 • Note Config-Lib Viewer Copy Library Version to Production—Restores your Cisco PGW 2200 Softswitch to the settings in an old configuration version. When you select this function, the Cisco PGW 2200 Softswitch software must not be running, or an error message is displayed.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Figure 3-7 Step 2 Log Viewer You can search for alarms that occurred between dates and times, by specifying month, day, year, hour, and minute settings. To conduct a search, choose a starting date and time from the Start Date/Time drop-down list boxes. Then choose a stop date and time from the Stop Date/Time drop-down lists.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Step 5 • TIOS • CP • PROT • MGMT • MML To search for logs of certain severities, select a severity or severities by clicking one or more entries in the Severity list box. To select multiple entries, hold down either the Ctrl or Shift key while clicking. The severity choices are cumulative—each level that you select also displays all levels below it.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Note Stopping the query can take several seconds. Your results might include several pages of information. You can use several buttons to navigate through the results. To go to the end of the results, click Bottom. To go to the next page of results, click More. To go to the beginning of the results, click Top. Step 9 To save the displayed data, choose the File > Save.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Figure 3-8 c. Measurement Viewer Window To refine your search further by specifying a counter interval, choose an interval from the Counter Interval drop-down list. The following intervals are valid for this field: – NO_SPECIFIC (default value) – 5_Minute – 15_Minute – 30_Minute – 60_Minute – 24_Hours d. To refine your search further by specifying a system component type, proceed to Step 3.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations b. To refine your search further by specifying a particular system component, choose a system component name from the drop-down list box to the right of the Component Type list box. Note c. The default value for this field instructs the viewer to search for all system components of the chosen component type. To refine your search further by specifying a measurement category type, proceed to Step 4.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Using the Trace Viewer You can use the trace viewer as part of performing a call trace. Click Trace Viewer in the Cisco MGC toolbar to open the Traces Files window. The Trace Files window lists the call trace files that you can choose (Figure 3-9). When you select a file, click View to open the Trace Viewer window (Figure 3-10). In the Trace Viewer window, you can select various call trace activities.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Note The translation verification viewer does not simulate the screening database and cause analysis dial plan functions. You can exit the translation verification viewer by choosing File > Exit. Verifying a Dial Plan Translation Complete the following steps to verify a dial plan translation: Step 1 To open the translation verification viewer, click Translation Verification on the Cisco MGC toolbar. A popup window displays.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Figure 3-11 DialPlan Translation Tab Window • NOA_CARRIER_NO_NUM • NOA_950_CALL • NOA_TEST_LINE_CODE • NOA_INT_INBOUND • NOA_NAT_OR_INTL_CARRIER_ACC_CODE_INC • NOA_CELL_GLOBAL_ID_GSM • NOA_CELL_GLOBAL_ID_NMT_900 • NOA_CELL_GLOBAL_ID_NMT_450 • NOA_CELL_GLOBAL_ID_AUTONET • NOA_PORTED_NUMBER • NOA_PISN_SPECIFIC_NUMBER • NOA_UK_SPECIFIC_ADDRESS • NOA_SPARE • NOA_SUBSCRIBER_OPERATOR_REQUESTED • NOA_NATION
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Step 5 • NOA_950_PUBLIC_HOTEL_LINE • NOA_TEST_CALL • NOA_MCI_VNET • NOA_INTERNATIONAL_OPERATOR_TO_OPERATOR_OUTSIDE_WZI • NOA_INTERNATIONAL_OPERATOR_TO_OPERATOR_INSIDE_WZI • NOA_DIRECT_TERMINATION_OVERFLOW • NOA_ISN_EXTENDED_INTERNATIONAL_TERMINATION • NOA_TRANSFER_ISN_TO_ISN • NOA_CREDIT_CARD • RESERVED Specify the Numbering Plan Indicator (NPI) setting for the called party by choosing a value from the called p
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations • diagnostic—Returns limited information about all of the stages of number and route analysis and messages and warnings about data files being read and whether default values are being used. This trace type is suited for determining the results that the viewer used to produce the outgoing numbers and trunk group.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations (13) B Number:'7075511234' ( 1)ending Call Information Reception... ( 1)entering Profile Analysis (NOA). (13) Tracing call number:'7075511234' (Called party number) ( 7) Trace for customer:'jst1' ( 5) TreeBase:'10' ( 2) tracing Dial plan, entering NOA table with... ( 1) 1 parameter(s): ( 4) NOA table index = 4. ( 2) reading NOA table...
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Figure 3-12 Configuration Tab Window Using the File Options Viewer The file options viewer (Figure 3-13) enables you to manage (rename, delete) the files within the $BASEDIR/etc/cust_specific directory. This directory contains all files that the various toolkit applications created. The MML export feature creates subdirectories, which contain configuration information in the form of MML commands.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Figure 3-13 File Options Viewer Window Using the MGC Backup Viewer The MGC backup viewer enables you to back up the software configuration of the Cisco PGW 2200 Softswitch. For more information on using the MGC backup utility, see the “Backup Procedures for Cisco PGW 2200 Softswitch Software” section on page 3-30. Figure 3-14 illustrates the main window for the MGC backup viewer.
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations Regular Operations Figure 3-15 MGC Restore Viewer Window Cisco PGW 2200 Softswitch Release 9.
CH A P T E R 4 Maintenance and Troubleshooting Overview Revised: March 7, 2011, OL-0800-14 This chapter contains an overview of maintenance and troubleshooting concepts that you can apply to maintaining the elements of the Cisco PGW 2200 Softswitch platform. It includes overall maintenance and system troubleshooting strategies, and reviews available troubleshooting tools. Although this chapter describes maintenance and troubleshooting separately, these activities are associated.
Chapter 4 Maintenance and Troubleshooting Overview Troubleshooting Strategy Overview • Replacing hardware components—Maintenance chapter for each element of the Cisco PGW 2200 Softswitch platform includes sections that describe how to replace the field-replaceable components of that device. You swap out components of a device to replace defective components and to upgrade hardware.
Chapter 4 Maintenance and Troubleshooting Overview Troubleshooting Strategy Overview Figure 4-1 General Problem-Solving Model Define the problem. Gather the facts. Consider possibilities based on the facts. Create an action plan. Implement the action plan. Observe the results. (If symptoms stop…) (If symptoms persist…) Problem resolved; terminate the process. Step 2 203195 Repeat the process. Gather the necessary facts to help isolate the symptoms and their possible causes.
Chapter 4 Maintenance and Troubleshooting Overview Troubleshooting Strategy Overview Note If you exhaust all of the common causes and actions (those causes that are outlined in this chapter and those causes that you have identified for your environment), your last recourse is to contact the Cisco Technical Assistance Center (TAC). See the “Obtaining Documentation and Submitting a Service Request” section on page xviii for more information about contacting the Cisco TAC.
Chapter 4 Maintenance and Troubleshooting Overview Troubleshooting Strategy Overview You can read system logs by using the viewers within the Cisco MGC viewer toolkit. For more information on the viewers that comprise the Cisco MGC toolkit, see the “Using the Cisco MGC Viewer Toolkit” section on page 3-119. See the Appendix A, “Configuring Cisco PGW 2200 Softswitch Log Files,” for more information on system log files.
Chapter 4 Maintenance and Troubleshooting Overview Troubleshooting Strategy Overview Cisco WAN Manager Cisco WAN Manager is part of the Cisco Service Management System. Cisco WAN Manager includes tools that operators of service provider networks and large enterprise networks can use to provision and manage their networks. The Cisco WAN Manager provides fault-management features and can be used along with other applications such as CiscoView, the Event Browser, and Configuration Save and Restore.
Chapter 4 Maintenance and Troubleshooting Overview Troubleshooting Strategy Overview Cisco SS7 Interface Diagnostic Commands Cisco SS7 interfaces provide the following integrated Cisco IOS command types to assist you in monitoring and troubleshooting systems: • show • debug • ping • trace Show Commands The show commands are powerful monitoring and troubleshooting tools.
Chapter 4 Maintenance and Troubleshooting Overview Troubleshooting Strategy Overview Using Debug Commands The debug commands in privileged EXEC mode can provide information about the traffic being seen (or not seen) on an interface. This information includes error messages that network nodes generate, protocol-specific diagnostic packets, and other useful troubleshooting data. Caution Be careful when using debug commands.
Chapter 4 Maintenance and Troubleshooting Overview Troubleshooting Strategy Overview For detailed information on using the ping command and extended ping commands, see the Cisco IOS Configuration Fundamentals Command Reference. Using the Trace Command The trace user command in EXEC mode discovers the routes that packets follow when traveling to their destinations.
Chapter 4 Maintenance and Troubleshooting Overview Troubleshooting Strategy Overview A cable tester might also be able to perform any of the following functions: • Test and report on cable conditions, including near-end crosstalk, attenuation, and noise • Perform TDR, traffic monitoring, and wire map functions • Display Media Access Control (MAC) layer information about network traffic, provide statistics such as network utilization and packet error rates, and perform limited protocol testing (for e
Chapter 4 Maintenance and Troubleshooting Overview Troubleshooting Strategy Overview TDRs and OTDRs TDRs are at the top end of the cable testing spectrum. These devices can quickly locate open and short circuits, crimps, kinks, sharp bends, impedance mismatches, and other defects in metallic cables. A TDR works by “bouncing” a signal off the end of the cable. Opens, shorts, and other problems reflect the signal back at different amplitudes, depending on the problem.
Chapter 4 Maintenance and Troubleshooting Overview Troubleshooting Strategy Overview Cisco PGW 2200 Softswitch Release 9.
CH A P T E R 5 Maintaining the Cisco PGW 2200 Softswitch Revised: March 7, 2011, OL-0800-14 This chapter contains the recommended hardware maintenance procedures for the Cisco PGW 2200 Softswitch. The Cisco PGW 2200 Softswitch performs call-processing, trunk resource management, alarm management, and routing. The Cisco PGW 2200 Softswitch also provides various Cisco telephony solutions with Advanced Intelligent Network (AIN) capabilities.
Chapter 5 Maintaining the Cisco PGW 2200 Softswitch Maintaining Technical Support Staff LEDs See Sun documentation for the specific Cisco PGW 2200 Softswitch hardware platform you are using. Sun Netra T 1120/1400 and Sun Netra T 1125/1405 The Sun Netra T 1120/1400 and Sun Netra T 1125/1405 have the following LEDs: • POWER—Green LED is illuminated at all times when the system is on.
Chapter 5 Maintaining the Cisco PGW 2200 Softswitch Maintaining Components The technical profile portion of the Sun audit analyzes the technical ability of service personnel and determines if the support staff is sufficient for quality customer support. Staff Software Troubleshooting Tools The support engineers must have a current version of Sunsolve to assist in troubleshooting and resolving problems.
Chapter 5 Maintaining the Cisco PGW 2200 Softswitch Maintaining Components Cisco PGW 2200 Softswitch Release 9.
CH A P T E R 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Revised: March 7, 2011, OL-0800-14 This chapter describes troubleshooting methods for the Cisco PGW 2200 Softswitch platform.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Overview The following sections present solutions to various equipment failure scenarios: • Cisco ITP-L Failure • Cisco PGW 2200 Softswitch Failure • Operating System Failure Cisco ITP-L Failure Each Cisco IP Transfer Point LinkExtender (ITP-L) has a Reliable User Datagram Protocol (RUDP)/User Datagram Protocol (UDP)/IP connection to each Cisco PGW 2200 Softswitch for the transfer of Message Transfer Part (MTP) Level 3
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Troubleshooting Using Cisco PGW 2200 Softswitch Alarms The Cisco PGW 2200 Softswitch generates alarms to indicate problems with processes, routes, linksets, signaling links, and bearer channels. The Cisco PGW 2200 Softswitch Release 9 Messages Reference lists all of the Cisco PGW 2200 Softswitch alarms and logs, and provides descriptions, possible causes, and suggested actions.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Where: • comp—MML name of the component. For a complete list of components, see the Cisco PGW 2200 Softswitch Release 9.8 Provisioning Guide. You can retrieve a list of provisioned components by entering the prov-rtrv:all MML command. • alarmCategory—MML name of the associated alarm category. The name you enter must match exactly the name of the alarm as it is displayed.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 4 Contact the Cisco TAC to analyze the problem further and to determine a solution. For more information about contacting the Cisco TAC, see the “Obtaining Documentation and Submitting a Service Request” section on page xviii. All C7 IP Links Fail This alarm occurs when communication is lost to all Cisco ITP-Ls of every configured protocol family.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 5 Verify that the configuration for your system is correct. To verify the provisioning data for your Cisco PGW 2200 Softswitch, use the prov-rtrv MML command, as described in the “Retrieving Provisioning Data” section on page 3-69. To verify the provisioning data for the Cisco ITP-Ls, use the show commands.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 5 Check the IP connectivity between the Cisco PGW 2200 Softswitch and the associated Cisco BRI voice gateway. If the IP connectivity is good, proceed to Step 6. If the IP connectivity is bad, restore the IP connectivity. If the alarm clears after the IP connectivity is restored, the procedure is complete. Otherwise, proceed to Step 6.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Note To find information on verifying the proper operation of an Ethernet interface on the Cisco PGW 2200 Softswitch, see the Sun Microsystems documentation that came with your system. For information on verifying the proper functioning of an Ethernet interface on a media gateway, see the documentation for the specific media gateway.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 5 Open a dynamic reconfiguration session to modify the routing contexts of the M3UA routing keys, as described in the “Invoking Dynamic Reconfiguration” section on page 3-66. If modifying the routing contexts corrects the problem, the procedure is complete. Otherwise, proceed to Step 6. Step 6 Verify that the AS is not shutdown on the Cisco ITP.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms If ensuring that the Cisco ITPs operate normally corrects the problem, the procedure is complete. Otherwise, proceed to Step 3. Step 3 Verify that the Ethernet interfaces between the Cisco PGW 2200 Softswitch and the Cisco ITPs are working properly.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 5 Open a dynamic reconfiguration session to modify the routing contexts of the M3UA routing keys, as described in the “Invoking Dynamic Reconfiguration” section on page 3-66. If modifying the routing contexts of the M3UA routing keys corrects the problem, the procedure is complete. Otherwise, proceed to Step 6. Step 6 Verify that the AS is not shut down on the Cisco ITP.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Note Step 4 For information on removing and replacing an Ethernet interface card on the Cisco PGW 2200 Softswitch, see the Sun Microsystems documentation that came with your system. For information on removing and replacing an Ethernet interface card on the Cisco ITP, see the documentation for the Cisco ITP.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Corrective Action To correct the problem that this alarm identifies, verify that the dial plan file was loaded correctly, by using the procedure that is described in “Verifying Proper Loading of a Dial Plan” section on page 6-121. ANAL: ATableFail_GetResult This alarm occurs when access to the result table failed during A-number analysis.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 5 Contact the Cisco TAC to analyze the problem further and to determine a solution. For more information about contacting the Cisco TAC, see the “Obtaining Documentation and Submitting a Service Request” section on page xviii. ANAL: BLoopCtrExceeded The alarm occurs when a B-number analysis operation has gone into an infinite loop.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Corrective Action To correct the problem, perform the following steps: Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93. Step 2 Verify that all the configured announcement IDs are within the range 0 through 9999, by using the numan-rtrv MML command. See Cisco PGW 2200 Softswitch Release 9.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms ANAL: BTableFlt_DgtRangeError This alarm occurs when the B-number analysis digit tree has been accessed with a digit that is out of range for the digit tree table. This alarm could occur if the system was incorrectly configured to support a base 10 dial plan, and an overdecadic digit was received from the line and passed to analysis.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 2 Verify that the associated cause table contains all of the existing call context cause values, by using the numan-rtrv MML command. See Cisco PGW 2200 Softswitch Release 9.8 Dial Plan Guide for more information. If the cause table is incomplete, modify its value using the numan-ed MML command. See Cisco PGW 2200 Softswitch Release 9.8 Dial Plan Guide for more information.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Corrective Action Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93. Step 2 Verify that the associated location table contains all of the possible references from the cause table, using the numan-rtrv MML command. See Cisco PGW 2200 Softswitch Release 9.8 Dial Plan Guide for more information.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Corrective Action To correct the problem, verify that the dial plan file was loaded correctly, by using the procedure that is described in the “Verifying Proper Loading of a Dial Plan” section on page 6-121.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 2 Verify that the specified application points in the result data are correct, using the numan-rtrv MML command. See Cisco PGW 2200 Softswitch Release 9.8 Dial Plan Guide for more information. If any of the application points are incorrect, modify their value using the numan-ed MML command. See Cisco PGW 2200 Softswitch Release 9.8 Dial Plan Guide for more information.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms If your system has been properly configured for dial plan use, the system returns a response like the following: MGC-01 - Media Gateway Controller 2001-06-01 10:09:47 M RTRV "session=active:trnkgrpprop" /* . . . CustGrpId=2222 . . . Step 3 If you need to modify your settings, start a provisioning session as described in the “Starting a Provisioning Session” section on page 3-64.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Corrective Action Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93. Step 2 Verify that the parameter, engine.SysConnectDataAccess, is set to true in the XECfgParm.dat file on the active Cisco PGW 2200 Softswitch. If the setting is correct, proceed to Step 4.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Corrective Action To correct the problem, perform the following steps: Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93. Step 2 Display the valid trunk group types using the prov-rtrv MML command that is described in the “Retrieving Provisioning Data” section on page 3-69.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Corrective Action To correct the problem, perform the following steps: Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93. Step 2 Verify that the NOA table uses all of the existing call context NOA values using the numan-rtrv MML command. See Cisco PGW 2200 Softswitch Release 9.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 2 Verify that the NPI table uses all of the possible references from the NOA table using the numan-rtrv MML command. See Cisco PGW 2200 Softswitch Release 9.8 Dial Plan Guide for more information. If the NPI table is missing any of the references from the NOA table, add them using the numan-ed MML command. See Cisco PGW 2200 Softswitch Release 9.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 3 Verify that the dial plan file was loaded correctly, by using the procedure that is described in the “Verifying Proper Loading of a Dial Plan” section on page 6-121. ANAL: Prof_InvldNPAValue This alarm occurs during profile analysis when the system encounters a 7-digit B-number and the NPA property is set against the originating trunk group.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Corrective Action To correct the problem, perform the following steps: Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93. Step 2 Perform a call trace, as described in the “Performing a Call Trace” section on page 6-156.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 2 Verify that the data for the provisioned route lists is correct by logging in to the active Cisco PGW 2200 Softswitch, starting an MML session, and entering the prov-rtrv:rtlist:“all” command: Step 3 If the data for the route lists is incorrect, correct it by using the prov-ed MML command. Otherwise, proceed to Step 4. See the Cisco PGW 2200 Softswitch Release 9.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms ANAL: RteTableFail_GetTrkAttrdata This alarm occurs when access to the trunk group attribute data table failed. The problem occurs if the index to the trunk group attribute data table is not valid or if the table is not loaded.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms ANAL: TableFail_CondRouteDescTable This alarm occurs when the conditional route description table could not be read during generic analysis. Corrective Action To correct the problem, perform the following steps: Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 3 Contact the Cisco TAC to analyze the problem further and to determine a solution. For more information about contacting the Cisco TAC, see the “Obtaining Documentation and Submitting a Service Request” section on page xviii. ANAL: TableFail_RouteHolTable This alarm occurs when route holiday table could not be read during generic analysis.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Corrective Action To correct the problem, perform the following steps: Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93. Step 2 Perform a call trace, as described in the “Performing a Call Trace” section on page 6-156.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Corrective Action To correct the problem, perform the procedure in the “Resolving an Association Alarm” section on page 6-122. Association Fail This alarm occurs when an SCTP association fails because of an IP connectivity failure or an out-of-service (OOS) destination.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms C7LNK CONGESTION This alarm occurs when an SS7 MTP2 link becomes congested and it cannot receive any more messages. Corrective Action If this alarm occurs repeatedly, perform the following steps to correct the problem: Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 2 Reroute the SS7 traffic to other links to reduce the congestion. See Cisco PGW 2200 Softswitch Release 9.8 Provisioning Guide for more information about adding links. If that does not resolve the problem, proceed to Step 3. Step 3 Contact the Cisco TAC to analyze the problem further and to determine a solution.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 2 Verify whether a charge table is present on your system by logging in to your active Cisco PGW 2200 Softswitch, starting an MML session, and entering the prov-rtrv:charge:“all” command: The system responds with a list of elements in the charge table, or with an error indicating that a charge table does not exist.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Caution Switchover operations cause the loss of all SS7 messages that are sent to the Cisco PGW 2200 Softswitch for approximately 3 seconds. This switchover affects unstable in-progress calls as well as new calls. Stable in-progress calls are not affected. If the switchover does not resolve the alarm, proceed to Step 8.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 2 Verify that the Ethernet interfaces between the Cisco PGW 2200 Softswitch and the Cisco CallManager cluster are working properly. Determine the status of the Ethernet interfaces on the Cisco PGW 2200 Softswitch by using the Cisco IPT Platform Administration application. See the online Help topic for this subject for more information.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms EISUP: Unexpected Msg/Par This alarm occurs when the EISUP module receives an unsupported message or parameter. This alarm is most likely to occur when the local EISUP version is older than the EISUP version used by the Cisco PGW 2200 Softswitch or the Cisco H.323 Signaling Interface (HSI) on the other end.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms FAIL This alarm occurs when the component referenced in the alarm failed. The failure might affect service, in which case, the system raises other alarms. Corrective Action To correct the problem, perform the following steps: Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms FailoverPeerLost This alarm occurs when the failover daemon on the standby Cisco PGW 2200 Softswitch is not reachable. Corrective Action To correct the problem, perform the following steps: Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms FAIL REMOTE STANDBY This alarm occurs on the active Cisco PGW 2200 Softswitch when a synchronization operation between the active and standby Cisco PGW 2200 Softswitches fails. The system automatically clears this alarm if a synchronization operation succeeds after the failure. If the synchronization succeeds, the system triggers the Standby Warm Start alarm.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 2 Verify that the standby Cisco PGW 2200 Softswitch is in the standby platform state, using the procedure that is defined in the “Verifying the Platform State of the Cisco PGW 2200 Softswitches” section on page 3-2. If the standby Cisco PGW 2200 Softswitch is in the standby platform state, the procedure is complete. Otherwise, proceed to Step 3.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 6 Shut down the Cisco PGW 2200 Softswitch software on your newly standby Cisco PGW 2200 Softswitch, as described in the “Shutting Down the Cisco PGW 2200 Softswitch Software Manually” section on page 2-4.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms INVALID M3UA RC This alarm occurs when the Cisco PGW 2200 Softswitch receives an M3UA message from the identified Cisco ITP that includes a routing context that has not been provisioned on the Cisco PGW 2200 Softswitch.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 5 Open a dynamic reconfiguration session to add the routing context to the SUA routing keys, as described in the “Invoking Dynamic Reconfiguration” section on page 3-66. If adding the routing context corrects the problem, the procedure is complete. Otherwise, proceed to Step 6. Step 6 Contact the Cisco TAC to analyze the problem further and to determine a solution.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 2 Verify that the affected Cisco ITP-L is operating. See the documentation for the Cisco 2800 Series Integrated Services Routers. If the affected Cisco ITP-L is not operating, start it using the procedure in the “Cisco SS7 Interface Startup Procedure” section on page 2-3. If starting the Cisco ITP-L does not resolve the problem, replace the affected Cisco ITP-L.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Corrective Action To correct the problem, perform the following steps: Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93. Step 2 Verify the IP addresses of the local interfaces on the standby Cisco PGW 2200 Softswitch by using the ifconfig -a UNIX command.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Corrective Action To correct the problem, run a manual COT test, as described in the “Running a Manual Continuity Test” section on page 6-149. License server unreachable This alarm appears if the license server is unavailable. The Cisco PGW 2200 Softswitch looks at the local license files to retrieve the configuration time TDM ports/ the run time license information.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms LIF FAIL This alarm occurs when a local Ethernet interface fails. Corrective Action To correct the problem, perform the following steps: Note If the Association Degraded or Association Failed alarms occur along with this alarm, follow the procedure that is defined in the “Resolving an Association Alarm” section on page 6-122.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms LIF LOF This alarm occurs when a loss of T1/E1 framing is detected on the LIF. The physical line has a signal but lost the framing pattern. Corrective Action To correct the problem, perform the following steps: Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 4 Contact the Cisco TAC to analyze the problem further and to determine a solution. For more information about contacting the Cisco TAC, see the “Obtaining Documentation and Submitting a Service Request” section on page xviii. LIF SES This alarm occurs when the LIF is automatically set to the out-of-service state because of severely errored seconds.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 4 If your port is configured to use D4 framing, the port might intermittently detect yellow alarms because the packet data might contain the pattern that is used to signal yellow alarm in D4 framing. If possible, switch to ESF framing in both the terminal equipment and the line equipment. If switching the framing does not clear the alarm, proceed to Step 5.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 3 Contact the Cisco TAC to analyze the problem further and to determine a solution. For more information about contacting the Cisco TAC, see the “Obtaining Documentation and Submitting a Service Request” section on page xviii. LIF: LOST CTS This alarm occurs when the physical line fails because its cable is broken or not plugged in. This is reported for V.35 facilities only.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 6 Verify that the AS is not shut down on the Cisco ITP. See the documentation for your Cisco ITP for more information. If the AS is shut down, restart it. Otherwise, proceed to Step 7. If restarting the AS corrects the problem, the procedure is complete. Otherwise, proceed to Step 7. Step 7 Contact the Cisco TAC to analyze the problem further and to determine a solution.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms MMDB: Database unavailable This alarm occurs when the main memory database is unavailable to provide any services. The Cisco PGW 2200 Softswitch attempts to recover. The alarm clears when the database becomes available.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms If that does not resolve the problem, proceed to Step 4. Step 4 Verify that the Ethernet interfaces between the Cisco PGW 2200 Softswitch and the associated media gateway are working properly. Note For information on verifying the proper operation of an Ethernet interface on the Cisco PGW 2200 Softswitch, see the Sun Microsystems documentation that came with your system.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms If the configuration of the Cisco PGW 2200 Softswitch is incorrect, begin a dynamic reconfiguration session, as described in the “Invoking Dynamic Reconfiguration” section on page 3-66. If the configuration of the affected media gateway is incorrect, modify the provisioning data for your system. See the documentation for the media gateway for more information.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93. Step 2 Perform a call trace, as described in the “Performing a Call Trace” section on page 6-156. Step 3 Contact the Cisco TAC to analyze the problem further and to determine a solution.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms OLC: Leg1deleteChanUnpackError This alarm occurs when the Cisco PGW 2200 Softswitch receives a Delete Channel (DLCX) message from the media gateway, which could not be unpacked. Cisco PGW 2200 Softswitch Release 9.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Corrective Action To correct the problem, perform the following steps: Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93. Step 2 Perform a call trace, as described in the “Performing a Call Trace” section on page 6-156.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms OOS TRAFFIC RE-ROUTE This alarm occurs when the traffic channels (bearer channels, IP network) on one side of the Cisco PGW 2200 Softswitch are lost, which causes the Cisco PGW 2200 Softswitch to reroute channels away from the affected component. Usually, this alarm is generally because of a network or equipment failure, but might be because of a provisioning failure.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Corrective Action If a rare spike in traffic causes this alarm, corrective action is not necessary. If this alarm occurs regularly, you should ensure that your links and routes are properly configured for load sharing, as described in the “SS7 Load Sharing Malfunction” section on page 6-97, and reroute some of your traffic to other Cisco PGW 2200 Softswitches.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Note This alarm can occur when a provisioning session is active during peak busy hours. If a provisioning session is active, you might clear the alarm by stopping the provisioning session. For more information on the MML commands to manage a provisioning session, see the “Provisioning a Cisco PGW 2200 Softswitch” section on page 3-64.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 5 Contact the Cisco TAC to analyze the problem further and to determine a solution. For more information about contacting the Cisco TAC, see the “Obtaining Documentation and Submitting a Service Request” section on page xviii. PC UNAVAIL This alarm occurs when a destination point code (DPC) is unavailable.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Note You can find information on verifying the proper operation of an Ethernet interface on the Cisco PGW 2200 Softswitch in the Sun Microsystems documentation that came with your system. If an element of the Ethernet connection (such as a cable or an Ethernet interface card) is not working properly, replace it. Otherwise, proceed to Step 3.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Corrective Action To correct the problem, enter some provisioning MML commands, or stop the provisioning session as described in the “Saving and Activating your Provisioning Changes” section on page 3-65. For more information about provisioning the Cisco PGW 2200 Softswitch, see Cisco PGW 2200 Softswitch Release 9.8 Provisioning Guide.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Corrective Action To correct the problem, either stop the provisioning session as described in the “Ending a Provisioning Session Without Activating your Changes” section on page 3-66. Alternatively, you can save and activate your changes according to the method described in the “Saving and Activating your Provisioning Changes” section on page 3-65.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 7 Contact the Cisco TAC to analyze the problem further and to determine a solution. For more information about contacting the Cisco TAC, see the “Obtaining Documentation and Submitting a Service Request” section on page xviii. ProtocolFileMissing This alarm occurs when the protocol files associated with your system configuration have not been installed.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Note For information on verifying the proper operation of an Ethernet interface on the Cisco PGW 2200 Softswitch, see the Sun Microsystems documentation that came with your system. If an element of the Ethernet connection (such as a cable or an Ethernet interface card) is not working properly, replace it. Otherwise, proceed to Step 3.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms SC CONFIG FAIL This alarm occurs when the provisioning parameters for the data link layer of a signaling channel are inconsistent or invalid. The signaling channel might already be provisioned. The configuration file might be corrupted so that the Cisco PGW 2200 Softswitch cannot read it.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Corrective Action To correct the problem, perform the following steps: Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93. Step 2 Ensure that the near-end and far-end data link terminations are operating. If the near-end or far-end data link terminations are not operating, fix as necessary.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Corrective Action To correct the problem, check the configuration of the affected SG and, if necessary, configure it to connect to the peer SG. SIP: DNS CACHE NEARLY FULL This alarm occurs when the domain name service (DNS) cache is nearly full.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Corrective Action To correct the problem, perform the following steps: Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Corrective Action To correct the problem, perform the following steps: Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93. Step 2 Determine whether a physical failure or an administrative shutdown caused the alarm. If a physical failure caused the alarm, proceed to Step 3.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms SS7 RTE KEY FAIL This alarm occurs when one or more routing keys for an SS7 signaling service that is associated with an SG has failed; the signaling service cannot receive some ISUP messages. The maximum number of routing keys that the associated SG supports might have been exceeded.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 2 Retrieve the current DNS properties by logging in to the active Cisco PGW 2200 Softswitch, starting an MML session, and entering the prov-rtrv:ss7SGPath:name=“sig_srv” command: Where: sig_srv is the MML name of the identified SS7 signaling service. The system returns a response that lists all the properties that are associated with the selected SS7 signaling service.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Note If you modify an ss7path that is configured for M3UAKEY, the system generates the “All M3UAKEY Ack Pending“ alarm for all the other ss7paths that are configured with the same M3UAKEY, although they are not being modified. Coincidentally, when you modify an ss7path, the system generates the M3UAKEY Ack Pending alarms when the prov-cpy and prov-dply commands are being processed.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93. Step 2 Determine the AS definitions on the associated Cisco ITP. See the documentation for your Cisco ITP for more information.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms SwitchoverFail This alarm occurs when a switchover operation from the active Cisco PGW 2200 Softswitch to the standby Cisco PGW 2200 Softswitch fails. Corrective Action To correct the problem, perform the procedure described in the “Recovering from a Switchover Failure” section on page 6-170.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Corrective Action To correct the problem, perform the following steps: Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93. Step 2 Perform a call trace, as described in the “Performing a Call Trace” section on page 6-156.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms TLC: Leg2notifyUnpackError This alarm occurs when the Cisco PGW 2200 Softswitch receives a Notify (NTFY) message from the media gateway, which could not be unpacked. Corrective Action To correct the problem, perform the following steps: Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 3 Contact the Cisco TAC to analyze the problem further and to determine a solution. For more information about contacting the Cisco TAC, see the “Obtaining Documentation and Submitting a Service Request” section on page xviii. TLC: Leg2chanOpFailed This alarm occurs when the Cisco PGW 2200 Softswitch detects an internal error or a problem that is related to a media gateway.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms numan-dlt:resulttable:custgrpid=”T002”, name=”result46”, resulttype=”CC_DIG” Otherwise, proceed to Step 5. Cisco PGW 2200 Softswitch Release 9.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 5 Verify that the BDigitCCPrefix property for the associated trunk group is set to 0 (disabled) by issuing the prov-rtrv MML command that is shown in the following example: prov-rtrv:trnkgrpprop:name=”trnkgrp1” If the BDigitCCPrefix property in the associated trunk group is not set to 0, enter the prov-ed MML command to modify the value of the property as shown in the following ex
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 11 Verify that the BDigitCCrm property for the associated trunk group is set to the correct number string.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Step 4 Verify that the IP path between the media gateway and the authentication server is working properly. If you find no problems in the IP path between the media gateway and the authentication, proceed to Step 5. Otherwise, fix the identified IP path problems. Step 5 Verify that the authentication server is working properly.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting Using Cisco PGW 2200 Softswitch Alarms Wrong IP Path This alarm occurs when an IP route or local interface that is associated with the identified component cannot be used. The system can raise this alarm when one of the following occurs: • Another route in the operating system routing table overrides the affected route. • Someone deletes a route that is configured on your system by issuing the route delete UNIX command.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting with System Logs XE Rsrc Fail This alarm occurs when memory resources have been exhausted on the active Cisco PGW 2200 Softswitch. If this alarm occurs frequently, you might need to add additional memory to the Cisco PGW 2200 Softswitch. See the Sun Microsystems documentation for your Cisco PGW 2200 Softswitch for more information about adding additional memory.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting with System Logs Viewing System Logs The log viewer, which is part of the Cisco MGC viewer toolkit, is the best tool for viewing logs. The log viewer enables you to search for specific log information, accounts for log rotations, and makes new logs available. The log server is responsible for log rotation. The log server closes the current file, and creates a new file for current logging.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting with System Logs Understanding System Log Messages Each system log message conforms to the following format: Timestamp, Process Name, Process ID, , Log ID: • Timestamp—Displays the date and time on the system when the log message was created, for example, “May 8 01:35:23:047 2001 EST”. The time that is displayed is presented to the millisecond level.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting with System Logs To change the log level of a single process, log in to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the set-log:process_name:log_level,[confirm] command. Where: • process_name—Name of the process for which you want to change the logging level. Processes are listed in the “Understanding Processes” section on page 3-5. • log_level—Desired logging level.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Troubleshooting with System Logs Note You cannot set the logging level of the process manager (PM-01) by issuing the set-log:all:log_level MML command. You can change the logging level of the process manager only by issuing the set-log:pm-01:log_level MML command. Note You cannot enter the set-log:all:log_level MML command to set all of the processes to the debug (DEBUG) logging level.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems • CPU utilization • Number of users that are logged in • Statistics for the Ethernet interfaces • IP routing • System setup • Swap space • Date and time of last system reboot • Permissions for the configuration library (CONFIG_LIB) • File permissions for the /opt/CiscoMGC/etc and /opt/CiscoMGC/bin directories • Copy of the XECfgParm.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems • Broadband ISUP (BISUP) There are many variations of the different parts of the SS7 protocol stack. MTP has ANSI, ITU, Bellcore, and several national variations. Each country and each major carrier might have slightly different variations of a part to fit its particular needs. The SS7 network must have the highest degree of reliability.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems The following sections describe signaling channel problems: • SS7 Link is Out-of-Service, page 6-96 • SS7 Load Sharing Malfunction, page 6-97 • Physical Layer Failures, page 6-98 • Configuration Errors, page 6-98 • Supporting Entity Failures, page 6-99 • Incomplete Signaling, page 6-99 • Changing Service States, page 6-99 SS7 Link is Out-of-Service If an SS7 link is out-of-service on your
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems Step 7 Contact the Cisco TAC to analyze the problem further and to determine a solution. For more information about contacting the Cisco TAC, see the “Obtaining Documentation and Submitting a Service Request” section on page xviii.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems Step 6 Modify the priority settings of the link by entering the prov-ed:c7iplnk:name=“lnkname”,pri=1 command. Where: lnkname—Name of an SS7 link that is not set to priority 1. Repeat this step for each link that is not set to priority 1. Step 7 If any of the SS7 routes show a priority other than 1, change the priority settings to ensure proper route load sharing.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems Ensure that the MTP2 timers and thresholds match the network defaults. Confirm that the far-end switch or STP has the same values as your system. When you use a Cisco ITP-L to terminate MTP2, confirm that the RUDP parameters match on both sides and are consistent with the documentation.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems • Uninhibit (UNH)—Signaling channel is requested to be removed from an INH state and to provide service for call processing. This state is for SS7 signaling channels only and fails on other types of signaling channels. Use this option (UNH), rather than the IS option, to return an inhibited signaling channel to service. Note Changing the state of a signaling channel generates an alarm.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems Bouncing SS7 Links Usually, mismatched signaling link codes (SLCs) or DPCs/OPCs between the Cisco PGW 2200 Softswitch and the far end cause this condition. To resolve a bouncing SS7 condition, perform the following steps: Step 1 If you have not already collected system data, refer to the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems Traffic Restart Ensure that the MTP3 traffic restart timers and thresholds agree with the network defaults. Confirm that the far-end switch or STP has the same values.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems Step 5 Contact the Cisco TAC to analyze the problem further and to determine a solution. For more information about contacting the Cisco TAC, see the “Obtaining Documentation and Submitting a Service Request” section on page xviii. SS7 Destination is Unavailable An SS7 destination is unavailable when all of the routes to the destination are out-of-service.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems Step 1 Log in to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the set-dest:sig_srv:serv_state command. Where: • sig_srv—MML name of the desired signaling service. • serv_state—Desired service state. The following service states are valid: – IS—Places a signaling service in service. – OOS—Takes a signaling service out of service.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems Setting the Service State of a C7/SS7 Link or Linkset To change the service state of an SS7 link, log in to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the set-c7lnk:c7link_name:serv_state command. Where: • c7link_name—MML name of the SS7 link you want to modify. • serv_state—Service state to set. Valid values for SS7 links are IS, OOS, FOOS, INH, and UNH.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems Setting the Service State of an IP Route To change the service state of an IP route, log in to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the set-iproute:iproute_name:serv_state[,confirm] command. Where: Note • iproute_name—MML name of the IP route you want to modify. • serv_state—Service state that you want to set. Valid values for IP links are IS, OOS, and FOOS.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems Setting the Service State of a Local Subsystem Number To set the service state of a local subsystem number (LSSN), perform the following steps: Step 1 Log in to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the set-lssn-state:ssn:serve_state command. Where: • ssn—MML name of the desired LSSN. • serv_state—Desired service state.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems Note See Cisco PGW 2200 Softswitch Release 9.8 Provisioning Guide for more information on the MTP timers. Verifying MTP2 Timers To verify the values that are used for the MTP2 timers on the Cisco ITP-Ls, complete the following steps: Step 1 Enter the #show ss7 mtp2 timer channel command at the Cisco ITP-L to display the settings for the MTP2 timers. Where: channel—Specifies a channel, 0 through 3.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems The system returns a message like the following: MGC-01 - Media Gateway Controller 2000-07-27 18:33:56 M RTRV "session=nsite04:sigsvcprop" /* mtp3ApcMtpRstrtT28 = 50 mtp3DlnkConnAckT7 = 10 mtp3FrcUnhT13 = 10 mtp3InhAckT14 = 20 mtp3LocInhTstT20 = 900 mtp3MaxSltTries = 2 mtp3MsgPriority = 2 mtp3MtpRstrtT24 = 60 mtp3RepeatRstrtT26 = 150 mtp3TfrUsed = false mtp3TraSnT29 = 600 mtp3tstSltmT1 = 60 mtp3tstSltmT
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems Note See Cisco Signaling Link Terminal for more information on the parameters for this command.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems mtp3ApcMtpRstrtT28 = 30 mtp3DlnkConnAckT7 = 10 mtp3FrcUnhT13 = 10 mtp3InhAckT14 = 20 mtp3LocInhTstT20 = 900 mtp3MaxSltTries = 2 mtp3MsgPriority = 2 mtp3MtpRstrtT24 = 100 mtp3RepeatRstrtT26 = 150 mtp3TfrUsed = false mtp3TraSntT29 = 600 mtp3tstSltmT1 = 60 mtp3tstSltmT2 = 600 mtp3UnhAckT12 = 10 reference = ANSI92 rudpAck = enable rudpKeepAlives = enable rudpNumRetx = 2 rudpRetxTimer = 6 rudpSdm = enable ru
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems Verifying and Modifying RLM Timers To change the values for these timers, change them on the Cisco PGW 2200 Softswitch and on the associated media gateways. See the documentation for your media gateway for more information on changing the RLM timers on the media gateway. To change the RLM timers on the Cisco PGW 2200 Softswitch, perform the following steps.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems Step 3 Modify the RLM timer properties, as needed, by issuing the prov-ed:lnksetprop:name=“protocol_fam”,prop_name=“value”,prop_name=“value”,... command. Where: • protocol_fam—MML name of the associated protocol family. • prop_name—Name of the RLM timer property you want to modify. • value—Value you want to set for the specified RLM timer property.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems Table 6-2 Configurable ISUP Timer Protocol Listings Timers • T1 Associated Protocol Files • ANSISS7_STANDARD • Q761_BASE • Q767_BASE • Q761_SINGAPORE • Q761_ARGENTINA • ISUPV2_FINNISH96 • ISUPV2_FRENCH • Q761_THAILAND • Q761_PERU • Q761_BELG_C2 • ISUPV2_JAPAN • T2, T5, T6 • ANSISS7_STANDARD • T7, T8, T9 • Q761_BASE • T12, T13, T14 • Q767_BASE • T15, T16, T17 • Q
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems Table 6-2 Timers • • Note T35 T38 • T_CCR • T_CCRR • T_CGB • T_CGBA • T_CRA • T_GRS • T_CVT Configurable ISUP Timer Protocol Listings (continued) Associated Protocol Files • Q761_BASE • Q767_BASE • Q761_SINGAPORE • Q761_ARGENTINA • ISUPV2_SPANISH • ISUPV2_FINNISH96 • ISUPV2_FRENCH • Q761_THAILAND • Q761_PERU • Q761_BELG_C2 • ISUPV2_JAPAN • Q761_BASE • Q761_S
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems To verify and modify the values that are used for the ISUP timers, complete the following steps: Step 1 Unless you previously created a profile for the associated signaling service or trunk group with modified values for these ISUP timers, the values for these eight timers match the default values listed in the preceding table.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems Step 7 Create a profile for your new ISUP timer values by using the prov-add:component:name=”comp_name”, isuptmrprofile=”profile_name” command. Where: • component—MML component type name for signaling service or trunk group profiles. Enter one of the following: – sigpathprof—Component type for signaling service profiles. – trnkgrpprof—Component type for trunk group profiles.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems Step 5 Shut down the Cisco PGW 2200 Softswitch software on your active Cisco PGW 2200 Softswitch, using the procedure in the “Shutting Down the Cisco PGW 2200 Softswitch Software Manually” section on page 2-4.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems Starting a Japanese SS7 Signaling Link Test To start a signaling link test on a link that is configured for Japanese SS7, log in to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the sta-ss7-slt:link command. Where link is the MML name of a link that is configured for Japanese SS7. For example, to start a signaling link test on a link that is called ls1-link1, enter the command.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems Starting a Japanese SS7 Signaling Route Test To start a signaling route test on a route that is configured for Japanese SS7, log in to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the sta-ss7-srt:pt_code:lset=”linkset” command. Where: • pt_code—MML name of an adjacent point code (APC) or destination point code (DPC) configured for Japanese SS7.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems Verifying Proper Loading of a Dial Plan Step 1 If you have not already collected system data, refer to the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93. Step 2 Search the active system log file, as described in the “Viewing System Logs” section on page 6-90, for logs that indicate that the dial plan was loaded incorrectly.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SS7 Network Related Problems Resolving an Association Alarm When an alarm indicates a failure on an association, perform the following steps: Step 1 If you have not already collected system data, refer to the method that is described in the “Collecting System Data for Cisco TAC” section on page 6-93. Step 2 If this alarm occurs along with the LIF FAIL alarm on the failed destination address, proceed to Step 3.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems Step 2 Remove the padding according the to point code address type that applies to the point code (14-, 16-, or 24-bit). Note For an explanation of the point code address types, see Cisco PGW 2200 Softswitch Release 9.8 Provisioning Guide.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems • Stopping Calls, page 6-144 • Auditing an MGCP Media Gateway, page 6-148 • Running a Manual Continuity Test, page 6-149 • Verifying Continuity Test Settings, page 6-149 • Media Gateway IP Destination or Link Out-of-Service, page 6-151 • Calls Fail at the Cisco PGW 2200 Softswitch, page 6-152 • 3.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems Step 2 Verify that the state of the Cisco PGW 2200 Softswitch changed by entering the rtrv-admin-state MML command, as described in the “Retrieving the Administrative State of a Cisco PGW 2200 Softswitch” section on page 3-56.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems Note Use this command only for time-division multiplexing (TDM) trunk groups. Allow the corresponding MML name for component type 0020. • state—The administrative state. The following states are valid: – Lock—Makes all bearer channels that are associated with the trunk group unavailable for call processing.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems – Unlock—Makes all bearer channels that are associated with the signaling service available for call processing. If the state is set to unlock, the media gateway becomes available. New calls are allowed to use the affected bearer channels.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems To set the administrative state of a bearer channel or a range of bearer channels in a span, perform the following steps: Step 1 Log in to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the rtrv-admin-state:sig_srv:span=x,bc=y[,rng=range]:state command: Where: • sig_srv—MML name of the signaling service.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems Where: • sig_srv—MML name of the signaling service. The following signaling service types are valid for this command: – In-band TDM up to MUX and then time switched to TDM media and sent to the Cisco PGW 2200 Softswitch. – In-band TDM signaling up to CU and then encapsulated and sent over IP to the Cisco PGW 2200 Softswitch.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems Note Not all SS7 variants support the querying of CICs. If you execute this command on a signaling service that is configured for an SS7 variant that does not support the querying of CICs, the system returns an error code, SABT, when the query operation times out. See Cisco PGW 2200 Softswitch Release 9 MML Command Reference for more information on the SABT error code.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems – OG_BUSY_BOTH_BLOC—Outgoing is busy, blocked both remotely and locally – IDLE—The circuit is idle, available for use – IDLE_LOC_BLOC—Idle, blocked locally – IDLE_REM_BLOC—Idle, blocked locally – IDLE_BOTH_BLOC—Idle, blocked both locally and remotely Resolving Local and Remote CIC State Mismatch When the local and remote states for CICs do not match and the problem lies with the local CIC states,
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems To perform a circuit validation test, complete the following steps: Step 1 Start an MML session on the active Cisco PGW 2200 Softswitch and validate the properties for a particular circuit identification code (CIC) using the vld-cic:dest_pc:cic=number command. Where: • dest_pc—MML name for the DPC associated with the affected CIC. • number—Trunk identification number for the affected CIC.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems • COT—Continuity check requirements indicator. The values in these fields should be the same in the LOC and REM lines. The following values are valid for this field: – UNK—Unknown continuity check requirements – NONE—No continuity check requirements – STAT—Statistical continuity check requirements – PERC—Per call continuity check requirements • TRK—Trunk number.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems The response lists the SS7 signaling services and their associated DPCs. Search for the DPC associated with the trunk to identify the name of the SS7 signaling service. In the example, dms100-pc is the name of the DPC associated with the trunk.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems You can map the preceding response to the circuit validation test in Step 1, as presented in the following list: • CctGrpCarrier—Value in this field maps to the value in the GRP field, as follows: – 0—Equal to UNK (unknown carrier) in the GRP field. – 1—Equal to ANL (analog carrier) in the GRP field. – 2—Equal to DIG (digital carrier) in the GRP field.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems Step 9 Identify the trunk group that is associated with the affected DPC using the prov-rtrv:trnkgrp:svc=”sig_serv” command: Where: sig_serv—MML name of the SS7 signaling service that was identified in Step 4.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems For example, to change the settings for the COT to per call and seizing (glare) to no circuit control for the trnkgrpdms trunk group, enter the prov-ed:ztrnkgrp:name="trnkgrpdms",ExtCOT="Loop", CotPercentage=”100”,GLARE="0" command: Step 12 Activate your new configuration as described in the “Saving and Activating your Provisioning Changes” section on page 3-65.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems The response lists the properties that are associated with the selected component ID. The MML name for the IP link is in the third column in the response. In the preceding example, “bh531-31” is the MML name for the IP link. Step 4 Repeat Step 3 for each component ID identified in Step 2.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems Step 9 Define the D-channel on the associated media gateway. See the documentation for the media gateway for information on how to define a D-channel. The procedure is finished. Step 10 Start a provisioning session as described in the “Starting a Provisioning Session” section on page 3-64. Step 11 Delete the appropriate D-channels using the prov-dlt:iplnk:name=”ip_link”,... command.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems Note You can configure the Cisco PGW 2200 Softswitch software to issue individual or group supervision messages for point codes that are associated with an ISUP signaling service. ISUP signaling services issue group supervision messages by default.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems Note You can configure the Cisco PGW 2200 Softswitch software to issue individual or group supervision messages for point codes that are associated with an ISUP signaling service. ISUP signaling services issue group supervision messages by default.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems Note The Cisco PGW 2200 Softswitch does not run the audit cron job when the CPU load of the call engine is greater than the limit set in the XECfgParm.dat file. For more information on XECfgParm.dat configuration, see Cisco PGW 2200 Softswitch Release 9 Software Installation and Configuration Guide.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems In the second message, which contains information on the affected CIC, the text that immediately follows the word “point” identifies the following: • MML name of the signaling service that is associated with the affected CIC (sigsrv1 in the example). • Internal hexadecimal code that is associated with the identified signaling service (00130002 in the example). This number appears in brackets.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems Repeat this step for each bearer channel you have identified as being stuck. Step 13 Repeat Step 3 and Step 4. Perform a third call state audit and search the active system log file to determine whether the previously identified CICs are still stuck. If the previously identified CICs are no longer stuck, proceed to Step 14. If these CICs are still stuck, proceed to Step 15.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems • Stopping Calls on Spans, page 6-146 • Stopping Calls on CICs, page 6-147 Stopping Calls on a Cisco PGW 2200 Softswitch To stop all active calls on all traffic channels on a Cisco PGW 2200 Softswitch, log in to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the stp-call:mgc,confirm command. Where: mgc— MML name of the desired Cisco PGW 2200 Softswitch.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems Where: sig_srv—MML name of the desired signaling service. The following signaling service types are valid for this command: • In-band TDM up to MUX and then time switched to TDM media and sent to the Cisco PGW 2200 Softswitch. • In-band TDM signaling up to CU and then encapsulated and sent over IP to the Cisco PGW 2200 Softswitch.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems Where: • sig_srv—MML name of the signaling service. The following signaling service types are valid for this command: – In-band TDM up to MUX and then time switched to TDM media and sent to the Cisco PGW 2200 Softswitch. – In-band TDM signaling up to CU and then encapsulated and sent over IP to the Cisco PGW 2200 Softswitch.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems Auditing an MGCP Media Gateway You can audit an MGCP media gateway from the Cisco PGW 2200 Softswitch.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems pass is" The response indicates whether the audit passed or failed. If the audit failed, see the documentation for the associated MGCP media gateway for more information on troubleshooting the identified problem. To retrieve an audit that is run on all the MGCP media gateways, log on to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the rtrv-aud-gw:all command.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems If the system is properly configured to use a dial plan, the system returns a response like the following: MGC-01 - Media Gateway Controller 2001-06-01 10:09:47 M RTRV "session=active:sigsvcprop" /* adjDestinations = 16 AlarmCarrier = 0 BothwayWorking = 1 CctGrpCarrier = 2 CGBA2 = 0 CircHopCount = 0 CLIPEss = 0 CotInTone = 2010 CotOutTone = 2010 CotPercentage = 0 CustGrpId=2222 dialogRange = 0 Ex
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems Media Gateway IP Destination or Link Out-of-Service If an IP link or destination to a media gateway is out-of-service, perform the following steps: Note An IP destination to a media gateway is out-of-service when both IP links associated with the destination are out-of-service.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems Step 9 Verify that the configuration for RLM on the Cisco PGW 2200 Softswitch matches the configuration on the media gateway. To display the configuration of the IP links on the Cisco PGW 2200 Softswitch, enter the prov-rtrv:iplnk:"all" MML command at the active Cisco PGW 2200 Softswitch.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems Step 3 Verify that the signaling channels are in-service, as described in the “Verifying the Status of all Signaling Services” section on page 3-9. If any of the signaling channels are out-of-service, attempt to return them to service by using the appropriate procedures. Otherwise, proceed to Step 4. Step 4 Run a call trace as described in the “Performing a Call Trace” section on page 6-156.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving Bearer Channel Connection Problems Step 7 Contact the Cisco TAC to analyze the problem further and to determine a solution. For more information about contacting the Cisco TAC, see the “Obtaining Documentation and Submitting a Service Request” section on page xviii. Calls are Misrouting If calls are misrouting, you might have a problem with your dial plan or routing data.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Resolving SIP Communication Problems Step 6 Deploy the updated dial plan by issuing the chg-dpl:custgrpid=”group_number” MML command: Wher: group_number—Customer group identification number that is associated with the affected dial plan. Step 7 Re-run the diagnostic trace on the dial plan according to way described in Step 1. If the system finds no errors, the procedure is complete.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Tracing Performing a Call Trace After eliminating all physical connections, signal links, bearer channels, and destinations as the cause of a problem, the call engine running on the Cisco PGW 2200 Softswitch might be part of a problem. Performing a call trace while making a call can derive details about what takes place inside the call engine and might indicate where a breakdown is occurring.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Tracing Where: The filename (yyyymmddhhmmss) is a time stamp that is formatted as follows: – yyyy—Four-digit designation for the year, such as 2000, 2001, or 2002. – mm—Two-digit designation for the month (01 through 12). – dd—Two-digit designation for the day of the month (01 through 31). – hh—Two-digit designation for the hour of the day (00 through 23). – mm—Two-digit designation for the minutes of an hour (00 through 59).
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Tracing • Trunk group trunk-level trace traces only calls for a given trunk (or CIC). Use this format if the trunk group and trunk on which the call is placed is known. sta-sc-trc:trkgrp:trk=w Note Step 2 See Cisco PGW 2200 Softswitch Release 9 MML Command Reference for detailed information on using the sta-sc-trc command. Make the call. Starting A Call Trace (on Release 9.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Tracing Table 6-3 Parameter List of the MML Command sta-sc-trc Parameter Name Description sig_path See Starting A Call Trace, page 6-156. span See Starting A Call Trace, page 6-156. Specify this parameter with the parameters rng and sig_path. rng See Starting A Call Trace, page 6-156. tc See Starting A Call Trace, page 6-156. Specify this parameter the parameters rng, span, and sig_path.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Tracing Table 6-3 Parameter Name mcl Parameter List of the MML Command sta-sc-trc (continued) Description Parameter Category The machine congestion level. Valid values are integers from Stop condition 0 to 3. Default value is 1. Where: 0—Do not stop the call trace when MCL occurs. 1—Stop the call trace when the MCL reaches MCL1. Parameter Combinations Optional parameters.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Tracing • Use the following command to start a 12 hour call trace of the call with duration longer than 3 hours in the trunk group tg-6006: sta-sc-trc:tg-6006,duration=10800,prd=43200,confirm You can use the following two commands to perform call traces on a standby Cisco PGW 2200 Softswitch.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Tracing The call trace stops for one of the following four reasons. • M Call trace is stopped because the MCL is reached. MGC-02 - Media Gateway Controller 2008-04-28 10:25:36.782 EDT RTRV “../var/trace/eisup-0428_eisup-pgw2_20080427223536.btr: MCL reached. " ; • Call trace is stopped automatically and the desired call trace is collected. MGC-02 - Media Gateway Controller 2008-04-30 14:39:19.042 CST M RTRV "..
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Tracing The script then displays a list of commands and prompts you to enter a command. The script lists the following commands: • S—Displays the call trace data using the SimPrint utility. For more information on SimPrint, see the “Understanding SimPrint” section on page 6-165. • F—Displays the call trace data using the SimPrint utility, and a listing of the sent and received fields. • D—Displays the data in the .
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Tracing If you are experiencing problems with call processing and need to contact Cisco for support, you should run a call trace before contacting Cisco TAC. The trace file helps the Cisco TAC troubleshoot the problem more effectively. For some problems, the Cisco TAC cannot begin troubleshooting the problem until you supply the trace file; so, it is a good practice to create this file before contacting them.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Tracing Understanding SimPrint SimPrint (SP) is a utility for viewing .trc files. SP converts a .trc file into a sequence diagram that shows all of the external and internal events that occur in a .trc file. The sequence diagram is useful for getting an overview of what is occurring in the trace.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Tracing To print diagnostic information on a hung call, complete the following steps: Step 1 If the hung call is a SIP-to-SIP call, proceed to Step 3. Otherwise, proceed to Step 2.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Tracing • xyz—Optional parameter that names the ASCII log file to which the output of this command is written. The name that you specify for this parameter is prefixed to the actual name of the file, which includes the sig_path name, date, and time. If you do not provide a log filename, a default name consisting of the sig_path name, date, and time is created. The extension of these log files is .prt.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Tracing Step 2 To change directories, enter the cd Step 3 Use a text file viewer, such as vi, to view the contents of the log file. /opt/CiscoMGC/var/trace UNIX command. Stopping an Abnormal Call Termination Trace You can stop an in-progress abnormal call termination trace by issuing the stp-abn-trc MML command.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Platform Troubleshooting The following sections contain procedures that pertain to resolving problems with the Cisco PGW 2200 Softswitch platform: • Verifying Cisco PGW 2200 Softswitch Ethernet Operation, page 6-169 • Deleting Unnecessary Files to Increase Available Disk Space, page 6-169 • Recovering from a Switchover Failure, page 6-170 • Recovering from Cisco PGW 2200 Softswitch Failure, page 6-172 • Rest
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Step 2 Delete the identified call trace files using the rm -i filename UNIX command. Where: filename—Name of the call trace file (either *.btr or *.trc) that you identified for deletion. Step 3 Repeat Step 2 for each additional call trace file that is identified for deletion.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Step 4 See the “Alarm Troubleshooting Procedures” section on page 6-4 for descriptions of the steps necessary to resolve the critical alarm that caused the switchover attempt. Step 5 Log in to the standby Cisco PGW 2200 Softswitch, start an MML session, and view the current alarms, as described in the “Retrieving All Active Alarms” section on page 6-3. Step 6 Resolve the listed alarms.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Step 10 Verify that the IP address parameters in the XECfgParm.dat file, which are presented in the following list, are set correctly on each host. • *.ipAddrLocalA • *.ipAddrLocalB • *.ipAddrPeerB • *.IP_Addr1 • *.IP_Addr2 • *.IP_Addr3 • *.IP_Addr4 • *.Virtual_IP_Addr If the IP address settings are correct, proceed to Step 11.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Note In these procedures, it is assumed that backup operations have been performed regularly on the Cisco PGW 2200 Softswitch. For more information on backing up the Cisco PGW 2200 Softswitch, see the “Backing Up System Software” section on page 3-29. Note Successful recovery from a natural or man-made disaster depends upon advanced planning for a possible disaster.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Recovering from a DiskSuite Failure on the Opteron Platform To recover from a DiskSuite failure on the Opteron platform, perform the following steps: Step 1 Shut down the Cisco PGW 2200 Softswitch. See “Cisco PGW 2200 Softswitch Shutdown Procedure” section on page 2-4. Step 2 Remove the damaged disk, for example, Disk 1. Step 3 Boot up the system from Disk 2.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Step 25 Enter the metadb Note Step 26 -a -c 3 c0t2d0s4 command and press Enter. See Step 4 for the meaning of the last parameter. Enter the metastat | grep metareplace command and press Enter to discover the failed submirrors. A list like the following is displayed.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Step 7 Start the Cisco PGW 2200 Softswitch software, as described in the “Starting the Cisco PGW 2200 Softswitch Software” section on page 2-2. Step 8 Synchronize the databases of the active and standby Cisco PGW 2200 Softswitches by using the procedure that is described in the Synchronizing Databases section of the Configuring the Cisco PGW 2200 Softswitch Software Release 9.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Step 13 Search for the pom.dataSync property and ensure that it is set to true. Step 14 Save the file and exit the text editor. Step 15 Start the Cisco PGW 2200 Softswitch software, as described in the “Starting the Cisco PGW 2200 Softswitch Software” section on page 2-2.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Listing Backup Files To list the backup files in a particular directory path, enter the mgcrestore on the Cisco PGW 2200 Softswitch. -d path -l UNIX command Where: path—Directory path in which you stored backup files, such as a directory on a remote server or a local tape drive.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Restoring a Backup File Using the Mgcrestore Script You can also restore a configuration by running the mgcrestore script. To restore the configuration data that is stored in a particular backup file that is stored in a directory, perform the following steps: Note Step 1 You can restore a backup file only when you are logged in to your system as mgcusr.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Configuration Export Failed Because of MMDB If you attempt to export your configuration settings by issuing the prov-exp:all MML command and the MMDB is not running, the system returns a failure message. The MMDB must be running for the prov-exp:all MML command to function.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Step 3 Verify that the *.disableMeas parameter in the XECfgParm.dat file is set to false on each host by using the procedure in the “Rebooting Software to Modify Configuration Parameters” section on page 6-183. Step 4 Contact the Cisco TAC to analyze the problem further and to determine a solution.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Step 2 If your system is provisioned to control Voice over IP (VoIP) calls that do not originate or terminate on SS7 or PRI (such as SIP-to-SIP or SIP-to-EISUP/H.323 calls), you must synchronize the system state data before continuing. To synchronize the system state data, proceed to Step 3. If your system is provisioned to control VoIP calls for which at least one call leg is SS7 or PRI, proceed to Step 4.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Rebooting Software to Modify Configuration Parameters Sometimes you might need to change your configuration settings in the XECfgParm.dat file while the system is in-service. To change a configuration while the system is in-service, perform the following procedure: Caution Performing this procedure stops the functioning of the Cisco PGW 2200 Softswitch software.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Diagnosing SNMP Failure A variety of problems can cause the Cisco PGW 2200 Softswitch to fail to respond to SNMP requests. The Cisco PGW 2200 Softswitch uses the Sun Microsystems Solaris 8 or Solaris 10 operating system. Both Solaris 8 and Solaris 10 are 64-bit operating systems and older hardware platforms cannot support them.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Step 6 Re-install the operating system as described in Cisco PGW 2200 Softswitch Release 9.8 Software Installation and Configuration Guide. Select the 64-bit kernel during installation. If the operating system installs successfully, proceed to Step 7. Otherwise, proceed to Step 9. Step 7 Repeat Step 5 to ensure that the 64-bit kernel is installed. If the 64-bit kernel is installed, proceed to Step 8.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Caution To correct the system time on the Cisco PGW 2200 Softswitches, you must log in as root. You should closely control the use of the superuser (root) password and privileges.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting NTP is Used and the Cisco PGW 2200 Softswitch is the Source of the CDRs If the Cisco PGW 2200 Softswitch is the source of CDRs and NTP maintains system time, the system time can get out of synchronization with the NTP server only if a user with root access (which should be strictly controlled) modifies the time on an Cisco PGW 2200 Softswitch. You cannot modify the time on the NTP server.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting When you enter this command, the system displays a list of files. Step 3 Check the list of files for the last finished filename, which is preceded by a period (.). Note the filename because you will need it later. Step 4 Log in to the standby Cisco PGW 2200 Softswitch as root and enter the command to change directory. Step 5 Enter the # toggle_ftp.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Securing Cisco BAMS To secure Cisco BAMS on your network: Step 1 Log in to the standby Cisco BAMS by enter the following command: % bams Step 2 The following steps require you to use MML commands. To use MML commands, enter the following command: % mml Step 3 Enter the node of the Cisco PGW 2200 Softswitch that you want to change.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting The system displays text like the following: You are running as root - Good... Operating System: SunOS 5.8 Disable ftp in inetd.conf file Done! Step 8 Type the following command and press Enter to toggle Telnet off: # toggle_telnet.sh disable Note is a name that you select. The system displays text like the following: You are running as root - Good... Operating System: SunOS 5.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Step 14 Enter y (yes) to continue and press Enter. The system displays text like the following: Generating security keys, this will take a couple of minutes... Generating public/private rsa key pair. Your identification has been saved in /opt/CiscoBAMS/local/.ssh/id_rsa. Your public key has been saved in /opt/CiscoBAMS/local/.ssh/id_rsa.pub.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Step 21 Repeat Step 15 through Step 19 for additional Cisco PGW 2200 Softswitch nodes. The system displays text like the following: mgcusr on successfully configured Do you want to configure second interface for ? n Step 22 Enter n (no) and press Enter.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Step 28 Enter y to continue and press Enter. The system displays text like the following: Sun Microsystems Inc. SunOS 5.6 Generic August 1997 Warning: Before running this script, SSH must be installed on all PGW and BAMS hosts. This script will reset the existing known hostkeys and user keys for bams user for each host entered during this session.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Step 33 Enter y (yes) again and press Enter. The system displays text like the following: mgcusr on successfully configured Do you want to configure second interface for ? n Step 34 Step 35 You can answer either y (yes) or n (no): • Yes (configuring a second interface) is optional. If you answer y, repeat Step 1 through Step 19. • If you answer no, proceed to Step 21.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Step 41 Check for alarms on the Cisco BAMS.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Step 2 Verify that the TIBCO adapter daemon is running by entering the following UNIX command on the active Cisco PGW 2200 Softswitch: ps -ef The system returns a response like the following: UID PID PPID C STIME TTY root 0 0 0 10:28:20 ? root 1 0 0 10:28:20 ? mgcusr 14437 14427 0 13:57:19 ? /opt/CiscoMGC/local/tibAdapter.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Installing the License File See the detailed procedure in Chapter 3, “Installing Cisco PGW 2200 Softswitch Software,” in the Cisco PGW 2200 Softswitch Release 9.8 Software Installation and Configuration Guide: http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9.8/Installation/Guide/Install98.html Replacing a Failed Disk This section describes the process for replacing a defective Cisco PGW 2200 Softswitch disk.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting State: Needs maintenance Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 8193150 blocks (3.9 GB) d7: Submirror of d9 State: Okay Size: 8193150 blocks (3.9 GB) Stripe 0: Device Start Block Dbase c3t0d0s3 0 No State Reloc Hot Spare Okay Yes d8: Submirror of d9 State: Needs maintenance Invoke: metareplace d9 c3t1d0s3 Size: 8193150 blocks (3.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Stripe 0: Device c3t0d0s0 Start Block 0 Dbase No State Reloc Hot Spare Okay Yes d2: Submirror of d3 State: Needs maintenance Invoke: metareplace d3 c3t1d0s0 Size: 4096575 blocks (2.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Step 7 Display the available disk information by issuing the following command: # format The system displays text like the following: (Use Ctrl-C to exit.) Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c3t0d0 /pci@79,0/pci1022,7458@11/pci1000,3060@2/sd@0,0 1.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Stripe 0: Device c3t0d0s3 Start Block 0 Dbase No State Reloc Hot Spare Okay Yes d8: Submirror of d9 State: Needs maintenance Invoke: metareplace d9 c3t1d0s3 Size: 8193150 blocks (3.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Stripe 0: Device c3t1d0s0 Start Block 0 Dbase No State Reloc Hot Spare Maintenance Yes d15: Mirror Submirror 0: d13 State: Okay Submirror 1: d14 State: Needs maintenance Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 4096575 blocks (2.0 GB) d13: Submirror of d15 State: Okay Size: 4096575 blocks (2.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting m W a M D F S R Step 12 replica replica replica replica replica replica replica replica is master, this is replica selected as input has device write errors is active, commits are occurring to this replica had problem with master blocks had problem with data blocks had format problems is too small to hold current data base had device read errors Enter the following commands to enable the mirror and submirror comp
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Device c3t0d0s3 Start Block 0 Dbase No State Reloc Hot Spare Okay Yes d8: Submirror of d9 State: Okay Size: 8193150 blocks (3.9 GB) Stripe 0: Device Start Block Dbase c3t1d0s3 0 No State Reloc Hot Spare Okay Yes d6: Mirror Submirror 0: d4 State: Okay Submirror 1: d5 State: Okay Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 10249470 blocks (4.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting d15: Mirror Submirror 0: d13 State: Okay Submirror 1: d14 State: Okay Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 4096575 blocks (2.0 GB) d13: Submirror of d15 State: Okay Size: 4096575 blocks (2.0 GB) Stripe 0: Device Start Block Dbase c3t0d0s6 0 No State Reloc Hot Spare Okay Yes d14: Submirror of d15 State: Okay Size: 4096575 blocks (2.
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform Platform Troubleshooting Cisco PGW 2200 Softswitch Release 9.
A P P E N D I X A Configuring Cisco PGW 2200 Softswitch Log Files Revised: March 7, 2011, OL-0800-14 This appendix describes the Cisco PGW 2200 Softswitch log files and the associated procedures for setting up the data dumper. The data dumper controls how files are processed for three of the log-file types. The logs records statistical information about the calls that the system processed. The logs also record network events, such as delays or service-affecting conditions.
Appendix A Configuring Cisco PGW 2200 Softswitch Log Files Configuring the Data Dumper Configuring the Data Dumper The Cisco PGW 2200 Softswitch software contains a function that is called the data dumper. The data dumper controls the destinations for active and archived log files for CDRs, measurements, and alarms. It also controls when the active files are archived. The data dumper runs automatically and works correctly with a default configuration.
Appendix A Configuring Cisco PGW 2200 Softswitch Log Files Configuring the Data Dumper Table A-2 Dumper Sink Log File Parameters (continued) Field Number Default Value Description 7 0 Defines the maximum size of the log file in bytes before it is moved to the spool directory. If this value is set to 0, the available disk space is the only factor that limits the size of the file.
Appendix A Configuring Cisco PGW 2200 Softswitch Log Files Configuring the Data Dumper Step 9 Repeat Step 1 through Step 5 on your standby Cisco PGW 2200 Softswitch. Step 10 Log on to the active Cisco PGW 2200 Softswitch, start an MML session and perform a manual switchover as described in the “Performing a Manual Switchover” section on page 3-96.
Appendix A Configuring Cisco PGW 2200 Softswitch Log Files Configuring the Data Dumper Step 10 Restart the Cisco PGW 2200 Softswitch software using the procedure that is described in the “Starting the Cisco PGW 2200 Softswitch Software” section on page 2-2. The procedure is complete. Step 11 Repeat Step 1 through Step 7 on your standby Cisco PGW 2200 Softswitch.
Appendix A Configuring Cisco PGW 2200 Softswitch Log Files Configuring the Data Dumper A comma separates each field. Table A-3 describes the content of each field. Table A-3 Archived Alarm File Fields Field Name Data Type Maximum Length Comments Release level Integer 3 Format of records (should be set to 0). Timestamp (seconds) Integer 10 Indicates the time, in seconds, since the start of the UNIX internal timer, time of epoch.
Appendix A Configuring Cisco PGW 2200 Softswitch Log Files Configuring the Data Dumper 0,1012013100,300,0,"occurrances","ISUP: CHAN MATE UNAVAILABLE","ss7svc4" A comma separates each field. Table A-4 describes the content of each field. Table A-4 Archived Measurement File Fields Field Name Data Type Maximum Length Comments Release level Integer 3 Format of records (should be set to 0).
Appendix A Configuring Cisco PGW 2200 Softswitch Log Files Configuring the Data Dumper Cisco PGW 2200 Softswitch Release 9.
A P P E N D I X B Troubleshooting Cisco ITP-L Signaling Revised: March 7, 2011, OL-0800-14 Cisco ITP-Ls function as signaling link interfaces to Signaling System 7 (SS7) Signal Transfer Point (STP) mated pairs on the SS7 network side. On the network side, Cisco ITP-Ls function as IP interfaces to the Cisco PGW 2200 Softswitches. Several different SS7 messages pass between the Cisco ITP-Ls and STPs. Messages also pass through Cisco switches between the Cisco ITP-Ls and Cisco PGW 2200 Softswitches.
Appendix B Troubleshooting Cisco ITP-L Signaling Cisco ITP-L Signaling Overview Cisco ITP-L Signaling Overview This section contains the following subsections: • IP Signaling Backhaul, page B-2 • Connection Management, page B-3 IP Signaling Backhaul The Cisco PGW 2200 Softswitch and Cisco ITP-L communicate using the Reliable User Datagram Protocol (RUDP) that is proprietary to Cisco to perform IP signaling backhaul.
Appendix B Troubleshooting Cisco ITP-L Signaling Cisco ITP-L Signaling Overview Backhaul Message IDs There are five types of IP signaling backhaul message IDs: • Backhaul reset commands • Connection management commands • Backhaul statistics messages • Flow control • Link status Backhaul Reset There are two types of IP signaling backhaul reset commands: • SoftReset (Link reset)—Command is sent from the Cisco PGW 2200 Softswitch to the Cisco ITP-L to put the backhaul signaling link in the Out-of-
Appendix B Troubleshooting Cisco ITP-L Signaling Cisco ITP-L Signaling Overview The following sections describe connection management: • Backhaul Statistics, page B-4 • Backhaul Congestion, page B-4 • Link Status, page B-5 Backhaul Statistics There are two IP signaling backhaul statistics messages: • Stats request—Cisco PGW 2200 Softswitch sends this command that to the Cisco ITP-L to request the Cisco ITP-L to return its MTP Level 1 (MTP1) and MTP2 statistics. The request is always processed.
Appendix B Troubleshooting Cisco ITP-L Signaling Troubleshooting SS7 Link Problems Link Status Congestion status is maintained for backhaul.
Appendix B Troubleshooting Cisco ITP-L Signaling Troubleshooting SS7 Link Problems Checking UDP Traffic Flows Check User Datagram Protocol (UDP) traffic flows between the Cisco PGW 2200 Softswitch and the Cisco ITP-L by entering the following commands: log on 2600, enable debug ip udp Depending on your configuration, the response should look like the following: 2600-1#debug ip udp UDP packet debugging is on 2600-1# 15:06:53: UDP: rcvd src=10.15.13.6(7000), 15:06:53: UDP: rcvd src=10.15.13.
Appendix B Troubleshooting Cisco ITP-L Signaling Troubleshooting SS7 Link Problems Table B-1 Debug Outputs, Probable Causes, and Recovery Actions Debug Output Probable Cause Recovery Action No output. Link is already aligned. 1. Check that term monitor is on. MTP2 is not started. 2. Reload Cisco ITP-L. 3. Cross-check configuration files.
Appendix B Troubleshooting Cisco ITP-L Signaling Troubleshooting SS7 Link Problems Table B-2 Debug Outputs, Probable Causes, and Recovery Actions (ANSI SS7) Debug Output Probable Cause Recovery Action No output MTP2 is not started. 1. Check that term monitor is on. 2. Reload the Cisco ITP-L. 3. Cross check configuration files. 15:08:31: MTP2 incoming trace enabled on channel 0. 15:08:31: MTP2 outgoing trace enabled on channel 0.
Appendix B Troubleshooting Cisco ITP-L Signaling Troubleshooting SS7 Link Problems Table B-3 Debug Outputs, Probable Causes, and Recovery Actions (ITU SS7) Debug Output Probable Causes Recovery Action No output MTP2 is not started. 1. Check that term monitor is on. 2. Reload the Cisco ITP-L. 3. Cross check configuration files. Nov 14 15:15:13.
Appendix B Troubleshooting Cisco ITP-L Signaling Troubleshooting SS7 Link Problems To check if they match with the Solaris configuration, issue the Solaris ifconfig -a command. File: sigChanDev.
Appendix B Troubleshooting Cisco ITP-L Signaling Troubleshooting Cisco ITP-L-to-STP Signaling Links ip classless ip route 172.18.0.0 255.255.0.0 10.15.13.1 no ip http server ! ss7 set failover-timer 3 ss7 session-0 address 10.15.13.6 7000 10.15.13.
Appendix B Troubleshooting Cisco ITP-L Signaling Troubleshooting Cisco ITP-L-to-STP Signaling Links MTP1 Communication Problems The next two sections describe the procedures for identifying and solving MTP1 communication problems. The initial indication of signaling problems may change in T1 (or E1) status. Check for alarms on the T1 (or E1) interface before performing any of the following procedures. Identifying MTP1 Communication Problems MTP1 standardizes SS7 signaling link physical connectivity.
Appendix B Troubleshooting Cisco ITP-L Signaling Troubleshooting Cisco ITP-L-to-STP Signaling Links Step 4 Test Cisco ITP-L ports and hardware by conducting a loop test of the signal link, excluding connectivity to the distant-end SS7 node and the LAN switch. If the test does not discover an MTP1 problem, the MTP1 problem likely resides within the STP node or the connection to the STP node. Step 5 If the problem is within the Cisco ITP-L, replace the unit.
Appendix B Troubleshooting Cisco ITP-L Signaling Troubleshooting Cisco ITP-L to Cisco PGW 2200 Softswitch Communications Step 3 Test router ports and hardware by conducting a loop test of the signal link, excluding connectivity to the distant-end SS7 node. Step 4 If the test does not discover an MTP2 (link alignment) problem, the problem likely resides within the distant end STP node. If you discover a problem with the Cisco ITP-L, replace the unit.
Appendix B Troubleshooting Cisco ITP-L Signaling Troubleshooting Cisco ITP-L to Cisco PGW 2200 Softswitch Communications Cisco ITP-Ls package received SS7 message data into RUDP datagrams that are transmitted through the LAN switches onto the Cisco PGW 2200 Softswitch. This process is reversed (Cisco ITP-L strips RUDP datagrams) as the Cisco ITP-Ls add standard SS7 message framing when the Cisco PGW 2200 Softswitches send SS7 messages to the Cisco ITP-Ls.
Appendix B Troubleshooting Cisco ITP-L Signaling Troubleshooting Cisco ITP-L to Cisco PGW 2200 Softswitch Communications Identifying IP Communication Problems ITP-L traffic is routed, rerouted, and (if necessary) retransmitted to the Cisco PGW 2200 Softswitches through the LAN switches.
Appendix B Troubleshooting Cisco ITP-L Signaling Cisco ITP-L Error Messages Cisco ITP-L Error Messages Table B-4 lists the Cisco ITP-L error messages that the Cisco PGW 2200 Softswitch broadcasts. Table B-4 Cisco ITP-L Error Messages Message Name Definition Recommended Action OWNERR, PQUICC, LOG_ERR, MSG_TRACEBACK| MSG_PROCESS An internal software error has occurred. Call your technical support representative for a software upgrade for the Cisco ITP-L.
Appendix B Troubleshooting Cisco ITP-L Signaling Cisco ITP-L Error Messages Table B-4 Cisco ITP-L Error Messages (continued) Message Name Definition Recommended Action TOOBIG, PQUICC, LOG_ALERT, 0, "PQUICC(%d/%d), packet too big"; A packet greater than the assigned MTU of this serial interface was queued for transmission. The system should recover. No action is required. If the message recurs, it might indicate an error that is related to data traffic patterns.
A P P E N D I X C Troubleshooting Cisco Switch Signaling Revised: March 7, 2011, OL-0800-14 Deploy two Cisco switches in fault-tolerant, Cisco telephony solutions. Both switches are active. Virtual local-area networks (VLANs) are set up within these switches. System components use these VLANs to route message traffic to other system components. Normally, at least two Cisco SS7 interfaces are connected to each switch for redundancy.
Appendix C Troubleshooting Cisco Switch Signaling Command Line Interface Commands that are entered from the CLI can apply to the entire system or to a specific module, port, or VLAN. Modules (module slots), ports, and VLANs are numbered starting with 1. To reference a specific port on a specific module, the command syntax is mod_num/port_num. For example, 3/1 denotes module 3, port 1. In some commands, such as set trunk, set cam, and set VLAN commands, you can enter lists of ports and VLANs.
Appendix C Troubleshooting Cisco Switch Signaling Troubleshooting Virtual Pathways and ISLs Command Line Interface Remote Access To get remote access to the CLI, complete the following steps: Step 1 From the remote host, enter the Telnet command and designate the name or IP address of the switch you wish to access (Telnet hostname | IP address). Step 2 At the Enter Password: prompt, enter the password for the CLI.
Appendix C Troubleshooting Cisco Switch Signaling Troubleshooting Virtual Pathways and ISLs VLAN AREHops STEHops Backup CRF ---- ------- ------- ---------998 10 10 off Step 3 Enter (for ISLs) the command show trunk.
A P P E N D I X D Cisco PGW 2200 Softswitch Measurements Revised: March 7, 2011, OL-0800-14 This appendix lists the ITU and ANSI measurements that the Cisco PGW 2200 Softswitch can produce. Table D-1 lists the ITU measurements. The logging intervals in this table are all measured in minutes, except for an interval of 24. A logging interval of 24 indicates a 24-hour time period. Table D-2 lists the ANSI ISDN User Part (ISUP) measurements.
Appendix D Table D-1 Cisco PGW 2200 Softswitch Measurements Operational Measurements Supported (continued) MML Counter Group:Name Description CALL-GROUP (continued) Calling statistics CALL: CallBackCallSetup Added in Release 9.7. This counter increments each time the Cisco PGW 2200 Softswitch receives a Call Back Call set up request from DPNSS, QSIG, or EISUP (with tunneled QSIG) interfaces. CALL: CallBackFreeNotification Added in Release 9.7.
Appendix D Table D-1 Cisco PGW 2200 Softswitch Measurements Operational Measurements Supported (continued) Related Components Logging Interval MML Counter Group:Name Description CALL-GROUP (continued) Calling statistics CALL: MessageWaitingIndication Added in Release 9.7. This counter increments each time the Cisco PGW 2200 Softswitch receives a Message Waiting Indication over DPNSS, QSIG, Tunneled QSIG, or SIP.
Appendix D Table D-1 Cisco PGW 2200 Softswitch Measurements Operational Measurements Supported (continued) Related Components Logging Interval MML Counter Group:Name Description CALL-GROUP (continued) Calling statistics CALL: SuccRedirected Number of successful redirected calls that the Cisco PGW 2200 Softswitch initiated CALL: SuccCall TOT Number of successful calls 15, 60, 24 CALL: TDMLicRej TOT Added in Release 9.7. TDM call is rejected due to run-time license management.
Appendix D Cisco PGW 2200 Softswitch Measurements Table D-1 Operational Measurements Supported (continued) MML Counter Group:Name Description ISUP-GROUP ISUP Signaling Service Statistics Related Components Logging Interval SS7 Point Code or SS7 Signaling 5, 30 Number of abnormal clear messages received Service 5, 30 Number of calls that invoked the advice of charge (AOC) feature ISUP: ABN REL TOT ISUP: AOC TOT ISUP: CHAN MATE UNAVAILABLE Number of Channel Mate Unavailable messages received 5, 3
Appendix D Table D-1 Cisco PGW 2200 Softswitch Measurements Operational Measurements Supported (continued) Related Components Logging Interval MML Counter Group:Name Description ISUP-GROUP (continued) ISUP Signaling Service Statistics ISUP: RCV CPG TOT Number of CPG messages received ISUP: RCV CQM TOT Number of CQM messages received SS7 Point Code or SS7 Signaling 5, 30 Service 5, 30 ISUP: RCV CQR TOT Number of CQR messages received 5, 30 ISUP: RCV CRA TOT Number of CRA messages received
Appendix D Table D-1 Cisco PGW 2200 Softswitch Measurements Operational Measurements Supported (continued) Related Components Logging Interval MML Counter Group:Name Description ISUP-GROUP (continued) ISUP Signaling Service Statistics ISUP: RCV REL TOT Number of REL messages received ISUP: RCV RES TOT Number of RES messages received SS7 Point Code or SS7 Signaling 5, 30 Service 5, 30 ISUP: RCV RLC TOT Number of RLC messages received 5, 30 ISUP: RCV RSC TOT Number of RSC messages received
Appendix D Table D-1 Cisco PGW 2200 Softswitch Measurements Operational Measurements Supported (continued) Related Components Logging Interval MML Counter Group:Name Description ISUP-GROUP (continued) ISUP Signaling Service Statistics (continued) ISUP: XMIT CHG TOT Number of CHG messages transmitted ISUP: XMIT CON TOT Number of CON messages transmitted SS7 Point Code or SS7 Signaling 5, 30 Service 5, 30 ISUP: XMIT COT TOT Number of COT messages transmitted 5, 30 ISUP: XMIT CPG TOT Number
Appendix D Cisco PGW 2200 Softswitch Measurements Table D-1 Operational Measurements Supported (continued) Related Components Logging Interval MML Counter Group:Name Description ISUP-GROUP (continued) ISUP Signaling Service Statistics (continued) ISUP: XMIT MPM TOT Number of MPM messages transmitted ISUP: XMIT MSG TOT Total number of messages that are transmitted ISUP: XMIT NRM TOT Number of NRM messages transmitted 5, 30 ISUP: XMIT OPR TOT Number of OPR messages transmitted 5, 30 ISUP:
Appendix D Table D-1 Cisco PGW 2200 Softswitch Measurements Operational Measurements Supported (continued) MML Counter Group:Name Description Related Components IUA GROUP (continued) IUA message statistics Association IUA: ASPDnAckRx Added in Release 9.6. Number of ASP Up Acknowledgement messages that the Cisco PGW 2200 Softswitch received from the media gateway on this SCTP association. 15, 60, 24 IUA: ASPDnTx Added in Release 9.6.
Appendix D Cisco PGW 2200 Softswitch Measurements Table D-1 Operational Measurements Supported (continued) MML Counter Group:Name Description IUA: DataRqt Added in Release 9.6. Number of Data messages that the Cisco PGW 2200 Softswitch sent to the media gateway on this SCTP association. Each message is transmitted by using the Q.921 acknowledged information transfer service. IUA: DataInd IUA: ErrorRx Related Components Logging Interval 15, 60, 24 Added in Release 9.6.
Appendix D Table D-1 Cisco PGW 2200 Softswitch Measurements Operational Measurements Supported (continued) Related Components Logging Interval MML Counter Group:Name Description IUA: UnitDataInd Added in Release 9.6. Number of Data messages that the Cisco PGW 2200 Softswitch received from the media gateway on this SCTP association. Each message is received through the user of the Q.21 unacknowledged information transfer service. 15, 60, 24 IUA: UnitDataRqt Added in Release 9.6.
Appendix D Table D-1 Cisco PGW 2200 Softswitch Measurements Operational Measurements Supported (continued) MML Counter Group:Name Description Related Components M3UA GROUP (continued) M3UA message statistics Association M3UA: AspActAckRx Number of ASP ACTIVE ACK messages received 15, 60, 24 M3UA: ASPActTx Number of ASP ACTIVE messages transmitted 15, 60, 24 M3UA: ASPDnAckRx Number of ASP DOWN acknowledge messages received 15, 60, 24 M3UA: ASPDnTx Number of ASP DOWN messages transmitted
Appendix D Table D-1 Cisco PGW 2200 Softswitch Measurements Operational Measurements Supported (continued) Related Components Logging Interval MML Counter Group:Name Description M3UA: RxProtErr Number of messages that are received with protocol errors, for any protocol anomaly (that is, reception of a parameter that is syntactically correct but unexpected in the current state). 15, 60, 24 M3UA: RxParmFieldErr Number of messages that are received with a parameter having a wrong length field.
Appendix D Cisco PGW 2200 Softswitch Measurements Table D-1 Operational Measurements Supported (continued) MML Counter Group:Name Description Related Components SC-GROUP Signaling link statistics SS7 Link SC: RCV BAD CRC Number of bad CRCs received 15, 60, 24 SC: RCV BAD TOT Total number of bad frames received 15, 60, 24 SC: RCV FRMR Number of bad FRMRs received 15, 60, 24 SC: RCV FRM TOT Total number of frames received 15, 60, 24 SC: RCV RESET Number of RESETs received 15, 60, 24 S
Appendix D Table D-1 Cisco PGW 2200 Softswitch Measurements Operational Measurements Supported (continued) Related Components Logging Interval MML Counter Group:Name Description SCTP: OOTB Added in Release 9.6. Number of out of the blue packets received. 15, 60, 24 SCTP: OrdDataRx Added in Release 9.6. Number of ordered data chunks received. 15, 60, 24 SCTP: OrdDataTx Added in Release 9.6. Number of ordered data chunks sent. 15, 60, 24 SCTP: PeerRestarted Added in Release 9.6.
Appendix D Table D-1 Cisco PGW 2200 Softswitch Measurements Operational Measurements Supported (continued) Related Components Logging Interval MML Counter Group:Name Description SIP: RCV 400 TOT Number of BAD REQUEST messages received 30 SIP: RCV 401 TOT Number of UNAUTHORIZED messages received 30 SIP: RCV 402 TOT Number of PAYMENT REQUIRED messages received 30 SIP: RCV 403 TOT Number of FORBIDDEN messages received 30 SIP: RCV 404 TOT Number of NOT FOUND messages received 30 SIP: RCV
Appendix D Table D-1 Cisco PGW 2200 Softswitch Measurements Operational Measurements Supported (continued) Related Components Logging Interval MML Counter Group:Name Description SIP: RCV 482 TOT Number of LOOP DETECTED messages received 30 SIP: RCV 483 TOT Number of TOO MANY HOPS messages received 30 SIP: RCV 484 TOT Number of ADDRESS INCOMPLETE messages received 30 SIP: RCV 485 TOT Number of AMBIGUOUS messages received 30 SIP: RCV 486 TOT Number of BUSY HERE messages received 30 SIP:
Appendix D Table D-1 Cisco PGW 2200 Softswitch Measurements Operational Measurements Supported (continued) Related Components Logging Interval MML Counter Group:Name Description SIP-GROUP (continued) SIP traffic statistics (continued) SIP: RCV BYE TOT Number of BYE messages received SIP: RCV CAN TOT Number of CANCEL messages received 30 SIP: RCV INVALID MSG TOT Number of invalid messages received 30 SIP: RCV INV TOT Number of INVITE messages received 30 SIP: RCV MSG TOT Number of messa
Appendix D Table D-1 Cisco PGW 2200 Softswitch Measurements Operational Measurements Supported (continued) Related Components Logging Interval MML Counter Group:Name Description SIP-GROUP (continued) SIP traffic statistics (continued) SIP: XMIT 400 TOT Number of BAD REQUEST messages transmitted SIP: XMIT 401 TOT Number of UNAUTHORIZED messages transmitted 30 SIP: XMIT 402 TOT Number of PAYMENT REQUIRED messages transmitted 30 SIP: XMIT 403 TOT Number of FORBIDDEN messages transmitted 30
Appendix D Table D-1 Cisco PGW 2200 Softswitch Measurements Operational Measurements Supported (continued) MML Counter Group:Name Description SIP-GROUP (continued) SIP traffic statistics (continued) SIP: XMIT 485 TOT SIP: XMIT 486 TOT Related Components Cisco PGW 2200 Softswitch Number of AMBIGUOUS messages transmitted Network Element Number of BUSY HERE messages transmitted Logging Interval 30 30 SIP: XMIT 487 TOT Number of REQUEST CANCELLED messages transmitted 30 SIP: XMIT 500 TOT Number
Appendix D Table D-1 Cisco PGW 2200 Softswitch Measurements Operational Measurements Supported (continued) MML Counter Group:Name Description Related Components SIPSP-GROUP SIP sigpath statistics SIP Sigpath SIPSP: BAD URL TOT Number of unresolved URLs 30 SIPSP: DNS CACHE NEW TOT Number of new entries in the DNS cache 30 SIPSP: DNS CACHE PURGE TOT Number of entries that are purged from the DNS cache 30 Number of entries that are refreshed in the DNS cache 30 SIPSP: DNS CACHE REFRESHED T
Appendix D Cisco PGW 2200 Softswitch Measurements Table D-1 Operational Measurements Supported (continued) Related Components Logging Interval MML Counter Group:Name Description STATE-GROUP User Defined Statistics STATE: CDB ReCord Xmit Number of CDBs transmitted STATE: User Count1 User-defined count 1 15, 60, 24 STATE: User Count2 User-defined count 2 15, 60, 24 STATE: User Count3 User-defined count 3 15, 60, 24 STATE: User Count4 User-defined count 4 15, 60, 24 STATE: User Count5
Appendix D Table D-1 Cisco PGW 2200 Softswitch Measurements Operational Measurements Supported (continued) MML Counter Group:Name Description Related Components Logging Interval SUA GROUP SUA message statistics Association SUA: AspActAckRx Number of ASP ACTIVE ACK messages received 15, 60, 24 SUA: ASPActTx Number of ASP ACTIVE messages transmitted 15, 60, 24 SUA: ASPDnAckRx Number of ASP DOWN acknowledge messages received 15, 60, 24 SUA: ASPDnTx Number of ASP DOWN messages transmitted
Appendix D Cisco PGW 2200 Softswitch Measurements Table D-1 Operational Measurements Supported (continued) MML Counter Group:Name Description Related Components SUA GROUP (continued) SUA message statistics Association SUA: RouteCntxErr Number of messages that are received with an invalid (unconfigured) Routing Context. 15, 60, 24 SUA: RxMsgClassErr Number of received messages with an unexpected or unsupported Message Class.
Appendix D Table D-1 Cisco PGW 2200 Softswitch Measurements Operational Measurements Supported (continued) Related Components Logging Interval MML Counter Group:Name Description TCAP-GROUP Transaction Capabilities Application Part statistics TCAP: ABT RCV Number of Abort messages received TCAP: ABT XMIT Number of Abort messages transmitted 5, 30 TCAP: BEGIN RCV Number of Begin messages received. This measurement is valid only for ETSI and ITU TCAP.
Appendix D Cisco PGW 2200 Softswitch Measurements Table D-1 Operational Measurements Supported (continued) Related Components Logging Interval MML Counter Group:Name Description TUP-GROUP Telephone User Part statistics TUP: ABN REL TOT Number of abnormal clear messages received TUP: CHAN MATE UNAVILABLE Number of Channel Mate Unavailable messages received 5, 30 TUP: RCV ACB TOT Number of ACB messages received 5, 30 TUP: RCV ACC TOT Number of ACC messages received 5, 30 TUP: RCV ACF TOT
Appendix D Table D-1 Cisco PGW 2200 Softswitch Measurements Operational Measurements Supported (continued) Related Components Logging Interval MML Counter Group:Name Description TUP-GROUP (continued) Telephone User Part statistics (continued) TUP: RCV GRS TOT Number of GRS messages received TUP: RCV GSE TOT Number of GSE messages received 5, 30 TUP: RCV GSM TOT Number of GSM messages received 5, 30 TUP: RCV HBA TOT Number of HBA messages received 5, 30 TUP: RCV HGB TOT Number of HGB me
Appendix D Table D-1 Cisco PGW 2200 Softswitch Measurements Operational Measurements Supported (continued) Related Components Logging Interval MML Counter Group:Name Description TUP-GROUP (continued) Telephone User Part statistics (continued) TUP: RCV SGU TOT Number of SGU messages received TUP: RCV SLB TOT Number of SLB messages received 5, 30 TUP: RCV SNA TOT Number of SNA messages received 5, 30 TUP: RCV SSB TOT Number of SSB messages received 5, 30 TUP: RCV SST TOT Number of SST me
Appendix D Table D-1 Cisco PGW 2200 Softswitch Measurements Operational Measurements Supported (continued) Related Components Logging Interval MML Counter Group:Name Description TUP-GROUP (continued) Telephone User Part statistics (continued) TUP: XMIT CFL TOT Number of CFL messages transmitted TUP: XMIT CGC TOT Number of CGC messages transmitted 5, 30 TUP: XMIT CHA TOT Number of CHA messages transmitted 5, 30 TUP: XMIT CHG TOT Number of CHG messages transmitted 5, 30 TUP: XMIT CHP TOT
Appendix D Table D-1 Cisco PGW 2200 Softswitch Measurements Operational Measurements Supported (continued) Related Components Logging Interval MML Counter Group:Name Description TUP-GROUP (continued) Telephone User Part statistics (continued) TUP: XMIT MUA TOT Number of MUA messages transmitted TUP: XMIT NNC TOT Number of NNC messages transmitted 5, 30 TUP: XMIT OPR TOT Number of OPR messages transmitted 5, 30 TUP: XMIT RAN TOT Number of RAN messages transmitted 5, 30 TUP: XMIT RLG TOT
Appendix D Cisco PGW 2200 Softswitch Measurements ANSI ISUP Measurements ANSI ISUP Measurements Table D-2 lists the ANSI ISUP measurements that the Cisco PGW 2200 Softswitch can generate.
Appendix D Cisco PGW 2200 Softswitch Measurements ANSI ISUP Measurements Table D-2 ANSI ISUP Measurements ANSI Measurement Name MML Counter Group:Name Description CountReceivedREL ISUP: RCV REL TOT Number of REL messages sent CountReceivedRES ISUP: RCV RES TOT Number of RES messages sent CountReceivedRLC ISUP: RCV RLC TOT Number of RLC messages sent CountReceivedRSC ISUP: RCV RSC TOT Number of RSC messages sent CountReceivedSUS ISUP: RCV SUS TOT Number of SUS messages sent CountReceive
Appendix D Cisco PGW 2200 Softswitch Measurements ANSI ISUP Measurements Table D-2 ANSI ISUP Measurements ANSI Measurement Name MML Counter Group:Name Description CountSentCVT ISUP: XMIT CVT TOT Number of Circuit Validation Test (CVT) messages received CountSentEXM ISUP: XMIT EXM TOT Number of Exit Messages (EXM) received CountSentFAC ISUP: XMIT FAC TOT Number of Facility (FAC) messages received CountSentFOT ISUP: XMIT FOT TOT Number of Forward Transfer (FOT) messages received CountSentG
I N D EX setting A 6-124 media gateway ACC retrieving ACL timer, modifying 3-90 setting alarm associations for ACC MCLs (table) call rejection percentages, managing 3-78 3-77 CANT and skip results matrix (table) setting setting 3-91 setting 3-79 threshold values,retrieving 3-94 using acknowledging 6-5 All Conn Cntl Links Fail resolution 3-85 adding on signaling configurations 6-4 All ISDN BRI IP Conn Fail resolution 3-80 All ISDN IP Conn Fail resolution adding on a call control c
Index ATableFlt_DgtRangeError resolution BLoopCtrExceeded resolution TrunkGrpRsltCtrExceeded resolution 6-13 ANAL/ 6-14 BNum_GetFail_SrvcTbl resolution Rte_TableHopCtrExceeded resolution 6-14 BNum_MdfyBFail_AnnounceID resolution 6-14 6-15 TableFail_CPCTable resolution BTableFail_GetDigTree resolution 6-15 TableFail_PercRouteTable resolution Cause_GetFail_CauseTbl resolution Cause_GetFail_DigModTbl resolution archived, field descriptions (table) 6-17 Cause_GetFail_InvldRsltType resolution
Index INVALID SUA RC resolution 6-45 Invalid Virtual_IP_Addr resolution 6-46 IP CONNECTION FAILED resolution IP RTE CONF FAIL resolution IP RTE FAIL resolution PEER LINK B FAILURE resolution 6-66 LIF: LOST CD resolution DynamicReconfiguration resolution PEER_SYNC_ERR resolution 6-53 6-54 6-49 6-50 SESSION TERMINATE resolution 6-67 PRI:B-Channel not available resolution 6-68 ProcM No Response resolution 6-68 ProtocolFileMissing resolution 6-69 6-51 REPL: all connections failure resoluti
Index Leg2deleteChanUnpackError resolution 3.
Index abnormal termination trace bearer channels, stopping on CICs, stopping on administrative state, retrieving administrative state, setting 6-152 Cisco MGC, stopping on media gateway, stopping on 6-145 signaling service, stopping on 6-146 trunk groups, stopping on 6-145 call trace alternatives starting stopping hung, manually resolving 6-142 6-141 media gateway states (table) 3-17 primary service states (table) 3-16 6-129 6-140 6-131 3-16 3-15 stuck, resolving 4-4 unblocking 6-1
Index configuration data calls, misrouting backup files proper loading, verifying listing provisioning 6-178 restoring verifying 6-179 configuration library 3-24 configuring 3-127 3-26 disk space, verifying amount available 3-127 3-139 3-134 disk monitor continuity test manual 3-135 translation configuration data, viewing 6-178 restoring using mgcrestore script configurations, administering 6-121 3-75 translation, verifying 6-178 restoring from a device managing 6-154 3-18
Index H debug outputs, probable causes, and recovery actions of ANSI SS7 (table) B-8 hardware shutdown error messages (table) Cisco MGC B-17 Ethernet connectivity, identifying problems 2-5 hardware and I/O signaling (figure) B-1 IP communication, identifying problems I IP signaling backhaul managing B-11 memory, verifying amount available 3-91 B-16 B-2 links to STPs, troubleshooting incoming load control B-15 3-22 MTP1 MCL communication problems threshold values modifying identi
Index bouncing, resolving strategy overview 6-101 measurements, retrieving state, changing 6-105 state, retrieving 3-45 3-106 4-1 technical support staff 5-2 measurements archived, field descriptions (table) linksets clearing measurments, retrieving 3-106 A-7 3-106 data dumper, configuring A-2 state, changing 6-105 dumper sink log file parameters (table) state, retrieving 3-45 links or linksets, retrieving local subsystem number See LSSN managing logs not being generated diagno
Index commands ACL timer, modifying displaying information about 3-40 displaying previously entered 3-39 reentering previously entered 3-41 session ending deleting 3-42 3-34 deleting all 3-2 session, starting MML terminal P automatic backup operation 3-39 retrieving active starting 3-80 periodic maintenance procedures 3-42 managing managing 3-90 listing 3-2 3-35 3-36 scheduling 1-7 3-31 backing up system software MTP 3-29 backup history timers settings, verifying 6-107,
Index network, securing managing ACC 6-187 peer, resolving failed connection to properties, rebooting to modify SNMP, diagnosing failure session, ending without activating changes 6-181 session, starting 6-117 replication, verifying configuration software, rebooting to modify configuration parameters 6-183 switchover failure, recovering system time, correcting TIBCO interface regular operations 6-170 bearer channels, managing 6-185 Cisco MGC, provisioning 6-195 3-52 3-64 Cisco MGC platform
Index D-channel, changing state of D-channels, retrieving state of verifying status 3-47 GSR messages, enabling incomplete signaling state information 6-106 3-10 3-9 SIP call information, retrieving 6-99 IP link, changing state of DNS cache, contents, displaying 6-105 IP links, retrieving state of 3-46 DNS cache, managing IP route, changing state of 6-106 DNS cache, purging IP routes, retrieving state of 6-105 links, retrieving state of 3-45 3-60 3-60 3-61 3-60 SIP-to-SIP calls, sto
Index software startup Cisco MGC circuit auditing 3-99 completion, verifying 2-3 spans failover daemon administrative state, retrieving administrative state, setting 3-98 failure, recovering from 3-57 6-170 fault-tolerant components 6-127 SS7 manual, performing understanding links changing the service state 3-97 3-98 3-96 3-97 system measurements 6-105 multiple versions, configuring to support viewing and searching 6-121 network 3-131 system time troubleshooting correcting 6-
Index dial plan translation configuration data, viewing 3-139 U dial plan translation tab window (figure) 3-136 users, verifying the number of 3-21 troubleshooting alarms, using 6-3 bit error rate testers block error rate testers breakout boxes cable testers V 4-10 4-10 viewer toolkit 4-10 measurement viewer 4-9 virtual memory, verifying available amount configuration export failure debug commands 6-180 4-9 4-10 general problem-solving model (figure) ITP-L diagnostic commands network a
Index Cisco PGW 2200 Softswitch Release 9.
