Insight Dynamics 6.1 Release Notes

Using a remote CMS database with components that use ESA for storage provisioning and server
operations
Some components in Insight Dynamics use the Extensible Server & Storage Adapter (ESA) for
storage provisioning and server operations. Information about resources managed by these
components may be unavailable or missing if you are using a remote CMS database. These
problems occur because ESA cannot access its database when the CMS is using a remote database.
If your CMS is running a remote database and you are using HP Insight Orchestration, HP Insight
Recovery, or logical server management to manage:
• Storage Provisioning Manager catalog-based storage pool entries
Candidate volumes will not be visible in SPM so you cannot create a catalog-based storage
pool entry. In Insight Orchestration, there will be no storage available for use.
• Operations Orchestration Workflow physical servers or non-HP servers
Portability groups containing Operations Orchestration Workflow (OOWF) physical servers
or non-HP servers will not be available for selection when you create a logical server or
storage pool entry. Insight Orchestration will not be able to perform operations that depend
on these types of servers.
• Annotated servers with Virtual Connect using Operations Orchestration workflows
The annotation will be missing, so there will be no server resources with local disks.
Suggested action Change the account under which the ESA service runs to an account that has
access to the remote database.
After installing and configuring the Insight Dynamics CMS to use a remote database:
1. Sign into the CMS as Administrator.
2. Enter the following command:
sc qc "HP Logical Server Automation" 2096
The output will contain a line similar to the following. The string displayed is the account
name that was configured.
SERVICE_START_NAME : string
3. Enter the following command, replacing string with the string in the preceding output. Note
the space between obj= and string.
sc config esa obj= string
4. Restart the ESA service using the Windows Services GUI, or by entering the following two
commands:
sc stop esa
sc start esa
Application Discovery
Major issues
Application Discovery service may run out of memory on initial start-up
On larger scale systems (on a 64-bit CMS), the Application Discovery service may run out of
memory and display an out of memory error on initial start-up. This can be corrected by modifying
the configuration file to increase memory allocation.
Suggested action Perform the following steps to increase the heap size parameter.
16 Issues and suggested actions