HP Virtual Server Environment Management for Integrity Version 4.0 Release Notes

• Using illegal characters when creating a regular expression in an AD template will crash
the Application Discovery user interface.
Application Discovery recognizes regular expressions constructed using Perl 5 or POSIX
syntax and semantics. If you use characters or syntax not recognized by these conventions
(shell syntax, for example), the AD user interface will crash.
Workaround See “PCRE - Perl Compatible Regular Expressions” at http://www.pcre.org/
for building valid regular expressions that you can include in AD application templates.
In the event of a crash, go the HP SIM Tools menu, and select Integrated
Consoles→Application Discovery to start a new session.
• There is no vseassist check to verify that the Application Discovery agent is installed
and running on managed systems.
Workaround Verify Application Discovery agent status by running Configure→Configure
VSE Ag ents→Check AD Agent States....
• New Application Discovery agent certificates must be exchanged even where managed
systems already have a VSE 3.x agent installed.
Use Configure→Configure VSE Agents→Exchange AD Agent Certificates to re-configure
those agents. For details, see “Complete the Certificate Exchange for Application Discovery”
in the VSE Management Software Version 4.0 Getting Started Guide.
Major Issues
• Application Discovery certificate exchange fails when Application Discovery is installed on
an HP-UX 11i v2 (11.23) or 11i v3 (11.31) CMS server that has OpenSSL version 0.9.8 installed.
Workaround Before installing Application Discovery on the CMS server, switch to version
0.9.7 of OpenSSL by executing the following commands:
# /opt/openssl/switchversion.sh
# vseinitconfig -a
Once installation is complete, you can return the CMS server to the original version of
OpenSSL by running the above script again.
• The Applications tab on an HP SIM System Page is blank (displays no information) for
managed systems where Application Discovery agent is not installed, configured, or running.
Workaround In the case where you know the managed system has an Application Discovery
agent installed, and you think data should be visible in the Applications tab, see
“Troubleshooting and Error Messages” in the HP Application Discovery Version 4.0 User's
Guide to configure or start the agent.
Minor Issues
• In the situation where an existing managed system is removed from HP SIM (is no longer
discovered by that CMS), and where Application Discovery agent is running and reporting
to the current CMS, the Application Discovery agent continues to report to Application
Discovery server on the CMS and the Application Discovery user interface continues to
display the host that is no longer a managed system of that CMS.
Workaround To prevent this situation from occurring, it is recommended that Application
Discovery agent be stopped before removing the managed system from HP SIM. Use
Configure→Configure VSE Agents→Stop AD Agents.... Alternatively, Application
32 Known Issues