CM Topology not displaying "inactive link" when link is physically disconnected

[kmong]

We are currently performing alarm simulation using LMS 3.2 by physically disconnecting the link between two switches. Alarms/events are reflected immediately in the DFM Alerts and Activities. But I noticed that it did not reflect on the Topology. I am expecting the link to turn red to show that the link was inactive, but there were no changes seen in the Topology. Here are the steps done in Campus Manager>Administration>Data Collection:

1. I have checked the data collection settings, data collection is performed every 4 hours.
2. I have verified that device polling is enabled for all devices. And then I lowered its value to 30 seconds to immediately detect any device or link failure.
3. I have checked the SNMP Timeouts and Retries. Changed the target IP to the specific subnet, Timeout is 6 seconds, and only 1 retry
4. I also checked DFM Poller Settings. Polling for DFM alerts are enabled and is set on its lowest time interval which is 6 minutes

I know that Campus Manager Topology is not for real time monitoring, but we atleast need to see the icons/links to change when a link is down or when a device is unreachable. What else could I do to resolve this?

Campus Manager is the latest version for LMS 3.2 (CM 5.2)

Thanks!

[Gaganjeet Chug]

Hi,

As you are already aware that Campus Manager is not for real time monitoring but you was on right track if you want to see the changes on the topology map :-

"I have verified that device polling is enabled for all devices. And then  I lowered its value to 30 seconds to immediately detect any device or  link failure.". You can make it to 2 minutes and not 30 seconds.

This is the only way to detect the changes that occur in network from the campus manager point of view however it will increase the network utilization too.

Thanks,

Gaganjeet

If this post answers your question, please click the "Correct Answer" button"

[kmong]

Why will i put it back to 2 minutes? I lowered it to 30 seconds so that it can easily detect any failure

[Gaganjeet Chug]

Hi,

"Why will i put it back to 2 minutes? I lowered it to 30 seconds so that it can easily detect any failure"

You can make it x second as well but the point is it will start polling the device in x seconds. If thats ok with your network then its fine with CiscoWorks too however as you are already aware that Campus Manager is not live monitoring tool and DFM is the best tool way for such kind of monitoring.

Thanks,

Gaganjeet