Cisco Systems OL-14356-01 Network Router User Manual


 
Implementing Routing Policy on Cisco IOS XR Software
How to Implement Routing Policy on Cisco IOS XR Software
RC-408
Cisco IOS XR Routing Configuration Guide
OL-14356-01
If there are parse errors, you are asked whether editing should continue:
RP/0/RP0/CPU0:router#edit route-policy policy_B
== MicroEMACS 3.8b () == rpl_edit.141738
route-policy policy_B
set metric-type type_1
if destination in (2001::/8) then
drop
endif
end-policy
!
== MicroEMACS 3.8b () == rpl_edit.141738 ==
Parsing.
105 bytes parsed in 1 sec (103)bytes/sec
% Syntax/Authorization errors in one or more commands.!! CONFIGURATION
FAILED DUE TO SYNTAX/AUTHORIZATION ERRORS
set metric-type type_1
if destination in (2001::/8) then
drop
endif
end-policy
!
Continue editing? [no]:
If you answer yes, the editor continues on the text buffer from where you left off. If you answer no, the
running configuration is not changed and the editing session is ended.
Editing Routing Policy Configuration Elements Using the Vim Editor
Editing elements of a routing policy with Vim (Vi IMproved) is similar to editing them with Emacs
except for some feature differences such as the keystrokes to save and quit. To write to a current file and
exit, use the :wq or :x or ZZ keystrokes. To quit and confirm, use the :q keystrokes. To quit and discard
changes, use the :q! keystrokes.
You can reference detailed online documentation for Vim at this URL: http://www.vim.org/
Editing Routing Policy Configuration Elements Using the CLI
The CLI allows you to enter and delete route policy statements. You can complete a policy configuration
block by entering applicable commands such as end-policy or end-set. Alternatively, the CLI interpreter
allows you to use the exit command to complete a policy configuration block. The abort command is
used to discard the current policy configuration and return to global configuration mode.
How to Implement Routing Policy on Cisco IOS XR Software
This section contains the following procedures:
Defining a Route Policy, page RC-409 (required)
Attaching a Routing Policy to a BGP Neighbor, page RC-410 (required)
Modifying a Routing Policy Using a Text Editor, page RC-412 (optional)