Supported Platforms
Configuring Static Label Switched Paths for MPLS (CLI Procedure)
Configuring static label-switched paths (LSPs) for MPLS is similar to configuring static routes on individual switches. As with static routes, there is no error reporting, liveliness detection, or statistics reporting.
To configure static LSPs, configure the ingress switch and each provider switch along the path up to and including the egress switch.
For the ingress switch, configure which packets to tag (based on the packet’s destination IP address), configure the next switch in the LSP, and the tag to apply to the packet. Manually assigned labels can have values from 0 through 1,048,575. Optionally, you can apply preference, class-of-service (CoS) values, node protection, and link protection to the packets.
For the transit switches in the path, configure the next switch in the path and the tag to apply to the packet. Manually assigned labels can have values from 1,000,000 through 1,048,575. Optionally, you can apply node protection and link protection to the packets.
For the egress switch, you generally just remove the label and continue forwarding the packet to the IP destination. However, if the previous switch removed the label, the egress switch examines the packet’s IP header and forwards the packet toward its IP destination.
Before you configure an LSP, you must configure the basic components for an MPLS network:
- Configure two PE switches. See Configuring MPLS on Provider Edge Switches Using Circuit Cross-Connect (CLI Procedure).
- Configure one or more provider switches. See Configuring MPLS on Provider Switches (CLI Procedure).
This topic describes how to configure an ingress PE switch, one or more provider switches, and an egress PE switch for static LSP:
Configuring the Ingress PE Switch
To configure the ingress PE switch:
- Configure an IP address for the core interfaces:
[edit]
user@switch# set interfaces interface-name unit logical-unit-number family inet address address
user@switch# set interfaces interface-name unit logical-unit-number family inet address address - Configure the name and the traffic rate associated with
the LSP:
[edit]
user@switch# set protocols mpls static-label-switched-path lsp-name ingress bandwidth rate - Configure the next hop switch for the LSP:
[edit]
user@switch# set protocols mpls static-label-switched-path lsp-name ingress next-hop address-of-next-hop - Enable link protection on the specified static LSP:
[edit]
user@switch# set protocols mpls static-label-switched-path lsp-name ingress link-protection bypass-name name - Specify the address of the egress switch for the LSP:
[edit]
user@switch# set protocols mpls static-label-switched-path path1 ingress to address-of-egress-switch - Configure the new label that you want to add to the top
of the label stack:
[edit]
user@switch# set protocols mpls static-label-switched-path path1 ingress push out-label - Optionally, configure the next hop address and the egress
router address that you want to bypass, for the static LSP:
[edit]
user@switch# set protocols mpls static-label-switched-path lsp-name by bypass next-hop address-of-next-hop
user@switch# set protocols mpls static-label-switched-path lsp-name by bypass to address-of-the-egress-switch
user@switch# set protocols mpls static-label-switched-path lsp-name bypass push out-label
Configuring the Provider and the Egress PE Switch
To configure a static LSP for MPLS on the provider and egress provider edge switch:
- Configure a transit static LSP:
[edit]
user@switch# set protocols mpls static-label-switched-path path1 transit incoming-label - Configure the next hop switch for the LSP:
[edit]
user@switch# set protocols mpls static-label-switched-path lsp-name transit incoming-label next-hop address-of-next-hop - Only for provider switches, remove the label at the top
of the label stack and replace it with the specified label:
[edit]
user@switch# set protocols mpls static-label-switched-path lsp-name transit incoming-label swap out-label - Only for the egress provider edge switch, remove the label
at the top of the label stack:
Note: If there is another label in the stack, that label becomes the label at the top of the label stack. Otherwise, the packet is forwarded as a native protocol packet (typically, as an IP packet).
[edit]
user@switch# set protocols mpls static-label-switched-path lsp-name transit incoming-label pop
