Community Talk

Hello,

We are having problems with a fpc, that is restarting or rebooting constantly on a Juniper MX480.  In the log We can see that:

Dec 22 10:08:25 jddosd[92830]: DDOS_PROTOCOL_VIOLATION_SET: Warning: Host-bound traffic for protocol/exception NDPv6:invalid-hop-limit exceeded its allowed bandwidth at fpc 2 for 21 times, started at 2022-12-22 10:08:24 CET
Dec 22 10:12:36 (FPC Slot 1, PIC Slot 0) ms10 xntpd: kernel time sync enabled 2001
Dec 22 10:13:41 jddosd[92830]: DDOS_PROTOCOL_VIOLATION_CLEAR: INFO: Host-bound traffic for protocol/exception NDPv6:invalid-hop-limit has returned to normal. Its allowed bandwith was exceeded at fpc 2 for 21 times, from 2022-12-22 10:08:24 CET to 2022-12-22 10:08:40 CET
Dec 22 10:27:09 kernel: hw.chassis.startup_time update to 1649204745.374658
Dec 22 10:34:42 jddosd[92830]: DDOS_PROTOCOL_VIOLATION_SET: Warning: Host-bound traffic for protocol/exception NDPv6:invalid-hop-limit exceeded its allowed bandwidth at fpc 2 for 22 times, started at 2022-12-22 10:34:41 CET
Dec 22 10:39:56 jddosd[92830]: DDOS_PROTOCOL_VIOLATION_CLEAR: INFO: Host-bound traffic for protocol/exception NDPv6:invalid-hop-limit has returned to normal. Its allowed bandwith was exceeded at fpc 2 for 22 times, from 2022-12-22 10:34:41 CET to 2022-12-22 10:34:55 CET
Dec 22 10:41:07 jddosd[92830]: DDOS_PROTOCOL_VIOLATION_SET: Warning: Host-bound traffic for protocol/exception NDPv6:invalid-hop-limit exceeded its allowed bandwidth at fpc 2 for 23 times, started at 2022-12-22 10:41:06 CET
Dec 22 10:46:11 jddosd[92830]: DDOS_PROTOCOL_VIOLATION_CLEAR: INFO: Host-bound traffic for protocol/exception NDPv6:invalid-hop-limit has returned to normal. Its allowed bandwith was exceeded at fpc 2 for 23 times, from 2022-12-22 10:41:06 CET to 2022-12-22 10:41:10 CET
Dec 22 11:03:22 fpc0 MQCHIP(0) PT Missing sop/eop errors from input blocks
Dec 22 11:03:24 last message repeated 2 times
Dec 22 11:12:42 kernel: tcp_timer_keep: Dropping socket connection due to keepalive timer expiration, idle/intvl/cnt: 300/300/5
Dec 22 11:12:42 kernel: tcp_timer_keep:Local(0x80000001:6987) Foreign(0x80000010:41147)
Dec 22 11:12:42 kernel: tcp_timer_keep: Dropping socket connection due to keepalive timer expiration, idle/intvl/cnt: 300/300/5
Dec 22 11:12:42 kernel: tcp_timer_keep:Local(0x80000001:6988) Foreign(0x80000010:41148)
Dec 22 11:12:43 kernel: tcp_timer_keep: Dropping socket connection due to keepalive timer expiration, idle/intvl/cnt: 1000/500/5
Dec 22 11:12:43 kernel: tcp_timer_keep:Local(0x80000001:33072) Foreign(0x80000010:40962)
Dec 22 11:12:44 datapath-traced[92835]: datapath_traced_connection_event_handler: Disconnected from MSPMAND
Dec 22 11:12:45 kernel: tcp_timer_keep: Dropping socket connection due to keepalive timer expiration, idle/intvl/cnt: 1000/1000/5
Dec 22 11:12:45 kernel: tcp_timer_keep:Local(0x80000001:6157) Foreign(0x80000010:40964)
Dec 22 11:12:45 kernel: tcp_timer_keep: Dropping socket connection due to keepalive timer expiration, idle/intvl/cnt: 3000/1000/3
Dec 22 11:12:45 kernel: tcp_timer_keep:Local(0x80000001:6985) Foreign(0x80000010:41145)
Dec 22 11:12:45 kernel: tcp_timer_keep: Dropping socket connection due to keepalive timer expiration, idle/intvl/cnt: 1000/1000/5
Dec 22 11:12:45 kernel: tcp_timer_keep:Local(0x80000001:32780) Foreign(0x80000010:40966)
Dec 22 11:12:46 chassisd[91722]: CHASSISD_I2CS_READBACK_ERROR: Readback error from I2C slave for FPC 0 ([0x12, 0xf] -> 0x0)
Dec 22 11:12:46 kernel: tcp_timer_keep: Dropping socket connection due to keepalive timer expiration, idle/intvl/cnt: 1000/1000/5
Dec 22 11:12:46 kernel: tcp_timer_keep:Local(0x80000001:6021) Foreign(0x80000010:40960)
Dec 22 11:12:46 kernel: PCF8584(RD): target ack timeout
Dec 22 11:12:46 kernel: PCF8584(RD): (i2c_s1=0x08, group=0x12, device=0x54)
Dec 22 11:12:46 kernel: PCF8584(RD): target ack timeout
Dec 22 11:12:46 kernel: PCF8584(RD): (i2c_s1=0x08, group=0x12, device=0x54)
Dec 22 11:12:46 kernel: PCF8584(RD): target ack timeout
Dec 22 11:12:46 kernel: PCF8584(RD): (i2c_s1=0x08, group=0x12, device=0x54)
Dec 22 11:12:46 chassisd[91722]: CHASSISD_IPC_CONNECTION_DROPPED: Dropped IPC connection for FPC 0
Dec 22 11:12:46 chassisd[91722]: CHASSISD_IPC_WRITE_ERR_NULL_ARGS: FRU has no connection arguments fru_send_msg FPC 0
Dec 22 11:12:46 chassisd[91722]: CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(0)
Dec 22 11:12:46 kernel: tcp_timer_keep: Dropping socket connection due to keepalive timer expiration, idle/intvl/cnt: 1000/1000/5
Dec 22 11:12:46 kernel: tcp_timer_keep:Local(0x80000001:6166) Foreign(0x80000010:40961)
Dec 22 11:12:46 kernel: if_pfe_ams_process_single_event: ifd:mams-0/0/0, ev = AMS_EV_MEMBER_DEL agg_state UP, member_state: ACTIVE, member_present_count = 2
Dec 22 11:12:46 kernel: if_pfe_ams_update_per_member_nh: Unknown operation (0) on
Dec 22 11:12:46 kernel: if_pfe_ams_update_per_member_nh: Unknown operation (0) on
Dec 22 11:12:46 mib2d[92851]: SNMP_TRAP_LINK_DOWN: ifIndex 522, ifAdminStatus up(1), ifOperStatus down(2), ifName ms-0/0/0
Dec 22 11:12:46 mib2d[92851]: SNMP_TRAP_LINK_DOWN: ifIndex 523, ifAdminStatus up(1), ifOperStatus down(2), ifName mams-0/0/0


and typing the commands:

start shell pfe network fpc0
show nvram

We can see many messages with Data TLB Miss :

System Exception: Vector/Code 0x00e00, Signal 11
Event occurred at: Dec 21 04:53:27.991832

Juniper Embedded Microkernel Version 20.4R3.8
Built by builder on 2021-09-07 17:10:19 UTC
Copyright (C) 1998-2021, Juniper Networks, Inc.
All rights reserved.
Reason string: "Data TLB Miss"
Context: Thread (TTP Transmit)

Which could be the problem with the pfc restarting?

Thank you

Regards