I have the 2 vswitchs (virtual switch) defined. Since the vswitch connected
to the OSA on a particular subnet, and the cloud knows how to get to that
subnet, then the user can connect. Unfortunately, the user has to specify
the IP address of one vswitch or the other. The default route is only going
to route them back via one anyway. I need to take it to the next level, and
keep it simple. I know, but I am due a Christmas miracle.
I have read documentation on this and they all indicate that this can be
done. But none really indicate how.
Mark Post
<[EMAIL PROTECTED]
et> To
Sent by: Linux on LINUX-390@VM.MARIST.EDU
390 Port cc
<[EMAIL PROTECTED]
IST.EDU> Subject
Re: z/VM and Linux Guest VIPA
routing?
12/21/2004 06:06
PM
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
Moving this type of routing outboard of the Linux/390 guests is what
VSWITCH was intended to do (if I remember Alan Altmark's and Vic Cross's
presentations correctly). I strongly recommend taking a look at
implementing VSWITCH, regardless.
Mark Post
-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Peter E. Abresch Jr. - at Pepco
Sent: Tuesday, December 21, 2004 5:53 PM
To: LINUX-390@VM.MARIST.EDU
Subject: z/VM and Linux Guest VIPA routing?
We are running 2 SuSE Linux SP03 in native LPAR mode. We have 3 OSA/e in
qdio mode and 1 OSA/e in non-qdio mode. We run the Quagga routing suite to
broadcast out our VIPA (dummy0) which all users use to access the Linux.
This has worked rather well and allows us to shut down specific OSAs and
network switches for maintenance.
Now we have just installed a z/VM 5.1 LPAR and have an additional 2 Linux
guests with possibly more on the way. I do not wish to run Quagga on each
guest as the overhead is noticeable.
Our OSAs are on 4 separate subnets connected to two different switches that
are connected via Ciscoâs HSRP. I have the z/VM system configured for VIPA
using 1 qdio OSA and 1 non-qdio OSA and running mproute. I have a virtual
switche defined on each of the other 2 qdio OSAs. These are what the Linux
guests are using. Obviously the static route on the Linux guest are making
them really use one OSA for most of the outbound traffic.
Thank you for your patience up to now. Here is the question.
Can I still configure a dummy0 on my Linux guests and use z/VM as my router
to broadcast this dummy0 IP address out into the cloud? That way I can
develope a script to switch between the 2 different OSAs on the Linux guest
when maintenance dictates.
If so, how do I go about getting started?
Is there a better method?
Be gentle, I am a z/VM newbie.
Thanks
Peter
This Email message and any attachment may contain information that is
proprietary, legally privileged, confidential and/or subject to copyright
belonging to Pepco Holdings, Inc. or its affiliates ("PHI"). This Email is
intended solely for the use of the person(s) to which it is addressed. If
you are not an intended recipient, or the employee or agent responsible for
delivery of this Email to the intended recipient(s), you are hereby
notified that any dissemination, distribution or copying of this Email is
strictly prohibited. If you have received this message in error, please
immediately notify the sender and permanently delete this Email and any
copies. PHI policies expressly prohibit employees from making defamatory
or offensive statements and infringing any copyright or any other legal
right by Email communication. PHI will not accept any liability in respect
of such communications.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
This Email message and any attachment may contain information that is
proprietary, legally privileged, confidential and/or subject to copyright
belonging to Pepco Holdings, Inc. or its affiliates ("PHI"). This Email is
intended solely for the use of the person(s) to which it is addressed. If
you are not an intended recipient, or the employee or agent responsible for
delivery of this Email to the intended recipient(s), you are hereby
notified that any dissemination, distribution or copying of this Email is
strictly prohibited. If you have received this message in error, please
immediately notify the sender and permanently delete this Email and any
copies. PHI policies expressly prohibit employees from making defamatory
or offensive statements and infringing any copyright or any other legal
right by Email communication. PHI will not accept any liability in respect
of such communications.
