EMC NS-120 Single Blade Initial Setup – part 2
So after completing the racking and cabling next comes the initialization and configuration of the NS-120. The Celerra Registration Setup (CSA) needs to be run from a workstation on the same VLAN/subnet, this will allow you to configure the IP address, passwords and licensing details of the Control Station and Storage Processors of the backend CX.
The default password for the ‘root’ and ‘nasadmin’ are ‘nasadmin’, but this can be changed during the initialization. I found that these accounts are both present on the Celerra but only the ‘nasadmin’ is configured on the CX by the initialization wizard.
The Unisphere and CX registration tools cannot be used as the CX is connected to the LAN via bridging on the Celerra’s network interfaces. Once the Celerra is initialized you should register it and the CX using the supplied Celerra RegWiz utility.
Once initialized you can connect to the Celerra and/or the CX, via Unisphere using the IP address you specified. The NS120 came configured from the factory with the first five disks in a RAID group and the sixth disk as a hot spare. There are also 8 Lun’s all presented to the Celerra blade as follows.
This includes two 919 GB unused LUN’s (Celerra-16_d7 and Celerra-17_d8) that could be used for file storage like CIFS or NFS. These two Lun’s can be safely removed and the free space, approx 1.8 GB (this system had 600gb FC drives so it may differ depending on the size on the disks) can be used for block (FC) if you wish. These LUN’s should not be used to high I/O workloads.
The other LUN’s are where the Dart and Flare OS’s for the storage system itself exist. Here is the volumes that are created by default, again you can see d7 and d8 which can be removed if you are using block.
This NS120 is the FC model, it has four FC ports per Storage Processor and is only licensed for CIFS. I will be deleting the d7, d8 LUN’s andcreating a smaller LUN that will be used for CIFS from the Celerra. The rest of the Storage will be carved up and presented as block from the CX4 directly to VMware and Windows hosts.