|
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 800 10.X patch digest
From: IT Resource Center (support_feedback
us-support2-mail.external.hp.com)
Date: Sun May 25 2003 - 10:34:27 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 800 10.X patch digest
Created: Sun May 25 7:05:05 EDT 2003
Table of Contents:
Document ID Title
--------------- -----------
PHSS_28988 s700_800 10.X OV DM5.03 Intermediate Patch April 2003
PHNE_28536 s800 10.20 LAN products cumulative Patch
PHSS_28738 s700_800 10.20 OV OB4.10 patch - CC packet
PHNE_28635 s700_800 10.20 EISA 100BT cumulative patch
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHSS_28988
Date Loaded: 20030522
Title: s700_800 10.X OV DM5.03 Intermediate Patch April 2003
Patch Name: PHSS_28988
Patch Description: s700_800 10.X OV DM5.03 Intermediate Patch April 2003
Creation Date: 03/05/18
Post Date: 03/05/22
Hardware Platforms - OS Releases:
s700: 10.01 10.10 10.20
s800: 10.01 10.10 10.20
Products:
OpenView Distributed Management 5.03
Filesets:
DMAgent.OVEMS-LOG,B.05.03 DMAgent.OVEMS-RUN,B.05.03
DMAgentDevKit.OVDM-XMPv7-PRG,B.05.03
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_28988
Symptoms:
PHSS_28988:
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_28988:
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.
SR:
F333003088 F333002901 F333003102 F333003095
Patch Files:
/opt/OV/lib/libxmpV7.a
/opt/OV/bin/ovead
/opt/OV/bin/ovladdb
/opt/OV/bin/ovladff
what(1) Output:
/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
/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
/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
cksum(1) Output:
574037718 895505 /opt/OV/bin/ovead
2461527867 1477592 /opt/OV/bin/ovladdb
906794317 1313460 /opt/OV/bin/ovladff
2868544963 1574236 /opt/OV/lib/libxmpV7.a
Patch Conflicts: None
Patch Dependencies:
s700: 10.01: PHSS_27695
s700: 10.10: PHSS_27695
s700: 10.20: PHSS_27695
s800: 10.01: PHSS_27695
s800: 10.10: PHSS_27695
s800: 10.20: PHSS_27695
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches:
PHSS_28989:
s700: 11.00
s800: 11.00
PSOV_03257:
sparcSOL: 2.4 2.5 2.6
Patch Package Size: 1820 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_28988
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_28988.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_28988. If you do not wish to retain a
copy of the original software, you can create an empty file
named /var/adm/sw/patch/PATCH_NOSAVE.
WARNING: If this file exists when a patch is installed, the
patch cannot be deinstalled. Please be careful
when using this feature.
It is recommended that you move the PHSS_28988.text file to
/var/adm/sw/patch for future reference.
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_28988.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_28988------------------------------------------
Document ID: PHNE_28536
Date Loaded: 20030522
Title: s800 10.20 LAN products cumulative Patch
Patch Name: PHNE_28536
Patch Description: s800 10.20 LAN products cumulative Patch
Creation Date: 03/05/07
Post Date: 03/05/22
Hardware Platforms - OS Releases:
s800: 10.20
Products: N/A
Filesets:
Networking.LAN-KRN Networking.LAN-RUN
Networking.NW-ENG-A-MAN
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHNE_28536: PANIC ABORT
Symptom 3 fixes panic caused by badly formatted
ethernet trailer encapsulated packets.
Symptom 2 fixes panic due to spinlock deadlock.
Symptom 6 fixes abort by lanadmin(1m) under certain
circumstances.
PHNE_23862: HANG PANIC
This patch fixes the spinlock deadlock and
the bad trailer encapsulated ethernet packet
hang problem.
PHNE_22352: PANIC
Without this patch, LASI based systems will panic
after network activity as mentioned in Symptom 1.
Without this patch, system panics when trying to run
the promiscuous tests on Core Ethernet interface as
mentioned in Symptom 9.
PHNE_21904: PANIC
Symptom 1 fixes a PANIC
PHNE_20656: PANIC OTHER
Symptom 9 fixes a PANIC
PHNE_18924: OTHER
Without this patch, packets which are sent out
by an interface will not be seen by the SAP level
promiscuous mode application.
PHNE_18174: PANIC
Symptom 2 fixes a panic.
PHNE_17000: PANIC
Without this patch, system may panic under heavy
load and having low memory, as mentioned in Symptom
1.
Without this patch, there is a likelihood of system
crash when promiscuous mode is turned on and off
repeatedly on Core 10BT lan card, as mentioned in
Symptom 2.
PHNE_14368: OTHER
Without fix 1, DLPI type 2 applications (e.g. SNA)
won't work over non-CKO FDDI.
PHNE_14502: ABORT
DLPI clone devices are not returned to free pool
after close in PHNE_13586, hence after a certain
number of operations utilities like lanadmin,
linkloop etc. will fail as they will not be able
to open /dev/dlpi.
PHNE_13586: PANIC
Fixes a panic in hp_dlpi_close.
PHNE_12872: PANIC
Fixes a panic in lan2_ru_restart and a panic with
linkloop to ATM card.
PHNE_12576: PANIC
Fixes couple of panics in dlpi.
PHNE_11704: OTHER
The first fix allow inbound FDDI packet with
certain MAC address to be accepted by DLPI. The
second fix allows DLPI applications to receive
control responses correctly even though another
DLPI application is closing its stream.
PHNE_11126: PANIC
Fixes a panic in NIO Ethernet, when operating in
promiscuous mode.
PHNE_11052: OTHER
Required for T600, and supersedes other critical
patch.
PHNE_10512: OTHER
Avoids, excessive reset of lan interface rendering
system unusable on the network
Path Name: /hp-ux_patches/s800/10.X/PHNE_28536
Symptoms:
PHNE_28536:
1. DLS user application cannot bind to SAP value 0x1010.
2. Spinlock deadlock for lanc_lookup_lock.
3. When receiving a badly formatted trailer protocol frame,
HPUX 10.20 crashes.
4. lanscan(1m) man page missing part of a sentence.
5. Improper padding of < 64 byte packets by NIO 10 BT driver
6. Possible core dump by lanadmin(1m).
PHNE_26072:
1. Local switch IOCTL fails on FDDI/TR interfaces.
PHNE_23862:
1. Spinlock deadlock for lanc_lookup_lock.
2. When receiving a badly formatted Trailer protocol frame,
HPUX 10.20 crashes.
3. lanscan man page missing part of a sentence.
PHNE_22352:
1. When one or more data lines of the AUI port had been
disconnected but the other lines are still connected,
LASI based systems will panic after network activity.
2. Modifications for lanadmin were not reflected by landiag
command.
3. lanscan usage string does not show option "q".
4. Switching ioctl fails for Core 10BT driver when cable is
disconnected.
5. HP-PB 10BT interface reports incorrect MIB statistics
causing Service Guard to misbehave.
6. Non superuser can execute the privileged lanadmin
options.
7. When a long Station address is given as an argument to
lanadmin command, it returns without reporting any error.
8. lanscan -P fails on the system with ATM card.
9. The system panics when trying to run the promiscuous
tests on Core 10BT interface.
10. FTAM transfer stop working after SG local switching.
11. Token Ring functional address are not working properly.
PHNE_21904:
1. Under heavy inbound traffic a system may panic with
the string "kalloc: out of virtual space.".
2. 'token2: Hard error on CTL_CCMD=0x1060' error
logged when trying to log a protocol.
3. Removing patch PHNE_21216 gives an error.
PHNE_21216:
1. T2 XID/TEST tests fail.
2. DLPI does not check for invalid multicast
address for FDDI.
3. lanconfig resets MTU size for gigabit interfaces.
4. lanc fails to prevent setting Station Address to
a multicast MAC address.
5. manpage changes needed for lanscan to reflect
'-q' option.
6. ER: lanc support for filtering IEEESAP_HP packets
on 10.20.
7. Promiscuous level 2 behaves differently on 10.20.
8. LLA fails to support 0x1010 SAPs.
9. Log messages lanc_ether_ics noticed in dmesg.
PHNE_20656:
1. ER: Support for APA in DLPI.
2. Problem with DL_SUBS_BIND_REQ.
3. ER:Lan Monitor support in DLPI.
4. Wrong address format for FDDI packets.
5. Ethernet cards setup incomplete after reboot.
6. /usr/sbin/lanscan does not have proper
ownership/permissions.
7. Data loss over serial line with unterminated Core
10BT card.
8. ER: To have lan2 clear netstat statistics with
'lanadmin' clear.
9. dlpi panic in t2_dlpi_finish_connect_res with vmtrace
active.
10. ER: Add '-q' option for lanscan.
PHNE_18924:
1. Sequence of packets as seen by promiscuous mode
application may be not be in the same sequence as they
are on the physical media.
2. When an interface is in promiscuous mode, dlpi/ lanc
loops back packets to IP stream even if MF_NOLOOPBACK
flag is set.
3. Promiscuous mode application may not see outbound
packets if it is operating in 'SAP level promiscuous'.
PHNE_18174:
1. HP-PB 10BT and Core 10BT drivers do not receive packets
they transmit, when in promiscuous mode.
2. System configured with Core 10BT lan interface, sometimes
panics (data page fault) with the target address showing
0xa00?????. System could panic with the message "panic:
mclfree".
3. swverify(1M) on the Networking product fails on the newer
workstations without Core 10BT lan interface.
PHNE_17000:
1. System panic under heavy load and having low memory.
2. System panic when Core Ethernet lan card is put into
promiscuous mode.
3. Change Core Ethernet and HP-PB Ethernet drivers to use
schednetisrmq().
4. Request to allow the MTU size on ethernet lan to be
adjustable.
5. Request for removal of "rx_bad_addr" from "Inbound
Discards" counter.
6. ER - A Tool to determine promiscuous mode is needed.
7. ATM interface named "el1000" is not displayed properly by
lanscan.
8. lanscan -v report shared library error against ATM NICs.
PHNE_14634:
1. No DELETE multicast requests were sent down to the
driver when application issued a DELETE on a
previously added multicast address.
2. Inconsistent behaviour by network drivers when
promiscuous mode was enabled.
3. Enabling and disabling of multicast addresses failed
on Token Ring drivers.
4. lanadmin needs easier way to reset MAC address
to default.
PHNE_14368:
1. DLPI type 2 won't work over FDDI devices that do not
support the Checksum Offload feature (e.g. HSC and
EISA FDDI)
2. linkloop returns ERANGE if MTU of link changed.
PHNE_14502:
1. Defect in PHNE_13586, DLPI clone devices not returned
to free pool after close.
2. DLPI command after DL_HP_HW_RESET may get ENXIO error.
PHNE_13586:
1. Panic in hp_dlpi_close/detach.
2. lanadmin does not support mode and speed changes for
100BT cards.
PHNE_12872:
1. System panic with data page fault in lan2_ru_restart.
2. IP multicast packets are received twice with lan3
driver.
3. Linkloop on a ATM device panics when PHNE_12576 is
installed.
PHNE_12576:
1. Panic in hp_dlpi_delete_wakeup routine under stress.
2. Panic while operating in promiscuous mode.
3. DL_HP_MULTICAST_REQ/ACK support for drivers supporting
IP level multicasting.
4. Wrong ifOper status displayed for Built-In lan card.
5. lanadmin command displays "%s" in the output, instead
of the error string.
6. lanadmin command fails after sufficient changing of
nmid/display commands.
PHNE_11704:
1. Inbound data is dropped for certain FDDI,
individual, MAC address. The msb of the MAC address
is checked incorrectly when received by DLPI.
2. Application will hang due to two applications
accessing the dlpi_wakeup_list at same time. Such
as lanadmin will hang while waiting for reception
of dlpi control response if other dlpi stream is
closing.
PHNE_11126:
1. Changing MTU to more than 4096 bytes on token ring
fails.
2. NIO Ethernet operating in promiscuous mode panics.
PHNE_11052:
1. Without this patch, NIO Ethernet will not work on T600.
PHNE_10512:
1. Systems using builtin lan through External MAU see
excessive resets. Applications trying to transmit a
packet could see ENOLINK.
2. 'mrouted' tunneling fails on HP-PB 10BaseT driver.
3. Some LAN interfaces need reset, when the H/W address is
changed.(Eg. HP-PB FDDI)
4. Some LAN interfaces require other operation to be
performed with reset to bring back the interface UP.
(Eg. HP-PB FDDI requires download operation during reset)
PHNE_9278:
Running netperf snap_script, the ipintr queue was filled
and stayed filled. Ping then start to fail. The linkloop
still ran fine over the link. However, the system did not
seem to recover from the queue full condition.
Defect Description:
PHNE_28536:
Fix Summary:
For ETHER 3,5
General: 1,2,4,6
1. CR JAGae43281, SR 8606279225
Protocol value 0x1010 was being reserved by DLPI for
trailer encapsulation as per RFC0893.
Resolution:
Protocol value 0x1010 is released for user applications.
2. CR: JAGae47937 SR: 8606283991
Fix for JAGad54952 introduced in PHNE_23862 was
omitted in PHNE_26072.
Resolution:
Missing fix reinserted.
3. CR: JAGae47937 SR: 8606283991
Fix for JAGad55423 introduced in PHNE_23862 was
omitted in PHNE_26072.
Resolution:
Missing fix reinserted.
4. CR: JAGae47937 SR: 8606283991
Fix for JAGab76532 introduced in PHNE_23862 was
omitted in PHNE_26072.
Resolution:
Missing fix reinserted.
5. CR: JAGae57955 SR: 8606294216
Padding of < 64 byte packets was not being handled by
NIO 10 BT driver correctly.
Resolution:
Padding of < 64 byte packets is now properly done.
6. CR: JAGae58591 SR: 8606294894
lanadmin(1m) can dump core under certain circumstances.
Resolution:
Boundary checks are made to prevent lanadmin(1m) aborts.
PHNE_26072:
Fix Summary:
For TR/FDDI: 1
1. CR JAGae02801, SR 8606233578
Local switch IOCTL SIOCSWITCHIFADDR fails on
FDDI and TR interfaces. The SIOCSWITCHIFADDR IOCTL
is used during SG failover operation. The code was
inadvertently returning EINVAL for this IOCTL on
FDDI and TR interfaces due to a unnecessary error
check.
Resolution:
This check was removed from the code.
PHNE_23862:
Fix Summary:
FOR ETHER:2
Common for all products:1, 3
1. JAGad54952:
Spinlock deadlock panic for lanc_lookup_lock.
panic+0x10
too_much_time+0x238
wait_for_lock_spinner+0x2f4
wait_for_lock_4way+0x2c
sl_retry+0x18
lanc_remove_protocol+0xb8
lanc_lla_close+0x2d0
closef+0x68
exit+0x214
rexit+0x20
syscall+0x75c
$syscallrtn+0x0
Resolution:
Locking across sleep causes problem. The lock that is held
by one processor before sleep is released by another
processor, there by creating a spinlock-deadlock.
Fixed by redesigning the locking mechanism.
2. JAGad55423:
On receiving a trailer encapsulated ethernet frame that is
badly formatted the system crashes.
m_free+0x70
m_cat+0x94
lanc_ether_trail_intr+0xf8
lanc_ether_ics+0x330
lanc_ether_trail_intr+0x6c
lanc_ether_ics+0x330
lanc_ether_trail_intr+0x6c
lanc_ether_ics+0x330
lanc_ether_trail_intr+0x6c
Resolution:
The badly formatted frame is detected and dropped by DLPI.
3. JAGab76532:
lanscan man page missing part of a sentence
Resolution:
lanscan man page is updated with complete sentence.
PHNE_22352:
Fix Summary:
For TOKENRING:11
For ETHER:1,4,5 and 9
Common for all products:2,3,6,7,8 and 10
1.JAGad35507: When transmit line being severed and the
receive lines being intact, the card will still receive
packets from the wire. So when the driver sends out a
loopback packet in the reset path, it assumes any
response to be the loopback response. So, it assumes
success of loopback even though the packet it received
was not a loopback packet. This causes the driver to come
online. The next transmit will again timeout causing
another reset. These continuous resets lead to the bus
timeout and hence the panic.
Resolution:
Ensure that the packet received in lan2_process_looper
is really a loopback packet.
2.JAGad21159: The patches on 10.20 were missing the link
between lanadmin and landiag. Due to this, the
modifications released in patch for lanadmin were not
reflected by landiag command.
Resolution:
The fix is to create a hard link between lanadmin and
landiag.
3.JAGac46780: Though the support for "q" option was already
added to lanscan, the usage string was not reflecting
the same.
Resolution:
Modified the usage string of lanscan to show "q" option.
4.JAGad25042: Core 10BT driver rejects control requests
when cable is disconnected. So SIOCSWITCHIFADDR ioctl
issued on it fails to switch IP address.
Resolution:
The driver is modified to accept and process
SIOCSWITCHIFADDR ioctl, even when the cable has been
disconnected.
5.JAGad15714: The MIB statistics were being updated for a
HP-PB 10BT card even though the cable was disconnected.
This was causing the Service Guard to misbehave as it
depends on the MIB statistics to detect the failure or
recovery of network interfaces.
Resolution:
The statistics now get updated when the packet is
successfully processed and transmitted.
6.JAGac88753: The non superuser has the permission to
execute lanadmin with privileged options which should be
possible only by super user.
Resolution:
The permissons of lanadmin have been changed from 4555 to
555 to prevent non super user accessing privileged
information.
7.JAGab75792: When the station Address argument passed to
lanadmin is too long, lanadmin does not display any error
message and does not return the value indicating the
failure of the command. This was causing problem for the
driver specific configuration scripts as they were not
able to detect the failure and the card also was not
getting configured.
Resolusion.
lanadmin will now print an error message for the long
MAC address and will exit with -1.
8.JAGab64391: lanscan -P command does not work correctly on
the system where there is an ATM card.
Resolution:
lanscan is modified to take care of this situation.
9.JAGad38176: The system was panicing while running the
promiscuous mode tests. The panic was because of a
window, where the promisc stream can be freed but still
hp_dlpi_intr tries to access it.
Resolution:
The Core 10BT driver code is modified to take care of the
problem by checking the content of the variable before
it was being used.
10.JAGac29671: When local switching is done from primary to
standby interface, FTAM is not able to transfer files.
During the local switchover, the new encapsulation flags
and also the MTU is not reflected to the upper layers and
the upper layers continue to send out packets with old
MTU size that causes packets to be dropped.
Resolution:
During the switchover, the MTU size and encapsulation
flags are changed in the 'ifnet' strucutre so that the
applications that uses the interface will know about the
change in MTU size and encapsulation.
11.JAGad21664: Enabling/Disabling the functional address are
not working as expected. When checking whether a
functional address is enabled during disabling that
functional address, DLPI compares the fuctional address
given by the user with a wrong address there by failing
the disable-functional address request. This causes
future enabling/disabling of that functional addresses to
fail.
Resolution:
Proper addresses are compared during
enablement/disablement of the fuctional addresses.
PHNE_21904:
Fix Summary:
Common for all products: 1,2,3.
1. JAGad03223: When a system is under heavy inbound network
load the incoming packets may hog the memory completely
resulting in a "kalloc: out of virtual address" panic.
Resolution:
An upper limit has been placed on the number of packets
on the DLPI linked list. Additionally, a global variable
ics_cnt_max can be used to change the default value of
512.
2. JAGad23566: When DLPI receives a BIND_REQ, it
check whether the protocol is already logged.
If the protocol is not logged, then it calls
the driver to log the protocol. But this
complete operation is not done as a single unit,
and by the time the hardware request is sent
to driver, another BIND_REQ may come in and
see that the protocol is not logged and that
too will create a duplicate hardware request,
and the driver hits a hardware error.
Resolution:
The lock which currently used is only during
the lookup process, and does not cover the
logging. Introduced a lock which can protect
the lookup and the logging, their by making
sure that no duplicate requests are sent to
the driver.
3. JAGad11998: The preremove script of the patch
PHNE_21216, was missing _PATCHID variable, which
resulted in error during removal of the patch.
Resolution:
This patch fixes this problem.
PHNE_21216:
Fix Summary:
For FDDI: 2.
For ETHER: 3, 4.
Common for all products: 1, 5, 6, 7, 8.
1. JAGab69560: T2 XID/TEST scaffold tests fail, because
the T2 code in DLPI, assumes that the XID/TEST data
is present in first mbuf, but there is a possibility
that the first mbuf only contains the LLC header and
the XID data is present in second mbuf. This assumption
was wrong, which created unexpected response from
DLPI to an application.
Resolution:
The T2 code has been changed to take care of this
situation, where the XID data can be present in the
second mbuf.
2. JAGac88801: When Enable/Disable multicast address
request was sent, DLPI does not check for invalid
multicast addresses for FDDI driver, so, if an
application tries to enable a invalid multicast address,
on a FDDI link, it succeeds.
Resolution:
The code change done to resolve this defect, checks
for the device type of FDDI when it tries to enable
a valid multicast address.
3. JAGac88848: "lanconfig" command when used to change
the MTU size, fails to do so, because the DLPI code
always takes the MTU size from the pre-defined
macros, this causes problems in a gigabit link where
jumbo frames are used and they don't fall under the
predefined set of MTU sizes.
Resolution:
The MTU size is taken from the hwift structure of
the link instead of the pre-defined values.
4. JAGac95565: lanc fails to prevent setting Station
Address to a multicast MAC address. The check
done to prevent this from happening, checks for the
device type of DEV_8023, but some ethernet drivers
set the device type to DEV_ETHER, so this checking
fails to prevent setting multicast address as the
station address when the drivers set the device type
to DEV_ETHER.
Resolution:
The checking done when trying to change the station
address now includes the check for device type of
DEV_ETHER.
5. JAGad01129: Manpage of lanscan does not reflect the
addition of '-q' option.
Resolution:
The manpage changes have been done to include the
usage of '-q' option in lanscan.
6. JAGad00107: ER: Support for filtering IEEESAP_HP
packets in lanc.
Resolution:
This enhancement has been done in lanc to support
filtering for IEEESAP_HP packets.
7. JAGac42727: SAP promiscuous application doesn't see
multicast packets, as the 'hp_dlpi_intr_put' routine
filters out the multicast packet when its in SAP
promiscuous mode.
Resolution:
The filtering of multicast packets when the stream
is in SAP promiscuous mode is not correct, the
changes were done to remove this wrong filtering.
8. 5003254151: LLA code used incorrect "<=" operator
to check for 0x1010 boundary.
Resolution:
While checking for the protocol value in
lanc_ether_control, the code used "<=" operator,
instead of "<" operator which allows the
value to exceed the boundary of allowed values.
9. JAGad04259: Messages "lanc_ether_ics:<number>" are logged
in dmesg/syslog.
Resolution:
Removed Message logging.
PHNE_20656:
1. JAGac56887 ER: Changes needed in DLPI to support APA
features.
Resolution:
Changes are made to DLPI to support some functionalities
of APA. The changes done were addition of new IOCTL's
APA_SET_DEFAULT_CONFIG_MODE, APA_GET_DLPI_VERSION &
APA_EVENT_SET_DEFAULT_CONFIG_MODE.
2. JAGac56915: Problem with DL_SUBS_BIND_REQ.
Resolution:
Update the DLPI internal data structure only after
the protocol logging is successful.
3. JAGac79105: Lan Monitor Support in DLPI:
Resolution:
The following changes were made to DLPI for
Lan Monitor support:
1. Block the primitives DL_BIND_REQ, DL_UNBIND_REQ,
DL_ENABMULTI_REQ, DL_DISABMUL TI_REQ,
DL_PROMISCON_REQ, DL_PROMISCOFF_REQ,
DL_SET_PHYS_ADDR_REQ from being processed when
the link is already part of an aggregate.
2. Handle events DL_EVENT_INTERFACE_DOWN,
DL_EVENT_INTERFACE_UP from drivers and
APA_EVENT_PROTOCOL_LOGGED from Lan Monitor.
3. New protocol bind flavor DL_HP_BIND_EXT, that
lets callers specify bind flags different from
defaults. This facilitates inbound packet processing
suitable for Lan Monitor.
4. Lock a port using hwift features bit DRV_PORT_IN_USE
to avoid a race condition between LM and DLPI
grabbing the port.
5. Support for binding protocol kind LAN_CANON that will
enable receiving poll packets by Lan Monitor
aggregated ports.
6. lanc_mib_event to pass Interface down/up events
to DLPI.
7. Block ioctls from transports to links that are part
of a fail-over group.
4. JAGac79079: DLPI converts the source and destination
addressess from canonical to wire format unconditionally
for all the FDDI packets, but some of the new FDDI cards
do the conversion themselfs, so the conversion done
by DLPI should not be unconditional.
Resolution:
The DLPI source has been changed to do the conversion
on condition that DRV_NO_MAC_CONVERT bit is not set in
the hwift features bit.
5. JAGab70839: Ethernet card does not get initialized as
per the settings specified in configuration file
upon reboot. The problem is seen for the cards
whose information in the configuration file is
at index greater than the number of cards in
the system.
Resolution:
Fix includes reading complete configuration information
by correct manipulation of index counter in the init
script.
6. JAGab84763: '/usr/sbin/lanscan' currently has owner and
group id set as bin/ bin, with setuid to bin. Even
though this does not create any particular problem,
this needs to be changed as in 11.0 release, i.e.
owner root group sys with setgid to sys.
Resolution:
Changes made to '/usr/sbin/lanscan' to have
uniformity across 11.0 and 10.20.
7. JAGaa22138: An unterminated/ disconnected Core 10BT
card causes data loss over the serial port. This is
because, when the card is disconnected, the driver
periodically tries to reset the card. The reset of
the card involves many calls to busywait(), which
leads to poor serial I/O performance.
Resolution:
The resolution is to eliminate some of the
busywait() calls in the reset path.
8. JAGab46779: The Core 10BT driver was not clearing
some of the variables when 'lanadmin' clear command
is run, which 'netstat' command reads. This leads to
inconsistency between 'lanadmin' displayed statistics
and 'netstat -i' displayed statistics.
Resolution:
The 'netstat' related variables are cleared now when
'lanadmin' clear command is run.
9. JAGac20293: Panic in t2_dlpi_finish_connect_res() with
Data Page Fault. The function where it panics has
incorrect ordering of statements, where the freed mbuf
is accessed.
Resolution:
The freeing of mbuf is done after the accessing of data
present in it is done.
10. JAGac79094: Add '-q' option for lanscan to display the
PPA numbers along with the aggregate information.
Resolution:
lanscan is modified to support the new option '-q' to
display the PPA numbers of the links along with the
aggregate information.
PHNE_18924:
1. Currently the kernel loops back the packets to
promiscuous mode application before they are put on the
DMA queue. Hence these packets will be seen by the
promiscuous mode application before the packets on the
physical media are seen.
Resolution:
The kernel is modified to loop back the outbound packets
to promiscuous mode application only after it is sent on
the physical media.
2. lanc/ dlpi currently ignores MF_NOLOOPBACK flag, before
looping back the packets to IP stream. In fact these
packets are to be sent only to promiscuous mode
application (if any) and not to IP stream.
Resolution:
lanc/ dlpi is modified to check for MF_NOLOOPBACK flag
and loop back the packets to appropriate streams only.
3. Due to a defect in lanc/ dlpi packets were not being
looped back properly when the promiscous mode
application is operating in 'SAP level promiscuous'.
Resolution:
Modified a comparison statement for SAP level
promiscuous in lanc/ dlpi to loopback concerned packets
to promiscuous mode application.
PHNE_18174:
1. HP-PB 10BT and Core 10BT drivers did not loopback
outbound packets while in promiscuous mode. So, the
stream which turned on the promiscuous mode didn't
receive the outbound packets.
Resolution:
Drivers now will loopback the outbound packets to DLPI
and DLPI will send the packets upstream.
2. Core 10BT lan interface did an extra DMA to a receive
frame descriptor under some conditions. This caused
corruption of the 256 byte bucket. The system panic'd on
the next 256 byte allocation request.
Resolution:
When the Core 10BT lan interface has used up the last
available receive frame descriptor, it generates a "Frame
Received" interrupt and also a "Receiver Not Ready"
interrupt. After processing each of these interrupts,
the driver attempted to start the receive engine with a
new pool of receive frame descriptors if the receive
engine status showed "Not Ready". Sometimes this could
result in the same pool of buffers being set up twice for
DMA. It has been corrected to start the receive engine
only on Receive unit "Not Ready interrupt".
3. Verify scripts for the Networking product assumed the
presence of Core 10BT lan interface on the machine. This
is no longer true on newer workstations.
Resolution:
SD Control scripts for the Networking product have been
modified to correct the problem.
PHNE_17000:
1. Not checking for the return value of m_copy() can cause
the system panic when system is heavily loaded and having
the low memory.
2. System may panic when promiscuous mode for core-ethernet
hardware is repeatedly turned on and off. This can
happen due to a small window between turning off the
promiscuous mode and accessing the promiscuous list
array.
3. Core-Ethernet and HP-PB Ethernet drivers use
"shednetisr()" and "schednetisrsq()" which can cause the
imbalance between the traffic on the "netisr" processes.
This can sometimes cause a severe performance impact.
4. Core Ethernet and HP-PB Ethernet does not allow the user
to change the MTU of the link. With this limitation in
the operating system, the customers will not be able to
use the software/applications which require to the change
MTU of the link.
5. The filter implementation in the HP-PB 10BT lan card
firmware to filter the inbound packets was not working as
expected. Due to which, the "rx_bad_addr" counter was
getting incremented wrongly. This has been corrected in
the driver.
6. A tool is required to determine if a lan interface is
currently in the promiscuous mode.
7. The ATM interfaces numbered up to el999 are well
displayed by lanscan command, but not el1000 or more.
This is because, in lanscan command, the number of digits
to use for display from the PPA/NMID is hardcoded as 3.
8. When ATM card is installed on a system, lanscan -v
command reports that it can not open the shared library
/usr/lib/lanscan/libpeatm.sl. This is because, HP DLPI
does not support ATM drivers and they have their own DLPI
layer and hence ATM drivers do not supply the shared
library used by lanscan command. The lanscan command
needs to check whether the corresponding driver supports
HP DLPI or not.
PHNE_14634:
1. Multicast DELETE requests were not sent down to the
hardware level by LANC. This resulted in stale
multicast addresses enabled in the hardware. This
has been corrected.
2. There was no support for handling promiscuous data
and the associated filtering at the LANC level.
This was being implemented at the driver level which
was not consistent across drivers. LANC has been
enhanced to support this feature so that drivers
need not implement handling of promiscuous data.
All promiscuous data will be processed by LANC.
3. LANC expects the multicast addresses in the wire
format. However, IP multicast addresses were passed
on in the canonical format which was rejected by
LANC. The fix now converts all multicast addresses
into wire format before calling lanc routines to
enable/disable multicast addresses.
4. lanadmin -A is enhanced to reset the MAC address to
default. When the address string is DEFAULT,
lanadmin restores the default address for the card.
PHNE_14368:
1. The type 2 code has always assumed that the FDDI
drivers support CKO feature. So when it builds the
LLC header for FDDI, the CKO info is always
prepended to it. This is incorrect for some recently
introduced FDDI's that do not support CKO.
2. "linkloop" does not check the MTU on the PPA prior
to sending out the test frame. If the customer has
changed the MTU of the link, linkloop will fail
unless the MTU size (or less) is specified via the
-s parameter. This causes the MC/ServiceGuard
cmlogconfig to fail when it shouldn't. The fix
would be to check the mtu size via DL_HP_PPA_REQ
(dl_mtu) or DL_INFO_REQ (dl_max_sdu) rather than
using the default size for the mac type.
PHNE_14502:
1. Due to a defect in close path of dlpi of PHNE_13586
dlpi clone devices will not be returned to free pool
after close. Due to this reason after a certain number
of operations, utilities like lanadmin, linkloop etc.
will fail as they will not be able to open /dev/dlpi.
2. Process issuing DL_HP_HW_RESET was getting woken up
after PORT_RESET phase of reset process. If a DLPI
request is issued immediately after DL_HP_HW_RESET,
ENXIO may be returned if the driver has not finished
the whole reset process. PORT_RESET phase is now
modified to wake up all entries in cmd_q other than
the one corresponding to RESET process. The RESET
process will be woken up by the process_looper after
the loopback test.
PHNE_13586:
1. hp_dlpi_close was reusing a variable after it is freed,
also it was using a lock after freeing it. Access to the
freed memory was causing the system panic.
2. An enhancement has been made in lanadmin to get and set
driver specific options. This will support speed and
mode changes for 100BT cards.
PHNE_12872:
1. A typo in lan2_int_fr_rnr caused the driver to miss
a call to lan2_rbd_supply. As a result, the
rbd_act_ptr remained to be null. This led to a
panic in lan2_ru_restart later on.
2. For broadcast and multicast packets IP normally
sets a flag indicating driver should not loopback
the packet. HP-PB Ethernet driver does not check
to see whether loopback is required or not. This
causes multiple packets to get delivered to IP.
3. Linkloop on ATM device panics when PHNE_12576 is
installed due to the dlpi detach code assuming
that Driver dependent data structure field in
the hardware specific dlpi data structure points
always to the ift structure of the lan. This is
not true for some devices including ATM. This
causes a panic due to an illegal pointer access.
PHNE_12576:
1. Race condition between deletion of an entry in
dlpi_wakeup_list and processing the entry causes panic
in hp_dlpi_delete_wakeup.
2. If the promiscuous mode application does a close in the
window between setting of lan_ift->promiscuous_filter
and hp_dlpi_datap->promiscuous_flg, promiscuous mode
will not be disabled during close, which causes a panic
when processing the next inbound packet.
3. For drivers supporting IP level multicasting, the
multicast address list is stored in a separate list.
Hence dlpi should check if the driver supports IP level
multicasting. If so it should return the multicast
address list from this list while processing
DL_HP_MULTICAST_REQ.
4. Sequence of setting IFF_UP flag and sending NMV_LINKUP
event from Built-In lan driver causes the ifOPer status
to be incorrect.
5. Due to a wrong call to 'printf' lanadmin command
displays '%s' in output string instead of the error
string.
6. dsname() function in lanadmin opens catalog file using
catopen() but does not close the same on return.
Hence if dsname() is called for sufficiently large
number of times, number of open files will cross
maxfiles limit, causing a failure in the next catopen().
PHNE_11704:
1. The checking of inbound packet was in wire format and
should be in canonical format in hp_dlpi_intr_put()
function.
2. The hp_dlpi_delete_wakeup(), if called by
hp_dlpi_close(), will remove every entry in
dlpi_wakeup_list. For those applications that are
waiting for the response of control requests will not
receive the response. In this case, the application
will appear to hang.
PHNE_11126:
1. DLPI uses hard coded value of 4096 bytes in the code,
thereby limiting the maximum value of MTU to 4096.
2. The NIO Ethernet was trying to acquire a lock already
held by it when operating in promiscuous
mode, resulting in a panic.
PHNE_11052:
1. 64-byte alignment changes to NIO Ethernet for T600
cache-line on 10.20 TFC.
PHNE_10512:
1. When built-in lan interface returns No carrier + Late
collision status in response to a transmit packet
request, builtin lan driver treats the situation as
carrier loss and resets the interface. The fix treats the
situation as late collision, instead.
2. HP-PB Ethernet driver should be modified to support IP
Multicasting. It is supported only on 10.10 release.
It should support IPM on 10.20 release too.
Without the IPM support, certain software (eg:gated,
mrouted) functionality is limited.
3. Lanadmin calls the device specific reset function, if
any, to do the reset operation after changing the H/W
address.
4. Lanadmin calls the device specific reset function, if one
is found, otherwise does the reset by itself.
PHNE_9278:
There was a window to enable netisr when ip input queue was
filled.
This work around to solve the reported problem by enabling
netisr whenever receiving an incoming message.
SR:
8606279225 8606283991 8606294216 8606294894 8606233063
8606233578 8606185750 8606186218 8606106979 8606166220
8606126024 8606155729 8606146371 8606129849 1653288886
8606168898 8606114898 8606152325 8606142643 8606134083
8606154248 5003254151 8606125784 8606130949 8606131979
8606130675 8606129933 8606129886 8606128305 8606126322
8606126350 8606128279 8606103762 8606112422 8606114023
8606128294 1653258665 1653257766 5003442897 5000699934
5003419895 5003315291 5003387050 5003388603 5003408674
1653251025 5003394551 1653232157 5003391888 1653230078
5003386516 5003375949 5003372565 5003362418 4701341230
5003353771 1653158527 8606135125
Patch Files:
/usr/sbin/lanadmin
/usr/sbin/landiag
/usr/sbin/linkloop
/usr/lib/lanadmin/libdslan2.1
/usr/lib/lanadmin/libdslan3.1
/usr/conf/lib/liblan.a
/usr/lib/nls/msg/C/lanadmin.cat
/usr/share/man/man1m.Z/lanadmin.1m
/usr/sbin/lanscan
/usr/share/man/man1m.Z/lanscan.1m
/usr/lib/nls/msg/C/lanscan.cat
/sbin/init.d/hpether
what(1) Output:
/usr/sbin/lanadmin:
lanadmin.c: $Revision: 1.3.116.12 $ B.10.20 PHNE_28
535(700)/PHNE_28536(800)
LAN: Version: B.10.10 $Date: 96/05/09 11:26:21 $
/usr/sbin/landiag:
lanadmin.c: $Revision: 1.3.116.12 $ B.10.20 PHNE_28
535(700)/PHNE_28536(800)
LAN: Version: B.10.10 $Date: 96/05/09 11:26:21 $
/usr/sbin/linkloop:
linkloop.c: PHNE_14367/PHNE_14368 $Revision: 1.7.116
.4 $ $Date: 98/04/17 16:11:11 $
LAN: Version: B.10.10 $Date: 96/05/09 11:26:21 $
/usr/lib/lanadmin/libdslan2.1:
dslan2.c: $Revision: 1.3.116.2 $ $Date: 97/10/01 01:
50:18 $ B.10.20 PHNE_12575(700)/PHNE_12576(8
00)
/usr/lib/lanadmin/libdslan3.1:
dslan3.c: $Revision: 1.3.116.2 $ $Date: 97/10/01 01:
50:40 $ B.10.20 PHNE_12575(700)/PHNE_12576(8
00)
/usr/conf/lib/liblan.a:
lan3.c: PHNE_28535(700)/PHNE_28536(800): $Revision:
1.9.112.20 $ $Date: 2003/03/11 02:18:10 $
lan_t2.c: PHNE_21215(700)/PHNE_21216(800) $Revision:
1.4.112.19 $ $Date: 2000/03/30 18:11:30 $
lan_dlpi.c for PHNE_21903(700)/PHNE_21904(800) $Revi
sion: 1.5.112.38 $ $Date: 2001/01/18 15:40:3
8 $
lanc_input.c: PHNE_28535(700)/PHNE_28536(800) : $Rev
ision: 1.9.112.18 $ $Date: 2003/01/21 18:11:
58$
lanc.c: PHNE_28535(700)/PHNE_28536(800) $Revision: 1
.10.112.18 $ $Date: 2003/01/20 16:42:34 $
FILESET LAN: lib lan: Version: A.10.00
lan2.c: PHNE_22351(700)/PHNE_22352(800) $Revision: 1
.9.112.32 $ $Date: 2000/11/23 03:04:58 $
/usr/lib/nls/msg/C/lanadmin.cat:
None
/usr/share/man/man1m.Z/lanadmin.1m:
None
/usr/sbin/lanscan:
lanscan.c: PHNE_22351(700)/PHNE_22352(800): $Revisio
n: 1.10.116.10 $ $Date: 2000/11/13 01:49:01
$
LAN: Version: B.10.10 $Date: 96/05/09 11:26:21 $
libvmmap.a $Revision: 78.1 $
/usr/share/man/man1m.Z/lanscan.1m:
None
/usr/lib/nls/msg/C/lanscan.cat:
None
/sbin/init.d/hpether:
hpether $Revision: 1.3.116.2 $ $Date: 99/12/31 11:27
:35 $
cksum(1) Output:
383466596 57344 /usr/sbin/lanadmin
383466596 57344 /usr/sbin/landiag
1517170158 40960 /usr/sbin/linkloop
863657114 16384 /usr/lib/lanadmin/libdslan2.1
1780037666 16384 /usr/lib/lanadmin/libdslan3.1
1112345819 383952 /usr/conf/lib/liblan.a
2104969713 5483 /usr/lib/nls/msg/C/lanadmin.cat
3710548927 3763 /usr/share/man/man1m.Z/lanadmin.1m
3981828067 53248 /usr/sbin/lanscan
2256967076 1718 /usr/share/man/man1m.Z/lanscan.1m
1489511935 2172 /usr/lib/nls/msg/C/lanscan.cat
1908115670 5577 /sbin/init.d/hpether
Patch Conflicts: None
Patch Dependencies:
s800: 10.20: PHCO_10947
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHNE_9278 PHNE_10512 PHNE_11052 PHNE_11126 PHNE_11704 PHNE_12576
PHNE_12872 PHNE_13586 PHNE_14502 PHNE_14368 PHNE_14634 PHNE_17000
PHNE_18174 PHNE_18924 PHNE_20656 PHNE_21216 PHNE_21904 PHNE_22352
PHNE_23862 PHNE_26072
Equivalent Patches:
PHNE_28535:
s700: 10.20
Patch Package Size: 390 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_28536
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHNE_28536.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHNE_28536. If you do not wish to retain a
copy of the original software, you can create an empty file
named /var/adm/sw/patch/PATCH_NOSAVE.
WARNING: If this file exists when a patch is installed, the
patch cannot be deinstalled. Please be careful
when using this feature.
It is recommended that you move the PHNE_28536.text file to
/var/adm/sw/patch for future reference.
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_28536.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHNE_28536------------------------------------------
Document ID: PHSS_28738
Date Loaded: 20030521
Title: s700_800 10.20 OV OB4.10 patch - CC packet
Patch Name: PHSS_28738
Patch Description: s700_800 10.20 OV OB4.10 patch - CC packet
Creation Date: 03/05/07
Post Date: 03/05/21
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products:
OmniBackII A.04.10
Filesets:
OMNIBACK-II.OMNI-HPUX-P,A.04.10
OMNIBACK-II.OMNI-OTHUX-P,A.04.10
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_28738
Symptoms:
PHSS_28738:
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_28331:
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_27587:
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_26877:
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_26341:
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_28738:
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_28331:
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_27587:
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_26877:
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_26341:
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.
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:
/opt/omni/databases/vendor/cc/hp/s800/hp-ux-1020/A.04.10/
packet.Z
/opt/omni/databases/vendor/cc/hp/s800/hp-ux-11/A.04.10/
packet.Z
/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
/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
what(1) Output:
/opt/omni/databases/vendor/cc/hp/s800/hp-ux-1020/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/hp/s800/hp-ux-11/A.04.10/
packet.Z:
None
/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
/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
cksum(1) Output:
3256642456 39356215 /opt/omni/databases/vendor/cc/hp/s800/
hp-ux-1020/A.04.10/packet.Z
2325068595 39361389 /opt/omni/databases/vendor/cc/hp/s800/
hp-ux-11/A.04.10/packet.Z
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
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
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_28731:
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_28731 is required for these defect fixes.
PHSS_28723:
SAP packet patch,
Release Date: Available
Id = HSLco37193 SR:H555008807
PHSS_28723 is required for this defect fix.
PHSS_28584:
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_28584.
PHSS_28341:
EMC packet patch,
Release Date: Available
Id = HSLco37193 SR:H555008807
PHSS_28341 is required for this defect fix.
PHSS_28333:
Media Agent (MA) packet patch,
Release Date: Available
Id = HSLco36526 SR:B555014660
Id = HSLco34581 SR:H555007993
PHSS_28333 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_26341 PHSS_26877 PHSS_27587 PHSS_28331
Equivalent Patches:
PHSS_28739:
s700: 11.00 11.11 11.20
s800: 11.00 11.11 11.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_28738
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_28738.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_28738. If you do not wish to retain a
copy of the original software, you can create an empty file
named /var/adm/sw/patch/PATCH_NOSAVE.
WARNING: If this file exists when a patch is installed, the
patch cannot be deinstalled. Please be careful
when using this feature.
It is recommended that you move the PHSS_28738.text file to
/var/adm/sw/patch for future reference.
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_28738.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_28738:
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_28738------------------------------------------
Document ID: PHNE_28635
Date Loaded: 20030521
Title: s700_800 10.20 EISA 100BT cumulative patch
Patch Name: PHNE_28635
Patch Description: s700_800 10.20 EISA 100BT cumulative patch
Creation Date: 03/04/29
Post Date: 03/05/21
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products:
EISA100BT B.10.20.01 B.10.20.02 B.10.20.03 B.10.20.04
B.10.20.05
Filesets:
100BT-EISA-KRN.100BT-KRN,B.10.20.01,B.10.20.02,B.10.20.03
100BT-EISA-KRN.100BT-KRN,B.10.20.04,B.10.20.05
100BT-EISA-RUN.100BT-INIT,B.10.20.01,B.10.20.02,B.10.20.03
100BT-EISA-RUN.100BT-INIT,B.10.20.04,B.10.20.05
100BT-EISA-RUN.100BT-RUN,B.10.20.01,B.10.20.02,B.10.20.03
100BT-EISA-RUN.100BT-RUN,B.10.20.04,B.10.20.05
100BT-EISA-FMT.100BT-FORMAT,B.10.20.01,B.10.20.02,B.10.20.03
100BT-EISA-FMT.100BT-FORMAT,B.10.20.04,B.10.20.05
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHNE_28635: PANIC
PHNE_27533: PANIC
PHNE_24782: PANIC
PHNE_23980: HANG
PHNE_22443: OTHER
System will not be on the network if the
primary interface is EISA 100BT.
PHNE_21373: PANIC
PHNE_19199: PANIC
PHNE_16153: PANIC
PHNE_13721: OTHER
Multicast & Promiscuous mode not working
PHNE_11507: OTHER
MAC Address change results in card not working
PHNE_10145: OTHER
ServiceGuard fails over EISA 100bt
Path Name: /hp-ux_patches/s700_800/10.X/PHNE_28635
Symptoms:
PHNE_28635:
1. ( SR:8606294055 CR:JAGae57795 )
Inadequate frame padding.
2. ( SR:8606289350 CR:JAGae53281 )
When the lanadmin(1M) command is used with the "-x"
option to query the EISA 10/100BT interface, the system
may panic with the following stack trace.
HP1_ospif_dlpi_ioctl+0x784
hp_dlpi_process_ioctl+0xf8
hp_dlpi_wput+0x188
putnext+0x74
wait_iocack+0x88
str_istr_ioctl+0x3f8
hpstreams_ioctl_int+0x590
hpstreams_ioctl+0x54
spec_ioctl+0xd4
vno_ioctl+0x98
ioctl+0x78
syscall+0x75c
syscallinit+0x320
PHNE_27533:
1. ( SR:8606188846 CR:JAGad58062 )
During heavy traffic EISA 10/100BT card experiences
multiple internal resets with the following message
logged to NetTL log file.
"bdm_watchdog: TX did not complete on time, resetting
adapter btlan01".
2. ( SR:8606174509 CR:JAGad43755 )
On a system with two or more EISA 10/100BT cards,
when the switch or hub is reset or powered off and on,
only one of the EISA 10/100BT card comes up.
3. ( SR:8606248819 CR:JAGae15216 )
EISA 100BT driver panics with "Data page fault" in
_bigmac_cmdfmt_tx().
4. ( SR:8606219928 CR:JAGad89070 )
"dhcpclient" fails to generate bootp request over
EISA 10/100BT interface.
PHNE_24782:
1. EISA 100BT driver panics with "Spinlock Deadlock"
in ospif_if_watchdog() and schednetisrsq().
-- JAGad69452
PHNE_23980:
1. EISA FDDI driver hangs because of EISA 100BT's
bus locking. -- JAGad50169
2. Reproducible system hang in oim_open() when
starting SAP. -- JAGad54480
3. suid bit set to lanadmin library. -- JAGad67830
PHNE_22443:
1. Card does not work in loopback mode with changed MAC
address in hpeisabtconf -- JAGad09607
PHNE_21373:
1. PHNE_19199 can impact configuration files for systems
having pre June 1999 AR version of the
EISA 10/100Base-TX/9000 product -- JAGac86743.
2. Potential spinlock deadlock in PHNE_19199 -- JAGad02653.
PHNE_19199:
1. EISA100BT sends corrupted MAC address for DLPI
test-xid requests. -- JAGaa41098
2. linkloop to self doesn't return error when cable is not
connected. -- JAGab03857
3. IP multicast datagrams looped back in the driver.
-- JAGaa41968
4. EISA100BT driver doesn't set ifOper status correctly
in the MIB structure. -- JAGaa21367
5. Some required EISA100BT structures are not available
on Q4. -- JAGaa21642
6. Automatic speed configuration doesn't work for EISA100BT.
-- JAGab46349
7. EISA100BT start-up doesn't give a warning when set to
full duplex. -- JAGaa21652
8. netstat -I is not working due to non-standard interface
naming convention. -- JAGab64848
9. Setting the speed is not possible in hpeisabtconf file.
-- JAGab65054
10. nettl traces are not formatted correctly. -- JAGab64926
11. Minimum frame length in 10BT mode should be 60 bytes
instead of 64 bytes. -- JAGab64392
12. ER: Allow the MTU size configuration using lanadmin.
-- JAGab64413
13. ER: IOCTL support is required for speed and duplex
setting using SAM. -- JAGab64697
14. EISA100BT generates duplicate packets under heavy load.
-- JAGab64911
15. Service Guard doesn't work with new interface naming
convention. -- JAGab64435
16. Interface state stays UP after Service Guard's local
switching. -- JAGab64418
17. Startup script does not allow for non-sequential arrays.
-- JAGab70575
18. Panic with 'Already Owns this Spinlock' on EISA 100BT.
-- JAGab68637
19. "lanadmin -S 0" command hangs.
-- JAGab72670
20. Panic during DLPI multicast testing.
-- JAGab84308
21. DLPI primitive to set physical address succeeds even
for invalid values -- JAGab84309
22. Driver does not return error for invalid multicast
addresses. -- JAGab84311
PHNE_16402:
1. Performance degradation.
PHNE_16153:
1. EISA 100BASE-T card does not come up on 715/100/E
workstations.
2. When there is heavy network traffic, EISA 100BASE-T
card does not come up at boot time.
3. EISA 100BASE-T panics on D and C class with Data
Page fault under heavy load.
PHNE_13721:
1. SAP promiscuous mode and layer2 multicast are not
supported.
2. SNAP LLC encapsulation is not supported.
3. When a request for factory MAC address is issued, the
EISA 100BT driver returns the current MAC address
instead.
4. Initialization scripts to alter the MAC address or the
duplex mode do not function correctly.
PHNE_11507:
The following symptoms correspond to the descriptions in
the defect descriptions fields for PHNE_11507:
Changing the MAC address on EISA 100BT card prevents further
correct operation of the card.
PHNE_10145:
The following symptoms correspond to the descriptions in
the defect descriptions fields for PHNE_10145:
Failover does not work correctly in ServiceGuard.
Defect Description:
PHNE_28635:
1. ( SR:8606294055 CR:JAGae57795 )
Inadequate frame padding.
Resolution:
Adequate frame padding is done.
2. ( SR:8606289350 CR:JAGae53281 )
When EISA 10/100BT interface self-test fails, a field in
the driver data structure is not initialized properly.
The system panics when the lanadmin(1M) command with
"-x" option tries to access this uninitialized field.
Resolution:
Proper check has been added to avoid accessing
uninitialized field in the driver data structure.
PHNE_27533:
1. ( SR:8606188846 CR:JAGad58062 )
The "Command Unit" of the EISA 10/100BT card goes into
an "IDLE" state even when there are packets queued up
for transmit. This would cause the card to be unaware
of new packets posted for transmission resulting in
bdm_watchdog timer going off thus triggering a card
reset.
Resolution:
If the "Command Unit" has gone into "IDLE" state and
transmit queue is not empty, then the "Command Unit" is
restarted in bigmac watchdog routine.
2. ( SR:8606174509 CR:JAGad43755 )
A single global variable was used to represent
"link state" for multiple instances of EISA 10/100BT
interfaces.
Resolution:
Separate "link state" variable is used for every
instance of EISA 10/100BT interface.
3. ( SR:8606248819 CR:JAGae15216 )
In response to EISA 100BT driver's dump command request,
the interface should dump card's internal registers onto
the host preallocated memory location. Instead, the data
was written on to the transmit descriptor thus corrupting
the transmit descriptor ring.
Resolution:
A separate descriptor is allocated for the dump
command.
4. ( SR:8606219928 CR:JAGad89070 )
"dhcpclient" uses DLPI_BIND_XPORT and DLPI_UNBIND_XPORT
ioctls to generate bootp request over EISA 10/100BT
interface, which are missing in EISA 100BT driver.
Resolution:
DLPI_BIND_XPORT and DLPI_UNBIND_XPORT ioctls are added
to support bootp request over EISA 10/100BT interface.
PHNE_24782:
1. Drivers should not hold the 'driver' lock while calling
functions across the subsystem. But, EISA 100BT driver
was calling schednetisr() holding driver lock, which
resulted in a panic.
Resolution:
Code has been modified such that driver will release
its 'driver' lock before calling schednetisr().
PHNE_23980:
1. EISA 100BT was holding bus unnecessarily because of
which EISA FDDI driver was hanging.
Resolution:
Unnecessary bus locking has been removed.
2. In the oim_open() function, a linked list was
processed improperly in a while loop.
Resolution:
Processing of the linked list has been modified in
the while loop.
3. The lanadmin library was set with suid bit.
Resolution:
File permissions have been modified.
PHNE_22443:
1. During card's reset mode, card loopbacks itself with
factory MAC address to sense speed. After this, card
was resetting with factory MAC address. It was not using
newly configured MAC address.
Resolution:
After loopback, card will be set with new MAC address.
PHNE_21373:
1. If PHNE_19199 is installed on a system having pre June
1999 Application Release (AR) version of the
EISA 10/100Base-TX/9000 product, the interface names of
EISA 100BT devices are changed from btlan0x to lanx
(where x is the interface index). This could cause
problem for products such as Service Guard and OSI
Transport Services, whose configuration files refer to
EISA 100BT interfaces with the old naming
convention(btlan0x).
Resolution:
A script is provided with this patch to interactively
modify all occurrences of "btlan0" to "lan" in an ASCII
text file supplied as an argument to it. The users can
run this script on their configuration files to perform
the switch to the new interface naming convention.
2. The spinlock deadlock was caused due to a lock ordering
problem between two spinlocks used by the driver.
Resolution:
The lock ordering has been corrected.
PHNE_19199:
1. An upper layer didn't set the source MAC address
while passing the packet to the driver and driver
expected MAC address to be set by upper layer.
Resolution:
Modified transmit path to copy source MAC address
for outbound packets.
2. Driver was not checking interface status for
loopback packets.
Resolution:
Code is modified to check interface status before
looping back the packet.
3. Driver didn't check whether it needs to loop back
the multicast packet to the local host.
Resolution:
The code was modified to check whether driver needs
to loop back the multicast packet.
4. EISA100BT driver was not consistent in setting ifOper
Status in the MIB with respect to lanscan.
Resolution:
Modified code to have consistency for lanadmin &
lanscan states.
5. Some required EISA100BT structures are not available
in debug file.
Resolution:
Added the necessary structures that are required for
debugging.
6. EISA100BT start-up script was not passing the speed
value to the 'lanadmin' command.
Resolution:
Start-up script was modified to pass the speed value
to the 'lanadmin' command.
7. EISA100BT start-up script didn't check for full duplex
mode setting.
Resolution:
Added a checking for invalid speed values.
8. netstat was not able to recognize EISA100BT interface
due to non-standard naming convention.
Resolution:
Modified EISA100BT interface to standard naming
convention.
9. hpeisabtconf file didn't support SPEED variable.
Resolution:
Added SPEED variable in hpeisabtconf file.
10. EISA100BT subsystem formatter was not able to
format the packets properly.
Resolution:
Rewrote the subsystem formatter to fix formatting
problems.
11. EISA100BT driver supported a minimum packet length
of 64 bytes in 10BT mode instead of the standard 60
bytes.
Resolution:
Modified the driver to support a minimum packet
length of 60 bytes instead of 64 bytes.
12. ER: Allow the MTU size configuration using lanadmin.
Resolution:
Added new IOCTL requests to support set/reset MTU
values.
13. ER: IOCTL support is required for speed and duplex
setting using SAM.
Resolution:
Modified driver to support additional ioctl requests
that are required for SAM support.
14. EISA100BT card was sending duplicate packets under
heavy UDP traffic.
Resolution:
Modified transmit path to flush/purge the data in the
cache and synchronized shared memory access between
card and memory.
15. While changing the driver to new naming convention,
the ifDescr variable was not modified to reflect the
same.
Resolution:
Modified the ifDescr variable to use the new naming
convention.
16. Interface state used to stay UP after IP address
was moved to a different interface and cable was
reconnected.
Resolution:
Modified code to store previous interface state
before bringing the interface DOWN. The saved
interface state will be checked to bring interface
UP.
17. Startup script was not able to recognize interface
entries in non-sequential order in file
/etc/rc.config.d/hpeisabtconf
Resolution:
Startup script is modified to process all interface
entries in file /etc/rc.config.d/hpeisabtconf, even
if they are in non-sequential order.
18. The panic happens when the driver receives a
SET_SPEED ioctl when there are pending inbound
packets.
Resolution:
Modified the code to release lock and
reclaim it again after processing pending inbound
packets.
19. Driver used to return negative value for invalid speed
values, due to which DLPI sleeps, and hence the lanadmin
command used to hang.
Resolution:
The driver now returns EINVAL to DLPI in case of an
invalid speed value.
20. The routine that deletes multicast addresses from the
driver's table was stepping out of the table boundary
and hence causing memory corruption.
Resolution:
This routine is changed to prevent memory corruption.
21. The DLPI primitive to set physical address succeeds
even for invalid values (all bits 0's or 1's).
Resolution:
A check has been added for these invalid addresses.
22. Driver returns success for invalid multicast hardware
addresses which do not have the least significant bit
of the first byte set.
Resolution:
A check is now made to ensure that this bit is set.
PHNE_16402:
1. A busy-wait in the performance path caused the
performance degradation.
PHNE_16153:
1. The driver did not set the speed correctly in 10Mb mode.
This occurred mainly on 715/100/E systems.
2. The driver sent a loopback packet without sensing the
media speed. The default speed was set to 100Mb. So,
under heavy network traffic the driver failed to receive
the loopback packet in 10Mb mode.
3. The driver did not do proper MP synchronization.
PHNE_13721:
1. Specific code for support of Promiscuous mode and layer2
multicast did not exist.
2. Specific code for support of SNAP LLC encapsulation did
not exist.
3. The driver incorrectly returned the current MAC address
when the factory MAC address was requested.
4. Variable names were inconsistent in hpeisabtconf and
hpeisabt scripts.
PHNE_11507:
The following defect description is for PHNE_11507:
Although the command for MAC address change completed
successfully, the change was registered only in the
software data-structures and not in the card (hardware).
PHNE_10145:
The following defect description is for PHN_10145:
When the primary cable is disconnected, the secondary
does not reflect UP state in lanscan to indicate the
successful Failover of ServiceGuard.
SR:
8606294055 8606289350 8606188846 8606174509 8606248819
8606219928 8606200268 8606180948 8606185278 8606198641
8606140285 8606129197 8606133508 5003397125 5003409003
5003451450 5003440230 1653289090 1653296236 4701430116
5003434928 1653311423 1653298547 8606103630 8606102706
8606104897 8606112069 8606112070 8606112072 1653275446
1653264465 1653267237 1653263970 1653253013 1653250639
1653255968 1653249318 1653219378 4701347781
Patch Files:
/usr/conf/lib/libbtlan0.a
/usr/lib/nls/msg/C/dsbtlan0.cat
/usr/lib/lanadmin/libdsbtlan0.sl
/usr/sbin/hpeisabt_init
/usr/newconfig/etc/rc.config.d/hpeisabtconf
/sbin/init.d/hpeisabt
/usr/lib/libeisa100btfmt.sl
/usr/newconfig/usr/conf/lib/libbtlan0.abtlan0
/usr/sbin/chbtlan0tolan
/usr/lib/nls/msg/C/fmteisa100bt.cat
what(1) Output:
/usr/conf/lib/libbtlan0.a:
FILESET EISA100BT: libbtlan0: Version: B.10.20.17 P
HNE_28635 $Date: 2003/02/07 21:50:53 $
/usr/lib/nls/msg/C/dsbtlan0.cat:
None
/usr/lib/lanadmin/libdsbtlan0.sl:
EISA100BT LANADMIN: libdsbtlan0: Version: B.10.20.1
7 PHNE_28635 $Date: 2003/02/07 22:22:54 $
/usr/sbin/hpeisabt_init:
None
/usr/newconfig/etc/rc.config.d/hpeisabtconf:
None
/sbin/init.d/hpeisabt:
None
/usr/lib/libeisa100btfmt.sl:
EISA100BT NETTL: libeisa100btfmt: Version: B.10.20.
17 PHNE_28635 $Date: 2003/02/07 22:25:57 $
/usr/newconfig/usr/conf/lib/libbtlan0.abtlan0:
FILESET EISA100BT: libbtlan0: Version: B.10.20.16 P
HNE_28635 $Date: 2003/02/07 21:50:53 $
/usr/sbin/chbtlan0tolan:
None
/usr/lib/nls/msg/C/fmteisa100bt.cat:
None
cksum(1) Output:
1377307198 317096 /usr/conf/lib/libbtlan0.a
3862894740 3138 /usr/lib/nls/msg/C/dsbtlan0.cat
785061898 36864 /usr/lib/lanadmin/libdsbtlan0.sl
780528253 5258 /usr/sbin/hpeisabt_init
3271958431 1237 /usr/newconfig/etc/rc.config.d/hpeisabtconf
2418239947 7667 /sbin/init.d/hpeisabt
1289306118 16384 /usr/lib/libeisa100btfmt.sl
470323117 317112 /usr/newconfig/usr/conf/lib/
libbtlan0.abtlan0
2014630193 5168 /usr/sbin/chbtlan0tolan
3989282158 5124 /usr/lib/nls/msg/C/fmteisa100bt.cat
Patch Conflicts: None
Patch Dependencies:
s700: 10.20: PHNE_13585
s800: 10.20: PHNE_13586
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHNE_10145 PHNE_11507 PHNE_13721 PHNE_16153 PHNE_16402 PHNE_19199
PHNE_21373 PHNE_22443 PHNE_23980 PHNE_24782 PHNE_27533
Equivalent Patches:
PHNE_28636:
s700: 11.00
s800: 11.00
PHNE_28637:
s700: 11.11
s800: 11.11
Patch Package Size: 350 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_28635
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHNE_28635.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHNE_28635. If you do not wish to retain a
copy of the original software, you can create an empty file
named /var/adm/sw/patch/PATCH_NOSAVE.
WARNING: If this file exists when a patch is installed, the
patch cannot be deinstalled. Please be careful
when using this feature.
It is recommended that you move the PHNE_28635.text file to
/var/adm/sw/patch for future reference.
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_28635.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
1. A new copy of the hpeisabtconf file is provided
under the directory /usr/newconfig/etc/rc.config.d.
It is recommended that the local modifications
to the /etc/rc.config.d/hpeisabtconf file be
incorporated into the new copy and be placed
under the directory /etc/rc.config.d. This new
hpeisabtconf is modified to support new
speed/duplex setting options for startup script.
2. From its 10.20.03 version (or patch PHNE_19199)
onwards, the EISA 10/100Base-TX/9000 product
began using the standard naming convention for
network interface names.
In the new or standard interface naming
convention, the name reported by the lanscan(1M)
command for these devices is lanx, where x is
the interface index.
In the old interface naming convention, the name
reported by the lanscan command for these devices
was btlan0x, where x is the interface index.
This patch WILL NOT change the existing EISA 100BT
interface naming convention existing on the system.
Based on the naming convention currently used the
appropriate patch files will be installed.
If you have a version older than 10.20.03 on your
system, and if you desire to migrate to the new
naming convention, then you must upgrade to
version 10.20.03 or later available as of the 1998
Application Release.
-----End of Document ID: PHNE_28635------------------------------------------
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]