SRX

 View Only
last person joined: 2 days ago 

Ask questions and share experiences about the SRX Series, vSRX, and cSRX.
  • 1.  reboot reason

    Posted 09-09-2024 03:39
    I would like to know why this device rebooted
    Sometimes the SRX reboots.
    The boot reason is given in the form of a code
    But I don't know the details.
    Juniper does not provide documentation on the boot reason codes
    Does anyone know?

    Routing Engine status:
        Temperature                 33 degrees C / 91 degrees F
        CPU temperature             61 degrees C / 141 degrees F
        Total memory              4096 MB Max  1270 MB used ( 31 percent)
          Control plane memory    2624 MB Max   761 MB used ( 29 percent)
          Data plane memory       1472 MB Max   500 MB used ( 34 percent)
        5 sec CPU utilization:
          User                      10 percent
          Background                 0 percent
          Kernel                     6 percent
          Interrupt                  0 percent
          Idle                      84 percent
        Model                          RE-SRX340

       Start time                     2024-09-09 15:01:34 KST
        Uptime                         1 hour, 21 minutes, 55 seconds
        Last reboot reason             0x800:reboot due to exception
        Load averages:                 1 minute   5 minute  15 minute
                                           0.14       0.21       0.18

    root@EXT_VPN% sysctl hw.re.reboot_reason hw.re.reboot_reason: 1
    hw.re.reboot_reason: 2048
    sysctl: unknown oid 'hw.re.reboot_reason:'



    ------------------------------
    SUNGHO YOON
    ------------------------------


  • 2.  RE: reboot reason

    Posted 30 days ago

    There's a good chance that a memory dump was saved when the exception occurred. Check with show system core-dumps. The name of the dump file may give you a clue as to the component that caused the exception. The memory dumps can be reviewed by JTAC for further analysis.

    You should also review system log messages recorded immediately before the crash as those may contain clues about events that led up to the crash.



    ------------------------------
    Nikolay Semov
    ------------------------------