I have 2 Dell Force10 MXL10 / 40 switches that form a VLT domain. From each of these 2 Dell Force 10 switches, one port-channel configured in vlt peer-lag mode comes out and these two ports arrive on a Catalyst 4500 forming a single Port-channel on Catalyst.
I created 1 more port-channel on each of the Dell Force10, to arrive with a single port-channel, now on a Catalyst 3750. When activating the port-channel between Force10 and Catalyst 3750 the port-channel is UP, but the Port-channel interfaces between the Dell Force10 and Catalyst 4500 are in "err-disable" status on the Catalyst 4500 side.
When I disable Port-channel between Force10 and Catalyst 3750, and apply the shutdown and no shutdown command on the Catalyst 4500 interfaces that connect to Force10, the Port-channel between Force10 and Catalyst 4500 is up again.
The catalyst 3750 I added to the scenario is completely isolated from the network so there are no loop conditions.
Attached current topology and the topology that generates the problem.
Solved! Go to Solution.
this has been posted to the wireless forum, might be better suited in the Network Architecture forum
You are right. In the outline of the topology I submitted, the log Po6 corresponds to the topology Po10. Excuse me for the mistake in the drawing.
Your UDLD suspicion is fully valid, I searched some sites and really this feature is not supported by Dell Force 10.
The UDLD configuration is configured globally on Catalyst 4500. I will keep the global configuration and schedule a maintenance window to disable UDLD for Catalyst 4500 interfaces that connects with Dell Force 10.
The only point that is still unclear is this, because Catalyst 4500 interfaces (Te2 / 9 and Te2 / 10) that connect to the Dell Force 10 go err-disable only when Port-channel 15 and Catalyst are enabled. the Dell Force 10?
I reinforce that the Catalyst 3750 is completely isolated from the network, so there is no scenario for loop condition.
I am awaiting release for a new maintenance window and trying to apply the scenario again.
This time I will disable the UDL feature of Catalyst 4500 and 3750 interfaces that connect with Dell Force 10. I hope the err-disable status will stop with this action.
Once you apply the settings I'll be back here to give feedback if it worked or not.
Thank you very much.
Just to give feedback, I tested by turning off the UDLD feature on the Cisco Catalyst 4500 switches and also on the 3750.
When port-channel 15 was raised between the DELL switch and Catalyst 3750, Po 15 was UP and no err-disable status occurred on the physical interfaces of the Po that connects with Catalyst 4500, so the UDLD feature was what it was. triggering the problem that knocked Po out between Catalyst 4500 and DELL. But I came across a new problem, when the Po between 15 between the DELL switch and the Catalyst 3750 goes UP, some networks that pass this trunk get pinged while others work normally.
The scenario is very strange, as Catalyst 3750 is isolated from the network at first, so there is no loop scenario in this condition.
The condition only normalizes when I disable Po 15 between the DELL switch and Catalyst 3750 and also need to shutdown and shutdown command on Catalyst 4500 Po 10 that connects with the Dell Switch. Once this is done, the intermittences that occur on some networks normalize and no longer failures.
I checked the logs of all switches involved and no STP loop and convergence logs are logged.