Specifically related to the EtherChannel is the number of Minimum Active Members that can be defined before the interface goes down, as well as the Maximum Number of Active Members. In this case we have statically assigned the IP address.įigure C shows the advanced options. At the bottom of the configuration page you must determine how the IP address of the interface is to be configured. This is because they are already configured. You'll notice that the GigabitEthernet0/0 as well as GigabitEthernet0/1 interfaces are not present. You select them and use the add button to move them into the group. Additionally you must add available physical interfaces as group members. In Figure B, you can see the need to provide a Port Channel ID, an interface name, and a security level. The next step is to provide the parameters for the EtherChannel. This presents an option to create an EtherChannel Interface. In the Figure A, I've navigated to Configuration>Device Settings>Interfaces and I've selected the Add button. Use ASDM and configure via a GUI interface.
Lets look at how to configure EtherChannels on the ASA. If one interface goes down the traffic still travels over the other interface. The ASA load balances traffic over the two interfaces in the bundle. What about the high availability? That comes with the bundle. There's the bandwidth increase that some may be looking for. So a 1-GBps interface can be EtherChanneled with another to become a 2-GBps bundle. Essentially what you are accomplishing is a bundle relationship between two interfaces that are looked at as one in the ASA. The solution is Etherchannel and it became available on the ASA in version 8.4. In this post I'll show you how to get more bandwidth with your Cisco ASA, as well as an added bonus of high availability. This is true in many cases, especially with higher end video applications becoming more prevalent in network environments.
0 kommentar(er)
