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

[Gert Doering]

Hi,

On Thu, Jan 22, 2004 at 10:56:57AM +0100, Gert Doering wrote:
> we had much fun yesterday in trying to make a 7507+VIP2-40+PA-2FE-TX work.

... as an update to this.  (It might someone else some grief...)

There have been a couple of theories as for why it could have crashed:

 - bad VIP2
 - bad PA-2FE-TX
 - "don't combine a PA-2FE-TX with anything else on a VIP2-40"

so we shipped a new VIP2-40 and a new PA-2FE-TX to said 7500 (PA in
Bay 0, to rule out problems with "PA-2FE in Bay 1"), put it into a 
different slot, and tried again.

Port FastE 0/0/0 works fine.

Port FastE 0/0/1 is diagnosed correctly, but as soon as you start sending
out big pings ("sweep range of sizes"), the VIP2 will crash.  Looks very 
similar to last time.

Jan 26 18:17:19: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0/1, changed state to up
Jan 26 18:17:48: %VIP2-3-MSG: slot0 VIP-3-PCI_BUS0_SYSERROR: PCI bus 0 system error.
Jan 26 18:17:48: %VIP2-1-MSG: slot0 PMA error register = 0082381800000000
Jan 26 18:17:48: %VIP2-1-MSG: slot0     PCI master address = 0823818
Jan 26 18:17:48: %VIP2-1-MSG: slot0 PA Bay 0 Upstream PCI-PCI Bridge, Handle=0
[..]
Jan 26 18:17:48: %VIP2-1-MSG: slot0          Signaled System Error  on primary bus
[..]
Jan 26 18:17:48: %VIP2-1-MSG: slot0          Detected Parity Error  on secondary bus
[..]
Jan 26 18:18:01: %VIP2-3-MSG: slot0 VIP-3-SVIP_RELOAD: SVIP Reload is called. 
Jan 26 18:18:01: %VIP2-3-MSG: slot0 VIP-3-SYSTEM_EXCEPTION: VIP System Exception occurred sig=22, code=0x0, context=0x60A95688

the VIP2 will then reload (and after reload, port 0 works fine...).

IOS is still 12.0(26)S1.  We didn't try other IOS versions, as this is a 
production router and we already had way too much outage due to this 
problem.

Dual RSP4s w/ 256 Mb DRAM each.

VIP2-40s had 32 or 64 Mb DRAM.  No dCEF.

VIP2-40s have "HW rev 2.04, board rev D0" and "HW rev 2.13, board rev A0"
(so it's not specific to a certain VIP2 HW rev).  

PA-2FE-TX is "HW rev 1.00, board rev. B0"


>From the looks of this, it's either a generic hardware incompatibility 
between the VIP2-40 and the PA-2FE-TX, or it is "just" an IOS bug.

Unfortunately, I have no second 7500 to verify this, and this box
does not have a support contract anymore (so I can't open a TAC ticket
either).  So I will leave it as it is for now (just not using the 0/0/1
port), and will eventually try again with 12.2S.

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