Description

High Chassisd CPU usage (70-80%) due to phone-home configuration preventing the execution of chassis-related commands.

Symptoms

With following phone-home configuration present:

 

set system phone-home rfc-compliant

 

High Chassisd CPU usage (70-80%) observed

 

root@device> show system processes extensive no-forwarding

 

last pid: 50779; load averages: 1.21, 1.01, 0.82 up 4+17:12:09   10:50:53

506 threads:  6 running, 449 sleeping, 2 zombie, 49 waiting

CPU: 0.8% user, 0.0% nice, 1.9% system, 0.1% interrupt, 97.1% idle

Mem: 537M Active, 3725M Inact, 1212M Wired, 444M Buf, 88G Free

Swap: 12G Total, 12G Free

 

 PID USERNAME   PRI NICE  SIZE   RES STATE   C  TIME   WCPU COMMAND

16877 root        94   0  924M  118M CPU2    2 355:08 72.46% chassisd{chassisd}

 

 

Since the master RE is hung, the backup RE becomes the master:

 

root@device> show chassis routing-engine no-forwarding

Alarm time               Class  Description

2025-02-22 13:47:30 IST  Major  RE1 network-service mode mismatch between configuration and kernel setting

2025-02-22 13:47:25 IST  Minor  Backup RE Active

 

The following log messages are continuously seen:

 

Mar 1 19:55:43 AIU: port_speed_txn_timer_handler jdhcpd_aiu_state is -1 phc state is 1

Mar 1 19:55:43 AIU: port_speed_txn_timer_handler aiu is not bound yet,do speed transition

Mar 1 19:55:43 PHC_MRATE AIU: fpc_port_speed_change_conf_commit CHASD_MRATE_CONF_FILE open failed with errno: 24: Too many open files

Mar 1 19:55:43 AIU: port_speed_txn_timer_handler Restart Timer,do speed transition

Mar 1 19:55:48 CHASSISD_FILE_OPEN: File open: /dev/hgcommdev, error: 24 -- Too many open files

Mar 1 19:55:48 CHASSISD_FILE_OPEN: File open: /dev/hgcommdev, error: 24 -- Too many open files

 

We have observed frequent logs related to Routing Engine 0 with Fru Online on thedevice. Below are some of the log entries:

 

Feb 24 08:30:12  <device> chassisd[24103]: CHASSISD_SNMP_TRAP7: SNMP trap generated: Fru Online (jnxFruContentsIndex 9, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName Routing Engine 0, jnxFruType 6, jnxFruSlot 0)

Feb 24 08:30:12  <device> chassisd[24103]: CHASSISD_SNMP_TRAP3: ENTITY trap generated: entStateOperEnabled (entPhysicalIndex 66, entStateAdmin 4, entStateAlarm 128)

Feb 24 08:30:52  <device> chassisd[24103]: CHASSISD_SNMP_TRAP7: SNMP trap generated: Fru Online (jnxFruContentsIndex 9, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName Routing Engine 0, jnxFruType 6, jnxFruSlot 0)

 

Solution

The phone-home configuration is designed for bootstrapping systems with factory settings. Therefore, “set system phone-home” is included only in the factory configuration and should not be explicitly configured or added to the base configuration. Remove the phone-home configuration using the command

delete system phone-home

Modification History

2025-03-20 : Article Created