Hello Billy 

 

DTCVSW1 and DTCVSW2 are the ones supplied by IBM.

 

Ed Martin

Aultman Health Foundation

330-363-5050

ext 35050

From: The IBM z/VM Operating System [mailto:[email protected]] On
Behalf Of Billy Bingham
Sent: Wednesday, February 17, 2010 12:35 PM
To: [email protected]
Subject: Re: VSWITCH

 

Mark,

 

What is machine VSWITCH? Is it a service machine of some sort?

 

 

Billy

 

On 17 Feb 2010 at 12:25, Mark Pace wrote:

 

> 

> Rather than adding a NICDEF to the USER DIRECT I use the SYSTEM
DTCPARMS

> 

> .**********************************************

> :nick.TCPIP :type.server 

>  :class.stack 

>  :attach.0720-0722 - Connect real OSA

>  :vnic.0620 system vswtch1 - Define a NIC and attach to VSWITCH 

> 

> On Wed, Feb 17, 2010 at 12:09 PM, Dave Jones <[email protected]>
wrote:

>     Nope, that's all you need in the SYSTEM CONFIG file to get CP to
create a VSWITCH at 

>     IPL time.

>     

>     DJ

> 

> 

> 

> On 02/17/2010 10:52 AM, Billy Bingham wrote:

>     I have the following in my SYSTEM CONFIG file:

>     

>     define vswitch vsw1 rdev 021C 0220

>     

>     

>     Do I need to attach 21C - 21E and 220 - 222 to any machine?

>     

>     

>     Thanks,

>     

>     Billy

>     

>     On 16 Feb 2010 at 13:28, Scott Rohling wrote:

> 

>     

>     oops -- that HOME statement should be:

>     

>     HOME

>     10.68.0.6 255.255.255.0 VMVSWD

>     

>     You point to the 'LINK' (VMVSWD in this case).. I cut the line
short in my last post.

>     

>     Scott

>     

>     On Tue, Feb 16, 2010 at 1:25 PM, Scott
Rohling<[email protected]> wrote:

>       Ok - Before I show the TCPIP PROFILE -- here is a line from the
TCPIP directory 

>     entry:

>     

>       NICDEF A000 TYPE QDIO LAN SYSTEM VSW1

>     

>       Our system has a VSWITCH called VSW1 .. TCPIP will use address
A000 to 

>     connect to it.

>     

>       In PROFILE TCPIP:

>     

>       DEVICE VMVSW OSD A000 PORTNAME VMVSW PORTNUMBER 0 AUTOR

>       LINK VMVSWD QDIOETHERNET VMVSW MTU 1492

>       .

>       .

>       HOME

>       10.68.0.6 255.255.255.0 VMVSW

>     

>       .

>       .

>       START VMVSW

>     

>       Really - just exactly like an OSA (it's a virtualized OSA) --
the only difference is 

>     where your

>       device comes from --- a virtual NIC attached to a VSWITCH,
instead of a dedicated 

>     OSA.

>       You can make the switch by simply changing the directory entry
for TCPIP.. (just 

>     make sure

>       TCPIP has been granted access to the vswitch!) Use the same
address as you 

>     used for

>       your OSA and use it on the NICDEF statement. Bring TCPIP down
and up again - 

>     done.

>     

>       Scott

>     

>     

>     

>     

>     

>     On Tue, Feb 16, 2010 at 12:00 PM, Billy
Bingham<[email protected]> 

>     wrote:

>       Scott,

>     

>       Can you send me the TCPIP PROFILE that you have setup to use
Vswitches?

>     

>     

>       Thanks,

>     

>       Billy

>     

>     

>       On 16 Feb 2010 at 11:40, Scott Rohling wrote:

>     

>       >

>       > Agreed -- I like connecting TCPIP to the VSWITCH and letting
the controllers 

>     manage the

>       > OSA's. It's also nice to be able to recycle TCPIP without
affecting Linux guests.

>       >

>       > Scott

>       >

>       > On Tue, Feb 16, 2010 at 11:27 AM, Mark Pace<[email protected]>
wrote:

>       > Yes.

>       >

>       > It can be done either way. You can connect TCPIP to it's own
OSA connection, 

>     or

>       connect

>       > TCPIP to the vswitch. There may be good reasons for not having
TCPIP 

>     connected to

>       the

>       > vswitch, but I don't know what they would be. With vswitch
having automatic fail-

>     over

>       when

>       > it has multiple OSA addresses, it's the way I run.

>       >

>       >

>       >

>       > On Tue, Feb 16, 2010 at 1:09 PM, Billy 

>     Bingham<[email protected]>

>       wrote:

>       > Hello all,

>       >

>       > Risking the old saying that it's better to have someone think
you're stupid than to 

>     open

>       your

>       > mouth and remove all doubt... but :)

>       >

>       > I'm confused about Vswitches on z/VM... sorta. I know you
define the Vswitch in 

>     the

>       System

>       > Config file, but does the TCPIP guest running on z/VM also use
that Vswitch or 

>     does

>       TCP/IP

>       > use it's own OSA connection and other Liniux guests (In this
case) use the 

>     Vswitch? Is

>       there

>       > a 'cookbook' available for setting up Vswitches?

>       >

>       > Any hints and tips appreciated.

>       >

>       >

>       > Billy

>       >

>       >

>       >

>       >

>       >

>       > --

>       > Mark Pace

>       > Mainline Information Systems

>       > 1700 Summit Lake Drive

>       > Tallahassee, FL. 32317

>       >

>       >

>     

>     

>     

>     

>     

>     

>     

>     

>     

> 

>     

>     

> 

> 

> 

>     -- 

>     Dave Jones

>     V/Soft

>     www.vsoft-software.com

>     Houston, TX

>     281.578.7544

> 

> 

> 

> -- 

> Mark Pace

> Mainline Information Systems

> 1700 Summit Lake Drive

> Tallahassee, FL. 32317

 

  

Reply via email to