Red Hat NETWORK 3.6 Reference Manual

Also see for NETWORK 3.6 -: Manual Configuration guide

Contents

Red Hat NETWORK 3.6 Reference Manual Manual pdf 171 page image

Appendix C. Probes 159This probe supports authentication. Provide a username and password in the appropriate fields to usethis feature. Also, the optional Virtual Host field can be used to monitor a separate documentationset located on the same physical machine presented as a standalone server. If your Web server is notconfigured to use virtual hosts (which is typically the case), you should leave this field blank. If youdo have virtual hosts configured, enter the domain name of the first host here. Add as many probes asnecessary to monitor all virtual hosts on the machine.Field ValueURL Path /Virtual HostExpect Header HTTP/1Expect ContentUserAgent* NOCpulse-check_http/1.0UsernamePasswordTimeout* 10HTTP Port* 80Critical Maximum Remote Service LatencyWarning Maximum Remote Service LatencyTable C-47. Network Services::Web Server (HTTP) settingsC.9. Oracle 8i and 9iThe probes in this section may be applied to instances of the Oracle database matching the versionssupported. Oracle probes require the configuration of the database and associations made by run-ning: $ORACLE_HOME/rdbms/admin/catalog.sql In addition, for these probes to function prop-erly, the Oracle user configured in the probe must have minimum privileges of CONNECT and SE-LECT_CATALOG_ROLE.Some Oracle probes are specifically aimed at tuning devices for long-term performance gains, ratherthan avoiding outages. Therefore, Red Hat recommends scheduling them to occur less frequently,between every hour and every two days. This will provide a better statistical representation than everyfew minutes while de-emphasizing anomalies that can occur. This applies to following probes: BufferCache, Data Dictionary Cache, Disk Sort Ratio, Library Cache, and Redo Log.For CRITICAL and WARNING thresholds based upon time to work as intended, their values cannotexceed the amount of time allotted to the timeout period. Otherwise, an UNKNOWN status will bereturned in all cases of extended latency, thereby nullifying the thresholds. For this reason, Red Hatstrongly recommends ensuring timeout periods exceed all timed thresholds. In this section, this refersspecifically to the probe TNS Ping.Finally, customers using these Oracle probes against a database using Oracle’s Multi-Threaded Server(MTS) will need to contact Red Hat support to have entries added to the RHN Server’s /etc/hosts fileto ensure the DNS name is resolved correctly.