Re: zLinux and IBM 3592-E05 tape drives

2006-10-03 Thread Tom Duerbusch
Thanks Allen

I sent in a request for the software.  I don't have the hardware, but I
can install the software on an image and read the manuals.

In the "Getting Started with zSeries Fibre Channel Protocol" Redpaper,
which was for z/800, z/900 processors, it answered my question.

There are 240 subchannels defined on a FCP port.  By giving one
subchannel per Linux image, effectively limiting the number of Linux
images that have access to FCP devices, all Linux images can have access
to the devices on the FC SAN.  

I think 240 zLinux images will be sufficient, for now.

I also see how they are mapped, from zLinux, to VM, to IOCP, to WWPN
and so on, and how the FC SAN switch works (reminds me of an Escon
Director).


Tom Duerbusch
THD Consulting
(all you really ever needed was a 370 mode processor and bus and tag
devices)

>>> [EMAIL PROTECTED] 10/2/2006 6:09 PM >>>
On Monday, 10/02/2006 at 04:41 EST, Tom Duerbusch 
<[EMAIL PROTECTED]> wrote:
> Not on a z9z/890...

Industry-standard N_Port ID Virtualization (NPIV) on the z9 is needed
if 
you want to apply zoning and LUN masking (FC access controls) to
virtual 
machines and/or LPARs just as they are for discrete systems.  With
NPIV, 
each FCP subchannel, rather than chpid, is assigned a unique WWPN. 
Matching support in the local FC switch is required.

On a z890 and z990 you can use the Linux-based FCP LUN Access Control 
utility to control guest/LPAR access to WWPNs and LUNs.  Even though
the 
other systems and switches see just one WWPN per FC chpid (and no
special 
switch support is needed), the utility instructs the FCP adapter to act
as 
a gatekeeper.  Read more about it on ResourceLink at 
https://www-1.ibm.com/servers/resourcelink/hom03010.nsf/pages/fcpaccumain?opendocument.

  (You get to this by navigating first to Tools and then selecting 
"Configuration Utility for FCP LUN Access Control" in the first
column.)

Alan Altmark
z/VM Development
IBM Endicott


Re: zLinux and IBM 3592-E05 tape drives

2006-10-03 Thread Marian Gasparovic
Tom,
yes, you can configure port to be in FCP or FICON
mode, so on one card you can use both protocols.

Marian Gasparovic
IBM Slovakia

--- Tom Duerbusch <[EMAIL PROTECTED]> wrote:

> OK, I'm reading this as one port of the 4 ports on
> my FICON adapter can be configured as a FCP Channel.
>  Is that correct?
> 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


Re: zLinux and IBM 3592-E05 tape drives

2006-10-03 Thread Tom Duerbusch
Wait a minutewh there...

I was under the impression that the difference between a Ficon card and a FCP 
card was the microcode.  AND a single card can not be used for both FICON and 
FCP connections.

However, the following from the FCP LUN Access Control utility seems to say the 
opposite:

"A zSeries 990 or 890 system with licensed internal code driver 55 and any 
required patches, and at least one FICON® Express card with an associated port 
configured as an FCP Channel in the IOCDS "

OK, I'm reading this as one port of the 4 ports on my FICON adapter can be 
configured as a FCP Channel.  Is that correct?

We currently have a single FICON card to our DS6800.  
We are going to acquire a second FICON card for reduncey and connect it to the 
DS6800.
I was going to take a port from each card and connect it to a proposed VTS.

Then I needed two FCP cards, for reduncy, for connection to the FC SAN thingie.

I can easily afford to take a port from each of my FICON cards for the FCP 
function, therefore eliminating the cost of the dual FCP cards.

So, is that something I can do?

Thanks

Tom Duerbusch
THD Consulting


>>> [EMAIL PROTECTED] 10/2/2006 6:09 PM >>>
On Monday, 10/02/2006 at 04:41 EST, Tom Duerbusch 
<[EMAIL PROTECTED]> wrote:
> Not on a z9z/890...

Industry-standard N_Port ID Virtualization (NPIV) on the z9 is needed if 
you want to apply zoning and LUN masking (FC access controls) to virtual 
machines and/or LPARs just as they are for discrete systems.  With NPIV, 
each FCP subchannel, rather than chpid, is assigned a unique WWPN. 
Matching support in the local FC switch is required.

On a z890 and z990 you can use the Linux-based FCP LUN Access Control 
utility to control guest/LPAR access to WWPNs and LUNs.  Even though the 
other systems and switches see just one WWPN per FC chpid (and no special 
switch support is needed), the utility instructs the FCP adapter to act as 
a gatekeeper.  Read more about it on ResourceLink at 
https://www-1.ibm.com/servers/resourcelink/hom03010.nsf/pages/fcpaccumain?opendocument.
 
  (You get to this by navigating first to Tools and then selecting 
"Configuration Utility for FCP LUN Access Control" in the first column.)

Alan Altmark
z/VM Development
IBM Endicott


Re: zLinux and IBM 3592-E05 tape drives

2006-10-02 Thread Alan Altmark
On Monday, 10/02/2006 at 04:41 EST, Tom Duerbusch 
<[EMAIL PROTECTED]> wrote:
> Not on a z9z/890...

Industry-standard N_Port ID Virtualization (NPIV) on the z9 is needed if 
you want to apply zoning and LUN masking (FC access controls) to virtual 
machines and/or LPARs just as they are for discrete systems.  With NPIV, 
each FCP subchannel, rather than chpid, is assigned a unique WWPN. 
Matching support in the local FC switch is required.

On a z890 and z990 you can use the Linux-based FCP LUN Access Control 
utility to control guest/LPAR access to WWPNs and LUNs.  Even though the 
other systems and switches see just one WWPN per FC chpid (and no special 
switch support is needed), the utility instructs the FCP adapter to act as 
a gatekeeper.  Read more about it on ResourceLink at 
https://www-1.ibm.com/servers/resourcelink/hom03010.nsf/pages/fcpaccumain?opendocument.
 
  (You get to this by navigating first to Tools and then selecting 
"Configuration Utility for FCP LUN Access Control" in the first column.)

Alan Altmark
z/VM Development
IBM Endicott


Re: zLinux and IBM 3592-E05 tape drives

2006-10-02 Thread Tom Duerbusch
Not on a z9z/890...

Tom Duerbusch
THD Consulting

>>> [EMAIL PROTECTED] 10/2/2006 3:50:17 PM >>>
Will reply with different detail on the LINUX-390 list,  where this was

cross posted.

The only ATTACH/DETACH in the traditional sense would be the FCP
channels. 
 They work  a lot  like ethernet adapters.  Think of them as OSAs and 
things begin to make more sense.  But they are called  "channels"  in
SAN 
land.  So then,  the tape drives in question are  "out there"  in the 
storage area network.  Attaching those is a different concept than CP 
ATTACH or DETACH.

Are you running a z9?  If not,  then all of your Linux guests will look

like the same mainframe to the SAN.

-- R;





Tom Duerbusch <[EMAIL PROTECTED]>
 
Sent by: The IBM z/VM Operating System 




10/02/2006 03:55 PM
Please respond to The IBM z/VM Operating System


From
Tom Duerbusch <[EMAIL PROTECTED]>
To
IBMVM@LISTSERV.UARK.EDU 
cc

Subject
zLinux and IBM 3592-E05 tape drives






We are thinking about buying some IBM 3592-E05 tape drives for the
Open
System group (well, actually, it's comming out of their budget), and
we
will put them in our, yet to be purchased IBM 3494 robotics unit.  The
tape drives will be dedicated to a FC SAN thingie.

Apparently, we can attach the mainframe to the FC SAN thingie, using
FCP connections.  Then, zLinux can have access to them.

As FCP tape drives are not known to VM.  And I have some 20-30 Linux
images running under VM, what is the procedure to attach/detach these
tape drives to each image?

Or is it something stupid, like I have to dedicate the drives to one
machine and then backup over vswitch from one machine to another to
the
tape drives?  (I say stupid, as backing up over "communications"
usually
takes more resources than backing up over hardwaredirectly to the
drives.)

Tom Duerbusch
THD Consulting


Re: zLinux and IBM 3592-E05 tape drives

2006-10-02 Thread Richard Troth

Will reply with different detail on
the LINUX-390 list,  where this was cross posted.

The only ATTACH/DETACH in the traditional
sense would be the FCP channels.  They work  a lot  like
ethernet adapters.  Think of them as OSAs and things begin to make
more sense.  But they are called  "channels"  in
SAN land.  So then,  the tape drives in question are  "out
there"  in the storage area network.  Attaching those is
a different concept than CP ATTACH or DETACH.

Are you running a z9?  If not,
 then all of your Linux guests will look like the same mainframe to
the SAN.

-- R;







Tom Duerbusch
<[EMAIL PROTECTED]>
 
Sent by:
The IBM z/VM
Operating System 




10/02/2006 03:55 PM
Please respond to The IBM z/VM Operating
System 




From
Tom Duerbusch <[EMAIL PROTECTED]>


To
IBMVM@LISTSERV.UARK.EDU


cc



Subject
zLinux and IBM 3592-E05
tape drives








We are thinking about buying some IBM 3592-E05 tape
drives for the Open
System group (well, actually, it's comming out of their budget), and we
will put them in our, yet to be purchased IBM 3494 robotics unit.  The
tape drives will be dedicated to a FC SAN thingie.

Apparently, we can attach the mainframe to the FC SAN thingie, using
FCP connections.  Then, zLinux can have access to them.

As FCP tape drives are not known to VM.  And I have some 20-30 Linux
images running under VM, what is the procedure to attach/detach these
tape drives to each image?

Or is it something stupid, like I have to dedicate the drives to one
machine and then backup over vswitch from one machine to another to the
tape drives?  (I say stupid, as backing up over "communications"
usually
takes more resources than backing up over hardwaredirectly to the
drives.)

Tom Duerbusch
THD Consulting



zLinux and IBM 3592-E05 tape drives

2006-10-02 Thread Tom Duerbusch
We are thinking about buying some IBM 3592-E05 tape drives for the Open
System group (well, actually, it's comming out of their budget), and we
will put them in our, yet to be purchased IBM 3494 robotics unit.  The
tape drives will be dedicated to a FC SAN thingie.

Apparently, we can attach the mainframe to the FC SAN thingie, using
FCP connections.  Then, zLinux can have access to them.

As FCP tape drives are not known to VM.  And I have some 20-30 Linux
images running under VM, what is the procedure to attach/detach these
tape drives to each image?

Or is it something stupid, like I have to dedicate the drives to one
machine and then backup over vswitch from one machine to another to the
tape drives?  (I say stupid, as backing up over "communications" usually
takes more resources than backing up over hardwaredirectly to the
drives.)

Tom Duerbusch
THD Consulting