HOW TO: Add/Discover Vblock in EMC UIM/P

In previous post we installed and configured UIM/P. We can now add and discover a Vblock.

1. Login to UIM/P as sysadmin;
2. Navigate to Administration, Vblocks, Add Vblock;
3. Select Vblock version, fill in IP addesses, user names and passwords and click Add and Discover;
4. If discovery fails, check user names and passwords. Confirm they work by manually  connecting to the equipment;
5. There are two other reasons the discovery may fail:
   1. Cannot discover UCS – make sure you imported UCS Manager certificate. See ‘Install and configure EMC UIM/P, Step 8, Install UCS Manager certificate‘
   2. Cannot discover VNX – There are two services, SMI-S and ECOM, must be enabled and running on VNX for UIM/P to successfully discover it. They are disabled by default and also get disabled during VNX software upgrade. Please refer to Primus emc287203 “What is SMI-S and ECOM and how to start the ECOM service on the Celerra/VNX Control Station“, also see below. You should contact EMC support to get these services enabled or you can do it yourself by following these instructions.
6. Validate Vblock setup: Administration, highlight Vblock, click Validate Setup. Make sure Setup Validation Status is Ready or Warning;
   
7. Configure Identity Pools: Administration – Identity Pools. For all pools configure Name, Range and Tag (Global)
   1. UUID Pool
   2. MAC Pool
   3. WWNN Pool
   4. WWPN Pool
8. Configure Blade and Storage Grades:
   1. Administration – Blade Pool – Manage Grades
   2. Administration – Storage Pool – Manage Grades
9. Add vCenter Server: Administration – vCenter Instances. Click Add, fill in the vCenter details and click OK. Verify connection to vCenter by clicking on Enable Connection.

You are now ready to run EMC Service Adoption Utility to import your Vblock configuration into UIM/P.

Stay tuned…

EMC Primus emc287203:

“What is SMI-S and ECOM and how to start the ECOM service on the Celerra/VNX Control Station”

Knowledgebase Solution

How to enable SMI-S and ECOM service:

1. Connect to Primary Control Station as nasadmin;
2. Edit /nas/sys/nas_mcd.cfg configuration file

   [nasadmin@VNX001A ~]$ cd /nas/sys
   [nasadmin@VNX001A sys]$ vi nas_mcd.cfg
   _

3. Uncomment all lines for each of the following services and save the nas_mcd.cfg file:
   1. daemon “cim server“;
   2. daemon “cim conf“;
   3. daemon “SMISPlugin Log Trimmer“;
   4. daemon “SMIS securitylog.txt Log Trimmer“;
   5. daemon “SMIS HTTP_trace.log Log Trimmer“;
   6. daemon “SMIS cimomlog.txt Log Trimmer“

    daemon  "cim server"
   executable      "/celerra/wbem/bin/start_cim_server"
   optional        no
   autorestart     yes
   cmdline         "/celerra/wbem"
   
   daemon "cim conf"
   executable      "/nas/sbin/dirsync"
   optional        no
   autorestart     yes
   cmdline         "-all /celerra/wbem/conf/ /nas/site/ecom_config  360"
   
   daemon "SMISPlugin Log Trimmer"
   executable      "/nas/sbin/log_trimmer"
   optional        no
   autorestart     yes
   ioaccess        no
   cmdline         "-n /nas/log/smis/SMISPlugin.log 1000 l 2 h t 4 y "
   
   daemon "SMIS securitylog.txt Log Trimmer"
   executable      "/nas/sbin/log_trimmer"
   optional        no
   autorestart     yes
   ioaccess        no
   cmdline         "-n /nas/log/smis/securitylog.txt 1000 l 2 h t 4 y "
   
   daemon "SMIS HTTP_trace.log Log Trimmer"
   executable      "/nas/sbin/log_trimmer"
   optional        no
   autorestart     yes
   ioaccess        no
   cmdline         "-n /nas/log/smis/HTTP_trace.log 1000 l 2 h t 4 y "
   
   daemon "SMIS cimomlog.txt Log Trimmer"
   executable      "/nas/sbin/log_trimmer"
   optional        no
   autorestart     yes
   ioaccess        no
   cmdline         "-n /nas/log/smis/cimomlog.txt 1000 l 2 h t 4 y "

4. Restart nas service OR reboot Primary Control Station

   /etc/rc/d/init.d/nas stop / start

   OR

   reboot

5. During reboot NAS services will be failed over to Secondary Control Station, please fail them back when Primary CS come back on

   [nasadmin@VNX001B /]$ /nas/sbin/getreason
   10 - slot_0 secondary control station
   11 - slot_1 primary control station
   5 - slot_2 contacted
   5 - slot_3 contacted
   5 - slot_4 contacted
   5 - slot_5 contacted
   [nasadmin@VNX001B /]$ /nasmcd/sbin/cs_standby -failover yes 

6. Verify if the services are up and running:

   [nasadmin@VNX001A /]$ ps -ef | grep -i ecom
   nasadmin 15451   951  0 13:33 pts/0    00:00:00 grep -i ecom
   root     21851  2967  0 Oct17 ?        00:00:01 /bin/sh /nas/sbin/dirsync -all /celerra/wbem/conf/ /nas/site/ecom_config 360
   root     23241 21850  0 Oct17 ?        00:16:54 ECOM
   [nasadmin@VNX001A /]$ ps -ef | grep -i smis
   nasadmin 15596   951  0 13:33 pts/0    00:00:00 grep -i smis
   root     21855  2967  0 Oct17 ?        00:00:06 /nas/sbin/log_trimmer -n /nas/log/smis/SMISPlugin.log 1000 l 2 h t 4 y
   root     21856  2967  0 Oct17 ?        00:00:00 /nas/sbin/log_trimmer -n /nas/log/smis/securitylog.txt 1000 l 2 h t 4 y
   root     21857  2967  0 Oct17 ?        00:00:00 /nas/sbin/log_trimmer -n /nas/log/smis/HTTP_trace.log 1000 l 2 h t 4 y
   root     21858  2967  0 Oct17 ?        00:00:03 /nas/sbin/log_trimmer -n /nas/log/smis/cimomlog.txt 1000 l 2 h t 4 y
   [nasadmin@VNX001A /]$ ps -ef | grep -i cim
   nasadmin 15845   951  0 13:33 pts/0    00:00:00 grep -i cim
   root     21850  2967  0 Oct17 ?        00:00:00 /bin/sh /celerra/wbem/bin/start_cim_server /celerra/wbem
   root     21858  2967  0 Oct17 ?        00:00:03 /nas/sbin/log_trimmer -n /nas/log/smis/cimomlog.txt 1000 l 2 h t 4 y

7. Verify that Control Station is listening on port 5989:

   [nasadmin@VNX001A /]$ netstat -an | grep 5989
   tcp        0      0 :::5989                     :::*                        LISTEN