Cisco Systems ASA5515K9, ASA 5500 Monitoring the ASA CX Module

59-12
Cisco ASA 5500 Series Configuration Guide using the CLI
Chapter59 Configuring the ASA CX Module
Monitoring the ASA CX Module
Monitoring the ASA CX Module
•Showing Module Status, page 59-12
•Showing Module Statistics, page59-13
•Monitoring Module Connections, page59-14
•Capturing Module Traffic, page 59-17
•Debugging the Module, page59-19
Note For ASA CX-related syslog messages, see the syslog message guide. ASA CX syslog messages start
with message number 429001.
Showing Module Status
To check the status of a module, enter one of the following commands:
Step6 (Optional)
class name2
Example:
hostname(config-pmap)# class cx_class2
If you created multiple class maps for ASA CX traffic, you can
specify another class for the policy.
See the “Feature Matching Within a Service Policy” section on
page 32-3 for detailed information about how the order of classes
matters within a policy map. Traffic cannot match more than one
class map for the same action type.
Step7 (Optional)
cxsc {fail-close | fail-open} [auth-proxy]
Example:
hostname(config-pmap-c)# cxsc fail-close
auth-proxy
Specifies that the second class of traffic should be sent to the ASA
CX module.
Add as many classes as desired by repeating these steps.
Step8 service-policy policymap_name {global |
interface interface_name}
Example:
hostname(config)# service-policy cx_policy
interface outside
Activates the policy map on one or more interfaces. global applies
the policy map to all interfaces, and interface applies the policy
to one interface. Only one global policy is allowed. You can
override the global policy on an interface by applying a service
policy to that interface. You can only apply one policy map to
each interface.
Command Purpose
Command Purpose
show module Displays the status.
show module 1 details Displays additional status information.