Adding a Static Route
Routes that are permanent fixtures in the routing and forwarding tables are often configured as static routes. These routes generally do not change, and often include only one or very few paths to the destination.
To create a static route in the routing table, you must, at minimum, define the route as static and associate a next-hop address with it. The static route in the routing table is inserted into the forwarding table when the next-hop address is reachable. All traffic destined for the static route is transmitted to the next-hop address for transit.
This workflow is applicable only for next-generation firewall sites. For other sites, you can add static routes through configuration templates.
You can specify options that define additional information about static routes that is included with the route when it is installed in the routing table. All static options are optional.
To create a static route for a routing instance:
- Select Resources > Devices.
The Devices page appears.
- Click the device name that you want to configure.
The Device-Name page appears
- Click the Configuration tab.
The Physical Interfaces, Routing Instances, and Zones tab appears.
- Click Routing Instances tab.
The Routing Instances page appears.
- Select a routing instance and click View/Configure link in the Static Route column.
The Static Routes page appears.
- Click the plus icon (+) .
The Create Static Route page appears.
- Complete the configuration settings according to the guidelines provided in Table 1.
- Click OK to save the changes.
Table 1: Fields on the Create Static Route Page
Enter the IPv4 or IPv6 address depending on the type of IP address specified.
Enter the subnet for the IPv4 address or the prefix for the IPv6 address.
Enter an IPv4 or IPv6 address for the next hop depending on the type of IP address specified for the static route.
Select the interface name to be used as the next hop.
|Qualified Next Hop|
Enter an IPv4 or IPv6 address for the qualified next hop depending on the type of IP address specified for the static route.
Select the interface name to be used as the qualified next hop.
Enter the preference for the qualified next hop; the lower the number, the higher the route preference.
Enter a metric value to signify the cost for an access route for the qualified next hop.
Select the name of the next routing table to the destination.
Enter the preference for the next hop; the lower the number, the higher the route preference.
Range: 0 through 2147483647
Enter a metric value which signifies the cost for an access route, for the next hop
Range: 0 through 2147483647
Specify whether to drop packets to destination; send no ICMP unreachable
Select whether indirectly connected next hops must be resolved (Resolve) or not (Do not resolve). Select None if no action is required.
Select whether the route must be retained (Retain) or deleted from the forwarding table (Do not retain) when the routing protocol process shuts down normally. Select None if no action is required.
Select whether the route must be installed in the forwarding table (Install) or not (Do not install). Select None if no action is required.
Select whether the route must be re-advertised by routing protocols (Re-advertise) or not (Do not re-advertise). Select None if no action is required.