Header Only - DO NOT REMOVE - Extreme Networks

Link aggregation Summit X690 Vs Enterasys N-Series


Userlevel 2
Hello i am making a Link agregation : summit X690 Vs Enterasys N7.
Configuration of Summit:

configure sharing 1:1 add ports 1:1,1:2[/code]Configuration Enterasys N-7

set port vlan ge.3.24-25;lag.0.62 1 modify-egress
set vlan egress 2-100 lag.0.62;ge.3.23-24;ge.5.23-24 tagged
set lacp aadminkey lag.0.62 62
set port lacp port ge.3.24 aadminkey 62
set port lacp port ge.3.25 aadminkey 62
set lacp singleportlag enable
set lacp enable
set port lacp port ge.3.24-25 enable

When i do a :
show port status lag.0.62

Port Alias Oper Admin Speed Duplex Type
(truncated) Status Status (bps)
------------ ---------------- -------- ------- ------ ------- ------------------
lag.0.62 down up lag
1 of 1 ports displayed, 0 port(s) with oper status 'up' or 'dormant'.

XXXXXX(su)->show lacp lag.0.62
Global Link Aggregation state: enabled
Single Port LAGs: enabled

Aggregator: lag.0.62
Actor Partner
System Identifier: 00:1f:45:d4:0f:5a 00:00:00:00:00:00
System Priority: 32768 32768
Admin Key: 62
Oper Key: 62 32768
Attached Ports: None.
Standby Ports: None.

I not see atacched ports in the link aggregation What could be happening? Missing Command?

13 replies

Userlevel 4
Hi Elena,

Maybe you can use the following command on EXOS just to check if you haven't created a STATIC LAG on the Purple side, while an LACP LAG on the Red side:

show sharing[/code]
Maybe adding the lacp parameter should help...

configure sharing 1:1 add ports 1:1,1:2 lacp[/code]
Best regards,
-Leo
Userlevel 2
Thanks Leo, with lacp command at the end not work, I think that the problem is in the Enterasys configuration. Not in the summit. What do you think?
Userlevel 4
Please try with following command on x690:

enable sharing 1:1 grouping 1:1-2 lacp

In the meanwhile, are you using x690 switches as stacking? When looking at the port name 1:1 of x690 switch, it is the name of ports when using stacking.
Userlevel 7
Hi Elena,

perhaps one line of the N-Series configuration is not correct?

set vlan egress 2-100 lag.0.62;ge.3.23-24;ge.5.23-24 tagged

All other lines use ports ge.3.24-25, but the above line uses ge.3.23-24.

Using your EOS commands on an SSA (different port numbers, of course) and adding the lacp keyword to the EXOS commands, I could configure an LAG between an X460-G2 and an SSA.

Did you enable the ports on the N-Series (and the EXOS switch as well)? What output results from the command show port status ge.3.24-25;lag.0.62 on the N7? If I disable the physical ports comprising the LAG on the SSA, the show lacp lag.0.62 output shows Attached Ports: None.

We could probably help better, if you could provide the output of the following commands:
  1. (N7) show port status ge.3.24-25;lag.0.62
  2. (N7) show port lacp port ge.3.24-25 status detail
  3. (N7) show lacp lag.0.62
  4. (X690) show port status 1:1-2 no-refresh
  5. (X690) show sharing
  6. (X690) show lacp lag 1:1 # I am not sure if the LAG group-id is 1 or 1:1
Thanks,
Erik
Userlevel 4
Erik Auerswald wrote:

Hi Elena,

perhaps one line of the N-Series configuration is not correct?

set vlan egress 2-100 lag.0.62;ge.3.23-24;ge.5.23-24 tagged

All other lines use ports ge.3.24-25, but the above line uses ge.3.23-24.

Using your EOS commands on an SSA (different port numbers, of course) and adding the lacp keyword to the EXOS commands, I could configure an LAG between an X460-G2 and an SSA.

Did you enable the ports on the N-Series (and the EXOS switch as well)? What output results from the command show port status ge.3.24-25;lag.0.62 on the N7? If I disable the physical ports comprising the LAG on the SSA, the show lacp lag.0.62 output shows Attached Ports: None.

We could probably help better, if you could provide the output of the following commands:
  1. (N7) show port status ge.3.24-25;lag.0.62
  2. (N7) show port lacp port ge.3.24-25 status detail
  3. (N7) show lacp lag.0.62
  4. (X690) show port status 1:1-2 no-refresh
  5. (X690) show sharing
  6. (X690) show lacp lag 1:1 # I am not sure if the LAG group-id is 1 or 1:1
Thanks,
Erik

Lag group-id is "1:1" in this case.
Userlevel 7
Erik Auerswald wrote:

Hi Elena,

perhaps one line of the N-Series configuration is not correct?

set vlan egress 2-100 lag.0.62;ge.3.23-24;ge.5.23-24 tagged

All other lines use ports ge.3.24-25, but the above line uses ge.3.23-24.

Using your EOS commands on an SSA (different port numbers, of course) and adding the lacp keyword to the EXOS commands, I could configure an LAG between an X460-G2 and an SSA.

Did you enable the ports on the N-Series (and the EXOS switch as well)? What output results from the command show port status ge.3.24-25;lag.0.62 on the N7? If I disable the physical ports comprising the LAG on the SSA, the show lacp lag.0.62 output shows Attached Ports: None.

We could probably help better, if you could provide the output of the following commands:
  1. (N7) show port status ge.3.24-25;lag.0.62
  2. (N7) show port lacp port ge.3.24-25 status detail
  3. (N7) show lacp lag.0.62
  4. (X690) show port status 1:1-2 no-refresh
  5. (X690) show sharing
  6. (X690) show lacp lag 1:1 # I am not sure if the LAG group-id is 1 or 1:1
Thanks,
Erik

Thanks. 🙂
Userlevel 2
Hello I have only one port attached for the test this is the output commands

================== N7 COMMANDS=================
VITSCOA1(su)->show port status ge.3.24-25;lag.0.62

Port Alias Oper Admin Speed Duplex Type
(truncated) Status Status (bps)
------------ ---------------- -------- ------- ------ ------- ------------------
ge.3.24 LAG up up 1.0G full 1000-t rj45
ge.3.25 LAG down up 100.0M full 100-tx rj45
lag.0.62 LAG down up lag
3 of 3 ports displayed, 1 port(s) with oper status 'up' or 'dormant'.

VITSCOA1(su)->show port lacp port ge.3.24-25 status detail

Global Link Aggregation state : enabled

Port Instance: ge.3.24 Port enable state: Enabled
ActorPort: 600 PartnerAdminPort: 600
ActorSystemPriority: 32768 PartnerOperPort: 600
ActorPortPriority: 32768 PartnerAdminSystemPriority: 32768
ActorAdminKey: 62 PartnerOperSystemPriority: 32768
ActorOperKey: 62 PartnerAdminPortPriority: 32768
ActorAdminState: -----GlA PartnerOperPortPriority: 32768
ActorOperState: -F---GlA PartnerAdminKey: 600
ActorSystemID: 00-1f-45-d4-0f-5a PartnerOperKey: 600
SelectedAggID: none PartnerAdminState: --DCS-lp
AttachedAggID: none PartnerOperState: --DCS-lp
MuxState: Detached PartnerAdminSystemID: 00-00-00-00-00-00
DebugRxState: Defaulted PartnerOperSystemID: 00-00-00-00-00-00
portStandbyReason: none

Port Instance: ge.3.25 Port enable state: Enabled
ActorPort: 601 PartnerAdminPort: 601
ActorSystemPriority: 32768 PartnerOperPort: 601
ActorPortPriority: 32768 PartnerAdminSystemPriority: 32768
ActorAdminKey: 62 PartnerOperSystemPriority: 32768
ActorOperKey: 62 PartnerAdminPortPriority: 32768
ActorAdminState: -----GlA PartnerOperPortPriority: 32768
ActorOperState: -F----lA PartnerAdminKey: 601
ActorSystemID: 00-1f-45-d4-0f-5a PartnerOperKey: 601
SelectedAggID: none PartnerAdminState: --DCS-lp
AttachedAggID: none PartnerOperState: --DC--lp
MuxState: Detached PartnerAdminSystemID: 00-00-00-00-00-00
DebugRxState: port Disabled PartnerOperSystemID: 00-00-00-00-00-00
portStandbyReason: none

VITSCOA1(su)->show lacp lag.0.62
Global Link Aggregation state: enabled
Single Port LAGs: enabled

Aggregator: lag.0.62
Actor Partner
System Identifier: 00:1f:45:d4:0f:5a 00:11:88:19:0d:79
System Priority: 32768 32768
Admin Key: 62
Oper Key: 62 32768
Attached Ports: None.
Standby Ports: None.

========================== SUMMIT X690 ==================

* (Software Update Required) Slot-1 VITSC0A3.9 # show ports 3:47-48 no-refresh

Port Summary
Port Display VLAN Name Port Link Speed Duplex
# String (or # VLANs) State State Actual Actual
========================================================================
3:47 (0028) E A 1000 FULL
3:48 (0028) E R
========================================================================
Port State: D-Disabled, E-Enabled, F-Disabled by link-flap detection,
L-Disabled due to licensing
Link State: A-Active, R-Ready, NP-Port not present, L-Loopback,
D-ELSM enabled but not up
d-Ethernet OAM enabled but not up

* (Software Update Required) Slot-1 VITSC0A3.10 # show sharing
Load Sharing Monitor
Config Current Agg Min Ld Share Dist Ld Share Agg Link Link Up
Master Master Control Active Algorithm Flags Group Mbr State Transitions
================================================================================
3:47 LACP 1 L2 A 3:47 - A 8
L2 3:48 - R 0
================================================================================
Link State: A-Active, D-Disabled, R-Ready, NP-Port not present, L-Loopback
Minimum Active: (<) Group is down. # active links less than configured minimum
Load Sharing Algorithm: (L2) Layer 2 address based, (L3) Layer 3 address based
(L3_L4) Layer 3 address and Layer 4 port based
(custom) User-selected address-based configuration
Custom Algorithm Configuration: ipv4 L3-and-L4, xor
Distribution Flags:
A - All: Distribute to all members,
L - Local Slot: Distribute to members local to ingress slot,
P - Port Lists: Distribute to per-slot configurable subset of members,
R - Resilient Hashing enabled.
Number of load sharing trunks: 1

* (Software Update Required) Slot-1 VITSC0A3.11 # show lacp lag 3:47

Lag Actor Actor Partner Partner Partner Agg Actor
Sys-Pri Key MAC Sys-Pri Key Count MAC
--------------------------------------------------------------------------------
3:47 0 0x0be7 00:1f:45:d4:0f:5a 32768 0x003e 0 02:04:96:9d:6e:6c

Port list:

Member Port Rx Sel Mux Actor Partner
Port Priority State Logic State Flags Port
--------------------------------------------------------------------------------
3:47 0 Current Selected Attached A-GS---- 600
3:48 0 Idle Unselected Detached -------- 0
================================================================================
Actor Flags: A-Activity, T-Timeout, G-Aggregation, S-Synchronization
C-Collecting, D-Distributing, F-Defaulted, E-Expired

========================================

I just test the summit making a LACP vs a Enterasys C2 and works !!!. Only fail Vs Enterasys N7!!
Userlevel 2
Please Help!!!
Userlevel 7
Elena Madrigal wrote:

Please Help!!!

If this is urgent, please contact GTAC directly.
Userlevel 7
Hi Elena,

it is interesting that the configuration works with a C2 (tested by you) and an S-Series (tested by me, with an X460-G2), but not with the N7.

The show port lacp port ge.3.24-25 status detail output contains unexpected results, but I cannot interpret them completely. The N7 seems to report LACP communication with the X690, but seems to wrongly interpret this as if the links are not supposed to be active, perhaps because it does not see or accept the system ID of the X690 (DebugRxState: Defaulted PartnerOperSystemID: 00-00-00-00-00-00).

Please note that the X690 asks for a software upgrade (* (Software Update Required) Slot-1 VITSC0A3.9 😵. Please consider upgrading the X690 to the latest patch level of the recommended EXOS release.

I concur with Drew that you should consider opening a GTAC case.

Thanks,
Erik
Userlevel 7
Hi Elena,

I have just tested the LAG configuration with an X460-G2 with EXOS 22.2.1.5-patch1-5 and an N1 with firmware 07.63.01.0006, and it works fine.

I currently suspect the non-production-ready X690 firmware to not set the LACP System ID and the N7 to not accept the all zero LACP System ID it sees. You could try to verify this by attaching a packet sniffer (e.g. a PC with Wireshark) to the X690 (or a mirror port on a switch connected to the X690, see How To Configure a Port Mirror on an EOS Modular Switch or How To Enable And Configure Mirroring In EXOS) and looking at the captured LACP PDUs.

A software update on the X690 and a new test with the configuration that works with a C2 with the N7 is probably easier and might actually solve the problem.

BTW, does the output of the command show port lacp port status detail on the C2 show an all zero operational LACP System ID as well?

Thanks,
Erik
Userlevel 2
Thanks erik, we found the issue and the problem is solved now, making the LAG as a static in the enterasys N7 works fine!!. Dinamic not work. Only work with a static config.
However with C2 works as dinamic and static config. I dont know the reason.
Thanks all people for the support.
Userlevel 7
Hello Elena,

it is great to read that the problem is solved by using a static LAG as workaround. Thanks for letting us know!

Please consider that a static LAG configuration can be dangerous, since any cabling changes regarding one of the switches participation in the static LAG may result in cabling errors that might result in a loop. Dynamic LAGs using LACP prevent a loop from forming by not activating the wrongly cabled links. Thus I always recommend to use LACP for LAGs.

Thanks,
Erik

Reply