| View previous topic :: View next topic |
| Author |
Message |
jbucks partially protected

Joined: 16 Oct 2009 Posts: 5
|
Posted: Fri Oct 16, 2009 3:51 pm Post subject: Is there a way to enter Xsan 1.4.2 client licenses |
|
|
Hello All,
First time poster. I've done several searches for this info, but have been unable to find a solution.
I would like to be able to add / install (reloaded computer) one of our Xsan 1.4.2 client license keys via command line / edit a file. Is there a way to do this? If so, how?
thanks,
Jim |
|
| Back to top |
|
 |
matx Xsan Master

Joined: 15 Apr 2005 Posts: 378
|
Posted: Fri Oct 16, 2009 4:25 pm Post subject: |
|
|
In Xsan 1.x the SN is kept in a text file on each client. To verify:
cd /Library/Filesystems/Xsan/config/
more role.plist |
|
| Back to top |
|
 |
jbucks partially protected

Joined: 16 Oct 2009 Posts: 5
|
Posted: Fri Oct 16, 2009 4:36 pm Post subject: Many thanks! |
|
|
| Many thanks! |
|
| Back to top |
|
 |
jbucks partially protected

Joined: 16 Oct 2009 Posts: 5
|
Posted: Mon Oct 19, 2009 11:25 am Post subject: |
|
|
Sadly, this did not work out (but I really wanted it to)....
I'm getting License authorization failure messages. And, yes, I've checked the license key for accuracy.
I changed two lines in the role.plist file:
- The interfaceIP string value
- the license string value
I left all the other files alone (and copied them from one of my other working clients).
Any ideas on what I might have done wrong?
Jim |
|
| Back to top |
|
 |
lotte Xsan Master

Joined: 11 Dec 2008 Posts: 190
|
Posted: Wed Oct 21, 2009 4:15 am Post subject: |
|
|
As far as I remember there is no other way than installing xsan admin (1.4.2) on the client, propagate the serial number and save this locally, then edit the necessary config files (fsnameservers, automount.plist) and you should be fine.
Maybe by doing this once you may find out where else the changes are commited on the client and then edit this manually. Remember there is also a file called xsan in /etc/systemserialnumbers which contains the license information...
Lotte |
|
| Back to top |
|
 |
jbucks partially protected

Joined: 16 Oct 2009 Posts: 5
|
Posted: Wed Oct 21, 2009 8:50 am Post subject: |
|
|
Thank you both!
A combination of both your clues appears to have worked out for me. I'll post a checklist for this later (in case anyone else needs it at some future date).
Jim |
|
| Back to top |
|
 |
jbucks partially protected

Joined: 16 Oct 2009 Posts: 5
|
Posted: Wed Oct 21, 2009 9:25 am Post subject: Here's my checklist for manually installing an Xsan Client |
|
|
It looks like the Xsan Client licenses are located two locations
(on each individual workstation).
/Library/Filesystems/Xsan/config/
drwxrwxr-x 8 root admin 272 Oct 19 09:24 config
Here are the file's ownership's and permissions:
-rw------- 1 root admin 64 Dec 2 2008 .auth_secret
-rw-r--r-- 1 root admin 420 Mar 18 2009 automount.plist
-rw-r--r--@ 1 root admin 30 Sep 4 03:02 fsnameservers
-rw-r--r-- 1 root admin 814 Sep 4 04:41 notifications.plist
-rw-r----- 1 root admin 505 Sep 4 04:41 role.plist
-rw-r--r-- 1 root admin 229 Sep 4 04:41 saninfo.plist
After installing the xsan client software (1.4.2), copy all the files
in the "config" directory from one of the other working clients.
Change two lines in the role.plist file:
- The interfaceIP string value (so it matches the IP for this workstation)
- the license string value (so it's the unique Xsan client
license number for this workstation)
Here is what the file looks like after being modified:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>failoverPriority</key>
<integer>0</integer>
<key>interfaceIP</key>
<string>999.999.999.999</string>
<key>interfaceName</key>
<string>en0</string>
<key>license</key>
<string>xsan-014-000-0-000-000-000-000-000-000-0</string>
<key>role</key>
<string>CLIENT</string>
<key>watermark</key>
<string></string>
</dict>
</plist>
The license info is also stored in /etc/systemserialnumbers/xsan file.
You may have to manually create the systemserialnumbers directory,
if it does not already exist.
drwx------ 3 root wheel 102 Oct 21 07:37 systemserialnumbers
-rwx------ 1 root _serialnumberd 41 Oct 21 07:37 xsan
There is only a single line in this file - the xsan client serial
number (NOT case sensitive, left justified).
xsan-014-000-0-000-000-000-000-000-000-0
When done, reboot the workstation. Make sure the Xsan volume(s) appear on the workstation's desktop. Run the cvadmin's "who" command to make sure the volumes are being properly set up & presented to the workstation.
Hope this helps the next person to run into this problem.
Jim |
|
| Back to top |
|
 |
|