It failed at 6:41 pm -- what brought it back up around ~7:40 pm -- the Cologix tech powering it on? Or cycling power?
Frank
-----Original Message-----
From: MICE Discuss [mailto:[log in to unmask]] On Behalf Of Doug McIntyre
Sent: Friday, July 24, 2015 10:53 PM
To: [log in to unmask]
Subject: Re: [MICE-DISCUSS] Multiple members reporting no light on the main switch
On Fri, Jul 24, 2015 at 08:10:24PM -0500, Jason Hanke wrote:
> Can someone log in and pull the alarms?
The alarm lit right now is just "boot from backup root".
The software upgrade should clear that.
This is the start of the logs around the time the 4500 rebooted tonight
Lots of info (pages and pages more), probably none too relevent to any issue.
Jul 24 18:38:15 MICE-SW1 ksyncd[1041]: ksyncd_select_control_plane_proto: rhost_sysctlbyname_get: No such file or directory
Jul 24 18:38:19 MICE-SW1 sfid[1022]: sfi_pfepeer_grace_timer expired
Jul 24 18:38:30 MICE-SW1 ksyncd[1041]: ksyncd_select_control_plane_proto: rhost_sysctlbyname_get: No such file or directory
Jul 24 18:38:45 MICE-SW1 ksyncd[1041]: ksyncd_select_control_plane_proto: rhost_sysctlbyname_get: No such file or directory
Jul 24 18:38:57 MICE-SW1 chassism[1021]: cm_ff_ifd_enable: fast failover enabled for internal-1/26
Jul 24 18:38:57 MICE-SW1 chassism[1021]: cm_ff_ifd_enable: fast failover enabled for internal-1/27
Jul 24 18:38:57 MICE-SW1 chassism[1021]: cm_ff_ifd_enable: fast failover enabled for internal-0/24
Jul 24 18:38:57 MICE-SW1 chassism[1021]: cm_ff_ifd_enable: fast failover enabled for internal-0/25
Jul 24 18:38:57 MICE-SW1 vccpd[1023]: VCCPD_PROTOCOL_ADJDOWN: Lost adjacency to a8d0.e5ba.37c0 on vcp-1.32768,
Jul 24 18:38:57 MICE-SW1 vccpd[1023]: ifl vcp-1.32768 set down, ifl flags 0, flags 0
Jul 24 18:38:57 MICE-SW1 vccpd[1023]: interface vcp-1 went down
Jul 24 18:38:57 MICE-SW1 vccpd[1023]: VCCPD_PROTOCOL_ADJDOWN: Lost adjacency to a8d0.e5ba.37c1 on vcp-0.32768,
Jul 24 18:38:57 MICE-SW1 vccpd[1023]: ifl vcp-0.32768 set down, ifl flags 0, flags 0
Jul 24 18:38:57 MICE-SW1 vccpd[1023]: interface vcp-0 went down
..
Probably getting up to the current recommended code base for this
hardware is the best course of action. (JunOS 12.3 has been working
very well for our Juniper EX switch stacks).
--
Doug McIntyre <[log in to unmask]>
~.~ ipHouse ~.~
Network Engineer/Provisioning/Jack of all Trades
