PLY_WAT-VMS SNSALPECO03022 PLY System Watchdog V2.2 Alpha ECO Summary
NOTE: An OpenVMS saveset or PCSI installation file is stored
on the Internet in a self-expanding compressed file.
The name of the compressed file will be kit_name-dcx_vaxexe
for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha.
Once the file is copied to your system, it can be expanded
by typing RUN compressed_file. The resultant file will
be the OpenVMS saveset or PCSI installation file which
can be used to install the ECO.
Copyright (c) Digital Equipment Corporation 1995, 1997. All rights reserved.
PRODUCT: POLYCENTER System Watchdog
OP/SYS: OpenVMS Alpha
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: SNSALPECO03022
ECO Kits Superseded by This ECO Kit: SNSALPECO02022
SNSALPECO01022
ECO Kit Approximate Size: 40950 Blocks
Saveset A - 315 Blocks
Saveset B - 11088 Blocks
Saveset C - 29547 Blocks
Kit Applies To: POLYCENTER System Watchdog V2.2
OpenVMS Alpha V6.1 and V6.2
System Reboot Necessary: No
ECO KIT SUMMARY:
An ECO kit exists for POLYCENTER System Watchdog V2.2 on OpenVMS Alpha
V6.1 and V6.2.
Problems Addressed in the SNSALPECO03022 Kit:
o Homogenized communication protocol layers for the Controller (sense
watchdog add|delete message), the Consolidator (requests) and the
SNS$SHR.EXE shareable image, while removing a deadlock possibility
in the tasking mechanism in use there.
o Node name length limit was raised from 6 to 16 characters.
o Arranged for event messages list redisplay after a considered Agent
node went unreachable, then reachable again.
o Cured potential Ada exception raising problems when an user program
would call SNS$SHR.EXE entries.
o Shadow sets related event messages now are correctly consolidated
with the cluster alias on clusters.
o Now using the SYSGEN parameter SCSNODE instead of the SYS$NODE
logical name translation.
o Added the SNS$LOOPING_PROCESS_CPU_RATIO logical name to allow the
user for tuning the LOP event conditions if necessary on some Agent
nodes.
o Presence of prerequisite DEC Ada RTL V6.2 is now checked during
installation of ECO.
o On nodes running DECnet phase V, the node synonym option is now set
for the SNS$WATCHDOG session control application, as required to
accommodate node short names usage.
o Year 2000 concerns are now dismissed to 31-DEC-9999 23:59:59.99
Problems Addressed in the SNSALPECO02022 Kit:
o Network connection attempts that timeout are now logged under the
OTH event code instead of the UNReachable node event code to help
their identification.
o Unauthorized TCP/IP connections to the Agent now are correctly
rejected.
o Extra vertical bar tailing the 8th parameter to action routines was
removed.
o Agent now can be used in TCP/IP only environments.
o The /LOG qualifier to the Controller "add message" and "delete
message" commands now correctly lets those commands display a
success message when the external event message can be respectively
added or removed successfully.
o The External Event Messages handling API, SYS$SHARE:SNS$SHR.EXE,
broken in the ECO01, is now fixed.
o You now can tune the timeout delay upon DECnet connection requests
(used to be about 40s, hardcoded in DECnet itself) and
acknowledgments (could hang forever in certain situations).
The default delay is now 15 seconds, and is tunable using the
SNS$DECNET_CONNECTION_TIMEOUT logical name.
Thanks to the above modification, the Agent no longer randomly
enters a deadlock state as sometimes happened on Alpha
multiprocessor systems (such as Digital Alpha servers 2100, 7620,
7720, etc...), consecutively to some local DECnet connectivity
operations.
o The local nodename is now fetched from SYSGEN parameter "SCSNODE"
instead of the SYS$NODE system logical name translation.
o The Controller no longer hangs when reading its command input from a
DCL file, and the input flow is not terminated with the EXIT keyword.
o The Consolidator no longer hangs on Alpha, unlike it sometimes did
randomly with the ECO01.
Problems Addressed in the SNSALPECO01022 Kit:
o The OpenVMS Agent can now be polled using TCP/IP. This
was not possible with the previous version which was limited
to DECnet access only.
NOTE: This ability relies on the UCX TCP/IP services presence.
o The TCP/IP communications error handling has been enhanced.
o The Consolidator now retries DECnet connection attempt before
generating a node UNReachable event.
o Action routines are not triggered anymore for each and every
message concerning a node newly detected as unreachable.
o A new logical name SNS$CONSOLIDATOR_BASE_PRIORITY can be defined
to customize the newly started Consolidators base priority. The
default priority was raised from 2 to 3 (batch priority).
o The Consolidator now accepts concealed logical names in logfile
specification as well as output and error file pathnames.
o A problem in System Watchdog V2.2 preventing the reuse of existing
consolidator logfiles has been corrected.
o The sense watchdog controller command can now read subsequent
commands on the standard input.
o A correction in Shadow Set names validation allows their
specification by logical name.
o Host based shadow set members states are now correctly detected.
o The SNS$SHR.EXE shareable image entries (external messages
management API) do not fail anymore when called intensively.
o Sample modules written in the C language provided in the
SNS$EXAMPLES directory are now ported to DEC C.
o New examples have been added in the SNS$EXAMPLES directory.
o The SNS$FEED_PCM.C source file for the sample POLYCENTER Console
Manager feeder was tidied up.
o The installation procedure is now more flexible about the transport
layer configuration. In addition, NCL commands have been provided
for DECnet phase V.
o The "Warning: OSFNOD is a cluster alias ..." validation message
is not issued anymore when polling an OSF/1 node through DECnet
phase V.
o The available range for the polling interval value is now
[0..65535].
o The DECtalk set LINE parameter now accepts logical names.
o The output for SHOW DECTALK_SET /FORMAT=COMMAND has been corrected.
o The Agent no longer randomly enters a deadlock state as sometimes
happened on Alpha multiprocessor systems (such as DEC7620,
DEC7720), consecutively to some network I/O operation.
Please refer to the Release Notes, SNS_ECO03022.RELEASE_NOTES, included
in this ECO for additional information.
INSTALLATION NOTES:
The system/cluster does not need to be rebooted after this kit is
installed. Important Post-Installation Operations:
o Stop and restart the Agent:
The installation procedure normally takes care of Agent stop and
restart on the local node. If you are working on a cluster, you
need however to manually stop and restart Agents on other cluster
members. Please refer to the installation guide and the
installation logfile for details.
o SNS$WATCHDOG object and account passwords coherence:
The installation procedure will update the password for the
SNS$WATCHDOG account and, if you are running DECnet Phase IV,
will ensure that the SNS$WATCHDOG DECnet object on the local node
will receive the very same password as the account.
If you are working on a cluster, you need to ensure this
coherence for both permanent and volatile NCP databases. You can
retrieve the new password from NCP on the local node, then use
SYSMAN to update the NCP databases accordingly of all other
cluster members (The installation logfile shows sample commands
to achieve this).
o Checking the new software proper installation:
You might want to check whether the ECO03 kit installation went
well on all concerned nodes. Simply start a new Consolidator
with a profile configured to poll all interesting Agents, then
the following command displays the list of Agents along with
their respective versions as well as the Controller and
Consolidator versions:
$ SENSE WATCHDOG SHOW CONSOLIDATOR/FULL
For all systems where the ECO03 kit was installed, that version
should be "V2.2-11".
IMPORTANT: This POLYCENTER System Watchdog V2.2 ECO03 kit requires
the new DEC Ada RTL V6.2. Check the version of the
following file: SYS$SHARE:ADARTL.EXE.
Unlike on OpenVMS V6.2, the new DEC Ada RTL V6.2 is not
native on OpenVMS V6.1, and has to be installed separately
prior to installing this ECO03 kit.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
snsalpeco02022.README
snsalpeco03022.CHKSUM
snsalpeco03022.CVRLET_TXT
snsalpeco03022.a-dcx_axpexe
snsalpeco03022.b-dcx_axpexe
snsalpeco03022.c-dcx_axpexe
|
