Event Monitoring Service Version A.03.
Legal Notices The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Event Monitoring Service Version A.03.10 Release Notes Announcements 1 Event Monitoring Service Version A.03.10 Release Notes Announcements Version A.03.10 of the Event Monitoring Service (B7609BA), includes media, license and manual. Version A.03.10 runs on HP-UX 10.20 and HP-UX 11.0. It is available for HP 9000/Series 700 and 800. The Event Monitoring Service (EMS) together with one or more EMS monitors is a tool you can use to monitor various system resources.
Event Monitoring Service Version A.03.10 Release Notes What’s New in this Version • The MIB Monitors: — HA Cluster Monitor checks the status of ServiceGuard clusters, nodes, or packages and services. — HA Network Interface Monitor reports the status of LAN interfaces. — HA System Resource Monitor checks the number of users, system load, and file system space.
Event Monitoring Service Version A.03.10 Release Notes What’s New in this Version For information about highly available monitors, refer to: • Using High Availability Monitors (HP Part Number B5736-90025) • The High Availability Monitors Version A.03.10 Release Notes • Writing Monitors for the Event Monitoring Service (HP Part Number B7611-90016) available on http://software.hp.com, under the High Availability area. General information about HP-UX 11.
Event Monitoring Service Version A.03.10 Release Notes What’s New in this Version page: http://docs.hp.com/hpux/ha Support information is available from the Hewlett-Packard Electronic Support Center: http://us-support.external.hp.com (US and Asia Pacific) http://europe-support.external.hp.
Event Monitoring Service Version A.03.10 Release Notes Compatibility Information and Installation Requirements Compatibility Information and Installation Requirements EMS should be installed on, each node that you want to monitor. It does not need to be installed on the management station, unless you want to also monitor the management station itself.
Event Monitoring Service Version A.03.10 Release Notes Compatibility Information and Installation Requirements Table 1-2 EMS MC/ServiceGuard Compatibility EMS Version HP-UX Release ServiceGuard Version A.02.00 HP-UX 11.00 MC/ServiceGuard A.11.01, A.11.03 HP-UX 11.00 MC/LockManager A.11.01, A.11.02, A.11.03 HP-UX 10.20 MC/ServiceGuard A.10.11 HP-UX 11.00 MC/ServiceGuard A.11.04, A.11.05, A.11.07, A.11.08 A.03.00 MC/LockManager A.11.04, A.11.05, A.11.06 ServiceGuard OPS Edition A.11.08 A.03.
Event Monitoring Service Version A.03.10 Release Notes Compatibility Information and Installation Requirements Hardware Requirements EMS runs on the HP 9000 series 700 and 800 servers. Memory Requirements EMS requires 2.75 Mb of disk space to install. An additional 13.0 Mb of disk space should be allocated for /etc/opt to support EMS logging facilities. Installing the Event Monitoring Service EMS checks the resources for local systems only.
Event Monitoring Service Version A.03.10 Release Notes Compatibility Information and Installation Requirements • Use the Software Management area in SAM If you have many systems, it may be easier to install over the network from a central location: 1. Create a network depot according to the instructions in Managing HP-UX Software with SD-UX. 2. rlogin or telnet to the remote host on which you are installing EMS. 3. Install over the network from the depot.
Event Monitoring Service Version A.03.10 Release Notes Patches and Fixes in this Version Patches and Fixes in this Version This section describes patches that are required and defects that have been fixed in version A.03.10 of Event Monitoring Service. Required and Recommended Patches The following patches (or their supersedents) are required or recommended with EMS A.03.10. This list is subject to change without notice. Contact your HP support representative for up-to-the-moment information.
Event Monitoring Service Version A.03.10 Release Notes Patches and Fixes in this Version longer need to be applied separately: Table 1-4 EMS Patches Rolled into EMS A.03.10 Patch Date HP-UX Description PHSS_18433 990708 10.20 s700 and s800 10.20 Event Monitoring Service (EMS) English patch PHSS_18434 990712 10.20 s700 and s800 10.20 Event Monitoring Service (EMS) Japanese patch PHSS_18435 990709 11.00 s700 and s800 11.00 Event Monitoring Service (EMS) English patch PHSS_18436 990713 11.
Event Monitoring Service Version A.03.10 Release Notes Patches and Fixes in this Version Table 1-5 Corrected Defects SR Number Problem and Resolution JAGab19144 Problem: When monitors were restarted due to system reboot, a restart notification was sent instead of a reboot notification JAGab69972 Resolution: Reboot notifications are sent only when a monitor is restarted during system start-up immediately after system reboot. Restart notifications are sent when a monitor is restarted at any other time.
Event Monitoring Service Version A.03.10 Release Notes Patches and Fixes in this Version Table 1-5 Corrected Defects SR Number Problem and Resolution JAGab04579 Problem: The EMS GUI running in character mode on HP-UX 11.0 would not show resources when attempting an Add operation. When running on HP-UX 10.20 or 11.0 in GUI mode, resources would sometimes be missing for the Add operation as well. Resolution: Update to EMS version A.03.10.
Event Monitoring Service Version A.03.10 Release Notes Known Problems and Workarounds Known Problems and Workarounds The following are known problems and suggested workarounds with the EMS: JAGab77628: ServiceGuard package package_status is not being reported on nodes in a failed state What is the problem? An EMS “error” event occurs when monitoring the resource instance /cluster/package/package_status/ . cmviewcl shows the local node STATE to be failed. The api.
Event Monitoring Service Version A.03.10 Release Notes Known Problems and Workarounds client connect failed: An error occurred while trying to connect to a remote system: Invalid argument -------------------End Event---------------------- What is the workaround? Perform the following: 1. Ensure the inetd is listening on port 1712. To do this, you can execute the following command. The desired output line is listed here: netstat -an | grep 1712 tcp 0 0 *.1712 *.
Event Monitoring Service Version A.03.10 Release Notes Known Problems and Workarounds nslookup $(hostname) Using /etc/hosts on: mynode Name: mynode Address: 192.1.2.3 If you are using DNS, typically the canonical [official] host name can be a fully-qualified domain name. For example, myhost.hp.com, even if you use only the first component, myhost, for the system hostname. See the search directive in the resolver(4) man page.
Event Monitoring Service Version A.03.10 Release Notes Known Problems and Workarounds / may be incorrectly reported. When monitoring the service status of a package running locally and the ServiceGuard coordinator node is not the same node, service status may be incorrectly reported as UNKNOWN or DOWN when it is really UP. cmviewcl shows the service is UP. What is the workaround? Configure package and service status monitoring on each node in the cluster.
Event Monitoring Service Version A.03.10 Release Notes Known Problems and Workarounds is in /etc/inetd.conf: registrar stream tcp nowait root \ /etc/opt/resmon/lbin/registrar \ /etc/opt/resmon/lbin/registrar After you have confirmed both registrar requirements, reconfigure inetd by executing: inetd -c — Add the /etc/services file to the lookup path your name lookup service uses. For example, modify the nsswitch.conf file to refer to /etc/services if you are running NIS.
Event Monitoring Service Version A.03.10 Release Notes Known Problems and Workarounds the command line by invoking Software Distributor as follows: # swinstall -x enforce_dependencies=false — To change the Enforce Dependency Analysis Errors through the swinstall GUI. 1. Cancel out of the Analysis. 2. From the Software menu, select Options, then Change. Click OK. 3. Scroll to the box for Enforce Dependency Analysis Errors in Agent and click to remove the check mark. Click OK. 4.
Event Monitoring Service Version A.03.10 Release Notes Software Availability in Native Languages installed. For more information about installation procedures and related issues, refer to the following manuals: • Managing HP-UX Software with SD-UX (B2355-90154) • swinstall (1M) in the HP-UX Reference (B2355-90166) Software Availability in Native Languages The following version of Event Monitoring Service, is available: • B7609BA Event Monitoring Service, version A.03.
Event Monitoring Service Version A.03.
