Administrator Guide
Managing Static Routes
To minimize hops between routers, static routes are recommended in routed networks when the FluidFS cluster has multiple direct paths to
various routers. Static routes allow you to congure the exact paths through which the system communicates with various clients on a
routed network.
Consider the network shown in the following gure. The system can have only one default gateway. Assume that router X is designated as
the default gateway. Packets that are sent to clients in subnet Y are routed to router X, and are then sent back (through the switch) to
router Y. These packets travel through router X needlessly, reducing the throughput to all subnets in the network.
Figure 46. Routed Network
The solution is to dene, in addition to a default gateway, a specic gateway for certain subnets by conguring static routes. To congure
these routes, 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.
View the Static Routes
View the current static routes.
1 In the Storage view, select a FluidFS cluster.
2 Click the File System tab.
3 In the File System view, select Cluster Connectivity.
4 Click the Client Network tab. The Static Route panel displays the static routes.
Add a Static Route
When adding a static route, you must specify the subnet properties and the gateway through which to access this subnet.
1 In the Storage view, select a FluidFS cluster.
2 Click the File System tab.
3 In the File System view, select Cluster Connectivity.
4 Click the Client Network tab.
5 In the Static Route panel, click Create Static Route. The Create Static Route dialog box opens.
6 In the Target Network IP Address eld, type a network IP address (for example, 192.0.2.27).
FluidFS Administration
375