Aruba 48 Port 2930f VSF Stacking issue

[calmet101]

I have started building a stack of 4x 2930f switches, I have a member 1 as the master and have successfully joined member 2 and part of member 3. I am using the following ports as my VSF links:

Member 1 

port 1/47 link 1

port 1/48 link 2

member 2

port 1/47 link 2

port 1/48 link 1

Member 3

port 1/47 link 2

port 1/48 link 1

Member 4

port 1/47 link 2

port 1/48 link 1

Here is the show VSF command with the stating members and their priorities, all looks good I am sure.

FOR92SW2930F# show vsf

VSF Domain ID : 1

MAC Address : 040973-011dcb

VSF Topology : Chain

VSF Status : Active

Uptime : 69d 1h 32m

VSF MAD : None

VSF Port Speed : 1G

Software Version : WC.16.10.0003

Mbr

ID MAC Address Model Pri Status

--- ----------------- ------------------------------------- --- ---------------

1 040973-011dc0 Aruba JL557A 2930F-48G-740W-PoE+-4... 255 Commander

2 3821c7-30a500 Aruba JL262A 2930F-48G-PoE+-4SFP S... 220 Standby

3 3821c7-2ee880 Aruba JL262A 2930F-48G-PoE+-4SFP S... 210 Member

Here is the output of my show VSF topology before I join member 4

FOR92SW2930F# show vsf topology

VSF member's interconnection with links:

Stby Cmdr

+---+ +---+ +---+

| 3 |1==2| 2 |1==1| 1 |

+---+ +---+ +---+

My Issue is that when I enter in members 3  link 2 in port 3/47 I get this error message:

FOR92SW2930F(config)# vsf member 3 link 2 3/47

A previous port unreservation is still in progress. Please try again momentarily.

I have never seen this before and I have tried completely erasing member 3 from the stack and then wiping members 3 config using erase startup-config, I then rebooted member 3, I then consoled into member 3 after disconnecting from stack and issued the command erase all just to be sure everything is whipped.

So at this point member 3 is like brand new, so I then connected it back into the stack from member 2’s VSF link and joins successfully but the same thing happens when I try to configure member 3’s link 2 on port 3/47, I get the same message as before. It is like the switch is holding on to something that stops the VSF negotiation stopping me from joining member 4 on the port I would like. I can use another port such as 3/46 and seems to work but it’s not going by what we normally do for VSF stacking ports. Ports 47 and 48 is what I want to use.

I feel like I have tried everything apart from rebooting the master as it is a live switch with APs connected so I don't want to disrupt anyone connected to them.

Has anyone had this issue before and have resolved it without rebooting the master?

[DIYO]

Hello calmet101,

this is probably a SW issue, you need to reboot the stack or at least the commander (for example, through a “redundancy switchover” command). Unfortunately, there is no other way around .

Additionally, I would open a case at the HPE support for a possible fix.

Best regards