Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory Some question about SAN on HP 4400 EVA Post 302957951 by cjcox on Friday 16th of October 2015 07:06:06 PM
Old 10-16-2015
So... generally for a minimal san, as you mentioned there is the storage, the switch and the host side.

I all of those case if the "holes" look like an empty rectangular hole, then those holes are missing SFP+ modules. In some cases you can purchase Twinax cables instead of going fiber to do this, in which case the SFP+ sides come with the cable, because your HP through and through, an HP rep can probabably see you such a cable. It will probably come out cheaper then individual SFP+'s and fiber cabling.

With all that said, the SFP+ is important, as vendors just don't generically handle SFP+'s. So make sure you get the right SFP+ for your devices. HP should be able to help.


And yes, you need connection from HBA (host) to switch and from storage to switch. Often times multiple for redundancy (multipath). You'll want multipath if this for enterprise use. If for home, then just single runs will do for playing around with SAN.

If going "discount" you probably would have done better with something more generic (like Nexsan) vs. an EVA. That way you have less problems with SFP's. My favorite is Qlogic switches, HBAs and Nexsan. But I know that Qlogic isn't going to popular anymore.

Today, I'd go Arista 10GBase-T, and go all copper Cat-6A for iSCSI. More generic, costs a lot less overall. But that's if I'm defining something new for the enterprise. If FC, then my choice (in the near past) would have been Qlogic HBAs, Qlogic switch (at least 8Gbit) and Nexsan. I'm a bit frustrated by the FC world right now, though I like it over iSCSI (better performing, easier to work with). Mainly because of all the SFP+ lock in.

FCoE? Suffers from too many of the same problems as iSCSI. To me these are just about equal. Theoretically easier to setup FCoE vs. iSCSI though.

And yes you can go straight from storage to host HBA. You dont' have to have a SAN.
 

9 More Discussions You Might Find Interesting

1. Linux Benchmarks

PowerMac 4400 YLD 3.0

CPU/Speed: PowerPC 603ev 200Mhz Ram: 92M EDO Ram Motherboard: Apple Bus: 2 PCI Cache: L1 32k and L2 256k Controller: ATA Disk: 2GB ATA Load: 1 user, running httpd, Xwin, various daemons Kernel: Linux 2.4.22-2f Kernel ELF?: ??? pgms: gcc versión 3.2.2 20030217 (Yellow Dog Linux 3.0 3.2.2-2a);... (0 Replies)
Discussion started by: clemare
0 Replies

2. HP-UX

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 ... (3 Replies)
Discussion started by: mr_manny
3 Replies

3. Solaris

Thoughts/experiences of SAN attaching V880 to EMC SAN

Hi everyone, I wonder if I can canvas any opinions or thoughts (good or bad) on SAN attaching a SUN V880/490 to an EMC Clarion SAN? At the moment the 880 is using 12 internal FC-AL disks as a db server and seems to be doing a pretty good job. It is not I/O, CPU or Memory constrained and the... (2 Replies)
Discussion started by: si_linux
2 Replies

4. AIX

Question about IBM San Ds4500

I have a question about SAN commands I have almost 15Tb of disk on my san but assigned and something else I have almost 11Tb There is a command to know, what its my real total storage capacity and another command to know how much I used .? Thanks again in advance (0 Replies)
Discussion started by: lo-lp-kl
0 Replies

5. 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

6. Red Hat

SAN/LVM question

Hey everyone. I am working on designing a logging solution for a deployment we have going out in a few months. Right now we have a single storage head end, connected via fibre to a SAN. Basically the plan is to create a number of smaller LUNs on the SAN, and then use LVM2 to handle concatenating... (5 Replies)
Discussion started by: msarro
5 Replies

7. 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

8. AIX

GPFS initial setup, but perhaps this is a SAN/VIO question

I'm having some trouble getting a POC of GPFS up and running. I've read a couple install guides including a couple IBM pdfs but I'm getting stumped on something I think is fairly fundamental.... I'm trying to do this all on a single 795, right now only the VIOs have HBAs so all LUNs are pointed to... (3 Replies)
Discussion started by: kneemoe
3 Replies

9. 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
ISP(4)							   BSD Kernel Interfaces Manual 						    ISP(4)

NAME
isp -- Qlogic based SCSI and FibreChannel SCSI Host Adapters SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device scbus device isp Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): isp_load="YES" DESCRIPTION
This driver provides access to SCSI or FibreChannel devices. SCSI features include support for Ultra SCSI and wide mode transactions for SCSI, Ultra2 LVD (for the ISP1080 and ISP1280), and Ultra3 LVD (for the ISP12160). Fibre Channel support uses FCP SCSI profile for FibreChannel. and utilizes Class 3 and Class 2 connections (Qlogic 2100 is Class 3 only, minor patches to the Qlogic 2200 to force Class 2 mode). Support is available for Public and Private loops, and for point-to-point connec- tions (Qlogic 2200 only). The newer 2-Gigabit cards (2300, 2312, 2322) and 4-Gigabit (2422, 2432) are also supported. Command tagging is supported for all (in fact, FibreChannel requires tagging). Fabric support is enabled by default for other than 2100 cards. Fabric support for 2100 cards has been so problematic and these cards are so old now that it is just not worth your time to try it. FIRMWARE
Firmware is available if the ispfw(4) module is loaded during bootstrap (q.v.). It is strongly recommended that you use the firmware available from ispfw(4) as it is the most likely to have been tested with this driver. HARDWARE
Cards supported by the isp driver include: ISP1000 SBus Fast Wide, Ultra Fast Wide cards, Single Ended or Differential cards. ISP1020 Qlogic 1020 Fast Wide and Differential Fast Wide PCI cards. ISP1040 Qlogic 1040 Ultra Wide and Differential Ultra Wide PCI cards. Also known as the DEC KZPBA-CA (single ended) and KZPBA-CB (HVD differential). Qlogic 1240 Qlogic 1240 Dual Bus Ultra Wide and Differential Ultra Wide PCI cards. Qlogic 1020 Qlogic 1020 SCSI cards. Qlogic 1040 Qlogic 1040 Ultra SCSI cards. Qlogic 1080 Qlogic 1280 LVD Ultra2 Wide PCI cards. Qlogic 1280 Qlogic 1280 Dual Bus LVD Ultra2 Wide PCI cards. Qlogic 12160 Qlogic 12160 Dual Bus LVD Ultra3 Wide PCI cards. Qlogic 210X Qlogic 2100 and 2100A Copper and Optical Fibre Channel Arbitrated Loop (single, dual). Qlogic 220X Qlogic 2200 Copper and Optical Fibre Channel Arbitrated Loop PCI cards (single, dual, quad). Qlogic 2300 Qlogic 2300 Optical Fibre Channel PCI cards. Qlogic 2312 Qlogic 2312 Optical Fibre Channel PCI cards. Qlogic 234X Qlogic 234X Optical Fibre Channel PCI cards (2312 chipset, single and dual attach). Qlogic 2322 Qlogic 2322 Optical Fibre Channel PCIe cards. Qlogic 200 Dell Branded version of the QLogic 2312 Fibre Channel PCI cards. Qlogic 2422 Qlogic 2422 Optical Fibre Channel PCI cards (4 Gigabit) Qlogic 2432 Qlogic 2432 Optical Fibre Channel PCIe cards (4 Gigabit) CONFIGURATION OPTIONS
Target mode support may be enabled with the options ISP_TARGET_MODE option. BOOT OPTIONS
The following options are switchable by setting values in /boot/device.hints. They are: hint.isp.0.disable A hint value to disable driver in kernel. hint.isp.0.fwload_disable A hint value to disable loading of firmware ispfw(4). hint.isp.0.prefer_memmap A hint value to use PCI memory space instead of I/O space access for. hint.isp.0.prefer_iomap A hint value to use PCI I/O space instead of Memory space access for. hint.isp.0.ignore_nvram A hint value to ignore board NVRAM settings for. Otherwise use NVRAM settings. hint.isp.0.fullduplex A hint value to set full duplex mode. hint.isp.0.topology A hint value to select topology of connection. Supported values are: lport Prefer loopback and fallback to point to point. nport Prefer point to point and fallback to loopback. lport-only Loopback only. nport-only Point to point only. hint.isp.0.portwwn This should be the full 64 bit World Wide Port Name you would like to use, overriding the value in NVRAM for the card. hint.isp.0.nodewwn This should be the full 64 bit World Wide Node Name you would like to use, overriding the value in NVRAM for the card. hint.isp.0.iid A hint to override or set the Initiator ID or Loop ID. For Fibre Channel cards in Local Loop topologies it is strongly recommended that you set this value to non-zero. hint.isp.0.role A hint to define default role for isp instance (target, initiator, both). hint.isp.0.debug A hint value for a driver debug level (see the file /usr/src/sys/dev/isp/ispvar.h for the values. SYSCTL OPTIONS
dev.isp.N.loop_down_limit This value says how long to wait in seconds after loop has gone down before giving up and expiring all of the devices that were visi- ble. The default is 300 seconds (5 minutes). A separate (nonadjustable) timeout is used when booting to not stop booting on lack of FC connectivity. dev.isp.N.gone_device_time This value says how long to wait for devices to reappear if they (temporarily) disappear due to loop or fabric events. While this timeout is running, I/O to those devices will simply be held. dev.isp.N.wwnn This is the readonly World Wide Node Name value for this port. dev.isp.N.wwpn This is the readonly World Wide Port Name value for this port. SEE ALSO
da(4), intro(4), ispfw(4), sa(4), scsi(4), gmultipath(8) AUTHORS
The isp driver was written by Matthew Jacob originally for NetBSD at NASA/Ames Research Center. BUGS
The driver currently ignores some NVRAM settings. Target mode support is not completely reliable yet. It works reasonably well for Fibre Channel, somewhat well for Qlogic 1040 cards, but does not yet work for the other cards (due to last minute unannounced changes in firmware interfaces). BSD
February 28, 2007 BSD
All times are GMT -4. The time now is 03:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy