The reboot of the vsf is normal when a link down is detected as in the case of link 1/1/52. Can you do a show interface 1/1/52? To check the link for physical errors.
If you can send us the crash it would be nice to see if there is any more information.
Also send if you can a show events -m and show events standby to see the vsf events, please. And the configuration about VSF, please.
The
---------------------------------
Daniel Ruiz
-----------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support.
Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC.
---------------------------------
Original Message:
Sent: Nov 09, 2024
From: ariyap
Subject: RE: Aruba 6300M VSF stack member rebooting
looks like this stack member lost its connection to the conductor and standby conductor.
Is your VSF stack in a a ring formation?
------------------------------
If my post was useful accept solution and/or give kudos.
Any opinions expressed here are solely my own and not necessarily that of HPE or Aruba.
------------------------------
Original Message:
Sent: Nov 07, 2024 11:53 PM
From: itwecomplete
Subject: Aruba 6300M VSF stack member rebooting
6300M JL661A and JL663A
Log:
2024-11-08T02:52:49.136239+00:00 BLC-6300M-1 crash-tools[4724]: Event|1206|LOG_INFO|||Module rebooted. Reason : Reboot of Member ID 2, Lost conductor and standby, Version: FL.10.14.1010#012, Boot-ID : ff97fbc5759e4ede893751a3265eaef1
2024-11-08T02:52:46.824937+00:00 BLC-6300M-1 vsfd[987]: Event|9901|LOG_INFO|CDTR|1|Member 2 boot complete
2024-11-08T02:52:42.637820+00:00 BLC-6300M-1 vsfd[987]: Event|9908|LOG_INFO|CDTR|1|Topology is Chain
2024-11-08T02:52:40.628825+00:00 BLC-6300M-1 vsfd[987]: Event|9923|LOG_INFO|CDTR|1|VSF link 1 is up
2024-11-08T02:52:38.967177+00:00 BLC-6300M-1 intfd[993]: Event|403|LOG_INFO|UKWN|1|Link status for interface 1/1/52 is up at 50 Gbps with RS-FEC
2024-11-08T02:52:02.828396+00:00 BLC-6300M-1 log-proxyd[1131]: Event|13001|LOG_INFO|CDTR|1|User admin logged in from 0.0.0.0 through CONSOLE session.
2024-11-08T02:50:41.128631+00:00 BLC-6300M-1 intfd[993]: Event|404|LOG_INFO|UKWN|1|Link status for interface 1/1/52 is down
2024-11-08T02:50:29.873890+00:00 BLC-6300M-1 vsflinkd[1138]: Event|9933|LOG_WARN|||Peer timeout on interface 1/1/52
2024-11-08T02:50:24.566895+00:00 BLC-6300M-1 intfd[993]: Event|403|LOG_INFO|UKWN|1|Link status for interface 1/1/52 is up at 50 Gbps with RS-FEC
2024-11-08T02:50:20.986734+00:00 BLC-6300M-1 intfd[993]: Event|404|LOG_INFO|UKWN|1|Link status for interface 2/1/52 is down - Line module not ready
2024-11-08T02:50:20.860014+00:00 BLC-6300M-1 vsfd[987]: Event|9924|LOG_INFO|CDTR|1|VSF link 1 is down
2024-11-08T02:50:20.859783+00:00 BLC-6300M-1 vsfd[987]: Event|9913|LOG_WARN|CDTR|1|Lost member 2 with Loss of communication
2024-11-08T02:50:20.859692+00:00 BLC-6300M-1 vsfd[987]: Event|9908|LOG_INFO|CDTR|1|Topology is Standalone
2024-11-08T02:50:20.781692+00:00 BLC-6300M-1 intfd[993]: Event|404|LOG_INFO|UKWN|1|Link status for interface 1/1/52 is down
Any idea why this would happen? The uptime is a week with only a few devices connected. No power outages at the time. I was sitting right beside the stack and heard member 2 reboot.
Thank you