[nsp] any known issues with VIP2-40 and PA-2FE-TX?

[Bruce Pinsky]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gert Doering wrote:

| Hi,
|
| we had much fun yesterday in trying to make a 7507+VIP2-40+PA-2FE-TX work.
|
| In short, it didn't... - the PA-2FE is detected, interfaces are present,
| and I can use FastE1/1/0 just fine.  If I start using FastE1/1/1
| ("extended ping with big packets" - or "BGP session startup"), the VIP2
| crashes, along these lines (detailed register dump omitted):
|
| 527: Jan 21 19:09:18: %VIP2-3-MSG: slot1 VIP-3-PCI_BUS0_SYSERROR: PCI bus
0 system error.
| 528: Jan 21 19:09:18: %VIP2-1-MSG: slot1 PMA error register =
028000C000000000
| 529: Jan 21 19:09:18: %VIP2-1-MSG: slot1     PCI master address = 28000C0
| 530: Jan 21 19:09:18: %VIP2-1-MSG: slot1 PA Bay 0 Upstream PCI-PCI
Bridge, Handle=0
| 531: Jan 21 19:09:18: %VIP2-1-MSG: slot1 DEC21050 bridge chip, config=0x0
| [..]
| 545: Jan 21 19:09:18: %VIP2-1-MSG: slot1 PA Bay 1 Upstream PCI-PCI
Bridge, Handle=1
| 546: Jan 21 19:09:18: %VIP2-1-MSG: slot1 DEC21050 bridge chip, config=0x0
| [..]
| 549: Jan 21 19:09:18: %VIP2-1-MSG: slot1          Signaled System Error
on primary bus
| [..]
| 554: Jan 21 19:09:18: %VIP2-1-MSG: slot1          Detected Parity Error
on secondary bus
| 562: Jan 21 19:09:31: %VIP2-3-MSG: slot1 VIP-3-SVIP_RELOAD: SVIP Reload
is called.
| 563: Jan 21 19:09:31: %VIP2-3-MSG: slot1 VIP-3-SYSTEM_EXCEPTION: VIP
System Exception occurred sig=22, code=0x0, context=0x60A95688
| 564:
| 567: Jan 21 19:09:32: %DBUS-3-DBUSINTERRSWSET: Slot 1, Internal Error due
to VIP crash
|
|
|>From what I understand, this could mean "the PA is broken" (parity error on
| secondary bus) or "the VIP is broken".  My reference document for this is
| http://www.cisco.com/warp/public/63/vip_crash.html
|
| The VIP2 works well (before and after our upgrade attempts) with a PA-8E1
| in Bay 0 and a PA-4E in Bay 1.  So I assume that the VIP is *not* broken.
|
| We tried the PA-2FE-TX in a different VIP2, and it crashed as well (albeit
| already at bootup, not waiting for actual traffic on the interface).
|
| We tried re-seating the PA-2FE (and the VIP memory, and swapping VIP memory),
| but that didn't help (except for a couple of OIR bus hangs :-( ).
|
| Now the interesting part: the PA-2FE-TX was tested fine (extended ping
| with "sweep range of size" on both ports) in a 7206 VXR.  So that's
| assumed to be non-broken as well.
|
|
| IOS is 12.0(26)S1, 7507, RSP4s, 4 VIP2-40, 1 VIP2-50.
|
| The VIP2-40 in question is decoded as this:
|
|         VIP2 controller, FRU: VIP2-40=, HW rev 2.04, board revision D0
|         Serial number: 08196112  Part number: 73-1684-03
|         Test history: 0x00        RMA number: 00-00-00
|         Flags: cisco 7000 board; 7500 compatible
|
| I know that there are issues with the PA-2FE-TX and the VIP2-50, which
| is why we didn't put it into that VIP2.  But I can't find anything about
| problems with the VIP2-40s...
|
|
| (I will ship a new VIP2 and a new PA-2FE-TX to that location later today,
| to try to pinpoint the issue better, but I'd really appreciate some more
| insights from other 7500 users...)
|

Was there any other PA in the other bay of the VIP2-40?   Don't know if it
would make a difference, but there is a note in the documentation for the
PA indicating only a single PA-2FE is supported for that VIP:

	The VIP2-40(=), VIP2-20(=), and VIP2-15(=) are limited to one PA-2FE per card.

And I found DDTS CSCdt45666, PA-2FE-TX: two PA-2FE-TX on one VIP2-40/2Mb
SRAM cause VIP crash.

- --
=========
bep

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (MingW32)

iD8DBQFAEGOhE1XcgMgrtyYRAgqiAJ9cK2HK98Hljg2Tg19+yVTPrOAcRwCgoNo2
jlVQzZR3xXzqNiUUy7MrhAE=
=0br6
-----END PGP SIGNATURE-----