This discussion is locked
borquee
Level 1 (4 points)
Servers Enterprise

Q: how to setup xsan with two controllers

Hi,

Here is the situation:

-Server 1 (adress book, ichat, mail and profile manager, dynamic host name, the works) should be secondary xsan controler for metadata

-Server 2 just xsan primary controler

 

I managed to setup Xsan on Server2 only when server1 is shutdown

If I turn ON Server1 Xsan goes down, shutdown Server1 all is nice again.

 

There are no IP conflicts, they are on a separate networks, they can ping each other fine...

 

As an earlier test setup I ran everything from Server1 (mail, chat, calendars and Xsan) and I could not authenticate Server2 either as a client or controler

Looked like Xsan went down as soon as I booted Server2

 

Any ideas?

 

Is there anything I should do when I introduce second server into network? Also I could see both servers from the client, looks like they don't tollerate each other

 

I would like to note that this is a test setup and I can wipe it clean if necesary ...


Thanks,

B.

xsan, Mac OS X (10.7.2)

Posted on Nov 19, 2011 1:59 PM

Close
borquee

Q: how to setup xsan with two controllers

  • All replies
  • Helpful answers

  • by receng,

    receng receng Nov 22, 2011 8:04 AM in response to borquee
    Level 1 (20 points)
    Nov 22, 2011 8:04 AM in response to borquee

    It looks to me like Server 2 is taking over the Volume when it is booted. When two servers think they are the primary controller at the same time the Xsan will go down.

    I would try uninstalling the XSAN from Server 2 first  and installing it back - make sure you got the serial number (or re-imaging it completely if you get problems with the following steps).

    Then, add it as a client first. If that works, add it as a controller with a lower priority.

    If that works, fail over the volume to Server 2 and bump up the controlller priority for Server 2 and bring the Server 1 priority down.

     

    If we are talinkg about Mac OS X Lion than you can't uninstall, just re-image.

     

    I am assuming that DNS and networking are correctly set up and that the servers can see all the LUNS.

  • by borquee,

    borquee borquee Nov 22, 2011 8:11 AM in response to receng
    Level 1 (4 points)
    Servers Enterprise
    Nov 22, 2011 8:11 AM in response to receng

    Hi

    They two Lion servers. Problem was resolved by joining server2 to server1's active directory (users->join)

     

    There is still this problem that I don't know how to make controller priority (options grayed out)

     

    Just few minutes ago I get the message like this "Volume Post2 in SAN xxxxxx has failed over.  It is now being hosted by yyyyy.lan."

  • by receng,

    receng receng Nov 30, 2011 10:59 AM in response to borquee
    Level 1 (20 points)
    Nov 30, 2011 10:59 AM in response to borquee

    The message means the volume has failed over. For some reason your primary mdc server stopped hosting the volume - I would look at the logs.

    Make sure you don't open XSAN admin in more than one machine and that you can see all servers and clients in XSAN admin.

     

    I am note sure why the controller priority would be grayed out.

    This is from the Xsan manual:

    Set a metadata controller’s failover priority:

     

    1. 1  Open Xsan Admin, select Volumes in the SAN Assets list, and select a volume in the list.
    2. 2  Choose Edit Failover Priority from the Action pop-up menu (gear).
    3. 3  Drag metadata controllers up or down in the list that appears.

      The closer a metadata controller is to the top of the list, the more likely it is that it willhost the volume.

    4. 4  Click OK.

     

    I would try failing back all volumes to your MDC1 and making the other server (MDC2) a client and then back to controller. This refreshes the configuration files.