Dell Force10 S25N-S50N FTOS Configuration Guide FTOS 8.4.2.7 E-Series TeraScal - Page 166

www.dell.com | support.dell.com Command Syntax set ipv6 next-hop ip-address set origin {egp | igp | incomplete} set tag tag-value set weight value Command Mode CONFIG-ROUTE-MAP CONFIG-ROUTE-MAP CONFIG-ROUTE-MAP CONFIG-ROUTE-MAP Purpose Assign an IPv6 address as the route's next hop. Assign an ORIGIN attribute. Specify a tag for the redistributed routes. Specify a value as the route's weight. Use these commands to create route map instances. There is no limit to the number of set and match commands per route map, but the convention is to keep the number of match and set filters in a route map low. Set commands do not require a corresponding match command. Configure a route map for route redistribution Route maps on their own cannot affect traffic and must be included in different commands to affect routing traffic. To apply a route map to traffic on the E-Series, you must call or include that route map in a command such as the redistribute or default-information originate commands in OSPF, ISIS, and BGP. Route redistribution occurs when FTOS learns the advertising routes from static or directly connected routes or another routing protocol. Different protocols assign different values to redistributed routes to identify either the routes and their origins. The metric value is the most common attribute that is changed to properly redistribute other routes into a routing protocol. Other attributes that can be changed include the metric type (for example, external and internal route types in OSPF) and route tag. Use the redistribute command in OSPF, RIP, ISIS, and BGP to set some of these attributes for routes that are redistributed into those protocols. Route maps add to that redistribution capability by allowing you to match specific routes and set or change more attributes when redistributing those routes. In Figure 8-25, the redistribute command calls the route map static ospf to redistribute only certain static routes into OSPF. According to the route map static ospf, only routes that have a next hop of Gigabitethernet interface 0/0 and that have a metric of 255 will be redistributed into the OSPF backbone area. Note: When re-distributing routes using route-maps, the user must take care to create the route-map defined in the redistribute command under the routing protocol. If no route-map is created, then NO routes are redistributed. Figure 8-25. Route Redistribution into OSPF 166 | IP Access Control Lists (ACL), Prefix Lists, and Route-maps