On Friday, 08/14/2009 at 11:03 EDT, "Kline, Martin"
<[email protected]> wrote:
> Alan said:
> >According to other parts of the query, your Linux guest has registered
> >10.0.102.215 (Layer 3 VSWITCH), which looks fine based on your VM
TCP/IP
>
> >configuration (same subnet, no VLANs). I assume your Linux default
> >gateway is also 10.0.102.4.
>
> >Are you using a VIPA in Linux? I am worried that you have VIPA
> >configured in your Linux guest but you haven't done "vipa add" to
> >register the IP address.
>
> The guest should have been configured as 10.0.219.215, and this has been
>
> done. Result is not much different, though. I still cannot access the
> guest Linux from the network.
>
> With this new info, is the Linux gateway maybe wrong? Should it be
> 10.0.219.1? something else?
Since the VSWITCH is VLAN UNAWARE, the OSA must plugged into an access
port on the switch. Ergo, all users of the OSA are in the same LAN
segment and they are, therefore, in same subnet.
Anything else will result in absolute chaos and annoy your Network People.
Rule #3: Don't annoy Network People.
FYI... Rule #2: Don't annoy Security People.
Rule #1: Don't annoy Chuckie.
Rule #0: Don't annoy the SO
To resolve: Look carefully at the drawing you made of your virtual
network. Does it have Network Person Stamp of Approval on it? If not,
that is the first problem to resolve. Next, compare your configuration to
the picture. If they don't match, you know what to do.
Of course, if you don't have a picture of you what you are trying to
build, see Rule #1.
Alan Altmark
z/VM Development
IBM Endicott
