Polling suspension options

Set a device or component to an unmanaged state to suspend it from Network Manager network polling.

When a device or component is unmanaged, it is not polled by Network Manager, and events are not generated for the device or component. Also, no root cause analysis (RCA) is performed on events for that device.

Restrictions

Setting the device to unmanaged affects only Network Manager polling, it does not stop other polls from retrieving information from the device or its components and raising alerts where applicable. However, the alerts from other sources are tagged as unmanaged to indicate that the device or component they were raised against are in maintenance state.

Options to suspend polling

To suspend a device or its component from active poll operations, you have the following options:

Set a device or component to unmanaged

You have the following options:

Use the Network Views or the Hop View
Use the Unmanage node tool

If you set a device to unmanaged, then all components within that device also become unmanaged. If an individual component within a device is set to unmanaged, then only that component and any components contained within become unmanaged, the device itself remains in managed state. A component can be managed or unmanaged only if the device within which it resides is in managed state. Also, setting the management interface associated with the chassis to unmanaged state does not suspend polls for the whole device.

Set specific interface types to be permanently unmanaged

This means that the specified interface types are not polled by Network Manager. Also, you can set new devices not to be polled initially after being discovered and added to the topology. These settings are determined by the PopulateDNCIM_ManagedStatus.stch file and the NCIM database tables.