IV63726: ALU 5620 SAM COLLECTORS SHOULD SUPPORT LLDP CONNECTIONS TO NON-SAM MANAGED DEVICES

3.9.0-TIV-ITNMIP-Solaris-FP0005
3.9.0_INSTALL_NLS_FP0005
3.9.0_INSTALL_FP0005
3.9.0-TIV-ITNMIP-Windows-FP0005
3.9.0-TIV-ITNMIP-zLinux-FP0005
3.9.0-TIV-ITNMIP-Linux-FP0005
3.9.0-TIV-ITNMIP-AIX-FP0005
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-FP3  : Platform independent and applicable for other
  FixPacks too (i.e. GA, FP1, FP2 & FP4).
  
  Currently the SAM Collectors only create layer 2 links from LLDP
  data is both ends of the link are managed by the SAM. If the
  remote end is not managed by the SAM then the link is dropped,
  which is unnecessary as there are alternative fields that could
  allow topology resolution in the stitchers. Consider using the
  systemName and portId fields in place of remotePeerPortPointer
  in such cases.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users discovered with ALU SAM 5260 LLDP connection support   *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Currently the SAM Collectors only create layer 2 links from  *
  * LLDP data is both ends of the link are managed by the SAM.If *
  * the remote end is not managed by the SAM then the link is    *
  * dropped, which is unnecessary as there are alternative       *
  * fields that could allow topology resolution in the           *
  * stitchers.Consider using the systemName and portId fields in *
  * place of remotePeerPortPointer in such cases                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to ITNM-IP | fix pack | 3.9.0-ITNMIP-FP0005          *
  *                                                              *
  * Modified the Collector to gather systemName (remote sysName) *
  * and portId (remote ifIndex) and to return links even when    *
  * the remotePeerPortPointer field is empty.Having seen the     *
  * data I'm not sure what remoteIndex represents afterall so    *
  * i'm not bothering to get it, but remember you can use the    *
  * Extrainfo.cfg feature to add more lldp.remotePeer fields     *
  * such as this to the LLDP neighbours (they will appear in     *
  * CollectorLayer2.returns m_RemoteNbr->m_ExtraInfo).           *
  ****************************************************************
  

Problem conclusion

• Modified the Collector to gather systemName (remote sysName) and
  portId (remote ifIndex) and to return links even when the
  remotePeerPortPointer field is empty.Having seen the data I'm
  not sure what remoteIndex represents afterall so i'm not
  bothering to get it, but remember you can use the Extrainfo.cfg
  feature to add more lldp.remotePeer fields such as this to the
  LLDP neighbours (they will appear in CollectorLayer2.returns
  m_RemoteNbr->m_ExtraInfo).
  

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

• R390 PSN

     UP

• R390 PSY

     UP