packet, and Quality of Service (QoS) values such as IP precedence: (config-route-map)# set ? as-path Prepend string for a BGP AS-path attribute automatic-tag Automatically compute TAG value OSI summary address comm-list set BGP community list (for deletion) community BGP community attribute dampening Set BGP route flap dampening parameters default Set default information extcommunity BGP extended community attribute interface Output interface IP specific information level Where to import route local-preference BGP local preference path attribute metric Metric value for destination routing protocol metric-type Type of metric for destination routing protocol origin BGP origin code Tag value for destination routing protocol weight BGP weight for routing table The IP-specific items that can be changed are accessed under the ip category: 1(config-route-map)# set ip ? default Set default information Set DF bit next-hop Next hop address precedence Set precedence field qos-group Set QOS Group ID Set type of service field Policy routing is the term used to describe using a route map to change information regarding where a packet is routed. Care should be used when policy routing, as policy-routing scenarios can involve process switching (which can put a serious strain on the router's CPU). Process switching is discussed in Chapter 15. Building a Route Map Route maps are named and are built from clauses. The name is included in each clause, and the clauses are numbered to determine the order in which they should be evaluated and to allow you to include/omit only certain steps without having to re- enter the entire route map. The default clause number is 10, and a good standard to use Building a Route Map is to number your clauses in intervals of 10. This allows you to insert multiple clauses without needing to redesign the entire route map. Individual clauses can be entered at any time. The parser will insert them in the proper order within the configuration. Each clause can either be a permit or a deny clause, with permit