IV39428: ITNM GUI CONSTRUCTS WRONG FILTER FOR ALERT VIEWS

IBM Tivoli Network Manager IP 3.9.0 Fix Pack 4, 3.9.0-TIV-ITNMIP-FP0004
IBM Tivoli Network Manager IP 3.9.0.3 Interim Fix 1, 3.9.0.3-TIV-ITNMIP-IF0001
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 GUI constructs wrong filter for Alert views. When opening
  the AEL from the Network View the creation filter is incorrect
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * In some cases there is a mismatch between the status in the  *
  * Network View Tree and the devices in the Network View        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * | fix pack | 3.9.0-ITNMIP-FP0004                             *
  ****************************************************************
  I. Major view contains devices with critical status
  An 'Alert' view is defined with the following SQL filter (by
  design):
  
    <filtered id="Major" label="Major" connectivity="ipsubnets"
  endNodes="true">
                   <filter schema="ncmonitor" table="activeEvent"
  filter="Severity=4 and Acknowledged=1"/>
    </filtered>
  
  The clause Severity=4means that the view would pick every device
  which has at least one alert with severity 4. This however does
  not mean that the view would be picking only devices which has
  at least one alert with severity 4 and no other alerts. For
  example a Major view can pick the following two devices because
  they contain at least one alert with major severity:
  
  Device_1 which has: 1 major and 1 critical alerts
  
  Device_2 which has: 1 minor and 1 major alerts
  
  
  
  Once displayed on the graph/map, the topology server would pull
  the status and colour the devices with the highest severity
  respectively:
  Device_1 would be coloured with critical status as the device
  contains major as well as critical alerts.
  Device_2 would be coloured with major status as the alert with
  highest
  severity for this device is major.
  
  
  
  If you would like to have a view displaying devices having only
  major alerts and no others, you could extend the SQL filter by
  constructing a sub query to eliminate the rest of the devices.
  
  
  
  II. AEL for a device from Major view contains other than major
  alerts.
  When the AEL is opened from the right click tools of a device in
  a view (regardless of the type of the view), the AEL will
  contain all events for the particular device. The 'Alert' views
  are no exception to this design and the name of the tool
  accurately reflects the expected behaviour 'Show Events' and not
  'Show Critical Events' for example.
  
  Lets take the previous example of a Major view with the two
  devices. If we use the 'Show Events' right click tool on a
  Critical coloured device in a Major view, it would be
  inconsistent if the AEL displays only the major alerts and not
  the ones which caused the critical colouring of the device.
  

Problem conclusion

• | fix pack | 3.9.0-ITNMIP-FP0004
  

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

• R390 PSN

     UP

• R390 PSY

     UP

• R401 PSN

     UP

• R401 PSY

     UP