MSS traffic reports serve several purposes, including how to:
- Determine if your messaging system is performing at peak efficiency
by providing actual usage information that you can compare with
the type of usage that was initially forecast for your system.
- Troubleshoot administration problems that can occur with subscribers
and equipment as system usage increases and requirements change.
This topic provides the following information about MSS traffic reports:
Archiving traffic reports
If you print messaging traffic reports on a regular basis and
file them sequentially by date, they can provide an ongoing audit
and historical reference of your messaging system. These reports
can be useful for analyzing trends and tracking system performance
over a period of time. Since traffic records collected for a specific
day, hour, or month are retained on the system only for a limited
number of days, hours, or months, it is imperative that you run
and print the reports on a regular schedule to ensure that you maintain
a complete record from one reporting period to the next. See Data
retention requirements for more information about how long the
system retains traffic records.
Interpreting traffic reports
You can use the traffic report data to spot potential problems with your system and to troubleshoot system threshold problems that can occur with subscribers
and equipment as system usage increases and requirements change:
- Spotting potential system problems: The Feature Daily and Feature Hourly Traffic reports provide statistical information that is useful for spotting potential problems and for evaluating how the messaging system is used:
- Number of remote subscribers administered on the system
- Number of login attempts
- Number of voice mail, call answer, broadcast, login announcement, urgent, and private messages sent
- Average storage time of voice mail and call answer calls
- Types of messages, including voice, text, and fax components and binary attachments
- Identifying system threshold problems: Threshold exceptions indicate that subscribers tried to use more message or list space than is available, and that warnings were issued. These exceptions can be the first indication that you need to change settings administered on the system:
- If you notice a large number of threshold exceptions for lists, it might indicate that you need to adjust the maximum number of lists allowed per subscriber. You can increase the number of lists assigned to each subscriber. You can also ask subscribers to delete old or unnecessary lists.
- If you notice that the upper and lower limits for message space are consistently exceeded, you can increase the mailbox size for an individual subscriber by modifying the subscriber's class-of-service. You can also decrease the Message Retention Time on the class-of-service page. Decreasing the Message Retention Time limits the length of time that the system retains messages within subscribers' mailboxes, resulting in more frequent deletion of old messages.
Types of traffic reports
Each application on the messaging system provides its own set
of reports for tracking data relevant and specific to the application
itself. The following table describes each traffic report.
To see more information about a specific report, click the link
in the Procedure Link column.
Report |
Description |
Procedure Link |
Messaging |
Community Traffic (Hourly/Daily) |
Displays the number of messages sent and received by each
community for the specified days or hours. If you use the Sending Restrictions feature to define the communities to which and from which mail can be sent and received, these reports also show the number of messages that were not sent or received for each community. |
Running a Community Daily or Hourly
Traffic Report |
Feature Traffic (Hourly/Daily) |
Displays traffic information by feature for the specified days or hours. The features are: remote subscribers, voice mail ( including fax, binary attachments, text components, broadcast, urgent, and private messages), and call
answer messages. |
Running a Feature Daily or Hourly
Traffic Report |
Load Traffic (Hourly/Daily) |
Displays the number of subscriber warnings issued for crossing pre-defined thresholds and system storage information for the specified days or hours. |
Running a Load Daily or Hourly Traffic
Report |
Subscriber Traffic (Daily/Monthly) |
Displays traffic information about a specific subscriber for the specified days or months.
|
Running a Subscriber Daily or Monthly
Traffic Report |
Networking |
Network Load Traffic
(Hourly/Daily) |
Displays network traffic information for the specified days or hours including network usage in seconds and number of incoming and outgoing messages and LDAP updates. |
Running a Network Load Hourly or
Daily Traffic Report |
Remote Messages Traffic
(Monthly/Daily) |
Displays up to 13 months' worth of information about the traffic
load between a local messaging machine and a specified remote messaging
machine. |
Running a Remote Message Daily or
Monthly Traffic Report |
MSS traffic reports use a command-based interface. For more information, see Using the MSS traffic report interface.
Top of page
|