08-19-2011 05:23 AM
I'm looking for some advice/tips/experience regarding attaching appliance devices to SAN. By appliances, I'm talking about devices with non-standard operating systems that you might not necessarily find in an interoperability matrix for a particular storage array.
For years, myself and my colleagues have opposed putting these appliances onto our SAN. This is mainly due to the fact that we have no insight or control over the operating system of the appliance, so we generally can't validate the device against an interop matrix. The worry being that the device could misbehave on the SAN and we might not be able to do anything about it.
That said, there seems to be a number of devices coming out and the pressure is on my team to come up with a good reason why we should continue the way we do -- no appliances on the SAN, they get their own special dedicated environment -- or whether we should reverse our stance and allow appliances on our SAN and storage.
Does anyone have any arguments/advice/experience they can offer?
For background, my company uses Brocade FOS switches and IBM SVC/DS8000 storage.
Thanks in advance,
08-20-2011 02:53 AM
first off, IBM does offer compatibility matrix for SAN Volume Controller family, please refer to the link below:
Being an in-band virtualization appliance, SVC also has very strict and detailed guidelines for cabling and zoning. These can be found in the SVC Information Center online:
If no specific instructions are given, industry standard single-initiatior or point-to-point zoning should apply.
General precautions should be taken as well, such as pilot/proof-of-concept setup, scheduled maintenance window, connecting one fabric at a time with warmup/cooldown periods, and so on.
Hope this helps,