We're running RME3.4 with all of the latest patches on Sol2.8. All of the attributes in the RME database are verified to match the SNMP community strings on the devices. The devices we are trying to completely manage on the other side of firewalls are 6500s, CSS-11506 and 3640s. The firewall rules have routing from CiscoWorks to each device and port 161 for SNMP is allowed to pass through. However, the SNMP Write community strings show as incorrect in the attribute check. We've deleted the SNMP write strings and readded them, still have the same problem. Also tried different strings and received the same problem. The only attribute failure is the SNMP write community strings, telnet, TFTP, SNMP read, radius all work fine.
If you're using RMEs Check Device Attribute (CDA) feature, then you'l find several bugs if you do a CCO Bug Toolkit search. CDA is not very relaiable. Do an export to file and see if the RW strings show up correctly as what you've entered. If they are then, CDA is wrong.
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.