You can use the UUID of a SAN MDC in Xsan to perform a lot of tasks. To locate the UUID of a SAN MDC in Xsan: sudo serveradmin settings san:UUID The output is just the GUID of the san client UUID. Now you know.
-
-
Set Up The VPN Server and Client on Yosemite Server
OS X Server has long had a VPN service that can be run. The server is capable of running the two most commonly used VPN protocols: PPTP and L2TP. The L2TP protocol is always in use, but the server can run both concurrently. You should use L2TP when at all possible. Sure, “All the great themes have been used up and turned into theme parks.” But security is a theme that it never hurts to keep in the forefront of your mind. If you were thinking of exposing the other services in Yosemite Server to the Internet without having users connect to a VPN service then you should think again,…
-
Xsan: Ghost SymLink Killah
An Xsan issue that had disappeared for awhile but that I’ve seen a few times recently. Symptom is that you have one client that won’t mount your Xsan volume. Other clients can mount but not that one. In the logs you see errors similar to the following: (Error) Store: {channel:0x202b18fa0 localPath:’/Volumes/36Chambers’} bring up failed — will retry If all of these things are true then you likely, even without having the volume mounted will have a file in the /Volumes/ folder with the name of the SAN. If that’s the case then you have a pretty quick and easy resolution. Rename the file and see if fsm mounts the volume.…