The Storio PowerShell toolkit relies on the EMC Solutions Enabler SMI Provider to carry out array management commands. To diagnose a problem related to the SMI Provider, we will need to get the log files with extra diagnostic information (verbose logging). This article describes how to enable verbose logging and gather up the resulting log files. Note these instructions are for Windows builds of the SMI Provider.
Enable Verbose Logging
To enable verbose logging for the SMI Provider, follow these steps on the server where it is installed:
Stop the ECOM service (this is the service that hosts the SMI Provider). You can do this from the command line by running net stop ecom.
Open the ECOM log configuration file in a text editor. Navigate to the <Program Files>\EMC\ECIM\ECOM\conf folder and open the Log_settings.xml file. I suggest that you make a backup of this file to make it easier to restore the original settings when you're done.
In the config file find the setting named Severity and set its value to NAVI_TRACE:
Save the config file and restart the ECOM service. You can do this from the command line by running net start ecom.
After the ECOM service has started, wait a minute or so while it finishes initializing. Otherwise you may get "(503) Server Unavailable" errors when invoking the PowerShell commands. Then re-run the scenario that causes the problem.
Gather ECOM Logs
The verbose log files for ECOM and the SMI Provider will be in the folder <Program Files>\EMC\ECIM\ECOM\log. Zip up the contents of this folder and send it along to us with a description of the steps you took to reproduce the problem.
Gather SYMAPI Logs
We may also ask you for another set of logs, located in <Program Files>\EMC\SYMAPI\log. These logs are for the underlying API (called SYMAPI) used by the SMI Provider. In fact it may save some time if you send us both ECOM and SYMAPI logs up front, in case we need both.