Integration Debugging Information

This section explains the Integration Debugging Information.

Debugging Information for the Cisco Adaptive Security Appliance

This section provides Debugging Information for the Cisco Adaptive Security Appliance

Cisco Adaptive Security Appliance Debugging Commands

The following table lists the debugging commands for the Cisco Adaptive Security Appliance.

Table 1. Cisco Security Appliance Debugging Commands

To

Use the Command

Notes

Show ICMP packet information for pings to the Cisco Adaptive Security Appliance interfaces

debug icmp trace

We strongly recommend that you disable debug messages once you have completed your troubleshooting. To disable ICMP debug messages, use the no debug icmp trace command.

Show messages relating to the certificate validation between IM and Presence Service /Cisco Adaptive Security Appliance or Cisco Adaptive Security Appliance/external domain

debug crypto ca

You can increase log level on the Cisco Adaptive Security Appliance by adding the log level parameter to this command, for example:

debug crypto ca 3

debug crypto ca messages

Displays only debug messages for input and output messages

debug crypto ca transactions

Displays only debug messages for transactions

Show the SIP messages sent through CiscoAdaptive Security Appliance

debug sip

Send log messages to a buffer (for later viewing)

terminal monitor

Enable system log messages

logging on

We strongly recommend that you disable system log messages once you have completed your troubleshooting. To disable system log messages, use the no logging on command.

Send system log messages to a buffer

logging buffer debug

Set system log messages to be sent to Telnet or SSH sessions

logging monitor debug

Designate a (syslog) server to receive the system log messages

logging host interface_name ip_address

  • The interface_name argument specifies the Cisco Adaptive Security Appliance interface through which you access the syslog server.

  • The ip_address argument specifies the IP address of the syslog server.

Ping the Interfaces

ping

Refer to the Troubleshooting section of the CiscoSecurity Appliance Command Line Configuration Guide for details on pinging the Cisco Adaptive Security Appliance interfaces, and also pinging between hosts on different interfaces to ensure that the traffic can pass successfully through the Cisco Adaptive Security Appliance.

You can also ping an interface in ASDM by choosing Tools > Ping.

Note

 

You cannot ping the public IM and Presence Service IP address. However the MAC address of the Cisco Adaptive Security Appliance outside interface should appear in the ARP table (arp –a).

Trace the route of a packet

traceroute

You can also trace the route of a packet in ASDM, choose Tools > Traceroute.

Trace the life span of a packet through the Cisco Adaptive Security Appliance

packet-tracer

You can also trace the life span of a packet in ASDM , choose Tools > Packet Tracer.

Related Information -

TLS Proxy Debugging Commands

Capture Output on Internal and External Interfaces

Procedure

Step 1

Enter configuration mode:

> Enable

> <password>

> configure terminal

Step 2

Define an access-list to specify the traffic to be captured, for example:

access-list cap extended permit ip 10.53.0.0 255.255.0.0 10.53.0.0 255.255.0.0

Step 3

It is recommended that you clear the capture content before starting the tests. Use the command "clear capture in" to clear the internal interface capture, and the command "clear capture out" to clear the external interface capture.

Step 4

Enter this command to capture the packets on the internal interface:

cap in interface inside access-list cap

Step 5

Enter this command to capture the packets on the external interface:

cap out interface outside access-list cap

Step 6

Enter this command to capture TLS specific packets:

capture capture_name type tls-proxy interface interface_name

Step 7

Enter this command to retrieve the packet capture:

copy /pcap capture:in tftp://xx.xx.xx.xx copy /pcap capture:out tftp://xx.xx.xx.xx

Enter this command to copy the output to disk and retrieve using ASDM (choose Actions > File Management > File Transfer):

copy /pcap capture:in disk0:in_1

TLS Proxy Debugging Commands

The following table lists the debugging commands for the TLS Proxy.

Table 2. TLS Proxy Debugging Commands

To

Use the Command(s)

Enable TLS proxy-related debug and syslog output

debug inspect tls-proxy events

debug inspect tls-proxy errors

debug inspect tls-proxy all

Show a TLS proxy session output

show log

Check the active TLS proxy sessions

show tls-proxy

View the detail of the current TLS proxy sessions

(Use when the Cisco Adaptive Security Appliance successfully establishes connections with the IM and Presence Service and the external domain)

show tls-proxy session detail

Access Edge and OCS Server Debugging

This section provides information on Access Edge and OCS Server Debugging.

Initiate Debug Session on OCS/Access Edge

Procedure

Step 1

On the external Access Edge server, choose Start > Administrative Tools > Computer Management.

Step 2

In the left pane, right-click Microsoft Office Communications Server 2007.

Step 3

Choose Logging Tool > New Debug Session.

Step 4

In the Logging Options, choose SIP Stack.

Step 5

For the Level value, choose All.

Step 6

Click Start Logging.

Step 7

When complete, click Stop Logging.

Step 8

Click Analyze Log Files.

Verify DNS Configuration on Access Edge

Procedure

Step 1

On the external Access Edge server, choose Start > Administrative Tools > Computer Management.

Step 2

Right-click on Microsoft Office Communications Server 2007in the left pane.

Step 3

Choose the Block tab.

Step 4

Check that none of the IM and Presence Service managed domains are blocked.

Step 5

Ensure that the following options are selected in the Access Methods pane:

  1. Federate with other domains

  2. Allow discovery of federation partners

Step 6

Check the Access Edge is publishing DNS SRV records.