DFM 2.0.10 - Questioned devices in Inventory Services

Unanswered Question
Jun 17th, 2008
User Badges:

I have several managed devices in DFM that are in "All Questioned Devices in Inventory Services" under SNMP timeout. These devices were in "All Known Devices in Inventory Services" before. What caused this and how can I rectify this problem. Thank you.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4.3 (3 ratings)
Loading.
Joe Clarke Tue, 06/17/2008 - 07:25
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

SNMP timeouts are typically caused by a change in the SNMP credentials on the device. They could also be caused by routing changes or ACL changes either on the target device or on an intermediate gateway.

santipongv Tue, 06/17/2008 - 07:33
User Badges:

There have been no such changes as you mentioned. Could it be something else?

Joe Clarke Tue, 06/17/2008 - 07:43
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Latency in the network could make SNMP time out. You can increase the DFM SNMP timeout under DFM > Device Management > SNMP Config. By default, it is four seconds.

santipongv Tue, 06/17/2008 - 07:46
User Badges:

I have increased SNMP timeout to 10 seconds, but nothing changed.

santipongv Tue, 06/17/2008 - 07:43
User Badges:

For one device, I have noticed that it was moved from All Known Devices to All Questioned Devices when there is a network congestion and it stays in All Questioned Devices since.

Joe Clarke Tue, 06/17/2008 - 07:45
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

There is a known bug where devices move into a Questioned state, but the reason is no SNMP Timeout. Those devices get put into the Questioned/Other state, and the cause is an internal error.


If the device says that SNMP timed out, you can start a sniffer trace filtering on udp/161 traffic, then try rediscovering the device.

Joe Clarke Tue, 06/17/2008 - 07:52
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Yuo can contact TAC to get it. The patch is a new DFMInChargeSubscriber.class.

santipongv Wed, 06/18/2008 - 06:45
User Badges:

I applied the patch, but now I am not able to remove/rediscover those devices. I did uncheck "Synchronize with Device Credential Repository" in Device Selector.

Joe Clarke Wed, 06/18/2008 - 09:11
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Delete the devices from DFM, and they should go into a pending state. Then, run:


pdterm InventoryCollector InventoryCollector1 TISServer DFMOGSServer Interactor Interactor1 NOSServer PTMServer


pdexec InventoryCollector InventoryCollector1 TISServer DFMOGSServer Interactor Interactor1 NOSServer PTMServer


That should purge the devices.

santipongv Wed, 06/18/2008 - 09:16
User Badges:

E:\PROGRA~1\CSCOpx\bin>pdterm InventoryCollector InventoryCollector1 TISServer D

FMOGSServer Interactor Interactor1 NOSServer PTMServer

ERROR: cmd failed. Server reason: One of the entries in a list of application n

ames to pdshow, pdexec or pdterm is invalid.


E:\PROGRA~1\CSCOpx\bin>pdexec InventoryCollector InventoryCollector1 TISServer D

FMOGSServer Interactor Interactor1 NOSServer PTMServer

ERROR: cmd failed. Server reason: Application InventoryCollector1 is not registe

red. All requests to operate on this application will be ignored.


santipongv Wed, 06/18/2008 - 09:20
User Badges:

Some devices have been moved back to Learning and then back to "All Questioned Devices in Inventory Services > Others (subcategory)"

Joe Clarke Wed, 06/18/2008 - 09:33
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Make sure the permissions on the patched file are correct, and that casuser has full access. Also, check with the TAC engineer to make sure you got a patch for DFM 2.0.

santipongv Wed, 06/18/2008 - 09:42
User Badges:

casuser has full access to the patched file. I told him that I have DFM 2.0.10 when I opened the case.

Joe Clarke Wed, 06/18/2008 - 09:45
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Since you have an SR open, provide this information to your engineer. They may need to get onto your server to check things.

Actions

This Discussion