ZyXEL Communications NXC5200 User Manual page 268

Chapter 19 Application Patrol
Connection and Packet Directions
Application patrol looks at the connection direction, that is from which zone the
connection was initiated and to which zone the connection is going.
A connection has outbound and inbound packet flows. The NXC controls the
bandwidth of traffic of each flow as it is going out through an interface.
• The outbound traffic flows from the connection initiator to the connection
responder.
• The inbound traffic flows from the connection responder to the connection
initiator.
Outbound and Inbound Bandwidth Limits
You can limit an application's outbound or inbound bandwidth. This limit keeps the
traffic from using up too much of the out-going interface's bandwidth. This way
you can make sure there is bandwidth for other applications. When you apply a
bandwidth limit to outbound or inbound traffic, each member of the out-going
zone can send up to the limit. Take a LAN to WLAN policy for example.
• Outbound traffic is limited to 200 kbps. The connection initiator is on the LAN so
outbound means the traffic traveling from the LAN to the WLAN. Each of the
WLAN zone's two interfaces can send the limit of 200 kbps of traffic.
• Inbound traffic is limited to 500 kbs. The connection initiator is on the LAN so
inbound means the traffic traveling from the WLAN to the LAN.
Figure 117 LAN to WLAN, Outbound 200 kbps, Inbound 500 kbps
Inbound
500 kbps
Bandwidth Management Priority
• The NXC gives bandwidth to higher-priority traffic first, until it reaches its
configured bandwidth rate.
• Then lower-priority traffic gets bandwidth.
• The NXC uses a fairness-based (round-robin) scheduler to divide bandwidth
among traffic flows with the same priority.
• The NXC automatically treats traffic with bandwidth management disabled as
priority 7 (the lowest priority).
268
Outbound
Outbound
200 kbps
200 kbps
NXC5200 User's Guide