The error looks like the cfeb went bad. I think it was trying to read stats off the ASIC but failed.
Did you try to reset it? -Pasvorn On 8/23/11, [email protected] <[email protected]> wrote: > Hi, > > My Juniper M10 router interfaces suddenly became unreachable. After getting > someone to the remote site and rebooting it, the interfaces were reachable > again. A close look at the logs points to issues with the cfeb just before > the loss. Am I losing my cfeb or I should be looking at the chassis? Do I > have to be looking at changing the router altogether? > > > The log > > Aug 24 02:36:22 xxx cfeb IA_PIO(0, 0): REG PIO RD timeout addr 0xf0c01020 > data 0x02000010 status 4 > Aug 24 02:36:22 xxx cfeb IA_PIO(0, 0): REG PIO RD timeout addr 0xf0c01004 > data 0x02000010 status 4 > Aug 24 02:36:22 xxx cfeb IA_PIO(0, 0): REG PIO WR timeout addr 0xf0c01004 > data 0x07ffffff status 4 > Aug 24 02:36:22 xxx cfeb IA_PIO(0, 0): REG PIO RD timeout addr 0xf0600420 > data 0x02000010 status 4 > Aug 24 02:36:22 xxx cfeb IA_PIO(0, 0): REG PIO WR timeout addr 0xf0600420 > data 0xffffffff status 4 > Aug 24 02:36:22 xxx cfeb IA_PIO(0, 0): REG PIO RD timeout addr 0xf0600820 > data 0x02000010 status 4 > Aug 24 02:36:22 xxx cfeb IA_PIO(0, 0): REG PIO WR timeout addr 0xf0600820 > data 0xffffffff status 4 > Aug 24 02:36:23 xxx cfeb IA_PIO(0, 0): REG PIO RD timeout addr 0xf0600c20 > data 0x02000010 status 4 > Aug 24 02:36:23 xxx cfeb IA_PIO(0, 0): REG PIO WR timeout addr 0xf0600c20 > data 0xffffffff status 4 > Aug 24 02:36:23 xxx cfeb IA_PIO(0, 0): REG PIO WR timeout addr 0xf0601020 > data 0x00000000 status 4 > Aug 24 02:36:23 xxx cfeb IA_RPKT(0, 0): hardware error, invalid db > pointer0x0, ia_rpkt_coalesce > Aug 24 02:36:30 xxx last message repeated 69 times > Aug 24 02:36:30 xxx cfeb IA_PCIIF(0): IA Bus 0 RXIF error, > ia_pciif_internal_error_check > Aug 24 02:36:30 xxx cfeb IA_RXIF(0, 0): Error Symbol: CRC Error > Aug 24 02:36:31 xxx cfeb IA_PCIIF(0): IA Bus 0 RXIF error, > ia_pciif_internal_error_check > Aug 24 02:36:51 xxx /kernel: > Aug 24 02:36:51 xxx /kernel: so-0/1/0.0 down: no keepalive. > Aug 24 02:36:51 xxx mib2d[1383]: SNMP_TRAP_LINK_DOWN: ifIndex 520, > ifAdminStatus up(1), ifOperStatus down(2), ifName so-0/1/0 > Aug 24 02:36:51 xxx rpd[1354]: bgp_ifachange_group:6251: NOTIFICATION sent > to a.a.a.a (External AS 6453): code 6 (Cease) subcode 6 (Other Configuration > Change), Reason: Interface change for the peer-group > Aug 24 02:37:01 xxx rpd[1354]: RPD_OSPF_NBRDOWN: OSPF neighbor b.b.b.b > (realm ospf-v2 ge-0/0/0.0 area 0.0.0.0) state changed from Full to Down due > to InActiveTimer (event reason: neighbor was inactive and declared dead) > Aug 24 02:37:52 xxx rpd[1354]: bgp_hold_timeout:3646: NOTIFICATION sent to > c.c.c.c (Internal AS 36961): code 4 (Hold Timer Expired Error), Reason: > holdtime expired for c.c.c.c (Internal AS 36961), socket buffer sndcc: 100 > rcvcc: 0 TCP state: 4, snd_una: 2293409040 snd_nxt: 2293409121 snd_wnd: > 16270 rcv_nxt: 1113804713 rcv_adv: 1113821097, hold timer 0 > > > Emmanuel > > > > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > -- Sent from my mobile device _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
