IV20642: HOPVIEW UNABLE SHOW TO LAYER3 CONNECTIVITY ON ROUTING MODULES (ENTITYTYPE=8)

IBM Tivoli Network Manager IP 3.9.0 Fix Pack 3, 3.9.0-TIV-ITNMIP-FP0003
IBM Tivoli Network Manager IP 3.9.0 Fix Pack 4, 3.9.0-TIV-ITNMIP-FP0004
IBM Tivoli Network Manager IP Edition 3.9.0 Fix Pack 5, 3.9.0-TIV-ITNMIP-FP0005

APAR status

• Closed as program error.

Error description

• v3.9-Applicable for both GA & FP1 builds & platform independent.
  
  MSFC modules (e.g. which normally found in any Cisco modular
  switch - 65xx etc) are now created duing discovery as
  EntityType=8 where as in previous versions the modules with
  routing capability (IpForwarding=1) were created as
  EntityType=1.
  
  As a result, when you search the routing module in HopView, it
  displays the switch that contains the module rather than actual
  module itself. If the module has any layer 3 connectivity -
  those connections are not displayed due to the fact, the main
  node doesn't hold Layer3 connectivity.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All ITNM 3.9 Users                                           *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * MSFC modules (e.g. which normally found in any Cisco modular *
  * switch - 65xx etc) are now created duing discovery as        *
  * EntityType=8 where as in previous versions the modules with  *
  * routing capability (IpForwarding=1) were created as          *
  * EntityType=1.                                                *
  *                                                              *
  * As a result, when you search the routing module in HopView,  *
  * it                                                           *
  * displays the switch that contains the module rather than     *
  * actual                                                       *
  * module itself. If the module has any layer 3 connectivity -  *
  * those connections are not displayed due to the fact, the     *
  * main                                                         *
  * node doesn't hold Layer3 connectivity.                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * | fix pack | 3.9.0-ITNMIP-FP0002                             *
  ****************************************************************
  

Problem conclusion

• Post install steps:
  
  Drop and recreate the mainNodeDetails view. This is best done
  when tip is down so as not to impact any running UI processes.
  
  DROP VIEW mainNodeDetails;
  
  CREATE VIEW mainNodeDetails AS SELECT c.accessIPAddress AS
  ipAddress, c.className, e.description, e.entityName,
  c.sysObjectId, e.entityId, c.sysName, x.classType,
  e.displayLabel, d.domainMgrId, c.sysDescr, c.sysLocation,
  c.sysContact, c.sysUpTime, c.sysServices, c.ipForwarding,
  c.entPhysicalVendorType, c.entPhysicalDescr, c.serialNumber,
  e.manual FROM entityData e INNER JOIN chassis c ON c.entityId =
  e.entityId INNER JOIN classMembers cm ON cm.entityId =
  e.entityId INNER JOIN entityClass x ON x.classId = cm.classId
  INNER JOIN domainMembers d ON d.entityId = e.entityId;
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  NC/PREC DISCOVY

• Fixed component ID

  5724O52DS

Applicable component levels

• R380 PSY

     UP