34-51
Cisco ME 3800X and 3600X Switch Software Configuration Guide
OL-23400-01
Chapter 34 Configuring MPLS, MPLS VPN, MPLS OAM, and EoMPLS
Configuring MPLS OAM and IP SLAs MPLS
Configuring the IP SLAs LSP Health Monitor
You can configure the MPLS LSP Health Monitor to discover BGP VPN next hops and automatically
create IP SLAs LSP ping or traceroute operations. You can specify an LSP ping or traceroute operation
and VRF tables to be used. By default the LSP Health Monitor discovers all BGP next- hop neighbors
by using all VRFs associated with the source provider edge router.
When you configure an LSP Health Monitor operation, you enter auto IP SLAs MPLS parameters
configuration mode where you can configure the optional parameters shown in the Steps 4 through 17.
See the IP SLAs-LSP Health Monitor feature module for more information about the parameters.
You must configure the MPLS LSP Health Monitor on a provider-edge router. The IP SLAs measurement
statistics are stored on the source PE router.
Beginning in privileged EXEC mode, follow these steps to configure the operation parameters, reaction
conditions, and scheduling options for a MPLS LSP monitor ping or traceroute.
Command Purpose
Step 1
configure terminal Enter global configuration mode.
Step 2
auto ip sla mpls-lsp-monitor operation-number Specify an LSP Health Monitor operation number and enter auto
IP SLA MPLS configuration mode. The operation number range
is from 1 to 2147483647.
Step 3
type {echo | pathEcho} {ipsla-vrf-all | vrf
vpn-name}
Configure the parameters of the LSP Health Monitor by
selecting the operation and entering auto IP SLAs MPLS
parameters configuration mode.
• echo—Select an LSP monitor ping operation.
• pathEcho—Select an LSP monitor traceroute operation.
• ipsla-vrf-all—Configure IP SLAs MPSL LSP monitor for
all VPNs.
• vrf vpn-name—Configure the IP SLAs LSP monitor for the
specified VPN.
Step 4
access-list access-list-number (Optional) Specify an access list to apply to LSP Health Monitor
operation.
Step 5
delete-scan-factor factor (Optional) Specify the number of times the LSP Health Monitor
checks the scan queue before automatically deleting IP SLAs
operations for BGP next-hop neighbors that are no longer valid.
The factor range is 0 to 2147483647. The default scan factor
is 1.
Note You must use the scan-interval command with this
command.
Step 6
exp exp-bits (Optional) Specify the experimental field value in the echo
request packet header. The range is 0 to 7; the default value is 0.
Step 7
force-explicit-null (Optional) Add an explicit null label to all echo request packets
of an IP SLAs operation.
Step 8
lsp-selector ip-address (Optional) Specify the local host IP address used to select the IP
SLAs operation LSP. The default is 127.0.0.1.
To Next Page
Loading...
Need help?
General