|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: IT Resource Center (support_feedback_at_us-support-mail.external.hp.com)
Date: Sun Aug 11 2002 - 12:29:02 CDT
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://www.itresourcecenter.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://www.itresourcecenter.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 Aug 11 3:05:04 PDT 2002
Table of Contents:
Document ID Title
--------------- -----------
PHSS_27342 s700_800 11.00 OV ITO6.0X Service Navigator Patch A.06.13
PHSS_27087 s700_800 11.X MC/ServiceGuard and SG-OPS Edition A.11.13
PHKL_27498 s700_800 11.11 Possible HPMC with PCI-to-PCI bridge
PHSS_27668 s700_800 11.X OV SIP3.0 SIP3.0: web server update
PHNE_27403 s700_800 11.11 J2793B X.25 SX25-HPerf/SYNC-WAN
PHNE_25181 s700_800 11.00 R6.11.00 SNAplus2 Link/Common, TN3270 patch
PHKL_27502 s700_800 11.11 MO 4k sector size; FIFO; Event Port; perf
PHKL_27314 s700_800 11.00 HPMC, FC conn, chassis log, I20 RAID, reboot
PHCO_27565 s700_800 11.00 sort(1) cumulative patch
PHCO_27373 s700_800 11.04 (VVOS) cumulative passwd(1) patch
PHCO_26522 s700_800 11.11 cumulative patch for syslogd(1M)
PHSS_27499 s700_800 11.04 VirtualVault 4.0 TGA daemon Update
PHNE_27223 s700_800 11.00 NTP timeservices upgrade plus utilities
PHKL_27553 s700_800 11.00 PSW, PA-8700, panic, printf cumulative fix
PHSS_27639 s700_800 11.X OV NNM6.2 http server fix
PHSS_27542 s700_800 11.04 (VVOS) Xserver cumulative patch
PHSS_27489 s700_800 11.00 OV SA1.02 CORBA 1.02-5 Fix
PHSS_27440 s700_800 11.04 HP Praesidium Webproxy 1.0 server update
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHSS_27342
Date Loaded: 20020809
Title: s700_800 11.00 OV ITO6.0X Service Navigator Patch A.06.13
Patch Name: PHSS_27342
Patch Description: s700_800 11.00 OV ITO6.0X Service Navigator Patch A.06.13
Creation Date: 02/07/09
Post Date: 02/08/09
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products:
OpenView IT/Operations 6.0
Filesets:
OVOPC-SVC.OVOPC-SVC-MGR,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP
OVOPC-SVC.OVOPC-SVC-ENG,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP
OVOPC-SVC.OVOPC-SVC-JPN,fr=A.06.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_27342
Symptoms:
PHSS_27342:
- SR: B555011914
In rare cases the opcsvcm process might abort if there
are problems during the errorhandling of configuration
requests (list, add, replace, remove of services).
- SR: B555013351
opcservice might hang on certain systems after the
operation is done and the result is displayed.
- SR: B555013943
A complete removal of services with 'opcservice -remove'
doesn't trigger a config change notification message to
the JavaGUI clients so you'll have an outdated service
tree but don't know it.
- SR: B555013950
In some rare cases the opcsvcm process aborts due to an
uncaught exception which might occur after a config
request has been processed.
- SR: H553000299
opcservice -check doesn't detect if a service has
multiple associations to a source.
PHSS_25359:
- SR: B555011808
The example service file cluster.xml contains a very
strange service.
- SR: B555011809
opcservice is not able to load the ITO 5 example service
cluster.svc
- SR: B555011896
Service calculation rules with multiple thresholds are
not properly converted into the ITO 6 XML format if they
don't specify the threshold percentage. The line
"warning 0% setto normal" is properly converted, but
the line "warning setto normal" would be ignored.
- SR: B555011903
Service changes are not propagated after a server restart
if the service definitions contain MultiCalcRules where
only some severities are mentioned: all not mentioned
severities are ignored.
- SR: B555012331
JavaGUI startup is very slow if you have lots of services
and there are lots of service status changes during the
startup. E.g. if you have a 3 MB service repository and
get one status change per second the startup time will
grow from 40 seconds up to 10 minutes.
- SR: 8606224584
You don't know when the opcsvcm is done with it's
initialization as there is no status info except in
the tracing.
PHSS_24741:
- SR: B555007667
opcservice -log does not replace the registration for
the same service.
- SR: B555009175
opcsvcconv does not convert all ampersand (&) signs, only
the first ampersand per line.
- SR: B555009794
opcservice -check reports errors for operator assignments
while -add accepts them.
- SR: B555011187
Assigning and adding services is slow if the service
repository is large.
- SR: H553000484
opcservice -calc option doesn't list any calculation
rules.
- SR: B555011805 and B555012121
opcservice does not allow SJIS or other non-ASCII
characters.
- SR: B555011806
Removing the A.06.08 Service Navigator patch removes the
service repository file and logging configuration file.
- SR: B555011159
opcservice -assign does not return an error if the
operator does not exist.
PHSS_23606:
- SR: 8606203780
The example gensvc_ito.sh script creates invalid output
for external nodes ('opcservice -check' won't accept
the resulting service definition). Secondly there was a
typo in the act_opcsv_hbp_status action definition
(hpb instead of hbp).
- SR: B555009686
'opcservice -check' doesn't report any errors other than
"Error: ItoUtil::Error"
- SR: B555010013
If you run 'opcservice -add <filename>' with a filename
which does not exist, you get a strange error:
"Error: XML parse error in 'file:<filename>', line 1,
char 1: missing '<'"
Instead I would expect something like:
"Error: Can't open 'file:/.root/something' for
reading."
Same problem appears for the '-replace <file>' and '-
check <file>' options.
- SR: B555010169
The service engine (opcsvcm) sometime crashes in the
middle of config change operations.
- SR: B555010265
opcservice -dump didn't work, just returned the message:
"Error: File argument missing for 'dump' operation."
- SR: B555010756
The service engine periodically dies if a config change
is finished while a change log to the database is still
in progress
- SR: B555010816
The example service definition cltsvr.xml was garbled.
- SR: B555010877
The opcsvcconf service definition conversion utility has
problems converting a service with the ITO 5 syntax if it
contains lines like
use "something" {}
The resulting service definition is garbled.
- SR: H553000306
When using the -remove option with opcservice, the output
is always: "Successfully removed services" even if you
remove actions/proprules/calcrules/operators which didn't
exist.
- SR: B555011101
'opcservice -remove' sometimes does not remove all
services if the service repository is too complex.
PHSS_22696:
- The output of opcservice -list -xml contained invalid
tags for actions and calculation rules. Therefore this
output could not be fed into the service engine again.
- 'opcservice -replace' does not replace services which
are assigned to an operator.
- Service Navigator status colors aren't updated after
opcsv -start
- If a propagation rule with 'Ignore' is used, the service
status in the Service Navigator is not propagated for
any service.
PHSS_22306:
- Wrong parameter checking in opcservice shell script
leads to unhandled shell error messages.
- the first assignment of a service to an operator which
did not yet exist in the service engine was not
performed
- service engine core throws a CNotFound exception when
the requested object is not known.
- Service data in code sets other than ISO8859-1 leads to
unreadable output of the opcservice command
- Service Engine: replace removes association to common
twice contained subservice
- operator is not informed if there is a change in Service
configuration and he has to reload config (in JavaUI)
- Default propagation rules are not correctly written to
the service engine's service repository if the
propagation rule has both a default rule and severity
specific rules.
- Connection to service engine fails after 12 hours use
- Improved thread handling and process termination
- wrong include dependencies in results.dtd file
- opcservice does not return errorcodes
- When using multiple instances of the class ServiceEngine
in a service API program, it core dumps when creating
the second instance.
- When a service for which logging has been enabled is
removed and the service engine restarted, the engine
crashes and is not able to restart.
- Can not use service examples in
/opt/OV/OpC/examples/services directory out of box
- Opcservice and opcsvcterm coredump
- The service navigator API starts a signal handler
thread, thus applications using the SN-API cannot use
signals at all.
Defect Description:
PHSS_27342:
- SR: B555013351
This is probably an OS problem, but we can implement
a workaround in opcservice so that exits as soon as the
result is delivered by opcsvcm, even if the connection
to opcsvcm is still open.
- SR: B555013950
In some rare cases the opcsvcm process aborts due to an
uncaught exception which might occur after a config
request has been processed. The exception has to be
caught and an error into the opcerror log file has to
be generated.
for SR's not listed in this section please see
the list of symptoms
PHSS_25359:
- SR: B555011808
The example service file cluster.xml contains a very
strange service. It was not properly converted from the
ITO 5 example cluster.svc
- SR: B555011808
The opcsvcm had problems loading an <Action> without
a defined <Command> or <URL>.
For a complete fix you need the A.06.10 libopcsvcreader
coming with the A.06.10 intermediate ITO server patch.
- SR: B555011903
The service engine doesn't properly add services which
have <CalcMultiThreshold>s where only some but not all
severities are handled because it sets all not mentioned
severities to "Normal" per default.
- SR: B555012331
The service engine locking mechanism gives the status
changes a higher prio over the service tree query,
so if there are lots of changes, the query won't get
a lock on the service engine to get its information.
Now you can specify how long the service engine will
wait after some changes are processed until the next
chunk is read from the queue. Use the opcsvinfo variable
SVCMSG_READ_INTERVAL to define the sleep interval in
seconds (default is '1'). Don't use too high numbers
because those status changes which are acknowledged
within the same interval will not be logged.
-SR: 8606224584
You don't know when the opcsvcm is done with it's
initialization so we added the status to the 'ps -ef'
info which now returns either:
... opcsvcm: initializing
or
... opcsvcm: running
for SR's not listed in this section please see
the list of symptoms
PHSS_24741:
- SR: B555011187
Assigning and adding services is slow if the service
repository is large because for each operation the
assignment tables in the database are rebuilt instead
of just adding the new information.
- SR: H553000484
opcservice -calc option doesn't list any calculation
rules because a wrong output message from the message
catalog was used.
for SR's not listed in this section please see
the list of symptoms
PHSS_23606:
- SR: B555009686
The error handling of opcservice contained a bug so that
all the information about a service definition parse
error was lost before the error was reported.
- SR: B555010013
opcservice didn't check whether a file exists before
reading it. This check was now added.
- SR: B555010169
The service engine didn't use a proper locking mechanism
to disallow multiple parallel config change operations.
- SR: B555010756
The service engine periodically dies if a config change
is finished while a change log to the database is still
in progress because the config change task doesn't
wait for still active threads but destroys some resources
needed by these threads.
- SR: B555010816
The example service definition cltsvr.xml was garbled
because it hadn't been properly converted from the
ITO A.05.30 file cltsvr.svc
- SR: B555010877
The opcsvcconf service definition conversion utility has
problems converting a service with the ITO 5 syntax if it
contains lines like
use "something" {}
As a workaround you had to use
use "something";
Now each '{}' is implicitly converted to ';' and you
get a WARNING if there is still more than one bracket
in one line.
- SR: B555011101
'opcservice -remove' sometimes does not remove all
services if the service repository is too complex
so opcservice has to call the opcsvcm again to remove
all services until they are really gone.
- SR: H553000306
The opcsvcm tries to remove the service from the list
of services and creates an error but the error was not
passed back to the callin opcservice command so far.
for SR's not listed in this section please see
the list of symptoms
PHSS_22696:
see the list of symptoms
PHSS_22306:
see the list of symptoms
Enhancement:
No
SR:
R555008695 H555003286 H553000484 H553000358 H553000348
H553000338 H553000306 H553000299 B555013950 B555013943
B555013351 B555012331 B555012121 B555011914 B555011903
B555011896 B555011809 B555011808 B555011806 B555011805
B555011187 B555011159 B555011101 B555010877 B555010816
B555010756 B555010265 B555010169 B555010013 B555009794
B555009686 B555009552 B555009195 B555009175 B555009076
B555008494 B555008339 B555008271 B555008225 B555007848
B555007667 B555007597 B555007588 B555007585 B555007584
B555007514 B555007448 B555007447 8606224584 8606203780
8606160383
Patch Files:
OVOPC-SVC.OVOPC-SVC-MGR,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/man/man1m.Z/opcservice.1m
/opt/OV/www/htdocs/ito_man/opcservice.1m.html
/opt/OV/bin/OpC/opcsvcdwn
/opt/OV/lib/libopcsvccore.sl
/etc/opt/OV/share/conf/OpC/mgmt_sv/dtds/results.dtd
/opt/OV/lib/libopcsvcclient.sl
/opt/OV/bin/OpC/opcservice
/opt/OV/bin/OpC/opcservice.sh
/opt/OV/bin/OpC/opcsvcconv
/opt/OV/bin/OpC/opcsvcterm
/opt/OV/lib/libopcsvcrequest.sl
/opt/OV/bin/OpC/opcsvcm
/opt/OV/lib/libopcsvclog.sl
/opt/OV/lib/libopcsvcmsg.sl
/opt/OV/lib/libopcsvcmodel.sl
/opt/OV/lib/libopcsvcsession.sl
/opt/OV/www/htdocs/ito_svc/opcsvcweb
OVOPC-SVC.OVOPC-SVC-ENG,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/lib/nls/C/opcsvc.cat
/opt/OV/OpC/examples/services/action.xml
/opt/OV/OpC/examples/services/banking.xml
/opt/OV/OpC/examples/services/carsupply.xml
/opt/OV/OpC/examples/services/cltsvr.xml
/opt/OV/OpC/examples/services/cluster.xml
/opt/OV/OpC/examples/services/diskless.xml
/opt/OV/OpC/examples/services/email.xml
/opt/OV/OpC/examples/services/factor.xml
/opt/OV/OpC/examples/services/fileserv.xml
/opt/OV/OpC/examples/services/gensvc_ito.sh
/opt/OV/OpC/examples/services/gensvc_ora.sh
/opt/OV/OpC/examples/services/georga.xml
/opt/OV/OpC/examples/services/icons.xml
/opt/OV/OpC/examples/services/inet.xml
/opt/OV/OpC/examples/services/isp.xml
/opt/OV/OpC/examples/services/ito.xml
/opt/OV/OpC/examples/services/local.xml
/opt/OV/OpC/examples/services/lvm.xml
/opt/OV/OpC/examples/services/outage.xml
/opt/OV/OpC/examples/services/perf.xml
/opt/OV/OpC/examples/services/redundant.xml
/opt/OV/OpC/examples/services/res.xml
/opt/OV/OpC/examples/services/sap.xml
OVOPC-SVC.OVOPC-SVC-JPN,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/lib/nls/ja_JP.SJIS/opcsvc.cat
what(1) Output:
OVOPC-SVC.OVOPC-SVC-MGR,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/man/man1m.Z/opcservice.1m:
None
/opt/OV/www/htdocs/ito_man/opcservice.1m.html:
None
/opt/OV/bin/OpC/opcsvcdwn:
HP OpenView VantagePoint A.06.13 PHSS_27342 (07/09/0
2)
/opt/OV/lib/libopcsvccore.sl:
HP OpenView VantagePoint A.06.13 PHSS_27342 (07/09/0
2)
/etc/opt/OV/share/conf/OpC/mgmt_sv/dtds/results.dtd:
None
/opt/OV/lib/libopcsvcclient.sl:
HP OpenView VantagePoint A.06.13 PHSS_27342 (07/09/0
2)
/opt/OV/bin/OpC/opcservice:
HP OpenView VantagePoint A.06.13 PHSS_27342 (07/09/0
2)
/opt/OV/bin/OpC/opcservice.sh:
HP OpenView VantagePoint A.06.13 (07/09/02)
/opt/OV/bin/OpC/opcsvcconv:
HP OpenView VantagePoint A.06.13 (07/09/02)
/opt/OV/bin/OpC/opcsvcterm:
HP OpenView VantagePoint A.06.13 PHSS_27342 (07/09/0
2)
/opt/OV/lib/libopcsvcrequest.sl:
HP OpenView VantagePoint A.06.13 PHSS_27342 (07/09/0
2)
/opt/OV/bin/OpC/opcsvcm:
HP OpenView VantagePoint A.06.13 PHSS_27342 (07/09/0
2)
/opt/OV/lib/libopcsvclog.sl:
HP OpenView VantagePoint A.06.13 PHSS_27342 (07/09/0
2)
/opt/OV/lib/libopcsvcmsg.sl:
HP OpenView VantagePoint A.06.13 PHSS_27342 (07/09/0
2)
/opt/OV/lib/libopcsvcmodel.sl:
HP OpenView VantagePoint A.06.13 PHSS_27342 (07/09/0
2)
/opt/OV/lib/libopcsvcsession.sl:
HP OpenView VantagePoint A.06.13 PHSS_27342 (07/09/0
2)
/opt/OV/www/htdocs/ito_svc/opcsvcweb:
HP OpenView VantagePoint A.06.13 (07/09/02)
OVOPC-SVC.OVOPC-SVC-ENG,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/lib/nls/C/opcsvc.cat:
None
/opt/OV/OpC/examples/services/action.xml:
None
/opt/OV/OpC/examples/services/banking.xml:
None
/opt/OV/OpC/examples/services/carsupply.xml:
None
/opt/OV/OpC/examples/services/cltsvr.xml:
None
/opt/OV/OpC/examples/services/cluster.xml:
None
/opt/OV/OpC/examples/services/diskless.xml:
None
/opt/OV/OpC/examples/services/email.xml:
None
/opt/OV/OpC/examples/services/factor.xml:
None
/opt/OV/OpC/examples/services/fileserv.xml:
None
/opt/OV/OpC/examples/services/gensvc_ito.sh:
None
/opt/OV/OpC/examples/services/gensvc_ora.sh:
None
/opt/OV/OpC/examples/services/georga.xml:
None
/opt/OV/OpC/examples/services/icons.xml:
None
/opt/OV/OpC/examples/services/inet.xml:
None
/opt/OV/OpC/examples/services/isp.xml:
None
/opt/OV/OpC/examples/services/ito.xml:
None
/opt/OV/OpC/examples/services/local.xml:
None
/opt/OV/OpC/examples/services/lvm.xml:
None
/opt/OV/OpC/examples/services/outage.xml:
None
/opt/OV/OpC/examples/services/perf.xml:
None
/opt/OV/OpC/examples/services/redundant.xml:
None
/opt/OV/OpC/examples/services/res.xml:
None
/opt/OV/OpC/examples/services/sap.xml:
None
OVOPC-SVC.OVOPC-SVC-JPN,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/lib/nls/ja_JP.SJIS/opcsvc.cat:
None
cksum(1) Output:
OVOPC-SVC.OVOPC-SVC-MGR,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
1588030240 4855 /opt/OV/man/man1m.Z/opcservice.1m
572636540 13973 /opt/OV/www/htdocs/ito_man/
opcservice.1m.html
3393963216 40960 /opt/OV/bin/OpC/opcsvcdwn
2385950651 1163264 /opt/OV/lib/libopcsvccore.sl
3283155182 1637 /etc/opt/OV/share/conf/OpC/mgmt_sv/dtds/
results.dtd
1021195631 1003520 /opt/OV/lib/libopcsvcclient.sl
2920144922 118784 /opt/OV/bin/OpC/opcservice
4175585626 2155 /opt/OV/bin/OpC/opcservice.sh
4279783248 30168 /opt/OV/bin/OpC/opcsvcconv
4105650848 65536 /opt/OV/bin/OpC/opcsvcterm
1711283286 516096 /opt/OV/lib/libopcsvcrequest.sl
708580734 151552 /opt/OV/bin/OpC/opcsvcm
636399252 294912 /opt/OV/lib/libopcsvclog.sl
138038899 176128 /opt/OV/lib/libopcsvcmsg.sl
631210675 749568 /opt/OV/lib/libopcsvcmodel.sl
3530193076 311296 /opt/OV/lib/libopcsvcsession.sl
4119491901 361 /opt/OV/www/htdocs/ito_svc/opcsvcweb
OVOPC-SVC.OVOPC-SVC-ENG,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
4294173203 6271 /opt/OV/lib/nls/C/opcsvc.cat
107001399 3311 /opt/OV/OpC/examples/services/action.xml
2322032178 9919 /opt/OV/OpC/examples/services/banking.xml
1562479766 8086 /opt/OV/OpC/examples/services/carsupply.xml
2776165449 6085 /opt/OV/OpC/examples/services/cltsvr.xml
1931399694 8048 /opt/OV/OpC/examples/services/cluster.xml
1287705731 3317 /opt/OV/OpC/examples/services/diskless.xml
2111682562 5670 /opt/OV/OpC/examples/services/email.xml
4248035457 1615 /opt/OV/OpC/examples/services/factor.xml
3185975603 8349 /opt/OV/OpC/examples/services/fileserv.xml
4146886487 13221 /opt/OV/OpC/examples/services/gensvc_ito.sh
1955479293 5134 /opt/OV/OpC/examples/services/gensvc_ora.sh
249825497 4998 /opt/OV/OpC/examples/services/georga.xml
1080579723 8200 /opt/OV/OpC/examples/services/icons.xml
4070043959 10418 /opt/OV/OpC/examples/services/inet.xml
292674876 15385 /opt/OV/OpC/examples/services/isp.xml
3232631873 26403 /opt/OV/OpC/examples/services/ito.xml
2944081597 842 /opt/OV/OpC/examples/services/local.xml
3863707930 4870 /opt/OV/OpC/examples/services/lvm.xml
974559619 3097 /opt/OV/OpC/examples/services/outage.xml
3518895756 4777 /opt/OV/OpC/examples/services/perf.xml
2017571346 1900 /opt/OV/OpC/examples/services/redundant.xml
61262513 2403 /opt/OV/OpC/examples/services/res.xml
571892809 12507 /opt/OV/OpC/examples/services/sap.xml
OVOPC-SVC.OVOPC-SVC-JPN,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
1334218497 6117 /opt/OV/lib/nls/ja_JP.SJIS/opcsvc.cat
Patch Conflicts: None
Patch Dependencies:
s700: 11.00: PHSS_24264
s800: 11.00: PHSS_24264
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_25359 PHSS_24741 PHSS_23606 PHSS_22696 PHSS_22306
Equivalent Patches: None
Patch Package Size: 4820 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_27342
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_27342.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_27342. 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_27342.text file is
available in the product readme:
swlist -l product -a readme -d 
/tmp/PHSS_27342.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_27342.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
(A) Patch Installation Instructions
-------------------------------
(A1) Stop all VPO processes on your Management Server;
this includes manager processes, communication
processes and user-interface processes on the
machine.
- Stop all the VPO GUIs that are running, by using
the "File:Exit" menubar item
- If you are running VPO in a MC/ServiceGuard
installation, put the VPO MC/SG package into
maintenance mode:
# touch /tmp/maint_NNM
- Stop the VPO Manager processes:
# ovstop opc ovoacomm
If any VPO process is still running, kill it
manually:
# kill -9 <pid-of-orphaned-process>
If you are running VPO in a MC/ServiceGuard
installation:
- Apply this patch to all MC/SG cluster nodes
(A2) Install the patch, following the standard installation
instructions (see above).
(A3) After installing PHSS_27342, restart the VPO
processes on your Management Server system:
- Restart the VPO Manager processes, and check that
the processes are running:
# /opt/OV/bin/OpC/opcsv -start
# /opt/OV/bin/OpC/opcsv -status
- If you are running VPO in a MC/ServiceGuard
installation, remove the maintenance mode flag:
# rm /tmp/maint_NNM
(B) Patch Deinstallation Instructions
---------------------------------
(B1) To deinstall the patch PHSS_27342 run swremove:
NOTE: Before removing the patch, stop all
VPO server processes, as described in
the Patch Installation Instructions (A1).
# swremove PHSS_27342
-----End of Document ID: PHSS_27342------------------------------------------
Document ID: PHSS_27087
Date Loaded: 20020809
Title: s700_800 11.X MC/ServiceGuard and SG-OPS Edition A.11.13
Patch Name: PHSS_27087
Patch Description: s700_800 11.X MC/ServiceGuard and SG-OPS Edition A.11.13
Creation Date: 02/05/14
Post Date: 02/08/09
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-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_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_27087
Symptoms:
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_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_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
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-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: 07/14/2002; PATCH: PHSS_27087
MC/ServiceGuard Product $Revision: 82.2 $
/usr/sbin/cmhaltpkg:
Build date: Tue Jul 16 19:16:28 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmhaltserv:
Build date: Tue Jul 16 19:16:28 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmmakepkg:
Build date: Tue Jul 16 19:16:28 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmmigrate:
Build date: Tue Jul 16 19:16:28 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmmodnet:
Build date: Tue Jul 16 19:16:28 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmmodpkg:
Build date: Tue Jul 16 19:16:28 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmrunpkg:
Build date: Tue Jul 16 19:16:28 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmrunserv:
Build date: Tue Jul 16 19:16:28 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmstartres:
Build date: Tue Jul 16 19:16:28 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmstopres:
Build date: Tue Jul 16 19:16:28 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Commands
Command Cln
Command Srv
Config
Command Utils
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
Cluster Management Provider Library
Serviceguard Schema 1.3.1
Build date: Tue Jul 16 19:26:42 PDT 2002
Build id: ibld_sgops_a1113patch
/opt/cmom/providers/qsprovider.omp:
Build date: Tue Jul 16 19:26:59 PDT 2002
Build id: ibld_sgops_a1113patch
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: Tue Jul 16 19:19:49 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
ATS Headers
API
Config DB
CommunicationSrv
Config
Local Comm
Util
/usr/sbin/stapplyconf:
Advanced Tape Support commands
Build date: Tue Jul 16 19:20:40 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
ATS Headers
ATS Utils
Command Cln
Command Srv
Command Utils
Config
Local Comm
Util
/usr/sbin/stcheckconf:
Advanced Tape Support commands
Build date: Tue Jul 16 19:20:40 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
ATS Headers
ATS Utils
Command Cln
Command Srv
Command Utils
Config
Local Comm
Util
/usr/sbin/stdeleteconf:
Advanced Tape Support commands
Build date: Tue Jul 16 19:20:40 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
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: Tue Jul 16 19:20:40 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
ATS Headers
ATS Utils
Command Cln
Command Srv
Command Utils
Config
Local Comm
Util
/usr/sbin/stquerycl:
Advanced Tape Support commands
Build date: Tue Jul 16 19:20:40 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
ATS Headers
ATS Utils
Command Cln
Command Srv
Command Utils
Config
Local Comm
Util
/usr/sbin/streclaim:
Advanced Tape Support commands
Build date: Tue Jul 16 19:20:40 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
ATS Headers
ATS Utils
Command Cln
Command Srv
Command Utils
Config
Local Comm
Util
/usr/sbin/stsetlog:
Advanced Tape Support commands
Build date: Tue Jul 16 19:20:40 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
ATS Headers
ATS Utils
Command Cln
Command Srv
Command Utils
Config
Local Comm
Util
/usr/sbin/stviewcl:
Advanced Tape Support commands
Build date: Tue Jul 16 19:20:40 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
ATS Headers
ATS Utils
Command Cln
Command Srv
Command Utils
Config
Local Comm
Util
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: 07/14/2002; PATCH: PHSS_27087
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Local Comm
Config
API
Util
/opt/nmapi/8.0/lib/libnmapi_64.a:
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Local Comm
Config
API
Util
/opt/nmapi/nmapi2/lib/libnmapi2.1:
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
NMAPI2 32
GMAPI 32
Build date: Tue Jul 16 19:23:11 PDT 2002
Build id: ibld_sgops_a1113patch
/opt/nmapi/nmapi2/lib/libnmapi2.sl:
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
NMAPI2 32
GMAPI 32
Build date: Tue Jul 16 19:23:11 PDT 2002
Build id: ibld_sgops_a1113patch
/opt/nmapi/nmapi2/lib/pa20_64/libnmapi2.1:
Build date: Tue Jul 16 19:27:39 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
NMAPI2 64
GMAPI 64
/opt/nmapi/nmapi2/lib/pa20_64/libnmapi2.sl:
Build date: Tue Jul 16 19:27:39 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
NMAPI2 64
GMAPI 64
/usr/contrib/bin/gmsetlog:
HP92453-02A.10.20 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
Build date: Tue Jul 16 19:22:49 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
GMAPI 32
/usr/lbin/cmgmsd:
HP92453-02A.10.20 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
Build date: Tue Jul 16 19:22:40 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
/usr/lib/libcmdlm.1:
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
ServiceGuard OPS Edition Product $Revision: 82.2 $
/usr/lib/libcmdlm.dlm.1:
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
ServiceGuard OPS Edition Product $Revision: 82.2 $
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: Tue Jul 16 19:16:28 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Commands
Command Cln
Command Srv
Config
Local Comm
Util
/usr/contrib/bin/cmsetsafety:
Build date: Tue Jul 16 19:16:28 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
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: Tue Jul 16 19:13:55 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
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: Tue Jul 16 19:15:41 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
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: Tue Jul 16 19:15:41 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Log Daemon
Local Comm
Util
/usr/lbin/cmlvmd:
HP92453-02A.10.20 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
Build date: Tue Jul 16 19:10:58 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Cluster LVM
Local Comm
Util
/usr/lbin/cmsnmpd:
Build date: Tue Jul 16 19:18:41 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
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: Tue Jul 16 19:10:14 PDT 2002
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: 07/14/2002; PATCH: PHSS_27087
GUI
Config
Command Cln
Command Utils
Local Comm
Util
/usr/lib/libcmcore.1:
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Cluster Monitor Product $Revision: 82.2 $
/usr/lib/libcmcore.sl:
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Cluster Monitor Product $Revision: 82.2 $
/usr/lib/libcmdlm.sl:
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
ServiceGuard OPS Edition Product $Revision: 82.2 $
/usr/lib/libcmpkg.sl:
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
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: 07/14/2002; PATCH: PHSS_27087
Cluster Monitor Product Only $Revision: 82.2 $
/usr/newconfig/usr/lib/libcmpkg.1:
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Cluster Monitor Product Only $Revision: 82.2 $
/usr/sbin/cmapplyconf:
Build date: Tue Jul 16 19:16:28 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmcheckconf:
Build date: Tue Jul 16 19:16:28 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmdeleteconf:
Build date: Tue Jul 16 19:16:28 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmgetconf:
Build date: Tue Jul 16 19:16:28 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmhaltcl:
Build date: Tue Jul 16 19:16:28 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmhaltnode:
Build date: Tue Jul 16 19:16:28 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmquerycl:
Build date: Tue Jul 16 19:16:28 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmruncl:
Build date: Tue Jul 16 19:16:28 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmrunnode:
Build date: Tue Jul 16 19:16:28 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmscancl:
None
/usr/sbin/cmviewcl:
Build date: Tue Jul 16 19:16:28 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Commands
Command Cln
Command Srv
Config
Command Utils
Local Comm
Util
/usr/sbin/cmviewconf:
Build date: Tue Jul 16 19:18:55 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Tools
/usr/sbin/convert:
Build date: Tue Jul 16 19:18:55 PDT 2002
Build id: ibld_sgops_a1113patch
A.11.13 Date: 07/14/2002; PATCH: PHSS_27087
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Tools
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
844425754 12288 /usr/lib/libcmpkg.1
3778019870 2437120 /usr/sbin/cmhaltpkg
3778019870 2437120 /usr/sbin/cmhaltserv
3778019870 2437120 /usr/sbin/cmmakepkg
3778019870 2437120 /usr/sbin/cmmigrate
3778019870 2437120 /usr/sbin/cmmodnet
3778019870 2437120 /usr/sbin/cmmodpkg
3778019870 2437120 /usr/sbin/cmrunpkg
3778019870 2437120 /usr/sbin/cmrunserv
3778019870 2437120 /usr/sbin/cmstartres
3778019870 2437120 /usr/sbin/cmstopres
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:
2800430484 2940928 /opt/cmom/providers/cmprovider.omp
170429374 32768 /opt/cmom/providers/qsprovider.omp
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
4039259480 1111760 /usr/lbin/cmtaped
58910841 2207744 /usr/sbin/stapplyconf
58910841 2207744 /usr/sbin/stcheckconf
58910841 2207744 /usr/sbin/stdeleteconf
1611118997 79568 /usr/sbin/stdisplay
58910841 2207744 /usr/sbin/stgetconf
58910841 2207744 /usr/sbin/stquerycl
58910841 2207744 /usr/sbin/streclaim
58910841 2207744 /usr/sbin/stsetlog
58910841 2207744 /usr/sbin/stviewcl
DLM-NMAPI.CM-NMAPI,fr=A.11.13,fa=HP-UX_B.11.00_32/64,v=HP:
1101311740 2300340 /opt/nmapi/8.0/lib/libnmapi_32.a
968387629 1652190 /opt/nmapi/8.0/lib/libnmapi_64.a
2940050303 270336 /opt/nmapi/nmapi2/lib/libnmapi2.1
2940050303 270336 /opt/nmapi/nmapi2/lib/libnmapi2.sl
3273513519 146320 /opt/nmapi/nmapi2/lib/pa20_64/libnmapi2.1
3273513519 146320 /opt/nmapi/nmapi2/lib/pa20_64/libnmapi2.sl
648222992 190160 /usr/contrib/bin/gmsetlog
2460446436 1058512 /usr/lbin/cmgmsd
2311829900 12288 /usr/lib/libcmdlm.1
2311829900 12288 /usr/lib/libcmdlm.dlm.1
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
4197664235 1126400 /usr/contrib/bin/cmsetlog
4197664235 1126400 /usr/contrib/bin/cmsetsafety
3600978113 65536 /usr/contrib/bin/get_sn
2601926851 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
3035118213 1443536 /usr/lbin/cmclconfd
143134157 3442384 /usr/lbin/cmcld
2631825329 184320 /usr/lbin/cmlogd
2464319369 1021648 /usr/lbin/cmlvmd
23330266 2162688 /usr/lbin/cmsnmpd
2611831408 206544 /usr/lbin/cmsrvassistd
3032011187 3282640 /usr/lbin/cmui
1337201414 12288 /usr/lib/libcmcore.1
1337201414 12288 /usr/lib/libcmcore.sl
2311829900 12288 /usr/lib/libcmdlm.sl
844425754 12288 /usr/lib/libcmpkg.sl
3718833304 12288 /usr/lib/libcmres.1
3718833304 12288 /usr/lib/libcmres.sl
2573719325 479232 /usr/lib/libsgcl.2
2573719325 479232 /usr/lib/libsgcl.sl
3667422374 12288 /usr/newconfig/usr/lib/libcmdlm.1
3639732566 12288 /usr/newconfig/usr/lib/libcmpkg.1
3778019870 2437120 /usr/sbin/cmapplyconf
3778019870 2437120 /usr/sbin/cmcheckconf
3778019870 2437120 /usr/sbin/cmdeleteconf
3778019870 2437120 /usr/sbin/cmgetconf
3778019870 2437120 /usr/sbin/cmhaltcl
3778019870 2437120 /usr/sbin/cmhaltnode
3778019870 2437120 /usr/sbin/cmquerycl
3778019870 2437120 /usr/sbin/cmruncl
3778019870 2437120 /usr/sbin/cmrunnode
1867742789 17221 /usr/sbin/cmscancl
3778019870 2437120 /usr/sbin/cmviewcl
2437196825 1806336 /usr/sbin/cmviewconf
282694595 1867776 /usr/sbin/convert
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_26928 PHSS_26674 PHSS_26180 PHSS_25915 PHSS_25124 PHSS_24678
Equivalent Patches: None
Patch Package Size: 33830 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_27087
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_27087.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_27087. 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_27087.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_27087.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_27087.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_27087------------------------------------------
Document ID: PHKL_27498
Date Loaded: 20020809
Title: s700_800 11.11 Possible HPMC with PCI-to-PCI bridge
Patch Name: PHKL_27498
Patch Description: s700_800 11.11 Possible HPMC with PCI-to-PCI bridge
Creation Date: 02/07/14
Post Date: 02/08/09
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_27498: OTHER
HPMC on A/L/N - class systems with A5838 SCSI/LAN
combo card.
Category Tags:
defect_repair general_release critical
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_27498
Symptoms:
PHKL_27498:
( SR:8606250050 CR:JAGae16432 )
On N-class, L-class, or A-class systems that have an A5838
SCSI/LAN combo card, the system might experience a High
Priority Machine Check (HPMC) when the SCSI interface on the
A5838 is reset.
Defect Description:
PHKL_27498:
( SR:8606250050 CR:JAGae16432 )
The A5838 combo card contains a built-in PCI-to-PCI bridge.
When the SCSI interface on the card goes into reset, the
SCSI driver does not permit any I/O though the interface.
This caused I/O activity to back up behind the PCI-to-PCI
bridge. The bridge implements a timer, and if an I/O is
behind the bridge for longer than the timer permits, the
timer expires and the system will take an HPMC.
Resolution:
The PCI-to-PCI bridge code was changed to turn off the
discard timer. When this timer is disabled, there will not
be an HPMC if an I/O waits behind the bridge for an
unusually long time.
SR:
8606250050
Patch Files:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libpci.a(p2pb_cdio.o)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libpci.a(p2pb_cdio.o)
what(1) Output:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libpci.a(p2pb_cdio.o):
p2pb_cdio.c $Date: 2002/07/12 13:43:55 $Revision: r1
1.11/1 PATCH_11.11 (PHKL_27498)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libpci.a(p2pb_cdio.o):
p2pb_cdio.c $Date: 2002/07/12 13:43:55 $Revision: r1
1.11/1 PATCH_11.11 (PHKL_27498)
cksum(1) Output:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
1889886709 4960 /usr/conf/lib/libpci.a(p2pb_cdio.o)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
676961648 10728 /usr/conf/lib/libpci.a(p2pb_cdio.o)
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches: None
Patch Package Size: 40 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_27498
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_27498.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_27498. 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_27498.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHKL_27498.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_27498.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHKL_27498------------------------------------------
Document ID: PHSS_27668
Date Loaded: 20020808
Title: s700_800 11.X OV SIP3.0 SIP3.0: web server update
Patch Name: PHSS_27668
Patch Description: s700_800 11.X OV SIP3.0 SIP3.0: web server update
Creation Date: 02/08/06
Post Date: 02/08/08
Hardware Platforms - OS Releases:
s700: 11.00 11.11
s800: 11.00 11.11
Products:
OpenView Service Information Portal 3.0
Filesets:
HPOVSIP.OVSIP,fr=B.01.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_27668
Symptoms:
PHSS_27668:
web server out of date
PHSS_27547:
web server out of date
Defect Description:
PHSS_27668:
web server out of date
Resolution:
web server updated
PHSS_27547:
web server out of date
Resolution:
web server updated
Enhancement:
No
SR:
8606272863 8606269500
Patch Files:
HPOVSIP.OVSIP,fr=B.01.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/SIP/apache/libexec/httpd.exp
/opt/OV/SIP/apache/libexec/libhttpd.ep
/opt/OV/SIP/apache/libexec/libhttpd.sl
/opt/OV/SIP/apache/libexec/libhttpd.sl.1
/opt/OV/SIP/apache/libexec/libhttpd.sl.1.3
/opt/OV/SIP/apache/libexec/libhttpd.sl.1.3.20
what(1) Output:
HPOVSIP.OVSIP,fr=B.01.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/SIP/apache/libexec/httpd.exp:
None
/opt/OV/SIP/apache/libexec/libhttpd.ep:
None
/opt/OV/SIP/apache/libexec/libhttpd.sl:
patched for CAN-2002-0392 [CERT VU#944335]
/opt/OV/SIP/apache/libexec/libhttpd.sl.1:
patched for CAN-2002-0392 [CERT VU#944335]
/opt/OV/SIP/apache/libexec/libhttpd.sl.1.3:
patched for CAN-2002-0392 [CERT VU#944335]
/opt/OV/SIP/apache/libexec/libhttpd.sl.1.3.20:
patched for CAN-2002-0392 [CERT VU#944335]
cksum(1) Output:
HPOVSIP.OVSIP,fr=B.01.00,fa=HP-UX_B.11.00_32/64,v=HP:
3078222384 7449 /opt/OV/SIP/apache/libexec/httpd.exp
3599790847 20480 /opt/OV/SIP/apache/libexec/libhttpd.ep
2571211339 1314816 /opt/OV/SIP/apache/libexec/libhttpd.sl
2571211339 1314816 /opt/OV/SIP/apache/libexec/libhttpd.sl.1
2571211339 1314816 /opt/OV/SIP/apache/libexec/
libhttpd.sl.1.3
2571211339 1314816 /opt/OV/SIP/apache/libexec/
libhttpd.sl.1.3.20
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_27547
Equivalent Patches:
OVSIPSOL_00005:
sparcSOL: 2.6 2.7 2.8
Patch Package Size: 5200 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_27668
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_27668.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_27668. 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_27668.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_27668.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_27668.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
========================================================
BEFORE LOADING THIS PATCH...
- Stop the Tomcat server.
- If you want to reinstall SIP, then you will have to
remove the patch. Once the re-install is over you
can apply the patch again.
NOTE : Tomcat is not started after the patch is loaded
You will need to manually start it.
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/SIP/patches. Please make
sure this file is in /tmp before installation.
========================================================
-----End of Document ID: PHSS_27668------------------------------------------
Document ID: PHNE_27403
Date Loaded: 20020808
Title: s700_800 11.11 J2793B X.25 SX25-HPerf/SYNC-WAN
Patch Name: PHNE_27403
Patch Description: s700_800 11.11 J2793B X.25 SX25-HPerf/SYNC-WAN
Creation Date: 02/07/31
Post Date: 02/08/08
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products:
SX25-HPerf B.11.11.00; SYNC-WAN B.11.11.00
Filesets:
SX25-HPerf.SX25-HPERF-SAM,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,v=HP
SYNC-WAN.SYNC-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_64,v=HP
SYNC-WAN.SYNC-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_32,v=HP
SX25-HPerf.SX25-HPERF-PAD,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,v=HP
SX25-HPerf.SX25-HPERF-COM,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,v=HP
SX25-HPerf.PA-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_64,v=HP
SX25-HPerf.PA-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_32,v=HP
SX25-HPerf.COM-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_64,v=HP
SX25-HPerf.COM-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_32,v=HP
SYNC-WAN.SYNC-COM,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,v=HP
SX25-HPerf.SX25-HPERF-MAN,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,v=HP
SX25-HPerf.SX25-HPERF-IP,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,v=HP
SX25-HPerf.COM-64SLIB,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,v=HP
SX25-HPerf.SX25-SNMP,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHNE_27403: PANIC CORRUPTION OTHER
JAGae00951 is critical because the X.25 port goes
down and becomes unusable.
JAGad65925 is critical because the X.25 port goes
down and becomes unusable.
PHNE_25596: PANIC
PHNE_23190: PANIC HANG MEMORY_LEAK OTHER
JAGad14826 is critical because it renders the
card nonfunctional.
JAGad40560 is critical because connection can't
be established if multiple listen ports
are configured.
JAGad38177 is critical because only way to
recover is to stop and restart the entire
subsystem.
Category Tags:
defect_repair enhancement general_release critical firmware
panic halts_system corruption memory_leak
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_27403
Symptoms:
PHNE_27403:
1. JAGad02521 / SR 8606133376
There is a typographical error in the "x25check" man
page. "STRMSGSZ" has been spelt wrongly as "STRMSGZ".
2. JAGae00951 / SR 8606231715
The level 2 state toggles between up and down and a lot
of CRC errors, bad frames etc. are reported in statistics.
This problem has been found while the X.25 J3526A card
was connected to a Cisco router using V.35.
3. JAGad97574 / SR 8606228517
When the HP-PB PSI card reports lot of "receive aborts"
(it can be seen by using "x25stat -g" command),
using "x25stat" command many times can lead to system
panic. The following message was seen using "dmesg":
"X.25 problem: No more timeout data structure".
4. JAGad65925 / SR 8606196727
The X.25 level 2 sends an unexpected FRMR frame and it
does not stay up. This problem has been observed with a
NORTEL DPN100 switch. However, it might happen with other
configuration.
5. JAGae30964 / SR 8606266719
Sometimes system panics when stopping X25 J3525A interface
with the following stack trace.
qenable+0xc
wan_rxebl+0x24
J3525_F_RxFrame+0x94
J3525_F_TriggerRxFrame+0xcf4
process_sw_triggers+0x134
sw_service+0x13c
mp_ext_interrupt+0x150
ihandler+0x904
6. JAGae32834 / SR 8606268596
While disabling "x29printd / x29server / x29uucpd"
daemons through SAM the x25 configuration was never
updated.
PHNE_25596:
1. JAGad52014 / SR 8606182798
System panics when following sequence of actions are
performed:
- Start the application which attaches to a PVC for data
transfer.
- Application is terminated/killed.
- Another application is started which attaches to the
same PVC.
- The interface cable for the port is disconnected.
2. JAGad52923 / SR 8606183710
System panics in X.25 socket code when X.25 facilities
are used.
3. JAGad53164 / SR 8606183954
System panicked with the following stack trace:
panic+0x14
report_trap_or_int_and_panic+0x84
trap+0xd9c
nokgdb+0x8
putq_owned+0x190
putq+0x1c
J3526_F_infc+0xb8
sxbinfc+0x58
sxbrsrv+0x388
sq_wrapper+0x94
ioctl_sleep+0x29c
wait_iocack+0x7c
str_istr_ioctl+0x738
hpstreams_ioctl_int+0x6a8
hpstreams_ioctl+0x50
spec_ioctl+0xac
vno_ioctl+0x90
ioctl+0x7c
syscall+0x6f8
$syscallrtn+0x0
4. JAGad54284 / SR 8606185082
x25init returns an error on J3526A card with the message
"Link of wan0012 under lapb0012 failed"
5. JAGad69251 / SR 8606200067
x25stop/x25init hangs on a J3526A card after doing
'ricreset'.
6. JAGad70181 / SR 8606201005
set_timer() may not restart the timer sometimes. This
may lead to LAPB not doing timer recovery operations at
times.
7. JAGad72705 / SR 8606203532
System panics due to spin lock deadlock in the function
J3526_F_time_is_out().
8. JAGad82177 / SR 8606212990
When more than one process/thread is using the same socket
descriptor and the socket is put to non-blocking mode,
the select() on the receive may hang even though there
is data to process.
9. JAGad87223 / SR 8606218073
The system panics in the X.25 socket layer code with the
top of the panic stack containing
"XIQ_F0_a_data_ind+0x168". This panic is observed when the
inbound data is received with 'D' bit set.
10. JAGad87211 / SR 8606218061
Customer cannot start the SNMP x25subagt on PA-RISC 1.1
systems.
PHNE_23190:
1. JAGad36972 / SR 8606167689
System may crash when the J3526A card goes into
"fatal" error mode. When the system crashes the
console message would contain the following message:
"J3526_F_it_handler(): Reject bit set
(CBSP = 0x....) for card 0x....".
2. JAGad34197 / SR 8606164900
Panic on N-class with 8 T1/E1 cards.
3. JAGad14826 / SR 8606145490
Cross-bus deadlock due to DMA stuck in STOPPED state.
4. JAGad36479 / SR 8606167193
Lot of x29server processes shown up in "ps -ef" output
with PPID as 1 (init process).
5. JAGad37977 / SR 8606168699
Non-privileged user is permitted to remove the temporary
files created by others in /var/x25/tmp directory.
6. JAGad39667 / SR 8606170403
System panicked in XIQ_F_handler function during ACC
(Advanced Communications Controller) stress testing.
7. JAGad40560 / SR 8606171296
"x29server" may not accept the second connection,if more
than one listen stream is configured.
8. JAGab77075
3.02 ACC does not generate CLEAR on SVC after shutdown(0)
unlike 2.40 ACC.
9. JAGad38177 / SR 8606168899
x25init sometimes fails with "nc ioctl X25_SET_SNID"
failed message.
10. JAGaa03408
When enabling SX25L3 (PLP) tracing in nettl, it returns
with error: ioctl call on x25 device failed with errno
19 (no such device).
11. JAGad47478 / SR 8606178251
When the J3526A card is reset in a loop for about 1000
times, the system panicked with "Data page fault"
message.
12. JAGad41662 / SR 8606172402
Memory leak (512 bytes) when X25_SETUP_PVC ioctl is
processed.
13. JAGad40862 / SR 8606171598
Need to enhance "x25stat" command to show "VC Up Time"
for all active virtual circuits.
14. JAGad47111 / SR 8606177884
Uni-processor system hangs when SS7 traffic is stopped
and trying to bring down the SS7 subsystem at the same
time.
15. JAGad47117 / SR 8606177890
"ricreset" on J3526A card displays "heartbeat" failure
message.
16. JAGad47673 / SR 8606178446
NetTL tracing for SX25L2 on a J3526A (4-port) card port
logs bad information which "netfmt" is not able to format
properly.
17. JAGad02522 / SR 8606133377
"x25check" does not work with message sizes > 2048 bytes.
Defect Description:
PHNE_27403:
1. JAGad02521 / SR 8606133376
"STRMSGSZ" has been spelt wrongly as "STRMSGZ".
Resolution:
The spelling has been corrected.
2. JAGae00951 / SR 8606231715
The problem was in the firmware. The Rx clock was sent
out as the Tx clock. Hence no clock was being sent on
TXCLOCK OUT.
Resolution:
The problem has been fixed in the firmware.
3. JAGad97574 / SR 8606228517
The firmware on HP-PB PSI card has limited number of
timeout structures. When "receive abort" occurs,
"timeout()" routine is called. If many such events occur
within a small period of time, that will result in all the
timeout structures getting used. Since there are no more
timeout structures left to honour the next request, the
firmware calls panic() resulting in the hang of processor
on the card. Later when the system tries to access the
card (during x25stat command), the system panics due to
some invalid processing.
Resolution:
The firmware code is changed so that additional timeouts
are not called when already one timeout() was pending for
the concerned event. This will ensure only one structure
getting used up even when the event occurs many times in
a small period of time. There by the card is in good shape
and the system will not panic.
4. JAGad65925 / SR 8606196727
The firmware on J3526A card has a problem and the X.25
level 2 sends an unexpected FRMR frame. After this the
level 2 goes down.
Resolution:
The problem has been fixed in the firmware.
5. JAGae30964 / SR 8606266719
One local variable was used before proper initialization.
In the case when it has some non zero garbage value the
control goes to qenable for a null queue and the system
panics.
Resolution:
The local variable has been initialized properly before
the use.
6. JAGae32834 / SR 8606268596
While disabling "x29printd / x29server / x29uucpd"
daemons through SAM the x25 configuration was never
updated.
Resolution:
The X29_SERVICE_STOP routine has been modified to update
configuration file /etc/rc.config.d/x25 properly, while
disabling "x29printd / x29server / x29uucpd" through SAM.
PHNE_25596:
1. JAGad52014 / SR 8606182798
Problem is that when PVC_DETACH request is sent down to
the X25 PLP, the xvc reference is not removed from the
xgldb (glue structure used by the upper multiplexer). So,
after the PVC detach, if cable is disconnected from the
port, the xvc structure gets freed. After this, when
upper stream is being closed, since it still has the
reference to the freed xvc, the system panics due to
invalid memory access.
Resolution:
The fix is to nullify the reference pointers when
N_PVC_DETACH primitive is processed by X25 PLP.
2. JAGad52923 / SR 8606183710
X.25 source reuses the buffer allocated during
the connection establishment for sending the disconnect
request when the socket is closed. The buffer
required for disconnect request is more than the
allocated buffer. Therefore writing to the unallocated
memory will cause the system panic.
Resolution:
The fix is to reuse the buffer only if the buffer
is of required size. Otherwise, allocate a new buffer
and copy the required fields to the newly allocated
buffer.
3. JAGad53164 / SR 8606183954
In the j3526 driver, "putq" routine provided by streams
was used to put a message onto a streams queue. At the
same time, in the corresponding streams module, "getq"
was called (on a different processor). As "putq" doesn't
synchronize the calls into streams module, the race
condition between "putq" and "getq" on the same queue
caused some pointers to go stale and subsequently caused
the system to panic.
Resolution:
All the calls to "putq" were converted to "streams_put"
which will synchronize the entry in to the streams
context by a non streams module. Also, care is taken to
release the streams spin lock before calling
"streams_put".
4. JAGad54284 / SR 8606185082
J3526 Cross-Bus firmware incorrectly derives the index
into Xbus streams table using the stream ID passed by
J3526 host driver. This results in error being returned
from firmware even though the stream is valid.
Resolution:
The fix is to mask off the bits which are not required
when forming the index from the stream ID passed.
5. JAGad69251 / SR 8606200067
After the card is reset, the driver state was not updated
to indicate that the card has been reset. So, when the
driver gets any commands from x25init/x25stop, it will
send down that command to card instead of rejecting it
with an error. Since the card is already reset, it will
not respond to any command and x25init/x25stop will wait
forever for the response from the driver. This will
result in x25init/x25stop application hang.
Resolution:
The fix was to set the driver state to 0 so that any
command other than reset and download down to the card
will result in error being returned.
6. JAGad70181 / SR 8606201005
While step_time() is processing the timers, if set_timer()
is called on the timer which is being processed OR the
next timer in the list, it will not restart the timer.
This will lead to the module which is depending on the
timer not behaving as expected.
Resolution:
set_timer() now saves the time in tm_left, if "in_use" is
set and step_time() checks this and restarts the timer.
7. JAGad72705 / SR 8606203532
In "j3526" driver's streams related code,
"streams_untimeout()" is being called in some places.
"streams_untimeout" will return only when it could
untimeout the timer function with the specified identifier
or when the timer function gets completed. In the j3526
driver code, "streams_untimeout" is called with the card's
streams lock held. The timer function,
J3526_F_time_is_out() also tries to hold the same lock.
This could lead to deadlock as streams_untimeout is
waiting for the timer function to return and the timer
function is waiting for the lock (which was held by the
code that called untimeout).
Resolution:
The driver releases the streams lock before calling
"streams_untimeout" routine.
8. JAGad82177 / SR 8606212990
When more than one process/thread is using the same socket
descriptor, mutex is used to allow exclusive access to
one of the thread. So, when one thread is performing some
operation, any operation by other thread will be blocked
until the first thread completes the operation. But when
the socket is put in non-blocking mode, if the mutex is
already held, the later operation will be dropped instead
of blocking. So, in this particular scenario, when write
operation was going on, the read operation arrived and it
was dropped due to mutex already held. As the read
operation got dropped, the state of the inbound state
machine did not get changed and this resulted in queuing
of inbound data and the arrival of inbound data
was never intimated to the application. As the state never
got changed after this, all the inbound data was just
queued in the streams queue and the select() done by
application will never return read ready.
Resolution:
The fix is to not drop the operation when mutex is held
and block the later operation until it is released.
9. JAGad87223 / SR 8606218073
When the inbound state machine of X.25 socket layer
received the data with 'D' bit set, it formed the
acknowledgement (DAck) message and put it at the head of
its read side queue. Later when the application receives
the data, the inbound state machine calls streams_put() to
enter in to streams context. At this time, two of the
streams requests waiting in the synchronization queue were
processed which should not have been the case. The first
one is data with 'D' bit set. This was processed and
another acknowledgement (DAck) was put at the head of the
read queue. At this point, the state machine goes in to
receiving state. The second request was data packet too.
Since the state was receiving, this request is put at the
end of the read queue. Later, the first DAck message from
the queue was sent out. Now due to the unexpected state
(i.e. receiving), in the subsequent processing, the
remaining two messages in the read side queue got swapped
resulting in the unprocessed data at the head and the
DAck message at the end. When the application received the
data again, this resulted in the first message in the read
queue being sent to the peer wrongly assuming it as DAck
message. And then the state machine processed the next
message assuming it as data and it resulted in the
de-reference of NULL pointer.
Resolution:
Whenever an acknowledgement (DAck) was put at the head of
the read side queue, a flag was set in the PCB structure
for that socket. When this flag was set, any inbound data
was unprocessed and put at the end of the queue. This
prevented the second DAck message being put at the head of
the read queue and also the state was intact across the
streams_put() calls. Thus the swapping of the messages in
the read queue were prevented and the data processing was
streamlined.
10. JAGad87211 / SR 8606218061
For 11.11 release, the (X25) SNMP subagent is generated
for PA RISC 2.0 only. While compiling the sources we did
not use the corresponding option for PA RISC 1.1.
Resolution:
Now at the time of compilation we have added the
corresponding option for PA RISC 1.1.
PHNE_23190:
1. JAGad36972 / SR 8606167689
When "Reject" bit error is encountered, the driver calls
untimeout() to stop the heartbeat checking at the driver
side. It was noticed that, even after calling
untimeout(), due to the timing issues, the heartbeat was
not stopped and the heartbeat routine was being executed.
Occasionally, the system crashed during the execution
of heartbeat function while reading the wdg_count from
the card. The reason for the system crash is that
the card is being accessed while it is in fatal error
state.
Resolution:
When the "Reject" bit error happens, change the
heartbeat status to "Not Started" and when the heartbeat
function is executed, it does not do anything if this
flag is set.
2. JAGad34197 / SR 8606164900
When trying to get the card dump, the driver reads
certain configuration information from the card before
starting the dump process. Due to memory corruption on
the card firmware,the configuration information obtained
from the card was incorrect. This caused a panic when
that information was used to set some flags on the card.
Resolution:
As the setting up of the NMI dump handler during the dump
is no more required, the driver now just issues the NMI
interrupt to the card to start the dump.
3. JAGad14826 / SR 8606145490
The DMA was stopped at some STOP chaining point and
never restarted despite the command at the end of
DMA_F_prog_ch1 routine or any attempts done at any
time.
Resolution:
The DMA register values are saved for checking
various conditions. Now the DMA engine hang condition
check has been corrected. Also the boundary condition
for the descriptor ring overflow is checked now.
4. JAGad36479 / SR 8606167193
The problem is that, when the x29server
process (x29server_2) which is responsible for
serving the connection terminates before the launch
of application, the client process (x29server_3) which
is supposed to turn into application process would
be blocked waiting for synchronization information
from x29server_2 and will be blocked forever as the
x29server_2 process has already terminated. Since
x29server_2 and x29server_3 communicate using ptys
and the master pty is not closed in the
x29server_3 (slave process), the termination of
x29server_2 process has not been intimated to the
x29server_3 process. This caused the hang in
x29server_3 process.
Resolution:
The fix is to close the master pty as soon as the
client process (x29server_3) is created.
5. JAGad37977 / SR 8606168699
/var/x25/tmp directory is used to create temporary
files during the execution of x25init, x25mibstat and
x25stat commands. The files are created and removed
during the execution of the corresponding commands.
Since the directory has 777 permission, it permits
the non-owner to remove the files created by others.
This has been corrected in this patch.
Resolution:
The solution to this is to create the directory with
the sticky bit set (permission 1777). In this way,
only the owner of the file would be allowed to remove
it. The files created in this directory can be made
unreadable to others by setting the umask of the user
to 027.
6. JAGad39667 / SR 8606170403
X.25 socket module received a shutdown indication from
the socket layer. During this, the X.25 socket layer
sends flush signal to inbound and outbound state
machines to flush all the data. First, the signal is
sent to outbound state machine where the state machine
executes streams_put() to flush the outbound data
queued in the streams queue. The streams_put() function
also checks to see if there are any messages queued in
the synchronization queue of the module. In this
particular case, the disconnect indication was present
and it processed that message. While processing the
disconnect indication, the X.25 socket layer made the
"nli_wq" pointer NULL in the pcb. Then, when the flush
signal is sent to inbound state machine, it tried to
access the "nli_wq" pointer and due to NULL pointer
de-reference, the system panicked with "Data page fault".
Resolution:
The fix is to check the value of "nli_wq" pointer before
accessing it.
7. JAGad40560 / SR 8606171296
If the x29server is configured to listen on multiple
addresses, then after the first connection, it may not
accept any connections on other listen streams. This
problem is due to not initializing the "fdsets" (file
descriptor sets) used for select() system call every
time.
Resolution:
The fix is to move the initialization of the "fdsets"
used in select system call inside the loop so that the
"fdsets" are initialized every time before calling the
select().
8. JAGab77075
After a user does a shutdown(0) on a socket, all further
attempts to send data on the socket should result in
X25/ACC sending a clear. Instead of a "CLEAR" packet, a
"RESET" was being sent.
Resolution:
Programmatic access to X25 was modified to send a "CLEAR"
packet based on "SO_CANTRCVMORE" flag, whenever a peer
tried to connect to a socket that had been operated upon
by a shutdown(0) by the user. The file descriptor of the
socket is closed only when the user does a "close".
9. JAGad38177 / SR 8606168899
Some of the fields in the "labels" array elements were
not initialized when "sx25d" allocates (using a free
entry from the static array) a label for an opened
stream. So, when x25init sends a message to sx25d to
push the "trc" module on top of already opened lapb,
since one of the fields in the label associated with the
lapb stream was NOT initialized, the sx25d was taking a
different code path than the path it was supposed to
take. In that path, instead of pushing the "trc" module
on top of existing lapb stream, it opens the lapb stream
again and attaches the same label to that stream (thus
previous association with the lapb stream is removed).
At this point, x25init does not know of this. After
this X25_SET_SNID ioctl sent by x25init failed as the
ioctl was passed on to the lapb stream instead of "trc"
module pushed on top of lapb (trc module was not pushed
on top of newly opened stream).
Resolution:
When the label is freed (marking the corresponding
entry as free), now, all the fields associated with that
label are initialized correctly.
10. JAGaa03408
Normally, when switching ON tracing for a port in a
subsystem, nettl first switches off all tracing for that
subsystem if tracing for that particular subsystem was
active earlier. If an x25init happens on a port on
which PLP trace has been enabled, some data structures
(in particular, the trc_pseudo_plp_state_list in
trcmodule.c file) are reset. "nettl" does not come to
know of this. Now if "nettl -traceon..." is executed
on that port, nettl first tries to switch OFF the
tracing on the port (because according to it the tracing
on the specified subsystem SX25L3 is enabled)- and is
not able to find the PLP-trace information data
structure (struct trc_strm_state) corresponding to the
given port and therefore reports Error 19.
Resolution:
The nettl tracing for a subsystem, if enabled, is now
explicitly turned OFF in x25stop. This way nettl is in
"sync" with events on x25 ports.
11. JAGad47478 / SR 8606178251
During the reset of the card, if the driver fails to
allocate memory, all the memory allocated so far would
be freed and also the card registers and card memory
would be unmapped. So in the next iteration, when user
tries to reset the card, the reset code tries to access
the NULL pointer and this results in system panic.
Resolution:
The fix is to map the card registers and memory if
they are not already mapped during the card reset.
12. JAGad41662 / SR 8606172402
When X25_SETUP_PVC ioctl is received, an mblk message is
allocated which never gets freed. This results in a
memory leak.
Resolution:
The memory is freed after its use.
13. JAGad40862 / SR 8606171598
"x25stat" command was not providing any option to the
user which can be used to request the "VC Up Time" of
the active virtual circuits.
Resolution:
Provided "-u" option in x25stat command so that the user
can request the "VC Up Time" for all active virtual
circuits. A new ioctl has been added for this purpose.
This option, however, has to be used in conjunction with
the "-v" option of x25stat command. Also, this option
is supported only for ACC cards.
14. JAGad47111 / SR 8606177884
Due to a race condition between handling of the closing
of the stream and data coming from the upper layers, the
streams subsystem went into infinite loop,processing the
upper layer data.
Resolution:
The fix is to disable the processing of the upper layer
messages when the stream is being closed.
15. JAGad47117 / SR 8606177890
When the card is reset, the heartbeat is NOT stopped.
So, after the card is reset, if the firmware is not
downloaded immediately, the driver's heartbeat routine
will wrongly detect this as card failure and displays a
"heartbeat" failure message.
Resolution:
The fix is to disable the heartbeat timer when the card
is reset.This will be enabled once the firmware download
is completed.
16. JAGad47673 / SR 8606178446
The data corruption is due to the bad implementation of
bcopy() on i960 processor (on the J3526A card). It does
not copy properly if the source or the destination
addresses are not aligned to a word boundary.
Resolution:
Implemented "bcopy_j3526()" to correctly copy the data
and remapped "bcopy()" to "bcopy_j3526()" (for LAPB)
in the firmware for J3526A card.
17. JAGad02522 / SR 8606133377
The default NSDU size is 2048 bytes.If the packet size
is more than that,the ACC driver nli2zcom/nlife fragments
the packet but "x25check" and "x25server" always expect
a single packet with out fragmentation.
Resolution:
The fix is to send "N_HP_SET_FRAG" streams control
message on both the client side data transfer stream
(by x25check) and the server side data transfer stream
(by x25server) to set the maximum fragment size equal
to the packet size.
Enhancement:
No (superseded patches contained enhancements)
PHNE_25596:
x25stat will show "VC Up Time" for all active VCs.
SR:
8606133376 8606231715 8606228517 8606196727 8606266719
8606268596 8606182798 8606183710 8606183954 8606185082
8606200067 8606201005 8606203532 8606212990 8606218073
8606218061 8606167689 8606164900 8606145490 8606167193
8606168699 8606170403 8606171296 8606168899 8606178251
8606172402 8606171598 8606177884 8606177890 8606178446
8606133377 8606167874 8606168414
Patch Files:
SX25-HPerf.SX25-HPERF-SAM,fr=B.11.11.00,
fa=HP-UX_B.11.11_32/64,v=HP:
/usr/sam/lib/x25/x25.tm
SYNC-WAN.SYNC-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_64,v=HP:
/etc/x25/ric_wvol.rel
/etc/x25/wnio.dwn
/usr/conf/lib/libwan.a
/etc/x25/ric_cxb.rel
/usr/conf/lib/wansyms.o
SYNC-WAN.SYNC-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_32,v=HP:
/etc/x25/ric_wvol.rel
/etc/x25/wnio.dwn
/usr/conf/lib/libwan.a
/etc/x25/ric_cxb.rel
/usr/conf/lib/wansyms.o
SX25-HPerf.SX25-HPERF-PAD,fr=B.11.11.00,
fa=HP-UX_B.11.11_32/64,v=HP:
/usr/sbin/x29server
SX25-HPerf.SX25-HPERF-COM,fr=B.11.11.00,
fa=HP-UX_B.11.11_32/64,v=HP:
/usr/sbin/x25init
/usr/sbin/sx25d
/usr/sbin/x25stop
/usr/lib/nls/C/x25stop.cat
/usr/sbin/x25stat
/usr/sbin/sx25stat
/usr/sbin/sx25statx
/etc/x25/ric_lapb.rel
/usr/sbin/x25check
/usr/sbin/x25server
/usr/lib/nls/C/x25check.cat
/usr/sbin/x25mibstat
/usr/sbin/x25ifstate
/var/x25/dlpi/dlpi_lib.c
/usr/lib/libx25mstat.a
SX25-HPerf.PA-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libx25pa.a
SX25-HPerf.PA-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libx25pa.a
SX25-HPerf.COM-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_64,v=HP:
/etc/x25/lnio.dwn
/usr/conf/lib/libx25.a
/usr/conf/lib/x25syms.o
SX25-HPerf.COM-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_32,v=HP:
/etc/x25/lnio.dwn
/usr/conf/lib/libx25.a
/usr/conf/lib/x25syms.o
SYNC-WAN.SYNC-COM,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/include/x25/x25hd_ioctl.h
SX25-HPerf.SX25-HPERF-MAN,fr=B.11.11.00,
fa=HP-UX_B.11.11_32/64,v=HP:
/usr/share/man/man1m.Z/x25check.1m
/usr/share/man/man1m.Z/x25init.1m
/usr/share/man/man1m.Z/x25stop.1m
/usr/share/man/man1m.Z/x25stat.1m
SX25-HPerf.SX25-HPERF-IP,fr=B.11.11.00,
fa=HP-UX_B.11.11_32/64,v=HP:
/usr/sbin/x25ping
SX25-HPerf.COM-64SLIB,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,
v=HP:
/usr/lib/pa20_64/libx25mstat.a
SX25-HPerf.SX25-SNMP,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,
v=HP:
/usr/sbin/x25subagt
what(1) Output:
SX25-HPerf.SX25-HPERF-SAM,fr=B.11.11.00,
fa=HP-UX_B.11.11_32/64,v=HP:
/usr/sam/lib/x25/x25.tm:
None
SYNC-WAN.SYNC-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_64,v=HP:
/etc/x25/ric_wvol.rel:
ARTIC960 (C) Serial WAN for 4 Port Synchronous PMC
Version 4.1.6 (using Spec Version 1.1)
/etc/x25/wnio.dwn:
hdlc.h 3.28 (Spider) 90/12/10
hdlc.h 3.28 (Spider) 90/12/10
hdlc.h 3.28 (Spider) 90/12/10
hdlc.h 3.28 (Spider) 90/12/10
NIO PSI firmware (11i) $Revision: 9.15 $ 23_Jul_02_1
6:59
/usr/conf/lib/libwan.a:
WAN Common Part Rev.A.01
FILESET WAN-COM (11i) $Revision: 6.15 $ 23_Jul_02_16
:59
J3526: Revision: A.1.4 $Date: 99/05/20 08:25:00
J3525 driver for HPUX 11.11 (64 bit) $Revision: 1.1
$
/etc/x25/ric_cxb.rel:
ONBOARD CXB: Revision: A.1.3 $Date: 2001/10/29 15:5
0:44 $
/usr/conf/lib/wansyms.o:
None
SYNC-WAN.SYNC-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_32,v=HP:
/etc/x25/ric_wvol.rel:
ARTIC960 (C) Serial WAN for 4 Port Synchronous PMC
Version 4.1.6 (using Spec Version 1.1)
/etc/x25/wnio.dwn:
hdlc.h 3.28 (Spider) 90/12/10
hdlc.h 3.28 (Spider) 90/12/10
hdlc.h 3.28 (Spider) 90/12/10
hdlc.h 3.28 (Spider) 90/12/10
NIO PSI firmware (11i) $Revision: 9.15 $ 23_Jul_02_1
6:35
/usr/conf/lib/libwan.a:
WAN Common Part Rev.A.01
FILESET WAN-COM (11i) $Revision: 6.15 $ 23_Jul_02_16
:35
J3526: Revision: A.1.4 $Date: 99/05/20 08:25:00
J3525 driver for HPUX 11.11 (32 bit) $Revision: 1.1
$
/etc/x25/ric_cxb.rel:
ONBOARD CXB: Revision: A.1.3 $Date: 2001/10/29 15:5
0:44 $
/usr/conf/lib/wansyms.o:
None
SX25-HPerf.SX25-HPERF-PAD,fr=B.11.11.00,
fa=HP-UX_B.11.11_32/64,v=HP:
/usr/sbin/x29server:
X.25 PAD Services $Revision: 11.1 $ 23_Jul_02_16:56
SX25-HPerf.SX25-HPERF-COM,fr=B.11.11.00,
fa=HP-UX_B.11.11_32/64,v=HP:
/usr/sbin/x25init:
Streams X.25 (11i) $Revision: 9.15 $ 23_Jul_02_16:53
/usr/sbin/sx25d:
None
/usr/sbin/x25stop:
Streams X.25 (11i) $Revision: 9.15 $ 23_Jul_02_16:53
/usr/lib/nls/C/x25stop.cat:
None
/usr/sbin/x25stat:
Streams X.25 (11i) $Revision: 9.15 $ 23_Jul_02_16:53
/usr/sbin/sx25stat:
None
/usr/sbin/sx25statx:
None
/etc/x25/ric_lapb.rel:
None
/usr/sbin/x25check:
Streams X.25 (11i) $Revision: 9.15 $ 23_Jul_02_16:53
/usr/sbin/x25server:
Streams X.25 (11i) $Revision: 9.15 $ 23_Jul_02_16:53
/usr/lib/nls/C/x25check.cat:
None
/usr/sbin/x25mibstat:
None
/usr/sbin/x25ifstate:
Streams X.25 (11i) $Revision: 9.15 $ 23_Jul_02_16:53
/var/x25/dlpi/dlpi_lib.c:
None
/usr/lib/libx25mstat.a:
None
SX25-HPerf.PA-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libx25pa.a:
FILESET SX25-PA (11i) $Revision: 9.15 $ 23_Jul_02_17
:08
SX25-HPerf.PA-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libx25pa.a:
FILESET SX25-PA (11i) $Revision: 9.15 $ 23_Jul_02_16
:51
SX25-HPerf.COM-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_64,v=HP:
/etc/x25/lnio.dwn:
hdlc.h 3.28 (Spider) 90/12/10
hdlc.h 3.28 (Spider) 90/12/10
hdlc.h 3.28 (Spider) 90/12/10
hdlc.h 3.28 (Spider) 90/12/10
NIO PSI firmware (11i) $Revision: 9.15 $ 23_Jul_02_1
6:59
/usr/conf/lib/libx25.a:
X25 Protocol Rev.B.02
FILESET SX25-COM (11i) $Revision: 9.15 $ 23_Jul_02_1
7:08
/usr/conf/lib/x25syms.o:
None
SX25-HPerf.COM-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_32,v=HP:
/etc/x25/lnio.dwn:
hdlc.h 3.28 (Spider) 90/12/10
hdlc.h 3.28 (Spider) 90/12/10
hdlc.h 3.28 (Spider) 90/12/10
hdlc.h 3.28 (Spider) 90/12/10
NIO PSI firmware (11i) $Revision: 9.15 $ 23_Jul_02_1
6:35
/usr/conf/lib/libx25.a:
X25 Protocol Rev.B.02
FILESET SX25-COM (11i) $Revision: 9.15 $ 23_Jul_02_1
6:51
/usr/conf/lib/x25syms.o:
None
SYNC-WAN.SYNC-COM,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/include/x25/x25hd_ioctl.h:
None
SX25-HPerf.SX25-HPERF-MAN,fr=B.11.11.00,
fa=HP-UX_B.11.11_32/64,v=HP:
/usr/share/man/man1m.Z/x25check.1m:
None
/usr/share/man/man1m.Z/x25init.1m:
None
/usr/share/man/man1m.Z/x25stop.1m:
None
/usr/share/man/man1m.Z/x25stat.1m:
None
SX25-HPerf.SX25-HPERF-IP,fr=B.11.11.00,
fa=HP-UX_B.11.11_32/64,v=HP:
/usr/sbin/x25ping:
Streams X.25 (11i) $Revision: 9.15 $ 23_Jul_02_16:53
SX25-HPerf.COM-64SLIB,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,
v=HP:
/usr/lib/pa20_64/libx25mstat.a:
None
SX25-HPerf.SX25-SNMP,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,
v=HP:
/usr/sbin/x25subagt:
HP92453-02A.11.00 HP-UX SYMBOLIC DEBUGGER (END.O ILP
32) $Revision: 75.02 $
IF SNMP Subagent rev. B.11.11.00 (04-Sep-01_10:16, 1
.01)
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
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
cksum(1) Output:
SX25-HPerf.SX25-HPERF-SAM,fr=B.11.11.00,
fa=HP-UX_B.11.11_32/64,v=HP:
2599324741 39395 /usr/sam/lib/x25/x25.tm
SYNC-WAN.SYNC-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_64,v=HP:
732049392 103501 /etc/x25/ric_wvol.rel
2356036432 40167 /etc/x25/wnio.dwn
2150103707 659174 /usr/conf/lib/libwan.a
3194651934 89390 /etc/x25/ric_cxb.rel
2986535142 537808 /usr/conf/lib/wansyms.o
SYNC-WAN.SYNC-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_32,v=HP:
732049392 103501 /etc/x25/ric_wvol.rel
2560077782 40167 /etc/x25/wnio.dwn
854636892 419024 /usr/conf/lib/libwan.a
3692015940 89390 /etc/x25/ric_cxb.rel
3968980711 426890 /usr/conf/lib/wansyms.o
SX25-HPerf.SX25-HPERF-PAD,fr=B.11.11.00,
fa=HP-UX_B.11.11_32/64,v=HP:
349135851 176128 /usr/sbin/x29server
SX25-HPerf.SX25-HPERF-COM,fr=B.11.11.00,
fa=HP-UX_B.11.11_32/64,v=HP:
2633255711 147456 /usr/sbin/x25init
82478467 36864 /usr/sbin/sx25d
2384986265 81920 /usr/sbin/x25stop
2686095942 3574 /usr/lib/nls/C/x25stop.cat
924749359 49152 /usr/sbin/x25stat
3674442569 81920 /usr/sbin/sx25stat
1965991310 86016 /usr/sbin/sx25statx
4206514186 106837 /etc/x25/ric_lapb.rel
943530214 45056 /usr/sbin/x25check
3991988662 45056 /usr/sbin/x25server
3072025543 10676 /usr/lib/nls/C/x25check.cat
1208154707 73728 /usr/sbin/x25mibstat
1797043938 32768 /usr/sbin/x25ifstate
2567200805 23391 /var/x25/dlpi/dlpi_lib.c
4056284066 28048 /usr/lib/libx25mstat.a
SX25-HPerf.PA-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_64,v=HP:
8497044 364916 /usr/conf/lib/libx25pa.a
SX25-HPerf.PA-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_32,v=HP:
3127714867 235134 /usr/conf/lib/libx25pa.a
SX25-HPerf.COM-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_64,v=HP:
4175638737 77339 /etc/x25/lnio.dwn
525840756 665056 /usr/conf/lib/libx25.a
3328078103 858720 /usr/conf/lib/x25syms.o
SX25-HPerf.COM-ALIB,fr=B.11.11.00,fa=HP-UX_B.11.11_32,v=HP:
1584445076 77339 /etc/x25/lnio.dwn
3209967530 439486 /usr/conf/lib/libx25.a
3254400235 676712 /usr/conf/lib/x25syms.o
SYNC-WAN.SYNC-COM,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,v=HP:
1743344219 8405 /usr/include/x25/x25hd_ioctl.h
SX25-HPerf.SX25-HPERF-MAN,fr=B.11.11.00,
fa=HP-UX_B.11.11_32/64,v=HP:
923224422 2893 /usr/share/man/man1m.Z/x25check.1m
2220635723 3568 /usr/share/man/man1m.Z/x25init.1m
2601890349 2148 /usr/share/man/man1m.Z/x25stop.1m
3398132756 2989 /usr/share/man/man1m.Z/x25stat.1m
SX25-HPerf.SX25-HPERF-IP,fr=B.11.11.00,
fa=HP-UX_B.11.11_32/64,v=HP:
2716057730 36864 /usr/sbin/x25ping
SX25-HPerf.COM-64SLIB,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,
v=HP:
1667950190 61640 /usr/lib/pa20_64/libx25mstat.a
SX25-HPerf.SX25-SNMP,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,
v=HP:
4179128158 350656 /usr/sbin/x25subagt
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHNE_23190 PHNE_25596
Equivalent Patches: None
Patch Package Size: 7410 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHNE_27403
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_27403.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_27403. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHNE_27403.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHNE_27403.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_27403.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHNE_27403------------------------------------------
Document ID: PHNE_25181
Date Loaded: 20020808
Title: s700_800 11.00 R6.11.00 SNAplus2 Link/Common, TN3270 patch
Patch Name: PHNE_25181
Patch Description: s700_800 11.00 R6.11.00 SNAplus2 Link/Common, TN3270 patch
Creation Date: 01/12/18
Post Date: 02/08/08
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products:
SNAplus2-Link R6.11.00
SNAplus2-Common R6.11.00
3270-Common R6.11.00
Filesets:
SNAplus2-Link.SNAP2-LINK,fr=R6.11.00.200,fa=HP-UX_B.11.00_32/64,v=HP
SNAplus2-Link.SNAP2-LINK,fr=R6.11.00.010,fa=HP-UX_B.11.00_32/64,v=HP
SNAplus2-Link.LINK-64ALIB,fr=R6.11.00.200,fa=HP-UX_B.11.00_64,v=HP
SNAplus2-Link.LINK-64ALIB,fr=R6.11.00.010,fa=HP-UX_B.11.00_64,v=HP
SNAplus2-Link.LINK-32ALIB,fr=R6.11.00.200,fa=HP-UX_B.11.00_32,v=HP
SNAplus2-Link.LINK-32ALIB,fr=R6.11.00.010,fa=HP-UX_B.11.00_32,v=HP
SNAplus2-Common.SNAP2-SAM,fr=R6.11.00.200,fa=HP-UX_B.11.00_32/64,v=HP
SNAplus2-Common.SNAP2-SAM,fr=R6.11.00.010,fa=HP-UX_B.11.00_32/64,v=HP
SNAplus2-Common.SNAP2-NOTES,fr=R6.11.00.200,fa=HP-UX_B.11.00_32/64,v=HP
SNAplus2-Common.SNAP2-NOTES,fr=R6.11.00.010,fa=HP-UX_B.11.00_32/64,v=HP
SNAplus2-Common.SNAP2-CORE,fr=R6.11.00.200,fa=HP-UX_B.11.00_32/64,v=HP
SNAplus2-Common.SNAP2-CORE,fr=R6.11.00.010,fa=HP-UX_B.11.00_32/64,v=HP
SNAplus2-Common.SNAP2-ASCIIADM,fr=R6.11.00.200,fa=HP-UX_B.11.00_32/64,v=HP
SNAplus2-Common.SNAP2-ASCIIADM,fr=R6.11.00.010,fa=HP-UX_B.11.00_32/64,v=HP
SNAplus2-Common.SNAP2-ADMIN,fr=R6.11.00.200,fa=HP-UX_B.11.00_32/64,v=HP
SNAplus2-Common.SNAP2-ADMIN,fr=R6.11.00.010,fa=HP-UX_B.11.00_32/64,v=HP
SNAplus2-Common.CORE-64SLIB,fr=R6.11.00.200,fa=HP-UX_B.11.00_64,v=HP
SNAplus2-Common.CORE-64SLIB,fr=R6.11.00.010,fa=HP-UX_B.11.00_64,v=HP
SNAplus2-Common.CORE-32SLIB,fr=R6.11.00.200,fa=HP-UX_B.11.00_32,v=HP
SNAplus2-Common.CORE-32SLIB,fr=R6.11.00.010,fa=HP-UX_B.11.00_32,v=HP
3270-Common.MANAGERS,fr=R6.11.00.200,fa=HP-UX_B.11.00_32/64,v=HP
3270-Common.MANAGERS,fr=R6.11.00.010,fa=HP-UX_B.11.00_32/64,v=HP
3270-Common.MANAGER-64SLIB,fr=R6.11.00.200,fa=HP-UX_B.11.00_64,v=HP
3270-Common.MANAGER-64SLIB,fr=R6.11.00.010,fa=HP-UX_B.11.00_64,v=HP
3270-Common.MANAGER-32SLIB,fr=R6.11.00.200,fa=HP-UX_B.11.00_32,v=HP
3270-Common.MANAGER-32SLIB,fr=R6.11.00.010,fa=HP-UX_B.11.00_32,v=HP
3270-Common.3270API,fr=R6.11.00.200,fa=HP-UX_B.11.00_32/64,v=HP
3270-Common.3270API,fr=R6.11.00.010,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHNE_25181: PANIC HANG
PHNE_24341: PANIC HANG
PHNE_24093: PANIC
PHNE_22721: PANIC
PHNE_22492: PANIC
PHNE_21336: PANIC
PHNE_21001: HANG ABORT
PHNE_19527: PANIC HANG CORRUPTION
PHNE_18000: HANG ABORT
PHNE_17229: PANIC HANG CORRUPTION
Category Tags:
defect_repair enhancement general_release critical panic
halts_system corruption
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_25181
Symptoms:
PHNE_25181:
(1) JAGad77708/8606208520
System panic due to data page fault.
Data Page Faults: libsixs.a nms_nah_process_mu_rsp+0x100
Crash in nms_nah_process_mu_rsp
Stack is:-
trap 0xa48
thandler 0xb7c
nms_nah_process_mu_rsp 0x100
nms_msm_queue_handler 0x694
nba_dispatch_process 0xd0
nba_scheduler 0x208
vpr_stream_lr_svc 0x160
sq_wrapper 0xb8
str_sched_up_daemon 0x2b0
str_sched_daemon 0xf4
main 0x94c
$vstart 0x34
(2) JAGad87318/8606218168
System panic in nrm_bld_and_send_deact_sess.
Stack trace:-
nrm_bld_and_send_deact_sess
nrm_send_deactivate_session
nrm_ps_to_rm_rec
nrm_queue_handler
nba_dispatch_input
nba_dispatch_process
nba_scheduler
vpr_stream_uw_drive_scheduler
vpr_stream_uw_svc
sq_wrapper
(3) JAGad91086/8606221968
Query_mode fails after doing initialize_session_limitstrace.
(4) JAGad96946/8606227887
SNA hang up on large system (32 CPUs), stack shows deadlock
in APPN code with re-entrancy due to Streams running service
procedure in interrupt context (on the ICS stack).
PHNE_24341:
(1) JAGad47872/8606178646
Delays in startup script due to ioscan.
(2) JAGad46888/8606177656
SAM install of SNAplus2 can be very slow and appear to be
hung on large systems.
(3) JAGad71274/8606202100
SNAplus2 hangs up under stress (one CPU locked)and attempts
to stop SNAplus2 fail. A system reboot is required to
recover. Stack trace shows sna_ndg_v0_get_rw_lock .
(4) JAGad69070/8606199884
There are software verification errors on an OS-Core fileset
when SNA is also installed.
(5) JAGad76402/8606207227
Panic in SNAPlus2 Router, nba_mm_free, while snapstop is in
progress.
Stack trace :-
trap 0xd9c
thandler 0xd24
nba_mm_free 0x68
vpr_create_entity 0x1f8
0x0afvpr_stream_open 0x3a8
open_wrapper 0x98
csq_protect 0x120
osr_open 0xb44
pse_open 0xf8
hpstreams_open 0x50
hpstreams_clone_open 0x214
call_open_close 0x144
opend 0x128
spec_open 0x78
vns_copen 0x4c
vn_open 0xa8
copen 0xd0
open 0x3c
syscall 0x6f8
syscallinit 0x54c
(6) JAGad71590/8606202416
T1 timer settings in xsnapadmin do not work. The t1_timeout
parameter in define_tr_ls (or Ethernet or FDDI) is ignored
by SNAplus2. It is exposed in xsnapadmin in the advanced
dialog for the LS. The T1 timer is fixed at 1 second.
PHNE_24093:
(1) JAGad65199/8606195995
Panic in wait_for_lock called from nps_free_rcb_mus.
Crash occurs just after ASSERT in nbmmgr.c line 589.
Stack is:-
wait_for_lock+0x2cc
sl_retry+0x1c
v0_get_rw_lock+0x38
vpr_stream_close+0x38
close_wrapper+0x6c
csq_protect+0x120
osr_pop_subr+0x1fc
osr_close_subr+0x324
hpstreams_close_int+0xd40
hpstreams_close+0x2c
call_open_close+0x1f8
closed+0xb0
spec_close+0x54
vn_close+0x48
vno_close+0x20
closef+0x68
exit+0x1108
rexit+0x28
syscall+0x200
$syscallrtn+0x0
WARNING: SNA ASSERT:
09:30:06 30 APR 2001
File: ../../c/cappn/nbmmgr.c
Line: 589
Condition: FALSE
PHNE_22721:
(1) JAGad35609/8606166322
RUI does not support segmented delivery from the lower
layers. Incorrect data is returned on RUI read call when
RU is segmented. Note that similarly, incorrect data could
be passed through on a PU concentrated connection.
(2) JAGad34156/8606164859
Autodial does not work with SNAPlus2 using EISA PSI card.
(3) JAGad41008/8606171744
Incorrect usage of incoming Attach is not being rejected.
(4) JAGad42004/8606172744
snapadmin command query_available_tp sometimes reports that
a TP is still available even after each of its multiple
copies have ended.
(5) JAGad43064/8606173811
Panic in qenable when stopping sna (snap stop).
qenable is called from vpr_timer_tick.
panic+0x14
report_trap_or_int_and_panic+0x80
interrupt+0x1d4
$ihndlr_rtn+0x0
qenable+0xc
vpr_timer_tick+0x30
str_timeout+0xc4
invoke_callouts_for_self+0xc0
sw_service+0xb0
mp_ext_interrupt+0x144
ivti_patch_to_nop3+0x0
sth_get_sth+0xc8
hpstreams_write+0x18
spec_rdwr+0x18c
vno_rw+0x1d4
write+0x104
(6) JAGad34698/8606165404
snapfilter does not work on 64-bit machines
(7) JAGad40346/8606171082
A MultiThreaded HLLAPI application on 11.0 will hang
up on the first verb call as the signal from the 3270
emulator does not work correctly. This problem applies
to both TN3270 and SNAP3270 emulators
(8) JAGad42503/8606173243
There is a changed behaviour of HA_WAIT verb call. The WAIT
verb can return early eg. when PS or OIA is updated.
(9) JAGad49181/8606179959
HLLAPI Query Host Update verb returns code of 65535 .
After applying fix for JAGad42479 (signals broken with
Multi Threaded HLLAPI library) the PAUSE verb works
incorrectly. Subsequent verbs timed out after 30 seconds
with a return code of -1.
(10) JAGad54056/8606184850
HLLAPI application used with TN3270 is intermittently
receiving an RC=9 when issuing Connect_PS verb. If a
HLLAPI application is started at the same time as
3270 (typically with a shell script) then the first
HLLAPI verb (typically connect) can fail with a return
code of 9. If so all subsequent HLLAPI verbs are rejected
with a return code of 1.
PHNE_22492:
(1) JAGad21193/8606151854
System panic from nrm_process_cnos_reply.
Panic with following stack:
panic+54:
report_trap_or_int_and_panic+80:
trap+0xDB8:
$RDB_trap_patch+40:
nrm_process_cnos_reply+270:
nrm_ps_to_rm_rec+780:
nrm_queue_handler+94:
nba_dispatch_input+2D0:
nba_dispatch_process+0xB4:
nba_scheduler+21C:
vpr_stream_lr_svc+154:
sq_wrapper+94:
str_sched_up_daemon+1C4:
str_sched_daemon+390:
main+7A0:
$vstart+48:
$locore+94:
Also an assert logged at same time as panic:
WARNING: SNA ASSERT:
07:25:11 20 JUL 2000
File: ../../p/sappn/nrmcnos.c
Line: 292
Condition: wait_req != NULL
(2) JAGad13997/8606144657
Panic in SNAPlus2 requiring further analysis
Crash with stack as follows
panic+0x10
report_trap_or_int_and_panic+0xe8
trap+0xa48
thandler+0xb7c
ncs_destroy_an_cb_if_required+0x1cc
ncs_reset_xid_info+0xa0
ncs_xid_processing+0x600
ncs_reset_ls+0x738
ncs_fsm_ls_int+0x1ed4
ncs_fsm_ls_ext+0x138c
ncs_pc_to_cs_signals+0x88
ncs_queue_handler+0xd0
nba_dispatch_input+0x298
nba_dispatch_process+0xa4
nba_scheduler+0x1b0
vpr_stream_lr_svc+0x134
sq_wrapper+0xb8
str_sched_up_daemon+0x1f8
str_sched_daemon+0xf4
main+0x958
$vstart+0x34
$locore+0x74
Also following asserts logged:-
WARNING: SNA ASSERT:
22:46:03 23 JUN 2000
File: ../../p/vappn/ncsfsmln.c
Line: 104
Condition: !an_cb->num_active_conns
WARNING: SNA ASSERT:
15:20:08 24 JUN 2000
File: ../../p/sappn/ncsxidtg.c
Line: 1272
Condition: tg_number == 0
(3) JAGab57822/8606101599
Customer has migrated a configuration to R6. However they
have taken the default TN Server port number during the
migration.
When they start the node they get a BIND failure message.
(4) JAGad03916/8606134781
Error in SAM when attempting to install PCI card in
SNAPlus2 :-Internal
Error: Cannot find tunable parameter 'num_boards_3525' in
the
internal kernel configuration data structure.
(5) JAGad12558/8606143222
NOF applications which reference AP_GLOBAL_TIMEOUT fail to
compile:
e.g.
cc: 'nofsample1.c', line 238: error 1000: Unexpected
symbol: '0x01'.
cc: 'nofsample1.c', line 238: error 1588: 'NB_BYTE'
undefined.
(6) JAGad25288/8606155977
snapadmin status_node command incorrectly causes error in
logfile.
With SNAplus2 R6 ,when issuing the snapadmin status_node
command it causes an error to be logged in the sna.err
file as follows:-
------ 10:22:24 BST 15 Aug 2000 -------------------
NOF Message 1 - 8, Subcode: 1 - 10
Log category: EXCEPTION Cause Type:
External
System:
hppimd54
Lost connection to NOF application. Application handle =
0x010000DE
Cause: The Node has lost its connection to a NOF
application
or an administration tool. This can occur if a NOF
application
ends without terminating its NOF connection.
Action: Check that the NOF application issues
DISCONNECT_NODE or CLOSE_FILE before terminating.
PHNE_21336:
(1) JAGad01270/8606132121
Customer is using the T(nn) option on snapsend and
snapreceive. However, the file transfer program is
returning with an error code saying the file transfer
was canceled.
File transfer works OK without the T(nn) option.
(2) JAGac95609/8606130719
System panic after call to npo_sess_limit_data_lock_mgr().
(3) JAGac86152/8606128605
LU Type 2 is inactive on the HP side but active on the IBM
side. No DACTLU or segmentation error is seen in the DLC
trace, but sna.err file shows the following:
APPN Message 512 - 171, Subcode: 0 - 10
Session segmentation error.
....
RU : (3 bytes)
(4) JAGac78841/8606128040
System panics after receiving an UNBIND during initialise
session limits processing. The stack shows that
nba_mm_free was called from nlu_remove_mode. A similar
problem was also reported in JAGac95609.
(5) JAGab74691/8606105945
3270 user gets PROG checks 432 (bracket race) when typing
ahead together with ASSERT in vbaccess line 324 and log 52
(internal error copying buffer). User needs to do reset on
3270 to recover.
(6) JAGab71415/8606104367
Data page fault panic when attempting to start sdlc
link station on EISA 8 port ACC card on 11.00.
Stack tracestack trace for event 0
crash event was a panic
panic+0x14
report_trap_or_int_and_panic+0x4c
trap+0x7a4
$call_trap+0x38
svphpoll+0x44
vhs_timer_proc+0x58
sna_sdlc_nba_dispatch_input+0x8c
sna_sdlc_nba_dispatch_process+0xa4
sna_sdlc_nba_scheduler+0x11c
sna_sdlc_vsi_stream_uw_service+0x3e0
sq_wrapper+0x90str_sched_mp_daemon+0x150
str_sched_daemon+0x3a8main+0x544
$vstart+0x34
$locore+0x90
PHNE_21001:
(1) JAGac78479/8606127677
Cannot reliably stop SDLC link station or port.
Once the port gets stuck in the stopping state
the sna has to be recycled.
(2) JAGab78721/8606108322
snap2adm coredumps when more than 250 dependent LU62s are
defined.
PHNE_20734:
(1) JAGab84956/8606112613
A customer application linked with libmgrdce.1 library
stopped working with no errors reported.
(2) JAGab83814/8606111714
The snapmsgf program fails to run with error message
'unable to open the catalog file ./vsnamsg.cat'.
(3) JAGab75474/8606106417
With release R6.11.00.200 of SNAPlus2 various user
application errors can be reported if the user is not root
or a member of the sna group. Example errors are:
snap3720 error msg 'Unable to open the configuration file'
CPIC application fails in CMINIT with RC=20
CPIC_PRODUCT_SPECIFIC_ERROR.
(4) JAGab65304/1653307843
When using snaptrcfmt -D to decode a DLC trace that
includes a BIND, the hex information of the BIND is
modified slightly. The SLU Name length is decremented by
1. There are also many minor problems with the details of
the BIND.
PHNE_19527:
(1) JAGab83920/8606111815
Customer's QLLC link fails to come up due to error in the
XID exchange. The sna.err log shows XID 3 error during
negotiation.
(2) JAGab83645/8606110894
Application cannot reconnect to HLLAPI session after
killing 3270 program. The hllapi verb connect_ps() fails
with HARC_SYSTEM_ERROR, and extended error code1 = 2000 and
extended error code2 = 0000.
(3) JAGab79003/8606108556
K580 system panics on reboot with the following error
messages:
System Panic:
9245XB HP-UX (B.10.20) #1: Sun Jun 9 06:31:19 PDT 1996
panic: (display==0xb800, flags==0x0) nio_initialize :
l_io_vec.iov_base == NULL
PC-Offset Stack Trace (read across, most recent is 1st):
0x00276f44 0x003fdab0 0x00404968 0x001297c4 0x00240ae8
0x002a7ea8 0x002a6ae4 0x00215088 0x002147e0 0x00295368
0x00295444 0x00295444 0x00295444 0x002951c0 0x00295d20
0x002f316c 0x000c7014 0x00183960
End Of Stack
It was not possible for the kernel to find a process
that caused this crash.
jCj1D
Dumpsys() called
(4) JAGab76276/8606106834
When the 'SNAplus2 Installation' icon is double clicked in
11.00 SAM, the main menu screen takes too long (30-45
seconds on a T500 machine) to come up.
(5) JAGab75469/8606106415
When starting an SDLC link the system panics with
following stack trace:
stack trace for event 0
crash event was a panic
FUNC
panic+0x10
report_trap_or_int_and_panic+0xe8
trap+0xa48
$RDB_trap_patch+0x20
sna_sdlc_vba_ips_putb+0x18
sdl_send_set_mode_frame+0x138
sdl_psecs+0xf88
sdl_prtmg+0x106c
sdl_wrxfr+0x5a8
sdl_receive_proc+0x80
sna_sdlc_nba_dispatch_input+0x254
sna_sdlc_nba_dispatch_process+0xa4
sna_sdlc_nba_scheduler+0x11c
vsi_stream_uw_service+0x3e0
sq_wrapper+0xb8
str_sched_mp_daemon+0x114
str_sched_daemon+0x1f4
main+0x97c
$vstart+0x34
(6) JAGab75335/8606106333
SAM SDLC/PSI configuration info. inconsistent when
user cancels SDLC changes. Exact sequence leading
up to this condition is shown below:
The following SNAplus2 configuration was done on a
K-class machine with two PSI cards configured for SDLC:
A. User selects 'remove component' to de-configure all
psi cards.
B. The SDLC configuration screen pops up. Now clicks on
the 'View Entire Card' button.
C. The 'View Entire Card' screen pops up. On the SDLC
configuration screen, the user selects all the cards
displayed and clicks on 'Remove'.
D. Now the user presses OK on the 'View Entire Card'
screen. It disappears.
E. Then the user clicks on 'Cancel' in the SDLC
configuration screen to abort any changes. The main menu
screen now displays the SDLC PSI as 'Not Added'. This is
incorrect since the user aborted SDLC configuration.
As a workaround, the user can get the actual configuration
state of the SDLC /PSI by doing a 'Options->Refresh List'.
(7) JAGab75114/8606106196
When adding SDLC(PSI) on T500 system using SAM, SAM builds
vmunix_test but then exits with a core dump and the error
message:
UNEXPECTED EXIT: process LANG=C LC_ALL=C
/usr/sam/lbin/samx -C -p 18985 /opt/sna/sam/C/mainMenu.ui
exited with a non-zero exit status. sam: Warning:
selector, SLIST_LABEL, is wider than the max window width.
sam: Warning: selector, SLIST, is wider than the max
window width.
sh: 20111 Memory fault(coredump)
(8) JAGab74185/8606105839
An LUA application receives an UNBIND indication from an
established LU-LU session. It responds with RSP.UNBIND and
encounters the following error:
primary return code: LUA_STATE_CHECK (0x0200)
secondary return code: LUA_NO_RUI_SESSION(0x81000000)
(9) JAGab73055/8606105164
While running SNAplus2 R6 on HPUX 11 a link failure
occurred. The sna.err log file recorded message 4096 - 13
(ASSERT: File name = ../../p/vhlwr/vhshmod.c ). This
caused the link to go down for one minute disrupting the
current file transfer. Following the ASSERT, the sdlc
driver executed ten consecutive svphrx() calls. After nine
of these failed the SDLC driver called svphclos() to stop
the link.
(10) JAGab71689/8606105222
The following message is noted periodically in sna.err
file:
10:07:29 EDT 09 Aug 1999 4096-5(0-0) P (UH2010D3)
PID 3733 (snaperrlog)Log parameter mismatch.
Message number = 512 - 137
The message 512 - 137 then follows with a question mark
for the sense code.
(11) JAGab71519/8606104163
This system panic occurred on a H20 running 10.20 with
128MB.
panic+0x10
report_trap_or_int_and_panic+0xe8
trap+0xa48
$call_trap+0x20
nsm_delete_session_id+0x104
nsm_cleanup_lu_lu_session+0x7b8
nsm_fsm_status+0x1d4c
nsm_process_deactivate_session+0x140
nsm_process_record_from_rm+0x1a8
nsm_queue_handler+0x68
nba_dispatch_process+0x114
nba_scheduler+0x208
vpr_stream_uw_svc+0x58c
sq_wrapper+0xb8
str_sched_up_daemon+0x2b0
str_sched_daemon+0xf4
main+0x974
$vstart+0x34
(12) JAGab70700/8606106276
If you are using 3270 with LANG set to de_DE.roman8 on a
character terminal, then the terminal goes into file
transfer mode whenever the host locks the 3270 keyboard.
This is a revisit of