Cisco ASA 5505 User Manual
Page 260
6-18
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)
!
interface port-channel 2
nameif inside
security-level 100
ip address 192.168.1.3 255.255.255.0
!
interface port-channel 3
nameif mgmt
security-level 100
ip address 10.1.1.5 255.255.255.0
Note
Other optional EtherChannel parameters can be configured after you import the new
configuration. See the
“Configuring an EtherChannel” section on page 6-27
Step 8
At the ASA CLI prompt, perform the following steps depending on your connection (console or remote).
•
Console connection:
a.
Copy the entire new configuration to the clipboard, including the altered interface section.
b.
Clear the running configuration by entering:
hostname(config)# clear configure all
Traffic through the ASA stops at this point.
c.
Paste in the new configuration at the prompt.
Traffic through the ASA resumes.
•
Remote connection:
a.
Save the new configuration to a TFTP or FTP server, so you can copy it to the startup
configuration on the ASA. For example, you can run a TFTP or FTP server on your PC.
b.
Clear the startup configuration by entering:
hostname(config)# write erase
c.
Copy the new configuration to the startup configuration by entering:
hostname(config)# copy url startup-config
See the
“Downloading a File to a Specific Location” section on page 81-3
d.
Reload the ASA using the reload command. Do not save the running configuration.
Step 9
Reenable failover by entering the failover command.
Detailed Steps (Multiple Mode)
We recommend that you update your system and context configurations offline as text files, and reimport
them for the following reasons:
•
Because you cannot add an allocated interface as a member of a redundant or EtherChannel
interface, you must deallocate the interface from any contexts. When you deallocate the interface,
any context command that referred to that interface is deleted. Because commands that refer to
interfaces are widespread throughout the configuration and affect multiple features, removing an
allocation from an in-use interface at the CLI or in ASDM would cause significant damage to your
configuration, not to mention significant downtime while you reconfigure all your features around
a new interface.