|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: IT Resource Center (support_feedback
us-support.external.hp.com)Date: Fri Jan 05 2001 - 05:32:29 CST
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:
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:
Login using your IT Resource Center User ID and Password.
Then select Individual Patches (under Maintenance and Support)
to access the patch. You may also download a patch via anonymous
ftp(1) from ftp.itrc.hp.com.
===============================================================================
Digest Name: weekly HP-UX series 700 11.X patch digest
Created: Sun Dec 31 3:05:10 PST 2000
Table of Contents:
Document ID Title
--------------- -----------
PHSS_22928 s700_800 11.04 (VVOS) AudioSubsystem 06/2000 Periodic Patch
PHCO_22931 s700_800 11.04 (VVOS) mksf(1M) cumulative patch
PHSS_22683 s700_800 11.X MC/ServiceGuard and SG-OPS Edition A.11.09
PHKL_22792 s700_800 11.00 Fix VM page read-ahead panics
PHKL_22785 s700_800 11.00 HPMC, FC reset & conn, chassis log, I20 RAID
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHSS_22928
Date Loaded: 20001228
Title: s700_800 11.04 (VVOS) AudioSubsystem 06/2000 Periodic Patch
Patch Name: PHSS_22928
Patch Description: s700_800 11.04 (VVOS) AudioSubsystem 06/2000 Periodic Patch
Creation Date: 00/12/15
Post Date: 00/12/28
Hardware Platforms - OS Releases:
s700: 11.04
s800: 11.04
Products: N/A
Filesets:
AudioSubsystem.AUDIO-SHLIBS,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_22928
Symptoms:
PHSS_22928:
Repackage base HP-UX patch PHSS_21663 for VVOS.
Note that the Aserver is not supported on VVOS.
Only the shared libraries are provided with this patch.
Based on HP-UX patch PHSS_21663:
1. Aserver leaves empty file
2. asecure has bad file permission
3. Insufficient memory allocated in Aserver and asecure
Based on HP-UX patch PPHSS_21482:
1. Aserver has bad file permissions.
Based on HP-UX patch PPHSS_18778:
1. Aserver has memory leaks.
Based on HP-UX patch PPHSS_17979:
1. Aserver -f option is not working correctly.
2. Aserver man page has incorrect information.
3. Audio lib has memory leak for -server option.
4. Audio widgets library dumps core.
Based on HP-UX patch PPHSS_17119:
1. Audio lib has memory leaks
2. Incorrect handling of processes in Aserver
3. Local DCE RPC not enabled in Aserver
4. Incorrect sample values from AGetTransStatus()
5. Aserver hangs if several background send_sounds are
started
Defect Description:
PHSS_22928:
Repackage base HP-UX patch PHSS_21663 for VVOS.
Note that the Aserver is not supported on VVOS.
Only the shared libraries are provided with this patch.
Based on HP-UX patch PPHSS_21663:
1. Aserver leaves empty file
2. asecure has bad file permission
3. Insufficient memory allocated in Aserver and asecure
Based on HP-UX patch PPHSS_21482:
1. Aserver has bad file permissions.
Resolution:
1. File permissions for Aserver has been changed to 0555.
Based on HP-UX patch PPHSS_18778:
1. Aserver has memory leaks.
Resolution:
1. free() called to plug the memory leaks in the
Aserver code.
Based on HP-UX patch PPHSS_17979:
1. Aserver -f option is not working correctly.
2. Aserver man page has incorrect information .
3. Audio lib has memory leak for -server option.
4. Audio widgets library dumps core .
Resolution:
1. When Aserver is executed with -f option the Aserver code
did not take care of removing the old Aserver
interfaces.This fix kills all the Aserver instances
when Aserver is invoked with Aserver -f option.
2. Ordinary users are allowed to restart the Aserver. But it
was documented that only root can restart the Aserver.
This incorrect documentation is changed in the Aserver
man page.
3. The free() library call was called at appropriate places.
4. Code specific to nck lib which is not delivered 11.00
onwards changed to dce specific.
Based on HP-UX patch PPHSS_17119:
1. Audio lib has memory leaks
2. Incorrect handling of processes in Aserver
3. Local DCE RPC not enabled in Aserver
4. Incorrect sample values from AGetTransStatus()
5. Aserver hangs if several background send_sounds are
started
SR:
8606124961 8606125261 8606134161 4701426619 4701408930
5003437368 5003409748 1653252585 1653272682
Patch Files:
AudioSubsystem.AUDIO-SHLIBS,fr=B.11.04,
fa=HP-UX_B.11.04_32/64,v=HP:
/opt/audio/lib/libAlib.1
/opt/audio/lib/libAlib.2
/opt/audio/lib/libAt.1
/opt/audio/lib/libAt.2
/opt/audio/lib/libAt.3
what(1) Output:
AudioSubsystem.AUDIO-SHLIBS,fr=B.11.04,
fa=HP-UX_B.11.04_32/64,v=HP:
/opt/audio/lib/libAlib.1:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Apr
1999 Patch Release
(build date: Sat Mar 20 04:51:04 MST 1999)
/opt/audio/lib/libAlib.2:
X Window System, Version 11 R6+ HP-UX B.11.00.00 Apr
1999 Patch Release
(build date: Mon Mar 22 02:55:27 MST 1999)
/opt/audio/lib/libAt.1:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Apr
1999 Patch Release
(build date: Sat Mar 20 05:57:32 MST 1999)
/opt/audio/lib/libAt.2:
X Window System, Version 11 R6+ HP-UX B.10.20.00 Apr
1999 Patch Release
(build date: Sun Mar 21 21:46:52 MST 1999)
/opt/audio/lib/libAt.3:
X Window System, Version 11 R6+ HP-UX B.11.00.00 Apr
1999 Patch Release
(build date: Mon Mar 22 03:01:29 MST 1999)
cksum(1) Output:
AudioSubsystem.AUDIO-SHLIBS,fr=B.11.04,
fa=HP-UX_B.11.04_32/64,v=HP:
3576145714 176128 /opt/audio/lib/libAlib.1
3163714669 167936 /opt/audio/lib/libAlib.2
1854311554 65536 /opt/audio/lib/libAt.1
3758439410 65536 /opt/audio/lib/libAt.2
298374357 61440 /opt/audio/lib/libAt.3
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches:
PHSS_21662:
s700: 10.01 10.10 10.20
s800: 10.01 10.10 10.20
PHSS_21663:
s700: 11.00
s800: 11.00
Patch Package Size: 550 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_22928
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_22928.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_22928. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHSS_22928.depot
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_22928.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_22928.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_22928.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHSS_22928------------------------------------------
Document ID: PHCO_22931
Date Loaded: 20001228
Title: s700_800 11.04 (VVOS) mksf(1M) cumulative patch
Patch Name: PHCO_22931
Patch Description: s700_800 11.04 (VVOS) mksf(1M) cumulative patch
Creation Date: 00/12/11
Post Date: 00/12/28
Hardware Platforms - OS Releases:
s700: 11.04
s800: 11.04
Products: N/A
Filesets:
OS-Core.UX-CORE,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP
OS-Core.CORE-ENG-A-MAN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP
VirtualVaultOS.VVOS-AUX-IA,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical:
Yes
PHCO_22931: PANIC
Based on PHCO_21596: PANIC
Category Tags:
defect_repair enhancement general_release critical panic
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_22931
Symptoms:
PHCO_22931:
port HP-UX patch PHCO_21596 (mksf cumulative) to VVOS.
Based on HP-UX patch PHCO_21596:
1) rmsf panics for interface cards. rmsf panics when
hardware path(for -H) or special file(for -a/-k) of
interface card is specified. The panic message is:
Data Page Fault, Type 15&13 - panic: Conditional trap.
-- 8606136041.
2) insf gives error when specifying instance number greater
than 255. The error message is
"insf : valid value for instance must be between 0 and 255"
-- 8606133730.
3)Insf will output "Don't know how to handle driver ..."
warning message, for drivers with no insf support
-- 5003394270.
4) lssf does not recognize new tape densities. There are new
tape densities like DLT_85937_52, DLT_85937_52c, and so on
which are listed by lssf as unknown densities-- 8606104841.
5)Insf core dumps on N-class with SEOS in the kernel
-- 8606135659.
Based on HP-UX patch PHCO_20182:
insf does not create USB device special files which
may be found on the B1000, C3000, and J5000 systems.
This patch also allows valid /dev/crt files to remain
unchanged when device files are created for the
framebuf pseudo driver. Existing configuration files
which contain references to /dev/crt device files are
less likely to have to change when a graphics card is
added or moved.
PHCO_19126:
Port HP-UX patch PHCO_19032 (mksf cumulative) to VVOS.
Based on HP-UX patch PHCO_19032:
Insf will output "Don't know how to handle driver ..."
warning message, for drivers with no insf support.
Some mux boards may have incorrect special files
created, if the hardware failed the diagnostics
routines.
Based on HP-UX patch PHCO_18302:
The man pages for insf(1M)/mksf(1M) do not reflect GSPdiag
device files (for SAS console).
On removing the patch PHCO_17090, the file
/var/adm/sw/swagent.log will contain the text
"/var/adm/sw/products/PHCO_18302/pfiles/postremove[38]:
test: A ] character is missing".
Based on HP-UX patch PHCO_17090:
More than 999 PTS device files cannot be created due to
exhaustion of name space(t[0-9,A-z][0-9,A-z][0-9,A-z]).
Based on HP-UX patch PHCO_16632:
Support to create SAS console devices files.
Creating pts device files in base-64
alphanumeric characters.
Lssf does not report some of DLT tape densities properly.
Based on HP-UX patch PHCO_15746:
Insf does not know how to handle "fcp" driver
Based on HP-UX patch PHCO_13571:
Need support for IBM 3590 cartridge format
Defect Description:
PHCO_22931:
port HP-UX patch PHCO_21596 (mksf cumulative) to VVOS.
Based on HP-UX patch PHCO_21596:
1)rmsf panics for interface cards.
Resolution: rmsf now checks the hardware type of the
specified hardware path(for -H option) or special file
name (for -a/-k) and if hardware type is DEVICE removes
its special files and device definition from the system.
Otherwise removes special file for leaf nodes and children
only for non leaf nodes.
2) insf gives error when specifying instance number greater
than 255
Resolution:The insf is modified check the instance number
range between 0 and maximum integer value.
3)Insf will output "Don't know how to handle driver ..."
warning message, for drivers with no insf support.
Resolution:These drivers are added to driver_entry_table[]
which will have corresponding insf,lssf and mksf function
pointers.
4) The new tape densities are not included in the database
maintained by lssf.
Resolution:The database is updated with new tape
densities.
5)Insf core dumps on N-class with SEOS in the kernel
because the varargs parameter to a function was not NULL
terminated.
Resolution: The parameter list is now NULL terminated.
Based on HP-UX patch PHCO_20182:
1)insf does not create USB device drivers
2)If a graphics device is added or moved in a system,
the relationship between /dev/crt special files and
graphics devices is not preserved for those devices
which are not changed. This applies to systems
which have more than one graphics device.
3)Added support for superio 3.5 inch floppy driver.
Resolution:
USB device files are created as needed.
/dev/crt device files that correspond to valid
graphics devices are not changed. This device
files are created for the framebuf pseudo driver.
superio floppy device files are created as needed.
PHCO_19126:
Port HP-UX patch PHCO_19032 (mksf cumulative) to VVOS.
Based on HP-UX patch PHCO_19032:
Insf gives error when there is no support for a driver
Resolution:
Insf no longer considers not knowing how to handle a driver
an error. (Mksf still does). A driver may not need special
file support in mksf.
Insf ran out of file descriptors when opening diag file.
Resolution:
Fixed file descriptor leak. There was a return, before a
close.
Based on HP-UX patch PHCO_18302:
The man pages for insf(1M)/mksf(1M) make no reference to
GSPdiag device files. These device files are used by the
SAS console.
Fixed the postremove script.
Resolution:
Fixed the insf.1m man page to include GSPdiag device files.
Fixed the shell test operator "[" syntax eror in the
postremove script.
Based on HP-UX patch PHCO_17090:
PTS device files greater than
999 are created in base64 encoding.
Based on HP-UX patch PHCO_16632:
Support for creatng device files for SAS console.
Support to create pts device files in base-64
alphanumeric characters.
Lssf reported "unknown density" for
some of the DLT densities in the table.
Based on HP-UX patch PHCO_15746:
The fcp and fcT1_cntl drivers did not have entries in
look up table.So noop entries were created for these
two drivers.
Based on HP-UX patch PHCO_13571:
Support for 3590 cartridge format in density
table for both compressed and uncompressed.
This would also support Fujitsu M2481 and
M2483 tape devices.
SR:
5003394270 8606133730 8606104841 8606136041 8606135659
5003397950 4701394767 4701389569 4701395301 4701377705
Patch Files:
OS-Core.UX-CORE,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
/sbin/insf
/sbin/lssf
/sbin/mksf
/sbin/rmsf
/usr/sbin/insf
/usr/sbin/lssf
/usr/sbin/mksf
/usr/sbin/rmsf
OS-Core.CORE-ENG-A-MAN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,
v=HP:
/usr/share/man/man1m.Z/insf.1m
/usr/share/man/man1m.Z/mksf.1m
/usr/share/man/man1m.Z/rmsf.1m
VirtualVaultOS.VVOS-AUX-IA,fr=B.11.04,
fa=HP-UX_B.11.04_32/64,v=HP:
/etc/auth/system/files.fcdb/05.patches/19126_PHCO.fcdb
what(1) Output:
OS-Core.UX-CORE,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
/sbin/insf:
$Revision: Hewlett-Packard ISSL Level vvos_rose42 $
$Header: Hewlett-Packard ISSL Release vvos_r
ose $ $Date: Wed Dec 13 18:25:13 EST 2000 $
$Source: cmd/mksf/hpux_rel.c, hpuxcmdfs, vvos_rose,
rose0121 $ $Date: 00/12/13 13:55:57 $ $Revis
ion: 1.4 PATCH_11.04 (PHCO_22931) $
$ PATCH/11.00:PHCO_20765 Jan 6 2000 15:29:16 $
/sbin/lssf:
$Revision: Hewlett-Packard ISSL Level vvos_rose42 $
$Header: Hewlett-Packard ISSL Release vvos_r
ose $ $Date: Wed Dec 13 18:25:13 EST 2000 $
$Source: cmd/mksf/hpux_rel.c, hpuxcmdfs, vvos_rose,
rose0121 $ $Date: 00/12/13 13:55:57 $ $Revis
ion: 1.4 PATCH_11.04 (PHCO_22931) $
$ PATCH/11.00:PHCO_20765 Jan 6 2000 15:29:16 $
/sbin/mksf:
$Revision: Hewlett-Packard ISSL Level vvos_rose42 $
$Header: Hewlett-Packard ISSL Release vvos_r
ose $ $Date: Wed Dec 13 18:25:13 EST 2000 $
$Source: cmd/mksf/hpux_rel.c, hpuxcmdfs, vvos_rose,
rose0121 $ $Date: 00/12/13 13:55:57 $ $Revis
ion: 1.4 PATCH_11.04 (PHCO_22931) $
$ PATCH/11.00:PHCO_20765 Jan 6 2000 15:29:16 $
/sbin/rmsf:
$Revision: Hewlett-Packard ISSL Level vvos_rose42 $
$Header: Hewlett-Packard ISSL Release vvos_r
ose $ $Date: Wed Dec 13 18:25:13 EST 2000 $
$Source: cmd/mksf/hpux_rel.c, hpuxcmdfs, vvos_rose,
rose0121 $ $Date: 00/12/13 13:55:57 $ $Revis
ion: 1.4 PATCH_11.04 (PHCO_22931) $
$ PATCH/11.00:PHCO_20765 Jan 6 2000 15:29:16 $
/usr/sbin/insf:
$Revision: Hewlett-Packard ISSL Level vvos_rose42 $
$Header: Hewlett-Packard ISSL Release vvos_r
ose $ $Date: Wed Dec 13 18:25:13 EST 2000 $
$Source: cmd/mksf/hpux_rel.c, hpuxcmdfs, vvos_rose,
rose0121 $ $Date: 00/12/13 13:55:57 $ $Revis
ion: 1.4 PATCH_11.04 (PHCO_22931) $
$ PATCH/11.00:PHCO_20765 Jan 6 2000 15:29:16 $
/usr/sbin/lssf:
$Revision: Hewlett-Packard ISSL Level vvos_rose42 $
$Header: Hewlett-Packard ISSL Release vvos_r
ose $ $Date: Wed Dec 13 18:25:13 EST 2000 $
$Source: cmd/mksf/hpux_rel.c, hpuxcmdfs, vvos_rose,
rose0121 $ $Date: 00/12/13 13:55:57 $ $Revis
ion: 1.4 PATCH_11.04 (PHCO_22931) $
$ PATCH/11.00:PHCO_20765 Jan 6 2000 15:29:16 $
/usr/sbin/mksf:
$Revision: Hewlett-Packard ISSL Level vvos_rose42 $
$Header: Hewlett-Packard ISSL Release vvos_r
ose $ $Date: Wed Dec 13 18:25:13 EST 2000 $
$Source: cmd/mksf/hpux_rel.c, hpuxcmdfs, vvos_rose,
rose0121 $ $Date: 00/12/13 13:55:57 $ $Revis
ion: 1.4 PATCH_11.04 (PHCO_22931) $
$ PATCH/11.00:PHCO_20765 Jan 6 2000 15:29:16 $
/usr/sbin/rmsf:
$Revision: Hewlett-Packard ISSL Level vvos_rose42 $
$Header: Hewlett-Packard ISSL Release vvos_r
ose $ $Date: Wed Dec 13 18:25:13 EST 2000 $
$Source: cmd/mksf/hpux_rel.c, hpuxcmdfs, vvos_rose,
rose0121 $ $Date: 00/12/13 13:55:57 $ $Revis
ion: 1.4 PATCH_11.04 (PHCO_22931) $
$ PATCH/11.00:PHCO_20765 Jan 6 2000 15:29:16 $
OS-Core.CORE-ENG-A-MAN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,
v=HP:
/usr/share/man/man1m.Z/insf.1m:
None
/usr/share/man/man1m.Z/mksf.1m:
None
/usr/share/man/man1m.Z/rmsf.1m:
None
VirtualVaultOS.VVOS-AUX-IA,fr=B.11.04,
fa=HP-UX_B.11.04_32/64,v=HP:
/etc/auth/system/files.fcdb/05.patches/19126_PHCO.fcdb:
$Revision: Hewlett-Packard ISSL 1.1 etc/auth/system/
files.fcdb/05.patches/19126_PHCO.fcdb, files
_etc, vvos_rose, rose0069 $ $Date: 99/07/15
15:27:49 $
cksum(1) Output:
OS-Core.UX-CORE,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
189098700 581632 /sbin/insf
189098700 581632 /sbin/lssf
189098700 581632 /sbin/mksf
189098700 581632 /sbin/rmsf
189098700 581632 /usr/sbin/insf
189098700 581632 /usr/sbin/lssf
189098700 581632 /usr/sbin/mksf
189098700 581632 /usr/sbin/rmsf
OS-Core.CORE-ENG-A-MAN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,
v=HP:
586425355 12470 /usr/share/man/man1m.Z/insf.1m
1595632506 13957 /usr/share/man/man1m.Z/mksf.1m
1393769275 5350 /usr/share/man/man1m.Z/rmsf.1m
VirtualVaultOS.VVOS-AUX-IA,fr=B.11.04,
fa=HP-UX_B.11.04_32/64,v=HP:
27565422 375 /etc/auth/system/files.fcdb/05.patches/
19126_PHCO.fcdb
Patch Conflicts: None
Patch Dependencies:
s700: 11.04: PHKL_19142 PHNE_19127
s800: 11.04: PHKL_19142 PHNE_19127
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHCO_19126
Equivalent Patches:
PHCO_21596:
s700: 11.00
s800: 11.00
Patch Package Size: 650 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHCO_22931
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_22931.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_22931. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHCO_22931.depot
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHCO_22931.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHCO_22931.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_22931.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHCO_22931------------------------------------------
Document ID: PHSS_22683
Date Loaded: 20001227
Title: s700_800 11.X MC/ServiceGuard and SG-OPS Edition A.11.09
Patch Name: PHSS_22683
Patch Description: s700_800 11.X MC/ServiceGuard and SG-OPS Edition A.11.09
Creation Date: 00/11/06
Post Date: 00/12/27
Hardware Platforms - OS Releases:
s700: 11.00 11.11
s800: 11.00 11.11
Products:
MC/ServiceGuard A.11.09
ServiceGuard OPS Edition A.11.09
Filesets:
DLM.CM-DLM,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP
DLM.CM-DLM-CMDS,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP
DLM-NMAPI.CM-NMAPI,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP
DLM-Clust-Mon.CM-CORE,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP
Cluster-Monitor.CM-CORE,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP
DLM-Pkg-Mgr.CM-PKG,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP
Package-Manager.CM-PKG,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP
CM-Provider-MOF.CM-MOF,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP
CM-Provider-MOF.CM-PROVIDER,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP
ATS-CORE.ATS-RUN,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical:
No (superseded patches were critical)
PHSS_22540: OTHER
The cluster node may TOC when a corrupted
DLPI packet is received.
PHSS_21996: OTHER
During heavy network congestion, one of the cluster
nodes can get stuck in a "reforming" state.
Category Tags:
defect_repair general_release critical
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_22683
Symptoms:
PHSS_22683:
1. ContinentalClusters customers can corrupt their data if
they run or enable a package (cmrunpkg or cmmodpkg -e,
or the analogous SAM GUI operations) when a conflicting
package is already running. For example, the customer
may attempt to enable a recovery package when the primary
package is already running on the remote cluster, or when
the data receiver package is already running on the local
cluster. cmrunpkg, cmmodpkg, and the SAM GUI do not check
to determine if conflicting packages are running.
2. The MC/ServiceGuard command cmrunnode will hang while
an upgrading node is trying to join an existing cluster.
The command could result in freezing up the network and
thus prohibit clients to connect to the system. This
happens only on nodes undergoing an HP-UX migration from
11.0 to 11.11 and APA link aggregates were part of its
cluster configuration.
3. The lock disk warning not issued in syslog on one node
in the cluster. This happens on the node for which the
cluster lock volume group is activated.
4. Service Guard commands such as cmrunnode could hang when
a DLPI error occurs without actually reporting a DLPI
error had occurred. ( Infact the node should TOC when a
DLPI error occurs but it does not in some cases)
5. Cmsnmpd will return unchanged/incorrect cluster status
despite multiple changes in the cluster state. This
happens after halting and starting the cluster a
substantial number of times. The error message,
'Error: retrieving node status: -7', will be
reported in the cmsnmpd log, /var/adm/SGsnmpsuba.log.
6. On a non-coordinator node, cmsnmpd does not update the
hpmcSGPkgStatus mib value when the package switching
option is changed from enabled to disabled using
"cmmodpkg -d pkgname".
7. On SG-OPS clusters running cmgmsd, during high
transactions times, cmcld can use a large amount of
CPU. On single CPUs systems, this can cause cmcld
(a real time process) to take over the system,
preventing other processes from running.
PHSS_22540:
1. Directory permissions have been repaired and
functionality restored.
2. MC/ServiceGuard node TOCd when corrupted DLPI packet
is received.
PHSS_21996:
This patch is required if you are running on HP-UX 11.11.
1. Cmrunnode fails to join an existing cluster due to a
configuration operation in progress. A message is
printed in syslog on the running node: "cmcld: Detected
different configuration data on node <nodename>". If a
configuration operation is in progress (either
cmapplyconf or cmgmsd transaction) and a cmrunnode
occurs on another node, it may hit a window where the
configuration version will get out of sync. In this case
the joining node will not be allowed into the cluster
but it will take some time for the cmcld to time out.
This defect can also be seen by the SG-OPS customers.
2. During extremely high memory & I/O loads on a system,
if a configuration transaction is begun (either by
cmgmsd or cmapplyconf) the cmcld may abort with the
message, "Aborting! This node did not reply to a CDB
request message". This defect can also be seen by the
SG-OPS customers.
3. Attempting to use a non-standard disk device name
for a cluster lock PV will fail. For example, take
VG vglock which contains disk /dev/dsk/c0lun0.
Attempting to use /dev/dsk/c0lun0 as either the
primary or secondary cluster lock PV will fail.
The cmapplyconf command will fail with:
"Error: Unable to determine a unique identifier for
physical volume /dev/dsk/c0lun0 on node <nodename>.....
When attempting to use a non-standard disk name....".
4. DLPI checksum messages can occur frequently and do not
provide enough detail.
5. During extremely high memory & I/O load on a system
while the cluster is reforming, a node may go down i.e.
TOC. This is because SG daemon could not get a socket
for communicating with other nodes. The socket call
returns error "Resource temporarily unavailable." This
message may or may not make it to
/var/adm/syslog/syslog.log before the system goes down.
6. Config daemon was not ignoring the DLPI interface that
has no connection
7. Sometimes if a configuration change is being committed
(either by cmgmsd or cmapplyconf) and something prevents
the cmclconfd from responding to cmcld (could be high
CPU consumption) the cmcld may abort with the message,
"Aborting! This node did not reply to a CDB request
message". This defect can also be seen by the SG-OPS
customers.
8. On SG OPS clusters where cmgmsd is generating a lot of
transactions, syslog can be filled up with the following
message:
"This online configuration request %s has failed - "
"another transaction is already in progress.\n"
9. During a cmrunnode, if another node in the cluster
fails, there is a very small timing window which
could prevent the cluster from reforming and all
nodes will TOC with the message "Cluster Formation
Failed" appearing in syslog. This can only occur
on clusters of 3 or greater nodes.
10.ServiceGuard external logging daemon, cmlogd, exits too
early when a node is halted. This prevents some log
messages from being written to the syslog file.
11.The cmmodnet command fails to add or remove package IP
address(es) with error, "cmmodnet : Unable to complete
command : Interrupted system call"
12.The following message is sometimes printed during lan
failover. It should not be printed at the default log
level: "cmcld: DLPI ack error for primitive 52, errno 4,
unix errno 16".
13.Cluster did not reform on reboot.
14.SG Daemon "cmcld" aborts when attempting to log an error
causing node to TOC.
15.Node does not rejoin the cluster after reboot when
AUTO_STARTCMD is set. The following messages are in
/var/adm/syslog/syslog.log:
cmcld: Timedout waiting for LVM daemon
cmcld: Daemon exiting to preserve data integrity
cmcld: Reason: LVM daemon did not start
16. When using ServiceGuard OPS Edition version A.11.09
with patch PHSS_21107 and OPS 7.3.3.4, new file
/tmp/udlm_shmem_addr_file.txt is unnecessarily
created.
For HPUX, this file is meaningless, but is causing
customers to wonder if it is a cause for concern.
17. A node may fail to automatically join the cluster
if multiple nodes are rebooting at the same time.
18. Simultaneous configuration operations, started from two
or more nodes within a cluster that share the same
machine ID, can potentially cause one of the nodes to
TOC with an assertion failure. This issue affects
Superdome partitions and some L-Class systems that
were manufactured with identical machine ID's.
19. During an online replacement operation of a LAN card,
ServiceGuard may recover the replaced card incorrectly
while its link is not fully UP and the driver is still
resetting.
20. If a user inadvertently kills the cmlvmd process, the
node will either reboot or TOC.
21. When system updated with HP-UX 11.11 Mission Critical
Operating Environment (MCOE) media, the ServiceGuard
binary configuration file convert utility may fail to
execute successfully. (/var/adm/sw/swagent.log shows
"Network is unreachable" error.)
22. In a two node cluster, due to heavy network
congestion, it was possible for one of the nodes
to get stuck in a "reforming" state. Once in this
state, cmcld would periodically write the message:
"Attempting to form a new cluster" in the syslog
file and cmviewcl would always show the cluster
state as "reforming".
PHSS_21866:
1. A package takeover will fail if the mountpoint is busy,
even if the FS_MOUNT_RETRY_COUNT is set to >0 in
the package control script.
2. The cmhaltnode command repeatedly fails with the message:
"Unable to halt cluster services at this time." This can
occurred if a lan failover has occurred on the node being
halted.
3. Second dual cluster lock not tried if first dual cluster
lock fails, leading to a cluster TOC. This problem only
impact customer using Dual Cluster Locks.
4. Virtual file descriptor leak.
5. Cmcld TOCs with a SIGSEGV leading to a cmcld core in
/var/adm/cmcluster with a stack trace in dlpi_recv or
ns_if_setgood(). The cmcld is not resistant against
corrupted DLPI frames.
6. ServiceGuard cluster daemon(cmcld) aborts with error
messages: "Interrupted system call. This may be caused
by a very high system load." followed by "Aborting!
Failed to send over DLPI"
7. DLPI errors returned from disconnected interface cards
during
configuration stage.
PHSS_21425:
1. If cmcld experiences unexpected interrupted system calls,
it could hit assertion core "Assertion failed: inp->state
== CL_NODE_ADDING"
2. ServiceGuard config commands(cmcheckconf, cmapplyconf)
consistently fail to configure a cluster with error
"Non-uniform connections detected". The problem is more
likely to occur on large cluster configurations or when
the network traffic is very busy.
3. ServiceGuard daemon(cmcld) generates a core dump upon
receiving a message from an unconfigured token ring
interface whose DLSAP address size is larger then 20
bytes.
4. ServiceGuard command cmhaltcl fails to halt all nodes
with the combination of a high value of HB_INTERVAL and
NODE_TIMEOUT.
PHSS_21107:
1. When using OPS 8.0.5 or 8.0.6 with ServiceGuard OPS
Edition, in certain instances the ogms daemon can
abort which will cause the node to TOC.
2. When using OPS 7.3.4 with ServiceGuard OPS Edition,
users were unable to define the shared memory attach
address for udlm clients.
3. When using OPS 7.3.4 with ServiceGuard OPS Edition
in a 2-node cluster, shutting down one instance and
its node can cause a hang at the "alter database open"
when the node and instance are restarted.
4. If you have patch PHSS_20872 installed and you attempt
to swremove the ServiceGuard or ServiceGuard OPS Edition
product while the cluster is up on any of the nodes, the
swremove will report that it failed, but some filesets
will be removed. As a result, ServiceGuard commands
on the node where the swremove was done will no longer
work. However, the commands will still function on the
other nodes.
PHSS_20872:
1. If NODE_TIMEOUT exceeds 30 seconds, cmhaltcl command
fails to halt the last node with an error message:
cmhaltcl : Unable to connect to daemon
2. If an swremove of ServiceGuard is attempted while the
cluster is up, the cluster is halted and the config
file (cmclconfig) is nulled out.
3. Users were unable to define the shared memory attach
address for udlm clients.
4. In 2-node clusters, shutting down one instance and its
node can cause a hang at the "alter database open" when
the node and instance are restarted.
5. When user specifies -T 6 they should get DEBUG level
logging. The problem is that when the user does a
cmquerycl -v -n sweetee -T 6 or cmcheckconf,
cmapplyconf, they will not get logging at the DEBUG
level.
6. Package control script will fail during startup of
a package, if the mount point used by the package is
busy. The package startup will fail. This has been
the intended behavior.
7. Misleading error messages if service names has '/'s in
it. Error: The cmapplyconf command will return the
following message: Unable to apply the configuration
change due to an invalid request. In addition cmcld
TOC's all nodes in cluster when online apply with
PKGNAME has '/' in it. If the cluster is offline, the
cmapplyconf will succeeds. But the subsequent cmruncl
will fail.
8. ServiceGuard commands fail to configure or re-configure
the clusters if X.25 is installed on any nodes.
9. cmhaltcl showed the cluster was successfully halted,
but cmviewcl found the cluster is still up and running.
10.Two node ServiceGuard cluster configured with dual
cluster lock fails to reform when one of the nodes
fails. Specifically, node A fails and node B is
unable to reform a one node cluster because the
cluster lock is found to be held by the failed node.
PHSS_20230:
This patch is required if you have:
- MC/ServiceGuard A.11.09 and need to use the Continental
Cluster product.
- MC/ServiceGuard A.11.09 and experiencing any of the
following symptoms.
- ServiceGuard OPS Edition A.11.09 and experiencing any
of the following symptoms.
This patch fixes the following symptoms found in either
MC/ServiceGuard and ServiceGuard OPS Edition A.11.09
(or earlier).
1. The entire ServiceGuard cluster TOCd when a local
switch occurred in a heartbeat subnet.
2. Node TOCd during a configuration operation with
either the message "Timed Out Waiting For Replies" or
"A process participating in a configuration operation
no longer exists".
3. The configuration commands, cmcheckconf and cmapplyconf
failed with the message "Device not found on any node".
4. All nodes TOCd on an Oracle Parallel Server 8.1.5
cluster.
5. Misleading message was logged in the syslog.log for
DVD-ROM device.
6. Recently released tape library robotic (autochanger)
devices not recognized by MC/ServiceGuard shared
tape facility.
Defect Description:
PHSS_22683:
1. MC/ServiceGuard is not aware of ContinentalClusters, so
it cannot prevent users from starting the wrong package.
Resolution: ContinentalClusters configurations will be
checked when starting or enabling a package.
2. The MC/ServiceGuard command cmrunnode is not aware of
the fact that the ppa values of existing APA link
aggregates have been changed from "1xx" to "9xx" after
system upgraded to HP-UX 11.11. This results in hanging
the command indefinitely because it continues to use
the old ppa values, which are stored in the cluster
binary configuration file.
Resolution: The binary conversion utility, which gets
run during post-installation of the patch, has been
modified to perform the appropriate LAN conversion
prior to running any commands.
3. When the volume group is activated on a node the open
for the cluster lock device (which is powered down or
failed) succeeds. But the health check will show a
problem later when querying the device.
Resolution: Modified cluster initialization to start
lock health check imediately after open of cluster lock
disk. Also modified cmruncl warning to tell system
administrator to check syslog on all nodes in cluster.
4. Some of the DLPI errors,especially the ones which are
not caused by unix system errors(for eg: DL_ATTACH_REQ
failing because of trying to attach an incorrect value
of PPA to a stream), were not being reported as errors
thus causing incorrect behavior of
some commands.
Resolution: Modified the error value being returned so
that all DLPI errors are reported as errors irrespective
of whether they are caused by unix system errors.
5. A file descriptor leak was detected that eventually
utilized all of the systems available file descriptors.
When cmsnmpd is no longer allowed to open any more file
descriptors, it's unable to retrieve and/or report the
current correct cluster status.
Resolution: An extra file desciptor close call was added.
6. The package switching bit in the hpmcSGPkgStatus mib
variable is never cleared when the Package Switching
option is changed from enabled to disabled. Without
the fix, cmsnmpd only updated this mib variable when
the Package Switching option was changed from disabled
to enabled.
Resolution: This was corrected by adding code to clear
the package switching bit in the hpmcSGPkgStatus mib
variable when the Package Switching option is changed
to disabled.
7. The machine hang problem is caused by cmgmsd retrying
begin_trans without any delay if begin_trans reports
another cdb transaction is in progress. The excessive
begin_trans request could in term caused cmcld to take
up a significant cpu cycles to response to those
requests. In a single-cpu L class machine, TOP reports
cmcld could 40% of the cpu time and cmgmsd could use
another 20% of the cpu. Since both processes are running
as higher-priority process than regular processes like
telnetd, this generates a starvation problem.
Resolution: The change is to slow down the
rate of cmgmsd retrying begin_trans.
PHSS_22540:
1. Directory permissions have been repaired throughout
the product.
2. MC/ServiceGuard tries to recover and log messages
including sender's node id when corrupted DLPI packet
is received. MC/ServiceGuard node TOCd while logging if
sender's node id is corrupted in DLPI packet.
Resolution: Algorithm is added to check validity of
sender's node id.
PHSS_21996:
1. There was a window between the time that the cmrunnode
command checked the configuration version and the time
that the cmcld was started where another configuration
operation (most likely from cmgmsd) could sneak in. When
the cmcld started with the old configuration version and
asked the coordinator to be let into the cluster, the
coordinator would not let the joining node in. The
joining node would keep trying until its autostart time-
out was up. In the meantime, the cmrunnode command was
kept waiting.
Resolution: Use configuration transaction during startup.
2. As part of beginning a transaction when the cluster is
online, each cmcld will send a message to their configd
requesting that it lock a file on behalf of them. This
was used to sync up with any cmrunnode commands that
might be going on at the same time. Under normal use,
the config lock request will return immediately with
either success or failure depending on whether the lock
was acquired. However, if the system is overloaded for
an extended period of time with I/O or the open of the
lock file hangs for some reason, a CDB message timer pops
and the node that did not respond to the begin request
will be killed.
Resolution: Remove unneeded cmcld-to-cmclconfd request.
3. Internally SG will traverse the device tree and then
build device names based on these device ids. SG would
then check the cluster lock disk PV string to these
device names it built. Since the names it built would
not actually be real device names the check would fail.
Resolution: Use the routine hpux library routine
ftw() to build the device tree using the actual device
names on the system. We then use these names to compare
againest that is in the cluster ascii file.
4. Attempting to understand the cause -
The messages encountered should reduce the possibilities.
Resolution:
Added hardware information to an existing message.
Added another data verification to reduce the window
of possible causes.
5. When ServiceGuard daemon 'cmcld' is attempting to
establish a heart beat connection a socket call returns
an error EAGAIN. This error causes cmcld to abort.
Resolution: SG daemon cmcld will retry socket calls when
following errors EAGAIN, ENOBUFS, and ENOSR
are returned.
6. If a source interface is not physically connected,
then the config daemon should ignore it. In dual
ported and quad-ported hardware, often one or more
ports will not be used. However config daemon
was not ignoring this cases and was logging it as
an error at a severity of level zero.
Resolution : Increased the log level for this kind of
thing to level three, so that this doesn't showup as
an error with severity level zero.
7. During the commit phase of the configuration transaction
the transaction thread was getting blocked waiting for
a message back from the cmclconfd.
Resolution: Spawn thread to manage communication with
the cmclconfd.
8. The logging message has always been at level 0.
We needed to find a way to get the collision message
back to the commands before we could raise it.
Resolution: Raise level of log message and change config
clients to interpret busy error return.
9. During the quiescence period of the cluster formation
for the new node joining, the new node is counted in the
last number of active nodes. When the existing nodes
dies, we go back to reform. We have to get quorum of
the last number of active nodes. But we only accept
votes from old members that were in the last incarnation.
So, our last number of active nodes is too high.
Resolution: Set a flag to indicate when the last number
of active nodes includes nodes that aren't allowed to
vote and interpret this flag when calculating quorum.
10.When a node is halted, cmcld shutdowns the cmlogd in
order to complete the service gracefully. This is
done with the attempt that any last minute messages will
be sending directly to syslog. However, there are a few
important networking log messages that have already been
sent to cmlogd and waiting to be written to syslog.
Therefore, upon exiting cmlogd service, these messages
will never make to syslog at all.
Resolution: The cmlogd daemon will not be shutdown when
a node is halted. Instead, it will die on itself
gracefully when it detects that cmcld has already exited.
11.The cmmodnet command fails because one of the socket
ioctls, which are called to add or remove IP address,
returns an EINTR(Interrupted system call) error code.
Although this is a transient error, ServiceGuard doesn't
retry the ioctl. Thus the command exits out with such
error.
Resolution: A retry mechanism has been implemented to
allow the cmmodnet command to call such ioctls repeatedly
when EINTR is returned.
12.Although lan failover works correctly, while it is
occurring, there is a window where DLPI returns
errors during driver reset. This produces error
messages customers could see in syslog.
Resolution: Log level was changed so error messages will
not appear in syslog anymore.
13.The inetd daemon has not completed initialization when
SG start script is executed. Therefore, inetd does not
start cmclconfd which starts the cluster.
Resolution: Modify script cmcluster.init to retry
cmrunnode -v.
14.The function cl_strerror aborts when attempting to print
a negative error number.
Resolution: Modify cl_strerror to print negative errors
as negative numbers.
15.The SG daemon aborts because cmlvmd does not start in
time, but cmlvmd stays up.
Resolution: Close timing window when starting lvm daemon.
16. The creation of this new file was introduced by a fix
included in PHSS_21107. For HPUX, this file is
meaningless and should not be created.
Resolution: This file will no longer be created.
17. A prior fix to the cmrunnode command involved adding
additional locking to the node startup process. This
locking effectively prevents two simultaneous
cmrunnode invocations from both succeeding.
Resolution: A retry mechanism was added to the system
startup script /sbin/init.d/cmcluster
18. When an online ServiceGuard node initiates a
configuration operation, it first generates a
transaction ID that will be used by all nodes to
identify this operation. This transaction ID must be
unique within the cluster. One component of the
transaction ID, used to make it node specific, is the
machine ID number as returned by uname(2). Within a
Superdome cabinet, all partitions return the same
machine ID and thus transaction ID's were not unique.
Resolution: The algorithm used to generate transaction
ID's has been changed such that it no longer relies on
the on the machine ID to make it unique.
19. New PCI LAN drivers, which support online I/O operation,
will reset the card's MIB statistics to zero during an
online replacement. This behavior creates a logic
problem for the ServiceGuard's network manager so that
it could declare a faulty recovery of the replaced card
when the link is not fully recovered.
Resolution: The algorithm used to determine the recovery
of a failed LAN card has been modified to support new
driver behavior.
20. For a variety of reasons, system administrators will
sometimes need to kill system processes. The cmlvmd
process was not masking the signals commonly used
for this purpose. Thus if an administrator mistakenly
sent a kill signal to cmlvmd, it would terminate. This
in turn would cause cmcld to either reboot or TOC the
system.
Resolution: Added additional signal handling to
cmlvmd.
21. The HP-UX 11.11 MCOE ServiceGuard binary file conversion
problem is due to the convert utility executing before
the operating system is fully functional.
Resolution: ServiceGuard configure script, which runs
the binary file conversion utility, is rerun by swconfig
when this patch is installed on the system.
22. There was a very small window in the cluster
reformation protocol that allowed a one node cluster
(with safety timer disabled) to attempt to begin
to re-form a two node cluster before re-enabling
the safety timer. If this was then followed by the
right combination of future failures, the single
node could get into a state where it was continually
attempting cluster reformations.
Resolution: The protocol has been modified such that
the safety timer must be enabled prior to allowing
cluster reformations to proceed.
PHSS_21866:
1. The function in the package control script that
frees up a busy mount point does not handle the
input parameters passed to it correctly in all cases.
The problem only occurs if:
1. there are mount options and
2. if the retry count is set to > 0 and
3. if the mount point is busy
Resolution: Account for the case that the mount
options (which are operated on as a single parameter
in the freeup_busy_mountpoint_and_mount_fs() function)
are passed correctly.
2. During the halt operation, the cmhaltnode command, locks
the configuration database to prevent changes while nodes
are halting. This locking is done by creating connections
to the configuration daemons on remote nodes and sending
messages requesting the lock to be held. During halts,
the cluster manager (cmcld) will always restore a node
to its original configuration. If a node had suffered
a NIC failure on its primary network and the
cluster manager had switched to a standby NIC then,
during halt, the primary IP would be switched back
to the failed NIC. This effectively causes a loss of
network connectivity to the node. If cmhaltnode had been
running on this node, it would lose connectivity to
the configuration daemons and be unable to unlock the
configuration database. This would result in the
configuration database being locked for two hours (the
default network keepalive timeout value).
Resolution: The locking algorithm has been changed to
only lock the local node if it is an active cluster
member (this is sufficient to prevent configuration
changes).
3. When dual cluster locks are configured, if the request to
acquire the first cluster lock fails, the cluster
membership
election is restarted -- if the request failed because
one or the other of the two lock disks is down, the
election will be restarted continuously until safety time
is exhausted, leading to a cluster TOC.
Resolution: changed dual cluster lock such that
1) if first dual lock fails at lock request, move on
and try second dual lock; 2) if first dual lock is
granted and second dual lock fails at lock request, SG
will assume cluster lock is granted and will move on
with cluster membership protocol.
4. KEPD file descriptor (console) is not closed potentially
may cause resource leak.
Resolution: close the file descriptor
5. DLPI Buffer is corrupted.
Resolution: Add checksum and size checks upon receipt.
Drop corrupted buffers after logging problem.
Add code to check the size of a message before sending.
6. ServiceGuard does not handle EINTR code properly when
putmsg() or getmsg() returns the error.
Resolution: Retry the system calls when EINTR error is
returned.
PHSS_21425:
1. The procedure that makes the connect() does not handle
the EINTR code properly.
Resolution: When the connect call returns EINTR, we will
retry.
2. There isn't any automatic retry mechanism available in
ServiceGuard's network probe area. Thus when several
network interfaces couldn't get probe messages from other
interfaces due to busy traffic, ServiceGuard config
commands prematurely determine the non-uniform network
connections between those interfaces.
Resolution: A retry mechanism has been implemented so
that missing probe messages will be re-transmitted until
they are received by their peers or until maximum number
of retries is reached.
3. A buffer designed to store the ASCII representation of
the unconfigured DLSAP address was not allocated long
enough. Thus causes the stack corruption problem.
Resolution: The buffer size has been increased to hold
the largest DLSAP address of any interface type.
4. The cmhaltcl fails to stick around long enough to halt
the last node in the cluster.
Resolution: To use the election timeout instead of the
node timeout to determine how long to wait for the
cluster to reform after halting each node during
cmhaltcl.
PHSS_21107:
1. Under certain conditions, the ogms daemon can abort
which causes the node to TOC. A special version of
ogms is available from Oracle that will not abort.
Contact Oracle and make reference to bug# 1107981 to
obtain this special version of ogms.
2. Users who so desired were unable to define the shared
memory attach address for udlm clients are now able
to do so with this change.
Resolution: Users have now been provided with a method
to specify the shared memory attach address.
3. In some cases, the instance and node that are still up,
do not recognize the shutdown of the other node. The
shadow process was waiting for the lamport clock status
to become normal, but DLM thought that its status was
already normal.
Resolution: A bug in the distributed clock that
improperly updated the clock value during DLM
reconfiguration has been fixed.
4. The checkremove script that was released with the
previous patch (PHSS_20872), does not work when it
is used to remove the SG or SG OPS product. It only
works for the removal of the patch, but not for an
entire product (ServiceGuard or ServiceGuard OPS
Edition).
Resolution: the checkremove script has been removed
from this patch. A new implementation will be added
at the next product release.
PHSS_20872:
1. With NODE_TIMEOUT >30 sec, cluster reformation takes
longer than 30 sec during the halt operation. The
command client code allowed the hard-coded 30 sec limit
for a cluster reformation. Any time it took over 30 sec
to reform, it failed with an above error message.
Resolution:
Replaced hard-coded 30 seconds limit with a variable
proportionate to the NODE_TIMEOUT.
2. The swremove scripts do not verify the state of the
cluster, and do a cmhaltcl -f followed by a
cmdeleteconf -f.
Resolution:
Added a new script that verifies the cluster
is down before proceeding with the swremove.
3. Users who so desired were unable to define the shared
memory attach address for udlm clients are now able to
do so with this change.
Resolution:
Users have been provided with a method to
specify the shared memory attach address.
4. In some cases, the instance and node that are still up,
do not recognize the shutdown of the other node. The
shadow process was waiting for the lamport clock status
to become normal, but DLM thought that its status was
already normal.
Resolution:
A bug in the distributed clock that incorrectly
updated the clock value during DLM reconfigurations
has been fixed.
5. When the logging interface was changed in 11.09, the
log_level parameter was no longer being passed into
cf_find_config().
Resolution:
Passed in log_level parameter. The fix has been merged
to 11.09 and 11.12 branch.
6. The package control script tries to mount all the
logical volumes specified in the control script in
their specified mount points while starting a
package. If any one of these mount points is busy,
the mount operation in the control script will fail,
the package will not startup.
Enhancement:
The package control script is enhanced to allow customer
to specify a retry count to retry the mount operation
if the mount fails. A new configuration variable,
FS_MOUNT_RETRY_COUNT is added to the package control
script, to optionally set the number of times the mount
operation will be retried. During each retry, fuser -k
will be used to remove any processes using the mount
point.
7. We didn't check the package name and service name up
front. Therefore when the name gets to be stored into
the CDB, the '/' is causing CDB problems.
Resolution:
Added code to validate the cluster name, package name
and service name up front.
8. Did not allocate enough buffer to store the MAC address
of X.25 interfaces, which is 20-byte long. This causes
the program stack to be inadvertently overwritten.
Resolution:
Increases the buffer size to efficiently store the MAC
address of any interfaces including X.25.
9. Did not traverse the whole linked list which contained
node information within the cluster if one linked list
element was taken off the linked list.
Resolution:
Remember the next element before take off the current
element from the linked list.
10.Previously, node which acquired cluster lock was unable
to execute clear lock on first lock device due to
continuously busy device status. Subsequent retries
prevented it from going on to clear the second lock
device.
Resolution:
If clear lock operation in dual lock configuration
encounters lock device busy status, a finite number of
retries is attempted, a "cluster lock facility" problem
message is logged.
PHSS_20230:
1. After a local switch, the ServiceGuard cluster
repeatedly fails to reform due to continuous and
unexpected broken TCP connections between the members
and the co-ordinator node. The safety time eventually
expires and thus causes the entire cluster to TOC.
Resolution:
Re-establish the connection, which has been disconnected
unexpectedly, if the victim node is in certain states.
2. Did not handle a timing window where the client doing
the configuration operation died after sending the
abort of the transaction to the cmcld.
Resolution:
Added code to manage the loss of a client process
better.
3. The inconsistency in the internal data structures
caused this failure.
Resolution:
Store and lookup the device name consistently
with the same data structure.
4. Parallel execution of the Oracle databases on the
cluster nodes lead to a cmcld daemon core followed by
the TOC on all the cluster nodes.
Resolution:
Changed the algorithm that generated the transaction
id. In the old way, it uses "clock ticks since last
reboot". It could generate the same id within the same
clock ticks. The new way is to use a counter in the
id. The counter is increased by 1 every time we
generate a new id.
5. The code didn't differentiate between a regular disk
and DVD-ROM disk.
Resolution:
The DVD-ROM will be skipped during device probing.
6. Tape library robotic (autochanger) not recognized
by MC/ServiceGuard Advanced Tape Services stquerycl
command.
Resolution:
Added C7200-8000 and A5617A identifiers to
MC/ServiceGuard Advanced Tape Services identification
file (/etc/cmcluster/sharedtape/ats_tapelibs).
SR:
8606106547 8606126610 8606106679 8606112176 8606129359
8606129766 8606141323 8606140372 8606143939 8606145227
8606140033 8606145229 8606139999 8606143005 8606145329
8606158792 8606155018 8606114259 8606155930 8606156893
8606156059 8606160283 8606109633 8606134787 8606159558
8606158175 8606157297 8606126975 8606156970 8606159559
8606159837 8606106319 8606165225 8606165889 8606166114
8606167337 8606167124 8606161913
Patch Files:
DLM.CM-DLM,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/dlm/lbin/cmlkmgrd
/opt/dlm/lib/libudlm.a
/opt/dlm/sbin/dlmstat
/usr/contrib/bin/dlmdump
DLM.CM-DLM-CMDS,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/dlm/sbin/dlmapplyconf
/opt/dlm/sbin/dlmcheckconf
/opt/dlm/sbin/dlmquery
DLM-NMAPI.CM-NMAPI,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/lbin/cmgmsd
DLM-Clust-Mon.CM-CORE,fr=A.11.09,fa=HP-UX_B.11.00_32/64,
v=HP:
Cluster-Monitor.CM-CORE,fr=A.11.09,fa=HP-UX_B.11.00_32/64,
v=HP:
/sbin/init.d/cmcluster
/usr/contrib/bin/cmsetlog
/usr/contrib/bin/cmsetsafety
/usr/lbin/cmclconfd
/usr/lbin/cmcld
/usr/lbin/cmlogd
/usr/lbin/cmlvmd
/usr/lbin/cmsnmpd
/usr/lbin/cmsrvassistd
/usr/lbin/cmui
/usr/sbin/cmapplyconf
/usr/sbin/cmcheckconf
/usr/sbin/cmdeleteconf
/usr/sbin/cmgetconf
/usr/sbin/cmhaltcl
/usr/sbin/cmhaltnode
/usr/sbin/cmquerycl
/usr/sbin/cmruncl
/usr/sbin/cmrunnode
/usr/sbin/cmviewcl
/usr/sbin/cmviewconf
/usr/sbin/convert
DLM-Pkg-Mgr.CM-PKG,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP:
Package-Manager.CM-PKG,fr=A.11.09,fa=HP-UX_B.11.00_32/64,
v=HP:
/usr/sbin/cmhaltpkg
/usr/sbin/cmhaltserv
/usr/sbin/cmmakepkg
/usr/sbin/cmmigrate
/usr/sbin/cmmodnet
/usr/sbin/cmmodpkg
/usr/sbin/cmrunpkg
/usr/sbin/cmrunserv
/usr/sbin/cmstartres
/usr/sbin/cmstopres
CM-Provider-MOF.CM-MOF,fr=A.11.09,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/cmom/mof/CMcluster.mof
/opt/cmom/mof/EMScore.mof
/opt/cmom/mof/SGcluster.mof
/opt/cmom/mof/SGpackage.mof
CM-Provider-MOF.CM-PROVIDER,fr=A.11.09,
fa=HP-UX_B.11.00_32/64,v=HP:
/opt/cmom/providers/cmprovider.omp
ATS-CORE.ATS-RUN,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP:
/etc/cmcluster/sharedtape/ats_tapelibs
what(1) Output:
DLM.CM-DLM,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/dlm/lbin/cmlkmgrd:
HP92453-02A.10.20 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
MC Lock Manager A.11.09 PHSS_22540 (lms.c)
$Revision: /main/st_odlm_tyurek_update_version/0 $
/opt/dlm/lib/libudlm.a:
MC Lock Manager A.11.09 PHSS_22540 (lms.c)
$Revision: /main/st_odlm_tyurek_update_version/0 $
/opt/dlm/sbin/dlmstat:
HP92453-02A.10.20 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
MC Lock Manager A.11.09 PHSS_22540 (lms.c)
$Revision: /main/st_odlm_tyurek_update_version/0 $
/usr/contrib/bin/dlmdump:
HP92453-02A.10.20 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
MC Lock Manager A.11.09 PHSS_22540 (lms.c)
$Revision: /main/st_odlm_tyurek_update_version/0 $
DLM.CM-DLM-CMDS,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/dlm/sbin/dlmapplyconf:
None
/opt/dlm/sbin/dlmcheckconf:
None
/opt/dlm/sbin/dlmquery:
None
DLM-NMAPI.CM-NMAPI,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/lbin/cmgmsd:
HP92453-02A.10.20 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
Build date: Thu Nov 9 10:40:36 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
DLM-Clust-Mon.CM-CORE,fr=A.11.09,fa=HP-UX_B.11.00_32/64,
v=HP:
/sbin/init.d/cmcluster:
$Revision: 82.2 $
/usr/contrib/bin/cmsetlog:
Build date: Thu Nov 9 10:29:53 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Commands
Command Cln
Command Srv
Config
Local Comm
Util
/usr/contrib/bin/cmsetsafety:
Build date: Thu Nov 9 10:29:53 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Commands
Command Cln
Command Srv
Config
Local Comm
Util
/usr/lbin/cmclconfd:
HP92453-02A.10.20 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
Build date: Thu Nov 9 10:23:27 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Config Daemon
Config
Command Cln
Command Srv
Local Comm
Util
Config DB
/usr/lbin/cmcld:
HP92453-02A.10.20 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
Build date: Thu Nov 9 10:28:19 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Daemon
Config DB
Cluster Monitor
Command Srv
CommunicationSrv
Config
Dlm
Local Comm
Network Sensor
Package Manager
Remote Comm
API
Service Sensor
Cluster LVM
Status DB
Sync
Util
/usr/lbin/cmlogd:
Build date: Thu Nov 9 10:28:19 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Log Daemon
Local Comm
Util
/usr/lbin/cmlvmd:
Build date: Thu Nov 9 10:20:16 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Cluster LVM
Local Comm
Util
/usr/lbin/cmsnmpd:
Build date: Mon Dec 4 15:53:49 PST 2000
Build id: ibld_sgops_a1109_patch_cmsnmpd
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
API
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
SNMPSUBAGENT
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
/usr/lbin/cmsrvassistd:
HP92453-02A.10.20 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
Build date: Thu Nov 9 10:18:59 PST 2000
Build id: ibld_sgops_a1109_patch
/usr/lbin/cmui:
HP92453-02A.10.20 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
GUI
Config
Command Cln
Command Utils
Local Comm
Util
/usr/sbin/cmapplyconf:
Build date: Thu Nov 9 10:29:53 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmcheckconf:
Build date: Thu Nov 9 10:29:53 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmdeleteconf:
Build date: Thu Nov 9 10:29:53 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmgetconf:
Build date: Thu Nov 9 10:29:53 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmhaltcl:
Build date: Thu Nov 9 10:29:53 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmhaltnode:
Build date: Thu Nov 9 10:29:53 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmquerycl:
Build date: Thu Nov 9 10:29:53 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmruncl:
Build date: Thu Nov 9 10:29:53 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmrunnode:
Build date: Thu Nov 9 10:29:53 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmviewcl:
Build date: Thu Nov 9 10:29:53 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmviewconf:
Build date: Thu Nov 9 10:35:36 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Tools
/usr/sbin/convert:
Build date: Thu Nov 9 10:35:36 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Tools
DLM-Pkg-Mgr.CM-PKG,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/sbin/cmhaltpkg:
Build date: Thu Nov 9 10:29:53 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmhaltserv:
Build date: Thu Nov 9 10:29:53 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmmakepkg:
Build date: Thu Nov 9 10:29:53 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmmigrate:
Build date: Thu Nov 9 10:29:53 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmmodnet:
Build date: Thu Nov 9 10:29:53 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmmodpkg:
Build date: Thu Nov 9 10:29:53 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmrunpkg:
Build date: Thu Nov 9 10:29:53 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmrunserv:
Build date: Thu Nov 9 10:29:53 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmstartres:
Build date: Thu Nov 9 10:29:53 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmstopres:
Build date: Thu Nov 9 10:29:53 PST 2000
Build id: ibld_sgops_a1109_patch
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
CM-Provider-MOF.CM-MOF,fr=A.11.09,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/cmom/mof/CMcluster.mof:
ServiceGuard A.11.09 Date: 12/06/1999 PATCH: PHSS_
20230
/opt/cmom/mof/EMScore.mof:
ServiceGuard A.11.09 Date: 12/06/1999 PATCH: PHSS_
20230
/opt/cmom/mof/SGcluster.mof:
ServiceGuard A.11.09 Date: 12/06/1999 PATCH: PHSS_
20230
/opt/cmom/mof/SGpackage.mof:
ServiceGuard A.11.09 Date: 12/06/1999 PATCH: PHSS_
20230
CM-Provider-MOF.CM-PROVIDER,fr=A.11.09,
fa=HP-UX_B.11.00_32/64,v=HP:
/opt/cmom/providers/cmprovider.omp:
Command Utils
Command Cln
Config DB
Config
API
MC/ServiceGuard Product $Revision: 82.2 $
Cluster Monitor Product Only $Revision: 82.2 $
Cluster Monitor Product $Revision: 82.2 $
A.11.09 Date: 11/06/2000; PATCH: PHSS_22683
Cluster Management Provider Library
Build date: Thu Nov 9 10:46:47 PST 2000
Build id: ibld_sgops_a1109_patch
ATS-CORE.ATS-RUN,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP:
/etc/cmcluster/sharedtape/ats_tapelibs:
Advanced Tape Services A.11.09 PHSS_20230
cksum(1) Output:
DLM.CM-DLM,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP:
638147772 1983176 /opt/dlm/lbin/cmlkmgrd
230652225 3293720 /opt/dlm/lib/libudlm.a
2173965052 1153664 /opt/dlm/sbin/dlmstat
1628774046 1218896 /usr/contrib/bin/dlmdump
DLM.CM-DLM-CMDS,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP:
2157256463 1519616 /opt/dlm/sbin/dlmapplyconf
2157256463 1519616 /opt/dlm/sbin/dlmcheckconf
2157256463 1519616 /opt/dlm/sbin/dlmquery
DLM-NMAPI.CM-NMAPI,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP:
3291296983 890576 /usr/lbin/cmgmsd
DLM-Clust-Mon.CM-CORE,fr=A.11.09,fa=HP-UX_B.11.00_32/64,
v=HP:
2834577398 4653 /sbin/init.d/cmcluster
4216669994 892928 /usr/contrib/bin/cmsetlog
4216669994 892928 /usr/contrib/bin/cmsetsafety
957008101 1246928 /usr/lbin/cmclconfd
3467981362 2307792 /usr/lbin/cmcld
597011245 135168 /usr/lbin/cmlogd
3341371177 249856 /usr/lbin/cmlvmd
3258423402 1761280 /usr/lbin/cmsnmpd
850783037 149200 /usr/lbin/cmsrvassistd
3403097436 2389712 /usr/lbin/cmui
150852739 1986560 /usr/sbin/cmapplyconf
150852739 1986560 /usr/sbin/cmcheckconf
150852739 1986560 /usr/sbin/cmdeleteconf
150852739 1986560 /usr/sbin/cmgetconf
150852739 1986560 /usr/sbin/cmhaltcl
150852739 1986560 /usr/sbin/cmhaltnode
150852739 1986560 /usr/sbin/cmquerycl
150852739 1986560 /usr/sbin/cmruncl
150852739 1986560 /usr/sbin/cmrunnode
150852739 1986560 /usr/sbin/cmviewcl
3445501177 1478656 /usr/sbin/cmviewconf
2464266229 1527808 /usr/sbin/convert
DLM-Pkg-Mgr.CM-PKG,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP:
150852739 1986560 /usr/sbin/cmhaltpkg
150852739 1986560 /usr/sbin/cmhaltserv
150852739 1986560 /usr/sbin/cmmakepkg
150852739 1986560 /usr/sbin/cmmigrate
150852739 1986560 /usr/sbin/cmmodnet
150852739 1986560 /usr/sbin/cmmodpkg
150852739 1986560 /usr/sbin/cmrunpkg
150852739 1986560 /usr/sbin/cmrunserv
150852739 1986560 /usr/sbin/cmstartres
150852739 1986560 /usr/sbin/cmstopres
CM-Provider-MOF.CM-MOF,fr=A.11.09,fa=HP-UX_B.11.00_32/64,
v=HP:
3282458452 14942 /opt/cmom/mof/CMcluster.mof
1354007112 323 /opt/cmom/mof/EMScore.mof
3485431659 8033 /opt/cmom/mof/SGcluster.mof
2019823577 10303 /opt/cmom/mof/SGpackage.mof
CM-Provider-MOF.CM-PROVIDER,fr=A.11.09,
fa=HP-UX_B.11.00_32/64,v=HP:
3760512314 2379776 /opt/cmom/providers/cmprovider.omp
ATS-CORE.ATS-RUN,fr=A.11.09,fa=HP-UX_B.11.00_32/64,v=HP:
1344553928 606 /etc/cmcluster/sharedtape/ats_tapelibs
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_22540 PHSS_21996 PHSS_21866 PHSS_20230 PHSS_20872 PHSS_21107
PHSS_21425
Equivalent Patches: None
Patch Package Size: 31930 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_22683
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_22683.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_22683. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHSS_22683.depot
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_22683.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_22683.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_22683.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
For ServiceGuard OPS Edition Clusters using OPS 8.0.5
or 8.0.6, do the following:
1) Halt the cluster.
2) Install this patch on all nodes.
3) On all nodes, add this new line to the Oracle
initialization file (usually named init.ora) as
follows:
ogms_home=/var/opt/ogms
4) Start the cluster and OPS.
5) For the install, the ServiceGuard snmp subagent was
stopped and not automatically restarted. This
subagent is primarily used with the ClusterView
product. If this applies to you, then restart it
manually by executing the following command:
/usr/lbin/cmsnmpd
For ServiceGuard OPS Edition Clusters using OPS 7.3.4, or
ServiceGuard OPS Edition Clusters using OPS 8.1.5 or higher
do the following:
1) Halt the cluster.
2) Install this patch on all nodes.
3) Relink Oracle applications on all nodes.
4) Start the cluster and OPS.
5) For the install, the ServiceGuard snmp subagent was
stopped and not automatically restarted. This
subagent is primarily used with the ClusterView
product. If this applies to you, then restart it
manually by executing the following command:
/usr/lbin/cmsnmpd
For MC/ServiceGuard Clusters, do the following:
1) Halt ServiceGuard on the node the patch is to be
installed on.
2) Install this patch on that node.
3) Restart ServiceGuard on that node.
4) Patch needs to be installed on all nodes in the
cluster
5) For the install, the ServiceGuard snmp subagent was
stopped and not automatically restarted. This
subagent is primarily used with the ClusterView
product. If this applies to you, then restart it
manually by executing the following command:
/usr/lbin/cmsnmpd
-----End of Document ID: PHSS_22683------------------------------------------
Document ID: PHKL_22792
Date Loaded: 20001227
Title: s700_800 11.00 Fix VM page read-ahead panics
Patch Name: PHKL_22792
Patch Description: s700_800 11.00 Fix VM page read-ahead panics
Creation Date: 00/12/01
Post Date: 00/12/27
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products: N/A
Filesets:
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_22792: PANIC
PHKL_21511: PANIC CORRUPTION
Category Tags:
defect_repair general_release critical panic corruption
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_22792
Symptoms:
PHKL_22792:
( SR: 8606147554 CR: JAGad16896 )
Customer will see a data-page-fault panic in pdprotget().
A typical panic stack would look like:
panic+0x14
report_trap_or_int_and_panic+0x80
trap+0xdb8
nokgdb+0x8
pdprotget+0xa0
process_read_ahead_pages+0x1a8
hdl_pfault+0x6a0
pfault+0x104
copyin+0x170
uiomove+0xc0
rwip+0x398
ufs_rdwr+0x124
vno_rw+0x84
writev+0x17c
syscall+0x480
$syscallrtn+0x0
( SR: 8606170083 CR: JAGad39347 )
Customer will see a data-page-fault panic in pdprotget().
A typical panic stack would look like:
panic+0x14
assfail+0x3c
_assfail+0x2c
sl_pre_check+0x120
spinlock+0x18
vfault+0xd8
trap+0x10e4
nokgdb+0x8
pdprotget+0x224
process_read_ahead_pages+0x36c
hdl_vfault+0x518
vfault+0x2b8
trap+0x1370
nokgdb+0x8
copyin+0xbc
uiomove+0x4a4
rw3vp+0x7ec
nfs3_write+0x140
nfs3_rdwr+0x8c
vno_rw+0xa4
4_2fa4_cl_rwuio+0x298
write+0x78
syscall+0x5fc
$syscallrtn+0x0
( SR: 8606156441 CR: JAGad25776 )
pfd corruption -- manifests as data-page-fault in
pdv_modset2_0 or pdv_protaccset2_0.
A typical panic stack would look like:
panic+0x14
report_trap_or_int_and_panic+0x84
interrupt+0x1d4
$ihndlr_rtn+0x0
pdv_modset2_0+0x27c
pdmodset+0x14c
hdl_unsetbits+0x264
pageiocleanup+0x11c
pageiodone+0x2c
biodone+0x1f0
lv_complete+0xc0
lv_terminate+0xd4
lv_parwrite_done+0x148
lv_end+0x128
biodone+0x1f0
scsi_fast_cbfn+0x260
c720_isr+0x52c
sapic_interrupt+0x2c
up_ext_interrupt+0x2c8
ivti_patch_to_nop2+0x0
idle+0x1c4
swidle_exit+0x0
PHKL_21511:
( SR: 8606130257 CR: JAGac95128 )
System panics with a data page fault due to various reasons,
such as virtual address not mapped, allocation of page zero,
or using a page of size zero. In most cases, the system
is doing heavy I/O across NFS mounts.
A typical panic stack would look like:
panic+0x14
allocate_page+0x12c
allocpfd+0x24
vfdfill+0x58
vm_fill_in_pages+0x64
vm_prepare_io+0x28
nfs_pagein+0x20c
virtual_fault+0x1c4
vfault+0xf4
trap+0x714
Defect Description:
PHKL_22792:
( SR: 8606147554 CR: JAGad16896 )
process_read_ahead_pages() both in its forward and backward
loops, does not correctly check for the presence of
translation.
Resolution:
Check both for the existence of an address translation for
the physical page, and make sure it is translated to our
address.
( SR: 8606170083 CR: JAGad39347 )
Incorrect parameter passed to pdprotget() call.
Resolution:
Pass the updated virtual address instead of the starting
address again and again.
( SR: 8606156441 CR: JAGad25776 )
We were freeing the pfd at the granularity of the superpage
instead of the 4K sub-page.
Resolution:
Use freepfd_one() to release a single 4K sub-page, instead
of freepfd().
PHKL_21511:
( SR: 8606130257 CR: JAGac95128 )
For better performance, the user data access pattern is
tracked and read-ahead is implemented for sequential
I/O's. A defect in the read-ahead code decrements the
reference count of pages within a large page incorrectly.
This results in freeing still in-use pages and corrupting
the memory freelist. When invalid pages are returned to the
allocation routines, the system panics with data page fault.
Resolution:
Decrement reference count of large pages correctly.
SR:
8606130257 8606147554 8606156441 8606170083
Patch Files:
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
/usr/conf/lib/libhp-ux.a(vfs_vm.o)
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
/usr/conf/lib/libhp-ux.a(vfs_vm.o)
what(1) Output:
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
/usr/conf/lib/libhp-ux.a(vfs_vm.o):
vfs_vm.c $Date: 2000/11/20 22:58:36 $Revision: r11ro
s/9 PATCH_11.00 (PHKL_22792)
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
/usr/conf/lib/libhp-ux.a(vfs_vm.o):
vfs_vm.c $Date: 2000/11/20 22:58:36 $Revision: r11ro
s/9 PATCH_11.00 (PHKL_22792)
cksum(1) Output:
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
160183242 43032 /usr/conf/lib/libhp-ux.a(vfs_vm.o)
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
1530331189 94200 /usr/conf/lib/libhp-ux.a(vfs_vm.o)
Patch Conflicts: None
Patch Dependencies:
s700: 11.00: PHKL_18543
s800: 11.00: PHKL_18543
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHKL_21511
Equivalent Patches: None
Patch Package Size: 170 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHKL_22792
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_22792.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_22792. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHKL_22792.depot
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHKL_22792.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHKL_22792.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_22792.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
This patch depends on base patch PHKL_18543.
For successful installation please insure that PHKL_18543
is already installed, or that PHKL_18543 is included
in the same depot with this patch and PHKL_18543
is selected for installation.
-----End of Document ID: PHKL_22792------------------------------------------
Document ID: PHKL_22785
Date Loaded: 20001227
Title: s700_800 11.00 HPMC, FC reset & conn, chassis log, I20 RAID
Patch Name: PHKL_22785
Patch Description: s700_800 11.00 HPMC, FC reset & conn, chassis log, I20 RAID
Creation Date: 00/12/19
Post Date: 00/12/27
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products: N/A
Filesets:
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_22785: OTHER
HPMC on panic.
PHKL_22363: OTHER
Rebooting one or more hosts in an FC-AL
configuration may cause loss of access
to LUNS for other hosts on the loop.
PHKL_19752: HANG
Category Tags:
defect_repair enhancement general_release critical
halts_system
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_22785
Symptoms:
PHKL_22785:
( SR: 8606161973 DTS: JAGad31289 )
System HPMC's during a panic.
PHKL_22363:
( SR: 8606158594 DTS: JAGad27924 )
In a configuration involving multiple hosts attached to a
fibre channel private loop, if one or more of the hosts is
rebooted, the non-rebooting host(s) experience I/O
performance problems. Additionally, in some cases, if an
'ioscan' is executed on a non-rebooting host during the
reboot window, a status of "NO_HW" may be generated for
some of the devices on the fibre.
PHKL_21119:
( SR: 8606126623 DTS: JAGac59464 )
On N and L class machines, the run LED remains on during
a reset of the system, in preparation for reboot.
PHKL_20979:
( SR: 8606125655 DTS: JAGac42317 )
The chassis code log files show incorrect time stamps. They
show either March 06, 2106 or January 01, 1970 (instead of
the current date). These incorrect dates show up every four
hours, and last for approximately one hour.
The logs are accessible through two mechanisms. They are
maintained and available when the online diagnostics
subsystem is enabled and running (the cclogd daemon is
running on the system). The last 200 are also maintained on
the Guardian Service Processor (GSP), and accessible from
the system consol after typing [ctrl]-b.
The date errors are cosmetic only and do not impact the
operating system or applications. The date errors are
generated on the GSP, which is supported by L-Class and
N-Class systems only.
PHKL_20176:
( SR: 8606108529 DTS: JAGab16799 )
Wrong Chassis Codes (Cxxx) displayed during shutdown.
( SR: 8606103410 DTS: JAGab70129 )
I20 RAID Disks are not supported.
PHKL_19752:
( SR: 1653287672 DTS: JAGab12583 )
When soft-rebooting (reboot/shutdown -r) a node other
than a V-class without doing a hardware reset, connections
to all fiber channel devices will be lost, causing the whole
cluster to be unusable.
Defect Description:
PHKL_22785:
( SR: 8606161973 DTS: JAGad31289 )
Sometimes the OS sleeps inside of panic while it is
flushing dirty buffers to disk. Upon waking up, the
scheduler sets a flag which (incorrectly) indicates
that the OS is executing in a process context.
As a result of this mistake, the OS later tries to
write to a virtual address from real mode.
Resolution:
Reset the flag mentioned above to indicate that the
OS is not executing in a process context and avoid
the writing to a virtual address in real mode
(i.e. the code that would create an HPMC).
PHKL_22363:
( SR: 8606158594 DTS: JAGad27924 )
When you reboot a machine on a fibre channel loop, its FC
card may start sending garbage; this can cause severe
performance degradation that may result in the inability
to communicate with devices on the fibre. Although we do
not expect many customers to observe this defect, we
believe it is serious enough to create a patch for those
who believe they might encounter the problem.
PHKL_21119:
( SR: 8606126623 DTS: JAGac59464 )
Previously, the standard set by FES was that the run LED
should remain on during a reboot. FES has changed that
standard to state that the run LED should be turned off
just before the machine is reset.
Resolution:
Included code to turn the run LED off before resetting
the system.
PHKL_20979:
( SR: 8606125655 DTS: JAGac42317 )
At boot time and every four hours thereafter, the operating
system sends the GSP the current time to update the GSP's
clock. Every hour, the cclogd also sends the GSP the time.
The time value sent by the operating system includes a year
value of '0' for 2000, instead of 100, or years since 1900.
The GSP interprets the year as 1900, which is invalid. It
generates an error code -1, which gets interpreted in the
logs as the date March 06, 2106. The GSP then resets its
clock to January 01, 1970. This happens with every
operating system time update to the GSP.
The time value sent by cclogd to the GSP is correct. As
this is sent every hour, we see the erroneous values on log
entries generated starting with the operating system update
until the next cclogd update.
This defect impacts L-Class and N-Class only, is visable
only in the chassis code logs, and has no impact on the
operating system or any applications. The log files are
viewable through the online diagnostic subsystem.
Resolution:
Change the current rounding up procedure in the operating
system GSP update routine so that the year will be the
number of years since 1900, as the GSP expects.
PHKL_20176:
( SR: 8606108529 DTS: JAGab16799 )
Chassis codes were changed for N-class and broke legacy
systems. (Cxxx) codes showed instead of (Dxxx) codes.
Resolution:
Replace the classic Dxxx chassis codes and reduce the
alert level to Forward Progress for Dxxx codes.
( SR: 8606103410 DTS: JAGab70129 )
I20 RAID Disks are not supported.
Resolution:
I20 RAID requires some modification to the boot path.
PHKL_19752:
( SR: 1653287672 DTS: JAGab12583 )
Fiber channel interfaces did not get reset when soft-
rebooting a machine other than a V-class, causing all the
connected devices to be disconnected and inaccessible.
Resolution:
Add PDC_IO to reset fiber channel interfaces when rebooting
the kernel.
SR:
1653287672 8606103410 8606108529 8606125655 8606126623
8606158594 8606161973
Patch Files:
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
/usr/conf/lib/libhp-ux.a(chassis_log.o)
/usr/conf/lib/libhp-ux.a(machdep.o)
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
/usr/conf/lib/libhp-ux.a(chassis_log.o)
/usr/conf/lib/libhp-ux.a(machdep.o)
what(1) Output:
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
/usr/conf/lib/libhp-ux.a(chassis_log.o):
chassis_log.c $Date: 2000/09/08 11:43:00 $Revision:
r11ros/5 PATCH_11.00 (PHKL_22363)
/usr/conf/lib/libhp-ux.a(machdep.o):
machdep.c $Date: 2000/12/07 14:55:15 $Revision: r11r
os/16 PATCH_11.00 (PHKL_22785)
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
/usr/conf/lib/libhp-ux.a(chassis_log.o):
chassis_log.c $Date: 2000/09/08 11:43:00 $Revision:
r11ros/5 PATCH_11.00 (PHKL_22363)
/usr/conf/lib/libhp-ux.a(machdep.o):
machdep.c $Date: 2000/12/07 14:55:15 $Revision: r11r
os/16 PATCH_11.00 (PHKL_22785)
cksum(1) Output:
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
3582437691 7652 /usr/conf/lib/libhp-ux.a(chassis_log.o)
2081314360 28508 /usr/conf/lib/libhp-ux.a(machdep.o)
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
411903387 16176 /usr/conf/lib/libhp-ux.a(chassis_log.o)
2163978677 73800 /usr/conf/lib/libhp-ux.a(machdep.o)
Patch Conflicts: None
Patch Dependencies:
s700: 11.00: PHKL_18543
s800: 11.00: PHKL_18543
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHKL_22363 PHKL_21119 PHKL_20979 PHKL_20176 PHKL_19752
Equivalent Patches: None
Patch Package Size: 170 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHKL_22785
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_22785.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_22785. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHKL_22785.depot
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHKL_22785.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHKL_22785.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_22785.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
This patch depends on base patch PHKL_18543.
For successful installation please insure that PHKL_18543
is already installed, or that PHKL_18543 is included
in the same depot with this patch and PHKL_18543
is selected for installation.
-----End of Document ID: PHKL_22785------------------------------------------
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]