Customer turned off the equipment and after solving the power issue, the equipment was turned on, however, when the equipment was up) the alarm: Major Host 1 : Chassis Manager connection down was present. The traffic is not affected now, however, our customer requests the solution to remove this alarm.
From chassisd
test_router chassisd[19079]: CHASSISD_SNMP_TRAP7: SNMP trap generated: Fru Online (jnxFruContentsIndex 9, jnxFruL1Index 2, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName Routing Engine 1, jnxFruType 6, jnxFruSlot 1)
test_router chassisd[19079]: CHASSISD_SNMP_TRAP3: ENTITY trap generated: entStateOperEnabled (entPhysicalIndex 55, entStateAdmin 4, entStateAlarm 0)
test_router chassisd[19079]: CHASSISD_SNMP_TRAP0: ENTITY trap generated: entConfigChanged
test_router alarmd[19475]: Alarm cleared: RE id=218104169, color=YELLOW, class=CHASSIS, reason=Loss of communication with Backup RE
test_router chassisd[19079]: CHASSISD_ZONE_BLOWERS_SPEED: Fans and impellers in zone 0 are now running at normal speed
test_routeralarmd[19475]: Alarm set: RE id=989856105, color=RED, class=CHASSIS, reason=Host 1 : Chassis Manager connection down
23:26:58 test_router eventd: sendto: No route to host
23:26:58 test_router eventd[19082]: SYSTEM_ABNORMAL_SHUTDOWN: System abnormally shut down
23:26:58 test_router eventd[19082]: SYSTEM_OPERATIONAL: System is operational
test_router alarm-mgmtd[19641]: LIBJSNMP_SA_IPC_REG_ROWS: ns_subagent_register_mibs: registering 5 rows
test_router alarm-mgmtd[19641]: LIBJSNMP_NS_LOG_WARNING: WARNING: Warning: Failed to connect to the agentx master agent (/var/run/snmpd_agentx): Unk
test_router jlaunchd: Alarm set command: /usr/sbin/cli (PID 19787) started
test_router chassisd[19139]: CHASSISD_SNMP_TRAP3: ENTITY trap generated: entStateOperEnabled (entPhysicalIndex 54, entStateAdmin 4, entStateAlarm 0)
On rare bootups the RE-RE (RE - Routing-Engine)link reaches a wedge condition where broadcast packets are received correctly, but unicast packets are not. The afflicted RE would need to be rebooted for the RE-RE link to resume functionality. Kindly reboot the RE affected to re-link the REs communication.