Protocol Independent Features
Except on the first page, right running head:
Heading1 or Heading1NewPage text (automatic)
515
Alcatel-Lucent
Beta Beta
OmniAccess 5740 Unified Services Gateway CLI Configuration Guide
ALU(config-route-map)# set as-path tag
ALU(config-route-map)# set metric 10
ALU(config-route-map)# set metric-type type-1
R
EDISTRIBUTE ROUTING INFORMATION
Redistributing information from one routing protocol to another applies to all of the
IP-based routing protocols. You can also conditionally control the redistribution of
routes between routing protocols by using Route-maps, and Access-lists.
One routing protocol exports the routes to other routing protocols. OSPF, RIP and
BGP can import as well as export routes to other dynamic routing protocols.
Connected routes and static routes cannot import routes from other routing
protocols. They can only redistribute routes to other dynamic routing protocols.
Although redistribution is a protocol-independent feature, some of the match and
set commands are specific to a particular protocol.
Command (in RCM) Description
redistribute {connected|static|bgp <1-
65535>|ospf <1-65535>}[metric <0-
16777214>|metric-type <1-2>|route-map
<map-name>|tag <0-4294967295>|subnets]
This command is used
redistribute routes to OSPF.
redistribute {bgp <1-65535>|connected
|ospf <1-65535> [match
{{external|nssa-external}[1|2]
|internal}]|static} [metric {<1-16>
|transparent}|route-map <route-map
reference>]
This command is used
redistribute routes to RIP.
Note: Currently, while
redistributing
BGP/OSPF
routes to RIP,
metric parameter
has to be
configured.
To Next Page
Loading...
