[j-nsp] PIO Read error?

[C. Hagel]

Adam, 
	The best way to determine if this is the PIC or the FPC/Midplane
is to try a different PIC in that slot.  If the New/Other PIC comes
online then you know it is a bad PIC and the FPC/Midplane is fine. 


On Fri, 25 Feb 2005 11:07:07 -0500
Adam Rothschild <asr at latency.net> wrote:

AR> Hello,
AR> 
AR> I've run into a GIG-SX (non rev B) PIC returning the following error
AR> repeatedly on a box running 6.3R1.3:
AR> 
AR>   Feb 25 08:08:54  somerouter feb CMFPC: PIC 0/0 PIO Read error, address 0x0048
AR> [...]
AR>   Feb 25 08:20:25  somerouter feb CMFPC: failed to read PIC 0/0 ID eeprom
AR> 
AR> ...and along with that, the underlying interface going into a down
AR> state.  'request chassis pic fpc-slot X pic-slot X [offline|online]'
AR> doesn't bring the interface back into service, nor does reseating the
AR> card.
AR> 
AR> I'm guessing we're dealing with a PIC gone sour, though I'd be
AR> interested in other hardware or software-related issues to look at as
AR> well, such as possible midplane failure.  Any clues would be
AR> appreciated.
AR> 
AR> Thanks,
AR> -a
AR> _______________________________________________
AR> juniper-nsp mailing list juniper-nsp at puck.nether.net
AR> http://puck.nether.net/mailman/listinfo/juniper-nsp


--
-C. Hagel
-JNCIP #103
-<nanog at lordkron.net>
--