Mismatched MDC's

[pablogott]

I was doing some basic maintenance/software updates so I failed over the volumes to the secondary MDC, updated and rebooted the primary, failed back over to the primary, rebooted the secondary MDC and when everything came back on something had gone wrong.

In Xsan admin (2.3/Lion Server) the list of computers no longer match up and it wouldn't let me fail back to the secondary MDC.

I could do the failovers fine from cvadmin.

I would like to remove the secondary MDC and add it back in for a fresh start. It doesn't show up in the primary MDC's xsan admin, so I don't know how else to force remove and add back in a controller that the configuration thinks is still there.

Also all the client computers are reporting "fsnameservers are incorrect"

So my question is, how can I cleanly remove a secondary MDC and add it back in without access from xsan admin?

And the real question is, how can I get my config healthy again?

[pablogott]

Managed to get the controller out and back in again.

Now my concern is config files don't match on all the client computers. Is there a good way to fix it besides removing everyone and adding them back in?

Also, my secondary MDC won't connect to the right xsan admin. It'll connect, but only show itself in the computer list. How can I get my xsan admin healthy again?