[ 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 210.
  3. Go on to one of the following tasks:

Table 210: 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 Configuration>View and Edit>Edit Configuration.
  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

Configuring ES-IS

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

To configure ES-IS for the J-series Services Router:

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

Table 211: 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 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

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

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

Table 212: 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 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

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

Table 213: 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

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

Table 214: 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 Configuration>View and Edit>Edit Configuration.
  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]