Re: gateway unreachable

[Bryan Dietz <BDietz@xxxxxxxxxx>]

I think you may have the same MAC (Local adapter)  address.  This can
happen after a migration.

Do a DSPLIND on each system.  If they are the same vary off one of the line
and change it.



----------------------------
Bryan Dietz
Aktion Associates

midrange-l-bounces@xxxxxxxxxxxx wrote on 12/15/2004 07:46:43 AM:

> Hi all!
>
> I have a new i520 and a old 170 in the same lan (subnet 255.255.255.248)
>
> My new has ip number 192.14.43.139 255.255.255.248 V5R3M0
> My old has ip number 192.14.43.138 255.255.255.248 V5R2M0
>
> Both has *DFTROUTE        *NONE            192.14.43.137    *NONE
> (a cisco router).
>
> If i IPL my new i520, the i get on my old 170, gateway unreachable. See
> below.
> After 5 second i get gateway now reachable. See below
>
> Any sugestion for my problem?
>
>
>
> Msg  . . :   TCP/IP gateway 192.14.43.137 unreachable.
> Cause . . . . . :   TCP/IP gateway 192.14.43.137 is no longer reachable
> from
>   this system. Connections routed through gateway 192.14.43.137 may fail
> if no
>   other route to the connection destinations can be found.
>
> Recovery  . . . :   If the problem persists then contact your network
>
>   administrator. If gateway 192.14.43.137 becomes available again another
>
>   message will be posted to indicate the gateway is now reachable.
>
>
>
> Msg  . . :   TCP/IP gateway 192.14.43.137 now reachable.
> Cause . . . . . :   TCP/IP gateway 192.14.43.137 is now reachable from
> this
>   system.  It was previously indicated that this gateway was unreachable,
> but
>   the gateway has now become available again.
>
> Recovery  . . . :   Informational message.
>
>
> Regards
> Jan  Rockstedt
>