cc/td/doc/product/wanbu/mgx8850/vism32
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Troubleshooting Tips

VISM Card LEDs

VISM and PXM Display, Log, and Diagnostic Loopback Path CLI Commands

VISM Display Card CLI Command

PXM Display Log CLI Command

PXM Diagnostic Loopback Path CLI Commands

PXM1E and PXM 45 Display CLI Commands

VISM Alarms

UNIX Snoop Trace Tool

Symptoms and Solutions

VISM Card Did Not Become Active

T1/E1 Configuration Mismatch

DSP Download Failure

VISM Front Card/Back Card Mismatch

Cannot Use the cc Command to Access a VISM Card

VISM Card Resets Intermittently

VISM Card Does Not Accept a Firmware Download

Echo Is Heard on a Voice Call

VISM Card LEDs Are Not Lighted

Firmware Does Not See the Card Insert Bit Status As Set

Troubleshooting Tips

Use the following troubleshooting tools and techniques to assist you in maintaining your VISM card:

• "VISM Card LEDs" section

• "VISM and PXM Display, Log, and Diagnostic Loopback Path CLI Commands" section

• "VISM Alarms" section

• "UNIX Snoop Trace Tool" section

• "Symptoms and Solutions" section

VISM Card LEDs

The VISM card uses the following three card status LEDs (see Figure 8-1) to indicate certain states:

•ACT—Green indicates the active state.

•STBY—Orange, or blinking orange, indicates one of the following:

–VISM is in the standby state.

–VISM is in the mismatch state.

–VISM card DSPs are currently involved in the VISM card bootup.

•FAIL—Red indicates the failure state, or certain stages of the bootup process.

The VISM card uses eight line status LEDs (see Figure 8-1) to indicate the following states of the eight T1 or E1 ports on the VISM back card:

•Green—A line has been added and there is no alarm on that line.

•Orange—A line has been added and there is a yellow alarm condition on the line.

•Red—A line has been added and there is one of the following conditions on the line:

–Loss of signal (LOS) (red alarm condition)

–Loss of frame (LOF)

–Alarm indication signal (AIS)

Figure 8-1 VISM Front Card LEDs

VISM and PXM Display, Log, and Diagnostic Loopback Path CLI Commands

You can use the following commands to troubleshoot your VISM card:

•The VISM dspcd command

•The PXM dsplog command

•PXM diagnostic loopback commands

Note Refer to the Cisco MGX 8000 Series platform command reference guides for more information on PXM commands.

VISM Display Card CLI Command

Use the VISM dspcd command to display the following types of information about your current VISM card:

•State of the VISM card

•Type of VISM card

•Version number and part numbers

•Daughter card version numbers and part numbers

The following example shows the results of a typical dspcd command:

NODENAME.1.3.VISM8.a > dspcd ModuleSlotNumber: 17 FunctionModuleState: Active FunctionModuleType: VISM-8T1 FunctionModuleSerialNum: SAK0331006P FunctionModuleHWRev: 0.0 FunctionModuleFWRev: 2.0.0_11Nov01_2 FunctionModuleResetReason: ? LineModuleType: LM-RJ48-8T1 LineModuleState: Present mibVersionNumber: 21 configChangeTypeBitMap: CardCnfChng, LineCnfChng pcb part no - (800 level): 800-04399-01 pcb part no - (73 level): 73-03618-01 Fab Part no - (28 level): 28-02791-01 PCB Revision: 08

Daughter Card Information: Daughter Card Serial Number: SAK0331003P pcb part no - (73 level): 73-03722-01 Fab Part no - (28 level): 28-02905-01 PCB Revision: 04

PXM Display Log CLI Command

Use the PXM dsplog command to display useful information for troubleshooting your VISM card. The log is maintained by the PXM. A VISM entry is displayed in the log in the following format:

•Date and time of the log

•Slot number of the VISM card from which a message is logged

•The process on the VISM card that logged that message

•Severity of the message:

–1 = Fatal error which causes the card to reboot

–6 = All other errors

•A log message description

The following example shows the results of a typical dsplog command:

09/09/2001-02:09:01 03 cam VISM-6-9157 VISM got time from PXM

PXM Diagnostic Loopback Path CLI Commands

The VISM-8T1 and VISM-8E1 cards provide the capability for creating loopback paths for diagnostic purposes. Use the VISM and PXM diagnostic loopback CLI commands to troubleshoot your VISM cards. The following loopback configurations are possible:

•Local line loopback. Use the PXM addlnloop command to enable local line loopback on a line-by-line basis. Use the PXM dellnloop command to disable local line loopback.

•Remote line loopback. The PXM cnfbert command is a T1/E1 diagnostic test package which includes some loopback tests.

Use the BERT and loopback functions to test the integrity of T1 and E1 lines. You can use the PXM cnfbert command on the PXM to perform the following actions:

–Run BERT on a per-line basis on the VISM card.

–Put a VISM line on a TDM side loopback.

–Put a VISM line on a network side loopback.

–Cause the VISM to put test equipment residing on the far side into loopback.

•OAM loopback through the CPU toward the network (per VC). This loopback is enabled automatically; no PXM or VISM CLI commands are required.

•DS0 loopback, at the compression DSP toward the TDM side. Use the PXM addendptloop command to enable DS0 loopback on a DS0-by-DS0 basis. Use the PXM delendptloop command to disable DS0 loopbacks.

•VC remote loopback. Use the PXM addconloop command to enable VC remote loopbacks. Use the PXM delconloop command to disable remote loopbacks.

PXM1E and PXM 45 Display CLI Commands

Refer to the Cisco MGX 8830, MGX 8850 (PXM45 and PXM1E), and Cisco MGX 8950 Command Reference, Release 4 for information on the following PXM1, PXM1E, and PXM45 card display commands.

VISM Alarms

Table 8-1 describes VISM T1 and E1 card alarms.

Table 8-1 VISM T1 and E1 Card Alarms 

Error
Alarm Type
Down stream (ATM side)
Up Stream (TDM side)
Comments

Link Failure—receive LOS 1

LOS1

AIS2

RAI3

RAI 3 returned on the transmit line.

Receive RAI 3

Yellow

RAI 3

None

—

Receive LOF4

—

AIS 2

RAI 3

RAI 3 returned on the transmit line.

Receive AIS 2

AIS 2

AIS 2

RAI 3

RAI 3 returned on the transmit line.

1 LOS = Loss of service.

2 AIS = Alarm indication signal.

3 RAI = Remote alarm indicator.

4 LOF = Loss of frame.


Refer to T1.403 for DS1 and G.704 for E1 definitions of alarm states. Alarms are propagated to the remote end over the ATM network in accordance with ATM specifications.

UNIX Snoop Trace Tool

Use the UNIX snoop trace tool to assist in diagnosing a problem. The snoop command can determine if there is any activity between the VISM and the call agent. The following example shows the command and a typical resulting terminal display:

snoop -x 42 -ta <ip address of CA> port <udp port of CA> E.g snoop -x 42 -ta vismvsc1 port 2427

Symptoms and Solutions

This section includes possible solutions to the following possible symptoms:

• "VISM Card Did Not Become Active" section

• "T1/E1 Configuration Mismatch" section

• "DSP Download Failure" section

• "VISM Front Card/Back Card Mismatch" section

• "Cannot Use the cc Command to Access a VISM Card" section

• "VISM Card Resets Intermittently" section

• "VISM Card Does Not Accept a Firmware Download" section

• "Echo Is Heard on a Voice Call" section

• "VISM Card LEDs Are Not Lighted" section

VISM Card Did Not Become Active

Investigate the following possible causes for a VISM card that does not become active:

•An E1 card is inserted in a slot where a T1 card was present, or a T1 card is inserted in a slot where an E1 card was present, resulting in configuration mismatch.

•The minimum number (five) of DSPs failed to download.

•A front card type does not match the back card type—if the front card is T1 and the back card is E1, or the front card is E1 and the back card is T1.

•The VISM card MIB image version does not match the PXM disk MIB image version.

T1/E1 Configuration Mismatch

Use the PXM dspcds command to identify a T1/E1 configuration mismatch, as follows:

NODENAME.1.7.PXM.a > dspcds Slot CardState CardType CardAlarm Redundancy ---- ----------- -------- --------- ----------- 1.1 Empty Clear 1.2 Empty Clear 1.3 Empty Clear 1.4 Empty Clear 1.5 Mismatch VISM-8E1 Clear 1.6 Empty Clear 1.7 Active PXM1-OC3 Clear 1.8 Empty Clear 1.9 Empty Clear 1.10 Empty Clear 1.11 Empty Clear 1.12 Empty Clear 1.13 Empty Clear 1.14 Empty Clear 1.15 Empty Clear 1.16 Empty Clear 1.17 Empty Clear 1.18 Empty Clear 1.19 Empty Clear

Use the PXM dspsmcnf command to identify a T1/E1 configuration mismatch, as follows:

NODENAME.1.7.PXM.a > dspsmcnf slot Card Rate Channel MIB Feature No. Type Control ized IMA MULTRKS Version Bits ------ ---------- ------- ------- ------- ------- ------- ------- 1 ------> No configuration file exist for this slot <------ 2 ------> No configuration file exist for this slot <------ 3 VISM-8T1 Off Off Off Off 20 0x0 4 ------> No configuration file exist for this slot <------ 5 VISM-8T1 Off Off Off Off 20 0x0 6 ------> No configuration file exist for this slot <------ 9 ------> No configuration file exist for this slot <------ 10 ------> No configuration file exist for this slot <------ 11 ------> No configuration file exist for this slot <------ 12 ------> No configuration file exist for this slot <------ 13 ------> No configuration file exist for this slot <------ 14 ------> No configuration file exist for this slot <------ 17 ------> No configuration file exist for this slot <------ 18 ------> No configuration file exist for this slot <------ 19 ------> No configuration file exist for this slot <------ 20 ------> No configuration file exist for this slot <------ 21 ------> No configuration file exist for this slot <------ 22 ------> No configuration file exist for this slot <------ 25 ------> No configuration file exist for this slot <------ 26 ------> No configuration file exist for this slot <------ 27 ------> No configuration file exist for this slot <------ 28 ------> No configuration file exist for this slot <------ 29 ------> No configuration file exist for this slot <------ 30 ------> No configuration file exist for this slot <------

Use the PXM dsplog command to show a card mismatch log entry, logged by VISM card on slot 5, as follows:

09/09/2001-00:01:47 05 dsplog VISM-6-9025 VISM going to standby : Config. Mismatch between PXM and VISM

Use the VISM dspcd command to display the following information:

NODENAME.1.5.VISM8.s > dspcd ModuleSlotNumber: 5 FunctionModuleState: Mismatch FunctionModuleType: VISM-8E1 FunctionModuleSerialNum: CAB12345678 FunctionModuleHWRev: 0.13 FunctionModuleFWRev: 2.2.10g.pm FunctionModuleResetReason: WatchDog timeout reset LineModuleType: Missing LineModuleState: Not Present mibVersionNumber: 20 configChangeTypeBitMap: CardCnfChng, LineCnfChng cardIntegratedAlarm: Clear pcb part no - (800 level): 800-03530-01 pcb part no - (73 level): 73-03021-01 Fab Part no - (28 level): 28-02492-01 PCB Revision: 01 Daughter Card Information: Daughter Card Serial Number: CAB12345678 pcb part no - (73 level): 73-03022-01 Fab Part no - (28 level): 28-02493-01 PCB Revision: 01 value = 34 = 0x22 = '"'

DSP Download Failure

Use the PXM dsplog command to determine if the minimum number (five) of the DSPs failed to download. The terminal displays results similar to the following:

NODENAME.1.7.PXM.a > dsplog 01/01/2001-00:02:10 05 tDspmDl VISM-6-9193 DSPM task errors : 6 DSPs failed to download

If the number of DSPs (six in the above case) is greater than five, the card will fail to be in the active state. If this condition happens repeatedly, replace the card.

Use the following PXM dspcds command, and the results, to determine the current state of VISM DSPs:

NODENAME.1.7.PXM.a > dspcds Slot CardState CardType CardAlarm Redundancy ---- ----------- -------- --------- ----------- 1.1 Empty Clear 1.2 Empty Clear 1.3 Empty Clear 1.4 Empty Clear 1.5 Failed VISM-8E1 Clear 1.6 Empty Clear 1.7 Active PXM1-OC3 Clear 1.8 Empty Clear 1.9 Empty Clear 1.10 Empty Clear 1.11 Empty Clear 1.12 Empty Clear 1.13 Empty Clear 1.14 Empty Clear 1.15 Empty Clear 1.16 Empty Clear 1.17 Empty Clear 1.18 Empty Clear 1.19 Empty Clear

VISM Front Card/Back Card Mismatch

Use the following PXM dsplog command to investigate a possible VISM front card/back card mismatch:

NODENAME.1.7.PXM.a > dsplog 01/01/2001-00:02:24 05 cmm VISM-6-9025 VISM going to standby : Config. Mismatch between ASC and VISMV 01/01/2001-00:02:24 05 cmm VISM-6-9023 Mismatch Backcard 01/01/2001-00:02:24 05 cmm VISM-6-9023 Mismatch Backcard

In a mismatch condition, use the PXM dspcds command to display the following type of information:

NODENAME.1.7.PXM.a > dspcds Slot CardState CardType CardAlarm Redundancy ---- ----------- -------- --------- ----------- 1.1 Empty Clear 1.2 Empty Clear 1.3 Empty Clear 1.4 Empty Clear 1.5 Mismatch VISM-8E1 Clear 1.6 Empty Clear 1.7 Active PXM1-OC3 Clear 1.8 Empty Clear 1.9 Empty Clear 1.10 Empty Clear 1.11 Empty Clear 1.12 Empty Clear 1.13 Empty Clear 1.14 Empty Clear 1.15 Empty Clear 1.16 Empty Clear 1.17 Empty Clear 1.18 Empty Clear 1.19 Empty Clear

Use the VISM dspcd command to display the following types of information:

NODENAME.1.5.VISM8.s > dspcd ModuleSlotNumber: 5 FunctionModuleState: Mismatch FunctionModuleType: VISM-8E1 FunctionModuleSerialNum: CAB0246014P FunctionModuleHWRev: 0.0 FunctionModuleFWRev: 2.2.10g.pm FunctionModuleResetReason: Reset by ASC from Cell Bus LineModuleType: LM-RJ48-8T1 LineModuleState: Invalid mibVersionNumber: 20 configChangeTypeBitMap: CardCnfChng, LineCnfChng cardIntegratedAlarm: Clear pcb part no - (800 level): 800-04399-01 pcb part no - (73 level): 73-03618-01 Fab Part no - (28 level): 28-02791-01 PCB Revision: 05 Daughter Card Information: Daughter Card Serial Number: CAB024601FF pcb part no - (73 level): 73-03722-01 Fab Part no - (28 level): 28-02905-01 PCB Revision: 02 value = 34 = 0x22 = '"'

Cannot Use the cc Command to Access a VISM Card

Use the PXM dspcds command to verify if the VISM card is in the active or standby state. If the VISM card is not in the active or standby state, you cannot use the cc command to access the card.

VISM Card Resets Intermittently

Investigate the following possibilities to determine why the VISM card is resetting intermittently:

•Bad hardware device on the card. Replace any corrupt hardware.

•Daughter card is not attached correctly to the VISM card. As a result, the VISM card is not able to maintain its abilities. Ensure that the daughter card is making electrical contact to the motherboard, and is mechanically secure.

VISM Card Does Not Accept a Firmware Download

There must be a VISM card in the slot to which firmware is being downloaded. Ensure that the VISM card is seated in the slot, and that it is making electrical contacts to the backplane.

The card must be in either the active or boot state. Confirm this is the case and try again.

Echo Is Heard on a Voice Call

Ensure that the call has the ECAN feature enabled. If the echo delay is longer than the provision tail length, ECAN does not work. Use the VISM cnfecantail command to configure a larger value for the tail length.

VISM Card LEDs Are Not Lighted

The VISM card may not be inserted completely in the slot. Ensure that the VISM card is seated in the slot correctly, with top and bottom half portions of the VISM card making electrical contact with the backplane.

Firmware Does Not See the Card Insert Bit Status As Set

This symptom can also indicate a bad VISM card or bad MGX slot.

hometocprevnextglossaryfeedbacksearchhelp

Posted: Thu Jun 10 16:30:42 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.