I wanted to add my VSA Celerra to my domain to play around with moving our production data movers to virtual data movers.  Granted, I did not want to attempt this on our production unit, and luckily I figured out a way to get this working.

Tools Required:

1. Patience!
2. At least 2 free IP addresses.
3. A vSphere Server with 8GB Ram and 2 CPU’s.
4. Uber-Celerra

1. Once you’ve downloaded and extracted the zip file the first thing to do is compare the md5 hash to make sure it matches up.
2. After that has been completed fire up your vSphere client and click on File –> DEPLOY OVF Template.
3. Now, go into your new shiny virtual appliance and configure it with at least 2 vCPU’s at 8 GB of memory… You can optionally add another NIC or two if you’d like.  I have 4 NIC’s running in my test.
4. Power it on after it has been reconfigured.
5. Assign it either 1 or 2 data movers, give it an ip address, subnet mask, and gateway.  Confirm your selections by hitting Y.
6. Now give it a DNS server and NTP server. 
7. It takes about 5-10 minutes for it to configure itself.  Once completed you should be presented with the following screen:
9. 
10. Crack open your brower and go to the IP address you specified.  In my case I’m using 10.88.24.240.
11. Once prompted for a login, type in nasadmin/nasadmin.

TWO DATA MOVER SETUP:

1. Go to your url for unisphere http://yoururlhere.com
2. Login via nasadmin/nasadmin
3. Click on System –> Network
4. Click on Create
5. Add any other network interfaces you need.   I like to follow the convention of eth0-last three ip octets.  For example if your IP is 192.168.1.200 then your eth interface would represent: eth0-200
6. 
7. Click on System –> Data Movers
8. Right Click server_2 –> Properties
9. Check the box Enable Unicode
10. Verify your timezone, NTP Server, and if you want your standby Mover i.e. server_3 or not.  It depends really if you want an active/active or active/passive connection.
11. Click on Apply and give it a good 5-10 minutes for it to reconfigure the DM and reboot the control station.
12. Once that has completed let’s verify we have all of our licenses.  Click on System –> System Information –> Manage Licenses.  They should all be checked, if not check the boxes and click on OK.

File Systems:

If you want to create a file system here is the procedure..

1. Click on Storage –> File Systems. 
2. Click on Create
3. Give your file system a name such as:  TestFS
4. Select the Storage Pool you would like to use.  Either Economy or Performance.
5. Enable any other features you would like such as Deduplication..
6. Click on Apply.

CIFS:

If you would like to create a CIFS server/share here’s what cha do…

1. Click on Sharing –> CIFS
2. On the left panel side click on Configure CIFS, then enable the checkbox for CIFS Service Started and click on OK.
3. 
4. Now that the CIFS Server is running on your DM server_2 you are ready to configure a CIFS Server.
5. On the left hand pane click on Create CIFS Server:
6. Server Type:  Windows 2000, Windows 2003 and Windows 2008.
7. NetBIOS Name: TestServer
8. Workgroup: WORKGROUP (leave it this for now unless you want to join the domain).
9. If leaving it on the WORKGROUP enable the checkbox Enable Local Users and set a password that you are going to remember.  I like to keep it simple and use password.
10. Interface:  Select your Interface that you set-up in the prior steps.
11. Click on OK.
    
12. Now it’s time to create a CIFS Share
13. Click on Create Share from the left hand pane under CIFS
14. 
15. Create a new CIFS Share with the following options:
16. Select your Data Mover: server_2
17. CIFS Share Name: TestShare
18. Check the box CIFS Servers: TestServer
19. Path: \TestFS
20. Click on OK.

Now you have created a CIFS Server, if you created a WORKSTATION only CIFS share than there’s just a couple of more steps to do. 

WORKSTATION CIFS SHARE

1. On to your desktop and hit CTRL-ALT-DELETE
2. Click on Change A Password… and input the following:
3. Username: administrator
4. Log on to: TestServer (if it fails make sure it resolves in DNS, if not add a record)
5. Old Password: (the password you set in the CIFS server step, i.e. password)
6. New Password: password123
7. Click on Change.  If everything works out right it will be successful and you can continue moving forward…  If not, try pinging testserver and see if it resolves, if it does try changing the password following the steps above from a different computer.

DOMAIN CIFS SHARE

If you tried to join the CIFS Server to the domain above and ran into complications with it complaining about:

Join failed. System was unable to join or has already joined the CIFS server to the domain. Go to the server log for more detail.

Then it is safe to say maybe your clock might be skewed… Let’s double check and see what’s going on…..

1. Open Putty
2. Type in your ip address of your control station
3. login via nasadmin/nasadmin
4. input:  date it should return something that resembles

   Wed Dec 29 07:55:28 PST 2010

5. Let’s check the DM to see if the control station and the DM match times type in: server_date server_2.  It should yield:

   server_2 : Wed Dec 29 07:56:21 PST 2010

6. If it is within 1 minute of the control station you should be able to add it to the domain.  If you are still getting an error type in:
7. server_date server_2 timesvc

   server_2 :

   Timeservice State

   time:            Wed Dec 29 07:57:40 PST 2010
   type:            ntp
   sync delay:     off
   interval:       60
   hosts:           192.168.1.1,

8. If there is not a hosts field then go back to your unisphere –> System –> Data Movers –> server_2 (right click – properties) and ensure you have your NTP Servers field filled out correctly.  It is also important to make sure both your CS and DM are in the same timezone.  If they are not you can change them by issuing the command:
9. server_date server_2 timezone
   
10. For a more detailed breakdown on why your NTP might be failing type in:   server_date server_2 timesvc stats ntp

    server_2 :
    Time synchronization statistics since start:
    hits= 18, misses= 0, first poll hit= 1, miss= 0
    Last offset: 0 secs, 0 usecs
    Current State: Running, connected, interval= 60
    Time sync hosts:
    192.168.1.1,

11. If there is an error it should indicate it here with the misses.
12. If all else fails and you cannot get NTP going to save a small hampster, than you can resynchronize the time service on the CIFS server client using the CS as the time server by issuing the following commands:
13. If Control Station Time Server service is out of synchronization, reset the Time to that of the Kerberos Time Service [or other Network Time Service   Server]: 
    #date  -s  "04/08/02 16:00:00"
14. If the CIFS Server is synchronizing to the Control Station [or any other external Time Source], you would resync the CIFS Server using the  following commands:  
    $server_date  server_2  timesvc  stop
    $server_date  server_2  timesvc  start
15. Now that you’ve hopefully managed to finagle a way to get your time to resemble that of the real world it’s time to add your CIFS Server to the domain.  I like to do it via command prompt so if there are any errors it will let me know…  The syntax is as follows:
16. server_cifs server_2 -J compname=TESTSERVER,domain=yourdomainhere,admin=domain_admin,ou="ou=Computers:ou=EMC Celerra"
17. This is under the assumption that your EMC devices are in the standard hierarchy in your AD OU’s…

Enjoy!