Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Example: Configuring Static Routes for CLNS When No IGP is Present

 

This example shows how to configure static routes for CLNS.

Requirements

Before you begin, configure the network interfaces. See Interfaces User Guide for Security Devices.

Overview

In this example, you configure static routes for CLNS. In the absence of an interior gateway protocol (IGP) on a certain link, a routing device might need to be configured with static routes for CLNS prefixes to be reachable by way of that link. This might be useful, for example, at an autonomous system (AS) boundary.

When you configure static routes for CLNS, consider the following tasks:

  • Specify the iso.0 routing table option to configure a primary instance CLNS static route.

  • Specify the instance-name.iso.0 routing table option to configure a CLNS static route for a particular routing instance.

  • Specify the route nsap-prefix statement to configure the destination for the CLNS static route.

  • Specify the next-hop (interface-name | iso-net) statement to configure the next hop, specified as an ISO network entity title (NET) or interface name.

  • Include the qualified-next-hop (interface-name | iso-net) statement to configure a secondary backup next hop, specified as an ISO network entity title or interface name.

Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Step-by-Step Procedure

To configure static routes for CLNS:

  1. Configure the routes.
  2. If you are done configuring the device, commit the configuration.

Results

Confirm your configuration by issuing the show routing-options command. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

Verification

Checking the Routing Table

Purpose

Make sure that the expected routes appear in the routing table.

Action

user@host> show route table iso.0

Meaning

The static routes appear in the routing table.