CHASSISD_TIMER_VAL_ERR

The CHASSISD_TIMER_VAL_ERR message is reported into the system message file whenever the chassis control process (chassisd) receives a null identifier from a timer and thus it could not clear the timer. This article documents an approach to troubleshoot this problem.

The CHASSISD_TIMER_VAL_ERR message is logged each time chassisd receives a null identifier from a timer and thus it could not clear the timer.

When chassisd receives a null identifier from a timer and thus cannot clear the timer, it logs the message into the syslog. This can occur when the chassisd process starts a timer to track the timeout period for an event, and the timer returns a null identifier, so the chassisd process could not clear the timer. Below are examples of the message reported:

The cause for this message is an ‘event’ that occurred on a Field Replaceable Unit (FRU) which caused it to send a null timer ID to chassisd. The ‘event’ may be a hardware failure of the FRU, a fault in the communication link between the FRU and the midplane, a crash of the FRU, a transient issue on the FRU, or a user initiated action on the FRU (offline/online).

Review the output of show log messages and show log chassisd. Look carefully at the messages that occur just before or after the CHASSISD_TIMER_VAL_ERR message to identify the FRU that was the source of the timer response. Messages of the following types can identify the FRU:

If the CHASSISD_TIMER_VAL_ERR message only occurs a few times in the logs, then it is likely due to a transient issue on the FRU.

If the surrounding messages indicate that the FRU was taken offline or brought online by a CLI command, then the CHASSISD_TIMER_VAL_ERR message is likely due to a user initiated action on the FRU.

If the surrounding messages indicate that the FRU restarted without user interaction, then the CHASSISD_TIMER_VAL_ERR message is likely due to a FRU crash.

If the surrounding messages indicate hardware issues with the FRU, then the CHASSISD_TIMER_VAL_ERR message is likely due to a hardware failure.

If the CHASSISD_TIMER_VAL_ERR message occurs continuously, troubleshooting actions outlined in the next section need to be done to isolate the source of the error.

If the CHASSISD_TIMER_VAL_ERR messages are due to a transient issue, monitor the router for a reoccurence of the messages.

If the CHASSISD_TIMER_VAL_ERR message is due to a user initiated action on the FRU then no action is required. These messages are normal when an FRU is taken offline.

If the CHASSISD_TIMER_VAL_ERR messages are due to a hardware failure, open a case with your technical support representative.

If the CHASSISD_TIMER_VAL_ERR messages are due to a FRU crash, monitor the router for a reoccurence of the FRU crash. If the FRU crashes repeatedly, open a case with your technical support representative.

If the CHASSISD_TIMER_VAL_ERR message occurs continuously, perform the following steps in a maintenance window:

  1. Take the FRU offline.
  2. Reseat the FRU.
  3. If needed, bring the FRU back online.

If the messages do not return immediately, monitor the router for a reoccurrence.

If the messages return, perform the following steps (if possible) in a maintenance window:

  1. Take the FRU offline.
  2. Remove the FRU.
  3. Insert the FRU into a different slot in the router.
  4. If needed, bring the FRU back online.

If the messages continue, open a case with your technical support representative.
If the messages do not continue, perform the following steps (if possible) in a maintenance window:

  1. Take the FRU offline.
  2. Remove the FRU.
  3. Insert the FRU into the original slot in the router.
  4. If needed, bring the FRU back online.
  5. Open a case with your technical support representative.

About the author

Prasanna

Leave a Comment