Control Compliance Suite for UNIX Best Practices for Agent or Agentless registration in a large UNIX environment

Article:TECH166893  |  Created: 2011-08-10  |  Updated: 2012-10-25  |  Article URL
Article Type
Technical Solution



Control Compliance Suite (CCS) for UNIX Data Collector Best Practices for setting up Agent or Agentless registration in a large UNIX environment




IBM, Solaris


The customer environment consists of up to 4000 UNIX systems and needs to determine the best way to go about adding them to the CCS for UNIX Data Collector


It is recommended to create a spreadsheet of all UNIX servers in the network with the following information prior to configuring CCS for UNIX Data Collector. This spreadsheet should contain the following information per UNIX server:

1.) All IP Addresses for the target system.

2.) All FQDNs for the target system.

3.) UNIX OS type.

4.) UNIX version.

For multi-NIC cards on a UNIX system that may have multiple FQDNs per IP address or several IP addresses with different FQDNs per UNIX system, it is advised to choose one corresponding IP/FQDN per target UNIX system to be used for the CCS for UNIX Agent or Agent-based mode and note this in the spreadsheet prior to configuration. Also check that the target UNIX system and CCS for UNIX Data Collector can be pinged by IP address and FQDN from both sides and that port 1236 can be reached from both sides. This will prevent confusion in managing CCS for UNIX nodes by preventing problems with registering the same target UNIX machine twice to CCS for UNIX. It also will prevent possible connectivity issues during registration or running queries that fail due to network related problems of pointing to the wrong IP/FQDN of a target UNIX server. For Solaris Zones, treat those target devices as separate UNIX servers in the spreadsheet and determine the best IP/FQDN to connect to.

Article URL

Terms of use for this information are found in Legal Notices