Logmsgs - SYS Logs

C H A P T E R
Syslog Messages
This chapter lists the messages in numerical order.
Note
When a number is skipped in a sequence, the message is no longer in the ASA code. For information about how to configure logging, SNMP, and NetFlow, see the CLI configuration guide. Table 1-1 lists the message classes and the ranges of message IDs that are associated with each class. The valid range for message IDs is between 100000 and 999999.
Table 1-1
Syslog Message Classes and Associated Message ID Numbers
Class aaa, auth acl appfw bridge ca citrix clst cmgr config cts dap eap, eapoudp eigrp email envmon ha id ids ikev2
Definition User Authentication Access Lists Application Firewall Transparent Firewall PKI Certification Authority Web VPN Clustering Card Management Command Interface Cisco TrustSec Dynamic Access Policies Network Admission Control EIGRP Routing E-mail Proxy Environment Monitoring High Availability (Failover) Identity-based Firewall Intrusion Detection System IKEv2 Toolkit
Syslog Message ID Numbers 109, 113 106 415 110, 220 717 723 747 323 111, 112, 208, 308 776 734 333, 334 336 719 735 101, 102, 103, 104, 105, 210, 311, 709, 727 746 400, 733 750, 751, 752
ASA Series Syslog Messages
1-1
Chapter 1
Syslog Messages
Table 1-1
Syslog Message Classes and Associated Message ID Numbers (continued)
Class ip ipaa ips ipv6 l4tm lb lic nac policy nac settings nap np npssl ospf passwd pp rip rm sch session snmp ssafe ssl sts svc sys td tre vipr vn vpdn vpn vpnc vpnfo vpnlb vxlan
Definition IP Stack IP Address Assignment Intrusion Protection System IPv6 Blacklists, Whitelists, and Graylists Load Balancing Licensing Network Admission Control Policy Network Access Point Network Processor NP SSL OSPF Routing Password Encryption Phone Proxy RIP Routing Resource Manager Smart Call Home User Session SNMP ScanSafe Secure Socket Layer Service Tag Switching SSL VPN Client System Threat Detection Transactional Rule Engine UC-IME VLAN Mapping PPTP and L2TP Sessions IKE and IPsec VPN Client VPN Failover VPN Load Balancing VXLAN
Syslog Message ID Numbers 209, 215, 313, 317, 408 735 400, 401, 420 325 338 728 444 731 713 319 725 318, 409, 503, 613 742 337 107, 312 321 120 106, 108, 201, 202, 204, 302, 303, 304, 305, 314, 405, 406, 407, 500, 502, 607, 608, 609, 616, 620, 703, 710 212 775 725 779 722 199, 211, 214, 216, 306, 307, 315, 414, 604, 605, 606, 610, 612, 614, 615,701, 711, 741 733 780 339 730 213, 403, 603 316, 320, 402, 404, 501, 602, 702, 713, 714, 715 611 720 718 778
Network Admission Control Settings 732
1-2
Chapter 1
Syslog Messages Messages 101001 to 199021
Table 1-1
Syslog Message Classes and Associated Message ID Numbers (continued)
Class webfo webvpn xlate
Definition Web-based Failover Web-based VPN NAT and PAT
Syslog Message ID Numbers 721 716 305
This chapter includes the following sections:

Messages 101001 to 199021, page 1-3 Messages 201002 to 219002, page 1-78 Messages 302003 to 339009, page 1-100 Messages 400000 to 450001, page 1-191 Messages 500001 to 509001, page 1-274 Messages 602101 to 634001, page 1-291 Messages 701001 to 780004, page 1-329
Messages 101001 to 199021

This section includes messages from 101001 to 199021.
101001
Error Message %ASA-1-101001: (Primary) Failover cable OK. Explanation The failover cable is present and functioning correctly. Primary can also be listed as
Secondary for the secondary unit.

Recommended Action None required.
101002
Error Message %ASA-1-101002: (Primary) Bad failover cable. Explanation The failover cable is present, but not functioning correctly. Primary can also be listed as Secondary for the secondary unit. Recommended Action Replace the failover cable.
1-3
Chapter 1 Messages 101001 to 199021
Syslog Messages
101003, 101004
Error Message %ASA-1-101003: (Primary) Failover cable not connected (this unit).
Error Message %ASA-1-101004: (Primary) Failover cable not connected (other unit). Explanation Failover mode is enabled, but the failover cable is not connected to one unit of the failover pair. Primary can also be listed as Secondary for the secondary unit. Recommended Action Connect the failover cable to both units of the failover pair.
101005
Error Message %ASA-1-101005: (Primary) Error reading failover cable status. Explanation The failover cable is connected, but the primary unit is unable to determine its status. Recommended Action Replace the cable.
103001
Error Message %ASA-1-103001: (Primary) No response from other firewall (reason code = code). Explanation The primary unit is unable to communicate with the secondary unit over the failover cable. Primary can also be listed as Secondary for the secondary unit. Table 1-2 lists the reason codes and the descriptions to determine why the failover occurred. Table 1-2 Reason Codes
Reason Code 1
Description The local unit is not receiving the hello packet on the failover LAN interface when LAN failover occurs or on the serial failover cable when serial failover occurs, and declares that the peer is down. An interface did not pass one of the four failover tests, which are as follows: 1) Link Up, 2) Monitor for Network Traffic, 3) ARP, and 4) Broadcast Ping. No proper ACK for 15+ seconds after a command was sent on the serial cable. The failover LAN interface is down, and other data interfaces are not responding to additional interface testing. In addition, the local unit is declaring that the peer is down. The standby peer went down during the configuration synchronization process.
2 3 4 5
Recommended Action Verify that the failover cable is connected correctly and both units have the same hardware, software, and configuration. If the problem persists, contact the Cisco TAC.
1-4
Chapter 1
103002
Error Message %ASA-1-103002: (Primary) Other firewall network interface interface_number OK. Explanation The primary unit has detected that the network interface on the secondary unit is okay. Primary can also be listed as Secondary for the secondary unit. Recommended Action None required.
103003
Error Message %ASA-1-103003: (Primary) Other firewall network interface interface_number failed. Explanation The primary unit has detected a bad network interface on the secondary unit. Primary can also be listed as Secondary for the secondary unit. Recommended Action Check the network connections on the secondary unit and the network hub connection. If necessary, replace the failed network interface.
103004
Error Message %ASA-1-103004: (Primary) Other firewall reports this firewall failed. Reason: reason-string Explanation The primary unit received a message from the secondary unit indicating that the primary
unit has failed. Primary can also be listed as Secondary for the secondary unit. The reason can be one of the following:

Missed poll packets on failover command interface exceeded threshold. LAN failover interface failed. Peer failed to enter Standby Ready state. Failed to complete configuration replication. This firewall's configuration may be out of sync. Failover message transmit failure and no ACK for busy condition received.
Recommended Action Verify the status of the primary unit.
1-5
Syslog Messages
103005
Error Message %ASA-1-103005: (Primary) Other firewall reporting failure. Reason: SSM card failure Explanation The secondary unit has reported an SSM card failure to the primary unit. Primary can also be listed as Secondary for the secondary unit. Recommended Action Verify the status of the secondary unit.
103006
Error Message %ASA-1-103006: (Primary|Secondary) Mate version ver_num is not compatible with ours ver_num Explanation The ASA has detected a peer unit that is running a version that is different than the local unit and is not compatible with the HA Hitless Upgrade feature.
ver_numVersion number
Recommended Action Install the same or a compatible version image on both units.
103007
Error Message %ASA-1-103007: (Primary|Secondary) Mate version ver_num is not identical with ours ver_num Explanation The ASA has detected that the peer unit is running a version that is not identical, but supports Hitless Upgrade and is compatible with the local unit. The system performance may be degraded because the image version is not identical, and the ASA may develop a stability issue if the nonidentical image runs for an extended period.
ver_numVersion number
Recommended Action Install the same image version on both units as soon as possible.
1-6
Chapter 1
104001, 104002
Error Message %ASA-1-104001: (Primary) Switching to ACTIVE (cause: string).
Error Message %ASA-1-104002: (Primary) Switching to STANDBY (cause: string). Explanation You have forced the failover pair to switch roles, either by entering the failover active
command on the standby unit, or the no failover active command on the active unit. Primary can also be listed as Secondary for the secondary unit. Possible values for the string variable are as follows:

state check bad/incomplete config ifc [interface] check, mate is healthier the other side wants me to standby in failed state, cannot be active switch to failed state other unit set to active by CLI config command fail active
Recommended Action If the message occurs because of manual intervention, no action is required. Otherwise, use the cause reported by the secondary unit to verify the status of both units of the pair.
104003
Error Message %ASA-1-104003: (Primary) Switching to FAILED. Explanation The primary unit has failed. Recommended Action Check the messages for the primary unit for an indication of the nature of the
problem (see message 104001). Primary can also be listed as Secondary for the secondary unit.
104004
Error Message %ASA-1-104004: (Primary) Switching to OK. Explanation A previously failed unit reports that it is operating again. Primary can also be listed as Secondary for the secondary unit. Recommended Action None required.
1-7
Syslog Messages
105001
Error Message %ASA-1-105001: (Primary) Disabling failover. Explanation In version 7.x and later, this message may indicate the following: failover has been automatically disabled because of a mode mismatch (single or multiple), a license mismatch (encryption or context), or a hardware difference (one unit has an IPS SSM installed, and its peer has a CSC SSM installed). Primary can also be listed as Secondary for the secondary unit. Recommended Action None required.
105002
Error Message %ASA-1-105002: (Primary) Enabling failover. Explanation You have used the failover command with no arguments on the console, after having previously disabled failover. Primary can also be listed as Secondary for the secondary unit. Recommended Action None required.
105003
Error Message %ASA-1-105003: (Primary) Monitoring on interface interface_name waiting Explanation The ASA is testing the specified network interface with the other unit of the failover pair. Primary can also be listed as Secondary for the secondary unit. Recommended Action None required. The ASA monitors its network interfaces frequently during
normal operation.
105004
Error Message %ASA-1-105004: (Primary) Monitoring on interface interface_name normal Explanation The test of the specified network interface was successful. Primary can also be listed as Secondary for the secondary unit. Recommended Action None required.
1-8
Chapter 1
105005
Error Message %ASA-1-105005: (Primary) Lost Failover communications with mate on interface interface_name. Explanation One unit of the failover pair can no longer communicate with the other unit of the pair. Primary can also be listed as Secondary for the secondary unit. Recommended Action Verify that the network connected to the specified interface is functioning
correctly.
105006, 105007
Error Message %ASA-1-105006: (Primary) Link status Up on interface interface_name.
Error Message %ASA-1-105007: (Primary) Link status Down on interface interface_name. Explanation The results of monitoring the link status of the specified interface have been reported.
Primary can also be listed as Secondary for the secondary unit.

Recommended Action If the link status is down, verify that the network connected to the specified interface is operating correctly.
105008
Error Message %ASA-1-105008: (Primary) Testing interface interface_name. Explanation Testing of a specified network interface has occurred. This testing is performed only if the ASA fails to receive a message from the standby unit on that interface after the expected interval. Primary can also be listed as Secondary for the secondary unit. Recommended Action None required.
105009
Error Message %ASA-1-105009: (Primary) Testing on interface interface_name {Passed|Failed}. Explanation The result (either Passed or Failed) of a previous interface test has been reported. Primary can also be listed as Secondary for the secondary unit. Recommended Action None required if the result is Passed. If the result is Failed, you should check the network cable connection to both failover units, that the network itself is functioning correctly, and verify the status of the standby unit.
1-9
Syslog Messages
105010
Error Message %ASA-3-105010: (Primary) Failover message block alloc failed Explanation Block memory was depleted. This is a transient message and the ASA should recover. Primary can also be listed as Secondary for the secondary unit. Recommended Action Use the show blocks command to monitor the current block memory.
105011
Error Message %ASA-1-105011: (Primary) Failover cable communication failure Explanation The failover cable is not permitting communication between the primary and secondary units. Primary can also be listed as Secondary for the secondary unit. Recommended Action Ensure that the cable is connected correctly.
105020
Error Message %ASA-1-105020: (Primary) Incomplete/slow config replication Explanation When a failover occurs, the active ASA detects a partial configuration in memory.
Normally, this is caused by an interruption in the replication service. Primary can also be listed as Secondary for the secondary unit.
Recommended Action After the ASA detects the failover, the ASA automatically reboots and loads the configuration from flash memory and/or resynchronizes with another ASA. If failovers occurs continuously, check the failover configuration and make sure that both ASAs can communicate with each other.
105021
Error Message %ASA-1-105021: (failover_unit) Standby unit failed to sync due to a locked context_name config. Lock held by lock_owner_name Explanation During configuration synchronization, a standby unit will reload itself if some other process locks the configuration for more than five minutes, which prevents the failover process from applying the new configuration. This can occur when an administrator pages through a running configuration on the standby unit while configuration synchronization is in process. See also the show running-config command in privileged EXEC mode and the pager lines num command in global configuration mode in the Cisco ASA 5500 Series Command Reference. Recommended Action Avoid viewing or modifying the configuration on the standby unit when it first boots up and is in the process of establishing a failover connection with the active unit.
1-10
Chapter 1
105031
Error Message %ASA-1-105031: Failover LAN interface is up Explanation The LAN failover interface link is up. Recommended Action None required.
105032
Error Message %ASA-1-105032: LAN Failover interface is down Explanation The LAN failover interface link is down. Recommended Action Check the connectivity of the LAN failover interface. Make sure that the speed or duplex setting is correct.
105034
Error Message %ASA-1-105034: Receive a LAN_FAILOVER_UP message from peer. Explanation The peer has just booted and sent the initial contact message. Recommended Action None required.
105035
Error Message %ASA-1-105035: Receive a LAN failover interface down msg from peer. Explanation The peer LAN failover interface link is down. The unit switches to active mode if it is
in standby mode.
Recommended Action Check the connectivity of the peer LAN failover interface.
105036
Error Message %ASA-1-105036: dropped a LAN Failover command message. Explanation The ASA dropped an unacknowledged LAN failover command message, indicating a
connectivity problem exists on the LAN failover interface.

Recommended Action Check that the LAN interface cable is connected.
1-11
Syslog Messages
105037
Error Message %ASA-1-105037: The primary and standby units are switching back and forth as the active unit. Explanation The primary and standby units are switching back and forth as the active unit, indicating a LAN failover connectivity problem or software bug exists. Recommended Action Make sure that the LAN interface cable is connected.
105038
Error Message %ASA-1-105038: (Primary) Interface count mismatch Explanation When a failover occurs, the active ASA detects a partial configuration in memory.
Normally, this is caused by an interruption in the replication service. Primary can also be listed as Secondary for the secondary unit.
Recommended Action Once the failover is detected by the ASA, the ASA automatically reboots and loads the configuration from flash memory and/or resynchronizes with another ASA. If failovers occur continuously, check the failover configuration and make sure that both ASAs can communicate with each other.
105039
Error Message %ASA-1-105039: (Primary) Unable to verify the Interface count with mate. Failover may be disabled in mate. Explanation Failover initially verifies that the number of interfaces configured on the primary and
secondary ASAs are the same. This message indicates that the primary ASA is not able to verify the number of interfaces configured on the secondary ASA. This message indicates that the primary ASA is not able to communicate with the secondary ASA over the failover interface. Primary can also be listed as Secondary for the secondary unit.
Recommended Action Verify the failover LAN, interface configuration, and status on the primary and
secondary ASAs. Make sure that the secondary ASA is running the ASA application and that failover is enabled.
1-12
Chapter 1
105040
Error Message %ASA-1-105040: (Primary) Mate failover version is not compatible. Explanation The primary and secondary ASAs should run the same failover software version to act as a failover pair. This message indicates that the secondary ASA failover software version is not compatible with the primary ASA. Failover is disabled on the primary ASA. Primary can also be listed as Secondary for the secondary ASA. Recommended Action Maintain consistent software versions between the primary and secondary ASAs to enable failover.
105042
Error Message %ASA-1-105042: (Primary) Failover interface OK Explanation The LAN failover interface link is up. Explanation The interface used to send failover messages to the secondary ASA is functioning.
Primary can also be listed as Secondary for the secondary ASA.

105043
Error Message %ASA-1-105043: (Primary) Failover interface failed Explanation The LAN failover interface link is down. Recommended Action Check the connectivity of the LAN failover interface. Make sure that the speed or duplex setting is correct.
105044
Error Message %ASA-1-105044: (Primary) Mate operational mode mode is not compatible with my mode mode. Explanation When the operational mode (single or multiple) does not match between failover peers, failover will be disabled. Recommended Action Configure the failover peers to have the same operational mode, and then
reenable failover.
1-13
Syslog Messages
105045
Error Message %ASA-1-105045: (Primary) Mate license (number contexts) is not compatible with my license (number contexts). Explanation When the feature licenses do not match between failover peers, failover will be
disabled.
Recommended Action Configure the failover peers to have the same feature license, and then reenable
failover.
105046
Error Message %ASA-1-105046 (Primary|Secondary) Mate has a different chassis Explanation Two failover units have a different type of chassis. For example, one has a three-slot chassis; the other has a six-slot chassis. Recommended Action Make sure that the two failover units are the same.
105047
Error Message %ASA-1-105047: Mate has a io_card_name1 card in slot slot_number which
is different from my io_card_name2

Explanation The two failover units have different types of cards in their respective slots. Recommended Action Make sure that the card configurations for the failover units are the same.
105048
Error Message %ASA-1-105048: (unit) Mates service module (application) is different from mine (application) Explanation The failover process detected that different applications are running on the service
modules in the active and standby units. The two failover units are incompatible if different service modules are used.

unitPrimary or secondary applicationThe name of the application, such as InterScan Security Card
Recommended Action Make sure that both units have identical service modules before trying to
reenable failover.
1-14
Chapter 1
106001
Error Message %ASA-2-106001: Inbound TCP connection denied from IP_address/port to IP_address/port flags tcp_flags on interface interface_name Explanation An attempt was made to connect to an inside address is denied by the security policy
that is defined for the specified traffic type. The IP address displayed is the real IP address instead of the IP address that appears through NAT. Possible tcp_flags values correspond to the flags in the TCP header that were present when the connection was denied. For example, a TCP packet arrived for which no connection state exists in the ASA, and it was dropped. The tcp_flags in this packet are FIN and ACK. The tcp_flags are as follows:

ACKThe acknowledgment number was received FINData was sent PSHThe receiver passed data to the application RSTThe connection was reset SYNSequence numbers were synchronized to start a connection URGThe urgent pointer was declared valid
106002
Error Message %ASA-2-106002: protocol Connection denied by outbound list acl_ID src inside_address dest outside_address Explanation The specified connection failed because of an outbound deny command. The protocol variable can be ICMP, TCP, or UDP. Recommended Action Use the show outbound command to check outbound lists.
106006
Error Message %ASA-2-106006: Deny inbound UDP from outside_address/outside_port to inside_address/inside_port on interface interface_name. Explanation An inbound UDP packet was denied by the security policy that is defined for the specified traffic type. Recommended Action None required.
1-15
Syslog Messages
106007
Error Message %ASA-2-106007: Deny inbound UDP from outside_address/outside_port to inside_address/inside_port due to DNS {Response|Query}. Explanation A UDP packet containing a DNS query or response was denied. Recommended Action If the inside port number is 53, the inside host probably is set up as a caching name server. Add an access-list command statement to permit traffic on UDP port 53 and a translation entry for the inside host. If the outside port number is 53, a DNS server was probably too slow to respond, and the query was answered by another server.
106010
Error Message %ASA-3-106010: Deny inbound protocol src [interface_name: source_address/source_port] [([idfw_user | FQDN_string], sg_info)] dst [interface_name: dest_address/dest_port}[([idfw_user | FQDN_string], sg_info)] Explanation An inbound connection was denied by your security policy. Recommended Action Modify the security policy if traffic should be permitted. If the message occurs at regular intervals, contact the remote peer administrator.
106011
Error Message %ASA-3-106011: Deny inbound (No xlate) string Explanation The message appears under normal traffic conditions if there are internal users that are accessing the Internet through a web browser. Any time a connection is reset, when the host at the end of the connection sends a packet after the ASA receives the connection reset, this message appears. It can typically be ignored. Recommended Action Prevent this message from getting logged to the syslog server by entering the no logging message 106011 command.
106012
Error Message %ASA-6-106012: Deny IP from IP_address to IP_address, IP options hex. Explanation An IP packet was seen with IP options. Because IP options are considered a security
risk, the packet was discarded.

Recommended Action Contact the remote host system administrator to determine the problem. Check the local site for loose source routing or strict source routing.
1-16
Chapter 1
106013
Error Message %ASA-2-106013: Dropping echo request from IP_address to PAT address IP_address Explanation The ASA discarded an inbound ICMP Echo Request packet with a destination address that corresponds to a PAT global address. The inbound packet is discarded because it cannot specify which PAT host should receive the packet. Recommended Action None required.
106014
Error Message %ASA-3-106014: Deny inbound icmp src interface_name: IP_address [([idfw_user | FQDN_string], sg_info)] dst interface_name: IP_address [([idfw_user | FQDN_string], sg_info)] (type dec, code dec) Explanation The ASA denied any inbound ICMP packet access. By default, all ICMP packets are
denied access unless specifically allowed.

106015
Error Message %ASA-6-106015: Deny TCP (no connection) from IP_address/port to IP_address/port flags tcp_flags on interface interface_name. Explanation The ASA discarded a TCP packet that has no associated connection in the ASA
connection table. The ASA looks for a SYN flag in the packet, which indicates a request to establish a new connection. If the SYN flag is not set, and there is no existing connection, the ASA discards the packet.
Recommended Action None required unless the ASA receives a large volume of these invalid TCP packets. If this is the case, trace the packets to the source and determine the reason these packets were sent.
1-17
Syslog Messages
106016
Error Message %ASA-2-106016: Deny IP spoof from (IP_address) to IP_address on interface interface_name. Explanation A packet arrived at the ASA interface that has a destination IP address of 0.0.0.0 and a
destination MAC address of the ASA interface. In addition, this message is generated when the ASA discarded a packet with an invalid source address, which may include one of the following or some other invalid address:

Loopback network (127.0.0.0) Broadcast (limited, net-directed, subnet-directed, and all-subnets-directed) The destination host (land.c)
To further enhance spoof packet detection, use the icmp command to configure the ASA to discard packets with source addresses belonging to the internal network, because the access-list command has been deprecated and is no longer guaranteed to work correctly.
Recommended Action Determine if an external user is trying to compromise the protected network. Check for misconfigured clients.
106017
Error Message %ASA-2-106017: Deny IP due to Land Attack from IP_address to IP_address Explanation The ASA received a packet with the IP source address equal to the IP destination, and the destination port equal to the source port. This message indicates a spoofed packet that is designed to attack systems. This attack is referred to as a Land Attack. Recommended Action If this message persists, an attack may be in progress. The packet does not
provide enough information to determine where the attack originates.
106018
Error Message %ASA-2-106018: ICMP packet type ICMP_type denied by outbound list acl_ID src inside_address dest outside_address Explanation The outgoing ICMP packet with the specified ICMP from local host (inside_address)
to the foreign host (outside_address) was denied by the outbound ACL list.
1-18
Chapter 1
106020
Error Message %ASA-2-106020: Deny IP teardrop fragment (size = number, offset = number) from IP_address to IP_address Explanation The ASA discarded an IP packet with a teardrop signature containing either a small
offset or fragment overlapping. This is a hostile event that circumvents the ASA or an Intrusion Detection System.
Recommended Action Contact the remote peer administrator or escalate this issue according to your
security policy.
106021
Error Message %ASA-1-106021: Deny protocol reverse path check from source_address to dest_address on interface interface_name Explanation An attack is in progress. Someone is attempting to spoof an IP address on an inbound connection. Unicast RPF, also known as reverse route lookup, detected a packet that does not have a source address represented by a route and assumes that it is part of an attack on your ASA.
This message appears when you have enabled Unicast RPF with the ip verify reverse-path command. This feature works on packets input to an interface; if it is configured on the outside, then the ASA checks packets arriving from the outside. The ASA looks up a route based on the source_address. If an entry is not found and a route is not defined, then this message appears and the connection is dropped. If there is a route, the ASA checks which interface it corresponds to. If the packet arrived on another interface, it is either a spoof or there is an asymmetric routing environment that has more than one path to a destination. The ASA does not support asymmetric routing. If the ASA is configured on an internal interface, it checks static route command statements or RIP, and if the source_address is not found, then an internal user is spoofing their address.
Recommended Action Even though an attack is in progress, if this feature is enabled, no user action
is required. The ASA repels the attack.
106022
Error Message %ASA-1-106022: Deny protocol connection spoof from source_address to dest_address on interface interface_name Explanation A packet matching a connection arrived on a different interface from the interface on
which the connection began. In addition, the ip verify reverse-path command is not configured. For example, if a user starts a connection on the inside interface, but the ASA detects the same connection arriving on a perimeter interface, the ASA has more than one path to a destination. This is known as asymmetric routing and is not supported on the ASA.
1-19
Syslog Messages
An attacker also might be attempting to append packets from one connection to another as a way to break into the ASA. In either case, the ASA shows this message and drops the connection.
Recommended Action Check that the routing is not asymmetric.
106023
Error Message %ASA-4-106023: Deny protocol src [interface_name:source_address/source_port] [([idfw_user|FQDN_string], sg_info)] dst interface_name:dest_address/dest_port [([idfw_user|FQDN_string], sg_info)] [type {string}, code {code}] by access_group acl_ID [0x8ed66b60, 0xf8852875] Explanation A real IP packet was denied by the ACL. This message appears even if you do not have
the log option enabled for an ACL. The IP address is the real IP address instead of the values that display through NAT. Both user identity information and FQDN information is provided for the IP addresses if a matched one is found. The ASA logs either identity information (domain\user) or FQDN (if the username is not available). If the identity information or FQDN is available, the ASA logs this information for both the source and destination.
Recommended Action If messages persist from the same source address, a footprinting or port scanning attempt might be occurring. Contact the remote host administrator.
106024
Error Message %ASA-2-106024: Access rules memory exhausted Explanation The access list compilation process has run out of memory. All configuration information that has been added since the last successful access list was removed from the ASA, and the most recently compiled set of access lists will continue to be used. Recommended Action Access lists, AAA, ICMP, SSH, Telnet, and other rule types are stored and
compiled as access list rule types. Remove some of these rule types so that others can be added.
106025, 106026
Error Message %ASA-6-106025: Failed to determine the security context for the packet:sourceVlan:source_address dest_address source_port dest_port protocol
Error Message %ASA-6-106026: Failed to determine the security context for the packet:sourceVlan:source_address dest_address source_port dest_port protocol Explanation The security context of the packet in multiple context mode cannot be determined. Both messages can be generated for IP packets being dropped in either router and transparent mode. Recommended Action None required.
1-20
Chapter 1
106027
Error Message %ASA-4-106027:Failed to determine the security context for the packet:vlansource Vlan#:ethertype src sourceMAC dst destMAC Explanation The security context of the packet in multiple context mode cannot be determined. This
message is generated for non-IP packets being dropped in transparent mode only.
106100
Error Message %ASA-6-106100: access-list acl_ID {permitted | denied | est-allowed} protocol interface_name/source_address(source_port) (idfw_user, sg_info) interface_name/dest_address(dest_port) (idfw_user, sg_info) hit-cnt number ({first hit | number-second interval}) hash codes Explanation The initial occurrence or the total number of occurrences during an interval are listed.
This message provides more information than message 106023, which only logs denied packets, and does not include the hit count or a configurable level. When an access-list line has the log argument, it is expected that this message ID might be triggered because of a nonsynchronized packet reaching the ASA and being evaluated by the access list. For example, if an ACK packet is received on the ASA (for which no TCP connection exists in the connection table), the ASA might generate message 106100, indicating that the packet was permitted; however, the packet is later correctly dropped because of no matching connection. The following list describes the message values:
permitted | denied | est-allowedThese values specify if the packet was permitted or denied by the ACL. If the value is est-allowed, the packet was denied by the ACL but was allowed for an already established session (for example, an internal user is allowed to accesss the Internet, and responding packets that would normally be denied by the ACL are accepted). protocolTCP, UDP, ICMP, or an IP protocol number. interface_nameThe interface name for the source or destination of the logged flow. The VLAN interfaces are supported. source_addressThe source IP address of the logged flow. The IP address is the real IP address instead of the values that display through NAT. dest_addressThe destination IP address of the logged flow. The IP address is the real IP address instead of the values that display through NAT. source_portThe source port of the logged flow (TCP or UDP). For ICMP, the number after the source port is the message type. idfw_userThe user identity username, including the domain name that is added to the existing syslog when the ASA can find the username for the IP address. sg_infoThe security group tag that is added to the syslog when the ASA can find a security group tag for the IP address. The security group name is displayed with the security group tag, if available.
1-21
Syslog Messages
dest_portThe destination port of the logged flow (TCP or UDP). For ICMP, the number after the destination port is the ICMP message code, which is available for some message types. For type 8, it is always 0. For a list of ICMP message types, see the following URL: http://www.iana.org/assignments/icmp-parameters/icmp-parameters.xml. hit-cnt numberThe number of times this flow was permitted or denied by this ACL entry in the configured time interval. The value is 1 when the ASA generates the first message for this flow. first hitThe first message generated for this flow. number-second intervalThe interval in which the hit count is accumulated. Set this interval using the access-list command with the interval option. hash codesTwo are always printed for the object group ACE and the constituent regular ACE. Values are determined on which ACE that the packet hit. To display these hash codes, enter the show-access list command.
106101
Error Message %ASA-1-106101 The number of ACL log deny-flows has reached limit (number). Explanation If you configured the log option for an ACL deny statement (access-list id deny
command), and a traffic flow matches the ACL statement, the ASA caches the flow information. This message indicates that the number of matching flows that are cached on the ASA exceeds the user-configured limit (using the access-list deny-flow-max command). This message might be generated as a result of a DoS attack.
numberThe limit configured using the access-list deny-flow-max command
106102
Error Message %ASA-6-106102: access-list acl_ID {permitted|denied} protocol for user username interface_name/source_address source_port interface_name/dest_address dest_port hit-cnt number {first hit|number-second interval} hash codes Explanation A packet was either permitted or denied by an access-list that was applied through a
VPN filter. This message is the VPN/AAA filter equivalent of message 106100.
1-22
Chapter 1
106103
Error Message %ASA-4-106103: access-list acl_ID denied protocol for user username interface_name/source_address source_port interface_name/dest_address dest_port hit-cnt number first hit hash codes Explanation A packet was denied by an access-list that was applied through a VPN filter. This
message is the VPN/AAA filter equivalent of message106023.

107001
Error Message %ASA-1-107001: RIP auth failed from IP_address: version=number, type=string, mode=string, sequence=number on interface interface_name Explanation The ASA received a RIP reply message with bad authentication. This message might be
caused by a misconfiguration on the router or the ASA or by an unsuccessful attempt to attack the routing table of the ASA.
Recommended Action This message indicates a possible attack and should be monitored. If you are not familiar with the source IP address listed in this message, change your RIP authentication keys between trusted entities. An attacker might be trying to determine the existing keys.
107002
Error Message %ASA-1-107002: RIP pkt failed from IP_address: version=number on interface interface_name Explanation A router bug, a packet with non-RFC values inside, or a malformed entry may have
caused this message to appear. This should not happen, and may be an attempt to exploit the routing table of the ASA.
Recommended Action This message indicates a possible attack and should be monitored. The packet
has passed authentication, if enabled, and bad data is in the packet. Monitor the situation and change the keys if there are any doubts about the originator of the packet.
108002
Error Message %ASA-2-108002: SMTP replaced string: out source_address in inside_address data: string Explanation A Mail Guard (SMTP) message has been generated by the inspect esmtp command. The ASA has replaced an invalid character in an e-mail address with a space. Recommended Action None required.
1-23
Syslog Messages
108003
Error Message %ASA-2-108003: Terminating ESMTP/SMTP connection; malicious pattern detected in the mail address from source_interface:source_address/source_port to dest_interface:dest_address/dset_port. Data:string Explanation The ASA has detected a malicious pattern in an e-mail address and drops the
connection. An attack is in progress.

108004
Error Message %ASA-4-108004: action_class: action ESMTP req_resp from src_ifc:sip|sport to dest_ifc:dip|dport;further_info Explanation An ESMTP classification is performed on an ESMTP message, and the specified criteria
are satisfied. The configured action is taken.

action_classThe class of action: ESMTP Classification for ESMTP match commands; ESMTP Parameter for parameter commands actionAction taken: Dropped, Dropped connection for, Reset connection for, or Masked header flags for req_respRequest or Response src_ifcSource interface name sip|sportSource IP address or source port dest_ifcDestination interface name dip|dportDestination IP address or destination port further infoOne of the following: For a single match command: matched Class id: match_command (for example, matched Class 1234: match body length 100). For parameter commands: parameter-command: descriptive-message (for example, mail-relay: No Mail Relay allowed)
1-24
Chapter 1
108005
Error Message %ASA-6-108005: action_class: Received ESMTP req_resp from src_ifc:sip|sport to dest_ifc:dip|dport;further_info Explanation An ESMTP classification is performed on an ESMTP message, and the specified criteria
are satisfied. The standalone log action is taken.

action_classThe class of action: ESMTP Classification for ESMTP match commands; ESMTP Parameter for parameter commands req_respRequest or Response src_ifcSource interface name sip|sportSource IP address or source port dest_ifcDestination interface name dip|dportDestination IP address or destination port further infoOne of the following: For a single match command: matched Class id: match_command (for example, matched Class 1234: match body length 100) For parameter commands (commands under the parameter section): parameter-command: descriptive-message (for example, mail-relay: No Mail Relay allowed)
108006
Error Message %ASA-7-108006: Detected ESMTP size violation from src_ifc:sip|sport to dest_ifc:dip|dport;declared size is: decl_size, actual size is act_size. Explanation This event is generated when an ESMTP message size exceeds the size declared in the
RCPT command.

src_ifcSource interface name sip|sportSource IP address or source port dest_ifcDestination interface name dip|dportDestination IP address or destination port decl_sizeDeclared size act_sizeActual size
1-25
Syslog Messages
108007
Error Message %ASA-6-108007: TLS started on ESMTP session between client client-side interface-name: client IP address/client port and server server-side interface-name: server IP address/server port Explanation On an ESMTP connection, the server has responded with a 220 reply code to the client STARTTLS command. The ESMTP inspection engine no longer inspects the traffic on this connection.
client-side interface-nameThe name for the interface that faces the client side client IP addressThe IP address of the client client portThe TCP port number for the client server-side interface-nameThe name for the interface that faces the server side server IP addressThe IP address of the server server portThe TCP port number for the server
Recommended Action Log and review the message. Check whether the ESMTP policy map associated with this connection has the allow-tls action log setting. If not, contact the Cisco TAC.
109001
Error Message %ASA-6-109001: Auth start for user user from inside_address/inside_port to outside_address/outside_port Explanation The ASA is configured for AAA and detects an authentication request by the specified
user.
109002
Error Message %ASA-6-109002: Auth from inside_address/inside_port to outside_address/outside_port failed (server IP_address failed) on interface interface_name. Explanation An authentication request failed because the specified authentication server cannot be contacted by the module. Recommended Action Check that the authentication daemon is running on the specified
authentication server.
1-26
Chapter 1
109003
Error Message %ASA-6-109003: Auth from inside_address to outside_address/outside_port failed (all servers failed) on interface interface_name, so marking all servers ACTIVE again. Explanation No authentication server can be found. Recommended Action Ping the authentication servers from the ASA. Make sure that the daemons are
running.
109005
Error Message %ASA-6-109005: Authentication succeeded for user user from inside_address/inside_port to outside_address/outside_port on interface interface_name. Explanation The specified authentication request succeeded. Recommended Action None required.
109006
Error Message %ASA-6-109006: Authentication failed for user user from inside_address/inside_port to outside_address/outside_port on interface interface_name. Explanation The specified authentication request failed, possibly because of an incorrect password. Recommended Action None required.
109007
Error Message %ASA-6-109007: Authorization permitted for user user from inside_address/inside_port to outside_address/outside_port on interface interface_name. Explanation The specified authorization request succeeded. Recommended Action None required.
1-27
Syslog Messages
109008
Error Message %ASA-6-109008: Authorization denied for user user from outside_address/outside_port to inside_address/ inside_port on interface interface_name. Explanation A user is not authorized to access the specified address, possibly because of an incorrect
password.
109010
Error Message %ASA-3-109010: Auth from inside_address/inside_port to outside_address/outside_port failed (too many pending auths) on interface interface_name. Explanation An authentication request cannot be processed because the server has too many requests
pending.
Recommended Action Check to see if the authentication server is too slow to respond to authentication requests. Enable the Flood Defender feature with the floodguard enable command.
109011
Error Message %ASA-2-109011: Authen Session Start: user 'user', sid number Explanation An authentication session started between the host and the ASA and has not yet
completed.
109012
Error Message %ASA-5-109012: Authen Session End: user 'user', sid number, elapsed number seconds Explanation The authentication cache has timed out. Users must reauthenticate on their next connection. You can change the duration of this timer with the timeout uauth command. Recommended Action None required.
1-28
Chapter 1
109013
Error Message %ASA-3-109013: User must authenticate before using this service Explanation The user must be authenticated before using the service. Recommended Action Authenticate using FTP, Telnet, or HTTP before using the service.
109014
Error Message %ASA-7-109014: A non-Telnet connection was denied to the configured virtual Telnet IP address. Explanation A request to authenticate did not have a corresponding request for authorization. Recommended Action Ensure that both the aaa authentication and aaa authorization command statements are included in the configuration.
109016
Error Message %ASA-3-109016: Can't find authorization ACL acl_ID for user 'user' Explanation The specified on the AAA server for this user does not exist on the ASA. This error can occur if you configure the AAA server before you configure the ASA. The Vendor-Specific Attribute (VSA) on your AAA server might be one of the following values:
acl=acl_ID shell:acl=acl_ID ACS:CiscoSecured-Defined-ACL=acl_ID
Recommended Action Add the ACL to the ASA, making sure to use the same name specified on the
AAA server.
109017
Error Message %ASA-4-109017: User at IP_address exceeded auth proxy connection limit (max) Explanation A user has exceeded the user authentication proxy limit, and has opened too many connections to the proxy. Recommended Action Increase the proxy limit by entering the proxy-limit proxy_limit command, or
ask the user to close unused connections. If the error persists, it may indicate a possible DoS attack.
1-29
Syslog Messages
109018
Error Message %ASA-3-109018: Downloaded ACL acl_ID is empty Explanation The downloaded authorization has no ACEs. This situation might be caused by
misspelling the attribute string ip:inacl# or omitting the access-list command.

junk:junk# 1=permit tcp any any eq junk ip:inacl#1=
Recommended Action Correct the ACL components that have the indicated error on the AAA server.
109019
Error Message %ASA-3-109019: Downloaded ACL acl_ID has parsing error; ACE string Explanation An error occurred during parsing the sequence number NNN in the attribute string
ip:inacl#NNN= of a downloaded authorization. The reasons include: - missing = - contains nonnumeric, nonpace characters between # and = - NNN is greater than 999999999.
ip:inacl# 1 permit tcp any any ip:inacl# 1junk2=permit tcp any any ip:inacl# 1000000000=permit tcp any any
Recommended Action Correct the ACL element that has the indicated error on the AAA server.
109020
Error Message %ASA-3-109020: Downloaded ACL has config error; ACE Explanation One of the components of the downloaded authorization has a configuration error. The
entire text of the element is included in the message. This message is usually caused by an invalid access-list command statement.
Recommended Action Correct the ACL component that has the indicated error on the AAA server.
109021
Error Message %ASA-7-109021: Uauth null proxy error Explanation An internal user authentication error has occurred. Recommended Action None required. However, if this error appears repeatedly, contact the Cisco
TAC.
1-30
Chapter 1
109022
Error Message %ASA-4-109022: exceeded HTTPS proxy process limit Explanation For each HTTPS authentication, the ASA dedicates a process to service the
authentication request. When the number of concurrently running processes exceeds the system-imposed limit, the ASA does not perform the authentication, and this message appears.
109023
Error Message %ASA-3-109023: User from source_address/source_port to dest_address/dest_port on interface outside_interface must authenticate before using this service. Explanation Based on the configured policies, you need to be authenticated before you can use this service port. Recommended Action Authenticate using Telnet, FTP, or HTTP before attempting to use this service
port.
109024
Error Message %ASA-6-109024: Authorization denied from source_address/source_port to dest_address/dest_port (not authenticated) on interface interface_name using protocol Explanation The ASA is configured for AAA and a user attempted to make a TCP connection across the ASA without prior authentication. Recommended Action None required.
109025
Error Message %ASA-6-109025: Authorization denied (acl=acl_ID) for user 'user' from source_address/source_port to dest_address/dest_port on interface interface_name using protocol Explanation The check failed. The check either matched a deny or did not match anything, such as
an implicit deny. The connection was denied by the user acl_ID, which was defined according to the AAA authorization policy on the Cisco Secure Access Control Server (ACS).
1-31
Syslog Messages
109026
Error Message %ASA-3-109026: [aaa protocol] Invalid reply digest received; shared server key may be mismatched. Explanation The response from the AAA server cannot be validated. The configured server key is probably incorrect. This message may be generated during transactions with RADIUS or TACACS+ servers. Recommended Action Verify that the server key, configured using the aaa-server command, is
correct.
109027
Error Message %ASA-4-109027: [aaa protocol] Unable to decipher response message Server = server_IP_address, User = user Explanation The response from the AAA server cannot be validated. The configured server key is probably incorrect. This message may be displayed during transactions with RADIUS or TACACS+ servers. The server_IP_address is the IP address of the relevant AAA server. The user is the user name associated with the connection. Recommended Action Verify that the server key, configured using the aaa-server command, is
correct.
109028
Error Message %ASA-4-109028: aaa bypassed for same-security traffic from ingress_ interface:source_address/source_port to egress_interface:dest_address/dest_port Explanation AAA is being bypassed for same security traffic that matches a configured AAA rule. This can only occur when traffic passes between two interfaces that have the same configured security level, when the same security traffic is permitted, and if the AAA configuration uses the include or exclude syntax. Recommended Action None required.
1-32
Chapter 1
109029
Error Message %ASA-5-109029: Parsing downloaded ACL: string Explanation A syntax error occurred while parsing an access list that was downloaded from a RADIUS server during user authentication.
stringAn error message detailing the syntax error that prevented the access list from parsing correctly
Recommended Action Use the information presented in this message to identify and correct the syntax error in the access list definition within the RADIUS server configuration.
109030
Error Message %ASA-4-109030: Autodetect ACL convert wildcard did not convert ACL access_list source|dest netmask netmask. Explanation A dynamic ACL that is configured on a RADIUS server is not converted by the
mechanism for automatically detecting wildcard netmasks. The problem occurs because this mechanism cannot determine if the netmask is a wildcard or a normal netmask.

access_list The access list that cannot be converted sourceThe source IP address destThe destination IP address netmaskThe subnet mask for the destination or source address in dotted-decimal notation
Recommended Action Check the access list netmask on the RADIUS server for the wildcard configuration. If the netmask is supposed to be a wildcard, and if all access list netmasks on that server are wildcards, then use the wildcard setting for acl-netmask-convert for the AAA server. Otherwise, change the netmask to a normal netmask or to a wildcard netmask that does not contain holes (that is, where the netmask presents consecutive binary 1s. For example, 00000000.00000000.00011111.11111111 or hex 0.0.31.255). If the mask is supposed to be normal and all access list netmasks on that server are normal, then use the normal setting for acl-netmask-convert for the AAA server.
109031
Error Message %ASA-4-109031: NT Domain Authentication Failed: rejecting guest login for username. Explanation A user has tried to authenticate to an NT domain that was configured for guest account
access and the username is not a valid username on the NT server. The connection is denied.
Recommended Action If the user is a valid user, add an account to the NT server. If the user is not allowed access, no action is required.
1-33
Syslog Messages
109032
Error Message %ASA-3-109032: Unable to install ACL access_list, downloaded for user username; Error in ACE: ace. Explanation The ASA received an access control list from a RADIUS server to apply to a user connection, but an entry in the list contains a syntax error. Th euse of a list containing an error could result in the violation of a security policy, so the ASA failed to authenticate the user.
access_listThe name assigned to the dynamic access list as it would appear in the output of the show access-list command usernameThe name of the user whose connection will be subject to this access list aceThe access list entry that was being processed when the error was detected
Recommended Action Correct the access list definition in the RADIUS server configuration.
109033
Error Message %ASA-4-109033: Authentication failed for admin user user from src_IP. Interactive challenge processing is not supported for protocol connections Explanation AAA challenge processing was triggered during authentication of an administrative
connection, but the ASA cannot initiate interactive challenge processing with the client application. When this occurs, the authentication attempt will be rejected and the connection denied.

userThe name of the user being authenticated src_IPThe IP address of the client host protocolThe client connection protocol (SSH v1 or administrative HTTP)
Recommended Action Reconfigure AAA so that challenge processing does not occur for these connection types. This generally means to avoid authenticating these connection types to RSA SecurID servers or to any token-based AAA server via RADIUS.
109034
Error Message %ASA-4-109034: Authentication failed for network user user from src_IP/port to dst_IP/port. Interactive challenge processing is not supported for protocol connections Explanation AAA challenge processing was triggered during authentication of a network connection, but the ASA cannot initiate interactive challenge processing with the client application. When this occurs, the authentication attempt will be rejected and the connection denied.
userThe name of the user being authenticated src_IP/portThe IP address and port of the client host dst_IP/portThe IP address and port of the server to which the client is attempting to connect
1-34
Chapter 1
protocolThe client connection protocol (for example, FTP)
Recommended Action Reconfigure AAA so that challenge processing does not occur for these connection types. This generally means to avoid authenticating these connection types to RSA SecurID servers or to any token-based AAA server via RADIUS.
109036
Error Message %ASA-6-109036: Exceeded 1000 attribute values for the attribute name attribute for user username. Explanation The LDAP response message contains an attribute that has more than 1000 values.
attribute_nameThe LDAP attribute name usernameThe username at login
109037
Error Message %ASA-3-109037: Exceeded 5000 attribute values for the attribute name attribute for user username. Explanation The ASA supports multiple values of the same attribute received from a AAA server. If the AAA server sends a response containing more than 5000 values for the same attribute, then the ASA treats this response message as being malformed and rejects the authentication. This condition has only been seen in lab environments using specialized test tools. It is unlikely that the condition would occur in a real-world production network.
attribute_nameThe LDAP attribute name usernameThe username at login
Recommended Action Capture the authentication traffic between the ASA and AAA server using a protocol sniffer (such as WireShark), then forward the trace file to the Cisco TAC for analysis.
109038
Error Message %ASA-3-109038: Attribute internal-attribute-name value string-from-server from AAA server could not be parsed as a type internal-attribute-name string representation of the attribute name Explanation The AAA subsystem tried to parse an attribute from the AAA server into an internal
representation and failed.
string-from-serverString received from the AAA server, truncated to 40 characters.
1-35
Syslog Messages
typeThe type of the specified attribute
Recommended Action Verify that the attribute is being generated correctly on the AAA server. For additional information, use the debug ldap and debug radius commands.
109039
Error Message %ASA-5-109039: AAA Authentication:Dropping an unsupported IPv6/IP46/IP64 packet from lifc:laddr to fifc:faddr Explanation A packet containing IPv6 addresses or IPv4 addresses translated to IPv6 addresses by
NAT requires AAA authentication or authorization. AAA authentication and authorization do not support IPv6 addresses. The packet is dropped.

lifcThe ingress interface laddrThe source IP address fifcThe egress interface faddrThe destination IP address after NAT translation, if any
109100
Error Message %ASA-6-109100: Received CoA update from coa-source-ip for user username, with session ID: audit-session-id, changing authorization attributes Explanation The ASA has successfully processed the CoA policy update request from coa-source-ip for user username with session id audit-session-id. This syslog message is generated after a change of authorization policy update has been received by the ASA, validated and applied. In a non-error case, this is the only syslog message that is generated when a change of authorization is received and processed.
coa-source-ipOriginating IP address of the change of authorization request usernameUser whose session is being changed audit-session-idThe global ID of the session being modified
109101
Error Message %ASA-6-109101: Received CoA disconnect request from coa-source-ip for user username, with audit-session-id: audit-session-id Explanation The ASA has received a correctly formatted Disconnect-Request for an active VPN
session and has successfully terminated the connection.
coa-source-ipOriginating IP address of the change of authorization request
1-36
Chapter 1
usernameUser whose session is being changed audit-session-idThe global ID of the session being modified
109102
Error Message %ASA-4-109102: Received CoA action-type from coa-source-ip, but cannot find named session audit-session-id Explanation The ASA has received a valid change of authorization request, but the session ID specified in the request does not match any active sessions on the ASA. This could be the result of the change of authorization server attempting to issue a change of authorization on a session that has already been closed by the user.
action-typeThe requested change of authorization action (update or disconnect) coa-source-ipOriginating IP address of the change of authorization request audit-session-idThe global ID of the session being modified
109103
Error Message %ASA-3-109103: CoA action-type from coa-source-ip failed for user username, with session ID: audit-session-id. Explanation The ASA has received a correctly formatted change of authorization request, but was
unable to process it successfully.

action-typeThe requested change of authorization action (update or disconnect) coa-source-ipOriginating IP address of the change of authorization request usernameUser whose session is being changed audit-session-idThe global ID of the session being modified
Recommended Action Investigate the relevant VPN subsystem logs to determine why the updated
attributes could not be applied or why the session could not be terminated.
109104
Error Message %ASA-3-109104: CoA action-type from coa-source-ip failed for user username, session ID: audit-session-id. Action not supported. Explanation The ASA has received a correctly formatted change of authorization request, but did not
process it because the indicated action is not supported by the ASA.
action-typeThe requested change of authorization action (update or disconnect)
1-37
Syslog Messages
coa-source-ipOriginating IP address of the change of authorization request usernameUser whose session is being changed audit-session-idThe global ID of the session being modified
110002
Error Message %ASA-6-110002: Failed to locate egress interface for protocol from src interface:src IP/src port to dest IP/dest port Explanation .An error occurred when the ASA tried to find the interface through which to send the
packet.

protocolThe protocol of the packet src interfaceThe interface from which the packet was received src IPThe source IP address of the packet src portThe source port number dest IPThe destination IP address of the packet dest portThe destination port number
Recommended Action Copy the error message, the configuration, and any details about the events leading up to the error, and contact Cisco TAC.
110003
Error Message %ASA-6-110003: Routing failed to locate next-hop for protocol from src interface:src IP/src port to dest interface:dest IP/dest port Explanation .An error occurred when the ASA tried to find the next hop on an interface routing table.
protocolThe protocol of the packet src interfaceThe interface from which the packet was received src IPThe source IP address of the packet src portThe source port number dest IPThe destination IP address of the packet dest portThe destination port number
Recommended Action Copy the error message, the configuration, and any details about the events leading up to the error, and contact Cisco TAC. During debugging, use the show asp table routing command to view the routing table details.
1-38
Chapter 1
111001
Error Message %ASA-5-111001: Begin configuration: IP_address writing to device Explanation You have entered the write command to store your configuration on a device (either floppy, flash memory, TFTP, the failover standby unit, or the console terminal). The IP_address indicates whether the login was made at the console port or with a Telnet connection. Recommended Action None required.
111002
Error Message %ASA-5-111002: Begin configuration: IP_address reading from device Explanation You have entered the read command to read your configuration from a device (either floppy disk, flash memory, TFTP, the failover standby unit, or the console terminal). The IP_address indicates whether the login was made at the console port or with a Telnet connection. Recommended Action None required.
111003
Error Message %ASA-5-111003: IP_address Erase configuration Explanation You have erased the contents of flash memory by entering the write erase command at the console. The IP_address value indicates whether the login was made at the console port or through a Telnet connection. Recommended Action After erasing the configuration, reconfigure the ASA and save the new configuration. Alternatively, you can restore information from a configuration that was previously saved, either on a floppy disk or on a TFTP server elsewhere on the network.
111004
Error Message %ASA-5-111004: IP_address end configuration: {FAILED|OK} Explanation You have entered the config floppy/memory/ network command or the write floppy/memory/network/standby command. The IP_address value indicates whether the login was made at the console port or through a Telnet connection. Recommended Action None required if the message ends with OK. If the message indicates a failure, try to fix the problem. For example, if writing to a floppy disk, ensure that the floppy disk is not write protected; if writing to a TFTP server, ensure that the server is up.
1-39
Syslog Messages
111005
Error Message %ASA-5-111005: IP_address end configuration: OK Explanation You have exited the configuration mode. The IP_address value indicates whether the login was made at the console port or through a Telnet connection. Recommended Action None required.
111007
Error Message %ASA-5-111007: Begin configuration: IP_address reading from device. Explanation You have entered the reload or configure command to read in a configuration. The
device text can be floppy, memory, net, standby, or terminal. The IP_address value indicates whether the login was made at the console port or through a Telnet connection.
111008
Error Message %ASA-5-111008: User user executed the command string Explanation The user entered any command, with the exception of a show command. Recommended Action None required.
111009
Error Message %ASA-7-111009:User user executed cmd:string Explanation The user entered a command that does not modify the configuration. This message appears only for show commands. Recommended Action None required.
111010
Error Message %ASA-5-111010: User username, running application-name from IP ip addr, executed cmd Explanation A user made a configuration change.
usernameThe user making the configuration change
1-40
Chapter 1
application-nameThe application that the user is running ip addrThe IP address of the management station cmdThe command that the user has executed
111111
Error Message %ASA-1-111111 error_message Explanation A system or infrastructure error has occurred. Recommended Action If the problem persists, contact the Cisco TAC.
112001
Error Message %ASA-2-112001: (string:dec) Clear complete. Explanation A request to clear the module configuration was completed. The source file and line number are identified. Recommended Action None required.
113001
Error Message %ASA-3-113001: Unable to open AAA session. Session limit [limit] reached. Explanation The AAA operation on an IPsec tunnel or WebVPN connection cannot be performed
because of the unavailability of AAA resources. The limit value indicates the maximum number of concurrent AAA transactions.
Recommended Action Reduce the demand for AAA resources, if possible.
1-41
Syslog Messages
113003
Error Message %ASA-6-113003: AAA group policy for user user is being set to policy_name. Explanation The group policy that is associated with the tunnel group is being overridden with a user-specific policy, policy_name. The policy_name is specified using the username command when LOCAL authentication is configured or is returned in the RADIUS CLASS attribute when RADIUS authentication is configured. Recommended Action None required.
113004
Error Message %ASA-6-113004: AAA user aaa_type Successful: server = server_IP_address, User = user Explanation The AAA operation on an IPsec or WebVPN connection has been completed successfully. The AAA types are authentication, authorization, or accounting. The server_IP_address is the IP address of the relevant AAA server. The user is the user name associated with the connection. Recommended Action None required.
113005
Error Message %ASA-6-113005: AAA user authentication Rejected: reason = string: server = server_IP_address, User = user: user IP = user_ip Explanation An authentication or authorization request for a user associated with an IPsec or
WebVPN connection has been rejected. Details of why the request was rejected are provided in the string field. The server_IP_address field is the IP address of the relevant AAA server. The user field is the username associated with the connection. The user_ip field is the IP address of the user who initiated the authentication or authorization request.
113006
Error Message %ASA-6-113006: User user locked out on exceeding number successive failed authentication attempts Explanation A locally configured user is being locked out. This happens when a configured number of consecutive authentication failures have occurred for this user and indicates that all future authentication attempts by this user will be rejected until an administrator unlocks the user using the
1-42
Chapter 1
clear aaa local user lockout command. The user is the user that is now locked, and the number is the consecutive failure threshold configured using the aaa local authentication attempts max-fail command.
Recommended Action Try unlocking the user using the clear_aaa_local_user_lockout command or
adjusting the maximum number of consecutive authentication failures that are tolerated.
113007
Error Message %ASA-6-113007: User user unlocked by administrator Explanation A locally configured user that was locked out after exceeding the maximum number of consecutive authentication failures set by using the aaa local authentication attempts max-fail command has been unlocked by the indicated administrator. Recommended Action None required.
113008
Error Message %ASA-6-113008: AAA transaction status ACCEPT: user = user Explanation The AAA transaction for a user associated with an IPsec or WebVPN connection was completed successfully. The user is the username associated with the connection. Recommended Action None required.
113009
Error Message %ASA-6-113009: AAA retrieved default group policy policy for user user Explanation The authentication or authorization of an IPsec or WebVPN connection has occurred.
The attributes of the group policy that were specified with the tunnel-group or webvpn commands have been retrieved.
113010
Error Message %ASA-6-113010: AAA challenge received for user user from server server_IP_address Explanation The authentication of an IPsec connection has occurred with a SecurID server. The user will be prompted to provide further information before being authenticated.
userThe username associated with the connection
1-43
Syslog Messages
server _IP_addressThe IP address of the relevant AAA server
113011
Error Message %ASA-6-113011: AAA retrieved user specific group policy policy for user user Explanation The authentication or authorization of an IPsec or WebVPN connection has occurred. The attributes of the group policy that was specified with the tunnel-group or webvpn commands have been retrieved. Recommended Action None required.
113012
Error Message %ASA-6-113012: AAA user authentication Successful: local database: user = user Explanation The user associated with a IPsec or WebVPN connection has been successfully authenticated to the local user database.
userThe username associated with the connection
113013
Error Message %ASA-6-113013: AAA unable to complete the request Error: reason = reason: user = user Explanation The AAA transaction for a user associated with an IPsec or WebVPN connection has failed because of an error or has been rejected because of a policy violation.
reasonThe reason details userThe username associated with the connection
1-44
Chapter 1
113014
Error Message %ASA-6-113014: AAA authentication server not accessible: server = server_IP_address: user = user Explanation The device was unable to communicate with the configured AAA server during the AAA transaction associated with an IPsec or WebVPN connection. This may or may not result in a failure of the user connection attempt depending on the backup servers configured in the aaa-server group and the availability of those servers. Recommended Action Verify connectivity with the configured AAA servers.
113015
Error Message %ASA-6-113015: AAA user authentication Rejected: reason = reason: local database: user = user: user IP = user_ip Explanation A request for authentication to the local user database for a user associated with an IPsec or WebVPN connection has been rejected.
reasonThe details of why the request was rejected userThe username associated with the connection user_ip The IP address of the user who initiated the authentication or authorization request
113016
Error Message %ASA-6-113016: AAA credentials rejected: reason = reason: server = server_IP_address: user = user: user IP = user_ip Explanation The AAA transaction for a user associated with an IPsec or WebVPN connection has
failed because of an error or rejected due to a policy violation.

reasonThe details of why the request was rejected server_IP_addressThe IP address of the relevant AAA server userThe username associated with the connection user_ip The IP address of the user who initiated the authentication or authorization request
1-45
Syslog Messages
113017
Error Message %ASA-6-113017: AAA credentials rejected: reason = reason: local database: user = user: user IP = user_ip Explanation The AAA transaction for a user associated with an IPsec or WebVPN connection has failed because of an error or rejected because of a policy violation. This event only appears when the AAA transaction is with the local user database rather than with an external AAA server.
reasonThe details of why the request was rejected userThe username associated with the connection user_ip The IP address of the user who initiated the authentication or authorization request
113018
Error Message %ASA-3-113018: User: user, Unsupported downloaded ACL Entry: ACL_entry, Action: action Explanation An ACL entry in unsupported format was downloaded from the authentication server.
The following list describes the message values:

userUser trying to log in ACL_entryUnsupported ACL entry downloaded from the authentication server actionAction taken when encountering the unsupported ACL entry
Recommended Action The ACL entry on the authentication server has to be changed by the
administrator to conform to the supported ACL entry formats.
113019
Error Message %ASA-4-113019: Group = group, Username = username, IP = peer_address, Session disconnected. Session Type: type, Duration: duration, Bytes xmt: count, Bytes rcv: count, Reason: reason Explanation An indication of when and why the longest idle user is disconnected.
groupGroup name usernameUsername IPPeer address Session TypeSession type (for example, IPsec or UDP) durationConnection duration in hours, minutes, and seconds Bytes xmtNumber of bytes transmitted Bytes rcvNumber of bytes received
1-46
Chapter 1
reasonReason for disconnection: User Requested Lost Carrier Lost Service Idle Timeout Max time exceeded Administrator Reset Administrator Reboot Administrator Shutdown Port Error NAS Error NAS Request NAS Reboot Port unneeded Connection preempted. Indicates that the allowed number of simultaneous (same user) logins has been exceeded. To resolve this problem, increase the number of simultaneous logins or have users only log in once with a given username and password. Port Suspended Service Unavailable Callback User error Host Requested SA Expired IKE Delete Bandwidth Management Error Certificate Expired Phase 2 Mismatch Firewall Mismatch Peer Address Changed ACL Parse Error Phase 2 Error Configuration Error Peer Reconnected Internal Error Crypto map policy not found L2TP initiated VLAN Mapping Error NAC-Policy Error
1-47
Syslog Messages
Dynamic Access Policy terminate Client type not supported Unknown

Recommended Action Unless the reason indicates a problem, then no action is required.
113020
Error Message %ASA-3-113020: Kerberos error: Clock skew with server ip_address greater than 300 seconds Explanation Authentication for an IPsec or WebVPN user through a Kerberos server has failed
because the clocks on the ASA and the server are more than five minutes (300 seconds) apart. When this occurs, the connection attempt is rejected.
ip_addressThe IP address of the Kerberos server
Recommended Action Synchronize the clocks on the ASA and the Kerberos server.
113021
Error Message %ASA-3-113021: Attempted console login failed. User username did NOT have appropriate Admin Rights. Explanation A user has tried to access the management console and was denied. usernameThe username entered by the user
Recommended Action If the user is a newly added admin rights user, check that the service type
(LOCAL or RADIUS authentication server) for that user is set to allow access:

nas-promptAllows login to the console and exec privileges at the required level, but not enable (configuration modification) access adminAllows all access and can be further constrained by command privileges
Otherwise, the user is inappropriately trying to access the management console; the action to be taken should be consistent with company policy for these matters.
113022
Error Message %ASA-2-113022: AAA Marking RADIUS server servername in aaa-server group AAA-Using-DNS as FAILED Explanation The ASA has tried an authentication, authorization, or accounting request to the AAA server and did not receive a response within the configured timeout window. The AAA server will be marked as failed and has been removed from service.
protocolThe type of authentication protocol, which can be one of the following:
1-48
Chapter 1
- RADIUS - TACACS+ - NT - RSA SecurID - Kerberos - LDAP

ip-addrThe IP address of the AAA server tagThe server group name
Recommended Action Verify that the AAA server is online and is accessible from the ASA.
113023
Error Message %ASA-2-113023: AAA Marking protocol server ip-addr in server group tag as ACTIVE Explanation The ASA has reactivated the AAA server that was previously marked as failed. The AAA server is now available to service AAA requests.
protocolThe type of authentication protocol, which can be one of the following: - RADIUS - TACACS+ - NT - RSA SecurID - Kerberos - LDAP ip-addrThe IP address of the AAA server tagThe server group name
113024
Error Message %ASA-5-113024: Group tg: Authenticating type connection from ip with username, user_name, from client certificate Explanation The prefill username feature overrides the username with one derived from the client
certificate for use in AAA.

tgThe tunnel group typeThe type of connection (ssl-client or clientless) ipThe IP address of the connecting user
1-49
Syslog Messages
user_nameThe name extracted from the client certificate for use in AAA
113025
Error Message %ASA-5-113025: Group tg: fields Could not authenticate connection type connection from ip Explanation A username cannot be successfully extracted from the certificate.
tgThe tunnel group fieldsThe DN fields being searched for connection typeThe type of connection (SSL client or clientless) ipThe IP address of the connecting user
Recommended Action The administrator should check that the authentication aaa certificate, ssl
certificate-authentication, and authorization-dn-attributes keywords have been set correctly.
113026
Error Message %ASA-4-113026: Error error while executing Lua script for group tunnel group Explanation An error occurred while extracting a username from the client certificate for use in AAA. This message is only generated when the username-from-certificate use-script option is enabled.
errorError string returned from the Lua environment tunnel groupThe tunnel group attempting to extract a username from a certificate
Recommended Action Examine the script being used by the username-from-certificate use-script
option for errors.
113027
Error Message %ASA-2-113027: Error activating tunnel-group scripts Explanation The script file cannot be loaded successfully. No tunnel groups using the username-from-certificate use-script option work correctly. Recommended Action The administrator should check the script file for errors using ASDM. Use the
debug aaa command to obtain a more detailed error message that may be useful.
1-50
Chapter 1
113028
Error Message %ASA-7-113028: Extraction of username from VPN client certificate has string. [Request num] Explanation The processing request of a username from a certificate is running or has finished.
numThe ID of the request (the value of the pointer to the fiber), which is a monotonically increasing number. stringThe status message, which can one of the following: - been requested - started - finished with error - finished successfully - completed
113029
Error Message %ASA-4-113029: Group group User user IP ipaddr Session could not be established: session limit of num reached Explanation The user session cannot be established because the current number of sessions exceeds
the maximum session load.

Recommended Action Increase the configured limit, if possible, to create a load-balanced cluster.
113030
Error Message %ASA-4-113030: Group group User user IP ipaddr User ACL acl from AAA doesn't exist on the device, terminating connection. Explanation The specified ACL was not found on the ASA.
groupThe name of the group userThe name of the user ipaddrThe IP address aclThe name of the ACL
Recommended Action Modify the configuration to add the specified ACL or to correct the ACL name.
1-51
Syslog Messages
113031
Error Message %ASA-4-113031: Group group User user IP ipaddr AnyConnect vpn-filter filter is an IPv6 ACL; ACL not applied. Explanation The type of ACL to be applied is incorrect. An IPv6 ACL has been configured as an
IPv4 ACL through the vpn-filter command.

groupThe group policy name of the user userThe username ipaddrThe public (not assigned) IP address of the user filterThe name of the VPN filter
Recommended Action Validate the VPN filter and IPv6 VPN filter configurations on the ASA, and the filter parameters on the AAA (RADIUS) server. Make sure that the correct type of ACL is specified.
113032
Error Message %ASA-4-113032: Group group User user IP ipaddr AnyConnect ipv6-vpn-filter filter is an IPv4 ACL; ACL not applied. Explanation The type of ACL to be applied is incorrect. An IPv4 ACL has been configured as an IPv6
ACL through the ipv6-vpn-filter command.

groupThe group policy name of the user userThe username ipaddrThe public (not assigned) IP address of the user filterThe name of the VPN filter
Recommended Action Validate the VPN filter and IPv6 VPN filter configurations on the ASA and the filter parameters on the AAA (RADIUS) server. Make sure that the correct type of ACL is specified.
113033
Error Message %ASA-6-113033: Group group User user IP ipaddr AnyConnect session not allowed. ACL parse error. Explanation The WebVPN session for the specified user in this group is not allowed because the associated ACL did not parse. The user will not be allowed to log in via WebVPN until this error has been corrected.
groupThe group policy name of the user userThe username
1-52
Chapter 1
ipaddrThe public (not assigned) IP address of the user
Recommended Action Correct the WebVPN ACL.
113034
Error Message %ASA-4-113034: Group group User user IP ipaddr User ACL acl from AAA ignored, AV-PAIR ACL used instead. Explanation The specified ACL was not used because a Cisco AV-PAIR ACL was used.
groupThe name of the group userThe name of the user ipaddrThe IP address aclThe name of the ACL
Recommended Action Determine the correct ACL to use and correct the configuration.
113035
Error Message %ASA-4-113035: Group group User user IP ipaddr Session terminated: AnyConnect not enabled or invalid AnyConnect image on the ASA. Explanation The user logged in via the AnyConnect client. The SVC service is not enabled globally,
or the SVC image is invalid or corrupted. The session connection has been terminated.

groupThe name of the group policy with which the user is trying to connect userThe name of the user who is trying to connect iaddrpThe IP address of the user who is trying to connect
Recommended Action Enable the SVC globally using the svc-enable command. Validate the integrity and versions of the SVC images by reloading new images using the svc image command.
113036
Error Message %ASA-4-113036: Group group User user IP ipaddr AAA parameter name value invalid. Explanation The given parameter has a bad value. The value is not shown because it might be very
long.

groupThe name of the group userThe name of the user ipadddrThe IP address
1-53
Syslog Messages
nameThe name of the parameter
Recommended Action Modify the configuration to correct the indicated parameter.
113037
Error Message %ASA-6-113037: Reboot pending, new sessions disabled. Denied user login. Explanation A user was unable to log in to WebVPN because the ASA is in the process of rebooting. Recommended Action None required.
113038
Error Message %ASA-4-113038: Group group User user IP ipaddr Unable to create AnyConnect parent session. Explanation The AnyConnect session was not created for the user in the specified group because of
resource issues. For example, the user may have reached the maximum login limit.

113039
Error Message %ASA-6-113039: Group group User user IP ipaddr AnyConnect parent session started. Explanation The AnyConnect session has started for the user in this group at the specified IP address.
When the user logs in via the AnyConnect login page, the AnyConnect session starts.

1-54
Chapter 1
113040
Error Message %ASA-4-113040: Terminating the VPN connection attempt from attempted group. Reason: This connection is group locked to locked group. Explanation The tunnel group over which the connection is attempted is not the same as the tunnel group set in the group lock.
attempted groupThe tunnel group over which the connection came in locked groupThe tunnel group that the connection is locked or restricted to
Recommended Action Check the group-lock value in the group policy or the user attributes.
114001
Error Message %ASA-1-114001: Failed to initialize 4GE SSM I/O card (error error_string). Explanation The system failed to initialize a 4GE SSM I/O card because of an I2C error or a switch
initialization error.

syslog_idMessage identifier error_stringAn I2C serial bus error or a switch access error, which is a decimal error code. The following are I2C serial bus errors: - I2C_BUS_TRANSACTION_ERROR - I2C_CHKSUM_ERROR - I2C_TIMEOUT_ERROR - I2C_BUS_COLLISION_ERROR - I2C_HOST_BUSY_ERROR - I2C_UNPOPULATED_ERROR - I2C_SMBUS_UNSUPPORT - I2C_BYTE_COUNT_ERROR - I2C_DATA_PTR_ERROR
Recommended Action Perform the following steps: 1. 2. 3. 4.
Log and review the messages and the errors associated with the event. Reboot the software running on the ASA. Power cycle the device. When you turn off the power, make sure you wait several seconds before turning the power on. If the problem persists, contact the Cisco TAC.
1-55
Syslog Messages
114002
Error Message %ASA-1-114002: Failed to initialize SFP in 4GE SSM I/O card (error error_string). Explanation The system failed to initialize an SFP connector in a 4GE SSM I/O card because of an I2C error or a switch initialization error.
syslog_idMessage identifier error_stringAn I2C serial bus error or a switch access error, which is a decimal error code. The following are the I2C serial bus errors: - I2C_BUS_TRANSACTION_ERROR - I2C_CHKSUM_ERROR - I2C_TIMEOUT_ERROR - I2C_BUS_COLLISION_ERROR - I2C_HOST_BUSY_ERROR - I2C_UNPOPULATED_ERROR - I2C_SMBUS_UNSUPPORT - I2C_BYTE_COUNT_ERROR - I2C_DATA_PTR_ERROR
114003
Error Message %ASA-1-114003: Failed to run cached commands in 4GE SSM I/O card (error error_string). Explanation The system failed to run cached commands in a 4GE SSM I/O card because of an I2C
error or a switch initialization error.

syslog_idMessage identifier error_stringAn I2C serial bus error or a switch access error, which is a decimal error code. The following are the I2C serial bus errors: - I2C_BUS_TRANSACTION_ERROR - I2C_CHKSUM_ERROR - I2C_TIMEOUT_ERROR - I2C_BUS_COLLISION_ERROR
1-56
Chapter 1
- I2C_HOST_BUSY_ERROR - I2C_UNPOPULATED_ERROR - I2C_SMBUS_UNSUPPORT - I2C_BYTE_COUNT_ERROR - I2C_DATA_PTR_ERROR

114004
Error Message %ASA-6-114004: 4GE SSM I/O Initialization start. Explanation he user has been notified that a 4GE SSM I/O initialization is starting.
syslog_idMessage identifier
114005
Error Message %ASA-6-114005: 4GE SSM I/O Initialization end. Explanation The user has been notified that an 4GE SSM I/O initialization is finished.
114006
Error Message %ASA-3-114006: Failed to get port statistics in 4GE SSM I/O card (error error_string). Explanation The ASA failed to obtain port statistics in a 4GE SSM I/O card because of an I2C error or a switch initialization error.
syslog_idMessage identifier error_stringAn I2C serial bus error or a switch access error, which is a decimal error code. The following are the I2C serial bus errors:
1-57
Syslog Messages
- I2C_BUS_TRANSACTION_ERROR - I2C_CHKSUM_ERROR - I2C_TIMEOUT_ERROR - I2C_BUS_COLLISION_ERROR - I2C_HOST_BUSY_ERROR - I2C_UNPOPULATED_ERROR - I2C_SMBUS_UNSUPPORT - I2C_BYTE_COUNT_ERROR - I2C_DATA_PTR_ERROR

114007
Error Message %ASA-3-114007: Failed to get current msr in 4GE SSM I/O card (error error_string). Explanation The ASA failed to obtain the current module status register information in a 4GE SSM I/O card because of an I2C error or a switch initialization error.
Recommended Action Perform the following steps: 1. 2.
Log and review the messages and the errors associated with the event. Reboot the software running on the ASA.
1-58
Chapter 1
3. 4.
Power cycle the device. When you turn off the power, make sure you wait several seconds before turning the power on. If the problem persists, contact the Cisco TAC.
114008
Error Message %ASA-3-114008: Failed to enable port after link is up in 4GE SSM I/O card due to either I2C serial bus access error or switch access error. Explanation The ASA failed to enable a port after the link transition to Up state is detected in a 4GE SSM I/O card because of either an I2C serial bus access error or a switch access error.
114009
Error Message %ASA-3-114009: Failed to set multicast address in 4GE SSM I/O card (error error_string). Explanation The ASA failed to set the multicast address in a 4GE SSM I/O card because of an I2C

syslog_idMessage identifier error_stringAn I2C serial bus error or a switch access error, which is a decimal error code. The following are I2C serial bus errors:
1-59
Syslog Messages
- I2C_BUS_TRANSACTION_ERROR - I2C_CHKSUM_ERROR - I2C_TIMEOUT_ERROR - I2C_BUS_COLLISION_ERROR - I2C_HOST_BUSY_ERROR - I2C_UNPOPULATED_ERROR - I2C_SMBUS_UNSUPPORT - I2C_BYTE_COUNT_ERROR - I2C_DATA_PTR_ERROR

114010
Error Message %ASA-3-114010: Failed to set multicast hardware address in 4GE SSM I/O card (error error_string). Explanation The ASA failed to set the multicast hardware address in a 4GE SSM I/O card because of an I2C error or a switch initialization error.
syslog_idMessage identifier error_stringAn I2C serial bus error or a switch access error, which is a decimal error code. The following are I2C serial bus errors: - I2C_BUS_TRANSACTION_ERROR - I2C_CHKSUM_ERROR - I2C_TIMEOUT_ERROR - I2C_BUS_COLLISION_ERROR - I2C_HOST_BUSY_ERROR - I2C_UNPOPULATED_ERROR - I2C_SMBUS_UNSUPPORT - I2C_BYTE_COUNT_ERROR - I2C_DATA_PTR_ERROR - I2C_DATA_PTR_ERROR
Recommended Action Perform the following steps: 1.
Log and review the messages and the errors associated with the event.
1-60
Chapter 1
2. 3. 4.
Reboot the software running on the ASA. Power cycle the device. When you turn off the power, make sure you wait several seconds before turning the power on. If the problem persists, contact the Cisco TAC.
114011
Error Message %ASA-3-114011: Failed to delete multicast address in 4GE SSM I/O card (error error_string). Explanation The ASA failed to delete the multicast address in a 4GE SSM I/O card because of either
an I2C error or a switch initialization error.

114012
Error Message %ASA-3-114012: Failed to delete multicast hardware address in 4GE SSM I/O card (error error_string). Explanation The ASA failed to delete the multicast hardware address in a 4GE SSM I/O card because of an I2C error or a switch initialization error.
1-61
Syslog Messages
error_stringAn I2C serial bus error or a switch access error, which is a decimal error code. The following are I2C serial bus errors: - I2C_BUS_TRANSACTION_ERROR - I2C_CHKSUM_ERROR - I2C_TIMEOUT_ERROR - I2C_BUS_COLLISION_ERROR - I2C_HOST_BUSY_ERROR - I2C_UNPOPULATED_ERROR - I2C_SMBUS_UNSUPPORT - I2C_BYTE_COUNT_ERROR - I2C_DATA_PTR_ERROR
114013
Error Message %ASA-3-114013: Failed to set mac address table in 4GE SSM I/O card (error error_string). Explanation The ASA failed to set the MAC address table in a 4GE SSM I/O card because of an I2C

1-62
Chapter 1
2. 3. 4.
114014
Error Message %ASA-3-114014: Failed to set mac address in 4GE SSM I/O card (error error_string). Explanation The ASA failed to set the MAC address in a 4GE SSM I/O card because of an I2C error
or a switch initialization error.

114015
Error Message %ASA-3-114015: Failed to set mode in 4GE SSM I/O card (error error_string). Explanation The ASA failed to set individual or promiscuous mode in a 4GE SSM I/O card because of an I2C error or a switch initialization error.
1-63
Syslog Messages
error_stringAn I2C serial bus error or a switch access error, which is a decimal error code. The following are I2C serial bus errors: - I2C_BUS_TRANSACTION_ERROR - I2C_CHKSUM_ERROR - I2C_TIMEOUT_ERROR - I2C_BUS_COLLISION_ERROR - I2C_HOST_BUSY_ERROR - I2C_UNPOPULATED_ERROR - I2C_SMBUS_UNSUPPORT - I2C_BYTE_COUNT_ERROR - I2C_DATA_PTR_ERROR
114016
Error Message %ASA-3-114016: Failed to set multicast mode in 4GE SSM I/O card (error error_string). Explanation The ASA failed to set the multicast mode in a 4GE SSM I/O card because of an I2C error or a switch initialization error.
1-64
Chapter 1
2. 3. 4.
114017
Error Message %ASA-3-114017: Failed to get link status in 4GE SSM I/O card (error error_string). Explanation The ASA failed to obtain link status in a 4GE SSM I/O card because of an I2C serial
bus access error or a switch access error.

Recommended Action Perform the following steps: 1. 2. 3. 4. 5.
Notify the system administrator. Log and review the messages and the errors associated with the event. Reboot the software running on the ASA. Power cycle the device. When you turn off the power, make sure you wait several seconds before turning the power on. If the problem persists, contact the Cisco TAC.
114018
Error Message %ASA-3-114018: Failed to set port speed in 4GE SSM I/O card (error error_string). Explanation The ASA failed to set the port speed in a 4GE SSM I/O card because of an I2C error or a switch initialization error.
1-65
Syslog Messages
error_stringAn I2C serial bus error or a switch access error, which is a decimal error code. The following are the I2C serial bus errors: - I2C_BUS_TRANSACTION_ERROR - I2C_CHKSUM_ERROR - I2C_TIMEOUT_ERROR - I2C_BUS_COLLISION_ERROR - I2C_HOST_BUSY_ERROR - I2C_UNPOPULATED_ERROR - I2C_SMBUS_UNSUPPORT - I2C_BYTE_COUNT_ERROR - I2C_DATA_PTR_ERROR
114019
Error Message %ASA-3-114019: Failed to set media type in 4GE SSM I/O card (error error_string). Explanation The ASA failed to set the media type in a 4GE SSM I/O card because of an I2C error or a switch initialization error.
1-66
Chapter 1
2. 3. 4.
114020
Error Message %ASA-3-114020: Port link speed is unknown in 4GE SSM I/O card. Explanation The ASA cannot detect the port link speed in a 4GE SSM I/O card. Recommended Action Perform the following steps: 1. 2. 3. 4.
Log and review the messages associated with the event. Reset the 4GE SSM I/O card and observe whether or not the software automatically recovers from the event. If the software does not recover automatically, power cycle the device. When you turn off the power, make sure you wait several seconds before you turn the power on. If the problem persists, contact the Cisco TAC.
114021
Error Message %ASA-3-114021: Failed to set multicast address table in 4GE SSM I/O card due to error. Explanation The ASA failed to set the multicast address table in the 4GE SSM I/O card because of either an I2C serial bus access error or a switch access error.
errorA switch access error (a decimal error code) or an I2C serial bus error. Possible I2C serial bus errors include: - I2C_BUS_TRANSACTION_ERROR - I2C_CHKSUM_ERROR - I2C_TIMEOUT_ERROR - I2C_BUS_COLLISION_ERROR - I2C_HOST_BUSY_ERROR - I2C_UNPOPULATED_ERROR - I2C_SMBUS_UNSUPPORT - I2C_BYTE_COUNT_ERROR - I2C_DATA_PTR_ERROR
Log and review the messages associated with the event. Try to reboot the ASA.
1-67
Syslog Messages
3. 4.
If the software does not recover automatically, power cycle the device. When you turn off the power, make sure you wait several seconds before you turn the power on. If the problem persists, contact the Cisco TAC.
114022
Error Message %ASA-3-114022: Failed to pass broadcast traffic in 4GE SSM I/O card due to error_string Explanation The ASA failed to pass broadcast traffic in the 4GE SSM I/O card because of a switch
access error.
error_stringA switch access error, which will be a decimal error code
Recommended Action Perform the following steps: 1. 2. 3.
Log the message and errors surrounding the event. Retrieve the ssm4ge_dump file from the compact flash, and send it to Cisco TAC. Contact Cisco TAC with the information collected in Steps 1 and 2.
Note
The 4GE SSM will be automatically reset and recover.
114023
Error Message %ASA-3-114023: Failed to cache/flush mac table in 4GE SSM I/O card due to error_string. Explanation A failure to cache or flush the MAC table in a 4GE SSM I/O card occurred because of an I2C serial bus access error or a switch access error. This message rarely occurs.
error_string Either an I2C serial bus error (see the second bullet for possible values) or a switch access error (which is a decimal error code). I2C serial bus errors are as follows: I2C_BUS_TRANSACTION_ERROR I2C_CHKSUM_ERROR I2C_TIMEOUT_ERROR I2C_BUS_COLLISION_ERROR I2C_HOST_BUSY_ERROR I2C_UNPOPULATED_ERROR I2C_SMBUS_UNSUPPORT I2C_BYTE_COUNT_ERROR
1-68
Chapter 1
I2C_DATA_PTR_ERROR
Log the syslog message and the errors surrounding the event. Try to software reboot the ASA. Power cycle the ASA.
Note
When you turn off the power, make sure that you wait several seconds before powering on again. After you complete steps 1-3, if the problem persists, contact the Cisco TAC and provide the information described in step 1. You may need to RMA the ASA.
115000
Error Message %ASA-2-115000: Critical assertion in process: process name fiber: fiber name, component: component name, subcomponent: subcomponent name, file: filename, line: line number, cond: condition Explanation The critical assertion has gone off and is used during development in checked builds only, but never in production builds.
process name The name of the process fiber name The name of the fiber component nameThe name of the specified component subcomponent nameThe name of the specified subcomponent filenameThe name of the specified file line numberThe line number for the specified line conditionThe specified condition
Recommended Action A high priority defect should be filed, the reason for the assertion should be investigated, and the problem corrected.
115001
Error Message %ASA-3-115001: Error in process: process name fiber: fiber name, component: component name, subcomponent: subcomponent name, file: filename, line: line number, cond: condition Explanation An error assertion has gone off and is used during development in checked builds only,
but never in production builds.

process name The name of the process fiber name The name of the fiber component nameThe name of the specified component subcomponent nameThe name of the specified subcomponent
1-69
Syslog Messages
filenameThe name of the specified file line numberThe line number for the specified line conditionThe specified condition
Recommended Action A defect should be filed, the reason for the assertion should be investigated, and the problem fixed.
115002
Error Message %ASA-4-115002: Warning in process: process name fiber: fiber name, component: component name, subcomponent: subcomponent name, file: filename, line: line number, cond: condition Explanation A warning assertion has gone off and is used during development in checked builds
only, but never in production builds.

process name The name of the process fiber name The name of the fiber component nameThe name of the specified component subcomponent nameThe name of the specified subcomponent filenameThe name of the specified file line numberThe line number for the specified line conditionThe specified condition
Recommended Action The reason for the assertion should be investigated and if a problem is found,
a defect should be filed, and the problem corrected.
120001
Error Message %ASA-5-120001: Smart Call-Home Module is started. Explanation The Smart Call-Home module started successfully after system bootup and failover in a stable state, and is ready to process Smart-Call Home events. Recommended Action None required.
120002
Error Message %ASA-5-120002: Smart Call-Home Module is terminated. Explanation When the Smart Call-Home module is disabled, it is then terminated. Recommended Action None required.
1-70
Chapter 1
120003
Error Message %ASA-6-120003: Process event group title Explanation The Smart Call-Home module retrieved an event from the queue to process.
groupThe event group, which may be the following: inventory, configuration, diagnostic, environment, snapshot, telemetry, threat, and test. titleThe event title
120004
Error Message %ASA-4-120004: Event group title is dropped. Reason reason Explanation A Smart Call-Home event was dropped. The event may have been dropped because of an internal error, the event queue is full, or the Smart Call-Home module was disabled after the message was generated, but before it was processed.
groupThe event group, which can be any of the following: inventory, configuration, diagnostic, environment, snapshot, telemetry, threat, and test. titleThe event title reasonThe drop reason, which can any of the following: Internal ErrorVarious internal system errors occurred, such as being out of memory or parsing a CLI failed. Queue FullThe number of events reached the configured limit. CancelledThe event was cancelled because the Smart Call-Home module is disabled.
Recommended Action If the drop reason is Queue Full, try to increase the event queue size and the
rate-limit configuration to avoid event queue buildup. If the drop reason is Internal Error, turn on debugging by entering the debug sch fail command to obtain more detailed debugging information.
120005
Error Message %ASA-4-120005: Message group to destination is dropped. Reason reason Explanation A Smart Call-Home message was dropped. The message may have been dropped
because of an internal error, a network error, or the Smart Call-Home module was disabled after the message was generated, but before it was delivered.

groupThe event group, which can be any of the following: inventory, configuration, diagnostic, environment, snapshot, telemetry, threat, and test. destinationThe e-mail or URL destination reasonThe drop reason, which can any of the following:
1-71
Syslog Messages
Internal ErrorVarious internal system errors occurred. Delivery FailedThe packets cannot be delivered because a network error occurred. CancelledThe event was cancelled because the Smart Call-Home module is disabled.
Recommended Action If the drop reason is Delivery Failed, the message is dropped after three unsuccessful retransmissions, or because the error is local (such as no route to destination). Search message 120006 for the delivery failure reason, or turn on debugging by entering the debug sch fail command to obtain more detailed debugging information.
120006
Error Message %ASA-4-120006: Delivering message group to destination failed. Reason reason Explanation An error occurred while the Smart Call Home module tried to deliver a message. The
error may be transient. The message is not dropped when message 120006 is generated. The message may be queued for retransmission. The message is only dropped when message 120005 is generated.

groupThe event group, which can be any of the following: inventory, configuration, diagnostic, environment, snapshot, telemetry, threat, and test destinationThe e-mail or URL destination reasonThe failure reason
Recommended Action Check the error reason in the message. If the reason is NO_ROUTE, INVALID_ADDRESS, or INVALID_URL, check the system configuration, DNS, and the name setting.
120007
Error Message %ASA-6-120007: Message group to destination delivered. Explanation A Smart Call Home message was successfully delivered.
groupThe event group, which can be any of the following: inventory, configuration, diagnostic, environment, snapshot, telemetry, threat, and test destinationThe e-mail or URL destination
1-72
Chapter 1
120008
Error Message %ASA-5-120008: SCH client client is activated. Explanation The Smart Call Home module is enabled, an event group is also enabled, and that event group is subscribed to by at least one active profile. If these conditions are met, then all clients of that group will be activated.
clientThe name of the Smart Call Home client
120009
Error Message %ASA-5-120009: SCH client client is deactivated. Explanation The Smart Call Home module is disabled, an event group is enabled, or an event group
is no longer subscribed to by any active profile. If these conditions are met, clients of that event group will be deactivated.
clientThe name of the Smart Call Home client
120010
Error Message %ASA-3-120010: Notify command command to SCH client client failed. Reason reason. Explanation The Smart Call Home module notified Smart Call Home clients of certain events
through the callback function. If the client does not interpret the command correctly, does not understand the command, or cannot process the command, an error will be returned.

commandENABLE, DISABLE, or READY clientThe name of the Smart Call Home client reasonThe reason for failure
Recommended Action Turn on debugging by entering the debug sch fail command to obtain more detailed debugging information.
1-73
Syslog Messages
120012
Error Message %ASA-5-120012: User username chose to choice call-home anonymous reporting at the prompt. Explanation The administrator was notified that a user has responded to the Smart Call Home prompt
to enable, disable, or postpone anonymous reporting.

usernameThe user who responded to the prompt choiceThe available entries are enable, disable, or postpone
Recommended Action To enable anonymous reporting in the future, enter the call-home reporting
anonymous command. To disable anonymous reporting, enter the no call-home reporting anonymous command.
199001
Error Message %ASA-5-199001: Reload command executed from Telnet (remote IP_address). Explanation The address of the host that is initiating an ASA reboot with the reload command has been recorded. Recommended Action None required.
199002
Error Message %ASA-6-199002: startup completed. Beginning operation. Explanation The ASA finished its initial boot and the flash memory reading sequence, and is ready to begin operating normally.
Note
You cannot block this message by using the no logging message command.
199003
Error Message %ASA-6-199003: Reducing link MTU dec. Explanation The ASA received a packet from the outside network that uses a larger MTU than the
inside network. The ASA then sent an ICMP message to the outside host to negotiate an appropriate MTU. The log message includes the sequence number of the ICMP message.
1-74
Chapter 1
199005
Error Message %ASA-6-199005: Startup begin Explanation The ASA started. Recommended Action None required.
199010
Error Message %ASA-1-199010: Signal 11 caught in process/fiber(rtcli async executor process)/(rtcli async executor) at address 0xf132e03b, corrective action at 0xca1961a0 Explanation The system has recovered from a serious error. Recommended Action Contact the Cisco TAC.
199011
Error Message %ASA-2-199011: Close on bad channel in process/fiber process/fiber, channel ID p, channel state s process/fiber name of the process/fiber that caused the bad channel close operation. Explanation An unexpected channel close condition has been detected.
pThe channel ID process/fiberThe name of the process/fiber that caused the bad channel close operation sThe channel state
Recommended Action Contact the Cisco TAC and attach a log file.
199012
Error Message %ASA-1-1199012: Stack smash during new_stack_call in process/fiber process/fiber, call target f, stack size s, process/fiber name of the process/fiber that caused the stack smash Explanation A stack smash condition has been detected.
fThe target of the new_stack_call process/fiberThe name of the process/fiber that caused the stack smash sThe new stack size specified in new_stack_call
Recommended Action Contact the Cisco TAC and attach a log file.
1-75
Syslog Messages
199013
Error Message %ASA-1-199013: syslog Explanation A variable syslog was generated by an assistive process.
syslogThe alert syslog passed verbatim from an external process
Recommended Action Contact the Cisco TAC.
199014
syslogThe critical syslog passed verbatim from an external process
199015
syslogThe error syslog passed verbatim from an external process
199016
syslogThe warning syslog passed verbatim from an external process
1-76
Chapter 1
199017
syslogThe notification syslog passed verbatim from an external process
199018
syslogThe informational syslog passed verbatim from an external process
199019
syslogThe debugging syslog passed verbatim from an external process
199020
Error Message %ASA-2-199020: System memory utilization has reached X%. System will reload if memory usage reaches the configured trigger level of Y%. Explanation The system memory utilization has reached 80% of the system memory watchdog
facility's configured value.

Recommended Action Reduce system memory utilization by reducing traffic load, removing traffic inspections, reducing the number of ACL entries, and so on. If a memory leak is suspected, contact Cisco TAC.
1-77
Syslog Messages
199021
Error Message %ASA-1-199021: System memory utilization has reached the configured watchdog trigger level of Y%. System will now reload Explanation .The system memory utilization has reached 100% of the system memory watchdog facility's configured value. The system will automatically reload. Recommended Action Reduce system memory utilization by reducing traffic load, removing traffic inspections, reducing the number of ACL entries, and so on. If a memory leak is suspected, contact Cisco TAC.

201002
Error Message %ASA-3-201002: Too many TCP connections on {static|xlate} global_address! econns nconns Explanation The maximum number of TCP connections to the specified global address was
exceeded.

econnsThe maximum number of embryonic connections nconnsThe maximum number of connections permitted for the static or xlate global address
Recommended Action Use the show static or show nat command to check the limit imposed on connections to a static address. The limit is configurable.
201003
Error Message %ASA-2-201003: Embryonic limit exceeded nconns/elimit for outside_address/outside_port (global_address) inside_address/inside_port on interface interface_name Explanation The number of embryonic connections from the specified foreign address with the
specified static global address to the specified local address exceeds the embryonic limit. When the limit on embryonic connections to the ASA is reached, the ASA attempts to accept them anyway, but puts a time limit on the connections. This situation allows some connections to succeed even if the ASA is very busy. This message indicates a more serious overload than message 201002, which can be caused by a SYN attack, or by a very heavy load of legitimate traffic.
nconnsThe maximum number of embryonic connections received
1-78
Chapter 1
elimitThe maximum number of embryonic connections specified in the static or nat command
Recommended Action Use the show static command to check the limit imposed on embryonic connections to a static address.
201004
Error Message %ASA-3-201004: Too many UDP connections on {static|xlate} global_address!udp connections limit Explanation The maximum number of UDP connections to the specified global address was
exceeded.
udp conn limitThe maximum number of UDP connections permitted for the static address or translation
Recommended Action Use the show static or show nat command to check the limit imposed on connections to a static address. You can configure the limit.
201005
Error Message %ASA-3-201005: FTP data connection failed for IP_address IP_address Explanation The ASA cannot allocate a structure to track the data connection for FTP because of insufficient memory. Recommended Action Reduce the amount of memory usage or purchase additional memory.
201006
Error Message %ASA-3-201006: RCMD backconnection failed for IP_address/port. Explanation The ASA cannot preallocate connections for inbound standard output for rsh commands
because of insufficient memory.

Recommended Action Check the rsh client version; the ASA only supports the Berkeley rsh client version. You can also reduce the amount of memory usage, or purchase additional memory.
1-79
Syslog Messages
201008
Error Message %ASA-3-201008: Disallowing new connections. Explanation You have enabled TCP system log messaging and the syslog server cannot be reached, or when using the ASA syslog server (PFSS) and the disk on the Windows NT system is full, or when the auto-update timeout is configured and the auto-update server is not reachable. Recommended Action Disable TCP syslog messaging. If using PFSS, free up space on the Windows
NT system where PFSS resides. Also, make sure that the syslog server is up and you can ping the host from the ASA console. Then restart TCP system message logging to allow traffic. If the Auto Update Server has not been contacted for a certain period of time, enter the [no] auto-update timeout period command to have it stop sending packets.
201009
Error Message %ASA-3-201009: TCP connection limit of number for host IP_address on interface_name exceeded Explanation The maximum number of connections to the specified static address was exceeded.
numberThe maximum of connections permitted for the host IP_addressThe host IP address interface_nameThe name of the interface to which the host is connected
Recommended Action Use the show static and show nat commands to check the limit imposed on connections to an address. The limit is configurable.
201010
Error Message %ASA-6-201010: Embryonic connection limit exceeded econns/limit for dir packet from source_address/source_port to dest_address/dest_port on interface interface_name Explanation An attempt to establish a TCP connection failed because of an exceeded embryonic
connection limit, which was configured with the set connection embryonic-conn-max MPC command for a traffic class.

econnsThe current count of embryonic connections associated to the configured traffic class limitThe configured embryonic connection limit for the traffic class dirinput: The first packet that initiates the connection is an input packet on the interface interface_name output: The first packet that initiates the connection is an output packet on the interface interface_name source_address/source_portThe source real IP address and the source port of the packet initiating the connection
1-80
Chapter 1
dest_address/dest_portThe destination real IP address and the destination port of the packet initiating the connection interface_nameThe name of the interface on which the policy limit is enforced
201011
Error Message %ASA-3-201011: Connection limit exceeded cnt/limit for dir packet from sip/sport to dip/dport on interface if_name. Explanation A new connection through the ASA resulted in exceeding at least one of the configured
maximum connection limits. This message applies both to connection limits configured using a static command, or to those configured using Cisco Modular Policy Framework. The new connection will not be allowed through the ASA until one of the existing connections is torn down, which brings the current connection count below the configured maximum.

cntCurrent connection count limitConfigured connection limit dirDirection of traffic, inbound or outbound sipSource real IP address sportSource port dipDestination real IP address dportDestination port if_nameName of the interface on which the traffic was received
201012
Error Message %ASA-6-201012: Per-client embryonic connection limit exceeded curr num/limit for [input|output] packet from IP_address/ port to ip/port on interface interface_name Explanation An attempt to establish a TCP connection failed because the per-client embryonic
connection limit was exceeded. By default, this message is rate limited to 1 message every 10 seconds.

curr numThe current number limitThe configured limit [input|output]Input or output packet on interface interface_name IP_addressReal IP address portTCP or UDP port
1-81
Syslog Messages
interface_nameThe name of the interface on which the policy is applied
Recommended Action When the limit is reached, any new connection request will be proxied by the
ASA to prevent a SYN flood attack. The ASA will only connect to the server if the client is able to finish the three-way handshake. This usually does not affect the end user or the application. However, if this creates a problem for any application that has a legitimate need for a higher number of embryonic connections, you can adjust the setting by entering the set connection per-client-embryonic-max command.
201013
Error Message %ASA-3-201013: Per-client connection limit exceeded curr num/limit for [input|output] packet from ip/port to ip/port on interface interface_name Explanation A connection was rejected because the per-client connection limit was exceeded.
curr numThe current number limitThe configured limit [input|output]The input or output packet on interface interface_name ipThe real IP address portThe TCP or UDP port interface_nameThe name of the interface on which the policy is applied
Recommended Action When the limit is reached, any new connection request will be silently dropped. Normally an application will retry the connection, which will cause a delay or even a timeout if all retries also fail. If an application has a legitimate need for a higher number of concurrent connections, you can adjust the setting by entering the set connection per-client-max command.
202001
Error Message %ASA-3-202001: Out of address translation slots! Explanation The ASA has no more address translation slots available. Recommended Action Check the size of the global pool compared to the number of inside network clients. A PAT address may be necessary. Alternatively, shorten the timeout interval of translates and connections. This error message can also be caused by insufficient memory; reduce the amount of memory usage, or purchase additional memory, if possible.
1-82
Chapter 1
202005
Error Message %ASA-3-202005: Non-embryonic in embryonic list outside_address/outside_port inside_address/inside_port Explanation A connection object (xlate) is in the wrong list. Recommended Action Contact the Cisco TAC.
202010
Error Message %ASA-3-202010: [NAT | PAT] pool exhausted for pool-name, port range [1-511 | 512-1023 | 1024-65535]. Unable to create protocol connection from in-interface:src-ip/src-port to out-interface:dst-ip/dst-port
pool-nameThe name of the NAT or PAT pool protocolThe protocol used to create the connection in-interfaceThe ingress interface src-ipThe source IP address src-portThe source port out-interfaceThe egress interface dest-ipThe destination IP address dst-portThe destination port
Explanation The ASA has no more address translation pools available. Recommended Action Use the show nat pool and show nat detail commands to determine why all
addresses and ports in the pool are used up. If this occurs under normal conditions, then add additional IP addresses to the NAT/PAT pool.
208005
Error Message %ASA-3-208005: (function:line_num) clear command return code Explanation The ASA received a nonzero value (an internal error) when attempting to clear the
configuration in flash memory. The message includes the reporting subroutine filename and line number.
Recommended Action For performance reasons, the end host should be configured not to inject IP fragments. This configuration change is probably because of NFS. Set the read and write size equal to the interface MTU for NFS.
1-83
Syslog Messages
209003
Error Message %ASA-4-209003: Fragment database limit of number exceeded: src = source_address, dest = dest_address, proto = protocol, id = number Explanation Too many IP fragments are currently awaiting reassembly. By default, the maximum number of fragments is 200 (to raise the maximum, see the fragment size command in the command reference). The ASA limits the number of IP fragments that can be concurrently reassembled. This restriction prevents memory depletion at the ASA under abnormal network conditions. In general, fragmented traffic should be a small percentage of the total traffic mix. An exception is in a network environment with NFS over UDP where a large percentage is fragmented traffic; if this type of traffic is relayed through the ASA, consider using NFS over TCP instead. To prevent fragmentation, see the sysopt connection tcpmss bytes command in the command reference. Recommended Action If this message persists, a denial of service (DoS) attack might be in progress. Contact the remote peer administrator or upstream provider.
209004
Error Message %ASA-4-209004: Invalid IP fragment, size = bytes exceeds maximum size = bytes: src = source_address, dest = dest_address, proto = protocol, id = number Explanation An IP fragment is malformed. The total size of the reassembled IP packet exceeds the
maximum possible size of 65,535 bytes.

Recommended Action A possible intrusion event may be in progress. If this message persists, contact
the remote peer administrator or upstream provider.
209005
Error Message %ASA-4-209005: Discard IP fragment set with more than number elements: src = Too many elements are in a fragment set. Explanation The ASA disallows any IP packet that is fragmented into more than 24 fragments. For more information, see the fragment command in the command reference. Recommended Action A possible intrusion event may be in progress. If the message persists, contact
the remote peer administrator or upstream provider. You can change the number of fragments per packet by using the fragment chain xxx interface_name command.
1-84
Chapter 1
210001
Error Message %ASA-3-210001: LU sw_module_name error = number Explanation A Stateful Failover error occurred. Recommended Action If this error persists after traffic lessens through the ASA, report this error to
the Cisco TAC.
210002
Error Message %ASA-3-210002: LU allocate block (bytes) failed. Explanation Stateful Failover cannot allocate a block of memory to transmit stateful information to the standby ASA. Recommended Action Check the failover interface using the show interface command to make sure its transmit is normal. Also check the current block memory using the show block command. If current available count is 0 within any of the blocks of memory, then reload the ASA software to recover the lost blocks of memory.
210003
Error Message %ASA-3-210003: Unknown LU Object number Explanation Stateful Failover received an unsupported Logical Update object and was unable to process it. This can be caused by corrupted memory, LAN transmissions, and other events. Recommended Action If you see this error infrequently, then no action is required. If this error occurs frequently, check the Stateful Failover link LAN connection. If the error was not caused by a faulty failover link LAN connection, determine if an external user is trying to compromise the protected network. Also check for misconfigured clients.
210005
Error Message %ASA-3-210005: LU allocate connection failed Explanation Stateful Failover cannot allocate a new connection on the standby unit. This may be caused by little or no RAM memory available within the ASA. Recommended Action Check the available memory using the show memory command to make sure
that the ASA has free memory. If there is no available memory, add more physical memory to the ASA.
1-85
Syslog Messages
210006
Error Message %ASA-3-210006: LU look NAT for IP_address failed Explanation Stateful Failover was unable to locate a NAT group for the IP address on the standby
unit. The active and standby ASAs may be out-of-sync with each other.
Recommended Action Use the write standby command on the active unit to synchronize system
memory with the standby unit.
210007
Error Message %ASA-3-210007: LU allocate xlate failed Explanation Stateful Failover failed to allocate a translation slot record. Recommended Action Check the available memory by using the show memory command to make
sure that the ASA has free memory available. If no memory is available, add more memory.
210008
Error Message %ASA-3-210008: LU no xlate for inside_address/inside_port outside_address/outside_port Explanation The ASA cannot find a translation slot record for a Stateful Failover connection; as a result, the ASA cannot process the connection information. Recommended Action Use the write standby command on the active unit to synchronize system
memory between the active and standby units.
210010
Error Message %ASA-3-210010: LU make UDP connection for outside_address:outside_port inside_address:inside_port failed Explanation Stateful Failover was unable to allocate a new record for a UDP connection. Recommended Action Check the available memory by using the show memory command to make
sure that the ASA has free memory available. If no memory is available, add more memory.
1-86
Chapter 1
210020
Error Message %ASA-3-210020: LU PAT port port reserve failed Explanation Stateful Failover is unable to allocate a specific PAT address that is in use. Recommended Action Use the write standby command on the active unit to synchronize system
memory between the active and standby units.
210021
Error Message %ASA-3-210021: LU create static xlate global_address ifc interface_name failed Explanation Stateful Failover is unable to create a translation slot. Recommended Action Enter the write standby command on the active unit to synchronize system memory between the active and standby units.
210022
Error Message %ASA-6-210022: LU missed number updates Explanation Stateful Failover assigns a sequence number for each record sent to the standby unit.
When a received record sequence number is out of sequence with the last updated record, the information in between is assumed to be lost, and this error message is sent as a result.
Recommended Action Unless LAN interruptions occur, check the available memory on both ASA units to ensure that enough memory is available to process the stateful information. Use the show failover command to monitor the quality of stateful information updates.
211001
Error Message %ASA-3-211001: Memory allocation Error Explanation The ASA failed to allocate RAM system memory. Recommended Action If this message occurs periodically, it can be ignored. If it repeats frequently, contact the Cisco TAC.
1-87
Syslog Messages
211003
Error Message %ASA-3-211003: Error in computed percentage CPU usage value Explanation The percentage of CPU usage is greater than 100 percent. Recommended Action If this message occurs periodically, it can be ignored. If it repeats frequently, contact the Cisco TAC.
211004
Error Message %ASA-1-211004: WARNING: Minimum Memory Requirement for ASA version ver not met for ASA image. min MB required, actual MB found. Explanation The ASA does not meet the minimum memory requirements for this version. A memory upgrade is required. If a memory upgrade is not immediately available, then downgrade the ASA to Version 8.2(1) or lower. Continuing to run an 8.3 image without meeting the minimum memory requirements is not supported and may result in critical system failures.
verRunning image version number minMinimum required amount of RAM to run the installed image. The available memory upgrade PID numbers are as follows: ASA5505-MEM-512= ASA5510-MEM-1GB= ASA5520-MEM-2GB= ASA5540-MEM-2GB= actualAmount of RAM currently installed in the system
Recommended Action Install the required amount of RAM. Use the memory upgrade PID numbers to order the required amount of RAM.
212001
Error Message %ASA-3-212001: Unable to open SNMP channel (UDP port port) on interface interface_number, error code = code Explanation The ASA is unable to receive SNMP requests destined for the ASA from SNMP management stations located on this interface. The SNMP traffic passing through the ASA on any interface is not affected. The error codes are as follows:
An error code of -1 indicates that the ASA cannot open the SNMP transport for the interface. This can occur when the user attempts to change the port on which SNMP accepts queries to one that is already in use by another feature. In this case, the port used by SNMP will be reset to the default port for incoming SNMP queries (UDP 161).
1-88
Chapter 1
An error code of -2 indicates that the ASA cannot bind the SNMP transport for the interface.
Recommended Action After the ASA reclaims some of its resources when traffic is lighter, reenter the
snmp-server host command for that interface.
212002
Error Message %ASA-3-212002: Unable to open SNMP trap channel (UDP port port) on interface interface_number, error code = code Explanation The ASA is unable to send its SNMP traps from the ASA to SNMP management stations
located on this interface. The SNMP traffic passing through the ASA on any interface is not affected. The error codes are as follows:

An error code of -1 indicates that the ASA cannot open the SNMP trap transport for the interface. An error code of -2 indicates that the ASA cannot bind the SNMP trap transport for the interface. An error code of -3 indicates that the ASA cannot set the trap channel as write-only.
Recommended Action After the ASA reclaims some of its resources when traffic is lighter, reenter the
snmp-server host command for that interface.
212003
Error Message %ASA-3-212003: Unable to receive an SNMP request on interface interface_number, error code = code, will try again. Explanation An internal error occurred in receiving an SNMP request destined for the ASA on the specified interface. The error codes are as follows:
An error code of -1 indicates that the ASA cannot find a supported transport type for the interface. An error code of -5 indicates that the ASA received no data from the UDP channel for the interface. An error code of -7 indicates that the ASA received an incoming request that exceeded the supported buffer size. An error code of -14 indicates that the ASA cannot determine the source IP address from the UDP channel. An error code of -22 indicates that the ASA received an invalid parameter.
Recommended Action None required. The ASA SNMP agent goes back to wait for the next SNMP
request.
1-89
Syslog Messages
212004
Error Message %ASA-3-212004: Unable to send an SNMP response to IP Address IP_address Port port interface interface_number, error code = code Explanation An internal error occurred in sending an SNMP response from the ASA to the specified host on the specified interface. The error codes are as follows:
An error code of -1 indicates that the ASA cannot find a supported transport type for the interface. An error code of -2 indicates that the ASA sent an invalid parameter. An error code of -3 indicates that the ASA was unable to set the destination IP address in the UDP channel. An error code of -4 indicates that the ASA sent a PDU length that exceeded the supported UDP segment size. An error code of -5 indicates that the ASA was unable to allocate a system block to construct the PDU.
212005
Error Message %ASA-3-212005: incoming SNMP request (number bytes) on interface interface_name exceeds data buffer size, discarding this SNMP request. Explanation The length of the incoming SNMP request that is destined for the ASA exceeds the size
of the internal data buffer (512 bytes) used for storing the request during internal processing. The ASA is unable to process this request. The SNMP traffic passing through the ASA on any interface is not affected.
Recommended Action Have the SNMP management station resend the request with a shorter length.
For example, instead of querying multiple MIB variables in one request, try querying only one MIB variable in a request. You may need to modify the configuration of the SNMP manager software.
212006
Error Message %ASA-3-212006: Dropping SNMP request from src_addr/src_port to ifc:dst_addr/dst_port because: reason username Explanation The ASA cannot process the SNMP request being sent to it for the following reasons:
user not foundThe username cannot be located in the local SNMP user database. username exceeds maximum lengthThe username embedded in the PDU exceeds the maximum length allowed by the SNMP RFCs. authentication algorithm failureAn authentication failure caused by an invalid password or a packet authenticated using the incorrect algorithm.
1-90
Chapter 1
privacy algorithm failureA privacy failure caused by an invalid password or a packet encrypted using the incorrect algorithm. error decrypting requestAn error occurred in the platform crypto module decrypting the user request. error encrypting responseAn error occurred in the platform crypto module encrypting the user response or trap notification. engineBoots has reached maximum valueThe engineBoots variable has reached the maximum allowed value. For more information, see message 212011.
Note
The username appears after each reason listed.

Recommended Action Check the ASA SNMP server settings and confirm that the NMS configuration is using the expected user, authentication, and encryption settings. Enter the show crypto accelerator statistics command to isolate errors in the platform crypto module.
212009
Error Message %ASA-5-212009: Configuration request for SNMP group groupname failed. User username, reason. Explanation A user has tried to change the SNMP server group configuration. One or more users that
refer to the group have insufficient settings to comply with the requested group changes.

groupnameA string that represents the group name usernameA string that represents the username reasonA string that represents one of the following reasons: - missing auth-passwordA user has tried to add authentication to the group, and the user has not specified an authentication password - missing priv-passwordA user has tried to add privacy to the group, and the user has not specified an encryption password - reference group intended for removalA user has tried to remove a group that has users belonging to it
Recommended Action The user must update the indicated user configurations before changing the group or removing indicated users, and then add them again after making changes to the group.
212010
Error Message %ASA-3-212010: Configuration request for SNMP user %s failed. Host %s reason. Explanation A user has tried to change the SNMP server user configuration by removing one or more hosts that reference the user. One message is generated per host.
%sA string that represents the username or hostname
1-91
Syslog Messages
reasonA string the represents the following reason: - references user intended for removalThe name of the user to be removed from the host.
Recommended Action The user must either update the indicated host configuration before changing a user or remove the indicated hosts, then add them again after making changes to the user.
212011
Error Message %ASA-3-212011: SNMP engineBoots is set to maximum value. Reason: %s User intervention necessary.
For example:
%ASA-3-212011: SNMP engineBoots is set to maximum value. Reason: error accessing persistent data. User intervention necessary.
Explanation The device has rebooted 214783647 times, which is the maximum allowed value of the engineBoots variable, or an error reading the persistent value from flash memory has occurred. The engineBoots value is stored in flash memory in the flash:/snmp/ctx-name file, where ctx-name is the name of the context. In single mode, the name of this file is flash:/snmp/single_vf. In multi-mode, the name of the file for the admin context is flash:/snmp/admin. During a reboot, if the device is unable to read from the file or write to the file, the engineBoots value is set to the maximum.
%sA string that represents the reason that the engineBoots value is set to the maximum allowed value. The two valid strings are device reboots and error accessing persistent data.
Recommended Action For the first string, the administrator must delete all SNMP Version 3 users and
add them again to reset the engineBoots variable to 1. All subsequent Version 3 queries will fail until all users have been removed. For the second string, the administrator must delete the context-specific file, then delete all SNMP Version users, and add them again to reset the engineBoots variable to 1. All subsequent Version 3 queries will fail until all users have been removed.
212012
Error Message %ASA-3-212012: Unable to write SNMP engine data to persistent storage. Explanation The SNMP engine data is written to the file, flash:/snmp/context-name. For example: in
single mode, the data is written to the file, flash:/snmp/single_vf. In the admin context in multi-mode, the file is written to the directory, flash:/snmp/admin. The error may be caused by a failure to create the flash:/snmp directory or the flash:/snmp/context-name file. The error may also be caused by a failure to write to the file.
Recommended Action The system administrator should remove the flash:/snmp/context-name file, then remove all SNMP Version 3 users, and add them again. This procedure should recreate the flash:/snmp/context-name file. If the problem persists, the system administrator should try reformatting the flash.
1-92
Chapter 1
213001
Error Message %ASA-3-213001: PPTP control daemon socket io string, errno = number. Explanation An internal TCP socket I/O error occurred. Recommended Action Contact the Cisco TAC.
213002
Error Message %ASA-3-213002: PPTP tunnel hashtable insert failed, peer = IP_address. Explanation An internal software error occurred while creating a new PPTP tunnel. Recommended Action Contact the Cisco TAC.
213003
Error Message %ASA-3-213003: PPP virtual interface interface_number isn't opened. Explanation An internal software error occurred while closing a PPP virtual interface. Recommended Action Contact the Cisco TAC.
213004
Error Message %ASA-3-213004: PPP virtual interface interface_number client ip allocation failed. Explanation An internal software error occurred while allocating an IP address to the PPTP client when the IP local address pool was depleted. Recommended Action Consider allocating a larger pool with the ip local pool command.
213005
Error Message %ASA-3-213005%: Dynamic-Access-Policy action (DAP) action aborted Explanation The DAP is dynamically created by selecting configured access policies based on the authorization rights of the user and the posture assessment results of the remote endpoint device. The resulting dynamic policy indicates that the session should be terminated. Recommended Action None required.
1-93
Syslog Messages
213006
Error Message %ASA-3-213006%: Unable to read dynamic access policy record. Explanation There was either an error in retrieving the DAP policy record data, or the action configuration was missing. Recommended Action A configuration change might have resulted in deleting a DAP record. Use
ASDM to recreate the DAP record.
214001
Error Message %ASA-2-214001: Terminating manager session from IP_address on interface interface_name. Reason: incoming encrypted data (number bytes) longer than number bytes Explanation An incoming encrypted data packet destined for the ASA management port indicates a
packet length exceeding the specified upper limit. This may be a hostile event. The ASA immediately terminates this management connection.
Recommended Action Ensure that the management connection was initiated by Cisco Secure Policy
Manager.
215001
Error Message %ASA-2-215001:Bad route_compress() call, sdb = number Explanation An internal software error occurred. Recommended Action Contact the Cisco TAC.
217001
Error Message %ASA-2-217001: No memory for string in string Explanation An operation failed because of low memory. Recommended Action If sufficient memory exists, then send the error message, the configuration, and
any details about the events leading up to the error to the Cisco TAC.
1-94
Chapter 1
216001
Error Message %ASA-n-216001: internal error in: function: message Explanation Various internal errors have occurred that should not appear during normal operation.
The severity level varies depending on the cause of the message.

nThe message severity functionThe affected component messageA message describing the cause of the problem
Recommended Action Search the Bug Toolkit for the specific text message and try to use the Output Interpreter to resolve the problem. If the problem persists, contact the Cisco TAC.
216002
Error Message ASA-3-216002: Unexpected event (major: major_id, minor: minor_id) received by task_string in function at line: line_num Explanation A task registers for event notification, but the task cannot handle the specific event.
Events that can be watched include those associated with queues, booleans, and timer services. If any of the registered events occur, the scheduler wakes up the task to process the event. This message is generated if an unexpected event woke up the task, but it does not know how to handle the event. If an event is left unprocessed, it can wake up the task very often to make sure that it is processed, but this should not occur under normal conditions. If this message appears, it does not necessarily mean the device is unusable, but something unusual has occurred and needs to be investigated.

major_idEvent identifier minor_id Event identifier task_stringCustom string passed by the task to identify itself functionThe function that received the unexpected event line_num Line number in the code
Recommended Action If the problem persists, contact the Cisco TAC.
1-95
Syslog Messages
216003
Error Message %ASA-3-216003: Unrecognized timer timer_ptr, timer_id received by task_string in function at line: line_num Explanation An unexpected timer event woke up the task, but the task does not know how to handle
the event. A task can register a set of timer services with the scheduler. If any of the timers expire, the scheduler wakes up the task to take action. This message is generated if the task is awakened by an unrecognized timer event. An expired timer, if left unprocessed, wakes up the task continuously to make sure that it is processed, and this is undesirable. This should not occur under normal conditions. If this message appears, it does not necessarily mean the device is unusable, but something unusual has occurred and needs to be investigated.

timer_ptrPointer to the timer timer_idTimer identifier task_stringCustom string passed by the task to identify itself functionThe function that received the unexpected event line_numLine number in the code
216004
Error Message %ASA-4-216004:prevented: error in function at file(line) - stack trace Explanation An internal logic error has occurred, which should not occur during normal operation.
errorInternal logic error. Possible errors include the following: - Exception - Dereferencing null pointer - Array index out of bounds - Invalid buffer size - Writing from input - Source and destination overlap - Invalid date - Access offset from array indices functionThe calling function that generated the error file(line)The file and line number that generated the error stack traceFull call stack traceback, starting with the calling function. For example: (0x001010a4 0x00304e58 0x00670060 0x00130b04)
1-96
Chapter 1
216005
Error Message %ASA-1-216005: ERROR: Duplex-mismatch on interface_name resulted in transmitter lockup. A soft reset of the switch was performed. Explanation A duplex mismatch on the port caused a problem in which the port can no longer transmit packets. This condition was detected, and the switch was reset to autorecover. This message applies only to the ASA 5505.
interface_nameThe interface name that was locked up
Recommended Action A duplex mismatch exists between the specified port and the ASA 5505 that is
connected to it. Correct the duplex mismatch by either setting both devices to autorecover, or hard coding the duplex mismatch for both devices to be the same.
218001
Error Message %ASA-2-218001: Failed Identification Test in slot# [fail#/res]. Explanation The module in slot# of the ASA cannot be identified as a genuine Cisco product. Cisco
warranties and support programs apply only to genuine Cisco products. If Cisco determines that the cause of a support issue is related to non-Cisco memory, SSM modules, SSC modules, or other modules, Cisco may deny support under your warranty or under a Cisco support program such as SmartNet.
Recommended Action If this message recurs, copy it exactly as it appears on the console or in the system log. Research and try to resolve the error using the Output Interpreter. Also perform a search with the Bug Toolkit. If the problem persists, contact the Cisco TAC.
218002
Error Message %ASA-2-218002: Module (slot#) is a registered proto-type for Cisco Lab use only, and not certified for live network operation. Explanation The hardware in the specified location is a prototype module that came from a Cisco lab. Recommended Action If this message reoccurs, copy it exactly as it appears on the console or in the
system log. Research and try to resolve the error using the Output Interpreter. Also perform a search with the Bug Toolkit. If the problem persists, contact the Cisco TAC.
1-97
Syslog Messages
218003
Error Message %ASA-2-218003: Module Version in slot# is obsolete. The module in slot = slot# is obsolete and must be returned via RMA to Cisco Manufacturing. If it is a lab unit, it must be returned to Proto Services for upgrade. Explanation Obsolete hardware has been detected or the show module command has been run for
the module. This message is generated once per minute after it first appears.
Recommended Action If this message recurs, copy it exactly as it appears on the console or in the system log. Research and try to resolve the error using the Output Interpreter. Also perform a search with the Bug Toolkit. If the problem persists, contact the Cisco TAC.
218004
Error Message %ASA-2-218004: Failed Identification Test in slot# [fail#/res] Explanation Aproblem occurred while identifying hardware in the specified location. Recommended Action If this message recurs, copy it exactly as it appears on the console or in the system log. Research and try to resolve the error using the Output Interpreter. Also perform a search with the Bug Toolkit. If the problem persists, contact the Cisco TAC.
219002
Error Message %ASA-3-219002: I2C_API_name error, slot = slot_number, device = device_number, address = address, byte count = count. Reason: reason_string Explanation The I2C serial bus API has failed because of a hardware or software problem.
I2C_API_nameThe I2C API that failed, which can be one of the following:
I2C_read_byte_w_wait() I2C_read_word_w_wait() I2C_read_block_w_wait() I2C_write_byte_w_wait() I2C_write_word_w_wait() I2C_write_block_w_wait() I2C_read_byte_w_suspend() I2C_read_word_w_suspend() I2C_read_block_w_suspend() I2C_write_byte_w_suspend() I2C_write_word_w_suspend() I2C_write_block_w_suspend()
1-98
Chapter 1
slot_numberThe hexadecimal number of the slot where the I/O operation that generated the message occurred. The slot number cannot be unique to a slot in the chassis. Depending on the chassis, two different slots might have the same I2C slot number. Also, the value is not necessarily less than or equal to the number of slots. The value depends on the way the I2C hardware is wired. device_numberThe hexadecimal number of the device on the slot for which the I/O operation was performed addressThe hexadecimal address of the device on which the I/O operation occurred byte_countThe byte count in decimal format of the I/O operation error_stringThe reason for the error, which can be one of the following:
I2C_BUS_TRANSACTION_ERROR I2C_CHKSUM_ERROR I2C_TIMEOUT_ERROR I2C_BUS_COLLISION_ERROR I2C_HOST_BUSY_ERROR I2C_UNPOPULATED_ERROR I2C_SMBUS_UNSUPPORT I2C_BYTE_COUNT_ERROR I2C_DATA_PTR_ERROR Recommended Action Perform the following steps: 1.
Log and review the messages and the errors associated with the event. If the message does not occur continuously and disappears after a few minutes, it might be because the I2C serial bus is busy. Reboot the software running on the ASA. Power cycle the device. When you turn off the power, make sure that you wait several seconds before turning the power on. If the problem persists, contact the Cisco TAC.
2. 3. 4.
1-99
Syslog Messages

302003
Error Message %ASA-6-302003: Built H245 connection for foreign_address outside_address/outside_port local_address inside_address/inside_port Explanation An H.245 connection has been started from the outside_address to the inside_address. The ASA has detected the use of an Intel Internet Phone. The foreign port (outside_port) only appears on connections from outside the ASA. The local port value (inside_port) only appears on connections that were started on an internal interface. Recommended Action None required.
302004
Error Message %ASA-6-302004: Pre-allocate H323 UDP backconnection for foreign_address outside_address/outside_port to local_address inside_address/inside_port Explanation An H.323 UDP back connection has been preallocated to the foreign address
(outside_address) from the local address (inside_address). The ASA has detected the use of an Intel Internet Phone. The foreign port (outside_port) only appears on connections from outside the ASA. The local port value (inside_port) only appears on connections that were started on an internal interface.
302010
Error Message %ASA-6-302010: connections in use, connections most used Explanation A TCP connection has restarted.
connectionsThe number of connections
1-100
Chapter 1
302012
Error Message %ASA-6-302012: Pre-allocate H225 Call Signalling Connection for faddr IP_address/port to laddr IP_address Explanation An H.225 secondary channel has been preallocated. Recommended Action None required.
302013
Error Message %ASA-6-302013: Built {inbound|outbound} TCP connection_id for interface:real-address/real-port (mapped-address/mapped-port) [(idfw_user)] to interface:real-address/real-port (mapped-address/mapped-port) [(idfw_user)] [(user)] Explanation A TCP connection slot between two hosts was created.
connection_id A unique identifier interface, real-address, real-portThe actual sockets mapped-address, mapped-portThe mapped sockets userThe AAA name of the user idfw_userThe name of the identity firewall user
If inbound is specified, the original control connection was initiated from the outside. For example, for FTP, all data transfer channels are inbound if the original control channel is inbound. If outbound is specified, the original control connection was initiated from the inside.
302014
Error Message %ASA-6-302014: Teardown TCP connection id for interface:real-address/real-port [(idfw_user)] to interface:real-address/real-port [(idfw_user)] duration hh:mm:ss bytes bytes [reason] [(user)] Explanation A TCP connection between two hosts was deleted. The following list describes the
message values:

id A unique identifier interface, real-address, real-portThe actual socket durationThe lifetime of the connection bytesThe data transfer of the connection userThe AAA name of the user idfw_userThe name of the identity firewall user
1-101
Syslog Messages
reasonThe action that causes the connection to terminate. Set the reason variable to one of the TCP termination reasons listed in Table 1-3.
TCP Termination Reasons
Table 1-3
Reason Conn-timeout Deny Terminate Failover primary closed FIN Timeout Flow closed by inspection Flow terminated by IPS Flow reset by IPS Flow terminated by TCP Intercept Flow timed out Flow timed out with reset Flow is a loopback Free the flow created as result of packet injection Invalid SYN Idle Timeout IPS fail-close No valid adjacency Pinhole Timeout
Description The connection ended when a flow is closed because of the expiration of its inactivity timer. Flow was terminated by application inspection. The standby unit in a failover pair deleted a connection because of a message received from the active unit. Force termination after 10 minutes awaiting the last ACK or after half-closed timeout. Flow was terminated by the inspection feature. Flow was terminated by IPS. Flow was reset by IPS. Flow was terminated by TCP Intercept. Flow has timed out. Flow has timed out, but was reset. Flow is a loopback. The connection was built because the packet tracer feature sent a simulated packet through the ASA. The SYN packet was not valid. The connection timed out because it was idle longer than the timeout value. Flow was terminated because the IPS card is down. This counter is incremented when the ASA tried to obtain an adjacency and could not obtain the MAC address for the next hop. The packet is dropped. The counter is incremented to report that the ASA opened a secondary flow, but no packets passed through this flow within the timeout interval, and so it was removed. An example of a secondary flow is the FTP data channel that is created after successful negotiation on the FTP control channel. When the ASA adds a lower cost (better metric) route, packets arriving that match the new route cause their existing connection to be torn down after the user-configured timeout (floating-conn) value. Subsequent packets rebuild the connection out of the interface with the better metric. To prevent the addition of lower cost routes from affecting active flows, you can set the floating-conn configuration timeout value to 0:0:0. A back channel initiation occurred from the wrong side. Force termination after 30 seconds, awaiting three-way handshake completion. The connection was terminated because of a bad TCP retransmission.
Route change
SYN Control SYN Timeout TCP bad retransmission
1-102
Chapter 1
Table 1-3
TCP Termination Reasons (continued)
Reason TCP FINs TCP Invalid SYN TCP Reset APPLIANCE TCP Reset - I TCP Reset - O TCP segment partial overlap
Description A normal close-down sequence occurred. The IP address follows the reason. Invalid TCP SYN packet. The flow is closed when a TCP reset is generated by the ASA. Reset was from the inside. Reset was from the outside. A partially overlapping segment was detected.
TCP unexpected A connection was terminated due to variation in the TCP window size. window size variation Tunnel has been torn down Unauth Deny Unknown Xlate Clear Flow was terminated because the tunnel is down. An authorization was denied by a URL filter. An unknown error has occurred. A command line was removed.
302015
Error Message %ASA-6-302015: Built {inbound|outbound} UDP connection number for interface_name:real_address/real_port (mapped_address/mapped_port) [(idfw_user)] to interface_name:real_address/real_port (mapped_address/mapped_port)[(idfw_user)] [(user)] Explanation A UDP connection slot between two hosts was created. The following list describes the
message values:

numberA unique identifier interface, real_address, real_portThe actual sockets mapped_address and mapped_portThe mapped sockets userThe AAA name of the user idfw_userThe name of the identity firewall user
If inbound is specified, then the original control connection is initiated from the outside. For example, for UDP, all data transfer channels are inbound if the original control channel is inbound. If outbound is specified, then the original control connection is initiated from the inside.
1-103
Syslog Messages
302016
Error Message %ASA-6-302016: Teardown UDP connection number for interface:real-address/real-port [(idfw_user)] to interface:real-address/real-port [(idfw_user)] duration hh:mm:ss bytes bytes [(user)] Explanation A UDP connection slot between two hosts was deleted. The following list describes the
message values:

numberA unique identifier interface, real_address, real_portThe actual sockets timeThe lifetime of the connection bytesThe data transfer of the connection idA unique identifier interface, real-address, real-portThe actual sockets durationThe lifetime of the connection bytesThe data transfer of the connection userThe AAA name of the user idfw_userThe name of the identity firewall user
302017
Error Message %ASA-6-302017: Built {inbound|outbound} GRE connection id from interface:real_address (translated_address) [(idfw_user)] to interface:real_address/real_cid (translated_address/translated_cid) [(idfw_user)] [(user) Explanation A GRE connection slot between two hosts was created. The id is an unique identifier.
The interface, real_address, real_cid tuple identifies the one of the two simplex PPTP GRE streams. The parenthetical translated_address, translated_cid tuple identifies the translated value with NAT. If inbound is indicated, then the connection can only be used inbound. If outbound is indicated, then the connection can only be used for outbound. The following list describes the message values:

idUnique number identifying the connection inboundControl connection is for inbound PPTP GRE flow outboundControl connection is for outbound PPTP GRE flow interface_nameThe interface name real_addressIP address of the actual host real_cidUntranslated call ID for the connection translated_addressIP address after translation
1-104
Chapter 1
translated_cidTranslated call userAAA user name idfw_userThe name of the identity firewall user
302018
Error Message %ASA-6-302018: Teardown GRE connection id from interface:real_address (translated_address) [(idfw_user)] to interface:real_address/real_cid (translated_address/translated_cid) [(idfw_user)] duration hh:mm:ss bytes bytes [(user)] Explanation A GRE connection slot between two hosts was deleted. The interface, real_address,
real_port tuples identify the actual sockets. Duration identifies the lifetime of the connection. The following list describes the message values:

idUnique number identifying the connection interfaceThe interface name real_addressIP address of the actual host real_portPort number of the actual host. hh:mm:ssTime in hour:minute:second format bytesNumber of PPP bytes transferred in the GRE session reasonReason why the connection was terminated userAAA user name idfw_userThe name of the identity firewall user
302019
Error Message %ASA-3-302019: H.323 library_name ASN Library failed to initialize, error code number Explanation The specified ASN library that the ASA uses for decoding the H.323 messages failed to initialize; the ASA cannot decode or inspect the arriving H.323 packet. The ASA allows the H.323 packet to pass through without any modification. When the next H.323 message arrives, the ASA tries to initialize the library again. Recommended Action If this message is generated consistently for a particular library, contact the Cisco TAC and provide them with all log messages (preferably with timestamps).
1-105
Syslog Messages
302020
Error Message %ASA-6-302020: Built {in | out}bound ICMP connection for faddr {faddr | icmp_seq_num} [(idfw_user)] gaddr {gaddr | cmp_type} laddr laddr [(idfw_user)] Explanation An ICMP session was established in the fast-path when stateful ICMP was enabled
using the inspect icmp command.

302021
Error Message %ASA-6-302021: Teardown ICMP connection for faddr {faddr | icmp_seq_num} [(idfw_user)] gaddr {gaddr | cmp_type} laddr laddr [(idfw_user)] Explanation An ICMP session is removed in the fast-path when stateful ICMP is enabled using the
inspect icmp command.

302033
Error Message %ASA-6-302033:Pre-allocated H323 GUP Connection for faddr interface:foreign address/foreign-port to laddr interface:local-address/local-port Explanation A GUP connection was started from the foreign address to the local address. The foreign
port (outside port) only appears on connections from outside the security device. The local port value (inside port) only appears on connections started on an internal interface.

interfaceThe interface name foreign-addressIP address of the foreign host foreign-portPort number of the foreign host local-addressIP address of the local host local-portPort number of the local host
1-106
Chapter 1
302034
Error Message %ASA-4-302034: Unable to pre-allocate H323 GUP Connection for faddr interface:foreign address/foreign-port to laddr interface:local-address/local-port Explanation The module failed to allocate RAM system memory while starting a connection or has no more address translation slots available.
interfaceThe interface name foreign-addressIP address of the foreign host foreign-portPort number of the foreign host local-addressIP address of the local host local-portPort number of the local host
Recommended Action If this message occurs periodically, it can be ignored. If it repeats frequently, contact the Cisco TAC. You can check the size of the global pool compared to the number of inside network clients. Alternatively, shorten the timeout interval of translations and connections. This message may also be caused by insufficient memory; try reducing the amount of memory usage, or purchasing additional memory.
302302
Error Message %ASA-3-302302: ACL = deny; no sa created Explanation IPsec proxy mismatches have occurred. Proxy hosts for the negotiated SA correspond
to a deny access-list command policy.

Recommended Action Check the access-list command statement in the configuration. Contact the
administrator for the peer.
302303
Error Message %ASA-6-302303: Built TCP state-bypass connection conn_id from initiator_interface:real_ip/real_port(mapped_ip/mapped_port) to responder_interface:real_ip/real_port (mapped_ip/mapped_port) Explanation A new TCP connection has been created, and this connection is a TCP-state-bypass
connection. This type of connection bypasses all the TCP state checks and additional security checks and inspections.
Recommended Action If you need to secure TCP traffic with all the normal TCP state checks as well as all other security checks and inspections, you can use the no set connection advanced-options tcp-state-bypass command to disable this feature for TCP traffic.
1-107
Syslog Messages
302304
Error Message %ASA-6-302304: Teardown TCP state-bypass connection conn_id from initiator_interface:ip/port to responder_interface:ip/port duration, bytes, teardown reason. Explanation A new TCP connection has been torn down, and this connection is a TCP-state-bypass connection. This type of connection bypasses all the TCP state checks and additional security checks and inspections.
durationThe duration of the TCP connection bytesThe total number of bytes transmitted over the TCP connection teardown reasonThe reason for the teardown of the TCP connection
Recommended Action If you need to secure TCP traffic with all the normal TCP state checks as well
as all other security checks and inspections, you can use the no set connection advanced-options tcp-state-bypass command to disable this feature for TCP traffic.
303002
Error Message %ASA-6-303002: FTP connection from src_ifc:src_ip/src_port to dst_ifc:dst_ip/dst_port, user username action file filename Explanation A client has uploaded or downloaded a file from the FTP server.
src_ifcThe interface where the client resides. src_ipThe IP address of the client. src_portThe client port. dst_ifcThe interface where the server resides. dst_ipThe IP address of the FTP server. dst_portThe server port. usernameThe FTP username. actionThe stored or retrieved actions. filenameThe file stored or retrieved.
1-108
Chapter 1
303004
Error Message %ASA-5-303004: FTP cmd_string command unsupported - failed strict inspection, terminating connection from source_interface:source_address/source_port to dest_interface:dest_address/dest_interface Explanation Strict FTP inspection on FTP traffic has been used, and an FTP request message contains a command that is not recognized by the device. Recommended Action None required.
303005
Error Message %ASA-5-303005: Strict FTP inspection matched match_string in policy-map policy-name, action_string from src_ifc:sip/sport to dest_ifc:dip/dport Explanation When FTP inspection matches any of the following configured values: filename, file
type, request command, server, or username, then the action specified by the action_string in this message occurs.

match_stringThe match clause in the policy map policy-nameThe policy map that matched action_stringThe action to take; for example, Reset Connection src_ifcThe source interface name sipThe source IP address sportThe source port dest_ifcThe destination interface name dipThe destination IP address dportThe destination port
304001
Error Message %ASA-5-304001: user@source_address [(idfw_user)] Accessed URL dest_address: url. Explanation The specified host tried to access the specified URL. Recommended Action None required.
1-109
Syslog Messages
304002
Error Message %ASA-5-304002: Access denied URL chars SRC IP_address [(idfw_user)] DEST IP_address: chars Explanation Access from the source address to the specified URL or FTP site was denied. Recommended Action None required.
304003
Error Message %ASA-3-304003: URL Server IP_address timed out URL url Explanation A URL server timed out. Recommended Action None required.
304004
Error Message %ASA-6-304004: URL Server IP_address request failed URL url Explanation A Websense server request failed. Recommended Action None required.
304005
Error Message %ASA-7-304005: URL Server IP_address request pending URL url Explanation A Websense server request is pending. Recommended Action None required.
304006
Error Message %ASA-3-304006: URL Server IP_address not responding Explanation The Websense server is unavailable for access, and the ASA attempts to either try to access the same server if it is the only server installed, or another server if there is more than one. Recommended Action None required.
1-110
Chapter 1
304007
Error Message %ASA-2-304007: URL Server IP_address not responding, ENTERING ALLOW mode. Explanation You used the allow option of the filter command, and the Websense servers are not responding. The ASA allows all web requests to continue without filtering while the servers are not available. Recommended Action None required.
304008
Error Message %ASA-2-304008: LEAVING ALLOW mode, URL Server is up. Explanation You used the allow option of the filter command, and the ASA receives a response message from a Websense server that previously was not responding. With this response message, the ASA exits the allow mode, which enables the URL filtering feature again. Recommended Action None required.
304009
Error Message %ASA-7-304009: Ran out of buffer blocks specified by url-block command Explanation The URL pending buffer block is running out of space. Recommended Action Change the buffer block size by entering the url-block block block_size
command.
305005
Error Message %ASA-3-305005: No translation group found for protocol src interface_name: source_address/source_port [(idfw_user)] dst interface_name: dest_address/dest_port [(idfw_user)] Explanation A packet does not match any of the outbound nat command rules. If NAT is not configured for the specified source and destination systems, the message will be generated frequently. Recommended Action This message indicates a configuration error. If dynamic NAT is desired for the
source host, ensure that the nat command matches the source IP address. If static NAT is desired for the source host, ensure that the local IP address of the static command matches. If no NAT is desired for the source host, check the ACL bound to the NAT 0 ACL.
1-111
Syslog Messages
305006
Error Message %ASA-3-305006: {outbound static|identity|portmap|regular) translation creation failed for protocol src interface_name:source_address/source_port [(idfw_user)] dst interface_name:dest_address/dest_port [(idfw_user)] Explanation A protocol (UDP, TCP, or ICMP) failed to create a translation through the ASA. The
ASA does not allow packets through that are destined for network or broadcast addresses. The ASA provides this checking for addresses that are explicitly identified with static commands. For inbound traffic, the ASA denies translations for an IP address identified as a network or broadcast address. The ASA does not apply PAT to all ICMP message types; it only applies PAT ICMP echo and echo-reply packets (types 8 and 0). Specifically, only ICMP echo or echo-reply packets create a PAT translation. As a result, when the other ICMP messages types are dropped, this message is generated. The ASA uses the global IP address and mask from configured static commands to differentiate regular IP addresses from network or broadcast IP addresses. If the global IP address is a valid network address with a matching network mask, then the ASA does not create a translation for network or broadcast IP addresses with inbound packets. For example:
static (inside,outside) 10.2.2.128 10.1.1.128 netmask 255.255.255.128
The ASA responds to global address 10.2.2.128 as a network address and to 10.2.2.255 as the broadcast address. Without an existing translation, the ASA denies inbound packets destined for 10.2.2.128 or 10.2.2.255, and logs this message. When the suspected IP address is a host IP address, configure a separate static command with a host mask in front of the subnet static command (the first match rule for static commands). The following static commands cause the ASA to respond to 10.2.2.128 as a host address:
static (inside,outside) 10.2.2.128 10.2.2.128 netmask 255.255.255.255 static (inside,outside) 10.2.2.128 10.2.2.128 netmask 255.255.255.128
The translation may be created by traffic started from the inside host with the IP address in question. Because the ASA views a network or broadcast IP address as a host IP address with an overlapped subnet static configuration, the network address translation for both static commands must be the same.
305007
Error Message %ASA-6-305007: addrpool_free(): Orphan IP IP_address on interface interface_number Explanation The ASA has attempted to translate an address that it cannot find in any of its global pools. The ASA assumes that the address was deleted and drops the request. Recommended Action None required.
1-112
Chapter 1
305008
Error Message %ASA-3-305008: Free unallocated global IP address. Explanation The ASA kernel detected an inconsistency condition when trying to free an unallocated global IP address back to the address pool. This abnormal condition may occur if the ASA is running a Stateful Failover setup, and some of the internal states are momentarily out of sync between the active unit and the standby unit. This condition is not catastrophic, and the synchronization recovers automatically. Recommended Action If the problem persists, contact the Cisco TAC.
305009
Error Message %ASA-6-305009: Built {dynamic|static} translation from interface_name [(acl-name)]:real_address [(idfw_user)] to interface_name:mapped_address Explanation An address translation slot was created. The slot translates the source address from the local side to the global side. In reverse, the slot translates the destination address from the global side to the local side. Recommended Action None required.
305010
Error Message %ASA-6-305010: Teardown {dynamic|static} translation from interface_name:real_address [(idfw_user)] to interface_name:mapped_address duration time Explanation The address translation slot was deleted. Recommended Action None required.
305011
Error Message %ASA-6-305011: Built {dynamic|static} {TCP|UDP|ICMP} translation from interface_name:real_address/real_port [(idfw_user)] to interface_name:mapped_address/mapped_port Explanation A TCP, UDP, or ICMP address translation slot was created. The slot translates the
source socket from the local side to the global side. In reverse, the slot translates the destination socket from the global side to the local side.
1-113
Syslog Messages
305012
Error Message %ASA-6-305012: Teardown {dynamic|static} {TCP|UDP|ICMP} translation from interface_name [(acl-name)]:real_address/{real_port|real_ICMP_ID} [(idfw_user)] to interface_name:mapped_address/{mapped_port|mapped_ICMP_ID} duration time Explanation The address translation slot was deleted. Recommended Action None required.
305013
Error Message %ASA-5-305013: Asymmetric NAT rules matched for forward and reverse flows; Connection protocol src interface_name:source_address/source_port [(idfw_user)] dst interface_name:dst_address/dst_port [(idfw_user)] denied due to NAT reverse path failure. Explanation An attempt to connect to a mapped host using its actual address was rejected. Recommended Action When not on the same interface as the host using NAT, use the mapped address instead of the actual address to connect to the host. In addition, enable the inspect command if the application embeds the IP address.
308001
Error Message %ASA-6-308001: console enable password incorrect for number tries (from IP_address) Explanation This is a ASA management message. This message appears after the specified number
of times a user incorrectly types the password to enter privileged mode. The maximum is three attempts.
Recommended Action Verify the password and try again.
1-114
Chapter 1
308002
Error Message %ASA-4-308002: static global_address inside_address netmask netmask overlapped with global_address inside_address Explanation The IP addresses in one or more static command statements overlap. global_address is the global address, which is the address on the lower security interface, and inside_address is the local address, which is the address on the higher security-level interface. Recommended Action Use the show static command to view the static command statements in your configuration and fix the commands that overlap. The most common overlap occurs if you specify a network address such as 10.1.1.0, and in another static command you specify a host within that range, such as 10.1.1.5.
311001
Error Message %ASA-6-311001: LU loading standby start Explanation Stateful Failover update information was sent to the standby ASA when the standby ASA is first to be online. Recommended Action None required.
311002
Error Message %ASA-6-311002: LU loading standby end Explanation Stateful Failover update information stopped sending to the standby ASA. Recommended Action None required.
311003
Error Message %ASA-6-311003: LU recv thread up Explanation An update acknowledgment was received from the standby ASA. Recommended Action None required.
1-115
Syslog Messages
311004
Error Message %ASA-6-311004: LU xmit thread up Explanation A Stateful Failover update was transmitted to the standby ASA. Recommended Action None required.
312001
Error Message %ASA-6-312001: RIP hdr failed from IP_address: cmd=string, version=number domain=string on interface interface_name Explanation The ASA received a RIP message with an operation code other than reply, the message
has a version number different from what is expected on this interface, and the routing domain entry was nonzero. Another RIP device may not be configured correctly to communicate with the ASA.
313001
Error Message %ASA-3-313001: Denied ICMP type=number, code=code from IP_address on interface interface_name Explanation When using the icmp command with an access list, if the first matched entry is a permit
entry, the ICMP packet continues processing. If the first matched entry is a deny entry, or an entry is not matched, the ASA discards the ICMP packet and generates this message. The icmp command enables or disables pinging to an interface. With pinging disabled, the ASA cannot be detected on the network. This feature is also referred to as configurable proxy pinging.
Recommended Action Contact the administrator of the peer device.
313004
Error Message %ASA-4-313004:Denied ICMP type=icmp_type, from source_address on interface interface_name to dest_address:no matching session Explanation ICMP packets were dropped by the ASA because of security checks added by the
stateful ICMP feature that are usually either ICMP echo replies without a valid echo request already passed across the ASA or ICMP error messages not related to any TCP, UDP, or ICMP session already established in the ASA.
1-116
Chapter 1
313005
Error Message %ASA-4-313005: No matching connection for ICMP error message: icmp_msg_info on interface_name interface. Original IP payload: embedded_frame_info icmp_msg_info = icmp src src_interface_name:src_address [([idfw_user | FQDN_string], sg_info)] dst dest_interface_name:dest_address [([idfw_user | FQDN_string], sg_info)] (type icmp_type, code icmp_code) embedded_frame_info = prot src source_address/source_port [([idfw_user | FQDN_string], sg_info)] dst dest_address/dest_port [(idfw_user|FQDN_string), sg_info] Explanation ICMP error packets were dropped by the ASA because the ICMP error messages are not
related to any session already established in the ASA.

Recommended Action If the cause is an attack, you can deny the host by using ACLs.
313008
Error Message %ASA-3-313008: Denied ICMPv6 type=number, code=code from IP_address on interface interface_name Explanation When using the icmp command with an access list, if the first matched entry is a permit entry, the ICMPv6 packet continues processing. If the first matched entry is a deny entry, or an entry is not matched, the ASA discards the ICMPv6 packet and generates this message.
The icmp command enables or disables pinging to an interface. When pinging is disabled, the ASA is undetectable on the network. This feature is also referred to as configurable proxy pinging.
Recommended Action Contact the administrator of the peer device.
313009
Error Message %ASA-4-313009: Denied invalid ICMP code icmp-code, for src-ifc:src-address/src-port (mapped-src-address/mapped-src-port) to dest-ifc:dest-address/dest-port (mapped-dest-address/mapped-dest-port) [user], ICMP id icmp-id, ICMP type icmp-type Explanation An ICMP echo request/reply packet was received with a malformed code(non-zero). Recommended Action If it is an intermittent event, no action is required. If the cause is an attack, you can deny the host using the ACLs.
1-117
Syslog Messages
314001
Error Message %ASA-6-314001: Pre-allocated RTSP UDP backconnection for src_intf:src_IP to dst_intf:dst_IP/dst_port. Explanation The ASA opened a UDP media channel for the RTSP client that was receiving data from
the server.

src_intfSource interface name src_IPSource interface IP address dst_intfDestination interface name dst_IPDestination IP address dst_portDestination port
314002
Error Message %ASA-6-314002: RTSP failed to allocate UDP media connection from src_intf:src_IP to dst_intf:dst_IP/dst_port: reason_string. Explanation The ASA cannot open a new pinhole for the media channel.
src_intfSource interface name src_IPSource interface IP address dst_intfDestination interface name dst_IPDestination IP address dst_portDestination port reason_stringPinhole already exists/Unknown
Recommended Action If the reason is unknown, check the free memory available by running the show memory command, or the number of connections used by running the show conn command, because the ASA is low on memory.
314003
Error Message %ASA-6-314003: Dropped RTSP traffic from src_intf:src_ip due to: reason. Explanation The RTSP message violated the user-configured RTSP security policy, either because it contains a port from the reserve port range, or it contains a URL with a length greater than the maximum limit allowed.
src_intfSource interface name src_IPSource interface IP address reasonThe reasons may be one of the following:
1-118
Chapter 1
- Endpoint negotiating media ports in the reserved port range from 0 to 1024 - URL length of url length bytes exceeds the maximum url length limit bytes
Recommended Action Investigate why the RTSP client sends messages that violate the security policy. If the requested URL is legitimate, you can relax the policy by specifying a longer URL length limit in the RTSP policy map.
314004
Error Message %ASA-6-314004: RTSP client src_intf:src_IP accessed RTSP URL RTSP URL Explanation An RTSP client tried to access an RTSP server.
src_intfSource interface name src_IPSource interface IP address RTSP URLRTSP server URL
314005
Error Message %ASA-6-314005: RTSP client src_intf:src_IP denied access to URL RTSP_URL. Explanation An RTSP client tried to access a prohibited site.
src_intfSource interface name src_IPSource interface IP address RTSP_URLRTSP server URL
314006
Error Message %ASA-6-314006: RTSP client src_intf:src_IP exceeds configured rate limit of rate for request_method messages. Explanation A specific RTSP request message exceeded the configured rate limit of RTSP policy.
src_intfSource interface name src_IPSource interface IP address rateConfigured rate limit
1-119
Syslog Messages
request_methodType of request message
Recommended Action Investigate why the specific RTSP request message from the client exceeded
the rate limit.
315004
Error Message %ASA-3-315004: Fail to establish SSH session because RSA host key retrieval failed. Explanation The ASA cannot find the RSA host key, which is required for establishing an SSH session. The ASA host key may be absent because it was not generated or because the license for this ASA does not allow DES or 3DES encryption. Recommended Action From the ASA console, enter the show crypto key mypubkey rsa command to verify that the RSA host key is present. If the host key is not present, enter the show version command to verify that DES or 3DES is allowed. If an RSA host key is present, restart the SSH session. To generate the RSA host key, enter the crypto key mypubkey rsa command.
1-120
Chapter 1
315011
Error Message %ASA-6-315011: SSH session from IP_address on interface interface_name for user user disconnected by SSH server, reason: reason Explanation An SSH session has ended. If a user enters quit or exit, the terminated normally
message appears. If the session disconnected for another reason, the text describes the reason. Table 1-4 lists the possible reasons why a session disconnected.
Table 1-4 SSH Disconnect Reasons
Text String Bad checkbytes CRC check failed
Explanation A mismatch was detected in the check bytes during an SSH key exchange.
Action Restart the SSH session.
None required. If this message persists, The CRC value computed for a call Cisco TAC. particular packet does not match the CRC value embedded in the packet; the packet is bad. Decryption of an SSH session key failed during an SSH key exchange. A nonprotocol version message was received during an SSH version exchange. This message indicates either an error internal to SSH on the ASA or an RSA key may not have been entered on the ASA or cannot be retrieved. Check the RSA host key and try again. Check the SSH client, to ensure it is a supported version. From the ASA console, enter the show crypto key mypubkey rsa command to verify that the RSA host key is present. If the host key is not present, enter the show version command to verify that DES or 3DES is allowed. If an RSA host key is present, restart the SSH session. To generate the RSA host key, enter the crypto key mypubkey rsa command. Enter the show version command to determine which features your license supports, then reconfigure the SSH client to use the supported cipher. None required.
Decryption failure Format error
Internal error
Invalid cipher type
The SSH client requested an unsupported cipher.
Invalid message The length of SSH message arriving at length the ASA exceeds 262,144 bytes or is shorter than 4096 bytes. The data may be corrupted.
Invalid message The ASA received a non-SSH message, Check whether the peer is an SSH client. If type or an unsupported or unwanted SSH it is a client supporting SSHv1, and this message. message persists, from the ASA serial console enter the debug ssh command and capture the debugging messages. Then contact the Cisco TAC.
1-121
Syslog Messages
Table 1-4
SSH Disconnect Reasons (continued)
Text String Out of memory
Explanation
Action
Restart the SSH session later. This message appears when the ASA cannot allocate memory for use by the SSH server, probably when the ASA is busy with high traffic. User authentication failed. Ask the user to verify username and password.
Rejected by server Reset by client
An SSH client sent the None required. SSH_MSG_DISCONNECT message to the ASA. None required. Encourage users to exit the client gracefully instead of just exiting.
status code: hex Users closed the SSH client window (hex) (running on Windows) instead of entering quit or exit at the SSH console. Terminated by operator Time-out activated The SSH session was terminated by entering the ssh disconnect command at the ASA console.
None required.
The SSH session timed out because the Restart the SSH connection. You can use duration specified by the ssh timeout the ssh timeout command to increase the command was exceeded. default value of 5 minutes up to 60 minutes if required.
316001
Error Message %ASA-3-316001: Denied new tunnel to IP_address. VPN peer limit (platform_vpn_peer_limit) exceeded Explanation If more VPN tunnels (ISAKMP/IPsec) are concurrently trying to be established than are supported by the platform VPN peer limit, then the excess tunnels are aborted. Recommended Action None required.
316002
Error Message %ASA-3-316002: VPN Handle error: protocol=protocol, src in_if_num:src_addr, dst out_if_num:dst_addr Explanation The ASA cannot create a VPN handle, because the VPN handle already exists.
protocolThe protocol of the VPN flow in_if_numThe ingress interface number of the VPN flow src_addrThe source IP address of the VPN flow
1-122
Chapter 1
out_if_numThe egress interface number of the VPN flow dst_addrThe destination IP address of the VPN flow
Recommended Action This message may occur during normal operation; however, if the message occurs repeatedly and a major malfunction of VPN-based applications occurs, a software defect may be the cause. Enter the following commands to collect more information and contact the Cisco TAC to investigate the issue further:
capture name type asp-drop vpn-handle-error show asp table classify crypto detail show asp table vpn-context
317001
Error Message %ASA-3-317001: No memory available for limit_slow Explanation The requested operation failed because of a low-memory condition. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
317002
Error Message %ASA-3-317002: Bad path index of number for IP_address, number max Explanation A software error occurred. Recommended Action If the problem persists, contact the Cisco TAC.
317003
Error Message %ASA-3-317003: IP routing table creation failure - reason Explanation An internal software error occurred, which prevented the creation of a new IP routing
table.
Recommended Action Copy the message exactly as it appears, and report it to Cisco TAC.
1-123
Syslog Messages
317004
Error Message %ASA-3-317004: IP routing table limit warning Explanation The number of routes in the named IP routing table has reached the configured warning
limit.
Recommended Action Reduce the number of routes in the table, or reconfigure the limit.
317005
Error Message %ASA-3-317005: IP routing table limit exceeded - reason, IP_address netmask Explanation Additional routes will be added to the table. Recommended Action Reduce the number of routes in the table, or reconfigure the limit.
317006
Error Message %ASA-3-317006: Pdb index error pdb, pdb_index, pdb_type Explanation The index into the PDB is out of range.
pdbProtocol Descriptor Block, the descriptor of the PDB index error pdb_indexThe PDB index identifier pdb_typeThe type of the PDB index error
Recommended Action If the problem persists, copy the error message exactly as it appears on the console or in the system log, contact the Cisco TAC, and provide the representative with the collected information.
317007
Error Message %ASA-6-317007: Added route_type route dest_address netmask via gateway_address [distance/metric] on interface_name route_type Explanation A new route has been added to the routing table.
Routing protocol type: C connected, S static, I IGRP, R RIP, M mobile B BGP, D EIGRP, EX - EIGRP external, O - OSPF IA - OSPF inter area, N1 - OSPF NSSA external type 1 N2 - OSPF NSSA external type 2, E1 - OSPF external type 1
1-124
Chapter 1
E2 - OSPF external type 2, E EGP, i - IS-IS, L1 - IS-IS level-1 L2 - IS-IS level-2, ia - IS-IS inter area

dest_addressThe destination network for this route netmaskThe netmask for the destination network gateway_addressThe address of the gateway by which the destination network is reached distanceAdministrative distance for this route metricMetric for this route interface_nameNetwork interface name through which the traffic is routed
317008
Error Message %ASA-6-317007: Deleted route_type route dest_address netmask via gateway_address [distance/metric] on interface_name route_type Explanation A new route has been deleted from the routing table.
Routing protocol type: C connected, S static, I IGRP, R RIP, M mobile B BGP, D EIGRP, EX - EIGRP external, O - OSPF IA - OSPF inter area, N1 - OSPF NSSA external type 1 N2 - OSPF NSSA external type 2, E1 - OSPF external type 1 E2 - OSPF external type 2, E EGP, i - IS-IS, L1 - IS-IS level-1 L2 - IS-IS level-2, ia - IS-IS inter area

dest_addressThe destination network for this route netmaskThe netmask for the destination network gateway_addressThe address of the gateway by which the destination network is reached distanceAdministrative distance for this route metricMetric for this route interface_nameNetwork interface name through which the traffic is routed
318001
Error Message %ASA-3-318001: Internal error: reason Explanation An internal software error occurred. This message occurs at five-second intervals. Recommended Action Copy the message exactly as it appears, and report it to the Cisco TAC.
1-125
Syslog Messages
318002
Error Message %ASA-3-318002: Flagged as being an ABR without a backbone area Explanation The router was flagged as an area border router without a backbone area configured in
the router. This message occurs at five-second intervals.

Recommended Action Restart the OSPF process.
318003
Error Message %ASA-3-318003: Reached unknown state in neighbor state machine Explanation An internal software error occurred. This message occurs at five-second intervals. Recommended Action Copy the message exactly as it appears, and report it to the Cisco TAC.
318004
Error Message %ASA-3-318004: area string lsid IP_address mask netmask adv IP_address type number Explanation The OSPF process had a problem locating the link state advertisement, which might
lead to a memory leak.

318005
Error Message %ASA-3-318005: lsid ip_address adv IP_address type number gateway gateway_address metric number network IP_address mask netmask protocol hex attr hex net-metric number Explanation OSPF found an inconsistency between its database and the IP routing table. Recommended Action If the problem persists, contact the Cisco TAC.
318006
Error Message %ASA-3-318006: if interface_name if_state number Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears, and report it to the Cisco TAC.
1-126
Chapter 1
318007
Error Message %ASA-3-318007: OSPF is enabled on interface_name during idb initialization Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears, and report it to the Cisco TAC.
318008
Error Message %ASA-3-318008: OSPF process number is changing router-id. Reconfigure virtual link neighbors with our new router-id Explanation The OSPF process is being reset, and it is going to select a new router ID. This action will bring down all virtual links. Recommended Action Change the virtual link configuration on all of the virtual link neighbors to reflect the new router ID.
318009
Error Message %ASA-3-318009: OSPF: Attempted reference of stale data encountered in function, line: line_num Explanation OSPF is running and has tried to reference some related data structures that have been
removed elsewhere. Clearing interface and router configurations may resolve the problem. However, if this message appears, some sequence of steps caused premature deletion of data structures and this needs to be investigated.

functionThe function that received the unexpected event line_num Line number in the code
318101
Error Message %ASA-3-318101: Internal error: REASON Explanation An internal software error has occurred.
REASONThe detailed cause of the event
1-127
Syslog Messages
318102
Error Message %ASA-3-318102: Flagged as being an ABR without a backbone area Explanation The router was flagged as an Area Border Router (ABR) without a backbone area in the
router.
318103
Error Message %ASA-3-318103: Reached unknown state in neighbor state machine Explanation An internal software error has occurred. Recommended Action None required.
318104
Error Message %ASA-3-318104: DB already exist: area AREA_ID_STR lsid i adv i type 0x x Explanation OSPF has a problem locating the LSA, which could lead to a memory leak.
AREA_ID_STRA string representing the area iAn integer value xA hexadecimal representation of an integer value
318105
Error Message %ASA-3-318105: lsid i adv i type 0x x gateway i metric d network i mask i protocol #x attr #x net-metric d Explanation OSPF found an inconsistency between its database and the IP routing table.
iAn integer value xA hexadecimal representation of an integer value dA number
1-128
Chapter 1
318106
Error Message %ASA-3-318106: if IF_NAME if_state d Explanation An internal error has occurred.
IF_NAMEThe name of the affected interface dA number
318107
Error Message %ASA-3-318107: OSPF is enabled on IF_NAME during idb initialization Explanation An internal error has occurred.
IF_NAMEThe name of the affected interface
318108
Error Message %ASA-3-318108: OSPF process d is changing router-id. Reconfigure virtual link neighbors with our new router-id Explanation The OSPF process is being reset, and it is going to select a new router ID, which brings
down all virtual links. To make them work again, you need to change the virtual link configuration on all virtual link neighbors.
dA number representing the process ID
Recommended Action Change the virtual link configuration on all the virtual link neighbors to include the new router ID.
318109
Error Message %ASA-3-318109: OSPFv3 has received an unexpected message: 0x / 0x Explanation OSPFv3 has received an unexpected interprocess message.
xA hexadecimal representation of an integer value
1-129
Syslog Messages
318110
Error Message %ASA-3-318110: Invalid encrypted key s. Explanation The specified encrypted key is not valid.
sA string representing the encrypted key
Recommended Action Either specify a clear text key and enter the service password-encryption command for encryption, or ensure that the specified encrypted key is valid. If the specified encrypted key is not valid, an error message appears during system configuration.
318111
Error Message %ASA-3-318111: SPI u is already in use with ospf process d Explanation An attempt was made to use a SPI that has already been used.
uA number representing the SPI dA number representing the process ID
Recommended Action Choose a different SPI.
318112
Error Message %ASA-3-318112: SPI u is already in use by a process other than ospf process d. Explanation An attempt was made to use a SPI that has already been used.
Recommended Action Choose a different SPI. Enter the show crypto ipv6 ipsec sa command to view a list of SPIs that are already being used.
318113
Error Message %ASA-3-318113: s s is already configured with SPI u. Explanation An attempt was made to use a SPI that has already been used.
sA string representing an interface uA number representing the SPI
Recommended Action Unconfigure the SPI first, or choose a different one.
1-130
Chapter 1
318114
Error Message %ASA-3-318114: The key length used with SPI u is not valid Explanation The key length was incorrect.
uA number representing the SPI
Recommended Action Choose a valid IPsec key. An IPsec authentication key must be 32 (MD5) or 40 (SHA-1) hexidecimal digits long.
318115
Error Message %ASA-3-318115: s error occured when attempting to create an IPsec policy for SPI u Explanation An IPsec API (internal) error has occurred.
sA string representing the error uA number representing the SPI
318116
Error Message %ASA-3-318116: SPI u is not being used by ospf process d. Explanation An attempt was made to unconfigure a SPI that is not being used with OSPFv3.
Recommended Action Enter a show command to see which SPIs are used by OSPFv3.
318117
Error Message %ASA-3-318117: The policy for SPI u could not be removed because it is in use. Explanation An attempt was made to remove the policy for the indicated SPI, but the policy was still being used by a secure socket.
uA number representing the SPI
1-131
Syslog Messages
318118
Error Message %ASA-3-318118: s error occured when attemtping to remove the IPsec policy with SPI u Explanation An IPsec API (internal) error has occurred.
sA string representing the specified error uA number representing the SPI
318119
Error Message %ASA-3-318119: Unable to close secure socket with SPI u on interface s Explanation An IPsec API (internal) error has occurred.
uA number representing the SPI sA string representing the specified interface
318120
Error Message %ASA-3-318120: OSPFv3 was unable to register with IPsec Explanation An internal error has occurred. Recommended Action None required.
318121
Error Message %ASA-3-318121: IPsec reported a GENERAL ERROR: message s, count d Explanation An internal error has occurred.
sA string representing the specified message dA number representing the total number of generated messages
1-132
Chapter 1
318122
Error Message %ASA-3-318122: IPsec sent a s message s to OSPFv3 for interface s. Recovery attempt d Explanation An internal error has occurred. The system is trying to reopen the secure socket and to
recover.

sA string representing the specified message and specified interface dA number representing the total number of recovery attempts
318123
Error Message %ASA-3-318123: IPsec sent a s message s to OSPFv3 for interface IF_NAME. Recovery aborted Explanation An internal error has occurred. The maximum number of recovery attempts has been
exceeded.

sA string representing the specified message IF_NAMEThe specified interface
318125
Error Message %ASA-3-318125: Init failed for interface IF_NAME Explanation The interface initialization failed. Possible reasons include the following:
The area to which the interface is being attached is being deleted. It was not possible to create the link scope database. It was not possible to create a neighbor datablock for the local router.
Recommended Action Remove the configuration command that initializes the interface and then try
it again.
1-133
Syslog Messages
318126
Error Message %ASA-3-318126: Interface IF_NAME is attached to more than one area Explanation The interface is on the interface list for an area other than the one to which the interface
links.
IF_NAMEThe specified interface
318127
Error Message %ASA-3-318127: Could not allocate or find the neighbor Explanation An internal error has occurred. Recommended Action None required.
319001
Error Message %ASA-3-319001: Acknowledge for arp update for IP address dest_address not received (number). Explanation The ARP process in the ASA lost internal synchronization because the ASA was
overloaded.
Recommended Action None required. The failure is only temporary. Check the average load of the
ASA and make sure that it is not used beyond its capabilities.
319002
Error Message %ASA-3-319002: Acknowledge for route update for IP address dest_address not received (number). Explanation The routing module in the ASA lost internal synchronization because the ASA was
overloaded.
ASA and make sure that it is not used beyond its capabilities.
1-134
Chapter 1
319003
Error Message %ASA-3-319003: Arp update for IP address address to NPn failed. Explanation When an ARP entry has to be updated, a message is sent to the network processor (NP)
in order to update the internal ARP table. If the module is experiencing high utilization of memory or if the internal table is full, the message to the NP may be rejected and this message generated.
Recommended Action Verify if the ARP table is full. If it is not full, check the load of the module by reviewing the CPU utilization and connections per second. If CPU utilization is high and/or there is a large number of connections per second, normal operations will resume when the load returns to normal.
319004
Error Message %ASA-3-319004: Route update for IP address dest_address failed (number). Explanation The routing module in the ASA lost internal synchronization because the system was
overloaded.
system and make sure that it is not used beyond its capabilities.
320001
Error Message %ASA-3-320001: The subject name of the peer cert is not allowed for connection Explanation When the ASA is an easy VPN remote device or server, the peer certificate includes
asubject name that does not match the output of the ca verifycertdn command. A man-in-the-middle attack might be occurring, where a device spoofs the peer IP address and tries to intercept a VPN connection from the ASA.
321001
Error Message %ASA-5-321001: Resource var1 limit of var2 reached. Explanation A configured resource usage or rate limit for the indicated resource was reached. Recommended Action None required.
1-135
Syslog Messages
321002
Error Message %ASA-5-321002: Resource var1 rate limit of var2 reached. Explanation A configured resource usage or rate limit for the indicated resource was reached. Recommended Action None required.
321003
Error Message %ASA-6-321003: Resource var1 log level of var2 reached. Explanation A configured resource usage or rate logging level for the indicated resource was
reached.
321004
Error Message %ASA-6-321004: Resource var1 rate log level of var2 reached Explanation A configured resource usage or rate logging level for the indicated resource was
reached.
321005
Error Message %ASA-2-321005: System CPU utilization reached utilization % Explanation The system CPU utilization has reached 95 percent or more and remains at this level for
five minutes.
utilization %The percentage of CPU being used
Recommended Action If this message occurs periodically, you can ignore it. If it repeats frequently,
check the output of the show cpu command and verify the CPU usage. If it is high, contact the Cisco TAC.
1-136
Chapter 1
321006
Error Message %ASA-2-321006: System memory usage reached utilization % Explanation The system memory usage has reached 80 percent or more and remains at this level for
five minutes.
utilization %The percentage of CPU being used
Recommended Action If this message occurs periodically, you can ignore it. If it repeats frequently,
check the output of the show memory command and verify the memory usage. If it is high, contact the Cisco TAC.
321007
Error Message %ASA-3-321007: System is low on free memory blocks of size block_size (free_blocks CNT out of max_blocks MAX) Explanation The system is low on free blocks of memory. Running out of blocks may result in traffic
disruption.

block_sizeThe block size of memory (for example, 4, 1550, 8192) free_blocksThe number of free blocks, as shown in the CNT column after using the show blocks command max_blocksThe maximum number of blocks that the system can allocate, as shown in the MAX column after using the show blocks command
Recommended Action Use the show blocks command to monitor the amount of free blocks in the CNT column of the output for the indicated block size. If the CNT column remains zero, or very close to it for an extended period of time, then the ASA may be overloaded or running into another issue that needs additional investigation.
322001
Error Message %ASA-3-322001: Deny MAC address MAC_address, possible spoof attempt on interface interface Explanation The ASA received a packet from the offending MAC address on the specified interface, but the source MAC address in the packet is statically bound to another interface in the configuration. Either a MAC-spoofing attack or a misconfiguration may be the cause. Recommended Action Check the configuration and take appropriate action by either finding the offending host or correcting the configuration.
1-137
Syslog Messages
322002
Error Message %ASA-3-322002: ARP inspection check failed for arp {request|response} received from host MAC_address on interface interface. This host is advertising MAC Address MAC_address_1 for IP Address IP_address, which is {statically|dynamically} bound to MAC Address MAC_address_2. Explanation If the ARP inspection module is enabled, it checks whether a new ARP entry advertised in the packet conforms to the statically configured or dynamically learned IP-MAC address binding before forwarding ARP packets across the ASA. If this check fails, the ARP inspection module drops the ARP packet and generates this message. This situation may be caused by either ARP spoofing attacks in the network or an invalid configuration (IP-MAC binding). Recommended Action If the cause is an attack, you can deny the host using the ACLs. If the cause is an invalid configuration, correct the binding.
322003
Error Message %ASA-3-322003:ARP inspection check failed for arp {request|response} received from host MAC_address on interface interface. This host is advertising MAC Address MAC_address_1 for IP Address IP_address, which is not bound to any MAC Address. Explanation If the ARP inspection module is enabled, it checks whether a new ARP entry advertised in the packet conforms to the statically configured IP-MAC address binding before forwarding ARP packets across the ASA. If this check fails, the ARP inspection module drops the ARP packet and generates this message. This situation may be caused by either ARP spoofing attacks in the network or an invalid configuration (IP-MAC binding). Recommended Action If the cause is an attack, you can deny the host using the ACLs. If the cause is an invalid configuration, correct the binding.
322004
Error Message %ASA-6-322004: No management IP address configured for transparent firewall. Dropping protocol protocol packet from interface_in:source_address/source_port to interface_out:dest_address/dest_port Explanation The ASA dropped a packet because no management IP address was configured in the
transparent mode.

protocolProtocol string or value interface_inInput interface name source_addressSource IP address of the packet source_portSource port of the packet interface_outOutput interface name dest_addressDestination IP address of the packet
1-138
Chapter 1
dest_portDestination port of the packet
Recommended Action Configure the device with the management IP address and mask values.
323001
Error Message %ASA-3-323001: Module module_id experienced a control channel communications failure.
Error Message %ASA-3-323001: Module in slot slot_num experienced a control channel communications failure. Explanation The ASA is unable to communicate via control channel with the module installed (in the specified slot).
module_idFor a software services module, specifies the services module name. slot_numFor a hardware services module, specifies the slot in which the failure occurred. Slot 0 indicates the system main board, and slot 1 indicates the module installed in the expansion slot.
323002
Error Message %ASA-3-323002: Module module_id is not able to shut down, shut down request not answered.
Error Message %ASA-3-323002: Module in slot slot_num is not able to shut down, shut down request not answered. Explanation The module installed did not respond to a shutdown request.
module_idFor a software services module, specifies the service module name. slot_numFor a hardware services module, specifies the slot in which the failure occurred. Slot 0 indicates the system main board, and slot 1 indicates the module installed in the expansion slot.
1-139
Syslog Messages
323003
Error Message %ASA-3-323003: Module module_id is not able to reload, reload request not answered.
Error Message %ASA-3-323003: Module in slot slotnum is not able to reload, reload request not answered. Explanation The module installed did not respond to a reload request.
module_idFor a software services module, specifies the service module name. slot_numFor a hardware services module, specifies the slot in which the failure occurred. Slot 0 indicates the system main board, and slot 1 indicates the module installed in the expansion slot.
323004
Error Message %ASA-3-323004: Module string one failed to write software newver (currently ver), reason. Hw-module reset is required before further use. Explanation The module failed to accept a software version, and will be transitioned to an
UNRESPONSIVE state. The module is not usable until the software is updated.

string oneThe text string that specifies the module newverThe new version number of software that was not successfully written to the module (for example, 1.0(1)0) verThe current version number of the software on the module (for example, 1.0(1)0) reasonThe reason the new version cannot be written to the module. The possible values for reason include the following: - write failure - failed to create a thread to write the image
Recommended Action If the module software cannot be updated, it will not be usable. If the problem persists, contact the Cisco TAC.
1-140
Chapter 1
323005
Error Message %ASA-3-323005: Module module_id can not be started completely
Error Message %ASA-3-323005: Module in slot slot_num can not be started completely Explanation This message indicates that the module can not be started completely. The module will
remain in the UNRESPONSIVE state until this condition is corrected. A module that is not fully seated in the slot is the most likely cause.

module_idFor a software services module, specifies the service module name. slot_numFor a hardware services module, specifies the slot number that contains the module.
Recommended Action Verify that the module is fully seated and check to see if any status LEDs on the module are on. It may take a minute after fully reseating the module for the ASA to recognize that it is powered up. If this message appears after verifying that the module is seated and after resetting the module using either the sw-module module service-module-name reset command or the hw-module module slotnum reset command, contact the Cisco TAC.
323006
Error Message %ASA-1-323006: Module ips experienced a data channel communication failure, data channel is DOWN. Explanation A data channel communication failure occurred and the ASA was unable to forward traffic to the services module. This failure triggers a failover when the failure occurs on the active ASA in an HA configuration. The failure also results in the configured fail open or fail closed policy being enforced on traffic that would normally be sent to the services module. This message is generated whenever a communication problem over the ASA dataplane occurs between the system module and the services module, which can be caused when the services module stops, resets, is removed or disabled. Recommended Action For software services modules such as IPS, recover the module using the sw-module module ips recover command. For hardware services modules, if this message is not the result of the SSM reloading or resetting and the corresponding syslog message 505010 is not seen after the SSM returns to an UP state, reset the module using the hw-module module 1 reset command.
1-141
Syslog Messages
323007
Error Message %ASA-3-323007: Module in slot slot experienced a firware failure and the recovery is in progress. Explanation An ASA with a 4GE-SSM installed experienced a short power surge, then rebooted. As
a result, the 4GE-SSM may come online in an unresponsive state. The ASA has detected that the 4GE-SSM is unresponsive, and automatically restarts the 4GE-SSM.
324000
Error Message %ASA-3-324000: Drop GTPv version message msg_type from source_interface:source_address/source_port to dest_interface:dest_address/dest_port Reason: reason Explanation The packet being processed did not meet the filtering requirements as described in the
reason variable and is being dropped.

324001
Error Message %ASA-3-324001: GTPv0 packet parsing error from source_interface:source_address/source_port to dest_interface:dest_address/dest_port, TID: tid_value, Reason: reason Explanation There was an error processing the packet. The following are possible reasons:
Mandatory IE is missing Mandatory IE incorrect IE out of sequence Invalid message format. Optional IE incorrect Invalid TEID Unknown IE Bad length field Unknown GTP message. Message too short Unexpected message seen Null TID
1-142
Chapter 1
Version not supported
Recommended Action If this message is seen periodically, it can be ignored. If it is seen frequently, then the endpoint may be sending out bad packets as part of an attack.
324002
Error Message %ASA-3-324002: No PDP[MCB] exists to process GTPv0 msg_type from source_interface:source_address/source_port to dest_interface:dest_address/dest_port, TID: tid_value Explanation If this message was preceded by message 321100, memory allocation error, the message indicates that there were not enough resources to create the PDP context. If not, it was not preceded by message 321100. For version 0, it indicates that the corresponding PDP context cannot be found. For version 1, if this message was preceded by message 324001, then a packet processing error occurred, and the operation stopped. Recommended Action If the problem persists, determine why the source is sending packets without a
valid PDP context.
324003
Error Message %ASA-3-324003: No matching request to process GTPv version msg_type from source_interface:source_address/source_port to source_interface:dest_address/dest_port Explanation The response received does not have a matching request in the request queue and should
not be processed further.

Recommended Action If this message is seen periodically, it can be ignored. But if it is seen frequently, then the endpoint may be sending out bad packets as part of an attack.
324004
Error Message %ASA-3-324004: GTP packet with version%d from source_interface:source_address/source_port to dest_interface:dest_address/dest_port is not supported Explanation The packet being processed has a version other than the currently supported version,
which is 0 or 1. If the version number printed out is an incorrect number and is seen frequently, then the endpoint may be sending out bad packets as part of an attack.
1-143
Syslog Messages
324005
Error Message %ASA-3-324005: Unable to create tunnel from source_interface:source_address/source_port to dest_interface:dest_address/dest_port Explanation An error occurred while trying to create the tunnel for the transport protocol data units. Recommended Action If this message occurs periodically, it can be ignored. If it repeats frequently, contact the Cisco TAC.
324006
Error Message %ASA-3-324006:GSN IP_address tunnel limit tunnel_limit exceeded, PDP Context TID tid failed Explanation The GPRS support node sending the request has exceeded the maximum allowed tunnels created, so no tunnel will be created. Recommended Action Check to see whether the tunnel limit should be increased or if there is a possible attack on the network.
324007
Error Message %ASA-3-324007: Unable to create GTP connection for response from source_address/0 to dest_address/dest_port Explanation An error occurred while trying to create the tunnel for the transport protocol data units for a differentsServicing GPRS support node or gateway GPRS support node. Recommended Action Check debugging messages to see why the connection was not created correctly. If the problem persists, contact the Cisco TAC.
324008
Error Message %ASA-3-324008: No PDP exists to update the data sgsn [ggsn] PDPMCB Info REID: teid_value, Request TEID; teid_value, Local GSN: IPaddress (VPIfNum), Remove GSN: IPaddress (VPIfNum) Explanation When a GTP HA message is received on the standby unit to update the PDP with data sgsn/ggsn PDPMCB information, the PDP is not found because of a previous PDP update message that was not successfully delivered or successfully processed on the standby unit. Recommended Action If this message occurs periodically, you can ignore it. If it occurs frequently, contact the Cisco TAC.
1-144
Chapter 1
324300
Error Message %ASA-3-324300: Radius Accounting Request from from_addr has an incorrect request authenticator Explanation When a shared secret is configured for a host, the request authenticator is verified with that secret. If it fails, it is logged and packet processing stops.
from_addrThe IP address of the host sending the RADIUS accounting request
Recommended Action Check to see that the correct shared secret was configured. If it is,
double-check the source of the packet to make sure that it was not spoofed.
324301
Error Message %ASA-3-324301: Radius Accounting Request has a bad header length hdr_len, packet length pkt_len Explanation The accounting request message has a header length that is not the same as the actual
packet length, so packet processing stops.

hdr_lenThe length indicated in the request header pkt_lenThe actual packet length
Recommended Action Make sure the packet was not spoofed. If the packet is legitimate, then capture the packet and make sure the header length is incorrect, as indicated by the message. If the header length is correct, and if the problem persists, contact the Cisco TAC.
325001
Error Message %ASA-3-325001: Router ipv6_address on interface has conflicting ND (Neighbor Discovery) settings Explanation Another router on the link sent router advertisements with conflicting parameters.
ipv6_addressIPv6 address of the other router interfaceInterface name of the link with the other router
Recommended Action Verify that all IPv6 routers on the link have the same parameters in the router
advertisement for hop_limit, managed_config_flag, other_config_flag, reachable_time and ns_interval, and that preferred and valid lifetimes for the same prefix, advertised by several routers, are the same. To list the parameters per interface, enter the show ipv6 interface command.
1-145
Syslog Messages
325002
Error Message %ASA-4-325002: Duplicate address ipv6_address/MAC_address on interface Explanation Another system is using your IPv6 address.
ipv6_addressThe IPv6 address of the other router MAC_addressThe MAC address of the other system, if known; otherwise, it is considered unknown. interfaceThe interface name of the link with the other system
Recommended Action Change the IPv6 address of one of the two systems.
325004
Error Message %ASA-4-325004: IPv6 Extension Header hdr_type action configuration. protocol from src_int:src_ipv6_addr/src_port to dst_interface: dst_ipv6_addr/dst_port. Explanation A user has configured one or multiple actions over the specified IPv6 header extension.
hdr_typeCan be one of the following values: ahConfigured action over the AH extension header countConfigured action over the number of extension headers destination-optionConfigured action over the destination option extension header espConfigured action over the ESP extension header fragmentConfigured action over the fragment extension header hop-by-hopConfigured action over the hop-by-hop extension header routing-address countConfigured action over the number of addresses in the routing extension header routing-typeConfigured action over the routing type extension header actionCan be one of the following values: deniedThe packet is denied. denied/loggedThe packet is denied and logged. loggedThe packet is logged.
Recommended Action If the configured action is not expected, under the policy-map command,
check the action in the match header extension_header_type command and the parameters command, and make the correct changes. For example:
hostname (config)# policy-map type inspect ipv6 pname hostname (config-pmap)# parameters hostname (config-pmap-p)# no match header extension_header_type ! to remove the configuration hostname (config-pmap-p)# no drop ! so packets with the specified extension_header_type are not dropped
1-146
Chapter 1
hostname (config-pmap-p)# no log ! so packets with the specified extension_header_type are not logged hostname (config-pmap-p)# no drop log ! so packets with the specified extension_header_type are not dropped or logged
325005
Error Message %ASA-4-325005: Invalid IPv6 Extension Header Content: string. detail regarding protocol, ingress and egress interface Explanation An IPv6 packet with a bad extension header has been detected.
stringCan be one of the following values: - wrong extension header order - duplicate extension header - routing extension header
Recommended Action Configure the capture command to record the dropped packet, then analyze the cause of the dropped packet. If the validity check of the IPv6 extension header can be ignored, disable the validity check in the IPv6 policy map by entering the following commands:
hostname (config)# policy-map type inspect ipv6 policy_name hostname (config-pmap)# parameters hostname (config-pmap-p)# no verify-header type
325006
Error Message %ASA-4-325006: IPv6 Extension Header not in order: Type hdr_type occurs after Type hdr_type. TCP prot from inside src_int: src_ipv6_addr/src_port to dst_interface:dst_ipv6_addr/dst_port Explanation An IPv6 packet with out-of-order extension headers has been detected. Recommended Action Configure the capture command to record the dropped packet, then analyze the extension header order of the dropped packet. If out-of-order header extensions are allowed, disable the out-of-order check in the IPv6 type policy map by entering the following commands:
hostname (config)# policy-map type inspect ipv6 policy_name hostname (config-pmap)# parameters hostname (config-pmap-p)# no verify-header order
1-147
Syslog Messages
326001
Error Message %ASA-3-326001: Unexpected error in the timer library: error_message Explanation A managed timer event was received without a context or a correct type, or no handler exists. Alternatively, if the number of events queued exceeds a system limit, an attempt to process them will occur at a later time. Recommended Action If the problem persists, contact the Cisco TAC.
326002
Error Message %ASA-3-326002: Error in error_message: error_message Explanation The IGMP process failed to shut down upon request. Events that are performed in preparation for this shutdown may be out-of-sync. Recommended Action If the problem persists, contact the Cisco TAC.
326004
Error Message %ASA-3-326004: An internal error occurred while processing a packet queue Explanation The IGMP packet queue received a signal without a packet. Recommended Action If the problem persists, contact the Cisco TAC.
326005
Error Message %ASA-3-326005: Mrib notification failed for (IP_address, IP_address) Explanation A packet triggering a data-driven event was received, and the attempt to notify the
MRIB failed.
1-148
Chapter 1
326006
Error Message %ASA-3-326006: Entry-creation failed for (IP_address, IP_address) Explanation The MFIB received an entry update from the MRIB, but failed to create the entry related
to the addresses displayed. The probable cause is insufficient memory.

326007
Error Message %ASA-3-326007: Entry-update failed for (IP_address, IP_address) Explanation The MFIB received an interface update from the MRIB, but failed to create the interface related to the addresses displayed. The probable cause is insufficient memory. Recommended Action If the problem persists, contact the Cisco TAC.
326008
Error Message %ASA-3-326008: MRIB registration failed Explanation The MFIB failed to register with the MRIB. Recommended Action If the problem persists, contact the Cisco TAC.
326009
Error Message %ASA-3-326009: MRIB connection-open failed Explanation The MFIB failed to open a connection to the MRIB. Recommended Action If the problem persists, contact the Cisco TAC.
326010
Error Message %ASA-3-326010: MRIB unbind failed Explanation The MFIB failed to unbind from the MRIB. Recommended Action If the problem persists, contact the Cisco TAC.
1-149
Syslog Messages
326011
Error Message %ASA-3-326011: MRIB table deletion failed Explanation The MFIB failed to retrieve the table that was supposed to be deleted. Recommended Action If the problem persists, contact the Cisco TAC.
326012
Error Message %ASA-3-326012: Initialization of string functionality failed Explanation The initialization of a specified functionality failed. This component might still operate
without the functionality.

326013
Error Message %ASA-3-326013: Internal error: string in string line %d (%s) Explanation A fundamental error occurred in the MRIB. Recommended Action If the problem persists, contact the Cisco TAC.
326014
Error Message %ASA-3-326014: Initialization failed: error_message error_message Explanation The MRIB failed to initialize. Recommended Action If the problem persists, contact the Cisco TAC.
326015
Error Message %ASA-3-326015: Communication error: error_message error_message Explanation The MRIB received a malformed update. Recommended Action If the problem persists, contact the Cisco TAC.
1-150
Chapter 1
326016
Error Message %ASA-3-326016: Failed to set un-numbered interface for interface_name (string) Explanation The PIM tunnel is not usable without a source address. This situation occurs because a
numbered interface cannot be found, or because of an internal error.

326017
Error Message %ASA-3-326017: Interface Manager error - string in string: string Explanation An error occurred while creating a PIM tunnel interface. Recommended Action If the problem persists, contact the Cisco TAC.
326019
Error Message %ASA-3-326019: string in string: string Explanation An error occurred while creating a PIM RP tunnel interface. Recommended Action If the problem persists, contact the Cisco TAC.
326020
Error Message %ASA-3-326020: List error in string: string Explanation An error occurred while processing a PIM interface list. Recommended Action If the problem persists, contact the Cisco TAC.
326021
Error Message %ASA-3-326021: Error in string: string Explanation An error occurred while setting the SRC of a PIM tunnel interface. Recommended Action If the problem persists, contact the Cisco TAC.
1-151
Syslog Messages
326022
Error Message %ASA-3-326022: Error in string: string Explanation The PIM process failed to shut down upon request. Events that are performed in preparation for this shutdown may be out-of-sync. Recommended Action If the problem persists, contact the Cisco TAC.
326023
Error Message %ASA-3-326023: string - IP_address: string Explanation An error occurred while processing a PIM group range. Recommended Action If the problem persists, contact the Cisco TAC.
326024
Error Message %ASA-3-326024: An internal error occurred while processing a packet queue. Explanation The PIM packet queue received a signal without a packet. Recommended Action If the problem persists, contact the Cisco TAC.
326025
Error Message %ASA-3-326025: string Explanation An internal error occurred while trying to send a message. Events scheduled to occur on the receipt of a message, such as deletion of the PIM tunnel IDB, may not occur. Recommended Action If the problem persists, contact the Cisco TAC.
326026
Error Message %ASA-3-326026: Server unexpected error: error_message Explanation The MRIB failed to register a client. Recommended Action If the problem persists, contact the Cisco TAC.
1-152
Chapter 1
326027
Error Message %ASA-3-326027: Corrupted update: error_message Explanation The MRIB received a corrupt update. Recommended Action If the problem persists, contact the Cisco TAC.
326028
Error Message %ASA-3-326028: Asynchronous error: error_message Explanation An unhandled asynchronous error occurred in the MRIB API. Recommended Action If the problem persists, contact the Cisco TAC.
327001
Error Message %ASA-3-327001: IP SLA Monitor: Cannot create a new process Explanation The IP SLA monitor was unable to start a new process. Recommended Action Check the system memory. If memory is low, then this is probably the cause. Try to reenter the commands when memory is available. If the problem persists, contact the Cisco TAC.
327002
Error Message %ASA-3-327002: IP SLA Monitor: Failed to initialize, IP SLA Monitor functionality will not work Explanation The IP SLA monitor failed to initialize. This condition is caused by either the timer wheel function failing to initialize or a process not being created. Sufficient memory is probably not available to complete the task. Recommended Action Check the system memory. If memory is low, then this is probably the cause. Try to reenter the commands when memory is available. If the problem persists, contact the Cisco TAC.
1-153
Syslog Messages
327003
Error Message %ASA-3-327003: IP SLA Monitor: Generic Timer wheel timer functionality failed to initialize Explanation The IP SLA monitor cannot initialize the timer wheel. Recommended Action Check the system memory. If memory is low, then the timer wheel function did
not initialize. Try to reenter the commands when memory is available. If the problem persists, contact the Cisco TAC.
328001
Error Message %ASA-3-328001: Attempt made to overwrite a set stub function in string. Explanation A single function can be set as a callback for when a stub with a check registry is
invoked. An attempt to set a new callback failed because a callback function has already been set.
stringThe name of the function
328002
Error Message %ASA-3-328002: Attempt made in string to register with out of bounds key Explanation In the FASTCASE registry, the key has to be smaller than the size specified when the
registry was created. An attempt was made to register with a key out-of-bounds.
Recommended Action Copy the error message exactly as it appears, and report it to the Cisco TAC.
329001
Error Message %ASA-3-329001: The string0 subblock named string1 was not removed Explanation A software error has occurred. IDB subblocks cannot be removed.
string0SWIDB or HWIDB string1The name of the subblock
1-154
Chapter 1
331001
Error Message ASA-3-331001: Dynamic DNS Update for 'fqdn_name' = ip_address failed Explanation The dynamic DNS subsystem failed to update the resource records on the DNS server. This failure might occur if the ASA is unable to contact the DNS server or the DNS service is not running on the destination system.
fqdn_nameThe fully qualified domain name for which the DNS update was attempted ip_addressThe IP address of the DNS update
Recommended Action Make sure that a DNS server is configured and reachable by the ASA. If the
problem persists, contact the Cisco TAC.
331002
Error Message ASA-5-331002: Dynamic DNS type RR for ('fqdn_name' - ip_address | ip_address - 'fqdn_name') successfully updated in DNS server dns_server_ip Explanation A dynamic DNS update succeeded in the DNS server.
typeThe type of resource record, which may be A or PTR fqdn_nameThe fully qualified domain name for which the DNS update was attempted ip_addressThe IP address of the DNS update dns_server_ipThe IP address of the DNS server
332001
Error Message %ASA-3-332001: Unable to open cache discovery socket, WCCP V2 closing down. Explanation An internal error that indicates the WCCP process was unable to open the UDP socket
used to listen for protocol messages from caches.

Recommended Action Ensure that the IP configuration is correct and that at least one IP address has
been configured.
1-155
Syslog Messages
332002
Error Message %ASA-3-332002: Unable to allocate message buffer, WCCP V2 closing down. Explanation An internal error that indicates the WCCP process was unable to allocate memory to hold incoming protocol messages. Recommended Action Ensure that enough memory is available for all processes.
332003
Error Message %ASA-5-332003: Web Cache IP_address/service_ID acquired Explanation A service from the web cache of the ASA was acquired.
IP_addressThe IP address of the web cache service_IDThe WCCP service identifier
332004
Error Message %ASA-1-332004: Web Cache IP_address/service_ID lost Explanation A service from the web cache of the ASA was lost.
IP_addressThe IP address of the web cache service_IDThe WCCP service identifier
Recommended Action Verify operation of the specified web cache.
333001
Error Message %ASA-6-333001: EAP association initiated - context: EAP-context Explanation An EAP association has been initiated with a remote host.
EAP-contextA unique identifier for the EAP session, displayed as an eight-digit hexadecimal number (for example, 0x2D890AE0)
1-156
Chapter 1
333002
Error Message %ASA-5-333002: Timeout waiting for EAP response - context:EAP-context Explanation A timeout occurred while waiting for an EAP response.
EAP-contextA unique identifier for the EAP session displayed as an eight-digit hexadecimal number (for example, 0x2D890AE0)
333003
Error Message %ASA-6-333003: EAP association terminated - context:EAP-context Explanation The EAP association has been terminated with the remote host.
333004
Error Message %ASA-7-333004: EAP-SQ response invalid - context:EAP-context Explanation The EAP-Status Query response failed basic packet validation.
333005
Error Message %ASA-7-333005: EAP-SQ response contains invalid TLV(s) context:EAP-context Explanation The EAP-Status Query response has one or more invalid TLVs.
1-157
Syslog Messages
333006
Error Message %ASA-7-333006: EAP-SQ response with missing TLV(s) context:EAP-context Explanation The EAP-Status Query response is missing one or more mandatory TLVs.
333007
Error Message %ASA-7-333007: EAP-SQ response TLV has invalid length context:EAP-context Explanation The EAP-Status Query response includes a TLV with an invalid length.
333008
Error Message %ASA-7-333008: EAP-SQ response has invalid nonce TLV context:EAP-context Explanation The EAP-Status Query response includes an invalid nonce TLV.
333009
Error Message %ASA-6-333009: EAP-SQ response MAC TLV is invalid - context:EAP-context Explanation The EAP-Status Query response includes a MAC that does not match the calculated
MAC.
1-158
Chapter 1
333010
Error Message %ASA-5-333010: EAP-SQ response Validation Flags TLV indicates PV request - context:EAP-context Explanation The EAP-Status Query response includes a validation flags TLV, which indicates that the peer requested a full posture validation. Recommended Action None required.
334001
Error Message %ASA-6-334001: EAPoUDP association initiated - host-address Explanation An EAPoUDP association has been initiated with a remote host.
host-addressThe IP address of the host in dotted decimal format (for example, 10.86.7.101)
334002
Error Message %ASA-5-334002: EAPoUDP association successfully established host-address Explanation An EAPoUDP association has been successfully established with the host.
334003
Error Message %ASA-5-334003: EAPoUDP association failed to establish - host-address Explanation An EAPoUDP association has failed to establish with the host.
Recommended Action Verify the configuration of the Cisco Secure Access Control Server.
1-159
Syslog Messages
334004
Error Message %ASA-6-334004: Authentication request for NAC Clientless host host-address Explanation An authentication request was made for a NAC clientless host.
334005
Error Message %ASA-5-334005: Host put into NAC Hold state - host-address Explanation The NAC session for the host was put into the Hold state.
334006
Error Message %ASA-5-334006: EAPoUDP failed to get a response from host host-address Explanation An EAPoUDP response was not received from the host.
334007
Error Message %ASA-6-334007: EAPoUDP association terminated - host-address Explanation An EAPoUDP association has terminated with the host.
1-160
Chapter 1
334008
Error Message %ASA-6-334008: NAC EAP association initiated - host-address, EAP context: EAP-context Explanation EAPoUDP has initiated EAP with the host.
host-addressThe IP address of the host in dotted decimal format (for example, 10.86.7.101) EAP-contextA unique identifier for the EAP session displayed as an eight-digit, hexadecimal number (for example, 0x2D890AE0)
334009
Error Message %ASA-6-334009: Audit request for NAC Clientless host - Assigned_IP. Explanation An audit request is being sent for the specified assigned IP address.
Assigned_IPThe IP address assigned to the client
335001
Error Message %ASA-6-335001: NAC session initialized - host-address Explanation A NAC session has started for a remote host.
335002
Error Message %ASA-5-335002: Host is on the NAC Exception List - host-address, OS: oper-sys Explanation The client is on the NAC Exception List and is therefore not subject to posture
validation.

host-addressThe IP address of the host in dotted decimal format (for example, 10.1.1.1) oper-sysThe operating system (for example, Windows XP) of the host
1-161
Syslog Messages
335003
Error Message %ASA-5-335003: NAC Default ACL applied, ACL:ACL-name - host-address Explanation The NAC default ACL has been applied for the client.
ACL-nameThe name of the ACL being applied host-addressThe IP address of the host in dotted decimal format (for example, 10.1.1.1)
335004
Error Message %ASA-6-335004: NAC is disabled for host - host-address Explanation NAC is disabled for the remote host.
335004
Error Message %ASA-6-335004: NAC is disabled for host - host-address Explanation NAC is disabled for the remote host.
335005
Error Message %ASA-4-335005: NAC Downloaded ACL parse failure - host-address Explanation Parsing of a downloaded ACL failed.
Recommended Action Verify the configuration of the Cisco Secure Access Control Server.
1-162
Chapter 1
335006
Error Message %ASA-6-335006: NAC Applying ACL: ACL-name - host-address Explanation The name of the ACL that is being applied as a result of NAC posture validation.
335007
Error Message %ASA-7-335007: NAC Default ACL not configured - host-address Explanation A NAC default ACL has not been configured.
335008
Error Message %ASA-5-335008: NAC IPsec terminate from dynamic ACL: ACL-name host-address Explanation A dynamic ACL obtained as a result of PV requires IPsec termination.
335009
Error Message %ASA-6-335009: NAC Revalidate request by administrative action host-address Explanation A NAC Revalidate action was requested by the administrator.
1-163
Syslog Messages
335010
Error Message %ASA-6-335010: NAC Revalidate All request by administrative action num sessions Explanation A NAC Revalidate All action was requested by the administrator.
numA decimal integer that indicates the number of sessions to be revalidated
335011
Error Message %ASA-6-335011: NAC Revalidate Group request by administrative action for group-name group - num sessions Explanation A NAC Revalidate Group action was requested by the administrator.
group-nameThe VPN group name numA decimal integer that indicates the number of sessions to be revalidated
335012
Error Message %ASA-6-335012: NAC Initialize request by administrative action host-address Explanation A NAC Initialize action was requested by the administrator.
335013
Error Message %ASA-6-335013: NAC Initialize All request by administrative action -
num sessions
Explanation A NAC Initialize All action was requested by the administrator.
numA decimal integer that indicates the number of sessions to be revalidated
1-164
Chapter 1
335014
Error Message %ASA-6-335014: NAC Initialize Group request by administrative action for group-name group - num sessions Explanation A NAC Initialize Group action was requested by the administrator.
group-nameThe VPN group name numA decimal integer that indicates the number of sessions to be revalidated
336001
Error Message %ASA-3-336001 Route desination_network stuck-in-active state in EIGRP-ddb_name as_num. Cleaning up Explanation The SIA state means that an EIGRP router has not received a reply to a query from one or more neighbors within the time allotted (approximately three minutes). When this happens, EIGRP clears the neighbors that did not send a reply and logs an error message for the route that became active.
destination_networkThe route that became active ddb_nameIPv4 as_numThe EIGRP router
Recommended Action Check to see why the router did not get a response from all of its neighbors and
why the route disappeared.
336002
Error Message %ASA-3-336002: Handle handle_id is not allocated in pool. Explanation The EIGRP router is unable to find the handle for the next hop.
handle_idThe identity of the missing handle
1-165
Syslog Messages
336003
Error Message %ASA-3-336003: No buffers available for bytes byte packet Explanation The DUAL software was unable to allocate a packet buffer. The ASA may be out of
memory.
bytesNumber of bytes in the packet
Recommended Action Check to see if the ASA is out of memory by entering the show mem or show tech command. If the problem persists, contact the Cisco TAC.
336004
Error Message %ASA-3-336004: Negative refcount in pakdesc pakdesc. Explanation The reference count packet count became negative.
pakdescPacket identifier
336005
Error Message %ASA-3-336005: Flow control error, error, on interface_name. Explanation The interface is flow blocked for multicast. Qelm is the queue element, and in this case,
the last multicast packet on the queue for this particular interface.

errorError statement: Qelm on flow ready interface_nameName of the interface on which the error occurred
336006
Error Message %ASA-3-336006: num peers exist on IIDB interface_name. Explanation Peers still exist on a particular interface during or after cleanup of the IDB of the EIGRP.
numThe number of peers interface_nameThe interface name
1-166
Chapter 1
336007
Error Message %ASA-3-336007: Anchor count negative Explanation An error occurred and the count of the anchor became negative when it was released. Recommended Action If the problem persists, contact the Cisco TAC.
336008
Error Message %ASA-3-336008: Lingering DRDB deleting IIDB, dest network, nexthop address (interface), origin origin_str Explanation An interface is being deleted and some lingering DRDB exists. networkThe destination network addressThe nexthop address interfaceThe nexthop interface origin_strString defining the origin
336009
Error Message %ASA-3-336009 ddb_name as_id: Internal Error Explanation An internal error occurred.
ddb_namePDM name (for example, IPv4 PDM) as_idAutonomous system ID
336010
Error Message %ASA-5-336010 EIGRP-ddb_name tableid as_id: Neighbor address (%interface) is event_msg: msg Explanation A neighbor went up or down.
ddb_nameIPv4 tableid Internal ID for the RIB as_idAutonomous system ID addressIP address of the neighbor
1-167
Syslog Messages
interfaceName of the interface event_msg Event that is occurring for the neighbor (that is, up or down) msgReason for the event. Possible event_msg and msg value pairs include: - resync: peer graceful-restart - down: holding timer expired - up: new adjacency - down: Auth failure - down: Stuck in Active - down: Interface PEER-TERMINATION received - down: K-value mismatch - down: Peer Termination received - down: stuck in INIT state - down: peer info changed - down: summary configured - down: Max hopcount changed - down: metric changed - down: [No reason]
Recommended Action Check to see why the link on the neighbor is going down or is flapping. This may be a sign of a problem, or a problem may occur because of this.
336011
Error Message %ASA-6-336011: event event Explanation A dual event occurred. The events can be one of the following:
Redist rt change SIA Query while Active
336012
Error Message %ASA-3-336012: Interface interface_names going down and neighbor_links links exist Explanation An interface is going down or is being removed from routing through IGRP, but not all links (neighbors) have been removed from the topology table. Recommended Action If the problem persists, contact the Cisco TAC.
1-168
Chapter 1
336013
Error Message %ASA-3-336013: Route iproute, iproute_successors successors, db_successors rdbs Explanation A hardware or software error occurred. Recommended Action If the problem persists, contact the Cisco TAC.
336014
Error Message %ASA-3-336014: EIGRP_PDM_Process_name, event_log Explanation A hardware or software error occurred. Recommended Action If the problem persists, contact the Cisco TAC.
336015
Error Message %ASA-3-336015: Unable to open socket for AS as_number Explanation A hardware or software error occurred. Recommended Action If the problem persists, contact the Cisco TAC.
336016
Error Message %ASA-3-336016: Unknown timer type timer_type expiration
Explanation A hardware or software error occurred. Recommended Action If the problem persists, contact the Cisco TAC.
336019
Error Message %ASA-3-336019: process_name as_number: prefix_source threshold prefix level (prefix_threshold) reached Explanation The number of prefixes in the topology database has reached the configured or default
threshold level. The prefix source may be any of the following:

Neighbor Redistributed
1-169
Syslog Messages
Aggregate
Recommended Action Use the show eigrp accounting command to obtain details about the source of
the prefixes and take corrective action.
337001
Error Message %ASA-3-337001: Phone Proxy SRTP: Encryption failed on packet from in_ifc:src_ip/src_port to out_ifc:dest_ip/dest_port Explanation The crypto hardware was unable to do SRTP encryption.
in_ifcThe input interface src_ipThe source IP address of the packet src_portThe source port of the packet output interface dest_ipThe destination IP address of the packet dest_portThe destination port of the packet
Recommended Action If this message persists, call the Cisco TAC to debug the crypto hardware to determine why SRTP encryption is failing.
337002
Error Message %ASA-3-337002: Phone Proxy SRTP: Decryption failed on packet from in_ifc:src_ip/src_port to out_ifc:dest_ip/dest_port Explanation The crypto hardware was unable to do SRTP decryption.
Recommended Action If this message persists, call the Cisco TAC to debug the crypto hardware to determine why SRTP decryption is failing.
337003
Error Message %ASA-3-337003: Phone Proxy SRTP: Authentication tag generation failed on packet from in_ifc:src_ip/src_port to out_ifc:dest_ip/dest_port Explanation The authentication tag generation failed in the crypto hardware.
in_ifcThe input interface
1-170
Chapter 1
src_ipThe source IP address of the packet src_portThe source port of the packet output interface dest_ipThe destination IP address of the packet dest_portThe destination port of the packet
Recommended Action If this message persists, call the Cisco TAC to debug the crypto hardware to determine why SRTP generation of the authentication tag is failing.
337004
Error Message %ASA-3-337004: Phone Proxy SRTP: Authentication tag validation failed on packet from in_ifc:src_ip/src_port to out_ifc:dest_ip/dest_port Explanation The computed authentication tag is not the same as the authentication tag in the packet.
Recommended Action Check to see whether an attack is underway.
337005
Error Message %ASA-4-337005: Phone Proxy SRTP: Media session not found for media_term_ip/media_term_port for packet from in_ifc:src_ip/src_port to out_ifc:dest_ip/dest_port Explanation The ASA received an SRTP or RTP packet that was destined to go to the media
termination IP address and port, but the corresponding media session to process this packet was not found.

in_ifcThe input interface src_ipThe source IP address of the packet src_portThe source port of the packet out_ifcThe output interface dest_ipThe destination IP address of the packet dest_portThe destination port of the packet
Recommended Action If this message occurs at the end of the call, it is considered normal because the
signaling messages may have released the media session, but the endpoint is continuing to send a few SRTP or RTP packets. If this message occurs for an odd-numbered media termination port, the endpoint is sending RTCP, which must be disabled from the CUCM. If this message happens
1-171
Syslog Messages
continuously for a call, debug the signaling message transaction either using phone proxy debug commands or capture commands to determine if the signaling messages are being modified with the media termination IP address and port.
337006
Error Message %ASA-3-337006: Phone Proxy SRTP: Failed to sign file filename requested by UDP client cifc:caddr/cport for sifc:saddr/sport Explanation The crypto hardware was unable to perform encryption and create a signature for a file.
filenameThe name of the file sifcThe server interface saddrThe server IP address sportThe server port cifcThe client interface caddrThe client IP address cportThe client port
Recommended Action If this message persists, check associated messages for other errors related to the crypto hardware engine.
337007
Error Message %ASA-3-337007: Phone Proxy SRTP: Failed to find configuration file filename for UDP client cifc:caddr/cport by server sifc:saddr/sport Explanation The CUCM returns the File Not Found error when a phone requests its configuration
file.

filenameThe name of the file sifcThe server interface saddrThe server IP address sportThe server port cifcThe client interface caddrThe client IP address cportThe client port
Recommended Action Check to make sure that this phone has been configured on the CUCM.
1-172
Chapter 1
337008
Error Message %ASA-3-337008: Phone Proxy: Unable to allocate media port from media-termination address phone_proxy_ifc:media_term_IP for client_ifc:client_IP/client_port; call failed. Explanation The ASA cannot find a port to allocate for media when creating a new media session. This message may occur because the user has not provided a large enough range of ports for phone proxy use, which is determined in the media-termination address command, or that all available ports are already being used.
media-termination addressThe media termination address phone_proxy_ifcThe media termination interface name (identity) media_term_ipThe media termination IP address client_ifcThe client interface name client_ipThe client IP address client_portThe client port
Recommended Action Check the phone-proxy configuration to see the range of media ports specified
and allocate a larger range of media ports if the range was too small, provided the security policy allows it. The default port range is 16384-32767.
337009
Error Message %ASA-3-337009: Unable to create secure phone entry, interface:IPaddr is already configured for the same MAC mac_addr. Explanation You tried to register the same secure phone with a different IP address. Because an entry
for the MAC address with the old IP address was already made, you cannot have multiple entries with the same MAC address and different IP addresses.

interfaceThe interface name from which the previous entry is registered ipaddrThe IP address of the existing secure phone entry mac_addrThe MAC address of the phone
Recommended Action Check the output of the show phone-proxy secure-phones command. Use the clear command to clear the entry that is causing the issue, then register the phone with the new IP address.
1-173
Syslog Messages
338001
Error Message %ASA-4-338001: Dynamic filter monitored blacklisted protocol traffic from in_interface:src_ip_addr/src_port (mapped-ip/mapped-port) to out_interface:dest_ip_addr/dest_port, (mapped-ip/mapped-port), source malicious address resolved from local or dynamic list: domain name, threat-level: level_value, category: category_name Explanation Traffic from a blacklisted domain in the dynamic filter database has appeared. The
threat level is a string that shows one of the following values: none, very-low, low, moderate, high, and very-high. The category is a string that shows the reason why a domain name is blacklisted (for example, botnet, Trojan, and spyware).
Recommended Action Access to a malicious site has been logged. Use the internal IP address to trace
the infected machine, or enter the dynamic-filter drop blacklist command to automatically drop such traffic.
338002
Error Message %ASA-4-338002: Dynamic filter monitored blacklisted protocol traffic from in_interface:src_ip_addr/src_port (mapped-ip/mapped-port) to out_interface:dest_ip_addr/dest_port (mapped-ip/mapped-port), destination malicious address resolved from local or dynamic list: domain name, threat-level: level_value, category: category_name Explanation Traffic to a blacklisted domain name in the dynamic filter database has appeared. The
1-174
Chapter 1
338003
Error Message %ASA-4-338003: Dynamic filter monitored blacklisted protocol traffic from in_interface:src_ip_addr/src_port (mapped-ip/mapped-port) to out_interface:dest_ip_addr/dest_port, (mapped-ip/mapped-port), source malicious address resolved from local or dynamic list: ip address/netmask, threat-level: level_value, category: category_name Explanation Traffic from a blacklisted IP address in the dynamic filter database has appeared. The threat level is a string that shows one of the following values: none, very-low, low, moderate, high, and very-high. The category is a string that shows the reason why a domain name is blacklisted (for example, botnet, Trojan, and spyware). Recommended Action Access to a malicious site has been logged. Use the internal IP address to trace
338004
Error Message %ASA-4-338004: Dynamic filter monitored blacklisted protocol traffic from in_interface:src_ip_addr/src_port (mapped-ip/mapped-port) to out_interface:dest_ip_addr/dest_port (mapped-ip/mapped-port), destination malicious address resolved from local or dynamic list: ip address/netmask, threat-level: level_value, category: category_name Explanation Traffic to a blacklisted IP address in the dynamic filter database has appeared. The threat
level is a string that shows one of the following values: none, very-low, low, moderate, high, and very-high. The category is a string that shows the reason why a domain name is blacklisted (for example, botnet, Trojan, and spyware).
338005
Error Message %ASA-4-338005: Dynamic filter dropped blacklisted protocol traffic from in_interface:src_ip_addr/src_port (mapped-ip/mapped-port) to out_interface:dest_ip_addr/dest_port (mapped-ip/mapped-port), source malicious address resolved from local or dynamic list: domain name, threat-level: level_value, category: category_name Explanation Traffic from a black-listed domain name in the dynamic filter database was denied. The
1-175
Syslog Messages
338006
Error Message %ASA-4-338006: Dynamic filter dropped blacklisted protocol traffic from in_interface:src_ip_addr/src_port (mapped-ip/mapped-port) to out_interface:dest_ip_addr/dest_port (mapped-ip/mapped-port), destination malicious address resolved from local or dynamic list: domain name, threat-level: level_value, category: category_name Explanation Traffic to a blacklisted domain name in the dynamic filter database was denied. The
338007
Error Message %ASA-4-338007: Dynamic filter dropped blacklisted protocol traffic from in_interface:src_ip_addr/src_port (mapped-ip/mapped-port) to out_interface:dest_ip_addr/dest_port (mapped-ip/mapped-port), source malicious address resolved from local or dynamic list: ip address/netmask, threat-level: level_value, category: category_name Explanation Traffic from a blacklisted IP address in the dynamic filter database was denied. The threat level is a string that shows one of the following values: none, very-low, low, moderate, high, and very-high. The category is a string that shows the reason why a domain name is blacklisted (for example, botnet, Trojan, and spyware). Recommended Action None required.
338008
Error Message %ASA-4-338008: Dynamic filter dropped blacklisted protocol traffic from in_interface:src_ip_addr/src_port (mapped-ip/mapped-port) to out_interface:dest_ip_addr/dest_port (mapped-ip/mapped-port), destination malicious address resolved from local or dynamic list: ip address/netmask, threat-level: level_value, category: category_name Explanation Traffic to a blacklisted IP address in the dynamic filter database was denied. The threat level is a string that shows one of the following values: none, very-low, low, moderate, high, and very-high. The category is a string that shows the reason why a domain name is blacklisted (for example, botnet, Trojan, and spyware). Recommended Action None required.
1-176
Chapter 1
338101
Error Message %ASA-4-338101: Dynamic filter action whitelisted protocol traffic from in_interface:src_ip_addr/src_port (mapped-ip/mapped-port) to out_interface:dest_ip_addr/dest_port, (mapped-ip/mapped-port), source malicious address resolved from local or dynamic list: domain name Explanation Traffic from a whitelisted domain in the dynamic filter database has appeared. Recommended Action None required.
338102
Error Message %ASA-4-338102: Dynamic filter action whitelisted protocol traffic from in_interface:src_ip_addr/src_port (mapped-ip/mapped-port) to out_interface:dest_ip_addr/dest_port (mapped-ip/mapped-port), destination malicious address resolved from local or dynamic list: domain name Explanation Traffic to a whitelisted domain name in the dynamic filter database has appeared. Recommended Action None required.
338103
Error Message %ASA-4-338103: Dynamic filter action whitelisted protocol traffic from in_interface:src_ip_addr/src_port (mapped-ip/mapped-port) to out_interface:dest_ip_addr/dest_port, (mapped-ip/mapped-port), source malicious address resolved from local or dynamic list: ip address/netmask Explanation Traffic from a whitelisted IP address in the dynamic filter database has appeared. Recommended Action None required.
338104
Error Message %ASA-4-338104: Dynamic filter action whitelisted protocol traffic from in_interface:src_ip_addr/src_port (mapped-ip/mapped-port) to out_interface:dest_ip_addr/dest_port (mapped-ip/mapped-port), destination malicious address resolved from local or dynamic list: ip address/netmask Explanation Traffic to a whitelisted IP address in the dynamic filter database has appeared. Recommended Action None required.
1-177
Syslog Messages
338201
Error Message %ASA-4-338201: Dynamic filter monitored greylisted protocol traffic from in_interface:src_ip_addr/src_port (mapped-ip/mapped-port) to out_interface:dest_ip_addr/dest_port, (mapped-ip/mapped-port), source malicious address resolved from local or dynamic list: domain name, threat-level: level_value, category: category_name Explanation Traffic from a greylisted domain in the dynamic filter database has appeared. The threat
level is a string that shows one of the following values: none, very-low, low, moderate, high, and very-high. The category is a string that shows the reason why a domain name is blacklisted (for example, botnet, Trojan, and spyware).
the infected machine, or enter the dynamic-filter drop blacklist command and the dynamic-filter ambiguous-is-black command to automatically drop such traffic.
338202
Error Message %ASA-4-338202: Dynamic filter monitored greylisted protocol traffic from in_interface:src_ip_addr/src_port (mapped-ip/mapped-port) to out_interface:dest_ip_addr/dest_port (mapped-ip/mapped-port), destination malicious address resolved from local or dynamic list: domain name, threat-level: level_value, category: category_name Explanation Traffic to a greylisted domain name in the dynamic filter database has appeared. The
the infected machine, or enter the dynamic-filter drop blacklist command and the dynamic-filter ambiguous-is-black command to automatically drop such traffic.
1-178
Chapter 1
338203
Error Message %ASA-4-338203: Dynamic filter dropped greylisted protocol traffic from in_interface:src_ip_addr/src_port (mapped-ip/mapped-port) to out_interface:dest_ip_addr/dest_port (mapped-ip/mapped-port), source malicious address resolved from local or dynamic list: domain name, threat-level: level_value, category: category_name Explanation Traffic from a greylisted domain name in the dynamic filter database was denied;
however, the malicious IP address was also resolved to domain names that are unknown to the dynamic filter database. The threat level is a string that shows one of the following values: none, very-low, low, moderate, high, and very-high. The category is a string that shows the reason why a domain name is blacklisted (for example, botnet, Trojan, and spyware).
Recommended Action Access to a malicious site was dropped. If you do not want to automatically drop greylisted traffic whose IP address matches both blacklisted domain names and unknown domain names, disable the dynamic-filter ambiguous-is-black command.
338204
Error Message %ASA-4-338204: Dynamic filter dropped greylisted protocol traffic from in_interface:src_ip_addr/src_port (mapped-ip/mapped-port) to out_interface:dest_ip_addr/dest_port (mapped-ip/mapped-port), destination malicious address resolved from local or dynamic list: domain name, threat-level: level_value, category: category_name Explanation Traffic to a greylisted domain name in the dynamic filter database was denied; however,
the malicious IP address was also resolved to domain names that are unknown to the dynamic filter database. The threat level is a string that shows one of the following values: none, very-low, low, moderate, high, and very-high. The category is a string that shows the reason why a domain name is blacklisted (for example, botnet, Trojan, and spyware).
Recommended Action Access to a malicious site was dropped. If you do not want to automatically drop greylisted traffic whose IP address matches both blacklisted domain names and unknown domain names, disable the dynamic-filter ambiguous-is-black command.
338301
Error Message %ASA-4-338301: Intercepted DNS reply for domain name from in_interface:src_ip_addr/src_port to out_interface:dest_ip_addr/dest_port, matched list Explanation A DNS reply that was present in an administrator whitelist, blacklist, or IronPort list
was intercepted.

nameThe domain name listThe list that includes the domain name, administrator whitelist, blacklist, or IronPort list
1-179
Syslog Messages
338302
Error Message %ASA-5-338302: Address ipaddr discovered for domain name from list, Adding rule Explanation An IP address that was discovered from a DNS reply to the dynamic filter rule table was
added.

ipaddrThe IP address from the DNS reply nameThe domain name listThe list that includes the domain name, administrator blacklist, or IronPort list
338303
Error Message %ASA-5-338303: Address ipaddr (name) timed out, Removing rule Explanation An IP address that was discovered from the dynamic filter rule table was removed.
ipaddrThe IP address from the DNS reply nameThe domain name
338304
Error Message %ASA-6-338304: Successfully downloaded dynamic filter data file from updater server url Explanation A new version of the data file has been downloaded.
urlThe URL of the updater server
1-180
Chapter 1
338305
Error Message %ASA-3-338305: Failed to download dynamic filter data file from updater server url Explanation The dynamic filter database has failed to download.
Recommended Action Make sure that you have a DNS configuration on the ASA so that the updater
server URL can be resolved. If you cannot ping the server from the ASA, check with your network administrator for the correct network connection and routing configuration. If you are still having problems, contact the Cisco TAC.
338306
Error Message %ASA-3-338306: Failed to authenticate with dynamic filter updater server url Explanation The ASA failed to authenticate with the dynamic filter updater server.
338307
Error Message %ASA-3-338307: Failed to decrypt downloaded dynamic filter database file Explanation The downloaded dynamic filter database file failed to decrypt. Recommended Action Contact the Cisco TAC.
338308
Error Message %ASA-5-338308: Dynamic filter updater server dynamically changed from old_server_host: old_server_port to new_server_host: new_server_port Explanation The ASA was directed to a new updater server host or port.
old_server_host:old_server_portThe previous updater server host and port new_server_host:new_server_portThe new updater server host and port
1-181
Syslog Messages
338309
Error Message %ASA-3-338309: The license on this ASA does not support dynamic filter updater feature. Explanation The dynamic filter updater is a licensed feature; however, the license on the ASA does not support this feature. Recommended Action None required.
338310
Error Message %ASA-3-338310: Failed to update from dynamic filter updater server url, reason: reason string Explanation The ASA failed to receive an update from the dynamic filter updater server.
urlThe URL of the updater server reason stringThe reason for the failure, which can be one of the following: - Failed to connect to updater server - Received invalid server response - Received invalid server manifest - Error in stored update file information - Script error - Function call error - Out of memory
Recommended Action Check the network connection to the server. Try to ping the server URL, which is shown in the output of the show dynamic-filter updater-client command. Make sure that the port is allowed through your network. If the network connection is not the problem, contact your network administrator.
339001
Error Message %ASA-3-339001: UC-IME-SIG: Ticket not found in SIP %s from %s:%A/%d to %s:%A/%d, packet dropped Explanation For UC-IME SIP signaling, all dialog-forming SIP messages received from the outside must include the X-Cisco-ViPR-Ticket header. If this header is missing from the message, the message will be dropped during SIP inspection. This header is only required when an existing SIP session (as determined by current SIP inspection rules) cannot be found for the message being inspected.
%sSIP message name (INVITE or REFER) %sSource interface name (inside or outside)
1-182
Chapter 1
%ASource IP address %dSource port %sDestination interface name (inside or outside) %ADestination IP address %dDestination port
Recommended Action Check to see if UC-IME calls are being spoofed.
339002
Error Message %ASA-3-339002: UC-IME-SIG: Invalid ticket in SIP %s from %s:%A/%d to %s:%A/%d, packet dropped, %s Explanation When UC-IME ticket inspection and validation are performed, several data checks for
timestamp validity and epoch matching, among others, are performed. If any of these checks fail, the SIP message or packet will be dropped.

%sSIP message name (INVITE or REFER) %sSource interface name (inside or outside) %ASource IP address %dSource port %sDestination interface name (inside or outside) %ADestination IP address %dDestination port %sAdditional description or data about the error condition
Recommended Action Check to see if UC-IME calls are being spoofed. Turn on UC-IME debug tracing to obtain more details about the error condition.
339003
Error Message %ASA-3-339003: UC-IME-SIG: Non-dialog forming SIP %s received from %s:%A/%d to %s:%A/%d, packet dropped Explanation When a SIP message is inspected by the UC-IME feature, checks are performed to see
if the message belongs to an existing SIP session. In a non-UC-IME scenario, a SIP request received will create a SIP session (if permitted by a configured policy). However, for the UC-IME feature, nondialog-creating SIP messages are not permitted to create a SIP session in the ASA and are dropped.

%sSIP message name (INVITE or REFER) %sSource interface name (inside or outside) %ASource IP address %dSource port
1-183
Syslog Messages
%sDestination interface name (inside or outside) %ADestination IP address %dDestination port
Recommended Action Check to see if UC-IME calls are being spoofed.
339004
Error Message %ASA-3-339004: UC-IME-SIG: Dropping SIP %s received from %s:%A/%d to %s:%A/%d, route header validation failed, %s Explanation When an outbound SIP message is inspected by the UC-IME feature, the domain name
included in the SIP route header is compared to the TLS certificate domain name. This comparison allows the UC-IME feature on the ASA to determine whether or not the SIP message is actually terminating at the intended enterprise. If a mismatch occurs, it implies that the remote end is not serving that domain, and the SIP session should be terminated.

%sSIP message name (INVITE or REFER) %sSource interface name (inside or outside) %ASource IP address %dSource port %sDestination interface name (inside or outside) %ADestination IP address %dDestination port %sAdditional description or data about the error condition (for example, the domain names received)
Recommended Action Check to see if the remote enterprise is attempting to hijack UC-IME calls.
339005
Error Message %ASA-3-339005: UC-IME-SIG: Message received from %s:%A/%d to %s:%A/%d does not contain SRTP, message dropped Explanation For UC-IME SIP signaling, SIP messages received that have media content from the
outside need to be SRTP. If this content is not SRTP, the message will be dropped during SIP inspection.

%sSource interface name (inside or outside) %ASource IP address %dSource port %sDestination interface name (inside or outside) %ADestination IP address
1-184
Chapter 1
%dDestination port
339006
Error Message %ASA-3-339006: UC-IME-Offpath: Failed to map remote UCM address %A:%d on %s interface, request from local UCM %A:%d on %s interface, reason %s Explanation For the UC-IME mapping service to work correctly, a correct configuration of global
NAT must be in place. If a misconfiguration is detected, a message will be generated to inform the administrator. At the same time, all requests from UCM clients must conform to the mapping service stun message format. All nonconforming requests will be dropped silently, and a message will be generated to notify the administrator about this occurrence.

%ARemote UCM IP address %dRemote UCM port %sInterface for the remote UCM IP address or port address %ALocal UCM IP address (used for the mapping service connection) %dLocal UCM port (used for the mapping service connection) %sInterface for the local UCM IP address or port address %sFailure reason
Recommended Action Check to see if the UC-IME Offpath and the UCM Offpath are configured
correctly.
339007
Error Message %ASA-6-339007: UC-IME-Offpath: Mapped address %A:%d on %s interface for remote UCM %A:%d on %s interface, request from local UCM %A:%d on %s interface Explanation UC-IME mapping service calls are tracked based on the mapping service client (UCM) address (IP:port) and remote UCM address (IP:port). The administrator may use this information to help debug an offpath UC-IME call.
%AMapped IP address %dMapped port %sInterface for the mapped IP address or port address %ARemote UCM IP address %dRemote UCM port %sInterface for the remote UCM IP address or port address %ALocal UCM IP address (used for the mapping-service connection) %dLocal UCM port (used for the mapping-service connection)
1-185
Syslog Messages
%sInterface for the local UCM IP address or port address
339008
Error Message %ASA-6-339008: UC-IME-Media: Media session with Call-ID %s and Session-ID %s terminated. RTP monitoring parameters: Failover state: %s, Refer msgs sent: %d, Codec payload format: %s, RTP ptime (ms): %d, Max RBLR pct( x100): %d, Max ITE count in 8 secs: %d, Max BLS (ms): %d, Max span PDV (usec): %d, Min span PDV (usec): %d, Mov avg span PDV (usec): %d, Total ITE count: %d, Total sec count: %d, Concealed sec count: %d, Severely concealed sec count: %d, Max call interval (ms): %d Explanation UC-IME media session termination is tracked based on the Call ID or Session ID. This
message is triggered at the end of a media session. The parameters returned by the RTP monitoring algorithm are included so that an administrator can adjust sensitivity parameters to improve the quality of service for a call.
%sFailover state, which can be one of the following: - No error, for an active session - No media at startup timer expired - Error in received sequence numbering - Both ITE and BLS thresholds exceeded - BLS threshold exceeded within Burst Interval - RBLR threshold exceeded within last 8 sec - Combination (> 3/4 RBLR + > 3/4 BLS) failover - No media since last received packet exceeded - ITE threshold exceeded %sCodec payload format:, which can be one of the following: - UNKNOWN - G722 - PCMU - PCMA - iLBC - iSAC
1-186
Chapter 1
339009
Error Message %ASA-6-339009: UC-IME: Ticket Password changed. Please update the same on UC-IME server. Explanation The ASA administrator is allowed to change the ticket password without knowing the old password. This message is generated to ensure that the administrator is aware of this change. The message also serves as a reminder to the administrator that if the UC-IME password is changed on the ASA, it should also be changed on the UC-IME server for everything to function correctly. Recommended Action Verify that the ticket password has been changed on the UC-IME server to match the value configured on the ASA.
340001
Error Message %ASA-3-340001: Loopback-proxy error: error_string context id context_id, context type = version/request_type/address_type client socket (internal)= client_address_internal/client_port_internal server socket (internal)= server_address_internal/server_port_internal server socket (external)= server_address_external/server_port_external remote socket (external)= remote_address_external/remote_port_external Explanation Loopback proxy allows third-party applications running on the ASA to access the network. The loopback proxy encountered an error.
context_idA unique, 32-bit context ID that is generated for each loopback client proxy request versionThe protocol version request_typeThe type of request, which can be one of the following: TC (TCP connection), TB (TCP bind), or UA (UDP association) address_typeThe types of addresses, which can be one of the following: IP4 (IPv4), IP6 (IPv6), or DNS (domain name service) client_address_internal/server_address_internalThe addresses that the loopback client and the loopback server used for communication client_port_internal/server_port_internalThe ports that the loopback client and the loopback server used for communication server_address_external/remote_address_externalThe addresses that the loopback server and the remote host used for communication server_port_external/remote_port_externalThe ports that the loopback server and the remote host used for communication error_stringThe error string that may help troubleshoot the problem
Recommended Action Copy the syslog message and contact the Cisco TAC.
1-187
Syslog Messages
340002
Error Message %ASA-6-340002: Loopback-proxy info: error_string context id context_id, context type = version/request_type/address_type client socket (internal)= client_address_internal/client_port_internal server socket (internal)= server_address_internal/server_port_internal server socket (external)= server_address_external/server_port_external remote socket (external)= remote_address_external/remote_port_external Explanation Loopback proxy allows third-party applications running on the ASA to access the network. The loopback proxy generated debugging information for use in troubleshooting.
context_idA unique, 32-bit context ID that is generated for each loopback client proxy request versionThe protocol version request_typeThe type of request, which can be one of the following: TC (TCP connection), TB (TCP bind), or UA (UDP association) address_typeThe types of addresses, which can be one of the following: IP4 (IPv4), IP6 (IPv6), or DNS (domain name service) client_address_internal/server_address_internalThe addresses that the loopback client and the loopback server used for communication client_port_internal/server_port_internalThe ports that the loopback client and the loopback server used for communication server_address_external/remote_address_externalThe addresses that the loopback server and the remote host used for communication server_port_external/remote_port_externalThe ports that the loopback server and the remote host used for communication error_stringThe error string that may help troubleshoot the problem
Recommended Action Copy the syslog message and contact the Cisco TAC.
341001
Error Message %ASA-6-341001: Policy Agent started successfully for VNMC vnmc_ip_addr Explanation The policy agent processes (DME, ducatiAG, and commonAG) started successfully.
vnmc_ip_addr-The IP address of the VNMC server
Recommended Action None.
1-188
Chapter 1
341002
Error Message %ASA-6-341002: Policy Agent stopped successfully for VNMC vnmc_ip_addr Explanation The policy agent processes (DME, ducatiAG, and commonAG) were stopped.
341003
Error Message %ASA-3-341003: Policy Agent failed to start for VNMC vnmc_ip_addr Explanation The policy agent failed to start.
Recommended Action Check for console history and the disk0:/pa/log/vnm_pa_error_status for error
messages. To retry starting the policy agent, issue the registration host command again.
341004
Error Message %ASA-3-341004: Storage device not available: Attempt to shutdown module %s failed. Explanation All SSDs have failed or been removed with the system in Up state. The system has
attempted to shut down the software module, but that attempt has failed.
%sThe software module (for example, cxsc)
Recommended Action Replace the remved or failed drive and reload the ASA.
341005
Error Message %ASA-3-341005: Storage device not available. Shutdown issued for module %s. Explanation All SSDs have failed or been removed with the system in Up state. The system is
shutting down the software module.
Recommended Action Replace the removed or failed drive and reload the software module.
1-189
Syslog Messages
341006
Error Message %ASA-3-341006: Storage device not available. Failed to stop recovery of module %s. Explanation All SSDs have failed or been removed with the system in recorvery state. The system
attempted to stop the recover, but that attempt failed.
Recommended Action Replace the removed or failed drive and reload the ASA.
341007
Error Message %ASA-3-341007: Storage device not available. Further recovery of module %s was stopped. This may take several minutes to complete. Explanation All SSDs have failed or been removed with the system in recovery state. The system is
stopping the recovery of the softwaremodule.
341008
Error Message %ASA-3-341008: Storage device not found. Auto-boot of module %s cancelled. Install drive and reload to try again. Explanation After getting the system into Up state, all SSDs have failed or been removed before
reloading the system. Because the default action during boot is to auto-boot the software module, that action is blocked because there is no storage device available.
341010
Error Message %ASA-6-341010: Storage device with serial number ser_no [inserted into | removed from] bay bay_no Explanation The ASA has detected insertion or removal events and generates this syslog message immediately. Recommended Action None required.
1-190
Chapter 1
341011
Error Message %ASA-3-341011: Storage device with serial number ser_no in bay bay_no faulty. Explanation The ASA polls the hard disk drive (HDD) health status every 10 minutes and generates
this syslog message if the HDD is in a failed state.


4000nn
Error Message %ASA-4-4000nn: IPS:number string from IP_address to IP_address on interface interface_name Explanation Messages 400000 through 400051 are Cisco Intrusion Prevention Service signature
messages.
Recommended Action See the Cisco Intrusion Prevention Service User Guide on Cisco.com.
Not all signature messages are supported by the ASA in this release. IPS messages all start with 4-4000nn and have the following format:
1-191
Syslog Messages
number
The signature number. For more information, see the Cisco Intrusion Prevention Service User Guide on Cisco.com. The signature messageapproximately the same as the NetRanger signature message. The local to remote address to which the signature applies.
string
IP_address
interface_name The name of the interface on which the signature originated. For example:
%ASA-4-400013 IPS:2003 ICMP redirect from 10.4.1.2 to 10.2.1.1 on interface dmz %ASA-4-400032 IPS:4051 UDP Snork attack from 10.1.1.1 to 192.168.1.1 on interface outside
Table 1-5 lists the supported signature messages.

Table 1-5 IPS Syslog Messages
Message Number Signature ID 400000 400001 400002 400003 400004 400005 400006 400007 400008 400009 400010 400011 400012 400013 400014 400015 400016 400017 400018 400019 400020 400021 400022 1000 1001 1002 1003 1004 1005 1006 1100 1102 1103 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012
Signature Title IP options-Bad Option List IP options-Record Packet Route IP options-Timestamp IP options-Security IP options-Loose Source Route IP options-SATNET ID IP options-Strict Source Route IP Fragment Attack IP Impossible Packet IP Fragments Overlap ICMP Echo Reply ICMP Host Unreachable ICMP Source Quench ICMP Redirect ICMP Echo Request ICMP Time Exceeded for a Datagram ICMP Parameter Problem on Datagram ICMP Timestamp Request ICMP Timestamp Reply ICMP Information Request ICMP Information Reply ICMP Address Mask Request ICMP Address Mask Reply
Signature Type Informational Informational Informational Informational Informational Informational Informational Attack Attack Attack Informational Informational Informational Informational Informational Informational Informational Informational Informational Informational Informational Informational Informational
1-192
Chapter 1
Table 1-5
IPS Syslog Messages (continued)
Message Number Signature ID 400023 400024 400025 400026 400027 400028 400029 400030 400031 400032 400033 400034 400035 400036 400037 400038 400039 400040 400041 400042 400043 400044 400045 400046 400047 400048 400049 400050 2150 2151 2154 3040 3041 3042 3153 3154 4050 4051 4052 6050 6051 6052 6053 6100 6101 6102 6103 6150 6151 6152 6153 6154 6155 6175 6180 6190
Signature Title Fragmented ICMP Traffic Large ICMP Traffic Ping of Death Attack TCP NULL flags TCP SYN+FIN flags TCP FIN only flags FTP Improper Address Specified FTP Improper Port Specified UDP Bomb attack UDP Snork attack UDP Chargen DoS attack DNS HINFO Request DNS Zone Transfer DNS Zone Transfer from High Port DNS Request for All Records RPC Port Registration RPC Port Unregistration RPC Dump Proxied RPC Request ypserv (YP server daemon) Portmap Request ypbind (YP bind daemon) Portmap Request yppasswdd (YP password daemon) Portmap Request ypupdated (YP update daemon) Portmap Request ypxfrd (YP transfer daemon) Portmap Request mountd (mount daemon) Portmap Request rexd (remote execution daemon) Attempt statd Buffer Overflow
Signature Type Attack Attack Attack Attack Attack Attack Informational Informational Attack Attack Attack Informational Informational Informational Informational Informational Informational Informational Attack Informational Informational Informational Informational Informational Informational Informational Attack
rexd (remote execution daemon) Portmap Request Informational
1-193
Syslog Messages
401001
Error Message %ASA-4-401001: Shuns cleared Explanation The clear shun command was entered to remove existing shuns from memory. An institution to keep a record of shunning activity was allowed. Recommended Action None required.
401002
Error Message %ASA-4-401002: Shun added: IP_address IP_address port port Explanation A shun command was entered, where the first IP address is the shunned host. The other
addresses and ports are optional and are used to terminate the connection if available. An institution to keep a record of shunning activity was allowed.
401003
Error Message %ASA-4-401003: Shun deleted: IP_address Explanation A single shunned host was removed from the shun database. An institution to keep a record of shunning activity was allowed. Recommended Action None required.
401004
Error Message %ASA-4-401004: Shunned packet: IP_address = IP_address on interface interface_name Explanation A packet was dropped because the host defined by IP SRC is a host in the shun database.
A shunned host cannot pass traffic on the interface on which it is shunned. For example, an external host on the Internet can be shunned on the outside interface. A record of the activity of shunned hosts was provided. This message and message %ASA-4-401005 can be used to evaluate further risk concerning this host.
1-194
Chapter 1
401005
Error Message %ASA-4-401005: Shun add failed: unable to allocate resources for IP_address IP_address port port Explanation The ASA is out of memory; a shun cannot be applied. Recommended Action The Cisco IPS should continue to attempt to apply this rule. Try to reclaim memory and reapply a shun manually, or wait for the Cisco IPS to do this.
402114
Error Message %ASA-4-402114: IPSEC: Received an protocol packet (SPI=spi, sequence number=seq_num) from remote_IP to local_IP with an invalid SPI.
protocolIPsec protocol spiIPsec Security Parameter Index seq_numIPsec sequence number remote_IPIP address of the remote endpoint of the tunnel usernameUsername associated with the IPsec tunnel local_IPIP address of the local endpoint of the tunnel
Explanation An IPsec packet was received that specifies an SPI that does not exist in the SA database. This may be a temporary condition caused by slight differences in aging of SAs between the IPsec peers, or it may be because the local SAs have been cleared. It may also indicate incorrect packets sent by the IPsec peer, which may be part of an attack. This message is rate limited to no more than one message every five seconds. Recommended Action The peer may not acknowledge that the local SAs have been cleared. If a new
connection is established from the local router, the two peers may then reestablish connection successfully. Otherwise, if the problem occurs for more than a brief period, either attempt to establish a new connection or contact the peer administrator.
402115
Error Message %ASA-4-402115: IPSEC: Received a packet from remote_IP to local_IP containing act_prot data instead of exp_prot data. Explanation An IPsec packet was received that is missing the expected ESP header. The peer is
sending packets that do not match the negotiated security policy, which may indicate an attack. This message is rate limited to no more than one message every five seconds.

remote_IPIP address of the remote endpoint of the tunnel local_IPIP address of the local endpoint of the tunnel act_protReceived IPsec protocol
1-195
Syslog Messages
exp_protExpected IPsec protocol
Recommended Action Contact the administrator of the peer.
402116
Error Message %ASA-4-402116: IPSEC: Received an protocol packet (SPI=spi, sequence number=seq_num) from remote_IP (username) to local_IP. The decapsulated inner packet doesnt match the negotiated policy in the SA. The packet specifies its destination as pkt_daddr, its source as pkt_saddr, and its protocol as pkt_prot. The SA specifies its local proxy as id_daddr/id_dmask/id_dprot/id_dport and its remote proxy as id_saddr/id_smask/id_sprot/id_sport. Explanation A decapsulated IPsec packet does not match the negotiated identity. The peer is sending
other traffic through this security association, which may be caused by a security association selection error by the peer, or it may be part of an attack. This message is rate limited to no more than one message every five seconds.

protocolIPsec protocol spiIPsec Security Parameter Index seq_numIPsec sequence number remote_IPIP address of the remote endpoint of the tunnel usernameUsername associated with the IPsec tunnel local_IPIP address of the local endpoint of the tunnel pkt_daddrDestination address from the decapsulated packet pkt_saddrSource address from the decapsulated packet pkt_protTransport protocol from the decapsulated packet id_daddrLocal proxy IP address id_dmaskLocal proxy IP subnet mask id_dprotLocal proxy transport protocol id_dportLocal proxy port id_saddrRemote proxy IP address id_smaskRemote proxy IP subnet mask id_sprotRemote proxy transport protocol id_sportRemote proxy port
Recommended Action Contact the administrator of the peer and compare policy settings.
1-196
Chapter 1
402117
Error Message %ASA-4-402117: IPSEC: Received a non-IPsec (protocol) packet from remote_IP to local_IP. Explanation The received packet matched the crypto map ACL, but it is not IPsec-encapsulated. The
IPsec peer is sending unencapsulated packets. This error can occur because of a policy setup error on the peer. For example, the firewall may be configured to only accept encrypted Telnet traffic to the outside interface port 23. If you attempt to use Telnet without IPsec encryption to access the outside interface on port 23, this message appears, but not with Telnet or traffic to the outside interface on ports other than 23. This error can also indicate an attack. This message is not generated except under these conditions (for example, it is not generated for traffic to the ASA interfaces themselves). See messages 710001, 710002, and 710003, which track TCP and UDP requests. This message is rate limited to no more than one message every five seconds.

protocolIPsec protocol remote_IPIP address of the remote endpoint of the tunnel local_IPIP address of the local endpoint of the tunnel
Recommended Action Contact the administrator of the peer to compare policy settings.
402118
Error Message %ASA-4-402118: IPSEC: Received an protocol packet (SPI=spi, sequence number seq_num) from remote_IP (username) to local_IP containing an illegal IP fragment of length frag_len with offset frag_offset. Explanation A decapsulatd IPsec packet included an IP fragment with an offset less than or equal to
128 bytes. The latest version of the security architecture for IP RFC recommends 128 bytes as the minimum IP fragment offset to prevent reassembly attacks. This may be part of an attack. This message is rate limited to no more than one message every five seconds.

protocolIPsec protocol spiIPsec Security Parameter Index seq_numIPsec sequence number remote_IPIP address of the remote endpoint of the tunnel usernameUsername associated with the IPsec tunnel local_IPIP address of the local endpoint of the tunnel frag_lenIP fragment length frag_offsetIP fragment offset in bytes
Recommended Action Contact the administrator of the remote peer to compare policy settings.
1-197
Syslog Messages
402119
Error Message %ASA-4-402119: IPSEC: Received an protocol packet (SPI=spi, sequence number=seq_num) from remote_IP (username) to local_IP that failed anti-replay checking. Explanation An IPsec packet was received with an invalid sequence number. The peer is sending
packets including sequence numbers that may have been previously used. This message indicates that an IPsec packet has been received with a sequence number outside of the acceptable window. This packet will be dropped by IPsec as part of a possible attack. This message is rate limited to no more than one message every five seconds.

Recommended Action Contact the administrator of the peer.
402120
Error Message %ASA-4-402120: IPSEC: Received an protocol packet (SPI=spi, sequence number=seq_num) from remote_IP (username) to local_IP that failed authentication. Explanation An IPsec packet was received and failed authentication. The packet is dropped. The
packet may have been corrupted in transit, or the peer may be sending invalid IPsec packets, which may indicate an attack if many of these packets were received from the same peer. This message is rate limited to no more than one message every five seconds.

Recommended Action Contact the administrator of the remote peer if many failed packets were
received.
1-198
Chapter 1
402121
Error Message %ASA-4-402121: IPSEC: Received an protocol packet (SPI=spi, sequence number=seq_num) from peer_addr (username) to lcl_addr that was dropped by IPsec (drop_reason). Explanation An IPsec packet to be decapsulated was received and subsequently dropped by the IPsec
subsystem. This may indicate a problem with the ASA configuration or with the ASA itself.

protocolIPsec protocol spiIPsec Security Parameter Index seq_numIPsec sequence number peer_addrIP address of the remote endpoint of the tunnel usernameUsername associated with the IPsec tunnel lcl_addrIP address of the local endpoint of the tunnel drop_reasonReason that the packet was dropped
402122
Error Message %ASA-4-402122: Received a cleartext packet from src_addr to dest_addr that was to be encapsulated in IPsec that was dropped by IPsec (drop_reason). Explanation A packet to be encapsulated in IPsec was received and subsequently dropped by the IPsec subsystem. This may indicate a problem with the ASA configuration or with the ASA itself.
src_addrSource IP address dest_addrDestination IP address drop_reasonReason that the packet was dropped
402123
Error Message %ASA-4-402123: CRYPTO: The accel_type hardware accelerator encountered an error (code=error_string) while executing crypto command command. Explanation An error was detected while running a crypto command with a hardware accelerator,
which may indicate a problem with the accelerator. This type of error may occur for a variety of reasons, and this message supplements the crypto accelerator counters to help determine the cause.

accel_typeHardware accelerator type error_stringCode indicating the type of error
1-199
Syslog Messages
commandCrypto command that generated the error
402124
Error Message %ASA-4-402124: CRYPTO: The ASA hardware accelerator encountered an error (Hardware error address, Core, Hardware error code, IstatReg, PciErrReg, CoreErrStat, CoreErrAddr, Doorbell Size, DoorBell Outstanding, SWReset). Explanation The crypto hardware chip has reported a fatal error, indicating that the chip is
inoperable. The information from this message captures the details to allow further analysis of the problem. The crypto chip is reset when this condition is detected to unobtrusively allow the ASA to continue functioning. Also, the crypto environment at the time this issue is detected is written to a crypto archive directory on flash to provide further debugging information. Various parameters related to the crypto hardware are included in this message, as follows:

HWErrAddrHardware address (set by crypto chip) CoreCrypto core experiencing the error HwErrCodeHardware error code (set by crypto chip) IstatRegInterrupt status register (set by crypto chip) PciErrRegPCI error register (set by crypto chip) CoreErrStatCore error status (set by crypto chip) CoreErrAddrCore error address (set by crypto chip) Doorbell SizeMaximum crypto commands allowed DoorBell OutstandingCrypto commands outstanding SWResetNumber of crypto chip resets since boot
Recommended Action Forward the message information to the Cisco TAC for further analysis.
402125
Error Message %ASA-4-402125: The ASA hardware accelerator ring timed out (parameters). Explanation The crypto driver has detected that either the IPSEC descriptor ring or SSL/Admin
descriptor ring is no longer progressing, meaning the crypto chip no longer appears to be functioning. The crypto chip is reset when this condition is detected to unobtrusively allow the ASA to continue functioning. Also, the crypto environment at the time this issue was detected was written to a crypto archive directory on flash to provide further debugging information.

ringIPSEC or Admin ring parametersInclude the following: - DescDescriptor address - CtrlStatControl/status value
1-200
Chapter 1
- ResultPSuccess pointer - ResultValSuccess value - CmdCrypto command - CmdSizeCommand size - ParamCommand parameters - DlenData length - DataPData pointer - CtxtPVPN context pointer - SWResetNumber of crypto chip resets since boot
Recommended Action Forward the message information to the Cisco TAC for further analysis.
402126
Error Message %ASA-4-402126: CRYPTO: The ASA created Crypto Archive File Archive Filename as a Soft Reset was necessary. Please forward this archived information to Cisco. Explanation A functional problem with the hardware crypto chip was detected (see syslog messages 402124 and 402125). To further debug the crypto problem, a crypto archive file was generated that included the current crypto hardware environment (hardware registers and crypto description entries). At boot time, a crypto_archive directory was automatically created on the flash file system (if it did not exist previously). A maximum of two crypto archive files are allowed to exist in this directory.
Archive FilenameThe name of the crypto archive file name. The crypto archive file names are of the form, crypto_arch_x.bin, where x = (1 or 2).
Recommended Action Forward the crypto archive files to the Cisco TAC for further analysis.
402127
Error Message %ASA-4-402127: CRYPTO: The ASA is skipping the writing of latest Crypto Archive File as the maximum # of files, max_number, allowed have been written to archive_directory. Please archive & remove files from Archive Directory if you want more Crypto Archive Files saved. Explanation A functional problem with the hardware crypto chip was detected (see messages 4402124 and 4402125). This message indicates a crypto archive file was not written, because the maximum number of crypto archive files already existed. max_numberMaximum number of files allowed in the archive directory; currently set to two
archive_directoryName of the archive directory
Recommended Action Forward previously generated crypto archive files to the Cisco TAC. Remove
the previously generated archive file(s) so that more can be written (if deemed necessary).
1-201
Syslog Messages
402128
Error Message %ASA-5-402128: CRYPTO: An attempt to allocate a large memory block failed, size: size, limit: limit Explanation An SSL connection is attempting to use more memory than allowed. The request has been denied.
sizeThe size of the memory block being allocated limitThe maximum size of allocated memory permitted
Recommended Action If this message persists, an SSL denial of service attack may be in progress.
Contact the remote peer administrator or upstream provider.
402129
Error Message %ASA-6-402129: CRYPTO: An attempt to release a DMA memory block failed, location: address Explanation An internal software error has occurred.
addressThe address being freed
Recommended Action Contact the Cisco TAC for assistance.
402130
Error Message %ASA-6-402130: CRYPTO: Received an ESP packet (SPI = 0x54A5C634, sequence number=0x7B) from 75.2.96.101 (user=user) to 85.2.96.10 with incorrect IPsec padding. Explanation The ASA crypto hardware accelerator detected an IPsec packet with invalid padding. The ATT VPN client sometimes pads IPsec packets incorrectly.
SPIThe SPI associated with the packet sequence numberThe sequence number associated with the packet userUsername string paddingPadding data from the packet
Recommended Action While this message is None required and does not indicate a problem with the ASA, customers using the ATT VPN client may wish to upgrade their VPN client software.
1-202
Chapter 1
402131
Error Message %ASA-4-402131: CRYPTO: status changing the accel_instance hardware accelerator's configuration bias from old_config_bias to new_config_bias. Explanation The hardware accelerator configuration has been changed on the ASA. Some ASA platforms have multiple hardware accelerators. One syslog message is generated for each hardware accelerator change.
statusIndicates success or failure accel_instanceThe instance of the hardware accelerator old_config_biasThe old configuration new_config_biasThe new configuration
Recommended Action If any of the accelerators fails when attempting to change its configuration, collect logging information and contact the Cisco TAC. If a failure occurs, the software will retry the configuration change multiple times. The software will fall back to the original configuration bias if the retry attempts fail. If multiple attempts to reconfigure the hardware accelerator fail, it may indicate a hardware failure.
402140
Error Message %ASA-3-402140: CRYPTO: RSA key generation error: modulus len len Explanation An error occurred during an RSA public key pair generation.
lenThe prime modulus length in bits
402141
Error Message %ASA-3-402141: CRYPTO: Key zeroization error: key set type, reason reason Explanation An error occurred during an RSA public key pair generation.
typeThe key set type, which can be any of the following: DH, RSA, DSA, or unknown reasonThe unexpected crypto session type
1-203
Syslog Messages
402142
Error Message %ASA-3-402142: CRYPTO: Bulk data op error: algorithm alg, mode mode Explanation An error occurred during a symmetric key operation.
opThe operation, which can be either encryption or decryption algThe encryption algorithm, which can be any of the following: DES, 3DES, AES, or RC4 modeThe mode, which can be any of the following: CBC, CTR, CFB, ECB, stateful-RC4, or stateless-RC4
402143
Error Message %ASA-3-402143: CRYPTO: alg type key op Explanation An error occurred during an asymmetric key operation.
algThe encryption algorithm, which can be either RSA or DSA typeThe key type, which can be either public or private opThe operation, which can be either encryption or decryption
402144
Error Message %ASA-3-402144: CRYPTO: Digital signature error: signature algorithm sig, hash algorithm hash Explanation An error occurred during digital signature generation.
sigThe signature algorithm, which can be either RSA or DSA hashThe hash algorithm, which can be any of the following: MD5, SHA1, SHA256, SHA384, or SHA512
1-204
Chapter 1
402145
Error Message %ASA-3-402145: CRYPTO: Hash generation error: algorithm hash Explanation A hash generation error occurred.
hashThe hash algorithm, which can be any of the following: MD5, SHA1, SHA256, SHA384, or SHA512
402146
Error Message %ASA-3-402146: CRYPTO: Keyed hash generation error: algorithm hash, key len len Explanation A keyed hash generation error occurred.
hashThe hash algorithm, which can be any of the following: MD5, SHA1, SHA256, SHA384, or SHA512 lenThe key length in bits
402147
Error Message %ASA-3-402147: CRYPTO: HMAC generation error: algorithm alg Explanation An HMAC generation error occurred.
algThe HMAC algorithm, which can be any of the following: HMAC-MD5, HMAC-SHA1, HMAC-SHA2, or AES-XCBC
402148
Error Message %ASA-3-402148: CRYPTO: Random Number Generator error Explanation A random number generator error occurred. Recommended Action Contact the Cisco TAC for assistance.
1-205
Syslog Messages
403101
Error Message %ASA-4-403101: PPTP session state not established, but received an XGRE packet, tunnel_id=number, session_id=number Explanation The ASA received a PPTP XGRE packet without a corresponding control connection
session.
403102
Error Message %ASA-4-403102: PPP virtual interface interface_name rcvd pkt with invalid protocol: protocol, reason: reason. Explanation The module received an XGRE encapsulated PPP packet with an invalid protocol field. Recommended Action If the problem persists, contact the Cisco TAC.
403103
Error Message %ASA-4-403103: PPP virtual interface max connections reached. Explanation The module cannot accept additional PPTP connections.Connections are allocated as
soon as they are available.

403104
Error Message %ASA-4-403104: PPP virtual interface interface_name requires mschap for MPPE. Explanation The MPPE was configured, but MS-CHAP authentication was not. Recommended Action Add MS-CHAP authentication with the vpdn group group_name ppp
authentication command.
1-206
Chapter 1
403106
Error Message %ASA-4-403106: PPP virtual interface interface_name requires RADIUS for MPPE. Explanation The MPPE was configured, but RADIUS authentication was not. Recommended Action Add RADIUS authentication with the vpdn group group_name ppp
authentication command.
403107
Error Message %ASA-4-403107: PPP virtual interface interface_name missing aaa server group info Explanation The AAA server configuration information cannot be found. Recommended Action Add the AAA server information with the vpdn group group_name client
authentication aaa aaa_server_group command.
403108
Error Message %ASA-4-403108: PPP virtual interface interface_name missing client ip address option Explanation The client IP address pool information is missing. Recommended Action Add IP address pool information with the vpdn group group_name client
configuration address local address_pool_name command.
403109
Error Message %ASA-4-403109: Rec'd packet not an PPTP packet. (ip) dest_address=dest_address, src_addr= source_address, data: string. Explanation The module received a spoofed PPTP packet, which may indicate a hostile event. Recommended Action Contact the administrator of the peer to check the PPTP configuration settings.
1-207
Syslog Messages
403110
Error Message %ASA-4-403110: PPP virtual interface interface_name, user: user missing MPPE key from aaa server. Explanation The AAA server was not returning the MPPE key attributes required to set up the MPPE encryption policy. Recommended Action Check the AAA server configuration. If the AAA server cannot return MPPE
key attributes, use local authentication instead by entering the vpdn group group_name client authentication local command.
403500
Error Message %ASA-6-403500: PPPoE - Service name 'any' not received in PADO. Intf:interface_name AC:ac_name. Explanation The ASA requested the PPPoE service any from the access controller at the Internet
service provider. The response from the service provider includes other services, but does not include the service any. This is a discrepancy in the implementation of the protocol. The PADO packet is processed normally, and connection negotiations continue.
403501
Error Message %ASA-3-403501: PPPoE - Bad host-unique in PADO - packet dropped. Intf:interface_name AC:ac_name Explanation The ASA sent an identifier called the host-unique value to the access controller. The
access controller responded with a different host-unique value. The ASA was unable to identify the corresponding connection request for this response. The packet was dropped, and connection negotiations were discontinued.
Recommended Action Contact the Internet service provider. Either the access controller at the service
provider is mishandling the host-unique value, or the PADO packet is being forged.
1-208
Chapter 1
403502
Error Message %ASA-3-403502: PPPoE - Bad host-unique in PADS - dropping packet. Intf:interface_name AC:ac_name Explanation The ASA sent an identifier called the host-unique value to the access controller. The
access controller responded with a different host-unique value. The ASA was unable to identify the corresponding connection request for this response. The packet was dropped, and connection negotiations were discontinued.
Recommended Action Contact the Internet service provider. Either the access controller at the service
provider is mishandling the host-unique value, or the PADO packet is being forged.
403503
Error Message %ASA-3-403503: PPPoE:PPP link down:reason Explanation The PPP link has gone down. There are many reasons why this can happen. The first format will display a reason if PPP provides one. Recommended Action Check the network link to ensure that the link is connected. The access
concentrator may be down. Make sure that your authentication protocol matches the access concentrator and that your name and password are correct. Verify this information with your ISP or network support person.
403504
Error Message %ASA-3-403504: PPPoE:No 'vpdn group group_name' for PPPoE is created Explanation PPPoE requires a dial-out configuration before starting a PPPoE session. In general, the configuration should specify a dialing policy, the PPP authentication, the username, and a password. The following example configures the ASA for PPPoE dialout. The my-username and my-password commands are used to authenticate the access concentrator, using PAP if necessary.
For example:
hostname# hostname# hostname# hostname# hostname# vpdn group my-pppoe request dialout pppoe vpdn group my-pppoe ppp authentication pap vpdn group my-pppoe localname my-username vpdn username my-username password my-password ip address outside pppoe setroute
Recommended Action Configure a VPDN group for PPPoE.
1-209
Syslog Messages
403505
Error Message %ASA-4-403505: PPPoE:PPP - Unable to set default route to IP_address at interface_name Explanation This message is usually followed by the message, default route already exists. Recommended Action Remove the current default route or remove the setroute parameter so that there is no conflict between PPPoE and the manually configured route.
403506
Error Message %ASA-4-403506: PPPoE:failed to assign PPP IP_address netmask netmask at interface_name Explanation This message is followed by one of the followings messages: subnet is the same as interface, or on failover channel. Recommended Action In the first case, change the address causing the conflict. In the second case, configure the PPPoE on an interface other than the failover interface.
403507
Error Message %ASA-3-403507: PPPoE:PPPoE client on interface interface failed to locate PPPoE vpdn group group_name Explanation You can configure the PPPoE client on an interface to use a particular VPDN group by entering the pppoe client vpdn group group_name command. If a PPPoE VPDN group of the configured name was not located during system startup, this message is generated.
interfaceThe interface on which the PPPoE client failed group_name The VPDN group name of the PPPoe client on the interface
Add the required VPDN group by entering the vpdn group group_name command. Request dialout PPPoE in global configuration mode, and add all the group properties. Remove the pppoe client vpdn group group_name command from the interface indicated. In this case, the PPPoE client will attempt to use the first PPPoE VPDN group defined.
Note
All changes take effect only after the PPPoE client on the interface is restarted by entering the ip address pppoe command.
1-210
Chapter 1
405001
Error Message %ASA-4-405001: Received ARP {request | response} collision from IP_address/MAC_address on interface interface_name to IP_address/MAC_address on interface interface_name Explanation The ASA received an ARP packet, and the MAC address in the packet differs from the
ARP cache entry.

Recommended Action This traffic might be legitimate, or it might indicate that an ARP poisoning attack is in progress. Check the source MAC address to determine where the packets are coming from and to see if they belong to a valid host.
405003
Error Message %ASA-4-405003: IP address collision detected between host IP_address at MAC_address and interface interface_name, MAC_address. Explanation A client IP address in the network is the same as the ASA interface IP address. Recommended Action Change the IP address of the client.
405101
Error Message %ASA-4-405101: Unable to Pre-allocate H225 Call Signalling Connection for foreign_address outside_address[/outside_port] to local_address inside_address[/inside_port] Explanation The module failed to allocate RAM system memory while starting a connection or has
no more address translation slots available.

Recommended Action If this message occurs periodically, it can be ignored. You can check the size
of the global pool compared to the number of inside network clients. A PAT address may be necessary. Alternatively, shorten the timeout interval of translates and connections. This error message may also be caused by insufficient memory; try reducing the amount of memory usage, or purchasing additional memory. If the problem persists, contact the Cisco TAC.
405002
Error Message %ASA-4-405002: Received mac mismatch collision from IP_address/MAC_address for authenticated host Explanation This packet appears for one of the following conditions:
The ASA received a packet with the same IP address, but a different MAC address from one of its uauth entries.
1-211
Syslog Messages
You configured the vpnclient mac-exempt command on the ASA, and the ASA received a packet with an exempt MAC address, but a different IP address from the corresponding uauth entry.
Recommended Action This traffic might be legitimate, or it might indicate that a spoofing attack is in
progress. Check the source MAC address and IP address to determine where the packets are coming from and if they belong to a valid host.
405101
Error Message %ASA-4-405101: Unable to Pre-allocate H225 Call Signalling Connection for foreign_address outside_address[/outside_port] to local_address inside_address[/inside_port] Explanation The ASA failed to allocate RAM system memory while starting a connection or has no more address translation slots available. Recommended Action Check the size of the global pool compared to the number of inside network clients. A PAT address may be necessary. Alternatively, shorten the timeout interval of translations and connections. Also, reduce the amount of memory usage, or purchase additional memory. If this message occurs periodically, it can be ignored. If the problem persists, contact the Cisco TAC.
405102
Error Message %ASA-4-405102: Unable to Pre-allocate H245 Connection for foreign_address outside_address[/outside_port] to local_address inside_address[/inside_port] Explanation The ASA failed to allocate RAM system memory while starting a connection or has no more address translation slots available. Recommended Action Check the size of the global pool compared to the number of inside network clients. A PAT address may be necessary. Alternatively, shorten the timeout interval of translations and connections. In addition, reduce the amount of memory usage, or purchase additional memory. If this message occurs periodically, it can be ignored. If the problem persists, contact the Cisco TAC.
405103
Error Message %ASA-4-405103: H225 message from source_address/source_port to dest_address/dest_port contains bad protocol discriminator hex Explanation The ASA is expecting the protocol discriminator, 0x08, but it received something other than 0x08. The endpoint may be sending a bad packet, or received a message segment other than the first segment. The packet is allowed through. Recommended Action None required.
1-212
Chapter 1
405104
Error Message %ASA-4-405104: H225 message received from outside_address/outside_port to inside_address/inside_port before SETUP Explanation An H.225 message was received out of order, before the initial SETUP message, which is not allowed. The ASA must receive an initial SETUP message for that H.225 call signalling channel before accepting any other H.225 messages. Recommended Action None required.
405105
Error Message %ASA-4-405105: H323 RAS message AdmissionConfirm received from source_address/source_port to dest_address/dest_port without an AdmissionRequest Explanation A gatekeeper has sent an ACF, but the ASA did not send an ARQ to the gatekeeper. Recommended Action Check the gatekeeper with the specified source_address to determine why it sent an ACF without receiving an ARQ from the ASA.
405106
Error Message %ASA-4-405106: H323 num channel is not created from %I/%d to %I/%d %s Explanation The ASA tried to create a match condition on the H.323 media-type channel. See the
match media-type command for more information.

405107
Error Message %ASA-4-405107: H245 Tunnel is detected and connection dropped from %I/%d to %I/%d %s Explanation An H.323 connection has been dropped because of an attempted H.245 tunnel control during call setup. See the h245-tunnel-block command for more information. Recommended Action None required.
1-213
Syslog Messages
405201
Error Message %ASA-4-405201: ILS ILS_message_type from inside_interface:source_IP_address to outside_interface:/destination_IP_address has wrong embedded address embedded_IP_address Explanation The embedded address in the ILS packet payload was not the same as the source IP address of the IP packet header. Recommended Action Check the host specified with the source_IP_address to determine why it sent
an ILS packet with an incorrect embedded IP address.
405300
Error Message %ASA-4-405300: Radius Accounting Request received from from_addr is not allowed Explanation The accounting request came from a host that was not configured in the policy map. The
message is logged and processing stops.
from_addrThe IP address of the host sending the request
Recommended Action If the host was configured to send RADIUS accounting messages to the ASA, make sure that it was configured in the correct policy map that was applied to the service policy. If the host was not configured to send RADIUS accounting messages to the ASA, then check to see why the messages are being sent. If the messages are illegitimate, then create the proper ACLs to drop the packets.
405301
Error Message %ASA-4-405301: Attribute attribute_number does not match for user user_ip Explanation When the validate-attribute command was entered, the attribute values stored in the
accounting request start received do not match those stored in the entry, if it exists.

attribute_numberThe RADIUS attribute to be validated with RADIUS accounting. Values range from 1 to 191. Vendor-specific attributes are not supported. user_ipThe IP address (framed IP attribute) of the user.
1-214
Chapter 1
406001
Error Message %ASA-4-406001: FTP port command low port: IP_address/port to IP_address on interface interface_name Explanation A client entered an FTP port command and supplied a port less than 1024 (in the well-known port range usually devoted to server ports). This is indicative of an attempt to avert the site security policy. The ASA drops the packet, terminates the connection, and logs the event. Recommended Action None required.
406002
Error Message %ASA-4-406002: FTP port command different address: IP_address(IP_address) to IP_address on interface interface_name Explanation A client entered an FTP port command and supplied an address other than the address used in the connection. An attempt to avert the site security policy occurred. For example, an attacker might attempt to hijack an FTP session by changing the packet on the way, and putting different source information instead of the correct source information. The ASA drops the packet, terminates the connection, and logs the event. The address in parentheses is the address from the port command. Recommended Action None required.
407001
Error Message %ASA-4-407001: Deny traffic for local-host interface_name:inside_address, license limit of number exceeded Explanation The host limit was exceeded. An inside host is counted toward the limit when one of the following conditions is true:
The inside host has forwarded traffic through the ASA within the last five minutes. The inside host has reserved an xlate connection or user authentication at the ASA.
Recommended Action The host limit is enforced on the low-end platforms. Use the show version command to view the host limit. Use the show local-host command to view the current active hosts and the inside users that have sessions at the ASA. To forcefully disconnect one or more users, use the clear local-host command. To expire the inside users more quickly from the limit, set the xlate, connection, and uauth timeouts to the recommended values or lower. (See Table 1-6.) Table 1-6 Timeouts and Recommended Values
Timeout Recommended Value xlate 00:05:00 (five minutes)
1-215
Syslog Messages
Table 1-6
Timeouts and Recommended Values
Timeout Recommended Value conn uauth 00:01:00 (one hour) 00:05:00 (five minutes)
407002
Error Message %ASA-4-407002: Embryonic limit nconns/elimit for through connections exceeded.outside_address/outside_port to global_address (inside_address)/inside_port on interface interface_name Explanation The number of connections from a specified foreign address over a specified global
address to the specified local address exceeded the maximum embryonic limit for that static. The ASA tries to accept the connection if it can allocate memory for that connection. It proxies on behalf of the local host and sends a SYN_ACK packet to the foreign host. The ASA retains pertinent state information, drops the packet, and waits for the acknowledgment from the client. The message might indicate legitimate traffic or that a DoS attack is in progress.
Recommended Action Check the source address to determine where the packets are coming from and
whether or not a valid host is sending them.
407003
Error Message %ASA-4-407003: Established limit for RPC services exceeded number Explanation The ASA tried to open a new hole for a pair of RPC servers or services that have already been configured after the maximum number of holes has been met. Recommended Action Wait for other holes to be closed (through associated timeout expiration), or limit the number of active pairs of servers or services.
408001
Error Message %ASA-4-408001: IP route counter negative - reason, IP_address Attempt: number Explanation An attempt to decrement the IP route counter into a negative value failed. Recommended Action Enter the clear ip route command to reset the route counter. If the problem
persists, contact the Cisco TAC.
1-216
Chapter 1
408002
Error Message %ASA-4-408002: ospf process id route type update address1 netmask1 [distance1/metric1] via source IP:interface1 address2 netmask2 [distance2/metric2] interface2 Explanation A network update was received from a different interface with the same distance and a
better metric than the existing route. The new route overrides the existing route that was installed through another interface. The new route is for redundancy purposes only and means that a path has shifted in the network. This change must be controlled through topology and redistribution. Any existing connections affected by this change are probably disabled and will time out. This path shift only occurs if the network topology has been specifically designed to support path redundancy, in which case it is expected.
408003
Error Message %ASA-4-408003: can't track this type of object hex Explanation A component of the tracking system has encountered an object type that is not supported by the component. A STATE object was expected.
hexA hexidecimal value(s) depicting variable value(s) or addresses in memory
Recommended Action Reconfigure the track object to make it a STATE object.
409001
Error Message %ASA-4-409001: Database scanner: external LSA IP_address netmask is lost, reinstalls Explanation The software detected an unexpected condition. The router will take corrective action and continue. Recommended Action None required.
409002
Error Message %ASA-4-409002: db_free: external LSA IP_address netmask Explanation An internal software error occurred. Recommended Action None required.
1-217
Syslog Messages
409003
Error Message %ASA-4-409003: Received invalid packet: reason from IP_address, interface_name Explanation An invalid OSPF packet was received. Details are included in the error message. The
cause might be an incorrect OSPF configuration or an internal error in the sender.

Recommended Action Check the OSPF configuration of the receiver and the sender configuration for
inconsistency.
409004
Error Message %ASA-4-409004: Received reason from unknown neighbor IP_address Explanation The OSPF hello, database description, or database request packet was received, but the router cannot identify the sender. Recommended Action None required.
409005
Error Message %ASA-4-409005: Invalid length number in OSPF packet from IP_address (ID IP_address), interface_name Explanation The ASA received an OSPF packet with a field length of less than normal header size
or that was inconsistent with the size of the IP packet in which it arrived. This indicates a configuration error in the sender of the packet.
Recommended Action From a neighboring address, locate the problem router and reboot it.
409006
Error Message %ASA-4-409006: Invalid lsa: reason Type number, LSID IP_address from IP_address, IP_address, interface_name Explanation The router received an LSA with an invalid LSA type. The cause is either memory
corruption or unexpected behavior on a router.

Recommended Action From a neighboring address, locate the problem router and reboot it. If the problem persists, contact the Cisco TAC.
1-218
Chapter 1
409007
Error Message %ASA-4-409007: Found LSA with the same host bit set but using different mask LSA ID IP_address netmask New: Destination IP_address netmask Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears, and report it to the Cisco TAC.
409008
Error Message %ASA-4-409008: Found generating default LSA with non-zero mask LSA type: number Mask: netmask metric: number area: string Explanation The router tried to generate a default LSA with an incorrect mask and possibly incorrect
metric because an internal software error occurred.

Recommended Action Copy the message exactly as it appears, and report it to the Cisco TAC.
409009
Error Message %ASA-4-409009: OSPF process number cannot start. There must be at least one up IP interface, for OSPF to use as router ID Explanation OSPF failed while attempting to allocate a router ID from the IP address of one of its
interfaces.
Recommended Action Make sure that there is at least one interface that is up and has a valid IP
address. If there are multiple OSPF processes running on the router, each requires a unique router ID. You must have enough interfaces up so that each of them can obtain a router ID.
409010
Error Message %ASA-4-409010: Virtual link information found in non-backbone area: string Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears, and report it to the Cisco TAC.
1-219
Syslog Messages
409011
Error Message %ASA-4-409011: OSPF detected duplicate router-id IP_address from IP_address on interface interface_name Explanation OSPF received a hello packet from a neighbor that has the same router ID as this routing process. A full adjacency cannot be established. Recommended Action The OSPF router ID should be unique. Change the neighbor router ID.
409012
Error Message %ASA-4-409012: Detected router with duplicate router ID IP_address in area string Explanation OSPF received a hello packet from a neighbor that has the same router ID as this routing process. A full adjacency cannot be established. Recommended Action The OSPF router ID should be unique. Change the neighbor router ID.
409013
Error Message %ASA-4-409013: Detected router with duplicate router ID IP_address in Type-4 LSA advertised by IP_address Explanation OSPF received a hello packet from a neighbor that has the same router ID as this routing process. A full adjacency cannot be established. Recommended Action The OSPF router ID should be unique. Change the neighbor router ID.
409023
Error Message %ASA-4-409023: Attempting AAA Fallback method method_name for request_type request for user user:Auth-server group server_tag unreachable Explanation An authentication or authorization attempt to an external server has failed and will be
performed using the local user database.

aaa_operationEither authentication or authorization usernameThe user associated with the connection server_groupThe name of the AAA server whose servers were unreachable
Recommended Action Investigate any connectivity problems with the AAA servers configured in the
first method. Ping the authentication servers from the ASA. Make sure that the daemons are running on the AAA server.
1-220
Chapter 1
409101
Error Message %ASA-4-409101: Received invalid packet: s from P, s Explanation An invalid OSPF packet was received. Details are included in the error message. The cause might be a misconfigured OSPF or an internal error in the sender. Recommended Action Check the OSPF configuration of the receiver and the sender for
inconsistencies.
409102
Error Message %ASA-4-409102: Received packet with incorrect area from P, s, area AREA_ID_STR, packet area AREA_ID_STR Explanation An OSPF packet was received with an area ID in its header that does not match the area
of this interface.
Recommended Action Check the OSPF configuration of the receiver and the sender for
inconsistencies.
409103
Error Message %ASA-4-409103: Received s from unknown neighbor i Explanation An OSPF hello, database description, or database request packet was received, but the
router could not identify the sender.

409104
Error Message %ASA-4-409104: Invalid length d in OSPF packet type d from P (ID i), s Explanation The system received an OSPF packet with a length field of less than normal header size
or inconsistent with the size of the IP packet in which it arrived. An error in the sender of the packet has occurred.
1-221
Syslog Messages
409105
Error Message %ASA-4-409105: Invalid lsa: s: Type 0x x, Length 0x x, LSID u from i Explanation The router received an LSA with invalid data. The LSA includes an invalid LSA type,
incorrect checksum, or incorrect length, which is caused by either memory corruption or unexpected behavior on a router.
Recommended Action From a neighboring address, locate the problem routerand do the following:
Collect a running configuration of the router by entering the show running-config command. Enter the show ipv6 ospf database command to gather data that may help identify the nature of the error. Enter the show ipv6 ospf database link-state-id command. The link-state-id argument is the IP address of the invalid LSA. Enter the show logging command to gather data that may help identify the nature of the error. Reboot the router.
If you cannot determine the nature of the error from the collected information, contact the Cisco TAC and provide the gathered information.
409106
Error Message %ASA-4-409106: Found generating default LSA with non-zero mask LSA type: 0x x Mask: i metric: lu area: AREA_ID_STR Explanation The router tried to generate the default LSA with the incorrect mask and possibly an
incorrect metric because of an internal software error.

409107
Error Message %ASA-4-409107: OSPFv3 process d could not pick a router-id, please configure manually Explanation OSPFv3 failed while attempting to allocate a router ID from the IP address of one of its
interfaces.
Recommended Action Make sure that there is at least one interface that is up and has a valid IP
address. If there are multiple OSPF processes running on the router, each requires a unique router ID. You must have enough up interfaces so that each of them can obtain a router ID.
1-222
Chapter 1
409108
Error Message %ASA-4-409108: Virtual link information found in non-backbone area: AREA_ID_STR Explanation An internal error has occurred. Recommended Action None required.
409109
Error Message %ASA-4-409109: OSPF detected duplicate router-id i from P on interface IF_NAME Explanation OSPF received a hello packet from a neighbor that has the same router ID as this routing
process. A full adjacency cannot be established. The OSPF router ID should be unique.
Recommended Action Change the neighbor router ID.
409110
Error Message %ASA-4-409110: Detected router with duplicate router ID i in area AREA_ID_STR Explanation OSPF received a hello packet from a neighbor that has the same router ID as this routing
process. A full adjacency cannot be established. The OSPF router ID should be unique.
Recommended Action Change the neighbor router ID.
409111
Error Message %ASA-4-409111: Multiple interfaces (IF_NAME/IF_NAME) on a single link detected. Explanation OSPFv3 enabled on multiple interfaces that are on the same link is not supported. Recommended Action OSPFv3 should be disabled or made passive on all except one of the interfaces.
1-223
Syslog Messages
409112
Error Message %ASA-4-409112: Packet not written to the output queue Explanation An internal error has occurred. Recommended Action None required.
409113
Error Message %ASA-4-409113: Doubly linked list linkage is NULL Explanation An internal error has occurred. Recommended Action None required.
409114
Error Message %ASA-4-409114: Doubly linked list prev linkage is NULL x Explanation An internal error has occurred. Recommended Action None required.
409115
Error Message %ASA-4-409115: Unrecognized timer d in OSPF s Explanation An internal error has occurred. Recommended Action None required.
409116
Error Message %ASA-4-409116: Error for timer d in OSPF process s Explanation An internal error has occurred. Recommended Action None required.
1-224
Chapter 1
409117
Error Message %ASA-4-409117: Can't find LSA database type x, area AREA_ID_STR, interface x Explanation An internal error has occurred. Recommended Action None required.
409118
Error Message %ASA-4-409118: Could not allocate DBD packet Explanation An internal error has occurred. Recommended Action None required.
409119
Error Message %ASA-4-409119: Invalid build flag x for LSA i, type 0x x Explanation An internal error has occurred. Recommended Action None required.
409120
Error Message %ASA-4-409120: Router-ID i is in use by ospf process d Explanation The ASA attempted to assign a router ID that is in use by another process. Recommended Action Configure another router ID for one of the processes.
409121
Error Message %ASA-4-409121: Router is currently an ASBR while having only one area which is a stub area Explanation An ASBR must be attached to an area that can carry AS External or NSSA LSAs. Recommended Action Make the area to which the router is attached into an NSSA or regular area.
1-225
Syslog Messages
409122
Error Message %ASA-4-409122: Could not select a global IPv6 address. Virtual links require at least one global IPv6 address. Explanation A virtual link was configured. For the virtual link to function, a global IPv6 address must be available. However, no global IPv6 address could be found on the router. Recommended Action Configure a global IPv6 address on an interface on this router.
409123
Error Message %ASA-4-409123: Neighbor command allowed only on NBMA networks Explanation The neighbor command is allowed only on NBMA networks. Recommended Action Check the configuration options for the neighbor command, and correct the options or the network type for the neighbor interface.
409125
Error Message %ASA-4-409125: Can not use configured neighbor: poll and priority options are allowed only for a NBMA network Explanation The configured neighbor was found on a point-to-multipoint network and either the poll or priority option was configured. These options are only allowed on NBMA type networks. Recommended Action Check the configuration options for the neighbor command, and correct the options or the network type for the neighbor interface.
409128
Error Message %ASA-4-409128: OSPFv3-d Area AREA_ID_STR: Router i originating invalid type 0x x LSA, ID u, Metric d on Link ID d Link Type d Explanation The router indicated in this message has originated an LSA with an invalid metric. If this is a router LSA and the link metric is zero, a risk of routing loops and traffic loss exists in the network. Recommended Action Configure a valid metric for the given LSA type and link type on the router that
originated the reported LSA.
1-226
Chapter 1
410001
Error Message %ASA-4-410001: UDP DNS request from source_interface:source_address/source_port to dest_interface:dest_address/dest_port; (label length | domain-name length) 52 bytes exceeds remaining packet length of 44 bytes. Explanation The domain-name length exceeds 255 bytes in a UDP DNS packet. See RFC 1035, Section 3.1 for more information. Recommended Action None required.
410002
Error Message %ASA-2-410002: Dropped num DNS responses with mis-matched id in the past sec second(s): from src_ifc:sip/sport to dest_ifc:dip/dport Explanation The ASA detects an excess number of DNS responses with a mismatched DNS
identifier. A high rate of mismatched DNS identifiers might indicate an attack on the cache. The threshold is set by the id-mismatch DNS policy-map parameter submode command.

numThe number of ID mismatch instances as configured by the id-mismatch command secThe duration in seconds as configured by the id-mismatch command src_ifcThe source interface name at which the DNS message is received with a mismatched DNS identifier sipThe source IP address sportThe source port dest_ifcThe destination interface name dipThe destination IP address dportThe destination port
Recommended Action Check the IP address and port in the message to trace the source of the attack. You can configure ACLs to block traffic permanently from the source.
410003
Error Message %ASA-4-410003: action_class: action DNS query_response from src_ifc:sip/sport to dest_ifc:dip/dport; further_info Explanation A DNS classification was performed on a DNS message and the specified criteria were
satisfied. As a result, the configured action occurs.

action_classThe DNS Classification action class actionThe action taken: Dropped, Dropped (no TSIG), or Masked header flags for query_responseEither query or response
1-227
Syslog Messages
src_ifcThe source interface name sipThe source IP address sportThe source port dest_ifcThe destination interface name dipThe destination IP address dportThe destination port further_infoOne of the following: matched Class id: class_name, matched Class id: match_command (for a standalone match command), or TSIG resource record not present (for messages generated by the tsig enforced command)
410004
Error Message %ASA-6-410004: action_class: action DNS query_response from src_ifc:sip/sport to dest_ifc:dip/dport; further_info Explanation A DNS classification was performed on a DNS message and the specified criteria were
satisfied.

action_classThe DNS Classification action class actionThe action taken: Received or Received (no TSIG) query_responseEither query or response src_ifcThe source interface name sipThe source IP address sportThe source port dest_ifcThe destination interface name dipThe destination IP address dportThe destination port further_infoOne of the following: matched Class id: class_name, matched Class id: match_command (for a standalone match command), or TSIG resource record not present (for messages generated by the tsig enforced command)
1-228
Chapter 1
411001
Error Message %ASA-4-411001: Line protocol on interface interface_name changed state to up Explanation The status of the line protocol has changed from down to up. If interface_name is a
logical interface name such as inside and outside, this message indicates that the logical interface line protocol has changed from down to up. If interface_name is a physical interface name such as Ethernet0 and GigabitEthernet0/1, this message indicates that the physical interface line protocol has changed from down to up.
1-229
Syslog Messages
411002
Error Message %ASA-4-411002:Line protocol on interface interface_name changed state to down Explanation The status of the line protocol has changed from up to down. If interface_name is a
logical interface name such as inside and outside, this message indicates that the logical interface line protocol has changed from up to down. In this case, the physical interface line protocol status is not affected. If interface_name is a physical interface name such as Ethernet0 and GigabitEthernet0/1, this message indicates that the physical interface line protocol has changed from up to down.
Recommended Action If this is an unexpected event on the interface, check the physical line.
411003
Error Message %ASA-4-411003: Configuration status on interface interface_name changed state to downup Explanation The configuration status of the interface has changed from down to up. Recommended Action If this is an unexpected event, check the physical line.
411004
Error Message %ASA-4-411004: Configuration status on interface interface_name changed state to up Explanation The configuration status of the interface has changed from down to up. Recommended Action None required.
411005
Error Message %ASA-4-411005: Interface variable 1 experienced a hardware transmit hang. The interface has been reset. Explanation The interface experienced a hardware transmit freeze that required a reset of the
Ethernet controller to restore the interface to full operation. This is a known issue with Gigabit interfaces on ASA 5510, ASA 5520, ASA 5540, and ASA 5550 ASAs.
variable 1The interface name, such as GigabitEthernet0/0
1-230
Chapter 1
412001
Error Message %ASA-4-412001:MAC MAC_address moved from interface_1 to interface_2 Explanation A host move was detected from one module interface to another. In a transparent ASA, mapping between the host (MAC) and ASA port is maintained in a Layer 2 forwarding table. The table dynamically binds packet source MAC addresses to an ASA port. In this process, whenever movement of a host from one interface to another interface is detected, this message is generated. Recommended Action The host move might be valid or might be an attempt to spoof host MACs on other interfaces. If it is a MAC spoof attempt, you can either locate vulnerable hosts on your network and remove them or configure static MAC entries, which will not allow MAC address and port binding to change. If it is a genuine host move, no action is required.
412002
Error Message %ASA-4-412002:Detected bridge table full while inserting MAC MAC_address on interface interface. Number of entries = num Explanation The bridge table was full and an attempt was made to add one more entry. The ASA maintains a separate Layer 2 forwarding table per context and the message is generated whenever a context exceeds its size limit. The MAC address will be added, but it will replace the oldest existing dynamic entry (if available) in the table. This might be an attempted attack. Recommended Action Make sure that the new bridge table entries are valid. In case of attack, use EtherType ACLs to control access to vulnerable hosts.
413001
Error Message %ASA-4-413001: Module module_id is not able to shut down. Module Error: errnum message Explanation The module identified by module_id was not able to comply with a request from the
ASA system module to shut down. It may be performing a task that cannot be interrupted, such as a software upgrade. The errnum and message text describes the reason why the module cannot shut down, and the recommended corrective action.
Recommended Action Wait for the task on the module to complete before shutting down the module, or use the session command to access the CLI on the module, and stop the task that is preventing the module from shutting down.
1-231
Syslog Messages
413002
Error Message %ASA-4-413002: Module module_id is not able to reload. Module Error: errnum message Explanation The module identified by module_id was not able to comply with a request from the
ASA module to reload. It may be performing a task that cannot be interrupted, such as a software upgrade. The errnum and message text describes the reason why the module cannot reload, and the recommended corrective action.
Recommended Action Wait for the task on the module to complete before reloading the module, or use the session command to access the CLI on the module and stop the task that is preventing the module from reloading.
413003
Error Message %ASA-4-413003: Module string one is not a recognized type Explanation A module was detected that is not recognized as a valid module type. Recommended Action Upgrade to a version of ASA software that supports the module type installed.
413004
Error Message %ASA-4-413004: Module string one failed to write software newver (currently ver), reason. Trying again. Explanation The module failed to accept a software version, and will be transitioned to an
UNRESPONSIVE state. Another attempt will be made to update the module software.

string oneThe text string that specifies the module newverThe new version number of software that was not successfully written to the module (for example, 1.0(1)0) verThe current version number of the software on the module (for example, 1.0(1)0) reasonThe reason the new version cannot be written to the module. The possible values for reason include the following: - write failure - failed to create a thread to write the image
Recommended Action None required. Subsequent attempts will either generate a message indicating
a successful update or failure. You may verify the module transitions to UP after a subsequent update attempt by using the show module command.
1-232
Chapter 1
413005
Error Message %ASA-4-413005: Module module_id, application is not supported app_name version app_vers type app_type
Error Message %ASA-4-413005: Module prod_id in slot slot_num, application is not supported app_name version app_vers type app_type Explanation The module installed in slot slot_num was running an unsupported application version
or type.

module_idThe name of the software services module prod_idProduct ID string slot_numThe slot number in which the module is installed. Slot 0 indicates the system main board, and slot 1 indicates the module installed in the expansion slot. app_nameApplication name (string) app_versApplication version (string) app_typeApplication type (decimal)
413006
Error Message %ASA-4-413006: prod-id Module software version mismatch; slot slot is prod-id version running-vers. Slot slot prod-id requires required-vers. Explanation The version of software running on the module in slot slot was not the version required
by another module.

slotSlot 0 indicates the system main board. Slot 1 indicates the module installed in the expansion slot. prod_idProduct ID string for the device installed in slot slot running_versVersion of software currently running on the module installed in slot slot required_versVersion of software required by the module in slot slot
1-233
Syslog Messages
413007
Error Message %ASA-1-413007: An unsupported ASA and IPS configuration is installed. mpc_description with ips_description is not supported. Explanation An unsupported ASA and IPS configuration has been detected during IPS SSP setup for slot 1. The ASA should continue to function normally with an unsupported configuration.
mpc_descriptionA description string for the ASA model, which can be one of the following: ASA5585-SSP-10, ASA5585-SSP-20, ASA5585-SSP-40, ASA5585-SSP-60, ASA5585-SSP-10-K7, ASA5585-SSP-20-K7, ASA5585-SSP-40-K7, ASA5585-SSP-60-K7. ips_descriptionA description string for the IPS SSP model, which can be one of the following: ASA5585-SSP-IPS10, ASA5585-SSP-IPS20, ASA5585-SSP-IPS40, ASA5585-SSP-IPS60, ASA5585-SSP-P10K7, ASA5585-SSP-P20K7, ASA5585-SSP-P40K7, ASA5585-SSP-P60K7.
413008
Error Message %ASA-1-413008: An unsupported combination of the power supply module and the fan module is detected. Two power supply modules are recommended when using ASA 10G and IPS 10G SSPs simultaneously Explanation Only one power supply and one fan module are inserted when an ASA 10G SSP and IPS 10G SSP are present. Recommended Action When using an ASA 10G SSP and IPS 10G SSP, insert two power supplies instead of one fan module and one power supply module.
414001
Error Message %ASA-3-414001: Failed to save logging buffer using file name filename to FTP server ftp_server_address on interface interface_name: [fail_reason] Explanation The logging module failed to save the logging buffer to an external FTP server. Recommended Action Take applicable actions based on the failed reason:
Protocol errorMake sure no connectivity issue exists between the FTP server and ASA, and that the FTP sever can accept the FTP port command and PUT requests. Invalid username or passwordMake sure that the configured FTP client username and password are correct. All other errorsIf the problem persists, contact the Cisco TAC.
1-234
Chapter 1
414002
Error Message %ASA-3-414002: Failed to save logging buffer to flash:/syslog directory using file name: filename: [fail_reason] Explanation The logging module failed to save the logging buffer to system flash. Recommended Action If the failed reason is caused by insufficient space, check the flash free space,
and make sure that the configured limits of the logging flash-size command are set correctly. If the error is a flash file system I/O error, then contact the Cisco TAC for assistance.
414003
Error Message %ASA-3-414003: TCP Syslog Server intf: IP_Address/port not responding. New connections are [permitted|denied] based on logging permit-hostdown policy. Explanation The TCP syslog server for remote host logging was successful, is connected to the
server, and new connections are permitted or denied based on the logging permit-hostdown policy. If the logging permit-hostdown policy is configured, a new connection is permitted. If not configured, a new connection is denied.

intfInterface of the ASA to which the server is connected IP_AddressIP address of the remote TCP syslog server portPort of the remote TCP syslog server
Recommended Action Validate that the configured TCP syslog server is up. To permit new connections, configure the logging permit-hostdown policy. To deny new connections, do not configure the logging permit-hostdown policy.
414004
Error Message %ASA-6-414004: TCP Syslog Server intf: IP_Address/port - Connection restored Explanation A retry to the TCP syslog server has been successful, and the connection has been
established. This message is the first to reach the syslog server after a successful connection.

1-235
Syslog Messages
414005
Error Message %ASA-3-414005: TCP Syslog Server intf: IP_Address/port connected, New connections are permitted based on logging permit-hostdown policy Explanation The TCP syslog server for remote host logging was successful, is connected to the server, and new connections are permitted based on the logging permit-hostdown policy. If the logging permit-hostdown policy is configured, a new connection is permitted.
414006
Error Message %ASA-3-414006: TCP Syslog Server configured and logging queue is full. New connections denied based on logging permit-hostdown policy. Explanation The logging queue is close to reaching the configured limit, so there is a risk that syslog
messages will be discarded.

Recommended Action See the "Configuring the Logging Queue" section in the CLI configuration guide for information about how to tune the queue size to avoid this situation. If you want to deny new connections in this case, use the no logging permit-hostdown command. If you want to allow new connections in this case, use the logging permit-hostdown command.
414007
Error Message %ASA-6-414007: TCP Syslog Server connection restored. New connections are allowed. Explanation The TCP syslog server for remote host logging was successfully connected and new
connections are permitted.

1-236
Chapter 1
414008
Error Message %ASA-6-414008: New connections are now allowed due to change of logging permit-hostdown policy. Explanation An administrator changed the logging permit-hostdown policy by entering the logging permit-hostdown command at a time when new connections are being denied. Due to this change of policy, new connections will be allowed. Recommended Action None required.
415001
Error Message %ASA-6-415001: HTTP - matched matched_string in policy-map map_name, header field count exceeded connection_action from int_type:IP_address/port_num to int_type:IP_address/port_num Explanation This message is generated when one of the following occurs:
The total number of fields in the HTTP header exceeds the user-configured number of header fields. The relevant command is: match {request | response} header count num. The appearance of a specified field in the HTTP header exceeds the user-configured number for this header field. The relevant command is: match {request | response} header header-name count num. matched_stringThe matched string is one of the following: - The class map ID, followed by the name of the class map. This string appears when the class map is user configured. - The actual match command that initiated the message. This string appears when the class map is internal.
map_nameThe name of the policy map connection_actionDropping the connection or resetting the connection interface_typeThe type of interface (for example, DMZ or outside) IP_addressThe IP address of the interface port_numThe port number
Recommended Action Enter the match {request | response} header command to reconfigure the
HTTP header field value.
1-237
Syslog Messages
415002
Error Message %ASA-6-415002: HTTP - matched matched_string in policy-map map_name, header field length exceeded connection_action from int_type:IP_address/port_num to int_type:IP_address/port_num Explanation The specified HTTP header field length exceeded the user-configured length.
matched_stringThe matched string is one of the following: - The class map ID, followed by the name of the class map. This string appears when the class map is user configured. - The actual match command that initiated the message. This string appears when the class map is internal.
map_nameThe name of the policy map connection_actionDropping connection or Resetting connection interface_typeThe type of interface (for example, DMZ or outside) IP_addressThe IP address of the interface port_numThe port number
Recommended Action Enter the match {request | response} header header_name length gt num
command to change the HTTP header field length.
415003
Error Message %ASA-6-415003: HTTP - matched matched_string in policy-map map_name, body length exceeded connection_action from int_type:IP_address/port_num to int_type:IP_address/port_num Explanation The length of the message body exceeded the user-configured length.
Recommended Action Enter the match {request | response} body length gt num command to change
the length of the message body.
1-238
Chapter 1
415004
Error Message %ASA-5-415004: HTTP - matched matched_string in policy-map map_name, content-type verification failed connection_action from int_type:IP_address/port_num to int_type:IP_address/port_num Explanation The magic number in the body of the HTTP message is not the correct magic number
for the MIME-type specified in the content-type field in the HTTP message header.
Recommended Action Enter the match {request | response} header content-type violation command to correct the error.
415005
Error Message %ASA-5-415005: HTTP - matched matched_string in policy-map map_name, URI length exceeded connection_action from int_type:IP_address/port_num to int_type:IP_address/port_num Explanation The length of the URI exceeded the user-configured length.
Recommended Action Enter the match request uri length gt num command to change the length of
the URI.
1-239
Syslog Messages
415006
Error Message %ASA-5-415006: HTTP - matched matched_string in policy-map map_name, URI matched connection_action from int_type:IP_address/port_num to int_type:IP_address/port_num Explanation The URI matched the regular expression that the user configured. See the match
request uri regex {regex-name | class class-name} command for more information.
415007
Error Message %ASA-5-415007: HTTP - matched matched_string in policy-map map_name, Body matched connection_action from int_type:IP_address/port_num to int_type:IP_address/port_num Explanation The message body matched the regular expression that the user configured. See the
match {request | response} body regex {regex-name | class class-name} command for more information.
map_nameThe name of the policy map connection_actionDropping the connection or resetting the connection interface_typeThe type of interface (for example, DMZ or outside) IP_addressThe IP address of the interface port_numThe port number None required.
Recommended Action
1-240
Chapter 1
415008
Error Message %ASA-5-415008: HTTP - matched matched_string in policy-map map_name, header matched connection_action from int_type:IP_address/port_num to int_type:IP_address/port_num Explanation A value in a user-specified field in the message header matched the regular expression
that the user configured. See the match {request | response } header header-field-name {regex-name | class class-name} command for more information.
415009
Error Message %ASA-5-415009: HTTP - matched matched_string in policy-map map_name, method matched connection_action from int_type:IP_address/port_num to int_type:IP_address/port_num Explanation The HTTP method matched the user-configured regular expression. See the match
request method {regex-name | class class-name} command for more information.
1-241
Syslog Messages
415010
Error Message %ASA-5-415010: matched matched_string in policy-map map_name, transfer encoding matched connection_action from int_type:IP_address/port_num to int_type:IP_address/port_num Explanation The value in the transfer encoding field matched the user-configured regular expression
or keyword. See the match {request | response} header transfer-encoding {{regex-name | class class-name} | keyword} command for more information.
1-242
Chapter 1
415011
Error Message %ASA-5-415011: HTTP - policy-map map_name:Protocol violation connection_action from int_type:IP_address/port_num to int_type:IP_address/port_num Explanation The HTTP parser cannot detect a valid HTTP message in the first few bytes of an HTTP
message.

Recommended Action Enter the protocol-violation action {drop | reset} log command to correct the
problem.
415012
Error Message %ASA-5-415012: HTTP - matched matched_string in policy-map map_name, Unknown mime-type connection_action from int_type:IP_address/port_num to int_type:IP_address/port_num Explanation The content-type field did not contain a MIME type that matches a built-in MIME type.
1-243
Syslog Messages
Recommended Action Enter the match {request | response} header content-type unknown
command to correct the problem.
415013
Error Message %ASA-5-415013: HTTP - policy-map map-name:Malformed chunked encoding connection_action from int_type:IP_address/port_num to int_type:IP_address/port_num Explanation A chunked encoding was malformed, and the HTTP message cannot be parsed. In
addition, logging for the protocol-violation command was configured.

map-name The name of the policy map connection_actionDropping the connection or resetting the connection interface_typeThe type of interface (for example, DMZ or outside) IP_addressThe IP address of the interface port_numThe port number
problem.
415014
Error Message %ASA-5-415014: HTTP - matched matched_string in policy-map map_name, Mime-type in response wasn't found in the accept-types of the request connection_action from int_type:IP_address/port_num to int_type:IP_address/port_num Explanation The MIME type in an HTTP response was not in the accept field of the request.
map_nameThe name of the policy map connection_actionDropping the connection or resetting the connection interface_typeThe type of interface (for example, DMZ or outside) IP_addressThe IP address of the interface
1-244
Chapter 1
port_numThe port number
Recommended Action Enter the match req-resp content-type mismatch command to correct the
problem.
415015
Error Message %ASA-5-415015: HTTP - matched matched_string in policy-map map_name, transfer-encoding unknown connection_action from int_type:IP_address/port_num to int_type:IP_address/port_num Explanation An empty transfer encoding occurred.
Recommended Action Enter the match {request | response} header transfer-encoding empty
command to correct the problem.
415016
Error Message %ASA-4-415016: policy-map map_name:Maximum number of unanswered HTTP requests exceeded connection_action from int_type:IP_address/port_num to int_type:IP_address/port_num Explanation The number of unanswered HTTP requests exceeded the internal number of requests
allowed.

problem.
1-245
Syslog Messages
415017
Error Message %ASA-6-415017: HTTP - matched_string in policy-map map_name, arguments matched connection_action from int_type:IP_address/port_num to int_type:IP_address/port_num Explanation A pattern in the arguments matches the user-configured regular expression or keyword.
See the match request args regex {regex-name | class class-name} command for more information.
415018
Error Message %ASA-5-415018: HTTP - matched matched_string in policy-map map_name, Header length exceeded connection_action from int_type:IP_address/port_num to int_type:IP_address/port_num Explanation The total header length exceeded the user-configured length for the header.
Recommended Action Enter the match {request | response} header length gt num command to
reduce the length of the header.
1-246
Chapter 1
415019
Error Message %ASA-5-415019: HTTP - matched matched_string in policy-map map_name, status line matched connection_action from int_type:IP_address/port_num to int_type:IP_address/port_num Explanation The status line in a response matched a user-configured regular expression. See the
match response status-line regex {regex-name | class class-name } command for more information.
415020
Error Message %ASA-5-415020: HTTP - matched matched_string in policy-map map_name, a non-ASCII character was matched connection_action from int_type:IP_address/port_num to int_type:IP_address/port_num Explanation A non-ASCII character was found.
Recommended Action Enter the match {request | response} header non-ascii command to correct
the problem.
1-247
Syslog Messages
416001
Error Message %ASA-4-416001: Dropped UDP SNMP packet from source_interface:source_IP/source_port to dest_interface:dest_address/dest_port; version (prot_version) is not allowed through the firewall Explanation An SNMP packet was denied passage through the ASA because of a bad packet format or because the prot_version is not allowed through the ASA. The prot_version parameter can be one of the following values: 1, 2, 2c, or 3. Recommended Action Change the settings for SNMP inspection using the snmp-map command, which allows the user to permit or deny specific protocol versions.
417001
Error Message %ASA-4-417001: Unexpected event received: number Explanation A process received a signal, but no handler was found for the event. Recommended Action If the problem persists, contact the Cisco TAC.
417004
Error Message %ASA-4-417004: Filter violation error: conn number (string:string) in string Explanation A client tried to modify a route attribute that the client does not own. Recommended Action If the problem persists, contact the Cisco TAC.
417006
Error Message %ASA-4-417006: No memory for string) in string. Handling: string Explanation An operation failed because of low memory, but will be handled with another
mechanism.
1-248
Chapter 1
418001
Error Message %ASA-4-418001: Through-the-device packet to/from management-only network is denied: protocol_string from interface_name IP_address (port) [([idfw_user|FQDN_string], sg_info)] to interface_name IP_address (port) [(idfw_user|FQDN_string), sg_info] Explanation A packet from the specified source to the destination was dropped because it is
traversing the ASA to and from the management-only network.

protocol_stringTCP, UDP, ICMP, or protocol ID as a number in decimal interface_name Interface name IP_addressIP address portPort number sg_infoSecurity group name or tag for the specified IP address
Recommended Action Determine who is generating this packet and why.
419001
Error Message %ASA-4-419001: Dropping TCP packet from src_ifc:src_IP/src_port to dest_ifc:dest_IP/dest_port, reason: MSS exceeded, MSS size, data size Explanation The length of the TCP packet exceeded the MSS advertised in the three-way handshake.
src_ifcInput interface name src_IPThe source IP address of the packet src_portThe source port of the packet dest_ifcThe output interface name dest_IPThe destination IP address of the packet dest_portThe destination port of the packet
Recommended Action If there is a need to allow packets that exceed the MSS, create a TCP map using
the exceed-mss command, as in the following example:

hostname# access-list http-list permit tcp any host server_ip eq 80 hostname# class-map http hostname# match access-list http-list hostname# tcp-map tmap hostname# exceed-mss allow hostname# policy-map global_policy hostname# class http hostname# set connection advanced-options tmap
1-249
Syslog Messages
419002
Error Message %ASA-4-419002: Received duplicate TCP SYN from in_interface:src_address/src_port to out_interface:dest_address/dest_port with different initial sequence number. Explanation A duplicate TCP SYN was received during the three-way-handshake that has a different
initial sequence number from the SYN that opened the embryonic connection. This may indicate that SYNs are being spoofed. This message occurs in Release 7.0.4.1 and later.

in_interfaceThe input interface src_addressThe source IP address of the packet src_portThe source port of the packet out_interfaceThe output interface dest_addressThe destination IP address of the packet dest_portThe destination port of the packet
419003
Error Message %ASA-4-419003: Cleared TCP urgent flag from out_ifc:src_ip/src_port to in_ifc:dest_ip/dest_port. Explanation A duplicate TCP SYN was received during the three-way-handshake that has a different
initial sequence number from the SYN that opened the embryonic connection. This may indicate that SYNs are being spoofed. This message occurs in Release 7.0.4.1 and later.

Recommended Action If you need to keep the urgent flag in TCP headers, use the urgent-flag allow
command in TCP map configuration mode.
1-250
Chapter 1
420001
Error Message %ASA-3-420001: IPS card not up and fail-close mode used, dropping ICMP packet ifc_in:SIP to ifc_out:DIP (type ICMP_TYPE, code ICMP_CODE)
For example:
%ASA-3-420001: IPS card not up and fail-close mode used, dropping TCP packet from ifc_in:SIP/SPORT to ifc_out:DIP/DPORT\n %ASA-3-420001: IPS card not up and fail-close mode used, dropping UDP packet from ifc_in:SIP/SPORT to ifc_out:DIP/DPORT\n %ASA-3-420001: IPS card not up and fail-close mode used, dropping protocol protocol packet from ifc_in:SIP to ifc_out:DIP\n
Explanation Packets are dropped when the IPS fail-close mode is used, and the IPS card is not up.
This message is rate limited.

ifc_inInput interface name ifc_outOutput interface name SIPSource IP of the packet SPORT Source port of the packet DIPDestination IP of the packet DPORT Destination port of the packet ICMP_TYPEType of the ICMP packet ICMP_CODECode of the ICMP packet
Recommended Action Bring up the IPS card.
420002
Error Message %ASA-4-420002: IPS requested to drop ICMP packets ifc_in:SIP to ifc_out:DIP (type ICMP_TYPE, code ICMP_CODE)
For example:
%ASA-4-420002: IPS requested to drop TCP packet from ifc_in:SIP/SPORT to ifc_out:DIP/DPORT\n %ASA-4-420002: IPS requested to drop UDP packet from ifc_in:SIP/SPORT to ifc_out:DIP/DPORT\n %ASA-4-420002: IPS requested to drop protocol packet from ifc_in:SIP to ifc_out:DIP\n
Explanation IPS requested that the packet be dropped.
ifc_inInput interface name ifc_outOutput interface name SIPSource IP of the packet SPORT Source port of the packet DIPDestination IP of the packet
1-251
Syslog Messages
DPORT Destination port of the packet ICMP_TYPEType of the ICMP packet ICMP_CODECode of the ICMP packet
420003
Error Message %ASA-4-420003: IPS requested to reset TCP connection from ifc_in:SIP/SPORT to ifc_out:DIP/DPORT Explanation IPS requested a reset of a TCP connection.
ifc_inInput interface name ifc_outOutput interface name SIPSource IP of the packet SPORT Source port of the packet DIPDestination IP of the packet DPORT Destination port of the packet
420004
Error Message %ASA-6-420004: Virtual Sensor sensor_name was added on the AIP SSM Explanation A virtual sensor was added on the AIP SSM card.
nCard number
420005
Error Message %ASA-6-420005: Virtual Sensor sensor_name was deleted from the AIP SSM Explanation A virtual sensor was deleted from the AIP SSM card.
nCard number
1-252
Chapter 1
420006
Error Message %ASA-3-420006: Virtual Sensor not present and fail-close mode used, dropping protocol packet from ifc_in:SIP/SPORT to ifc_out:DIP/DPORT Explanation Packets are dropped when the IPS fail-close mode is used, and the virtual sensor used for the packet is not present.
protocolProtocol used to send the packet ifc_inInput interface name ifc_outOutput interface name SIPSource IP address of the packet SPORTSource port of the packet DIPDestination IP address of the packet DPORTDestination port of the packet
Recommended Action Add the virtual sensor.
420007
Error Message %ASA-4-420007: application-string cannot be enabled for the module in slot slot_id. The modules current software version does not support this feature. Please upgrade the software on the module in slot slot_id to support this feature. Received backplane header version version_number, required backplane header version version_number or higher. Explanation This message is generated by any new feature in the ASA that needs a corresponding
software version in the SSM or SSC hardware module. The message is sent each time that the ASA module manager detects state changes in the SSM or SSC hardware module.

application-stringThe name of the application (for example, Promiscuous IDS) slot_idThe module identifier, which is 1 for the current ASA version_numberThe version number of the message header between the ASA and the IPS application
Recommended Action Load the SSM or SSC hardware module with the correct software images that support the designated application.
1-253
Syslog Messages
420008
Error Message %ASA-3-420008: IPS module license disabled and fail-close mode used, dropping packet. Explanation The IPS module license has been disabled and when the fail-close mode is configured, all traffic destined for the IPS module will be dropped. You can check the status of the license by using the show activation-key command. Recommended Action Use the activation-key command to apply an activation key that has the IPS
license enabled.
421001
Error Message %ASA-3-421001: TCP|UDP flow from interface_name:IP_address/port to interface_name:IP_address/port is dropped because application has failed. Explanation A packet was dropped because the CSC SSM application failed. By default, this message is rate limited to 1 message every 10 seconds.
interface_nameThe interface name IP_addressThe IP address portThe port number applicationThe CSC SSM is the only application supported in the current release
Recommended Action Determine the problem with the service module.
421002
Error Message %ASA-6-421002: TCP|UDP flow from interface_name:IP_address/port to interface_name:IP_address/port bypassed application checking because the protocol is not supported. Explanation The connection bypassed service module security checking because the protocol that it
is using cannot be scanned by the service module. For example, the CSC SSM is not capable of scanning Telnet traffic. If the user configures Telnet traffic to be scanned, the traffic will bypass the scanning service. By default, this message is rate limited to 1 message every 10 seconds.

IP_addressThe IP address portThe port number interface_nameThe name of the interface on which the policy is applied applicationThe CSC SSM is the only application supported in the current release
Recommended Action The configuration should be modified to only include protocols that are supported by the service module.
1-254
Chapter 1
421003
Error Message %ASA-3-421003: Invalid data plane encapsulation. Explanation A packet injected by the service module did not have the correct data plane header. Packets exchanged on the data backplane adhere to a Cisco proprietary protocol called ASDP. Any packet that does not have the proper ASDP header is dropped. Recommended Action Use the capture name type asp-drop [ssm-asdp-invalid-encap] command to capture the offending packets and contact the Cisco TAC.
421004
Error Message %ASA-7-421004: Failed to inject {TCP|UDP} packet from IP_address/port to IP_address/port Explanation The ASA has failed to inject a packet as instructed by the service module. This may happen if the ASA tries to inject a packet into a flow that has already been released or when the ASA maintains its connection table independently from the service module. Normally it will not cause any problem.
IP_addressThe IP address portThe port number
Recommended Action If ASA performance is affected, or if the problem persists, contact the Cisco
TAC.
421005
Error Message %ASA-6-421005: interface_name:IP_address is counted as a user of application Explanation A host has been counted toward the license limit. The specified host was counted as a user of application. The total number of users in 24 hours is calculated at midnight for license validation.
interface_nameThe interface name IP_addressThe IP address applicationThe CSC SSM
Recommended Action None required. However, if the overall count exceeds the user license that you have purchased, contact the Cisco TAC to upgrade your license.
1-255
Syslog Messages
421006
Error Message %ASA-6-421006: There are number users of application accounted during the past 24 hours. Explanation The total number of users who have used an application for the past 24 hours have been identified. This message is generated every 24 hours to give the total number of hosts that have used services provided by the service module.
applicationThe CSC SSM
Recommended Action None required. However, if the overall count exceeds the user license that you have purchased, contact the Cisco TAC to upgrade your license.
421007
Error Message %ASA-3-421007: TCP|UDP flow from interface_name:IP_address/port to interface_name:IP_address/port is skipped because application has failed. Explanation A flow was skipped because the service module application has failed. By default, this
message is rate limited to 1 message every 10 seconds.

IP_addressThe IP address portThe port number interface_nameThe name of the interface on which the policy is applied applicationThe CSC SSM
Recommended Action Determine the problem with the service module.
422004
Error Message %ASA-4-422004: IP SLA Monitor number0: Duplicate event received. Event number number1 Explanation The IP SLA monitor process has received a duplicate event. Currently, this message applies to destroy events. Only one destroy request will be applied. This is only a warning message.
number0The SLA operation number number1The SLA operation event ID
Recommended Action If this recurs, enter the show sla monitor configuration SLA_operation_id command and copy the output of the command. Copy the message as it appears on the console or in the system log. Then contact the Cisco TAC and provide the representative with the information that you have, along with information about the application that is configuring and polling the SLA probes.
1-256
Chapter 1
422005
Error Message %ASA-4-422005: IP SLA Monitor Probe(s) could not be scheduled because clock is not set. Explanation One or more IP SLA monitor probes cannot be scheduled because the system clock was
not set.
Recommended Action Make sure that the system clock is functional by using NTP or another
mechanism.
422006
Error Message %ASA-4-422006: IP SLA Monitor Probe number: string Explanation The IP SLA monitor probe cannot be scheduled. Either the configured starting time has already occurred or the starting time is invalid.
numberThe SLA operation ID stringA string describing the error
Recommended Action Reschedule the failed probe with a valid start time.
423001
Error Message %ASA-4-423001: {Allowed | Dropped} invalid NBNS pkt_type_name with error_reason_str from ifc_name:ip_address/port to ifc_name:ip_address/port. Explanation The NBNS packet format is incorrect. Recommended Action None required.
423002
Error Message %ASA-4-423002: {Allowed | Dropped} mismatched NBNS pkt_type_name with error_reason_str from ifc_name:ip_address/port to ifc_name:ip_address/port. Explanation An NBNS ID mismatch occurred. Recommended Action None required.
1-257
Syslog Messages
423003
Error Message %ASA-4-423003: {Allowed | Dropped} invalid NBDGM pkt_type_name with error_reason_str from ifc_name:ip_address/port to ifc_name:ip_address/port. Explanation The NBDGM packet format is incorrect. Recommended Action None required.
423004
Error Message %ASA-4-423004: {Allowed | Dropped} mismatched NBDGM pkt_type_name with error_reason_str from ifc_name:ip_address/port to ifc_name:ip_address/port. Explanation An NBDGM ID mismatch occurred. Recommended Action None required.
423005
Error Message %ASA-4-423005: {Allowed | Dropped} NBDGM pkt_type_name fragment with error_reason_str from ifc_name:ip_address/port to ifc_name:ip_address/port. Explanation The NBDGM fragment format is incorrect. Recommended Action None required.
1-258
Chapter 1
424001
Error Message %ASA-4-424001: Packet denied protocol_string intf_in:src_ip/src_port [([idfw_user | FQDN_string], sg_info)] intf_out:dst_ip/dst_port[([idfw_user | FQDN_string], sg_info)]. [Ingress|Egress] interface is in a backup state. Explanation A packet was dropped because it was traversing the ASA to or from a redundant
interface. Interface functionality is limited on low-end platforms. The interface specified by the backup interface command can only be a backup for the primary interface configured. If the default route to the primary interface is up, any traffic through the ASA from the backup interface will be denied. Conversely, if the default route to the primary interface is down, traffic through the ASA from the primary interface will be denied.

protocol_stringThe protocol string; for example, TCP or protocol ID (a decimal number) intf_inThe input interface name src_ipThe source IP address of the packet src_portThe source port of the packet intf_outThe output interface name dst_ipThe destination IP address of the packet dst_portThe destination port of the packet sg_infoThe security group name or tag for the specified IP address
Recommended Action Determine the source of the denied packet.
424002
Error Message %ASA-4-424002: Connection to the backup interface is denied: protocol_string intf:src_ip/src_port intf:dst_ip/dst_port Explanation A connection was dropped because it is in a backup state. Interface functionality is
limited on low-end platforms. The backup interface can only be a backup for the primary interface specified by the backup interface command. If the default route to the primary interface is up, any connection to the ASA through the backup interface will be denied. Conversely, if the default route to the primary interface is down, connections to the ASA through the primary interface will be denied.

protocol_stringThe protocol string; for example, TCP or protocol ID (a decimal number) intf_inThe input interface name src_ipThe source IP address of the packet src_portThe source port of the packet intf_outThe output interface name dst_ipThe destination IP address of the packet dst_portThe destination port of the packet
Recommended Action Determine the source of the denied packet.
1-259
Syslog Messages
425001
Error Message %ASA-6-425001 Redundant interface redundant_interface_name created. Explanation The specified redundant interface was created in the configuration.
redundant_interface_nameRedundant interface name
425002
Error Message %ASA-6-425002 Redundant interface redundant_interface_name removed. Explanation The specified redundant interface was removed from the configuration.
redundant_interface_nameRedundant interface name
425003
Error Message %ASA-6-425003 Interface interface_name added into redundant interface redundant_interface_name. Explanation The specified physical interface was added to the specified redundant interface as a member interface.
interface_nameAn interface name redundant_interface_nameRedundant interface name
425004
Error Message %ASA-6-425004 Interface interface_name removed from redundant interface redundant_interface_name. Explanation The specified redundant interface was removed from the specified redundant interface.
1-260
Chapter 1
425005
Error Message %ASA-5-425005 Interface interface_name become active in redundant interface redundant_interface_name Explanation Within a redundant interface, one member interface is the active member. Traffic only
passes through the active member interface. The specified physical interface became the active member of the specified redundant interface. Member interface switchover occurs when one of the following is true:
The redundant-interface interface-name active-member interface-name command was
executed.
The active member interface is down, while the standby member interface is up. The standby member interface comes up (from down), while the active member interface
remains down.

Recommended Action Check the status of the member interfaces.
425006
Error Message %ASA-3-425006 Redundant interface redundant_interface_name switch active member to interface_name failed. Explanation An error occurred when member interface switchover was attempted.
redundant_interface_nameRedundant interface name interface_nameAn interface name
426001
Error Message %ASA-6-426001: PORT-CHANNEL:Interface ifc_name bundled into EtherChannel interface Port-channel num Explanation The interface port-channel num or the channel-group num mode mode command has been used on a nonexistent port channel.
ifc_nameThe EtherChannel interface name numThe port channel number
1-261
Syslog Messages
426002
Error Message %ASA-6-426002: PORT-CHANNEL:Interface ifc_name unbundled from EtherChannel interface Port-channel num Explanation The no interface port-channel num command has been used.
ifc_nameThe EtherChannel interface name numThe port channel number
426003
Error Message %ASA-6-426003: PORT-CHANNEL:Interface ifc_name1 has become standby in EtherChannel interface Port-channel num Explanation The channel-group num mode mode command has been used.
ifc_name1The EtherChannel interface name numThe port channel number
426004
Error Message %ASA-4-426004: PORT-CHANNEL: Interface ifc_name1 is not compatible with ifc_name and will be suspended (speed of ifc_name1 is X Mbps, Y is 1000 Mbps).
Error Message %ASA-4-426004: Interface ifc_name1 is not compatible with ifc_name1 and will be suspended (ifc_name1 is Full-duplex, ifc_name1 is Half-duplex) Explanation The channel-group num mode mode command is executed on a physical interface and
there is a speed or duplex mismatch of this physical interface with that of the port channel.

ifc_nameThe interface that is being added to the port channel ifc_name1The interface that is already in the port channel and in a bundled state
Recommended Action Do one of the following:
Change the speed of the physical interface to that of the port channel and execute the channel-group num mode mode command again. Leave the member interface in a suspended state. When the last active member is removed, then that member will try to reestablish LACP on the suspended member.
1-262
Chapter 1
426101
Error Message %ASA-6-426101: PORT-CHANNEL:Interface ifc_name is allowed to bundle into EtherChannel interface port-channel id by CLACP Explanation A port has been bundled in a span-cluster channel group. Recommended Action None required.
426102
Error Message %ASA-6-426102: PORT-CHANNEL:Interface ifc_name is moved to standby in EtherChannel interface port-channel id by CLACP Explanation A port has been moved to hot-standby state in a span-cluster channel group. Recommended Action None required.
426103
Error Message %ASA-6-426103: PORT-CHANNEL:Interface ifc_name is selected to move from standby to bundle in EtherChannel interface port-channel id by CLACP Explanation A standby port has been selected to move to bundled state in a span-cluster channel
group.
426104
Error Message %ASA-6-426104: PORT-CHANNEL:Interface ifc_name is unselected in EtherChannel interface port-channel id by CLACP Explanation A bundled port has been unbundled in a span-cluster channel group to obtain space for other ports to be bundled. Recommended Action None required.
1-263
Syslog Messages
428002
Error Message %ASA-6-428002: WAAS confirmed from in_interface:src_ip_addr/src_port to out_interface:dest_ip_addr/dest_port, inspection services bypassed on this connection. Explanation WAAS optimization was detected on a connection. All layer 7 inspection services,
including IPS, are bypassed on WAAS-optimized connections.

Recommended Action No action is required if the network includes WAE devices; otherwise, the
network administrator should investigate the use of the WAAS option on this connection.
429001
Error Message %ASA-3-429001: CXSC card not up and fail-close mode used. Dropping protocol packet from interface_name:ip_address/port to interface_name:ip_address/port Explanation Data has been dropped because an SSP is down and a fail-close policy exists. Recommended Action Check the status of the service module and contact the Cisco TAC for
assistance, if necessary.
429002
Error Message %ASA-4-429002: CXSC service card requested to drop protocol packet from interface_name:ip_address/port to interface_name:ip_address/port Explanation The CXSC SSP requested that the ASA drop a packet of a connection. Recommended Action None.
429003
Error Message %ASA-4-429003: CXSC service card requested to reset TCP connection from interface_name:ip_addr/port to interface_name:ip_addr/port Explanation The CXSC SSP requested that the ASA reset a TCP connection. Recommended Action None required.
1-264
Chapter 1
429004
Error Message %ASA-3-429004: Unable to set up authentication-proxy rule for the cx action on interface interface_name for policy_type service-policy. Explanation The ASA could not set up to-the-box rules for authentication proxy with the CXSC
action because of some internal errors, such as insufficient memory.

Recommended Action This error should not occur. Contact the Cisco TAC.for assistance.
429005
Error Message %ASA-6-429005: Set up authentication-proxy protocol_type rule for the CXSC action on interface interface_name for traffic destined to ip_address/port for policy_type service-policy. Explanation The ASA successfully set up to-the-box rules for authentication proxy with the CXSC
action.
429006
Error Message %ASA-6-429006: Cleaned up authentication-proxy rule for the CXSC action on interface interface_name for traffic destined to ip_address for policy_type service-policy. Explanation The ASA successfully cleaned up to-the-box rules for authentication proxy with the CXSC action. Recommended Action None.
429007
Error Message %ASA-4-429007: CXSC redirect will override Scansafe redirect for flow from interface_name:ip_address/port to interface_name:ip_address/port with username Explanation A flow matches both CXSC and Scansafe redirects. The message indicates that the
CXSC redirect overrides the Scansafe redirect for the displayed flow.
Recommended Action If this is unwanted behavior, then reconfigure the policy to ensure that no overlap of CXSC and Scansafe redirection occurs for the same flow.
1-265
Syslog Messages
429008
Error Message %ASA-4-429008: Unable to respond to VPN query from CX for session 0x%x. Reason %s Explanation The CX sent a VPN session query to the ASA, but it did not respond either because of
an invalid session ID or another reason. Valid reasons can be any of the following:

TLV length is invalid TLV memory allocation failed VPN session query message enqueue failed VPN session ID is invalid
431001
Error Message %ASA-4-431001: RTP conformance: Dropping RTP packet from in_ifc:src_ip/src_port to out_ifc:dest_ip/dest_port, Drop reason: drop_reason value Explanation The RTP packet was dropped.
in_ifcThe input interface src_ipThe source IP address of the packet src_portThe source port of the packet out_ifcThe output interface dest_ipThe destination IP address of the packet dest_portThe destination port of the packet drop_reasonOne of the following drop reasons: - Incorrect version valueThe version number from the packet is incorrect. - Invalid payload-type valueThe payload type from the packet is invalid. - Incorrect SSRC valueThe SSRC from the packet is incorrect. - Out-of-range sequence number value sequence number from the packet. - Out of sequence in packet in probation value sequence number from the packet.
Recommended Action Examine the dropped RTP packets to determine which field the RTP source is setting incorrectly. Also examine the source to verify that it is legitimate and not an attacker trying to misuse an opening in the ASA.
1-266
Chapter 1
431002
Error Message %ASA-4-431002: RTCP conformance: Dropping RTCP packet from in_ifc:src_ip/src_port to out_ifc:dest_ip/dest_port, Drop reason: drop_reason value Explanation The RTCP packet was dropped.
in_ifcThe input interface src_ipThe source IP address of the packet src_portThe source port of the packet out_ifcThe output interface dest_ipThe destination IP address of the packet dest_portThe destination port of the packet drop_reasonOne of the following drop reasons: - Incorrect version valueThe version number from the packet is incorrect. - Invalid payload-type valueThe payload type from the packet is incorrect.
Recommended Action Examine the dropped RTP packets to determine which field the RTP source is setting incorrectly. Also examine the source to verify that it is legitimate and not an attacker trying to misuse an opening in the ASA.
444004
Error Message %ASA-2-444004: Temporary license key key has expired. Applying permanent license key permkey Explanation The temporary license that was installed has expired. The features that the license provided are no longer available.
keyThe temporary activation key permkeyThe permanent activation key
Recommended Action A permanent license should be purchased and installed.
444005
Error Message %ASA-4-444005: Timebased activation key activation-key will expire in num days Explanation This message is generated every 24 hours, indicating that the temporary license will
expire in the number of days specified. After that date, the features that the license provided will no longer be available.
activation-keyThe temporary activation key
1-267
Syslog Messages
numThe number of days left until expiration
Recommended Action If the amount of time remaining is less than 30 days, you should purchase another time-based activation key before the temporary license runs out.
444007
Error Message %ASA-2-444007: Timebased activation key activation-key has expired. Reverting to [permanent | timebased] license key. The following features will be affected: feature, feature Explanation The time-based activation key has expired. The specified features that the license
provided are no longer available.

activation-keyThe temporary activation key featureThe name of the licensed feature being affected
Recommended Action You must purchase another time-based activation key as soon as possible to prevent service disruption for the features specified.
444008
Error Message %ASA-4-444008: %s license has expired, and the system is scheduled to reload in x days. Apply a new activation key to enable %s license and prevent the automatic reload. Explanation The specific license has expired, which will cause the system to reload in x days. Apply a new activation key to enable the specific license and prevent automatic reload. Recommended Action Apply a new activation key to enable the specific license and prevent automatic
reload.
444009
Error Message %ASA-2-444009: %s license has expired 30 days ago. The system will now reload. Explanation The specific license expired 30 days ago. The system will reload. Recommended Action None required.
1-268
Chapter 1
444100
Error Message %ASA-5-444100: Shared request request failed. Reason: reason Explanation A shared license client request was unsuccessfully sent or processed by the server.
requestValid requests are: - get AnyConnect Premium - release AnyConnect Premium - transfer AnyConnect Premium reasonThe reason that the request failed. Valid reasons are: - connection failed to server - version not supported by server - message signature invalid - client ID unknown by server - server is not active - license capacity reached
444101
Error Message %ASA-5-444101: Shared license service is active. License server address: address Explanation The shared license server has become active.
addressThe license server IPv4 or IPv6 address
444102
Error Message %ASA-2-444102: Shared license service inactive. License server is not responding. Explanation The shared license service was inactive because the license server was not responding. The ASA failed to register with the shared license server. Recommended Action Verify that the license server address, secret, and port are configured correctly.
1-269
Syslog Messages
444103
Error Message %ASA-6-444103: Shared licensetype license usage is over 90% capacity. Explanation The shared license usage on the network is over 90 percent capacity.
licensetypeAnyConnect Premium
444104
Error Message %ASA-6-444104: Shared licensetype license availability: value. Explanation The shared license availability on the network appeared.
licensetypeAnyConnect Premium valueThe license availability
444105
Error Message %ASA-2-444105: Released value shared licensetype license(s). License server has been unreachable for 24 hours. Explanation The shared license server has been unreachable for 24 hours, and all shared licenses that
have been acquired by the ASA have been released. The ASA failed to register with the license server.

licensetypeAnyConnect Premium valueThe license availability
Recommended Action Verify the connectivity to the license server, and that the configuration has not
been changed on the license server.
444106
Error Message %ASA-4-444106: Shared license backup server address is not available. Explanation The shared license backup server is not reachable. License server information is not synchronized with the backup device.
addressThe IPv4 or IPv6 address of the backup license server
1-270
Chapter 1
444107
Error Message %ASA-6-444107: Shared license service status on interface ifname. Explanation The shared license service has been enabled or disabled on the specified interface.
ifnameThe interface name. statusThe status of the license server. Valid values are enabled or disabled.
444108
Error Message %ASA-6-444108: Shared license state client id id. Explanation The multi-site license client ID has registered or expired with the server.
idThe ID of the client stateThe state of the license server. Valid values are registered or expired.
444109
Error Message %ASA-4-444109: Shared license backup server role changed to state. Explanation The shared backup license server role has changed.
stateThe state of the license server. Valid values are active or inactive.
444110
Error Message %ASA-4-444110: Shared license server backup has days remaining as active license server. Explanation The shared backup license server is in an active role and remains active for a specified
number of days. The ASA failed to register with the license server, and needs to register with the primary license server soon.
daysThe number of days left as the active license server
Recommended Action Verify that the license server is online and reachable by the ASA.
1-271
Syslog Messages
444111
Error Message %ASA-2-444111: Shared license backup service has been terminated due to the primary license server address being unavailable for more than days days. The license server needs to be brought back online to continue using shared licensing. Explanation The shared backup license server active time has expired. The primary server needs to
go online in order for the shared license service to continue.

addressThe IPv4 or IPv6 address of the license server daysThe number of days that the license server has been unavailable
Recommended Action Register with the primary license server in order to continue using the shared
license service.
446001
Error Message %ASA-4-446001: Maximum TLS Proxy session limit of max_sess reached. Explanation A configured maximum session limit for TLS proxy was reached. New sessions beyond
the limit were denied.
max_sessThe currently effective maximum session limit
Recommended Action If more TLS sessions are needed, use the tls-proxy maximum-sessions max_sess command to increase the limit. Alternatively, you can use the tls-proxy proxy_name and tls-proxy maximum-sessions max_sess commands, and then reboot for the commands to take effect.
446003
Error Message %ASA-4-446003: Denied TLS Proxy session from src_int:src_ip/src_port to dst_int:dst_ip/dst_port, UC-IME license is disabled. Explanation The UC-IME license is either on or off. Once enabled, UC-IME can use any number of
available TLS sessions, according to the ASA limit and the K8 export limit.

src_intThe source interface name (inside or outside) src_ipThe source IP address src_portThe source port dst_intThe destination interface name (inside or outside) dst_ipThe destination IP address dst_portThe destination port
Recommended Action Check to see if UC-IME is disabled. If so, activate it.
1-272
Chapter 1
447001
Error Message %ASA-4-447001: ASP DP to CP queue_name was full. Queue length length, limit limit Explanation This message indicates a particular data path (DP) to control point (CP) event queue is
full, and one or more multiple enqueue actions have failed. If the event contains a packet block, such as for CP application inspection, the packet will be dropped by the DP, and a counter from the show asp drop command will increment. If the event is for punt to CP, a typical counter is the Punt no memory ASP-drop counter.

queueThe name of the DP-CP event queue. lengthThe current number of events on the queue. limitThe maximum number of events that are allowed on the queue.
Recommended Action The queue-full condition reflects the fact that the load on the CP has exceeded
the CP processing ability, which may or may not be a temporary condition. You should consider reducing the feature load on the CP if this message appears repeatedly. Use the show asp event dp-cp command to identify the features that contribute the most load on the event queue.
448001
Error Message %ASA-4-448001: Denied SRTP crypto session setup on flow from src_int:src_ip/src_port to dst_int:dst_ip/dst_port, licensed K8 SRTP crypto session of limit exceeded Explanation For a K8 platform, the limit of 250 SRTP crypto sessions is enforced. Each pair of SRTP
encrypt or decrypt sessions is counted as one SRTP crypto session. A call is counted toward this limit only when encryption or decryption is required for a medium, which means that if the pass-through is set for the call, even if both legs use SRTP, they are not counted toward this limit.

src_intThe source interface name (inside or outside) src_ipThe source IP address src_portThe source port dst_intThe destination interface name (inside or outside) dst_ipThe destination IP address dst_portThe destination port limitThe K8 limit of SRTP crypto sessions (250)
Note
The K8 license limit applies to both UC and UC-IME calls.

Recommended Action None required. You can set up new SRTP crypto sessions only when existing
SRTP crypto sessions have been released.
1-273
Syslog Messages
450001
Error Message ASA-4-450001: Deny traffic for protocol protocol_id src interface_name:IP_address/port dst interface_name:IP_address/port, licensed host limit of num exceeded. Explanation The licensed host limit was exceeded. This message applies to the ASA 5505 ASA only.
protocol_idThe protocol ID number interface_nameThe interface associated with the sender or receiver of the packet IP_addressThe IP address of the sender/receiver of the packet portThe port number of the packet transmitted numThe maximum host limit value

500001
Error Message %ASA-5-500001: ActiveX content modified src IP_address dest IP_address on interface interface_name. Explanation You have turned on the activex option using the filter command, and the ASA detected an ActiveX object. The activex option allows the ASA to filter out ActiveX contents by modifying it so that it no longer is tagged as an HTML object. Recommended Action None required.
500002
Error Message %ASA-5-500002: Java content modified src IP_address dest IP_address on interface interface_name. Explanation You have turned on the java option using the filter command, and the ASA detected an
Java applet. The java option allows the ASA to filter out Java contents by modifying it so that it no longer is tagged as an HTML object.
1-274
Chapter 1
500003
Error Message %ASA-5-500003: Bad TCP hdr length (hdrlen=bytes, pktlen=bytes) from source_address/source_port to dest_address/dest_port, flags: tcp_flags, on interface interface_name Explanation A header length in TCP was incorrect. Some operating systems do not handle TCP
resets (RSTs) correctly when responding to a connection request to a disabled socket. If a client tries to connect to an FTP server outside the ASA and the FTP server is not listening, then it sends an RST. Some operating systems send incorrect TCP header lengths, which causes this problem. UDP uses ICMP port unreachable messages. The TCP header length may indicate that it is larger than the packet length, which results in a negative number of bytes being transferred. A negative number appears by a message as an unsigned number, which makes it appear much larger than it would be normally; for example, it may show 4 GB transferred in one second. This message should occur infrequently.
500004
Error Message %ASA-4-500004: Invalid transport field for protocol=protocol, from source_address/source_port to dest_address/dest_port Explanation An invalid transport number was used, in which the source or destination port number
for a protocol is zero. The protocol value is 6 for TCP and 17 for UDP.
Recommended Action If these messages persist, contact the administrator of the peer.
500005
Error Message %ASA-3-500005: connection terminated for protocol from in_ifc_name:src_adddress/src_port to out_ifc_name:dest_address/dest_port due to invalid combination of inspections on same flow. Inspect inspect_name is not compatible with filter filter_name. Explanation A connection matched with single or multiple inspection and/or single or multiple filter
features that are not allowed to be applied to the same connection.

protocolThe protocol that the connection was using in_ifc_nameThe input interface name src_addressThe source IP address of the connection src_portThe source port of the connection out_ifc_nameThe output interface name dest_addressThe destination IP address of the connection dest_portThe destination port of the packet
1-275
Syslog Messages
inspect_nameThe inspect or filter feature name filter_nameThe filter feature name
Recommended Action Review the class-map, policy-map, service-policy, and/or filter command
configurations that are causing the referenced inspection and/or filter features that are matched for the connection. The rules for inspection and filter feature combinations for a connection are as follows:
The inspect http [http-policy-map] and/or filter url and/or filter java and/or filter activex
commands are valid.

The inspect ftp [ftp-policy-map] and/or filter ftp commands are valid. The filter https command with any other inspect command or filter command is not valid.
Besides these listed combinations, any other inspection and/or filter feature combinations are not valid.
501101
Error Message %ASA-5-501101: User transitioning priv level Explanation The privilege level of a command was changed. Recommended Action None required.
502101
Error Message %ASA-5-502101: New user added to local dbase: Uname: user Priv: privilege_level Encpass: string Explanation A new username record was created, which included the username, privilege level, and
encrypted password.
502102
Error Message %ASA-5-502102: User deleted from local dbase: Uname: user Priv: privilege_level Encpass: string Explanation A username record was deleted, which included the username, privilege level, and encrypted password. Recommended Action None required.
1-276
Chapter 1
502103
Error Message %ASA-5-502103: User priv level changed: Uname: user From: privilege_level To: privilege_level Explanation The privilege level of a user changed. Recommended Action None required.
502111
Error Message %ASA-5-502111: New group policy added: name: policy_name Type: policy_type Explanation A group policy was configured using the group-policy CLI command.
policy_nameThe name of the group policy policy_typeEither internal or external
502112
Error Message %ASA-5-502112: Group policy deleted: name: policy_name Type: policy_type Explanation A group policy has been removed using the group-policy CLI command.
policy_nameThe name of the group policy policy_typeEither internal or external
503001
Error Message %ASA-5-503001: Process number, Nbr IP_address on interface_name from string to string, reason Explanation An OSPFv2 neighbor has changed its state. The message describes the change and the
reason for it. This message appears only if the log-adjacency-changes command is configured for the OSPF process.
Recommended Action Copy the message exactly as it appears, and report it to the Cisco TAC.
1-277
Syslog Messages
503101
Error Message %ASA-5-503101: Process d, Nbr i on s from s to s, s Explanation An OSPFv3 neighbor has changed its state. The message describes the change and the
reason for it. This message appears only if the log-adjacency-changes command is configured for the OSPF process.
504001
Error Message %ASA-5-504001: Security context context_name was added to the system Explanation A security context was successfully added to the ASA. Recommended Action None required.
504002
Error Message %ASA-5-504002: Security context context_name was removed from the system Explanation A security context was successfully removed from the ASA. Recommended Action None required.
505001
Error Message %ASA-5-505001: Module string one is shutting down. Please wait... Explanation A module is being shut down. Recommended Action None required.
505002
Error Message %ASA-5-505002: Module ips is reloading. Please wait... Explanation An IPS module is being reloaded. Recommended Action None required.
1-278
Chapter 1
505003
Error Message %ASA-5-505003: Module string one is resetting. Please wait... Explanation A module is being reset. Recommended Action None required.
505004
Error Message %ASA-5-505004: Module string one shutdown is complete. Explanation A module has been shut down. Recommended Action None required.
505005
Error Message %ASA-5-505005: Module ips is initializing control communication. Please wait... Explanation An IPS module has been detected, and the ASA is initializing control channel communication with it. Recommended Action None required.
505006
Error Message %ASA-5-505006: Module string one is Up. Explanation A module has completed control channel initialization and is in the UP state. Recommended Action None required.
1-279
Syslog Messages
505007
Error Message %ASA-5-505007: Module module_id is recovering. Please wait...
Error Message %ASA-5-505007: Module prod_id in slot slot_num is recovering. Please wait... Explanation A software module is being recovered with the sw-module module service-module-name recover boot command, or a hardware module is being recovered with the hw-module module slotnum recover boot command.
module_idThe name of the software services module. prod_idThe product ID string. slot_numThe slot in which the hardware services module is installed. Slot 0 indicates the system main board, and slot 1 indicates the module installed in the expansion slot.
505008
Error Message %ASA-5-505008: Module module_id software is being updated to newver (currently ver)
Error Message %ASA-5-505008: Module module_id in slot slot_num software is being updated to newver (currently ver) Explanation The services module software is being upgraded. The update is proceeding normally. module_idThe name of the software services module
slot_numThe slot number that contains the hardware services module newverThe new version number of software that was not successfully written to the module (for example, 1.0(1)0) verThe current version number of the software on the module (for example, 1.0(1)0)
505009
Error Message %ASA-5-505009: Module string one software was updated to newver Explanation The 4GE SSM module software was successfully upgraded. string oneThe text string that specifies the module
newverThe new version number of software that was not successfully written to the module (for example, 1.0(1)0)
1-280
Chapter 1
verThe current version number of the software on the module (for example, 1.0(1)0)
505010
Error Message %ASA-5-505010: Module in slot slot removed. Explanation An SSM was removed from the ASA chassis.
slotThe slot from which the SSM was removed
505011
Error Message %ASA-1-505011: Module ips, data channel communication is UP. Explanation The data channel communication recovered from a DOWN state. Recommended Action None required.
505012
Error Message %ASA-5-505012: Module module_id, application stopped application, version version
Error Message %ASA-5-505012: Module prod_id in slot slot_num, application stopped application, version version Explanation An application was stopped or removed from a services module. This may occur when
the services module upgraded an application or when an application on the services module was stopped or uninstalled.

module_idThe name of the software services module prod_idThe product ID string for the device installed in the hardwre services module slot_numThe slot in which the application was stopped applicationThe name of the application stopped versionThe application version stopped
Recommended Action If an upgrade was not occurring on the 4GE SSM or the application was not intentionally stopped or uninstalled, review the logs from the 4GE SSM to determine why the application stopped.
1-281
Syslog Messages
505013
Error Message %ASA-5-505013: Module module_id application changed from: application version version to: newapplication version newversion.
Error Message %ASA-5-505013: Module prod_id in slot slot_nunm application changed from: application version version to: newapplication version newversion. Explanation An application version changed, such as after an upgrade. A software update for the application on the services module is complete.
module_idThe name of the software services module applicationThe name of the application that was upgraded versionThe application version that was upgraded prod_idThe product ID string for the device installed in the hardware services module slot_numThe slot in which the application was upgraded applicationThe name of the application that was upgraded versionThe application version that was upgraded newapplicationThe new application name newversionThe new application version
Recommended Action Verify that the upgrade was expected and that the new version is correct.
505014
Error Message %ASA-1-505014: Module module_id, application down name, version version reason
Error Message %ASA-1-505014: Module prod_id in slot slot_num, application down name, version version reason Explanation The application running on the module is disabled.
module_idThe name of the software services module prod_idThe product ID string for the device installed in the hardware services module slot_numThe slot in which the application was disabled. Slot 0 indicates the system main board, and slot 1 indicates the module installed in the expansion slot. nameApplication name (string) applicationThe name of the application that was upgraded versionThe application version (string) reasonFailure reason (string)
1-282
Chapter 1
505015
Error Message %ASA-1-505015: Module module_id, application up application, version version
Error Message %ASA-1-505015: Module prod_id in slot slot_num, application up application, version version Explanation The application running on the SSM in slot slot_num is up and running.
module_idThe name of the software services module prod_idThe product ID string for the device installed in the hardware services module slot_numThe slot in which the application is running. Slot 0 indicates the system main board, and slot 1 indicates the module installed in the expansion slot. applicationThe application name (string) versionThe application version (string)
505016
Error Message %ASA-3-505016: Module module_id application changed from: name version version state state to: name version state state.
Error Message %ASA-3-505016: Module prod_id in slot slot_num application changed from: name version version state state to: name version state state. Explanation The application version or a name change was detected.
module_idThe name of the software services module prod_idThe product ID string for the device installed in the hardware services module slot_numThe slot in which the application changed. Slot 0 indicates the system main board, and slot 1 indicates the module installed in the expansion slot. nameApplication name (string) versionThe application version (string) stateApplication state (string) applicationThe name of the application that changed
Recommended Action Verify that the change was expected and that the new version is correct.
1-283
Syslog Messages
506001
Error Message %ASA-5-506001: event_source_string event_string Explanation The status of a file system has changed. The event and the source of the event that
caused a file system to become available or unavailable appear. Examples of sources and events that can cause a file system status change are as follows:

External CompactFlash removed External CompactFlash inserted External CompactFlash unknown event
507001
Error Message %ASA-5-507001: Terminating TCP-Proxy connection from interface_inside:source_address/source_port to interface_outside:dest_address/dest_port - reassembly limit of limit bytes exceeded Explanation The assembly buffer limit was exceeded during TCP segment reassembly.
source_address/source_portThe source IP address and the source port of the packet initiating the connection dest_address/dest_portThe destination IP address and the destination port of the packet initiating the connection interface_insideThe name of the interface on which the packet which initiated the connection arrives interface_outsideThe name of the interface on which the packet which initiated the connection exits limitThe configured embryonic connection limit for the traffic class
507002
Error Message %ASA-4-507002: Data copy in proxy-mode exceeded the buffer limit Explanation An operational error occurred during processing of a fragmented TCP message. Recommended Action None required.
1-284
Chapter 1
507003
Error Message %ASA-3-507003: The flow of type protocol from the originating interface: src_ip/src_port to dest_if:dest_ip/dest_port terminated by inspection engine, reasonExplanation The TCP proxy or session API terminated a connection for various reasons, which are
provided in the message.

protocolThe protocol for the flow src_ipThe source IP address for the flow src_portThe name of the source port for the flow dest_ifThe destination interface for the flow dest_ipThe destination IP address for the flow dest_portThe destination port for the flow reasonThe description of why the flow is being terminated by the inspection engine. Valid reasons include: - Failed to create flow - Failed to initialize session API - Filter rules installed/matched are incompatible - Failed to consolidate new buffer data with original - Reset unconditionally - Reset based on service reset inbound configuration - Disconnected, dropped packet - Packet length changed - Reset reflected back to sender - Proxy inspector reset unconditionally - Proxy inspector drop reset - Proxy inspector received data after FIN - Proxy inspector disconnected, dropped packet - Inspector reset unconditionally - Inspector drop reset - Inspector received data after FIN - Inspector disconnected, dropped packet - Could not buffer unprocessed data - Session API proxy forward failed - Conversion of inspect data to session data failed - SSL channel for TLS proxy is closed
1-285
Syslog Messages
508001
Error Message %ASA-5-508001: DCERPC message_type non-standard version_type version version_number from src_if:src_ip/src_port to dest_if:dest_ip/dest_port, terminating connection. Explanation During DCERPC inspection, a message header included a nonstandard major or minor
version.

message_typeThe DCERPC message type version_typeThe version type, which can be major or minor version_numberThe nonstandard version in the message header
Recommended Action If this is a valid version, and the problem persists, contact the Cisco TAC.
508002
Error Message %ASA-5-508002: DCERPC response has low endpoint port port_number from src_if:src_ip/src_port to dest_if:dest_ip/dest_port, terminating connection. Explanation During DCERPC inspection, a response message included an endpoint port number less
than 1024 (in the range of well-known server ports).

509001
Error Message %ASA-5-509001: Connection attempt from src_intf:src_ip/src_port [([idfw_user | FQDN_string], sg_info)] to dst_intf:dst_ip/dst_port [([idfw_user | FQDN_string], sg_info)] was prevented by "no forward" command. Explanation The no forward interface command was entered to block traffic from the source
interface to the destination interface given in the message. This command is required on low-end platforms to allow the creation of interfaces beyond the licensed limit.

src_intfThe name of the source interface to which the no forward interface command restriction applies dst_intfThe name of the destination interface to which the no forward interface command restriction applies sg_infoThe security group name or tag for the specified IP address
Recommended Action Upgrade the license to remove the requirement of this command on low-end platforms, then remove the command from the configuration.
1-286
Chapter 1
520001
Error Message %ASA-3-520001: error_string
Explanation A malloc failure occurred in ID Manager. The errror string can be either of the
following:

Malloc failureid_reserve Malloc failureid_get
520002
Error Message %ASA-3-520002: bad new ID table size
Explanation A bad new table request to the ID Manager occurred. Recommended Action Contact the Cisco TAC.
520003
Error Message %ASA-3-520003: bad id in error_string (id: 0xid_num) Explanation An ID Manager error occurred. The error string may be any of the following:
id_create_new_table (no more entries allowed) id_destroy_table (bad table ID) id_reserve id_reserve (bad ID) id_reserve: ID out of range id_reserve (unassigned table ID) id_get (bad table ID) id_get (unassigned table ID) id_get (out of IDs!) id_to_ptr id_to_ptr (bad ID) id_to_ptr (bad table ID) id_get_next_id_ptr (bad table ID) id_delete id_delete (bad ID)
1-287
Syslog Messages
id_delete (bad table key)
520004
Error Message %ASA-3-520004: error_string Explanation An id_get was attempted at the interrupt level. Recommended Action Contact the Cisco TAC.
520005
Error Message %ASA-3-520005: error_string Explanation An internal error occurred with the ID Manager. Recommended Action Contact the Cisco TAC.
520010
Error Message %ASA-3-520010: Bad queue elem qelem_ptr: flink flink_ptr, blink blink_ptr, flink-blink flink_blink_ptr, blink-flink blink_flink_ptr Explanation An internal software error occurred, which can be any of the following:
qelem_ptrA pointer to the queue data structure flink_ptrA pointer to the forward element of the queue data structure blink_ptrA pointer to the backward element of the queue data structure flink_blink_ptrA pointer to the forward elements backward pointer of the queue data structure blink_flink_ptrA pointer to the backward elements forward pointer of the queue data structure
520011
Error Message %ASA-3-520011: Null queue elem Explanation An internal software error occurred. Recommended Action Contact the Cisco TAC.
1-288
Chapter 1
520013
Error Message %ASA-3-520013: Regular expression access check with bad list acl_ID Explanation A pointer to an access list is invalid. Recommended Action The event that caused this message to be issued should not have occurred. It can mean that one or more data structures have been overwritten. If this message recurs, and you decide to report it to your TAC representative, you should copy the text of the message exactly as it appears and include the associated stack trace. Because access list corruption may have occurred, a TAC representative should verify that access lists are functioning correctly.
520020
Error Message %ASA-3-520020: No memory available Explanation The system is out of memory. Recommended Action Try one of the following actions to correct the problem:
Reduce the number of routes accepted by this router. Upgrade hardware. Use a smaller subset image on run-from-RAM platforms.
520021
Error Message %ASA-3-520021: Error deleting trie entry, error_message Explanation A software programming error occurred. The error message can be any of the following:
Inconsistent annotation Couldn't find our annotation Couldn't find deletion target
Recommended Action Copy the error message exactly as it appears, and report it to Cisco TAC.
520022
Error Message %ASA-3-520022: Error adding mask entry, error_message Explanation A software or hardware error occurred. The error message can be any of the following:
Mask already in tree Mask for route not entered
1-289
Syslog Messages
Non-unique normal route, mask not entered
Recommended Action Copy the error message exactly as it appears, and report it to Cisco TAC.
520023
Error Message %ASA-3-520023: Invalid pointer to head of tree, 0x radix_node_ptr Explanation A software programming error occurred. Recommended Action Copy the error message exactly as it appears, and report it to Cisco TAC.
520024
Error Message %ASA-3-520024: Orphaned mask #radix_mask_ptr, refcount= radix_mask_ptrs ref count at # radix_node_address, next=# radix_node_next Explanation A software error occurred. Recommended Action Copy the error message exactly as it appears, and report it to Cisco TAC.
520025
Error Message %ASA-3-520025: No memory for radix initialization: error_msg Explanation The system ran out of memory during initialization. This should only occur if an image is too large for the existing dynamic memory. The error message can be either of the following:
Initializing leaf nodes Mask housekeeping
Recommended Action Use a smaller subset image or upgrade hardware.
1-290
Chapter 1

602101
Error Message %ASA-6-602101: PMTU-D packet number bytes greater than effective mtu number dest_addr=dest_address, src_addr=source_address, prot=protocol Explanation The ASA sent an ICMP destination unreachable message and fragmentation is needed,
but the dont-fragment bit has been set.

Recommended Action Make sure that the data is sent correctly.
602103
Error Message %ASA-6-602103: IPSEC: Received an ICMP Destination Unreachable from src_addr with suggested PMTU of rcvd_mtu; PMTU updated for SA with peer peer_addr, SPI spi, tunnel name username, old PMTU old_mtu, new PMTU new_mtu. Explanation The MTU of an SA was changed. When a packet is received for an IPsec tunnel, the
corresponding SA is located and the MTU is updated based on the MTU suggested in the ICMP packet. If the suggested MTU is greater than 0 but less than 256, then the new MTU is set to 256. If the suggested MTU is 0, the old MTU is reduced by 256 or it is set to 256whichever value is greater. If the suggested MTU is greater than 256, then the new MTU is set to the suggested value.

src_addrIP address of the PMTU sender rcvd_mtuSuggested MTU received in the PMTU message peer_addrIP address of the IPsec peer spiIPsec Security Parameter Index usernameUsername associated with the IPsec tunnel old_mtuPrevious MTU associated with the IPsec tunnel new_mtuNew MTU associated with the IPsec tunnel
1-291
Syslog Messages
602104
Error Message %ASA-6-602104: IPSEC: Received an ICMP Destination Unreachable from src_addr, PMTU is unchanged because suggested PMTU of rcvd_mtu is equal to or greater than the current PMTU of curr_mtu, for SA with peer peer_addr, SPI spi, tunnel name username. Explanation An ICMP message was received indicating that a packet sent over an IPsec tunnel
exceeded the path MTU, and the suggested MTU was greater than or equal to the current MTU. Because the MTU value is already correct, no MTU adjustment is made. This may happen when multiple PMTU messages are received from different intermediate stations, and the MTU is adjusted before the current PMTU message is processed.

src_addrIP address of the PMTU sender rcvd_mtuSuggested MTU received in the PMTU message curr_mtuCurrent MTU associated with the IPsec tunnel peer_addrIP address of the IPsec peer spiIPsec Security Parameter Index usernameUsername associated with the IPsec tunnel
602303
Error Message %ASA-6-602303: IPSEC: An direction tunnel_type SA (SPI=spi) between local_IP and remote_IP (username) has been created. Explanation A new SA was created.
directionSA direction (inbound or outbound) tunnel_typeSA type (remote access or L2L) spiIPsec Security Parameter Index local_IPIP address of the tunnel local endpoint remote_IPIP address of the tunnel remote endpoint usernameUsername associated with the IPsec tunnel
1-292
Chapter 1
602304
Error Message %ASA-6-602304: IPSEC: An direction tunnel_type SA (SPI=spi) between local_IP and remote_IP (username) has been deleted. Explanation An SA was deleted.
602305
Error Message %ASA-3-602305: IPSEC: SA creation error, source source address, destination destination address, reason error string Explanation An error has occurred while creating an IPsec security association. Recommended Action This is typically a transient error condition. If this message occurs consistently, contact the Cisco TAC.
603101
Error Message %ASA-6-603101: PPTP received out of seq or duplicate pkt, tnl_id=number, sess_id=number, seq=number. Explanation The ASA received a PPTP packet that was out of sequence or duplicated. Recommended Action If the packet count is high, contact the peer administrator to check the client
PPTP configuration.
603102
Error Message %ASA-6-603102: PPP virtual interface interface_name - user: user aaa authentication started. Explanation The ASA sent an authentication request to the AAA server. Recommended Action None required.
1-293
Syslog Messages
603103
Error Message %ASA-6-603103: PPP virtual interface interface_name - user: user aaa authentication status Explanation The ASA received an authentication response from the AAA server. Recommended Action None required.
603104
Error Message %ASA-6-603104: PPTP Tunnel created, tunnel_id is number, remote_peer_ip is remote_address, ppp_virtual_interface_id is number, client_dynamic_ip is IP_address, username is user, MPPE_key_strength is string Explanation A PPTP tunnel was created. Recommended Action None required.
603105
Error Message %ASA-6-603105: PPTP Tunnel deleted, tunnel_id = number, remote_peer_ip= remote_address Explanation A PPTP tunnel was deleted. Recommended Action None required.
603106
Error Message %ASA-6-603106: L2TP Tunnel created, tunnel_id is number, remote_peer_ip is remote_address, ppp_virtual_interface_id is number, client_dynamic_ip is IP_address, username is user Explanation An L2TP tunnel was created. Recommended Action None required.
1-294
Chapter 1
603107
Error Message %ASA-6-603107: L2TP Tunnel deleted, tunnel_id = number, remote_peer_ip = remote_address Explanation An L2TP tunnel was deleted. Recommended Action None required.
603108
Error Message %ASA-6-603108: Built PPTP Tunnel at interface_name, tunnel-id = number, remote-peer = IP_address, virtual-interface = number, client-dynamic-ip = IP_address, username = user, MPPE-key-strength = number Explanation A new PPPoE tunnel was created. Recommended Action None required.
603109
Error Message %ASA-6-603109: Teardown PPPOE Tunnel at interface_name, tunnel-id = number, remote-peer = IP_address Explanation A new PPPoE tunnel was deleted. Recommended Action None required.
603110
Error Message %ASA-4-603110: Failed to establish L2TP session, tunnel_id = tunnel_id, remote_peer_ip = peer_ip, user = username. Multiple sessions per tunnel are not supported Explanation An attempt to establish a second session was detected and denied. Cisco does not
support multiple L2TP sessions per tunnel.

tunnel_idThe L2TP tunnel ID peer_ipThe peer IP address usernameThe name of the authenticated user
1-295
Syslog Messages
604101
Error Message %ASA-6-604101: DHCP client interface interface_name: Allocated ip = IP_address, mask = netmask, gw = gateway_address Explanation The ASA DHCP client successfully obtained an IP address from a DHCP server. The dhcpc command statement allows the ASA to obtain an IP address and network mask for a network interface from a DHCP server, as well as a default route. The default route statement uses the gateway address as the address of the default router. Recommended Action None required.
604102
Error Message %ASA-6-604102: DHCP client interface interface_name: address released Explanation The ASA DHCP client released an allocated IP address back to the DHCP server. Recommended Action None required.
604103
Error Message %ASA-6-604103: DHCP daemon interface interface_name: address granted MAC_address (IP_address) Explanation The ASA DHCP server granted an IP address to an external client. Recommended Action None required.
604104
Error Message %ASA-6-604104: DHCP daemon interface interface_name: address released build_number (IP_address) Explanation An external client released an IP address back to the ASA DHCP server. Recommended Action None required.
1-296
Chapter 1
604105
Error Message %ASA-4-604105: DHCPD: Unable to send DHCP reply to client hardware_address on interface interface_name. Reply exceeds options field size (options_field_size) by number_of_octets octets. Explanation An administrator can configure the DHCP options to return to the DHCP client. Depending on the options that the DHCP client requests, the DHCP options for the offer could exceed the message length limits. A DHCP offer cannot be sent, because it will not fit within the message limits.
hardware_addressThe hardware address of the requesting client. interface_nameThe interface to which server messages are being sent and received options_field_sizeThe maximum options field length. The default is 312 octets, which includes 4 octets to terminate. number_of_octetsThe number of exceeded octets.
Recommended Action Reduce the size or number of configured DHCP options.
605004
Error Message %ASA-6-605004: Login denied from source-address/source-port to interface:destination/service for user username
The following form of the message appears when the user attempts to log in to the console:
Login denied from serial to console for user username
Explanation An incorrect login attempt or a failed login to the ASA occurred. For all logins, three
attempts are allowed per session, and the session is terminated after three incorrect attempts. For SSH and Telnet logins, this message is generated after the third failed attempt or if the TCP session is terminated after one or more failed attempts. For other types of management sessions, this message is generated after every failed attempt.

source-addressSource address of the login attempt source-portSource port of the login attempt interfaceDestination management interface destinationDestination IP address serviceDestination service username Destination management interface
Recommended Action If this message appears infrequently, no action is required. If this message
appears frequently, it may indicate an attack. Communicate with the user to verify the username and password.
1-297
Syslog Messages
605005
Error Message %ASA-6-605005: Login permitted from source-address/source-port to interface:destination/service for user username
The following form of the message appears when the user logs in to the console:
Login permitted from serial to console for user username
Explanation A user was authenticated successfully, and a management session started.
source-addressSource address of the login attempt source-portSource port of the login attempt interfaceDestination management interface destinationDestination IP address serviceDestination service usernameDestination management interface
606001
Error Message %ASA-6-606001: ASDM session number number from IP_address started Explanation An administrator has been authenticated successfully, and an ASDM session started. Recommended Action None required.
606002
Error Message %ASA-6-606002: ASDM session number number from IP_address ended Explanation An ASDM session ended. Recommended Action None required.
1-298
Chapter 1
606003
Error Message %ASA-6-606003: ASDM logging session number id from IP_address started id session ID assigned Explanation An ASDM logging connection was started by a remote management client.
IP_addressIP address of the remote management client
606004
Error Message %ASA-6-606004: ASDM logging session number id from IP_address ended Explanation An ASDM logging connection was terminated.
idSession ID assigned IP_addressIP address of remote management client
607001
Error Message %ASA-6-607001: Pre-allocate SIP connection_type secondary channel for interface_name:IP_address/port to interface_name:IP_address from string message Explanation The fixup sip command preallocated a SIP connection after inspecting a SIP message.
The connection_type is one of the following strings:

SIGNALLING UDP SIGNALLING TCP SUBSCRIBE UDP SUBSCRIBE TCP Via UDP Route RTP RTCP
1-299
Syslog Messages
607002
Error Message %ASA-4-607002: action_class: action SIP req_resp req_resp_info from src_ifc:sip/sport to dest_ifc:dip/dport; further_info Explanation A SIP classification was performed on a SIP message, and the specified criteria were
satisfied. As a result, the configured action occurs.

action_classThe class of the action: SIP Classification for SIP match commands or SIP Parameter for parameter commands actionThe action taken: Dropped, Dropped connection for, Reset connection for, or Masked header flags for req_respRequest or Response req_resp_infoThe SIP method name if the type is Request: INVITE or CANCEL. The SIP response code if the type is Response: 100, 183, 200. src_ifcThe source interface name sipThe source IP address sportThe source port dest_ifcThe destination interface name dipThe destination IP address dportThe destination port further_infoMore information appears for SIP match and SIP parameter commands, as follows: For SIP match commands: matched Class id: class-name For example:
matched Class 1234: my_class
For SIP parameter commands: parameter-command: descriptive-message For example:

strict-header-validation: Mandatory header field Via is missing state-checking: Message CANCEL is not permitted to create a Dialog.
1-300
Chapter 1
607003
Error Message %ASA-6-607003: action_class: Received SIP req_resp req_resp_info from src_ifc:sip/sport to dest_ifc:dip/dport; further_info Explanation A SIP classification was performed on a SIP message, and the specified criteria were
satisfied. As a result, the standalone log action occurs.

action_classSIP classification for SIP match commands or SIP parameter for parameter commands req_respRequest or Response req_resp_infoThe SIP method name if the type is Request: INVITE or CANCEL. The SIP response code if the type is Response: 100, 183, 200. src_ifcThe source interface name sipThe source IP address sportThe source port dest_ifcThe destination interface name dipThe destination IP address. dportThe destination port. further_infoMore information appears for SIP match and SIP parameter commands, as follows: For SIP match commands: matched Class id: class-name For example:
matched Class 1234: my_class
For SIP parameter commands: parameter-command: descriptive-message For example:

strict-header-validation: Mandatory header field Via is missing state-checking: Message CANCEL is not permitted to create a Dialog.
608001
Error Message %ASA-6-608001: Pre-allocate Skinny connection_type secondary channel for interface_name:IP_address to interface_name:IP_address from string message Explanation The inspect skinny command preallocated a Skinny connection after inspecting a
Skinny message. The connection_type is one of the following strings:

SIGNALLING UDP SIGNALLING TCP
1-301
Syslog Messages
SUBSCRIBE UDP SUBSCRIBE TCP Via UDP Route RTP RTCP
608002
Error Message %ASA-4-608002: Dropping Skinny message for in_ifc:src_ip/src_port to out_ifc:dest_ip/dest_port, SCCPPrefix length value too small Explanation A Skinny (SSCP) message was received with an SCCP prefix length less than the
minimum length configured.

in_ifcThe input interface src_ipThe source IP address of the packet src_portThe source port of the packet out_ifcThe output interface dest_ipThe destination IP address of the packet dest_portThe destination port of the packet valueThe SCCP prefix length of the packet
Recommended Action If the SCCP message is valid, then customize the Skinny policy map to increase the minimum length value of the SSCP prefix.
608003
Error Message %ASA-4-608003: Dropping Skinny message for in_ifc:src_ip/src_port to out_ifc:dest_ip/dest_port, SCCPPrefix length value too large Explanation A Skinny (SSCP) message was received with an SCCP prefix length greater than the
maximum length configured.

1-302
Chapter 1
valueThe SCCP prefix length of the packet
Recommended Action If the SCCP message is valid, then customize the Skinny policy map to increase the maximum length value of the SCCP prefix.
608004
Error Message %ASA-4-608004: Dropping Skinny message for in_ifc:src_ip/src_port to out_ifc:dest_ip/dest_port, message id value not allowed Explanation This SCCP message ID is not allowed.
Recommended Action If the SCCP messages should be allowed, then customize the Skinny policy
map to allow them.
608005
Error Message %ASA-4-608005: Dropping Skinny message for in_ifc:src_ip/src_port to out_ifc:dest_ip/dest_port, message id value registration not complete Explanation This SCCP message ID is not allowed, because the endpoint did not complete
registration.

Recommended Action If the SCCP messages that are being dropped are valid, then customize the Skinny policy map to disable registration enforcement.
1-303
Syslog Messages
609001
Error Message %ASA-7-609001: Built local-host interface_name:IP_address Explanation A network state container was reserved for host IP_address connected to interface interface_name. Recommended Action None required.
609002
Error Message %ASA-7-609002: Teardown local-host interface_name:IP_address duration time Explanation A network state container for host IP_address connected to interface interface_name
was removed.
610001
Error Message %ASA-3-610001: NTP daemon interface interface_name: Packet denied from IP_address Explanation An NTP packet was received from a host that does not match one of the configured NTP servers. The ASA is only an NTP client; it is not a time server and does not respond to NTP requests. Recommended Action None required.
610002
Error Message %ASA-3-610002: NTP daemon interface interface_name: Authentication failed for packet from IP_address Explanation The received NTP packet failed the authentication check. Recommended Action Make sure that both the ASA and the NTP server are set to use authentication,
and the same key number and value.
1-304
Chapter 1
610101
Error Message %ASA-6-610101: Authorization failed: Cmd: command Cmdtype: command_modifier Explanation Command authorization failed for the specified command. The command_modifier is one of the following strings: cmd (this string means the command has no modifier) clear no show Explanation If the ASA encounters any other value other than the four command types listed, the
message unknown command type appears.

611101
Error Message %ASA-6-611101: User authentication succeeded: Uname: user Explanation User authentication succeeded when accessing the ASA. Recommended Action None required.
611102
Error Message %ASA-6-611102: User authentication failed: Uname: user Explanation User authentication failed when attempting to access the ASA. Recommended Action None required.
611103
Error Message %ASA-5-611103: User logged out: Uname: user Explanation The specified user logged out. Recommended Action None required.
1-305
Syslog Messages
611104
Error Message %ASA-5-611104: Serial console idle timeout exceeded Explanation The configured idle timeout for the ASA serial console was exceeded because of no user
activity.
611301
Error Message %ASA-6-611301: VPNClient: NAT configured for Client Mode with no split tunneling: NAT address: mapped_address Explanation The VPN client policy for client mode with no split tunneling was installed. Recommended Action None required.
611302
Error Message %ASA-6-611302: VPNClient: NAT exemption configured for Network Extension Mode with no split tunneling Explanation
The VPN client policy for network extension mode with no split tunneling was
installed.
611303
Error Message %ASA-6-611303: VPNClient: NAT configured for Client Mode with split tunneling: NAT address: mapped_address Split Tunnel Networks: IP_address/netmask IP_address/netmask Explanation The VPN client policy for client mode with split tunneling was installed. Recommended Action None required.
1-306
Chapter 1
611304
Error Message %ASA-6-611304: VPNClient: NAT exemption configured for Network Extension Mode with split tunneling: Split Tunnel Networks: IP_address/netmask IP_address/netmask Explanation The VPN client policy for network extension mode with split tunneling was installed. Recommended Action None required.
611305
Error Message %ASA-6-611305: VPNClient: DHCP Policy installed: Primary DNS: IP_address Secondary DNS: IP_address Primary WINS: IP_address Secondary WINS: IP_address Explanation
The VPN client policy for DHCP was installed.
611306
Error Message %ASA-6-611306: VPNClient: Perfect Forward Secrecy Policy installed Explanation
Perfect forward secrecy was configured as part of the VPN client download policy.
611307
Error Message %ASA-6-611307: VPNClient: Head end: IP_address Explanation
The VPN client is connected to the specified headend.
611308
Error Message %ASA-6-611308: VPNClient: Split DNS Policy installed: List of domains: string string Explanation A split DNS policy was installed as part of the VPN client downloaded policy. Recommended Action None required.
1-307
Syslog Messages
611309
Error Message %ASA-6-611309: VPNClient: Disconnecting from head end and uninstalling previously downloaded policy: Head End: IP_address Explanation A VPN client is disconnecting and uninstalling a previously installed policy. Recommended Action None required.
611310
Error Message %ASA-6-611310: VNPClient: XAUTH Succeeded: Peer: IP_address Explanation The VPN client Xauth succeeded with the specified headend. Recommended Action None required.
611311
Error Message %ASA-6-611311: VNPClient: XAUTH Failed: Peer: IP_address Explanation
The VPN client Xauth failed with the specified headend.
611312
Error Message %ASA-6-611312: VPNClient: Backup Server List: reason Explanation When the ASA is an Easy VPN remote device, the Easy VPN server downloaded a list of backup servers to the ASA. This list overrides any backup servers that you have configured locally. If the downloaded list is empty, then the ASA uses no backup servers. The reason is one of the following messages:
A list of backup server IP addresses Received NULL list. Deleting current backup servers
1-308
Chapter 1
611313
Error Message %ASA-3-611313: VPNClient: Backup Server List Error: reason Explanation When the ASA is an Easy VPN remote device, and the Easy VPN server downloads a backup server list to the ASA, the list includes an invalid IP address or a hostname. The ASA does not support DNS, and therefore does not support hostnames for servers, unless you manually map a name to an IP address using the name command. Recommended Action On the Easy VPN server, make sure that the server IP addresses are correct, and
configure the servers as IP addresses instead of hostnames. If you must use hostnames on the server, use the name command on the Easy VPN remote device to map the IP addresses to names.
611314
Error Message %ASA-6-611314: VPNClient: Load Balancing Cluster with Virtual IP: IP_address has redirected the to server IP_address Explanation When the ASA is an Easy VPN remote device, the master server of the load balancing
cluster redirected the ASA to connect to a particular server.

611315
Error Message %ASA-6-611315: VPNClient: Disconnecting from Load Balancing Cluster member IP_address Explanation When the ASA is an Easy VPN remote device, it disconnected from a load balancing
cluster server.
611316
Error Message %ASA-6-611316: VPNClient: Secure Unit Authentication Enabled Explanation When the ASA is an Easy VPN remote device, the downloaded VPN policy enabled
SUA.
1-309
Syslog Messages
611317
Error Message %ASA-6-611317: VPNClient: Secure Unit Authentication Disabled Explanation When the ASA is an Easy VPN remote device, the downloaded VPN policy disabled
SUA.
611318
Error Message %ASA-6-611318: VPNClient: User Authentication Enabled: Auth Server IP: IP_address Auth Server Port: port Idle Timeout: time Explanation When the ASA is an Easy VPN remote device, the downloaded VPN policy enabled IUA for users on the ASA inside network.
IP_addressThe server IP address to which the ASA sends authentication requests. portThe server port to which the ASA sends authentication requests timeThe idle timeout value for authentication credentials
611319
Error Message %ASA-6-611319: VPNClient: User Authentication Disabled Explanation When the ASA is an Easy VPN remote device, the downloaded VPN policy disabled IUA for users on the ASA inside network. Recommended Action None required.
611320
Error Message %ASA-6-611320: VPNClient: Device Pass Thru Enabled Explanation When the ASA is an Easy VPN remote device, the downloaded VPN policy enabled device pass-through. The device pass-through feature allows devices that cannot perform authentication (such as an IP phone) to be exempt from authentication when IUA is enabled. If the Easy VPN server enabled this feature, you can specify the devices that should be exempt from authentication (IUA) using the vpnclient mac-exempt command on the ASA. Recommended Action None required.
1-310
Chapter 1
611321
Error Message %ASA-6-611321: VPNClient: Device Pass Thru Disabled Explanation When the ASA is an Easy VPN remote device, the downloaded VPN policy disabled device pass-through. Recommended Action None required.
611322
Error Message %ASA-6-611322: VPNClient: Extended XAUTH conversation initiated when SUA disabled Explanation When the ASA is an Easy VPN remote device and the downloaded VPN policy disabled
SUA, the Easy VPN server uses two-factor/SecurID/cryptocard-based authentication mechansims to authenticate the ASA using XAUTH.
Recommended Action If you want the Easy VPN remote device to be authenticated using two-factor/SecureID/cryptocard-based authentication mechanisms, enable SUA on the server.
611323
Error Message %ASA-6-611323: VPNClient: Duplicate split nw entry Explanation When the ASA is an Easy VPN remote device, the downloaded VPN policy included duplicate split network entries. An entry is considered a duplicate if it matches both the network address and the network mask. Recommended Action Remove duplicate split network entries from the VPN policy on the Easy VPN
server.
612001
Error Message %ASA-5-612001: Auto Update succeeded:filename, version:number Explanation An update from an Auto Update server was successful. The filename variable is image,
ASDM file, or configuration. The version number variable is the version number of the update.
1-311
Syslog Messages
612002
Error Message %ASA-4-612002: Auto Update failed:filename, version:number, reason:reason Explanation An update from an Auto Update server failed.
filenameEither an image file, an ASDM file, or a configuration file. numberThe version number of the update. reasonThe failure reason, which may be one of the following: - Failover module failed to open stream buffer - Failover module failed to write data to stream buffer - Failover module failed to perform control operation on stream buffer - Failover module failed to open flash file - Failover module failed to write data to flash - Failover module operation timeout - Failover command link is down - Failover resource is not available - Invalid failover state on mate - Failover module encountered file transfer data corruption - Failover active state change - Failover command EXEC failed - The image cannot run on current system - Unsupported file type
Recommended Action Check the configuration of the Auto Update server. Check to see if the standby unit is in the failed state. If the Auto Update server is configured correctly, and the standby unit is not in the failed state, contact the Cisco TAC.
612003
Error Message %ASA-4-612003:Auto Update failed to contact:url, reason:reason Explanation The Auto Update daemon was unable to contact the specified URL url, which can be
the URL of the Auto Update server or one of the file server URLs returned by the Auto Update server. The reason field describes why the contact failed. Possible reasons for the failure include no response from the server, authentication failed, or a file was not found.
Recommended Action Check the configuration of the Auto Update server.
1-312
Chapter 1
613001
Error Message %ASA-6-613001: Checksum Failure in database in area string Link State Id IP_address Old Checksum number New Checksum number Explanation OSPF has detected a checksum error in the database because of memory corruption. Recommended Action Restart the OSPF process.
613002
Error Message %ASA-6-613002: interface interface_name has zero bandwidth Explanation The interface reported its bandwidth as zero. Recommended Action Copy the message exactly as it appears, and report it to the Cisco TAC.
613003
Error Message %ASA-6-613003: IP_address netmask changed from area string to area string Explanation An OSPF configuration change has caused a network range to change areas. Recommended Action Reconfigure OSPF with the correct network range.
613004
Error Message %ASA-3-613004: Internal error: memory allocation failure Explanation An internal software error occurred. Recommended Action Copy the error message exactly as it appears, and report it to Cisco TAC.
613005
Error Message %ASA-3-613005: Flagged as being an ABR without a backbone area Explanation The router was flagged as an Area Border Router (ABR) without a backbone area in the
router.
1-313
Syslog Messages
613006
Error Message %ASA-3-613006: Reached unknown state in neighbor state machine Explanation An internal software error in this router has resulted in an invalid neighbor state during database exchange. Recommended Action Copy the error message, the configuration and any details about the events leading up to this error and submit them to Cisco TAC.
613007
Error Message %ASA-3-613007: area string lsid IP_address mask netmask type number Explanation OSPF is trying to add an existing LSA to the database. Recommended Action Copy the error message, the configuration and any details about the events leading up to this error and submit them to Cisco TAC.
613008
Error Message %ASA-3-613008: if inside if_state number Explanation An internal error occurred. Recommended Action Copy the error message, the configuration and any details about the events leading up to this error and submit them to Cisco TAC.
613011
Error Message %ASA-3-613011: OSPF process number is changing router-id. Reconfigure virtual link neighbors with our new router-id Explanation An OSPF process is being reset, and it is going to select a new router ID. This action
brings down all virtual links. To make them work again, the virtual link configuration needs to be changed on all virtual link neighbors.
Recommended Action Change the virtual link configuration on all the virtual link neighbors to reflect
the new router ID.
1-314
Chapter 1
613013
Error Message %ASA-3-613013: OSPF LSID IP_address adv IP_address type number gateway IP_address metric number forwarding addr route IP_address/mask type number has no corresponding LSA Explanation OSPF found inconsistency between its database and the IP routing table. Recommended Action Copy the error message, the configuration and any details about the events leading up to this error, and submit them to Cisco TAC.
613014
Error Message %ASA-6-613014: Base topology enabled on interface string attached to MTR compatible mode area string Explanation OSPF interfaces attached to MTR-compatible OSPF areas require the base topology to
be enabled.
613015
Error Message %ASA-4-613015: Process 1 flushes LSA ID IP_address type-number adv-rtr IP_address in area mask Explanation A router is extensively re-originating or flushing the LSA reported by this error
message.
Recommended Action If this router is flushing the network LSA, it means the router received a network LSA whose LSA ID conflicts with the IP address of one of the router's interfaces and flushed the LSA out of the network. For OSPF to function correctly, the IP addresses of transit networks must be unique. Conflicting routers are the router reporting this error message and the router with the OSPF router ID reported as adv-rtr in this message. If this router is re-originating an LSA, it is highly probable that some other router is flushing this LSA out of the network. Find that router and avoid the conflict. The conflict for a Type-2 LSA may be due to a duplicate LSA ID. For a Type-5 LSA, it may be a duplicate router ID on the router reporting this error message and on the routers connected to a different area. In an unstable network, this message may also warn of extensive re-origination of the LSA for some other reason. Contact Cisco TAC to investigate this type of case.
1-315
Syslog Messages
613016
Error Message %ASA-3-613016: Area string router-LSA of length number bytes plus update overhead bytes is too large to flood. Explanation The router tried to build a router-LSA that is larger than the huge system buffer size or
the OSPF protocol imposed maximum.

Recommended Action If the reported total length (LSA size plus overhead) is larger than the huge system buffer size but less than 65535 bytes (the OSPF protocol imposed maximum), you may increase the huge system buffer size. If the reported total length is greater than 65535, you need to decrease the number of OSPF interfaces in the reported area.
613017
Error Message %ASA-4-613017: Bad LSA mask: Type number, LSID IP_address Mask mask from IP_address Explanation The router received an LSA with an invalid LSA mask because of an incorrect
configuration from the LSA originator. As a result, this route is not installed in the routing table.
Recommended Action Find the originating router of the LSA with the bad mask, then correct any misconfiguration of this LSA's network. For further debugging, call Cisco TAC for assistance.
613018
Error Message %ASA-4-613018: Maximum number of non self-generated LSA has been exceeded OSPF number - number LSAs Explanation The maximum number of non self-generated LSAs has been exceeded. Recommended Action Check whether or not a router in the network is generating a large number of LSAs as a result of a misconfiguration.
613019
Error Message %ASA-4-613019: Threshold for maximum number of non self-generated LSA has been reached "OSPF number" - number LSAs Explanation The threshold for the maximum number of non self-generated LSAs has been reached. Recommended Action Check whether or not a router in the network is generating a large number of LSAs as a result of a misconfiguration.
1-316
Chapter 1
613021
Error Message %ASA-4-613021: Packet not written to the output queue Explanation An internal error occurred. Recommended Action Copy the error message, the configuration and any details about the events leading up to this error, and submit them to Cisco TAC.
613022
Error Message %ASA-4-613022: Doubly linked list linkage is NULL Explanation An internal error occurred. Recommended Action Copy the error message, the configuration and any details about the events leading up to this error, and submit them to Cisco TAC.
613023
Error Message %ASA-4-613023: Doubly linked list prev linkage is NULL number Explanation An internal error occurred. Recommended Action Copy the error message, the configuration and any details about the events leading up to this error, and submit them to Cisco TAC.
613024
Error Message %ASA-4-613024: Unrecognized timer number in OSPF string Explanation An internal error occurred. Recommended Action Copy the error message, the configuration and any details about the events leading up to this error, and submit them to Cisco TAC.
1-317
Syslog Messages
613025
Error Message %ASA-4-613025: Invalid build flag number for LSA IP_address, type number Explanation An internal error occurred. Recommended Action Copy the error message, the configuration and any details about the events leading up to this error, and submit them to Cisco TAC.
613026
Error Message %ASA-4-613026: Can not allocate memory for area structure Explanation An internal error occurred. Recommended Action Copy the error message, the configuration and any details about the events leading up to this error, and submit them to Cisco TAC.
613027
Error Message %ASA-6-613027: OSPF process number removed from interface interface_name Explanation The OSPF process was removed from the interface because of an IP VRF. Recommended Action None.
613028
Error Message %ASA-6-613028: Unrecognized virtual interface intetface_name. Treat it as loopback stub route Explanation The virtual interface type was not recognized by OSPF, so it is treated as a loopback
interface stub route.

1-318
Chapter 1
613029
Error Message %ASA-3-613029: Router-ID IP_address is in use by ospf process number Explanation The ASA attempted to assign a router ID that is in use by another process. Recommended Action Configure another router ID for one of the processes.
613030
Error Message %ASA-4-613030: Router is currently an ASBR while having only one area which is a stub area Explanation An ASBR must be attached to an area that can carry AS external or NSSA LSAs. Recommended Action Make the area to which the router is attached into an NSSA or regular area.
613031
Error Message %ASA-4-613031: No IP address for interface inside Explanation The interface is not point-to-point and is unnumbered. Recommended Action Change the interface type or give the interface an IP address.
613032
Error Message %ASA-3-613032: Init failed for interface inside, area is being deleted. Try again. Explanation The interface initialization failed. The possible reasons include the following:
The area to which the interface is being attached is being deleted. It was not possible to create a neighbor datablock for the local router.
Recommended Action Remove the configuration command that covers the interface and then try it
again.
1-319
Syslog Messages
613033
Error Message %ASA-3-613033: Interface inside is attached to more than one area Explanation The interface is on the interface list for an area other than the one to which the interface
links.
Recommended Action Copy the error message, the configuration and any details about the events leading up to this error, and submit them to Cisco TAC.
613034
Error Message %ASA-3-613034: Neighbor IP_address not configured Explanation The configured neighbor options are not valid. Recommended Action Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface.
613035
Error Message %ASA-3-613035: Could not allocate or find neighbor IP_address Explanation An internal error occurred. Recommended Action Copy the error message exactly as it appears, and report it to Cisco TAC.
613036
Error Message %ASA-4-613036: Can not use configured neighbor: cost and database-filter options are allowed only for a point-to-multipoint network Explanation The configured neighbor was found on an NBMA network and either the cost or database-filter option was configured. These options are only allowed on point-to-multipoint type networks. Recommended Action Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface.
1-320
Chapter 1
613037
Error Message %ASA-4-613037: Can not use configured neighbor: poll and priority options are allowed only for a NBMA network Explanation The configured neighbor was found on a point-to-multipoint network and either the poll or priority option was configured. These options are only allowed on NBMA-type networks. Recommended Action Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface.
613038
Error Message %ASA-4-613038: Can not use configured neighbor: cost or database-filter option is required for point-to-multipoint broadcast network Explanation The configured neighbor was found on a point-to-multipoint broadcast network. Either the cost or database-filter option needs to be configured. Recommended Action Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface.
613039
Error Message %ASA-4-613039: Can not use configured neighbor: neighbor command is allowed only on NBMA and point-to-multipoint networks Explanation The configured neighbor was found on a network for which the network type was neither NBMA nor point-to-multipoint. Recommended Action None.
613040
Error Message %ASA-4-613040: OSPF-1 Area string: Router IP_address originating invalid type number LSA, ID IP_address, Metric number on Link ID IP_address Link Type number Explanation The router indicated in this message has originated an LSA with an invalid metric. If this is a router LSA and the link metric is zero, a risk of routing loops and traffic loss in the network exists. Recommended Action Configure a valid metric for the given LSA type and link type on the router originating on the reported LSA.
1-321
Syslog Messages
613041
Error Message %ASA-6-613041: OSPF-100 Areav string: LSA ID IP_address, Type number, Adv-rtr IP_address, LSA counter DoNotAge Explanation An internal error has corrected itself. There is no operational effect related to this error
message.
Recommended Action Check the system memory. If memory is low, then the timer wheel functionality did not initialize. Try to reenter the commands when memory is available. If there is sufficient memory, then contact the Cisco TAC and provide output from the show memory, show processes, and show tech-support ospf commands.
613042
Error Message %ASA-4-613042: OSPF process number lacks forwarding address for type 7 LSA IP_address in NSSA string - P-bit cleared Explanation There is no viable forwarding address in the NSSA area. As a result, the P-bit must be cleared and the Type 7 LSA is not translated into a Type 5 LSA by the NSSA translator. See RFC 3101. Recommended Action Configure at least one interface in the NSSA with an advertised IP address. A
loopback is preferable because an advertisement does not depend on the underlying layer 2 state.
613043
Error Message %ASA-6-613043: Explanation A negative database reference count occurred. Recommended Action Check the system memory. If memory is low, then the timer wheel functionality did not initialize. Try to reenter the commands when memory is available. If there is sufficient memory, then contact the Cisco TAC and provide output from the show memory, show processes, and show tech-support ospf commands.
613101
Error Message %ASA-6-613101: Checksum Failure in database in area s\n Link State Id i Old Checksum #x New Checksum #x\n Explanation OSPF has detected a checksum error in the database because of memory corruption. Recommended Action Restart the OSPF process.
1-322
Chapter 1
613102
Error Message %ASA-6-613102: interface s has zero bandwidth Explanation The interface reports its bandwidth as zero. Recommended Action None required.
613103
Error Message %ASA-6-613103: i m changed from area AREA_ID_STR to area AREA_ID_STR Explanation An OSPF configuration change has caused a network range to change areas. Recommended Action None required.
613104
Error Message %ASA-6-613104: Unrecognized virtual interface IF_NAME. Explanation The virtual interface type was not recognized by OSPFv3, so it is treated as a loopback interface stub route. Recommended Action None required.
614001
Error Message %ASA-6-614001: Split DNS: request patched from server: IP_address to server: IP_address Explanation Split DNS is redirecting DNS queries from the original destination server to the primary enterprise DNS server. Recommended Action None required.
614002
Error Message %ASA-6-614002: Split DNS: reply from server:IP_address reverse patched back to original server:IP_address Explanation Split DNS is redirecting DNS queries from the enterprise DNS server to the original destination server. Recommended Action None required.
1-323
Syslog Messages
615001
Error Message %ASA-6-615001: vlan number not available for firewall interface Explanation The switch removed the VLAN from the ASA. Recommended Action None required.
615002
Error Message %ASA-6-615002: vlan number available for firewall interface Explanation The switch added the VLAN to the ASA. Recommended Action None required.
616001
Error Message %ASA-6-616001:Pre-allocate MGCP data_channel connection for inside_interface:inside_address to outside_interface:outside_address/port from message_type message Explanation An MGCP data channel connection, RTP, or RTCP was preallocated. The message text also specifies which message has triggered the connection preallocation. Recommended Action None required.
617001
Error Message %ASA-6-617001: GTPv version msg_type from source_interface:source_address/source_port not accepted by source_interface:dest_address/dest_port Explanation A request was not accepted by the peer, which is usually seen with a Create PDP Context
request.
1-324
Chapter 1
617002
Error Message %ASA-6-617002: Removing v1 PDP Context with TID tid from GGSN IP_address and SGSN IP_address, Reason: reason or Removing v1 primary|secondary PDP Context with TID tid from GGSN IP_address and SGSN IP_address, Reason: reason Explanation A PDP context was removed from the database either because it expired, a Delete PDP
Context Request/Response was exchanged, or a user removed it using the CLI.

617003
Error Message %ASA-6-617003: GTP Tunnel created from source_interface:source_address/source_port to source_interface:dest_address/dest_port Explanation A GTP tunnel was created after receiving a Create PDP Context Response that accepted
the request.
617004
Error Message %ASA-6-617004: GTP connection created for response from source_interface:source_address/0 to source_interface:dest_address/dest_port Explanation The SGSN or GGSN signaling address in the Create PDP Context Request or Response,
respectively, was different from the SGSN/GGSN sending it.

617100
Error Message ASA-6-617100: Teardown num_conns connection(s) for user user_ip Explanation The connections for this user were torn down because either a RADIUS accounting stop
or RADIUS accounting start was received, which includes attributes that were configured in the policy map for a match. The attributes did not match those stored for the user entry, if the user entry exists.

num_connsThe number of connections torn down user_ipThe IP address (framed IP attribute) of the user
1-325
Syslog Messages
620001
Error Message %ASA-6-620001: Pre-allocate CTIQBE {RTP | RTCP} secondary channel for interface_name:outside_address[/outside_port] to interface_name:inside_address[/inside_port] from CTIQBE_message_name message Explanation The ASA preallocated a connection object for the specified CTIQBE media traffic. This message is rate limited to one message every 10 seconds. Recommended Action None required.
620002
Error Message %ASA-4-620002: Unsupported CTIQBE version: hex: from interface_name:IP_address/port to interface_name:IP_address/port Explanation The ASA received a CTIQBE message with an unsupported version number, and dropped the packet. This message is rate limited to one message every 10 seconds. Recommended Action If the version number captured in the log message is unreasonably large (greater than 10), the packet may be malformed, a non-CTIQBE packet, or corrupted before it arrives at the ASA. We recommend that you determine the source of the packets. If the version number is reasonably small (less than or equal to 10), then contact the Cisco TAC to see if a new ASA image that supports this CTIQBE version is available.
621001
Error Message %ASA-6-621001: Interface interface_name does not support multicast, not enabled Explanation An attempt was made to enable PIM on an interface that does not support multicast. Recommended Action If the problem persists, contact the Cisco TAC.
621002
Error Message %ASA-6-621002: Interface interface_name does not support multicast, not enabled Explanation An attempt was made to enable IGMP on an interface that does not support multicast. Recommended Action If the problem persists, contact the Cisco TAC.
1-326
Chapter 1
621003
Error Message %ASA-6-621003: The event queue size has exceeded number Explanation The number of event managers created has exceeded the expected amount. Recommended Action If the problem persists, contact the Cisco TAC.
621006
Error Message %ASA-6-621006: Mrib disconnected, (IP_address,IP_address) event cancelled Explanation A packet triggering a data-driven event was received, but the connection to the MRIB was down. The notification was cancelled. Recommended Action If the problem persists, contact the Cisco TAC.
621007
Error Message %ASA-6-621007: Bad register from interface_name:IP_address to IP_address for (IP_address, IP_address) Explanation A PIM router configured as a rendezvous point or with NAT has received a PIM register
packet from another PIM router. The data encapsulated in this packet is invalid.
Recommended Action The sending router is erroneously sending non-RFC registers. Upgrade the
sending router.
622001
Error Message %ASA-6-622001: string tracked route network mask address, distance number, table string, on interface interface-name Explanation A tracked route has been added to or removed from a routing table, which means that the state of the tracked object has changed from up or down.
stringAdding or Removing networkThe network address maskThe network mask addressThe gateway address numberThe route administrative distance stringThe routing table name
1-327
Syslog Messages
interface-nameThe interface name as specified by the nameif command
622101
Error Message %ASA-6-622101: Starting regex table compilation for match_command; table entries = regex_num entries Explanation Information on the background activities of regex compilation appear.
match_commandThe match command to which the regex table is associated regex_numThe number of regex entries to be compiled
622102
Error Message %ASA-6-622102: Completed regex table compilation for match_command; table size = num bytes Explanation Information on the background activities of the regex compilation appear.
match_commandThe match command to which the regex table is associated numThe size, in bytes, of the compiled table
634001
Error Message %ASA-6-634001: DAP: User user, Addr ipaddr, Connection connection; The following DAP records were selected for this connection: DAP Record names Explanation The DAP records selected for the connection appear.
userThe authenticated username ipaddrThe IP address of the remote client connectionThe type of client connection: - IPsecIPsec connection - AnyConnectAnyConnect connection - ClientlessWeb browser connection - Cut-Through-ProxyCut-Through-Proxy connection - L2TPL2TP client connection
1-328
Chapter 1
DAP record namesThe comma-separated list of the DAP record names

This section includes messages from 701001 to 780004. Most of the ISAKMP messages have a common set of prepended objects to help identify the tunnel. These objects precede the descriptive text of a message when available. If the object is not known at the time the message is generated, the specific heading = value combination will not be displayed. The objects will be prepended as follows: Group = groupname, Username = user, IP = IP_address,... Where the Group identifies the tunnel group, the Username is the username from the local database or AAA server, and the IP address is the public IP address of the remote access client or L2L peer.
701001
Error Message %ASA-7-701001: alloc_user() out of Tcp_user objects Explanation A AAA message that appears if the user authentication rate is too high for the module to handle new AAA requests. Recommended Action Enable Flood Defender with the floodguard enable command.
701002
Error Message %ASA-7-701002: alloc_user() out of Tcp_proxy objects Explanation A AAA message that appears if the user authentication rate is too high for the module to handle new AAA requests. Recommended Action Enable Flood Defender with the floodguard enable command.
702305
Error Message %ASA-3-702305: IPSEC: An direction tunnel_type SA (SPI=spi) between local_IP and remote_IP (username) is rekeying due to sequence number rollover. Explanation More than four billion packets have been received in the IPsec tunnel, and a new tunnel
is being negotiated.

directionSA direction (inbound or outbound) tunnel_typeSA type (remote access or L2L)
1-329
Syslog Messages
spiIPsec Security Parameter Index local_IPIP address of the tunnel local endpoint remote_IPIP address of the tunnel remote endpoint usernameUsername associated with the IPsec tunnel
Recommended Action Contact the peer administrator to compare the SA lifetime setting.
702307
Error Message %ASA-7-702307: IPSEC: An direction tunnel_type SA (SPI=spi) between local_IP and remote_IP (username) is rekeying due to data rollover. Explanation An SA data life span expired. An IPsec SA is rekeying as a result of the amount of data
transmitted with that SA. This information is useful for debugging rekeying issues.

703001
Error Message %ASA-7-703001: H.225 message received from interface_name:IP_address/port to interface_name:IP_address/port is using an unsupported version number Explanation The ASA received an H.323 packet with an unsupported version number. The ASA
might reencode the protocol version field of the packet to the highest supported version.
Recommended Action Use the version of H.323 that the ASA supports in the VoIP network.
703002
Error Message %ASA-7-703002: Received H.225 Release Complete with newConnectionNeeded for interface_name:IP_address to interface_name:IP_address/port Explanation The ASA received the specified H.225 message, and the ASA opened a new signaling connection object for the two specified H.323 endpoints. Recommended Action None required.
1-330
Chapter 1
709001, 709002
Error Message %ASA-7-709001: FO replication failed: cmd=command returned=code
Error Message %ASA-7-709002: FO unreplicable: cmd=command Explanation Failover messages that only appear during the development debugging and testing
phases.
709003
Error Message %ASA-1-709003: (Primary) Beginning configuration replication: Sending to mate. Explanation A failover message that appears when the active unit starts replicating its configuration to the standby unit. Primary can also be listed as Secondary for the secondary unit. Recommended Action None required.
709004
Error Message %ASA-1-709004: (Primary) End Configuration Replication (ACT) Explanation A failover message that appears when the active unit completes replication of its
configuration on the standby unit. Primary can also be listed as Secondary for the secondary unit.
709005
Error Message %ASA-1-709005: (Primary) Beginning configuration replication: Receiving from mate. Explanation The standby ASA received the first part of the configuration replication from the active ASA. Primary can also be listed as Secondary for the secondary unit. Recommended Action None required.
1-331
Syslog Messages
709006
Error Message %ASA-1-709006: (Primary) End Configuration Replication (STB) Explanation A failover message that appears when the standby unit completes replication of a configuration sent by the active unit. Primary can also be listed as Secondary for the secondary unit. Recommended Action None required.
709007
Error Message %ASA-2-709007: Configuration replication failed for command command Explanation A failover message that appears when the standby unit is unable to complete replication of a configuration sent by the active unit. The command that caused the failure appears at the end of the message. Recommended Action If the problem persists, contact the Cisco TAC.
710001
Error Message %ASA-7-710001: TCP access requested from source_address/source_port to interface_name:dest_address/service Explanation The first TCP packet destined to the ASA requests to establish a TCP session. This packet is the first SYN packet of the three-way handshake. This message appears when the respective (Telnet, HTTP, or SSH) has permitted the packet. However, the SYN cookie verification is not yet completed and no state is reserved. Recommended Action None required.
710002
Error Message %ASA-7-710002: {TCP|UDP} access permitted from source_address/source_port to interface_name:dest_address/service Explanation For a TCP connection, the second TCP packet destined for the ASA requested to
establish a TCP session. This packet is the final ACK of the three-way handshake. The respective (Telnet, HTTP, or SSH) has permitted the packet. Also, the SYN cookie verification was successful and the state is reserved for the TCP session. For a UDP connection, the connection was permitted. For example, the module received an SNMP request from an authorized SNMP management station, and the request has been processed. This message is rate limited to one message every 10 seconds.
1-332
Chapter 1
710003
Error Message %ASA-3-710003: {TCP|UDP} access denied by ACL from source_IP/source_port to interface_name:dest_IP/service Explanation The ASA denied an attempt to connect to the interface service. For example, the ASA received an SNMP request from an unauthorized SNMP management station. If this message appears frequently, it can indicate an attack.
For example:
%ASA-3-710003: UDP access denied by ACL from 95.1.1.14/5000 to outside:95.1.1.13/1005
Recommended Action Use the show run http, show run ssh, or show run telnet commands to verify that the ASA is configured to permit the service access from the host or network.
710004
Error Message %ASA-7-710004: TCP connection limit exceeded from Src_ip/Src_port to In_name:Dest_ip/Dest_port (current connections/connection limit = Curr_conn/Conn_lmt) Explanation The maximum number of ASA management connections for the service was exceeded. The ASA permits at most five concurrent management connections per management service. Alternatively, an error may have occurred in the to-the-box connection counter.
Src_ipThe source IP address of the packet Src_portThe source port of the packet In_ifcThe input interface Dest_ipThe destination IP address of the packet Dest_portThe destination port of the packet Curr_connThe number of current to-the-box admin connections Conn_lmtThe connection limit
Recommended Action From the console, use the kill command to release the unwanted session. If the message was generated because of an error in the to-the-box counter, run the show conn all command to display connection details.
1-333
Syslog Messages
710005
Error Message %ASA-7-710005: {TCP|UDP} request discarded from source_address/source_port to interface_name:dest_address/service Explanation The ASA does not have a UDP server that services the UDP request. Also, a TCP packet
that does not belong to any session on the ASA may have been discarded. In addition, this message appears (with the SNMP service) when the ASA receives an SNMP request with an empty payload, even if it is from an authorized host. When the service is SNMP, this message occurs a maximum of once every 10 seconds so that the log receiver is not overwhelmed.
Recommended Action In networks that use broadcasting services such as DHCP, RIP, or NetBIOS extensively, the frequency of this message can be high. If this message appears in excessive numbers, it may indicate an attack.
710006
Error Message %ASA-7-710006: protocol request discarded from source_address to interface_name:dest_address Explanation The ASA does not have an IP server that services the IP protocol request; for example,
the ASA receives IP packets that are not TCP or UDP, and the ASA cannot service the request.
Recommended Action In networks that use broadcasting services such as DHCP, RIP, or NetBIOS extensively, the frequency of this message can be high. If this message appears in excessive numbers, it may indicate an attack.
710007
Error Message %ASA-7-710007: NAT-T keepalive received from 86.1.161.1/1028 to outside:86:1.129.1/4500 Explanation The ASA received NAT-T keepalive messages. Recommended Action None required.
711001
Error Message %ASA-7-711001: debug_trace_msg Explanation You have entered the logging debug-trace command for the logging feature. When the logging debug-trace command is enabled, all debugging messages will be redirected to the message for processing. For security reasons, the message output must be encrypted or sent over a secure out-of-band network. Recommended Action None required.
1-334
Chapter 1
711002
Error Message %ASA-4-711002: Task ran for elapsed_time msecs, process = process_name, PC = PC Tracebeback = traceback Explanation A process used the CPU for more than 100 milliseconds. This message is used for
debugging CPU purposes, and can appear once every five seconds for each offending process.

PCInstruction pointer of the CPU hogging process tracebackStack trace of the CPU hogging process, which can include up to 12 addresses
711003
Error Message ASA-7-711003: Unknown/Invalid interface identifier(vpifnum) detected. Explanation An internal inconsistency that should not occur during normal operation has occurred. However, this message is not harmful if it rarely occurs. If it occurs frequently, it might be worthwhile debugging.
vpifnumThe 32-bit value corresponding to the interface
711004
Error Message %ASA-4-711004: Task ran for msec msec, Process = process_name, PC = pc, Call stack = call stack Explanation A process used the CPU for more than 100 milliseconds. This message is used for debugging CPU purposes, and can appear once every five seconds for each offending process.
msecLength of the detected CPU hog in milliseconds process_nameName of the hogging process pcInstruction pointer of the CPU hogging process call stackStack trace of the CPU hogging process, which can include up to 12 addresses
1-335
Syslog Messages
711005
Error Message %ASA-5-711005: Traceback: call_stack Explanation An internal software error that should not occur has occurred. The device can usually recover from this error, and no harmful effect to the device results.
call_stackThe EIPs of the call stack
711006
Error Message %ASA-7-711006: CPU profiling has started for n-samples samples. Reason: reason-string. Explanation CPU profiling has started.
n-samplesThe specified number of CPU profiling samples reason-stringThe possible values are: CPU utilization passed cpu-utilization% Process process-name CPU utilization passed cpu-utilization% None specified
Recommended Action Collect CPU profiling results and provide them to Cisco TAC.
713004
Error Message %ASA-3-713004: device scheduled for reboot or shutdown, IKE key acquire message on interface interface num, for Peer IP_address ignored Explanation The ASA has received an IKE packet from a remote entity trying to initiate a tunnel. Because the ASA is scheduled for a reboot or shutdown, it does not allow any more tunnels to be established. The IKE packet is ignored and dropped. Recommended Action None required.
713201
Error Message %ASA-5-713201: Duplicate Phase Phase packet detected. Action Explanation The ASA has received a duplicate of a previous Phase 1 or Phase 2 packet, and will
transmit the last message. A network performance or connectivity issue may have occurred, in which the peer is not receiving sent packets in a timely manner.
PhasePhase 1 or 2
1-336
Chapter 1
ActionRetransmitting last packet, or No last packet to transmit.
Recommended Action Verify network performance or connectivity.
713202
Error Message %ASA-6-713202: Duplicate IP_addr packet detected. Explanation The ASA has received a duplicate first packet for a tunnel that the ASA is already aware of and negotiating, which indicates that the ASA probably received a retransmission of a packet from the peer.
IP_addrThe IP address of the peer from which the duplicate first packet was received
Recommended Action None required, unless the connection attempt is failing. If this is the case, debug further and diagnose the problem.
713006
Error Message %ASA-5-713006: Failed to obtain state for message Id message_number, Peer Address: IP_address Explanation The ASA does not know about the received message ID. The message ID is used to
identify a specific IKE Phase 2 negotiation. An error condition on the ASA may have occurred, and may indicate that the two IKE peers are out-of-sync.
713008
Error Message %ASA-3-713008: Key ID in ID payload too big for pre-shared IKE tunnel Explanation A key ID value was received in the ID payload, which was longer than the maximum allowed size of a group name for this IKE session using preshared keys authentication. This is an invalid value, and the session is rejected. Note that the key ID specified would never work because a group name of that size cannot be created in the ASA. Recommended Action Make sure that the client peer (most likely an Altiga remote access client) specifies a valid group name. Notify the user to change the incorrect group name on the client. The current maximum length for a group name is 32 characters.
1-337
Syslog Messages
713009
Error Message %ASA-3-713009: OU in DN in ID payload too big for Certs IKE tunnel Explanation An OU value in the DN was received in the ID payload, which was longer than the
maximum allowed size of a group name for this IKE session using Certs authentication. This OU is skipped, and another OU or other criteria may find a matching group.
Recommended Action For the client to be able to use an OU to find a group in the ASA, the group name must be a valid length. The current maximum length of a group name is 32 characters.
713010
Error Message %ASA-5-713010: IKE area: failed to find centry for message Id message_number Explanation An attempt was made to locate a conn_entry (IKE phase 2 structure that corresponds to an IPsec SA) using the unique message ID, which failed. The internal structure was not found, which may occur if a session was terminated in a nonstandard way, but it is more likely that an internal error occurred. Recommended Action If this problem persists, investigate the peer.
713012
Error Message %ASA-3-713012: Unknown protocol (protocol). Not adding SA w/spi=SPI value Explanation An illegal or unsupported IPsec protocol has been received from the peer. Recommended Action Check the ISAKMP Phase 2 configuration on the peer(s) to make sure it is
compatible with the ASA.
713014
Error Message %ASA-3-713014: Unknown Domain of Interpretation (DOI): DOI value Explanation The ISAKMP DOI received from the peer is unsupported. Recommended Action Check the ISAKMP DOI configuration on the peer.
1-338
Chapter 1
713016
Error Message %ASA-3-713016: Unknown identification type, Phase 1 or 2, Type ID_Type Explanation The ID received from the peer is unknown. The ID can be an unfamiliar valid ID or an invalid or corrupted ID. Recommended Action Check the configuration on the headend and peer.
713017
Error Message %ASA-3-713017: Identification type not supported, Phase 1 or 2, Type ID_Type Explanation The Phase 1 or Phase 2 ID received from the peer is legal, but not supported. Recommended Action Check the configuration on the headend and peer.
713018
Error Message %ASA-3-713018: Unknown ID type during find of group name for certs, Type ID_Type Explanation Tn internal software error has occurred. Recommended Action If the problem persists, contact the Cisco TAC.
713020
Error Message %ASA-3-713020: No Group found by matching OU(s) from ID payload: OU_value Explanation Tn internal software error has occurred. Recommended Action If the problem persists, contact the Cisco TAC.
1-339
Syslog Messages
713022
Error Message %ASA-3-713022: No Group found matching peer_ID or IP_address for Pre-shared key peer IP_address Explanation No group exists in the group database with the same name as the value (key ID or IP address) specified by the peer. Recommended Action Verify the configuration on the peer.
713024
Error Message %ASA-7-713024: Group group IP ip Received local Proxy Host data in ID Payload: Address IP_address, Protocol protocol, Port port Explanation The ASA has received the Phase 2 local proxy ID payload from the remote peer. Recommended Action None required.
713025
Error Message %ASA-7-713025: Received remote Proxy Host data in ID Payload: Address IP_address, Protocol protocol, Port port Explanation The ASA has received the Phase 2 local proxy ID payload from the remote peer. Recommended Action None required.
713028
Error Message %ASA-7-713028: Received local Proxy Range data in ID Payload: Addresses IP_address - IP_address, Protocol protocol, Port port Explanation The ASA has received the Phase 2 local proxy ID payload of the remote peer, which
includes an IP address range.

1-340
Chapter 1
713029
Error Message %ASA-7-713029: Received remote Proxy Range data in ID Payload: Addresses IP_address - IP_address, Protocol protocol, Port port Explanation The ASA has received the Phase 2 local proxy ID payload of the remote peer, which
includes an IP address range.

713032
Error Message %ASA-3-713032: Received invalid local Proxy Range IP_address IP_address Explanation The local ID payload included the range ID type, and the specified low address was not
less than the high address. A configuration problem may exist.

Recommended Action Check the configuration of ISAKMP Phase 2 parameters.
713033
Error Message %ASA-3-713033: Received invalid remote Proxy Range IP_address IP_address Explanation The remote ID payload included the range ID type, and the specified low address was not less than the high address. A configuration problem may exist. Recommended Action Check the configuration of ISAKMP Phase 2 parameters.
713034
Error Message %ASA-7-713034: Received local IP Proxy Subnet data in ID Payload: Address IP_address, Mask netmask, Protocol protocol, Port port Explanation The local IP proxy subnet data has been received in the Phase 2 ID payload. Recommended Action None required.
1-341
Syslog Messages
713035
Error Message %ASA-7-713035: Group group IP ip Received remote IP Proxy Subnet data in ID Payload: Address IP_address, Mask netmask, Protocol protocol, Port port Explanation The remote IP proxy subnet data has been received in the Phase 2 ID payload. Recommended Action None required.
713039
Error Message %ASA-7-713039: Send failure: Bytes (number), Peer: IP_address Explanation An internal software error has occurred, and the ISAKMP packet cannot be transmitted. Recommended Action If the problem persists, contact the Cisco TAC.
713040
Error Message %ASA-7-713040: Could not find connection entry and can not encrypt: msgid message_number Explanation An internal software error has occurred, and a Phase 2 data structure cannot be found. Recommended Action If the problem persists, contact the Cisco TAC.
713041
Error Message %ASA-5-713041: IKE Initiator: new or rekey Phase 1 or 2, Intf interface_number, IKE Peer IP_address local Proxy Address IP_address, remote Proxy Address IP_address, Crypto map (crypto map tag) Explanation The ASA is negotiating a tunnel as the initiator. Recommended Action None required.
1-342
Chapter 1
713042
Error Message %ASA-3-713042: IKE Initiator unable to find policy: Intf interface_number, Src: source_address, Dst: dest_address Explanation The IPsec fast path processed a packet that triggered IKE, but the IKE policy lookup failed. This error may be timing related. The ACLs that triggered IKE might have been deleted before IKE processed the initiation request. This problem will most likely correct itself. Recommended Action If the condition persists, check the L2L configuration, paying special attention
to the type of ACL associated with crypto maps.
713043
Error Message %ASA-3-713043: Cookie/peer address IP_address session already in progress Explanation IKE has been triggered again while the original tunnel is in progress. Recommended Action None required.
713048
Error Message %ASA-3-713048: Error processing payload: Payload ID: id Explanation A packet has been received with a payload that cannot be processed. Recommended Action If this problem persists, a misconfiguration may exist on the peer.
713049
Error Message %ASA-5-713049: Security negotiation complete for tunnel_type type (group_name) Initiator/Responder, Inbound SPI = SPI, Outbound SPI = SPI Explanation An IPsec tunnel has been started. Recommended Action None required.
1-343
Syslog Messages
713050
Error Message %ASA-5-713050: Connection terminated for peer IP_address. Reason: termination reason Remote Proxy IP_address, Local Proxy IP_address Explanation An IPsec tunnel has been terminated. Possible termination reasons include:
IPsec SA Idle Timeout IPsec SA Max Time Exceeded Administrator Reset Administrator Reboot Administrator Shutdown Session Disconnected Session Error Terminated Peer Terminate
713052
Error Message %ASA-7-713052: User (user) authenticated. Explanation The remote access user was authenticated. Recommended Action None required.
713056
Error Message %ASA-3-713056: Tunnel rejected: SA (SA_name) not found for group (group_name)! Explanation The IPsec SA was not found. Recommended Action If this is a remote access tunnel, check the group and user configuration, and
verify that a tunnel group and group policy have been configured for the specific user group. For externally authenticated users and groups, check the returned authentication attributes.
1-344
Chapter 1
713060
Error Message %ASA-3-713060: Tunnel Rejected: User (user) not member of group (group_name), group-lock check failed. Explanation The user is configured for a different group than what was sent in the IPsec negotiation. Recommended Action If you are using the Cisco VPN client and preshared keys, make sure that the group configured on the client is the same as the group associated with the user on the ASA. If you are using digital certificates, the group is dictated either by the OU field of the certificate, or the user automatically defaults to the remote access default group.
713061
Error Message %ASA-3-713061: Tunnel rejected: Crypto Map Policy not found for Src:source_address, Dst: dest_address! Explanation The ASA was not able to find security policy information for the private networks or
hosts indicated in the message. These networks or hosts were sent by the initiator and do not match any crypto ACLs at the ASA. This is most likely a misconfiguration.
Recommended Action Check the protected network configuration in the crypto ACLs on both sides and make sure that the local net on the initiator is the remote net on the responder and vice-versa. Pay special attention to wildcard masks, and host addresses versus network addresses. Non-Cisco implementations may have the private addresses labeled as proxy addresses or red networks.
713062
Error Message %ASA-3-713062: IKE Peer address same as our interface address IP_address Explanation The IP address configured as the IKE peer is the same as the IP address configured on one of the ASA IP interfaces. Recommended Action Check the L2L and IP interface configurations.
713063
Error Message %ASA-3-713063: IKE Peer address not configured for destination IP_address Explanation The IKE peer address is not configured for an L2L tunnel. Recommended Action Check the L2L configuration.
1-345
Syslog Messages
713065
Error Message %ASA-3-713065: IKE Remote Peer did not negotiate the following: proposal attribute Explanation An internal software error has occurred. Recommended Action If the problem persists, contact the Cisco TAC.
713066
Error Message %ASA-7-713066: IKE Remote Peer configured for SA: SA_name Explanation The crypto policy settings of the peer have been configured. Recommended Action None required.
713068
Error Message %ASA-5-713068: Received non-routine Notify message: notify_type (notify_value) Explanation Notification messages that caused this event are not explicitly handled in the notify
processing code.
Recommended Action Examine the specific reason to determine the action to take. Many notification
messages indicate a configuration mismatch between the IKE peers.
713072
Error Message %ASA-3-713072: Password for user (user) too long, truncating to number characters Explanation The password of the user is too long. Recommended Action Correct password lengths on the authentication server.
1-346
Chapter 1
713073
Error Message %ASA-5-713073: Responder forcing change of Phase 1/Phase 2 rekeying duration from larger_value to smaller_value seconds Explanation Rekeying durations are always set to the lower of the values proposed by IKE peers. The
value of the initiator is the lower one.

713074
Error Message %ASA-5-713074: Responder forcing change of IPsec rekeying duration from larger_value to smaller_value Kbs Explanation Rekeying durations are always set to the lower of the values proposed by IKE peers. The
value of the initiator is the lower one.

713075
Error Message %ASA-5-713075: Overriding Initiator's IPsec rekeying duration from larger_value to smaller_value seconds Explanation Rekeying durations are always set to the lower of the values proposed by IKE peers. The value of the responder is the lower one. Recommended Action None required.
713076
Error Message %ASA-5-713076: Overriding Initiator's IPsec rekeying duration from larger_value to smaller_value Kbs Explanation Rekeying durations are always set to the lower of the values proposed by IKE peers. The value of the responder is the lower one. Recommended Action None required.
1-347
Syslog Messages
713078
Error Message %ASA-2-713078: Temp buffer for building mode config attributes exceeded: bufsize available_size, used value Explanation An internal software error has occurred while processing modecfg attributes. Recommended Action Disable any unnecessary tunnel group attributes, or shorten any text messages that are excessively long. If the problem persists, contact the Cisco TAC.
713081
Error Message %ASA-3-713081: Unsupported certificate encoding type encoding_type Explanation One of the loaded certificates is unreadable, and may be an unsupported encoding
scheme.
Recommended Action Check the configuration of digital certificates and trustpoints.
713082
Error Message %ASA-3-713082: Failed to retrieve identity certificate Explanation The identity certificate for this tunnel cannot be found. Recommended Action Check the configuration of digital certificates and trustpoints.
713083
Error Message %ASA-3-713083: Invalid certificate handle Explanation The identity certificate for this tunnel cannot be found. Recommended Action Check the configuration of digital certificates and trustpoints.
1-348
Chapter 1
713084
Error Message %ASA-3-713084: Received invalid phase 1 port value (port) in ID payload Explanation The port value received in the IKE phase 1 ID payload was incorrect. Acceptable values are 0 or 500 (ISAKMP is also known as IKE). Recommended Action Make sure that a peer conforms to the IKE standards to avoid a network problem resulting in corrupted packets.
713085
Error Message %ASA-3-713085: Received invalid phase 1 protocol (protocol) in ID payload Explanation The protocol value received in the IKE phase 1 ID payload was incorrect. Acceptable values are 0 or 17 (UDP). Recommended Action Make sure that a peer conforms to the IKE standards to avoid a network problem resulting in corrupted packets.
713086
Error Message %ASA-3-713086: Received unexpected Certificate payload Possible invalid Auth Method (Auth method (auth numerical value)) Explanation A certificate payload was received, but our internal certificate handle indicates that we
do not have an identity certificate. The certificate handle was not obtained through a normal enrollment method. One likely reason this can happen is that the authentication method is not made through RSA or DSS signatures, although the IKE SA negotiation should fail if each side is misconfigured.
Recommended Action Check the trustpoint and ISAKMP configuration settings on the ASA and its
peer.
713088
Error Message %ASA-3-713088: Set Cert filehandle failure: no IPsec SA in group group_name Explanation The tunnel group cannot be found, based on the digital certificate information. Recommended Action Verify that the tunnel group is set up correctly to handle the certificate information of the peer.
1-349
Syslog Messages
713092
Error Message %ASA-5-713092: Failure during phase 1 rekeying attempt due to collision Explanation An internal software error has occurred. This is often a benign event. Recommended Action If the problem persists, contact the Cisco TAC.
713094
Error Message %ASA-7-713094: Cert validation failure: handle invalid for Main/Aggressive Mode Initiator/Responder! Explanation An internal software error has occurred. Recommended Action You may have to reenroll the trustpoint. If the problem persists, contact the
Cisco TAC.
713098
Error Message %ASA-3-713098: Aborting: No identity cert specified in IPsec SA (SA_name)! Explanation An attempt was made to establish a certificate-based IKE session, but no identity certificate has been specified in the crypto policy. Recommended Action Specify the identity certificate or trustpoint that you want to transmit to peers.
713099
Error Message %ASA-7-713099: Tunnel Rejected: Received NONCE length number is out of range! Explanation An internal software error has occurred. Recommended Action If the problem persists, contact the Cisco TAC.
713102
Error Message %ASA-3-713102: Phase 1 ID Data length number too long - reject tunnel! Explanation IKE has received an ID payload that includes an identification data field of 2 K or larger. Recommended Action None required.
1-350
Chapter 1
713103
Error Message %ASA-7-713103: Invalid (NULL) secret key detected while computing hash Explanation An internal software error has occurred. Recommended Action If the problem persists, contact the Cisco TAC.
713104
Error Message %ASA-7-713104: Attempt to get Phase 1 ID data failed while hash computation Explanation An internal software error has occurred. Recommended Action If the problem persists, contact the Cisco TAC.
713105
Error Message %ASA-3-713105: Zero length data in ID payload received during phase 1 or 2 processing Explanation A peer sent an ID payload without including any ID data, which is invalid. Recommended Action Check the configuration of the peer.
713107
Error Message %ASA-3-713107: IP_Address request attempt failed! Explanation An internal software error has occurred. Recommended Action If the problem persists, contact the Cisco TAC.
713109
Error Message %ASA-3-713109: Unable to process the received peer certificate Explanation The ASA was unable to process the certificate received from the remote peer, which can occur if the certificate data was malformed (for example, if the public key size is larger than 4096 bits) or if the data in the certificate cannot be stored by the ASA. Recommended Action Try to reestablish the connection using a different certificate on the remote
peer.
1-351
Syslog Messages
713112
Error Message %ASA-3-713112: Failed to process CONNECTED notify (SPI SPI_value)! Explanation The ASA was unable to successfully process the notification payload that included the
CONNECTED notify type. This may occur if the IKE phase 2 structure cannot be found using the SPI to locate it, or the commit bit had not been set in the received ISAKMP header. The latter case may indicate a nonconforming IKE peer.
Recommended Action If the problem persists, check the configuration of the peer and/or disable commit bit processing.
713113
Error Message %ASA-7-713113: Deleting IKE SA with associated IPsec connection entries. IKE peer: IP_address, SA address: internal_SA_address, tunnel count: count Explanation An IKE SA is being deleted with a nonzero tunnel count, which means that either the IKE SA tunnel count has lost synchronization with the associated connection entries or the associated connection cookie fields for the entries have lost synchronization with the cookie fields of the IKE SA to which the connection entry points. If this occurs, the IKE SA and its associated data structures will not be freed, so that the entries that may point to it will not have a stale pointer. Recommended Action None required. Error recovery is built-in.
713114
Error Message %ASA-7-713114: Connection entry (conn entry internal address) points to IKE SA (SA_internal_address) for peer IP_address, but cookies don't match Explanation An internal software error has occurred. Recommended Action If the problem persists, contact the Cisco TAC.
713115
Error Message %ASA-5-713115: Client rejected NAT enabled IPsec request, falling back to standard IPsec Explanation The client rejected an attempt by the ASA to use IPsec over UDP. IPsec over UDP is used to allow multiple clients to establish simultaneous tunnels to the ASA through a NAT device. The client may have rejected the request, either because it does not support this feature or because it is configured not to use it. Recommended Action Verify the configuration on the headend and peer.
1-352
Chapter 1
713117
Error Message %ASA-7-713117: Received Invalid SPI notify (SPI SPI_Value)! Explanation The IPsec SA identified by the SPI value is no longer active on the remote peer, which might indicate that the remote peer has rebooted or been reset. Recommended Action This problem should correct itself once DPDs recognize that the peer no longer has the appropriate SAs established. If DPD is not enabled, this may require you to manually reestablish the affected tunnel.
713118
Error Message %ASA-3-713118: Detected invalid Diffie-Helmann group_descriptor group_number, in IKE area Explanation The group_descriptor field included an unsupported value. Currently we support only
groups 1, 2, 5, and 7. In the case of a centry, the group_descriptor field may also be set to 0 to indicate that perfect forward secrecy is disabled.
Recommended Action Check the peer Diffie-Hellman configuration.
713119
Error Message %ASA-5-713119: Group group IP ip PHASE 1 COMPLETED Explanation IKE Phase 1 has completed successfully. Recommended Action None required.
713120
Error Message %ASA-5-713120: PHASE 2 COMPLETED (msgid=msg_id) Explanation IKE Phase 2 has completed successfully. Recommended Action None required.
1-353
Syslog Messages
713121
Error Message %ASA-7-713121: Keep-alive type for this connection: keepalive_type Explanation The type of keepalive mechanism that is being used for this tunnel is specified. Recommended Action None required.
713122
Error Message %ASA-3-713122: Keep-alives configured keepalive_type but peer IP_address support keep-alives (type = keepalive_type) Explanation Keepalives were configured on or off for this device, but the IKE peer does or does not support keepalives. Recommended Action No action is required if this configuration is intentional. If it is not intentional,
change the keepalive configuration on both devices.
713123
Error Message %ASA-3-713123: IKE lost contact with remote peer, deleting connection (keepalive type: keepalive_type) Explanation The remote IKE peer did not respond to keepalives within the expected window of time, so the connection to the IKE peer was terminated. The message includes the keepalive mechanism used. Recommended Action None required.
713124
Error Message %ASA-3-713124: Received DPD sequence number rcv_sequence_# in DPD Action, description expected seq # Explanation The remote IKE peer sent a DPD with a sequence number that did not match the
expected sequence number. The packet is discarded. This might indicate a packet loss problem with the network.
1-354
Chapter 1
713127
Error Message %ASA-3-713127: Xauth required but selected Proposal does not support xauth, Check priorities of ike xauth proposals in ike proposal list Explanation The peer wanted to perform a XAUTH, but the ASA did not choose the XAUTH IKE
proposal.
Recommended Action Check the priorities of the IKE xauth proposals in the IKE proposal list.
713128
Error Message %ASA-6-713128: Connection attempt to VCPIP redirected to VCA peer IP_address via load balancing Explanation A connection attempt has been made to the VCPIP and has been redirected to a less loaded peer using load balancing. Recommended Action None required.
713129
Error Message %ASA-3-713129: Received unexpected Transaction Exchange payload type: payload_id Explanation An unexpected payload has been received during XAUTH or Mode Cfg, which may
indicate that the two peers are out-of-sync, that the XAUTH or Mode Cfg versions do not match, or that the remote peer is not complying with the appropriate RFCs.
Recommended Action Verify the configuration between peers.
713130
Error Message %ASA-5-713130: Received unsupported transaction mode attribute: attribute id Explanation The device received a request for a valid transaction mode attribute (XAUTH or Mode Cfg) that is currently not supported. This is generally a benign condition. Recommended Action None required.
1-355
Syslog Messages
713131
Error Message %ASA-5-713131: Received unknown transaction mode attribute: attribute_id Explanation The ASA has received a request for a transaction mode attribute (XAUTH or Mode Cfg) that is outside the range of known attributes. The attribute may be valid but only supported in later versions of configuration mode, or the peer may be sending an illegal or proprietary value. This should not cause connectivity problems, but may affect the functionality of the peer. Recommended Action None required.
713132
Error Message %ASA-3-713132: Cannot obtain an IP_address for remote peer Explanation A request for an IP address for a remote access client from the internal utility that
provides these addresses cannot be satisfied.

Recommended Action Check the configuration of IP address assignment methods.
713133
Error Message %ASA-3-713133: Mismatch: Overriding phase 2 DH Group(DH group DH group_id) with phase 1 group(DH group DH group_number Explanation The configured Phase 2 PFS Group differed from the DH group that was negotiated for
Phase 1.
713134
Error Message %ASA-3-713134: Mismatch: P1 Authentication algorithm in the crypto map entry different from negotiated algorithm for the L2L connection Explanation The configured LAN-to-LAN proposal is different from the one accepted for the
LAN-to-LAN connection. Depending on which side is the initiator, different proposals will be used.
1-356
Chapter 1
713135
Error Message %ASA-5-713135: message received, redirecting tunnel to IP_address. Explanation The tunnel is being redirected because of load balancing on the remote ASA. A
REDIRECT_CONNECTION notify packet was received.

713136
Error Message %ASA-5-713136: IKE session establishment timed out [IKE_state_name], aborting! Explanation The Reaper has detected an ASA stuck in an inactive state. The Reaper will try to
remove the inactive ASA.

713137
Error Message %ASA-5-713137: Reaper overriding refCnt [ref_count] and tunnelCnt [tunnel_count] -- deleting SA! Explanation An internal software error has occurred. Recommended Action If the problem persists, contact the Cisco TAC.
713138
Error Message %ASA-3-713138: Group group_name not found and BASE GROUP default preshared key not configured Explanation No group exists in the group database with the same name as the IP address of the peer. In Main Mode, the ASA will fall back and try to use the default preshared key configured in one of the default groups. The default preshared key is not configured. Recommended Action Verify the configuration of the preshared keys.
1-357
Syslog Messages
713139
Error Message %ASA-5-713139: group_name not found, using BASE GROUP default preshared key Explanation No tunnel group exists in the group database with the same name as the IP address of the peer. In Main Mode, the ASA will fall back and use the default preshared key configured in the default group. Recommended Action None required.
713140
Error Message %ASA-3-713140: Split Tunneling Policy requires network list but none configured Explanation The split tunneling policy is set to either split tunneling or to allow local LAN access.
A split tunneling ACL must be defined to represent the information required by the VPN client.
Recommended Action Check the configuration of the ACLs.
713141
Error Message %ASA-3-713141: Client-reported firewall does not match configured firewall: action tunnel. Received -- Vendor: vendor(id), Product product(id), Caps: capability_value. Expected -- Vendor: vendor(id), Product: product(id), Caps: capability_value Explanation The ASA installed on the client does not match the configured required ASA. This
message lists the actual and expected values, and whether the tunnel is terminated or allowed.
Recommended Action You may need to install a different personal ASA on the client or change the configuration on the ASA.
713142
Error Message %ASA-3-713142: Client did not report firewall in use, but there is a configured firewall: action tunnel. Expected -- Vendor: vendor(id), Product product(id), Caps: capability_value Explanation The client did not report an ASA in use using ModeCfg, but one is required. The event
lists the expected values and whether the tunnel is terminated or allowed. Note that the number following the product string is a bitmask of all of the allowed products.
Recommended Action You may need to install a different personal ASA on the client or change the configuration on the ASA.
1-358
Chapter 1
713143
Error Message %ASA-7-713143: Processing firewall record. Vendor: vendor(id), Product: product(id), Caps: capability_value, Version Number: version_number, Version String: version_text Explanation Debugging information about the ASA installed on the client appears. Recommended Action None required.
713144
Error Message %ASA-5-713144: Ignoring received malformed firewall record; reason error_reason TLV type attribute_value correction Explanation Bad ASA information was received from the client. Recommended Action Check the personal configuration on the client and the ASA.
713145
Error Message %ASA-6-713145: Detected Hardware Client in network extension mode, adding static route for address: IP_address, mask: netmask Explanation A tunnel with a hardware client in network extension mode has been negotiated, and a
static route is being added for the private network behind the hardware client. This configuration enables the ASA to make the remote network known to all the routers on the private side of the headend.
713146
Error Message %ASA-3-713146: Could not add route for Hardware Client in network extension mode, address: IP_address, mask: netmask Explanation An internal software error has occurred. A tunnel with a hardware client in network
extension mode has been negotiated, and an attempt to add the static route for the private network behind the hardware client failed. The routing table may be full, or a possible addressing error has occurred.
1-359
Syslog Messages
713147
Error Message %ASA-6-713147: Terminating tunnel to Hardware Client in network extension mode, deleting static route for address: IP_address, mask: netmask Explanation A tunnel to a hardware client in network extension mode is being removed, and the static route for the private network is being deleted behind the hardware client. Recommended Action None required.
713148
Error Message %ASA-5-713148: Terminating tunnel to Hardware Client in network extension mode, unable to delete static route for address: IP_address, mask: netmask Explanation While a tunnel to a hardware client in network extension mode was being removed, a route to the private network behind the hardware client cannot be deleted. This might indicate an addressing or software problem. Recommended Action Check the routing table to ensure that the route is not there. If it is, it may have
to be removed manually, but only if the tunnel to the hardware client has been completely removed.
713149
Error Message %ASA-3-713149: Hardware client security attribute attribute_name was enabled but not requested. Explanation The headend ASA has the specified hardware client security attribute enabled, but the attribute was not requested by the VPN 3002 hardware client. Recommended Action Check the configuration on the hardware client.
713152
Error Message %ASA-3-713152: Unable to obtain any rules from filter ACL_tag to send to client for CPP, terminating connection. Explanation The client is required to use CPP to provision its ASA, but the headend device was unable to obtain any ACLs to send to the client. This is probably due to a misconfiguration. Recommended Action Check the ACLs specified for CPP in the group policy for the client.
1-360
Chapter 1
713154
Error Message %ASA-4-713154: DNS lookup for peer_description Server [server_name] failed! Explanation This message appears when a DNS lookup for the specified server has not been
resolved.
Recommended Action Check the DNS server configuration on the ASA. Also check the DNS server
to ensure that it is operational and has hostname to IP address mapping.
713155
Error Message %ASA-5-713155: DNS lookup for Primary VPN Server [server_name] successfully resolved after a previous failure. Resetting any Backup Server init. Explanation A previous DNS lookup failure for the primary server might have caused the ASA to initialize a backup peer. This message indicates that a later DNS lookup on the primary server finally succeeded and is resetting any backup server initializations. A tunnel initiated after this point will be aimed at the primary server. Recommended Action None required.
713156
Error Message %ASA-5-713156: Initializing Backup Server [server_name or IP_address] Explanation The client is failing over to a backup server, or a failed DNS lookup for the primary server caused the ASA to initialize a backup server. A tunnel initiated after this point will be aimed at the specified backup server. Recommended Action None required.
713157
Error Message %ASA-4-713157: Timed out on initial contact to server [server_name or IP_address] Tunnel could not be established. Explanation The client tried to initiate a tunnel by sending out IKE MSG1, but did not receive a
response from the ASA on the other end. If backup servers are available, the client will attempt to connect to one of them.
Recommended Action Verify connectivity to the headend ASA.
1-361
Syslog Messages
713158
Error Message %ASA-5-713158: Client rejected NAT enabled IPsec Over UDP request, falling back to IPsec Over TCP Explanation The client is configured to use IPsec over TCP. The client rejected the attempt by the ASA to use IPsec over UDP. Recommended Action If TCP is desired, no action is required. Otherwise, check the client
configuration.
713159
Error Message %ASA-3-713159: TCP Connection to Firewall Server has been lost, restricted tunnels are now allowed full network access Explanation The TCP connection to the ASA server was lost for a certain reason, such as the server has rebooted, a network problem has occurred, or an SSL mismatch has occurred. Recommended Action If the server connection was lost after the initial connection was made, then the server and network connections must be checked. If the initial connection is lost immediately, this might indicate an SSL authentication problem.
713160
Error Message %ASA-7-713160: Remote user (session Id - id) has been granted access by the Firewall Server Explanation Normal authentication of the remote user to the ASA server has occurred. Recommended Action None required.
713161
Error Message %ASA-3-713161: Remote user (session Id - id) network access has been restricted by the Firewall Server Explanation The ASA server has sent the ASA a message indicating that this user must be restricted.
There are several reasons for this, including ASA software upgrades or changes in permissions. The ASA server will transition the user back into full access mode as soon as the operation has been completed.
Recommended Action No action is required unless the user is never transitioned back into full access
state. If this does not happen, refer to the ASA server for more information on the operation that is being performed and the state of the ASA software running on the remote machine.
1-362
Chapter 1
713162
Error Message %ASA-3-713162: Remote user (session Id - id) has been rejected by the Firewall Server Explanation The ASA server has rejected this user. Recommended Action Check the policy information on the ASA server to make sure that the user is configured correctly.
713163
Error Message %ASA-3-713163: Remote user (session Id - id) has been terminated by the Firewall Server Explanation The ASA server has terminated this user session, which can occur if the integrity agent stops running on the client machine or if the security policy is modified by the remote user in any way. Recommended Action Verify that the ASA software on the client machine is still running and that the
policy is correct.
713164
Error Message %ASA-7-713164: The Firewall Server has requested a list of active user sessions Explanation The ASA server will request the session information if it detects that it has stale data or if it loses the session data (because of a reboot). Recommended Action None required.
713165
Error Message %ASA-3-713165: Client IKE Auth mode differs from the group's configured Auth mode Explanation The client negotiated with preshared keys while its tunnel group points to a policy that
is configured to use digital certificates.

Recommended Action Check the client configuration.
1-363
Syslog Messages
713166
Error Message %ASA-3-713166: Headend security gateway has failed our user authentication attempt - check configured username and password Explanation The hardware client has failed extended authentication. This is most likely a username
and password problem or an authentication server issue.

Recommended Action Verify that the configured username and password values on each side match. Also verify that the authentication server at the headend is operational.
713167
Error Message %ASA-3-713167: Remote peer has failed user authentication - check configured username and password Explanation The remote user has failed to extend authentication. This is most likely a username or
password problem, or an authentication server issue.

Recommended Action Verify that the configured username and password values on each side match. Also verify that the authentication server being used to authenticate the remote user is operational.
713168
Error Message %ASA-3-713168: Re-auth enabled, but tunnel must be authenticated interactively! Explanation Reauthentication on rekeying has been enabled, but the tunnel authentication requires manual intervention. Recommended Action If manual intervention is desired, no action is required. Otherwise, check the
interactive authentication configuration.
713169
Error Message %ASA-7-713169: IKE Received delete for rekeyed SA IKE peer: IP_address, SA address: internal_SA_address, tunnelCnt: tunnel_count Explanation IKE has received a delete message from the remote peer to delete its old IKE SA after a rekey has completed. Recommended Action None required.
1-364
Chapter 1
713170
Error Message %ASA-7-713170: Group group IP ip IKE Received delete for rekeyed centry IKE peer: IP_address, centry address: internal_address, msgid: id Explanation IKE has received a delete message from the remote peer to delete its old centry after
Phase 2 rekeying is completed.

713171
Error Message %ASA-7-713171: NAT-Traversal sending NAT-Original-Address payload Explanation UDP-Encapsulated-Transport was either proposed or selected during Phase 2. Send this payload for NAT-Traversal in this case. Recommended Action None required.
713172
Error Message %ASA-6-713172: Automatic NAT Detection Status: Remote end is|is not behind a NAT device This end is|is not behind a NAT device Explanation NAT-Traversal auto-detected NAT. Recommended Action None required.
713174
Error Message %ASA-3-713174: Hardware Client connection rejected! Network Extension Mode is not allowed for this group! Explanation A hardware client is attempting to tunnel in using network extension mode, but network extension mode is not allowed. Recommended Action Verify the configuration of the network extension mode versus PAT mode.
1-365
Syslog Messages
713176
Error Message %ASA-2-713176: Device_type memory resources are critical, IKE key acquire message on interface interface_number, for Peer IP_address ignored Explanation The ASA is processing data intended to trigger an IPsec tunnel to the indicated peer.
Because memory resources are at a critical state, it is not initiating any more tunnels. The data packet has been ignored and dropped.
Recommended Action If condition persists, verify that the ASA is efficiently configured. An ASA with increased memory may be required for this application.
713177
Error Message %ASA-6-713177: Received remote Proxy Host FQDN in ID Payload: Host Name: host_name Address IP_address, Protocol protocol, Port port Explanation A Phase 2 ID payload containing an FQDN has been received from the peer. Recommended Action None required.
713178
Error Message %ASA-5-713178: IKE Initiator received a packet from its peer without a Responder cookie Explanation An internal software error has occurred. Recommended Action If the problem persists, contact the Cisco TAC.
713179
Error Message %ASA-5-713179: IKE AM Initiator received a packet from its peer without a payload_type payload Explanation An internal software error has occurred. Recommended Action If the problem persists, contact the Cisco TAC.
1-366
Chapter 1
713182
Error Message %ASA-3-713182: IKE could not recognize the version of the client! IPsec Fragmentation Policy will be ignored for this connection! Explanation An internal software error has occurred. Recommended Action If the problem persists, contact the Cisco TAC.
713184
Error Message %ASA-6-713184: Client Type: Client_type Client Application Version: Application_version_string Explanation The client operating system and application version appear. If the information is not
available, then N/A will be indicated.

713185
Error Message %ASA-3-713185: Error: Username too long - connection aborted Explanation The client returned an invalid length username, and the tunnel was torn down. Recommended Action Check the username and make changes, if necessary.
713186
Error Message %ASA-3-713186: Invalid secondary domain name list received from the authentication server. List Received: list_text Character index (value) is illegal Explanation An invalid secondary domain name list was received from an external RADIUS authentication server. When split tunnelling is used, this list identifies the domains that the client should resolve through the tunnel. Recommended Action Correct the specification of the Secondary-Domain-Name-List attribute (vendor-specific attribute 29) on the RADIUS server. The list must be specified as a comma-delimited list of domain names. Domain names may include only alphanumeric characters, a hyphen, an underscore, and a period.
1-367
Syslog Messages
713187
Error Message %ASA-7-713187: Tunnel Rejected: IKE peer does not match remote peer as defined in L2L policy IKE peer address: IP_address, Remote peer address: IP_address Explanation The IKE peer that is attempting to bring up this tunnel is not the one that is configured in the ISAKMP configuration that is bound to the received remote subnet. Recommended Action Verify that L2L settings are correct on the headend and peer.
713189
Error Message %ASA-3-713189: Attempted to assign network or broadcast IP_address, removing (IP_address) from pool. Explanation The IP address from the pool is either the network or broadcast address for this subnet.
This address will be marked as unavailable.

Recommended Action This error is generally benign, but the IP address pool configuration should be
checked.
713190
Error Message %ASA-7-713190: Got bad refCnt (ref_count_value) assigning IP_address (IP_address) Explanation The reference counter for this SA is invalid. Recommended Action None required.
713191
Error Message %ASA-3-713191: Maximum concurrent IKE negotiations exceeded! Explanation To minimize CPU-intensive cryptographic calculations, the ASA limits the number of connection negotiations in progress. When a new negotiation is requested and the ASA is already at its limit, the new negotiation is rejected. When an existing connection negotiation completes, new connection negotiation will again be permitted. Recommended Action See the crypto ikev1 limit max-in-negotiation-sa command. Increasing the limit can degrade performance..
1-368
Chapter 1
713193
Error Message %ASA-3-713193: Received packet with missing payload, Expected payload: payload_id Explanation The ASA received an encrypted or unencrypted packet of the specified exchange type that had one or more missing payloads. This usually indicates a problem on the peer. Recommended Action Verify that the peer is sending valid IKE messages.
713194
Error Message %ASA-3-713194: Sending IKE|IPsec Delete With Reason message: termination_reason Explanation A delete message with a termination reason code was received. Recommended Action None required.
713195
Error Message %ASA-3-713195: Tunnel rejected: Originate-Only: Cannot accept incoming tunnel yet! Explanation The originate-only peer can accept incoming connections only after it brings up the first P2 tunnel. At that point, data from either direction can initiate additional Phase 2 tunnels. Recommended Action If a different behavior is desired, the originate-only configuration needs to be
revised.
713196
Error Message %ASA-5-713196: Remote L2L Peer IP_address initiated a tunnel with same outer and inner addresses. Peer could be Originate Only - Possible misconfiguration! Explanation The remote L2L peer has initiated a public-public tunnel. The remote L2L peer expects a response from the peer at the other end, but does not receive one, because of a possible misconfiguration. Recommended Action Check the L2L configuration on both sides.
1-369
Syslog Messages
713197
Error Message %ASA-5-713197: The configured Confidence Interval of number seconds is invalid for this tunnel_type connection. Enforcing the second default. Explanation The configured confidence interval in the group is outside of the valid range. Recommended Action Check the confidence setting in the group to make sure it is within the valid
range.
713198
Error Message %ASA-3-713198: User Authorization failed: user User authorization failed. Username could not be found in the certificate Explanation A reason string that states that a username cannot be found in the certificate appears. Recommended Action Check the group configuration and client authorization.
713199
Error Message %ASA-5-713199: Reaper corrected an SA that has not decremented the concurrent IKE negotiations counter (counter_value)! Explanation The Reaper corrected an internal software error. Recommended Action If the problem persists, contact the Cisco TAC.
713203
Error Message %ASA-3-713203: IKE Receiver: Error reading from socket. Explanation An error occurred while reading a received IKE packet. This is generally an internal error and might indicate a software problem. Recommended Action This problem is usually benign, and the system will correct itself. If the problem persists, contact the Cisco TAC.
1-370
Chapter 1
713204
Error Message %ASA-7-713204: Adding static route for client address: IP_address Explanation This message indicates that a route to the peer-assigned address or to the networks
protected by a hardware client was added to the routing table.

713205
Error Message %ASA-3-713205: Could not add static route for client address: IP_address Explanation An attempt to add a route to the client-assigned address or to the networks protected by a hardware client failed. This might indicate duplicate routes in the routing table or a corrupted network address. The duplicate routes might be caused by routes that were not cleaned up correctly or by having multiple clients sharing networks or addresses. Recommended Action Check the IP local pool configuration as well as any other IP address-assigning mechanism being used (for example, DHCP or RADIUS). Make sure that routes are being cleared from the routing table. Also check the configuration of networks and/or addresses on the peer.
713206
Error Message %ASA-3-713206: Tunnel Rejected: Conflicting protocols specified by tunnel-group and group-policy Explanation A tunnel was dropped because the allowed tunnel specified in the group policy was
different from the allowed tunnel in the tunnel group configuration.

Recommended Action Check the tunnel group and group policy configuration.
713208
Error Message %ASA-3-713208: Cannot create dynamic rule for Backup L2L entry rule rule_id Explanation A failure occurred in creating the ACLs that trigger IKE and allow IPsec data to be processed properly. The failure was specific to the backup L2L configuration, which may indicate a configuration error, a capacity error, or an internal software error. Recommended Action If the ASA is running the maximum number of connections and VPN tunnels, there may be a memory issue. If not, check the backup L2L and crypto map configurations, specifically the ACLs associated with the crypto maps.
1-371
Syslog Messages
713209
Error Message %ASA-3-713209: Cannot delete dynamic rule for Backup L2L entry rule id Explanation A failure occurred in deleting the ACLs that trigger IKE and allow IPsec data to be processed correctly. The failure was specific to the backup L2L configuration. This may indicate an internal software error. Recommended Action If the problem persists, contact the Cisco TAC.
713210
Error Message %ASA-3-713210: Cannot create dynamic map for Backup L2L entry rule_id Explanation A failure occurred in creating a run-time instance of the dynamic crypto map associated
with backup L2L configuration. This may indicate a configuration error, a capacity error, or an internal software error.
Recommended Action If the ASA is running the maximum number of connections and VPN tunnels, there may be a memory issue. If not, check the backup L2L and crypto map configurations, and specifically the ACLs associated with the crypto maps.
713211
Error Message %ASA-6-713211: Adding static route for L2L peer coming in on a dynamic map. address: IP_address, mask: netmask Explanation The ASA is adding a route for the private address or networks of the peer. In this case, the peer is either a client or a L2L peer with an unknown address. Both of these cases use dynamic crypto maps to allow the tunnel. Recommended Action None required.
713212
Error Message %ASA-3-713212: Could not add route for L2L peer coming in on a dynamic map. address: IP_address, mask: netmask Explanation The ASA failed while attempting to add a route for the private address or networks of the peer. In this case, the peer is either a client or a L2L peer with an unknown address. Both of these cases use dynamic crypto maps to allow the tunnel. This might indicate duplicate routes, a full routing table, or a failure of the ASA to remove previously used routes. Recommended Action Check the routing table to make sure there is room for additional routes and that obsolete routes are not present. If the table is full or includes obsolete routes, remove the routes and try again. If the problem persists, contact the Cisco TAC.
1-372
Chapter 1
713213
Error Message %ASA-6-713213: Deleting static route for L2L peer that came in on a dynamic map. address: IP_address, mask: netmask Explanation The ASA is deleting a route for the private address or networks of the peer. In this case,
the peer is either a client or a L2L peer with an unknown address. Both of these cases use dynamic crypto maps to allow the tunnel.
713214
Error Message %ASA-3-713214: Could not delete route for L2L peer that came in on a dynamic map. address: IP_address, mask: netmask Explanation The ASA experienced a failure while deleting a route for the private address or networks
of the peer. In this case, the peer is either a client or a L2L peer with an unknown address. Both of these cases use dynamic crypto maps to allow the tunnel. The route may have already been deleted,or an internal software error has occurred.
Recommended Action If the route has already been deleted, the condition is benign and the device will
function normally. If the problem persists or can be linked to routing issues over VPN tunnels, then check the routing and addressing portions of the VPN L2L configuration. Check the reverse route injection and the ACLs associated with the appropriate crypto map. If the problem persists, contact the Cisco TAC.
713215
Error Message %ASA-6-713215: No match against Client Type and Version rules. Client: type version is/is not allowed by default Explanation The client type and the version of a client did not match any of the rules configured on the ASA. The default action appears. Recommended Action Determine what the default action and deployment requirements are, and make
the applicable changes.
1-373
Syslog Messages
713216
Error Message %ASA-5-713216: Rule: action [Client type]: version Client: type version allowed/not allowed Explanation The client type and the version of a client have matched one of the rules. The results of
the match and the rule are displayed.

Recommended Action Determine what the deployment requirements are, and make the appropriate
changes.
713217
Error Message %ASA-3-713217: Skipping unrecognized rule: action: action client type: client_type client version: client_version Explanation A malformed client type and version rule exist. The required format is action client type | client version action. Either permit or deny client type and client version are displayed under Session Management. Only one wildcard per parameter (*) is supported. Recommended Action Correct the rule.
713218
Error Message %ASA-3-713218: Tunnel Rejected: Client Type or Version not allowed. Explanation The client was denied access according to the configured rules. Recommended Action None required.
713219
Error Message %ASA-6-713219: Queuing KEY-ACQUIRE messages to be processed when P1 SA is complete. Explanation Phase 2 messages are being enqueued after Phase 1 completes. Recommended Action None required.
1-374
Chapter 1
713220
Error Message %ASA-6-713220: De-queuing KEY-ACQUIRE messages that were left pending. Explanation Queued Phase 2 messages are being processed. Recommended Action None required.
713221
Error Message %ASA-7-713221: Static Crypto Map check, checking map = crypto_map_tag, seq = seq_number... Explanation The ASA is iterating through the crypto maps looking for configuration information. Recommended Action None required.
713222
Error Message %ASA-7-713222: Group group Username username IP ip Static Crypto Map check, map = crypto_map_tag, seq = seq_number, ACL does not match proxy IDs src:source_address dst:dest_address Explanation While iterating through the configured crypto maps, the ASA cannot match any of the
associated ACLs. This generally means that an ACL was misconfigured.

Recommended Action Check the ACLs associated with this tunnel peer, and make sure that they
specify the appropriate private networks from both sides of the VPN tunnel.
713223
Error Message %ASA-7-713223: Static Crypto Map check, map = crypto_map_tag, seq = seq_number, no ACL configured Explanation The crypto map associated with this peer is not linked to an ACL. Recommended Action Make sure an ACL associated with this crypto map exists, and that the ACL
includes the appropriate private addresses or network from both sides of the VPN tunnel.
1-375
Syslog Messages
713224
Error Message %ASA-7-713224: Static Crypto Map Check by-passed: Crypto map entry incomplete! Explanation The crypto map associated with this VPN tunnel is missing critical information. Recommended Action Verify that the crypto map is configured correctly with both the VPN peer, a transform set, and an associated ACL.
713225
Error Message %ASA-7-713225: [IKEv1], Static Crypto Map check, map map_name, seq = sequence_number is a successful match Explanation The ASA found a valid matching crypto map for this VPN tunnel. Recommended Action None required.
713226
Error Message %ASA-3-713226: Connection failed with peer IP_address, no trust-point defined in tunnel-group tunnel_group Explanation When the device is configured to use digital certificates, a trustpoint must be specified
in the configuration. When the trustpoint is missing from the configuration, this message is generated to flag an error.

IP_addressIP address of the peer tunnel_groupTunnel group for which the trustpoint was missing in the configuration
Recommended Action The administrator of the device has to specify a trustpoint in the configuration.
713227
Error Message %ASA-3-713227: Rejecting new IPsec SA negotiation for peer Peer_address. A negotiation was already in progress for local Proxy Local_address/Local_netmask, remote Proxy Remote_address/Remote_netmask Explanation When establishing a Phase SA, the ASA will reject a new Phase 2 matching this proxy. Recommended Action None required.
1-376
Chapter 1
713228
Error Message %ASA-6-713228: Group = group, Username = uname, IP = remote_IP_address Assigned private IP address assigned_private_IP to remote user Explanation IKE obtained a private IP address for the client from DHCP or from the address pool.
groupThe name of the group unameThe name of the user remote_IP_addressThe IP address of the remote client assigned_private_IPThe client IP address assigned by DHCP or from the local address pool
713229
Error Message %ASA-5-713229: Auto Update - Notification to client client_ip of update string: message_string. Explanation A VPN remote access client is notified that updated software is available for download.
The remote client user is responsible for choosing to update the client access software.

client_ipThe IP address of the remote client message_stringThe message text sent to the remote client
713230
Error Message %ASA-3-713230 Internal Error, ike_lock trying to lock bit that is already locked for type type Explanation An internal error occurred, which is reporting that the IKE subsystem is attempting to lock memory that has already been locked. This indicates errors on semaphores that are used to protect memory violations for IKE SAs. This message does not indicate that anything is seriously wrong. However, an unexpected event has occurred, and steps are automatically being taken for recovery.
typeString that describes the type of semaphore that had a locking issue
1-377
Syslog Messages
713231
Error Message %ASA-3-713231 Internal Error, ike_lock trying to unlock bit that is not locked for type type Explanation An internal error has occurred, which is reporting that the IKE subsystem is attempting to unlock memory that is not currently locked. This indicates errors on semaphores that are used to protect memory violations for IKE SAs. This message does not indicate that anything is seriously wrong. However, an unexpected event has occurred, and steps are automatically being taken for recovery.
typeString that describes the type of semaphore that had a locking issue
713232
Error Message %ASA-3-713232 SA lock refCnt = value, bitmask = hexvalue, p1_decrypt_cb = value, qm_decrypt_cb = value, qm_hash_cb = value, qm_spi_ok_cb = value, qm_dh_cb = value, qm_secret_key_cb = value, qm_encrypt_cb = value Explanation All the IKE SA are locked, and a possible error has been detected. This message reports
errors on semaphores that are used to protect memory violations for IKE SAs.

valueDecimal value hexvalueHexadecimal value
713233
Error Message %ASA-7-713233: (VPN-unit) Remote network (remote network) validated for network extension mode. Explanation The remote network received during the Phase 2 negotiation was validated. The message indicates the results of the remote network check during Phase 2 negotiations for Network Extension Mode clients. This is part of an existing feature that prevents users from misconfiguring their hardware client network (for example, configuring overlapping networks or the same network on multiple clients).
remote networkSubnet address and subnet mask from Phase 2 proxy
1-378
Chapter 1
713234
Error Message %ASA-7-713234: (VPN-unit) Remote network (remote network) from network extension mode client mismatches AAA configuration (aaa network). Explanation The remote network received during the Phase 2 negotiation does not match the framed-ip-address and framed-subnet-mask that were returned from the AAA server for this session.
remote networkSubnet address and subnet mask from Phase 2 proxy aaa networkSubnet address and subnet mask configured through AAA
Recommended Action Do one of the following:
Check the address assignment for this user and group, then check the network configuration on the HW client, and correct any inconsistencies. Disable address assignment for this user and group.
713235
Error Message %ASA-6-713235: Attempt to send an IKE packet from standby unit. Dropping the packet! Explanation Normally, IKE packets should never be sent from the standby unit to the remote peer. If
such an attempt is made, an internal logic error may have occurred. The packet never leaves the standby unit because of protective code. This message facilitates debugging.
713236
Error Message %ASA-7-713236: IKE_DECODE tx/rx Message (msgid=msgid) with payloads:payload1 (payload1_len) + payload2 (payload2_len)...total length: tlen Explanation IKE sent or received various messages.
The following example shows the output when IKE receives a message with an 8-byte hash payload, an 11-byte notify payload, and two 13-byte vendor-specific payloads:
%ASA-7-713236: IKE_DECODE RECEIVED Message msgid=0) with payloads: HDR + HASH (8) + NOTIFY (11) + VENDOR (13) + VENDOR (13) + NONE (0)
1-379
Syslog Messages
713237
Error Message %ASA-5-713237: ACL update (access_list) received during re-key re-authentication will not be applied to the tunnel. Explanation The Phase 1 rekey of a remote access IPsec tunnel appears under the following
conditions:

The tunnel is configured to reauthenticate the user when the tunnel is rekeyed. The RADIUS server returns an access list or a reference to a locally configured access list that is different from the one that was returned when the tunnel was first established. access_listName associated with the static or dynamic access list, as displayed in the output of the show access-list command
Under these conditions, the ASA ignores the new access list and this message is generated.
Recommended Action IPsec users must reconnect for new user-specific access lists to take effect.
713238
Error Message %ASA-3-713238: Invalid source proxy address: 0.0.0.0! Check private address on remote client Explanation The private side address of a network extension mode client came across as 0.0.0.0. This usually indicates that no IP address was set on the private interface of the hardware client. Recommended Action Verify the configuration of the remote client.
713239
Error Message %ASA-4-713239: IP_Address: Tunnel Rejected: The maximum tunnel count allowed has been reached Explanation An attempt to create a tunnel has occurred after the maximum number of tunnels
allowed has been reached.
IP_AddressThe IP address of the peer
1-380
Chapter 1
713240
Error Message %ASA-4-713240: Received DH key with bad length: received length=rlength expected length=elength Explanation A Diffie-Hellman key with the incorrect length was received from the peer.
rlengthThe length of the DH key that was received elengthThe expected length (based on the DH key size)
713241
Error Message %ASA-4-713241: IE Browser Proxy Method setting_number is Invalid Explanation An invalid proxy setting was found during ModeCfg processing. P1 negotiation will
fail.
Recommended Action Check the msie-proxy method command settings (a subcommand of the
group-policy command), which should conform to one of the following: [auto-detect | no-modify | no-proxy | use-server]. Any other value or no value is incorrect. Try resetting the msie-proxy method command settings. If the problem persists, contact the Cisco TAC.
713242
Error Message %ASA-4-713242: Remote user is authenticated using Hybrid Authentication. Not starting IKE rekey. Explanation The ASA has detected a request to start an IKE rekey for a tunnel configured to use
Hybrid Xauth, but the rekey was not started. The ASA will wait for the client to detect and initiate an IKE rekey.
713243
Error Message %ASA-4-713243: META-DATA Unable to find the requested certificate Explanation The IKE peer requested a certificate from the cert-req payload. However, no valid
identity certificate issued by the requested DN was found.

Check the identity certificates. Enroll or import the desired certificate.
1-381
Syslog Messages
3.
Enable certificate debugging for more details.
713244
Error Message %ASA-4-713244: META-DATA Received Legacy Authentication Method(LAM) type type is different from the last type received type. Explanation The LAM attribute type received differs from the last type received. The type must be consistent throughout the user authentication process. The user authentication process cannot proceed, and the VPN connection will not be established.
typeThe LAM type
713245
Error Message %ASA-4-713245: META-DATA Unknown Legacy Authentication Method(LAM) type type received. Explanation An unsupported LAM type was received during the CRACK challenge or response user authentication process. The user authentication process cannot proceed, and the VPN connection will not be established.
typeThe LAM type
713246
Error Message %ASA-4-713246: META-DATA Unknown Legacy Authentication Method(LAM) attribute type type received. Explanation The ASA received an unknown LAM attribute type, which should not cause
connectivity problems, but might affect the functionality of the peer.
typeThe LAM attribute type
1-382
Chapter 1
713247
Error Message %ASA-4-713247: META-DATA Unexpected error: in Next Card Code mode while not doing SDI. Explanation An unexpected error occurred during state processing. Recommended Action If the problem persists, contact the Cisco TAC.
713248
Error Message %ASA-5-713248: META-DATA Rekey initiation is being disabled during CRACK authentication. Explanation When an IKE SA is negotiated using the CRACK authentication method, the Phase 1
SA rekey timer at the headend expired before a successful rekey. Because the remote client is always the initiator of the exchange when using the CRACK authentication method, the headend will not initiate the rekey. Unless the remote peer initiates a successful rekey before the IKE SA expires, the connection will come down upon IKE SA expiration.
713249
Error Message %ASA-4-713249: META-DATA Received unsupported authentication results: result Explanation While negotiating an IKE SA using the CRACK authentication method, the IKE
subsystem received a result that is not supported during CRACK authentication from the authentication subsystem. The user authentication fails, and the VPN connection is torn down.
resultThe result returned from the authentication subsystem
713250
Error Message %ASA-5-713250: META-DATA Received unknown Internal Address attribute: attribute Explanation The ASA received a request for an internal address attribute that is not recognizable.
The attribute might be valid, but not currently supported, or the peer might be sending an illegal value. This should not cause connectivity problems, but might affect the functionality of the peer.
1-383
Syslog Messages
713251
Error Message %ASA-4-713251: META-DATA Received authentication failure message Explanation The ASA received a notification message that indicated an authentication failure while an IKE SA is negotiated using the CRACK authentication method. The connection is torn down. Recommended Action None required.
713252
Error Message %ASA-5-713252: Group = group, Username = user, IP = ip, Integrity Firewall Server is not available. VPN Tunnel creation rejected for client. Explanation When the group policy is configured to require the client to authenticate with a Zonelab
Integrity Server, the server might need to be connected to the concentrator depending on the failure policy configured. If the fail policy is to reject the client connection, this message is generated when a Zonelab Integrity Server is not connected to the ASA at the time the client is connecting.

groupThe tunnel group to which the remote access user is connecting userThe remote access user ipThe IP address of the remote access user
Recommended Action Check that the configurations on the concentrator and the Zonelab Integrity
Server match. Then verify that communication exists between the concentrator and the Zonelab Integrity Server.
713253
Error Message %ASA-5-713253: Group = group, Username = user, IP = ip, Integrity Firewall Server is not available. Entering ALLOW mode. VPN Tunnel created for client. Explanation When the group policy is configured to require a client to authenticate with a Zonelab
Integrity Server, the server might need to be connected to the concentrator, depending on the failure policy configured. If the failure policy is to accept the client connection, and provide unrestricted network access, this message is generated when a Zonelab Integrity Server is not connected to the ASA at the time the client is connecting.

groupThe tunnel group to which the remote access user is connecting userThe remote access user ipThe IP address of the remote access user
Recommended Action Check that the configurations on the ASA and the Zonelab Integrity Server match, and verify that communication exists between the ASA and the Zonelab Integrity Server.
1-384
Chapter 1
713254
Error Message %ASA-3-713254: Group = groupname, Username = username, IP = peerip, Invalid IPsec/UDP port = portnum, valid range is minport - maxport, except port 4500, which is reserved for IPsec/NAT-T Explanation You cannot use UDP port 4500 for IPsec/UDP connections, because it is reserved for
IPsec or NAT-T connections. The CLI does not allow this configuration for local groups. This message should only occur for externally defined groups.

groupnameThe name of the user group usernameThe name of the user peeripThe IP address of the client portnumThe IPsec/UDP port number on the external server minportThe minimum valid port number for a user-configurable port, which is 4001 maxportThe maximum valid port number for a user-configurable port, which is 49151
Recommended Action Change the IPsec or UDP port number on the external server to another port
number. Valid port numbers are 4001 to 49151.
713255
Error Message %ASA-4-713255: IP = peer-IP, Received ISAKMP Aggressive Mode message 1 with unknown tunnel group name group-name Explanation An unknown tunnel group was specified in ISAKMP Aggressive Mode message 1.
peer-ipThe address of the peer group-nameThe group name specified by the peer
Recommended Action Check the tunnel group and client configurations to make sure that they are
valid.
713256
Error Message %ASA-6-713256: IP = peer-IP, Sending spoofed ISAKMP Aggressive Mode message 2 due to receipt of unknown tunnel group. Aborting connection. Explanation When the peer specifies an invalid tunnel group, the ASA will still send message 2 to prevent the peer from gleaning tunnel group information.
peer-ipThe address of the peer
1-385
Syslog Messages
713257
Error Message %ASA-5-713257: Phase var1 failure: Mismatched attribute types for class var2: Rcv'd: var3 Cfg'd: var4 Explanation An ASA has acted as the responder in a LAN-to-LAN connection. It indicates that the
ASA crypto configuration does not match the configuration of the initiator. The message specifies during which phase the mismatch occurred, and which attributes both the responder and the initiator had that were different.

var1The phase during which the mismatch occurred var2The class to which the attributes that do not match belong var3The attribute received from the initiator var4The attribute configured
Recommended Action Check the crypto configuration on both of the LAN-to-LAN devices for inconsistencies. In particular, if a mismatch between UDP-Tunnel (NAT-T) and something else is reported, check the crypto maps. If one configuration has NAT-T disabled on the matched crypto map and the other does not, this will cause a failure.
713258
Error Message %ASA-3-713258: IP = var1, Attempting to establish a phase2 tunnel on var2 interface but phase1 tunnel is on var3 interface. Tearing down old phase1 tunnel due to a potential routing change. Explanation The ASA tries to establish a Phase 2 tunnel on an interface, and a Phase 1 tunnel already
exists on a different interface. The existing Phase 1 tunnel is torn down to allow the establishment of a new tunnel on the new interface.

var1The IP address of the peer var2The interface on which the ASA is trying to establish a Phase 2 tunnel var3The interface on which the Phase 1 tunnel exists
Recommended Action Check whether or not the route of the peer has changed. If the route has not changed, a possible misconfiguration may exist.
713259
Error Message %ASA-5-713259: Group = groupname, Username = username, IP = peerIP, Session is being torn down. Reason: reason Explanation The termination reason for the ISAKMP session appears, which occurs when the session
is torn down through session management.

groupnameThe tunnel group of the session being terminated usernameThe username of the session being terminated
1-386
Chapter 1
peerIPThe peer address of the session being terminated reasonThe RADIUS termination reason of the session being terminated. Reasons include the following: - Port Preempted (simultaneous logins) - Idle Timeout - Max Time Exceeded - Administrator Reset
713260
Error Message %ASA-3-713260: Output interface %d to peer was not found Explanation When trying to create a Phase 1 SA, the interface database could not be found for the interface ID. Recommended Action If the problem persists, contact the Cisco TAC.
713261
Error Message %ASA-3-713261: IPV6 address on output interface %d was not found Explanation When trying to create a Phase 1 SA, no IPv6 address is specified on the local interface. Recommended Action For information about how to set up an IPv6 address on a desired interface, see the Configuring IPv6 Addressing section in the CLI configuration guide.
713262
Error Message %ASA-3-713262: Rejecting new IPSec SA negotiation for peer Peer_address. A negotiation was already in progress for local Proxy Local_address/Local_prefix_len, remote Proxy Remote_address/Remote_prefix_len Explanation When establishing a Phase SA, the ASA will reject a new Phase 2 SA matching this
proxy.

Peer_addressThe new address attempting to intiate Phase 2 with a proxy matching an existing negotiation Local_addressThe address of the previous local peer currently negotiating Phase 2 Local_prefix_lenThe length of the subnet prefix according to CIDR notation Remote_addressThe address of the proxy
1-387
Syslog Messages
Remote_prefix_lenThe length of the subnet prefix according to CIDR notation
713263
Error Message %ASA-7-713263: Received local IP Proxy Subnet data in ID Payload: Address IP_address, Mask /prefix_len, Protocol protocol, Port port Explanation The ASA is adding a route for the private address or networks of the peer. In this case,

IP_addressThe base IP address of the destination network of the peer prefix_lenThe length of the subnet prefix according to CIDR notation protocol The proxy protocol portThe proxy port
713264
Error Message %ASA-7-713264: Received local IP Proxy Subnet data in ID Payload: Address IP_address, Mask/prefix_len, Protocol protocol, Port port {Received remote IP Proxy Subnet data in ID Payload: Address %a, Mask/%d, Protocol %u, Port %u} Explanation The ASA is adding a route for the private address or networks of the peer. In this case,

IP_addressThe base IP address of the destination network of the peer prefix_lenThe length of the subnet prefix according to CIDR notation protocol The proxy protocol portThe proxy port
1-388
Chapter 1
713265
Error Message %ASA-6-713265: Adding static route for L2L peer coming in on a dynamic map. address: IP_address, mask: /prefix_len Explanation The ASA is adding a route for the private address or networks of the peer. In this case, the peer is either a client or a L2L peer with an unknown address. Both of these cases use dynamic crypto maps to allow the tunnel.
IP_addressThe base IP address of the destination network of the peer prefix_lenThe length of the subnet prefix according to CIDR notation
713266
Error Message %ASA-3-713266: Could not add route for L2L peer coming in on a dynamic map. address: IP_address, mask: /prefix_len Explanation The ASA failed while attempting to add a route for the private address or networks of the peer. In this case, the peer is either a client or a L2L peer with an unknown address. Both of these cases use dynamic crypto maps to allow the tunnel. This might indicate duplicate routes, a full IPv6 routing table, or a failure of the ASA to remove previously used routes.
Recommended Action Check the IPv6 routing table to make sure there is room for additional routes,
and that obsolete routes are not present. If the table is full or includes obsolete routes, remove the routes and try again. If the problem persists, contact the Cisco TAC.
713267
Error Message %ASA-6-713267: Deleting static route for L2L peer that came in on a dynamic map. address: IP_address, mask: /prefix_len Explanation The ASA failed while attempting to add a route for the private address or networks of
the peer. In this case, the peer is either a client or a L2L peer with an unknown address. Both of these cases use dynamic crypto maps to allow the tunnel.

1-389
Syslog Messages
713268
Error Message %ASA-3-713268: Could not delete route for L2L peer that came in on a dynamic map. address: IP_address, mask: /prefix_len Explanation The ASA experienced a failure while deleting a route for the private address or networks
of the peer. In this case, the peer is either a client or a L2L peer with an unknown address. Both of these cases use dynamic crypto maps to allow the tunnel. The route may have already been deleted, or an internal software error has occurred.

Recommended Action If the route has already been deleted, the condition is benign and the device will
function normally. If the problem persists or can be linked to routing issues over VPN tunnels, then check the routing and addressing portions of the VPN L2L configuration. Also check the reverse route injection and the ACLs associated with the appropriate crypto map. If the problem persists, contact the Cisco TAC.
713269
Error Message %ASA-6-713269: Detected Hardware Client in network extension mode, adding static route for address: IP_address, mask: /prefix_len Explanation A tunnel with a hardware client in network extension mode has been negotiated, and a
static route is being added for the private network behind the hardware client. This configuration enables the ASA to make the remote network known to all the routers on the private side of the headend.

713270
Error Message %ASA-3-713270: Could not add route for Hardware Client in network extension mode, address: IP_address, mask: /prefix_len Explanation An internal software error has occurred. A tunnel with a hardware client in network extension mode has been negotiated, and an attempt to add the static route for the private network behind the hardware client failed. The IPv6 routing table may be full, or a possible addressing error has occurred.
1-390
Chapter 1
713271
Error Message %ASA-6-713271: Terminating tunnel to Hardware Client in network extension mode, deleting static route for address: IP_address, mask:/prefix_len Explanation A tunnel to a hardware client in network extension mode is being removed, and the static route for the private network is being deleted behind the hardware client.
713272
Error Message %ASA-3-713272: Terminating tunnel to Hardware Client in network extension mode, unable to delete static route for address: IP_address, mask: /prefix_len Explanation While a tunnel to a hardware client in network extension mode was being removed, a route to the private network behind the hardware client cannot be deleted. This might indicate an addressing or software problem.
Recommended Action Check the IPv6 routing table to ensure that the route is not there. If it is, it may
have to be removed manually, but only if the tunnel to the hardware client has been completely removed.
713273
Error Message %ASA-7-713273: Deleting static route for client address: IP_Address IP_Address address of client whose route is being removed Explanation A route to the peer-assigned address or the networks protected by a hardware client were removed from the routing table. Recommended Action None required.
1-391
Syslog Messages
713274
Error Message %ASA-3-713274: Could not delete static route for client address: IP_Address IP_Address address of client whose route is being removed Explanation While a tunnel to an IPsec client was being removed, its entry in the routing table could
not be removed. This condition may indicate a networking or software problem.

Recommended Action Check the routing table to make sure that the route does not exist. If it does, it may need to be removed manually, but only if the tunnel has been closed successfully.
713900
Error Message %ASA-1-713900: Descriptive_event_string. Explanation A serious event or failure has occurred. For example, the ASA is trying to generate a Phase 2 deletion, but the SPI did not match any of the existing Phase 2 SAs. Recommended Action In the example described, both peers are deleting Phase 2 SAs at the same time.
In this case, it is a benign error and can be ignored. If the error is persistent and results in negative side effects such as dropped tunnels or device reboots, it may reflect a software failure. In this case, copy the error message exactly as it appears on the console or in the system log, and then contact the Cisco TAC for further assistance.
713901
Error Message %ASA-2-713901: Descriptive_event_string. Explanation An error has occurred, which may be the result of a configuration error on the headend or remote access client. The event string provides details about the error that occurred. Recommended Action You may need to troubleshoot the message to determine what caused the error.
Check the ISAKMP and crypto map configuration on both peers.
713902
Error Message %ASA-3-713902: Descriptive_event_string. Explanation An error has occurred, which may be the result of a configuration error either on the headend or remote access client. Recommended Action It might be necessary to troubleshoot the configuration to determine the cause of the error. Check the ISAKMP and crypto map configuration on both peers.
1-392
Chapter 1
713903
Error Message %ASA-4-713903: Descriptive_event_string. Explanation A warning appears, which may be the result of unexpected behavior of a peer (such as a loss of connectivity). For example:
%ASA-4-713903: Group = IPSecGroup. IP = 70.172.17.23, Error: Unable to remove PeerTblEntry.
An IPsec connection attempt failed (for example, in an authentication failure) that was caused by an incorrectly typed password or the inadvertent disconnection of an IPsec client during authentication.
713904
Error Message %ASA-5-713904: Descriptive_event_string. Explanation Notification status information appears, which is used to track events that have
occurred.
713905
Error Message %ASA-6-713905: Descriptive_event_string. Explanation Information status details appear, which are used to track events that have occurred. Recommended Action None required.
713906
Error Message %ASA-7-713906: Descriptive_event_string. Explanation Debugging status information appears, which is used to track events that have occurred. Recommended Action None required.
1-393
Syslog Messages
714001
Error Message %ASA-7-714001: description_of_event_or_packet Explanation A description of an IKE protocol event or packet was provided. Recommended Action None required.
714002
Error Message %ASA-7-714002: IKE Initiator starting QM: msg id = message_number Explanation The ASA has sent the first packet of the Quick mode exchange as the Phase 2 initiator. Recommended Action None required.
714003
Error Message %ASA-7-714003: IKE Responder starting QM: msg id = message_number Explanation The ASA has received the first packet of the Quick mode exchange as the Phase 2
responder.
714004
Error Message %ASA-7-714004: IKE Initiator sending 1st QM pkt: msg id = message_number Explanation The protocol of the first Quick Mode packet was decoded. Recommended Action None required.
714005
Error Message %ASA-7-714005: IKE Responder sending 2nd QM pkt: msg id = message_number Explanation The protocol of the second Quick Mode packet was decoded. Recommended Action None required.
1-394
Chapter 1
714006
Error Message %ASA-7-714006: IKE Initiator sending 3rd QM pkt: msg id = message_number Explanation The protocol of the third Quick Mode packet was decoded. Recommended Action None required.
714007
Error Message %ASA-7-714007: IKE Initiator sending Initial Contact Explanation The ASA is building and sending the initial contact payload. Recommended Action None required.
714011
Error Message %ASA-7-714011: Description of received ID values Explanation The ASA received the displayed ID information during the negotiation. Recommended Action None required.
715001
Error Message %ASA-7-715001: Descriptive statement Explanation A description of an event or problem encountered by the ASA appears. Recommended Action The action depends on the description.
715004
Error Message %ASA-7-715004: subroutine name() Q Send failure: RetCode (return_code) Explanation An internal error occurred when attempting to put messages in a queue. Recommended Action This is often a benign condition. If the problem persists, contact the Cisco TAC.
1-395
Syslog Messages
715005
Error Message %ASA-7-715005: subroutine name() Bad message code: Code (message_code) Explanation An internal subroutine received a bad message code. Recommended Action This is often a benign condition. If the problem persists, contact the Cisco TAC.
715006
Error Message %ASA-7-715006: IKE got SPI from key engine: SPI = SPI_value Explanation The IKE subsystem received an SPI value from IPsec. Recommended Action None required.
715007
Error Message %ASA-7-715007: IKE got a KEY_ADD msg for SA: SPI = SPI_value Explanation IKE has completed tunnel negotiation and has successfully loaded the appropriate encryption and hashing keys for IPsec use. Recommended Action None required.
715008
Error Message %ASA-7-715008: Could not delete SA SA_address, refCnt = number, caller = calling_subroutine_address Explanation The calling subroutine cannot delete the IPsec SA. This might indicate a reference count
problem.
Recommended Action If the number of stale SAs grows as a result of this event, contact the Cisco
TAC.
715009
Error Message %ASA-7-715009: IKE Deleting SA: Remote Proxy IP_address, Local Proxy IP_address Explanation SA is being deleted with the listed proxy addresses. Recommended Action None required.
1-396
Chapter 1
715013
Error Message %ASA-7-715013: Tunnel negotiation in progress for destination IP_address, discarding data Explanation IKE is in the process of establishing a tunnel for this data. All packets to be protected by this tunnel will be dropped until the tunnel is fully established. Recommended Action None required.
715019
Error Message %ASA-7-715019: Group group Username username IP ip IKEGetUserAttributes: Attribute name = name Explanation The modecfg attribute name and value pair being processed by the ASA appear. Recommended Action None required.
715020
Error Message %ASA-7-715020: construct_cfg_set: Attribute name = name Explanation The modecfg attribute name and value pair being transmitted by the ASA appear. Recommended Action None required.
715021
Error Message %ASA-7-715021: Delay Quick Mode processing, Cert/Trans Exch/RM DSID in progress Explanation Quick mode processing is being delayed until all Phase 1 processing has been completed (for transaction mode). Recommended Action None required.
1-397
Syslog Messages
715022
Error Message %ASA-7-715022: Resume Quick Mode processing, Cert/Trans Exch/RM DSID completed Explanation Phase 1 processing has completed, and quick mode is being resumed. Recommended Action None required.
715027
Error Message %ASA-7-715027: IPsec SA Proposal # chosen_proposal, Transform # chosen_transform acceptable Matches global IPsec SA entry # crypto_map_index Explanation The indicated IPsec SA proposal and transform were selected from the payloads that the responder received. This data can be useful when attempting to debug IKE negotiation issues. Recommended Action None required.
715028
Error Message %ASA-7-715028: IKE SA Proposal # 1, Transform # chosen_transform acceptable Matches global IKE entry # crypto_map_index Explanation The indicated IKE SA transform was selected from the payloads that the responder
received. This data can be useful when attempting to debug IKE negotiation issues.
715033
Error Message %ASA-7-715033: Processing CONNECTED notify (MsgId message_number) Explanation The ASA is processing a message containing a notify payload with the notify type CONNECTED (16384). The CONNECTED notify type is used to complete the commit bit processing and should be included in the fourth overall quick mode packet, which is sent from the responder to the initiator. Recommended Action None required.
1-398
Chapter 1
715034
Error Message %ASA-7-715034: action IOS keep alive payload: proposal=time 1/time 2 sec. Explanation Processing for sending or receiving a keepalive payload message is being performed. Recommended Action None required.
715035
Error Message %ASA-7-715035: Starting IOS keepalive monitor: seconds sec. Explanation The keepalive timer will monitor for a variable number of seconds for keepalive
messages.
715036
Error Message %ASA-7-715036: Sending keep-alive of type notify_type (seq number number) Explanation Processing for sending a keepalive notify message is being performed. Recommended Action None required.
715037
Error Message %ASA-7-715037: Unknown IOS Vendor ID version: major.minor.variance Explanation The capabilities of this version of the Cisco IOS are not known. Recommended Action There may be interoperability issues with features such as IKE keepalives. If the problem persists, contact the Cisco TAC.
1-399
Syslog Messages
715038
Error Message %ASA-7-715038: action Spoofing_information Vendor ID payload (version: major.minor.variance, capabilities: value) Explanation Processing for the Cisco IOS vendor ID payload has been performed. The action being performed might be Altiga spoofing the Cisco IOS. Recommended Action None required.
715039
Error Message %ASA-7-715039: Unexpected cleanup of tunnel table entry during SA delete. Explanation An entry in the IKE tunnel table was never removed when the SA was freed. This indicates a defect in the state machine. Recommended Action If the problem persists, contact the Cisco TAC.
715040
Error Message %ASA-7-715040: Deleting active auth handle during SA deletion: handle = internal_authentication_handle Explanation The authentication handle was still active during SA deletion. This is part of cleanup
recovery during the error condition.

715041
Error Message %ASA-7-715041: Received keep-alive of type keepalive_type, not the negotiated type Explanation A keepalive of the type indicated in the message was received unexpectedly. Recommended Action Check the keepalive configuration on both peers.
1-400
Chapter 1
715042
Error Message %ASA-7-715042: IKE received response of type failure_type to a request from the IP_address utility Explanation A request for an IP address for a remote access client from the internal utility that
provides these addresses cannot be satisfied. Variable text in the message string indicates more specifically what went wrong.
Recommended Action Check the IP address assignment configuration and adjust accordingly.
715044
Error Message %ASA-7-715044: Ignoring Keepalive payload from vendor not support KeepAlive capability Explanation A Cisco IOS keepalive payload from a vendor was received without keepalive
capabilities being set. The payload is ignored.

715045
Error Message %ASA-7-715045: ERROR: malformed Keepalive payload Explanation A malformed keepalive payload has been received. The payload is ignored. Recommended Action None required.
715046
Error Message %ASA-7-715046: Group = groupname, Username = username, IP = IP_address, constructing payload_description payload Explanation An IP address from a remote client for a specific group and user shows details about the IKE payload being constructed. Recommended Action None required.
1-401
Syslog Messages
715047
Error Message %ASA-7-715047: processing payload_description payload Explanation Details of the IKE payload received and being processed appear. Recommended Action None required.
715048
Error Message %ASA-7-715048: Send VID_type VID Explanation The type of vendor ID payload being sent appears. Recommended Action None required.
715049
Error Message %ASA-7-715049: Received VID_type VID Explanation The type of vendor ID payload received appears. Recommended Action None required.
715050
Error Message %ASA-7-715050: Claims to be IOS but failed authentication Explanation The vendor ID received looks like a Cisco IOS VID, but does not match hmac_sha. Recommended Action Check the vendor ID configuration on both peers. If this issue affects interoperability and the problem persists, contact the Cisco TAC.
1-402
Chapter 1
715051
Error Message %ASA-7-715051: Received unexpected TLV type TLV_type while processing FWTYPE ModeCfg Reply Explanation An unknown TLV was received in an ASA record while an FWTYPE ModeCfg Reply
was being processed. The TLV will be discarded. This might occur either because of packet corruption or because the connecting client supports a later version of the ASA protocol.
Recommended Action Check the personal FW installed on the Cisco VPN client and the personal firewall configuration on the ASA. This may also indicate a version mismatch between the VPN client and the ASA.
715052
Error Message %ASA-7-715052: Old P1 SA is being deleted but new SA is DEAD, cannot transition centries Explanation The old P1 SA is being deleted, but has no new SA to transition to because it was marked for deletion as well. This generally indicates that the two IKE peers are out-of-sync with each other and may be using different rekey times. The problem should correct itself, but there may be some small amount of data loss until a fresh P1 SA is reestablished. Recommended Action None required.
715053
Error Message %ASA-7-715053: MODE_CFG: Received request for attribute_info! Explanation The ASA received a mode configuration message requesting the specified attribute. Recommended Action None required.
715054
Error Message %ASA-7-715054: MODE_CFG: Received attribute_name reply: value Explanation The ASA received a mode configuration reply message from the remote peer. Recommended Action None required.
1-403
Syslog Messages
715055
Error Message %ASA-7-715055: Send attribute_name Explanation The ASA sent a mode configuration message to the remote peer. Recommended Action None required.
715056
Error Message %ASA-7-715056: Client is configured for TCP_transparency Explanation Because the remote end (client) is configured for IPsec over TCP, the headend ASA must not negotiate IPsec over UDP or IPsec over NAT-T with the client. Recommended Action The NAT transparency configuration may require adjustment of one of the peers if the tunnel does not come up.
715057
Error Message %ASA-7-715057: Auto-detected a NAT device with NAT-Traversal. Ignoring IPsec-over-UDP configuration. Explanation IPsec-over-UDP mode configuration information will not be exchanged because NAT-Traversal was detected. Recommended Action None required.
715058
Error Message %ASA-7-715058: NAT-Discovery payloads missing. Aborting NAT-Traversal. Explanation The remote end did not provide NAT-Discovery payloads required for NAT-Traversal after exchanging NAT-Traversal VIDs. At least two NAT-Discovery payloads must be received. Recommended Action This may indicate a nonconforming NAT-T implementation. If the offending peer is a Cisco product and the problem persists, contact the Cisco TAC. If the offending peer is not a Cisco product, then contact the manufacturer support team.
1-404
Chapter 1
715059
Error Message %ASA-7-715059: Proposing/Selecting only UDP-Encapsulated-Tunnel and UDP-Encapsulated-Transport modes defined by NAT-Traversal Explanation You need to use these modes instead of the usual transport and tunnel modes defined in the SA to successfully negotiate NAT-Traversal. Recommended Action None required.
715060
Error Message %ASA-7-715060: Dropped received IKE fragment. Reason: reason Explanation The reason for dropping the fragment appears. Recommended Action The recommended action depends on the drop reason, but might indicate a problem with an intervening NAT device or a nonconforming peer.
715061
Error Message %ASA-7-715061: Rcv'd fragment from a new fragmentation set. Deleting any old fragments. Explanation A resend of the same packet occurred, but fragmented to a different MTU, or another packet altogether. Recommended Action None required.
715062
Error Message %ASA-7-715062: Error assembling fragments! Fragment numbers are non-continuous. Explanation There is a gap in fragment numbers. Recommended Action This might indicate a network problem. If the condition persists and results in dropped tunnels or prevents certain peers from negotiating with the ASA, contact the Cisco TAC.
1-405
Syslog Messages
715063
Error Message %ASA-7-715063: Successfully assembled an encrypted pkt from rcv'd fragments! Explanation Assembly for a fragmented packet that was received was successful. Recommended Action None required.
715064
Error Message %ASA-7-715064 -- IKE Peer included IKE fragmentation capability flags: Main Mode: true/false Aggressive Mode: true/false Explanation The peer supports IKE fragmentation based on the information provided in the message. Recommended Action None required.
715065
Error Message %ASA-7-715065: IKE state_machine subtype FSM error history (struct data_structure_address) state, event: state/event pairs Explanation A Phase 1 error occurred and the state, event history pairs will be displayed in reverse
chronological order.
Recommended Action Most of these errors are benign. If the problem persists, contact the Cisco TAC.
715066
Error Message %ASA-7-715066: Can't load an IPsec SA! The corresponding IKE SA contains an invalid logical ID. Explanation The logical ID in the IKE SA is NULL. The Phase II negotiation will be torn down. Recommended Action An internal error has occurred. If the problem persists, contact the Cisco TAC.
1-406
Chapter 1
715067
Error Message %ASA-7-715067: QM IsRekeyed: existing sa from different peer, rejecting new sa Explanation The LAN-TO-LAN SA that is being established already exists, that is, an SA with the same remote network, but is sourced from a different peer. This new SA will be deleted, because this is not a legal configuration. Recommended Action Check the LAN-TO-LAN configuration on all associated peers. Specifically,
multiple peers should not be sharing private networks.
715068
Error Message %ASA-7-715068: QM IsRekeyed: duplicate sa found by address, deleting old sa Explanation The remote access SA that is being established already exists, that is, an SA with the same remote network, but is sourced from a different peer. The old SA will be deleted, because the peer may have changed its IP address. Recommended Action This may be a benign condition, especially if a client tunnel was terminated
abruptly. If the problem persists, contact the Cisco TAC.
715069
Error Message %ASA-7-715069: Invalid ESP SPI size of SPI_size Explanation The ASA received an IPsec SA proposal with an invalid ESP SPI size. This proposal will be skipped. Recommended Action Generally, this is a benign condition but might indicate that a peer may be nonconforming. If the problem persists, contact the Cisco TAC.
715070
Error Message %ASA-7-715070: Invalid IPComp SPI size of SPI_size Explanation The ASA received an IPsec SA proposal with an invalid IPComp SPI size. This proposal will be skipped. Recommended Action Generally, this is a benign condition but might indicate that a peer is
nonconforming. If the problem persists, contact the Cisco TAC.
1-407
Syslog Messages
715071
Error Message %ASA-7-715071: AH proposal not supported Explanation The IPsec AH proposal is not supported. This proposal will be skipped. Recommended Action None required.
715072
Error Message %ASA-7-715072: Received proposal with unknown protocol ID protocol_ID Explanation The ASA received an IPsec SA proposal with an unknown protocol ID. This proposal will be skipped. Recommended Action Generally, this is a benign condition, but might indicate that a peer is nonconforming. If the problem persists, contact the Cisco TAC.
715074
Error Message %ASA-7-715074: Could not retrieve authentication attributes for peer IP_address Explanation The ASA cannot get authorization information for the remote user. Recommended Action Make sure that authentication and authorization settings have been configured
correctly. If the problem persists, contact the Cisco TAC.
715075
Error Message %ASA-7-715075: Group = group_name, IP = IP_address Received keep-alive of type message_type (seq number number) Explanation This message is paired with DPD R-U-THERE message 715036, which logs the DPD
sending messages.

group_nameThe VPN group name of the peer IP_addressIP address of the VPN peer message_typeThe message type (DPD R-U-THERE or DPD R-U-THERE-ACK) numberThe DPD sequence number Received peer sending DPD R-U-THERE message Received peer reply DPD R-U-THERE-ACK message
Two possible cases:

1-408
Chapter 1
Be aware of the following:
The DPD R-U-THERE message is received and its sequence number matches the outgoing DPD reply messages. If the ASA sends a DPD R-U-THERE-ACK message without first receiving a DPD R-U-THERE message from the peer, it is likely experiencing a security breech.
The received DPD R-U-THERE-ACK message's sequence number is matched with previously sent DPD messages. If the ASA did not receive a DPD R-U-THERE-ACK message within a reasonable amount of time after sending a DPD R-U-THERE message to the peer, the tunnel is most likely down.
715076
Error Message %ASA-7-715076: Computing hash for ISAKMP Explanation IKE computed various hash values.
This object will be prepended as follows: Group = groupname, Username = username, IP = ip_address...
715077
Error Message %ASA-7-715077: Pitcher: msg string, spi spi Explanation Various messages have been sent to IKE.
msg_string can be one of the following:

Received a key acquire message Received SPI for nonexistent SA Received key delete msg Received KEY_UPDATE Received KEY_REKEY_IB Received KEY_REKEY_OB Received KEY_SA_ACTIVE Could not find IKE SA to activate IPSEC (OB) Could not find IKE SA to rekey IPSEC (OB) KEY_SA_ACTIVE no centry found KEY_ADD centry not found KEY_UPDATE centry not found
1-409
Syslog Messages
This object will be prepended as follows: Group = groupname, Username = username, IP = ip_address,...
715080
Error Message %ASA-7-715080: VPN: Starting P2 rekey timer: 28800 seconds. Explanation An IKE rekey timer has started. Recommended Action None required.
716001
Error Message %ASA-6-716001: Group group User user IP ip WebVPN session started. Explanation The WebVPN session has started for the user in this group at the specified IP address.
When the user logs in via the WebVPN login page, the WebVPN session starts.
716002
Error Message %ASA-6-716002: Group GroupPolicy User username IP ip WebVPN session terminated: User requested. Explanation The WebVPN session has been terminated by a user request. Possible reasons include:
Lost carrier Lost service Idle timeout Max time exceeded Administrator reset Administrator reboot Administrator shutdown Port error NAS error NAS request NAS reboot Port unneeded
1-410
Chapter 1
Port preempted. This reason indicates that the allowed number of simultaneous (same user) logins has been exceeded. To resolve this problem, increase the number of simultaneous logins or have users only log in once with a given username and password. Port suspended Service unavailable Callback User error Host requested Bandwidth management error ACL parse error VPN simultaneous logins limit specified in the group policy Unknown
Recommended Action Unless the reason indicates a problem, then no action is required.
716003
Error Message %ASA-6-716003: Group group User user IP ip WebVPN access GRANTED: url Explanation The WebVPN user in this group at the specified IP address has been granted access to
this URL. The user access to various locations can be controlled using WebVPN-specific ACLs.
716004
Error Message %ASA-6-716004: Group group User user WebVPN access DENIED to specified location: url Explanation The WebVPN user in this group has been denied access to this URL. The WebVPN user
access to various locations can be controlled using WebVPN-specific ACLs. In this case, a particular entry is denying access to this URL.
716005
Error Message %ASA-6-716005: Group group User user WebVPN ACL Parse Error: reason Explanation The ACL for the WebVPN user in the specified group failed to parse correctly. Recommended Action Correct the WebVPN ACL.
1-411
Syslog Messages
716006
Error Message %ASA-6-716006: Group name User user WebVPN session terminated. Idle timeout. Explanation The WebVPN session was not created for the user in the specified group because the
VPN tunnel protocol is not set to WebVPN.

716007
Error Message %ASA-4-716007: Group group User user WebVPN Unable to create session. Explanation The WebVPN session was not created for the user in the specified group because of
resource issues. For example, the user may have reached the maximum login limit.
716008
Error Message %ASA-7-716008: WebVPN ACL: action Explanation The WebVPN ACL has begun performing an action (for example, begin parsing). Recommended Action None required.
716009
Error Message %ASA-6-716009: Group group User user WebVPN session not allowed. WebVPN ACL parse error. Explanation The WebVPN session for the specified user in this group is not allowed because the
associated ACL did not parse. The user will not be allowed to log in via WebVPN until this error has been corrected.
Recommended Action Correct the WebVPN ACL.
1-412
Chapter 1
716010
Error Message %ASA-7-716010: Group group User user Browse network. Explanation The WebVPN user in the specified group browsed the network. Recommended Action None required.
716011
Error Message %ASA-7-716011: Group group User user Browse domain domain. Explanation The WebVPN specified user in this group browsed the specified domain. Recommended Action None required.
716012
Error Message %ASA-7-716012: Group group User user Browse directory directory. Explanation The specified WebVPN user browsed the specified directory. Recommended Action None required.
716013
Error Message %ASA-7-716013: Group group User user Close file filename. Explanation The specified WebVPN user closed the specified file. Recommended Action None required.
716014
Error Message %ASA-7-716014: Group group User user View file filename. Explanation The specified WebVPN user viewed the specified file. Recommended Action None required.
1-413
Syslog Messages
716015
Error Message %ASA-7-716015: Group group User user Remove file filename. Explanation The WebVPN user in the specified group removed the specified file. Recommended Action None required.
716016
Error Message %ASA-7-716016: Group group User user Rename file old_filename to new_filename. Explanation The specified WebVPN user renamed the specified file. Recommended Action None required.
716017
Error Message %ASA-7-716017: Group group User user Modify file filename. Explanation The specified WebVPN user modified the specified file. Recommended Action None required.
716018
Error Message %ASA-7-716018: Group group User user Create file filename. Explanation The specified WebVPN user created the specified file. Recommended Action None required.
716019
Error Message %ASA-7-716019: Group group User user Create directory directory. Explanation The specified WebVPN user created the specified directory. Recommended Action None required.
1-414
Chapter 1
716020
Error Message %ASA-7-716020: Group group User user Remove directory directory. Explanation The specified WebVPN user removed the specified directory. Recommended Action None required.
716021
Error Message %ASA-7-716021: File access DENIED, filename. Explanation The specified WebVPN user was denied access to the specified file. Recommended Action None required.
716022
Error Message %ASA-4-716022: Unable to connect to proxy server reason. Explanation The WebVPN HTTP/HTTPS redirect failed for the specified reason. Recommended Action Check the HTTP/HTTPS proxy configuration.
716023
Error Message %ASA-4-716023: Group name User user Session could not be established: session limit of maximum_sessions reached. Explanation The user session cannot be established because the current number of sessions exceeds the maximum session load. Recommended Action Increase the configured limit, if possible, to create a load-balanced cluster.
1-415
Syslog Messages
716024
Error Message %ASA-7-716024: Group name User user Unable to browse the network.Error: description Explanation The user was unable to browse the Windows network using the CIFS protocol, as
indicated by the description. For example, Unable to contact necessary server indicates that the remote server is unavailable or unreachable. This might be a transient condition or may require further troubleshooting.
Recommended Action Check the connectivity between the WebVPN device and the server being accessed by the CIFS protocol. Also check the NetBIOS name server configuration on the ASA.
716025
Error Message %ASA-7-716025: Group name User user Unable to browse domain domain. Error: description Explanation The user was unable to browse the remote domain using the CIFS protocol. Recommended Action Check the connectivity between the WebVPN device and the server being accessed by the CIFS protocol. Check the NetBIOS name server configuration on the ASA.
716026
Error Message %ASA-7-716026: Group name User user Unable to browse directory directory. Error: description Explanation The user was unable to browse the remote directory using the CIFS protocol. Recommended Action Check the connectivity between the WebVPN device and the server being accessed by the CIFS protocol. Also check the NetBIOS name server configuration on the ASA.
716027
Error Message %ASA-7-716027: Group name User user Unable to view file filename. Error: description Explanation The user was unable to view the remote file using the CIFS protocol. Recommended Action Check the connectivity between the WebVPN device and the server being accessed by the CIFS protocol. Also check the NetBIOS name server configuration on the ASA.
1-416
Chapter 1
716028
Error Message %ASA-7-716028: Group name User user Unable to remove file filename. Error: description Explanation The user was unable to remove the remote file using the CIFS protocol, probably caused
by a lack of file permissions.

Recommended Action Check the connectivity between the WebVPN device and the server being accessed by the CIFS protocol. Also check the NetBIOS name server configuration on the ASA and the file permissions.
716029
Error Message %ASA-7-716029: Group name User user Unable to rename file filename. Error: description Explanation The user was unable to rename the remote file using the CIFS protocol, probably caused
by lack of file permissions.

716030
Error Message %ASA-7-716030: Group name User user Unable to modify file filename. Error: description Explanation A problem occurred when a user attempted to modify an existing file using the CIFS
protocol, probably caused by a lack of file permissions.

1-417
Syslog Messages
716031
Error Message %ASA-7-716031: Group name User user Unable to create file filename. Error: description Explanation A problem occurred when a user attempted to create a file using the CIFS protocol,
probably caused by a file permissions problem.

716032
Error Message %ASA-7-716032: Group name User user Unable to create folder folder. Error: description Explanation A problem occurred when a user attempted to create a folder using the CIFS protocol,
probably caused by a file permissions problem.

716033
Error Message %ASA-7-716033: Group name User user Unable to remove folder folder. Error: description Explanation A problem occurred when a user of the CIFS protocol attempted to remove a folder,
which probably occurred because of a permissions problem or a problem communicating with the server on which the file resides.
Recommended Action Check the connectivity between the WebVPN device and the server being accessed by the CIFS protocol. Also check the NetBIOS name server configuration on the ASA.
716034
Error Message %ASA-7-716034: Group name User user Unable to write to file filename. Explanation A problem occurred when a user attempted to write to a file using the CIFS protocol,
probably caused by a permissions problem or a problem communicating with the server on which the file resides.
1-418
Chapter 1
716035
Error Message %ASA-7-716035: Group name User user Unable to read file filename. Explanation A problem occurred when a user of the CIFS protocol tried to read a file, probably
caused by a file permissions problem.

Recommended Action Check the file permissions.
716036
Error Message %ASA-7-716036: Group name User user File Access: User user logged into the server server. Explanation A user successfully logged into the server using the CIFS protocol Recommended Action None required.
716037
Error Message %ASA-7-716037: Group name User user File Access: User user failed to login into the server server. Explanation A user attempted to log in to a server using the CIFS protocol, but was unsuccessful. Recommended Action Verify that the user entered the correct username and password.
716038
Error Message %ASA-6-716038: Group group User user IP ip Authentication: successful, Session Type: WebVPN. Explanation Before a WebVPN session can start, the user must be authenticated successfully by a
local or remote server (for example, RADIUS or TACACS+).

1-419
Syslog Messages
716039
Error Message %ASA-6-716039: Authentication: rejected, group = name user = user, Session Type: %s Explanation Before a WebVPN session starts, the user must be authenticated successfully by a local
or remote server (for example, RADIUS or TACACS+). In this case, the user credentials (username and password) either did not match, or the user does not have permission to start a WebVPN session.
%sThe session type, which can be either WebVPN or admin
Recommended Action Verify the user credentials on the local or remote server and that WebVPN is configured for the user.
716040
Error Message %ASA-6-716040: Reboot pending, new sessions disabled. Denied user login. Explanation A user was unable to log in to WebVPN because the ASA is in the process of rebooting.
userThe session user
716041
Error Message %ASA-6-716041: access-list acl_ID action url url hit_cnt count Explanation The WebVPN URL named acl_ID has been hit count times for location url, whose
action is permitted or denied.

acl_IDThe WebVPN URL ACL countThe number of times the URL was accessed urlThe URL that was accessed actionThe user action
1-420
Chapter 1
716042
Error Message %ASA-6-716042: access-list acl_ID action tcp source_interface/source_address (source_port) dest_interface/dest_address(dest_port) hit-cnt count Explanation The WebVPN TCP named acl_ID has been hit count times for packet received on the
source interface source_interface/source_address and source port source_port forwarded to dest_interface/dest_address destination dest_port, whose action is permitted or denied.

countThe number of times the ACL was accessed source_interfaceThe source interface source_addressThe source IP address source_portThe source port dest_interfaceThe destination interface dest_addressThe destination IP address actionThe user action
716043
Error Message %ASA-6-716043 Group group-name, User user-name, IP IP_address: WebVPN Port Forwarding Java applet started. Created new hosts file mappings. Explanation The user has launched a TCP port-forwarding applet from a WebVPN session.
group-nameGroup name associated with the session user-nameUsername associated with the session IP_addressSource IP address associated with the session
716044
Error Message %ASA-4-716044: Group group-name User user-name IP IP_address AAA parameter param-name value param-value out of range. Explanation The given parameter has a bad value.
group-nameThe name of the group user-nameThe name of the user IP_addressThe IP address param-nameThe name of the parameter
1-421
Syslog Messages
param-valueThe value of the parameter
Recommended Action Modify the configuration to correct the indicated parameter. If the parameter is
vlan or nac-settings, verify that it is correctly configured on the AAA server and the ASA.
716045
Error Message %ASA-4-716045: Group group-name User user-name IP IP_address AAA parameter param-name value invalid. Explanation The given parameter has a bad value. The value is not shown because it might be very
long.

group-nameThe name of the group user-nameThe name of the user IP_addressThe IP address param-nameThe name of the parameter
Recommended Action Modify the configuration to correct the indicated parameter.
716046
Error Message %ASA-4-716046: Group group-name User user-name IP IP_address User ACL access-list-name from AAA doesn't exist on the device, terminating connection. Explanation The specified ACL was not found on the ASA.
group-nameThe name of the group user-nameThe name of the user IP_addressThe IP address access-list-nameThe name of the ACL
Recommended Action Modify the configuration to add the specified ACL or to correct the ACL name.
716047
Error Message %ASA-4-716047: Group group-name User user-name IP IP_address User ACL access-list-name from AAA ignored, AV-PAIR ACL used instead. Explanation The specified ACL was not used because a Cisco AV-PAIR ACL was used.
group-nameThe name of the group user-nameThe name of the user IP_addressThe IP address
1-422
Chapter 1
access-list-nameThe name of the ACL
Recommended Action Determine the correct ACL to use and correct the configuration.
716048
Error Message %ASA-4-716048: Group group-name User user-name IP IP_address No memory to parse ACL. Explanation There was not enough memory to parse the ACL.
Recommended Action Purchase more memory, upgrade the ASA, or reduce the load on it.
716049
Error Message %ASA-6-716049: Group group-name User user-name IP IP_address Empty SVC ACL. Explanation The ACL to be used by the client was empty.
Recommended Action Determine the correct ACL to use and modify the configuration.
716050
Error Message %ASA-6-716050: Error adding to ACL: ace_command_line Explanation The ACL entry had a syntax error.
ace_command_line The ACL entry that is causing the error
Recommended Action Correct the downloadable ACL configuration.
1-423
Syslog Messages
716051
Error Message %ASA-6-716051: Group group-name User user-name IP IP_address Error adding dynamic ACL for user. Explanation There is not enough memory to perform the action.
Recommended Action Purchase more memory, upgrade the ASA, or reduce the load on it.
716052
Error Message %ASA-4-716052: Group group-name User user-name IP IP_address Pending session terminated. Explanation A user did not complete login and the pending session was terminated. This may be due
to an SVC that was unable to connect.

Recommended Action Check the user PC for SVC compatibility.
716053
Error Message %ASA-5-716053: SSO Server added: name: name Type: type Explanation The SSO server name of the specified type has been configured.
nameThe name of the server typeThe type of the server (the only server type is SiteMinder)
716054
Error Message %ASA-5-716054: SSO Server deleted: name: name Type: type Explanation The SSO server name of the specified type has been removed from the configuration.
nameThe name of the server
1-424
Chapter 1
typeThe type of server (the only server type is SiteMinder)
716055
Error Message %ASA-6-716055: Group group-name User user-name IP IP_address Authentication to SSO server name: name type type succeeded Explanation The WebVPN user has been successfully authenticated to the SSO server.
group-nameThe group name user-nameThe username IP_addressThe IP address of the server nameThe name of the server typeThe type of server (the only server type is SiteMinder)
716056
Error Message %ASA-3-716056: Group group-name User user-name IP IP_address Authentication to SSO server name: name type type failed reason: reason Explanation The WebVPN user failed to authenticate to the SSO server.
group-nameThe group name user-nameThe username IP_addressThe IP address of the server nameThe name of the server typeThe type of server (the only server type is SiteMinder) reasonThe reason for the authentication failure
Recommended Action Either the user or the ASA administrator needs to correct the problem,
depending on the reason for the failure.
716057
Error Message %ASA-3-716057: Group group User user IP ip Session terminated, no type license available. Explanation A user has attempted to connect to the ASA using a client that is not licensed. This
message may also occur if a temporary license has expired.
groupThe group policy that the user logged in with
1-425
Syslog Messages
userThe name of the user IPThe IP address of the user typeThe type of license requested, which can be one of the following: - AnyConnect Mobile - LinkSys Phone - The type of license requested by the client (if other than the AnyConnect Mobile or LinkSys Phone) - Unknown
Recommended Action A permanent license with the appropriate feature should be purchased and
installed.
716058
Error Message %ASA-6-716058: Group group User user IP ip AnyConnect session lost connection. Waiting to resume. Explanation The SSL tunnel was dropped and the AnyConnect session enters the inactive state,
which can be caused by a hibernating host, a standby host, or a loss of network connectivity.

groupThe tunnel group name associated with the AnyConnect session userThe name of the user associated with the session ipThe source IP address of the session
716059
Error Message %ASA-6-716059: Group group User user IP ip AnyConnect session resumed. Connection from ip2. Explanation An AnyConnect session resumed from the inactive state.
groupThe tunnel group name associated with the AnyConnect session userThe name of the user associated with the session ipThe source IP address of the session ip2The source IP address of the host on which the session is resumed
1-426
Chapter 1
716060
Error Message %ASA-6-716060: Group group User user IP ip Terminated AnyConnect session in inactive state to accept a new connection. License limit reached. Explanation An AnyConnect session in the inactive state was logged out to allow a new incoming
SSL VPN (AnyConnect or clientless) connection.

groupThe tunnel group name associated with the AnyConnect session userThe name of the user associated with the session ipThe source IP address of the session
716061
Error Message %ASA-3-716061: Group DfltGrpPolicy User user IP ip addr IPv6 User Filter tempipv6 configured for AnyConnect. This setting has been deprecated, terminating connection Explanation The IPv6 VPN filter has been deprecated and if it is configured instead of a unified filter
for IPv6 traffic access control, the connection will be terminated.

Recommended Action Configure a unified filter with IPv6 entries to control IPv6 traffic for the user.
716500
Error Message %ASA-2-716500: internal error in: function: Fiber library cannot locate AK47 instance Explanation The fiber library cannot locate the application kernel layer 4 to 7 instance. Recommended Action To determine the cause of the problem, contact the Cisco TAC.
716501
Error Message %ASA-2-716501: internal error in: function: Fiber library cannot attach AK47 instance Explanation The fiber library cannot attach the application kernel layer 4 to 7 instance. Recommended Action To determine the cause of the problem, contact the Cisco TAC.
1-427
Syslog Messages
716502
Error Message %ASA-2-716502: internal error in: function: Fiber library cannot allocate default arena Explanation The fiber library cannot allocate the default arena. Recommended Action To determine the cause of the problem, contact the Cisco TAC.
716503
Error Message %ASA-2-716503: internal error in: function: Fiber library cannot allocate fiber descriptors pool Explanation The fiber library cannot allocate the fiber descriptors pool. Recommended Action To determine the cause of the problem, contact the Cisco TAC.
716504
Error Message %ASA-2-716504: internal error in: function: Fiber library cannot allocate fiber stacks pool Explanation The fiber library cannot allocate the fiber stack pool. Recommended Action To determine the cause of the problem, contact the Cisco TAC.
716505
Error Message %ASA-2-716505: internal error in: function: Fiber has joined fiber in unfinished state Explanation The fiber has joined fiber in an unfinished state. Recommended Action To determine the cause of the problem, contact the Cisco TAC.
716506
Error Message %ASA-2-716506: UNICORN_SYSLOGID_JOINED_UNEXPECTED_FIBER Explanation An internal fiber library was generated. Recommended Action Contact the Cisco TAC.
1-428
Chapter 1
716507
Error Message %ASA-1-716507: Fiber scheduler has reached unreachable code. Cannot continue, terminating. Explanation The ASA has experienced an unexpected error and has recovered. Recommended Action Check for high CPU usage or CPU hogs, and potential memory leaks. If the problem persists, contact the Cisco TAC.
716508
Error Message %ASA-1-716508: internal error in: function: Fiber scheduler is scheduling rotten fiber. Cannot continuing terminating Explanation The fiber scheduler is scheduling rotten fiber, so it cannot continue terminating. Recommended Action To determine the cause of the problem, contact the Cisco TAC.
716509
Error Message %ASA-1-716509:internal error in: function: Fiber scheduler is scheduling alien fiber. Cannot continue terminating Explanation The fiber scheduler is scheduling alien fiber, so it cannot continue terminating. Recommended Action To determine the cause of the problem, contact the Cisco TAC.
716510
Error Message %ASA-1-716510:internal error in: function: Fiber scheduler is scheduling finished fiber. Cannot continue terminating Explanation The fiber scheduler is scheduling finished fiber, so it cannot continue terminating. Recommended Action To determine the cause of the problem, contact the Cisco TAC.
1-429
Syslog Messages
716512
Error Message %ASA-2-716512:internal error in: function: Fiber has joined fiber waited upon by someone else Explanation The fiber has joined fiber that is waited upon by someone else. Recommended Action To determine the cause of the problem, contact the Cisco TAC.
716513
Error Message %ASA-2-716513: internal error in: function: Fiber in callback blocked on other channel Explanation The fiber in the callback was blocked on the other channel. Recommended Action To determine the cause of the problem, contact the Cisco TAC.
716515
Error Message %ASA-2-716515:internal error in: function: OCCAM failed to allocate memory for AK47 instance Explanation The OCCAM failed to allocate memory for the AK47 instance. Recommended Action To determine the cause of the problem, contact the Cisco TAC.
716516
Error Message %ASA-1-716516: internal error in: function: OCCAM has corrupted ROL array. Cannot continue terminating Explanation The OCCAM has a corrupted ROL array, so it cannot continue terminating. Recommended Action To determine the cause of the problem, contact the Cisco TAC.
716517
Error Message %ASA-2-716517: internal error in: function: OCCAM cached block has no associated arena Explanation The OCCAM cached block has no associated arena. Recommended Action To determine the cause of the problem, contact the Cisco TAC.
1-430
Chapter 1
716518
Error Message %ASA-2-716518: internal error in: function: OCCAM pool has no associated arena Explanation The OCCAM pool has no associated arena. Recommended Action To determine the cause of the problem, contact the Cisco TAC.
716519
Error Message %ASA-1-716519: internal error in: function: OCCAM has corrupted pool list. Cannot continue terminating Explanation The OCCAM has a corrupted pool list, so it cannot continue terminating. Recommended Action To determine the cause of the problem, contact the Cisco TAC.
716520
Error Message %ASA-2-716520:internal error in: function: OCCAM pool has no block list Explanation The OCCAM pool has no block list. Recommended Action To determine the cause of the problem, contact the Cisco TAC.
716521
Error Message %ASA-2-716521: internal error in: function: OCCAM no realloc allowed in named pool Explanation The OCCAM did not allow reallocation in the named pool. Recommended Action To determine the cause of the problem, contact the Cisco TAC.
716522
Error Message %ASA-2-716522: internal error in: function: OCCAM corrupted standalone block Explanation The OCCAM has a corrupted standalone block. Recommended Action To determine the cause of the problem, contact the Cisco TAC.
1-431
Syslog Messages
716525
Error Message %ASA-2-716525: UNICORN_SYSLOGID_SAL_CLOSE_PRIVDATA_CHANGED Explanation An internal SAL error has occurred. Recommended Action Contact the Cisco TAC.
716526
Error Message %ASA-2-716526: UNICORN_SYSLOGID_PERM_STORAGE_SERVER_LOAD_FAIL Explanation A failure in the mounting of the permanent storage server directory occurred. Recommended Action Contact the Cisco TAC.
716527
Error Message %ASA-2-716527: UNICORN_SYSLOGID_PERM_STORAGE_SERVER_STORE_FAIL Explanation A failure in the mounting of the permanent storage file occurred. Recommended Action Contact the Cisco TAC.
716528
Error Message %ASA-1-716528: Unexpected fiber scheduler error; possible out-of-memory condition Explanation The ASA has experienced an unexpected error and has recovered. Recommended Action Check for high CPU usage or CPU hogs, and potential memory leaks. If the problem persists, contact the Cisco TAC.
716600
Error Message %ASA-3-716600: Rejected size-recv KB Hostscan data from IP src-ip. Hostscan results exceed default | configured limit of size-conf KB. Explanation When the size of the received Hostscan data exceeds the limit configured on the ASA,
the data is discarded.

size-recvSize of received Hostscan data in kilobytes src-ipSource IP address
1-432
Chapter 1
default | configuredKeyword specifying whether the value of the Hostscan data limit is the default or configured by the administrator size-confConfigured upper limit on the size of the Hostscan data that the ASA accepts from clients
Recommended Action Contact Cisco TAC to increase the upper limit on the size of Hostscan data that the ASA accepts from clients.
716601
Error Message %ASA-3-716601: Rejected size-recv KB Hostscan data from IP src-ip. System-wide limit on the amount of Hostscan data stored on ASA exceeds the limit of data-max KB. Explanation When the amount of Hostscan data stored on the ASA exceeds the limit, new Hostscan
results are rejected.

size-recvSize of received Hostscan data in kilobytes src-ipSource IP address data-maxLimit on the amount of Hostscan results to be stored by the ASA in kilobytes
Recommended Action Contact Cisco TAC to change the limit on stored Hostscan data.
716602
Error Message %ASA-3-716602: Memory allocation error. Rejected size-recv KB Hostscan data from IP src-ip. Explanation An error occurred while memory was being allocated for Hostscan data.
Recommended Action Set the Hostscan limit to the default value if it is configured. If the problem persists, contact Cisco TAC.
716603
Error Message %ASA-7-716603: Received size-recv KB Hostscan data from IP src-ip. Explanation The Hostscan data of a specified size was successfully received.
1-433
Syslog Messages
717001
Error Message %ASA-3-717001: Querying keypair failed. Explanation A required keypair was not found during an enrollment request. Recommended Action Verify that a valid keypair exists in the trustpoint configuration, then resubmit
the enrollment request.
717002
Error Message %ASA-3-717002: Certificate enrollment failed for trustpoint trustpoint_name. Reason: reason_string. Explanation An enrollment request for this trustpoint has failed.
trustpoint nameTrustpoint name that the enrollment request was for reason_stringThe reason the enrollment request failed
Recommended Action Check the CA server for the failure reason.
717003
Error Message %ASA-6-717003: Certificate received from Certificate Authority for trustpoint trustpoint_name. Explanation A certificate was successfully received from the CA for this trustpoint.
trustpoint_nameTrustpoint name
Recommended Action None required
717004
Error Message %ASA-6-717004: PKCS #12 export failed for trustpoint trustpoint_name. Explanation The trustpoint failed to export, because of one of the following: only a CA certificate
exists, and an identity certificate does not exist for the trustpoint, or a required keypair is missing.
Recommended Action Make sure that required certificates and keypairs are present for the given
trustpoint.
1-434
Chapter 1
717005
Error Message %ASA-6-717005: PKCS #12 export succeeded for trustpoint trustpoint_name. Explanation The trustpoint was successfully exported.
717006
Error Message %ASA-6-717006: PKCS #12 import failed for trustpoint trustpoint_name. Explanation Import of the requested trustpoint failed to be processed.
Recommended Action Verify the integrity of the imported data. Then make sure that the entire pkcs12
record is correctly pasted, and reimport the data.
717007
Error Message %ASA-6-717007: PKCS #12 import succeeded for trustpoint trustpoint_name. Explanation Import of the requested trustpoint was successfully completed.
717008
Error Message %ASA-2-717008: Insufficient memory to process_requiring_memory. Explanation An internal error occurred while attempting to allocate memory for the process that reqires memory. Other processes may experience problems allocating memory and prevent further processing.
process_requiring_memoryThe specified process that requires memoryr
Recommended Action Collect memory statistics and logs for further debugging and reload the ASA.
1-435
Syslog Messages
717009
Error Message %ASA-3-717009: Certificate validation failed. Reason: reason_string. Explanation A certificate validation failed, which might be caused by a validation attempt of a
revoked certificate, invalid certificate attributes, or configuration issues.
reason_stringThe reason that the certificate validation failed
Recommended Action Make sure the configuration has a valid trustpoint configured for validation if
the reason indicates that no suitable trustpoints were found. Check the ASA time to ensure that it is accurate relative to the certificate authority time. Check the reason for the failure and correct any issues that are indicated.
717010
Error Message %ASA-3-717010: CRL polling failed for trustpoint trustpoint_name. Explanation .CRL polling has failed and may cause connections to be denied if CRL checking is
required.
trustpoint_nameThe name of the trustpoint that requested the CRL
Recommended Action Verify that connectivity exists with the configured CRL distribution point and
make sure that manual CRL retrieval also functions correctly.
717011
Error Message %ASA-2-717011: Unexpected event event event_ID Explanation An event that is not expected under normal conditions has occurred. Recommended Action If the problem persists, contact the Cisco TAC.
717012
Error Message %ASA-3-717012: Failed to refresh CRL cache entry from the server for trustpoint trustpoint_name at time_of_failure Explanation An attempt to refresh a cached CRL entry has failed for the specified trustpoint at the indicated time of failure. This may result in obsolete CRLs on the ASA, which may cause connections that require a valid CRL to be denied.
trustpoint_nameThe name of the trustpoint
1-436
Chapter 1
time_of_failureThe time of failure
Recommended Action Check connectivity issues to the server, such as a downed network or server.
Try to retrieve the CRL manually using the crypto ca crl retrieve command.
717013
Error Message %ASA-5-717013: Removing a cached CRL to accommodate an incoming CRL. Issuer: issuer Explanation When the device is configured to authenticate IPsec tunnels using digital certificates,
CRLs may be cached in memory to avoid requiring a CRL download during each connection. If the cache fills to the point where an incoming CRL cannot be accommodated, older CRLs will be removed until the required space is made available. This message is generated for each purged CRL.
issuerThe name of the device that removes cached CRLs
717014
Error Message %ASA-5-717014: Unable to cache a CRL received from CDP due to size limitations (CRL size = size, available cache space = space) Explanation When the device is configured to authenticate IPsec tunnels using digital certificates,
CRLs may be cached in memory to avoid requiring a CRL download during each connection. This message is generated if a received CRL is too large to fit in the cache. Large CRLs are still supported even though they are not cached. This means that the CRL will be downloaded with each IPsec connection, which may affect performance during IPsec connection bursts.
717015
Error Message %ASA-3-717015: CRL received from issuer is too large to process (CRL size = crl_size, maximum CRL size = max_crl_size) Explanation An IPsec connection caused a CRL that is larger than the maximum permitted CRL size
to be downloaded. This error condition causes the connection to fail. This message is rate limited to one message every 10 seconds.
Recommended Action Scalability is perhaps the most significant drawback to the CRL method of revocation checking. To solve this problem, the only options are to investigate a CA-based solution to reduce the CRL size or configure the ASA not to require CRL validation.
1-437
Syslog Messages
717016
Error Message %ASA-6-717016: Removing expired CRL from the CRL cache. Issuer: issuer Explanation When the ASA is configured to authenticate IPsec tunnels using digital certificates, CRLs may be cached in memory to avoid requiring a CRL download during each connection. This message is generated when either the CA specified expiration time or the configured cache time has lapsed and the CRL is removed from the cache. Recommended Action None required.
717017
Error Message %ASA-3-717017: Failed to query CA certificate for trustpoint trustpoint_name from enrollment_url Explanation An error occurred when an attempt was made to authenticate a trustpoint by requesting
a CA certificate from a certificate authority.

Recommended Action Make sure that an enrollment URL is configured with this trustpoint, ensure
connectivity with the CA server, then retry the request.
717018
Error Message %ASA-3-717018: CRL received from issuer has too many entries to process (number of entries = number_of_entries, maximum number allowed = max_allowed) Explanation An IPsec connection caused a CRL that includes more revocation entries than can be
supported to be downloaded. This is an error condition that will cause the connection to fail. This message is rate limited to one message every 10 seconds.

issuerThe X.500 name of the CRLs issuer number_of_entriesThe number of revocation entries in the received CRL max_allowedThe maximum number of CRL entries that the ASA supports
Recommended Action Scalability is perhaps the most significant drawback to the CRL method of revocation checking. The only options to solve this problem are to investigate a CA-based solution to reduce the CRL size or configure the ASA not to require CRL validation.
1-438
Chapter 1
717019
Error Message %ASA-3-717019: Failed to insert CRL for trustpoint trustpoint_name. Reason: failure_reason. Explanation A CRL is retrieved, but found to be invalid and cannot be inserted into the cache because
of the failure_reason.

trustpoint_nameThe name of the trustpoint that requested the CRL failure_reasonThe reason that the CRL failed to be inserted into cache
Recommended Action Make sure that the current ASA time is correct relative to the CA time. If the NextUpdate field is missing, configure the trustpoint to ignore the NextUpdate field.
717020
Error Message %ASA-3-717020: Failed to install device certificate for trustpoint label. Reason: reason string. Explanation A failure occurred while trying to enroll or import an enrolled certificate into a
trustpoint.

labelLabel of the trustpoint that failed to install the enrolled ASA certificate reason_stringThe reason that the certificate cannot be verified
Recommended Action Use the failure reason to remedy the cause of failure and retry the enrollment. Common failures are due to invalid certificates being imported into the ASA or a mismatch of the public key included in the enrolled certificate with the keypair referenced in the trustpoint.
717021
Error Message %ASA-3-717021: Certificate data could not be verified. Locate Reason: reason_string serial number: serial number, subject name: subject name, key length key length bits. Explanation An attempt to verify the certificate that is identified by the serial number and subject name was unsuccessful for the specified reason. When verifying certificate data using the signature, several errors can occur that should be logged, including invalid key types and unsupported key size.
reason_stringThe reason that the certificate cannot be verified serial numberSerial number of the certificate that is being verified subject nameSubject name included in the certificate that is being verified key lengthThe number of bits in the key used to sign this certificate
Recommended Action Check the specified certificate to ensure that it is valid, that it includes a valid
key type, and that it does not exceed the maximum supported key size.
1-439
Syslog Messages
717022
Error Message %ASA-6-717022: Certificate was successfully validated. certificate_identifiers Explanation The identified certificate was successfully validated.
certificate_identifiersInformation to identify the certificate that was validated successfully, which might include a reason, serial number, subject name, and additional information
717023
Error Message %ASA-3-717023: SSL failed to set device certificate for trustpoint trustpoint name. Reason: reason_string. Explanation A failure occurred while trying to set an ASA certificate for the given trustpoint for authenticating the SSL connection.
trustpoint nameName of the trustpoint for which SSL failed to set an ASA certificate reason_stringReason indicating why the ASA certificate cannot be set
Recommended Action Resolve the issue indicated by the reason reported for the failure by doing the
following:

Make sure that the specified trustpoint is enrolled and has an ASA certificate. Make sure the ASA certificate is valid. Reenroll the trustpoint, if required.
717024
Error Message %ASA-7-717024: Checking CRL from trustpoint: trustpoint name for purpose Explanation A CRL is being retrieved.
trustpoint nameName of the trustpoint for which the CRL is being retrieved purposeReason that the CRL is being retrieved
1-440
Chapter 1
717025
Error Message %ASA-7-717025: Validating certificate chain containing number of certs certificate(s). Explanation A certificate chain is being validated.
number of certsNumber of certificates in the chain
717026
Error Message %ASA-4-717026: Name lookup failed for hostname hostname during PKI operation. Explanation The given hostname cannot be resolved while attempting a PKI operation.
hostnameThe hostname that failed to resolve
Recommended Action Check the configuration and the DNS server entries for the given hostname to make sure that it can be resolved. Then retry the operation.
717027
Error Message %ASA-3-717027: Certificate chain failed validation. reason_string. Explanation A certificate chain cannot be validated.
reason_stringReason for the failure to validate the certificate chain
Recommended Action Resolve the issue noted by the reason and retry the validation attempt by
performing any of the following actions:

Make sure that connectivity to a CA is available if CRL checking is required. Make sure that a trustpoint is authenticated and available for validation. Make sure that the identity certificate within the chain is valid based on the validity dates. Make sure that the certificate is not revoked.
1-441
Syslog Messages
717028
Error Message %ASA-6-717028: Certificate chain was successfully validated additional info. Explanation A certificate chain was successfully validated.
additional infoMore information for how the certificate chain was validated (for example, with warning indicates that a CRL check was not performed)
717029
Error Message %ASA-7-717029: Identified client certificate within certificate chain. serial number: serial_number, subject name: subject_name. Explanation The certificate specified as the client certificate is identified.
serial_numberSerial number of the certificate that is identified as the client certificate subject_nameSubject name included in the certificate that is identified as the client certificate
717030
Error Message %ASA-7-717030: Found a suitable trustpoint trustpoint name to validate certificate. Explanation A suitable or usable trustpoint is found that can be used to validate the certificate.
trustpoint nameTrustpoint that will be used to validate the certificate
717031
Error Message %ASA-4-717031: Failed to find a suitable trustpoint for the issuer: issuer Reason: reason_string Explanation A usable trustpoint cannot be found. During certificate validation, a suitable trustpoint must be available in order to validate a certificate.
issuer Issuer of the certificate that was being validated
1-442
Chapter 1
reason_stringThe reason that a suitable trustpoint cannot be found
Recommended Action Resolve the issue indicated in the reason by checking the configuration to make sure that a trustpoint is configured, authenticated, and enrolled. Also make sure that the configuration allows for specific types of certificates, such as identity certificates.
717033
Error Message %ASA-6-717033: OCSP response status - Successful. Explanation An OCSP status check response was received successfully. Recommended Action None required.
717034
Error Message %ASA-7-717034: No-check extension found in certificate. OCSP check bypassed. Explanation An OCSP responder certificate was received that includes an id-pkix-ocsp-nocheck extension, which allows this certificate to be validated without an OCSP status check. Recommended Action None required.
717035
Error Message %ASA-4-717035: OCSP status is being checked for certificate. certificate_identifier. Explanation The certificate for which an OCSP status check occurs is identified.
certificate_identifierInformation that identifies the certificate being processed by the certificate map rules
1-443
Syslog Messages
717036
Error Message ASA-7-717036: Looking for a tunnel group match based on certificate maps for peer certificate with certificate_identifier. Explanation The peer certificate identified by the certificate identifier is being processed through the configured certificate maps to attempt a possible tunnel group match.
717037
Error Message %ASA-4-717037: Tunnel group search using certificate maps failed for peer certificate: certificate_identifier. Explanation The peer certificate identified by the certificate identifier was processed through the configured certificate maps to attempt a possible tunnel group match, but no match can be found.
Recommended Action Make sure that the warning is expected based on the received peer certificate and the configured crypto CA certificate map rules.
717038
Error Message %ASA-7-717038: Tunnel group match found. Tunnel Group: tunnel_group_name, Peer certificate: certificate_identifier. Explanation The peer certificate identified by the certificate identifier was processed by the configured certificate maps, and a match was found to the tunnel group.
certificate_identifierInformation that identifies the certificate being processed by the certificate map rules tunnel_group_nameThe name of the tunnel group matched by the certificate map rules
1-444
Chapter 1
717039
Error Message %ASA-3-717039: Local CA Server internal error detected: error. Explanation An internal processing error has occurred with the local CA server.
errorError string
Recommended Action Based on the error, take the necessary steps to resolve the issue. Currently, the possible errors include:
CA key does not existMake sure that the CA key is present, or restore the key from a backup, if necessary. Failed to rollover expired CA certificateMake sure that the clock is correct and that the CA certificate is expired, then restart the CA server to try to reissue the certificate. Failed to generate self-signed certificate for Local CA Server certificate rollover upon expirationMake sure that the clock is correct and that the CA certificate is about to expire, then restart the CA server to try to reissue the certificate. Failed to configure Local CA ServerTurn on debugging and try to configure the CA server again to determine the cause of the failure. Invalid issuer name configuredChange the issuer name DN to a valid DN string.
717040
Error Message %ASA-2-717040: Local CA Server has failed and is being disabled. Reason: reason. Explanation The local CA server is being disabled because of an error.
reasonReason string Currently, the possible errors include: Storage downMake sure that storage is accessible, and reenable the CA server by using the no shut command.
Recommended Action Based on the reason, take the necessary steps to resolve the issue.
717041
Error Message %ASA-7-717041: Local CA Server event: event info. Explanation Event details that have occurred on the CA server are reported to allow you to track or debug the CA server health, including when the CA server is created, enabled, or disabled, or when the CA server certificate is rolled over.
event infoDetails of the event that occurred
1-445
Syslog Messages
717042
Error Message %ASA-3-717042: Failed to enable Local CA Server.Reason: reason. Explanation Errors occurred when an attempt was made to enable the local CA server.
reasonReason that the local CA server failed to enable
Recommended Action Resolve the issue encountered that is reported in the reason string. Currently, the possible reasons include:
Failed to create server trustpoint Failed to create server keypair Time has not been set Failed to init storage Storage not accessible Failed to validate self-signed CA certificate Failed to generate self-signed CA certificate CA certificate has expired Failed to generate CRL Failed to archive CA key and certificate Failed to generate empty user or certificate database file Failed to load user or certificate database file
717043
Error Message %ASA-6-717043: Local CA Server certificate enrollment related info for user: user. Info: info. Explanation Enrollment-related activities for a user are being monitored. The username and specific
enrollment information are reported so that enrollments, e-mail invitation generation, and renewal reminder generation can be monitored.

userUsername about whom the enrollment information log is being generated infoEnrollment information string
1-446
Chapter 1
717044
Error Message %ASA-3-717044: Local CA server certificate enrollment related error for user: user. Error: error. Explanation Errors that occur in the processing of certificate enrollment are reported, which may
include errors in notifying users via e-mail for renewal reminders, errors during issuance of a certificate to complete enrollment, invalid username or OTP, and expired enrollment attempts.

userUsername for whom the enrollment error log is being generated errorEnrollment error
Recommended Action If the error does not provide enough information to diagnose and resolve the issue, turn on debugging and try enrollment again.
717045
Error Message %ASA-7-717045:Local CA Server CRL info: info Explanation The CRL file is monitored when it is generated and regenerated.
infoInformational string of the CRL event
717046
Error Message %ASA-3-717046: Local CA Server CRL error: error. Explanation Errors that are encountered while trying to generate and reissue the local CA server CRL file are reported.
errorError string
Recommended Action Take appropriate action to resolve the reported issue, which may include verifying that storage is accessible, and that the CRL file is valid in storage and signed by the existing local CA server.
717047
Error Message %ASA-6-717047: Revoked certificate issued to user: username, with serial number serial number. Explanation Any certificates issued by the local CA server that have been revoked are being
monitored.
usernameUsername of the owner of the certificate that is being revoked
1-447
Syslog Messages
serial numberSerial number of the certificate that has been revoked
717048
Error Message %ASA-6-717048: Unrevoked certificate issued to user: username, with serial number serial number. Explanation Any certificates that were issued by the local CA server that were previously revoked,
and that are now being unrevoked and removed from the CRL are being monitored.

usernameUsername of the owner of the certificate that is being unrevoked serial numberSerial number of the certificate that has been unrevoked
717049
Error Message %ASA-1-717049: Local CA Server certificate is due to expire in number days and a replacement certificate is available for export. Explanation The administrator is alerted to an upcoming CA certificate expiration so that the
administrator can take action to export the replacement certificate to all ASAs that will require the new certificate.
numberThe number of days before the local CA server certificate expires
Recommended Action To avoid certificate validation failures on any ASAs that require the local CA server certificate, action should be taken before the actual expiration of the current local CA server certificate, which is indicated by the number value. Note that the local CA server does not require any action because the CA certificate will be replaced automatically. Use the show crypto ca server certificate command to view the replacement or rollover local CA server certificate and copy it for import into any ASA that will require the new certificate.
717050
Error Message %ASA-5-717050: SCEP Proxy: Processed request type type from IP client ip address, User username, TunnelGroup tunnel_group name, GroupPolicy group-policy name to CA IP ca ip address Explanation The SCEP proxy received a message and relayed it to the CA. The response from the
CA is relayed back to the client.
typeThe request type string that is received by the SCEP proxy, which can be one of the following SCEP message types: PKIOperation, GetCACaps, GetCACert, GetNextCACert, and GetCACertChain. client ip addressThe source IP address of the request received
1-448
Chapter 1
usernameThe username that is associated with the VPN session in which the SCEP request is received tunnel-group nameThe tunnel group that is associated with the VPN session in which the SCEP request is received group-policy nameThe group policy that is associated with the VPN session in which the SCEP request is received ca ip addressThe IP address of the CA that is configured in the group policy
717051
Error Message %ASA-3-717051: SCEP Proxy: Denied processing the request type type received from IP client ip address, User username, TunnelGroup tunnel group name, GroupPolicy group policy name to CA ca ip address. Reason: msg Explanation The SCEP proxy denied processing of the request, which may be caused by a misconfiguration, an error condition in the proxy, or an invalid request.
typeThe request type string that is received by the SCEP proxy, which can be one of the following SCEP message types: PKIOperation, GetCACaps, GetCACert, GetNextCACert, and GetCACertChain. client ip addressThe source IP address of the request received usernameThe username that is associated with the VPN session in which the SCEP request is received tunnel-group nameThe tunnel group that is associated with the VPN session in which the SCEP request is received group-policy nameThe group policy that is associated with the VPN session in which the SCEP request is received ca ip addressThe IP address of the CA that is configured in the group policy msgThe reason string that explains the reason or error for why the request processing is denied
Recommended Action Identify the cause from the reason printed. If the reason indicates that the request is invalid, check the CA URL configuration. Otherwise, confirm that the tunnel group is enabled for SCEP enrollment and debug further by using the debug crypto ca scep-proxy command.
1-449
Syslog Messages
718001
Error Message %ASA-7-718001: Internal interprocess communication queue send failure: code error_code Explanation An internal software error has occurred while attempting to enqueue a message on the VPN load balancing queue. Recommended Action This is generally a benign condition. If the problem persists, contact the Cisco
TAC.
718002
Error Message %ASA-5-718002: Create peer IP_address failure, already at maximum of number_of_peers Explanation The maximum number of load-balancing peers has been exceeded. The new peer is
ignored.
Recommended Action Check your load balancing and network configuration to ensure that the number of load-balancing peers does not exceed the maximum allowed.
718003
Error Message %ASA-6-718003: Got unknown peer message message_number from IP_address, local version version_number, remote version version_number Explanation An unrecognized load-balancing message was received from one of the load-balancing peers. This may indicate a version mismatch between peers, but is most likely caused by an internal software error. Recommended Action Verify that all load-balancing peers are compatible. If they are and this
condition persists or is linked to undesirable behavior, contact the Cisco TAC.
718004
Error Message %ASA-6-718004: Got unknown internal message message_number Explanation An internal software error occurred. Recommended Action This is generally a benign condition. If the problem persists, contact the Cisco
TAC.
1-450
Chapter 1
718005
Error Message %ASA-5-718005: Fail to send to IP_address, port port Explanation An internal software error occurred during packet transmission on the load-balancing
socket. This mght indicate a network problem.

Recommended Action Check the network-based configuration on the ASA and verify that interfaces
are active and protocol data is flowing through the ASA. If the problem persists, contact the Cisco TAC.
718006
Error Message %ASA-5-718006: Invalid load balancing state transition [cur=state_number][event=event_number] Explanation A state machine error has occurred. This might indicate an internal software error. Recommended Action This is generally a benign condition. If the problem persists, contact the Cisco
TAC.
718007
Error Message %ASA-5-718007: Socket open failure failure_code Explanation An error occurred when the load-balancing socket tried to open. This might indicate a network problem or an internal software error. Recommended Action Check the network-based configuration on the ASA and verify that interfaces
718008
Error Message %ASA-5-718008: Socket bind failure failure_code Explanation An error occurred when the ASA tried to bind to the load-balancing socket. This might
indicate a network problem or an internal software error.

1-451
Syslog Messages
718009
Error Message %ASA-5-718009: Send HELLO response failure to IP_address Explanation An error occurred when the ASA tried to send a hello response message to one of the
load-balancing peers. This might indicate a network problem or an internal software error.
718010
Error Message %ASA-5-718010: Sent HELLO response to IP_address Explanation The ASA transmitted a hello response message to a load-balancing peer. Recommended Action None required.
718011
Error Message %ASA-5-718011: Send HELLO request failure to IP_address Explanation An error occurred when the ASA tried to send a hello request message to one of the load-balancing peers. This may indicate a network problem or an internal software error. Recommended Action Check the network-based configuration on the ASA and verify that interfaces
718012
Error Message %ASA-5-718012: Sent HELLO request to IP_address Explanation The ASA transmitted a hello request message to a load-balancing peer. Recommended Action None required.
1-452
Chapter 1
718013
Error Message %ASA-6-718013: Peer IP_address is not answering HELLO Explanation The load-balancing peer is not answering a hello request message. Recommended Action Check the status of the load-balancing SSF peer and the network connections.
718014
Error Message %ASA-5-718014: Master peer IP_address is not answering HELLO Explanation The load balancing master peer is not answering the hello request message. Recommended Action Check the status of the load balancing SSF master peer and the network
connections.
718015
Error Message %ASA-5-718015: Received HELLO request from IP_address Explanation The ASA received a hello request message from the load balancing peer. Recommended Action None required.
718016
Error Message %ASA-5-718016: Received HELLO response from IP_address Explanation The ASA received a Hello Response packet from a load balancing peer. Recommended Action None required.
718017
Error Message %ASA-7-718017: Got timeout for unknown peer IP_address msg type message_type Explanation The ASA processed a timeout for an unknown peer. The message was ignored because the peer may have already been removed from the active list. Recommended Action If the message persists or is linked to undesirable behavior, check the load
balancing peers and verify that all are configured correctly.
1-453
Syslog Messages
718018
Error Message %ASA-7-718018: Send KEEPALIVE request failure to IP_address Explanation An error has occurred while attempting to send a Keepalive Request message to one of the load balancing peers. This t indicate a network problem or an internal software error. Recommended Action Check the network-based configuration on the ASA and verify that interfaces
718019
Error Message %ASA-7-718019: Sent KEEPALIVE request to IP_address Explanation The ASA transmitted a Keepalive Request message to a load balancing peer. Recommended Action None required.
718020
Error Message %ASA-7-718020: Send KEEPALIVE response failure to IP_address Explanation An error has occurred while attempting to send a Keepalive Response message to one of the load balancing peers. This may indicate a network problem or an internal software error. Recommended Action Check the network-based configuration on the ASA and verify that interfaces
718021
Error Message %ASA-7-718021: Sent KEEPALIVE response to IP_address Explanation The ASA transmitted a Keepalive Response message to a load balancing peer. Recommended Action None required.
1-454
Chapter 1
718022
Error Message %ASA-7-718022: Received KEEPALIVE request from IP_address Explanation The ASA received a Keepalive Request message from a load balancing peer. Recommended Action None required.
718023
Error Message %ASA-7-718023: Received KEEPALIVE response from IP_address Explanation The ASA received a Keepalive Response message from a load balancing peer. Recommended Action None required.
718024
Error Message %ASA-5-718024: Send CFG UPDATE failure to IP_address Explanation An error has occurred while attempting to send a Configuration Update message to one of the load balancing peers. This might indicate a network problem or an internal software error. Recommended Action Check the network-based configuration on the ASA and verify that interfaces
718025
Error Message %ASA-7-718025: Sent CFG UPDATE to IP_address Explanation The ASA transmitted a Configuration Update message to a load balancing peer. Recommended Action None required.
718026
Error Message %ASA-7-718026: Received CFG UPDATE from IP_address Explanation The ASA received a Configuration Update message from a load balancing peer. Recommended Action None required.
1-455
Syslog Messages
718027
Error Message %ASA-6-718027: Received unexpected KEEPALIVE request from IP_address Explanation The ASA received an unexpected Keepalive request message from a load balancing
peer.
Recommended Action If the problem persists or is linked with undesirable behavior, verify that all load balancing peers are configured and discovered correctly.
718028
Error Message %ASA-5-718028: Send OOS indicator failure to IP_address Explanation An error has occurred while attempting to send an OOS indicator message to one of the
load balancing peers. This might indicate a network problem or an internal software error.
718029
Error Message %ASA-7-718029: Sent OOS indicator to IP_address Explanation The ASA transmitted an OOS indicator message to a load balancing peer. Recommended Action None required.
718030
Error Message %ASA-6-718030: Received planned OOS from IP_address Explanation The ASA received a planned OOS message from a load balancing peer. Recommended Action None required.
1-456
Chapter 1
718031
Error Message %ASA-5-718031: Received OOS obituary for IP_address Explanation The ASA received an OOS obituary message from a load balancing peer. Recommended Action None required.
718032
Error Message %ASA-5-718032: Received OOS indicator from IP_address Explanation The ASA received an OOS indicator message from a load balancing peer. Recommended Action None required.
718033
Error Message %ASA-5-718033: Send TOPOLOGY indicator failure to IP_address Explanation An error has occurred while attempting to send a Topology indicator message to one of the load balancing peers. This might indicate a network problem or an internal software error. Recommended Action Check the network-based configuration on the ASA. and verify that interfaces are active, and protocol data is flowing through the ASA. If the problem persists, contact the Cisco TAC.
718034
Error Message %ASA-7-718034: Sent TOPOLOGY indicator to IP_address Explanation The ASA sent a Topology indicator message to a load balancing peer. Recommended Action None required.
718035
Error Message %ASA-7-718035: Received TOPOLOGY indicator from IP_address Explanation The ASA received a Topology indicator message from a load balancing peer. Recommended Action None required.
1-457
Syslog Messages
718036
Error Message %ASA-7-718036: Process timeout for req-type type_value, exid exchange_ID, peer IP_address Explanation The ASA processed a peer timeout. Recommended Action Verify that the peer should have been timed out. If not, check the load balancing peer configuration and the network connection between the peer and the ASA.
718037
Error Message %ASA-6-718037: Master processed number_of_timeouts timeouts Explanation The ASA in the master role processed the specified number of peer timeouts. Recommended Action Verify that the timeouts are legitimate. If not, check the peer load balancing
configuration and the network connection between the peer and the ASA.
718038
Error Message %ASA-6-718038: Slave processed number_of_timeouts timeouts Explanation The ASA in the slave role processed the specified number of peer timeouts. Recommended Action Verify that the timeouts are legitimate. If not, check the peer load balancing
configuration and the network connection between the peer and the ASA.
718039
Error Message %ASA-6-718039: Process dead peer IP_address Explanation The ASA has detected a dead peer. Recommended Action Verify that the dead peer detection is legitimate. If not, check the peer load balancing configuration and the network connection between the peer and the ASA.
1-458
Chapter 1
718040
Error Message %ASA-6-718040: Timed-out exchange ID exchange_ID not found Explanation The ASA has detected a dead peer, but the exchange ID is not recognized. Recommended Action None required.
718041
Error Message %ASA-7-718041: Timeout [msgType=type] processed with no callback Explanation The ASA has detected a dead peer, but a call back was not used in the processing. Recommended Action None required.
718042
Error Message %ASA-5-718042: Unable to ARP for IP_address Explanation The ASA experienced an ARP failure when attempting to contact a peer. Recommended Action Verify that the network is operational and that all peers can communicate with
each other.
718043
Error Message %ASA-5-718043: Updating/removing duplicate peer entry IP_address Explanation The ASA found and is removing a duplicate peer entry. Recommended Action None required.
718044
Error Message %ASA-5-718044: Deleted peer IP_address Explanation The ASA is deleting a load balancing peer. Recommended Action None required.
1-459
Syslog Messages
718045
Error Message %ASA-5-718045: Created peer IP_address Explanation The ASA has detected a load balancing peer. Recommended Action None required.
718046
Error Message %ASA-7-718046: Create group policy policy_name Explanation The ASA has created a group policy to securely communicate with the load balancing
peers.
718047
Error Message %ASA-7-718047: Fail to create group policy policy_name Explanation The ASA experienced a failure when attempting to create a group policy for securing
the communication between load balancing peers.

Recommended Action Verify that the load balancing configuration is correct.
718048
Error Message %ASA-5-718048: Create of secure tunnel failure for peer IP_address Explanation The ASA experienced a failure when attempting to establish an IPsec tunnel to a load balancing peer. Recommended Action Verify that the load balancing configuration is correct and that the network is
operational.
718049
Error Message %ASA-7-718049: Created secure tunnel to peer IP_address Explanation The ASA successfully established an IPsec tunnel to a load balancing peer. Recommended Action None required.
1-460
Chapter 1
718050
Error Message %ASA-5-718050: Delete of secure tunnel failure for peer IP_address Explanation The ASA experienced a failure when attempting to terminate an IPsec tunnel to a load balancing peer. Recommended Action Verify that the load balancing configuration is correct and that the network is
operational.
718051
Error Message %ASA-6-718051: Deleted secure tunnel to peer IP_address Explanation The ASA successfully terminated an IPsec tunnel to a load balancing peer. Recommended Action None required.
718052
Error Message %ASA-5-718052: Received GRAT-ARP from duplicate master MAC_address Explanation The ASA received a gratuitous ARP from a duplicate master. Recommended Action Check the load balancing configuration and verify that the network is
operational.
718053
Error Message %ASA-5-718053: Detected duplicate master, mastership stolen MAC_address Explanation The ASA detected a duplicate master and a stolen master. Recommended Action Check the load balancing configuration and verify that the network is
operational.
1-461
Syslog Messages
718054
Error Message %ASA-5-718054: Detected duplicate master MAC_address and going to SLAVE Explanation The ASA detected a duplicate master and is switching to slave mode. Recommended Action Check the load balancing configuration and verify that the network is
operational.
718055
Error Message %ASA-5-718055: Detected duplicate master MAC_address and staying MASTER Explanation The ASA detected a duplicate master and is staying in slave mode. Recommended Action Check the load balancing configuration and verify that the network is
operational.
718056
Error Message %ASA-7-718056: Deleted Master peer, IP IP_address Explanation The ASA deleted the load balancing master from its internal tables. Recommended Action None required.
718057
Error Message %ASA-5-718057: Queue send failure from ISR, msg type failure_code Explanation An internal software error has occurred while attempting to enqueue a message on the VPN load balancing queue from an Interrupt Service Routing. Recommended Action This is generally a benign condition. If the problem persists, contact the Cisco
TAC.
1-462
Chapter 1
718058
Error Message %ASA-7-718058: State machine return code: action_routine, return_code Explanation The return codes of action routines belonging to the load balancing finite state machine are being traced. Recommended Action None required.
718059
Error Message %ASA-7-718059: State machine function trace: state=state_name, event=event_name, func=action_routine Explanation The events and states of the load balancing finite state machine are being traced. Recommended Action None required.
718060
Error Message %ASA-5-718060: Inbound socket select fail: context=context_ID. Explanation The socket select call returned an error and the socket cannot be read. This might
indicate an internal software error.

718061
Error Message %ASA-5-718061: Inbound socket read fail: context=context_ID. Explanation The socket read failed after data was detected through the select call. This might indicate an internal software error. Recommended Action If the problem persists, contact the Cisco TAC.
718062
Error Message %ASA-5-718062: Inbound thread is awake (context=context_ID). Explanation The load balancing process is awakened and begins processing. Recommended Action None required.
1-463
Syslog Messages
718063
Error Message %ASA-5-718063: Interface interface_name is down. Explanation The load balancing process found the interface down. Recommended Action Check the interface configuration to make sure that the interface is operational.
718064
Error Message %ASA-5-718064: Admin. interface interface_name is down. Explanation The load balancing process found the administrative interface down. Recommended Action Check the administrative interface configuration to make sure that the interface
is operational.
718065
Error Message %ASA-5-718065: Cannot continue to run (public=up/down, private=up/down, enable=LB_state, master=IP_address, session=Enable/Disable). Explanation The load balancing process can not run because all prerequisite conditions have not
been met. The prerequisite conditions are two active interfaces and load balancing enabled.
Recommended Action Check the interface configuration to make sure at least two interfaces are
operational and load balancing is enabled.
718066
Error Message %ASA-5-718066: Cannot add secondary address to interface interface_name, ip IP_address. Explanation Load balancing requires a secondary address to be added to the outside interface. A failure occurred in adding that secondary address. Recommended Action Check the address being used as the secondary address and make sure that it is
valid and unique. Check the configuration of the outside interface.
1-464
Chapter 1
718067
Error Message %ASA-5-718067: Cannot delete secondary address to interface interface_name, ip IP_address. Explanation The deletion of the secondary address failed, which might indicate an addressing problem or an internal software error. Recommended Action Check the addressing information of the outside interface and make sure that the secondary address is valid and unique. If the problem persists, contact the Cisco TAC.
718068
Error Message %ASA-5-718068: Start VPN Load Balancing in context context_ID. Explanation The load balancing process has been started and initialized. Recommended Action None required.
718069
Error Message %ASA-5-718069: Stop VPN Load Balancing in context context_ID. Explanation The load balancing process has been stopped. Recommended Action None required.
718070
Error Message %ASA-5-718070: Reset VPN Load Balancing in context context_ID. Explanation The LB process has been reset. Recommended Action None required.
718071
Error Message %ASA-5-718071: Terminate VPN Load Balancing in context context_ID. Explanation The LB process has been terminated. Recommended Action None required.
1-465
Syslog Messages
718072
Error Message %ASA-5-718072: Becoming master of Load Balancing in context context_ID. Explanation The ASA has become the LB master. Recommended Action None required.
718073
Error Message %ASA-5-718073: Becoming slave of Load Balancing in context context_ID. Explanation The ASA has become the LB slave. Recommended Action None required.
718074
Error Message %ASA-5-718074: Fail to create access list for peer context_ID. Explanation ACLs are used to create secure tunnels over which the LB peers can communicate. The
ASA was unable to create one of these ACLs. This might indicate an addressing problem or an internal software problem.
Recommended Action Check the addressing information of the inside interface on all peers and ensure that all peers are discovered correctly. If the problem persists, contact the Cisco TAC.
718075
Error Message %ASA-5-718075: Peer IP_address access list not set. Explanation While removing a secure tunnel, the ASA detected a peer entry that did not have an associated ACL. Recommended Action None required.
1-466
Chapter 1
718076
Error Message %ASA-5-718076: Fail to create tunnel group for peer IP_address. Explanation The ASA experienced a failure when trying to create a tunnel group for securing the
communication between load balancing peers.

Recommended Action Verify that the load balancing configuration is correct.
718077
Error Message %ASA-5-718077: Fail to delete tunnel group for peer IP_address. Explanation The ASA experienced a failure when attempting to delete a tunnel group for securing
the communication between load balancing peers.

718078
Error Message %ASA-5-718078: Fail to create crypto map for peer IP_address. Explanation The ASA experienced a failure when attempting to create a crypto map for securing the communication between load balancing peers. Recommended Action Verify that the load balancing configuration is correct.
718079
Error Message %ASA-5-718079: Fail to delete crypto map for peer IP_address. Explanation The ASA experienced a failure when attempting to delete a crypto map for securing the communication between load balancing peers. Recommended Action None required.
1-467
Syslog Messages
718080
Error Message %ASA-5-718080: Fail to create crypto policy for peer IP_address. Explanation The ASA experienced a failure when attempting to create a transform set to be used in
securing the communication between load balancing peers. This might indicate an internal software problem.
718081
Error Message %ASA-5-718081: Fail to delete crypto policy for peer IP_address. Explanation The ASA experienced a failure when attempting to delete a transform set used in
securing the communication between load balancing peers.

718082
Error Message %ASA-5-718082: Fail to create crypto ipsec for peer IP_address. Explanation When cluster encryption for VPN load balancing is enabled, the VPN load balancing
device creates a set of site-to-site tunnels for every other device in the load balancing cluster. For each tunnel, a set of crypto parameters (access list, crypto maps, and transform set) is created dynamically. One or more crypto parameters failed to be created or configured.
IP_addressThe IP address of the remote peer
Recommended Action Examine the message for other entries specific to the type of crypto parameters that failed to be created.
718083
Error Message %ASA-5-718083: Fail to delete crypto ipsec for peer IP_address. Explanation When the local VPN load balancing device is removed from the cluster, crypto
parameters are removed. One or more crypto parameters failed to be deleted.
IP_addressThe IP address of the remote peer
Recommended Action Examine the message for other entries specific to the type of crypto parameters that failed to be deleted.
1-468
Chapter 1
718084
Error Message %ASA-5-718084: Public/cluster IP not on the same subnet: public IP_address, mask netmask, cluster IP_address Explanation The cluster IP address is not on the same network as the outside interface of the ASA. Recommended Action Make sure that both the cluster (or virtual) IP address and the outside interface
address are on the same network.
718085
Error Message %ASA-5-718085: Interface interface_name has no IP address defined. Explanation The interface does not have an IP address configured. Recommended Action Configure an IP address for the interface.
718086
Error Message %ASA-5-718086: Fail to install LB NP rules: type rule_type, dst interface_name, port port. Explanation The ASA experienced a failure when attempting to create a SoftNP ACL rule to be used in securing the communication between load balancing peers. This may indicate an internal software problem. Recommended Action If the problem persists, contact the Cisco TAC.
718087
Error Message %ASA-5-718087: Fail to delete LB NP rules: type rule_type, rule rule_ID. Explanation The ASA experienced a failure when attempting to delete the SoftNP ACL rule used in securing the communication between load balancing peers. Recommended Action None required.
1-469
Syslog Messages
718088
Error Message %ASA-7-718088: Possible VPN LB misconfiguration. Offending device MAC MAC_address. Explanation The presence of a duplicate master indicates that one of the load balancing peers may be misconfigured. Recommended Action Check the load balancing configuration on all peers, but pay special attention
to the peer identified.
719001
Error Message %ASA-6-719001: Email Proxy session could not be established: session limit of maximum_sessions has been reached. Explanation The incoming e-mail proxy session cannot be established because the maximum session limit has been reached.
maximum_sessionsThe maximum session number
719002
Error Message %ASA-3-719002: Email Proxy session pointer from source_address has been terminated due to reason error. Explanation The session has been terminated because of an error. The possible errors are failure to
add a session to the session database, failure to allocate memory, and failure to write data to a channel.

pointerThe session pointer source_addressThe e-mail proxy client IP address reasonThe error type
719003
Error Message %ASA-6-719003: Email Proxy session pointer resources have been freed for source_address. Explanation The dynamic allocated session structure has been freed and set to NULL after the
session terminated.
pointerThe session pointer
1-470
Chapter 1
source_addressThe e-mail proxy client IP address
719004
Error Message %ASA-6-719004: Email Proxy session pointer has been successfully established for source_address. Explanation A new incoming e-mail client session has been established. Recommended Action None required.
719005
Error Message %ASA-7-719005: FSM NAME has been created using protocol for session pointer from source_address. Explanation The FSM has been created for an incoming new session.
NAMEThe FSM instance name for the session protocolThe e-mail protocol type (for example, POP3, IMAP, and SMTP) pointerThe session pointer source_addressThe e-mail proxy client IP address
719006
Error Message %ASA-7-719006: Email Proxy session pointer has timed out for source_address because of network congestion. Explanation Network congestion is occurring, and data cannot be sent to either an e-mail client or an e-mail server. This condition starts the block timer. After the block timer is timed out, the session expires.
pointerThe session pointer source_addressThe e-mail proxy client IP address
Recommended Action Retry the operation after a few minutes.
1-471
Syslog Messages
719007
Error Message %ASA-7-719007: Email Proxy session pointer cannot be found for source_address. Explanation A matching session cannot be found in the session database. The session pointer is bad.
719008
Error Message %ASA-3-719008: Email Proxy service is shutting down. Explanation The e-mail proxy is disabled. All resources are cleaned up, and all threads are
terminated.
719009
Error Message %ASA-7-719009: Email Proxy service is starting. Explanation The e-mail proxy is enabled. Recommended Action None required.
719010
Error Message %ASA-6-719010: protocol Email Proxy feature is disabled on interface interface_name. Explanation The e-mail proxy feature is disabled on a specific entry point, invoked from the CLI.
This is the main off switch for the user. When all protocols are turned off for all interfaces, the main shut-down routine is invoked to clean up global resources and threads.

protocolThe e-mail proxy protocol type (for example, POP3, IMAP, and SMTP) interface_name The ASA interface name
1-472
Chapter 1
719011
Error Message %ASA-6-719011: Protocol Email Proxy feature is enabled on interface interface_name. Explanation The e-mail proxy feature is enabled on a specific entry point, invoked from the CLI. This is the main on switch for the user. When it is first used, the main startup routine is invoked to allocate global resources and threads. Subsequent calls only need to start listening threads for the particular protocol.
protocolThe e-mail proxy protocol type (for example, POP3, IMAP, and SMTP) interface_name The ASA interface name
719012
Error Message %ASA-6-719012: Email Proxy server listening on port port for mail protocol protocol. Explanation A listening channel is opened for a specific protocol on a configured port and has added
it to a TCP select group.

portThe configured port number protocolThe e-mail proxy protocol type (for example, POP3, IMAP, and SMTP)
719013
Error Message %ASA-6-719013: Email Proxy server closing port port for mail protocol protocol. Explanation A listening channel is closed for a specific protocol on a configured port and has
removed it from the TCP select group.

portThe configured port number protocolThe e-mail proxy protocol type (for example, POP3, IMAP, and SMTP)
1-473
Syslog Messages
719014
Error Message %ASA-5-719014: Email Proxy is changing listen port from old_port to new_port for mail protocol protocol. Explanation A change is signaled in the listening port for the specified protocol. All enabled
interfaces for that port have their listening channels closed and have restarted listening on the new port. This action is invoked from the CLI.

old_portThe previously configured port number new_port The newly configured port number protocolThe e-mail proxy protocol type (for example, POP3, IMAP, and SMTP)
719015
Error Message %ASA-7-719015: Parsed emailproxy session pointer from source_address username: mailuser = mail_user, vpnuser = VPN_user, mailserver = server Explanation The username string is received from the client in the format vpnuser (name delimiter)
mailuser (server delimiter) mailserver (for example: xxx:[email protected]). The name delimiter is optional. When the delimiter is not there, the VPN username and mail username are the same. The server delimiter is optional. When it is not present, the default configured mail server will be used.

pointerThe session pointer source_addressThe e-mail proxy client IP address mail_userThe e-mail account username VPN_userThe WebVPN username serverThe e-mail server
719016
Error Message %ASA-7-719016: Parsed emailproxy session pointer from source_address password: mailpass = ******, vpnpass= ****** Explanation The password string is received from the client in the format, vpnpass (name delimiter) mailpass (for example: xxx:yyy). The name delimiter is optional. When it is not present, the VPN password and mail password are the same.
1-474
Chapter 1
719017
Error Message %ASA-6-719017: WebVPN user: vpnuser invalid dynamic ACL. Explanation The WebVPN session is aborted because the ACL has failed to parse for this user. The
ACL determines what the user restrictions are on e-mail account access. The ACL is downloaded from the AAA server. Because of this error, it is unsafe to proceed with login.
vpnuserThe WebVPN username
Recommended Action Check the AAA server and fix the dynamic ACL for this user.
719018
Error Message %ASA-6-719018: WebVPN user: vpnuser ACL ID acl_ID not found Explanation The ACL cannot be found at the local maintained ACL list. The ACL determines what
the user restrictions are on e-mail account access. The ACL is configured locally. Because of this error, you cannot be authorized to proceed.

vpnuserThe WebVPN username acl_IDThe local configured ACL identification string
Recommended Action Check the local ACL configuration.
719019
Error Message %ASA-6-719019: WebVPN user: vpnuser authorization failed. Explanation The ACL determines what the user restrictions are on e-mail account access. The user
cannot access the e-mail account because the authorization check fails.
719020
Error Message %ASA-6-719020: WebVPN user vpnuser authorization completed successfully. Explanation The ACL determines what the user restrictions are on e-mail account access. The user is authorized to access the e-mail account.
1-475
Syslog Messages
719021
Error Message %ASA-6-719021: WebVPN user: vpnuser is not checked against ACL. Explanation The ACL determines what the user restrictions are on e-mail account access. The
authorization checking using the ACL is not enabled.
Recommended Action Enable the ACL checking feature, if necessary.
719022
Error Message %ASA-6-719022: WebVPN user vpnuser has been authenticated. Explanation The username is authenticated by the AAA server.
719023
Error Message %ASA-6-719023: WebVPN user vpnuser has not been successfully authenticated. Access denied. Explanation The username is denied by the AAA server. The session will be aborted. The user is not allowed to access the e-mail account.
719024
Error Message %ASA-6-719024: Email Proxy piggyback auth fail: session = pointer user=vpnuser addr=source_address Explanation The Piggyback authentication is using an established WebVPN session to verify the
username and IP address matching in the WebVPN session database. This is based on the assumption that the WebVPN session and e-mail proxy session are initiated by the same user, and a WebVPN session is already established. Because the authentication has failed, the session will be aborted. The user is not allowed to access the e-mail account.

pointerThe session pointer vpnuserThe WebVPN username
1-476
Chapter 1
source_addressThe client IP address
719025
Error Message %ASA-6-719025: Email Proxy DNS name resolution failed for hostname. Explanation The hostname cannot be resolved with the IP address because it is not valid, or no DNS
server is available.
hostnameThe hostname that needs to be resolved
Recommended Action Check DNS server availability and whether or not the configured mail server
name is valid.
719026
Error Message %ASA-6-719026: Email Proxy DNS name hostname resolved to IP_address. Explanation The hostname has successfully been resolved with the IP address.
hostnameThe hostname that needs to be resolved IP_addressThe IP address resolved from the configured mail server name
720001
Error Message %ASA-4-720001: (VPN-unit) Failed to initialize with Chunk Manager. Explanation The VPN failover subsystem fails to initialize with the memory buffer management
subsystem. A system-wide problem has occurred, and the VPN failover subsystem cannot be started.
unitEither Primary or Secondary
Recommended Action Examine the messages for any sign of system-level initialization problems.
720002
Error Message %ASA-6-720002: (VPN-unit) Starting VPN Stateful Failover Subsystem... Explanation The VPN failover subsystem is starting and booting up.
1-477
Syslog Messages
720003
Error Message %ASA-6-720003: (VPN-unit) Initialization of VPN Stateful Failover Component completed successfully Explanation The VPN failover subsystem initialization is completed at boot time.
720004
Error Message %ASA-6-720004: (VPN-unit) VPN failover main thread started. Explanation The VPN failover main processing thread is started at boot time.
720005
Error Message %ASA-6-720005: (VPN-unit) VPN failover timer thread started. Explanation The VPN failover timer processing thread is started at boot time.
720006
Error Message %ASA-6-720006: (VPN-unit) VPN failover sync thread started. Explanation The VPN failover bulk synchronization processing thread is started at boot time.
1-478
Chapter 1
720007
Error Message %ASA-4-720007: (VPN-unit) Failed to allocate chunk from Chunk Manager. Explanation The set of preallocated memory buffers is running out. The ASA has a resource issue. The ASA may be under heavy load when too many messages are being processed.
Recommended Action This condition may be improved later when the VPN failover subsystem processes outstanding messages and frees up previously allocated memory.
720008
Error Message %ASA-4-720008: (VPN-unit) Failed to register to High Availability Framework. Explanation The VPN failover subsystem failed to register to the core failover subsystem. The VPN
failover subsystem cannot be started, which may be caused by initialization problems of other subsystems.
Recommended Action Search the message for any sign of system-wide initialization problems.
720009
Error Message %ASA-4-720009: (VPN-unit) Failed to create version control block. Explanation The VPN failover subsystem failed to create a version control block. This step is required for the VPN failover subsystem to find out the backward compatible firmware versions for the current release. The VPN failover subsystem cannot be started, which may be caused by initialization problems of other subsystems.
1-479
Syslog Messages
720010
Error Message %ASA-6-720010: (VPN-unit) VPN failover client is being disabled Explanation An operator enabled failover without defining a failover key. In order to use a VPN failover, a failover key must be defined.
Recommended Action Use the failover key command to define a shared secret key between the active
and standby units.
720011
Error Message %ASA-4-720011: (VPN-unit) Failed to allocate memory Explanation The VPN failover subsystem cannot allocate a memory buffer, which indicates a system-wide resource problem. The ASA may be under heavy load.
Recommended Action This condition may be improved later when you reduce the load on the ASA by reducing incoming traffic. By reducing incoming traffic, memory allocated for processing the existing work load will be available, and the ASA may return to normal operation.
720012
Error Message %ASA-6-720012: (VPN-unit) Failed to update IPsec failover runtime data on the standby unit. Explanation The VPN failover subsystem cannot update IPsec-related runtime data because the corresponding IPsec tunnel has been deleted on the standby unit.
720013
Error Message %ASA-4-720013: (VPN-unit) Failed to insert certificate in trustpoint
trustpoint_name
Explanation The VPN failover subsystem tried to insert a certificate in the trustpoint.
unitEither Primary or Secondary trustpoint_nameThe name of the trustpoint
Recommended Action Check the certificate content to determine if it is invalid.
1-480
Chapter 1
720014
Error Message %ASA-6-720014: (VPN-unit) Phase 2 connection entry (msg_id=message_number, my cookie=mine, his cookie=his) contains no SA list. Explanation No security association is linked to the Phase 2 connection entry.
unitEither Primary or Secondary message_numberThe message ID of the Phase 2 connection entry mineThe My Phase 1 cookie hisThe peer Phase 1 cookie
720015
Error Message %ASA-6-720015: (VPN-unit) Cannot found Phase 1 SA for Phase 2 connection entry (msg_id=message_number,my cookie=mine, his cookie=his). Explanation The corresponding Phase 1 security association for the given Phase 2 connection entry
cannot be found.

unitEither Primary or Secondary message_numberThe message ID of the Phase 2 connection entry mineThe My Phase 1 cookie hisThe peer Phase 1 cookie
720016
Error Message %ASA-5-720016: (VPN-unit) Failed to initialize default timer #index. Explanation The VPN failover subsystem failed to initialize the given timer event. The VPN failover subsystem cannot be started at boot time.
unitEither Primary or Secondary indexThe internal index of the timer event
1-481
Syslog Messages
720017
Error Message %ASA-5-720017: (VPN-unit) Failed to update LB runtime data Explanation The VPN failover subsystem failed to update the VPN load balancing runtime data.
720018
Error Message %ASA-5-720018: (VPN-unit) Failed to get a buffer from the underlying core high availability subsystem. Error code code. Explanation The ASA may be under heavy load. The VPN failover subsystem failed to obtain a
failover buffer.

unitEither Primary or Secondary codeThe error code returned by the high-availability subsystem
Recommended Action Decrease the amount of incoming traffic to improve the current load condition. With decreased incoming traffic, the ASA will free up memory allocated for processing the incoming load.
720019
Error Message %ASA-5-720019: (VPN-unit) Failed to update cTCP statistics. Explanation The VPN failover subsystem failed to update the IPsec/cTCP-related statistics.
Recommended Action None required. Updates are sent periodically, so the standby unit IPsec/cTCP
statistics should be updated with the next update message.
720020
Error Message %ASA-5-720020: (VPN-unit) Failed to send type timer message. Explanation The VPN failover subsystem failed to send a periodic timer message to the standby unit.
unitEither Primary or Secondary typeThe type of timer message
Recommended Action None required. The periodic timer message will be resent during the next
timeout.
1-482
Chapter 1
720021
Error Message %ASA-5-720021: (VPN-unit) HA non-block send failed for peer msg message_number. HA error code. Explanation The VPN failover subsystem failed to send a nonblock message. This is a temporary condition caused by the ASA being under load or out of resources.
unitEither Primary or Secondary message_numberThe ID number of the peer message codeThe error return code
Recommended Action The condition will improve as more resources become available to the ASA.
720022
Error Message %ASA-4-720022: (VPN-unit) Cannot find trustpoint trustpoint Explanation An error occurred when the VPN failover subsystem tried to look up a trustpoint by
name.

unitEither Primary or Secondary trustpointThe name of the trustpoint.
Recommended Action The trustpoint may be deleted by an operator.
720023
Error Message %ASA-6-720023: (VPN-unit) HA status callback: Peer is not present. Explanation The VPN failover subsystem is notified by the core failover subsystem when the local ASA detected that a peer is available or becomes unavailable.
unitEither Primary or Secondary notEither not or left blank
1-483
Syslog Messages
720024
Error Message %ASA-6-720024: (VPN-unit) HA status callback: Control channel is status. Explanation The failover control channel is either up or down. The failover control channel is defined by the failover link and show failover commands, which indicate whether the failover link channel is up or down.
unitEither Primary or Secondary status Up or Down
720025
Error Message %ASA-6-720025: (VPN-unit) HA status callback: Data channel is status. Explanation The failover data channel is up or down.
unitEither Primary or Secondary statusUp or Down
720026
Error Message %ASA-6-720026: (VPN-unit) HA status callback: Current progression is being aborted. Explanation An operator or other external condition has occurred and has caused the current failover
progression to abort before the failover peer agrees on the role (either active or standby). For example, when the failover active command is entered on the standby unit during the negotiation, or when the active unit is being rebooted.
720027
Error Message %ASA-6-720027: (VPN-unit) HA status callback: My state state. Explanation The state of the local failover device is changed.
1-484
Chapter 1
stateCurrent state of the local failover device
720028
Error Message %ASA-6-720028: (VPN-unit) HA status callback: Peer state state. Explanation The current state of the failover peer is reported.
unitEither Primary or Secondary stateCurrent state of the failover peer
720029
Error Message %ASA-6-720029: (VPN-unit) HA status callback: Start VPN bulk sync state. Explanation The active unit is ready to send all the state information to the standby unit.
720030
Error Message %ASA-6-720030: (VPN-unit) HA status callback: Stop bulk sync state. Explanation The active unit finished sending all the state information to the standby unit.
720031
Error Message %ASA-7-720031: (VPN-unit) HA status callback: Invalid event received. event=event_ID. Explanation The VPN failover subsystem received an invalid callback event from the underlying
failover subsystem.
1-485
Syslog Messages
event_IDThe invalid event ID received
720032
Error Message %ASA-6-720032: (VPN-unit) HA status callback: id=ID, seq=sequence_#, grp=group, event=event, op=operand, my=my_state, peer=peer_state. Explanation The VPN failover subsystem indicated that a status update was notified by the
underlying failover subsystem.

unitEither Primary or Secondary IDClient ID number sequence_#Sequence number groupGroup ID eventCurrent event operandCurrent operand my_stateThe system current state peer_stateThe current state of the peer
720033
Error Message %ASA-4-720033: (VPN-unit) Failed to queue add to message queue. Explanation System resources may be running low. An error occurred when the VPN failover subsystem tried to queue an internal message. This may be a temporary condition indicating that the ASA is under heavy load, and the VPN failover subsystem cannot allocate resource to handle incoming traffic.
Recommended Action This error condition may disappear if the current load of the ASA is reduced, and additional system resources become available for processing new messages again.
720034
Error Message %ASA-7-720034: (VPN-unit) Invalid type (type) for message handler. Explanation An error occurred when the VPN failover subsystem tried to process an invalid message
type.
1-486
Chapter 1
typeMessage type
720035
Error Message %ASA-5-720035: (VPN-unit) Fail to look up CTCP flow handle Explanation The cTCP flow may be deleted on the standby unit before the VPN failover subsystem
tries to do a lookup.
Recommended Action Look for any sign of cTCP flow deletion in the message to determine the reason
(for example, idle timeout) why the flow was deleted.
720036
Error Message %ASA-5-720036: (VPN-unit) Failed to process state update message from the active peer. Explanation An error occurred when the VPN failover subsystem tried to process a state update message received by the standby unit.
unit - Either Primary or Secondary
Recommended Action None required. This may be a temporary condition because of the current load or low system resources.
720037
Error Message %ASA-6-720037: (VPN-unit) HA progression callback: id=id,seq=sequence_number,grp=group,event=event,op=operand, my=my_state,peer=peer_state. Explanation The status of the current failover progression is reported.
unitEither Primary or Secondary idClient ID sequence_numberSequence number groupGroup ID eventCurrent event operandCurrent operand my_stateCurrent state of the ASA
1-487
Syslog Messages
peer_stateCurrent state of the peer
720038
Error Message %ASA-4-720038: (VPN-unit) Corrupted message from active unit. Explanation The standby unit received a corrupted message from the active unit. Messages from the active unit are corrupted, which may be caused by incompatible firmware running between the active and standby units. The local unit has become the active unit of the failover pair.
720039
Error Message %ASA-6-720039: (VPN-unit) VPN failover client is transitioning to active state Explanation The local unit has become the active unit of the failover pair.
720040
Error Message %ASA-6-720040: (VPN-unit) VPN failover client is transitioning to standby state. Explanation The local unit has become the standby unit of the failover pair.
720041
Error Message %ASA-7-720041: (VPN-unit) Sending type message id to standby unit Explanation A message has been sent from the active unit to the standby unit.
unitEither Primary or Secondary typeMessage type
1-488
Chapter 1
idIdentifier for the message
720042
Error Message %ASA-7-720042: (VPN-unit) Receiving type message id from active unit Explanation A message has been received from the active unit by the standby unit.
unitEither Primary or Secondary typeMessage type idIdentifier for the message
720043
Error Message %ASA-4-720043: (VPN-unit) Failed to send type message id to standby unit Explanation An error occurred when the VPN failover subsystem tried to send a message from the active unit to the standby unit. The error may be caused by message 720018, in which the core failover subsystem runs out of failover buffer or the failover LAN link is down.
unitEither Primary or Secondary typeMessage type idIdentifier for the message
Recommended Action Use the show failover command to see if the failover pair is running correctly
and the failover LAN link is up.
720044
Error Message %ASA-4-720044: (VPN-unit) Failed to receive message from active unit Explanation An error occurred when the VPN failover subsystem tried to receive a message on the standby unit. The error may be caused by a corrupted message or an inadequate amount of memory allocated for storing the incoming message.
Recommended Action Use the show failover command and look for receive errors to determine if this is a VPN failover-specific problem or a general failover issue. Corrupted messages may be caused by incompatible firmware versions running on the active and standby units. Use the show memory command to determine if a low memory condition exists.
1-489
Syslog Messages
720045
Error Message %ASA-6-720045: (VPN-unit) Start bulk syncing of state information on standby unit. Explanation The standby unit has been notified to start receiving bulk synchronization information
from the active unit.
720046
Error Message %ASA-6-720046: (VPN-unit) End bulk syncing of state information on standby unit Explanation The standby unit has been notified that bulk synchronization from the active unit is
completed.
720047
Error Message %ASA-4-720047: (VPN-unit) Failed to sync SDI node secret file for server IP_address on the standby unit. Explanation An error occurred when the VPN failover subsystem tried to synchronize a node secret
file for the SDI server on the standby unit. The SDI node secret file is stored in flash. The error may indicate that the flash file system is full or corrupted.

unitEither Primary or Secondary IP_addressIP address of the server
Recommended Action Use the dir command to display the flash contents. The node secret file has the
filename, ip.sdi.
720048
Error Message %ASA-7-720048: (VPN-unit) FSM action trace begin: state=state, last event=event, func=function. Explanation A VPN failover subsystem finite state machine function has started.
1-490
Chapter 1
stateCurrent state eventLast event functionCurrent executing function
720049
Error Message %ASA-7-720049: (VPN-unit) FSM action trace end: state=state, last event=event, return=return, func=function. Explanation A VPN failover subsystem finite state machine function has finished.
unitEither Primary or Secondary stateCurrent state eventLast event returnReturn code functionCurrent executing function
720050
Error Message %ASA-7-720050: (VPN-unit) Failed to remove timer. ID = id. Explanation A timer cannot be removed from the timer processing thread.
unitEither Primary or Secondary idTimer ID
720051
Error Message %ASA-4-720051: (VPN-unit) Failed to add new SDI node secret file for server id on the standby unit. Explanation An error occurred when the VPN failover subsystem tried to add a node secret file for
the SDI server on the standby unit. The SDI node secret file is stored in flash. The error may indicate that the flash file system is full or corrupted.
1-491
Syslog Messages
idIP address of the SDI server
filename, ip.sdi.
720052
Error Message %ASA-4-720052: (VPN-unit) Failed to delete SDI node secret file for server id on the standby unit. Explanation An error occurred when the VPN failover subsystem tried to delete a node secret file on the active unit. The node secret file being deleted may not exist in the flash file system, or there was problem reading the flash file system.
unitEither Primary or Secondary IP_addressIP address of the SDI server
filename, ip.sdi.
720053
Error Message %ASA-4-720053: (VPN-unit) Failed to add cTCP IKE rule during bulk sync, peer=IP_address, port=port Explanation An error occurred when the VPN failover subsystem tried to load a cTCP IKE rule on
the standby unit during bulk synchronization. The standby unit may be under heavy load, and the new IKE rule request may time out before completion.

unitEither Primary or Secondary IP_addressPeer IP address portPeer port number
720054
Error Message %ASA-4-720054: (VPN-unit) Failed to add new cTCP record, peer=IP_address, port=port. Explanation A cTCP record is replicated to the standby unit and cannot be updated. The
corresponding IPsec over cTCP tunnel may not be functioning after failover. The cTCP database may be full, or a record with the same peer IP address and port number exists already.

unitEither Primary or Secondary IP_addressPeer IP address
1-492
Chapter 1
portPeer port number
Recommended Action This may be a temporary condition and may improve when the existing cTCP
tunnel is restored.
720055
Error Message %ASA-4-720055: (VPN-unit) VPN Stateful failover can only be run in single/non-transparent mode. Explanation The VPN subsystem does not start unless it is running in single (nontransparent) mode.
Recommended Action Configure the ASA for the appropriate mode to support VPN failover and
restart the ASA.
720056
Error Message %ASA-6-720056: (VPN-unit) VPN Stateful failover Message Thread is being disabled. Explanation The VPN failover subsystem main message processing thread is disabled when you have
tried to enable failover, but a failover key is not defined. A failover key is required for VPN failover.
720057
Error Message %ASA-6-720057: (VPN-unit) VPN Stateful failover Message Thread is enabled. Explanation The VPN failover subsystem main message processing thread is enabled when failover is enabled and a failover key is defined.
1-493
Syslog Messages
720058
Error Message %ASA-6-720058: (VPN-unit) VPN Stateful failover Timer Thread is disabled. Explanation The VPN failover subsystem main timer processing thread is disabled when the failover key is not defined and failover is enabled.
720059
Error Message %ASA-6-720059: (VPN-unit) VPN Stateful failover Timer Thread is enabled. Explanation The VPN failover subsystem main timer processing thread is enabled when the failover key is defined and failover is enabled.
720060
Error Message %ASA-6-720060: (VPN-unit) VPN Stateful failover Sync Thread is disabled. Explanation The VPN failover subsystem main bulk synchronization processing thread is disabled when failover is enabled, but the failover key is not defined.
unitEither Primary or Secondary.
720061
Error Message %ASA-6-720061: (VPN-unit) VPN Stateful failover Sync Thread is enabled. Explanation The VPN failover subsystem main bulk synchronization processing thread is enabled when failover is enabled and the failover key is defined.
1-494
Chapter 1
720062
Error Message %ASA-6-720062: (VPN-unit) Active unit started bulk sync of state information to standby unit. Explanation The VPN failover subsystem active unit has started bulk synchronization of state information to the standby unit.
720063
Error Message %ASA-6-720063: (VPN-unit) Active unit completed bulk sync of state information to standby. Explanation The VPN failover subsystem active unit has completed bulk synchronization of state information to the standby unit.
720064
Error Message %ASA-4-720064: (VPN-unit) Failed to update cTCP database record for peer=IP_address, port=port during bulk sync. Explanation An error occurred while the VPN failover subsystem attempted to update an existing
cTCP record during bulk synchronization. The cTCP record may have been deleted from the cTCP database on the standby unit and cannot be found.

Recommended Action Search in the message.
1-495
Syslog Messages
720065
Error Message %ASA-4-720065: (VPN-unit) Failed to add new cTCP IKE rule, peer=peer, port=port. Explanation An error occurred when the VPN failover subsystem tried to add a new IKE rule for the
cTCP database entry on the standby unit. The ASA may be under heavy load, and the request for adding a cTCP IKE rule timed out and was never completed.

Recommended Action This may be a temporary condition.
720066
Error Message %ASA-4-720066: (VPN-unit) Failed to activate IKE database. Explanation An error occurred when the VPN failover subsystem tried to activate the IKE security association database while the standby unit was transitioning to the active state. There may be resource-related issues on the standby unit that prevent the IKE security association database from activating.
Recommended Action Use the show failover command to see if the failover pair is still working
correctly and/or look for other IKE-related errors in the message.
720067
Error Message %ASA-4-720067: (VPN-unit) Failed to deactivate IKE database. Explanation An error occurred when the VPN failover subsystem tried to deactivate the IKE security association database while the active unit was transitioning to the standby state. There may be resource-related issues on the active unit that prevent the IKE security association database from deactivating.
correctly and/or look for IKE-related errors in the message.
1-496
Chapter 1
720068
Error Message %ASA-4-720068: (VPN-unit) Failed to parse peer message. Explanation An error occurred when the VPN failover subsystem tried to parse a peer message received on the standby unit. The peer message received on the standby unit cannot be parsed.
Recommended Action Make sure that both active and standby units are running the same version of firmware. Also, use the show failover command to ensure that the failover pair is still working correctly.
720069
Error Message %ASA-4-720069: (VPN-unit) Failed to activate cTCP database. Explanation An error occurred when the VPN failover subsystem tried to activate the cTCP database while the standby unit was transitioning to the active state. There may be resource-related issues on the standby unit that prevent the cTCP database from activating.
correctly and/or look for other cTCP related errors in the message.
720070
Error Message %ASA-4-720070: (VPN-unit) Failed to deactivate cTCP database. Explanation An error occurred when the VPN failover subsystem tried to deactivate the cTCP database while the active unit was transitioning to the standby state. There may be resource-related issues on the active unit that prevent the cTCP database from deactivating.
correctly and/or look for cTCP related errors in the message.
1-497
Syslog Messages
720071
Error Message %ASA-5-720071: (VPN-unit) Failed to update cTCP dynamic data. Explanation An error occurred while the VPN failover subsystem tried to update cTCP dynamic data.
Recommended Action This may be a temporary condition. Because this is a periodic update, wait to
see if the same error recurs. Also, look for other failover-related messages in the message.
720072
Error Message %ASA-5-720072: Timeout waiting for Integrity Firewall Server [interface,ip] to become available. Explanation The Zonelab Integrity Server cannot reestablish a connection before timeout. In an
active/standby failover setup, the SSL connection between a Zonelab Integrity Server and the ASA needs to be reestablished after a failover.

interfaceThe interface to which the Zonelab Integrity Server is connected ipThe IP address of the Zonelab Integrity Server
Recommended Action Check that the configuration on the ASA and the Zonelab Integrity Server match, and verify communication between the ASA and the Zonelab Integrity Server.
720073
Error Message %ASA-4-720073: (VPN-unit) Fail to insert certificate in trustpoint trustpoint on the standby unit. Explanation An error occurred when the VPN failover subsystem tried to insert a certificate in the
trustpoint. This error may be caused by invalid content of the certificate.

unitEither Primary or Secondary trustpointName of the trustpoint
Recommended Action Use the write standby command on the active unit to replicate the certificate
to the standby unit manually. Search in the message to see if there are any failover or PKI-related errors.
1-498
Chapter 1
721001
Error Message %ASA-6-721001: (device) WebVPN Failover SubSystem started successfully.(device) either WebVPN-primary or WebVPN-secondary. Explanation The WebVPN failover subsystem in the current failover unit, either primary or secondary, has been started successfully.
(device)Either the WebVPN primary or the WebVPN secondary device
721002
Error Message %ASA-6-721002: (device) HA status change: event event, my state my_state, peer state peer. Explanation The WebVPN failover subsystem receives status notification from the core HA
component periodically. The incoming event, the new state of the local ASA, and the new state of the failover peer are reported.

(device)Either the WebVPN primary or the WebVPN secondary ASA eventNew HA event my_stateThe new state of the local ASA peerThe new state of the peer
721003
Error Message %ASA-6-721003: (device) HA progression change: event event, my state my_state, peer state peer. Explanation The WebVPN failover subsystem transitions from one state to another state based on the
event notified by the core HA component. The incoming event, the new state of the local ASA, and the new state of the failover peer are being reported.

(device)Either the WebVPN primary or the WebVPN secondary ASA eventNew HA event my_stateThe new state of the local ASA peerThe new state of the peer
1-499
Syslog Messages
721004
Error Message %ASA-6-721004: (device) Create access list list_name on standby unit. Explanation A WebVPN-specific access list is replicated from the active unit to the standby unit. A
successful installation of the WebVPN access list on the standby unit has occurred.

(device)Either the WebVPN primary or the WebVPN secondary ASA list_nameThe access list name
721005
Error Message %ASA-6-721005: (device) Fail to create access list list_name on standby unit. Explanation When a WebVPN-specific access list is installed on the active unit, a copy is installed on the standby unit. The access list failed to be installed on the standby unit. The access list may have existed on the standby unit already.
(device)Either the WebVPN primary or the WebVPN secondary ASA list_nameName of the access list that failed to install on the standby unit
Recommended Action Use the show access-list command on both the active and standby units. Compare the content of the output and determine whether there is any discrepancy. Resynchronize the standby unit, if needed, by using the write standby command on the active unit.
721006
Error Message %ASA-6-721006: (device) Update access list list_name on standby unit. Explanation The content of the access list has been updated on the standby unit.
(device)Either the WebVPN primary or the WebVPN- econdary ASA list_nameName of the access list that was updated
1-500
Chapter 1
721007
Error Message %ASA-4-721007: (device) Fail to update access list list_name on standby unit. Explanation An error occurred while the standby unit tried to update a WebVPN-specific access list.
The access list cannot be located on the standby unit.

(device)Either the WebVPN primary or the WebVPN-= secondary ASA list_nameName of the access list that was not updated
Recommended Action Use a show access-list command on both the active and standby units. Compare the content of the output and determine whether or not there is any discrepancy. Resynchronize the standby unit, if needed, by using the write standby command on the active unit.
721008
Error Message %ASA-6-721008: (device) Delete access list list_name on standby unit. Explanation When a WebVPN-specific access list is removed from the active unit, a message is sent
to the standby unit requesting that the same access list be removed. As a result, a WebVPN-specific access list has been removed from the standby unit.

(device)Either the WebVPN primary or the WebVPN secondary ASA list_nameName of the access list that was removed
721009
Error Message %ASA-6-721009: (device) Fail to delete access list list_name on standby unit. Explanation When a WebVPN-specific access list is removed on the active unit, a message is sent to the standby unit requesting the same access list be removed. An error condition occurred when an attempt was made to remove the corresponding access list on the standby unit. The access list did not exist on the standby unit.
(device)Either the WebVPN primary or the WebVPN secondary ASA list_nameName of the access list that was deleted
Recommended Action Use a show access-list command on both the active and standby units. Compare the content of the output and determine whether there is any discrepancy. Resynchronize the standby unit, if needed, by using the write standby command on the active unit.
1-501
Syslog Messages
721010
Error Message %ASA-6-721010: (device) Add access list rule list_name, line line_no on standby unit. Explanation When an access list rule is added to the active unit, the same rule is added on the standby
unit. A new access list rule was added successfully on the standby unit.

(device)Either the WebVPN primary or the WebVPN secondary ASA list_nameName of the access list that was deleted line_noLine number of the rule added to the access list
721011
Error Message %ASA-4-721011: (device) Fail to add access list rule list_name, line line_no on standby unit. Explanation When an access list rule is added to the active unit, an attempt is made to add the same
access list rule to the standby unit. An error occurred when an attempt is made to add a new access list rule to the standby unit. The same access list rule may exist on the standby unit.

(device)Either the WebVPN primary or the WebVPN secondary ASA list_nameName of the access list that was deleted line_noLine number of the rule added to the access list
Recommended Action Use a show access-list command on both the active and standby units. Compare the content of the output and determine if there is any discrepancy. Resynchronize the standby unit, if needed, by using the write standby command on the active unit.
721012
Error Message %ASA-6-721012: (device) Enable APCF XML file file_name on the standby unit. Explanation When an APCF XML file is installed on the active unit, an attempt is made to install the
same file on the standby unit. An APCF XML file was installed successfully on the standby unit. Use the dir command on the standby unit to show that the XML file exists in the flash file system.

(device)Either the WebVPN primary or the WebVPN secondary ASA file_nameName of the XML file on the flash file system
1-502
Chapter 1
721013
Error Message %ASA-4-721013: (device) Fail to enable APCF XML file file_name on the standby unit. Explanation When an APCF XML file is installed on the active unit, an attempt is made to install the same file on the standby unit. An APCF XML file failed to install on the standby unit.
Recommended Action Use a dir command on both the active and standby unit. Compare the directory listing and determine if there is any discrepancy. Resynchronize the standby unit, if needed, by using the write standby command on the active unit.
721014
Error Message %ASA-6-721014: (device) Disable APCF XML file file_name on the standby unit. Explanation When an APCF XML file is removed on the active unit, an attempt is made to remove
the same file on the standby unit. An APCF XML file was removed from the standby unit successfully.

721015
Error Message %ASA-4-721015: (device) Fail to disable APCF XML file file_name on the standby unit. Explanation When an APCF XML file is removed on the active unit, an attempt is made to remove
the same file on the standby unit. An error occurred when an attempt was made to remove an APCF XML file from the standby unit. The file may not be installed on the standby unit.

Recommended Action Use a show running-config webvpn command to make sure the APCF XML
file of interest is not enabled. As long as it is not enabled, you may ignore this message. Otherwise, try to disable the file by using the no apcf file_name command in the webvpn configuration submode.
1-503
Syslog Messages
721016
Error Message %ASA-6-721016: (device) WebVPN session for client user user_name, IP ip_address has been created. Explanation A remote WebVPN user has logged in successfully and the login information has been
installed on the standby unit.

(device)Either the WebVPN primary or the WebVPN secondary ASA user_nameName of the user ip_addressIP address of the remote user
721017
Error Message %ASA-4-721017: (device) Fail to create WebVPN session for user user_name, IP ip_address. Explanation When a WebVPN user logs in to the active unit, the login information is replicated to
the standby unit. An error occurred while replicating the login information to the standby unit.

Recommended Action Use the show vpn-sessiondb detail webvpn command for a regular WebVPN
user, or the show vpn-sessiondb detail svc command for a WebVPN SVC user on both the active and standby units. Compare the entries and determine whether the same user session record appears on both ASAs. Resynchronize the standby unit, if needed, by using the write standby command on the active unit.
721018
Error Message %ASA-6-721018: (device) WebVPN session for client user user_name, IP ip_address has been deleted. Explanation When a WebVPN user logs out on the active unit, a logout message is sent to the standby
unit to remove the user session from the standby unit. A WebVPN user record was removed from the standby unit successfully.

1-504
Chapter 1
721019
Error Message %ASA-4-721019: (device) Fail to delete WebVPN session for client user user_name, IP ip_address. Explanation When a WebVPN user logs out on the active unit, a logout message is sent to the standby
unit to remove the user session from the standby unit. An error occurred when an attempt was made to remove a WebVPN user record from the standby unit.

Recommended Action Use the show vpn-sessiondb detail webvpn command for a regular WebVPN
user, or the show vpn-sessiondb detail svc command for a WebVPN SVC user on both the active and standby units. Check whether there is any discrepancy. Resynchronize the standby unit, if needed, by using the write standby command on the active unit.
722001
Error Message %ASA-4-722001: IP IP_address Error parsing SVC connect request. Explanation The request from the SVC was invalid. Recommended Action Research as necessary to determine if this error was caused by a defect in the
SVC, an incompatible SVC version, or an attack against the device.
722002
Error Message %ASA-4-722002: IP IP_address Error consolidating SVC connect request. Explanation There is not enough memory to perform the action. Recommended Action Purchase more memory, upgrade the device, or reduce the load on the device.
722003
Error Message %ASA-4-722003: IP IP_address Error authenticating SVC connect request. Explanation The user took too long to download and connect. Recommended Action Increase the timeouts for session idle and maximum connect time.
1-505
Syslog Messages
722004
Error Message %ASA-4-722004: Group group User user-name IP IP_address Error responding to SVC connect request. Explanation There is not enough memory to perform the action. Recommended Action Purchase more memory, upgrade the device, or reduce the load on the device.
722005
Error Message %ASA-5-722005: Group group User user-name IP IP_address Unable to update session information for SVC connection. Explanation There is not enough memory to perform the action. Recommended Action Purchase more memory, upgrade the device, or reduce the load on the device.
722006
Error Message %ASA-5-722006: Group group User user-name IP IP_address Invalid address IP_address assigned to SVC connection. Explanation An invalid address was assigned to the user. Recommended Action Verify and correct the address assignment, if possible. Otherwise, notify your network administrator or escalate this issue according to your security policy. For additional assistance, contact the Cisco TAC.
722007
Error Message %ASA-3-722007: Group group User user-name IP IP_address SVC Message: type-num/ERROR: message Explanation The SVC issued a message.
type-num A number from 0 to 31 indicating a message type. Message types are as follows: - 0Normal - 16Logout - 17Closed due to error - 18Closed due to rekey - 1-15, 19-31Reserved and unused
1-506
Chapter 1
messageA text message from the SVC
722008
type-num A number from 0 to 31 indicating a message type. Message types are as follows: - 0Normal - 16Logout - 17Closed due to error - 18Closed due to rekey - 1-15, 19-31Reserved and unused messageA text message from the SVC
722009
1-507
Syslog Messages
722010
Error Message %ASA-5-722010: Group group User user-name IP IP_address SVC Message: type-num/NOTICE: message Explanation The SVC issued a message.
722011
Error Message %ASA-5-722011: Group group User user-name IP IP_address SVC Message: type-num/NOTICE: message Explanation The SVC issued a message.
722012
Error Message %ASA-5-722012: Group group User user-name IP IP_address SVC Message: type-num/INFO: message Explanation The SVC issued a message.
type-num A number from 0 to 31 indicating a message type. Message types are as follows: - 0Normal - 16Logout
1-508
Chapter 1
- 17Closed due to error - 18Closed due to rekey - 1-15, 19-31Reserved and unused
messageA text message from the SVC
722013
722014
type-num A number from 0 to 31 indicating a message type. Message types are as follows: - 0Normal. - 16Logout - 17Closed due to error - 18Closed due to rekey - 1-15, 19-31Reserved and unused messageA text message from the SVC
1-509
Syslog Messages
722015
Error Message %ASA-4-722015: Group group User user-name IP IP_address Unknown SVC frame type: type-num Explanation The SVC sent an invalid frame type to the device, which might be caused by an SVC version incompatibility.
type-numThe number identifier of the frame type
Recommended Action Verify the SVC version.
722016
Error Message %ASA-4-722016: Group group User user-name IP IP_address Bad SVC frame length: length expected: expected-length Explanation The expected amount of data was not available from the SVC, which might be caused
by an SVC version incompatibility.

722017
Error Message %ASA-4-722017: Group group User user-name IP IP_address Bad SVC framing: 525446, reserved: 0 Explanation The SVC sent a badly framed datagram, which might be caused by an SVC version incompatibility. Recommended Action Verify the SVC version.
722018
Error Message %ASA-4-722018: Group group User user-name IP IP_address Bad SVC protocol version: version, expected: expected-version Explanation The SVC sent a version unknown to the device, which might be caused by an SVC
version incompatibility.
1-510
Chapter 1
722019
Error Message %ASA-4-722019: Group group User user-name IP IP_address Not enough data for an SVC header: length Explanation The expected amount of data was not available from the SVC, which might be caused by an SVC version incompatibility. Recommended Action Verify the SVC version.
722020
Error Message %ASA-3-722020: TunnelGroup tunnel_group GroupPolicy group_policy User user-name IP IP_address No address available for SVC connection Explanation Address assignment failed for the AnyConnect session. No IP addresses are available.
tunnel_groupThe name of the tunnel group that the user was assigned to or used to log in group_policyThe name of the group policy that the user was assigned to user-nameThe name of the user with which this message is associated IP_addressThe public IP (Internet) address of the client machine
Recommended Action Check the configuration listed in the ip local ip command to see if enough
addresses exist in the pools that have been assigned to the tunnel group and the group policy. Check the DHCP configuration and status. Check the address assignment configuration. Enable IPAA syslog messages to determine why the AnyConnect client cannot obtain an IP address.
722021
Error Message %ASA-3-722021: Group group User user-name IP IP_address Unable to start compression due to lack of memory resources Explanation There is not enough memory to perform the action. Recommended Action Purchase more memory, upgrade the device, or reduce the load on the device.
722022
Error Message %ASA-6-722022: Group group-name User user-name IP addr (TCP | UDP) connection established (with | without) compression Explanation The TCP or UDP connection was established with or without compression. Recommended Action None required.
1-511
Syslog Messages
722023
Error Message %ASA-6-722023: Group group User user-name IP IP_address SVC connection terminated {with|without} compression Explanation The SVC terminated either with or without compression. Recommended Action None required.
722024
Error Message %ASA-6-722024: SVC Global Compression Enabled Explanation Subsequent SVC connections will be allowed to perform tunnel compression if SVC compression is enabled in the corresponding user or group configuration. Recommended Action None required.
722025
Error Message %ASA-6-722025: SVC Global Compression Disabled Explanation Subsequent SVC connections will not be allowed to perform tunnel compression. Recommended Action None required.
722026
Error Message %ASA-6-722026: Group group User user-name IP IP_address SVC compression history reset Explanation A compression error occurred. The SVC and the ASA corrected it. Recommended Action None required.
722027
Error Message %ASA-6-722027: Group group User user-name IP IP_address SVC decompression history reset Explanation A decompression error occurred. The SVC and the ASA corrected it. Recommended Action None required.
1-512
Chapter 1
722028
Error Message %ASA-5-722028: Group group User user-name IP IP_address Stale SVC connection closed. Explanation An unused SVC connection was closed. Recommended Action None required. However, the client may be having trouble connecting if multiple connections are established. The SVC log should be examined.
722029
Error Message %ASA-7-722029: Group group User user-name IP IP_address SVC Session Termination: Conns: connections, DPD Conns: DPD_conns, Comp resets: compression_resets, Dcmp resets: decompression_resets Explanation The number of connections, reconnections, and resets that have occurred are reported. If connections is greater than 1 or the number of DPD_conns, compression_resets, or decompression_resets is greater than 0, it may indicate network reliability problems, which may be beyond the control of the ASA administrator. If there are many connections or DPD connections, the user may be having problems connecting and may experience poor performance.
connectionsThe total number of connections during this session (one is normal) DPD_connsThe number of reconnections due to DPD compression_resetsThe number of compression history resets decompression_resetsThe number of decompression history resets
Recommended Action The SVC log should be examined. You may want to research and take appropriate action to resolve possible network reliability problems.
722030
Error Message %ASA-7-722030: Group group User user-name IP IP_address SVC Session Termination: In: data_bytes (+ctrl_bytes) bytes, data_pkts (+ctrl_pkts) packets, drop_pkts drops Explanation End-of-session statistics are being recorded.
data_bytesThe number of inbound (from SVC) data bytes ctrl_bytesThe number of inbound control bytes data_pktsThe number of inbound data packets ctrl_pktsThe number of inbound control packets drop_pktsThe number of inbound packets that were dropped
1-513
Syslog Messages
722031
Error Message %ASA-7-722031: Group group User user-name IP IP_address SVC Session Termination: Out: data_bytes (+ctrl_bytes) bytes, data_pkts (+ctrl_pkts) packets, drop_pkts drops. Explanation End-of-session statistics are being recorded.
data_bytesThe number of outbound (to SVC) data bytes ctrl_bytesThe number of outbound control bytes data_pktsThe number of outbound data packets ctrl_pktsThe number of outbound control packets ctrl_pktsThe number of outbound packets that were dropped
722032
Error Message %ASA-5-722032: Group group User user-name IP IP_address New SVC connection replacing old connection. Explanation A new SVC connection is replacing an existing one. You may be having trouble
connecting.
Recommended Action Examine the SVC log.
722033
Error Message %ASA-5-722033: Group group User user-name IP IP_address First SVC connection established for SVC session. Explanation The first SVC connection was established for the SVC session. Recommended Action None required.
722034
Error Message %ASA-5-722034: Group group User user-name IP IP_address New SVC connection, no existing connection. Explanation A reconnection attempt has occurred. An SVC connection is replacing a previously closed connection. There is no existing connection for this session because the connection was already dropped by the SVC or the ASA. You may be having trouble connecting. Recommended Action Examine the ASA log and SVC log.
1-514
Chapter 1
722035
Error Message %ASA-3-722035: Group group User user-name IP IP_address Transmitting large packet length (threshold +num). Explanation A large packet was sent to the client. The source of the packet may not be aware of the MTU of the client.
lengthThe length of the large packet +numThe threshold
722036
Error Message %ASA-3-722036: Group group User user-name IP IP_address Received large packet length (threshold +num). Explanation A large packet was sent to the client. The packets that were arriving on the ASA had the
DF bit set, and the ASA was unable to fragment it.

lengthThe length of the large packet +numThe threshold
Recommended Action Enter the anyconnect ssl df-bit-ignore enable command under the group
policy to allow the ASA to fragment the packets arriving with the DF bit set.
722037
Error Message %ASA-5-722037: Group group User user-name IP IP_address SVC closing connection: reason. Explanation An SVC connection was terminated for the given reason. This behavior may be normal, or you may be having trouble connecting.
reasonThe reason that the SVC connection was terminated
Recommended Action Examine the SVC log.
1-515
Syslog Messages
722038
Error Message %ASA-5-722038: Group group-name User user-name IP IP_address SVC terminating session: reason. Explanation An SVC session was terminated for the given reason. This behavior may be normal, or you may be having trouble connecting.
reasonThe reason that the SVC session was terminated
Recommended Action Examine the SVC log if the reason for termination was unexpected.
722039
Error Message %ASA-4-722039: Group group, User user, IP ip, SVC vpn-filter acl is an IPv6 ACL; ACL not applied. Explanation The type of ACL to be applied is incorrect. An IPv6 ACL has been configured as an IPv4
ACL through the vpn-filter command.

groupThe group policy name of the user userThe username ipThe public (not assigned) IP address of the user aclThe name of the invalid ACL
Recommended Action Validate the VPN filter and IPv6 VPN filter configurations on the ASA, and the filter parameters on the AAA (RADIUS) server. Make sure that the correct type of ACL is specified.
722040
Error Message %ASA-4-722040: Group group, User user, IP ip, SVC 'ipv6-vpn-filter acl' is an IPv4 ACL; ACL not applied Explanation The type of ACL to be applied is incorrect. An IPv4 ACL has been configured as an IPv6 ACL through the ipv6-vpn-filter command.
groupThe group policy name of the user userThe username ipThe public (not assigned) IP address of the user aclThe name of the invalid ACL
Recommended Action Validate the VPN filter and IPv6 VPN filter configurations on the ASA and the filter parameters on the AAA (RADIUS) server. Make sure that the correct type of ACL is specified.
1-516
Chapter 1
722041
Error Message %ASA-4-722041: TunnelGroup tunnel_group GroupPolicy group_policy User username IP peer_address No IPv6 address available for SVC connection. Explanation An IPv6 address was not available for assignment to the remote SVC client.
nThe SVC connection identifier
Recommended Action Augment or create an IPv6 address pool, if desired.
722042
Error Message %ASA-4-722042: Group group User user IP ip Invalid Cisco SSL Tunneling Protocol version. Explanation An invalid SVC or AnyConnect client is trying to connect.
groupThe name of the group policy with which the user is trying to connect userThe name of the user who is trying to connect ipThe IP address of the user who is trying to connect
Recommended Action Validate that the SVC or AnyConnect client is compatible with the ASA.
722043
Error Message %ASA-5-722043: Group group User user IP ip DTLS disabled: unable to negotiate cipher. Explanation The DTLS (UDP transport) cannot be established. The SSL encryption configuration
was probably changed.

Recommended Action Revert the SSL encryption configuration. Make sure there is at least one block cipher (AES, DES, or 3DES) in the SSL encryption configuration.
1-517
Syslog Messages
722044
Error Message %ASA-5-722044: Group group User user IP ip Unable to request ver address for SSL tunnel. Explanation An IP address cannot be requested because of low memory on the ASA.
groupThe name of the group policy with which the user is trying to connect userThe name of the user who is trying to connect ipThe IP address of the user who is trying to connect verEither IPv4 or IPv6, based on the IP address version being requested
Recommended Action Reduce the load on the ASA or add more memory.
722045
Error Message %ASA-3-722045: Connection terminated: no SSL tunnel initialization data. Explanation Data to establish a connection is missing. This is a defect in the ASA software. Recommended Action Contact the Cisco TAC for assistance.
722046
Error Message %ASA-3-722046: Group group User user IP ip Session terminated: unable to establish tunnel. Explanation The ASA cannot set up connection parameters. This is a defect in the ASA software.
1-518
Chapter 1
722047
Error Message %ASA-4-722047: Group group User user IP ip Tunnel terminated: SVC not enabled or invalid SVC image on the ASA. Explanation The user logged in via the web browser and tried to start the SVC or AnyConnect client. The SVC service is not enabled globally, or the SVC image is invalid or corrupted. The tunnel connection has been terminated, but the clientless connection remains.
Recommended Action Enable the SVC globally using the svc enable command. Validate the integrity
of versions of the SVC images by reloading new images using the svc image command.
722048
Error Message %ASA-4-722048: Group group User user IP ip Tunnel terminated: SVC not enabled for the user. Explanation The user logged in via the web browser, and tried to start the SVC or AnyConnect client. The SVC service is not enabled for this user. The tunnel connection has been terminated, but the clientless connection remains.
Recommended Action Enable the service for this user using the group-policy and username
commands.
722049
Error Message %ASA-4-722049: Group group User user IP ip Session terminated: SVC not enabled or invalid image on the ASA. Explanation The user logged in via the AnyConnect client. The SVC service is not enabled globally,
or the SVC image is invalid or corrupted. The session connection has been terminated.

Recommended Action Enable the SVC globally using the svc-enable command. Validate the integrity and versions of the SVC images by reloading new images using the svc image command.
1-519
Syslog Messages
722050
Error Message %ASA-4-722050: Group group User user IP ip Session terminated: SVC not enabled for the user. Explanation The user logged in through the AnyConnect client. The SVC service is not enabled for
this user. The session connection has been terminated.

Recommended Action Enable the service for this user using the group-policy and username
commands.
722051
Error Message %ASA-6-722051: Group group-policy User username IP public-ip IPv4 Address assigned-ip IPv6 Address assigned-ip assigned to session Explanation The specified address has been assigned to the given user.
group-policyThe group policy that allowed the user to gain access usernameThe name of the user public-ipThe public IP address of the connected client assigned-ipThe IPv4 or IPv6 address that is assigned to the client
722053
Error Message %ASA-6-722053: Group g User u IP ip Unknown client user-agent connection. Explanation An unknown or unsupported SSL VPN client has connected to the ASA. Older clients
include the Cisco SVC and the Cisco AnyConnect client earlier than Version 2.3.1.

gThe group policy under which the user logged in uThe name of the user ipThe IP address of the client user-agentThe user agent (usually includes the version) received from the client
Recommended Action Upgrade to a supported Cisco SSL VPN client.
1-520
Chapter 1
723001
Error Message %ASA-6-723001: Group group-name, User user-name, IP IP_address: WebVPN Citrix ICA connection connection is up. Explanation The Citrix connection is up.
group-nameThe name of the Citrix group user-nameThe name of the Citrix user IP_addressThe IP address of the Citrix user connectionThe Citrix connection identifier
723002
Error Message %ASA-6-723002: Group group-name, User user-name, IP IP_address: WebVPN Citrix ICA connection connection is down. Explanation The Citrix connection is down.
Recommended Action No action is required when the Citrix ICA connection is terminated intentionally by the client, the server, or the ASA administrator. However, if this is not the case, verify that the WebVPN session in which the Citrix ICA connection is set up is still active. If it is inactive, then receiving this message is normal. If the WebVPN session is still active, verify that the ICA client and Citrix server both work correctly and that there is no error displayed. If not, bring either or both up or respond to any error. If this message is still received, contact the Cisco TAC and provide the following information:
Network topology Delay and packet loss Citrix server configuration Citrix ICA client information Steps to reproduce the problem Complete text of all associated messages
1-521
Syslog Messages
723003
Error Message %ASA-7-723003: No memory for WebVPN Citrix ICA connection connection. Explanation The ASA is running out of memory. The Citrix connection was rejected.
connectionThe Citrix connection identifier
Recommended Action Verify that the ASA is working correctly. Pay special attention to memory and
buffer usage. If the ASA is under heavy load, buy more memory and upgrade the ASA or reduce the load on the ASA. If the problem persists, contact the Cisco TAC.
723004
Error Message %ASA-7-723004: WebVPN Citrix encountered bad flow control flow. Explanation The ASA encountered an internal flow control mismatch, which can be caused by
massive data flow, such as might occur during stress testing or with a high volume of ICA connections.
Recommended Action Reduce ICA connectivity to the ASA. If the problem persists, contact the Cisco
TAC.
723005
Error Message %ASA-7-723005: No channel to set up WebVPN Citrix ICA connection. Explanation The ASA was unable to create a new channel for Citrix. Recommended Action Verify that the Citrix ICA client and the Citrix server are still alive. If not, bring them back up and retest. Check the ASA load, paying special attention to memory and buffer usage. If the ASA is under heavy load, upgrade the ASA, add memory, or reduce the load. If the problem persists, contact the Cisco TAC.
723006
Error Message %ASA-7-723006: WebVPN Citrix SOCKS errors. Explanation An internal Citrix SOCKS error has occurred on the ASA. Recommended Action Verify that the Citrix ICA client is working correctly. In addition, check the
network connection status between the Citrix ICA client and the ASA, paying attention to packet loss. Resolve any abnormal network conditions. If the problem persists, contact the Cisco TAC.
1-522
Chapter 1
723007
Error Message %ASA-7-723007: WebVPN Citrix ICA connection connection list is broken. Explanation The ASA internal Citrix connection list is broken.
Recommended Action Verify that the ASA is working correctly, paying special attention to memory
and buffer usage. If the ASA is under heavy load, upgrade the ASA, add memory, or reduce the load. If the problem persists, contact the Cisco TAC.
723008
Error Message %ASA-7-723008: WebVPN Citrix ICA SOCKS Server server is invalid. Explanation An attempt was made to access a Citrix Socks server that does not exist.
serverThe Citrix server identifier
Recommended Action Verify that the ASA is working correctly. Note whether or not there is any
memory or buffer leakage. If this issue occurs frequently, capture information about memory usage, network topology, and the conditions during which this message is received. Send this information to the Cisco TAC for review. Make sure that the WebVPN session is still up while this message is being received. If not, determine the reason that the WebVPN session is down. If the ASA is under heavy load, upgrade the ASA, add memory, or reduce the load. If the problem persists, contact the Cisco TAC.
723009
Error Message %ASA-7-723009: Group group-name, User user-name, IP IP_address: WebVPN Citrix received data on invalid connection connection. Explanation Data was received on a Citrix connection that does not exist.
Recommended Action The original published Citrix application connection was probably terminated, and the remaining active published applications lost connectivity. Restart all published applications to generate a new Citrix ICA tunnel. If the ASA is under heavy load, upgrade the ASA, add memory, or reduce the load. If the problem persists, contact the Cisco TAC.
1-523
Syslog Messages
723010
Error Message %ASA-7-723010: Group group-name, User user-name, IP IP_address: WebVPN Citrix received closing channel channel for invalid connection connection. Explanation An abort was received on a nonexistent Citrix connection, which can be caused by
massive data flow (such as stress testing) or a high volume of ICA connections, especially during network delay or packet loss.

group-nameThe name of the Citrix group user-nameThe name of the Citrix user IP_addressThe IP address of the Citrix user channelThe Citrix channel identifier connectionThe Citrix connection identifier
Recommended Action Reduce the number of ICA connections to the ASA, obtain more memory for the ASA, or resolve the network problems.
723011
Error Message %ASA-7-723011: Group group-name, User user-name, IP IP_address: WebVPN Citrix receives bad SOCKS socks message length msg-length. Expected length is exp-msg-length. Explanation The Citrix SOCKS message length is incorrect.
group-nameThe name of the Citrix group user-nameThe name of the Citrix user IP_addressThe IP address of the Citrix user
Recommended Action Verify that the Citrix ICA client is working correctly. In addition, check the
network connection status between the ICA client and the ASA, paying attention to packet loss. After resolving any abnormal network conditions, if the problem still exists, contact the Cisco TAC.
723012
Error Message %ASA-7-723012: Group group-name, User user-name, IP IP_address: WebVPN Citrix received bad SOCKS socks message format. Explanation The Citrix SOCKS message format is incorrect.
group-nameThe name of the Citrix group user-nameThe name of the Citrix user
1-524
Chapter 1
IP_addressThe IP address of the Citrix user
Recommended Action Verify that the Citrix ICA client is working correctly. In addition, check the
network connection status between the ICA client and the ASA, paying attention to packet loss. After resolving any abnormal network conditions, if the problem still exists, contact the Cisco TAC.
723013
Error Message %ASA-7-723013: WebVPN Citrix encountered invalid connection connection during periodic timeout. Explanation The ASA internal Citrix timer has expired, and the Citrix connection is invalid.
Recommended Action Check the network connection between the Citrix ICA client and the ASA, and between the ASA and the Citrix server. Resolve any abnormal network conditions, especially delay and packet loss. Verify that the ASA works correctly, paying special attention to memory or buffer problems. If the ASA is under heavy load, obtain more memory, upgrade the ASA, or reduce the load. If the problem persists, contact the Cisco TAC.
723014
Error Message %ASA-7-723014: Group group-name, User user-name, IP IP_address: WebVPN Citrix TCP connection connection to server server on channel channel initiated. Explanation The ASA internal Citrix Secure Gateway is connected to the Citrix server.
group-nameThe name of the Citrix group user-nameThe name of the Citrix user IP_addressThe IP address of the Citrix user connectionThe connection name serverThe Citrix server identifier channelThe Citrix channel identifier (hexadecimal)
724001
Error Message %ASA-4-724001: Group group-name User user-name IP IP_address WebVPN session not allowed. Unable to determine if Cisco Secure Desktop was running on the client's workstation. Explanation The session was not allowed because an error occurred during processing of the CSD
Host Integrity Check results on the ASA.
group-nameThe name of the group
1-525
Syslog Messages
user-nameThe name of the user IP_addressThe IP address
Recommended Action Determine whether the client firewall is truncating long URLs. Uninstall CSD
from the client and reconnect to the ASA.
724002
Error Message %ASA-4-724002: Group group-name User user-name IP IP_address WebVPN session not terminated. Cisco Secure Desktop was not running on the client's workstation. Explanation CSD is not running on the client machine.
Recommended Action Verify that the end user can install and run CSD on the client machine.
725001
Error Message %ASA-6-725001 Starting SSL handshake with remote_device interface_name: IP_address/port for SSL_version session. Explanation The SSL handshake has started with the remote device.
remote_deviceEither the server or the client, depending on the device that initiated the connection interface_nameThe interface that the SSL session is using IP_addressThe remote device IPv4 or IPv6 address portThe remote device IP port number SSL_versionThe SSL version for the SSL handshake (SSLv3 or TLSv1)
725002
Error Message %ASA-6-725002 Device completed SSL handshake with remote_device interface_name: IP_address/port Explanation The SSL handshake has completed successfully with the remote device.
remote_deviceEither the server or the client, depending on the device that initiated the connection
1-526
Chapter 1
interface_nameThe interface that the SSL session is using IP_addressThe remote device IPv4 or IPv6 address portThe remote device IP port number
725003
Error Message %ASA-6-725003 SSL client interface_name: IP_address/port request to resume previous session. Explanation The remote device is trying to resume a previous SSL session.
725004
Error Message %ASA-6-725004 Device requesting certificate from SSL client interface_name: IP_address/port for authentication. Explanation The ASA has requested a client certificate for authentication.
725005
Error Message %ASA-6-725005 SSL server interface_name: IP_address/port requesting our device certificate for authentication. Explanation The server has requested the certificate of the ASA for authentication.
1-527
Syslog Messages
725006
Error Message %ASA-6-725006 Device failed SSL handshake with remote_device interface_name: IP_address/port Explanation The SSL handshake with the remote device has failed.
remote_deviceEither the server or the client, depending on the device that initiates the connection interface_nameThe interface that the SSL session is using IP_addressThe remote device IPv4 or IPv6 address portThe remote device IP port number
Recommended Action Look for syslog message 725014, which indicates the reason for the failure.
725007
Error Message %ASA-6-725007 SSL session with remote_device interface_name: IP_address/port terminated. Explanation The SSL session has terminated.
remote_deviceEither the server or the client, depending on the device that initiates the connection interface_nameThe interface that the SSL session is using IP_addressThe remote device IP address portThe remote device IP port number
725008
Error Message %ASA-7-725008 SSL client interface_name: IP_address/port proposes the following number cipher(s). Explanation The number of ciphers proposed by the remote SSL device are listed.
interface_nameThe interface that the SSL session is using IP_addressThe remote device IP address portThe remote device IP port number numberThe number of ciphers in the proposal
1-528
Chapter 1
725009
Error Message %ASA-7-725009 Device proposes the following number cipher(s) to SSL server interface_name: IP_address/port. Explanation The number of ciphers proposed to the SSL server are listed.
numberThe number of ciphers in the proposal interface_nameThe interface that the SSL session is using IP_addressThe remote device IP address portThe remote device IP port number
725010
Error Message %ASA-7-725010 Device supports the following number cipher(s). Explanation The number of ciphers supported by the ASA for an SSL session are listed.
numberThe number of supported ciphers
725011
Error Message %ASA-7-725011 Cipher[order]: cipher_name Explanation Always following messages 725008, 725009, and 725010, this message indicates the cipher name and its order of preference.
orderThe order of the cipher in the cipher list cipher_nameThe name of the cipher from the cipher list
725012
Error Message %ASA-7-725012 Device chooses cipher: cipher_name for SSL session with client interface_name:IP_address/port Explanation The cipher that was chosen by the Cisco device for the SSL session is listed.
cipher_nameThe name of the cipher from the cipher list interface_nameThe interface that the SSL session is using
1-529
Syslog Messages
IP_addressThe remote device IP address portThe remote device IP port number
725013
Error Message %ASA-7-725013 SSL Server interface_name:IP_address/port chooses cipher: cipher_name Explanation The cipher that was chosen by the server for the SSL session is identified.
cipher_nameThe name of the cipher from the cipher list interface_nameThe interface that the SSL session is using IP_addressThe remote device IP address portThe remote device IP port number
725014
Error Message %ASA-7-725014 SSL lib error. Function: function Reason: reason Explanation The reason for failure of the SSL handshake is indicated.
functionThe function name where the failure is reported reasonThe description of the failure condition
Recommended Action Include this message when reporting any SSL-related issue to the Cisco TAC.
725015
Error Message %ASA-3-725015 Error verifying client certificate. Public key size in client certificate exceeds the maximum supported key size. Explanation The verification of an SSL client certificate failed because of an unsupported (large) key
size.
Recommended Action Use client certificates with key sizes that are less than or equal to 4096 bits.
1-530
Chapter 1
726001
Error Message %ASA-6-726001: Inspected im_protocol im_service Session between Client im_client_1 and im_client_2 Packet flow from src_ifc:/sip/sport to dest_ifc:/dip/dport Action: action Matched Class class_map_id class_map_name Explanation An IM inspection was performed on an IM message and the specified criteria were
satisfied. The configured action is taken.

im_protocolMSN IM or Yahoo IM im_serviceThe IM services, such as chat, conference, file transfer, voice, video, games, or unknown im_client_1, im_client_2The client peers that are using the IM service in the session: client_login_name or ? src_ifcThe source interface name sipThe source IP address sportThe source port dest_ifcThe destination interface name dipThe destination IP address dportThe destination port actionThe action taken: reset connection, dropped connection, or received class_map_idThe matched class-map ID class_map_nameThe matched class-map name
730001
Error Message %ASA-7-730001 Group groupname, User username, IP ipaddr: VLAN MAPPING to VLAN vlanid Explanation VLAN mapping succeeded.
groupnameThe group name usernameThe username ipaddrThe IP address of this session vlanid The VLAN ID that is used for the VLAN mapping session
1-531
Syslog Messages
730002
Error Message %ASA-7-730002 Group groupname, User username, IP ipaddr: VLAN MAPPING to VLAN vlanid failed Explanation VLAN mapping failed.
Recommended Action Verify that all the VLAN mapping-related configurations are correct, and that the VLAN ID is valid.
730003
Error Message %ASA-7-730003: NACApp sets IP ipaddr VLAN to vlanid Explanation ASA receives an SNMP set message from NACApp to set the new VLAN ID for the
session.

ipaddrThe IP address of this session vlanid The VLAN ID that is used for the VLAN mapping session
730004
Error Message %ASA-6-730004: Group groupname User username IP ipaddr VLAN ID vlanid from AAA ignored. Explanation The VLAN ID received from AAA is different from the current one in use, and it is
ignored for the current session.

Recommended Action If the newly received VLAN ID must be used, then the current session needs
to be torn down. Otherwise, no action is required.
1-532
Chapter 1
730005
Error Message %ASA-6-730005: Group groupname User username IP ipaddr VLAN ID vlanid from AAA is invalid. Explanation The VLAN ID received from AAA is invalid.
Recommended Action Verify the VLAN ID configurations on the AAA server and ASA are both
correct.
730006
Error Message %ASA-7-730006: Group groupname, User username, IP ipaddr: is on NACApp AUTH VLAN vlanid. Explanation The session is under NACApp posture assessment.
730007
Error Message %ASA-7-73007: Group groupname, User username, IP ipaddr: changed VLAN to <%s> ID vlanid Explanation NACApp (Cisco NAC appliance) posture assessment is done with the session, the
VLAN is changed from AUTH VLAN to a new VLAN.

groupnameThe group name usernameThe username ipaddrThe IP address of this session

%sA string
vlanid The VLAN ID that is used for the VLAN mapping session
1-533
Syslog Messages
730008
Error Message %ASA-6-730008: Group groupname, User username, IP ipaddr, VLAN MAPPING timeout waiting NACApp. Explanation NACApp (Cisco NAC appliance) posture assessment takes longer than the timeout
value configured.

Recommended Action Check the status of the NACApp setup.
730009
Error Message %ASA-5-730009: Group groupname, User username, IP ipaddr, CAS casaddr, capacity exceeded, terminating connection. Explanation The load capacity of the NACApp (Cisco NAC appliance) CAS is execeeded, the new
incoming session that uses it is terminating.

groupnameThe group name usernameThe username ipaddrThe IP address of this session casaddrThe IP Address of CAS (Clean Access Server)
Recommended Action Review and revise planning for how many groups, and which groups, are associated with the CAS to ensure that its load capacity is not exceeded.
730010
Error Message %ASA-7-730010: Group groupname, User username, IP ipaddr, VLAN Mapping is enabled on VLAN vlanid. Explanation VLAN mapping is enabled in the session.
groupnameThe group name usernameThe username ipaddrThe IP address of this session vlanidThe VLAN ID that is used for the VLAN mapping session
1-534
Chapter 1
731001
Error Message %ASA-6-731001: NAC policy added: name: policyname Type: policytype. Explanation A new NAC-policy has been added to the ASA.
policynameThe NAC policy name policytypeThe type of NAC policy
731002
Error Message %ASA-6-731002: NAC policy deleted: name: policyname Type: policytype. Explanation A NAC policy has been removed from the ASA.
731003
Error Message %ASA-6-731003: nac-policy unused: name: policyname Type: policytype. Explanation The NAC policy is unused because there is an existing NAC policy with the same name,
but a different type.

Recommended Action If the new NAC policy must be used, the existing NAC policy must be removed
first. Otherwise, no action is required.
732001
Error Message %ASA-6-732001: Group groupname, User username, IP ipaddr, Fail to parse NAC-SETTINGS nac-settings-id, terminating connection. Explanation The ASA cannot apply the NAC settings because no memory is available.
1-535
Syslog Messages
nac-settings-id The ID that is used for the NAC filter
Recommended Action Upgrade the ASA memory. Resolve any errors in the log before this problem occurs. If the problem persists, contact the Cisco TAC.
732002
Error Message %ASA-6-732002: Group groupname, User username, IP ipaddr, NAC-SETTINGS settingsid from AAA ignored, existing NAC-SETTINGS settingsid_inuse used instead. Explanation The NAC settings ID cannot be applied because there is a different one for the session.
groupnameThe group name usernameThe username ipaddrThe IP address of this session settingsid The settings ID, which should be a NAC policy name settingsid_inuse The NAC settings ID that is currently in use
Recommended Action If the new NAC settings ID must be applied, then all the active sessions that
use it must be torn down first. Otherwise, no action is required.
732003
Error Message %ASA-6-732003: Group groupname, User username, IP ipaddr, NAC-SETTINGS nac-settings-id from AAA is invalid, terminating connection. Explanation The NAC settings received from AAA are invalid.
groupnameThe group name usernameThe username ipaddrThe IP address of this session nac-settings-id The ID that is used for the NAC filter
Recommended Action Verify that the NAC settings configurations on the AAA server and ASA are
both correct.
1-536
Chapter 1
733100
Error Message %ASA-4-733100: Object drop rate rate_ID exceeded. Current burst rate is rate_val per second, max configured rate is rate_val; Current average rate is rate_val per second, max configured rate is rate_val; Cumulative total count is total_cnt Explanation The specified object in the message has exceeded the specified burst threshold rate or
average threshold rate. The object can be a drop activity of a host, TCP/UDP port, IP protocol, or various drops caused by potential attacks. The ASA may be under attack.
ObjectThe general or particular source of a drop rate count, which might include the following: - Firewall - Bad pkts - Rate limit - DoS attck - ACL drop - Conn limit - ICMP attk - Scanning - SYN attck - Inspect - Interface (A citation of a particular interface object might take a number of forms. For example, you might see 80/HTTP, which would signify port 80, with the well-known protocol HTTP.)
rate_IDThe configured rate that is being exceeded. Most objects can be configured with up to three different rates for different intervals. rate_valA particular rate value. total_cntThe total count since the object was created or cleared.
The following three examples show how these variables occur:

For an interface drop caused by a CPU or bus limitation:
%ASA-4-733100: [Interface] drop rate 1 exceeded. Current burst rate is 1 per second, max configured rate is 8000; Current average rate is 2030 per second, max configured rate is 2000; Cumulative total count is 3930654.
For a scanning drop caused by potential attacks:

ASA-4-733100: [Scanning] drop rate-1 exceeded. Current burst rate is 10 per second_max configured rate is 10; Current average rate is 245 per second_max configured rate is 5; Cumulative total count is 147409 (35 instances received)
For bad packets caused by potential attacks:

%ASA-4-733100: [Bad pkts] drop rate 1 exceeded. Current burst rate is 0 per second, max configured rate is 400; Current average rate is 760 per second, max configured rate is 100; Cumulative total count is 1938933
1-537
Syslog Messages
Because of the scanning rate configured and the threat-detection rate scanning-rate 3600
average-rate 15 command:
%ASA-4-733100: [144.60.88.2] drop rate-2 exceeded. Current burst rate is 0 per second, max configured rate is 8; Current average rate is 5 per second, max configured rate is 4; Cumulative total count is 38086
Recommended Action Perform the following steps according to the specified object type that appears
in the message:
1.
If the object in the message is one of the following:
Firewall Bad pkts Rate limit DoS attck ACL drop Conn limit ICMP attck Scanning SYN attck Inspect Interface
Check whether the drop rate is acceptable for the running environment.
2.
Adjust the threshold rate of the particular drop to an appropriate value by using the threat-detection rate xxx command, where xxx is one of the following:
acl-drop bad-packet-drop conn-limit-drop dos-drop fw-drop icmp-drop inspect-drop interface-drop scanning-threat syn-attack 3. 4.
If the object in the message is a TCP or UDP port, an IP address, or a host drop, check whether or not the drop rate is acceptable for the running environment. Adjust the threshold rate of the particular drop to an appropriate value by using the threat-detection rate bad-packet-drop command.
Note
If you do not want the drop rate exceed warning to appear, you can disable it by using the no threat-detection basic-threat command.
1-538
Chapter 1
733101
Error Message %ASA-4-733101: Object objectIP (is targeted|is attacking). Current burst rate is rate_val per second, max configured rate is rate_val; Current average rate is rate_val per second, max configured rate is rate_val; Cumulative total count is total_cnt. Explanation The ASA detected that a specific host (or several hosts in the same 1024-node subnet)
is either scanning the network (attacking), or is being scanned (targeted).

objectAttacker or target (a specific host or several hosts in the same 1024-node subnet) objectIPThe IP address of the scanning attacker or scanned target rate_valA particular rate value total_cntThe total count
The following two examples show how these variables occur:

%ASA-4-733101: Subnet 100.0.0.0 is targeted. Current burst rate is 200 per second, max configured rate is 0; Current average rate is 0 per second, max configured rate is 0; Cumulative total count is 2028. %ASA-4-733101: Host 175.0.0.1 is attacking. Current burst rate is 200 per second, max configured rate is 0; Current average rate is 0 per second, max configured rate is 0; Cumulative total count is 2024
Recommended Action For the specific host or subnet, use the show threat-detection statistics host ip-address ip-mask command to check the overall situation and then adjust the threshold rate of the scanning threat to the appropriate value. After the appropriate value is determined, an optional action can be taken to shun those host attackers (not subnet attacker) by configuring the threat-detection scanning-threat shun-host command. You may specify certain hosts or object groups in the shun-host except list. For more information, see the CLI configuration guide. If scanning detection is not desirable, you can disable this feature by using the no threat-detection scanning command.
733102
Error Message %ASA-4-733102:Threat-detection adds host %I to shun list Explanation A host has been shunned by the threat detection engine. When the threat-detection scanning-threat shun command is configured, the attacking hosts will be shunned by the threat detection engine.
%IA particular hostname
1-539
Syslog Messages
The following message shows how this command was implemented:

%ASA-4-733102: Threat-detection add host 11.1.1.40 to shun list
Recommended Action To investigate whether the shunned host is an actual attacker, use the
threat-detection statistics host ip-address command. If the shunned host is not an attacker, you can remove the shunned host from the threat detection engine by using the clear threat-detection shun ip address command. To remove all shunned hosts from the threat detection engine, use the clear shun command. If you receive this message because an inappropriate threshold rate has been set to trigger the threat detection engine, then adjust the threshold rate by using the threat-detection rate scanning-threat rate-interval x average-rate y burst-rate z command.
733103
Error Message %ASA-4-733103: Threat-detection removes host %I from shun list Explanation A host has been shunned by the threat detection engine. When you use the clear-threat-detection shun command, the specified host will be removed from the shunned list.
%IA particular hostname
The following message shows how this command is implemented:

%ASA-4-733103: Threat-detection removes host 11.1.1.40 from shun list
733104
Error Message %ASA-4-733104: TD_SYSLOG_TCP_INTERCEPT_AVERAGE_RATE_EXCEED Explanation The ASA is under Syn flood attack and protected by the TCP intercept mechanism, if the average rate for intercepted attacks exceeds the configured threshold. The message is showing which server is under attack and where the attacks are coming from. Recommended Action Write an ACL to filter out the attacks.
733105
Error Message %ASA-4-733105: TD_SYSLOG_TCP_INTERCEPT_BURST_RATE_EXCEED Explanation The ASA is under Syn flood attack and protected by the TCP intercept mechanism, if the burst rate for intercepted attacks exceeds the configured threshold. The message is showing which server is under attack and where the attacks are coming from. Recommended Action Write an ACL to filter out the attacks.
1-540
Chapter 1
734001
Error Message %ASA-6-734001: DAP: User user, Addr ipaddr, Connection connection: The following DAP records were selected for this connection: DAP record names Explanation The DAP records that were selected for the connection are listed.
userThe authenticated username ipaddrThe IP address of the remote client connectionThe type of client connection, which can be one of the following: - IPsec - AnyConnect - Clientless (web browser) - Cut-Through-Proxy - L2TP DAP record namesThe comma-separated list of the DAP record names
734002
Error Message %ASA-5-734002: DAP: User user, Addr ipaddr: Connection terrminated by the following DAP records: DAP record names Explanation The DAP records that terminated the connection are listed.
userThe authenticated username ipaddrThe IP address of the remote client DAP record namesThe comma-separated list of the DAP record names
734003
Error Message %ASA-7-734003: DAP: User name, Addr ipaddr: Session Attribute: attr name/value Explanation The AAA and endpoint session attributes that are associated with the connection are
listed.

userThe authenticated username ipaddrThe IP address of the remote client attr/valueThe AAA or endpoint attribute name and value
1-541
Syslog Messages
734004
Error Message %ASA-3-734004: DAP: Processing error: Code number Explanation A DAP processing error occurred.
numberThe internal error code
Recommended Action Provide the Cisco TAC with the message and information about the conditions that generated the error.
734005
Error Message %ASA-6-734005: DAP: User user, Addr ip: Administrative Message: custom message Explanation DAP CheckAndMsg is configured to generate a custom message that is configured by the ASA administrator.
userThe username being used for the connection ipThe IP address of the endpoint custom messageThe custom message configured in CheckAndMsg
735001
Error Message %ASA-1-735001 IPMI: Cooling Fan var1: OK Explanation A cooling fan has been restored to normal operation.
var1The device number markings
735002
Error Message %ASA-1-735002 IPMI: Cooling Fan var1: Failure Detected Explanation A cooling fan has failed.
Check for obstructions that would prevent the fan from rotating. Replace the cooling fan.
1-542
Chapter 1
3.
If the problem persists, record the message as it appears and contact the Cisco TAC.
735003
Error Message %ASA-1-735003 IPMI: Power Supply var1: OK Explanation A power supply has been restored to normal operation.
735004
Error Message %ASA-1-735004 IPMI: Power Supply var1: Failure Detected Explanation AC power has been lost, or the power supply has failed.
Check for AC power failure. Replace the power supply. If the problem persists, record the message as it appears and contact the Cisco TAC.
735005
Error Message %ASA-1-735005 IPMI: Power Supply Unit Redundancy OK Explanation Power supply unit redundancy has been restored. Recommended Action None required.
735006
Error Message %ASA-1-735006 IPMI: Power Supply Unit Redundancy Lost Explanation A power supply failure occurred. Power supply unit redundancy has been lost, but the ASA is functioning normally with minimum resources. Any further failures will result in an ASA shutdown. Recommended Action To regain full redundancy, perform the following steps: 1. 2.
Check for AC power failure. Replace the power supply.
1-543
Syslog Messages
3.
If the problem persists, record the message as it appears and contact the Cisco TAC.
735007
Error Message %ASA-1-735007 IPMI: CPU var1: Temp: var2 var3, Critical Explanation The CPU has reached a critical temperature.
var1The device number markings var2The temperature value var3Temperature value units (C, F)
Recommended Action Record the message as it appears and contact the Cisco TAC.
735008
Error Message %ASA-1-735008 IPMI: Chassis Ambient var1: Temp: var2 var3, Critical Explanation A chassis ambient temperature sensor has reached a critical level.
var1The device number markings var2The temperature value var3Temperature value units (C, F)
735009
Error Message %ASA-2-735009: IPMI: Environment Monitoring has failed initialization and configuration. Environment Monitoring is not running. Explanation Environment monitoring has experienced a fatal error during initialization and was unable to continue. Recommended Action Collect the output of the show environment and debug ipmi commands. Record the message as it appears and contact the Cisco TAC.
1-544
Chapter 1
735010
Error Message %ASA-3-735010: IPMI: Environment Monitoring has failed to update one or more of its records. Explanation Environment monitoring has experienced an error that temporarily prevented it from updating one or more of its records. Recommended Action If this message appears repeatedly, collect the output from the show
environment driver and debug ipmi commands. Record the message as it appears and contact the Cisco TAC.
735011
Error Message %ASA-1-735011: Power Supply var1: Fan OK Explanation The power supply fan has returned to a working operating state.
var1 Fan number
735012
Error Message %ASA-1-735012: Power Supply var1: Fan Failure Detected Explanation The power supply fan has failed.
var1 Fan number
Recommended Action Contact Cisco TAC to troubleshoot the failure. Power down the unit until this
failure is resolved.
735013
Error Message %ASA-1-735013: Voltage Channel var1: Voltage OK Explanation A voltage channel has returned to a normal operating level.
var1 Voltage channel number
1-545
Syslog Messages
735014
Error Message %ASA-1-735014: Voltage Channel var1: Voltage Critical Explanation A voltage channel has changed to a critical level.
var1 Voltage channel number
735015
Error Message %ASA-4-735015: CPU var1: Temp: var2 var3, Warm Explanation The CPU temperature is warmer than the normal operating range.
var1CPU Number var2Temperature Value var3Units
Recommended Action Continue to monitor this component to ensure that it does not reach a critical
temperature.
735016
Error Message %ASA-4-735016: Chassis Ambient var1: Temp: var2 var3, Warm Explanation The chassis temperature is warmer than the normal operating range.
var1Chassis Sensor Number var2Temperature Value var3Units
temperature.
735017
Error Message %ASA-1-735017: Power Supply var1: Temp: var2 var3, OK Explanation The power supply temperature has returned to a normal operating temperature.
var1Power Supply Number var2Temperature Value
1-546
Chapter 1
var3Units
735018
Error Message %ASA-4-735018: Power Supply var1: Temp: var2 var3, Critical Explanation The power supply has reached a critical operating temperature.
var1Power Supply Number var2Temperature Value var3Units
735019
Error Message %ASA-4-735019: Power Supply var1: Temp: var2 var3, Warm Explanation The power supply temperature is warmer than the normal operating range.
var1Power Supply Number var2Temperature Value var3Units
temperature.
735020
Error Message %ASA-1-735020: CPU var1: Temp: var2 var3 OK Explanation The CPU temperature has returned to the normal operating temperature.
var1CPU Number var2Temperature Value var3Units
1-547
Syslog Messages
735021
Error Message %ASA-1-735021: Chassis var1: Temp: var2 var3 OK Explanation The chassis temperature has returned to the normal operating temperature.
var1Chassis Sensor Number var2Temperature Value var3Units
735022
Error Message %ASA-1-735022: CPU# is running beyond the max thermal operating temperature and the device will be shutting down immediately to prevent permanent damage to the CPU. Explanation The ASA has detected a CPU running beyond the maximum thermal operating temperature, and will shut down immediately after detection. Recommended Action The chassis and CPU need to be inspected immediately for ventilation issues.
735023
Error Message %ASA-2-735023: ASA was previously shutdown due to the CPU complex running beyond the maximum thermal operating temperature. The chassis needs to be inspected immediately for ventilation issues. Explanation At boot time, the ASA detected a shutdown that occurred because a CPU was running beyond the maximum safe operating temperature. Using the show environment command will indicate that this event has occurred. Recommended Action The chassis need to be inspected immediately for ventilation issues.
735024
Error Message %ASA-1-735024: IO Hub var1: Temp: var2 var3, OK Explanation The IO hub temperature has returned to the normal operating temperature.
ar1 - IO hub number var2 - Temperature value
1-548
Chapter 1
var3 Units
735025
Error Message %ASA-1-735025: IO Hub var1: Temp: var2 var3, Critical Explanation The IO hub temperature has a critical temperature.
ar1 - IO hub number var2 - Temperature value var3 Units
735026
Error Message %ASA-4-735026: IO Hub var1: Temp: var2 var3, Warm Explanation The IO hub temperature is warmer than the normal operating range.
ar1 - IO hub number var2 - Temperature value var3 Units
temperature.
735027
Error Message %ASA-1-735027: CPU cpu_num Voltage Regulator is running beyond the max thermal operating temperature and the device will be shutting down immediately. The chassis and CPU need to be inspected immediately for ventilation issues. Explanation The ASA has detected a CPU voltage regulator running beyond the maximum thermal operating temperature, and shuts down immediately after detection.
cpu_numThe number to identify which CPU voltage regulator experienced the thermal event
Recommended Action The chassis and CPU need to be inspected immediately for ventilation issues.
1-549
Syslog Messages
735028
Error Message %ASA-2-735028: ASA was previously shutdown due to a CPU Voltage Regulator running beyond the max thermal operating temperature. The chassis and CPU need to be inspected immediately for ventilation issues. Explanation At boot time, the ASA detected a shutdown that occurred because of a CPU voltage regulator running beyond the maximum safe operating temperature. Enter the show environment command to indicate that this event has occurred. Recommended Action The chassis and CPU need to be inspected immediately for ventilation issues.
735029
Error Message %ASA-1-735029: IO Hub is running beyond the max thermal operating temperature and the device will be shutting down immediately to prevent permanent damage to the circuit. Explanation The ASA has detected that the IO hub is running beyond the maximum thermal operating temperature, and will shut down immediately after detection. Recommended Action The chassis and IO hub need to be inspected immediately for ventilation issues.
736001
Error Message %ASA-2-736001: Unable to allocate enough memory at boot for jumbo-frame reservation. Jumbo-frame support has been disabled. Explanation Insufficient memory has been detected when jumbo frame support was being configured. As a result, jumbo-frame support was disabled. Recommended Action Try reenabling jumbo frame support using the jumbo-frame reservation command. Save the running configuration and reboot the ASA. If the problem persists, contact the Cisco TAC.
737001
Error Message %ASA-7-737001: IPAA: Received message message-type Explanation The IP address assignment process received a message.
message-typeThe message received by the IP address assignment process
1-550
Chapter 1
737002
Error Message %ASA-3-737002: IPAA: Received unknown message num variables Explanation The IP address assignment process received a message.
numThe identifier of the message received by the IP address assignment process
737003
Error Message %ASA-5-737003: IPAA: DHCP configured, no viable servers found for tunnel-group tunnel-group Explanation The DHCP server configuration for the given tunnel group is not valid.
tunnel-groupThe tunnel group that IP address assignment is using for configuration
Recommended Action Validate the DHCP configuration for the tunnel group. Make sure that the DHCP server is online.
737004
Error Message %ASA-5-737004: IPAA: DHCP configured, request failed for tunnel-group 'tunnel-group' Explanation The DHCP server configuration for the given tunnel group is not valid.
Recommended Action Validate the DHCP configuration for the tunnel group. Make sure that the DHCP server is online.
737005
Error Message %ASA-6-737005: IPAA: DHCP configured, request succeeded for tunnel-group tunnel-group Explanation The DHCP server request has succeeded.
1-551
Syslog Messages
737006
Error Message %ASA-6-737006: IPAA: Local pool request succeeded for tunnel-group tunnel-group Explanation The local pool request has succeeded.
737007
Error Message %ASA-5-737007: IPAA: Local pool request failed for tunnel-group tunnel-group Explanation The local pool request has failed. The pool assigned to the tunnel group may be
exhausted.
Recommended Action Validate the IP local pool configuration by using the show ip local pool
command.
737008
Error Message %ASA-5-737008: IPAA: 'tunnel-group' not found Explanation The tunnel group was not found when trying to acquire an IP address for configuration. A software defect may cause this message to be generated.
Recommended Action Check the tunnel group configuration. Contact the Cisco TAC and report the
issue.
737009
Error Message %ASA-6-737009: IPAA: AAA assigned address ip-address, request failed Explanation The remote access client software requested the use of a particular address. The request to the AAA server to use this address failed. The address may be in use.
ip-addressThe IPv4 or IPv6 address that the client requested
Recommended Action Check the AAA server status and the status of IP local pools.
1-552
Chapter 1
737010
Error Message %ASA-6-737010: IPAA: AAA assigned address ip-address, request succeeded Explanation The remote access client software requested the use of a particular address and successfully received this address.
737011
Error Message %ASA-5-737011: IPAA: AAA assigned ip-address, not permitted, retrying Explanation The remote access client software requested the use of a particular address. The vpn-addr-assign aaa command is not configured. An alternatively configured address assignment method will be used.
Recommended Action If you want to permit clients to specify their own address, enable the vpn-addr-assign aaa command.
737012
Error Message %ASA-4-737012: IPAA: Address assignment failed Explanation The remote access client software request of a particular address failed.
ip-addressThe IP address that the client requested
Recommended Action If using IP local pools, validate the local pool configuration. If using AAA, validate the configuration and status of the AAA server. If using DHCP, validate the configuration and status of the DHCP server. Increase the logging level (use notification or informational) to obtain additional messages to identify the reason for the failure.
1-553
Syslog Messages
737013
Error Message %ASA-4-737013: IPAA: Error freeing address ip-address, not found Explanation The ASA tried to free an address, but it was not on the allocated list because of a recent
configuration change.
ip-addressThe IPv4 or IPv6 address to be released
Recommended Action Validate your address assignment configuration. If this message recurs, it might be due to a software defect. Contact the Cisco TAC and report the issue.
737014
Error Message %ASA-6-737014: IPAA: Freeing AAA address ip-address Explanation The ASA successfully released the IP address assigned through AAA.
737015
Error Message %ASA-6-737015: IPAA: Freeing DHCP address ip-address Explanation The ASA successfully released the IP address assigned through DHCP.
ip-addressThe IP address to be released
737016
Error Message %ASA-6-737016: IPAA: Freeing local pool address ip-address Explanation The ASA successfully released the IP address assigned through local pools.
1-554
Chapter 1
737017
Error Message %ASA-6-737017: IPAA: DHCP request attempt num succeeded Explanation The ASA successfully sent a request to a DHCP server.
numThe attempt number
737018
Error Message %ASA-5-737018: IPAA: DHCP request attempt num failed Explanation The ASA failed to send a request to a DHCP server.
numThe attempt number
Recommended Action Validate the DHCP configuration and connectivity to the DHCP server.
737019
Error Message %ASA-4-737019: IPAA: Unable to get address from group-policy or tunnel-group local pools Explanation The ASA failed to acquire an address from the local pools configured on the group policy or tunnel group. The local pools may be exhausted. Recommended Action Validate the local pool configuration and status. Validate the group policy and
tunnel group configuration of local pools.
737023
Error Message %ASA-5-737023: IPAA: Unable to allocate memory to store local pool address ip-address Explanation The ASA is low on memory.
ip-addressThe IP address that was acquired
Recommended Action The ASA may be overloaded and need more memory, or there may be a memory leak caused by a software defect. Contact the Cisco TAC and report the issue.
1-555
Syslog Messages
737024
Error Message %ASA-5-737024: IPAA: Client requested address ip-address, already in use, retrying Explanation The client requested an IP address that is already in use. The request will be tried using a new IP address.
ip-addressThe IP address that the client requested
737025
Error Message %ASA-5-737025: IPAA: Duplicate local pool address found, ip-address in quarantine Explanation The IP address that was to be given to the client is already in use. The IP address has been removed from the pool and will not be reused.
ip-addressThe IP address that was acquired
Recommended Action Validate the local pool configuration; there may be an overlap caused by a software defect. Contact the Cisco TAC and report the issue.
737026
Error Message %ASA-6-737026: IPAA: Client assigned ip-address from local pool Explanation The client has assigned the given address from a local pool.
ip-addressThe IP address that was assigned to the client
737027
Error Message %ASA-3-737027: IPAA: No data for address request Explanation A software defect has been found. Recommended Action Contact the Cisco TAC and report the issue.
1-556
Chapter 1
737028
Error Message %ASA-4-737028: IPAA: Unable to send ip-address to standby: communication failure Explanation The active ASA was unable to communicate with the standby ASA. The failover pair may be out-of-sync.
Recommended Action Validate the failover configuration and status.
737029
Error Message %ASA-6-737029: IPAA: Added ip-address to standby Explanation The standby ASA accepted the IP address assignment.
737030
Error Message %ASA-4-737030: IPAA: Unable to send ip-address to standby: address in use Explanation The standby ASA has the given address already in use when the active ASA attempted
to acquire it. The failover pair may be out-of-sync.
737031
Error Message %ASA-6-737031: IPAA: Removed ip-address from standby Explanation The standby ASA cleared the IP address assignment.
1-557
Syslog Messages
737032
Error Message %ASA-4-737032: IPAA: Unable to remove ip-address from standby: address not found Explanation The standby ASA did not have an IP address in use when the active ASA attempted to release it. The failover pair may be out-of-sync.
737033
Error Message %ASA-4-737033: IPAA: Unable to assign addr_allocator provided IP address ip_addr to client. This IP address has already been assigned by previous_addr_allocator Explanation The address assigned by the AAA/DHCP/local pool is already in use.
addr_allocatorThe DHCP/AAA/local pool ip_addrThe IP address allocated by the DHCP/AAA/local pool previous_ addr_allocatorThe address allocater that already assigned the IP address (local pool, AAA, or DHCP)
Recommended Action Validate the AAA/DHCP/local pool address configurations. Overlap may
occur.
741000
Error Message %ASA-6-741000: Coredump filesystem image created on variable 1 -size variable 2 MB Explanation A core dump file system was successfully created. The file system is used to manage
core dumps by capping the amount of disk space that core dumps may use.

variable 1The file system on which the core dumps are placed (for example, disk0:, disk1:, and flash:) variable 2The size of the created core dump file system in MB
Recommended Action Make sure that you save your configuration after creating the core dump file
system.
1-558
Chapter 1
741001
Error Message %ASA-6-741001: Coredump filesystem image on variable 1 - resized from variable 2 MB to variable 3 MB Explanation The core dump file system has been successfully resized.
variable 1The file system on which the core dumps are placed variable 2The size of the previous core dump file system in MB variable 3The size of the current, newly resized core dump file system in MB
Recommended Action Make sure that you save your configuration after resizing the core dump file
system. Resizing the core dump file system deletes the contents of the existing core dump file system. As a result, make sure that you archive any information before you resize the core dump file system.
741002
Error Message %ASA-6-741002: Coredump log and filesystem contents cleared on variable 1 Explanation All core dumps have been deleted from the core dump file system, and the core dump log has been cleared. The core dump file system and coredump log are always synchronized with each other.
variable 1The file system on which the core dumps are placed (for example, disk0:, disk1:,and flash:)
Recommended Action None required. You can clear the core dump file system to reset it to a known
state using the clear coredump command.
741003
Error Message %ASA-6-741003: Coredump filesystem and its contents removed on variable 1 Explanation The core dump file system and its contents have been removed, and the core dump feature has been disabled.
variable 1The file system on which the core dumps are placed (for example, disk0:, disk1:,and flash:)
Recommended Action Make sure that you save your configuration after the core dump feature has
been disabled.
1-559
Syslog Messages
741004
Error Message %ASA-6-741004: Coredump configuration reset to default values Explanation The core dump configuration has been reset to its default value, which is disabled. Recommended Action Make sure that you save your configuration after the core dump feature has
been disabled.
741005
Error Message %ASA-4-741005: Coredump operation variable 1 failed with error variable 2 variable 3 Explanation An error occurred during the performance of a core dump-related operation.
variable 1This variable may have the following values: - CREATE_FSYSAn error occurred when creating the core dump file system. - CLEAR_LOGAn error occurred when clearing the core dump log. - DELETE_FSYSAn error occurred when deleting the core dump file system. - CLEAR_FSYSAn error occurred when removing the contents of the core dump file system. - MOUNT_FSYSAn error occurred when mounting the core dump file system. variable 2The decimal number that provides additional information about the cause of the error specified in variable 1. variable 3The descriptive ASCII string associated with variable 2. The ASCII string can have the following values: - coredump files already exist - unable to create coredump filesystem - unable to create loopback device - filesystem type not supported - unable to delete the coredump filesystem - unable to delete loopback device - unable to unmount coredump filesystem - unable to mount coredump filesystem - unable to mount loopback device - unable to clear coredump filesystem - coredump filesystem not found - requested coredump filesystem too big - coredump operation aborted by administrator - coredump command execution failed - coredump IFS error encountered
1-560
Chapter 1
- coredump, unidentified error encountered

Recommended Action Make sure that the core dump feature is disabled in the configuration, and send the message to the Cisco TAC for further analysis.
741006
Error Message %ASA-4-741006: Unable to write Coredump Helper configuration, reason variable 1 Explanation An error occurred when writing to the coredump helper configuration file. This error
occurs only if disk0: is full. The configuration file is located in disk0:.coredumpinfo/coredump.cfg.
variable 1This variable includes a basic file system-related string that indicates why the writing of the core dump helper configuration file failed.
Recommended Action Disable the core dump feature, remove unneeded items from disk0:, and then
reenable core dumps, if desired.
742001
Error Message %ASA-3-742001: failed to read master key for password encryption from persistent store Explanation An attempt to read the master password encryption key from the nonvolatile memory
after bootup failed. Encrypted passwords in the configuration are not decrypted unless the master key is set to the correct value using the key config-key password encryption command.
Recommended Action If there are encrypted passwords in the configuration that must be used, set the
master key to the previous value used to encrypt the password using the key config-key password encryption command. If there are no encrypted passwords or they can be discarded, set a new master key. If password encryption is not used, no action is required.
742002
Error Message %ASA-3-742002: failed to set master key for password encryption Explanation An attempt to read the key config-key password encryption command failed. The error may be caused by the following reasons:
Configuration from a nonsecure terminal (for example, over a Telnet connection) was made. Failover is enabled, but it does not use an encrypted link. Another user is setting the key at the same time. When trying to change the key, the old key is incorrect. The key is too small to be secure.
1-561
Syslog Messages
Other reasons for the error may be valid. In these cases, the actual error is printed in response to the command.
Recommended Action Correct the problem indicated in the command response.
742003
Error Message %ASA-3-742003: failed to save master key for password encryption, reason reason_text Explanation An attempt to save the master key to nonvolatile memory failed. The actual reason is
specified by the reason_text parameter. The reason can be an out-of-memory condition, or the nonvolatile store can be inconsistent.
Recommended Action If the problem persists, reformat the nonvolatile store that is used to save the key by using the write erase command. Before performing this step, make sure that you back up the out-of-the-box configuration. Then reenter the write erase command.
742004
Error Message %ASA-3-742004: failed to sync master key for password encryption, reason reason_text Explanation An attempt to synchronize the master key to the peer failed. The actual reason is specified by the reason_text parameter. Recommended Action Try to correct the problem specified in the reason_text parameter.
742005
Error Message %ASA-3-742005: cipher text enc_pass is not compatible with the configured master key or the cipher text has been tampered with Explanation An attempt to decrypt a password failed. The password may have been encrypted using a master key that is different from the current master key, or the encrypted password has been changed from its original form. Recommended Action If the correct master key is not being used, correct the problem. If the encrypted
password has been modified, reapply the configuration in question with a new password.
1-562
Chapter 1
742006
Error Message %ASA-3-742006: password decryption failed due to unavailable memory Explanation An attempt to decrypt a password failed because no memory was available. Features
using this password will not work as desired.

Recommended Action Correct the memory problem.
742007
Error Message %ASA-3-742007: password encryption failed due to unavailable memory Explanation An attempt to encrypt a password failed because no memory was available. Passwords
may be left in clear text form in the configuration.

Recommended Action Correct the memory problem, and reapply the configuration that failed password encryption.
742008
Error Message %ASA-3-742008: password enc_pass decryption failed due to decoding error Explanation Password decryption failed because of decoding errors, which may occur if the encrypted password has been modified after being encrypted. Recommended Action Reapply the configuration in question with a clear text password.
742009
Error Message %ASA-3-742009: password encryption failed due to decoding error Explanation Password encryption failed because of decoding errors, which may be an internal software error. Recommended Action Reapply the configuration in question with a clear text password. If the problem persists, contact the Cisco TAC.
1-563
Syslog Messages
742010
Error Message %ASA-3-742010: encrypted password enc_pass is not well formed Explanation The encrypted password provided in the command is not well formed. The password
may not be a valid, encrypted password, or it may have been modified since it was encrypted.

reason_textA string that represents the actual cause of the failure enc_passThe encrypted password that is related to the issue
Recommended Action Reapply the configuration in question with a clear text password.
743000
Error Message %ASA-1-743000: The PCI device with vendor ID: vendor_id device ID: device_id located at bus:device.function bus_num:dev_num, func_num has a link link_attr_name of actual_link_attr_val when it should have a link link_attr_name of expected_link_attr_val. Explanation A PCI device in the system is not configured correctly, which may result in the system not performing at its optimum level. Recommended Action Collect the output of the show controller pci detail command, and contact the
Cisco TAC.
743001
Error Message %ASA-1-743001: Backplane health monitoring detected link failure Explanation A hardware failure has probably occurred and has been detected on one of the links between the ASA Services Module and the switch chassis. Recommended Action Contact the Cisco TAC.
743002
Error Message %ASA-1-743002: Backplane health monitoring detected link OK Explanation A link has been restored between the ASA Services Module and the switch chassis. However, the failure and subsequent recovery probably indicates a hardware failure. Recommended Action Contact the Cisco TAC.
1-564
Chapter 1
743004
Error Message %ASA-1-743004: System is not fully operational - PCI device with vendor ID vendor_id (vendor_name), device ID device_id (device_name) not found Explanation A PCI device in the system that is needed for it to be fully operational was not found.
vendor_idHexadecimal value that identifies the device vendor vendor_nameText string that identifies the vendor name device_idHexadecimal value that identifies the vendor device device_nameText string that identifies the device name
Recommended Action Collect the output of the show controller pci detail command and contact the
Cisco TAC.
743010
Error Message %ASA-3-743010: EOBC RPC server failed to start for client module client name. Explanation The service failed to start for a particular client of the EOBC RPC service on the server. Recommended Action Call the Cisco TAC.
743011
Error Message %ASA-3-743011: EOBC RPC call failed, return code code string. Explanation The EOBC RPC client failed to make an RPC to the intended server. Recommended Action Call the Cisco TAC.
746001
Error Message %ASA-6-746001: user-identity: activated import user groups | activated host names | user-to-IP address databases download started Explanation A database (user groups, hostnames, or IP addresses) download has started. Recommended Action None required.
1-565
Syslog Messages
746002
Error Message %ASA-6-746002: user-identity: activated import user groups | activated host names | user-to-IP address databases download complete Explanation A database (user groups, hostnames, or IP addresses) download has completed. Recommended Action None required.
746003
Error Message %ASA-3-746003: user-identity: activated import user groups | activated host names | user-to-IP address databases download failed - reason Explanation A database (user groups, hostnames, or IP addresses) download has failed because of a
timeout.
Recommended Action Check the off-box AD agent status. If the AD agent is down, resolve that issue first. If the AD agent is up and running, try to download the database again. If the problem persists, contact the Cisco TAC.
746004
Error Message %ASA-4-746004: user identity: Total number of activated user groups exceeds the max_groups groups for this platform. Explanation The total number of activated user groups exceeds the maximum number of 256 user groups for this platform. Recommended Action Too many user groups have been configured and activated. Reduce the number
of configured user groups. Run the clear user-identity user no-policy-activated command to release user records that have not been activated in any policy. Run the show user-identity user all command to check the total number of users in the database.
746005
Error Message %ASA-3-746005: user-identity: The AD Agent AD agent IP address cannot be reached - reason [action] Explanation The ASA cannot reach the AD agent. There has been no response from the AD agent, or the RADIUS registration failed because the buffer was too small. Recommended Action Check the network connection between the AD agent and the ASA. Try to
reach another AD agent, if one is configured and available. If the problem persists, contact the Cisco TAC.
1-566
Chapter 1
746006
Error Message %ASA-4-746006: user-identity: Out of sync with AD Agent, start bulk download Explanation The AD agent cannot update the IP-user mapping events on the ASA and the AD agent event log overflows, which causes inconsistency between the AD agent and the ASA IP-user database. Recommended Action None required. If this message persists, check the connection between the AD
agent and the ASA.
746007
Error Message %ASA-5-746007: user-identity: NetBIOS response failed from User user_name at user_ip Explanation No NetBIOS response was received for the number of retries made. Recommended Action None required.
746008
Error Message %ASA-6-746008: user-identity: NetBIOS Probe Process started Explanation The NetBIOS process has started. Recommended Action None required.
746009
Error Message %ASA-6-746009: user-identity: NetBIOS Probe Process stopped Explanation The NetBIOS process has stopped. Recommended Action None required.
1-567
Syslog Messages
746010
Error Message %ASA-3-746010: user-identity: update import-user domain_name\\group_name - Import Failed [reason] Explanation Entering the user-identity update import-user username command failed to update a
user element. Reasons for failure include the following: timeout, partial update, import aborted, group does not exist, or no reason given.
Recommended Action If the reason for failure does not exist, verify that the group name is correct in the policy. Otherwise, check the connectivity between the ASA and the AD server.
746011
Error Message %ASA-4-746011: Total number of users created exceeds the maximum number of max_users for this platform. Explanation The AD group has more than the hard-coded maximum number (64000) of levels. Too many users have been configured in the activated policy. Recommended Action Change your policies so that the number of configured users and users under configured groups does not exceed the limit.
746012
Error Message %ASA-5-746012: user-identity: Add IP-User mapping IP Address domain_name\user_name result - reason Explanation A new user-IP mapping has been added to the user-to-IP address mapping database. The
status of the operation (success or failure) is indicated. The success reason is VPN user. The failure reasons include the following: Maximum user limit reached and Duplicated address.
746013
Error Message %ASA-5-746013: user-identity: Delete IP-User mapping IP Address domain_name\user_name result - reason Explanation A change has been made to the user-to-IP address mapping database. The status of the
operation (success or failure) is indicated. The success reasons include the following: Inactive timeout, NetBIOS probing failed, PIP notification, VPN user logout, Cut-through-proxy user logout, and MAC address mismatch. The failure reason is PIP notification.
1-568
Chapter 1
746014
Error Message %ASA-5-746014: user-identity: [FQDN] fqdn address IP Address obsolete. Explanation A fully qualified domain name has become obsolete. Recommended Action None required.
746015
Error Message %ASA-5-746015: user-identity: FQDN] fqdn resolved IP address. Explanation A fully qualified domain name lookup has succeeded. Recommended Action None required.
746016
Error Message %ASA-3-746016: user-identity: DNS lookup failed, reason: reason Explanation A DNS lookup has failed. Failure reasons include timeout, unresolvable, and no
memory.
Recommended Action Verify that the FQDN is valid, and that the DNS server is reachable from the ASA. If the problem persists, contact the Cisco TAC.
746017
Error Message %ASA-6-746017: user-identity: Update import-user domain_name\\group_name Explanation The user-identity update import-user command has been issued. Recommended Action None required.
746018
Error Message %ASA-6-746018: user-identity: Update import-user domain_name\\group_name done Explanation The user-identity update import-user command has been issued, and the import has
been completed successfully.

Recommended Action None requried.
1-569
Syslog Messages
746019
Error Message %ASA-3-746019: user-identity: Update|Remove AD Agent AD agent IP Address IP-user mapping user_IP - domain_name\user_name failed Explanation The ASA failed to update or remove an IP-user mapping on the AD agent. Recommended Action Check the status of the AD agent and the connectivity between the ASA and
the AD agent. If the problem persists, contact the Cisco TAC.
747001
Error Message %ASA-3-747001: Clustering: Recovered from state machine event queue depleted. Event (event-id, ptr-in-hex, ptr-in-hex) dropped. Current state state-name, stack ptr-in-hex, ptr-in-hex, ptr-in-hex, ptr-in-hex, ptr-in-hex, ptr-in-hex Explanation The cluster FSM event queue is full, and a new event has been dropped. Recommended Action None.
747002
Error Message %ASA-5-747002: Clustering: Recovered from state machine dropped event (event-id, ptr-in-hex, ptr-in-hex). Intended state: state-name. Current state: state-name. Explanation The cluster FSM received an event that is incompatible with the current state. Recommended Action None.
747003
Error Message %ASA-5-747003: Clustering: Recovered from state machine failure to process event (event-id, ptr-in-hex, ptr-in-hex) at state state-name. Explanation The cluster FSM failed to process an event for all reasons given. Recommended Action None.
1-570
Chapter 1
747004
Error Message %ASA-6-747004: Clustering: state machine changed from state state-name to state-name. Explanation The cluster FSM has progressed to a new state. Recommended Action None.
747005
Error Message %ASA-7-747005: Clustering: State machine notify event event-name (event-id, ptr-in-hex, ptr-in-hex) Explanation The cluster FSM has notified clients about an event. Recommended Action None.
747006
Error Message %ASA-7-747006: Clustering: State machine is at state state-name Explanation The cluster FSM moved to a stable state; that is, Disabled, Slave, or Master. Recommended Action None.
747007
Error Message %ASA-5-747007: Clustering: Recovered from finding stray config sync thread, stack ptr-in-hex, ptr-in-hex, ptr-in-hex, ptr-in-hex, ptr-in-hex, ptr-in-hex. Explanation Astray configuration sync thread has been detected. Recommended Action None.
1-571
Syslog Messages
747008
Error Message %ASA-4-747008: Clustering: New cluster member name with serial number serial-number-A rejected due to name conflict with existing unit with serial number serial-number-B. Explanation The same unit name has been configured on multiple units. Recommended Action None.
747009
Error Message %ASA-2-747009: Clustering: Fatal error due to failure to create RPC server for module module name. Explanation The ASA failed to create an RPC server. Recommended Action Disable clustering on this unit and try to re-enable it. Contact the Cisco TAC if
the problem persists.
747010
Error Message %ASA-3-747010: Clustering: RPC call failed, message message-name, return code code-value. Explanation An RPC call failure has occurred. The system tries to recover from the failure. Recommended Action None.
747011
Error Message %ASA-2-747011: Clustering: Memory allocation error. Explanation A memory allocation failure occurred in clustering. Recommended Action Disable clustering on this unit and try to re-enable it. If the problem persists,
check the memory usage on the ASA.
1-572
Chapter 1
747012
Error Message %ASA-3-747012: Clustering: Failed to replicate global object id hex-id-value in domain domain-name to peer unit-name, continuing operation. Explanation A global object ID replication failure has occurred. Recommended Action None.
747013
Error Message %ASA-3-747013: Clustering: Failed to remove global object id hex-id-value in domain domain-name from peer unit-name, continuing operation. Explanation A global object ID removal failure has occurred. Recommended Action None.
747014
Error Message %ASA-3-747014: Clustering: Failed to install global object id hex-id-value in domain domain-name, continuing operation. Explanation A global object ID installation failure has occurred. Recommended Action None.
747015
Error Message %ASA-4-747015: Clustering: Forcing stray member unit-name to leave the cluster. Explanation A stray cluster member has been found. Recommended Action None.
1-573
Syslog Messages
747016
Error Message %ASA-4-747016: Clustering: Found a split cluster with both unit-name-A and unit-name-B as master units. Master role retained by unit-name-A, unit-name-B will leave, then join as a slave. Explanation A split cluster has been found. Recommended Action None.
747017
Error Message %ASA-4-747017: Clustering: Failed to enroll unit unit-name due to maximum member limit limit-value reached. Explanation The ASA failed to enroll a new unit because the maximum member limit has been
reached.
747018
Error Message %ASA-3-747018: Clustering: State progression failed due to timeout in module module-name. Explanation The cluster FSM progression has timed out. Recommended Action None.
747019
Error Message %ASA-4-747019: Clustering: New cluster member name rejected due to Cluster Control Link IP subnet mismatch (ip-address/ip-mask on new unit, ip-address/ip-mask on local unit). Explanation The master unit found that a new joining unit has an incompatible cluster interface IP
address.
1-574
Chapter 1
747020
Error Message %ASA-4-747020: Clustering: New cluster member unit-name rejected due to encryption license mismatch. Explanation The master unit found that a new joining unit has an incompatible encryption license. Recommended Action None.
747021
Error Message %ASA-3-747021: Clustering: Master unit unit-name is quitting due to interface health check failure on interface-name. Explanation The master unit has disabled clustering because of an interface health check failure. Recommended Action None.
747022
Error Message %ASA-3-747022: Clustering: Asking slave unit unit-name to quit because it failed interface health check x times, rejoin will be attempted after y min. Failed interface: interface-name. Explanation This syslog message occurs when the maximum number of rejoin attempts has not been exceeded. A slave unit has disabled clustering because of an interface health check failure for the specified amount of time. This unit will re-enable itself automatically after the specified amount of time (ms). Recommended Action None.
747023
Error Message %ASA-3-747023: Clustering: Master unit unit-name is quitting due to card name card health check failure, and master Security Service Card state is state-name. Explanation The master unit has disabled clustering because of a Security Service Card health check
failure.
1-575
Syslog Messages
747024
Error Message %ASA-3-747024: Clustering: Asking slave unit unit-name to quit due to card name card health check failure, and its Security Service Card state is state-name. Explanation A slave unit has disabled clustering because of a Security Service Card health check
failure.
747025
Error Message %ASA-4-747025: Clustering: New cluster member unit-name rejected due to firewall mode mismatch. Explanation A master unit found a joining unit that has an incompatible firewall mode. Recommended Action None.
747026
Error Message %ASA-4-747026: Clustering: New cluster member unit-name rejected due to cluster interface name mismatch (ifc-name on new unit, ifc-name on local unit). Explanation A master unit found a joining unit that has an incompatible cluster control link interface
name.
747027
Error Message %ASA-4-747027: Clustering: Failed to enroll unit unit-name due to insufficient size of cluster pool pool-name in context-name. Explanation A master unit could not enroll a joining unit because of the size limit of the minimal
cluster pool configured.

1-576
Chapter 1
747028
Error Message %ASA-4-747028: Clustering: New cluster member unit-name rejected due to interface mode mismatch (mode-name on new unit, mode-name on local unit). Explanation A master unit found a joining unit that has an incompatible interface-mode, either
spanned or individual.
747029
Error Message %ASA-4-747029: Clustering: Unit unit-name is quitting due to Cluster Control Link down. Explanation A unit disabled clustering because of a cluster interface failure. Recommended Action None.
747030
Error Message %ASA-3-747030: Clustering: Asking slave unit unit-name to quit because it failed interface health check x times (last failure on interface-name), Clustering must be manually enabled on the unit to re-join. Explanation An interface health check has failed and the maximum number of rejoin attempts has been exceeded. A slave unit has disabled clustering because of an interface health check failure. Recommended Action None.
747031
Error Message %ASA-3-747031: Clustering: Platform mismatch between cluster master (platform-type) and joining unit unit-name (platform-type). unit-name aborting cluster join. Explanation The joining unit's platform type does not match with that of the cluster master.
unit-nameName of the unit in the cluster bootstrap platform-typeType of ASA platform
Recommended Action Make sure that the joining unit has the same platform type as that of the cluster
master.
1-577
Syslog Messages
747032
Error Message %ASA-3-747032: Clustering: Service module mismatch between cluster master (module-name) and joining unit unit-name (module-name)in slot slot-number. unit-name aborting cluster join. Explanation The joining unit's external modules are not consistent (module type and order in which they are installed) with those on the cluster master.
module-nameName of the external module unit-nameName of the unit in the cluster bootstrap slot-numberThe number of the slot in which the mismatch occurred
Recommended Action Make sure that the modules installed on the joining unit are of the same type and are in the same order as they are in the cluster master.
747033
Error Message %ASA-3-747033: Clustering: Interface mismatch between cluster master and joining unit unit-name. unit-name aborting cluster join. Explanation The joining unit's interfaces are not the same as those on the cluster master.
unit-nameName of the unit in the cluster bootstrap
Recommended Action Make sure that the interfaces available on the joining unit are the same as those
on the cluster master.
750001
Error Message %ASA-5-750001: Local:local IP:local port Remote:remote IP: remote port Username: username Received request to request an IPsec tunnel; local traffic selector = local selectors: range, protocol, port range; remote traffic selector = remote selectors: range, protocol, port range Explanation A request is being made for an operation on the IPsec tunnel such as a rekey, a request
to establish a connection, and so on.

local IP:local port Local IP address for this request. The ASA IP address and port number used for this connection remote IP:remote port Remote IP address for this request. Peer IP address and port number that the connection is coming from usernameUsername of the requester for remote access, if known, or the tunnel group local selectorsLocally configured traffic selectors or proxies that are being used for this IPsec tunnel
1-578
Chapter 1
remote selectorsRemote peers requested traffic selectors or proxies for this IPsec tunnel
750002
Error Message %ASA-5-750002: Local:local IP:local port Remote: remote IP: remote port Username: username Received a IKE_INIT_SA request Explanation An incoming tunnel or SA initiation request (IKE_INIT_SA request) has been received.
local IP:local port Local IP address for this request. The ASA IP address and port number used for this connection remote IP:remote port Remote IP address for this request. Peer IP address and port number that the connection is coming from usernameUsername of the requester for remote access, if known, or the tunnel group
750003
Error Message %ASA-4-750003: Local: local IP:local port Remote: remote IP:remote port Username: username Negotiation aborted due to ERROR: error Explanation The negotiation of an SA was aborted because of the provided error reason.
local IP:local port Local IP address for this request. The ASA IP address and port number used for this connection remote IP:remote port Remote IP address for this request. Peer IP address and port number that the connection is coming from usernameUsername of the requester for remote access, if known yet errorError reason for aborting the negotiation
Recommended Action Review the syslog and follow the flow of the logs to determine if this syslog is
the final in the exchange and if it is the cause of a potential failure or a transient error that was renegotiated through. For example, a peer may suggest a DH group via the KE payload that is not configured that causes an initial request to fail, but the correct DH group is communicated so that the peer can come back with the correct group in a new request.
1-579
Syslog Messages
750004
Error Message %ASA-5-750004: Local: local IP: local port Remote: remote IP: remote port Username: username Sending COOKIE challenge to throttle possible DoS Explanation An incoming connection request was challenged with a cookie based on the cookie
challenge thresholds that are configured to prevent a possible DoS attack.

local IP:local port Local IP address for this request. The ASA IP address and port number used for this connection remote IP:remote port Remote IP address for this request. Peer IP address and port number that the connection is coming from usernameUsername of the requester for remote access, if known yet
750005
Error Message %ASA-5-750005: Local: local IP: local port Remote: remote IP: remote port Username: username IPsec rekey collision detected. I am lowest nonce initiator, deleting SA with inbound SPI SPI Explanation A rekey collision was detected (both peers trying to initiate a rekey at the same time),
and it was resolved by keeping the one initiated by this ASA because it had the lowest nonce. This action caused the indicated SA referenced by the SPI to be deleted.

local IP:local port Local IP address for this request. The ASA IP address and port number used for this connection remote IP:remote port Remote IP address for this request. Peer IP address and port number that the connection is coming from usernameUsername of the requester for remote access, if known yet SPISPI handle of the SA being deleted by resolving the rekey collision that was detected
750006
Error Message %ASA-5-750006: Local: local IP: local port Remote: remote IP: remote port Username: username SA UP. Reason: reason Explanation An SA came up for the given reason, such as for a newly established connection or a
rekey.

local IP:local port Local IP address for this request. The ASA IP address and port number used for this connection remote IP:remote port Remote IP address for this request. Peer IP address and port number that the connection is coming from
1-580
Chapter 1
usernameUsername of the requester for remote access, if known yet reasonReason that the SA came into the UP state
750007
Error Message %ASA-5-750007: Local: local IP: local port Remote: remote IP: remote port Username: username SA DOWN. Reason: reason Explanation An SA was torn down or deleted for the given reason, such as a request by the peer,
operator request (via an administrator action), rekey, and so on.

local IP:local port Local IP address for this request. The ASA IP address and port number used for this connection remote IP:remote port Remote IP address for this request. Peer IP address and port number that the connection is coming from usernameUsername of the requester for remote access, if known yet reasonReason that the SA came into the DOWN state
750008
Error Message %ASA-5-750008: Local: local IP: local port Remote: remote IP: remote port Username: username SA rejected due to system resource low Explanation An SA request was rejected to alleviate a low system resource condition.
local IP:local port Local IP address for this request. The ASA IP address and port number used for this connection remote IP:remote port Remote IP address for this request. Peer IP address and port number that the connection is coming from usernameUsername of the requester for remote access, if known yet
Recommended Action Check CAC settings for IKEv2 to determine if this is expected behavior based
on configured thresholds; otherwise, if the condition persists, investigate further to alleviate the issue.
1-581
Syslog Messages
750009
Error Message %ASA-5-750009: Local: local IP: local port Remote: remote IP: remote port Username: username SA request rejected due to CAC limit reached: Rejection reason: reason Explanation A Connection Admission Control (CAC) limiting threshold was reached, which caused
the SA request to be rejected.

local IP:local port Local IP address for this request. The ASA IP address and port number used for this connection remote IP:remote port Remote IP address for this request. Peer IP address and port number that the connection is coming from usernameUsername of the requester for remote access, if known yet reasonReason that the SA was rejected
Recommended Action Check CAC settings for IKEv2 to determine if this is expected behavior based
on configured thresholds; otherwise, if the condition persists, investigate further to alleviate the issue.
750010
Error Message %ASA-5-750010: Local: local-ip Remote: remote-ip Username:username IKEv2 local throttle-request queue depth threshold of threshold reached; increase the window size on peer peer for better performance
local-ipLocal peer IP address remote-ipRemote peer IP address usernameUsername of the requester for remote access or tunnel group name for L2L, if known yet thresholdQueue depth threshold of the local throttle-request queue reached peerRemote peer IP address
Explanation The ASA overflowed its throttle request queue to the specified peer, indicating that the peer is slow. The throttle request queue holds requests destined for the peer, which cannot be sent immediately because the maximum number of requests allowed to be in-flight based on the IKEv2 window size were already in-flight. As in-flight requests are completed, requests are pulled off of the throttle request queue and sent to the peer. If the peer is not processing these requests quickly, the throttle queue backs up. Recommended Action If possible, increase the IKEv2 window size on the remote peer to allow more concurrent requests to be in-flight, which may improve performance.
Note
The ASA does not currently support an increased IKEv2 window size setting.
1-582
Chapter 1
750011
Error Message %ASA-3-750011: Tunnel Rejected: Selected IKEv2 encryption algorithm (IKEV2 encry algo) is not strong enough to secure proposed IPSEC encryption algorithm (IPSEC encry algo). Explanation The tunnel was rejected because the selected IKEv2 encryption algorithm is not strong enough to secure the proposed IPSEC encryption algorithm. Recommended Action Configure a stronger IKEv2 encryption algorithm to match or exceed the
strength of the IPsec child SA encryption algorithm.
750012
Error Message %ASA-4-750012: Selected IKEv2 encryption algorithm (IKEV2 encry algo) is not strong enough to secure proposed IPSEC encryption algorithm (IPSEC encry algo). Explanation The selected IKEv2 encryption algorithm is not strong enough to secure the proposed IPSEC encryption algorithm. Recommended Action Configure a stronger IKEv2 encryption algorithm to match or exceed the
strength of the IPsec child SA encryption algorithm.
751001
Error Message %ASA-3-751001: Local: localIP:port Remote:remoteIP:port Username: username/group Failed to complete Diffie-Hellman operation. Error: error Explanation A failure to complete a Diffie-Hellman operation occurred, as indicated by the error.
localIP:portThe local IP address and port number remoteIP:portThe remote IP address and port number username/groupThe username or group associated with this connection attempt errorThe error string that indicates the specific error
Recommended Action A low memory issue or other internal error that should be resolved has occurred. If it persists, use the memory tracking tool to isolate the issue.
1-583
Syslog Messages
751002
Error Message %ASA-3-751002: Local: localIP:port Remote:remoteIP:port Username: username/group No preshared key or trustpoint configured for self in tunnel group group Explanation The ASA was unable to find any type of authentication information in the tunnel group that it could use to authenticate itself to the peer.
localIP:portThe local IP address and port number remoteIP:portThe remote IP address and port number username/groupThe username or group associated with this connection attempt groupThe name of the tunnel group
Recommended Action Check the tunnel group configuration, and configure a preshared key or certificate for self-authentication in the indicated tunnel group.
751003
Error Message %ASA-7-751003: Local: localIP:port Remote:remoteIP:port Username: username/group Need to send a DPD message to peer Explanation Dead peer detection needs to be performed for the specified peer to determine if it is still alive. The ASA may have terminated a connection to the peer.
localIP:portThe local IP address and port number remoteIP:portThe remote IP address and port number username/groupThe username or group associated with this connection attempt
751004
Error Message %ASA-3-751004: Local: localIP:port Remote:remoteIP:port Username: username/group No remote authentication method configured for peer in tunnel group group Explanation A method to authenticate the remote peer was not found in the configuration to allow the connection.
1-584
Chapter 1
groupThe name of the tunnel group
Recommended Action Check the configuration to make sure that a valid remote peer authentication
setting is present.
751005
Error Message %ASA-3-751005: Local: localIP:port Remote:remoteIP:port Username: username/group AnyConnect client reconnect authentication failed. Session ID: sessionID, Error: error Explanation A failure occurred during an AnyConnect client reconnection attempt using the session
token.

localIP:portThe local IP address and port number remoteIP:portThe remote IP address and port number username/groupThe username or group associated with this connection attempt sessionIDThe session ID used to try to reconnect errorThe error string to indicate the specific error that occurred during the reconnection attempt
Recommended Action Take action according to the error specified, if necessary. The error may indicate that a session was removed instead of remaining in resume state because a client disconnect was detected or sessions were cleared on the ASA. If necessary, also compare this message to the event logs on the Anyconnect client.
751006
Error Message %ASA-3-751006: Local: localIP:port Remote:remoteIP:port Username: username/group Certificate authentication failed. Error: error Explanation A failure related to certificate authentication occurred.
localIP:portThe local IP address and port number remoteIP:portThe remote IP address and port number username/groupThe username or group associated with this connection attempt errorThe error string to indicate the specific certificate authentication failure
Recommended Action Take action according to the error specified, if necessary. Check the certificate
trustpoint configuration and make sure that the necessary CA certificate exists to be able to correctly verify client certificate chains. Use the debug crypto ca commands to isolate the failure.
1-585
Syslog Messages
751007
Error Message %ASA-5-751007: Local: localIP:port Remote:remoteIP:port Username: username/group Configured attribute not supported for IKEv2. Attribute: attribute Explanation A configured attribute could not be applied to the IKE version 2 connection because it
is not supported for IKE version 2 connections.

localIP:portThe local IP address and port number remoteIP:portThe remote IP address and port number username/groupThe username or group associated with this connection attempt attributeThe attribute that is configured to be applied
Recommended Action None required, To eliminate this message from being generated, you can remove the IKE version 2 configuration setting.
751008
Error Message %ASA-3-751008: Local: localIP:port Remote:remoteIP:port Username: username/group Group=group, Tunnel rejected: IKEv2 not enabled in group policy Explanation IKE version 2 is not allowed based on the enabled protocols for the indicated group to which a connection attempt was mapped, and the connection was rejected.
localIP:portThe local IP address and port number remoteIP:portThe remote IP address and port number username/groupThe username or group associated with this connection attempt groupThe tunnel group used for connection
Recommended Action Check the group policy VPN tunnel protocol setting and enable IKE version 2,
if desired.
751009
Error Message %ASA-3-751009: Local: localIP:port Remote:remoteIP:port Username: username/group Unable to find tunnel group for peer. Explanation A tunnel group could not be found for the peer.
Recommended Action Check the configuration and tunnel group mapping rules, then configure them to allow the peer to land on a configured group.
1-586
Chapter 1
751010
Error Message %ASA-3-751010: Local: localIP:port Remote:remoteIP:port Username: username/group Unable to determine self-authentication method. No crypto map setting or tunnel group found. Explanation A method for authenticating the ASA to the peer could not be found in either the tunnel group or crypto map.
Recommended Action Check the configuration, and configure a self-authentication method in the crypto map for the initiator L2L or in the applicable tunnel group.
751011
Error Message %ASA-3-751011: Local: localIP:port Remote:remoteIP:port Username: username/group Failed user authentication. Error: error Explanation A failure occured during user authentication within EAP for an IKE version 2 remote access connection.
localIP:portThe local IP address and port number remoteIP:portThe remote IP address and port number username/groupThe username or group associated with this connection attempt errorThe error string that indicates the specific error
Recommended Action Make sure that the correct authentication credentials were provided and debug
further to determine the exact cause of failure, if necessary.
751012
Error Message %ASA-3-751012: Local: localIP:port Remote:remoteIP:port Username: username/group Failure occurred during Configuration Mode processing. Error: error Explanation A failure occurred during configuration mode processing while settings were being applied to the connection.
1-587
Syslog Messages
errorThe error string that indicates the specific error
Recommended Action Take action based on the indicated error. Use the debug crypto ikev2 commands to determine the cause of the failure, or debug the indicated subsystem that is specified by the error, if necessary.
751013
Error Message %ASA-3-751013: Local: localIP:port Remote:remoteIP:port Username: username/group Failed to process Configuration Payload request for attribute attribute ID. Error: error Explanation The Configuration Payload request failed to process and generate a Configuration Payload response for an attribute that was requested by the peer.
localIP:portThe local IP address and port number remoteIP:portThe remote IP address and port number username/groupThe username or group associated with this connection attempt attribute ID The attribute ID on which the failure occurred errorThe error string that indicates the specific error
Recommended Action A memory error, configuration error, or another type of error has occurred. Use the debug crypto ikev2 commands to help isolate the cause of the failure.
751014
Error Message %ASA-4-751014: Local: localIP:port Remote remoteIP:port Username: username/group Warning Configuration Payload request for attribute attribute ID could not be processed. Error: error Explanation A warning occurred while processing a CP request to generate a CP response for a requested attribute.
localIP:portThe local IP address and port number remoteIP:portThe remote IP address and port number username/groupThe username or group associated with this connection attempt attribute ID The attribute ID on which the failure occurred errorThe error string that indicates the specific error
Recommended Action Take action based on the attribute indicated in the warning and the indicated warning message. For example, a newer client is being used with an older ASA image, which does not understand a new attribute that has been added to the client. An upgrade of the ASA image may be necessary to allow the attribute to be processed.
1-588
Chapter 1
751015
Error Message %ASA-4-751015: Local: localIP:port Remote remoteIP:port Username: username/group SA request rejected by CAC. Reason: reason Explanation The connection was rejected by the call admission control to protect the ASA based on
configured thresholds or conditions indicated by the reason listed.

localIP:portThe local IP address and port number remoteIP:portThe remote IP address and port number username/groupThe username or group associated with this connection attempt reasonThe reason that the SA request was rejected
Recommended Action Check the reason and resolve the condition if a new connection should have been accepted or change the configured thresholds.
751016
Error Message %ASA-4-751016: Local: localIP:port Remote remoteIP:port Username: username/group L2L peer initiated a tunnel with the same outer and inner addresses. Peer could be Originate only - Possible misconfiguration! Explanation The peer may be configured for originate-only connections based on the received outer and inner IP addresses for the tunnel.
Recommended Action Check the L2L peer configuration.
751017
Error Message %ASA-3-751017: Local: localIP:port Remote remoteIP:port Username: username/group Configuration Error error description Explanation An error in the configuration that prevented the connection has been detected.
localIP:portThe local IP address and port number remoteIP:portThe remote IP address and port number username/groupThe username or group associated with this connection attempt error descriptionA brief description of the configuration error
Recommended Action Correct the configuration based on the indicated error.
1-589
Syslog Messages
751018
Error Message %ASA-3-751018: Terminating the VPN connection attempt from attempted group. Reason: This connection is group locked to locked group. Explanation The tunnel group over which the connection is attempted is not the same as the tunnel group set in the group lock.
attempted groupThe tunnel group over which the connection came in locked groupThe tunnel group that the connection is locked or restricted to
Recommended Action Check the group-lock value in the group policy or the user attributes.
751019
Error Message %ASA-4-751019: Local:LocalAddr Remote:RemoteAddr Username:username Failed to obtain an licenseType license. Maximum license limit limit exceeded. Explanation A session creation failed because the maximum license limit was exceeded, which
caused a failure to either initiate or respond to a tunnel request.

LocalAddrLocal address for this connection attempt RemoteAddrRemote peer address for this connection attempt usernameUsername for the peer attempting the connection licenseType License type that was exceeded (other VPN or AnyConnect Premium/Essentials) limitNumber of licenses allowed and was exceeded
Recommended Action Make sure that enough licenses are available for all allowed users and/or obtain
more licenses to allow the rejected connections. For multiple context mode, allow more licenses for the context that reported the failure, if necessary.
751020
Error Message %ASA-3-751020: Local:%A:%u Remote:%A:%u Username:%s An %s remote access connection failed. Attempting to use an NSA Suite B crypto algorithm (%s) without an AnyConnect Premium license. Explanation An IKEv2 remote access tunnel could not be created because of an NSA Suite B ASA
license restriction, or an AnyConnect Premium license was applied but explicitly disabled with the anyconnect-essentials command in the webvpn configuration mode.
Recommended Action Make sure that either an AnyConnect Premium license is installed on the ASA
or that no NSA Suite B crypto algorithms are configured in the remote access IKEv2 policies or IPsec proposals.
1-590
Chapter 1
751021
Error Message %ASA-4-751021: Local:variable 1:variable 2 Remote:variable 3:variable 4 Username:variable 5 variable 6 with variable 7 encryption is not supported with this version of the AnyConnect Client. Please upgrade to the latest Anyconnect Client. Explanation An out-of-date AnyConnect client tried to connect to an ASA that has IKEv2 with AES-GCM encryption policy configured.
variable 1Local IP address variable 2Local port variable 3Remote client IP address variable 4Remote client port variable 5Username of the AnyConnect client (may be unknown because this occurs before the user enters a username) variable 6Connection protocol type (IKEv1, IKEv2) variable 7Combined mode encryption type (AES-GCM, AES-GCM 256)
Recommended Action Upgrade the AnyConnect client to the latest version to use IKEv2 with AES-GCM encryption.
751022
Error Message %ASA-3-751022: Local: local-ip Remote: remote-ip Username:username Tunnel rejected: Crypto Map Policy not found for remote traffic selector rem-ts-start/rem-ts-end/rem-ts.startport/rem-ts.endport/rem-ts.protocol local traffic selector local-ts-start/local-ts-end/ local-ts.startport/local-ts.endport/local-ts.protocol! Explanation The ASA was not able to find security policy information for the private networks or hosts indicated in the message. These networks or hosts were sent by the initiator and do not match any crypto ACLs at the ASA. This is most likely a misconfiguration.
local-ipLocal peer IP address remote-ipRemote peer IP address usernameUsername of the requester for remote access, if known yet rem-ts-startRemote traffic selector start address rem-ts-endRemote traffic selector end address rem-ts.startportRemote traffic selector start port rem-ts.endportRemote traffic selector end port rem-ts.protocolRemote traffic selector protocol local-ts-startLocal traffic selector start address local-ts-endLocal traffic selector end address local-ts.startportLocal traffic selector start port
1-591
Syslog Messages
local-ts.endportLocal traffic selector end port local-ts.protocolLocal traffic selector protocol
Recommended Action Check the protected network configuration in the crypto ACLs on both sides and make sure that the local network on the initiator is the remote network on the responder and vice-versa. Pay special attention to wildcard masks and host addresses as compared to network addresses. Non-Cisco implementations may have the private addresses labeled as proxy addresses or red networks.
751023
Error Message %ASA-6-751023: Local a:p Remote: a:p Username:n Unknown client connection Explanation An unknown non-Cisco IKEv2 client has connected to the ASA.
nThe group or username (depending on context) aAn IP address pThe port number uaThe user-agent presented by the client to the ASA
Recommended Action Upgrade to a Cisco-supported IKEv2 client.
751024
Error Message %ASA-3-751024: Local:ip-addr Remote:ip-addr Username:username IKEv2 IPv6 User Filter tempipv6 configured. This setting has been deprecated, terminating connection Explanation The IPv6 VPN filter has been deprecated and if it is configured instead of a unified filter
for IPv6 traffic access control, the connection will be terminated.

Recommended Action Configure a unified filter with IPv6 entries to control IPv6 traffic for the user.
752001
Error Message %ASA-2-752001: Tunnel Manager received invalid parameter to remove record Explanation A failure to remove a record from the tunnel manager that might prevent future tunnels to the same peer from initiating has occurred. Recommended Action Reloading the device will remove the record, but if the error persists or recurs,
perform additional debugging of the specific tunnel attempt.
1-592
Chapter 1
752002
Error Message %ASA-7-752002: Tunnel Manager Removed entry. Map Tag = mapTag. Map Sequence Number = mapSeq. Explanation An entry to initiate a tunnel was successfully removed.
mapTagName of the crypto map for which the initiation entry was removed mapSeqSequence number of the crypto map for which the initiation entry was removed
752003
Error Message %ASA-5-752003: Tunnel Manager dispatching a KEY_ACQUIRE message to IKEv2. Map Tag = mapTag. Map Sequence Number = mapSeq Explanation An attempt is being made to initiate an IKEv2 tunnel that was based on the crypto map
indicated.

752004
Error Message %ASA-5-752004: Tunnel Manager dispatching a KEY_ACQUIRE message to IKEv1. Map Tag = mapTag. Map Sequence Number = mapSeq Explanation An attempt is being made to initiate an IKEv1 tunnel that was based on the crypto map
indicated.

752005
Error Message %ASA-2-752005: Tunnel Manager failed to dispatch a KEY_ACQUIRE message. Memory may be low. Map Tag = mapTag. Map Sequence Number = mapSeq. Explanation An attempt to dispatch a tunnel initiation attempt failed because of an internal error, such as a memory allocation failure.
mapTagName of the crypto map for which the initiation entry was removed
1-593
Syslog Messages
mapSeqSequence number of the crypto map for which the initiation entry was removed
Recommended Action Use the memory tracking tools and additional debugging to isolate the issue.
752006
Error Message %ASA-3-752006: Tunnel Manager failed to dispatch a KEY_ACQUIRE message. Probable mis-configuration of the crypto map or tunnel-group. Map Tag = Tag. Map Sequence Number = num, SRC Addr: address port: port Dst Addr: address port: port. Explanation An attempt to dispatch a tunnel initiation attempt failed because of a configuration error
of the indicated crypto map or associated tunnel group.

TagName of the crypto map for which the initiation entry was removed numSequence number of the crypto map for which the initiation entry was removed addressThe source IP address or destination IP address portThe source port number or destination port number
Recommended Action Check the configuration of the tunnel group and crypto map indicated to make
sure that it is complete.
752007
Error Message %ASA-3-752007: Tunnel Manager failed to dispatch a KEY_ACQUIRE message. Entry already in Tunnel Manager. Map Tag = mapTag. Map Sequence Number = mapSeq Explanation An attempt was made to re-add an existing entry into the tunnel manager.
Recommended Action
If the issue persists, make sure that the configuration of the peer will allow the tunnel, and debug further to make sure that the tunnel manager entries are being added and removed correctly during tunnel initiation and successful or failed initiation attempts. Debug IKE version 2 or IKE version 1 connections further, because they may still be in the process of creating the tunnel.
1-594
Chapter 1
752008
Error Message %ASA-7-752008: Duplicate entry already in Tunnel Manager Explanation A duplicate request to initiate a tunnel was made, and the tunnel manager is already
attempting to initiate the tunnel.

Recommended Action None required. If the issue persists, either IKE version 1 or IKE version 2 may
have attempted a tunnel initiation and not have timed out yet. Debug further using the applicable commands to make sure that the tunnel manager entry is removed after successful or failed initiation attempts.
752009
Error Message %ASA-4-752009: IKEv2 Doesn't support Multiple Peers Explanation An attempt to initiate a tunnel with IKE version 2 failed because the crypto map is
configured with multiple peers, which is not supported for IKE version 2. Only IKE version 1 supports multiple peers.
Recommended Action Check the configuration to make sure that multiple peers are not expected for
IKE version 2 site-to-site initiation.
752010
Error Message %ASA-4-752010: IKEv2 Doesn't have a proposal specified Explanation No IPsec proposal was found to be able to initiate an IKE version 2 tunnel . Recommended Action Check the configuration, then configure an IKE version 2 proposal that can be
used to initiate the tunnel, if necessary.
752011
Error Message %ASA-4-752011: IKEv1 Doesn't have a transform set specified Explanation No IKE version 1 transform set was found to be able to initiate an IKE version 2 tunnel. Recommended Action Check the configuration, then configure an IKE version 2 transform set that can be used to initiate the tunnel, if necessary.
1-595
Syslog Messages
752012
Error Message %ASA-4-752012: IKEv protocol was unsuccessful at setting up a tunnel. Map Tag = mapTag. Map Sequence Number = mapSeq. Explanation The indicated protocol failed to initiate a tunnel using the configured crypto map.
protocolIKE version number 1 or 2 for IKEv1 or IKEv2 mapTagName of the crypto map for which the initiation entry was removed mapSeqSequence number of the crypto map for which the initiation entry was removed
Recommended Action Check the configuration, then debug further within the indicated protocol to determine the cause of the failed tunnel attempt.
752013
Error Message %ASA-4-752013: Tunnel Manager dispatching a KEY_ACQUIRE message to IKEv2 after a failed attempt. Map Tag = mapTag. Map Sequence Number = mapSeq. Explanation The tunnel manager is attempting to initiate the tunnel again after it failed.
Recommended Action Check the configuration, and make sure that the crypto maps are correctly configured. Then determine if the tunnel is successfully created on the second attempt.
752014
Error Message %ASA-4-752014: Tunnel Manager dispatching a KEY_ACQUIRE message to IKEv1 after a failed attempt. Map Tag = mapTag. Map Sequence Number = mapSeq. Explanation The tunnel manager is falling back and attempting to initiate the tunnel using IKE version 1 after the tunnel failed.
Recommended Action Check the configuration, and make sure that the crypto maps are correctly configured. Then determine if the tunnel is successfully created on the second attempt.
1-596
Chapter 1
752015
Error Message %ASA-3-752015: Tunnel Manager has failed to establish an L2L SA. All configured IKE versions failed to establish the tunnel. Map Tag = mapTag. Map Sequence Number = mapSeq. Explanation An attempt to bring up an L2L tunnel to a peer failed after trying with all configured
protocols.

Recommended Action Check the configuration, and make sure that the crypto maps are correctly configured. Debug the individual protocols to isolate the cause of the failure.
752016
Error Message %ASA-5-752016: IKEv protocol was successful at setting up a tunnel. Map Tag = mapTag. Map Sequence Number = mapSeq. Explanation The indicated protocol (IKE version 1 or IKE version 2) successfully created an L2L
tunnel.

protocolIKE version number 1 or 2 for IKEv1 or IKEv2 mapTagName of the crypto map for which the initiation entry was removed mapSeqSequence number of the crypto map for which the initiation entry was removed
752017
Error Message %ASA-4-752017: IKEv2 Backup L2L tunnel initiation denied on interface interface matching crypto map name, sequence number number. Unsupported configuration. Explanation The ASA uses IKEv1 to initiate the connection because IKEv2 does not support the
backup L2L feature.

Recommended Action None required if IKEv1 is enabled. You must enable IKEv1 to use the backup
L2L feature.
1-597
Syslog Messages
766001
Error Message %ASA-3-766001: CTS SXP: Configured source IP source ip error Explanation An error occurred while using this configured source IP address to set up an SXP
connection.

source ipIPv4 or IPv6 source address errorDetailed message regarding what type of error occurs while using the configured address to set up the SXP connection, which can be one of the following: - Does not belong to this device. - Does not match outbound interface IP address.
Recommended Action Reconfigure the SXP connection to have a valid source IP address. Alternatively, unconfigure the source IP address and let the device select the correct source IP address based on a route lookup.
766002
Error Message %ASA-3-766002: CTS SXP: Invalid message from peer peer IP: error Explanation An error occurred while parsing an SXP message.
peer IPIPv4 or IPv6 peer address error Description of message parsing problem
766003
Error Message %ASA-3-766003: CTS SXP: Connection with peer peer IP failed: error Explanation An SXP configuration error occurred. The connection cannot be set up correctly.
peer IPIPv4 or IPv6 peer address error Description of SXP configuration problem. The error can be one of the following values: - Mode mismatch with received one. - Does not exist. - With the same peer, but different source IP address exists. - Version mismatch with received one. - Received binding update while in speaker mode.
Recommended Action Make sure that the connection configurations on both ends have the correct mode and IP addresses.
1-598
Chapter 1
766004
Error Message %ASA-3-766004: CTS SXP: Fail to start listening socket after TCP process restart. Explanation The SXP on this device cannot accept SXP connection setup requests from remote devices, because it cannot update the binding manager. Recommended Action Disable and reenable the SXP feature to see if the listening socket can be
restarted.
766005
Error Message %ASA-3-766005: CTS SXP: Binding Binding IP - SGname(SGT) from peer IP instance connection instance num error. Explanation An SXP binding update error has occurred.
Binding IPIPv4 or IPv6 binding address SGname (SGT)Binding SGT information. Has the following format if SGname is available: SGname (SGT) and the following format if SGname is unavailable: SGT. peer IPIPv4 or IPv6 peer address that sent the binding connection instance numInstance number of the SXP connection from which the binding came errorDetailed message about the binding error
766006
Error Message %ASA-3-766006: CTS SXP: Internal error: error Explanation The CTS SXP system encountered an internal failure.
errorDetailed message about the SXP internal error, which can be one of the following: - Source IP address of existing SXP connection cannot change. - Password type of existing connection cannot change. - Connection mode is the same as the existing configuration. - IP address does not exist.
1-599
Syslog Messages
766007
Error Message %ASA-3-766007: CTS SXP: Connection with peer peer IP (instance connection instance num) state changed from original state to Off. Explanation The CTS SXP system encountered an internal failure, because the SXP connection with the specified instance number changed its state to off.
peer IPIPv4 or IPv6 peer address connection instance numSXP connection instance number original stateOriginal connection state
766008
Error Message %ASA-6-766008: CTS SXP: Connection with peer IP (instance connection instance num) state changed from original state to final state. Explanation The SXP connection with the specified instance number changed state.
peer IPIPv4 or IPv6 peer address source IPIPv4 or IPv6 source address connection instance numSXP connection instance number original stateOriginal connection state final stateFinal connection state, which can be any state except the Off state.
Recommended Action .None required.
766009
Error Message %ASA-5-766009: CTS SXP: password changed. Explanation The SXP system password has been changed. Recommended Action None required.
766010
Error Message %ASA-5-766010: CTS SXP: SXP default source IP is changed original source IP final source IP. Explanation The SXP default source IP address has been changed on this device.
original source IPIPv4 or IPv6 original default source IP address
1-600
Chapter 1
final source IPIPv4 or IPv6 final default source IP address
766011
Error Message %ASA-5-766011: CTS SXP: operational state. Explanation The SXP feature has changed operational state and works only when the feature is
enabled.
operational stateFlags the state whether CTS SXP is enabled or disabled.
766012
Error Message %ASA-7-766012: CTS SXP: timer name timer started for connection with peer peer IP. Explanation The specified SXP timer started.
peer IPIPv4 or IPv6 peer address. For timers that are not triggered by connection-based events, that is, the retry open timer, a default IP address of 0.0.0.0 is used. timer nameTimer name
766013
Error Message %ASA-7-766013: CTS SXP: timer name timer stopped for connection with peer peer IP. Explanation The specified SXP timer stopped.
peer IPIPv4 or IPv6 peer address. For timers that are not triggered by connection-based events, that is, the retry open timer, a default IP address of 0.0.0.0 is used. timer nameTimer name
1-601
Syslog Messages
766014
Error Message %ASA-7-766014: CTS SXP: SXP received binding forwarding request (action) binding binding IP - SGname(SGT). Explanation The SXP received a binding forwarding request. The request comes from the binding
manager when it wants SXP to broadcast the latest net binding changes within the binding manager.

actionAdd or delete operation binding IPIPv4 or IPv6 binding address SGname (SGT)Binding SGT information. Has the following format if SGname is available: SGname (SGT) and the following format if SGname is unavailable: SGT.
766015
Error Message %ASA-7-766015: CTS SXP: Binding binding IP - SGname(SGT) is forwarded to peer peer IP (instance connection instance num). Explanation The SXP forwarded binding to the peer.
binding IPIPv4 or IPv6 binding address SGname (SGT)Binding SGT information. Has the following format if SGname is available: SGname (SGT) and the following format if SGname is unavailable: SGT. peer IPIPv4 or IPv6 peer address connection instance numSXP connection instance number
766016
Error Message %ASA-7-766016: CTS SXP: Binding binding IP - SGName(SGT) from peer peer IP (instance binding's connection instance num) changed from old instance: old instance num, old sgt: old SGName(SGT). Explanation Binding changed in the SXP database.
binding IPIPv4 or IPv6 binding address SGname (SGT)Binding SGT information. Has the following format if SGname is available: SGname (SGT) and the following format if SGname is unavailable: SGT. peer IPBinding source IPv4 or IPv6 address bindings connection instance numSXP connection instance number old instance numOld connection instance number on which the binding was learned
1-602
Chapter 1
old SGName (SGT)Binding old SGT information. Has the following format if SGname is available: SGname (SGT) and the following format if SGname is unavailable: SGT.
766017
Error Message %ASA-7-766017: CTS SXP: Binding binding IP - SGname(SGT) from peer peer IP (instance connection instance num) deleted in SXP database. Explanation Binding was deleted in the SXP database.
binding IPIPv4 or IPv6 binding address SGname (SGT)Binding SGT information. Has the following format if SGname is available: SGname (SGT) and the following format if SGname is unavailable: SGT. peer IPBinding source IPv4 or IPv6 peer address connection instance numSXP connection instance number
766018
Error Message %ASA-7-766018: CTS SXP: Binding binding IP - SGname(SGT) from peer peer IP (instance connection instance num) added in SXP database. Explanation Binding was aded in the SXP database.
binding IPIPv4 or IPv6 binding address SGname (SGT)Binding SGT information. Has the following format if SGname is available: SGname (SGT) and the following format if SGname is unavailable: SGT. peer IPBinding source IPv4 or IPv6 peer address connection instance numSXP connection instance number
766019
Error Message %ASA-7-766019: CTS SXP: Binding binding IP - SGname(SGT) action taken. Update binding manager. Explanation The SXP updated the binding manager with the binding change.
binding IPIPv4 or IPv6 binding address SGname (SGT)Binding SGT information. Has the following format if SGname is available: SGname (SGT) and the following format if SGname is unavailable: SGT.
1-603
Syslog Messages
action takenAction taken, which can be one of the following: added, deleted, or changed.
766020
Error Message %ASA-3-766020: CTS SXP: Unable to locate egress interface to peer peer IP. Explanation The ASA cannot locate the egress interface to the SXP peer.
binding IPIPv4 or IPv6 address
Recommended Action Make sure that the SXP peer is routable from the device.
766201
Error Message %ASA-4-766201: CTS PAC: CTS PAC for Server IP_address, A-ID PAC issuer name will expire in number days Explanation A CTS PAC is nearing its expiration date. Recommended Action Obtain a new PAC and import it.
766202
Error Message %ASA-3-766202: CTS PAC for Server IP_address, A-ID PAC issuer name has expired Explanation A CTS PAC has expired. Recommended Action Obtain a new PAC and import it.
766203
Error Message %ASA-3-766203: Unable to retrieve CTS Environment data due to: reason Explanation The ASA was unable to retrieve the CTS environment data and SGT name table for one
of the following reasons:

PAC has expired PAC data not available Error response from ISE Unable to retrieve server secret from the PAC
1-604
Chapter 1
Database error Invalid SG info value received Unable to add SG tag to database Error closing database Database update aborted Recommended Action If this message persists, contact the Cisco TAC for assistance.
766204
Error Message %ASA-3-766204: CTS Environment data has expired Explanation The CTS environmentThe CTS environment data and SGT name table have expired,
which is likely to occur after unresolved environment data retrieval failures have occurred.
Recommended Action If this message persists, contact the Cisco TAC for assistance.
766251
Error Message %ASA-6-766251: CTS SGT-MAP: Binding binding IP - SGname(SGT) from source name added to binding manager. Explanation Binding from the specified source was added to the binding manager.
binding IPIPv4 or IPv6 binding address SGname (SGT)Binding SGT information. Has the following format if SGname is available: SGname (SGT) and the following format if SGname is unavailable: SGT. source nameName of the contributing source. Currently, SXP is the only contributing source.
766252
Error Message %ASA-5-766252: CTS SGT-MAP: CTS SGT-MAP: Binding binding IP SGname(SGT) from source name deleted from binding manager. Explanation Binding from the specified source was deleted from the binding manager. Explanation Binding from the specified source was added to the binding manager.
binding IPIPv4 or IPv6 binding address SGname (SGT)Binding SGT information. Has the following format if SGname is available: SGname (SGT) and the following format if SGname is unavailable: SGT.
1-605
Syslog Messages
source nameName of the contributing source. Currently, SXP is the only contributing source.
766253
Error Message %ASA-6-766253: CTS SGT-MAP: Binding binding IP - new SGname(SGT) from new source name changed from old sgt: old SGname(SGT) from old source old source name. Explanation A particular IP to SGT binding has changed in the binding manager.
binding IPIPv4 or IPv6 binding address new SGname (SGT)New binding SGT information. Has the following format if SGname is available: SGname (SGT) and the following format if SGname is unavailable: SGT. new source nameName of the new contributing source. Currently, SXP is the only contributing source. old SGname (SGT)Old binding SGT information. Has the following format if SGname is available: SGname (SGT) and the following format if SGname is unavailable: SGT. old source nameName of the old contributing source. Currently, SXP is the only contributing source.
766254
Error Message %ASA-3-766254: CTS SGT-MAP: Binding manager unable to action binding binding IP - SGname(SGT) from source name. Explanation The binding manager cannot insert, delete, or update the binding
actionBinding manager operation. Either insert, delete or update. binding IPIPv4 or IPv6 binding address SGname (SGT)Binding SGT information. Has the following format if SGname is available: SGname (SGT) and the following format if SGname is unavailable: SGT. source nameName of the contributing source. Currently, SXP is the only contributing source.
1-606
Chapter 1
766301
Error Message %ASA-7-766301: CTS Policy: Security-group tag sgt is mapped to security-group name "sgname" Explanation The security group tag referenced in the policy is known and the lookup in the security group table is successful. As a result, the tag name mapping is derived.
sgtSecurity group tag referenced in the policy sgnameSecurity group name mapping derived from the table
766302
Error Message %ASA-7-766302: CTS Policy: Unknown security-group tag sgt referenced in policies Explanation The security group tag referenced in the policy was unknown and the lookup in the security group table failed. However, the policy referencing the tag can still be enforced.
sgtSecurity group tag referenced in the policy
Recommended Action Check to see if the security group tag exists in the ISE. If the tag exists, it will become known after the next refresh. If the tag does not exist in the ISE, consider removing all associated policies on the ASA.
766303
Error Message %ASA-6-766303: CTS Policy: Security-group name "sgname" is resolved to security-group tag sgt Explanation The securitygroup name referenced in the policy was resolved and the lookup in the
security group table was successful. As a result, the tag derived from the table is used for policy enforcement.

sgnameSecurity group name referenced in the policy sgtSecurity group tag mapping derived from the table
1-607
Syslog Messages
766304
Error Message %ASA-4-766304: CTS Policy: Unresolved security-group name "sgname" referenced, policies based on this name will be inactive Explanation The securitygroup name referenced in the policy cannot be resolved to a tag and the
lookup in the security group table failed. AS a result, the policy referencing the name is inactive, but remains in the configuration.
sgnameSecurity group name referenced in the policy
Recommended Action Check to see if the security group name exists in the ISE. If the name exists, the table can be refreshed so the name gets resolved and policies can be enforced. If the name does not exist in the ISE, consider removing all associated policies on the ASA.
766305
Error Message %ASA-4-766305: CTS Policy: Security-group table cleared, all polices referencing security-group names will be deactivated Explanation The security group table downloaded from the ISE is cleared on the ASA and policies based on security group tags continue to be enforced. However, policies based on names become inactive, but remain in the configuration. Recommended Action Refresh the securitygroup table on the ASA so all policies based on security group names can be enforced.
766307
Error Message %ASA-7-766307: CTS Policy: Security-group name for security-group tag sgt renamed from old_sgname" to "new_sgname" Explanation In the newly downloaded security group table on the ASA, a change in the security
group name for a security group tag was detected; however, there was no change in policy status.

sgtSecurity group tag referenced in the policy old_sgnameOld security group name new_sgnameNew security group name
1-608
Chapter 1
766308
Error Message %ASA-7-766308: CTS Policy: Previously unknown security-group tag sgt is now mapped to security-group name "sgname" Explanation In the newly downloaded security group table on the ASA, a previously unknown security group tag was found in the table; however, there was no change in policy status.
sgtSecurity group tag referenced in the policy sgnameSecurity group name derived from the new security group table
766309
Error Message %ASA-5-766309: CTS Policy: Previously known security-group tag sgt is now unknown Explanation In the newly downloaded security group table on the ASA, a previously known security group tag no longer exists. There is no change in policy status, and the policy can still be enforced.
sgtSecurity group tag referenced in the policy
Recommended Action If the security group tag does not exist in the new table, the security group has been removed in the ISE. Consider removing all policies that reference the tag.
766310
Error Message %ASA-5-766310: CTS Policy: Security-group name "sgname" remapped from security-group tag old_sgt to new_sgt Explanation In the newly downloaded security group table on the ASA, a change in the security group tag for a security group name was detected. All policies referencing the name are updated to reflect the new tag, and policies are enforced based on the new tag.
sgnameSecurity group name referenced in the policy old_sgtOld security group tag new_sgtNew security group tag
Recommended Action Because of the change in tag value, make sure that the configured policies are
still accurate.
1-609
Syslog Messages
766311
Error Message %ASA-6-766311: CTS Policy: Previously unresolved security-group name "sgname" is now resolved to security-group tag sgt Explanation In the newly downloaded security group table on the ASA, a previously unresolved
security group name was resolved to a tag, and the new tag can be used to enforce policies.

sgnameSecurity group name referenced in the policy sgtSecurity group tag derived from the new security group table
766312
Error Message %ASA-4-766312: CTS Policy: Previously resolved security-group name "sgname" is now unresolved, policies based on this name will be deactivated Explanation In the newly downloaded security group table on the ASA, a previously resolved security group name no longer exists. As a result, all policies based on this security group name become inactive, but remain in the configuration.
sgnameSecurity group name referenced in the policy
Recommended Action If the security group name does not exist in the new table, the security group has been removed in the ISE. Check the policy configuration on the ASA, consider removing policies referencing the name.
766313
Error Message %ASA-3-766313: CTS Policy: Failure to update policies for security-group "sgname"-sgt Explanation An error was encountered in updating the policies. Policy enforcement will continue based on old tag values and is no longer accurate.
sgnameSecurity group name that has a change in tag value sgtNew security group tag value
Recommended Action To reflect the correct tag value, remove all policies referencing the security group name and reapply them. If the error persists, contact the Cisco TAC for assistance.
1-610
Chapter 1
767001
Error Message %ASA-6-767001: Inspect-name: Dropping an unsupported IPv6/IP46/IP64 packet from interface:IP Addr to interface:IP Addr (fail-close) Explanation A fail-close option was set for a service policy, and a particular inspect received an IPv6,
IP64, or IP46 packet. Based on the fail-close option setting, this syslog message is generated and the packet is dropped.
768001
Error Message %ASA-3-768001: QUOTA: resource utilization is high: requested req, current curr, warning level level Explanation A system resource allocation level has reached its warning threshold. In the case of a
management session, the resource is simultaneous administrative sessions.

resourceThe name of the system resource; in this case, it is a management session. reqThe number requested; for a management session, it is always 1. currThe current number allocated; equals level for a management session levelThe warning threshold, which is 90 percent of the configured limit
768002
Error Message %ASA-3-768002: QUOTA: resource quota exceeded: requested req, current curr, limit limit Explanation A request for a system resource would have exceeded its configured limit and was
denied. In the case of a management session, the maximum number of simultaneous administrative sessions on the system has been reached.

resourceThe name of the system resource; in this case, it is a management session. reqThe number requested; for a management session, it is always 1. currThe current number allocated; equals level for a management session limitThe configured resource limit
1-611
Syslog Messages
768003
Error Message %ASA-4-768003: SSH: connection timed out: username username, IP ip Explanation An SSH session was disconnected because of inactivity.
usernameThe name of the user ipThe IP address of the user
769001
Error Message %ASA-5-769001: UPDATE: ASA image src was added to system boot list Explanation The system image has been updated. The name of a file previously downloaded onto the
system has been added to the system boot list.
srcThe name or URL of the source image file
769002
Error Message %ASA-5-769002: UPDATE: ASA image src was copied to dest Explanation The system image has been updated. An image file has been copied onto the system.
srcThe name or URL of the source image file destThe name of the destination image file
769003
Error Message %ASA-5-769003: UPDATE: ASA image src was renamed to dest Explanation The system image has been updated. An existing image file has been renamed to an image file name in the system boot list.
srcThe name or URL of the source image file destThe name of the destination image file
1-612
Chapter 1
769004
Error Message %ASA-5-769004: UPDATE: ASA image checksum error copying src to dest Explanation The image verification test failed during the copying of an image file.
srcThe file name or URL of the source image file destThe file name of the destination image file
Recommended Action Try to update using another source image file.
770001
Error Message %ASA-4-770001: Resource resource allocation is more than the permitted list of limit for this platform. If this condition persists, the ASA will be rebooted. Explanation The CPU or memory resource allocation for the ASA virtual machine has exceeded the
allowed limit for this platform. This condition does not occur unless the setting for the ASA virtual machine has been changed from that specified in the software downloaded from Cisco.
Recommended Action To continue ASA operation, change the CPU or memory resource allocation of the virtual machine to what was specified with the software downloaded from Cisco or to the resource limits specified in the Cisco ASA 1000V CLI Configuration Guide for this platform.
770002
Error Message %ASA-1-770002: Resource resource allocation is more than the permitted limit for this platform. ASA will be rebooted. Explanation The CPU or memory resource allocation for the ASA virtual machine has exceeded the allowed limit for this platform. This condition does not occur unless the setting for the ASA virtual machine has been changed from that specified in the software downloaded from Cisco. The ASA will continue to reboot if the resource allocation is not changed. Recommended Action Change the CPU or memory reosurce allocation to the virtual machine to what
was specified with the software downloaded from Cisco or to the resource limits specified in the Cisco ASA 1000V CLI Configuration Guide for this platform.
1-613
Syslog Messages
770003
Error Message %ASA-4-770003: Resource resource allocation is less than the minimum requirement of value for this platform. If this condition persists, performance will be lower than normal. Explanation The CPU or memory resource allocation to the ASA virtual machine is less than the
minimum requirement for this platform. If this condition persists, performance will be lower than normal.
Recommended Action To continue ASA operation, change the CPU or memory reosurce allocation of the virtual machine to what was specified with the software downloaded from Cisco or see the memory limit and CPU reservation settings specified in the Cisco ASA 1000V CLI Configuration Guide for this platform.
770001
Error Message %ASA-4-770001: Resource resource allocation is more than the permitted list of limit for this platform. If this condition persists, the ASA will be rebooted. Explanation The CPU or memory resource allocation for the ASA virtual machine has exceeded the
allowed limit for this platform. This condition does not occur unless the setting for the ASA virtual machine has been changed from that specified in the software downloaded from Cisco.
Recommended Action To continue ASA operation, change the CPU or memory resource allocation of the virtual machine to what was specified with the software downloaded from Cisco or to the resource limits specified in the Cisco ASA 1000V CLI Configuration Guide for this platform.
770002
Error Message %ASA-1-770002: Resource resource allocation is more than the permitted limit for this platform. ASA will be rebooted. Explanation The CPU or memory resource allocation for the ASA virtual machine has exceeded the allowed limit for this platform. This condition does not occur unless the setting for the ASA virtual machine has been changed from that specified in the software downloaded from Cisco. The ASA will continue to reboot if the resource allocation is not changed. Recommended Action Change the CPU or memory reosurce allocation to the virtual machine to what
was specified with the software downloaded from Cisco or to the resource limits specified in the Cisco ASA 1000V CLI Configuration Guide for this platform.
1-614
Chapter 1
770003
Error Message %ASA-4-770003: Resource resource allocation is less than the minimum requirement of value for this platform. If this condition persists, performance will be lower than normal. Explanation The CPU or memory resource allocation to the ASA virtual machine is less than the
minimum requirement for this platform. If this condition persists, performance will be lower than normal.
Recommended Action To continue ASA operation, change the CPU or memory reosurce allocation of the virtual machine to what was specified with the software downloaded from Cisco or see the memory limit and CPU reservation settings specified in the Cisco ASA 1000V CLI Configuration Guide for this platform.
771001
Error Message %ASA-5-771001: CLOCK: System clock set, source: src, before: time, after: time Explanation The system clock was set from a local source.
srcThe time protocol, which can be any of the following: NTP, SNTP, VINES, or the RFC-868 time protocol ipThe IP address of the time server timeThe time string in the form, Sun Apr 1 12:34:56.789 EDT 2012
771002
Error Message %ASA-5-771002: CLOCK: System clock set, source: src, IP ip, before: time, after: time Explanation The system clock was set from a remote source.
srcThe time source, which can be either manual or hardware calendar ipThe IP address of the time server timeThe time string in the form, Sun Apr 1 12:34:56.789 EDT 2012
1-615
Syslog Messages
772002
Error Message %ASA-3-772002: PASSWORD: console login warning, user username, cause: password expired Explanation A user logged into the system console with an expired password, which is permitted to avoid system lockout.
usernameThe name of the user
Recommended Action The user should change the login password.
772003
Error Message %ASA-2-772003: PASSWORD: session login failed, user username, IP ip, cause: password expired Explanation A user logged tried to log into the system with an expired password and was denied
access.

sessionThe session type, which can be SSH or Telnet usernameThe name of the user ipThe IP address of the user
Recommended Action If the user has authorized access, an administrator must change the password for the user. Unauthorized access attempts should trigger an appropriate response, for example. traffic from that IP address can be blocked.
772004
Error Message %ASA-3-772004: PASSWORD: session login failed, user username, IP ip, cause: password expired Explanation A user logged tried to log into the system with an expired password and was denied
access.

sessionThe session type, which is ASDM usernameThe name of the user ipThe IP address of the user
Recommended Action If the user has authorized access, an administrator must change the password for the user. Unauthorized access attempts should trigger an appropriate response, for example. traffic from that IP address can be blocked.
1-616
Chapter 1
772005
Error Message %ASA-6-772005: REAUTH: user username passed authentication Explanation The user authenticated successfully after changing the password.
772006
Error Message %ASA-2-772006: REAUTH: user username failed authentication Explanation The user entered the wrong password while trying to change it. As a result, the password
was not changed.
Recommended Action The user should retry changing the password using the change-password
command.
774001
Error Message %ASA-2-774001: POST: unspecified error Explanation The crypto service provider failed the power on self-test. Recommended Action Contact the Cisco TAC.
774002
Error Message %ASA-2-774002: POST: error err, func func, engine eng, algorithm alg, mode mode, dir dir, key len len Explanation The crypto service provider failed the power on self-test.
errThe failure cause funcThe function engThe engine, which can be NPX, Nlite, or software algThe algorithm, which can be any of the following: RSA, DSA, DES, 3DES, AES, RC4, MD5, SHA1, SHA256, SHA386, SHA512, HMAC-MD5, HMAC-SHA1, HMAC-SHA2, or AES-XCBC modeThe mode, which can be any of the following: none, CBC, CTR, CFB, ECB, stateful-RC4, or stateless-RC4
1-617
Syslog Messages
dirEither encryption or decryption lenThe key length in bits
775001
Error Message %ASA-6-775001: Scansafe: protocol connection conn_id from interface_name:real_address/real_port [(idfw_user)] to interface_name:real_address/real_port redirected to server_interface_name:server_ip_address Explanation A ScanSafe server is configured, and traffic matches a policy that has been configured
to redirect the connection to the ScanSafe server for content scanning and other malware protection services.
775002
Error Message %ASA-4-775002: Reason - protocol connection conn_id from interface_name:real_address/real_port [(idfw_user)] to interface_name:real_address/real_port is action locally Explanation If the source IP address and port of the new ScanSafe redirected connection matches the existing connection, then the ASA drops the new connection and this syslog message is generated.
Reason Duplicate connection with same source address and port port
Recommended Action Make sure of all of the following:
The ScanSafe license key is configured. The public key is configured. The ScanSafe server is reachable by the ASA. The maximum number of connections has not been reached.
Note
Configuring PAT and ScanSafe on a single connection are not recommended.
1-618
Chapter 1
775003
Error Message %ASA-6-775003: Scansafe:protocol connection conn_id from interface_name:real_address/real_port [(idfw_user)] to interface_name:real_address/real_port is whitelisted. Explanation The traffic has been matched and does not need to be redirected to the ScanSafe server
for content scanning, but can be sent directly to the intended web server.
775004
Error Message %ASA-4-775004: Scansafe: Primary server ip_address is not reachable Explanation The primary ScanSafe server is not reachable on either of the configured HTTP or HTTPS ports. Recommended Action None required.
775005
Error Message %ASA-6-775005: Scansafe: Primary server ip_address is reachable now Explanation The primary ScanSafe server is reachable on both of the configured HTTP and HTTPS
ports.
775006
Error Message %ASA-6-775006: Primary server interface:ip_address is not reachable and backup server interface:ip_address is now active Explanation If the primary ScanSafe server becomes unreachable, the ASA checks the connectivity
to the configured backup ScanSafe server; if the backup server is reachable, it becomes the active server.
1-619
Syslog Messages
775007
Error Message %ASA-2-775007: Scansafe: Primary server_interface_name:server_ip_address and backup server_interface_name:server_ip_address servers are not reachable. Explanation Neither the primary nor backup ScanSafe server is reachable. Based on the configured default action( fail_close or fail_open), traffic is getting dropped or sent to the web server without being redirected. Recommended Action If both the ScanSafe servers are not reachable, you can change the ScanSafe
configuration to fail_open to send traffic to the web server without having it redirected to the ScanSafe server. This configuration changes the default action to permit.
778001
Error Message %ASA-6-778001: VXLAN: Invalid VXLAN segment-id segment-id for protocol from ifc-name:(IP-address/port) to ifc-name:(IP-address/port). Explanation The ASA tries to create an inner connection for a VXLAN packet, but the VXLAN
packet has an invalid segment ID.

778002
Error Message %ASA-6-778002: VXLAN: There is no VNI interface for segment-id segment-id. Explanation A decapsulated ingress VXLAN packet is discarded, because the segment ID in the VXLAN header does not match the segment ID of any VNI interface configured on the ASA. Recommended Action None required.
778003
Error Message %ASA-6-778003: VXLAN: Invalid VXLAN segment-id segment-id for protocol from ifc-name:(IP-address/port) to ifc-name:(IP-address/port) in FP. Explanation The ASA Fast Path sees a VXLAN packet with an invalid segment ID. Recommended Action Check the VNI interface segment ID configurations to see if the dropped packet has the VXLAN segment ID that does not match any VNI segment ID configuration.
1-620
Chapter 1
778004
Error Message %ASA-6-778004: VXLAN: Invalid VXLAN header for protocol from ifc-name:(IP-address/port) to ifc-name:(IP-address/port) in FP. Explanation The ASA VTEP sees a VXLAN packet with an invalid VXLAN header. Recommended Action None required.
778005
Error Message %ASA-6-778005: VXLAN: Packet with VXLAN segment-id segment-id from ifc-name is denied by FP L2 check. Explanation A VXLAN packet is denied by a Fast Path L2 check. Recommended Action Check the VNI interface segment ID configurations to see if the dropped packet has the VXLAN segment ID that does not match any VNI segment ID configuration. Check to see i f the STS table has an entry that matches the dropped packets segment ID.
778006
Error Message %ASA-6-778006: VXLAN: Invalid VXLAN UDP checksum from ifc-name:(IP-address/port) to ifc-name:(IP-address/port) in FP. Explanation The ASA VTEP received a VXLAN packet with an invalid UDP checksum value. Recommended Action None required.
778007
Error Message %ASA-6-778007: VXLAN: Packet from ifc-name:IP-address/port to IP-address/port was discarded due to invalid NVE peer. Explanation The ASA VTEP received a VXLAN packet from an IP address that is different from the
configured NVE peer.

1-621
Syslog Messages
779001
Error Message %ASA-6-779001: STS: Out-tag lookup failed for in-tag segment-id of protocol from ifc-name:IP-address/port to IP-address/port. Explanation The ASA tries to create a connection for a VXLAN packet, but failed to use the STS
lookup table to locate the out-tag for the in-tag (segment ID) in the VXLAN packet.
779002
Error Message %ASA-6-779002: STS: STS and NAT locate different egress interface for segment-id segment-id, protocol from ifc-name:IP-address/port to IP-address/port Explanation The ASA tries to create a connection for a VXLAN packet, but the STS lookup table
and NAT policy locate a different egress interface.

779003
Error Message %ASA-3-779003: STS: Failed to read tag-switching table - reason Explanation The ASA tried to read the tag-switching table, but failed. Recommended Action None required.
779004
Error Message %ASA-3-779004: STS: Failed to write tag-switching table - reason Explanation The ASA tried to write to the tag-switching table, but failed. Recommended Action None required.
1-622
Chapter 1
779005
Error Message %ASA-3-779005: STS: Failed to parse tag-switching request from http reason Explanation The ASA tried to parse the HTTP request to see what to do on the tag-switching table,
but failed.
779006
Error Message %ASA-3-779006: STS: Failed to save tag-switching table to flash reason Explanation The ASA tried to save the tag-switching table to flash memory, but failed. Recommended Action None required.
779007
Error Message %ASA-3-779007: STS: Failed to replicate tag-switching table to peer reason Explanation The ASA attempts to replicate the tag-switching table to the failover standby unit or clustering slave units, but failed to do so. Recommended Action None required.
780001
Error Message %ASA-6-780001: RULE ENGINE: Started compilation for access-group transaction - description of the transaction. Explanation The rule engine has started compilation for an access group transaction. The description of the transaction is the command line input of the access group itself. Recommended Action None required.
1-623
Syslog Messages
780002
Error Message %ASA-6-780002: RULE ENGINE: Finished compilation for access-group transaction - description of the transaction. Explanation The rule engine has finished compilation for a transaction. Taking access group as an
example, the description of the transaction is the command line input of the access group itself.
780003
Error Message %ASA-6-780003: RULE ENGINE: Started compilation for nat transaction description of the transaction. Explanation The rule engine has started compilation for a NAT transaction. The description of the transaction is the command line input of the nat command itself. Recommended Action None required.
780004
Error Message %ASA-6-780004: RULE ENGINE: Finished compilation for nat transaction - description of the transaction. Explanation The rule engine has finished compilation for a NAT transaction. The description of the transaction is the command line input of the nat command itself. Recommended Action None required.
1-624

Logmsgs - SYS Logs

Uploaded by

Copyright:

Available Formats

Logmsgs - SYS Logs

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Logmsgs - SYS Logs

Uploaded by

Copyright:

Available Formats

C H A P T E R

Syslog Message Classes and Associated Message ID Numbers

ASA Series Syslog Messages

Syslog Message Classes and Associated Message ID Numbers (continued)

Network Admission Control Settings 732

ASA Series Syslog Messages

Syslog Messages Messages 101001 to 199021

Syslog Message Classes and Associated Message ID Numbers (continued)

Class webfo webvpn xlate

Definition Web-based Failover Web-based VPN NAT and PAT

Syslog Message ID Numbers 721 716 305

This chapter includes the following sections:

Messages 101001 to 199021

Secondary for the secondary unit.

ASA Series Syslog Messages

Chapter 1 Messages 101001 to 199021

ASA Series Syslog Messages

Syslog Messages Messages 101001 to 199021

Recommended Action Verify the status of the primary unit.

ASA Series Syslog Messages

Chapter 1 Messages 101001 to 199021

ASA Series Syslog Messages

Syslog Messages Messages 101001 to 199021

ASA Series Syslog Messages

Chapter 1 Messages 101001 to 199021

ASA Series Syslog Messages

Syslog Messages Messages 101001 to 199021

Primary can also be listed as Secondary for the secondary unit.

ASA Series Syslog Messages

Chapter 1 Messages 101001 to 199021

ASA Series Syslog Messages

Syslog Messages Messages 101001 to 199021

connectivity problem exists on the LAN failover interface.

ASA Series Syslog Messages

Chapter 1 Messages 101001 to 199021

ASA Series Syslog Messages

Syslog Messages Messages 101001 to 199021

Primary can also be listed as Secondary for the secondary ASA.

ASA Series Syslog Messages

Chapter 1 Messages 101001 to 199021

is different from my io_card_name2

ASA Series Syslog Messages

Syslog Messages Messages 101001 to 199021

Recommended Action None required.

ASA Series Syslog Messages

Chapter 1 Messages 101001 to 199021

risk, the packet was discarded.

ASA Series Syslog Messages

Syslog Messages Messages 101001 to 199021

denied access unless specifically allowed.

ASA Series Syslog Messages

Chapter 1 Messages 101001 to 199021

provide enough information to determine where the attack originates.

ASA Series Syslog Messages

Syslog Messages Messages 101001 to 199021

is required. The ASA repels the attack.

ASA Series Syslog Messages

Chapter 1 Messages 101001 to 199021

ASA Series Syslog Messages