Patch Name: PHSS_28843 Patch Description: s700_800 11.00 EMS (A.03.20) & HA Monitors (A.03.20) patch Creation Date: 03/07/03 Post Date: 03/09/23 Hardware Platforms - OS Releases: s700: 11.00 s800: 11.00 Products: B7609BA EMS A.03.20 B5736BA HA Monitors A.03.20 B5736DA HA Monitors A.03.20 Filesets: EMS-Core.EMS-CORE,fr=A.03.20,fa=HP-UX_B.11.00_32/64,v=HP EMS-Config.EMS-GUI,fr=A.03.20,fa=HP-UX_B.11.00_32/64,v=HP EMS-MIBMonitor.MIBMON-RUN,fr=A.03.20,fa=HP-UX_B.11.00_32/64,v=HP EMS-DiskMonitor.DISKMON-RUN,fr=A.03.20,fa=HP-UX_B.11.00_32/64,v=HP EMS-RdbmsMon.RDBMSMON-RUN,fr=A.03.20,fa=HP-UX_B.11.00_32/64,v=HP Automatic Reboot?: No Status: General Release Critical: Yes PHSS_28843: ABORT CORRUPTION When there is memory corruption, the EMS registrar may send a NULL resource name to the legacy monitor. As a result, the legacy monitor may dump core. PHSS_23575: OTHER The problem solved was causing data loss. Category Tags: defect_repair enhancement general_release critical halts_system corruption Path Name: /hp-ux_patches/s700_800/11.X/PHSS_28843 Symptoms: PHSS_28843: 1. For JAGae64347 EMS registrar may send a NULL Resource Name to the legacy monitor when there is memory corruption. As a result,the legacy monitor may dump core. 2. For JAGae63196 When the clients try to connect to a remote machine, EMS clients like moncheck and toggle_switch may fail with the message "EMS registrar inetd service not started. Start registrar and retry.". 3. For JAGae61828 EMS mibmond and rdbmsmond monitors log wrong identification strings to syslog. 4. For JAGae61730 EMS diskmond shows an incorrect state (PVG_UP) for /vg//pv_summary even when the /etc/lvmpvg file is removed. 5. For JAGae59337 After a second reboot, following the first reboot in quick succession, PSM monitor (psmmon) requests are deleted and the persistence file is set to zero bytes. 6. For JAGae54891 When an EMS client and registrar try to write data to a socket, the write system call might fail with errno set to EAGAIN repeatedly. As a result the EMS client, e.g. p_client or cmcld, process may consume high CPU. 7. For JAGae50732 The description for syslog in the online help does not contain information about logging level and facility. 8. For JAGae38359 After a system reboot, when an attempt is made to register non-persistent monitoring requests (during RC script execution), EMS times out with a message. ServiceGuard may log "ems timed out" in syslog.log and a package with EMS resource dependencies may start on an adoptive node. This problem occurs only if there are any existing persistent requests during RC script execution. PHSS_28144: 1. For JAGae46452 When hardware monitoring is disabled using monconfig(K), persistent requests that are setup using the EMS GUI sometimes get deleted and sometimes not. 2. For JAGae45457 In a scenario where there are four sets of mirrored disks (eight disks) and four Physical Volume Groups (PVG) and when one disk is DOWN, pv_summary reports that the disk is in DOWN state, even though the corresponding mirrored disk is up and accessible. PHSS_26871: 1. For JAGae30244 EMS diskmond persistence requests are lost after a reboot. 2. For JAGae08920 At times, multiple instances of the same monitor may be running on the system. 3. For JAGae13889 The EMS disk monitor, diskmond, aborts and dumps core if any of the volume group entries in the /etc/lvmtab file, have more than 255 Physical Volume Links/Paths. 4. For JAGae27135 EMS persistence requests are deleted when the EMS startup script is manually executed to start and stop EMS. (/sbin/init.d/ems stop and /sbin/init.d/ems start) PHSS_25897: 1. For JAGad92412 When monitoring ServiceGuard package services with svcmond, EMS reports "Error" for the status of service when the package in which the service resides, changes to the state UNAVAIL. 2. For JAGad95942 If the default port number for the snmp snmp-trap 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. 3. For JAGad94757 During the upgrade of the OnlineDiag bundle, some persistent monitor requests may be deleted and not re-established after the upgrade. 4. For JAGad39793 Upon system restart and/or monitor restart, some persistent monitor requests associated with the various MIB monitors (i.e., clustermond, rdbmsmond, fsmond, lanmond, mibmond, pkgmond, and svcmond) may be deleted due to delay in monitor initialization. 5. For JAGab77527 Some EMS clients may not be able to register monitoring requests upon system restart, thus causing "Event 11" error to be logged to client.log 6. For JAGad93308 This is an enhancement to the "resls" utility.The ability to check the resource value/state was not available in resls utility from the command line 7. For JAGae05308 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 first event. The second attempt to add the event is generally successful. PHSS_24149: 1. For JAGad62063 If customer has a Service Guard 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). PHSS_23592: 1. For JAGad56655: If a customer has a Service Guard 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. 2. For JAGad58993 Within the EMS Configuration tool accessed via SAM, the resoure 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) PHSS_23575: 1. 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. 2. Symptom for defect JAGad54357: If PHSS_22896 had been applied to a system, a subsequent swverify would report a 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. Sympton for defect JAGad37995 Duplicate of JAGad51995 PHSS_22896: 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. 5. Symptom for defect JAGad06311: Disk monitor marked PV/VG down on CHECK_CONDITION errors on XP256. When doing operations on the XP256 on different LUNs, the disk monitor prints check_ condition errors in api.log and marks the VG as DOWN. Defect Description: PHSS_28843: 1. Reason for JAGae64347: EMS registrar creates a dictionary object, which is populated with the contents of the dictionary files. The dictionary object gets corrupted when legacy monitors are used. This may result in the EMS registrar sending a NULL resource name to the legacy monitor. Resolution: The memory corruption in handling dictionary objects in the EMS registrar has been fixed. 2. Reason for JAGae63196: The clients use the rm_service_up API provided by the shared libraries libresmon.1 and librescli.1. The rm_service_up API does not handle standard errors like EINPROGRESS and EINTR from the connect(2) system call. Resolution: EMS code has been modified to handle EINPROGRESS and EINTR errors. 3. Reason for JAGae61828: EMS mibmond and rdbmsmond monitors log wrong identification strings to syslog because of memory corruption. Resolution: The memory corruption in EMS has been fixed. Now, EMS mibmond and rdbmsmond monitors log correct identification strings to syslog. 4. Reason for JAGae61730: EMS diskmond does not check if the /etc/lvmpvg file is removed before using the cached data. It uses the data that it had cached earlier even when the /etc/lvmpvg file is deleted. As a result, EMS diskmond shows an incorrect state (PVG_UP) for pv_summary. Resolution: Now, EMS diskmond checks if the /etc/lvmpvg file exists before using the data it had cached earlier. 5. Reason for JAGae59337: psmmon persistence requests are set and the system is then rebooted. Before the bootup is complete, the system is rebooted again due to an unrelated hardware problem. After the second reboot, all the persistence monitoring requests associated with psmmon are deleted. The persistence file is set to zero bytes. Resolution: The EMS startup and shutdown scripts are modified to remove and touch a file respectively. psmmon on detecting the touched file under a dual reboot condition, sends RM_NOT_READY signal instead of RM_REJECT signal. Hence the requests are not deleted from the persistence file. 6. Reason for JAGae54891: Since the EMS client continues to send requests to the registrar, the TCP receive buffers are filled. As a result, neither registrar nor the EMS client are able to write(2) to the socket. The client's write requests fail with errno set to EAGAIN repeatedly and may lead to the client running into an endless loop resulting in high CPU usage. As the registrar is blocked on writing an error reply to the EMS client, it finally hangs. Resolution: The EMS code has been modified such that the EMS client and registrar write data to a socket successfully. 7. Reason for JAGae50732: EMS notification messages are sent to syslog with logging level LOG_INFO and facility LOG_LOCAL1. This information is not captured in the online help. Resolution: The description for syslog in the online help has been modified to include information about logging level and facility. 8. Reason for JAGae38359: After a system reboot, when an attempt is made to register non-persistent monitoring requests, EMS tries to start persistent monitor requests using the p_client process. But the p_client process is designed to wait for completion of startup script execution. If the startup script execution takes a longer time, EMS clients time out. Resolution: The code in EMS has been modified to allow new persistent and non-persistent requests to be registered during RC Scripts execution. PHSS_28144: 1. Reason for JAGae46452: When two or more persistent requests for a single EMS hardware monitor are setup using the EMS GUI, they do not get deleted if hardware monitoring is disabled with monconfig(K) and re-enabled by monconfig(E). If only one single persistent request for a hardware monitor is configured in the EMS GUI, the same procedure of disabling and enabling hardware monitoring will delete this request. Resolution: p_client has been changed such that all the persistent requests for hardware resources configured through the EMS GUI are deleted when hardware monitoring is disabled. This is the right behaviour, which is also explained during monconfig(K) execution. 2. Reason for JAGae45457: There are four sets of mirrored disks (eight disks) and four Physical Volume Groups (PVG). Each disk has its primary physical volume link in one PVG and the alternate physical volume link in the other PVG. In such a scenario, when one disk goes down, its mirror is still accessible. However, pv_summary reports that the disk is in DOWN state. Resolution: EMS algorithm has been modified. Now, pv_summary reports that the disk is in PVG_UP state. PHSS_26871: 1. Reason for JAGae30244: EMS diskmond persistence requests are lost because the registrar does not handle persistence requests properly when there is a delay in the monitor initialization. Instead of a RM_NOT_READY signal, it sends a RM_NO_MONITOR_FOUND signal to the persistence client that results in the requests getting deleted. Resolution : Now, the registrar sends the RM_NOT_READY signal when there is a delay in the monitor initialization. 2. Reason for JAGae08920: The registrar starts the monitor. The registrar (parent process) obtains a semaphore lock and then creates a child process, which starts the monitor. However, sometimes when the parent process gets the control, it releases the semaphore even before the child process has finished starting the monitor. This allows another registrar process to obtain the semaphore lock and start another instance of the same monitor. Resolution: The parent process now releases the semaphore only when the child process has successfully started the monitor or when the child process dies before opening the pipe file for the monitor. 3. Reason for JAGae13889: The disk monitor currently supports only 255 Physical Volume Paths/Links for each of the Physical Volume Groups. Resolution: The disk monitor has been modified to dynamically handle any number of Physical Volume Paths/Links for each of the Physical Volume Groups. 4. Reason for JAGae27135: EMS persistence requests are deleted when the /etc/init.d/ems startup script is manually executed. This is because the startup script should not be executed manually, and when executed manually, EMS assumes a startup situation. Resolution: The /sbin/init.d/ems script has been modified to prevent the requests from getting lost. PHSS_25897: 1. Reason for JAGad92412: As per the fix JAGad62063, the status of service is identical to the corresponding package status. Unlike packages, service monitor in EMS did not recognize the UNAVAIL status as valid. Hence the UNAVAIL status for services was considered invalid and the resource status was reported as 'Error'. With this patch the UNAVAIL status is now a valid status recognized by the service monitor 2. Reason for JAGad95942 pkgmond was using the default snmp port instead of checking the port number specified in the command line string in the mibmond.dict file. 3. Reason for JAGad94757 During the upgrade of the OnlineDiag bundle all hardware monitoring is shutdown. If the EMS persistence client is invoked during this upgrade, the OnlineDiag Peripheral Status Monitor (PSM) would return RM_MONITOR_SHUTDOWN status to the EMS persistence client for any monitor request associated with the PSM. The EMS persistence client would treat this as though the monitor was unavailable and delete the monitor request. The EMS persistence client has been changed to filter PSM requests during an OnlineDiag upgrade. The users now need to touch the "upgrade_touch" file in the /etc/opt/resmon/monitors directory before upgrading the OnlineDiag bundle. When this file is present, the EMS persistence client will not attempt to invoke the hardware monitors associated with the OnlineDiag bundle. This file needs to be deleted after the upgrade is complete. 4. Reason for JAGad39793 When the system reboots or EMS restarts, various MIB monitors start building and initializing a resource tree for all resources that are monitored. If this initialization takes more than 15 sec, the MIB monitor fails to process the requests received by the registrar. This causes the registrar to timeout and send an error message to the client. Some or all persistence requests get deleted. For MIB monitors that are being initialized, registrar now sends RM_NOT_READY message to the client. When the client receives this message it continues to maintain all persistence requests of the MIB monitors. 5. Reason for JAGab77527 inetd should be running when a connection needs to be established between the client and the registrar. For any reason, if the client application starts before inetd is up and running, this problem occurs and error messages are logged to the client.log file. A new API has been added to the libresmon library to fix this problem. It is described in /etc/opt/resmon/lib/NewClientAPI.readme 6. Reason for JAGad93308 This is an enhancement to the "resls" utility. A new command-line option "-s" is now added to this utility to output the status of a resource to stdout. 7. Reason for JAGae05308 When a user adds an event using EMS GUI and if diskmond starts (re)building its resource tree, it sends a not ready signal to EMS GUI, which in turn displays the error message. With this patch, diskmond does not send the not ready signal when it is building the resource tree and events can be added. PHSS_24149: 1. 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 where 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. PHSS_23592: 1. Reason for JAGad56655: The wrong constructor was used to establish the SNMP session. It was resetting the community name to public, the retries 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. 2. Reason for JAGad58993 The EMS Configuration tool should not allow configuration against the path of /StorageAreaNetwork/events. PHSS_23575: 1. 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. 2. Reason for JAGad54357: PHSS_22896 changed the permissions from 777 to 755, but did not update the IPD as well. PHSS_22896: 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. 5. Reason for JAGad06311: The disk monitor was only retrying certain check_ conditions such as a powerfail or a bus reset, whereas it should really be retrying any valid check condition. Code was changed to retry any valid check_ condition and also to print out an additional sense byte. Enhancement: No (superseded patches contained enhancements) PHSS_25897: This patch delivers new functionality for the resls utility. A new command line option "-s" is added to output the status of a resource to stdout. SR: 8606300877 8606299702 8606298328 8606298230 8606295672 8606291048 8606286793 8606274282 8606282499 8606281515 8606265991 8606241662 8606247452 8606262805 8606182779 8606170269 8606169592 8606136444 8606156762 8606137193 8606185155 8606168717 8606189780 8606187448 8606192851 8606223309 8606226880 8606225684 8606170529 8606107338 8606224213 8606236247 Patch Files: EMS-Core.EMS-CORE,fr=A.03.20,fa=HP-UX_B.11.00_32/64,v=HP: /etc/opt/resmon/lbin/p_client /etc/opt/resmon/lbin/registrar /etc/opt/resmon/lib/libresmon.1 /etc/opt/resmon/lib/librescli.1 /etc/opt/resmon/lib/NewClientAPI.readme /etc/opt/resmon/lib/nls/msg/C/resmon.cat /sbin/init.d/ems /etc/opt/resmon/monitors/disable_resource.config /opt/resmon/bin/resls /opt/resmon/share/man/man1/resls.1 EMS-Config.EMS-GUI,fr=A.03.20,fa=HP-UX_B.11.00_32/64,v=HP: /etc/opt/resmon/monitors/classes.config /usr/obam/lib/help/C/ems/ems00.ht /usr/obam/lib/help/C/ems/ems.hv /usr/obam/lib/help/C/ems/ems.hvk /usr/obam/lib/help/C/ems/ems.xrh EMS-MIBMonitor.MIBMON-RUN,fr=A.03.20,fa=HP-UX_B.11.00_32/64, v=HP: /etc/opt/resmon/lbin/mibmond /opt/resmon/share/man/man1/mibmond.1 EMS-DiskMonitor.DISKMON-RUN,fr=A.03.20, fa=HP-UX_B.11.00_32/64,v=HP: /etc/opt/resmon/lbin/diskmond /etc/opt/resmon/lib/nls/msg/C/diskmond.cat EMS-RdbmsMon.RDBMSMON-RUN,fr=A.03.20,fa=HP-UX_B.11.00_32/64, v=HP: /etc/opt/resmon/lbin/rdbmsmond what(1) Output: EMS-Core.EMS-CORE,fr=A.03.20,fa=HP-UX_B.11.00_32/64,v=HP: /etc/opt/resmon/lbin/p_client: EMS (A.03.20 PHSS_28843) /etc/opt/resmon/lbin/registrar: EMS (A.03.20 PHSS_28843) /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_28843) /etc/opt/resmon/lib/librescli.1: EMS (A.03.20 PHSS_28843) /etc/opt/resmon/lib/NewClientAPI.readme: None /etc/opt/resmon/lib/nls/msg/C/resmon.cat: None /sbin/init.d/ems: None /etc/opt/resmon/monitors/disable_resource.config: None /opt/resmon/bin/resls: EMS (A.03.20 PHSS_28843) /opt/resmon/share/man/man1/resls.1: None EMS-Config.EMS-GUI,fr=A.03.20,fa=HP-UX_B.11.00_32/64,v=HP: /etc/opt/resmon/monitors/classes.config: None /usr/obam/lib/help/C/ems/ems00.ht: None /usr/obam/lib/help/C/ems/ems.hv: None /usr/obam/lib/help/C/ems/ems.hvk: None /usr/obam/lib/help/C/ems/ems.xrh: None EMS-MIBMonitor.MIBMON-RUN,fr=A.03.20,fa=HP-UX_B.11.00_32/64, v=HP: /etc/opt/resmon/lbin/mibmond: HP C++ HPCPLUSPLUS A.11.00 EMS (A.03.20 PHSS_28843) 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 /opt/resmon/share/man/man1/mibmond.1: None EMS-DiskMonitor.DISKMON-RUN,fr=A.03.20, fa=HP-UX_B.11.00_32/64,v=HP: /etc/opt/resmon/lbin/diskmond: HP C++ HPCPLUSPLUS A.11.00 EMS (A.03.20 PHSS_28843) /etc/opt/resmon/lib/nls/msg/C/diskmond.cat: None EMS-RdbmsMon.RDBMSMON-RUN,fr=A.03.20,fa=HP-UX_B.11.00_32/64, v=HP: /etc/opt/resmon/lbin/rdbmsmond: HP C++ HPCPLUSPLUS A.11.00 EMS (A.03.20 PHSS_28843) 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 cksum(1) Output: EMS-Core.EMS-CORE,fr=A.03.20,fa=HP-UX_B.11.00_32/64,v=HP: 3905062357 86016 /etc/opt/resmon/lbin/p_client 3934250531 163840 /etc/opt/resmon/lbin/registrar 4248872472 536576 /etc/opt/resmon/lib/libresmon.1 657163648 249856 /etc/opt/resmon/lib/librescli.1 3586865821 1340 /etc/opt/resmon/lib/NewClientAPI.readme 2512010886 82419 /etc/opt/resmon/lib/nls/msg/C/resmon.cat 347714107 2293 /sbin/init.d/ems 3826384824 374 /etc/opt/resmon/monitors/ disable_resource.config 393522805 32768 /opt/resmon/bin/resls 794406847 1219 /opt/resmon/share/man/man1/resls.1 EMS-Config.EMS-GUI,fr=A.03.20,fa=HP-UX_B.11.00_32/64,v=HP: 2941305945 252 /etc/opt/resmon/monitors/classes.config 2532554396 26785 /usr/obam/lib/help/C/ems/ems00.ht 2241000876 4774 /usr/obam/lib/help/C/ems/ems.hv 1562564889 38 /usr/obam/lib/help/C/ems/ems.hvk 3401677053 3102 /usr/obam/lib/help/C/ems/ems.xrh EMS-MIBMonitor.MIBMON-RUN,fr=A.03.20,fa=HP-UX_B.11.00_32/64, v=HP: 2562692713 2547712 /etc/opt/resmon/lbin/mibmond 2841300900 7238 /opt/resmon/share/man/man1/mibmond.1 EMS-DiskMonitor.DISKMON-RUN,fr=A.03.20, fa=HP-UX_B.11.00_32/64,v=HP: 1281354046 360448 /etc/opt/resmon/lbin/diskmond 2823935231 13609 /etc/opt/resmon/lib/nls/msg/C/diskmond.cat EMS-RdbmsMon.RDBMSMON-RUN,fr=A.03.20,fa=HP-UX_B.11.00_32/64, v=HP: 5981259 2560000 /etc/opt/resmon/lbin/rdbmsmond Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: Support Tool Manager (STM) version A.42.00 (Planned - September 2003), or greater, must also be installed to provide a complete solution for the psmmon persistence requests being deleted. This is documented in SR 8606295672 (JAGae59337). This fix is only necessary when the Peripheral Status Monitor (psmmon) is being used. Patch PHSS_28843 can be installed on systems with earlier STM versions with no impact to the STM or EMS products. However the above STM version is necessary for the complete solution to SR 8606295672 (JAGae59337). Supersedes: PHSS_22896 PHSS_23575 PHSS_23592 PHSS_24149 PHSS_25897 PHSS_26871 PHSS_28144 Equivalent Patches: PHSS_28844: s700: 11.11 s800: 11.11 Patch Package Size: 1700 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_28843 5. Run swinstall to install the patch: swinstall -x autoreboot=true -x patch_match_target=true \ -s /tmp/PHSS_28843.depot By default swinstall will archive the original software in /var/adm/sw/save/PHSS_28843. If you do not wish to retain a copy of the original software, include the patch_save_files option in the swinstall command above: -x patch_save_files=false WARNING: If patch_save_files is false when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. For future reference, the contents of the PHSS_28843.text file is available in the product readme: swlist -l product -a readme -d @ /tmp/PHSS_28843.depot To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_28843.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: 1. Restart all EMS clients after installing this patch. In addition, since shared library is being replaced, all the EMS monitors need to be killed to allow EMS to restart them automatically if required. Rebooting the system will ensure that all clients and monitors are restarted properly. 2. If the port numbers for the snmp and snmp-trap services are changed on a MC/ServiceGuard cluster node, the same change needs to be made on all other nodes in the cluster too. 3. EMS does not provide start and stop functionality. Thus, do not use /sbin/init.d/ems script to start or stop the EMS services.