In-label, Next-hop, Out-label – Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) User Manual
Page 178
![background image](/manuals/361646/178/background.png)
154
Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide
53-1003031-02
Static transit LSP
1
In-label
Use the in-label command to specify the label that will be received in the packets and used to
identify the static transit LSP in the router. That in turn decides who the next hop will be (based on
the “next-hop” configuration). No in-interface is configured as we use the global label-space. It
would be an error to configure the same in-label for multiple LSPs, or specify a value outside the
static range.
Brocade(config-mpls-static-transit-lsp-t1)# in-label 400
Syntax: [no] in-label value
The value parameter represents the label received in the MPLS header in the packets from the
upstream.
Acceptable ranges for this parameter include the Static label min-value and Static label max-value.
The value should not exceed the static label range configured on the router.
Next-hop
The next-hop command represents the next-hop address based on which the out-interface and
next-hop interface address will be obtained using longest match. You must provide a correct
next-hop address or the LSP will not come up at this node.
The next-hop should be reachable by an Ethernet, VE or LAG interface. MPLS or GRE tunnels as
next-hop out-interfaces are not supported. It would be an error to specify IP addresses that are
generic local host or multicast.
Brocade(config-mpls-static-transit-lsp-t1)# next-hop 192.1.1.1
Syntax: [no] next-hop address
The address parameter represents the next-hop address. It must be a valid IPv4 address. This can
be a directly connected next-hop interface address or a non-directly connected interface address or
loopback address.
Out-label
Use the out-label command to specify the label to be swapped for packets coming in with the
in-label configured. If not, it is assumed to be a penultimate hop router and the incoming label will
be popped before the packet is forwarded with no MPLS header to the downstream.
Brocade(config-mpls-static-transit-lsp-t1)# out-label 1048575
Syntax: [no] out-label value
The value parameter is the label value swapped onto the packets sent to the downstream router. If
not configured, PHP is assumed and the implicit-null label(3) is assumed resulting in a pop.
The acceptable range for the value parameter is the valid MPLS label range (0-1048575 or 220-1),
0 (explicit null) and 3 (implicit null). The configured value parameter must be a value the next hop
router knows and is within its valid label range.