IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 18 (7.1.0-TIV-NCI-FP0018)

Download Description

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

WARNING!
Log4j vulnerabilities (CVE-2021-44228,CVE-2021-45105,CVE-2021-45046 and CVE-2021-44832) affect this fix pack.
IBM strongly recommends upgrading to a refreshed fix pack starting at fix pack 23 or later. If upgrading to a refreshed fix pack is not possible, 
you can apply interim fix 10 (7.1.0-TIV-NCI-IF0010).

During the upgrade, the previous versions of Log4j will be moved to a backup location for rollback purposes. These versions are not actively used
by the product however security scans may continue to flag the backup copy. If the files must be removed but the rollback capability is still required, an archive of the backup location should be created before deleting the log4j files.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Before installing or upgrading IBM Tivoli Netcool/Impact 7.1.0.18, refer to the Following documentation:

• https://www.ibm.com/docs/en/tivoli-netcoolimpact/7.1
• Download attached package to review readme file. Review list of enhancements, pre-req, installation instructions and known issues in IBM Tivoli Netcool/Impact
  7.1.0 Fixpacks.
• Review Known Issues section in Fix Pack 18 release page.

A change introduced by this Fix Pack might negatively affect existing product function.
1. Refer to APAR IJ22703 for a description of the problem produced by APAR IJ18173 and the corrective action.
2. Refer to APAR IJ24991 for a description of the problem and corrective action.
3. Refer to APAR IJ24935 for a description of the problem produced by APAR IJ20837 and the corrective action.
4. Refer to APAR IJ25145 for a description of the problem produced by APAR IJ17322 and the corrective action.
5. Refer to APAR IJ28513 for a description of the problem and corrective action.
6. Refer to APAR IJ28824 for a description of the problem produced by APAR IJ18823 and the corrective action.
7. Unable to save ImpactDB data source, please refer to doc https://www.ibm.com/support/pages/node/6407084 for a description of the problem.
    The issue is fixed with APAR IJ30330 planned for 7.1.0-TIV-NCI-FP0021.
8. The impact-http-headers.jar is missing from server only installs.
    The issue is fixed with APAR IJ39619 planned for 7.1.0-TIV-NCI-FP0026.
*********************************************************************************************************************

For details of an individual APAR, go to https://www.ibm.com/support/home/ then enter the APAR name/# in "Search Support" then select search.

The following Netcool/Impact APARs are delivered with Fix Pack 18:

• IJ10104: IN NOI EVENT ANALYTICS, NEED TO CHECK RESOURCE COLUMN IN RESTRICT FIELDS OF PROCESSRELATEDEVENTPATTERNS EVENTREAD
• IJ18211: REMOTETBSMSHELL THROWS AN EXCEPTION WHEN RUN IN TBSM IMPACT SERVER
• IJ18135: RFE: NOI: EVENT ANALYTICS - Event Analytics not generating patterns when not using the Global settings for Event Identity
• IJ18352: WEBSERVICE LISTENER ALLOW FILTER TO SUBSTITUTE THE INCOMING SOAPACTION HEADER
• IJ18496: ORACLE ERRORS PRODUCED IF TYPE_SCROLL_SENSTIVE IS ENABLED. THE QUERIES RUN ON NETCOOL & DATA'S RETURNED BUT ERRORS
               ARE ANNOYING
• IJ18576: NOT ABLE TO ASSIGN IMPACT ROLE TO MULTIPLE USERS/GROUPS BY RUNNING ONE COMMAND
• IJ18759: THE JMS LISTENER SERVICE STOPS WHEN FAILBACK OCCURS
• IJ19615: REPORT_PURGEDATA POLICY DOES NOT CLEAR OLD RECORDS IN SOME CASES
• IJ19623: ERROR ADDING IMPACT AS A CONSOLE INTEGRATION FOR DASH, WHEN USING FEDERATED LDAP REPOSITORIES FOR AUTHENTICATION
• IJ19712: SETNAMESERVER SCRIPT REMOVES SOME SSL SETTINGS SET BY CONFIGIMPACTSSL
• IJ19797: NETCOOL/IMPACT 7.1 FIX PACK UPGRADE RESETS NOI SERVICES WITH AUTOSTART=FALSE BACK TO AUTOSTART=TRUE
• IJ19848: MWM NOT WORKING CORRECTLY FOR 1ST HOUR OF DAY WHEN DST IN FORCE
• IJ19908: COMMANDLINESERVICE DOES NOT ALWAYS STAY RUNNING AFTER FAILOVER
• IJ19950: MWM GUI SELECT ALL WILL SELECT FILTERED OUT ENTRIES
• IJ20045: IMPACT CONTAINS DIFFERENT VERSIONS OF LOG4J JAR FILE
• IJ20073: PERFORMANCE ISSUE SAVING A PATTERN WHEN A CONFIGURATION HAS A LARGE NUMBER DIFFERENT EVENT TYPES IN RELATED EVENTS
• IJ20096: IMPACT SECONDARY SERVER(S) CAN TAKE A LONG TIME TO START IF MANY FILES IN $IMPACT_HOME/DB/DERBY DIRECTORY
• IJ20108: "ERROR [DATAMODELUIRESOURCE] DATASOURCE WITH NUMBER NN DOES NOT EXIST" AFTER IMPACT FIX PACK
• IJ20127: FILE IMPACTDAP.PROPERTIES REPLACED BY STANDARD FILE WHEN FP INSTALLED
• IJ20247: SNMPGETACTION NOT PASSED VALID 'VARIDLIST' IN JAVASCRIPT POLICY
• IJ20275: CPU HIGH USAGE DUE TO BLOCKED THREADS
• IJ20535: CONFAUTH4LDAP SHOULD CHECK THAT OMNNIBUS AUTH IS NOT SET
• IJ20584: RFE: SELF MONITORING WARNINGS ABOUT MEMORY ARE NOT ALWAYS A PROBLEM
• IJ20694: BLOCK CONCURRENT DELETION OF RBA TRIGGERS FROM CORRUPTING EVENT READER PROPS FILE
• IJ20722: CUSTOM DATA TYPES LINKED TO THE XMLDSAMEDIATORDATASOURCE NOT EXPORTED/IMPORTED
• IJ20816: Seasonality Rules. DAY OF WEEK and HOUR only, does not work when the current hour is after start hour
• IJ20817: Seasonality Rules. Deadlock reading NOI.DEFAULTVALUES
• IJ20837: CONFAUTH4LDAP.SH COMPLETES 'BUILD SUCCESSFUL' WHEN IT FAILED DUE TO MISSING LDAPBINDPASS IN IMPACTDAP.PROPERTIES
• IJ20916: MWM POLICY UNNECESSARILY SETS SUPPRESSESCL TO 6 FOR EVENTS
• IJ20955: DELAY OCCURS IN SECONDARY.PREFERREDPRIMARY BECOMING PRIMARY
• IJ21003: IPL FUNCTION CALL YIELD DIFFERENT OUTCOME WHEN READING FROM CSV FILE
• IJ21037: ENABLE SNMPSETACTION TO PROCESS INTEGER ARGUMENTS IN THE VALUELIST
• IJ21089: TO ENABLE IMPACT MWM TIMEZONE LIST TO BE CUSTOMIZABLE
• IJ21182: CONVERTXMLTOIMPACTOBJECTS FUNCTION OF IMPACT POLICY DOES NOT HANDLE DUPLICATE XML TAG
• IJ21188: IMPACT 7.1.0.17 SLOW LOGIN
• IJ21202: EVENT READER SKIPS EVENTS DURING AN EVENT FLOOD
• IJ21425: IMPACT EMAIL READER SERVICE GENERATES MULTIPLE WARN MESSAGES IN IMPACTSERVER.LOG
• IJ21615: IMPACT LDAP ENABLEMENT SCRIPT DOES NOT ADD ADDITIONAL ENTRY INTO LDAP REGISTRY XML FILE
• IJ21732: FLEXIBILITY FOR TREEMAP WIDGET BACKGROUND COLOR
• IJ21808: PRIMARY IMPACT SERVER DOES NOT WAKE-UP AND PING SECONDARIES
• IJ21987: RFE: COMMAND LINE TOOL NEEDS ADDITIONAL OPTIONS FOR READER FILTERS
• IJ21989: NULLPOINTEREXCEPTION IS POSSIBLE WHILE RETRIEVING EVENT READER STATE
• IJ22067: NETCOOL/IMPACT 7.1 FP 16 - CONNECTION COUNT EXCEEDS THE DATABASE MAX SQL CONNECTION VALUE
• IJ22256: INCORRECT IMPACTDB REPLICATION IN 3+ NODE CLUSTER
• IJ22411: ADD TIMEOUT PROPERTIES FOR GETHTTP CONNECTION CREATESOCKET WHICH ARE NECESSARY FOR JAVA APAR IJ22333
• IJ23080: RELATED EVENT PATTERN NOT CORRELATES EVENT BY SECONDARY IMPACT INSTANCE

• IJ18823: SECURITY VULNERABILITY DUE TO ANJULARJS LIBRARY FILE
• IJ20163: SECURITY APAR UPGRADE TO LATEST APACHE COMMONS BEANUTILS IN IMPACT
• IJ21951: SECURITY APAR UPGRADE TO LATEST APACHE LOG4J V2 IN IMPACT 710
• IJ22540: SECURITY APAR UPGRADE TO IBM SDK 8.0.6.5 IN IMPACT 710 FP18
• IJ22733: SECURITY APAR UPGRADE TO APACHE COMMONS FILEUPLOAD IN IMPACT 710

• IJ10384: NOI EVENT ANALYTICS - RELATED EVENT PATTERN WITH MULTIPLE RESOUCE COLUMNS DOES NOT CORRELATE EVENTS AS EXPECTED
• IJ13101: REGULAR EXPRESSION AND NAME SIMILARITY FEATURE
• IJ17915: NETCOOL/IMPACT - IMPACT.SERVER.MAXLOGSIZEBYTES AND IMPACT.SERVER.MAXBACKUPINDEX UNDER TBSM_SERVER.PROPS NOT
               HONORED
• IJ18160: NETCOOL/IMPACT - DOCUMENT FOR RESTORATIVE SVN COMMANDS
• IJ18496: ORACLE ERRORS PRODUCED IF TYPE_SCROLL_SENSTIVE IS ENABLED. THE QUERIES RUN ON NETCOOL & DATA'S RETURNED BUT ERRORS
              ARE ANNOYING
• IJ18576: NOT ABLE TO ASSIGN IMPACT ROLE TO MULTIPLE USERS/GROUPS BY RUNNING ONE COMMAND
• IJ18759: THE JMS LISTENER SERVICE STOPS WHEN FAILBACK OCCURS
• IJ19614: ENABLEAUDIT PROPERTIES ARE NOT DOCUMENTED
• IJ19623: ERROR ADDING IMPACT AS A CONSOLE INTEGRATION FOR DASH, WHEN USING FEDERATED LDAP REPOSITORIES FOR AUTHENTICATION
• IJ19849: EVENT ANALYTICS CONFIGURATION BLANK SCREEN IF DEFAULT FIELDS ARE MISSING
• IJ20059: DOCUMENTAION REGRADING THE "IMPACT ADMIN" USER, WHEN SETTING UP FEDERATED LDAP REPOSITORIES ON IMPACT 7.1
• IJ20162: IMPACT DERBY STACK OVERFLOW
• IJ20174: SPECIAL CHARACTER DOCUMENTATION WHICH CHARACTERS NEED ESCAPING REGEX/SQL
• IJ20317: IMPACT 7.1 SINGLE EQUAL OPERATOR CAN BE USED WITHIN IF() STATEMENTS FOR IPL POLICIES
• IJ20584: SELF MONITORING WARNINGS ABOUT MEMORY ARE NOT ALWAYS A PROBLEM
• IJ20837: CONFAUTH4LDAP.SH COMPLETES 'BUILD SUCCESSFUL' WHEN IT FAILED DUE TO MISSING LDAPBINDPASS IN IMPACTDAP.PROPERTIES
• IJ20913: EVENT ANALYTICS ACKNOWLEDGED FIELD DOES NOT EXIST IN HISTORY DB CAUSES ERRORS
• IJ20949: DOCUMENT THAT POLICY LOGGER PROPERTIES CAN CAUSE HIGH LOAD ON THE IMPACT SERVER ESPECIALLY WITH NOI EXTENSION
• IJ21037: ENABLE SNMPSETACTION TO PROCESS INTEGER ARGUMENTS IN THE VALUELIST
• IJ21443: IMPACT 7.1 DOCUMENTATION CHANGES FOR ADDING SIGNED CERTIFICATES TO NETCOOL/IMPACT GUI SERVER
• IJ21987: RFE: COMMAND LINE TOOL NEEDS ADDITIONAL OPTIONS FOR READER FILTERS

3.0 Troubleshooting Netcool Impact 7.1 > General issues 

 - You now can (if needed) reset the Derby DB to a default state (in a NOI installation); by using the following steps:

  1.Find appropriately named ImpactDB_NOI_FP18.zip file located in

    $IMPACT_HOME/install/dbcore.

  2.Stop all ImpactServers in the cluster (primary and secondary that run Derby DB).

  3.Backup/Remove the existing ImpactDB directory structure in $IMPACT_HOME/db/<ServerName>/derby.

  4.Copy the zip file found in step 1 to $IMPACT_HOME/db/<ServerName>/derby and unzip it.

  5.Start Impact Server primary, let it fully initialize and start, and now start secondary server and let it re-sync from the primary.

 - Enabling LDAP Authentication

   When editing the $IMPACT_HOME/install/security/impactdap.properties before enabling LDAP  Authentication, ensure the version of the impactdap.properties

   is from the latest install! 

   * Do not copy a props file from a different/older FixPack. 

   * Ensure to only edit the properties, do not delete/remove any of the properties before running the $IMPACT_HOME/install/security/confAuth4LDAP.sh 
     script

   * If setting up new LDAP authentication with an Active Directory LDAP server on an Impact FP18 install, the following 5 properties will need to be un-commented in impactdap.properties
     # Custom LDAP Search Filtering (Default values for Microsoft Active Directory)
     LDAPUserFilter="(&(sAMAccountName=%v)(objectcategory=user))"
     LDAPGroupFilter="(&(cn=%v)(objectcategory=group))"
     LDAPUserIdMap="user:sAMAccountName"
     LDAPGroupIdMap="*:cn"
     LDAPGroupMemberIdMap="memberof:member"

- The following applies only to Netcool/Impact Clients with Netcool Operations Insight (NOI) - and only for those with Existing configurations:
After upgrading to Netcool/Impact 7.1.0 FP13 (and above), run through the Wizard; confirm, verify & save the configuration. Refer to: Event Analytics 
Configuration 
1. It is a known issue that custom rollup changes to properties and params files are overwritten. Running through the wizard will repair these.
2. Also for seasonality View, it is advisable to run through the Wizard to make sure the right columns are displayed. Refer to the following to the link, 
for appropriate actions related to "Migration of rollups in Netcool/Impact":
https://www.ibm.com/support/knowledgecenter/SSTPTP_1.4.1/com.ibm.netcool_ops.doc/soc/event_analytics/concept/soc_ea_rollup_migrate.html

- The EventReader service for Seasonality Events is called "ProcessSeasonalityEvents" and it does not (by default) read updated or de-duplicated events. 
"Get updated events" is not selected (by default) in the UI for the "ProcessSeasonityEvents" Service, on the Event Mapping tab. 
The reason for this is due to the wide Filter for the "ProcessSeasonityEvents" Event Reader service. By default, the filter is  set to "1=1". With this wide filter, 
if "Get updated events" was enabled, and Seasonality rules fired, this could lead to an infinite loop. i.e. Seasonality Rules updating events which in turn get 
read by the reader and fire the Seasonality Rules again. The solution is for the Event Mapping Filter to be set, in such a way, as to avoid already processed 
events. i.e. if the Seasonality rules are setting the Service field to "something" then the Event Mapping Filter could be set to restrict these.

- NOI: Impact Event Isolation and Correlation page does not load if non-default cluster name is used (such as NCICLUSTER_Z )
To resolve this issue, perform the following actions:
- stop the Impact GUI server $IMPACT_HOME/bin/stopGUIServer.sh
- copy or rename the file with the correct cluster name. For example:
cp $IMPACT_HOME/opview/displays/NCICLUSTER-EIC_configure.html $IMPACT_HOME/opview/displays/NCICLUSTER_Z-EIC_configure.html
 - restart the Impact GUI server $IMPACT_HOME/bin/startGUIServer.sh
- go to the Event Isolation and Correlation page and confirm the page is displayed without the errors.

 - NOI 1.5: The Event Analytics Configuration wizard reports an Unexpected Token error when the Impact GUI server under the Turkish locale 
Symptom: When loading the Event Analytics configuration page, an "Unexpected token: E" error is reported. Configuration cannot continue.
Root Cause:When the Impact GUI server is running under the Turkish locale, the GUI server is unable to find the contents of the uiproviderconfig directory.
Resolution: Switch to a different locale and restart the Impact GUI server

- Customization made to web.xml is overwritten
Symptom: Any customization made to the web.xml file of a .war file (such as opview.war and netcool.war)  may be overwritten during the upgrade process.
Resolution: Please check the web.xml file after completing the upgrade and reapply the customization. You can find the old customization in the following 
directory. Merge the customization, as appropriate: <backup>/install/gui_backup/<prior-fp name>/wlp/usr/servers/ImpactUI/apps/ImpactUI.ear

- In Impact clustered environment, an open policy cannot be unlocked after FAILOVER occurs
Symptom: On a Primary node cluster, if a policy or service is edited and left opened (in locked/edited mode) and a failover occurs, then the Secondary 
server could potentially show the policy, or service, as being locked by user "default", as seen here: "Error: File etc/NCI_1_<filename> is locked by user: 
default"
Resolution:
1) Stop the acting Primary Impact server 
2) Clear out the following file by removing all un-commented lines: <impact_home>/etc/<impact_server>_versioncontrol.locks
3) Restart the Impact server 

- When Uninstalling Impact, the directory uiproviderconfig may not get deleted
Symptom: When Uninstalling an Impact installation, that has Impact 7.1.0 FP18, the directory uiproviderconfig may not get deleted.
Root cause: A softlink to directory <impact_home>/uiproviderconfig/translation may prevent the deletion of the directory
Resolution: Manually remove the <impact_home>/uiproviderconfig/translation directory