Note

Effective with Cisco IOS Release 15.0(1)SY, the active-probe 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 configure an Optimized Edge Routing (OER) active probe for a target prefix, use the active-probe command in OER master controller configuration mode. To disable the active probe, use the no form of this command.

Syntax Description

Command Default

No active probes are configured.

Command Modes

OER master controller configuration

Command History

Usage Guidelines

The active-probe command is entered on an OER master controller.

This command is used to optionally configure a master controller to command a border router to transmit active probes to a target IP address or prefix. The active probe is used to measure the delay (round-trip response time) of the target prefix to determine the performance of the current exit and to detect if the prefix is out-of-policy. The border router collects these performance statistics from the active probe and transmits this information to the master controller, which uses this information to optimize the prefix and to select the best available exit based on default and user-defined policies. The performance information is applied to the most specific optimized prefix, which includes the active probe host address. If the prefix is optimized and currently using the best in-policy exit link, the master controller does not take any action.

Active Probing requires you to configure a specific host or target address. The target address can also be learned by OER through the NetFlow or Top Talker and Delay learning functionality. Active probes must be sent out of an OER managed external interface, which may or may not be the preferred route for an Optimized Prefix (OP). OER can be configured to use the following four types of active probes:

• ICMP Echo--A ping is sent to the target address. Configuring an ICMP echo probe does not require knowledgeable cooperation from the target device. However, repeated probing could trigger an Intrusion Detection System (IDS) alarm in the target network. If an IDS is configured in a target network that is not under your administrative control, we recommend that you notify the target network administration entity.
• Jitter--A jitter probe is sent to the target address. A target port number must be specified. A remote responder must be enabled on the target device, regardless of the configured port number. An optional codec value can be configured. The codec value is required for Mean Opinion Score (MOS) calculations.
• TCP Connection--A TCP connection probe is sent to the target address. A target port number must be specified. A remote responder must be enabled if TCP messages are configured to use a port number other than TCP well-known port number 23.
• UDP Echo--A UDP echo probe is sent to the target address. A target port number must be specified. A remote responder must be enabled on the target device, regardless of the configured port number.

OER uses Cisco IOS IP Service Level Agreements (SLAs), a standard feature in Cisco IOS software, to command a border router to transmit an active probe to the target address. No explicit IP SLAs configuration is required on the master controller or the border router. Support for IP SLAs is enabled by default when the OER process is created. However, a remote responder must be enabled on the target device when configuring an active probe using UDP echo messages or when configuring an active probe using TCP connection messages that are configured to use a port other than the TCP well-known port number 23. The remote responder is enabled by configuring the ip sla monitor responder global configuration command on the target device.

Note	For external BGP (eBGP) peering sessions, the IP address of the eBGP peer must be reachable from the border router via a connected route in order for active probes to be generated.

Related Commands

Note

Effective with Cisco IOS Release 15.0(1)SY, the active-probe address source 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 configure an interface on a border router as the source of the active probe, use the active-probe address source command in OER border router configuration mode. To configure active probing to use a default exit interface, use the no form of this command.

Syntax Description

Command Default

The source IP address is used from the default Optimized Edge Routing (OER) external interface that transmits the active probe.

Command Modes

OER border router configuration

Command History

Usage Guidelines

The active-probe address sourcecommand allows you to specify the source interface, from which active probes are transmitted. When this command is configured, the primary IP address of the specified interface is used as the active probe source. The active probe source interface IP address must be unique to ensure that the probe reply is routed back to the specified source interface. If the interface is not configured with an IP address, the active probe will not be generated. If the IP address is changed after the interface has been configured as an active probe source, active probing is stopped, and then restarted with the new IP address. If the IP address is removed after the interface has been configured as an active probe source, active probing is stopped and is not restarted until a valid primary IP address is configured.

Note	For external Border Gateway Protocol (eBGP) peering sessions, the IP address of the eBGP peer must be reachable from the border router via a connected route in order for active probes to be generated.

Related Commands

To configure an Optimized Edge Routing (OER) master controller to aggregate learned prefixes based on the type of traffic flow, use the aggregation-type command in OER Top Talker and Top Delay learning configuration mode. To set learned prefix aggregation to the default type, use the no form of this command.

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:

prefix-list prefix-mask : 24

Command Modes

OER Top Talker and Top Delay learning configuration

Command History

Usage Guidelines

The aggregation-type command is entered on a master controller. This command is used to configure OER to aggregate learned prefixes based on the traffic flow type. BGP prefixes or non-BGP prefixes can be aggregated, and traffic flows can be aggregated based on prefix length.

Entering the bgp keyword configures the aggregation of learned prefixes based on prefix entries in the BGP routing table. This keyword is used if internal BGP (iBGP) peering is enabled in the OER managed network.

Entering the non-bgp keyword configures the aggregation of learned prefixes based on any other routing protocol. Prefix entries that are present in the BGP routing table are ignored when this keyword is entered.

Related Commands

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

To register an application interface client with an Optimized Edge Routing (OER) master controller and specify a priority value for the application interface client, use the api client command in OER master controller configuration mode. To unregister the application interface client and return the priority to the default value, use the no form of this command.

Syntax Description

Command Default

No application interface clients are registered with OER.

Command Modes

OER master controller configuration (config-oer-mc)

Command History

Usage Guidelines

The api client command is used to register an API client with OER and specify the priority of the API client.

Cisco IOS Release 12.4(15)T

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

Related Commands

To register an application interface provider with an Optimized Edge Routing (OER) master controller and enter OER master controller application interface provider configuration mode, use the api provider command in OER master controller configuration mode. To unregister the application interface provider, use the no form of this command.

Syntax Description

Command Default

An application interface provider is not registered with an OER master controller.

Command Modes

OER master controller configuration (config-oer-mc)

Command History

Usage Guidelines

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.

Use the optional priority keyword to specify a priority value for the provider when multiple providers are registered with OER. The number 1 assigns the highest priority to any requests through the application interface. If you assign a priority, each provider must be assigned a different priority number. If you try to assign the same priority number to two different providers, an error message is displayed on the console.

Note	API provider IDs and API priority values in the range of 1 to 100 are reserved for internal Cisco applications.

Use the show oer api provider command to view information about the currently registered providers. Use the show oer master policy command with the dynamic keyword to display information about policies created dynamically by an application using the OER application interface.

Related Commands

To configure a user-defined custom application to be monitored by Optimized Edge Routing (OER), use the application define command in OER master controller configuration mode. To remove the definition of a user-defined custom application to be monitored by OER, use the no form of this command.

Syntax Description

Command Default

No custom-defined applications are defined for use with OER.

Command Modes

OER master controller configuration (config-oer-mc)

Command History

Usage Guidelines

The application define command allows a user-defined custom application to be defined on the master controller as an application that can be used in OER configuration to create a traffic class that can be measured and controlled using OER techniques. An access list can be used to define the traffic flows to create a custom application.

In Cisco IOS Release 12.4(20)T, the ability to define a custom application to be identified using NBAR, was introduced. NBAR includes many defined applications but a Packet Description Language Module (PDLM) can be used to add a new protocol to the list of supported NBAR applications. A PDLM uses a mapping of static TCP and UDP port numbers to create a custom application. The application defined by a PDLM file must be recognized on an OER border router and configured on the master controller using the application define command. The OER master controller makes a request to the border router to determine if the application is supported. Use the show oer master nbar application command to check if the application is supported on each border router.

To display defined applications use the show oer master defined or the show oer border defined commands.

Related Commands

To set the backoff timer to adjust the time period for prefix policy decisions, use the backoff command in OER master controller configuration mode. To set the backoff timer to the default value, use the no form of this command.

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

Command Modes

OER master controller configuration

Command History

Usage Guidelines

The backoff command is entered on an OER master controller. This command is used to adjust the transition period that the master controller holds an out-of-policy prefix. The master controller waits for the transition period before making an attempt to find an in-policy exit. This command is configured with a minimum and maximum timer value and can be configured with an optional step 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.

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.

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.

Related Commands

Note

Effective with Cisco IOS Release 15.0(1)SY, the 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 enter OER managed border router configuration mode to establish communication with an Optimized Edge Routing (OER) border router, use the border command in OER master controller configuration mode. To disable communication with the specified border router, use the no form of this command.

Syntax Description

Command Default

Border key-chain configuration is required during initial configuration. Once configured, the key-chain keyword is optional.

Passive monitoring in OER observe mode is enabled by default when communication is established between an OER border router and master controller.

Command Modes

OER master controller configuration

Command History

Usage Guidelines

The border command is entered on a master controller. This command is used to establish communication between a master controller and border router. Communication is established between the master controller and border router processes to allow the master controller to monitor and control prefixes and exit links. Communication must also be established on the border router with the master OER border configuration command.

At least one border router must be configured to enable OER. A maximum of ten border routers can be configured to communicate with a single master controller. The IP address that is used to specify the border router must be assigned to an interface physically located on the border router and must be reachable by the master controller.

Communication between the master controller and the border router is protected by key-chain authentication. The authentication key must be configured on both the master controller and the border router before communication can be established. The key-chain configuration is defined in global configuration mode on both the master controller and the border router before key-chain authentication is enabled for master controller to border router communication. For more information about key management in Cisco IOS software, see the "Managing Authentication Keys" section in the "Configuring IP Protocol-Independent Features" chapter of the Cisco IOS IP Routing Protocols Configuration Guide , Release 12.4 .

When the border command is entered, the router enters OER managed border router configuration mode. Local interfaces must be defined as internal or as external with the interface(OER) OER managed border router configuration command. A single OER master controller can support up to 20 interfaces.

Enabling a Border Router and Master Controller Process on the Same Router

A Cisco router can be configured to perform in dual operation and run a master controller process and border router process on the same router. However, this router will use more memory than a router that is configured to run only a border router process. This factor should be considered when selecting a router for dual operation.

Related Commands

Note

Effective with Cisco IOS Release 15.0(1)SY, the clear oer api 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 reset the Optimized Exit Routing (OER) application program interface (API) sessions between the border router and master controller, use the clear oer api command in privileged EXEC mode.

Syntax Description

Command Modes

Privileged EXEC (#)

Command History

Related Commands

Note

Effective with Cisco IOS Release 15.0(1)SY, the clear 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 reset a connection between a border router and the master controller, use the clear oer border command in privileged EXEC mode.

Syntax Description

Command Modes

Privileged EXEC

Command History

Usage Guidelines

The clear oer border command is entered on a border router. The border router and master controller will automatically reestablish communication after this command is entered.

Related Commands

To reset an Optimized Edge Routing (OER) master controller process and all active border router connections, use the clear oer mastercommand in privileged EXEC mode.

Syntax Description

Command Modes

Privileged EXEC

Command History

Usage Guidelines

The clear oer master command is entered on a master controller. The master controller will restart all configured and default processes and reestablish communication with active border routers after this command is entered.

Related Commands

To reset an Optimized Edge Routing (OER) master controller applications and all active TCP protocol connections, use the clear oer master appl tcp command in privileged EXEC mode.

Syntax Description

Command Modes

Privileged EXEC (#)

Command History

Related Commands

To reset an active border router connection or all connections with a master controller, use the clear oer master border command in privileged EXEC mode.

Syntax Description

Command Modes

Privileged EXEC

Command History

Usage Guidelines

The clear oer master border command is entered on a master controller.

Related Commands

To clear Optimized Edge Routing (OER) controlled prefixes from the master controller database, use the clear oer master prefixcommand in privileged EXEC mode.

Syntax Description

Command Modes

Privileged EXEC

Command History

Usage Guidelines

The clear oer master prefix command is entered on a master controller.

Related Commands

To clear Optimized Edge Routing (OER) controlled traffic classes from the master controller database, use the clear oer master traffic-classcommand in privileged EXEC mode.

Syntax Description

Command Modes

Privileged EXEC (#)

Command History

Usage Guidelines

The clear oer master traffic-class command is entered on a master controller. In Cisco IOS Release 12.4(20)T, and later releases, to clear OER-controlled traffic classes defined by an application identified using Network-Based Application Recognition (NBAR) from the master controller database, use the clear oer master traffic-class application nbarcommand.

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

Related Commands

To clear Optimized Edge Routing (OER) controlled traffic classes defined by an application identified using Network-Based Application Recognition (NBAR) from the master controller database, use the clear oer master traffic-class application nbarcommand in privileged EXEC mode.

Syntax Description

Command Default

All OER-controlled traffic classes defined by applications identified using NBAR are cleared.

Command Modes

Privileged EXEC (#)

Command History

Usage Guidelines

The clear oer master traffic-class application nbar command is entered on a master controller. To clear all other types of OER-controlled traffic classes from the master controller database, use the clear oer master traffic-classcommand.

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 clear oer master 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 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 cleared. 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 cleared.

Related Commands

To configure cost-based optimization policies on a master controller, use the cost-minimization command in OER border exit interface configuration mode. To disable a cost-based optimization policy, use the no form of this command.

Syntax Description

Command Default

No cost-based optimization policies are configured.

Command Modes

OER border exit interface configuration (config-oer-mc-br-if)

Command History

Usage Guidelines

The cost-minimization command is configured on a master controller. Cost-based optimization allows you to configure link policies based on the Internet service provider (ISP) financial cost of each exit link in your network. The cost-minimizationcommand allows you to configure the master controller to send traffic over exit links that provide the most cost-effective bandwidth utilization, while still maintaining the desired performance characteristics.

Related Commands

To set the number of traffic classes to be learned by a learn list during an Optimized Edge Routing (OER) learn session, use the count command in learn list configuration mode. To reset the number of traffic classes to be learned by a learn list to the default values, use the no form of this command.

Syntax Description

Command Default

If this command is not configured, the number of traffic classes to be learned by a learn list during an OER learn session is set to the default value.

Command Modes

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

Command History

Usage Guidelines

Use this command to set the number of traffic classes that a border router sends to the master controller for a learn list during an OER learn session. An overall maximum number of traffic classes for a learn list can also be configured.

Related Commands

Note

Effective with Cisco IOS Release 15.0(1)SY, the debug oer api 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) application interface debugging information, use the debug oer apicommand in privileged EXEC mode. To stop the display of OER application interface debugging information, use the no form of this command.

Syntax Description

Command Modes

Privileged EXEC (#)

Command History

Usage Guidelines

The debug oer apicommand is used to display messages about any configured OER application interface providers or host devices. 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 application interface provides an automated method for networks to be aware of applications and provides application-aware performance routing.

Caution

When the detail keyword is entered, the amount of detailed output to be displayed can utilize a considerable amount of system resources. Use the detailkeyword with caution in a production network.

Related Commands

Note

Effective with Cisco IOS Release 15.0(1)SY, the debug oer api 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 debug oer api client command is replaced by the debug oer api command. See the debug oer api command for more information.

To display Optimized Edge Routing (OER) application interface client debugging information for master controller and border router communication, use the debug oer api client command in privileged EXEC mode. To stop the display of OER application interface debugging information, use the no form of this command.

Syntax Description

Command Modes

Privileged EXEC (#)

Command History

Usage Guidelines

The debug oer api client command can be entered on a master controller. This command is used to display messages about a configured OER application interface client. When the detail keyword is entered, the amount of detailed output to be displayed can utilize a considerable amount of system resources. Use the detailkeyword with caution in a production network.

Cisco IOS Release 12.4(15)T

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

Related Commands

Note

Effective with Cisco IOS Release 15.0(1)SY, the debug 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 general OER border router debugging information, use the debug oer bordercommand in privileged EXEC mode. To stop the display of OER debugging information, use the no form of this command.

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Usage Guidelines

The debug oer border command is entered on a border router. This command is used to display debugging information about the OER border process, controlled routes and monitored prefixes.

Related Commands

Note

Effective with Cisco IOS Release 15.0(1)SY, the debug oer border active-probe 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 debugging information for active probes configured on the local border router, use the debug oer border active-probecommand in privileged EXEC mode. To stop the display of debug event information, use the no form of this command.

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Usage Guidelines

The debug oer border active-probe command is entered on a master controller. This command is used to display the status and results of active probes that are configured on the local border router.

Related Commands

Note

Effective with Cisco IOS Release 15.0(1)SY, the debug oer border 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 debugging information about learned prefixes on the local border router, use the debug oer border learncommand in privileged EXEC mode. To stop the display of debug event information, use the no form of this command.

Syntax Description

Command Modes

Privileged EXEC (#)

Command History

Usage Guidelines

The debug oer border learn command is entered on a border router. This command is used to display debugging information about prefixes learned on the local border router.

Related Commands

Note

Effective with Cisco IOS Release 15.0(1)SY, the debug 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 debugging information for OER-controlled or monitored routes on the local border router, use the debug oer border routes command in privileged EXEC mode. To stop the display of debug event information, use the no form of this command.

Syntax Description

Command Modes

Privileged EXEC (#)

Command History

Usage Guidelines

The debug oer border routes command is entered on a border router. This command is used to display the debugging information about OER-controlled or monitored routes on the local border router.

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). If a parent route for the traffic class exists in the RIB, policy-based routing is used to control the prefix.

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. If a parent route for the traffic class exists in the EIGRP routing table, temporary EIGRP routes are injected and identified by adding a configurable extended community tag value.

Related Commands

Note

Effective with Cisco IOS Release 15.0(1)SY, the debug oer border traceroute reporting 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 debugging information for traceroute probes on the local border router, use the debug oer border traceroute reporting command in privileged EXEC mode. To stop the display of debug event information, use the no form of this command.

Syntax Description

Command Modes

Privileged EXEC (#)

Command History

Usage Guidelines

The debug oer border traceroute reportingcommand is entered on a border router. This command is used to display the debugging information about traceroute probes sourced on the local border router.

Related Commands

Note

Effective with Cisco IOS Release 15.0(1)SY, the debug oer cc 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 OER communication control debugging information for master controller and border router communication, use the debug oer cc command in privileged EXEC mode. To stop the display of OER debugging information, use the no form of this command.

Syntax Description

Command Modes

Privileged EXEC

Command History

Usage Guidelines

The debug oer cc command can be entered on a master controller on a border router. This command is used to display messages exchanged between the master controller and the border router. These messages include control commands, configuration commands, and monitoring information. Enabling this command will cause very detailed output to be displayed and can utilize a considerable amount of system resources. This command should be enabled with caution in a production network.

Related Commands

To display debugging information for OER border router events on an OER master controller, use the debug oer master bordercommand in privileged EXEC mode. To stop border router event debugging, use the no form of this command.

Syntax Description

Command Modes

Privileged EXEC

Command History

Usage Guidelines

The debug oer master border command is entered on a master controller. The output displays information related to the events or updates from one or more border routers.

Related Commands

To display data collection debugging information for OER monitored prefixes, use the debug oer master collectorcommand in privileged EXEC mode. To disable the display of this debugging information, use the no form of this command.

Syntax Description

Command Modes

Privileged EXEC

Command History

Usage Guidelines

The debug oer master collector command is entered on a master controller. The output displays data collection information for monitored prefixes.

Related Commands

To display debugging information for cost-based optimization policies, use the debug oer master cost-minimization command in privileged EXEC mode. To disable the display of this debugging information, use the no form of this command.

Syntax Description

Command Modes

Privileged EXEC

Command History

Usage Guidelines

The debug oer master cost-minimization command is entered on a master controller. The output displays debugging information for cost-minimization policies.

Related Commands

To display debug event information for OER managed exits, use the debug oer master exitcommand in privileged EXEC mode. To stop the display of debug event information, use the no form of this command.

Syntax Description

Command Modes

Privileged EXEC

Command History

Usage Guidelines

The debug oer master exit command is entered on a master controller. This command is used to display debugging information for master controller exit selection processes.

Related Commands

To display debug information for OER master controller learning events, use the debug oer master learn command in privileged EXEC mode. To stop the display of debug information, use the no form of this command.

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Usage Guidelines

The debug oer master learn command is entered on a master controller. This command is used to display debugging information for master controller learning events.

Related Commands

To display debug events related to prefix processing on an OER master controller, use the debug oer master prefixcommand in privileged EXEC mode. To disable the display of debug information, use the no form of this command.

Syntax Description

Command Modes

Privileged EXEC

Command History

Usage Guidelines

The debug oer master prefix command is entered on a master controller. This command displays debugging information related to prefix monitoring and processing.

Related Commands

To display debug events related to prefix-list processing on an OER master controller, use the debug oer master prefix-listcommand in privileged EXEC mode. To disable the display of debug information, use the no form of this command.

Syntax Description

Command Modes

Privileged EXEC

Command History

Usage Guidelines

The debug oer master prefix-listcommand is entered on a master controller. This command displays debugging information related to prefix-list processing.

Related Commands

To display debug information about the OER master controller process, use the debug oer master process command in privileged EXEC mode. To stop displaying debug information, use the no form of this command.

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC (#)

Command History

Usage Guidelines

The debug oer master process command is entered on a master controller.

Related Commands

To display debug information about traceroute probes, use the debug oer master traceroute reporting command in privileged EXEC mode. To stop displaying debug information, use the no form of this command.

Syntax Description

Command Modes

Privileged EXEC

Command History

Usage Guidelines

The debug oer master traceroute reporting command is entered on a master controller. This command is used to display traceroute events on a master controller.

Related Commands

To set a delay threshold for an Optimized Edge Routing (OER) policy, or to configure OER traffic class learning based on highest delay times, use the delay command in master controller, Top Talker and Top Delay learning, or learn list configuration mode. To reset the delay values to their default, use the no form of this command.

Syntax Description

Master Controller Configuration Mode

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

None

Command Modes

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

Command History

Usage Guidelines

Configuring in Master Controller Configuration Mode

Use the delay command entered in OER master controller configuration mode to set the delay threshold for a traffic class within an OER policy as a relative percentage or as an absolute value. If the configured delay threshold is exceeded, then the traffic class is out-of-policy.

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 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 the long-term delay measurement is 100 milliseconds and the 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.

Configuring in Top Talker and Top Delay Learning and Learn List Configuration Modes

Use the delay command under the Top Talker and Top Delay learning or learn list configuration mode to enable traffic class learning based on the highest delay time. OER measures the delay for optimized prefixes when this command is enabled, and the master controller creates a list of traffic classes based on the highest delay time.

Related Commands

To specify route downgrade options for an Optimized Edge Routing (OER) managed interface using Border Gateway Protocol (BGP) advertisements, use the downgrade bgp command in OER border exit interface configuration mode. To remove the route downgrade options, use the no form of this command.

Syntax Description

Command Default

No route downgrade options are specified.

Command Modes

OER border exit interface configuration

Command History

Usage Guidelines

Use the downgrade bgp command to attach a BGP prepend community to an inside prefix BGP advertisement from the network to another autonomous system such as an Internet Service Provider (ISP). The BGP prepend community will increase the number of autonomous system hops in the advertisement of the inside prefix from the ISP to its peers. Autonomous system prepend BGP community is the preferred method to be used for OER BGP inbound optimization because there is no risk of the local ISP filtering the extra autonomous system hops.

Related Commands

To set the length of time that Optimized Edge Routing (OER) learned prefixes are kept in the central policy database, use the expire aftercommand in OER Top Talker and Top Delay learning configuration mode. To disable the expiration timer and restore default behavior, use the no form of this command.

Syntax Description

Command Default

New prefixes are not learned if router memory utilization is greater than 90 percent. Inactive prefixes are removed (oldest first) from the central policy database as memory is needed.

Command Modes

OER Top Talker and Top Delay learning configuration

Command History

Usage Guidelines

The expire aftercommand is entered on an OER master controller in OER Top Talker and Top Delay learning configuration mode. This command is used to configure a session or time-based expiration period for learned prefixes. Each session is equal to one monitoring period plus a periodic interval time that separates monitoring periods. The time-based expiration timer is configured in minutes.

Related Commands