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
3.9.0.4-TIV-ITNMIP-CORE-OpenSSL-Windows-IF0001
3.9.0.4-TIV-ITNMIP-GUI-Windows-IF0001
3.9.0.4-TIV-ITNMIP-GUI-Window-IF0001
3.9.0.4-TIV-ITNMIP-GUI-Unix-IF0001
3.9.0.4-TIV-ITNMIP-CORE-OpenSSL-zLinux-IF0001
3.9.0.4-TIV-ITNMIP-CORE-OpenSSL-Solaris-IF0001
3.9.0.4-TIV-ITNMIP-CORE-OpenSSL-Linux-IF0001
3.9.0.4-TIV-ITNMIP-CORE-OpenSSL-AIX-IF0001
3.9.0.4-TIV-ITNMIP-zLinux-CORE-IF0001
3.9.0.4-TIV-ITNMIP-Windows-CORE-IF0001
3.9.0.4-TIV-ITNMIP-Solaris-CORE-IF0001
3.9.0.4-TIV-ITNMIP-Linux-CORE-IF0001
3.9.0.4-TIV-ITNMIP-AIX-CORE-IF0001
3.9.0.4_README_NLS_IF0001
3.9.0.4_README_GUI_IF0001
3.9.0.4_README_CORE_OpenSSL_IF0001
3.9.0.4_README_CORE_IF0001
IBM Tivoli Network Manager IP 3.9.0.4 Interim Fix 1, 3.9.0.4-TIV-ITNMIP-IF0001
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
The list of nodes with outstanding ping requests, indexed by request sequence ID and containing a pointer to a handler for the response is not being handled correctly. When the response comes back in the request sequence ID is removed from the list. This list contains a bunch of invalid entries, either from sequence numbers that were allocated but never used or from entries that were never properly removed after the operation was done. When Poller starts to create a request it adds the Ping request to this nodes list, if the sequence ID is already contained within the list it assumes the data in the list is valid. The ping goes out, comes back, and the handler is looked up from this list. No valid handler is actually defined in the list and so we core. Plan to add code to replace stale entries in this list.
Local fix
In one case, IPv6 interfaces were scheduled for polling, but there was no IPv6 interface defined on the virtual machine server. If that is not the case, then there is no apparent work around.
Problem summary
**************************************************************** * USERS AFFECTED: * * ITNM user who are running core on a system that does not * * support IPv6, but they are attempting to do IPv6 ping * * polling. * **************************************************************** * PROBLEM DESCRIPTION: * * ITNM user who are running core on a system that does not * * support IPv6, but they are attempting to do IPv6 ping * * polling. The list of nodes with outstanding ping requests * * gets cluttered with bad entries from the IPv6 requests. * * Over time this can cause poller to fail. * **************************************************************** * RECOMMENDATION: * * fix pack | 3.9.0-ITNMIP-FP0005 * * | fix pack | 4.1.0-ITNMIP-FP0001 * * | fix pack | 3.9.4-ITNMIP-IF0001 * ****************************************************************
Problem conclusion
Poller will not manage this list better when IPv6 socket is bad
Temporary fix
disable IPv6 polling if poller is running on IPv4 only system.
Comments
APAR Information
APAR number
IV60293
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-05-09
Closed date
2014-05-27
Last modified date
2015-04-13
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
R410 PSN
UP
R410 PSY
UP
R411 PSN
UP
R411 PSY
UP
Document Information
Modified date:
13 April 2015