Junos OS

last person joined: 5 hours ago

Ask questions and share experiences about Junos OS.

Back to discussions

Expand all | Collapse all

Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

Jump to Best Answer

1. Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

0 Recommend
Erdem
Posted 02-04-2018 04:34

Reply Reply Privately
I try to upgrade our MX480 to 15.1R6-S4 - the name of pakage is junos-install-mx-x86-64-15.1R6-S4.tgz

but every time the router validate it successfuly and reboot but back to original version Junos: 15.1F7.3

the subscriber managemnet is actvie on Router , I disabled interface si-0/0/0 it and do upgrading but no result

Original Version :

Spoiler
Model: mx480
Junos: 15.1F7.3
JUNOS OS Kernel 64-bit [20170209.344539_builder_stable_10]
JUNOS OS libs [20170209.344539_builder_stable_10]
JUNOS OS runtime [20170209.344539_builder_stable_10]
JUNOS OS time zone information [20170209.344539_builder_stable_10]
JUNOS network stack and utilities [20170302.065919_builder_junos_151_f7]
JUNOS modules [20170302.065919_builder_junos_151_f7]
JUNOS OS libs compat32 [20170209.344539_builder_stable_10]
JUNOS OS 32-bit compatibility [20170209.344539_builder_stable_10]
JUNOS libs compat32 [20170302.065919_builder_junos_151_f7]
JUNOS runtime [20170302.065919_builder_junos_151_f7]
Junos vmguest package [20170302.065919_builder_junos_151_f7]
JUNOS py base [20170302.065919_builder_junos_151_f7]
JUNOS OS vmguest [20170209.344539_builder_stable_10]
JUNOS OS crypto [20170209.344539_builder_stable_10]
JUNOS platform support [20170302.065919_builder_junos_151_f7]
JUNOS libs [20170302.065919_builder_junos_151_f7]
JUNOS mtx Data Plane Crypto Support [20170302.065919_builder_junos_151_f7]
JUNOS daemons [20170302.065919_builder_junos_151_f7]
JUNOS Voice Services Container package [20170302.065919_builder_junos_151_f7]
JUNOS Services SSL [20170302.065919_builder_junos_151_f7]
JUNOS Services Stateful Firewall [20170302.065919_builder_junos_151_f7]
JUNOS Services RPM [20170302.065919_builder_junos_151_f7]
JUNOS Services PTSP Container package [20170302.065919_builder_junos_151_f7]
JUNOS Services NAT [20170302.065919_builder_junos_151_f7]
JUNOS Services Mobile Subscriber Service Container package [20170302.065919_builder_junos_151_f7]
JUNOS Services MobileNext Software package [20170302.065919_builder_junos_151_f7]
JUNOS Services LL-PDF Container package [20170302.065919_builder_junos_151_f7]
JUNOS Services Jflow Container package [20170302.065919_builder_junos_151_f7]
JUNOS Services IPSec [20170302.065919_builder_junos_151_f7]
JUNOS IDP Services [20170302.065919_builder_junos_151_f7]
JUNOS Services HTTP Content Management package [20170302.065919_builder_junos_151_f7]
JUNOS Services Crypto [20170302.065919_builder_junos_151_f7]
JUNOS Services Captive Portal and Content Delivery Container package [20170302.065919_builder_junos_151_f7]
JUNOS Services COS [20170302.065919_builder_junos_151_f7]
JUNOS Border Gateway Function package [20170302.065919_builder_junos_151_f7]
JUNOS AppId Services [20170302.065919_builder_junos_151_f7]
JUNOS Services Application Level Gateways [20170302.065919_builder_junos_151_f7]
JUNOS Services AACL Container package [20170302.065919_builder_junos_151_f7]
JUNOS Packet Forwarding Engine Support (wrlinux) [20170302.065919_builder_junos_151_f7]
JUNOS Packet Forwarding Engine Support (MX/EX92XX Common) [20170302.065919_builder_junos_151_f7]
JUNOS Packet Forwarding Engine Support (M/T Common) [20170302.065919_builder_junos_151_f7]
JUNOS Online Documentation [20170302.065919_builder_junos_151_f7]
JUNOS FIPS mode utilities [20170302.065919_builder_junos_151_f7]

Freebsd version

Spoiler
FreeBSD Monster JNPR-10.3-20170209.344539_build FreeBSD JNPR-10.3-20170209.344539_builder_stable_10 #0: Thu Feb 9 12:50:04 PST 2017     builder@basith.juniper.net:/volume/build/junos/occam/freebsd/stable_10/20170209.builder.344539/obj/amd64/juniper/kernels/JNPR-AMD64-PRD/kernel amd64

Logs - upgrade and reboot -

Spoiler
Feb 4 13:30:05 Monster mgd[5012]: /usr/libexec/ui/package -X update -reboot /var/tmp/junos-install-mx-x86-64-15.1R6-S4.tgz
Feb 4 13:31:08 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:08 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:31:12 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:12 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:31:12 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:12 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:31:12 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:12 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:31:12 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:12 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:31:12 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:12 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:31:12 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:12 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:31:13 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:13 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:31:13 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:13 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:31:13 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:13 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:31:14 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:14 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:31:14 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:14 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:31:14 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:14 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:31:14 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:14 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:31:15 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:15 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:31:15 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:15 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:31:15 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:15 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:31:16 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:16 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:31:16 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:16 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:31:16 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:16 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:31:16 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:16 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:31:16 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:16 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:31:16 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:16 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:31:16 Monster mountd[4625]: bad exports list line /var/db/ext/juniper
Feb 4 13:31:16 Monster mountd[4625]: bad exports list line /var/tmp/gcov
Feb 4 13:32:11 Monster shutdown: reboot requested by root at Sun Feb 4 13:32:11 2018
Feb 4 13:32:11 Monster shutdown: reboot by root:
Feb 4 13:32:11 Monster mib2d[4542]: MIB2D_FILE_OPEN_FAILURE: Unable to open file '': No such file or directory
Feb 4 13:32:11 Monster rpdc: performing a "rpdc -D chassisd toggletrace" command for user root
Feb 4 13:32:11 Monster jlaunchd: watchdog (PID 4532) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: bslockd (PID 4533) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: tnp-process (PID 4534) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: chassis-control (PID 4536) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: app-engine-virtual-machine-management-service (PID 4537) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: craft-control (PID 4539) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: management (PID 4540) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: mib-process (PID 4542) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: inet-process (PID 4543) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: pfed (PID 4546) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: periodic-packet-services (PID 4547) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: disk-monitoring (PID 4548) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: neighbor-liveness (PID 4552) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: event-processing (PID 4553) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: clksyncd-service (PID 4554) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: dhcp-service (PID 4555) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: general-authentication-service (PID 4556) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: subscriber-management (PID 4558) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: shm-rtsdbd (PID 4560) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: gstatd (PID 4561) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: process-monitor (PID 4564) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: smg-service (PID 4565) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: application-identification (PID 4566) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: license-service (PID 4567) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: routing (PID 4602) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: l2-learning (PID 4603) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: sonet-aps (PID 4604) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: remote-operations (PID 4605) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: class-of-service (PID 4606) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: link-management (PID 4607) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: routing-socket-proxy (PID 4608) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: pic-services-logging (PID 4609) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: redundancy-device (PID 4610) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: ppp (PID 4611) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: dynamic-flow-capture (PID 4612) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: l2cpd-service (PID 4613) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: tunnel-oamd (PID 4614) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: ethernet-link-fault-management (PID 4615) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: ethernet-connectivity-fault-management (PID 4616) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: mpls-traceroute (PID 4617) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: secure-neighbor-discovery (PID 4618) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: iccp-service (PID 4619) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: ddos-service (PID 4620) terminate signal 15 sent
Feb 4 13:32:11 Monster l2cpd[4613]: JTASK_SIGNAL_TERMINATE: first termination signal received
Feb 4 13:32:11 Monster agentd[4621]: AgentD got SIGTERM
Feb 4 13:32:11 Monster agentd[4621]: agentd_sigterm_proc: AgentD received SIGTERM. is_master:1
Feb 4 13:32:11 Monster rmopd[4605]: rmopd exiting on SIGTERM
Feb 4 13:32:11 Monster jlaunchd: rpcbind-service (PID 4622) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: nfsd-service (PID 4623) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: mspd (PID 4624) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: mountd-service (PID 4625) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: subscriber-management-helper (PID 4626) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: kernel-offload-service (PID 4627) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: dot1x-protocol (PID 4628) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: pki-service (PID 4629) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: alarm-control (PID 4630) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: interface-control (PID 4631) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: snmp (PID 4633) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: sntp (PID 4634) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: internal-routing-service (PID 4635) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: transport-control (PID 4636) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: alarm-management (PID 4637) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: firewall (PID 4638) terminate signal 15 sent
Feb 4 13:32:11 Monster jlaunchd: stats-agent (PID 4639) terminate signal 15 sent
Feb 4 13:32:11 Monster bbe=smgd[4565]: bbe_smd_sigterm_event: Received SIGTERM
Feb 4 13:32:11 Monster agentd[4621]: AgentD got SIGTERM
Feb 4 13:32:11 Monster dot1xd[4628]: JTASK_SIGNAL_TERMINATE: first termination signal received
Feb 4 13:32:11 Monster dot1xd[4628]: task_terminate.c task_pre_terminate_method in ESP SERVER:33015.0.0.0.0+33015.128.0.0.1+57938
Feb 4 13:32:11 Monster dot1xd[4628]: task_terminate.c task_pre_terminate_method in PNACD
Feb 4 13:32:11 Monster fpc0 PPMAN disconnected; Remote side closed
Feb 4 13:32:11 Monster clksyncd[4554]: SIGTERM - clksyncd
Feb 4 13:32:11 Monster rpd[4602]: JTASK_SIGNAL_TERMINATE: first termination signal received
Feb 4 13:32:11 Monster rpd[4602]: task_terminate.c task_pre_terminate_method in OSPF
Feb 4 13:32:12 Monster agentd[4621]: AgentD exiting on SIGTERM
Feb 4 13:32:12 Monster fpc0 CLKSYNC: Master closed connection
Feb 4 13:32:12 Monster fpc0 CLKSYNC: Master socket closed, 0x16d8b828
Feb 4 13:32:12 Monster rpd[4602]: RPD_OSPF_NBRDOWN: OSPF neighbor 10.20.1.102 (realm ospf-v2 ge-0/0/0.0 area 0.0.0.0) state changed from Full to Down due to KillNbr (event reason: interface went down)
Feb 4 13:32:12 Monster rpd[4602]: JTASK_SIGNAL_TERMINATE: second termination signal received
Feb 4 13:32:12 Monster rpd[4602]: JTASK_EXIT: Exit rpd[4602] version 15.1F7.3 built by builder on 2017-03-02 10:18:03 UTC, caller 0x1004643
Feb 4 13:32:12 Monster l2cpd[4613]: JTASK_EXIT: Exit l2cpd[4613] version 15.1F7.3 built by builder on 2017-03-02 09:35:09 UTC, caller 0x82a01f0
Feb 4 13:32:12 Monster dot1xd[4628]: JTASK_EXIT: Exit dot1xd[4628] version 15.1F7.3 built by builder on 2017-03-02 09:32:41 UTC, caller 0x83b8290
Feb 4 13:32:12 Monster fpc0 CLKSYNC disconnected; CLKSYNC socket closed abruptly
Feb 4 13:32:12 Monster chassisd[4536]: ch_calypso_sigterm_handler: signo=15   slot_id=0 other_slot_id=1
Feb 4 13:32:12 Monster fpc0 DDOS: Master socket closed
Feb 4 13:32:12 Monster fpc0 DDOS disconnected: DDOS socket closed abruptly
Feb 4 13:32:12 Monster fpc0 DDOS: Null pipe
Feb 4 13:32:12 Monster fpc0 BULKGET: Master socket closed
Feb 4 13:32:12 Monster fpc0 BULKGET disconnected: BULKGET socket closed abruptly
Feb 4 13:32:12 Monster fpc0 L2ALM: Master closed connection
Feb 4 13:32:12 Monster fpc0 L2ALM: Master socket closed, 0x16d8b1f8
Feb 4 13:32:12 Monster fpc0 L2ALM disconnected; L2ALM socket closed abruptly
Feb 4 13:32:15 Monster jlaunchd: stats-agent (PID 4639) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: alarm-management (PID 4637) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: transport-control (PID 4636) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: internal-routing-service (PID 4635) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: sntp (PID 4634) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: snmp (PID 4633) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: interface-control (PID 4631) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: alarm-control (PID 4630) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: pki-service (PID 4629) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: dot1x-protocol (PID 4628) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: kernel-offload-service (PID 4627) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: subscriber-management-helper (PID 4626) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: mountd-service (PID 4625) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: mspd (PID 4624) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: nfsd-service (PID 4623) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: rpcbind-service (PID 4622) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: SDN-Telemetry (PID 4621) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: ddos-service (PID 4620) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: iccp-service (PID 4619) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: secure-neighbor-discovery (PID 4618) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: mpls-traceroute (PID 4617) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: ethernet-link-fault-management (PID 4615) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: tunnel-oamd (PID 4614) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: l2cpd-service (PID 4613) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: dynamic-flow-capture (PID 4612) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: ppp (PID 4611) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: redundancy-device (PID 4610) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: pic-services-logging (PID 4609) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: routing-socket-proxy (PID 4608) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: link-management (PID 4607) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: class-of-service (PID 4606) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: remote-operations (PID 4605) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: sonet-aps (PID 4604) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: l2-learning (PID 4603) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: license-service (PID 4567) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: application-identification (PID 4566) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: smg-service (PID 4565) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: process-monitor (PID 4564) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: gstatd (PID 4561) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: shm-rtsdbd (PID 4560) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: subscriber-management (PID 4558) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: general-authentication-service (PID 4556) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: dhcp-service (PID 4555) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: clksyncd-service (PID 4554) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: neighbor-liveness (PID 4552) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: disk-monitoring (PID 4548) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: periodic-packet-services (PID 4547) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: inet-process (PID 4543) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: mib-process (PID 4542) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: management (PID 4540) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: craft-control (PID 4539) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: app-engine-virtual-machine-management-service (PID 4537) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: tnp-process (PID 4534) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: bslockd (PID 4533) exited with status=0 Normal Exit
Feb 4 13:32:15 Monster jlaunchd: watchdog (PID 4532) exited with status=0 Normal Exit
Feb 4 13:32:17 Monster jlaunchd: some processes would not die; ps axl advised
Feb 4 13:32:20 Monster chassisd[4536]: ch_calypso_restart_hard: set offline led for hard reset, slot=0 other_slot_id=1
Feb 4 13:32:20 Monster kernel: mastership: routing engine 0 relinquishing as master: voluntarily requested
Feb 4 13:32:20 Monster kernel: NHACK_DEBUG: nhack_delete_in_use_list EntryNHACK_DEBUG: nhack_delete_free_list Entry
Feb 4 13:32:20 Monster kernel: pfe_listener_disconnect: conn dropped: issu_master = 0,listener idx=0, addr=0x80000010, reason: transition to slave
Feb 4 13:32:20 Monster chassisd[4536]: CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(0)
Feb 4 13:32:20 Monster chassisd[4536]: CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(1)
Feb 4 13:32:20 Monster chassisd[4536]: CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(2)
Feb 4 13:32:20 Monster chassisd[4536]: CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(3)
Feb 4 13:32:20 Monster chassisd[4536]: CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(4)
Feb 4 13:32:20 Monster chassisd[4536]: CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(5)
Feb 4 13:32:20 Monster chassisd[4536]: CHASSISD_IFDEV_DETACH_ALL_PSEUDO: ifdev_detach(pseudo devices: all)
Feb 4 13:33:38 Monster eventd[4583]: SYSTEM_ABNORMAL_SHUTDOWN: System abnormally shut down
Feb 4 13:33:38 Monster eventd[4583]: SYSTEM_OPERATIONAL: System is operational
Feb 4 13:33:38 Monster kernel: Waiting (max 60 seconds) for system process `vnlru' to stop...done
Feb 4 13:33:38 Monster kernel: Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Feb 4 13:33:38 Monster kernel: Waiting (max 60 seconds) for system process `syncer' to stop...
Feb 4 13:33:38 Monster kernel: Syncing disks, vnodes remaining...0 0 0 0 done
Feb 4 13:33:38 Monster kernel: All buffers synced.
Feb 4 13:33:38 Monster kernel: Uptime: 1h29m50s
Feb 4 13:33:38 Monster kernel: besw0: 3 Broadcom SDK kernel threads killed
Feb 4 13:33:38 Monster kernel: Khelp module "jsocket" can't unload until its refcount drops from 2 to 0.
Feb 4 13:33:38 Monster kernel: Rebooting...

Log - Rebooting - 1

Spoiler
Feb 4 13:33:38 Monster kernel: Rebooting...
Feb 4 13:33:38 Monster kernel: cpu_reset: Stopping other CPUs
Feb 4 13:33:38 Monster kernel: Copyright (c) 1992-2016 The FreeBSD Project.
Feb 4 13:33:38 Monster kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Feb 4 13:33:38 Monster kernel:        The Regents of the University of California. All rights reserved.
Feb 4 13:33:38 Monster kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Feb 4 13:33:38 Monster kernel: FreeBSD JNPR-10.3-20171012.356211_builder_stable_10 #0: Thu Oct 12 01:16:37 PDT 2017
Feb 4 13:33:38 Monster kernel:     builder@basith.juniper.net:/volume/build/junos/occam/freebsd/stable_10/20171012.builder.356211/obj/amd64/juniper/kernels/JNPR-AMD64-PRD/kernel amd64
Feb 4 13:33:38 Monster kernel: gcc version 4.2.1 (for JUNOS)
Feb 4 13:33:38 Monster kernel: VT(vga): resolution 640x480
Feb 4 13:33:38 Monster kernel: sysctl: OID number(10) is already in use for 'option_Q_maxlen'
Feb 4 13:33:38 Monster kernel: CPU: QEMU Virtual CPU version 1.7.2 (2000.05-MHz K8-class CPU)
Feb 4 13:33:38 Monster kernel:   Origin="GenuineIntel" Id=0x663 Family=0x6 Model=0x6 Stepping=3
Feb 4 13:33:38 Monster kernel:   Features=0x783fbfd<FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2>
Feb 4 13:33:38 Monster kernel:   Features2=0x80802001<SSE3,CX16,POPCNT,HV>
Feb 4 13:33:38 Monster kernel:   AMD Features=0x20100800<SYSCALL,NX,LM>
Feb 4 13:33:38 Monster kernel:   AMD Features2=0x21<LAHF,ABM>
Feb 4 13:33:38 Monster kernel:   TSC: P-state invariant
Feb 4 13:33:38 Monster kernel: real memory = 51539607552 (49152 MB)
Feb 4 13:33:38 Monster kernel: avail memory = 50004144128 (47687 MB)
Feb 4 13:33:38 Monster kernel: platform_early_bootinit: M/T/EX Series Early Boot Initialization
Feb 4 13:33:38 Monster kernel: Olive CPU
Feb 4 13:33:38 Monster kernel: Event timer "LAPIC" quality 400
Feb 4 13:33:38 Monster kernel: ACPI APIC Table: <BOCHS BXPCAPIC>
Feb 4 13:33:38 Monster kernel: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
Feb 4 13:33:38 Monster kernel: FreeBSD/SMP: 4 package(s) x 1 core(s)
Feb 4 13:33:38 Monster kernel: cpu0 (BSP): APIC ID: 0
Feb 4 13:33:38 Monster kernel: cpu1 (AP): APIC ID: 1
Feb 4 13:33:38 Monster kernel: cpu2 (AP): APIC ID: 2
Feb 4 13:33:38 Monster kernel: cpu3 (AP): APIC ID: 3
Feb 4 13:33:38 Monster kernel: random: <Software, Yarrow> initialized
Feb 4 13:33:38 Monster kernel: Security policy loaded: JUNOS MAC/privcheck (mac_privcheck)
Feb 4 13:33:38 Monster kernel: Security policy loaded: MAC/veriexec (mac_veriexec)
Feb 4 13:33:38 Monster kernel: Security policy loaded: Junos MAC/fips (mac_fips)
Feb 4 13:33:38 Monster kernel: MAC/veriexec fingerprint module loaded: SHA1
Feb 4 13:33:38 Monster kernel: MAC/veriexec fingerprint module loaded: SHA256
Feb 4 13:33:38 Monster kernel: ioapic0 <Version 1.1> irqs 0-23 on motherboard
Feb 4 13:33:38 Monster kernel: netisr_init: !debug_mpsafenet, forcing maxthreads from 4 to 1
Feb 4 13:33:38 Monster kernel: Initializing M/T/EX platform properties ..
Feb 4 13:33:38 Monster kernel: rts_sysconf_ifstate_init: registerd rtcb osd: slotid 2
Feb 4 13:33:38 Monster kernel: ofwbus0: <Open Firmware Device Tree> on motherboard
Feb 4 13:33:38 Monster kernel: fdtio0: <FDT I/O port space> on ofwbus0
Feb 4 13:33:38 Monster kernel: fpga0: <RE system controller> port 0x191-0x198 on fdtio0
Feb 4 13:33:38 Monster kernel: cryptosoft0: <software crypto> on motherboard
Feb 4 13:33:38 Monster kernel: acpi0: <BOCHS BXPCRSDT> on motherboard
Feb 4 13:33:38 Monster kernel: acpi0: Power Button (fixed)
Feb 4 13:33:38 Monster kernel: cpu0: <ACPI CPU> on acpi0
Feb 4 13:33:38 Monster kernel: cpu1: <ACPI CPU> on acpi0
Feb 4 13:33:38 Monster kernel: cpu2: <ACPI CPU> on acpi0
Feb 4 13:33:38 Monster kernel: cpu3: <ACPI CPU> on acpi0
Feb 4 13:33:38 Monster kernel: atrtc0: <AT realtime clock> port 0x70-0x71,0x72-0x77 irq 8 on acpi0
Feb 4 13:33:38 Monster kernel: Event timer "RTC" frequency 32768 Hz quality 0
Feb 4 13:33:38 Monster kernel: hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Feb 4 13:33:38 Monster kernel: Timecounter "HPET" frequency 100000000 Hz quality 950
Feb 4 13:33:38 Monster kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
Feb 4 13:33:38 Monster kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0xb008-0xb00b on acpi0
Feb 4 13:33:38 Monster kernel: pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
Feb 4 13:33:38 Monster kernel: pci0: <ACPI PCI bus> on pcib0
Feb 4 13:33:38 Monster kernel: isab0: <PCI-ISA bridge> at device 1.0 on pci0
Feb 4 13:33:38 Monster kernel: isa0: <ISA bus> on isab0
Feb 4 13:33:38 Monster kernel: atapci0: <Intel PIIX3 WDMA2 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc260-0xc26f at device 1.1 on pci0
Feb 4 13:33:38 Monster kernel: ata0: <ATA channel> at channel 0 on atapci0
Feb 4 13:33:38 Monster kernel: ata1: <ATA channel> at channel 1 on atapci0
Feb 4 13:33:38 Monster kernel: ichsmb0: <SMBus controller> port 0xc1e0-0xc1ff mem 0xfeba0000-0xfeba0fff irq 11 at device 2.0 on pci0
Feb 4 13:33:38 Monster kernel: acb0: <Atlas Enhanced Control Subsystem V2> mem 0xfeba1000-0xfeba1fff irq 11 at device 3.0 on pci0
Feb 4 13:33:38 Monster kernel: Fatal trap 12: page fault while in kernel mode
Feb 4 13:33:38 Monster kernel: cpuid = 0; apic id = 00
Feb 4 13:33:38 Monster kernel: fault virtual address = 0x0
Feb 4 13:33:38 Monster kernel: fault code             = supervisor read data, page not present
Feb 4 13:33:38 Monster kernel: instruction pointer    = 0x20:0xffffffff823c2512
Feb 4 13:33:38 Monster kernel: stack pointer          = 0x28:0xffffffff824ae760
Feb 4 13:33:38 Monster kernel: frame pointer          = 0x28:0xffffffff824ae7d0
Feb 4 13:33:38 Monster kernel: code segment           = base 0x0, limit 0xfffff, type 0x1b
Feb 4 13:33:38 Monster kernel:                        = DPL 0, pres 1, long 1, def32 0, gran 1
Feb 4 13:33:38 Monster kernel: processor eflags       = interrupt enabled, resume, IOPL = 0
Feb 4 13:33:38 Monster kernel: current process                = 0 (swapper)
Feb 4 13:33:38 Monster kernel: trap number            = 12
Feb 4 13:33:38 Monster kernel: panic: page fault
Feb 4 13:33:38 Monster kernel: cpuid = 0
Feb 4 13:33:38 Monster kernel: Uptime: 1s
Feb 4 13:33:38 Monster kernel: Automatic reboot in 15 seconds - press a key on the console to abort
Feb 4 13:33:38 Monster kernel: Rebooting...

Log -rebooting 2

Spoiler
Feb 4 13:33:38 Monster kernel: Rebooting...
Feb 4 13:33:38 Monster kernel: cpu_reset: Stopping other CPUs
Feb 4 13:33:38 Monster kernel: Copyright (c) 1992-2016 The FreeBSD Project.
Feb 4 13:33:38 Monster kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Feb 4 13:33:38 Monster kernel:        The Regents of the University of California. All rights reserved.
Feb 4 13:33:38 Monster kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Feb 4 13:33:38 Monster kernel: FreeBSD JNPR-10.3-20171012.356211_builder_stable_10 #0: Thu Oct 12 01:16:37 PDT 2017
Feb 4 13:33:38 Monster kernel:     builder@basith.juniper.net:/volume/build/junos/occam/freebsd/stable_10/20171012.builder.356211/obj/amd64/juniper/kernels/JNPR-AMD64-PRD/kernel amd64
Feb 4 13:33:38 Monster kernel: gcc version 4.2.1 (for JUNOS)
Feb 4 13:33:38 Monster kernel: VT(vga): resolution 640x480
Feb 4 13:33:38 Monster kernel: sysctl: OID number(10) is already in use for 'option_Q_maxlen'
Feb 4 13:33:38 Monster kernel: CPU: QEMU Virtual CPU version 1.7.2 (2000.05-MHz K8-class CPU)
Feb 4 13:33:38 Monster kernel:   Origin="GenuineIntel" Id=0x663 Family=0x6 Model=0x6 Stepping=3
Feb 4 13:33:38 Monster kernel:   Features=0x783fbfd<FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2>
Feb 4 13:33:38 Monster kernel:   Features2=0x80802001<SSE3,CX16,POPCNT,HV>
Feb 4 13:33:38 Monster kernel:   AMD Features=0x20100800<SYSCALL,NX,LM>
Feb 4 13:33:38 Monster kernel:   AMD Features2=0x21<LAHF,ABM>
Feb 4 13:33:38 Monster kernel:   TSC: P-state invariant
Feb 4 13:33:38 Monster kernel: real memory = 51539607552 (49152 MB)
Feb 4 13:33:38 Monster kernel: avail memory = 50004144128 (47687 MB)
Feb 4 13:33:38 Monster kernel: platform_early_bootinit: M/T/EX Series Early Boot Initialization
Feb 4 13:33:38 Monster kernel: Olive CPU
Feb 4 13:33:38 Monster kernel: Event timer "LAPIC" quality 400
Feb 4 13:33:38 Monster kernel: ACPI APIC Table: <BOCHS BXPCAPIC>
Feb 4 13:33:38 Monster kernel: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
Feb 4 13:33:38 Monster kernel: FreeBSD/SMP: 4 package(s) x 1 core(s)
Feb 4 13:33:38 Monster kernel: cpu0 (BSP): APIC ID: 0
Feb 4 13:33:38 Monster kernel: cpu1 (AP): APIC ID: 1
Feb 4 13:33:38 Monster kernel: cpu2 (AP): APIC ID: 2
Feb 4 13:33:38 Monster kernel: cpu3 (AP): APIC ID: 3
Feb 4 13:33:38 Monster kernel: random: <Software, Yarrow> initialized
Feb 4 13:33:38 Monster kernel: Security policy loaded: JUNOS MAC/privcheck (mac_privcheck)
Feb 4 13:33:38 Monster kernel: Security policy loaded: MAC/veriexec (mac_veriexec)
Feb 4 13:33:38 Monster kernel: Security policy loaded: Junos MAC/fips (mac_fips)
Feb 4 13:33:38 Monster kernel: MAC/veriexec fingerprint module loaded: SHA1
Feb 4 13:33:38 Monster kernel: MAC/veriexec fingerprint module loaded: SHA256
Feb 4 13:33:38 Monster kernel: ioapic0 <Version 1.1> irqs 0-23 on motherboard
Feb 4 13:33:38 Monster kernel: netisr_init: !debug_mpsafenet, forcing maxthreads from 4 to 1
Feb 4 13:33:38 Monster kernel: Initializing M/T/EX platform properties ..
Feb 4 13:33:38 Monster kernel: rts_sysconf_ifstate_init: registerd rtcb osd: slotid 2
Feb 4 13:33:38 Monster kernel: ofwbus0: <Open Firmware Device Tree> on motherboard
Feb 4 13:33:38 Monster kernel: fdtio0: <FDT I/O port space> on ofwbus0
Feb 4 13:33:38 Monster kernel: fpga0: <RE system controller> port 0x191-0x198 on fdtio0
Feb 4 13:33:38 Monster kernel: cryptosoft0: <software crypto> on motherboard
Feb 4 13:33:38 Monster kernel: acpi0: <BOCHS BXPCRSDT> on motherboard
Feb 4 13:33:38 Monster kernel: acpi0: Power Button (fixed)
Feb 4 13:33:38 Monster kernel: cpu0: <ACPI CPU> on acpi0
Feb 4 13:33:38 Monster kernel: cpu1: <ACPI CPU> on acpi0
Feb 4 13:33:38 Monster kernel: cpu2: <ACPI CPU> on acpi0
Feb 4 13:33:38 Monster kernel: cpu3: <ACPI CPU> on acpi0
Feb 4 13:33:38 Monster kernel: atrtc0: <AT realtime clock> port 0x70-0x71,0x72-0x77 irq 8 on acpi0
Feb 4 13:33:38 Monster kernel: Event timer "RTC" frequency 32768 Hz quality 0
Feb 4 13:33:38 Monster kernel: hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Feb 4 13:33:38 Monster kernel: Timecounter "HPET" frequency 100000000 Hz quality 950
Feb 4 13:33:38 Monster kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
Feb 4 13:33:38 Monster kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0xb008-0xb00b on acpi0
Feb 4 13:33:38 Monster kernel: pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
Feb 4 13:33:38 Monster kernel: pci0: <ACPI PCI bus> on pcib0
Feb 4 13:33:38 Monster kernel: isab0: <PCI-ISA bridge> at device 1.0 on pci0
Feb 4 13:33:38 Monster kernel: isa0: <ISA bus> on isab0
Feb 4 13:33:38 Monster kernel: atapci0: <Intel PIIX3 WDMA2 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc260-0xc26f at device 1.1 on pci0
Feb 4 13:33:38 Monster kernel: ata0: <ATA channel> at channel 0 on atapci0
Feb 4 13:33:38 Monster kernel: ata1: <ATA channel> at channel 1 on atapci0
Feb 4 13:33:38 Monster kernel: ichsmb0: <SMBus controller> port 0xc1e0-0xc1ff mem 0xfeba0000-0xfeba0fff irq 11 at device 2.0 on pci0
Feb 4 13:33:38 Monster kernel: acb0: <Atlas Enhanced Control Subsystem V2> mem 0xfeba1000-0xfeba1fff irq 11 at device 3.0 on pci0
Feb 4 13:33:38 Monster kernel: Fatal trap 12: page fault while in kernel mode
Feb 4 13:33:38 Monster kernel: cpuid = 0; apic id = 00
Feb 4 13:33:38 Monster kernel: fault virtual address = 0x0
Feb 4 13:33:38 Monster kernel: fault code             = supervisor read data, page not present
Feb 4 13:33:38 Monster kernel: instruction pointer    = 0x20:0xffffffff823c2512
Feb 4 13:33:38 Monster kernel: stack pointer          = 0x28:0xffffffff824ae760
Feb 4 13:33:38 Monster kernel: frame pointer          = 0x28:0xffffffff824ae7d0
Feb 4 13:33:38 Monster kernel: code segment           = base 0x0, limit 0xfffff, type 0x1b
Feb 4 13:33:38 Monster kernel:                        = DPL 0, pres 1, long 1, def32 0, gran 1
Feb 4 13:33:38 Monster kernel: processor eflags       = interrupt enabled, resume, IOPL = 0
Feb 4 13:33:38 Monster kernel: current process                = 0 (swapper)
Feb 4 13:33:38 Monster kernel: trap number            = 12
Feb 4 13:33:38 Monster kernel: panic: page fault
Feb 4 13:33:38 Monster kernel: cpuid = 0
Feb 4 13:33:38 Monster kernel: Uptime: 1s
Feb 4 13:33:38 Monster kernel: Automatic reboot in 15 seconds - press a key on the console to abort
Feb 4 13:33:38 Monster kernel: Rebooting...

log -rebootig 3 - Back to original version

Spoiler
eb 4 13:33:38 Monster kernel: Copyright (c) 1992-2016 The FreeBSD Project.
Feb 4 13:33:38 Monster kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Feb 4 13:33:38 Monster kernel:        The Regents of the University of California. All rights reserved.
Feb 4 13:33:38 Monster kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Feb 4 13:33:38 Monster kernel: FreeBSD JNPR-10.3-20170209.344539_builder_stable_10 #0: Thu Feb 9 12:50:04 PST 2017
Feb 4 13:33:38 Monster kernel:     builder@basith.juniper.net:/volume/build/junos/occam/freebsd/stable_10/20170209.builder.344539/obj/amd64/juniper/kernels/JNPR-AMD64-PRD/kernel amd64
Feb 4 13:33:38 Monster kernel: gcc version 4.2.1 (for JUNOS)
Feb 4 13:33:38 Monster kernel: VT(vga): resolution 640x480
Feb 4 13:33:38 Monster kernel: sysctl: OID number(10) is already in use for 'option_Q_maxlen'
Feb 4 13:33:38 Monster kernel: CPU: QEMU Virtual CPU version 1.7.2 (2000.05-MHz K8-class CPU)
Feb 4 13:33:38 Monster kernel:   Origin="GenuineIntel" Id=0x663 Family=0x6 Model=0x6 Stepping=3
Feb 4 13:33:38 Monster kernel:   Features=0x783fbfd<FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2>
Feb 4 13:33:38 Monster kernel:   Features2=0x80802001<SSE3,CX16,POPCNT,HV>
Feb 4 13:33:38 Monster kernel:   AMD Features=0x20100800<SYSCALL,NX,LM>
Feb 4 13:33:38 Monster kernel:   AMD Features2=0x21<LAHF,ABM>
Feb 4 13:33:38 Monster kernel:   TSC: P-state invariant
Feb 4 13:33:38 Monster kernel: real memory = 51539607552 (49152 MB)
Feb 4 13:33:38 Monster kernel: avail memory = 50005741568 (47689 MB)
Feb 4 13:33:38 Monster kernel: Event timer "LAPIC" quality 400
Feb 4 13:33:38 Monster kernel: ACPI APIC Table: <BOCHS BXPCAPIC>
Feb 4 13:33:38 Monster kernel: platform_early_bootinit: M/T/EX Series Early Boot Initialization
Feb 4 13:33:38 Monster kernel: mtx_platform_set_re_type: vm_retype :RE-S-2X00x6
Feb 4 13:33:38 Monster kernel: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
Feb 4 13:33:38 Monster kernel: FreeBSD/SMP: 4 package(s) x 1 core(s)
Feb 4 13:33:38 Monster kernel: cpu0 (BSP): APIC ID: 0
Feb 4 13:33:38 Monster kernel: cpu1 (AP): APIC ID: 1
Feb 4 13:33:38 Monster kernel: cpu2 (AP): APIC ID: 2
Feb 4 13:33:38 Monster kernel: cpu3 (AP): APIC ID: 3
Feb 4 13:33:38 Monster kernel: random: <Software, Yarrow> initialized
Feb 4 13:33:38 Monster kernel: Security policy loaded: MAC/veriexec (mac_veriexec)
Feb 4 13:33:38 Monster kernel: Security policy loaded: Junos MAC/fips (mac_fips)
Feb 4 13:33:38 Monster kernel: Security policy loaded: Junos MAC/SDK (mac_sdk)
Feb 4 13:33:38 Monster kernel: Security policy loaded: JUNOS MAC/privcheck (mac_privcheck)
Feb 4 13:33:38 Monster kernel: MAC/veriexec fingerprint module loaded: SHA1
Feb 4 13:33:38 Monster kernel: MAC/veriexec fingerprint module loaded: SHA256
Feb 4 13:33:38 Monster kernel: ioapic0 <Version 1.1> irqs 0-23 on motherboard
Feb 4 13:33:38 Monster kernel: netisr_init: !debug_mpsafenet, forcing maxthreads from 4 to 1
Feb 4 13:33:38 Monster kernel: Initializing M/T/EX platform properties ..
Feb 4 13:33:38 Monster kernel: rts_sysconf_ifstate_init: registerd rtcb osd: slotid 2
Feb 4 13:33:38 Monster kernel: ofwbus0: <Open Firmware Device Tree> on motherboard
Feb 4 13:33:38 Monster kernel: fdtio0: <FDT I/O port space> on ofwbus0
Feb 4 13:33:38 Monster kernel: fpga0: <RE system controller> port 0x191-0x198 on fdtio0
Feb 4 13:33:38 Monster kernel: cryptosoft0: <software crypto> on motherboard
Feb 4 13:33:38 Monster kernel: acpi0: <BOCHS BXPCRSDT> on motherboard
Feb 4 13:33:38 Monster kernel: acpi0: Power Button (fixed)
Feb 4 13:33:38 Monster kernel: cpu0: <ACPI CPU> on acpi0
Feb 4 13:33:38 Monster kernel: cpu1: <ACPI CPU> on acpi0
Feb 4 13:33:38 Monster kernel: cpu2: <ACPI CPU> on acpi0
Feb 4 13:33:38 Monster kernel: cpu3: <ACPI CPU> on acpi0
Feb 4 13:33:38 Monster kernel: atrtc0: <AT realtime clock> port 0x70-0x71,0x72-0x77 irq 8 on acpi0
Feb 4 13:33:38 Monster kernel: Event timer "RTC" frequency 32768 Hz quality 0
Feb 4 13:33:38 Monster kernel: hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Feb 4 13:33:38 Monster kernel: Timecounter "HPET" frequency 100000000 Hz quality 950
Feb 4 13:33:38 Monster kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
Feb 4 13:33:38 Monster kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0xb008-0xb00b on acpi0
Feb 4 13:33:38 Monster kernel: pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
Feb 4 13:33:38 Monster kernel: pci0: <ACPI PCI bus> on pcib0
Feb 4 13:33:38 Monster kernel: isab0: <PCI-ISA bridge> at device 1.0 on pci0
Feb 4 13:33:38 Monster kernel: isa0: <ISA bus> on isab0
Feb 4 13:33:38 Monster kernel: atapci0: <Intel PIIX3 WDMA2 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc260-0xc26f at device 1.1 on pci0
Feb 4 13:33:38 Monster kernel: ata0: <ATA channel> at channel 0 on atapci0
Feb 4 13:33:38 Monster kernel: ata1: <ATA channel> at channel 1 on atapci0
Feb 4 13:33:38 Monster kernel: ichsmb0: <SMBus controller> port 0xc1e0-0xc1ff mem 0xfeba0000-0xfeba0fff irq 11 at device 2.0 on pci0
Feb 4 13:33:38 Monster kernel: acb0: <Atlas Enhanced Control Subsystem V2> mem 0xfeba1000-0xfeba1fff irq 11 at device 3.0 on pci0
Feb 4 13:33:38 Monster kernel: acb0: acb: softc at 0xfffff8000b4af400, fpga regs at 0xfffff800feba1000
Feb 4 13:33:38 Monster kernel: spi: zl30143 clock initialized to 19.44 MHz
Feb 4 13:33:38 Monster kernel: spi: zl30130 clock module initialized
Feb 4 13:33:38 Monster kernel: pci0: <network> at device 4.0 (no driver attached)
Feb 4 13:33:38 Monster kernel: xhci0: <Intel Wellsburg USB 3.0 controller> mem 0xfeb90000-0xfeb9ffff irq 10 at device 5.0 on pci0
Feb 4 13:33:38 Monster kernel: xhci0: 32 bytes context size, 64-bit DMA
Feb 4 13:33:38 Monster kernel: usbus0 on xhci0
Feb 4 13:33:38 Monster kernel: ixlv0: <Intel(R) Ethernet Connection XL710 VF Driver, Version - 1.2.6> mem 0xfebe0000-0xfebeffff,0xfebf0000-0xfebf3fff at device 6.0 on pci0
Feb 4 13:33:38 Monster kernel: ixlv0: Using MSIX interrupts with 2 vectors
Feb 4 13:33:38 Monster kernel: igb0: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> mem 0xfebf4000-0xfebf7fff,0xfebf8000-0xfebfbfff at device 7.0 on pci0
Feb 4 13:33:38 Monster kernel: igb0: Using MSIX interrupts with 2 vectors
Feb 4 13:33:38 Monster kernel: esb0: <i6300esb watchdog Driver, Version - 0.05> mem 0xfeba2000-0xfeba200f at device 16.0 on pci0
Feb 4 13:33:38 Monster kernel: virtio_pci0: <VirtIO PCI Network adapter> port 0xc200-0xc21f mem 0xfeba3000-0xfeba3fff irq 10 at device 17.0 on pci0
Feb 4 13:33:38 Monster kernel: vtnet0: <VirtIO Networking Adapter> on virtio_pci0
Feb 4 13:33:38 Monster kernel: virtio_pci1: <VirtIO PCI Network adapter> port 0xc220-0xc23f mem 0xfeba4000-0xfeba4fff irq 10 at device 18.0 on pci0
Feb 4 13:33:38 Monster kernel: vtnet1: <VirtIO Networking Adapter> on virtio_pci1
Feb 4 13:33:38 Monster kernel: virtio_pci2: <VirtIO PCI Network adapter> port 0xc240-0xc25f mem 0xfeba5000-0xfeba5fff irq 11 at device 19.0 on pci0
Feb 4 13:33:38 Monster kernel: vtnet2: <VirtIO Networking Adapter> on virtio_pci2
Feb 4 13:33:38 Monster kernel: virtio_pci3: <VirtIO PCI Block adapter> port 0xc100-0xc13f mem 0xfeba6000-0xfeba6fff irq 11 at device 20.0 on pci0
Feb 4 13:33:38 Monster kernel: vtblk0: <VirtIO Block Adapter> on virtio_pci3
Feb 4 13:33:38 Monster kernel: vtblk0: 15361MB (31459328 512 byte sectors)
Feb 4 13:33:38 Monster kernel: virtio_pci4: <VirtIO PCI Block adapter> port 0xc140-0xc17f mem 0xfeba7000-0xfeba7fff irq 10 at device 21.0 on pci0
Feb 4 13:33:38 Monster kernel: vtblk1: <VirtIO Block Adapter> on virtio_pci4
Feb 4 13:33:38 Monster kernel: vtblk1: 15360MB (31457280 512 byte sectors)
Feb 4 13:33:38 Monster kernel: pci0: <old> at device 22.0 (no driver attached)
Feb 4 13:33:38 Monster kernel: virtio_pci5: <VirtIO PCI SCSI adapter> port 0xc180-0xc1bf mem 0xfeba9000-0xfeba9fff irq 11 at device 23.0 on pci0
Feb 4 13:33:38 Monster kernel: vtscsi0: <VirtIO SCSI Adapter> on virtio_pci5
Feb 4 13:33:38 Monster kernel: uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 on acpi0
Feb 4 13:33:38 Monster kernel: uart0: console (9600,n,8,1)
Feb 4 13:33:38 Monster kernel: uart0: [GIANT-LOCKED]
Feb 4 13:33:38 Monster kernel: uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
Feb 4 13:33:38 Monster kernel: uart1: [GIANT-LOCKED]
Feb 4 13:33:38 Monster kernel: orm0: <ISA Option ROM> at iomem 0xeb800-0xeffff on isa0
Feb 4 13:33:38 Monster kernel: uart2: <16550 or compatible> at port 0x3e8-0x3ef irq 4 on isa0
Feb 4 13:33:38 Monster kernel: uart2: [GIANT-LOCKED]
Feb 4 13:33:38 Monster kernel: uart3: <16550 or compatible> at port 0x2e8-0x2ef irq 3 on isa0
Feb 4 13:33:38 Monster kernel: uart3: [GIANT-LOCKED]
Feb 4 13:33:38 Monster kernel: virtual chassis member-id = 255
Feb 4 13:33:38 Monster kernel: virtual chassis mode      = 0
Feb 4 13:33:38 Monster kernel: virtual chassis fpc-slots = 255
Feb 4 13:33:38 Monster kernel: virtual chassis effective fpc-slots = 12
Feb 4 13:33:38 Monster kernel: virtual chassis ifstate revert      = 1
Feb 4 13:33:38 Monster kernel: Initializing product: 33 ..
Feb 4 13:33:38 Monster kernel: Setting up M/T interface operations and attributes
Feb 4 13:33:38 Monster kernel: md0: Preloaded image </packages/sets/active/boot/os-kernel/contents.izo> 7826432 bytes at 0xffffffff81a5d990
Feb 4 13:33:38 Monster kernel: random: unblocking device.
Feb 4 13:33:38 Monster kernel: usbus0: 5.0Gbps Super Speed USB v3.0
Feb 4 13:33:38 Monster kernel: acb: acb_late_attach: Initializing silabs clocks to drive 8727 external phy
Feb 4 13:33:38 Monster kernel: JUNOS procfs is initialized.
Feb 4 13:33:38 Monster kernel: Timecounters tick every 1.000 msec
Feb 4 13:33:38 Monster kernel: Loading Redundant LT driver
Feb 4 13:33:38 Monster kernel: Registered AMT tunnel Encap with UDP Tunnel!
Feb 4 13:33:38 Monster kernel: ###PCB Group initialized for udppcbgroup
Feb 4 13:33:38 Monster kernel: ###PCB Group initialized for tcppcbgroup
Feb 4 13:33:38 Monster kernel: rts_init: registered inrtsock osd: slotid 3
Feb 4 13:33:38 Monster kernel: ugen0.1: <0x8086> at usbus0
Feb 4 13:33:38 Monster kernel: uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
Feb 4 13:33:38 Monster kernel: ada0 at ata0 bus 0 scbus0 target 1 lun 0
Feb 4 13:33:38 Monster kernel: ada0: <QEMU HARDDISK 1.7.2> ATA-7 device
Feb 4 13:33:38 Monster kernel: ada0: Serial Number QM00002
Feb 4 13:33:38 Monster kernel: ada0: 16.700MB/s transfers (WDMA2, PIO 8192bytes)
Feb 4 13:33:38 Monster kernel: ada0: 512MB (1048576 512 byte sectors)
Feb 4 13:33:38 Monster kernel: ada0: Previously was known as ad1
Feb 4 13:33:38 Monster kernel: SMP: AP CPU #2 Launched!
Feb 4 13:33:38 Monster kernel: SMP: AP CPU #1 Launched!
Feb 4 13:33:38 Monster kernel: SMP: AP CPU #3 Launched!
Feb 4 13:33:38 Monster kernel: Kernel thread "wkupdaemon" (pid 20) exited prematurely.
Feb 4 13:33:38 Monster kernel: Timecounter "TSC" frequency 2000045600 Hz quality 1000
Feb 4 13:33:38 Monster kernel: Root mount waiting for: usbus0
Feb 4 13:33:38 Monster kernel: uhub0: 21 ports with 21 removable, self powered
Feb 4 13:33:38 Monster kernel: Trying to mount root from cd9660:/dev/md0.uzip []...
Feb 4 13:33:38 Monster kernel: besw0: <Broadcom BCM56680 GigE Switch> mem 0xfeb80000-0xfeb8ffff irq 11 at device 4.0 on pci0
Feb 4 13:33:38 Monster kernel: Loading JUNOS chassis module
Feb 4 13:33:38 Monster kernel: chassis_init_hw_chassis_startup_time: chassis startup time 0.000000
Feb 4 13:33:38 Monster kernel: IPsec: Initialized Security Association Processing.
Feb 4 13:33:38 Monster kernel: pci-hgcomdev module loadedhgcommdev0: <HGCOMMDEV For Host VM communication> port 0xc000-0xc0ff mem 0xfeba8000-0xfeba8fff at device 22.0 on pci0
Feb 4 13:33:38 Monster kernel: hgcommdev0: hgcommdev: registers at 0xfffff800feba8000
Feb 4 13:33:38 Monster kernel: Loading the CHMIC module
Feb 4 13:33:38 Monster kernel: Loading POS driver
Feb 4 13:33:38 Monster kernel: Loading Aggregate sonet driver
Feb 4 13:33:38 Monster kernel: Loading the IMA Link Media Layer; Attaching to media services layer
Feb 4 13:33:38 Monster kernel: Loading the IMA Group Media Layer; Attaching to media services layer
Feb 4 13:33:38 Monster kernel: Loading the SONET Media Layer; Attaching to media services layer
Feb 4 13:33:38 Monster kernel: Loading the Protobuf-C module
Feb 4 13:33:38 Monster kernel: Loading the JAM-Core module
Feb 4 13:33:38 Monster kernel: Loading the JAM-Core module - succeeded
Feb 4 13:33:38 Monster kernel: Loading Multilink Services PICs module.
Feb 4 13:33:38 Monster kernel: Loading the M&T Platform NETPFE module
Feb 4 13:33:38 Monster kernel: MTX Platform JAM-Core module - load success
Feb 4 13:33:38 Monster kernel: MPC NG 2E/3E JAM Plugin: load succeeded
Feb 4 13:33:38 Monster kernel: Loading BCMSDK module.....
Feb 4 13:33:38 Monster kernel: bcm_sdk_init(): DevID = 0xb680, RevID = 0x12
Feb 4 13:33:38 Monster kernel: bcm_sdk_init: device ID: dev: 0xb680, rev: 0x12
Feb 4 13:33:38 Monster kernel: bcm_sdk_init: device unit no: 0
Feb 4 13:33:38 Monster kernel: bcm_soc_cm_device_init: device unit no: 0
Feb 4 13:33:38 Monster kernel: bcore_init: after soc_reset_init
Feb 4 13:33:38 Monster kernel: bcore_init: after soc_misc_init
Feb 4 13:33:38 Monster kernel: bcore_init: after soc_mmu_init
Feb 4 13:33:38 Monster kernel: bcore_init: before bcm_init
Feb 4 13:33:38 Monster kernel: bcore_init: before port stuff
Feb 4 13:33:38 Monster kernel: bcore_init: after port stuff
Feb 4 13:33:38 Monster kernel: bcore_init: link scan interval is (soc_property): 4000000
Feb 4 13:33:38 Monster kernel: bcore_mxseries_init: Finished mxseries port configuration
Feb 4 13:33:38 Monster kernel: bcore_init: Finished platform specific initialization
Feb 4 13:33:38 Monster kernel: bcm_sdk_init: Done sdk init
Feb 4 13:33:38 Monster kernel: veriexec: no signatures for device. file='/sbin/kats/cannot-exec' fsid=168 fileid=51404 gen=1 uid=0 pid=2852
Feb 4 13:33:38 Monster kernel: lag enhanced disabled 0
Feb 4 13:33:38 Monster jlaunchhelperd[4588]: initializing jlaunchhelperd
Feb 4 13:33:38 Monster jlaunchhelperd[4588]: jlaunchd created. Suspending until program state changes
Feb 4 13:33:38 Monster jlaunchhelperd[4590]: Launching /sbin/jlaunchd...
Feb 4 13:33:38 Monster root: /etc/rc: WARNING: run_rc_command: cannot run
Feb 4 13:33:38 Monster jlaunchd: watchdog (PID 4605) started
Feb 4 13:33:38 Monster watchdog: watchdog being started by pid 4590
Feb 4 13:33:38 Monster jlaunchd: bslockd (PID 4606) started
Feb 4 13:33:38 Monster kernel: mastership: sent other RE mastership loss signal
Feb 4 13:33:38 Monster jlaunchd: tnp-process (PID 4615) started
Feb 4 13:33:38 Monster jlaunchd: interface-control (PID 4616) started
Feb 4 13:33:38 Monster jlaunchd: chassis-control (PID 4617) started
Feb 4 13:33:38 Monster jlaunchd: app-engine-virtual-machine-management-service (PID 4618) started
Feb 4 13:33:38 Monster jlaunchd: alarm-control (PID 4619) started
Feb 4 13:33:38 Monster jlaunchd: craft-control (PID 4620) started
Feb 4 13:33:38 Monster jlaunchd: management (PID 4621) started
Feb 4 13:33:38 Monster sdk-vmmd: is_platform_rainier: Platform found as rainier
Feb 4 13:33:38 Monster jlaunchd: snmp (PID 4622) started
Feb 4 13:33:38 Monster jlaunchd: mib-process (PID 4623) started
Feb 4 13:33:38 Monster jlaunchd: inet-process (PID 4624) started
Feb 4 13:33:38 Monster jlaunchd: sntp (PID 4625) started
Feb 4 13:33:38 Monster jlaunchd: sntpsync (PID 4626) started
Feb 4 13:33:38 Monster jlaunchd: pfed (PID 4627) started
Feb 4 13:33:38 Monster jlaunchd: periodic-packet-services (PID 4628) started
Feb 4 13:33:38 Monster jlaunchd: disk-monitoring (PID 4629) started
Feb 4 13:33:38 Monster jlaunchd: kernel-replication (PID 4630) started
Feb 4 13:33:38 Monster jlaunchd: firewall (PID 4631) started
Feb 4 13:33:38 Monster jlaunchd: internal-routing-service (PID 4632) started
Feb 4 13:33:38 Monster jlaunchd: neighbor-liveness (PID 4633) started
Feb 4 13:33:38 Monster eventd[4637]: SYSTEM_OPERATIONAL: System is operational
Feb 4 13:33:38 Monster jlaunchd: jdid-management (PID 4641) started
Feb 4 13:33:38 Monster jlaunchd: subscriber-management (PID 4642) started
Feb 4 13:33:38 Monster jlaunchd: stats-agent (PID 4643) started
Feb 4 13:33:38 Monster kernel: mastership: sent other RE mastership loss signal
Feb 4 13:33:38 Monster jlaunchd: shm-rtsdbd (PID 4644) started
Feb 4 13:33:38 Monster jlaunchd: gstatd (PID 4645) started
Feb 4 13:33:38 Monster jlaunchd: transport-control (PID 4646) started
Feb 4 13:33:38 Monster jlaunchd: alarm-management (PID 4647) started
Feb 4 13:33:38 Monster jlaunchd: process-monitor (PID 4648) started
Feb 4 13:33:38 Monster jlaunchd: smg-service (PID 4649) started
Feb 4 13:33:38 Monster jlaunchd: application-identification (PID 4650) started
Feb 4 13:33:38 Monster jlaunchd: license-service (PID 4651) started
Feb 4 13:33:38 Monster jlaunchd: Starting of initial processes complete
Feb 4 13:33:38 Monster kernel: mastership: sent other RE mastership loss signal
Feb 4 13:33:38 Monster gstatd: gstatd is starting.
Feb 4 13:33:38 Monster gstatd: re-initialising gstatd
Feb 4 13:33:38 Monster gstatd: get_var_disk:/var resides on "/dev/gpt/var"
Feb 4 13:33:38 Monster bbe=smgd[4649]: bbe-smgd: main enhanced_broadband_edge_enabled 1, enhanced_broadband_edge_disable_knob 0 boot max_db_size 419430400, boot fSize 0, boot ppSize 0
Feb 4 13:33:38 Monster gstatd: get_var_disk: Command to find disk of /var:"/sbin/geom label status | grep "gpt/var""
Feb 4 13:33:38 Monster kernel: mastership: sent other RE mastership loss signal
Feb 4 13:33:38 Monster chassisd[4617]: JAM:PL: Registered attributes for c23
Feb 4 13:33:38 Monster mib2d[4623]: MIB2D_FILE_OPEN_FAILURE: Unable to open file '': No such file or directory
Feb 4 13:33:38 Monster gstatd: Monitoring device vtbd1 on under-perform
Feb 4 13:33:38 Monster chassisd[4617]: JAM:PL: Registered attributes for c24
Feb 4 13:33:38 Monster kernel: mastership: sent other RE mastership loss signal
Feb 4 13:33:38 Monster appidd[4650]: LICENSE_SOCKET_FAILURE: 'evConnect' failed for socket 11:
Feb 4 13:33:38 Monster chassisd[4617]: JAM:PL: Registered attributes for c25
Feb 4 13:33:39 Monster kernel: mastership: sent other RE mastership loss signal
Feb 4 13:33:39 Monster chassisd[4617]: JAM:PL: Registered attributes for c43
Feb 4 13:33:39 Monster chassisd[4617]: JAM: Plugin installed for stout_mic_12x40ge PIC.
Feb 4 13:33:39 Monster chassisd[4617]: JAM: Plugin installed for stout_mic_6x40ge PIC.
Feb 4 13:33:39 Monster chassisd[4617]: JAM: Plugin installed for stout_mic_8x100ge PIC.
Feb 4 13:33:39 Monster chassisd[4617]: JAM: Plugin installed for stout_mic_20x10ge PIC.
Feb 4 13:33:39 Monster chassisd[4617]: JAM: Plugin installed for stout_load_mic PIC.
Feb 4 13:33:39 Monster kernel: mastership: sent other RE mastership loss signal
Feb 4 13:33:39 Monster jdidd: JDID Internal version info: JDID Infra 3.8.4
Feb 4 13:33:39 Monster jdidd: jdid_plat_svcs_init called
Feb 4 13:33:39 Monster jdidd: plat_svcs_init: Model (mx480) not supported.
Feb 4 13:33:39 Monster jdidd: jdid_plat_svcs_init returned 1
Feb 4 13:33:39 Monster jdidd: jdid_plat_svcs_init failed, retval = 1, exit.
Feb 4 13:33:39 Monster jlaunchd: jdid-management (PID 4641) exited with status=0 Normal Exit
Feb 4 13:33:39 Monster jlaunchd: jdid-management (PID 4657) started
Feb 4 13:33:39 Monster kernel: mastership: sent other RE mastership loss signal
Feb 4 13:33:39 Monster kernel: mastership: sent other RE mastership loss signal
Feb 4 13:33:39 Monster bbe=smgd[4649]: bbe-smgd: bbe_smgd_init_core_dump_mode_brief:693 file not found - create it --> file /var/etc/junos-core-brief-mode
Feb 4 13:33:39 Monster craftd[4620]: craftd detected platform mx480
Feb 4 13:33:39 Monster kernel: mastership: sent other RE mastership loss signal
Feb 4 13:33:39 Monster alarmd[4619]: clksyncd connection succeeded after 0 retries
Feb 4 13:33:39 Monster alarmd[4619]: craftd connection succeeded after 0 retries
Feb 4 13:33:39 Monster alarmd[4619]: resending alarm state
Feb 4 13:33:39 Monster alarmd[4619]: 1#clearing alarms
Feb 4 13:33:39 Monster alarmd[4619]: 2#resending alarms
Feb 4 13:33:39 Monster kernel: mastership: sent other RE mastership loss signal
Feb 4 13:33:39 Monster dfwd[4631]: Not initializing dfwlib_listen_socket on backup
Feb 4 13:33:39 Monster bbe=smgd[4649]: PPPoE-MGMT: Init
Feb 4 13:33:39 Monster kernel: mastership: sent other RE mastership loss signal
Feb 4 13:33:39 Monster last message repeated 2 times
Feb 4 13:33:39 Monster bbe=smgd[4649]: shmlog log bbe-central-debug event id BBE_CENTRAL_IFL_RECONCILE_FLOW_NOTIFY_DESTROY_NO_RECONCILE_ENTRY string len 64 exceeds max of 64
Feb 4 13:33:39 Monster kernel: mastership: sent other RE mastership loss signal
Feb 4 13:33:39 Monster bbe=smgd[4649]: shmlog log bbe-jdhcp-debug event id BBE_JDHCP_CLIENT_GARBAGE_COLLECT_ITEM format string len of 96 exceeds max of 96
Feb 4 13:33:39 Monster bbe=smgd[4649]: shmlog log bbe-jdhcp-debug event id BBE_JDHCP_IPCCONN_RETRY_Q_ENTRY_ADD format string len of 102 exceeds max of 96
Feb 4 13:33:39 Monster bbe=smgd[4649]: shmlog log bbe-jdhcp-debug event id BBE_JDHCP_IPCCONN_RETRY_Q_ENTRY_REMOVE format string len of 102 exceeds max of 96
Feb 4 13:33:39 Monster kernel: mastership: sent other RE mastership loss signal
Feb 4 13:33:39 Monster bbe=smgd[4649]: smd_pppoe-notice created, eventCount: 108, configurableVerbosity: 0
Feb 4 13:33:39 Monster bbe=smgd[4649]: smd_pppoe-info created, eventCount: 122, configurableVerbosity: 0
Feb 4 13:33:39 Monster bbe=smgd[4649]: smd_pppoe-debug not created
Feb 4 13:33:39 Monster bbe=smgd[4649]: smd_pppoe-debug failed
Feb 4 13:33:39 Monster kernel: mastership: sent other RE mastership loss signal
Feb 4 13:33:40 Monster kernel: mastership: sent other RE mastership loss signal
Feb 4 13:33:40 Monster kernel: mastership: routing engine 0 becoming master tnp_local_addr:4
Feb 4 13:33:40 Monster kernel: mxseries_become_master: routing engine 0 became master after 1 usec
Feb 4 13:33:40 Monster kernel: NHACK_DEBUG: nhack_delete_in_use_list EntryNHACK_DEBUG: nhack_delete_free_list Entry
Feb 4 13:33:40 Monster kernel: NHACK_DEBUG: nhack_delete_in_use_list EntryNHACK_DEBUG: nhack_delete_free_list Entry
Feb 4 13:33:40 Monster alarmd[4619]: chassisd connection succeeded after 1 retries
Feb 4 13:33:40 Monster craftd[4620]: LIBJSNMP_SA_IPC_REG_ROWS: ns_subagent_register_mibs: registering 1 rows
Feb 4 13:33:40 Monster craftd[4620]: chassisd connection succeeded after 1 retries
Feb 4 13:33:40 Monster license-check[4651]: LIBJSNMP_SA_IPC_REG_ROWS: ns_subagent_register_mibs: registering 3 rows
Feb 4 13:33:40 Monster bfdd[4633]: LIBJSNMP_SA_IPC_REG_ROWS: ns_subagent_register_mibs: registering 3 rows
Feb 4 13:33:40 Monster chassisd[4617]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power off (jnxFruContentsIndex 7, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC @ 0/*/*, jnxFruType 3, jnxFruSlot 0, jnxFruOfflineReason 2, jnxFruLastPowerOff 4843, jnxFruLastPowerOn 0)
Feb 4 13:33:40 Monster pfed: LIBJSNMP_SA_IPC_REG_ROWS: ns_subagent_register_mibs: registering 2 rows
Feb 4 13:33:40 Monster jdhcpd: Registered new SHM-IPC user 'dhcpToAutoconf' within environment 'autoconf-dhcp'
Feb 4 13:33:40 Monster jdhcpd: Notifying producers about new consumer dhcpToAutoconf
Feb 4 13:33:40 Monster jdhcpd: Successfully registered SHM-IPC user 'dhcpToAutoconf' with uid 101
Feb 4 13:33:40 Monster jdhcpd: registerWithShmIpc: successfully create ipcAddr and user, dhcpToAutoconf, autoconfToDhcp
Feb 4 13:33:40 Monster alarm-mgmtd[4647]: LIBJSNMP_SA_IPC_REG_ROWS: ns_subagent_register_mibs: registering 5 rows
Feb 4 13:33:41 Monster jdhcpd: LIBJSNMP_SA_IPC_REG_ROWS: ns_subagent_register_mibs: registering 9 rows
Feb 4 13:33:41 Monster authd[4640]: LIBJSNMP_SA_IPC_REG_ROWS: ns_subagent_register_mibs: registering 11 rows
Feb 4 13:33:41 Monster authd[4640]: Startup: ISSU State is IDLE
Feb 4 13:33:43 Monster dcd[4616]: dcd_snd_init_cga: GRES not ready
Feb 4 13:33:43 Monster dcd[4616]: Not adding attribute: [link-protection-sub-group] in parsing database as attribute is already present
Feb 4 13:33:44 Monster chassisd[4617]: CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(0)
Feb 4 13:33:44 Monster chassisd[4617]: CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(1)
Feb 4 13:33:44 Monster chassisd[4617]: CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(2)
Feb 4 13:33:44 Monster chassisd[4617]: CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(3)
Feb 4 13:33:44 Monster chassisd[4617]: CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(4)
Feb 4 13:33:44 Monster chassisd[4617]: CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(5)
Feb 4 13:33:44 Monster chassisd[4617]: CHASSISD_IFDEV_DETACH_ALL_PSEUDO: ifdev_detach(pseudo devices: all)
Feb 4 13:33:44 Monster jdidd: JDID Internal version info: JDID Infra 3.8.4
Feb 4 13:33:44 Monster jdidd: jdid_plat_svcs_init called
Feb 4 13:33:44 Monster jdidd: plat_svcs_init: Model (mx480) not supported.
Feb 4 13:33:44 Monster jdidd: jdid_plat_svcs_init returned 1
Feb 4 13:33:44 Monster jdidd: jdid_plat_svcs_init failed, retval = 1, exit.
Feb 4 13:33:44 Monster jlaunchd: jdid-management (PID 4657) exited with status=0 Normal Exit
Feb 4 13:33:44 Monster jlaunchd: jdid-management (PID 4676) started
Feb 4 13:33:47 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pseudos: created pseudo interface device for demux0
Feb 4 13:33:47 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pseudos: created pseudo interface device for cbp0
Feb 4 13:33:47 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pseudos: created pseudo interface device for pip0
Feb 4 13:33:47 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pseudos: created pseudo interface device for pp0
Feb 4 13:33:47 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pseudos: created pseudo interface device for irb
Feb 4 13:33:47 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pseudos: created pseudo interface device for vtep
Feb 4 13:33:47 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pseudos: created pseudo interface device for esi
Feb 4 13:33:47 Monster snmpd[4622]: SNMPD_TRAP_COLD_START: trap_generate_cold: SNMP trap: cold start
Feb 4 13:33:47 Monster jlaunchd: interface-control (PID 4616) terminate signal 15 sent
Feb 4 13:33:47 Monster kernel: bcm_sdk_switch_port_phy_init: before switch port phy init stuff
Feb 4 13:33:47 Monster kernel: bcm_sdk_switch_port_phy_init: after switch port phy init stuff
Feb 4 13:33:47 Monster kernel: bcm_sdk_switch_port_phy_init: before switch port phy init stuff
Feb 4 13:33:47 Monster kernel: bcm_sdk_switch_port_phy_init: after switch port phy init stuff
Feb 4 13:33:47 Monster jlaunchd: alarm-control (PID 4619) terminate signal 15 sent
Feb 4 13:33:47 Monster jlaunchd: snmp (PID 4622) terminate signal 15 sent
Feb 4 13:33:47 Monster craftd[4620]: craftd_user_conn_shutdown: socket 11, errno = 0
Feb 4 13:33:47 Monster jlaunchd: mib-process (PID 4623) sending signal HUP: due to "proto-mastership": 0x1
Feb 4 13:33:47 Monster jlaunchd: routing (PID 4678) started
Feb 4 13:33:47 Monster jlaunchd: l2-learning (PID 4679) started
Feb 4 13:33:47 Monster jlaunchd: inet-process (PID 4624) sending signal USR1: due to "chas-mastership": 0x1
Feb 4 13:33:47 Monster jlaunchd: sonet-aps (PID 4680) started
Feb 4 13:33:47 Monster jlaunchd: sntp (PID 4625) terminate signal 15 sent
Feb 4 13:33:47 Monster jlaunchd: sntpsync (PID 4626) Signal 15 sent
Feb 4 13:33:47 Monster jlaunchd: pfed (PID 4627) sending signal USR2: due to "proto-mastership": 0x1
Feb 4 13:33:47 Monster mib2d[4623]: MIB2D_FILE_OPEN_FAILURE: Unable to open file '': No such file or directory
Feb 4 13:33:47 Monster pfed: pfed_sigusr2_handler enhanced_broadband_edge_enabled TRUE
Feb 4 13:33:47 Monster jlaunchd: remote-operations (PID 4681) started
Feb 4 13:33:47 Monster jlaunchd: class-of-service (PID 4682) started
Feb 4 13:33:47 Monster jlaunchd: periodic-packet-services (PID 4628) sending signal HUP: due to "proto-mastership": 0x1
Feb 4 13:33:47 Monster jlaunchd: link-management (PID 4683) started
Feb 4 13:33:47 Monster jlaunchd: kernel-replication (PID 4630) Signal 15 sent
Feb 4 13:33:47 Monster jlaunchd: firewall (PID 4631) terminate signal 15 sent
Feb 4 13:33:47 Monster jlaunchd: internal-routing-service (PID 4632) terminate signal 15 sent
Feb 4 13:33:47 Monster jlaunchd: routing-socket-proxy (PID 4684) started
Feb 4 13:33:47 Monster jlaunchd: pic-services-logging (PID 4685) started
Feb 4 13:33:47 Monster jlaunchd: neighbor-liveness (PID 4633) sending signal HUP: due to "proto-mastership": 0x1
Feb 4 13:33:47 Monster jlaunchd: redundancy-device (PID 4686) started
Feb 4 13:33:47 Monster jlaunchd: ppp (PID 4687) started
Feb 4 13:33:47 Monster jlaunchd: dynamic-flow-capture (PID 4688) started
Feb 4 13:33:47 Monster jlaunchd: event-processing (PID 4637) sending signal HUP: due to "chas-mastership": 0x1
Feb 4 13:33:48 Monster kernel: bcm_sdk_port_speed_set: before bcm_port_autoneg_set
Feb 4 13:33:48 Monster kernel: bcm_sdk_port_speed_set: before bcm_port_speed_set
Feb 4 13:33:48 Monster kernel: bcm_sdk_switch_port_phy_init: before switch port phy init stuff
Feb 4 13:33:48 Monster kernel: bcm_sdk_switch_port_phy_init: after switch port phy init stuff
Feb 4 13:33:48 Monster kernel: bcm_sdk_switch_port_phy_init: before switch port phy init stuff
Feb 4 13:33:48 Monster kernel: bcm_sdk_switch_port_phy_init: after switch port phy init stuff
Feb 4 13:33:48 Monster kernel: bcm_sdk_port_speed_set: before bcm_port_autoneg_set
Feb 4 13:33:48 Monster kernel: bcm_sdk_port_speed_set: before bcm_port_speed_set
Feb 4 13:33:48 Monster kernel: bcm_sdk_switch_port_phy_init: before switch port phy init stuff
Feb 4 13:33:48 Monster kernel: bcm_sdk_switch_port_phy_init: after switch port phy init stuff
Feb 4 13:33:48 Monster kernel: bcm_sdk_switch_port_phy_init: before switch port phy init stuff
Feb 4 13:33:48 Monster kernel: bcm_sdk_switch_port_phy_init: after switch port phy init stuff
Feb 4 13:33:48 Monster chassisd[4617]: LIBJSNMP_SA_IPC_REG_ROWS: ns_subagent_register_mibs: registering 151 rows
Feb 4 13:33:48 Monster clksyncd[4638]: LIBJSNMP_SA_IPC_REG_NONE: ns_subagent_register_mibs: no objects to register
Feb 4 13:33:48 Monster agentd[4697]: LIBJSNMP_SA_IPC_REG_ROWS: ns_subagent_register_mibs: registering 1 rows
Feb 4 13:33:48 Monster mib2d[4623]: LIBJSNMP_SA_IPC_REG_ROWS: ns_subagent_register_mibs: registering 104 rows
Feb 4 13:33:48 Monster pkid[4705]: LIBJSNMP_SA_IPC_REG_ROWS: ns_subagent_register_mibs: registering 2 rows
Feb 4 13:33:48 Monster rpd[4678]: JTASK_MODE_SWITCH: Switching to 64-bit mode
Feb 4 13:33:48 Monster clksyncd[4638]: LIBJSNMP_NS_LOG_WARNING: WARNING: Warning: Failed to connect to the agentx master agent (/var/run/snmpd_agentx): Unknown host (/var/run/snmpd_agentx) (Connection refused)
Feb 4 13:33:47 Monster jlaunchd: clksyncd-service (PID 4638) sending signal HUP: due to "proto-mastership": 0x1
Feb 4 13:33:47 Monster jlaunchd: l2cpd-service (PID 4689) started
Feb 4 13:33:47 Monster jlaunchd: tunnel-oamd (PID 4690) started
Feb 4 13:33:47 Monster jlaunchd: ethernet-link-fault-management (PID 4691) started
Feb 4 13:33:47 Monster jlaunchd: dhcp-service (PID 4639) sending signal USR2: due to "proto-mastership": 0x1
Feb 4 13:33:47 Monster jlaunchd: general-authentication-service (PID 4640) sending signal USR1: due to "proto-mastership": 0x1
Feb 4 13:33:47 Monster jlaunchd: ethernet-connectivity-fault-management (PID 4692) started
Feb 4 13:33:47 Monster jlaunchd: mpls-traceroute (PID 4693) started
Feb 4 13:33:47 Monster jlaunchd: secure-neighbor-discovery (PID 4694) started
Feb 4 13:33:48 Monster pkid[4705]: LIBJSNMP_NS_LOG_WARNING: WARNING: Warning: Failed to connect to the agentx master agent (/var/run/snmpd_agentx): Unknown host (/var/run/snmpd_agentx) (Connection refused)
Feb 4 13:33:48 Monster rpd[4678]: task_connect: addr /var/run/snmpd_agentx: Connection refused
Feb 4 13:33:48 Monster rpd[4678]: JTASK_SNMP_CONN_RETRY: snmp_task_socket_connect: reattempting connection to SNMP agent (/var/run/snmpd_agentx): Connection refused
Feb 4 13:33:48 Monster rpd[4678]: JTASK_TASK_BEGIN: Commencing routing updates version 15.1F7.3, built 2017-03-02 10:18:03 UTC by builder
Feb 4 13:33:48 Monster agentd[4697]: LIBJSNMP_NS_LOG_WARNING: WARNING: Warning: Failed to connect to the agentx master agent (/var/run/snmpd_agentx): Unknown host (/var/run/snmpd_agentx) (Connection refused)
Feb 4 13:33:48 Monster rmopd[4681]: LIBJSNMP_SA_IPC_REG_ROWS: ns_subagent_register_mibs: registering 28 rows
Feb 4 13:33:48 Monster cfmd[4692]: LIBJSNMP_SA_IPC_REG_ROWS: ns_subagent_register_mibs: registering 20 rows
Feb 4 13:33:48 Monster agentd[4697]: agentd_config_read: Entering config read. is_master:1
Feb 4 13:33:49 Monster dfcd[4688]: LIBJSNMP_SA_IPC_REG_ROWS: ns_subagent_register_mibs: registering 2 rows
Feb 4 13:33:49 Monster rmopd[4681]: LIBJSNMP_NS_LOG_WARNING: WARNING: Warning: Failed to connect to the agentx master agent (/var/run/snmpd_agentx): Unknown host (/var/run/snmpd_agentx) (Connection refused)
Feb 4 13:33:49 Monster cfmd[4692]: LIBJSNMP_NS_LOG_WARNING: WARNING: Warning: Failed to connect to the agentx master agent (/var/run/snmpd_agentx): Unknown host (/var/run/snmpd_agentx) (Connection refused)
Feb 4 13:33:49 Monster dot1xd[4704]: task_connect: addr /var/run/snmpd_agentx: Connection refused
Feb 4 13:33:49 Monster dot1xd[4704]: JTASK_SNMP_CONN_RETRY: snmp_task_socket_connect: reattempting connection to SNMP agent (/var/run/snmpd_agentx): Connection refused
Feb 4 13:33:49 Monster dfcd[4688]: LIBJSNMP_NS_LOG_WARNING: WARNING: Warning: Failed to connect to the agentx master agent (/var/run/snmpd_agentx): Unknown host (/var/run/snmpd_agentx) (Connection refused)
Feb 4 13:33:49 Monster jdidd: JDID Internal version info: JDID Infra 3.8.4
Feb 4 13:33:49 Monster jdidd: jdid_plat_svcs_init called
Feb 4 13:33:49 Monster jdidd: plat_svcs_init: Model (mx480) not supported.
Feb 4 13:33:49 Monster jdidd: jdid_plat_svcs_init returned 1
Feb 4 13:33:49 Monster jdidd: jdid_plat_svcs_init failed, retval = 1, exit.
Feb 4 13:33:49 Monster jlaunchd: jdid-management (PID 4676) exited with status=0 Normal Exit
Feb 4 13:33:49 Monster jlaunchd: jdid-management (PID 4757) started
Feb 4 13:33:49 Monster mib2d[4623]: LIBJSNMP_NS_LOG_WARNING: WARNING: Warning: Failed to connect to the agentx master agent (/var/run/snmpd_agentx): Unknown host (/var/run/snmpd_agentx) (Connection refused)
Feb 4 13:33:49 Monster l2cpd[4689]: task_connect: addr /var/run/snmpd_agentx: Connection refused
Feb 4 13:33:49 Monster l2cpd[4689]: JTASK_SNMP_CONN_RETRY: snmp_task_socket_connect: reattempting connection to SNMP agent (/var/run/snmpd_agentx): Connection refused
Feb 4 13:33:49 Monster l2cpd[4689]: task_connect: addr /var/run/l2ald_control: No such file or directory
Feb 4 13:33:49 Monster cosd[4682]: COSD_DEVICE_MISSING: Cannot locate device [index 64, unit 0]
Feb 4 13:33:49 Monster cosd[4682]: LIBJSNMP_SA_IPC_REG_ROWS: ns_subagent_register_mibs: registering 9 rows
Feb 4 13:33:49 Monster l2ald[4679]: LIBJSNMP_SA_IPC_REG_ROWS: ns_subagent_register_mibs: registering 3 rows
Feb 4 13:33:49 Monster l2ald[4679]: LIBJSNMP_NS_LOG_WARNING: WARNING: Warning: Failed to connect to the agentx master agent (/var/run/snmpd_agentx): Unknown host (/var/run/snmpd_agentx) (Connection refused)
Feb 4 13:33:49 Monster cosd[4682]: LIBJSNMP_NS_LOG_WARNING: WARNING: Warning: Failed to connect to the agentx master agent (/var/run/snmpd_agentx): Unknown host (/var/run/snmpd_agentx) (Connection refused)
Feb 4 13:33:52 Monster dcd[4708]: Not adding attribute: [link-protection-sub-group] in parsing database as attribute is already present
Feb 4 13:33:52 Monster snmpd[4709]: SNMPD_TRAP_COLD_START: trap_generate_cold: SNMP trap: cold start
Feb 4 13:33:52 Monster alarm-mgmtd[4714]: LIBJSNMP_SA_IPC_REG_ROWS: ns_subagent_register_mibs: registering 5 rows
Feb 4 13:33:52 Monster alarmd[4706]: chassisd connection succeeded after 0 retries
Feb 4 13:33:52 Monster alarmd[4706]: clksyncd connection succeeded after 0 retries
Feb 4 13:33:52 Monster alarmd[4706]: craftd connection succeeded after 0 retries
Feb 4 13:33:52 Monster alarmd[4706]: resending alarm state
Feb 4 13:33:52 Monster alarmd[4706]: 1#clearing alarms
Feb 4 13:33:52 Monster alarmd[4706]: 2#resending alarms
Feb 4 13:33:53 Monster transportd[4713]: LIBJSNMP_SA_IPC_REG_ROWS: ns_subagent_register_mibs: registering 33 rows
Feb 4 13:33:53 Monster ppmd[4628]: ppmd_cfm_open: new conn received 0x8b0c00c
Feb 4 13:33:53 Monster cfmd[4692]: cfmd_chassis_mac_addr_init:631 Done fetching reserved mac address. Going past mac-address init
Feb 4 13:33:53 Monster dfwd[4712]: dfwdlib_process_purge:10717 num_client_id = 1
Feb 4 13:33:53 Monster dfwd[4712]: dfwdlib_process_purge:10722 num_id_list[0] = 9
Feb 4 13:33:54 Monster jdidd: JDID Internal version info: JDID Infra 3.8.4
Feb 4 13:33:54 Monster jdidd: jdid_plat_svcs_init called
Feb 4 13:33:54 Monster jdidd: plat_svcs_init: Model (mx480) not supported.
Feb 4 13:33:54 Monster jdidd: jdid_plat_svcs_init returned 1
Feb 4 13:33:54 Monster jdidd: jdid_plat_svcs_init failed, retval = 1, exit.
Feb 4 13:33:54 Monster jlaunchd: jdid-management (PID 4757) exited with status=0 Normal Exit
Feb 4 13:33:54 Monster jlaunchd: jdid-management is thrashing, not restarted
Feb 4 13:33:54 Monster chassisd[4617]: CHASSISD_SNMP_TRAP10: SNMP trap generated: fabric plane offline (jnxFruContentsIndex 12, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName CB 0, jnxFruType 5, jnxFruSlot 0, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 5342)
Feb 4 13:33:54 Monster chassisd[4617]: CHASSISD_SNMP_TRAP10: SNMP trap generated: fabric plane offline (jnxFruContentsIndex 12, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName CB 0, jnxFruType 5, jnxFruSlot 0, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 5342)
Feb 4 13:33:55 Monster chassisd[4617]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 7, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: MPC2E NG PQ & Flex Q @ 0/*/*, jnxFruType 3, jnxFruSlot 0, jnxFruOfflineReason 2, jnxFruLastPowerOff 4843, jnxFruLastPowerOn 6273)
Feb 4 13:33:55 Monster chassisd[4617]: CHASSISD_SNMP_TRAP7: SNMP trap generated: fabric plane online (jnxFruContentsIndex 12, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName CB 0, jnxFruType 5, jnxFruSlot 0)
Feb 4 13:34:01 Monster chassisd[4617]: CHASSISD_SNMP_TRAP7: SNMP trap generated: fabric plane online (jnxFruContentsIndex 12, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName CB 0, jnxFruType 5, jnxFruSlot 0)
Feb 4 13:34:01 Monster alarmd[4706]: Alarm set: RE color=RED, class=CHASSIS, reason=Host 0 fxp0 : Ethernet Link Down
Feb 4 13:34:01 Monster craftd[4620]: Major alarm set, Host 0 fxp0 : Ethernet Link Down
Feb 4 13:34:37 Monster ppmd[4628]: ppmd_rpm_rpc_build_helper: 232 type 1
Feb 4 13:34:37 Monster kernel: pic_listener_connect: conn established: mgmt addr=0x80000010
Feb 4 13:34:37 Monster fpc0 ce_coc12_mic_module_init:1535: @# defaulting to NOT emitting syslogs for CE-COC12-MIC trace
Feb 4 13:34:39 Monster fpc0 CLKSYNC: master RE connection made
Feb 4 13:34:40 Monster fpc0 L2ALM master RE connection made
Feb 4 13:34:40 Monster jdhcpd: callback: Connection to peer timed out
Feb 4 13:34:41 Monster fpc0 pfe_pme_max 24
Feb 4 13:35:33 Monster ppmd[4628]: ppmd_delete_cfm_pending_entries: CFMD delete pending timer expired
Feb 4 13:35:33 Monster ppmd[4628]: ppmd_delete_cfm_pending_entries: connection received 0x8b0c00c
Feb 4 13:36:02 Monster chassisd[4617]: Use of MPC in IP services mode requires L3 bundle or license
Feb 4 13:36:03 Monster rdd[4686]: RDD Peer (Ident: 0) came up.
Feb 4 13:36:03 Monster chassisd[4617]: CHASSISD_SNMP_TRAP7: SNMP trap generated: Fru Online (jnxFruContentsIndex 7, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: MPC2E NG PQ & Flex Q @ 0/*/*, jnxFruType 3, jnxFruSlot 0)
Feb 4 13:36:03 Monster chassisd[4617]: CHASSISD_SNMP_TRAP3: ENTITY trap generated: entStateOperEnabled (entPhysicalIndex 7, entStateAdmin 4, entStateAlarm 0)
Feb 4 13:36:03 Monster chassisd[4617]: CHASSISD_SNMP_TRAP3: ENTITY trap generated: entStateOperEnabled (entPhysicalIndex 7, entStateAdmin 4, entStateAlarm 6)
Feb 4 13:36:03 Monster chassisd[4617]: Err: tunnel bandwidth 30000000000 not supported(0/0)
Feb 4 13:36:03 Monster last message repeated 8 times
Feb 4 13:36:03 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: fpc_create_devs_from_queue: created interface device for lc-0/0/0
Feb 4 13:36:03 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: fpc_create_devs_from_queue: created interface device for si-0/0/0
Feb 4 13:36:03 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: fpc_create_devs_from_queue: created interface device for pfh-0/0/0
Feb 4 13:36:03 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: fpc_create_devs_from_queue: created interface device for pfe-0/0/0
Feb 4 13:36:03 Monster chassisd[4617]: Err: tunnel bandwidth 30000000000 not supported(0/0)
Feb 4 13:36:03 Monster last message repeated 8 times
Feb 4 13:36:03 Monster kernel: GENCFG: op 32 (Resync blob) failed; err 7 (Doesn't Exist)
Feb 4 13:36:03 Monster fpc0 Power off ports setting: 0
Feb 4 13:36:05 Monster kernel: GENCFG: op 32 (Resync blob) failed; err 7 (Doesn't Exist)
Feb 4 13:36:05 Monster kernel: IF_MSG_IFD_BULK_MUP_DOWN: IFD[0] idx 49156 is NULL; peer type 17 index 0 ignored
Feb 4 13:36:05 Monster kernel: IF_MSG_IFD_BULK_MUP_DOWN: IFD[1] idx 49157 is NULL; peer type 17 index 0 ignored
Feb 4 13:36:05 Monster kernel: IF_MSG_IFD_BULK_MUP_DOWN: IFD[2] idx 53273 is NULL; peer type 17 index 0 ignored
Feb 4 13:36:05 Monster kernel: IF_MSG_IFD_BULK_MUP_DOWN: IFD[3] idx 53274 is NULL; peer type 17 index 0 ignored
Feb 4 13:36:05 Monster kernel: IF_MSG_IFD_BULK_MUP_DOWN: IFD[4] idx 53275 is NULL; peer type 17 index 0 ignored
Feb 4 13:36:05 Monster kernel: IF_MSG_IFD_BULK_MUP_DOWN: IFD[5] idx 53254 is NULL; peer type 17 index 0 ignored
Feb 4 13:36:05 Monster kernel: IF_MSG_IFD_BULK_MUP_DOWN: IFD[6] idx 53256 is NULL; peer type 17 index 0 ignored
Feb 4 13:36:05 Monster kernel: IF_MSG_IFD_BULK_ALARM: IFD is NULL (0/53256); ignored
Feb 4 13:36:09 Monster fpc0 CLKSYNC: Transitioned to centralized mode
Feb 4 13:36:10 Monster chassisd[4617]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 8, jnxFruL1Index 1, jnxFruL2Index 1, jnxFruL3Index 0, jnxFruName PIC: @ 0/0/*, jnxFruType 11, jnxFruSlot 0, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 13784)
Feb 4 13:36:10 Monster chassisd[4617]: CHASSISD_SNMP_TRAP3: ENTITY trap generated: entStateOperEnabled (entPhysicalIndex 25, entStateAdmin 4, entStateAlarm 0)
Feb 4 13:36:10 Monster chassisd[4617]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 8, jnxFruL1Index 1, jnxFruL2Index 2, jnxFruL3Index 0, jnxFruName PIC: @ 0/1/*, jnxFruType 11, jnxFruSlot 0, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 13788)
Feb 4 13:36:10 Monster chassisd[4617]: CHASSISD_SNMP_TRAP3: ENTITY trap generated: entStateOperEnabled (entPhysicalIndex 26, entStateAdmin 4, entStateAlarm 0)
Feb 4 13:36:11 Monster chassisd[4617]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 8, jnxFruL1Index 1, jnxFruL2Index 3, jnxFruL3Index 0, jnxFruName PIC: @ 0/2/*, jnxFruType 11, jnxFruSlot 0, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 13847)
Feb 4 13:36:11 Monster chassisd[4617]: CHASSISD_SNMP_TRAP3: ENTITY trap generated: entStateOperEnabled (entPhysicalIndex 27, entStateAdmin 4, entStateAlarm 0)
Feb 4 13:36:11 Monster chassisd[4617]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 8, jnxFruL1Index 1, jnxFruL2Index 4, jnxFruL3Index 0, jnxFruName PIC: @ 0/3/*, jnxFruType 11, jnxFruSlot 0, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 13849)
Feb 4 13:36:11 Monster chassisd[4617]: CHASSISD_SNMP_TRAP3: ENTITY trap generated: entStateOperEnabled (entPhysicalIndex 28, entStateAdmin 4, entStateAlarm 0)
Feb 4 13:36:12 Monster fpc0 Calling 4p 80g shim
Feb 4 13:36:15 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for ge-0/0/0
Feb 4 13:36:15 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for ge-0/0/1
Feb 4 13:36:15 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for ge-0/0/2
Feb 4 13:36:15 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for ge-0/0/3
Feb 4 13:36:15 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for ge-0/0/4
Feb 4 13:36:15 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for ge-0/0/5
Feb 4 13:36:15 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for ge-0/0/6
Feb 4 13:36:15 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for ge-0/0/7
Feb 4 13:36:15 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for ge-0/0/8
Feb 4 13:36:15 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for ge-0/0/9
Feb 4 13:36:16 Monster fpc0 mic_sfp_pca9548_swtbl_clean: Reset MUX to SFP ports
Feb 4 13:36:16 Monster fpc0 Reset media mux for mic slot 0
Feb 4 13:36:17 Monster fpc0 MIC(0/0)(0): SFP plugged in
Feb 4 13:36:17 Monster fpc0 MIC(0/0)(2): SFP plugged in
Feb 4 13:36:17 Monster fpc0 MIC(0/0)(4): SFP plugged in
Feb 4 13:36:17 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for ge-0/1/0
Feb 4 13:36:17 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for ge-0/1/1
Feb 4 13:36:17 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for ge-0/1/2
Feb 4 13:36:17 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for ge-0/1/3
Feb 4 13:36:17 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for ge-0/1/4
Feb 4 13:36:17 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for ge-0/1/5
Feb 4 13:36:17 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for ge-0/1/6
Feb 4 13:36:17 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for ge-0/1/7
Feb 4 13:36:17 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for ge-0/1/8
Feb 4 13:36:17 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for ge-0/1/9
Feb 4 13:36:17 Monster chassisd[4617]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 20, jnxFruL1Index 1, jnxFruL2Index 1, jnxFruL3Index 0, jnxFruName MIC: 3D 20x 1GE(LAN)-E,SFP @ 0/0/*, jnxFruType 11, jnxFruSlot 0, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 0)
Feb 4 13:36:19 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for xe-0/2/0
Feb 4 13:36:19 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for xe-0/2/1
Feb 4 13:36:19 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for xe-0/3/0
Feb 4 13:36:19 Monster chassisd[4617]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for xe-0/3/1
Feb 4 13:36:19 Monster chassisd[4617]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 20, jnxFruL1Index 1, jnxFruL2Index 2, jnxFruL3Index 0, jnxFruName MIC: 3D 4x 10GE XFP @ 0/1/*, jnxFruType 11, jnxFruSlot 0, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 0)
Feb 4 13:36:23 Monster fpc0 xfp-0/2/0 plugged in
Feb 4 13:36:23 Monster fpc0 xfp-0/2/1 plugged in
Feb 4 13:36:24 Monster fpc0 xfp-0/3/0 plugged in
Feb 4 13:36:24 Monster fpc0 xfp-0/3/1 plugged in
Feb 4 13:36:29 Monster fpc0 MIC(0/0) link 0 SFP laser bias current low alarm cleared
Feb 4 13:36:29 Monster fpc0 MIC(0/0) link 0 SFP output power low alarm cleared
Feb 4 13:36:29 Monster fpc0 MIC(0/0) link 0 SFP laser bias current low warning cleared
Feb 4 13:36:29 Monster fpc0 MIC(0/0) link 0 SFP output power low warning cleared
Feb 4 13:36:29 Monster fpc0 MIC(0/0) link 2 SFP laser bias current low alarm cleared
Feb 4 13:36:29 Monster fpc0 MIC(0/0) link 2 SFP output power low alarm cleared
Feb 4 13:36:29 Monster fpc0 MIC(0/0) link 2 SFP laser bias current low warning cleared
Feb 4 13:36:29 Monster fpc0 MIC(0/0) link 2 SFP output power low warning cleared
Feb 4 13:36:30 Monster fpc0 MIC(0/0) link 4 SFP laser bias current low alarm cleared
Feb 4 13:36:30 Monster fpc0 MIC(0/0) link 4 SFP output power low alarm cleared
Feb 4 13:36:30 Monster fpc0 MIC(0/0) link 4 SFP laser bias current low warning cleared
Feb 4 13:36:30 Monster fpc0 MIC(0/0) link 4 SFP output power low warning cleared
Feb 4 13:37:34 Monster login: Login attempt for user amousa from host 93.184.4.10
Feb 4 13:37:35 Monster login[4784]: (pam_sm_authenticate): DEBUG: PAM_USER: amousa
Feb 4 13:37:35 Monster login[4784]: (pam_sm_authenticate): DEBUG: Updating lock-attempts of user: amousa       attempts: 1
Feb 4 13:37:35 Monster login[4784]: (pam_sm_acct_mgmt): DEBUG: PAM_USER: amousa
Feb 4 13:37:35 Monster login[4784]: LOGIN_INFORMATION: User amousa logged in from host 93.184.4.10 on device pts/0
Feb 4 13:37:39 Monster mgd[4786]: UI_DBASE_LOGIN_EVENT: User 'amousa' entering configuration mode
Feb 4 13:37:50 Monster mgd[4786]: UI_LOAD_EVENT: User 'amousa' is performing a 'rollback 1'
Feb 4 13:37:52 Monster mgd[4786]: UI_COMMIT: User 'amousa' requested 'commit' operation (comment: none)
Feb 4 13:37:52 Monster mgd[4786]: UI_CHILD_EXITED: Child exited: PID 4791, status 7, command '/usr/sbin/mustd'
Feb 4 13:37:52 Monster jpppd: pid = 4806: PppIssuMgr: ctor
Feb 4 13:37:52 Monster jpppd: Ppp::~Ppp entered
Feb 4 13:37:52 Monster sdk-vmmd: is_platform_rainier: Platform found as rainier
Feb 4 13:37:52 Monster chassisd[4793]: JAM:PL: Registered attributes for c23
Feb 4 13:37:52 Monster chassisd[4793]: JAM:PL: Registered attributes for c24
Feb 4 13:37:52 Monster chassisd[4793]: JAM:PL: Registered attributes for c25
Feb 4 13:37:53 Monster chassisd[4793]: JAM:PL: Registered attributes for c43
Feb 4 13:37:53 Monster chassisd[4793]: JAM: Plugin installed for stout_mic_12x40ge PIC.
Feb 4 13:37:53 Monster chassisd[4793]: JAM: Plugin installed for stout_mic_6x40ge PIC.
Feb 4 13:37:53 Monster chassisd[4793]: JAM: Plugin installed for stout_mic_8x100ge PIC.
Feb 4 13:37:53 Monster chassisd[4793]: JAM: Plugin installed for stout_mic_20x10ge PIC.
Feb 4 13:37:53 Monster chassisd[4793]: JAM: Plugin installed for stout_load_mic PIC.
Feb 4 13:37:54 Monster ffp[4815]: "dynamic-profiles": No change to profiles
Feb 4 13:37:54 Monster mib2d[4623]: MIB2D_FILE_OPEN_FAILURE: Unable to open file '': No such file or directory
Feb 4 13:37:54 Monster jlaunchd: jdid-management (PID 4823) started
Feb 4 13:37:54 Monster jlaunchd: ppp-service (PID 4824) started
Feb 4 13:37:54 Monster jlaunchd: l2tp-universal-edge (PID 4825) started
Feb 4 13:37:54 Monster jlaunchd: datapath-trace-service (PID 4826) started
Feb 4 13:37:54 Monster jlaunchd: can not access /usr/sbin/overlayd: No such file or directory
Feb 4 13:37:54 Monster jlaunchd: overlay-ping-traceroute (PID 0) started
Feb 4 13:37:54 Monster jdidd: JDID Internal version info: JDID Infra 3.8.4
Feb 4 13:37:54 Monster jdidd: jdid_plat_svcs_init called
Feb 4 13:37:54 Monster jdidd: plat_svcs_init: Model (mx480) not supported.
Feb 4 13:37:54 Monster jdidd: jdid_plat_svcs_init returned 1
Feb 4 13:37:54 Monster jdidd: jdid_plat_svcs_init failed, retval = 1, exit.
Feb 4 13:37:54 Monster jlaunchd: jdid-management (PID 4823) exited with status=0 Normal Exit
Feb 4 13:37:54 Monster mgd[4786]: UI_COMMIT_COMPLETED: commit complete
Feb 4 13:37:54 Monster jlaunchd: jdid-management (PID 4832) started
Feb 4 13:37:54 Monster jpppd: pid = 4824: PppIssuMgr: ctor
Feb 4 13:37:54 Monster jl2tpd: jl2tpd-notice created, eventCount: 993, configurableVerbosity: 1
Feb 4 13:37:54 Monster jpppd: jpppd-notice created, eventCount: 461, configurableVerbosity: 1
Feb 4 13:37:54 Monster jl2tpd: jl2tpd-info created, eventCount: 132, configurableVerbosity: 1
Feb 4 13:37:54 Monster jpppd: jpppd-info created, eventCount: 149, configurableVerbosity: 1
Feb 4 13:37:54 Monster jl2tpd: jl2tpd-debug created, eventCount: 905, configurableVerbosity: 1
Feb 4 13:37:54 Monster jpppd: jpppd-debug created, eventCount: 1316, configurableVerbosity: 1
Feb 4 13:37:54 Monster jl2tpd: shmlog log jl2tpd-debug event id destinationSfTransmitEnableTimerRestarted format lastProcessUid=%d, tunnelsProcessed=%d and argcnt 1 format cnt 2 arg types 0 0 appear incompatible. Event data will be shown as integers
Feb 4 13:37:54 Monster jl2tpd: shmlog log jl2tpd-debug event id destinationSfTransmitEnableProcessingComplete format lastProcessUid=%d, tunnelsProcessed=%d and argcnt 1 format cnt 2 arg types 0 0 appear incompatible. Event data will be shown as integers
Feb 4 13:37:54 Monster jl2tpd: shmlog log jl2tpd-debug event id destinationFpTransmitEnableTimerRestarted format lastProcessUid=%d, tunnelsProcessed=%d and argcnt 1 format cnt 2 arg types 0 0 appear incompatible. Event data will be shown as integers
Feb 4 13:37:54 Monster jl2tpd: shmlog log jl2tpd-debug event id destinationFpTransmitEnableProcessingComplete format lastProcessUid=%d, tunnelsProcessed=%d and argcnt 1 format cnt 2 arg types 0 0 appear incompatible. Event data will be shown as integers
Feb 4 13:37:54 Monster jl2tpd: shmlog log jl2tpd-debug event id sessionScavenge format sessionUid=%d, tunnelUid=%d, status=%d, lsid=%d, tunnel_id_key=%d and argcnt 4 format cnt 5 arg types 0 0 0 0 0 appear incompatible. Event data will be shown as integers
Feb 4 13:37:54 Monster jl2tpd: shmlog log jl2tpd-debug event id sessionSetConnectSpeed format sessionUid=%d, tx=%d*1000, rx=%d*1000, lsid=%d, tunnel_id_key=%d and argcnt 4 format cnt 5 arg types 0 0 0 0 0 appear incompatible. Event data will be shown as integers
Feb 4 13:37:54 Monster jl2tpd: shmlog log jl2tpd-debug event id tunnelDownSessionProcessCount format tunnelUid=%d, sessioncount=%d, size=%d, tunnel_id_key=%d and argcnt 3 format cnt 4 arg types 0 0 0 0 appear incompatible. Event data will be shown as integers
Feb 4 13:37:54 Monster jpppd: shmlog log jpppd-debug event id l2tpReceiveDataPacket format %s, %s, %s, tunnelId=%d sessionId=%d and argcnt 5 format cnt 5 arg types 7 7 9 9 0 appear incompatible. Event data will be shown as integers
Feb 4 13:37:54 Monster jpppd: shmlog log jpppd-debug event id l2tpApplyLinkInterfaceAttributes format %s, local magic number %s, peer magic number =%s, localtunnelId=%d localsessionId=%d and argcnt 6 format cnt 5 arg types 7 7 0 0 0 0 appear incompatible. Event data will be shown as integers
Feb 4 13:37:54 Monster jpppd: initDebugEvents: Failed to read trace filters
Feb 4 13:37:54 Monster jl2tpd: Registered new SHM-IPC user 'jl2tpd' within environment 'ppp-l2tp'
Feb 4 13:37:54 Monster jl2tpd: Notifying producers about new consumer jl2tpd
Feb 4 13:37:54 Monster jl2tpd: Successfully registered SHM-IPC user 'jl2tpd' with uid 101
Feb 4 13:37:54 Monster jl2tpd: registerWithShmIpc: successfully create ipcAddr and user, jl2tpd, jpppd
Feb 4 13:37:55 Monster jpppd: Registered new SHM-IPC user 'pppToPppoe' within environment 'ppp-pppoe'
Feb 4 13:37:55 Monster jpppd: Notifying producers about new consumer pppToPppoe
Feb 4 13:37:55 Monster jpppd: Successfully registered SHM-IPC user 'pppToPppoe' with uid 101
Feb 4 13:37:55 Monster jpppd: registerWithShmIpc: successfully create ipcAddr and user, pppToPppoe, pppoeToPpp
Feb 4 13:37:58 Monster jpppd: Registered new SHM-IPC user 'jpppd' within environment 'ppp-l2tp'
Feb 4 13:37:58 Monster jpppd: Notifying producers about new consumer jpppd
Feb 4 13:37:58 Monster jpppd: Successfully registered SHM-IPC user 'jpppd' with uid 102
Feb 4 13:37:58 Monster jpppd: registerWithShmIpc: successfully create ipcAddr and user, jpppd, jl2tpd
Feb 4 13:37:58 Monster jl2tpd: connHandler: got a connect callback, name jpppd, status 2
Feb 4 13:37:58 Monster jpppd: connHandler: got a connect callback, name jl2tpd, status 2
Feb 4 13:37:59 Monster jdidd: JDID Internal version info: JDID Infra 3.8.4
Feb 4 13:37:59 Monster jdidd: jdid_plat_svcs_init called
Feb 4 13:37:59 Monster jdidd: plat_svcs_init: Model (mx480) not supported.
Feb 4 13:37:59 Monster jdidd: jdid_plat_svcs_init returned 1
Feb 4 13:37:59 Monster jdidd: jdid_plat_svcs_init failed, retval = 1, exit.
Feb 4 13:37:59 Monster jlaunchd: jdid-management (PID 4832) exited with status=0 Normal Exit
Feb 4 13:37:59 Monster jlaunchd: jdid-management (PID 4833) started
Feb 4 13:38:04 Monster jdidd: JDID Internal version info: JDID Infra 3.8.4
Feb 4 13:38:04 Monster jdidd: jdid_plat_svcs_init called
Feb 4 13:38:04 Monster jdidd: plat_svcs_init: Model (mx480) not supported.
Feb 4 13:38:04 Monster jdidd: jdid_plat_svcs_init returned 1
Feb 4 13:38:04 Monster jdidd: jdid_plat_svcs_init failed, retval = 1, exit.
Feb 4 13:38:04 Monster jlaunchd: jdid-management (PID 4833) exited with status=0 Normal Exit
Feb 4 13:38:04 Monster jlaunchd: jdid-management (PID 4834) started
Feb 4 13:38:09 Monster jdidd: JDID Internal version info: JDID Infra 3.8.4
Feb 4 13:38:09 Monster jdidd: jdid_plat_svcs_init called
Feb 4 13:38:09 Monster jdidd: plat_svcs_init: Model (mx480) not supported.
Feb 4 13:38:09 Monster jdidd: jdid_plat_svcs_init returned 1
Feb 4 13:38:09 Monster jdidd: jdid_plat_svcs_init failed, retval = 1, exit.
Feb 4 13:38:09 Monster jlaunchd: jdid-management (PID 4834) exited with status=0 Normal Exit
Feb 4 13:38:09 Monster jlaunchd: jdid-management is thrashing, not restarted
Feb 4 13:38:55 Monster jpppd: callback: Connection to peer timed out
2. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

0 Recommend
rnayar
Posted 02-04-2018 04:47

Reply Reply Privately
what is the RE model the you are using?

Regards,

Rahul
3. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

0 Recommend
Erdem
Posted 02-04-2018 05:00

Reply Reply Privately
RE bios

Spoiler
Routing Engine BIOS Version: NGRE_v00.53.00.01

RE status

Spoiler
Routing Engine status:
Slot 0:
    Current state                  Master
    Election priority              Master (default)
    Temperature                 32 degrees C / 89 degrees F
    CPU temperature             47 degrees C / 116 degrees F
    DRAM                      49117 MB (49152 MB installed)
    Memory utilization           5 percent
    5 sec CPU utilization:
      User                       0 percent
      Background                 0 percent
      Kernel                     1 percent
      Interrupt                  0 percent
      Idle                      99 percent
    1 min CPU utilization:
      User                       0 percent
      Background                 0 percent
      Kernel                     1 percent
      Interrupt                  0 percent
      Idle                      99 percent
    5 min CPU utilization:
      User                       0 percent
      Background                 0 percent
      Kernel                     1 percent
      Interrupt                  0 percent
      Idle                      99 percent
    15 min CPU utilization:
      User                       0 percent
      Background                 0 percent
      Kernel                     1 percent
      Interrupt                  0 percent
      Idle                      98 percent
    Model                          RE-S-2X00x6
    Serial ID                      CAJX7941
    Start time                     2018-02-04 13:32:52 IST
    Uptime                         1 hour, 4 minutes, 39 seconds
    Last reboot reason             0x4000:VJUNOS reboot
    Load averages:                 1 minute   5 minute 15 minute
                                       0.21       0.23       0.23

RE details

Spoiler
Hardware inventory:
Item             Version Part number Serial number     Description
Chassis                                JN126ADABAFB      MX480
Midplane         REV 46   750-047862   ACRK4568          Enhanced MX480 Midplane
FPM Board        REV 04   760-059208   CAJP6899          Front Panel Display
PEM 0            Rev 01   740-063046   QCS1746U0BK       PS 1.4-2.52kW; 90-264V AC in
PEM 1            Rev 01   740-063046   QCS1744U1FA       PS 1.4-2.52kW; 90-264V AC in
PEM 2            Rev 01   740-063046   QCS1746U023       PS 1.4-2.52kW; 90-264V AC in
PEM 3            Rev 01   740-063046   QCS1746U0CV       PS 1.4-2.52kW; 90-264V AC in
Routing Engine 0 REV 16   750-054758   CAJX7941          RE-S-2X00x6
CB 0             REV 09   750-062572   CAJZ4066          Enhanced MX SCB 2
FPC 0            REV 11   750-063184   CAJX6658          MPC2E NG PQ & Flex Q
CPU            REV 13   711-045719   CAJX1272          RMPC PMB
MIC 0          REV 18   750-049846   CAJW9955          3D 20x 1GE(LAN)-E,SFP
    PIC 0                 BUILTIN      BUILTIN           10x 1GE(LAN) -E SFP
      Xcvr 0     REV 01   740-031850   NYF1QKM           SFP-LX10
      Xcvr 2     REV 01   740-031850   NYF0WGJ           SFP-LX10
      Xcvr 4     REV 01   740-031850   NYF0X8L           SFP-LX10
    PIC 1                 BUILTIN      BUILTIN           10x 1GE(LAN) -E SFP
MIC 1          REV 33   750-028387   CAHX5975          3D 4x 10GE XFP
    PIC 2                 BUILTIN      BUILTIN           2x 10GE XFP
      Xcvr 0     REV 01   740-031833   AYF1BMN           XFP-10G-LR
      Xcvr 1     REV 01   740-031833   AYD1LCM           XFP-10G-LR
    PIC 3                 BUILTIN      BUILTIN           2x 10GE XFP
      Xcvr 0     REV 01   740-031833   AYF1ND3           XFP-10G-LR
      Xcvr 1     REV 01   740-031833   AYF1BLL           XFP-10G-LR
Fan Tray                                                 Enhanced Left Fan Tray
4. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4
Best Answer

0 Recommend
rnayar
Posted 02-04-2018 05:06

Reply Reply Privately
Thank you. So you're using NGRE.

Prerequisite for Next Generation Routing Engine:
On MX960, MX480, MX240 and PTX5000, NG-RE will be supported from 15.1F3, 16.1R1 and higher.

On MX2K, NG-RE will be supported from 15.1F5, 16.1R2, 16.2R1 and higher.

Please refer below link: https://kb.juniper.net/resources/sites/CUSTOMERSERVICE/content/live/TECHNOTES/0/TN303/en_US/NextGenRoutingEngine_Tech_Intro.pdf

Please download 16.1R6 recommended subscriber-management release.

Regards,

Rahul
5. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

0 Recommend
Erdem
Posted 02-04-2018 06:03

Reply Reply Privately
Dear rahoul , I see this alerts on download page ???

Alerts

High: The Junos software version 16.1R1 is supported on MX Series routers only. It does not include support for CLNS, ISSU, J-Web, PTP, Virtual Chassis, VXLAN, and Subscriber Management Services. Please check the release note for Junos software version 16.1R1 for more details about features supported in the release.

High: Customers using MX Series platforms with NG MPCs may have a different Recommended Release than is listed on this page. Please see Juniper TAC Recommendation for the Recommended Release for your platform.
6. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

0 Recommend
rnayar
Posted 02-04-2018 06:30

Reply Reply Privately
Hi,

Subscriber-management support on 16.1 starting from R4. Latest one is 16.1 R6.

Regards,
Rahul N
7. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

0 Recommend
Erdem
Posted 02-05-2018 00:46

Reply Reply Privately
I have one RE , so if i upgrade vmhost and reboot , is current junos will wake up with new vmhost ?? I suppose that new vmhost will support old junos . is that right .

I install vmhost 16.1R6-S1 and junos 16.1R6-S1 .
8. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

0 Recommend
rnayar
Posted 02-05-2018 01:47

Reply Reply Privately
When you upgrade using junos-vmhost-install-x.tgz,it upgrades both the host software and Junos OS.
9. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

0 Recommend
Erdem
Posted 02-05-2018 03:40

Reply Reply Privately
Great Rahul

The upgrade to 16.1R6 completed successfuly .

but I can't commit any configuration .

error: ffp_intf_ifd_hier_tagging_config_verify: Modified IFD "si-0/0/0" flags 0x2020 is in use by BBE subscriber, commit denied - hierarchical-scheduler config changed
error: foreign file propagation (ffp) failed

just after remove hierarchical-scheduler under interface si-0/0/0 .

all thing now is work successfuly . but what the affect of deactivate this command ??
10. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

0 Recommend
rnayar
Posted 02-05-2018 03:51

Reply Reply Privately
Hi,

Please use the below configuration and let me know you're seeing any issue. I would request you to open thread to avoid mixing of issues.

MX> show configuration interfaces si-0/0/0
hierarchical-scheduler maximum-hierarchy-levels 2;
encapsulation generic-services;
unit 0 {
family inet;
family inet6;
}

Regards,

Rahul
11. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

0 Recommend
Erdem
Posted 02-05-2018 04:19

Reply Reply Privately
the process of commit

Spoiler

Spoiler

amousa@MX480# commit

error: ffp_intf_ifd_hier_tagging_config_verify: Modified IFD "si-0/0/0" flags 0x2020 is in use by BBE subscriber, commit denied - hierarchical-scheduler config changed
error: foreign file propagation (ffp) failed

amousa@MX480# deactivate interfaces si-0/0/0 hierarchical-scheduler

[edit]
amousa@MX480# commit
commit complete

amousa@MX480# show interfaces si-0/0/0
inactive: hierarchical-scheduler maximum-hierarchy-levels 2;
encapsulation generic-services;
unit 0 {
family inet;
}

Version status

Spoiler
Model: mx480
Junos: 16.1R6-S1.1
JUNOS OS Kernel 64-bit [20171207.04b87e3_builder_stable_10]
JUNOS OS libs [20171207.04b87e3_builder_stable_10]
JUNOS OS runtime [20171207.04b87e3_builder_stable_10]
JUNOS OS time zone information [20171207.04b87e3_builder_stable_10]
JUNOS network stack and utilities [20171229.043805_builder_junos_161_r6_s1]
JUNOS libs [20171229.043805_builder_junos_161_r6_s1]
JUNOS OS libs compat32 [20171207.04b87e3_builder_stable_10]
JUNOS OS 32-bit compatibility [20171207.04b87e3_builder_stable_10]
JUNOS libs compat32 [20171229.043805_builder_junos_161_r6_s1]
JUNOS runtime [20171229.043805_builder_junos_161_r6_s1]
Junos vmguest package [20171229.043805_builder_junos_161_r6_s1]
JUNOS py extensions [20171229.043805_builder_junos_161_r6_s1]
JUNOS py base [20171229.043805_builder_junos_161_r6_s1]
JUNOS OS vmguest [20171207.04b87e3_builder_stable_10]
JUNOS OS crypto [20171207.04b87e3_builder_stable_10]
JUNOS mx libs compat32 [20171229.043805_builder_junos_161_r6_s1]
JUNOS mx runtime [20171229.043805_builder_junos_161_r6_s1]
JUNOS common platform support [20171229.043805_builder_junos_161_r6_s1]
JUNOS modules [20171229.043805_builder_junos_161_r6_s1]
JUNOS mx modules [20171229.043805_builder_junos_161_r6_s1]
JUNOS mx libs [20171229.043805_builder_junos_161_r6_s1]
JUNOS Data Plane Crypto Support [20171229.043805_builder_junos_161_r6_s1]
JUNOS mtx Data Plane Crypto Support [20171229.043805_builder_junos_161_r6_s1]
JUNOS daemons [20171229.043805_builder_junos_161_r6_s1]
JUNOS mx daemons [20171229.043805_builder_junos_161_r6_s1]
JUNOS Voice Services Container package [20171229.043805_builder_junos_161_r6_s1]
JUNOS Services TLB Service PIC package [20171229.043805_builder_junos_161_r6_s1]
JUNOS Services SSL [20171229.043805_builder_junos_161_r6_s1]
JUNOS Services Stateful Firewall [20171229.043805_builder_junos_161_r6_s1]
JUNOS Services RPM [20171229.043805_builder_junos_161_r6_s1]
JUNOS Services PTSP Container package [20171229.043805_builder_junos_161_r6_s1]
JUNOS Services PCEF package [20171229.043805_builder_junos_161_r6_s1]
JUNOS Services NAT [20171229.043805_builder_junos_161_r6_s1]
JUNOS Services Mobile Subscriber Service Container package [20171229.043805_builder_junos_161_r6_s1]
JUNOS Services MobileNext Software package [20171229.043805_builder_junos_161_r6_s1]
JUNOS Services Logging Report Framework package [20171229.043805_builder_junos_161_r6_s1]
JUNOS Services LL-PDF Container package [20171229.043805_builder_junos_161_r6_s1]
JUNOS Services Jflow Container package [20171229.043805_builder_junos_161_r6_s1]
JUNOS Services Deep Packet Inspection package [20171229.043805_builder_junos_161_r6_s1]
JUNOS Services IPSec [20171229.043805_builder_junos_161_r6_s1]
JUNOS Services IDS [20171229.043805_builder_junos_161_r6_s1]
JUNOS IDP Services [20171229.043805_builder_junos_161_r6_s1]
JUNOS Services HTTP Content Management package [20171229.043805_builder_junos_161_r6_s1]
JUNOS Services Crypto [20171229.043805_builder_junos_161_r6_s1]
JUNOS Services Captive Portal and Content Delivery Container package [20171229.043805_builder_junos_161_r6_s1]
JUNOS Services COS [20171229.043805_builder_junos_161_r6_s1]
JUNOS Border Gateway Function package [20171229.043805_builder_junos_161_r6_s1]
JUNOS AppId Services [20171229.043805_builder_junos_161_r6_s1]
JUNOS Services Application Level Gateways [20171229.043805_builder_junos_161_r6_s1]
JUNOS Services AACL Container package [20171229.043805_builder_junos_161_r6_s1]
JUNOS SDN Software Suite [20171229.043805_builder_junos_161_r6_s1]
JUNOS Extension Toolkit [20171229.043805_builder_junos_161_r6_s1]
JUNOS Packet Forwarding Engine Support (wrlinux) [20171229.043805_builder_junos_161_r6_s1]
JUNOS Packet Forwarding Engine Support (MX/EX92XX Common) [20171229.043805_builder_junos_161_r6_s1]
JUNOS Packet Forwarding Engine Support (M/T Common) [20171229.043805_builder_junos_161_r6_s1]
JUNOS Packet Forwarding Engine Support (MX Common) [20171229.043805_builder_junos_161_r6_s1]
JUNOS Online Documentation [20171229.043805_builder_junos_161_r6_s1]
12. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

0 Recommend
rnayar
Posted 02-05-2018 04:23

Reply Reply Privately
Hi,

Thanks for the output. Please open new thread.

Share the configuration and also confirm if you've any subscriber at the time of commit.

Also share the output of "show chassis hardware"

Regards,

Rahul
13. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

0 Recommend
Erdem
Posted 02-05-2018 04:30

Reply Reply Privately
we have 2 online subscribers , after i commit no one disconnect and i check disconnect one of subsciber by

run clear network-access aaa subscriber username b@bnett

and the user reconnect successfuly and i checked also the speed of it and parameters that given by FreeRadius
14. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

0 Recommend
rnayar
Posted 02-05-2018 04:42

Reply Reply Privately
Hi,

Please read below document for HCOS

https://www.juniper.net/documentation/en_US/junos/topics/concept/hierarchical-scheduling-mic-mpc-understanding.html

MPC2E NG PQ & Flex Q doesn't support HCOS and it's a non-HCOS card.

To enable queueing on non-HQOS cards, use this command: set chassis fpc <slot#> flexible-queuing-mode.Note that committing "set chassis fpc X flexible-queuing-mode” configuration causes fpc X reboot.

Regards,
Rahul

Junos OS

Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

Erdem02-04-2018 04:34

rnayar02-04-2018 04:47

Erdem02-04-2018 05:00

rnayar02-04-2018 05:06Best Answer

Erdem02-04-2018 06:03

rnayar02-04-2018 06:30

Erdem02-05-2018 00:46

rnayar02-05-2018 01:47

Erdem02-05-2018 03:40

rnayar02-05-2018 03:51

Erdem02-05-2018 04:19

rnayar02-05-2018 04:23

Erdem02-05-2018 04:30

rnayar02-05-2018 04:42

1. Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

2. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

3. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

4. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4 Best Answer

5. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

6. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

7. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

8. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

9. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

10. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

11. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

12. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

13. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

14. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4

4. RE: Upgrade MX480 - 64 Bit from 15.1F7.3 to 15.1R6-S4
Best Answer