Unsolved

1 Rookie

 • 

9 Posts

2160

December 14th, 2020 09:00

S6000-ON LACP issues

Hello,

I have one stack of S6000-ON switches and one stack of S6010-ON which experience the same issues.
I have multiple LACP port channels active, and on the S6000-ON stack there is one host experiencing issues where the host cannot be reached by other hosts on the same stack, except when I shut down the Fo 2/26 interface (when I shut the Fo 1/26 interface it is still broken).

On the S6010-ON stack this was even worse, that why we have migrated all the hosts to the S6000-ON to get a replacement for the S6010-ON.

When I destroy the Port channel the host is on and configure the interfaces as "separate" interfaces on the switch, everything works perfectly.

We have tried swapping the cables for new, swapping the cables from Fo 1/26 to Fo 2/26 and vice versa, updating the NIC firmware on the host, used other interfaces in the same port channel (Fo 1/28 and Fo 2/28), nothing helps. Only when I shutdown one specific interface of the port channel, everything starts working.

We have tried creating a static LAG as well, and that didn't help either.

We see no port errors or discards.

I don't understand it anymore.
The S6000-ON stack is running firmware 9.14(2.7)
The S6010-ON stack is running firmware 9.14(2.8)

As mentioned before, the S6010-ON stack has had issues with creating a LACP Port channel to an S6000 (non ON) stack as well, and with a LACP port channel to the S6000-ON stack as well. Now we have migrated everything towards the S6000-ON the problems have become less, but now it's only one host experiencing issues and only with the port channel interface (each host has 4 interfaces to the stack, 2 of the 4 interfaces are in a port channel).

Any ideas? Anyone else has seen this behaviour before? It looks like the Port channel just stops accepting/forwarding traffic when I enable a second interface in the port channel.

Moderator

 • 

9.6K Posts

 • 

42.2K Points

December 14th, 2020 13:00

Hi bladman87,

Are there any spanning-tree errors? How many ports are in your port channel? What happens if you stop using 1/26 and 2/26 in the port channel?

1 Rookie

 • 

9 Posts

December 14th, 2020 14:00

Also there is no difference in behavior when setup as a static LAG instead of a dynamic (LACP) LAG.

Also configuring it with a different port channel ID doesn’t help.

1 Rookie

 • 

9 Posts

December 14th, 2020 14:00

Hi Josh,

Yes, all ports show as up, that also applies to the port channels. An show interfaces port-channel brief report all port channels as up.

 

1 Rookie

 • 

9 Posts

December 14th, 2020 14:00

Hi Josh,

There is no spanning tree active on the storage network (as it’s supposed to be).

There are 2 interfaces in the port channel: 1/26 and 2/26. We have tried adding 1/28 and 2/28 and that doesn’t change or resolve the issue.

As mentioned, we have had similar issues on the S6010-ON stack, but then across multiple hosts. 

Also we have found that some hosts cán communicate with the affected host on the affected address. Also we have found that it doesn’t affect all IP addresses on the host (it has multiple addresses on the same port channel, in the same VLAN and IP segment).

Moderator

 • 

9.6K Posts

 • 

42.2K Points

December 14th, 2020 14:00

Does “show int port brief” show all of the ports as up? You may want to turn of fast switchover. Page 331 https://dell.to/37kTbDg

 

Moderator

 • 

9.6K Posts

 • 

42.2K Points

December 14th, 2020 15:00

Can you run a show tech-support and upload the log to https://dell.to/3oOT8Fu and private message me the service tag?

1 Rookie

 • 

9 Posts

December 15th, 2020 14:00

Hi Josh,

I have uploaded the file and have sent you a private message, can you confirm?

Kind regards

6 Operator

 • 

2.9K Posts

December 15th, 2020 14:00

Hello,

 

Josh is out today, but it looks like he should be back in tomorrow. We don't have access to each other's PMs, so if you'd like to send me a copy of the PM, I can use that to help make sure the log information is available.

1 Rookie

 • 

9 Posts

December 16th, 2020 00:00

@Dell-DylanJ I have just sent you a PM.

Thanks in advance!

Moderator

 • 

9.6K Posts

 • 

42.2K Points

December 16th, 2020 09:00

Dec 14 16:39:30 %STKUNIT1-M:CP %LLDP-3-MAC_PHY_CFG: Configuration mismatch with neighbor on interface Fo 1/26

Dec 14 16:39:30 %STKUNIT1-M:CP %LLDP-3-MAC_PHY_CFG: Configuration mismatch with neighbor on interface Fo 1/25

Dec 14 16:39:30 %STKUNIT1-M:CP %LLDP-3-MAC_PHY_CFG: Configuration mismatch with neighbor on interface Fo 2/26

Dec 14 16:39:30 %STKUNIT1-M:CP %LLDP-3-MAC_PHY_CFG: Configuration mismatch with neighbor on interface Fo 2/25

 

It seems to think the the configuration on the ports doesn’t match. What kind of storage is it attached to?

1 Rookie

 • 

9 Posts

December 17th, 2020 10:00

Hi Josh, I have seen this error and is caused by LLDP discovery used by Storpool to identify the ports where the server is connected to. This is only for troubleshooting purposes and when LLDP is disabled then the error doesn't appear anymore. I think it is because they ask for more information than we have enabled on the switches. On the old S6000 (non-ON) which doesn't have the issues we see the same in the logging but port channels work perfectly. The old S6000 runs firmware 9.7.0.0P4.

1 Rookie

 • 

9 Posts

January 4th, 2021 06:00

Hi Josh, I didn't receive any response back. It's reproducible on the S6000-ON ánd the S6010-ON series.

Moderator

 • 

9.6K Posts

 • 

42.2K Points

January 4th, 2021 09:00

What type of storage is it connected to?

1 Rookie

 • 

9 Posts

January 4th, 2021 09:00

Storpool storage, which is software defined storage. But we have the issues on the switch LACP interconnects as well.

Moderator

 • 

9.6K Posts

 • 

42.2K Points

January 4th, 2021 10:00

I think at this point the best option is to call phone support and have an escalation created.

No Events found!

Top