Supported Platforms
Configuring MPLS LSPs for GMPLS
To enable the proper GMPLS switching parameters, configure the label-switched path (LSP) attributes that are appropriate for your network connection. The default value for switching-type is psc-1, which is also appropriate for standard MPLS.
To configure the LSP attributes, include the lsp-attributes statement at the [edit protocols mpls label-switched-path lsp-name] hierarchy level:
If you include the no-cspf statement in the label-switched path configuration, you must also configure primary and secondary paths, or the configuration cannot be committed.
The following sections describe how to configure each of the LSP attributes for a GMPLS LSP:
Configuring the Encoding Type
You need to specify the encoding type of the payload carried by the LSP. It can be any of the following:
- ethernet—Ethernet
- packet—Packet
- pdh—Plesiochronous digital hierarchy (PDH)
- sonet-sdh—SONET/SDH
The default value is packet.
To configure the encoding type, include the encoding-type statement at the [edit protocols mpls label-switched-path lsp-name lsp-attributes] hierarchy level:
Configuring the GPID
You need to specify the type of payload carried by the LSP. The payload is the type of packet underneath the MPLS label. The payload is specified by the generalized payload identifier (GPID).
You can specify the GPID with any of the following values:
- hdlc—High-Level Data Link Control (HDLC)
- ethernet—Ethernet
- ipv4—IP version 4 (default)
- pos-scrambling-crc-16—For interoperability with other vendors’ equipment
- pos-no-scrambling-crc-16—For interoperability with other vendors’ equipment
- pos-scrambling-crc-32—For interoperability with other vendors’ equipment
- pos-no-scrambling-crc-32—For interoperability with other vendors’ equipment
- ppp—Point-to-Point Protocol (PPP)
To configure the GPID, include the gpid statement at the [edit protocols mpls label-switched-path lsp-name lsp-attributes] hierarchy level:
Configuring the Signal Bandwidth Type
The signal bandwidth type is the encoding used for path computation and admission control. To configure the signal bandwidth type, include the signal-bandwidth statement at the [edit protocols mpls label-switched-path lsp-name lsp-attributes] hierarchy level:
Configuring GMPLS Bidirectional LSPs
Because MPLS and GMPLS use the same configuration hierarchy for LSPs, it is helpful to know which LSP attributes control LSP functionality. Standard MPLS packet-switched LSPs are unidirectional, whereas GMPLS nonpacket LSPs are bidirectional.
If you use the default packet-switching type of psc-1, your LSP becomes unidirectional. To enable a GMPLS bidirectional LSP, you must select a non-packet-switching type option, such as lambda, fiber, or ethernet. Include the switching-type statement at the [edit protocols mpls label-switched-path lsp-name lsp-attributes] hierarchy level:
Allowing Nonpacket GMPLS LSPs to Establish Paths Through Routers Running the Junos OS
By setting the A-bit in the Admin Status object. you can enable nonpacket GMPLS LSPs to establish paths through routers that run Junos. When an ingress router sends an RSVP PATH message with the Admin Status A-bit set, an external device (not a router running the Junos OS) can either perform a Layer 1 path setup test or help bring up an optical cross-connect.
When set, the A-bit in the Admin Status object indicates the administrative down status for a GMPLS LSP. This feature is used specifically by nonpacket GMPLS LSPs. It does not affect control path setup or data forwarding for packet LSPs.
Junos does not distinguish between the control path setup and data path setup. Other nodes along the network path use RSVP PATH signaling using the A-bit in a meaningful way.
To configure the Admin Status object for a GMPLS LSP, include the admin-down statement:
You can include this statement at the following hierarchy levels:
- [edit protocols mpls label-switched-path lsp-name]
- [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name]
