Something everyone carries around with them, a camera phone, can be a massive help. Even if the light is so faint that you can barely make it out, you should be able to tell the difference with a camera phone.
Here's an example of a rx cable (with no light coming from it):
Here's an example of a tx cable (with light coming from it):
It's really blurry ...
You can use multipath FC connections from your servers to the MSA2040 without the use of a switch.
You would connect your HBAs on thee servers to each of the two controllers on the MSA. The MSA2040 was designed for this, and this is a fully supported cabling and VMware host design.
Sure you can do that. Good summary is here:
Some good play with SCST instead of a default LIO is here (uses QLogic HBAs):
In a nutshell: You can expose any physical or virtual block device as FC target.
Mainly you want to make sure your VM's will be OK with no disk IO. Installing the VMware tools will take care of this with 4.x and newer. You also want to set the right settings on your ESX hosts related to timeouts, these are detailed on the netapp site in TR-3749
Really it does not matter which protocol you are using for cluster fail overs since the ...
It's a hard disk with a FC interface.
Nope, you probably can't just arbitrarily replace one of them with a disk with a different interface, and different IO characteristics, especially in a storage array. But ask your vendor to be certain, or consult their documentation!
If you have a single port on each switch that's logging in as a loop port, you need to address this. The first thing I'd do is try unplugging it and plugging it back in. If it still shows up as a loop port when it relogs back into the fabric, take a look at hard-coding the port to be an F port. I found instructions here.
Be prepared that if there's some ...
FC doesn't use LAG to achieve link redundancy or aggregation. It uses MultiPath IO (MPIO) to establish multiple logical communications channels and presents them to the storage subsystem as a single device.
I do not see any reason to do this nowadays.
You have modern ethernet NICs with high bandwidth and throughput.
Also you do not introduce all kind of inflexibilities introduced with FC and IPFC.
Some of them:
You can't aggregate FC HBAs -> combine both 10GbE and get 20GbE. You can have them active/standby or use both active/active and get 5Gbps on each.
You should be able to do that. Good guide here:
I'd still leave all the storage mgmt to hypervisor and deal with VHDX only. With shared VHDX, and major improvements around it in WS2016 you don't need raw access to FC anymore. IMHO.
If you have a choice, I'd recommend an HP MSA2040 SAS unit if you only plan to connect to one server. It's a simpler and more effective connection option. Otherwise, this is probably the wrong product for you.
Please read the HP StorageWorks MSA 2040 QuickSpecs guide here.
If you wish to use fiber channel, you have two options: 8Gb and 16Gb SFPs. The MSA ...
This kind of setup model is called hyper-convergence when compute and storage are running on the same hosts.
From my experience, I have never meet FC HBA that could run replication between 2 directly connected hosts. Check specifics of your FC, could it proceed with EoFC. If so, FC could be used for configuration of iSCSI shared storage between nodes since ...
So you have a single FC LUN presented to both a physical machine and to a VM and you want to use ext3 - is that right?
If so then you need to learn about the difference between block-level and file-level sharing - and quickly, as you've irretrievably corrupted this LUN already.
You have two machines (whether they're physicals or VMs is irrelevant) that ...
Ok, I guess I need to post an answer. In one word it is: insist.
The problem is not resolved 100% to my liking, as we still have one fabric with 1 (one) CRC error sporadically. The other one is clean. But I can live with that.
In any case we won't continue to use the CWDM units for a very long time, but rather switch to a passive DWDM multiplexer next year ...
At the beginning host knows WWNN and WWPN.
Well, forget WWNN. WWNN, theoretically, should be the same on all ports of all HBAs of a computer, but this is rarely the case. Usually it is the same on one HBA, but I've seen a case of multiport HBA with multiple WWNNs. So it's a bit of a mess.
Upon logging to fabric (FLOGI/PLOGI), host gets to know its P_ID ...
Yes, it's very possible - I even did it once, only once however - it's all documented in RFC 4171 and most if not all HBA manufacturers support it, though obviously not as well as they do 'normal' FC.
By the way I did it with Emulex 1105's on RHEL 5.3x64 and Cisco MDS9509's if that helps.
Would this be an acceptable production solution?
No. It would not. You do say that you'd like to "experiment with iSCSI." It is fine for experimentation.
I would be using the server like a ISCSI gateway. But I wouldn't want to use Window's horrendous storage pools\RAID solution I would just want to pass clients straight through to the LUNs I served up to ...
if all 4 are next to each other, would it then be possible to Fibre
Channel cascade them and have a RAID 6 across the nodes?
No, they're not disk shelves, they're full servers with their own CPUs, memory, DAS disks - it's the software that clusters them into pairs for resilience - so no you can't just FC-connect them all together. Oh and 'multiplex' isn't ...
Can we directly connect the SAN to the server HBA and skip on the
Yes, no problem here.
Will we still be able to use vMotion and High Availability using
direct connections from all servers?
What you'll be losing out on, though, is the ability to leverage multiple fibre paths from your HBAs to your SAN, meaning that if your HBAs fail, ...
Further to my comment, I think you're right about them being overlapping terms - mis-used in various ways.
You can download the actual IEEE 802.3-2012 standard here... it's interesting reading if you're in the right frame of mind.
The relevant part of the standard is Section 5, Clause 58, which starts with:
The 100BASE-LX10 and 100BASE-...
when I go to Network Connections, I can't see the adapters
Hahaha, are you trolling us? it's not a network adapter!
Seriously, it's an FC HBA, you need to install the HBA drivers and MPIO, connect it to an FC switch, zone the HBA into a VSAN that's linked to an FC array of some form that's also presenting LUNs to the pWWN of that HBA and then once that's ...
Q1: Does iSCSI forward SMART information? Can Stablebit Drive Scanner work with them as though they were localally installed drives. What is the simplest free (GPL/Open Source etc) OS / Software to use to achieve this? I won't consider a propriatory OS unless Windows Server 2019 is a good solution.
A1: There are commercial iSCSI targets forwarding all the ...
What version of ESXi hypervisor do you have installed? The following procedure is for ESXi 5.x and it is performed from GUI with vSphere client 5.x.
I would shutdown all the virtual machines on that datastore as you wrote, then I would remove/unregister all the machines from the inventory and finally I would unmount it which ensures that there is no active ...
Would this be an acceptable production solution?
Well that would work but I wouldn't say it was production because the latencies are going to be awful and there's no resilience - so for a lab it'd be fine but I wouldn't say it was even remotely production spec.
So, can we (safely) mount a NTFS volume on two servers?
Not unless you're using Windows Failover Clustering with applications that support it. What you're seeing is expected when you present the same NTFS to two non-clustered servers.
That picture is of an LC port. As TheCleaner said, the vast majority of fibre storage will be LC/LC, which means you want to get LC/LC cables and ensure than any servers you plug in use LC HBAs (interface card). You probably can't find 2Gb HBAs these days, but a 4Gb or 8Gb HBA will be able to negotiate down to 2Gb. A 16Gb HBA won't.
You can direct connect a ...
ad 1) There are different kinds of storage solutions on the market - you would need to take care what you're buying:
JBOD enclosures with passive backplanes - you will find some of these for SAS. They just provide cut-through connections for multi-lane links and do not have any logics or any kind of management
JBODs with (SAS or FC) expanders - these are ...
My solution was a bit more complicated. I was able establish a JBOD on my NetApp DS14MK4 (14 x 450GB) using an HP Qlogic QLE2462 HBA on an Ubuntu 16.10 box using the following commands (some settings will be different based on your hard drive type and sizes, so adjust accordingly):
Enable Qlogic HBA BIOS using on system boot-up (Disabled by default)