Routing

Static Routes

A Static Route defines the gateway to use for a particular network. The device supports the use of static routes to forward traffic:

Between the device and any external interface, for example, you may need to define a static route so that the device can communicate with the email server used to send event notifications.

Between the device and any GRE interface.

Note Static routes configured on the device are not used to route traffic to subnets at the other end of an IPSec VPN tunnel. The destination network’s configuration in the Security Association associated with a VPN tunnel is used for this. For more information, see “Edit the Default SA for Client-to-Site VPN Connections using L2TP over IPSec” on page 194.

Routes across a VPN are always the most specific. There is no way to configure a static route, or a route learned via RIP to override a VPN route.

You can view and manage static route from the Static Routes page (Network > Configuration > Static Routes). From this page you can:

View the list of existing routes

Select a Records per page setting to change the number of static route entries displayed in the table

Delete a static route

Create a static route

The following figure shows the Static Routes page:

Figure 6–10: Network Configuration: Static Routes Page

X Family LSM User’s Guide V 2.5.1

159