Over the last few weeks we have determined (without equivocation) that we
are z/VM communications mice.  Communications men or women would have
dispatched the following problem forthwith.

What we are attempting to do is describe our connectivity requirements for
testing zVos to IBM¹s Dallas development center.  I feel as though we are
throwing them somewhat of a curve ball because our environment is not Linux
and not strictly CMS/VM.


Here is what we have:

1. A second level VM system running on the Dallas First level.

2. On that second level system there are two server machines which have to
be able to communicate with a z/Vos management console in Birmingham via
HTTP.

3. On the same machine there are 3 virtual x86 machines that must be reached
from the Birmingham network with RDP and/or VNC over a Specific subnet and
port range.

4. The servers and virtualized machines are on the same VLAN.

5. VPN


Questions:

1. What has to happen on the first level machine to permit access to a
specific subnet and port range on the VLAN of the second level machine?

2. Shouldn't we be able to get away with just having a VSWITCH/VLAN
combination on the second level machine without dedicating an OSA adapter?
Anybody done this in a DR environment.

3.  Would use of a virtual OSA adapter in the second level machine make this
easier or just ratchet the level of complexity?


Thanks
--.  .-  .-.  -.--

Gary Dennis
Mantissa Corporation

Reply via email to