MDC

mi5key's picture

Mac clients flooding Quantum MDCs with requests on startup.

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.

Thanks

MDC locking up. XSAN 3.1 OSX 10.9.4, MDC Mac Mini

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.

Any thoughts?

kworq's picture

Open Directory Replica on a MDC - Incorrect Search Policy

Forums: 

Im having an issue I hope someone can enlighten me on. 

I have an xsan environment with 2 metadata controllers. MDC1 is just a the master controller. MDC 2 is also a AFP re-share and is an open directory master. 

All clients and MDC’s are bound to MDC2 open directory master. 

When MDC2 needs to be rebooted all clients loose ACL’s to the xsan because the OD is offline. 

I made the MDC1 an open directory replica and that functions as expected. Unfortunately now in xsan admin MDC1 now says “Incorrect Search Policy”  because it is now bond to itself and not MDC2. 

How can I have both? Can a MDC not be a OD Replica?

Subscribe to RSS - MDC