03-26-2014 06:22 AM
Hi,
I'm thinking of creating a feature request but want to hear your opinion first. This idea came up when I was configuring switches remotely, and a miscabling caused some issues.
My idea is to have a test feature of CDP that would work like this:
A new capability code could be used (like 't' for testing) to mark this connection temporary, so the other end would also not learn anything about the new device.
What do you think?
03-27-2014 05:12 PM
There are a lot of ways to accomplish that without a new feature. If it is a switch port, simply configure it as an access port with an undefined vlan. Routed ports even eaiser no ip address. Or is there some reason these techniques would not work.
03-28-2014 01:31 AM
They wouldn't work if the cables are laid to the wrong switchports; and you can't check it from a remote location. I've seen a few incidents because of this. :)
03-28-2014 06:35 AM
I dont understand the statement. It seems that your feature would a) not pass any real traffic and b) automatically shut the port back down. While my suggestion would not accomdate b), when could you do your test cdp command but not do switchport access vlan 999 no shut, as your stated suggestion requires access to the device CLI remotely or not.
04-04-2014 03:59 AM
Oh, I pushed the wrong button, see my answer above (with the drawing).
04-04-2014 03:58 AM
Consider this scenario:
I've requested a link between Switch 1 and Switch 2. The subcontractor made a mistake and laid the cable between Switch 1 and Switch 22. I configure the switchports on Switch 1 and Switch 2, bring up the interfaces, then nothing happens.
Your solution wouldn't help in this case, because I don't know where the cable is connected. I can't set all unused ports on all switches to find it, and I don't want to risk creating a loop or other issues.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide