The ODD thing is happening, i receive these logs:
Fru Offline (jnxFruContentsIndex 9, jnxFruL1Index 2, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName Routing Engine 1, jnxFruType 6, jnxFruSlot 1, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 0)
but when i look into >show routing-engine it never was offline.
Model RE-S-1800x4Start time 2019-09-08 00:42:48 CESTUptime 41 days, 1 hour, 8 minutes, 35 secondsLast reboot reason Router rebooted after a normal shutdown.Load averages: 1 minute 5 minute 15 minute0.60 0.39 0.28
fxp0 was checked it didn't flap :
Physical interface: fxp0, Enabled, Physical link is UpInterface index: 64, SNMP ifIndex: 1, Generation: 3Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Clocking: Unspecified, Speed: 1000mbpsDevice flags : Present RunningInterface flags: SNMP-TrapsLink type : Full-DuplexPhysical info : UnspecifiedHold-times : Up 0 ms, Down 0 msDamping : half-life: 0 sec, max-suppress: 0 sec, reuse: 0, suppress: 0, state: unsuppressedAlternate link address: UnspecifiedLast flapped : 2019-09-08 00:24:37 CEST (5w6d 01:26 ago)
What can be the cause of that logs? how to solve the issue ?
Can you please confirm what kind of Juniper device yo are refering to? Is it a dual RE device or a single RE?In case of dual RE system sometimes REs do not fail but the keepalive failure might have happen which will give wrong ideas about the backup RE status.
Please share the logs right before the offline error. Also, complete "show chassis routing-engine" output
PS: If my reply answers your question please accept it as solution, kudos are appreciated too!!
its a dual RE system.
For some reason RE1 keepalives are lost and thats why RE0 is logging it as offline. Also there are no any more logs that indicate to a problem
Oct 19 00:45:00 event = E_NO_IPC, state = master, param = 0x0x0Oct 19 00:45:00 currentAction = A_WARN1
Oct 19 00:45:00 No response from the other routing engine for the last 2 seconds.
Oct 19 00:45:00 Currentstate master NextState master reason_code 1Oct 19 00:45:00 new state = masterOct 19 00:45:00 vc master RE state change: in-synch -> initializingOct 19 00:45:00 vc master RE append vc ext disabledOct 19 00:45:00 send hello/REinfo packetOct 19 00:45:00 slot:0 send RE_INFOOct 19 00:45:06 event = E_ORE_B, state = master, param = 0x0xa021008Oct 19 00:45:06 currentAction = A_NOOP
Oct 19 00:45:06 Currentstate master NextState master reason_code 1Oct 19 00:45:06 new state = masterOct 19 00:45:06 vc master RE state change: initializing -> synchingOct 19 00:45:06 vc master RE append vc ext enabledOct 19 00:45:06 slot:0 send RE_INFOOct 19 00:45:06 vc master RE recv backup RE vc data, mid=255 sn=ÿÿÿÿÿÿÿÿÿÿÿÿ slots=8Oct 19 00:45:06 vc master RE state change: synching -> in-synch
I think you got the answer for your question about the log message,
One of the reason could be CPU high condition in Master RE due to which it missed the keepalive from backup RE
More details are availabe in the KB - https://kb.juniper.net/InfoCenter/index?page=content&id=KB27703&actp=METADATA
Please accept the solution, if it answred your query
Could you please confirm if you are seeing keepalive loss log before FRU offline log,
Please check if this KB helps you
Please accept my solution, if it resolved your query