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..)