
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2017 06:33 PM - edited 03-08-2019 12:52 PM
What is best practice for interface description ?
Solved! Go to Solution.
- Labels:
-
Other Switching
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2017 07:57 AM
Two particular points to keep in mind. First, you'll probably want some information in descriptions to help when troubleshooting a down interface. Second, you may want both "permanent" and "temporary" information in the description. The former might be things like a service provider and circuit information. The latter might something like "*** circuit accidentally cut 11/23/17 - should be restored 11/28/17 - J. Doe ***, which would be removed when circuit back on-line.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2017 06:52 PM
It can be whatever you want as long as it makes sense for you and your organization.
Here are a couple of examples:
to 1st floor access-sw port 1/1 ip 10.10.10.1
to isp router port 3/1 circuit id 1234567
HTH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2017 08:26 PM
There is no "best practice" for giving an interface a description.
It could named as "Yipee, Yipee Ka Yaya" or "yabba dabba D000" but it won't help if the description doesn't mean anything.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2017 09:46 AM
I would say that the Best Practice is that every interface should have a description and that the description should convey information that is meaningful to the team that supports the network. Depending on your environment that meaningful information might be about physical location, or might be about its function, or connectivity between devices, or something else that is meaningful to your team.
HTH
Rick
Rick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2017 07:08 AM
P1:XIF:WCL:150MB:ComCast:H00A64534:xif-b208inr04 EBGP #3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2017 07:57 AM
Two particular points to keep in mind. First, you'll probably want some information in descriptions to help when troubleshooting a down interface. Second, you may want both "permanent" and "temporary" information in the description. The former might be things like a service provider and circuit information. The latter might something like "*** circuit accidentally cut 11/23/17 - should be restored 11/28/17 - J. Doe ***, which would be removed when circuit back on-line.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2017 08:01 AM
Generally I use "Hostname-Card-Port".
With this information you can troubleshoot faster.
B.R.
M.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2017 08:11 AM - edited 11-27-2017 08:14 AM
Hi
I think there are many ways, but you could be specify for example Circuit name with destination host and port, for example:
interface g0/0
description [VC 101 to NY01L2R01 G0/1]
>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<
