DCTARP026I ARPIN: Unknown or Invalid Hardware Address


 
 APAR Identifier ...... PQ67471      Last Changed ........ 02/11/11
 DTCARP026I ARPIN: UNKNOWN OR INVALID HARDWARE ADDRESS
 
 Symptom ...... IN IN                Status ........... CLOSED  PER
 Severity ................... 3      Date Closed ......... 02/11/06
 Component .......... 5735FAL00      Duplicate of ........
 Reported Release ......... 420      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 420   : UQ71547 available 02/11/11 (1000 )
 Release 430   : UQ71548 available 02/11/11 (1000 )
 
 Parent APAR:
 Child APAR list:
 
 ERROR DESCRIPTION:
 
 Customer has setup a z/VM system that uses VIPA and MPROUTE for
 network routing.  This host can connect to only other hosts
 that use dynamic routing.  Hosts that rely on static gateway
 routing cannot connect to the z/VM host.
 
 From tracing the problem with a statically-routed remote host,
 it was found that host issued an ARP broadcast for the z/VM
 VIPA address, but the z/VM would not respond.  A "MORETRACE
 ARP" trace showed the request ARP failed with this trace
 message:
 
   DTCARP026I ARPIN: Unknown or invalid hardware address
 
 LOCAL FIX:
 
 PROBLEM SUMMARY:
 ****************************************************************
 * USERS AFFECTED: Users with STATIC gateways to z/VM VIPA      *
 *                 devices.                                     *
 ****************************************************************
 * PROBLEM DESCRIPTION: Users with STATIC gateway statements    *
 *                      to z/VM VIPA addresses are unable to    *
 *                      connect to the VIPA addresses.          *
 ****************************************************************
 * RECOMMENDATION: APPLY PTF                                    *
 ****************************************************************
 When z/VM TCP/IP receives an ARP query for a VIPA address,
 it does not respond. So connections to z/VM VIPA addresses do
 not work.
 
 PROBLEM CONCLUSION:
 TCP/IP was changed to respond to ARP queries for VIPA addresses.
 
 TEMPORARY FIX:
 
 COMMENTS:
 
 MODULES/MACROS:   TCARP    TCPIP
 
 SRLS:      NONE
 
 RTN CODES:
 
 CIRCUMVENTION:
 
 MESSAGE TO SUBMITTER: