Wired Intelligent Edge

last person joined: 18 hours ago 

Bring performance and reliability to your network with the HPE Aruba Networking Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of your switching devices, and find ways to improve security across your network to bring together a mobile-first solution
Back to discussions
Expand all | Collapse all

VSF Standby rebooting

This thread has been viewed 1 times

  • 1.  VSF Standby rebooting

    Posted Oct 30, 2019 12:29 PM
      |   view attached

    Dears,

     

    I have configured two 5406 as core with VSF

    Member 1 

    Priority: 128

     

    Member 2

    Priority: 128

     

    11 IDFs are there, all are connected to both core switches with proper trunk configuration and all are working fine.

     

    Now the problem is that, once we shutdown the VSF commander,  the stabdby also rebooting. Is it a normal behaviour? if not how to fix the issue?

     

     

     



  • 2.  RE: VSF Standby rebooting

    Posted Oct 30, 2019 01:46 PM
    Did you check the logs of the 2nd switch?


  • 3.  RE: VSF Standby rebooting

    MVP GURU
    Posted Oct 30, 2019 07:54 PM
    Hi!

    Using the same priority value for both VSF Members is not a best practice...that said would be interesting to have a look at sanitized running configuration (and some diagnostic show commands related to vsf status and MAD, if any MAD was setup)...also what do you mean with "once we shutdown the VSF Commander"? AFAIK you can't "shutdown" the Commander...at worst you simply can power-off it or, at best, force a failover...not a shutdown.


  • 4.  RE: VSF Standby rebooting

    Posted Oct 31, 2019 12:20 AM
      |   view attached

    HI parnassus,

     

     

     

     

     

     

    Attachment(s)

    txt
    CORE.txt   7 KB 1 version


  • 5.  RE: VSF Standby rebooting

    MVP GURU
    Posted Nov 02, 2019 09:53 PM

    Hi, sorry for delay in answering...

     

    I don't understand if reported MAC Addresses are real or were modified ad-hoc...by the way...the the one with lower value (mac-address 548028-800000) appears to belong to VSF Member with id 2...since both VSF Members own the very same priority value (left for both at default 128) I suspect that the VSF Member 2 owned the VSF Commander role when you powered off it [*] (you can check that by using the show vsf and show vsf detail CLI commands)...in that case if the Commander switch (id 2) was powered off then the Standby switch (id 1) should have taken over as the new Commander for the entire stack (the VSF Fragment contaning the Standby should indeed remain active)...and that should have happened without causing any Standby member reboot...so, to answer your question, no...it is not normal that powering down the Commander member the Standby reboots.

     

    In any case a MAD (for VSF Split scenarios mitigation) should be setup and verified. Are you using OoBM interfaces to perform that or what?

     

    [*] bur you never said us WHAT VSF Member id had the switch you powered off (you simply wrote us you powered off the Commander...).