Devices.vscsi.disk ?

10 More Discussions You Might Find Interesting

1. AIX

How to put vscsi in available state?

Hello Friends, My question/problem is that I noticed 2 servers in my environment vscsi is showing up as defined (not available) or is defined and not showing the path to both vscsi's when ruining lspath command. I am new to AIX admin, work alone, and work in an small environment. My question is,...

2. 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. 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. 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

5. 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...

6. UNIX for Advanced & Expert Users

Doubt in AIX and HP-UX disk devices addressing

Hi people, Does anyone know how the AIX form the hdisk addresses ? I mean, if the AIX use the SAN fields like switch id, domain id, port id and etc... After I understand that my next question is: Why the AIX do not change the hdisks addressing if I change the AIX HBAs of the SAN switch and/or...

7. AIX

how do I change major-minor numbers of disk devices

Good evening ... does anyone of you know how to change major/minor numbers of disk devices ? I had to migrate from raid1 to raid5 and this messed up my ASM cluster - I know which devices should have which IDs to match the content - but I have no idea how to change it. Any help would be...

8. AIX

deinstall devices.fcp.disk.array.rte

Hello, I am trying to "deinstall devices.fcp.disk.array.rte" fileset from an AIX5.3 box. Have been unsuccessful so far. "smit remove" threw the below error: FAILURES -------- Filesets listed in this section failed pre-deinstall verification and will not be removed. ...

9. UNIX for Dummies Questions & Answers

passthrough devices vs. named devices

I am having trouble understanding the difference between a passthrough device and a named device and when you would use one or the other to access equipment. As an example, we have a tape library and giving the command "camcontrol devlist" gives the following output: akx# camcontrol...

10. Solaris

Disk devices in solaris 10 x86

I'm trying to mirror 2 eide disks on a solaris 10 x86 system. Im trying to use the prtvtoc | fmthard command to mirror the vtoc. How do they represent the entire disk like in solaris 9 (c0t0d0s2 = entire device) 0. c0d0 <DEFAULT cyl 26497 alt 2 hd 16 sec 63> ...

LEARN ABOUT OPENSOLARIS

did

did(7)						     Sun Cluster Device and Network Interfaces						    did(7)

NAME

       did - user configurable disk id driver

DESCRIPTION

       Note -

	 Beginning  with  the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software
	 still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more  infor-
	 mation about the object-oriented command set, see the Intro(1CL) man page.

       Disk  ID  (DID)	is  a  user  configurable pseudo device driver that provides access to	underlying disk, tape, and CDROM devices. When the
       device supports unique device ids, multiple paths to a device are determined according to the device id of the  device.	Even  if  multiple
       paths are available with the same device id, only one DID name is given to the actual device.

       In  a  clustered environment, a particular physical device will have the same DID name regardless of its connectivity to more than one host
       or controller.  This, however, is only true of devices that support a global unique device identifier such as physical disks.

       DID maintains parallel directories for each type of device that it manages under /dev/did. The devices in these directories behave the same
       as  their  non-DID  counterparts.  This	includes  maintaining slices for disk and CDROM devices as well as names for different tape device
       behaviors.  Both raw and block device access is also supported for disks by means of /dev/did/rdsk and /dev/did/rdsk.

       At any point in time, I/O is only supported down one path to the device.  No multipathing support is currently available through DID.

       Before a DID device can be used, it must first be initialized by means of the scdidadm(1M) command.

IOCTLS

       The DID driver maintains an admin node as well as nodes for each DID device minor.

       No user ioctls are supported by the admin node.

       The  DKIOCINFO ioctl is supported when called against the DID device nodes such as /dev/did/rdsk/d0s2.

       All other ioctls are passed directly to the driver below.

FILES

       /dev/did/dsk/dnsm		   block disk or CDROM device, where  n is the device number and  m is the slice number

       /dev/did/rdsk/dnsm		   raw disk or CDROM device, where  n is the device number and	m is the slice number

       /dev/did/rmt/n			   tape device , where n is the device number

       /dev/did/admin			   administrative device

       /kernel/drv/did			   driver module

       /kernel/drv/did.conf		   driver configuration file

       /etc/did.conf			   scdidadm configuration file for non-clustered systems

       Cluster Configuration Repository (CCscdidadm(1M) maintains configuration in the CCR for clustered systems

SEE ALSO

       devfsadm(1M), Intro(1CL), cldevice(1CL), scdidadm(1M)

NOTES

       DID creates names for devices in groups, in order to decrease the overhead during device hot-plug.  For disks, device names are created	in
       /dev/did/dsk  and   /dev/did/rdsk  in  groups of 100 disks at a time.  For tapes, device names are created in  /dev/did/rmt in groups of 10
       tapes at a time.  If more devices are added to the cluster  than are handled by the current names, another group will be created.

Sun Cluster 3.2 						   24 April 2001							    did(7)

AIX