All necessary (for monitoring) OIDs and traps it give. With net-snmp tools I can get all this, but with Cisco Works I have problem. Device set as "Unknown" and I can`t receive traps from it (DMF "see" event only from known device). It can possible to solve this problem, by means of addition extra OIDs to clarify device entity for Cisco Works? Are there any other ways?
I can confirm that this sysObjectID is supported in Common Services 3.0.3, RME 4.0.3, and DFM 2.0.3. Try deleting the device from DCR, then re-adding it. Keep in mind that the SNMP read-only community string is vital for this device to become known in DCR.
I did it, manually added device as PIX. In DFM did: Device Management->Rediscover/Delete->All Unknown Devices->Rediscover button. Tcpdump show recuests/responses. Here all good. But device sill unknown.
Don't select a device type when you add it. Leave it as unknown, and then let one of the applications figure out what type of device it is.
When you originally told me the sysObjectID, was that from a walk of the system branch, or did you just tell me the sysObjectID you chose in DCR? I want to see the output of the following snmpwalk command:
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.