Sponsored Content
Operating Systems AIX AIX - FC Switch migration, SAN Migration question! Post 302952253 by agent.kgb on Sunday 16th of August 2015 12:44:51 PM
Old 08-16-2015
For standard AIX MPIO - lspath, for IBM SDD PCM - pcmpath, Hitachi and their OEMs - dlnkmgr.

If the link is down on your HBA port, you should see it using either fcstat or lsattr -El fscsiX where X is the number of your device.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

AIX Migration

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)
Discussion started by: Student37
1 Replies

2. HP-UX

SAN migration

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)
Discussion started by: Hils
0 Replies

3. AIX

AIX 5.2 to 5.3 migration

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

4. AIX

IY17981 fix required for aix 4.3.3 to aix 5L migration but not found

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

5. HP-UX

SAN Migration of HP-UX hosts

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)
Discussion started by: jps460
5 Replies

6. Solaris

Need Help On Solaris Cluster Steps For San Migration

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)
Discussion started by: sunshinedeepu
0 Replies

7. AIX

SAN Migration

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)
Discussion started by: ElizabethPJ
10 Replies

8. HP-UX

SAN Migration question

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

9. Red Hat

Volume group not activated at boot after SAN migration

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

10. Solaris

How to identify if disk is attached to SAN and assist in migration.?

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
pcilib(7)							 The PCI Utilities							 pcilib(7)

NAME
pcilib - a library for accessing PCI devices DESCRIPTION
The PCI library (also known as pcilib and libpci) is a portable library for accessing PCI devices and their configuration space. ACCESS METHODS
The library supports a variety of methods to access the configuration space on different operating systems. By default, the first matching method in this list is used, but you can specify override the decision (see the -A switch of lspci). linux-sysfs The /sys filesystem on Linux 2.6 and newer. The standard header of the config space is available to all users, the rest only to root. Supports extended configuration space, PCI domains, VPD (from Linux 2.6.26), physical slots (also since Linux 2.6.26) and information on attached kernel drivers. linux-proc The /proc/bus/pci interface supported by Linux 2.1 and newer. The standard header of the config space is available to all users, the rest only to root. intel-conf1 Direct hardware access via Intel configuration mechanism 1. Available on i386 and compatibles on Linux, Solaris/x86, GNU Hurd and Windows. Requires root privileges. intel-conf2 Direct hardware access via Intel configuration mechanism 2. Available on i386 and compatibles on Linux, Solaris/x86, GNU Hurd and Windows. Requires root privileges. Warning: This method is able to address only the first 16 devices on any bus and it seems to be very unreliable in many cases. fbsd-device The /dev/pci device on FreeBSD. Requires root privileges. aix-device Access method used on AIX. Requires root privileges. nbsd-libpci The /dev/pci0 device on NetBSD accessed using the local libpci library. obsd-device The /dev/pci device on OpenBSD. Requires root privileges. dump Read the contents of configuration registers from a file specified in the dump.name parameter. The format corresponds to the output of lspci -x. PARAMETERS
The library is controlled by several parameters. They should have sensible default values, but in case you want to do something unusual (or even something weird), you can override them (see the -O switch of lspci). Parameters of specific access methods dump.name Name of the bus dump file to read from. fbsd.path Path to the FreeBSD PCI device. nbsd.path Path to the NetBSD PCI device. obsd.path Path to the OpenBSD PCI device. proc.path Path to the procfs bus tree. sysfs.path Path to the sysfs device tree. Parameters for resolving of ID's via DNS net.domain DNS domain containing the ID database. net.cache_name Name of the file used for caching of resolved ID's. SEE ALSO
lspci(8), setpci(8), update-pciids(8) AUTHOR
The PCI Utilities are maintained by Martin Mares <mj@ucw.cz>. pciutils-3.1.7 31 January 2010 pcilib(7)
All times are GMT -4. The time now is 06:27 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy