These release notes support Version 1.1.5 of the ptx®/CTC software intended for use with IBM® NUMA-Q and Symmetry® 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:
ptx/CTC requires that the following products be installed on your system:
DYNIX/ptx® V4.4.10.
ptx/CLUSTERS V2.1.4.
ptx/SVM V2.1.4, if using ptx/CTC for ptx/SVM failover.
ptx/TCP/IP V4.5.4 or later, if using ptx/CTC for IP failover.
ptx/CFS V1.0.5 if using ptx/CTC for CFS object failover.
The database must be accessible to all nodes in the cluster and should be stored on a raw shared ptx/SVM volume or a raw shared partition. It is strongly recommended that the database reside on a mirrored, shared ptx/SVM volume as a safeguard against disk failure. Each object in the database uses approximately 2,000 bytes of space. In general, the database should be large enough to hold the maximum number of objects in your configuration, plus room for future growth.
For installation instructions, refer to the DYNIX/ptx and Layered Products Software Installation Release Notes.
Note that ptx/CLUSTERS V2.1.4 or later must already be installed or must be installed at the same time as ptx/CTC V1.1.5.
The following documentation is available on the HTML documentation CD:
This section lists the following problem report summaries:
The numbers in parentheses identify the problems in the problem-tracking system.
This release of ptx/CTC contains fixes for the following software defects:
(254841) The IPADDR failover method contained unneeded route and arp commands.
(250680) When the delay was set to greater than 0, the WLU did not deploy.
(250690) The SVMPRIVDG failover method was used in cases other than vxdg -C -x import.
(255393) During normal failover in a 3-node cluster, the final MAC addresses were incorrect, resulting in two of the nodes not being able to ping each other, while the third node could ping both of the other nodes.
(255396) ctcadm loaddb ctcfile dumped core due to a syntax error in ctcfile.
(255521) When the CTC object was started, the ctc daemon dumped core.
This section lists open problems in this release of ptx/CTC:
Workaround. Do not give two ptx/CTC objects the same name.
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.
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."