IV22660: NCO_P_NCPMONITOR HUP

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.9 Linux.
  
  PROBLEM DESC:
  
  When sending the HUP signal to the nco_p_ncpmonitor probe with
  
  ITNM  version 3.9, the probe responds to this signal by
  reconnecting to the   objectserver. The objectserver reports
  this by two ConnectionWatch events. However, the ConnectionWatch
  disconnection event (problem event) is often send one second
  later than the ConnectionWatch connection event   (resolution
  event) when the ITNM probe reponds to the HUP signal. Because
  LastOccurrence of the resolution ConnectionWatch event is
  earlier than the problem ConnectionWatch, the generic clear
  trigger  doesn't clear the problem ConnectionWatch event.
  
  This behavior is noticed so far only with the ITNM probe when
  it responds to the HUP signal.For other Omnibus probe that we
  operate, the HUP respond of the probe
  doesn't have this effect.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All ITNM 3.9 Users                                           *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The monitor probe, nco_p_ncpmonitor, will re-read the rules  *
  * file ($NCHOME/probes/<platform>/nco_p_ncpmonitor.rules) upon *
  * SIGHUP.                                                      *
  *                                                              *
  * When processing a HUP signal, a disconnection event is       *
  * received by Omnibus after a new connection event. This       *
  * leaves the alert in a Problem state, as it does not get      *
  * cleared (as the resolution is received before the            *
  * corresponding Problem).                                      *
  * This does not happen with other probes.                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * upgrade to | fix pack | 3.9.0-ITNMIP-FP0004                  *
  ****************************************************************
  

Problem conclusion

• The probe had a custom signal handler for HUP signals. This
  creates a new connection and uses that to read the rules file.
  

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

• R410 PSN

     UP

• R410 PSY

     UP