Re: SAN questions
We have used direct connect SAN disk with NPIV and currently our production servers use that method for the data lun whereas the boot and root are minidisks on EDEV SAN disk. Our initial implementations were all direct connect SAN disk using NPIV. We are transitioning to all EDEV over the next month as we are satisfied it performs as well as we need and it buys us the more simple multipathing and disaster recovery definitions in VM instead of making definitions within linux for each guest. We have never used standard CKD. We do not have IBM SVC (EMC DMX3 VMAX with Cisco switches). For monitoring the storage definitions we use Velocity to report on the disk. Craig Collins State of WI, DOA, DET On Thu, Jul 14, 2011 at 1:27 PM, Ron Wells ron.we...@slfs.com wrote: sure would From: Rick Troth r...@casita.net To: LINUX-390@VM.MARIST.EDU Date: 07/14/2011 01:18 PM Subject:SAN questions Sent by:Linux on 390 Port LINUX-390@VM.MARIST.EDU gang -- To those using SAN with Linux-on-z, are you using direct guest in the fabric (dedicated FCPs, where Linux sees the storage)? How do you keep track of storage? Is there an SVC in the mix? What do you like about it? (or dislike) Are you using EDEV? Why or why not? I plan to update my SAN for z/VM (and zLinux) presentation for the workshop. Would like to hear some current tails and terrors. Thanks. -- R; -- 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/ -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. -- 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: LVM on CKD?
Thank you everyone for your confirmation and instructions. It threw off our Linux Support person when YaSt wouldn't keep the LVM option on the disk as he was doing the install. Following the suggestions we were able to configure it and it is working now. Craig Collins State of WI, DOA, DET On Thu, Jun 9, 2011 at 7:24 AM, Ayer, Paul W pwa...@statestreet.com wrote: I find that fdasd /dev/dasd_ shows Linux Native for a dasdfmt disks and it shows Linux LVM LVM after you do a pvcreate command to the disk. Using p to look at the partitions and q to not change them ... Command action m print this menu p print the partition table n add a new partition d delete a partition v change volume serial t change partition type r re-create VTOC and delete all partitions u re-create VTOC re-using existing partition sizes s show mapping (partition number - data set name) q quit without saving changes w write table to disk and exit Paul -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Shane G Sent: Wednesday, June 08, 2011 7:44 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: LVM on CKD? On Thu, Jun 9th, 2011 at 6:12 AM, Mark Post wrote: To be honest, I don't think LVM itself cares about the partition type. pvcreate will use any partition you point it at. This is unfortunately (almost unbelievably) true - with the notable exception of swap. Regardless of the partition type of a swap extent, pvcreate recognises the swap header and will query you before trashing it. Any other partition type - including those with valid filesystems and data - will be fair game. Shane ... (N.B. - not (re-)verified on z/) -- 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/ -- 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/
LVM on CKD?
Is anyone using an LVM configuration with CKD or EDEV devices? We're trying to install SLES11 SP1 on EDEVs and wanted to setup a data LUN using LVM but YaSt keeps changing the type to native linux when we set it to LVM. Not sure if we are doing something wrong or LVM is not supported on these types of devices. Craig Collins State of WI, DOA, DET -- 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: rescue mode
We run the install exec again for the server to get linux up and then putty into it. Just make sure you don't have any sort of automated install setup for it otherwise you will reinstall the operating system. We don't use the SLES 11 AUTOINST parameter so we don't run into that issue. You'll need to sign into the server on the ip address listed in the install parameters using the userid and password listed in the parameters. Once in, you will need to mount the server's disk in order to do any updates. Shut it down and reboot when done. Craig Collins State of WI, DOA, DET On Wed, Jun 1, 2011 at 9:37 AM, Mauro Souza thoriu...@gmail.com wrote: I think you don't have to go into single user mode. I guess you'd put some disk on fstab, and it doesn't come online, putting your system on read-only rescue mode. If I am right, you can do this: *mount -o remount,rw /* *grep -v 'problematic disk' /etc/fstab /etc/fstab.1* *cat /etc/fstab.1* if the new fstab is fine, do this: *mv /etc/fstab.1 /etc/fstab* *reboot* Mauro http://mauro.limeiratem.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. On Wed, Jun 1, 2011 at 11:24 AM, Testa, Richard richard.te...@doit.nh.govwrote: Hello, How do you boot into single user/rescue mode on zlinux...I need to edit the fstab file, and it is in read only mode(maintenance)I tried the following but getting an error... CP VI VMSG 0 SINGLE Best Regards Richard Testa OIT-Operation Unix Systems Administrator NH Department of Information Technology 603-271-5460 (w) 603-235-2659 (c) www.nh.gov/doit -- 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/ -- 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: Storage Options
We are using or have used McData 3232, McData i10k, and Cisco 9513 switches for zSeries Fiber Channel connectivity to our SAN storage. We have used these to communicate with EMC Clariion, DMX3, VMAX, and HDS TagmaStore disk subsystems. Currently we are using the Cisco 9513 switches with EMC VMAX for the zLinux and z/VM disk LUN connectivity. We use NPIV and have some of the LUNs defined directly in the zLinux guests as FBA devices and others defined as EDEVs in z/VM which we then assign to the zLinux guests as minidisks. For ease of definition related to disaster recovery scenarios we have decided to migrate all of our servers over time to using the EDEV minidisks, knowing that there could be performance implications but our IO rates are low enough that we are not concerned. Just to clarify, there is no FICON involved in these connections as they are all Fiber Channel. The zSeries channels can be used for native FC or FICON connections. If you want to use NPIV, which I highly recommend, then you need to set the NPIV on for each LPAR where you are using it through the HMC with the channel offline to all LPARs. Craig Collins State of WI, DOA, DET On Thu, May 12, 2011 at 7:52 AM, Davey, Clair cda...@scspa.com wrote: What model of switches are people using for Ficon to Fiber Channel connectivity to your SANS? The contents of this e-mail are confidential to the ordinary user of the e-mail address to which it was addressed and may also be privileged. If you are not the addressee of this e-mail you should not copy, forward, disclose or otherwise use it or any part of it in any form whatsoever. If you have received this e-mail in error, please notify us by telephone or e-mail the sender by replying to this message, and then delete this e-mail and other copies of it from your computer system. We reserve the right to monitor all e-mail communications through our network. -- 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: FBA/SCSI vs ECKD zLinux on VM
I'd recommend you also look at using Emulated FBA devices as long as you are considering alternatives. They are defined as EDEVs under z/VM. when you compare the options. Know that the largest size devices is around 300 GB, I've forgotten the exact size. It's an option to be aware of for a number of reasons including multipathing and disaster recovery, if you need those, without the requirements that disk be defined as CKD. As already stated by Christian Paro, recognize the performance aspects between all of the options and the requirements of your workloads. We currently use EDEV FBA devices for boot/root/swap and linux server managed FBA/SCSI for data LUNs, but continue to think about moving it all to EDEV FBA definitions. Craig Collins State of WI On Fri, Mar 11, 2011 at 12:00 PM, Christian Paro christian.p...@gmail.comwrote: A full set of benchmarks for different disk technologies with z/VM: http://www.vm.ibm.com/perf/reports/zvm/html/520dasd.html On Fri, Mar 11, 2011 at 12:57 PM, Donald Russell russell@gmail.com wrote: I currently have a dozen or so RHEL 5.6 zLinux running on multiple VM 6.1 (well, 5, but 6.1 RSN), on z10 processors. The largest (disk space) is about 3TB and is currently FBA/SCSI We're thinking of changing this to ECKD to take advantage of the SAP to do the real IO, instead of IO being handled within zLinux itself. (We have other zLinux system using ECKD) On one hand using ECKD will get us some CPU cycles back due to more work being done by the SAP, but just recenly I heard that IO can be faster (higher throughput) with FBA/SCSI. I'm assuming there's no clear answer as to which is best, because like so many performance tuning things, the answer is always it depends. But, what are other people doing? My experience so far seems to be that the choice of SCSI or ECKD depends on the background of the people making the decision people with a s390 background are familiar with ECKD, people coming from a unix/linux background are familiar with SCSI.. Thank you -- 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/ -- 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: TSM server
Yes, we actually worked with our account team from IBM and they brought in some of the IBM experts to help us take a closer look at this. It was determined that the additional memory was needed due to the database change between the two versions. Given enough memory, I think it would work fine. We decided the best alternative for us was to move it off of zSeries, that it wasn't the best fit for z/Linux. On Tue, Mar 8, 2011 at 7:17 PM, Alan Altmark alan_altm...@us.ibm.comwrote: On Tuesday, 03/08/2011 at 08:51 EST, Craig Collins grizl...@gmail.com wrote: We were using zLinux to host TSM servers with TSM release 5.5 and were happy with performance and memory consumption. We backed-up 100s of servers a night using a z10 processor with multiple IFLs. Once we upgraded to TSM 6.1, the memory consumption became prohibitive (8+ GB). We kept increasing the memory allocations and even after going through all of the DB2 performance tuning parameters for TSM 6.1, we could no longer justify the additional memory cost as compared to stand alone servers for TSM 6.1 so we have moved TSM off of zLinux. When you observe this sort of behavior, be certain to open a PMR with the application owner (TSM in this case) and bring your account team or business partner into the loop. Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training 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: TSM server
We were using zLinux to host TSM servers with TSM release 5.5 and were happy with performance and memory consumption. We backed-up 100s of servers a night using a z10 processor with multiple IFLs. Once we upgraded to TSM 6.1, the memory consumption became prohibitive (8+ GB). We kept increasing the memory allocations and even after going through all of the DB2 performance tuning parameters for TSM 6.1, we could no longer justify the additional memory cost as compared to stand alone servers for TSM 6.1 so we have moved TSM off of zLinux. Craig Collins State of WI On Thu, Mar 3, 2011 at 2:39 PM, Melancon, Ruddy melanc...@dot.state.al.uswrote: We are in the process of bringing up a Tivoli Storage Manager [TSM] server using zLinux [SLES11] under zVM [6.2]. We are going to use the IBM7650G with XIV back end storage to provide Virtual Tape. The idea is to backup intel servers directly to tape then replicate to remote DR site. We have run into problems with memory allocations. We were using 2GB memory with 750MB of swap space in vdev. We started getting sql errors with the indication that it was a memory or swap space issue. I have increased the memory to 3GB and now the image will only allow us to run 11 TSM processes before getting errors. This will not be good for production. I will increase this to 4 GB memory with 2GB of swap space to see what happens. Does anyone have experience and/or recommendations as to the correct settings for memory allocations? Ruddy A. Melancon IT Systems Specialist, Senior Alabama Department of Transportation 334-353-6323 -- 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: EDEV FBA disks and Cloning
We created the golden image server on EDEV FBA disk as well so our clone is from EDEV FBA to EDEV FBA. I presume if we are using the CMS FORMAT/RESERVE sequence we should do so for the source golden image build as well as the clone system before copying. When we tried using dd to clone, I watched the VM console for the server and there are many block errors during the copies. This was before we rebuilt using the FORMAT/RESERVE. I'm going to try that next. We'll rebuild the golden image after formatting the disk with that method and then try the clone again. I'll update with results when we complete that work. -- 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: EDEV FBA disks and Cloning
1. rebuilt the golden image, preparing the disk with CMS FORMAT RESERVE on EDEV FBA mini-disks 2. prepared the clone system disk with CMS FORMAT RESERVE on EDEV FBA mini-disks 3. Altered the clonerw.sh script so that it recognized the disk as FBA instead of CKD to get the device names and deleted the format section of the script. 4. ran the clonerw.sh script and through the ssh session, it gave no error messages, however on the VM guest console we received many iterations of the following messages for each device during the dd copy command executions: Buffer I/O error on device dasdc, logical block 4547 lost page write due to I/O error on dasdc end_request: I/O error, dev dasdc, sector 36400 Mar 3 08:28:14 S11CLONE kernel: end_request: I/O error, dev dasdc, sector 77016 5. tried booting the clone but expected failure due to I/O errors and as expected the boot failed 6. Under CMS, used DDR to copy each of the EDEV FBA disks from the golden image to the clone 7. Clone server booted without issue. Working on some parts of boot.findself script to set the ifcfg-eth0 ip address that don't appear to be working, but the server came up without an error. So, we have a method to make the clone, but the clonerw.sh script doesn't seem to work with this disk without further modifications that we can't figure out at this point. On Thu, Mar 3, 2011 at 10:12 AM, Mark Post mp...@novell.com wrote: On 3/2/2011 at 03:47 PM, Richard Troth vmcow...@gmail.com wrote: There is a lot of confusion about 'dasdfmt' versus 'mkfs'. If you already know the difference, please excuse this note. Rick, Do me a favor and stick this out on the wiki (after editing it a bit for style). I think this would be useful for others that might trip across it and don't know about this listserve. 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/ -- 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: EDEV FBA disks and Cloning
the script does have the sync command executing after the copy with dd completes -- 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: EDEV FBA disks and Cloning
FYI - the problem we were having with the boot.findself script had to do with upper/lower case matching issues when the script interrogated the sles11 parameter files searching for the source and destination server names and ip addresses. So, the script worked fine once we matched the cases to what the script expected as it scanned the parameters. -- 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/
EDEV FBA disks and Cloning
We're walking through the IBM doc Sharing and Maintaining SLES11 Linux under z/VM using DCSSs and an NSS but using EDEV FBA devices instead of native CKD devices. We've move to the point where we are making our first cloned copy and are running into issues. The original script identifies the CKD disk mount points, then uses 'dasdfmt' to format the destination CKD devices and 'dd' to do a block copy from the source to the destination devices. We've altered the script to identify the FBA devices, format them with 'mkfs' and then use the 'dd' to perform the block copy. When we try to boot the cloned copy, we don't even get the boot menu, it just fails with HCPGIR453W CP entered; program interrupt loop. If we copy the devices from within CMS using DDR, the destination server boots successfully following the copy. Does anyone successfully clone servers using scripts run from within a running linux clone server for EDEV FBA devices? I'd also be interested in hearing from anyone who has used EDEV FBA devices to generate sles11 servers which share read-only portions of the boot root partitions without DCSS NSS related to what they segment off for each server to use read-write locally. We think that's more likely the scenario we would want to go with, but we are walking through the above named document to get familiar with that method as a possibility. Craig Collins State of WI, DOA, DET -- 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/
Autoyast SWAPGEN SLES11
We're in the processes of testing out using the autoyast facility to build repeatable linux servers. We built a SLES11 server through the normal install process, customized it, and then produced the autoyast.xml file for use with building replica systems. However we are having a hard time figuring out how to modify the autoyast.xml file to account for the virtual swap disk built with SWAPGEN. Has someone already been through this process, and if so would you share the modifications required so we don't need to reinvent the wheel. It appears that the generated autoyast.xml is trying to format the SWAPGEN created disk and that is causing the install process to abend. Thanks, Craig Collins State of WI -- 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
OSA-Express3 10 Gb, Vswitch, and SLES10 Linux Throughput
We are just starting to use OSA-Express3 10 Gb ports for SLES10-SP2 Linux guests. We're trying to use these with TSM servers running on SLES10 to backup other non-zSeries servers in our environment. We are using the 10 Gb OSAs connected to VSWITCHes in zVM 5.4. Currently we have only one SLES10 TSM server connected to a VSWITCH that is the only thing connected to a 10 Gb OSA and are seeing throughput of less than 1 Gb/s. The Cisco switch the OSA port is connected to recognizes the speed as 10 Gb. The TSM server and all of the servers it is backing up are on the same subnet and there is no firewall involved. Thanks to linuxvm.org, we found Share presentation 2192 by Mario Held from August 2009 named Linux on System z Performance Update - Part 2: Networking and Crypto which we found helpful and we have altered some of our settings based upon the recommendations. We also have been over the OSA and Vswitch documentation from IBM looking for any speed settings related to this type of OSA card, a VSWITCH, or a nic definition for a linux guest on zVM, but did not find anything. We still are not getting throughput we expect (or maybe desire). We wondered if a nic setting in SLES10 could be keeping the connection from getting above the 1 Gb/s mark, but cannot find a parameter to change as the normal parameters with ethtool don't seem to apply in this environment. Is anyone else using a 10 Gb OSA through a VSWITCH and getting throughput greater than 1 Gb for a single server instance? If so, are there any settings you needed to change to get to that performance level? Or is there a maximum of around 1 Gb that a single server instance can achieve? We're grasping at straws at this point. Any ideas are appreciated. Craig Collins State of WI, DOA, DET -- 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
Re: OSA-Express3 10 Gb, Vswitch, and SLES10 Linux Throughput
The other thing we will need to do is set the vlanid since we wont be doing that through the vswitch as we have been up until now. We found the command to do that against the nic definition, which is what I am guessing we will need to do after everything is setup with the bonding. Thanks for the info and the quick responses. Craig Collins State of WI, DOA, DET -- 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
Re: SLES 11 Install Issue
Mark, thanks for the tip about having both SSH and VNC available. I pulled the following from the end of the y2log. We've also opened an issue with Novell. 2009-04-14 08:14:12 1 ZVMTST21(2784) [YCP] PackageCallbacks.ycp:1930 Downloading ftp://s...@xx.xx.199.4/../../nfs/sles11/DVD1/media.1/media to /var/adm/mount/AP_0x0001/media.1/media 2009-04-14 08:14:12 1 ZVMTST21(2784) [YCP] URL.ycp:322 Escaped username 'sles' = 'sles' 2009-04-14 08:14:12 1 ZVMTST21(2784) [YCP] Progress.ycp:587 Resetting the subprogressbar... 2009-04-14 08:14:12 3 ZVMTST21(2784) [zypp] MediaCurl.cc(doGetFileCopy):1284 curl error: 18: transfer closed with 62 bytes remaining to read, temp file size 0 byte. 2009-04-14 08:14:12 1 ZVMTST21(2784) [zypp] PathInfo.cc(_Log_Result):292 unlink /var/adm/mount/AP_0x0001/media.1/media.new.zypp.w9kXm4 2009-04-14 08:14:12 5 ZVMTST21(2784) [zypp] Exception.cc(log):133 MediaCurl.cc(doGetFileCopy):1401 THROW:MediaCurl.cc(doGetFileCopy):1401: Download (curl) error for 'ftp://sles @xx.xx.199.4/../../nfs/sles11/DVD1/media.1/media': 2009-04-14 08:14:12 5 ZVMTST21(2784) [zypp] Exception.cc(log):133 Error code: Unrecognized error 2009-04-14 08:14:12 5 ZVMTST21(2784) [zypp] Exception.cc(log):133 Error message: transfer closed with 62 bytes remaining to read 2009-04-14 08:14:12 5 ZVMTST21(2784) [zypp] Exception.cc(log):133 2009-04-14 08:14:12 5 ZVMTST21(2784) [zypp] Exception.cc(log):133 MediaCurl.cc(doGetFileCopy):1406 RETHROW: MediaCurl.cc(doGetFileCopy):1401: Download (curl) error for 'ftp://sles @xx.xx.199.4/../../nfs/sles11/DVD1/media.1/media': 2009-04-14 08:14:12 5 ZVMTST21(2784) [zypp] Exception.cc(log):133 Error code: Unrecognized error 2009-04-14 08:14:12 5 ZVMTST21(2784) [zypp] Exception.cc(log):133 Error message: transfer closed with 62 bytes remaining to read 2009-04-14 08:14:12 5 ZVMTST21(2784) [zypp] Exception.cc(log):133 We'll see what turns up. Craig Collins State of WI -- 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
SLES 11 Install Issue
Using these parameters:ramdisk_size=65536 root=/dev/ram1 ro init=/linuxrc TERM=dumb Hostname= Gateway=yy.yy.199.1 HostIP=yy.yy.199.21 Nameserver=none InstNetDev=osa Netmask=255.255.255.0 Broadcast=yy.yy.199.255 OsaInterface=qdio OsaMedium=eth Layer2=0 ReadChannel=0.0.a100 WriteChannel=0.0.a101 DataChannel=0.0.a102 Portname=DEFNIC Install=ftp://yy.yy.199.4/../../nfs/sles11/DVD1 linuxrcstderr=/dev/console UseSSH=1 SSHPassword=password username=root password=pass123 We are getting the error: eth0 activated hostip: yy.yy.199.21 gateway: yy.yy.199.1 loading ftp://yy.yy.199.4/../../nfs/sles11/DVD1/content - /content error 9: Server denied you to change to the given directory When I look at the directory yy.yy.199.4/../../nfs/sles11/DVD1 I do find a file named content but not a directory, which it appears the install is searching for. Has anyone run across this or do you have any suggestions? Craig Collins State of Wisconsin -- 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
Re: SLES 11 Install Issue
Actually, specifying the userid password as part of the ftp specification got us past that problem. We're using the base ftp service that comes with redhat 5 that we also used to serve up sles10 without specifying the userid and password on the ftp parm itself. So it appears to be reacting differently between sles10 sles11. Now, we are receiving an error after starting the install through yast using vnc that the sles11/DVD1/media.1/media failed, unrecognizable error, transfer closed with 62 bytes remaining to be read. I'm wondering if we should download the media again from Novell. Maybe our copy is incomplete/corrupt. Craig Collins State of WIsconsin On Mon, Apr 13, 2009 at 11:29 AM, Mark Post mp...@novell.com wrote: On 4/13/2009 at 11:30 AM, Mark Pace mpac...@gmail.com wrote: They have changed the format of the install paramters. I don't believe so. Use Install=ftp://username:passw...@ipaddress/root That format, or the individual specification of userid and password (for non-anonymous access) has worked for me. 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 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
Re: SLES 11 Install Issue
We downloaded the media again and re-deployed it on the ftp server, but we still received the media failure error. Any ideas? On Mon, Apr 13, 2009 at 12:09 PM, Craig Collins grizl...@gmail.com wrote: Actually, specifying the userid password as part of the ftp specification got us past that problem. We're using the base ftp service that comes with redhat 5 that we also used to serve up sles10 without specifying the userid and password on the ftp parm itself. So it appears to be reacting differently between sles10 sles11. Now, we are receiving an error after starting the install through yast using vnc that the sles11/DVD1/media.1/media failed, unrecognizable error, transfer closed with 62 bytes remaining to be read. I'm wondering if we should download the media again from Novell. Maybe our copy is incomplete/corrupt. Craig Collins State of WIsconsin On Mon, Apr 13, 2009 at 11:29 AM, Mark Post mp...@novell.com wrote: On 4/13/2009 at 11:30 AM, Mark Pace mpac...@gmail.com wrote: They have changed the format of the install paramters. I don't believe so. Use Install=ftp://username:passw...@ipaddress/root That format, or the individual specification of userid and password (for non-anonymous access) has worked for me. 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 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
Re: Cloning FCP-only Linuxes
Yes, we've cloned FCP-only NPIV SLES 10 zLinux systems and have a set of procedures we've written to do so. They are a little raw but I would be willing to share them with you. Drop me a direct email if you want a copy. Craig Collins State of WI, DOA, DET craig.coll...@wi.gov On Fri, Oct 24, 2008 at 8:06 PM, Romanowski, John (OFT) john.romanow...@oft.state.ny.us wrote: I've cloned a lot of non-NPIV, FCP-only SLES 9 and 10's. It's more work than cloning dasd mainly due to the LUN numbers, their wwpn's and serial numbers being absolute and not static virtual values like mdisk addresses. The golden image's LUN values are in various files and have to be changed on the new LUN to the new LUN's values after cloning. Also, set the new guest's LOADDEV wwpn and LUN number in its CP directory definition. This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Lee Stewart Sent: Friday, October 24, 2008 6:24 PM To: LINUX-390@VM.MARIST.EDU Subject: Cloning FCP-only Linuxes Hi... Has anyone had any luck cloning FCP-only Linuxes? No ECKD/FBA/EDEV disks, just SAN disks on FCP. Thanks, Lee -- Lee Stewart, Senior SE Sirius Computer Solutions Phone: (303) 798-2954 Fax: (720) 228-2321 Email: lee.stew...@siriuscom.com Web: 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 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 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
Re: z/Linux cloning
Is anyone doing cloning of FCP LUNs under SLES10 SP2, not minidisks? We're looking at how we might clone our systems which are all using FCP for all of the LUNs. The virtualizaiton cookbooks all refer to using DDR and minidisks. We figure if we can work out a good way to copy the partitions from golden image LUN to clone image LUN, we can work through the rest of the script to make the necessary alterations to the guest. We're trying to stay away from subsystem provided flashcopy type functions due to licensing costs. Craig Collins State of WI -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Synchronous remote copy FCP disk and DR
Yes, we run mkintrd each time before zipl. But the zipl wouldn't work properly because the zipl.conf was not correct, nor was the boot directory built properly. Based upon our tests, when we selected by-uuid, the install process would not properly build the zipl.conf or the entire boot directory. We tried this a couple of times to ensure it wasn't just operator error and a missed parameter setting during the boot. So, we went on to the next option of re-installing and setting the disk mapping to be by-name. This time it built the zipl.conf and boot directory structure properly, just like when we took the default setting of by-path. We were then able to use this new configuration to boot from either instance of our FCP connected LUN on either our production storage subsystem or through the disaster recovery storage subsystem (synchronous remote copy pair, split for boot test), and get the proper mount points built. Now we just need to figure out if there is a way to alter our previously installed production guests to utilize the by-name setting instead of the by-path setting in order to be ready for a DR situation. We'd rather not need to reinstall for those guests. On Tue, Jul 1, 2008 at 11:33 AM, Mark Post [EMAIL PROTECTED] wrote: On Tue, Jul 1, 2008 at 10:05 AM, in message [EMAIL PROTECTED], Craig Collins [EMAIL PROTECTED] wrote: We tried the cms console command and the tried setting up our fstab and zipl.conf using the by-uuid definitions and still it appears to be looking for the by-id definition during boot and so it is still tied to the physical device serial number. Did you re-run mkinitrd before zipl? Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Synchronous remote copy FCP disk and DR
We're wondering if anyone has any experience with disaster recovery of the zLinux guests when using FCP disk. For a variety of reasons, we chose to use the NPIV FCP disk instead of CKD for our Linux guests, including boot LUNs. The disk is synchronously remote copied between data centers. As part of our disaster recovery planning, we started to think about being able to boot off of the mirrored copy of the LUNs. When we built our guest to test DR with, we make both the primary LUNs and what will be the remote copy LUNs active to the guest and define them within Linux. We then made the remote copy LUNs unavailable to the guest by synchronizing the primary and remote copy LUNs. We made updates, shutdown the guest, split the disk, changed the switch zoning so that the primary disk was unavailable and only the disaster recovery disk was detected. It appears that the fstab entries, zipl.conf, bootmapper, and likely other configuration items, use the subsystem serial number as part of the identification for the partitions on the FCP disk in SLES10. Since the serial number for the remote subsystem is different from the primary, when we split the pair and try to boot from the remote disk, the intial boot process starts but we eventually get 'Waiting for device /dev/disk/by-id/scsi-x-part4 to appear:' and this references the boot LUN on the primary disk. It exits to the shell at that point. If anyone else has already gone through this and knows all of the configuration items we need to update to make this work, we would appreciate the information so we don't have to reinvent the wheel. If not, we'll keep working through this and share what we figure out with the list if anyone is interested. Craig Collins State of WI -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: zFCP Disk
We did get it to work. Not exactly with the steps listed since yast would not complete the define since the LUN didn't work on the storage. We had given up since EMC said they hadn't heard of it being done and that the NPIV may not work. But, knowing someone else was successful and how they remembered doing it gave us renewed energy to work through it again. Thank You for the help. We can now put some more old storage to use. Craig Collins State of WI On Feb 6, 2008 3:08 PM, Jerry Whitteridge [EMAIL PROTECTED] wrote: The Clarion requires you to have accessed the storage subsystem itself before the work can be done (I'm not a storage guy -- especially not mid-range) and I was just listing for Craig the steps we had to go through as the Clarion is different to the DMX's. I am now accessing the Clarion successfully (but haven't rebooted to confirm it is all still there !) Jerry Whitteridge Safeway Inc 925 951 4184 -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of George Kuch Sent: Wednesday, February 06, 2008 1:03 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: zFCP Disk Have you confirmed that the NPIV ports are in the same fabric zone as the clariion ? Regards, George Kuch zSeries zFCP Firmware Development [EMAIL PROTECTED], 845-435-6806, t/l 295-6806 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 LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: zFCP Disk
Sorry, should have written . . . since yast would not complete the define since the LUN was not provisioned on the storage. On Feb 8, 2008 11:25 AM, Craig Collins [EMAIL PROTECTED] wrote: We did get it to work. Not exactly with the steps listed since yast would not complete the define since the LUN didn't work on the storage. We had given up since EMC said they hadn't heard of it being done and that the NPIV may not work. But, knowing someone else was successful and how they remembered doing it gave us renewed energy to work through it again. Thank You for the help. We can now put some more old storage to use. Craig Collins State of WI On Feb 6, 2008 3:08 PM, Jerry Whitteridge [EMAIL PROTECTED] wrote: The Clarion requires you to have accessed the storage subsystem itself before the work can be done (I'm not a storage guy -- especially not mid-range) and I was just listing for Craig the steps we had to go through as the Clarion is different to the DMX's. I am now accessing the Clarion successfully (but haven't rebooted to confirm it is all still there !) Jerry Whitteridge Safeway Inc 925 951 4184 -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of George Kuch Sent: Wednesday, February 06, 2008 1:03 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: zFCP Disk Have you confirmed that the NPIV ports are in the same fabric zone as the clariion ? Regards, George Kuch zSeries zFCP Firmware Development [EMAIL PROTECTED], 845-435-6806, t/l 295-6806 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 LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Peoplesoft/Oracle on SUSE Linux under zSeries
We are considering running the Oracle databases for a Peoplesoft implementation on SUSE guests running under zVM. If anyone is doing it today we'd like to know as validation of this option. Also, we've been told that even if we get that to work the other pieces of the Peoplesoft implementation will need to go on non-zSeries distributed systems servers and are wondering if anyone has implemented the actual application code and interfaces on zSeries Linux guests. Some people in our organization are concerned that none of this can be done and if someone is doing it already it helps us validate it is an option which should be considered. Thanks in advance for any information. Craig Collins State of WI -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: zFCP Disk
We had given up on trying to get the EMC Clariion provisioned to SLES10 using NPIV. The NPIV id for the linux guest is logged into the switch and is provisioned to EMC DMX3 storage, so we know the connection to the switch is working. On the Clariion side we can't provision for the NPIV connection, as if the NPIV id was not logged into the switch. So, are you using NPIV with the connections to the EMC Clariion and if so, do you have any other tips from your experience that might help us get this to work? Craig Collins State of WI On Feb 1, 2008 2:35 PM, Jerry Whitteridge [EMAIL PROTECTED] wrote: Much of the doc out there is for earlier releases (I'm running SLES10) and there is no real step by step information out there to add FCP to an existing Linux Virtual Server. The FCP Redbooks and NPIV Redbooks make some sign cant assumptions on the level of knowledge that we have. So for example: I'm attaching to a EMC Clarion in my test environment. I had to sign into the switch before they could finish the masking, but when using yast it insisted on knowing ALL the details of the FCP connection before I could proceed. By experimentation I found that if I used the zfcp_host_configure command to set the VM device on line it signed me in and out of the switch. Then there was more time spent trying to find commands to show what I could see and where they were all located. Some of the things I came across like san_disc showed up but with no examples to go by I couldn't work out what it was asking for or the appropriate entries. Other commands I came across like lsscsi, lszfcp are mentioned in differing presentations scattered around the web. If this mailing list and the z/VM one did not exist my project would have failed totally. (Thank you ALL !) Jerry Whitteridge Safeway Inc 925 951 4184 -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Friday, February 01, 2008 11:56 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: zFCP Disk On Fri, Feb 1, 2008 at 2:43 PM, in message [EMAIL PROTECTED] , Spann, Elizebeth (Betsie) [EMAIL PROTECTED] wrote: -snip- I was able to get multipathing working, I believe, using DM-MPIO. My challenge is getting LVM2 working in a multipath environment. The /etc/multipath.conf and /etc/lvm/lvm.conf files have to be configured correctly. Anybody out there doing this? Yes, a number of people have done it, and there's some decent documentation for it as well. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 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 LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
NPIV FCP connections through Multiple FC Switches
We're running into a configuration issue trying to get NPIV FCP connections to work through a switched fabric distributed across two locations. At our primary location, the z9 FCP is connected into Switch #1, a McData 3232 switch. We have EMC DMX3 storage connected to Switch #1 as well and are able to get the NPIV id logged onto the fabric, provisioned, and connecting to the storage without a problem. We have Linux guests booting off of the SAN and are not using 3390 disk for them. We setup the switch binding and added the WWPN of the z9 port as a detached node on switch #1 to get this to work. That's the good news. The problem we are having is getting the NPIV id logged into our backup location DMX3 which is connected to Switch #2, another McData 3232 switch ISL'd to Switch #1. We thought we had a setting incorrect on the switches so that the traffic is not making it all the way to the second DMX3, however when we use the SCSIDISC utility under VM against the device which corresponds to the NPIV id, it actually detects the storage port on the DMX3 but the DMX3 shows that we are not logged into the storage port with the NPIV. We've tried multiple settings on the switches to get this connected, but without any success. We have the NPIV and Switch Binding features active on both McData 3232 switches even though I believe we only need NPIV on the switch that the z9 port physically connects to. Has anyone else done this and do you have suggestions as to settings we should look at? Craig Collins State of Wisconsin -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: NPIV FCP connections through Multiple FC Switches
We stumbled across the answer and wanted to document it here in case someone else runs into this problem in the future. The physical port on the z9 had to be added to the zone definition on the switches before we could get it to log into the remote storage through the remote switch. The z9 WWPN did not need to be in the zone definition if only the local switch was used. Craig Collins State of Wisconsin On 9/6/07, Craig Collins [EMAIL PROTECTED] wrote: We're running into a configuration issue trying to get NPIV FCP connections to work through a switched fabric distributed across two locations. At our primary location, the z9 FCP is connected into Switch #1, a McData 3232 switch. We have EMC DMX3 storage connected to Switch #1 as well and are able to get the NPIV id logged onto the fabric, provisioned, and connecting to the storage without a problem. We have Linux guests booting off of the SAN and are not using 3390 disk for them. We setup the switch binding and added the WWPN of the z9 port as a detached node on switch #1 to get this to work. That's the good news. The problem we are having is getting the NPIV id logged into our backup location DMX3 which is connected to Switch #2, another McData 3232 switch ISL'd to Switch #1. We thought we had a setting incorrect on the switches so that the traffic is not making it all the way to the second DMX3, however when we use the SCSIDISC utility under VM against the device which corresponds to the NPIV id, it actually detects the storage port on the DMX3 but the DMX3 shows that we are not logged into the storage port with the NPIV. We've tried multiple settings on the switches to get this connected, but without any success. We have the NPIV and Switch Binding features active on both McData 3232 switches even though I believe we only need NPIV on the switch that the z9 port physically connects to. Has anyone else done this and do you have suggestions as to settings we should look at? Craig Collins State of Wisconsin -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
