09-28-2015 10:07 PM - edited 03-10-2019 11:06 PM
How do interface descriptions work with 802.1x? Will the descriptions remain blank? Will all ports participating in NAC get a generic description? Is it possible to dynamically configure the port description based on the device that is connected to the interface? Other?
Thanks in advance!
09-29-2015 04:06 AM
Interface descriptions are not affected by 802.1x. Generally 802.1x uses RADIUS A-V (Attribute-Value) pairs to send down changes to the network access device. There's not an A-V pair for interface description that I'm aware of.
09-29-2015 10:19 PM
Thanks so much for your response! Is there available guidance/standards on interface descriptions for ports participating in 802.1x?
09-30-2015 05:41 AM
There's no official guidance or best practice recommendation that I've ever seen. It's very much a local preference whether or not to even use interface descriptions.
Personally I use them only for a quick visual check for what a given interface should be. They can be misleading though as they are only as good as your knowledge of and control over the physical connections to your devices.
That's one of the reasons we use ISE whereby the identity of what's connected to a given interface is better ascertained by looking at the Accounting record of that interface.
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