Junos
Highlighted
Junos

Unusual Reboot Reason on Juniper

[ Edited ]
‎07-03-2017 06:58 AM

Hi,

 

I have the following reboot reason showing on a Juniper Model: ex2300-c-12t

 

admin@FLMD002869> show chassis routing-engine
Routing Engine status:
Slot 0:
Current state Master
Temperature 48 degrees C / 118 degrees F
CPU temperature 48 degrees C / 118 degrees F
DRAM 1951 MB
Memory utilization 22 percent
5 sec CPU utilization:
User 15 percent
Background 0 percent
Kernel 26 percent
Interrupt 1 percent
Idle 58 percent
Model RE-EX2300C-12T
Serial ID BUILTIN
Start time 2038-01-19 03:14:07 UTC
Uptime 1 day, 16 hours, 51 seconds
Last reboot reason 0x8000: swizzle reboot
Load averages: 1 minute 5 minute 15 minute
1.83 0.91 0.53

 

However we cannot find a clear explanation of the reason 0x8000: swizzle reboot it does not show anywhere on the internet when I try to google it.

 

Has anyone seen this before and know what it means?

 

 

 

regards

 

 

 

Ryan Neil

7 REPLIES 7
Highlighted
Junos

Re: Unusual Reboot Reason on Juniper

‎07-03-2017 11:00 PM

Hi,

 

There isn't any specific information on this reboot reason on Internet. However, I would suggest to check the log messages for the time of the issue which will definitely tell the reboot reason. To specifically know what is the meaning of "Last reboot reason 0x8000: swizzle reboot" JTAC is the right team.

 

 

Regards,

Rahul

 

Please mark my solution as accepted if it helped.

Highlighted
Junos

Re: Unusual Reboot Reason on Juniper

[ Edited ]
‎07-04-2017 12:32 AM

Hi,

 

The logs on the Juniper do not show anything at the time of the reboot there is nothing for that particular day which was the 1st of July

 

The logs go from the 30th of March straight to the 3rd of July which is strange as you would expect to see something when it rebooted.

 

It is bizarre that there is nothing at all on the internet regarding that reboot reason even our Juniper Ambassador has not seen this reboot reason before.

 

 

regards

 

 

Ryan Neil

 

 

Highlighted
Junos

Re: Unusual Reboot Reason on Juniper

‎07-04-2017 03:14 AM

Hi Ryan,

 

You can check the output of "show system boot-messages" and look for some clue. Also make sure there is no crash file generated.

 

Another way to find reboot reason is to login to the shell and execute the below command:

 

% sysctl hw.re.reboot_reason 
hw.re.reboot_reason: 1

 

the reboot reason will show some code which has some meaning.

I remember the below two codes only. And the codes may differ for different platform.

 

Code 0 means reboot due to power failure or power cycle.  
Code 1 is  is a reboot triggered by hardware watchdog. 

 

You are always wlecome to share any output and logs for the community members to refer.

If nothing works at all, I would suggest to contact JTAC for the reboot reason.

 

 

Regards,

Rahul

 

Please mark my solution as accepted if it helped.

 

 

Highlighted
Junos

Re: Unusual Reboot Reason on Juniper

‎07-04-2017 03:44 AM

admin@FLMD002869> show system boot-messages
fpc0:
--------------------------------------------------------------------------
GDB: debug ports: uart
GDB: current port: uart
KDB: debugger backends: ddb gdb ndb
KDB: current backend: ddb
Copyright (c) 1992-2015 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD JNPR-11.0-20160921.337570_builder_head-336320 #0 r337570: Wed Sep 21 03:56 :43 PDT 2016
builder@feyrith.juniper.net:/b/builder/freebsd-sazmac2/freebsd/head-336320/201 60921.builder.337570/obj/arm/juniper/kernels/JNPR-ARM-PRD/kernel arm
Juniper clang version 3.5.0 (tags/RELEASE_350/final)
CPU: Cortex A9-r4 rev 1 (Cortex-A core)
Supported features: ARM_ISA THUMB2 JAZELLE THUMBEE ARMv4 Security_Ext
WB disabled EABT branch prediction enabled
LoUU:2 LoC:2 LoUIS:2
Cache level 1:
32KB/32B 4-way data cache WB Read-Alloc Write-Alloc
32KB/32B 4-way instruction cache Read-Alloc
real memory = 2147483648 (2048 MB)
avail memory = 2002718720 (1909 MB)
Security policy loaded: Junos MAC/SDK (mac_sdk)
Security policy loaded: JUNOS MAC/privcheck (mac_privcheck)
Security policy loaded: MAC/veriexec (mac_veriexec)
Security policy loaded: Junos MAC/fips (mac_fips)
MAC/veriexec fingerprint module loaded: SHA1
MAC/veriexec fingerprint module loaded: SHA256
random: entropy device external interface
Initializing DCF platform properties ..
rts_sysconf_ifstate_init: registerd rtcb osd: slotid 2
Calling dcf_ng_hw_init for platform hw vecs initialization
ofwbus0: <Open Firmware Device Tree>
simplebus0: <Flattened device tree simple bus> on ofwbus0
mpcore0: <ARM Cortex-A9 MPCore> on simplebus0
bcmidm0: <Broadcom Interconnect Device Management (IDM)> mem 0x100000-0x1fffff on simplebus0
ihost_proc0: <Broadcom iHost PLL> mem 0x1000000-0x1000fff on simplebus0
l2cache0: <PL310 L2 cache controller> mem 0x1022000-0x1022fff irq 32 on mpcore0
l2cache0: Part number: 0x3, release: 0x9 (r3p3)
l2cache0: L2 Cache enabled: 256KB/32B 16 ways
gic0: <ARM Generic Interrupt Controller> mem 0x1021000-0x1021fff,0x1020100-0x10201 ff on mpcore0
gic0: pn 0x390, arch 0x1, rev 0x2, implementer 0x43b irqs 256
mp_tmr0: <ARM MPCore Timers> mem 0x1020200-0x10202ff,0x1020600-0x102061f irq 27,29 on mpcore0
Timecounter "MPCore" frequency 625000000 Hz quality 800
Event timer "MPCore" frequency 625000000 Hz quality 1000
cmic0: <Broadcom CMIC> mem 0x3200000-0x32fffff irq 221 on ofwbus0
cmic0: called :bcm_cmic_attach,Dev Chip Id is 0x1b063:
bcmdmu0: <Broadcom BCM56XXX dmu> mem 0xf000-0xffff on simplebus0
bcm560xgmac0: <Broadcom-56060 GMAC> mem 0x42000-0x42fff irq 142 on simplebus0
bcmidm0: chip dev id :0x1b063
miibus0: <MII bus> on bcm560xgmac0
brgphy0: <BCM54616S 10/100/1000baseTX PHY> PHY 1 on miibus0
brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-mas ter, 1000baseT-FDX, 1000baseT-FDX-master, auto
ehci0: <BCMIPROC-USB-EHCI> mem 0x48000-0x49fff irq 104 on simplebus0
ehci0: called :bcmusb_ehci_attach,Dev Chip Id is 0x1b063:
usbus0: EHCI version 1.0
usbus0 on ehci0
gpio0: <Broadcom BCM56XXX GPIO controller> mem 0xa000-0xa0ff irq 116 on simplebus0
gpiobus0: <GPIO bus> on gpio0
gpioc0: <GPIO controller> on gpio0
uart0: <16750 or compatible> mem 0x20000-0x200ff irq 105 on simplebus0
uart0: console (9600,n,8,1)
uart0: [GIANT-LOCKED]
uart1: <16750 or compatible> mem 0x21000-0x210ff irq 106 on simplebus0
uart1: [GIANT-LOCKED]
iichb0: <Broadcom iProc SMBus Controller> mem 0x8000-0x8fff irq 117 on simplebus0
iicbus0: <OFW I2C bus> on iichb0
iic0: <I2C generic I/O> on iicbus0
iicswitch0: <I2C Switch/Multiplexer> at addr 0x70 on iicbus0
poe0: <POE> on iicswitch0
poe reset failed
rtc8564je_rtc0: <EPSON 8564JE Real Time Clock(RTC)> on iicswitch0
cpld0: <Juniper CPLD for iProc> at addr 0x31 on iicbus0
cpldbus0: <CPLD Functions> on cpld0
wdog0: <CPLD Watchdog Timer for iProc> on cpldbus0
oamctl0: <OAM Control using CPLD for iProc> on cpldbus0
fan0: <CPLD fan controller> on cpldbus0
fan1: <CPLD fan controller> on cpldbus0
resetctrl0: <I2C switch reset driver> on cpldbus0
bcmcru0: <Broadcom BCM56XXX cru> mem 0xe000-0xefff on simplebus0
spi0: <Broadcom BCM56XXX SPI> mem 0x47000-0x47fff irq 102 on simplebus0
spibus0: <OFW SPI bus> on spi0
mx25l0: <M25Pxx Flash Family> at cs 0 on spibus0
mx25l0: mx25ll64, sector 65536 bytes, 128 sectors
cryptosoft0: <software crypto>
Initializing product: 169 ..
md0: Preloaded image </packages/sets/active/boot/os-kernel/contents.izo> 7971840 bytes at 0xc2848000
usbus0: 480Mbps High Speed USB v2.0
JUNOS procfs is initialized.
Timecounters tick every 10.000 msec
Loading Redundant LT driver
Registered AMT tunnel Encap with UDP Tunnel!
###PCB Group initialized for udppcbgroup
###PCB Group initialized for tcppcbgroup
rts_init: registered inrtsock osd: slotid 3
ugen0.1: <Broadcom> at usbus0
uhub0: <Broadcom EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
Root mount waiting for:Kernel thread "wkupdaemon" (pid 25) exited prematurely.
usbus0
Root mount waiting for: usbus0
uhub0: 3 ports with 3 removable, self powered
Root mount waiting for: usbus0
ugen0.2: <vendor 0x05e3> at usbus0
uhub1: <vendor 0x05e3 USB2.0 Hub, class 9/0, rev 2.00/85.37, addr 2> on usbus0
Root mount waiting for: usbus0
uhub1: 4 ports with 3 removable, self powered
Root mount waiting for: usbus0
ugen0.3: <vendor 0x13fe> at usbus0
umass0: <vendor 0x13fe USB DISK 2.0, class 0/0, rev 2.00/1.00, addr 3> on usbus0
umass0: SCSI over Bulk-Only; quirks = 0x8100
umass0:0:0: Attached to scbus0
Root mount waiting for: usbus0
Trying to mount root from cd9660:/dev/md0.uzip []...
da0 at umass-sim0 bus 0 scbus0 target 0 lun 0
da0: < USB DISK 2.0 PMAP> Removable Direct Access SPC-4 SCSI device
da0: Serial Number 65006CDD1C1AAD84
da0: 40.000MB/s transfers
da0: 1910MB (3911680 512 byte sectors: 255H 63S/T 243C)
da0: quirks=0x3<NO_SYNC_CACHE,NO_6_BYTE>
random: unblocking device.

Highlighted
Junos

Re: Unusual Reboot Reason on Juniper

‎07-04-2017 03:54 AM

root@FLMD002869:RE:0% sysctl hw.re.reboot_reason
hw.re.reboot_reason: 32768

Highlighted
Junos

Re: Unusual Reboot Reason on Juniper

‎07-04-2017 04:01 AM

admin@FLMD002869> file list detail /var/crash

/var/crash:
total blocks: 16
total files: 0

Highlighted
Junos
Solution
Accepted by topic author ryanneil123
‎07-05-2017 06:03 AM

Re: Unusual Reboot Reason on Juniper

‎07-04-2017 09:14 PM

Hi Ryan,

 

Unfortunately, there isn't any information about the reboot reason on Internet and the boot messages also do not give any clue. I would suggest to contact JTAC to check if this is a hardware or software issue.

 

 

Regards,

Rahul

 

Please mark my solution as accepted if it helped.