04-12-2009
hi,
1. depending on the type of SAN storage, usually the LUN id can be found with lscfg -l hdisk##
2. you can set the pvid like this: chdev -dev hdisk## -attr pv=yes
hope this helps
Randy
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
We recently purchased a 3 tb RAID. In the setup, it created 2 slices, one 2 tb and one 1 tb slice. Right now only the 2 tb slice is visible when booting up. I was told that the second slice needs to be mapped to a lun and a port like the first slice is.
Does anyone know how I would go... (1 Reply)
Discussion started by: user23
1 Replies
2. AIX
We have a frame the uses 2 vios that assign disk storage to LPAR's. We have a LPAr with multiple disk and I want to know how do I tell which vio is serving the disk. For example the LPAr has hdisk 0, 1, 2, 3 all the same size. I want to know which vio is serving hdisk0, 1. (4 Replies)
Discussion started by: daveisme
4 Replies
3. AIX
Hello,
I have created mapping of 2 virtual adapters for Lpars using following command:
mkvdev -vdev ipanalyzerlv1 -vadapter vhost11
mkvdev -vdev ipanalyzerlv -vadapter vhost13
The above two commands were succesfull
but when I want to map the third virtual device to the same Lpar than... (3 Replies)
Discussion started by: Vit0_Corleone
3 Replies
4. AIX
Hi All,
Besides the licenses on VIO and LPAR. What's the main difference with the two? I have installed VIO, my manager told me so, because it's like a free hypervisor but I never installed LPAR before. How do you install it? And if you can give more info on the two, that would be great.
... (5 Replies)
Discussion started by: itik
5 Replies
5. AIX
Hi,
I would like to know how to share lun in between 2 lpars.
I have run tbe below command on vio server.
/usr/sbin/chdev -l hdisk1 -a reserve_policy=no_reserve
after above command I am able to assign lun on one Lpar. but it is not visible to other lpar.
even after this I have run... (3 Replies)
Discussion started by: manoj.solaris
3 Replies
6. AIX
Please forgive me here as I don't fully understand what I am talking about here so if I use the wrong terminology please overlook me.
We have multiple AIX LPARs on the managed system with two VIO Servers. A Co-Worker and I are trying to set up a new LPAR client (The guy that knows this is out)... (14 Replies)
Discussion started by: juredd1
14 Replies
7. AIX
Hi guys,
does anyone know how to get a list of the LPAR running on VIOS?
Thanks! (5 Replies)
Discussion started by: cecco16
5 Replies
8. AIX
I am trying to install AIX 5.3 on one of the LPARs through VIOS but I get this error 0518
Reference Code Selection
0518 (Time stamp: 12/18/12 12:10:20 AM UTC)
Starting kernel (Time stamp: 12/18/12 12:10:15 AM UTC)
AIX is starting. (Time stamp: 12/18/12 12:10:15 AM... (10 Replies)
Discussion started by: filosophizer
10 Replies
9. AIX
Hi,
Just joined to new company with one Power 720 Express (8202-E4C) server and have no much experience with IBM systems.
I am trying to move everything I mentioned to different subnet as required by customer contract (currently sitting on same subnet as company lan). Access to this subnet will... (8 Replies)
Discussion started by: spricer
8 Replies
10. AIX
Hello,
VIOS 2.2.1.4 using IVM.
I'm trying to extend a virtual disk assigned to a running lpar so that I can expand the lpar's datavg and grow some filesystems for the user.
Storage admin expanded the lun and new size was reflected in VIO right away. I then needed the storage pool to... (2 Replies)
Discussion started by: j_aix
2 Replies
LEARN ABOUT OPENSOLARIS
targ
TARG(4) BSD Kernel Interfaces Manual TARG(4)
NAME
targ -- SCSI target emulator driver
SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file:
device targ
DESCRIPTION
The targ driver provides an interface for usermode programs to emulate SCSI target devices. A sample program that emulates a disk drive
(similar to da(4)) can be found in /usr/share/examples/scsi_target.
The targ driver supplies control devices, /dev/targ0, /dev/targ1, etc. If a device is already in use, open(2) will fail and errno will be
set to EBUSY. After opening the device, the file descriptor must be bound to a specific bus/target/LUN and enabled to process CCBs using the
TARGIOCENABLE ioctl. The process then uses write(2) to send CCBs to the SIM and poll(2) or kqueue(2) to see if responses are ready. Point-
ers to completed CCBs are returned via read(2). Any data transfers requested by the user CCBs are done via zero-copy IO.
IOCTLS
The following ioctl(2) calls are defined in the header file <cam/scsi/scsi_targetio.h>.
TARGIOCENABLE (struct ioc_enable_lun) Enable target mode on the LUN specified by the following structure:
struct ioc_enable_lun {
path_id_t path_id;
target_id_t target_id;
lun_id_t lun_id;
int grp6_len;
int grp7_len;
};
The selected path (bus), target, and LUN must not already be in use or EADDRINUSE is returned. If grp6_len or grp7_len are
non-zero, reception of vendor-specific commands is enabled.
TARGIOCDISABLE Disable target mode and abort all pending CCBs. The CCBs may optionally be read as they complete. TARGIOCENABLE can then be
called to activate a different LUN. Multiple disable calls have no effect. The close(2) system call automatically disables
target mode if enabled.
TARGIOCDEBUG (int) Enables CAM_PERIPH debugging if the argument is non-zero, otherwise disables it.
FILES
<cam/scsi/scsi_targetio.h> describes the usermode interface.
/sys/cam/scsi/scsi_target.c is the driver source file.
/dev/targ* are the control devices.
SEE ALSO
/usr/share/examples/scsi_target, ahc(4), isp(4), scsi(4)
FreeBSD Target Information, http://www.root.org/~nate/freebsd/.
AUTHORS
The targ driver first appeared in FreeBSD 3.0 and was written by Justin T. Gibbs. It was rewritten for FreeBSD 5.0 by Nate Lawson
<nate@root.org>.
BUGS
Currently, only the ahc(4) and isp(4) drivers fully support target mode.
The ahc(4) driver does not support tagged queuing in target mode.
BSD
November 15, 2002 BSD