Set Up EMC NAS into your Windows Domain

This is post is covering the implementation of EMC NAS Appliance within Windows Domain.

At first, I had to set some sort of Prototype and become a little familiar with the NAS itself. I have tried to make as simpliest as possible the steps, this is quiet long howto. However at the end of this post, another one will follow to implement an Antivirus with this NAS. Hope that you will eventually help anyone at some stage. Three machines as a minimum are needed:

  • 1. Domain controller (using Windows 2003) chosen 2003 rather than 2008 as a matter of resources consumption.
  • 2. The EMC Celerra Simulator, unfortunately the only available version was 5.6
  • 3. Windows 2003 running an Antivirus. I have chosen Symantec Scan Engine (v5.2.x).

I have been using some EMC Documentation, the doc 300.003.555 pdf file for the implementation and steps for the EMC NAS simulator. Let get started then. Assuming that you already have the Domain controller up and running. We then start the EMC Simulator. Once the machine is fully started. The following prompt is seen:

 

The default credential is root and nasadmin as password. – log as root user and set the network running this command: Check which network interface available, run: ifconfig –a | more in my situation, I do have a DHCP on that same segment, however I will assign a static IP for the NAS.

 

Setup the Network card IP / Netmask and Gateway running the command: netconfig –d eth0

 

 

 

Run the command to stop the interface eth0: Ifdown eth0 and to start it again applying your IP entered run : ifup eth0 and finally ifconfig eth0 to verify the current network details:

 

Accessing to the Celerra Manager, the eth2 needs to be set also. Follow the same instruction as mentioned above, of course replace eth0 interface with eth0. Note that both network card can be on the same network. Ex:

 

 

 

Applying the change running ifup eth2, I will from now be able to connect into the Celerra Manager interface. (Note: Java is needed on the remote machine to connect to it.)

Ex:

 

 

 

 

 

 

 

 

Once logged, enable the license to enable the feature that you might use/need; As the NAS will not be available unless you enable CIFS and NFS. (one by one.) Select Tabulation Licenses.

Info : Each virtual Data Mover has 750 MB of memory for processing requests. The simulator comes enabled with 25 GB of virtual storage at installation time. This comes in the form of two storage pools, one 20 GB and one 5 GB.   Now, the next step is to next the wizard from the Celerra Manager: https://IP

You will need to logout, and log in with/as root account and not as nasadmin. Credential : root/nasadmin

 

 

 

 

 

 

Expand the menu, select Wizards and then click on Set Up Celerra button. New window will appear, as follow:

  • Set the Host Name, change localhost with the Hostname that wish the EMC NAS to have. Once you click on NEXT another window appears stating that changing the hostname will require to issue a new SSL certificate and the wizard will stop.

Press OK button to continue.

The wizard will remains, keep going the wizard as follow:

  • Set the DNS Domain Name and change if needed the DNS IP address to match your internal DNS and click on NEXT

  • If you do have multiple Domains, enter the domain order that the NAS will search. (Even if only one domain in) and click on NEXT

  • NTP server, as part of a domain, the NAS also need to be sync with the DC. Add your DC IP address and click on NEXT

  • Set the Time Zone. Then NEXT
  • Select the System Licenses and click on NEXT

  • Click on NEXT and Submit to apply the changes.

Changing the Time Zone will prompt you stating that EMC NAS require a reboot.

Reboot through SSH with the root credential, by typing reboot.

Once the EMC NAS has finally restarted. Now you should have noticed the Hostname has changed from the Console window:

Re-connect through the EMC Manager as previously (https://IP of eth2)

And log as root again. Get back to the wizard menu; select again the Set Up Celerra. Most of the information is already filled in as we go through earlier before the restart.

Click on NEXT to follow up each step as previously passed, and submit even if no changes are made.

You can eventually go through and click on the CIFS server instead, however I do prefer to use this screen to make sure that we would not bypass any of these steps.

/strongp

Leave a Reply

Your email address will not be published. Required fields are marked *