Red Hat NETWORK SATELLITE 5.3.0 - CHANNEL MANAGEMENT, Reference Manual

Page: 177 / 318

Monitoring the RHN Server
165
CPU used, and the WARNING threshold is set to 70 percent, the probe will go into a WARNING state.
Some probes offer a multitude of such thresholds.
In order to get the most out of your Monitoring entitlement and avoid false notifications, Red Hat
recommends running your probes without notifications for a time to establish baseline performance
for each of your systems. Although the default values provided for probes may suit you, every
organization has a different environment that may require altering thresholds.
8.5.3. Monitoring the RHN Server
In addition to monitoring all of your client systems, you may also use RHN to monitor your RHN
Server, whether that be an RHN Satellite a RHN Proxy Server. To monitor your RHN Server, find a
system monitored by the server, and go to that system's
System Details � Probes
tab.
Click
create new probe
and select the
Satellite
Probe Command Group. Next, complete the
remaining fields as you would for any other probe. Refer to
Section 8.5.1, “Managing Probes”
for
instructions.
Although the RHN Server appears to be monitored by the client system, the probe is actually run from
the server on itself. Thresholds and notifications work normally.
Note
Any probes that require Red Hat Network Monitoring Daemon connections cannot be
used against a RHN Satellite or RHN Proxy Server on which Monitoring software is
running. This includes most probes in the Linux command group as well as the Log Agent
probes and the Remote Program probes. Use the Satellite command group probes to
monitor RHN Satellites and RHN Proxy Servers. In the case of Proxy scouts, the probes
are listed under the system for which they are reporting data.
8.6. Troubleshooting
Though all Monitoring-related activities are conducted through the RHN website, Red Hat provides
access to some command line diagnostic tools that may help you determine the cause of errors. To
use these tools, you must be able to become the
nocpulse
user on the RHN Server conducting the
monitoring.
First log into the RHN Server as root. Then switch to the
nocpulse
user with the following command:
su - nocpulse
You may now use the diagnostic tools described within the rest of this section.
8.6.1. Examining Probes with
rhn-catalog
To thoroughly troubleshoot a probe, you must first obtain its probe ID. You may obtain this information
by running
rhn-catalog
on the RHN Server as the
nocpulse
user. The output will resemble:
2 ServiceProbe on example1.redhat.com (199.168.36.245): test 2