Description

Error Message Seen " fpcx gencfg no msg handlers for gencfg msg command 2"

Symptoms

Mar 9 14:11:06.037 MX960_re0 fpc1 gencfg no msg handlers for gencfg msg command 2
Mar 9 14:11:06.037 MX960_re0 fpc3 gencfg no msg handlers for gencfg msg command 2
Mar 9 14:11:06.038 MX960_re0 fpc9 gencfg no msg handlers for gencfg msg command 2
Mar 9 14:11:13.221 MX960_re0 fpc7 gencfg no msg handlers for gencfg msg command 2
Mar 9 14:11:13.221 MX960_re0 fpc7 gencfg no msg handlers for gencfg msg command 2
Mar 9 14:11:13.342 MX960_re0 fpc0 gencfg no msg handlers for gencfg msg command 2
Mar 9 14:11:13.342 MX960_re0 fpc0 gencfg no msg handlers for gencfg msg command 2
Mar 9 14:11:13.342 MX960_re0 fpc7 gencfg no msg handlers for gencfg msg command 2

Solution

Above error messages can be seen once customer performs the below action:

1) Disabling any interface + Commit Performed --> Error seen

2) Enabling any interface + Commit Performed --> Error seen

3) Disable interface + No commit performed --> No error seen

4) Enabling interface + No commit performed --> No error seen

5) No changes Performed + Commit Performed --> No Error seen

Jtac Observation:
================ 

+After performing the above steps multiple times we conclude that this looks more of an information message. 

+This does not have any adverse effect on the device or the network. 

Explanation on Gencfg:
================ 

+The GENCFG infrastructure provides a generic framework for publishing any information to consumers. 

+This information is stored in the kernel and then forwarded to the consumers (PFE, PIC, replicated RE, and other daemons running on the RE) who subscribe.

 Why Gencfg ?
================  

+Reduce Kernel Changes

+Lesser number of messages to handle for ISSU

+Generic Framework
 

When to use Gencfg?
================  

+Dont want the kernel to parse information

+Want replication of information

+Want to share information with PFE/PIC or other deamons
 

So above messages are just information logs which can be ignored.

 

Modification History

2024-09-26 : Article Created

2026-03/16 : Added SRX HE/Branch