Filter
Top Products
7. Click OK.
Managing Static Routes
To minimize hops between routers, static routes are recommended in routed networks when there are
multiple direct paths from the FluidFS cluster to various routers. Static routes allow you to configure the
exact paths in which the system communicates with various clients on a routed network.
Consider the network shown in the following figure. There can be only one default gateway for the
system. Assume that router X is designated as the default gateway. Packets that are sent to clients in
subnet Y would be routed to router X, which would then be sent back (through the switch) to router Y.
These packets travel through router X needlessly, reducing the throughput to all subnets in the network.
The solution is to define, in addition to a default gateway, a specific gateway for certain subnets by
configuring static routes. To do this, you must describe each subnet in your network and identify the
most suitable gateway to access that subnet.
Static routes do not have to be designated for the entire network—a default gateway is most suitable
when performance is not an issue. You can select when and where to use static routes to best meet
performance needs.
Viewing the Static Routes
View the current static route.
1. Click the Performance & Connectivity tab on the left.
2. Click the Client Network & Time tab on the top.
The static routes are displayed in the Routing pane.
Adding a Static Route
When adding a static route, specify the subnet properties and the gateway through which to access this
subnet.
1. Click the Performance & Connectivity tab on the left.
2. Click the Client Network & Time tab on the top.
3. In the Routing pane, click .
55