|
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 11.X patch digest
From: IT Resource Center (support_feedback
us-support2-mail.external.hp.com)
Date: Sun Mar 16 2003 - 12:16:50 CST
- 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 11.X patch digest
Created: Sun Mar 16 6:05:03 EST 2003
Table of Contents:
Document ID Title
--------------- -----------
PHSS_28624 s700_800 11.11 MetroCluster CA A.04.20 patch
PHSS_28421 s700_800 11.00 OV CVIEWS1.0 cumulative fixes
PHSS_28452 s700_800 11.X OV ITO7.1X Data Comm Component Linux A.07.12
PHSS_27722 s700_800 11.X MC/ServiceGuard and SG-OPS Edition A.11.13
PHKL_28513 s700_800 11.11 SCSI IO Cumulative Patch
PHCO_27977 s700_800 11.11 HP VxVM B.03.20.1/vxvmconvert Patch
PHCO_28623 s700_800 11.11 fsck_hfs(1M) cumulative patch
PHKL_27985 s700_800 11.11 HP VxVM B.03.20.1/VVR Patch
PHKL_28496 s700_800 11.00 SCSI IO Subsystem Cumulative Patch
PHSS_28776 s700_800 11.X OV EMANATE14.2 hp_unixagt filesystem fix
PHCO_28482 s700_800 11.00 tbl(1) cumulative patch
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHSS_28624
Date Loaded: 20030313
Title: s700_800 11.11 MetroCluster CA A.04.20 patch
Patch Name: PHSS_28624
Patch Description: s700_800 11.11 MetroCluster CA A.04.20 patch
Creation Date: 03/02/19
Post Date: 03/03/13
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products:
B8109BA MetroCluster CA A.04.20
Filesets:
SG-CA-Tool.CM-SGCA,fr=A.04.20,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical:
Yes
PHSS_28624: OTHER
Package is unable to start on any node in the
cluster.
Category Tags:
defect_repair general_release critical
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_28624
Symptoms:
PHSS_28624:
The following symptoms may be seen when the XP/CA device
group has more than 12 LUNs.
1. During package startup, the package will fail and log a
message stating that the fence level is in a MIXED state
even though the fence level for the device group is not
in a MIXED state.
2. During resynchronization from the SVOL, the package may
fail and log a message stating that "The copy of the
device group is stuck" even though the copy is not stuck.
Defect Description:
PHSS_28624:
1. The MetroCluster binary does not allocate enough memory
to store all of the output of the pairdisplay command
when the device group contains more than 12 devices.
The output is used to determine which fence level is
used and the copy percentage completed during
resynchronization. Since it does not allocate enough
memory for the output, it truncates the information
without telling the caller that the information is
incomplete. Therefore, the caller treats the truncated
output as valid output and incorrectly determines the
fence level and the copy percentage completed from this
truncated output.
2. The same reason as stated in item 1.
Enhancement:
No
SR:
8606295789
Patch Files:
SG-CA-Tool.CM-SGCA,fr=A.04.20,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/sbin/DRCheckXPCADevGrp
/usr/sbin/DRMonitorXPCADevGrp
what(1) Output:
SG-CA-Tool.CM-SGCA,fr=A.04.20,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/sbin/DRCheckXPCADevGrp:
HP aC++ B3910B A.03.25 Classic Iostream Library
HP aC++ B3910B A.03.25 Language Support Library
HP DRCM XPCA Technology -- A.04.20 PHSS_28624
HP Data Replication Integration Framework -- A.01.00
/usr/sbin/DRMonitorXPCADevGrp:
HP aC++ B3910B A.03.25 Classic Iostream Library
HP aC++ B3910B A.03.25 Language Support Library
DeviceGroup Monitor -- A.01.00 PHSS_28624
cksum(1) Output:
SG-CA-Tool.CM-SGCA,fr=A.04.20,fa=HP-UX_B.11.11_32/64,v=HP:
508755226 266240 /usr/sbin/DRCheckXPCADevGrp
1268793450 258048 /usr/sbin/DRMonitorXPCADevGrp
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches: None
Patch Package Size: 530 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_28624
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_28624.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_28624. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_28624.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_28624.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_28624.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHSS_28624------------------------------------------
Document ID: PHSS_28421
Date Loaded: 20030312
Title: s700_800 11.00 OV CVIEWS1.0 cumulative fixes
Patch Name: PHSS_28421
Patch Description: s700_800 11.00 OV CVIEWS1.0 cumulative fixes
Creation Date: 03/03/04
Post Date: 03/03/12
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products:
OpenView Customer Views 1.0
Filesets:
OVISP.OVISP,fr=B.01.00.00,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_28421
Symptoms:
PHSS_28421:
8606223855: Customer Views permanent license fails to be
picked up when Customer Views is installed with evaluation
license on multi-homed system. Extra tracing and logging
facilites are required to trace the reason in future.
8606196699: Customer Views needs a separate license for
each node of a Sun cluster.
8606219382: ovcustomer dies with SIGSEGV when
print_associated_node command is executed.
8606208484: Customer Views containers with autolayout off
show weird behaviour when ovw is reopened.
PHSS_24090:
All multi-homed objects (interface count greater than 1)
that are copied from ipmap to be displayed within submBld
are created by default with Object status source so that
when the status changes in ipmap, the corresponding object
in submBld will also get updated with the same status.
However this model is not consistent with ipmap in regards
to networks and multi-homed objects.
Multi-homed objects within ipmap are by default set with
Compound Propagated status source yet the submBld copied
multi-homed objects are set with Object status source.
Consequently the multi-homed objects in submBld are
inconsistent with ipmap. Note: if the user specifically
manages an unmanaged, previously discovered object the
status source in ipmap is set to Object status.
PHSS_23367:
Customer Views submBld does not appear to be updating the
status for Network symbols within the Sites-> <location> ->
LAN's containers. Consequently status is not propagated up
to the Sites container.
PHSS_22144:
When a new submap is created and opened from the OVW GUI,
keySys core dumps on Solaris, and submBld leaves orphaned
submaps behind.
PHSS_21488:
ovcustomer can dump core while running "ovcustomer
export_all_organizations_for_import" with lots of nodes
per organization
Defect Description:
PHSS_28421:
8606223855: The Customer Views licensing architecture does
not recognize the LOOPBACK and NNM_INTERFACE settings if
defined in the ov.conf file. This means that the Customer
Views licensing fails to pick proper license keys for a
multi-homed environment.
Resolution:
8606223855: Code has been modified to make Customer Views
licensing architecture to pick up license from
$OV_CONF/.license file which corresponds to NNM_INTERFACE
entry made in ov.conf.
8606196699: The Customer Views licensing architecture does
not recognize NNM_INTERFACE settings if defined in the
ov.conf file. This means that Customer Views licensing
architecture fails to pickup proper license keys for
Service Guard cluster/Sun cluster environment.
Resolution:
8606196699: Code has been modified to recognize floating
IP address on Sun cluster environment.
8606219382: ovcustomer was dying when a pointer variable
was dereferenced from the underlying NULL-valued pointer.
Resolution:
8606219382: Code is modified to handle the NULL valued
pointer before it gets dereferenced.
8606208484: Customer Views doesn't keep track of the
symbols which were in New Object Holding Area when ovw was
last closed. So it shows weird behavior when ovw is
reopened and new object are displayed to Customer Views
submaps with autolayout on.
Resolution:
8606208484: Customer Views has been modified to remove
Autolayout "off" option from its submaps.
PHSS_24090:
CV multi-homed (Computer & Connector) symbols need to be
set with Compound (Propagated) status source to better
match the status of the ipmap managed multi-homed symbols.
Resolution:
Add a special case to the CreateSymbol section of submBld
to check if the symbolType is Computer or Connector. Then
check if the interface count is greater than 1 (to
determine if the object is multi-homed) and if so, set the
status source to Compound Propagated otherwise the status
source will remain the default, Object status.
Note: This fix will only set the status to Compound
Propagated for all newly created multi-homed nodes. It
will not alter the status for any pre-existing symbols.
PHSS_23367:
CV network symbols need to have Compound (Propagated)
status source to better handle the status of ipmap managed
network symbols. Otherwise if the ipmap network symbol has
Compound status source, instead of Object, the submBld
created symbol will display Unknown status and the true
status can't propagate through the Site containers.
Resolution:
Add a special case to the CreateSymbol section of submBld
to check if the symbolType is Network then set the status
source to Compound else the status source is set to Object.
PHSS_22144:
keySys core dump problem was caused by the incorrect use of
the mapInfo pointer passed to keySys during a OVW map open
callback.
The submBld orphaned submaps problem is caused by the fact
that the submBld process maintains some global state after
closing and opening a new map. the prior state is
incorrectly applied to the new map, resulting in the
orphaned OVW submaps.
Resolution:
We now call OVwGetMapInfo() to obtain the true MapInfo
handle in keySys.
In submBld, we now clear all global state after closing and
opening a new map.
PHSS_21488:
ovcustomer was passing a small buffer to libovorg, and
libovorg was overrunning the end of the buffer.
Resolution:
changed libovorg, ovcustomer, etc., to use OVStrings to
pass text around.
Enhancement:
No
SR:
8606219382 8606196699 8606223855 8606208484 8606185133
8606179348 8606152678 8606128069
Patch Files:
OVISP.OVISP,fr=B.01.00.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/www/cgi-bin/Wfindorgs.exe
/opt/OV/www/cgi-bin/Wfindres.exe
/opt/OV/bin/submBld
/opt/OV/bin/keySys
/opt/OV/bin/ovcustomer
/opt/OV/bin/listorgs
/opt/OV/bin/findorgs
/opt/OV/bin/findres
/opt/OV/lib/libnnmspkey.3
/opt/OV/lib/libovorg.3
what(1) Output:
OVISP.OVISP,fr=B.01.00.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/www/cgi-bin/Wfindorgs.exe:
None
/opt/OV/www/cgi-bin/Wfindres.exe:
None
/opt/OV/bin/submBld:
ISP Submap Hierarchy Builder
HP OpenView Windows NNM Release B.06.10
PATCH PHSS_28421, 03042003
HP 9000 S700/S800 HP-UX 11.x
Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/keySys:
Key Systems
HP OpenView Windows NNM Release B.06.10
PATCH PHSS_28421, 03042003
HP 9000 S700/S800 HP-UX 11.x
Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/ovcustomer:
ovcustomer executable
HP OpenView Windows NNM Release B.06.10
PATCH PHSS_28421, 03042003
HP 9000 S700/S800 HP-UX 11.x
Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/listorgs:
listorgs
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_28421, 03042003
HP 9000 S700/S800 HP-UX 11.x
Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/findorgs:
findorgs
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_28421, 03042003
HP 9000 S700/S800 HP-UX 11.x
Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/findres:
findres
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_28421, 03042003
HP 9000 S700/S800 HP-UX 11.x
Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/lib/libnnmspkey.3:
HP OpenView Licensing NNM Release B.06.10
PATCH PHSS_28421, 03042003
HP 9000 S700/S800 HP-UX 11.x
Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/lib/libovorg.3:
ovorg
ovorg
cksum(1) Output:
OVISP.OVISP,fr=B.01.00.00,fa=HP-UX_B.11.00_32/64,v=HP:
1581585792 65752 /opt/OV/lib/libnnmspkey.3
1974155082 49368 /opt/OV/lib/libovorg.3
1397367557 190896 /opt/OV/bin/submBld
960581865 117360 /opt/OV/bin/keySys
892437364 156310 /opt/OV/bin/ovcustomer
745468743 57617 /opt/OV/bin/listorgs
3325004731 65840 /opt/OV/bin/findorgs
3217189640 65831 /opt/OV/bin/findres
3544585336 32889 /opt/OV/www/cgi-bin/Wfindorgs.exe
1817769833 32889 /opt/OV/www/cgi-bin/Wfindres.exe
Patch Conflicts: None
Patch Dependencies:
s700: 11.00: PHSS_24798
s800: 11.00: PHSS_24798
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_24090 PHSS_23367 PHSS_22144 PHSS_21488
Equivalent Patches:
PHSS_28420:
s700: 10.20
s800: 10.20
CVIEWS_00016:
sparcSOL: 2.5 2.6 2.7 2.8
CVIEWS_00015:
intelNT: 4.00 4.01
intelWIN2000: 1.00
Patch Package Size: 870 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_28421
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_28421.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_28421. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_28421.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_28421.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_28421.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
If there are any ovw 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 are
detected.
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_name>.text file
to /opt/OV/ReleaseNotes/patches. Please make
sure this file is in /tmp before installation.
========================================================
-----End of Document ID: PHSS_28421------------------------------------------
Document ID: PHSS_28452
Date Loaded: 20030311
Title: s700_800 11.X OV ITO7.1X Data Comm Component Linux A.07.12
Patch Name: PHSS_28452
Patch Description: s700_800 11.X OV ITO7.1X Data Comm Component Linux A.07.12
Creation Date: 03/03/07
Post Date: 03/03/11
Hardware Platforms - OS Releases:
s700: 11.00 11.11
s800: 11.00 11.11
Products:
OpenView Operations 7.1
Filesets:
OVOPC-CLT.OVOPC-LIN-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64,v=HP
OVOPC-CLT.OVOPC-LIN-CLT,fr=A.07.10,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_28452
Symptoms:
PHSS_28452:
- SR: B555012657
llbserver is now enhanced. It is possible to print out a
list of applications registered with llbserver by running
'llbserver -query'.
With 'llbserver -ping' one can check if llbserver is
running.
- SR: B555013635
Many instances of llbserver can run in parallel on the
same port.
- SR: B555015110
SuSE 8.1 and RedHat 8.0 are not supported
Defect Description:
PHSS_28452:
- SR: B555012657
llbserver is now enhanced. It is possible to print out a
list of applications registered with llbserver by running
'llbserver -query'.
With 'llbserver -ping' one can check if llbserver is
running.
- SR: B555013635
Many instances of llbserver can run in parallel on the
same port.
Now llbserver checks whether another instance is already
running on configured port.
- SR: B555015110
SuSE 8.1 and RedHat 8.0 are supported now
for SR's not listed in this section please see
the list of symptoms
Enhancement:
No
SR:
B555015110 B555013635 B555012657
Patch Files:
OVOPC-CLT.OVOPC-LIN-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
v=HP:
OVOPC-CLT.OVOPC-LIN-CLT,fr=A.07.10,fa=HP-UX_B.11.11_32/64,
v=HP:
/var/opt/OV/share/databases/OpC/mgd_node/vendor/linux/intel/
linux22/A.07.10/RPC_DCE_TCP/comm_pkg.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/linux/intel/
linux22/A.07.10/RPC_DCE_TCP/comm_version
what(1) Output:
OVOPC-CLT.OVOPC-LIN-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
v=HP:
/var/opt/OV/share/databases/OpC/mgd_node/vendor/linux/intel/
linux22/A.07.10/RPC_DCE_TCP/comm_pkg.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/linux/intel/
linux22/A.07.10/RPC_DCE_TCP/comm_version:
None
cksum(1) Output:
OVOPC-CLT.OVOPC-LIN-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
v=HP:
2310941026 1064960 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/linux/intel/linux22/A.07.10/RPC_DCE_TCP/
comm_pkg.Z
2717782698 8 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/linux/intel/linux22/A.07.10/RPC_DCE_TCP/
comm_version
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches:
ITOSOL_00189:
sparcSOL: 2.7 2.8
Patch Package Size: 1070 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_28452
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_28452.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_28452. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_28452.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_28452.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_28452.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHSS_28452------------------------------------------
Document ID: PHSS_27722
Date Loaded: 20030311
Title: s700_800 11.X MC/ServiceGuard and SG-OPS Edition A.11.13
Patch Name: PHSS_27722
Patch Description: s700_800 11.X MC/ServiceGuard and SG-OPS Edition A.11.13
Creation Date: 03/01/29
Post Date: 03/03/11
Hardware Platforms - OS Releases:
s700: 11.00 11.11
s800: 11.00 11.11
Products:
MC/ServiceGuard A.11.13
ServiceGuard OPS Edition A.11.13
MC/ServiceGuard quorum server for HP-UX version A.01.00
Filesets:
DLM-Pkg-Mgr.CM-PKG,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP
Package-Manager.CM-PKG,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP
DLM-Clust-Mon.CM-CORE,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP
Cluster-Monitor.CM-CORE,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP
DLM-Clust-Mon.CM-CORE-MAN,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP
Cluster-Monitor.CM-CORE-MAN,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP
DLM-NMAPI.CM-NMAPI,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP
DLM-ATS-Core.ATS-RUN,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP
ATS-CORE.ATS-RUN,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP
DLM-Prov-MOF.CM-MOF,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP
CM-Provider-MOF.CM-MOF,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP
DLM-Prov-MOF.CM-PROVIDER,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP
CM-Provider-MOF.CM-PROVIDER,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical:
Yes
PHSS_27722: ABORT
cmcld could abort when a package with name more
than 36 characters and an ip address is halted.
cmcld could abort (with assertion failure) if it
goes for the quorum server, the qs lock is granted
but there is a reconfiguration before lock granted
message arrives.
PHSS_27087: ABORT
When using a contributed support tool to disable
and then re-enable safety time, the tool fails to
restore safety time protection properly, resulting
in node TOC.
If cmviewcl command is issued at the same time
either package configured resource, subnet or
service being deleted from the configuration, then
cmviewcl may fail with a SIGSEGV creating a core.
A series of single point network card or hub
failures may cause a cl_sync timeout resulting in
the entire cluster going down.
At cmcld start up, i.e. cmrunnode or cmruncl,
syslog shows this message,
"cmcld: Assertion failed: pnet != NULL, file:
comm_link.c, line: 140."
cmcld immediately aborts and dumps core.
Service Assistant Daemon (cmsrvassistd) can dump
core in /var/adm/cmcluster if SIGCHLD is delivered
while in the middle of a syslog call.
PHSS_26928: ABORT
In a 2 node ServiceGuard cluster, if cmcld on one
node experiences a long kernal hang and again tries
to join the cluster then the whole cluster can
crash.
A series of short kernel hangs on one node lead to
cluster reformation and continues during
reformation. This opens a small timing window
where the node that is healthy hits an assertion
failure.
PHSS_26674: ABORT CORRUPTION OTHER
ServiceGuard daemon (cmcld) may abort with core
dump when a package is started or halted.
A ServiceGuard OPS node may TOC after a false
unclean shutdown.
ServiceGuard daemon (cmcld) may abort with core
dump due to DLPI errors.
ServiceGuard daemon (cmcld) may abort with core
dump during cluster formation.
A package may be started on two nodes, causing
data corruption.
PHSS_26180: ABORT
ServiceGuard command "cmrunnode" can abort with
core dump after cluster is started on a node.
ServiceGuard configuration command will not able to
configure package with EMS resource if that
resource is not available on local node.
PHSS_25915: ABORT
ServiceGuard daemon "/usr/lbin/cmcld" can abort
with core dump when multiple cmapplyconf or
cmrunnode commands are issued and any one of them
is aborted.
PHSS_25124: ABORT
ServiceGuard daemon "/usr/lbin/cmcld" aborts with
core dump "/var/adm/cmcluster/core." The
function "cl_delete_event" was freeing
the data memory of an event twice if the
event had a destructor function attached
to it. The destructor would free it and
then cl_delete_event would free the same
memory again.
PHSS_24678: CORRUPTION
Formation of 2 clusters may potentially result in
packages running on 2 nodes at the same time
and may potentially result in data corruption
issues.
Category Tags:
defect_repair enhancement general_release critical
halts_system corruption
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_27722
Symptoms:
PHSS_27722:
1. The cmviewcl command intermittently fails with an
error message:
cmviewcl : Unable to query status for all packages:
Device busy
2. The hpmcSGClusterDown trap is never generated or sent
and the hpmcClusterState mib variable is never set to
down by the cmsnmpd subagent when the cluster is halted.
3. When multiple package commands (cm*pkg) are issued
during a cluster reformation, only the command issued
last will succeed. The rest of them may hang.
4. Admin functions executed through ServiceGuard
Manager are not logged in syslog on a cluster
node where operation takes place.
5. The man page for cmcheckconf gives the wrong
information for the -k option. The information for
this option is actually for the cmquerycl -k option.
6. During an online package modification which
removes previously-existing EMS resources, the
previously-existing resources are not unregistered
from EMS and deleted from memory properly, resulting in
lingering monitor requests and unfreed heap space.
7. When FS_MOUNT_RETRY_COUNT is set to 1 and if
the mount command fails to mount the file system
due to mount point being busy, the script returns
a failure even after successfully killing the processes
using that mount point and being able to retry and
successfully mount the file system in the second try.
As a result the package fails to start on the node.
Messages like the following will appear in the package
log file:
ERROR: Function check_and_mount
ERROR: Failed to mount /dev/vg01/lvol01
8. An SG command could hang shortly after a cluster
formation.
9. Online node reconfiguration with cmapplyconf fails
occasionally because of a race condition problem.
10. In the cmlvmd shutdown routine, SLVM Shutdown ioctl is
issued unnecessarily for SG OPS. syslog will show a
message saying that SLVM is already initialized.
11. cmcld could abort when a package with name more than 36
characters and an ip address is halted.
12. cmcld may log the following error message to syslog
while still functioning properly:
cmcld: Failed to connect to <IP address>:<port>
(Interrupted system call)
13. If two clusters have their private subnets bridged to
the public subnet and there is no route from cluster
A's interfaces to the cluster B's private subnet,
there is a race condition between the non-routable udp
broadcast packets coming from A's private subnet and
the udp broadcast packets coming from A's public
subnet that would cause cluster A from being able to
discover cluster B.
14. cmcld could abort (with assertion failure) if it goes
for the quorum server, the qs lock is granted but there
is a cluster reformation before lock granted message
arrives.
15. If any problem occurs during package startup after NFS
services have been started, causing package start to
fail, package restart would fail again even after
fixing the problem.
16. It is possible that when a ServiceGuard package
unmounts filesystems in umount_fs, not all filesystems
are unmounted and the volume group deactivation fails
with device busy. This is most likely to be true when
CONCURRENT_MOUNT_AND_UMOUNT_OPERATIONS is set to a
large number.
17. The following error message is found in the
package control log file:
"fuser: illegal option --C"
18. The cmviewconf command does not show the quorum server
(if one is configured).
19. Erroneous hpmcSGPkgDown traps with blank nodenames
are generated by cmsnmpd during cluster start up
or reformations caused when SG nodes fail, halt or
are started.
20. The cmsnmpd subagent doesn't update the
hpmcSGPkgSubnetStatus MIB variable when a package's
subnet fails or comes up.
21. When a node is halted, cmsnmpd shows inaccurate
hpmcNodeRole mib variables on the halted node.
22. During a normal cluster shutdown, cmsnmpd doesn't
receive a node halted event from the SG subagent api
on the last node in the cluster to be halted. This
causes cmsnmpd to assume that the last node in the
cluster failed, and sets the hpmcNodeStatus mib
to "failed" and doesn't send out the appropriate
hpmcSGNodeHalted trap.
23. When an Oracle RAC database instance goes down
unexpectedly or is shutdown because "shutdown abort"
is used, the surviving Oracle RAC database instances
can take longer than normal time to finish database
recovery and return to normal operation.
24. If a user tries to change a package script timeout
using SAM/GUI without any other modifications, SAM/GUI
will ignore the changes and package configuration will
remain unchanged.
PHSS_27087:
1. When using the unsupported contributed cmsetsafety tool
to disable and then re-enable safety time, the tool
fails to restore safety time protection properly,
resulting in node TOC.
2. If the cmviewcl is issued at the same time that a
package resource,subnet or service is being deleted
from the configuration by another session using
cmapplyconf, then the cmviewcl may fail with a SIGSEGV
creating a core.
The stack trace by GDB typically contains:
#0 0xc01ffd40 in kill () from /usr/lib/libc.2
#1 0xc019b3b4 in raise () from /usr/lib/libc.2
#2 0xc01db550 in abort_C () from /usr/lib/libc.2
#3 0xc01db5ac in abort () from /usr/lib/libc.2
#4 0xd5ca8 in cdb_get_resource_list
(cluster_handle=0x40025f38 "",
pkg_name=0x40032b38 "pkg9424_2",
num_resources=2, resource_list=0x400325f0)
at config/config_cdb_data.c:1138
#5 0x8f560 in view_resource
(cluster_handle=0x40025f38 "",
pkg_name=0x40032b38 "pkg9424_2",
node_name=0x40036df0 "buf",
print_for_unowned=1) at cmd/cmd_view.c:2581
#6 0x8d224 in view_unowned_pkg
(cluster_handle=0x40025f38 "",
pkg_name=0x40032b38 "pkg9424_2",
package_format=0x40022990 "
vflag=1, lflag=1, plimit=1,
pkg_status=0x40009340 "down",
pkg_state=0x40009338 "halted",
pkg_switching=0x400093a0 "disabled",
pkg_owner=0x400354f8 "unowned",
status_str=0x40008ed8 "up")
at cmd/cmd_view.c:1859
#7 0x8ae88 in view_cluster
(cluster_name=0x40026118 "STRESS_lvk_0419",
vflag=1, lflag=1, numpkgs=0,
pkgs=0x40025430, numnodes=0,
nodes=0x40025440, climit=0,
plimit=1, nlimit=0, gflag=0)
#8 0x87a5c in view_main (argc=4, argv=0x7f7f01a4)
at cmd/cmd_view.c:289
#9 0x76758 in main (argc=4, argv=0x7f7f01a4)
at cmd/cmd_main.c:220
3. A package configured to use the large number of
file systems spread across the multiple volume groups
takes longer to mount the file systems. Also there
is no mechanism provided in the control script for
the user to specify additional options to fsck and
umount commands used in the package control script.
4. When cmcld is running with more than ten network
interface cards configured on a cluster node, its
CPU utilization percentage raises significantly.
This problem is mostly exposed with Superdome machines,
or systems with large VLAN configuration.
5. A series of single point network card or hub failures may
cause a cl_sync timeout resulting in the entire cluster
going down. Syslog reports error:
"Node id X did not reach sync step 0 for activity 3"
6. A cmapplyconf succeeds with unquoted 2-word value for
string resource. For example:
RESOURCE_UP_VALUE = very stable
The cmapplyconf would succeed, but the resource would
be "UP" when its value was "very" not "very stable".
7. In SAM/GUI a user is not able to see a hierarchy of EMS
resources in package configuration screens.
8. The cmsnmpd subagent will store the package status
as unknown, instead of down in the ServiceGuard MIB
table when a package's node fails and the package is
not restarted.
9. If cmrunnode or cmruncl times out, in a subsequent
cluster formation a package configured with automatic
start resources may fail to come up on its primary node.
10.ServiceGuard commands cmcheckconf/cmapplyconf with -P
option and without -C option can take longer to finish.
Even specifying -k option does not improve a performance.
This can be also noticed if ServiceGuard is upgraded from
11.09 or earlier version to 11.13 or 11.14.
11.ServiceGuard commands cmcheckconf/cmapplyconf with -k
option can take long time if there are large number of
disks and volume group configured on system while only
very few of them are mentioned in cluster ascii file.
12.At cmcld start up, i.e. cmrunnode or cmruncl, syslog
shows this message,
"cmcld: Assertion failed: pnet != NULL, file:
comm_link.c, line: 140."
cmcld immediately aborts and dumps core.
13.Service Assistant Daemon (cmsrvassistd) can dump core
in /var/adm/cmcluster if SIGCHLD is delivered while in
the middle of a syslog call. The stack trace in the
core dump would look like this:
#0 0x400c942f in tz_compute (tm=0xbffff064)
at ../sysdeps/i386/bits/string.h:343
#1 0x400c95c4 in __tz_convert (timer=0xbfffeee8,
use_localtime=1, tp=0xbffff064) at tzset.c:593
#2 0x400c576b in __localtime_r (t=0xbfffeee8,
tp=0xbffff064) at localtime.c:33
#3 0x4010298d in vsyslog (pri=27, fmt=0x805f740 "Unable to
send 64 bytes (Software caused connection abort).\n",
ap=0xbffff0dc) at syslog.c:170
#4 0x401028a9 in syslog (pri=27, fmt=0x805f740 "Unable to
send 64 bytes (Software caused connection abort).\n")
at syslog.c:102
#5 0x0804ba2c in cl_vsyslog (private_data=0x0,
category=131072, level=0, module=5,
fmt=0x8059dc0 "Unable to send %d bytes (%s).\n",
ap=0xbffff130) at utils/cl_syslog.c:91
#6 0x0805859b in cl_clog (clog_handle=0x0,
category=131072, level=0, module=5,
fmt=0x8059dc0 "Unable to send %d bytes (%s).\n") at
utils/cl_clog.c:123
#7 0x0804c356 in cl_local_cl_send (fd=0,
service_id=12,msg=0xbffff1ac, msg_length=32, flags=1,
reply=0x0, timeout=0x0,logh=0x0 at
lcomm/local_client.c:497
#8 0x0804b885 in handle_sig_chld (in=17) at
servsen/serv_assist.c:1236
#9 <signal handler called>
Also, the message the user will see is:
"Process creation daemon terminated due to a
signal(11)."
14.After customer modified the hostname, packages using
VxVM disk groups failed to start.
15.At package start up, busy mount point might not be
freed up and re-mounted appropriately.
PHSS_26928:
1. After a package has been added to a cluster, cmsnmpd may
not update the MIB and hence the package may not be
available as a resource to be monitored by another
package.
2. When the PACKAGE environment variable is improperly set
in the package control script, the script fails with
errors such as the following:
cmmodnet : Subnet <subnet> is not a configured subnet.
cmmodnet : Use the "netstat -in" command to list the
configured subnets.
No errors are logged to syslog.
3. If there are multiple cluster nodes issuing
configuration queries at roughly the same time,
cmgetconf can silently timeout.
4. When a node with a node ID that is not the first or last
node ID in the cluster is removed from a ServiceGuard
OPS Cluster, the "cmviewcl -l group" command will return
an error message like:
cmviewcl : Failed to convert node_name xxx to node_id.
5. Primarily on ServiceGuard OPS clusters, the cmrunnode
command executed from the cmcluster rc script may fail.
When this happens, other nodes in the cluster may log
messages in syslog such as:
cmcld: Detected different configuration data on node
<Node Name>
cmcld: Can not form cluster with node <Node Name>
cmcld: Quitting due to configuration data version
mismatch
6. In a 2 node ServiceGuard cluster, if cmcld on one node
experiences a long kernal hang and again tries to join
the cluster then the whole cluster can crash. This
can be seen on more than 2 nodes if cmcld on all the
nodes except on one node experiences long kernel hang.
The syslog on node which does not experience the kernel
hang will log messages like:
cmcld: Timed out node <node_name>. It may have failed.
cmcld: Attempting to form a new cluster
cmcld: Safety time set for 128.96 seconds from now
cmcld: Did not receive all votes: 1 out of 2
cmcld: All votes (100) are required at this point.
vmunix: SCSI: Reset requested from above -- lbolt:
246237, bus: 2^M^M
cmcld: Got at least 50 votes: 1 out of 2 last active
nodes.
cmcld: Obtaining Cluster Lock
cmcld: Successfully issued request for cluster lock
/dev/dsk/c2t8d0
vmunix: SCSI: Resetting SCSI -- lbolt: 246337, bus: 2^M^M
vmunix: SCSI: Reset detected -- lbolt: 246337, bus: 2^M^M
cmcld: Cluster lock disk /dev/dsk/c2t8d0 appears healthy
cmcld: Successfully obtained the Cluster Lock
cmcld: lock id: 6
cmcld: Turning off safety time protection since the
cluster
cmcld: may now consist of a single node. If ServiceGuard
cmcld: fails, this node will not automatically halt
cmcld: Active node <nodename> has voted for me
cmcld: Enabling safety time protection
cmcld: Enabled safety time with 257774
cmcld: Attempting to adjust cluster membership
cmcld: Safety time set for 7.71 seconds from now
cmcld: Active node <nodename> has voted for me
cmcld: Clearing Cluster Lock
7. When a shutdown(1m) command is run from two nodes
concurrently, it can cause cmhaltnode to fail. This can
happen if one node has completed its cmhaltnode and the
other node is still running cmhaltnode. This problem can
also be seen if a cmhaltnode command is halting the
cluster on one node and another node in the cluster does
a TOC or a reboot before the cmhaltnode command
completes.
The /etc/rc.log.old will contain messages or command
will exit with messages like:
Warning: Do not modify or enable packages until the
halt operation is completed.
Halting Package <pkg_name>
cmhaltnode : Unable to halt package <pkg_name>: Socket
is not connected
Check the syslog and pkg log files for more detailed
information:
cmhaltnode : Warning : node failed to HALT
ERROR: Unable to halt cluster on this node.
8. Large numbers of the following message are logged to the
syslog.log file:
Mar 18 10:00:48 HGALUX07 cmclconfd[15865]: Unable to
attach to network interface 1.
This happens whenever customers try to view properties
of objects in SG MGR, or when cmquerycl, cmcheckconf,
cmapplyconf are issued.
9. A series of short kernel hangs on one node lead to
cluster reformation and continues during reformation.
This opens a small timing window where the node that is
healthy hits the assertion failure,
cmcld: Assertion failed: !node->hb_eligible,
file: election.c, line: 5699.
10. cmapplyconf continually fails with Error:
Unable to begin the configuration change
11. Message missing when EMS Monitor returns RM_NOT_READY
In 11.09, we print the "monitor is not ready" message
as soon as we get a RM_NOT_READY reply back from a
register operation. In 11.13, we do not print this
message.
12. cmsnmpd will not store cluster name in the mib
definition when started while cluster or local
node are halted. A call to "resls /cluster/status"
will result in output which is missing the cluster
name.
PHSS_26674:
1. When a local LAN failover fails, no error messages about
the failure are logged to syslog.
2. When the concurrent fsck's have been defined in the
package control script, the fsck's executed on the
Journaled File System during a package start up log
messages in a random order. As a result it is hard to
associate the messages from the package control script
log with the volume groups being checked.
3. When SAM GUI switches environments, certain tasks are no
longer available.
4. When using the admin feature of ServiceGuard Manager to
start a node, if the node is powered off or is in the
process of shutdown or reboot, a confusing error message
appears in the progress dialog box:
"unable to obtain cluster membership with
instance id SGClusterNodeContainment:<instance-id>"
5. Certain network load balancers or switches may not be
able to complete local switch within ten seconds after a
local switch occurs in ServiceGuard. This can result in
the client side not experiencing the failover
performance benefit that the network load balancer can
provide.
6. The ServiceGuard daemon, cmcld, may experience SIGSEGV
and accordingly dump core when a package is started or
halted. The resulting stack trace will show
segmentation violation.
7. DLM references are still seen in the configuration ascii
file generated by cmquerycl for ServiceGuard OPS Edition.
8. If an EMS monitor on the system is not yet ready to
monitor a resource on which a ServiceGuard package is
dependent, the package will fail to start.
The following messages may be seen in syslog:
cmcld: ems monitor for <resource name> is not ready
above message repeats 2 times
cmcld: Resource <resource name> set to "UP".
cmcld: Package <package name> cannot run on this node
because resource <resource name> does not meet
package RESOURCE_UP_VALUE.
9. A package configured with a deferred start resource may
start and halt immediately when the cluster starts up.
The following messages may be seen in syslog:
cmcld: Started package <package name> on node <node
name>.
cmcld: Package <package name> cannot run on this node
because resource <resource name> does not meet
package RESOURCE_UP_VALUE.
cmcld: Resource <resource name> in package <package
name> does not meet RESOURCE_UP_VALUE.
cmcld: Executing '<package control script path> stop'
for package <package name>, as service <service
ID>.
10. Issuing the command "cmsetlog -M RES" to turn up
logging in the resource module does not work.
11. A ServiceGuard OPS node may fail to halt resulting in
a TOC. The following error messages may be seen in
syslog:
cmcld: CMGMSD successfully halted
cmcld: Failed to unregister all resource monitor
requests.
cmcld: This node (<node name>) has ceased cluster
activities.
cmcld: Daemon exiting
cmcld: CMGMSD/GMS halted but unable to halt SG.
Rebooting...
12. Quorum Server is now supported on ServiceGuard A.11.13.
This is a new feature. The Quorum Server software,
information and documentation is available on
http://www.software.hp.com. Documentation is also
available on docs.hp.com/hpux/ha
Also, the man pages have been updated to show the -q
option, and the commands have the -q option turned on
by default.
13. ServiceGuard A.11.13 now supports adding a new package
resource to any package while the cluster is running.
14. ServiceGuard daemon cmcld aborts with the message
"DLPI error! dl_errno: 1, dl_unix_errno: 0." in syslog.
This leads to a system TOC.
15. When nodes configured for a particular package are only
a subset of the nodes in the cluster, a call to
cmGetstatus(CM_PKG_STATUS) may return -26, causing
cmsnmpd to sever the socket connection with the
ServiceGuard cmcld daemon. This behavior will happen
when the user brings up the cluster or node and/or
restarts the cmsnmpd subagent. Once the socket
connection with SG is severed, no MIB variables or SNMP
traps will be updated or sent, which results in stale
data in the SG MIB table.
16. During cluster formation, cmcld can exit with a
segmentation violation. The stack trace of the
resulting core looks like:
cl_local_srv_free\952 (00121284) (`thread(24))
ss_monitor_operation_phase_II\441 (001285A0)
ss_cl_local_reply_event\944 (00129A88)
ss_event_handler\1069 (00129F20)
ss_event_handler (hpux_export stub) (00129E38)
cl_event_loop\434 (001C34E0)
cl_event_loop (hpux_export stub) (001C2D18)
cma__thread_base+01e8 (002283B0)
cma__thread_start1+0030 (0022A500)
cma__thread_start0+0004 (00229F9C)
17. Shortly after a cluster starts (via cmruncl or
cmrunnode on all nodes), cmcld can exit with the
following message:
Fatal internal error - Assertion failed:
ntohl(node_ptr->node_info.p_state) == P_NOT_OWNED,
file: pkg_list.c, line: 298
It is possible that before cmcld exits, packages may
have started up on this node, however these packages
will not be halted. So when the remaining nodes in the
cluster take over the packages that were running on
this node, it is possible for data corruption to occur
if VxVM disk groups are used in the packages, since
they are activated on more than one node. Also,
software components which communicate with the affected
application may experience connection problems
associated with the package's IP address appearing on
two nodes at the same time.
18. cmviewcl -v fails to show services of system
multi-node packages. This problem was introduced with
PHSS_26180.
19. A package configured with automatic start resources may
start on an adoptive node instead of on the primary node
during cluster startup, due to the resources being
registered with EMS earlier on the adoptive node than on
the primary node.
20. Not all resource monitor requests are unregistered with
EMS when cmcld exits, so the next time cmcld starts up
and registers the same requests with EMS, it will not
get immediate notifications regarding the state of the
resources, and packages will not be able to start.
PHSS_26180:
1. SG supports only 60 packages. With this patch it now
supports 150 packages. After installing this patch on
all nodes in the cluster, the cluster must be brought
down in order to increase the MAX_CONFIGURED_PACKAGES
parameter in the cluster ascii file. Once this is
changed, up to 150 packages may be configured.
Note that once a cluster has more than 60 packages
configured, any upgrade to SG version 11.14 MUST include
patch PHSS_26056. So, after halting a node and
upgrading that node to 11.14, PHSS_26056 must be applied
before bringing that node back into the running cluster.
If this procedure is not followed, any nodes running
11.14 without the patch could crash (TOC) due to cmcld
dying with SIGSEGV or SIGBUS. Be sure to set
AUTOSTART_CMCLD to 0 in /etc/rc.config.d/cmcluster
before beginning the upgrade to 11.14.
The SG11.14 patch PHSS_26056 will be released later this
spring. Until it is released, customers using > 60
packages must remain on 11.13 and not upgrade to 11.14.
Note that running 150 packages requires systems that
have a lot of capacity. If your systems are not
powerful enough, some of your packages may not start or
may partially start. In this case, you will need to
reduce the number of packages. Test each node by
running the cluster on that node only (cmruncl -n node),
and make sure all packages start that are configured to
run on that node.
NOTE: At this time ServiceGuard Manager does not
support more than 60 packages per cluster.
2. The cmrunnode command may core dump immediately before
exiting with output similar to:
cmrunnode : Waiting for cluster to form.....
cmrunnode : Cluster successfully formed.
cmrunnode : Check the syslog files on all nodes in the
cluster
cmrunnode : to verify that no warnings occurred during
startup.
Bus error(coredump)
3. The cmcheckconf/cmapplyconf command will fail for a
package if EMS resource is not available on the node
where command is issued even if that package only runs
on other nodes in the cluster where the resource is
available.The commands will fail with output similar
to:
Error: ems subclass request for <resource_name> failed,
resource type (3016)
Error: Failed to get type information for
<resource_name> on node <remote_node_name>
PHSS_25915:
1. A package that has a resource with more than one
RESOURCE_UP_VALUE criterium defined is halted as
soon as the value for the resource changes such that one
of the criteria is unsatisfied, even if the value might
meet other criteria. Affected users include HA Disk
Monitor users who are recommended to configure more
than one RESOURCE_UP_VALUE criterium for each
volume group monitored.
2. When any unused node (i.e. node not part of a cluster)
is included in the scope of a ServiceGuard-related
query for the Object Manager, we would get incorrect
results. For example, an error may be encountered on
ServiceGuard Manager while trying to save a
configuration involving an unused node.
To reproduce this defect in ServiceGuard Manager:
1) Check the "include unused nodes" option in the
startup screen.
2) Connect to the Object Manager and view the current
configuration.
3) Save the current configuration. It will fail with the
error message:
"Error 0011 : Failed to save file <file name>
Cause : Server Schema Error."
3. cmviewconf displays an incorrect HALT_SCRIPT_TIMEOUT
value for a package when the RUN_SCRIPT_TIMEOUT is
set to NO_TIMEOUT (0) and the HALT_SCRIPT_TIMEOUT
is set to a non-zero value.
4. After an upgrade of a ServiceGuard cluster to version
11.13 from version 11.12 or earlier, if any package
with an EMS resource has been added and deleted before
upgrade, then the addition of any new package to the
cluster after upgrade may fail. The cmapplyconf command
will return error messages like:
Error: Unable to apply the configuration change:
Unknown error: 3015.
Check the syslog file(s) for additional information.
cmapplyconf : Unable to apply the configuration
The syslog may contain the error messages like:
cmcld: cdb_db_prepare - 3015 error occurred 5
5. If cmrunnode or cmapplyconf are stopped in the middle of
execution and there are multiple such commands running
concurrently, then the cmcld may fail with a SIGSEGV or
SIGBUS creatig a core in /var/adm/cmcluster/core. The
syslog will contain the messages like,
cmlvmd: Could not read messages from /usr/lbin/cmcld:
Software caused connection abort
cmlvmd: CLVMD exiting
cmsrvassistd[]: The cluster daemon aborted our
connection.
cmsrvassistd[]: Lost connection with ServiceGuard
cluster daemon (cmcld): Software caused connection
abort
The stack trace by GDB typically contains:
#0 0x105d94 in cdb_client_port_close () from
/usr/lbin/cmcld
#1 0x1413a0 in cl_thread_start () from /usr/lbin/cmcld
#2 0x1aa8e8 in cma__thread_base () from /usr/lbin/cmcld
#3 0x1aca38 in cma__thread_start1()from /usr/lbin/cmcld
#4 0x1ac4d4 in cma__thread_start0 () from
/usr/lbin/cmcld
#5 0x105f0c in cdb_client_port_close () from
/usr/lbin/cmcld
6. If a configuration operation gets aborted during a
cluster reformation with a down node joining the cluster,
cmcld may abort on the node that is rejoining with the
following messages:
Action - Invalid transaction state of NO_TRANS for
node id x, (ABORTED)
Internal error - Aborting: cdb/cdb_coord_comm.c 517
(Invalid transaction state)
PHSS_25124:
1. A package with more than one EMS resource configured is
unable to restart on the same node after the cluster
has been halted at least once.
2. ServiceGuard Manager failed to halt Linux cluster.
3. ServiceGuard command cmapplyconf still succeeds while
there is an error in network configuration such as
"Non-uniform connection detected."
4. When the .rhost and cmclnodelist file are missing or not
setup properly, ServiceGuard command cmquerycl or
cmviewcl no longer prints the error message "Permission
denied to X" where X is the IP address of the node.
Instead, the command prints misleading error messages
such as:
"Error" Unable to establish communication to node Y"
5. If a node is halting while a ContinentalClusters customer
runs a ContinentalClusters command, that command could
fail with a stack trace.
6. ServiceGuard daemon "/usr/lbin/cmcld" will ABORT,
leaving a core dump "/var/adm/cmcluster/core." The
symptoms can include varying abort messages and
varying stack traces in the cores. There is no single
consistent message or pattern of messages found in
syslog that can predict this. Typically, the failure
will be when processing Event Monitoring Services.
However, many times it would be an unexplained segment
violation. Use of cmapplyconf or packages using
resources can sometimes lead to the problem.
7. Under extreme stress test, cmcld's memory might jump
128K after cluster has formed.
8. A package configured to use the large number of
file systems spread across the multiple volume groups
takes longer to failover.
9. ServiceGuard commands cmstartres and cmstopres fails
for long resource name of more than 40 characters with
error,
"Resource name should not be longer than 1024
characters."
10.ServiceGuard cluster with serial link will fail if all
heartbeat network switches fails. The similar thing
with serial link can be seen if crossover cables are
used for all heartbeats and one of the node fails.
PHSS_24678:
1. The snmpdm agent logs "CloneVarBind: Unable to clone
vb->value.os_value" messages in the /var/adm/snmpd.log
file when the cmsnmpd subagent is brought up or
certain ServiceGuard events are generated while the
local node or cluster is down.
2. After starting and stopping Oracle OPS, with the command
netstat -an | grep 5408, there are tcp connections with
status FIN_WAIT_2. Port 5408 is used by cmgmsd and gmapi
clients. It was observed that these TCP connections do
not go away until they reach the max tcp resources or
until the cluster is halted.
3. Without this patch, SGManager GUI cannot perform
ServiceGuard administrative operations such as
run and halt node, package or cluster. This patch
along with PHSS_22175 will enable SGManager to
perform ServiceGuard administration.
4. Add mechanisms to ensure that SG shared tape
functionality is not available if kernel tuneable for
stape reserved/release functionality is disabled.
5. cmquerycl command times out and fails when there are
additional subnets on some nodes that are not on other
nodes:
Error: Unable to establish communication to node
<nodename>
Failed to gather configuration information.
In addition, other SG commands such as cmviewcl
and cmhaltpkg are delayed 10 seconds.
6. The cmapplyconf command gets internal error when adding
a node to a cluster.
Internal error: Got unexpected generic_ack with no error
number from cmclconfd on <nodename>.
Error: Unable to retrieve configuration file from node
<nodename>: Error 0
cmapplyconf : Unable to apply the configuration
7. Automatic failback fails for packages which are
configured with:
FAILBACK_POLICY AUTOMATIC
. . .
STORAGE_GROUP VxVMdg
where VxVMdg is a CVM disk group.
A package which is configured with FAILBACK_POLICY
AUTOMATIC is supposed to move back to the primary
node when that node rejoins the cluster. In this
case it does not.
8. "Error releasing device <dsk> (#) in volume group <vg>:
No such device or address"
error messages are printed in syslog by cmclconfd when
cmcheckconf, cmapplyconf, cmgetconf or cmquerycl were
issued. One possible side effect is that syslog may
report on cluster start that cluster lock is not
initialized, although early on, after cmapplyconf, it
did report that cluster lock already got initialized.
Another symptom is that subsequent tries to create
or import a VG can fail.
9. The cmcld daemon may log the message "timers delayed x.x
seconds" due to kernel latency issues. A ServiceGuard
cluster of more than 2 nodes with no cluster lock, after
experiencing a long kernel hang caused by such latency
issues, may result in the formation of 2 clusters. The
node which experiences the long kernel hang may form a
1-node cluster, while the remaining nodes in the cluster
may form another cluster.
10. A 2-node ServiceGuard cluster with a cluster lock
may result in the formation of 2 clusters if all
heartbeat networks experience prolonged heavy
network congestion or if the cmcld daemon on any node
experiences frequent kernel hangs within short periods
of time.
Defect Description:
PHSS_27722:
1. During cluster reconfiguration, if a node trying
to join the cluster responds last to the config_com
probe, it updates the pnode information for other
nodes as EBUSY, which results in the subsequent
failures.
Resolution:
Don't update the configd cache if responding node
is in the EBUSY state.
2. The hpmcSGClusterDown trap was never implemented because
there was no reliable way for the SG subagent api to
send a "cluster down" event because each node halts
independently and once cmcld stops running, cmsnmpd
can no longer retrieve the cluster status from the
SG subagent api.
Resolution:
When cmsnmpd receives an event that the local node
has halted or failed, then it will locally check the
cluster status and set the hpmcClusterStatus
mib variable to "down" and send a cluster down trap
if the cluster is down.
3. During a reconfiguration, if multiple package commands
are issued, only the command issued last will succeed.
Rest of them will hang. The timer that got created
to retry the package commands, was getting overwritten
by successive commands. So, only the command that was
issued last will succeed, and the rest of the commands
get lost without being replied. This leads to a command
hang, for the ones that were lost without being replied.
Resolution:
Fixed the timer creation code for
the commands, to create individual timers for
each command, so that all the commands can be retried
and replied correctly.
4. This is an enhancement request. Remote admin requests
executed through Object Manager were not tracked
through syslog on a cluster node where operation
takes place.
Resolution: Enhanced admin code paths in config
library and ServiceGuard daemons to log more
information about the user requesting the request,
where the request being issued and how is it issued.
In order for this additional logging to be fully active
in CMProvider, COM A.01.03 Patch PHSS_26675 must also be
installed.
5. The manual entry for cmcheckconf incorrectly described
cmcheckconf -k as cmquerycl -k.
Resolution: Make change so the manual page displays the
right description.
6. Due to a coding error, resources that do not exist in
the new package configuration are skipped over and not
handled.
Resolution:
When the configuration transaction is being committed,
obtain resource information from delete list compiled
during the prepare transaction phase instead of from CDB.
7. Package with FS_MOUNT_RETRY_COUNT set to 1 failed
to start even after script successfully cleaned up
the busy mount point and successfully mounted the
file system.
Resolution:
Handle the scenario described above correctly
in the script by returning a success to the caller of
the freeup_busy_mountpoint_and_mount_fs().
8. During cluster formation, timers may be inadvertently
cancelled.
Resolution:
Correct the code that cancels timers during cluster
reformation.
9. cdb thread and reconfig thread have potential race
condition during online node reconfiguration
Resolution:
Rectify the code to remove the race condition.
10. SLVM initialization ioctl is not given for SG, but SLVM
shutdown ioctl is issued.
Resolution:
Do not issue SLVM shutdown ioctl for SG.
11. A message sent from cmmodnet to cmcld contained too
little space for the package name. cmcld read off the
end of the message, causing the core.
Resolution:
Increased the size of the message.
12. During a call to connect(), EINTR (interrupted system
call) is returned, causing the call to fail. This occurs
within local messaging mechanisms, so normal cluster
operations are not affected.
Resolution:
Retry the connect() call if EINTR is returned, since it
is just a transient error.
13. If the non routable probe reach the config daemon on B,
B will try to respond to this probe, but the response
will be dropped by the kernel because there is no route
to A's private subnet from B. Then when the packet
from the public subnet reaches B, the config daemon
drops this probe because B already received a probe
from A and considers this a duplicate probe.
Resolution:
Instead of doing limited udp broadcast, do a subnet
directed broadcast, which would be received on all
subnets but the message will be ignored by the driver
if the subnet specified in the broadcast does not
match the subnet of the interface itself.
14. cmcld could abort (with assertion failure) if it goes
for the quorum server, the qs lock is granted but there
is a reconfiguration before lock granted message
arrives.
Resolution:
Remove the assertion, this state should be allowed.
15. Since package start failed after NFS services had been
started, the undo sequence should take care of halting
the NFS services. However, this step is skipped leading
to package restart failure since control script tries
to start NFS services which are already running.
Resolution:
Add the step of halting NFS services to undo sequence
in package control script to handle the case where
error occurs after NFS services started.
16. The mount and umount patches, PHCO_24635 and
PHCO_26451 introduced a retry mechanism so mount
command could get a correct result from mount table
without locking it. This mechanism however still
sometimes returns an incorrect list of mounted file
systems since retry is not done indefinitely. Since
SG relies on result from mount command, there are times
when SG is not able to unmount all file systems because
of incorrect result it got from mount command.
Resolution:
Executing mount once instead of
CONCURRENT_MOUNT_AND_UMOUNT_OPERATIONS time reduces the
chance of mount returning incorrect information, thus
reducing the chance of umount_fs missing file systems
needed to be unmounted.
17. This is a coding mistake. The option -c was meant to be
used to display the use of the busy mount point
together with file systems under that mount point.
Resolution:
Get rid of -C option. The option -c is not used either
since in the case there is no file systems under the
busy mount point, fuser command will fail, although
-c option is just for verbose purpose.
18. This is an enhancement submitted by WTEC to include the
quorum server and its parameters in the cmviewconf
output.
Resolution:
Added code to display the quorum server and its
properties if one is defined.
19. This defect was introduced by SG 11.13 patch
PHSS_27087 and SG 11.14 patch PHSS_27246 and is
caused because there is no efficient way to send
a PkgDown trap when a coordinator node failed
and packages went down without all cluster
nodes knowing the previous package statuses.
Resolution: Changed cmsnmpd and package manager to
replicate package status information on all nodes in
the cluster. Any package status change from "up" to
"down" will be detected by all nodes in the cluster
and trigger the appropriate PkgDown trap to be sent
with the corresponding node name.
20. The subnet down/up SG api events didn't trigger the
cmsnmpd to correctly update the package subnet
status mib variable on all running nodes in
the cluster.
Resolution:
cmsnmpd correctly updates the package subnet mib
variable on all running nodes and sets the subnet
status to "unknown" on all halted nodes.
21. The node halted event doesn't trigger cmsnmpd
to set all hpmcNodeRole mibs to "unknown" on the
halted node.
Resolution:
Set all hpmcNodeRole mibs to "unknown" when a node
is halted.
22. The problem is a side effect of performance improvements
in the shutdown path of cmcld. Because cmcld is
shutting down faster, messages cached on the client
side MAY not have the time needed (race condition) to be
delivered to the subagent in time.
Resolution:
Make sure the client side delivers the cached
messages regardless of whether cmcld is still there
or not. If the connection drops (cmcld shutdown), put
the local connection (lcomm) into cache flush mode.
After the cache is flushed then deliver the drop
connection errno.
23. When an Oracle process goes away, it can take up to 10
seconds for cmgmsd to detect the death of a process.
After detecting the death of a process, cmgmsd starts
group membership reconfiguration to clean up this
process and inform the surviving Oracle instances about
the new group membership. Oracle cannot start database
recovery unit it receives the new group membership.
Resolution: In the current implemenation, cmgmsd checks
the health of the local group member processes every 10
seconds by looking up the kernel process table. cmgmsd
is changed to keep a socket connection to every local
group member process. When the process goes away, cmgmsd
can detect the socket connection is broken immediately
because the kernel closes the socket connection for
death processes. This allows cmgmsd to detect the death
processes very quickly.
24. SAM/GUI code sets the flag indicating that the script
timeouts changes have been made, but then does not
check it when deciding whether to update configuration
Resolution:
Fixed SAM/GUI code to check whether the flag indicating
changes in script timeouts is set.
PHSS_27087:
1. When safety time is disabled, a timer is started to
simulate safety time protection, but when safety time is
re-enabled, the timer is not cancelled and eventually
pops, leading to node TOC.
Resolution:
Change support tool to cancel the timer when enabling
safety time.
2. cmviewcl command tried to reference the CDB object that
no longer exist after online delete operation.
Resolution:
While getting object list from CDB, add an extra check
to verify that the number of objects retrieved from the
CDB are as expected.
3. The package control script used the default file
system type while mounting the file systems. The
mount command spent additional time in determining
the file system type required to mount the file
system. Also the array variables to provide
additional options to the fsck and umount
command didn't exit in the package control script.
Resolution:
Add variables FS_UMOUNT_OPT, FS_FSCK_OPT and FS_TYPE to
package control script template. These additional
variables can be used as described in the comment
section of the package control script.
4. Due to the support of online hotswap LAN cards and APA
product, ServiceGuard's network manager inefficiently
checks for change of MAC address of each LAN card on a
regular basis. This check does consumes lots of CPU
power, and the problem starts exposing when there are
many LAN cards configured in the cluster node where
cmcld is running.
Resolution:
Efficiently redesign the checking mechanism so that it
will not take lots of system CPU power while keeping
the supported features in tact.
5. Network connections (heartbeat and general service) are
not reestablished when the physical network is restored
until cluster reformation time. Connections are not
cleaned up fast enough when physical network goes down.
This defect was originally root caused in JAG ad94082.
A quick fix was put into PHSS_25499. That fix has been
backed out. This is the complete fix for that problem.
Resolution:
Add the 'rcomm health monitor' to monitor health of
connections. Reestablish responding connections,
disconnect non-responding connections.
6. The parser which reads and parses the package ascii
file, was looking for key word "AND." If a token was
not "AND" or "and" it was ignored.
Resolution:
The package ascii parser was modified to print error
when token after first up value is not "AND."
7. SAM/GUI did not use a proper routine to look up EMS
resources and therefore could not go beyond "/".
Resolution: The package configuration code was modified
to properly traverse EMS hierarchy
8. When cmsnmpd tries to determine if a package status has
changed when an node failure causes a cluster reconfig,
the valid/invalid bit is never checked and the
packages local flags aren't updated.
Resolution: Changed cmsnmpd to update a package's local
flags and to identify a package status change when a
package status changes from invalid to valid after a
node failure or cluster reconfig.
9. Resource monitor requests are not unregistered with
EMS when cmcld exits from a cmrunnode/cmruncl time-out,
so the next time cmcld starts up and registers the same
requests with EMS, it will not get immediate
notifications regarding the state of the resources, and
a package will not be able to start on that node.
Resolution:
Unregister resource monitor requests before cmcld exits
from a cmrunnode/cmruncl time-out.
10.In ServiceGuard release of 11.12 and later, a probing
mechanism is added when only -P option is used without
-C option. This was mainly done to validate CVM disk
group. This probing can take a long time particularly on
system having large number of disk and/or volume groups.
Resolution:
Don't do probing if only -P option is specified without
-C option.
11.ServiceGuard commands cmcheckconf/cmapplyconf even with
-k option opens all volume groups found in lvmtab file.
It will not matter how many volume groups are mentioned
in cluster ascii file, all volumes will probed.
Resolution:
When -k option is specified then probe volume groups
which are mentioned in cluster ascii file and skip rest
of volume groups found in lvmtab file.
12.This problem happens when customer tries to modify
the bridged net configuration. If the cluster has
existing binary configuration, cmcheckconf/cmapplyconf
are supposed to update the binary configuration
accordingly. However, these commands fail to do so and
only until cmruncl/cmrunnode do their own network
probing does ServiceGuard realizes the bridged net
configuration has been changed. At this time, cmcld goes
through the list of network cards it found, compare with
what exists in the binary configuration generated by
cmapplyconf but could not find a match, hence the
assertion failure.
Resolution:
Made change so cmcheckconf/cmapplyconf update binary
configuration correctly.
13.We are not properly blocking signals in the Service
Assistant Daemon.
Resolution:
We should only unblock signals before entering
the select call, and they should be blocked during all
other times.
14.This is actually not a defect. What happened was, when
VxVM is initialized, it stores the hostname as a
variable called 'hostid'. The package control script
use both this hostid and the value of the hostname
command. As a result, this hostid and hostname should
always match, which means if whenever hostname is
modified, hostid should be updated accordingly.
Resolution:
Added comment in package control script specifying
hostid need to be changed if hostname is changed,
using the vxdctl command.
15.The function used to free up mount point was not called
with the right option.
Resolution:
Added -c option to the fuser function call so all files
beneath the busy mount point would be displayed and all
the processes using the files would received SIGKILL.
PHSS_26928:
1. cmsnmpd may hold stale cluster data that prevents it from
updating the MIB correctly. The workaround is to restart
cmsnmpd.
Resolution:
Refresh the cluster data held by cmsnmpd every time a
configuration change occurs.
2. The PACKAGE environment variable should never be
explicitly set in the package control script, since it is
obtained from ServiceGuard when the script is executed.
However, in case the user sets it unknowingly, more
intuitive error messages should be logged.
Resolution:
Log the following message to syslog when the PACKAGE
environment variable specifies a package name that cannot
be found in the configuration:
cmcld: Unable to lookup package <package name>.
Documentation in the package control script has also been
enhanced to warn the user not to set the PACKAGE
environment variable.
3. When a query is sent it includes an id. The ids are
unique within a node but not within a cluster. This
can cause the receiver to believe they have already
sent a reply to a specific query even though it's
really from someone else.
Resolution:
Include the sender's node name as part of the query
id.
4. The Node_id is not changed after cluster is
reconfigured. So when a node with a node ID that is not
the first or last node ID in the cluster is removed from
the Cluster, there will be a free slot in node_id list,
and then cmviewcl will not be able to get the node name
for the removed node_id.
Resolution:
Continue to check the next node_id instead of reporting
this error.
5. The cmrunnode command collects cluster configuration
information from all nodes and copies the latest one
before starting the cluster. But sometimes during
system startup when all systems are starting, the
cmrunnode command can fail to collect the cluster
configuration information which can result in
failure of cluster formation.
Resolution:
A fix is added to make sure that the cmrunnode command
collects correct cluster configuration version, and if
unable to do so, it fails with error. The startup
script will then retry the command for 10 minutes and if
still unsuccessful, it will then give up.
6. The problem happens when one node of a cluster hangs,
causing a cluster reformation, and then returns
immediately before the cluster reformation completes
(late vote). If the cluster reformation is in the last
phase when the hung node returns and votes, the
coordinator must determine if it will accept the node
back into the election. There is a small window during
which this determination is done incorrectly.
Resolution:
The fix is to accurately determine whether the hung node
should be accepted back into the election. This
prevents the election from being restarted and both
nodes TOCing by safety timer expiring. In some cases,
the hung node will be allowed back in, and in other
cases it will TOC.
7. The cmhaltnode command halts packages first. While
halting the packages if other nodes in the cluster
reboot or halt, the cluster communications for halting
the package may get disconnected, resulting in an error,
ENOTCONN. This error causes the cmhaltnode command to
exit out without halting the cluster.
Resolution:
If an ENOTCONN error is generated before completing the
cmhaltnode command, the command will now handle this and
will retry to halt cluster services again, but this time
the rebooted or halted node will not be used for the
cluster communications for the package being halted.
8. At network probing phase, ServiceGuard tries to bind to
network interfaces of unsupported type.
Resolution:
Check for and skip lan cards of unsupported type.
9. SG design assumed once a node votes late and gets
deferred, it's no longer heartbeating with coordinator.
It turns out, although rarely, this does happen.
Resolution:
At election timeout, drop any node that's hb_eligible
but did not send us vote.
10. A cmapplyconf command is started, but goes away
immediately. The proxy server does not know this
because the proxy server did not check bind failure to
the command's lcomm port. Proxy server believes the
command is there, so it starts a transaction (acquires
config lock) and waits for the transaction to start.
Proxy will never know that the command is already gone.
Subsequent applyconfs will fail since the config lock
is held already.
11. The "monitor is not ready" is not printed in 11.13 as
it was in 11.09 - customers prefer that the behavior
be like it was on 11.09
Resolution:
Change message for RM_NOT_READY so it is
printed as it was in 11.09 - when the monitor
is not ready.
12. The fix submitted for JAGad68565 in
PHSS_24678 (SG11.13) and PHSS_24536 (SG11.09)
to intialize all Emanate Cluster related variables
to empty strings when the cluster or local node
wasn't running caused resls to show the cluster
name as an empty string if the local node is halted.
Resolution:
Change was made to initialize all status variables to
empty string when cmsnmpd first starts, independant
of whether the cluster or local node are up or down.
PHSS_26674:
1. Error messages describing local LAN failover failures are
not logged to syslog in a production environment.
Resolution:
Make change such that the error messages are logged to
syslog in a production environment.
2. This is an enhancement request to make the control
script messages easier to read.
Resolution:
The package control script template is updated to
use -p option during fsck on the Journal File Systems.
3. The problem occurs due to SAM GUI code not properly
going through necessary checks.
Resolution:
Fix has been implemented to properly transmit code
checks.
4. This is an expected error when the node is in the
process of reboot or shutdown. However, the error
messages should be more readable.
Resolution:
Changed the error message to the following:
"Unable to obtain the cluster membership;
Node <node-name> may be unreachable."
5. The ServiceGuard unsolicited ARP reply broadcasts are
not sent in rapid intervals after a local switch. This
causes a delay in receiving the ARP reply from network
devices.
Resolution:
The unsolicited ARP replies are now sent every second
during the first ten broadcasts, then the interval
starts increasing exponentially.
6. The package start or halt notification message may fail
to send due to connection abort, but an unexpected reply
message is received while the data associated with the
reply has been cleaned up. Thus a segmentation
violation occurs.
Resolution:
Do not send the reply message if the request
message has failed due to connection abort.
7. cmquerycl in SGOPS generates the configuration ascii
file which has references to DLM. As DLM is obsoleted,
we need to remove the references.
Resolution:
Removed the references to DLM.
8. ServiceGuard does not retry registering a resource if the
EMS monitor returns RM_NOT_READY.
Resolution:
When an EMS monitor returns RM_NOT_READY, keep on trying
to register the resource until the monitor returns
RM_ACCEPT.
9. The control script for a package configured with a
deferred start resource may complete successfully before
the resource is actually registered with EMS. When the
ServiceGuard daemon checks to make sure the resource is
monitored and up, the check will fail and the package
will be halted.
Resolution:
Changed the cmstartres command used in the package
control script to not complete until the resource is
registered with EMS.
10. The cmsetlog command does not accept "RES" as a valid
module.
Resolution:
Fixed cmsetlog to accept "RES" as a valid module and
turn up logging in the resource module appropriately.
11. A coding error in the ServiceGuard daemon shutdown
sequence makes it possible for the daemon to interpret
the unregistering of resource monitor requests to be
unsuccessful even in a successful case. On a
ServiceGuard OPS node, the shutdown sequence must be
clean, otherwise the node will be rebooted (TOC).
Resolution:
Fixed the coding error such that the success of the
unregistering operation is determined correctly.
12. Not a defect. The quorum server is an alternative to
the cluster lock disk. The quorum server is a process
that runs on an HP-UX host that is external to the
cluster. A quorum server may be used in clusters with
any number of nodes, and an individual quorum server
may provide tie-breaking services to as many 50
clusters containing up to a total of 100 nodes.
An HP-UX quorum server may cannot be used for a Linux
cluster, and a Linux quorum server cannot be used for
an HP-UX cluster.
13. There has been some confusion as to whether this feature
is supported. The ServiceGuard lab is now making an
official announcement that it is. Please note that this
feature only works through cmapplyconf on the command
line. Changes are being made to SAM GUI to allow both
online and offline resource addition (JAGae16264).
14. This is actually a DLPI bug. The DLS provider somehow
returns dl_errno as 1, which means bad address, for a
temporary resource shortage. It should return dl_errno
as 4 with unix_errno as ENOBUFS or ENOSR instead so
ServiceGuard could handle this transient problem
accordingly.
Resolution:
A DLPI patch will be released to fix this problem.
The workaround solution in ServiceGuard is to
abort only if we receive the dl_errno 1 too frequently
in a relatively long period of time, which indicates
a permanent, serious problem. Otherwise, the problem
is transient and will be ignored.
15. cmGetstatus() incorrectly uses the number of nodes
the package can run on instead of the number of
nodes in the cluster when validating that each node
the package is configured to run on is actually in
the cluster. The only workaround is to configure
each package to run on only the first P nodes in the
cluster.
Resolution: cmGetstatus() was changed to use the
number of nodes in the cluster when validating
each node that the package can run on.
16. If sending a message to cmsrvassistd fails,
the service sensor can free a pointer twice,
resulting in a segmentation violation.
Resolution: Changed the service sensor to
only free reply messages when the send
succeeded.
17. When a package is to be started, the coordinator node
sends a "start request" to the node that's supposed
to run the package. If the reply to that message
indicates a problem due to an upcoming cluster
formation, then the state of that package was being
reset to "not busy". If another event arrives
before the cluster formation (e.g. a resource becomes
available on the coordinator node), then the package
may be started. However, the original message could
have made it to the node that was supposed to run the
package, so the package could be run on both nodes.
Resolution:
Keep the package state "busy" so nothing else will
happen to the package until the cluster formation
event arrives.
18. An incomplete implementation of a more efficient
method of looking up package parameters in cmviewcl
for 150 packages causes this problem.
Resolution: Complete the implementation for system
multi-node packages.
19. During cluster startup, on each node the Package
Manager thread queues up events on the EMS thread to
register resources with EMS without waiting for the
events to complete. The EMS thread on one node may get
CPU time earlier than the EMS thread on another node, so
at the time nodes are evaluated for package ownership,
resources for a certain package may be registered on an
adoptive node but not on the primary node.
Resolution:
Make the Package Manager thread wait for the EMS thread
to finish registering resources with EMS before carrying
on with other initialization operations.
20. This defect was originally addressed in JAGad93682, the
fix for which was included in PHSS_25124. We are now
backing out the fix for JAGad93682 (when registering
a monitor request, send START/STOP/START to unregister
any lingering request and register a fresh request) and
implementing a more correct solution, namely making sure
that all monitor requests are unregistered with EMS
before cmcld exits.
Resolution:
Make the main daemon thread wait until the EMS thread
finishes unregistering all monitor requests before
deleting the EMS thread and exiting.
PHSS_26180:
1. Not a defect.
2. After command starts cluster successfully, during
cleanup it tries to free some data which may
have already freed creating bus error.
Resolution:
Fix is to free that data as part of cleanup only so
removed intermediate cleanup.
3. The cmcheckconf/cmapplyconf commands tries to contact
EMS resource registar on the remote node where package
was suppose to run and resource is available. But due to
linking problem with EMS toolkit command end up talking
to local node where resource was not available.
Resolution:
Corrected the linking problem of commands with EMS
toolkit.
PHSS_25915:
1. When ServiceGuard is notified that the value for a
resource has changed, it determines that the resource is
down if just one of the RESOURCE_UP_VALUE criteria is
unsatisfied and fails the package.
Resolution:
When a resource changes value, determine the status of
the resource by checking that at least one of the
criteria is met and allow the package to continue to run
if the resource is still considered up.
2. Unused nodes are searched for in the cmprovider's
cluster-related cache, but they are not present in the
cache.
Resolution:
When looking up an individual node in the cmprovider's
cluster-related cache, skip if the node is an unused
node.
3. cmviewconf checks the wrong variable when determining
what value to display for HALT_SCRIPT_TIMEOUT.
Resolution:
Modify cmviewconf to check the correct variable when
determining what value to display for
HALT_SCRIPT_TIMEOUT.
4. While adding package information to the cluster database
on ServiceGuard version 11.13, cmapplyconf tries to get
rid of unused EMS resources. There is a coding error
there which leads to the command failure.
Resolution:
The coding error is fixed and the correct routine is now
called to remove the resources completely from the
cluster database.
5. Multiple commands create multiple transactions in the
queue. When one of the commands is aborted, the
corresponding transaction is also aborted. A lock is
released and a pointer is moved to next transaction. As
the lock is released another thread may come and delete
the next transaction thinking that it has been aborted.
Later when that deleted transaction is referenced, cmcld
dumps core with SIGBUS or SIGSEGV.
Resolution:
The fix is to always go back to the first transaction
when a transaction is aborted and destroy the
transaction. Also make sure that no transaction pointers
are held while the lock is released. Instead, re-lookup
will be done to find the correct transaction.
6. There is an invalid assertion in the code that checks
that all nodes are in a legal state corresponding to the
reply message received from a node. It is asserted that
a state of NO_TRANS is not legal when it is.
Resolution:
The fix was to change the code so that NO_TRANS is
considered a legal state at this point.
PHSS_25124:
1. cmhaltcl does not stop all monitor requests, and when
the cluster is brought up again, monitor requests for
the same resources are sent to the EMS registrar, which
sees them as duplicates of the requests that are still
lingering around and does not send immediate
notifications regarding the states of the resources.
Without knowledge of the resource states, ServiceGuard
cannot start the package.
Resolution:
Send register, unregister then register again to the
EMS registrar to ensure a new monitor request is
registered (the first register is necessary to get
the request ID).
2. The CMProvider failed to remove the node after it was
successfully halted. As a result, the same node was
halted more than one time and depending upon the node's
state, the subsequent halt operation resulted in the
failure.
Resolution:
Remove the node from the list right after the node
is successfully halted.
3. There is a logic error in the cmapplyconf command that
inadvertently allows it to create or update the CDB file
even though a network configuration setup problem has
been detected. This may lead to potential system TOC
when the cluster is started due to loss of heartbeat.
Resolution:
The logic error has been fixed so that the command will
exit out when detecting any networking problem.
4. The "Permission denied to X" error message was no longer
logged at default level so that it never shows up in the
command output.
Resolution:
The log level of the error message has been lowered to
the default level so the message will be visible to
users.
5. In SG, when the cluster is starting or halting on a node,
SG should provide configuration data to api clients from
the disk via cmclconfd. Instead, it was failing.
Resolution:
If cluster is "busy" (starting or halting)
SG now gets configuration data via cmclconfd for its api
clients.
6. The function "cl_delete_event" was freeing the data
memory of an event twice if the event had a
destructor function attached to it. The destructor
would free it and then cl_delete_event would free
the same memory again.
Resolution:
The function "cl_delete_event" was modified to only
free the data of an event if no destructor function
is attached to the event. If a destructor function is
attached, The destructor is responsible for freeing
the data part of the event.
7. Not enough memory preallocation was done for stressful
workloads in cma libraries.
Resolution:
Added cm__alloc_mem in the preallocation to preallocate
256 of extra memory. Fixed split brain detector event
leak(currently sbd is turned off).
8. The package run/halt script performs the volume group
activation/deactivation, fscks and mount/umount for
each file system sequentially. This fix will allow
end-user to specify the number of concurrent vgchange,
fsck or mount/umount during a package startup or
shutdown.
Resolution:
The package control script template was updated to
allow end-user to specify the number of concurrent
volume-group activation or deactivation, fsck and
file system mount or umount. The default is set to 1
to mimic the old behavior.
Following are descriptions of and explanations of
usage of the four new package variables:
CONCURRENT VGCHANGE OPERATIONS
Specify the number of concurrent volume group
activations or deactivations to allow during
package startup or shutdown. Setting this value
to an appropriate number may improve the performance
while activating or deactivating a large number
of volume groups in the package. If the specified
value is less than 1, the script defaults it to 1
and proceeds with a warning message in the package
control script logfile.
CONCURRENT_VGCHANGE_OPERATIONS=1
CONCURRENT DISK GROUP OPERATIONS
Specify the number of concurrent VxVM DG imports
or deports to allow during package startup or
shutdown. Setting this value to an appropriate
number may improve the performance while importing
or deporting a large number of disk groups in the
package. If the specified value is less than 1,
the script defaults it to 1 and proceeds with a
warning message in the package control script logfile.
CONCURRENT_DISKGROUP_OPERATIONS=1
CONCURRENT FSCK OPERATIONS
Specify the number of concurrent fsck to allow
during package startup. Setting this value to
an appropriate number may improve the performance
while checking a large number of file systems in
the package. If the specified value is less than 1,
the script defaults it to 1 and proceeds with a
warning message in the package control script
logfile.
CONCURRENT_FSCK_OPERATIONS=1
CONCURRENT MOUNT AND UMOUNT OPERATIONS
Specify the number of concurrent mounts and
umounts to allow during package startup or
shutdown. Setting this value to an appropriate
number may improve the performance while mounting
or un-mounting a large number of file systems in
the package. If the specified value is less than 1,
the script defaults it to 1 and proceeds with a
warning message in the package control script logfile.
CONCURRENT_MOUNT_AND_UMOUNT_OPERATIONS=1
9. To enforce the length less than 1024, the resource name
length was incorrectly compared with different variable.
Resolution:
The fix is added for correct comparison of resource
name length with MAX_PATH_LENGTH(1024) and package name
length with MAX_NAME_LENGTH(40).
10.When all heartbeat networks goes down and serial device
is configured then node who noticed these failures will
delay himself before going for cluster lock. This will
ensure that if other node is good then it can obtain
the cluster lock and form a one node cluster. But
if other node is down or also delayed then before this
node can acquire cluster lock, safety time can expire
and this node can TOCed. In case of heartbeat network
switch failure both nodes can delay themselves and whole
cluster can fail.
Resolution:
To enforce the delay, more time is spent in FC state.
Very large number of FCs are sent if node notices that
it has serial device and all heartbeat networks are
down. This number of FCs are so huge that if other node
is also delayed or failed then this node will do TOCed
as it does not have enough time to form one node cluster.
The recalculations are done for how many FCs to send so
that the other node has enough time to get the lock and
form one node cluster and if it does not do that then
this node has enough time to form one node cluster.
PHSS_24678:
1. When the cmsnmpd agent is brought up or ServiceGuard
events are generated while the SG daemon, cmcld, is
down, there are several cluster related variables that
are left uninitialized. When the cmsnmpd subagent sends
these uninitialized variables to the SNMP Master agent
(snmpdm), error messages appear in snmpd.log and
can cause the log file to grow quite large.
Resolution:
The cmsnmpd agent usually retrieves cluster
status information by calling the SG API call
cmGetStatus(). This call returns cluster status
information ONLY when cmcld is running and the SG
node is up. When the cluster or node are down,
the cmsnmpd subagent has no way of retrieving
cluster staus information and it sends traps with
unintialized variables to the snmpdm agent. The fix
was to initialize all cluster related variables
when cmsnmpd is first brought up.
2. cmgmsd does not issue a close socket call, causing this
tcp resource leak.
Resolution:
With the changes, cmgmsd will check if there are valid
file descriptors about to close then closes them when
there is a call to cdb_callback_commit().
3. This is an enhancement to ServiceGuard provider. This
feature will enable "ServiceGuard Manager A.02.00" and
later versions to perform Administration features
on ServiceGuard clusters.
Resolution:
Added the admin functionality with changes to the
cmprovider.omp. With this patch along with PHSS_22175
customers can perform cluster administration
from the SGManager GUI.
4. The kernel tuneable for stape reserve/release
functionality, st_ats_enabled, currently defaults to
enabled on 11.0 and 11.i HP-UX systems. In the near
future, this tuneable will be defaulted to disabled.
Currently, ATS does not check the state of this tuneable
before proceeding with shared tape operations.
Resolution:
Added check in shared tape daemon cmtaped that causes
it to treat node has having no ATS tape devices if kernel
tuneable st_ats_enabled is disabled on node. Also added
check in ATS configuration commands to block SG shared
tape configuration if one or more nodes in cluster has
kernel tuneable disabled.
5. When cmquerycl command is issued, one probe (UDP
datagram) is sent on each interface on the querying
node, with the address of the interface as the
datagram's source address, even if the datagram may
be physically routed from another LAN card. The queried
node responds to the first datagram it receives and
drops the subsequent ones. It is possible that the source
address contained in the datagram being responded to is
not accessible from the queried node (e.g. source
address is local to a private subnet of the querying
node), so the reply is lost and cmquerycl on the
querying node eventually times out and fails. With
other SG commands, the same behavior occurs but
the request simply times out after 10 seconds and
the command continues.
Resolution:
Changed to send only one UDP probe using INADDR_ANY to
ensure a valid route between the nodes.
6. The cmapplyconf command gets internal error when adding
a node to a cluster. This happens because one cmclconfd
is updating the configuration file while another
cmclconfd is trying to read the configuration file.
Prior to release A.11.13 these operations were done
synchronously.
Resolution:
The basic problem was that the cmclconfd that was
reading the configuration file would either fail or
only read part of the configuration file when it was
being updated by another cmclconfd. The fix was to stat
the configuration file open and read it, and stat it
again. We continue this sequence until
bytes_read == pre stat size == post stat size.
When all are equal the function cf_local_file_to_mem
returns success and provided the correct configuration
file was read the cmapplyconf succeeds.
7. When a node joins cluster, ServiceGuard checks to
see if any package needs to be moved back to its
primary node. If the package uses CVM disk groups,
it depends on the VxVM-CVM-pkg to be running. However,
the VxVM-CVM-pkg will be starting, not running at this
time. When VxVM-CVM-pkg moves to running state, a
routine is called to start dependents. That routine
did not check to see if any dependent needed to be
moved back to its primary node.
Resolution:
Added check for AUTO_FAILBACK in the function
start_dependents.
8. The ServiceGuard config daemon cmclconfd passes an array
that contains physical volume names to an LVM
library function while trying to detach physical
volume groups during the device query process of
cmcheckconf/cmapplyconf. Later on, cmclconfd frees the
memory allocated for the array but the LVM library keeps
using it. This leads to memory corruption which results
in LVM detaching from an incorrect list of physical
volumes and therefore failure to release the volume
group. A side effect of this problem is the failure to
initialize the cluster lock properly in some
circumstances.
Resolution:
Make change so that LVM library makes a copy
of the physical volume data rather than use a pointer
to the existing data.
9. During a kernel hang, the remote nodes time out the
delayed node and form a cluster. Once the delayed node
resumes execution, a logic error within ServiceGuard
allows it to form a separate 1-node cluster.
Resolution:
The logical error has been fixed and some
more assertions are added at a later part of the cluster
reformation to ensure that from a cluster of 3 or more
nodes, one node does not form a separate cluster.
10. During multiple cluster reformations, ServiceGuard may
erroneously clear the cluster lock, allowing 2 clusters
to form.
Resolution:
A fix is added to ensure that the cluster
lock does not get erroneously cleared. Also at a later
part of the cluster reformation, some assertions are
added to ensure that the cluster lock is still held.
Enhancement:
Yes
PHSS_27722:
This patch delivers new functionality for logging the
audit messages into the syslog.log for the admin
operations.
This patch delivers new functionality for including the
quorum server and its parameters in the cmviewconf command.
PHSS_27087:
This patch delivers new functionality for package control
script to do parallel fsck and umount. For this purpose
variables FS_UMOUNT_OPT FS_FSCK_OPT and FS_TYPE are added
to package control script. The comment section of package
control script describes use of these variables.
PHSS_26928:
New syslog messages logged when the PACKAGE
environment variable specifies a package name
that cannot be found in the configuration.
PHSS_26674:
More error messages are logged to syslog in a
production environment. The package control script
template is updated to use -p option during fsck
on the Journal File Systems. cmsetlog now accepts
"RES" as a valid module.
SR:
8606199378 8606207880 8606215545 8606215621 8606209075
8606222969 8606214965 8606212693 8606219681 8606200990
8606158555 8606140550 8606178310 4701391482 8606217091
8606220905 8606221218 8606224594 8606224615 8606222631
8606221920 8606207035 8606226503 8606225932 8606226894
8606225203 8606223632 8606229487 8606208524 8606220084
8606231688 8606233054 8606230826 8606229591 8606233943
8606236658 8606237504 8606232772 8606238968 8606227696
8606238957 8606244429 8606250049 8606229966 8606241953
8606242718 8606237295 8606229495 8606251204 8606245169
8606248970 8606234353 8606245185 8606232614 8606246814
8606249108 8606251394 8606231669 8606249878 8606248834
8606251434 8606251633 8606248845 8606232561 8606254986
8606247612 8606249052 8606244410 8606257766 8606251320
8606254001 8606255032 8606259876 8606256716 8606260131
8606262131 8606233259 8606244305 8606260489 8606249878
8606264328 8606268205 8606261124 8606247648 8606258432
8606242547 8606256106 8606256331 8606208266 8606264135
8606255339 8606272001 8606260426 8606214892 8606280988
8606271637 8606261781 8606278861 8606278820 8606269861
8606283230 8606267626 8606280203 8606269037 8606281709
8606281543 8606269292 8606287005 8606284273 8606289077
8606283370 8606282343 8606287690
Patch Files:
DLM-Pkg-Mgr.CM-PKG,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP:
Package-Manager.CM-PKG,fr=A.11.13,fa=HP-UX_B.11.00_32/64,
v=HP:
/usr/lbin/cm/C/CMpack.ou
/usr/lbin/cm/C/CMpackadmin.ui
/usr/lbin/cm/C/CMpackconf.ui
/usr/lib/libcmpkg.1
/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
DLM-Clust-Mon.CM-CORE,fr=A.11.13,fa=HP-UX_B.11.00_32/64,
v=HP:
Cluster-Monitor.CM-CORE,fr=A.11.13,fa=HP-UX_B.11.00_32/64,
v=HP:
/sbin/init.d/cmcluster
/usr/contrib/bin/cmsetlog
/usr/contrib/bin/cmsetsafety
/usr/contrib/bin/get_sn
/usr/contrib/bin/sscnfmtr
/usr/lbin/cm/C/CMcore.ou
/usr/lbin/cm/C/CMcoreadmin.ui
/usr/lbin/cm/C/CMcoreconf.ui
/usr/lbin/cmclconfd
/usr/lbin/cmcld
/usr/lbin/cmlogd
/usr/lbin/cmlvmd
/usr/lbin/cmsnmpd
/usr/lbin/cmsrvassistd
/usr/lbin/cmui
/usr/lib/libcmcore.1
/usr/lib/libcmcore.sl
/usr/lib/libcmdlm.sl
/usr/lib/libcmpkg.sl
/usr/lib/libcmres.1
/usr/lib/libcmres.sl
/usr/lib/libsgcl.2
/usr/lib/libsgcl.sl
/usr/newconfig/usr/lib/libcmdlm.1
/usr/newconfig/usr/lib/libcmpkg.1
/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/cmscancl
/usr/sbin/cmviewcl
/usr/sbin/cmviewconf
/usr/sbin/convert
DLM-Clust-Mon.CM-CORE-MAN,fr=A.11.13,fa=HP-UX_B.11.00_32/64,
v=HP:
Cluster-Monitor.CM-CORE-MAN,fr=A.11.13,
fa=HP-UX_B.11.00_32/64,v=HP:
/usr/share/man/man1m.Z/cmapplyconf.1m
/usr/share/man/man1m.Z/cmcheckconf.1m
/usr/share/man/man1m.Z/cmquerycl.1m
/usr/share/man/man1m.Z/cmviewcl.1m
DLM-NMAPI.CM-NMAPI,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/nmapi/8.0/lib/libnmapi_32.a
/opt/nmapi/8.0/lib/libnmapi_64.a
/opt/nmapi/nmapi2/lib/libnmapi2.1
/opt/nmapi/nmapi2/lib/libnmapi2.sl
/opt/nmapi/nmapi2/lib/pa20_64/libnmapi2.1
/opt/nmapi/nmapi2/lib/pa20_64/libnmapi2.sl
/usr/contrib/bin/gmsetlog
/usr/lbin/cmgmsd
/usr/lib/libcmdlm.1
/usr/lib/libcmdlm.dlm.1
DLM-ATS-Core.ATS-RUN,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP:
ATS-CORE.ATS-RUN,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP:
/etc/cmcluster/sharedtape/ats_tapelibs
/usr/lbin/cmtaped
/usr/sbin/stapplyconf
/usr/sbin/stcheckconf
/usr/sbin/stdeleteconf
/usr/sbin/stdisplay
/usr/sbin/stgetconf
/usr/sbin/stquerycl
/usr/sbin/streclaim
/usr/sbin/stsetlog
/usr/sbin/stviewcl
DLM-Prov-MOF.CM-MOF,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP:
CM-Provider-MOF.CM-MOF,fr=A.11.13,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/cmom/mof/CMcluster.mof
/opt/cmom/mof/CMnetwork.mof
/opt/cmom/mof/EMScore.mof
/opt/cmom/mof/QSquorumserver.mof
/opt/cmom/mof/SGcluster.mof
/opt/cmom/mof/SGincarnationevent.mof
/opt/cmom/mof/SGnetwork.mof
/opt/cmom/mof/SGpackage.mof
/opt/cmom/mof/SGquorumserver.mof
DLM-Prov-MOF.CM-PROVIDER,fr=A.11.13,fa=HP-UX_B.11.00_32/64,
v=HP:
CM-Provider-MOF.CM-PROVIDER,fr=A.11.13,
fa=HP-UX_B.11.00_32/64,v=HP:
/opt/cmom/providers/cmprovider.omp
/opt/cmom/providers/qsprovider.omp
what(1) Output:
DLM-Pkg-Mgr.CM-PKG,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/lbin/cm/C/CMpack.ou:
RCS $Header: CMpack.ou,v 82.2 98/10/19 19:13:55 ssa
Exp $
/usr/lbin/cm/C/CMpackadmin.ui:
$Revision: 82.2 $
/usr/lbin/cm/C/CMpackconf.ui:
$Revision: 82.2 $
/usr/lib/libcmpkg.1:
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
MC/ServiceGuard Product $Revision: 82.2 $
/usr/sbin/cmhaltpkg:
Build date: Thu Feb 27 12:53:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmhaltserv:
Build date: Thu Feb 27 12:53:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmmakepkg:
Build date: Thu Feb 27 12:53:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmmigrate:
Build date: Thu Feb 27 12:53:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmmodnet:
Build date: Thu Feb 27 12:53:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmmodpkg:
Build date: Thu Feb 27 12:53:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmrunpkg:
Build date: Thu Feb 27 12:53:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmrunserv:
Build date: Thu Feb 27 12:53:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmstartres:
Build date: Thu Feb 27 12:53:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmstopres:
Build date: Thu Feb 27 12:53:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
DLM-Clust-Mon.CM-CORE,fr=A.11.13,fa=HP-UX_B.11.00_32/64,
v=HP:
/sbin/init.d/cmcluster:
$Revision: 82.2 $
/usr/contrib/bin/cmsetlog:
Build date: Thu Feb 27 12:53:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Commands
Command Cln
Command Srv
Config
Local Comm
Util
/usr/contrib/bin/cmsetsafety:
Build date: Thu Feb 27 12:53:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Commands
Command Cln
Command Srv
Config
Local Comm
Util
/usr/contrib/bin/get_sn:
get_sn Revision 1.7
/usr/contrib/bin/sscnfmtr:
sscnfmtr Revision 1.1
Tools
/usr/lbin/cm/C/CMcore.ou:
None
/usr/lbin/cm/C/CMcoreadmin.ui:
$Revision: 82.2 $
/usr/lbin/cm/C/CMcoreconf.ui:
$Revision: 82.2 $
/usr/lbin/cmclconfd:
HP92453-02A.10.20 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
Build date: Thu Feb 27 12:51:23 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
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 Feb 27 12:52:52 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Daemon
Config DB
Cluster Monitor
Command Srv
CommunicationSrv
Config
Dlm
Local Comm
Network Sensor
Package Manager
Remote Comm
Quorum Module
API
Service Sensor
Cluster LVM
Status DB
Sync
Util
/usr/lbin/cmlogd:
Build date: Thu Feb 27 12:52:52 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Log Daemon
Local Comm
Util
/usr/lbin/cmlvmd:
HP92453-02A.10.20 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
Build date: Thu Feb 27 12:48:50 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Cluster LVM
Local Comm
Util
/usr/lbin/cmsnmpd:
Build date: Thu Feb 27 12:55:18 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
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 Feb 27 12:48:14 PST 2003
Build id: ibld_sgops_a1113patch
/usr/lbin/cmui:
HP92453-02A.10.20 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
GUI
Config
Command Cln
Command Utils
Local Comm
Util
/usr/lib/libcmcore.1:
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Cluster Monitor Product $Revision: 82.2 $
/usr/lib/libcmcore.sl:
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Cluster Monitor Product $Revision: 82.2 $
/usr/lib/libcmdlm.sl:
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
ServiceGuard OPS Edition Product $Revision: 82.2 $
/usr/lib/libcmpkg.sl:
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
MC/ServiceGuard Product $Revision: 82.2 $
/usr/lib/libcmres.1:
MC/ServiceGuard Resource Lib $Revision: 82.2 $
/usr/lib/libcmres.sl:
MC/ServiceGuard Resource Lib $Revision: 82.2 $
/usr/lib/libsgcl.2:
None
/usr/lib/libsgcl.sl:
None
/usr/newconfig/usr/lib/libcmdlm.1:
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Cluster Monitor Product Only $Revision: 82.2 $
/usr/newconfig/usr/lib/libcmpkg.1:
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Cluster Monitor Product Only $Revision: 82.2 $
/usr/sbin/cmapplyconf:
Build date: Thu Feb 27 12:53:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmcheckconf:
Build date: Thu Feb 27 12:53:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmdeleteconf:
Build date: Thu Feb 27 12:53:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmgetconf:
Build date: Thu Feb 27 12:53:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmhaltcl:
Build date: Thu Feb 27 12:53:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmhaltnode:
Build date: Thu Feb 27 12:53:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmquerycl:
Build date: Thu Feb 27 12:53:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmruncl:
Build date: Thu Feb 27 12:53:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmrunnode:
Build date: Thu Feb 27 12:53:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmscancl:
None
/usr/sbin/cmviewcl:
Build date: Thu Feb 27 12:53:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmviewconf:
Build date: Thu Feb 27 12:55:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Tools
/usr/sbin/convert:
Build date: Thu Feb 27 12:55:30 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Tools
DLM-Clust-Mon.CM-CORE-MAN,fr=A.11.13,fa=HP-UX_B.11.00_32/64,
v=HP:
/usr/share/man/man1m.Z/cmapplyconf.1m:
None
/usr/share/man/man1m.Z/cmcheckconf.1m:
None
/usr/share/man/man1m.Z/cmquerycl.1m:
None
/usr/share/man/man1m.Z/cmviewcl.1m:
None
DLM-NMAPI.CM-NMAPI,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/nmapi/8.0/lib/libnmapi_32.a:
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Local Comm
Config
API
Util
/opt/nmapi/8.0/lib/libnmapi_64.a:
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
Local Comm
Config
API
Util
/opt/nmapi/nmapi2/lib/libnmapi2.1:
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
NMAPI2 32
GMAPI 32
Build date: Thu Feb 27 12:58:42 PST 2003
Build id: ibld_sgops_a1113patch
/opt/nmapi/nmapi2/lib/libnmapi2.sl:
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
NMAPI2 32
GMAPI 32
Build date: Thu Feb 27 12:58:42 PST 2003
Build id: ibld_sgops_a1113patch
/opt/nmapi/nmapi2/lib/pa20_64/libnmapi2.1:
Build date: Thu Feb 27 13:02:26 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
NMAPI2 64
GMAPI 64
/opt/nmapi/nmapi2/lib/pa20_64/libnmapi2.sl:
Build date: Thu Feb 27 13:02:26 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
NMAPI2 64
GMAPI 64
/usr/contrib/bin/gmsetlog:
HP92453-02A.10.20 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
Build date: Thu Feb 27 12:58:25 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
GMAPI 32
/usr/lbin/cmgmsd:
HP92453-02A.10.20 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
Build date: Thu Feb 27 12:58:18 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
/usr/lib/libcmdlm.1:
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
ServiceGuard OPS Edition Product $Revision: 82.2 $
/usr/lib/libcmdlm.dlm.1:
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
ServiceGuard OPS Edition Product $Revision: 82.2 $
DLM-ATS-Core.ATS-RUN,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP:
/etc/cmcluster/sharedtape/ats_tapelibs:
Advanced Tape Services A.11.09
/usr/lbin/cmtaped:
HP92453-02A.10.20 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
Advanced Tape Support daemon
Build date: Thu Feb 27 12:56:11 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
ATS Headers
API
Config DB
CommunicationSrv
Config
Local Comm
Util
/usr/sbin/stapplyconf:
Advanced Tape Support commands
Build date: Thu Feb 27 12:56:49 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
ATS Headers
ATS Utils
Command Cln
Command Srv
Command Utils
Config
Local Comm
Util
/usr/sbin/stcheckconf:
Advanced Tape Support commands
Build date: Thu Feb 27 12:56:49 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
ATS Headers
ATS Utils
Command Cln
Command Srv
Command Utils
Config
Local Comm
Util
/usr/sbin/stdeleteconf:
Advanced Tape Support commands
Build date: Thu Feb 27 12:56:49 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
ATS Headers
ATS Utils
Command Cln
Command Srv
Command Utils
Config
Local Comm
Util
/usr/sbin/stdisplay:
HP92453-02A.10.20 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
/usr/sbin/stgetconf:
Advanced Tape Support commands
Build date: Thu Feb 27 12:56:49 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
ATS Headers
ATS Utils
Command Cln
Command Srv
Command Utils
Config
Local Comm
Util
/usr/sbin/stquerycl:
Advanced Tape Support commands
Build date: Thu Feb 27 12:56:49 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
ATS Headers
ATS Utils
Command Cln
Command Srv
Command Utils
Config
Local Comm
Util
/usr/sbin/streclaim:
Advanced Tape Support commands
Build date: Thu Feb 27 12:56:49 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
ATS Headers
ATS Utils
Command Cln
Command Srv
Command Utils
Config
Local Comm
Util
/usr/sbin/stsetlog:
Advanced Tape Support commands
Build date: Thu Feb 27 12:56:49 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
ATS Headers
ATS Utils
Command Cln
Command Srv
Command Utils
Config
Local Comm
Util
/usr/sbin/stviewcl:
Advanced Tape Support commands
Build date: Thu Feb 27 12:56:49 PST 2003
Build id: ibld_sgops_a1113patch
A.11.13 Date: 1/17/2003; PATCH: PHSS_27722
ATS Headers
ATS Utils
Command Cln
Command Srv
Command Utils
Config
Local Comm
Util
DLM-Prov-MOF.CM-MOF,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/cmom/mof/CMcluster.mof:
ServiceGuard Schema 1.3.1
/opt/cmom/mof/CMnetwork.mof:
ServiceGuard Schema 1.3.1
/opt/cmom/mof/EMScore.mof:
ServiceGuard Schema 1.3.1
/opt/cmom/mof/QSquorumserver.mof:
None
/opt/cmom/mof/SGcluster.mof:
ServiceGuard Schema 1.3.1
/opt/cmom/mof/SGincarnationevent.mof:
ServiceGuard Schema 1.3.1
/opt/cmom/mof/SGnetwork.mof:
ServiceGuard Schema 1.3.1
/opt/cmom/mof/SGpackage.mof:
ServiceGuard Schema 1.3.1
/opt/cmom/mof/SGquorumserver.mof:
ServiceGuard Schema 1.3.1
DLM-Prov-MOF.CM-PROVIDER,fr=A.11.13,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 $
Product Name: HP Cluster Object Manager
Version: A.01.03.01
Patch Name: PHSS_26675
Cluster Management Provider Library
Serviceguard Schema 1.3.1
Build date: Thu Feb 27 13:01:36 PST 2003
Build id: ibld_sgops_a1113patch
/opt/cmom/providers/qsprovider.omp:
Build date: Thu Feb 27 13:01:51 PST 2003
Build id: ibld_sgops_a1113patch
cksum(1) Output:
DLM-Pkg-Mgr.CM-PKG,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP:
931382500 622 /usr/lbin/cm/C/CMpack.ou
1779608406 65684 /usr/lbin/cm/C/CMpackadmin.ui
3998340222 65789 /usr/lbin/cm/C/CMpackconf.ui
3559103172 12288 /usr/lib/libcmpkg.1
4289071559 2457600 /usr/sbin/cmhaltpkg
4289071559 2457600 /usr/sbin/cmhaltserv
4289071559 2457600 /usr/sbin/cmmakepkg
4289071559 2457600 /usr/sbin/cmmigrate
4289071559 2457600 /usr/sbin/cmmodnet
4289071559 2457600 /usr/sbin/cmmodpkg
4289071559 2457600 /usr/sbin/cmrunpkg
4289071559 2457600 /usr/sbin/cmrunserv
4289071559 2457600 /usr/sbin/cmstartres
4289071559 2457600 /usr/sbin/cmstopres
DLM-Clust-Mon.CM-CORE,fr=A.11.13,fa=HP-UX_B.11.00_32/64,
v=HP:
873785469 7868 /sbin/init.d/cmcluster
3952986743 1134592 /usr/contrib/bin/cmsetlog
3952986743 1134592 /usr/contrib/bin/cmsetsafety
1301330158 65536 /usr/contrib/bin/get_sn
1448834642 53248 /usr/contrib/bin/sscnfmtr
1204333406 547 /usr/lbin/cm/C/CMcore.ou
1864590287 67664 /usr/lbin/cm/C/CMcoreadmin.ui
2726478983 67424 /usr/lbin/cm/C/CMcoreconf.ui
1853364095 1447632 /usr/lbin/cmclconfd
81568464 3462864 /usr/lbin/cmcld
41463606 180224 /usr/lbin/cmlogd
3254709752 1029840 /usr/lbin/cmlvmd
3508225439 2179072 /usr/lbin/cmsnmpd
2785591557 198352 /usr/lbin/cmsrvassistd
3583913579 3294928 /usr/lbin/cmui
1998633412 12288 /usr/lib/libcmcore.1
1998633412 12288 /usr/lib/libcmcore.sl
2459020395 12288 /usr/lib/libcmdlm.sl
3559103172 12288 /usr/lib/libcmpkg.sl
2989553038 12288 /usr/lib/libcmres.1
2989553038 12288 /usr/lib/libcmres.sl
2794852951 479232 /usr/lib/libsgcl.2
2794852951 479232 /usr/lib/libsgcl.sl
1837847798 12288 /usr/newconfig/usr/lib/libcmdlm.1
1053532106 12288 /usr/newconfig/usr/lib/libcmpkg.1
4289071559 2457600 /usr/sbin/cmapplyconf
4289071559 2457600 /usr/sbin/cmcheckconf
4289071559 2457600 /usr/sbin/cmdeleteconf
4289071559 2457600 /usr/sbin/cmgetconf
4289071559 2457600 /usr/sbin/cmhaltcl
4289071559 2457600 /usr/sbin/cmhaltnode
4289071559 2457600 /usr/sbin/cmquerycl
4289071559 2457600 /usr/sbin/cmruncl
4289071559 2457600 /usr/sbin/cmrunnode
1867742789 17221 /usr/sbin/cmscancl
4289071559 2457600 /usr/sbin/cmviewcl
3629006061 1814528 /usr/sbin/cmviewconf
2958720936 1880064 /usr/sbin/convert
DLM-Clust-Mon.CM-CORE-MAN,fr=A.11.13,fa=HP-UX_B.11.00_32/64,
v=HP:
653565006 4928 /usr/share/man/man1m.Z/cmapplyconf.1m
2392445717 2996 /usr/share/man/man1m.Z/cmcheckconf.1m
838261007 18329 /usr/share/man/man1m.Z/cmquerycl.1m
3231004894 7687 /usr/share/man/man1m.Z/cmviewcl.1m
DLM-NMAPI.CM-NMAPI,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP:
2627175398 2311076 /opt/nmapi/8.0/lib/libnmapi_32.a
1455084998 1659654 /opt/nmapi/8.0/lib/libnmapi_64.a
2071051007 266240 /opt/nmapi/nmapi2/lib/libnmapi2.1
2071051007 266240 /opt/nmapi/nmapi2/lib/libnmapi2.sl
748609243 145872 /opt/nmapi/nmapi2/lib/pa20_64/libnmapi2.1
748609243 145872 /opt/nmapi/nmapi2/lib/pa20_64/libnmapi2.sl
421561969 177872 /usr/contrib/bin/gmsetlog
500812388 1062608 /usr/lbin/cmgmsd
2459020395 12288 /usr/lib/libcmdlm.1
2459020395 12288 /usr/lib/libcmdlm.dlm.1
DLM-ATS-Core.ATS-RUN,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP:
272811593 595 /etc/cmcluster/sharedtape/ats_tapelibs
189800231 1111760 /usr/lbin/cmtaped
3441418042 2215936 /usr/sbin/stapplyconf
3441418042 2215936 /usr/sbin/stcheckconf
3441418042 2215936 /usr/sbin/stdeleteconf
1912479668 79568 /usr/sbin/stdisplay
3441418042 2215936 /usr/sbin/stgetconf
3441418042 2215936 /usr/sbin/stquerycl
3441418042 2215936 /usr/sbin/streclaim
3441418042 2215936 /usr/sbin/stsetlog
3441418042 2215936 /usr/sbin/stviewcl
DLM-Prov-MOF.CM-MOF,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP:
3151552603 16681 /opt/cmom/mof/CMcluster.mof
3180290089 10790 /opt/cmom/mof/CMnetwork.mof
452118744 685 /opt/cmom/mof/EMScore.mof
3920192188 738 /opt/cmom/mof/QSquorumserver.mof
385207907 11821 /opt/cmom/mof/SGcluster.mof
3347974820 4882 /opt/cmom/mof/SGincarnationevent.mof
1220999373 2473 /opt/cmom/mof/SGnetwork.mof
881627924 21084 /opt/cmom/mof/SGpackage.mof
3252401630 3155 /opt/cmom/mof/SGquorumserver.mof
DLM-Prov-MOF.CM-PROVIDER,fr=A.11.13,fa=HP-UX_B.11.00_32/64,
v=HP:
1179195789 2969600 /opt/cmom/providers/cmprovider.omp
1557758394 32768 /opt/cmom/providers/qsprovider.omp
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_24678 PHSS_25124 PHSS_25915 PHSS_26180 PHSS_26674 PHSS_26928
PHSS_27087
Equivalent Patches: None
Patch Package Size: 34050 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_27722
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_27722.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_27722. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_27722.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_27722.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_27722.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
For ServiceGuard OPS Edition Clusters using OPS 8.0.6,
do the following:
1) Halt the cluster.
2) Install this patch on all nodes.
3) Relink Oracle applications on all nodes.
4) On all nodes, add this new line to the Oracle
initialization file (usually named init.ora) as
follows:
ogms_home=/var/opt/ogms
5) Start the cluster and OPS.
For ServiceGuard OPS Edition Clusters using OPS 8.1.6 or
higher do the following:
1) Halt OPS and ServiceGuard on the node the patch is to
be installed on.
2) Install this patch on that node.
3) Restart ServiceGuard and OPS on that node.
4) Patch needs to be installed on all nodes in the
cluster.
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.
For customers using PHSS_26180 or later who have set
MAX_CONFIGURED_PKGS to be a value greater than 60 packages,
the following procedure must be used when upgrading to
SG 11.14:
1) Set AUTOSTART_CMCLD to 0 in /etc/rc.config.d/cmcluster
2) Halt ServiceGuard (cmhaltnode)
3) Upgrade this node to ServiceGuard or SG-OPS Edition 11.14
4) Install 11.14 SG and SG-OPS Patch PHSS_26056 or later to
obtain > 60 package support on 11.14
5) Restart the node (cmrunnode)
6) Modify /etc/rc.config.d/cmcluster to have the desired
AUTOSTART_CMCLD value set
7) Repeat for all nodes in the cluster.
SR#: 8606215545
Cluster Object Manager patch PHSS_22175 or later must
be installed in addition to PHSS_25915 or later in order to
use the Administration features of ServiceGuard Manager
version A.02.00.
If installing PHSS_26674 or later on a ServiceGuard cluster
with PHSS_26180 or earlier installed, do the following:
1) Kill all EMS monitors (e.g. diskmond, mibmond, etc) on
each node before starting ServiceGuard on that node.
For quorum server A.01.00, visit http://www.software.hp.com
for information on installation and documentation:
1) Go to http://www.software.hp.com
2) Click on "high availability"
3) Click on "mc/serviceguard quorum server for hp-ux"
-----End of Document ID: PHSS_27722------------------------------------------
Document ID: PHKL_28513
Date Loaded: 20030311
Title: s700_800 11.11 SCSI IO Cumulative Patch
Patch Name: PHKL_28513
Patch Description: s700_800 11.11 SCSI IO Cumulative Patch
Creation Date: 03/01/27
Post Date: 03/03/11
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
ProgSupport.C-INC,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_28513: PANIC CORRUPTION
PHKL_28096: HANG
PHKL_27579: PANIC HANG
PHKL_27563: HANG
PHKL_26519: PANIC HANG
PHKL_25896: ABORT HANG
PHKL_25509: HANG
PHKL_25165: OTHER PANIC HANG
Boot and ioscan time is improved on large
configurations.
Enhancements are made to support c8xx ioctl's.
PHKL_23313: PANIC HANG CORRUPTION MEMORY_LEAK
PHKL_24441: PANIC HANG
Category Tags:
defect_repair hardware_enablement enhancement
general_release critical panic halts_system corruption
memory_leak
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_28513
Symptoms:
PHKL_28513:
( SR:8606226043 CR:JAGad95114 )
Data integrity issues or HPMC with Channel B of A5159A and
Core I/O FWD SCSI HBA on the following systems:
rp24xx (A-class), rp54xx (L-class), rp7400 (N-class).
Description field in ioscan output for affected Core I/O
FWD SCSI cards will contain string 'C87x'.
( SR:8606286272 CR:JAGae50215 )
SCSI controllers with 896 chip(revision 4) under certain
circumstances may send wrong data on the SCSI bus after
a bus reset.
( SR:8606289589 CR:JAGae53519 )
Panic in SCSI stack with the following trace:
panic+0x14
wait_for_lock+0x2cc
call_wait_for_lock+0x20
scsi_start+0x50
scsi_free_scb+0xac
scsi_strategy_real+0xcd4
ioforw_sched+0xa4
scsi_cmd+0x3a4
scsi_probe+0x444
parallel_scsi_probe+0x1b4
wsio_probe+0xe0
wsio_find_it+0x34
wsio_scan+0x70
gio_scan_subtree+0x188
gio_scan_subtree+0x1c4
gio_scan_subtree+0x1c4
gio_scan_subtree+0x1c4
gio_scan_subtree+0x1c4
gio_scan_subtree+0x1c4
io_scan+0x9c
do_io_scan+0x48
dev_config_ioctl+0xd8
spubind_cdev_ioctl+0x94
spec_ioctl+0xac
vno_ioctl+0x90
ioctl+0x1f4
syscall+0x28c
$syscallrtn+0x0
PHKL_28096:
( SR:8606271035 CR:JAGae35271 )
In a mirrored disk environment on rp8400/rp7410
systems, if one of the internal disks fails and
is hot-swapped, the alternate disk does not
spin up, thus resulting in an application hang.
PHKL_27579:
( SR:8606245156 CR:JAGae11630 )
The system will HPMC when a bus reset occurs
on an A5838A SCSI HBA.
( SR:8606242143 CR:JAGae09397 )
The system may experience intermittent bus
hangs followed by resets on the ports of the
A5159A card and Core I/O FWD SCSI HBA
on the following systems: rp24xx (A-class),
rp54xx (L-class), rp7400 (N-class), rp8400,
when connected to a disk enclosure.
( SR:8606241873 CR:JAGae09130 )
The ioscan may hang and on the following reboot
the system panics with a stack trace that is
not consistent.
( SR:8606216118 CR:JAGad85288 )
When the SCSI bus is being opened, if an
interrupt is serviced at the same time, the
system panics with the following stack trace:
panic+0x14
report_trap_or_int_and_panic+0x84
interrupt+0x1d4
$ihndlr_rtn+0x0
c720_isr+0x890
sapic_interrupt+0x2c
mp_ext_interrupt+0x318
ivti_patch_to_nop3+0x0
bz_pre_sl_loop+0x4
c720_if_bus_open+0x318
scsi_lun_open+0x12d4
sctl_open+0x24
scsi_probe+0x370
parallel_scsi_probe+0x1a8
wsio_probe+0xe0
wsio_find_it+0x34
wsio_scan+0x70
gio_scan_subtree+0x188
gio_scan_subtree+0x1c4
gio_scan_subtree+0x1c4
io_scan+0x9c
do_io_scan+0x48
dev_config_ioctl+0xd8
spubind_cdev_ioctl+0x94
spec_ioctl+0xac
vno_ioctl+0x90
ioctl+0x1f4
syscall+0x480
$syscallrtn+0x0
( SR:8606257328 CR:JAGae21633 )
Application may hang after an OLAR card resume
operation if the card has been suspended while
a SCSI bus reset was in progress.
( SR:8606204859 CR:JAGad74037 )
SCSI driver can not communicate with the target
(nCipher encryption device) that initiates speed
and width negotiation. This results in parity
errors on the SCSI bus and as a result SCSI bus
resets.
( SR:8606232873 CR:JAGae02101 )
I/O errors may occur when attempting to do more
than one backup on tape.
( SR:8606238711 CR:JAGae07734 )
LVM is not switching to an alternate path
due to an error returned by the SCSI driver.
( SR:8606264850 CR:JAGae29181 )
open() on CDROM drive takes too long when no
CD is present.
PHKL_27563:
( SR:8606265990 CR:JAGae30243 )
I/O hang due to a pending I/O request in the lun disk
queue.
PHKL_26519:
( SR:8606236118 CR:JAGae05183 )
When an LVM I/O request to a SCSI device fails or times out,
any subsequent failed I/O requests to same LUN are returned
with error without being retried by the SCSI disk driver.
( SR:8606226361 CR:JAGad95431 )
Applications may hang due to incorrect SCSI error handling
introduced in patch PHKL_24441.
( SR:8606135832 CR:JAGad04964 )
Enhancement: This product update enables the support for 16
byte CDBs (Command Descriptor Block) in the SCSI driver.
( SR:8606214047 CR:JAGad83238 )
The system may experience a HPMC when a SCSI adapter is
suspended through use of the OLA/R functions accessible
through rad(1M) and sam(1M).
( SR:8606236116 CR:JAGae05181 )
When PHKL_24441 is installed and LVM is trying to switch
from the primary path to an alternate path, the SCSI
subsystem may report false read errors to LVM.
PHKL_25896:
( SR:8606228002 CR:JAGad97060 )
Some disks report a capacity of zero bytes at cold boot or
cold install. This causes the initial boot or install after
a cold start to fail.
PHKL_25509:
( SR:8606203627 CR:JAGad72800 )
There is no way to turn off c720 interface driver
vmunix: scb->cdb: %x %x %x %x %x %x
messages in syslog.log, while other related messages can be
suppressed.
( SR:8606186960 CR:JAGad56170 )
A high number of
SCSI: asense data-done -- lbolt %d, dev: %x, tag: %x
messages may be logged in syslog.log when using Plasmon
optical drives.
( SR:8606201476 CR:JAGad70652 )
The following informative message on the console and in
syslog.log causes unnecessarily alarm by customers:
SCSI: Attempt to access partially open device -- dev: %x
( SR:8606199892 CR:JAGad69078 )
On HP SureStore E Disk Array 12 (A3586A), processes can hang
with the following message in the syslog.log:
Device violation of Contingent Allegiance
( SR:8606194472 CR:JAGad63680 )
On workstation model C3700, the external narrow SCSI bus is
setup incorrectly. The 'diskinfo' command returns invalid
information and I/O's on this bus hang.
( SR:8606177456 CR:JAGad46688 )
It takes an unreasonable amount of time to import Disk
Groups with the VxVM volume manager on a FC60 array.
PHKL_25165:
( SR:8606207855 CR:JAGad77032 )
The ioctl system call returns invalid values if called with
SIOC_GET_TGT_LIMITS or SIOC_GET_TGT_PARMS parameters for a
SCSI device controlled by the c8xx driver.
( SR:8606170140 CR:JAGad39404 )
Well functionning systems with Fibre Channel devices
generate an excessive number of logs. This causes log files
cluttering, diag2 daemon overrun or /var filesystem free
space exhaustion.
( SR:8606172682 CR:JAGad41942 )
With the per lun queue depth feature, queue depth
modification on a lun that does not support tag queueing is
not rejected, even though the queue depth on such a device
cannot be modified.
Queue depth can be changed only once on devices supporting
tag queueing.
( SR:8606166652 CR:JAGad35939 )
If an application uses the sctl/ioctl passthrough interface
with the read/write data size mismatching the buffer size,
the system experiences a Data Page Fault panic with the
following routines on the stack:
panic+0x14
report_trap_or_int_and_panic+0x4c
interrupt+0x1e8
$ihndlr_rtn+0x0
lbcopy_pcxu_method+0xc
privlbcopy+0x1c
( SR:8606192639 CR:JAGad61851 )
The system boot time and ioscan command (without -k option)
time are too long, especially in a system with a large Fibre
Channel Array configuration.
( SR:8606189054 CR:JAGad58270 )
If many processes access the same bus, some processes might
become unkillable. This error condition has been experienced
only on systems with a hundred or more luns on the same bus.
( SR:8606166664 CR:JAGad35951 )
A system with 2 ALT 8-series DLT (Quantum 4000) on the same
card showed the following panic:
panic: (display==0xb800, flags==0x0) Data page fault 1111
The stack trace was:
scsi_start+0x18
scsi_retry+0xd8
invoke_callouts+0x160
softclock+0x38
sw_service+0x154
mp_ext_interrupt+0x2a0
$RDB_int_patch+0x58
mpn_splx_free_lock_ul4_brn_target+0x4
net_callout+0x90
netisr_netisr+0x1bc
netisr_daemon+0x68
PHKL_23313:
( SR:8606174670 CR:JAGad43916 )
Compiling kernel-intrusive programs (such as drivers and
programs that access /dev/mem or /dev/kmem) on HP-UX 11.11
may result in compiler warnings or errors due to namespace
violations. Executing such programs may cause kernel
structure data corruption, resulting in memory leaks, hangs,
or panics.
PHKL_24441:
( SR:8606173682 CR:JAGad42939 )
High Availability systems hang when under heavy load
and many I/O errors are being returned by the scsi
driver (possibly due to a hardware problem).
( SR:8606175843 CR:JAGad45083 )
A defective SCSI bus controller generates continuous
SCSI bus resets and causes the system to panic.
The panic results in the following stack trace:
panic+0x14
settimeout_for_cpu+0x174
Ktimeout+0x3c
c720_reset_chip+0x129c
c720_isrRST+0x94
c720_isr+0x15cc
sapic_interrupt+0x2c
( SR:8606176606 CR:JAGad45845 )
If device tracing is enabled (with appropriate values
for scsi_trace_dev and scsi_trace_mask, typically for
debugging) and when the system experiences errors
during I/O through the passthrough driver, the system
panics.
panic+0x14
report_trap_or_int_and_panic+0x80
interrupt+0x1d4
$ihndlr_rtn+0x0
scsi_dmesg_log_io+0xf8
scsi_action+0x1b8
scsi_status_action+0x6c
scsi_cbfn+0x41c
scsi_fast_cbfn+0x1b0
c720_call_cbfns+0x60
c720_isr+0x5bc
epic_isr+0x58
mp_ext_interrupt+0x34c
ivti_patch_to_nop3+0x0
idle+0x164
swidle_exit+0x0
( SR:8606173887 CR:JAGad43140 )
There are various symptoms as described under the
following CRs.
( SR:8606169027 CR:JAGad38305 )
Disk I/O hangs even when LVM PV-Link is configured.
The system could report a "DIAGNOSTIC SYSTEM WARNING".
The on-line diagnostic log would show an I/O Error.
( SR:8606178152 CR:JAGad47379 )
Process hang can result during a device open. The system
log (/var/adm/syslog/syslog.log) shows Queue Full status
and a large retry count on an Inquiry request.
( SR:8606168578 CR:JAGad37858 )
The process hangs if an ioctl is issued to a non-existent
hardware path.
( SR:8606178041 CR:JAGad47268 )
"vgchange -a n <VG Name>" command hangs when the cable is
disconnected on the alternate link, if immediate
reporting (IR) is true.
( SR:8606167814 CR:JAGad37097 )
ioscan -fn command hangs when there is a bad disk present.
( SR:8606139670 CR:JAGad08981 )
The system panics when a certain type of SCSI error
occurs while doing writes on hfs filesystem.
The /var/adm/syslog/syslog.log reports Check Condition
status with sense key: (03) Medium Error.
( SR:8606166721 CR:JAGad36008 )
When a bus is shared between two systems, if one of the
systems continuously sends out bus resets, the I/Os from
the other system on this bus hang, consequently the
PV-Link switch would not occur.
Defect Description:
PHKL_28513:
( SR:8606226043 CR:JAGad95114 )
In extremely rare conditions, single byte writes to
onboard memory (SCRIPT RAM) may not complete on Channel B
of A5159A and Core I/O FWD SCSI HBA on rp24xx, rp54xx
rp7400 systems.
This may result in following problems:
a. Data integrity issues
b. System crash due to HPMC
Resolution:
Driver is changed to perform word writes instead of byte
writes.
( SR:8606286272 CR:JAGae50215 )
To avoid data corruption Disable Pipe Request(DPR) bit is
to be set during SCSI operations. In the present code
it is being done only once, in chip initialization
routine, and it gets reset after a successful
chip reset operation.
Resolution:
Set the DPR bit in the chip reset routine instead of chip
initialization routine. This will make sure that DPR bit
is set on chip reset.
( SR:8606289589 CR:JAGae53519 )
The SCSI LUN pointer is invalid for the bus scsi control
block (SCB) and therefore can cause a recursive bus lock
held panic in Multi-LUN configuration.
Resolution:
The LUN pointer is reset to zero for the bus pool SCB
before it is freed. Hence, recursive holding of the
bus lock is avoided.
PHKL_28096:
( SR:8606271035 CR:JAGae35271 )
The internal hot-swap disks are not configured
to spin up at power-on. Hence, any access to the
the hot swap disks returned a sense data
of ASC = 0x04,ASCQ = 0x02.This resulted in the
I/O getting retried forever resulting in
application hang.
Resolution:
The SCSI driver is modified to send a Start Unit
command to spin up the drives when a sense
data of ASC=0x04, ASCQ=0x02 is returned by
the target.The original I/O is resumed after the
Start Unit command is completed.
PHKL_27579:
( SR:8606245156 CR:JAGae11630 )
The SCSI controller chip on the A5838A card
was reset when it was doing DMA. After reset,
some of the DMA transactions were not getting
claimed by the SCSI controller chip. This
caused the timer on the card bridge to expire
and HPMC the system.
Resolution:
The problem is resolved by aborting the ongoing
DMA before resetting the card.
( SR:8606242143 CR:JAGae09397 )
The Disable Overlapped Arbitration bit in
the Control register Zero is used for
gaining access to the PCI bus while another
function is executing a PCI cycle.The register
bit was not set and hence caused intermittent
bus hangs and bus resets on the cards
containing the 53C876 chip.
Resolution:
The Disable Overlapped Arbitration bit is now
set on the cards containing the 53C876 chip
whenever the chip is reset. This avoids the hang
and subsequent resets.
( SR:8606241873 CR:JAGae09130 )
The scsi_isc array maximum limit is 255.If the instance
is greater than 255 overflow occurs and leads to memory
corruption and subsequent panic. The c720 interface
driver was not validating the maximum limit of the instance
number.
Resolution:
The driver init routine was changed to check if
the instance numbers were greater than 256 and if so return
an error. This causes the bus instance numbers
greater than 256 to become unclaimed and hence avoids
the system panic.
( SR:8606216118 CR:JAGad85288 )
The system panics because of a race condition between the
SCSI bus open and the interrupt being serviced. The
interrupt was getting serviced before the internal
data structures in the bus open routine were completely
initialized.
Resolution:
The fix is to set a flag after initializing the data
structures in the SCSI bus open routine. In the ISR
routine, a check is made to verify if this flag is set.
The interrupt is serviced only if this flag is set. The
flag is unset in the SCSI bus close routine.
( SR:8606257328 CR:JAGae21633 )
When the SCSI bus reset is in progress, a flag is set
and this flag is cleared in a routine that will be
executed 3 seconds after the bus is reset using a timer
routine. Before this function executes,if the card is
suspended, as the suspend routine cancels the timeout,
the flag will never get cleared. Even after the
resume, the flag remains set and when this flag is set,
no I/O are possible. This will cause application hang.
Resolution:
The flag should be reset in the suspend routine
before canceling the timeout routine.
( SR:8606204859 CR:JAGad74037 )
The SCSI driver does not distinguish between speed/width
negotiations initiated by the target or the driver.
The mismatch in the speed setting on the host and the target
resulted in Parity Error on the bus.
Resolution:
SCSI driver now tracks whether the response from the target
is a response to host initiated negotiation or a
unsolicitated request from the target.
( SR:8606232873 CR:JAGae02101 )
The driver used to map request sense buffer for every
I/O (and unmap them on completion). During heavy load the
mapping failed and caused the system to panic. The problem
was fixed by mapping the request sense buffer during bus
open and re-using the physical address for each I/O until
the bus is closed. However, while re-using the request
sense buffers between I/O, the driver was not invalidating
the buffer.
Resolution:
Modify the request sense buffer handling code in c720
driver as below
1. Allocate and map one request sense buffer in
initialization function and re-use it during the life
of the card.
2. Invalidate the buffer after every completion status
receipt from device.
( SR:8606238711 CR:JAGae07734 )
The disk driver returns EINVAL for I/O request
to LVM due to some hardware condition.
LVM was not retrying the I/O requests even
when an alternate path to the LUN existed.
This resulted in some filesystem and system
hang condition.
Resolution:
The disk driver is modified to return an error
of EPOWERF when an EINVAL condition
is reported by the device for an LVM I/O
except for ASC=0x0C , ASCQ=0xA0
(Oracle Hard Integrity error).
LVM will retry the I/O on an alternate path
due to EPOWERF returned by the disk driver.
( SR:8606264850 CR:JAGae29181 )
The open(2) on a CDROM drive without a CD in it takes
a considerable amount of time compared to having a CD
in the drive. As a result of it, the boot time increased
with VxVM. The delay comes from the driver sending a
"Start Stop Unit" (SSU) command to spin up the disc
and retrying the command 5 times even when the
O_NDELAY flag is set.
Resolution:
The solution is not to retry the "Start Stop Unit"
command if the O_NDELAY flag is set and retry
5 times if the flag is not set, so that the Operating
System realizes faster that there is no media in
the CDROM drive.
PHKL_27563:
( SR:8606265990 CR:JAGae30243 )
The I/O subsystem hang occured because an I/O remained
in the lun disk queue. The I/O remained in the queue
because of a failure in allocating the resource.
Resolution:
The code has been modified to take care that the
I/O subsystem hang does not happen when allocation
of the resource fails.
PHKL_26519:
( SR:8606236118 CR:JAGae05183 )
Upon detecting a timed out I/O request, the driver sets a
flag in the LUN data structure indicating "do not retry any
requests for this LUN". After successful completion of a
subsequent I/O request, this flag should be cleared.
However, when the subsequent I/O request completes
successfully, the driver's normal completion path (in which
this flag is cleared) is not executed and hence the flag
remains set. If any subsequent I/O requests do not complete
successfully, they are failed immediately without performing
a retry.
Resolution:
Ensure that the driver follows the normal completion path
for the first successful completion of an I/O request
following a failed I/O request.
( SR:8606226361 CR:JAGad95431 )
When I/O requests from LVM fail or time-out due to bad
disks, the SCSI disk driver returns an incorrect error code
to LVM causing the LVM to retry the I/O request forever
instead of returning failure. This causes the application
which has issued the I/O request to hang indefinitely.
Resolution:
Ensure that the I/O request failed due to MEDIUM ERROR
is reported back to LVM with EMEDIA error.
( SR:8606135832 CR:JAGad04964 )
This product update contains minor enhancements required to
enable the support for 16 byte CDBs (Command Descriptor
Block) in the SCSI driver.
Resolution:
The SCSI driver has been to modified for the support of 16
byte CDBs (Command Descriptor Block).
( SR:8606214047 CR:JAGad83238 )
The SCSI driver accesses the adapter registers in its
interrupt service routine (ISR). Although card interrupts
are disabled during the suspend operation, if spurious
interrupts are delivered to the SCSI driver, the driver
would attempt to read the card registers, resulting in a
HPMC.
Resolution:
The SCSI driver has been modified so that it does not
attempt to process spurious interrupts when it is in a
suspended state.
( SR:8606236116 CR:JAGae05181 )
After an LVM I/O times out, the flag L_FAIL_QUEUE_IO can
remain set and prevent LVM probes from being sent to the
device to see if it has returned on-line. Also, many SCSI
read error messages will be seen in syslog.
Resolution:
Only set the flag (L_FAIL_QUEUE_IO) if there are I/O
requests queued to be sent to the device.
PHKL_25896:
( SR:8606228002 CR:JAGad97060 )
Some disks do not start spinning automatically. The SCSI
subsystem retry policy changed with PHKL_24441 and, as a
result, the Start Unit command is not retried. These two
changes combined cause the first Start Unit command to these
disks to fail. Successive commands issued to these disks
also fail. Later, a Read Capacity command to the device
returns a capacity of zero bytes.
Resolution:
The SCSI subsystem retry policy is refined to retry the
Start Unit command five times. With these successive
retries, the disks start spinning and later return the
correct capacity size.
PHKL_25509:
( SR:8606203627 CR:JAGad72800 )
All messages logged by the c720 driver can be suppressed by
setting appropriate value for a c720 driver global variable.
This message was not controlled by this variable.
Resolution:
The value of the global variable is now checked before
printing the mentioned message.
( SR:8606186960 CR:JAGad56170 )
The Plasmon devices return 256 bytes of Sense data. The
allocated buffer for sense data is also 256 bytes, causing
the residue to be zero. When the residue is zero, the
mentioned message is printed.
Resolution:
The code that prints the mentioned message is removed since
a zero residue is not an error.
( SR:8606201476 CR:JAGad70652 )
This informative message is logged while trying to access a
device with zero capacity (i.e. a placeholder LUN when LUNS
are not defined contiguously) or a device without media.
Resolution:
This message is no longer logged by default for partially
opened devices. This message log can be enabled for
debugging purposes by setting appropriate value in
scsi_log_mask.
( SR:8606199892 CR:JAGad69078 )
Devices of HP SureStore E Disk Array 12 sometimes
successfully complete I/Os when in Contingent Allegiance
(CHECK CONDITION state of SCSI devices). These I/O
completions were not reported to the requesting layer,
causing the process to hang.
Resolution:
If an I/O completes sucessfully when the device is in
Contingent Allegiance condition, the I/O is returned with an
error to the requesting layer for further action (typically
an I/O retry).
( SR:8606194472 CR:JAGad63680 )
While determining whether the SCSI bus is wide or narrow,
the C3700 model was not considered.
Resolution:
The model string for the C3700 was added to the list of
models with narrow external SCSI buses.
( SR:8606177456 CR:JAGad46688 )
On the last close of a device, the scsi driver attempts to
synchronize the cache of the device. Using a FC60 array,
this is unnecessary and it also causes an Automatic LUN
Tranfer (ALT). The unneeded ALT operations cause a
significant delay when attempting to import Disk groups.
Resolution:
Disk driver does not synchronize cache on FC60 array devices
when the device is closed.
PHKL_25165:
( SR:8606207855 CR:JAGad77032 )
The SCSI services did not support these ioctls for the c8xx
driver.
Resolution:
SCSI services is enhanced to support these ioctls for the
c8xx driver.
( SR:8606170140 CR:JAGad39404 )
Many non critical conditions generate logs. By example,
addition or removal of devices in the loop generate many
resets.
Resolution:
The logging mechanism is adapted to record only critical
error conditions. The following conditions are recorded:
Unit Attention and Deferred errors
I/O retried unsuccessfully
I/O unsuccessful and not retried
Also, if the SLOG_SUCCESS_RETRY is set in scsi_log_mask,
I/Os completing successfully after prior unsuccessful
attempts are recorded. This helps to identify devices
repeatedly returning errors before being successful.
( SR:8606172682 CR:JAGad41942 )
The nature of the lun is not checked when modifying the
queue depth of the lun.
When modifying the queue depth of a lun, the new value
is overwritten by the previous value.
Resolution:
The nature of a lun is checked while modifying its queue
depth. If the lun does not support tag queueing, an error
code is returned.
The code is adapted to support multiple queue depth changes.
( SR:8606166652 CR:JAGad35939 )
If a SCSI I/O is initiated using the sctl/ioctl passthrough
function and the transfer size is greater than the size of
the malloc'd buffer for this transfer, the system panics.
Resolution:
Check the access permissions of the buffer supplied by the
user before using it. This ensures the system won't panic
if the size of the I/O is greater than the size of the
buffer.
( SR:8606192639 CR:JAGad61851 )
While probing for each LUN, the corresponding bus is opened
and closed. The bus open takes a long time, especially in
large Fibre Channel Array configurations. Since all
possible LUNs are probed on each target whether or not they
are present, the probe time can be quite long on large Fibre
Channel Array configurations, resulting in long boot times
and long ioscan times (without the -k option).
Resolution:
The bus is kept open until all the LUNs corresponding to all
the targets on that bus are probed.
( SR:8606189054 CR:JAGad58270 )
Under heavy I/O load on the same bus, when some per bus
resource (tag, nexus) becomes unavailable, I/Os are stored
in specific queues, waiting for the resource to become
available. Under some conditions, the queues are not
checked once the resource is once again available, leaving
the I/O requests unserviced. The corresponding processes
remain in an unkillable state, waiting for I/O completion
or failure that never occurs.
Resolution:
Additional tests were added to check if I/Os are pending in
the queues, and to process them if the resources are now
available.
( SR:8606166664 CR:JAGad35951 )
While retrying an I/O that has timed out, the system may
access a previously freed target pointer, resulting in a
panic.
Resolution:
Timed-out requests are sent to a temporary queue. This
prevents them from being processed and started until the
target pointer is once again valid.
PHKL_23313:
( SR:8606174670 CR:JAGad43916 )
A number of program header files were delivered in their
"debug" forms rather than in their intended "performance"
forms. Kernel-intrusive programs (such as drivers and
programs that access /dev/mem or /dev/kmem) compiled with
these header files may contain internal structures that are
not aligned with the actual kernel structures.
Resolution:
A set of patches redeliver the header files in their
intended forms. All kernel-intrusive programs originally
compiled using the header files included on the HP-UX 11.11
Operating Environment OE Install and Recovery media dated
December 2000 must be recompiled using the corrected header
files.
All of the corrected header file patches are included in the
BUNDLE11i bundle on the HP-UX 11.11 Operating Environment
Core OE Install and Recovery media dated February 2001 or
later.
The complete list of header file patches is:
PHNE_23288 /usr/conf/net/netmp.h
/usr/include/net/netmp.h
/usr/conf/sys/socketvar.h
/usr/include/sys/socketvar.h
/usr/conf/sys/unpcb.h
/usr/include/sys/unpcb.h
PHNE_23289 /usr/include/sio/mux4.h
PHKL_23290 /usr/conf/space.h.d/system_space.h
PHKL_23291 /usr/conf/graf/gpu_data.h
PHKL_23292 /usr/conf/io/scsi_surface.h
PHKL_23293 /usr/conf/sys/assert.h
PHKL_23294 /usr/conf/sys/buf.h
/usr/include/sys/buf.h
PHKL_23295 /usr/conf/sys/debug.h
/usr/include/sys/debug.h
PHKL_23296 /usr/conf/sys/dnlc.h
/usr/include/sys/dnlc.h
PHKL_23297 /usr/conf/sys/io.h
/usr/include/sys/io.h
PHKL_23298 /usr/include/sys/ki_iface.h
PHKL_23299 /usr/conf/sys/pfdat.h
/usr/include/sys/pfdat.h
PHKL_23300 /usr/include/sys/proc_debug.h
PHKL_23301 /usr/conf/sys/proc_iface.h
/usr/include/sys/proc_iface.h
PHKL_23302 /usr/conf/sys/rw_lock.h
/usr/include/sys/rw_lock.h
PHKL_23303 /usr/conf/sys/sem_alpha.h
/usr/include/sys/sem_alpha.h
PHKL_23304 /usr/conf/sys/sem_beta.h
/usr/include/sys/sem_beta.h
PHKL_23305 /usr/conf/sys/sem_sync.h
/usr/include/sys/sem_sync.h
PHKL_23306 /usr/conf/sys/sem_utl.h
/usr/include/sys/sem_utl.h
PHKL_23307 /usr/conf/sys/spinlock.h
/usr/include/sys/spinlock.h
PHKL_23308 /usr/conf/sys/vas.h
/usr/include/sys/vas.h
PHKL_23309 /usr/conf/sys/vfd.h
/usr/include/sys/vfd.h
PHKL_23310 /usr/conf/sys/vnode.h
/usr/include/sys/vnode.h
PHKL_23311 /usr/conf/ufs/inode.h
/usr/include/sys/inode.h
PHKL_23312 /usr/conf/wsio/pci.h
/usr/include/sys/pci.h
PHKL_23313 /usr/include/sys/scsi_ctl.h
PHKL_23314 /usr/conf/pa/sync/spinlock.h
/usr/include/pa/sync/spinlock.h
PHKL_23315 /usr/conf/pa/cpu.h
/usr/include/pa/cpu.h
PHKL_23316 /usr/conf/pa/sys/map.h
PHKL_24441:
( SR:8606173682 CR:JAGad42939 )
I/Os which timeout were not always being returned with
an error but were being retried indefinitely. This
resulted in requests that had timed out, getting stuck
in the disk driver's queue, resulting in a hang.
Resolution:
The requests are tracked and those which timeout are
returned to the upper layer, thus allowing it to switch
to an alternate path if one is configured.
( SR:8606175843 CR:JAGad45083 )
On every SCSI bus reset, a new timer was set for further
processing. This lead to timer table overflow that
caused the system to panic.
Resolution:
Everytime the bus reset occurs, the previously-set timer
(if it exists), is cancelled and a new timer is set.
This ensures only one timer exists per bus at a given
time thus preventing the timer table overflow.
( SR:8606176606 CR:JAGad45845 )
In the passthrough driver I/O path, the logging function
referenced a NULL pointer while trying to generate a
hardware path string for the device, causing the system
panic.
Resolution:
For I/Os through the passthrough driver, the logging
function now checks for NULL pointer and the hardware
path information for the device is not logged for such
I/Os.
( SR:8606173887 CR:JAGad43140 )
( SR:8606169027 CR:JAGad38305 )
( SR:8606178152 CR:JAGad47379 )
( SR:8606168578 CR:JAGad37858 )
( SR:8606178041 CR:JAGad47268 )
( SR:8606167814 CR:JAGad37097 )
( SR:8606139670 CR:JAGad08981 )
( SR:8606166721 CR:JAGad36008 )
Few error conditions were retried indefinitely causing
process hang or PVLink switch not to occur. While in the
case of error-intolerant upper layers (like the hfs
filesystem) the error returns caused file system panics.
Resolution:
Depending on where the I/O is issued from:
1. Device open/ioctl,
2. I/Os from an error-intolerant upper layer or
3. I/Os from LVM-like upper layers,
various error conditions are now handled appropriately.
Enhancement:
No (superseded patches contained enhancements)
PHKL_28513:
Enhancements were delivered in a patch this one has
superseded. Please review the Defect Description
text for more information.
SR:
8606135832 8606139670 8606166652 8606166664 8606166721
8606167814 8606168578 8606169027 8606170140 8606172682
8606173682 8606173887 8606174670 8606175843 8606176606
8606177456 8606178041 8606178152 8606186960 8606189054
8606192639 8606194472 8606199892 8606201476 8606203627
8606204859 8606207855 8606214047 8606216118 8606226043
8606226361 8606228002 8606232873 8606236116 8606236118
8606238711 8606241873 8606242143 8606245156 8606257328
8606264850 8606265990 8606271035 8606286272 8606289589
Patch Files:
ProgSupport.C-INC,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/include/sys/scsi_ctl.h
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libwsio.a(scsi_c720.o)
/usr/conf/lib/libwsio.a(scsi_ctl.o)
/usr/conf/lib/libwsio.a(scsi_disk.o)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libwsio.a(scsi_c720.o)
/usr/conf/lib/libwsio.a(scsi_ctl.o)
/usr/conf/lib/libwsio.a(scsi_disk.o)
what(1) Output:
ProgSupport.C-INC,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/include/sys/scsi_ctl.h:
scsi_ctl.h $Date: 2003/01/13 05:09:36 $Revision: r11
.11/5 PATCH_11.11 (PHKL_28513) */
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libwsio.a(scsi_c720.o):
scsi_c720.c $Date: 2003/01/13 04:47:59 $Revision: r1
1.11/6 PATCH_11.11 (PHKL_28513)
/usr/conf/lib/libwsio.a(scsi_ctl.o):
scsi_ctl.c $Date: 2003/01/13 05:06:47 $Revision: r11
.11/5 PATCH_11.11 (PHKL_28513)
/usr/conf/lib/libwsio.a(scsi_disk.o):
scsi_disk.c $Date: 2002/10/30 02:42:35 $Revision: r1
1.11/6 PATCH_11.11 (PHKL_28096)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libwsio.a(scsi_c720.o):
scsi_c720.c $Date: 2003/01/13 04:47:59 $Revision: r1
1.11/6 PATCH_11.11 (PHKL_28513)
/usr/conf/lib/libwsio.a(scsi_ctl.o):
scsi_ctl.c $Date: 2003/01/13 05:06:47 $Revision: r11
.11/5 PATCH_11.11 (PHKL_28513)
/usr/conf/lib/libwsio.a(scsi_disk.o):
scsi_disk.c $Date: 2002/10/30 02:42:35 $Revision: r1
1.11/6 PATCH_11.11 (PHKL_28096)
cksum(1) Output:
ProgSupport.C-INC,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
238730050 67102 /usr/include/sys/scsi_ctl.h
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
1010069282 155048 /usr/conf/lib/libwsio.a(scsi_c720.o)
2808363869 110888 /usr/conf/lib/libwsio.a(scsi_ctl.o)
1041978436 27504 /usr/conf/lib/libwsio.a(scsi_disk.o)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
2632735042 305624 /usr/conf/lib/libwsio.a(scsi_c720.o)
3266164674 275304 /usr/conf/lib/libwsio.a(scsi_ctl.o)
705452651 60928 /usr/conf/lib/libwsio.a(scsi_disk.o)
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHKL_24441 PHKL_28096 PHKL_27579 PHKL_27563 PHKL_26519 PHKL_25896
PHKL_25509 PHKL_25165 PHKL_23313
Equivalent Patches: None
Patch Package Size: 1050 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_28513
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_28513.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_28513. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHKL_28513.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHKL_28513.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_28513.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHKL_28513------------------------------------------
Document ID: PHCO_27977
Date Loaded: 20030310
Title: s700_800 11.11 HP VxVM B.03.20.1/vxvmconvert Patch
Patch Name: PHCO_27977
Patch Description: s700_800 11.11 HP VxVM B.03.20.1/vxvmconvert Patch
Creation Date: 02/09/30
Post Date: 03/03/10
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products:
HP VxVM B.03.20.1
Filesets:
HPvxvm.VXVM-RUN,fr=B.03.20.1,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical:
Yes
PHCO_27977: ABORT
Category Tags:
defect_repair general_release critical halts_system
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_27977
Symptoms:
PHCO_27977:
( SR:8606290914 CR:JAGae54757)
HP: vxvmconvert: analysis problem with enclosure based names
( SR:8606221522 CR:JAGad90656 )
vxvmconvert: vxlvmencap Memory fault (coredump) from
vxhpcap.
( SR:8606279193 CR:JAGae43249 )
The get_vg_pvols routine can't handle physical VG's.
( SR:8606275881 CR:JAGae39956 )
vxvmconvert cant handle LARGE extent based STRIPED volumes.
( SR:8606279194 CR:JAGae43250 )
The get_vg_pvols has problem with DMP alternate links.
( SR:8606279207 CR:JAGae43263 )
vxhpcap cores when 255 lvols are in VG.
( SR:8606279196 CR:JAGae43252 )
vxhpcap cores on large "extent based" striped LVM volumes.
( SR:8606267273 CR:JAGae31516 )
vxvmconvert doesn't save LVM config record if one already
exists.
( SR:8606267552 CR:JAGae31794 )
vxvmconvert passes analysis phase but then fails if disk
has ISL header.
( SR:8606275674 CR:JAGae39750 )
vxhpcap dumps core on systems with more than 256 disks.
( SR:8606278842 CR:JAGae42899 )
The dogi_get_group_pvlist() and get_vg_pvols() are not
handling Physical Volume Groups correctly.
( SR:8606289449 CR:JAGae53380 )
Conversion problem with pvlinks and EMC Powerpath.
( SR:8606289441 CR:JAGae53372 )
Rollback failed on physical Volume Groups.
Defect Description:
PHCO_27977:
( SR:8606290914 CR:JAGae54757)
Problem in conversion found during testing if
enclosure based names are used.
( SR:8606221522 CR:JAGad90656 )
The fault is due to the input file to vxhpcap from
vxlvmencap does not contain the %vgname string marker.
The core dump is from strncpy. This is because the VG has
PVs which have multiple paths but not all paths are
specified for the VG.
( SR:8606279193 CR:JAGae43249 )
The get_vg_pvols does not work with Volume Groups using
Physical Volume Groups.
( SR:8606275881 CR:JAGae39956 )
The problem is that extent based striping on HP, when
converted, results in hundreds of subdisks when the volume
size is large. This causes vxhpcap to have a buffer
overrun when generating the "vxmake plex" command which
follows with each and every subdisk in the plex. vxhpcap
can currently handle only about 50 subdisks. So, if the
volume using extent based striping is using the default 4MB
partitions, this would translate to only being able to
convert a VG up to about 200MB. Of course, if the
partitions were 256MB, then we could handle up to about
12 Gig.
( SR:8606279194 CR:JAGae43250 )
The get_vg_pvols does not work with Physical Volume Groups.
( SR:8606279207 CR:JAGae43263 )
vxhpcap utility is trying to access the 256th entry in the
VG_entry.lv structure. So this is an "array index out of
bounds" problem.
( SR:8606279196 CR:JAGae43252 )
The vxmake command will fail if the vxmake command line is
too long. Since the large extent based volumes, result in
thousands of subdisks being created, the vxmake plex
sd="list of 4000+ subdisks" causes the vxmake command
to fail.
( SR:8606267273 CR:JAGae31516 )
When vxvmconvert is used to convert LVM volume groups to
VxVM disk groups, for some reason conversion fails, the
next time customer run vxvmconvert on the same volume
group, vxvmconvert doesn't save lvm configuration records
and do not proceed with updating rollback information. As
a result rollback of the disk group is unavailable. This
because if the config file usded by the commands already
exists(created on the failed attempt) then vgcfgbackup
fails.
( SR:8606267552 CR:JAGae31794 )
The problem with this disk was that it had ISL directory
header in the first block (block zero). This disk was
probably a boot disk at some point (configured with
pvcreate -B and mkboot) and then recreated with pvcreate -f.
( SR:8606275674 CR:JAGae39750 )
vxhpcap dumps core and aborts with SIGSEGV on systems with
more than 256 disks.
( SR:8606278842 CR:JAGae42899 )
The routines dogi_get_group_pvlist() and get_vg_pvols()
are not handling Physical Volume Groups correctly.
( SR:8606289449 CR:JAGae53380 )
Conversion problem with pvlinks and EMC Powerpath.
primay problem was that get_vg_pvols could not handle the
case where LVM uses a non-primary path to a disk as the
VG's only known path to the disk.
( SR:8606289441 CR:JAGae53372 )
Rollback failed on physical Volume Groups.
vxvm:vxdisk: ERROR: Failed to obtain locks:
c0t10d0: no such object in the configuration
vxvm:vxdisk: ERROR: Failed to obtain locks:
c0t11d0: no such object in the configuration
vgdisplay: Volume group "/dev/vg01" does not exist in
the "/etc/lvmtab" file.
vgdisplay: Cannot display volume group "vg01".
Resolution:
( SR:8606290914 CR:JAGae54757)
We now handle enclosure based names during the
conversion.
( SR:8606221522 CR:JAGad90656 )
Change vxvmconvert to cope with this type of set-up and
convert the VG. It is valid for a VG to not have all paths
to the VG specified.
( SR:8606279193 CR:JAGae43249 )
Changed get_vg_pvols() to just use vxhpcap instead.
( SR:8606275881 CR:JAGae39956 )
Increased buffer size to allow for large amount of subdisks
in a plex.
( SR:8606279194 CR:JAGae43250 )
Changed get_vg_pvols() to be able to handle physical VGs.
( SR:8606279207 CR:JAGae43263 )
The array for logical volume information was set to 255
items and it needed to be 256.
( SR:8606279196 CR:JAGae43252 )
Added code to handle many thousands of disks.
( SR:8606267273 CR:JAGae31516 )
Added check for config file before attempting backup.
( SR:8606267552 CR:JAGae31794 )
Added extra lifls checks to examine the disks.
( SR:8606275674 CR:JAGae39750 )
Changed the structure definition from char to uint to
support large number of disks.
( SR:8606278842 CR:JAGae42899 )
Updated get_vg_pvols() and dogi_get_group_pvlist() to handle
physical volume groups correctly.
( SR:8606289449 CR:JAGae53380 )
Fix so that LVM can use non-primary path to a disk as the
VG's only known path to the disk.
( SR:8606289441 CR:JAGae53372 )
Fix so that Rollback of physical Volume Groups works.
Enhancement:
No
SR:
8606221522 8606279193 8606275881 8606279194 8606279207
8606279196 8606267273 8606267552 8606275674 8606278842
8606289449 8606289441
Patch Files:
HPvxvm.VXVM-RUN,fr=B.03.20.1,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/vxvm/bin/vxhpcap
/usr/lib/vxvm/voladm.d/bin/vxsave_lvmrecs
/usr/lib/vxvm/voladm.d/lib/vxadm_syslib.sh
/usr/lib/vxvm/voladm.d/bin/disk.anal.ckinit
/usr/lib/vxvm/voladm.d/bin/disk.lvm.ckinit
/usr/lib/vxvm/voladm.d/bin/disk.convert
/usr/lib/vxvm/voladm.d/bin/minor_numchk
/usr/lib/vxvm/voladm.d/lib/vxadm_lvmlib.sh
/usr/lib/vxvm/voladm.d/lib/vxadm_lib.sh
/usr/lib/vxvm/bin/vxlvmencap
what(1) Output:
HPvxvm.VXVM-RUN,fr=B.03.20.1,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/vxvm/bin/vxhpcap:
vxhpcap.c $Date: 2003/01/07 08:34:28 $Revision: 32.7
PATCH_11.11 (PHCO_27977)
/usr/lib/vxvm/voladm.d/bin/disk.anal.ckinit:
disk.anal.ckinit.sh $Date: 2002/12/23 07:45:59 $Revi
sion: 32.3 PATCH_11.11 (PHCO_27977)
src/hp/cmd/vxvm/voladm/disk.anal.ckinit.sh 1.15.52.3
12/22/02 13:18:34 - Copyright (c) 1999 VERI
TAS Software Corp.
unixvm:src/hp/cmd/vxvm/voladm/disk.anal.ckinit.sh 1.
15.52.3
/usr/lib/vxvm/voladm.d/bin/disk.convert:
disk.convert.sh $Date: 2002/12/11 08:14:29 $Revision
: 32.3 PATCH_11.11 (PHCO_27977)
src/hp/cmd/vxvm/voladm/disk.convert.sh 1.34.52.3 12/
10/02 15:07:09 - Copyright (c) 1999 VERITAS
Software Corp.
unixvm:src/hp/cmd/vxvm/voladm/disk.convert.sh 1.34.5
2.3
/usr/lib/vxvm/voladm.d/bin/disk.lvm.ckinit:
disk.lvm.ckinit.sh $Date: 2002/12/23 07:56:58 $Revis
ion: 32.3 PATCH_11.11 (PHCO_27977)
src/hp/cmd/vxvm/voladm/disk.lvm.ckinit.sh 1.18.52.5
12/22/02 13:20:48 - Copyright (c) 1999 VERIT
AS Software Corp.
unixvm:src/hp/cmd/vxvm/voladm/disk.lvm.ckinit.sh 1.1
8.52.5
/usr/lib/vxvm/voladm.d/bin/minor_numchk:
minor_numchk.sh $Date: 2002/12/09 09:36:40 $Revision
: 32.2 PATCH_11.11 (PHCO_27977)
src/hp/cmd/vxvm/voladm/minor_numchk.sh 1.3.52.1 12/0
2/02 15:18:54 -
unixvm:src/hp/cmd/vxvm/voladm/minor_numchk.sh 1.3.52
.1
/usr/lib/vxvm/voladm.d/lib/vxadm_lib.sh:
vxadm_lib.sh $Date: 2002/12/11 07:58:44 $Revision: 3
2.2 PATCH_11.11 (PHCO_27977)
src/hp/cmd/vxvm/voladm/vxadm_lib.sh 1.30.52.10 12/10
/02 14:07:33 - Copyright (c) 1999 VERITAS So
ftware Corp.
unixvm:src/hp/cmd/vxvm/voladm/vxadm_lib.sh 1.30.52.1
0
/usr/lib/vxvm/voladm.d/lib/vxadm_lvmlib.sh:
vxadm_lvmlib.sh $Date: 2003/01/07 08:42:31 $Revision
: 32.7 PATCH_11.11 (PHCO_27977)
src/hp/cmd/vxvm/voladm/vxadm_lvmlib.sh 1.32.52.9 01/
06/03 13:22:20 - Copyright (c) 1999 VERITAS
Software Corp.
unixvm:src/hp/cmd/vxvm/voladm/vxadm_lvmlib.sh 1.32.5
2.9
/usr/lib/vxvm/voladm.d/lib/vxadm_syslib.sh:
vxadm_syslib.sh $Date: 2002/12/12 08:07:20 $Revision
: 32.6 PATCH_11.11 (PHCO_27977)
src/hp/cmd/vxvm/voladm/vxadm_syslib.sh 1.45.52.6 12/
10/02 15:31:48 - Copyright (c) 1999 VERITAS
Software Corp.
unixvm:src/hp/cmd/vxvm/voladm/vxadm_syslib.sh 1.45.5
2.6
/usr/lib/vxvm/voladm.d/bin/vxsave_lvmrecs:
vxsave_lvmrecs.sh $Date: 2002/12/30 13:27:11 $Revisi
on: 32.7 PATCH_11.11 (PHCO_27977)
vxsave_lvmrecs.sh 32.4 10/02/02 13:01:35 -
unixvm:vxsave_lvmrecs.sh 32.4
/usr/lib/vxvm/bin/vxlvmencap:
vxlvmencap.sh $Date: 2003/01/07 08:39:42 $Revision:
32.3 PATCH_11.11 (PHCO_27977)
src/hp/cmd/vxvm/support/vxlvmencap.sh 1.10.52.4 08/2
2/01 10:51:07 - Copyright (c) 1999 VERITAS S
oftware Corp.
unixvm:src/hp/cmd/vxvm/support/vxlvmencap.sh 1.10.52
.4
cksum(1) Output:
HPvxvm.VXVM-RUN,fr=B.03.20.1,fa=HP-UX_B.11.11_32/64,v=HP:
1141997224 102400 /usr/lib/vxvm/bin/vxhpcap
2390587215 43552 /usr/lib/vxvm/voladm.d/bin/disk.anal.ckinit
1638225708 14229 /usr/lib/vxvm/voladm.d/bin/disk.convert
673530599 46838 /usr/lib/vxvm/voladm.d/bin/disk.lvm.ckinit
888070867 2104 /usr/lib/vxvm/voladm.d/bin/minor_numchk
33979540 61691 /usr/lib/vxvm/voladm.d/lib/vxadm_lib.sh
3769750491 42156 /usr/lib/vxvm/voladm.d/lib/vxadm_lvmlib.sh
491862189 47456 /usr/lib/vxvm/voladm.d/lib/vxadm_syslib.sh
1840944733 8487 /usr/lib/vxvm/voladm.d/bin/vxsave_lvmrecs
2196129147 11092 /usr/lib/vxvm/bin/vxlvmencap
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches: None
Patch Package Size: 410 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_27977
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_27977.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_27977. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHCO_27977.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHCO_27977.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_27977.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHCO_27977------------------------------------------
Document ID: PHCO_28623
Date Loaded: 20030310
Title: s700_800 11.11 fsck_hfs(1M) cumulative patch
Patch Name: PHCO_28623
Patch Description: s700_800 11.11 fsck_hfs(1M) cumulative patch
Creation Date: 03/02/25
Post Date: 03/03/10
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.CORE-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair enhancement general_release
manual_dependencies
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_28623
Symptoms:
PHCO_28623:
( SR:8606287954 CR:JAGae51887 )
fsck_hfs(1M) is unable to ensure the consistency of a file
system. The file system is mountable after running fsck,
but rm(1) on the directory reports an error that the
directory is not empty although ls(1) may report that the
directory is empty.
PHCO_26699:
( SR:8606247419 CR:JAGae13857 )
fsck(1M) performance slow on large systems.
Defect Description:
PHCO_28623:
( SR:8606287954 CR:JAGae51887 )
fsck_hfs(1M) does not fix corruption in the direct and
indirect data block areas of large directories. This may
lead to a situation where many files are unreferenced,
making them invisible to ls(1), but nevertheless exist,
causing rm(1) to fail.
Resolution:
The solution is either to save as much of the directory as
possible or remove the whole directory; either way the
integrity of the file system is preserved. If fsck_hfs(1M)
removes the whole directory, all files will be moved to the
lost+found directory; but in certain cases fsck is able to
salvage part of the directory by zeroing out all blocks
starting from the corrupt block onwards; in such cases all
files in those blocks are moved to the lost+found directory.
PHCO_26699:
( SR:8606247419 CR:JAGae13857 )
fsck(1M) always does sync(2) causing performance degradation
on systems with large buffer cache.
Resolution:
Improve performance by adding "-s" switch to fsck(1M) to
suppress sync(2) call.
Enhancement:
No (superseded patches contained enhancements)
PHCO_28623:
Enhancements were delivered in a patch this one has
superseded. Please review the Defect Description
text for more information.
SR:
8606247419 8606287954
Patch Files:
OS-Core.CORE-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
/usr/share/man/man1m.Z/fsck_hfs.1m
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/sbin/fs/hfs/fsck
what(1) Output:
OS-Core.CORE-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
/usr/share/man/man1m.Z/fsck_hfs.1m:
None
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/sbin/fs/hfs/fsck:
fsck.c $Date: 2003/02/07 01:03:10 $Revision: r11.11/
4 PATCH_11.11 (PHCO_28623)
$Revision: (#) all CUP11.11_BL2003_0225_2 PATCH_11.
11 PHCO_28623
Tue Feb 25 09:18:15 PST 2003 $
$ Version_11.11 Feb 7 2003 13:18:48 $
cksum(1) Output:
OS-Core.CORE-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
448625028 5365 /usr/share/man/man1m.Z/fsck_hfs.1m
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
4270940751 344064 /sbin/fs/hfs/fsck
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies:
PHCO_26699 requires patch PHCO_26701 to get full command
interface implementation.
Any of these patches may be installed independently of the
others with no adverse effect on the system.
The following command messages may occur if a relevant patch
is missing:
> fsck -F hfs ... Warning: -f option is not supported for
this filesystem
> fsck -F vxfs ... fsck: illegal option -- s
Supersedes:
PHCO_26699
Equivalent Patches:
PHCO_28116:
s700: 11.00
s800: 11.00
Patch Package Size: 370 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_28623
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_28623.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_28623. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHCO_28623.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHCO_28623.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_28623.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHCO_28623------------------------------------------
Document ID: PHKL_27985
Date Loaded: 20030310
Title: s700_800 11.11 HP VxVM B.03.20.1/VVR Patch
Patch Name: PHKL_27985
Patch Description: s700_800 11.11 HP VxVM B.03.20.1/VVR Patch
Creation Date: 02/09/30
Post Date: 03/03/10
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products:
HP VxVM B.03.20.1
Filesets:
HPvxvm.VXVM-KRN,fr=B.03.20.1,fa=HP-UX_B.11.11_32,v=HP
HPvxvm.VXVM-KRN,fr=B.03.20.1,fa=HP-UX_B.11.11_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_27985: PANIC
Category Tags:
defect_repair general_release critical panic
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_27985
Symptoms:
PHKL_27985:
( SR:8606279201 CR:JAGae43257 )
VVR: Memory overrun.
( SR:8606279202 CR:JAGae43258 )
VVR: IO stops at 99%
( SR:8606279205 CR:JAGae43261 )
RLINKs won't connect in a virtual IP environment
( SR:8606292818 CR:JAGae56570 )
VVR: panic during readback processing
Defect Description:
PHKL_27985:
( SR:8606279201 CR:JAGae43257 )
Attempt is made to free the memory twice.
Stack trace is:
crash event was a panic
panic+0x6c
kmem_arena_panic+0x1e4
kmem_free+0x244
vol_free+0x2c
Xvolmemfree+0x298
vol_ru_free_update+0x134
vol_ru_readback_delete+0x58
vol_ru_alloc_buffer_done+0xbc
voliod_iohandle+0x1f8
voliod_loop+0xd70
kthread_daemon_startup+0x24
kthread_daemon_startup+0x0
panic+0x6c
( SR:8606279202 CR:JAGae43258 )
VVR AIX io stops at 99% full srl in asyn with dcm on both
primary and secondary, when the rlink is "disconnecting
due to ack timeout".
( SR:8606279205 CR:JAGae43261 )
Both the primary as well as secondary rlinks remain in
disconnected state, and don't come back to connected state.
The problem is that after we do a 'vradmin -f startrep',
the RLINKs are not going into CONNECT state. This is due
to freeing memory before network layer could actually send
data completely.
( SR:8606292818 CR:JAGae56570 )
While runnig the tcs, machine panicked at the following
in vol_ru_readback_process():
TED_ASSERT("vol_ru_readback_process:1a", update != NULL);
update->free_mlist = mlist;
The problem here is that the srl is completely messed up.
There is no update where the first one is supposed to be,
and the update with start seqno doesn't exist at all.
The problem lies in vol_ru_find_first_pending(),
which compares the first update on the main queue with the
first update on the catchup queue, but assumes that they
are both single updates. If either is a multiupdate, the
fields will be off and this comparison is invalid and
meaningless.
Resolution:
( SR:8606279201 CR:JAGae43257 )
Changed the way the memory is being freed to avoid
double free.
( SR:8606279202 CR:JAGae43258 )
Generate msgid and put the nio in rp_senderq which fixes
the problem where lowest msgid is not at the end.
( SR:8606279205 CR:JAGae43261 )
Fix is to free the allocated buffer in callback function.
Now, it will be freed only when network layer has actually
sent it.
( SR:8606292818 CR:JAGae56570 )
Fix the code such that a macro is used to extract the
correct field depending on whether the update is a single
or multi update.
Enhancement:
No
SR:
8606279201 8606279202 8606279205 8606292818
Patch Files:
HPvxvm.VXVM-KRN,fr=B.03.20.1,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libvxvm.a(kmsg_common.o)
/usr/conf/lib/libvxvm.a(kmsg_udp.o)
/usr/conf/lib/libvxvm.a(rv_update.o)
/usr/conf/lib/libvxvm.a(rvio.o)
HPvxvm.VXVM-KRN,fr=B.03.20.1,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libvxvm.a(kmsg_common.o)
/usr/conf/lib/libvxvm.a(kmsg_udp.o)
/usr/conf/lib/libvxvm.a(rv_update.o)
/usr/conf/lib/libvxvm.a(rvio.o)
what(1) Output:
HPvxvm.VXVM-KRN,fr=B.03.20.1,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libvxvm.a(kmsg_common.o):
kmsg_common.c $Date: 2002/10/01 08:12:52 $Revision:
32.2 PATCH_11.11 (PHKL_27985)
/usr/conf/lib/libvxvm.a(kmsg_udp.o):
kmsg_udp.c $Date: 2002/10/01 08:38:08 $Revision: 32.
3 PATCH_11.11 (PHKL_27985)
/usr/conf/lib/libvxvm.a(rv_update.o):
rv_update.c $Date: 2002/11/07 18:16:07 $Revision: 32
.2 PATCH_11.11 (PHKL_27985)
/usr/conf/lib/libvxvm.a(rvio.o):
rvio.c $Date: 2002/10/01 08:13:30 $Revision: 32.2 PA
TCH_11.11 (PHKL_27985)
HPvxvm.VXVM-KRN,fr=B.03.20.1,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libvxvm.a(kmsg_common.o):
kmsg_common.c $Date: 2002/10/01 08:12:52 $Revision:
32.2 PATCH_11.11 (PHKL_27985)
/usr/conf/lib/libvxvm.a(kmsg_udp.o):
kmsg_udp.c $Date: 2002/10/01 08:38:08 $Revision: 32.
3 PATCH_11.11 (PHKL_27985)
/usr/conf/lib/libvxvm.a(rv_update.o):
rv_update.c $Date: 2002/11/07 18:16:07 $Revision: 32
.2 PATCH_11.11 (PHKL_27985)
/usr/conf/lib/libvxvm.a(rvio.o):
rvio.c $Date: 2002/10/01 08:13:30 $Revision: 32.2 PA
TCH_11.11 (PHKL_27985)
cksum(1) Output:
HPvxvm.VXVM-KRN,fr=B.03.20.1,fa=HP-UX_B.11.11_32,v=HP:
3712928784 8044 /usr/conf/lib/libvxvm.a(kmsg_common.o)
2538432124 2928 /usr/conf/lib/libvxvm.a(kmsg_udp.o)
3606562903 70504 /usr/conf/lib/libvxvm.a(rv_update.o)
2568838124 67108 /usr/conf/lib/libvxvm.a(rvio.o)
HPvxvm.VXVM-KRN,fr=B.03.20.1,fa=HP-UX_B.11.11_64,v=HP:
3682002686 24664 /usr/conf/lib/libvxvm.a(kmsg_common.o)
3410624342 5904 /usr/conf/lib/libvxvm.a(kmsg_udp.o)
3604468350 131000 /usr/conf/lib/libvxvm.a(rv_update.o)
3339693007 129464 /usr/conf/lib/libvxvm.a(rvio.o)
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches: None
Patch Package Size: 460 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.
&