The default scheme is defaulted to Source and Destination IP address. Next, we've modified the load balancing scheme. This value defaults to 8, which is the maximum number of interfaces that can be in one EtherChannel. 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.
#ETHERCHANNEL ASA ASDM HOW TO#
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. For container instances, you can share data interfaces only in this case can multiple logical devices communicate over the backplane.Some may say that bandwidth is king. All traffic must exit the chassis on one interface and return on another interface to reach another logical device. Lo gic al dev ice s can not for m a ser vic e cha in wi th eac h oth er, and the y can not com mun ica te ove r the bac kpl ane with each other. Y ou can then conf igur e the sec urit y pol icy wit hin the appl icat ion operating system. When you deploy the logical device, the supervisor downloads an application image of your choi ce and est abli shes a def ault conf igur ati on. A logical device lets you run one application instance and also one optional decorator application to form a service chain. To use the FXOS CLI, see the FXOS CLI configuration guide. Y ou conf igur e har dwar e int erf ace set tin gs, sma rt lic ens ing (fo r the ASA ), and oth er bas ic ope rat ing parameters on the supervisor using the Firepower Chassis Manager. The on-the-box Firepower Chassis Manager provides simple, GUI-based management cap abil iti es. The Fir epow er 4100 runs its own oper ati ng sys tem on the supe rvi sor cal led the Fir epow er eXt ensi ble Ope rat ing System (FXOS).