Wired Intelligent Edge (Campus Switching and Routing)

Reply
MVP Expert

ArubaOS-CX 10.02/10.03: anybody tried static (non LACP) VSX LAG against VMware vSphere host?

Hi all,

 

I'm interested in learning opinions/pro/cons about using static (so non LACP) VSX LAG (available since ArubaOS-CX 10.02 and also on latest ArubaOS-CX 10.03) against VMware vSphere host's bonded ports (the vSphere host I'm referring to will use VSS Virtual Standard Switch - not VDS Virtual Distributed Switch - so usage of IEEE 803.3ad LACP is not possible and we need to rely on static Non-Protocol Ports Aggregation).

 

Thanks for sharing, Davide.

Regular Contributor I

Re: ArubaOS-CX 10.03: anybody tried static (non LACP) VSX LAG against VMware vSphere host?

When the vmware switches are running in switch independent mode, i would not built in any "ïntelligence" into the network, vmware load-balances per vm on the connected interfaces will do the trick in that cases.

 

If 1 VM would require more bandwith then 1 interface can offer, then i would implement LACP on vmware (MC-LAG on the core).



- - - - Aruba ACCX #748, ACDX #758, ACMP, ACEAP | HPE Master ASE - - - -
- - - - - - - Feel free to give kudos or accept as a solution! - - - - - - - - -
MVP Expert

Re: ArubaOS-CX 10.03: anybody tried static (non LACP) VSX LAG against VMware vSphere host?

Hi, thank you for answering...that's basically true...but:

 

(1) the balancing is valid for traffic leaving the ESXi host (considering the physical ports connected to the considered vSwitch configured in Active/Active mode)...what happen to incoming traffic to ESXi host on that very same vSwitch if no aggregation (neither LACP nor Static) is deployed?

 

(2) LACP is supported only on vNetwork with VDS Virtual Distributed Switch...which we can't actually implement (we haven't the supporting licensing for implementing VDS so we work only with VSS Virtual Standard Switch which doesn't support LACP but only static port aggregation without any protocol).

 

I'm worried to understand if there are pro/cons in using static port trunking on VSS to VSX (with VSX LAG static as per AOS-CX 10.02/10.03) instead of simply using two active/active ports on VSS to VSX.

 

Thanks!

Regular Contributor I

Re: ArubaOS-CX 10.03: anybody tried static (non LACP) VSX LAG against VMware vSphere host?

(1) For vmware load balanced, the incoming traffic wil be received on the same port for that particular vm. So always per-vm load balancing.

 

(2) I'm not sure what type of load balancing mechanism is used when using static port aggregation, does it even load balance accros more then 1 interface, or is active-standby?

 

The vmware load-balancing is pretty solid, but load-balancing on per-vm basis is not the most effective way IMO.



- - - - Aruba ACCX #748, ACDX #758, ACMP, ACEAP | HPE Master ASE - - - -
- - - - - - - Feel free to give kudos or accept as a solution! - - - - - - - - -
MVP Expert

Re: ArubaOS-CX 10.03: anybody tried static (non LACP) VSX LAG against VMware vSphere host?

Hi!

 

(1) OK...still I don't understand if a Static LAG (so in a scenario, as you said, with some "intelligence" on Host's physical network ports side and on the peer Switch side) is better or worst than leaving the vSphere Host's physical network ports in Active/Active and letting the vSwitch to balance egress traffic (generated by VM) to physical network...is using Static LAG overcomplicating the scenario (considering that we have VSX as peer) or not?

 

(2) As far as I understood Static LAG member ports are, once aggregated, all partecipating but, with regards to Static LAG versus LACP LAP, the difference is that Static LAG has no control protocol to manage member ports status and relationship with peer's LACP LAG (so this explain the term "Non Protocol" used by HP/HPE)...this main difference means less control-related features (like no Failover, no Hot-Standby port, no canditate aggregable port configuration verification...illuminating blog articles here and here)...the interesting point is that Static LAG versus LACP LAG doesn't necessarily mean that load balancing algorithms are different in favour of LACP LAG (they are, indeed, the same)...it's just that vSphere requires specifically to use "Route based on IP Hash" with Static LAG (so operating on VSS)...which basically means using the well known "src-dst IP" load balancing algorithm (as it often happens using LACP LAG).

MVP Expert

Re: ArubaOS-CX 10.03: anybody tried static (non LACP) VSX LAG against VMware vSphere host?

for me avoid static LAG (and also LACP LAG) with VMware ESXi (or only for very specific use case...)



PowerArubaSW: Powershell Module to use Aruba Switch API for Vlan, VlanPorts, LACP, LLDP... More info

PowerArubaCP: Powershell Module to use ClearPass API (create NAD, Guest...) More info

PowerArubaCX: Powershell Module to use ArubaCX API (get interface/vlan/ports info)

PowerArubaIAP: Powershell Module to use Aruba Instant AP

PowerArubaMC: Powershell Module to use Mobility Controller / Master


ACMP 6.4 / ACMX #107 / ACCP 6.5 / ACSP
MVP Expert

Re: ArubaOS-CX 10.03: anybody tried static (non LACP) VSX LAG against VMware vSphere host?

Hi Alexis, thanks! probably I'll step down(or not?) on multichassis static (VSX LAG Static) until I understand how to check if my setup is working or not...I tried yesterday with a 2 10Gbps ports member of a multichassis static (1 port on each VSX Member) against a ESXi 6.7 U3 set with 2 10 Gbps ports in Load Balancing (Route Based on IP Hash)...but, despite all involved ports are up, apparently ArubaOS-CX doesn't provide any feedback via the show lacp interface multi-chassis command I'm used to: I see the lag30(mc) line (local/remote) - lag 30 is my ststic one - totally empty (is this expected because it is not an usual LACP one?)...so, at first, I was a little bit in doubt about what I've set...show events on both peers reports that involved interfaces are up and lag30 is formed...also ESXi seems good on that. Today I'll check it better, I was too much in a hurry yesterday.
MVP Expert

Re: ArubaOS-CX 10.03: anybody tried static (non LACP) VSX LAG against VMware vSphere host?

The more I dive deeply into VSX Static LAG the more this configuration become interesting from the management standpoint...below my findings about VSX diagnostic done against my configured lag30 and its member interfaces 1/1/33.

 

ArubaOS-CX GUI reports the VSX (Multi-Chassis) Static LAG lag30 as Up (both interfaces are Up on both nodes):

 

ESXi host reported Up state for involved NICs' ports:

ESXi01_s1p2_and_s3p2_connected_to_VSX.png

 

 

ESXi vSwitch2 used to test VSX Static LAG (lag30):

 

Properties

Network label			DF Backend (1)
VLAN ID				None (0)

Security

Promiscuous mode		Reject
MAC address changes 		Accept
Forged transmits		Accept

Traffic shaping

Average bandwidth		--
Peak bandwidth			--
Burst size			--

Teaming and failover

Load balancing			Route based on IP hash

INFO: In the IP hash load balancing policy all physical switch ports connected to the active uplinks must be in link aggregation mode.
INFO: IP hash load balancing should be set for all port groups using the same set of uplinks.

Network failure detection	Link status only
Notify switches			Yes
Failback			Yes
Active adapters			vmnic1, vmnic7
Standby adapters		--
Unused adapters			--

And visually:ESXi01_vSwitch2_connected_to_VSX.png

Aruba 8320 VSX Primary VSX Static LAG (lag30) status:

VSX_Static_LAG_lag30_Aruba_8320-1_Primary_01.png

VSX_Static_LAG_lag30_Aruba_8320-1_Primary_02.png

 

Aruba 8320 VSX Secondary VSX Static LAG (lag30) status:VSX_Static_LAG_lag30_Aruba_8320-2_Secondary_01.png

VSX_Static_LAG_lag30_Aruba_8320-2_Secondary_02.png

 

Now the CLI part:

 

=== Aruba 8320 Node 1 (Primary) VSX Static LAG configuration ===

interface lag 30 multi-chassis static
    vsx-sync vlans
    description 8320-1-VSX-LAG-Static-lag30-ESXi01
    no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed 1,20,30,40
    loop-protect
    loop-protect vlan 1,20,30,40

interface 1/1/33 
    description Leg_to_s1p2_ESXi01_vmnic1_vSwitch2
    no shutdown
    mtu 9198
    flow-control rx
    lag 30

=== Aruba 8320 Node 2 (Secondary) VSX Static LAG configuration ===
interface lag 30 multi-chassis static
    vsx-sync vlans
    description 8320-2-VSX-LAG-Static-lag30-ESXi01
    no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed 1,20,30,40
    loop-protect
    loop-protect vlan 1,20,30,40

interface 1/1/33 
    description Leg_to_s3p2_ESXi01_vmnic7_vSwitch2
    no shutdown
    mtu 9198
    flow-control rx
    lag 30

=== Aruba 8320 VSX Static LAG (lag30) diagnostic on Primary and Secondary ===
Aruba-8320-1# show lacp aggregates

Aggregate name   : lag30 (multi-chassis)             
Interfaces       : 1/1/33                            
Peer interfaces  : 1/1/33                            
Heartbeat rate   : N/A                               
Hash             : l3-src-dst                        
Aggregate mode   : Off

Aruba-8320-1# show lacp aggregates vsx-peer

Aggregate name   : lag30 (multi-chassis)             
Interfaces       : 1/1/33                            
Peer interfaces  : 1/1/33                            
Heartbeat rate   : N/A                               
Hash             : l3-src-dst                        
Aggregate mode   : Off

Aruba-8320-1# show vsx lacp aggregates lag30   
                    Local-peer                        Remote-peer
-------------------------------------------------------------------------------

Aggregate name   : lag30 (multi-chassis)             lag30 (multi-chassis)
Interfaces       : 1/1/33                            1/1/33 
Peer interfaces  : 1/1/33                            1/1/33 
Heartbeat rate   : N/A                               N/A
Hash             : l3-src-dst                        l3-src-dst
Aggregate mode   : Off                               Off

Aruba-8320-2# show vsx lacp aggregates lag30
                    Local-peer                        Remote-peer
-------------------------------------------------------------------------------

Aggregate name   : lag30 (multi-chassis)             lag30 (multi-chassis)
Interfaces       : 1/1/33                            1/1/33 
Peer interfaces  : 1/1/33                            1/1/33 
Heartbeat rate   : N/A                               N/A
Hash             : l3-src-dst                        l3-src-dst
Aggregate mode   : Off                               Off

Aruba-8320-1# show lacp interfaces

State abbreviations :
A - Active        P - Passive      F - Aggregable I - Individual
S - Short-timeout L - Long-timeout N - InSync     O - OutofSync
C - Collecting    D - Distributing 
X - State m/c expired              E - Default neighbor state

Actor details of all interfaces:
------------------------------------------------------------------------------
Intf    Aggr       Port  Port  State   System-ID         System Aggr Forwarding
        Name       Id    Pri                             Pri    Key  State     
------------------------------------------------------------------------------
1/1/33  lag30(mc)                                                    up        

Partner details of all interfaces:
------------------------------------------------------------------------------
Intf    Aggr       Port  Port  State   System-ID         System Aggr           
        Name       Id    Pri                             Pri    Key            
------------------------------------------------------------------------------
1/1/33  lag30(mc)                                                              

Aruba-8320-1# show lacp interfaces vsx-peer 

State abbreviations :
A - Active        P - Passive      F - Aggregable I - Individual
S - Short-timeout L - Long-timeout N - InSync     O - OutofSync
C - Collecting    D - Distributing 
X - State m/c expired              E - Default neighbor state

Actor details of all interfaces:
------------------------------------------------------------------------------
Intf    Aggr       Port  Port  State   System-ID         System Aggr Forwarding
        Name       Id    Pri                             Pri    Key  State     
------------------------------------------------------------------------------
1/1/33  lag30(mc)                                                    up        

Partner details of all interfaces:
------------------------------------------------------------------------------
Intf    Aggr       Port  Port  State   System-ID         System Aggr           
        Name       Id    Pri                             Pri    Key            
------------------------------------------------------------------------------
1/1/33  lag30(mc)                                                              

And configuration related events generated during lag30 setup yesterday (Errors on VSX Secondary should be probably related to the fact I was saving VSX Primary before lag30 was configured on VSX Secondary):

 

=== Aruba 8320 Node 1 (Primary) VSX Static LAG events related to 1/1/33 and lag30 configuration ===

2019-09-24:16:43:17.115485|hpe-rdiscd|3910|LOG_INFO|AMM|-|Interface: 1/1/33 is deleted from router discovery
2019-09-24:16:47:17.218517|hpe-rdiscd|3910|LOG_INFO|AMM|-|Interface: 1/1/34 is deleted from router discovery
2019-09-24:17:03:11.653192|hpe-config|6801|LOG_INFO|AMM|-|Copying configs from: running-config to: startup-config
2019-09-24:17:10:02.902801|hpe-config|6801|LOG_INFO|AMM|-|Copying configs from: running-config to: startup-config
2019-09-24:17:16:59.661158|lacpd|1303|LOG_INFO|AMM|-|Interface 1/1/33 added to LAG 30. Existing configuration on interface 1/1/33 will be removed.
2019-09-24:17:16:59.696098|ops-switchd|4803|LOG_INFO|AMM|-|All dynamic MAC addresses on port 1/1/33 were flushed
2019-09-24:17:16:59.699173|ops-switchd|1401|LOG_DEBUG|AMM|-|Trunk set succeeds unit 0 lag_id 4
2019-09-24:17:16:59.699216|ops-switchd|1301|LOG_INFO|AMM|-|Dynamic LAG lag30 created
2019-09-24:17:16:59.699255|ops-switchd|1409|LOG_INFO|AMM|-|LAG lag30, set to load balance mode to l3-src-dst-hash
2019-09-24:17:16:59.701674|ops-switchd|1404|LOG_DEBUG|AMM|-|Trunk member add port succeeds on unit 0 hw_port 33 tid 4
2019-09-24:17:17:35.273114|hpe-vsxd|7014|LOG_INFO|AMM|-|VSX 30 state local down, remote down
2019-09-24:17:17:44.802017|hpe-config|6801|LOG_INFO|AMM|-|Copying configs from: running-config to: startup-config
2019-09-24:17:29:02.232570|pmd|3804|LOG_INFO|AMM|-|Transceiver hot-swap insert for interface 1/1/33
2019-09-24:17:33:40.949961|hpe-vsxd|7014|LOG_INFO|AMM|-|VSX 30 state local down, remote down
2019-09-24:17:33:41.026283|hpe-vsxd|7012|LOG_INFO|AMM|-|VSX 30 state local down, remote up
2019-09-24:17:34:25.107870|lldpd|110|LOG_INFO|AMM|-|Configured LLDP reinit-delay to 2
2019-09-24:17:34:25.124641|intfd|403|LOG_INFO|AMM|-|Link status for interface 1/1/33 is up
2019-09-24:17:34:25.152520|hpe-vsxd|7013|LOG_INFO|AMM|-|VSX 30 state local up, remote up
2019-09-24:17:34:25.156592|hpe-vsxd|7013|LOG_INFO|AMM|-|VSX 30 state local up, remote up
2019-09-24:17:34:33.320050|lldpd|104|LOG_INFO|AMM|-|LLDP neighbor f8:f2:1e:59:e7:91 added on 1/1/33

=== Aruba 8320 Node 2 (Secondary) VSX Static LAG events related to 1/1/33 and lag30 configuration ===

2019-09-24:16:50:15.097019|hpe-rdiscd|3910|LOG_INFO|AMM|-|Interface: 1/1/33 is deleted from router discovery
2019-09-24:17:03:00.228386|hpe-config|6801|LOG_INFO|AMM|-|Copying configs from: running-config to: startup-config
2019-09-24:17:03:16.174430|vsx-syncd|7603|LOG_INFO|AMM|-|Configuration-persistence : configuration saved to startup-configuration on primary VSX device.
2019-09-24:17:03:16.580494|hpe-config|6801|LOG_INFO|AMM|-|Copying configs from: running-config to: startup-config
2019-09-24:17:03:23.817133|vsx-syncd|7603|LOG_INFO|AMM|-|Configuration-persistence : configuration saved to startup-configuration on secondary VSX device.
2019-09-24:17:07:00.282175|hpe-rdiscd|3910|LOG_INFO|AMM|-|Interface: 1/1/34 is deleted from router discovery
2019-09-24:17:09:52.080474|hpe-config|6801|LOG_INFO|AMM|-|Copying configs from: running-config to: startup-config
2019-09-24:17:10:07.285763|vsx-syncd|7603|LOG_INFO|AMM|-|Configuration-persistence : configuration saved to startup-configuration on primary VSX device.
2019-09-24:17:10:07.683633|hpe-config|6801|LOG_INFO|AMM|-|Copying configs from: running-config to: startup-config
2019-09-24:17:10:14.894096|vsx-syncd|7603|LOG_INFO|AMM|-|Configuration-persistence : configuration saved to startup-configuration on secondary VSX device.
2019-09-24:17:16:39.026350|vsx-syncd|7602|LOG_INFO|AMM|-|Configuration sync update : Missing Reference Error: Could not find Port lag30 on secondary VSX database.
2019-09-24:17:16:39.218306|vsx-syncd|7601|LOG_ERR|AMM|-|Configuration sync error : Missing reference in database while syncing configuration. Use "show running-config vsx-sync peer-diff" to help identify the missing reference.
2019-09-24:17:16:43.328284|vsx-syncd|7602|LOG_INFO|AMM|-|Configuration sync update : Missing Reference Error: Could not find Port lag30 on secondary VSX database.
2019-09-24:17:16:43.527611|vsx-syncd|7601|LOG_ERR|AMM|-|Configuration sync error : Missing reference in database while syncing configuration. Use "show running-config vsx-sync peer-diff" to help identify the missing reference.
2019-09-24:17:16:47.196342|vsx-syncd|7602|LOG_INFO|AMM|-|Configuration sync update : Missing Reference Error: Could not find Port lag30 on secondary VSX database.
2019-09-24:17:16:47.507171|vsx-syncd|7601|LOG_ERR|AMM|-|Configuration sync error : Missing reference in database while syncing configuration. Use "show running-config vsx-sync peer-diff" to help identify the missing reference.
2019-09-24:17:17:03.590207|vsx-syncd|7601|LOG_ERR|AMM|-|Configuration sync error : Missing reference in database while syncing configuration. Use "show running-config vsx-sync peer-diff" to help identify the missing reference.
2019-09-24:17:17:19.850505|hpe-vsxd|7014|LOG_INFO|AMM|-|VSX 30 state local down, remote down
2019-09-24:17:17:22.585726|vsx-syncd|7602|LOG_INFO|AMM|-|Configuration sync update : VSX configuration-sync updated database
2019-09-24:17:17:35.231058|lacpd|1303|LOG_INFO|AMM|-|Interface 1/1/33 added to LAG 30. Existing configuration on interface 1/1/33 will be removed.
2019-09-24:17:17:35.327042|ops-switchd|4803|LOG_INFO|AMM|-|All dynamic MAC addresses on port 1/1/33 were flushed
2019-09-24:17:17:35.332017|ops-switchd|1401|LOG_DEBUG|AMM|-|Trunk set succeeds unit 0 lag_id 6
2019-09-24:17:17:35.332083|ops-switchd|1301|LOG_INFO|AMM|-|Dynamic LAG lag30 created
2019-09-24:17:17:35.332150|ops-switchd|1409|LOG_INFO|AMM|-|LAG lag30, set to load balance mode to l3-src-dst-hash
2019-09-24:17:17:35.335095|ops-switchd|1404|LOG_DEBUG|AMM|-|Trunk member add port succeeds on unit 0 hw_port 33 tid 6
2019-09-24:17:17:40.764550|hpe-config|6801|LOG_INFO|AMM|-|Copying configs from: running-config to: startup-config
2019-09-24:17:17:56.876722|vsx-syncd|7603|LOG_INFO|AMM|-|Configuration-persistence : configuration saved to startup-configuration on secondary VSX device.
2019-09-24:17:29:22.147653|pmd|3804|LOG_INFO|AMM|-|Transceiver hot-swap insert for interface 1/1/33
2019-09-24:17:33:40.963502|lldpd|110|LOG_INFO|AMM|-|Configured LLDP reinit-delay to 2
2019-09-24:17:33:40.979534|intfd|403|LOG_INFO|AMM|-|Link status for interface 1/1/33 is up
2019-09-24:17:33:41.020537|hpe-vsxd|7011|LOG_INFO|AMM|-|VSX 30 state local up, remote down
2019-09-24:17:33:41.029885|hpe-vsxd|7011|LOG_INFO|AMM|-|VSX 30 state local up, remote down
2019-09-24:17:33:49.295089|lldpd|104|LOG_INFO|AMM|-|LLDP neighbor e4:43:4b:7a:f9:12 added on 1/1/33
2019-09-24:17:34:25.163042|hpe-vsxd|7013|LOG_INFO|AMM|-|VSX 30 state local up, remote up

So...in the end...the setup I've done looks correct from a pure configuration standpoint, at least looking at what Aruba nodes' GUIs report...BUT the usual command show lacp interface multi-chassis apparently fails to report lag30(mc) status correctly.

 

At this point my main question is:

 

Provided that one want to deploy a VSX Static LAG because no LAG LACP is supported by downlinked peer (here the ESXi)...is there on ArubaOS-CX 10.2/10.3 an equivalent to the well known ArubaOS-Switch's show trunks in order to diagnose the VSX Static LAG status since the show lacp interface multi-chassis (exactly because is heavily LACP biased?) seems to refuse to report anything about a Multi-Chassis Static LAG? or...Am I missing some other documented alternative about how to diagnose a VSX Static LAG? forgot to specify I'm on ArubaOS-CX 10.02.0031...not yet on 10.03.

MVP Expert

Re: ArubaOS-CX 10.03: anybody tried static (non LACP) VSX LAG against VMware vSphere host?

With a Static VSX LAG (lag30(mc) and lag31(mc) in my scenario), it looks like the output of show lacp interfaces multi-chassis (redacted below to show only lag30(mc) and lag31(mc)) is inferior (in terms of information provided) if compared to the output of the command show lacp interfaces (redacted below to show only lag30(mc) and lag31(mc)) typically used in case of non-VSX LAGs!

 

Documentation:

Displaying_Static_non-VSX_LAG.png

 

..so, at this point, it looks like that using a command born to display non-VSX Static LAGs' status is the only (and best) way we can use to understand if a Static VSX LAG is (or is not) in Forwarding State (See above the "Up" on the last column).

 

Info reported by the command one think it should not be the most appropriate:

 

Aruba-8320-1# show lacp interfaces 

State abbreviations :
A - Active        P - Passive      F - Aggregable I - Individual
S - Short-timeout L - Long-timeout N - InSync     O - OutofSync
C - Collecting    D - Distributing 
X - State m/c expired              E - Default neighbor state

Actor details of all interfaces:
------------------------------------------------------------------------------
Intf    Aggr       Port  Port  State   System-ID         System Aggr Forwarding
        Name       Id    Pri                             Pri    Key  State     
------------------------------------------------------------------------------
1/1/33  lag30(mc)                                                    up        
1/1/34  lag31(mc)                                                    up        

Partner details of all interfaces:
------------------------------------------------------------------------------
Intf    Aggr       Port  Port  State   System-ID         System Aggr           
        Name       Id    Pri                             Pri    Key            
------------------------------------------------------------------------------
1/1/33  lag30(mc)                                                              
1/1/34  lag31(mc)                                                              

Versus no info provided by the command one think it should be the most appropriate:

 

Aruba-8320-1# show lacp interfaces multi-chassis 

State abbreviations :
A - Active        P - Passive      F - Aggregable I - Individual
S - Short-timeout L - Long-timeout N - InSync     O - OutofSync
C - Collecting    D - Distributing 
X - State m/c expired              E - Default neighbor state

Actor details of all interfaces:
------------------------------------------------------------------------------
Intf    Aggregate  Port    Port     State   System-ID         System   Aggr    
        name       id      Priority                           Priority Key     
------------------------------------------------------------------------------
1/1/33  lag30(mc)                                                              
1/1/34  lag31(mc)                                                              


Partner details of all interfaces:
------------------------------------------------------------------------------
Intf    Aggregate  Partner Port     State   System-ID         System   Aggr    
        name       Port-id Priority                           Priority Key     
------------------------------------------------------------------------------
1/1/33  lag30(mc)                                                              
1/1/34  lag31(mc)                                                              


Remote Actor details of all interfaces:
------------------------------------------------------------------------------
Intf   Aggregate  Port    Port     State   System-ID         System   Aggr    
       name       id      Priority                           Priority Key     
------------------------------------------------------------------------------
1/1/33 lag30(mc)                                                              
1/1/34 lag31(mc)                                                              


Remote Partner details of all interfaces:
------------------------------------------------------------------------------
Intf   Aggregate  Partner Port     State   System-ID         System   Aggr    
       name       Port-id Priority                           Priority Key     
------------------------------------------------------------------------------
1/1/33 lag30(mc)                                                              
1/1/34 lag31(mc)

I think it's crystal clear at this point that this CLI approach is very counter-intuitive because - primarily - Static LAGs can be implemented as VSX LAGs other than as non-VSX LAGs...so the proper command to check their status - having lag(mc) in our VSX scenario - must be the show lacp interfaces multi-chassis...and not the show lacp interfaces command.

 

In any case those show lacp based commands are (and were, since very beginning), IMHO, all way too counter-inutitive for the task (the grammar used is counter-intuitive[*]).

 

Why? because:

 

  • To check a non-VSX LAGs status (Static or LACP, it doesn't matter) a user should use a command such show lag [<lag-interface-id>|<all>] eventually with options.
  • To check a VSX LAG status (Static or LACP, it doesn't matter) a user should use a command such show vsx lag [<lag-interface-id>|<all>] eventually with options.
  • The differentiating factor is (and always have been) - at least in a ArubaOS-CX driven environment - only the fact that a LAG could be implemented as a non-VSX LAG or that it could be implemented as a VSX LAG (clearly is reasonable considering a VSX scenario) and not that a LAG is consequently using Static (Non Control Protocol) or LACP.

[*] Simply consider that the show lacp interfaces command actually - at minimum - shows:

 

  • VSX LACP LAGs = VSX LAGs using LACP
  • VSX Static LAGs = VSX LAGs not using LACP
  • non-VSX LACP LAGs = indeed LACP LAG used for VSX ISL is listed

Sorry for being so long...I started this thread requesting an opinion about VSX Static LAG coupling with vSphere VSS Port Aggregation...and ended opinioning about ArubaOS-CX grammar and some of its counter-intuitive commands...but this was simply discovered along the way...and I just pick up the challenge.

 

I think a similar strange behaviour should be checked (and, if possible, addressed) by Product Development...personally I found that the ArubaOS-CX CLI is too raw on specific areas...in other terms IMHO there is room for improvements.

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: