Direct links to fixes
4.1.1-TIV-ITNMIP-Linux-FP0002
4.1.1_README_NLS_FP0002
4.1.1_README_FP0002
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
4.1.1_README_NLS_FP0001
4.1.1_README_FP0001
4.1.1-TIV-ITNMIP-Linux-FP0001
IBM Tivoli Network Manager IP Edition 3.9.0 Fix Pack 5, 3.9.0-TIV-ITNMIP-FP0005
IBM Tivoli Network Manager IP Edition 4.1.1 Fix Pack 2, 4.1.1-TIV-ITNMIP-FP0002
APAR status
Closed as program error.
Error description
All devices that go through the BuildContainment stitcher and are put through AddAvayaEntityContainment stitcher (when the Avaya agent is enabled) regardless of whether the devices are Avaya. Most non comms devices such as servers wont have chassises, containers or vlans (chassisReturn, containersReturn, vlanInterfaceReturn) so are processed and survive those portions of the stitcher. However, some servers that are processed by the avayaInterfaceReturn section produce the CRivStitcherRuleNested.cc log error when interfaceEntityName (m_IfName) evaluates to NULL when MatchPatterned against slot / port * the AddAvayaEntityContainment.stch stitcher is inefficient as it processes ALL devices for chassis,containers,interfaces,vlans * MatchPattern does not gracefully handle null values * interfaceEntityName should be checked for NULL prior to matching to prevent the stitcher erroring and terminating without completion
Local fix
if (validAvayaEntityAgent <> NULL) { Record avayaReturn = RetrieveSingleOQL ( "SELECT m_ExtraInfo->m_rcChasNumSlots FROM AvayaPhysicalInventory.returns WHERE ( m_UniqueAddress = eval(text,'$workAddress') AND m_ExtraInfo->m_rcChasNumSlots <> NULL );" ); if (avayaReturn <> NULL) { // Add Avaya Entity containment ExecuteStitcher( 'AddAvayaEntityContainment' , 'AvayaPhysicalInventory', baseName, workAddress , baseAddress ); } delete avayaReturn; }
Problem summary
**************************************************************** * USERS AFFECTED: * * ITNM-IP 3.9 on all platform, i.e. Windows, Linux, Solaris * * and AIX * **************************************************************** * PROBLEM DESCRIPTION: * * multiple occurances of the below in ncp_disco.DOMAIN.trace * * * * 2014-10-09T12:54:43: Warning: W-RIV-002-139: [5t] * * CRivStitcherRuleNested.cc(240) The following stitcher rule * * failed to complete correctly. Rules List in stitcher * * AddAvayaEntityContainment * **************************************************************** * RECOMMENDATION: * * Upgrade to ITNM-IP | fix pack | 3.9.0-ITNMIP-FP0005 * **************************************************************** All devices that go through the BuildContainment stitcher and are entering AddAvayaEntityContainment stitcher (when the Avaya agent is enabled) regardless of whether the devices are Avaya.
Problem conclusion
To perform a check on the record before calling AddAvayaEntityContainment stitcher in the BuildContainment stitcher. This would prevent those non-avaya devices from entering the AddAvayaEntityContainment stitcher.
Temporary fix
Comments
APAR Information
APAR number
IV65963
Reported component name
TIV NETWK MGR I
Reported component ID
5724S4500
Reported release
390
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-10-17
Closed date
2014-11-03
Last modified date
2014-11-03
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
R411 PSN
UP
R411 PSY
UP
Document Information
Modified date:
03 November 2014