Installation guide

Section 3.3:Configuring syslog Event Logging 65
– Verify that the network connection to network-based switches is operational. Most switches
have a link light that indicates connectivity.
– It should be possible to ping the network switch; if not, then the switch may not be properly
configured for its network parameters.
– Verify that the correct password and login name (depending on switch type) have been speci-
fied in the cluster configuration database (as established by running cluconfig). A useful
diagnostic approach is to verify telnet access to the network switch using the same parameters
as specified in the cluster configuration.
After successfully verifying communication with the switch, attempt to power cycle the other cluster
member. Prior to doing this, it would is recommended to verify that the other cluster member is not
actively performing any important functions (such as serving cluster services to active clients). The
following command depicts a successful power cycle operation:
clustonith -r clu3
Successfully power cycled host clu3.
3.2.3 Displaying the Cluster Software Version
Invoke the rpm -qa clumanager command to display the revision of the installed cluster RPM.
Ensure that both cluster systems are running the same version.
3.3 Configuring syslog Event Logging
It is possible to edit the /etc/syslog.conf file to enable the cluster to log events to a file that is
different from the /var/log/messages log file. Logging cluster messages to a separate file will
help to diagnose problems more clearly.
The cluster systems use the syslogd daemon to log cluster-related events to a file, as specified in
the /etc/syslog.conf file. The log file facilitates diagnosis of problems in the cluster. It is
recommended to set up event logging so that the syslogd daemon logs cluster messages only from the
system on which it is running. Therefore, you need to examine the log files on both cluster systems
to get a comprehensive view of the cluster.
The syslogd daemon logs messages from the following cluster daemons:
• cluquorumd — Quorum daemon
• clusvcmgrd — Service manager daemon
• clupowerd — Power daemon
• cluhbd — Heartbeat daemon
• clumibd — Administrative system monitoring daemon