I changed out one the two FC switches. It appears my paths have all come back up except for this one "dac0" which appears as "missing" and I'm not having any luck getting rid of that... All of the disks came back fine, just dac0 is missing. This output is from my lpar, not the underlying VIO server. Any ideas?
Hi , Migrating AIX 4.3.3 ML10 to 5.3 ML1 (retaining 32 bit)
after successfully going through 5 of the 5.3 Install CD's. After "All fileset's processed successfully " message I was told that system would reboot and then I would get prompted for setting TERm type ( i have an ascii ibm3151) and... (1 Reply)
Hi, I'm going to be involved in a migration of SAN islands to one big SAN. I've not worked with SANs before and I'm not sure how to approach this. I suspect the disk devices on the HP servers are going to change, when the EVA's and servers are plugged into this new Cisco 9509 switch.
Any... (0 Replies)
Hello All,
We want to upgrade our 44p Model 270 from AIX 5.2 to 5.3. This is a standalone devlopment server but downtime is something we don't want because we have a short development deadline looming. I have no tape drive to make backups to. I myself am a developer and don't have any... (4 Replies)
Hi,
redbook documentation is telling that IY17981 fix is required for aix 4.3.3 to aix 5L migration. But there is no mention about that fix in any ML installation packages.
- My system is ML11 :
oslevel –r
4330-11
- But xlC.rte is on wrong version :
lslpp -L xlC.rte
xlC.rte ... (3 Replies)
Hello gurus,
I am a SAN Admin - not very familiar with the HPUX administration - so need help with the steps in regards to the migration I need to do at my client place.
Environment: Migrating from CX4 to VMAX - using OR/Hot Pull.
Here are the steps I have put together - HPUX gurus please... (5 Replies)
I am going to do a SAN Array migration and need the sequence of steps required on the Solaris cluster before moving the old array luns to new array luns.
Here are the steps and I need info on the bold points:( I might even be wrong on the sequence of steps please correct me if I am wrong)
1.... (0 Replies)
Hi all,
We are migrating our SAN storage from HSV360 to 3PAR. The system runs aix 6.1 version with HACMP.
Please let me know what are requirements from OS side and how are the data copied to the new disks. (10 Replies)
Hi,
I am very new to HP-UX, and we're going to be doing a SAN migration.
We're going to take down the machine, and zone it to the new SAN.
My question is, will the device names change and will that interfere with the LVM?
If the new disks come in with different device names, how would I... (3 Replies)
I have an IBM blade running RHEL 5.4 server, connected to two Hitachi SANs using common fibre cards & Brocade switches. It has two volume groups made from old SAN LUNs. The old SAN needs to be retired so we allocated LUNs from the new SAN, discovered the LUNs as multipath disks (4 paths) and grew... (4 Replies)
I am working on VM host and collecting data to identify the type of storage attached to the server which will be migrated to VNX.
it has one ldom created on it
luxadm probe output ---
No Network Array enclosures found in /dev/es
Found Fibre Channel device(s):
Node... (7 Replies)
Discussion started by: kpatel786
7 Replies
LEARN ABOUT HPUX
lsdev
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)