EMC VMAX – SMI-S Configuration & Discovery
The following are some configuration notes for configuring the ‘VMAX Management HOST’ for communication via SMI-S for purposes such as ‘ViPR’ or with ‘VCE Vision’. Before proceeding ensure you have […]
Virtualization & Storage
The following are some configuration notes for configuring the ‘VMAX Management HOST’ for communication via SMI-S for purposes such as ‘ViPR’ or with ‘VCE Vision’. Before proceeding ensure you have […]
The following are some configuration notes for configuring the ‘VMAX Management HOST’ for communication via SMI-S for purposes such as ‘ViPR’ or with ‘VCE Vision’. Before proceeding ensure you have presented and configured the ‘VMAX Management HOST’ with gatekeeper volumes from the VMAX to allow for in-band communication over Fibre Channel. EMC SMI-S provider is included as part of ‘Solutions Enabler with SMIS’ install package which can be downloaded from ‘support.emc.com’.
Begin by installing SMI-S Provider, ensuring you select the ‘Array provider’ (Windows does not require Host provider) and chose the option for SMISPROVIDER_COMPONENT:
From the windows services.msc console check that both the ‘ECOM’ and ‘storsrvd’ services are set to automatic and in a running state:
Check that EMC storsrvd daemon is installed and running from a Windows cmd prompt using stordaemon.exe:
stordaemon install storsrvd -autostart
stordaemon start storsrvd
stordaemon.exe list
Or using the SC (service control) command you can query/start/config the ECOM and storsrvd services:
sc query ECOM.exe
sc query storsrvd
sc start ECOM.exe
sc start storsrvd
sc config ECOM.exe start=auto
sc config storsrvd start=auto
Run netstat -a
and check the host is listening on ports 5988 5989:
UPDATE ENVIRONMENT VARIABLES:
Add the SYMCLI installation directory path (DRIVE:\Program Files\EMC\ECIM\ECOM\BIN) to the list of system paths:
Or use the windows CLI to add the SYMCLI and ECOM directories to the PATH environment variable:
setx /M PATH "%PATH%;C:\Program Files\EMC\SYMCLI\bin;C:\Program Files\EMC\ECIM\ECOM\bin"
Perform a Symcfg Discover
followed by Symcfg List
to ensure communication is present between the VMAX and the VMAX management server.
If experiencing issues such as the ECOM service failing to start it is worth rebooting the mgmt server at this stage.
ECOM SERVER: Adding A NEW SMI-S Provider User
Provided all the validations are successful then proceed to login to the ECOM server and create the user you would like to use for connectivity:
Open https://localhost:5989/ecomconfig
Login with default credentials of: admin / #1Password
Select the option to add a new user and create the Vision user with administrator role and scope local:
Windows Firewall
If the Windows firewall is enabled then rules will need to be created to allow ECOM ports TCP 5988&5989 and SLP port UDP 427. For example using the windows command line netsh
to create rules for SLP and ECOM:
netsh advfirewall firewall add rule name="SLP" dir=in protocol=UDP localport=427 action=allow
netsh advfirewall firewall add rule name=”ECOM” dir=in protocol=TCP localport=5988-5989 action=allow
netsh advfirewall firewall show rule name=SLP
netsh advfirewall firewall show rule name=ECOM
Confirm VMAX Connectivity VIA SMI-S (TestSMIProvider)
Open a Windows cmd prompt session as admin user, if the environment variable has not been set then you will need to ‘cd’ to c:\Program Files\EMC\ECIM\ECOM\BIN. Type TestSMIProvider.exe at the prompt, from here chose all defaults except for the Vision user and password created through the ECOM console:
At the prompt type ‘dv’ (display version info) command to confirm connectivity between the VMAX and SMI-S:
For any troubleshooting please refer to: ‘C:\Program Files\EMC\ECIM\ECOM\log’
Note: When configuring Vision please ensure to use the ‘VMAX Management HOST’ IP address for all VMAX entries in the Vblock.xml configuration file.
Ramblings by Keith Lee
Discussions about all things VxRail.
Random Technology thoughts from an Irish Virtualization Geek (who enjoys saving the world in his spare time).
Musings of a VMware Cloud Geek
Converged and Hyper Converged Infrastructure
'Scamallach' - Gaelic for 'Cloudy' ...
Storing data and be awesome
Best Practices et al
Every Cloud Has a Tin Lining.
Hi David,
this is brilliant info! but I think is only valid untill vmax2 ? Since we have moved to VMAX3 which is mostly manged by emgt, symcli works by redirecting the commands to emgmt. is there a way also to use SMIS to redicret on egmt ?
Hi Vivek thanks for the feedback. External smis may also be used with VMAX3.