Submitted by mi5key on Wed, 11/05/2014 - 5:04pm
We have an assortment of Mac clients that connect to Quantum MDCs (M440/5) for the volumes. When these Macs (running Mavericks) startup , they flood the MDCs with request for their LUNS. Something in the startup of the OS isn't showing the fiber LUNs at that time, so the client asks the MDCs again, and again, and so on. When the LUNs finally do show up on the fiber ports, Xsan connects to the volumes just fine.
Is there a way to delay Xsan startup until the fiber ports have been initialized properly?
We are using ATTO CelerityFC8 fiber cards, and zoned via Brocade DCX switches.
Submitted by awince on Mon, 09/29/2014 - 6:23pm
XSAN configuration went well. System appears to work well for about a week, then MDC1 will usually freeze up. It appears to fail over to MDC2, but XSAN admin and cvadmin still list MDC1 as hosting. This is usually discovered by clients losing access to volume. It requires a hard shutdown of MDC1 and sometimes MDC2 and reboot of storage to get back. The log files are usually lost in the Hard Boot. Once restarted, everything works ok again for about a week then freezes again.