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

Configuring CLNS Static Routes

If some devices in your network do not support IS-IS, you must configure CLNS static routes. You might also consider using static routes if your network is simple.

This procedure, as well as the configuration provided in Verifying CLNS VPN Configuration, uses the following ISO NET address and NSAP prefix:

To configure CLNS static routes:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or the CLI configuration editor.
  2. Perform the configuration tasks described in Table 25.
  3. If you are finished configuring the router, commit the configuration.
  4. If applicable, go on to one of the following tasks:

Table 25: Configuring Static CLNS Routes

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Routing instances level in the configuration hierarchy.
  1. In the J-Web interface, select Configuration>View and Edit>Edit Configuration.
  2. Next to Routing instances, click Configure or Edit.
  3. Under Instance name, click aaaa.

From the [edit] hierarchy level, enter

edit routing-instances aaaa

Configure the next-hop ISO NET address for an NSAP prefix.
  1. Next to Routing options, click Configure.
  2. Next to Rib, click Add new entry.
  3. In the Rib name box, type aaaa.iso.0.
  4. Next to Static, click Configure.
  5. Next to Iso route, click Add new entry.
  6. In the Destination box, type 47.0005.80ff.f800.0000.bbbb.1022/104.
  7. From the Next hop list, select Next hop.
  8. Next to Next hop, click Add new entry.
  9. In the Value box, type 47.0005.80ff.f800.0000.aaaa.1000.1921.6800.4196.00.
  10. Click OK.

Enter

set routing-options iso-route 47.0005.80ff.f800.0000.bbbb.1022/104 next-hop 47.0005.80ff.f800.0000.aaaa.1000.1921.6800.4196.00

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

[an error occurred while processing this directive]