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 OSF1

cfgmgr_set_status

cfgmgr_set_status(9r)													     cfgmgr_set_status(9r)

NAME

       cfgmgr_set_status - General: Reports failure to the cfgmgr framework

SYNOPSIS

       int cfgmgr_set_status(
	       char *driver_name );

ARGUMENTS

       Specifies  the  name of the device driver for which you want to report an associated failure. This name is a string that matches the string
       you specified for the entry_name item in the /etc/sysconfigtab database. Typically, third-party driver  writers	specify  the  driver  name
       (followed  by  a  colon) in the sysconfigtab file fragment, which gets appended to the /etc/sysconfigtab database during the driver product
       installation.

DESCRIPTION

       The cfgmgr_set_status routine reports to the cfgmgr framework that a failure has occurred during static configuration.	If  the  specified
       device  driver is in the static configuration state, it does not know that the configuration operation is complete until all register call-
       back requests (routines) have successfully completed. Therefore, a device driver calls cfgmgr_set_status to report a possible failure  dur-
       ing static configuration to the cfgmgr framework.

       Specifically,  cfgmgr_set_status  performs  the following failure operations: Adjusts the state of the specified device driver Unconfigures
       the specified device driver from the cfgmgr framework

       The cfgmgr_set_status routine calls the device driver's configure routine at its CFG_OP_UNCONFIGURE entry point as part	of  these  failure
       operations.  The  code  associated  with  the CFG_OP_UNCONFIGURE entry point is responsible for determining how to deallocate any allocated
       resources during these failure operations.

       The cfgmgr_set_status routine does not notify the operator of a configuration failure. Part of the code associated with	the  CFG_OP_UNCON-
       FIGURE  entry  point  could include an error logging operation to record the fact that a failure has occurred. The reason for doing this is
       that the cfgmgr framework's task is to accomplish the unconfigure operation of a statically configured device driver.

       You call the cfgmgr_set_status routine in the device driver's callback routine when the static configuration operation fails.  You register
       a callback routine by calling the register_callback routine.

RETURN VALUES

       Upon  successful completion, cfgmgr_set_status returns the value ESUCCESS. This success value indicates that cfgmgr_set_status adjusted the
       state of the device driver and caused the cfgmgr framework to unconfigure the driver. Otherwise, cfgmgr_set_status returns one of the  fol-
       lowing  error  constants defined in /usr/sys/include/sys/sysconfig.h and /usr/sys/include/sys/errno.h: The device driver that you specified
       in the driver_name argument does not exist. In this case, cfgmgr_set_status cannot adjust the state and unconfigure the device driver.  The
       device  driver  that  you specified in the driver_name argument was not statically configured.  The device driver that you specified in the
       driver_name argument is not in the static configuration state.

EXAMPLES

       See Writing Device Drivers: Tutorial for a code example of the cfgmgr_set_status interface.

SEE ALSO

       Routines: cfgmgr_get_state(9r), register_callback(9r)

															     cfgmgr_set_status(9r)

AIX