IV16149: wrong subnet and netmask for Chassis IpAddress

ITNMIP_Patch_V3.8.0.89_Win32
3.8.0-TIV-ITNMIP-Solaris-REF-FP0007
3.8.0-TIV-ITNMIP-Linux-REF-FP0007
ITNMIP_Patch_V3.8.0.89_AIXPPC32
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

• ITNM 3.8 FP5
  Linux
  
  The current issue is that the device has wrong information:
  
  
  
  
  
  
  
  
  
  
  
  It seems that when the discovery runs the first time, the
  default
  network is /24 for all the devices.... and after this netmask is
  never
  updated according to the SNMP information recovered when ITNM
  build the
  devices and its interfaces. First the default value of /24 is
  misleading. The default should be /32 (= scope of a single
  host).... and
  secondly this netmask (/32) should be updated according to the
  SNMP
  info.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ITNM 3.8 FP6, 3.9 FP2 and earlier versions.                  *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * ITNM was attributing the wrong subnet (mask) for a chassis   *
  * entity. It was being given a /24 instead of /21 mask. This   *
  * was the result of an incorrect inferrence.                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to ITNM 3.8 FP7 or 3.9 FP3                           *
  * fix pack | 3.9.0-ITNMIP-FP0003                               *
  * fix pack | 3.8.0-ITNMIP-FP0007                               *
  ****************************************************************
  

Problem conclusion

• ITNM will now look at the interface that has the ip address that
  ITNM found the device by (m_UniqueAddress) and use it's subnet
  config to add to the chassis.
  

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 PSN

     UP

• R380 PSY

     UP

• R390 PSN

     UP

• R390 PSY

     UP