[c-nsp] Troubleshooting OC3

[Paul Stewart]

Sure can... Thanks for the help..;)

Interface ATM1/0 is up
Hardware is ENHANCED ATM PA - OC3 (155000Kbps)
Framer is PMC PM5346 S/UNI-155-LITE, SAR is LSI ATMIZER II
Firmware rev: G160, Framer rev: 0, ATMIZER II rev: 3
  idb=0x5008EE3C, ds=0x5008FA60, vc=0x65528B40
  slot 1, unit 1, subunit 0, fci_type 0x0056, ticks 697455
  4000 rx buffers: size=512, encap=64, trailer=28, magic=4
Curr Stats:
  VCC count: current=1376, peak=2583
  AAL2 VCC count: 0
  AAL2 TX no buffer count: 0
  AAL2 RX no buffer count: 0
  SAR crashes: Rx SAR=0, Tx SAR=0
  rx_cell_lost=846836, rx_no_buffer=0, rx_crc_10=0, rx_no_mem=0
  rx_cell_len=0, rx_no_vcd=28151, rx_cell_throttle=0, tx_aci_err=0
Rx Free Ring status:
  base=0x3CA7C040, size=4096, write=768
Rx Compl Ring status:
  base=0x0C57B5E0, size=4096, read=1638
Tx Ring status:
  base=0x3CF039C0, size=8192, write=2736
Tx Compl Ring status:
  base=0x0C583620, size=4096, read=1368
BFD Cache status:
  base=0x500D4420, size=6144, read=6143
Rx Cache status:
  base=0x500D4380, size=16, write=6
Tx Shadow status:
  base=0x2007BA00, size=8192, read=2735, write=2736
Control data:
  rx_max_spins=94, max_tx_count=109, tx_count=1
  rx_threshold=2667, rx_count=6, tx_threshold=4608
  tx bfd write indx=0x10DF, rx_pool_info=0x65526B60
Control data base address:
       rx_buf_base = 0x0C329740        rx_p_base = 0x50095AC0
            rx_pak = 0x654D5260              cmd = 0x500956E0
            framer = 0x604F1E28        framer_cb = 0x65522B80
       framer_base = 0x3C900000     pci_pa_stats = 0x0C587660
    device_base[0] = 0x3C800000   device_base[1] = 0x3CC00000
     ssram_base[0] = 0x3CA00000    ssram_base[1] = 0x3CE00000
     sdram_base[0] = 0x3CB00000    sdram_base[1] = 0x3CF00000
     pa_cmd_buf[0] = 0x3CA7FC00    pa_cmd_buf[1] = 0x3CE7FC00
       vcd_base[0] = 0x3CA00000      vcd_base[1] = 0x3CE18000
      chip_dump[0] = 0x0C58768C     chip_dump[1] = 0x0C58778C
   sar_buf_base[0] = 0x3CB24000  sar_buf_base[1] = 0x3CF0C000
       bfd_base[0] = 0x3CA64000      bfd_base[1] = 0x3CE00000
       acd_base[0] = 0x3CA22080      acd_base[1] = 0x3CE38240
Bad particle count = 0
SAR AutoRecovery : Disabled
SAR AR   rx stuck count=0  tx stuck count=0
         rx_crashes    =0  tx_crashes    =0
Framer Information:
 Framing mode: SONET OC3 STS-3c
 No alarm detected
Facility statistics: current interval elapsed 855 seconds
          sbip      lbip      lfebe      pbip     pfebe    hcse
   ------------------------------------------------------------

   sbip:  Section BIP8
   lbip:  Line BIP8/24
   lfebe: Line FEBE
   pbip:  Path BIP8
   pfebe: Path FEBE
   hcse:  Rx Cell HCS Error 

-----Original Message-----
From: james edwards [mailto:hackerwacker at cybermesa.com] 
Sent: Monday, January 16, 2006 4:26 PM
To: cisco-nsp at puck.nether.net
Cc: Paul Stewart
Subject: Re: [c-nsp] Troubleshooting OC3

Could you post the output of "show controller ATM1/0" ?  CRC errors at
the "sh interfaces" level in ATM can mean several things. The output of
"show controller ATM1/0" will tell you if the physical OC-3 is seeing
errors.

James
Routing and Security Administrator
At the Santa Fe Office: Cyber Mesa Telecom jamesh at cybermesa.com
noc at cybermesa.com http://www.cybermesa.com/ContactCM