Juniper JUNOS 10.1 - RELEASE NOTES REV 4 User Manual

[JUNOS XML API Operational Reference]
MPLS Applications
■ Static LSPs at the ingress router—You can now configure a named static LSP
at the ingress router. This feature allows you to configure multiple static LSPs
between two specific routers. It is not necessary to configure unique names for
static versus dynamic LSPs (a static LSP could have the same name as a dynamic
LSP configured on the same router). This feature also allows you to configure a
single-hop static LSP by specifying either an explicit null label or no label.
To configure a static LSP on an ingress router, include the ingress statement at
the [edit protocols mpls static-label-switched-path static-lsp-name] hierarchy level.
You must also configure the to and next-hop statements at the [edit protocols mpls
static-label-switched-path static-lsp-name] hierarchy level. You can optionally
configure the push statement. If you configure the push statement, you must
specify a non-reserved label in the range of 0 through 1,048,575.
To display information about ingress static LSPs, issue the show mpls lsp static
ingress command. To display routing table entries corresponding to ingress static
LSPs, issue the show route table inet.3 command or the show route next-hop
next-hop-ip-address static-label-switched-path static-lsp-name command.
[MPLS, Routing Protocols and Policies Command Reference]
■ Static LSPs at the transit router—You can now configure a named static LSP
on a transit router. To configure a transit static LSP, include the transit statement
at the [edit protocols mpls static-label-switched-path path-name] hierarchy level
and include the next-hop statement at the [edit protocols mpls
static-label-switched-path static-lsp-name] hierarchy level. You must also configure
either the pop or the swap statement at the [edit protocols mpls
static-label-switched-path static-lsp-name transit] hierarchy level. If you configure
the swap statement, you must specify a non-reserved label in the range of 0
through 1,048,575.
The transit static LSP is added to the mpls.0 routing table. You should configure
each static LSP using a unique name and at least a unique incoming label on the
router. Each transit static LSP can have one or more incoming labels configured.
If a transit LSP has more than one incoming label, each would effectively operate
as an independent LSP, meaning you could configure all of the related LSP
attributes for each incoming label. The range of incoming labels available is
limited to the standard static LSP range of labels (1,000,000 through 1,048,575).
To verify that a static LSP has been added to the routing table, issue the show
route table mpls.0 command.
[MPLS]
■ Bypass static LSPs—You can now configure a named bypass static LSP for ingress
and transit static LSPs, to be used if the primary LSP fails. To configure a bypass
static LSP, include the bypass statement at the [edit protocols mpls
static-label-switched-path path-name] hierarchy level. You must also configure the
to and next-hop statements at the [edit protocols mpls static-label-switched-path
static-lsp-name bypass] hierarchy level. You can also configure link and node
protection for static LSPs. If you configure both link and node protection for the
static LSP and the primary link fails, the node protection feature is preferred.
New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers ■ 21
New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers

Juniper JUNOS 10.1 - RELEASE NOTES REV 4 Specifications

General

Brand	Juniper
Model	JUNOS 10.1 - RELEASE NOTES REV 4
Category	Software
Language	English