Database, disco.profilingData, Details.returns.  If an admin wants to find a quick chassis count from the last discovery in IBM Tivoli Network Manager,  what is the best way to find this?

Database

This is probably the most accurate measure

[root@nc9053115085 precision]# dbaccess - -
> connect to 'itnm' user 'ncim';
   ENTER PASSWORD:

Connected.

> select * from domainSummary;

domainmgrid     1
createtime      2014-01-30 15:16:36
changetime      2014-01-31 14:15:28
entitycount     81152
chassiscount    8445
interfacecount  30206
 

When model has pushed the updated topology to NCIM, the database will show an updated timestamp in changetime and a current chassiscount.  Maybe the user doesn't have access to the database?

disco.profilingData

Technote for collecting disco profiling data

This not only provides the lastest discovery information, but accumulates previous discovery data.   But there might be some confusion here look at this snippet from disco.profilingData

          'm_NumMainNodesWithAccess' => 1806,
          'm_Phase3StartTime' => 1391123150,
          'm_NumInterfaces' => 30206,
          'm_NumRouters' => 994,
          'm_NumMainNodes' => 8445,
          'm_NumIPs' => 22304,
          'm_NumSwitches' => 0,
          'm_DiscoveryMode' => 0,
          'm_Position' => 'LAST',
          'm_NumDetailsReturns' => 11561,

m_NumMainNodes is your chassis count.  This data is taken from workingEntities.finalEntity.   But look at m_NumDetailsReturns.   Shouldn't Details.returns reflect a chassiscount?

Details.returns

Remember Details.returns has been fed from finders during discovery.   These are commonly IP addresses that were discovered by ping.   Maybe there are some interfaces or some duplication that will be cleaned up during AssocAddress and the translations portion of discovery.  Details.returns is not necessarily a chassis count!
 

 

Tags:  itnm details disco