CA^® Network and Systems Management System Monitoring Option for OpenVMS r3.2

10.0 Contact Customer Support

1.0 Welcome

This readme file provides information that supplements the CA Network and Systems Management (NSM) System Monitoring Option for OpenVMS documentation.

2.0 Operating System Support

CA NSM System Monitoring Option for OpenVMS r3.2 supports the following operating systems:

• HP OpenVMS Industry Standard 64 V8.2-1, V8.3, and V8.3-1H1

• HP OpenVMS Alpha V7.3-2, V8.2, and V8.3

  We recommend that you install any HP OpenVMS ECOs with an installation rating of 1.

3.0 System Requirements

TCP/IP Stack Requirements

• HP TCP/IP Services for OpenVMS Industry Standard 64 V5.5 and V5.6

• HP TCP/IP Services for OpenVMS Alpha V5.4, V5.5 and V5.6

• Process Software TCPware 5.7-2

• Process Software MultiNet V5.1 and V5.2

3.1 Agent Technology Services

OpenVMS I64 Requirements

• To install Agent Technology Services a minimum of 360,000 blocks free disk space is required.

• To run the Agent Technology Services a minimum of 125,000 blocks free disk space is required.

OpenVMS Alpha Requirements

• To install Agent Technology Services a minimum of 250,000 blocks free disk space is required.

• To run the Agent Technology Services a minimum of 70,000 blocks free disk space is required.

Disk space refers to space required for the product base files and does not take into account the requirements for log and archive data collected by CA NSM System Monitoring Option.

3.2 OpenVMS System Agent

OpenVMS I64 Requirements

• To install Agent Technology Services a minimum of 75,000 blocks free disk space is required.

• To run the Agent Technology Services a minimum of 15,000 blocks free disk space is required.

OpenVMS Alpha Requirements

• To install Agent Technology Services a minimum of 65,000 blocks free disk space is required.

• To run the Agent Technology Services a minimum of 15,000 blocks free disk space is required.

Disk space refers to space required for the product base files and does not take into account the requirements for log and archive data collected by CA NSM System Monitoring Option.

3.3 Log Agent

OpenVMS I64 Requirements

• To install Agent Technology Services a minimum of 60,000 blocks free disk space is required.

• To run the Agent Technology Services a minimum of 10,000 blocks free disk space is required.

OpenVMS Alpha Requirements

• To install Agent Technology Services a minimum of 60,000 blocks free disk space is required.

• To run the Agent Technology Services a minimum of 10,000 blocks free disk space is required.

Disk space refers to space required for the product base files and does not take into account the requirements for log and archive data collected by CA NSM System Monitoring Option.

4.0 CA NSM Manager Support

Unicenter NSM 3.1-0506

CCS-0307 GA + Maintenance – 9-14-05

CA NSM or CCS r11

CA NSM or CCS r11.1, r11.2

If you are using OpenVMS caiLoga2 agent, you must first apply the following patch:

Version Number	Patch
r11 GA	QO82137 or later (not necessary for r11 CUM)

If you are using OpenVMS System Agent, you must first apply the following patch:

Version Number	Patch
r11.2 GA	RO04299 (This is not necessary if you install CCS r11.2 from the SMO r3.2 DVD.)

Note: Make sure to install the Windows side OpenVMS System Agent components from the CA NSM System Management Option for OpenVMS Product Explorer.

5.0 Installation Considerations

• Natively Mount CD on OpenVMS. Use the following command to mount the CD and bring up the install menu. The word “device” needs to be replaced with your own drive information.

  To mount the CD on OpenVMS, enter the following command at the DCL prompt:

  $ mount/over=id device:
  

  To bring up the install menu, enter the following command at the DCL prompt:

  $ run device:[000000]setup_platform.exe
  

  Note: Device is the CD-ROM or DVD-ROM drive. Platform is the OpenVMS platform you are installing on, either alpha or ia64. An example command might be:

  $ run DQA0:[000000]setup_ia64.exe
  

• With the release of CA NSM System Monitoring Option for OpenVMS r3.2, the packaging for OpenVMS Alpha has changed. The package contains three discs: one disc for CA NSM System Monitoring Option for OpenVMS VAX r3.0, and two discs for CA NSM System Monitoring Option for OpenVMS Alpha r3.2.  Please note that although the VAX r3.0 disc also contains the Alpha r3.0 release, you should only install on Alpha using the Alpha r3.2 disc. One exception: use the r3.0 disc to install on OpenVMS Alpha V6.2.

• After installing a component of CA NSM System Monitoring Option for OpenVMS in a cluster with a shared system disk, when you install on a subsequent node, the install might say that the component is already installed, whether it is installed on the cluster node or not. Ignore the message and continue with the component install. For example, when installing the Agent Technology Services component, you might see this question:

  This version of CA NSM AGENT TECHNOLOGY SERVICES is already installed
  * Do you want to continue [YES] ?
  

  Enter YES (or press Enter) to continue and complete the installation.

5.1 Upgrade Considerations

Upgrade to CA NSM System Monitoring Option for OpenVMS r3.2 is supported from the following versions, which are in active support:

• Unicenter NSM System Monitoring Option for OpenVMS 3.0 (Alpha)

• Unicenter NSM System Monitoring Option for OpenVMS r3.1 (I64)

If you upgrade the OpenVMS System Agent in a cluster, refer to the Cluster Monitoring section for important information.

6.0 General Considerations

This section contains general information you should know before using CA NSM System Monitoring Option for OpenVMS r3.2.

6.1 Version Numbers

CA has changed their product version scheme. The official version of this release of CA NSM System Monitoring Option for OpenVMS is r3.2. This version is the same as V3.2.

6.2 MultiNet

For systems running MultiNet, you might need to manually change the SNMP trap port of 162. Replace “162” with another port number in the following file:

SYS$SYSDEVICE:[AWS.node.SERVICES.CONFIG.AWS_SADMIN]AWS_SADMIN.CFG

6.3 Cluster monitoring

If you upgrade the OpenVMS System Agent in a cluster, for best results, first disable all cluster monitoring. Re-enable cluster monitoring when the upgrades are complete.

Preferred Node to Monitor the cluster

To set a Preferred Cluster Monitor, use one of the following methods:

• Set the value “Set Node to Monitor Cluster:” on the “OpenVMS Agent View – Cluster Monitor” abrowser page

• Set the preferred Cluster Monitor MIB field - vmsAgentClusterNodeToMonitor - via a configset.

With either method, the preferred cluster monitor value is propagated to all nodes in the cluster that are enabled to monitor the cluster.

When an active "set monitor" is done, the agent attempts to set the Cluster Monitor to this value.

For issues regarding cluster monitoring, see the Known Issues list.

6.4 Object Granularity

For information on Object Granularity, see the Unicenter® Network and Systems Management document “Inside Systems Management Guide”, available on Support Online.

To turn on Object Granularity for the OpenVMS System Agent, complete the following tasks on the Windows management system:

1. Stop the 2D Map.

2. Stop awservices: awservices stop.

3. Load the granularity change as follows:

   For r11.x

   awwvcfg -c "%AGENTWORKS_DIR%\services\config\distrib\
   wvgate\sysagtvms.wvc_gran"
   

   For 3.1

   awwvcfg -c "%AGENTWORKS_DIR%\SERVICES\CONFIG\
   AWS_WVGATE\sysagtvms.wvc_gran"
   

4. Start the awservices: awservices start.

5. If necessary, start the 2D Map.

Note: When Object Granularity is in use and you remove a monitored object via the Abrowser or MIB browser, the object's granularity object is not automatically removed from the 2D Map. This might result in black being propagated up the 2D Map. You must remove the granularity object manually. Drill down to the object in the 2D Map, switch to Design Mode, select the object, right click and choose Delete, choose Delete child objects, and then click OK. Switch back to Run Mode.

6.5 Username case-sensitivity

When populating the Cluster page that checks for Process presence cluster-wide, it is now necessary to respect the string casing shown by “SHOW SYSTEM “ and “SHOW PROCESS/ID= “ for both the Process name and the Username. Node names remain case-insensitive. In earlier versions, only the Process name was considered case-sensitive. However, the monitoring of special processes such as the DECwindows component DTLOGIN and the DFS server process DFS$COM_ACP requires username case-sensitivity.

6.6 Custom community strings

If you are using custom community strings with CA NSM r11.2, CA recommends the following settings:

Node Class:     Host:OpenVMS
Agent Classes:  ANY
Port Number:  6665

Note: See the section 4.0 CA NSM Manager Support for a required patch with OpenVMS Agents and NSM r11.2.

7.0 Known Issues

The following are known issues for CA Network and Systems Management System Monitoring Option for OpenVMS for r3.2:

• The following Status Policy is not supported with OpenVMS caiLogA2 agent:

  First Line Only

• CA NSM 3.1 patch QO74293 is required to fix the truncation problems that might rise when using the abrowser interface to collect and display large lists of objects available for monitoring, as sampled by the System Agent.

  Object list truncation in the abrowser pages occurs when a user requests for data using the abrowser “View Menu, Available XXX Menu Items”, and when the returned buffers exceed certain sizes. This patch fixes all concerned object lists.

• The “SizeChng” field on the system agent's abrowser Monitoring Files page is reflecting a static value—the number of bytes the file must grow during the poll in order to trigger—rather than the dynamic value that the online abrowser help states (indicates how much the file has grown since the last poll).

• The System Agent Abrowser might display the message “Warning- an error occurred while processing this request. Script: browser.SysAgtVMS Node: <node-name> View: Batch Jobs” when using NSM or CCS r11.1 and the MultiNet stack. To avoid this message, change the SNMP version from “v2c” to “v1” in the OpenVMS Agent View SNMP Connection Parameters window which is accessed from the File menu, Connect entry.

• With NSM r3.1, when you select a granularity icon, right click and choose View Agent, you see a repository error: "CA-Unicenter NSM   X  CAE0323: Repository error. Error Code: 53." This can be safely ignored.
  To view the agent, right click off the parent OpenVMS Agent icon and choose View Agent.

7.1 Cluster Monitoring Issues

• When cluster monitoring is enabled and a preferred cluster monitor is in use, you might experience SADMIN database corruption on a node in the cluster. When this corruption occurs, you need to recreate the SADMIN database. See the section “Troubleshooting Your Setup” in the document “Using the System Monitoring Option”. If you do not regenerate the database, you will not be able to restart the System Agent.

• If cluster monitoring is enabled and you wish to scan for missing processes where two processes of the same name on a single system have different usernames, you must use the cluster-wide scan. If you scan from an individual system, you will not be able to single out these processes.

• “Agent Status” in the abrowser Cluster View: the “Cluster Monitored Nodes” page is incompletely implemented and might show an incorrect status. Specifically, the cluster monitor state within a given running agent might not be picked up properly.

• When rapid changes are made to the Preferred Cluster Monitor node via “Set Node to Monitor Cluster:”, you might see object store corruption. To avoid this corruption, allow the change to “settle”. Wait until you see the desired Cluster Monitor change on the abrowser page where the change was originated. Repeat the “Set” if necessary to see the desired value.

• When multiple system agents are stopped and started concurrently and a preferred cluster monitor is in use, you might see object store corruption. Avoiding concurrent starts and stops to avoid this corruption.

• If you set monitor to a system that is not known to the agent node, there is no feedback to inform you of this fact.

8.0 Published Fixes

The complete list of published bug fixes for this product can be found at CA Support Online: https://support.ca.com .

The following fixes and behavioral changes are included in this release. These fixes are new for r3.2. Where applicable, the published PTF number is specified before the description of the fix:

PTF Number	Description
QO82137	The caiLogA2 agent on OpenVMS is not being discovered by CA NSM r11. Traps from agent are not recognized.
QO86045	When the OpenVMS I64 operating system has marked sections of memory as bad, the system agent does not detect it.
QI91087	In the guide Using the System Monitoring Option for OpenVMS I64, Appendix C is incorrect and commands on 2-19 and 2-20 are incorrect.
QO91902	The system agent might take a long time to startup with a configset. The problem seems more prone to happen when there are many cluster processes in the configset. This fix is to be used when the System agent, version 3.1 has already been installed on the system.
QO91903	The system agent might take a long time to startup with a configset. The problem seems more prone to happen when there are many cluster processes in the configset. This fix is a patch to the original installation kit of the System agent, version 3.1, and is applied before the System agent is installed.
RO04629	Sites with multiple NIC cards cannot bind the services and agent to a specific address. Also need that address in the PDU.

9.0 Documentation

The file names for the PDF guides are as follows:

Guide Name	File Name
CA Network and Systems Management System Monitoring Option for OpenVMS Using the System Monitoring Option	CANSM_Using_SMO.pdf
CA Network and Systems Management System Monitoring Option for OpenVMS Using the Log Agent	CANSM_Using_Logagent.pdf
CA Network and Systems Management System Monitoring Option for OpenVMS Release Notes	CANSM_Release_notes.pdf
Unicenter Common Services Administrator Guide	CCS_Administrator_ENU.pdf

To view PDF files, you must download and install the Adobe Reader from the Adobe website if it is not already installed on your computer.

Updated guides are available at http://ca.com/support.

10.0 Contact Customer Support

Contact Technical Support

For online technical assistance and a complete list of locations, primary service hours, and telephone numbers, contact Technical Support at http://www.ca.com/support.

Provide Feedback

If you have comments or questions about CA product documentation, you can send a message to techpubs@ca.com.

If you would like to provide feedback about CA product documentation, please complete our short customer survey, which is also available on the CA Support website.