OCI and EMC Symmetrix 101.
OCI wants to discover EMC Symmetrix arrays by parsing XML formatted Symcli (Solutions Enabler CLI) output.
How does it get that data:
#1. 95% of the time, the OCI server or acquisition unit is acting as a client - Solutions Enabler is a client server program. In this mode you need:
The OCI server to be running the same, or older version of Solutions Enabler as the server you are talking to
The storsrvd daemon needs to be installed and running on the Solutions Enabler server you are talking to (please make your customer install this daemon, and set to run autostart so when they reboot their SE server, OCI doesn't have inventory fail because the storsvrd daemon is no longer running)
#2. 5% of the time customers provision FC gatekeeper volumes to OCI, or run an OCI Remote Acquisition Unit (RAU) on an Solutions Enabler host (with direct FC connectivity to arrays) - in this config, we choose "local" under "Connection Caching" in the datasource, as we are running commands directly against the array. I have been working with a customer this week that does almost all their Symmetrix discovery this way - they are building 8GB VMs with RDM gatekeepers. They have the SMI-S enabled version of Solutions Enabler installed, and we use symcli for inventory, and SMI-S for performance gathering. It is also worth mentioning in this config, the OCI datasource still needs to have the "service name" attribute populated, but its contents are irrelevant, as the netcnfg alias file is not used for local communication.
So, lets continue with #1, the client server model.
We established you need Solutions Enabler installed. You also need to edit your netcnfg file , in ..\emc\symapi\config
This defines aliases, which is the first field on the Inventory page in your OCI datasource creation.
Your OCI datasource also needs the right path to the symcli binaries set. Finally, the default connection caching setting, REMOTE_CACHED, should work fine
What can go wrong?
The storsvrd daemon is not running on the host we defined in our netcnfg alias - to troubleshoot from OCI, open your netcnfg file, extract the IP address or FQDN of the SE host, and try:
telnet NNNNN 2707 , where NNNNN is the IP/FQDN
Assuming telnet is installed - if this times out, there is nothing listening on tcp 2707, or there is a firewall. If you get a blinking cursor, the daemon is up.
Once you know the status of the daemon, you either work on getting the daemon running (and please work on getting installed autostart ), or troubleshooting your problem..
Troubleshooting is probably another post. There are 2 threads for it:
Cracking open recordings, and reading them
Setting environment variables manually, and running commands manually. This approach has been degraded somewhat in value due to some Symmetrix security configurations that mean your output (run as you) may vary from what OCI (running as hostname\SYSTEM) will see