Best practices for creating names/description for switch links

[schulcz]

Hi Guys!

I’m thinking about a good naming scheme for switch-to-switch, switch-to-router, switch-to-firewall, switch-to-server (and so on) links that are informative enough, transparent (the backbone and access ports are spectacularly separated at first glance), but still not too long (e.g. --- === xxxxx === ---). I don't like overly long names because they usually lose the point. For example, when I'm using a "show int statu" command, I'm usually forced to use the "show int descr" command as well to see what I looking for, which slows down the troubleshooting or configuration process.

I’ve seen plenty of methods in client networks in recent years, but I couldn’t tell which one was the most practical.

I wonder who uses what method to form the names? (e.g. for simple links or for aggregated links and so on..)

Thanks!

[balaji.bandi]

we generally follow naming convention :

Site = (can be company short)  EX : BB

Localtion : area of the switch EX : CEN

Building :

Floor :

serving switch :

BB-CEN-BLD02-ACC1

BB-CEN-BLD02-ACC2 - if you have 2 stack switch there.

is this works for you ?

[Reza Sharifi]

switch-to-switch

source sw-1 to destination sw-2 port 1/1/1 to 3/2/8

description: to-5th-flr-sw-2 port 3/2/8

source sw-2 to destination sw-1 port 3/2/8 to 1/1/1

description: to-8th-flr-sw-1 port 1/1/1

switch-to-firewall

description: to-1st-flr-fw-1 port 1/1

firewall to switch

description: to-2nd-flr-sw-3 port 3/5/1

or 

description: to-5th-flr-3750-2 port 3/2/8

description: to-8th-flr-4500-1 port 1/1/1

And so on...

you can usually add more characters up to 32.

HTH

[Giuseppe Larosa]

Hello @schulcz ,

I usually use something like

interface x/y

desc  to  <remote-hostname>:<remote-interface>

with a host naming convention that tells the role of the device SW RT FW in the first two letters of the hostname.

Hope to help

Giuseppe