Vm & ZLinux VSWITCH question

[Ron MacRae]

Hi all,
I have a VM & zLinux vswitch issue that I'm hoping someone can help me with. I know this list is primarily z/OS but the VM lists I've looked at don't appear to be active.

Let me state up front I know sod all about TCPIP and am doing this by following the manuals, some of which appear to be conflicting due to different zVM releases, or perhaps due to my lack of basic knowledge here.

I have a zVM 6.2 LPAR connected to TCPIP via OSA card at address 888
I have a zLinix LPAR connected to TCPIP via OSA card at address 780

These both work fine. We now want to run the zLinux as a VM instead of an LPAR but when we IPL the VM it fails with -

^1A..failed qeth-bus-ccw-0.0.0870 No interface found

The real VM OSA card show as -
q 888-88a
05:33:31 OSA 0888 ATTACHED TO TCPIP 0888 DEVTYPE OSA CHPID FD OSD
05:33:31 OSA 0889 ATTACHED TO TCPIP 0889 DEVTYPE OSA CHPID FD OSD
05:33:31 OSA 088A ATTACHED TO TCPIP 088A DEVTYPE OSA CHPID FD OSD

I can't list the z/LINUX LPAR virtual devices as we had to revert back to an LPAR.

The manuals talk about defining a vswitch and we did this by issuing the commands -
CP DEFINE VSWITCH VSWITCH1
CP SET VSWITCH VSWITCH1 GRANT LINVM

and the VSWITCH looks like

VSWITCH SYSTEM VSWITCH1 Type: QDIO Connected: 0 Maxconn: INFINITE
PERSISTENT RESTRICTED IP Accounting: OFF
USERBASED
VLAN Unaware
MAC address: 02-00-00-00-00-01 MAC Protection: OFF
State: Defined
IPTimeout: 5 QueueStorage: 8
Isolation Status: OFF

and in the directory of LINVM machine we added

NICDEF 0780 TYPE QDIO LAN SYSTEM VSWITCH1

According to the manuals we are following I think this is all we need to do.

What have I missed and/or screwed up?

Thanks in advance, Ron.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Lutz Hamann]

Hi Ron,

alhough I think the IBMVM forum is the right place to address your question,
I do not see a the 'real' OSD-device representing your VSWITCH1.

I.E. : RDEV: 0500.P00 VDEV: 0500 Controller: DTCVSW2


ciao Lutz

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Mark Pace]

Is this a typo?
^1A..failed qeth-bus-ccw-0.0.0870 No interface fo

Is Linux really using 870 - everything else I see you describe address 780.

Post by Lutz Hamann
Hi Ron,
alhough I think the IBMVM forum is the right place to address your question,
I do not see a the 'real' OSD-device representing your VSWITCH1.
I.E. : RDEV: 0500.P00 VDEV: 0500 Controller: DTCVSW2
ciao Lutz
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,

--
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Lutz Hamann]

That can only answered by Ron :-)

Nonetheless a VSWITCH needs a real OSD-device for communicating outside
a z/VM LPAR if the Controller is DTCVSWx.

Please correct me if I should be wrong ...


ciao Lutz

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Ron MacRae]

Sorry guys. 0870 is the correct address. Everywhere where I put 780 was wrong.

The OSA card on the zLinux LPAR is 0870 and I defined a NICDEF on 870 for the zLinux VM.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Ron MacRae]

Lutz,
You say "I do not see a the 'real' OSD-device representing your VSWITCH1" and I agree we have not defined that, it wasn't specified in the example i was following which said simply issue the commands -

"CP DEFINE VSWITCH VSWITCH1
CP SET VSWITCH VSWITCH1 GRANT LNXVM "

Because an RDEV was not on the sample command in the book I thought it would find this out from TCPIP.

Should the define VSWITCH be -

"CP DEFINE VSWITCH VSWITCH1 RDEV 888" to connect to the same OSA card as used by the VM machine?

Is that what you are saying or am I missunderstanding you?

Ron.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Ron MacRae]

Lutz,
OK I must have misunderstood.

When I try - CP SET VSWITCH VSWITCH1 RDEV 888

I get -
HCPSWU2838I Device 0888.P00 specified for VSWITCH VSWITCH1 is already attached.

888 is the OSA card that the VM LPAR is already using.


Ron.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Lutz Hamann]

Ron,

of course you can' specify 888 as RDEV for your VSWITCH1 because you've attached this OSD-device
to TCPIP !

You should have further real device (i.e. 870) for your VSWITCH1 to connect to 'outer-world' ...

But since this topic is not related to z/OS - maybe we should discuss it off-line ?


ciao Lutz

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Lutz Hamann]

Sorry for fast finger tips - I should have said "can not" instead of "can'" :-(

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Chris Mason]

Ron

Let me state up front I know sod all about TCPIP ...

1. Consult the minimally one person in your "shop" who has been educated in matters to do with the Internet Protocol (IP) and its related protocols such as TCP and see what he or she thinks about your configuration definitions.

2. Perhaps both of you could consult the following redpaper which I found excellent on its first topic VLANs and appears to be as excellent on the topic of VSWITCH.[1]

Linux on IBM eServer zSeries and S/390: VSWITCH and VLAN Features of z/VM 4.4
http://www.redbooks.ibm.com/abstracts/redp3719.html

3. Such questions as this are best posed in list IBMTCP-L where there is the greater concentration of expertise in the products of which the first manifestation was the first version of "TCP/IP for VM" back in the early '90s. Having said that, many of the denizens of that list also keep an eye on IBM-MAIN.

For IBMTCP-L subscribe / signoff / archive access instructions, send email to ***@VM.MARIST.EDU with the message: INFO IBMTCP-L

-

According to the manuals we are following ...

Posters should always state precisely *which* manuals they are following for very obvious reasons one of which is to avoid responders mentioning what is already known!

-

[1] However I need to qualify this by saying that "VM guru" Alan Altmark has been less keen on this redpaper saying that the latest edition of the manual "(z/VM) Connectivity" should be used for everything to do with VSWITCH. The latest I can easily locate is the following:

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/HCSC9C00/

-

Chris Mason

Hi all,
I have a VM & zLinux vswitch issue that I'm hoping someone can help me with. I know this list is primarily z/OS but the VM lists I've looked at don't appear to be active.
Let me state up front I know sod all about TCPIP and am doing this by following the manuals, some of which appear to be conflicting due to different zVM releases, or perhaps due to my lack of basic knowledge here.
I have a zVM 6.2 LPAR connected to TCPIP via OSA card at address 888
I have a zLinix LPAR connected to TCPIP via OSA card at address 780
These both work fine. We now want to run the zLinux as a VM instead of an LPAR but when we IPL the VM it fails with -
^1A..failed qeth-bus-ccw-0.0.0870 No interface found
The real VM OSA card show as -
q 888-88a
05:33:31 OSA 0888 ATTACHED TO TCPIP 0888 DEVTYPE OSA CHPID FD OSD
05:33:31 OSA 0889 ATTACHED TO TCPIP 0889 DEVTYPE OSA CHPID FD OSD
05:33:31 OSA 088A ATTACHED TO TCPIP 088A DEVTYPE OSA CHPID FD OSD
I can't list the z/LINUX LPAR virtual devices as we had to revert back to an LPAR.
The manuals talk about defining a vswitch and we did this by issuing the commands -
CP DEFINE VSWITCH VSWITCH1
CP SET VSWITCH VSWITCH1 GRANT LINVM
and the VSWITCH looks like
VSWITCH SYSTEM VSWITCH1 Type: QDIO Connected: 0 Maxconn: INFINITE
PERSISTENT RESTRICTED IP Accounting: OFF
USERBASED
VLAN Unaware
MAC address: 02-00-00-00-00-01 MAC Protection: OFF
State: Defined
IPTimeout: 5 QueueStorage: 8
Isolation Status: OFF
and in the directory of LINVM machine we added
NICDEF 0780 TYPE QDIO LAN SYSTEM VSWITCH1
According to the manuals we are following I think this is all we need to do.
What have I missed and/or screwed up?
Thanks in advance, Ron.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Ron MacRae]

Lutz,
Thanks for your help. As I said before I used to be a VM sysprog 20+ years ago before TCPIP entered the IBM world.

I was hoping the VSWITCH would allow us to use the same OSA card as VM.
That was what I was trying to achieve.

I had thought it might be like VMWARE's VM where I can have several virtual machines all using different IP addresses via the same network card as the host windows box. Obviously it isn't but I don't have another picture in my head.

There is no way to get this all running of the one OSA? We need one card for the TCPIP VM and another one for the VSWITCH?

We will pull another OSA card across to this LPAR and try again.

Thanks for the clarification.

Ron.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Mark Post]

Post by Ron MacRae
I was hoping the VSWITCH would allow us to use the same OSA card as VM.
That was what I was trying to achieve.
I had thought it might be like VMWARE's VM where I can have several virtual
machines all using different IP addresses via the same network card as the
host windows box. Obviously it isn't but I don't have another picture in my
head.
There is no way to get this all running of the one OSA? We need one card for
the TCPIP VM and another one for the VSWITCH?

You _can_ do what you want. You just need to understand that one OSA card can have many subchannel addresses. You can share the card, but not the subchannel addresses. So, from MAINT, or any other userid with CP class B, do a "#cp q osa free" command. Pick any three consecutive addresses, and specify the first one as the RDEV for the VSWITCH.


Mark Post

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Chris Mason]

Lutz

But since this topic is not related to z/OS ...

Some time ago I was chastised very roundly indeed by one of the "usual suspects" inhabiting this list for what this very suggestion implies!!!

Apparently, IBM-MAIN is ***not*** exclusively to be regarded as a z/OS list. Perhaps if this were so it would have a more appropriate title.

... maybe we should discuss it off-line ?

Furthermore, there is some competition for degree of irritation in an intriguing problem - some say "issue"! - having been presented only to have what may be a resolution discovered "off-line". Maybe not!

Chris Mason

Ron,
of course you can' specify 888 as RDEV for your VSWITCH1 because you've attached this OSD-device
to TCPIP !
You should have further real device (i.e. 870) for your VSWITCH1 to connect to 'outer-world' ...
But since this topic is not related to z/OS - maybe we should discuss it off-line ?
ciao Lutz

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[McKown, John]

-----Original Message-----
From: IBM Mainframe Discussion List
Sent: Wednesday, June 20, 2012 10:24 AM
Subject: Re: Vm & ZLinux VSWITCH question
Lutz

But since this topic is not related to z/OS ...

Some time ago I was chastised very roundly indeed by one of
the "usual suspects" inhabiting this list for what this very
suggestion implies!!!

Personally, I consider this list to be for almost anything having to do with zEnterprise (and its predecessors) topics. Granted, there may be more specific forums for some things, such as MVS-OE (z/OS UNIX), IBMTCP-L, Linux-390, z/VM, TSO REXX (who __do__ mean REXX in TSO, not REXX in general), CICS, DB2, IMS, and likely others of which I am not aware. IBM-MAIN is definitely __not__ "z/OS only". This despite the fact that most readers are z/OS, and perhaps some z/VSE.
--
John McKown
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
[phone] phone *
***@healthmarkets.com * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Anne & Lynn Wheeler]

Post by McKown, John
Personally, I consider this list to be for almost anything having to
do with zEnterprise (and its predecessors) topics. Granted, there may
be more specific forums for some things, such as MVS-OE (z/OS UNIX),
IBMTCP-L, Linux-390, z/VM, TSO REXX (who __do__ mean REXX in TSO, not
REXX in general), CICS, DB2, IMS, and likely others of which I am not
aware. IBM-MAIN is definitely __not__ "z/OS only". This despite the
fact that most readers are z/OS, and perhaps some z/VSE.

as an aside ... IBM-MAIN mailing list originated on BITNET(/EARN) which
was almost all vm370 systems ... using technology similar to that of the
corporate internal network ... which also was almost all vm370 systems.

currently the IBM-MAIN mailing list is also gatewayed to ("USENET")
newsgroups ... although posts to newsgroups don't travel in the other
direction. Some of the other mailing lists that originated on BITNET
have at various times been also gatewayed to newsgroups ... like z/VM
... but gateway isn't currently active.

BITNET
http://en.wikipedia.org/wiki/BITNET

the early LISTSERV mailing list software for bitnet was similar to the
TOOLSRUN that had been earlier developed for the internal network
... but TOOSLRUN also supported USENET newsgroup like function ... in
addition to mailing lists ... this has BITNET migrating to the 1986
Paris-developed LISTSERV in 1987
http://en.wikipedia.org/wiki/LISTSERV

misc. past posts mentioning BITNET (and/or EARN in europe)
http://www.garlic.com/~lynn/subnetwork.html#bitnet

old email from person tasked with creating EARN:
http://www.garlic.com/~lynn/2001h.html#email840320

misc. past posts mentioning internal network (larger than
arpanet/internet from just about the beginning until
sometime late 85 or early 86)
http://www.garlic.com/~lynn/subnetwork.html#internalnet

I had been blamed for online computer conferencing on the internal
network in the late 70s and early 80s. Folklore is that when the
executive committee was told about online computer conferencing (and the
internal network), 5of6 wanted to fire me. Officially sanctioned
"discussion groups" and TOOLSRUN were somewhat the outcome of
investigations into my activities.

Internal network was result of co-worker at the science center,
reference
http://en.wikipedia.org/wiki/Edson_Hendricks

there is "typo" in the above about 1981 and ARPANET conversion to
TCP/IP, 250 ARPANET nodes and 1000 vnet nodes. All that happened in 1983
(not 1981). Also, ARPANET nodes were "IMPs" (tightly controlled by the
government and only number around 100 at the time of conversion). There
were possibly 250 "hosts" at 1983 cut-over (connected to those IMPs).
The requirement for tightly controlled IMPs is one of the contributing
factors to the internal network growing faster than the
arpanet/internet.

also from above:

In 1976, MIT Professor Jerry Saltzer accompanied Hendricks to DARPA,
where Henricks described his innovations to the principal scientist,
Dr. Vinton P. Cerf. From that point on, Vint and other DARPA scientists
adopted Hendricks' connectionless approach. The result developed into
the Internet as we know it today.

... snip ...

some number of people from MIT (IBM 7094) CTSS went to the 5th flr of
545 tech sq. for Multics & project MAC (including Jerry Saltzer) and
others went to the science center on the 4th flr, did virtual machines,
internal network, GML/SGML, bunch of other things. misc. past posts
mentioning science center
http://www.garlic.com/~lynn/subtopic.html#545tech

RSCS/VNET had layered networking (as opposed to JES2/NJI) and could
easily do drivers that talked to other systems (again as opposed to
JES2/NJI). JES2/NJI for nearly the whole time had limitations on the
maximum number of defined nodes ... which was less than the number of
internal nodes for at least a couple decades ... coupled with attribute
that JES2/NJI would trash traffic where either the origin and/or
destination node wasn't defined in its local table. JES2/NJI also had
characteristic that it tended to crash the host MVS system if traffic
was exchanged between JES2/NJI systems at different release levels. For
whatever reason, the RSCS/VNET discontinued shipping the native drivers
and only shipped the JES2/NJI drivers (with RSCS/VNET) ... even though
they continued to be used on the internal network because they were more
efficient and had higher throughput. misc. past posts mentioning HASP,
JES2, NJI, etc
http://www.garlic.com/~lynn/submain.html#hasp

[Chris Mason]

Ron

Post by Ron MacRae
There is no way to get this all running of the one OSA?

Paying attention to the question mark at the end of what is otherwise apparently a statement, my very limited understanding of the principles of VSWITCH is that one real OSA is all you need and then only if you want your virtual LAN to "morph" into a real LAN at some point in its existence.

Please read at least the redpaper and come back when you have digested the principles of VSWITCH.

Here is a definition from the "Introduction to Connectivity Terminology" chapter of the "Connectivity" manual:

<quote>

1.2.1.4 What Is a Guest LAN?

A guest LAN represents a simulated LAN segment that can be connected to simulated network interface cards. There are two types of LAN segments: OSA-Express and HiperSockets. Each guest LAN is isolated from other guest LANs on the same system (unless some member of one LAN group acts as a router to other groups).

1.2.1.5 What Is a Virtual Switch?

A virtual switch is a special type of guest LAN that provides external LAN connectivity through an OSA-Express device without the need for a routing virtual machine.

</quote>
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/HCSC9C00/1.2.1.4
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/HCSC9C00/1.2.1.5

Note that a "guest LAN", obviously the OSA-Express flavour, is what I called a "virtual LAN" above to emphasis the passage through minimally a single OSA feature to a *real* LAN, "external LAN connectivity".

I do hope I've remembered the principles of a VSWITCH from the time I last read up on the topic a few years ago!

Chris Mason

Post by Ron MacRae
Lutz,
Thanks for your help. As I said before I used to be a VM sysprog 20+ years ago before TCPIP entered the IBM world.
I was hoping the VSWITCH would allow us to use the same OSA card as VM.
That was what I was trying to achieve.
I had thought it might be like VMWARE's VM where I can have several virtual machines all using different IP addresses via the same network card as the host windows box. Obviously it isn't but I don't have another picture in my head.
There is no way to get this all running of the one OSA? We need one card for the TCPIP VM and another one for the VSWITCH?
We will pull another OSA card across to this LPAR and try again.
Thanks for the clarification.
Ron.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Lutz Hamann]

Sorry Chris - I simply did not want to bore the folks here with z/VM -specific details :-)

And yes I know that IBM-MAIN is and has always been a good focal point for all
mainframe-related stuff ...


ciao Lutz

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Mark Pace]

You can use the same OSA card. But what you need to do is give that OSA to
the vswitch and then connect TCPIP to the vswitch instead of the OSA.
There are some changes to TCPIP that would have to happen.


Take this to the vm list - it is quite active and lots of help there.

The IBM z/VM Operating System <***@listserv.uark.edu>

On Wed, Jun 20, 2012 at 11:41 AM, Lutz Hamann

Post by Lutz Hamann
Sorry Chris - I simply did not want to bore the folks here with z/VM -specific details :-)
And yes I know that IBM-MAIN is and has always been a good focal point for all
mainframe-related stuff ...
ciao Lutz
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,

--
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Ron MacRae]

Chris,
In reply to your suggestions.


1) I've already spoken to our IP guy but he's a z/OS guy, as am I really, and between us we're still stuck.

2) Thanks for the redpaper, I hadn't seen that one. However a lot of the detail on the older versions doesn't seem to match with VM 6.2, but that is likely down to my lack of understanding.

3) I'll try IBMTCP-L. As i said I tried some VM lists but never saw any replies or indeed traffic.

I've got an up to date copy of the connectivity manual. It comes with the VM 6.2 documentation set.

Thanks, Ron.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Jerry Whitteridge]

Ron - This list is the active z/VM list and has all the experts on the use of the vswitch you need


***@LISTSERV.UARK.EDU




Jerry Whitteridge
Lead Systems Programmer
Safeway Inc.
925 951 4184

If you feel in control
you just aren't going fast enough.


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@listserv.ua.edu] On Behalf Of Ron MacRae
Sent: Wednesday, June 20, 2012 8:47 AM
To: IBM-***@listserv.ua.edu
Subject: Re: Vm & ZLinux VSWITCH question

Chris,
In reply to your suggestions.


1) I've already spoken to our IP guy but he's a z/OS guy, as am I really, and between us we're still stuck.

2) Thanks for the redpaper, I hadn't seen that one. However a lot of the detail on the older versions doesn't seem to match with VM 6.2, but that is likely down to my lack of understanding.

3) I'll try IBMTCP-L. As i said I tried some VM lists but never saw any replies or indeed traffic.

I've got an up to date copy of the connectivity manual. It comes with the VM 6.2 documentation set.

Thanks, Ron.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN


"Email Firewall" made the following annotations.
------------------------------------------------------------------------------

Warning:
All e-mail sent to this address will be received by the corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain proprietary information and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately.

==============================================================================

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Mark Post]

Oh, and if you're finding the manuals a bit confusion, hopefully this article will help clear up some things:
http://www.mainframezone.com/article/planning-and-implementing-vswitch-for-linux-390-guests


Mark Post

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Ron MacRae]

Hi guys,
Thanks to all of you who helped me get this sorted. It's all up and running very nicely now with multiple OSAs for redunancy etc and hipersockets.

Lutz, Thanks for the clarifications.
Chris, Thanks for the redpaper, it was much clearer, but perhaps that was because I had a glimmer of what I was trying to do by that time.


It's all quite trivial once you have a clear picture of what you are trying to do.

For those interested it's quite simple.
Define VSWITCHs and point them at real OSA triplets, not the one used by TCPIP.

CP DEFINE VSWITCH VSWITCH1 RDEV 88B
CP DEFINE VSWITCH VSWITCH2 RDEV 72B
CP SET VSWITCH VSWITCH1 GRANT LINUXVM1
CP SET VSWITCH VSWITCH2 GRANT LINUXVM1

These get picked up by different switch machines to give additional redundancy.
q vswitch all
VSWITCH SYSTEM VSWITCH1 Type: QDIO Connected: 1 Maxconn: INFINITE
PERSISTENT RESTRICTED NONROUTER Accounting: OFF
USERBASED
VLAN Unaware
MAC address: 02-00-00-00-00-01 MAC Protection: OFF
State: Ready
IPTimeout: 5 QueueStorage: 8
Isolation Status: OFF
Uplink Port:
RDEV: 088B.P00 VDEV: 0600 Controller: DTCVSW2
VSWITCH SYSTEM VSWITCH2 Type: QDIO Connected: 1 Maxconn: INFINITE
PERSISTENT RESTRICTED NONROUTER Accounting: OFF
USERBASED
VLAN Unaware
MAC address: 02-00-00-00-00-02 MAC Protection: OFF
State: Ready
IPTimeout: 5 QueueStorage: 8
Isolation Status: OFF
Uplink Port:
RDEV: 072B.P00 VDEV: 0600 Controller: DTCVSW1
Ready; T=0.01/0.01 12:30:29

In the directory for LINUXVM1 -

NICDEF 0710 TYPE QDIO LAN SYSTEM VSWITCH1
NICDEF 0870 TYPE QDIO LAN SYSTEM VSWITCH2

Where 710 and 870 are where the linux machine expects its OSA cards to be.

For hipersockets, just dedicate 3 OSA ports, from the hipersocket channel.
DEDICATE F000 F000
DEDICATE F001 F001
DEDICATE F002 F002

All works a treat once you can imagine how it hangs together.

Talk about making something simple sound complicated. :)

Thanks again,

Ron.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Ron MacRae]

Jerry,
You pointed me at ***@LISTSERV.UARK.EDU.

I'd already subscribed to this as an RSS feed in Google reader. That's my prefered method of seeing all the detail when I want to rather than getting interrupted by emails all the time. I use the same process for IBM-MAIN and several other groups/lists I follow.

However according to Google reader the last update for this list was october 2011. I assumed it was an inactive list. From logging on to the actual server I can see that it is a very active list. I guess Google has dropped IBMVM.

Do you, or does anyone, know of an RSS feed for IBMVM?

Ron.



----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Mark Post]

Post by Ron MacRae
Do you, or does anyone, know of an RSS feed for IBMVM?

According to the links on the Listserv web interface:
http://listserv.uark.edu/cgi-bin/wa?RSS&L=IBMVM&v=ATOM1.0
http://listserv.uark.edu/cgi-bin/wa?RSS&L=IBMVM&v=1.0
http://listserv.uark.edu/cgi-bin/wa?RSS&L=IBMVM&v=2.0


Mark Post

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Jerry Whitteridge]

I'm afraid not - I use all the mailing lists as true mailing lists. Note that even this one is only gated one way to the newsgroup and that any posts to the newsgroup will NOT be seen by folks that are subscribed to the mailing list.

Jerry Whitteridge
Lead Systems Programmer
Safeway Inc.
925 951 4184

If you feel in control
you just aren't going fast enough.


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@listserv.ua.edu] On Behalf Of Ron MacRae
Sent: Thursday, June 21, 2012 9:55 AM
To: IBM-***@listserv.ua.edu
Subject: Re: Vm & ZLinux VSWITCH question

Jerry,
You pointed me at ***@LISTSERV.UARK.EDU.

I'd already subscribed to this as an RSS feed in Google reader. That's my prefered method of seeing all the detail when I want to rather than getting interrupted by emails all the time. I use the same process for IBM-MAIN and several other groups/lists I follow.

However according to Google reader the last update for this list was october 2011. I assumed it was an inactive list. From logging on to the actual server I can see that it is a very active list. I guess Google has dropped IBMVM.

Do you, or does anyone, know of an RSS feed for IBMVM?

Ron.



----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN


"Email Firewall" made the following annotations.
------------------------------------------------------------------------------

Warning:
All e-mail sent to this address will be received by the corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain proprietary information and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately.

==============================================================================

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Anne & Lynn Wheeler]

Post by Ron MacRae
I'd already subscribed to this as an RSS feed in Google reader. That's
my prefered method of seeing all the detail when I want to rather than
getting interrupted by emails all the time. I use the same process for
IBM-MAIN and several other groups/lists I follow.
However according to Google reader the last update for this list was
october 2011. I assumed it was an inactive list. From logging on to
the actual server I can see that it is a very active list. I guess
Google has dropped IBMVM.

re:
http://www.garlic.com/~lynn/2012i.html#20 Vm & Zlinux VSWITCH question

Google gets its feed from usenet newsgroup ... these show up in the
bit.listserv "hierarchy" (reflect their bitnet ancestry) ... so the
mailing list has to have an active gateway to usenet newsgroup (like
ibm-main currently), however the ibmvm mailing list gateway to usenet
hasn't been active for some time.

note that mailing lists also have a digest mode ... posts are collected
into single email digest and usually distributed once a day (usually in
the middle of the night ... at least if you are continental US).

[Lutz Hamann]

Hi Ron,

very glad to hear that your problem is solved now and all works for you !

Sometimes a few explaining words are very usefull for further understanding
of manuals/presentations. At least that is my experience ...

If there should occure any further problems pls. feel free to address them on- or
offline :-)


ciao Lutz




----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN