Patch Name: PHSS_23577 Patch Description: s700_800 10.20 Event Monitoring Service(EMS A.03.20) patch Creation Date: 01/06/18 Post Date: 01/08/06 Hardware Platforms - OS Releases: s700: 10.20 s800: 10.20 Products: B7609BA EMS A.03.20 Filesets: EMS-Core.EMS-CORE,A.03.20 EMS-Config.EMS-GUI,A.03.20 EMS-MIBMonitor.MIBMON-RUN,A.03.20 Automatic Reboot?: No Status: General Release Critical: Yes PHSS_23577: OTHER The problem JAGad51995 solved was causing data loss. Path Name: /hp-ux_patches/s700_800/10.X/PHSS_23577 Symptoms: PHSS_23577: 1. Symptom for defect JAGad58993: Within the EMS Configuration tool accessed via SAM, the resource of /StorageAreaNetwork/events is given as a resource path that a monitoring request can be defined against. This path should not be accessible through this interface. If a request against this resource path was configured through the EMS interface, there is a possibility that the request would be lost over time. Requests against /StorageAreaNetwork/events should be configured through monconfig (OnlineDiag) 2. Symptom for defect JAGad54357: If PHSS_22897 had been applied to a system, a subsequent swverify would report an inconsistency WARNING against the file permissions for the /etc/opt/resmon/log and /var/opt/resmon/log directories. The WARNING is: WARNING: Directory "/etc/opt/resmon/log" should have mode "777" but the actual mode is "755". 3. Symptom for defect JAGad51995: Persistent monitoring requests for diskmond are deleted by EMS. After system boot or restart of EMS (specifically: restart of p_client and diskmond), persistent monitoring requests for diskmond may be deleted by EMS. 4. Symptom for defect JAGad62063: If a customer has a ServiceGuard cluster where they are monitoring two services in the same package, (/cluster/package/service_status/[pkg_name]/[srvc_name]) 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 acutally UP) and the other service_status returns the correct value (UP). 5. Symptom for defect JAGad56655: If a customer has a ServiceGuard cluster where each node has an SNMP read-community name other than the default ("public"), the EMS Package Monitor pkgmond and Service Monitor svcmond fail to report correct status for package_status and service_status respectively. For example, the package resource /cluster/package/package_status/yampkg1 is set to UNAVAIL and the service status resource /cluster/package/service_status/yampkg1/yam is set to ERROR. PHSS_22897: 1. Symptom for defect JAGad39533: Not all resource requests are seen in the EMS GUI when more than 1023 resource instances have monitoring requests established against them. The resource requests exist, but they just can't be displayed by the EMS GUI. 2. Symptom for defect JAGad38867 Certain EMS files have permissions on them that are too open. The /etc/opt/resmon/log directory currently has permissions of 777 (along with /var/opt/resmon/log), and the /etc/opt/resmon/persistence/runlevel4_flag has 666. 3. Symptom for defect JAGad05568: Persistent monitoring requests sometimes disappeared after reboot. When same instance request has been setup both in a SG package and in SAM, the persistent request (setup in SAM) sometimes disappeared after reboot, but persistence file still contains the request. 4. Symptom for defect JAGad26096: EMS does not work properly when system is booted in single user mode and then issues 'init 3' to start up the system process. Defect Description: PHSS_23577: 1. Reason for JAGad58993 The EMS Configuration tool should not allow configuration against the path of /StorageAreaNetwork/events 2. Reason for JAGad54357 PHSS_22897 changed the permissions form 777 to 755, but did not update the IPD as well. 3. Reason for JAGad51995 When the system reboots or EMS restarts, diskmond starts building and initializing a resource tree for all disks, volume groups and logical volumes configured on the system. If this initialization exceeds more than 15 sec, diskmond fails to process the requests received by registrar. This causes the registrar to timeout and send an error message to the client. Some or all persistence requests get deleted. 4. Reason for JAGad62063 The EMS service monitor "svcmond" obtains the service_status from the cluster coordinator's MIB variable hpmcSGPkgSvcStatus which may be incorrect depending on where the package is actually running. Furthermore, due to the design of the Service Guard SNMP subagent cnsnmpd, only the node were the package is running will have a MIB containing the correct service_status. The EMS service monitor "svcmond" was modified to report the same status for the service_status as that reported for the package_status. Current logic is that a Service Guard package cannot have a package_status that is UP if any of its services are not UP as well. 5. Reason for JAGad56655 The wrong constuctor was used to establish the SNMP session. It was resetting to 1 and the interval to 5 seconds and ignoring what had been specified on the mibmond.dict entry for pkgmond and svcmond. The fix was to preserve the user's settings in a global variable and then restore them right before establishing the SNMP session. PHSS_22897: 1. Reason for JAGad39533 When the framework returns resource instance information back to a requestor, it fills in a table with the resource instances. The table size is fixed at 1023. If more than 1023 resource instances exist, then the additional resource instances are simply ignored and not returned to the caller. 2. Reason for JAGad38867 The files and/or directories involved here were simply created with permission values that are too open. 3. Reason for JAGad05568: There is a race condition between two p_clients. When the system is rebooted, SG starts up, sends EMS requests to EMS. But, the associated monitor is not running, so EMS registrar forks a p_client to start the monitor. But, this p_client did not get persistence lock, so registrar starts the monitor. Meanwhile, init p_client tries to process the persistence file, it found the monitor is running, so it skips the persistence file and requests lost. 4. Reason for JAGad26096: When the system is booted as single user mode, EMS commands in /etc/inittab do not get executed, so EMS does not know it is a reboot situation. SR: 8606170269 8606169592 8606136444 8606156762 8606189780 8606185155 8606182779 8606192851 8606187448 Patch Files: /etc/opt/resmon/lbin/mibmond /etc/opt/resmon/lbin/p_client /etc/opt/resmon/lbin/registrar /etc/opt/resmon/lib/libresmon.1 /etc/opt/resmon/lib/nls/msg/C/resmon.cat /etc/opt/resmon/monitors/classes.config /opt/resmon/share/man/man1/mibmond.1 /sbin/init.d/ems what(1) Output: /etc/opt/resmon/lbin/mibmond: EMS (A.03.20 PHSS_23116 (HA Monitors) & PHSS_23577 ( EMS)) SNMP++ 2.5 $Header: address.cpp,v 1.28 96/08/08 19:3 8:48 hmgr Exp $ SNMP++ 2.5 $Header: counter.cpp,v 1.8 96/02/09 14:03 :12 hmgr Exp $ SNMP++ 2.5 $Header: gauge.cpp,v 1.8 96/02/09 14:03:2 0 hmgr Exp $ SNMP++ 2.5 $Header: octet.cpp,v 1.14 96/06/26 10:17: 49 hmgr Exp $ -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 HP C++ HPCPLUSPLUS A.10.08 /etc/opt/resmon/lbin/p_client: EMS (A.03.20 PHSS_23116 (HA Monitors) & PHSS_23577 ( EMS)) /etc/opt/resmon/lbin/registrar: EMS (A.03.20 PHSS_23116 (HA Monitors) & PHSS_23577 ( EMS)) /etc/opt/resmon/lib/libresmon.1: $Header: send_email_notification.c,v x.0306 98/08/05 08:35:47 $Header: log_source.c,v x.0305 98/07/29 11:00:47 hmg r Exp $ EMS (A.03.20 PHSS_23116 (HA Monitors) & PHSS_23577 ( EMS)) /etc/opt/resmon/lib/nls/msg/C/resmon.cat: None /etc/opt/resmon/monitors/classes.config: None /opt/resmon/share/man/man1/mibmond.1: None /sbin/init.d/ems: None cksum(1) Output: 4169118226 2494464 /etc/opt/resmon/lbin/mibmond 4003493044 73728 /etc/opt/resmon/lbin/p_client 2938910704 143360 /etc/opt/resmon/lbin/registrar 1070476784 524288 /etc/opt/resmon/lib/libresmon.1 144009313 79687 /etc/opt/resmon/lib/nls/msg/C/resmon.cat 2941305945 252 /etc/opt/resmon/monitors/classes.config 1330176236 7090 /opt/resmon/share/man/man1/mibmond.1 1419108792 1592 /sbin/init.d/ems Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_22897 Equivalent Patches: None Patch Package Size: 3320 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHSS_23577 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_23577.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_23577. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. WARNING: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHSS_23577.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_23577.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: 1. To use the functionality in this patch, you will need to restart all clients after installing this patch. In addition, since a shared library is being replaced, you will need to restart any monitors that are active.