Patch Name: PHSS_28045 Patch Description: s700_800 11.00 OV SA1.01 MD Patch-10 Creation Date: 02/10/25 Post Date: 02/11/18 Hardware Platforms - OS Releases: s700: 11.00 s800: 11.00 Products: OpenView Service Assurance 1.01 MD Filesets: OVCA_mdRT.OVCAMD-API,fr=A.01.01,fa=HP-UX_B.11.00_32/64,v=HP OVCA_mdAUX.OVCAMD-AUX,fr=A.01.01,fa=HP-UX_B.11.00_32/64,v=HP OVCA_mdRT.OVCAMD-RUN,fr=A.01.01,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_28045 Symptoms: PHSS_28045: Cumulative Consolidated Patch PHSS_28044: 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. 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. PTSfc02479: During an alarm storm or restart of MD, FMS receives duplicate alarms. PHSS_26174: Consolidated Patch PHSS_26168: 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_25576: Consolidated Patch PHSS_25575: PTSfc02031 The formatter process was running through an indefinite loop when an alarm with a particular format is sent Say, the alarm extraction pattern has more than two consecutive ANY patterns of size 255 bytes each and an alarm satisfies this pattern PHSS_24896: Consolidated Patch PHSS_24890: PTSfc01470: Lookup Table Default Value Mapping Problem Trouble Report ============== Issue 12: Lookup Table Default Value Mapping Problem Peter Sagi Westel NIS 02/19/2001 In case of AXE MSC alarm mapping a look-up table is used for mapping the name of the links for link alarms. When the default value of the look-up table contains space(es), only a part of the default value is mapped (up to and not including the first space). Find attached the ASCII dump of the problem (PresDump.err) and check the end of the FDN. The last part (the value of the ItpPort naming attribute) should be 'Nem tudom' instead of just 'Nem'. Please also check the look-up table (LookupTbl.err) extracted from the configuration file table.conf. There are also files (presenter dump and look-up table extract) for another configuration. In that case the default value contains no spaces, so the error does not appear. The error symptom is independent from other circumstances, that is in other cases when using look-up table for mapping it appears. $ diff LookupTbl.OK LookupTbl.err 2c2 < LinkOrDest[S10]='',PortInstName[S10]='Unknown' --- > LinkOrDest[S10]='',PortInstName[S10]='Nem tudom' 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'. PTSfc01805: State the problem symptom(s): "fmscfg" doesn't handle the special characters (\ , ") properly in table entries Describe how to reproduce the problem symptom(s): Case-1 ------ To create an entry like: nmsc"4 in some table, user has to specify this in fmscfg like: nmsc\"4 otherwise it will be saved as: nmsc *** same is the case for '\' character. Case-2 ------ i) entry in table is specified like: msc\"4 ii) save and exit from fmscfg iii) run fmscfg again iv) the entry in step (i) will appear as: nmsc"4 v) make some other changes and save again. vi) run fmscfg vii) the entry in step (i) will appear as: nmsc *** similar behavior is observed with '\' character. Describe user's site system configuration and operating system - HP-UX 11.x Frequency of product problem symptom(s) - Happens always. PHSS_24367: Consolidated Patch PHSS_24359: PTSfc01648: Correlation does not work in case of Logical connectivity. PTSfc01680: Faulty behavior by HLP-Parser PTSfc01732: fmpmdevcd incorrectly references $FMSVAR directory. PHSS_23761: Consolidated Patch PHSS_23751: PTSfc01476: When only the MD is running and the fmpmdevcd is required to dump correlation info, it writes to the ovfmpevcd.log file (FMS log). PHSS_23380: PTSfc01015: Mapper Core dumps. Defect Description: PHSS_28045: Cumulative Consolidated Patch Resolution: Cumulative Consolidated Patch PHSS_28044: 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 internal memory error. Resolution: The code is changed to avoid the memory error (by increasing the failure stack size) 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. Resolution: The code has been modified in such a way that the maximum configurable value can be set to 99999. PTSfc02479: When MD loses connection with FMS and then reconnects, or MD is restarted, MD resends some of the alarms that were sent before the connection was lost. Resolution: The binaries ovfmpmdimdd and fmpmdifmpsd are changed to solve this problem. PHSS_26174: Consolidated Patch PHSS_26168: 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_25576: Consolidated Patch PHSS_25575: PTSfc02031 : The formatter process was running through an indefinite loop when an alarm with a particular format is sent Resolution: The Parsing pattern for ANY pattern has been modified PHSS_24896: Consolidated Patch PHSS_24890: 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. PTSfc01805: fmscfg utility doesn't handle the special charaters like \," properly. Resolution: 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. PTSfc01805: The Special Characters like Backslash(\), Comma(,) and Double Quote(") should be escaped properly before writing into the configuration file. PHSS_24367: Consolidated Patch PHSS_24359: 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. PTSfc01732: fmpmdevcd incorrectly references $FMSVAR directory. 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. PTSfc01732: The MD side code has been taken care of not to use the FMSVAR directory any more. PHSS_23761: Consolidated Patch PHSS_23751: PTSfc01476: When only the MD is running and the fmpmdevcd is required to dump correlation info, it writes to the ovfmpevcd.log file (FMS log). Resolution: PTSfc01476: The executable was linking to the wrong library.This has been fixed to link to the correct shared library. PHSS_23380: PTSfc01015: In Table-lookup mapping configuration if an input column value is specified that is not a formatted fault field of the message class then the mapper process of MD dumps when the alarms of the message class are sent to MD. Resolution: PTSfc01015: Checked for an input column name, against the list of formatted fields for the message received and if found absent then the message is discarded with adequate trace messages. Enhancement: No SR: F333002692 F333002515 F333002494 F333002479 F333002162 F333002031 F333001767 F333001470 F333001805 F333001680 F333001648 F333001732 F333001476 F333001015 Patch Files: OVCA_mdRT.OVCAMD-API,fr=A.01.01,fa=HP-UX_B.11.00_32/64,v=HP: /opt/OEMF/V5.0/MD/prg-sample/lib/libcfg.a /opt/OEMF/V5.0/MD/prg-sample/lib/libhlpascii.a OVCA_mdAUX.OVCAMD-AUX,fr=A.01.01,fa=HP-UX_B.11.00_32/64, v=HP: /opt/OEMF/V5.0/FMS/bin/fmscfg OVCA_mdRT.OVCAMD-RUN,fr=A.01.01,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.01,fa=HP-UX_B.11.00_32/64,v=HP: /opt/OEMF/V5.0/MD/prg-sample/lib/libcfg.a: OpenView Communications / Assurance Library Function s to read and write MD configuration A.01.01 - Release (T42a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28045, 10252002 /opt/OEMF/V5.0/MD/prg-sample/lib/libhlpascii.a: OpenView Communications / Assurance High Level Parse r for ASCII Pattern A.01.01 - Release (T42a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28045, 10252002 OVCA_mdAUX.OVCAMD-AUX,fr=A.01.01,fa=HP-UX_B.11.00_32/64, v=HP: /opt/OEMF/V5.0/FMS/bin/fmscfg: OpenView Communications / Assurance FMS Configurator A.01.01 - Release (T42a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28045, 10252002 OVCA_mdRT.OVCAMD-RUN,fr=A.01.01,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.01 - Release (T42 a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28045, 10252002 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.01 - Release (T42a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28045, 10252002 /opt/OEMF/V5.0/MD/bin/fmpmddctcpd: TCP/IP DC $Revision: 1.3 $ OpenView Communications / Assurance TCP/IP Data Coll ector A.01.01 - Release (T42a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28045, 10252002 /opt/OEMF/V5.0/MD/bin/fmpmdevcd: OpenView Communications / Assurance Mediation Device Alarm Correlator A.01.01 - Release (T42a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28045, 10252002 ECS.c $Revision: 1.9 $ $Date: 1998/04/22 23:30:06 $ ECS 3.0 (A.03.00) ECS REV: 980915.1306(opt) HP-UX B.11.00 5.0 eventio.c $Revision: 1.37 $ $Date: 1998/05/18 04:14: 16 $ sockstack.c $Revision: 1.68 $ $Date: 1998/06/09 01:1 6:51 $ container.c $Revision: 1.17 $ $Date: 1998/02/18 00:4 9:18 $ trace.c $Revision: 1.12 $ $Date: 1998/03/12 04:48:38 $ fatal.c $Revision: 1.13 $ $Date: 1998/05/07 02:26:33 $ log.c $Revision: 1.7 $ $Date: 1997/07/04 07:34:11 $ mesgbuf.c $Revision: 1.18 $ $Date: 1998/05/07 00:28: 35 $ /opt/OEMF/V5.0/MD/bin/fmpmdformd: OpenView Communications / Assurance Event Formatter A.01.01 - Release (T42a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28045, 10252002 /opt/OEMF/V5.0/MD/bin/fmpmdifmpsd: OpenView Communications / Assurance Interface to FMS A.01.01 - Release (T42a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28045, 10252002 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.01 - Release (T42a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28045, 10252002 /opt/OEMF/V5.0/MD/bin/fmpmdmapd: OpenView Communications / Assurance Event Mapper A.0 1.01 - Release (T42a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28045, 10252002 /opt/OEMF/V5.0/MD/bin/fmpmdsnmpdcd: OpenView Communications / Assurance SNMP Data Collec tor A.01.01 - Release (T42a) HP 9000 S700/S800 HP-UX 11.x ANSI C++ (+eh) Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri ghts Reserved. PATCH PHSS_28045, 10252002 libovsnmp cksum(1) Output: OVCA_mdRT.OVCAMD-API,fr=A.01.01,fa=HP-UX_B.11.00_32/64,v=HP: 225431692 709400 /opt/OEMF/V5.0/MD/prg-sample/lib/libcfg.a 3267748641 21556 /opt/OEMF/V5.0/MD/prg-sample/lib/ libhlpascii.a OVCA_mdAUX.OVCAMD-AUX,fr=A.01.01,fa=HP-UX_B.11.00_32/64, v=HP: 3141923447 1880064 /opt/OEMF/V5.0/FMS/bin/fmscfg OVCA_mdRT.OVCAMD-RUN,fr=A.01.01,fa=HP-UX_B.11.00_32/64,v=HP: 2039725450 835584 /opt/OEMF/V5.0/MD/bin/fmpmdccid 692918483 458752 /opt/OEMF/V5.0/MD/bin/fmpmddc232d 4259881845 475136 /opt/OEMF/V5.0/MD/bin/fmpmddctcpd 864564758 999424 /opt/OEMF/V5.0/MD/bin/fmpmdevcd 3089043533 712704 /opt/OEMF/V5.0/MD/bin/fmpmdformd 3759422429 1753088 /opt/OEMF/V5.0/MD/bin/fmpmdifmpsd 2595941025 131072 /opt/OEMF/V5.0/MD/bin/fmpmdlogd 3938955482 1835008 /opt/OEMF/V5.0/MD/bin/fmpmdmapd 997626717 860160 /opt/OEMF/V5.0/MD/bin/fmpmdsnmpdcd Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_28044 PHSS_26174 PHSS_26168 PHSS_25576 PHSS_25575 PHSS_24896 PHSS_24890 PHSS_24367 PHSS_24359 PHSS_23761 PHSS_23751 PHSS_23380 Equivalent Patches: None Patch Package Size: 10470 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_28045 5. Run swinstall to install the patch: swinstall -x autoreboot=true -x patch_match_target=true \ -s /tmp/PHSS_28045.depot By default swinstall will archive the original software in /var/adm/sw/save/PHSS_28045. 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_28045.text file is available in the product readme: swlist -l product -a readme -d @ /tmp/PHSS_28045.depot To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_28045.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: PHSS_28044: PTSfc2494: None PTSfc2515: None PTSfc02692:None PTSfc02479:None PHSS_25575: None PHSS_24890: Stop the MD. Install the Patch. Start the MD. PHSS_24359: Stop the MD. Install the Patch. Start the MD. PHSS_23751: Stop MD using mdstop. Install the Patch. Start MD using mdstart. PHSS_23380: Stop MD using mdstop. Install the patch Start MD using the mdstart.