Quality Of Service - Edge-Core ES3628C Management Manual

24 10/100 ports + 4ge intelligent layer 2/3/4 fast ethernet switch
Table of Contents

Advertisement

CLI – The following example globally enables IP Port Priority service on the switch,
maps HTTP traffic (on port 1) to CoS value 0, and then displays the IP Port Priority
settings.
Console(config)#map ip port
Console(config)#interface ethernet 1/1
Console(config-if)#map ip port 80 cos 0
Console(config-if)#end
Console#show map ip port ethernet 1/5
TCP port mapping status: disabled
Port
Port no. COS
--------- -------- ---
Eth 1/ 1
Console#
*
Mapping specific values for IP Port Priority is implemented as an interface configuration
command, but any changes will apply to the all interfaces on the switch.

Quality of Service

The commands described in this section are used to configure Quality of Service
(QoS) classification criteria and service policies. Differentiated Services (DiffServ)
provides policy-based management mechanisms used for prioritizing network
resources to meet the requirements of specific traffic types on a per hop basis.
Each packet is classified upon entry into the network based on access lists, IP
Precedence, DSCP values, or VLAN lists. Using access lists allows you select traffic
based on Layer 2, Layer 3, or Layer 4 information contained in each packet. Based
on configured network policies, different kinds of traffic can be marked for different
kinds of forwarding.
All switches or routers that access the Internet rely on class information to provide
the same forwarding treatment to packets in the same class. Class information can
be assigned by end hosts, or switches or routers along the path. Priority can then be
assigned based on a general policy, or a detailed examination of the packet.
However, note that detailed examination of packets should take place close to the
network edge so that core switches and routers are not overloaded.
Switches and routers along the path can use class information to prioritize the
resources allocated to different traffic classes. The manner in which an individual
device handles traffic in the DiffServ architecture is called per-hop behavior. All
devices along a path should be configured in a consistent manner to construct a
consistent end-to-end QoS solution.
Notes: 1.
You can only configure one rule per Class Map. However, you can include
multiple classes in a Policy Map.
2.
You must create a Class Map before creating a Policy Map.
80
0
3
Quality of Service
4-212
4-143
4-212
4-216
3-161

Advertisement

Table of Contents
loading

Table of Contents