Downloads |
 Feedback
|
Table Of Contents
Using OER to Profile the Traffic Classes
Prerequisites for Using OER to Profile the Traffic Classes
Restrictions for Using OER to Profile the Traffic Classes
Information About Using OER to Profile the Traffic Classes
OER Automatic Traffic Class Learning
Prefix Traffic Class Learning Using OER
Application Traffic Class Learning Using OER
OER Manual Traffic Class Configuration
Prefix Traffic Class Configuration Using OER
Application Traffic Class Configuration Using OER
How to Configure OER to Profile the Traffic Classes
Configuring OER to Automatically Learn Prefix-Based Traffic Classes
Configuring OER to Automatically Learn Traffic Classes Using Inside Prefixes
Configuring OER to Automatically Learn Prefix-Based Traffic Classes Using Protocol or Port Number
Specifying the Flow Keys for Automatic Learning of Application Traffic Classes
Creating an Access List to Specify a Filter for Automatically Learned Application Traffic
Displaying Application Traffic Flow Information on a Border Router
Manually Selecting Prefixes for OER Monitoring
OER Map Operation for the OER Profile Phase
Manually Selecting Inside Prefixes for OER Monitoring
OER Map Operation for Inside Prefixes
Manually Selecting Traffic Classes Using Prefix, Protocol, Port, and DSCP Value
Configuration Examples for Using OER to Profile the Traffic Classes
Configuring OER to Automatically Learn Prefix-Based Traffic Classes: Example
Configuring OER to Automatically Learn Traffic Classes Using Inside Prefixes: Example
Manually Selecting Prefixes for OER Monitoring: Example
Manually Selecting Inside Prefixes for OER Monitoring: Example
Manually Selecting Traffic Classes Using Prefix, Protocol, Port, and DSCP Value: Example
Feature Information for Using OER to Profile the Traffic Classes
Using OER to Profile the Traffic Classes
First Published: January 29, 2007Last Updated: November 20, 2009This module describes how Optimized Edge Routing (OER) profiles the traffic classes. To optimize traffic routing, subsets of the total traffic must be identified, and these traffic subsets are named traffic classes. The OER master controller can profile traffic classes either by manual configuration on the master controller, or by automatic learning on the basis of parameters such as throughput or delay characteristics of traffic on the border routers. Automatic learning requires traffic class parameters to be configured on the master controller.
Note
If you are running Cisco IOS Release 12.4(15)T or a later release, please refer to the "Using Performance Routing to Profile the Traffic Classes" module for the latest configuration information and tasks introduced for Performance Routing. Performance Routing (PfR) is an extension of the Optimized Edge Routing (OER) technology and the commands and command modes for PfR use the oer naming convention.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Using OER to Profile the Traffic Classes" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
•
•
•
•
•
Prerequisites for Using OER to Profile the Traffic Classes
•
•
Restrictions for Using OER to Profile the Traffic Classes
If any of the border routers is a Cisco Catalyst 6500 switch or a Cisco 7600 series router, there are some hardware constraints and the master controller will set the monitoring mode to special where only the throughput method of learning is used to profile the traffic classes. If both delay and throughput are configured, the master controller will ignore the delay configuration. For more details about the special monitoring mode, see the "Measuring the Traffic Class Performance and Link Utilization Using OER" module for more details.
Information About Using OER to Profile the Traffic Classes
To configure the master controller to profile traffic classes, you should understand the following concepts:
•
•
OER Traffic Class Profiling
Before optimizing traffic, OER has to determine the traffic classes from the traffic flowing through the border routers. To optimize traffic routing, subsets of the total traffic must be identified, and these traffic subsets are named traffic classes. The list of traffic classes entries is named a Monitored Traffic Class (MTC) list. The entries in the MTC list can be profiled either by automatically learning the traffic flowing through the device or by manually configuring the traffic classes. Learned and configured traffic classes can both exist in the MTC list at the same time. The OER profile phase includes both the learn mechanism and the configure mechanism. The overall structure of the OER traffic class profile process and its component parts can be seen in Figure 1.
Figure 1 OER Traffic Class Profiling Process
The ultimate objective of this phase is to select a subset of traffic flowing through the network. This subset of traffic—the traffic classes in the MTC list—represents the classes of traffic that need to be routed based on the best performance path available.
More details about each of the components in Figure 1 are contained in the following concepts:
•
•
OER Automatic Traffic Class Learning
OER can automatically learn the traffic classes while monitoring the traffic flow through border routers. Although the goal is to optimize a subset of the traffic, you may not know all the exact parameters of this traffic and OER provides a method to automatically learn the traffic and create traffic classes by populating the MTC list. Several features have been added to OER since the original release to add functionality to the automatic traffic class learning process.
Within the automatic traffic class learning process there are now three components. One component describes the automatic learning of prefix-based traffic classes, the second component describes automatic learning of application-based traffic classes, and the third component describes the use of learn lists to categorize both prefix-based and application-based traffic classes. These three components are described in the following sections:
•
•
•
Prefix Traffic Class Learning Using OER
The OER master controller can be configured, using NetFlow Top Talker functionality, to automatically learn prefixes based on the highest outbound throughput or the highest delay time. Throughput learning measures prefixes that generate the highest outbound traffic volume. Throughput prefixes are sorted from highest to lowest. Delay learning measures prefixes with the highest round-trip response time (RTT) to optimize these highest delay prefixes to try to reduce the RTT for these prefixes. Delay prefixes are sorted from the highest to the lowest delay time.
OER can automatically learn two types of prefixes:
•
•
In Cisco IOS Release 12.4(9)T, 12.2(33)SRB, and later releases, the ability to learn inside prefixes was introduced. Using BGP, OER can select inside prefixes to support best entrance selection for traffic that originates from prefixes outside an autonomous system destined for prefixes inside the autonomous system. In prior releases, only outside prefixes were supported. Company networks advertise the inside prefixes over the Internet using an Internet service provider (ISP) and receive advertisements for outside prefixes from an ISP.
Note
Automatic prefix learning is configured in OER Top Talker and Top Delay learning configuration mode. The learn command is used to enter this mode from OER master controller configuration mode. When automatic prefix learning is enabled, prefixes and their delay or throughput characteristics are measured on the border routers. Performance measurements for the prefix-based traffic classes are reported to the master controller where the learned prefixes are stored in the MTC list.
Prefixes are learned on the border routers through monitoring the traffic flow using the embedded NetFlow capability. All incoming and outgoing traffic flows are monitored. The top 100 flows are learned by default, but the master controller can be configured to learn up to 2500 flows for each learn cycle. In Cisco IOS Release 12.4(20)T, 12.2(33)SRE, and later releases, the limit of 5000 prefixes that can be controlled by a master controller was removed. In Cisco IOS Release 12.4(15)T, 12.2(33)SRB, 12.2(33)SXH, and earlier releases, the master controller can control a maximum of 5000 prefixes.
The master controller can be configured to aggregate learned prefixes based on type, BGP or non-BGP (static). Prefixes can be aggregated based on the prefix length. Traffic flows are aggregated using a /24 prefix length by default. Prefix aggregation can be configured to include any subset or superset of the network, from single host route (/32) to a major network address range. For each aggregated prefix, up to five host addresses are selected to use as active probe targets. Prefix aggregation is configured with the aggregation-type command in OER Top Talker and Delay learning configuration mode.
Application Traffic Class Learning Using OER
In the first release of OER, Cisco IOS Release 12.3(8)T, only Layer 3 prefixes could be learned. In subsequent releases, Layer 4 options such as protocol or port numbers were added as filters to the prefix-based traffic class. The protocol and port numbers can be used to identify specific application traffic classes; protocol and port number parameters are monitored only within the context of a prefix and are not sent to the master controller database (MTC list). The prefix that carries the specific traffic is then monitored by the master controller. In Cisco IOS Release 12.4(9)T, Release 12.2(33)SRB, and later releases, application traffic class learning supports Differentiated Services Code Point (DSCP) values in addition to protocol and port numbers, and these Layer 4 options are entered in the MTC list.
Port and Protocol Based Prefix Learning by OER
In Cisco IOS Release 12.3(11)T, Release 12.2(33)SRB, and later releases, prefix learning on the basis of port numbers or protocols was introduced. This feature allows you to configure the master controller to filter the prefix-based traffic class based on the protocol number or the source or destination port number, carried by TCP or UDP traffic. This feature provides a very granular filter that can be used to further optimize prefixes learned based on throughput and delay. The traffic classes sent to the MTC list on the master controller, however, only contain the prefix information, not the protocol and port numbers.
Port and protocol based prefix learning allows you to optimize or exclude traffic streams for a specific protocol or the TCP port, UDP port, or range of port numbers. Traffic can be optimized for a specific application or protocol. Uninteresting traffic can be excluded, allowing you to focus router system resources, and reduce unnecessary CPU and memory utilization. In cases where traffic streams need to be excluded or included over ports that fall above or below a certain port number, the range of port numbers can be specified. Port and protocol prefix based learning is configured with the protocol command in OER Top Talker and Top Delay learning configuration mode.
For a list of IANA assigned port numbers, see the following document:
•
For a list of IANA assigned protocol numbers, see the following document:
•
DSCP Value, Port, and Protocol Learning by OER
In Cisco IOS Release 12.4(9)T, 12.2(33)SRB, and later releases, the ability to filter and aggregate application traffic by DSCP value, port number or protocol was introduced. Traffic classes can be defined by a combination of keys comprising of protocol, port numbers, and DSCP values. The ability to filter out traffic that is not required, and the ability to aggregate the traffic in which you are interested, was introduced. Information such as protocol, port number, and DSCP value is now sent to the master controller database in addition to the prefix information. The new functionality allows OER to both actively and passively monitor application traffic. Using new CLI and access lists, OER can be configured to automatically learn application traffic classes.
Learn List Configuration Mode
In Cisco IOS Release 12.4(15)T, a new configuration mode named learn list was introduced. Learn lists are a way to categorize learned traffic classes. In each learn list, different criteria including prefixes, application definitions, filters, and aggregation parameters for learning traffic classes can be configured.
If you are running Cisco IOS Release 12.4(15)T or a later release, please refer to the "Using Performance Routing to Profile the Traffic Classes" module for learn list configuration information and tasks introduced for Performance Routing. Performance Routing (PfR) is an extension of the Optimized Edge Routing (OER) technology and the commands and command modes for PfR use the oer naming convention.
OER Manual Traffic Class Configuration
OER can be manually configured to create traffic classes for monitoring and subsequent optimizing. Automatic learning generally uses a default prefix length of /24 but manual configuration allows exact prefixes to be defined. Within the manual traffic class configuration process there are two components— manually configuring prefix-based traffic classes and manually configuring application-based traffic classes, both of which are described in the following sections:
•
•
Prefix Traffic Class Configuration Using OER
A prefix or range of prefixes can be selected for OER monitoring by configuring an IP prefix list. The IP prefix list is then imported into the MTC list by configuring a match clause in an OER map. An OER map is similar to an IP route map. IP prefix lists are configured with the ip prefix-list command and OER maps are configured with the oer-map command in global configuration mode.
The prefix list syntax operates in a slightly different way with OER than in regular routing. The ge keyword is not used and the le keyword is used by OER to specify only an inclusive prefix. A prefix list can also be used to specify an exact prefix.
A master controller can monitor and control an exact prefix of any length including the default route. If an exact prefix is specified, OER monitors only the exact prefix.
A master controller can monitor and control an inclusive prefix using the le keyword and the le-value argument set to 32. OER monitors the configured prefix and any more specific prefixes (for example, configuring the 10.0.0.0/8 le 32 prefix would include the 10.1.0.0/16 and the 10.1.1.0/24 prefixes) over the same exit and records the information in the routing information base (RIB).
Note
An IP prefix list with a deny statement can be used to configure the master controller to exclude a prefix or prefix length for learned traffic classes. Deny prefix list sequences should be applied in the lowest OER map sequences for best performance. In Cisco IOS Release 12.4(9)T, 12.2(33)SRB, and later releases, the master controller can be configured to tell border routers to filter out uninteresting traffic using an access list.
Note
Two types of prefix can be manually configured for OER monitoring using an IP prefix list:
•
•
In Cisco IOS Release 12.4(9)T, 12.2(33)SRB, and later releases, the ability to manually configure inside prefixes was introduced. Using BGP, OER can be configured to select inside prefixes to support best entrance selection for traffic that originates from prefixes outside an autonomous system destined for prefixes inside the autonomous system. In prior releases, only outside prefixes were supported. Company networks advertise the inside prefixes over the Internet using an Internet service provider (ISP) and receive advertisements for outside prefixes from an ISP.
Note
Application Traffic Class Configuration Using OER
In the first release of OER, Cisco IOS Release 12.3(8)T, only Layer 3 prefixes could be manually configured during the OER profile phase. In Cisco IOS Release 12.4(2)T, 12.2(33)SRB, and later releases, support for OER application-aware routing for policy-based routing (PBR) was introduced. Application-aware routing allows the selection of traffic for specific applications based on values in the IP packet header, other than the Layer 3 destination address through a named extended IP access control list (ACL). Only named extended ACLs are supported. The extended ACL is configured with a permit statement and then referenced in an OER map. The protocol and port numbers can be used to identify specific application traffic classes, but protocol and port number parameters are monitored only within the context of a prefix, and are not sent to the MTC list. Only the prefix that carries the specific application traffic is profiled by the master controller. With application-aware routing support, active monitoring of application traffic was supported. Passive monitoring of application traffic was introduced in Cisco IOS Release 12.4(9)T, 12.2(33)SRB, and later releases, with application traffic class configuration support of the profiling of DSCP values as well as protocol and port numbers. DSCP values, port numbers, and protocols in addition to prefixes, are all now stored in the MTC list.
In Cisco IOS Release 12.4(15)T, new static application mapping was introduced under OER map configuration mode to simplify the configuration of traffic classes. If you are running Cisco IOS Release 12.4(15)T or a later release, please refer to the "Using Performance Routing to Profile the Traffic Classes" module for static application mapping configuration information and tasks introduced for Performance Routing. Performance Routing (PfR) is an extension of the Optimized Edge Routing (OER) technology and the commands and command modes for PfR use the oer naming convention.
How to Configure OER to Profile the Traffic Classes
An OER master controller can be configured to automatically learn the traffic classes, or the traffic classes can be manually configured. Two types of traffic classes—to be automatically learned or manually configured—can be profiled:
•
•
Note
One or more of the following tasks may be performed:
•
•
•
•
•
•
•
•
•
Configuring OER to Automatically Learn Prefix-Based Traffic Classes
Perform this task to configure an OER master controller to automatically learn prefixes to be used as traffic classes to be entered in the MTC list. This task is performed on the master controller shown in Figure 2.
Figure 2 Network Diagram of OER Master Controller and Border Routers
The learn command is entered in OER master controller configuration mode and is required to enter OER Top Talker and Top Delay configuration mode. This task configures prefix learning based on the highest outbound throughput or the highest delay time, and one or both of these parameters must be specified. Optional configuration parameters such as learning period timers, maximum number of prefixes, and an expiration time for MTC list entries are also shown.
Note
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
DETAILED STEPS
What to Do Next
This section shows how to configure automatic prefix learning. To configure specific prefixes for OER monitoring and optimization, see the "Manually Selecting Prefixes for OER Monitoring" section.
Configuring OER to Automatically Learn Traffic Classes Using Inside Prefixes
In Cisco IOS Release 12.4(9)T, 12.2(33)SRB, and later releases, the OER BGP inbound optimization feature introduced the ability to automatically learn inside prefixes to support best entrance selection for traffic that originates from prefixes outside an autonomous system destined for prefixes inside the autonomous system.
Perform this task to configure an OER master controller to automatically learn inside prefixes to be used as traffic classes to be entered in the MTC list. This task is configured at the master controller and introduces the inside bgp command used in OER Top Talker and Top Delay configuration mode. This task configures automatic prefix learning of the inside prefixes (prefixes within the network). Optional configuration parameters such as learning period timers, maximum number of prefixes, and an expiration time for MTC list entries are also shown.
Prerequisites
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
DETAILED STEPS
What to Do Next
This section shows how to configure automatic prefix learning for inside prefixes. To configure specific inside prefixes for OER monitoring and optimization, see the "Manually Selecting Inside Prefixes for OER Monitoring" section.
Configuring OER to Automatically Learn Prefix-Based Traffic Classes Using Protocol or Port Number
Perform this task to configure an OER master controller to learn traffic classes to be entered in the MTC list based on prefixes but filtered by the protocol or port number. This task is performed on a master controller. The learn command is entered in OER master controller configuration mode and is required to enter OER Top Talker and Top Delay configuration mode. This task configures prefix learning based on the highest outbound throughput or the highest delay time and one or both of these parameters must be specified. After the prefix has been learned, a protocol or port number can be specified to create a subset of traffic classes. Optional configuration parameters such as learning period timers, the maximum number of prefixes, and an expiration time for MTC list entries are also shown.
Prerequisites
This task requires Cisco IOS Release 12.3(11)T, 12.2(33)SRB, or later release, to be running on the master controller and border routers.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
DETAILED STEPS
What to Do Next
This section shows how to configure automatic prefix-based traffic class learning using protocol or port number. To configure specific prefix-based traffic classes using protocol or port numbers for OER monitoring and optimization, see the "Manually Selecting Traffic Classes Using Prefix, Protocol, Port, and DSCP Value" section.
Specifying the Flow Keys for Automatic Learning of Application Traffic Classes
Perform this task at the master controller to define the application traffic flow fields that OER can use to automatically learn traffic classes to be entered in the MTC list. In Cisco IOS Release 12.4(9)T, 12.2(33)SRB, and later releases, traffic class commands were introduced to help define the application traffic classes. The traffic class commands can be used in the following situations:
•
•
In Cisco IOS Release 12.4(9)T and 12.2(33)SRB the ability to learn traffic using protocol, port number, and DSCP value (in addition to prefix) was introduced. Specifying the protocol, ports, and DSCP value allows application traffic to be identified in more detail. In this task, only traffic class keys are specified for voice traffic. The voice application traffic is identified by the UDP protocol, a DSCP value of ef, and port numbers in the range from 3000 to 4000. The master controller is also configured to learn the top prefixes based on highest outbound throughput for the specified traffic and the resulting traffic classes are added to the OER application database to be passively and actively monitored.
To display information about the traffic classes learned by OER use the"Displaying Application Traffic Flow Information on a Border Router" section.
Prerequisites
This task requires the master controller and border routers to be running Cisco IOS Release 12.4(9)T, 12.2(33)SRB, or later releases.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
DETAILED STEPS
Creating an Access List to Specify a Filter for Automatically Learned Application Traffic
Perform this task at the master controller to create an access list to filter specific application traffic for OER monitoring. In Cisco IOS Release 12.4(9)T and 12.2(33)SRB the ability to learn traffic using protocol, port number, and DSCP value (in addition to prefix) was introduced. Specifying the protocol, ports, and DSCP value allows application traffic to be identified in more detail.
In the Specifying the Flow Keys for Automatic Learning of Application Traffic Classes task, traffic keys were used to identify application traffic because no knowledge of any of the prefixes was assumed. If you know some prefixes that you want to exclude, then you can use this task to create an access list and filter out unwanted traffic. In this example for Voice traffic, the access list, VOICE_FILTER_LIST, configures OER to identify all UDP traffic from any source to a destination prefix of 10.1.0.0/16 with a DSCP value of ef that represents voice traffic. The access list is applied using a traffic class command that filters out unwanted traffic. The master controller is also configured to learn the top prefixes based on highest outbound throughput for the filtered traffic and the resulting traffic classes are added to the OER application database to be passively and actively monitored.
To display information about the traffic classes learned by OER use the"Displaying Application Traffic Flow Information on a Border Router" section.
Prerequisites
This task requires the master controller and border routers to be running Cisco IOS Release 12.4(9)T, 12.2(33)SRB, or later releases.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
ip access-list {standard | extended} access-list-name
Example:Router(config)# ip access-list extended VOICE_FILTER_LIST
Defines an IP access list by name.
•
•
Step 4
[sequence-number] permit udp source source-wildcard [operator [port]] destination destination-wildcard [operator [port]] [dscp dscp-value]
Example:Router(config-ext-nacl)# permit udp any 10.1.0.0 0.0.255.255 dscp ef
Sets conditions to allow a packet to pass a named IP access list.
•
Note
Step 5
exit
Example:Router(config-ext-nacl)# exit
(Optional) Exits extended access list configuration mode and returns to global configuration mode.
Step 6
oer master
Example:Router(config)# oer master
Enters OER master controller configuration mode to configure a Cisco router as a master controller and to configure master controller policy and timer settings.
Step 7
learn
Example:Router(config-oer-mc)# learn
Enters OER Top Talker and Top Delay learning configuration mode to configure prefix learning policies and timers.
Step 8
aggregation-type {bgp | non-bgp | prefix-length} prefix-mask
Example:Router(config-oer-mc-learn)# aggregation-type prefix-length 24
(Optional) Configures a master controller to aggregate learned prefixes based on traffic flow type.
•
•
•
•
•
Step 9
throughput
Example:Router(config-oer-mc-learn)# throughput
Configures the master controller to learn the top prefixes based on the highest outbound throughput.
•
•
Step 10
monitor-period minutes
Example:Router(config-oer-mc-learn)# monitor-period 10
(Optional) Sets the time period that an OER master controller learns traffic flows.
•
•
•
•
Step 11
periodic-interval minutes
Example:Router(config-oer-mc-learn)# periodic-interval 20
(Optional) Sets the time interval between prefix learning periods.
•
•
Step 12
prefixes number
Example:Router(config-oer-mc-learn)# prefixes 200
(Optional) Sets the number of prefixes that the master controller will learn during the monitoring period.
•
•
Step 13
traffic-class filter access-list access-list-name
Example:Router(config-oer-mc-learn)# traffic-class filter access-list VOICE_FILTER_LIST
Supports filtering of traffic classes during OER passive monitoring by using an extended access list.
•
Step 14
end
Example:Router(config-oer-mc-learn)# end
Exits OER Top Talker and Top Delay learning configuration mode, and returns to privileged EXEC mode.
Creating an Access List to Specify Aggregation Criteria for Automatically Learned Application Traffic
Perform this task at the master controller to create an access list to aggregate learned application traffic for OER monitoring. In Cisco IOS Release 12.4(9)T and 12.2(33)SRB the ability to learn traffic using protocol, port number, and DSCP value (in addition to prefix) was introduced. Specifying the protocol, ports, and DSCP value allows application traffic to be identified in more detail.
In the Creating an Access List to Specify a Filter for Automatically Learned Application Traffic task, the application traffic was filtered to profile traffic for a specific destination prefix, but in this task, the application traffic is being aggregated for a range of destination ports. In this example, the access list, VOICE_AGG_LIST is configured to aggregate traffic with a destination port in the range from 3000 to 4000 and with a DSCP value of ef. This UDP traffic represents voice traffic and OER will create traffic classes based on the specified port number range and DSCP value. In this task, the master controller is also configured to learn the top prefixes based on highest outbound throughput for the aggregated traffic and the resulting traffic classes are added to the OER application database to be passively and actively monitored.
The last step in this task is an optional step to review the configuration on the OER master controller. To display more information about the traffic classes learned by OER use the"Displaying Application Traffic Flow Information on a Border Router" section.
Prerequisites
This task requires the master controller and border routers to be running Cisco IOS Release 12.4(9)T, 12.2(33)SRB, or later releases.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
ip access-list {standard | extended} access-list-name
Example:Router(config)# ip access-list extended VOICE_AGG_LIST
Defines an IP access list by name.
•
•
Step 4
[sequence-number] permit udp source source-wildcard [operator [port]] destination destination-wildcard [operator [port]] [dscp dscp-value]
Example:Router(config-ext-nacl)# permit udp any any range 3000 4000 dscp ef
Sets conditions to allow a packet to pass a named IP access list.
•
Note
Step 5
exit
Example:Router(config-ext-nacl)# exit
(Optional) Exits extended access list configuration mode and returns to global configuration mode.
Step 6
oer master
Example:Router(config)# oer master
Enters OER master controller configuration mode to configure a Cisco router as a master controller and to configure master controller policy and timer settings.
Step 7
learn
Example:Router(config-oer-mc)# learn
Enters OER Top Talker and Top Delay learning configuration mode to configure prefix learning policies and timers.
Step 8
aggregation-type {bgp | non-bgp | prefix-length} prefix-mask
Example:Router(config-oer-mc-learn)# aggregation-type prefix-length 24
(Optional) Configures a master controller to aggregate learned prefixes based on traffic flow type.
•
•
•
•
•
Step 9
throughput
Example:Router(config-oer-mc-learn)# throughput
Configures the master controller to learn the top prefixes based on the highest outbound throughput.
•
•
Step 10
monitor-period minutes
Example:Router(config-oer-mc-learn)# monitor-period 10
(Optional) Sets the time period that an OER master controller learns traffic flows.
•
•
•
•
Step 11
periodic-interval minutes
Example:Router(config-oer-mc-learn)# periodic-interval 20
(Optional) Sets the time interval between prefix learning periods.
•
•
Step 12
prefixes number
Example:Router(config-oer-mc-learn)# prefixes 200
(Optional) Sets the number of prefixes that the master controller will learn during the monitoring period.
•
•
Step 13
traffic-class aggregate access-list access-list-name
Example:Router(config-oer-mc-learn)# traffic-class aggregate access-list VOICE_AGG_LIST
Supports aggregation of traffic classes during OER passive monitoring by using an extended access list.
•
Step 14
end
Example:Router(config-oer-mc-learn)# end
Exits OER Top Talker and Top Delay learning configuration mode, and returns to privileged EXEC mode.
Step 15
show oer master
Example:Router# show oer master
(Optional) Displays information about the status of the OER-managed network; the output includes information about the master controller, the border routers, OER managed interfaces, and default and user-defined policy settings.
Examples
The following example output for the show oer master command displays the additional configuration for the traffic class aggregation, filters, and key list under the Learn Settings section.
Router# show oer masterOER state: ENABLED and ACTIVEConn Status: SUCCESS, PORT: 7777Version: 2.0Number of Border routers: 2Number of Exits: 2Number of monitored prefixes: 0 (max 5000)Max prefixes: total 5000 learn 2500Prefix count: total 0, learn 0, cfg 0Border Status UP/DOWN AuthFail Version1.1.1.2 ACTIVE UP 00:18:57 0 2.01.1.1.1 ACTIVE UP 00:18:58 0 2.0Global Settings:max-range-utilization percent 20 recv 20mode route metric bgp local-pref 5000mode route metric static tag 5000trace probe delay 1000loggingDefault Policy Settings:backoff 180 200 180delay relative 50holddown 300periodic 0probe frequency 56mode route controlmode monitor activemode select-exit goodloss relative 10jitter threshold 20mos threshold 3.60 percent 30unreachable relative 50resolve delay priority 11 variance 20resolve utilization priority 12 variance 20*tag 0Learn Settings:current state : STARTEDtime remaining in current state : 70 secondsthroughputno delayno inside bgptraffic-class filter access-list voice-filter-acl <----traffic-class aggregate access-list voice-agg-acl <----traffic-class keys protocol dscp dport <----no protocolmonitor-period 2periodic-interval 1aggregation-type prefix-length 24prefixes 10expire after time 720Displaying Application Traffic Flow Information on a Border Router
Perform this task to display application traffic flow information. These commands are entered on a border router through which the application traffic is flowing. The commands can be entered in any order. Keywords in Step 2 and Step 4 require the border router to be running Cisco IOS Release 12.4(9)T, 12.2(33)SRB, 12.2(33)SXH, or later releases.
Prerequisites
This task requires the master controller and border routers to be running Cisco IOS Release 12.4(9)T, 12.2(33)SRB, or later releases.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Step 1
Enables privileged EXEC mode. Enter your password if prompted.
Router> enableStep 2
This command is used to display traffic class filter and aggregation ACL information. The following example displays the voice application filter, aggregation, and keys information configured in the first three tasks under the "Specifying the Flow Keys for Automatic Learning of Application Traffic Classes" task.
Router# show oer border passive learnOER Border Learn Configuration :State is enabledMeasurement type: throughput, Duration: 2 minAggregation type: prefix-length, Prefix length: 24No port protocol configTraffic Class Filter List:List: SrcPrefix SrcMask DstPrefix DstMaskProt DSCP sport_opr sport_range dport_opr dport_range Grant1: 0.0.0.0 0 10.1.0.0 1617 ef 0 [1, 65535] 0 [1, 65535] PermitTraffic Class Aggregate List:List: Prot DSCP sport_opr sport_range dport_opr dport_range Grant1: 17 ef 0 [1, 65535] 7 [3000, 4000] PermitKeys: protocol dscp DstPortStep 3
This is a NetFlow command that is used to display all the flows (including applications) currently active on the border router. The following example displays traffic flow statistics by protocol, source address, and destination:
Router# show ip cache verbose flowIP packet size distribution (203337 total packets):1-32 64 96 128 160 192 224 256 288 320 352 384 416 448 480.397 .602 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000512 544 576 1024 1536 2048 2560 3072 3584 4096 4608.000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000IP Flow Switching Cache, 278544 bytes5 active, 4091 inactive, 310 added47486 ager polls, 0 flow alloc failuresActive flows timeout in 30 minutesInactive flows timeout in 15 secondsIP Sub Flow Cache, 25800 bytes13 active, 1011 inactive, 355 added, 310 added to flow0 alloc failures, 0 force free1 chunk, 1 chunk addedlast clearing of statistics neverProtocol Total Flows Packets Bytes Packets Active(Sec) Idle(Sec)-------- Flows /Sec /Flow /Pkt /Sec /Flow /FlowTCP-other 14 0.0 7370 40 9.7 1556.8 3.4UDP-other 9 0.0 7579 28 6.4 1601.0 3.5ICMP 282 0.0 1 64 0.0 0.0 15.6Total: 305 0.0 562 35 16.3 118.7 14.7SrcIf SrcIPaddress DstIf DstIPaddress Pr TOS Flgs PktsPort Msk AS Port Msk AS NextHop B/Pk ActiveEt8/0 172.20.1.1 Et0/0 10.1.3.1 11 B8 10 633407D0 /0 0 0DAC /0 0 10.40.40.2 28 1337.8Et8/0 172.20.1.1 Et0/0 10.2.2.1 06 00 00 633807D0 /0 0 0DAC /0 0 10.40.40.2 40 1338.6Et8/0 172.20.1.1 Et0/0 10.1.3.1 06 00 00 633307D0 /0 0 0DAC /0 0 10.40.40.2 40 1337.6Et8/0 172.20.1.1 Et0/0 10.1.1.1 06 00 00 633407D0 /0 0 1964 /0 0 10.40.40.2 40 1337.8Et8/0 172.20.1.1 Et0/0 10.1.1.1 11 B8 10 633907D0 /0 0 0E10 /0 0 10.40.40.2 28 1338.8Total number of prefixes 2Step 4
This command is used to display real-time prefix information collected from the border router through NetFlow passive monitoring. Using the learned and applications keywords you can display information about learned applications. In the output you can see that only application traffic classes matching the traffic class keys, filter, and aggregation criteria set in the first three tasks under the "Specifying the Flow Keys for Automatic Learning of Application Traffic Classes" task are saved in the learn cache.
Router# show oer border passive cache learned applicationsOER Learn Cache:State is enabledMeasurement type: throughput, Duration: 2 minAggregation type: prefix-length, Prefix length: 244096 oer-flows per chunk,8 chunks allocated, 32 max chunks,5 allocated records, 32763 free records, 4588032 bytes allocatedPrefix Mask Pkts B/Pk Delay Samples ActiveProt Dscp SrcPort DstPortHost1 Host2 Host3 Host4 Host5dport1 dport2 dport3 dport4 dport510.1.3.0 /24 873 28 0 0 13.317 ef [1, 65535] [3000, 4000]10.1.3.1 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.03500 0 0 0 010.1.1.0 /24 7674 28 0 0 13.417 ef [1, 65535] [3000, 4000]10.1.1.1 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.03600 0 0 0 0
What To Do Next
Manually Selecting Prefixes for OER Monitoring
Perform this task to manually select prefixes for monitoring. An IP prefix list is created to define the prefix or prefix range. The prefix list is then imported into the central policy database by configuring a match clause in an OER map. For details about using IP prefix lists with OER, see the "Prefix Traffic Class Configuration Using OER" section.
OER Map Operation for the OER Profile Phase
An OER map may appear to be similar to a route map but there are significant differences. An OER map is configured to select an IP prefix list using a match clause. The OER map is configured with a sequence number like a route map, and the OER map with the lowest sequence number is evaluated first. The operation of an OER map differs from a route map at this point. There are two important distinctions:
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
What to Do Next
This section shows how to manually configure prefix learning. To configure automatic prefix learning, see the "Configuring OER to Automatically Learn Prefix-Based Traffic Classes" section.
Manually Selecting Inside Prefixes for OER Monitoring
In Cisco IOS Release 12.4(9)T, 12.2(33)SRB, and later releases, the OER BGP inbound optimization feature introduced the ability to manually select inside prefixes to support best entrance selection for traffic that originates from prefixes outside an autonomous system destined for prefixes inside the autonomous system. Perform this task to manually select inside prefixes for OER monitoring by creating an IP prefix list to define the inside prefix or prefix range. The prefix list is then imported into the MTC list by configuring a match clause in an OER map. For details about using IP prefix lists with OER, see the "Prefix Traffic Class Configuration Using OER" section.
OER Inside Prefixes
An OER inside prefix is defined as a public IP prefix assigned to a company. An OER outside prefix is defined as a public IP prefix assigned outside the company. Companies advertise the inside prefixes over the Internet using an Internet service provider (ISP) and receive advertisements for outside prefixes from an ISP.
OER Map Operation for Inside Prefixes
The operation of an OER map is similar to the operation of a route-map. An OER map is configured to select an IP prefix list or OER learn policy using a match clause and then to apply OER policy configurations using a set clause. The OER map is configured with a sequence number like a route-map, and the OER map with the lowest sequence number is evaluated first. In Cisco IOS Release 12.4(9)T and 12.2(33)SRB, the inside keyword that identifies inside prefixes was added to the match ip address (OER) command.
Prerequisites
This task requires the master controller and border routers to be running Cisco IOS Release 12.4(9)T, 12.2(33)SRB, or later releases.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
What to Do Next
This section shows how to configure specific inside prefixes for OER monitoring and optimization. To configure automatic prefix learning for inside prefixes, see the "Configuring OER to Automatically Learn Traffic Classes Using Inside Prefixes" section.
Manually Selecting Traffic Classes Using Prefix, Protocol, Port, and DSCP Value
Perform this task to manually select traffic classes using prefixes, protocols, port numbers, and DSCP value for OER monitoring. An IP access list is created to define the parameters to identify the traffic classes. The access list can then be imported into the MTC list by configuring a match clause in an OER map.
This example task uses an access list to identify voice traffic. Before voice traffic can be optimized, it must be identified. In this task, the voice traffic that is to be optimized is identified by a protocol of UDP, a range of source and destination port numbers from 16384 to 32767, a destination prefix of 10.20.20.0/24, and a DSCP value of ef.
IP Protocol Stack for Voice
Voice traffic uses a variety of protocols and streams on the underlying IP network. Figure 3 is a representation of the protocol options available for carrying voice traffic over IP. Most signaling traffic for voice is carried over TCP. Most voice calls are carried over User Datagram Protocol (UDP) and Real-Time Protocol (RTP). You can configure your voice devices to use a specific range of destination port numbers over UDP to carry voice call traffic.
Figure 3 Protocol Stack Options Available for Voice Traffic
Prerequisites
This task requires the master controller and border routers to be running Cisco IOS Release 12.4(9)T, 12.2(33)SRB, or later releases.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
ip access-list {standard | extended} access-list-name
Example:Router(config)# ip access-list extended VOICE_ACCESS_LIST
Defines an IP access list by name.
•
•
Step 4
[sequence-number] permit udp source source-wildcard [operator [port]] destination destination-wildcard [operator [port]] [dscp dscp-value]
Example:Router(config-ext-nacl)# permit udp any range 16384 32767 10.20.20.0 0.0.0.15 range 16384 32767 dscp ef
Sets conditions to allow a packet to pass a named IP access list.
•
•
Step 5
exit
Example:Router(config-ext-nacl)# exit
(Optional) Exits extended access list configuration mode and returns to global configuration mode.
Step 6
oer-map map-name sequence-number
Example:Router(config)# oer-map VOICE_MAP 10
Enters OER map configuration mode to configure an OER map to apply policies to selected IP prefixes.
•
•
•
Step 7
match ip address {access-list access-list-name | prefix-list prefix-list-name}
Example:Router(config-oer-map)# match ip address access-list VOICE_ACCESS_LIST
References an extended IP access list or IP prefix as match criteria in an OER map.
•
•
Step 8
end
Example:Router(config-oer-map)# end
(Optional) Exits OER map configuration mode and returns to privileged EXEC mode.
What to Do Next
This section shows how to manually select traffic classes using prefixes, protocols, port numbers, and DSCP value for OER monitoring. To configure automatic learning of traffic classes using prefixes, protocols, port numbers, and DSCP values, see the "Specifying the Flow Keys for Automatic Learning of Application Traffic Classes" section.
Configuration Examples for Using OER to Profile the Traffic Classes
The examples in this section show how to configure automatic prefix learning and how to select specific prefixes for monitoring.
•
•
•
•
•
Configuring OER to Automatically Learn Prefix-Based Traffic Classes: Example
The following example, starting in global configuration mode, configures the master controller to automatically learn top prefixes based on the highest delay. The prefix monitoring period is set to 10 minutes. The number of prefixes that are monitored during each monitoring period is set to 500. The time interval between each monitoring period is set to 20 minutes.
Router(config)# oer masterRouter(config-oer-master)# learnRouter(config-oer-master-learn)# delayRouter(config-oer-master-learn)# aggregation-type bgpRouter(config-oer-master-learn)# monitor-period 10Router(config-oer-master-learn)# periodic-interval 20Router(config-oer-master-learn)# prefixes 500Router(config-oer-master-learn)# endConfiguring OER to Automatically Learn Traffic Classes Using Inside Prefixes: Example
The following example shows how to configure OER to automatically learn prefixes inside the network:
Router> enableRouter# configure terminalRouter(config)# oer masterRouter(config-oer-mc)# learnRouter(config-oer-mc-learn)# inside bgpRouter(config-oer-mc-learn)# monitor-period 10Router(config-oer-mc-learn)# periodic-interval 20Router(config-oer-mc-learn)# prefixes 500Router(config-oer-mc-learn)# endConfiguring OER to Automatically Learn Traffic Classes Using Prefixes and Protocol or Port Numbers: Example
The following example, starting in global configuration mode, learns traffic for SSH sessions that use 49152 as the destination port number in the IP packet header.
Router(config)# oer masterRouter(config-oer-master)# learnRouter(config-oer-master-learn)# throughputRouter(config-oer-master-learn)# aggregation-type bgpRouter(config-oer-master-learn)# monitor-period 10Router(config-oer-master-learn)# periodic-interval 20Router(config-oer-master-learn)# protocol 22 port 49152 dstRouter(config-oer-master-learn)# endConfiguring OER to Automatically Learn Traffic Classes Using Protocol, Ports, and DSCP Value: Example
The following example, starting in global configuration mode, configures the master controller to automatically learn defined application traffic. Using a series of traffic class commands under OER learn configuration mode, only voice traffic with a DSCP bit set to ef, a protocol of UDP, and a destination port in the range of 3000 to 4000 is learned and added to the OER MTC list on the master controller.
The prefix monitoring period is set to 2 minutes. The number of prefixes that are monitored during each monitoring period is set to 10. The time interval between each monitoring period is set to 20 minutes.
Router(config)# ip access-list extended voice-filter-aclRouter(config-ext-nacl)# permit udp any 10.1.0.0 0.0.255.255 dscp efRouter(config-ext-nacl)# exitRouter(config)# ip access-list extended voice-agg-aclRouter(config-ext-nacl)# permit udp any any range 3000 4000 dscp efRouter(config-ext-nacl)# exitRouter(config)# oer masterRouter(config-oer-master)# learnRouter(config-oer-master-learn)# aggregation-type prefix-length 24Router(config-oer-master-learn)# throughputRouter(config-oer-master-learn)# monitor-period 2Router(config-oer-master-learn)# periodic-interval 1Router(config-oer-master-learn)# prefixes 10Router(config-oer-master-learn)# traffic-class filter access-list voice-filter-aclRouter(config-oer-master-learn)# traffic-class aggregate access-list voice-agg-aclRouter(config-oer-master-learn)# traffic-class keys protocol dport dscpRouter(config-oer-master-learn)# endMore details about the OER network configuration for the example shown above can be seen in the running configuration file:
Router# show running-configoer masterport 7777logging!border 10.1.1.1 key-chain key1interface Serial12/0 externalinterface Ethernet8/0 internal!border 10.1.1.2 key-chain key2interface Ethernet0/0 externalinterface Ethernet8/0 internal!learnthroughputperiodic-interval 1monitor-period 2prefixes 10traffic-class filter access-list voice-filter-acltraffic-class aggregate access-list voice-agg-acltraffic-class keys protocol dscp dportbackoff 180 200mode route controlmode monitor active!active-probe echo 10.1.2.1active-probe echo 10.1.1.1active-probe echo 10.1.3.1Manually Selecting Prefixes for OER Monitoring: Example
The following example, starting in global configuration mode, configures an OER map to exclude traffic from the 192.168.0.0/16 network and include traffic from the 10.5.5.0/24 network. Excluded prefixes are not imported into the MTC list.
Router(config)# ip prefix-list seq 10 EXCLUDE deny 192.168.0.0/16 le 32Router(config)# ip prefix-list seq 10 IMPORT permit 10.5.5.0/24Router(config)# oer-map PREFIXES 10Router(config-oer-map)# match ip address prefix-list EXCLUDERouter(config-oer-map)# exitRouter(config)# oer-map PREFIXES 20Router(config-oer-map)# match ip address prefix-list IMPORTRouter(config-oer-map)# endManually Selecting Inside Prefixes for OER Monitoring: Example
The following example shows how to manually configure OER to learn prefixes inside the network using an OER map:
Router> enableRouter# configure terminalRouter(config)# ip prefix-list INSIDE_PREFIXES seq 20 permit 192.168.1.0/24Router(config)# oer-map INSIDE_MAP 10Router(config-oer-map)# match ip address prefix-list INSIDE_PREFIXES insideRouter(config-oer-map)# endManually Selecting Traffic Classes Using Prefix, Protocol, Port, and DSCP Value: Example
The following configuration is performed on an edge router which is both an OER master controller and a border router (for example, in a remote office network) to identify voice traffic using an extended named access list.
Router> enableRouter# configure terminalRouter(config)# ip access-list extended Voice_TrafficRouter(config-ext-nacl)# 10 permit udp any 10.1.0.0 0.0.255.255 range 16384 32767 dscp efRouter(config-ext-nacl)# exitRouter(config)# oer-map Voice_MAP 10Router(config-oer-map)# match ip address access-list Voice_TrafficRouter(config-oer-map)# endWhere To Go Next
This module covered the OER profile phase and it has assumed that you started with the "Cisco IOS Optimized Edge Routing Overview" and the "Setting Up OER Network Components" module. The profile phase is the first phase in the OER performance loop. To learn more about the other OER phases, read through the other modules in the following list:
•
•
•
After you understand the various OER phases, review the OER solutions modules that are listed under "Related Documents" section.
Additional References
The following sections provide references related to using OER to profile the traffic classes.
Related Documents
Cisco OER technology overview
Concepts and configuration tasks required to set up OER network components
OER solution module: voice traffic optimization using OER active probes.
OER solution module: configuring VPN IPsec/GRE tunnel interfaces as OER-managed exit links.
"Configuring VPN IPsec/GRE Tunnel Interfaces As OER-Managed Exit Links" module
Cisco OER commands: complete command syntax, command mode, command history, defaults, usage guidelines and examples
IP prefix list commands
Technical Assistance
Feature Information for Using OER to Profile the Traffic Classes
Table 1 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Release 12.3(11)T, 12.2(33)SRB, or a later release appear in the table.
For information on a feature in this technology that is not documented here, see the "Cisco IOS Optimized Edge Routing Features Roadmap."
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 1 Feature Information for Using OER to Profile the Traffic Classes
Port and Protocol Based Prefix Learning
12.3(11)T
12.2(33)SRBPort and protocol based prefix learning allows you to configure a master controller to learn prefixes based on the protocol type and TCP or UDP port number.
The following sections provide information about this feature:
•
•
•
•
•
The protocol command was introduced by this feature.
expire command1
12.3(14)T
12.2(33)SRBThe expire command is used to set an expiration period for learned prefixes. By default, the master controller removes inactive prefixes from the central policy database as memory is needed. This command allows you to refine this behavior by setting a time or session based limit. The time based limit is configured in minutes. The session based limit is configured for the number of monitor periods (or sessions).
OER Application-Aware Routing: PBR
12.4(2)T
12.2(33)SRBThe OER Application-Aware Routing: PBR feature introduces the capability to optimize IP traffic based on the type of application that is carried by the monitored prefix. Independent policy configuration is applied to the subset (application) of traffic.
The following sections provide information about this feature:
•
The following commands were introduced or modified by this feature: debug oer border pbr, debug oer master prefix, match ip address (OER), show oer master active-probes, and show oer master appl.
OER BGP Inbound Optimization
12.4(9)T
12.2(33)SRBOER BGP inbound optimization supports best entrance selection for traffic that originates from prefixes outside an autonomous system destined for prefixes inside the autonomous system. External BGP (eBGP) advertisements from an autonomous system to an Internet service provider (ISP) can influence the entrance path for traffic entering the network. OER uses eBGP advertisements to manipulate the best entrance selection.
The following sections provide information about this feature:
•
•
•
•
•
The following commands were introduced or modified by this feature: clear oer master prefix, downgrade bgp, inside bgp, match ip address (OER), match oer learn, max range receive, maximum utilization receive, show oer master prefix.
OER DSCP Monitoring
12.4(9)T
12.2(33)SRBOER DSCP Monitoring introduced automatic learning of traffic classes based on protocol, port numbers, and DSCP value. Traffic classes can be defined by a combination of keys comprising of protocol, port numbers, and DSCP values, with the ability to filter out traffic that is not required, and the ability to aggregate the traffic in which you are interested. Layer 4 information such as protocol, port number, and DSCP information is now sent to the master controller database in addition to the Layer 3 prefix information. The new functionality allows OER to both actively and passively monitor application traffic.
The following sections provide information about this feature:
•
•
•
The following commands were introduced or modified by this feature: show oer border passive applications, show oer border passive cache, show oer border passive learn, show oer master appl, traffic-class aggregation, traffic-class filter, and traffic-class keys.
OER Border Router Only Functionality
12.2(33)SXH
In Cisco IOS Release 12.2(33)SXH support for using a Cisco Catalyst 6500 series switch as an OER border router was introduced. Only border router functionality is included in the Cisco IOS Release 12.2(33)SXH images; no master controller configuration is available. The master controller that communicates with the Cisco Catalyst 6500 series switch being used as a border router must be a router running Cisco IOS Release 12.4(6)T or a later release. The OER master controller software has been modified to handle the limited functionality supported by the Cisco Catalyst 6500 border routers. Using the Route Processor (RP), the Catalyst 6500 border routers can capture throughput statistics only for a traffic class compared to the delay, loss, unreachability, and throughput statistics collected by non-Catalyst 6500 border routers. A master controller automatically detects the limited capabilities of the Catalyst 6500 border routers and downgrades other border routers to capture only the throughput statistics for traffic classes. By ignoring other types of statistics, the master controller is presented with a uniform view of the border router functionality.
The following sections provide information about this feature:
•
•
The following command was introduced or modified by this feature: show oer border passive cache.
1 This is a minor enhancement. Minor enhancements are not typically listed in Feature Navigator.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0910R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2007-2009 Cisco Systems, Inc. All rights reserved.
