[j-nsp] Weird FPC errors MX480

Paul Stewart paul at paulstewart.org
Fri Mar 21 10:53:28 EDT 2014


Hey there…



MX480 running 11.4R9.4 and I’m getting weird error logs from a MPC2-3D with
a pair of 4X10G MIC cards:



Mar 21 10:33:26  core2.toronto1 fpc2 PPE Sync XTXN Err Trap:  Count 3322791,
PC 617d, 0x617d:  flow_age_read_active_timestamp     0x617d:  flow_age_ipv4

Mar 21 10:33:28  core2.toronto1 fpc2 LUCHIP(1) PPE_3 Errors sync xtxn error

Mar 21 10:33:28  core2.toronto1 fpc2 PPE Sync XTXN Err Trap:  Count 3322792,
PC 617d, 0x617d:  flow_age_read_active_timestamp     0x617d:  flow_age_ipv4

Mar 21 10:33:33  core2.toronto1 fpc2 LUCHIP(1) PPE_15 Errors sync xtxn error

Mar 21 10:33:33  core2.toronto1 fpc2 PPE Sync XTXN Err Trap:  Count 3322793,
PC 617d, 0x617d:  flow_age_read_active_timestamp     0x617d:  flow_age_ipv4

Mar 21 10:33:42  core2.toronto1 fpc2 LUCHIP(1) PPE_2 Errors sync xtxn error

Mar 21 10:33:42  core2.toronto1 fpc2 PPE Sync XTXN Err Trap:  Count 3322794,
PC 617d, 0x617d:  flow_age_read_active_timestamp     0x617d:  flow_age_ipv4

Mar 21 10:33:43  core2.toronto1 fpc2 LUCHIP(1) PPE_6 Errors sync xtxn error

Mar 21 10:33:43  core2.toronto1 fpc2 PPE Sync XTXN Err Trap:  Count 3322795,
PC 617d, 0x617d:  flow_age_read_active_timestamp     0x617d:  flow_age_ipv4

Mar 21 10:33:48  core2.toronto1 fpc2 LUCHIP(1) PPE_11 Errors sync xtxn error

Mar 21 10:33:48  core2.toronto1 fpc2 PPE Sync XTXN Err Trap:  Count 3322796,
PC 617d, 0x617d:  flow_age_read_active_timestamp     0x617d:  flow_age_ipv4



JTAC told me this is cosmetic but I am not convinced.  Anyone run across
this before?  It has been ongoing for a while and did not create any service
impact however this morning we started dropping packets on at least one port
and have not ruled out the card as a potential issue.

Thanks,

Paul





More information about the juniper-nsp mailing list