10 More Discussions You Might Find Interesting
1. AIX
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,... (12 Replies)
Discussion started by: Adnans2k
12 Replies
2. AIX
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
3. AIX
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
4. AIX
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
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
6. UNIX for Advanced & Expert Users
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... (1 Reply)
Discussion started by: rapina
1 Replies
7. AIX
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... (2 Replies)
Discussion started by: zxmaus
2 Replies
8. AIX
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.
... (2 Replies)
Discussion started by: ronykris
2 Replies
9. UNIX for Dummies Questions & Answers
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... (1 Reply)
Discussion started by: thumper
1 Replies
10. Solaris
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>
... (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies
cfg_subsys_attr_t(9s) cfg_subsys_attr_t(9s)
NAME
cfg_subsys_attr_t - General: Contains attribute information for kernel modules
SYNOPSIS
typedef struct {
char name[CFG_ATTR_NAME_SZ];
uchar type;
uchar operation;
caddr_t addr;
ulong min_val;
ulong max_val;
ulong val_size; } cfg_subsys_attr_t;
MEMBERS
Specifies the ASCII name of the attribute. The name must be between 2 and CFG_ATTR_NAME_SZ characters in length, including the terminating
null character. Do not begin the ASCII name of the attribute with the Method_ or Device_ characters. The cfgmgr framework reserves certain
names that begin with the Method_ and Device_ characters. Specifies the data type associated with the name attribute. See the DESCRIPTION
section for the constants you can pass to the type member. Specifies the operations that the cfgmgr framework can perform on the
attribute. See the DESCRIPTION section for the constants you can pass to the operation member. Specifies the address of the data value
associated with the attribute. The cfgmgr framework obtains the data value for this attribute from the /etc/sysconfigtab database and
stores it at this address. The cfgmgr framework performs this storage operation if the following occurs: The attribute appears in the
cfg_subsys_attr_t table (declared and initialized in the kernel module) with an operation code of CFG_OP_CONFIGURE. The kernel module
writer passes the CFG_OP_CONFIGURE constant to the optype argument of the kernel module's configure routine. This is the kernel module's
configuration entry point for handling static or dynamic configuration requests.
Although the configure routine can initialize attributes that appear in the array with an operation code of CFG_OP_CONFIGURE, the
cfgmgr framework overrides this initialization with the value specified in the /etc/sysconfigtab database. Specifies the minimum
length of a string data value. If the data type for the attribute is numeric, specifies the minimum range. Specifies the maximum
length of a string data value. If the data type for the attribute is numeric, specifies the maximum range. Specifies the binary
data size.
DESCRIPTION
The cfg_subsys_attr_t data structure contains information that kernel modules use to describe a variety of attributes. Kernel module writ-
ers declare and initialize an array of cfg_subsys_attr_t data structures in their kernel modules. The cfg_subsys_attr_t data structure is a
simplified version of the cfg_attr_t data structure and is designed to save space in the kernel.
You must set the type member to one of the following constants: Data type is a null-terminated array of characters. Data type is a 32-bit
signed integer. Data type is a 32-bit unsigned integer. Data type is a 64-bit signed integer. Data type is a 64-bit unsigned integer.
Data type is an array of bytes. Data type is an 8-bit unsigned character. Data type is a 16-bit unsigned short integer.
You can set the operation member to one of the following constants: The cfgmgr framework configures the attribute. This means the cfgmgr
framework obtains a data value for the attribute from the /etc/sysconfigtab database. The configure operation occurs when the cfgmgr frame-
work calls the kernel module's configure routine at its CFG_OP_CONFIGURE entry point. (That is, the optype argument of theconfigure rou-
tine evaluates to the CFG_OP_CONFIGURE constant.) The cfgmgr framework queries (reads) the attribute. This means the kernel module cooper-
ates with the cfgmgr framework to provide the value associated with the attribute as a result of user-initiated query requests. These
requests are typically the result of the sysconfig -q command. The query operation occurs when the cfgmgr framework calls the kernel mod-
ule's configure routine at its CFG_OP_QUERY entry point. (That is, the optype argument of the configure routine evaluates to the
CFG_OP_QUERY constant.) The cfgmgr framework reconfigures the attribute. This means the cfgmgr framework reconfigures the data value for
the attribute. This functionality allows a user to modify the attribute. A reconfigure request is typically the result of the sysconfig
-r command. The reconfigure operation occurs when the cfgmgr framework calls the kernel module's configure routine at its CFG_OP_RECONFIG-
URE entry point. (That is, the optype argument of the configure routine evaluates to the CFG_OP_RECONFIGURE constant.)
FILES
SEE ALSO
Data Structures: cfg_attr_t(9s)
cfg_subsys_attr_t(9s)