We are going start implementing UDLD on our core switches , is there any potential gottchas other than turning it on globally and then at the port level ? Should we disable it at the port level before enableing it globally and then bring it up one at a time . Also is there any disruption on the ckt. while this is being activated or is completely transparent to the user community .
There are no gotchas such as port resets as it is a overlay protocol, the only real choice is whether to enable aggress-mode.
Do not use UDLD with the ON - AUTO trunk combination. So make sure that they are auto/des or auto/auto which is recommended by Cisco.
When enabling aggressive UDLD, the recommended message interval is 30 seconds; beware that it might shut down the port on a link where there is an extended period of trunk state mismatch on two sides of the link, especially when the NMP is significantly loaded.
Is there any problem if you are using the on/ on trunk combination ? That's what we are using , way back when we first started using this we had problems trying to use the desirable/desirable combination . I saw the reference you were talking about about the on/auto combination , out of curiosity what problems does that cause if you did use the on/auto combination , it's not really clear reading the material other than it says it's not reccomended .
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...