Web Management Guide-R04
Table Of Contents
- How to Use This Guide
- Contents
- Figures
- Tables
- Getting Started
- Web Configuration
- Using the Web Interface
- Basic Management Tasks
- Displaying System Information
- Displaying Hardware/Software Versions
- Configuring Support for Jumbo Frames
- Displaying Bridge Extension Capabilities
- Managing System Files
- Setting the System Clock
- Configuring the Console Port
- Configuring Telnet Settings
- Displaying CPU Utilization
- Configuring CPU Guard
- Displaying Memory Utilization
- Resetting the System
- Interface Configuration
- VLAN Configuration
- Address Table Settings
- Spanning Tree Algorithm
- Congestion Control
- Class of Service
- Layer 2 Queue Settings
- Layer 3/4 Priority Settings
- Setting Priority Processing to IP Precedence/DSCP or CoS
- Mapping Ingress DSCP Values to Internal DSCP Values
- Mapping CoS Priorities to Internal DSCP Values
- Mapping Internal DSCP Values to Egress CoS Values
- Mapping IP Precedence Values to Internal DSCP Values
- Mapping IP Port Priority to Internal DSCP Values
- Quality of Service
- VoIP Traffic Configuration
- Security Measures
- AAA Authentication, Authorization and Accounting
- Configuring User Accounts
- Web Authentication
- Network Access (MAC Address Authentication)
- Configuring HTTPS
- Configuring the Secure Shell
- Access Control Lists
- Filtering IP Addresses for Management Access
- Configuring Port Security
- Configuring 802.1X Port Authentication
- DoS Protection
- DHCPv4 Snooping
- DHCPv6 Snooping
- IPv4 Source Guard
- IPv6 Source Guard
- ARP Inspection
- Application Filter
- Basic Administration Protocols
- Configuring Event Logging
- Link Layer Discovery Protocol
- Simple Network Management Protocol
- Configuring Global Settings for SNMP
- Setting Community Access Strings
- Setting the Local Engine ID
- Specifying a Remote Engine ID
- Setting SNMPv3 Views
- Configuring SNMPv3 Groups
- Configuring Local SNMPv3 Users
- Configuring Remote SNMPv3 Users
- Specifying Trap Managers
- Creating SNMP Notification Logs
- Showing SNMP Statistics
- Remote Monitoring
- Switch Clustering
- Setting a Time Range
- Ethernet Ring Protection Switching
- OAM Configuration
- Connectivity Fault Management
- Configuring Global Settings for CFM
- Configuring Interfaces for CFM
- Configuring CFM Maintenance Domains
- Configuring CFM Maintenance Associations
- Configuring Maintenance End Points
- Configuring Remote Maintenance End Points
- Transmitting Link Trace Messages
- Transmitting Loop Back Messages
- Transmitting Delay-Measure Requests
- Displaying Local MEPs
- Displaying Details for Local MEPs
- Displaying Local MIPs
- Displaying Remote MEPs
- Displaying Details for Remote MEPs
- Displaying the Link Trace Cache
- Displaying Fault Notification Settings
- Displaying Continuity Check Errors
- OAM Configuration
- UDLD Configuration
- LBD Configuration
- Smart Pair Configuration
- Multicast Filtering
- Overview
- Layer 2 IGMP (Snooping and Query for IPv4)
- Configuring IGMP Snooping and Query Parameters
- Specifying Static Interfaces for a Multicast Router
- Assigning Interfaces to Multicast Services
- Setting IGMP Snooping Status per Interface
- Filtering IGMP Query Packets and Multicast Data
- Displaying Multicast Groups Discovered by IGMP Snooping
- Displaying IGMP Snooping Statistics
- Filtering and Throttling IGMP Groups
- MLD Snooping (Snooping and Query for IPv6)
- Multicast VLAN Registration for IPv4
- Multicast VLAN Registration for IPv6
- Basic IP Functions
- IP Configuration
- General IP Routing
- IP Services
- Appendices
- Glossary
Chapter 10
| Quality of Service
Creating QoS Policies
– 274 –
Creating QoS Policies
Use the Traffic > DiffServ (Configure Policy) page to create a policy map that can be
attached to multiple interfaces. A policy map is used to group one or more class
map statements (page 270), modify service tagging, and enforce bandwidth
policing. A policy map can then be bound by a service policy to one or more
interfaces (page 284).
Configuring QoS policies requires several steps. A class map must first be
configured which indicates how to match the inbound packets according to an
access list, a DSCP or IP Precedence value, or a member of specific VLAN. A policy
map is then configured which indicates the boundary parameters used for
monitoring inbound traffic, and the action to take for conforming and non-
conforming traffic. A policy map may contain one or more classes based on
previously defined class maps.
The class of service or per-hop behavior (i.e., the priority used for internal queue
processing) can be assigned to matching packets. In addition, the flow rate of
inbound traffic can be monitored and the response to conforming and non-
conforming traffic based by one of three distinct policing methods as described
below.
Police Flow Meter – Defines the committed information rate (maximum
throughput), committed burst size (burst rate), and the action to take for
conforming and non-conforming traffic.
Policing is based on a token bucket, where bucket depth (that is, the maximum
burst before the bucket overflows) is specified by the “burst” field (BC), and the
average rate tokens are removed from the bucket is specified by the “rate” option
(CIR). Action may be taken for traffic conforming to the maximum throughput, or
exceeding the maximum throughput.
srTCM Police Meter – Defines an enforcer for classified traffic based on a single rate
three color meter scheme defined in RFC 2697. This metering policy monitors a
traffic stream and processes its packets according to the committed information
rate (CIR, or maximum throughput), committed burst size (BC, or burst rate), and
excess burst size (BE). Action may taken for traffic conforming to the maximum
throughput, exceeding the maximum throughput, or exceeding the excess burst
size.
◆ The PHB label is composed of five bits, three bits for per-hop behavior, and two
bits for the color scheme used to control queue congestion. In addition to the
actions defined by this command to transmit, remark the DSCP service value, or
drop a packet, the switch will also mark the two color bits used to set the drop
precedence of a packet. A packet is marked green if it doesn't exceed the
committed information rate and committed burst size, yellow if it does exceed
the committed information rate and committed burst size, but not the excess
burst size, and red otherwise.