System Administration Guide: IP Services

IPQoS Network Topologies

This section illustrates IPQoS strategies for various network needs.

IPQoS on Individual Hosts

The following figure shows a single network of IPQoS-enabled systems.

Figure 33–1 IPQoS Systems on a Network Segment

Topology diagram shows a local network with a Diffserv
router, and three IPQoS-enabled systems: FTP server, database server, and
a web server.

This network is but one segment of a corporate intranet. By enabling IPQoS on the application servers and web servers, you can control the rate at which each IPQoS system releases outgoing traffic. If you make the router Diffserv aware, you can further control incoming and outgoing traffic.

The examples in this guide use the “IPQoS on an individual host” scenario. For the example topology that is used throughout the guide, see Figure 33–4.

IPQoS on a Network of Server Farms

The following figure shows a network with several heterogeneous server farms.

Figure 33–2 Network of IPQoS-Enabled Server Farms

Topology diagram shows a network with a Diffserv router,
an IPQoS-enabled load balancer, and three server farms.

In such a topology, the router is Diffserv aware, and therefore able to queue and rate both incoming and outgoing traffic. The load balancer is also Diffserv-aware, and the server farms are IPQoS enabled. The load balancer can provide additional filtering beyond the router by using selectors such as user ID and project ID. These selectors are included in the application data.

This scenario provides flow control and traffic forwarding to manage congestion on the local network. This scenario also prevents outgoing traffic from the server farms from overloading other portions of the intranet.

IPQoS on a Firewall

The following figure shows a segment of a corporate network that is secured from other segments by a firewall.

Figure 33–3 Network Protected by an IPQoS-Enabled Firewall

Topology diagram shows a network consisting of a Diffserv
router, an IPQoS-enabled firewall, an Oracle Solaris system, and
other hosts.

In this scenario, traffic flows into a Diffserv-aware router where the packets are filtered and queued. All incoming traffic that is forwarded by the router then travels into the IPQoS-enabled firewall. To use IPQoS, the firewall must not bypass the IP forwarding stack.

The firewall's security policy determines whether incoming traffic is permitted to enter or depart the internal network. The QoS policy controls the service levels for incoming traffic that has passed the firewall. Depending on the QoS policy, outgoing traffic can also be marked with a forwarding behavior.