|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
HP-UX series 700 11.X patch digest
From: IT Resource Center (support_feedback
us-support2-mail.external.hp.com)
Date: Tue May 27 2003 - 12:42:29 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
HP Support Information Digests
===============================================================================
o IT Resource Center World Wide Web Service
---------------------------------------------------
If you subscribed through the IT Resource Center and would
like to be REMOVED from this mailing list, access the
IT Resource Center on the World Wide Web at:
http://support.itrc.hp.com/
Login using your IT Resource Center User ID and Password.
Then select Support Information Digests (located under
Maintenance and Support). You may then unsubscribe from the
appropriate digest.
To download a patch referenced below, access the
IT Resource Center on the World Wide Web at:
http://support.itrc.hp.com/
Login using your IT Resource Center User ID and Password.
Then select Individual Patches (under Maintenance and Support)
to access the patch. You may also download a patch via anonymous
ftp(1) from ftp.itrc.hp.com.
===============================================================================
Digest Name: weekly HP-UX series 700 11.X patch digest
Created: Sun May 25 7:05:42 EDT 2003
Table of Contents:
Document ID Title
--------------- -----------
PHSS_28803 s700_800 11.04 Virtualvault 4.6 TGP Logging Enhancement
PHSS_28989 s700_800 11.00 OV DM5.03 Intermediate Patch April 2003
PHSS_28739 s700_800 11.X OV OB4.10 patch - CC packet
PHCO_28656 s700_800 11.X VERITAS Enterprise Administrator Patch
PHCO_28651 s700_800 11.X VERITAS Enterprise Administrator Srvc Patch
PHNE_28606 s700_800 11.00 3.10.01 ACC X.25/9000 Link S/W Patch
PHCO_25514 s700_800 11.00 libnss_files cumulative patch
PHCO_28563 s700_800 11.00 pwgrd(1M) cumulative patch
PHSS_28547 s700_800 11.11 AudioSubsystem Periodic Patch
PHSS_28548 s700_800 11.11 AudioDevKit 2003 Periodic Patch
PHCO_27415 s700_800 11.11 ls(1) cumulative patch
PHKL_28999 s700_800 11.11 getmount_entry;rename;creat;[u]mount;VxFS3.5
PHKL_29039 s700_800 11.11 SCSI IO Cumulative Patch
PHKL_29041 s700_800 11.00 SCSI IO Subsystem Cumulative Patch
PHSS_28736 s700_800 11.X OV DP5.00 patch - CS packet
PHSS_28737 s700_800 11.X OV DP5.00 patch - INFORMIX packet
PHSS_28863 s700_800 11.00 OV ITO6.0X Solaris Agent Patch A.06.15
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHSS_28803
Date Loaded: 20030523
Title: s700_800 11.04 Virtualvault 4.6 TGP Logging Enhancement
Patch Name: PHSS_28803
Patch Description: s700_800 11.04 Virtualvault 4.6 TGP Logging Enhancement
Creation Date: 03/05/15
Post Date: 03/05/23
Hardware Platforms - OS Releases:
s700: 11.04
s800: 11.04
Products:
Virtualvault A.04.60
Filesets:
VaultTGP.TGP-CORE,fr=A.04.60,fa=HP-UX_B.11.04_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_28803
Symptoms:
PHSS_28803:
1. Provide enhanced verbose logging for TGP.
2. When SSL is enabled, tgp deemon may exhibit unexpected
behavior.
PHSS_27637:
1. When IP aliasing is configured, trying to create/modify
TGP service entries through 'Trusted Gateway Proxy
Administration' screen results in an error,
"Sufficient memory can not be allocated to create the
CREATE screen."
The same kind of error occurs while trying to modify a
TGP service entry.
2. When SSL is enabled, tgp daemon may exhibit unexpected
behavior.
Defect Description:
PHSS_28803:
1. Provide enhanced verbose logging for TGP.
2. When SSL is enabled, tgp deemon may exhibit unexpected
behavior.
Resolution:
1. TGP logging enhancement has been provided.
2. Migrated OpenSSL version of TGP to 0.9.6j.
PHSS_27637:
1. The tgp-edit cgi fails to fetch the MAC label for a lan
interface when that interface is configured with multiple
IP addresses (IP aliasing).
2. When SSL is enabled, tgp daemon may exhibit unexpected
behavior.
Resolution:
1. Since the MAC label associated with a lan interface must
be the same for all aliases of that interface, query the
interface without the alias name (use lan0 instead of
lan0:1).
2. TGP daemon has been built with OpenSSL version 0.9.6e to
fix the problem.
Enhancement:
No
SR:
8606272389 8606270675 8606298161 8606311448
Patch Files:
VaultTGP.TGP-CORE,fr=A.04.60,fa=HP-UX_B.11.04_32/64,v=HP:
/var/opt/vaultTS/inside/vault/bin/tgp-edit
/tcb/lib/tgpd
what(1) Output:
VaultTGP.TGP-CORE,fr=A.04.60,fa=HP-UX_B.11.04_32/64,v=HP:
/var/opt/vaultTS/inside/vault/bin/tgp-edit:
$Source: src/admin/cgi/tgp-edit/tgp-edit.c, vaultTGP
, vaultTGP_4.6 $ $Date: 02/08/22 13:01:31 $
$Revision: 1.8.1.12 PATCH_11.04 (PHSS_27637)
$
/tcb/lib/tgpd:
$Source: src/tgproxy/main.c, vaultTGP, vaultTGP_4.6
$ $Date: 03/05/15 08:43:01 $ $Revision: 1.17
.1.1 PATCH_11.04 (PHSS_28803) $
$Source: src/tgproxy/configuration.c, vaultTGP, vaul
tTGP_4.6 $ $Date: 03/05/15 08:42:39 $ $Revis
ion: 1.8.3.1 PATCH_11.04 (PHSS_28803) $
$Source: src/tgproxy/proxy.c, vaultTGP, vaultTGP_4.6
$ $Date: 03/05/15 08:43:22 $ $Revision: 1.1
0.3.1 PATCH_11.04 (PHSS_28803) $
$Source: src/tgproxy/tgp_audit.c, vaultTGP, vaultTGP
_4.6 $ $Date: 03/05/15 08:45:15 $ $Revision:
1.7 PATCH_11.04 (PHSS_28803) $
HP VirtualVault, tgpd, revision A.04.60
cksum(1) Output:
VaultTGP.TGP-CORE,fr=A.04.60,fa=HP-UX_B.11.04_32/64,v=HP:
3500358800 78055 /var/opt/vaultTS/inside/vault/bin/tgp-edit
216287803 1188178 /tcb/lib/tgpd
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_27637
Equivalent Patches:
PHSS_28802:
s700: 11.04
s800: 11.04
Patch Package Size: 560 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_28803
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_28803.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_28803. 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_28803.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_28803.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_28803.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_27637:
The patch installation replaces the Trusted Gateway
Proxy Daemon (tgpd). Use the 'Start or Stop Trusted
Gateway Proxy' interface to stop the daemon before
installing the patch and to restart it after installing
the patch. In the event that the TGP daemon is not
stopped prior to this patch installation, the daemon
will be terminated.
-----End of Document ID: PHSS_28803------------------------------------------
Document ID: PHSS_28989
Date Loaded: 20030522
Title: s700_800 11.00 OV DM5.03 Intermediate Patch April 2003
Patch Name: PHSS_28989
Patch Description: s700_800 11.00 OV DM5.03 Intermediate Patch April 2003
Creation Date: 03/05/20
Post Date: 03/05/22
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products:
OpenView Distributed Management 5.03
Filesets:
DMAgent.OVEMS-LOG,fr=B.05.03,fa=HP-UX_B.10.00_700/800,v=HP
DMAgent.OVEMS-RUN,fr=B.05.03,fa=HP-UX_B.10.00_700/800,v=HP
DMAgentDevKit.OVDM-XMPv7-PRG,fr=B.05.03,fa=HP-UX_B.10.00_700/800,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_28989
Symptoms:
PHSS_28989:
PTSfc02901 : The Error logging is improper when the fork
fails.
PTSfc03088 : Build error occurred while using libxmpV7.a
library
PTSfc03102 : In ovlad log object files, record IDs are not
sequential.
PTSfc03095 : get request on corrupted log for scope level
2 request leads to blocking
Defect Description:
PHSS_28989:
PTSfc02901 : fork() failure does not log error messages
as the error handling code never gets
executed.
Resolution:
The Resolution is HP proprietary.
PTSfc03088: When compiling an application using
libxmpV7.a library, following "undefined
symbol" error occurred.mpP_handle_replies
-- referenced in the text segment of
/opt/OV/lib/libxmpV7.a (mp_set_req.o).
LibxmpV7.a archive library was not build
properly
Resolution:
The Resolution is HP proprietary.
PTSfc03102 : In ovlad flatfile version, log record ID
will not be sequential. When the log object
file is full, and in wrap around case,
ovlad doesn't maintain the sequential
numbers. Instead, it skips some numbers
in-between.
Resolution:
The Resolution is HP proprietary.
PTSfc03095 : ovlad sends the error message on corrupted
log for scope level 2 get request without
sending confirmation message to pmd.
pmd waits for confirmation and application
blocks.
Resolution:
The Resolution is HP proprietary.
Enhancement:
No
SR:
F333003088 F333002901 F333003102 F333003095
Patch Files:
DMAgent.OVEMS-LOG,fr=B.05.03,fa=HP-UX_B.10.00_700/800,v=HP:
/opt/OV/bin/ovladdb
/opt/OV/bin/ovladff
DMAgent.OVEMS-RUN,fr=B.05.03,fa=HP-UX_B.10.00_700/800,v=HP:
/opt/OV/bin/ovead
DMAgentDevKit.OVDM-XMPv7-PRG,fr=B.05.03,
fa=HP-UX_B.10.00_700/800,v=HP:
/opt/OV/lib/libxmpV7.a
what(1) Output:
DMAgent.OVEMS-LOG,fr=B.05.03,fa=HP-UX_B.10.00_700/800,v=HP:
/opt/OV/bin/ovladdb:
PATCH PHSS_24061, DM5.03 Consolidated Patch (Apr 200
1)
PATCH PHSS_23827, DM5.03 Intermediate Patch (Apr 200
1)
PATCH PHSS_16122, DM5.03 Consolidated Patch (Aug 199
8)
PATCH PHSS_16859, DM5.03 Consolidated patch Nov1998
HP OpenView Event Log Agent (ODBC Based) DM Release
A.05.03
HP 9000 S700/S800 HP-UX 10.x OpenView version Apr 1
4 2003
Copyright (c) 1990-2003 Hewlett-Packard Company
DFIX9027: acse_util.c 16Nov99
DFIX9017 acse_util.c 18Jun1999
DFIX9012 acse_util.c 28Jan1999
DFIX9066: acse_assoc.c 08Nov2001
DFIX9027: acse_assoc.c 16Nov99
DFIX9004: acse_assoc.c 12May98
PATCH PHSS_20460, 991120
PATCH PHSS_15213, 980511
PATCH PHSS_20460, 991120
PATCH PHSS_18263, 990415
DFIX9027: acse_bind.c 16Nov99
DFIX9015 acse_bind.c 15Apr1999
DFIX9027: acse_mgr.c 16Nov99
DFIX9027: om_opi_stack.c 16Nov99
DFIX9089: om_opi_stack.c 09July2002
DFIX9087: om_opi_stack.c 09July2002
DFIX9022: om_opi_stack.c 08Oct99
DFIX9038: om_action_request.c 08Mar00
DFIX9027: om_action_request.c 16Nov99
PATCH PHSS_21238, 000308
DFIX9091 : om_common.c 19Aug2002
DFIX9010: om_create_request.c 12Nov1998
DFIX9099 : om_get_request.c 24March2003
DFIX9089 : om_get_request.c 09July2002
DFIX9087 : om_get_request.c 09July2002
DFIX9038: om_set_request.c 08Mar00
DFIX9002: om_set_request.c 20Apr98
PATCH PHSS_22444, 000921
DFIX9064: stx_check_obj.c 3rd August 2001
DFIX9061: stx_check_obj.c 24Apr2001
DFIX9051: stx_check_obj.c 14Dec2000
DFIX9046: stx_check_obj.c 03Oct00
DFIX9038: stx_check_obj.c 08Mar00
DFIX9010: stx_check_obj.c 12Nov1998
DFIX9003: stx_check_obj.c 24apr1998
PATCH PHSS_18263, 990415
DFIX9054: om_process_attributeList.c 29Jan2001
DFIX9029: om_process_attributeList.c Nov191999
DFIX9015: om_process_attributeList.c 26Apr1999
DFIX9010: om_process_attributeList.c 12Nov1998
DFIX9054:om_process_modificationList.c 29Jan2001
DFIX9054 :dtd.c,23 Jan 2001
PATCH PHSS_21238, 000309
DFIX9044: struct.c 30Aug2000
DFIX9036 struct.c 21 Feb 2000
DFIX9044: list.c 30Aug2000
DFIX9097 codec.c 24Oct2002
DIFX9009 codec.c 15Oct1998
DFIX9086:dtd_code.c,17 May 2002
DFIX9047:dtd_code.c,13 Oct 2000
DFIX9027: leh_reconf.c 16Nov99
DFIX9017: leh_reconf.c 20Jul1999
DFIX9092 leh_log.c 19Aug2002
DFIX9090 leh_log.c 19Aug2002
DFIX9070 leh_log.c 18Jan2002
DFIX9025 leh_log.c 15Nov1999
DFIX9068: opi_sock.c 17Jan2002
DFIX9019: opi_sock.c 25Aug99
DFIX9062: opi_sock_util.c 19Apr2001
DFIX9019: opi_sock_util.c 25Aug99
PATCH PHSS_20108, 991011
PATCH PHSS_19638, 990825
DFIX9022: pm_ipc.c 08Oct99
DFIX9019: pm_ipc.c 25Aug99
DFIX9001: pm_ipc.c 20Apr98
DFIX9085 pm_dsm.c 15/5/2002
DFIX9012 pm_indicate.c 28Jan1999
DFIX9056: pm_init.c 22Mar01
DFIX9033: pm_init.c 28Mar00
DFIX9027: pm_init.c 16Nov99
PATCH PHSS_20460, 991120
PATCH PHSS_17424, 990118
PATCH PHSS_14693, 980402
PATCH PHSS_18957, DM5.03 Consolidated patch July1999
PATCH PHSS_20462, DM5.03 Consolidated patch Nov1999
PATCH PHSS_21240, DM5.03 Consolidated Patch Mar2000
PATCH PHSS_25190, 20010910
PATCH PHSS_26811,DM5.03 Intermediate Patch April 200
2
PATCH PHSS_27273,DM5.03 Intermediate Patch June 2002
PATCH PHSS_27665,DM5.03 Intermediate Patch September
2002
PATCH PHSS_27695,DM5.03 Consolidated Patch September
2002
PATCH PHSS_28988,DM5.03 Intermediate Patch May 2003
DFIX9010: pm_rq.c 12Nov1998
DFIX9095: pm_fork.c 02-Sep-2002
DFIX9060: pm_trace.c 03Apr2001
DFIX9027: inetaddr.c 16Nov99
DFIX9027: localaddr.c 16Nov99
DFIX9027: paddr.c 16Nov99
DFIX9034 apdu.c 03Feb2000
DFIX9010: sg.c 12Nov1998
DFIX9027: aconnect.c 16Nov99
DFIX9087 : sequent.c 09July2002
DFIX9025 maxsize.c 15Nov 1999
PATCH PHSS_17905, 990311
DFIX9013 rdbsql.c 11Mar1999
DFIX9025 dbinsert.c 19Nov1999
/opt/OV/bin/ovladff:
PATCH PHSS_24061, DM5.03 Consolidated Patch (Apr 200
1)
PATCH PHSS_23827, DM5.03 Intermediate Patch (Apr 200
1)
PATCH PHSS_16122, DM5.03 Consolidated Patch (Aug 199
8)
PATCH PHSS_16859, DM5.03 Consolidated patch Nov1998
HP OpenView Event Log Agent (Flat File Based) DM Rel
ease A.05.03
HP 9000 S700/S800 HP-UX 10.x OpenView version Apr 1
4 2003
Copyright (c) 1990-2003 Hewlett-Packard Company
DFIX9027: acse_util.c 16Nov99
DFIX9017 acse_util.c 18Jun1999
DFIX9012 acse_util.c 28Jan1999
DFIX9066: acse_assoc.c 08Nov2001
DFIX9027: acse_assoc.c 16Nov99
DFIX9004: acse_assoc.c 12May98
PATCH PHSS_20460, 991120
PATCH PHSS_15213, 980511
PATCH PHSS_20460, 991120
PATCH PHSS_18263, 990415
DFIX9027: acse_bind.c 16Nov99
DFIX9015 acse_bind.c 15Apr1999
DFIX9027: acse_mgr.c 16Nov99
DFIX9027: om_opi_stack.c 16Nov99
DFIX9089: om_opi_stack.c 09July2002
DFIX9087: om_opi_stack.c 09July2002
DFIX9022: om_opi_stack.c 08Oct99
DFIX9038: om_action_request.c 08Mar00
DFIX9027: om_action_request.c 16Nov99
PATCH PHSS_21238, 000308
DFIX9091 : om_common.c 19Aug2002
DFIX9010: om_create_request.c 12Nov1998
DFIX9099 : om_get_request.c 24March2003
DFIX9089 : om_get_request.c 09July2002
DFIX9087 : om_get_request.c 09July2002
DFIX9038: om_set_request.c 08Mar00
DFIX9002: om_set_request.c 20Apr98
PATCH PHSS_22444, 000921
DFIX9064: stx_check_obj.c 3rd August 2001
DFIX9061: stx_check_obj.c 24Apr2001
DFIX9051: stx_check_obj.c 14Dec2000
DFIX9046: stx_check_obj.c 03Oct00
DFIX9038: stx_check_obj.c 08Mar00
DFIX9010: stx_check_obj.c 12Nov1998
DFIX9003: stx_check_obj.c 24apr1998
PATCH PHSS_18263, 990415
DFIX9054: om_process_attributeList.c 29Jan2001
DFIX9029: om_process_attributeList.c Nov191999
DFIX9015: om_process_attributeList.c 26Apr1999
DFIX9010: om_process_attributeList.c 12Nov1998
DFIX9054:om_process_modificationList.c 29Jan2001
DFIX9054 :dtd.c,23 Jan 2001
PATCH PHSS_21238, 000309
DFIX9044: struct.c 30Aug2000
DFIX9036 struct.c 21 Feb 2000
DFIX9044: list.c 30Aug2000
DFIX9097 codec.c 24Oct2002
DIFX9009 codec.c 15Oct1998
DFIX9086:dtd_code.c,17 May 2002
DFIX9047:dtd_code.c,13 Oct 2000
DFIX9027: leh_reconf.c 16Nov99
DFIX9017: leh_reconf.c 20Jul1999
DFIX9092 leh_log.c 19Aug2002
DFIX9090 leh_log.c 19Aug2002
DFIX9070 leh_log.c 18Jan2002
DFIX9025 leh_log.c 15Nov1999
DFIX9068: opi_sock.c 17Jan2002
DFIX9019: opi_sock.c 25Aug99
DFIX9062: opi_sock_util.c 19Apr2001
DFIX9019: opi_sock_util.c 25Aug99
PATCH PHSS_20108, 991011
PATCH PHSS_19638, 990825
DFIX9022: pm_ipc.c 08Oct99
DFIX9019: pm_ipc.c 25Aug99
DFIX9001: pm_ipc.c 20Apr98
DFIX9085 pm_dsm.c 15/5/2002
DFIX9012 pm_indicate.c 28Jan1999
DFIX9056: pm_init.c 22Mar01
DFIX9033: pm_init.c 28Mar00
DFIX9027: pm_init.c 16Nov99
PATCH PHSS_20460, 991120
PATCH PHSS_17424, 990118
PATCH PHSS_14693, 980402
PATCH PHSS_18957, DM5.03 Consolidated patch July1999
PATCH PHSS_20462, DM5.03 Consolidated patch Nov1999
PATCH PHSS_21240, DM5.03 Consolidated Patch Mar2000
PATCH PHSS_25190, 20010910
PATCH PHSS_26811,DM5.03 Intermediate Patch April 200
2
PATCH PHSS_27273,DM5.03 Intermediate Patch June 2002
PATCH PHSS_27665,DM5.03 Intermediate Patch September
2002
PATCH PHSS_27695,DM5.03 Consolidated Patch September
2002
PATCH PHSS_28988,DM5.03 Intermediate Patch May 2003
DFIX9010: pm_rq.c 12Nov1998
DFIX9095: pm_fork.c 02-Sep-2002
DFIX9060: pm_trace.c 03Apr2001
DFIX9027: inetaddr.c 16Nov99
DFIX9027: localaddr.c 16Nov99
DFIX9027: paddr.c 16Nov99
DFIX9034 apdu.c 03Feb2000
DFIX9010: sg.c 12Nov1998
DFIX9094 : connect.c : 20Aug2002
DFIX9088 : connect.c : 09July2002
DFIX9087 : connect.c : 09July2002
DFIX9078 : connect.c : 09Apr2002
DFIX9063 : connect.c : 02Aug01
DFIX9027 : connect.c : 16Nov99
DFIX9073: create_log.c 02Mar02
DFIX9027: create_log.c 16Nov99
DFIX9016 create_log.c 19May99
DFIX9073 : delete_log.c : 02Mar02
DFIX9100 : create_rec.c : 03Apr03
DFIX9063 : create_rec.c : 02Aug01
DFIX9027: create_rec.c 16Nov99
DFIX9016 create_rec.c 19May99
DFIX9087 : sequent.c 09July2002
DFIX9070 sequent.c 18Jan2002
PATCH PHSS_18618, 990518
DFIX9016 status.c 19May99
DFIX9093 : arc.c : 20Aug2002
DFIX9077 : arc.c : 09Apr2002
DFIX9076 : arc.c : 08Apr2002
DFIX9074 : arc.c : 25Feb2002
DFIX9073 : arc.c : 02Mar2002
DFIX9072 : arc.c : 08Apr2002
DFIX9063 : arc.c : 02Aug01
DMAgent.OVEMS-RUN,fr=B.05.03,fa=HP-UX_B.10.00_700/800,v=HP:
/opt/OV/bin/ovead:
PATCH PHSS_24061, DM5.03 Consolidated Patch (Apr 200
1)
PATCH PHSS_23827, DM5.03 Intermediate Patch (Apr 200
1)
PATCH PHSS_16122, DM5.03 Consolidated Patch (Aug 199
8)
PATCH PHSS_16859, DM5.03 Consolidated patch Nov1998
HP OpenView Event Agent DM Release A.05.03
HP 9000 S700/S800 HP-UX 10.x OpenView version Apr 1
4 2003
Copyright (c) 1990-2003 Hewlett-Packard Company
DFIX9027: acse_util.c 16Nov99
DFIX9017 acse_util.c 18Jun1999
DFIX9012 acse_util.c 28Jan1999
DFIX9066: acse_assoc.c 08Nov2001
DFIX9027: acse_assoc.c 16Nov99
DFIX9004: acse_assoc.c 12May98
PATCH PHSS_20460, 991120
PATCH PHSS_15213, 980511
PATCH PHSS_20460, 991120
PATCH PHSS_18263, 990415
DFIX9027: acse_bind.c 16Nov99
DFIX9015 acse_bind.c 15Apr1999
DFIX9027: acse_mgr.c 16Nov99
DFIX9068: opi_sock.c 17Jan2002
DFIX9019: opi_sock.c 25Aug99
DFIX9062: opi_sock_util.c 19Apr2001
DFIX9019: opi_sock_util.c 25Aug99
PATCH PHSS_20108, 991011
PATCH PHSS_19638, 990825
DFIX9022: pm_ipc.c 08Oct99
DFIX9019: pm_ipc.c 25Aug99
DFIX9001: pm_ipc.c 20Apr98
DFIX9027: om_opi_stack.c 16Nov99
DFIX9089: om_opi_stack.c 09July2002
DFIX9087: om_opi_stack.c 09July2002
DFIX9022: om_opi_stack.c 08Oct99
DFIX9038: om_action_request.c 08Mar00
DFIX9027: om_action_request.c 16Nov99
PATCH PHSS_21238, 000308
DFIX9091 : om_common.c 19Aug2002
DFIX9010: om_create_request.c 12Nov1998
DFIX9099 : om_get_request.c 24March2003
DFIX9089 : om_get_request.c 09July2002
DFIX9087 : om_get_request.c 09July2002
DFIX9038: om_set_request.c 08Mar00
DFIX9002: om_set_request.c 20Apr98
PATCH PHSS_22444, 000921
DFIX9064: stx_check_obj.c 3rd August 2001
DFIX9061: stx_check_obj.c 24Apr2001
DFIX9051: stx_check_obj.c 14Dec2000
DFIX9046: stx_check_obj.c 03Oct00
DFIX9038: stx_check_obj.c 08Mar00
DFIX9010: stx_check_obj.c 12Nov1998
DFIX9003: stx_check_obj.c 24apr1998
PATCH PHSS_18263, 990415
DFIX9054: om_process_attributeList.c 29Jan2001
DFIX9029: om_process_attributeList.c Nov191999
DFIX9015: om_process_attributeList.c 26Apr1999
DFIX9010: om_process_attributeList.c 12Nov1998
DFIX9054:om_process_modificationList.c 29Jan2001
DFIX9054 :dtd.c,23 Jan 2001
PATCH PHSS_21238, 000309
DFIX9044: struct.c 30Aug2000
DFIX9036 struct.c 21 Feb 2000
DFIX9044: list.c 30Aug2000
DFIX9097 codec.c 24Oct2002
DIFX9009 codec.c 15Oct1998
DFIX9086:dtd_code.c,17 May 2002
DFIX9047:dtd_code.c,13 Oct 2000
DFIX9085 pm_dsm.c 15/5/2002
DFIX9012 pm_indicate.c 28Jan1999
DFIX9056: pm_init.c 22Mar01
DFIX9033: pm_init.c 28Mar00
DFIX9027: pm_init.c 16Nov99
PATCH PHSS_20460, 991120
PATCH PHSS_17424, 990118
PATCH PHSS_14693, 980402
PATCH PHSS_18957, DM5.03 Consolidated patch July1999
PATCH PHSS_20462, DM5.03 Consolidated patch Nov1999
PATCH PHSS_21240, DM5.03 Consolidated Patch Mar2000
PATCH PHSS_25190, 20010910
PATCH PHSS_26811,DM5.03 Intermediate Patch April 200
2
PATCH PHSS_27273,DM5.03 Intermediate Patch June 2002
PATCH PHSS_27665,DM5.03 Intermediate Patch September
2002
PATCH PHSS_27695,DM5.03 Consolidated Patch September
2002
PATCH PHSS_28988,DM5.03 Intermediate Patch May 2003
DFIX9010: pm_rq.c 12Nov1998
DFIX9095: pm_fork.c 02-Sep-2002
DFIX9060: pm_trace.c 03Apr2001
DFIX9027: inetaddr.c 16Nov99
DFIX9027: localaddr.c 16Nov99
DFIX9027: paddr.c 16Nov99
DFIX9034 apdu.c 03Feb2000
DFIX9010: sg.c 12Nov1998
DMAgentDevKit.OVDM-XMPv7-PRG,fr=B.05.03,
fa=HP-UX_B.10.00_700/800,v=HP:
/opt/OV/lib/libxmpV7.a:
PATCH PHSS_14693, 980402
PATCH PHSS_25190, 20010910
DFIX9065: cii_ent.c 13Sept2001
DFIX9019: cii_ent.c 25Aug99
DFIX9021: ch_get_rsp.c 20Sep99
DFIX9026: mp_error_m.c 11Nov99
PATCH PHSS_18263, 990415
DFIX9015: mp_receive.c 26Apr99
DFIX9010: mp_rel_req.c 12Nov98
DFIX9010: mp_rel_rsp.c 12Nov98
DFIX9011: dec_assAtt.c 04Jan1999
DFIX9011: dec_fcts.c 04Jan1999
DFIX9011: enc_obj.c 04Jan1999
PATCH PHSS_17290, 990104
PATCH PHSS_20460, 991120
DFIX9024: x_comp.yacc 12Nov1999
PATCH PHSS_15644, 980617
DFIX9005: x_comp_cla.c 17Jun1998
libXOM 1.9 (BULL S.A) 7/1/92
DFIX9027: iso_reg.c 16Nov99
PATCH PHSS_20460, 991120
DFIX9052 iso_reg.c 22Dec2000
DFIX9027: iso_dreg.c 16Nov99
DFIX9004: smf_defilt.c 12May1998
PATCH PHSS_15213, 980511
DFIX9052 smf_defflt.c 22Dec2000
PATCH PHSS_20108, 991011
PATCH PHSS_19638, 990825
DFIX9022: pm_ipc.c 08Oct99
DFIX9019: pm_ipc.c 25Aug99
DFIX9001: pm_ipc.c 20Apr98
cksum(1) Output:
DMAgent.OVEMS-LOG,fr=B.05.03,fa=HP-UX_B.10.00_700/800,v=HP:
2461527867 1477592 /opt/OV/bin/ovladdb
906794317 1313460 /opt/OV/bin/ovladff
DMAgent.OVEMS-RUN,fr=B.05.03,fa=HP-UX_B.10.00_700/800,v=HP:
574037718 895505 /opt/OV/bin/ovead
DMAgentDevKit.OVDM-XMPv7-PRG,fr=B.05.03,
fa=HP-UX_B.10.00_700/800,v=HP:
2868544963 1574236 /opt/OV/lib/libxmpV7.a
Patch Conflicts: None
Patch Dependencies:
s700: 11.00: PHSS_27696
s800: 11.00: PHSS_27696
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches:
PHSS_28988:
s700: 10.01 10.10 10.20
s800: 10.01 10.10 10.20
PSOV_03257:
sparcSOL: 2.4 2.5 2.6
Patch Package Size: 1810 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_28989
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_28989.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_28989. 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_28989.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_28989.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_28989.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
BEFORE LOADING THIS PATCH...
If there are any OV sessions running on either the
Management Station or on any Management Consoles,
these sessions need to be closed. The "ovstop"
command should then be executed.
WARNING : The patch will not install if any Network Node
Manager processes or DM processes are detected.
BACKUP ALL OpenView DIRECTORIES TO TAPE.
This pre-caution ensures that if you have problems
after installing the patch, you will be able to
restore your current state from tape.
NOTE : ovstart is NOT executed after the patch is loaded
You will need to manually run ovstart. Also, in order to
keep a history of the patches installed on your system
the post-install script will attempt to copy this
patch text file to /usr/OV/ReleaseNotes/patches
(or /opt/OV/ReleaseNotes/patches). Please make sure
this file is in /tmp before installation.
-----End of Document ID: PHSS_28989------------------------------------------
Document ID: PHSS_28739
Date Loaded: 20030521
Title: s700_800 11.X OV OB4.10 patch - CC packet
Patch Name: PHSS_28739
Patch Description: s700_800 11.X OV OB4.10 patch - CC packet
Creation Date: 03/05/07
Post Date: 03/05/21
Hardware Platforms - OS Releases:
s700: 11.00 11.11 11.20
s800: 11.00 11.11 11.20
Products:
OmniBackII A.04.10
Filesets:
OMNIBACK-II.OMNI-HPUX-P,fr=A.04.10,fa=HP-UX_B.11.00_32/64,v=HP
OMNIBACK-II.OMNI-OTHUX-P,fr=A.04.10,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release manual_dependencies
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_28739
Symptoms:
PHSS_28739:
Id = HSLco39535 SR: H555009430
Sanconf does not recognize device that does not
have the /dev/rmt/*mn file name standard.
Id = HSLco40532 SR: H555009862
When starting "omnir -mssql -barhost <host> -base
<basename>", restore ends with:
"Set '<basename>:0' not found. Most probably there
is a DNS configuration problem or one of the systems
is not in the same Cell Manager system."
Id = HSLco40559 SR: H555009877
Backup specification does not reflect correct
schedules.
Id = HSLco40563 SR: H555009880
GUI does not have the selection for the T3590 drive.
Id = HSLco40640 SR: H555009917
GUI ends abnormally when there are more than
100 tablespaces selected for Oracle8 backup
specification.
Id = HSLco40763 SR: H555009970
Mount Request window consumes up to 100% cpu on Unix.
Id = HSLco40839 SR: H555010002
Tape status is not displayed in the GUI.
Id = HSLco40855 SR: H555010015
Some messages in Monitor context are not displayed
properly on systems with Japanese localization.
Id = HSLco40890 SR: H555010038
Output of command "omnirpt -report session_devices"
cuts device name after 12 characters.
Id = HSLco40958 SR: H555010071
Windows XP clients are not shown in a list of
available clients when trying to configure a backup
of Disk Image objects (rawdisks).
Id = HSLco41076 SR: H555010138
Disk usage for DCBF directory appears incorrectly
in GUI.
Id = HSLco41182 SR: H555010190
OmniBack GUI ends abnormally after a failover in
cluster environment.
Id = HSLco41274 SR:H555010237
When executing:
"omnimm -disable_device <logical device>"
command, not all devices are disabled.
PHSS_28332:
Id = HSLco36395 SR: H555008639
Kanji "month" character is not displayed correctly in
the scheduler calendar control.
Id = HSLco36502 SR: H555008659
OmniBack II user is not able to change and save the
schedule-time specification of a backup datalist.
Id = HSLco37193 SR: H555008807
When backing up SAP integration with EMC split mirror
functionality, not all the SAP files are backed up.
Id = HSLco38141 SR: H555009022
Missing barcode from original media.
Id = HSLco38201 SR: H555009033
GUI is unable to select Lotus object backup version
for restore.
Id = HSLco38335 SR: H555009064
Japanese OmniBack II GUI displays truncated database
session messages.
Id = HSLco38443 SR: H555009111
GUI abnormally ends when accessing OmniBack II
event log.
Id = HSLco38505 SR: H555009147
Switching to Instant Recovery context randomly
displays some other context, when Cell Manager
is not configured for XP.
Id = HSLco38889 SR: H555009228
When creating a NDMP backup datalist, no valid hosts
can be selected to run pre/post-exec script in GUI.
Id = HSLco39130 SR: H555009286
Catalog binary file is deleted if original medium with
copy is recycled or exported. Importing the catalog
from copy medium is not possible.
Id = HSLco39326 SR: H555009339
Excluded directories are reselected in restore
context.
Id = HSLco39486 SR: H555009404
GUI started with "xomni -restore -debug 1-99"
ends abnormally when Informix server option in
Restore context is selected.
Id = HSLco39892 SR: H555009570
GUI does not allow blank hostname for local
pre/post-exec script.
Id = JAGae19133 SR: 8606254802
"BalanceNone"' option for SAP integration does
not work from GUI.
PHSS_27588:
Id = HSLco33238 SR:H555007372
Multiple messages:
"Memory copy mode activated"
appear in the session output during MS SQL backup
with the Fast Direct mode enabled.
Id = HSLco34581 SR:H555007993
"devbra" returns 'rewind on close' devices.
Id = HSLco35611 SR:H555008476
Restore GUI can not handle two separate Oracle7
database with the same SID. GUI does not display
all objects versions.
Id = HSLco36219 SR:H555008624
When viewing sessions in database context and then
switching context, GUI ends abnormally.
Id = HSLco36343 SR:H555008636
Statistics for DCBF directory are incorrect in GUI.
Id = HSLco36478 SR:H555008657
While attempting to restore an Informix Backup
GUI ends abnormally.
Id = HSLco36526 SR:B555014660
Sanconf does not distinguish between tape devices
having serial numbers longer than 10 digits.
Id = HSLco36751 SR:H555008700
Move client operation does not move the client from
one cell to another but returns the message that
selected client exists in all cells.
Id = HSLco36798 SR:H555008715
GUI does not respond when view is clicked in main menu.
Id = HSLco36983 SR:H555008752
Fields on notification page disappear after switching
contexts.
Id = HSLco36986 SR:H555008754
Report "Extended report on used media" gives wrong info
about used media in selected timeframe.
Id = HSLco36988 SR:H555008755
When saving a XP datalist or barlist created through
the GUI, the following message pops up:
"This backup will not start because the SureStore
Disk Array XP license is not available.".
Id = HSLco36998 SR:H555008757
When filesystem is chosen for restore error message
pops up:
"error: Error details unknown.".
Id = HSLco37094 SR:H555008779
Notifications script can be run from anywhere even
with ExternalScriptMode set to 1.
Id = HSLco37174 SR:H555008803
Menu item /Tools/Database Administration is grayed
out in MOM GUI.
Id = HSLco37359 SR:H555008849
OmniBack II GUI abnormally ends on exit.
Id = HSLco37939 SR:H555008927
While configuring OmniBack II reports using GUI only
datalists are listed (barlists are missing).
Id = JAGae12418 SR:8606245960
Backup GUI displays selection, which is inconsistent
with datalist.
Id = JAGae27939 SR:8606263614
GUI session restore picks the last version of file.
Id = JAGae36127 SR:8606271949
MS Exchange 2000 objects are not shown.
PHSS_26878:
Id = HSLco31458 SR:H555006839
When using "omnir -rawdisk", the following is reported:
"[Warning] From: RSM<host> "" Time:<time>
Following trees from <host>: <Label> session <ID>
were not found in database:
ToSection=Section".
Id = HSLco33515 SR:H555007485
After using CLI command omnimm -chkfreemedia
the following messages are logged in the debug.log
file:
"06/13/01 12:00:01 OMNIMM.10542.0
["lib/cmn/obstr.c /main/17":187] A.04.00 b364
StrToUserSessionId: "0": not in correct format
06/13/01 12:00:01 OMNIMM.10542.0
["lib/cmn/obstr.c /main/17":428] A.04.00 b364
StrFromObjectName: "Default LTO": no host/mpoint
delimiter"
Id = HSLco33578 SR:H555007518
Description and Location fields in select media dialog
box do not allow wildcards.
Id = HSLco33579 SR:H555007519
When browsing pre-allocation media list only hexID and
label are displayed. Other properties are missing.
Id = HSLco33645 SR:H555007546
"Point in time restore" restore option of
Transaction log backup in OmniBack II MSSQL
integration is not limited.
Id = HSLco33767 SR:H555007591
GUI crashes during browsing SQL 7 restore objects.
Id = HSLco34046 SR:H555007697
When device different from original device is selected
for restore, device is not changed and original device
is used for restore.
Id = HSLco34166 SR:H555007748
OmniBack II SSEA integration option
"Keep Version available for Instant Restore" for
Continuous Access XP and Combined
(Continuous Access XP + Business Copy XP)
is not supported, but is selectable.
Id = HSLco34174 SR:H555007752
"omnicellinfo -dlobj" ends abnormally.
Id = HSLco34683 SR:H555008049
If xomni is started with -cde option, characters on
tabs in the results area are not readable.
Id = JAGad92807 SR:8606223711
The current link in the Info menu is labeled
'OmniBack II FAQ' and it points to:
http://ovweb3.external.hp.com/ovfaq
Id = NSMbb44613 SR:B555013242
The OmniBack II GUI startup performance is poor
on HP-UX systems.
Id = HSLco34610 SR:H555008004
When GUI does not get MSSQL instances properly and user
enters the instance manually by typing, GUI instead of
proceeding asks for instance configuration.
Id = HSLco34641 SR:H555008020
"Restore to another instance field" is missing in
SQL 2000 restore context.
Id = HSLco35458 SR:H555008431
MOM GUI does not display users.
Id = HSLco35714 SR:H555008510
SAP restore objects are not displayed.
Id = HSLco35716 SR:H555008511
Data protection and catalog protection date for same
object differs for one day.
Id = HSLco35943 SR:H555008559
After modifying OBII 3.5 Oracle8 barlist using the
4.x GUI, RMAN script gets corrupted.
PHSS_26342:
Id = HSLco31198 SR: H555006778
Restore of Oracle7 database to a different host
(backup host and target host are not the same)
fails with the following error message:
"grep: can't open
/etc/opt/omni/oracle/rcs/<Oracle_Sid>.rcs"
Id = HSLco31665 SR: H555006875
When files are selected for restore and restore is
started, RSM reports:
"Error starting VBDA <DATALIST_NAME> on <computer>:
Maximum number of files/directories specified
=> DA will not be started.
Try to specify less files/directories and
restart backup."
Id = HSLco31733 SR: H555006893
Additional dates added to periodic backup schedule
after 13 months.
Id = HSLco31949 SR: H555006942
OmniBack II A.04.10 GUI abnormally ends when trying to
connect to OmniBack II A.04.00 Cell Manager.
Id = HSLco32409 SR: H555007048
GUI shows incorrect number of SQL objects for the
system.
Id = JAGad95458 SR: 8606226389
Compress option for the SAP integration in GUI is
enabled.
Id = HSLco32637 SR:H555007125
Printing in OmniBack II 4.x HP-UX GUI does not work.
Id = HSLco32864 SR:H555007211
Linux clients can not be updated from GUI.
Id = HSLco32873 SR:H555007218
If you try to restore files in interval that does not
include full backup the following error appears:
"DB unknown error".
Id = HSLco33095 SR:H555007294
Device wizard text update is not working on HPUX 4.X
GUI.
Id = HSLco33471 SR:H555007472
Split pre-exec and post-exec scripts in the EMC
integration are grayed out.
Id = JAGae02797 SR:8606233574
Comments can not be added to RMAN script via OmniBack
if '#' is specified before comment.
Id = HSLco31357 SR:H555006818
GUI crashes during object messages check.
Id = HSLco31031 SR:H555006752
During client upgrade it is not possible to
automatically select all the hosts for the same
Installation Server.
Defect Description:
PHSS_28739:
Id = HSLco39535
Only device files of the format /dev/rmt/*mn are
filtered in devlist_ux.c.
Resolution:
New environment variable OB2BROWSEALLDEVICES is
introduced in '.omnirc' file. Possible values are
0 (default) and 1. If set to 1 the function will
also browse the /dev/rmt/*n device files.
Id = HSLco40532
The source of <basename> is not parsed.
Resolution:
The source of <basename> is parsed.
Id = HSLco40559
Schedules with excluded days are interpreted
incorrectly.
Resolution:
Schedule interpretation for excluded days is changed.
Id = HSLco40563
Magstar 3590 is not supported in the Data Protector GUI.
Resolution:
Selection for media type T3590 is added in the
OmniBack GUI.
Part of SSPUX410_066.
Id = HSLco40640
Buffer that holds tablespace names is too small.
Resolution:
Buffer size is increased.
Id = HSLco40763
Frequency of Mount Request window timer is too high.
Resolution:
Frequency of Mount Request window timer is decreased.
Id = HSLco40839
Some info about tape status is not displayed in
the GUI.
Resolution:
Tape status info is added to data displayed in
Media/Properties GUI context.
Id = HSLco40855
Some standard functions (memcpy(), strchr()) do not
work properly when converting messages on systems
with Japanese localization.
Resolution:
Message manipulation functions have been improved
in order to properly display messages in localized
Japanese environment.
Id = HSLco40890
Field for device name in output of command
"omnirtp -report session_devices" is limited to
12 characters.
Resolution:
Number of characters is increased to 20.
Id = HSLco40958
Windows XP operating system is not included in list
of possible operating systems available for Disk
Image backup.
Resolution:
Additional checking for Windows XP is added.
Id = HSLco41076
"Free for allocation" option is not implemented
correctly.
Resolution:
Formula for calculating "Free for allocation" option
is properly adjusted.
Id = HSLco41182
After a failover happens, one of the pointers points
to NULL causing GUI to end abnormally.
Resolution:
NULL pointer control is improved.
Id = HSLco41274 SR:H555010237
If the system has a large number of devices and the
device, which is put as argument to omnimm, has a
lock name, then not all devices are disabled. Device
list is split in more parts and not all parts are
searched for devices with the same lock name.
Resolution:
The search procedure is changed.
PHSS_28332:
Id = HSLco36395
Font used in the scheduler calendar control has
incorrectly set locale information.
Resolution:
Font's locale information is correctly set.
Id = HSLco36502
OmniBack II user, with only "Start backup specification"
user right, is not able to change and save the
schedule-time specification of a backup datalist.
Resolution:
New global variable "SaveScheduleAllowed" is added
and it works in combination with "Start backup
specification" user right. Default value is 0 and
it is usual interface behavior. If value is set to 1,
"SaveScheduleAllowed=1", during saving datalist error
message is still displayed, but the schedule is saved.
Id = HSLco37193
In split mirror environment with huge SAP databases
it can happen that the size of the message buffer
OmniBack II uses is too small to receive complete list
of SAP files to be backed up.
Resolution:
Setting the OB2IPCBUFSIZE environment variable in the
/opt/omni/.omnirc file on Cell Server, R1 and R2 hosts,
specifying the desired amount of memory to be used for
the buffer solves the described problem.
Please read the following instructions and make sure
that the patches listed in "Other Dependencies" section
(see below) are installed and the environment
variable is set on Cell Server, R1 and R2 systems before
running the backup!
How to determine the buffer size?
---------------------------------
N_obj: number of objects (files)
N_fs: number of file systems
N_lvmvg: number of volume groups
N_dg: number of disk groups
N_rdsk: number of rawdisks
Obj: Object Name
ObjBack: Object Backup Name
MntPathLen: Path name on backup (R2) host
(example: /var/opt/omni/tmp/App_host)
fsmnt: File System Mount Point
fsdev: File System Device File
(example: /dev/dsk/[c0t1d1,lvol1])
vg: Volume group
(ex: /dev/vg01)
dg: Disk group (VxVM) - dependence on mapfile
which is required for creating disk group
(example:/dev/vx/dsk/dg01)
rdsk: Raw disk file name
(example: /dev/rdsk/c1t1d1)
AvgLen_<xxx> average length of <xxx>
There are two different buffers used:
1. BSM <-> R1
2. R1 <-> R2
Calculating the BSM <-> R1 buffer size
--------------------------------------
MsgSize_BSM_R1 = N_obj * (AvgLen_Obj + 1 + MntPathLen)
Calculating the R1 <-> R2 buffer size
-------------------------------------
MsgSize_R1_R2 =
N_obj*(AvgLen_Obj+1+AvgLen_ObjBack) +
N_fs*(AvgLen_fsmnt*2 + MntPathLen + AvgLen_fsdev*2)+
N_lvmvg*(AvgLen_vg*2) + N_dg*(AvgLen_dg*2) +
N_rdsk*(AvgLen_rdsk*2)
Calculating the OB2IPCBUFSIZE value
-----------------------------------
OB2IPCBUFSIZE > max (MsgSize_BSM_R1, MsgSize_R1_R2)
RESTORE NOTE:
-------------
If restore is started using the sapbda utility,
the variable OB2IPCBUFSIZE must be exported to
environment prior to starting sapbda.
Known problems:
---------------
If the calculated variable OB2IPCBUFSIZE is correctly
set, but is still too small for the file list to fit
into the message buffer, the session will fail with
the following error seen in the report:
BR295I Splitting mirror disks...
BR280I Time stamp <time>
BR279E Return code from '/opt/omni/lbin/ob2smbsplit
/<sap_homedir_path>/.<filename>.lst': 2
BR299E Split/resynchronization of mirror disks failed
In this case the variable OB2IPCBUFSIZE must be
recalculated to appropriate value. See above how to
determine it.
Part of SSPUX410_033.
Id = HSLco38141
Report for original medium does not contain barcode
information.
Resolution:
Barcode information is correctly displayed.
Id = HSLco38201
Lotus object versions are not correctly stored in the
Internal Database which prevents GUI to find them.
Resolution:
Record structure containing information about the Lotus
object versions is changed.
Id = HSLco38335
The length of database session messages in Japanese
version of OmniBack II is incorrectly determined.
Resolution:
New function was added to determine the message
length.
Id = HSLco38443
OmniBack II calls FormatMessage function with two
instead of three parameters that accesses uninitialized
memory.
Resolution:
Third parameter is added.
Id = HSLco38505
Instead of Instant Recovery context GUI randomly
initializes some other context. When Cell Manager
is configured for XP, everything works properly.
Resolution:
Instant Recovery context is unconditionally initialized.
Id = HSLco38889
Pre/post-exec script hosts selection does not contain
the appropriate hosts when creating a NDMP datalist.
Resolution:
NDMP pre/post-exec script host selection is corrected
to display the appropriate hosts.
Id = HSLco39130
When Recycling or exporting original medium from
OmniBack II database purge deletes Detail Catalog
Binary Files (DCBF) even if the copy medium is still
protected in the OmniBack II database. In addition
importing catalog from copy is not possible.
Resolution:
Catalog import from copy medium is possible.
Part of SSPUX410_053.
Id = HSLco39326
When object version is changed, all tree sub items
are marked again and all excludes are deleted.
Resolution:
All explicit excludes are left in restore tree after
changing object version.
Id = HSLco39486
DbgPlain function is called with wrong string format.
Resolution:
String format for DbgPlain() is corrected.
Id = HSLco39892
There was not blank string in the "On-Client" combo box.
Resolution:
Blank string is added to combo box context and handling
with this option is added to the algorithm for making
a data list.
Id = JAGae19133
From OmniBack II A.04.00 onwards, 'BalanceNone' is
obsoleted and changed to 'BalanceLoad'.
Resolution:
'BalanceNone' option for SAP integration is implemented
again in GUI.
PHSS_27588:
Id = HSLco33238
MS SQL backup using Fast Direct mode results as
"proper backup", but there are too many messages.
Resolution:
Only one message of type:
"[Normal] From: BMA<hostname> "<device_name>"
Time: <dd.mm.yy hh:mm:ss>
Memory copy mode activated."
per Backup Media Agent (BMA) is displayed.
Id = HSLco34581
In case that "st_san_safe" kernel parameter is enabled,
system cannot work with 'rewind on close' devices.
So "devbra" is returning devices which are not usable.
Resolution:
"devbra" is changed in order to return
'non-rewind on close' devices.
Id = HSLco35611
GUI does not check on which host Oracle7 database is
backed up and all backup versions are appended to
the first one found.
Resolution:
Host matching and object version adding to list is
improved.
Id = HSLco36219
Problem occurs when there are a lot of sessions or
when there are a lot of tree nodes in scoping pane.
Resolution:
Tree control in scoping pane is dynamically collapsed
before context is switched.
Part of SSPUX410_034
Id = HSLco36343
GUI reports incorrect statistics for DCBF directory.
Resolution:
GUI is improved in order to report correct
statistics for DCBF directory.
Id = HSLco36478
Incorrect indirection operator is used.
Resolution:
Indirection operator is used correctly.
Id = HSLco36526
Devbra and sanconf are limited to 10 character serial
numbers only. When there are devices with 12 digit
SN detected, devbra truncates the last two digits.
As a result, several physical devices are then treated
as one and the same device.
Resolution:
Devbra is using all digits of the device SN to
distinguish between devices.
Part of SSPUX410_040.
Id = HSLco36751
List of clients residing in the destination cell
server is not updated.
Resolution:
List of clients residing in the destination cell
server is now properly updated.
Id = HSLco36798
After installation of SSPUX410_024 or SSPUX410_029,
GUI goes into infinite loop when view is clicked in
main menu.
Resolution:
Additional activation checking is added in users
context.
Id = HSLco36983
During second initialization of combo box an error
occurs while retrieving datalist and leaving the rest
of the fields uninitialized.
Resolution:
Fields on notification page do not disappear after
switching contexts.
Id = HSLco36986
OmniBack II does not properly create list of sessions
for used media in selected timeframe.
Resolution:
"Extended report on used media" report is removed from
reporting.
Id = HSLco36988
GUI never looks for the new 1TB XP license, but always
looks for the old XP standard license. The same is with
the new 1TB EMC license.
Resolution:
GUI also looks for the new 1TB EMC and 1TB XP licenses.
Id = HSLco36998
The cause for the error message is refreshing of media
tab. While refreshing it tries to retrieve object
versions of subfolders, which were not clicked, hence
not initialized.
Resolution:
GUI now searches only folders which have object
versions initialized.
Id = HSLco37094
Script can be run from anywhere because omnirpt does
not check the global options file.
Resolution:
Omnirpt was changed and now it checks the global
options file for ExternalScriptMode entry.
Id = HSLco37174
GUI expects "start backup" instead of "monitor" user
rights for starting Database context GUI.
Resolution:
GUI now checks "monitor" user rights for showing
/Tools/Database Administration menu item.
Id = HSLco37359
OmniBack II GUI abnormally ends on exit, when
there are two "Schedule" tabs opened at a time.
Resolution:
OmniBack II GUI ends normally.
Id = HSLco37939
Barlists are members of a group which is not displayed
under reporting group in GUI Reporting.
Resolution:
Barlists are moved to a group that is displayed in GUI.
Id = JAGae12418
GUI is not able to handle nested mount points.
When GUI receives excluded directory from datalist
file it assumes that the part of the string between
first and second slash represents mount point.
Besides this, mount point is shown in GUI as a
mountpoint and as directory.
Resolution:
GUI is aware of nested mountpoints.
Id = JAGae27939
Even though session selected for restore is not the
last one, GUI will pick the latest version of file
for restore.
Resolution:
Version selection mechanism is fixed.
Id = JAGae36127
"omnidb" options "-msese" and "-msexchange" do not show
MS Exchange 2000 objects.
Resolution:
New "omnidb -msese" option is implemented.
PHSS_26878:
Id = HSLco31458
Restore Session Manager in integration protocol is
changed and omnir is not updated correctly.
Resolution:
omnir is corrected.
Id = HSLco33515
After using CLI command omnimm -chkfreemedia
inappropriate messages are logged in the debug.log
file.
Resolution:
Inappropriate messages are no longer logged in the
debug.log file.
Id = HSLco33578
Description and Location fields in the Select Media
dialog box do not allow wildcards.
Resolution:
Description and Location fields in the Select Media
dialog box now support wildcards.
Id = HSLco33579
Message handler for device medium object does not
parse MS_GETTEXT message correctly. Therefore
pre-allocation list does not display all the data.
Resolution:
Message parsing in device medium object improved.
Id = HSLco33645
"Point in time restore" restore option of
Transaction log backup in OmniBack II MSSQL
integration is not limited.
Resolution:
"Point in time restore" restore option is limited by
the backups. The maximum time is limited by start of
backup session selected for restore. The minimum time
is limited by first previous full or differential
backup.
Id = HSLco33767
Insufficient amount of memory is allocated.
Resolution:
Enough memory is allocated.
Id = HSLco34046
Change device option is not working in host
restore mode.
Resolution:
Code is corrected.
Id = HSLco34166
OmniBack II SSEA integration option
"Keep Version available for Instant Restore" for
Continuous Access XP and Combined
(Continuous Access XP + Business Copy XP)
is not supported, but is selectable.
Resolution:
Option "Keep Version available for Instant Restore"
for other than Business Copy XP is grayed out.
Id = HSLco34174
The array that holds the objects of datalist is too
small.
Resolution:
The array is increased.
Id = HSLco34683
CDE text default color is white. OmniBack II has white
background so text is not readable.
Resolution:
Instead of button text we now use info text for tabs,
which is black.
Id = JAGad92807
This page is outdated. It must be labeled 'eCare
Support' and it must point to:
http://support.openview.hp.com/support.jsp?FromPROD
=ob_4_1
Resolution:
Label and links are fixed.
Id = NSMbb44613
At startup time all contexts/dlls are loaded.
On UX systems this needs ~2 seconds for each.
On top of that, ReadSubTree() is performed 3 times for
each context.
Resolution:
Usually administrator does not need all contexts from
the start. It is enough to first load database, monitor,
and backup. dlls for other contexts are only loaded when
the context is accessed during GUI session.
Id = HSLco34610
GUI does not check if instance is already configured.
Resolution:
GUI checks if instance is already configured.
Id = HSLco34641
"Restore to another instance" combo box for displaying
instances installed on SQL Server 2000 is missing.
Resolution:
"Restore to another instance" combo box is added.
Id = HSLco35458
MOM GUI is not aware of users and the result is "Not
Available" message in results area.
Resolution:
MOM GUI correctly displays users.
Part of SSPUX410_024.
Id = HSLco35714
If SAP host is selected in restore context, number of
objects is correct, but first object is displayed for
every object. Cause for the problem is definition of
variable mount.
Resolution:
Value of mount is not initialized but assigned.
Id = HSLco35716
Data protection value is improperly calculated.
Resolution:
Data protection calculation is improved.
Id = HSLco35943
OBII 4.x GUI reparsed RMAN script and incorrectly
recomposes it.
Resolution:
RMAN script parsing can be disabled by specifying the
following global variable:
NoGUIRMANScriptParsing=1
Part of SSPUX410_029.
PHSS_26342:
Id = HSLco31198
When restoring Oracle7 tablespace that is backed
up on one backup host to another target Oracle
client, the Restore Session Manager copies the rcs
file to the backup host instead of target host.
Resolution:
The rcs files are properly restored to the
target host.
Id = HSLco31665
Files which are grayed out in GUI are excluded with
option -exclude. Since the number of '-exclude' options
is limited, this can cause restore to fail.
Resolution:
Handling of excluded files is changed.
Id = HSLco31733
In next year the same date is not the same day in
week. Scheduled dates after one year are just copied,
so backups are scheduled on wrong days.
Resolution:
Days are correctly moved to next year.
Id = HSLco31949
Any attempt to establish connection to OmniBack II
A.04.00 Cell Manager from OmniBack II A.04.10 GUI,
when having no permissions to do so, results in
core dump of OmniBack II A.04.10 GUI.
Resolution:
Message "No permission" is displayed when one tries to
connect to a system where one does not have
sufficient permissions.
Part of SSPUX410_004.
Id = HSLco32409
GUI incorrectly determines which SQL objects has
already been added to SQL restore and which not.
Consequently GUI may display no objects at all,
though omnidb shows objects or the same object
several times.
Resolution:
GUI now correctly determines which SQL objects
have to be added to restore tree.
Id = JAGad95458
The Release Notes state that compression is not
supported for any of the database integrations.
Resolution:
The Compress option in GUI is disabled.
Id = HSLco32637
Printing is not possible due to missing windu xprinter
directory and *.drv files in OmniBack II installation.
Resolution:
Files are copied to the correct location.
Id = HSLco32864
GUI expects Windows Installation Server for Linux
client. However the right one is UNIX Installation
Server.
Resolution:
Checking is improved with new macro for GUI.
Id = HSLco32873
Selecting files for restore within interval that does
not include the full backup will trigger an error in
the list_full_rest_chain function.
Resolution:
The function marks an error and sends it to GUI, which
will show a message:
"You have chosen an interval which does not include
all the sessions needed to compose a full restore
chain. Please reconnect to the Cell Server".
Id = HSLco33095
When adding new device in GUI and device type is
changed to SCSI library in first step of wizard,
data format is not changed to interface type.
Resolution:
Window is invalidated and updated.
Id = HSLco33471
Split pre-exec and post-exec scripts working with the
EMC integration are disabled.
Resolution:
Split pre-exec and post-exec scripts working with the
EMC integration are enabled again.
Id = JAGae02797
OmniBack II uses '#' character for internal parsing.
Resolution:
Code is changed. New character <alt + 178> is used for
OmniBack II internal parsing.
Id = HSLco31357
In case that object has large number of messages,
GUI crashes during message check.
Resolution:
GUI is improved in order not to crash.
Id = HSLco31031
During client upgrade it is not possible to
automatically select all the hosts for the same
Installation Server.
Resolution:
GUI is improved.
Enhancement:
No
SR:
H555010071 H555009970 H555009880 H555009862 H555009917
H555010190 H555010038 H555010237 H555010138 H555009877
H555009430 H555010002 H555010015 H555009286 H555008639
H555009111 H555008659 H555009202 H555009022 H555009033
H555009404 8606254802 H555009064 H555009570 H555009147
H555009228 H555008807 H555009339 H555008395 H555008764
H555008755 H555008476 H555008927 H555008657 H555008757
H555007993 8606280024 H555008849 H555008779 8606263614
8606245960 B555014660 8606271949 H555008700 H555006822
H555008803 H555007372 H555008624 H555008715 H555008752
H555008636 H555008664 H555008637 H555008754 H555007748
H555006839 H555008559 8606223711 H555007697 B555013242
H555008020 H555008004 H555008510 H555008511 H555008431
H555008049 H555007518 H555007752 H555007546 H555007519
H555007591 H555007485 H555006893 H555006875 H555007211
8606226389 H555006778 H555007125 H555007218 H555007048
H555006752 H555007472 8606233574 H555006942 H555007294
H555006818
Patch Files:
OMNIBACK-II.OMNI-HPUX-P,fr=A.04.10,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/omni/databases/vendor/cc/hp/s800/hp-ux-11/A.04.10/
packet.Z
/opt/omni/databases/vendor/cc/hp/s800/hp-ux-1020/A.04.10/
packet.Z
/opt/omni/databases/vendor/momgui/hp/s800/hp-ux-1020/
A.04.10/packet.Z
/opt/omni/databases/vendor/momgui/hp/s800/hp-ux-11/A.04.10/
packet.Z
OMNIBACK-II.OMNI-OTHUX-P,fr=A.04.10,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/omni/databases/vendor/cc/dec/alpha/osf1-4/A.04.10/
packet.Z
/opt/omni/databases/vendor/cc/gpl/i386/linux-60/A.04.10/
packet.Z
/opt/omni/databases/vendor/cc/ibm/rs6000/aix-42/A.04.10/
packet.Z
/opt/omni/databases/vendor/cc/ncr/i386/mp-ras/A.04.10/
packet.Z
/opt/omni/databases/vendor/cc/sco/i386/sco_sv/A.04.10/
packet.Z
/opt/omni/databases/vendor/cc/sco/i386/unixware/A.04.10/
packet.Z
/opt/omni/databases/vendor/cc/sequent/i386/dynix/A.04.10/
packet.Z
/opt/omni/databases/vendor/cc/sgi/mips/irix-62/A.04.10/
packet.Z
/opt/omni/databases/vendor/cc/siemens/r400/sinix/A.04.10/
packet.Z
/opt/omni/databases/vendor/cc/sun/sparc/solaris-26/A.04.10/
packet.Z
what(1) Output:
OMNIBACK-II.OMNI-HPUX-P,fr=A.04.10,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/omni/databases/vendor/cc/hp/s800/hp-ux-11/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/hp/s800/hp-ux-1020/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/momgui/hp/s800/hp-ux-1020/
A.04.10/packet.Z:
None
/opt/omni/databases/vendor/momgui/hp/s800/hp-ux-11/A.04.10/
packet.Z:
None
OMNIBACK-II.OMNI-OTHUX-P,fr=A.04.10,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/omni/databases/vendor/cc/dec/alpha/osf1-4/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/gpl/i386/linux-60/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/ibm/rs6000/aix-42/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/ncr/i386/mp-ras/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/sco/i386/sco_sv/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/sco/i386/unixware/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/sequent/i386/dynix/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/sgi/mips/irix-62/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/siemens/r400/sinix/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/sun/sparc/solaris-26/A.04.10/
packet.Z:
None
cksum(1) Output:
OMNIBACK-II.OMNI-HPUX-P,fr=A.04.10,fa=HP-UX_B.11.00_32/64,
v=HP:
2325068595 39361389 /opt/omni/databases/vendor/cc/hp/s800/
hp-ux-11/A.04.10/packet.Z
3256642456 39356215 /opt/omni/databases/vendor/cc/hp/s800/
hp-ux-1020/A.04.10/packet.Z
2258807040 214427 /opt/omni/databases/vendor/momgui/hp/s800/
hp-ux-1020/A.04.10/packet.Z
948989081 214455 /opt/omni/databases/vendor/momgui/hp/s800/
hp-ux-11/A.04.10/packet.Z
OMNIBACK-II.OMNI-OTHUX-P,fr=A.04.10,fa=HP-UX_B.11.00_32/64,
v=HP:
3829631447 6802595 /opt/omni/databases/vendor/cc/dec/alpha/
osf1-4/A.04.10/packet.Z
1336311922 5431787 /opt/omni/databases/vendor/cc/gpl/i386/
linux-60/A.04.10/packet.Z
1944896905 6109072 /opt/omni/databases/vendor/cc/ibm/rs6000/
aix-42/A.04.10/packet.Z
2740347538 5979362 /opt/omni/databases/vendor/cc/ncr/i386/
mp-ras/A.04.10/packet.Z
192309531 5903947 /opt/omni/databases/vendor/cc/sco/i386/
sco_sv/A.04.10/packet.Z
1237661393 5755855 /opt/omni/databases/vendor/cc/sco/i386/
unixware/A.04.10/packet.Z
998290913 5914807 /opt/omni/databases/vendor/cc/sequent/
i386/dynix/A.04.10/packet.Z
618773527 7892038 /opt/omni/databases/vendor/cc/sgi/mips/
irix-62/A.04.10/packet.Z
374689289 6697445 /opt/omni/databases/vendor/cc/siemens/
r400/sinix/A.04.10/packet.Z
3083702480 6083438 /opt/omni/databases/vendor/cc/sun/sparc/
solaris-26/A.04.10/packet.Z
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies:
If any newer SSP for the Cell Console is installed
on your system, you must re-apply the SSP after
installing this Cell Console patch.
PHSS_28732:
Cell Server (CS) packet patch,
Release date: Available
Id = HSLco40559 SR:H555009877
Id = HSLco39130 SR:H555009286
Id = HSLco37939 SR:H555008927
Id = HSLco37193 SR:H555008807
Id = HSLco33515 SR:H555007485
Id = HSLco32873 SR:H555007218
Id = JAGae12418 SR:8606245960
PHSS_28732 is required for these defect fixes.
PHSS_28724:
SAP packet patch,
Release Date: Available
Id = HSLco37193 SR:H555008807
PHSS_28724 is required for this defect fix.
PHSS_28585:
Core packet patch,
Release Date: Available
Id = HSLco37193 SR:H555008807
Id = HSLco35716 SR:H555008511
Id = HSLco34641 SR:H555008020
Id = HSLco32873 SR:H555007218
Id = JAGad92807 SR:8606223711
Bad catalog access messages are displayed without
PHSS_28585.
PHSS_28342:
EMC packet patch,
Release Date: Available
Id = HSLco37193 SR:H555008807
PHSS_28342 is required for this defect fix.
PHSS_28334:
Media Agent (MA) packet patch,
Release Date: Available
Id = HSLco36526 SR:B555014660
Id = HSLco34581 SR:H555007993
PHSS_28334 is required for these defect fixes.
OMNIBACK_00079:
NT_MA packet patch,
Release Date: Available
Id = HSLco33238 SR:H555007372
OMNIBACK_00079 is required for this defect fix.
Supersedes:
PHSS_28332 PHSS_27588 PHSS_26878 PHSS_26342
Equivalent Patches:
PHSS_28738:
s700: 10.20
s800: 10.20
Patch Package Size: 129700 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_28739
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_28739.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_28739. 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_28739.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_28739.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_28739.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_28739:
NOTE!
This Patch has to be installed on the Installation
Server host.
The User Interface must be redistributed to the client
system(s) after the installation of the patch in order
to get the fixes into effect.
For distribution of the User Interface, refer to the
OmniBackII Installation guide.
Patch includes the following Site Specific Patches:
SSPUX410_004
SSPUX410_024
SSPUX410_029
SSPUX410_033
SSPUX410_034
SSPUX410_040
SSPUX410_053
SSPUX410_066
-----End of Document ID: PHSS_28739------------------------------------------
Document ID: PHCO_28656
Date Loaded: 20030521
Title: s700_800 11.X VERITAS Enterprise Administrator Patch
Patch Name: PHCO_28656
Patch Description: s700_800 11.X VERITAS Enterprise Administrator Patch
Creation Date: 03/02/27
Post Date: 03/05/21
Hardware Platforms - OS Releases:
s700: 11.00 11.11
s800: 11.00 11.11
Products:
VRTSob 3.0.2.261a
Filesets:
VRTSobgui.VEA-FILESET,fr=3.0.2.261a,fa=HP-UX_B.11.11_32/64,v=HP
VRTSobgui.VEA-FILESET,fr=3.0.2.261a,fa=HP-UX_B.11.11_32/64,v=VERITAS
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_28656
Symptoms:
PHCO_28656:
Incremental fixes implemented in VEA 3.0.2.272
integrated back into VEA 3.0.2.261.
Defect Description:
PHCO_28656:
This patch majorly contains bug fixes of the VERITAS
Enterprise Administrator (VEA), which were done
between the VEA release 3.0.2.261 and the VEA release
3.0.2.272, as reported by different VERITAS point
products using VEA.
Enhancement:
No
SR:
8606297830
Patch Files:
VRTSobgui.VEA-FILESET,fr=3.0.2.261a,fa=HP-UX_B.11.11_32/64,
v=HP:
VRTSobgui.VEA-FILESET,fr=3.0.2.261a,fa=HP-UX_B.11.11_32/64,
v=VERITAS:
/opt/VRTSob/bin/vea
/opt/VRTSob/lib/OBGUI.jar
/opt/VRTSob/lib/cat/resource.jar
/opt/VRTSob/lib/ci.jar
/opt/VRTSob/lib/cicustom.jar
what(1) Output:
VRTSobgui.VEA-FILESET,fr=3.0.2.261a,fa=HP-UX_B.11.11_32/64,
v=HP:
/opt/VRTSob/bin/vea:
None
/opt/VRTSob/lib/OBGUI.jar:
None
/opt/VRTSob/lib/cat/resource.jar:
None
/opt/VRTSob/lib/ci.jar:
None
/opt/VRTSob/lib/cicustom.jar:
None
cksum(1) Output:
VRTSobgui.VEA-FILESET,fr=3.0.2.261a,fa=HP-UX_B.11.11_32/64,
v=HP:
701711362 3900 /opt/VRTSob/bin/vea
4047466685 1574530 /opt/VRTSob/lib/OBGUI.jar
1916146153 413 /opt/VRTSob/lib/cat/resource.jar
1566481442 369093 /opt/VRTSob/lib/ci.jar
593545730 51593 /opt/VRTSob/lib/cicustom.jar
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches: None
Patch Package Size: 1980 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 PHCO_28656
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_28656.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_28656. 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 PHCO_28656.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHCO_28656.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_28656.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHCO_28656------------------------------------------
Document ID: PHCO_28651
Date Loaded: 20030521
Title: s700_800 11.X VERITAS Enterprise Administrator Srvc Patch
Patch Name: PHCO_28651
Patch Description: s700_800 11.X VERITAS Enterprise Administrator Srvc Patch
Creation Date: 03/04/29
Post Date: 03/05/21
Hardware Platforms - OS Releases:
s700: 11.00 11.11
s800: 11.00 11.11
Products:
VRTSob 3.0.2.261a
Filesets:
VRTSob.VEAS-FILESET,fr=3.0.2.261a,fa=HP-UX_B.11.11_32/64,v=HP
VRTSob.VEAS-FILESET,fr=3.0.2.261a,fa=HP-UX_B.11.11_32/64,v=VERITAS
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_28651
Symptoms:
PHCO_28651:
Incremental fixes implemented in VEA 3.0.2.272 integrated
back into VEA 3.0.2.261.
Defect Description:
PHCO_28651:
This patch majorly contains bug fixes of the VERITAS
Enterprise Administrator (VEA) service, which were done
between the VEA release 3.0.2.261 and the VEA release
3.0.2.272, as reported by different VERITAS point products
using VEA.
Enhancement:
No
SR:
8606297831
Patch Files:
VRTSob.VEAS-FILESET,fr=3.0.2.261a,fa=HP-UX_B.11.11_32/64,
v=HP:
VRTSob.VEAS-FILESET,fr=3.0.2.261a,fa=HP-UX_B.11.11_32/64,
v=VERITAS:
/opt/VRTSob/bin/vxalerttype
/opt/VRTSob/bin/vxobjecttype
/opt/VRTSob/bin/vxregctl
/opt/VRTSob/bin/vxsvc
/opt/VRTSob/bin/vxsvcctrl
/opt/VRTSob/extensions/GlobalObject/IsisSkin/java/1033/
GlobalObjects.jar
/opt/VRTSob/extensions/ObguiPrint/IsisSkin/java/1033/
ObguiPrint.jar
/opt/VRTSob/extensions/PrintController/IsisSkin/java/1033/
PrintController.jar
/opt/VRTSob/extensions/System/IsisSkin/java/1033/
SystemExtension.jar
/opt/VRTSob/extensions/alertlog/IsisSkin/java/1033/
AlertExtension.jar
/opt/VRTSob/extensions/controlPanel/IsisSkin/java/1033/
controlPanel.jar
/opt/VRTSob/extensions/genericlogger/IsisSkin/java/1033/
TaskExtension.jar
/opt/VRTSob/lib/libvxapi.sl
/opt/VRTSob/providers/alertlog/alertlog.sl
/opt/VRTSob/providers/controlPanel/controlpanel.sl
/opt/VRTSob/providers/genericlogger/libgenericlogger.sl
/opt/VRTSob/sbin/isisd
what(1) Output:
VRTSob.VEAS-FILESET,fr=3.0.2.261a,fa=HP-UX_B.11.11_32/64,
v=HP:
/opt/VRTSob/bin/vxalerttype:
None
/opt/VRTSob/bin/vxobjecttype:
None
/opt/VRTSob/bin/vxregctl:
None
/opt/VRTSob/bin/vxsvc:
None
/opt/VRTSob/bin/vxsvcctrl:
None
/opt/VRTSob/extensions/GlobalObject/IsisSkin/java/1033/
GlobalObjects.jar:
None
/opt/VRTSob/extensions/ObguiPrint/IsisSkin/java/1033/
ObguiPrint.jar:
None
/opt/VRTSob/extensions/PrintController/IsisSkin/java/1033/
PrintController.jar:
None
/opt/VRTSob/extensions/System/IsisSkin/java/1033/
SystemExtension.jar:
None
/opt/VRTSob/extensions/alertlog/IsisSkin/java/1033/
AlertExtension.jar:
None
/opt/VRTSob/extensions/controlPanel/IsisSkin/java/1033/
controlPanel.jar:
None
/opt/VRTSob/extensions/genericlogger/IsisSkin/java/1033/
TaskExtension.jar:
None
/opt/VRTSob/lib/libvxapi.sl:
None
/opt/VRTSob/providers/alertlog/alertlog.sl:
None
/opt/VRTSob/providers/controlPanel/controlpanel.sl:
None
/opt/VRTSob/providers/genericlogger/libgenericlogger.sl:
None
/opt/VRTSob/sbin/isisd:
None
cksum(1) Output:
VRTSob.VEAS-FILESET,fr=3.0.2.261a,fa=HP-UX_B.11.11_32/64,
v=HP:
2808313137 135168 /opt/VRTSob/bin/vxalerttype
3797361834 135168 /opt/VRTSob/bin/vxobjecttype
2290452317 90112 /opt/VRTSob/bin/vxregctl
3017587946 90112 /opt/VRTSob/bin/vxsvc
1991398835 1276 /opt/VRTSob/bin/vxsvcctrl
2590381074 6845 /opt/VRTSob/extensions/GlobalObject/
IsisSkin/java/1033/GlobalObjects.jar
2622137533 16945 /opt/VRTSob/extensions/ObguiPrint/IsisSkin/
java/1033/ObguiPrint.jar
2710301984 9272 /opt/VRTSob/extensions/PrintController/
IsisSkin/java/1033/PrintController.jar
3281165167 1459 /opt/VRTSob/extensions/System/IsisSkin/java/
1033/SystemExtension.jar
3078716101 43895 /opt/VRTSob/extensions/alertlog/IsisSkin/
java/1033/AlertExtension.jar
269186791 5789 /opt/VRTSob/extensions/controlPanel/IsisSkin/
java/1033/controlPanel.jar
947195510 52538 /opt/VRTSob/extensions/genericlogger/
IsisSkin/java/1033/TaskExtension.jar
3221409792 8079272 /opt/VRTSob/lib/libvxapi.sl
785238079 983040 /opt/VRTSob/providers/alertlog/alertlog.sl
2447554998 20480 /opt/VRTSob/providers/controlPanel/
controlpanel.sl
2198365113 913408 /opt/VRTSob/providers/genericlogger/
libgenericlogger.sl
192981623 4467 /opt/VRTSob/sbin/isisd
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches: None
Patch Package Size: 10390 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 PHCO_28651
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_28651.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_28651. 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 PHCO_28651.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHCO_28651.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_28651.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHCO_28651------------------------------------------
Document ID: PHNE_28606
Date Loaded: 20030520
Title: s700_800 11.00 3.10.01 ACC X.25/9000 Link S/W Patch
Patch Name: PHNE_28606
Patch Description: s700_800 11.00 3.10.01 ACC X.25/9000 Link S/W Patch
Creation Date: 03/05/02
Post Date: 03/05/20
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products:
Z7480AA B.03.02.00 B.03.10.00 B.03.10.01
Z7476AA B.03.02.00 B.03.10.00 B.03.10.01
Filesets:
ACC-SX25.ACC-SX25-KRN,fr=B.03.02.00,fa=HP-UX_B.11.00_32,v=HP
ACC-SX25.ACC-SX25-KRN,fr=B.03.10.00,fa=HP-UX_B.11.00_32,v=HP
ACC-SX25.ACC-SX25-KRN,fr=B.03.10.01,fa=HP-UX_B.11.00_32,v=HP
ACC-SX25.ACC-SX25-KRN,fr=B.03.02.00,fa=HP-UX_B.11.00_64,v=HP
ACC-SX25.ACC-SX25-KRN,fr=B.03.10.00,fa=HP-UX_B.11.00_64,v=HP
ACC-SX25.ACC-SX25-KRN,fr=B.03.10.01,fa=HP-UX_B.11.00_64,v=HP
ACC-SX25.ACC-SX25-RUN,fr=B.03.02.00,fa=HP-UX_B.11.00_32/64,v=HP
ACC-SX25.ACC-SX25-RUN,fr=B.03.10.00,fa=HP-UX_B.11.00_32/64,v=HP
ACC-SX25.ACC-SX25-RUN,fr=B.03.10.01,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHNE_28606: PANIC HANG
PHNE_26297: OTHER
Once the problem mentioned in JAGad97577
happens, stopping the X.25 link and ZCOM
subsystem does not resolve the problem. The
only way to recover is to reboot the system.
PHNE_23722: PANIC
PHNE_22253: MEMORY_LEAK HANG
PHNE_20745: PANIC HANG
Category Tags:
defect_repair hardware_enablement enhancement
general_release critical panic halts_system memory_leak
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_28606
Symptoms:
PHNE_28606:
SR 8606306906 / CR JAGae69940:
System Panics with Data Page Fault on K-class system
with 4-port NIO card with the following stack trace :
stack trace for event 0
crash event was a panic
panic+0x14
report_trap_or_int_and_panic+0x4c
trap+0xeb0
$call_trap+0x38
N2Z_F0_rserv+0x7c0
sq_wrapper+0x90
str_sched_mp_daemon+0x130
str_sched_daemon+0x2dc
main+0xaa0
$vstart+0x34
$locore+0x90
stack trace for event 1
crash event was a panic
panic+0x14
wait_for_lock+0x270
slu_retry+0x18
N2Z_F0_close+0x458
close_wrapper+0x38
csq_protect+0x10c
osr_pop_subr+0x1ec
osr_close_subr+0xc0c
hpstreams_close_int+0x30c
streams_close+0x10
XSO_F0_close_dirty_list+0x78
XPR_F_pr_usrreq+0x1fc
soclose+0x220
soo_close+0x7c
closef+0x60
close+0x84
syscall+0x1e4
$syscallrtn+0x0
SR 8606236935 / CR JAGae05984:
'x25stat' doesn't report the Negotiated parameters
correctly for flowcontrol and thruputclass
SR 8606289434 / CR JAGae53365:
ACC not recovering after sending an RNR(Receiver Not
Ready).
SR 8606266220 / CR JAGae30469:
System panics with a Data Page Fault with the
following stack trace :
panic+0x14
report_trap_or_int_and_panic+0x84
interrupt+0x1d4
$ihndlr_rtn+0x0
streams_put+0x30
N2Z_F_reset_ind+0x94
N2z_iev_reset_ind+0x128
N2z_ReadEvent_Recvd+0x2278
SR 8606259525 / CR JAGae23843:
System panics with a Data Page Fault with the
following stack trace :
panic+0x6c
report_trap_or_int_and_panic+0x94
trap+0xed4
nokgdb+0x8
kfree+0xe4
N2z_shutdown_x25_subsys+0x6ac
N2Z_F0_close+0x708
close_wrapper+0x38
SR 8606235666 / CR JAGae04809:
In nli2zcom driver some spinlock issues were found
which can result in spinlock timeout or deadlock
panics.
PHNE_26297:
SR 8606231736 / CR JAGae00972:
ACC X.25 IP/X25 will no longer work after the 2nd
"x25init".
SR 8606228520 / CR JAGad97577:
When there is a lot of open and close of X.25 sockets
and the ACC kernel limit "n2z_max_devs" is reached, X.25
socket creation with socket() call returns invalid
errno 65535(-1).
PHNE_23722:
SR 8606227359 / CR JAGad96420:
ioctls in n2z_cntrl fails with "Bad address" error
SR 8606225328 / CR JAGad94415:
ACC 3.xx sends the calling address in call accept packet
SR 8606171598 / CR JAGad40862:
Need to enhance "x25stat" command to show "VC Up Time"
for all active virtual circuits.
SR 8606144441 / CR JAGad13781:
'x25init' fails due to insufficient HP-UX memory.
SR 8606146312 / CR JAGad15656:
'x25init' command fails with the following error
message in nettl log when there are more number of VCs
configured than the number of terminal ZLU entries in
the ".answ" file.
N2Z: The zconfig() call to create a new L3 ZLU has
unexpectedly failed with error -15. Unable to
startup the X.25 line (Mux = 0, Port 7, Subc
0)!
SR 8606146870 / CR JAGad16213:
Data page fault in streams_put with the following stack
trace :
panic+0x14
report_trap_or_int_and_panic+0x94
interrupt+0x1d0
$ihndlr_rtn+0x0
streams_put+0x2c
N2Z_F_reset_ind+0x90
N2z_iev_reset_ind+0x138
N2z_ReadEvent_Recvd+0x1d94
SR 8606152276 / CR JAGad21615:
System panics due to spinlock deadlock with the
following stack trace :
panic+0x14
too_much_time+0x2e8
wait_for_lock+0x204
sl_retry+0x1c
N2Z_F0_open+0x9b8
open_wrapper+0x40
csq_protect+0x120
SR 8606197878 / CR JAGad67069:
When an "x25stat" is done, the Max Framesize that is
displayed is shown in bits instead of bytes.
SR 8606197879 / CR JAGad67070:
System panics with the Spinlock timeout failure when
system runs out of system buffers.
SR 8606151859 / CR JAGad21198:
System panics with a Data Page Fault with the following
stack trace :
panic+0x14
report_trap_or_int_and_panic+0x5c
interrupt+0x1f8
$ihndlr_rtn+0x0
N2Z_F_disc_ind+0xf4
N2z_iev_disconnect_ind+0xc60
N2z_ReadEvent_Recvd+0x588
Zc_putq+0x60
PHNE_22253:
CR JAGad13782
memory leak in nli2zcom driver.
PHNE_20745:
CR JAGad03672
Potential data loss when sending large messages spanning
multiple send request with the M-bit set and the VC goes
into outbound flow control.
CR JAGad03662
Inbound data would not be available to an application using
the SET_FRAGMENT_SIZE ioctl until a large amount of data
(2K-28K bytes) or the entire message had arrived
CR JAGad03531
"x25stat -c" does not display the correct values for the
facility settings or throughput class.
CR JAGad03534
When an X.25 link is configured with flow control and/or
throughput class facilities and the user or other upper
layer protocol stack (e.g. SNA QLLC, OTS, etc) also
supplies one or more of these facilities, the facilities
string will contain duplicate facility codes.
CR JAGad02275
System panic in N2Z_F0_rserv() during extreme traffic
loads with a grossly undersize ZCOM buffer pool and
running x25stop.
The stack trace is:
panic+0x14
report_trap_or_int_and_panic+0x80
trap+0xdb8
nokgdb+0x8
N2Z_F0_rserv+0x624
sq_wrapper+0x9c
ioctl_sleep+0x304
wait_iocack+0x7c
str_istr_ioctl+0x73c
hpstreams_ioctl_int+0x2a4
hpstreams_ioctl+0x50
spec_ioctl+0xac
vno_ioctl+0x90
ioctl+0x84
syscall+0x200
$syscallrtn+0x0
CR JAGad01873
System panics when hitting Ctrl-C (^C) during "x25init"
CR JAGad00253
System hang when running CHO tests.
CR JAGac42655
System panic in Zc_balloc() or Zc_bfree() or a panic with
the string "Caller attempted to free buffer twice!" and
the following stack trace :
panic+0x14
n2z_free_zcom_buffer+0x7a8
freeb+0x81c
freemsg+0x1c
XIQ_F_handler+0x45c
XST_F_read_put+0x294
csq_turnover_with_lock+0x88
streams_put+0x224
XSO_F0_a_retry_shutdown+0x190
XSO_F_handler+0x2fe0
XSO_F_handler+0x350c
XPR_F_pr_usrreq+0x5f4
sodisconnect+0x4c
soclose+0x390
soo_close+0x90
closef+0x68
exit+0x324
psig+0x258
syscall+0x97c
$syscallrtn+0x0
CR JAGab66344
When running lanscan, no I/O hardware path is displayed
for initialized X.25 links.
CR JAGac39375
When running "x25stat" with the "-v" option, the
incorrect or missing local and remote addresses are
displayed.
CR JAGac39379
When running "x25stat" with the "-c" option, the high LCN
value is always one greater than it should be.
CR JAGac39382
When running "x25stat" with the "-c" option, the line
speed (baud rate) is not displayed correctly.
CR JAGac42322
When "x25init" is run in parallel with a zmasterd
stop/kill, subsequent "x25inits" can fail. The failure
is always logged as a zconfig() failed with ZCOM error
-85 (invalid sender's ZLU) in the nettl log file. At
this point, the only way to clear this problem is to
reboot the system.
CR JAGab66351
The ACC X.25/9000 link software product SD control
scripts and other invoked 'ksh' scripts violated the SD
control script guidelines for output messages.
CR JAGab66277
When the user's path variable was not defined or at
least not set with the paths expected by the ACC
scripts, various ACC script failures would occur.
CR JAGab72105
Using n2z_cfg, you could not set the port back into
loopback mode on a 64-bit system.
CR JAGab68606
Message logged by the 'zx25d' driver when an inbound
diagnostic packet arrives displays random values for
the mux, port, and subchannel number.
CR JAGab73855
System panic in asm_spinlock/XSY_F_plp_callback on
'x25init'.
CR JAGab84691
Enhancement Request: Add support for the new 8-port
PCI card.
CR JAGab84870
System panic in N2Z_F_disc_conf().
CR JAGac29102
PANIC: Data page fault in N2Z_F_data_ind() when under
extreme loads
CR JAGab29104
This is an enhancement to improve driver trace
performance and a minor improvement in accuracy of
display when there is lots of trace output. Affects
zx25d, naccX, and n2z driver trace and display
programs.
CR JAGab66272
when 'x25init' is hit with signals, it fails with a error
message indicating that N2Z_IOCTL failed. Subsequent
usage of x25init results in the same error message
getting displayed and x25init does not complete.
CR JAGab66270
when a zmasterd stop is done while >200 VCs are
established and data transfer is being done (as in QA
tests_x25_cmd/test27) a panic occurs.
CR JAGab66342
When running the installation verification loopback
tests for the X.25/ACC product, the second invocation
of "x25init" failed.
CR JAGab83699
Every time "x25init" was run for an ACC card, the
following two messages were logged in syslog.log:
"vmunix: stream thresholds received: context = 3fa5480"
"vmunix: stream denied received: context = 3fa5480"
PHNE_20101:
CR JAGab82635
After running a series of stress tests that use lot
of sockets the system fails with "Can't open any more
Nli2zcom streams" message.
A test program showed errors such as:
"accept() #189 failed, errno = 65535: Unknown error"
CR JAGab81509
system panics with "kernel stack overflow"
panic+0x14
report_trap_or_int_and_panic+0x80
trap+0x958
nokgdb+0x8
XLS_F0_call_match_1+0x0
XLS_F_handler+0x6e8
XST_F_read_put+0x3f8
putnext+0x198
N2Z_F0_n_di_listen+0x25c
N2Z_F0_wput+0x2c48
putnext+0x198
XLS_F0_a_disconnect_req+0xcc
XLS_F_handler+0xed0
XLS_F_handler+0x1540
XST_F_read_put+0x3f8
putnext+0x198
N2Z_F0_n_di_listen+0x25c
N2Z_F0_wput+0x2c48
putnext+0x198
N2Z_F0_n_di_listen+0x25c
CR JAGab66316
System panics when x25init is done with a large
configuration of Vcs > 8K.
panic+0x14
report_trap_or_int_and_panic+0x80
interrupt+0x1d4
$ihndlr_rtn+0x0
asm_spinlock+0x14
XSY_F_plp_callback_func+0x54
N2Z_F_link_up+0x2c
N2z_ReadEvent_Recvd+0x133c
Zc_putq+0x64
Zc_addq+0x1cc
Zc_dataput_p+0x34
zksend+0x2a4
Zx_Send_appl_status+0x1d0
Zx_proc_unsol_event+0xd28
zx25_event_handler+0x3f0
Zc_putq+0x64
nacc1_receive_data+0x178
nacc1_pass_rxdata+0x8c
nacc1_cmplt_read+0x4b4
nacc1_complete_req+0x25d8
nacc1_end_io+0x380
nacc1_int_event+0x47c
nacc1_isr+0x14
wsio_interrupt+0x58
mp_ext_interrupt+0x14c
ivti_patch_to_nop3+0x0
idle+0x1dc
swidle_exit+0x0
CR JAGab72034
system panic when zmasterd stop is done during x25init
q4> trace event 0
stack trace for event 0
crash event was a panic
panic+0x14
report_trap_or_int_and_panic+0x80
trap+0xdb8
nokgdb+0x8
N2z_Enable_ZLUs+0x134
N2z_start_link+0x5a8
N2Z_F0_start_link_ioctl+0x28c
N2Z_F0_wput+0x2408
putnext+0x198
wait_iocack+0x68
str_istr_ioctl+0x73c
hpstreams_ioctl_int+0x2a4
hpstreams_ioctl+0x50
spec_ioctl+0xac
vno_ioctl+0x90
ioctl+0x84
syscall+0x200
$syscallrtn+0x0
Another panic stack seen:
q4> trace event 0
stack trace for event 0
crash event was a panic
panic+0x14
report_trap_or_int_and_panic+0x80
trap+0xde8
nokgdb+0x8
N2z_shutdown_x25_subsys+0x584
N2Z_F0_close+0x4a0
close_wrapper+0x38
csq_protect+0x120
osr_pop_subr+0x220
osr_close_subr+0x324
hpstreams_close_int+0x314
hpstreams_close+0x2c
call_open_close+0x1f8
closed+0xb0
spec_close+0x54
vn_close+0x48
vno_close+0x20
closef+0x64
close+0x88
syscall+0x200
$syscallrtn+0x0
CR JAGab82415 / SR 8606109715
Memory leak of 2K stream buffers in call accept path.
JAGab72105
On a 64bit system, the 'n2z_pcfg' command can not set
the port to a LOOPBACK state.
CR JAGab72028
'nz2_pcfg' causes backplane DMA timeout and card crash.
Seen when the following was performed:
-Start acc with ports in LBACK
-run 'x25init' on each port
-change port mode to rs232 using 'n2z_pcfg'
-the command appears to hang, and there
is a backplane timeout, after which the card is unusable
and the ports will not come up, until ACC is
stopped and restated. (zmon restart does not bring
card back - you have to use zmasterd kill)
Log message includes:
Backplane command (DMA) has timed out !
CR JAGab66270
system panic when zmasterd stop is done during
connection and data transfer involving 200 VCs.
q4> trace event 0
stack trace for event 0
crash event was a panic
panic+0x14
report_trap_or_int_and_panic+0x4c
trap+0x7a4
$RDB_trap_patch+0x38
N2Z_F0_wput+0x814
putnext+0x50
XST_F_write_service+0xe8
sq_wrapper+0x90
str_sched_mp_daemon+0x150
str_sched_daemon+0x3a0
main+0x540
$vstart+0x34
$locore+0x90
CR JAGab66342
The 'x25init' program functionality was changed to require
that each X.25 IP address be assigned to a separate subnet.
The default x25init configuration files for the loopback
tests did not an IP address on a separate subnet.
This caused the second x25init to fail. The scripts which
build the 'x25init' configuration files have been change
to comment out the IP parameters since they are not used
in the loopback verification tests.
CR JAGab83699
Two debugging printf's were accidentally left in
the shipped driver. These statements have been removed.
PHNE_19049:
CR JAGab66250
ACC passes Invalid QOS parameters when an outgoing
connection is sent / rejected.
When a large message is sent with 'Mbit',the circuit
will hang after receiving 'N2z_max_ninb_pkts' packets.
When SNA with QLLC option is used on ACC , the inbound
data was queued using "putq" that causes performance
problems.
CR JAGab66253
Fix the Transient Reject problem seen by OTS, the symptom
could be that when OTS is configured with Transient Reject
the Inbound calls are not accepted.
DTS TPO0h02841 / SR 4701431023
ACC 3.02, Using padem the "ls -R", will cause ACC to hang
TPO0h02756
A variety of strange HDLC protocol problems including
N2 retransmit limit exceeded error , T3/T4 timeouts.
TPO0h02728
The 'n2z_pcfg' utility fails with an error and does not
configured the ACC MUX port.
TPO0h02696
Under heavy load, the system would panic with a data page
fault in 'N2z_restart_qdwrts()'.
DTS TPO0h02602
It takes too long (30-60 sec) for an Application to
receive OOB_VC_CLEAR on an Inbound Disconnect
Indication.
DTS TPO0h02561
System panic in N2z_close().
DTS TPO0h01987
Enhancement request to implement the 'isdn_pcfg'
utility program to reconfigure the ISDN port.
DTS TPO0h01629
Traces won't work if the core dump is not in the default
directory. (/var/adm/crash)
DTS TPO0h02703
While testing the OTS/9000 product with X25/ACC, the
routine QVF_F_qos_to_x25fac () returns an error
code (-1), when there is no error, when processing a
disconnect indication.
Defect Description:
PHNE_28606:
SR 8606306906 / CR JAGae69940:
This problem happens when "x25stop" is issued after
a "zmasterd kill". This results in a race condition
in which even after the zcom cleanup routines are
called, streams layer calls the 'N2Z callback'
service routine to queue the data to upper layers.
But since the cleanup routines have freed most of
the relevant data structures like 'lhvcp', 'N2Z'
service routine causes a panic while accessing
these data structures.
Resolution: The fix is to prevent 'N2Z' service routine
to return immediately if a 'zcom' shutdown is in progress
or complete. N2Z_F0_rserv() routine is modified to check
if 'N2Z_ZCOM_SHUTDOWN_COMPLETE' flag is set in
'n2z_cb.state' and return immediately if set.
SR 8606236935 / CR JAGae05984:
This problem is related to misinterpretation of the
flag used for getting these negotiated parameters.
The flag, which was assumed by ACC to display the
thruput parameters, was actually used by the x25 stack
to display the flowcontrol parameters. Hence for an
"x25stat" command that issued while flowcontrol is set,
ACC takes this as thruputflag and responds with
values related to thruputflag.
Resolution: Correct flag has been set so that
"x25stat" displays the flowcontrol information
correctly when turned on.
SR: 8606289434 / CR: JAGae53365
After sending an 'RNR', ACC/X.25 driver did not send
an RR to clear the flowcontrol i.e. 'NLI2ZCOM' driver
was not coming out of flowcontrol mode. This caused
the communication to be in a pending (hung) state
until another event clears the flowcontrol condition
such as a Reset packet after the timeout.
Resolution: To resolve this defect, code change has
been done to check the flowcontrol parameters of the
'NLI2ZCOM' driver. Once the driver is out of the
flowcontrol it sends 'RR'.
SR: 8606266220 / CR: JAGae30469
This problem arises due a to race condition between
the detaching and resetting of a PVC. This panic is
happening because the Reset and Detach processing of
the same PVC are going on simultaneously. While
detaching the PVC, the 'readq' pointer is set to NULL
and when 'Reset' is trying to access that pointer it
results in a Data Page Fault panic in "N2Z_F_reset_ind"
function.
Resolution: The fix is to prevent Detach and Reset
of a PVC to go simultaneously. This is achieved by
setting a flag 'Nz_X25_RESET_ACTIVE' (lhvcp flag) in
"N2z_iev_reset_ind( )" to indicate that a 'Reset' is
active and do not start Detaching this PVC, wait
till 'Reset' is over for this PVC.
SR: 8606259525 / CR: JAGae23843
This panic was a result of a Race condition between
'zmasterd' shutdown and the 'x25subsystem' shutdown. In
one thread "N2z_zcom_shutdown_cleanup()" function was
running in which 'l2pda->vctbl' is made NULL and in
another thread "N2z_shutdown_x25_subsys()" was going on.
When "N2z_shutdown_x25_subsys()" tries to access
'l2pda->vctbl' which has been made NULL by
"N2z_zcom_shutdown_cleanup()", the system panics.
Resolution: Fix was to add a check for 'l2pda->vctbl'
is NULL or not in "N2z_shutdown_x25_subsys()". Also
care has been taken to prevent a race condition.
SR: 8606235666 / CR: JAGae04809
In "N2z_Cfg_Zlus()" routine, it was observed that
in one code path, there were chances of a thread
going to sleep while holding the spinlock and in
another code path, where the spinlock is supposed to
be held, it was not holding the lock. Both these
cases can lead to spinlock timeout/deadlock panics
or race conditions.
Resolution: Code changes have been done to take care
of these issues.
PHNE_26297:
SR: 8606231736 / CR: JAGae00972
If multiple X.25 links are used concurrently on a
system, then following symptoms happen: 'IP over x25'
works with 'x25init -c config_file -a ip_to_x121_map'
command, if it was issued before 'sx25d' process
startup. But if we restart the x.25 link with the same
command while 'sx25d' is still running, then 'IP over
X25' do not work while all the SVC and PVC operations
for the link work normally. If we stop all the x.25
links via "x25stop -K" or "x25stop -d" individually, which
causes 'sx25d' process stop, and then with the above
"x25init" command, IP over X.25 works.
In "N2z_stop_link" processing, we scan through all the VC
structures and cleanup that are not in idle state. In
this process, we check to see if there is any stream
associated with the VC. If so, stype of stream context
was set as 'N2Z_ERROR_STRM' for the duration till the x25
upper layers releases the previous connection
established by 'ping'. So, when "x25init" is done for the
second time within this duration, "x25init" path
identifies that VC stream context type as ERROR stream
and 'ping' doesn't go through.
Resolution:
Fix is to change the N2Z_ERROR_STRM to
N2Z_UNKNOWN_STRM, so that the ping will go through.
SR: 8606228520 / CR: JAGad97577
This problem has been noticed with PVCs and while
detaching the PVC in "N2Z_F_pvc_detach_up()" routine, the
VC Stream q_ptr field was made NULL. However in VC
Stream close routine "N2Z_F0_close()", if q_ptr is NULL,
then the further closing and clean-up of the VC stream
was not complete, and hence VC Streams were not
returned to free pool. So this caused the driver to
run out of available VC Streams and the socket() call
returns errno. 65535 after the kernel 'n2z_max_devs' is
reached.
Resolution:
A new 'lhvcp' flag mask has been introduced and this
flag is set during PVC detach processing to indicate
that VC Stream close is still pending and thereby
avoiding a need to set the VC Stream 'q_ptr' to NULL.
Code change has been made to check for this flag and
reset the flag during 'lhvcp' allocation.
PHNE_23722:
SR: 8606227359 / CR: JAGad96420
When trying to set the tunable values using 'n2z_cntrl',
it fails with "Bad address" error. For eg., "n2z_cntrl
-d0" will display "n2z_cntrl: Bad address". This is
because, the parameters used in ioctl function were not
correct. The second parameter of the ioctl should be
'I_STR' and the third parameter should be the 'strioctl'
structure.
Resolution : This has been fixed as follows:
Instead of calling ioctl like,
"ioctl(ssmfd, N2Z_CTS_CD_FLAG, &flag)"
ioctl will now be called by filling the strioctl
structure and then call,
"ioctl(ssmfd, I_STR,&strioctl)"
SR: 8606225328 / CR: JAGad94415
ACC 3.xx has a non NULL calling address in the call
accept packet, which is refused by TRANSPAC.
Resolution : This problem has been fixed by providing
a tunable parameter, which can be set using
"/opt/acc/bin/n2z_cntrl". By default this flag is set to
'0'. So, calling address in call accept packet is '0' by
default. If set to '1', the call accept packet contains
the calling address.
SR: 8606171598 / CR: JAGad40862
'x25stat' in ACC 3.xx does not display "VC Up Time" for
all the active virtual circuits.
Resolution : Provided "-u" option in "x25stat" command
so that the user can request the "VC Up Time" for all
active virtual circuits. A new ioctl has been added
for this purpose. This option, however, has to be used
in conjunction with the "-v" option of x25stat command.
SR: 8606144441 / CR: JAGad13781
When "MALLOC with wait" is called with lock held, it
returns NULL even though there is enough memory. In
this case, the 'zx25drv' held the lock and called "MALLOC
with wait". This returns NULL, causing 'x25init' to
fail.
Resolution: The fix is to unlock the spinlock before
calling the MALLOC macro.
SR: 8606146312 / CR: JAGad15656
'x25init' command fails because there are not enough
number of terminal ZLU entries configured in the
".answ" file.
Resolution: The fix is to instruct the user of this
possible cause and to tune these parameters in .answ
file and then start-up the ZCOM subsystem.
SR: 8606146870 / CR: JAGad16213
After a PVC detach occurred (which causes the stream to
be closed), an inbound request queued on the read side
is passed upwards on a now invalid stream. This
resulted in the panic.
Resolution: The fix is to clear the read side "q_ptr"
field during the PVC detach processing which prevents
any request pending on the read side from being passed
upwards.
SR: 8606152276 / CR: JAGad21615
When the system was running out of memory, it would
cause the 'nli2zcom' to drop a data packet and issue a
'reset' request on the VC. This particular condition
caused many resets and reset confirmations to be issued
during heavy data transfer loads. The 'NLI2ZCOM' driver
showed that a reset request (or response) was being
sent to the 'DAM' driver at the same time that an inbound
event was arriving from the 'DAM' on the same card. The
'DAM' held the 'IFT' lock and passed the event to the
'NLI2ZCOM' driver which found the 'N2Z' lock already held.
The 'NLI2ZCOM' driver locked its spinlock and passed a
request to the 'DAM' which found the 'IFT' lock already
held. Thus a classic spinlock deadlock has occurred.
Resolution: The fix is to have the 'NLI2ZCOM' driver
drop its lock when issuing a request to the 'DAM' and
then re-acquire its lock upon return from the 'DAM'. This
was done for both the outbound 'Reset' Request and 'Reset'
Response functions.
SR: 8606197878 / CR: JAGad67069
When an 'x25stat' is done, the Max. Framesize that is
displayed is shown in bits instead of bytes.
Resolution: The code has been changed such that the
max frame size is displayed in bytes instead of bits.
SR: 8606197879 / CR: JAGad67070
The Spinlock timeout failure seems to be happening
because the function "N2z_Disable_ZLUs()" calls "zcntl()"
holding the "SPINLOCK(glock)". Because there are no
buffers available, the "Zc_gosleep()" is eventually
called which in turn calls "sleep()". This is causing
the spinlock timeout failure to occur because the
spinlock should not be held when the "sleep()" is called.
Resolution: Released the spinlock before calling the
zcntl() in function "N2z_Disable_ZLUs()".
SR: 8606151859 / CR: JAGad21198
The data page fault panic is because a NULL pointer was
dereferenced.
Resolution: To fix this problem a check has been added
to verify if the pointer is NULL.
PHNE_22253:
CR JAGad13782
Multiple connections over ACC/X25 are made.
After 5 days of intensive stress on the machine
it needs to be rebooted because of a memory
leak in the 512 bucket. The problem can be
reproduced on all possible systems running
hpux 11.00. The result found with vmtrace
activated on the dumps is shown below:
0 0x9c80000 512 0 Wed Jun 7 07:45:22
2000 vmtrace_kmalloc+0x1c8
kmalloc+0x5ec allocb+0x32c
N2z_iev_pass_data_up+0x210
N2z_ReadEvent_Recvd+0x1ea8
0 0x4b00000 512 0 Tue Jun 6 14:30:29 2000
vmtrace_kmalloc+0x1c8 kmalloc+0x5ec
allocb+0x32c
N2z_iev_pass_data_up+0x210
N2z_ReadEvent_Recvd+0x1ea8
Resolution:
Memory is now freed where ever applicable.
PHNE_20745:
CR JAGad03672
When "drain_outb_queue()" sends data to the 'DAM', it
must unlock the global spinlock in order to avoid
a potential spinlock deadlock between the lower
layer's and the 'nli2zcom' driver's spinlocks. Right
after the spinlock is unlocked, a write completion or
user level data requests can cause the write service
procedure to run resulting in additional data being
queued on the outbound data queues and
"drain_outb_queue()" being called reentrantly. Code is
already in place to detect the reentrant call and to
exit. However, the first instance thinks that it has
transmitted the entire message and calls freemsg.
This behavior is incorrect because the 2nd instance
appended data to the first instance's request and thus
when the first instance calls "freemsg()" it causes the
data from the 2nd instance to be thrown away and never
transmitted. Code has been added to detect the
reentrant call and to avoid calling "freemsg()" in this
special corner case.
CR JAGad03662
The format of the control write request used to tell the
card the threshold for forwarding inbound data to the
system was modified in the firmware but the drivers were
never updated. The 'nli2zcom' driver has been changed to
issue this request using the new format.
CR JAGad03531
The driver was not returning these values to 'x25stat'.
The code has been corrected.
CR JAGad03534
This problem was introduced in a prior patch due to a
logic error. The code has been corrected to only add
the default facilities configured through 'x25init' if
the called did not supply them.
CR JAGad02275
This panic occurs when the 'nli2zcom' driver's read
server is entered on a stream whose VC has been closed
and the VC's data structure deallocated (by x25stop).
The read server retrieves the pointer to the VC
structure from the 'RD(Q)->q_ptr' field and
dereferences it thereby causing the panic. The
"x25stop" processing code now sets the 'q_ptr' field
to NULL before deallocating the VC'structure.
CR JAGad01873
The panic occurred when "N2z_stop_link" tried to free the
ZCOM buffer that holds clear data for a VC. The pointer
to this buffer is maintained in the VC's 'clear_pkt' field.
Currently, neither the 'clear_pkt' or 'call_pkt' fields are
used and should always be zero. It appears that some stale
data somehow got into the field (which of course was not a
real ZCOM buffer). The system panic'd when an attempt was
make to free this buffer. This fix is to comment out all
calls to 'Zc_Mfree' for these two fields.
CR JAGad00253
When running internal tests, it was discovered that there
were several small memory leaks that existed when handling
a variety of exception conditions. Under some situations,
the number of exception conditions occurring can grow
exponentially causing the system to run out of memory
and hang. These memory leaks have been corrected.
CR JAGac42655
This problem occurred when an application that was
generating extreme traffic loads on 2000+ VCs is killed
(kill -9). The root cause is a violation of the streams
synchronization rules by the 'nli2zcom' driver. The driver
was issuing a 'flushq' call on the read queue from the write
side (wput). This caused Streams/UX to both free a
message and at the same time pass the message upwards to
the X.25/9000 layers. When the upper layers was finished
processing, it freed the message a second time resulting
in this panic. The 'nli2zcom' driver code has been modified
to use an alternative method for flushing its read side
queue which avoids calling 'flushq'. This method follows
the synchronization rules and therefore avoids this race
condition.
CR JAGab66344
The 'lanscan' program uses the results of the
X.25/9000 ioctl(X25_RD_HDW_PATH) which was recently
added. The ACC 'nli2zcom' driver did not implement this
functionality and just returned a null string. We now
return the full I/O path to the card associated with
the SNID in the ioctl request.
CR JAGac39375
The 'nli2zcom' drivers was supplying the correct
addresses, however the code was retrieve the address
lengths from the wrong fields in the VC structure. The
code has been modified to use the proper fields for the
address lengths.
CR JAGac39379
The driver returns these values through an ioctl
request. The driver needs to calculate the upper LCN
value based on the number of VCs and the starting LCN
value. This calculation was performed incorrectly
resulting in an upper LCN value that is always one
greater than it should be. The calculation has been
corrected.
CR JAGac39382
There was a logic error in the code which retrieved and
calculated the baud rate value. The logic error has
been corrected and the baud rate is now displayed with
its proper value.
CR JAGac42322
What is happening is that the zmasterd stop is
notifying the driver that the ZCOM subsystem is being
shutdown. The driver cleans up all the links and
detaches from 'ZCOM'. However, before ZCOM actually
begins its shutdown process another 'x25init' enters the
driver and causes it to reattach to ZCOM. The ZCOM
subsystem is then shutdown but the 'nli2zcom' driver
stills thinks its attached. The next time an 'x25init'
is run, it fails because the driver is using an invalid
program ZLU (check sums don't match). Code has been
added to the driver to detect this race condition and
to avoid it.
CR JAGab66351
The ksh and control scripts have been corrected to
follow the SD guidelines.
CR JAGab66277
All ACC scripts have been reviewed and a "PATH"
statement added containing the standard HP-UX
directories for various system utilities. This should
allow the scripts to find the utilities regardless of
the customer has setup the path environment variable.
CR JAGab72105
The problem was introduced by the C-compiler on 64-bit
systems. The compiler added padding to the beginning of
a data structure that was passed as a parameter to the
function which set the port configuration. This data
structure was a 4-byte union containing the port
configuration value. The padding caused the value to always
contain zero or some other random value. Therefore, the
card port could never be correctly configured using the
'n2z_pcfg' utility. The parameter type was changed to an
"int" instead of the union data structure which corrected
the problem.
CR JAGab68606
The code which logs this message was not supplying the mux,
port, and subchannel parameters causing random values to
be displayed. The code has been corrected.
CR JAGab73855
The problem was caused by walking off the end of the
'zx25_pda_infotbl' and 'n2z_zlu_tables' when the VC ZLU is
greater than the size of these tables.
This corrupted random areas of system memory leading to
the above panic.
CR JAGab84691
The ACC team is developing a new 8-port PCI serial card.
The ACC software and firmware needs to be enhanced to
support this new card.
CR JAGab84870
The problem occurs when an outbound disconnect request is
issued followed by a stream close on the VC stream
*before* the disconnect confirm packet arrives.
The disconnect request changes the type of the stream
context structure to "unknown". When the stream close
is issued, the code is unable to perform the proper
cleanup processing for the VC stream because the context
structure type is no longer assigned to a "VC" stream.
This allows the disconnect confirm packet to be delivered
to the upper half of the driver after the stream has been
closed which causes the system panic. The fix is
to delete the line that assigned the context structure
type to unknown when an outbound disconnect request is
issued.
CR JAGac29102
Under extremely heavy loads with insufficient streams
buffers being available, this panic can occur. An
outbound call is placed and when the call is confirmed,
if the driver is unable to allocate a streams buffer to
pass the call confirmation upward, the driver clears the
call by sending a clear indication up the stack and a clear
request down the stack. However, before the clear request
is processed, a VC up status, immediately followed by
inbound data arrives. The VC up status unconditionally
changes the state of the VC from clearing to data
transfer which allows the inbound data to be sent upwards.
The panic occurs when the VC data structures that have been
nulled by the clear request are referenced in the
processing of the inbound data packet. A change was made
to the VC up status processing to ignore this status if
the VC is in the clearing state. This causes the data
packet to be discarded rather then passed upwards and thus
avoids the panic.
CR JAGab29104
Sometimes an ACC problem can not be reproduced with
trace turned on due to timing differences. The
chances of reproducing a problem with trace turned
on increases with better performance of the trace code.
Also, with better performance, it can be acceptable
to leave trace permanently turned on for faster
troubleshooting.
CR JAGab66272
None.
CR JAGab66270
The VC stream context (V_sctx->stype) was unprotected in
'n2z_upper.c' and could change from a valid VC stream to an
unknown stream while executing
PHNE_20101:
CR JAGab82635
When the problem happened the test that is run uses lot
of sockets and closes them.At this time the timing is
such that the clear collision happens i.e., when
Disconnect request is sent to the remote and the remote
also sends a Disconnect (indication) and the 'Nli2zcom'
is not sending Disconnect confirmation to the upper
layers and simply terminates the circuit.
The upper layers wait for disconnect confirmation and
don't send close() on the stream until that is received.
So when the problem happened the 'Nli2zcom' driver was
not receiving close() and so Minor device table gets
full.
CR JAGab81509
"putq()" should be used instead of "putnext()".
When "putq()" is used we delegate the service thread
to do the job that way we are switching process context
and avoiding the stack overflow.
CR JAGab66316
By default the 'N2z_max_zlus' are defined 16K while the
'Zx25_max_zlus' are only 8K. So in a large configuration
where the Zlu # >8k , the zx25 driver does not check
for the zlu # and there by corrupts Sentry driver
structures. This leads to a Panic.
CR JAGab72034
System panic when zmasterd stop is done during 'x25init'
There is a race condition that happens when 'x25init' is
in progress and zcom subsystem is shutdown.
'X25init' goes to sleep waiting for the Zlus to be
enabled and if meanwhile the user shutsdown Zcom, the
shutdown process removes all the 'Nli2zcom' Link data
structures and marks the links / Vcs down.
Now if the Zlu enabled event happens , the driver tries
to access freed data and results in panic.
CR JAGab82415 / SR 8606109715
Memory leak of 2K stream buffers in call accept path.
In the normal path the driver was simply not freeing
the buffer.
CR JAGab72105
Using the "n2z_pcfg zx25m0p0 3 0x8000" command to set the
port to a LOOPBACK state is not working on the 64bit
system. The problem is - the parameter "0x8000" is not
properly passed to the N2z_Zcom_Port_Config() routine on
the 64bit system.
CR JAGab72028
A data structure being passed to the DAM was not aligned
correctly when compiled in a 64 bit environment
and the structure was modified to compile correctly.
CR JAGab66270
A race condition during shutdown leaves data structures
unprotected. Additional lock protection solves this
problem.
PHNE_19049:
CR JAGab66255
When an 'N_CI' call is issued (outbound call request)
and is rejected due to some reason, the 'N_DI' (disconnect
Indication ) passed to upper layers has Invalid QOS
fields.
When a packet is received with 'Mbit', sometimes the
'Dbit' is getting turned on.This is due to a bug
in the way the parenthesis are used in the logic.
However the driver was only incrementing the 'inb_npkts'
if both M&D bits are ON but not decrementing correctly.
This leads to sending flowcontrol to the remote once the
"inb_npkts > max_inb_pkts" but the flow control is
never turned off. 'inb_npkts' counter should be decremented
when a packet with M&D bit is moved up the stack.
When SNA with QLLC option is used on ACC , the inbound
data was queued using "putq" that causes performance
problem. This was done to work around a bug in SNA that
makes using "putnext" (faster) fail. Now that SNA
is fixed in a patch , we can undo this and use "putnext"
to queue inbound data for better performance.
The transient reject feature used by OTS expects the
Incoming call to be redirected to the Next listener
if the Call Reject is not Permanent. 'Nli2zcom' driver
had a logic problem that resulted in the call getting
queued to the first matching listener always.
DTS TPO0h02841 / SR 4701431023
The inbound flow control is incorrect handled by the 'N2Z'
driver. Also, the zksend call is used the wrong parameter.
TPO0h02756
The X.25/9000 product does not allow the 'T2' value to
be configured and does not pass in a reasonable value
to the ACC drivers when 'x25init' is run. This results
in the 'T2' timer not being configured correctly.
Modify the ACC 'nli2zcom' driver to set the 'T2' timer to
the value of the 'T1' timer divided by 2.
TPO0h02728
The 'NLI2ZCOM' driver was retrieving the mux, port, and
subchannel values from the wrong field of the stream
structure. In addition, the two IOCTL requests used to
perform this functionality had the wrong modes. These
two problems have been corrected.
TPO0h02696
When adding an X.25 link to a linked list of L2 PDAs
with pending writes to process, one of the source
statements that is used to add the L2 PDA to the linked
list was out of order causing the list to become corrupt.
Later when the list was traversed, the system would
panic. The source code statements were reordered
to correctly construct the linked list.
TPO0h02602
It is found that 'NLI2ZCOM' driver send it up 'M_FLUSH'
on receiving a Disconnect Indication but that will
stop at 'NLIFE's' lower side.
So all the buffers from 'NLIFE' toward the 'STREAM head'
are not flushed and so the Disconnect Indication MSG
sits behind the Data msgs and takes too long to
reach the Application.
TPO0h02561
panic+0x14
report_trap_or_int_and_panic+0x4c
interrupt+0x1ec
$ihndlr_rtn+0x0
nacc1_process_firqs+0x56c
nacc1_complete_req+0x1fe8
nacc1_end_io+0x26c
nacc1_int_event+0x1e8
nacc1_isr+0x14
wsio_interrupt+0x54
inttr_emulate_save_fpu+0x100
spinunlock+0x2c
settimeout_for_cpu+0xbc
timeout+0x34
lpmc_lumberjack+0x28
invoke_callouts_for_self+0xac
sw_service+0x94
This problem was caused when a request was issued
to the 'zx25dvr' from the 'nli2zcom' (N2Z) driver to
clear a VC which then failed due to lack of 'ZCOM'
memory used to build the clear request packet.The
'N2Z' driver passed up an 'M_ERROR' but the state of
the VC was not cleaned up in either the 'n2z' or
'zx25' drivers. Also, the "zksend()" function filtered
request for both normal write and control request
for a low memory condition.
When the remote side cleared the VC, it was passed
up by the 'zx25' driver to the 'n2z' which improperly
passed the clear up to the SISL code causing a
panic.
The "zksend()" function was modified to only reject
write requests when ZCOM memory runs low. Control
writes and control request are will continue to be
sent until ZCOM is completely out of memory.
The 'nli2zcom' driver was modified to detect a low
memory error from the 'zx25' request to clear a SVC.
In this case, the driver logs an error message and
disables and re-enables the X.25 link ZLU.
For non-memory errors, the SVC ZLU is disabled and
re-enabled. In both cases, 'M_ERROR' is no longer
called and success is returned to the upper layers
for the clear request. Note that the disable
request causes the VC to be cleared or the link to
be reset.
TPO0h01987
Enhancement request to implement the 'isdn_pcfg'
utility program to put the ISDN port into a
tristate( reconfigure the port pmode state).
DTS TPO0h01629:
There was no option to specify a different path for the
core dump directory. We have added the '-f' option that
allows an user to specify the full path of the core dump.
DTS TPO0h02703
While testing the OTS/9000 product with X25/ACC, the
routine "QVF_F_qos_to_x25fac()" returns an error code (-1),
when there is no error, when processing a disconnect
indication.
Enhancement:
No (superseded patches contained enhancements)
PHNE_23721:
This is an enhancement for "x25stat" command
to show "VC Up Time" for all active virtual
circuits.
SR:
8606306906 8606236935 8606289434 8606266220 8606259525
8606235666 8606231736 8606228520 8606227359 8606225328
8606171598 8606144441 8606146312 8606146870 8606152276
8606197878 8606197879 8606151859 8606144442 8606134537
8606134527 8606134396 8606134399 8606133128 8606132725
8606131096 8606125776 8606124015 8606124019 8606124022
8606125660 1653309682 8606112363 8606112521 8606114338
D500340299 8606110949 8606109934 8606108806 8606109715
4701431023
Patch Files:
ACC-SX25.ACC-SX25-KRN,fr=B.03.02.00,fa=HP-UX_B.11.00_32,
v=HP:
ACC-SX25.ACC-SX25-KRN,fr=B.03.10.00,fa=HP-UX_B.11.00_32,
v=HP:
ACC-SX25.ACC-SX25-KRN,fr=B.03.10.01,fa=HP-UX_B.11.00_32,
v=HP:
/usr/conf/acc/nli2zcom.h
/usr/conf/acc/n2z_trace.h
/usr/conf/lib/libn2z.a
/usr/conf/lib/libn2zsyms.o
/opt/acc/bin/n2ztrc
/opt/acc/bin/n2z_pcfg
/usr/conf/space.h.d/zsx25_space.h
/usr/conf/master.d/zsx25
ACC-SX25.ACC-SX25-KRN,fr=B.03.02.00,fa=HP-UX_B.11.00_64,
v=HP:
ACC-SX25.ACC-SX25-KRN,fr=B.03.10.00,fa=HP-UX_B.11.00_64,
v=HP:
ACC-SX25.ACC-SX25-KRN,fr=B.03.10.01,fa=HP-UX_B.11.00_64,
v=HP:
/usr/conf/acc/nli2zcom.h
/usr/conf/acc/n2z_trace.h
/usr/conf/lib/libn2z.a
/usr/conf/lib/libn2zsyms.o
/opt/acc/bin/n2ztrc
/opt/acc/bin/n2z_pcfg
/usr/conf/space.h.d/zsx25_space.h
/usr/conf/master.d/zsx25
ACC-SX25.ACC-SX25-RUN,fr=B.03.02.00,fa=HP-UX_B.11.00_32/64,
v=HP:
ACC-SX25.ACC-SX25-RUN,fr=B.03.10.00,fa=HP-UX_B.11.00_32/64,
v=HP:
ACC-SX25.ACC-SX25-RUN,fr=B.03.10.01,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/acc/bin/make_n2z_ipmap
/opt/acc/bin/make_n2z_route
/opt/acc/bin/make_n2z_x25init
/opt/acc/bin/n2z_cntrl
/opt/acc/lbin/add_n2z_nls
/opt/acc/lbin/make_n2z_devs
/usr/lib/nls/C/zx25fmt.cat
/etc/x25/x25init.sample
what(1) Output:
ACC-SX25.ACC-SX25-KRN,fr=B.03.02.00,fa=HP-UX_B.11.00_32,
v=HP:
/usr/conf/acc/nli2zcom.h:
$Header: nli2zcom.h/main/r3.10_r3.02/5 04/28/03 1
8:43:28 $
/usr/conf/acc/n2z_trace.h:
$Header: n2z_trace.h/main/r3.10_r3.02/2 03/12/03
10:42:55 $
/opt/acc/bin/n2ztrc:
ACC Rel B.03.10.01 for 32-bit B.11.00 PHNE_28606 n2z
trc
$ PATCH/11.00:PHCO_19491 Aug 9 1999 09:49:32 $
/opt/acc/bin/n2z_pcfg:
ACC Rel B.03.02 for B.11.00 PHNE_20101 $Header: n2z_
pcfg.c/main/3 10/18/98 21:50:07 $
$ PATCH/11.00:PHCO_16629 Oct 23 1998 15:31:36 $
/usr/conf/space.h.d/zsx25_space.h:
$Header: n2z_space.h/main/r3.10_r3.02/1 11/20/01
15:50:52 $
/usr/conf/lib/libn2z.a:
ACC Rel B.03.10.01 for 32-bit B.11.00 PHNE_28606 lib
n2z.a
/usr/conf/lib/libn2zsyms.o:
None
/usr/conf/master.d/zsx25:
None
ACC-SX25.ACC-SX25-KRN,fr=B.03.02.00,fa=HP-UX_B.11.00_64,
v=HP:
/usr/conf/acc/nli2zcom.h:
$Header: nli2zcom.h/main/r3.10_r3.02/5 04/28/03 1
8:43:28 $
/usr/conf/acc/n2z_trace.h:
$Header: n2z_trace.h/main/r3.10_r3.02/2 03/12/03
10:42:55 $
/opt/acc/bin/n2ztrc:
ACC Rel B.03.10.01 for 64-bit B.11.00 PHNE_28606 n2z
trc
$ PATCH/11.00:PHCO_19491 Aug 9 1999 09:56:42 $
/opt/acc/bin/n2z_pcfg:
ACC Rel B.03.02 for B.11.00 PHNE_20101 $Header: n2z_
pcfg.c/main/3 10/18/98 21:50:07 $
$ PATCH/11.00:PHCO_16629 Oct 23 1998 15:31:36 $
/usr/conf/space.h.d/zsx25_space.h:
$Header: n2z_space.h/main/r3.10_r3.02/1 11/20/01
15:50:52 $
/usr/conf/lib/libn2z.a:
ACC Rel B.03.10.01 for 64-bit B.11.00 PHNE_28606 lib
n2z.a
/usr/conf/lib/libn2zsyms.o:
None
/usr/conf/master.d/zsx25:
None
ACC-SX25.ACC-SX25-RUN,fr=B.03.02.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/acc/bin/make_n2z_ipmap:
None
/opt/acc/bin/make_n2z_route:
None
/opt/acc/bin/make_n2z_x25init:
None
/opt/acc/bin/n2z_cntrl:
ACC Rel B.03.10.01 for 32-bit B.11.00 PHNE_23722 $He
ader: n2z_cntrl.c/main/r3.10_r3.02/1 11/2
0/01 15:46:58 $
$ PATCH/11.00:PHCO_19491 Aug 9 1999 09:49:32 $
/opt/acc/lbin/add_n2z_nls:
None
/opt/acc/lbin/make_n2z_devs:
None
/usr/lib/nls/C/zx25fmt.cat:
None
/etc/x25/x25init.sample:
NACC x25init.sample $Rev: /main/3 $
cksum(1) Output:
ACC-SX25.ACC-SX25-KRN,fr=B.03.02.00,fa=HP-UX_B.11.00_32,
v=HP:
108255258 55075 /usr/conf/acc/nli2zcom.h
3587844265 57709 /usr/conf/acc/n2z_trace.h
4111119619 436336 /usr/conf/lib/libn2z.a
2544310981 273472 /usr/conf/lib/libn2zsyms.o
1601695024 249856 /opt/acc/bin/n2ztrc
3425167226 156368 /opt/acc/bin/n2z_pcfg
2528857527 10612 /usr/conf/space.h.d/zsx25_space.h
265170293 5566 /usr/conf/master.d/zsx25
ACC-SX25.ACC-SX25-KRN,fr=B.03.02.00,fa=HP-UX_B.11.00_64,
v=HP:
108255258 55075 /usr/conf/acc/nli2zcom.h
3587844265 57709 /usr/conf/acc/n2z_trace.h
4280520492 965794 /usr/conf/lib/libn2z.a
1388249573 340448 /usr/conf/lib/libn2zsyms.o
3083407996 338056 /opt/acc/bin/n2ztrc
3425167226 156368 /opt/acc/bin/n2z_pcfg
2528857527 10612 /usr/conf/space.h.d/zsx25_space.h
265170293 5566 /usr/conf/master.d/zsx25
ACC-SX25.ACC-SX25-RUN,fr=B.03.02.00,fa=HP-UX_B.11.00_32/64,
v=HP:
2797378038 9480 /opt/acc/bin/make_n2z_ipmap
3875774991 11013 /opt/acc/bin/make_n2z_route
3922711005 15082 /opt/acc/bin/make_n2z_x25init
3593047420 196608 /opt/acc/bin/n2z_cntrl
2423085775 6280 /opt/acc/lbin/add_n2z_nls
2007601403 4492 /opt/acc/lbin/make_n2z_devs
102571960 41753 /usr/lib/nls/C/zx25fmt.cat
209400739 676 /etc/x25/x25init.sample
Patch Conflicts: None
Patch Dependencies:
s700: 11.00: PHNE_26693 PHNE_23723
s800: 11.00: PHNE_26693 PHNE_23723
Hardware Dependencies: None
Other Dependencies:
To enable the feature mentioned in JAGad40862
ie. usage of "-u" option with x25stat command
to display "VC Up Time", the patch PHNE_23190
or its superseding patch must be installed.
Supersedes:
PHNE_19049 PHNE_20101 PHNE_20745 PHNE_22253 PHNE_23722 PHNE_26297
Equivalent Patches: None
Patch Package Size: 1370 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 PHNE_28606
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_28606.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_28606. 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 PHNE_28606.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHNE_28606.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_28606.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHNE_28606------------------------------------------
Document ID: PHCO_25514
Date Loaded: 20030519
Title: s700_800 11.00 libnss_files cumulative patch
Patch Name: PHCO_25514
Patch Description: s700_800 11.00 libnss_files cumulative patch
Creation Date: 03/04/09
Post Date: 03/05/19
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products: N/A
Filesets:
OS-Core.CORE-64SLIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
OS-Core.CORE-SHLIBS,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical:
No (superseded patches were critical)
PHCO_23189: CORRUPTION
Category Tags:
defect_repair general_release critical corruption
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_25514
Symptoms:
PHCO_25514:
( SR:8606258815 CR:JAGae23135 )
Daemon programs do not recognize changes made to the
system database files.
PHCO_23189:
Host file aliases cause static buffer allocation
overrun. JAGad40031
Memory leak when parsing netgroup. JAGad07432
PHCO_16039:
Threaded applications running on systems configured
to use the files name service may abort with a core
dump. JAGaa13611.
PHCO_14717:
gethostbyname() run performance in a kernel thread
environment while using /etc/hosts is low compared
to a process-based run. JAGaa01281.
Defect Description:
PHCO_25514:
( SR:8606258815 CR:JAGae23135 )
Changes made to system database files are not reflected
in daemon programs due to stdio buffering.
Resolution:
NSS files backend is modified so that any changes in
system database files are reflected in running programs
without delay.
PHCO_23189:
gethostbyname(3) returns garbage in hostname because
of the static buffer overflow which is used to hold
aliases for the hostname.
Resolution Description::
gethostbyname() returns garbage in hp->h_host because it
is not set to point to the first alias hp->h_aliases[0]
when the function __nss_netdb_aliases() returns zero.
The static buffer which is of size 2336 bytes allocated in
the function __nss_XbyY_buf_alloc() is used to store all
the aliases, inet addresses and pointer to all the aliases
for a given hostname.
Buffer containing all the aliases.
(abuf - abuf_start) - total length of all the aliases
args->buf.buffer - starting address of the buffer
(hp->h_addr_list - args->buf.buffer) - remaining length of
the buffer after filling the inet address to store the
aliases and pointer to aliases.
The function __nss_netdb_aliases() returns zero when the
buffer is not of sufficent length. This is the error case
and hence errno is set to args->erange = 1 and returning
from the function gethostbyname() with out setting the
hp->h_name.
Now this case is changed. When __nss_netdb_aliases()
function returns zero the hp->h_aliases is set to starting
address of the buffer and set hp->h_name to hp->h_aliases[0]
hp->h_aliases[0] contains the hostname. We display only the
aliases in the first line when there is a buffer overrun.
This is the behaviour in 10.20. The new variable nu_aliases
is added which holds the number of aliases present in the
first line
JAGad40031; SR 8606170767
The customer periodically experience mount problems from
their nfs clients, they get access denied error messages.
This happens because of the memory leak when parsing
netgroup.
Resolution Description:
The problem is fixed. the cause for the problem was
that there was an unnecessary memory being allocated in one
of the internal functions.
JAGad04732; SR 8606138231
PHCO_16039:
Threaded applications running on systems configured
to use the files name service may abort with a core
dump. JAGaa13611.
PHCO_14717:
_nss_files_read_line() in libnss_files.1 runs slowly
in kernel thread environment. JAGaa01281.
Enhancement:
No
SR:
8606258815 8606138231 8606170767
Patch Files:
OS-Core.CORE-64SLIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/lib/pa20_64/libnss_files.1
OS-Core.CORE-SHLIBS,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/lib/libnss_files.1
what(1) Output:
OS-Core.CORE-SHLIBS,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/lib/libnss_files.1:
$ PATCH/11.00:PHCO_25514 Apr 8 2003 08:01:36 $
OS-Core.CORE-64SLIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/lib/pa20_64/libnss_files.1:
$ PATCH/11.00:PHCO_25514 Apr 8 2003 08:01:50 $
cksum(1) Output:
OS-Core.CORE-SHLIBS,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
444813867 40960 /usr/lib/libnss_files.1
OS-Core.CORE-64SLIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
2329485476 45408 /usr/lib/pa20_64/libnss_files.1
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHCO_14717 PHCO_16039 PHCO_23189
Equivalent Patches: None
Patch Package Size: 110 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 PHCO_25514
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_25514.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_25514. 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 PHCO_25514.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHCO_25514.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_25514.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
If libnss_files patches are installed without rebooting,
applications currently running which are linked shared
against libnss_files will still continue using the
former version of libnss_files. If this presents a
problem to any applications, you should reboot.
-----End of Document ID: PHCO_25514------------------------------------------
Document ID: PHCO_28563
Date Loaded: 20030519
Title: s700_800 11.00 pwgrd(1M) cumulative patch
Patch Name: PHCO_28563
Patch Description: s700_800 11.00 pwgrd(1M) cumulative patch
Creation Date: 03/04/29
Post Date: 03/05/19
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products: N/A
Filesets:
OS-Core.UX-CORE,fr=B.11.00,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/PHCO_28563
Symptoms:
PHCO_28563:
pwgrd(1M) is sometimes not processing the requests
correctly when filesystem having /var/spool/pwgr
directory is full.
PHCO_28006:
1. pwgrd(1m) is intermittently consuming CPU time and not
responding to the requests coming to it.
2. pwgrd(1m) is not caching the user names after any
Invalid Entry in /etc/passwd.
PHCO_24586:
1.pwgrd(1M) does not store groupnames having more than
8 characters correctly.
2.Access problems with pwgrd(1M).
PHCO_18445:
There are multiple failures if the system is upgraded using
patch bundle.
PHCO_16796:
Postinstall script of the previous patch PHCO_14257
fails on 10.x systems.
PHCO_14257:
Previous patch PHCO_13497 doesn't install correctly on
new systems.
PHCO_13497:
When the system clock is set backwards and either
/etc/passwd, /etc/group or /etc/logingroup have a modify
time later than the clock. The symptom is that pwgrd
accumulates CPU time until the clock has passed the modify
time of the /etc/ files.
Defect Description:
PHCO_28563:
pwgrd(1M) sometimes not processing the request correctly
when the filesystem where /var/spool/pwgr directory
resides is full.
pwgrd(1M) maintains the hash files in /var/spool/pwgr/
directory and when the filesystem is full, hashtable
updation may fail. Since this error condition was not
handled pwgrd(1M) was processing the request incorrectly.
Resolution:
pwgrd(1M) has been modified to shutdown the hashing if
the hashtable updation fails, so that it does not uses
this hashtable for processing the request.
PHCO_28006:
1.pwgrd(1m) intermittently consumes CPU time and is not
responding to any request. This happens because the
flags associated with the hashtables were not updated
correctly.
Resolution :
The code has been modified to make sure that the
flags associated with the hashtables are updated
properly.
2.pwgrd(1m) is not caching the user/group information
after any Invalid Entry in /etc/passwd and /etc/group.
Eg.
=> If the /etc/passwd file has the following entries:
...
nobody:*:2:2::/:
www:*::1::/: -->THIS IS INVALID SINCE THERE IS NO UID.
user1:*:202:60::/mnt/user1:/usr/bin/ksh
...
=> Login as user1 and touch a file.
$ touch testfile
=> Check the ownership of this file.
$ ll testfile
<< WHEN PWGRD DAEMON IS NOT RUNNING >>
-rw-rw-rw- 1 user1 ssgrp 0 Dec 2 15:29 testfile
The user name of the file is correctly getting
displayed.
<< WHEN PWGRD DAEMON IS RUNNING >>
-rw-rw-rw- 1 202 ssgrp 0 Dec 2 15:29 testfile
Here ls(1) is not able to print the user name since
pwgrd(1m) is not caching the details of user1.
Resolution :
The code has been modified to make sure that all the
valid entries in /etc/passwd and /etc/group file is
cached.
PHCO_24586:
1.pwgrd(1M) can not handle groupnames more than 8
characters in length correctly. This was happening as
pwgrd(1M) used to truncate groupnames to 8 characters
before caching them. Then this truncated group name
used to append in the pwgrd output file.
Resolution:
The code has been modified to take care of the full
groupname(without truncation) to be appended to
pwgrd output file.
2.Access problems with pwgrd(1M).
Resolution:
The code has been modified to take care of the access
problems.
PHCO_18445:
The postinstall script which starts the pwgrd daemon is
executed immediately after the installation of patch.
The newly started pwgrd does not work properly when the
patch is installed through a patch bundle. Due to this
commands like chown, chgrp will fail in performing their
respective operations on patches getting installed after
the pwgrd patch in the bundle during installation.
Resolution:
The automatic startup of pwgrd daemon is moved from
postinstall to configure script. In case of patch bundle
installation, this script will run after the complete
installation of bundle. In case of single patch
installation, it will run immediately after the patch
installation.
PHCO_16796:
When upgrading a 10.x system to 11.00 Extension Software,
the Postinstall script of the patch PHCO_14257 fails with
a core dump. This is because, the Postinstall script tries
to start the 11.00 pwgrd on 10.x systems.
Resolution:
The /usr/sbin/pwgrd doesn't exist on 10.20. Therefore
if the machine is not 10.20 then only the the
/usr/sbin/pwgrd is started.
PHCO_14257:
Installing PHCO_13497 on a new system causes SD error
PHCO_13497:
pwgrd is always active, uses lots of CPU time
Enhancement:
No
SR:
8606292407 8606282157 8606278564 8606165796 8606108334
8606163498 4701424333 4701384453
Patch Files:
OS-Core.UX-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/sbin/pwgrd
what(1) Output:
OS-Core.UX-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/sbin/pwgrd:
Password/Group Caching/Hashing Daemon $Revision: 82.
25.1.9 $
PATCH_11_00: cache.o filetime.o hashtable.o hpux_rel
.o main.o misc.o server.o string_lst.o 03/04
/29
cksum(1) Output:
OS-Core.UX-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
3572776104 40960 /usr/sbin/pwgrd
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHCO_13497 PHCO_14257 PHCO_16796 PHCO_18445 PHCO_24586 PHCO_28006
Equivalent Patches:
PHCO_28007:
s700: 11.11
s800: 11.11
Patch Package Size: 50 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 PHCO_28563
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_28563.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_28563. 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 PHCO_28563.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHCO_28563.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_28563.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHCO_28563------------------------------------------
Document ID: PHSS_28547
Date Loaded: 20030519
Title: s700_800 11.11 AudioSubsystem Periodic Patch
Patch Name: PHSS_28547
Patch Description: s700_800 11.11 AudioSubsystem Periodic Patch
Creation Date: 03/04/23
Post Date: 03/05/19
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products:
AudioSubsystem B.11.11
Filesets:
AudioSubsystem.AUDIO-SRV,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
AudioSubsystem.AUDIO-SHLIBS,fr=B.11.11,fa=HP-UX_B.11.11_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_28547
Symptoms:
PHSS_28547:
1. Mixing 8-bit and 16-bit wav files causes sound
distortion.
2. 64 bit audio programs can not be created or run
on 11.11.
PHSS_27193:
1. AOpenAudio() doesn't work on 11.11
2. New Audio libraries not compatible with old Aserver
Defect Description:
PHSS_28547:
1. Audio problems mixing wav files with 8 and 16 bit
sample rate.
Resolution:
The delay is changed from 0.1 seconds to 3 seconds
to set the audio file parameters.
2. There is no libAlibkt for 11.11.
Resolution:
libAlibkt.1 is delivered.
PHSS_27193:
1. AOpenAudio() doesn't work on 11.11
2. New Audio libraries not compatible with old Aserver
Enhancement:
No
SR:
8606275973 8606287569 8606247423 8606261782
Patch Files:
AudioSubsystem.AUDIO-SRV,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
/opt/audio/bin/Aserver
/opt/audio/bin/asecure
AudioSubsystem.AUDIO-SHLIBS,fr=B.11.11,
fa=HP-UX_B.11.11_32/64,v=HP:
/opt/audio/lib/libAlibkt.1
/opt/audio/lib/pa20_64/libAlibkt.1
/opt/audio/lib/libAlib.1
/opt/audio/lib/libAlib.2
what(1) Output:
AudioSubsystem.AUDIO-SRV,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
/opt/audio/bin/Aserver:
X Window System, Version 11 R6+ HP-UX B.11.11.00 Per
iodic Patch Release
(build date: Mon Apr 21 20:33:14 IST 2003)
/opt/audio/bin/asecure:
X Window System, Version 11 R6+ HP-UX B.11.11.00 Per
iodic Patch Release
(build date: Fri May 31 18:40:12 IST 2002)
HP asecure v A.03.16 MP May 31 2002 14:24:09
AudioSubsystem.AUDIO-SHLIBS,fr=B.11.11,
fa=HP-UX_B.11.11_32/64,v=HP:
/opt/audio/lib/libAlibkt.1:
X Window System, Version 11 R6+ HP-UX B.11.11.00 Per
iodic Patch Release
(build date: Mon Apr 21 20:29:46 IST 2003)
/opt/audio/lib/pa20_64/libAlibkt.1:
X Window System, Version 11 R6+ HP-UX B.11.11.00 Per
iodic Patch Release
(build date: Mon Apr 21 20:29:50 IST 2003)
/opt/audio/lib/libAlib.1:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Per
iodic Patch Release
(build date: Fri May 31 18:13:52 IST 2002)
/opt/audio/lib/libAlib.2:
X Window System, Version 11 R6+ HP-UX B.11.11.00 Per
iodic Patch Release
(build date: Fri May 31 18:19:40 IST 2002)
cksum(1) Output:
AudioSubsystem.AUDIO-SRV,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
303034669 262144 /opt/audio/bin/Aserver
1898529025 69632 /opt/audio/bin/asecure
AudioSubsystem.AUDIO-SHLIBS,fr=B.11.11,
fa=HP-UX_B.11.11_32/64,v=HP:
3081813089 217088 /opt/audio/lib/libAlibkt.1
3383681740 228752 /opt/audio/lib/pa20_64/libAlibkt.1
3338424114 176128 /opt/audio/lib/libAlib.1
2250997178 184320 /opt/audio/lib/libAlib.2
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_27193
Equivalent Patches: None
Patch Package Size: 480 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_28547
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_28547.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_28547. 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_28547.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_28547.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_28547.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHSS_28547------------------------------------------
Document ID: PHSS_28548
Date Loaded: 20030519
Title: s700_800 11.11 AudioDevKit 2003 Periodic Patch
Patch Name: PHSS_28548
Patch Description: s700_800 11.11 AudioDevKit 2003 Periodic Patch
Creation Date: 03/04/24
Post Date: 03/05/19
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products:
HP-UX Audio Developer Kit B.11.11.01 B.11.11.02
Filesets:
AudioDevKit.AUDIO-PRG,fr=B.11.11.01,fa=HP-UX_B.11.11_32/64,v=HP
AudioDevKit.AUDIO-PRG,fr=B.11.11.02,fa=HP-UX_B.11.11_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_28548
Symptoms:
PHSS_28548:
1. 64 bit audio programs can not be created or run
on 11.11.
Defect Description:
PHSS_28548:
1. There is no libAlibkt for 11.11.
Resolution:
libAlibkt.1 is delivered.
Enhancement:
No
SR:
8606287569
Patch Files:
AudioDevKit.AUDIO-PRG,fr=B.11.11.01,fa=HP-UX_B.11.11_32/64,
v=HP:
AudioDevKit.AUDIO-PRG,fr=B.11.11.02,fa=HP-UX_B.11.11_32/64,
v=HP:
/opt/audio/lib/libAlibkt.sl
/opt/audio/lib/pa20_64/libAlibkt.sl
what(1) Output:
AudioDevKit.AUDIO-PRG,fr=B.11.11.01,fa=HP-UX_B.11.11_32/64,
v=HP:
/opt/audio/lib/libAlibkt.sl:
X Window System, Version 11 R6+ HP-UX B.11.11.00 Per
iodic Patch Release
(build date: Mon Apr 21 20:29:46 IST 2003)
/opt/audio/lib/pa20_64/libAlibkt.sl:
X Window System, Version 11 R6+ HP-UX B.11.11.00 Per
iodic Patch Release
(build date: Mon Apr 21 20:29:50 IST 2003)
cksum(1) Output:
AudioDevKit.AUDIO-PRG,fr=B.11.11.01,fa=HP-UX_B.11.11_32/64,
v=HP:
3081813089 217088 /opt/audio/lib/libAlibkt.sl
3383681740 228752 /opt/audio/lib/pa20_64/libAlibkt.sl
Patch Conflicts: None
Patch Dependencies:
s700: 11.11: PHSS_28547
s800: 11.11: PHSS_28547
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches: None
Patch Package Size: 20 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_28548
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_28548.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_28548. 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_28548.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_28548.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_28548.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHSS_28548------------------------------------------
Document ID: PHCO_27415
Date Loaded: 20030519
Title: s700_800 11.11 ls(1) cumulative patch
Patch Name: PHCO_27415
Patch Description: s700_800 11.11 ls(1) cumulative patch
Creation Date: 03/05/04
Post Date: 03/05/19
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_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/PHCO_27415
Symptoms:
PHCO_27415:
( SR:8606265148 CR:JAGae29476 )
ls(1) shows negative value for a link count more than 32767
( SR:8606203481 CR:JAGad72654 )
ll(1) displays a value 4294967295 as uid and gid for CD-ROM
files.
Defect Description:
PHCO_27415:
( SR:8606265148 CR:JAGae29476 )
When the link count of a file or directory is more than
32767,ls -l displays negative value for the link count.
This problem occurs because st_nlink is an unsigned short
variable and the contents of this is being assigned to a
signed short variable leading to truncation.
NOTE: In order to create more than 32767 hard links to
a file, a GR patch PHKL_28185 needs to be installed on the
system
Steps to reproduce the problem:
1. Create more than 32767 hard links to a file test_file.
2. $ls -l test_file
-rw-rw-rw- -32767 vts ssgrp 0 Mar 19 13:53 test_file
Resolution:
The code has been modified to use the correct data type to
take care of truncation problem.
( SR:8606203481 CR:JAGad72654 )
ll(1) or ls -l displays the positive UID/GID's for CD-ROM
files, but it should display the negative UID/GID's as per
the man page of stat(2).
An incorrect type specifier was used in the printf() API
for printing UID and GID values.
Steps to reproduce the problem:
1. Mount a CD-ROM on a mount point /test
2. ls -l /test
total 28672
-r-xr-xr-x 1 4294967295 4294967295 4998 Feb 8 2002
HPII_FAQ.TXT
dr-xr-xr-x 1 4294967295 4294967295 2048 Feb 8 2002
PCINSTAL
Resolution:
The correct type specifiers are being used now,for printing
the UID and GID values.
Enhancement:
No
SR:
8606203481 8606265148
Patch Files:
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/sbin/ls
/usr/bin/l
/usr/bin/lc
/usr/bin/ll
/usr/bin/ls
/usr/bin/lsf
/usr/bin/lsr
/usr/bin/lsx
what(1) Output:
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/sbin/ls:
ls.c $Date: 2003/03/13 02:04:47 $Revision: r11.11/2
PATCH_11.11 (PHCO_27415)
$Revision: (#) all CUP11.11_BL2003_0504_1 PATCH_11.
11 PHCO_27415
Sun May 4 22:45:01 PDT 2003 $
$ Version_11.11 Mar 31 2003 09:02:37 $
/usr/bin/l:
ls.c $Date: 2003/03/13 02:04:47 $Revision: r11.11/2
PATCH_11.11 (PHCO_27415)
$Revision: (#) all CUP11.11_BL2003_0504_1 PATCH_11.
11 PHCO_27415
Sun May 4 22:44:52 PDT 2003 $
/usr/bin/lc:
ls.c $Date: 2003/03/13 02:04:47 $Revision: r11.11/2
PATCH_11.11 (PHCO_27415)
$Revision: (#) all CUP11.11_BL2003_0504_1 PATCH_11.
11 PHCO_27415
Sun May 4 22:44:52 PDT 2003 $
/usr/bin/ll:
ls.c $Date: 2003/03/13 02:04:47 $Revision: r11.11/2
PATCH_11.11 (PHCO_27415)
$Revision: (#) all CUP11.11_BL2003_0504_1 PATCH_11.
11 PHCO_27415
Sun May 4 22:44:52 PDT 2003 $
/usr/bin/ls:
ls.c $Date: 2003/03/13 02:04:47 $Revision: r11.11/2
PATCH_11.11 (PHCO_27415)
$Revision: (#) all CUP11.11_BL2003_0504_1 PATCH_11.
11 PHCO_27415
Sun May 4 22:44:52 PDT 2003 $
/usr/bin/lsf:
ls.c $Date: 2003/03/13 02:04:47 $Revision: r11.11/2
PATCH_11.11 (PHCO_27415)
$Revision: (#) all CUP11.11_BL2003_0504_1 PATCH_11.
11 PHCO_27415
Sun May 4 22:44:52 PDT 2003 $
/usr/bin/lsr:
ls.c $Date: 2003/03/13 02:04:47 $Revision: r11.11/2
PATCH_11.11 (PHCO_27415)
$Revision: (#) all CUP11.11_BL2003_0504_1 PATCH_11.
11 PHCO_27415
Sun May 4 22:44:52 PDT 2003 $
/usr/bin/lsx:
ls.c $Date: 2003/03/13 02:04:47 $Revision: r11.11/2
PATCH_11.11 (PHCO_27415)
$Revision: (#) all CUP11.11_BL2003_0504_1 PATCH_11.
11 PHCO_27415
Sun May 4 22:44:52 PDT 2003 $
cksum(1) Output:
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
3236820252 294912 /sbin/ls
93218879 28672 /usr/bin/l
93218879 28672 /usr/bin/lc
93218879 28672 /usr/bin/ll
93218879 28672 /usr/bin/ls
93218879 28672 /usr/bin/lsf
93218879 28672 /usr/bin/lsr
93218879 28672 /usr/bin/lsx
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches: None
Patch Package Size: 340 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 PHCO_27415
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_27415.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_27415. 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 PHCO_27415.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHCO_27415.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_27415.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHCO_27415------------------------------------------
Document ID: PHKL_28999
Date Loaded: 20030519
Title: s700_800 11.11 getmount_entry;rename;creat;[u]mount;VxFS3.5
Patch Name: PHKL_28999
Patch Description: s700_800 11.11 getmount_entry;rename;creat;[u]mount;VxFS3.5
Creation Date: 03/05/08
Post Date: 03/05/19
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical: No
Category Tags:
defect_repair enhancement general_release
manual_dependencies
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_28999
Symptoms:
PHKL_28999:
( SR:8606295554 CR:JAGae59236 )
Automount fails to mount cdfs with PHKL_26239
and returns EBUSY. The problem is noticed when
mounting non-NFS file systems using direct
maps and not with indirect maps. This problem
can also cause Block-Level Incremental Backups (BLIB)
performed with the Veritas NetBackup application
to fail with errno 16 (EBUSY).
PHKL_27800:
( SR:8606263709 CR:JAGae28034 )
This product update is member of a set needed to enable
the optional HP-UX support for VxFS 3.5 Cluster mount
feature. Upon installation, the HP-UX BaseVxFS bundle
will install the full set of product updates (including
this one) necessary to enable the support for VxFS 3.5
Cluster mount feature.
If the HP-UX VxFS 3.5 product is not installed, this
product update will have no impact on your system.
( SR:8606198319 CR:JAGad67509 )
This product update is member of a set needed to enable
the optional HP-UX VFS support for VxFS 3.5. Upon
Installation, the HP-UX Base VxFS bundle will install the
full set of product updates (including this one) necessary
to enable the VFS support for VxFS 3.5.
If the HP-UX VxFS 3.5 product is not installed, this product
update will have no impact on your system.
PHKL_26239:
( SR:8606247419 CR:JAGae13857 )
Enhancement: This product update is a member of a set
which improve the performance of mount(2) and umount(2).
The full list of product updates that address this
performance improvement are: PHKL_26239, PHKL_26694,
PHKL_26695, PHKL_26698, and PHKL_27211.
Each of these product updates may be installed independently
of the others. Each provides an incremental performance
improvement.
( SR:8606241982 CR:JAGae09237 )
Enhancement: Provide device major numbers that are suitable
for use in /etc/mnttab.
( SR:8606260639 CR:JAGae24962 )
opendir(3C) performance may be quite slow when there are a
lot of directories involving long path names.
( SR:8606178913 CR:JAGad48138 )
Either or both of the following symptoms may appear
on a given system:
1. Service Guard may experience umount(2) failures.
2. System throughput and/or response time may degrade when
CPUs are added to a configuration that executes a
significant number of calls to getcwd(3).
PHKL_23239:
( SR:8606175337 CR:JAGad44579 )
Overall system throughput degradation when getmount_entry()
and getmount_cnt() hit contention for the filesys_sema (an
alpha semaphore).
PHKL_26749:
( SR:8606248238 CR:JAGae14638 )
creat(2) system call fails with ENOENT.
PHKL_26099:
( SR:8606233922 CR:JAGae03145 )
Applications using rename(2) may run slower than necessary.
Defect Description:
PHKL_28999:
( SR:8606295554 CR:JAGae59236 )
A flag is incorrectly checked when adding a VFS structure
outside of the normal mount code path. The flag is
properly checked in the normal mount code path, so the
additional check is not needed.
Resolution:
The fix is to remove the check of the flag when adding a
vfs structure.
PHKL_27800:
( SR:8606263709 CR:JAGae28034 )
This product update contains minor enhancements required to
enable the HP-UX support for VxFS 3.5 Cluster mount.
Resolution:
Enhancements added to disallow mounting another file system
within a VxFS 3.5 Cluster mount.
( SR:8606198319 CR:JAGad67509 )
This product update contains minor enhancements required to
enable the HP-UX VFS support for VxFS 3.5.
Resolution:
Enhancements added to remove VxFS 3.5 entries from VFS
switch table.
PHKL_26239:
( SR:8606247419 CR:JAGae13857 )
This product update contains minor changes necessary to
improve the performance of mount(2) and umount(2) for all
file systems. We incorrectly held a lock to serialize all
access to all file systems for mount/umount service calls.
These file systems specific operations are already
serialized where necessary, and the additional higher
level serialization results in unnecessary performance
degradation.
Resolution:
Removed the unnecessary use of a file system lock that used
to unconditionally serialize all access to all file systems
for mount/umount service calls.
( SR:8606241982 CR:JAGae09237 )
Device major numbers are currently assigned the value 0xff.
This value can not be used in /etc/mnttab, which needs a
value between 0x0 and 0x7f.
Resolution:
Provide device major numbers that are in the 0x0 to 0x7f
range.
( SR:8606260639 CR:JAGae24962 )
opendir(3C) uses open(2) and stat(2) calls, each with path
name parameters. With large numbers of directories, there
are multiple calls to open(2) and stat(2).
Resolution:
open(2) already has access to the information provided by
stat(2) to opendir(3C). opendir(3C) uses open(2) with a new
parameter to gain access to this additional information,
thus avoiding the additional call to stat(2).
( SR:8606178913 CR:JAGad48138 )
The mechanism for retrieving information about mounted
file systems from the kernel is extremely inefficient.
Its cost is essentially a quadratic function
of the number of mounted file systems.
Resolution:
Added a new system call to retrieve information for all
currently mounted file systems, which makes the performance
linear with the number of mounted file systems.
PHKL_23239:
( SR:8606175337 CR:JAGad44579 )
It is not efficient to use the alpha semaphore to serialize
access to the list of vfs structs.
Resolution:
Use the rootvfs_lock (a simple spinlock) instead of the
filesys_sema to serialize access to the list of vfs structs.
PHKL_26749:
( SR:8606248238 CR:JAGae14638 )
creat(2) races with unlink(2) allowing a ENOENT failure.
Resolution:
The function that creates a file, vn_create(), was
modified to return a referenced vnode to the open
function, vn_open(), thereby eliminating the original
race with unlink(2).
PHKL_26099:
( SR:8606233922 CR:JAGae03145 )
rename(2) always gets the file system semaphore,
even though it is not needed for mp safe file systems,
which include HFS and JFS.
Resolution:
rename(2) will only get the file system semaphore
for file systems that are not mp safe.
Enhancement:
No (superseded patches contained enhancements)
PHKL_27800:
Enhancements added to disallow mounting another
file system within a VxFS 3.5 Cluster mount and to
remove VxFS 3.5 entries from VFS switch table, when
this product is configured.
Additional enhancements were delivered in a patch
this one has superseded. Please review the Defect
Description text for more information.
SR:
8606175337 8606178913 8606198319 8606233922 8606241982
8606247419 8606248238 8606260639 8606263709 8606295554
Patch Files:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libfs.a(vfs.o)
/usr/conf/lib/libfs.a(vfs_scalls.o)
/usr/conf/lib/libfs.a(vfs_vnode.o)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libfs.a(vfs.o)
/usr/conf/lib/libfs.a(vfs_scalls.o)
/usr/conf/lib/libfs.a(vfs_vnode.o)
what(1) Output:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libfs.a(vfs.o):
vfs.c $Date: 2003/05/04 23:42:24 $Revision: r11.11/7
PATCH_11.11 (PHKL_28999)
/usr/conf/lib/libfs.a(vfs_scalls.o):
vfs_scalls.c $Date: 2002/01/16 13:02:55 $Revision: r
11.11/1 PATCH_11.11 (PHKL_26099)
/usr/conf/lib/libfs.a(vfs_vnode.o):
vfs_vnode.c $Date: 2002/05/22 10:09:42 $Revision: r1
1.11/4 PATCH_11.11 (PHKL_26239)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libfs.a(vfs.o):
vfs.c $Date: 2003/05/04 23:42:24 $Revision: r11.11/7
PATCH_11.11 (PHKL_28999)
/usr/conf/lib/libfs.a(vfs_scalls.o):
vfs_scalls.c $Date: 2002/01/16 13:02:55 $Revision: r
11.11/1 PATCH_11.11 (PHKL_26099)
/usr/conf/lib/libfs.a(vfs_vnode.o):
vfs_vnode.c $Date: 2002/05/22 10:09:42 $Revision: r1
1.11/4 PATCH_11.11 (PHKL_26239)
cksum(1) Output:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
3221125061 24556 /usr/conf/lib/libfs.a(vfs.o)
3115512741 35672 /usr/conf/lib/libfs.a(vfs_scalls.o)
4190002545 10904 /usr/conf/lib/libfs.a(vfs_vnode.o)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
1548406516 68584 /usr/conf/lib/libfs.a(vfs.o)
2033759386 92880 /usr/conf/lib/libfs.a(vfs_scalls.o)
160674366 25856 /usr/conf/lib/libfs.a(vfs_vnode.o)
Patch Conflicts: None
Patch Dependencies:
s700: 11.11: PHCO_27120
s800: 11.11: PHCO_27120
Hardware Dependencies: None
Other Dependencies:
PHKL_26239: This product update, along with PHCO_27910
(libc) and PHKL_26467 (new system call), provide the
enabling performance enhancement for accessing information
about mounted file systems. The following set of product
updates: PHCO_26242, PHCO_27120, PHCO_26331, PHCO_26332,
PHCO_26333 and PHCO_26334 each take advantage of this
performance enhancement, and thus provide incremental
performance improvements. Each of these product updates may
be installed independently of each other, and in any order.
The three enabling product updates, plus at least one of the
others are necessary to see an improvement in performance.
None are required if this enhancement is not desired.
PHKL_26239: opendir(3C) performance requires product update
PHCO_27910 (libc). Each of these product updates may be
installed independently of each other, in any order, or
not at all if this enhancement is not desired.
Supersedes:
PHKL_27800 PHKL_26749 PHKL_26239 PHKL_26099 PHKL_23239
Equivalent Patches: None
Patch Package Size: 120 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 PHKL_28999
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_28999.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_28999. 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 PHKL_28999.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHKL_28999.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_28999.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHKL_28999------------------------------------------
Document ID: PHKL_29039
Date Loaded: 20030519
Title: s700_800 11.11 SCSI IO Cumulative Patch
Patch Name: PHKL_29039
Patch Description: s700_800 11.11 SCSI IO Cumulative Patch
Creation Date: 03/04/30
Post Date: 03/05/19
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
ProgSupport.C-INC,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_29039: MEMORY_LEAK HANG
PHKL_28513: PANIC CORRUPTION
PHKL_28096: HANG
PHKL_27579: PANIC HANG
PHKL_27563: HANG
PHKL_26519: PANIC HANG
PHKL_25896: ABORT HANG
PHKL_25509: HANG
PHKL_25165: OTHER PANIC HANG
Boot and ioscan time is improved on large
configurations.
Enhancements are made to support c8xx ioctl's.
PHKL_23313: PANIC HANG CORRUPTION MEMORY_LEAK
PHKL_24441: PANIC HANG
Category Tags:
defect_repair hardware_enablement enhancement
general_release critical panic halts_system corruption
memory_leak
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_29039
Symptoms:
PHKL_29039:
( SR:8606244397 CR:JAGae10884 )
When an error is encountered in the bus or target
open routines, the system exhausts its memory due
to memory leak.
( SR:8606290867 CR:JAGae54710 )
Incorrect block device activity data is reported
by sar(1M) when the disks have failed operations.
( SR:8606267129 CR:JAGae31372 )
When I/O errors happen, the syslog file
shows negative values for the buffer
pointer fields.
( SR:8606266450 CR:JAGae30698 )
Default SCSI diagnostic logging is severely limited by
PHKL_25165.
( SR:8606160884 CR:JAGad30203 )
Devices belonging to class SCSI_PROCESSOR
are reported as UNCLAIMED by ioscan(1M).
( SR:8606298657 CR:JAGae62156 )
Application hang due to error returned by the SCSI
driver.
( SR:8606307922 CR:JAGae70957 )
I/O request failing with 'Reservation Conflict' are retried
forever resulting in application hang.
PHKL_28513:
( SR:8606226043 CR:JAGad95114 )
Data integrity issues or HPMC with Channel B of A5159A and
Core I/O FWD SCSI HBA on the following systems:
rp24xx (A-class), rp54xx (L-class), rp7400 (N-class).
Description field in ioscan output for affected Core I/O
FWD SCSI cards will contain string 'C87x'.
( SR:8606286272 CR:JAGae50215 )
SCSI controllers with 896 chip(revision 4) under certain
circumstances may send wrong data on the SCSI bus after
a bus reset.
( SR:8606289589 CR:JAGae53519 )
Panic in SCSI stack with the following trace:
panic+0x14
wait_for_lock+0x2cc
call_wait_for_lock+0x20
scsi_start+0x50
scsi_free_scb+0xac
scsi_strategy_real+0xcd4
ioforw_sched+0xa4
scsi_cmd+0x3a4
scsi_probe+0x444
parallel_scsi_probe+0x1b4
wsio_probe+0xe0
wsio_find_it+0x34
wsio_scan+0x70
gio_scan_subtree+0x188
gio_scan_subtree+0x1c4
gio_scan_subtree+0x1c4
gio_scan_subtree+0x1c4
gio_scan_subtree+0x1c4
gio_scan_subtree+0x1c4
io_scan+0x9c
do_io_scan+0x48
dev_config_ioctl+0xd8
spubind_cdev_ioctl+0x94
spec_ioctl+0xac
vno_ioctl+0x90
ioctl+0x1f4
syscall+0x28c
$syscallrtn+0x0
PHKL_28096:
( SR:8606271035 CR:JAGae35271 )
In a mirrored disk environment on rp8400/rp7410
systems, if one of the internal disks fails and
is hot-swapped, the alternate disk does not
spin up, thus resulting in an application hang.
PHKL_27579:
( SR:8606245156 CR:JAGae11630 )
The system will HPMC when a bus reset occurs
on an A5838A SCSI HBA.
( SR:8606242143 CR:JAGae09397 )
The system may experience intermittent bus
hangs followed by resets on the ports of the
A5159A card and Core I/O FWD SCSI HBA
on the following systems: rp24xx (A-class),
rp54xx (L-class), rp7400 (N-class), rp8400,
when connected to a disk enclosure.
( SR:8606241873 CR:JAGae09130 )
The ioscan may hang and on the following reboot
the system panics with a stack trace that is
not consistent.
( SR:8606216118 CR:JAGad85288 )
When the SCSI bus is being opened, if an
interrupt is serviced at the same time, the
system panics with the following stack trace:
panic+0x14
report_trap_or_int_and_panic+0x84
interrupt+0x1d4
$ihndlr_rtn+0x0
c720_isr+0x890
sapic_interrupt+0x2c
mp_ext_interrupt+0x318
ivti_patch_to_nop3+0x0
bz_pre_sl_loop+0x4
c720_if_bus_open+0x318
scsi_lun_open+0x12d4
sctl_open+0x24
scsi_probe+0x370
parallel_scsi_probe+0x1a8
wsio_probe+0xe0
wsio_find_it+0x34
wsio_scan+0x70
gio_scan_subtree+0x188
gio_scan_subtree+0x1c4
gio_scan_subtree+0x1c4
io_scan+0x9c
do_io_scan+0x48
dev_config_ioctl+0xd8
spubind_cdev_ioctl+0x94
spec_ioctl+0xac
vno_ioctl+0x90
ioctl+0x1f4
syscall+0x480
$syscallrtn+0x0
( SR:8606257328 CR:JAGae21633 )
Application may hang after an OLAR card resume
operation if the card has been suspended while
a SCSI bus reset was in progress.
( SR:8606204859 CR:JAGad74037 )
SCSI driver can not communicate with the target
(nCipher encryption device) that initiates speed
and width negotiation. This results in parity
errors on the SCSI bus and as a result SCSI bus
resets.
( SR:8606232873 CR:JAGae02101 )
I/O errors may occur when attempting to do more
than one backup on tape.
( SR:8606238711 CR:JAGae07734 )
LVM is not switching to an alternate path
due to an error returned by the SCSI driver.
( SR:8606264850 CR:JAGae29181 )
open() on CDROM drive takes too long when no
CD is present.
PHKL_27563:
( SR:8606265990 CR:JAGae30243 )
I/O hang due to a pending I/O request in the lun disk
queue.
PHKL_26519:
( SR:8606236118 CR:JAGae05183 )
When an LVM I/O request to a SCSI device fails or times out,
any subsequent failed I/O requests to same LUN are returned
with error without being retried by the SCSI disk driver.
( SR:8606226361 CR:JAGad95431 )
Applications may hang due to incorrect SCSI error handling
introduced in patch PHKL_24441.
( SR:8606135832 CR:JAGad04964 )
Enhancement: This product update enables the support for 16
byte CDBs (Command Descriptor Block) in the SCSI driver.
( SR:8606214047 CR:JAGad83238 )
The system may experience a HPMC when a SCSI adapter is
suspended through use of the OLA/R functions accessible
through rad(1M) and sam(1M).
( SR:8606236116 CR:JAGae05181 )
When PHKL_24441 is installed and LVM is trying to switch
from the primary path to an alternate path, the SCSI
subsystem may report false read errors to LVM.
PHKL_25896:
( SR:8606228002 CR:JAGad97060 )
Some disks report a capacity of zero bytes at cold boot or
cold install. This causes the initial boot or install after
a cold start to fail.
PHKL_25509:
( SR:8606203627 CR:JAGad72800 )
There is no way to turn off c720 interface driver
vmunix: scb->cdb: %x %x %x %x %x %x
messages in syslog.log, while other related messages can be
suppressed.
( SR:8606186960 CR:JAGad56170 )
A high number of
SCSI: asense data-done -- lbolt %d, dev: %x, tag: %x
messages may be logged in syslog.log when using Plasmon
optical drives.
( SR:8606201476 CR:JAGad70652 )
The following informative message on the console and in
syslog.log causes unnecessarily alarm by customers:
SCSI: Attempt to access partially open device -- dev: %x
( SR:8606199892 CR:JAGad69078 )
On HP SureStore E Disk Array 12 (A3586A), processes can hang
with the following message in the syslog.log:
Device violation of Contingent Allegiance
( SR:8606194472 CR:JAGad63680 )
On workstation model C3700, the external narrow SCSI bus is
setup incorrectly. The 'diskinfo' command returns invalid
information and I/O's on this bus hang.
( SR:8606177456 CR:JAGad46688 )
It takes an unreasonable amount of time to import Disk
Groups with the VxVM volume manager on a FC60 array.
PHKL_25165:
( SR:8606207855 CR:JAGad77032 )
The ioctl system call returns invalid values if called with
SIOC_GET_TGT_LIMITS or SIOC_GET_TGT_PARMS parameters for a
SCSI device controlled by the c8xx driver.
( SR:8606170140 CR:JAGad39404 )
Well functionning systems with Fibre Channel devices
generate an excessive number of logs. This causes log files
cluttering, diag2 daemon overrun or /var filesystem free
space exhaustion.
( SR:8606172682 CR:JAGad41942 )
With the per lun queue depth feature, queue depth
modification on a lun that does not support tag queueing is
not rejected, even though the queue depth on such a device
cannot be modified.
Queue depth can be changed only once on devices supporting
tag queueing.
( SR:8606166652 CR:JAGad35939 )
If an application uses the sctl/ioctl passthrough interface
with the read/write data size mismatching the buffer size,
the system experiences a Data Page Fault panic with the
following routines on the stack:
panic+0x14
report_trap_or_int_and_panic+0x4c
interrupt+0x1e8
$ihndlr_rtn+0x0
lbcopy_pcxu_method+0xc
privlbcopy+0x1c
( SR:8606192639 CR:JAGad61851 )
The system boot time and ioscan command (without -k option)
time are too long, especially in a system with a large Fibre
Channel Array configuration.
( SR:8606189054 CR:JAGad58270 )
If many processes access the same bus, some processes might
become unkillable. This error condition has been experienced
only on systems with a hundred or more luns on the same bus.
( SR:8606166664 CR:JAGad35951 )
A system with 2 ALT 8-series DLT (Quantum 4000) on the same
card showed the following panic:
panic: (display==0xb800, flags==0x0) Data page fault 1111
The stack trace was:
scsi_start+0x18
scsi_retry+0xd8
invoke_callouts+0x160
softclock+0x38
sw_service+0x154
mp_ext_interrupt+0x2a0
$RDB_int_patch+0x58
mpn_splx_free_lock_ul4_brn_target+0x4
net_callout+0x90
netisr_netisr+0x1bc
netisr_daemon+0x68
PHKL_23313:
( SR:8606174670 CR:JAGad43916 )
Compiling kernel-intrusive programs (such as drivers and
programs that access /dev/mem or /dev/kmem) on HP-UX 11.11
may result in compiler warnings or errors due to namespace
violations. Executing such programs may cause kernel
structure data corruption, resulting in memory leaks, hangs,
or panics.
PHKL_24441:
( SR:8606173682 CR:JAGad42939 )
High Availability systems hang when under heavy load
and many I/O errors are being returned by the scsi
driver (possibly due to a hardware problem).
( SR:8606175843 CR:JAGad45083 )
A defective SCSI bus controller generates continuous
SCSI bus resets and causes the system to panic.
The panic results in the following stack trace:
panic+0x14
settimeout_for_cpu+0x174
Ktimeout+0x3c
c720_reset_chip+0x129c
c720_isrRST+0x94
c720_isr+0x15cc
sapic_interrupt+0x2c
( SR:8606176606 CR:JAGad45845 )
If device tracing is enabled (with appropriate values
for scsi_trace_dev and scsi_trace_mask, typically for
debugging) and when the system experiences errors
during I/O through the passthrough driver, the system
panics.
panic+0x14
report_trap_or_int_and_panic+0x80
interrupt+0x1d4
$ihndlr_rtn+0x0
scsi_dmesg_log_io+0xf8
scsi_action+0x1b8
scsi_status_action+0x6c
scsi_cbfn+0x41c
scsi_fast_cbfn+0x1b0
c720_call_cbfns+0x60
c720_isr+0x5bc
epic_isr+0x58
mp_ext_interrupt+0x34c
ivti_patch_to_nop3+0x0
idle+0x164
swidle_exit+0x0
( SR:8606173887 CR:JAGad43140 )
There are various symptoms as described under the
following CRs.
( SR:8606169027 CR:JAGad38305 )
Disk I/O hangs even when LVM PV-Link is configured.
The system could report a "DIAGNOSTIC SYSTEM WARNING".
The on-line diagnostic log would show an I/O Error.
( SR:8606178152 CR:JAGad47379 )
Process hang can result during a device open. The system
log (/var/adm/syslog/syslog.log) shows Queue Full status
and a large retry count on an Inquiry request.
( SR:8606168578 CR:JAGad37858 )
The process hangs if an ioctl is issued to a non-existent
hardware path.
( SR:8606178041 CR:JAGad47268 )
"vgchange -a n <VG Name>" command hangs when the cable is
disconnected on the alternate link, if immediate
reporting (IR) is true.
( SR:8606167814 CR:JAGad37097 )
ioscan -fn command hangs when there is a bad disk present.
( SR:8606139670 CR:JAGad08981 )
The system panics when a certain type of SCSI error
occurs while doing writes on hfs filesystem.
The /var/adm/syslog/syslog.log reports Check Condition
status with sense key: (03) Medium Error.
( SR:8606166721 CR:JAGad36008 )
When a bus is shared between two systems, if one of the
systems continuously sends out bus resets, the I/Os from
the other system on this bus hang, consequently the
PV-Link switch would not occur.
Defect Description:
PHKL_29039:
( SR:8606244397 CR:JAGae10884 )
The system exhausts its memory due to memory leak because
of not freeing a data structure in the error
path.
Resolution:
Free the data structure when the error path
is taken in the bus or target open routines
to plug the memory leak.
( SR:8606290867 CR:JAGae54710 )
The disk failure paths do not ensure that
kmetric completion routines are called
to update the block device activity data.
This results in incorrect data being reported
for block device activity.
Resolution:
The kmetric completion routines are called in the
disk driver error paths to ensure that the
correct values are reported for block device activity.
( SR:8606267129 CR:JAGae31372 )
The I/O routine prints the buffer pointer fields as signed
values. This results in reporting of negative values to
syslog output.
Resolution:
The I/O error routine is modified to
print the buffer pointer fields as
unsigned values.
( SR:8606266450 CR:JAGae30698 )
The SCSI logging policy introduced in PHKL_25165
restricted the SCSI logs to prevent unwanted messages.
This limits the debugging efforts of test engineers.
Resolution:
A new flag is introduced in the scsi_log_mask variable
that can be set through adb(1). Setting this flag would
enable original logging behavior, if required.
( SR:8606160884 CR:JAGad30203 )
Devices which report their class as SCSI_PROCESSOR
are not claimed by any driver and hence are
reported as UNCLAIMED.
Resolution:
Devices which belong to class SCSI_PROCESSOR
are now claimed by the pass-through driver and
hence are shown as CLAIMED by ioscan.
( SR:8606298657 CR:JAGae62156 )
When a non-LVM I/O request fails with
a sense key of "Illegal Request", the disk driver
retries the I/O forever instead of returning failure.
This causes the application to hang indefinitely.
Resolution:
The disk driver is modified to return an error
EINVAL for a non-LVM I/O request when we have
a sense key of "Illegal Request".
( SR:8606307922 CR:JAGae70957 )
Driver treats the 'Reservation Conflict' error
status as transient error and the I/O resulting
in that status is retried until a successful completion.
In case of 'Persistent Reservation', since the
reservations are persistent across power cycle
of the device, the error cannot be treated as
transient.
Resolution:
The I/O request failing with 'Reservation Conflict' status
are failed immediately without a retry.
PHKL_28513:
( SR:8606226043 CR:JAGad95114 )
In extremely rare conditions, single byte writes to
onboard memory (SCRIPT RAM) may not complete on Channel B
of A5159A and Core I/O FWD SCSI HBA on rp24xx, rp54xx
rp7400 systems.
This may result in following problems:
a. Data integrity issues
b. System crash due to HPMC
Resolution:
Driver is changed to perform word writes instead of byte
writes.
( SR:8606286272 CR:JAGae50215 )
To avoid data corruption Disable Pipe Request(DPR) bit is
to be set during SCSI operations. In the present code
it is being done only once, in chip initialization
routine, and it gets reset after a successful
chip reset operation.
Resolution:
Set the DPR bit in the chip reset routine instead of chip
initialization routine. This will make sure that DPR bit
is set on chip reset.
( SR:8606289589 CR:JAGae53519 )
The SCSI LUN pointer is invalid for the bus scsi control
block (SCB) and therefore can cause a recursive bus lock
held panic in Multi-LUN configuration.
Resolution:
The LUN pointer is reset to zero for the bus pool SCB
before it is freed. Hence, recursive holding of the
bus lock is avoided.
PHKL_28096:
( SR:8606271035 CR:JAGae35271 )
The internal hot-swap disks are not configured
to spin up at power-on. Hence, any access to the
the hot swap disks returned a sense data
of ASC = 0x04,ASCQ = 0x02.This resulted in the
I/O getting retried forever resulting in
application hang.
Resolution:
The SCSI driver is modified to send a Start Unit
command to spin up the drives when a sense
data of ASC=0x04, ASCQ=0x02 is returned by
the target.The original I/O is resumed after the
Start Unit command is completed.
PHKL_27579:
( SR:8606245156 CR:JAGae11630 )
The SCSI controller chip on the A5838A card
was reset when it was doing DMA. After reset,
some of the DMA transactions were not getting
claimed by the SCSI controller chip. This
caused the timer on the card bridge to expire
and HPMC the system.
Resolution:
The problem is resolved by aborting the ongoing
DMA before resetting the card.
( SR:8606242143 CR:JAGae09397 )
The Disable Overlapped Arbitration bit in
the Control register Zero is used for
gaining access to the PCI bus while another
function is executing a PCI cycle.The register
bit was not set and hence caused intermittent
bus hangs and bus resets on the cards
containing the 53C876 chip.
Resolution:
The Disable Overlapped Arbitration bit is now
set on the cards containing the 53C876 chip
whenever the chip is reset. This avoids the hang
and subsequent resets.
( SR:8606241873 CR:JAGae09130 )
The scsi_isc array maximum limit is 255.If the instance
is greater than 255 overflow occurs and leads to memory
corruption and subsequent panic. The c720 interface
driver was not validating the maximum limit of the instance
number.
Resolution:
The driver init routine was changed to check if
the instance numbers were greater than 256 and if so return
an error. This causes the bus instance numbers
greater than 256 to become unclaimed and hence avoids
the system panic.
( SR:8606216118 CR:JAGad85288 )
The system panics because of a race condition between the
SCSI bus open and the interrupt being serviced. The
interrupt was getting serviced before the internal
data structures in the bus open routine were completely
initialized.
Resolution:
The fix is to set a flag after initializing the data
structures in the SCSI bus open routine. In the ISR
routine, a check is made to verify if this flag is set.
The interrupt is serviced only if this flag is set. The
flag is unset in the SCSI bus close routine.
( SR:8606257328 CR:JAGae21633 )
When the SCSI bus reset is in progress, a flag is set
and this flag is cleared in a routine that will be
executed 3 seconds after the bus is reset using a timer
routine. Before this function executes,if the card is
suspended, as the suspend routine cancels the timeout,
the flag will never get cleared. Even after the
resume, the flag remains set and when this flag is set,
no I/O are possible. This will cause application hang.
Resolution:
The flag should be reset in the suspend routine
before canceling the timeout routine.
( SR:8606204859 CR:JAGad74037 )
The SCSI driver does not distinguish between speed/width
negotiations initiated by the target or the driver.
The mismatch in the speed setting on the host and the target
resulted in Parity Error on the bus.
Resolution:
SCSI driver now tracks whether the response from the target
is a response to host initiated negotiation or a
unsolicitated request from the target.
( SR:8606232873 CR:JAGae02101 )
The driver used to map request sense buffer for every
I/O (and unmap them on completion). During heavy load the
mapping failed and caused the system to panic. The problem
was fixed by mapping the request sense buffer during bus
open and re-using the physical address for each I/O until
the bus is closed. However, while re-using the request
sense buffers between I/O, the driver was not invalidating
the buffer.
Resolution:
Modify the request sense buffer handling code in c720
driver as below
1. Allocate and map one request sense buffer in
initialization function and re-use it during the life
of the card.
2. Invalidate the buffer after every completion status
receipt from device.
( SR:8606238711 CR:JAGae07734 )
The disk driver returns EINVAL for I/O request
to LVM due to some hardware condition.
LVM was not retrying the I/O requests even
when an alternate path to the LUN existed.
This resulted in some filesystem and system
hang condition.
Resolution:
The disk driver is modified to return an error
of EPOWERF when an EINVAL condition
is reported by the device for an LVM I/O
except for ASC=0x0C , ASCQ=0xA0
(Oracle Hard Integrity error).
LVM will retry the I/O on an alternate path
due to EPOWERF returned by the disk driver.
( SR:8606264850 CR:JAGae29181 )
The open(2) on a CDROM drive without a CD in it takes
a considerable amount of time compared to having a CD
in the drive. As a result of it, the boot time increased
with VxVM. The delay comes from the driver sending a
"Start Stop Unit" (SSU) command to spin up the disc
and retrying the command 5 times even when the
O_NDELAY flag is set.
Resolution:
The solution is not to retry the "Start Stop Unit"
command if the O_NDELAY flag is set and retry
5 times if the flag is not set, so that the Operating
System realizes faster that there is no media in
the CDROM drive.
PHKL_27563:
( SR:8606265990 CR:JAGae30243 )
The I/O subsystem hang occured because an I/O remained
in the lun disk queue. The I/O remained in the queue
because of a failure in allocating the resource.
Resolution:
The code has been modified to take care that the
I/O subsystem hang does not happen when allocation
of the resource fails.
PHKL_26519:
( SR:8606236118 CR:JAGae05183 )
Upon detecting a timed out I/O request, the driver sets a
flag in the LUN data structure indicating "do not retry any
requests for this LUN". After successful completion of a
subsequent I/O request, this flag should be cleared.
However, when the subsequent I/O request completes
successfully, the driver's normal completion path (in which
this flag is cleared) is not executed and hence the flag
remains set. If any subsequent I/O requests do not complete
successfully, they are failed immediately without performing
a retry.
Resolution:
Ensure that the driver follows the normal completion path
for the first successful completion of an I/O request
following a failed I/O request.
( SR:8606226361 CR:JAGad95431 )
When I/O requests from LVM fail or time-out due to bad
disks, the SCSI disk driver returns an incorrect error code
to LVM causing the LVM to retry the I/O request forever
instead of returning failure. This causes the application
which has issued the I/O request to hang indefinitely.
Resolution:
Ensure that the I/O request failed due to MEDIUM ERROR
is reported back to LVM with EMEDIA error.
( SR:8606135832 CR:JAGad04964 )
This product update contains minor enhancements required to
enable the support for 16 byte CDBs (Command Descriptor
Block) in the SCSI driver.
Resolution:
The SCSI driver has been to modified for the support of 16
byte CDBs (Command Descriptor Block).
( SR:8606214047 CR:JAGad83238 )
The SCSI driver accesses the adapter registers in its
interrupt service routine (ISR). Although card interrupts
are disabled during the suspend operation, if spurious
interrupts are delivered to the SCSI driver, the driver
would attempt to read the card registers, resulting in a
HPMC.
Resolution:
The SCSI driver has been modified so that it does not
attempt to process spurious interrupts when it is in a
suspended state.
( SR:8606236116 CR:JAGae05181 )
After an LVM I/O times out, the flag L_FAIL_QUEUE_IO can
remain set and prevent LVM probes from being sent to the
device to see if it has returned on-line. Also, many SCSI
read error messages will be seen in syslog.
Resolution:
Only set the flag (L_FAIL_QUEUE_IO) if there are I/O
requests queued to be sent to the device.
PHKL_25896:
( SR:8606228002 CR:JAGad97060 )
Some disks do not start spinning automatically. The SCSI
subsystem retry policy changed with PHKL_24441 and, as a
result, the Start Unit command is not retried. These two
changes combined cause the first Start Unit command to these
disks to fail. Successive commands issued to these disks
also fail. Later, a Read Capacity command to the device
returns a capacity of zero bytes.
Resolution:
The SCSI subsystem retry policy is refined to retry the
Start Unit command five times. With these successive
retries, the disks start spinning and later return the
correct capacity size.
PHKL_25509:
( SR:8606203627 CR:JAGad72800 )
All messages logged by the c720 driver can be suppressed by
setting appropriate value for a c720 driver global variable.
This message was not controlled by this variable.
Resolution:
The value of the global variable is now checked before
printing the mentioned message.
( SR:8606186960 CR:JAGad56170 )
The Plasmon devices return 256 bytes of Sense data. The
allocated buffer for sense data is also 256 bytes, causing
the residue to be zero. When the residue is zero, the
mentioned message is printed.
Resolution:
The code that prints the mentioned message is removed since
a zero residue is not an error.
( SR:8606201476 CR:JAGad70652 )
This informative message is logged while trying to access a
device with zero capacity (i.e. a placeholder LUN when LUNS
are not defined contiguously) or a device without media.
Resolution:
This message is no longer logged by default for partially
opened devices. This message log can be enabled for
debugging purposes by setting appropriate value in
scsi_log_mask.
( SR:8606199892 CR:JAGad69078 )
Devices of HP SureStore E Disk Array 12 sometimes
successfully complete I/Os when in Contingent Allegiance
(CHECK CONDITION state of SCSI devices). These I/O
completions were not reported to the requesting layer,
causing the process to hang.
Resolution:
If an I/O completes sucessfully when the device is in
Contingent Allegiance condition, the I/O is returned with an
error to the requesting layer for further action (typically
an I/O retry).
( SR:8606194472 CR:JAGad63680 )
While determining whether the SCSI bus is wide or narrow,
the C3700 model was not considered.
Resolution:
The model string for the C3700 was added to the list of
models with narrow external SCSI buses.
( SR:8606177456 CR:JAGad46688 )
On the last close of a device, the scsi driver attempts to
synchronize the cache of the device. Using a FC60 array,
this is unnecessary and it also causes an Automatic LUN
Tranfer (ALT). The unneeded ALT operations cause a
significant delay when attempting to import Disk groups.
Resolution:
Disk driver does not synchronize cache on FC60 array devices
when the device is closed.
PHKL_25165:
( SR:8606207855 CR:JAGad77032 )
The SCSI services did not support these ioctls for the c8xx
driver.
Resolution:
SCSI services is enhanced to support these ioctls for the
c8xx driver.
( SR:8606170140 CR:JAGad39404 )
Many non critical conditions generate logs. By example,
addition or removal of devices in the loop generate many
resets.
Resolution:
The logging mechanism is adapted to record only critical
error conditions. The following conditions are recorded:
Unit Attention and Deferred errors
I/O retried unsuccessfully
I/O unsuccessful and not retried
Also, if the SLOG_SUCCESS_RETRY is set in scsi_log_mask,
I/Os completing successfully after prior unsuccessful
attempts are recorded. This helps to identify devices
repeatedly returning errors before being successful.
( SR:8606172682 CR:JAGad41942 )
The nature of the lun is not checked when modifying the
queue depth of the lun.
When modifying the queue depth of a lun, the new value
is overwritten by the previous value.
Resolution:
The nature of a lun is checked while modifying its queue
depth. If the lun does not support tag queueing, an error
code is returned.
The code is adapted to support multiple queue depth changes.
( SR:8606166652 CR:JAGad35939 )
If a SCSI I/O is initiated using the sctl/ioctl passthrough
function and the transfer size is greater than the size of
the malloc'd buffer for this transfer, the system panics.
Resolution:
Check the access permissions of the buffer supplied by the
user before using it. This ensures the system won't panic
if the size of the I/O is greater than the size of the
buffer.
( SR:8606192639 CR:JAGad61851 )
While probing for each LUN, the corresponding bus is opened
and closed. The bus open takes a long time, especially in
large Fibre Channel Array configurations. Since all
possible LUNs are probed on each target whether or not they
are present, the probe time can be quite long on large Fibre
Channel Array configurations, resulting in long boot times
and long ioscan times (without the -k option).
Resolution:
The bus is kept open until all the LUNs corresponding to all
the targets on that bus are probed.
( SR:8606189054 CR:JAGad58270 )
Under heavy I/O load on the same bus, when some per bus
resource (tag, nexus) becomes unavailable, I/Os are stored
in specific queues, waiting for the resource to become
available. Under some conditions, the queues are not
checked once the resource is once again available, leaving
the I/O requests unserviced. The corresponding processes
remain in an unkillable state, waiting for I/O completion
or failure that never occurs.
Resolution:
Additional tests were added to check if I/Os are pending in
the queues, and to process them if the resources are now
available.
( SR:8606166664 CR:JAGad35951 )
While retrying an I/O that has timed out, the system may
access a previously freed target pointer, resulting in a
panic.
Resolution:
Timed-out requests are sent to a temporary queue. This
prevents them from being processed and started until the
target pointer is once again valid.
PHKL_23313:
( SR:8606174670 CR:JAGad43916 )
A number of program header files were delivered in their
"debug" forms rather than in their intended "performance"
forms. Kernel-intrusive programs (such as drivers and
programs that access /dev/mem or /dev/kmem) compiled with
these header files may contain internal structures that are
not aligned with the actual kernel structures.
Resolution:
A set of patches redeliver the header files in their
intended forms. All kernel-intrusive programs originally
compiled using the header files included on the HP-UX 11.11
Operating Environment OE Install and Recovery media dated
December 2000 must be recompiled using the corrected header
files.
All of the corrected header file patches are included in the
BUNDLE11i bundle on the HP-UX 11.11 Operating Environment
Core OE Install and Recovery media dated February 2001 or
later.
The complete list of header file patches is:
PHNE_23288 /usr/conf/net/netmp.h
/usr/include/net/netmp.h
/usr/conf/sys/socketvar.h
/usr/include/sys/socketvar.h
/usr/conf/sys/unpcb.h
&nbs