These release notes support Version 1.1.4 of the ptx/CTC software intended for use with Symmetry® 5000, and NUMA computer systems. ptx/CTC manages mission-critical applications during and after cluster transitions. Read this document before you install or run this release of ptx/CTC.
This version of ptx/CTC can be used with the following systems:
The following products must be installed on your system to use V1.1.4 of ptx/CTC:
DYNIX/ptx® V4.5.3 or later
ptx/CLUSTERS V2.2.2 or later
ptx/SVM V2.2.2 or later, if using ptx/CTC for ptx/SVM failover.
ptx/TCP/IP V4.6.3 or later, if using ptx/CTC for IP failover.
ptx/CFS V1.1.3 or later, if using ptx/CTC for CFS object failover.
ptx/CTC V1.1.4 is automatically installed when ptx/CLUSTERS V2.2.2 is installed. For installation instructions, refer to the DYNIX/ptx and Layered Products Software Installation Release Notes.
The ptx/CTC Administration Guide, available on the online documentation CD-ROM or at http://webdocs.numaq.ibm.com/, supports this release of ptx/CTC.
This section lists the following problem report summaries:
The numbers in parentheses identify the problems in the problem-tracking system.
ptx/CTC V1.1.4 includes fixes for the following software defects.
(254251) The -R option of the edc command was not used for attaching and detaching menus.
(254841) The IPADDR failover method contained unneeded route and arp commands.
(250690) The SVMPRIVDG failover method was used in cases other than vxdg -C -x import.
(255131) ptx/CTC Patch 254841 did not install properly.
(255396) ctcadm loaddb ctcfile dumped core due to a syntax error in ctcfile.
(255305) arp entries on systems that recently failed over were incorrect.
(255408) FP#250680 contained an error (a missing quotation mark) in the SVMPRIVDG script.
(255521) When the CTC object was started, the ctc daemon dumped core.
The following problem reports are outstanding for V1.1.4 of ptx/CTC.
Workaround. Do not give two ptx/CTC objects the same name.
Workaround. If you enter the ctcadm command at the UNIX shell prompt, it will accept standard input as arguments. The acceptable arguments should follow the syntax for the ctcadm command as described in the ctcadm man page. An invalid syntax will terminate the interactive mode.
Workaround. Since the ctcadm command is run as root, the root environment is inherited by ctcadm when performing operations such as start, stop, and verify. Perform failover tests manually with root environment by first typing su - root.
Workaround. Always install ptx/CLUSTERS and ptx/CTC together. If you have already installed ptx/CLUSTERS, re-install ptx/CTC from the CD-ROM so that the menus will reappear.
Wordaround. Ignore messages.
Workaround. Stop ptx/CTC, set the database location, and then restart ptx/CTC. This procedure is described in the ptx/CTC Administration Guide, in the section titled "Creating Your ptx/CTC Configuration."
The ptx/CTC database retains knowledge of old node names. This occurs if you permanently remove nodes from the cluster or rename a node in the cluster. This causes extraneous messages in the EESlog file.