To create route map instances, use these commands. There is no limit to the number of match commands per route map, but theconvention is to keep the number of match filters in a route map low. Set commands do not require a corresponding matchcommand.Configuring Set ConditionsTo configure a set condition, use the following commands.• Add an AS-PATH number to the beginning of the AS-PATH.CONFIG-ROUTE-MAP modeset as-path prepend as-number [... as-number]• Generate a tag to be added to redistributed routes.CONFIG-ROUTE-MAP modeset automatic-tag• Specify an OSPF area or ISIS level for redistributed routes.CONFIG-ROUTE-MAP modeset level {backbone | level-1 | level-1-2 | level-2 | stub-area}• Specify a value for the BGP route’s LOCAL_PREF attribute.CONFIG-ROUTE-MAP modeset local-preference value• Specify a value for redistributed routes.CONFIG-ROUTE-MAP modeset metric {+ | - | metric-value}• Specify an OSPF or ISIS type for redistributed routes.CONFIG-ROUTE-MAP modeset metric-type {external | internal | type-1 | type-2}• Assign an IP address as the route’s next hop.CONFIG-ROUTE-MAP modeset next-hop ip-address• Assign an IPv6 address as the route’s next hop.CONFIG-ROUTE-MAP modeset ipv6 next-hop ip-address• Assign an ORIGIN attribute.CONFIG-ROUTE-MAP modeset origin {egp | igp | incomplete}• Specify a tag for the redistributed routes.CONFIG-ROUTE-MAP modeset tag tag-value• Specify a value as the route’s weight.CONFIG-ROUTE-MAP modeset weight valueTo create route map instances, use these commands. There is no limit to the number of set commands per route map, but theconvention is to keep the number of set filters in a route map low. Set commands do not require a corresponding match command.Access Control Lists (ACLs) 107
