[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring a Basic Set of Static Routes (Required)

Customer routes that are connected to stub networks are often configured as static routes. Figure 58 shows a sample network.

Figure 58: Customer Routes Connected to a Stub Network

Image g015023.gif

To configure customer routes as static routes, like the ones in Figure 58, follow these steps on the Services Router to which the customer routes are connected:

Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
Perform the configuration tasks described in Table 64.
If you are finished configuring the router, commit the configuration.
Go on to one of the following procedures:
- To manually control static route selection, see Controlling Static Route Selection (Optional).
- To determine how static routes are imported into the routing and forwarding tables, see Controlling Static Routes in the Routing and Forwarding Tables (Optional).
- To define default properties for static routes, see Defining Default Behavior for All Static Routes (Optional).
- To check the configuration, see Verifying the Static Route Configuration.

Table 64: Configuring Basic Static Routes

Navigate to the Static level in the configuration hierarchy.

In the configuration editor hierarchy, select Routing options>Static.

From the top of the configuration hierarchy, enter

edit routing-options static

Add the static route 192.168.47.5/32, and define the next-hop address 10.10.10.10.

Next to Route, click Add new entry.
In the Destination box, type 192.168.47.5/32.
From the Next hop list, select Next hop.
Next to Next hop, click Add new entry.
In the Value box, type 10.10.10.10.
Click OK.

Define the static route and set the next-hop address:

set route 192.168.47.5 next-hop 10.10.10.10

[Contents] [Prev] [Next] [Index] [Report an Error]