Cisco ASA Series Cli Configuration Manual page 426

Starting Interface Configuration (ASA 5510 and Higher)
!
interface Management0/1
channel-group 3 mode active
no shutdown
!
interface port-channel 1
interface port-channel 2
interface port-channel 3
Step 6
Change the interface allocation per context to use the new EtherChannel or redundant interfaces. See the
"Configuring a Security Context" section on page
For example, to take advantage of existing cabling, you would continue to use the formerly in-use
interfaces in their old roles as part of the inside and outside redundant interfaces:
context customerA
allocate-interface port-channel1 int1
allocate-interface port-channel2 int2
allocate-interface port-channel3 mgmt
context customerB
allocate-interface port-channel1
allocate-interface port-channel2
allocate-interface port-channel3
Note
Step 7
For contexts that do not use mapped names, change the context configuration to use the new
EtherChannel or redundant interface ID. (Contexts that use mapped interface names do not require any
alteration.)
For example:
CustomerB Context
interface port-channel1
nameif outside
security-level 0
ip address 10.20.15.5 255.255.255.0
!
interface port-channel2
nameif inside
security-level 100
ip address 192.168.6.78 255.255.255.0
!
interface port-channel3
nameif mgmt
security-level 100
ip address 10.8.1.8 255.255.255.0
management-only
Cisco ASA Series CLI Configuration Guide
1-22
You might want to take this opportunity to assign mapped names to interfaces if you have not
done so already. For example, the configuration for customerA does not need to be altered at all;
it just needs to be reapplied on the ASA. The customerB configuration, however, needs to have
all of the interface IDs changed; if you assign mapped names for customerB, you still have to
change the interface IDs in the context configuration, but mapped names might help future
interface changes.
Chapter 1 Starting Interface Configuration (ASA 5510 and Higher)
1-20.