Mailing List Archive: m160 pic/fpc error messages

Anyone every seen anything like this before? Obviously something is
very broken but I'm having trouble nailing down exactly what it is.
Does anyone know which components could be affected here? Its only
happening on one 2xge pic.

We get this cam error for each vrrp session we put on it:

Dec 6 15:37:41 re0.j1.scnet.net fpc0 GE(0/0): GEM failed to enable
(0x44020641), link 0
Dec 6 15:37:41 re0.j1.scnet.net fpc0 GE(0/0): link 0 failed to add dst
entry 7 to CAM (1)
Dec 6 15:37:41 re0.j1.scnet.net fpc0 IFFPC: 'IFD Ether mfilter set'
(opcode 57) failed
Dec 6 15:37:41 re0.j1.scnet.net fpc0 ifd 244; Ether mfilter error (1)
Dec 6 15:37:41 re0.j1.scnet.net fpc0 GE(0/0): link 0 failed to add dst
entry 8 to CAM (1)

And this in general after moving traffic over some .q vlans:

Dec 6 16:03:27 re0.j1.scnet.net fpc0 CMFPC: PIC 0 PIO Read error,
address 0x4028
Dec 6 16:03:57 re0.j1.scnet.net fpc0 last message repeated 30 times
Dec 6 16:05:57 re0.j1.scnet.net fpc0 last message repeated 120 times
Dec 6 16:08:55 re0.j1.scnet.net fpc0 last message repeated 178 times
Dec 6 16:08:56 re0.j1.scnet.net chassisd[2202]: No response from the
other routing engine for the last 360 seconds.
Dec 6 16:08:56 re0.j1.scnet.net fpc0 CMFPC: PIC 0 PIO Read error,
address 0x4028
Dec 6 16:08:58 re0.j1.scnet.net fpc0 last message repeated 2 times
Dec 6 16:10:58 re0.j1.scnet.net fpc0 last message repeated 120 times
Dec 6 16:15:01 re0.j1.scnet.net fpc0 last message repeated 243 times
Dec 6 16:15:02 re0.j1.scnet.net chassisd[2202]: No response from the
other routing engine for the last 360 seconds.
Dec 6 16:15:02 re0.j1.scnet.net fpc0 CMFPC: PIC 0 PIO Read error,
address 0x4028
Dec 6 16:15:28 re0.j1.scnet.net fpc0 last message repeated 26 times
Dec 6 16:17:28 re0.j1.scnet.net fpc0 last message repeated 120 times
Dec 6 16:21:09 re0.j1.scnet.net fpc0 last message repeated 220 times
Dec 6 16:21:09 re0.j1.scnet.net chassisd[2202]: No response from the
other routing engine for the last 360 seconds.
Dec 6 16:21:10 re0.j1.scnet.net fpc0 CMFPC: PIC 0 PIO Read error,
address 0x4028
Dec 6 16:21:29 re0.j1.scnet.net fpc0 last message repeated 19 times
Dec 6 16:23:29 re0.j1.scnet.net fpc0 last message repeated 120 times

I have plenty more similar logs if anyone has an idea.

Thanks,
Jordan

--
Jordan Lowe
Server Central Network
(888) 875-4804 x255

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/juniper-nsp/attachments/20031206/aefc3409/attachment.html

open a support case,please. In this case the FPC can not talk to
the PIC in Slot 0 via PIO ( polled input/output ) anymore. So the
communication path is broken. You may want to verify if this is
pic-slot or pic dependant to understand which part needs to be
replaced.

Sunday, December 7, 2003, 4:38:01 AM, you wrote:
> ?

> ?

> Anyone every seen anything like this before?? Obviously
> something is very broken but I #8217;m
> having trouble nailing down exactly what it is.? Does anyone know which components could
> be affected here?? Its only happening on one 2xge pic.

> ?

> ?

> We get this cam error for each vrrpsession we put on it:

> ?

> Dec? 6 15:37:41? re0.j1.scnet.net fpc0 GE(0/0): GEM
> failed to enable (0x44020641), link 0

> Dec? 6 15:37:41? re0.j1.scnet.net fpc0 GE(0/0): link 0
> failed to add dst entry 7 to CAM(1)

> Dec? 6 15:37:41? re0.j1.scnet.net fpc0 IFFPC: 'IFD Ether
> mfilter set' (opcode 57) failed

> Dec? 6 15:37:41? re0.j1.scnet.net fpc0 ifd 244; Ether mfilter error (1)

> Dec? 6 15:37:41? re0.j1.scnet.net fpc0 GE(0/0): link 0
> failed to add dst entry 8 to CAM(1)

> ?

> And this in general after moving traffic over some .q vlans:

> ?

> Dec? 6 16:03:27? re0.j1.scnet.net fpc0 CMFPC: PIC 0 PIO
> Read error, address 0x4028

> Dec? 6 16:03:57? re0.j1.scnet.net fpc0 last message
> repeated 30 times

> Dec? 6 16:05:57? re0.j1.scnet.net fpc0 last message
> repeated 120 times

> Dec? 6 16:08:55? re0.j1.scnet.net fpc0 last message
> repeated 178 times

> Dec? 6 16:08:56? re0.j1.scnet.net chassisd[2202]:
> No response from the other routing engine for the last 360 seconds.

> Dec? 6 16:08:56? re0.j1.scnet.net fpc0 CMFPC: PIC 0 PIO
> Read error, address 0x4028

> Dec? 6 16:08:58? re0.j1.scnet.net fpc0 last message
> repeated 2 times

> Dec? 6 16:10:58? re0.j1.scnet.net fpc0 last message
> repeated 120 times

> Dec? 6 16:15:01? re0.j1.scnet.net fpc0 last message
> repeated 243 times

> Dec? 6 16:15:02? re0.j1.scnet.net chassisd[2202]:
> No response from the other routing engine for the last 360 seconds.

> Dec? 6 16:15:02? re0.j1.scnet.net fpc0 CMFPC: PIC 0 PIO
> Read error, address 0x4028

> Dec? 6 16:15:28? re0.j1.scnet.net fpc0 last message
> repeated 26 times

> Dec? 6 16:17:28? re0.j1.scnet.net fpc0 last message
> repeated 120 times

> Dec? 6 16:21:09? re0.j1.scnet.net fpc0 last message
> repeated 220 times

> Dec? 6 16:21:09? re0.j1.scnet.net chassisd[2202]:
> No response from the other routing engine for the last 360 seconds.

> Dec? 6 16:21:10? re0.j1.scnet.net fpc0 CMFPC: PIC 0 PIO
> Read error, address 0x4028

> Dec? 6 16:21:29? re0.j1.scnet.net fpc0 last message
> repeated 19 times

> Dec? 6 16:23:29? re0.j1.scnet.net fpc0 last message
> repeated 120 times

> ?

> ?

> I have plenty more similar logs if anyone has an idea.

> ?

> Thanks,
> Jordan

> --

> Jordan Lowe
> Server Central Network
> (888) 875-4804 x255

> ?