Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring MPLS Protocol (NSM Procedure)

    You can enable MPLS on the router using the MPLS option. See the following topics:

    Enabling MPLS on the Router (NSM Procedure)

    You can enable MPLS on the router using the MPLS option.

    To enable MPLS on the router in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols.
    4. Select Mpls.
    5. Add or modify settings as specified in Table 1.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 1: MPLS Configuration Details

    TaskYour Action

    Enable MPLS on the router.

    1. In the Comment box, enter the comment.
    2. Select the Disable check box to disable the functionality of the configured object.
    3. From the Traffic Engineering list, select whether MPLS performs traffic engineering on BGP destinations only or on both BGP and IGP destinations.
    4. From the Advertisement Hold Time list, select the hold time, in seconds.

      Range: 0 through 65,535 seconds

      Default: 5 seconds

    5. From the Rsvp Error Hold Time list, select the amount of time MPLS retains RSVP PathErr messages and considers them for CSPF computations.

      Range: 0 through 240 seconds

      Default: 25 seconds

    6. Select the Optimize Aggressive check box to enable aggressive optimization.
    7. From the Smart Optimize Timer list, select the number of seconds to wait before switching an LSP back to its original path.

      Range: 0 through 65,535 seconds

      Default: 180 seconds

    8. Select the No Propagate Ttl check box to disable normal time-to-live (TTL) decrementing.
    9. Select the Explicit Null check box to advertise label 0 to the egress router of an LSP.
    10. Select the IPv6 Tunneling check box to allow IPv6 routes to be resolved over an MPLS network.
    11. Select the Icmp Tunneling check box to enable ICMP tunneling, which can be used for debugging and tracing purposes.
    12. From the Revert Timer list, select the amount of time (in seconds) that an LSP must wait before traffic reverts to a primary path.

      Range: 0 through 65,535 seconds

      Default: 60 seconds

     
    1. Select the Expand Loose Hop check box to allow an LSP to traverse multiple OSPF areas within a service provider’s network.
    2. From the Class Of Service list, select the CoS value.

      Range: 0 through 7

      Default: If you do not specify a CoS value, the IP precedence bits from the packet’s IP header are used as the packet’s CoS value.

    3. Select the No Decrement Ttl check box to disable normal time-to-live (TTL) decrementing.
    4. From the Hop Limit list, select the maximum number of hops.

      Range: 2 through 255 (for an LSP); 0 through 255 (for fast reroute)

      Default: 255 (for an LSP); 6 (for fast reroute)

    5. Select the No Cspf check box to disable constrained-path LSP computation.
    6. Select the Admin Down check box to indicate the administrative down status for an LSP.
    7. From the Optimize Timer list, select the length of the optimize timer, in seconds.

      Range: 0 through 65,535 seconds

      Default: 0 seconds (the optimize timer is disabled)

    8. From the Preference list, select the preference to assign to the route. A route with a lower preference value is preferred.

      Range: 0 through 4,294,967,295

      Default: 5 for static MPLS LSPs, 7 for RSVP MPLS LSPs, 9 for LDP MPLS LSPs

    9. From the Setup Priority list, select the setup priority.

      Range: 0 through 7, where 0 is the highest and 7 is the lowest priority

      Default: 7 (The session cannot preempt any existing sessions.)

     
    1. From the Reservation Priority list, select the reservation priority, used to keep a reservation after it has been set up.

      Range: 0 through 7, where 0 is the highest and 7 is the lowest priority

      Default: 0 (Once the session is set up, no other session can preempt it.)

    2. Select one of the following:
      • record—to specify whether an LSP should actively record the routes in the path.
      • no-record—to specify whether an LSP should not record the routes in the path.
    3. Select the standby check box to have the path remain up at all times to provide instant switchover if connectivity problems occur.

    Configuring Administrative Group (NSM Procedure)

    You can configure an administrative group constraint for each LSP or for each primary or secondary LSP path using the Admin Group option.

    To configure an administrative group in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols.
    4. Select Mpls.
    5. Add or modify settings as specified in Table 2.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 2: Administrative Group Configuration Details

    TaskYour Action

    Configure administrative group.

    1. Click Admin Group next to Mpls.
    2. In the Comment box, enter the comment.

    Define the administrative groups to exclude for an LSP or for a path’s primary and secondary paths.

    1. Click Exclude next to Admin Group.
    2. Click Add new entry next to Exclude.
    3. In the New exclude window, enter the names of one or more groups.

    Require the LSP to traverse links that include all of the defined administrative groups.

    1. Click Include All next to Admin Group.
    2. Click Add new entry next to Include All.
    3. In the New include-all window, enter the names of one or more groups.

    Define the administrative groups to include for an LSP or for a path’s primary and secondary paths.

    1. Click Include Any next to Admin Group.
    2. Click Add new entry next to Include Any.
    3. In the New include-any window, enter the names of one or more groups.

    Configuring Administrative Groups (NSM Procedure)

    You can configure administrative groups to implement link coloring of resource classes using the Admin Groups option.

    To configure administrative groups in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols.
    4. Select Mpls.
    5. Add or modify settings as specified in Table 3.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 3: Administrative Groups Configuration Details

    TaskYour Action

    Configure administrative groups.

    1. Click Admin Groups next to Mpls.
    2. Click Add new entry next to Admin Groups.
    3. In the Name box, enter the name of the group. You can assign up to 32 names.
    4. In the Comment box, enter the comment.
    5. From the Group Value list, select the value assigned to the group.

      Range: 0 through 31

    Define the administrative groups to exclude for an LSP or for a path’s primary and secondary paths.

    1. Click Exclude next to Admin Group.
    2. Click Add new entry next to Exclude.
    3. In the New exclude window, enter the names of one or more groups.

    Require the LSP to traverse links that include all of the defined administrative groups.

    1. Click Include All next to Admin Group.
    2. Click Add new entry next to Include All.
    3. In the New include-all window, enter the names of one or more groups.

    Define the administrative groups to include for an LSP or for a path’s primary and secondary paths.

    1. Click Include Any next to Admin Group.
    2. Click Add new entry next to Include Any.
    3. In the New include-any window, enter the names of one or more groups.

    Configuring Bandwidth for the Reroute Path (NSM Procedure)

    When configuring fast reroute, allocate bandwidth for the reroute path. By default, no bandwidth is reserved for the rerouted path. The fast reroute bandwidth does not need to be identical to that allocated for the LSP itself.

    To configure bandwidth for the reroute path in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols.
    4. Select Mpls.
    5. Add or modify settings as specified in Table 4.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 4: Automatic Policers Configuration Details

    TaskYour Action

    Allocate bandwidth for the reroute path.

    1. Click Bandwidth next to Mpls.
    2. In the Comment box, enter the comment.
    3. In the Per Traffic Class Bandwidth box, enter the bandwidth, in bits per second.
    4. In the Ct0 box, enter the bandwidth, for the specified class.
    5. In the Ct1 box, enter the bandwidth, for the specified class.
    6. In the Ct2 box, enter the bandwidth, for the specified class.
    7. In the Ct3 box, enter the bandwidth, for the specified class.

    Apply the same policer action to all the class types.

    1. Click Class next to Automatic Policing.
    2. Click Add new entry next to Class.
    3. From the Name list, select the class type to which the policer action is to be applied.
    4. In the Comment box, enter the comment.
    5. Select one of the policer actions.
      • drop—Drop all packets.
      • loss-priority-high—Set the packet loss priority (PLP) to high.
      • loss-priority-low—Set the PLP to low.

    Configuring DiffServ-Aware Traffic Engineering (NSM Procedure)

    Differentiated Services (DiffServ)-aware traffic engineering provides a way to guarantee a specified level of service over an MPLS network. The routers providing DiffServ-aware traffic engineering are part of a differentiated services network domain. All routers participating in a differentiated services domain must have DiffServ-aware traffic engineering enabled.

    To configure DiffServ-aware traffic engineering in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols.
    4. Select Mpls.
    5. Add or modify settings as specified in Table 5.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 5: DiffServ-Aware Traffic Engineering Configuration Details

    TaskYour Action

    Configure DiffServ-aware traffic engineering.

    1. Click Diffserv Te next to Mpls.
    2. In the Comment box, enter the comment.
    3. In the Per Traffic Class Bandwidth box, enter the bandwidth, in bits per second.
    4. From the Bandwidth Model list, select the bandwidth model for differentiated services.
      • extended-mam—The extended maximum allocation model (MAM) is a bandwidth model based on MAM.
      • mam—The MAM is defined in RFC 4125, Maximum Allocation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering.
      • rdm—The Russian dolls bandwidth allocation model (RDM) is defined in RFC 4127, Russian Dolls Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering.

    Specify the traffic engineering class matrix for a multiclass label switched path (LSP) or a DiffServ-aware traffic engineering LSP.

    1. Click Te Class Matrix next to Diffserv Te.
    2. In the Comment box, enter the comment.
    3. For the traffic engineering classes, configure the following:
      1. In the Comment box, enter the comment.
      2. From the Traffic Class list, select the traffic class for the traffic engineering class.
      3. From the Priority list, select the priority of the class type.

        Range: 0 through 7

    Configuring MPLS on Interfaces (NSM Procedure)

    To configure MPLS on interfaces in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols.
    4. Select Mpls.
    5. Add or modify settings as specified in Table 6.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 6: Interface Configuration Details

    TaskYour Action

    Enable MPLS on one or more interfaces.

    1. Click Interface next to Mpls.
    2. Click Add new entry next to Interface.
    3. In the Name box, enter the Name of the interface on which to configure MPLS.
    4. In the Comment box, enter the comment.
    5. Select the Disable check box to disable the functionality of the configured object.

    Define administrative groups for an interface.

    1. Click Admin Group next to interface.
    2. In the Comment box, enter the comment.
    3. Click Add new entry next to Admin Group.
    4. In the New admin-group window, enter one or more names of groups.

    Label MPLS packets.

    1. Click Label Map next to interface.
    2. Click Add new entry next to Label Map.
    3. In the Name box, enter the interface name.
    4. From the Swap list, select the label value.

      Range: 1,000,000 through 1,048,575. Labels 0 through 999,999 are for internal use. Labels 1,000,000 through 1,048,575 are unassigned by the Junos OS and are available for static label switched paths (LSPs). When you configure static LSPs, you can use only this range of labels.

    5. From the Swap Label list, select the label value.
    6. From the Push Label list, select the label value.

      Range: 0 through 1,048,575

    7. Select the Pop check box to remove the label from the top of the label stack.
    8. From the Preference list, select the preference to be assigned to the route.

      Range: 0 through 4,294,967,295

      Default: 5 for static MPLS LSPs, 7 for RSVP MPLS LSPs, 9 for LDP MPLS LSPs

    9. From the Class of Service list, select the CoS value.

      Range: 0 through 7

      Default: If you do not specify a CoS value, the IP precedence bits from the packet’s IP header are used as the packet’s CoS value

    Configure IP address of the next hop to the destination.

    1. Select one of the following:
      • next-hop—to configure the IP address of the next hop to the destination.
        1. Enter the IP address of the next-hop router.
      • reject—to reject the packet.
      • discard—to discard the packet.

    Configure a Label Switched Path (LSP) to Use in Dynamic MPLS

    Configuring Label Switched Path (NSM Procedure)

    You can configure a label switched path (LSP) to use in dynamic MPLS.

    To configure a LSP in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols.
    4. Select Label Switched Path.
    5. Add or modify settings as specified in Table 7.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 7: LSP Configuration Details

    TaskYour Action

    Configure label switched path.

    1. Click Add new entry next to Label Switched Path.
    2. In the Name box, enter the name that identifies the LSP.
    3. In the Comment box, enter the comment.
    4. Select the Disable check box to disable the functionality of the configured object.
    5. Select the No Install To Address check box to prevent the egress router address configured using the to statement from being installed into the inet.3 and inet.0 routing tables.
    6. Select the Backup check box to configure a backup provider edge (PE) group for ingress PE router redundancy when point-to-multipoint LSP are used for multicast distribution.
    7. In the From box, enter the source address to use for the LSP.
     
    1. Select the Ldp Tunneling check box to enable the LSP to be used for LDP tunneling.
    2. From the Metric list, select the LSP metric value

      Default: No metric assigned (dynamic)

      Range: 1 through 16,777,215

    3. From the Retry Timer list, select the amount of time between attempts to connect to the primary path.

      Default: 30 seconds

      Range: 1 through 600 seconds

    4. From the Retry Limit list, select the maximum number of tries to establish the primary path.

      Default: 0 (The ingress node never stops trying to establish the primary path.)

      Range: 0 through 10,000

    5. From the Revert Timer list, select the amount of time (in seconds) that an LSP must wait before traffic reverts to a primary path.

      Default: 60 seconds

      Range: 0 through 65,535 seconds

    6. From the Class 0f Service list, select the CoS value.

      Range: 0 through 7.

      Default: If you do not specify a CoS value, the IP precedence bits from the packet’s IP header are used as the packet’s CoS value.

    7. Select the No Decrement Ttl check box to disable normal time-to-live (TTL) decrementing.
    8. From the Hop Limit list, select the maximum number of hops.

      Range: 2 through 255 (for an LSP); 0 through 255 (for fast reroute)

      Default: 255 (for an LSP); 6 (for fast reroute)

    9. Select the No Cspf check box to disable constrained-path LSP computation.
     
    1. Select the Admin Down check box to set the A-bit in the Admin Status object.
    2. From the Optimize Timer list, select the length of the optimize timer, in seconds.

      Range: 0 through 65,535 seconds

      Default: 0 seconds (the optimize timer is disabled)

    3. From the Preference list, select the preference to assign to the route.

      Range: 1 through 255

      Default: 5 for static MPLS LSPs, 7 for RSVP MPLS LSPs, 9 for LDP MPLS LSPs

    4. From the Setup Priority list, select the setup priority.

      Range: 0 through 7, where 0 is the highest and 7 is the lowest priority.

      Default: 7 (The session cannot preempt any existing sessions.)

    5. From the Reservation Priority list, select the reservation priority.

      Range: 0 through 7, where 0 is the highest and 7 is the lowest priority.

      Default: 0 (Once the session is set up, no other session can preempt it.)

     
    1. Select one of the following:
      • record—Record routes
      • no-record—Does not record routes
    2. Select the Standby check box to have the path remain up at all times to provide instant switchover if connectivity problems occur.
    3. Select one of the following options:
      • random—Choose the path at random.
      • least-fill—Prefer the path with the most available bandwidth (with the largest minimum available bandwidth ratio).
      • most-fill—Prefer the path with the least available bandwidth (with the minimum available bandwidth ratio). The minimum available bandwidth ratio of a path is the smallest available bandwidth ratio belonging to any of the links in the path.
    4. In the Description box, enter the textual description of the LSP.
    5. Select one of the following options:
      • link-protection—Enable link protection.
      • node-link-protection—Enable node and link protection on the specified LSP.
      • most-fill—Prefer the path with the least available bandwidth (with the minimum available bandwidth ratio). The minimum available bandwidth ratio of a path is the smallest available bandwidth ratio belonging to any of the links in the path.
    6. Select the Adaptive check box for RSVP to use shared explicit (SE) reservation styles and assists in smooth transition during rerouting.
    7. Select the Associate backup Pe Groups check box to enable an LSP to monitor the status of its destination PE router.

    Configuring Administrative Group (NSM Procedure)

    You can configure an administrative group constraint for each Label Switched Path (LSP) or for each primary or secondary LSP path using the Admin Group option.

    To configure an administrative group in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols > MPLS.
    4. Select Label Switched Path.
    5. Add or modify settings as specified in Table 8.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 8: Administrative Group Configuration Details

    TaskYour Action

    Configure administrative group.

    1. Click Add new entry next to Label Switched Path.
    2. Click Admin Group next to label-switched-path.
    3. In the Comment box, enter the comment.

    Define the administrative groups to exclude for an LSP or for a path’s primary and secondary paths.

    1. Click Exclude next to Admin Group.
    2. Click Add new entry next to Exclude.
    3. In the New exclude window, enter the names of one or more groups.

    Require the LSP to traverse links that include all of the defined administrative groups.

    1. Click Include All next to Admin Group.
    2. Click Add new entry next to Include All.
    3. In the New include-all window, enter the names of one or more groups.

    Define the administrative groups to include for an LSP or for a path’s primary and secondary paths.

    1. Click Include Any next to Admin Group.
    2. Click Add new entry next to Include Any.
    3. In the New include-any window, enter the names of one or more groups.

    Configuring Automatic Bandwidth Allocation for LSPs (NSM Procedure)

    Automatic bandwidth allocation allows an MPLS tunnel to automatically adjust its bandwidth allocation based on the volume of traffic flowing through the tunnel. You can configure an LSP with minimal bandwidth, and this feature can dynamically adjust the LSP’s bandwidth allocation based on current traffic patterns.

    To configure automatic bandwidth allocation in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols > MPLS.
    4. Select Label Switched Path.
    5. Add or modify settings as specified in Table 9.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 9: Automatic Bandwidth Configuration Details

    TaskYour Action

    Configure automatic bandwidth.

    1. Click Add new entry next to Label Switched Path.
    2. Click Auto Bandwidth next to label-switched-path.
    3. Select the Enable Feature check box to enable the option.
    4. In the Comment box, enter the comment.
    5. From the Adjust Interval list, select the bandwidth reallocation interval, in seconds.

      Range: 300 through 4,294,967,295 seconds

      Default: 86,400 seconds

    6. From the Adjust Threshold list, select the threshold for automatic bandwidth adjustment.
    7. In the Minimum Bandwidth box, enter the minimum bandwidth in bits per second (bps) for an LSP with automatic bandwidth allocation enabled.
    8. In the Maximum Bandwidth box, enter the maximum amount of bandwidth in bits per second (bps).
    9. Select the Monitor Bandwidth check box to configure passive bandwidth utilization monitoring.
    10. From the Adjust Threshold Overflow Limit list, select the number of consecutive bandwidth overflow samples.

      Range: 1 through 65,535

    Configuring Bandwidth for the Reroute Path (NSM Procedure)

    When configuring fast reroute, allocate bandwidth for the reroute path. By default, no bandwidth is reserved for the rerouted path. The fast reroute bandwidth does not need to be identical to that allocated for the LSP itself.

    To configure bandwidth for the reroute path in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols > Mpls.
    4. Select Label Switched Path.
    5. Add or modify settings as specified in Table 10.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 10: Bandwidth Configuration Details

    TaskYour Action

    Allocate bandwidth for the reroute path.

    1. Click Add new entry next to Label Switched Path.
    2. Click Bandwidth next to label-switched-path.
    3. In the Comment box, enter the comment.
    4. In the Per Traffic Class Bandwidth box, enter the bandwidth, in bits per second.
    5. In the Ct0 box, enter the bandwidth, for the specified class.
    6. In the Ct1 box, enter the bandwidth, for the specified class.
    7. In the Ct2 box, enter the bandwidth, for the specified class.
    8. In the Ct3 box, enter the bandwidth, for the specified class.

    Configuring Fast Reroute (NSM Procedure)

    Fast reroute provides a mechanism for automatically rerouting traffic on an LSP if a node or link in an LSP fails, thus reducing the loss of packets traveling over the LSP.

    To configure fast reroute in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols > Mpls.
    4. Select Label Switched Path.
    5. Add or modify settings as specified in Table 11.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 11: Fast Reroute Configuration Details

    TaskYour Action

    Configure fast reroute.

    1. Click Fast Reroute next to Label Switched Path.
    2. Select the Enable Feature check box to enable the option.
    3. In the Comment box, enter the comment.
    4. From the Hop Limit list, select the maximum number of hops.

      Range: 2 through 255 (for an LSP); 0 through 255 (for fast reroute)

      Default: 255 (for an LSP); 6 (for fast reroute)

    Allocate bandwidth for the reroute path.

    1. Click Bandwidth next to Fast Reroute.
    2. Select one of the following:
      • bandwidth—specify the traffic rate associated with the LSP and enter the bandwidth.
      • bandwidth-percent—configure the percentage of bandwidth to reserve for the detour path in case the primary path for a traffic engineered LSP or a multiclass LSP fails and select the bandwidth percentage.

    Control exclusion of administrative groups.

    1. Select one of the following:
      • exclude—Define the administrative groups to exclude for fast reroute.
        1. Click Add new entry next to exclude.
        2. In the New exclude window, enter the names of one or more groups.
      • no-exclude—Disable administrative group exclusion.

    Control inclusion of administrative groups.

    1. Select one of the following:
      • include-all—Define the administrative groups that must all be included for fast reroute.
        1. Click Add new entry next to include-all.
        2. In the New include-all window, enter the names of one or more groups.
      • no-include-all—Disable administrative group inclusion.

    Control inclusion of administrative groups.

    1. Select one of the following:
      • include-any—Define the administrative groups to include for fast reroute.
        1. Click Add new entry next to include-any.
        2. In the New include-any window, enter the names of one or more groups.
      • no-include-any—Disable administrative group inclusion.

    Adding LSP-Related Routes to the inet.3 Routing Table (NSM Procedure)

    By default, a host route toward the egress router is installed in the inet.3 routing table. Installing the host route allows BGP to perform next-hop resolution. It also prevents the host route from interfering with prefixes learned from dynamic routing protocols and stored in the inet.0 routing table.

    To add additional routes into the inet.3 routing table in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols > Mpls.
    4. Select Label Switched Path.
    5. Add or modify settings as specified in Table 12.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 12: Install Configuration Details

    TaskYour Action

    Associate one or more prefixes with an LSP.

    1. Click Add new entry next to Label Switched Path.
    2. Click Install next to label-switched-path.
    3. Click Add new entry next to Install.
    4. In the Name box, enter the routing table.
    5. In the Comment box, enter the comment.
    6. Select the Active check box to install the route into the inet.0 routing table. This allows you to issue a ping or traceroute command on this address.

    Configuring MPLS LSPs for GMPLS (NSM Procedure)

    To enable the proper GMPLS switching parameters you can use the Lsp Attributes option.

    To configure the LSP attributes in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols > Mpls.
    4. Select Label Switched Path.
    5. Add or modify settings as specified in Table 13.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 13: Lsp Attributes Configuration Details

    TaskYour Action

    Define the parameters signaled during LSP setup.

    1. Click Add new entry next to Label Switched Path.
    2. Click Lsp Attributes next to label-switched-path.
    3. In the Comment box, enter the comment.
    4. From the Signal Bandwidth list, select the type of bandwidth encoding used on the LSP. The options available for selection are 10gigether, ds1, ds3, e1, e3, ethernet, fastether, gigether, stm-1, stm-4, stm-16, stm-64, stm-256, sts-1, vt1-5, or vt2.
    5. From the Switching Type list, select the switching method for the LSP. Select one of the following:
      • fiber—Fiber switching
      • lambda—Lambda switching
      • psc-1—Packet switching
      • tdm—Time-division multiplexing (TDM) switching
    6. From the Encoding Type list, select the encoding type of payload carried by the LSP. Select one of the following:
      • ethernet—Ethernet
      • packet—Packet
      • pdh—Plesiochronous digital hierarchy (PDH)
      • sonet-sdh—SONET/SDH
    7. From the Gpid list, select the type of payload carried by the LSP. Select one of the following:
      • ethernet—Ethernet (GPID value: 33)
      • hdlc—High-level Data Link Control (HDLC) (GPID value: 44)
      • ipv4—IP version 4 (GPID value: 0x0800)
      • pos-no-scrambling-crc-16—for interoperability with other vendors’ equipment (GPID value: 29)
      • pos-no-scrambling-crc-32—for interoperability with other vendors’ equipment (GPID value: 30)
      • pos-scrambling-crc-16—for interoperability with other vendors’ equipment (GPID value: 31)
      • pos-scrambling-crc-32—for interoperability with other vendors’ equipment (GPID value: 32)
      • ppp—Point-to-Point Protocol (PPP) (GPID value: 50)

    Configuring BFD for MPLS IPv4 LSPs (NSM Procedure)

    You can configure BFD for LSPs that use either LDP or RSVP as the signaling protocol using the Oam option.

    To configure BFD for LSPs in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols > Mpls.
    4. Select Label Switched Path.
    5. Add or modify settings as specified in Table 14.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 14: Oam Configuration Details

    TaskYour Action

    Enable OAM for RSVP-signaled LSPs.

    1. Click Add new entry next to Label Switched Path.
    2. Click Oam next to label-switched-path.
    3. In the Comment box, enter the comment.
    4. From the Lsp Ping Interval list, select the duration of the LSP ping interval in seconds.

      Range: 30 through 3,600 seconds

    Enable Bidirectional Forwarding Detection (BFD) for all of the MPLS LSPs or for just a specific LSP.

    1. Click Bfd Liveness Detection next to Oam.
    2. In the Comment box, enter the comment.
    3. From the Version list, select the BFD version to be used for detection.
    4. From the Minimum Interval list, select the minimum transmit and receive interval.

      Range: 1 through 255,000 milliseconds

    5. From the Minimum Receive Interval list, select the minimum receive interval.

      Range: 1 through 255,000 milliseconds

    6. From the Multiplier list, select the detection time multiplier.

      Range: 1 through 255

      Default: 3

    7. Select the No Adaptation check box to disable BFD adaptation.

    Specify the threshold for the adaptation of the detection time.

    1. Click Detection Time next to Bfd Liveness Detection.
    2. In the Comment box, enter the comment.
    3. From the Threshold list, select the threshold for detecting the adaptation of the transmit interval.

    Configure route and next-hop properties in the event of a BFD protocol session failure event on an RSVP label-switched path.

    1. Click Failure Action next to Bfd Liveness Detection.
    2. In the Comment box, enter the comment.
    3. Click Teardown next to Failure Action.
    4. Select one of the following:
      • teardown—when a BFD session fails for an RSVP LSP, the associated LSP path is taken down and resignaled immediately.
      • make-before-break—when a BFD session fails for an RSVP LSP, an attempt is made to signal a new LSP path before tearing down the old LSP path.
        1. In the Comment box, enter the comment.
        2. From the Teardown Timeout list, select the time in seconds.

    Specify the minimum transmit interval for failure detection.

    1. Click Transmit Interval next to Failure Action Detection.
    2. In the Comment box, enter the comment.
    3. From the Minimum Interval list, select the minimum interval at which the local router transmits hello packets to the neighbor with which it has established a BFD session.
    4. From the Threshold list, select the threshold for detecting the adaptation of the transmit interval.

      Range: 0 to 4,294,967,295

    Configure MPLS tracing options.

    1. Click Traceoptions next to Oam.
    2. In the Comment box, enter the comment.
    3. Select the No Remote Trace check box to disable remote tracing globally or for a specific tracing operation.
    4. Click File next to Traceoptions.
    5. In the Filename box, enter the name of the file to receive the output of the tracing operation.
    6. In the Size box, enter the maximum size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes (GB).
    7. From the Files list, select the maximum number of trace files.

      Range: 2 through 1000

    8. Select one of the following:
      • world-readable—To enable unrestricted file access.
      • no-world-readable—To restrict file access to owner.
    9. In the Match box, enter the regular expression.
    10. Click Flag next to Traceoptions.
    11. Click Add new entry next to Flag
    12. From the Name list, select the flag.
    13. In the Comment box, enter the comment.

    Configuring the Primary Point-to-Multipoint LSP (NSM Procedure)

    A point-to-multipoint LSP must have a configured primary point-to-multipoint LSP to carry traffic from the ingress router. The configuration of the primary point-to-multipoint LSP is similar to a signaled LSP. You can specify an LSP as either a point-to-multipoint LSP or as a branch LSP of a point-to-multipoint LSP by specifying the point-to-multipoint LSP path name.

    To configure the primary Point-to-Multipoint LSP in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols > Mpls.
    4. Select Label Switched Path.
    5. Add or modify settings as specified in Table 15.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 15: Point-to-Multipoint Configuration Details

    TaskYour Action

    Configure the primary Point-to-Multipoint LSP.

    1. Click Add new entry next to Label Switched Path.
    2. Click P2mp next to label-switched-path.
    3. Select the Enable Feature check box to enable the option.
    4. In the Comment box, enter the comment.
    5. In the Path_name box, enter the name of the point-to-multipoint LSP path that identifies the sequence of nodes that form the point-to-multipoint LSP.

    Configuring Policers for LSPs (NSM Procedure)

    MPLS LSP policing allows you to control the amount of traffic forwarded through a particular LSP. Policing helps to ensure that the amount of traffic forwarded through an LSP never exceeds the requested bandwidth allocation. LSP policing is supported on regular LSPs, LSPs configured with DiffServ-aware traffic engineering, and multiclass LSPs. You can configure multiple policers for each multiclass LSP. For regular LSPs, each LSP policer is applied to all of the traffic traversing the LSP. The policer's bandwidth limitations become effective as soon as the total sum of traffic traversing the LSP exceeds the configured limit.

    To configure policers for LSPs in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols > Mpls.
    4. Select Label Switched Path.
    5. Add or modify settings as specified in Table 16.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 16: Policer Configuration Details

    TaskYour Action

    Specify the policing filter for the LSP.

    1. Click Add new entry next to Label Switched Path.
    2. Click Policing next to label-switched-path.
    3. In the Comment box, enter the comment.
    4. From the Filter list, select the name of the policing filter.
    5. Select the No Auto Policing check box to disable automatic policing on this LSP.

    Configuring Primary Paths for an LSP (NSM Procedure)

    Configuring Primary Paths for an LSP (NSM Procedure)

    You can specify the primary path to use for an LSP using the Primary option. You can configure only one primary path. You can optionally specify preference, CoS, and bandwidth values for the primary path, which override any equivalent values that you configure for the LSP.

    To configure primary paths for an LSP in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols > Mpls.
    4. Select Label Switched Path.
    5. Add or modify settings as specified in Table 17.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 17: Primary Paths Configuration Details

    TaskYour Action

    Configure the primary paths for an LSP.

    1. Click Add new entry next to Label Switched Path.
    2. Click Primary next to label-switched-path.
    3. Click Add new entry next to Primary.
    4. In the Name box, enter the name of a path.
    5. In the Comment box, enter the comment.
    6. From the Class Of Service list, select the CoS value.

      Range: 0 through 7.

      Default: If you do not specify a CoS value, the IP precedence bits from the packet’s IP header are used as the packet’s CoS value.

    7. Select the No Decrement Ttl check box to disable normal time-to-live (TTL) decrementing.
    8. From the Hop Limit list, select the maximum number of hops.

      Range: 2 through 255 (for an LSP); 0 through 255 (for fast reroute)

    9. Select the No Cspf check box to disable constrained-path LSP computation.
     
    1. Select the Admin Down check box to set the A-bit in the Admin Status object.
    2. From the Optimize Timer list, select the length of the optimize timer, in seconds.

      Range: 0 through 65,535 seconds

      Default: 0 seconds (the optimize timer is disabled)

    3. From the Preference list, select the preference to assign to the route.

      Range: 0 to 4,294,967,295

      Default: 5 for static MPLS LSPs, 7 for RSVP MPLS LSPs, 9 for LDP MPLS LSPs

    4. From the Setup Priority list, select the setup priority.

      Range: 0 through 7, where 0 is the highest and 7 is the lowest priority.

     
    1. From the Reservation Priority list, select the reservation priority.

      Range: 0 through 7, where 0 is the highest and 7 is the lowest priority.

    2. Select one of the following:
      • record—Record routes
      • no-record—Does not record routes
    3. Select the Standby check box to have the path remain up at all times to provide instant switchover if connectivity problems occur.
    4. Select the Adaptive check box for RSVP to use shared explicit (SE) reservation styles and assists in smooth transition during rerouting.
    5. From the Select list, select the conditions under which the path is selected to carry traffic. Select one the following:
      • manual—The path is selected for carrying traffic if it is up and stable for at least the revert timer window (potentially before the revert timer has elapsed). Traffic is sent to other working paths if the current path is down or degraded (receiving errors).
      • unconditional—The path is always selected for carrying traffic, even if it is currently down or degraded (receiving errors).

    Configuring Administrative Group (NSM Procedure)

    You can configure an administrative group constraint for each LSP or for each primary or secondary LSP path using the Admin Group option.

    To configure administrative group in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols > Mpls.
    4. Select Label Switched Group.
    5. Add or modify settings as specified in Table 18.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 18: Administrative Group Configuration Details

    TaskYour Action

    Configure administrative group.

    1. Click Add new entry next to Label Switched Path.
    2. Click Primary next to label-switched-path.
    3. Click Add new entry next to Primary.
    4. Click Admin Group next to Primary.
    5. In the Comment box, enter the comment.

    Define the administrative groups to exclude for an LSP or for a path’s primary and secondary paths.

    1. Click Exclude next to Admin Group.
    2. Click Add new entry next to Exclude.
    3. In the New exclude window, enter the names of one or more groups.

    Require the LSP to traverse links that include all of the defined administrative groups.

    1. Click Include All next to Admin Group.
    2. Click Add new entry next to Include All.
    3. In the New include-all window, enter the names of one or more groups.

    Define the administrative groups to include for an LSP or for a path’s primary and secondary paths.

    1. Click Include Any next to Admin Group.
    2. Click Add new entry next to Include Any.
    3. In the New include-any window, enter the names of one or more groups.

    Configuring Class-Type Bandwidth Constraints for Multiclass LSPs (NSM Procedure)

    You configure a multiclass LSP by using the Bandwidth option.

    To configure bandwidth for the multiclass LSP in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols > Mpls.
    4. Select Label Switched Path.
    5. Add or modify settings as specified in Table 19.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 19: Bandwidth Configuration Details

    TaskYour Action

    Configure an LSP as a multiclass LSP.

    1. Click Add new entry next to Label Switched Path.
    2. Click Primary next to label-switched-path.
    3. Click Add new entry next to primary.
    4. Click Bandwidth next to Primary.
    5. In the Comment box, enter the comment.
    6. In the Per Traffic Class Bandwidth box, enter the bandwidth, in bits per second.
    7. In the Ct0 box, enter the bandwidth, for the specified class.
    8. In the Ct1 box, enter the bandwidth, for the specified class.
    9. In the Ct2 box, enter the bandwidth, for the specified class.
    10. In the Ct3 box, enter the bandwidth, for the specified class.

    Configuring BFD for MPLS IPv4 LSPs (NSM Procedure)

    You can configure BFD for LSPs that use either LDP or RSVP as the signaling protocol using the Oam option.

    To configure BFD for LSPs in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols > Mpls.
    4. Select Label Switched Path.
    5. Add or modify settings as specified in Table 20.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 20: Oam Configuration Details

    TaskYour Action

    Enable OAM for RSVP-signaled LSPs.

    1. Click Add new entry next to Label Switched Path.
    2. Click Primary next to label-switched-path.
    3. Click Add new entry next to Primary.
    4. Click Oam next to primary.
    5. In the Comment box, enter the comment.
    6. From the Lsp Ping Interval list, select the duration of the LSP ping interval in seconds.

    Enable Bidirectional Forwarding Detection (BFD) for all of the MPLS LSPs or for just a specific LSP.

    1. Click Bfd Liveness Detection next to Oam.
    2. In the Comment box, enter the comment.
    3. From the Version list, select the BFD version to be used for detection.
    4. From the Minimum Interval list, select the minimum transmit and receive interval.

      Range: 1 through 255,000 milliseconds

    5. From the Minimum Receive Interval list, select the minimum receive interval.

      Range: 1 through 255,000 milliseconds

    6. From the Multiplier list, select the detection time multiplier.

      Range: 1 through 255

      Default: 3

    7. Select the No Adaptation check box to disable BFD adaptation.

    Specify the threshold for the adaptation of the detection time.

    1. Click Detection Time next to Bfd Liveness Detection.
    2. In the Comment box, enter the comment.
    3. From the Threshold list, select the threshold for detecting the adaptation of the transmit interval.

    Configure route and next-hop properties in the event of a BFD protocol session failure event on an RSVP label-switched path.

    1. Click Failure Action next to Bfd Liveness Detection.
    2. In the Comment box, enter the comment.
    3. Click Teardown next to Failure Action.
    4. Select one of the following:
      • teardown—when a BFD session fails for an RSVP LSP, the associated LSP path is taken down and resignaled immediately.
      • make-before-break—when a BFD session fails for an RSVP LSP, an attempt is made to signal a new LSP path before tearing down the old LSP path.
        1. In the Comment box, enter the comment.
        2. From the Teardown Timeout list, select the time in seconds.

    Specify the minimum transmit interval for failure detection.

    1. Click Transmit Interval next to Failure Action.
    2. In the Comment box, enter the comment.
    3. From the Minimum Interval list, select the minimum interval at which the local router transmits hello packets to the neighbor with which it has established a BFD session.

      Range: 1 through 255,000 milliseconds

    4. From the Threshold list, select the threshold for detecting the adaptation of the transmit interval.

      Range: 0 through 4,294,967,295 milliseconds

    Configure MPLS tracing options.

    1. Click Traceoptions next to Oam.
    2. In the Comment box, enter the comment.
    3. Select the No Remote Trace check box to disable remote tracing globally or for a specific tracing operation.
    4. Click File next to Traceoptions.
    5. In the Filename box, enter the name of the file to receive the output of the tracing operation.
    6. In the Size box, enter the maximum size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes (GB).
    7. From the Files list, select the maximum number of trace files.

      Range: 2 through 1000

    8. Select one of the following:
      • world-readable—To enable unrestricted file access.
      • no-world-readable—To restrict file access to owner.
    9. In the Match box, enter the regular expression.
    10. Click Flag next to Traceoptions.
    11. Click Add new entry next to Flag
    12. From the Name list, select the flag.
    13. In the Comment box, enter the comment.

    Configuring Secondary Paths for an LSP (NSM Procedure)

    Configuring Secondary Paths for an LSP (NSM Procedure)

    You can specify one or more secondary paths to use for the LSP. You can configure more than one secondary path. All secondary paths are equal, and the first one that is available is chosen. You can specify secondary paths even if you have not specified any primary paths. Optionally, you can specify preference, CoS, and bandwidth values for the secondary path, which override any equivalent values that you configure for the LSP.

    To configure secondary paths for an LSP in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols > Mpls.
    4. Select Label Switched Path.
    5. Add or modify settings as specified in Table 21.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 21: Secondary Paths Configuration Details

    TaskYour Action

    Configure the secondary paths for an LSP.

    1. Click Add new entry next to Label Switched Path.
    2. Click Secondary next to label-switched-path.
    3. Click Add new entry next to Secondary.
    4. In the Name box, enter the name of a path.
    5. In the Comment box, enter the comment.
    6. From the Class Of Service list, select the CoS value.

      Range: 0 through 7.

      Default: If you do not specify a CoS value, the IP precedence bits from the packet’s IP header are used as the packet’s CoS value.

    7. Select the No Decrement Ttl check box to disable normal time-to-live (TTL) decrementing.
    8. From the Hop Limit list, select the maximum number of hops.

      Range: 2 through 255 (for an LSP); 0 through 255 (for fast reroute)

      Default: 255 (for an LSP); 6 (for fast reroute)

    9. Select the No Cspf check box to disable constrained-path LSP computation.
     
    1. Select the Admin Down check box to set the A-bit in the Admin Status object.
    2. From the Optimize Timer list, select the length of the optimize timer, in seconds.

      Range: 0 through 65,535 seconds

      Default: 0 seconds (the optimize timer is disabled)

    3. From the Preference list, select the preference to assign to the route.

      Range: 0 to 4,294,967,295

      Default: 5 for static MPLS LSPs, 7 for RSVP MPLS LSPs, 9 for LDP MPLS LSPs

    4. From the Setup Priority list, select the setup priority.

      Range: 0 through 7, where 0 is the highest and 7 is the lowest priority.

    5. From the Reservation Priority list, select the reservation priority.

      Range: 0 through 7, where 0 is the highest and 7 is the lowest priority.

    6. Select one of the following:
      • record—Record routes
      • no-record—Does not record routes
    7. Select the Standby check box to have the path remain up at all times to provide instant switchover if connectivity problems occur.
    8. Select the Adaptive check box for RSVP to use shared explicit (SE) reservation styles and assists in smooth transition during rerouting.
    9. From the Select list, select the conditions under which the path is selected to carry traffic. Select one the following:
      • manual—The path is selected for carrying traffic if it is up and stable for at least the revert timer window (potentially before the revert timer has elapsed). Traffic is sent to other working paths if the current path is down or degraded (receiving errors).
      • unconditional—The path is always selected for carrying traffic, even if it is currently down or degraded (receiving errors).

    Configuring Administrative Group (NSM Procedure)

    You can configure an administrative group constraint for each LSP or for each primary or secondary LSP path using the Admin Group option.

    To configure administrative group in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols > Mpls.
    4. Select Label Switched Group.
    5. Add or modify settings as specified in Table 22.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 22: Administrative Group Configuration Details

    TaskYour Action

    Configure administrative group.

    1. Click Add new entry next to Label Switched Path.
    2. Click Secondary next to label-switched-path.
    3. Click Add new entry next to Secondary.
    4. Click Admin Group next to secondary.
    5. In the Comment box, enter the comment.

    Define the administrative groups to exclude for an LSP or for a path’s secondary paths.

    1. Click Exclude next to Admin Group.
    2. Click Add new entry next to Exclude.
    3. In the New exclude window, enter the names of one or more groups.

    Require the LSP to traverse links that include all of the defined administrative groups.

    1. Click Include All next to Admin Group.
    2. Click Add new entry next to Include All.
    3. In the New include-all window, enter the names of one or more groups.

    Define the administrative groups to include for an LSP or for a path’s primary and secondary paths.

    1. Click Include Any next to Admin Group.
    2. Click Add new entry next to Include Any.
    3. In the New include-any window, enter the names of one or more groups.

    Configuring Class-Type Bandwidth Constraints for Multiclass LSPs (NSM Procedure)

    You configure a multiclass LSP by using the Bandwidth option.

    To configure bandwidth for the multiclass LSP in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols > Mpls.
    4. Select Label Switched Path.
    5. Add or modify settings as specified in Table 23.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 23: Bandwidth Configuration Details

    TaskYour Action

    Configure an LSP as a multiclass LSP.

    1. Click Add new entry next to Label Switched Path.
    2. Click Secondary next to label-switched-path.
    3. Click Add new entry next to Secondary.
    4. Click Bandwidth next to secondary.
    5. In the Comment box, enter the comment.
    6. In the Per Traffic Class Bandwidth box, enter the bandwidth, in bits per second.
    7. In the Ct0 box, enter the bandwidth, for the specified class.
    8. In the Ct1 box, enter the bandwidth, for the specified class.
    9. In the Ct2 box, enter the bandwidth, for the specified class.
    10. In the Ct3 box, enter the bandwidth, for the specified class.

    Configuring BFD for MPLS IPv4 LSPs (NSM Procedure)

    You can configure BFD for LSPs that use either LDP or RSVP as the signaling protocol using the Oam option.

    To configure BFD for LSPs in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols > Mpls.
    4. Select Label Switched Path.
    5. Add or modify settings as specified in Table 24.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 24: Oam Configuration Details

    TaskYour Action

    Enable OAM for RSVP-signaled LSPs.

    1. Click Add new entry next to Label Switched Path.
    2. Click Secondary next to label-switched-path.
    3. Click Add new entry next to Secondary.
    4. Click Oam next to secondary.
    5. In the Comment box, enter the comment.
    6. From the Lsp Ping Interval list, select the duration of the LSP ping interval in seconds.

    Enable Bidirectional Forwarding Detection (BFD) for all of the MPLS LSPs or for just a specific LSP.

    1. Click Bfd Liveness Detection next to Oam.
    2. In the Comment box, enter the comment.
    3. From the Version list, select the BFD version to be used for detection.
    4. From the Minimum Interval list, select the minimum transmit and receive interval.

      Range: 1 through 255,000 milliseconds

    5. From the Minimum Receive Interval list, select the minimum receive interval.

      Range: 1 through 255,000 milliseconds

    6. From the Multiplier list, select the detection time multiplier.

      Range: 1 through 255

      Default: 3

    7. Select the No Adaptation check box to disable BFD adaptation.

    Specify the threshold for the adaptation of the detection time.

    1. Click Detection Time next to Bfd Liveness Detection.
    2. In the Comment box, enter the comment.
    3. From the Threshold list, select the threshold for detecting the adaptation of the transmit interval.

    Configure route and next-hop properties in the event of a BFD protocol session failure event on an RSVP label-switched path.

    1. Click Failure Action next to Bfd Liveness Detection.
    2. In the Comment box, enter the comment.
    3. Click Teardown next to Failure Action.
    4. Select one of the following:
      • teardown—when a BFD session fails for an RSVP LSP, the associated LSP path is taken down and resignaled immediately.
      • make-before-break—when a BFD session fails for an RSVP LSP, an attempt is made to signal a new LSP path before tearing down the old LSP path.
        1. In the Comment box, enter the comment.
        2. From the Teardown Timeout list, select the time in seconds.

    Specify the minimum transmit interval for failure detection.

    1. Click Transmit Interval next to Failure Action.
    2. In the Comment box, enter the comment.
    3. From the Minimum Interval list, select the minimum interval at which the local router transmits hello packets to the neighbor with which it has established a BFD session.
    4. From the Threshold list, select the threshold for detecting the adaptation of the transmit interval.

      Range: 0 to 4,294,967,295

    Configure LSP tracing options.

    1. Click Traceoptions next to Oam.
    2. In the Comment box, enter the comment.
    3. Select the No Remote Trace check box to disable remote tracing globally or for a specific tracing operation.
    4. Click File next to Traceoptions.
    5. In the Filename box, enter the name of the file to receive the output of the tracing operation.
    6. In the Size box, enter the maximum size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes (GB).
    7. From the Files list, select the maximum number of trace files.

      Range: 2 through 1000

    8. Select one of the following:
      • world-readable—To enable unrestricted file access.
      • no-world-readable—To restrict file access to owner.
    9. In the Match box, enter the regular expression.
    10. Click Flag next to Traceoptions.
    11. Click Add new entry next to Flag
    12. From the Name list, select the flag.
    13. In the Comment box, enter the comment.

    Configuring the Egress Router Address for LSPs (NSM Procedure)

    When configuring an LSP, you must specify the address of the egress router by using the To option.

    To configure the egress router of a dynamic LSP in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols > Mpls.
    4. Select Label Switched Path.
    5. Add or modify settings as specified in Table 25.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 25: Egress Router Address Configuration Details

    TaskYour Action

    Specify the address of the egress router.

    1. Click Add new entry next to Label Switched Path.
    2. Click To next to label-switched-path.
    3. Select one of the following:
      • To—Specify the egress router of a dynamic LSP and enter the address of the egress router.
      • Template—Configure an LSP template.

    Tracing LSP Packets and Operations (NSM Procedure)

    You can trace LSP packets and operations using the Traceoptions option.

    To trace LSP packets and operations in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols > Mpls.
    4. Select Label Switched Path.
    5. Add or modify settings as specified in Table 26.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 26: LSP Traceoptions Configuration Details

    TaskYour Action

    Trace LSP packets and operations.

    1. Click Add new entry next to Label Switched Path.
    2. Click Traceoptions next to label-switched-path.
    3. In the Comment box, enter the comment.
    4. Click File next to Traceoptions.
    5. In the Comment box, enter the comment.
    6. In the Filename box, enter the name of the file to receive the output.
    7. In the Size box, enter the maximum size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes (GB).
    8. From the Files list, select the maximum number of trace files.

      Range: 2 through 1000

    9. Select one of the following:
      • world-readable—To enable unrestricted file access.
      • no-world-readable—To restrict file access to owner.

    Specify the tracing operation to perform.

    1. Click Flag next to Traceoptions.
    2. Click Add new entry next to Flag.
    3. In the Comment box, enter the comment.
    4. From the Name list, select the tracing operation to be performed.
    5. In the Comment box, enter the comment.

    Configuring System Log Messages and SNMP Traps for LSPs (NSM Procedure)

    Whenever a label switched paths (LSPs) makes a transition from up to down, or down to up, and whenever an LSP switches from one active path to another, the ingress router generates a system log message and sends an SNMP trap.

    To configure system log messages and SNMP traps for LSPs in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols.
    4. Select Mpls.
    5. Add or modify settings as specified in Table 27.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 27: Log Updown Configuration Details

    TaskYour Action

    Log a message or send an SNMP trap whenever an LSP makes a transition from up to down, or vice versa.

    1. Click Log Updown next to Mpls.
    2. In the Comment box, enter the comment.
    3. Select one of the following:
      • syslog—To log a message to the system log file.
      • no-syslog—Does not log a message to the system log file.
    4. Select the Trap Path Down check box to generate SNMP traps whenever an LSP path goes down.
    5. Select the Trap Path Up check box to generate SNMP traps whenever an LSP path goes up.

    Send an SNMP trap.

    1. Click Trap next to Log Updown.
    2. Select one of the following:
      • trap—To send an SNMP trap.
      • no–trap—Does not send an SNMP trap.
        1. In the Comment box, enter the comment.
        2. Select the Mpls Lsp Traps check box to block the MPLS LSP traps defined in the jnx-mpls.mib but to allow the rfc3812.mib traps.
        3. Select the Rfc3812 Traps check box to block the traps defined in the rfc3812.mib but to allow the MPLS LSP traps defined in the jnx-mpls.mib.

    Configuring BFD for MPLS IPv4 LSPs (NSM Procedure)

    You can configure BFD for label switched paths (LSPs) that use either LDP or RSVP as the signaling protocol using the Oam option.

    To configure BFD for LSPs in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols.
    4. Select Mpls.
    5. Add or modify settings as specified in Table 28.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 28: Oam Configuration Details

    TaskYour Action

    Enable OAM for RSVP-signaled LSPs.

    1. Click Oam next to Mpls.
    2. In the Comment box, enter the comment.
    3. From the Lsp Ping Interval list, select the duration of the LSP ping interval in seconds.

    Enable Bidirectional Forwarding Detection (BFD) for all of the MPLS LSPs or for just a specific LSP.

    1. Click Bfd Liveness Detection next to Oam.
    2. In the Comment box, enter the comment.
    3. From the Version list, select the BFD version to be used for detection.
    4. From the Minimum Interval list, select the minimum transmit and receive interval.

      Range: 1 through 255,000 milliseconds

    5. From the Minimum Receive Interval list, select the minimum receive interval.

      Range: 1 through 255,000 milliseconds

    6. From the Multiplier list, select the detection time multiplier.

      Range: 1 through 255

      Default: 3

    7. Select the No Adaptation check box to disable BFD adaptation.

    Specify the threshold for the adaptation of the detection time.

    1. Click Detection Time next to Bfd Liveness Detection.
    2. In the Comment box, enter the comment.
    3. From the Threshold list, select the threshold for detecting the adaptation of the transmit interval.

    Configure route and next-hop properties in the event of a BFD protocol session failure event on an RSVP label-switched path.

    1. Click Failure Action next to Bfd Liveness Detection.
    2. In the Comment box, enter the comment.
    3. Click Teardown next to Failure Action.
    4. Select one of the following:
      • teardown—when a BFD session fails for an RSVP LSP, the associated LSP path is taken down and resignaled immediately.
      • make-before-break—when a BFD session fails for an RSVP LSP, an attempt is made to signal a new LSP path before tearing down the old LSP path.
        1. In the Comment box, enter the comment.
        2. From the Teardown Timeout list, select the time in seconds.

    Specify the minimum transmit interval for failure detection.

    1. Click Transmit Interval next to Failure Action.
    2. In the Comment box, enter the comment.
    3. From the Minimum Interval list, select the minimum interval at which the local router transmits hello packets to the neighbor with which it has established a BFD session.

      Range: 1 to 255,000 milliseconds

    4. From the Threshold list, select the threshold for detecting the adaptation of the transmit interval.

      Range: 0 to 4,294,967,295

    Configure MPLS tracing options.

    1. Click Traceoptions next to Oam.
    2. In the Comment box, enter the comment.
    3. Select the No Remote Trace check box to disable remote tracing globally or for a specific tracing operation.
    4. Click File next to Traceoptions.
    5. In the Filename box, enter the name of the file to receive the output of the tracing operation.
    6. In the Size box, enter the maximum size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes (GB).
    7. From the Files list, select the maximum number of trace files.

      Range: 2 through 1000

    8. Select one of the following:
      • world-readable—To enable unrestricted file access.
      • no-world-readable—To restrict file access to owner.
    9. In the Match box, enter the regular expression.
    10. Click Flag next to Traceoptions.
    11. Click Add new entry next to Flag
    12. From the Name list, select the flag.
    13. In the Comment box, enter the comment.

    Configuring Named Paths (NSM Procedure)

    To configure signaled label switched paths (LSPs), you must first create one or more named paths on the ingress router. For each path, you can specify some or all transit routers in the path, or you can leave it empty. Each pathname can contain up to 32 characters and can include letters, digits, periods, and hyphens. The name must be unique within the ingress router.

    To configure named paths in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols.
    4. Select Mpls.
    5. Add or modify settings as specified in Table 29.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 29: Named Path Configuration Details

    TaskYour Action

    Create a named path.

    1. Click Path next to Mpls.
    2. Click Add new entry next to Path.
    3. In the Name box, enter the hostname.
    4. In the Comment box, enter the comment.

    Specify the sequence of explicit routers that form the path.

    1. Click Path List next to Path.
    2. In the Name box, enter the Name that identifies the sequence of nodes that form an LSP.
    3. In the Comment box, enter the comment.
    4. Select one of the following:
      • loose—indicate that the next address in the path statement is a loose link. This means that the LSP can traverse through other routers before reaching this router.
      • strict—indicate that the LSP must go to the next address specified in the path statement without traversing other nodes.

    Configuring MTU Signaling in RSVPs (NSM Procedure)

    To configure maximum transmission unit (MTU) signaling in RSVP, you need to configure MPLS to allow IP packets to be fragmented before they are encapsulated in MPLS. You also need to configure MTU signaling in RSVP. For troubleshooting purposes, you can configure MTU signaling alone without enabling packet fragmentation.

    To configure MTU signaling in RSVP in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols.
    4. Select Mpls.
    5. Add or modify settings as specified in Table 30.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 30: Path MTU Configuration Details

    TaskYour Action

    Configure MTU options for MPLS paths, including packet fragmentation and MTU signaling.

    1. Click Path Mtu next to Mpls.
    2. Select the Enable Feature check box to enable the option.
    3. In the Comment box, enter the comment.
    4. Select the Allow Fragmentation check box to allow IP packets to be fragmented before they are encapsulated in MPLS.

    Configure MTU signaling in RSVP.

    1. Click Rsvp next to Path Mtu.
    2. Select the Enable Feature check box to enable the option.
    3. In the Comment box, enter the comment.
    4. Select the Mtu Signaling check box to enable MTU signaling in RSVP.

    Configuring static LSPs on the Ingress Router (NSM Procedure)

    You can configure static LSPs on the ingress router using the Static Path option.

    To configure static path in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols.
    4. Select Mpls.
    5. Add or modify settings as specified in Table 31.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 31: Static Path Configuration Details

    TaskYour Action

    Configure static path.

    1. Click Static Path next to Mpls.
    2. Click Add new entry next to Static Path.
    3. From the Name list, select the routing table.
    4. In the Comment box, enter the comment.

    Configure static LSPs on the ingress router.

    1. Click Path next to static-path.
    2. Click Add new entry next to Path.
    3. In the Name box, enter the name of the routing table.
    4. In the Comment box, enter the comment.
    5. In the Next Hop box, enter the IP address of the next hop to the destination.
     
    1. From the Push list, select the out-label value.

      Range: 0 through 1,048,575

    2. From the Double Push Bottom list, select the bottom-label value.

      Range: Labels 0 through 999,999 are for internal use. Labels 1,000,000 through 1,048,575 are unassigned by the Junos OS and are available for static LSPs.

    3. From the Double Push Top list, select the top-label value.

      Range: Labels 0 through 999,999 are for internal use. Labels 1,000,000 through 1,048,575 are unassigned by the Junos OS and are available for static LSPs.

    4. From the Triple Push Bottom list, select the bottom-label value.

      Range: 0 through 1,048,575. Labels 0 through 999,999 are for internal use. Labels 1,000,000 through 1,048,575 are unassigned by the Junos OS and are available for static LSPs.

    5. From the Triple Push Middle list, select the middle-label value.

      Range: 0 through 1,048,575. Labels 0 through 999,999 are for internal use. Labels 1,000,000 through 1,048,575 are unassigned by the Junos OS and are available for static LSPs.

    6. From the Triple Push Top list, select the top-label value.

      Range: 0 through 1,048,575. Labels 0 through 999,999 are for internal use. Labels 1,000,000 through 1,048,575 are unassigned by the Junos OS and are available for static LSPs.

    7. From the Preference list, select the preference to be assigned to the route.
    8. From the Class Of Service list, select the CoS value.

      Range: 0 through 7

      Default: If you do not specify a CoS value, the IP precedence bits from the packet’s IP header are used as the packet’s CoS value.

    Configuring MPLS Statistics (NSM Procedure)

    You can enable MPLS statistics collection and reporting using the Statistics option.

    To configure static path in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols.
    4. Select Mpls.
    5. Add or modify settings as specified in Table 32.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 32: MPLS Statistics Configuration Details

    TaskYour Action

    Enable MPLS statistics collection and reporting.

    1. Click Statistics next to Mpls.
    2. In the Comment box, enter the comment.
    3. From the Interval list, select the interval at which to periodically collect statistics.

      Range: 1 through 65,535

      Default: none

    4. Select the Auto Bandwidth check box to collect statistics related to automatic bandwidth.

    Configure the file.

    1. Click File next to Statistics.
    2. In the Comment box, enter the comment.
    3. In the Filename box, enter the name of the file to receive the output.
    4. In the Size box, enter the maximum size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes (GB).
    5. From the Files list, select the maximum number of trace files.

      Range: 2 through 1000

    6. Select one of the following:
      • world-readable—To enable unrestricted file access.
      • no-world-readable—To restrict file access to owner.

    Tracing MPLS Packets and Operations (NSM Procedure)

    You can trace MPLS packets and operations using the Traceoptions option.

    To trace MPLS packets and operations in NSM:

    1. In the NSM navigation tree, select Device Manager > Devices.
    2. Click the Device Tree tab, and then double-click the device to select it.
    3. Click the Configuration tab. In the configuration tree, expand Protocols.
    4. Select Mpls.
    5. Add or modify settings as specified in Table 33.
    6. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 33: Traceoptions Configuration Details

    TaskYour Action

    Trace MPLS packets and operations.

    1. Click Traceoptions next to Mpls.
    2. In the Comment box, enter the comment.
    3. Click File next to Traceoptions.
    4. In the Comment box, enter the comment.
    5. In the Filename box, enter the name of the file to receive the output.
    6. In the Size box, enter the maximum size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes (GB).
    7. From the Files list, select the maximum number of trace files.

      Range: 2 through 1000

    8. Select one of the following:
      • world-readable—To enable unrestricted file access.
      • no-world-readable—To restrict file access to owner.

    Specify the tracing operation to perform.

    1. Click Flag next to Traceoptions.
    2. Click Add new entry next to Flag.
    3. In the Comment box, enter the comment.
    4. From the Name list, select the tracing operation to be performed.
    5. In the Comment box, enter the comment.

    Published: 2013-01-02