The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the Cisco NX-OS Multiprotocol Label Switching commands that begin with P.
To configure a Message Digest (MD5) password for Label Distribution Protocol (LDP) sessions with neighbors whose LDP router IDs are permitted by a specified prefix list, use the password option command. To return to the default setting, use the no form of this command.
password option number for prefix-list key-chain keychain-name
Order in which the prefix lists is evaluated when the device determines a neighbor password. The valid range is from 1 to 32767. |
|
|
|
---|---|
This example shows how to configure an MD5 password for LDP sessions with neighbors whose LDP router IDs are permitted by a specified prefix list:
|
|
---|---|
Configures the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP). |
To configure a Label Distribution Protocol (LDP) password when establishing a session between LDP peers, use the password required command. To return to the default setting, use the no form of this command.
password required [for prefix-list]
(Optional) Specifies a prefix list when establishing a session between a peers. |
|
|
|
---|---|
This example shows how to configure an LDP password when establishing a session between LDP peers:
|
|
---|---|
Configures the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP). |
To configure a path option for a Multiprotocol Label Switching (MPLS) traffic engineering (TE) tunnel, use the path-option command. To restore the system to its default condition, use the no form of this command.
path-option [protect] preference-number {dynamic | explicit {identifier id | name name} [verbatim]} [lockdown] [bandwidth kbps] [attributes listname]
TE interface configuration mode
|
|
---|---|
You can configure multiple path options for a single tunnel. For example, there can be several explicit path options and a dynamic option for one tunnel. The path setup preference is for lower (not higher) numbers, so option 1 is preferred.
If you specify the dynamic keyword, the software checks both the physical bandwidth of the interface and the available TE bandwidth to be sure that the requested amount of bandwidth does not exceed the physical bandwidth of any link. To oversubscribe links, you must specify the explicit keyword. If you use the explicit keyword, the software checks only how much bandwidth is available on the link for TE; the amount of bandwidth that you configure is not limited to how much physical bandwidth is available on the link.
This example shows how to configure the tunnel to use a named TE explicit path and if that path is not available, then to fall back to a path dynamically calculated from the TE topology database:
|
|
---|---|
To configure the metric type to use if a metric type is not explicitly configured for a Multiprotocol Label Switching (MPLS) traffic engineering (TE) tunnel, use the path-selection metric command. To restore the system to its default condition, use the no form of this command.
path-selection metric {igp | te}
|
|
---|---|
If you configure the TE path selection metric type, you should configure the MPLS TE administrative weight on each interface for which TE is enabled.
Use this command to specify the metric type to be used for traffic engineering (TE) tunnels for which the tunnel path-selection metric command has not been specified.
The metric type to be used for path calculation for a given tunnel is determined as follows:
•If you entered the tunnel path-selection metric command to specify a metric type for the tunnel, use that metric type.
•If you entered the TE configuration mode path-selection metric was entered to specify a metric type, use that metric type.
•If you did not do any of the above tasks, use the default (te) metric.
This example shows how to configure the metric type to use if a metric type is not explicitly configured for an MPLS TE tunnel:
|
|
---|---|
To configure the metric type to be used if a metric type is not explicity configured for an Multiprotocol Label Switching (MPLS) traffic engineering (TE) tunnel, use the path-selection metric command. To restore the system to its default condition, use the no form of this command.
path-selection metric {igp | te}
TE interface configuration mode
|
|
---|---|
If you configure the TE path selection metric type, you should configure the MPLS TE administrative weight on each interface for which TE is enabled.
Use this command to specify the metric type to be used for traffic engineering (TE) tunnels for which the tunnel path-selection metric command has not been specified.
The metric type to be used for path calculation for a given tunnel is determined as follows:
•If you entered the tunnel path-selection metric command was entered to specify a metric type for the tunnel, use that metric type.
•If you entered the TE configuration mode path-selection metric was entered to specify a metric type, use that metric type.
•If you did not do any of the above tasks, use the default (te) metric.
This example shows how to configure the metric type to use if a metric type is not explicitly configured for an MPLS TE tunnel:
|
|
---|---|
To allow overloaded nodes in Constrained Shortest Path First (CSPF), use the path-selection overload allow command. To return to the default setting, use the no form of this command.
path-selection overload allow {head [middle [tail]] | middle [tail] | tail}
no path-selection overload allow
|
|
---|---|
This example shows how to specify that an overloaded node can still be used as a tunnel head in the traffic engineering (TE) constrained Shortest Path First (CSPF):
|
|
---|---|
Configures the Multiprotocol Label Switching (MPLS) Traffic Engineering Protocol (MPLS-TE). |
To test the Multiprotocol Label Switching (MPLS) label switched path (LSP) reachability, use the ping mpls command.
ping mpls {ipv4 destination-address/destination-mask-length | pseudowire ipv4-address vc-id | traffic-eng tunnel-te interface number}
Specifies the target virtual channel (VC) as an IPv4 address and VC ID. |
|
|
|
---|---|
This example shows how to specify the test MPLS LSP reachability:
|
|
---|---|
Configures the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP). |
To target virtual circuit (VC) specified as an IPv4 address and VC ID, use the ping mpls pseudowire command.
ping mpls pseudowire ipv4-address vc-id
|
|
---|---|
This example shows how to target a VC specified as an IPv4 address and VC ID:
|
|
---|---|
To create a policy map to enforce a committed data rate of 256000 bits per second, use the police command. To return to the default setting, use the no form of this command.
police [cir] {x [bps | kbps | mbps | gbps] | percent x-percent} [[bc] bc [bytes | kbytes | mbytes | ms | us]] [pir y [bps | kbps | mbps | gbps] | percent y-percent] [[be] be [bytes | kbytes | mbytes | ms | us]] [conform conform-action [exceed exceed-action [violate violate-action]]]
no police [cir] {x [bps | kbps | mbps | gbps] | percent x-percent} [[bc] bc [bytes | kbytes | mbytes | ms | us]] [pir y [bps | kbps | mbps | gbps] | percent y-percent] [[be] be [bytes | kbytes | mbytes | ms | us]] [conform conform-action [exceed exceed-action [violate violate-action]]]
|
|
---|---|
This example shows how to create a policy map to enforce a committed data rate of 256000 bps. If the data rate is in conformance, the router sets the EXP field of the outer (topmost) label of the MPLS header. If the data rate is exceeded, the router drops packets:
|
|
---|---|
Configures the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP). |
To configure a policy map, use the policy-map command. To return to the default setting, use the no form of this command.
policy-map [type qos] policy-map-name
no policy-map [type qos] policy-map-name
Policy map name. The maximum size is 40 alphanumeric characters. |
|
|
---|---|
This example shows how to configure a policy map:
|
|
---|---|
Configures the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP). |
To enter interface port profile configuration mode and configure a pseudowire port profile, use the port-profile type pseudowire command.
port-profile type pseudowire profile-name
Name of the profile. The string can be any alphanumeric string up to 80 characters. |
|
|
---|---|
This example shows how to specify an address to exclude while configuring an explicit path:
|
|
---|---|
Enters interface pseudowire configuration mode and configures a static pseudowire logical interface. |
|
To configure the label switched path (LSP) priority, use the priority command. To restore the system to its default condition, use the no form of this command.
priority setup-priority [hold-priority]
By default, the setup priority is 7. The value of hold priority is the same as the value of setup priority.
LSP attribute configuration mode
|
|
---|---|
Use the setup-priority argument when signaling an LSP to determine which existing LSPs can be preempted. The range is from 0 to 7, where a lower number indicates a higher priority. Therefore, an LSP with a setup priority of 0 can preempt any LSP with a nonzero priority.
Use the hold-priority argument LSP to determine if an LSP should be preempted by other LSPs that are being signaled. The range is from 0 to 7, where a lower number indicates a higher priority.
The two priorities enables the signaling of an LSP with a low setup priority (so that the LSP does not preempt other LSPs during the setup) and a high hold priority (so that the LSP is not preempted after it is established). The setup priority and hold priority are typically configured to be equal; the setup priority cannot be higher (numerically smaller) than the hold priority.
This example shows how to configure the LSP priority:
|
|
---|---|
Configures the Multiprotocol Label Switching (MPLS) Traffic Engineering Protocol (MPLS-TE). |
To configure the label switched path (LSP) priority, use the priority command. To restore the system to its default condition, use the no form of this command.
priority setup-priority [hold-priority]
By default, the setup priority is 7. The value of hold priority is the same as the value of setup priority.
TE interface configuration mode
|
|
---|---|
Use the setup-priority argument when signaling an LSP to determine which existing LSPs can be preempted. The range is from 0 to 7, where a lower number indicates a higher priority. Therefore, an LSP with a setup priority of 0 can preempt any LSP with a nonzero priority.
Use the hold-priority argument LSP to determine if an LSP should be preempted by other LSPs that are being signaled. The range is from 0 to 7, where a lower number indicates a higher priority.
The two priorities enable the signaling of an LSP with a low setup priority (so that the LSP does not preempt other LSPs during the setup) and a high hold priority (so that the LSP is not preempted after it is established). The setup priority and hold priority are typically configured to be equal; the setup priority cannot be higher (numerically smaller) than the hold priority.
This example shows how to configure the LSP priority:
|
|
---|---|
To enable a Multiprotocol Label Switching (MPLS) traffic engineering (TE) tunnel to request a backup tunnel to protect against a link or node failure, use the fast-reroute command. To restore the system to its default condition, use the no form of this command.
protection fast-reroute [bw-protect]
(Optional) Sets the bandwidth protection desired bit so that backup bandwidth protection is requested at each hop that the LSP traverses. |
LSP attribute configuration mode
|
|
---|---|
This example shows how to enable failure protection on the LSP:
|
|
---|---|
Configures the Multiprotocol Label Switching (MPLS) Traffic Engineering Protocol (MPLS-TE). |