Wired Intelligent Edge

6300m VSF stack intermittent central alarms "stack member added/removed"

Very straight forward setup - nothing special. See further below for details.

Apparently since a firmware upgrade earlier this year we experience such alarms on two independent 2-member stacks.

It looks like the stacks are really falling apart for a short moment as some devices downstream randomly experience disconnection alarms. Which and how many device get announced as disconnected may depend on random individual polling situations it seems.

After some reading here I added OOBM links on both clusters to no avail.

I just updated both from 10.16.1020 to 10.18.0001 and wait for any effect.

Actually there was one cluster link failure on one of them previously and was shown and fixed by replacing an SFP module but in terms of the mentioned effects or else there was absolutelyno difference. The uplink is single port only but I did already consider to use lacp - may be that reduces effects when the stack is split (YMMV....:-)  )

show image
---------------------------------------------------------------------------
AOS-CX Primary Image
---------------------------------------------------------------------------
Version : FL.10.16.1020                 
Size    : 790 MB                        
Date    : 2025-12-16 21:06:53 UTC       
SHA-256 : 2b9d1bc2498368acebb4ab31d8b8cf4c5f92286115e7916e72d746bb3d2c7c08    

---------------------------------------------------------------------------
AOS-CX Secondary Image
---------------------------------------------------------------------------
Version : FL.10.18.0001                 
Size    : 805 MB                        
Date    : 2026-05-21 16:46:25 UTC       
SHA-256 : a546d6ad226915ee4a1f484e20c361aea4432112d0829a0588872da7dc926690    

Default Image : secondary                     
Boot Profile Timeout : 5 seconds

------------------------------------------------------
Management Module 1/1 (Active)
------------------------------------------------------
Active Image       : secondary                     
Service OS Version : FL.01.19.0001                 
BIOS Version       : FL.01.0004                    

h-dsl-dms-cc-sw10950# show vsf

Force Autojoin             : Disabled
Autojoin Eligibility Status: Not Eligible
MAC Address                : 
Egress Shape               : Enabled
Egress Shape Rate          : None
Secondary                  : 2
Topology                   : Ring
Status                     : No Split
Split Detection Method     : mgmt

Mbr Mac Address         type           Status   
ID
--- ------------------- -------------- ---------------
1   a8:52:d4:xxx   JL658A         Conductor
2   a8:52:d4:yyy   JL658A         Standby
h-dsl-dms-cc-sw10950# show vsf topology 
 Conductor    Standby      
 +-------+    +-------+   
 |   1   |1==1|   2   |
 +-------+    +-------+   
     2            2
     +============+

h-dsl-dms-cc-sw10950# show vsf         
detail          member          topology       
link            split-detection

h-dsl-dms-cc-sw10950# show vsf detail 
VSF Stack
        MAC Address                  : yyy
        Secondary                    : 2
        Topology                     : ring
        Egress Shape                 : Enabled
        Egress Shape Rate            : None
        Status                       : No Split
        Split Detection Method       : mgmt
        Software Version             : FL.10.18.0001
        Force Autojoin               : Disabled
        Autojoin Eligibility Status  : Not Eligible
        Autojoin Ineligibility Reason: Configuration changes detected
        Name                         : HPE-ANW-VSF-6300
        Contact                      :   
        Location                     :   

Member ID                            : 1
        MAC Address                  : xxxx
        Type                         : JL658A
        Model                        : 6300M 24-port SFP+ and 4-port SFP56 Switch
        Status                       : Conductor
        ROM Version                  : FL.01.19.0001
        Serial Number                : SG35LMP1JP
        Uptime                       : 3 days, 10 minutes
        CPU Utilization              : 9%
        Memory Utilization           : 17%
        VSF Link 1                   : Up, connected to peer member 2, link 1
        VSF Link 2                   : Up, connected to peer member 2, link 2

Member ID                            : 2
        MAC Address                  : xxx
        Type                         : JL658A
        Model                        : 6300M 24-port SFP+ and 4-port SFP56 Switch
        Status                       : Standby
        ROM Version                  : FL.01.19.0001
        Serial Number                : SG35LMP1JC
        Uptime                       : 3 days, 9 minutes
        CPU Utilization              : 33%
        Memory Utilization           : 17%
        VSF Link 1                   : Up, connected to peer member 1, link 1
        VSF Link 2                   : Up, connected to peer member 1, link 2

Any ideas or recommendations ? Similar experiences ?

regards,

Holger

It seems now after 9 days that on both stacks the misbehavior has been vanishing after the update to  FL.10.18.0001  .

But I have not found anything documented.

I will keep an eye for long and drop a line here and will be trusting the result after another week.

The timeout for non-occurrence can sometimes be quite long... :-)

7 views of this document - nobody looking here at all ?!

regards,

Holger

What are the links between stack members ? DAC or SFP+cords ?

I had a problem once, concerning "compatible" DACs that were not that compatible !

Check the interfaces stats (errors).

Thanks, the interfaces are all looking good.

In fact the stack members are pretty distributed across two DCs so DAC would not have worked anyway.

As it seems the problem may be gone now with the newer release.

Having two independent stacks showing the same problem we should really have seen it again by now.

It showed up at least once a week per stack.   Keeping fingers crossed ... :-)

After now 14 days I saw no more reoccurrences of the problem.

I am confident now the problem is gone after updating from  10.16.1020 to 10.18.0001.   I let you know otherwise.