Description

On GGSN J120/J20 running R5 2009A, based on Junos 9.0R4.5, upon every configuration commit or commit check, customer is seeing following syslog messages: kernel: control-cores 3 data-cores 0 debugger-on-panic 13

Symptoms

On GGSN J120/J20 running R5 2009A, based on Junos 9.0R4.5, upon every configuration commit or commit check, or when the GGSN PICs are initializing, customer is seeing messages similar to the ones below in the file messages.

user@J120> monitor start message | match control-core
Jul 2 13:03:21 j120 (FPC Slot 2, PIC Slot 1) kernel: control-cores 3 data-cores 0 debugger-on-panic 13
Jul 2 13:03:21 j120 (FPC Slot 2, PIC Slot 0) kernel: control-cores 3 data-cores 0 debugger-on-panic 13
Jul 2 13:03:21 j120 (FPC Slot 2, PIC Slot 3) kernel: control-cores 3 data-cores 255 debugger-on-panic 255
...
Nov 24 13:32:20 j120 (FPC Slot 2, PIC Slot 1) kernel: control-cores 3 data-cores 0 debugger-on-panic 0
Nov 24 13:32:19 j120 (FPC Slot 2, PIC Slot 3) kernel: control-cores 3 data-cores 0 debugger-on-panic 0
Nov 24 13:32:19 j120 (FPC Slot 2, PIC Slot 0) kernel: control-cores 3 data-cores 0 debugger-on-panic 0
...
In order to check severity information, insert in the syslog configuration "explicit-priority".
More details about severity messages can be found in online documentation: Including Priority Information in System Log Messages
user@J120# show system sylog file messages
any notice;
authorization info;
explicit-priority;

user@J120# run monitor start messages | match control-core
user@J120# commit synchronize
 ...
Dec 10 12:51:34 J120 (FPC Slot 2, PIC Slot 0) kernel: %USER- 2 : control-cores 3 data-cores 0 debugger-on-panic 0

Having explicit-priority configured, it can be seen that the syslog message has severity level 2.

Solution

There is no concern about this type of syslog messages as they are of informational nature.

A Problem Report (PR) is being created by JTAC to modify the severity level of such messages.