05-12-2009
quick question:
From my SAN i have allocated a disk to VIO Server and from VIO Server to my LPAR
If I increase the space of the logical SAN DISK ; how will it get reflected on the lpar ?
Do I need to varyoffvg the vG of LPAR, go to my VIO Server and use the command chvg -g ?
any ideas for online (without varyoffvg ?)
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
iobind(1M) iobind(1M)
NAME
iobind - bind a driver to a device
SYNOPSIS
instance]
DESCRIPTION
The command may be used to perform online unbinding of a device LUN hardware path from its current driver and binding a new driver to it.
As part of the binding operation, the specified driver will be bound to the LUN hardware path and also to its corresponding legacy hardware
paths.
The hardware path specified as the argument to the option must be of the form 64000/0x/0x. The driver name specified with the option will
be bound to the LUN and legacy hardware paths. The optional option specifies an instance number to be assigned to the device associated
with the hardware path. If this option is not used, the device will be assigned a new instance number in the new driver's class. The
optional forces the binding to occur at the next reboot if it cannot be done online.
The device must not be in use while the unbind operation is performed. The driver must support online unbinding and binding. If either of
these requirements is false and the option is not given, the user will be asked if the binding can take effect at the next reboot. The
user is given the option to proceed or not.
If a driver supports online unbinding and binding, then after completes, a device will have one of the following software states as shown
by the command:
The specified driver was successfully bound to the hardware path.
The specified driver cannot be used to claim the hardware at
the specified hardware path.
The device at the address is responding, but it is in an
error state.
The device at the specified hardware path is no longer responding.
The specified hardware path is locked. Try again later.
The driver failed.
Options
recognizes the following options:
Force the binding even though a driver does not support online unbinding
and binding or the device is in use. In this case, the binding will take effect at the next reboot.
The LUN hardware path of a device
must be of the form 64000/0x/0x.
The instance number to be assigned to the device.
The name of the driver that the LUN and legacy hardware paths are to be bound to.
RETURN VALUE
Exit values are:
Successful completion.
An error condition occurred.
EXAMPLES
Unbind the driver bound to the device at hardware path and bind the device to Use the default instance number of the driver's class.
Unbind the driver bound to the device at hardware path and bind the device to Assign it the instance number
Do a forced binding. If the driver does not support online binding or the device is busy, the binding will be deferred till next reboot.
WARNINGS
The and commands should not be run at the same time because both commands attempt to bind drivers. In particular, there may be a short
window while will leave a hardware path unbound. If runs during that window, it may bind a different driver to that hardware path. If
this happens, must be executed again to bind the desired driver.
may be executed only by the superuser.
SEE ALSO
ioscan(1M), intro(7).
iobind(1M)