07-28-2015
I don't know the name of your managed system. It is the IBM server, where all your LPARs reside. You can look which managed systems you have using the command lssyscfg -r sys -F name
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
in TCP, is TIME_WAIT state really essential..!!! (3 Replies)
Discussion started by: sasikanth
3 Replies
2. Solaris
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
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
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
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
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
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
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
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
lsdev(1M) lsdev(1M)
NAME
lsdev - list device drivers in the system
SYNOPSIS
driver | class] block_major] char_major] major] [major ...]
DESCRIPTION
The command lists, one pair per line, the major device numbers and driver names of device drivers configured into the system and available
for invocation via special files. A in either the block or character column means that a major number does not exist for that type.
If no arguments are specified, lists all drivers configured into the system.
If the option is specified, will not print a heading. This option may be useful when the output of will be used by another program.
The and options are used to select specific device drivers for output. If more than one option is specified, all drivers that match the
criteria specified by those options will be listed. These search options are divided into two types: name search keys (the and options)
and major number search keys (the and options). If both types of options are present, only entries that match both types are printed. The
same type of option may appear more than once on the command line with each occurrence providing an ORing effect of that search type. The
and options may not be specified at the same time.
The ability to process major arguments is provided for compatibility and functions like the option.
Options
List device drivers that match
class.
List device drivers with the name
driver.
List device drivers with a block major number of
block_major.
List device drivers with a character major number of
char_major.
List device drivers with either a character
major number or block major equal to major.
DIAGNOSTICS
The and options may not be specified at the same time.
A major number is malformed or out of range.
EXAMPLES
To output entries for all drivers in the class:
To output entries that are in the class that have either a block or character major number of
To get the character major number of into a shell environment variable:
WARNINGS
Some device drivers available from the system may be intended for use by other drivers. Attempting to use them directly from a special
file may produce unexpected results.
A driver may be listed even when the hardware requiring the driver is not present. Attempts to access a driver without the corresponding
hardware will fail.
only lists drivers that are configured into the currently executing kernel. For a complete list of available drivers, please run (see
sam(1M).
DEPENDENCIES
Since relies on the device driver information provided in a routine, may not list drivers installed by other means.
AUTHOR
was developed by HP.
SEE ALSO
sam(1M).
Section 7 entries related to specific device drivers.
lsdev(1M)