Comware

I'm creating a new VSF Stack with 6200F - 8 in total (Ring topology). The Commander is on software version 10.13.1040. The other members are on 10.10.1070. When I add a new member to the stack it joins and then reboots as it should. It then starts updating itself to be on the same version as the conductor. Once it's updated, it does a final power cycle then reboots the stack and zeroises the conductor. I have tried 2 times and both times it does this. 

Does anyone know why it keeps rebooting and zeroising the stack? 

------------------------------
Steinar

Original Message:
Sent: Sep 10, 2024 03:05 AM
From: OneEvade
Subject: Zeroisation of VSF Stack after adding new memeber?

I'm creating a new VSF Stack with 6200F - 8 in total (Ring topology). The Commander is on software version 10.13.1040. The other members are on 10.10.1070. When I add a new member to the stack it joins and then reboots as it should. It then starts updating itself to be on the same version as the conductor. Once it's updated, it does a final power cycle then reboots the stack and zeroises the conductor. I have tried 2 times and both times it does this. 

Does anyone know why it keeps rebooting and zeroising the stack? 

And manual, like this:

Conf t
vsf member 1 [yes, it should be 1, until you hit renumber, for #2]
link 1 1/1/49 {yes, here too, like everything}
link 2 1/1/50 (this one too)
Exit
vsf renumber-to 2 (this then from 3; 4; 5; 6; 7; 8 )[all 7 pcs]

for 24 port:

link 1 1/1/25
link 2 1/1/26

Connect L2 to L1 starting at Sw1 [Commander], all the way (2 > 1 > 2 > 1...)

Sett member 2 as Standby, after join complete 

(this one you will have to look up yourself :))

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

Steinar

Original Message:
Sent: Sep 11, 2024 09:22 AM
From: Steinar Grande
Subject: Zeroisation of VSF Stack after adding new memeber?

------------------------------
Steinar

Original Message:
Sent: Sep 10, 2024 03:05 AM
From: OneEvade
Subject: Zeroisation of VSF Stack after adding new memeber?

I'm creating a new VSF Stack with 6200F - 8 in total (Ring topology). The Commander is on software version 10.13.1040. The other members are on 10.10.1070. When I add a new member to the stack it joins and then reboots as it should. It then starts updating itself to be on the same version as the conductor. Once it's updated, it does a final power cycle then reboots the stack and zeroises the conductor. I have tried 2 times and both times it does this. 

Does anyone know why it keeps rebooting and zeroising the stack? 

Hi, thanks for the reply ! When I first did the stack I was following the official guide.

I did Member 1 links ect ect and renumbered it. It is exactly like the example you provided. After renumbering it would reboot itself - Then it would reboot a second time and reboot the stack causing a Zeroistation of the stack.

Today I decided to load 10.13.1040 onto the remaining switches. NOT in the stack to see if it was a software issue. It was not :(

Contacted Aruba support and went through a different process of trying to use the TYPE Command:

'''
conf t
vsf member 6
type - JL782A 
'''

It unfortunately did the same thing. Once added to the stack, It will reboot itself then reboot the stack and zeroise it.

Any help is greatly appreciated! 

Many thanks 

And manual, like this:

Conf t
vsf member 1 [yes, it should be 1, until you hit renumber, for #2]
link 1 1/1/49 {yes, here too, like everything}
link 2 1/1/50 (this one too)
Exit
vsf renumber-to 2 (this then from 3; 4; 5; 6; 7; 8 )[all 7 pcs]

for 24 port:

link 1 1/1/25
link 2 1/1/26

Connect L2 to L1 starting at Sw1 [Commander], all the way (2 > 1 > 2 > 1...)

Sett member 2 as Standby, after join complete 

(this one you will have to look up yourself :))

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

Steinar

Original Message:
Sent: Sep 11, 2024 09:22 AM
From: Steinar Grande
Subject: Zeroisation of VSF Stack after adding new memeber?

------------------------------
Steinar

Original Message:
Sent: Sep 10, 2024 03:05 AM
From: OneEvade
Subject: Zeroisation of VSF Stack after adding new memeber?

I'm creating a new VSF Stack with 6200F - 8 in total (Ring topology). The Commander is on software version 10.13.1040. The other members are on 10.10.1070. When I add a new member to the stack it joins and then reboots as it should. It then starts updating itself to be on the same version as the conductor. Once it's updated, it does a final power cycle then reboots the stack and zeroises the conductor. I have tried 2 times and both times it does this. 

Does anyone know why it keeps rebooting and zeroising the stack? 

Hi, I think the error is in your sequence.

You wrote: >> You set up VSF-Ports on member 1 and then renumbered the master.

The master should be and stay member 1. The others only need to renumber.

But please check, that you removed all member Information from the stack so there should be only one single switch (no vsf). And this should be your master switch (also run the no vsf command). Then the Switch should reboot and the ports should be named only 1/1/1 ... 1/1/xx.

Then copy the complete config to another factory resettet Switch (1 of the other 7 in your stack). Try to build a stack without the current "master" switch. so only a stack of 7. If this works, maybe the first switch has a broken nvram or something else.

If this build of 7 works you could just swap the two switches (new master vs. old master), then "erase zeroize" the old master and try to join as a member.

BTW: Don't forget to set a secondary/standby conductor !!!. This could also cause the problems with reboot and not working stacks as probably the master needs to re-write ist database for a 8 member stack and has no backup-switch (Standby) to write the database to.

Happy troubleshooting

Greetings Franz

------------------------------
prefers to not experiment with live customer equipment...

Original Message:
Sent: Sep 11, 2024 11:05 AM
From: John Walsham
Subject: Zeroisation of VSF Stack after adding new memeber?

Hi, thanks for the reply ! When I first did the stack I was following the official guide.

I did Member 1 links ect ect and renumbered it. It is exactly like the example you provided. After renumbering it would reboot itself - Then it would reboot a second time and reboot the stack causing a Zeroistation of the stack.

Today I decided to load 10.13.1040 onto the remaining switches. NOT in the stack to see if it was a software issue. It was not :(

Contacted Aruba support and went through a different process of trying to use the TYPE Command:

'''
conf t
vsf member 6
type - JL782A 
'''

It unfortunately did the same thing. Once added to the stack, It will reboot itself then reboot the stack and zeroise it.

Any help is greatly appreciated! 

Many thanks 

Original Message:
Sent: Sep 11, 2024 09:37 AM
From: Steinar Grande
Subject: Zeroisation of VSF Stack after adding new memeber?

And manual, like this:

Conf t
vsf member 1 [yes, it should be 1, until you hit renumber, for #2]
link 1 1/1/49 {yes, here too, like everything}
link 2 1/1/50 (this one too)
Exit
vsf renumber-to 2 (this then from 3; 4; 5; 6; 7; 8 )[all 7 pcs]

for 24 port:

link 1 1/1/25
link 2 1/1/26

Connect L2 to L1 starting at Sw1 [Commander], all the way (2 > 1 > 2 > 1...)

Sett member 2 as Standby, after join complete 

(this one you will have to look up yourself :))

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

Steinar

Original Message:
Sent: Sep 11, 2024 09:22 AM
From: Steinar Grande
Subject: Zeroisation of VSF Stack after adding new memeber?

------------------------------
Steinar

Original Message:
Sent: Sep 10, 2024 03:05 AM
From: OneEvade
Subject: Zeroisation of VSF Stack after adding new memeber?

I'm creating a new VSF Stack with 6200F - 8 in total (Ring topology). The Commander is on software version 10.13.1040. The other members are on 10.10.1070. When I add a new member to the stack it joins and then reboots as it should. It then starts updating itself to be on the same version as the conductor. Once it's updated, it does a final power cycle then reboots the stack and zeroises the conductor. I have tried 2 times and both times it does this. 

Does anyone know why it keeps rebooting and zeroising the stack?