MPROUTE Routing Table Not Updated When CTC Link is Started
APAR Identifier ...... PQ52180 Last Changed ........ 01/10/31 MPROUTE ROUTING TABLE NOT UPDATED WHEN CTC LINK IS STARTED Symptom ...... IN INOUT Status ........... CLOSED PER Severity ................... 3 Date Closed ......... 01/10/23 Component .......... 5735FAL00 Duplicate of ........ Reported Release ......... 3A0 Fixed Release ............ 999 Component Name TCP/IP V2 FOR V Special Notice Current Target Date .. Flags SCP ................... Platform ............ Status Detail: SHIPMENT - Packaged solution is available for shipment. PE PTF List: PTF List: Release 3A0 : UQ59103 available 01/10/30 (1000 ) Release 410 : UQ59104 available 01/10/30 (1000 ) Release 420 : UQ59105 available 01/10/30 (1000 ) Parent APAR: Child APAR list: ERROR DESCRIPTION: Customer has a CTC connection defined between a Linux guest and a VM host, which is connected to a remaining network by two OSA QDIO adapters. The VM TCP/IP host is first initialized, after which the Linux guest is initialized. Following this, PINGs between the Linux and VM hosts succeed, while those between the Linux guest and hosts elsewhere in the network fail. Recycling the VM MPROUTE server machine resolves this situation. Investigating the problem reveals that the VM TCP/IP server is not updating MPROUTE once an ERROR-STATUS condition for the CTC connection has been cleared. LOCAL FIX: PROBLEM SUMMARY: **************************************************************** * USERS AFFECTED: All users of MPRoute * **************************************************************** * PROBLEM DESCRIPTION: The VM TCP/IP stack does not send a * * status update to the MPRoute server * * when an Error-Status condition for * * a CTC connection has been cleared. * **************************************************************** * RECOMMENDATION: APPLY PTF * **************************************************************** The VM TCP/IP stack sends information to the MPRoute server whenever interfaces change state. For most devices, a state change is reflected in the DeviceStatus field of the DCB. For CTC devices, however, the DeviceStatus may indicate that the device is ready but the ErrorStatus flag in the LCB is set to indicate that there is still a problem. PROBLEM CONCLUSION: TCTOCTC has been updated to call the CTCLinkStateChange routine whenever the ErrorStatus changes. This will invoke a call to the LinkStateChange routine in TCMIB. LinkStateChange will check the new ErrorStatus against the old ErrorStatus. If there is a change, an update will be sent to the MPRoute server. TEMPORARY FIX: COMMENTS: MODULES/MACROS: TCPIP TCTOCTC SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: