. . . . .
Monitoring QoS Policy
359
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MONITORING QOS POLICY
The QoS Policy and its impact on traffic can be monitored using SmartView
Tracker, Eventia Reporter, and SmartView Monitor. Each SmartConsole tool
provides a rich set of data, to evaluate the effectiveness of the QoS Policy.
SmartView Tracker
The following two conditions must be met, for a match on a QoS Policy rule to
be logged:
• The QoS logging box must be checked on the Gateway Properties >
Additional Logging Configuration screen.
• The connection’s matching rule must be marked with either Log or Account,
in the rule’s track field.
QOS TRACK FIELD SET TO LOG
QoS rules with the track field set to Log can generate the following types of log
events:
• Connection Rejection
QoS rejects a connection when the number of guaranteed connections is
exceeded, and/or when the rule’s action properties are not set to accept
additional connections.
• Running Out of Packet Buffers
QoS generates an Out of Packet Buffers string when QoS global packet
buffers are exhausted, or one of the interface direction’s packet buffers is
exhausted. This report is generated no more frequently than once every 12
hours.
• LLQ Packet Drop
When a packet is dropped from an LLQ connection, a report is generated.
This report is generated no more frequently than once every 5 minutes.
