in-path bundle
Adds a bundle of interfaces for link aggregation protocol support.
Syntax
[no] in-path bundle <bundle-name> interfaces <interface>
Parameters
<bundle-name> | Bundle name. |
interfaces <interface> | Specifies a comma-separated list of interfaces (for example, inpath0_0,inpath0_1). |
Usage
This command is used to provide support to interoperate with other networking devices that communicate using link aggregation protocols, such as Etherchannel. Link aggregation compatibility allows easier integration into networks with preexisting link aggregation in place. The SteelHead does not terminate the link aggregation protocol and it is transparent to the link aggregation devices.
All interfaces in a bundle must have the same settings including the WAN and LAN interfaces:
• Speed/duplex
• MTU
• VLAN ID
• IP subnet (each interface must have a unique IP address on the same subnet)
• Default gateway
• User defined routing table entries
Once a bundle is configured, the corresponding settings cannot be changed until the bundle is removed. Each bundle can have as many interfaces as you want and you can configure multiple bundles per SteelHead.
Link state propagation must be turned on to propagate the link state. Use the in-path lsp enable command to turn on link state propagation.
In a failover scenario, a link state alarm is triggered that shows which in-path interface went down and which in-path interface from the bundle is the backup. The failover logic chooses the next available link from the bundle and moves all the flows from the failed link to the backup link.
You must restart the optimization service for your changes to take effect. The no command option removes the bundle of interfaces.
Example
amnesiac (config) # in-path bundle bundle1 interfaces inpath0_0,inpath0_1
amnesiac (config) # service restart
Product
SteelHead CX, SteelHead EX, SteelHead-v, SteelHead-c
Related Commands