Sponsored Content
Operating Systems AIX How to put vscsi in available state? Post 302950734 by bakunin on Tuesday 28th of July 2015 10:09:29 AM
Old 07-28-2015
You seem to lack a solid understanding how all the virtualisation works:

First you create a virtual SCSI adapter on the VIOS and allow a certain LPAR to use it. For the LPAR it is used like any physical SCSI adapter, save for the fact that it is just a software construct in the VIOS. You do this on the HMC (see here), then run cfgdev on the VIOS.

Next you create (virtual) SCSI-devices on the VIOS: see the command "mkvdev" on the VIOS for creating such devices. You create such a device by assigning a "backing device" (some disk space the VIOS can control) and connect it to a virtual SCSI adapter.

For instance:
Code:
mkvdev -vdev hdisk10 -dev vtdisk_lpar5 -vadapter vhost5

This means: take "hdisk10" on the VIOS and use it(s disk space) to create a virtual disk "vtdisk_lpar5", which is connected to a virtual SCSI adapter named "vhost5". If "vhost5" is connected to the "lpar 5" you can run the cfgmgr command there and the newly connected disk would appear.

I hope this helps.

bakunin
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

TIME_WAIT state

in TCP, is TIME_WAIT state really essential..!!! (3 Replies)
Discussion started by: sasikanth
3 Replies

2. Solaris

Zone in down state.

One of my zone is stuck in down state, not able to boot it or halt it .. not even detach .. is there any way to recover without rebooting the whole system ( global zone ) ? (3 Replies)
Discussion started by: fugitive
3 Replies

3. AIX

Migrating hdisks from vscsi to NPIV with powerpath

Hi All, I'm preparing to migrate some servers from vscsi to pass-thru NPIV. I am planning to have the SAN team move the exact LUNs from vio1/vio2 to those two VWWN through NPIV. My question is on the partition itself.. right now, let's say I have hdisk0/1/2/3/4 that are part of datavg. They... (2 Replies)
Discussion started by: lapfrank
2 Replies

4. AIX

Vscsi and npiv on same adapter

Hi, I want to change from vscsi to npiv. Is it possible to use both on the same adapter, so we can change the systems one by one, or must we place a second FC adapter in the VIO servers? Thanks, Ronald (2 Replies)
Discussion started by: ronaldm60
2 Replies

5. AIX

hdisk mapping to a vSCSi Adapter

Hello, I have a VIOS System and would like to do mapping some hdisks, hdisk160 until hdisk165 to a vSCSi Adapter. I try to do this in the oem_setup_env like the following: for i in $(lspv | grep hdisk* | awk {'print $1'}; do mkdev -V $i -p vhost20 done There where a mapping with... (4 Replies)
Discussion started by: torsten163
4 Replies

6. AIX

Kdb - vscsi disk mapping from AIX 5.3 CLIENT side

If you're familiar with vscsi mappings thru a VIO Server, you are probably aware, on an AIX 6.1 Client LPAR, that: print cvai | kdbcan provide useful information to you.... like VIO Server name & vhost #. But, "cvai" does not appear to be part of the Kernel Debugger in AIX 5.3. My question is... (3 Replies)
Discussion started by: The Doctor
3 Replies

7. AIX

Open firmware state to running state

Hi Admins, I am having a whole system lpar in open firmware state on HMC. How can I bring it to running state ? Let me know. Thanks. (2 Replies)
Discussion started by: snchaudhari2
2 Replies

8. AIX

Devices.vscsi.disk ?

Hello, When I assigned CDROM from IVM (VIOS) to LPAR and then running cfgmgr i get the following message on the client lpar #cfgmgr cfgmgr: 0514-621 WARNING: The following device packages are required for device support but are not currently installed. devices.vscsi.disk searching... (0 Replies)
Discussion started by: filosophizer
0 Replies

9. UNIX for Advanced & Expert Users

Unable to install client AIX LPAR to vscsi hdisk provided from VIOS

Hi everybody, I have Power5 server with 4 internal hdisks each of 70Gb. VIOS server was installed via Virtual I/O Server Image Repository on the HMC. HMC release - 7.7.0 VIOS rootvg installed on 2 disk(these disks merged to one storage pool during VIOS install process),and 2 others hdisks... (2 Replies)
Discussion started by: Ravil Khalilov
2 Replies
atapi_ide(7)						 Miscellaneous Information Manual					      atapi_ide(7)

NAME
atapi_ide - Interface for ATAPI or IDE (PC) devices SYNOPSIS
PCI bus CMD/Acer ATAPI/IDE adapter: bus pci0 at * bus ata0 at * controller scsi0 at ata0 slot 0 controller scsi1 at ata0 slot 1 PCI bus Cypress ATAPI/IDE adapter: bus pci0 at * bus ata0 at * bus ata1 at * controller scsi0 at ata0 slot 0 controller scsi1 at ata1 slot 0 PCMCIA bus ATA/IDE disk card: bus pcmcia0 at * bus ata0 at pcmcia? controller scsi0 at ata0 DESCRIPTION
Devices commonly known for their use on PC devices as ATA or IDE devices are supported using the SCSI CAM device driver. The ATA standard has also been expanded to include what are known as ATAPI devices. The SCSI CAM device driver is also used for those disks and CD-ROM devices. These devices may also be known under the names EIDE, ATA-2, Fast-ATA, or Ultra-ATA. Beacuse the ATA/IDE standard was not developed until after many of the devices that used this standard were produced, there are many devices which do not strictly comply with the standard. While it is possible some industry standard devices may appear to work, it is also possible they will cause hang or data corruption cases when used under more stressful situations. For this reason, it is recommended that only the supported devices be used. These devices have been tested and are certified for correct operation. ATAPI/IDE controllers allow the connection of two devices. These two devices are known as the master device and the slave device. If only one device is connected, that device must be the master (slave-only configurations are not supported). When used by the SCSI CAM device driver, the IDE master device is assigned SCSI id 0 for that controller. The slave device is assigned SCSI id 1 for that controller. No other SCSI ids are assigned on that controller. Most ATAPI/IDE adapters contain two channels (known as the primary and secondary). Each of these channels may contain their own master and slave devices. Therefore, a dual channel ATAPI/IDE controller may contain up to 4 devices (a master and slave pair on each channel). These 4 devices are then accessed as SCSI id 0 and 1 on each channel. Many SCSI operations translate perfectly for use on IDE. For example, read and write operations are the same. However, many SCSI disk mode pages are emulated by the IDE device driver. For example, you can display the SCSI inquiry mode pages using the following command: % scu show inq pages pages are created by the device driver to contain the long (full IDE) form of the device name, serial number, revision, and the operational modes of the device. Only a shortened version of this information is available with the standard SCSI inquiry command. Note also that the following command: % scu show pages Shows that the SCSI mode pages contain only partial information. Only that informa- tion (such as geometry) that the drive reports to the system is able to be reformatted into these emulated SCSI mode pages. Much of the information (such as RPM) is simply not available from the drive, and therefore not accurately reported. ATAPI devices are much more closely related to SCSI devices, and as such contain their own mode pages. Therefore, for these devices, the mode page values reported are those from the device, and no emulation is involved. ATAPI tape devices are not supported at this time. FILES
/dev/disk/dsk??? /dev/disk/dsk??? RELATED INFORMATION
SCSI(7), rz(7), and disklabel(8) delim off atapi_ide(7)
All times are GMT -4. The time now is 10:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy