Manage Static Routes

CLI commands are available to manage static routes for traffic going out from the filer. These static routes can also be used for wireless access to edge filers.

The CLI commands interface with the Network Manager to manage the static routes. Each time a static route is added or deleted, all configured routes in the Network Manager are replaced with a new set of routes, which are saved in the database.

See Execute CLI Commands from the Administrator User Interface for details about running CLI commands in an edge filer.

Adding Static Routes

To add single static route, for example 192.168.1.1_32, use the following CLI: rs add /config/network/static_routes 'DestIpMask' 192.168.1.1_32 'GwIP' 200.10.1.1
where:
DestIpMask is the destination IP and destination mask, separated by underscore.
GwIP is the network gateway IP.

To add multiple static routes with same destination IP, but different masks, for example: 192.168.1.3_32, 192.168.1.4_32, use the following CLI where each static route is separated by a comma (,): rs add /config/network/static_routes 'DestIpMask' 192.168.1.3_32 'GwIP' 200.10.1.1, 'DestIpMask' 192.168.1.4_32 'GwIP' 200.10.1.1

Removing a Static Route

To remove a static route, for example, 192.168.1.1_32, use the following CLI: rs del /config/network/static_routes/192.168.1.1_32

Displaying the Defined Static Routes

To display the static routes defined for the edge filer, use the following CLI: rs show /config/network/static_routes

Cleaning the Defined Static Routes

If the static routes configuration causes connectivity problems, you can remove the defined static routes using the following CLI, while logged in as the user setup: rs exec /config/network cleanStaticRoutes