LACP Across 5632's

[Telair]

Having a bit of a problem getting LACP to work across two 5632's that are IST'ed together.  Running software v6.2.0.201 on both switches.  I have an HP blade chassis that needs two 10Gig links from our 5632's and uses LACP to bind them together.  But not having any luck getting the LACP group to form between the two 5632's.  Anyone know the process to get LACP working between the two units?  I can make an LACP group work across 8600's, but the 5632's must have a different process it seems.

[Dominik]

Besides the usual commands:

8600# config ethernet x/x lacp enable
8600# config ethernet x/x lacp key 1
8600# config ethernet x/x lacp aggregation true
8600# config lacp smlt-sys-id xx:xx:xx:xx:xx:xx
8600# config lacp enable

You have to insert a LACP key mapping.
I do this usually with the EDM in the section:
VLAN >> MLT/LACP >> LACP key mapping >> insert


Good Luck

[Telair]

Those commands do not work as stated on my 5632's?  So I did the same steps via EDM which seems to say it is running, but it won't let me map the LACP key to the single port SMLT ID.  I put in the LACP key I used (510 on both ports) and the SMLT ID from each port (500) and apply it.  It just kicks back an error "inconsistentValue".

Any more ideas?

[Michael McNamara]

The commands provided above by @Dominik were in the Passport CLI format, that's why they don't work.

Here's a quick example of how to setup a regular LACP trunk group on the "stackable" switches;


config t
interface fastEthernet 33-34
 lacp key 13
 lacp mode active
 lacp timeout-time short
 lacp aggregation enable
exit


Perhaps you could provide a diagram with relative port numbers?

Also, you'd need to identify these as SLT ports... how to-do that in the ERS 5632, not sure myself.

Have you reviewed the Avaya configuration guides?

[Dominik]

Arghh I am sorry for posting the wrong scipt.

Here is the right procedure from AVAYA  to get LACP running on a ERS5000 series switch (since SW 6.2 LACP over SMLT is supported)

LACP over SMLT configuration example
The following configuration example shows you how to configure LASP over SMLT.
The configuration is a triangle SMLT in which A and B are SMLT aggregation switches and
C is the edge switch. The MAC address for switch A is 00:aa:aa:aa:aa:00; for switch B,
00:bb:bb:bb:bb:00: and C, 00:cc:cc:cc:cc:00.


Prerequisites
• Ports 3 and 4 of switches A and B are SMLT ports.
• LACP is enabled on ports 1–4 of edge switch C, ports 3 and 4 of switch A, and ports 3 and 4 of switch B,
• The switches are all in Global Configuration mode.


Switch A configuration
Use the following procedure to configure switch A.

Procedure steps
1. Prevent loops by configuring the switch in advance mode:
lacp port-mode advance
2. Select switch A base MAC (00:aa:aa:aa:aa:00) as the system MAC and configure
the LAC system MAC for SMLT:
lacp smlt sys-id 00:aa:aa:aa:aa:00
3. Place switch A in interface mode:
interface fastethernet 3,4
4. Assign key 2 to ports 3 and 4
lacp key 2
5. Enable LACP on ports 3 and 4:
lacp mode active
6. Return switch A to Global Configuration mode:
exit
7. Bind MLT 30 to key 2. This command tells MLT application to reserve MLT 30 for
LACP key 2. Otherwise MLT will dynamically allocate an unused MLT # for LACP.
Populate SMLT ID to the reserved trunk to make it SMLT enabled.
lacp key 2 mlt 30 smlt 2
8. Enable MLT1 with ports 1 and 2.
mlt 1 en mem 1-2
9. Set MLT 1 as the IST trunk.
int mlt 1
10. Set the IST VLAN ID as 10 and the IST peer IP address as 10.30.20.101.
ist enable peer-ip 10.30.20.101 vlan 10
11. Return switch A to the Global Configuration mode:
exit


Switch B configuration
Use the following procedure to configure switch B.

Procedure steps
1. Prevent loops by configuring the switch in advance mode:
lacp port-mode advance
2. Select switch A base MAC (00:aa:aa:aa:aa:00) as the system MAC and configure
the LAC system MAC for SMLT:
lacp smlt sys-id 00:aa:aa:aa:aa:00
3. Place switch A in interface mode:
interface fastethernet 5
4. Assign key 2 to ports 3 and 4:
lacp key 2
5. Enable LACP on ports 3 and 4:
lacp mode active
6. Return switch B to the Global Configuration mode:
exit
7. Bind MLT 30 to key 2. This command instructs the MLT application to reserve MLT
30 for LACP key 2. Otherwise MLT will dynamically allocate an unused MLT number
for LACP. Populate SMLT ID to the reserved trunk to make it SMLT-enabled.
lacp key 2 mlt 30 smlt 2
8. Enable MLT1 with ports 1 and 2.
mlt 1 en mem 1-2
9. Set MLT 1 as the IST trunk.
int mlt 1
10. Set the IST VLAN ID as 10 and the IST peer IP address as 10.30.20.101.
ist enable peer-ip 10.30.20.100 vlan 10
11. Return switch B to the Global Configuration mode:
exit

Good Luck

[Telair]

OK. I'll have to try that on some switches in the lab.  In the mean time, we re-ran the fiber so each Virtual Connect module is connected to a stack of 5632's and not across IST links.  LACP comes up no problem then.

Thanks for the help.  I'll play with that in the lab a bit to figure it out before I go with that in the production network.

[Michael McNamara]

OK. I'll have to try that on some switches in the lab.  In the mean time, we re-ran the fiber so each Virtual Connect module is connected to a stack of 5632's and not across IST links.  LACP comes up no problem then.

Since you mentioned Virtual Connect... you are aware you can't form LACP connections across multiple Virtual Connect modules right? Your LACP connections most be from a single VC module.

Cheers!

[Telair]

Yes.  I found that out the hard way when we tried installing our first one a while back.  Took a few days of working on it before I sat down and read the manual.