With one vswitch connected to two osa's you can get failover.
If the physical switches are on two different vlans for test/production you can
mimic this on one vswitch by using the same two vlans, one on production the
other sandbox. The vlan spec guarantees data isolation and separation and
vsw
Thanks Alan/Mark,
"What am I trying to do?" -
Well I have a LPAR with z/VM 520. We have some production Linux systems and
a few 'test sand boxes' for us to play with.
I have always had 2 access ports via 2 OSA cards to 2 6509s. I have just
been given 2 trunk port connections via 2 new OSA cards
>>> On Wed, Sep 5, 2007 at 10:19 AM, in message
<[EMAIL PROTECTED]>,
Peter Rothman <[EMAIL PROTECTED]> wrote:
> My apologies - I see the TCPIP LINK statement has a VLAN option.
> Is there a way to specify the VLAN for Linux? We are on
> Linux version 2.6.16.21-0.8-default ([EMAIL PROTECTED]) (gcc
On Wednesday, 09/05/2007 at 10:20 EDT, Peter Rothman
<[EMAIL PROTECTED]> wrote:
> My apologies - I see the TCPIP LINK statement has a VLAN option.
> Is there a way to specify the VLAN for Linux? We are on
> Linux version 2.6.16.21-0.8-default ([EMAIL PROTECTED]) (gcc version 4.1.0
> (SUSE Linux))
Subject
Re: Another VSWITCH question
09/05/2007 10:23
AM
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
vconfig from candelatech should be on your
vconfig from candelatech should be on your linux distro from suse. Also go to
http://www.candelatech.com/~greear/
David
-Original Message-
From: Linux on 390 Port on behalf of Peter Rothman
Sent: Wed 9/5/2007 10:19 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Another VSWITCH question
My
Subject
Re: Another VSWITCH question
09/05/2007 09:44
AM
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
how have you configured the PORTTYPE on t
to
Linux on 390 Port
To
LINUX-390@VM.MARIST.EDU
cc
Subject
Re: Another VSWITCH question
Huh? One more time, in very small words, please
As I understand it, the rules are:
If the switch port is defined as access mode (IOS "switchport mode
access"), packets with tags pr
IST.EDU> Subject
Re: Another VSWITCH question
09/05/2007 09:44
AM
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
Subject
Re: Another VSWITCH question
09/05/2007 09:45
AM
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
What release of VM on you on? In 5.3.0, we separate
> In 5.3.0, we separated the default VLAN and
> the native VLAN. Prior to 5.3.0, the default VLAN is the same as the
> native VLAN. In this case, defining the VSWITCH to default to VLAN
147
> means that 147 is the native VLAN (or untagged set). Most likely,
the
> OSA card is plugged into an ac
: Wed 9/5/2007 9:35 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Another VSWITCH question
Thanks for the replies to my previous question.
Our network folks have configured their 6509 connection to our OSAs with 1
vlan - 147.
If I define my VSWITCH with a default VLAN ID of 147 and then "grant
IP
(Bolinda) Adams
[EMAIL PROTECTED]
z/VM Development - Virtual Networking
Peter Rothman <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port
09/05/2007 09:35 AM
Please respond to
Linux on 390 Port
To
LINUX-390@VM.MARIST.EDU
cc
Subject
Another VSWITCH question
Thanks for the replies
Thanks for the replies to my previous question.
Our network folks have configured their 6509 connection to our OSAs with 1
vlan - 147.
If I define my VSWITCH with a default VLAN ID of 147 and then "grant
IPSTACK vlan 147" - all is OK - I can PING etc.
However if I define the VSWITCH with a differ
Monday 17 January 2005 23:45, You wrote:
> Hi,
> Anyone know of a way to delete a VSWITCH without IPLing?
> Betsie
z/VM 4.4, from MAINT:
q vswitch
VSWITCH SYSTEM VSWITCH_NAME Type: VSWITCH Active: 0 MAXCONN: INFINITE
...
cp detach vswitch VSWITCH_NAME
VSWITCH SYSTEM VSWITCH_NAME is d
Betsie,
Check out DETACH VSWITCH (in the 5.1 CP Commands and Reference).
Betsie Spann wrote:
Hi,
Anyone know of a way to delete a VSWITCH without IPLing?
Betsie
--
For LINUX-390 subscribe / signoff / archive access instructions,
se
Hi,
Anyone know of a way to delete a VSWITCH without IPLing?
Betsie
--
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
Post, Mark K wrote:
He could always use 104 and 105 for the read/write channels, and 103 as the
data channel.
But that was the point Bruce and I were fighting about. If you were
attaching the 3 devices of a tripod to a virtual machine you could, but
if you define a VSWITCH you specify the first o
He could always use 104 and 105 for the read/write channels, and 103 as the
data channel.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Rob
van der Heij
Sent: Friday, April 09, 2004 4:21 AM
To: [EMAIL PROTECTED]
Subject: Re: VSWITCH question
From: Rob van der Heij <[EMAIL PROTECTED]>
Subject: Re: VSWITCH question
To: [EMAIL PROTECTED]
Precedence: list
Bruce Hayden wrote:
>Yes, generate more OSA I/O devices and then specify one of them (such as
>103) for the vswitch. I have exactly this configuration working on a
>co
Bruce Hayden wrote:
Yes, generate more OSA I/O devices and then specify one of them (such as
103) for the vswitch. I have exactly this configuration working on a
couple of systems. This is not unlike sharing an OSA between LPARS, but
in this case the sharing is all within the same LPAR.
Well no
: Thursday, April 08, 2004 4:53 PM
To: [EMAIL PROTECTED]
Subject: Re: VSWITCH question
On Thu, 2004-04-08 at 23:02, David Booher wrote:
>
>CNTLUNIT CUNUMBR=0100,PATH=(00),UNIT=OSA
>IODEVICE ADDRESS=(0100,03),CUNUMBR=(0100),UNIT=OSA, X
> UNITADD=00
>IO
Ref: Your note of Thu, 8 Apr 2004 16:02:46 -0500 (attached)
Yes, generate more OSA I/O devices and then specify one of them (such as
103) for the vswitch. I have exactly this configuration working on a
couple of systems. This is not unlike sharing an OSA between LPARS, but
in this case the shar
On Thu, 2004-04-08 at 23:02, David Booher wrote:
>
>CNTLUNIT CUNUMBR=0100,PATH=(00),UNIT=OSA
>IODEVICE ADDRESS=(0100,03),CUNUMBR=(0100),UNIT=OSA, X
> UNITADD=00
>IODEVICE ADDRESS=(010F),CUNUMBR=(0100),UNIT=OSAD, X
> UNITADD=FE
>
> Should I genera
V wants a
> REAL device, so is it possible to generate more addresses for the real OSA?
>
> Dave
>
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> Ferguson, Neale
> Sent: Thursday, April 08, 2004 3:50 PM
> To: [EMAIL PROTECTED]
>
: [EMAIL PROTECTED]
Subject: Re: [LINUX-390] VSWITCH question
So, my current IOCP has:
CNTLUNIT CUNUMBR=0100,PATH=(00),UNIT=OSA
IODEVICE ADDRESS=(0100,03),CUNUMBR=(0100),UNIT=OSA, X
UNITADD=00
IODEVICE ADDRESS=(010F),CUNUMBR=(0100),UNIT=OSAD, X
UNITADD
r the real OSA?
Dave
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Ferguson, Neale
Sent: Thursday, April 08, 2004 3:50 PM
To: [EMAIL PROTECTED]
Subject: Re: VSWITCH question
The VSWITCH OSA devices are attached to no one. CP will drive them but use
t
I am confused about the RDEV setting on the DEFINE VSWITCH command. I currently have
my OSA adapter (address 0100,0101,0102) attached to TCPIP and defined as:
DEVICE [EMAIL PROTECTED] OSD 0100 PORTNAME QSPORT0 PRIR
LINK VMTCPIP QDIOETHERNET [EMAIL PROTECTED]
When I attempt to a
The VSWITCH OSA devices are attached to no one. CP will drive them but use
the VM TCPIP stack to initialize the devices. CP uses the *VSWITCH IUCV
service to talk with the stack. The stack will issue the necessary CCWs to
get the OSAs initialized. From that point on CP will drive the devices
itself
29 matches
Mail list logo
