README - HP Systems Insight Manager 5.3

2 Known Issues and Workarounds
Automatic Event Handling
Action on Events tasks (now called Automatic Event Handling tasks) upgraded from HP SIM 4.0 are not
executing as expected. This could happen to any Automatic Event Handling task if the task was not executed
before upgrading. To correct this issue, edit the tasks with the same settings and save them.
-------------------------------------------------------------
You can retrieve XML information for a specific Automatic Event Handling task by using the mxtask -lf
command and then use that XML information to create another Automatic Event Handling task using the
mxtask -cf XML file name . The actual task name in the XML file must be changed because an
Automatic Event Handling task already exists for that name.
One issue that can cause a problem is that if the original Automatic Event Handling task was created with
event and system criteria information specified during the creation of the task rather than using an existing
event collection, then the query that is created for the original task is temporary and only exists while the
original task exists. If that same event collection is used for the new Automatic Event Handling task, then that
task can become invalid if the original task is deleted and the event collection is then deleted. Another
problem is if the XML data retrieved from the original task is used to create a new Automatic Event Handling
task after the original task is deleted. Then, an error of invalid or missing XML data is displayed.
You cannot recreate an Automatic Event Handling task from an XML file because the XML is referencing an
event collection that was created and subsequently deleted along with the original task. You must use the
GUI to create a new Automatic Event Handling task and specify the same characteristics as the original task.
This problem occurs when the task was previously created by selecting the Use system attributes that I
will specify option.
-------------------------------------------------------------
When running Mozilla and creating an Automatic Event Handling task, and the task is being created with
multiple event criteria, the event type criteria must not be the last criteria chosen. If the event type criteria is
the last criteria chosen, the event type criteria will not be included in the task. This does not apply if the event
type criteria is the only criteria listed
This same issue occurs with the Advanced Search feature if you click View or Save As. Use the workaround
as described in the previous paragraph in order for the View or Save As buttons to work correctly.
Browser
My Browser is displaying an error message Communication with the HP SIM server has been
lost.
The HP SIM portal relies on the CMS to respond quickly to all requests.
• If the CMS is slow to respond to one request, browser performance may fall significantly during that
time.
• If the CMS is slow to respond to two requests, the browser appears to lock up completely during
subsequent interaction; the browser does not send additional requests until there are fewer than two
outstanding requests.
• If four sequential ping-like requests each takes more than 30 seconds to complete, due either to request
queuing or slow CMS response, the browser will display the message, Communication with the
HP SIM server has been lost, even though the CMS might still be responsive to other browser
sessions.
On a LAN, the browser receives a CMS response to most requests within 10-100 milliseconds, which is
nearly instantaneous. Requests that involve database queries or secondary network communication may take
a few seconds to respond.
Automatic Event Handling 11