Veritas cluster sensor
The Veritas cluster sensor discovers Veritas Cluster Servers.
The sensor collects general information about the Veritas Cluster Server and the services that are installed on it. Services are organized in service groups and contain information about the resources that are used.
The sensor can create relationships between the services and applications installed on a cluster.
Sensor name that is used in the GUI and logs
VeritasClusterSensor
Security issues
- hastatus
- haclus
- hasys
- hares
- hagrp
- hatype
- hauser
Before running Veritas commands, a login to the cluster is performed on systems that support the Veritas halogin command. These are UNIX systems with VCS version 4.1 and higher. The sensor logs in using the user name and password from the High Availability Solutions access list entry.
To specify that the sensor should use sudo when running Veritas Cluster Server commands on Linux® or UNIX systems, configure the appropriate parameters in the collation.properties file.
To run the commands without using the sudo command, the Agile Service Manager service account must be a member of the Veritas Admin Group on the target.
- halogin [user] [password]
- halogout -endallsessions
- halogout -endsession localhost
- haclus -display
- hasys -display
- hares -dep
- hares -display
- hagrp -resources [group]
- hagrp -dep [group]
- hagrp -display
- hatype -display
You must configure sudo ndd with NOPASSWORD
for the access user.
Model objects created
The sensor creates the following model objects:
- app.ConfigFile
- app.SoftwareInstallation
- app.veritas.cluster.VCSCluster
- app.veritas.cluster.VCSHADServer
- app.veritas.cluster.VCSLocalServiceGroup
- app.veritas.cluster.VCSResourceConfiguration
- app.veritas.cluster.VCSServiceGroup
- app.veritas.cluster.VCSSystem