A static route defines where to send traffic for specific destination networks.
This section describes the steps to add a static route to an ASA device.
Procedure
Step 1 | In the left pane, click . |
Step 2 | Click the ASA tab. |
Step 3 | Select a device you want to configure a static route. |
Step 4 | In the Management pane on the right, click Routing. |
Step 5 | Click to add a static route. |
Step 6 | You can enter a Description for the route. |
Step 7 | Select whether the route is for an IPv4 or IPv6 address. |
Step 8 | Configure the route properties:
Interface: Select the interface through which you want to send traffic. The gateway address needs to be accessible through this interface. You can use a Null0 route to forward unwanted or undesirable traffic so the traffic is dropped. Static Null0 routes have a favorable performance profile. You can also use static null0 routes to prevent routing loops. The ASA CLI accepts both Null0 or null0 strings.
-
Gateway IP: (Not applicable to a Null0 route) Select the network object that identifies the IP address for the gateway to the destination network. Traffic is sent to this address.
-
Metric: The administrative distance for the route, between 1 and 254. The default for static routes is 1. If there are additional routers between the interface and the gateway, enter the number of hops as the administrative distance.
Administrative distance is a parameter used to compare routes. The lower the number, the higher precedence the route is given. Connected routes (networks directly connected to an interface on the device) always take precedence over static routes.
-
Destination IP: Select the network object(s), that identifies the destination network, that contains the host(s), that uses the gateway in this route.
-
Destination Mask (only for IPv4 addressing): Enter the subnet mask for the destination IP.
-
Tracking (only for IPv4 addressing): Enter a unique identifier for the route tracking process.
|
Step 9 | Click Save. |
Step 10 | Review and deploy the changes you made, or wait and deploy multiple changes at once. |