Cisco ASA 5505 - Manual (Page 271)

6-29
Cisco ASA 5500 Series Configuration Guide using the CLI
Chapter 6 Starting Interface Configuration (ASA 5510 and Higher)
Starting Interface Configuration (ASA 5510 and Higher)
What to Do Next
Optional Tasks:
• Customize the EtherChannel interface. See the “Customizing the EtherChannel” section on
page 6-29 .
• Configure VLAN subinterfaces. See the “Configuring VLAN Subinterfaces and 802.1Q Trunking”
section on page 6-30 .
Required Tasks:
• For multiple context mode, assign interfaces to contexts and automatically assign unique MAC
addresses to context interfaces. See the
“Configuring Multiple Contexts” section on page 5-14 .
• For single context mode, complete the interface configuration. See the Chapter 8, “Completing
Interface Configuration (Routed Mode),” or Chapter 9, “Completing Interface Configuration
(Transparent Mode).”
Customizing the EtherChannel
This section describes how to set the maximum number of interfaces in the EtherChannel, the minimum
number of operating interfaces for the EtherChannel to be active, the load balancing algorithm, and other
optional parameters.
Detailed Steps
Command Purpose
Step 1 interface port-channel channel_id
Example:
hostname(config)# interface port-channel 1
Specifies the port-channel interface. This interface was created
automatically when you added an interface to the channel group.
If you have not yet added an interface, then this command creates
the port-channel interface.
Note You need to add at least one member interface to the
port-channel interface before you can configure logical
parameters for it such as a name.
Step 2 lacp max-bundle number
Example:
hostname(config-if)# lacp max-bundle 6
Specifies the maximum number of active interfaces allowed in the
channel group, between 1 and 8. The default is 8.
Step 3 port-channel min-bundle number
Example:
hostname(config-if)# port-channel
min-bundle 2
Specifies the minimum number of active interfaces required for
the port-channel interface to become active, between 1 and 8. The
default is 1. If the active interfaces in the channel group falls
below this value, then the port-channel interface goes down, and
could trigger a device-level failover.