Sponsored Content
Operating Systems HP-UX is anybody using EMC symmetrix? Post 87996 by kduffin on Sunday 30th of October 2005 11:18:58 PM
Old 10-31-2005
Powerlink requires registration from an organization with EMC support. If you have an issue getting EMC to issue you a login, contact your EMC rep and he/she can push it through. Be sure to extoll which products you should have access to as product realms are segregated in Powerlink.

Cheers,

Keith
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Good sites to learn EMC symmetrix

i need to learn this very quick. i'm not trying delve deep into it. just enough to do basic things. does anyone know of any good sites to visit?? (1 Reply)
Discussion started by: TRUEST
1 Replies

2. Solaris

Emc

Dear gentelmen kindly please update me me how can i know disks on EMC and get size for all disks on EMC? (1 Reply)
Discussion started by: magasem
1 Replies

3. HP-UX

Emc

Dear gentelmen kindly please update me how can i know disks on EMC and get size for all disks on EMC? (0 Replies)
Discussion started by: magasem
0 Replies

4. HP-UX

Adding a new set of hardisk in EMC Symmetrix

Hello everyone! Could anybody help me how to configure a set of disk? From our existing EMC storage, we still have spaces for a new set of disk. I know how to replace a deffective disk but never had experience in setting/replacing a new pair of disk (M1 and M2). My objective here is to increase... (1 Reply)
Discussion started by: Tris
1 Replies

5. Solaris

EMC Failover

Hi guys, I'm running vxdmp and powerpath at the same time. Vxdmp for internal disks and powerpath for external. The problem is that, on the failover tests which a fiber cable should be removed, the system cannot recognize the disks. Any hints on how to configure powerpath in order to... (4 Replies)
Discussion started by: glenioborges
4 Replies

6. Red Hat

Configure EMC Powerpath?

Hi , I have a redhat 5.3 server which has 2 vg.. one is rootvg in local harddisk and another one is applicationvg in SAN.. When I reboot the server , EMC powerpath driver is not starting up automatically. Hence applicationvg is not mounting properly. Therefore I need to unmount it manually and... (4 Replies)
Discussion started by: Makri
4 Replies

7. AIX

Need EMC Symmetrix driver for AIX 5.3

Hi all, I hope I'm putting my first post at this site into the right forum. I need help finding the EMC disk driver for AIX version 5.3. I have some new EMC disk presented to a backup server of mine, and right now the EMC hdisks show up looking like this in an lsdev: hdisk495 Available... (2 Replies)
Discussion started by: C.J.Hund
2 Replies

8. AIX

Help with EMC BCV device

I'm trying to auto-mount EMC Symmetrix BCV device at boot. but having problem making BCV available. I put script called mkbcv to the inittab and engineer suggested to add 120 sec sleep between cfgmgr so I did that also. My mkbcv script seems to be working fine, it says "hdisk4 Available" ... (1 Reply)
Discussion started by: shuhei365
1 Replies

9. AIX

AIX Sanboot from EMC Symmetrix with NPIV

Hi All.. On to a new implementation with AIX 7.1 san boot from EMC disks (Using NPIV). Anyone played with this recently? Wondering if we need PowerPath on the AIX clients or has native MPIO matured to replace it. Thoughts? Thanks Mr B (6 Replies)
Discussion started by: balaji_prk
6 Replies
SCSI_ID(8)						   Linux Administrator's Manual 						SCSI_ID(8)

NAME
scsi_id - retrieve and generate a unique SCSI identifier SYNOPSIS
scsi_id [options] DESCRIPTION
scsi_id queries a SCSI device via the SCSI INQUIRY vital product data (VPD) page 0x80 or 0x83 and uses the resulting data to generate a value that is unique across all SCSI devices that properly support page 0x80 or page 0x83. If a result is generated it is sent to standard output, and the program exits with a zero value. If no identifier is output, the program exits with a non-zero value. scsi_id is primarily for use by other utilities such as udev that require a unique SCSI identifier. By default all devices are assumed black listed, the --whitelisted option must be specified on the command line or in the config file for any useful behaviour. SCSI commands are sent directly to the device via the SG_IO ioctl interface. In order to generate unique values for either page 0x80 or page 0x83, the serial numbers or world wide names are prefixed as follows. Identifiers based on page 0x80 are prefixed by the character 'S', the SCSI vendor, the SCSI product (model) and then the the serial number returned by page 0x80. For example: # /lib/udev/scsi_id --page=0x80 --whitelisted --device=/dev/sda SIBM 3542 1T05078453 Identifiers based on page 0x83 are prefixed by the identifier type followed by the page 0x83 identifier. For example, a device with a NAA (Name Address Authority) type of 3 (also in this case the page 0x83 identifier starts with the NAA value of 6): # /lib/udev/scsi_id --page=0x83 --whitelisted --device=/dev/sda 3600a0b80000b174b000000d63efc5c8c OPTIONS
--blacklisted The default behaviour - treat the device as black listed, and do nothing unless a white listed device is found in the scsi_id con- fig-file. --device=device Send SG_IO commands to device, such as /dev/sdc. --config=config-file Read configuration and black/white list entries from config-file rather than the default /etc/scsi_id.config file. --whitelisted Treat the device as white listed. The --whitelisted option must be specified on the command line or in the scsi_id configuration file for scsi_id to generate any output. --page=0x80|0x83|pre-spc3-83 Use SCSI INQUIRY VPD page code 0x80, 0x83, or pre-spc3-83. The default behaviour is to query the available VPD pages, and use page 0x83 if found, else page 0x80 if found, else nothing. Page pre-spc3-83 should only be utilized for those scsi devices which are not compliant with the SPC-2 or SPC-3 format for page 83. While this option is used for older model 4, 5, and 6 EMC Symmetrix devices, its use with SPC-2 or SPC-3 compliant devices will fallback to the page 83 format supported by these devices. --replace-whitespace Reformat the output : replace all whitespaces by underscores. --export Export all data in KEY=<value> format used to import in other programs. --verbose Generate verbose debugging output. --version Display version number and exit. FILES
/etc/scsi_id.config Configuration of black/white list entries and per device options: # one config per line, short match strings match longer strings # vendor=string[,model=string],options=<per-device scsi_id command line options> vendor="ATA",options=-p 0x80 SEE ALSO
udev(7) AUTHORS
Developed by Patrick Mansfield <patmans@us.ibm.com> based on SCSI ID source included in earlier linux 2.5 kernels, sg_utils source, and SCSI specifications. December 2003 SCSI_ID(8)
All times are GMT -4. The time now is 03:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy