Unmanage Interfaces via discovery
What is one of best logic to use to unmanage interfaces of network devices that are not connected to other devices and by doing so, does it impact any functionality?
The managedstatus is an attribute under ExtraInfo, and if present, it takes the following values:
- 0 = managed (also the default if the field is not present)
- 1 = unmanaged (this can be altered via the GUI)
- 2 = unmanaged by disco (this cannot be altered via the GUI)
- 3 = unmanaged by disco that are Out of Scope.
Out of the box, ITNM has a discovery stitcher ($NCHOME/precision/disco/stitchers/TagManagedEntities.stch) that unmanages Interfaces (EntityType = 2) and the logic used is self explanatory. The stitcher is called in final phase of discovery and sets ExtraInfo->ManagedStatus flag to either 2 or 3.
Typically when customers are using 'SNMP Link State' policy, it meant to poll entire table where most of the interface status users may not be interested in. Often customers only interested to poll interfaces that are connected to another device and unmanage rest.
In-order to unmanage all interfaces that are not connected to another device - you can append following logic : (ExtraInfo->ReverseRelatedTo is NULL and RelatedTo is NULL).
Here is excerpt from TagManagedEntities.stch with new logic appended:
oqlUpdate = oqlUpdate + interfaceFilter + rediscoveryFilter +
ExtraInfo->m_IfDescr like 'Dialer'
(ExtraInfo->ReverseRelatedTo is NULL and RelatedTo is NULL)
ExtraInfo->m_IfDescr like 'Async'
...................deleted few lines.................
ExtraInfo->m_IfDescr like 'VLAN'
ExtraInfo->m_IfAlias like 'NoMon'
It doesn't impact any functionality - but its possible you might miss some of the Interface Ping polls if you have configured interfaces that aren't connected to any other device.
More support for:
Tivoli Network Manager IP Edition
Software version: 3.8, 3.9
Operating system(s): AIX, Linux, Solaris, Windows
Reference #: 1626269
Modified date: 06 February 2017
Translate this page: