When a Device is Disabled, Device Status Stays Ready in NETSTAT DEVLINKS. RouteD Server is Not Informed About the Link Failure
APAR Identifier ...... PQ59871 Last Changed ........ 03/12/22 WHEN A DEVICE IS DISABLED, DEVICE STATUS STAYS READY IN NETSTAT DEVLINKS. ROUTED SERVER IS NOT INFORMED ABOUT THE LINK FAILURE Symptom ...... IN INCORROUT Status ........... CLOSED PER Severity ................... 2 Date Closed ......... 02/06/13 Component .......... 5735FAL00 Duplicate of ........ Reported Release ......... 320 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 : UQ67156 available 02/06/19 (0401 ) Release 320 : UQ67174 available 02/06/19 (1000 ) Release 410 : UQ67177 available 02/06/19 (1000 ) Release 420 : UQ67181 available 02/06/19 (1000 ) Release 430 : UQ67184 available 02/06/19 (1000 ) Parent APAR: Child APAR list: ERROR DESCRIPTION: When a device is physically disabled, TCPIP keeps the device in READY status. ROUTED server is not informed that the link is disabled and keeps its routes via this link. LOCAL FIX: PROBLEM SUMMARY: **************************************************************** * USERS AFFECTED: All z/VM TCP/IP users running RouteD and LCS * * (LAN Channel Station) attached devices. * **************************************************************** * PROBLEM DESCRIPTION: When an LCS attached device becomes * * disabled, the stack fails to downgrade * * the device status from the READY state. * * Since the device remains READY, RouteD * * does not detect the outage and * * continues to keep the device in its * * routing table. * **************************************************************** * RECOMMENDATION: APPLY PTF * **************************************************************** When an LCS device becomes disabled, a PCCAcrtlSTOPlan command is sent to the stack. The stack waits 5 seconds and then restarts the device by issuing a PCCActrlSTRTlan command. Upon completion of the PCCActrlSTRTlan command, the stack fails to interrogate the return code and arbitrarily places the device back into the READY state. When RouteD performs its device scan, there is no indication that a problem has occurred with the device so the routing table remains unchanged. PROBLEM CONCLUSION: The PktProcessControlPacket() routine in module TCPKT has been modified to test the return code received on a PCCActrlSTRTlan command. When the return code is non-zero, the device will be shut down (NOT READY) and an error message will be generated which will present the failing return code. Documentation for this new message will be included in any future updates to the following publication: GC24-6022-00 -- z/VM: TCP/IP Level 430 Messages and Codes - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Chapter 20. TCP/IP Server Messages Page: 314 New Message Text: DTCPKT106E Device <devicename>: Error detected on Start Lan command, PCCActrlRETcode = <nn> Explanation: An error was detected on the Start Lan command System Action: The device is shutdown. User or Operator Response: None System Programmer Response: Verify that the cable for the device is plugged in and that the device is properly configured. If the problem persists, record the displayed error return code and report it to IBM Support Center. TEMPORARY FIX: COMMENTS: MODULES/MACROS: ALLMACRO FPTOPC3 MSTCP TCPIP TCPKT TCPKTC TCTOCLAW TCTOPC3 SRLS: GC24602201 RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: