index int64 0 4.08k | text stringlengths 34 4.9k ⌀ | url stringclasses 38
values |
|---|---|---|
223 | Platform Description
Releases
Feature Name
We introduced Smart Software Licensing for the ASA on the Firepower
9300.
We introduced the following commands: feature strong-encryption,
feature mobile-sp, feature context
Cisco Smart Software Licensing for the 9.4(1.150)
ASA on the Firepower 9300
Smart Software Licensing le... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
224 | CHAPTER 5
Logical Devices for the Firepower 4100/9300
TheFirepower 4100/9300 is a flexible security platform on which you can install one or more logical devices.
This chapter describes basic interface configuration and how to add a standalone or High Availability logical
device using the chassis manager. To add a clus... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
225 | Note The chassis management interface does not support jumbo frames.
Interface Types
Physical interfaces and EtherChannel (port-channel) interfaces can be one of the following types:
• Data—Use for regular data. Data interfaces cannot be shared between logical devices, and logical devices
cannot communicate over the ba... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
226 | Table 3: Interface Type Support
Cluster:
Subinterface
Cluster
(EtherChannel
only)
Data-Sharing: Mgmt Eventing
Subinterface
Data: Data-Sharing
Subinterface
Application Data
Standalone Yes — — — Yes Yes — —
Native
Instance
Threat
Defense
Standalone Yes Yes Yes Yes Yes Yes — —
Container
Instance
Yes — — — Yes Yes Yes —
(E... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
227 | Independent Interface States in the Chassis and in the Application
You can administratively enable and disable interfaces in both the chassis and in the application. For an
interface to be operational, the interface must be enabled in both operating systems. Because the interface
state is controlled independently, you ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
228 | and container instances on the other module. For example, you can install a native instance on module
1 and module 2, but container instances on module 3.
• Clustering—All security modules in the cluster, whether it is intra-chassis or inter-chassis, must be the
same type. You can have different quantities of installed... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
229 | port-channel interface uses a unique MAC address from a pool; interface membership does not affect
the MAC address.
General Guidelines and Limitations
Firewall Mode
You can set the firewall mode to routed or transparent in the bootstrap configuration for the threat defense
and ASA.
High Availability
• Configure high av... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
230 | If you remove an interface inFXOS(for example, if you remove a network module, remove an EtherChannel,
or reassign an interface to an EtherChannel), then the ASA configuration retains the original commands so
that you can make any necessary adjustments; removing an interface from the configuration can have wide
effects... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
231 | Firepower /eth-uplink/fabric/interface # set debounce-time 5000
Step 4 (Optional) Set the interface type.
set port-type {data | mgmt | cluster}
Example:
Firepower /eth-uplink/fabric/interface # set port-type mgmt
The data keyword is the default type. Do not choose the cluster keyword; by default, the cluster control li... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
232 | Firepower /eth-uplink/fabric/interface #
Add an EtherChannel (Port Channel)
An EtherChannel (also known as a port channel) can include up to 16 member interfaces of the same media
type and capacity, and must be set to the same speed and duplex. The media type can be either RJ-45 or SFP;
SFPs of different types (copper ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
233 | Procedure
Step 1 Enter interface mode:
scope eth-uplink
scope fabric a
Step 2 Create the port-channel:
create port-channel id
enable
Step 3 Assign member interfaces:
create member-port interface_id
You can add up to 16 member interfaces of the same media type and capacity. The member interfaces must
be set to the same ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
234 | Step 6 (Optional) Set the required duplex for members of the port-channel.
set duplex {fullduplex | halfduplex}
If you add a member interface that is configured with the specified duplex, it will not successfully join the
port channel. The default is fullduplex.
Example:
Firepower /eth-uplink/fabric/port-channel* # set... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
235 | Add a Standalone ASA
Standalone logical devices work either alone or in a High Availability pair. On the Firepower 9300 with
multiple security modules, you can deploy either a cluster or standalone devices. The cluster must use all
modules, so you cannot mix and match a 2-module cluster plus a single standalone device,... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
236 | Firepower /ssa # show app
Name Version Author Supported Deploy Types CSP Type Is Default
App
---------- --------------- ---------- ---------------------- -----------
--------------
asa 9.9.1 cisco Native Application No
asa 9.10.1 cisco Native Application Yes
ftd 6.2.3 cisco Native Application Yes
b) Set the scope to th... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
237 | Firepower /ssa* #
Example:
Firepower /ssa # scope slot 1
Firepower /ssa/slot # enter app-instance asa ASA1
Firepower /ssa/slot/app-instance* # set startup-version 9.10.1
Firepower /ssa/slot/app-instance* # exit
Firepower /ssa/slot* # exit
Firepower /ssa* #
Step 3 Create the logical device.
enter logical-device device_n... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
238 | Firepower /ssa/logical-device* # create mgmt-bootstrap asa
Firepower /ssa/logical-device/mgmt-bootstrap* #
b) Specify the firewall mode, routed or transparent.
create bootstrap-key FIREWALL_MODE
set value {routed | transparent}
exit
In routed mode, the device is considered to be a router hop in the network. Each interf... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
239 | exit
Example:
Firepower /ssa/logical-device/mgmt-bootstrap* # create ipv4 1 default
Firepower /ssa/logical-device/mgmt-bootstrap/ipv4* # set ip 10.10.10.34 mask 255.255.255.0
Firepower /ssa/logical-device/mgmt-bootstrap/ipv4* # set gateway 10.10.10.1
Firepower /ssa/logical-device/mgmt-bootstrap/ipv4* # exit
Firepower /... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
240 | Container Default-Small Not Applicable None
Step 7 See the ASA configuration guide to start configuring your security policy.
Example
Firepower# scope ssa
Firepower /ssa # scope slot 1
Firepower /ssa/slot # enter app-instance asa MyDevice1
Firepower /ssa/slot/app-instance* # set startup-version 9.10.1
Firepower /ssa/sl... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
241 | These interfaces exchange high availability traffic between the 2 chassis. We recommend that you use a 10
GB data interface for a combined failover and state link. If you have available interfaces, you can use separate
failover and state links; the state link requires the most bandwidth. You cannot use the management-t... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
242 | Procedure
Step 1 Enter security services mode:
Firepower# scope ssa
Step 2 Edit the logical device:
Firepower /ssa # scope logical-device device_name
Step 3 Unallocate an interface from the logical device:
Firepower /ssa/logical-device # delete external-port-link name
Enter the show external-port-link command to view i... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
243 | Firepower-module1>
Step 2 Connect to the application console.
connect asa name
To view the instance names, enter the command without a name.
Example:
Firepower-module1> connect asa asa1
Connecting to asa(asa1) console... hit Ctrl + A + D to return to bootCLI
[...]
asa>
Step 3 Exit the application console to the FXOS mo... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
244 | History for Logical Devices
Feature Version Details
We introduced the Firepower 4112.
Note Requires FXOS 2.8.1.
ASA for the Firepower 9.14(1)
4112
We introduced the SM-56 security module.
Note Requires FXOS 2.6.1.157.
Firepower 9300 SM-56 9.12.2
support
We introduced the Firepower 4115, 4125, and 4145.
Note Requires FX... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
245 | Feature Version Details
With FXOS 1.1.4, the ASA supports inter-chassis clustering on the Firepower 4100 series.
We did not modify any commands.
Support for the Firepower 9.6(1)
4100 series
With FXOS 1.1.3, you can now enable inter-chassis, and by extension inter-site clustering. You can
include up to 6 modules in up t... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
246 | CHAPTER 6
Transparent or Routed Firewall Mode
This chapter describes how to set the firewall mode to routed or transparent, as well as how the firewall works
in each firewall mode.
You can set the firewall mode independently for each context in multiple context mode.
• About the Firewall Mode, on page 187
• Default Set... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
247 | Layer 2 connectivity is achieved by using a "bridge group" where you group together the inside and outside
interfaces for a network, and the ASA uses bridging techniques to pass traffic between the interfaces. Each
bridge group includes a Bridge Virtual Interface (BVI) to which you assign an IP address on the network.
... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
248 | About Bridge Groups
A bridge group is a group of interfaces that the ASA bridges instead of routes. Bridge groups are supported
in both transparent and routed firewall mode. Like any other firewall interfaces, access control between
interfaces is controlled, and all of the usual firewall checks are in place.
Bridge Vir... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
249 | Figure 24: Transparent Firewall Network with Two Bridge Groups
Bridge Groups in Routed Firewall Mode
Bridge group traffic can be routed to other bridge groups or routed interfaces. You can choose to isolate bridge
group traffic by not assigning a name to the BVI interface for the bridge group. If you name the BVI, then... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
250 | Figure 25: Routed Firewall Network with an Inside Bridge Group and an Outside Routed Interface
Passing Traffic Not Allowed in Routed Mode
In routed mode, some types of traffic cannot pass through the ASA even if you allow it in an access rule. The
bridge group, however, can allow almost any traffic through using either... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
251 | • IPv6 neighbor discovery and router solicitation packets can be passed using access rules.
• Broadcast and multicast traffic can be passed using access rules.
Allowed MAC Addresses
The following destination MAC addresses are allowed through the bridge group if allowed by your access
policy (see Allowing Layer 3 Traffi... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
252 | • SIP
• Skinny (SCCP)
• SQL*Net
• SunRPC
• TFTP
• Traffic at least one hop away for which the ASA performs NAT—Configure a static route on the ASA
for traffic destined for the remote network. You also need a static route on the upstream router for traffic
destined for the mapped addresses to be sent to the ASA.
This ro... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
253 | Unsupported Features for Bridge Groups in Transparent Mode
The following table lists the features are not supported in bridge groups in transparent mode.
Table 4: Unsupported Features in Transparent Mode
Feature Description
Dynamic DNS —
DHCPv6 stateless server Only the DHCPv4 server issupported on bridge group member ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
254 | Feature Description
The routed firewall can act as a DHCPv4 server, but it does not support
DHCP relay on BVIs or bridge group member interfaces.
DHCP relay
You can, however, add static routes for BVIs. You can also allow dynamic
routing protocolsthrough the ASA using an accessrule. Non-bridge group
interfaces support ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
255 | • The ASA does not support traffic on secondary networks; only traffic on the same network as the BVI
IP address is supported.
• An IP address for the BVI is required for each bridge group for to-the-device and from-the-device
management traffic, as well as for data traffic to pass through the ASA. For IPv4 traffic, sp... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
256 | SeeSet the ASA Image, ASDM, andStartupConfiguration, on page 1266 forinformation about downloading
text files.
Set the Firewall Mode
This section describes how to change the firewall mode.
We recommend that you set the firewall mode before you perform any other configuration because changing
the firewall mode clears th... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
257 | Examples for Firewall Mode
This section includes examples of how traffic moves through the ASA in the routed and transparent firewall
mode.
How Data Moves Through the ASA in Routed Firewall Mode
The following sections describe how data movesthrough the ASA in routed firewall mode in multiple scenarios.
An Inside User V... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
258 | 3. The ASA translates the real address (10.1.2.27) to the mapped address 209.165.201.10, which is on the
outside interface subnet.
The mapped address could be on any subnet, but routing is simplified when it is on the outside interface
subnet.
4. The ASA then records that a session is established and forwards the packe... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
259 | 3. Because it is a new session, the ASA verifies that the packet is allowed according to the terms of the
security policy.
For multiple context mode, the ASA first classifies the packet to a context.
4. The ASA then adds a session entry to the fast path and forwards the packet from the DMZ interface.
5. When the DMZ we... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
260 | 3. The ASA then records that a session is established and forwards the packet out of the DMZ interface.
4. When the DMZ web server responds to the request, the packet goes through the fast path, which lets the
packet bypass the many lookups associated with a new connection.
5. The ASA forwards the packet to the inside ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
261 | A DMZ User Attempts to Access an Inside Host
The following figure shows a user in the DMZ attempting to access the inside network.
Figure 31: DMZ to Inside
The following steps describe how data moves through the ASA:
1. A user on the DMZ network attempts to reach an inside host. Because the DMZ does not have to route
t... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
262 | Figure 32: Typical Transparent Firewall Data Path
The following sections describe how data moves through the ASA.
An Inside User Visits a Web Server
The following figure shows an inside user accessing an outside web server.
CLI Book 1: Cisco Secure Firewall ASA Series General Operations CLI Configuration Guide, 9.19
20... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
263 | Figure 33: Inside to Outside
The following steps describe how data moves through the ASA:
1. The user on the inside network requests a web page from www.example.com.
2. The ASA receives the packet and adds the source MAC address to the MAC address table, if required.
Because it is a new session, it verifies that the pa... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
264 | Figure 34: Inside to Outside with NAT
The following steps describe how data moves through the ASA:
1. The user on the inside network requests a web page from www.example.com.
2. The ASA receives the packet and adds the source MAC address to the MAC address table, if required.
Because it is a new session, it verifies th... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
265 | An Outside User Visits a Web Server on the Inside Network
The following figure shows an outside user accessing the inside web server.
Figure 35: Outside to Inside
The following steps describe how data moves through the ASA:
1. A user on the outside network requests a web page from the inside web server.
2. The ASA rece... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
266 | 6. The ASA forwards the packet to the outside user.
An Outside User Attempts to Access an Inside Host
The following figure shows an outside user attempting to access a host on the inside network.
Figure 36: Outside to Inside
The following steps describe how data moves through the ASA:
1. A user on the outside network a... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
267 | History for the Firewall Mode
Table 6: Feature History for Firewall Mode
Platform Feature Information
Releases
Feature Name
A transparent firewall is a Layer 2 firewall that actslike a “bump
in the wire,” or a “stealth firewall,” and is not seen as a router
hop to connected devices.
We introduced the following commands... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
268 | Platform Feature Information
Releases
Feature Name
Integrated Routing and Bridging provides the ability to route
between a bridge group and a routed interface. A bridge group
is a group of interfaces that the ASA bridges instead of routes.
The ASA is not a true bridge in that the ASA continues to act
as a firewall: acc... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
269 | CLI Book 1: Cisco Secure Firewall ASA Series General Operations CLI Configuration Guide, 9.19
210
Getting Started with the ASA
History for the Firewall Mode | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
270 | P ART II
High Availability and Scalability
• Multiple Context Mode, on page 213
• Failover for High Availability, on page 259
• Failover for High Availability in the Public Cloud, on page 311
• ASA Cluster for the Secure Firewall 3100, on page 331
• ASA Cluster for the Firepower 4100/9300, on page 419
• ASA Cluster for... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
271 | null | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
272 | CHAPTER 7
Multiple Context Mode
This chapter describes how to configure multiple security contexts on the ASA.
• About Security Contexts, on page 213
• Licensing for Multiple Context Mode, on page 223
• Prerequisites for Multiple Context Mode, on page 224
• Guidelines for Multiple Context Mode, on page 224
• Defaults f... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
273 | Context Configuration Files
This section describes how the ASA implements multiple context mode configurations.
Context Configurations
For each context, the ASA includes a configuration that identifies the security policy, interfaces, and all the
options you can configure on a standalone device. You can store context c... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
274 | Unique Interfaces
If only one context is associated with the ingress interface, the ASA classifies the packet into that context. In
transparent firewall mode, unique interfacesfor contexts are required,so this method is used to classify packets
at all times.
Unique MAC Addresses
If multiple contextsshare an interface, ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
275 | Note that all new incoming traffic must be classified, even from inside networks. The following figure shows
a host on the Context B inside network accessing the Internet. The classifier assigns the packet to Context B
because the ingress interface is Gigabit Ethernet 0/1.3, which is assigned to Context B.
Figure 38: I... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
276 | Figure 39: Transparent Firewall Contexts
Cascading Security Contexts
Placing a context directly in front of another context is called cascading contexts; the outside interface of one
context is the same interface as the inside interface of another context. You might want to cascade contexts
if you want to simplify the ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
277 | Figure 40: Cascading Contexts
Management Access to Security Contexts
The ASA provides system administrator access in multiple context mode as well as access for individual
context administrators.
System Administrator Access
You can access the ASA as a system administrator in two ways:
• Access the ASA console.
From the... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
278 | In routed firewall mode, you can share the Management interface across all contexts.
In transparent firewall mode, the Management interface is special. In addition to the maximum allowed
through-traffic interfaces, you can also use the Management interface as a separate management-only interface.
However, in multiple c... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
279 | Default Class
All contexts belong to the default class if they are not assigned to another class; you do not have to actively
assign a context to the default class.
If a context belongs to a class other than the default class, those class settings always override the default class
settings. However, if the other class ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
280 | Use Oversubscribed Resources
You can oversubscribe the ASA by assigning more than 100 percent of a resource across all contexts (with
the exception of non-burst VPN resources). For example, you can set the Bronze class to limit connections
to 20 percent per context, and then assign 10 contexts to the class for a total ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
281 | About MAC Addresses
You can manually assign MAC addresses to override the default. For multiple context mode, you can
automatically generate unique MAC addresses (for all interfaces assigned to a context) and single context
mode (for subinterfaces)..
You might want to assign unique MAC addresses to subinterfaces define... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
282 | The MAC address format without a prefix is a legacy version. See the mac-address auto command in the
command reference for more information about the legacy format.
Note
VPN Support
For VPN resources, you must configure resource management to allow any VPN tunnels.
You can use site-to-site VPN in multiple context mode.... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
283 | Model License Requirement
Essentials License: 2 contexts.
Optional License, Maximum:
Secure Firewall 3110: 100
Secure Firewall 3120: 100
Secure Firewall 3130: 100
Secure Firewall 3140: 100
Secure Firewall 3100
Essentials License: 10 contexts.
Optional License: up to 250 contexts.
Firepower 4100
Essentials License: 10 c... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
284 | Unsupported Features
Multiple context mode does not support the following features:
• RIP
• OSPFv3. (OSPFv2 is supported.)
• Multicast routing
• Threat Detection
• Unified Communications
• QoS
• Virtual Tunnel Interfaces (VTIs)
• Static route tracking
Multiple context mode does not currently support the following featu... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
285 | Defaults for Multiple Context Mode
• By default, the ASA is in single context mode.
• See Default Class, on page 220.
Configure Multiple Contexts
Procedure
Step 1 Enable or Disable Multiple Context Mode, on page 226.
Step 2 (Optional) Configure a Class for Resource Management, on page 228.
For VPN support, you must con... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
286 | Before you begin
Back up your startup configuration if it differs from the running configuration. When you convert from single
mode to multiple mode, the ASA converts the running configuration into two files. The original startup
configuration is not saved. See Back Up and Restore Configurations or Other Files, on page... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
287 | *** change mode
Restore Single Context Mode
To copy the old running configuration to the startup configuration and to change the mode to single mode,
perform the following steps.
Before you begin
Perform this procedure in the system execution space.
Procedure
Step 1 Copy the backup version of your original running conf... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
288 | Table 7: Resource Names and Limits
System Limit Description
Minimum and
Maximum Number
Resource Name Rate orConcurrent per Context
ASDM management sessions.
ASDM sessions use two HTTPS
connections: one for monitoring that is
always present, and one for making
configuration changes that is present
only when you make cha... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
289 | System Limit Description
Minimum and
Maximum Number
Resource Name Rate orConcurrent per Context
The number of Secure Client sessions
allowed beyond the amount assigned to
a context with vpn anyconnect. For
example, if your model supports 5000
peers, and you assign 4000 peers across
all contexts with vpn anyconnect, the... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
290 | System Limit Description
Minimum and
Maximum Number
Resource Name Rate orConcurrent per Context
1 minimum 100 SSH sessions.
5 maximum
ssh Concurrent
Storage limit of context directory in
MB. Specify the drive using the
storage-url command.
The maximum depends on
your specified flash memory
drive
The maximum
depends on ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
291 | • If you also set the quota management-session command within a context to set the maximum
administrative sessions (SSH, etc.), then the lower value will be used.
Example
For example, to set the default class limit for conns to 10 percent instead of unlimited, and to allow
5 site-to-site VPN tunnels with 2 tunnels allo... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
292 | • Configure interfaces. For transparent mode contexts, you cannot share interfaces between contexts, so
you might want to use subinterfaces. To plan for Management interface usage,see Management Interface
Usage, on page 218.
• Firepower 1100, Firepower 2100 in Appliance mode, Secure Firewall 3100—Basic Interface
Config... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
293 | ciscoasa(config-ctx)# allocate-interface gigabitethernet0/1.100 int1
ciscoasa(config-ctx)# allocate-interface gigabitethernet0/1.200 int2
ciscoasa(config-ctx)# allocate-interface gigabitethernet0/2.300-gigabitethernet0/2.305
int3-int8
Note Do not include a space between the interface type and the port number.
• Enter t... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
294 | ciscoasa(config)# mkdir disk1:/shared-storage
ciscoasa(config)# context admin
ciscoasa(config-ctx)# storage-url private disk1:/private-storage context
ciscoasa(config-ctx)# storage-url shared disk1:/shared-storage shared
You can specify one private storage space per context. You can read/write/delete from this director... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
295 | Example
The following example sets the admin context to be “administrator,” creates a context called
“administrator” on the internal flash memory, and then adds two contexts from an FTP server:
ciscoasa(config)# admin-context admin
ciscoasa(config)# context admin
ciscoasa(config-ctx)# allocate-interface gigabitethernet... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
296 | If you do not enter a prefix, then the ASA autogenerates the prefix based on the last two bytes of the interface.
If you manually enter a prefix, then the prefix is a decimal value between 0 and 65535. This prefix is converted
to a four-digit hexadecimal number, and used as part of the MAC address.
Change Between Conte... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
297 | Procedure
Step 1 Remove a single context:
no context name
All context commands are also removed. The context configuration file is not removed from the config URL
location.
Step 2 Remove all contexts (including the admin context):
clear context
The context configuration files are not removed from the config URL locatio... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
298 | A few system configuration commands, including ntp server, identify an interface name that belongs to the
admin context. If you change the admin context, and that interface name does not exist in the new admin
context, be sure to update any system commands that refer to the interface.
Change the Security Context URL
Th... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
299 | ciscoasa(config)#
Step 3 Enter the context configuration mode for the context you want to change.
context name
Example:
ciscoasa(config)# context ctx1
Step 4 Enter the new URL. The system immediately loads the context so that it is running.
config-url new_url
Example:
ciscoasa(config)# config-url ftp://user1:passw0rd@1... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
300 | Step 3 Reload the configuration:
copy startup-config running-config
Example:
ciscoasa/ctx1(config)# copy startup-config running-config
The ASA copies the configuration from the URL specified in the system configuration. You cannot change
the URL from within a context.
Reload by Removing and Re-adding the Context
To rel... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
301 | Example
The following is sample output from the show context command. The following sample output
shows three contexts:
ciscoasa# show context
Context Name Interfaces URL
*admin GigabitEthernet0/1.100 disk0:/admin.cfg
GigabitEthernet0/1.101
contexta GigabitEthernet0/1.200 disk0:/contexta.cfg
GigabitEthernet0/1.201
cont... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
302 | Flags: 0x00000009, ID: 258
See the command reference for more information about the detail output.
The following is sample output from the show context count command:
ciscoasa# show context count
Total active contexts: 2
View Resource Allocation
From the system execution space, you can view the allocation for each reso... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
303 | Table 9: show resource allocation Fields
Field Description
Resource The name of the resource that you can limit.
The total amount of the resource that is allocated across all contexts. The amount is an
absolute number of concurrent instances or instances per second. If you specified a
percentage in the class definition... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
304 | gold 1 D 5 5 5.00%
silver 1 CA 10 10 10.00%
bronze 0 CA 5
All Contexts: 3 20 20.00%
Routes default all C unlimited N/A
gold 1 D unlimited 5 N/A
silver 1 CA 10 10 N/A
bronze 0 CA 5 N/A
All Contexts: 3 20 N/A
Xlates default all CA unlimited
gold 1 DA unlimited
silver 1 CA 23040 23040 N/A
bronze 0 CA 11520
All Contexts: 3... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
305 | Field Description
The percentage of the total system resources that is allocated across all contexts in the
class. If the resource is unlimited, this display is blank. If the resource does not have a
system limit, then this column shows N/A.
% of Avail
View Resource Usage
From the system execution space, you can view t... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
306 | • To show all resources, set the count_threshold to 0.
Examples
The following is sample output from the show resource usage context command, which shows the
resource usage for the admin context:
ciscoasa# show resource usage context admin
Resource Current Peak Limit Denied Context
Telnet 1 1 5 0 admin
Conns 44 55 N/A 0... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
307 | Resource Current Peak Limit Denied Context
Telnet 0 0 100 0 System
SSH 0 0 100 0 System
ASDM 0 0 32 0 System
Routes 0 0 N/A 0 System
IPSec 0 0 5 0 System
Syslogs [rate] 1 18 N/A 0 System
Conns 0 1 280000 0 System
Xlates 0 0 N/A 0 System
Hosts 0 2 N/A 0 System
Conns [rate] 1 1 N/A 0 System
Inspects [rate] 0 0 N/A 0 Syst... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
308 | Connections 0/s 0/s
TCP Conns 0/s 0/s
UDP Conns 0/s 0/s
URL Access 0/s 0/s
URL Server Req 0/s 0/s
WebSns Req 0/s 0/s
TCP Fixup 0/s 0/s
HTTP Fixup 0/s 0/s
FTP Fixup 0/s 0/s
AAA Authen 0/s 0/s
AAA Author 0/s 0/s
AAA Account 0/s 0/s
TCP Intercept 322779/s 322779/s
The following is sample output from the show resource usag... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
309 | chunk:list-hdr 1 1 unlimited 0 system
chunk:route 1 1 unlimited 0 system
block:16384 510 885 unlimited 0 system
block:2048 32 34 unlimited 0 system
The following sample output shows the resources being used by TCP intercept for the entire system.
(Sample text in bold shows the TCP intercept information.)
ciscoasa(confi... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
310 | The all option is required to view the assigned MAC addresses. Although the mac-address auto command
is user-configurable in global configuration mode only, the command appears as a read-only entry in context
configuration mode along with the assigned MAC address. Only allocated interfaces that are configured with
a na... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
311 | mac-address auto GigabitEthernet0/1.1 a2d2.0400.120a a2d2.0400.120b
mac-address auto GigabitEthernet0/1.2 a2d2.0400.120e a2d2.0400.120f
mac-address auto GigabitEthernet0/1.3 a2d2.0400.1212 a2d2.0400.1213
config-url disk0:/CTX2.cfg
!
View MAC Addresses Within a Context
This section describes how to view MAC addresses wi... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
312 | • Creates a context called “administrator” on the internal flash memory to be part of the default resource
class.
• Adds two contexts from an FTP server as part of the gold resource class.
ciscoasa(config)# mac-address auto prefix 19
ciscoasa(config)# class default
ciscoasa(config-class)# limit-resource conns 10%
cisco... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
313 | History for Multiple Context Mode
Table 11: History for Multiple Context Mode
Platform Feature Information
Releases
Feature Name
Multiple context mode was introduced.
We introduced the following commands: context, mode, and class.
Multiple security contexts 7.0(1)
Automatic assignment of MAC address to context interfac... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
314 | Platform Feature Information
Releases
Feature Name
In multiple context mode, the ASA now converts the automatic MAC address
generation configuration to use a default prefix. The ASA auto-generates the prefix
based on the last two bytes of the interface (ASA 5500-X) or backplane (ASASM)
MAC address. This conversion happ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
315 | Platform Feature Information
Releases
Feature Name
You can now use the following remote access features in multiple context mode:
• AnyConnect 3.x and later (SSL VPN only; no IKEv2 support)
• Centralized Secure Client image configuration
• Secure Client image upgrade
• Context Resource Management for Secure Client conn... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
316 | Platform Feature Information
Releases
Feature Name
Localization is supported globally. There is only one set of localization files that are
shared across different contexts.
We did not modify any commands.
Remote Access VPN localization is 9.6(2)
supported in multiple context mode
Remote Access VPN for IKEv2 is 9.9(2) ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
317 | CLI Book 1: Cisco Secure Firewall ASA Series General Operations CLI Configuration Guide, 9.19
258
High Availability and Scalability
History for Multiple Context Mode | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
318 | CHAPTER 8
Failover for High Availability
This chapter describes how to configure Active/Standby or Active/Active failover to accomplish high availability
of the ASA.
• About Failover, on page 259
• Licensing for Failover, on page 278
• Guidelines for Failover, on page 279
• Defaults for Failover, on page 281
• Configur... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
319 | Both failover modes support stateful or stateless failover.
Failover System Requirements
This section describes the hardware, software, and license requirements for ASAs in aFailover configuration.
Hardware Requirements
The two units in a Failover configuration must:
• Be the same model. In addition, for container inst... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
320 | • Be in the same FIPS mode.
• (Firepower 4100/9300) Have the same flow offload mode, either both enabled or both disabled.
License Requirements
The two units in a failover configuration do not need to have identical licenses; the licenses combine to make
a failover cluster license.
Failover and Stateful Failover Links
... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
321 | • 5506-X through 5555-X—You cannot use the Management interface as the failover link; you must use
a data interface. The only exception is for the 5506H-X, where you can use the management interface
as the failover link.
• 5506H-X—You can use the Management 1/1 interface asthe failover link. If you configure it for fai... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
322 | Dedicated Interface
You can use a dedicated data interface (physical or EtherChannel) for the state link. See Interface for the
Failover Link, on page 261 for requirements for a dedicated state link, and Connecting the Failover Link, on
page 262 for information about connecting the state link as well.
For optimum perfo... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa919/configuration/general/asa-919-general-config.pdf |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.