IV28101: NOSUCHNAME EVENTS GENERATED FOR ENTITIES THAT WERE POLLING WITHOUT ERROR.

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

APAR status

• Closed as program error.

Error description

• Product:  Tivoli Network Manager
  Version: 3.8
  Component: ncp_poller
  
  
  Replication:
  Configure SNMP Link State poll policy *with* interface scoping.
  (Policies without interface scopes will not trigger this APAR).
  Failover to the Backup domain by stopping the entire Primary
  domain.
  (Failing over by stopping a monitored component will not trigger
  this APAR).
  Failback by restarting the Primary domain.
  
  
  
  Symptoms:
  On failback the SNMP Link state policy may produce alerts
  reporting No Such Name found for the monitored interfaces.
  In the default product the symptoms are intermittant and may
  not occur on every occasion.
  
  L3 can replicate consistently in a development environment where
  a delay can be hard coded into the software.
  
  
  Cause:
  When a poll policy is initialised, various ncpoller tables are
  populated with information about the poll. This includes, for
  example, the OIDs to query and the target addresses to poll.
  
  When the SNMP Link State poll policy is configured without
  interface scoping, there is no problem - we walk through the
  whole of the ifTable.
  
  To select individual rows from a table, the table index forms
  part of the requested OID, and the ifTable is indexed on
  ifIndex. With interface scoping, the individual in-scope
  instances (the ifIndex values that indicate the rows of
  interest) are added to an additional ncpoller table. When
  querying the target, we request multiple OIDs per SNMP Get
  request, where each OID is one of the base OIDs
  (ifAdminStatus/ifOperStatus) with the appropriate ifIndex
  instance value appended.
  
  There is a small margin in which the poll can be triggered
  before that instance data is available in the ncpoller data.
  When this occurs, the request is incorrectly dispatched without
  the necessary instance suffix. As an SNMP Get request is used,
  there is no such OID available to query. The SNMP Get Request
  contains just the incomplete, instance-less
  ifAdminStatus/ifOperStatus OIDs, and the device responds with a
  NO SUCH NAME error.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ITNM 3.8 poller users. Platform independent.                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * On failback configured SNMP Link state policies, which use   *
  * interface filtering, may start producing alerts reporting    *
  * NOSUCHNAME found  for the monitored interfaces. In the       *
  * default product the symptoms are intermittent and may not    *
  * occur on every occasion.                                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Suggest to upgrade to product version 3.8.0-ITNMIP-FP0007    *
  ****************************************************************
  

Problem conclusion

• The code has been updated such that SNMP Link state and
  Threshold poll policies configure the poller data structures
  with the appropriate data required to build the OIDs prior to
  starting the polling mechanism.
  

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

  TIV NETWK MGR I

• Fixed component ID

  5724S4500

Applicable component levels

• R380 PSN

     UP

• R380 PSY

     UP

• R390 PSN

     UP

• R390 PSY

     UP

• R401 PSN

     UP

• R401 PSY

     UP