|
I need some help figuring out if I'm way in over my head or just retarded. Moderate networking/system administration background with zero exposure to SCSI storage. Inherited a bunch of sweet equipment and I'm staging a HA Hyper-V environment. My problem is this: The SAN is making me feel like a moron. 2x Poweredge T410, Xeon 5630 /w 96 GB RAM for hosts with with 8 NICs each HP P2000 G3 iSCSI Dual controller /w 4x 1GB iSCSI per controller The person I inherited the SAN from had it set up with two gigabit switches for access, which I may not need since I plan on directly attaching the storage to my two hosts if possible (seems like it based on the documentation). It looks like the traffic is split into two data VLANs on the switches, which I don't believe I would need either. But my problems don't begin there. I can't even fathom how to connect to the SAN or mount the volumes. I have an IP address that I can ping on the management port but that's it. Is there some special way to use the Windows iSCSI initiator that I don't know about? Is there some configuration wizard or software controller from HP that I just can't find? Is there a guide for special people like myself? iSCSI SAN configuration for dummies turns up nothing
|
# ¿ Apr 11, 2014 19:39 |
|
|
# ¿ Apr 19, 2024 14:06 |
|
Oh my god it's a webserver I can't believe I didn't check that, thank you so much
|
# ¿ Apr 11, 2014 20:10 |
|
Thanks guys, I'll find a class to take or professional to mentor me before I dig into this further
|
# ¿ Apr 11, 2014 23:09 |
|
Just speaking from a Windows + GPO standpoint, I don't think that's possible? The whole point of sending Crtl + Alt + Delete is because it's a kernel interrupt, so it should supersede any VDI client (or fake login screen) on the host machine. Windows + L is a faster way to lock anyway.
|
# ¿ Jul 29, 2014 19:48 |
|
Zero VGS posted:2) I see in additional to the SAN I might also need a SAN Switch. If I'm never going beyond these two servers, is there any kind of PCI expansion I can get or something to plug the SAN's SAS cables directly into the servers and skip this SAN Switch business? The SAN switches are just for more redundancy and to keep your rack neat. If you have spare ports on a couple of other managed switches you can use those, but a basic implementation of a dual controller SAN would look like this with mgmt VLAN on port 1, data VLAN on ports 4-5, and trunks on 7-8. e: Assuming you're getting an iSCSI SAN. You'd have to buy a lot of equipment to implement FC. Roargasm fucked around with this message at 17:58 on Mar 25, 2015 |
# ¿ Mar 25, 2015 17:47 |
|
Hyper-V can do shared volumes with SMB shares, so if you don't mind screwing your future self you could get set up with a cheap NAS or Windows file server and maybe migrate later. Your NVR could be a killer VGS - that's 24/7 write during business hours and you'll need to give it multiple TB of storage to have a decent retention period in HD. Dedicated NVR boxes are a dime a dozen. And I'm not an engineer but I would never quote a HA virt setup for less than $30K.
|
# ¿ Mar 26, 2015 01:37 |
|
"Venom" security vulnerability threatens most datacenters
|
# ¿ May 13, 2015 15:11 |
|
NevergirlsOFFICIAL posted:Yeah there is iSCSI. iSCSI is block level storage (operating on bits) while most NAS is file level. In file level storage, a file needs to be locked while a client is writing to it, meaning no one else can do the same until it's done. That makes block level storage much better for shared virt or database environments since simultaneous access happens all the time. Roargasm fucked around with this message at 02:33 on Jun 4, 2015 |
# ¿ Jun 4, 2015 02:28 |
|
|
# ¿ Apr 19, 2024 14:06 |
|
Docjowles posted:I preface this by saying I have never tried this on the combination of Windows guests and VMware hosts, so it may not work for poo poo. I am a Linux guy these days. why this over puppet?
|
# ¿ May 26, 2017 17:36 |