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
ISCSID(8)						    BSD System Manager's Manual 						 ISCSID(8)

NAME
iscsid -- interface to kernel iSCSI driver SYNOPSIS
iscsid [-n] [-d lvl] DESCRIPTION
The iSCSI initiator runs as a kernel driver, and provides access to iSCSI targets running across a network using the iSCSI protocol, RFC 3720. The iscsid utility itself interfaces to the kernel iSCSI driver, and also communicates, using isns(3), with the iSCSI name service running on other hosts to locate services and iSCSI instances. In normal operation, iscsid is a standard daemon, and will detach from the controlling terminal using daemon(3) and then loops, reading requests, processing them, and sending responses. Communication takes place over a Unix domain socket. iscsid exits on receiving a terminate message, (no response to one that is sent to the kernel), or when an error occurs reading from or writing to the socket. The -d flag increases the debug level to lvl. Any level above 0 causes iscsid to remain in the foreground, and increases the amount of debug output. The -n flag makes the daemon single-threaded. It is envisaged that user-level communication take place with iscsid using the iscsictl(8) utility, rather than directly over its communica- tion socket. An example of setting up the in-kernel iSCSI initiator is shown in iscsictl(8). SEE ALSO
daemon(3), isns(3), iscsictl(8) HISTORY
The iscsid utility appeared in NetBSD 6.0. AUTHORS
Alistair Crooks <agc@NetBSD.org> wrote this manual page. The iscsid utility was contributed by Wasabi Systems, Inc. BSD
May 27, 2012 BSD
All times are GMT -4. The time now is 02:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy