RingMaster Management Guide - Juniper Networks
RingMaster Management Guide - Juniper Networks
RingMaster Management Guide - Juniper Networks
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>RingMaster</strong> Services<br />
5. To prevent <strong>RingMaster</strong> Services from accepting all types of certificates from the MXs it<br />
monitors, click Accept all certificates to disable the option. By default, <strong>RingMaster</strong> Services<br />
accepts certificates from MXs regardless of whether they are generated by a certificate<br />
authority (CA) or they are self-signed certificates. When you disable this option, the Accept<br />
self-signed certificates option remains enabled.<br />
6. To prevent <strong>RingMaster</strong> Services from accepting self-signed certificates from the MXs it<br />
monitors, click Accept Self-signed certificates to disable the option. When both the Accept<br />
all certificates and Accept Self-signed certificates options are disabled, <strong>RingMaster</strong><br />
Services accepts only CA generated certificates.<br />
7. To specify a key store filename and a password to protect access to that file:<br />
a. Enter the filename in the File field.<br />
b. To change the file type for the key store file, select one of the following in the Type<br />
pull-down:<br />
◆ PKCS12 — Public-Key Cryptography Standard number 12, the standard format used by<br />
Linux machines.<br />
◆ JKS — Java Key Store, a format used by Java platforms and applications.<br />
c. Enter the password in the Password field. When both the Accept all certificates and Accept<br />
self-signed certificates options are disabled, and you specify a key store file, <strong>RingMaster</strong><br />
Services accepts a certificate from an MX only if the public key information for that<br />
certificate is in the key store file.<br />
Click Save to save the changes.<br />
Monitoring Settings<br />
By default, status monitoring and monitoring of MX notifications is enabled. Status monitoring supplies<br />
data for the Explore and Status Summary windows of the Monitor tab. SNMP notifications (traps)<br />
generated by MXs supply data for the Client Monitor, RF Monitor, and RF Trends windows.<br />
Table 1– 1 lists the source of the data for each window in the Monitor button and for the Performance<br />
Statistics window.<br />
Table 1– 1. Sources of Monitor Data<br />
<strong>RingMaster</strong> Client Display Data Source Default<br />
Monitor — Status Summary Status monitoring of MXs by <strong>RingMaster</strong> Services Enabled<br />
Monitor — Clients Enable Client Session Collection option Enabled<br />
Monitor — Traffic Radio and Port statistics. Enabled<br />
Monitor — High Utilization,<br />
RF Interference, and<br />
Coverage Hole<br />
Enable Traffic & RF Trending option and configure RF<br />
Threshold Settings<br />
Enabled<br />
Alarms Input from all polls Enabled<br />
The monitoring options require SNMP traps to be enabled on the monitored MXs and also require<br />
<strong>RingMaster</strong> Services to be configured as a notification target (trap receiver) for each of the MXs.<br />
The data for some reports also requires monitoring options to be enabled. For information, see<br />
descriptions for each report in Chapter 7 “<strong>RingMaster</strong> Reports”.<br />
To change monitoring settings:<br />
Copyright © 2011, <strong>Juniper</strong> <strong>Networks</strong>, Inc. <strong>RingMaster</strong> Services 15