(I am trying this email again, been having some
problem posting)

Alan said:
> 3. DEFINE VSWITCH, specifying one or more available OSAs.  Those OSAs (a)
> SHOULD NOT be shared with any other stack or LPAR, and (b) MUST all go to
> the same LAN segment.

Question 1:
I want to move to VSWITCH for the double-OSA failover
capability. But I have 2 VM LPARs, and 2, not 4, OSAs.

Assuming this picture: 
(Richard: Please use monospace fon, or paste into Notepad) :-)

+---------------+---------------+
|  lpar a       |  lpar b       |
|               |               |
|               |               |
| VMtcp a       | VMtcp b       |
+-----------+---+----+----------+
            |  OSA1  |
            +--------+
                |
                |
========LAN=10.0.0.0/16==========

Where tcp-a is 10.0.0.12, and tcp-b
is 10.0.0.7, and today they share the
same (single) OSA1.

If I put a VSWITCH in lpar-a, using both
OSA1 and OSA2, what do I do with lpar-b?
Can I really not put a VSWITCH in each LPAR
using the same pair of OSAs?

Question 2: This question is independent of the first one

(This is a rehash of a question that went unanswered a year ago -
http://listserv.uark.edu/scripts/wa.exe?A2=ind0707&L=ibmvm&D=0&F=P&T=0&X=64AA48769B3D5443B0&Y=shimonl%40iname.com&P=18992&F=

Is there any problem with VMtcp-a, with IP 10.0.0.12,
acting as a virtual router to a virtual machine in its
LPAR, connected to it by a CTC?
If my network routes traffic to
10.1.2.2 via 10.0.0.12, will the VSWITCH OSA give that
traffic to VMtcp-a to deal with? At the time I had experimented
with this, but it had failed. I do not remember getting any
ideas why, and the archives don't show any answer.

Thanks,
Shimon


--
************************************************************************
Shimon Lebowitz                mailto:[EMAIL PROTECTED]
VM System Programmer           .
Israel Police National HQ.    
Jerusalem, Israel              phone: +972 2 542-9877  fax: 542-9308
************************************************************************

Reply via email to