Lionel Dyck wrote:
Vic - thanks.
You said that if using vswitch that vlan was not needed if all the guests
were on the same subnet. How would you connect the guests then?
He probably meant to say 'same VLAN'
The port on the outboard switch can be configured to treat all hosts
connected to that
Not only want, need to control. VLAN tagging from the mainframe will
require close coordination with the router/switch networking
administrators. For example, If VLAN 436 is configured within the
mainframe, then the router/switch networking administrators will need to
configure VLAN 436 in their
I thought OSPF was a routing protocol and if all the VSWITCH users are on
the same subnet than why do they need a router?
Larry Davis
-Original Message-
From: Lionel Dyck [mailto:[EMAIL PROTECTED]
Sent: Monday, June 14, 2004 16:31 PM
To: [EMAIL PROTECTED]
Subject: Re: z/VM Linux Network
On Tue, 2004-06-15 at 07:06, Davis, Larry wrote:
I thought OSPF was a routing protocol and if all the VSWITCH users are on
the same subnet than why do they need a router?
Because people outside that subnet may want to get to them? Sure,
VSWITCH guests will all be able to see each other with no
If I have interpreted the book correctly, and it is true
that OSPF is not
used with VSWITCH, we will not be able to take that path as VSWITCH
protocols will not be supported by our networking group.
What are my options - apparently out networking group has
indicated they
want to use only
On Wed, 9 Jun 2004, Lionel Dyck wrote:
we are once again embarking on a linux on zseries pilot and our mainframe
network folks are arguing about things...
Lionel,
I join the VSWITCH chorus!
Just be aware that using VSWITCH makes you totally dependent upon the
network guys for availability
Port [EMAIL PROTECTED]
06/13/2004 11:37 PM
Please respond to
Linux on 390 Port [EMAIL PROTECTED]
To
[EMAIL PROTECTED]
cc
Subject
Re: z/VM Linux Network recommendations
On Wed, 9 Jun 2004, Lionel Dyck wrote:
we are once again embarking on a linux on zseries pilot and our
mainframe
network
PROTECTED]
To
[EMAIL PROTECTED]
cc
Subject
Re: z/VM Linux Network recommendations
On Monday, 06/14/2004 at 06:42 MST, Lionel Dyck [EMAIL PROTECTED]
wrote:
You said that if using vswitch that vlan was not needed if all the
guests
were on the same subnet. How would you connect the guests then?
1
On Monday, 06/14/2004 at 07:38 MST, Lionel Dyck [EMAIL PROTECTED]
wrote:
Alan - thanks - guess I have some more reading to do on this.
:-) Be careful. That just may make things more confusing.
If you want to understand what IEEE VLANs are, how they work, and how
switches are configured, it's
On Mon, 2004-06-14 at 15:30, Lionel Dyck wrote:
My mainframe networking guy came back to me with this comment:
If I have interpreted the book correctly, and it is true that OSPF is not
used with VSWITCH, we will not be able to take that path as VSWITCH
protocols will not be supported by our
On Monday, 06/14/2004 at 01:30 MST, Lionel Dyck [EMAIL PROTECTED]
wrote:
My mainframe networking guy came back to me with this comment:
If I have interpreted the book correctly, and it is true that OSPF is
not
used with VSWITCH, we will not be able to take that path as VSWITCH
protocols will
be
the failover Controller.
Larry Davis
-Original Message-
From: Lionel Dyck [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 09, 2004 17:16 PM
To: [EMAIL PROTECTED]
Subject: z/VM Linux Network recommendations
we are once again embarking on a linux on zseries pilot and our mainframe
we are once again embarking on a linux on zseries pilot and our mainframe
network folks are arguing about things (z/vm routing or use direct to
linux for the route) while our network engineers are saying no static
routing period.
what i'd like is your recommendations on what the best setup would
On Wed, 2004-06-09 at 16:15, Lionel Dyck wrote:
we are once again embarking on a linux on zseries pilot and our mainframe
network folks are arguing about things (z/vm routing or use direct to
linux for the route) while our network engineers are saying no static
routing period.
what i'd like
I concur, the Vswitch is the way to go. You get the best of both
worlds, all of the guests connect to an internal LAN service and they
all look like they are on the same network as z/VM.
On Wed, 2004-06-09 at 16:15, Lionel Dyck wrote:
we are once again embarking on a linux on zseries pilot and
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-390] z/VM Linux Network recommendations
I concur, the Vswitch is the way to go. You get the best of both worlds,
all of the guests connect to an internal LAN service and they all look like
they are on the same network as z/VM.
On Wed, 2004-06-09 at 16:15, Lionel
On Wednesday, 06/09/2004 at 02:15 MST, Lionel Dyck [EMAIL PROTECTED]
wrote:
we are once again embarking on a linux on zseries pilot and our
mainframe
network folks are arguing about things (z/vm routing or use direct to
linux for the route) while our network engineers are saying no static
17 matches
Mail list logo
