Minimizing Messaging Traffic

TED provides message notifications so that administrators and selected end users can be kept informed. Notifications can be sent in several ways:

• Information can be sent to log files
• Notifications can be sent via e-mail messages
• SNMP traps can be used and displayed on both local and remote consoles

Message Notification Levels

There are seven levels of messaging available, from no messages to be broadcast to a developer trace option. Regardless of the destination for a message, resources are directly affected by the level you choose. For information on setting message levels, see:

• Distributor object: Step 3

• Subscriber object: Step 3

The level you choose for a log file will affect the rate at which the log file grows. Because log files have no maximum size, you can control the size of a log file by choosing to delete entries after x number of days. For information on setting message levels, see:

• Distributor object: Step 2

• Subscriber object: Step 2

Sending Notifications Over LANs and WANs

The greatest impact on network traffic can come from the levels you choose for SNMP traps and for the remote console.

For information on setting message levels for SNMP traps, e-mail messages, and the server's console, see:

• Distributor object: Step 3

• Subscriber object: Step 3

SNMP Traps

SNMP messages are sent only if there is an SNMP policy in effect for the receiving server, regardless of the level you choose for the messages. SNMP traffic is affected by both the level you choose and by the SNMP configuration in the policy on the server. There is one SNMP packet per message per destination in the SNMP Trap Target policy. IPX^TM addresses are not supported for trap targets.

E-Mail Messages

E-mail messages can also affect network traffic. Like SNMP, e-mail will send only one e-mail per message per e-mail user defined. E-mail is also configured by a server policy. You must define and enable the policy on the sending server for e-mail messages to be sent.