Since we're on the topic of SAN ...
What Mark said is true. While Alan points out correctly that the
(virtual or real) WWPN follows the subchannel, if you connect Linux
directly to the SAN, you'll still have to tell Linux which WWPN+LUN
pair(s) to use. My conclusion after careful analysis: hemorr
That's handy to know.
Another thing about rescuing some other guest's LUN, if (to avoid looking up
where to echo the LUN's wwpn and LUN# to the /sys structures to put that LUN
online) I use zfcp_disk_configure to put the LUN online, that command
adds/updates files in /etc to automatically brin
>>> On 6/25/2009 at 3:55 PM, Alan Altmark wrote:
-snip-
> It doesn't matter what user ID is used. The NPIV WWPN is assigned to the
> subchannel. ATTACH the sc to whatever guest you want. (The old
> userid-based LUN Access Control authorization scheme is long gone.)
True, but having to config
On Thursday, 06/25/2009 at 03:32 EDT, "Romanowski, John (OFT)"
wrote:
> Some more pedantism: For both dasd and SCSI disks, booting a rescue
system on
> the downed zLinux server makes repairing the file easier:
> the VM userid already has access to the disk in question, no need to
LINK to or
> get
Very good points here, John.
Romanowski, John (OFT) wrote:
Some more pedantism: For both dasd and SCSI disks, booting a rescue system on
the downed zLinux server makes repairing the file easier:
the VM userid already has access to the disk in question, no need to LINK to or
get the other useri
Some more pedantism: For both dasd and SCSI disks, booting a rescue system on
the downed zLinux server makes repairing the file easier:
the VM userid already has access to the disk in question, no need to LINK to or
get the other userid zoned/masked to the downed server's LUN.
> -Original Me
Not to be too pedantic here, but the methods being offered on how to
access one zLinux's file system from another, to make repairs or
whatever, all assume that the Linux file systems are on 'old-style'
mainframe DASD, either ECKD (3390) or FBA (either 9336 or EDEV). If the
zLinux guest is installe
Is anyone running IBM FileNet P8 4.5 on zLinux (SUSE) using DB2 also
running on
zLinux(SUSE)? Our open system group would like to move it over to our
z/VM system running Linux,
but would like to know if anyone else has FileNet running on zlinux.
Thanks
Tom Morris
tmor...@wcfgroup.com
WCF
Attach the other disk, or in the case of minidisk, Link to the other disk.
vary the device online
chccwdev --online ccuu
Find the device
lsdasd
mount the device
mount /dev/dasdx1 /mnt
On Thu, Jun 25, 2009 at 8:19 AM, Lee, Gary D. wrote:
> Under vm 5.3 both instances are suse sles10.
>
> Some
Good question, Ron.
This is a case where LVMing the root can lead to pain.
If the root is not LVMed, then you can follow Bernie's recipe. Easy!
Otherwise (with logical volumes) you might have multiple PVs to attach
... and worse ... what if the volume groups collide? (same name - you
can work aro
Gary,
I need a little more information on how your systems are set up.
Are you using lvm for your operating system disk on instance a and
instance b?
Ron
Lee, Gary D. wrote:
Under vm 5.3 both instances are suse sles10.
Some one edited the /etc/inittab on instance A.
How can we mount instanc
Yes. OSPF is just a payload on a normal IP packet. I'd suggest layer 2 for the
VSWITCH to permit easier use of the OSPF multicast component, but it will work
fine without it.
> -Original Message-
> From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
> Bruce Furber
> Se
We are running z/VM 5.4 with linux machines running off a VSWITCH.
Can I run QUAGGA OSPF thru the VSWITCH or do I need to dedicate OSA ports to my
Linux machine?
T.I.A. for any help.
Bruce
--
For LINUX-390 subscribe / signoff /
>From "B"
# vmcp link "A" 100 1100 mr ( assuming 100 is instance A's root disk )
# chccwdev -e 0.0.1100
# mkdir /Aroot
# lsdasd ( to determine /dev/dasd? )
# mount /dev/dasd? /Aroot
Then you can either # cd /Aroot/etc
Or
# chroot /Aroot
Under vm 5.3 both instances are suse sles10.
Some one edited the /etc/inittab on instance A.
How can we mount instance a's root fs to instance b so as to fix the inittab?
Or, is there a better way?
Thanks for any help.
Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310
-Snip-
Reboot the z/VM guest. You should get a menu. At that point enter:
#cp vi vmsg 0 init=3D/bin/bash
-Snip-
I don't get a menu, just the logon prompt. Still, I'll try it.
Vince Getgood
--
For LINUX-390 s
16 matches
Mail list logo