17-24
Cisco ASA Series Firewall CLI Configuration Guide
Chapter 17 ASA CX Module
Troubleshooting Problems with the Authentication Proxy
•
cxsc-request—The frame was requested to be dropped by CXSC due a policy on CXSC whereby
CXSC would set the actions to Deny Source, Deny Destination, or Deny Pkt.
•
cxsc-fail-close—The packet is dropped because the card is not up and the policy configured was
‘fail-close’ (rather than ‘fail-open’ which allows packets through even if the card was down).
•
cxsc-fail—The CXSC configuration was removed for an existing flow and we are not able to process
it through CXSC; it will be dropped. This should be very unlikely.
•
cxsc-malformed-packet—The packet from CXSC contains an invalid header. For instance, the
header length may not be correct.
Flow Drops:
•
cxsc-request—The CXSC requested to terminate the flow. The actions bit 0 is set.
•
reset-by-cxsc—The CXSC requested to terminate and reset the flow. The actions bit 1 is set.
•
cxsc-fail-close—The flow was terminated because the card is down and the configured policy was
‘fail-close.’
Troubleshooting Problems with the Authentication Proxy
If you are having a problem using the authentication proxy feature, follow these steps to troubleshoot
your configuration and connections.
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 (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.
Procedure
Step 1
Check your configurations.
•
On the ASA, check the output of the
show asp table classify domain cxsc-auth-proxy
command
and make sure there are rules installed and that they are correct.
•
In PRSM, ensure the directory realm is created with the correct credentials and test the connection
to make sure you can reach the authentication server; also ensure that a policy object or objects are
configured for authentication.
Step 2
Check the output of the
show service-policy cxsc
command to see if any packets were proxied.
Step 3
Perform a packet capture on the backplane (
capture
name
interface asa_dataplane
), and check to see
if traffic is being redirected on the correct configured port.You can check the configured port using the
show running-config cxsc
command or the
show asp table classify domain cxsc-auth-proxy
command.
Summary of Contents for ASA 5512-X
Page 5: ...P A R T 1 Service Policies and Access Control ...
Page 6: ......
Page 51: ...P A R T 2 Network Address Translation ...
Page 52: ......
Page 127: ...P A R T 3 Application Inspection ...
Page 128: ......
Page 255: ...P A R T 4 Connection Settings and Quality of Service ...
Page 256: ......
Page 303: ...P A R T 5 Advanced Network Protection ...
Page 304: ......
Page 339: ...P A R T 6 ASA Modules ...
Page 340: ......