Extreme Networks ExtremeWare 7.7, Command Reference Manual

Page: 2536 / 2620

2536 ExtremeWare 7.7 Command Reference Guide
MPLS Commands—BlackDiamond Switch Only
hold-priority
range is also 0 to 7 and is set equal to the
setup-priority
by default. ExtremeWare
does not support LSP preemption.
The
retry-timeout
keyword specifies the maximum number of seconds the switch allows for LSP
setup. If the LSP cannot be established within
retry-timeout
seconds, the LSP is signaled again. The
default value for
retry-timeout
is 30 seconds with a configurable range of 5 to 600 seconds. The
hop-count
parameter limits the number of LSRs the path can traverse, including the ingress and egress
router. The default
hop-count
value is 255 with a configurable range of two to 255.
After an LSP has established, the egress LSR may be optionally pinged to determine end-to-end path
connectivity. If a ping response is not received within [2 *
ping-interval
– 1] seconds, the LSP is
considered unavailable. The
ping-interval
keyword specifies how frequently an ICMP echo request is
transmitted to the egress LSR IP address on the established LSP. The default
ping-interval
is zero,
which indicates no end-to-end LSP health checking is performed. You can set the
ping-interval
value
to any interval between 0 and 60 seconds.
The route
metric
is used to determine if an established RSVP-TE LSP will actually be used to send
data. Whenever the configured metric is less than, or equal, to the calculated IGP metric, the LSP is
used for sending routed IP traffic. In this case, the LSP is also used to send TLS data when the TLS
tunnel is configured by specifying the tunnel LSP endpoint IP address. Traffic is distributed across up to
four equal-cost LSPs. The valid metric values range from 1 to 65535. Specifying the
igp-tracking
keyword forces the route metric to track the underlying IGP metrics. If no IGP metric exists for the LSP
(for example, the LSP traverses a RIP network), the metric is ignored. Tracking IGP metrics is the
default behavior.
The
record
keyword is used to enable hop-by-hop path recording. The enabled keyword causes the
record route object (RRO) to be inserted into the path message. The RRO is returned in the reserve
message and contains a list of IPv4 subobjects that describe the RSVP-TE path. Path recording by
default is disabled. When disabled, no RRO is inserted into the path message.
The mtu keyword optionally specifies the MTU value transport payload packet (customer packet). The
mtu value is exchanged with vpls configured peer nodes. All VPLS peer nodes must be configured with
the same mtu value. If the mtu values do not match, VC-LSPs cannot be established between VPLS
peers. By default the VPLS mtu is set to 1500. The configurable mtu range is 1492 through 9216.
Changing the mtu setting will cause established VC-LSPs to terminate. VPLS payload packets may be
dropped if the VPLS MTU setting is greater than the MPLS MTU setting for the VC-LSP interface. The
vplsping command may be used to verify end-to-end path connectivity for specific payload packet
sizes.
Example
The following command adds a profile with the configured attributes:
• Reserved bandwidth signaled is 100 Mbps.
• Tunnel LSP setup priority is 1.
• Tunnel LSP hold priority is 0.
• Route recording is enabled.
configure mpls rsvp-te add profile customer1 bandwidth 100m setup-priority 1
hold-priority 0 record enabled