Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 

Select PIDs - Basic Troubleshooting Verification.docx

Check Hardware Troubleshooting Index Page for additional recommendations:

http://www.cisco.com/en/US/partner/products/hw/routers/ps214/products_tech_note09186a008012fb88.shtml

Part Numbers selecionados (Selected Part Numbers)

Product Family

Product ID


Product Family

Product ID

7600

7600-ES+20G3C


ASR9000

A9K-2KW-DC

7600-ES+20G3CXL


A9K-2T20GE-B

7600-ES+2TG3CXL


A9K-2T20GE-L

7600-ES+4TG3C


A9K-40GE-B

7600-ES20-10G3C


A9K-40GE-L

7600-ES20-10G3CXL


A9K-4T-B

7600-SIP-200


A9K-4T-L

7600-SIP-400


A9K-8T-B

7600-SIP-600


A9K-8T-L

76-ES+T-20G


A9K-RSP-4G

76-ES+XC-20G3C


CRS

CRS-FP140

RSP720-3C-GE


CRS-MSC-140G

RSP720-3CXL-GE


CRS-MSC-B

C6000

WS-SUP720-3B


MGX

MGX-RPM-PR-512

WS-SUP720-3BXL


MGX-VXSM-155

ASR5000

ASR5K-PSC-32G-K9


MGX-VXSM-T1E1

ASR5K-PSC-64G-K9


PXM45/C

GSR

12000-SIP-401


UBR10K

UBR10-MC5X20H-D

12000-SIP-601


UBR-MC20X20V-20D

PRP-2


UBR-MC20X20V-5D

C3560

WS-C3560-48PS-S


ESR-PRE4




C3750

WS-C3750G-48TS-S

Basic steps to verify below PIDs

Diagnostics needed to be gathered & attached to the RMA

7600, C6000, GSR, ASR9000,CRS, C3560,C3750

  • Verify Memory by replacing with Known good Memory

        Describe Physical Condition (LED Colors & Status)

  • Describe what was found/investigated to identify the hardware failure. (i.e What outputs suggests it’s the hardware?)
  • Attach Login details to SVO RMA (admin/IPaddress)
  • Show tech output
  • Logs from logging/snmp server (when available)

ASR5K

  • Describe what was found/investigated to identify the hardware failure. (i.e What outputs suggests it’s the hardware?)
  • Describe  Physical condition (LED Colors and Status)
  • Attach Login details to SVO RMA (admin/IPaddress)
  • Show support details (SSD)

UBR10K

  • Describe what was found/investigated to identify the hardware failure. (i.e What outputs suggests it’s the hardware?)
  • Describe Physical Condition (LED Colors & Status)
  • Attach Login details to SVO RMA (admin/IPaddress)
  • Show tech output
  • Show logs output for the day the problem happened (if not available , pull the SYSlogs )
  • If modems falling offline on a line card we would need the below output
    • show tech cmts cable x/y/z
    • Show cable hop  (5 times)
    • Show controller cable x/y/z up  | inc SNR  (5 times)
    • Crash files from line card (where applicable)  - Below are Instructions
      • Enable service internal First
      • Router(Config)# service internal
      • (config)# end
      • telnet to MC5x20 card:
      • Router#telnet 127.0.0.51     ( you might have to source from the Ethernet)

For XX:

==>.50 for card 5/0

==>.51 for card 5/1

==>.60 for card 6/0

==>.70 for card 7/0

==>.71 for card 7/1

==>.80 for card 8/0

==>.81 for card 8/1

  • "term len 0"
  • "show tech" from the line card (Make sure you are enable mode in the card)
  • Do a "dir bootflash:" to see the crashinfo files on the bootflash of the card, if there are multiple crashfiles you can match the timestamp with latest crash file. Once you know the name of crash file. To collect that crashinfo file do "more bootflash:<file_name>"

MGX

  • Describe what was found/investigated to identify the hardware failure. (i.e What outputs suggests it’s the hardware?)
  • Describe  Physical condition (LED Colors and Status)
  • Attach Login details to SVO RMA (admin/IPaddress)
  • Provide outputs of the following Commands
    • Dspcds
    • dspcd  <  problematic slot >
    • dsprevs
    • dsprevs -s
    • dsprmrsrcs
    • dsplog
    • dsplog -sl  < problematic slot  >
    • dsperrs
    • dsperr -sl   <  problematic slot   >  -en  <error # >
    • dsperrs -sl  <  problematic slot  >
    • dsperrhist   < problematic slot  >
    • show tech from RPM module
    • show log from RPM module
    • on pxm45C  go to shellconn
    • shmCsmTraceShow  < problematic slot   >
    • showCd   < problematic slot   >
    • dspclkalms
    • dspclksrcs
    • dspcurclk
    • dspclockinfo (from shellConn)

Diagnósticos que precisam ser coletados e anexados ao RMA

7600, C6000, GSR, ASR9000,CRS, C3560,C3750

  • Verifique a memória trocando-a por um pente que esteja funcionando
  • Descreva a condição física (Cores e status dos LED)
  • Descreva o que foi encontrado/investigado para identificar a falha de hardware (ex: Que output sugere que a falha é de hardware?)
  • Anexe detalhes de Login ao RMA no SVO  (admin/IPaddress)
  • Show tech output
  • Logs do servidor de logging/snmp (se disponível)

ASR5K

  • Descreva o que foi encontrado/investigado para identificar a falha de hardware (ex: Que output sugere que a falha é de hardware?)
  • Descreva a condição física (Cores e status dos LED)
  • Anexe detalhes de Login ao RMA no SVO  (admin/IPaddress)
  • Show support details (SSD)

UBR10K

  • Descreva o que foi encontrado/investigado para identificar a falha de hardware (ex: Que output sugere que a falha é de hardware?)
  • Descreva a condição física (Cores e status dos LED)
  • Anexe detalhes de Login ao RMA no SVO  (admin/IPaddress)
  • Show tech output
  • Show logs output do dia em que o problema ocorreu (se não estiver disponível , forneça o SYSlogs )
  • Se o modem está falhando offline em um line card nós precisamos do output abaixo:
    • show tech cmts cable x/y/z
    • Show cable hop  (5 vezes)
    • Show controller cable x/y/z up  | inc SNR  (5 vezes)
    • Crash files do line card (onde for aplicável)  - Abaixo seguem as instruções
      • Enable service internal First
      • Router(Config)# service internal
      • (config)# end
      • telnet to MC5x20 card:
      • Router#telnet 127.0.0.51     ( você talvez precise gerá-lo da Ethernet)

For XX:

==>.50 for card 5/0

==>.51 for card 5/1

==>.60 for card 6/0

==>.70 for card 7/0

==>.71 for card 7/1

==>.80 for card 8/0

==>.81 for card 8/1

  • "term len 0"
  • "show tech" da line card (Tenha certeza que o modo na line card está ativo)
  • Rode um "dir bootflash:" para visualizer os arquivos de crashinfo no bootflash do cartão, se houver múltiplos crashfiles você pode conferir a data com o crashfile mais recente. Uma vez que você souber o nome do crashfile, rode "more bootflash:<file_name>" para coletar o crashinfo

MGX

  • Descrição do que foi encontrado/investigado para identificar a falha de hardware (ex: Que output sugere que a falha é de hardware?)
  • Descreva a condição física (Cores e status dos LED)
  • Anexe detalhes de Login ao RMA no SVO  (admin/IPaddress)
  • Forneça outputs dos seguintes comandos
    • Dspcds
    • dspcd  <  problematic slot >
    • dsprevs
    • dsprevs -s
    • dsprmrsrcs
    • dsplog
    • dsplog -sl  < problematic slot  >
    • dsperrs
    • dsperr -sl   <  problematic slot   >  -en  <error # >
    • dsperrs -sl  <  problematic slot  >
    • dsperrhist   < problematic slot  >
    • show tech do RPM module
    • show log do RPM module
    • on pxm45C  go to shellconn
    • shmCsmTraceShow  < problematic slot   >
    • showCd   < problematic slot   >
    • dspclkalms
    • dspclksrcs
    • dspcurclk
    • dspclockinfo (from shellConn)

Version history
Revision #:
1 of 1
Last update:
‎06-03-2013 07:18 AM
Updated by:
 
Everyone's tags (3)