Patch Name: PHSS_28296 Patch Description: s700_800 11.X OV SA1.02 MD Patch-6 Creation Date: 02/12/04 Post Date: 02/12/13 Hardware Platforms - OS Releases: s700: 11.00 11.11 s800: 11.00 11.11 Products: OpenView Service Assurance 1.02 MD Filesets: OVCA_mdRT.OVCAMD-API,fr=A.01.02,fa=HP-UX_B.11.00_32/64,v=HP OVCA_mdAUX.OVCAMD-AUX,fr=A.01.02,fa=HP-UX_B.11.00_32/64,v=HP OVCA_mdRT.OVCAMD-RUN,fr=A.01.02,fa=HP-UX_B.11.00_32/64,v=HP Automatic Reboot?: No Status: General Release Critical: No Category Tags: defect_repair general_release Path Name: /hp-ux_patches/s700_800/11.X/PHSS_28296 Symptoms: PHSS_28296: Cumulative Consolidated Patch PHSS_28289: PTSfc02692: With FMS down and only MD up, if the number of alarms received by IFMPS exceeds the maximum size of the buffer configured, the older alarms are over written. In the IFMP.log file the message 'A Fault being deleted. Port Name=' is seen after sending some alarms. PTSfc02989: Valid alarms are being dropped by mapper process. Steps to reproduce the problem. 1). Start MD. 2). Send a valid alarm to the MD subsystem. 3). Add new message class. Configure extraction and mapping details for the new message class through "fmscfg" utility. 4). Run "fmscfgsync -conf" and "fmscfgsync -mdupd" 5). Send a valid alarm, which matches with the new message class configured in step 3. 6). The alarm will be dropped by the mapper process. Check $MDVAR/share/log/MAP.log for the error. PTSfc03012: Standard(M3100) local probable cause values in integer form are being displayed as in the problem presenter. PHSS_27495: Consolidated Patch PHSS_27488: PTSfc02494: While issuing "mdcfgupd" command for 8 to 10 times successively, the mapper process exits. Subsequently, all other MD processes exit. PTSfc02515: Alarms of size >=2570 bytes are not being parsed properly and hence land up in the Unknown Log. PHSS_26440: Consolidated Patch PHSS_26432: PTSfc02498: Alarms are logged as Invalid in RAW LOG by the logger whenever Data Collector receives the header of the alarm in multiple chunks. PTSfc02479: During an alarm storm or restart of MD, FMS receives duplicate alarms. PTSfc02379: The fmsmhimport of object with RDN value lenght greater than 60 characters fails. PHSS_25809: Consolidated Patch PHSS_25803: PTSfc02031: The formatter will consume more CPU time while parsing an alarm with more than two consecutive ANY parsing patterns. PTSfc02327: RAW log file will be backed up by Logger during MD starup and the RAW_ALT will not be backed up. PTSfc02162: The Port specific fields in fmscfg utility doesn't accept more than 77 characters even though the size of the field has been defined as 255 characters. PHSS_25331: Consolidated Patch PHSS_25329: PTSfc01470: Lookup Table Default Value Mapping Problem PTSfc01767: The TCP data collectors are not re-spawned on failure for ever.When the TCP data collector (Supplied with the product) looses connection from the server, the data collector goes down. CCI will respawn the Data collector. This is supposed to be the method of reconnection when the data collector is running as a client.But in the customer environment, we are consistently seeing that the TCP data collector is not re-spawned consistently. The CCI will respawn the TCP data collector for several time, but the server port on the NE is not available for some reason for a long time, then the respawn stops. This could be specific with the Verizon environment as the number of TCP data collectors are more than 30.This behaviour is seen more often when more than one TCP data collector connections are lost.Currently, the data collectors are started using configuration update command 'mdcfgupd'. PTSfc02009: Enhancement required: To have an external API to the AS state m/c in the mapper to force-trigger the Alarm synchronization (AS) for a particular port. PTSfc02142: Supply Post AS phase perl scripts and other services as programming samples. PHSS_24600: PTSfc01648: Correlation does not work in case of Logical connectivity. PTSfc01680: Faulty behavior by HLP-Parser. PTSfc01805: Mapper exits when AS (Alarm Synchronization) feature is enabled for any port. PTSfc01806: During CHO testing the rs232 dc dumped core. The dump is not consistent. PTSfc01807: RS232DC dumps core when the configured pipe is not present. PTSfc01808: RS232 DC leaks memory. PTSfc01809: fmpmddc232d processes leak memory and uses most of CPU. PTSfc01810: TCP DC leaks memory, does not abort connect with small reinit timeout. PTSfc01814: If a DC is killed the Alarm synchronization logic goes out of synch. PTSfc01895: When dcapi sample is compiled, it fails displaying unresolved linker errors. PTSfc01896: Found during system testing. Defect Description: PHSS_28296: Cumulative Consolidated Patch Resolution: Cumulative Consolidated Patch PHSS_28289: PTSfc02692: When FMS is down and only MD is up, if the number of alarms received by IFMPS exceeds the maximum size of the buffer configured, the older alarms are over written. Resolution: The code has been modified in such a way that the maximum configurable value can be set to 99999. PTSfc02989: The mapper does not reload the config files oid.conf and fmpmap.conf when a dynamic config update command is issued. Resolution: The mapper code has been modified to reload the oid.conf and fmpmap.conf files during dynamic config update. PTSfc03012: Standard local probable cause values in integer form are treated as undefined. Resolution: Local probable cause values in integer form are handled to distinguish the standard ones from the undefined. PHSS_27495: Consolidated Patch PHSS_27488: PTSfc02494: When mdcfgupd is executed 8 to 10 times successively, the mapper process initializes some specific data structures without freeing the memory allocated previously. Subsequent memory allocations causes the memory to be corrupted and mapper exits. Resolution: The code has been modified in such a way that subsequent invocation of mdcfgupd does not corrupt the allocated memory. PTSfc02515: Alarms of size >=2570 bytes are not being parsed properly and hence land up in the Unknown Log,due to an internal memory error. Resolution: The code is changed to avoid the memory error (by increasing the failure stack size) PHSS_26440: Consolidated Patch PHSS_26432: PTSfc02498: The alarms, whose header is received in more than one read operation by the Data Collector are logged as Invalid Alarms. Resolution: The parser has been modified to take care of the above mentioned case. PTSfc02479: When MD looses connection with FMS and then reconnects, it resends some of the alarms that were sent before connection loss. Resolution: FMS is modified with information about the last alarm it received from the MD before connection loss. PTSfc02379: Importing objects with Attribute value excess of 60 chars using fmsmhimport fails and not seen in Map Presenter. Resolution: FMS binaries oemfmoihandlr,ovfmpeld,ovfmpmdimdd & fmscfg are modified to eliminate this problem. PHSS_25809: Consolidated Patch PHSS_25803: PTSfc02031: The formatter process was runs through an indefinite loop (consuming around 90% of CPU time) while parsing an alarm with consecutive ANY patterns in message parsing rules Resolution: The Parsing pattern for ANY pattern has been modified PTSfc02327: The Logger process doesn't take backup of RAW_ALT Log file during MD startup. Resolution: RAW_ALT file is backed up during startup. PTSfc02162: Port Specific fields in fmscfg utility does not accept more than 77 characters even though the size of the field has been defined as 255 characters Resolution: This problem was because of improper memory allocation. This was corrected and the variable initialized properly. PHSS_25331: Consolidated Patch PHSS_25329: PTSfc01470: Have looked at the zip file, seems like there are manual additionals to the table.conf file. PTSfc01767: The CCI process in MD is responsible to respawn the DCs when they fail.However if the attempt to respawn a DC fails, that particular DC will be marked as failed and will never be respawned again. This is the normal behavior of CCI. As far as TCP Client DCs are concerned, when the server goes down, the cient tries to re-connect 10 times sleeping 10s before each retry. If the connection could not be established CCI deems that the DC is dead and marks it as failed. At the customer site, since the server was down for a long time, respawn was failing. PTSfc02009: Enhancement requested. PTSfc02142: The enhancement can be supplied as programming samples in SA 1.02 patch-2 Resolution: PTSfc01470: I have checked the configuration with spaces 'ab c d' in the Table lookup, it works fine. The spaces are carried to the Problem Presenter.If you still have probs, send me your config and the alarms, so that I can check it out for you It seems like somebody has edited the table.conf file. The line in the LookupTbl.err which reads as BEGIN TABLE mtAXE10_Sp2Name LinkOrDest[S10]="",PortInstName[S10]="Nem tudom" "2-100", "BSC11" "2-101", "BSCNOR" is INCORRECT. It needs to read as BEGIN TABLE mtAXE10_Sp2Name LinkOrDest[S10]="",PortInstName[S10]="" "2-100", "Nem tudom" "2-101", "BSCNOR" The line after the BEGIN TABLE, just indicates if the field is a Printable string or an integer. Values must not be assigned at this point.I have checked with the column value being "Nem tudom", it seems to work fine. PS: From the swlist that you have sent, it seems like there are no OVC/SA patches installed in this machine. Could you please upgrade to 1.01-3 as well? PTSfc01767: A new optional port specific field is added for TCP DCs which will allow the user to specify whether he wants to re-spawn the DC continuously and if so how many times to retry. The field name will be "RetryCount". The possible filed values and DC behavior is mentioned below. Field Value DC behavior Example Field not present Retry 10 times (10 is default) -- Field Present, No value Retry till connect succeeds RetryCount Filed Present, Value 0 Retry till connect succeeds RetryCount="0" Filed Present, Value=X Retry X times RetryCount="X" (where X is non-zero). However, note that when the AlarmSync/Reinit feature is enabled, this field will be ignored. PTSfc02009: Not avilable PTSfc02142: Not available LinkOrDest[S10]="",PortInstName[S10]="Nem tudom" "2-100", "BSC11" "2-101", "BSCNOR" is INCORRECT. It needs to read as BEGIN TABLE mtAXE10_Sp2Name LinkOrDest[S10]="",PortInstName[S10]="" "2-100", "Nem tudom" "2-101", "BSCNOR" The line after the BEGIN TABLE, just indicates if the field is a Printable string or an integer. Values must not be assigned at this point.I have checked with the column value being "Nem tudom", it seems to work fine. PS: From the swlist that you have sent, it seems like there are no OVC/SA patches installed in this machine. Could you please upgrade to 1.01-3 as well? PTSfc01767: A new optional port specific field is added for TCP DCs which will allow the user to specify whether he wants to re-spawn the DC continuously and if so how many times to retry. The field name will be "RetryCount". The possible filed values and DC behavior is mentioned below. Field Value DC behavior Example Field not present Retry 10 times (10 is default) -- Field Present, No value Retry till connect succeeds RetryCount Filed Present, Value 0 Retry till connect succeeds RetryCount="0" Filed Present, Value=X Retry X times RetryCount="X" (where X is non-zero). However, note that when the AlarmSync/Reinit feature is enabled, this field will be ignored. PTSfc02009: Not avilable PTSfc02142: Not available LinkOrDest[S10]="",PortInstName[S10]="Nem tudom" "2-100", "BSC11" "2-101", "BSCNOR" is INCORRECT. It needs to read as BEGIN TABLE mtAXE10_Sp2Name LinkOrDest[S10]="",PortInstName[S10]="" "2-100", "Nem tudom" "2-101", "BSCNOR" The line after the BEGIN TABLE, just indicates if the field is a Printable string or an integer. Values must not be assigned at this point.I have checked with the column value being "Nem tudom", it seems to work fine. PS: From the swlist that you have sent, it seems like there are no OVC/SA patches installed in this machine. Could you please upgrade to 1.01-3 as well? PTSfc01767: A new optional port specific field is added for TCP DCs which will allow the user to specify whether he wants to re-spawn the DC continuously and if so how many times to retry. The field name will be "RetryCount". The possible filed values and DC behavior is mentioned below. Field Value DC behavior Example Field not present Retry 10 times (10 is default) -- Field Present, No value Retry till connect succeeds RetryCount Filed Present, Value 0 Retry till connect succeeds RetryCount="0" Filed Present, Value=X Retry X times RetryCount="X" (where X is non-zero). However, note that when the AlarmSync/Reinit feature is enabled, this field will be ignored. PTSfc02009: Not avilable PTSfc02142: Not available PHSS_24600: PTSfc01648: Correlation does not work in case of Logical connectivity. PTSfc01680: 1)Valid Alarms get clubbed together for a pair of begin- only patterns configured. 2)TCP/IP DC gets connection reset repeatedly for a pair of begin-end patterns configured. PTSfc01805: Memory corruption happens while handling the spontaneous alarms which leads mapper to dump core. PTSfc01806: When run for a long time with alarms pumped in continuously , RS232 DC exits non-consistently. PTSfc01807: RS232 DC exits when the RS232 device is configured as a non-existing pipe and AS is enabled. The dump is immediate. PTSfc01808: a. RS232 DC leaks 7 bytes memory everytime it receives AS/HB/Reset/Reinit requests. b. When the port specific scrpt uses a SouthBound device, for each alarm DC leaks 1024 bytes of memory. PTSfc01809: Resident memory size and CPU usage of fmpmddc232d processes keep increasing when invalid alarms are pumped continuously. PTSfc01810: TCP DC leaks memory everytime it receives AS/HB/Reset/Reinit request. When the Reinit timeout is small, and connection to NE fails, TCP DC keeps trying to connect. PTSfc01814: When DCs die and get respawned by CCI process, the state engine of mapper process with AS-enabled may be in different state which will lead to chaos. There should be a hand-shake mechanism between the mapper and cci so that mapper can reset the port objects of that DC which gets respawned. PTSfc01895: The library libctlmsgext.a has not been included in the libraries dependency. PTSfc01896: "fmscfg" doesn't handle the special characters (\ , ") properly in table entries. Resolution: PTSfc01648: The neShortname was not properly set for constructing the problem and therefore the problems were not macthing properly for logical connectivity cases. Now it is taken care of. PTSfc01680: The algorithms for Parse and Search routines changed and rewritten along with two new search routines. PTSfc01805: Memory corruption is resolved by changing the alarm list handling code. PTSfc01806: After receiving a RESET request from AS module, Check the validity of device fd before clearing it from the select mask. PTSfc01807: After receiving a RESET request from AS module, Check the validity of device fd before clearing it from the select mask. PTSfc01808: Added code to free memory when no longer needed. PTSfc01809: Added code to pass the buffer text as invalid to logger if no begin string/end string was found in buffer and no pattern is configured to have only an endstring. PTSfc01810: 1. Added code to free memory allocated to portname after processing the request from CCI. 2. Added code not to receive CCI messages between connection retries. PTSfc01814: The CCI detects the death of DCs. After detection it should send the death information to the Alarm synchronization module. Then CCI has to wait for the Alarm synchronization module to move all the Ports(under the DC) to an appropriate state as far as alarm synchronization is concerned. Once the CCI gets the acknowledgement from the Alarm synchronization module, it can go ahead and try to respawn the DC. PTSfc01895: The library is included in the Makefile of dcApi and also the library is placed under the prg-sample/lib path. PTSfc01896: The special characters(\ , ") should be escaped properly before writing into the configuration file. Enhancement: No SR: F333002989 F333002692 F333003012 F333002494 F333002515 F333002498 F333002379 F333002479 F333002327 F333002031 F333002162 F333001767 F333002142 F333001470 F333002009 F333001896 F333001808 F333001809 F333001810 F333001680 F333001648 F333001805 F333001814 F333001806 F333001895 F333001807 Patch Files: OVCA_mdRT.OVCAMD-API,fr=A.01.02,fa=HP-UX_B.11.00_32/64,v=HP: /opt/OEMF/V5.0/MD/prg-sample/README.ASTRIGGERAPI /opt/OEMF/V5.0/MD/prg-sample/post_as_customization/ CustomScript.pm /opt/OEMF/V5.0/MD/prg-sample/post_as_customization/ FMS_query.cc /opt/OEMF/V5.0/MD/prg-sample/post_as_customization/Makefile /opt/OEMF/V5.0/MD/prg-sample/post_as_customization/README /opt/OEMF/V5.0/MD/prg-sample/post_as_customization/ filter.conf /opt/OEMF/V5.0/MD/prg-sample/post_as_customization/util.cc /opt/OEMF/V5.0/MD/prg-sample/post_as_customization/util.hh /opt/OEMF/V5.0/MD/prg-sample/lib/libcfg.a /opt/OEMF/V5.0/MD/prg-sample/lib/libctlmsgext.a /opt/OEMF/V5.0/MD/prg-sample/lib/libhlpascii.a /opt/OEMF/V5.0/MD/prg-sample/include/astrigger.h /opt/OEMF/V5.0/MD/prg-sample/dcapi/Makefile OVCA_mdAUX.OVCAMD-AUX,fr=A.01.02,fa=HP-UX_B.11.00_32/64, v=HP: /opt/OEMF/V5.0/FMS/bin/fmscfg OVCA_mdRT.OVCAMD-RUN,fr=A.01.02,fa=HP-UX_B.11.00_32/64,v=HP: /opt/OEMF/V5.0/MD/bin/fmpmdccid /opt/OEMF/V5.0/MD/bin/fmpmddc232d /opt/OEMF/V5.0/MD/bin/fmpmddctcpd /opt/OEMF/V5.0/MD/bin/fmpmdevcd /opt/OEMF/V5.0/MD/bin/fmpmdformd /opt/OEMF/V5.0/MD/bin/fmpmdifmpsd /opt/OEMF/V5.0/MD/bin/fmpmdlogd /opt/OEMF/V5.0/MD/bin/fmpmdmapd /opt/OEMF/V5.0/MD/bin/fmpmdsnmpdcd what(1) Output: OVCA_mdRT.OVCAMD-API,fr=A.01.02,fa=HP-UX_B.11.00_32/64,v=HP: /opt/OEMF/V5.0/MD/prg-sample/README.ASTRIGGERAPI: None /opt/OEMF/V5.0/MD/prg-sample/post_as_customization/ CustomScript.pm: None /opt/OEMF/V5.0/MD/prg-sample/post_as_customization/ FMS_query.cc: None /opt/OEMF/V5.0/MD/prg-sample/post_as_customization/Makefile: None /opt/OEMF/V5.0/MD/prg-sample/post_as_customization/README: None /opt/OEMF/V5.0/MD/prg-sample/post_as_customization/ filter.conf: None /opt/OEMF/V5.0/MD/prg-sample/post_as_customization/util.cc: None /opt/OEMF/V5.0/MD/prg-sample/post_as_customization/util.hh: None /opt/OEMF/V5.0/MD/prg-sample/lib/libcfg.a: OpenView Communications / Assurance Library Function s to read and write MD configuration A.01.02 - Release (OFFICIALb136a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28296, 12042002 /opt/OEMF/V5.0/MD/prg-sample/lib/libctlmsgext.a: OpenView Communications / Assurance Library - class library for new inter module messages and se maphore related calls for DC_N_PIPE semaphor es- both features required for AS/HB enhance mnets A.01.02 - Release (OFFICIALb136a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28296, 12042002 /opt/OEMF/V5.0/MD/prg-sample/lib/libhlpascii.a: OpenView Communications / Assurance High Level Parse r for ASCII Pattern A.01.02 - Release (OFFIC IALb136a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28296, 12042002 /opt/OEMF/V5.0/MD/prg-sample/include/astrigger.h: None /opt/OEMF/V5.0/MD/prg-sample/dcapi/Makefile: None OVCA_mdAUX.OVCAMD-AUX,fr=A.01.02,fa=HP-UX_B.11.00_32/64, v=HP: /opt/OEMF/V5.0/FMS/bin/fmscfg: OpenView Communications / Assurance FMS Configurator A.01.02 - Release (OFFICIALb136a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28296, 12042002 OVCA_mdRT.OVCAMD-RUN,fr=A.01.02,fa=HP-UX_B.11.00_32/64,v=HP: /opt/OEMF/V5.0/MD/bin/fmpmdccid: OpenView Communications / Assurance Command Communic ation and Interpreter A.01.02 - Release (OFF ICIALb136a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28296, 12042002 FLEXlm 6.1g (liblmgr.a), Copyright (C) 1988-1999 Glo betrotter Software, Inc. /opt/OEMF/V5.0/MD/bin/fmpmddc232d: OpenView Communications / Assurance RS232 Data Colle ctor A.01.02 - Release (OFFICIALb136a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28296, 12042002 yaccpar 1.8 (Berkeley) 01/20/91 /opt/OEMF/V5.0/MD/bin/fmpmddctcpd: TCP/IP DC $Revision: /main/granby/13 $ OpenView Communications / Assurance TCP/IP Data Coll ector A.01.02 - Release (OFFICIALb136a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28296, 12042002 yaccpar 1.8 (Berkeley) 01/20/91 /opt/OEMF/V5.0/MD/bin/fmpmdevcd: OpenView Communications / Assurance Mediation Device Alarm Correlator A.01.02 - Release (OFFICIA Lb136a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28296, 12042002 /opt/OEMF/V5.0/MD/bin/fmpmdformd: OpenView Communications / Assurance Event Formatter A.01.02 - Release (OFFICIALb136a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28296, 12042002 /opt/OEMF/V5.0/MD/bin/fmpmdifmpsd: OpenView Communications / Assurance Interface to FMS A.01.02 - Release (OFFICIALb136a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28296, 12042002 DFIX15001: mp_error_m.c 23Dec99 DFIX15000: cii_ent.c 30sep1999 PATCH PHSS_20050, 990929 DFIX15000: pm_ipc.c 30sep1999 DFIX15001: x_comp.yacc 22Dec1999 /opt/OEMF/V5.0/MD/bin/fmpmdlogd: OpenView Communications / Assurance Event Logger A.0 1.02 - Release (OFFICIALb136a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28296, 12042002 /opt/OEMF/V5.0/MD/bin/fmpmdmapd: OpenView Communications / Assurance Event Mapper A.0 1.02 - Release (OFFICIALb136a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28296, 12042002 yaccpar 1.8 (Berkeley) 01/20/91 /opt/OEMF/V5.0/MD/bin/fmpmdsnmpdcd: OpenView Communications / Assurance SNMP Data Collec tor A.01.02 - Release (OFFICIALb136a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28296, 12042002 libovsnmp cksum(1) Output: OVCA_mdRT.OVCAMD-API,fr=A.01.02,fa=HP-UX_B.11.00_32/64,v=HP: 464119448 2153 /opt/OEMF/V5.0/MD/prg-sample/ README.ASTRIGGERAPI 3765309386 490 /opt/OEMF/V5.0/MD/prg-sample/dcapi/Makefile 2170717891 562 /opt/OEMF/V5.0/MD/prg-sample/include/ astrigger.h 3890217632 708892 /opt/OEMF/V5.0/MD/prg-sample/lib/libcfg.a 906829692 60020 /opt/OEMF/V5.0/MD/prg-sample/lib/ libctlmsgext.a 440118397 22152 /opt/OEMF/V5.0/MD/prg-sample/lib/ libhlpascii.a 2588221099 14012 /opt/OEMF/V5.0/MD/prg-sample/ post_as_customization/CustomScript.pm 3320602948 5399 /opt/OEMF/V5.0/MD/prg-sample/ post_as_customization/FMS_query.cc 3436956201 1410 /opt/OEMF/V5.0/MD/prg-sample/ post_as_customization/Makefile 2577131858 2808 /opt/OEMF/V5.0/MD/prg-sample/ post_as_customization/README 1034380113 116 /opt/OEMF/V5.0/MD/prg-sample/ post_as_customization/filter.conf 4171280392 35685 /opt/OEMF/V5.0/MD/prg-sample/ post_as_customization/util.cc 2530194451 6932 /opt/OEMF/V5.0/MD/prg-sample/ post_as_customization/util.hh OVCA_mdAUX.OVCAMD-AUX,fr=A.01.02,fa=HP-UX_B.11.00_32/64, v=HP: 1309155490 1884160 /opt/OEMF/V5.0/FMS/bin/fmscfg OVCA_mdRT.OVCAMD-RUN,fr=A.01.02,fa=HP-UX_B.11.00_32/64,v=HP: 3243009572 868352 /opt/OEMF/V5.0/MD/bin/fmpmdccid 3202288904 1859584 /opt/OEMF/V5.0/MD/bin/fmpmddc232d 3493309764 1875968 /opt/OEMF/V5.0/MD/bin/fmpmddctcpd 2640014140 1019904 /opt/OEMF/V5.0/MD/bin/fmpmdevcd 572498205 729088 /opt/OEMF/V5.0/MD/bin/fmpmdformd 1256031008 1753088 /opt/OEMF/V5.0/MD/bin/fmpmdifmpsd 3531693413 143360 /opt/OEMF/V5.0/MD/bin/fmpmdlogd 582325190 3444736 /opt/OEMF/V5.0/MD/bin/fmpmdmapd 1671707416 872448 /opt/OEMF/V5.0/MD/bin/fmpmdsnmpdcd Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_28289 PHSS_27495 PHSS_27488 PHSS_26440 PHSS_26432 PHSS_25809 PHSS_25803 PHSS_25331 PHSS_25329 PHSS_24600 Equivalent Patches: None Patch Package Size: 15020 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_28296 5. Run swinstall to install the patch: swinstall -x autoreboot=true -x patch_match_target=true \ -s /tmp/PHSS_28296.depot By default swinstall will archive the original software in /var/adm/sw/save/PHSS_28296. 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_28296.text file is available in the product readme: swlist -l product -a readme -d @ /tmp/PHSS_28296.depot To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_28296.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: PHSS_28296: Please follow the instructions mentioned below while installing the MD patch. Stop the MD using 'mdstop' utility. Install the Patch. Start the MD using 'mdstart' utility. PHSS_27488: PTSfc2515: None