Table of Contents
Advertisement
2. Define the custom services that you need.
service mms tcp 1755
service smtp tcp 25
service pop3 tcp 110
The Microsoft Media Server (MMS) protocol can use several transports (UDP, TCP, and HTTP). However, for a SmartPath AP to be
able to map a service to a SmartPath QoS class, it must be able to identify that service by a unique characteristic such as a static
destination port number or a nonstandard protocol number. Unlike MMS/UDP and MMS/HTTP, both of which use a range of
destination ports, MMS/TCP uses the static destination Port 1755, which a SmartPath AP can use to map the service to a class.
Therefore, you define a custom service for MMS using TCP Port 1755. You also define custom services for SMTP and POP3 so that
you can map them to SmartPath Class 3. By doing so, you can prioritize e-mail traffic above other types of traffic that the
SmartPath AP assigns to Class 2 by default.
3. Map services to classes.
qos classifier-map service mms qos 5
qos classifier-map service smtp qos 3
qos classifier-map service pop3 qos 3
Unless you map a specific service to a QoS class, a SmartPath AP maps all traffic to Class 2. In this example, you prioritize voice,
media, and e-mail traffic by assigning them to higher QoS classes than Class 2, and then by defining the forwarding and weight-
ing mechanisms for each class (see Step 3).
Step 2: Create profiles to check traffic arriving at interfaces on SmartPath AP-1.
1. Define two classifier profiles for the traffic types "mac" and "service."
qos classifier-profile employee-voice mac
qos classifier-profile employee-voice service
qos classifier-profile eth0-voice mac
qos classifier-profile eth0-voice service
Classifier profiles define which components of incoming traffic SmartPath AP-1 checks. Because you specify "mac" and "service",
it checks the MAC address in the Ethernet frame header and the service type (by protocol number in the IP packet header and
port number in the transport packet header). If it detects traffic matching a classifier-map, it maps it to the appropriate class.
However, before this can happen, you must first associate the profiles with the interfaces that will be receiving the traffic that you
want checked. This you do with the next two commands.
2. Associate the classifier profiles with the employee SSID and the eth0 interface so that SmartPath AP-1 can classify incoming
traffic arriving at these two interfaces.
ssid employee qos-classifier employee-voice
interface eth0 qos-classifier eth0-voice
By creating two QoS classifiers and associating them with the employee SSID and eth0 interface, SmartPath AP-1 can classify
traffic flowing in both directions for subsequent QoS processing; that is, it can classify traffic flowing from the wireless LAN to the
wired LAN, and from the wired LAN to the wireless LAN.
NOTE: If the surrounding network uses the IEEE 802.1p QoS classification system (for wired network traffic) or 802.11e (for
wireless network traffic), you can ensure that SmartPath AP-1 checks for them by entering these commands:
qos classifier-profile eth0-voice 8021p
qos classifier-profile employee-voice 80211e
724-746-5500 | blackbox.com
Chapter 11: Deployment Examples CLI
Page 151
Advertisement
Chapters
Table of Contents
