IBM Support

IJ38296: PING TO REMOTE HOST FAILED MSG IN MULTIPATH ROUTE ETHERCHANNELS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as documentation error.

Error description

  • The cause of "PING TO REMOTE HOST FAILED" message could
    be
    that the ping monitoring packet of the EtherChannel
    does not respond within the "Number of Retries"
    in an environment where the ping monitoring packet of
    the connected EtherChannel is trying to communicate via
    the unconnected EtherChannel. In this case the message
    is harmless and does not indicate a real problem but
    it would make it difficult to diagnose a real failure.
    

Local fix

  • a possible workaround would be to use a separate "address
    to ping" for each etherchannel and add a specific
    host route with the right etherchannel interface name
    for the destination IP to the routing table
    

Problem summary

  • PING TO REMOTE HOST FAILED MSG IN MULTIPATH ROUTE ETHERCHANNELS
    

Problem conclusion

  • ping monitoring is not supported in multipath routing
    environments
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ38296

  • Reported component name

    AIX V7.1

  • Reported component ID

    5765H4000

  • Reported release

    710

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-03-08

  • Closed date

    2022-04-05

  • Last modified date

    2022-04-05

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SG11R"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"710","Line of Business":{"code":"LOB08","label":"Cognitive Systems"}}]

Document Information

Modified date:
18 April 2022