Table Of Contents

VXSM Trouble Shooting

Collecting Trouble Shooting Data

Trouble Shooting Procedures

Getting Information on Current Voice Calls (H.248)

Examples

Getting Information on Current Voice Calls (TGCP)

Other Useful Trouble Shooting Commands

VXSM Trouble Shooting

---

This chapter describes how to trouble shoot and resolve known types of problems on the Cisco MGX 8850 VXSM card. The following topics are covered in this chapter:

•Collecting Trouble Shooting Data

•Trouble Shooting Procedures

•Getting Information on Current Voice Calls (H.248)

•Getting Information on Current Voice Calls (TGCP)

•Other Useful Trouble Shooting Commands

Collecting Trouble Shooting Data

This section provides procedures for collecting trouble shooting data for when a VXSM card fails. These procedures use PXM45, VXSM, RPM-XF and AXSM commands. See Chapter 5, "VXSM CLI Commands" in this document for detailed descriptions of the VXSM CLI commands. Refer to the following documents for descriptions of the PXM45, RPM-XF and AXSM CLI commands:

•Cisco MGX 8850 (PXM1E/PXM45), MGX 8950, and MGX 8830 Command Reference, Release 4.

•Cisco ATM Services (AXSM) Software Configuration Guide and Command Reference for MGX Switches, Release 4

•Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4

Table 9-1 shows the initial steps you can take using CLI commands to trouble shoot any problem on the VXSM. These steps enable you to collect data and failure reports.

Table 9-1 Initial Trouble Shooting Steps Using CLI Commands 

Run these CLI commands on the PXM45:

1. dspcds

2. dspcd

3. dsplog

4. dsperr

5. dspversion

6. dsprev

7. dspclksrc

Run these CLI commands on the VXSM:

1. dspcd

2. dspversion

Trouble Shooting Procedures

Table 9-2 provides a list of known types of problems, their possible causes, and their possible solutions. The problems are listed alphabetically by topic.

Table 9-2 VXSM Trouble Shooting Procedures 

Problem	Possible Cause	Possible Solutions
Access to Card— Cannot use the cc command to access VXSM card.	VSXM card is not in the active or standby state. If the VSXM card is not in the active or standby state, you cannot use the cc command to access the card.	Verify that the VXSM card is in either the active or standby state, by issuing the PXM45 CLI command, dspcds. See Possible Solutions for "Active Card—VXSM card did not become active".
Active Card— VXSM card did not become active.	VXSM card was inserted into the wrong slot. Slot 7, 8, 15 and 16 are reserved for other service modules.	Remove the VXSM card. Verify that the pins on the backplane are not bent and the power key is intact. Attempt to insert the VXSM card into a slot that is not reserved.
	PXM45 and VXSM run time images are not compatible	Check the latest Cisco MGX8850 Release Notes and make sure that the PXM45 and VXSM images are current and are compatible. If they are not, update the VXSM boot image and runtime image by issuing the following PXM45 CLI commands: 1. burnboot 2. setrev
	VXSM runtime image is not available from the PXM45 hard drive or is corrupted.	Download the correct VXSM image to PXM45-HD. Use the PXM45 dsprevs CLI command in order to verify that the image file name and size are correct. Then, issue the clrsmcnf command and the setrev command to clear and reload the correct image.
	The setrev command was not executed for the VXSM card.	Issue the PXM45 CLI command, setrev.
	The VXSM card is inserted in a slot that was previously configured for a different card type and the slot is still in the Reserved state.	Insert the VXSM card into a different slot or issue the clrsmcnf CLI command.
Alarm— PVC is in alarm.	The OC3 cable is bad, does not exist, or is not connected properly.	1. Check for alarms on the AXSM line associated with the VXSM PVC using the dsplns and dsplnalm CLI commands. 2. On the AXSM, issue the addlnloop command with the option for local loopback set. 3. Check whether the alarm is cleared using the dspcons command. 4. If the alarm is cleared, check the TX/RX connections between the AXSM and the router's ATM interface. 5. If the TX/RX connections are correct, replace the OC3 cable.
	The router's ATM interface is not configured.	On the router, issue the IOS command, show run, to verify whether the VPI/VCI and traffic parameters are correct. If necessary, reconfigure the VPI/VCI and traffic parameters.
	The PVC has been added on the VXSM, but not on the AXSM, or vice versa.	Verify that the PVC has been added on both cards by issuing the dspcons command on both the VXSM and the AXSM. If necessary, add the connection, using the addcon command.
CA-Initiated Commands Ignored	An association does not exist between the CA and the VXSM.	Display the H.248 association state using the dsph248state CLI command (or SNMP equivalent).
VXSM is Rejecting Call Attempts
	TDM/SCN termination does not exist.	Display the VIFs (Voice Interfaces) using the dspvifs CLI command (or SNMP equivalent). If the VIF corresponding to the TDM/SCN termination does not exist, it must be added using the addvif CLI command (or SNMP equivalent).
	H.248 packages not associated with VIF.	Display the VIFs (Voice Interfaces) using the dspvifs CLI command (or SNMP equivalent). Verify that the appropriate H.248 packages have been added corresponding to the VIFs. H.248 packages can be added using cnfvifterm CLI command (or SNMP equivalent).
	Inadequate resources (CPU, memory, message queues, ...).	Display the system resources using the following CLI commands, •dspconcacs •dspcrr •dspcpursc •dspmemrsc •dsprpcrsc •dspmsgqrsc
	A H.248 Add TDM termination command from the CA may be rejected if the TDM termination is already associated with a (non-null) context.	The CA should attempt to clean-up the orphaned TDM termination. In the event that the CA is not able to subtract the orphaned termination, the cnfh248oos CLI command (or SNMP equivalent) can be used to forcefully subtract ALL of the terminations (and calls) on the VXSM. This should be used as a second-to-last resort. In the event that the cnfh248oos CLI command won't subtract the termination, the card will need to be reset.
	The CA port has not been provisioned on the VXSM.	The CA port can be provisioned using the addmgcgrpmgc CLI command (or SNMP equivalent).
Echo— Echo is present in voice call.	Echo cancellation (ECAN) is either not enabled or is not configured properly.	Ensure that the ECAN feature is enabled.
Fail— dspcds command output on the PXM shows VXSM card as failed.	VXSM card is in the initial boot process.	Use the PXM45 CLI dspcds command in order to monitor the boot process and card bring-up. Allow time for the boot process to complete.
	VXSM boot flash or configuration file is corrupted.	Capture the output of the PXM45 dsplog -sl CLI command.Capture the console output. Issue the PXM45 CLI command clrsmcnf with the option all to clear the configuration for the slot. If the problem persists, contact Cisco Systems, Inc.
	VXSM slot is configured for another service module	Physically reset the VXSM card or move it to another slot. Issue the PXM45 CLI command, clrsmcnf with the option all to clear configuration for the slot.
Firmware— Firmware does not download to VXSM card.	VXSM card is not present or is not seated properly.	Make sure that the VXSM card is seated properly in the slot so that the top and bottom portions of card are making electrical contact with back plane.
	VSXM card is not in the active state or the standby state.	Verify that the VXSM card is in either the active or standby state, by issuing the PXM45 dspcds CLI command. Check for a card state of Boot/Init or Failed. Perform the PXM45 dsprevs CLI command to verify that the proper firmware image resides on the PXM. See Possible Solutions for "Active Card—VXSM card did not become active".
	VXSM card or MGX slot is defective.	Attempt to insert the VXSM card into another slot. If the problem persists, contact Cisco Systems, Inc.
LEDs— All VXSM front panel LEDs are off.	Card is not seated properly in the slot.	Make sure that the VXSM card is seated properly in the slot so that the top and bottom portions of card are making electrical contact with back plane.
Mismatch— Front card, back card mismatch.	Configuration mismatch	Use the dspcds, dspcd and dsplog CLI commands to identify the configuration mismatch.
Mismatch— T1/E1 mismatch.	Configuration mismatch	Issue the PXM45 dspcds and dspsmcnf CLI commands to identify a configuration mismatch. After the slot is identified, issue the PXM45 dsplog CLI command to show the card mismatch log entry.
Ping— Card does not respond to ping from router.	PVC connection is not established between VXSM and AXSM/RPM-XF.	Verifying that the physical connection between the AXSM and the router's ATM interface is properly connected. Verify that the LEDs for the ATM interface and the VXSM interface are green. Verify that the TX/RX cables are not crossed.
	PVC connection is in fail or alarm status.	Verify the alarm status by issuing the PXM45 dspcons or dspalms commands.
	The router's ATM interface is not configured.	From the router, issue the IOS show atm pvc and show run commands to verify that the ATM PVC status is up and that the VPI/VCI, traffic parameters and the IP address are configured properly.
	The IP address is incorrect.	From VXSM and AXSM, issue the PXM45 CLI command dspcons to verify that the VPI/VCI for the PVC between the VXSM and AXSM is correct. Issue the PXM45 dspconips CLI command and the IOS route show command to verify that the IP address and netmask for the PVC are correct.
	An IP address has not been provisioned corresponding to the AAL5 bearer PVC.	Issue the VXSM addipcon CLI command.
Resets— Card constantly reboots-becomes active and then resets again.	The MGX switch is fully loaded and the power is reaching its shut off threshold.	Issue the PXM45 dspenvalms and dspndalms CLI commands to see if the power and temperature for the shelf and the card are within acceptable limits. If the problem persists, contact Cisco Systems, Inc.
	VXSM card is getting too hot due to poor air circulation
	The MGX fans are not functioning.
Resets— Card resets occasionally.	Too many calls are made while a debugging command is enabled.	Minimize the number of calls when debugging is enabled, reduce the trace level in order to minimize the number of trace messages or turn off debugging altogether.
Slot— VXSM card is in place, but the dspcds command on the PXM shows that the slot is empty.	The pins on the back plane are bent or a power key is missing.	Remove the VXSM from the slot and observe the back panel to make sure that the pins on that slot are not bent and that the power key (the orange or yellow plastic cap in the center of the slot) exists. Insert the VXSM card into another slot. If the problem persists, contact Cisco Systems.

Getting Information on Current Voice Calls (H.248)

With H.248, calls are modeled using a "context". A context contains one or more "terminations". In Release 5, a context can contain at most two terminations.In this release, there are two types of terminations: TDM (also referred to as SCN or Switched Circuit Network); and RTP.

A basic VoIP call "leg" is modeled as a context containing one TDM termination and one RTP termination.

Figure 9-1 VoIP Call Leg Model

.

A TDM hairpin call is modeled as a context containing two TDM terminations.

Figure 9-2 TDM Hairpin Model

Table 9-3 shows the commands used to get information about the current voice calls on the VXSM.

Table 9-3 How to Display Current Voice Calls on the VXSM 

Step	CLI Commands
1. Display all of the H.248 terminations on the VXSM card.	dsph248calls
2. Display the status of all the H.248 contexts on the VXSM card.	dsph248status -cntxs
3. Display the status of a particular H.248 context on the VXSM card.	dsph248status -cntx <context ID>
4. Display the status of a particular H.248 TDM/SCN termination on the VXSM card.	dsph248status -term 1 1 <term_id> dsph248status -term 1 2 <term_name> dsph248status -term 1 3 <oc3> <ds1> <ds0>
5. Display the status of a particular H.248 RTP termination on the VXSM card.	dsph248status -term 3 1 <term_id> dsph248status -term 3 2 <term_name>
6. Display information pertaining to all of the H.248 associations on the VXSM card.	dsph248status -assoc
7. Display information pertaining to a particular H.248 termination on the VXSM card.	dsph248call -term
8. Display counters corresponding to all of the H.248 physical (TDM/SCN) terminations on the VXSM card.	dsph248cnts -phyterm
9. Display H.248 command counters.	dsph248cnt -cmd <association>
10. Display counters pertaining to a particular H.248 physical (TDM/SCN) termination on the VXSM card.	dsph248cnt -phyterm 1 <bay.line.path.vtg/ds3.vt/ds1:ds0>
11. Display information regarding all of the H.248 contexts.	dsph248cnt -cntx <association>
12. Display counters pertaining to all H.248 ephemeral (RTP, ...) terminations on the VXSM card.	dsph248cnt -ephterm
13. Display counters pertaining to a particular H.248 association.	dsph248cnt -assoc <association>

Examples

The dsph248calls CLI command displays all of the H.248 terminations,

shelf.1.VXSM.a > dsph248calls

TermId TermType Media Codec Vad Ecan

------ -------- -------- ----- ----- ----

1 SCN 'Voice' 'G.711 U' ----- 'Enabled'

8067 RTP 'Voice' 'G.711 U' 'Enabled' -----

2 SCN 'Voice' 'G.711 U' ----- 'Enabled'

8068 RTP 'Voice' 'G.711 U' 'Enabled' -----

The dsph248status -cntxs CLI command displays the status of all H.248 contexts,

shelf.1.VXSM.a > dsph248status -cntxs

=======================================

Status for all contexts

=======================================

Number of active contexts:2

List of contexts

Status of context 4:

Creation date and time:02/03/2004, 17:31:21

Number of terminations in context:2

List of termination IDs:

8068 2

Status of context 3:

Creation date and time:02/03/2004, 17:31:21

Number of terminations in context:2

List of termination IDs:

8067 1

The dsph248status -cntx CLI command displays the status of a particular H.248 context,

shelf.1.VXSM.a > dsph248status -cntx 1

=======================================

Status of context 1

=======================================

Creation date and time: 07/04/2003, 13:55:45

Number of terminations in context: 2

List of terminations:

term_id: 8065, term_type: MG_TERM_TYPE_PDN_IP, term_name: RTP8065

term_id: 3, term_type: MG_TERM_TYPE_SCN, term_name: ds/1/1/3

The dsph248status -term CLI command displays the status of a particular H.248 termination,

shelf.1.VXSM.a > dsph248status -term 1 1 1

==========================================

Status of termination with ID 1

==========================================

Termination type:MG_TERM_TYPE_SCN

Termination name:ds/1/1/1

Termination state:MG_TERM_STATE_INSERVICE

Termination test flag:False

Termination context id:3

Id of profile on termination:0

Number of streams on termination:1

Termination about to be deleted:False

Next state of termination:MG_NEXT_STATE_INSERVICE

Last modified/updated:02/03/2004, 17:31:21

NOTE:This timestamp is not preserved across switchovers.

It is independently generated on each card.

Supported packages:

H248_GENERIC_PKG H248_TDMC_PKG

The dsph248call -term CLI command displays information pertaining to a particular H.248 termination,

shelf.1.VXSM.a > dsph248call -term 1

Term Id :1

Term Type :SCN

Term Name :ds/1/1/1

connMode :4 ('Send-recv')

loopBackType :1 ('None')

RTP Encapsulation Parameters ...

ssrc :424285698 (0x194a1602)

RTCP Enable :TRUE

dspCodec :2 ('G.711 U')

packetPeriod :'20 ms'

vadMode :2 ('Enabled')

vadThreshold :-38

vadHangoverTime :250 ms

ecan enabled :'Enabled'

ecanTail :128 ms

ecanFlags :0x0

Type <CR> to continue, Q<CR> to stop:

upspeedCodec :2 ('G.711 U')

jitterMode :2 ('Adaptive')

jitterMinDelay :5 ms

jitterMaxDelay :100 ms

jitterNomDelay :30 ms

jitterFaxNomDelay :0 ms

txGain :0

rxGain :0

nsePayloadType :100 (0x64)

nteTxPayloadType :0 (0x0)

nteRxPayloadType :0 (0x0)

profileType :0

profileNum :0

hsRedCount :0

lsRedCount :0

toneDetect :0x3c32

toneDetectBitmap :0x0

Type <CR> to continue, Q<CR> to stop:

digitDetect :1 ('DTMF')

digitRelayMethod :1 ('Send as Voice')

icsEnable :0 (FALSE)

nx64FramePattern :0 (CRML_PATTERN_NONE)

trunkMode :0 (CRML_MODE_NONE)

nx64FrameFlagCnt :0

dtmfTransport :0 (FALSE)

trunkCond :0 (FALSE)

The dsph248cnts -phyterm CLI command displays counters corresponding to all of the H.248 physical (TDM/SCN) terminations on the VXSM card,

shelf.1.VXSM.a > dsph248cnts -phyterm

=================================================================

All Gateway Physical Terminations Statistic

DS1:DS0 Termination Termination Num of Num of Num of OOS Num of OOS

line Id Name Add Failure from MGC from OAM

============ =========== ============ ====== ======= ==========

1.1.1.2.3:1 361 DS/1/16/1 1 0 0 0

1.1.1.2.3:2 362 DS/1/16/2 0 0 0 0

......

1.1.1.2.3:23 383 DS/1/16/23 0 0 0 0

1.1.1.2.3:24 384 DS/1/16/24 1 0 0 0

The dsph248cnt -ephterm CLI command displays counters corresponding to all of the H.248 ephemeral (RTP, ...) terminations on the VXSM card,

shelf.1.VXSM.a > dsph248cnt -ephterm

=========================================================

Gateway Ephemeral Terminations Statistic

=========================================================

Num of Add Commands : 2

Num of Commands Failure : 0

Getting Information on Current Voice Calls (TGCP)

The TGCP call model is based upon endpoints and connections. Connections have modes. Supported modes include Receive-Only, Send/Receive, Inactive, Loopback, and Continuity Test. The connection model is shown in Figure 9-3.

Figure 9-3 TGCP Connection Model

To obtain information regarding the status of TGCP activities. use the PXM and VXSM commands as follows/

The following PXM CLI commands will display the list of events and errors logged by the active and standby VXSM cards, starting with the most recent event or error.

Table 9-4 Useful PXM CLI Commands for Trouble Shooting the VXSM 

Command	Description
dsperr -sl <primary slot>	Displays the error for a primary VXSM.
dsperr -sl <secondary slot>	Displays the error for a secondary VXSM.
dsplog -sl <primary slot>	Displays the log for a primary VXSM.
dsplog -sl <secondary slot>	Displays the log for a secondary VXSM.

The following VXSM CLI commands are useful to monitor the basic operation of the currently active VXSM card and to check if calls are being processed after switchover:

Table 9-5 Useful VXSM CLI Commands for Trouble Shooting the VXSM 

Command	Description
dspxgcpcnts	Displays xgcp command counts.
dspxgcpdetailcnts	Displays xgcp details.
dspxgcpendpts	Displays xgcp endpoints.
dspxgcpendptcons	Dispaly xgcp endpoint connections

dspxgcpcnts - displays a static summary of the number of TGCP commands that failed/succeeded on the ACTV card at that moment; executing this command a few times will give the user an idea whether commands are being sent to the VXSM and whether VXSM is processing those commands

dspxgcpdetailcnts - displays number of times a particular TGCP command is received/sent/retransmitted

dspxgcpendpts <endpt-name> - displays all the endpt state, if connection is present on that endpoint.

`dspxgcpendpts *' can be used to display all

-dspxgcpendptcons <endpt-name> - displays the connection id, call id of the connection on that endpoint

Other Useful Trouble Shooting Commands

Table 9-6 gives a list and descriptions of other CLI commands that can be useful in trouble shooting the VXSM.

Table 9-6 List of Other Useful Commands for Trouble Shooting the VXSM 

Command	Description
dspcputhreshold	Displays data about the current CPU utilization.
dsplog	Displays the log file that lists the current errors on the switch.
dsperr	Displays the error for a specific slot.
addlnloop	Enables a local line loopback.
dellnloop	Disables a local line loopback.
cnfbert	Configures a bit error rate test.
addendptloop	Enables a DS0 loopback on a DS0-by-DS0 basis.
delendptloop	Disables a DS0 loopback.
addconloop	Enables a VC remote loopback.
delconloop	Disables a VC remote loopback.