DFM3.2/LMS3.2 lots of Unresponsive-Events

Unanswered Question
Jan 27th, 2010


We cant use DFM3.2/LMS3.2 due to a lot of false-positve Unresponsive-Events. The cause is that a virgin installed DFM polls each found IP-interfaces, that is not administrativly shutdown. This behavior is unuseable for this network, because of some isolated and protected networks not beeing routed to the LMS.


1. Is there a possibility to let DFM availability ping the device management IP's got from DCR only (like in previous DFM versions)?

2. or is there a possibility to can filter out networks for availability ping's in DFM?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Joe Clarke Fri, 01/29/2010 - 17:19

1. DFM will, by default, ping all IP interfaces on a device.  You can go to DFM > Device Management > Device Details, and unmanage those IP addresses which you do not want DFM to ping.  That will greatly reduce those unresponsive events.  Note: you cannot unmanage the device's management IP address.  DFM must always be able to ping this address.

2. See 1.

STEFFEN NEUSER Wed, 02/03/2010 - 01:40

Thx, Joe for this very good hint.

To keep the management IP for polling was not the point. If we can't reach the management IP's, than we would have problems at a very basic level: how to choose management IP's:)

Many thx, Steffen


This Discussion