In this example, the RCL enterprise network administrator used NBAR and determined that the major sources of network traffic are from the following applications:
■ Structured Query Language (SQL)
The RCL senior management team has determined that only SQL and HTTP traffic are mission-critical to the company.
RCL has decided to implement four traffic classes as follows:
■ A real-time traffic class for VoIP traffic—all RTP traffic
■ A mission-critical data traffic class for mission-critical traffic—SQL and HTTP traffic
■ A bulk traffic class for business traffic that is not mission-critical—FTP, DNS, Exchange
■ A best-effort traffic class for all best-effort traffic—Napster and all other traffic
The RCL network administrator has decided not to implement a scavenger traffic class to limit the Napster traffic at this time, but is constantly monitoring the Napster traffic. In the future, if more bandwidth is required for the business-related applications, a scavenger traffic class will be added and the Napster traffic will be classified into this scavenger traffic class.
This topic describes typical enterprise traffic classes and the delay, jitter, packet-loss, and bandwidth requirements of each enterprise traffic class.
The table summarizes the key QoS requirements (bandwidth, packet loss, delay, and jitter) for some of the major different categories of applications.
Was this article helpful?