All rights reserved. Juniper had to go back to the whiteboard and design a new network processer specifically for solving the switching challenges in the modern data center. Below commands should provide details of last reboot and reason: Network Processors Network processors are just a type of application-specific integrated circuit (ASIC). I mean for example, was it rebooted by user issueing 'reboot system' or was the device powered off and then powered ON. All rights reserved. I'm posting to see if anyone can help me compile a list of last reboot reason codes . Jun 6 13:32:20 fwba01 /kernel: KERNEL_MEMORY_CRITICAL: System low on free memory, notifying init (#1264).Jun 6 13:35:17 fwba01 /kernel: rt_pfe_veto: Severe low-free-pages, below threshold. Would you like to mark this message as the new best answer? so im wondering is it possible to find out the reason of a switch reboot or not , and if so how? ArubaOS version 6.4.2.8. AP's connected same poe switch. What doesuser@srx show system core-dumps reveal? Back online at ~15:32, Nov 14 14:00:01 fw1 sshd[15292]: Failed password for root from 218.29.228.34 port 51898 ssh2Nov 14 14:00:01 fw1 sshd[15293]: Received disconnect from 218.29.228.34: 11: Bye ByeNov 14 14:00:06 fw1 sshd[15294]: Failed password for root from 218.29.228.34 port 54687 ssh2Nov 14 14:00:06 fw1 sshd[15298]: Received disconnect from 218.29.228.34: 11: Bye ByeNov 14 14:00:11 fw1 sshd[15299]: Failed password for root from 218.29.228.34 port 57818 ssh2Nov 14 14:00:11 fw1 sshd[15300]: Received disconnect from 218.29.228.34: 11: Bye ByeNov 14 14:00:14 fw1 sshd[15301]: Failed password for root from 218.29.228.34 port 60566 ssh2Nov 14 14:00:15 fw1 sshd[15302]: Received disconnect from 218.29.228.34: 11: Bye ByeNov 14 14:00:19 fw1 sshd[15303]: Failed password for root from 218.29.228.34 port 35269 ssh2Nov 14 14:00:19 fw1 sshd[15304]: Received disconnect from 218.29.228.34: 11: Bye ByeNov 14 14:00:22 fw1 sshd[15305]: Failed password for root from 218.29.228.34 port 38429 ssh2Nov 14 14:00:23 fw1 sshd[15306]: Received disconnect from 218.29.228.34: 11: Bye ByeNov 14 14:00:27 fw1 sshd[15307]: Failed password for root from 218.29.228.34 port 40565 ssh2Nov 14 14:00:28 fw1 sshd[15308]: Received disconnect from 218.29.228.34: 11: Bye ByeNov 14 14:00:31 fw1 sshd[15309]: Failed password for root from 218.29.228.34 port 43430 ssh2Nov 14 14:00:31 fw1 sshd[15310]: Received disconnect from 218.29.228.34: 11: Bye ByeNov 14 14:00:35 fw1 sshd[15311]: Failed password for root from 218.29.228.34 port 45417 ssh2Nov 14 14:00:35 fw1 sshd[15312]: Received disconnect from 218.29.228.34: 11: Bye ByeNov 14 14:00:39 fw1 sshd[15313]: Failed password for root from 218.29.228.34 port 47800 ssh2Nov 14 14:00:40 fw1 sshd[15314]: Received disconnect from 218.29.228.34: 11: Bye ByeNov 14 14:00:43 fw1 sshd[15315]: Failed password for root from 218.29.228.34 port 50389 ssh2Nov 14 14:00:44 fw1 sshd[15316]: Received disconnect from 218.29.228.34: 11: Bye ByeNov 14 14:00:48 fw1 sshd[15317]: Failed password for root from 218.29.228.34 port 52934 ssh2Nov 14 14:00:48 fw1 sshd[15318]: Received disconnect from 218.29.228.34: 11: Bye ByeNov 14 14:00:52 fw1 sshd[15319]: Failed password for root from 218.29.228.34 port 55159 ssh2Nov 14 14:00:52 fw1 sshd[15320]: Received disconnect from 218.29.228.34: 11: Bye ByeNov 14 14:00:55 fw1 sshd[15321]: Failed password for root from 218.29.228.34 port 57770 ssh2Nov 14 14:00:56 fw1 sshd[15322]: Received disconnect from 218.29.228.34: 11: Bye ByeNov 14 14:18:53 fw1 login: LOGIN_INFORMATION: User asdf logged in from host xxx on device ttyp0Nov 14 14:59:31 fw1 init: can not access /usr/sbin/jdiameterd: No such file or directoryNov 14 14:59:31 fw1 init: diameter-service (PID 0) startedNov 14 14:59:31 fw1 init: can not access /usr/sbin/ipmid: No such file or directoryNov 14 14:59:31 fw1 init: ipmi (PID 0) startedNov 14 15:07:02 fw1 init: can not access /usr/sbin/jdiameterd: No such file or directoryNov 14 15:07:02 fw1 init: diameter-service (PID 0) startedNov 14 15:07:02 fw1 init: can not access /usr/sbin/ipmid: No such file or directoryNov 14 15:07:02 fw1 init: ipmi (PID 0) startedNov 14 15:07:22 fw1 login: LOGIN_INFORMATION: User asdf logged in from host xxxx on device ttyp0Nov 14 15:09:20 fw1 sshd[15838]: fatal: Read from socket failed: Connection reset by peerNov 14 15:10:26 fw1 login: LOGIN_INFORMATION: User asdf logged in from host xxxx on device ttyp0Nov 14 15:13:47 fw1 login: LOGIN_INFORMATION: User asdf logged in from host xxxx on device ttyp0Nov 14 15:15:51 fw1 login: LOGIN_INFORMATION: User asdf logged in from host xxxx on device ttyp1Nov 14 15:19:43 fw1 sshd[16120]: Connection closed by xxxxNov 14 15:19:59 fw1 init: can not access /usr/sbin/jdiameterd: No such file or directoryNov 14 15:19:59 fw1 init: diameter-service (PID 0) startedNov 14 15:19:59 fw1 init: can not access /usr/sbin/ipmid: No such file or directoryNov 14 15:19:59 fw1 init: ipmi (PID 0) startedNov 14 15:22:05 fw1 init: can not access /usr/sbin/jdiameterd: No such file or directoryNov 14 15:22:05 fw1 init: diameter-service (PID 0) startedNov 14 15:22:05 fw1 init: can not access /usr/sbin/ipmid: No such file or directoryNov 14 15:22:05 fw1 init: ipmi (PID 0) startedNov 14 15:25:44 fw1 init: can not access /usr/sbin/jdiameterd: No such file or directoryNov 14 15:25:44 fw1 init: diameter-service (PID 0) startedNov 14 15:25:44 fw1 init: can not access /usr/sbin/ipmid: No such file or directoryNov 14 15:25:44 fw1 init: ipmi (PID 0) startedNov 14 15:30:43 fw1 /kernel: getmemsize: msgbufp[size=32768] = 0x8000cfe4Nov 14 15:30:43 fw1 /kernel: Copyright (c) 1996-2011, Juniper Networks, Inc.Nov 14 15:30:43 fw1 /kernel: All rights reserved.Nov 14 15:30:43 fw1 /kernel: Copyright (c) 1992-2006 The FreeBSD Project.Nov 14 15:30:43 fw1 /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994Nov 14 15:30:43 fw1 /kernel: The Regents of the University of California. There isn't any specific information on this reboot reason on Internet. 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 armJuniper 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 enabledLoUU:2 LoC:2 LoUIS:2Cache level 1: 32KB/32B 4-way data cache WB Read-Alloc Write-Alloc 32KB/32B 4-way instruction cache Read-Allocreal 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: SHA1MAC/veriexec fingerprint module loaded: SHA256random: entropy device external interfaceInitializing DCF platform properties ..rts_sysconf_ifstate_init: registerd rtcb osd: slotid 2Calling dcf_ng_hw_init for platform hw vecs initializationofwbus0: simplebus0: on ofwbus0mpcore0: on simplebus0bcmidm0: mem 0x100000-0x1fffff on simplebus0ihost_proc0: mem 0x1000000-0x1000fff on simplebus0l2cache0: mem 0x1022000-0x1022fff irq 32 on mpcore0l2cache0: Part number: 0x3, release: 0x9 (r3p3)l2cache0: L2 Cache enabled: 256KB/32B 16 waysgic0: mem 0x1021000-0x1021fff,0x1020100-0x10201 ff on mpcore0gic0: pn 0x390, arch 0x1, rev 0x2, implementer 0x43b irqs 256mp_tmr0: mem 0x1020200-0x10202ff,0x1020600-0x102061f irq 27,29 on mpcore0Timecounter "MPCore" frequency 625000000 Hz quality 800Event timer "MPCore" frequency 625000000 Hz quality 1000cmic0: mem 0x3200000-0x32fffff irq 221 on ofwbus0cmic0: called :bcm_cmic_attach,Dev Chip Id is 0x1b063:bcmdmu0: mem 0xf000-0xffff on simplebus0bcm560xgmac0: mem 0x42000-0x42fff irq 142 on simplebus0bcmidm0: chip dev id :0x1b063miibus0: on bcm560xgmac0brgphy0: PHY 1 on miibus0brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-mas ter, 1000baseT-FDX, 1000baseT-FDX-master, autoehci0: mem 0x48000-0x49fff irq 104 on simplebus0ehci0: called :bcmusb_ehci_attach,Dev Chip Id is 0x1b063:usbus0: EHCI version 1.0usbus0 on ehci0gpio0: mem 0xa000-0xa0ff irq 116 on simplebus0gpiobus0: on gpio0gpioc0: on gpio0uart0: <16750 or compatible> mem 0x20000-0x200ff irq 105 on simplebus0uart0: console (9600,n,8,1)uart0: [GIANT-LOCKED]uart1: <16750 or compatible> mem 0x21000-0x210ff irq 106 on simplebus0uart1: [GIANT-LOCKED]iichb0: mem 0x8000-0x8fff irq 117 on simplebus0iicbus0: on iichb0iic0: on iicbus0iicswitch0: at addr 0x70 on iicbus0poe0: on iicswitch0poe reset failedrtc8564je_rtc0: on iicswitch0cpld0: at addr 0x31 on iicbus0cpldbus0: on cpld0wdog0: on cpldbus0oamctl0: on cpldbus0fan0: on cpldbus0fan1: on cpldbus0resetctrl0: on cpldbus0bcmcru0: mem 0xe000-0xefff on simplebus0spi0: mem 0x47000-0x47fff irq 102 on simplebus0spibus0: on spi0mx25l0: at cs 0 on spibus0mx25l0: mx25ll64, sector 65536 bytes, 128 sectorscryptosoft0: Initializing product: 169 ..md0: Preloaded image 7971840 bytes at 0xc2848000usbus0: 480Mbps High Speed USB v2.0JUNOS procfs is initialized.Timecounters tick every 10.000 msec Loading Redundant LT driverRegistered AMT tunnel Encap with UDP Tunnel!###PCB Group initialized for udppcbgroup###PCB Group initialized for tcppcbgrouprts_init: registered inrtsock osd: slotid 3ugen0.1: at usbus0uhub0: on usbus0Root mount waiting for:Kernel thread "wkupdaemon" (pid 25) exited prematurely. Dear community. Also, the names of any running processes that are scheduled to be shut down Performing an In-Service Software Reboot - Juniper Networks Hi, You can do a 'show log user' and see at least if the reboot was initiated by a user, if there's no information on messages file. After analyzing logs I have found this messages on rebooted node. https://www.juniper.net/assets/scripts/global-nav.js, https://events.juniper.net/assets/scripts/custom/events.js. 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. This article explains what happens to the logs on a Juniper device after it's RE (routing engine) is rebooted or replaced. op_state=1Nov 14 15:30:43 fw1 /kernel: Init: Power Port (0)Nov 14 15:30:43 fw1 /kernel: usb0: on dwc0Nov 14 15:30:43 fw1 /kernel: usb0: USB revision 2.0Nov 14 15:30:43 fw1 /kernel: uhub0: vendor 0x0000 DWC OTG root hub, class 9/0, rev 2.00/1.00, addr 1Nov 14 15:30:43 fw1 /kernel: uhub0: 1 port with 1 removable, self poweredNov 14 15:30:43 fw1 /kernel: uhub1: vendor 0x0409 product 0x005a, class 9/0, rev 2.00/1.00, addr 2Nov 14 15:30:43 fw1 /kernel: uhub1: single transaction translatorNov 14 15:30:43 fw1 /kernel: uhub1: 3 ports with 2 removable, self poweredNov 14 15:30:43 fw1 /kernel: pcib0: on obio0Nov 14 15:30:43 fw1 /kernel: Disabling Octeon big bar supportNov 14 15:30:43 fw1 /kernel: PCI Status: PCI 32-bit: 0xc041bNov 14 15:30:43 fw1 /kernel: pcib0: Initialized controllerNov 14 15:30:43 fw1 /kernel: pci0: on pcib0Nov 14 15:30:43 fw1 /kernel: pci0: at device 1.0 (no driver attached)Nov 14 15:30:43 fw1 /kernel: atapci0: port 0x8-0xb,0x10-0x17,0x18-0x1b,0x20-0x2f mem 0x8020000-0x80200ff irq 0 at device 2.0 on pci0Nov 14 15:30:43 fw1 /kernel: ata2: on atapci0Nov 14 15:30:43 fw1 /kernel: ata3: on atapci0Nov 14 15:30:43 fw1 /kernel: cpld0 on obio0Nov 14 15:30:43 fw1 /kernel: gblmem0 on obio0Nov 14 15:30:43 fw1 /kernel: octpkt0: on obio0Nov 14 15:30:43 fw1 /kernel: cfi0: on obio0Nov 14 15:30:43 fw1 /kernel: platform_cookie_read not implementedNov 14 15:30:43 fw1 /kernel: Timecounter "mips" frequency 700000000 Hz quality 0Nov 14 15:30:43 fw1 /kernel: Timecounters tick every 1.000 msecNov 14 15:30:43 fw1 /kernel: Loading the NETPFE ethernet moduleNov 14 15:30:43 fw1 /kernel: Loading E1/T1/J1 driverNov 14 15:30:43 fw1 /kernel: Loading the DS1/E1 Media Layer; Attaching to media services layerNov 14 15:30:43 fw1 /kernel: Loading common multilink module.Nov 14 15:30:43 fw1 /kernel: Loading the NETPFE PPPoE moduleNov 14 15:30:43 fw1 /kernel: Loading the netpfe services driverNov 14 15:30:43 fw1 /kernel: Loading the NETPFE docsis moduleNov 14 15:30:43 fw1 /kernel: Loading DS0 driverNov 14 15:30:43 fw1 /kernel: Loading the DS0 Media Layer; Attaching to media services layerNov 14 15:30:43 fw1 /kernel: Loading the XDSL Media Layer; Attaching to media services layerNov 14 15:30:43 fw1 /kernel: Loading the IPSec driverNov 14 15:30:43 fw1 /kernel: Loading the PTM driverNov 14 15:30:43 fw1 /kernel: Loading the ISDN driverNov 14 15:30:43 fw1 /kernel: Loading the ISDN BRI Media Layer; Attaching to media services layerNov 14 15:30:43 fw1 /kernel: Loading Link Services PICs module.Nov 14 15:30:43 fw1 /kernel: IPsec: Initialized Security Association Processing.Nov 14 15:30:43 fw1 /kernel: ad0: Device does not support APMNov 14 15:30:43 fw1 /kernel: ad0: 1006MB at ata2-master WDMA2Nov 14 15:30:43 fw1 /kernel: SMP: AP CPU #1 Launched!Nov 14 15:30:43 fw1 /kernel: Trying to create bootdev, rootpartition ad0s2aNov 14 15:30:43 fw1 /kernel: Trying to mount root from ufs:/dev/ad0s2aNov 14 15:30:43 fw1 /kernel: WARNING: / was not properly dismountedNov 14 15:30:46 fw1 /kernel: Loading the DIALER driverNov 14 15:30:56 fw1 init: watchdog (PID 1077) startedNov 14 15:30:56 fw1 init: bslockd (PID 1078) startedNov 14 15:30:56 fw1 init: tnp-process (PID 1079) startedNov 14 15:30:56 fw1 init: interface-control (PID 1080) startedNov 14 15:30:56 fw1 init: chassis-control (PID 1081) startedNov 14 15:30:56 fw1 init: alarm-control (PID 1082) startedNov 14 15:30:56 fw1 init: craft-control (PID 1083) startedNov 14 15:30:56 fw1 init: ntp (PID 1084) startedNov 14 15:30:56 fw1 init: management (PID 1085) startedNov 14 15:30:56 fw1 init: snmp (PID 1086) startedNov 14 15:30:56 fw1 init: mib-process (PID 1087) startedNov 14 15:30:56 fw1 init: routing (PID 1088) startedNov 14 15:30:56 fw1 init: l2-learning (PID 1089) startedNov 14 15:30:56 fw1 init: inet-process (PID 1090) startedNov 14 15:30:56 fw1 init: pfe (PID 1091) startedNov 14 15:30:56 fw1 init: remote-operations (PID 1092) startedNov 14 15:30:56 fw1 init: class-of-service (PID 1093) startedNov 14 15:30:56 fw1 init: ipsec-key-management (PID 1094) startedNov 14 15:30:56 fw1 init: periodic-packet-services (PID 1095) startedNov 14 15:30:57 fw1 init: firewall (PID 1096) startedNov 14 15:30:57 fw1 init: internal-routing-service (PID 1097) startedNov 14 15:30:57 fw1 init: neighbor-liveness (PID 1098) startedNov 14 15:30:57 fw1 init: forwarding (PID 1099) startedNov 14 15:30:57 fw1 init: dhcp (PID 1100) startedNov 14 15:30:57 fw1 init: usb-control (PID 856) startedNov 14 15:30:57 fw1 init: ppp (PID 1101) startedNov 14 15:30:57 fw1 init: event-processing (PID 871) startedNov 14 15:30:58 fw1 init: lacp (PID 1102) startedNov 14 15:30:58 fw1 init: general-authentication-service (PID 1103) startedNov 14 15:30:58 fw1 init: mpls-traceroute (PID 1104) startedNov 14 15:30:58 fw1 init: database-replication (PID 1105) startedNov 14 15:30:58 fw1 init: secure-neighbor-discovery (PID 1106) startedNov 14 15:30:58 fw1 init: wireless-wan-service (PID 1107) startedNov 14 15:30:58 fw1 init: relay-process (PID 1108) startedNov 14 15:30:58 fw1 init: jsrp-service (PID 1109) startedNov 14 15:30:58 fw1 init: network-security (PID 1110) startedNov 14 15:30:58 fw1 init: pki-service (PID 1111) startedNov 14 15:30:58 fw1 init: web-management (PID 1112) startedNov 14 15:30:58 fw1 init: can not access /usr/sbin/jdiameterd: No such file or directoryNov 14 15:30:58 fw1 init: diameter-service (PID 0) startedNov 14 15:30:59 fw1 init: idp-policy (PID 1113) startedNov 14 15:30:59 fw1 init: network-security-trace (PID 1116) startedNov 14 15:30:59 fw1 init: firewall-authentication-service (PID 1117) startedNov 14 15:30:59 fw1 init: security-log (PID 1118) startedNov 14 15:30:59 fw1 init: utmd (PID 1119) startedNov 14 15:31:00 fw1 init: simple-mail-client-service (PID 1120) startedNov 14 15:31:00 fw1 init: can not access /usr/sbin/ipmid: No such file or directoryNov 14 15:31:00 fw1 init: ipmi (PID 0) startedNov 14 15:31:00 fw1 init: wireless-lan-service (PID 1121) startedNov 14 15:31:00 fw1 init: multicast-snooping (PID 1122) startedNov 14 15:31:00 fw1 init: license-service (PID 1123) startedNov 14 15:31:01 fw1 init: service-deployment (PID 1127) startedNov 14 15:31:01 fw1 init: ethernet-switching (PID 1128) startedNov 14 15:31:01 fw1 init: Starting of initial processes completeNov 14 15:31:03 fw1 snmpd[1086]: SNMPD_TRAP_COLD_START: trap_generate_cold: SNMP trap: cold startNov 14 15:31:24 fw1 init: can not access /usr/sbin/jdiameterd: No such file or directoryNov 14 15:31:24 fw1 init: diameter-service (PID 0) startedNov 14 15:31:24 fw1 init: can not access /usr/sbin/ipmid: No such file or directoryNov 14 15:31:24 fw1 init: ipmi (PID 0) startedNov 14 15:31:30 fw1 /kernel: RT_PFE: RT msg op 1 (PREFIX ADD) failed, err 5 (Invalid)Nov 14 15:31:30 fw1 /kernel: GENCFG: op 2 (Gencfg Blob) failed; err 5 (Invalid)Nov 14 15:31:30 fw1 /kernel: GENCFG: op 2 (Gencfg Blob) failed; err 7 (Doesn't Exist)Nov 14 15:31:30 fw1 last message repeated 3 timesNov 14 15:32:21 fw1 sshd[1150]: Accepted password for asdf from xxxx port 18870 ssh2Nov 14 15:38:55 fw1 checklogin[1212]: warning: can't get client address: Bad file descriptorNov 14 15:38:55 fw1 checklogin[1212]: WEB_AUTH_SUCCESS: Authenticated httpd client (username asdf)Nov 14 16:00:59 fw1 sshd[1989]: Could not write ident string to UNKNOWN.
Harvard Premed Handbook,
Brooklyn Summer Camps For 4 Year Olds,
Sunset Hills, Thousand Oaks,
Articles J
