It all depends on how you want to manage these devices, and how you are adding them to DCR. Cisco generally recommends one create a loopback interface on all multi-interface devices, and use that address for management. You can then enable Loopback resolution in Campus Manager Discovery, and Campus will find the lowest UP loopback, and use that for management. So in that case, you only need a DNS record for that loopback.
If the device is a Layer 3 device (A.K.A. a router) I always add a loopback address. I add the device to the DCR by the loobback. I also add the following config to force the L3 device to use the loopback for most of the management traffic
ip flow-export source Loopback0
ip tacacs source-interface Loopback0
logging source-interface Loopback0
snmp-server trap-source Loopback0
If the device is a Layer 2 device (A.K.A a switch that does no routing) it usually only has one L3 interface for management. In this case I use the single L3 interface for management and add the commands listed above changing Loobback0 to whatever the L3 VLAN is.
I then have a forward and reverse DNS entry for the management address and only reverse DNS entries for any remaining L3 interfaces. Having the reverse DNS for all the interfaces makes traceroutes easy to read.
I manage about 10,000 Cisco devices this way and it works great.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.