Description

Mx204 was rebooted with reboot reason as panic. 
root@mx> show version detail no-forwarding
Hostname: mx
Model: mx204
Junos: 22.2R3-S2.8 
root@mx> show system core-dumps no-forwarding
 -rw------- 1 root wheel 1700675584 Mar 16 04:59 /var/crash/vmcore.0
lrwxr-xr-x 1 root wheel         8 Mar 16 04:59 /var/crash/vmcore.last@ -> vmcore.0
/var/tmp/*core*: No such file or directory
/var/tmp/pics/*core*: No such file or directory
/var/crash/kernel.*: No such file or directory
/var/jails/rest-api/tmp/*core*: No such file or directory
/tftpboot/corefiles/*core*: No such file or directory
total files: 2 
root@mx> show chassis routing-engine no-forwarding
 Routing Engine status:
   Temperature                41 degrees C / 105 degrees F
   CPU temperature            41 degrees C / 105 degrees F
   DRAM                     16330 MB (16384 MB installed)
   Memory utilization         17 percent
   Model                         RE-S-1600x8
   Start time                    2024-03-16 04:56:58 WIB
   Uptime                        7 hours, 12 minutes, 24 seconds
   Last reboot reason            0x1000:reboot due to panic
   Load averages:                1 minute  5 minute 15 minute
                                      0.57      0.54      0.57 
   et-0/0/2 {
       flexible-vlan-tagging;
       mtu 9192;
       encapsulation flexible-ethernet-services;
       unit 3029 {
           vlan-id 3029;
           family inet {
               accounting {
                   source-class-usage {
                       input;
                       output;
                   }
               } 
Continuous SNMP polling for an extended period on Junos platforms with SCU/DCU configurations will lead to a kernel crash. 
The crash is associated with a NULL check failure, attributed to the uninitialised parameters for name length and class name, resulting in traffic disruption. 
The VMhost also got disconnected and rebooted, please take the fix of the below PR. 
./messages:2024-03-16T04:56:41.062165+07:00 mx-node kernel: High host-mode time vcpu 1 delay 671761 us exit reason EXTERNAL_INTERRUPT rip 0x0 info 0 800000fd
./messages:2024-03-16T04:56:41.062181+07:00 mx-node kernel: High host-mode time vcpu 2 delay 671761 us exit reason EXTERNAL_INTERRUPT rip 0x0 info 0 800000fd
./messages:2024-03-16T04:56:41.062182+07:00 mx-node kernel: High host-mode time vcpu 4 delay 671756 us exit reason EXTERNAL_INTERRUPT rip 0x0 info 0 800000fd
./messages:2024-03-16T04:56:41.062183+07:00 mx-node kernel: High host-mode time vcpu 3 delay 671759 us exit reason EXTERNAL_INTERRUPT rip 0x0 info 0 800000fd
./messages-2024-03-16T04:56:41.457208+07:00 mx-node kernel: High host-mode time vcpu 0 delay 237825 us exit reason IO_INSTRUCTION rip 0xec1f0 info cfc0003 0 

Symptoms

Continuous polling of SCU/DCU using snmp.

Solution

Need to take fix of the below PR.
https://prsearch.juniper.net/PR1767098 
Resolved-In
junos:22.1R3-S5 junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R3 junos:23.2R2 junos:23.4R1 junos:23.4R2 junos:24.1R1

Modification History

2024-03-26 : Article Created