Interface Label-Map Commands

label-map

Syntax

[no] label-map in-label

Context

config>router>mpls>interface

Description

This command is used on either transit or egress LSP routers when a static LSP is defined. The static LSP on the ingress router is initiated using the config>router>mpls>static-lsp lsp-name command. The in-label is associated with a pop action or a swap action, but not both. If both actions are specified, the last action specified takes effect.

The no form of this command deletes the static LSP configuration associated with the in-label.

Parameters

in-label

specifies the incoming MPLS label on which to match

Values

32 to 1023

pop

Syntax

[no] pop

Context

config>router>mpls>if>label-map

Description

This command specifies that the incoming label must be popped (removed). No label stacking is supported for a static LSP. The service header follows the top label. Once the label is popped, the packet is forwarded based on the service header.

The no form of this command removes the pop action for the in-label.

Default

n/a

swap

Syntax

swap out-label nexthop ip-address

no swap

Context

config>router>mpls>if>label-map

Description

This command swaps the incoming label and specifies the outgoing label and next-hop IP address on an LSR for a static LSP.

The no form of this command removes the swap action associated with the in-label.

Default

n/a

Parameters

out-label

specifies the label value to be swapped with the in-label. Label values 16 through 1048575 are defined as follows:

Label values 16 through 31 are 7705 SAR reserved

Label values 32 through 1023 are available for static assignment

Label values 1024 through 2047 are reserved for future use

Label values 2048 through 18431 are statically assigned for services

Label values 28672 through 131071 are dynamically assigned for both MPLS and services

Label values 131072 through 1048575 are reserved for future use

Values

16 to 1048575

ip-address

specifies the IP address to forward to. If an ARP entry for the next hop exists, then the static LSP will be marked operational. If an ARP entry does not exist, software will set the operational status of the static LSP to down and continue to ARP for the configured next-hop at a fixed interval.