Cisco Systems ASA 5510 Network Router User Manual


  Open as PDF
of 2086
 
12-18
Cisco ASA 5500 Series Configuration Guide using ASDM
Chapter 12 Starting Interface Configuration (ASA 5510 and Higher)
Starting Interface Configuration (ASA 5510 and Higher)
no nameif
no security-level
no ip address
!
interface port-channel 1
nameif outside
security-level 0
ip address 10.86.194.225 255.255.255.0
!
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 12-29.
Step 8 Save the entire new configuration, including the altered interface section.
Step 9 Re-zip the backup folder with the altered configuration.
Step 10 Choose Tools > Restore Configurations, and choose the altered configuration zip file. Be sure to
replace the existing running configuration; do not merge them. See the “Restoring Configurations”
section on page 80-17 for more information.
Step 11 Reenable failover by choosing Configuration > Device Management > High Availability > Failover,
and checking the Enable failover check box. Click Apply, and click No when prompted if you want to
configure basic failover settings.
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.
Changing your configuration offline lets you use the same interface names for your new logical
interfaces, so you do not need to touch the feature configurations that refer to interface names. You
only need to change the interface configuration.
Clearing the running system configuration and immediately applying a new configuration will
minimize the downtime of your interfaces. You will not be waiting to configure the interfaces in real
time.
Step 1 Connect to the ASA, and change to the system; if you are using failover, connect to the active ASA.