Input qos on ingress to the diffserv domain policy – Enterasys Networks Security Router X-PeditionTM User Manual
Page 311

QoS Policy Configuration Examples
XSR User’s Guide 12-29
XSR(config)#interface multilink 1
XSR(config-if
XSR(config-if
XSR(config)#interface fastethernet 1
XSR(config-if
Input QoS on Ingress to the Diffserv Domain Policy
If the XSR is positioned on the edge of the diffserv (DS) domain, it must perform edge traffic
conditioning required by the diffserv domain for traffic entering from outside the domain. Traffic
conditioning on input QoS include marking and policing.
In the following example, the Ethernet interface is situated outside the DS domain. All other XSR
interfaces belong to the DS domain. Incoming traffic is classified in three flows: RTP traffic which
is marked with the EF code point, traffic flow for destination 10.10.10.0 which is policed to 10
Mbps, and FTP traffic which is policed to 5Mbps with conforming traffic marked with AF=21 and
exceeding traffic marked with AF=23. All other traffic is marked with DSCP=0 and policed to 10
Mbps.
XSR(config)#class-map RTP
XSR(config-cmap
XSR(config-cmap
XSR(config)#class-map Dest10
XSR(config-cmap
XSR(config-cmap
XSR(config)#class-map FTP
XSR(config-cmap
XSR(config-cmap
XSR(config)#access-list 110 permit udp any any eq 3020
XSR(config)#access-list 112 permit tcp any 10.10.10.0 0.0.0.255
XSR(config)#access-list 113 permit tcp any any range 20 21
XSR(config)#policy-map Eht
XSR(config-pmap
XSR(config-pmap-c
XSR(config-pmap-c
XSR(config-pmap
XSR(config-pmap-c
XSR(config-pmap-c
XSR(config-pmap
XSR(config-pmap-c
exceed-action set-dscp-transmit 23
XSR(config-pmap-c
XSR(config-pmap
XSR(config-pmap-c
XSR(config-pmap-c
XSR(config-pmap-c
XSR(config-pmap