How Make Unknown device Known in CW?

[Karl_Walther]

Good day!

I make SNMP agent for some router.

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?

Thanks!

[Joe Clarke]

What version of CiscoWorks? What type of device is this? What is its sysObjectID?

[Karl_Walther]

1. Cisco Works Common Servicies 3.0.3

2. Campus Manager 4.0.3

3. Cisco View 6.1.2

4. Device Fault Manager 2.0.3

5. Integration Utility 1.6.0

sysObjectId - initially was random,

later set 1.3.6.1.4.1.9.1.227 - as PIX, but it is useless. Evidently, this insufficiently :(

[Joe Clarke]

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.

[Karl_Walther]

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.

[Joe Clarke]

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:

snmpwalk -v 1 -c system

[Karl_Walther]

in previous post I made mistake: in "Rediscover/Delete" status not "unknown", but "learning" and discover progress stop at 10%

# snmpwalk -v 1 -c public 10.4.0.98 system

SNMPv2-MIB::sysDescr.0 = STRING: CryptoRouter, ID 0

SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.9.1.227

DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (398) 0:00:03.98

SNMPv2-MIB::sysContact.0 = STRING: walther

SNMPv2-MIB::sysName.0 = STRING:

SNMPv2-MIB::sysLocation.0 = STRING:

SNMPv2-MIB::sysServices.0 = INTEGER: 3

SNMPv2-MIB::sysORLastChange.0 = Timeticks: (0) 0:00:00.00

[Karl_Walther]

The problem was solved by adding extra OIDs similar with real PIX. WS is nightmare.

jclarke thanks.