High Availability Monitors Version A.04.00.01 Release Notes

Patches and Fixes in This Version

Chapter 1 17

Resolution: Now, the UNAVAIL status is a valid status recognized by the service monitor.

JAGae05308

Problem: When adding monitoring events using EMS GUI, the following error message is

displayed: "The selected monitor is not currently available" This usually happens when the

event added is the ﬁrst event. The second attempt to add the event is generally successful.

Resolution: Now, diskmond does not send the RM_NOT_READY signal when it is building the

resource tree and events can be added.

JAGad98635

Problem: EMS GUI cannot be used to drill down to view the status of the ﬁrst conﬁgured

package.

Resolution:Now, a new variable is introduced so that the original data is left undisturbed.

JAGad95942

Problem: If the port number for the SNMP service on a MC/ServiceGuard cluster is changed,

and pkgmond is invoked with this new port number (using -p), the snmpget queries of

pkgmond time out. The EMS GUI displays UNAVAIL status for all packages.

Resolution: pkgmond is ﬁxed to check the port number speciﬁed in the command line string in

the mibmond.dict ﬁle.

JAGad37795

Problem: EMS deleted persistent monitoring requests for diskmond after system reboot or

restart of EMS.

Resolution: The diskmond monitor is modiﬁed to send RM_NOT_READY signal to the registrar

process when it is in the middle of building a resource tree for disks, volume groups, and

logical volumes. Diskmond checks every ﬁve seconds for a message from the registrar, and

responds with the RM_NOT_READY signal if it ﬁnds one.

JAGad62023

Problem: If customer has a MC/ServiceGuard cluster where they are monitoring two services

in the same package, inconsistent service_status is reported between different services

within the package. For example, when the package is running on the cluster coordinator

node, one service_status returns DOWN (even though the service is actually UP) and the other

service_status returns the correct value (UP).

Resolution: The EMS service monitor "svcmond" is modiﬁed to report the same status for

service_status as that reported for the package_status. Current logic is that a

MC/ServiceGuard package cannot have a package_status that is UP if any of its services are

not UP as well.