Arrggh - I have guests at both .49 and .50, I evidently included the trace
to .49 (same results).  Strike .50 in my note and replace it with .49 (sorry
for the confusion).

Michael Coffin, VM Systems Programmer
Internal Revenue Service - Room 6527
1111 Constitution Avenue, N.W.
Washington, D.C.  20224

Voice: (202) 927-4188   FAX:  (202) 622-3123
[EMAIL PROTECTED]



-----Original Message-----
From: Rob Schwartz [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 18, 2002 10:21 AM
To: [EMAIL PROTECTED]
Subject: Re: Odd TraceRoute To Linux/390 Guests via VM TCPIP


Hey Michael,

Am I missing something here... What is 152.225.118.49????

Rob

Robert C Schwartz
Technical Services
Boscovs Department Stores LLC
610-929-7387
[EMAIL PROTECTED]

----- Original Message -----
From: "Michael Coffin" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 18, 2002 10:02 AM
Subject: Odd TraceRoute To Linux/390 Guests via VM TCPIP


> (Crossposted on VMESA-L and Linux-VM)
>
> Hi Folks,
>
> I'm in the process of implementing gigabit ethernet for a client and
> am very curious about something.  I have a TCPIP stack on VM (VM/ESA
> 2.4.0) with a dedicated gigabit card at IP address 152.225.118.46.  I
> have a Linux/390 guest virtual machine VCTC coupled to this TCPIP
> virtual machine at IP address 152.225.118.50.  Take a look at the
> traceroute below, when I trace to .46 it's nice and clean.  However
> when I trace to .50 .46 times out.  Any idea what causes this?  VM's
> TCPIP is proxyarping for these guests, by the way.
>
> I:\>tracert 152.225.118.46
>
> Tracing route to 152.225.118.46 over a maximum of 30 hops
>
>   1   <10 ms   <10 ms   <10 ms  152.225.39.2
>   2   <10 ms   <10 ms   <10 ms  152.225.119.194
>   3   <10 ms   <10 ms   <10 ms  152.225.46.36
>   4   <10 ms   <10 ms   <10 ms  152.225.118.46
>
> Trace complete.
>
> I:\>tracert 152.225.118.49
>
> Tracing route to 152.225.118.49 over a maximum of 30 hops
>
>   1   <10 ms   <10 ms   <10 ms  152.225.39.2
>   2   <10 ms   <10 ms   <10 ms  152.225.119.194
>   3   <10 ms   <10 ms   <10 ms  152.225.46.36
>   4     *        *        *     Request timed out.
>   5   <10 ms   <10 ms   <10 ms  152.225.118.49
>
> Trace complete.
>
> Thanks in advance.  :)
>
> -Michael Coffin

Reply via email to