Issues tables

Following are the known and corrected issues in this release of BMC PATROL for Event Management and its service packs and patches.

Description	Defect ID	Affected versions	Corrected in
Availability target IP Address was appended to the notify event description when the availability target was down.	QM001968227	2.9.00, 2.9.10	2.9.00.03. 2.9.10.01
Wildcard characters did not work for the the msgBody and msgText rules, when they were configured for multiple types of events.	QM001974513	2.9.00.02, 2.9.10	2.9.00.03, 2.9.10.01
If wildcards were used for threshold rules in multiple application classes, after processing the rules of the first application class, the following message was displayed in the PATROL Agent error log file: PatrolAgent-E-EINTERNAL: No command type for parameter <parameter_name> -- parameter suspended	QM001726243	2.9.00	2.9.00.01
When the `alarmResend` option is used, source event information is missing in NOTIFY_EVENT.	QM001734865	2.9.00	2.9.00.01
The poll time settings were set to the default values on restarting the PATROL Agent.	QM001818378	2.9.00	2.9.00.01, 2.9.00.02
HostPingFailure did not send any alert message, when the server was stopped. The following output of the ping command was displayed: `Reply from <Host Name>: Destination host unreachable`	QM001828740	2.9.00	2.9.00.01
A warning message is logged in the PATROL Agent error log file when only the arsAction rule is specified. For example, arsAction = 2	QM001851744	2.9.00	2.9.00.02
The `paramSettingsStatusFlag` configuration variable is getting set to `6` even when there is no difference in the active KM list.	QM001861132	2.9.00	2.9.00.02
When multiple parameters change to the ALARM status at the same time, the recovery action worked for only one instance.	QM001863590	2.9.00	2.9.00.02
The new standard catalog missed the IS_CONNECT and IS_DISCONNECT events that were related to self-monitoring.	QM001863592	2.9.00	2.9.00.02

Page tree

Issues tables