Configuring MPLS

The following example configures a static and dynamic label block.

--{ + candidate shared default }--[  ]--
# info with-context system mpls
    system {
        mpls {
            label-ranges {
                static s1 {
                    start-label 10001
                    end-label 11000
                }
                dynamic d1 {
                    start-label 11001
                    end-label 12000
                }
            }
        }
    }

--{ + candidate shared default }--[  ]--
# info from state with-context system mpls label-ranges
    system {
        mpls {
            label-ranges {
                static s1 {
                    shared true
                    start-label 10001
                    end-label 11000
                    allocated-labels 0
                    free-labels 1000
                    status ready
                }
                dynamic d1 {
                    start-label 11001
                    end-label 12000
                    allocated-labels 0
                    free-labels 1000
                    status ready
                }
            }
        }
    }

The following example shows the default network-instance configured for an ingress LER, specifying the label to push to MPLS-encapsulated packets. In this example, multiple next-hops (ECMP) are specified in a next-hop group.

--{ + candidate shared default }--[  ]--
# info with-context network-instance default next-hop-groups group srva_tora_ipv4
    network-instance default {
        next-hop-groups {
            group srva_tora_ipv4 {
                nexthop 0 {
                    ip-address 192.13.1.3
                    resolve false
                    pushed-mpls-label-stack [
                        544334
                    ]
                }
                nexthop 2 {
                    ip-address 192.13.1.3
                    resolve false
                    pushed-mpls-label-stack [
                        205679
                    ]
                }
            }
        }
    }

Specify a static label block for MPLS

The following example shows the default network-instance configured as a transit LSR in the label switched path.

This example configures MPLS to use a static label block named s2. The static label block is configured with a start-label value and an end-label value. See Configuring label blocks for an example of a static label block configuration.

The example configures incoming MPLS transit traffic with label 1000 to use the next-hops in next-hop-group nhop_group_1 for label-swap operations.

--{ + candidate shared default }--[  ]--
# info with-context network-instance default mpls
    network-instance default {
        mpls {
            static-label-block s2
            static-entry 1000 preference 100 {
                operation swap
                next-hop-group nhop_group_1
            }
        }
    }

Specify next-hop for MPLS

The following example specifies the MPLS next-hop for nhop_group_1. Only one MPLS next-hop is supported per next-hop-group. In this example, the label for outgoing traffic to MPLS next-hop 192.35.1.5 is swapped to 1001.

--{ + candidate shared default }--[  ]--
# info with-context network-instance default next-hop-groups group nhop_group_1
    network-instance default {
        next-hop-groups {
            group nhop_group_1 {
                nexthop 0 {
                    ip-address 192.35.1.5
                    resolve false
                    pushed-mpls-label-stack [
                        1001
                    ]
                }
            }
        }
    }

The following example shows the default network-instance configured to perform PHP for the LSR. In this example, the setting for pushed-mpls-label-stack is IMPLICIT_NULL, which causes the label for outgoing traffic to MPLS next-hop 192.35.1.1 to be popped.

--{ + candidate shared default }--[  ]--
# info with-context network-instance default next-hop-groups group nhop_group_2
    network-instance default {
        next-hop-groups {
            group nhop_group_2 {
                nexthop 0 {
                    ip-address 192.35.1.1
                    resolve false
                    pushed-mpls-label-stack [
                        IMPLICIT_NULL
                    ]
                }
            }
        }
    }

Define label block for static LSP entries

The following example specifies a static label block to use for the static LSPs. The mpls static-label-block command references a static label block configured under system mpls label-ranges.

--{ candidate shared default }--[  ]--
# info with-context network-instance default mpls static-label-block
    network-instance default {
        mpls {
            static-label-block static-egress-lsp-block-1
        }
    }

Configure static LSP entries

The following example configures a static LSP entry for unicast traffic.

--{ candidate shared default }--[  ]--
# info with-context network-instance default mpls lsps
    network-instance default {
        mpls {
            lsps {
                static-lsp static-lsp-1 {
                    payload-type unicast
                    egress {
                        incoming-label 17001
                        network-instance ip-vrf-1
                        pipe-mode true
                        next-hop 10 {
                            ip-address 10.20.20.1
                        }
                    }
                }
            }
        }
    }

The static egress LSP parameters are as follows:

• payload-type — specifies the payload type: unicast (default) or multicast.
• egress incoming-label — specifies a valid and available MPLS label value from the configured static label block or the default label block.
• egress network-instance — specifies a locally configured IP-VRF network instance. Each next-hop IP address is resolved to a routed subinterface in the specified network instance. Because different IP VRFs can have overlapping IP addresses, ip-address on its own is insufficient to determine the egress IP interface.
• egress pipe-mode — controls the QoS classification and marking of packets matching the MPLS ILM entry. When set to true, packets matching the static LSP ILM entry are classified and marked based on the traffic-class/EXP value of the label-stack entry that is popped. No copying of these fields to the IP header is performed. A setting of false (implying uniform mode) is not supported.
• egress next-hop index — specifies an index value for the next hop. A maximum of one next hop is supported.
• egress next-hop ip-address — specifies an IPv4 or IPv6 address. IPv4 addresses can be global or link-local, while IPv6 addresses can be global-unicast or a link-local address with zone (for example: fe80::1234%ethernet-1/1.1). A pop-and-forward operation is performed to the specified IP address. That is, the top label stack entry is removed and the packet is forwarded out the selected next hop with its remaining MPLS label stack entries (if any), its IP headers, and its payload.

Configure static egress LSP traffic-class classification

The following example configures an MPLS traffic class policy mapping a traffic class to a specific forwarding class and drop probability and binds that policy to all static egress LSPs.

--{ candidate shared default }--[  ]--
# info with-context qos classifiers static-mpls-lsp-egress MPLS_POLICY
qos {
    classifiers {
        static-mpls-lsp-egress MPLS_POLICY
        mpls-traffic-class-policy MPLS_POLICY {
            traffic-class 2 {
                forwarding-class AF3
                drop-probability low
            }
        }
    }
}

Disable MPLS reception on a customer-facing subinterface

The following example disables ingress MPLS packet reception on subinterface ethernet-1/1.1 in the default network-instance.

--{ + candidate shared default }--[  ]--
# info with-context network-instance default interface ethernet-1/1.1 mpls
    network-instance default {
        interface ethernet-1/1.1 {
            mpls {
                forward-received-packets false
            }
        }
    }

Enable MPLS reception on a routed subinterface

The following example enables ingress MPLS packet reception on subinterface ethernet-1/2.1 in the default network-instance.

--{ + candidate shared default }--[  ]--
# info with-context network-instance default interface ethernet-1/2.1 mpls
    network-instance default {
        interface ethernet-1/2.1 {
            mpls {
                forward-received-packets true
            }
        }
    }

Display MPLS discard counters for a subinterface

When MPLS reception is disabled on a routed subinterface, Ethernet-MPLS packets received on that subinterface are dropped. Use the info from state with-context command to display the subinterface and the MPLS discard counters.

--{ + candidate shared default }--[  ]--
# info from state with-context interface ethernet-1/1 subinterface 1 statistics in-discarded-packets
    interface ethernet-1/1 {
        subinterface 1 {
            statistics {
                in-discarded-packets 12
            }
        }
    }
--{ + candidate shared default }--[  ]--
# info from state with-context interface ethernet-1/1 subinterface 1 mpls statistics in-discarded-packets
    interface ethernet-1/1 {
        subinterface 1 {
            mpls {
                statistics {
                    in-discarded-packets 0
                }
            }
        }
    }

Configure a system-wide default MPLS MTU value

--{ + candidate shared default }--[  ]--
# info with-context system mtu
    system {
        mtu {
            default-mpls-mtu 4096
        }
    }

Configure an MPLS MTU for a routed subinterface

--{ + candidate shared default }--[  ]--
# info with-context interface ethernet-1/1 subinterface 1
    interface ethernet-1/1 {
        subinterface 1 {
            type routed
            admin-state enable
            mpls-mtu 4096
            ipv4 {
                admin-state enable
                address 192.168.11.1/30 {
                }
            }
            ipv6 {
                admin-state enable
                address 2001:1::192:168:11:1/126 {
                }
            }
        }
    }

Display the system-wide default MPLS MTU value

--{ + candidate shared default }--[  ]--
# info from state with-context system mtu default-mpls-mtu
    system {
        mtu {
            default-mpls-mtu 4096
        }
    }

Display the MPLS MTU for a subinterface

--{ + candidate shared default }--[  ]--
# info from state with-context interface ethernet-1/1 subinterface 1 mpls-mtu
    interface ethernet-1/1 {
        subinterface 1 {
            mpls-mtu 4096
        }
    }

Enable IPv4 explicit null label for next-hop group

The following example enables IPv4 explicit null labels for next-hop group null-group.

--{ candidate shared default }--[  ]--
# info network-instance default next-hop-groups group null-group
    network-instance default {
        next-hop-groups {
            group null-group {
                nexthop 1 {
                    resolve false
                    pushed-mpls-label-stack [
                        IPV4_EXPLICIT_NULL
                    ]
                }
            }
        }
    }

Enable the label-only hash option

The following example enables the label-only hash option on an LSR.

--{ candidate shared default }--[  ]--
# system load-balancing lsr-profile label-stack

Enable the LSR label hash option with Ethernet or IP headers (with L4 and TEID)

The following example enables the LSR label option with Ethernet or IP headers (with L4 and TEID) on an LSR.

--{ candidate shared default }--[  ]--
# system load-balancing lsr-profile label-eth-or-ip-l4-teid