|
Command or Action |
Purpose |
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
-
Enter your password if prompted.
|
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode. |
|
key chain name-of-chain
Example:
Router(config)# key chain border1_OER
|
Enables key-chain authentication and enters key-chain configuration mode.
-
Key-chain authentication protects the communication session between the master controller and the border router. The key ID and key string must match in order for communication to be established.
-
In this example, a key chain is created for use with border router 1.
|
|
key key-id
Example:
Router(config-keychain)# key 1
|
Identifies an authentication key on a key chain.
-
The key ID must match the key ID configured on the border router.
|
|
key-string text
Example:
Router(config-keychain-key)# key-string b1
|
Specifies the authentication string for the key and enters key-chain key configuration mode.
-
The authentication string must match the authentication string configured on the border router.
-
Any encryption level can be configured.
-
In this example, a key string is created for use with border router 1.
|
|
exit
Example:
Router(config-keychain-key)# exit
|
Exits key-chain key configuration mode and returns to key-chain configuration mode. |
|
exit
Example:
Router(config-keychain)# exit
|
Exits key-chain configuration mode and returns to global configuration mode. |
|
Repeat Step 3 through Step 7 with appropriate changes to configure key chain authentication for each border router.
|
-- |
|
oer master
Example:
Router(config)# oer master
|
Enters OER master controller configuration mode to configure a router as a master controller.
-
A master controller and border router process can be enabled on the same router (for example, in a network that has a single router with two exit links to different service providers).
Note |
Only the syntax used in this context is displayed. For more details, see the Cisco IOS Optimized Edge Routing Command Reference. |
|
|
port port-number
Example:
Router(config-oer-mc)# port 65534
|
(Optional) Configures a dynamic port for communication between the master controller and border router.
-
Communication cannot be established until the same port number has been configured on both the master controller and the border router.
Note |
Manual port number configuration is required to establish OER communication only when running Cisco IOS Release 12.3(8)T. |
|
|
logging
Example:
Router(config-oer-mc)# logging
|
Enables syslog messages for a master controller or border router process.
-
The notice level of syslog messages is enabled by default.
|
|
border ip-address [key-chain key-chain-name]
Example:
Router(config-oer-mc)# border 10.1.1.2 key-chain border1_OER
|
Enters OER-managed border router configuration mode to establish communication with a border router.
-
An IP address is configured to identify the border router.
-
At least one border router must be specified to create an OER-managed network. A maximum of ten border routers can be controlled by a single master controller.
-
The value for the key-chain-name argument must match the key-chain name configured in Step 3.
Note |
The key-chain keyword and key-chain-name argument must be entered when a border router is initially configured. However, this keyword is optional when reconfiguring an existing border router. |
|
|
interface type number external
Example:
Router(config-oer-mc-br)# interface Ethernet 1/0 external
|
Configures a border router interface as an OER-managed external interface.
-
External interfaces are used to forward traffic and for active monitoring.
-
A minimum of two external border router interfaces are required in an OER-managed network. At least one external interface must be configured on each border router. A maximum of 20 external interfaces can be controlled by single master controller.
Tip |
Configuring an interface as an OER-managed external interface on a router enters OER border exit interface configuration mode. In this mode, you can configure maximum link utilization or cost-based optimization for the interface. |
Note |
Entering the interface command without the external or internal keyword places the router in global configuration mode and not OER border exit configuration mode. The no form of this command should be applied carefully so that active interfaces are not removed from the router configuration. |
|
|
exit
Example:
Router(config-oer-mc-br-if)# exit
|
Exits OER-managed border exit interface configuration mode and returns to OER-managed border router configuration mode. |
|
interface type number internal
Example:
Router(config-oer-mc-br)# interface Ethernet 0/0 internal
|
Configures a border router interface as an OER controlled internal interface.
-
Internal interfaces are used for passive monitoring only. Internal interfaces do not forward traffic.
-
At least one internal interface must be configured on each border router.
Note |
Support to configure a VLAN interface as an internal interface was introduced in Cisco IOS Release 12.3(14)T and 12.2(33)SRB. |
|
|
exit
Example:
Router(config-oer-mc-br)# exit
|
Exits OER-managed border router configuration mode and returns to OER master controller configuration mode. |
|
Repeat Step 12 through Step 16 with appropriate changes to establish communication with each border router.
|
-- |
|
keepalive timer
Example:
Router(config-oer-mc)# keepalive 10
|
(Optional) Configures the length of time that an OER master controller will maintain connectivity with an OER border router after no keepalive packets have been received.
-
The example sets the keepalive timer to 10 seconds. The default keepalive timer is 60 seconds.
|
|
end
Example:
Router(config-oer-mc-learn)# end
|
Exits OER Top Talker and Top Delay learning configuration mode and returns to privileged EXEC mode. |
|
show running-config
Example:
Router# show running-config
|
(Optional) Displays the running configuration to verify the configuration entered in this task. |