Cisco IOS Optimized Edge Routing Command Reference
S through U
Downloads: This chapterpdf (PDF - 645.0KB) The complete bookPDF (PDF - 1.44MB) | Feedback

set active-probeset backoffset delayset holddownset interface (OER)set jitterset link-groupset lossset modeset mosset next-hop (OER)set periodicset probeset resolveset traceroute reportingset unreachableshow oer api clientshow oer api providershow oer bordershow oer border active-probesshow oer border defined applicationshow oer border passive applicationsshow oer border passive cacheshow oer border passive learnshow oer border passive prefixesshow oer border routesshow oer mastershow oer master active-probesshow oer master applshow oer master bordershow oer master cost-minimizationshow oer master defined applicationshow oer master learn listshow oer master link-groupshow oer master nbar applicationshow oer master policyshow oer master prefixshow oer master traffic-classshow oer master traffic-class application nbarshow oer proxyshutdown (OER)throughputtraceroute probe-delaytraffic-class access-listtraffic-class aggregatetraffic-class applicationtraffic-class application nbartraffic-class filtertraffic-class keystraffic-class prefix-listunreachable

S through U

set active-probe

To configure an Optimized Edge Routing (OER) map active probe with a forced target assignment, use the set active-probe command in OER map configuration mode. To disable the active probe, use the no form of this command.

set active-probe probe-type ip-address [ target-port number ] [ codec codec-name ] [ dscp value ]
no set active-probe probe-type ip-address

Syntax Description

probe-type

Type of probe. Must be one of the following:

  • echo --Uses Internet Control Message Protocol (ICMP) echo (ping) messages.
  • jitter --Uses jitter messages.
  • tcp-conn --Uses TCP connection messages.
  • udp-echo --Uses User Datagram Protocol (UDP) echo messages.

ip-address

Target IP address of a prefix to be monitored using the specified type of probe.

target-port

(Not specified for echo probes.) Specifies the destination port number for the active probe. A remote responder must be configured on the target device with the ip sla monitor responder global configuration command.

Note    The ip sla monitor responder command was introduced in Cisco IOS Release 12.3(14)T. This command replaces the rtr responder command.

number

Port number in the range from 1 to 65535.

codec

(Optional) Only used with the jitter probe type. Specifies the codec value used for Mean Opinion Score (MOS) calculation.

codec-name

Codec value, must be one of the following:

  • g711alaw--G.711 A Law 64000 bps
  • g711ulaw--G.711 U Law 64000 bps
  • g729a--G.729 8000 bps

dscp

(Optional) Sets the Differentiated Services Code Point (DSCP) value.

value

DSCP value.

Command Default

No active probes are configured with a forced target assignment.

Command Modes

OER map configuration

Command History

Release

Modification

12.4(6)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

15.0(1)M

This command was modified. The dscp keyword and value argument were added.

12.2(33)SRE

This command was modified. The dscp keyword and value argument were added.

Usage Guidelines

Cisco IOS Release 15.0(1)M, 12.2(33)SRE, and Later Releases

If the optional dscp keyword and value argument are not specified, active probes are created using the DSCP value of the traffic class. For example, the software creates two sets of probes for the following three traffic classes. Traffic class 2 is assigned a probe with a DSCP value of "ef" and the other two traffic classes share a probe with a DSCP value of 0.

  • Traffic class 1: 10.1.1.0/24, destination port 23
  • Traffic class 2: 10.1.2.0/24, dscp ef
  • Traffic class 3: 10.1.2.0/24, destination port 991

If the optional dscp keyword and value argument is provided, probes are created using the specified DSCP value. For example, if the DSCP value specified for the set active-probe command is "cs1", only one probe is created for the three traffic classes.

Examples

The following example shows how to configure an ICMP reply (ping) message probe with a forced target assignment within an OER map. The 10.1.2.10 address is the forced target assignment. A remote responder must also be enabled on the target device.

Router(config)# oer-map MAP1 10
Router(config-oer-map)# match ip prefix-list LIST1
Router(config-oer-map)# set active-probe echo 10.1.2.10 

The following example shows how to configure a TCP connection message probe with a forced target assignment within an PfR map. The 10.1.2.10 address is the forced target assignment, the target port is defined as 29, and the DSCP value is set to ef. A remote responder must be enabled on the target device. This example requires Cisco IOS Release 15.0(1)M, 12.2(33)SRE, or a later release.

Router(config)# pfr-map MAP2 10
Router(config-pfr-map)# match ip prefix-list LISTMAP2
Router(config-pfr-map)# set active-probe tcp-conn 10.1.2.10 target-port 29 dscp ef

Related Commands

Command

Description

active-probe

Configures an OER active probe for a target prefix.

ip sla monitor responder

Enables the IP SLAs Responder for general IP SLAs operations.

oer-map

Enters OER map configuration mode to configure an OER map to apply policies to selected IP prefixes.

show oer border active-probes

Displays connection and status information about active probes on an OER border router.

show oer master active-probes

Displays connection and status information about active probes on an OER master controller.

set backoff

To configure an Optimized Edge Routing (OER) map to set the backoff timer to adjust the time period for prefix policy decisions, use the set backoff command in OER map configuration mode. To delete the set clause entry, use the no form of this command.

set backoff min-timer max-timer [ step-timer]
no set backoff

Syntax Description

min-timer

Minimum value for the backoff timer, in seconds. The configurable time period for this argument is from 180 to 7200. The default timer value is 300.

max-timer

Maximum value for the backoff timer, in seconds. The configurable time period for this argument is from 180 to 7200. The default timer value is 3000.

step-timer

(Optional) Tme period value for the step timer, in seconds. The step timer is used to add time to the out-of-policy waiting period each time the backoff timer expires and OER is unable to find an in-policy exit. The configurable time period for this argument is from 180 to 7200. The default timer value is 300.

Command Default

OER uses the following default values if this command is not configured or if the no form of this command is entered:

min-timer : 300max-timer: 3000step-timer: 300

Command Modes

OER map configuration

Command History

Release

Modification

12.3(8)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

Usage Guidelines

The set backoff command is entered on a master controller in OER map configuration mode. This command is used to configure an OER map to set the transition period that the master controller holds an out-of-policy prefix. The master controller uses a backoff timer to schedule the prefix transition period in which OER holds the out-of-policy prefix before moving the prefix to an in-policy state by selecting an in-policy exit. This command is configured with a minimum and maximum timer value and can be configured with an optional step timer.

Minimum Timer --The min-timer argument is used to set the minimum transition period in seconds. If the current prefix is in-policy when this timer expires, no change is made and the minimum timer is reset to the default or configured value. If the current prefix is out-of-policy, OER will move the prefix to an in-policy and reset the minimum timer to the default or configured value.

Maximum Timer --The max-timer argument is used to set the maximum length of time OER holds an out-of-policy prefix when there are no OER controlled in-policy prefixes. If all OER controlled prefixes are in an out-of-policy state and the value from the max-timerargument expires, OER will select the best available exit and reset the minimum timer to the default or configured value.

Step Timer --The step-timer argument allows you to optionally configure OER to add time each time the minimum timer expires until the maximum time limit has been reached. If the maximum timer expires and all OER managed exits are out-of-policy, OER will install the best available exit and reset the minimum timer.

Configuring a new timer value will immediately replace the existing value if the new value is less than the time remaining. If the new value is greater than the time remaining, the new timer value will be used when the existing timer value expires.

Examples

The following example creates an OER map named BACKOFF that sets the minimum timer to 400 seconds, the maximum timer to 4000 seconds, and the step timer to 400 seconds for traffic from the prefix list named CUSTOMER:

Router(config)# oer-map BACKOFF 70 
Router(config-oer-map)# match ip address prefix-list CUSTOMER 
Router(config-oer-map)# set backoff 400 4000 400 

Related Commands

Command

Description

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

oer-map

Enters OER map configuration mode to configure an OER map to apply policies to selected IP prefixes.

periodic (OER)

Sets the backoff timer to adjust the time period for prefix policy decisions.

set delay

To configure an Optimized Edge Routing (OER) map to configure OER to set the delay threshold, use the set delay command in OER map configuration mode. To delete the set clause entry, use the no form of this command.

set delay { relative percentage | threshold maximum }
no set delay

Syntax Description

relative percentage

Sets a relative delay policy based on a comparison of short-term and long-term delay percentages. The range of values that can be configured for this argument is a number from 1 to 1000. Each increment represents one tenth of a percent.

threshold maximum

Sets the absolute maximum delay time, in milliseconds. The range of values that can be configured for this argument is from 1 to 10000.

Command Default

OER uses the following default value if this command is not configured or if the no form of this command is entered:

relative percentage : 500 (50 percent)

Command Modes

OER map configuration

Command History

Release

Modification

12.3(8)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

Usage Guidelines

The set delay command is entered on a master controller in OER map configuration mode. This command is configured in an OER map to set the delay threshold as a relative percentage or as an absolute value for match criteria.

The relative keyword is used to configure a relative delay percentage. The relative delay percentage is based on a comparison of short-term and long-term measurements. The short-term measurement reflects the delay percentage within a 5-minute time period. The long-term measurement reflects the delay percentage within a 60-minute period. The following formula is used to calculate this value:

Relative delay measurement = ((short-term measurement - long-term measurement) / long-term measurement) * 100

The master controller measures the difference between these two values as a percentage. If the percentage exceeds the user-defined or default value, the delay percentage is determined to be out-of-policy. For example, if long-term delay measurement 100 milliseconds and short-term delay measurement is 120 milliseconds, the relative delay percentage is 20 percent.

The threshold keyword is used to configure the absolute maximum delay period in milliseconds.

If the measured delay of the prefix is higher than the configured delay threshold, then the prefix is out-of-policy. If the short-term delay of the prefix is more than long-term delay by the percentage value configured, then the prefix is out-of-policy.

Examples

The following example creates an OER map named DELAY that sets the absolute maximum delay threshold to 2000 milliseconds for traffic from the prefix list named CUSTOMER:

Router(config)# oer-map DELAY 80 
Router(config-oer-map)# match ip address prefix-list CUSTOMER
 
Router(config-oer-map)# set delay threshold 2000 

Related Commands

Command

Description

delay

Configures configure prefix delay parameters.

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

oer-map

Enters OER map configuration mode to configure an OER map to apply policies to selected IP prefixes.

set holddown

To configure an OER map to set the prefix route dampening timer for the minimum period of time in which a new exit must be used before an alternate exit can be selected, use the set holddown command in OER map configuration mode. To delete the set clause entry, use the no form of this command.

set holddown timer
no set holddown

Syntax Description

timer

Sets the prefix route dampening time period, in seconds. The range for this argument is from 90 to 65535. The default value is 300.

Command Default

OER uses the following default value if this command is not configured or if the no form of this command is entered:

timer : 300 seconds

Command Modes

OER map configuration (config-oer-map)

Command History

Release

Modification

12.3(8)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

Usage Guidelines

The set holddown command is entered on a master controller in OER map configuration mode. This command is used to configure the prefix route dampening timer for the minimum period of time in which a new exit must be used before an alternate exit can be selected. The master controller puts a prefix in a holddown state during an exit change to isolate the prefix during the transition period, preventing the prefix from flapping because of rapid state changes. OER does not implement policy changes while a prefix is in the holddown state. A prefix will remain in a holddown state for the default or configured time period. When the holddown timer expires, OER will select the best exit based on performance and policy configuration. However, an immediate route change will be triggered if the current exit for a prefix becomes unreachable.

Configuring a new timer value will immediately replace the existing value if the new value is less than the time remaining. If the new value is greater than the time remaining, the new timer value will be used when the existing timer is reset.

Examples

The following example creates an OER map named HOLDDOWN that sets the holddown timer to 120 seconds for traffic from the prefix list named CUSTOMER:

Router(config)# oer-map HOLDDOWN 10 
Router(config-oer-map)# match ip address prefix-list CUSTOMER 
Router(config-oer-map)# set holddown 120 

Related Commands

Command

Description

holddown

Configures the prefix route dampening timer to set the minimum period of time that a new exit must be used before an alternate exit can be selected.

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

oer-map

Enters OER map configuration mode to configure an OER map to apply policies to selected IP prefixes.

set interface (OER)

To configure an Optimized Edge Routing (OER) map to send packets that match prefixes in an access list on OER border routers to the null interface, use the set interface command in OER map configuration mode. To delete the set clause entry, use the no form of this command.

set interface null0
no set interface null0

Syntax Description

null0

Specifies that packets will be sent to the null interface, which means that the packets are discarded.

Command Default

No packets are send to the null interface.

Command Modes

OER map configuration

Command History

Release

Modification

12.4(6)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

Usage Guidelines

The set interface command is entered on a master controller in OER map configuration mode. This command can be used for OER black hole filtering if the border routers detect a denial-of-service (DoS) attack by directing packets to the null interface. The null interface is a virtual network interface that is similar to the loopback interface. Whereas traffic to the loopback interface is directed to the router itself, traffic sent to the null interface is discarded. This interface is always up and can never forward or receive traffic; encapsulation always fails. The null interface functions similarly to the null devices available on most operating systems. Null interfaces are used as a low-overhead method of discarding unnecessary network traffic.

Examples

The following example shows how to configure an OER map named BLACK_HOLE_MAP that directs packets to the null interface. To use this configuration for a DoS attack, leave the access list empty until an attack is detected and add the prefix or prefixes that are determined to be the source of the attack. Subsequent packets received from the specified prefix or prefixes will be discarded.

Router(config)# oer-map black-hole-map 10
Router(config-oer-map)# match ip address access-list black-hole-list
Router(config-oer-map)# set interface null0

Related Commands

Command

Description

oer-map

Enters OER map configuration mode to configure an OER map to apply policies to selected IP prefixes.

set next-hop (OER)

Configures an OER map to send packets that match prefixes in an access list on OER border routers to the specified next hop.

set jitter

To configure an Optimized Edge Routing (OER) map to set the maximum jitter value that OER will permit for an exit link, use the set jitter command in OER map configuration mode. To delete the set clause entry, use the no form of this command.

set jitter threshold maximum
no set jitter threshold maximum

Syntax Description

threshold

Specifies a maximum absolute threshold value for jitter. Jitter is a measure of voice quality.

maximum

Number (in milliseconds) in the range from 1 to 1000, where 1 represents the highest voice quality, and 1000 represents the lowest voice quality. The default value is 30.

Command Default

No jitter values are specified.

Command Modes

OER map configuration

Command History

Release

Modification

12.4(6)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

Usage Guidelines

The set jitter command is entered on a master controller in OER map configuration mode. This command is used to specify the maximum tolerable jitter value permitted on an exit link. Jitter is a measure of voice quality where the lower the jitter value, the higher the voice quality. If the jitter value is greater than the user-defined or the default value, OER determines that the exit link is out-of-policy and searches for an alternate exit link.

Another measure of voice quality is the estimated Mean Opinion Score (MOS). Use the set mos command and the set jitter command in an OER map to define voice quality.

Examples

The following example shows how to configure an OER map named JITTER that sets the threshold jitter value. If the jitter threshold value exceeds 20 milliseconds, the master controller searches for a new exit link.

Router(config)# oer-map JITTER 10
Router(config-oer-map)# set jitter threshold 20

Related Commands

Command

Description

jitter

Specifies the threshold jitter value that OER will permit for an exit link.

oer-map

Enters OER map configuration mode to configure an OER map to apply policies to selected IP prefixes.

set mos

Configures an OER map to specify the threshold and percentage Mean Opinion Score (MOS) values that OER will permit for an exit link.

set link-group

To specify a link group for traffic classes defined in an Optimized Edge Routing (OER) policy, use the set link-group command in OER map configuration mode. To delete the set clause entry, use the no form of this command.

set link-group link-group-name [ fallback link-group-name ]
no set link-group link-group-name

Syntax Description

link-group-name

Name of link group.

fallback

(Optional) Specifies a fallback link group to be used if the primary link group is out-of-policy (OOP).

Command Default

No link groups are specified for a traffic class.

Command Modes

OER map configuration (config-oer-map)

Command History

Release

Modification

12.4(15)T

This command was introduced.

Usage Guidelines

The set link-group command is entered on a master controller in OER map configuration mode. This command is used to define a link group for the traffic class matched in an OER map.

Introduced in Cisco IOS Release 12.4(15)T, link groups are used to define a group of exit links as a preferred set of links or a fallback set of links for OER to use when optimizing traffic classes specified in an OER policy. Up to three link groups can be specified for each interface. Use the link-group command to define the link group for an interface and use the set link-group command to define the primary link group and a fallback link group for a specified traffic class in an OER map.

Use the show oer master link-group command to view information about configured OER link groups.

Examples

The following example shows how to configure an OER map named link_video_map that configures OER to create a traffic class that matches an access list named video_list. The traffic class is configured to use a link group named video as the primary link group, and a fallback group named voice. The video link group may be a set of high bandwidth links that are preferred for video traffic.

Router(config)# oer-map link_video_map 10
Router(config-oer-map)# match ip address access-list video_list
Router(config-oer-map)# set link-group video fallback voice

Related Commands

Command

Description

link-group

Configures an OER border router exit interface as a member of a link group.

oer-map

Enters OER map configuration mode to configure an OER map to apply policies to selected IP prefixes.

show oer master link-group

Displays information about OER link groups.

set loss

To configure an OER map to set the relative or maximum packet loss limit that OER will permit for an exit link, use the set losscommand in OER map configuration mode. To delete the set clause entry, use the no form of this command.

set loss { relative average | threshold maximum }
no set loss

Syntax Description

relative average

Sets a relative percentage of packet loss based on a comparison of short-term and long-term packet loss percentages. The range of values that can be configured for this argument is a number from 1 to 1000. Each increment represents one tenth of a percent.

threshold maximum

Sets absolute packet loss based on packets per million (PPM). The range of values that can be configured for this argument is from 1 to 1000000.

Command Default

OER uses the following default value if this command is not configured or if the no form of this command is entered:

relative average : 100 (10 percent)

Command Modes

OER map configuration

Command History

Release

Modification

12.3(8)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

Usage Guidelines

The set loss command is entered on a master controller in OER map configuration mode. This command is used to configure an OER map to set the relative percentage or maximum number of packets that OER will permit to be lost during transmission on an exit link. If packet loss is greater than the user-defined or the default value, OER determines that the exit link is out-of-policy and searches for an alternate exit link.

The relative keyword is used to configure the relative packet loss percentage. The relative packet loss percentage is based on a comparison of short-term and long-term packet loss. The short-term measurement reflects the percentage of packet loss within a 5-minute period. The long-term measurement reflects the percentage of packet loss within a 60-minute period. The following formula is used to calculate this value:

Relative packet loss = ((short-term loss - long-term loss) / long-term loss) * 100

The master controller measures the difference between these two values as a percentage. If the percentage exceeds the user-defined or default value, the exit link is determined to be out-of-policy. For example, if long-term packet loss is 200 PPM and short-term packet loss is 300 PPM, the relative loss percentage is 50 percent.

The threshold keyword is used to configure the absolute maximum packet loss. The maximum value is based on the actual number of PPM that have been lost.

Examples

The following example creates an OER map named LOSS that sets the relative percentage of acceptable packet loss for traffic from the prefix list named CUSTOMER to a 20 percent relative percentage. If the packet loss on the current exit link exceeds 20 percent, the master controller will search for a new exit.

Router(config)# oer-map LOSS 10 
Router(config-oer-map)# match ip address prefix-list CUSTOMER 
Router(config-oer-map)# set loss relative 200
 

Related Commands

Command

Description

loss

Sets the relative or maximum packet loss limit that OER will permit for an exit link.

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

oer-map

Enters OER map configuration mode to configure an OER map to apply policies to selected IP prefixes.

set mode

To configure an Optimized Edge Routing (OER) map to configure route monitoring, route control, or exit selection for matched traffic, use the set mode command in OER map configuration mode. To delete the set clause entry, use the no form of this command.

set mode { monitor { active [ throughput] | both | fast | passive } | route { control | observe } | select-exit { best | good } }
no set mode { monitor | route { control | observe } | select-exit }

Syntax Description

monitor

Enables the configuration of OER monitoring settings.

active

Enables active monitoring.

throughput

(Optional) Enables active monitoring with throughput data from passive monitoring.

both

Enables both active and passive monitoring.

fast

Enables continuous active monitoring and passive monitoring.

passive

Enables passive monitoring.

route

Enables the configuration of OER route control policy settings.

control

Enables automatic route control.

observe

Configures OER to passively monitor and report without making any changes.

select-exit

Enables the exit selection based on performance or policy.

best

Configures OER to select the best available exit based on performance or policy.

good

Configures OER to select the first exit that is in-policy.

Command Default

OER uses the following default settings if this command is not configured or if the no form of this command is entered:

Monitoring: Both active and passive monitoring is enabled. Route control: Observe mode route control is enabled. Exit Selection: The first in-policy exit is selected.

Command Modes

OER map configuration

Command History

Release

Modification

12.3(8)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

12.4(15)T

The fast and throughput keywords were added.

Usage Guidelines

The set mode command is entered on a master controller in OER map configuration mode. This command is used to configure an OER map to enable and configure control mode and observe mode settings, passive monitoring and active monitoring, and exit link selection for traffic that is configured as match criteria.

Observe Mode

Observe mode monitoring is enabled by default. In observe mode, the master controller monitors prefixes and exit links based on default and user-defined policies and then reports the status of the network and the decisions that should be made but does not implement any changes. This mode allows you to verify the effectiveness of this feature before it is actively deployed.

Control Mode

In control mode, the master controller coordinates information from the border routers and makes policy decisions just as it does in observe mode. The master controller monitors prefixes and exits based on default and user-defined policies but then implements changes to optimize prefixes and to select the best exit. In this mode, the master controller gathers performance statistics from the border routers and then transmits commands to the border routers to alter routing as necessary in the OER managed network.

Passive Monitoring

The master controller passively monitors IP prefixes and TCP traffic flows. Passive monitoring is configured on the master controller. Monitoring statistics are gathered on the border routers and then reported back to the master controller. OER uses NetFlow to collect and aggregate passive monitoring statistics on a per prefix basis. No explicit NetFlow configuration is required. NetFlow support is enabled by default when passive monitoring is enabled. OER uses passive monitoring to measure the following information:

Delay --OER measures the average delay of TCP flows for a prefix. Delay is the measurement of the time between the transmission of a TCP synchronization message and receipt of the TCP acknowledgement.

Packet Loss --OER measures packet loss by tracking TCP sequence numbers for each TCP flow. OER estimates packet loss by tracking the highest TCP sequence number. If a subsequent packet is received with a lower sequence number, OER increments the packet loss counter.

Reachability --OER measures reachability by tracking TCP synchronization messages that have been sent repeatedly without receiving a TCP acknowledgement.

Throughput --OER measures outbound throughput for optimized prefixes. Throughput is measured in bits per second (bps).


Note


OER passively monitors TCP traffic flows for IP traffic. Passive monitoring of non-TCP sessions is not supported.

Active Monitoring

OER uses Cisco IOS IP Service Level Agreements (SLAs) to enable active monitoring. IP SLAs support is enabled by default. IP SLAs support allows OER to be configured to send active probes to target IP addresses to measure the jitter and delay, determining if a prefix is out-of-policy and if the best exit is selected. The border router collects these performance statistics from the active probe and transmits this information to the master controller. The master controller uses this information to optimize the prefix and select the best available exit based on default and user-defined policies. The active-probe command is used to create an active probe.

In Cisco IOS Release 12.4(15)T the throughput keyword was added to enable the throughput data from passive mode monitoring to be considered when optimizing UDP traffic for both performance and load-balancing. UDP traffic can be optimized only for performance (for example, delay, jitter, and loss) when active monitoring data is available. To enable load-balancing of UDP traffic, throughput data from passive monitoring is required.

Fast Failover Monitoring

In Cisco IOS Release 12.4(15)T, a new monitoring mode, fast monitoring, was introduced. Fast monitoring sets the active probes to continuously monitor all the exits (probe-all), and passive monitoring is enabled too. Fast failover monitoring can be used with all types of active probes: ICMP echo, Jitter, TCP connection, and UDP echo. When the mode monitor fast command is enabled, the probe frequency can be set to a lower frequency than for other monitoring modes, to allow a faster failover ability. Under fast monitoring with a lower probe frequency, route changes can be performed within 3 seconds of an out-of-policy situation. When an exit becomes OOP under fast monitoring, the select best exit is operational and the routes from the OOP exit are moved to the best in-policy exit. Fast monitoring is a very aggressive mode that incurs a lot of overhead with the continuous probing. We recommend that you use fast monitoring only for performance sensitive traffic.

Optimal Exit Link Selection

The master controller can be configured to select a new exit for an out-of-policy prefix based on performance or policy. You can configure the master controller to select the first in-policy exit by entering the good keyword, or you can configure the master controller to select the best exit with the best keyword. If the good keyword is used and there is no in-policy exit, the prefix is uncontrolled.

Examples

The following example creates an OER map named OBSERVE that configures OER to observe and report but not control traffic from the prefix list named CUSTOMER:

Router(config)# oer-map OBSERVE 80
 
Router(config-oer-map)# match ip address prefix-list CUSTOMER 
Router(config-oer-map)# set mode route observe 

Related Commands

Command

Description

mode (OER)

Configures route monitoring or route control on an OER master controller

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

oer-map

Enters OER map configuration mode to configure an OER map to apply policies to selected IP prefixes.

set mos

To configure an Optimized Edge Routing (OER) map to set the threshold and percentage Mean Opinion Score (MOS) values that OER) will permit for an exit link, use the set mos command in OER map configuration mode. To reset the threshold MOS values to their default value, use the no form of this command.

set mos threshold minimum percentage percent
no set mos threshold minimum percentage percent

Syntax Description

threshold

Specifies a threshold MOS value that represents a minimum voice quality for exit link utilization.

minimum

Number (to two decimal places) in the range from 1.00 to 5.00. The number 1.00 represents the lowest voice quality, and the number 5.00 represents the highest voice quality. The default MOS value is 3.60.

percentage

Specifies a percentage value that is compared with the percentage of MOS samples that are below the MOS threshold.

percent

Number, as a percentage.

Command Default

The default MOS value is 3.60.

Command Modes

OER map configuration

Command History

Release

Modification

12.4(6)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

Usage Guidelines

The set mos command is entered on a master controller in OER map configuration mode and used to determine voice quality. The number of MOS samples over a period of time that are below the threshold MOS value are calculated. If the percentage of MOS samples below the threshold is greater than the configured percentage, OER determines that the exit link is out-of-policy and searches for an alternate exit link.

Another measure of voice quality is the jitter value. Use the set mos command and the set jitter command in an OER map to define voice quality.

Examples

The following example creates an OER map named MOS that configures the master controller to search for a new exit link if more than 30 percent of the MOS samples are below the MOS threshold of 3.80.

Router(config)# oer-map MOS 10
 
Router(config-oer-map)# match ip address prefix-list LIST1
Router(config-oer-map)# set mos threshold 3.80 percent 30

Related Commands

Command

Description

mos

Configures the maximum mos value that OER will permit for an exit link.

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

oer-map

Enters OER map configuration mode to configure an OER map to apply policies to selected IP prefixes.

set next-hop (OER)

To configure an Optimized Edge Routing (OER) map to send packets that match prefixes in an access list on OER border routers to the specified next hop, use the set next-hop command in OER map configuration mode. To delete the set clause entry, use the no form of this command.

set next-hop ip-address
no set next-hop ip-address

Syntax Description

ip-address

IP address of the next hop to which the packets will be sent.

Command Default

No packets are sent to the next hop.

Command Modes

OER map configuration

Command History

Release

Modification

12.4(6)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

Usage Guidelines

This command can be used for OER sinkhole filtering if the border routers detect a denial-of-service (DoS) attack by directing packets to the specified next hop. The packets may be saved, analyzed, or discarded at the next hop.

Examples

The following example shows how to configure an OER map named SINKHOLE_MAP that directs packets to the specified next hop. Use this configuration in preparation for a DoS attack, leave the access list empty until an attack is detected and add the prefix or prefixes that are determined to be the source of the attack. Subsequent packets received from the specified prefix or prefixes will be sent to the specified next hop.

Router(config)# oer-map SINKHOLE_MAP 10
Router(config-oer-map)# match ip address access-list SINKHOLE-LIST
Router(config-oer-map)# set next-hop 10.20.24.3

Related Commands

Command

Description

oer-map

Enters OER map configuration mode to configure an OER map to apply policies to selected IP prefixes.

set interface

Configures an OER map to send packets that match prefixes in an access list on OER border routers to the null interface.

set periodic

To configure an Optimized Edge Routing (OER) map to set the time period for the periodic timer, use the set periodic command in OER map configuration mode. To delete the set clause entry, use the no form of this command.

set periodic timer
no set periodic

Syntax Description

timer

Length of time set for the periodic timer, in seconds. The value for the timer argument is from 180 to 7200.

Command Default

No default behavior or values

Command Modes

OER map configuration

Command History

Release

Modification

12.3(8)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

Usage Guidelines

The set periodiccommand is entered on a master controller in OER map configuration mode. This command is used to configure an OER map to configure OER to periodically select the best exit based on the periodic timer value for traffic that is configured as match criteria in an OER map. When this timer expires, OER will automatically select the best exit, regardless if the current exit is in-policy or out-of-policy. The periodic timer is reset when the new exit is selected.

Examples

The following example creates an OER map named PERIODIC that sets the periodic timer to 300 seconds for traffic from the prefix list named CUSTOMER. When the timer expires, OER will select the best exit.

Router(config)# oer-map PERIODIC 80
 
Router(config-oer-map)# match ip address prefix-list CUSTOMER 
Router(config-oer-map)# set periodic 300 

Related Commands

Command

Description

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

oer-map

Enters OER map configuration mode to configure an OER map to apply policies to selected IP prefixes.

periodic (OER)

Configures OER to periodically select the best exit.

set probe

To set the frequency of an Optimized Edge Routing (OER) active probe, use the set probe command in OER map configuration mode. To reset the frequency of an OER active probe to its default value, use the no form of this command.

set probe { frequency seconds | packets packet-count }
no set probe { frequency seconds | packets packet-count }

Syntax Description

frequency

Sets the frequency of an active probe.

seconds

Number of seconds in the range from 4 to 60. The default is 60.

packets

Specifies the number of probe packets for a jitter probe.

packet-count

Number of probe packets in the range from 1 to 255. The default is 100.

Command Default

The default active probe frequency is 60 seconds.

The default number of packets probe is 100.

Command Modes

OER map configuration (config-oer-map)

Command History

Release

Modification

12.4(6)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

12.4(15)T

The minimum number of seconds was lowered from 4 seconds to 2 second to support the fast failover monitoring mode.

12.4(24)T

This command was modified. The packets keyword and the packet-count argument were added.

Usage Guidelines

The set probe command is entered on a master controller in OER map configuration mode. This command is used within an OER map configuration to set the frequency of the active probes. Unless the default frequency of 60 seconds is used, configuring the set probe command will increase the frequency of the probes. Increased probe frequency results in a lower response time of OER. The frequency can be increased for a number of policies, but if all active probes are set to an increased frequency, an Intrusion Detection Service (IDS) may be triggered.

In Cisco IOS Release 12.4(15)T, a new monitoring mode, fast monitoring, was introduced. Fast monitoring sets the active probes to continuously monitor all the exits (probe-all), and passive monitoring is enabled too. Fast failover monitoring can be used with all types of active probes: ICMP echo, Jitter, TCP connection, and UDP echo. When the set mode monitor fast command is enabled, the probe frequency can be set to a lower frequency than for other monitoring modes, to allow a faster failover ability. The minimum number of seconds was lowered from 4 seconds to 2 second to support the fast failover monitoring mode. Under fast monitoring with a lower probe frequency, route changes can be performed within 3 seconds of an out-of-policy situation.

n Cisco IOS Release 12.4(24)T, the ability to configure the number of probe packets for jitter probes was introduced. Using the packets keyword and the packet-count argument the number of packets per jitter probe can be set. The new keyword is supported under OER map configuration mode only, not at a global level. The new keyword applies only to jitter probes and the configuration affects global probes and forced probes for all traffic classes.

Examples

The following example shows how to set the frequency of an active probe to be 10 seconds using an OER map named PROBE:

Router(config)# oer-map PROBE 10
Router(config-oer-map)# set probe frequency 10

The following example shows how to set the frequency of an active probe to be 2 seconds using an OER map named FAST after the fast failover monitoring mode is enabled:

Router(config)# oer-map FAST 10
Router(config-oer-map)# set mode monitor fast
Router(config-oer-map)# set probe frequency 2

The following example shows how to set the number of probe packets for a jitter probe at 33 packets using an OER map named JITTER:

Router(config)# oer-map JITTER 
Router(config-oer-map)# set probe packets 33

Related Commands

Command

Description

active-probe

Configures an OER active probe for a target prefix.

set mode (OER)

Configures an OER map to configure route monitoring, route control, or exit selection for matched traffic.

oer-map

Enters OER map configuration mode to configure an OER map to apply policies to selected IP prefixes.

set resolve

To configure an OER map to set policy priority for overlapping policies, use the set resolve command in OER map configuration mode. To delete the set clause entry, use the no form of this command.

set resolve { cost priority value | delay priority value variance percentage | jitter priority value variance percentage | loss priority value variance percentage | mos priority value variance percentage | range priority value | utilization priority value variance percentage }
no set resolve { cost | delay | jitter | loss | mos | range | utilization }

Syntax Description

cost

Specifies policy priority settings for cost optimization.

delay

Specifies policy priority settings for packet delay.

jitter

Specifies policy priority settings for jitter.

loss

Specifies policy priority settings for packet loss.

mos

Specifies policy priority settings for Mean Opinion Score (MOS).

range

Specifies policy priority settings for range.

utilization

Specifies policy priority settings for exit link utilization.

priority value

Sets the priority of the policy. The configurable range for this argument is from 1 to 10. The number 1 has the highest priority, and the number 10 has the lowest priority.

variance percentage

Sets the allowable variance for the policy, as a percentage. The configurable range of this argument is from 1 to 100.

Command Default

None

Command Modes

OER map configuration

Command History

Release

Modification

12.3(8)T

This command was introduced.

12.4(6)T

The jitter and mos keywords were added.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

Usage Guidelines

The set resolvecommand is entered on a master controller in OER map configuration mode. This command is used to set priority when multiple policies are configured for the same prefix. When this command is configured, the policy with the highest priority will be selected to determine the policy decision.

The priority keyword is used to specify the priority value. The number 1 assigns the highest priority to the policy. The number 10 sets the lowest priority. Each policy must be assigned a different priority number. If you try to assign the same priority number to two different policy types, an error message will be displayed on the console.

The variance keyword is used to set an allowable variance for a user-defined policy. This keyword configures the allowable percentage that an exit link or prefix can vary from the user-defined policy value and still be considered equivalent. For example, if exit link delay is set to 80 percent and a 10 percent variance is configured, exit links that delay values from 80 to 89 percent will be considered equal.


Note


Variance cannot be set for cost or range policies.

Examples

The following example creates an OER map named RESOLVE that sets the priority for delay policies to 1 for traffic learned based on highest outbound throughput. The variance is set to allow a 10 percent difference in delay statistics before a prefix is determined to be out-of-policy.

Router(config)# oer-map RESOLVE 10
 
Router(config-oer-map)# match oer learn throughput 
Router(config-oer-map)# set resolve delay priority 1 variance 10 

Related Commands

Command

Description

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

oer-map

Enters OER map configuration mode to configure an OER map to apply policies to selected IP prefixes.

resolve

Sets the priority of a policy when multiple overlapping policies are configured.

set traceroute reporting

To configure an Optimized Edge Routing (OER) map to enable traceroute reporting, use the set traceroute reporting command in OER map configuration mode. To delete the set clause entry, use the no form of this command.

set traceroute reporting [ policy { delay | loss | unreachable } ]
no set traceroute reporting [ policy { delay | loss | unreachable } ]

Syntax Description

policy

(Optional) Configures policy-based traceroute reporting.

delay

(Optional) Configures traceroute reporting based on delay policies.

loss

(Optional) Configures traceroute reporting based on packet loss policies.

unreachable

(Optional) Configures traceroute reporting based on reachability policies.

Command Default

Traceroute reporting is not enabled using an OER map.

Command Modes

OER map configuration

Command History

Release

Modification

12.3(14)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

Usage Guidelines

The set traceroute reporting command is entered on a master controller in OER map configuration mode. This command is used to enable continuous and policy-based traceroute probing. Traceroute probing allows you to monitor prefix performance on a hop-by-hop basis. Delay, loss, and reachability measurements are gathered for each hop from the probe source to the target prefix.

The following types of traceroute reporting are configured with this command:

Continuous --A traceroute probe is triggered for each new probe cycle. Entering this command without any keywords enables continuous reporting. The probe is sourced from the current exit of the prefix.

Policy based --A traceroute probe is triggered automatically when a prefix goes into an out-of-policy state. Entering this command with the policy keyword enables policy based traceroute reporting. Policy based traceroute probes are configured individually for delay, loss, and reachability policies. The monitored prefix is sourced from a match clause in an OER map. Policy based traceroute reporting stops when the prefix returns to an in-policy state.

The show oer master prefix command is used to display traceroute probe results. An on-demand traceroute probe can be initiated when entering the show oer master prefix command with the current and now keywords. The set traceroute reporting command does not have to be configured to initiate an on-demand traceroute probe.

Examples

The following example, starting in global configuration mode, enables continuous traceroute probing for prefixes that are learned based on delay:

Router(config)# oer-map TRACE 10 
Router(config-oer-map)# match oer learn delay
 
Router(config-oer-map)# set traceroute reporting 

Related Commands

Command

Description

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

oer-map

Enters OER map configuration mode to configure an OER map to apply policies to selected IP prefixes.

show oer master prefix

Displays the status of monitored prefixes.

traceroute probe-delay

Sets the time interval between traceroute probe cycles.

set unreachable

To configure an OER map to set the maximum number of unreachable hosts, use the set unreachable command in OER map configuration mode. To delete the set clause entry, use the no form of this command.

set unreachable { relative average | threshold maximum }
no set unreachable

Syntax Description

relative average

Sets a relative percentage of unreachable hosts based on a comparison of short-term and long-term percentages. The range of values that can be configured for this argument is a number from 1 to a 1000. Each increment represents one tenth of a percent.

threshold maximum

Sets the absolute maximum number of unreachable hosts based on flows per million (fpm). The range of values that can be configured for this argument is from 1 to 1000000.

Command Default

OER uses the following default value if this command is not configured or if the no form of this command is entered:

relative average : 50 (5 percent)

Command Modes

OER map configuration

Command History

Release

Modification

12.3(8)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

Usage Guidelines

The set unreachable command is entered on a master controller in OER map configuration mode. This command is used to set the relative percentage or the absolute maximum number of unreachable hosts, based on flows per million, that OER will permit from an OER managed exit link. If the absolute number or relative percentage of unreachable hosts is greater than the user-defined or the default value, OER determines that the exit link is out-of-policy and searches for an alternate exit link.

The relative keyword is used to configure the relative percentage of unreachable hosts. The relative unreachable host percentage is based on a comparison of short-term and long-term measurements. The short-term measurement reflects the percentage of hosts that are unreachable within a 5-minute period. The long-term measurement reflects the percentage of unreachable hosts within a 60 minute period. The following formula is used to calculate this value:

Relative percentage of unreachable hosts = ((short-term percentage - long-term percentage) / long-term percentage) * 100

The master controller measures the difference between these two values as a percentage. If the percentage exceeds the user-defined or default value, the exit link is determined to be out-of-policy. For example, if 10 hosts are unreachable during the long-term measurement and 12 hosts are unreachable during short-term measurement, the relative percentage of unreachable hosts is 20 percent.

The threshold keyword is used to configure the absolute maximum number of unreachable hosts. The maximum value is based on the actual number of hosts that are unreachable based on fpm.

Examples

The following example creates an OER map named UNREACHABLE that configures the master controller to search for a new exit link when the difference between long and short term measurements (relative percentage) is greater than 10 percent for traffic learned based on highest delay:

Router(config)# oer-map UNREACHABLE 10
 
Router(config-oer-map)# match oer learn delay
 
Router(config-oer-map)# set unreachable relative 100
 

Related Commands

Command

Description

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

oer-map

Enters OER map configuration mode to configure an OER map to apply policies to selected IP prefixes.

show oer api client


Note


Effective with Cisco IOS Release 15.0(1)SY, the show oer api client command is hidden. Although this command is still available in Cisco IOS software, the CLI interactive Help does not display it if you attempt to view it by entering a question mark at the command line. This command will be completely removed in a future release.

Note


Effective with Cisco IOS Release 12.4(15)T, the show oer api client command is replaced by the show oer api providercommand. See the show oer api provider command for more information.

To display information about Optimized Edge Routing (OER) application interface clients, use the show oer api client command in privileged EXEC mode.

show oer api client [ detail]

Syntax Description

detail

(Optional) Displays detailed prefix information about the specified prefix or all prefixes.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.4(6)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

12.4(15)T

The show oer api client command is replaced by the show oer api provider command.

12.2SX

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

15.0(1)SY

This command was modified. This command was hidden.

Usage Guidelines

The show oer api client command is entered on a master controller. This command is used to display the number of prefixes added by the application interface client, the sequence numbers of policies added by the application interface client, and the client ID. The detail keyword is used to display more detailed information about the application interface client.

Cisco IOS Release 12.4(15)T

In Cisco IOS Release 12.4(15)T and later releases, the show oer api client command is replaced by the show oer api provider command. The show oer api client command is currently supported for backwards compatibility, but support may be removed in a future Cisco IOS software release.

Examples

The following example shows the status of a monitored prefix:

Router# show oer api client
OER Prefix Stats:
  Dly: Delay in ms
  EBw: Egress Bandwidth
  IBw: Ingress Bandwidth
Prefix      State     Curr BR   CurrI/F  Dly   EBw   IBw
----------------------------------------------------------
10.1.5.0/24 INPOLICY  10.1.1.2  Et1/0     19     1     1 

The table below describes the significant fields shown in the display.

Table 1 show oer api client Field Descriptions

Field

Description

Prefix

IP address and prefix length.

State

Status of the prefix.

Curr BR

Border router from which these statistics were gathered.

Curr I/F

Current exit link interface on the border router.

Dly

Delay in milliseconds.

EBw

Egress bandwidth.

IBw

Ingress bandwidth.

The following output shows the detailed status of a monitored prefix:

Router# show oer api client detail
 
Prefix: 10.1.1.0/26 
   State: DEFAULT*      Time Remaining: @7 
   Policy: Default 
   Most recent data per exit 
   Border          Interface           PasSDly  PasLDly  ActSDly  ActLDly 
  *10.2.1.1        Et1/0                   181      181      250      250 
   10.2.1.2        Et2/0                     0        0      351      351 
   10.3.1.2        Et3/0                     0        0       94      943 
   Latest Active Stats on Current Exit:
   Type     Target          TPort Attem Comps      DSum     Min     Max     Dly
   echo     10.1.1.1            N     2     2       448     208     240     224
   echo     10.1.1.2            N     2     2       488     228     260     244
   echo     10.1.1.3            N     2     2       568     268     300     284
Prefix performance history records
 Current index 2, S_avg interval(min) 5, L_avg interval(min) 60
Age       Border          Interface       OOP/RteChg Reasons 
Pas: DSum  Samples  DAvg  PktLoss Unreach    Ebytes    Ibytes      Pkts   Flows
Act: Dsum Attempts  DAvg    Comps Unreach
00:00:03  10.1.1.1        Et1/0
        0        0     0        0       0         0         0         0       0
     1504        6   250        6       0

The table below describes the significant fields shown in the display.

Table 2 show oer api client detail Field Descriptions

Field

Description

Prefix

IP address and prefix length.

State

Status of the prefix.

Time Remaining

Time remaining in the current prefix learning cycle.

Policy

The state that the prefix is in. Possible values are Default, In-policy, Out-of-policy, Choose, and Holddown.

Most recent data per exit

Border router exit link statistics for the specified prefix. The asterisk (*) character indicates the exit that is being used.

Latest Active Stats on Current Exit

Active probe statistics. This field includes information about the probe type, target IP address, port number, and delay statistics.

Type

The type of active probe. Possible types are ICMP echo, TCP connect, or UDP echo. The example uses default ICMP echo probes (default TCP), so no port number is displayed.

Prefix performance history records

Displays border router historical statistics. These statistics are updated about once a minute and stored for 1 hour.

Related Commands

Command

Description

api client

Configures an OER application interface client.

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

show oer api provider

To display information about application interface providers registered with Optimized Edge Routing (OER), use the show oer api provider command in privileged EXEC mode.

show oer api provider [ detail]

Syntax Description

detail

(Optional) Displays detailed information about application interface providers.

Command Default

Detailed information about API providers is not displayed.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.4(15)T

This command was introduced.

Usage Guidelines

The show oer api provider command is entered on a master controller. This command is used to display application interface provider and host information including the ID of each configured provider, the priority of the provider and the host (if configured), and the IP addresses of each configured host device. The detailkeyword is used to display more detailed information.

The OER application interface defines the mode of communication and messaging between applications and the network for the purpose of optimizing the traffic associated with the applications. A provider is defined as an entity outside the network in which the router configured as an OER master controller exists, for example, an ISP, or a branch office of the same company. The provider has one or more host devices running one or more applications that use the OER application interface to communicate with an OER master controller. A provider must be registered with an OER master controller before an application on a host device can interface with OER. Use the api provider command to register the provider, and use the host-addresscommand to configure a host device. After registration, a host device in the provider network can initiate a session with an OER master controller. The OER application interface provides an automated method for networks to be aware of applications and provides application-aware performance routing.

Examples

The following example shows information about configured application interface providers and host devices:

Router# show oer api provider
API Version: Major 2, Minor 0
  Provider id 1, priority 4000
   Host ip 172.17.1.1, priority 4001
   Host ip 10.1.2.2, priority 3001
  Provider id 2, priority 20
  Provider id 3, priority 10

The table below describes the significant fields shown in the display.

Table 3 show oer api provider Field Descriptions

Field

Description

API Version, Major, Minor

Version number of the application interface with major and minor releases.

Provider id

ID number of an application interface provider.

priority

The priority assigned to the policies of a provider or of a host

Host ip

IP address of a host device.

The following example shows detailed information about configured application interface providers and host devices:

Router# show oer api provider detail
API Version: Major 2, Minor 0
  Provider id 1001, priority 65535
   Host ip 10.3.3.3, priority 65535
    Session id 9, Version Major 2, Minor 0
    Num pfx created 2, Num policies created 2
    Last active connection time (sec) 00:00:01
    Policy ids : 101, 102,
   Host ip 10.3.3.4, priority 65535
    Session id 10, Version Major 2, Minor 0
    Num pfx created 1, Num policies created 1
    Last active connection time (sec) 00:00:03
    Policy ids : 103,
  Provider id 2001, priority 65535
   Host ip 172.19.198.57, priority 65535
    Session id 11, Version Major 2, Minor 0
    Num pfx created 0, Num policies created 0
    All Prefix report enabled
    All exit report enabled

The table below describes the significant fields shown in the display that are different from the table above.

Table 4 show oer api provider detail Field Descriptions

Field

Description

Session id

Session ID automatically allocated by OER when an application interface provider initiates a session.

Num pfx

Number of traffic classes created by the application interface provider application.

Num policies created

Number of policies dynamically created by the application interface provider application.

Last active connection time

Time, in seconds, since the last active connection from the application interface provider.

Policy ids

IDs assigned to each policy dynamically created by the application interface provider application.

All Prefix report enabled

Traffic class reports from the OER master controller are enabled for the application interface provider.

All exit report enabled

Exit link reports from the OER master controller are enabled for the application interface provider.

Related Commands

Command

Description

api provider

Registers an application interface provider with an OER master controller and enters OER master controller application interface provider configuration mode.

debug oer api provider

Displays OER application interface debugging information.

host-address

Configures information about a host device used by an application interface provider to communicate with an OER master controller.

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

show oer border


Note


Effective with Cisco IOS Release 15.0(1)SY, the show oer border command is hidden. Although this command is still available in Cisco IOS software, the CLI interactive Help does not display it if you attempt to view it by entering a question mark at the command line. This command will be completely removed in a future release.

To display information about an Optimized Edge Routing (OER) border router connection and OER controlled interfaces, use the show oer border command in privileged EXEC mode.

show oer border

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.3(8)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

12.2SX

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

15.0(1)SY

This command was modified. This command was hidden.

Usage Guidelines

The show oer border command is entered on an OER border router. The output displays information about the border router, the status of the master controller connection, and border router interfaces.

Examples

The following example shows the status of a border router:

Router# show oer border
OER BR 10.1.1.3 ACTIVE, MC 10.1.1.1 UP/DOWN: UP 00:57:55,
  Auth Failures: 0
  Conn Status: SUCCESS, PORT: 3949
  Exits
  Et0/0           INTERNAL
  Et1/0           EXTERNAL

The table below describes the significant fields shown in the display.

Table 5 show oer border Field Descriptions

Field

Description

OER BR

Displays the IP address and the status of the local border router (ACTIVE or DISABLED).

MC

Displays the IP address of the master controller, the connection status (UP or DOWN), the length of time that connection with master controller has been active, and the number of authentication failures that have occurred between the border router and master controller.

Exits

Displays OER managed exit interfaces on the border router. This field displays the interface type, number, and OER status (EXTERNAL or INTERNAL).

Auth Failures

Displays the number of authentication failures.

Conn Status

Displays the connection status. This field displays "SUCCESS" or "FAILED".

PORT

Displays the TCP port number used to communicate with the master controller.

Related Commands

Command

Description

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

show oer border active-probes


Note


Effective with Cisco IOS Release 15.0(1)SY, the show oer border active-probes command is hidden. Although this command is still available in Cisco IOS software, the CLI interactive Help does not display it if you attempt to view it by entering a question mark at the command line. This command will be completely removed in a future release.

To display connection status and information about active probes on an Optimized Edge Routing (OER) border router, use the show oer border active-probescommand in privileged EXEC mode.

show oer border active-probes

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

12.2SX

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

15.0(1)SY

This command was modified. This command was hidden.

Usage Guidelines

The show oer border active-probes command is entered on a border router. This command displays the target active-probe assignment for a given prefix and the current probing status, including the border router or border routers that are executing the active probes.

Examples

The following example shows three active probes, each configured for a different prefix. The target port, source IP address, and exit interface are displayed in the output.

Router# show oer border active-probes 
        OER Border active-probes
Type      = Probe Type
Target    = Target IP Address
TPort     = Target Port
Source    = Send From Source IP Address
Interface = Exit interface
Att       = Number of Attempts
Comps   = Number of completions
N - Not applicable
Type     Target          TPort Source          Interface           Att   Comps
udp-echo 10.4.5.1           80 10.0.0.1        Et1/0                 1       0
tcp-conn 10.4.7.1           33 10.0.0.1        Et1/0                 1       0
echo     10.4.9.1            N 10.0.0.1        Et1/0                 2       2

The table below describes the significant fields shown in the display.

Table 6 show oer border active-probes Field Descriptions

Field

Description

Type

The active probe type.

Target

The target IP address.

TPort

The target port.

Source

The source IP address.

Interface

The OER managed exit interface.

ATT

The number of attempts.

Comps

The number successfully completed attempts.

Related Commands

Command

Description

active-probe

Configures active probes to monitor an OER controlled prefixes.

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

show oer border defined application

To display information about user-defined applications used in Optimized Edge Routing (OER), use the show oer border defined application command in privileged EXEC mode.

show oer border defined application

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.4(15)T

This command was introduced.

Usage Guidelines

The show oer border defined applicationcommand is entered on an OER border router. This command displays all user-defined applications that are defined on the master controller. To define a custom application to be used by OER, use the application define command on the OER master controller.

To display the same information on the OER master controller, use the show oer master defined applicationcommand.

Examples

The following partial output shows information about the user-defined application definitions configured for use with OER:

Router# show oer border defined application
OER Defined Applications:
Name                Appl_ID Dscp Prot     SrcPort     DstPort SrcPrefix         
--------------------------------------------------------------------------------
telnet                    1 defa  tcp       23-23     1-65535 0.0.0.0/0         
telnet                    1 defa  tcp     1-65535       23-23 0.0.0.0/0         
ftp                       2 defa  tcp       21-21     1-65535 0.0.0.0/0         
ftp                       2 defa  tcp     1-65535       21-21 0.0.0.0/0         
cuseeme                   4 defa  tcp   7648-7648     1-65535 0.0.0.0/0         
cuseeme                   4 defa  tcp   7649-7649     1-65535 0.0.0.0/0         
dhcp                      5 defa  udp       68-68       67-67 0.0.0.0/0         
dns                       6 defa  tcp       53-53     1-65535 0.0.0.0/0         
dns                       6 defa  tcp     1-65535       53-53 0.0.0.0/0         
dns                       6 defa  udp       53-53     1-65535 0.0.0.0/0         
dns                       6 defa  udp     1-65535       53-53 0.0.0.0/0         
finger                    7 defa  tcp       79-79     1-65535 0.0.0.0/0         
finger                    7 defa  tcp     1-65535       79-79 0.0.0.0/0         
gopher                    8 defa  tcp       70-70     1-65535 0.0.0.0/0 
.
.
.

The table below describes the significant fields shown in the display.

Table 7 show oer border defined application Field Descriptions

Field

Description

Name

Application Name

Appl_ID

Application ID

Dscp

Differentiated Services Code Point (DSCP) value

Prot

Protocol

SrcPort

Source port number for the traffic class

DstPort

Destination port number for the traffic class

SrcPrefix

IP address of the traffic class source

Related Commands

Command

Description

application define

Defines a user-defined application to be monitored by OER.

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

show oer master defined application

Displays information about user-defined application definitions used in OER.

show oer border passive applications


Note


Effective with Cisco IOS Release 15.0(1)SY, the show oer border passive applications command is hidden. Although this command is still available in Cisco IOS software, the CLI interactive Help does not display it if you attempt to view it by entering a question mark at the command line. This command will be completely removed in a future release.

To display the list of application traffic classes monitored by Optimized Edge Routing (OER), use the show oer border passive applications command in privileged EXEC mode.

show oer border passive applications

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(9)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

12.2SX

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

15.0(1)SY

This command was modified. This command was hidden.

Usage Guidelines

The show oer border passive applications command is entered on a border router. This command displays a list of application traffic classes monitored by the border router using NetFlow passive monitoring.

Examples

The following example displays an application traffic class monitored by a border router:

Router# show oer border passive applications
OER Passive monitored Appl:
 + - monitor more specific
 Prefix         /Mask  Prot  Dscp   SrcPort          DstPort         Appl_ID
10.1.3.0        /24     17     ef   [1, 65535]       [3000, 4000]     1

The table below describes the significant fields shown in the display.

Table 8 show oer border passive applications Field Descriptions

Field

Description

Prefix

IP address.

/Mask

Prefix length.

Prot

Application protocol number.

Dscp

Differentiated Services Code Point (DSCP) value.

SrcPort

Source application port number, a single port number, or a range of port numbers.

DstPort

The destination application port, a single port number, or a range of port numbers.

Appl_ID

Unique ID that identifies an application traffic class.

Related Commands

Command

Description

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

show oer border passive cache


Note


Effective with Cisco IOS Release 15.0(1)SY, the show oer border passive cache command is hidden. Although this command is still available in Cisco IOS software, the CLI interactive Help does not display it if you attempt to view it by entering a question mark at the command line. This command will be completely removed in a future release.

To display passive measurement information collected by NetFlow for Optimized Edge Routing (OER) monitored prefixes and traffic flows, use the show oer border passive cache command in privileged EXEC mode.

show oer border passive cache learned [ application | traffic-class ]

Syntax Description

learned

Displays measurement information about monitored learned prefixes.

application

(Optional) Displays measurement information about monitored learned prefixes for an application traffic class.

traffic-class

(Optional) Displays flow cache information about monitored learned prefixes for an OER traffic class.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.3(8)T

This command was introduced.

12.4(9)T

The applications and application keywords were added.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

12.4(15)T

The traffic-class keyword was added.

12.2SX

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

15.0(1)M

This command was modified. The applicationsand prefix keywords were removed.

12.2(33)SRE

This command was modified. The applicationsand prefix keywords were removed.

15.0(1)SY

This command was modified. This command was hidden.

Usage Guidelines

The show oer border passive cache command is entered on a border router. This command displays real-time prefix information collected from the border router through NetFlow passive monitoring.

Entering the learned keyword displays learned prefixes. A maximum of five host addresses and five ports are collected for each prefix. The output will also show the throughput in bytes and the delay in milliseconds. If the application keyword is entered, the output displays information about learned prefixes that match other application criteria such as Differentiated Services Code Point (DSCP) value, protocol, or port number. The traffic-class keyword when used with the learned keyword displays cache information about monitored learned prefixes for an OER traffic class.

Examples

The following example displays passive monitoring information about learned prefixes:

Router# show oer border passive cache learned
 OER Learn Cache:
    State is enabled
    Measurement type: throughput, Duration: 2 min
    Aggregation type: prefix-length, Prefix length: 24
    4096 oer-flows per chunk,
    22 chunks allocated, 32 max chunks,
    1 allocated records, 90111 free records, 8913408 bytes allocated
Prefix         Mask     Pkts  B/Pk  Delay Samples   Active
Host1          Host2          Host3          Host4          Host5
dport1         dport2         dport3         dport4         dport5
10.1.5.0        /24      17K    46    300      2     45.1
10.1.5.2       10.1.5.3       0.0.0.0        0.0.0.0        0.0.0.0
1024           80             0              0              0

The table below describes the significant fields shown in the display.

Table 9 show oer border passive cache learned Field Descriptions

Field

Description

State is...

Displays OER prefix learning status. The output displays enabled or disabled.

Measurement type

Displays how the prefix is learned. The output displays throughput, delay, or both throughput and delay.

Duration

Displays the duration of the learning period in minutes.

Aggregation type

Displays the aggregation type. The output displays BGP, non-BGP, or prefix-length.

... oer-flows per chunk

Displays number of flow records per memory chunk.

... chunks allocated

Number of memory chunks allocated.

... allocated records

Number of records currently allocated in the learn cache.

Prefix

IP address and port of the learned prefix.

Mask

The prefix length as specified in a prefix mask.

Pkts B/Pk

The number of packets and bytes per packet.

Delay Samples

The number of delay samples that NetFlow has collected.

Active

The time for which the flow has been active.

The following example uses the learned and application keywords to display measurement information about monitored application traffic classes that have been learned by OER. In this example for voice traffic, the voice application traffic is identified by the User Datagram Protocol (UDP) protocol, a DSCP value of ef, and port numbers in the range from 3000 to 4000.

Router# show oer border passive cache learned application
OER Learn Cache:
    State is enabled
    Measurement type: throughput, Duration: 2 min
    Aggregation type: prefix-length, Prefix length: 24
    4096 oer-flows per chunk,
    8 chunks allocated, 32 max chunks,
    5 allocated records, 32763 free records, 4588032 bytes allocated
Prefix         Mask     Pkts  B/Pk  Delay Samples   Active
Prot  Dscp  SrcPort          DstPort           
Host1          Host2          Host3          Host4          Host5    
dport1         dport2         dport3         dport4         dport5
10.1.3.0        /24     873     28      0      0      13.3 
17      ef [1, 65535]       [3000, 4000]   
10.1.3.1       0.0.0.0        0.0.0.0        0.0.0.0        0.0.0.0        
3500            0               0               0               0              
10.1.1.0        /24    7674     28      0      0      13.4 
17      ef [1, 65535]       [3000, 4000]   
10.1.1.1       0.0.0.0        0.0.0.0        0.0.0.0        0.0.0.0        
3600            0               0               0               0

Related Commands

Command

Description

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

show oer border passive learn


Note


Effective with Cisco IOS Release 15.0(1)SY, the show oer border passive learn command is hidden. Although this command is still available in Cisco IOS software, the CLI interactive Help does not display it if you attempt to view it by entering a question mark at the command line. This command will be completely removed in a future release.

To display the configured, learned parameters to be used with passive measurement information collected by NetFlow for Optimized Edge Routing (OER) learned traffic flows, use the show oer border passive learn command in privileged EXEC mode.

show oer border passive learn

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.4(9)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

12.2SX

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

15.0(1)SY

This command was modified. This command was hidden.

Usage Guidelines

The show oer border passive learn command is entered on a border router. This command displays configured parameters including filter and aggregate application information collected from the border router through NetFlow passive monitoring.

Examples

The following example displays passive monitoring information about learned traffic flows:

Router# show oer border passive learn
OER Border Learn Configuration :
    State is enabled
    Measurement type: throughput, Duration: 2 min
    Aggregation type: prefix-length, Prefix length: 24
    No port protocol config
 Traffic Class Filter List:
   List: SrcPrefix       SrcMask DstPrefix       DstMask
         Prot  DSCP  sport_opr sport_range    dport_opr dport_range     Grant 
      1: 0.0.0.0         0       10.1.0.0        16    
         17      ef  0         [1, 65535]      0        [1, 65535]      Permit
 Traffic Class Aggregate List:
   List: Prot  DSCP  sport_opr sport_range    dport_opr dport_range     Grant 
      1: 17      ef  0         [1, 65535]      7        [3000, 4000]    Permit
 Keys:  protocol dscp DstPort

The table below describes the significant fields shown in the display.

Table 10 show oer border passive applications Field Descriptions

Field

Description

State is

Displays OER prefix learning status. The output displays enabled or disabled.

Measurement type

Displays how the prefix is learned. The output displays either throughput or delay.

Duration

Displays the duration of the learning period in minutes.

Aggregation type

Displays the aggregation type. The output displays BGP, non-BGP, or prefix-length.

No port protocol config

Indicates that no port protocol has been configured.

Traffic Class Filter List

Section showing the traffic class filter parameters.

Traffic Class Aggregate List

Section showing the traffic class aggregation parameters.

Keys

Parameters contained in the key list.

Related Commands

Command

Description

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

show oer border passive prefixes


Note


Effective with Cisco IOS Release 15.0(1)SY, the show oer border passive prefixes command is hidden. Although this command is still available in Cisco IOS software, the CLI interactive Help does not display it if you attempt to view it by entering a question mark at the command line. This command will be completely removed in a future release.

To display information about passive monitored prefixes, use the show oer border passive prefixes command in Privileged EXEC mode.

show oer border passive prefixes

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.3(8)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

12.2SX

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

15.0(1)SY

This command was modified. This command was hidden.

Usage Guidelines

The show oer border passive prefixes command is entered on a border router. The output of this command displays prefixes monitored by NetFlow on the border router. The prefixes displayed in the output are monitored by the master controller.

Examples

The following example shows a prefix that is passively monitored by NetFlow:

Router# show oer border passive prefixes
 
OER Passive monitored prefixes:
Prefix         Mask   Match Type
10.1.5.0       /24     exact

The table below describes the significant fields shown in the display.

Table 11 show oer border passive prefixes Field Descriptions

Field

Description

Prefix

IP address of the learned prefix.

Mask

The prefix length as specified in a prefix mask.

Match Type

Type of prefix being monitored. The prefix can be exact or nonexact.

Related Commands

Command

Description

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

show oer border routes


Note


Effective with Cisco IOS Release 15.0(1)SY, the show oer border routes command is hidden. Although this command is still available in Cisco IOS software, the CLI interactive Help does not display it if you attempt to view it by entering a question mark at the command line. This command will be completely removed in a future release.

To display information about Optimized Edge Routing (OER)-controlled routes, use the show oer border routes command in privileged EXEC mode.

show oer border routes { bgp | cce | eigrp [ parent] | rwatch | static }

Syntax Description

bgp

Displays information for OER routes controlled by Border Gateway Protocol (BGP).

eigrp

Displays information for OER routes controlled by Enhanced Interior Gateway Routing Protocol (EIGRP).

parent

Displays information for EIGRP parent routes.

cce

Displays information for OER routes controlled by Common Classification Engine (CCE).

rwatch

Displays information for OER routes that are being watched in the Routing Information Base (RIB).

static

Displays information for OER routes controlled by static routes.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.3(8)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

12.2SX

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

12.4(20)T

The cce keyword was added.

12.4(24)T

The rwatch keyword was added.

15.0(1)M

This command was modified. The eigrp and parent keywords were added to support EIGRP route control.

12.2(33)SRE

This command was modified. The eigrp and parent keywords were added to support EIGRP route control.

15.0(1)SY

This command was modified. This command was hidden.

Usage Guidelines

The show oer border routes command is entered on a border router. This command is used to display information about OER-controlled routes on a border router. You can display information about BGP or static routes.

In Cisco IOS Release 12.4(20)T, the cce keyword was added to display information about OER-controlled traffic classes that are identified using Network-Based Application Recognition (NBAR).

Examples

The following example displays BGP learned routes on a border router:

Router# show oer border routes bgp 
OER BR 10.1.1.2 ACTIVE, MC 10.1.1.3 UP/DOWN: UP 00:10:08,
   Auth Failures: 0
   Conn Status: SUCCESS, PORT: 3949
BGP table version is 12, local router ID is 10.10.10.2
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
               r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
OER Flags: C - Controlled, X - Excluded, E - Exact, N - Non-exact, I - Injected
    Network          Next Hop        OER    LocPrf Weight Path
*> 10.1.0.0/16      10.40.40.2      CE                0 400 600 i

The table below describes the significant fields shown in the display.

Table 12 show oer border routes bgp Field Descriptions

Field

Description

C-Controlled

Indicates the monitored prefix is currently under OER control.

X-Excluded

Indicates the monitored prefix is controlled by a different border router.

E - Exact

Indicates that an exact prefix indicates is controlled, but more specific routes are not.

N - Non-exact

Indicates that the prefix and all more specific routes are under OER control.

I - Injected

Indicates that the prefix is injected into the BGP routing table. If a less specific prefix exists in the BGP table and OER has a more specific prefix configured, then BGP will inject the new prefix and OER will flag it as I-Injected.

XN

Indicates that the prefix and all more specific prefixes are under the control of another border router, and, therefore, this prefix is excluded. (Not shown in the example output.

CNI

Indicates that the prefix is injected, and this prefix and all more specific prefixes are under OER control.

CEI

Indicates that the specific prefix is injected and under OER control.

CN

Indicates that the prefix and all more specific prefixes are under OER control.

CE

Indicates that the specific prefix is under OER control.

Network

The IP address and prefix mask.

Next Hop

The next hop of the prefix.

OER

Type of OER control.

LocPrf

The BGP local preference value.

Weight

The weight of the route.

Path

The BGP path type.

The following example displays OER-controlled routes identified using NBAR:

Router# show oer border routes cce
Class-map oer-class-acl-oer_cce#2-stile-telnet, permit, sequence 0, mask 24
  Match clauses:
    ip address (access-list): oer_cce#2
    stile: telnet
  Set clauses:
    ip next-hop 10.1.3.2
    interface Ethernet2/3
  Statistic:
    Packet-matched: 60

The table below describes the significant fields shown in the display.

Table 13 show oer border routes cce Field Descriptions

Field

Description

Class-map

Indicates the name OER map used to control the OER traffic classes.

Match clauses

Indicates the match criteria being applied to the traffic classes.

ip address (access-list)

Name of access list used to match the destination prefixes of the controlled traffic classes identified using NBAR.

stile

Protocol being controlled.

Set clauses

Indicates the set criteria being applied to the matched traffic classes.

ip next-hop

IP address of the next hop to which the controlled traffic is sent. The next hop should be to a noncontrolling router.

interface

Interface name and number through which the controlled traffic is sent. If this is an ingress interface, the border router is not controlling the traffic classes. If this is an egress interface of the border router, the route is being controlled.

Statistic

Displays statistics such as number of packets matched.

The following example, available in Cisco IOS Release 15.0(10M, 12.2(33)SRE, and later releases, displays EIGRP-controlled routes on a border router with information about the parent route that exists in the EIGRP routing table. In this example, the output shows that prefix 10.1.2.0/24 is being controlled by OER. This command is used to show parent route lookup and route changes to existing parent routes when the parent route is identified from the EIGRP routing table.

Router# show oer border routes eigrp
Flags: C - Controlled by oer, X - Path is excluded from control, 
       E - The control is exact, N - The control is non-exact
Flags Network            Parent             Tag       
CE    10.1.2.0/24        10.0.0.0/8         5000

In this example, the parent keyword is used and more details are shown about the parent route lookup.

Router# show oer border routes eigrp parent
Network            Gateway            Intf       Flags   
10.0.0.0/8         10.40.40.2         Ethernet4  1       
Child Networks
Network            Flag

Related Commands

Command

Description

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

show oer master

To display information about an Optimized Edge Routing (OER) master controller, use the show oer master command in privileged EXEC mode.

show oer master

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T

This command was introduced.

12.3(11)T

The protocol field was added to the output of this command under the "Learn Settings" heading.

12.3(14)T

The trace probe delay field was added to the output of this command under the "Global Settings" heading.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

Usage Guidelines

The show oer master command is entered on a master controller. The output of this command 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 displays the status of an OER managed network on a master controller:

Router# show oer master
 
OER state: ENABLED and ACTIVE
  Conn Status: SUCCESS, PORT: 3949
  Number of Border routers: 2
  Number of Exits: 2
  Number of monitored prefixes: 10 (max 5000)
Border           Status   UP/DOWN             AuthFail
10.4.9.7         ACTIVE   UP       02:54:40          0
10.4.9.6         ACTIVE   UP       02:54:40          0
Global Settings:
  max-range-utilization percent 20
  mode route metric bgp local-pref 5000
  mode route metric static tag 5000
  trace probe delay 1000 
  logging
Default Policy Settings:
  backoff 300 3000 300
  delay relative 50
  holddown 300
  periodic 0
  mode route control 
  mode monitor both
  mode select-exit best
  loss relative 10
  unreachable relative 50
  resolve delay priority 11 variance 20
  resolve utilization priority 12 variance 20
Learn Settings:
  current state : SLEEP
  time remaining in current state : 4567 seconds
  throughput
  delay
  no protocol 
  monitor-period 10
  periodic-interval 20
  aggregation-type bgp
  prefixes 100
  expire after time 720 

The table below describes the significant fields shown in the display.

Table 14 show oer master Field Descriptions

Field

Description

OER state

Indicates the status of the master controller. The state will be either "Enabled" or "Disabled" and "Active" or "Inactive."

Conn Status

Indicates the state of the connection between the master controller and the border router. The state is displayed as "SUCCESS" to indicate as successful connection. The state is displayed as "CLOSED" if there is no connection.

PORT:

Displays the port number that is used for communication between the master controller and the border router.

Number of Border routers:

Displays the number of border router that peer with the master controller.

Number of Exits:

Displays the number of exit interfaces under OER control.

Number of monitored prefixes:

Displays the number prefixes that are actively or passively monitored.

Border

Displays the IP address of the border router.

Status

Indicates the status of the border router. This field displays either "ACTIVE" or "INACTIVE."

UP/DOWN

Displays the connection status. The output displays "DOWN" or "UP." "UP" is followed by the length of time that the connection has been in this state.

AuthFail

Displays the number of authentication failures between the master controller and the border router.

Global Settings:

Displays the configuration of global OER master controller settings.

Default Policy Settings:

Displays default OER master controller policy settings.

Learn Settings:

Display OER learning settings.

Related Commands

Command

Description

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

show oer master active-probes

To display connection and status information about active probes on an Optimized Edge Routing (OER) master controller, use the show oer master active-probes command in privileged EXEC mode.

show oer master active-probes [ appl | forced ]

Syntax Description

appl

(Optional) Filters the output display that active probes generate for application traffic configured with the OER Application-Aware Routing: PBR feature.

forced

(Optional) Filters the output display that active probes generate for voice traffic configured with a forced target assignment.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T

This command was introduced.

12.4(2)T

Support for the appl keyword was introduced in Cisco IOS Release 12.4(2)T.

12.4(6)T

Support for the forced keyword was introduced in Cisco IOS Release 12.4(6)T.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

Usage Guidelines

The show oer master active-probes command is entered on a master controller. This command is used to display the status of active probes. The output from this command displays the active probe type and destination, the border router that is the source of the active probe, the target prefixes that are used for active probing, and whether the probe was learned or configured. Entering the appl keyword filters the output to display information about applications optimized by the master controller. Entering the forced keyword filters the output to display information about voice traffic that is configured with a forced target assignment optimized by the master controller.

Examples

The following example shows the status of configured and running active probes:

Router# show oer master active-probes
 
        OER Master Controller active-probes
Border   = Border Router running this Probe
State    = Un/Assigned to a Prefix
Prefix   = Probe is assigned to this Prefix
Type     = Probe Type
Target   = Target Address
TPort    = Target Port
How      = Was the probe Learned or Configured
N - Not applicable
The following Probes exist:
State      Prefix             Type     Target          TPort How
Assigned   10.1.1.1/32       echo     10.1.1.1           N Lrnd
Assigned   10.1.4.0/24       echo     10.1.4.1           N Lrnd
Assigned   10.1.2.0/24       echo     10.1.2.1           N Lrnd
Assigned   10.1.4.0/24       udp-echo 10.1.4.1       65534 Cfgd
Assigned   10.1.3.0/24       echo     10.1.3.1           N Cfgd
Assigned   10.1.2.0/24       tcp-conn 10.1.2.1          23 Cfgd
The following Probes are running:
Border          State    Prefix             Type     Target          TPort
192.168.2.3     ACTIVE   10.1.4.0/24       udp-echo 10.1.4.1       65534 
172.16.1.1      ACTIVE   10.1.2.0/24       tcp-conn 10.1.2.1          23 

The table below describes the significant fields shown in the display.

Table 15 show oer master active-probes Field Descriptions

Field

Description

The following Probes exist:

Displays the status of configured active probes.

State

Displays the status of the active probe. The output displays "Assigned" or "Unassigned."

Prefix

Displays the prefix and prefix mask of the target active probe.

Type

Displays the type of active probe. The output displays "echo," "jitter," "tcp-conn," or "udp-echo."

Target

Displays the target IP address for the active probe.

TPort

Displays the target port for the active probe.

How

Displays how the active probe was created. The output will indicate the probe is configured or learned.

The following Probes are running:

Displays the status of active probes that are running.

Border

Displays the IP address of the border router.

The following example shows the status of configured and running active probes when a jitter probe has been configured:

Router# show oer master active-probes
 
OER Master Controller active-probes
Border   = Border Router running this Probe
State    = Un/Assigned to a Prefix
Prefix   = Probe is assigned to this Prefix
Type     = Probe Type
Target   = Target Address
TPort    = Target Port
How      = Was the probe Learned or Configured
N - Not applicable
The following Probes exist:
State      Prefix             Type         Target      TPort How    codec
Assigned   10.1.1.0/24      jitter      10.1.1.10       2000 Cfgd g711ulaw
Assigned   10.1.1.0/24        echo       10.1.1.2          N Lrnd        N
The following Probes are running:
Border          State     Prefix            Type     Target          TPort
10.1.1.2         ACTIVE   10.1.1.0/24     jitter     10.1.1.10        2000
10.1.1.2         ACTIVE   10.1.1.0/24       echo     10.1.1.6            N
10.2.2.3         ACTIVE   10.1.1.0/24     jitter     10.1.1.10        2000
10.2.2.3         ACTIVE   10.1.1.0/24       echo     10.1.1.6            N
10.1.1.1         ACTIVE   10.1.1.0/24     jitter     10.1.1.10        2000
10.1.1.1         ACTIVE   10.1.1.0/24       echo     10.1.1.6            N

The table below describes the significant fields shown in the display that are different from those in the table above.

Table 16 show oer master active-probes (jitter and MOS) Field Descriptions

Field

Description

codec

Displays the codec value configured for MOS calculation. Codec values can be one of the following: g711alaw, g711ulaw, or g729a.

Related Commands

Command

Description

active-probe

Configures active probes to monitor an OER controlled prefixes.

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

show oer master appl

To display information about application traffic classes monitored and controlled by an Optimized Edge Routing (OER) master controller, use the show oer master appl command in privileged EXEC mode.

{ show oer master appl [ access-list name ] [ detail] [ learned [ delay | throughput ] ] | [ tcp | udp ] [ protocol-number] [ min-port max-port ] [ dst | src ] [ detail | policy ] }

Syntax Description

access-list name

(Optional) Filters the output based on the specified named extended access list.

detail

(Optional) Displays detailed information.

learned

(Optional) Displays information about learned application traffic classes.

delay

(Optional) Displays information about applications learned using delay as the learning criterion.

throughput

(Optional) Displays information about applications learned using throughput as the learning criterion.

tcp

(Optional) Filters the output based on TCP traffic.

udp

(Optional) Filters the output based on User Datagram Protocol (UDP) traffic.

protocol-number

(Optional) Filters the output based on the specified protocol number.

min-port max-port

(Optional) Filters the output based on the specified port number or range of port numbers.

dst

(Optional) Filters the output based on the destination port number.

src

(Optional) Filters the output based on the source port number.

policy

(Optional) Displays the policy for the application or port number.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(2)T

This command was introduced.

12.4(9)T

The learned, delay, and throughput keywords were added.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

Usage Guidelines

The show oer master appl command is entered on an OER master controller. This command is used to display information about application traffic classes that are configured for monitoring and optimization.

Examples

The following example shows TCP application traffic filtered based on port 80 (HTTP):

Router# show oer master appl tcp 80 80 dst policy
 
Prefix             Appl Prot       Port                 Port Type       Policy         
--------------------------------------------------------------------------------
10.1.0.0/16        tcp             [80, 80]             dst             20             
10.1.1.0/24        tcp             [80, 80]             dst             10

The table below describes the significant fields shown in the display.

Table 17 show oer master appl Field Descriptions

Field

Description

Prefix

IP address of the monitored prefix that carries the application traffic.

Appl Prot

Application protocol.

Port

Application port number.

Port Type

Source or destination application port number.

Policy

Application policy number.

The following example shows information about learned application traffic classes:

Router# show oer master appl learned
OER Prefix Statistics:
 Pas - Passive, Act - Active, S - Short term, L - Long term, Dly - Delay (ms),
 P - Percentage below threshold, Jit - Jitter (ms), 
 MOS - Mean Opinion Score
 Los - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),
 E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicable
 U - unknown, * - uncontrolled, + - control more specific, @ - active probe all
 # - Prefix monitor mode is Special, & - Blackholed Prefix
 % - Force Next-Hop, ^ - Prefix is denied
Prefix                Prot Port [src][dst]/ApplId        DSCP Source Prefix     
                          State     Time Curr BR         CurrI/F         Protocol
                        PasSDly  PasLDly   PasSUn   PasLUn  PasSLos  PasLLos
                        ActSDly  ActLDly   ActSUn   ActLUn      EBw      IBw
                        ActSJit  ActPMOS
--------------------------------------------------------------------------------
100.1.0.0/16           tcp [1, 65535] [80, 80]           defa 0.0.0.0/0         
                       DEFAULT*       87 U               U               U       
Router# show oer master appl tcp 80 80 dst
OER Prefix Statistics:
 Pas - Passive, Act - Active, S - Short term, L - Long term, Dly - Delay (ms),
 P - Percentage below threshold, Jit - Jitter (ms), 
 MOS - Mean Opinion Score
 Los - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),
 E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicable
 U - unknown, * - uncontrolled, + - control more specific, @ - active probe all
 # - Prefix monitor mode is Special, & - Blackholed Prefix
 % - Force Next-Hop, ^ - Prefix is denied
Prefix                Prot Port [src][dst]/ApplId        DSCP Source Prefix     
                          State     Time Curr BR         CurrI/F         Protocol
                        PasSDly  PasLDly   PasSUn   PasLUn  PasSLos  PasLLos
                        ActSDly  ActLDly   ActSUn   ActLUn      EBw      IBw
                        ActSJit  ActPMOS
--------------------------------------------------------------------------------
100.1.0.0/16           tcp [1, 65535] [80, 80]           defa 0.0.0.0/0         
                       DEFAULT*       52 U               U               U 

The table below describes the significant fields shown in the display that are different from those in the table above.

Table 18 show oer master appl learned Field Descriptions

Field

Description

ApplId

ID of the application.

DSCP

Differentiated Services Code Point (DSCP) value.

Source Prefix

IP address of the application source.

State

Current state of the application traffic class flow.

Time

Time, in seconds, between probe messages.

Curr BR

IP address of the border router through which the prefix associated with this application traffic class is being currently routed.

CurrI/F

Interface of the border router through which the prefix associated with this application traffic class is being currently routed.

Proto

Protocol.

The following example shows information about application traffic classes learned using delay as the learning criterion:

Router# show oer master appl learned delay
OER Prefix Statistics:
 Pas - Passive, Act - Active, S - Short term, L - Long term, Dly - Delay (ms),
 P - Percentage below threshold, Jit - Jitter (ms), 
 MOS - Mean Opinion Score
 Los - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),
 E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicable
 U - unknown, * - uncontrolled, + - control more specific, @ - active probe all
 # - Prefix monitor mode is Special, & - Blackholed Prefix
 % - Force Next-Hop, ^ - Prefix is denied
Prefix                Prot Port [src][dst]               DSCP Source Prefix     
                          State     Time Curr BR         CurrI/F         Proto   
                        PasSDly  PasLDly   PasSUn   PasLUn  PasSLos  PasLLos
                        ActSDly  ActLDly   ActSUn   ActLUn      EBw      IBw
                        ActSJit  ActPMOS
--------------------------------------------------------------------------------
10.1.3.0/24            udp [1, 65535] [3000, 4000]         ef 0.0.0.0/0         
                      INPOLICY*      @70 1.1.1.2         Et0/0           PBR     
                              U        U        0        0        0        0
                              3        4        0        0        1        0
                              N        N

The following example shows information about application traffic classes learned using throughput as the learning criterion:

Router# show oer master appl learned throughput
OER Prefix Statistics:
 Pas - Passive, Act - Active, S - Short term, L - Long term, Dly - Delay (ms),
 P - Percentage below threshold, Jit - Jitter (ms), 
 MOS - Mean Opinion Score
 Los - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),
 E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicable
 U - unknown, * - uncontrolled, + - control more specific, @ - active probe all
 # - Prefix monitor mode is Special, & - Blackholed Prefix
 % - Force Next-Hop, ^ - Prefix is denied
Prefix                Prot Port [src][dst]               DSCP Source Prefix     
                          State     Time Curr BR         CurrI/F         Proto   
                        PasSDly  PasLDly   PasSUn   PasLUn  PasSLos  PasLLos
                        ActSDly  ActLDly   ActSUn   ActLUn      EBw      IBw
                        ActSJit  ActPMOS
--------------------------------------------------------------------------------
10.1.1.0/24            udp [1, 65535] [3000, 4000]         ef 0.0.0.0/0         
                      INPOLICY*      @70 1.1.1.2         Et0/0           PBR     
                              U        U        0        0        0        0
                             11        7        0        0        1        0
                              N        N

Related Commands

Command

Description

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

show oer master border

To display the status of connected Optimized Edge Routing (OER) border routers, use the show oer master bordercommand in privileged EXEC mode.

show oer master border [ ip-address] [ detail | report | topology ]

Syntax Description

ip-address

(Optional) Specifies the IP address of a single border router.

detail

(Optional) Displays detailed border router information.

report

(Optional) Displays border router related link reports.

topology

(Optional) Displays the status of the policy based routing (PBR) requirement.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.3(8)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

12.4(15)T

This command was modified. The topologykeyword was added, and the show oer master border command output was enhanced to include the status of the PBR requirement.

Usage Guidelines

The show oer master bordercommand and all the keywords are entered on a master controller. The output of this command shows the status of connections with border routers.

Examples

The following example displays the status of border router connections with a master controller:

Router# show oer master border
OER state: ENABLED and ACTIVE
  Conn Status: SUCCESS, PORT: 3949
  Version: 2.2
  Number of Border routers: 3
  Number of Exits: 3
  Number of monitored prefixes: 1 (max 5000)
  Max prefixes: total 5000 learn 2500
  Prefix count: total 1, learn 0, cfg 1
  PBR Requirements met
  Nbar Status: Inactive
Border           Status   UP/DOWN             AuthFail  Version
10.165.201.5     ACTIVE   UP       00:05:29          0  2.2
10.165.201.6     ACTIVE   UP       00:05:29          0  2.2
10.165.201.7     ACTIVE   UP       00:05:29          0  2.2

The table below describes the significant fields shown in the display. All the other fields in the output are self-explanatory.

Table 19 show oer master border Field Descriptions

Field

Description

Border

Displays the IP address of the border router.

Status

Displays the status of the border router. The output displays "ACTIVE" or "INACTIVE."

UP/DOWN

Displays the connection status and the length of time that the connection has been up. The output displays "DOWN" or "UP." The up time is displayed in weeks, days, hours, minutes, and seconds.

AuthFail

Displays the number of authentication failures between the master controller and the border router.

Version

Displays the version for all of the border routers configured on the master controller.

The following example displays detailed information about border router connections with a master controller:

Router# show oer master border detail
Border           Status   UP/DOWN             AuthFail  Version
10.1.1.2         ACTIVE   UP       14:03:40          0  3.0
 Et2/0           EXTERNAL UP             
 Et0/0           INTERNAL UP             
 Et1/0           EXTERNAL UP             
 
 External            Capacity      Max BW   BW Used    Load Status          Exit Id
 Interface            (kbps)       (kbps)    (kbps)    (%)                         
 ---------       --  --------      ------   -------    ---- ------          -------
 Et2/0           Tx       800         600       226      28 UP                    2
                 Rx                   800         0       0
 Et1/0           Tx       800         600        97      12 UP                    1
                 Rx                   800        55       6

The table below describes the significant fields shown in the display.

Table 20 show oer master border detail Field Descriptions

Field

Description

Border

Displays the IP address of the border router.

Status

Displays the status of the border router. The output displays "ACTIVE" or "INACTIVE."

UP/DOWN

Displays the connection status and the length of time that the connection has been up. The output displays "DOWN" or "UP." The up time is displayed in weeks, days, hours, minutes, and seconds.

AuthFail

Displays the number of authentication failures between the master controller and the border router.

External Interface

Displays the external OER controlled interface.

Capacity

Displays the capacity of the interface in kilobytes per second.

Max BW

Displays the maximum usable bandwidth in kilobytes per second as configured on the interface.

BW Used

Displays the amount of bandwidth in use in kilobytes per second.

Load

Displays the amount of bandwidth in use as a percentage of the total capacity of the interface.

Status

Displays the status of the link.

Exit Id

Displays the ID number assigned by the master controller to identify the exit.

Tx

Displays the percentage of interface utilization in the outbound direction.

Rx

Displays the percentage of interface utilization in the inbound direction.

The following example displays if the PBR requirement for the application control by OER is met or not:

Router# show oer master border topology
LocalBR        LocalEth          RemoteBR       RemoteEth      nbar_type
--------------------------------------------------------------------------------
10.165.201.4   Ethernet0/0       10.165.202.2   Ethernet0/0    Directly Connected  
10.165.201.4   Ethernet0/0       10.165.201.3   Ethernet0/0    Directly Connected  
10.165.201.3   Ethernet0/0       10.165.201.4   Ethernet0/0    Directly Connected  
10.165.201.3   Ethernet0/0       10.165.201.3   Ethernet0/0    Directly Connected  
10.165.201.2   Ethernet0/0       10.165.201.4   Ethernet0/0    Directly Connected  
10.165.201.2   Ethernet0/0       10.165.201.2   Ethernet0/0    Directly Connected  
PBR Requirements met

The table below describes the significant fields shown in the display.

Table 21 show oer master border topology Field Descriptions

Field

Description

LocalBR

Displays the local border router.

LocalEth

Displays the local interface connection for the local border router.

RemoteBR

Displays the remote border router that is connected with the local border router.

RemoteEth

Displays the remote interface connection for the remote border router.

nbar_type

Displays the type of NBAR connection for each of the border routers. Three types of connection status are available: Directly Connected, One-How-Away Neighbor, and Not Connected.

The following example displays the border router link report:

Router# show oer master border report
Border           Status   UP/DOWN             AuthFail  Version
10.165.202.132   ACTIVE   UP       00:05:54          0  2.2
10.165.202.131   ACTIVE   UP       00:05:57          0  2.2
10.165.202.130   ACTIVE   UP       00:06:00          0  2.2
10.165.202.129   ACTIVE   UP       00:06:03          0  2.2

The table below describes the significant fields shown in the display.

Table 22 show oer master report detail Field Descriptions

Field

Description

Border

Displays the IP address of the border router.

Status

Displays the status of the border router. The output displays "ACTIVE" or "INACTIVE."

UP/DOWN

Displays the connection status and the length of time that the connection has been up. The output displays "DOWN" or "UP." The up time is displayed in weeks, days, hours, minutes, and seconds.

AuthFail

Displays the number of authentication failures between the master controller and the border router.

Status

Displays the status of the link.

Related Commands

Command

Description

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

show oer master cost-minimization

To display the status of cost-based optimization policies, use the show oer master cost-minimization command in privileged EXEC mode.

show oer master cost-minimization { billing-history | border ip-address [ interface] | nickname name }

Syntax Description

billing-history

Deploys the billing history

border ip-address

Displays information for a single border router.

interface

(Optional) Displays information for only the specified interface.

nickname name

Displays information for the service provider. A nickname must be configured before output will be displayed.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.3(14)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

Usage Guidelines

The show oer master cost-minimization command is entered on a master controller. The output of this command shows the status of cost-based policies.

Examples

The following example displays the billing history for cost policies:

Router# show oer master cost-minimization billing-history 
Billing History for the past three months
        ISP2 on 10.1.1.2         Ethernet0/0     
  80-percent on 10.1.1.1         Ethernet0/0     
                 Mon1                  Mon2                  Mon3
Nickname     SustUtil       Cost   SustUtil       Cost   SustUtil       Cost
----------    ------------------    ------------------   ------------------
      ISP2        ---NA---      1737222676 1737222676        ---NA---     
80-percent        ---NA---      1737231684 1737231684        ---NA---     
----------    ------------------    ------------------   ------------------
Total Cost                     0            3474454360                     0

The table below describes the significant fields shown in the display.

Table 23 show oer master cost-minimization billing-history Field Descriptions

Field

Description

Nickname

The nickname assigned to the service provider.

SustUtil

The sustained utilization of the exit link.

Cost

The financial cost of the link.

Total Cost

The total financial cost for the month.

The following example displays cost optimization information only for Ethernet 1/0:

Router# show oer master cost-minimization border 10.1.1.2 Ethernet1/0
 
 Nickname  : ispname          Border: 10.1.1.2         Interface: Et1/0           
 Calc type : Combined
 Start Date: 20
 Fee       : Tier Based
             Tier1 : 100, fee: 10000
             Tier2 : 90, fee: 9000
 Period    : Sampling 22, Rollup 1400
 Discard   : Type Percentage, Value 22
 Rollup Information:
 Total           Discard         Left            Collected       
 60              13              36              0               
 Current Rollup Information:
   MomentaryTgtUtil:         7500 Kbps    CumRxBytes:            38669
  StartingRollupTgt:         7500 Kbps    CumTxBytes:            39572
   CurrentRollupTgt:         7500 Kbps    TimeRemain:        09:11:01
 Rollup Utilization (Kbps):
 Egress/Ingress Utilization Rollups (Descending order) 
 1   : 0            2   : 0

The table below describes the significant fields shown in the display.

Table 24 show oer master cost-minimization border Field Descriptions

Field

Description

Nickname

Nickname of the service provider.

Border

IP address of the border router.

Interface

Interface for which the cost policy is configured.

Calc type

Displays the configured billing method.

Start Date

Displays the starting date of the billing period.

Fee

Displays the billing type (fixed or tiered) and the billing configuration.

Period

Displays the sampling and rollup configuration.

Discard

Displays the discard configuration, type, and value.

Rollup Information

Displays rollup statistics.

Current Rollup Information

Displays rollup statistics for the current sampling cycle.

Rollup Utilization

Displays rollup utilization statistics in kilobytes per second.

The following example displays cost optimization information for the specified service provider:

Router# show oer master cost-minimization nickname ISP1
 
 Nickname  : ISP1             Border: 10.1.1.2         Interface: Et1/0           
 Calc type : Combined
 Start Date: 20
 Fee       : Tier Based
             Tier1 : 100, fee: 10000
             Tier2 : 90, fee: 9000
 Period    : Sampling 22, Rollup 1400
 Discard   : Type Percentage, Value 22
 Rollup Information:
 Total           Discard         Left            Collected       
 60              13              36              0               
 Current Rollup Information:
   MomentaryTgtUtil:         7500 Kbps    CumRxBytes:            38979
  StartingRollupTgt:         7500 Kbps    CumTxBytes:            39692
   CurrentRollupTgt:         7500 Kbps    TimeRemain:        09:10:49
 Rollup Utilization (Kbps):
 Egress/Ingress Utilization Rollups (Descending order) 
 1   : 0            2   : 0 

Related Commands

Command

Description

cost-minimization

Configures cost-based optimization policies on a master controller.

debug oer master cost-minimization

Displays debugging information for cost-based optimization policies.

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

show oer master defined application

To display information about user-defined application definitions used in Optimized Edge Routing (OER), use the show oer master defined application command in privileged EXEC mode.

show oer master defined application

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.4(15)T

This command was introduced.

Usage Guidelines

The show oer master defined applicationcommand is entered on an OER master controller. This command displays all applications that are user-defined. To define a custom application to be used by OER, use the application define command on the OER master controller.

To display the same information on an OER border router, use the show oer border defined applicationcommand.

Examples

The following partial example output shows information about the user-defined applications configured for use with OER:

Router# show oer master defined application
OER Defined Applications:
Name                Appl_ID Dscp Prot     SrcPort     DstPort SrcPrefix         
--------------------------------------------------------------------------------
telnet                    1 defa  tcp       23-23     1-65535 0.0.0.0/0         
telnet                    1 defa  tcp     1-65535       23-23 0.0.0.0/0         
ftp                       2 defa  tcp       21-21     1-65535 0.0.0.0/0         
ftp                       2 defa  tcp     1-65535       21-21 0.0.0.0/0         
cuseeme                   4 defa  tcp   7648-7648     1-65535 0.0.0.0/0         
cuseeme                   4 defa  tcp   7649-7649     1-65535 0.0.0.0/0         
cuseeme                   4 defa  tcp     1-65535   7648-7648 0.0.0.0/0         
dhcp                      5 defa  udp       68-68       67-67 0.0.0.0/0         
dns                       6 defa  tcp       53-53     1-65535 0.0.0.0/0         
dns                       6 defa  tcp     1-65535       53-53 0.0.0.0/0         
dns                       6 defa  udp       53-53     1-65535 0.0.0.0/0         
dns                       6 defa  udp     1-65535       53-53 0.0.0.0/0         
finger                    7 defa  tcp       79-79     1-65535 0.0.0.0/0         
finger                    7 defa  tcp     1-65535       79-79 0.0.0.0/0         
gopher                    8 defa  tcp       70-70     1-65535 0.0.0.0/0 
.
.
.

The table below describes the significant fields shown in the display.

Table 25 show oer master defined application Field Descriptions

Field

Description

Name

Application Name

Appl_ID

Application ID

Dscp

Differentiated Services Code Point (DSCP) value

Prot

Protocol

SrcPort

Source port number for the traffic class

DstPort

Destination port number for the traffic class

SrcPrefix

IP address of the traffic class source

Related Commands

Command

Description

application define

Defines a user-defined application to be monitored by OER.

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

show oer border defined application

Displays information about user-defined application definitions used in OER.

show oer master learn list

To display configuration information about Optimized Edge Routing (OER) learn lists, use the show oer master learn list command in privileged EXEC mode.

show oer master learn list [ list-name]

Syntax Description

list-name

(Optional) Name of learn list.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.4(15)T

This command was introduced.

Usage Guidelines

The show oer master learn list command is entered on an OER master controller. This command is used to display configuration information about learn lists. In Cisco IOS Release 12.4(15)T, the learn list configuration mode was introduced. Learn lists are a way to categorize learned traffic classes. In each learn list, different criteria for learning traffic classes including prefixes, application definitions, filters, and aggregation parameters can be configured. A traffic class is automatically learned by OER based on each learn list criteria, and each learn list is configured with a sequence number. The sequence number determines the order in which learn list criteria are applied. Learn lists allow different OER policies to be applied to each learn list; in previous releases, the traffic classes could not be divided, and an OER policy was applied to all the traffic classes profiled during one learning session.

Examples

The following example shows how to display configuration information about two learn lists, LIST1 and LIST2:

Router# show oer master learn list
Learn-List LIST1 10
   Configuration:
    Application: ftp
    Aggregation-type: bgp
    Learn type: thruput
    Policies assigned: 8 10
   Stats:
    Application Count: 0
    Application Learned:
 Learn-List LIST2 20
   Configuration:
    Application: telnet
    Aggregation-type: prefix-length 24
    Learn type: thruput
    Policies assigned: 5 20
   Stats:
    Application Count: 2
    Application Learned:
     Appl Prefix 10.1.5.0/24 telnet
     Appl Prefix 10.1.5.16/28 telnet

The table below describes the significant fields shown in the display.

Table 26 show oer master learn list Field Descriptions

Field

Description

Learn-List

Identifies the OER learn list name and sequence number.

Application

Application protocol.

Aggregation-type

Type of TCF aggregation.

Learn type

Throughput or delay.

Policies assigned

Application policy number.

Application Count

Number of applications learned.

Application Learned

Type of application that is learned.

Related Commands

Command

Description

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

show oer master link-group

To display information about Optimized Edge Routing (OER) link groups, use the show oer master link-group command in privileged EXEC mode.

show oer master link-group [ link-group-name]

Syntax Description

link-group-name

(Optional) Name of link group.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.4(15)T

This command was introduced.

Usage Guidelines

The show oer master link-group command is entered on an OER master controller. This command is used to display information about link groups including the link group name, the border router and the interface on the border router that is the exit link, and the ID of the exit link.

Introduced in Cisco IOS Release 12.4(15)T, link groups are used to define a group of exit links as a preferred set of links or a fallback set of links for OER to use when optimizing a specified traffic class. Up to three link groups can be specified for each interface. Use the link-group command to define the link group for an interface and use the set link-group command to define the primary link group and a fallback link group for a specified traffic class in an OER map.

Examples

The following example displays information about all configured link groups:

Router# show oer master link-group
link group video
  Border           Interface       Exit id 
  192.168.1.2      Serial2/0       1       
 link group voice
  Border           Interface       Exit id 
  192.168.1.2      Serial2/0       1       
  192.168.1.2      Serial3/0       2       
  192.168.3.2      Serial4/0       4       
 link group data
  Border           Interface       Exit id 
  192.168.3.2      Serial3/0       3 

The table below describes the significant fields shown in the display.

Table 27 show oer master link-group Field Descriptions

Field

Description

link group

Name of the link group.

Border

IP address of the border router on which the exit link exists.

Interface

Type and number of the interface on the border router that is the exit link.

Exit id

ID number of the exit link.

The following example displays information only about the link group named voice:

Router# show oer master link-group voice
link group voice
  Border           Interface       Exit id 
  192.168.1.2      Serial2/0       1       
  192.168.1.2      Serial3/0       2       
  192.168.3.2      Serial4/0       4

Related Commands

Command

Description

link-group

Configures an OER border router exit interface as a member of a link group.

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

set link-group

Specifies a link group for traffic classes defined in an OER policy.

show oer master nbar application

To display information about the status of an application identified using Network-Based Application Recognition (NBAR) for each Optimized Edge Routing (OER) border router, use the show oer master nbar application command in privileged EXEC mode.

show oer master nbar application

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.4(20)T

This command was introduced.

Usage Guidelines

The show oer master nbar applicationcommand is entered on an OER master controller. This command is used to verify the validity of an application that is identified using NBAR at each OER border router. If the NBAR application is not supported on one or more border routers, then all the traffic classes related to that NBAR application are marked inactive and cannot be optimized using OER.

NBAR is capable of identifying applications based on the following three types of protocols:

  • Non-UDP and Non-TCP IP protocols--For example, Generic Routing Encapsulation (GRE), and Internet Control Message Protocol (ICMP).
  • TCP and UDP protocols that use statically assigned port numbers--For example, CU-SeeMe desktop video conference (CU-SeeMe-Server) andPost Office Protocol over Transport Layer Security (TLS) and Secure Sockets Layer (SSL) server (SPOP3-Server).
  • TCP and UDP protocols that dynamically assign port numbers and require stateful inspection--For example, Real-Time Transport Protocol audio streaming (RTP-audio) and BitTorrent File Transfer Traffic (BitTorrent).

The list of applications identified using NBAR and available for profiling of OER or Performance Routing traffic classes is constantly evolving. For lists of many of the NBAR applications defined using static or dynamically assigned ports, see the Using Performance Routing to Profile the Traffic Classes module.

For more details about NBAR, see the Classifying Network Traffic Using NBAR section of the Cisco IOS Quality of Service Solutions Configuration Guide .

Examples

The following partial output shows information about the status of a number of applications identified using NBAR at three OER border routers. In this example, applications based on BGP, BitTorrent, and HTTP protocols are valid at all three OER border routers and traffic classes for these applications are active. While applications such as ConnectionLess Network Service (CLNS) and KaZaA are invalid on at least one border router, all traffic classes based on these application are marked inactive.

Router# show oer master nbar application
NBAR Appl                  10.1.1.4        10.1.1.2        10.1.1.3
-------------------------------------------------------------------
aarp                        Invalid         Invalid         Invalid
appletalk                   Invalid         Invalid         Invalid
arp                         Invalid         Invalid         Invalid
bgp                           Valid           Valid           Valid
bittorrent                    Valid           Valid           Valid
bridge                      Invalid         Invalid         Invalid
bstun                       Invalid         Invalid         Invalid
cdp                         Invalid         Invalid         Invalid
citrix                      Invalid         Invalid         Invalid
clns                          Valid         Invalid         Invalid
clns_es                     Invalid         Invalid         Invalid
clns_is                     Invalid         Invalid         Invalid
cmns                        Invalid         Invalid         Invalid
compressedtcp               Invalid         Invalid         Invalid
cuseeme                     Invalid         Invalid         Invalid
decnet                      Invalid         Invalid         Invalid
decnet_node                 Invalid         Invalid         Invalid
decnet_router-l1            Invalid         Invalid         Invalid
decnet_router-l2            Invalid         Invalid         Invalid
dhcp                        Invalid         Invalid         Invalid
directconnect               Invalid         Invalid         Invalid
dlsw                        Invalid         Invalid         Invalid
dns                         Invalid         Invalid         Invalid
edonkey                     Invalid         Invalid         Invalid
egp                         Invalid         Invalid         Invalid
eigrp                       Invalid         Invalid         Invalid
exchange                    Invalid         Invalid         Invalid
fasttrack                   Invalid         Invalid         Invalid
finger                      Invalid         Invalid         Invalid
ftp                         Invalid         Invalid         Invalid
gnutella                    Invalid         Invalid         Invalid
Morpheus                    Invalid         Invalid         Invalid
gopher                      Invalid         Invalid         Invalid
gre                         Invalid         Invalid         Invalid
h323                        Invalid         Invalid         Invalid
http                          Valid           Valid           Valid
icmp                        Invalid         Invalid         Invalid
imap                        Invalid         Invalid         Invalid
ip                          Invalid         Invalid         Invalid
ipinip                      Invalid         Invalid         Invalid
ipsec                       Invalid         Invalid         Invalid
ipv6                        Invalid         Invalid         Invalid
ipx                         Invalid         Invalid         Invalid
irc                         Invalid         Invalid         Invalid
kazaa2                        Valid         Invalid           Valid
.
.
.

The table below describes the significant fields shown in the display.

Table 28 show oer master nbar application Field Descriptions

Field

Description

Appl

Application Name

10.1.1.4

IP address of an OER border router

10.1.1.2

IP address of an OER border router

10.1.1.3

IP address of an OER border router

Related Commands

Command

Description

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

show oer master traffic-class application nbar

Displays information about application traffic classes that are identified using NBAR and are monitored and controlled by an OER master controller.

show oer master policy

To display policy settings on an Optimized Edge Routing (OER) master controller, use the show oer master policy command in privileged EXEC mode.

show oer master policy { sequence-number | policy-name | default | dynamic }

Syntax Description

sequence-number

Displays only the specified OER map sequence.

policy-name

Displays only the specified OER map name.

default

Displays the default policy information.

dynamic

Displays dynamic policy information.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.3(8)T

This command was introduced.

12.4(6)T

The output was modified to display the active probe frequency, if configured.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

12.4(15)T

The dynamic keyword was added to support the OER application interface.

Usage Guidelines

The show oer master policy command is entered on a master controller. The output of this command displays default policy and policies configured with an OER map.

In Cisco IOS Release 12.4(15)T, an OER application interface was introduced. The OER application interface defines the mode of communication and messaging between applications and the network for the purpose of optimizing the traffic associated with the applications. A provider is defined as an entity outside the network in which the router configured as an OER master controller exists, for example, an ISP, or a branch office of the same company. The provider has one or more host devices running one or more applications that use the OER application interface to communicate with an OER master controller. The OER application interface allows applications running on a host device in the provider network to dynamically create policies to influence the existing traffic classes, or specify new traffic class criteria. The dynamic keyword displays the policies dynamically created by an application interface provider application.

Examples

The following example displays default policy and policies configured in an OER map named CUSTOMER. The asterisk(*) character is displayed next to policy settings that override default settings.

Router# show oer master policy
* Overrides Default Policy Setting
Default Policy Settings:
  backoff 300 3000 300
  delay relative 50
  holddown 300
  periodic 0
  mode route control 
  mode monitor both
  mode select-exit best
  loss relative 10
  unreachable relative 50
  resolve delay priority 11 variance 20
  resolve utilization priority 12 variance 20
oer-map CUSTOMER 10
  match ip prefix-lists: NAME 
  backoff 300 3000 300
  delay relative 50
  holddown 300
  periodic 0
  mode route control 
  mode monitor both
  mode select-exit best
  loss relative 10
  unreachable relative 50
 *resolve utilization priority 1 variance 10
 *resolve delay priority 11 variance 20
 *probe frequency 30
oer-map CUSTOMER 20
  match ip prefix-lists: 
  match oer learn delay
  backoff 300 3000 300
  delay relative 50
  holddown 300
  periodic 0
 *mode route control 
  mode monitor both
  mode select-exit best
  loss relative 10
  unreachable relative 50
  resolve delay priority 11 variance 20
  resolve utilization priority 12 variance 20

The table below describes the significant fields shown in the display.

Table 29 show oer master policy Field Descriptions

Field

Description

Default Policy Settings:

Displays OER default configuration settings under this heading.

oer-map...

Displays the OER map name and sequence number. The policy settings applied in the OER map are displayed under this heading.

The following example displays dynamic policies created by applications using the OER application interface. The asterisk(*) character is displayed next to policy settings that override default settings.

Router# show oer master policy dynamic
Dynamic Policies:
 
  proxy id 10.3.3.3
  sequence no. 18446744069421203465, provider id 1001, provider priority 65535
    host priority 65535, policy priority 101, Session id 9
  backoff 90 90 90
  delay relative 50
  holddown 90
  periodic 0
  probe frequency 56
  mode route control 
  mode monitor both
  mode select-exit good
  loss relative 10
  jitter threshold 20
  mos threshold 3.60 percent 30
  unreachable relative 50
  next-hop not set
  forwarding interface not set
  resolve delay priority 11 variance 20
  resolve utilization priority 12 variance 20
 
  proxy id 10.3.3.3
  sequence no. 18446744069421269001, provider id 1001, provider priority 65535
    host priority 65535, policy priority 102, Session id 9
  backoff 90 90 90
  delay relative 50
  holddown 90
  periodic 0
  probe frequency 56
  mode route control 
  mode monitor both
  mode select-exit good
  loss relative 10
  jitter threshold 20
  mos threshold 3.60 percent 30
  unreachable relative 50
  next-hop not set
  forwarding interface not set
  resolve delay priority 11 variance 20
  resolve utilization priority 12 variance 20
          
  proxy id 10.3.3.4
  sequence no. 18446744069421334538, provider id 1001, provider priority 65535
    host priority 65535, policy priority 103, Session id 10
  backoff 90 90 90
  delay relative 50
  holddown 90
  periodic 0
  probe frequency 56
  mode route control 
  mode monitor both
  mode select-exit good
  loss relative 10
  jitter threshold 20
  mos threshold 3.60 percent 30
  unreachable relative 50
  next-hop not set
  forwarding interface not set
  resolve delay priority 11 variance 20
  resolve utilization priority 12 variance 20

The table below describes the significant fields shown in the display.

Table 30 show oer master policy dynamic Field Descriptions

Field

Description

Dynamic Policies:

Displays OER dynamic policy configurations under this heading.

proxy id

IP address of the host application interface device that created the policy.

sequence no.

Number indicating the sequence in which the policy was run.

provider id

ID number of the application interface provider.

provider priority

The priority assigned to the application interface provider. If a priority has not been configured, the default priority is 65535.

host priority

The priority assigned to the host application interface device. If a priority has not been configured, the default priority is 65535.

policy priority

The priority assigned to the policy.

Session id

ID number of the application interface provider session.

Related Commands

Command

Description

api provider

Registers an application interface provider with an OER master controller and enters OER master controller application interface provider configuration mode.

host-address

Configures information about a host device used by an application interface provider to communicate with an OER master controller.

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

show oer master prefix

To display the status of monitored prefixes, use the show oer master prefix command in privileged EXEC mode.

show oer master prefix [ detail | inside [ detail] | learned [ delay | inside | throughput ] | prefix [ detail | policy | report | traceroute [ exit-id | border-address | current ] [ now] ] ]

Syntax Description

detail

(Optional) Displays detailed prefix information about the specified prefix or all prefixes.

inside

(Optional) Displays detailed prefix information about inside prefixes.

learned

(Optional) Displays information about learned prefixes.

delay

(Optional) Displays information about learned prefixes based on delay.

throughput

(Optional) Displays information about learned prefixes based on throughput.

prefix

(Optional) Specifies the prefix, entered as an IP address and bit length mask.

policy

(Optional) Displays policy information for the specified prefix.

report

(Optional) Displays detailed performance information and information about report requests from Optimized Edge Routing (OER) application interface providers for the specified prefix.

traceroute

(Optional) Displays path information from traceroute probes.

exit-id

(Optional) Displays path information based on the OER assigned exit ID.

border-address

(Optional) Display path information sourced from the specified border router.

current

(Optional) Displays traceroute probe statistics from the most recent traceroute probe.

now

(Optional) Initiates a new traceroute probe and displays the statistics that are returned.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.3(8)T

This command was introduced.

12.3(14)T

Support for traceroute reporting was added.

12.4(6)T

The output was modified to support jitter and MOS reporting.

12.4(9)T

The inside keyword was added to support OER BGP inbound optimization.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

12.4(15)T

This command was modified. The report keyword was added to support the Performance Routing - Application Interface feature.

12.4(24)T

This command was modified. The output was modified to support the Protocol Independent Route Optimization (PIRO) feature.

15.0(1)M

This command was modified. The output was modified to support EIGRP route control.

12.2(33)SRE

This command was modified. The output was modified to support EIGRP route control and the PIRO feature.

Usage Guidelines

The show oer master prefix command is entered on a master controller. This command is used to display the status of monitored prefixes. The output from this command includes information about the source border router, current exit interface, prefix delay, and egress and ingress interface bandwidth. The output can be filtered to display information for only a single prefix, learned prefixes, inside prefixes, and prefixes learned based on delay or throughput.

The traceroute keyword is used to display traceroute probe results. The output generated by this keyword provides hop by hop statistics to the probe target network. The output can be filtered to display information only for the exit ID (OER assigns an ID number to each exit interface) or for the specified border router. The current keyword displays traceroute probe results from the most recent traceroute probe. The now keyword initiates a new traceroute probe and displays the results.

Examples

The following example shows the status of a monitored prefix:

Router# show oer master prefix 
OER Prefix Stats:
  Dly: Delay in ms
  EBw: Egress Bandwidth
  IBw: Ingress Bandwidth
Prefix      State     Curr BR   CurrI/F  Dly   EBw   IBw
----------------------------------------------------------
10.1.5.0/24 INPOLICY  10.1.1.2  Et1/0     19     1     1 

The table below describes the significant fields shown in the display.

Table 31 show oer master prefix Field Descriptions

Field

Description

Prefix

IP address and prefix length.

State

Status of the prefix.

Curr BR

Border router from which these statistics were gathered.

Curr I/F

Current exit link interface on the border router.

Dly

Delay in milliseconds.

EBw

Egress bandwidth.

IBw

Ingress bandwidth.

The following output shows the detailed status of a monitored prefix:

Router# show oer master prefix detail
 
Prefix: 10.1.1.0/26 
   State: DEFAULT*      Time Remaining: @7 
   Policy: Default 
   Most recent data per exit 
   Border          Interface           PasSDly  PasLDly  ActSDly  ActLDly 
  *10.2.1.1        Et1/0                   181      181      250      250 
   10.2.1.2        Et2/0                     0        0      351      351 
   10.3.1.2        Et3/0                     0        0       94      943 
   Latest Active Stats on Current Exit:
   Type     Target          TPort Attem Comps      DSum     Min     Max     Dly
   echo     10.1.1.1            N     2     2       448     208     240     224
   echo     10.1.1.2            N     2     2       488     228     260     244
   echo     10.1.1.3            N     2     2       568     268     300     284
Prefix performance history records
 Current index 2, S_avg interval(min) 5, L_avg interval(min) 60
Age       Border          Interface       OOP/RteChg Reasons 
Pas: DSum  Samples  DAvg  PktLoss Unreach    Ebytes    Ibytes      Pkts   Flows
Act: Dsum Attempts  DAvg    Comps Unreach
00:00:03  10.1.1.1        Et1/0
        0        0     0        0       0         0         0         0       0
     1504        6   250        6       0

The table below describes the significant fields shown in the display.

Table 32 show oer master prefix detail Field Descriptions

Field

Description

Prefix

IP address and prefix length.

State

Status of the prefix.

Time Remaining

Time remaining in the current prefix learning cycle.

Policy

The state that the prefix is in. Possible values are Default, In-policy, Out-of-policy, Choose, and Holddown.

Most recent data per exit

Border router exit link statistics for the specified prefix. The asterisk (*) character indicates the exit that is being used.

Latest Active Stats on Current Exit

Active probe statistics. This field includes information about the probe type, target IP address, port number, and delay statistics.

Type

The type of active probe. Possible types are ICMP echo, TCP connect, or UDP echo. The example uses default ICMP echo probes (default TCP), so no port number is displayed.

Prefix performance history records

Displays border router historical statistics. These statistics are updated about once a minute and stored for 1 hour.

The following example shows prefix statistics from a traceroute probing:

Router# show oer master prefix 10.1.5.0/24 traceroute 
* - current exit, + - control more specific
Ex - Exit ID, Delay in msec
--------------------------------------------------------------------------------
Path for Prefix: 10.1.5.0/24         Target: 10.1.5.2       
Exit ID: 2, Border: 10.1.1.3         External Interface: Et1/0    
Status: DONE, How Recent: 00:00:08 minutes old
Hop  Host            Time(ms) BGP 
1    10.1.4.2        8        0   
2    10.1.3.2        8        300 
3    10.1.5.2        20       50  
--------------------------------------------------------------------------------
Exit ID: 1, Border: 10.1.1.2         External Interface: Et1/0    
Status: DONE, How Recent: 00:00:06 minutes old
Hop  Host            Time(ms) BGP 
1    0.0.0.0         3012     0   
2    10.1.3.2        12       100 
3    10.1.5.2        12       50  
--------------------------------------------------------------------------------

The table below describes the significant fields shown in the display.

Table 33 show oer master prefix traceroute Field Descriptions

Field

Description

Path for Prefix

Specified IP address and prefix length.

Target

Traceroute probe target.

Exit ID

OER assigned exit ID.

Status

Status of the traceroute probe.

How Recent

Time since last traceroute probe.

Hop

Hop number of the entry.

Host

IP address of the entry.

Time

Time, in milliseconds, for the entry.

BGP

BGP autonomous system number for the entry.

The following example shows prefix statistics including Jitter and MOS percentage values when the Jitter probe is configured for the 10.1.5.0 prefix:

Router# show oer master prefix 10.1.5.0/24 
OER Prefix Statistics:
 Pas - Passive, Act - Active, S - Short term, L - Long term, Dly - Delay (ms),
 P - Percentage below threshold, Jit - Jitter, MOS - Mean Opinion Score,
 Los - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),
 E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicable
 U - unknown, * - uncontrolled, + - control more specific, @ - active probe all
Prefix                  State     Time Curr BR         CurrI/F         Protocol
                      PasSDly  PasLDly   PasSUn   PasLUn  PasSLos  PasLLos
                      ActSDly  ActLDly   ActSUn   ActLUn      EBw      IBw
                     %ActSJit %ActPMOS
--------------------------------------------------------------------------------
10.1.1.0/24          DEFAULT*       @3 10.1.1.1         Et5/0           U       
                            U        U        0        0        0        0
                            6        6   400000   400000       17        1
                         1.45       25

The table below describes the significant fields shown in the display that are different from the show oer master prefix Field Descriptions table and the show oer master prefix detail Field Descriptions table.

Table 34 show oer master prefix (Jitter and MOS) Field Descriptions

Field

Description

Protocol

Protocol: U (UDP).

PasSDly

Delay, in milliseconds, in short-term statistics from passive probe monitoring. If no statistics are reported, it displays U for unknown.

PasLDly

Delay, in milliseconds, in long-term statistics from passive probe monitoring. If no statistics are reported, it displays U for unknown.

PasSUn

Number of passively monitored short-term unreachable packets in flows-per-million.

PasLUn

Number of passively monitored long-term unreachable packets in flows-per-million.

PasSLos

Number of passively monitored short-term lost packets in packets-per-million.

PasLLos

Number of passively monitored long-term lost packets in packets-per-million.

ActSDly

Number of actively monitored short-term delay packets.

ActLDly

Number of actively monitored long-term delay packets.

ActSUn

Number of actively monitored short-term unreachable packets in flows-per-million.

ActLUn

Number of actively monitored long-term unreachable packets in flows-per-million.

ActSJit

Number of actively monitored short-term jitter packets.

ActPMOS

Number of actively monitored MOS packets with a percentage below threshold.

The following example shows detailed prefix statistics when Jitter or MOS are configured as a priority:

Router# show oer master prefix 10.1.1.0/24 detail 
Prefix: 10.1.1.0/24
   State: DEFAULT*    Time Remaining: @9
   Policy: Default
   Most recent data per exit
   Border          Interface         PasSDly  PasLDly  ActSDly  ActLDly
  *10.1.1.1        Et5/0                   0        0        6        6
   10.2.2.3        Et2/0                   0        0        7        7
   10.1.1.2        Et0/0                   0        0       14       14
   Most recent voice data per exit 
   Border          Interface         ActSJit  ActPMOS 
  *10.1.1.1        Et5/0                2.00        0
   10.2.2.3        Et2/0                2.01       20
   10.1.1.2        Et0/0                4.56       50
   Latest Active Stats on Current Exit:
   Type     Target          TPort Attem Comps    DSum     Min     Max     Dly
   udpJit   10.1.1.8         2000     2     2       8       4       4       4
   udpJit   10.1.1.7         3000     2     2      20       4      16      10
   udpJit   10.1.1.6         4000     2     2       8       4       4       4
   echo     10.1.1.4            N     2     0       0       0       0       0
   echo     10.1.1.3            N     2     0       0       0       0       0
   Latest Voice Stats on Current Exit:
   Type     Target          TPort     Codec Attem Comps  JitSum     MOS
   udpJit   10.1.1.8         2000  g711alaw     2     2    2.34    4.56
   udpJit   10.1.1.7         3000  g711ulaw     2     2    2.56    4.11
   udpJit   10.1.1.6         4000     g729a     2     2    1.54    3.57
   udpJit   10.1.1.5         4500      none     2     2    1.76      NA
Prefix performance history records
 Current index 3, S_avg interval(min) 5, L_avg interval(min) 60
Age       Border          Interface       OOP/RteChg Reasons                  
Pas: DSum  Samples  DAvg  PktLoss  Unreach   Ebytes   Ibytes     Pkts    Flows
Act: Dsum Attempts  DAvg    Comps  Unreach   Jitter LoMOSCnt    MOSCn
00:00:07  10.1.1.1        Et5/0                                               
        0        0     0        0        0     5920        0      148        1
       36       10     6        6        4        2        1        1
00:01:07  10.1.1.1        Et5/0                                               
        0        0     0        0        0    12000    12384      606       16
       36       10     6        6        4        3        0        1
00:02:07  10.1.1.1        Et5/0
        0        0     0        0        0   409540    12040      867        9
       36       10     6        6        4       15        1        1

The table below describes the significant fields shown in the display that are different from the show oer master prefix detail Field Descriptions table.

Table 35 show oer master prefix detail (Jitter or MOS Priority) Field Descriptions

Field

Description

Codec

Displays the codec value configured for MOS calculation. Codec values can be one of the following: g711alaw, g711ulaw, or g729a.

JitSum

Summary of jitter.

MOS

MOS value.

Jitter

Jitter value.

LoMOSCnt

MOS-low count.

The following example shows prefix statistics including information about application interface provider report requests for the 10.1.1.0 prefix:

Router# show oer master prefix 10.1.1.0/24 report
Prefix Performance Report Request
   Created by: Provider 1001, Host 10.3.3.3, Session 9
   Last report sent 3 minutes ago, context 589855, frequency 4 min
 
Prefix Performance Report Request
   Created by: Provider 1001, Host 10.3.3.4, Session 10
   Last report sent 1 minutes ago, context 655372, frequency 3 min
 
OER Prefix Statistics:
 Pas - Passive, Act - Active, S - Short term, L - Long term, Dly - Delay (ms),
 P - Percentage below threshold, Jit - Jitter (ms), 
 MOS - Mean Opinion Score
 Los - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),
 E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicable
 U - unknown, * - uncontrolled, + - control more specific, @ - active probe all
 # - Prefix monitor mode is Special, & - Blackholed Prefix
 % - Force Next-Hop, ^ - Prefix is denied
 
Prefix                  State     Time Curr BR         CurrI/F         Protocol
                      PasSDly  PasLDly   PasSUn   PasLUn  PasSLos  PasLLos
                      ActSDly  ActLDly   ActSUn   ActLUn      EBw      IBw
                      ActSJit  ActPMOS  ActSLos  ActLLos
--------------------------------------------------------------------------------
10.1.1.0/24             INPOLICY        0 10.3.3.3        Et4/3           BGP     
                               N        N        N        N        N        N
                             138      145        0        0        N        N
                               N        N

The table below describes the significant fields shown in the display that are different from the show oer master prefix Field Descriptions, show oer master prefix detail Field Descriptions and show oer master prefix (Jitter and MOS) Field Descriptions tables.

Table 36 show oer master prefix report Field Descriptions

Field

Description

Provider

Application interface provider ID.

Host

IP address of a host device in the application interface provider network.

Session

Session number automatically allocated by OER when an application interface provider initiates a session.

Last report sent

The number of minutes since a report was sent to the application interface provider.

ActSLos

Number of actively monitored short-term lost packets in packets-per-million.

ActLDly

Number of actively monitored long-term lost packets in packets-per-million.

In Cisco IOS Release 12.4(24)T, 12.2(33)SRE, and later releases, PIRO introduced the ability for OER to search for a parent route--an exact matching route, or a less specific route--in any IP Routing Information Base (RIB). The following example shows that the protocol displayed for the prefix 10.1.0.0 is RIB-PBR, which means that the parent route for the traffic class exists in the RIB and policy-based routing is used to control the prefix.

Router# show oer master prefix 10.1.0.0
OER Prefix Statistics:
 Pas - Passive, Act - Active, S - Short term, L - Long term, Dly - Delay (ms),
 P - Percentage below threshold, Jit - Jitter (ms), 
 MOS - Mean Opinion Score
 Los - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),
 E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicable
 U - unknown, * - uncontrolled, + - control more specific, @ - active probe all
 # - Prefix monitor mode is Special, & - Blackholed Prefix
 % - Force Next-Hop, ^ - Prefix is denied
Prefix                  State     Time Curr BR         CurrI/F         Protocol
                      PasSDly  PasLDly   PasSUn   PasLUn  PasSLos  PasLLos
                      ActSDly  ActLDly   ActSUn   ActLUn      EBw      IBw
                      ActSJit  ActPMOS  ActSLos  ActLLos
--------------------------------------------------------------------------------
10.1.0.0/24          INPOLICY        0 10.11.1.3       Et1/0           RIB-PBR     
                          129      130        0        0      214      473
                            U        U        0        0       33        3
                            N        N

In Cisco IOS Release 15.0(1)M, 12.2(33)SRE, and later releases, EIGRP route control introduced the ability for OER to search for a parent route--an exact matching route, or a less specific route--in the EIGRP routing table. In this example, the protocol displayed for the prefix 10.1.0.0 is EIGRP and this means that the parent route for the traffic class exists in the EIGRP routing table and OER is controlling the prefix.

Router# show oer master prefix 10.1.0.0
OER Prefix Statistics:
 Pas - Passive, Act - Active, S - Short term, L - Long term, Dly - Delay (ms),
 P - Percentage below threshold, Jit - Jitter (ms), 
 MOS - Mean Opinion Score
 Los - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),
 E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicable
 U - unknown, * - uncontrolled, + - control more specific, @ - active probe all
 # - Prefix monitor mode is Special, & - Blackholed Prefix
 % - Force Next-Hop, ^ - Prefix is denied
Prefix                  State     Time Curr BR         CurrI/F         Protocol
                      PasSDly  PasLDly   PasSUn   PasLUn  PasSLos  PasLLos
                      ActSDly  ActLDly   ActSUn   ActLUn      EBw      IBw
                      ActSJit  ActPMOS
--------------------------------------------------------------------------------
10.1.0.0/16           DEFAULT*      @69 10.1.1.1        Gi1/22          EIGRP    
                            U        U        0        0        0        0
                            U        U        0        0       22        8
                            N        N

Related Commands

Command

Description

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

set traceroute reporting

Configures an OER map to enable traceroute reporting.

traceroute probe-delay

Sets the time interval between traceroute probe cycles.

show oer master traffic-class

To display information about traffic classes that are monitored and controlled by an Optimized Edge Routing (OER) master controller, use the show oer master traffic-class command in privileged EXEC mode.

show oer master traffic-class [ access-list access-list-name | application application-name [ prefix] | inside | learned [ delay | inside | list list-name | throughput ] | prefix prefix | prefix-list prefix-list-name ] [ active] [ passive] [ status] [ detail]

Syntax Description

access-list

(Optional) Displays information about traffic classes defined by an access list.

access-list-name

(Optional) Name of an access list. Names cannot contain either a space or quotation marks and must begin with an alphabetic character to distinguish them from numbered access lists.

application

(Optional) Displays information about application traffic classes.

application-name

(Optional) Name of a predefined static application using fixed ports. See the table below.

prefix

(Optional) An IP address and bit length mask representing a prefix to be cleared.

inside

(Optional) Displays information about inside traffic classes.

learned

(Optional) Displays information about learned traffic classes.

delay

(Optional) Displays information about learned traffic classes defined using delay.

list

(Optional) Displays information about learned traffic classes defined in an OER learn list.

list-name

(Optional) Name of an OER learn list.

throughput

(Optional) Displays information about learned traffic classes defined using throughput.

prefix

(Optional) Displays information about traffic classes defined by a specified destination prefix.

prefix-list

(Optional) Displays information about traffic classes defined by a prefix list.

prefix-list-name

(Optional) Name of a prefix list. Names cannot contain either a space or quotation marks and must begin with an alphabetic character to distinguish them from numbered access lists.

active

(Optional) Displays active performance monitoring information only.

passive

(Optional) Displays passive performance monitoring information only.

status

(Optional) Displays status information only.

detail

(Optional) Displays detailed information.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.4(15)T

This command was introduced.

12.2(33)SXI4

This command was integrated into Cisco IOS Release 12.2(33)SXI4.

Usage Guidelines

The show oer master traffic-class command is entered on an OER master controller. This command is used to display information about traffic classes that are configured for monitoring and optimization. In Cisco IOS Release 12.4(15)T, new traffic-class and match traffic-classcommands were introduced to simplify the learning of traffic classes. In Cisco IOS Release 12.4(20)T, the ability to identify a traffic class using Network Based Application Recognition (NBAR) was introduced. Four types of traffic classes can be automatically learned using a traffic-classcommand in a learn list, or manually configured using a match traffic-classcommand in an OER map:

  • Traffic classes based on destination prefixes.
  • Traffic classes representing custom application definitions using access lists.
  • Traffic classes based on a static application mapping name with an optional prefix list filtering to define destination prefixes.
  • Traffic classes based on an NBAR-identified application mapping name with an optional prefix list filtering to define destination prefixes.

If none of the active, passive, or status keywords is specified, then the output will display the active, passive, and status information for the traffic classes. To restrict the amount of output, you can specify one or two of the active, passive, or status keywords, but the order of the keywords is important. If you specify the active keyword first then the passive or status keywords can be entered, if you specify the passive keyword first, then only the status keyword can be entered. The status keyword can be entered only by itself; the active and passive keywords are not accepted if they follow the status keyword. The optional detail keyword will display detailed output for the traffic classes.

To display information about traffic classes identified using NBAR, use the show oer master traffic-class application nbarcommand.

The table below displays the keywords that represent the application that can be configured with the show oer master traffic-classcommand. Replace the application-name argument with the appropriate keyword from the table.

Table 37 Static Application List Keywords

Keyword

Protocol

Port

cuseeme

TCP/UDP

7648 7649 7648 7649 24032

dhcp (Client)

UDP/TCP

68

dhcp (Server)

UDP/TCP

67

dns

UDP/TCP

53

finger

TCP

79

ftp

TCP

20 21

gopher

TCP/UDP

70

http

TCP/UDP

80

httpssl

TCP

443

imap

TCP/UDP

143 220

irc

TCP/UDP

194

kerberos

TCP/UDP

88 749

l2tp

UDP

1701

ldap

TCP/UDP

389

mssql

TCP

1443

nfs

TCP/UDP

2049

nntp

TCP/UDP

119

notes

TCP/UDP

1352

ntp

TCP/UDP

123

pcany

UDP TCP

22 5632 65301 5631

pop3

TCP/UDP

110

pptp

TCP

17233

simap

TCP/UDP

585 993 (Preferred)

sirc

TCP/UDP

994

sldap

TCP/UDP

636

smtp

TCP

25

snntp

TCP/UDP

563

spop3

TCP/UDP

123

ssh

TCP

22

telnet

TCP

23

Examples

The following example shows information about traffic classes destined for the 10.1.1.0/24 prefix:

Router# show oer master traffic-class
OER Prefix Statistics:
 Pas - Passive, Act - Active, S - Short term, L - Long term, Dly - Delay (ms),
 P - Percentage below threshold, Jit - Jitter (ms), 
 MOS - Mean Opinion Score
 Los - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),
 E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicable
 U - unknown, * - uncontrolled, + - control more specific, @ - active probe all
 # - Prefix monitor mode is Special, & - Blackholed Prefix
 % - Force Next-Hop, ^ - Prefix is denied
 
DstPrefix                   Appl_ID Dscp Prot     SrcPort     DstPort SrcPrefix         
           Flags             State     Time            CurrBR  CurrI/F Protocol
         PasSDly  PasLDly   PasSUn   PasLUn  PasSLos  PasLLos      EBw      IBw
         ActSDly  ActLDly   ActSUn   ActLUn  ActSJit  ActPMOS  ActSLos  ActLLos
--------------------------------------------------------------------------------
10.1.1.0/24               N defa    N           N           N N                 
               #          OOPOLICY       32         10.11.1.3    Et1/0      BGP
               N        N        N        N        N        N        N      IBwN
             130      134        0        0        N        N

The following example of the show oer master traffic-class command with the inside keyword shows information about traffic classes:

Router# show oer master traffic-class inside
OER Prefix Statistics:
 Pas - Passive, Act - Active, S - Short term, L - Long term, Dly - Delay (ms),
 P - Percentage below threshold, Jit - Jitter (ms), 
 MOS - Mean Opinion Score
 Los - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),
 E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicable
 U - unknown, * - uncontrolled, + - control more specific, @ - active probe all
 # - Prefix monitor mode is Special, & - Blackholed Prefix
 % - Force Next-Hop, ^ - Prefix is denied
 
DstPrefix (inside)  Appl_ID Dscp Prot     SrcPort     DstPort SrcPrefix         
           Flags             State     Time            CurrBR  CurrI/F Protocol
         PasSDly  PasLDly   PasSUn   PasLUn  PasSLos  PasLLos      EBw      IBw
         ActSDly  ActLDly   ActSUn   ActLUn  ActSJit  ActPMOS  ActSLos  ActLLos
--------------------------------------------------------------------------------
10.0.0.0/16               N    N    N           N           N N                 
                          DEFAULT*        0                 U                 U 

The table below describes the significant fields shown in the display.

Table 38 show oer master traffic-class Field Descriptions

Field

Description

DstPrefix

Destination IP address and prefix length for the traffic class.

Appl_ID

Application ID.

Dscp

Differentiated Services Code Point (DSCP) value.

Prot

Protocol.

SrcPort

Source port number for the traffic class.

DstPort

Destination port number for the traffic class.

SrcPrefix

IP address of the traffic class source.

Flags

Special characteristics for the traffic class.

State

Current state of the traffic class.

Time

Time, in seconds, between monitoring messages.

Curr BR

IP address of the border router through which this traffic class is being currently routed.

CurrI/F

Interface of the border router through which this traffic class is being currently routed.

Protocol

Protocol. A value of U means unknown; there is no measurement data.

PasSDly

Passive monitoring short term delay in milliseconds.

PasLDly

Passive monitoring long term delay in milliseconds.

PasSUn

Number of passively monitored short-term unreachable packets in flows per million.

PasLUn

Number of passively monitored long-term unreachable packets in flows per million.

PasSLos

Number of passively monitored short-term lost packets in packets per million.

PasLLos

Number of passively monitored long-term lost packets in packets per million.

EBw

Egress bandwidth.

IBw

Ingress bandwidth.

ActSDly

Active monitoring short-term delay in milliseconds.

ActLDly

Active monitoring long-term delay in milliseconds.

ActSUn

Number of actively monitored short-term unreachable packets in flows per million.

ActLUn

Number of actively monitored long-term unreachable packets in flows per million.

ActSJit

Number of actively monitored short-term jitter packets.

ActPMOS

Number of actively monitored Mean Opinion Score (MOS) packets with a percentage below threshold.

ActSLos

Number of actively monitored short-term packets lost.

ActLLos

Number of actively monitored long-term packets lost.

Related Commands

Command

Description

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

show oer master traffic-class application nbar

Displays information about application traffic classes that are identified using NBAR and are monitored and controlled by an OER master controller.

show oer master traffic-class application nbar

To display information about application traffic classes that are identified using Network-Based Application Recognition (NBAR) and are monitored and controlled by an Optimized Edge Routing (OER) master controller, use the show oer master traffic-class application nbar command in privileged EXEC mode.

show oer master traffic-class application nbar nbar-appl-name [ prefix] [ [ active passive status ] | detail ]

Syntax Description

nbar-appl-name

Name of a dynamic application identified using NBAR. See the Usage Guidelines section for more details.

prefix

(Optional) An IP address and bit length mask representing a prefix.

active

(Optional) Displays active performance monitoring information only.

passive

(Optional) Displays passive performance monitoring information only.

status

(Optional) Displays status information only.

detail

(Optional) Displays detailed information.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.4(20)T

This command was introduced.

Usage Guidelines

The show oer master traffic-class application nbar command is entered on an OER master controller. This command is used to display information about application traffic classes that are identified using NBAR. To display information about traffic classes defined using static application mapping, use the show oer master traffic-classcommand.

The optional detail keyword will display detailed output for the NBAR application traffic classes. If the detail keyword is not specified, and if none of the active, passive, or status keywords is specified, then the output will display the active, passive, and status information for the traffic classes. To restrict the amount of output, specify just one or two of the active, passive, or status keywords. If specified, the active, passive, or status keywords must be specified in the order shown in the syntax.

NBAR is capable of identifying applications based on the following three types of protocols:

  • Non-UDP and Non-TCP IP protocols--For example, Generic Routing Encapsulation (GRE), and Internet Control Message Protocol (ICMP).
  • TCP and UDP protocols that use statically assigned port numbers--For example, CU-SeeMe desktop video conference (CU-SeeMe-Server) andPost Office Protocol over Transport Layer Security (TLS) and Secure Sockets Layer (SSL) server (SPOP3-Server).
  • TCP and UDP protocols that dynamically assign port numbers and require stateful inspection--For example, Real-Time Transport Protocol audio streaming (RTP-audio) and BitTorrent File Transfer Traffic (BitTorrent).

The list of applications identified using NBAR and available for profiling OER or Performance Routing traffic classes is constantly evolving. For lists of many of the NBAR applications defined using static or dynamically assigned ports, see the Using Performance Routing to Profile the Traffic Classes module.

For more details about NBAR, see the Classifying Network Traffic Using NBAR section of the Cisco IOS Quality of Service Solutions Configuration Guide .

If the prefix argument is specified, only the OER-controlled traffic class that matches the application specified by the nbar-appl-name argument and the destination prefix specified by the prefix argument are displayed. If the prefix argument is not specified, all OER-controlled traffic classes that match the application specified by the nbar-appl-name argument, regardless of the destination prefix, are displayed.

Examples

The following example shows information about traffic classes consisting of Real-time Transport Protocol streaming audio (RTP-audio) traffic:

Router# show oer master traffic-class application nbar rtp-audio
OER Prefix Statistics:
 Pas - Passive, Act - Active, S - Short term, L - Long term, Dly - Delay (ms),
 P - Percentage below threshold, Jit - Jitter (ms), 
 MOS - Mean Opinion Score
 Los - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),
 E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicable
 U - unknown, * - uncontrolled, + - control more specific, @ - active probe all
 # - Prefix monitor mode is Special, & - Blackholed Prefix
 % - Force Next-Hop, ^ - Prefix is denied
DstPrefix           Appl_ID Dscp Prot     SrcPort     DstPort SrcPrefix         
           Flags             State     Time            CurrBR  CurrI/F Protocol
         PasSDly  PasLDly   PasSUn   PasLUn      EBw      IBw
         ActSDly  ActLDly   ActSUn   ActLUn  ActSJit  ActPMOS
--------------------------------------------------------------------------------
100.1.1.0/28      RTP-Audio defa    N           N           N 0.0.0.0/0         
                          DEFAULT*      461         101.1.1.2    Et1/0        U
               U        U        0        0        1        2
             150      130        0        0       15        0
100.1.1.16/28     RTP-Audio defa    N           N           N 0.0.0.0/0         
                          DEFAULT*      461         101.1.1.2    Et1/0        U
               U        U        0        0        1        2
             250      200        0        0       30        0

The table below describes the significant fields shown in the display.

Table 39 show oer master traffic-class Field Descriptions

Field

Description

DstPrefix

Destination IP address and prefix length for the traffic class.

Appl_ID

Application ID. The application can be a static application or an NBAR identified application.

Dscp

Differentiated Services Code Point (DSCP) value.

Prot

Protocol.

SrcPort

Source port number for the traffic class.

DstPort

Destination port number for the traffic class.

SrcPrefix

IP address of the traffic class source.

Flags

Special characteristics for the traffic class, see the key above for details.

State

Current state of the traffic class.

Time

Time, in seconds, between monitoring messages.

Curr BR

IP address of the border router through which this traffic class is being currently routed.

CurrI/F

Interface of the border router through which this traffic class is being currently routed.

Protocol

Protocol. If the traffic class is being controlled by OER this field displays on of the following: BGP, STATIC, or CCE. A value of U means unknown; OER is not controlling the traffic class.

PasSDly

Passive monitoring short term delay in milliseconds.

PasLDly

Passive monitoring long term delay in milliseconds.

PasSUn

Number of passively monitored short term unreachable packets in flows-per-million.

PasLUn

Number of passively monitored long term unreachable packets in flows-per-million.

PasSLos

Number of passively monitored short term lost packets in packets-per-million.

PasLLos

Number of passively monitored long term lost packets in packets-per-million.

EBw

Egress bandwidth.

IBw

Ingress bandwidth.

ActSDly

Active monitoring short term delay in milliseconds.

ActLDly

Active monitoring long term delay in milliseconds.

ActSUn

Number of actively monitored short term unreachable packets in flows-per-million.

ActLUn

Number of actively monitored long term unreachable packets in flows-per-million.

ActSJit

Number of actively monitored short term jitter packets.

ActPMOS

Number of actively monitored Mean Opinion Score (MOS) packets with a percentage below threshold.

Related Commands

Command

Description

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

show oer master traffic-class

Displays information about traffic classes that are monitored and controlled by an OER master controller.

show oer proxy


Note


Effective with Cisco IOS Release 15.0(1)SY, the show oer proxy command is hidden. Although this command is still available in Cisco IOS software, the CLI interactive Help does not display it if you attempt to view it by entering a question mark at the command line. This command will be completely removed in a future release.

To display Optimized Edge Routing (OER) proxy information, use the show oer proxy command in privileged EXEC mode.

show oer proxy

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.2(33)SRB

This command was introduced.

12.2(33)SXI

This command was integrated into Cisco IOS Release 12.2(33)SXI.

12.4(24)T

This command was integrated into Cisco IOS Release 12.4(24)T.

15.0(1)SY

This command was modified. This command was hidden.

Examples

The following is sample output from the show oer proxy command:

Router# show oer proxy
 
OER PROXY 0.0.0.0 DISABLED, MC 0.0.0.0 UP/DOWN: DOWN
  Conn Status: NOT OPEN, Port 3949

The table below describes the significant fields shown in the display.

Table 40 show oer proxy Field Descriptions

Field

Description

OER PROXY

Displays the IP address and the status of the OER proxy.

MC

Displays the IP address of the master controller (MC).

UP/DOWN

Displays the connection status: UP or DOWN.

Conn Status

Displays the connection status: OPEN or NOT OPEN.

Port

Displays the TCP port number used to communicate with the master controller.

Related Commands

Command

Description

show oer api

Displays information about OER application interface clients.

shutdown (OER)


Note


Effective with Cisco IOS Release 15.0(1)SY, the shutdown command is hidden. Although this command is still available in Cisco IOS software, the CLI interactive Help does not display it if you attempt to view it by entering a question mark at the command line. This command will be completely removed in a future release.

To stop an Optimized Edge Routing (OER) master controller or OER border router process without removing the OER process configuration, use the shutdown command in OER master controller or OER border router configuration mode. To start a stopped OER process, use the no form of this command.

shutdown
no shutdown

Syntax Description

This command has no arguments or keywords.

Command Default

No master controller or border router is stopped.

Command Modes

  OER border router configuration (config-oer-br)
OER master controller configuration (config-oer-mc)

Command History

Release

Modification

12.3(8)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

12.2SX

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

15.0(1)SY

This command was modified. This command was hidden.

Usage Guidelines

The shutdown command is entered on a master controller or border router. Entering the shutdown command stops an active master controller or border router process but does not remove any configuration parameters. The shutdowncommand is displayed in the running configuration file when enabled. To disable a master controller or border router and completely remove the process configuration from the running configuration file, use the no oer master or no oer border command in global configuration mode.

Cisco IOS Release 12.2(33)SXH

This command is supported only in OER border router configuration mode.

Examples

The following example stops an active OER border router session:

Router(config)# oer border
Router(config-oer-br)# shutdown

The following example starts an inactive OER master controller session:

Router(config)# oer master
Router(config-oer-mc)# no shutdown

Related Commands

Command

Description

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

throughput

To configure Optimized Edge Routing (OER) to learn the top prefixes based on the highest outbound throughput, use the throughput command in Top Talker and Top Delay learning configuration mode or learn list configuration mode. To disable learning based on outbound throughput, use the no form of this command.

throughput
no throughput

Syntax Description

This command has no arguments or keywords.

Command Default

None

Command Modes

Learn list configuration (config-oer-mc-learn-list) Top Talker and Top Delay learning configuration (config-oer-mc-learn)

Command History

Release

Modification

12.3(8)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

12.4(15)T

Support for the learn list configuration mode was added to this command.

Usage Guidelines

The throughput command is entered on a master controller. The master controller creates a list of prefixes based on the highest outbound throughput. This command is used to configure a master controller to learn prefixes based on the highest outbound packet throughput. When this command is enabled, OER will learn the top prefixes across all border routers according to the highest outbound throughput.

Examples

Top Talker and Top Delay Learning Configuration Mode

The following example shows how to configure a master controller to learn the top prefixes based on the highest outbound throughput:

Router(config)# oer master
Router(config-oer-mc)# learn
Router(config-oer-mc-learn)# throughput

Learn List Configuration Mode

The following example shows how to configure a master controller to learn top prefixes based on the highest throughput for a learn list named LEARN_REMOTE_LOGIN_TC that learns Telnet and Secure Shell (SSH) application TCF entries:

Router(config)# oer master 
Router(config-oer-mc)# learn 
Router(config-oer-mc-learn)# list seq 10 refname LEARN_REMOTE_LOGIN_TC
Router(config-oer-mc-learn-list)# traffic-class application telnet ssh
Router(config-oer-mc-learn-list)# aggregation-type prefix-length 24 
Router(config-oer-mc-learn-list)# throughput

Related Commands

Command

Description

learn

Enters OER Top Talker and Top Delay learning configuration mode to configure prefixes for OER to learn.

list (OER)

Creates an OER learn list to specify criteria for learning traffic classes and enters learn list configuration mode.

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

traceroute probe-delay

To set the time interval between traceroute probe cycles, use the traceroute probe-delaycommand in Optimized Edge Routing (OER) master controller configuration mode. To set the interval between probes to the default value, use the no form of this command.

traceroute probe-delay milliseconds
no traceroute probe-delay milliseconds

Syntax Description

milliseconds

Configures the time interval, in milliseconds, between traceroute probes. The configurable range for this argument is a number from 0 to 65535.

Command Default

The following value is used when this command is not configured or the no form is entered:

milliseconds : 1000

Command Modes

OER master controller configuration

Command History

Release

Modification

12.3(14)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

Usage Guidelines

The traceroute probe-delay command is entered on a master controller. This command is used to set the delay interval between traceroute probes.

Continuous and policy based traceroute reporting is configured with the set traceroute reporting OER map configuration mode command. The time interval between traceroute probes is configured with the traceroute probe-delay command in OER master controller configuration mode. On-demand traceroute probes are triggered by entering the show oer master prefix command with the current and now keywords.

Examples

The following example, which starts in global configuration mode, sets the delay interval between traceroute probes to 10000 milliseconds:

Router(config)# oer master 
Router(config-oer-mc)# traceroute probe-delay 10000 

Related Commands

Command

Description

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

set traceroute reporting

Configures an OER map to enable traceroute reporting.

show oer master prefix

Displays the status of monitored prefixes.

traffic-class access-list

To define an Optimized Edge Routing (OER) application traffic class using an access list applied to learned traffic flows, use the traffic-class access-list command in learn list configuration mode. To disable the definition of OER learned traffic flows into application traffic classes using an access list, use the no form of this command.

traffic-class access-list access-list-name [ filter prefix-list-name ]
no traffic-class access-list

Syntax Description

access-list-name

Name of an access list. Names cannot contain either a space or quotation marks and must begin with an alphabetic character to distinguish them from numbered access lists.

filter

(Optional) Specifies that the traffic flows are filtered on the basis of a prefix list.

prefix-list-name

(Optional) Name of a prefix list (created using the ip prefix-list command).

Command Default

OER application traffic classes are not defined using an access list.

Command Modes

Learn list configuration (config-oer-mc-learn-list)

Command History

Release

Modification

12.4(15)T

This command was introduced.

Usage Guidelines

The traffic-class access-list command is used to configure the master controller to automatically learn application traffic defined in an access list. Only one access list can be specified, but the access list may contain many access list entries (ACEs) to help define the traffic class parameters.

In Cisco IOS Release 12.4(15)T, the learn list configuration mode was introduced. Learn lists are a way to categorize learned traffic classes. In each learn list, different criteria for learning traffic classes including prefixes, application definitions, filters, and aggregation parameters can be configured. A traffic class is automatically learned by OER based on each learn list criteria, and each learn list is configured with a sequence number. The sequence number determines the order in which learn list criteria are applied. Learn lists allow different OER policies to be applied to each learn list; in previous releases the traffic classes could not be divided, and an OER policy was applied to all the traffic classes.


Note


The traffic-class access-list command, the traffic-class application command, and the traffic-class prefix-list commands are all mutually exclusive in an OER learn list. Only one of these commands can be specified per OER learn list.

Examples

The following example, starting in global configuration mode, shows how to define a custom application traffic class using an access list. Every entry in the access list defines one application, and the destination network of the traffic class is determined by the specified aggregation method. After the access list is configured, the master controller automatically learns the defined application traffic based on highest throughput. A prefix list may be used to filter the traffic flows by destination prefix.

Router(config)# ip access-list extended USER_DEFINED_TC
Router(config-ext-nacl)# permit tcp any any 500
Router(config-ext-nacl)# permit tcp any any range 700 750
Router(config-ext-nacl)# permit udp 10.1.1.1 0.0.0.0 any 
Router(config-ext-nacl)# permit ip any any dscp ef 
Router(config-ext-nacl)# exit
Router(config)# oer master 
Router(config-oer-mc)# learn 
Router(config-oer-mc-learn)# list seq 10 refname LEARN_USER_DEFINED_TC 
Router(config-oer-mc-learn-list)# traffic-class access-list USER_DEFINED_TC
Router(config-oer-mc-learn-list)# aggregation-type prefix-length 24 
Router(config-oer-mc-learn-list)# throughput 
Router(config-oer-mc-learn-list)# end 

Related Commands

Command

Description

aggregation-type

Configures an OER master controller to aggregate learned prefixes based on the type of traffic flow.

learn

Enters OER Top Talker and Top Delay learning configuration mode to configure prefixes for OER to learn.

list (OER)

Creates an OER learn list to specify criteria for learning traffic classes and enters learn list configuration mode.

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

traffic-class aggregate

To aggregate Optimized Edge Routing (OER) learned traffic flows into application traffic classes using an access list, use the traffic-class aggregate command in OER Top Talker and Top Delay learning configuration mode. To disable the aggregation of OER learned traffic flows into application traffic classes using an access list, use the no form of this command.

traffic-class aggregate access-list access-list-name
no traffic-class aggregate access-list access-list-name

Syntax Description

access-list

Specifies that an IP access list is to be used to aggregate the OER learned traffic flows into application traffic classes.

access-list-name

Name of the access list. Names cannot contain either a space or quotation marks and must begin with an alphabetic character to distinguish them from numbered access lists.

Command Default

OER learned traffic flows are not aggregated into application traffic classes using an access list.

Command Modes

OER Top Talker and Top Delay learning configuration

Command History

Release

Modification

12.4(9)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

Usage Guidelines

The traffic-class aggregate command can be used with the traffic-class filter and traffic-class keys commands to configure the master controller to automatically learn defined application traffic. Only one access list can be specified, but the access list may contain many access list entries (ACEs) to help define the traffic class parameters.


Note


The traffic-class aggregate command is different from the aggregation-type command that aggregates learned prefixes based on the type of traffic flow. The traffic-class aggregate command introduces the ability to use an access list to aggregate learned traffic flows to create an application traffic class. Both commands can be used in the same configuration.

Examples

The following example, starting in global configuration mode, configures the master controller to automatically learn defined application traffic. In this example, two access lists are created to identify and define voice traffic in the network. Using the traffic-class aggregate and the traffic-class filter commands with the access lists, only voice traffic with a Differentiated Services Code Point (DSCP) bit set to ef, a User Datagram Protocol (UDP), and a destination port in the range of 3000 to 4000 is learned and added to the OER application database on the master controller.

Router(config)# ip access-list extended voice-filter-acl
Router(config-ext-nacl)# permit udp any 10.1.0.0 0.0.255.255 dscp ef
 
Router(config-ext-nacl)# exit
Router(config)# ip access-list extended voice-agg-acl
Router(config-ext-nacl)# permit udp any any range 3000 4000 dscp ef
 
Router(config-ext-nacl)# exit
Router(config)# oer master
 
Router(config-oer-master)# learn
 
Router(config-oer-master-learn)# aggregation-type prefix-length 24
 
Router(config-oer-master-learn)# throughput
 
Router(config-oer-master-learn)# traffic-class filter access-list voice-filter-acl
 
Router(config-oer-master-learn)# traffic-class aggregate access-list voice-agg-acl 
Router(config-oer-master-learn)# traffic-class keys protocol dport dscp
Router(config-oer-master-learn)# end

Related Commands

Command

Description

aggregation-type

Configures an OER master controller to aggregate learned prefixes based on the type of traffic flow.

learn

Enters OER Top Talker and Top Delay learning configuration mode to configure prefixes for OER to learn.

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

traffic-class filter

Filters uninteresting traffic from OER learned traffic flows using an access list.

traffic-class keys

Specifies a key list used by an OER border router to aggregate the traffic flows into learned application classes.

traffic-class application

To define an Optimized Edge Routing (OER) traffic class using a predefined static application, use the traffic-class application command in learn list configuration mode. To remove the definition of an OER learned traffic class using a predefined static application, use the no form of this command.

traffic-class application application-name [ filter prefix-list-name ]
no traffic-class application application-name [ filter prefix-list-name ]

Syntax Description

application-name

Name of a predefined static application using fixed ports. See the table below.

filter

(Optional) Specifies that the traffic flows are filtered on the basis of a prefix list.

prefix-list-name

(Optional) Name of a prefix list (created using the ip prefix-list command).

Command Default

OER traffic classes are not defined using a static application mapping.

Command Modes

Learn list configuration (config-oer-mc-learn-list)

Command History

Release

Modification

12.4(15)T

This command was introduced.

Usage Guidelines

The traffic-class application command is used to configure the master controller to automatically learn traffic using a keyword that represents an application. OER maps the application keyword to a protocol--TCP or UDP, or both--and one or more ports and this mapping is shown in the table below. More than one application can be configured as part of the traffic class.

In Cisco IOS Release 12.4(15)T, the learn list configuration mode was introduced. Learn lists are a way to categorize learned traffic classes. In each learn list, different criteria for learning traffic classes including prefixes, application definitions, filters, and aggregation parameters can be configured. A traffic class is automatically learned by OER based on each learn list criteria, and each learn list is configured with a sequence number. The sequence number determines the order in which learn list criteria are applied. Learn lists allow different OER policies to be applied to each learn list; in previous releases, the traffic classes could not be divided, and an OER policy was applied to all the traffic classes.


Note


The traffic-class access-list command, the traffic-class application command, the traffic-class application nbar command, and the traffic-class prefix-list commands are all mutually exclusive in an OER learn list. Only one of these commands can be specified per OER learn list.

The table below displays the keywords that represent the application that can be configured with the traffic-class application command. Replace the application-name argument with the appropriate keyword from the table.

Table 41 Static Application List Keywords

Keyword

Protocol

Port

cuseeme

TCP UDP

7648 7649 7648 7649 24032

dhcp (Client)

UDP/TCP

68

dhcp (Server)

UDP/TCP

67

dns

UDP/TCP

53

finger

TCP

79

ftp

TCP

20 21

gopher

TCP/UDP

70

http

TCP/UDP

80

httpssl

TCP

443

imap

TCP/UDP

143 220

irc

TCP/UDP

194

kerberos

TCP/UDP

88 749

l2tp

UDP

1701

ldap

TCP/UDP

389

mssql

TCP

1443

nfs

TCP/UDP

2049

nntp

TCP/UDP

119

notes

TCP/UDP

1352

ntp

TCP/UDP

123

pcany

UDP TCP

22 5632 65301 5631

pop3

TCP/UDP

110

pptp

TCP

17233

simap

TCP/UDP

585 993 (Preferred)

sirc

TCP/UDP

994

sldap

TCP/UDP

636

smtp

TCP

25

snntp

TCP/UDP

563

spop3

TCP/UDP

123

ssh

TCP

22

telnet

TCP

23

Examples

The following example, starting in global configuration mode, shows how to define application traffic classes using two OER learn lists, LEARN_REMOTE_LOGIN_TC and LEARN_FILE_TRANSFER_TC. The number of traffic classes to be learned in both learn list sessions is set to 50, and the maximum number of traffic classes to be learned for all sessions of the learn list is set to 90. The remote login traffic class is configured using keywords representing Telnet and Secure Shell (SSH) traffic and the resulting prefixes are aggregated to a prefix length of 24. The file transfer traffic class is configured using a keyword that represents FTP and is also aggregated to a prefix length of 24. A prefix-list is applied to the file transfer traffic class to permit traffic from the 10.0.0.0/8 prefix. The master controller is 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.

Router(config)# ip prefix-list INCLUDE_10_NET 10.0.0.0/8
Router(config)# oer master 
Router(config-oer-mc)# learn 
Router(config-oer-mc-learn)# list seq 10 refname LEARN_REMOTE_LOGIN_TC
Router(config-oer-mc-learn-list)# count 50 max 90
Router(config-oer-mc-learn-list)# traffic-class application telnet ssh
Router(config-oer-mc-learn-list)# aggregation-type prefix-length 24 
Router(config-oer-mc-learn-list)# throughput 
Router(config-oer-mc-learn-list)# exit
Router(config-oer-mc-learn)# list seq 20 refname LEARN_FILE_TRANSFER_TC
Router(config-oer-mc-learn-list)# count 50 max 90
Router(config-oer-mc-learn-list)# traffic-class application ftp filter INCLUDE_10_NET
Router(config-oer-mc-learn-list)# aggregation-type prefix-length 24 
Router(config-oer-mc-learn-list)# throughput
Router(config-oer-mc-learn-list)# end

Related Commands

Command

Description

aggregation-type

Configures an OER master controller to aggregate learned prefixes based on the type of traffic flow.

learn

Enters OER Top Talker and Top Delay learning configuration mode to configure prefixes for OER to learn.

list (OER)

Creates an OER learn list to specify criteria for learning traffic classes and enters learn list configuration mode.

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

traffic-class application nbar

Defines an OER traffic class using an NBAR application mapping.

traffic-class application nbar

To define an Optimized Edge Routing (OER) traffic class using an Network-Based Application Recognition (NBAR) application mapping, use the traffic-class application nbar command in learn list configuration mode. To remove the definition of an OER learned traffic class using an application identified using NBAR, use the no form of this command.

traffic-class application nbar nbar-appl-name [ nbar-appl-name . . . ] [ filter prefix-list-name ]
no traffic-class application nbar [ nbar-appl-name . . . ]

Syntax Description

nbar-appl-name

Keyword representing the name of a dynamic application identified using NBAR. One application must be specified, but the ellipses show that more than one application keyword can be specified, up to a maximum of ten. See the Usage Guidelines section for more details.

filter

(Optional) Specifies that the traffic flows are filtered on the basis of a prefix list.

prefix-list-name

(Optional) Name of a prefix list (created using the ip prefix-list command).

Command Default

OER traffic classes are not defined using an NBAR application mapping.

Command Modes

Learn list configuration (config-oer-mc-learn-list)

Command History

Release

Modification

12.4(20)T

This command was introduced.

Usage Guidelines

The traffic-class application nbar command is used to configure the master controller to automatically learn traffic using a keyword that represents an application that can be identified using NBAR. More than one application can be configured as part of the traffic class with a maximum of ten applications entered per command line. Enter multiple traffic-class application nbar command statements if you need to specify more than ten applications.

NBAR is capable of identifying applications based on the following three types of protocols:

  • Non-UDP and Non-TCP IP protocols--For example, Generic Routing Encapsulation (GRE), and Internet Control Message Protocol (ICMP).
  • TCP and UDP protocols that use statically assigned port numbers--For example, CU-SeeMe desktop video conference (CU-SeeMe-Server) andPost Office Protocol over Transport Layer Security (TLS) and Secure Sockets Layer (SSL) server (SPOP3-Server).
  • TCP and UDP protocols that dynamically assign port numbers and require stateful inspection--For example, Real-Time Transport Protocol audio streaming (RTP-audio) and BitTorrent File Transfer Traffic (BitTorrent).

Use the traffic-class application nbar ? command to determine if an application can be identified using NBAR and replace the nbar-appl-name argument with the appropriate keyword from the screen display.

The list of applications identified using NBAR and available for profiling of OER or Performance Routing traffic classes is constantly evolving. For lists of many of the NBAR applications defined using static or dynamically assigned ports, see the Using Performance Routing to Profile the Traffic Classes module.

For more details about NBAR, see the Classifying Network Traffic Using NBAR section of the Cisco IOS Quality of Service Solutions Configuration Guide .

In Cisco IOS Release 12.4(15)T, the learn list configuration mode was introduced. Learn lists are a way to categorize learned traffic classes. In each learn list, different criteria for learning traffic classes including prefixes, application definitions, filters, and aggregation parameters can be configured. A traffic class is automatically learned by OER based on each learn list criteria, and each learn list is configured with a sequence number. The sequence number determines the order in which learn list criteria are applied. Learn lists allow different OER policies to be applied to each learn list; in previous releases, the traffic classes could not be divided, and an OER policy was applied to all the traffic classes.


Note


The traffic-class access-list command, the traffic-class application command, the traffic-class application nbar command, and the traffic-class prefix-list commands are all mutually exclusive in an OER learn list. Only one of these commands can be specified per OER learn list.

Examples

The following example, starting in global configuration mode, shows how to define application traffic classes identified by using NBAR and two OER learn lists, LEARN_VOICE_TC and LEARN_VIDEO_TC. The number of traffic classes to be learned in both learn list sessions is 50, and the maximum number of traffic classes to be learned for all sessions of the learn list is 90.

The Voice over IP (VoIP) traffic class is configured using keywords representing RTP-Audio and the resulting prefixes are aggregated to a prefix length of 24. The video traffic class is configured using a keyword that represents RTP-video and is also aggregated to a prefix length of 24. A prefix list is applied to the video traffic class to match traffic for the destination prefix of 10.0.0.0/8. The master controller is configured to learn the top prefixes based on highest outbound throughput for the learned traffic, and the resulting traffic classes are added to the OER application database.

The traffic streams that the learn list profiles for both the RTP-audio and the RTP-video applications are:

10.1.1.1
10.1.2.1
20.1.1.1
20.1.2.1

The traffic classes that are learned for each application are:

10.1.1.0/24 rtp-audio
10.1.2.0/24 rtp-audio
20.1.1.0/24 rtp-audio
20.1.2.0/24 rtp-audio
10.1.1.0/24 rtp-video
10.1.2.0/24 rtp-video

The difference in traffic classes learned is due to the optional INCLUDE_10_NET prefix list that only includes RTP-video application traffic with a destination prefix that matches the prefix 10.0.0.0/8.

Router(config)# ip prefix-list INCLUDE_10_NET 10.0.0.0/8
Router(config)# oer master 
Router(config-oer-mc)# learn 
Router(config-oer-mc-learn)# list seq 10 refname LEARN_VOICE_TC
Router(config-oer-mc-learn-list)# count 50 max 90
Router(config-oer-mc-learn-list)# traffic-class application nbar rtp-audio
Router(config-oer-mc-learn-list)# aggregation-type prefix-length 24 
Router(config-oer-mc-learn-list)# throughput 
Router(config-oer-mc-learn-list)# exit
Router(config-oer-mc-learn)# list seq 20 refname LEARN_VIDEO_TC
Router(config-oer-mc-learn-list)# count 50 max 90
Router(config-oer-mc-learn-list)# traffic-class application nbar rtp-video
filter INCLUDE_10_NET
Router(config-oer-mc-learn-list)# aggregation-type prefix-length 24 
Router(config-oer-mc-learn-list)# throughput
Router(config-oer-mc-learn-list)# end

Related Commands

Command

Description

aggregation-type

Configures an OER master controller to aggregate learned prefixes based on the type of traffic flow.

learn

Enters OER Top Talker and Top Delay learning configuration mode to configure prefixes for OER to learn.

list (OER)

Creates an OER learn list to specify criteria for learning traffic classes and enters learn list configuration mode.

match traffic-class application nbar

Defines a match clause using an NBAR application mapping in an OER map to create a traffic class.

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

traffic-class filter

To filter uninteresting traffic from Optimized Edge Routing (OER) learned traffic flows using an access list, use the traffic-class filter command in OER Top Talker and Top Delay learning configuration mode. To disable the filtering of OER learned traffic flows using an access list, use the no form of this command.

traffic-class filter access-list access-list-name
no traffic-class filter access-list access-list-name

Syntax Description

access-list

Specifies that an IP access list is to be used to filter uninteresting traffic from OER learned traffic flows.

access-list-name

Name of the access list. Names cannot contain either a space or quotation marks and must begin with an alphabetic character to distinguish them from numbered access lists.

Command Default

Uninteresting traffic is not filtered from OER traffic flows using an access list.

Command Modes

OER Top Talker and Top Delay learning configuration

Command History

Release

Modification

12.4(9)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

Usage Guidelines

OER is used to optimize the performance of selected traffic flows in your network. While defining the selected traffic flows, this command is used to filter out traffic that you are not interested in optimizing.

The traffic-class filter command can be used with the traffic-class aggregate and traffic-class keys commands to configure the master controller to automatically learn defined application traffic. Only one access list can be specified, but the access list may contain many access list entries (ACEs) to help define the traffic class parameters.

Examples

The following example, starting in global configuration mode, configures the master controller to automatically learn defined application traffic. In this example, two access lists are created to identify and define voice traffic in the network. Using the traffic-class aggregate and the traffic-class filter commands with the access lists, only voice traffic with a Differentiated Services Code Point (DSCP) bit set to ef, a User Datagram Protocol (UDP), and a destination port in the range of 3000 to 4000 is learned and added to the OER application database on the master controller.

Router(config)# ip access-list extended voice-filter-acl
Router(config-ext-nacl)# permit udp any 10.1.0.0 0.0.255.255 dscp ef
 
Router(config-ext-nacl)# exit
Router(config)# ip access-list extended voice-agg-acl
Router(config-ext-nacl)# permit udp any any range 3000 4000 dscp ef
 
Router(config-ext-nacl)# exit
Router(config)# oer master
 
Router(config-oer-master)# learn
 
Router(config-oer-master-learn)# aggregation-type prefix-length 24
 
Router(config-oer-master-learn)# throughput
 
Router(config-oer-master-learn)# traffic-class filter access-list voice-filter-acl
 
Router(config-oer-master-learn)# traffic-class aggregate access-list voice-agg-acl 
Router(config-oer-master-learn)# traffic-class keys dscp protocol dport
Router(config-oer-master-learn)# end

Related Commands

Command

Description

aggregation-type

Configures an OER master controller to aggregate learned prefixes based on the type of traffic flow.

learn

Enters OER Top Talker and Top Delay learning configuration mode to configure prefixes for OER to learn.

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

traffic-class aggregate

Aggregates OER learned traffic flows into application traffic classes using an access list.

traffic-class keys

Specifies a key list used by an OER border router to aggregate the traffic flows into learned application classes.

traffic-class keys

To specify a key list of fields in the traffic flows that an Optimized Edge Routing (OER) border router uses to aggregate traffic flows into application traffic classes, use the traffic-class keys command in OER Top Talker and Top Delay learning configuration mode. To remove the key list, use the no form of this command.

traffic-class keys [ default | [ dscp] [ protocol [ dport] [ sport] ] ]
no traffic-class keys [ default | [ dscp] [ protocol [ dport] [ sport] ] ]

Syntax Description

default

(Optional) Aggregates the traffic flows into application traffic classes on the basis of protocol and destination port.

dscp

(Optional) Aggregates the traffic flows into application traffic classes on the basis of Differentiated Services Code Point (DSCP) value.

protocol

(Optional) Aggregates the traffic flows into application traffic classes on the basis of the protocol.

dport

(Optional) Aggregates the traffic flows into application traffic classes on the basis of the destination port.

sport

(Optional) Aggregates the traffic flows into application traffic classes on the basis of the source port.

Command Default

No OER traffic class key lists are created.

Command Modes

OER Top Talker and Top Delay learning configuration

Command History

Release

Modification

12.4(9)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

Usage Guidelines

The traffic-class keys command can be used with the traffic-class filter and traffic-class aggregate commands to configure the master controller to automatically learn defined application traffic. This command is used only if the traffic-class aggregate command is not configured or returns no matches.

Examples

In this following task, the traffic-class filter command references an access list that is used to filter out unwanted traffic, and an access list with aggregation criteria aggregates the traffic into subsets of traffic classes using the traffic-class aggregate command. Traffic class keys are specified with the traffic-class keys command, but they will be used only if the traffic class aggregation access list does not have any matches. Usually traffic class keys are specified when there is no traffic class aggregation. In this example, only voice traffic with a DSCP bit set to ef, a User Datagram Protocol (UDP), and a destination port in the range of 3000 to 4000 is learned and added to the OER application database on the master controller.

Router(config)# ip access-list extended voice-filter-acl
Router(config-ext-nacl)# permit udp any 10.1.0.0 0.0.255.255 dscp ef
 
Router(config-ext-nacl)# exit
Router(config)# ip access-list extended voice-agg-acl
Router(config-ext-nacl)# permit udp any any range 3000 4000 dscp ef
 
Router(config-ext-nacl)# exit
Router(config)# oer master
 
Router(config-oer-master)# learn
 
Router(config-oer-master-learn)# aggregation-type prefix-length 24
 
Router(config-oer-master-learn)# throughput
 
Router(config-oer-master-learn)# traffic-class filter access-list voice-filter-acl
 
Router(config-oer-master-learn)# traffic-class aggregate access-list voice-agg-acl 
Router(config-oer-master-learn)# traffic-class keys dscp protocol dport
Router(config-oer-master-learn)# end

Related Commands

Command

Description

learn

Enters OER Top Talker and Top Delay learning configuration mode to configure prefixes for OER to learn.

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

traffic-class aggregate

Aggregates OER learned traffic flows into application traffic classes using an access list.

traffic-class filter

Filters uninteresting traffic from OER learned traffic flows using an access list.

traffic-class prefix-list

To define an Optimized Edge Routing (OER) traffic class using a prefix list applied to learned traffic classes, use the traffic-class prefix-list command in learn list configuration mode. To disable the definition of OER learned traffic flows into traffic classes using a prefix list, use the no form of this command.

traffic-class prefix-list prefix-list-name [ inside]
no traffic-class prefix-list

Syntax Description

prefix-list-name

Name of a prefix list. Names cannot contain either a space or quotation marks and must begin with an alphabetic character to distinguish them from numbered access lists.

inside

(Optional) Specifies that the prefix list contains inside prefixes.

Command Default

OER application traffic classes are not defined using a prefix list.

Command Modes

Learn list configuration (config-oer-mc-learn-list)

Command History

Release

Modification

12.4(15)T

This command was introduced.

Usage Guidelines

The traffic-class prefix-list command is used to configure the master controller to automatically learn traffic based only on destination prefixes. Use the optional inside keyword to specify prefixes that are within the internal network.

In Cisco IOS Release 12.4(15)T, the learn list configuration mode was introduced. Learn lists are a way to categorize learned traffic classes. In each learn list, different criteria for learning traffic classes including prefixes, application definitions, filters, and aggregation parameters can be configured. A traffic class is automatically learned by OER based on each learn list criteria, and each learn list is configured with a sequence number. The sequence number determines the order in which learn list criteria are applied. Learn lists allow different OER policies to be applied to each learn list; in previous releases the traffic classes could not be divided, and an OER policy was applied to all the traffic classes.


Note


The traffic-class prefix-list command, the traffic-class application command, and the traffic-class access-list commands are all mutually exclusive in an OER learn list. Only one of these commands can be specified per OER learn list.

Examples

The following example, starting in global configuration mode, shows how to define traffic classes based only on destination prefixes for a learn list named LEARN_PREFIX_TC. The traffic classes are created using the prefix list, LEARN_LIST1, in which every entry in the prefix list defines one destination network of a traffic class. After the prefix list is configured, the master controller automatically learns the traffic classes based on the highest throughput.

Router(config)# ip prefix-list LEARN_LIST1 permit seq 10 10.0.0.0/8
Router(config)# ip prefix-list LEARN_LIST1 permit seq 20 172.16.0.0/16
Router(config)# oer master 
Router(config-oer-mc)# learn 
Router(config-oer-mc-learn)# list seq 10 refname LEARN_PREFIX_TC 
Router(config-oer-mc-learn-list)# aggregation-type prefix-length 24 
Router(config-oer-mc-learn-list)# traffic-class prefix-list LEARN_LIST1
Router(config-oer-mc-learn-list)# throughput
Router(config-oer-mc-learn-list)# end 

Related Commands

Command

Description

aggregation-type

Configures an OER master controller to aggregate learned prefixes based on the type of traffic flow.

learn

Enters OER Top Talker and Top Delay learning configuration mode to configure prefixes for OER to learn.

list (OER)

Creates an OER learn list to specify criteria for learning traffic classes and enters learn list configuration mode.

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

unreachable

To set the relative percentage or maximum number of unreachable hosts that Optimized Edge Routing (OER) permits from an OER-managed exit link, use the unreachablecommand in OER master controller configuration mode. To return the maximum number of unreachable hosts to the default value, use the no form of this command.

unreachable { relative average | threshold maximum }
no unreachable

Syntax Description

relative average

Sets a relative percentage of unreachable hosts based on a comparison of short-term and long-term percentages. The range of values that can be configured for this argument is a number from 1 to a 1000. Each increment represents one tenth of a percent.

threshold maximum

Sets the absolute maximum number of unreachable hosts based on flows per million (fpm). The range of values that can be configured for this argument is from 1 to 1000000.

Command Default

OER uses the following default value if this command is not configured or if the no form of this command is entered:

relative average : 50 (5 percent)

Command Modes

OER master controller configuration

Command History

Release

Modification

12.3(8)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

Usage Guidelines

The unreachablecommand entered on a master controller. This command is used to specify the relative percentage or the absolute maximum number of unreachable hosts, based on fpm, that OER will permit from an OER-managed exit link. If the absolute number or relative percentage of unreachable hosts is greater than the user-defined or the default value, OER determines that the exit link is out-of-policy and searches for an alternate exit link.

The relative keyword is used to configure the relative percentage of unreachable hosts. The relative unreachable host percentage is based on a comparison of short-term and long-term measurements. The short-term measurement reflects the percentage of hosts that are unreachable within a 5-minute period. The long-term measurement reflects the percentage of unreachable hosts within a 60-minute period. The following formula is used to calculate this value:

Relative percentage of unreachable hosts = ((short-term percentage - long-term percentage) / long-term percentage) * 100

The master controller measures the difference between these two values as a percentage. If the percentage exceeds the user-defined or default value, the exit link is determined to be out-of-policy. For example, if 10 hosts are unreachable during the long-term measurement and 12 hosts are unreachable during short-term measurement, the relative percentage of unreachable hosts is 20 percent.

The threshold keyword is used to configure the absolute maximum number of unreachable hosts. The maximum value is based on the actual number of hosts that are unreachable based on fpm.

Examples

The following example configures the master controller to search for a new exit link when the difference between long- and short-term measurements (relative percentage) is greater than 10 percent:

Router(config)# oer master
Router(config-oer-mc)# unreachable relative 100

The following example configures OER to search for a new exit link when 10,000 hosts are unreachable:

Router(config)# oer master
Router(config-oer-mc)# unreachable threshold 10000
 

Related Commands

Command

Description

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

© 2007-2012 Cisco Systems, Inc. All rights reserved.