Configuring the collation.properties file entries

This topic lists the collation.properties file entries that the sensor uses.

The following properties specify that the sensor uses sudo to elevate privileges when running Veritas Cluster Server commands:

  • com.collation.discover.agent.command.hastatus.Linux=sudo /opt/VRTSvcs/bin/hastatus
  • com.collation.discover.agent.command.haclus.Linux=sudo /opt/VRTSvcs/bin/haclus
  • com.collation.discover.agent.command.hasys.Linux=sudo /opt/VRTSvcs/bin/hasys
  • com.collation.discover.agent.command.hares.Linux=sudo /opt/VRTSvcs/bin/hares
  • com.collation.discover.agent.command.hagrp.Linux=sudo /opt/VRTSvcs/bin/hagrp
  • com.collation.discover.agent.command.hatype.Linux=sudo /opt/VRTSvcs/bin/hatype
  • com.collation.discover.agent.command.hauser.Linux=sudo /opt/VRTSvcs/bin/hauser
You can scope each property to a specific operating system or IP address, as in the following examples:
  • com.collation.discover.agent.command.hastatus =sudo /opt/VRTSvcs/bin/hastatus
  • com.collation.discover.agent.command.hastatus.Linux=sudo /opt/VRTSvcs/bin/hastatus
  • com.collation.discover.agent.command.hastatus.Linux.192.168.1.1=sudo /opt/VRTSvcs/bin/hastatus

Specify the sudo option for an operating system only if it required for all systems running that operating system; otherwise, specify the option only for the specific IP addresses where the sudo command is configured. You must configure sudo ndd with NOPASSWORD for the access user.

On each target system for which privilege escalation is needed, configure the sudo command with the NOPASSWD option. Otherwise, your discovery hangs until the Agile Service Manager server times out.