I wanted to advise you never to use this convention, it makes it very hard to troubleshoot or to identify the routers or switches. if you need to have this info on the router you should add it may be on the banner or you may add it in "snmp-server location XXXXXXX" this may also be useful.
Also it would be very hard to change this nameing convention once implemented.
I suggest to use naming convention that contains the function and the geografical location.
Our network is part of a CAN. For the most part I monitor the switches and routers in our LAN. In terms of identifying the routers/switches, I think the naming convention we use identifies the device location all the way down to rack position and IP. Why do you feel it makes it hard to troubleshoot or identify?
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...