02.10.2013 Views

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

In Figure 248, <strong>the</strong> redistribute command calls <strong>the</strong> route map staticospf to redistribute only certain static<br />

routes into OSPF. According to <strong>the</strong> route map staticospf, only routes that have a next hop of<br />

Gigabite<strong>the</strong>rnet interface 0/0 and that have a metric of 255 will be redistributed into <strong>the</strong> OSPF backbone<br />

area.<br />

Note: When re-distributing routes using route-maps, <strong>the</strong> user must take care to create <strong>the</strong><br />

route-map defined in <strong>the</strong> redistribute command under <strong>the</strong> routing protocol. If no route-map<br />

is created, <strong>the</strong>n NO routes are redistributed.<br />

Figure 248 Route Redistribution into OSPF<br />

router ospf 34<br />

default-in<strong>for</strong>mation originate metric-type 1<br />

redistribute static metric 20 metric-type 2 tag 0 route-map staticospf<br />

!<br />

route-map staticospf permit 10<br />

match interface GigabitE<strong>the</strong>rnet 0/0<br />

match metric 255<br />

set level backbone<br />

Configure a route map <strong>for</strong> route tagging<br />

One method <strong>for</strong> identifying routes from different routing protocols is to assign a tag to routes from that<br />

protocol. As <strong>the</strong> route enters a different routing domain, it is tagged and that tag is passed along with <strong>the</strong><br />

route as it passes through different routing protocols. This tag can <strong>the</strong>n be used when <strong>the</strong> route leaves a<br />

routing domain to redistribute those routes again.<br />

In Figure 249, <strong>the</strong> redistribute ospf command with a route map is used in <strong>the</strong> ROUTER RIP mode to<br />

apply a tag of 34 to all internal OSPF routes that are redistributed into RIP.<br />

Figure 249 Tagging OSPF Routes Entering a RIP Routing Domain<br />

!<br />

router rip<br />

redistribute ospf 34 metric 1 route-map torip<br />

!<br />

route-map torip permit 10<br />

match route-type internal<br />

set tag 34<br />

!<br />

Continue clause<br />

Normally, when a match is found, set clauses are executed, and <strong>the</strong> packet is <strong>the</strong>n <strong>for</strong>warded; no more<br />

route-map modules are processed. If <strong>the</strong> continue command is configured at <strong>the</strong> end of a module, <strong>the</strong> next<br />

module (or a specified module) is processed even after a match is found. Figure 250 shows a continue<br />

clause at <strong>the</strong> end of a route-map module. In this example, if a match is found in <strong>the</strong> route-map “test”<br />

module 10, module 30 will be processed.<br />

364 IP Access Control Lists, Prefix Lists, and Route-maps

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!