Adding or Editing a Route Map
In ASDM, you can define a route map by adding, editing, or deleting a route map name, sequence number, or redistribution.
To add or edit a route map, perform the following steps:
Step 1 In ASDM, choose Configuration > Device Setup > Routing > Route Maps.
Step 2 Click Add.
The Add Route Map or Edit Route Map dialog box appears.
Step 3 Enter the route map name and sequence number. The route map name is the name that you assign to a particular route. The sequence number is the order in which you add or delete the route map entries into the ASA.
Note If you are editing an existing route map, the fields for Route Map name and sequence number are already filled in.
Step 4 To reject route matches from redistribution, click Deny. If you use an ACL in a route map Deny clause, routes that are permitted by the ACL are not redistributed. To allow route matches for redistribution. click Permit. If you use an ACL in a route map Permit clause, routes that are permitted by the ACL are redistributed.
In addition, if you use an ACL in a route map Permit or Deny clause, and the ACL denies a route, then the route map clause match is not found and the next route map clause is evaluated.
Step 5 Click the Match Clause tab to choose routes to which this clause should be applied, and set the following parameters:
- Check the Match first hop interface of route check box to enable or disable matching the first hop interface of a route or to match any routes with the specified next hop interface. If you specify more than one interface, then the route can match either interface.
– Enter the interface name in the Interface field, or click the ellipses to display the Browse Interface dialog box.
– Choose one or more interfaces, click Interface, then click OK.
– Check the Match Address check box to enable or disable the Match address of a route or match packet.
– Check the Match Next Hop check box to enable or disable the Match next hop address of a route.
– Check the Match Route Source check box to enable or disable the Match advertising source address of the route.
– Choose Access List to Prefix List from the drop-down list to match the IP address.
– According to the previous selection, click the ellipses to display the Browse Access List or Browse Prefix List dialog box.
– Choose the ACL or prefix list that you want.
- Check the Match metric of route check box to enable or disable matching the metric of a route.
– In the Metric Value field, type the metric values. You can enter multiple values, separated by commas. This setting allows you to match any routes that have a specified metric. The metric value can range from 0 to 4294967295.
- Check the Match Route Type check box to enable or disable matching of the route type. Valid route types are External1, External2, Internal, Local, NSSA-External1, and NSSA-External2. When enabled, you can choose more than one route type from the list.
Step 6 Click the Set Clause tab to modify the following information, which will be redistributed to the target protocol:
- Check the Set Metric Clause check box to enable or disable the metric value for the destination routing protocol, and type the value in the Value field.
- Check the Set Metric Type check box to enable or disable the type of metric for the destination routing protocol, and choose the metric type from the drop-down list.
Step 7 Click the BGP Match Clause tab to choose routes to which this clause should be applied, and set the following parameters:
- Check the Match AS path access lists check box to enable matching the BGP autonomous system path access list with the specified path access list. If you specify more than one path access list, then the route can match either path access list.
- Check the Match Community check box to enable matching the BGP community with the specified community. If you specify more than one community, then the route can match either community. Any route that does not match atleast one Match community will not be advertised for outbound route maps.
– Check the Match the specified community exactly check box to enable matching the BGP community exactly with the specified community.
- Check the Match Policy list check box to configure a route map to evaluate and process a BGP policy. If you specify more than one policy list, then the route can process either policy list.
Step 8 Click the BGP Set Clause tab to modify the following information, which will be redistributed to the BGP protocol:
- Check the Set AS Path check box to modify an autonomous system path for BGP routes.
– Check the Prepend AS path check box to prepend an arbitrary autonomous system path string to BGP routes. Usually the local AS number is prepended multiple times, increasing the autonomous system path length. If you specify more than one AS path number then the route can prepend either AS numbers.
– Check the Prepend Last AS to the AS Path check box to prepend the AS path with the last AS number. Enter a value for the AS number from 1 to 10.
– Check the Convert route tag into AS Path check box to convert the tag of a route into an autonomous system path.
- Check the Set Community check box to set the BGP communities attributes.
– Click Specify Community to enter a community number, if applicable. Valid values are from 1 to 4294967200, internet, no-advertise and no-export.
– Check Add to the existing communities to add the community to the already existing communities.
– Click None to remove the community attribute from the prefixes that pass the route map.
- Check the Set local preference check box to specify a preference value for the autonomous system path.
- Check the Set weight check box to specify the BGP weight for the routing table. Enter a value between 0 and 65535.
- Check the Set origin check box to specify the BGP origin code. Valid values are Local IGP and Incomplete.
- Check the Set next hop check box to specify the output address of packets that fulfill the match clause of a route map.
– Click Specify IP address to enter the IP address of the next hop to which packets are output. It need not be an adjacent router. If you specify more than one IP address then the packets can output at either IP address.
– Click Use peer address to set the next hop to be the BGP peer address.
Step 9 Click OK.