Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-22 Thread Alan Altmark 
On Friday, 04/22/2016 at 04:50 GMT, Offer Baruch  
wrote:
> If you make sure you have NATIVE NONE and keep track of your grants 
(just
> like PORTBASED) there is no real security concern...
> The guest is only allowed the vlans you grant it (just like PORTBASED) 
and
> he cant send any untagged frames.
> I would rather manage a USERBASED VSWITCH with trunks over managing 
ports
> with PORTBASED any day...
> It is much easier to make vlan mistakes with PORTBASED... USERBASED is 
much
> more intuitive, easy to manage and easy to view...

To that end, there is work under way to simplify the configuration of 
PORTBASED VSWITCHes.  With the proposed configuration simplification, the 
only difference between the two is the explicit v. implicit port numbering 
scheme.  I think that can be consolidated back into a single VSWITCH.

> I agree you should close all the security holes before you do that... 
but
> that seems a better solution then PORTBASED.
>
> There are pro's and con's for everything but I would recommend USERBASED
> for security reasons and management reasons (assuming you know what you 
are
> doing).

At the end of the day, it's your choice.  The problem was that USERBASED 
did not address the explicit need to put two access port vNICs on the same 
VSWITCH in different VLANs.  The PORTBASED VSWITCH solved that problem, 
but introduced others.   Let's talk again after we've made some progress 
on the VSWITCH Reconciliation Project (Do you like the name?  I just made 
it up!)

Alan Altmark

Senior Managing z/VM and Linux Consultant
Lab Services System z Delivery Practice
IBM Systems & Technology Group
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-22 Thread Offer Baruch 
So,

If you make sure you have NATIVE NONE and keep track of your grants (just
like PORTBASED) there is no real security concern...
The guest is only allowed the vlans you grant it (just like PORTBASED) and
he cant send any untagged frames.
I would rather manage a USERBASED VSWITCH with trunks over managing ports
with PORTBASED any day...
It is much easier to make vlan mistakes with PORTBASED... USERBASED is much
more intuitive, easy to manage and easy to view...

I agree you should close all the security holes before you do that... but
that seems a better solution then PORTBASED.

There are pro's and con's for everything but I would recommend USERBASED
for security reasons and management reasons (assuming you know what you are
doing).

Offer Baruch
On Apr 22, 2016 6:19 PM, "Alan Altmark"  wrote:

> On Friday, 04/22/2016 at 07:07 GMT, Offer Baruch 
> wrote:
> > Can you please explain what is the problem with linux working in trunk
> mode?
> > What security problem are you talking about?
>
> An untrusted server should not be on a trunk port.  Ever.  A trunk can
> also carry untagged frames, and those frames will be associated with the
> *native* VLAN of the switch.  I can't get people to code "VLAN AWARE
> NATIVE NONE", so they are getting "NATIVE 1".  That means untagged frames
> from a VLAN-aware guest will be placed on VLAN 1, which is the default for
> most switch vendors, and is used to carry switch management traffic.  And
> to talk to other hosts attached to the default VLAN.
>
> I'm not sure if a physical switch port can have the native VLAN ID for
> that port excluded from the allowed VLANs, or if that will raise an error.
>  NATIVE NONE causes untagged frames to be dropped on trunking vNICs.  z/VM
> 6.1 and earlier don't have that capability, so be careful.
>
> Trunks are for switches, not hosts.  From the network's point of view, ALL
> hosts are evil.  Let us say that in order to save money, you are attaching
> multiple hosts to a trunked OSA port.  There are NO OSA controls on what
> LPARs can use what VLANs, so it must be assumed that the host can attach
> itself to any VLAN authorized for the port.
>
> In a VSWITCH, we don't have that problem.  However, VLAN IDs can and do
> change.  You don't want a VLAN-aware host to be accidentally left on the
> wrong VLAN.  Network People don't expect hosts to be using trunks without
> a Really Good Reason.
>
> Alan Altmark
>
> Senior Managing z/VM and Linux Consultant
> Lab Services System z Delivery Practice
> IBM Systems & Technology Group
> ibm.com/systems/services/labservices
> office: 607.429.3323
> mobile; 607.321.7556
> alan_altm...@us.ibm.com
> IBM Endicott
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-22 Thread Alan Altmark 
On Friday, 04/22/2016 at 07:07 GMT, Offer Baruch  
wrote:
> Can you please explain what is the problem with linux working in trunk 
mode?
> What security problem are you talking about?

An untrusted server should not be on a trunk port.  Ever.  A trunk can 
also carry untagged frames, and those frames will be associated with the 
*native* VLAN of the switch.  I can't get people to code "VLAN AWARE 
NATIVE NONE", so they are getting "NATIVE 1".  That means untagged frames 
from a VLAN-aware guest will be placed on VLAN 1, which is the default for 
most switch vendors, and is used to carry switch management traffic.  And 
to talk to other hosts attached to the default VLAN.

I'm not sure if a physical switch port can have the native VLAN ID for 
that port excluded from the allowed VLANs, or if that will raise an error. 
 NATIVE NONE causes untagged frames to be dropped on trunking vNICs.  z/VM 
6.1 and earlier don't have that capability, so be careful.

Trunks are for switches, not hosts.  From the network's point of view, ALL 
hosts are evil.  Let us say that in order to save money, you are attaching 
multiple hosts to a trunked OSA port.  There are NO OSA controls on what 
LPARs can use what VLANs, so it must be assumed that the host can attach 
itself to any VLAN authorized for the port.

In a VSWITCH, we don't have that problem.  However, VLAN IDs can and do 
change.  You don't want a VLAN-aware host to be accidentally left on the 
wrong VLAN.  Network People don't expect hosts to be using trunks without 
a Really Good Reason.

Alan Altmark

Senior Managing z/VM and Linux Consultant
Lab Services System z Delivery Practice
IBM Systems & Technology Group
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-22 Thread Offer Baruch 
Alan,
Can you please explain what is the problem with linux working in trunk mode?
What security problem are you talking about?

Thanks
Offer Baruch
On Apr 22, 2016 8:00 AM, "Alan Altmark"  wrote:

> On Friday, 04/22/2016 at 02:41 GMT, Grzegorz Powiedziuk
>  wrote:
> >
> > 3. Less common, useful in some cases - OSA is plugged into "trunk" port
> on
> > real switch and in general same as (2). But, when you do grant, you can
> say
> > that this specific grant should act as "porttype trunk" (and you specify
> > which vlans are trunked)  so VSWITCH instead of removing the vlan tag,
> > forwards the whole thing to linux guest. So linux guest should be
> > configured to receive and send tagged frames.  As Mark mentioned, during
> > install process it might be troublesome.
>
> Please don't do this.  Instead, use a PORTBASED VSWITCH so that you can
> two vNICs, each assigned to a different VLAN on the same VSWITCH.
>
> Except for a VSWITCH sniffer, there's no longer any need for Linux to be
> VLAN-aware when running as a guest.
>
> Alan Altmark
>
> Senior Managing z/VM and Linux Consultant
> Lab Services System z Delivery Practice
> IBM Systems & Technology Group
> ibm.com/systems/services/labservices
> office: 607.429.3323
> mobile; 607.321.7556
> alan_altm...@us.ibm.com
> IBM Endicott
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-21 Thread Alan Altmark 
On Friday, 04/22/2016 at 02:41 GMT, Grzegorz Powiedziuk 
 wrote:
>
> 3. Less common, useful in some cases - OSA is plugged into "trunk" port 
on
> real switch and in general same as (2). But, when you do grant, you can 
say
> that this specific grant should act as "porttype trunk" (and you specify
> which vlans are trunked)  so VSWITCH instead of removing the vlan tag,
> forwards the whole thing to linux guest. So linux guest should be
> configured to receive and send tagged frames.  As Mark mentioned, during
> install process it might be troublesome.

Please don't do this.  Instead, use a PORTBASED VSWITCH so that you can 
two vNICs, each assigned to a different VLAN on the same VSWITCH.

Except for a VSWITCH sniffer, there's no longer any need for Linux to be 
VLAN-aware when running as a guest.

Alan Altmark

Senior Managing z/VM and Linux Consultant
Lab Services System z Delivery Practice
IBM Systems & Technology Group
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-21 Thread Grzegorz Powiedziuk 
2016-04-21 16:29 GMT-04:00 Mark Post :

> >>> On 4/21/2016 at 03:38 PM, Grzegorz Powiedziuk 
> wrote:
> -snip-
> > I believe Mark said that having linux to handle vlan tagging is hard.
> >
> > But what you are trying to do is different. In your case, vswitch is
> > removing/adding vlan tags from/to  frames on the fly.
>
> If Grzegorz is correct in _his_ assumption, what he posted is a good
> description of what goes on and that _is_ something the installer can
> handle with no problems since from the guest's perspective it is not VLAN
> aware.
>
>
You're right. That is just assumption and after I read again the whole
thread I am not sure anymore  if this is what Dave wanted
So to give a full picture, you have three options ( simplified ):

1. Basic - Osa is plugged into "access" port on the real switch so there
are no vlan tags between real switch and OSA, and there are no vlan tags in
vswitch or linux. VSWITCH has to be set as "vlan unware".

2. Most common and useful - OSA is plugged into a "trunk" port on a real
switch. That port has to have vlan(s) added to it.  VSWITCH handles vlan
tags. So between vswitch (osa) and real switch the traffic is tagged with
vlan ids. Vswitch removes and adds vlan tags depending on direction.
Traffic between VSWITCH and linux guest is a untagged - standard network
frames. So from linux perspective it is like (1) . VSWITCH has to be set as
vlan AWARE and grants should have a vlan tag.

3. Less common, useful in some cases - OSA is plugged into "trunk" port on
real switch and in general same as (2). But, when you do grant, you can say
that this specific grant should act as "porttype trunk" (and you specify
which vlans are trunked)  so VSWITCH instead of removing the vlan tag,
forwards the whole thing to linux guest. So linux guest should be
configured to receive and send tagged frames.  As Mark mentioned, during
install process it might be troublesome.
In that case you might want to change it to (2) just for the install and
later configure vlan interface in the linux and redefine your grant to
porttype trunk afterwards.

Gregory

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-21 Thread Mark Post 
>>> On 4/21/2016 at 04:38 PM, Alan Altmark  wrote: 
> On Thursday, 04/21/2016 at 07:39 GMT, Grzegorz Powiedziuk 
>  wrote:
>> I believe Mark said that having linux to handle vlan tagging is hard.
> 
> There is nothing difficult about getting Linux to perform VLAN tagging. 
> The question is not one of capability, but of network security management.

Perhaps on an already-installed system.  Working around the limitations of the 
SLE11 installer can indeed be very difficult.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-21 Thread Alan Altmark 
On Thursday, 04/21/2016 at 07:39 GMT, Grzegorz Powiedziuk 
 wrote:
> I believe Mark said that having linux to handle vlan tagging is hard.

There is nothing difficult about getting Linux to perform VLAN tagging. 
The question is not one of capability, but of network security management.


> In your case, you let the vswitch to do vlan tagging and untaging. So
> vswitch has to be vlan aware so it can receive and understand tagged 
frames
> from the outside real, switch.
> When it receives a tagged frame from  the outside world it removes the 
vlan
> tag, and send the actual frame to guests which have  "granted" access to
> that speciffic vlan.  And when vswitch receives an untaged frame from
> guest, it adds a vlan tag to it and sends it to real switch (trunk port
> specifically) .
> So from linux perspective, there are no vlan tags and everything is nice 
an
> easy.

A nice explanation.

> define vswitch vlan aware vs vswitch .. vlan xxx I don't believe makes 
any
> difference in your case
> According to manual
> "defvid
> defines the virtual switch as a VLAN-aware switch supporting IEEE 
standard
> 802.lQ. The defvid defines the default VLAN ID to be assigned to guest
> ports when no VLAN ID is coded on the SET VSWITCH GRANT VLAN command"

Yes, there is a difference.  Please see my post.

Alan Altmark

Senior Managing z/VM and Linux Consultant
Lab Services System z Delivery Practice
IBM Systems & Technology Group
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-21 Thread Mark Post 
>>> On 4/21/2016 at 03:38 PM, Grzegorz Powiedziuk  
>>> wrote: 
-snip-
> I believe Mark said that having linux to handle vlan tagging is hard.
> 
> But what you are trying to do is different. In your case, vswitch is
> removing/adding vlan tags from/to  frames on the fly.

If Grzegorz is correct in _his_ assumption, what he posted is a good 
description of what goes on and that _is_ something the installer can handle 
with no problems since from the guest's perspective it is not VLAN aware.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-21 Thread Grzegorz Powiedziuk 
2016-04-21 14:52 GMT-04:00 Dave Myers :

> Since Mark has told us that what we're attempting to do is not supported
> by the RAM system...I'll close this thread and thank you all for your
> feedback.
>
> I do have one last question for Alan.
>
> In this statement does the VLAN AWARE specify TRUNKING to the uplink OSA ?
> If not what is the difference between what we coded VLAN 229 and  VLAN
> AWARE?
>
> DEFINE VSWITCH VSW1  RDEV 400.P1  VLAN AWARE  NATIVE NONE
>
> Thanks,
> Dave
>
>
I believe Mark said that having linux to handle vlan tagging is hard.

But what you are trying to do is different. In your case, vswitch is
removing/adding vlan tags from/to  frames on the fly.

To do what Mark mentioned (and I doubt this is what you want to do) you
have to specify porttype trunk when you do the grant command. This will let
linux guest to see vlan tags. But I am pretty sure that you don't want to
do this.

In your case, you let the vswitch to do vlan tagging and untaging. So
vswitch has to be vlan aware so it can receive and understand tagged frames
from the outside real, switch.
When it receives a tagged frame from  the outside world it removes the vlan
tag, and send the actual frame to guests which have  "granted" access to
that speciffic vlan.  And when vswitch receives an untaged frame from
guest, it adds a vlan tag to it and sends it to real switch (trunk port
specifically) .
So from linux perspective, there are no vlan tags and everything is nice an
easy.

So what you are doing, should work perfectly fine as long the real switch
is set up correctly (port is set to trunk and your vlan was added to it)

When it comes to syntax

define vswitch vlan aware vs vswitch .. vlan xxx I don't believe makes any
difference in your case
According to manual
"defvid
defines the virtual switch as a VLAN-aware switch supporting IEEE standard
802.lQ. The defvid defines the default VLAN ID to be assigned to guest
ports when no VLAN ID is coded on the SET VSWITCH GRANT VLAN command"


Gregory

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-21 Thread Alan Altmark 
On Thursday, 04/21/2016 at 06:59 GMT, Dave Myers 
 wrote:
> I do have one last question for Alan.
>
> In this statement does the VLAN AWARE specify TRUNKING to the uplink OSA 
?
> If not what is the difference between what we coded VLAN 229 and  VLAN 
AWARE?
>
> DEFINE VSWITCH VSW1  RDEV 400.P1  VLAN AWARE  NATIVE NONE

Yes, VLAN AWARE specifies trunking on the uplink.  The difference is that 
you authorized everyone who was not explicitly authorized to a VLAN to use 
VLAN 229, and I required everyone to have an explicit GRANT.

By the way, if you have an ESM and the ESM returns an empty list of VLANs, 
your syntax would give the guest access to VLAN 229.  [This is fixed in 
6.4.]

I've been harping on the use of "VLAN AWARE NATIVE NONE" for all z/VM 6.2 
and later systems since ... z/VM 6.2.  And I expect (hope?) that there are 
going to be some changes in the future to disable the use of a VLAN ID on 
the DEFINE VSWITCH.

Alan Altmark

Senior Managing z/VM and Linux Consultant
Lab Services System z Delivery Practice
IBM Systems & Technology Group
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-21 Thread Dave Myers 
Since Mark has told us that what we're attempting to do is not supported by the 
RAM system...I'll close this thread and thank you all for your feedback.

I do have one last question for Alan.

In this statement does the VLAN AWARE specify TRUNKING to the uplink OSA ?
If not what is the difference between what we coded VLAN 229 and  VLAN AWARE?

DEFINE VSWITCH VSW1  RDEV 400.P1  VLAN AWARE  NATIVE NONE

Thanks,
Dave



From: Dave Myers
Sent: Wednesday, April 20, 2016 10:37 PM
To: 'linux-390@VM.MARIST.EDU' <linux-390@VM.MARIST.EDU>
Subject: RE: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

Hi all,
I appreciate your help..please keep suggestions coming.
Marcy, the last post from you was not readable on the list.
Thanks,
Dave

From: Dave Myers
Sent: Wednesday, April 20, 2016 9:29 PM
To: 'linux-390@VM.MARIST.EDU' 
<linux-390@VM.MARIST.EDU<mailto:linux-390@VM.MARIST.EDU>>
Subject: RE: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

VLAN def in system config is:
define vswitch vsw1 rdev 400.p1  vlan 229

In LNXDFLT profile we have:

COMMAND SET VSWITCH VSW1 GRANT   VLAN 229
COMMAND DEFINE NIC 300 TYPE QDIO
COMMAND COUPLE 300 TO SYSTEM VSW1

When we logon to the guest from which we are executing the SLES11SP4, we get 
positive msgs that the vnic is coupled to the vswitch.



[cid:image001.gif@01D14C4B.903B2B30]

Dave Myers  |  Senior Systems Engineer - System z
Office: 303.996.7125 | Mobile: 303.619.0782 |  
dave.my...@siriuscom.com<mailto:dave.my...@siriuscom.com>
Sirius Computer Solutions | www.siriuscom.com<http://www.siriuscom.com/>
10100 Reunion Place, Suite 500, San Antonio, TX 78216



From: Dave Myers
Sent: Wednesday, April 20, 2016 8:56 PM
To: 'linux-390@VM.MARIST.EDU' 
<linux-390@VM.MARIST.EDU<mailto:linux-390@VM.MARIST.EDU>>
Subject: RE: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

The define VSWITCH and the COUPLE both produce no errors.  That part looks good.
Yes. We are using this VLAN for some z/OS interfaces, so it is not new.

The SLES11SP4 EXEC does not show any errors.
The only message we get, after a 1-2 minute hang in the SLES11SP4 EXEC is:
" unable to find ... repository".

When I switch to a different VLAN that is not trunked and I keep the same NFS 
location of the repository is works OK and finds my NFS server.



From: Dave Myers
Sent: Wednesday, April 20, 2016 7:19 PM
To: 'linux-390@VM.MARIST.EDU' 
<linux-390@VM.MARIST.EDU<mailto:linux-390@VM.MARIST.EDU>>
Subject: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

I am trying to install SLES11 SP4 under zVM VSWITCH.
The VSWITCH is attached to an OSA that is TRUNKED to a switch port.
We defined VLAN ID on the VSWITCH def and also on the GRANT ACCESS statement 
for the guest.
We cannot connect when we run the SLES11SP4  EXEC.

Does anyone know if this is supported for install by the SLES11 SP4 RAM system?
Or does anyone know how to debug this connection from the SLES11SP4  EXEC ?

Thanks,
Dave


This message (including any attachments) is intended only for the use of the 
individual or entity to which it is addressed and may contain information that 
is non-public, proprietary, privileged, confidential, and exempt from 
disclosure under applicable law. If you are not the intended recipient, you are 
hereby notified that any use, dissemination, distribution, or copying of this 
communication is strictly prohibited. This message may be viewed by parties at 
Sirius Computer Solutions other than those named in the message header. This 
message does not contain an official representation of Sirius Computer 
Solutions. If you have received this communication in error, notify Sirius 
Computer Solutions immediately and (i) destroy this message if a facsimile or 
(ii) delete this message immediately if this is an electronic communication. 
Thank you.

Sirius Computer Solutions<http://www.siriuscom.com>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-20 Thread Mark Post 
>>> On 4/20/2016 at 10:28 PM, Dave Myers  wrote: 
> VLAN def in system config is:
> define vswitch vsw1 rdev 400.p1  vlan 229

It's been a while since I played with this stuff, but one thing I know for 
sure: If the Linux guest has to be aware of which VLAN(s) it's supposed to be 
seeing, that is not supported by the installer.  You would need to manually 
intervene to set up the 802.1q parameters for it to work.

So, whether the VSWITCH itself is VLAN aware or not is irrelevant to the Linux 
guest.  As soon as the Linux guest itself needs to be VLAN aware, you're on 
your own.  (I've done it myself and it's not hard, but it _is_ outside of what 
the installer can handle automagicaly at the SLES11 SP4 level.)


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-20 Thread Marcy Cortes 
Not sure why I was unreadable but Alan covered me and more



Marcy

-Original Message-
From: Alan Altmark [alan_altm...@us.ibm.com<mailto:alan_altm...@us.ibm.com>]
Sent: Wednesday, April 20, 2016 10:56 PM Central Standard Time
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Install not working for SLES11 SP4 thru TRUNKED VSWITCH


On Thursday, 04/21/2016 at 02:29 GMT, Dave Myers
<dave.my...@siriuscom.com> wrote:
> VLAN def in system config is:
> define vswitch vsw1 rdev 400.p1  vlan 229

Gaaack!  Please use

DEFINE VSWITCH VSW1  RDEV 400.P1  VLAN AWARE  NATIVE NONE

Have your switch admin verify that
o The port 400.P1 is plugged into is configured as a trunk
o The port is configured for IEEE 802.1q (aka "DOT1Q"), not ISL or other
vendor-proprietary trunking protocol
o The port has been added to VLAN 229

Check QUERY VSWITCH VSW1 DETAILS and look at the TX, RX, DISCARD counts.

Alan Altmark

Senior Managing z/VM and Linux Consultant
Lab Services System z Delivery Practice
IBM Systems & Technology Group
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-20 Thread Alan Altmark 
On Thursday, 04/21/2016 at 02:29 GMT, Dave Myers 
 wrote:
> VLAN def in system config is:
> define vswitch vsw1 rdev 400.p1  vlan 229

Gaaack!  Please use

DEFINE VSWITCH VSW1  RDEV 400.P1  VLAN AWARE  NATIVE NONE

Have your switch admin verify that
o The port 400.P1 is plugged into is configured as a trunk
o The port is configured for IEEE 802.1q (aka "DOT1Q"), not ISL or other 
vendor-proprietary trunking protocol
o The port has been added to VLAN 229

Check QUERY VSWITCH VSW1 DETAILS and look at the TX, RX, DISCARD counts.

Alan Altmark

Senior Managing z/VM and Linux Consultant
Lab Services System z Delivery Practice
IBM Systems & Technology Group
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-20 Thread Dave Myers 
Hi all,
I appreciate your help..please keep suggestions coming.
Marcy, the last post from you was not readable on the list.
Thanks,
Dave

From: Dave Myers
Sent: Wednesday, April 20, 2016 9:29 PM
To: 'linux-390@VM.MARIST.EDU' <linux-390@VM.MARIST.EDU>
Subject: RE: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

VLAN def in system config is:
define vswitch vsw1 rdev 400.p1  vlan 229

In LNXDFLT profile we have:

COMMAND SET VSWITCH VSW1 GRANT   VLAN 229
COMMAND DEFINE NIC 300 TYPE QDIO
COMMAND COUPLE 300 TO SYSTEM VSW1

When we logon to the guest from which we are executing the SLES11SP4, we get 
positive msgs that the vnic is coupled to the vswitch.



[cid:image001.gif@01D14C4B.903B2B30]

Dave Myers  |  Senior Systems Engineer - System z
Office: 303.996.7125 | Mobile: 303.619.0782 |  
dave.my...@siriuscom.com<mailto:dave.my...@siriuscom.com>
Sirius Computer Solutions | www.siriuscom.com<http://www.siriuscom.com/>
10100 Reunion Place, Suite 500, San Antonio, TX 78216



From: Dave Myers
Sent: Wednesday, April 20, 2016 8:56 PM
To: 'linux-390@VM.MARIST.EDU' 
<linux-390@VM.MARIST.EDU<mailto:linux-390@VM.MARIST.EDU>>
Subject: RE: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

The define VSWITCH and the COUPLE both produce no errors.  That part looks good.
Yes. We are using this VLAN for some z/OS interfaces, so it is not new.

The SLES11SP4 EXEC does not show any errors.
The only message we get, after a 1-2 minute hang in the SLES11SP4 EXEC is:
" unable to find ... repository".

When I switch to a different VLAN that is not trunked and I keep the same NFS 
location of the repository is works OK and finds my NFS server.



From: Dave Myers
Sent: Wednesday, April 20, 2016 7:19 PM
To: 'linux-390@VM.MARIST.EDU' 
<linux-390@VM.MARIST.EDU<mailto:linux-390@VM.MARIST.EDU>>
Subject: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

I am trying to install SLES11 SP4 under zVM VSWITCH.
The VSWITCH is attached to an OSA that is TRUNKED to a switch port.
We defined VLAN ID on the VSWITCH def and also on the GRANT ACCESS statement 
for the guest.
We cannot connect when we run the SLES11SP4  EXEC.

Does anyone know if this is supported for install by the SLES11 SP4 RAM system?
Or does anyone know how to debug this connection from the SLES11SP4  EXEC ?

Thanks,
Dave


This message (including any attachments) is intended only for the use of the 
individual or entity to which it is addressed and may contain information that 
is non-public, proprietary, privileged, confidential, and exempt from 
disclosure under applicable law. If you are not the intended recipient, you are 
hereby notified that any use, dissemination, distribution, or copying of this 
communication is strictly prohibited. This message may be viewed by parties at 
Sirius Computer Solutions other than those named in the message header. This 
message does not contain an official representation of Sirius Computer 
Solutions. If you have received this communication in error, notify Sirius 
Computer Solutions immediately and (i) destroy this message if a facsimile or 
(ii) delete this message immediately if this is an electronic communication. 
Thank you.

Sirius Computer Solutions<http://www.siriuscom.com>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-20 Thread Marcy Cortes 
What does q vswitch show you?



Marcy

-Original Message-
From: Dave Myers [dave.my...@siriuscom.com<mailto:dave.my...@siriuscom.com>]
Sent: Wednesday, April 20, 2016 09:29 PM Central Standard Time
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Install not working for SLES11 SP4 thru TRUNKED VSWITCH


VLAN def in system config is:
define vswitch vsw1 rdev 400.p1  vlan 229

In LNXDFLT profile we have:

COMMAND SET VSWITCH VSW1 GRANT   VLAN 229
COMMAND DEFINE NIC 300 TYPE QDIO
COMMAND COUPLE 300 TO SYSTEM VSW1

When we logon to the guest from which we are executing the SLES11SP4, we get 
positive msgs that the vnic is coupled to the vswitch.



[cid:image001.gif@01D14C4B.903B2B30]

Dave Myers  |  Senior Systems Engineer - System z
Office: 303.996.7125 | Mobile: 303.619.0782 |  
dave.my...@siriuscom.com<mailto:dave.my...@siriuscom.com>
Sirius Computer Solutions | www.siriuscom.com<http://www.siriuscom.com/>
10100 Reunion Place, Suite 500, San Antonio, TX 78216



From: Dave Myers
Sent: Wednesday, April 20, 2016 8:56 PM
To: 'linux-390@VM.MARIST.EDU' <linux-390@VM.MARIST.EDU>
Subject: RE: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

The define VSWITCH and the COUPLE both produce no errors.  That part looks good.
Yes. We are using this VLAN for some z/OS interfaces, so it is not new.

The SLES11SP4 EXEC does not show any errors.
The only message we get, after a 1-2 minute hang in the SLES11SP4 EXEC is:
" unable to find ... repository".

When I switch to a different VLAN that is not trunked and I keep the same NFS 
location of the repository is works OK and finds my NFS server.



From: Dave Myers
Sent: Wednesday, April 20, 2016 7:19 PM
To: 'linux-390@VM.MARIST.EDU' 
<linux-390@VM.MARIST.EDU<mailto:linux-390@VM.MARIST.EDU>>
Subject: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

I am trying to install SLES11 SP4 under zVM VSWITCH.
The VSWITCH is attached to an OSA that is TRUNKED to a switch port.
We defined VLAN ID on the VSWITCH def and also on the GRANT ACCESS statement 
for the guest.
We cannot connect when we run the SLES11SP4  EXEC.

Does anyone know if this is supported for install by the SLES11 SP4 RAM system?
Or does anyone know how to debug this connection from the SLES11SP4  EXEC ?

Thanks,
Dave


This message (including any attachments) is intended only for the use of the 
individual or entity to which it is addressed and may contain information that 
is non-public, proprietary, privileged, confidential, and exempt from 
disclosure under applicable law. If you are not the intended recipient, you are 
hereby notified that any use, dissemination, distribution, or copying of this 
communication is strictly prohibited. This message may be viewed by parties at 
Sirius Computer Solutions other than those named in the message header. This 
message does not contain an official representation of Sirius Computer 
Solutions. If you have received this communication in error, notify Sirius 
Computer Solutions immediately and (i) destroy this message if a facsimile or 
(ii) delete this message immediately if this is an electronic communication. 
Thank you.

Sirius Computer Solutions<http://www.siriuscom.com>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-20 Thread Dave Myers 
VLAN def in system config is:
define vswitch vsw1 rdev 400.p1  vlan 229

In LNXDFLT profile we have:

COMMAND SET VSWITCH VSW1 GRANT   VLAN 229
COMMAND DEFINE NIC 300 TYPE QDIO
COMMAND COUPLE 300 TO SYSTEM VSW1

When we logon to the guest from which we are executing the SLES11SP4, we get 
positive msgs that the vnic is coupled to the vswitch.



[cid:image001.gif@01D14C4B.903B2B30]

Dave Myers  |  Senior Systems Engineer - System z
Office: 303.996.7125 | Mobile: 303.619.0782 |  
dave.my...@siriuscom.com<mailto:dave.my...@siriuscom.com>
Sirius Computer Solutions | www.siriuscom.com<http://www.siriuscom.com/>
10100 Reunion Place, Suite 500, San Antonio, TX 78216



From: Dave Myers
Sent: Wednesday, April 20, 2016 8:56 PM
To: 'linux-390@VM.MARIST.EDU' <linux-390@VM.MARIST.EDU>
Subject: RE: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

The define VSWITCH and the COUPLE both produce no errors.  That part looks good.
Yes. We are using this VLAN for some z/OS interfaces, so it is not new.

The SLES11SP4 EXEC does not show any errors.
The only message we get, after a 1-2 minute hang in the SLES11SP4 EXEC is:
" unable to find ... repository".

When I switch to a different VLAN that is not trunked and I keep the same NFS 
location of the repository is works OK and finds my NFS server.



From: Dave Myers
Sent: Wednesday, April 20, 2016 7:19 PM
To: 'linux-390@VM.MARIST.EDU' 
<linux-390@VM.MARIST.EDU<mailto:linux-390@VM.MARIST.EDU>>
Subject: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

I am trying to install SLES11 SP4 under zVM VSWITCH.
The VSWITCH is attached to an OSA that is TRUNKED to a switch port.
We defined VLAN ID on the VSWITCH def and also on the GRANT ACCESS statement 
for the guest.
We cannot connect when we run the SLES11SP4  EXEC.

Does anyone know if this is supported for install by the SLES11 SP4 RAM system?
Or does anyone know how to debug this connection from the SLES11SP4  EXEC ?

Thanks,
Dave


This message (including any attachments) is intended only for the use of the 
individual or entity to which it is addressed and may contain information that 
is non-public, proprietary, privileged, confidential, and exempt from 
disclosure under applicable law. If you are not the intended recipient, you are 
hereby notified that any use, dissemination, distribution, or copying of this 
communication is strictly prohibited. This message may be viewed by parties at 
Sirius Computer Solutions other than those named in the message header. This 
message does not contain an official representation of Sirius Computer 
Solutions. If you have received this communication in error, notify Sirius 
Computer Solutions immediately and (i) destroy this message if a facsimile or 
(ii) delete this message immediately if this is an electronic communication. 
Thank you.

Sirius Computer Solutions<http://www.siriuscom.com>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-20 Thread Alan Altmark 
On Thursday, 04/21/2016 at 01:56 GMT, Dave Myers 
 wrote:
> The define VSWITCH and the COUPLE both produce no errors.  That part 
looks good.
> Yes. We are using this VLAN for some z/OS interfaces, so it is not new.
>
> The SLES11SP4 EXEC does not show any errors.
> The only message we get, after a 1-2 minute hang in the SLES11SP4 EXEC 
is:
> " unable to find ... repository".
>
> When I switch to a different VLAN that is not trunked and I keep the 
same NFS
> location of the repository is works OK and finds my NFS server.

You mean, "switch to a different **VSWITCH** that is not trunked..." [not 
VLAN-aware], right?  All VLANs are "trunked".  If you're not trunking, 
then VLAN IDs aren't flowing.

Please provide the syntax you use to define your VLAN-aware VSWITCH.  I 
suspect that either the port is not in trunk mode, or you have the syntax 
incorrect.

Alan Altmark

Senior Managing z/VM and Linux Consultant
Lab Services System z Delivery Practice
IBM Systems & Technology Group
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-20 Thread Dave Myers 
The define VSWITCH and the COUPLE both produce no errors.  That part looks good.
Yes. We are using this VLAN for some z/OS interfaces, so it is not new.

The SLES11SP4 EXEC does not show any errors.
The only message we get, after a 1-2 minute hang in the SLES11SP4 EXEC is:
" unable to find ... repository".

When I switch to a different VLAN that is not trunked and I keep the same NFS 
location of the repository is works OK and finds my NFS server.



From: Dave Myers
Sent: Wednesday, April 20, 2016 7:19 PM
To: 'linux-390@VM.MARIST.EDU' <linux-390@VM.MARIST.EDU>
Subject: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

I am trying to install SLES11 SP4 under zVM VSWITCH.
The VSWITCH is attached to an OSA that is TRUNKED to a switch port.
We defined VLAN ID on the VSWITCH def and also on the GRANT ACCESS statement 
for the guest.
We cannot connect when we run the SLES11SP4  EXEC.

Does anyone know if this is supported for install by the SLES11 SP4 RAM system?
Or does anyone know how to debug this connection from the SLES11SP4  EXEC ?

Thanks,
Dave


This message (including any attachments) is intended only for the use of the 
individual or entity to which it is addressed and may contain information that 
is non-public, proprietary, privileged, confidential, and exempt from 
disclosure under applicable law. If you are not the intended recipient, you are 
hereby notified that any use, dissemination, distribution, or copying of this 
communication is strictly prohibited. This message may be viewed by parties at 
Sirius Computer Solutions other than those named in the message header. This 
message does not contain an official representation of Sirius Computer 
Solutions. If you have received this communication in error, notify Sirius 
Computer Solutions immediately and (i) destroy this message if a facsimile or 
(ii) delete this message immediately if this is an electronic communication. 
Thank you.

Sirius Computer Solutions<http://www.siriuscom.com>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-20 Thread Marcy Cortes 
Is anything else on your vswitch working or is this a new set up?
We run trunked ports and use the vlan on the grant statement with SP4 so that 
isn't an issue.

What messages are you getting?Did you get your default route right?  



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Dave Myers
Sent: Wednesday, April 20, 2016 5:19 PM
To: LINUX-390@VM.MARIST.EDU
Subject: [LINUX-390] Install not working for SLES11 SP4 thru TRUNKED VSWITCH

I am trying to install SLES11 SP4 under zVM VSWITCH.
The VSWITCH is attached to an OSA that is TRUNKED to a switch port.
We defined VLAN ID on the VSWITCH def and also on the GRANT ACCESS statement 
for the guest.
We cannot connect when we run the SLES11SP4  EXEC.

Does anyone know if this is supported for install by the SLES11 SP4 RAM system?
Or does anyone know how to debug this connection from the SLES11SP4  EXEC ?

Thanks,
Dave


This message (including any attachments) is intended only for the use of the 
individual or entity to which it is addressed and may contain information that 
is non-public, proprietary, privileged, confidential, and exempt from 
disclosure under applicable law. If you are not the intended recipient, you are 
hereby notified that any use, dissemination, distribution, or copying of this 
communication is strictly prohibited. This message may be viewed by parties at 
Sirius Computer Solutions other than those named in the message header. This 
message does not contain an official representation of Sirius Computer 
Solutions. If you have received this communication in error, notify Sirius 
Computer Solutions immediately and (i) destroy this message if a facsimile or 
(ii) delete this message immediately if this is an electronic communication. 
Thank you.

Sirius Computer Solutions<http://www.siriuscom.com>

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-20 Thread Scott Rohling 
What happens when you 'CP COUPLE nicaddress TO SYSTEM vswitchname'  from
this guests console?  If there's an error it may help troubleshoot..

You need to ensure you're connected to the VSWITCH -- does CP Q VSWITCH
vswitchname DETAILS show this guest connected?

Scott Rohling

On Wed, Apr 20, 2016 at 5:18 PM, Dave Myers 
wrote:

> I am trying to install SLES11 SP4 under zVM VSWITCH.
> The VSWITCH is attached to an OSA that is TRUNKED to a switch port.
> We defined VLAN ID on the VSWITCH def and also on the GRANT ACCESS
> statement for the guest.
> We cannot connect when we run the SLES11SP4  EXEC.
>
> Does anyone know if this is supported for install by the SLES11 SP4 RAM
> system?
> Or does anyone know how to debug this connection from the SLES11SP4  EXEC ?
>
> Thanks,
> Dave
>
>
> This message (including any attachments) is intended only for the use of
> the individual or entity to which it is addressed and may contain
> information that is non-public, proprietary, privileged, confidential, and
> exempt from disclosure under applicable law. If you are not the intended
> recipient, you are hereby notified that any use, dissemination,
> distribution, or copying of this communication is strictly prohibited. This
> message may be viewed by parties at Sirius Computer Solutions other than
> those named in the message header. This message does not contain an
> official representation of Sirius Computer Solutions. If you have received
> this communication in error, notify Sirius Computer Solutions immediately
> and (i) destroy this message if a facsimile or (ii) delete this message
> immediately if this is an electronic communication. Thank you.
>
> Sirius Computer Solutions
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-20 Thread Dave Myers 
I am trying to install SLES11 SP4 under zVM VSWITCH.
The VSWITCH is attached to an OSA that is TRUNKED to a switch port.
We defined VLAN ID on the VSWITCH def and also on the GRANT ACCESS statement 
for the guest.
We cannot connect when we run the SLES11SP4  EXEC.

Does anyone know if this is supported for install by the SLES11 SP4 RAM system?
Or does anyone know how to debug this connection from the SLES11SP4  EXEC ?

Thanks,
Dave


This message (including any attachments) is intended only for the use of the 
individual or entity to which it is addressed and may contain information that 
is non-public, proprietary, privileged, confidential, and exempt from 
disclosure under applicable law. If you are not the intended recipient, you are 
hereby notified that any use, dissemination, distribution, or copying of this 
communication is strictly prohibited. This message may be viewed by parties at 
Sirius Computer Solutions other than those named in the message header. This 
message does not contain an official representation of Sirius Computer 
Solutions. If you have received this communication in error, notify Sirius 
Computer Solutions immediately and (i) destroy this message if a facsimile or 
(ii) delete this message immediately if this is an electronic communication. 
Thank you.

Sirius Computer Solutions

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/