NETSTAT HOME Only Reports Primary Address
APAR Identifier ...... PQ44430 Last Changed ........ 01/06/27
NETSTAT HOME ONLY REPORTS PRIMARY ADDRESS
Symptom ...... IN INCORROUT Status ........... CLOSED PER
Severity ................... 4 Date Closed ......... 01/02/08
Component .......... 5735FAL00 Duplicate of ........
Reported Release ......... 320 Fixed Release ............ 999
Component Name TCP/IP V2 FOR V Special Notice HIPER
Current Target Date .. Flags RESTART/BOOT/IPL
SCP ................... FUNCTIONLOSS
Platform ............
Status Detail: SHIPMENT - Packaged solution is available for
shipment.
PE PTF List:
PTF List:
Release 3A0 : UQ51533 available 01/02/21 (1000 )
Release 320 : UQ51534 available 01/02/21 (0101 )
Parent APAR:
Child APAR list:
ERROR DESCRIPTION:
Customer is using TCP/IP FL320. The HOME statement has been
specified in the TCP/IP server configuration file (PROFILE
TCPIP) with multiple addresses for the same link:
HOME
9.130.249.38 VCTC8
9.130.249.39 VCTC8
The NETSTAT HOME command reports only the primary address
(first address listed):
netstat home
VM TCP/IP Netstat Level 320
Home address list:
Address Link
------- ------
9.130.249.38 VCTC8
Customer states that the correct output (for multiple Home
addresses) was reported by prior VM TCP/IP releases (for
example, TCP/IP FL310. This has been confirmed by IBM support.
LOCAL FIX:
None.
Additional Symptom:
DHCPD will only supply IP addresses in the subnet of the first
HOME statement if multiple HOME statements are coded for the
same LINK.
PROBLEM SUMMARY:
****************************************************************
* USERS AFFECTED: All users of VM TCP/IP FL320 and Level 3A0 *
****************************************************************
* PROBLEM DESCRIPTION: When multiple IP addresses are defined *
* for the same link, only the first *
* entry is reported by NETSTAT HOME. *
****************************************************************
* RECOMMENDATION: APPLY PTF *
****************************************************************
The TCP/IP stack maintains a HOME list that contains the IP
address, and link control block (LCB) address.
When the HOME list is searched, the default home entry is
determined by comparing the LCB address of the current list
entry to the LCB address of the default home entry.
However when multiple IP addresses are assigned to the same
link and the name of the link happens to be the default link
(either the first home entry in the HOME list or via the
PRIMARYINTERFACE statement), the LCB address check will match,
and the entry is skipped from being added to the HOME list even
though its address is different.
For example, in AdrHomeList() in TCPARSE, a list is created
from the stack's HOME list. The default home entry is placed
first in the new list. Then each entry from the HOME list
is moved to the new list. A check is made to bypass adding
duplicate default home entry in the home list by checking the
LCB address of each entry to the LCB address of the default
home entry.
The result is that all entries with the same LCB addresses
as the default home are erroneously skipped. In the case where
a same link name is assigned to multiple IP address and it is
the default home entry link, only the primary link is displayed
by the NETSTAT HOME command.
PROBLEM CONCLUSION:
Whenever a check is made for the default home entry during a
HOME list search, both the LCB address and the IP address are
compared and added to the HOME list as long as one of the
condition is not true.
TEMPORARY FIX:
COMMENTS:
MODULES/MACROS: TCIPDOW TCPARSE TCPIP
SRLS: NONE
RTN CODES:
CIRCUMVENTION:
MESSAGE TO SUBMITTER:
|
