MPLS/GRE Tunnels

MPLS LSPs can use GRE tunnels to cross routing areas, Autonomous Systems, and ISPs. Bridging MPLS LSPs over an intervening IP domain is possible without disrupting the outlying MPLS domain.

LSPs can reach any destination that the GRE tunnels can reach. MPLS applications can be deployed without requiring all transit nodes to support MPLS, or requiring all transit nodes to support the same label distribution protocols (LDP or RSVP). If you use CSPF, you must configure OSPF or IS-IS through the GRE tunnel. Traffic engineering is not supported over GRE tunnels; for example, you cannot reserve bandwidth or set priority or preemption.

Configuring MPLS/GRE Tunnels: overview

MPLS LSPs can use GRE tunnels to cross routing areas, Autonomous Systems, and ISPs. Bridging MPLS LSPs over an intervening IP domain is possible without disrupting the outlying MPLS domain.

LSPs can reach any destination that the GRE tunnels can reach. MPLS applications can be deployed without requiring all transit nodes to support MPLS, or requiring all transit nodes to support the same label distribution protocols (LDP or RSVP). If you use CSPF, you must configure OSPF or IS-IS through the GRE tunnel. Traffic engineering is not supported over GRE tunnels; for example, you cannot reserve bandwidth or set priority or preemption.

JUNOScope supports configuring MPLS/GRE tunnels.

Configuring MPLS/GRE Tunnels involves three tasks:

1. Configure LSP Paths : This step is required only if you want to provide static LSP paths.
2. Configure Protocols: This step will configure protocols on interfaces.
3. Provision MPLS/GRE tunnels: Here MPLS/GRE tunnel provisioning is done.

Configuring LSP Paths

LSP Paths consist of ordered set of nodes.

To configure LSP Paths

1. In the JUNOScope main window, click Provisioning > Configure MPLS/GRE Tunnels. The Configure MPLS/GRE Tunnels dialog box appears.

   

2. Click Configure LSP Paths. The Configure LSP Paths dialog box appears.

   

3. Click Add, or select a path and click Delete if you wish to delete the path. The Configure LSP Paths dialog appears.

   Note: You can also import or export a path. See Importing an LSP Path or Exporting an LSP Path.

   

4. 4. From the Device Name drop-down, select the name of the device to which LSP Path will be applied.
5. In the Name text box, enter the name of the LSP Path. You can add a Comment.
6. Enter the Node information such as IP address and whether the node in the LSP path is Strict or Loose.

   Strict indicates that the next hop must be adjacent.

   Loose indicate that the next hop might not be adjacent.

7. Click Add to add a new node to the Path.
8. Select a node and click Remove to remove it from the path. You can click Remove All to remove all the nodes you have added
9. Use the Move Up and Move Down buttons to specify the sequence of nodes in the path.
10. Click Save to save the path to be used during MPLS/GRE Tunnel Provisioning.

    Note: Clicking Save only saves the path in the JUNOScope database. The configuration for Path will be pushed to device only during Provisioning of MPLS/GRE tunnels

11. Click Reset if you wish to only retain the nodes that are present in original Path before the changes were done
12. Click Previous to navigate to the page before this page was entered.

Exporting LSP Paths

You can export LSP paths in xml format. To export an LSP Path

To export an LSP Path

1. Click Export. The Save File dialog box appears. All the paths are exported into an xml file.

   

2. Save the xml file in a location of your choice.

Importing LSP Paths

You can import LSP Paths which you have earlier exported and saved.

To import an LSP Path

1. Click Import in the Configure LSP Paths dialog box. The Import LSP Paths dialog box appears.

   

2. Click Browse… and select the file you wish to import.
3. Select one of the option buttons: Ignore; Merge; Override.
   • Ignore—(Default) An existing record stored in the JUNOScope server takes precedence over any imported record. The imported record is ignored and the existing record is not affected. Any imported record that does not exist in the JUNOScope server is inserted.
   • Merge—If a record exists in the JUNOScope server and also exists in the imported record, the imported record is merged with the existing record and is augmented as necessary. If an imported record is in conflict with an existing record, the imported record takes precedence over the existing record. The existing record is merged with the imported record; however, the fields of the imported record take precedence over the fields of the existing record. Any imported record that does not exist in the JUNOScope server is inserted.
   • Override—All records in the JUNOScope server are deleted, then all imported records are inserted. Before the override operation occurs, a message window appears with the following confirmation prompt: “ The import with override option will delete all the existing records. Do you want to continue?” Select Yes or No to continue.
4. Click Import.

Configuring Protocols

You can specify the protocols to be configured on interfaces.

To configure a protocol

1. Click Configure Protocols under MPLS/GRE Tunnels. The Configure Protocols dialog appears.

   

2. From the Device Name drop-down, select the name of the device to which protocols are to be configured.
3. From the Protocols drop-down, select one of the following: ISIS, MPLS, LDP, RSVP, OSPF, INET.
4. Click Open. Depending on the protocol selected, parameters specific to it appear. The parameters for specific interfaces are described in the following sections.

   Note: For all protocols, you can select the Enable on all Interfaces check box. For selecting the interfaces and other specific parameters, follow the steps below.

5. Click Save to save the interfaces to be used during MPLS/GRE Tunnel Provisioning.

   Note: Save will only save the protocols to be configured in JUNOScope database. Actual configuration will be pushed to device only during Provisioning of MPLS/GRE tunnels.

For ISIS

1. Select the interface(s).
2. Specify the Logical Unit. You can select the Disable check box.
3. Select the Level from the drop-down.
4. Click Add.
5. You can use Move Up and Move Down buttons to reorder the sequence.

For LDP

1. Select the interface(s).
2. Specify the Logical Unit. You can select the Disable check box.
3. Click Add.
4. You can use Move Up and Move Down buttons to reorder the sequence.

For MPLS

1. Select the interface(s).
2. Specify the Logical Unit. You can select the Disable check box.
3. Click Add.
4. You can use Move Up and Move Down buttons to reorder the sequence.

For OSPF

1. Select the interface(s).
2. Specify the Logical Unit. You can select the Disable check box.
3. Specify the Area.
4. Select the Traffic Engineering (TE) check box.
5. Click Add.
6. You can use Move Up and Move Down buttons to reorder the sequence.

For RSVP

1. Select the interface(s).
2. Specify the Logical Unit. You can select the Disable check box.
3. Optionally, select Node Protection and Link Protection check boxes.
4. Click Add.
5. You can use Move Up and Move Down buttons to reorder the sequence.

For INET

1. Select the interface(s).
2. Specify the Logical Unit. You can select the Disable check box.
3. Specify the IP Address and Mask.
4. Click Add.
5. You can use Move Up and Move Down buttons to reorder the sequence.

MPLS/GRE Tunnel Provisioning

Three types of tunnels will be supported. These are : MPLS RSVP tunnel; MPLS LDP tunnel; and GRE tunnel The MPLS/GRE Tunnel Provisioning proceeds in four steps as described in the following sections.

Step1: Select Device Sources and Source/Destination devices

In this step you choose the device source and destination endpoint devices.

You can select device source by selecting either a group or by selecting devices directly You can choose one of the device groups from a list of device groups already created.

Device groups can be created by grouping devices dynamically based on some filtering criteria such as location, name, model, hostname . Alternatively, devices can be grouped using static labels. When you select a device group, the corresponding device group will be expanded and all the ASG/CSG devices will be shown in Destination endpoint.

You can also directly select devices already added to JUNOScope: in this case, all the devices in ASG devices in JUNOScope will be shown in Select ASG/CSG Devices list.

To select a device source

1. Select an option button to specify whether you wish to Select Devices Directly or Select a Device Group.
2. If you choose to select devices directly, you can search for devices on the following criteria under Find a device that includes the following:
   • You can select a field such as Device Name, Device Hostname, Model, Location or Comment.
   • You can select an operator such as Contains, Does not Contain, Starts With, Ends with, Equals.
   • You can enter a value to search and click View to display a list of devices.
3. Select at least two Devices and click Next.

Step 2: Add/Edit/Delete Tunnel

In this step, you will provide details about the tunnel.

Three types of tunnel are supported. These are:MPLS-RSVP, MPLS-LDP, GRE

Community Member is used to identify a community used for mapping the LSP to a policy-based community.

Note: In the JUNOScope implementation for Tunnel Provisioning, for an ASG device a one to one mapping is done between LSP and Community (using the same name) if a unique Community Member is provided. If for an ASG device user does not provide unique Community Member, this particular LSP can not be mapped to a pseudowire.

However, for CSG device, community member field is not required.

To Add/Edit/Delete Tunnel

1. From the Tunnel Type drop-down, select a tunnel type. The available values are: MPLS – RSVP, MPLS – LDP, and GRE.
2. From the Source Device and Destination Device drop-downs, select the source and device names.
3. Under Provide Source Endpoint Details:
   1. Specify an LSP Name and LSP Bandwidth.
   2. Select an LSP Path to be used as Primary for the LSP Name entered. This field is required only if Tunnel type selected is MPLS-RSVP. For MPLS-LDP and GRE tunnel type this field will be disabled.
   3. Select an LSP Path to be used as Secondary for the LSP Name entered. This should be different from the Primary LSP Path.

      This field is required only if Tunnel type selected is MPLS-RSVP. For MPLS-LDP and GRE tunnel type this field will be disabled.

      Note: You should specify a different LSP Primary Path and LSP Secondary Path.

   4. From the respective drop-downs, select the Setup Priority, Reservation Priority, and the QoS Priority.
   5. Check the Enable Fast Reroute check box to enable fast reroute.

      This field is used only if Tunnel type selected is MPLS-RSVP Otherwise, this field will be unchecked.

   6. Specify the Reroute Bandwidth, which is the bandwidth reserved for reroute

      This field will be enabled if Tunnel Type is MPLS-RSVP and Enable Fast Reroute check box is checked. Otherwise this field will be disabled.

   7. Specify the Hop Limit, which is the maximum number of hops.

      This field will be enabled if Tunnel Type is MPLS-RSVP and Enable Fast Reroute check box is selected. Otherwise this field will be disabled.

   8. Select the check boxes, if you wish to, Enable Node Link Protection and Enable Link Protection.
   9. Select the GRE Interface, if the tunnel type is GRE, from the drop-down.
   10. Specify the Logical Unit for tunnel interface or software tunnel interface.

       This field is required only when tunnel type selected is GRE. For MPLS-RSVP, MPLS-LDP this field will be disabled.

4. Repeat step 3 and all the substeps for the Device End Point, under Provide Destination Endpoint Details.
5. Click Add Entry to add a record in the list area.
6. Click Edit/View/Delete to edit, view, or delete selected tunnels.
7. Click Next to go to Step 3 of the wizard or click Previous to go to Step 1 of the wizard.

   Note: You can click Force Deploy to push the configuration details to the devices, without making modifications to it, if you are editing the cofiguration.

The tabular area at the bottom displays all the tunnels between devices that are selected in Step 1 of the wizard.

The following information is presented in the table:

• State

  State reflects the state of the record, namely:

  • New: If a record is newly added. The state field will be shown in blue.
  • Modified: If a record is modified. The state field will be shown in Red.
  • Unchanged: If a record is not modified. The state field will be shown in green.

    Note: If multiple users are simultaneously accessing this wizard, each user will have different working records and changes in records will be stored at session level.

• Tunnel Type
• Source Device
• Source LSP
• Source GRE Interface
• Destination Device
• Destination LSP
• Destination GRE Interface

Step 3: Confirm Tunnel selections

In this step you will confirm the creation, deletion, or modification of the Tunnel Parameters that you selected in step 2. Any validation errors will be reported in this step.

To confirm Tunnel selections

1. Click Confirm to go to Step 4 of the wizard (Provision Tunnels).
2. Click Previous to go to Step 2 of the wizard (Add/Edit/Delete Tunnels).

Step 4: Provision MPLS/GRE Tunnels

In this step configurations are generated for MPLS/GRE tunnels created in step 3 and are pushed to devices.

To provision MPLS/GRE Tunnels

1. Select the Now radio button to push the configuration to the devices in realtime.
2. Select the save Operation As button radio button and provide a name for the operation: the configuration can be saved as a named operation.
3. Select the Schedule radio button to select a schedule. The configurations will be pushed at the scheduled time.

   Note: The schedule can be chosen from those defined in Settings. See Settings

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.