I am using CW LMS 2.6. I have managed my devices using the IP Address. i have all my devices and their IPs in the /etc/hosts file (OS Solaris 9).
My problem is that i made a mistake in that file and put the same name to two IPs (10.10.1.1 and 10.10.1.2 for example had EX name).
When i tried to see syslog messages for that two devices, i see all messages (i suppose that are syslogs from the two devices) only in one device (10.10.1.1) and no messages in the other device. I suppose that it makes the relation between IP and name only for the first entry in the hosts file and enters all the messages as they were only from that device.
if i watch for syslog in the syslog_info file i see that syslog messages are arriving with that name (EX).
I have deleted the devices in CiscoWorks, and i have corrected the mistake in the hosts file (now 10.10.1.1 has EX1 and 10.10.1.2 has EX2) and i have managed the devices once more but now, although syslog messages are arriving to CW (i have done an snoop) i cannot see them in the CiscoWorks, nor in the syslog_info file because they continue arriving with EX name.
You should use the resolver.pl script that comes with CiscoWorks to make sure those IP addresses really resolve to different names:
Next, when you say you rebooted CW, does this mean you rebooted the server, or simply restarted dmgtd? If the latter, you might try restarting syslogd and nscd on the Solaris server (or do an actual reboot).
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.