This post is more than 5 years old
8 Posts
0
2777
September 23rd, 2010 01:00
NS-480 LACP Errors
Hi,
I have a NS-480 here that I am trying to get LACP working on with a stacked pair of Dell PowerConnect 6248 switches.
I currently have two other LACP links on the Dell switches (for uplink and for another server on the switches). Using the same configuration on the PowerConnects as the other links for the NS-480 links (only using cge0/1 on both data movers) results in the LACP link not coming up at all with the following errors reported in the logs (from the Celerra):
Facility: DRIVERS
Description: LAP_Port::receive_LACP len=114 expected_len=110
This message is repeated over and over again, which I assume is why LACP is not working.
Has anyone got LACP working between EMC gear and a PowerConnect switch before? For troubleshooting purposes I also tried setting LACP up on a single switch (non stacked) incase that was causing any issues with no luck.
I had a look at the logs from the Dell switch but there doesn't appear to be anything meaningful in them.
Thanks
gbarretoxx1
366 Posts
0
September 24th, 2010 07:00
Hi,
Please, refer to emc247936.
" The Dell switch sends 128 byte LACP packets, with four extra bytes at the end. The Data Mover appears to have a check for the length of the packet and it fails if it does not match, regardless of its contents."
There are patches for 5.6.49 that contains an enhancement to support this switch.
Gustavo Barreto.
sebbyr
99 Posts
0
September 23rd, 2010 08:00
What is the status of your LACP connection on the NAS? You could get it by running the following:
server_sysconfig server_2 -v (this will list out your virtual devices)
server_sysconfig server_2 -v -i DEVICE_NAME (this will give you the status of the device, and if LACP is configured on it)
Thanks.
- Sebby Robles
udev
8 Posts
0
September 23rd, 2010 10:00
Hi Sebby,
The output is as follows:
Also, the relevant config on the switch is as follows:
Rainer_EMC
4 Operator
•
8.6K Posts
0
September 23rd, 2010 11:00
the difference of 4 bytes is a bit curious - do you have by any chance VLAN tagging configured on one side but not on the other?
Rainer
gbarretoxx1
366 Posts
0
September 23rd, 2010 14:00
Hi,
change this :
channel-group 48 mode auto
to :
channel-group 48 mode active
Gustavo Barreto.
Rainer_EMC
4 Operator
•
8.6K Posts
0
September 23rd, 2010 15:00
PAgP ?
gbarretoxx1
366 Posts
0
September 23rd, 2010 15:00
Hi Rainer,
No. This is for LACP. This needs to be set to "active" on the switch side.
##################################################################################################################################
channel-group
To assign and configure an EtherChannel interface to an EtherChannel group, use the channel-group command. Use the no form of this command to remove the channel-group configuration from the interface.
channel-group number mode {active | on | {auto [non-silent]} | {desirable [non-silent]} | passive}
no channel-group number
Syntax Description
number
Specifies the channel group number; see the "Usage Guidelines" section for valid values.
mode
EtherChannel mode of the interface.
active
Enables LACP unconditionally.
on
Enables EtherChannel only.
auto
Places a port into a passive negotiating state in which the port responds to PAgP packets it receives but does not initiate PAgP packet negotiation.
non-silent
(Optional) Used with the auto or desirable mode when traffic is expected from the other device.
desirable
Places a port into an active negotiating state in which the port initiates negotiations with other ports by sending PAgP packets.
passive
Enables LACP only if an LACP device is detected.
##################################################################################################################################
gbarretoxx1
366 Posts
0
September 23rd, 2010 15:00
Hi Rainer,
No. This is for LACP. This needs to be set to "active" on the switch side.
channel-group
To assign and configure an EtherChannel interface to an EtherChannel group, use the channel-group command. Use the no form of this command to remove the channel-group configuration from the interface.
channel-group number mode {active | on | {auto [non-silent]} | {desirable [non-silent]} | passive}
no channel-group number
Syntax Description
number
Specifies the channel group number; see the "Usage Guidelines" section for valid values.
mode
EtherChannel mode of the interface.
active
Enables LACP unconditionally.
on
Enables EtherChannel only.
auto
Places a port into a passive negotiating state in which the port responds to PAgP packets it receives but does not initiate PAgP packet negotiation.
non-silent
(Optional) Used with the auto or desirable mode when traffic is expected from the other device.
desirable
Places a port into an active negotiating state in which the port initiates negotiations with other ports by sending PAgP packets.
passive
Enables LACP only if an LACP device is detected.
udev
8 Posts
0
September 23rd, 2010 21:00
Hi Gustavo,
On the switches (Dell PowerConnect 6248's) we don't seem to have that option, as I think that is from the Cisco docs:
I had a look in the port-channel interface configuration and can't see any way there to make it active either, although on the interfaces I can see the BPDU's being sent/received.
Hi Rainer,
At the moment on both ends there is no VLAN tagging configured and as a test I removed the VLAN altogether on the switch (there is no VLAN setup on the EMC side of things) with the same results.
Please let me know if you would like any more information.
Rainer_EMC
4 Operator
•
8.6K Posts
0
September 24th, 2010 04:00
Hi Gustavo,
that's what I meant - since the Celerra doesn't speak PAgP (like another Cisco switch would) the ports of the switch need to specifically configured which aggregation protocol to use
Rainer
udev
8 Posts
0
September 24th, 2010 06:00
Hi Gustavo,
You may be on to something there... we are currently running with 5.6.49-3.
Thanks
gbarretoxx1
366 Posts
0
September 24th, 2010 06:00
Hi Rainer,
ok..understood.
Thanks,
gbarretoxx1
366 Posts
1
September 24th, 2010 06:00
Hi,
I just found one recent case with the same symptom.
The DART was changed to support Dell PowerConnect 6248's on newer codes.
What's your NAS code version ?
Gustavo Barreto.
udev
8 Posts
0
September 24th, 2010 07:00
Hi Gustavo,
Many thanks for that, I was sure I did a search on Powerlink earlier and it didn't return any results (searched "LAP_Port::receive_LACP"), thank you for digging that up.
Thanks