CommandPointTM for Unicenter TNG® V1.0.0 is an integration module (add-on) that provides Computer Associates® (CA) Unicenter TNG V2.1 access to basic NUMA-Q®-specific administrative capabilities and data.
CommandPoint for Unicenter TNG provides the following features:
launching capability for the NUMA-Q CommandPoint family of products (CommandPoint Admin, CommandPoint Clusters, and CommandPoint SVM)
integration of NUMA-Q-specific errors and events (EES information)
integration of NUMA-Q SNMP subagent (SNMP trap) information
These Release Notes contain the following information:
Compatibility information
Installation instructions
Launching CommandPoint Products
ptx®/AGENT Integration
EES Integration
These release notes do not describe how to use Computer Associates products. Refer to the Computer Associates documentation for that information.
CommandPoint for Unicenter TNG V1.0.0 is compatible with CA Unicenter TNG V2.1.
CommandPoint for Unicenter TNG V1.0.0 is compatible with the following software products running on Symmetry® and NUMA-Q® systems:
DYNIX/ptx® V4.4.4 or later (required)
ptx/LAN V4.5.3 or later (required)
ptx/TCP/IP V4.5.1 or later (required)
ptx/NFS® V4.6.2 or later (optional)
ptx/AGENT V1.3.1 (required)
EES V1.0.1 (required)
ptx/SVM V2.1 (optional)
ptx/CLUSTERS V2.1 (optional)
CommandPoint SVM V2.1.0 (optional)
CommandPoint Clusters V2.1.0 (optional)
CommandPoint Admin V4.4.0 (optional)
Windows NT® V4.0 (with Service Pack 3 or later) (required)
CommandPoint for Unicenter TNG has two separate installation processes, one for DYNIX/ptx and one for Windows NT.
CommandPoint for Unicenter TNG V1.0.0 is installed on DYNIX/ptx using ptx/INSTALL. Perform the following steps to install and setup CommandPoint for Unicenter TNG:
Check that CA Unicenter TNG is installed and configured.
Install TNG_EventForwarder V1.0 using ptx/INSTALL.
Modify the master agent's config file /usr/agent/config/agt/snmpd.cnf (refer to the Modifying the Master Agent Configuration File section for details)
Determine which level of EES errors (info, warning, or error) you want forwarded to CA Unicenter. Then execute: tng_evtfwd set filter={info|warning|error} tng_dir=/tng. For example: tng_evtfwd set filter=warning tng_dir=/opt/tng (This command will modify the tng_evtfwd.cfg file every time it is executed.)
Start forwarding events by executing: tng_evtfwd start. To stop EES event forwarding, you would enter: tng_evtfwd stop.
ATTENTION The TNG Event Management application must be started prior to starting tng_evtfwd.
After starting the TNG Event Management application, check the following directory for the TNG pipe file:
%TNGDIR%/opr/config/%hostname%/pipe
There should be only one pipe file. If there is more than one pipe file, you need to stop the TNG Event Management application, remove all the files under %TNGDIR%/opr/config/%hostname%/pipe, and restart the TNG Event Management application.
You need to modify the ptx/AGENT's master agent's configuration file /usr/agent/config/agt/snmpd.cnf so that it will be recognized by the TNG discovery process and be able to send traps to the manager node (on Windows NT) as follows:
Modify the sysObjectID value in the /usr/agent/config/agt/snmpd.cnf as follows so that the TNG discovery process is able to recognize a NUMA-Q server host (what you need to enter is in bold):
# Entry type: sysObjectID # Entry format: OIDsysObjectID internet.4.1.147.3.1.1.1.3
Modify the notifyEntry as follows so that ptx/Agent sends traps to the TNG manager node (what you need to enter is in bold):
#Entry type: notifyEntry #Format: notifyIndex (integer) #notifySPI (snmpv1, snmpv2c, usecNoAuth, usecAuth, usecPriv) #notifyIdentityName (text) #notifyTransportLabel (text) #notifyContextName (text) #notifyViewName (text) #notifyMemoryType (nonVolatile, permanent, readOnly)notifyEntry 1 snmpv1 public myhost SEQUENT All nonVolatile
Modify transportEntry as follows so that ptx/Agent sends traps to the TNG manager node (what you need to enter is in bold):
#Entry type: transportEntry #Format: transportLabel (text) #transportSubIndex (integer) #transportDomain (snmpUDPDomain, snmpIPXDomain, etc.) #transportAddress (transport address, i.e. 192.147.142.254:0) #transportReceiveMask (transport mask, i.e. 255.255.255.252:0) #transportMMS (integer) #transportMemoryType (nonVolatile, permanent, readOnly)
transportEntry myhost 1 snmpUDPDomain 192.147.142.254:0 255.255.255.255:0 150
ATTENTION Replace the 192.147.142.254 with your Unicenter TNG manager node's IP address.
Modify the acEntry as follows (what you need to enter is in bold):
#Entry type: acEntry #Format: acSPI (snmpv1, snmpv2c, usecNoAuth, usecAuth, usecPriv) # acGroupName (text) # acContextName (text) # acContextNameMask (octetString) # acPrivs (nothing, readOnly, readWrite) # acReadViewName (text) # acWriteViewName (text) # acMemoryType (nonVolatile, permanent, readOnly) acEntry snmpv1 Anyone default - readOnly All All nonVolatile
acEntry snmpv1 Privileged default - readWrite All All nonVolatile
acEntry snmpv2c Anyone default - readOnly All All nonVolatile acEntry snmpv2c Privileged default - readWrite All All nonVolatile
Modify the communityEntry as follows:
#Entry type: communityEntry #Format: communityAuthSnmpID (octetString) # communityName (text) # communityGroupName (text) # communityContextSnmpID (octetString) # communityContextName (text) # communityTransportLabel (text) # communityMemoryType (nonVolatile, permanent, readOnly)
communityEntry localSnmpID admin Privileged localSnmpID default - nonVolatile
communityEntry localSnmpID admin Privileged localSnmpID default - nonVolatile communityEntry localSnmpID public Anyone localSnmpID default - nonVolatile communityEntry localSnmpID publicV2 Privileged localSnmpID default - nonVolatile
CommandPoint for Unicenter TNG V1.0.0 is installed on Windows NT using Installshield.
Perform the following steps to install and setup CommandPoint for Unicenter TNG:
Check that CA Unicenter TNG is installed and configured.
If you have installed CommandPoint Admin, CommandPoint Clusters, and CommandPoint SVM, verify the installation directory of these three products. For example, the default path for CommandPoint Admin is c:\ProgramFiles\CommandPoint.
Load the System Management CD and click on \cptng\setup.exe
After installing CommandPoint for Unicenter TNG, perform the following tasks to activate the ptx/AGENT's policy on the Distributed State Machine:
At the manager node, open a DOS command prompt and stop TNG by executing unicntrl stop all.
At the manager node, Stop Agent services by executing aswervices stop.
Change directories to cptng_Install_Dir\trix and run setup.bat to import new classes and objects into the repository.
Run the DSM Wizard and select sqntPtxMib, sqntClustersMib, sqntSvmMib to be monitored by the Distributed State Machine, and click Next. Make sure that Host:Sequent_server is in the Node class name for each of the NUMA-Q SNMP sub agents, then click Next. Select the sub-net or the individual host(s) to be managed.
Make sure that ptx/AGENT is running on the NUMA-Q machine that you want to monitor.
From the DOS command prompt on the manager node, run resetdsm at the command prompt. After resetdsm is finished, run awservices start.
Restart TNG by executing unicntrl start uni.
You can launch the NUMA-Q CommandPoint family of products (CommandPoint Admin, CommandPoint Clusters, and CommandPoint SVM) from CommandPoint for Unicenter TNG. You can launch these NUMA-Q applications from the TNGS 2D/3D map.
The CommandPoint Admin launching menu-item is accessible via the NUMA-Q Server Icon level. The CommandPoint Clusters and CommandPoint SVM launching menu-items are accessible via the Agent object icon that TNG has found and created.
CommandPoint for Unicenter TNG sends SNMP trap status to CA Unicenter TNG.
After installing CommandPoint for Unicenter TNG, you need to reset the Distributed State Machine. TNG will create the ptx, Clusters, and SVM Agent objects for a NUMA-Q Server if it finds that the sub agents are running on the server. It is important to make sure that the ptx, clusters, and SVM sub-agents are running on the NUMA-Q server before resetting the Distributed State Machine.
From the TNG Agent object icon, you can start the following:
TNG's Object View application in context (meaning point to the correct host and load the appropriate mibs).
TNG's Agent View
TNG's Node View application
TNG's Mib Browser
CommandPoint Clusters application (if the Clusters agent is installed) or CommandPoint SVM application (if the SVM agent is installed).
CommandPoint for Unicenter TNG forwards EES events to TNG and the TNG console log.
After installing and setting up the TNG Event Forwarder (tng_evtfwd), errors and events will be forwarded to the Console log the same way that TNG collects events from syslog. There is no new interface on the manager node (the Windows NT console log); however, on the managed node (the NUMA-Q server) the tng-evtfwdd daemon should be running (see tng_evtfwd man page for more usage information).
ATTENTION This daemon should be installed only if TNG Enterprise management was installed. It should be re-cycled (stop and start) after the TNG enterprise management is re-cycled.