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

Configuring CLNS with a Configuration Editor

To configure CLNS, you must perform the first task and then one or more of the following tasks (depending on your network):

Note: Many of the configuration statements used in this section can be included at different hierarchy levels in the configuration. For more information, see the JUNOS Routing Protocols Configuration Guide.

Configuring a VPN Routing Instance (Required)

You typically configure ES-IS, IS-IS, and CLNS static routes using a VPN routing instance. For more information about routing instances, see Configuring a VPN Routing Instance.

To configure a VPN routing instance:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 202.
  3. Go on to one of the following tasks:

Table 202: Configuring a VPN Routing Instance for CLNS

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the top of the configuration hierarchy and create the routing instance aaaa.

  1. In the J-Web interface, select Configure>CLI Tools>Point and Click CLI.
  2. Next to Routing instances, click Configure or Edit.
  3. Next to Instance, click Add new entry.
  4. In the Instance name box, type aaaa.
  5. Click OK.

From the [edit] hierarchy level, enter

edit routing-instances aaaa

Specify the instance type vrf for Layer 3 VPNs.

In the Instance type list, select vrf.

Enter

set instance-type vrf

Specify the interfaces that belong to the routing instance aaaa—for example, lo0.1, e1–2/0/0.0, and t1–3/0/0.0.

(See the interface naming conventions in Network Interface Naming.)

  1. Next to Interface, click Add New Entry.
  2. In the Interface name box, type lo0.1.
  3. Click OK.
  4. Next to Interface, click Add New Entry.
  5. In the Interface name box, type e1–2/0/0.0.
  6. Click OK.
  7. Next to Interface, click Add New Entry.
  8. In the Interface name box, type t1–3/0/0.0.
  9. Click OK.

Enter

  1. set interface lo0.1
  2. set interface e1–2/0/0.0
  3. set interface t1–3/0/0.0

Specify the route distinguisher—for example, 10.255.245.1:1.

In the Rd type box, type 10.255.245.1:1.

Enter

set route-distinguisher 10.255.245.1:1

Specify the policy for the Layer 3 VRF table—for example, target:11111:1.

  1. Next to Vrf target, click Configure.
  2. In the Community box, type target:11111:1.
  3. Click OK.

Enter

set vrf-target target:11111:1

ES-IS Overview

If a device is a PE router within a CLNS island that contains any end systems, you must configure ES-IS on the device.

End System-to-Intermediate System (ES-IS) is a protocol that resolves Layer 3 ISO network service access points (NSAP) to Layer 2 addresses. ES-IS has an equivalent role as Address Resolution Protocol (ARP) in Internet Protocol version 4 (IPv4).

ES-IS provides the basic interaction between CLNS hosts (end systems) and routers (intermediate systems). ES-IS allows hosts to advertise NSAP addresses to other routers and hosts attached to the network. Those routers can then advertise the address to the rest of the network using Intermediate System-to-Intermediate System (IS-IS). Routers use ES-IS to advertise their network entity title (NET) to hosts and routers attached to that network. ES-IS routes are exported to Layer 1 Intermediate System-to-Intermediate System (IS-IS) by default. You can also export ES-IS routes into Layer 2 IS-IS by configuring a routing policy. ES-IS generates and receives end system hello (ESH) hello messages when the protocol is configured on an interface. ES-IS is a resolution protocol that allows a network to be fully ISO integrated at both the network and data layer.

ES-IS Configuration Guidelines

End System-to-Intermediate System (ES-IS) provides the basic interaction between Connectionless Network Services (CLNS) hosts (end systems) and routers (intermediate systems). ES-IS allows hosts to advertise network services access point (NSAP) addresses to other routers and hosts attached to the network. Those routers can then advertise the address to the rest of the network using Intermediate System-to-Intermediate System (IS-IS). Routers use ES-IS to advertise their network entity title (NET) to hosts and routers attached to that network.

ES-IS routes are exported to Layer 1 Intermediate System-to-Intermediate System (IS-IS) by default. You can also export ES-IS routes into Layer 2 IS-IS by configuring a routing policy.

ES-IS is enabled only if either ES-IS or IS-IS is configured on the router. ES-IS must not be disabled. If ES-IS is not explicitly configured, the interface sends and receives only Intermediate System Hello (ISH) messages. If ES-IS is explicitly configured and disabled, the interface does not send or receive ES-IS packets. If ES-IS is explicitly configured and not disabled, the interface sends and receives ISH messages as well as ES-IS packets.

One of the interfaces configured for ES-IS must be configured with an ISO address used for hello messages. The ISO address family must be configured on an interface to support ES-IS on that interface.

Configuring ES-IS

To configure ES-IS:

  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 203.
  3. If you are finished configuring the router, commit the configuration.
  4. If applicable, go on to one of the following tasks:

    For a complete list of ES-IS configuration and operational statements, see the JUNOS Software CLI Reference Guide.

Table 203: Configuring ES-IS

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 Configure>CLI Tools>Point and Click CLI.
  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

Enable ES-IS on all interfaces.

  1. Next to Protocols, click Configure.
  2. Next to Esis, click Configure.
  3. Next to Interface, click Add new entry.
  4. In the Interface name box, type all.
  5. Click OK until you return to the Protocols statement page.

Enter

set protocols esis interface all

Configure the End System Configuration Timer

  1. Next to Protocols, click Configure.
  2. Next to Esis, click Configure.
  3. Next to Interface, click Edit.
  4. Under Interface, click the name of the interface you created.
  5. Next to End system configuration timer, enter (in seconds) how often a system reports its availability to other systems. The default is 180.
  6. Click OK until you return to the Protocols statement page.

Enter

set protocols esis interface all end-system-configuration-timer 180;

Configure Graceful Restart

  1. Next to Protocols, click Configure.
  2. Next to Esis, click Configure.
  3. Under Graceful Restart, select the DisableYes checkbox or leave it unselected to enable this feature.
  4. If enabled, enter a Restart duration between 30 and 300 seconds. The default is 180.
  5. Click OK until you return to the Protocols statement page.

Enter

set protocols esis graceful-restart restart-duration 180;

Configure Preference Value

  1. Next to Protocols, click Configure.
  2. Next to Preference Value, enter the value to determine the best path by the Routing Engine.
  3. Click OK until you return to the Protocols statement page.

Enter

set protocols esis preference value;

Configuring IS-IS for CLNS

You can configure IS-IS to exchange CLNS routes within a CLNS island. To export BGP routes into IS-IS, you must configure and apply an export policy. For more information about policies, see Configuring Routing Policies.

If you have a pure CLNS island—an island that does not contain any IP devices—you must disable IPv4 and IPv6 routing.

To configure IS-IS for CLNS:

  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 204.
  3. If you are finished configuring the router, commit the configuration.
  4. If applicable, go on to one of the following tasks:

Table 204: Configuring IS-IS to Exchange 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 Configure>CLI Tools>Point and Click CLI.
  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

Enable CLNS routing.

  1. Next to Protocols, click Configure.
  2. Next to Isis, click Configure.
  3. Next to CLNS routing, select the Yes box.

Enter

set protocols isis clns-routing

Enable IS-IS on all interfaces.

(See the interface naming conventions in Network Interface Naming.)

  1. Next to Interface, click Add new entry.
  2. In the Interface name box, type all.
  3. Click OK.

Enter

set protocols isis interface all

(Optional) To configure a pure CLNS network, disable IPv4 and IPv6 routing.

  1. Next to No ipv4 routing, select the Yes box.
  2. Next to No ipv6 routing, select the Yes box.
  3. Click OK.

Enter

set protocols isis no-ipv4-routing no-ipv6-routing

Define the BGP export policy name—for example, dist-bgp—and the family and protocol.

  1. On the main Configuration page next to Policy options, click Configure or Edit.
  2. Next to Policy statement, click Add new entry.
  3. In the Policy name box, type dist-bgp.
  4. Next to From, click Configure.
  5. In the Family list, select iso.
  6. Next to Protocol, click Add new entry.
  7. In the Value list, select bgp.
  8. Click OK until you return to the Policy statement page.

From the [edit] hierarchy level, enter

set policy-options policy-statement dist-bgp from family iso protocol bgp

Define the action for the export policy.

  1. Next to Then, click Configure.
  2. In the Accept reject list, select accept.
  3. Click OK until you return to the main Configuration page.

From the [edit] hierarchy level, enter

set policy-options policy-statement dist-bgp then accept

Apply the export policy to IS-IS.

  1. On the main Configuration page next to Routing instances, click Configure or Edit.
  2. Next to aaaa, click Protocols.
  3. Next to Isis, click Edit.
  4. Next to Export, click Add new entry.
  5. In the Value box, type dist-bgp.
  6. Click OK until you return to the Instance page.

From the [edit] hierarchy level, enter

set routing-instances aaaa protocols isis export dist-bgp

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 205.
  3. If you are finished configuring the router, commit the configuration.
  4. If applicable, go on to one of the following tasks:

Table 205: 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 Configure>CLI Tools>Point and Click CLI.
  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

Configuring BGP for CLNS

To configure BGP to carry CLNS VPN NLRI:

  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 206.
  3. If you are finished configuring the router, commit the configuration.
  4. To verify the configuration, see Verifying CLNS VPN Configuration.

Table 206: Configuring BGP to Carry CLNS VPN NLRI Messages

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Bgp level in the configuration hierarchy.

  1. In the J-Web interface, select Configure>CLI Tools>Point and Click CLI.
  2. Next to Protocols, click Configure or Edit.
  3. Next to Bgp, click Configure or Edit.

From the [edit] hierarchy level, enter

set protocols bgp group pedge-pedge neighbor 10.255.245.215 family iso-vpn unicast

Define a BGP group name—for example, pedge-pedge.

  1. Next to Group, click Add new entry.
  2. In the Group name box, type pedge-pedge.

Define a BGP peer neighbor address for the group—for example, 10.255.245.215.

  1. Next to Neighbor, click Add new entry.
  2. In the Address box, type 10.255.245.215.

Define the family.

  1. Under Family, next to Iso vpn, click Configure.
  2. Next to Unicast, select the Yes box.
  3. Click OK.
[Contents] [Prev] [Next] [Index] [Report an Error]


[an error occurred while processing this directive]