|
|
Sponsored Content
Operating Systems
HP-UX
Any EVA admin's out there?
Post 302075951 by mr_manny on Wednesday 7th of June 2006 06:40:00 PM
06-07-2006
Any EVA admin's out there?
I was conveniently excluded from some EVA8000 training, and now find myself with an EVA zoned, but no physical devices 
My ioscan appears as follows:
ba 1 0/1 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
fc 0 0/1/0/0 td CLAIMED INTERFACE HP Tachyon TL/TS Fibre Channel Mass Storage Adapter
/dev/td0
fcp 2 0/1/0/0.1 fcp CLAIMED INTERFACE FCP Domain
ext_bus 11 0/1/0/0.1.12.0.0 fcparray CLAIMED INTERFACE FCP Array Interface
target 16 0/1/0/0.1.12.0.0.0 tgt CLAIMED DEVICE
ctl 9 0/1/0/0.1.12.0.0.0.0 sctl CLAIMED DEVICE HP HSV210
/dev/rscsi/c11t0d0
target 17 0/1/0/0.1.12.0.0.1 tgt CLAIMED DEVICE
ctl 10 0/1/0/0.1.12.0.0.1.0 sctl CLAIMED DEVICE HP HSV210
/dev/rscsi/c11t1d0
target 18 0/1/0/0.1.12.0.0.2 tgt CLAIMED DEVICE
ctl 11 0/1/0/0.1.12.0.0.2.0 sctl CLAIMED DEVICE HP HSV210
/dev/rscsi/c11t2d0
target 19 0/1/0/0.1.12.0.0.3 tgt CLAIMED DEVICE
ctl 12 0/1/0/0.1.12.0.0.3.0 sctl CLAIMED DEVICE HP HSV210
/dev/rscsi/c11t3d0
target 20 0/1/0/0.1.12.0.0.4 tgt CLAIMED DEVICE
ctl 13 0/1/0/0.1.12.0.0.4.0 sctl CLAIMED DEVICE HP HSV210
/dev/rscsi/c11t4d0
target 21 0/1/0/0.1.12.0.0.5 tgt CLAIMED DEVICE
ctl 14 0/1/0/0.1.12.0.0.5.0 sctl CLAIMED DEVICE HP HSV210
/dev/rscsi/c11t5d0
target 22 0/1/0/0.1.12.0.0.6 tgt CLAIMED DEVICE
ctl 15 0/1/0/0.1.12.0.0.6.0 sctl CLAIMED DEVICE HP HSV210
/dev/rscsi/c11t6d0
We have two controllers zoned to the same luns, but It is my understanding that we may need a product called secure path.
Is there a way to configure an EVA w/pvlinks (no secure path)?
There appear to be a few failover modes on the EVA...
server OS = 11.0
any assistance would be appreciated,
manny
My ioscan appears as follows:
ba 1 0/1 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
fc 0 0/1/0/0 td CLAIMED INTERFACE HP Tachyon TL/TS Fibre Channel Mass Storage Adapter
/dev/td0
fcp 2 0/1/0/0.1 fcp CLAIMED INTERFACE FCP Domain
ext_bus 11 0/1/0/0.1.12.0.0 fcparray CLAIMED INTERFACE FCP Array Interface
target 16 0/1/0/0.1.12.0.0.0 tgt CLAIMED DEVICE
ctl 9 0/1/0/0.1.12.0.0.0.0 sctl CLAIMED DEVICE HP HSV210
/dev/rscsi/c11t0d0
target 17 0/1/0/0.1.12.0.0.1 tgt CLAIMED DEVICE
ctl 10 0/1/0/0.1.12.0.0.1.0 sctl CLAIMED DEVICE HP HSV210
/dev/rscsi/c11t1d0
target 18 0/1/0/0.1.12.0.0.2 tgt CLAIMED DEVICE
ctl 11 0/1/0/0.1.12.0.0.2.0 sctl CLAIMED DEVICE HP HSV210
/dev/rscsi/c11t2d0
target 19 0/1/0/0.1.12.0.0.3 tgt CLAIMED DEVICE
ctl 12 0/1/0/0.1.12.0.0.3.0 sctl CLAIMED DEVICE HP HSV210
/dev/rscsi/c11t3d0
target 20 0/1/0/0.1.12.0.0.4 tgt CLAIMED DEVICE
ctl 13 0/1/0/0.1.12.0.0.4.0 sctl CLAIMED DEVICE HP HSV210
/dev/rscsi/c11t4d0
target 21 0/1/0/0.1.12.0.0.5 tgt CLAIMED DEVICE
ctl 14 0/1/0/0.1.12.0.0.5.0 sctl CLAIMED DEVICE HP HSV210
/dev/rscsi/c11t5d0
target 22 0/1/0/0.1.12.0.0.6 tgt CLAIMED DEVICE
ctl 15 0/1/0/0.1.12.0.0.6.0 sctl CLAIMED DEVICE HP HSV210
/dev/rscsi/c11t6d0
We have two controllers zoned to the same luns, but It is my understanding that we may need a product called secure path.
Is there a way to configure an EVA w/pvlinks (no secure path)?
There appear to be a few failover modes on the EVA...
server OS = 11.0
any assistance would be appreciated,
manny
|
|
6 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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?
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
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
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?
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
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
LEARN ABOUT CENTOS
scsi_stop
SCSI_STOP(8) SG3_UTILS SCSI_STOP(8) NAME
scsi_stop - stop (spin down) one or more SCSI disks SYNOPSIS
scsi_stop [--help] [--verbose] [--wait] DEVICE [DEVICE]* DESCRIPTION
This bash shell script calls the sg_start utility on each given DEVICE. The purpose is to spin down (stop) each given DEVICE. OPTIONS
Arguments to long options are mandatory for short options as well. -h, --help print out the usage message then exit. -v, --verbose increase level or verbosity. -w, --wait wait for the spin down (stop) on each given DEVICE to complete. The default action is to do each stop in immediate mode. NOTES
The sg_start utility calls the SCSI START STOP UNIT command and can either start (spin up) or stop (spin down) a SCSI disk depending on the given command line options. EXIT STATUS
The exit status of this script is 0 when it is successful. Otherwise the exit status is that of the last sg_start utility called. See the sg3_utils(8) man page. AUTHORS
Written by D. Gilbert COPYRIGHT
Copyright (C) 2009-2013 Douglas Gilbert This software is distributed under a FreeBSD license. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR- POSE. SEE ALSO
sg_start (sg3_utils) sg3_utils-1.36 May 2013 SCSI_STOP(8)