IBM Support

EZA0461I PING #ping_number timed out

Question & Answer


Question

After we issue the PING command, why are we getting the message EZA0461I PING: #ping_number timed out ?

Answer

There are various hardware and configuration errors that can cause a PING to time out:

  1. Check the cables to make sure they are set up properly.

  2. For OSA non-QDIO devices:
    a. Verify that OSA addresses coded in the HOME list are the same IP addresses that are in the OAT table.
    b. If running VIPA, the VIPA address must also be in the OAT table.

  3. Verify that DEVICE and LINK statements are correct in the TCPIP.PROFILE.

  4. If PINGing by IP address works, but PINGing by name times out, make sure you are picking up the correct address from your nameserver or local files.

  5. For static routes, verify that the GATEWAY/BEGINROUTES statements are correct in the PROFILE.

  6. If you are running OMPROUTE or OROUTED, verify that they are configured properly and there are no error messages in the logs.

  7. Look at NETSTAT GATE, NETSTAT ROUTE and NETSTAT DEVLINK output for any errors regarding the device or routing information.

NOTE: For OSA devices, if you are expecting the stack to act like a router and forward packets, you must configure this accurately. For non-QDIO devices, define this in OSA/SF. For QDIO, use the PRIRouter parameter on the DEVICE statement.

See also Table 10. Diagnosis of a timeout in the IP Diagnosis manual.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"","Version":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Product Synonym

ZOSCS COMMSERVER

Document Information

Modified date:
18 July 2017

UID

dwa1387430