Data Collection takes too much time to finish after enabling debug

[kmong]

Hello guys,

I am currently troubleshooting Topology services. DFM alerts do not reflect in the topology when we were performing alert simulation. We disconnected the link between two switches, alerts can be seen in the Alerts and Activities window, but it did not reflect in the Topology, we were expecting the link to turn red or atleast see a DFM alert icon on top of the device, but nothing happens.

So the TAC engineer told me to enable debugging on all modules for the Data Collection,add the ip address of the 2 devices being tested, close the topology, and then disconnect the link, and lastly perform data collection on Campus Managers home page after disconnecting the link.

Problem is when performing data collection, the process takes too much time before it ends. There are only 101 devices for data collection, data collection started at 12:05 am, it is now 2:11 am and the data collection is still running. I am suspecting that the process already hanged up, because the last time we tried this, data collection also did not end, it is still running for about 3 days, I was only able to access the topology after restarting the daemons

Help on this case please. I am using LMS 3.2 installed on a Solaris server, Campus manager version is CM 5.2

[ngoldwat]

Hi,

Campus Manager polls the entire network for device and link status periodically. The default value is 2 hours.

You can check it in Campus Manager > Admin > Data Collection > Device poller.

This feature allows you to:

* Configure the time interval at which the network is polled.
* Poll only a critical set of devices.

Use this option to see the device and link status without running Data Collection.

Since Data Collection consumes significant system resources, you can simply poll the network and view the device and link status in Topology maps. If you decrease the value from 2 hours to a small value like 2 or 5 minutes, it will cause a jump in CPU utilization and bandwidth resulting in performance degradation.

You can also use the following:

Adding Critical Devices to the Device Poller
=========================================

You can add devices to the Critical Devices list as follows:

1. Launch a Topology map.
2. Right click a device and choose the Add device to Critical Poller option.

To add a device to the Critical Devices list from N-Hop View Portlet:

1. Launch N-Hop View Portlet.
2. Go to the configuration screen and choose the Poll devices option.

For complete details on N-Hop view portlet, see N-Hop View Portlet.

Caution:

If the critical set of devices is more than 30, the amount of traffic generated as part of polling cycle will be occupying good amount of bandwidth.

For further details please check the Help guide of your LMS, use the following keywords: "device poller"

Unfortunately, this is the only option available, the Network Topology is not a real-time tool. For real-time fault notification you need to use DFM.

Thanks,

Nick