Message DTCRTD4918E Continually Issued to ROUTED Console
APAR Identifier ...... PQ85067 Last Changed ........ 04/04/05 MESSAGE DTCRTD4918E CONTINUALLY ISSUED TO ROUTED CONSOLE Symptom ...... IN INCORROUT Status ........... CLOSED PER Severity ................... 3 Date Closed ......... 04/04/02 Component .......... 5735FAL00 Duplicate of ........ Reported Release ......... 440 Fixed Release ............ 999 Component Name TCP/IP V2 FOR V Special Notice Current Target Date .. Flags SCP ................... Platform ............ Status Detail: PACKAGING - Solution is being packaged for shipment. PE PTF List: PTF List: Release 440 : PTF UQ87029 not available yet Parent APAR: Child APAR list: ERROR DESCRIPTION: User migrated to z/VM R440 from R430 and reports the RouteD console is filling up with messages: DTCRTD4882I DATE/TIME: DTCRTD4918E rtchange: SIOCDELRT ioctl failed No such process (ESRCH) . Tracing the problem indicates that known routes are being deleted by mistakes with message: DTCRTD4954I X minute timer expired for route RouteD tries to delete the routes multiple times causing the above messages to fill the console. LOCAL FIX: Circumvention is available contact VM TCPIP Support. PROBLEM SUMMARY: **************************************************************** * USERS AFFECTED: All users of RouteD * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: APPLY PTF * **************************************************************** Users see RIPv1 routes repeatedly being added to the routing table. These routes expire after 3 minutes. When RouteD tries to change the metric of these routes to 16, an error occurs. The following messages are seen many times: DTCRTD4954I 3 minute timer expired for route to 10.10.10.10 DTCRTD4889I CHANGE metric destination 10.10.10.10, router xx.xx.xx.xx from 2 to 16 DTCRTD4918E rtchange: SIOCDELRT ioctl failed In addition, the RouteD internal routing table contains duplicate entries. PROBLEM CONCLUSION: When RouteD gets a RIPv1 packet and is processing the individual routes, it calls rtlookup to see if the route is already known. The rtlookup routine is not finding the match, so the same route will be added many times. The rtlookup routine has been changed to correctly handle RIPv1 packets. TEMPORARY FIX: COMMENTS: MODULES/MACROS: ROUTED RTIF RTINPUT RTOUTPUT RTSTART RTTABLES SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: