Aruba VSF change status standby to member

[H_BO]

Hi,
i've got two 2930F in a vsf shown as below:

 VSF member's interconnection with links:

 Stby     Cmdr
 +---+    +---+
 | 2 |1==1| 1 |
 +---+    +---+

Is it possible to Change Stby to a full VSF member? I want to use LACP trunks with both switches as failover function.

Detail overview:

 VSF Domain ID    : 11
 MAC Address      : 9cdc71-39e7cb
 VSF Topology     : Chain
 VSF Status       : Active
 Uptime           : 285d 16h 11m
 VSF MAD          : None
 VSF Port Speed   : 10G
 Software Version : WC.16.05.0003

Name             : core01
Contact          : Technik
Location         :


Member ID        : 1
MAC Address      : 9cdc71-39e7c0
Type             : JL254A
Model            : Aruba JL254A 2930F-48G-4SFP+ Switch
Priority         : 128
Status           : Commander
ROM Version      : WC.16.01.0004
Serial Number    : Confidential Info Erased
Uptime           : 285d 16h 11m
CPU Utilization  : 0%
Memory - Total   : 345,879,040 bytes
Free             : 225,035,072 bytes
VSF Links -
#1 : Active, Peer member 2
#2 : Inactive



Member ID        : 2
MAC Address      : 9cdc71-919480
Type             : JL254A
Model            : Aruba JL254A 2930F-48G-4SFP+ Switch
Priority         : 100
Status           : Standby
ROM Version      : WC.16.01.0004
Serial Number    : Confidential Info Erased
Uptime           : 285d 16h 0m
CPU Utilization  : 0%
Memory - Total   : 345,879,040 bytes
Free             : 241,850,228 bytes
VSF Links -
#1 : Active, Peer member 1
#2 : Inactive

Thanks.

[HP-Browniee]

Hello

You can use LACP with the standby and the commander. Your stack is correct.

Standby just means that it will become the new commander when the current commander fails. 

[parnassus]

In VSF terms, Standby is just a VSF Member possible role status (Commander, Standby, Member) and, especially in a two VSF Member scenario, a well formed VSF has a Standby member and a Commnader member.

VSF Standby member is - basically - already a (full) VSF Member.

As written by @HP-Browniee you can (or, better, you should...for resiliency) setup a LACP uplink against both VSF Members since you're doing that against a single logical Switch that is the entire VSF from a Switch/Server without any particular issue (in other terms: one leg of LACP Aggregated Trunk goes to VSF Member 1, the other leg goes to VSF Member 2).

[raj567]

Hi ,

I am going to do VSF between Two core  2930F switches .I am going to do with 2 DAC Cables.So 2 ports in commander and 2 ports in standby will go for DAC Cables.

Remaining 2 ports  in first 2930F switch and 2 ports in second 2930F switch will be there as free.

I am going to connect 4 uplinks coming from 4 different Locations in those 4 free ports which are in  two core switches.

will this Topology works.please suggest for configuration and implementation Plan.

Rajesh

[parnassus]

Please open a new thread here.

If you're dealing with a VSF made of two Switches and if your VSF is going to act as a distribution/core layer for the rest of your network topology then your access layer (placed in your four "locations") should be uplinked to this VSF by using Port Trunking (Links Aggregations with at least two member interfaces per Port Trunk) with LACP as link aggregation control protocol...so each "dual homed" access switch/host will be concurrently physically connected to both VSF Members to enhance connection resiliency and throughput between access layer and core/distribution layer...otherwise why using VSF if you then have single link downlinks to your access layer from VSF?