| Oracle® Enterprise Manager Oracle Collaboration Suite Metric Reference Manual 10g Release 2 (10.2) Part Number B25985-01 |
|
|
View PDF |
| Oracle® Enterprise Manager Oracle Collaboration Suite Metric Reference Manual 10g Release 2 (10.2) Part Number B25985-01 |
|
|
View PDF |
The NNTP Outbound Server propagates feed messages to other NNTP peer servers. Messages are propagated based on the server Outbound Feed settings. Messages being propagated will be queued in the Newsfeed Queue by the NNTP Inbound Server at the time the message is received.
This category includes metrics pertaining to news messages leaving the Oracle Email system.
This metric indicates the rate of errors in the news feed. Errors include network outages, misconfigured peer details, host connection failures, and so on. This rate should ideally be zero or very low.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Evaluation and Collection Frequency |
|---|---|
| All Versions | Every 10 minutes |
User Action
Sustained high values for this metric usually indicate that there are problems with the quality of network connections between the Oracle Email system and the news peer servers. For example, a slow network is causing the peer to timeout and close connections. Check the following:
Check to see if sufficient network resources are available and that peer servers are functioning normally.
Check the NNTP Outbound Server log files to see what kind of errors, if any, have been noted by the server. Use esd_logscan.pl to scan the server log files.
This metric indicates the rate at which news messages are being fed to all NNTP peer servers configured to receive feed.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Evaluation and Collection Frequency |
|---|---|
| All Versions | Every 10 minutes |
User Action
This metric must be interpreted in conjunction with the Newsfeed Queue metric of the Oracle Collaboration Suite Database (mailstore) target. If the List Queue is also empty or near empty, this is an indication that there are very few messages being fed to peers and this is normal. If the Newsfeed Queue is long but the Message processing rate is low, then users will experience delays in receiving responses to messages posted to newsgroups. Check the following:
First, use the monitoring tools available on your operating system (for example, sar, and top) to verify there are sufficient operating system resources.
Next, check to see if the network connection between your system and peer servers are congested.
If operating system resources are available and the network is not congested, check the NNTP Outbound Server log files for any errors in accessing the Oracle directory server and/or the Oracle Collaboration Suite Database. Use esd_logscan.pl to scan the server log files.
This metric indicates the number of messages that were offered to a peer, but were refused because the peer had already received it from another server. It is normal for this metric to be non-zero. Sustained high values could mean that the remote peers are receiving feeds from other servers and probably are not required to be fed from the Oracle Email system.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Evaluation and Collection Frequency |
|---|---|
| All Versions | Every 10 minutes |
User Action
Message refusal is not considered an error and merely indicates that the peer already has the message or does not want it for some reason, such as spam check failures. Sustained high values for this metric indicate that peer servers are receiving news messages from other news server before the Oracle Email system can propagate them. This is applicable only to messages that are passing through the system.
This category contains metrics related to NNTP Outbound Server resource usage.
This metric details the efficiency with which network connections are opened to peer servers. For systems with high Message Transfer Rates, this metric should be close to 1. Low values for this metric do not necessarily indicate a problem.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Evaluation and Collection Frequency |
|---|---|
| All Versions | Every 10 minutes |
User Action
This metric can be used to tune the connection cache parameter of the NNTP Outbound Server. Adjust the number of connections in the cache and the timeout value of the connections so that this metric is always close to 1.0. However, if the outbound feed traffic is very low in your system, as indicated by the Message Transmission Rate, it is usually more efficient to keep this metric at zero by setting the number of cached connections to zero.
This category contains metrics that provide information about the Up/Down status of the NNTP Outbound Server.
This metric provides information about the Up/Down status of the NNTP Outbound Server and alerts you when the status is down. The NNTP Outbound Server shows a status of Down when all processes on the host are down.
Metric Summary
The following table shows how often the metric's value is collected and compared against the default thresholds. The Consecutive Number of Occurrences Preceding Notification column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 52-1 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold' | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 5 Minutes |
After Every Sample |
= |
Not Defined |
0 |
1 |
Failed to connect to NNTP server |
User Action
You can restart the NNTP Outbound Server by selecting the target and clicking the Restart button on the Email Application home page. To investigate why the service is down, check for alerts that may have been generated. If the NNTP Outbound Server does not restart, the likely cause is that the server cannot connect to at least one of the Oracle Collaboration Suite Databases (mailstores) or to the Oracle directory server.
