Devices.vscsi.disk ?


 
Thread Tools Search this Thread
Operating Systems AIX Devices.vscsi.disk ?
# 1  
Old 09-14-2018
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

Code:
#cfgmgr

cfgmgr: 0514-621 WARNING: The following device packages are required for device support but are not currently installed.
devices.vscsi.disk

searching AIX 5.3 CDROM, I couldn't find devices.vscsi.disk

anyone faced similar problem ?
Login or Register to Ask a Question

Previous Thread | Next Thread

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,... (12 Replies)
Discussion started by: Adnans2k
12 Replies

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 Replies)
Discussion started by: The Doctor
3 Replies

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 Replies)
Discussion started by: torsten163
4 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

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

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... (1 Reply)
Discussion started by: rapina
1 Replies

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... (2 Replies)
Discussion started by: zxmaus
2 Replies

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. ... (2 Replies)
Discussion started by: ronykris
2 Replies

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... (1 Reply)
Discussion started by: thumper
1 Replies

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> ... (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies
Login or Register to Ask a Question
sysconfig(8)						      System Manager's Manual						      sysconfig(8)

NAME
sysconfig - Maintains the kernel subsystem configuration SYNOPSIS
/sbin/sysconfig [-h hostname] [-i index] [-o opcode] [-v] -c | -d | -m | -q | -Q | -r | -s | -u [subsystem-name] [attribute-list] FLAGS
Configures the specified subsystem by initializing its attribute values and, possibly, loading it into the kernel. Display the attribute settings in the /etc/sysconfigtab file for the specified subsystem. Specifies that the operation be performed on system hostname. Speci- fies the index to be used for querying or reconfiguring indexed attributes. Queries the mode for the specified subsystems. A subsystem's mode can be static or dynamic. If you omit the subsystem name, sysconfig displays the mode of all the configured subsystems. Perform a system-defined operation corresponding to the specified operation code (opcode). The opcode function must be implemented for the specified subststem. Optionally, pass an attribute and value as input data. For example: # sysconfig -o proc 101 maxusers=512 Queries attribute val- ues for the configured subsystem specified by subsystem-name. If you omit attribute-list, values of all the specified subsystem's attributes are displayed. Queries information about attributes of the configured subsystem specified by subsystem-name. The information includes the attribute data type, the operations supported, and the minimum and maximum values allowed for the attribute. Note that the minimum and maximum values means length and size for attributes of char and binary types, respectively. If you omit the attribute-list, information about all attributes in the specified subsystem is displayed. Reconfigures the specified subsystem. You must supply the sub- system-name argument and the attribute-list argument when you use this flag. Queries the subsystem state for the specified subsystems. If you omit the subsystem name, sysconfig displays the state of all the configured subsystems. Unconfigures and, if the subsystem is load- able, unloads the specified subsystem from the kernel. (Verbose) This flag displays debugging information from the cfgmgr server and the kloadsrv. The kloadsrv loader output is sent to /dev/console. This information can be used to determine the names of any unresolved sym- bols from dynamically linked modules. DESCRIPTION
The sysconfig command is used to query or modify the kernel subsystem configuration. You use this command to add subsystems to your running kernel, reconfigure subsystems already in the kernel, ask for information about (query) subsystems in the kernel, and unconfigure and remove subsystems from the kernel. A subset of kernel subsystems can be managed using the sysconfig command. This command allows you to add and remove loadable subsystems from the running kernel. It also allows you to modify the value of subsystem attributes, so long as the subsystem supports run-time modi- fications. (You can also use the dxkerneltuner application to modify the value of subsystem attributes. This application provides a win- dow interface to tuning kernel subsystems. For more information, see dxkerneltuner(8).) The first argument to the sysconfig command is the subsystem-name argument. The subsystem-name argument names the subsystem on which you want to perform the operation specified by one of the required flags, such as the -c (configure) flag or the -q (query attributes) flag. The subsystem-name argument is required for all flags except -s and -m. If you omit subsystem-name when you use one of these flags, the sysconfig command displays information about all loaded subsystems. The attribute-list argument lists attribute names and, depending on the operation, attribute values. For reconfigure operations (-r), the attribute-list argument has the following format: attribute1=value1 attribute2=value2... You cannot include spaces between the attribute name, the equal sign (=), and the value. For query attribute (-q) operations, the attribute-list has the following format: attribute1 attribute2... The attribute-list argument is required when you use the -r flag and is options with the -q flag. Any attribute-list specifies with other flags is ignored by the sysconfig command. When you configure a subsystem using the -c flag, you make that subsystem available for use. If the subsystem is loadable, the sysconfig command loads the subsystem and then initializes the value of its attributes. The command reads information from an in-memory copy of the /etc/sysconfigtab file to determine the initial value of attributes. Attributes that are omitted from the /etc/sysconfigtab file are given their default value. (You control the contents of the /etc/sysconfigtab file with the sysconfigdb command. See the sysconfigdb(8) reference page for more information.) If you want to modify the value of a subsystem attribute, you use the -r (reconfigure) flag. When you use the -r flag, the sysconfig com- mand modifies the named attributes by storing the value you specify in them. The modifications take effect immediately. To store the attribute values so that they are used the next time the subsystem is configured, you must modify the /etc/sysconfigtab file. Use the sysconfigdb command to modify the /etc/sysconfigtab file, as described on the sysconfigdb(8) reference page. To get information about subsystem attributes, use either the -q flag or the -Q flag. You can specify an attribute list with both these flags. When you use the -q flag, the sysconfig command reads the value of attributes from the kernel and displays those values on your local display. When you use the -Q flag, the sysconfig command displays the following information about either each attribute in the sub- system or, if specified, each attribute in the attribute-list: Attribute datatype. Operations supported by the attribute. This information indicates, for example, whether you can reconfigure the attribute using the sysconfig -r command. Minimum and maximum allowed attribute value. Use the -m flag to determine whether a subsystem supports being added and removed from the kernel using the sysconfig -c or sysconfig -u command. The -m flag displays the subsystem name and indicates whether that subsystem is static (you must rebuild the kernel to add or remove it from the kernel) or dynamic (you can load and unload it from the kernel using the sysconfig command). If you omit the subsystem- name argument, the sysconfig command displays this information for all loaded and configured subsystems. To get information about the state of subsystems, use the -s flag. This flag provides a list of the subsystems that are currently loaded and configured into the kernel. If you specify subsystem-name, the command displays information about the state of that subsystem. Each subsystem can have one of three states: Loaded and configured (available for use) Loaded and unconfigured (not available for use, but still loaded) This state applies only to static subsystems, which can be unconfigured but cannot be unloaded. Unloaded (not available for use) This state applies only to loadable subsystems, which are automatically unloaded from the kernel when you unconfigure them with the sysconfig -u command. Subsystems that are not being used can be unconfigured using the -u flag. Unconfiguring subsystems can help save kernel memory, making it available for other uses. You can unconfigure any static or loadable subsystem that supports run-time unconfiguration. If you unconfigure a loadable subsystem, that subsystem is also unloaded from the kernel. When you issue the sysconfig command, it opens a communications socket to a cfgmgr configuration management server on the target system. The target system can be your local system or a remote system specified by the -h flag. The sysconfig command uses the socket to send the configure, reconfigure, query attributes, query subsystem state, or unconfigure request. The sysconfig command receives output from the cfgmgr. You can use the sysconfig command to display the value of attributes on any system, local or remote. However, if you want to configure, reconfigure, or unconfigure a subsystem, you must be authorized to modify the kernel configuration on the target host. By default, the superuser (root login) can configure, reconfigure, or unconfigure the subsystems on the local host. To allow configuration, reconfigura- tion, or unconfiguration on a remote host, the file /etc/cfgmgr.auth must exist. This file lists each host that is allowed to configure, reconfigure, or unconfigure subsystems on the local host. See the cfgmgr.auth(4) reference page for more information about the cfgmgr.auth file and its format. Array Attributes Because the square bracket ([ and ]) characters have special meaning to the UNIX shell, when you try to query or reconfigure individual array elements from the shell command line, you must escape these two characters. For example sysconfig -q subsys1 attr1 attr2 attr3 When both -i and a subscript are specified, the subscript takes precedence. However, when no subscript is specified, the -i applies pro- viding the attribute is an array attribute. The command sysconfig -Q cannot be used to query an individual array element. EXAMPLES
The following list shows examples of using the sysconfig command: To display all the subsystems configured in the local kernel, enter the following command: # sysconfig -s Used without arguments, the -s flag displays information about the state of all subsystems on the local system. To configure a sub- system into the kernel, use the -c flag, as shown: # sysconfig -c cmftest This command configures a subsystem named cmftest into the kernel. If the subsystem is loadable, it is also loaded in response to this command. To query a subsystem on a remote host, issue a command such as the following one: # sysconfig -h salmon -q ipc This command displays information about the ipc subsystem on host salmon. To reconfigure an attribute, use the -r flag: # sysconfig -h salmon -r cmftest maxlen=255 -v This command modifies the cmftest subsystem by setting its maxlen attribute equal to 255. The cmftest subsystem on the remote host salmon is modified. The -v flag causes the sysconfig command to display debugging information, which may be displayed to the con- sole. To display the current settings of attributes in the /etc/sysconfigtab file, use the -d option as follows: # sysconfig -d generic generic: memberid = 0 new_vers_high = 1441151880873377792 new_vers_low = 15044 RETURN VALUES
The sysconfig program returns zero after successful completion of the specified operation. If an operation fails, the program returns one. If you specify multiple attributes in a single sysconfig operation, a zero is returned if at least one attribute operation is successful. A one is only returned if the sysconfig operation fails on every attribute. FILES
The configuration management server command path The kernel load server daemon command path The configuration management authorization database The configuration database RELATED INFORMATION
Commands: autosysconfig(8), cfgmgr(8), dxkerneltuner(8), sysconfigdb(8), kloadsrv(8) Files: sysconfigtab(4), cfgmgr.auth(4) System Administration delim off sysconfig(8)