Static routing configuration examples

 

·     Introduction

·     Prerequisites

·     Restrictions and guidelines

·     Example: Configuring static routes

 

The following information provides static routing configuration examples.

Static routes are manually configured. If a network's topology is simple, you only need to configure static routes for the network to work correctly.

Static routes cannot adapt to network topology changes. If a fault or a topological change occurs in the network, the network administrator must modify the static routes manually.

 

This document is not restricted to specific software or hardware versions. Procedures and information in the examples might be slightly different depending on the software or hardware version of the device.

The configuration examples were created and verified in a lab environment, and all the devices were started with the factory default configuration. When you are working on a live network, make sure you understand the potential impact of every command on your network.

The following information is provided based on the assumption that you have basic knowledge of the static routing feature.

 

When you configure a static route, make sure the network of its next hop is reachable. In addition, make sure the next hop device has a minimum of one route to reach the local device.

Network configuration

As shown in Figure 1, configure static routes on Device A, Device B, and Device C for interconnections between Host A and Host B.

Figure 1 Network diagram

 

Software versions used

This configuration example was created and verified on R8860 of the F1000-AI-55 device.

Procedure

Configuring Device A

1.     Assign IP addresses to interfaces and add the interfaces to security zones:

# On the top navigation bar, click Network.

# From the navigation pane, select Interface Configuration > Interfaces.

# Click the Edit icon for GE 1/0/2.

# In the dialog box that opens, configure the interface:

a.     Select the Untrust security zone.

b.     Click the IPv4 Address tab, and then enter the IP address and mask of the interface. In this example, enter 1.1.4.1/30.

c.     Click OK.

# Add GE 1/0/1 to the Trust security zone and set its IP address to 1.1.2.3/24 in the same way you configure GE 1/0/2.

2.     Configure security policies:

# On the top navigation bar, click Policies.

# From the navigation pane, select Security Policies > Security Policies.

# Click Create.

# In the dialog box that opens, configure security policy test-a:

¡     Enter security policy name test-a.

¡     Select source zone Trust.

¡     Select destination zone Untrust.

¡     Set the type to IPv4.

¡     Set the action to Permit.

¡     Set the source IPv4 address to 1.1.2.2/24.

¡     Set the destination IPv4 address to 1.1.3.2/24.

# Click OK.

# Click Create to create another security policy.

# In the dialog box that opens, configure security policy test-b:

¡     Enter security policy name test-b.

¡     Select source zone Untrust.

¡     Select destination zone Trust.

¡     Set the type to IPv4.

¡     Set the action to Permit.

¡     Set the source IPv4 address to 1.1.3.2/24.

¡     Set the destination IPv4 address to 1.1.2.2/24.

# Click OK.

3.     Configure a static route:

# On the top navigation bar, click Network.

# From the navigation pane, select Routing > Static Routing.

# On the IPv4 Static Routing tab, click Create.

# In the dialog box that opens, configure an IPv4 static route, as shown in Figure 3.

Figure 2 Creating an IPv4 static route

 

# Click OK.

Configuring Device B

# Configure two static routes to reach networks 1.1.2.0/24 (Device A) and 1.1.3.0/24 (Device C), respectively. The configuration method is the same as that you configure the static route on Device A. (Details not shown.)

Configuring Device C

# Configure two static routes to reach networks 1.1.2.0/24 (Device A) and 1.1.4.0/30 (Device B), respectively. The configuration method is the same as that you configure the static route on Device A. (Details not shown.)

Verifying the configuration

# Verify that Host A can ping Host B.

C:\Users\abc>ping 1.1.3.2

 

Pinging 1.1.3.2 with 32 bytes of data:

Reply from 1.1.3.2: bytes=32 time=1ms TTL=255

Reply from 1.1.3.2: bytes=32 time=1ms TTL=255

Reply from 1.1.3.2: bytes=32 time=1ms TTL=255

Reply from 1.1.3.2: bytes=32 time=1ms TTL=255

 

Ping statistics for 1.1.3.2:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 1ms, Maximum = 1ms, Average = 1ms

The output shows that Host B can be pinged from Host A.