
config mpls rsvp-te add ero
ExtremeWare Software 7.0.0 Command Reference Guide
1399
router ID or a configured loopback IP address, the router interface which the packet is received is
ignored.
The LSR path order is optionally specified using the
order
keyword. The
order number
parameter is
an integer value from 1 to 65535. IP prefixes with a lower number are sequenced before IP prefixes with
a higher number. You can specify multiple paths and assign them an order number. The order number
determines the path that the LSP follows. Thus, the LSP path follows the configured path of the IP
prefix with the order value from low to high. If the
order
keyword is not specified, the number value
for the LSR defaults to a value 100 higher than the current highest number value.
If the list of IP prefixes, added to the path, does not reflect an actual path through the network
topology, the path message is returned with an error from a downstream LSR and the LSP is not
established.
The order of a configured subobject can not be changed. The ERO subobject must be deleted and
re-added using a different order. If a subobject is added to or deleted from the ERO while the
associated LSP is established, the path is torn down and is resignaled using the new ERO.
Duplicate ERO subobjects are not allowed. Defining an ERO for the path is optional. If you do not
configure an ERO, the path is signaled along the best-routed path and the ERO is not included in the
path message. When the last subobject in the ERO of the path message is reached and the egress IP
node of the path has not been reached, the remaining path to the egress node is signaled along the
best-routed path. Specification of an ERO could lead to undesirable routed paths, so you should be
careful when terminating the ERO routed-path definition prior to the configured path egress node.
Example
The following command adds a strict ERO subobject of 192.18.32.5 to the specified path:
config mpls rsvp-te path paththroughdenver add ero ipaddress 192.18.32.5
History
This command was first available in an ExtremeWare IP Technology Services Release based on
v6.1.8b12.
This command was subsequently incorporated into ExtremeWare 7.0.0.
Platform Availability
This command is available on the BlackDiamond switch only.
Summary of Contents for ExtremeWare 7.0.0
Page 88: ...88 ExtremeWare Software 7 0 0 Command Reference Guide Commands for Accessing the Switch ...
Page 276: ...276 ExtremeWare Software 7 0 0 Command Reference Guide FDB Commands ...
Page 324: ...324 ExtremeWare Software 7 0 0 Command Reference Guide QoS Commands ...
Page 342: ...342 ExtremeWare Software 7 0 0 Command Reference Guide NAT Commands ...
Page 502: ...502 ExtremeWare Software 7 0 0 Command Reference Guide SLB Commands ...
Page 680: ...680 ExtremeWare Software 7 0 0 Command Reference Guide Security Commands ...
Page 734: ...734 ExtremeWare Software 7 0 0 Command Reference Guide STP Commands ...
Page 772: ...772 ExtremeWare Software 7 0 0 Command Reference Guide ESRP Commands ...
Page 1226: ...1226 ExtremeWare Software 7 0 0 Command Reference Guide IPX Commands ...
Page 1242: ...1242 ExtremeWare Software 7 0 0 Command Reference Guide ARM Commands ...
Page 1320: ...1320 ExtremeWare Software 7 0 0 Command Reference Guide PoS Commands ...
Page 1430: ...1430 ExtremeWare Software 7 0 0 Command Reference Guide MPLS Commands ...