I'm struggling to understand why I obtain two different Distributing/Non-Distributing states for the very same interface of a VSX LAG (lag 10 on our VSX) when I execute two CLI commands that should apparently provide a common result (with regard to the above mentioned states):
First, please consider the output of show lacp interface multi-chassis for the interface 1/1/19 only member of the 2 ports VSX LAG named lag 10...note that Partner (the local VSX Member, primary node, where I'm logged in) and Remote Partner details (the remote VSX Peer, secondary node) show different results ALFNCD versus only ALFNC:
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/19 lag10(mc) 19 1 ALFNCD d0:67:26:XX:XX:XX 65534 10
Partner details of all interfaces:
------------------------------------------------------------------------------
Intf Aggregate Partner Port State System-ID System Aggr
name Port-id Priority Priority Key
------------------------------------------------------------------------------
1/1/19 lag10(mc) 1 128 ALFNCD 00:14:5e:99:54:8c 32768 48879
Remote Actor details of all interfaces:
------------------------------------------------------------------------------
Intf Aggregate Port Port State System-ID System Aggr
name id Priority Priority Key
------------------------------------------------------------------------------
1/1/19 lag10(mc) 1019 1 ALFNCD d0:67:26:XX:XX:XX 65534 10
Remote Partner details of all interfaces:
------------------------------------------------------------------------------
Intf Aggregate Partner Port State System-ID System Aggr
name Port-id Priority Priority Key
------------------------------------------------------------------------------
1/1/19 lag10(mc) 2 128 ALFNC 00:14:5e:99:54:8c 32768 48879 Watching the output above it looks like 1/1/19 on Remote Partner, a Server, is not Distributing...conversely...if I drill down to discover if that difference is found also with commands show lacp interfaces multi-chassis 1/1/19 and show lacp interfaces multi-chassis 1/1/19 vsx-peer I immediately found instead that:
Aruba-8320-1# show lacp interfaces multi-chassis 1/1/19
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
Aggregate-name : lag10(multi-chassis)
-------------------------------------------------
Actor Partner
-------------------------------------------------
Port-id | 19 | 1
Port-priority | 1 | 128
Key | 10 | 48879
State | ALFNCD | ALFNCD
System-ID | d0:67:26:XX:XX:XX | 00:14:5e:99:54:8c
System-priority | 65534 | 32768
Aruba-8320-1# show lacp interfaces multi-chassis 1/1/19 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
Aggregate-name : lag10(multi-chassis)
-------------------------------------------------
Actor Partner
-------------------------------------------------
Port-id | 1019 | 2
Port-priority | 1 | 128
Key | 10 | 48879
State | ALFNCD | ALFNCD
System-ID | d0:67:26:XX:XX:XX | 00:14:5e:99:54:8c
System-priority | 65534 | 32768there is no difference - both partner interfaces look Distributing "D" - for Partner port-id 1 (connected to 1/1/19 on local VSX I'm logged in) and for Partner port-id 2 (connected to 1/1/19 on remote VSX Peer).
What is the reason for such VSX LAG status difference? Am I misunderstanding those concurrent outputs?