Sponsored Content
Full Discussion: Any EVA admin's out there?
Operating Systems HP-UX Any EVA admin's out there? Post 302076014 by msuluhan on Thursday 8th of June 2006 08:32:31 AM
Old 06-08-2006
Hi

You can use alternated PV links for each PV link if you can't use SecurePath. But SecurePath has more advantages than alternated PV links

you can look at man page of pvcreate,

There is a section from man

When a pv_path refers to one of the physical volumes already in the volume group by a different pv_path name to indicate the use of a different controller, this new path becomes an alternate link to the physical volume. When two paths that reference the same disk are provided in the pv_path list, the order of the paths is important. The first path becomes the "primary link" to the physical volume, the second becomes an "alternate link" to the physical volume. The primary link is the path used to access the physical volume unless the primary link becomes unavailable in which case LVM automatically switches to the alternate link to access the physical volume. Currently LVM supports a maximum of 8 paths to a physical volume (7 alternates and one primary).

I hope it helps to your problem
 

6 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Can AIX 5.3 - 6 Boot From HP EVA 6000 SAN

Hi There, Has anyone had any luck with or know how to get AIX 5+ to boot from a HP EVA 6000 SAN? The servers used here will be P Class Blades My initial searches on this so far did not bring results so I am guessing this may not be possible on HP SAN's but please let me know if I am... (0 Replies)
Discussion started by: fazzasx
0 Replies

2. What is on Your Mind?

Windows Admin switching to *nix Admin

I'm currently a Windows admin and have wanted to jump ship to the *nix side for a while now. I've been studying both through an lpic level 1 manual as I have time (focusing on debian), and a solaris 10 cert book. The problem is I only have a handful of hours a week to study, and my current job... (3 Replies)
Discussion started by: bobwilson
3 Replies

3. Solaris

EVA storage HUNG / Solaris issue

Hi, I have a query , is it possible that few LUNs presented to the Solaris OS which are in the unlabeled state can hung EVA frame and cause it to get unresponsive ? please help. thanks. (1 Reply)
Discussion started by: mushtaq
1 Replies

4. AIX

Attach HP EVA to IBM AIX powerpc singlepath

Dear all. We have a very big issue on Attach HP EVA to IBM AIX powerpc singlepath. the configurations on lscfg -vl fcs2 fcs2 U789C.001.DQD8D74-P1-C2-T1 4Gb FC PCI Express Adapter (df1000fe) Part Number.................10N7249 Serial... (3 Replies)
Discussion started by: Juri_al
3 Replies

5. What is on Your Mind?

Regarding Admin life either as DBA or UNIX Linux admin

I am planning to choose my career as Unix/Linux Admin or a DBA. But I have come to know from forums and few admins like the job will be 24/7. I have few questions on that. Can we get "DAY" shifts in any one of the admin Job ? Can't we have shift timings in any company ? Eventhough the... (7 Replies)
Discussion started by: Jacktts
7 Replies

6. Filesystems, Disks and Memory

Some question about SAN on HP 4400 EVA

Good morning. For testing purpose i have buy a SAN DISK SHELF i need now a controller(hsv300) and a switch SAN Is my first SAN so i'm a little confused about cables. For testing we use an old rx2600 hp server the adapter is HP A6795AX A6795-62001 Some fast questions: i need an fc/fc cable... (7 Replies)
Discussion started by: Linusolaradm1
7 Replies
pci_config_get8(9F)					   Kernel Functions for Drivers 				       pci_config_get8(9F)

NAME
pci_config_get8, pci_config_get16, pci_config_get32, pci_config_get64, pci_config_put8, pci_config_put16, pci_config_put32, pci_con- fig_put64, pci_config_getb, pci_config_getl, pci_config_getll, pci_config_getw, pci_config_putb, pci_config_putl, pci_config_putll, pci_config_putw - read or write single datum of various sizes to the PCI Local Bus Configuration space SYNOPSIS
#include <sys/ddi.h> #include <sys/sunddi.h> uint8_t pci_config_get8(ddi_acc_handle_t handle, off_t offset); uint16_t pci_config_get16(ddi_acc_handle_t handle, off_t offset); uint32_t pci_config_get32(ddi_acc_handle_t handle, off_t offset); uint64_t pci_config_get64(ddi_acc_handle_t handle, off_t offset); void pci_config_put8(ddi_acc_handle_t handle, off_t offset, uint8_t value); void pci_config_put16(ddi_acc_handle_t handle, off_t offset, uint16_t value); void pci_config_put32(ddi_acc_handle_t handle, off_t offset, uint32_t value); void pci_config_put64(ddi_acc_handle_t handle, off_t offset, uint64_t value); INTERFACE LEVEL
Solaris DDI specific (Solaris DDI). PARAMETERS
handle The data access handle returned from pci_config_setup(9F). offset Byte offset from the beginning of the PCI Configuration space. value Output data. DESCRIPTION
These routines read or write a single datum of various sizes from or to the PCI Local Bus Configuration space. The pci_config_get8(), pci_config_get16(), pci_config_get32(), and pci_config_get64() functions read 8 bits, 16 bits, 32 bits, and 64 bits of data, respectively. The pci_config_put8(), pci_config_put16(), pci_config_put32(), and pci_config_put64() functions write 8 bits, 16 bits, 32 bits, and 64 bits of data, respectively. The offset argument must be a multiple of the datum size. Since the PCI Local Bus Configuration space is represented in little endian data format, these functions translate the data from or to native host format to or from little endian format. pci_config_setup(9F) must be called before invoking these functions. RETURN VALUES
pci_config_get8(), pci_config_get16(), pci_config_get32(), and pci_config_get64() return the value read from the PCI Local Bus Configura- tion space. CONTEXT
These routines can be called from user, kernel, or interrupt context. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |PCI Local Bus | +-----------------------------+-----------------------------+ SEE ALSO
attributes(5), pci_config_setup(9F), pci_config_teardown(9F) NOTES
These functions are specific to PCI bus device drivers. For drivers using these functions, a single source to support devices with multiple bus versions may not be easy to maintain. The functions described in this manual page previously used symbolic names which specified their data access size; the function names have been changed so they now specify a fixed-width data size. See the following table for the new name equivalents: SunOS 5.10 1 Jan 1997 pci_config_get8(9F)
All times are GMT -4. The time now is 06:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy