06-17-2008 07:24 AM
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.
06-17-2008 07:25 AM
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.
06-17-2008 07:33 AM
There have been no such changes as you mentioned. Could it be something else?
06-17-2008 07:43 AM
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.
06-17-2008 07:46 AM
I have increased SNMP timeout to 10 seconds, but nothing changed.
06-17-2008 07:43 AM
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.
06-17-2008 07:45 AM
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.
06-17-2008 07:49 AM
Is there a sw patch for this bug?
06-17-2008 07:52 AM
Yuo can contact TAC to get it. The patch is a new DFMInChargeSubscriber.class.
06-18-2008 06:45 AM
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.
06-18-2008 09:11 AM
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.
06-18-2008 09:16 AM
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.
06-18-2008 09:20 AM
Some devices have been moved back to Learning and then back to "All Questioned Devices in Inventory Services > Others (subcategory)"
06-18-2008 09:33 AM
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.
06-18-2008 09:42 AM
casuser has full access to the patched file. I told him that I have DFM 2.0.10 when I opened the case.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: