Cisco IOS Optimized Edge Routing Command Reference

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

Command Default

No active probes are configured with a forced target assignment.

Command Modes

OER map configuration (config-oer-map)

Command History

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

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

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: 300
max-timer: 3000
step-timer: 300

Command Modes

OER map configuration

Command History

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-timer argument 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

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

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

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

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

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

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

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

Command Default

No packets are send to the null interface.

Command Modes

OER map configuration

Command History

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

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

Command Default

No jitter values are specified.

Command Modes

OER map configuration

Command History

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

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

Command Default

No link groups are specified for a traffic class.

Command Modes

OER map configuration (config-oer-map)

Command History

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

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 loss command 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

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

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

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

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

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

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

Command Default

The default MOS value is 3.60.

Command Modes

OER map configuration

Command History

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

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

Command Default

No packets are sent to the next hop.

Command Modes

OER map configuration

Command History

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

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

Command Default

No default behavior or values

Command Modes

OER map configuration

Command History

Usage Guidelines

The set periodic command 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

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

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

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.

In 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

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

Command Default

None

Command Modes

OER map configuration

Command History

Usage Guidelines

The set resolve command 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

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

Command Default

Traceroute reporting is not enabled using an OER map.

Command Modes

OER map configuration

Command History

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

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

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

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

show oer api client

Effective with Cisco IOS Release 12.4(15)T, the show oer api client command is replaced by the show oer api provider command. 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

Command Modes

Privileged EXEC (#)

Command History

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 

Table 30 describes the significant fields shown in the display.

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

Table 31 describes the significant fields shown in the display.

Related Commands

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

Command Default

Detailed information about API providers is not displayed.

Command Modes

Privileged EXEC (#)

Command History

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 detail keyword 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-address command 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

Table 32 describes the significant fields shown in the display.

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

Table 33 describes the significant fields shown in the display that are different from Table 32.

Related Commands

show oer border

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

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

Table 34 describes the significant fields shown in the display.

Related Commands

show oer border active-probes

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

show oer border active-probes

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

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

Table 35 describes the significant fields shown in the display.

Related Commands

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

Usage Guidelines

The show oer border defined application command 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 application command.

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 

.

.

.

Table 36 describes the significant fields shown in the display.

Related Commands

show oer border passive applications

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

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

Table 37 describes the significant fields shown in the display.

Related Commands

show oer border passive cache

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

Command Modes

Privileged EXEC (#)

Command History

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

Table 38 describes the significant fields shown in the display.

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

show oer border passive learn

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

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

Table 39 describes the significant fields shown in the display.

Related Commands

show oer border passive prefixes

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

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

Table 40 describes the significant fields shown in the display.

Related Commands

show oer border routes

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

Command Modes

Privileged EXEC (#)

Command History

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

Table 41 describes the significant fields shown in the display.

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

Table 42 describes the significant fields shown in the display.

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 Commands10.1.2.0/24       6

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

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 

Table 43 describes the significant fields shown in the display.

Related Commands

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

Command Modes

Privileged EXEC

Command History

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 

Table 44 describes the significant fields shown in the display.

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

Table 45 describes the significant fields shown in the display that are different from those in Table 44.

Related Commands

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

Command Modes

Privileged EXEC

Command History

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

Table 46 describes the significant fields shown in the display.

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 

Table 47 describes the significant fields shown in the display that are different from those in Table 46.

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

show oer master border

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

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

Syntax Description

Command Modes

Privileged EXEC (#)

Command History

Usage Guidelines

The show oer master border command 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

Table 48 describes the significant fields shown in the display. All the other fields in the output are self-explanatory.

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

Table 49 describes the significant fields shown in the display.

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

Table 50 describes the significant fields shown in the display.

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

Table 51 describes the significant fields shown in the display.

Related Commands

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}