[c-nsp] Cisc07206 VXR fast ethernet ports
Rodney Dunn
rodunn at cisco.com
Wed Aug 24 00:09:50 EDT 2005
On Wed, Aug 24, 2005 at 12:33:55PM +0900, Ganbold wrote:
> At 11:21 AM 8/24/2005, you wrote:
> >You have done something on one card that isn't supported.
> >
> > PA Bay 0 Information:
> > Gigabit-Ethernet PA, 1 ports
> > EEPROM format version 1
> > HW rev 1.00, Board revision A0
> > Serial number: 25246822 Part number: 73-3144-04
> >
> > PA Bay 1 Information:
> > Dual Port Fast Ethernet (RJ45), 2 ports
> > EEPROM format version 4
> > HW rev 1.00, Board revision B0
> > Serial number: MPC05210075 Part number: 73-5419-06
> >
> >
> >there isn't a GIGE PA for a 75xx. The only GIG option for a 75xx
> >is the full height GEIP boards (one Vip2-50 based the other VIP4-80 based).
>
> We have both, full height GEIP and GIGE PA on 7513 and it is working.
Ok good. But what you have in slot1 isn't suported. You can't have
a FE and a GIGE in the same slot on the 75xx.
>
>
> >I think you may have it recreated in slot 2 though.
>
> Yes.
>
> >This is the footprint we are looking for in this problem:
> >
> > > 01:36:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> > FastEthernet2/1/0, c
> >ha
> > > nged state to up
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 PMA error register0 =
> > 0000000000000000
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 PCI0 master address = 00000000
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 PCI0 slave address = 00000000
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 PMA error register1 =
> > 0082281C01800000
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 PCI Master Parity error
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 PCI Slave Parity error
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 PCI1 master address = 0082281C
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 PCI1 slave address = 000E000C
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 Latched Addresses
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 MPU addr exception/WPE
> > address = 00
> >00
> > > 0000
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 MPU addr exception/WPE data
> > = 00000
> >00
> > > 0
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 ProcMem addr exception =
> > 00000000
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 Pakmem addr exception = 00000000
> > > 01:38:12: %VIP4-80 RM7000-1-MSG: slot2 System reloaded by a fatal
> > hardware err
> >or
> > > 01:38:12: %VIP4-80 RM7000-1-MSG: slot2 caller=0x600E793C
> > > 01:38:12: %VIP4-80 RM7000-1-MSG: slot2 System exception: sig=22,
> > code=0x0, con
> >te
> > > xt=0x6076FFC8
> >
> >
> >Can you please remove slot1 and recreate the problem with just slot2
> >in the chassis?
>
> You mean to remove GIGE PA? Unfortunately I can't.
> Because we have already sent back those PA-2FE-TX cards
> to the reseller and asking them to change those.
Ok. I meant the entire slot1 because that slot is not supported as
I explained above.
>
> >Can you open a TAC case and ask them to attach it to CSCsa50332?
>
> Should I do it now? Or should we wait those cards ?
We need a system that is seeing the problem to open the case on
so we can try to debug it. Preferrably a lab recreate.
>
>
> >What type of traffic were you sending and at what loads?
>
> Traffic is very low, it is less than 10mb.
Ok, on all ports and what was the traffic profile mostly?
Between the FE ports on the same card? To/from the Serial ports
on the same card? or to/from other ports on other cards?
>
>
> >I'm going to try it in the lab again.
>
> Please let me know if you find something.
> Rodney I have one more question. Is it possible to change hardware and
> board revisions?
> Maybe I'm asking impossible question. Please let me know.
All new cards ordered from Cisco will have the new board revisions.
It's pretty impossible for an RMA to be done to get a specific board
rev because if there is a bad problem with them they are purged from
the depos and replinished with the newer board revs anyway. Or at least
that is the goal.
>
> thanks,
>
> Ganbold
>
>
> >Rodney
> >
> >
> >
> >
> >
> >
> > On Wed, Aug 24, 2005 at 10:09:21AM +0900, Ganbold wrote:
> > > I have same problem.
> > > We tested the 2 PA-2FE-TX cards on Cisco 7513 with VIP4-50 and VIP4-80.
> > > When we first installed it was OK.
> > > But when we connected cables and run real traffic router crashed and
> > reloaded.
> > > We tried both cards on several different slots, but it was the same,
> > router
> > > crashed and reloaded.
> > > That was really strange.
> > >
> > > I attached the log file in this regard.
> > >
> > > Following is the show diag output:
> > >
> > > core-ub2#sh diag
> > > Slot 1:
> > > Physical slot 1, ~physical slot 0xE, logical slot 1, CBus 0
> > > Microcode Status 0x4
> > > Master Enable, LED, WCS Loaded
> > > Board is analyzed
> > > Pending I/O Status: None
> > > EEPROM format version 1
> > > VIP4-50 RM5271 controller, HW rev 2.02, board revision A0
> > > Serial number: 20752386 Part number: 73-4708-04
> > > Test history: 0x00 RMA number: 00-00-00
> > > Flags: cisco 7000 board; 7500 compatible
> > >
> > > EEPROM contents (hex):
> > > 0x20: 01 31 02 02 01 3C A8 02 49 12 64 04 00 00 00 00
> > > 0x30: 50 17 EF 00 00 00 00 00 00 00 00 00 00 00 00 00
> > >
> > > Slot database information:
> > > Flags: 0x4 Insertion time: 0x44E0 (1d15h ago)
> > >
> > > Controller Memory Size: 256 MBytes DRAM, 65536 KBytes SRAM
> > >
> > > PA Bay 0 Information:
> > > Gigabit-Ethernet PA, 1 ports
> > > EEPROM format version 1
> > > HW rev 1.00, Board revision A0
> > > Serial number: 25246822 Part number: 73-3144-04
> > >
> > > PA Bay 1 Information:
> > > Dual Port Fast Ethernet (RJ45), 2 ports
> > > EEPROM format version 4
> > > >>>>> HW rev 1.00, Board revision B0
> > > Serial number: MPC05210075 Part number: 73-5419-06
> > >
> > > 1 crash since restart.
> > > Last crash context (Aug 03 2005 20:52:19):
> > > $0 : 00000000, AT : 00000000, v0 : 00000002, v1 : 00000FF0
> > > a0 : 60993840, a1 : 30390000, a2 : 00000001, a3 : 40080008
> > > t0 : 00000180, t1 : 4E90424C, t2 : 00000001, t3 : 3400FF02
> > > t4 : 600E7978, t5 : 000000F8, t6 : 00000000, t7 : 00000000
> > > s0 : 6094A5A0, s1 : AC820100, s2 : 60993840, s3 : 60991C60
> > > s4 : 00000065, s5 : 00000001, s6 : 80000000, s7 : 60720000
> > > t8 : 60730000, t9 : 00000000, k0 : 00000000, k1 : 0000066B
> > > gp : 60691140, sp : 6076B498, s8 : 00000000, ra : 6022C4DC
> > > EPC : 00000002, ErrorEPC : 80008680, SREG : 3400E103
> > > Cause 00000410 (Code 0x4): Address Error (load or instruction
> > > fetch) exc
> > > eption
> > > Traceback= 0x2 0x6022C4DC 0x60260D0C 0x600E7820
> > >
> > >
> > > Ganbold
> > >
> > > At 09:10 AM 8/24/2005, you wrote:
> > > >We have tried to recreate this and can't.
> > > >
> > > >Can you post the crashinfo file so I can look at it?
> > > >
> > > >What type of crash was it?
> > > >
> > > >If someone can recreate it and help us I'll be more
> > > >than glad to debug it and get DE involved to find
> > > >root cause.
> > > >
> > > >The bug we are using to track it is:
> > > >
> > > >CSCsa50332
> > > >Externally found moderate defect: Waiting (W)
> > > >VIP4-80 with PA-2FE-TX may crash with parity error
> > > >
> > > >Rodney
> > > >
> > > >
> > > >
> > > >On Tue, Aug 23, 2005 at 11:27:34PM +0200, Gert Doering wrote:
> > > > > Hi,
> > > > >
> > > > > On Tue, Aug 23, 2005 at 04:12:58PM -0500, Jerry Kersey wrote:
> > > > > > bandwidth points are 600 and 400. Cisco says they have never saw
> > this
> > > > > > problem before. I find it hard to belive that no one else is trying
> > > > to run 3
> > > > > > or 4 fast ethernet ports on one ov these routers... What happens
> > is the
> > > > > > fa2/1 port starts going up/down several times, the router crashes,
> > > > creates a
> > > > > > crashinfo file and reloads...
> > > > >
> > > > > Welcome to the club. There seems to be a certain revision of PA-2FE-TX
> > > > > cards that give lots of problems, as soon as their port 1 is
> > used. "Been
> > > > > there, done that" (on a VIP2-50 and on a 7206/NPE-400).
> > > > >
> > > > > Can you put the card into a lab router and run "show diag" against it?
> > > > >
> > > > > I'd bet it's hardware revision 1.0, board revision B0.
> > > > >
> > > > > gert
> > > > >
> > > > >
> > > > > --
> > > > > USENET is *not* the non-clickable part of WWW!
> > > > >
> > > > //www.muc.de/~gert/
> > > > > Gert Doering - Munich,
> > > > Germany gert at greenie.muc.de
> > > > > fax:
> > > > +49-89-35655025 gert at net.informatik.tu-muenchen.de
> > > > > _______________________________________________
> > > > > cisco-nsp mailing list cisco-nsp at puck.nether.net
> > > > > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > > > > archive at http://puck.nether.net/pipermail/cisco-nsp/
> > > >_______________________________________________
> > > >cisco-nsp mailing list cisco-nsp at puck.nether.net
> > > >https://puck.nether.net/mailman/listinfo/cisco-nsp
> > > >archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
> > > core-ub2#sh logg
> > > core-ub2#sh logging
> > > Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)
> > > Console logging: level debugging, 203 messages logged
> > > Monitor logging: level debugging, 0 messages logged
> > > Buffer logging: level debugging, 203 messages logged
> > > Trap logging: level informational, 211 message lines logged
> > >
> > > Log Buffer (65536 bytes):
> > >
> > > 00:00:06: %RSP-3-DEVERR: Read cis from dev 1 error -6
> > > 00:00:11: %RSP-3-SLAVECHANGE: Slave changed state from Slave to
> > Non-participant
> > > 00:00:14: %RSP-3-SLAVECHANGE: Slave changed state from Non-participant
> > to Slave
> > > 00:01:27: %RSP-3-SLAVECHANGE: Slave changed state from Slave to
> > Non-participant
> > > 00:01:29: %RSP-3-SLAVECHANGE: Slave changed state from Non-participant
> > to Slave
> > > 00:02:07: %SYS-5-CONFIG_I: Configured from memory by console
> > >
> > > 01:17:54: %SYS-5-CONFIG_I: Configured from console by vty0 (202.179.10.1)
> > > 01:17:55: %LINK-3-UPDOWN: Interface FastEthernet1/1/1, changed state to
> > down
> > > 01:17:56: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> > FastEthernet1/1/1, cha
> > > nged state to down
> > > 01:18:14: %VIP4-50 RM5271-1-MSG: slot1 IOBUS Error Interrupt Status
> > register 0x4
> > > 01:18:14: %VIP4-50 RM5271-1-MSG: slot1 Address/Command Strobe Timeout
> > > 01:18:14: %VIP4-50 RM5271-1-MSG: slot1 IOBUS Error Address High 0x1C01
> > > 01:18:14: %VIP4-50 RM5271-1-MSG: slot1 IOBUS Error Address Low 0xC
> > > 01:18:15: %LINK-3-UPDOWN: Interface FastEthernet1/1/1, changed state to up
> > > 01:18:16: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> > FastEthernet1/1/1, cha
> > > nged state to up
> > > 01:18:30: %VIP4-50 RM5271-1-MSG: slot1 System reloaded by a Bus Error
> > exception
> > > 01:18:30: %VIP4-50 RM5271-1-MSG: slot1 caller=0x600E793C
> > > 01:18:30: %VIP4-50 RM5271-1-MSG: slot1 System exception: sig=10,
> > code=0x10, cont
> > > ext=0x606F92C0
> > > 01:18:30: %VIP4-50 RM5271-1-MSG: slot1 $0 : 00000000, AT : 00000000, v0
> > : 000000
> > > 02, v1 : 00000FF0,
> > > 01:18:30: %VIP4-50 RM5271-1-MSG: slot1 a0 : 60993840, a1 : 30390000, a2
> > : 000000
> > > 01, a3 : 40080008,
> > > 01:18:30: %VIP4-50 RM5271-1-MSG: slot1 t0 : 00000180, t1 : 4E90424C, t2
> > : 000000
> > > 01, t3 : 3400FF02,
> > > 01:18:30: %VIP4-50 RM5271-1-MSG: slot1 t4 : 600E7978, t5 : 000000F8, t6
> > : 000000
> > > 00, t7 : 00000000,
> > > 01:18:30: %VIP4-50 RM5271-1-MSG: slot1 s0 : 6094A5A0, s1 : AC820100, s2
> > : 609938
> > > 40, s3 : 60991C60,
> > > 01:18:30: %VIP4-50 RM5271-1-MSG: slot1 s4 : 00000065, s5 : 00000001, s6
> > : 800000
> > > 00, s7 : 60720000,
> > > 01:18:30: %VIP4-50 RM5271-1-MSG: slot1 t8 : 60730000, t9 : 00000000, k0
> > : 000000
> > > 00, k1 : 0000066B,
> > > 01:18:30: %VIP4-50 RM5271-1-MSG: slot1 gp : 60691140, sp : 6076B498, s8
> > : 000000
> > > 00, ra : 6022C4DC,
> > > 01:18:30: %VIP4-50 RM5271-1-MSG: slot1 EPC : 00000002, ErrorEPC :
> > 80008680, SREG
> > > : 3400E103
> > > 01:18:30: %VIP4-50 RM5271-1-MSG: slot1 Cause 00000410 (Code 0x4)
> > > 01:18:30: %VIP4-50 RM5271-1-MSG: slot1 Traceback= 2 6022C4DC
> > 60260D0C 600
> > > E7820
> > > 01:18:30: %RSP-3-FOREVER: cmd 2 to VIP4-50 RM5271 (slot 1) took 99
> > usecs, done 1
> > > -Traceback= 603FF3C0 603FF9C4 603F779C 603F5694 60338CE8 60338F18
> > 6035C824 6035C
> > > 810
> > > 01:18:30: %RSP-3-FOREVER: cmd 38 to VIP4-50 RM5271 (slot 1) took 111
> > usecs, done
> > > 1
> > > -Traceback= 603FF3C0 603FF9C4 603F77D8 60403F64 603F56C4 60338CE8
> > 60338F18 6035C
> > > 824 6035C810
> > > 01:18:30: %RSP-3-FOREVER: cmd 2 to VIP4-50 RM5271 (slot 1) took 271
> > usecs, done
> > > 1
> > > -Traceback= 603FF3C0 603FF9C4 603F779C 603F5694 60338CE8 60338F18
> > 6035C824 6035C
> > > 810
> > > 01:18:30: %RSP-3-FOREVER: cmd 38 to VIP4-50 RM5271 (slot 1) took 149
> > usecs, done
> > > 1
> > > -Traceback= 603FF3C0 603FF9C4 603F77D8 60403F64 603F56C4 60338CE8
> > 60338F18 6035C
> > > 824 6035C810
> > > 01:18:31: %DBUS-3-DBUSINTERRSWSET: Slot 1, Internal Error due to VIP crash
> > > 01:18:45: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.1 on
> > GigabitEthernet1/0/0 f
> > > rom FULL to DOWN, Neighbor Down: Dead timer expired
> > > 01:19:05: %RSP-3-RESTART: cbus complex
> > > 01:20:56: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.8 on Serial4/1
> > from FULL to
> > > DOWN, Neighbor Down: Dead timer expired
> > > 01:20:56: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.10.1 on
> > FastEthernet3/0/0 fro
> > > m FULL to DOWN, Neighbor Down: Dead timer expired
> > > 01:20:56: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.17 on Serial2/0/5
> > from FULL
> > > to DOWN, Neighbor Down: Dead timer expired
> > > 01:20:56: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.5 on Serial4/0
> > from FULL to
> > > DOWN, Neighbor Down: Dead timer expired
> > > 01:20:56: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.13 on
> > FastEthernet3/1/0 fro
> > > m FULL to DOWN, Neighbor Down: Dead timer expired
> > > 01:20:56: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.35 on Serial4/5
> > from FULL t
> > > o DOWN, Neighbor Down: Dead timer expired
> > > 01:20:58: %LINK-3-UPDOWN: Interface FastEthernet1/1/1, changed state to
> > down
> > > 01:20:58: %LINK-3-UPDOWN: Interface FastEthernet11/0/0, changed state
> > to down
> > > 01:20:59: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> > FastEthernet1/1/1, cha
> > > nged state to down
> > > 01:21:06: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.10.1 on
> > FastEthernet3/0/0 fro
> > > m LOADING to FULL, Loading Done
> > > 01:21:06: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.5 on Serial4/0
> > from LOADING
> > > to FULL, Loading Done
> > > 01:21:06: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.8 on Serial4/1
> > from LOADING
> > > to FULL, Loading Done
> > > 01:21:16: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.17 on Serial2/0/5
> > from LOAD
> > > ING to FULL, Loading Done
> > > 01:21:16: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.35 on Serial4/5
> > from LOADIN
> > > G to FULL, Loading Done
> > > 01:21:35: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.1 on
> > GigabitEthernet1/0/0 f
> > > rom LOADING to FULL, Loading Done
> > > 01:21:36: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.13 on
> > FastEthernet3/1/0 fro
> > > m LOADING to FULL, Loading Done
> > > 01:23:54: %LINK-5-CHANGED: Interface FastEthernet1/1/1, changed state
> > to adminis
> > > tratively down
> > > 01:24:29: %LINK-3-UPDOWN: Interface FastEthernet2/1/1, changed state to
> > down
> > > 01:24:43: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> > FastEthernet2/1/1, cha
> > > nged state to up
> > > 01:24:49: %SYS-5-CONFIG_I: Configured from console by console
> > > 01:24:49: %LINK-3-UPDOWN: Interface FastEthernet2/1/1, changed state to
> > down
> > > 01:24:50: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> > FastEthernet2/1/1, cha
> > > nged state to down
> > > 01:25:39: %LINK-3-UPDOWN: Interface FastEthernet2/1/1, changed state to up
> > > 01:25:40: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> > FastEthernet2/1/1, cha
> > > nged state to up
> > > 01:30:08: %LINK-3-UPDOWN: Interface FastEthernet2/1/1, changed state to
> > down
> > > 01:30:10: %LINK-3-UPDOWN: Interface FastEthernet2/1/1, changed state to up
> > > 01:34:49: %SYS-5-CONFIG_I: Configured from console by console
> > > 01:34:49: %LINK-3-UPDOWN: Interface FastEthernet2/1/0, changed state to
> > down
> > > 01:36:03: %LINK-3-UPDOWN: Interface FastEthernet2/1/0, changed state to up
> > > 01:36:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> > FastEthernet2/1/0, cha
> > > nged state to up
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 PMA error register0 =
> > 0000000000000000
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 PCI0 master address = 00000000
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 PCI0 slave address = 00000000
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 PMA error register1 =
> > 0082281C01800000
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 PCI Master Parity error
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 PCI Slave Parity error
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 PCI1 master address = 0082281C
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 PCI1 slave address = 000E000C
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 Latched Addresses
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 MPU addr exception/WPE
> > address = 0000
> > > 0000
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 MPU addr exception/WPE data
> > = 0000000
> > > 0
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 ProcMem addr exception =
> > 00000000
> > > 01:37:57: %VIP4-80 RM7000-1-MSG: slot2 Pakmem addr exception = 00000000
> > > 01:38:12: %VIP4-80 RM7000-1-MSG: slot2 System reloaded by a fatal
> > hardware error
> > > 01:38:12: %VIP4-80 RM7000-1-MSG: slot2 caller=0x600E793C
> > > 01:38:12: %VIP4-80 RM7000-1-MSG: slot2 System exception: sig=22,
> > code=0x0, conte
> > > xt=0x6076FFC8
> > > 01:38:12: %VIP4-80 RM7000-1-MSG: slot2 $0 : 00000000, AT : 00000000, v0
> > : 607000
> > > 00, v1 : FFC8BE6E,
> > > 01:38:12: %VIP4-80 RM7000-1-MSG: slot2 a0 : 0000007A, a1 : 00000000, a2
> > : 000000
> > > 01, a3 : 609164C0,
> > > 01:38:12: %VIP4-80 RM7000-1-MSG: slot2 t0 : 080045FF, t1 : 4E90424C, t2
> > : 080045
> > > 00, t3 : FFFFFFCB,
> > > 01:38:12: %VIP4-80 RM7000-1-MSG: slot2 t4 : 600E7978, t5 : 00000000, t6
> > : 000001
> > > 00, t7 : 00000001,
> > > 01:38:12: %VIP4-80 RM7000-1-MSG: slot2 s0 : 00000000, s1 : 00001E00, s2
> > : 609C49
> > > C0, s3 : 00000002,
> > > 01:38:12: %VIP4-80 RM7000-1-MSG: slot2 s4 : 00000001, s5 : 00000000, s6
> > : 607000
> > > 00, s7 : 00000000,
> > > 01:38:12: %VIP4-80 RM7000-1-MSG: slot2 t8 : 60730000, t9 : 00000000, k0
> > : 000000
> > > 00, k1 : 00000644,
> > > 01:38:12: %VIP4-80 RM7000-1-MSG: slot2 gp : 60691140, sp : 6076B500, s8
> > : 000000
> > > 00, ra : 600E7820,
> > > 01:38:12: %VIP4-80 RM7000-1-MSG: slot2 EPC : 60260CF8, ErrorEPC :
> > 80008680, SREG
> > > : 3400E103
> > > 01:38:12: %VIP4-80 RM7000-1-MSG: slot2 Cause 00001800 (Code 0x0)
> > > 01:38:12: %VIP4-80 RM7000-1-MSG: slot2 Traceback= 60260CF8 600E7820
> > > 01:38:13: %DBUS-3-DBUSINTERRSWSET: Slot 2, Internal Error due to VIP crash
> > > 01:38:27: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.17 on Serial2/0/5
> > from FULL
> > > to DOWN, Neighbor Down: Dead timer expired
> > > 01:38:42: %RSP-3-RESTART: cbus complex
> > > 01:40:32: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.13 on
> > FastEthernet3/1/0 fro
> > > m FULL to DOWN, Neighbor Down: Dead timer expired
> > > 01:40:32: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.35 on Serial4/5
> > from FULL t
> > > o DOWN, Neighbor Down: Dead timer expired
> > > 01:40:32: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.8 on Serial4/1
> > from FULL to
> > > DOWN, Neighbor Down: Dead timer expired
> > > 01:40:32: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.10.1 on
> > FastEthernet3/0/0 fro
> > > m FULL to DOWN, Neighbor Down: Dead timer expired
> > > 01:40:32: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.1 on
> > GigabitEthernet1/0/0 f
> > > rom FULL to DOWN, Neighbor Down: Dead timer expired
> > > 01:40:32: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.5 on Serial4/0
> > from FULL to
> > > DOWN, Neighbor Down: Dead timer expired
> > > 01:40:34: %LINK-3-UPDOWN: Interface FastEthernet2/1/0, changed state to
> > down
> > > 01:40:34: %LINK-3-UPDOWN: Interface FastEthernet11/0/0, changed state
> > to down
> > > 01:40:35: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> > FastEthernet2/1/0, cha
> > > nged state to down
> > > 01:40:42: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.10.1 on
> > FastEthernet3/0/0 fro
> > > m LOADING to FULL, Loading Done
> > > 01:40:42: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.5 on Serial4/0
> > from LOADING
> > > to FULL, Loading Done
> > > 01:40:42: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.8 on Serial4/1
> > from LOADING
> > > to FULL, Loading Done
> > > 01:40:42: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.35 on Serial4/5
> > from LOADIN
> > > G to FULL, Loading Done
> > > 01:40:44: %LINK-3-UPDOWN: Interface FastEthernet2/1/1, changed state to
> > down
> > > 01:40:45: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> > FastEthernet2/1/1, cha
> > > nged state to down
> > > 01:40:52: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.17 on Serial2/0/5
> > from LOAD
> > > ING to FULL, Loading Done
> > > 01:41:11: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.1 on
> > GigabitEthernet1/0/0 f
> > > rom LOADING to FULL, Loading Done
> > > 01:41:12: %OSPF-5-ADJCHG: Process 117, Nbr 202.179.5.13 on
> > FastEthernet3/1/0 fro
> > > m LOADING to FULL, Loading Done
> > >
> > > core-ub2#$
> > > core-ub2#
> > >
> > 33333333333333333333333333333333333333333333333333333333333333333333333333333333
> > > core-ub2#sh diag
> > > Slot 1:
> > > Physical slot 1, ~physical slot 0xE, logical slot 1, CBus 0
> > > Microcode Status 0x4
> > > Master Enable, LED, WCS Loaded
> > > Board is analyzed
> > > Pending I/O Status: None
> > > EEPROM format version 1
> > > VIP4-50 RM5271 controller, HW rev 2.02, board revision A0
> > > Serial number: 20752386 Part number: 73-4708-04
> > > Test history: 0x00 RMA number: 00-00-00
> > > Flags: cisco 7000 board; 7500 compatible
> > >
> > > EEPROM contents (hex):
> > > 0x20: 01 31 02 02 01 3C A8 02 49 12 64 04 00 00 00 00
> > > 0x30: 50 17 EF 00 00 00 00 00 00 00 00 00 00 00 00 00
> > >
> > > Slot database information:
> > > Flags: 0x4 Insertion time: 0x44E0 (01:44:38 ago)
> > >
> > > Controller Memory Size: 256 MBytes DRAM, 65536 KBytes SRAM
> > >
> > > PA Bay 0 Information:
> > > Gigabit-Ethernet PA, 1 ports
> > > EEPROM format version 1
> > > HW rev 1.00, Board revision A0
> > > Serial number: 25246822 Part number: 73-3144-04
> > >
> > > PA Bay 1 Information:
> > > Dual Port Fast Ethernet (RJ45), 2 ports
> > > EEPROM format version 4
> > > HW rev 1.00, Board revision B0
> > > Serial number: MPC05210075 Part number: 73-5419-06
> > >
> > > 1 crash since restart.
> > > Last crash context (Aug 03 2005 20:52:19):
> > > $0 : 00000000, AT : 00000000, v0 : 00000002, v1 : 00000FF0
> > > a0 : 60993840, a1 : 30390000, a2 : 00000001, a3 : 40080008
> > > t0 : 00000180, t1 : 4E90424C, t2 : 00000001, t3 : 3400FF02
> > > t4 : 600E7978, t5 : 000000F8, t6 : 00000000, t7 : 00000000
> > > s0 : 6094A5A0, s1 : AC820100, s2 : 60993840, s3 : 60991C60
> > > s4 : 00000065, s5 : 00000001, s6 : 80000000, s7 : 60720000
> > > t8 : 60730000, t9 : 00000000, k0 : 00000000, k1 : 0000066B
> > > gp : 60691140, sp : 6076B498, s8 : 00000000, ra : 6022C4DC
> > > EPC : 00000002, ErrorEPC : 80008680, SREG : 3400E103
> > > Cause 00000410 (Code 0x4): Address Error (load or instruction
> > fetch) exc
> > > eption
> > > Traceback= 0x2 0x6022C4DC 0x60260D0C 0x600E7820
> > >
> > >
> > >
> > > --Boot log begin--
> > >
> > > Cisco Internetwork Operating System Software
> > > IOS (tm) VIP Software (SVIP-DW-M), Version 12.1(5a)E1, EARLY DEPLOYMENT
> > RELEASE
> > > SOFTWARE (fc1)
> > > Copyright (c) 1986-2000 by cisco Systems, Inc.
> > > Compiled Tue 26-Dec-00 23:01 by eaarmas
> > > Image text-base: 0x60010940, data-base: 0x60360000
> > >
> > >
> > > --Boot log end--
> > >
> > > Slot 2:
> > > Physical slot 2, ~physical slot 0xD, logical slot 2, CBus 0
> > > Microcode Status 0x4
> > > Master Enable, LED, WCS Loaded
> > > Board is analyzed
> > > Pending I/O Status: None
> > > EEPROM format version 1
> > > VIP4-80 RM7000 controller, HW rev 2.01, board revision A0
> > > Serial number: 23274300 Part number: 73-3143-03
> > > Test history: 0x00 RMA number: 00-00-00
> > > Flags: cisco 7000 board; 7500 compatible
> > >
> > > EEPROM contents (hex):
> > > 0x20: 01 22 02 01 01 63 23 3C 49 0C 47 03 00 00 00 00
> > > 0x30: 50 05 35 00 00 00 00 00 00 00 00 00 00 00 00 00
> > >
> > > Slot database information:
> > > Flags: 0x4 Insertion time: 0x44E0 (01:44:41 ago)
> > >
> > > Controller Memory Size: 256 MBytes DRAM, 65536 KBytes SRAM
> > >
> > > PA Bay 0 Information:
> > > Mx Serial PA, 8 ports
> > > EEPROM format version 1
> > > HW rev 1.16, Board revision A0
> > > Serial number: 22490416 Part number: 73-1580-09
> > >
> > > PA Bay 1 Information:
> > > Dual Port Fast Ethernet (RJ45), 2 ports
> > > EEPROM format version 4
> > > HW rev 1.00, Board revision B0
> > > Serial number: JAE05490880 Part number: 73-5419-06
> > >
> > > 1 crash since restart.
> > > Last crash context (Aug 03 2005 21:12:01):
> > > Nevada Error Interrupt Register = 0x2
> > > PMA error interrupt
> > > PMA Error Register = 0000000000000000
> > > PCI master address = 0000000
> > > $0 : 00000000, AT : 00000000, v0 : 60700000, v1 : FFC8BE6E
> > > a0 : 0000007A, a1 : 00000000, a2 : 00000001, a3 : 609164C0
> > > t0 : 080045FF, t1 : 4E90424C, t2 : 08004500, t3 : FFFFFFCB
> > > t4 : 600E7978, t5 : 00000000, t6 : 00000100, t7 : 00000001
> > > s0 : 00000000, s1 : 00001E00, s2 : 609C49C0, s3 : 00000002
> > > s4 : 00000001, s5 : 00000000, s6 : 60700000, s7 : 00000000
> > > t8 : 60730000, t9 : 00000000, k0 : 00000000, k1 : 00000644
> > > gp : 60691140, sp : 6076B500, s8 : 00000000, ra : 600E7820
> > > EPC : 60260CF8, ErrorEPC : 80008680, SREG : 3400E103
> > > Cause 00001800 (Code 0x0): Interrupt exception
> > > Traceback= 0x60260CF8 0x600E7820
> > >
> > >
> > > --Boot log begin--
> > >
> > > Cisco Internetwork Operating System Software
> > > IOS (tm) VIP Software (SVIP-DW-M), Version 12.1(5a)E1, EARLY DEPLOYMENT
> > RELEASE
> > > SOFTWARE (fc1)
> > > Copyright (c) 1986-2000 by cisco Systems, Inc.
> > > Compiled Tue 26-Dec-00 23:01 by eaarmas
> > > Image text-base: 0x60010940, data-base: 0x60360000
> > >
> > >
> > > --Boot log end--
> > >
> > > Slot 3:
> > > Physical slot 3, ~physical slot 0xC, logical slot 3, CBus 0
> > > Microcode Status 0x4
> > > Master Enable, LED, WCS Loaded
> > > Board is analyzed
> > > Pending I/O Status: None
> > > EEPROM format version 1
> > > VIP2 R5K controller, HW rev 2.02, board revision A0
> > > Serial number: 10020157 Part number: 73-2167-04
> > > Test history: 0x00 RMA number: 00-00-00
> > > Flags: cisco 7000 board; 7500 compatible
> > >
> > > EEPROM contents (hex):
> > > 0x20: 01 1E 02 02 00 98 E5 3D 49 08 77 04 00 00 00 00
> > > 0x30: 50 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00
> > >
> > > Slot database information:
> > > Flags: 0x4 Insertion time: 0x44E0 (01:44:47 ago)
> > >
> > > Controller Memory Size: 128 MBytes DRAM, 8192 KBytes SRAM
> > >
> > > PA Bay 0 Information:
> > > Fast-Ethernet PA, 1 ports, 100BaseTX-ISL
> > > EEPROM format version 1
> > > HW rev 1.04, Board revision B0
> > > Serial number: 22551810 Part number: 73-1688-05
> > >
> > > PA Bay 1 Information:
> > > Fast-Ethernet PA, 1 ports, 100BaseTX-ISL
> > > EEPROM format version 1
> > > HW rev 1.04, Board revision B0
> > > Serial number: 20671794 Part number: 73-1688-05
> > >
> > > --Boot log begin--
> > >
> > > Cisco Internetwork Operating System Software
> > > IOS (tm) VIP Software (SVIP-DW-M), Version 12.1(5a)E1, EARLY DEPLOYMENT
> > RELEASE
> > > SOFTWARE (fc1)
> > > Copyright (c) 1986-2000 by cisco Systems, Inc.
> > > Compiled Tue 26-Dec-00 23:01 by eaarmas
> > > Image text-base: 0x60010940, data-base: 0x60360000
> > >
> > >
> > > --Boot log end--
> > >
> > > Slot 4:
> > > Physical slot 4, ~physical slot 0xB, logical slot 4, CBus 0
> > > Microcode Status 0x0
> > > Master Enable, LED, WCS Loaded
> > > Board is analyzed
> > > EEPROM format version 1
> > > FSIP controller, HW rev 1.12, board revision A0
> > > Serial number: 05896699 Part number: 73-1126-06
> > > Test history: 0x00 RMA number: 00-00-00
> > > Flags: cisco 7000 board; 7500 compatible
> > >
> > > EEPROM contents (hex):
> > > 0x20: 01 07 01 0C 00 59 F9 FB 49 04 66 06 00 00 00 00
> > > 0x30: 50 00 00 00 FF 00 00 00 00 00 00 00 00 00 00 00
> > >
> > > Slot database information:
> > > Flags: 0x4 Insertion time: 0x44E0 (01:44:50 ago)
> > > Slot 6:
> > > EEPROM format version 1
> > > Route/Switch Processor 8, HW rev 1.03, board revision A0
> > > Serial number: 13949594 Part number: 73-4221-03
> > > Test history: 0x00 RMA number: 00-00-00
> > > Flags: cisco 7000 board; 7500 compatible
> > >
> > > EEPROM contents (hex):
> > > 0x20: 01 24 01 03 00 D4 DA 9A 49 10 7D 03 00 00 00 00
> > > 0x30: 50 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > Slot 7:
> > > EEPROM format version 1
> > > Route/Switch Processor 8, HW rev 1.03, board revision A0
> > > Serial number: 23979134 Part number: 73-4221-03
> > > Test history: 0x00 RMA number: 00-00-00
> > > Flags: cisco 7000 board; 7500 compatible
> > >
> > > EEPROM contents (hex):
> > > 0x20: 01 24 01 03 01 6D E4 7E 49 10 7D 03 00 00 00 00
> > > 0x30: 50 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > Slot 10:
> > > Physical slot 10, ~physical slot 0x5, logical slot 10, CBus 0
> > > Microcode Status 0x0
> > > Master Enable, LED, WCS Loaded
> > > Board is analyzed
> > > EEPROM format version 1
> > > FSIP controller, HW rev 1.12, board revision A0
> > > Serial number: 05896785 Part number: 73-1126-06
> > > Test history: 0x00 RMA number: 00-00-00
> > > Flags: cisco 7000 board; 7500 compatible
> > >
> > > EEPROM contents (hex):
> > > 0x20: 01 07 01 0C 00 59 FA 51 49 04 66 06 00 00 00 00
> > > 0x30: 50 00 00 00 FF 00 00 00 00 00 00 00 00 00 00 00
> > >
> > > Slot database information:
> > > Flags: 0x4 Insertion time: 0x44E0 (01:44:53 ago)
> > > Slot 11:
> > > Physical slot 11, ~physical slot 0x4, logical slot 11, CBus 0
> > > Microcode Status 0x4
> > > Master Enable, LED, WCS Loaded
> > > Board is analyzed
> > > Pending I/O Status: None
> > > EEPROM format version 1
> > > FEIP2 controller, HW rev 2.11, board revision E0
> > > Serial number: 15357761 Part number: 73-1684-04
> > > Test history: 0x0E RMA number: 00-00-00
> > > Flags: cisco 7000 board; 7500 compatible
> > >
> > > EEPROM contents (hex):
> > > 0x20: 01 20 02 0B 00 EA 57 41 49 06 94 04 0E 00 00 00
> > > 0x30: 70 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00
> > >
> > > Slot database information:
> > > Flags: 0x4 Insertion time: 0x44E0 (01:44:56 ago)
> > >
> > > Controller Memory Size: 32 MBytes DRAM, 2048 KBytes SRAM
> > >
> > > PA Bay 0 Information:
> > > Fast-Ethernet PA, 1 ports, 100BaseTX-ISL
> > > EEPROM format version 1
> > > HW rev 1.04, Board revision B0
> > > Serial number: 15342689 Part number: 73-2570-02
> > >
> > > --Boot log begin--
> > >
> > > Cisco Internetwork Operating System Software
> > > IOS (tm) VIP Software (SVIP-DW-M), Version 12.1(5a)E1, EARLY DEPLOYMENT
> > RELEASE
> > > SOFTWARE (fc1)
> > > Copyright (c) 1986-2000 by cisco Systems, Inc.
> > > Compiled Tue 26-Dec-00 23:01 by eaarmas
> > > Image text-base: 0x60010940, data-base: 0x60360000
> > >
> > >
> > > --Boot log end--
> > >
> > > Slot 31 (virtual):
> > > EEPROM format version 1
> > > Chassis Interface, HW rev 1.01, board revision C0
> > > Serial number: 16191650 Part number: 73-1306-02
> > > Test history: 0x00 RMA number: 00-00-00
> > > Flags: cisco 7000 board
> > >
> > > EEPROM contents (hex):
> > > 0x20: 01 10 01 01 00 F7 10 A2 49 05 1A 02 00 00 00 00
> > > 0x30: 60 00 00 00 FF 00 00 00 00 00 00 00 00 00 00 00
More information about the cisco-nsp
mailing list