Tivoli Network Manager and Discovery Library Adapter. A "type" of chicken or egg.
kcstone 0600021BUE Visits (3832)
IBM Tivoli Network Manger (ITNM IP 3.9) can use the Discovery Library Adapter (DLA) to export data for integration into other systems.
Detailed documentation exists here
One common question with the DLA, is an explanation of this particular "type"
Type should be something like a router or a switch, but what was discovered as a ComputerSystem?
What went wrong with the discovery of this entity? Or is the DLA not working correctly?
Looking at the discovery, or discovered topology in ncim, no "ComputerSystem" is found, so that means it must be the DLA then?
Understand the assignment of "type" to understand whether the source of the problem is ITNM, or the DLA.
If an entity is found to be "ComputerSystem" in all likelihood, the sysObjectId was not associated correctly during discovery. Take a look at the fields of ncim.deviceFunction in ncim
Look at the popu
To add a new entry to ncim.deviceFunction simply insert a new row using your preferred method for your database access.
Here is an example with ncp_oql from the ITNM core server
[root@server data]# cd $PRECISION_HOME
Once this is done update popu
When using the Discovery Library Adapter it is hard to tell whether a problem is with the DLA or ITNM. In this case ITNM was the chicken.
I mean the egg.