EasyManuals Logo
Home>Cisco>Firewall>ASA 5512-X

Cisco ASA 5512-X Cli Configuration Guide

Cisco ASA 5512-X
2164 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #1525 background imageLoading...
Page #1525 background image
1-21
Cisco ASA Series CLI Configuration Guide
Chapter 1 Configuring the ASA CX Module
Troubleshooting the ASA CX Module
When the ASA CX module sends a redirect to a client to authenticate, and that redirect is sent to the
ASA, the ASA sends it to the ASA CX module. In this example, 192.168.18.3 is the interface address
and port 8888 is the authentication proxy port reserved on that interface for the authentication proxy
feature:
DP CXSC Msg: rcvd authentication proxy data from 192.168.18.5:2214 -> 192.168.18.3:8888,
forwarding to cx
When a VPN connection is established on the ASA, and the ASA sends connection information to the
ASA CX module:
CXSC Event: Dumping attributes from the vpn session record
CXSC Event: tunnel->Protocol: 17
CXSC Event: tunnel->ClientVendor: SSL VPN Client
CXSC Event: tunnel->ClientVersion: Cisco AnyConnect VPN Agent for Windows 2.4.1012
CXSC Event: Sending VPN RA session data to CXSC
CXSC Event: sess index: 0x3000
CXSC Event: sess type id: 3
CXSC Event: username: devuser
CXSC Event: domain: CN=Users,DC=test,DC=priv
CXSC Event: directory type: 1
CXSC Event: login time: 1337124762
CXSC Event: nac result: 0
CXSC Event: posture token:
CXSC Event: public IP: 172.23.34.108
CXSC Event: assigned IP: 192.168.17.200
CXSC Event: client OS id: 1
CXSC Event: client OS:
CXSC Event: client type: Cisco AnyConnect VPN Agent for Windows 2.4.1012
CXSC Event: anyconnect data: , len: 0
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:
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.
2. Check the output of the show service-policy cxsc command to see if any packets were proxied.
3. Perform a packet capture on the backplane, and check to see if traffic is being redirected on the
correct configured port. See the “Capturing Module Traffic” section on page 1-20. You can check
the configured port using the show running-config cxsc command or the show asp table classify
domain cxsc-auth-proxy command.
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.

Table of Contents

Other manuals for Cisco ASA 5512-X

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the Cisco ASA 5512-X and is the answer not in the manual?

Cisco ASA 5512-X Specifications

General IconGeneral
BrandCisco
ModelASA 5512-X
CategoryFirewall
LanguageEnglish

Related product manuals