For some reason a couple of msfc's that have never shown to be down just started being unreachable a couple of days ago. The msfc's are in fact up and running fine. The interesting thing is that it now has them listed with the loopback ip instead of the vlan 1 ip address as all other devices are. What would cause this to change since no changes have been made in CiscoWorks? If I delete and re-add the devices manually, they show to be fine until the next discovery. My discovery settings seem to be fine and have not changed prior to this occuring.
The discovery uses DNS if configured, so it could be that your DNS now points to the loopback address of the MSFC instead of the Vlan 1 address. On discovery an interface is discovered - a lookup is done for a name, then a lookup on the name. The IP returned is used by ANI/Campus Manager....
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.