Information About the ASA CX Module
The ASA CX module lets you enforce security based on the full context of a situation. This context includes the identity of the user (who), the application or website that the user is trying to access (what), the origin of the access attempt (where), the time of the attempted access (when), and the properties of the device used for the access (how). With the ASA CX module, you can extract the full context of a flow and enforce granular policies such as permitting access to Facebook but denying access to games on Facebook, or permitting finance employees access to a sensitive enterprise database but denying the same access to other employees.
How the ASA CX Module Works with the ASA
The ASA CX module runs a separate application from the ASA. The ASA CX module includes external management interface(s) so you can connect to the ASA CX module directly. Any data interfaces on the ASA CX module are used for ASA traffic only.
Traffic goes through the firewall checks before being forwarded to the ASA CX module. When you identify traffic for ASA CX inspection on the ASA, traffic flows through the ASA and the ASA CX module as follows:
1. Traffic enters the ASA.
2. Incoming VPN traffic is decrypted.
3. Firewall policies are applied.
4. Traffic is sent to the ASA CX module.
5. The ASA CX module applies its security policy to the traffic, and takes appropriate actions.
6. Valid traffic is sent back to the ASA; the ASA CX module might block some traffic according to its security policy, and that traffic is not passed on.
7. Outgoing VPN traffic is encrypted.
8. Traffic exits the ASA.
Figure 30-1 shows the traffic flow when using the ASA CX module. In this example, the ASA CX module automatically blocks traffic that is not allowed for a certain application. All other traffic is forwarded through the ASA.
Figure 30-1 ASA CX Module Traffic Flow in the ASA
Note If you have a connection between hosts on two ASA interfaces, and the ASA CX service policy is only configured for one of the interfaces, then all traffic between these hosts is sent to the ASA CX module, including traffic originating on the non-ASA CX interface (because the feature is bidirectional). However, the ASA only performs the authentication proxy on the interface to which the service policy is applied, because authentication proxy is applied only to ingress traffic (see the “Information About Authentication Proxy” section).
Monitor-Only Mode
For demonstration purposes, you can configure a service policy or a traffic-forwarding interface in monitor-only mode.
For guidelines and limitations for monitor-only mode, see the “Guidelines and Limitations” section.
Service Policy in Monitor-Only Mode
For testing and demonstration purposes, you can configure the ASA to send a duplicate stream of read-only traffic to the ASA CX module, so you can see how the module inspects the traffic without affecting the ASA traffic flow. In this mode, the ASA CX module inspects the traffic as usual, makes policy decisions, and generates events. However, because the packets are read-only copies, the module actions do not affect the actual traffic. Instead, the module drops the copies after inspection. Figure 30-2 shows the ASA CX module in monitor-only mode.
Figure 30-2 ASA CX Monitor-Only Mode
Traffic-Forwarding Interface in Monitor-Only Mode
You can alternatively configure ASA interfaces to be traffic-forwarding interfaces, where all traffic received is forwarded directly to the ASA CX module without any ASA processing. For testing and demonstration purposes, traffic-forwarding removes the extra complication of ASA processing. Traffic-forwarding is only supported in monitor-only mode, so the ASA CX module drops the traffic after inspecting it. Figure 30-3 shows the ASA GigabitEthernet 0/3 interface configured for traffic-forwarding. That interface is connected to a switch SPAN port so the ASA CX module can inspect all of the network traffic.
Figure 30-3 ASA CX Traffic-Forwarding
Information About ASA CX Management
Initial Configuration
For initial configuration, you must use the CLI on the ASA CX module to run the
setup
command and configure other optional settings.
To access the CLI, you can use the following methods:
– ASA CX console port—The ASA CX console port is a separate external console port.
– ASA CX Management 1/0 interface using SSH—You can connect to the default IP address (192.168.8.8), or you can use ASDM to change the management IP address and then connect using SSH. The ASA CX management interface is a separate external Gigabit Ethernet interface.
Note You cannot access the ASA CX hardware module CLI over the ASA backplane using the session command.
-
ASA 5512-X through ASA 5555-X:
– ASA session over the backplane—If you have CLI access to the ASA, then you can session to the module and access the module CLI.
– ASA CX Management 0/0 interface using SSH—You can connect to the default IP address (192.168.1.2), or you can use ASDM to change the management IP address and then connect using SSH. These models run the ASA CX module as a software module. The ASA CX management interface shares the Management 0/0 interface with the ASA. Separate MAC addresses and IP addresses are supported for the ASA and ASA CX module. You must perform configuration of the ASA CX IP address within the ASA CX operating system (using the CLI or ASDM). However, physical characteristics (such as enabling the interface) are configured on the ASA. You can remove the ASA interface configuration (specifically the interface name) to dedicate this interface as an ASA CX-only interface. This interface is management-only.
Policy Configuration and Management
After you perform initial configuration, configure the ASA CX policy using Cisco Prime Security Manager (PRSM). Then configure the ASA policy for sending traffic to the ASA CX module using ASDM or the ASA CLI.
Note When using PRSM in multiple device mode, you can configure the ASA policy for sending traffic to the ASA CX module within PRSM, instead of using ASDM or the ASA CLI. Using PRSM lets you consolodate management to a single management system. However, PRSM has some limitations when configuring the ASA service policy; see the ASA CX user guide for more information.
Information About Authentication Proxy
When the ASA CX needs to authenticate an HTTP user (to take advantage of identity policies), you must configure the ASA to act as an authentication proxy: the ASA CX module redirects authentication requests to the ASA interface IP address/proxy port. By default, the port is 885 (user configurable). Configure this feature as part of the service policy to divert traffic from the ASA to the ASA CX module. If you do not enable the authentication proxy, only passive authentication is available.
Note If you have a connection between hosts on two ASA interfaces, and the ASA CX service policy is only configured for one of the interfaces, then all traffic between these hosts is sent to the ASA CX module, including traffic orginiating on the non-ASA CX interface (the feature is bidirectional). However, the ASA only performs the authentication proxy on the interface to which the service policy is applied, because this feature is ingress-only.
Information About VPN and the ASA CX Module
The ASA includes VPN client and user authentication metadata from the Cisco AnyConnect client when forwarding traffic to the ASA CX module, which allows the ASA CX module to include this information as part of its policy lookup criteria. The VPN metadata is sent only at VPN tunnel establishment time along with a type-length-value (TLV) containing the session ID. The ASA CX module caches the VPN metadata for each session. Each tunneled connection sends the session ID so the ASA CX module can look up that session’s metadata.
Compatibility with ASA Features
The ASA includes many advanced application inspection features, including HTTP inspection. However, the ASA CX module provides more advanced HTTP inspection than the ASA provides, as well as additional features for other applications, including monitoring and controlling application usage.
To take full advantage of the ASA CX module features, see the following guidelines for traffic that you send to the ASA CX module:
-
Do not configure ASA inspection on HTTP traffic.
-
Do not configure Cloud Web Security (ScanSafe) inspection. If you configure both the ASA CX action and Cloud Web Security inspection for the same traffic, the ASA only performs the ASA CX action.
-
Other application inspections on the ASA are compatible with the ASA CX module, including the default inspections.
-
Do not enable the Mobile User Security (MUS) server; it is not compatible with the ASA CX module.
-
Do not enable ASA clustering; it is not compatible with the ASA CX module.
-
If you enable failover, when the ASA fails over, any existing ASA CX flows are transferred to the new ASA, but the traffic is allowed through the ASA without being acted upon by the ASA CX module. Only new flows recieved by the new ASA are acted upon by the ASA CX module.
-
(9.1(1) and earlier) Does not support NAT 64. In 9.1(2) and later, NAT 64 is supported.
Configuring the ASA CX Module
This section describes how to configure the ASA CX module.
Connecting the ASA CX Management Interface
In addition to providing management access to the ASA CX module, the ASA CX management interface needs access to an HTTP proxy server or a DNS server and the Internet for signature updates and more. This section describes recommended network configurations. Your network may differ.
ASA 5585-X (Hardware Module)
The ASA CX module includes a separate management interface from the ASA. For initial setup, you can connect with SSH to the ASA CX Management 1/0 interface using the default IP address (192.168.8.8/24). If you cannot use the default IP address, you can either use the console port or use ASDM to change the management IP address so you can use SSH.
If you have an inside router
If you have an inside router, you can route between the management network, which can include both the ASA Management 0/0 and ASA CX Management 1/0 interfaces, and the ASA inside network for Internet access. Be sure to also add a route on the ASA to reach the Management network through the inside router.
If you do not have an inside router
If you have only one inside network, then you cannot also have a separate management network, which would require an inside router to route between the networks. In this case, you can manage the ASA from the inside interface instead of the Management 0/0 interface. Because the ASA CX module is a separate device from the ASA, you can configure the ASA CX Management 1/0 address to be on the same network as the inside interface.
ASA 5512-X through ASA 5555-X (Software Module)
These models run the ASA CX module as a software module, and the ASA CX management interface shares the Management 0/0 interface with the ASA.
If you have an inside router
If you have an inside router, you can route between the Management 0/0 network, which includes both the ASA and ASA CX management IP addresses, and the inside network for Internet access. Be sure to also add a route on the ASA to reach the Management network through the inside router.
If you do not have an inside router
If you have only one inside network, then you cannot also have a separate management network. In this case, you can manage the ASA from the inside interface instead of the Management 0/0 interface. If you remove the ASA-configured name from the Management 0/0 interface, you can still configure the ASA CX IP address for that interface. Because the ASA CX module is essentially a separate device from the ASA, you
can
configure the ASA CX management address to be on the same network as the inside interface.
Note You must remove the ASA-configured name for Management 0/0; if it is configured on the ASA, then the ASA CX address must be on the same network as the ASA, and that excludes any networks already configured on other ASA interfaces. If the name is not configured, then the ASA CX address can be on any network, for example, the ASA inside network.
(ASA 5512-X through ASA 5555-X; May Be Required) Installing the Software Module
If you purchase the ASA with the ASA CX module, the module software and required solid state drive(s) (SSDs) come pre-installed and ready to go. If you want to add the ASA CX to an existing ASA, or need to replace the SSD, you need to install the ASA CX boot software and partition the SSD according to this procedure. To physically install the SSD, see the ASA hardware guide.
Note For the ASA 5585-X hardware module, you must install or upgrade your image from within the ASA CX module. See the ASA CX module documentation for more information.
Prerequisites
-
The free space on flash (disk0) should be at least 3GB plus the size of the boot software.
-
In multiple context mode, perform this procedure in the system execution space.
Detailed Steps
Step 1 Download the ASA CX boot software from Cisco.com to your computer.
If you have a Cisco.com login, you can obtain the boot software from the following website:
http://www.cisco.com/cisco/software/release.html?mdfid=284325223&softwareid=284399946
The boot software lets you set basic ASA CX network configuration, partition the SSD, and download the larger system software from a server of your choice to the SSD.
Step 2 Download the ASA CX system software from Cisco.com to an HTTP, HTTPS, or FTP server accessible from the ASA CX management interface.
If you have a Cisco.com login, you can obtain the boot software from the following website:
http://www.cisco.com/cisco/software/release.html?mdfid=284325223&softwareid=284399946
Step 3 In ASDM, choose
Tools > File Management
, and then choose
File Transfer > Between Local PC and Flash
. Transfer the boot software to disk0 on the ASA. Do not transfer the system software; it is downloaded later to the SSD.
Step 4 Connect to the ASA CLI, and enter privileged EXEC mode. See the “Getting Started” chapter in the general operations configuration guide to access the ASA CLI.
Step 5 If you are replacing the IPS module with the ASA CX module, shut down and uninstall the IPS module, and then reload the ASA:
ciscoasa# sw-module module ips shutdown ciscoasa# sw-module module ips uninstall
After the ASA reloads, reconnect to the ASA CLI.
Step 6 Set the ASA CX module boot image location in ASA disk0 by entering the following command:
ciscoasa# sw-module module cxsc recover configure image disk0:file_path
Example:
ciscoasa# sw-module module cxsc recover configure image disk0:asacx-boot-9.1.1.img
Step 7 Load the ASA CX boot image by entering the following command:
ciscoasa# sw-module module cxsc recover boot
Step 8 Wait approximately 5 minutes for the ASA CX module to boot up, and then open a console session to the now-running ASA CX boot image. The default username is
admin
and the default password is
Admin123
.
ciscoasa# session cxsc console Establishing console session with slot 1 Opening console session with module cxsc. Connected to module cxsc. Escape character sequence is 'CTRL-SHIFT-6 then x'.
Step 9 Partition the SSD:
Partition Successfully Completed
Step 10 Perform the basic network setup using the
setup
command according to the “Configuring Basic ASA CX Settings at the ASA CX CLI” section (do not exit the ASA CX CLI), and then return to this procedure to install the software image.
Step 11 Install the system software from the server:
asacx-boot> system install url
Example:
The following command installs the asacx-sys-9.1.1.pkg system software.
asacx-boot> system install https://upgrades.example.com/packages/asacx-sys-9.1.1.pkg Cisco ASA CX System Upgrade Do you want to continue with upgrade? [n]: Y Warning: Please do not interrupt the process or turn off the system. Doing so might leave system in unusable state. Stopping all the services ... Starting upgrade process ... Reboot is required to complete the upgrade. Press Enter to reboot the system.
Step 12 Press
Enter
to reboot the ASA CX module. Rebooting the module closes the console session. Allow 10 or more minutes for application component installation and for the ASA CX services to start.
(ASA 5585-X) Changing the ASA CX Management IP Address
If you cannot use the default management IP address (192.168.8.8), then you can set the management IP address from the ASA. After you set the management IP address, you can access the ASA CX module using SSH to perform initial setup.
Note For a software module, you can access the ASA CX CLI to perform setup by sessioning from the ASA CLI; you can then set the ASA CX management IP address as part of setup. See the “Configuring Basic ASA CX Settings at the ASA CX CLI” section.
Guidelines
In multiple context mode, perform this procedure in the system execution space.
Detailed Steps
Multiple Context Mode
Step 1 In the System, choose Tools > Command Line Interface.
Step 2 Enter the following command:
|
|
session 1 do setup host ip
ip_address
/
mask
,
gateway_ip
ciscoasa# session 1 do setup host ip 10.1.1.2/24,10.1.1.1
|
Sets the ASA CX management IP address, mask, and gateway.
|
Step 3 Click Send.
Single Context Mode
Step 1 In ASDM, choose
Wizards > Startup Wizard
.
Step 2 Click
Next
to advance through the initial screens until you reach the ASA CX Basic Configuration screen.
Step 3 Enter the new management IP address, subnet mask, and default gateway.
Step 4 (Optional) Change the Auth Proxy Port. You can set this later if desired. See the “(Optional) Configuring the Authentication Proxy Port” section for more information.
Step 5 Click
Finish
to skip the remaining screens, or click
Next
to advance through the remaining screens and complete the wizard.
Configuring Basic ASA CX Settings at the ASA CX CLI
You must configure basic network settings and other parameters on the ASA CX module before you can configure your security policy.
Detailed Steps
Step 1 Do one of the following:
-
(All models) Use SSH to connect to the ASA CX management IP address.
-
(ASA 5512-X through ASA 5555-X) Open a console session to the module from the ASA CLI (see the “Getting Started” chapter in the general operations configuration guide to access the ASA CLI). In multiple context mode, session from the system execution space.
ciscoasa# session cxsc console
Step 2 Log in with the username
admin
and the password
Admin123
. You will change the password as part of this procedure.
Step 3 Enter the following
command:
Example:
Welcome to Cisco Prime Security Manager Setup Default values are inside [ ]
You are prompted through the setup wizard. The following example shows a typical path through the wizard; if you enter
Y
instead of
N
at a prompt, you will be able to configure some additional settings. This example shows how to configure both IPv4 and IPv6 static addresses. You can configure IPv6 stateless auto configuration by answering
N
when asked if you want to configure a static IPv6 address.
Enter a hostname [asacx]: asa-cx-host Do you want to configure IPv4 address on management interface?(y/n) [Y]: Y Do you want to enable DHCP for IPv4 address assignment on management interface?(y/n)[N]: N Enter an IPv4 address [192.168.8.8]: 10.89.31.65 Enter the netmask [255.255.255.0]: 255.255.255.0 Enter the gateway [192.168.8.1]: 10.89.31.1 Do you want to configure static IPv6 address on management interface?(y/n) [N]: Y Enter an IPv6 address: 2001:DB8:0:CD30::1234/64 Enter the gateway: 2001:DB8:0:CD30::1 Enter the primary DNS server IP address [ ]: 10.89.47.11 Do you want to configure Secondary DNS Server? (y/n) [N]: N Do you want to configure Local Domain Name? (y/n) [N] Y Enter the local domain name: example.com Do you want to configure Search domains? (y/n) [N] Y Enter the comma separated list for search domains: example.com Do you want to enable the NTP service?(y/n) [N]: Y Enter the NTP servers separated by commas: 1.ntp.example.com, 2.ntp.example.com
Step 4 After you complete the final prompt, you are presented with a summary of the settings. Look over the summary to verify that the values are correct, and enter
Y
to apply your changed configuration. Enter
N
to cancel your changes.
Example:
Apply the changes?(y,n) [Y]: Y Configuration saved successfully! Generating self-signed certificate, the web server will be restarted after that Press ENTER to continue...
Note If you change the host name, the prompt does not show the new name until you log out and log back in.
Step 5 If you do not use NTP, configure the time settings. The default time zone is the UTC time zone. Use the
show time
command to see the current settings. You can use the following commands to change time settings:
Step 6 Change the admin password by entering the following command:
Example:
The password must be at least 8 characters long and must contain at least one uppercase letter (A-Z), at least one lowercase letter (a-z) and at least one digit (0-9). Enter password: Farscape1 Confirm password: Farscape1 SUCCESS: Password changed for user admin
Step 7 Enter the
exit
command to log out.
Configuring the Security Policy on the ASA CX Module Using PRSM
This section describes how to launch PRSM to configure the ASA CX module application. For details on using PRSM to configure your ASA CX security policy, see the ASA CX user guide.
Detailed Steps
You can launch PRSM from your web browser, or you can launch it from ASDM.
-
Launch PRSM from a web browser by enter the following URL:
https://ASA_CX_management_IP
Where the ASA CX management IP address is the one you set in the “Configuring Basic ASA CX Settings at the ASA CX CLI” section.
-
Launch PRSM from ASDM by choosing
Home > ASA CX Status
, and clicking the
Connect to the ASA CX application
link.
Guidelines
In multiple context mode, perform this procedure within each security context.
Detailed Steps
Step 1 In ASDM, choose
Configuration > Firewall > Advanced > ASA CX Auth Proxy
.
Step 2 Enter a port greater than 1024. The default is 885.
Step 3 Click
Apply
.
Redirecting Traffic to the ASA CX Module
You can redirect traffic to the ASA CX module by creating a service policy that identifies specific traffic. For demonstration purposes only, you can also enable monitor-only mode for the service policy, which forwards a copy of traffic to the ASA CX module, while the original traffic remains unaffected.
Another option for demonstration purposes is to configure a traffic-forwarding interface instead of a service policy in monitor-only mode. The traffic-forwarding interface sends all traffic directly to the ASA CX module, bypassing the ASA.
Creating the ASA CX Service Policy
This section identifies traffic to redirect from the ASA to the ASA CX module. Configure this policy on the ASA. If you want to use a traffic-forwarding interface for demonstration purposes, skip this procedure and see the “Configuring Traffic-Forwarding Interfaces (Monitor-Only Mode)” section instead.
Note When using PRSM in multiple device mode, you can configure the ASA policy for sending traffic to the ASA CX module within PRSM, instead of using ASDM or the ASA CLI. However, PRSM has some limitations when configuring the ASA service policy; see the ASA CX user guide for more information.
Prerequisites
-
If you enable the authentication proxy on the ASA using this procedure, be sure to also configure a directory realm for authentication on the ASA CX module. See the ASA CX user guide for more information.
-
If you have an active service policy redirecting traffic to an IPS module (that you replaced with the ASA CX), you must remove that policy before you configure the ASA CX service policy.
-
Be sure to configure both the ASA policy and the ASA CX to have matching modes: both in monitor-only mode, or both in normal inline mode.
-
In multiple context mode, perform this procedure within each security context.
Detailed Steps
Step 1 Choose
Configuration > Firewall > Service Policy Rules
.
Step 2 Choose
Add > Add Service Policy Rule
. The Add Service Policy Rule Wizard - Service Policy dialog box appears.
Step 3 Complete the Service Policy dialog box as desired. See the ASDM online help for more information about these screens.
Step 4 Click
Next
. The Add Service Policy Rule Wizard - Traffic Classification Criteria dialog box appears.
Step 5 Complete the Traffic Classification Criteria dialog box as desired. See the ASDM online help for more information about these screens.
Step 6 Click
Next
to show the Add Service Policy Rule Wizard - Rule Actions dialog box.
Step 7 Click the
ASA CX Inspection
tab.
Step 8 Check the
Enable ASA CX for this traffic flow
check box.
Step 9 In the If ASA CX Card Fails area, click one of the following:
-
Permit traffic
—Sets the ASA to allow all traffic through, uninspected, if the ASA CX module is unavailable.
-
Close traffic
—Sets the ASA to block all traffic if the ASA CX module is unavailable.
Step 10 (Optional) To enable the authentication proxy, which is required for active authentication, check the
Enable Auth Proxy
check box. This option is not available in monitor-only mode.
Step 11 (Optional) For demonstration purposes only, check the
Monitor-only
check box to send a read-only copy of traffic to the ASA CX module. See the “Monitor-Only Mode” section for more information.
Note You must configure all classes and policies to be either in monitor-only mode, or in normal inline mode; you cannot mix both modes on the same ASA.
Step 12 Click
OK
and then
Apply
.
Step 13 Repeat this procedure to configure additional traffic flows as desired.
Configuring Traffic-Forwarding Interfaces (Monitor-Only Mode)
This section configures traffic-forwarding interfaces, where all traffic is forwarded directly to the ASA CX module. This method is for demonstration purposes only. For a normal ASA CX service policy, see the “Creating the ASA CX Service Policy” section.
For more information see the “Monitor-Only Mode” section. See also the “Guidelines and Limitations” section for guidelines and limitations specific to traffic-forwarding interfaces.
You can only configure this feature at the CLI; you can use the Command Line Interface tool.
Prerequisites
-
Be sure to configure both the ASA policy and the ASA CX to have matching modes: both in monitor-only.
-
In multiple context mode, perform this procedure within each security context.
Detailed Steps
Step 1 Choose
Tools > Command Line Interface
.
Step 2 Click the
Multiple Line
radio button.
Step 3 Enter the following commands:
|
|
|
Step 1
|
interface
physical_interface
ciscoasa(config)# interface gigabitethernet 0/5
|
Enters interface configuration mode for the physical interface you want to use for traffic-forwarding.
|
Step 2
|
no nameif
ciscoasa(config-ifc)# no nameif
|
Removes any name configured for the interface. If this interface was used in any ASA configuration, that configuration is removed. You cannot configure traffic-forwarding on a named interface.
|
Step 3
|
traffic-forward cxsc monitor-only
ciscoasa(config-ifc)# traffic-forward cxsc monitor-only
|
Enables traffic-forwarding. You see a warning similar to the following:
WARNING: This configuration is purely for demo of CX functionality and shouldn't be used on a production ASA and any issues found when mixing demo feature with production ASA is not supported.
|
Step 4
|
no shutdown
ciscoasa(config-ifc)# no shutdown
|
Enables the interface.
|
Step 4 Repeat for any additional interfaces.
Step 5 Click
Send
.
Examples
The following example makes GigabitEthernet 0/5 a traffic-forwarding interface:
Managing the ASA CX Module
This section includes procedures that help you manage the module.
Resetting the Password
You can reset the module password to the default. For the user
admin
, the default password is
Admin123
. After resetting the password, you should change it to a unique value using the module application.
Resetting the module password causes the module to reboot. Services are not available while the module is rebooting.
If you cannot connect to ASDM with the new password, restart ASDM and try to log in again. If you defined a new password and still have an existing password in ASDM that is different from the new password, clear the password cache by choosing
File > Clear ASDM Password Cache
, then restart ASDM and try to log in again.
To reset the module password to the default of Admin123, perform the following steps.
Guidelines
In multiple context mode, perform this procedure in the system execution space.
Detailed Steps
Step 1 From the ASDM menu bar, choose
Tools > ASA CX Password Reset
.
The Password Reset confirmation dialog box appears.
Step 2 Click
OK
to reset the password to the default
Admin123
.
A dialog box displays the success or failure of the password reset.
Step 3 Click
Close
to close the dialog box.
Reloading or Resetting the Module
To reload or reset the module, enter one of the following commands at the ASA CLI.
Guidelines
In multiple context mode, perform this procedure in the system execution space.
Detailed Steps
|
|
For a hardware module (ASA 5585-X):
hw-module module 1 reload
For a software module (ASA 5512-X through ASA 5555-X):
sw-module module cxsc reload
ciscoasa# hw-module module 1 reload
|
Reloads the module software.
|
For a hardware module:
For a software module:
sw-module module cxsc reset
ciscoasa# hw-module module 1 reset
|
Performs a reset, and then reloads the module.
|
Shutting Down the Module
Shutting down the module software prepares the module to be safely powered off without losing configuration data.
Note
: If you reload the ASA, the module is not automatically shut down, so we recommend shutting down the module before reloading the ASA. To gracefully shut down the module, perform the following steps at the ASA CLI.
Guidelines
In multiple context mode, perform this procedure in the system execution space.
Detailed Steps
|
|
For a hardware module (ASA 5585-X):
hw-module module 1 shutdown
For a software module (ASA 5512-X through ASA 5555-X):
sw-module module cxsc shutdown
ciscoasa# hw-module module 1 shutdown
|
Shuts down the module.
|
(ASA 5512-X through ASA 5555-X) Uninstalling a Software Module Image
To uninstall a software module image and associated configuration, perform the following steps.
Guidelines
In multiple context mode, perform this procedure in the system execution space.
Detailed Steps
|
|
|
Step 1
|
sw-module module
cxsc
uninstall
ciscoasa# sw-module module cxsc uninstall
Module cxsc will be uninstalled. This will completely remove the
disk image associated with the sw-module including any configuration
that existed within it.
Uninstall module <id>? [confirm]
|
Permanently uninstalls the software module image and associated configuration.
|
Step 2
|
reload
ciscoasa# reload
|
Reloads the ASA. You must reload the ASA before you can install a new module type.
|
(ASA 5512-X through ASA 5555-X) Sessioning to the Module From the ASA
To access the ASA CX software module CLI from the ASA, you can session from the ASA. You can either session to the module (using Telnet) or create a virtual console session. A console session might be useful if the control plane is down and you cannot establish a Telnet session.
You may need to access the CLI if you are using multiple context mode and you need to set basic network settings using the CLI, or for troubleshooting.
Guidelines
In multiple context mode, perform this procedure in the system execution space.
Detailed Steps
|
|
Telnet session.
ciscoasa# session cxsc
Opening command session with slot 1.
Connected to module cxsc. Escape character sequence is 'CTRL-^X'.
cxsc login: admin
Password: Admin123
|
Accesses the module using Telnet. You are prompted for the username and password. The default username is
admin
, and the default password is
Admin123
.
|
Console session.
ciscoasa# session cxsc console
Establishing console session with slot 1
Opening console session with module cxsc.
Connected to module cxsc. Escape character sequence is 'CTRL-SHIFT-6 then x'.
cxsc login: admin
Password: Admin123
|
Accesses the module console. You are prompted for the username and password. The default username is
admin
, and the default password is
Admin123
.
Note Do not use this command in conjunction with a terminal server where Ctrl-Shift-6, x is the escape sequence to return to the terminal server prompt. Ctrl-Shift-6, x is also the sequence to escape the ASA CX console and return to the ASA prompt. Therefore, if you try to exit the ASA CX console in this situation, you instead exit all the way to the terminal server prompt. If you reconnect the terminal server to the ASA, the ASA CX console session is still active; you can never exit to the ASA prompt. You must use a direct serial connection to return the console to the ASA prompt.
Use the session cxsc command instead.
|