Table Of Contents
Syslog Messages
This chapter lists the syslog messages in numerical order.
Note
When a number is skipped in a sequence, the message is no longer in the security appliance code.
For information about how to configure logging and SNMP, see the Cisco Security Appliance Command Line Configuration Guide.
Table 1-1 lists the syslog message classes and the ranges of syslog message IDs associated with each class. The valid range of syslog message IDs is between 100000 and 999999, respectively.
This chapter includes the following sections:
Messages 101001 to 199012
This section contains messages from 101001 to 199012.
101001
Error Message %PIX|ASA-1-101001: (Primary) Failover cable OK.Explanation This is a failover message. This message reports that 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 %PIX|ASA-1-101002: (Primary) Bad failover cable.Explanation This is a failover message. This message reports that 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.
101003, 101004
Error Message %PIX|ASA-1-101003: (Primary) Failover cable not connected (this unit).Error Message %PIX|ASA-1-101004: (Primary) Failover cable not connected (other unit).Explanation Both instances are failover messages. These messages are logged when 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 %PIX|ASA-1-101005: (Primary) Error reading failover cable status.Explanation This is a failover message. This message is displayed if the failover cable is connected, but the primary unit is unable to determine its status.
Recommended Action Replace the cable.
102001
Error Message %PIX|ASA-1-102001: (Primary) Power failure/System reload other side.Explanation This is a failover message. This message is logged if the primary unit detects a system reload or a power failure on the other unit. "Primary" can also be listed as "Secondary" for the secondary unit.
Recommended Action On the unit that experienced the reload, issue the show crashinfo command to determine if there is a traceback associated with the reload. Also verify that the unit is powered on and that power cables are properly connected.
103001
Error Message %PIX|ASA-1-103001: (Primary) No response from other firewall (reason code = code).Explanation This is a failover message. This message is displayed if 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.
Recommended Action Verify that the failover cable is connected properly and both units have the same hardware, software, and configuration. If the problem persists, contact the Cisco TAC.
103002
Error Message %PIX|ASA-1-103002: (Primary) Other firewall network interface interface_number OK.Explanation This is a failover message. This message is displayed when the primary unit detects 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 %PIX|ASA-1-103003: (Primary) Other firewall network interface interface_number failed.Explanation This is a failover message. This message is displayed if the primary unit detects 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 check the network hub connection. If necessary, replace the failed network interface.
103004
Error Message %PIX|ASA-1-103004: (Primary) Other firewall reports this firewall failed.Explanation This is a failover message. This message is displayed if the primary unit receives a message from the secondary unit indicating that the primary has failed. (Primary) can also be listed as (Secondary) for the secondary unit.
Recommended Action Verify the status of the primary unit.
103005
Error Message %PIX|ASA-1-103005: (Primary) Other firewall reporting failure.Explanation This is a failover message. This message is displayed if the secondary unit reports a 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 %PIX|ASA-1-103006: (Primary|Secondary) Mate version ver_num is not compatible with ours ver_numExplanation This message appears when PIX firewall detects peer unit is running a version that is not the same as local unit and also is not compatible with HA Hitless Upgrade feature.
•
Recommended Action Install same or compatible versions image on both firewall units.
103007
Error Message %PIX|ASA-1-103007: (Primary|Secondary) Mate version ver_num is not identical with ours ver_numExplanation This message appears when PIX firewall detects peer unit is running a version that is not identical but does support Hitless Upgrade and is compatible with local unit. The system performance could be degraded due to the image version not being equal and could encounter a stability issue if running for extended period.
•
Recommended Action Install same version image on both units as soon as possible.
104001, 104002
Error Message %PIX|ASA-1-104001: (Primary) Switching to ACTIVE (cause: string).Error Message %PIX|ASA-1-104002: (Primary) Switching to STNDBY (cause: string).Explanation Both instances are failover messages. These messages usually are logged when you force the 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:
•
•
•
•
•
•
•
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 %PIX|ASA-1-104003: (Primary) Switching to FAILED.Explanation This is a failover message. This message is displayed when the primary unit fails.
Recommended Action Check the syslog 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 %PIX|ASA-1-104004: (Primary) Switching to OK.Explanation This is a failover message. This message is displayed when a previously failed unit now reports that it is operating again. (Primary) can also be listed as (Secondary) for the secondary unit.
Recommended Action None required.
105001
Error Message %PIX|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 %PIX|ASA-1-105002: (Primary) Enabling failover.Explanation This is a failover message, which is displayed when you enter 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 %PIX|ASA-1-105003: (Primary) Monitoring on interface interface_name waitingExplanation This is a failover message. The security appliance 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 security appliance monitors its network interfaces frequently during normal operations.
105004
Error Message %PIX|ASA-1-105004: (Primary) Monitoring on interface interface_name normalExplanation This is a failover message. The test of the specified network interface was successful. (Primary) can also be listed as (Secondary) for the secondary unit.
Recommended Action None required.
105005
Error Message %PIX|ASA-1-105005: (Primary) Lost Failover communications with mate on interface interface_name.Explanation This is a failover message. This message is displayed if this 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 %PIX|ASA-1-105006: (Primary) Link status `Up' on interface interface_name.Error Message %PIX|ASA-1-105007: (Primary) Link status `Down' on interface interface_name.Explanation Both instances are failover messages. These messages report the results of monitoring the link status of the specified interface. (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 %PIX|ASA-1-105008: (Primary) Testing interface interface_name.Explanation This is a failover message. This message is displayed when the tests a specified network interface. This testing is performed only if the security appliance 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 %PIX|ASA-1-105009: (Primary) Testing on interface interface_name {Passed|Failed}.Explanation This is a failover message. This message reports the result (either Passed or Failed) of a previous interface test. (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.
105010
Error Message %PIX|ASA-3-105010: (Primary) Failover message block alloc failedExplanation Block memory was depleted. This is a transient message and the security appliance 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 %PIX|ASA-1-105011: (Primary) Failover cable communication failureExplanation 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 properly connected.
105020
Error Message %PIX|ASA-1-105020: (Primary) Incomplete/slow config replicationExplanation When a failover occurs, the active security appliance 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 security appliance, the security appliance automatically reloads itself and loads configuration from Flash memory and/or resynchronizes with another security appliance. If failovers happen continuously, check the failover configuration and make sure both security appliance units can communicate with each other.
105021
Error Message %PIX|ASA-1-105021: (failover_unit) Standby unit failed to sync due to a locked context_name config. Lock held by lock_owner_nameExplanation During configuration synchronizing, a standby unit will reload itself if some other process locks the configuration for more than 5 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 EXEC command and the pager lines num CONFIG command.
Recommended Action Avoid viewing or modifying configuration on standby unit when it first comes up and is in the process of establishing a failover connection with the active unit.
105031
Error Message %PIX|ASA-1-105031: Failover LAN interface is upExplanation LAN failover interface link is up.
Recommended Action None required.
105032
Error Message %PIX|ASA-1-105032: LAN Failover interface is downExplanation LAN failover interface link is down.
Recommended Action Check the connectivity of the LAN failover interface. Make sure that the speed/duplex setting is correct.
105034
Error Message %PIX|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 %PIX|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 %PIX|ASA-1-105036: dropped a LAN Failover command message.Explanation The security appliance dropped an unacknowledged LAN failover command message, indicating a connectivity problem on the LAN failover interface.
Recommended Action Check that the LAN interface cable is connected.
105037
Error Message %PIX|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.
Recommended Action Check that the LAN interface cable is connected.
105038
Error Message %PIX|ASA-1-105038: (Primary) Interface count mismatchExplanation When a failover occurs, the active security appliance 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 security appliance, the security appliance automatically reloads itself and loads the configuration from Flash memory and/or resyncs with another security appliance. If failovers happen continuously, check the failover configuration and make sure that both security appliance units can communicate with each other.
105039
Error Message %PIX|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 security appliances are the same. This message indicates that the primary security appliance is not able to verify the number of interfaces configured on the secondary security appliance. This message indicates that the primary security appliance is not able communicate with the secondary security appliance over the failover interface. (Primary) can also be listed as (Secondary) for the secondary security appliance.
Recommended Action Verify the failover LAN, interface configuration, and status on the primary and secondary security appliances. Make sure that the secondary security appliance is running the security appliance application and that failover is enabled.
105040
Error Message %PIX|ASA-1-105040: (Primary) Mate failover version is not compatible.Explanation The primary and secondary security appliance should run the same failover software version to act as a failover pair. This message indicates that the secondary security appliance failover software version is not compatible with the primary security appliance. Failover is disabled on the primary security appliance. (Primary) can also be listed as (Secondary) for the secondary security appliance.
Recommended Action Maintain consistent software versions between the primary and secondary security appliances to enable failover.
105042
Error Message %PIX|ASA-1-105042: (Primary) Failover interface OKExplanation LAN failover interface link is up.
Explanation The interface used to send failover messages to the secondary security appliance is functioning. (Primary) can also be listed as (Secondary) for the secondary security appliance.
Recommended Action None required.
105043
Error Message %PIX|ASA-1-105043: (Primary) Failover interface failedExplanation LAN failover interface link is down.
Recommended Action Check the connectivity of the LAN failover interface. Make sure that the speed/duplex setting is correct.
105044
Error Message %PIX|ASA-1-105044: (Primary) Mate operational mode mode is not compatible with my mode mode.Explanation When the operational mode (single or multi) 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.
105045
Error Message %PIX|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 %PIX|ASA-1-105046 (Primary|Secondary) Mate has a different chassisExplanation This message is issued when two failover units have a different type of chassis. For example, one is a PIX, the other is an ASA-5520, or one has a 3-slot chassis, the other has a 6-slot chassis.
Recommended Action Make sure that the two failover units are the same.
105047
Error Message %PIX|ASA-1-105047: Mate has a io_card_name1 card in slot slot_number which is different from my io_card_name2Explanation 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) Mate's 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.
•
•
Recommended Action Make sure that both units have identical service modules before trying to re-enable failover.
106001
Error Message %PIX|ASA-2-106001: Inbound TCP connection denied from IP_address/port to IP_address/port flags tcp_flags on interface interface_nameExplanation This is a connection-related message. This message occurs when an attempt to connect to an inside address is denied by the security policy that is defined for the specified traffic type. 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 security appliance, and it was dropped. The tcp_flags in this packet are FIN and ACK.
The tcp_flags are as follows:
•
•
•
•
•
•
Recommended Action None required.
106002
Error Message %PIX|ASA-2-106002: protocol Connection denied by outbound list acl_ID src inside_address dest outside_addressExplanation This is a connection-related message. This message is displayed if the specified connection fails 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 %PIX|ASA-2-106006: Deny inbound UDP from outside_address/outside_port to inside_address/inside_port on interface interface_name.Explanation This is a connection-related message. This message is displayed if an inbound UDP packet is denied by the security policy that is defined for the specified traffic type.
Recommended Action None required.
106007
Error Message %PIX|ASA-2-106007: Deny inbound UDP from outside_address/outside_port to inside_address/inside_port due to DNS {Response|Query}.Explanation This is a connection-related message. This message is displayed if a UDP packet containing a DNS query or response is 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 %PIX|ASA-3-106010: Deny inbound protocol src interface_name:dest_address/dest_port dst interface_name:source_address/source_portExplanation This is a connection-related message. This message is displayed if an inbound connection is 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 %PIX|ASA-3-106011: Deny inbound (No xlate) stringExplanation The message will appear 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 security appliance receives the reset, this message will appear. It can typically be ignored.
Recommended Action Prevent this syslog message from getting logged to the syslog server by entering the no logging message 106011 command.
106012
Error Message %PIX|ASA-6-106012: Deny IP from IP_address to IP_address, IP options hex.Explanation This is a packet integrity check message. 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.
106013
Error Message %PIX|ASA-2-106013: Dropping echo request from IP_address to PAT address IP_addressExplanation The security appliance 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 %PIX|ASA-3-106014: Deny inbound icmp src interface_name: IP_address dst interface_name: IP_address (type dec, code dec)Explanation The security appliance denied any inbound ICMP packet access. By default, all ICMP packets are denied access unless specifically permitted.
Recommended Action None required.
106015
Error Message %PIX|ASA-6-106015: Deny TCP (no connection) from IP_address/port to IP_address/port flags tcp_flags on interface interface_name.Explanation The security appliance discarded a TCP packet that has no associated connection in the security appliance connection table. The security appliance 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 not an existing connection, the security appliance discards the packet.
Recommended Action None required unless the security appliance 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.
106016
Error Message %PIX|ASA-2-106016: Deny IP spoof from (IP_address) to IP_address on interface interface_name.Explanation This message is generated when a packet arrives at the security appliance interface that has a destination IP address of 0.0.0.0 and a destination MAC address of the security appliance interface. In addition, this message is generated when the security appliance discarded a packet with an invalid source address, which may include one of the following or some other invalid address:
•
•
•
To further enhance spoof packet detection, use the icmp command to configure the security appliance 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 %PIX|ASA-2-106017: Deny IP due to Land Attack from IP_address to IP_addressExplanation The security appliance 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 %PIX|ASA-2-106018: ICMP packet type ICMP_type denied by outbound list acl_ID src inside_address dest outside_addressExplanation 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.
Recommended Action None required.
106020
Error Message %PIX|ASA-2-106020: Deny IP teardrop fragment (size = number, offset = number) from IP_address to IP_addressExplanation The security appliance discarded an IP packet with a teardrop signature containing either a small offset or fragment overlapping. This is a hostile event that circumvents the security appliance or an Intrusion Detection System.
Recommended Action Contact the remote peer administrator or escalate this issue according to your security policy.
106021
Error Message %PIX|ASA-1-106021: Deny protocol reverse path check from source_address to dest_address on interface interface_nameExplanation 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 security appliance.
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 security appliance checks packets arriving from the outside.
The security appliance looks up a route based on the source_address. If an entry is not found and a route is not defined, then this syslog message appears and the connection is dropped.
If there is a route, the security appliance 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 security appliance does not support asymmetric routing.
If the security appliance 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 security appliance repels the attack.
106022
Error Message %PIX|ASA-1-106022: Deny protocol connection spoof from source_address to dest_address on interface interface_nameExplanation A packet matching a connection arrives on a different interface from the interface that the connection began on.
For example, if a user starts a connection on the inside interface, but the security appliance detects the same connection arriving on a perimeter interface, the security appliance has more than one path to a destination. This is known as asymmetric routing and is not supported on the security appliance.
An attacker also might be attempting to append packets from one connection to another as a way to break into the security appliance. In either case, the security appliance displays this message and drops the connection.
Recommended Action This message appears when the ip verify reverse-path command is not configured. Check that the routing is not asymmetric.
106023
Error Message %PIX|ASA-4-106023: Deny protocol src [interface_name:source_address/source_port] dst interface_name:dest_address/dest_port [type {string}, code {code}] by access_group acl_IDExplanation A real IP packet was denied by the ACL. This message displays even if you do not have the log option enabled for an ACL.
Recommended Action If messages persist from the same source address, messages might indicate a foot-printing or port-scanning attempt. Contact the remote host administrators.
106024
Error Message %PIX|ASA-2-106024: Access rules memory exhaustedExplanation 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 system, 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 %PIX|ASA-6-106025: Failed to determine the security context for the packet:sourceVlan:source_address dest_address source_port dest_port protocolError Message %PIX|ASA-6-106026: Failed to determine the security context for the packet:sourceVlan:source_address dest_address source_port dest_port protocolExplanation 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.
106027
Error Message %PIX|ASA-4-106027:Failed to determine the security context for the packet:vlansource Vlan#:ethertype src sourceMAC dst destMACExplanation 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.
Recommended Action None required.
106100
Error Message %PIX|ASA-6-106100: access-list acl_ID {permitted | denied | est-allowed} protocol interface_name/source_address(source_port) -> interface_name/dest_address(dest_port) hit-cnt number ({first hit | number-second interval}) hash codesExplanation This message is generated any time that a packet is seen that does not match an existing connection on the security appliance. The message indicates either the initial occurrence or the total number of occurrences during an interval. 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 syslog ID might be triggered because of a non-synchronized packet reaching the security appliance and being evaluated by the access-list. For example, if an ACK packet is received on the security appliance (for which no TCP connection exists in the connection table), the device might generate syslog 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:
Explanation permitted | denied | est-allowed —These 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).
•
•
•
•
•
•
•
•
•
•
Recommended Action None required.
106101
Error Message %PIX|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 security appliance caches the flow information. This message indicates that the number of matching flows that are cached on the security appliance exceeds the user-configured limit (using the access-list deny-flow-max command).
The number value is the limit configured using the access-list deny-flow-max command.
Recommended Action None required. This message might be generated as a result of a DoS attack.
106102
Error Message %ASA-6-106102: access-list acl_ID {permitted|denied} protocol interface_name/source_address source_port interface_name/dest_address dest_port hit-cnt number {first hit|number-second interval}Explanation This message indicates that a packet was either permitted or denied by an access list that is applied through a VPN filter.
Recommended Action None required.
107001
Error Message %PIX|ASA-1-107001: RIP auth failed from IP_address: version=number, type=string, mode=string, sequence=number on interface interface_nameExplanation This is an alert log message. The security appliance received a RIP reply message with bad authentication. This message might be caused by a misconfiguration on the router or the security appliance or by an unsuccessful attempt to attack the routing table of the security appliance.
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 %PIX|ASA-1-107002: RIP pkt failed from IP_address: version=number on interface interface_nameExplanation This is an alert log message. This message could be caused by a router bug, a packet with non-RFC values inside, or a malformed entry. This should not happen, and may be an attempt to exploit routing table of the security appliance.
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.
107003
Error Message %PIX-3-107003: RIP: Attempted reference of stale data encountered in function, line: line_numExplanation This syslog message is generated when RIP is running and tries to reference some related data structures that have been removed elsewhere. Clearing the interface and router configurations might correct the problem. However, when this syslog message appears, it is an indication that some sequence of steps caused premature deletion of data structures and that should be investigated.
•
•
Recommended Action Copy the error message exactly as it appears, and report it to Cisco TAC.
108002
Error Message %PIX|ASA-2-108002: SMTP replaced string: out source_address in inside_address data: stringExplanation This is a Mail Guard (SMTP) message generated by the inspect esmtp command. This message is displayed if the security appliance replaces an invalid character in an e-mail address with a space.
Recommended Action None required.
108003
Error Message %PIX|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:stringExplanation This message is generated by Mail Guard (SMTP). This message is displayed if the security appliance detects malicious pattern in an e-mail address and drops the connection. This indicates an attack in progress.
Recommended Action None required.
108004
Error Message %PIX|ASA-4-108004: action_class: action ESMTP req_resp from src_ifc:sip|sport to dest_ifc:dip|dport;further_infoExplanation This event is generated when a ESMTP classification is performed on a ESMTP message and the specified criteria are satisfied. The configured action is taken.
•
•
•
•
•
•
•
•
For 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).
Recommended Action None required.
108005
Error Message %PIX|ASA-6-108005: action_class: Received ESMTP req_resp from src_ifc:sip|sport to dest_ifc:dip|dport;further_infoExplanation This event is generated when a ESMTP classification is performed on a ESMTP message and the specified criteria are satisfied. The standalone log action is taken.
•
•
•
•
•
•
•
For single match command: matched Class id: match_command (for example, matched Class 1234: match body length 100).
For parameter commands (commands under parameter section): parameter-command: descriptive-message (for example, mail-relay: No Mail Relay allowed).
Recommended Action None required.
108006
Error Message %PIX|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.
•
•
•
•
•
•
Recommended Action None required.
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 portExplanation This message indicates that 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.
•
•
•
•
•
•
Recommended Action Log and review the message. Check whether the ESMTP policy map associated with this connection has the following setting: "allow-tls action log." If not, contact the Cisco TAC.
109001
Error Message %PIX|ASA-6-109001: Auth start for user user from inside_address/inside_port to outside_address/outside_portExplanation This is an authentication, authorization and accounting (AAA) message. This message is displayed if the security appliance is configured for AAA and detects an authentication request by the specified user.
Recommended Action None required.
109002
Error Message %PIX|ASA-6-109002: Auth from inside_address/inside_port to outside_address/outside_port failed (server IP_address failed) on interface interface_name.Explanation This is a AAA message. This message is displayed if an authentication request fails 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.
109003
Error Message %PIX|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 This is a AAA message. This message is displayed if no authentication server can be found.
Recommended Action Ping the authentication servers from the security appliance. Make sure that the daemons are running.
109005
Error Message %PIX|ASA-6-109005: Authentication succeeded for user user from inside_address/inside_port to outside_address/outside_port on interface interface_name.Explanation This is a AAA message. This message is displayed when the specified authentication request succeeds.
Recommended Action None required.
109006
Error Message %PIX|ASA-6-109006: Authentication failed for user user from inside_address/inside_port to outside_address/outside_port on interface interface_name.Explanation This is a AAA message. This message is displayed if the specified authentication request fails, possibly because of an incorrect password.
Recommended Action None required.
109007
Error Message %PIX|ASA-6-109007: Authorization permitted for user user from inside_address/inside_port to outside_address/outside_port on interface interface_name.Explanation This is a AAA message. This message is displayed when the specified authorization request succeeds.
Recommended Action None required.
109008
Error Message %PIX|ASA-6-109008: Authorization denied for user user from outside_address/outside_port to inside_address/ inside_port on interface interface_name.Explanation This is a AAA message. This message is displayed if a user is not authorized to access the specified address, possibly because of an incorrect password.
Recommended Action None required.
109010
Error Message %PIX|ASA-3-109010: Auth from inside_address/inside_port to outside_address/outside_port failed (too many pending auths) on interface interface_name.Explanation This is a AAA message. This message is displayed if 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 %PIX|ASA-2-109011: Authen Session Start: user 'user', sid numberExplanation An authentication session started between the host and the security appliance and has not yet completed.
Recommended Action None required.
109012
Error Message %PIX|ASA-5-109012: Authen Session End: user 'user', sid number, elapsed number secondsExplanation 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.
109013
Error Message %PIX|ASA-3-109013: User must authenticate before using this serviceExplanation The user must be authenticated before using the service.
Recommended Action Authenticate using FTP, Telnet, or HTTP before using the service.
109014
Error Message %PIX|ASA-7-109014: uauth_lookup_net fail for uauth_in()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 %PIX|ASA-3-109016: Can't find authorization ACL acl_ID for user 'user'Explanation The access control list specified on the AAA server for this user does not exist on the security appliance. This error can occur if you configure the AAA server before you configure the security appliance. The Vender-Specific Attribute (VSA) on your AAA server might be one of the following values:
•
•
•
Recommended Action Add the ACL to the security appliance, making sure to use the same name specified on the AAA server.
109017
Error Message %PIX|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.
109018
Error Message %PIX|ASA-3-109018: Downloaded ACL acl_ID is emptyExplanation The downloaded authorization access control list 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 %PIX|ASA-3-109019: Downloaded ACL acl_ID has parsing error; ACE stringExplanation An error is encountered during parsing the sequence number NNN in the attribute string ip:inacl#NNN= of a downloaded authorization access control list. The reasons include: - missing = - contains non-numeric, non-space characters between '#' and '=' - NNN is greater than 999999999.
ip:inacl# 1 permit tcp any anyip:inacl# 1junk2=permit tcp any anyip:inacl# 1000000000=permit tcp any anyRecommended Action Correct the ACL element that has the indicated error on the AAA server.
109020
Error Message %PIX|ASA-3-109020: Downloaded ACL has config error; ACEExplanation One of the components of the downloaded authorization access control list has a configuration error. The entire text of the element is included in the syslog 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 %PIX|ASA-7-109021: Uauth null proxy errorExplanation An internal User Authentication error has occurred.
Recommended Action None required. However, if this error appears repeatedly, contact the Cisco TAC.
109022
Error Message %PIX|ASA-4-109022: exceeded HTTPS proxy process limitExplanation For each HTTPS authentication, the security appliance dedicates a process to service the authentication request. When the number of concurrently running processes exceeds the system-imposed limit, the security appliance does not perform the authentication, and this message is displayed.
Recommended Action None required.
109023
Error Message %PIX|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 This is a AAA message. 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 the above service port.
109024
Error Message %PIX|ASA-6-109024: Authorization denied from source_address/source_port to dest_address/dest_port (not authenticated) on interface interface_name using protocolExplanation This is a AAA message. This message is displayed if the security appliance is configured for AAA and a user attempted to make a TCP connection across the security appliance without prior authentication.
Recommended Action None required.
109025
Error Message %PIX|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 protocolExplanation The access control list 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 access control list acl_ID, which was defined per the AAA authorization policy on Cisco Secure Access Control Server (ACS).
Recommended Action None required.
109026
Error Message %PIX|ASA-3-109026: [aaa protocol] Invalid reply digest received; shared server key may be mismatched.Explanation The response from the AAA server could not be validated. It is likely that the configured server key is incorrect. This event 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 %PIX|ASA-4-109027: [aaa protocol] Unable to decipher response message Server = server_IP_address, User = userExplanation The response from the AAA server could not 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 %PIX|ASA-4-109028: aaa bypassed for same-security traffic from ingress_ interface:source_address/source_port to
egress_interface:dest_address/dest_portExplanation 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.
109029
Error Message %PIX|ASA-5-109029: Parsing downloaded ACL: stringExplanation A syntax error was encountered while parsing an access list that was downloaded from a RADIUS server during user authentication.
•
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 %PIX|ASA-4-109030: Autodetect ACL convert wildcard did not convert ACL access_list source | dest netmask netmask.Explanation This message is displayed when 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 could not determine if the netmask is a wildcard or a normal netmask.
•
•
•
•
Recommended Action Check the access list netmask on the RADIUS server for wildcard configuration. If it is meant to be a wildcard, and if all access list netmasks on that server are wildcard 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. In other words, where the netmask presents consecutive binary 1's. For example, 00000000.00000000.00011111.11111111 or hex 0.0.31.255. If the mask is meant to be normal and all access list netmasks on that server are normal then use the normal setting acl-netmask-convert for the AAA server.
109031
Error Message %PIX|ASA-4-109031: NT Domain Authentication Failed: rejecting guest login for username.Explanation This message is displayed when a user tries to authenticate to an NT Auth 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.
109032
Error Message %PIX|ASA-3-109032: Unable to install ACL access_list, downloaded for user username; Error in ACE: ace.Explanation This message is displayed when an access control list is received from a RADIUS server during the authentication of a network user. The log event indicates a syntax error in one of the elements of the access list. When this occurs, the element is discarded but the rest of access list is still applied. The entire text of the malformed element is included in the message. Note that this condition does not result in an authentication failure.
•
•
•
Recommended Action Correct the access list definition in the RADIUS server configuration.
109033
Error Message %PIX|ASA-4-109033: Authentication failed for admin user user from src_IP. Interactive challenge processing is not supported for protocol connectionsExplanation AAA challenge processing was triggered during authentication of an administrative connection, but the security appliance cannot initiate interactive challenge processing with the client application. When this occurs, the authentication attempt will be rejected and the connection denied.
•
•
•
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 %PIX|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 connectionsExplanation AAA challenge processing was triggered during authentication of a network connection, but the security appliance cannot initiate interactive challenge processing with the client application. When this occurs, the authentication attempt will be rejected and the connection denied.
•
•
•
•
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.
109035
Error Message %ASA-3-109035: Exceeded maximum number (999) of DAP attribute instances for user string.Explanation The Dynamic Access Policy supports multiple values of the same attribute received from an AAA server. If the AAA server should send a response containing more than 999 values for the same attribute, then the ASA will treat this response message as being malformed and reject the authentication. This condition has only been seen in lab environments using specialized test tools. It is unlikely that the condition should occur in a real-world production network.
•
Recommended Action If this message is generated, it would be helpful to capture the authentication traffic between the ASA and AAA server using a protocol sniffer (such as WireShark) and forward the trace file to Cisco Engineering for analysis.
109036
Error Message %ASA-3-109036: RADIUS Server has received a request from unconfigured ip address src_ip_addr, dropping the request.Explanation The local RADIUS Server is not configured to receive requests from the specified source. The local RADIUS Server accepts RADIUS requests only from the IP address using the radius-client-interface if_name [ip ip_address]key secret_key command. RADIUS requests from all other IP addresses are dropped. This message is rate-limited at 1 message every 10 seconds.
•
Recommended Action Investigate who is generating such packets and why. Block the sender if it is not the wireless AP.
109037
Error Message %ASA-6-109037: RADIUS Server has sent an Access Accept message to the client ip-address, user = usernameExplanation The RADIUS Server successfully authenticated a user according to the local database and sent a RADIUS Access-Accept message to the client.
•
•
Recommended Action None required.
109038
Error Message %ASA-6-109038: RADIUS Server has sent an Access Reject message to the client ip-address, user = usernameExplanation The RADIUS Server could not authenticate the user according to the local database and sent an Access-Reject message to the client.
•
•
Recommended Action None required.
110002
Error Message %PIX|ASA-6-110002: Failed to locate egress interface for protocol from src interface:src IP/src port to dest IP/dest portExplanation .An error occurred when the security appliance tried to find the interface through which to send the packet.
•
•
•
•
•
•
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 %PIX|ASA-6-110003: Routing failed to locate next-hop for protocol from src interface:src IP/src port to dest interface:dest IP/dest portExplanation .An error occurred when the security appliance tried to find the next hop on an interface routing table.
•
•
•
•
•
•
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.
111001
Error Message %PIX|ASA-5-111001: Begin configuration: IP_address writing to deviceExplanation This message is displayed when you enter 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 %PIX|ASA-5-111002: Begin configuration: IP_address reading from deviceExplanation This message is displayed when you enter the read command to read your configuration from 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.
111003
Error Message %PIX|ASA-5-111003: IP_address Erase configurationExplanation This is a management message. This message is displayed when you erase 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 security appliance and save the new configuration. Alternatively, you can restore information from a configuration that was previously saved, either on floppy or on a TFTP server elsewhere on the network.
111004
Error Message %PIX|ASA-5-111004: IP_address end configuration: {FAILED|OK}Explanation This message is displayed when you enter 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.
111005
Error Message %PIX|ASA-5-111005: IP_address end configuration: OKExplanation This message is displayed when you exit 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 %PIX|ASA-5-111007: Begin configuration: IP_address reading from device.Explanation This message is displayed when you enter 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.
Recommended Action None required.
111008
Error Message %PIX|ASA-5-111008: User user executed the command stringExplanation The user entered any command, with the exception of a show command.
Recommended Action None required.
111009
Error Message %PIX|ASA-7-111009:User user executed cmd:stringExplanation 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 cmdExplanation This message is generated whenever a user makes a configuration change.
•
•
•
•
Recommended Action None required.
111111
Error Message %PIX|ASA-1-111111 error_messageExplanation System or infrastructure error has occurred.
Recommended Action If the problem persists, contact the Cisco TAC.
112001
Error Message %PIX|ASA-2-112001: (string:dec) Clear complete.Explanation This message is displayed when a request to clear the module configuration is completed. The source file and line number are identified.
Recommended Action None required.
113001
Error Message %PIX|ASA-3-113001: Unable to open AAA session. Session limit [limit] reached.Explanation The AAA operation on an IPSec tunnel or WebVPN connection could not be performed because of the unavailability of system resources. The limit value indicates the maximum number of concurrent AAA transactions.
Recommended Action Reduce the demand for AAA resources if possible.
113003
Error Message %PIX|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 %PIX|ASA-6-113004: AAA user aaa_type Successful: server = server_IP_address, User = userExplanation This is an indication that a 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 %PIX|ASA-6-113005: AAA user authentication Rejected: reason = string: server = server_IP_address, User = userExplanation This is an indication that either 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 reason field. server_IP_address is the IP address of the relevant AAA server. user is the user name associated with the connection. aaa_operation is either authentication or authorization.
Recommended Action None required.
113006
Error Message %PIX|ASA-6-113006: User user locked out on exceeding number successive failed authentication attemptsExplanation 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 clear aaa local user lockout command. user is the user that is now locked and number is the consecutive failure threshold configured with 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 %PIX|ASA-6-113007: User user unlocked by administratorExplanation A locally configured user that was locked out after exceeding the maximum number of consecutive authentication failures set by the aaa local authentication attempts max-fail command has been unlocked by the indicated administrator.
Recommended Action None required.
113008
Error Message %PIX|ASA-6-113008: AAA transaction status ACCEPT: user = userExplanation 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 %PIX|ASA-6-113009: AAA retrieved default group policy policy for user userExplanation This message may be generated during the authentication or authorization of an IPSec or WebVPN connection. The attributes of the group policy that were specified with the tunnel-group or webvpn commands have been retrieved.
Recommended Action None required.
113010
Error Message %PIX|ASA-6-113010: AAA challenge received for user user from server server_IP_addressExplanation This message may be generated during the authentication of an IPSec connection when the authentication is done with a SecurID server. The user will be prompted to provide further information prior to being authenticated. server _IP_address is the IP address of the relevant AAA server. user is the username associated with the connection.
Recommended Action None required.
113011
Error Message %PIX|ASA-6-113011: AAA retrieved user specific group policy policy for user userExplanation This event may be generated during the authentication or authorization of an IPSec or WebVPN connection. 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 %PIX|ASA-6-113012: AAA user authentication Successful: local database: user = userExplanation The user associated with a IPSec or WebVPN connection has been successfully authenticated to the local user database. user is the username associated with the connection.
Recommended Action None required.
113013
Error Message %PIX|ASA-6-113013: AAA unable to complete the request Error: reason = reason: user = userExplanation The AAA transaction for a user associated with an IPSec or WebVPN connection has failed due to an error or has been rejected due to a policy violation. Details are provided in the reason field. user is the username associated with the connection.
Recommended Action None required.
113014
Error Message %PIX|ASA-6-113014: AAA authentication server not accessible: server = server_IP_address: user = userExplanation 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 %PIX|ASA-6-113015: AAA user authentication Rejected: reason = reason: local database: user = userExplanation A request for authentication to the local user database for a user associated with an IPSec or WebVPN connection has been rejected. Details of why the request was rejected are provided in the reason field. user is the username associated with the connection.
Recommended Action None required.
113016
Error Message %PIX|ASA-6-113016: AAA credentials rejected: reason = reason: server = server_IP_address: user = userExplanation The AAA transaction for a user associated with an IPSec or WebVPN connection has failed due to an error or rejected due to a policy violation. Details are provided in the reason field. server_IP_address is the IP address of the relevant AAA server. user is the username associated with the connection.
Recommended Action None required.
113017
Error Message %PIX|ASA-6-113017: AAA credentials rejected: reason = reason: local database: user = user\Explanation This is an indication that the AAA transaction for a user associated with an IPSec or WebVPN connection has failed due to an error or rejected due to a policy violation. Details are provided in the reason field. This event only appears when the AAA transaction is with the local user database rather than with an external AAA server. user is the username associated with the connection.
Recommended Action None required.
113018
Error Message %PIX|ASA-3-113018: User: user, Unsupported downloaded ACL Entry: ACL_entry, Action: actionExplanation An ACL entry in unsupported format was downloaded from the authentication server.The following list describes the message values:
•
•
•
Recommended Action The ACL entry on the authentication server has to be changed appropriately by the administrator to conform with the supported ACL entry formats.
113019
Error Message %PIX|ASA-auth-4-113019: Group = group, Username = username, IP = peer_address, Session disconnected. Session Type: type, Duration: duration, Bytes xmt: count, Bytes rcv: count, Reason: reasonExplanation This is an informational message that indicates when and why the longest idle user is disconnected.
•
•
•
•
•
•
•
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.
Recommended Action None required.
113020
Error Message %PIX|ASA-3-113020: Kerberos error: Clock skew with server ip_address greater than 300 secondsExplanation This message is displayed when authentication for an IPSec or WebVPN user through a Kerberos server fails because the clocks on the security appliance and the server are more than five minutes (300 seconds) apart. When this occurs, the connection attempt is rejected.
•
Recommended Action Synchronize the clocks on the security appliance 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 attempted access to the management console and was denied.
•
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:
•
•
Otherwise, the user is inappropriately attempting 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 server_name in aaa-server group AAA-Using-DNS as FAILEDExplanation This syslog message indicates that the security appliance 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.
Recommended Action Verify that the AAA server is online and is accessible from the security appliance.
113023
Error Message %ASA-2-113023: AAA Marking protocol server ip-addr in server group tag as ACTIVEExplanation This syslog message indicates that the security appliance has reactivated the AAA server that was previously marked as "failed." The AAA server is now available to service AAA requests.
•
- RADIUS
- TACACS+
- NT
- RSA SecurID
- Kerberos
- LDAP
•
•
Recommended Action None required.
113024
Error Message %ASA-5-113024: Group tg: Authenticating type connection from ip with username, user_name, from client certificateExplanation This message is generated when the pre-fill username feature overrides the username with one derived from the client certificate for use in AAA.
•
•
•
•
Recommended Action None required.
113025
Error Message %ASA-5-113025: Group tg: FAILED to extract username from certificate while authenticating type connection from ipExplanation This message indicates that a username could not be successfully extracted from the certificate for use in AAA.
•
•
•
Recommended Action The administrator should check that the authentication aaa certificate, ssl certificate-authentication, and authorization-dn-attributes keywords are all set correctly.
114001
Error Message %ASA-1-114001: Failed to initialize 4GE SSM I/O card (error error_string).Explanation This message is displayed when the system fails to initialize a 4GE SSM I/O card due to an I2C error or a switch initialization error.
•
•
–
–
–
–
–
–
–
–
–
Recommended Action Perform the following steps:
1.
2.
3.
4.
114002
Error Message %ASA-1-114002: Failed to initialize SFP in 4GE SSM I/O card (error error_string).This message is displayed when the system fails to initialize an SFP connector in an 4GE SSM I/O card due to an I2C error or a switch initialization error.
•
•
–
–
–
–
–
–
–
–
–
Recommended Action Perform the following steps:
1.
2.
3.
4.
114003
Error Message %ASA-1-114003: Failed to run cached commands in 4GE SSM I/O card (error error_string).Explanation This message is displayed when the system fails to run cached commands in an 4GE SSM I/O card due to an I2C error or a switch initialization error.
•
•
–
–
–
–
–
–
–
–
–
Recommended Action Perform the following steps:
1.
2.
3.
4.
114004
Error Message %ASA-6-114004: 4GE SSM I/O Initialization start.Explanation This message is displayed to notify the user that an 4GE SSM I/O Initialization is starting.
•
Recommended Action No action is required.
114005
Error Message %ASA-6-114005: 4GE SSM I/O Initialization end.Explanation This message is displayed to notify user that an 4GE SSM I/O Initialization is finished.
•
Recommended Action No action is required.
114006
Error Message %ASA-3-114006: Failed to get port statistics in 4GE SSM I/O card (error error_string).Explanation This message is displayed when the system fails to get port statistics in an 4GE SSM I/O card due to an I2C error or a switch initialization error.
•
•
–
–
–
–
–
–
–
–
–
Recommended Action Perform the following steps:
1.
2.
3.
4.
114007
Error Message %ASA-3-114007: Failed to get current msr in 4GE SSM I/O card (error error_string).Explanation This message is displayed when the system fails to get the current module status register information in an 4GE SSM I/O card due to an I2C error or a switch initialization error.
•
•
–
–
–
–
–
–
–
–
–
Recommended Action Perform the following steps:
1.
2.
3.
4.
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 This message is displayed when the system fails to enable a port after the link transition to Up state is detected in an 4GE SSM I/O card due to either an I2C serial bus access error or a switch access error.
•
•
–
–
–
–
–
–
–
–
–
Recommended Action Perform the following steps:
1.
2.
3.
4.
114009
Error Message %ASA-3-114009: Failed to set multicast address in 4GE SSM I/O card (error error_string).Explanation This message is displayed when the system fails to set the multicast address in an 4GE SSM I/O card due to an I2C error or a switch initialization error.
•
•
–
–
–
–
–
–
–
–
–
Recommended Action Perform the following steps:
1.
2.
3.
4.
114010
Error Message %ASA-3-114010: Failed to set multicast hardware address in 4GE SSM I/O card (error error_string).Explanation This message is displayed when the system fails to set the multicast hardware address in an 4GE SSM I/O card due to an I2C error or a switch initialization error.
•
•
–
–
–
–
–
–
–
–
–
–
Recommended Action Perform the following steps:
1.
2.
3.
4.
114011
Error Message %ASA-3-114011: Failed to delete multicast address in 4GE SSM I/O card (error error_string).•
•
–
–
–
–
–
–
–
–
–
Explanation This message is displayed when the system fails to delete the multicast address in an 4GE SSM I/O card due to either an I2C error or a switch initialization error.
Recommended Action Perform the following steps:
1.
2.
3.
4.
114012
Error Message %ASA-3-114012: Failed to delete multicast hardware address in 4GE SSM I/O card (error error_string).•
•
–
–
–
–
–
–
–
–
–
Explanation This message is displayed when the system fails to delete the multicast hardware address in an 4GE SSM I/O card due to an I2C error or a switch initialization error.
Recommended Action Perform the following steps:
1.
2.
3.
4.
114013
Error Message %ASA-3-114013: Failed to set mac address table in 4GE SSM I/O card (error error_string).Explanation This message is displayed when the system fails to set the MAC address table in an 4GE SSM I/O card due to an I2C error or a switch initialization error.
•
•
–
–
–
–
–
–
–
–
–
Recommended Action Perform the following steps:
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 This message is displayed when the system fails to set the MAC address in an 4GE SSM I/O card due to an I2C error or a switch initialization error.
Recommended Action Perform the following steps:
1.
2.
3.
4.
114015
Error Message %ASA-3-114015: Failed to set mode in 4GE SSM I/O card (error error_string).•
•
–
–
–
–
–
–
–
–
–
Explanation This message is displayed when the system fails to set individual/promiscuous mode in an 4GE SSM I/O card due to an I2C error or a switch initialization error.
Recommended Action Perform the following steps:
1.
2.
3.
4.
114016
Error Message %ASA-3-114016: Failed to set multicast mode in 4GE SSM I/O card (error error_string).•
•
–
–
–
–
–
–
–
–
–
Explanation This message is displayed when the system fails to set the multicast mode in an 4GE SSM I/O card due to an I2C error or a switch initialization error.
Recommended Action Perform the following steps:
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 This message is displayed when the system fails to get link status in an 4GE SSM I/O card due to either an I2C serial bus access error or a switch access error.
•
•
–
–
–
–
–
–
–
–
–
Recommended Action Perform the following steps:
1.
2.
3.
4.
5.
114018
Error Message %ASA-3-114018: Failed to set port speed in 4GE SSM I/O card (error error_string).Explanation This message is displayed when the system fails to set the port speed in an 4GE SSM I/O card due to an I2C error or a switch initialization error.
•
•
–
–
–
–
–
–
–
–
–
Recommended Action Perform the following steps:
1.
2.
3.
4.
114019
Error Message %ASA-3-114019: Failed to set media type in 4GE SSM I/O card (error error_string).Explanation This message is displayed when the system fails to set the media type in an 4GE SSM I/O card due to an I2C error or a switch initialization error.
•
•
–
–
–
–
–
–
–
–
–
Recommended Action Perform the following steps:
1.
2.
3.
4.
114020
Error Message %ASA-3-114020: Port link speed is unknown in 4GE SSM I/O card.Explanation This message is displayed when the system cannot detect the port link speed in an 4GE SSM I/O card.
Recommended Action Perform the following steps:
1.
2.
3.
4.
114021
Error Message %PIX|ASA-3-114021: Failed to set multicast address table in 4GE SSM I/O card due to error.Explanation This message is displayed when the system fails to set the multicast address table in the 4GE SSM I/O card due to either I2C serial bus access error, or to switch access error.
•
- 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.
114022
Error Message %ASA-3-114022: Failed to pass broadcast traffic in 4GE SSM I/O card due to error_stringExplanation The security appliance failed to pass broadcast traffic in the 4GE SSM I/O card because of a switch access error.
•
Recommended Action Perform the following steps:
1.
2.
3.
Note
120001
Error Message %ASA-5-120001: Smart Call Home Module was started.Explanation This message is generated when the Smart Call Home module is enabled and starts successfully after system bootup and failover in stable state. The module is ready to process Smart Call Home events.
Recommended Action None required.
120002
Error Message %ASA-5-120002: Smart Call Home Module was terminated.Explanation When the Smart Call Home module is disabled, it is terminated and this message is generated. You can only disable the Smart Call Home module through CLI commands or when the configuration is cleared. This message can result from an operation action or a failover configuration synchronization.
Recommended Action None required.
120003
Error Message %ASA-6-120003: Process event group `title'.Explanation This message is generated when the Smart Call Home module gets an event from the queue to process.
•
•
Recommended Action None required.
120004
Error Message %ASA-4-120004: Event group `title' was dropped. Reason `reason'.Explanation This message is generated when a Smart Call Home event is dropped. The event may be dropped because of an internal error, the event queue is full, or the Smart Call Home module is disabled after the message is generated, but before it can be processed.
•
•
•
- NO_MEMORY
- BUFFER_TOO_SMALL
- INTERNAL_ERROR
- INTERRUPTED
- DISABLED
- INVALID_CONTEXT
- COMMAND_PARSE_ERROR
- QUEUE_FULL
- QUEUE_FAILED
Recommended Action If the drop reason is QUEUE_FULL, increase the event queue size and the rate limit configuration to avoid event queue buildup. If the reason is INTERNAL_ERROR, turn on debugging by using the debug sch fail command to obtain more detailed debugging information.
120005
Error Message %ASA-4-120005: Message group to `destination' was dropped. Reason `reason'.Explanation This message is generated when a Smart Call Home module message is dropped. The message may be dropped because of an internal error, a network error, or the Smart Call Home module is disabled after the message is generated, but before it can be delivered.
•
•
•
- NO_MEMORY
- BUFFER_TOO_SMALL
- INTERNAL_ERROR
- INTERRUPTED
- INVALID_STATE
- INVALID_ADDRESS
- INVALID_URL
- INVALID_CONTEXT
- INVALID SLOT
- COMMAND_PARSE_ERROR
- QUEUE_FULL
- QUEUE_FAILED
- EXCEED_LIMIT
- INVALID_TYPE
- MISSING_REQUIRED_ATTRIBUTE
- INSUFFICIENT_REQUIRED_ELEMENT
- DUPLICATED_ELEMENT
- TOO_MANY_ELEMENTS
- INVALID_ELEMENT
- MISSING_REQUIRED_ELEMENT
- DUPLICATED_ATTRIBUTE
- INVALID_ATTRIBUTE
- INVALID_ID
- SOCKET_ERROR
- NO_ROUTE
- CONNECT_FAILED
- WRITE_FAILED
- READ_FAILED
- SMTP_COMMAND_FAILED
- HTTP_FAILED
- DELIVERY_FULL
Recommended Action If the drop reason is DELIVERY_FULL, the message is dropped after three unsuccessful retransmissions, or because the error is local, such as no route to the destination. Search syslog message 120006 for the failure delivery reason, or turn on debugging by using the debug sch fail command to obtain detailed debugging information.
120006
Error Message %ASA-4-120006: Delivering message group to `destination' failed. Reason: `reason'Explanation This error may be transient. This message is generated when an error occurred while the Smart Call Home module was trying to deliver a message. The message is not dropped; it may be queued for retransmission. The message is only dropped when syslog message 120005 is generated.
•
•
•
Recommended Action Check the error reason in the syslog message. If the reason is NO_ROUTE, INVALID_ADDRESS, or INVALID_URL, check the system configuration, DNS, and name settings.
120007
Error Message %ASA-6-120007: Message group to `destination' delivered.Explanation This message is generated when a Smart Call Home module message is successfully delivered.
•
•
Recommended Action None required.
120008
Error Message %ASA-5-120008: SCH client `client' was activated.Explanation When the Smart Call Home module is enabled, an event group is enabled, and that group is subscribed to by at least one active profile, all clients of that group are activated and this message is generated.
•
Recommended Action None required.
120009
Error Message %ASA-5-120009: SCH client `client' was deactivated.Explanation When the Smart Call Home module is disabled, or an event group is no longer subscribed to by any active profile, all clients of that group are deactivated and this message is generated.
•
Recommended Action None required.
120010
Error Message %ASA-3-120010: Notify command command to SCH client `client' failed. Reason `reason'.Explanation This is usually an internal system error. The Smart Call Home module notifies Smart Call Home client of an event. If the client does not interpret the event correctly, does not understand the command, or cannot process the command, an error occurs and this message is generated.
•
•
•
Recommended Action Turn on debugging by using the debug sch fail command to obtain more detailed error message information.
199001
Error Message %PIX|ASA-5-199001: Reload command executed from telnet (remote IP_address).Explanation This message logs the address of the host that is initiating a security appliance reboot with the reload command.
Recommended Action None required.
199002
Error Message %PIX|ASA-6-199002: startup completed. Beginning operation.Explanation The security appliance finished its initial boot and the Flash memory reading sequence, and is ready to begin operating normally.
Note
Recommended Action None required.
199003
Error Message %PIX|ASA-6-199003: Reducing link MTU dec.Explanation The security appliance received a packet from the outside network that uses a larger MTU than the inside network. The security appliance 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.
Recommended Action None required.
199005
Error Message %PIX|ASA-6-199005: Startup beginExplanation The security appliance started.
Recommended Action None required.
199006
Error Message %PIX-5-199006: Orderly reload started at when by whom. Reload reason: reasonExplanation This message is generated when a reload operation is started.
•
•
•
Recommended Action No action is required from the user.
199007
Error Message %PIX-5-199007: Reload scheduled for when by whom at when-command-issued. Reload reason: reasonExplanation This message is generated when a reload operation is scheduled by using the in or at option of the reload command.
•
•
•
•
Recommended Action No action is required from the user.
199008
Error Message %PIX-5-199008: Scheduled reload for when-reload-is-supposed-to-happen cancelled by whom at when.Explanation This message is generated when a scheduled reload operation is cancelled.
•
•
•
Recommended Action No action is required from the user.
199009
Error Message %PIX-7-199009: Reloaded at when by whom. Reload reason: reasonExplanation This message is generated when a reload operation is started.
•
•
•
Recommended Action No action is required from the user.
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 0xca1961a0Explanation The crash recovery mechanism generates this message after a 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.
•
•
•
Recommended Action Contact 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 smashExplanation A stack smash condition has been detected.
•
•
•
Recommended Action Contact Cisco TAC and attach a log file.
Messages 201002 to 219002
This section contains messages from 201002 to 219002.
201002
Error Message %PIX|ASA-3-201002: Too many TCP connections on {static|xlate} global_address! econns nconnsExplanation This is a connection-related message. This message is displayed when the maximum number of TCP connections to the specified global address was exceeded. The econns variable is the maximum number of embryonic connections and the nconns variable is the maximum number of connections permitted for the static or xlate.
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 %PIX|ASA-2-201003: Embryonic limit exceeded nconns/elimit for outside_address/outside_port (global_address) inside_address/inside_port on interface interface_nameExplanation This is a connection-related message regarding traffic to the security appliance. This message is displayed when 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 security appliance is reached, the security appliance attempts to accept them anyway, but puts a time limit on the connections. This situation allows some connections to succeed even if the security appliance is very busy. The nconns variable lists the number of embryonic connections received and the elimit variable lists the maximum number of embryonic connections specified in the static or nat command.
Recommended Action This message indicates a more serious overload than message 201002. It could be caused by a SYN attack, or by a very heavy load of legitimate traffic. Use the show static command to check the limit imposed on embryonic connections to a static address.
201004
Error Message %PIX|ASA-3-201004: Too many UDP connections on {static|xlate} global_address! udp connections limitExplanation This is a connection-related message. This message is displayed when the maximum number of UDP connections to the specified global address was exceeded. The udp conn limit variable is the maximum number of UDP connections permitted for the static 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 %PIX|ASA-3-201005: FTP data connection failed for IP_address IP_addressExplanation The security appliance could not 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 %PIX|ASA-3-201006: RCMD backconnection failed for IP_address/port.Explanation This is a connection-related message. This message is displayed if the security appliance is unable to preallocate connections for inbound standard output for rsh commands due to insufficient memory.
Recommended Action Check the rsh client version; the security appliance only supports the Berkeley rsh. You can also reduce the amount of memory usage, or purchase additional memory.
201008
Error Message %PIX|ASA-3-201008: The security appliance is disallowing new connections.Explanation This message appears when you have enabled TCP syslog messaging and the syslog server cannot be reached, or when using security appliance 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 security appliance 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, the following command will cause it to cease sending packets: [no] auto-update timeout period.
201009
Error Message %PIX|ASA-3-201009: TCP connection limit of number for host IP_address on interface_name exceededExplanation This is a connection-related message. This message is displayed when the maximum number of connections to the specified static address was exceeded. The number variable is the maximum of connections permitted for the host specified by the IP_address variable.
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 %PIX|ASA-3-201010: Embryonic connection limit exceeded econns/limit for dir packet from source_address/source_port to dest_address/dest_port on interface interface_nameExplanation An attempt to establish a TCP connection failed due to an exceeded embryonic connection limit, which was configured with the set connection embryonic-conn-max MPC command for a traffic class.
•
•
•
input: 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.•
•
•
Recommended Action None required.
201011
Error Message %PIX|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 firewall device 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 firewall device until one of the existing connections are torn down thereby bringing the current connection count below the configured maximum.
•
•
•
•
•
•
•
•
Recommended Action None required.
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_nameExplanation 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.
•
•
•
•
•
•
Recommended Action When the limit is reached, any new connection request will be proxied by the security appliance to prevent a SYN flood attack. The security appliance 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_nameExplanation A connection was rejected because the per-client connection limit was exceeded.
•
•
•
•
•
•
Recommended Action When the limit is reached any new connection request will be silently dropped. Normally an application will retry. This will cause 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 %PIX|ASA-3-202001: Out of address translation slots!Explanation This is a connection-related message. This message is displayed if the security appliance 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 could also be caused by insufficient memory; reduce the amount of memory usage, or purchase additional memory usage if possible.
202005
Error Message %PIX|ASA-3-202005: Non-embryonic in embryonic list outside_address/outside_port inside_address/inside_portExplanation This is a connection-related message. This message is displayed when a connection object (xlate) is in the wrong list.
Recommended Action Contact the Cisco TAC.
202011
Error Message %PIX|ASA-3-202011: Connection limit exceeded econns/limit for dir packet from source_address/source_port to dest_address/dest_port on interface interface_nameExplanation This message is displayed when an attempt to create a TCP or UDP connection fails due to an exceeded connection limit which is configured with the set connection conn-max MPC command for a traffic class.
•
•
•
input—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.•
•
•
Recommended Action None required.
208005
Error Message %PIX|ASA-3-208005: (function:line_num) clear command return codeExplanation The security appliance 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 to not inject IP fragments. This configuration change is probably due to NFS. Set the read and write size equal to the interface MTU for NFS.
209003
Error Message %PIX|ASA-4-209003: Fragment database limit of number exceeded: src = source_address, dest = dest_address, proto = protocol, id = numberExplanation Too many IP fragments are currently awaiting reassembly. By default, the maximum number of fragments is 200 (refer to the fragment size command in the Cisco Security Appliance Command Reference to raise the maximum). The security appliance limits the number of IP fragments that can be concurrently reassembled. This restriction prevents memory depletion at the security appliance 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 security appliance, consider using NFS over TCP instead. To prevent fragmentation, see the sysopt connection tcpmss bytes command in the Cisco Security Appliance 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 %PIX|ASA-4-209004: Invalid IP fragment, size = bytes exceeds maximum size = bytes: src = source_address, dest = dest_address, proto = protocol, id = numberExplanation 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's administrator or upstream provider.
209005
Error Message %PIX|ASA-4-209005: Discard IP fragment set with more than number elements: src = Too many elements are in a fragment set.Explanation The security appliance disallows any IP packet that is fragmented into more than 24 fragments. Refer to the fragment command in the Cisco Security Appliance Command Reference for more information.
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.
210001
Error Message %PIX|ASA-3-210001: LU sw_module_name error = numberExplanation A Stateful Failover error occurred.
Recommended Action If this error persists after traffic lessens through the security appliance, report this error to Cisco TAC.
210002
Error Message %PIX|ASA-3-210002: LU allocate block (bytes) failed.Explanation Stateful Failover could not allocate a block of memory to transmit stateful information to the standby security appliance.
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 security appliance software to recover the lost blocks of memory.
210003
Error Message %PIX|ASA-3-210003: Unknown LU Object numberExplanation Stateful Failover received an unsupported Logical Update object and therefore was unable to process it. This could 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. Check for misconfigured clients.
210005
Error Message %PIX|ASA-3-210005: LU allocate connection failedExplanation Stateful Failover cannot allocate a new connection on the standby unit. This may be caused by little or no RAM memory available within the security appliance.
Recommended Action Check the available memory using the show memory command to make sure that the security appliance has free memory in the system. If there is no available memory, add more physical memory to the security appliance.
210006
Error Message %PIX|ASA-3-210006: LU look NAT for IP_address failedExplanation Stateful Failover was unable to locate a NAT group for the IP address on the standby unit. The active and standby security appliance units may be out of synchronization.
Recommended Action Use the write standby command on the active unit to synchronize system memory with the standby unit.
210007
Error Message %PIX|ASA-3-210007: LU allocate xlate failedExplanation Stateful Failover failed to allocate a translation (xlate) slot record.
Recommended Action Check the available memory by using the show memory command to make sure that the security appliance has free memory in the system. If no memory is available, add more memory.
210008
Error Message %PIX|ASA-3-210008: LU no xlate for inside_address/inside_port outside_address/outside_portExplanation Unable to find a translation slot (xlate) record for a Stateful Failover connection; unable to process the connection information.
Recommended Action Enter the write standby command on the active unit to synchronize system memory between the active and standby units.
210010
Error Message %PIX|ASA-3-210010: LU make UDP connection for outside_address:outside_port inside_address:inside_port failedExplanation 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 security appliance has free memory in the system. If no memory is available, add more memory.
210011
Error Message %PIX|ASA-3-210011: Connection limit exceeded cnt/limit for dir packet from sip/sport to dip/dport on interface if_name.Explanation This syslog message indicates that establishing a new connection through the security appliance will result in exceeding at least one of the configured maximum connection limits. The syslog message applies both for 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 security appliance until one of the existing connections are torn down, thereby bringing the current connection count below the configured maximum.
•
•
•
•
•
•
•
•
Recommended Action Because connection limits are configured for a good reason, this syslog message could indicate a possible DOS attack, in which case the source of the traffic could likely be a spoofed IP address. If the source IP address is not totally random, identifying the source and blocking it using an access-list might help. In other cases getting sniffer traces and analyzing the source of the traffic would help in isolating unwanted traffic from legitimate traffic.
210020
Error Message %PIX|ASA-3-210020: LU PAT port port reserve failedExplanation Stateful Failover is unable to allocate a specific PAT address which is in use.
Recommended Action Enter the write standby command on the active unit to synchronize system memory between the active and standby units.
210021
Error Message %PIX|ASA-3-210021: LU create static xlate global_address ifc interface_name failedExplanation Stateful Failover is unable to create a translation slot (xlate).
Recommended Action Enter the write standby command on the active unit to synchronize system memory between the active and standby units.
210022
Error Message %PIX|ASA-6-210022: LU missed number updatesExplanation 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 lost and this error message is sent.
Recommended Action Unless there are LAN interruptions, check the available memory on both security appliance units to ensure that there is enough memory to process the stateful information. Use the show failover command to monitor the quality of stateful information updates.
211001
Error Message %PIX|ASA-3-211001: Memory allocation ErrorExplanation 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.
211003
Error Message %PIX|ASA-3-211003: CPU utilization for number seconds = percentExplanation This message is displayed if the percentage of CPU usage is greater than 100 percent for the number of seconds.
Recommended Action If this message occurs periodically, it can be ignored. If it repeats frequently, contact the Cisco TAC.
212001
Error Message %PIX|ASA-3-212001: Unable to open SNMP channel (UDP port port) on interface interface_number, error code = codeExplanation This is an SNMP message. This message reports that the security appliance is unable to receive SNMP requests destined for the security appliance from SNMP management stations located on this interface. This does not affect the SNMP traffic passing through the security appliance through any interface.
An error code of -1 indicates that the security appliance could not 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).
An error code of -2 indicates that the security appliance could not bind the SNMP transport for the interface.Recommended Action After the security appliance reclaims some of its resources when traffic is lighter, reenter the snmp-server host command for that interface.
212002
Error Message %PIX|ASA-3-212002: Unable to open SNMP trap channel (UDP port port) on interface interface_number, error code = codeExplanation This is an SNMP message. This message reports that the security appliance is unable to send its SNMP traps from the security appliance to SNMP management stations located on this interface. This does not affect the SNMP traffic passing through the security appliance through any interface.
An error code of -1 indicates that the security appliance could not open the SNMP trap transport for the interface.
An error code of -2 indicates that the security appliance could not bind the SNMP trap transport for the interface.
An error code of -3 indicates that the security appliance could not set the trap channel as write-only.Recommended Action After the security appliance reclaims some of its resources when traffic is lighter, reenter the snmp-server host command for that interface.
212003
Error Message %PIX|ASA-3-212003: Unable to receive an SNMP request on interface interface_number, error code = code, will try again.Explanation This is an SNMP message. This message is displayed because of an internal error in receiving an SNMP request destined for the security appliance on the specified interface.
An error code of -1 indicates that the security appliance could not find a supported transport type for the interface.
An error code of -5 indicates that the security appliance received no data from the UDP channel for the interface.
An error code of -7 indicates that the security appliance received an incoming request that exceeded the supported buffer size.
An error code of -14 indicates that the security appliance was unable to determine the source IP address from the UDP channel.
An error code of -22 indicates that the security appliance received an invalid parameter.Recommended Action None required. The security appliance SNMP agent goes back to wait for the next SNMP request.
212004
Error Message %PIX|ASA-3-212004: Unable to send an SNMP response to IP Address IP_address Port port interface interface_number, error code = codeExplanation This is an SNMP message. This message is displayed because of an internal error in sending an SNMP response from the security appliance to the specified host on the specified interface.
An error code of -1 indicates that the security appliance could not find a supported transport type for the interface.
An error code of -2 indicates that the security appliance sent an invalid parameter.
An error code of -3 indicates that the security appliance was unable to set the destination IP address in the UDP channel.
An error code of -4 indicates that the security appliance sent a PDU length that exceeded the supported UDP segment size.
An error code of -5 indicates that the security appliance was unable to allocate a system block to construct the PDU.Recommended Action None required.
212005
Error Message %PIX|ASA-3-212005: incoming SNMP request (number bytes) on interface interface_name exceeds data buffer size, discarding this SNMP request.Explanation This is an SNMP message. This message reports that the length of the incoming SNMP, request which is destined for the security appliance exceeds the size of the internal data buffer (512 bytes) used for storing the request during internal processing. The security appliance is unable to process this request. This situation does not affect the SNMP traffic passing through the security appliance using any interface.
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 %PIX|ASA-3-212006: Dropping SNMP request from source_address/source_port to interface_name:dest_address/dest_port because: reason.Explanation This is an SNMP message. This message is displayed if the device is unable to process a SNMP request to the device for the following reasons.
•
•
Recommended Action Make sure that the SNMP daemon is entering by issuing the snmp-server enable command. Only SNMPv1 and SNMPv2c packets are handled by the device.
213001
Error Message %PIX|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 %PIX|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 %PIX|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 %PIX|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.
Recommended Action This error occurs when the IP local address pool was depleted. Consider allocating a larger pool with the ip local pool command.
213005
Error Message %PIX|ASA-3-213005%: Dynamic-Access-Policy action (DAP) action abortedExplanation The Dynamic Access Policy created for this connection has determined that the session should be terminated.
Recommended Action The Dynamic Access Policy 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.
213006
Error Message %PIX|ASA-3-21306%: 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. There was an error reading the configured dynamic access policy record.
Recommended Action A configuration change might have resulted in deleting a dynamic access policy record. Use ASDM to re-create the dynamic access policy record.
214001
Error Message %PIX|ASA-2-214001: Terminating manager session from IP_address on interface interface_name. Reason: incoming encrypted data (number bytes) longer than number bytesExplanation An incoming encrypted data packet destined for the security appliance management port indicates a packet length exceeding the specified upper limit. This may be a hostile event. The security appliance immediately terminates this management connection.
Recommended Action Ensure that the management connection was initiated by Cisco Secure Policy Manager.
215001
Error Message %PIX|ASA-2-215001:Bad route_compress() call, sdb= numberExplanation An internal software error occurred.
Recommended Action Contact the Cisco TAC.
217001
Error Message %PIX|ASA-2-217001: No memory for string in stringExplanation An operation failed due to low memory.
Recommended Action If sufficient memory exists, then copy the error message, the configuration, and any details about the events leading up the error to the Cisco TAC.
216001
Error Message %ASA-n-216001: internal error in: function: messageExplanation This message reports a variety of internal errors that should not appear during normal operation. The severity level varies depending on the cause of the message.
•
•
•
Recommended Action Search the Bug Toolkit for the specific text message and also try to use the Output Interpreter to resolve the problem. If the problem persists, contact the Cisco TAC.
216002
Error Message PIX|ASA-3-216002: Unexpected event (major: major_id, minor: minor_id) received by task_string in function at line: line_numExplanation This message is displayed when a task registers for event notification and the task cannot handle the specific event. Events that can be watched include those associated with queues, booleans, timer services, and so forth. 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 and 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 it is processed, but this should not occur under normal conditions. If This message is displayed, it does not necessarily mean the box is unusable, but something unusual has occurred and needs to be investigated.
•
•
•
•
•
Recommended Action If the problem persists, contact the Cisco TAC.
216003
Error Message %PIX|ASA-3-216003: Unrecognized timer timer_ptr, timer_id received by task_string in function at line: line_numExplanation This message is displayed when an unexpected timer event woke up the task and 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 woken up by an unrecognized timer event.
An expired timer, if left unprocessed, wakes up the task continuously to make sure it is processed, and this is undesirable. This should not occur under normal conditions. If This message is displayed, it does not necessarily mean the box is unusable, but something unusual has occurred and needs to be investigated.
•
•
•
•
•
Recommended Action If the problem persists, contact the Cisco TAC.
216004
Error Message %PIX|ASA-4-216004:prevented: error in function at file(line) - stack traceExplanation This syslog message reports an internal logic error, and should not occur during normal operation.
•
–
–
–
–
–
–
–
–
•
•
•
Recommended Action If the problem persists, contact the Cisco TAC.
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 whereby the port could no longer transmit packets. This condition was detected, and the switch was reset to auto-recover from this condition. This message applies only to the ASA 5505 device.
•
Recommended Action A duplex-mismatch exists between the specified port and the device that is connected to it. Correct the duplex-mismatch by either setting both devices to "auto," or hard-coding the duplex on both sides to be the same.
218001
Error Message %PIX|ASA-2-218001: Failed Identification Test in slot# [fail#/res].Explanation The module in slot# of the security appliance could not 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 cards, or other modules, Cisco may deny support under your warranty or under a Cisco support program such as SmartNet.
Recommended Action If this message reoccurs, copy it exactly as it appears on the console or in the syslog. Research and attempt 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 %PIX|ASA-2-218002: Module (slot#) is a registered proto-type for Cisco Lab use only, and not certified for live network operation.Explanation 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 syslog. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Toolkit. If the problem persists, contact the Cisco TAC.
218003
Error Message %PIX|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 This syslog message is generated when obsolete hardware is detected or when the show module command is entered for the module. This syslog message is generated every minute once it starts.
Recommended Action If this message reoccurs, copy it exactly as it appears on the console or in the syslog. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Toolkit. If the problem persists, contact the Cisco TAC.
218004
Error Message %PIX|ASA-2-218004: Failed Identification Test in slot# [fail#/res]Explanation There was a problem while identifying hardware in the specified location.
Recommended Action If this message reoccurs, copy it exactly as it appears on the console or in the syslog. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of 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_stringExplanation The I2C serial bus API has failed. This might be because of a hardware or software problem.
•
–
–
–
–
–
–
–
–
–
–
–
–
•
•
•
•
•
–
–
–
–
–
–
–
–
–
Recommended Action Perform the following steps:
1.
2.
3.
4.
Messages 302003 to 339001
This section contains messages from 302003 to 339001.
302003
Error Message %PIX|ASA-6-302003: Built H245 connection for foreign_address outside_address/outside_port local_address inside_address/inside_portExplanation This is a connection-related message. This message is displayed when an H.245 connection is started from the outside_address to the inside_address. This message only occurs if the security appliance detects the use of an Intel Internet Phone. The foreign port (outside port) only displays on connections from outside the security appliance. The local port value (inside port) only appears on connections started on an internal interface.
Recommended Action None required.
302004
Error Message %PIX|ASA-6-302004: Pre-allocate H323 UDP backconnection for foreign_address outside_address/outside_port to local_address inside_address/inside_portExplanation This is a connection-related message. This message is displayed when an H.323 UDP back-connection is preallocated to the foreign address (outside_address) from the local address (inside_address). This message only occurs if the security appliance detects the use of an Intel Internet Phone. The foreign port (outside_port) only displays on connections from outside the security appliance. The local port value (inside_port) only appears on connections started on an internal interface.
Recommended Action None required.
302009
Error Message %PIX|ASA-6-302009: Rebuilt TCP connection number for foreign_address outside_address/outside_port global_address global_address/global_port local_address inside_address/inside_portExplanation This is a connection-related message. This message appears after a TCP connection is rebuilt after a failover. A sync packet is not sent to the other security appliance. The outside_address IP address is the foreign host, the global_address IP address is a global address on the lower security level interface, and the inside_address IP address is the local IP address "behind" the security appliance on the higher security level interface.
Recommended Action None required.
302010
Error Message %PIX|ASA-6-302010: connections in use, connections most usedExplanation This is a connection-related message. This message appears after a TCP connection restarts. connections is the number of connections.
Recommended Action None required.
302012
Error Message %PIX|ASA-6-302012: Pre-allocate H225 Call Signalling Connection for faddr IP_address/port to laddr IP_addressExplanation An H.225 secondary channel has been preallocated.
Recommended Action None required.
302013
Error Message %PIX|ASA-6-302013: Built {inbound|outbound} TCP connection_id for interface:real-address/real-port (mapped-address/mapped-port) to interface:real-address/real-port (mapped-address/mapped-port) [(user)]Explanation A TCP connection slot between two hosts was created.
•
•
•
•
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.
Recommended Action None required.
302014
Error Message %PIX|ASA-6-302014: Teardown TCP connection id for interface:real-address/real-port to interface:real-address/real-port duration hh:mm:ss bytes bytes [reason] [(user)]Explanation A TCP connection between two hosts was deleted. The following list describes the message values:
•
•
•
•
•
The reason variable presents the action that causes the connection to terminate. Set the reason variable to one of the TCP termination reasons listed in Table 1-3.
Recommended Action None required.
302015
Error Message %PIX|ASA-6-302015: Built {inbound|outbound} UDP connection number for interface_name:real_address/real_port (mapped_address/mapped_port) to interface_name:real_address/real_port (mapped_address/mapped_port) [(user)]Explanation A UDP connection slot between two hosts is created. The following list describes the message values:
•
•
•
•
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.
Recommended Action None required.
302016
Error Message %PIX|ASA-6-302016: Teardown UDP connection number for interface:real-address/real-port to interface:real-address/real-port duration hh:mm:ss bytes bytes [(user)]Explanation A UDP connection slot between two hosts was deleted. The following list describes the message values:
•
•
•
•
•
•
•
•
•
Recommended Action None required.
302017
Error Message %PIX|ASA-6-302017: Built {inbound|outbound}
GRE connection id from
interface:real_address (translated_address) to
interface:real_address/real_cid
(translated_address/translated_cid)[(user)Explanation A GRE connection slot between two hosts is 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:•
•
•
•
•
•
•
•
•
Recommended Action This is an informational message.
302018
Error Message %PIX|ASA-6-302018: Teardown GRE connection id from
interface:real_address (translated_address) to
interface:real_address/real_cid
(translated_address/translated_cid)
duration hh:mm:ss bytes bytes [(user)]Explanation A GRE connection slot between two hosts is deleted. The interface, real_address, real_port tuples identify the actual sockets. Duration accounts the lifetime of the connection. The following list describes the message values:
•
•
•
•
•
•
•
•
Recommended Action This is an informational message.
302019
Error Message %PIX|ASA-3-302019: H.323 library_name ASN Library failed to initialize, error code numberExplanation The specified ASN library that the security appliance uses for decoding the H.323 messages failed to initialize; the security appliance cannot decode or inspect the arriving H.323 packet. The security appliance allows the H.323 packet to pass through without any modification. When the next H.323 message arrives, the security appliance attempts 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).
302020
Error Message %PIX|ASA-6-302020: Built {in | out}bound ICMP connection for faddr {faddr | icmp_seq_num} gaddr {gaddr | cmp_type} laddr laddrExplanation An ICMP session was established in the fast-path when stateful ICMP is enabled using the inspect icmp command.
Recommended Action None required.
302021
Error Message %PIX|ASA-6-302021: Teardown ICMP connection for faddr {faddr | icmp_seq_num} gaddr {gaddr | cmp_type} laddr laddrExplanation An ICMP session was removed in the fast-path when stateful ICMP is enabled using the inspect icmp command.
Recommended Action None required.
302033
Error Message %PIX|ASA-6-302033:Pre-allocated H323 GUP Connection for faddr interface:foreign address/foreign-port to laddr interface:local-address/local-portExplanation This is a connection-related message. This message is displayed when a GUP connection is started from the foreign_address to the local_address. The foreign port (outside port) only displays on connections from outside the security device. The local port value (inside port) only appears on connections started on an internal interface.
•
•
•
•
•
Recommended Action None required
302034
Error Message %PIX|ASA-4-302034: Unable to pre-allocate H323 GUP Connection for faddr interface: foreign address/foreign-port to laddr interface:local-address/local-portExplanation 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. If it repeats frequently, contact 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 translates and connections. This error message may also be caused by insufficient memory; try reducing the amount of memory usage, or purchasing additional memory.
302302
Error Message %PIX|ASA-3-302302: ACL = deny; no sa createdExplanation IPSec proxy mismatches. 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.
303002
Error Message PIX-6-303002: FTP connection from src_ifc:src_ip/src_port todst_ifc:dst_ip/dst_port, user username action file filename
Explanation This event is generated whenever a client uploads or downloads a file from the FTP server.
•
•
•
•
•
•
•
•
•
Recommended Action None required.
303003
Error Message %PIX|ASA-5-303003: FTP cmd_string command denied - failed strict inspection, terminating connection from %s:%A/%d to %s:%A/%d.Explanation This message is generated when using strict FTP inspection on FTP traffic. It is displayed if an FTP request message contains a command that is not recognized by the device.
Recommended Action None required.
303004
Error Message %PIX|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_interfaceExplanation This message is generated when using strict FTP inspection on FTP traffic. It is displayed if an FTP request message contains a command that is not recognized by the device.
Recommended Action None required.
303005
Error Message %PIX|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/dportExplanation This message is generated when FTP inspection matches any of the following configured values: filename, file type, request command, server, or user name. Then the action specified by the action_string in this syslog message occurs.
•
•
•
•
•
•
•
•
•
Recommended Action None required.
304001
Error Message %PIX|ASA-5-304001: user@source_address Accessed {JAVA URL|URL} dest_address: urlExplanation This is an FTP/URL message. This message is displayed when the specified host attempts to access the specified URL.
Recommended Action None required.
304002
Error Message %PIX|ASA-5-304002: Access denied URL chars SRC IP_address DEST IP_address: charsExplanation This is an FTP/URL message. This message is displayed if access from the source address to the specified URL or FTP site is denied.
Recommended Action None required.
304003
Error Message %PIX|ASA-3-304003: URL Server IP_address timed out URL urlExplanation A URL server timed out.
Recommended Action None required.
304004
Error Message %PIX|ASA-6-304004: URL Server IP_address request failed URL urlExplanation This is an FTP/URL message. This message is displayed if a Websense server request fails.
Recommended Action None required.
304005
Error Message %PIX|ASA-7-304005: URL Server IP_address request pending URL urlExplanation This is an FTP/URL message. This message is displayed when a Websense server request is pending.
Recommended Action None required.
304006
Error Message %PIX|ASA-3-304006: URL Server IP_address not respondingExplanation This is an FTP/URL message. The Websense server is unavailable for access, and the security appliance 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.
304007
Error Message %PIX|ASA-2-304007: URL Server IP_address not responding, ENTERING ALLOW mode.Explanation This is an FTP/URL message. This message is displayed when you use the allow option of the filter command, and the Websense servers are not responding. The security appliance allows all web requests to continue without filtering while the servers are not available.
Recommended Action None required.
304008
Error Message %PIX|ASA-2-304008: LEAVING ALLOW mode, URL Server is up.Explanation This is an FTP/URL message. This message is displayed when you use the allow option of the filter command, and the security appliance receives a response message from a Websense server that previously was not responding. With this response message, the security appliance exits the allow mode, which enables the URL filtering feature again.
Recommended Action None required.
304009
Error Message %PIX|ASA-7-304009: Ran out of buffer blocks specified by url-block commandExplanation 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 %PIX|ASA-3-305005: No translation group found for protocol src interface_name: source_address/source_port dst interface_name: dest_address/dest_portExplanation 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.
305006
Error Message %PIX|ASA-3-305006: {outbound static|identity|portmap|regular) translation creation failed for protocol src interface_name:source_address/source_port dst interface_name:dest_address/dest_portExplanation A protocol (UDP, TCP, or ICMP) failed to create a translation through the security appliance. This message appears as a fix to caveat CSCdr00663 that requested that security appliance not allow packets that are destined for network or broadcast addresses. The security appliance provides this checking for addresses that are explicitly identified with static command statements. With the change, for inbound traffic, the security appliance denies translations for a destined IP address identified as a network or broadcast address.
The security appliance 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 xlate. So, when the other ICMP messages types are dropped, syslog message 305006 (on the security appliance) is generated.
The security appliance utilizes the global IP and mask from configured static command statements to differ 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 security appliance 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
Global address 10.2.2.128 is responded to as a network address and 10.2.2.255 is responded to as the broadcast address. Without an existing translation, security appliance denies inbound packets destined for 10.2.2.128 or 10.2.2.255, and logs this syslog message.
When the suspected IP is a host IP, configure a separated static command statement with a host mask in front of the subnet static (first match rule for static command statements). The following static causes the security appliance 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.128The translation may be created by traffic started with the inside host with the questioned IP address. Because the security appliance views a network or broadcast IP address as a host IP address with overlapped subnet static configuration, the network address translation for both static command statements must be the same.
Recommended Action None required.
305007
Error Message %PIX|ASA-6-305007: addrpool_free(): Orphan IP IP_address on interface interface_numberExplanation The security appliance has attempted to translate an address that it cannot find in any of its global pools. The security appliance assumes that the address was deleted and drops the request.
Recommended Action None required.
305008
Error Message %PIX|ASA-3-305008: Free unallocated global IP address.Explanation The security appliance 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 security appliance is running a Stateful Failover setup and some of the internal states are momentarily out of synchronization between the active unit and the standby unit. This condition is not catastrophic, and the sync recovers automatically.
Recommended Action If the problem persists, contact the Cisco TAC.
305009
Error Message %PIX|ASA-6-305009: Built {dynamic|static} translation from interface_name [(acl-name)]:real_address to interface_name:mapped_addressExplanation 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 %PIX|ASA-6-305010: Teardown {dynamic|static} translation from interface_name:real_address to interface_name:mapped_address duration timeExplanation The address translation slot was deleted.
Recommended Action None required.
305011
Error Message %PIX|ASA-6-305011: Built {dynamic|static} {TCP|UDP|ICMP} translation from interface_name:real_address/real_port to interface_name:mapped_address/mapped_portExplanation 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.
Recommended Action None required.
305012
Error Message %PIX|ASA-6-305012: Teardown {dynamic|static} {TCP|UDP|ICMP} translation from interface_name [(acl-name)]:real_address/{real_port|real_ICMP_ID}to interface_name:mapped_address/{mapped_port|mapped_ICMP_ID} duration timeExplanation The address translation slot was deleted.
Recommended Action None required.
305013
Error Message %PIX|ASA-5-305013: Asymmetric NAT rules matched for forward and reverse flows; Connection protocol src interface_name:source_address/source_port dest interface_name:dest_address/dest_port 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 applicable inspect command if the application embeds the IP address.
308001
Error Message %PIX|ASA-6-308001: console enable password incorrect for number tries (from IP_address)Explanation This is a security appliance management message. This message is displayed 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.
308002
Error Message %PIX|ASA-4-308002: static global_address inside_address netmask netmask overlapped with global_address inside_addressExplanation 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 %PIX|ASA-6-311001: LU loading standby startExplanation Stateful Failover update information was sent to the standby security appliance when the standby security appliance is first to be online.
Recommended Action None required.
311002
Error Message %PIX|ASA-6-311002: LU loading standby endExplanation Stateful Failover update information stopped sending to the standby security appliance.
Recommended Action None required.
311003
Error Message %PIX|ASA-6-311003: LU recv thread upExplanation An update acknowledgment was received from the standby security appliance.
Recommended Action None required.
311004
Error Message %PIX|ASA-6-311004: LU xmit thread upExplanation This message appears when a Stateful Failover update is transmitted to the standby security appliance.
Recommended Action None required.
312001
Error Message %PIX|ASA-6-312001: RIP hdr failed from IP_address: cmd=string, version=number domain=string on interface interface_nameExplanation The security appliance 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.
Recommended Action This message is informational, but it may also indicate that another RIP device is not configured correctly to communicate with the security appliance.
313001
Error Message %PIX|ASA-3-313001: Denied ICMP type=number, code=code from IP_address on interface interface_nameExplanation 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 security appliance discards the ICMP packet and generates this syslog message. The icmp command enables or disables pinging to an interface. With pinging disabled, the security appliance 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 %PIX|ASA-4-313004:Denied ICMP type=icmp_type, from source_address oninterface interface_name to dest_address:no matching sessionExplanation ICMP packets were dropped by the security appliance 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 security appliance or ICMP error messages not related to any TCP, UDP, or ICMP session already established in the security appliance.
Recommended Action None required.
313005
Error Message %PIX|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 dst dest_interface_name:dest_address (type icmp_type, code icmp_code) embedded_frame_info = prot src source_address/source_port dst dest_address/dest_portExplanation ICMP error packets were dropped by the security appliance because the ICMP error messages are not related to any session already established in the security appliance.
Recommended Action If the cause is an attack, you can deny the host by using ACLs.
313008
Error Message %PIX|ASA-3-313008: Denied ICMPv6 type=number, code=code from IP_address on interface interface_nameExplanation 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 security appliance discards the ICMPv6 packet and generates this syslog message.
The icmp command enables or disables pinging to an interface. When pinging is disabled, the security appliance is undetectable on the network. This feature is also referred to as "configurable proxy pinging."
Recommended Action Contact the administrator of the peer device.
314001
Error Message %PIX|ASA-6-314001: Pre-allocated RTSP UDP backconnection for src_intf:src_IP to dst_intf:dst_IP/dst_port.Explanation Open UDP media channel for RTSP client receiving data from server
•
•
•
•
•
Recommended Action None required.
314002
Error Message %PIX|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 security appliance cannot open a new pinhole for the media channel
•
•
•
•
•
•
Recommended Action If the reason is "unknown," check the free memory available (show memory), or number of connections used (show conn), because the security appliance is low on memory.
314003
Error Message %PIX|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.
•
•
•
–
–
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 %PIX|ASA-6-314004: RTSP client src_intf:src_IP accessed RTSP URL RTSP URLExplanation RTSP client attempt to access an RTSP server.
•
•
•
Recommended Action None required.
314005
Error Message %PIX|ASA-6-314005: RTSP client src_intf:src_IP denied access to URL RTSP_URL.Explanation RTSP client attempt to access prohibited site, as configured on the security appliance.
•
•
•
Recommended Action None required.
314006
Error Message %PIX|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.
•
•
•
•
Recommended Action Investigate why the specific RTSP request message from the client exceeded the rate limit.
315004
Error Message %PIX|ASA-3-315004: Fail to establish SSH session because RSA host key retrieval failed.Explanation The security appliance could not find the security appliance RSA host key, which is required for establishing an SSH session. The security appliance host key may be absent because it was not generated or because the license for this security appliance does not allow DES or 3DES.
Recommended Action From the security appliance 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.
315011
Error Message %PIX|ASA-6-315011: SSH session from IP_address on interface interface_name for user user disconnected by SSH server, reason: reasonExplanation This message appears after an SSH session completes. If a user enters quit or exit, the terminated normally message displays. If the session disconnected for another reason, the text describes the reason. Table 1-4 lists the possible reasons why a session disconnected.
Recommended Action None required.
316001
Error Message %PIX|ASA-3-316001: Denied new tunnel to IP_address. VPN peer limit (platform_vpn_peer_limit) exceededExplanation If more VPN tunnels (ISAKMP/IPSec) are concurrently attempting to be established than 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_addrExplanation This message is generated when the security appliance is unable to create a VPN handle, because the VPN handle already exists.
•
•
•
•
•
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-errorshow asp table classify crypto detailshow asp table vpn-context317001
Error Message %PIX|ASA-3-317001: No memory available for limit_slowExplanation 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 %PIX|ASA-3-317002: Bad path index of number for IP_address, number maxExplanation A software error occurred.
Recommended Action If the problem persists, contact the Cisco TAC.
317003
Error Message %PIX|ASA-3-317003: IP routing table creation failure - reasonExplanation An internal software error occurred, which prevented the creation of new IP routing table.
Recommended Action Copy the message exactly as it appears, and report it to Cisco TAC.
317004
Error Message %PIX|ASA-3-317004: IP routing table limit warningExplanation 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 %PIX|ASA-3-317005: IP routing table limit exceeded - reason, IP_address netmaskExplanation 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 %PIX|ASA-3-317006: Pdb index error pdb, pdb_index, pdb_typeExplanation The index into the pdb is out of range.
•
•
•
Recommended Action If the problem persists, copy the error message exactly as it appears on the console or in the syslog, contact the Cisco TAC, and provide the representative with the gathered information.
318001
Error Message %PIX|ASA-3-318001: Internal error: reasonExplanation An internal software error occurred. This message occurs at 5-second intervals.
Recommended Action If the problem persists, contact the Cisco TAC.
318002
Error Message %PIX|ASA-3-318002: Flagged as being an ABR without a backbone areaExplanation The router was flagged as an area border router (ABR) without a backbone area configured in the router. This message occurs at 5-second intervals.
Recommended Action Restart the OSPF process.
318003
Error Message %PIX|ASA-3-318003: Reached unknown state in neighbor state machineExplanation An internal software error occurred. This message occurs at 5 second intervals.
Recommended Action None required.
318004
Error Message %PIX|ASA-3-318004: area string lsid IP_address mask netmask adv IP_address type numberExplanation OSPF had a problem locating the link state advertisement (LSA), which might lead to a memory leak.
Recommended Action If the problem persists, contact the Cisco TAC.
318005
Error Message %PIX|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 numberExplanation 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 %PIX|ASA-3-318006: if interface_name if_state numberExplanation An internal error occurred.
Recommended Action If the problem persists, contact the Cisco TAC.
318007
Error Message %PIX|ASA-3-318007: OSPF is enabled on interface_name during idb initializationExplanation An internal error occurred.
Recommended Action If the problem persists, contact the Cisco TAC.
318008
Error Message %PIX|ASA-3-318008: OSPF process number is changing router-id. Reconfigure virtual link neighbors with our new router-idExplanation 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 virtual link configuration on all of the virtual link neighbors to reflect the new router ID.
318009
Error Message %PIX|ASA-3-318009: OSPF: Attempted reference of stale data encountered in function, line: line_numExplanation This message is displayed when OSPF is running and tries 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.
•
•
Recommended Action If the problem persists, contact the Cisco TAC.
319001
Error Message %PIX|ASA-3-319001: Acknowledge for arp update for IP address dest_address not received (number).Explanation The ARP process in the security appliance lost internal synchronization because the system was overloaded.
Recommended Action No immediate action is required. The failure is only temporary. Check the average load of the system and make sure it is not used beyond its capabilities.
319002
Error Message %PIX|ASA-3-319002: Acknowledge for route update for IP address dest_address not received (number).Explanation The routing module in the security appliance lost internal synchronization because the system was overloaded.
Recommended Action No immediate action required. The failure is only temporary. Check the average load of the system and make sure it is not used beyond its capabilities.
319003
Error Message %PIX|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 with respect to 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 %PIX|ASA-3-319004: Route update for IP address dest_address failed (number).Explanation The routing module in the security appliance lost internal synchronization because the system was overloaded.
Recommended Action No immediate action required. The failure is only temporary. Check the average load of the system and make sure it is not used beyond its capabilities.
320001
Error Message %PIX|ASA-3-320001: The subject name of the peer cert is not allowed for connectionExplanation When the security appliance is an easy VPN remote device or server, the peer certificate contains a subject name that does not match the ca verifycertdn command.
Recommended Action This message might indicate a "man in the middle" attack, where a device spoofs the peer IP address and attempts to intercept a VPN connection from the security appliance.
321001
Error Message %PIX|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.
321002
Error Message %PIX|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 %PIX|ASA-6-321003: Resource var1 log level of var2 reached.Explanation A configured resource usage or rate log level for the indicated resource was reached.
Recommended Action None required.
321004
Error Message %PIX|ASA-6-321004: Resource var1 rate log level of var2 reachedExplanation A configured resource usage or rate log level for the indicated resource was reached.
Recommended Action None required.
322001
Error Message %PIX|ASA-3-322001: Deny MAC address MAC_address, possible spoof attempt on interface interfaceExplanation The security appliance 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 your configuration. This could be caused by either be a MAC-spoofing attack or a misconfiguration.
Recommended Action Check the configuration and take appropriate action by either finding the offending host or correcting the configuration.
322002
Error Message %PIX|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 security appliance. 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 %PIX|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 security appliance. 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 %PIX|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_portExplanation The security appliance dropped a packet due to no management IP address configured in the transparent mode.
•
•
•
•
•
•
•
Recommended Action Configure the device with management IP address and mask values.
323001
Error Message %ASA-3-323001: Module in slot slotnum experienced a control channel communications failure.Explanation System is unable to communicate via control channel with module installed in slot slot.
•
Recommended Action If the problem persists, contact the Cisco TAC.
323002
Error Message %ASA-3-323002: Module in slot slotnum is not able to shut down, shut down request not answered.Explanation Module installed in slot slot didn't respond to a shut down request.
•
Recommended Action If the problem persists, contact the Cisco TAC.
323003
Error Message %ASA-3-323003: Module in slot slotnum is not able to reload, reload request not answered.Explanation Module installed in slot slot didn't respond to a reload request.
•
Recommended Action If the problem persists, contact the Cisco TAC.
323004
Error Message %ASA-3-323004: Module in slot slotnum failed to write software vnewver (currently vver), reason. Hw-module reset is required before further use.Explanation The module in the specified slot number failed to accept a software version, and will be transitioned to an UNRESPONSIVE state. The module is not usable until the software is updated.
•
•
•
•
–
–
Recommended Action The module must be reset by using the hw-module module slotnum reset before further upgrade attempts will be made. If the module software can not be updated it will not be usable. Ensure the module is completely seated in the chassis. If the problem persists, contact the Cisco TAC.
323005
Error Message %ASA-3-323005: Module in slot slotnum can not be powered on completelyExplanation This message indicates that the module can not be powered up completely. The module will remain in the UNRESPONSIVE state until this condition is corrected. A likely cause of this is a module that is not fully seated in the slot.
•
Recommended Action Verify that the module is fully seated in the slot and check if any status LEDs on the module are on. It may take a minute after fully reseating the module for the system to recognize that it is powered up. If this message appears after verifying that the module is seated and after resetting the module using the hw-module module slotnum reset command, contact the Cisco TAC.
323006
Error Message %ASA-1-323006: Type Module in slot slot experienced a data channel communication failure, data channel is DOWN.Explanation This message indicates that a data channel communication failure occurred and the system was unable to forward traffic to the SSM. This failure triggers a failover when the failure occurs on the active appliance 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 SSM. This message is generated whenever a communication problem over the security appliance dataplane occurs between the system module and the SSM, which can be caused when the SSM stops, resets, or is removed.
•
•
Recommended Action If this message is not the result of the SSM reloading or resetting and the corresponding message 1-505010 is not seen after the SSM returns to an UP state, the module may need to be reset using the hw-module module 1 reset command.
323007
Error Message %ASA-3-323007: Module in slot slot experienced a firmware failure and the recovery is in progress.Explanation If an security appliance with a 4GE-SSM card installed experiences a short power surge and reboots, the 4GE-SSM may come up in an unresponsive state. The security appliance detects this condition and automatically recovers.
•
Recommended Action None required.
324000
Error Message %PIX|ASA-3-324000: Drop GTPv version message msg_type from source_interface:source_address/source_port to dest_interface:dest_address/dest_port Reason: reasonExplanation The packet being processed did not meet the filtering requirements as described in the reason variable and is being dropped.
Recommended Action None required.
324001
Error Message %PIX|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: reasonExplanation There was an error processing the packet. The following are possible reasons:
•
•
•
•
•
•
•
•
•
•
•
•
•
Recommended Action If this message is seen periodically, it can be ignored. If it is seen frequently, then the endpoint maybe sending out bad packets as part of an attack.
324002
Error Message %PIX|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_valueExplanation 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 could not 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, contact the Cisco TAC.
324003
Error Message %PIX|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_portExplanation 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 maybe sending out bad packets as part of an attack.
324004
Error Message %PIX|ASA-3-324004: GTP packet with version%d from source_interface:source_address/source_port to dest_interface:dest_address/dest_port is not supportedExplanation 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.
Recommended Action None required.
324005
Error Message %PIX|ASA-3-324005: Unable to create tunnel from source_interface:source_address/source_port to dest_interface:dest_address/dest_portExplanation An error occurred while trying to create the tunnel for the TPDUs.
Recommended Action If this message occurs periodically, it can be ignored. If it repeats frequently, contact the Cisco TAC.
324006
Error Message %PIX|ASA-3-324006:GSN IP_address tunnel limit tunnel_limit exceeded, PDP Context TID tid failedExplanation The GSN 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 %PIX|ASA-3-324007: Unable to create GTP connection for response from source_address/0 to dest_address/dest_portExplanation An error occurred while trying to create the tunnel for the TPDUs for a different SGSN or GGSN.
Recommended Action Check debugs and messages to see why the connection was not created properly. If the problem persists, contact the Cisco TAC.
324300
Error Message %PIX|ASA-3-324300: Radius Accounting Request from from_addr has an incorrect request authenticatorExplanation 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.
•
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 it is not spoofed.
324301
Error Message %PIX|ASA-3-324301: Radius Accounting Request has a bad header length hdr_len, packet length pkt_lenExplanation The accounting request message has a header length that is not the same as the actual packet length, so packet processing stops.
•
•
Recommended Action Make sure the packet is not spoofed. If the packet is legitimate, then capture the packet and make sure the header length is incorrect as indicated by the syslog message. If the header length is correct, of the problem persists, contact the Cisco TAC.
325001
Error Message %PIX|ASA-3-325001: Router ipv6_address on interface has conflicting ND (Neighbor Discovery) settingsExplanation Another router on the link sent router advertisements with conflicting parameters. ipv6_address is the IPv6 address of the other router. interface is the interface 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 command show ipv6 interface.
325002
Error Message %PIX|ASA-4-325002: Duplicate address ipv6_address/MAC_address on interfaceExplanation Another system is using your IPv6 address. ipv6_address is the IPv6 address of the other router. MAC_address is the MAC address of the other system if known, otherwise "unknown." interface is the interface name of the link with the other system.
Recommended Action Change the IPv6 address of one of the two systems.
325003
Error Message %PIX-3-325003: EUI-64 source address check failed. Dropped packet from interface_in:source_address/source_port to dest_address/dest_port with source MAC address MAC_address.Explanation The ipv6 enforce-eui64 command is configured for the input interface of this packet, but the source address of the packet is not a correct EUI-64 address derived from the source MAC address.
Recommended Action None required.
326001
Error Message %PIX|ASA-3-326001: Unexpected error in the timer library: error_messageExplanation A managed timer event was received without a context or a proper type or no handler exists. This message will also be displayed if the number of events queued exceed a system limit and will be attempted to be processed at a later time.
Recommended Action If the problem persists, contact the Cisco TAC.
326002
Error Message %PIX|ASA-3-326002: Error in error_message: error_messageExplanation The IGMP process failed to shut down upon request. Events that are performed in preparation for this shut down may be out of synchronization.
Recommended Action If the problem persists, contact the Cisco TAC.
326004
Error Message %PIX|ASA-3-326004: An internal error occurred while processing a packet queueExplanation The IGMP packet queue received a signal without a packet.
Recommended Action If the problem persists, contact the Cisco TAC.
326005
Error Message %PIX|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.
Recommended Action If the problem persists, contact the Cisco TAC.
326006
Error Message %PIX|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, which can cause insufficient memory.
Recommended Action If the problem persists, contact the Cisco TAC.
326007
Error Message %PIX|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 likely result is insufficient memory.
Recommended Action If the problem persists, contact the Cisco TAC.
326008
Error Message %PIX|ASA-3-326008: MRIB registration failedExplanation The MFIB failed to register with the MRIB.
Recommended Action If the problem persists, contact the Cisco TAC.
326009
Error Message %PIX|ASA-3-326009: MRIB connection-open failedExplanation The MFIB failed to open a connection to the MRIB.
Recommended Action If the problem persists, contact the Cisco TAC.
326010
Error Message %PIX|ASA-3-326010: MRIB unbind failedExplanation The MFIB failed to unbind from the MRIB.
Recommended Action If the problem persists, contact the Cisco TAC.
326011
Error Message %PIX|ASA-3-326011: MRIB table deletion failedExplanation 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 %PIX|ASA-3-326012: Initialization of string functionality failedExplanation The initialization of a functionality failed. This component might still operate without the functionality.
Recommended Action If the problem persists, contact the Cisco TAC.
326013
Error Message %PIX|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 %PIX|ASA-3-326014: Initialization failed: error_message error_messageExplanation The MRIB failed to initialize.
Recommended Action If the problem persists, contact the Cisco TAC.
326015
Error Message %PIX|ASA-3-326015: Communication error: error_message error_messageExplanation The MRIB received a malformed update.
Recommended Action If the problem persists, contact the Cisco TAC.
326016
Error Message %PIX|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 could not be found, or because of some internal error.
Recommended Action If the problem persists, contact the Cisco TAC.
326017
Error Message %PIX|ASA-3-326017: Interface Manager error - string in string: stringExplanation An error occurred while creating a PIM tunnel interface.
Recommended Action If the problem persists, contact the Cisco TAC.
326019
Error Message %PIX|ASA-3-326019: string in string: stringExplanation An error occurred while creating a PIM RP tunnel interface.
Recommended Action If the problem persists, contact the Cisco TAC.
326020
Error Message %PIX|ASA-3-326020: List error in string: stringExplanation An error occurred while processing a PIM interface list.
Recommended Action If the problem persists, contact the Cisco TAC.
326021
Error Message %PIX|ASA-3-326021: Error in string: stringExplanation An error occurred while setting the SRC of a PIM tunnel interface.
Recommended Action If the problem persists, contact the Cisco TAC.
326022
Error Message %PIX|ASA-3-326022: Error in string: stringExplanation The PIM process failed to shut down upon request. Events that are performed in preparation for this shut down may be out of sync.
Recommended Action If the problem persists, contact the Cisco TAC.
326023
Error Message %PIX|ASA-3-326023: string - IP_address: stringExplanation An error occurred while processing a PIM group range.
Recommended Action If the problem persists, contact the Cisco TAC.
326024
Error Message %PIX|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 %PIX|ASA-3-326025: stringExplanation An internal error occurred while trying to send a message. Events scheduled to happen on receipt of the message such as deletion of the PIM tunnel IDB may not take place.
Recommended Action If the problem persists, contact the Cisco TAC.
326026
Error Message %PIX|ASA-3-326026: Server unexpected error: error_messsageExplanation The MRIB failed to register a client.
Recommended Action If the problem persists, contact the Cisco TAC.
326027
Error Message %PIX|ASA-3-326027: Corrupted update: error_messsageExplanation The MRIB received a corrupt update.
Recommended Action If the problem persists, contact the Cisco TAC.
326028
Error Message %PIX|ASA-3-326028: Asynchronous error: error_messsageExplanation An unhandled asynchronous error occurred in the MRIB API.
Recommended Action If the problem persists, contact the Cisco TAC.
327001
Error Message %PIX|ASA-3-327001: IP SLA Monitor: Cannot create a new processExplanation IP SLA Monitor was unable to start a new process.
Recommended Action Check the system memory. If memory is low, then this is the likely cause. Try to reenter the commands when memory is available. If the problem persists, contact the Cisco TAC.
327002
Error Message %PIX|ASA-3-327002: IP SLA Monitor: Failed to initialize, IP SLA Monitor functionality will not workExplanation IP SLA monitor failed to initialize. This condition is caused by either the timer wheel timer functionality failed to initialize or a process could not be created. A likely cause of this condition is that sufficient memory is not available to complete the task.
Recommended Action Check the system memory. If memory is low, then this is the likely cause. Try to reenter the commands when memory is available. If the problem persists, contact the Cisco TAC.
327003
Error Message %PIX|ASA-3-327003: IP SLA Monitor: Generic Timer wheel timer functionality failed to initializeExplanation IP SLA monitor could not initialize the timer wheel.
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 the problem persists, contact the Cisco TAC
328001
Error Message %PIX|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 w/ check registry is invoked. This message indicates that an attempt to set a new callback failed because a callback function has already been set.
•
Recommended Action If the problem persists, contact the Cisco TAC.
329001
Error Message %PIX|ASA-3-329001: The string0 subblock named string1 was not removedExplanation A software error has occurred. This message displays when IDB subblocks cannot be removed.
•
•
Recommended Action If the problem persists, contact the Cisco TAC.
331001
Error Message ASA|PIX-3-331001: Dynamic DNS Update for 'fqdn_name' <=> ip_address failedExplanation This message is generated when the dynamic DNS subsystem fails to update the resource records on the DNS server. This failure might occur if the security appliance is unable to contact the DNS server or DNS service is not running on the destination system.
•
•
Recommended Action Make sure a DNS server is configured and reachable by the security appliance. If the problem persists, contact the Cisco TAC.
331002
Error Message ASA|PIX-5-331002: Dynamic DNS type RR for ('fqdn_name' -> ip_address | ip_address -> 'fqdn_name') successfully updated in DNS server dns_server_ipExplanation This message is generated when a Dynamic DNS update succeeds in the DNS server.
•
•
•
•
332001
Error Message %ASA|PIX-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 is configured.
332002
Error Message %ASA|PIX-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 there is enough memory available for all processes.
332003
Error Message %ASA|PIX-5-332003: Web Cache IP_address/service_ID acquiredExplanation A service from the web cache of the security appliance was acquired.
•
•
Recommended Action None required.
332004
Error Message %ASA|PIX-1-332004: Web Cache IP_address/service_ID lostExplanation A service from the web cache of the security appliance was lost.
•
•
Recommended Action Verify operation of specified web cache.
333001
Error Message %PIX|ASA-6-333001: EAP association initiated - context:EAP-contextExplanation An EAP association has been initiated with a remote host.
•
Recommended Action None required.
333002
Error Message %PIX|ASA-5-333002: Timeout waiting for EAP response - context:EAP-contextExplanation A timeout occurred while waiting for an EAP response.
•
Recommended Action None required.
333003
Error Message %PIX|ASA-6-333003: EAP association terminated - context:EAP-contextExplanation The EAP association has been terminated with the remote host.
•
Recommended Action None required.
333004
Error Message %PIX|ASA-7-333004: EAP-SQ response invalid - context:EAP-contextExplanation The EAP-Status Query response failed basic packet validation.
•
Recommended Action If the problem persists, contact the Cisco TAC.
333005
Error Message %PIX|ASA-7-333005: EAP-SQ response contains invalid TLV(s) - context:EAP-contextExplanation The EAP-Status Query response has one or more invalid TLVs.
•
Recommended Action If the problem persists, contact the Cisco TAC.
333006
Error Message %PIX|ASA-7-333006: EAP-SQ response with missing TLV(s) - context:EAP-contextExplanation The EAP-Status Query response is missing one or more mandatory TLVs.
•
Recommended Action If the problem persists, contact the Cisco TAC.
333007
Error Message %PIX|ASA-7-333007: EAP-SQ response TLV has invalid length - context:EAP-contextExplanation The EAP-Status Query response contains a TLV with an invalid length.
•
Recommended Action If the problem persists, contact the Cisco TAC.
333008
Error Message %PIX|ASA-7-333008: EAP-SQ response has invalid nonce TLV - context:EAP-contextExplanation The EAP-Status Query response contains an invalid nonce TLV.
•
Recommended Action If the problem persists, contact the Cisco TAC.
333009
Error Message %PIX|ASA-6-333009: EAP-SQ response MAC TLV is invalid - context:EAP-contextExplanation The EAP-Status Query response contains a MAC which does not match the calculated MAC.
•
Recommended Action If the problem persists, contact the Cisco TAC.
333010
Error Message %PIX|ASA-5-333010: EAP-SQ response Validation Flags TLV indicates PV request - context:EAP-contextExplanation The EAP-Status Query response contains a Validation Flags TLV which indicates that the peer requested a full posture validation.
Recommended Action None required.
334001
Error Message %PIX|ASA-6-334001: EAPoUDP association initiated - <host-address>Explanation An EAPoUDP association has been initiated with a remote host.
•
Recommended Action None required.
334002
Error Message %PIX|ASA-5-334002: EAPoUDP association successfully established - host-addressExplanation An EAPoUDP association has been successfully established with the host.
•
Recommended Action None required.
334003
Error Message %PIX|ASA-5-334003: EAPoUDP association failed to establish - host-addressExplanation An EAPoUDP association has failed to establish with the host.
•
Recommended Action Verify configuration of Cisco Secure Access Control Server.
334004
Error Message %PIX|ASA-6-334004: Authentication request for NAC Clientless host - host-addressExplanation An authentication request was made for a NAC Clientless host.
•
Recommended Action None required.
334005
Error Message %PIX|ASA-5-334005: Host put into NAC Hold state - host-addressExplanation The NAC session for the host was put into the Hold state.
•
Recommended Action None required.
334006
Error Message %PIX|ASA-5-334006: EAPoUDP failed to get a response from host - host-addressExplanation An EAPoUDP response was not received from the host.
•
Recommended Action None required.
334007
Error Message %PIX|ASA-6-334007: EAPoUDP association terminated - host-addressExplanation An EAPoUDP association has terminated with the host.
•
Recommended Action None required.
334008
Error Message %PIX|ASA-6-334008: NAC EAP association initiated - host-address, EAP context:EAP-contextExplanation EAPoUDP has initiated EAP with the host.
•
•
Recommended Action None required.
334009
Error Message %PIX|ASA-6-334009: Audit request for NAC Clientless host - Assigned_IP.Explanation This is an informational message indicating that an audit request is being sent for the specified assigned IP address.
•
Recommended Action None required.
335001
Error Message %PIX|ASA-6-335001: NAC session initialized - host-addressExplanation A NAC session has started for a remote host.
•
Recommended Action None required.
335002
Error Message %PIX|ASA-5-335002: Host is on the NAC Exception List - host-address, OS:oper-sysExplanation The client is on the NAC Exception List is is therefore not subject toPosture Validation.
•
•
Recommended Action None required.
335003
Error Message %PIX|ASA-5-335003: NAC Default ACL applied, ACL:ACL-name - host-addressExplanation The NAC Default ACL has been applied for the client.
•
•
Recommended Action None required.
335004
Error Message %PIX|ASA-6-335004: NAC is disabled for host - host-addressExplanation NAC is disabled for the remote host.
•
Recommended Action None required.
335004
Error Message %PIX|ASA-6-335004: NAC is disabled for host - host-addressExplanation NAC is disabled for the remote host.
•
Recommended Action None required.
335005
Error Message %PIX|ASA-4-335005: NAC Downloaded ACL parse failure - host-addressExplanation Parsing of downloaded ACL failed.
•
Recommended Action Verify configuration of Cisco Secure Access Control Server.
335006
Error Message %PIX|ASA-6-335006: NAC Applying ACL:ACL-name - host-addressExplanation Name of the ACL being applied as a result of NAC Posture Validation.
•
•
Recommended Action None required.
335007
Error Message %PIX|ASA-7-335007: NAC Default ACL not configured - host-addressExplanation NAC Default ACL has not been configured.
•
Recommended Action None required.
335008
Error Message %PIX|ASA-5-335008: NAC IPSec terminate from dynamic ACL:ACL-name - host-addressExplanation A dynamic ACL obtained as a result of PV warrants IPSec termination.
•
•
Recommended Action None required.
335009
Error Message %PIX|ASA-6-335009: NAC 'Revalidate' request by administrative action - host-addressExplanation NAC "Revalidate" was requested by the administrator.
•
Recommended Action None required.
335010
Error Message %PIX|ASA-6-335010: NAC 'Revalidate All' request by administrative action - num sessionsExplanation NAC "Revalidate All" was requested by the administrator.
•
Recommended Action None required.
335011
Error Message %PIX|ASA-6-335011: NAC 'Revalidate Group' request by administrative action for group-name group - num sessionsExplanation NAC "Revalidate Group" was requested by the administrator.
•
•
Recommended Action None required.
335012
Error Message %PIX|ASA-6-335012: NAC 'Initialize' request by administrative action - host-addressExplanation NAC "Initialize" was requested by the administrator.
•
Recommended Action None required.
335013
Error Message %PIX|ASA-6-335013: NAC 'Initialize All' request by administrative action - num sessionsExplanation NAC "Initialize All" was requested by the administrator.
•
Recommended Action None required.
335014
Error Message %PIX|ASA-6-335014: NAC 'Initialize Group' request by administrative action for group-name group - num sessionsExplanation NAC 'Initialize Group' was requested by the administrator.
•
•
Recommended Action None required.
336001
Error Message %ASA-3-336001 Route desination_network stuck-in-active state in EIGRP-ddb_name as_num. Cleaning upExplanation The stuck in active (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 3 minutes). When this happens, EIGRP clears the neighbors that did not send a reply and logs an error message for the route that went active.
•
•
•
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 Handle not allocated. The EIGRP router is unable to find the handle for the next hop.
•
Recommended Action If the problem persists, contact the Cisco TAC.
336003
Error Message %ASA-3-336003: No buffers available for bytes byte packetExplanation No Buffer. The Diffusing Update Algorithm (DUAL) software was unable to allocate a packet buffer. The system may be out of memory.
•
Recommended Action Check to see if the system is out of memory by doing a `show mem' or `show tech'. If the problem persists, contact the Cisco TAC.
336004
Error Message %ASA-3-336004: Negative refcount in pakdesc pakdesc.Explanation Negative refcount. The reference count packet count that went negative.
•
Recommended Action If the problem persists, contact the Cisco TAC.
336005
Error Message %ASA-3-336005: Flow control error, error, on interface_name.Explanation This log is issued when the interface is flow-blocked for multicast. Qelm is the 'queue element', in this case, the last multicast packet on the queue for this particular interface.
•
•
Recommended Action If the problem persists, contact the Cisco TAC.
336006
Error Message %ASA-3-336006: num peers exist on IIDB interface_name.Explanation Peers still exist on a particular interface during or after clean up of the IDB of the EIGRP.
•
•
Recommended Action If the problem persists, contact the Cisco TAC.
336007
Error Message %ASA-3-336007: Anchor count negativeExplanation Negative Anchor Count. 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_strExplanation Lingering DRDB. An interface is being deleted and some lingering DRDB exists.
•
•
•
•
Recommended Action If the problem persists, contact the Cisco TAC.
336009
Error Message %ASA-3-336009 ddb_name as_id: Internal ErrorExplanation An internal error occurred.
•
•
Recommended Action If the problem persists, contact the Cisco TAC.
336010
Error Message %ASA-5-336010 EIGRP-<ddb_name> tableid as_id: Neighbor address (%interface) is event_msg: msgExplanation Neighbor Change. A neighbor went up or down.
•
•
•
•
•
•
•
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 eventExplanation A dual event occurred. The events can be one of the following:
•
•
Recommended Action If the problem persists, contact the Cisco TAC.
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_portExplanation This message occurs when the crypto hardware was unable to do SRTP encryption.
•
•
•
•
•
Recommended Action If this message persists, call Cisco TAC to debug the crypto hardware to see 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_portExplanation This message occurs when the crypto hardware was unable to do SRTP decryption.
•
•
•
•
•
Recommended Action If this message persists, call Cisco TAC to debug the crypto hardware to see 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_portExplanation This message occurs when the authentication tag generation fails in the crypto hardware.
•
•
•
•
•
Recommended Action If this message persists, call Cisco TAC to debug the crypto hardware to see 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_portExplanation This message occurs when 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-3-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_portExplanation This message occurs when the security appliance gets an SRTP/RTP packet destined to the media termination IP address and port but the corresponding media session to process this packet is not found.
•
•
•
•
•
•
Recommended Action If this syslog occurs at the end of the call, it is considered normal because the signaling messages could have released the media session but the end-point is continuing to send a few SRTP/RTP packets. If this syslog occurs for a odd numbered media termination port, the endpoint is sending RTCP and that has to be disabled from the CUCM. If this syslog happens continuously for a call, debug the signaling message transaction either using phone proxy debug commands or capture commands to see 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/sportExplanation This message occurs when the crypto hardware was unable to perform encryption and create a signature for a file.
•
•
•
•
•
•
•
Recommended Action If this message persists, check associated syslog 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/sportExplanation This message occurs when the CUCM returns the "File Not Found" error when a phone requests its configuration file.
•
•
•
•
•
•
•
Recommended Action Check to make sure that this phone has been configured on the CUCM.
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 This syslog is generated when we could not find a port to allocate for media when creating a new media session. This could be because of the fact that the user has not provided a big enough range of ports for phone proxy use, declared in the media-termination address command, or the fact that all the available ports are already used up.
•
•
•
•
•
•
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 and if their 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 This syslog is generated when the user tries to register the same secure phone with a different IP. Since we already made an entry for the MAC address with the old IP, the user cannot have multiple entries with the same MAC address with different IP's.
•
•
•
Recommended Action Check the output of the show phone-proxy secure-phones command. Run the clear command to clear the entry which is causing the issue. Next, register the phone with the new IP.
338001
Error Message %ASA-4-338001: Dynamic filter monitored black listed 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_nameExplanation This syslog message is generated when traffic from a blacklisted domain in the dynamic filter database appears. 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, spyware, and so on).
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 black listed 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_nameExplanation This syslog message is generated when traffic to a blacklisted domain name in the dynamic filter database appears. 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, spyware, and so on).
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.
338003
Error Message %ASA-4-338003: Dynamic filter monitored black listed 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_nameExplanation This syslog message is generated when traffic from a blacklisted IP address in the dynamic filter database appears. 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, spyware, and so on).
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.
338004
Error Message %ASA-4-338004: Dynamic filter monitored black listed 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_nameExplanation This syslog message is generated when traffic to a blacklisted IP address in the dynamic filter database appears. 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, spyware, and so on).
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.
338005
Error Message %ASA-4-338005: Dynamic filter dropped black listed 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_nameExplanation This message is generated when traffic from a black-listed domain name in the dynamic filter database is 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, spyware, and so on).
Recommended Action None required.
338006
Error Message %ASA-4-338006: Dynamic filter dropped black listed 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_nameExplanation This message is generated when traffic from a black-listed domain name in the dynamic filter database is 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, spyware, and so on).
Recommended Action None required.
338007
Error Message %ASA-4-338007: Dynamic filter dropped black listed 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_nameExplanation This message is generated when traffic from a black-listed IP address in the dynamic filter database is 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, spyware, and so on).
Recommended Action None required.
338008
Error Message %ASA-4-338008: Dynamic filter dropped black listed 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_nameExplanation This message is generated when traffic from a black-listed IP address in the dynamic filter database is 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, spyware, and so on).
Recommended Action None required.
338201
Error Message %ASA-4-338201: Dynamic filter monitored grey listed 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_nameExplanation This syslog message is generated when traffic to a greylisted domain in the dynamic filter database appears. 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, spyware, and so on).
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 and the dynamic-filter ambiguous-is-black command to automatically drop such traffic.
338202
Error Message %ASA-4-338202: Dynamic filter monitored grey listed 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_nameExplanation This syslog message is generated when traffic from a greylisted domain name in the dynamic filter database appears. 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, spyware, and so on).
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 and the dynamic-filter ambiguous-is-black command to automatically drop such traffic.
338203
Error Message %ASA-4-338203: Dynamic filter dropped grey listed 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_nameExplanation This syslog message is generated when traffic from a greylisted domain name in the dynamic filter database is denied; however, the malicious IP address is 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, spyware, and so on).
Recommended Action Access to a malicious site was dropped. If you do not want to automatically drop grey-listed 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 grey listed 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_nameExplanation This syslog message is generated when traffic from a greylisted domain name in the dynamic filter database is denied; however, the malicious IP address is 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, spyware, and so on).
Recommended Action Access to a malicious site was dropped. If you do not want to automatically drop grey-listed traffic whose IP address matches both blacklisted domain names and unknown domain names, disable the dynamic-filter ambiguous-is-black command.
339001
Error Message %ASA-3-339001: UC-IME-SIG: Ticket not found in SIP %s from %s:%A/%d to %s:%A/%d, packet droppedExplanation For UC-IME SIP signaling, all dialog-forming SIP messages received from the outside must contain the UC-IME 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.
•
•
•
•
•
•
•
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, %sExplanation 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.
•
•
•
•
•
•
•
•
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 droppedExplanation 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, non-dialog-creating SIP messages are not permitted to create a SIP session in the security appliance and are dropped.
•
•
•
•
•
•
•
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, %sExplanation 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.
•
•
•
•
•
•
•
•
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 droppedExplanation 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.
•
•
•
•
•
•
Recommended Action None required.
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 %sExplanation For the UC-IME Mapping Service to work correctly, a correct configuration of global NAT must be in place. If this misconfiguration is detected, a syslog error 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 syslog error message will be generated to notify the administrator about this occurrence.
•
•
•
•
•
•
•
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.
Recommended Action None required.
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(x 100): %d, Max ITE count in 8 secs: %d, Max BLS (ms): %d, Max span PDV (usec): %d, Min span PDV (usec): %d, Move 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): %dExplanation 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 of a call.
•
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
•
UNKNOWN, G722, PCMU, PCMA, iLBC, or iSAC
Recommended Action None required.
339009
Error Message %ASA-6-339009: UC-IME: Ticket Password changed. Please update the same on UC-IME server.Explanation The security appliance 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 syslog also serves as a reminder to the administrator that if the UC-IME password is changed on the security appliance, 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 security appliance.
Messages 400000 to 466002
This section contains messages from 400000 to 466002.
4000nn
Error Message %PIX|ASA-4-4000nn: IPS:number string from IP_address to IP_address on interface interface_nameExplanation Messages 400000 through 400051 are Cisco Intrusion Prevention Service signature messages.
Recommended Action See the Cisco Intrusion Prevention Service User Guide on Cisco.com.
All signature messages are not supported by the security appliance in this release. IPS syslog messages all start with 4-4000nn and have the following format:
Options:
•
The signature number. See the Cisco Intrusion Detection System User Guide on Cisco.com.
•
The signature message, which is approximately the same as the NetRanger signature message.
•
The local to remote address to which the signature applies.
•
The name of the interface on which the signature originated.
For example:
%PIX|ASA-4-400013 IPS:2003 ICMP redirect from 10.4.1.2 to 10.2.1.1 on interface dmz%PIX|ASA-4-400032 IPS:4051 UDP Snork attack from 10.1.1.1 to 192.168.1.1 on interface outsideTable 1-5 lists the supported signature messages.
401001
Error Message %PIX|ASA-4-401001: Shuns clearedExplanation The clear shun command was entered to remove existing shuns from memory.
Recommended Action None required. This message is displayed to allow an institution to keep a record of shunning activity.
401002
Error Message %PIX|ASA-4-401002: Shun added: IP_address IP_address port portExplanation 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.
Recommended Action None required. This message is displayed to allow an institution to keep a record of shunning activity.
401003
Error Message %PIX|ASA-4-401003: Shun deleted: IP_addressExplanation A single shunned host was removed from the shun database.
Recommended Action None required. This message is displayed to allow an institution to keep a record of shunning activity.
401004
Error Message %PIX|ASA-4-401004: Shunned packet: IP_address ==> IP_address on interface interface_nameExplanation 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.
Recommended Action None required. This message provides a record of the activity of shunned hosts. This message and syslog message %PIX|ASA-4-401005 can be used to evaluate further risk assessment concerning this host.
401005
Error Message %PIX|ASA-4-401005: Shun add failed: unable to allocate resources for IP_address IP_address port portExplanation The security appliance is out of memory; a shun could not be applied.
Recommended Action The Cisco Intrusion Detection System should continue to attempt to apply this rule. Attempt to reclaim memory and reapply a shun manually, or wait for the Cisco Intrusion Detection System to do this.
402114
Error Message %PIX|ASA-4-402114: IPSEC: Received an protocol packet (SPI=spi, sequence number= seq_num) from remote_IP to local_IP with an invalid SPI.•
•
•
•
•
•
Explanation This message is displayed when an IPSec packet is received that specifies an SPI that does not exist in the SA database. This may be a temporary condition due to 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 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 %PIX|ASA-4-402115: IPSEC: Received a packet from remote_IP to local_IP containing act_prot data instead of exp_prot data.Explanation This message is displayed when an IPSec packet is received that is missing the expected ESP header. The peer is sending packets that do not match the negotiated security policy. This may indicate an attack. This message is rate limited to no more than one message every five seconds.
•
•
•
•
Recommended Action Contact the peer administrator.
402116
Error Message %PIX|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 doesn't 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 This message is displayed when a decapsulated IPSec packet does not match the negotiated identity. The peer is sending other traffic through this security association. It may be due to 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.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Recommended Action Contact the peer administrator and compare policy settings.
402117
Error Message %PIX|ASA-4-402117: IPSEC: Received a non-IPSec (protocol) packet from remote_IP to local_IP.Explanation This message is displayed when 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 Telnet without IPSec encryption to the outside interface on port 23, this message appears, but not on telnet or traffic to the outside interface on ports other than 23. This error can also indicate an attack. This syslog message is not generated except under these conditions (for example, it is not generated for traffic to the firewall interfaces themselves). See messages 710001, 710002, and 710003 for messages that track TCP and UDP requests. This message is rate limited to no more than one message every five seconds.
•
•
•
Recommended Action Contact the peer administrator to compare policy settings.
402118
Error Message %PIX|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 This message is displayed when a decapsulatd IPSec packet contains 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.
•
•
•
•
•
•
•
•
Recommended Action Contact the administrator of the remote peer to compare policy settings.
402119
Error Message %PIX|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 This message is displayed when an IPSec packet is received with an invalid sequence number. The peer is sending packets containing sequence numbers that may have been previously used. This syslog 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 peer administrator.
402120
Error Message %PIX|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 This message is displayed when an IPSec packet is received and fails authentication. The packet is dropped. The packet may have been corrupted in transit or the peer may be sending invalid IPSec packets. This may indicate an attack if many of these packets are 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 are received.
402121
Error Message %PIX|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 This message is displayed when an IPSec packet to be decapsulated was received and subsequently dropped by the IPSec subsystem. This could indicate a problem with the device configuration or with the device itself.
•
•
•
•
•
•
•
Recommended Action If the problem persists, contact the Cisco TAC.
402122
Error Message %PIX|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 could indicate a problem with the device configuration or with the device itself.
•
•
•
Recommended Action If the problem persists, contact the Cisco TAC.
402123
Error Message %PIX|ASA-4-402123: CRYPTO: The accel_type hardware accelerator encountered an error (code= error_string) while executing crypto command command.Explanation This message is displayed when an error is detected while running a crypto command with a hardware accelerator. This could 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.
•
•
•
Recommended Action If the problem persists, contact the Cisco TAC
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 This syslog message appears when the crypto hardware chip has reported a fatal error, indicating the chip is inoperable. The information from this syslog message captures the information and to allow further analysis of this 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 debug information. Various parameters related to the crypto hardware are contained in this syslog message; these include:
•
•
•
•
•
•
•
•
•
•
Recommended Action Forward the syslog message information to 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 either the IPSEC 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 is detected is written to a crypto archive directory on flash, to provide further debug information.
•
•
Desc—Descriptor address
CtrlStat—Control/status value
ResultP—Success pointer
ResultVal—Success value
Cmd—Crypto command
CmdSize—Command size
Param—Command parameters
Dlen—Data length
DataP—Data pointer
CtxtP—VPN context pointer
SWReset—Number of crypto chip resets since boot
Recommended Action Forward the syslog message information to Cisco 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 There was a functional problem detected with the hardware crypto chip (see syslog messages 4402124/4402125). To further debug the crypto problem a crypto archive file is generated, containing the current crypto hardware environment (hardware registers, Crypto Desc Entries, and so on). At boot time, a crypto_archive directory is automatically created on the flash file system (if not in prior existence). A maximum of two crypto archive files are allowed to exist in this directory.
•
Recommended Action Forward the crypto archive file(s) to Cisco 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 There was a functional problem detected with the HW Crypto chip (see syslog messages 4402124 and 4402125). This syslog message indicates a crypto archive file was not written as the maximum number of crypto archive files already existed.
•
•
Recommended Action Forward previously generated crypto archive files to Cisco. Remove the previously generated archive file(s) so more can be written (if deemed necessary).
402128
Error Message %ASA-5-402128: CRYPTO: An attempt to allocate a large memory block failed, size: size, limit: limitExplanation An SSL connection is attempting to use more memory than allowed. The request has been denied.
•
•
Recommended Action If this message persists, an SSL denial of service (DoS) 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: addressExplanation An internal software error has occurred.
•
Recommended Action Contact the Cisco TAC for assistance.
402130
Error Message %PIX|ASA-3-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.
•
•
•
•
Recommended Action There have been customers using the ATT VPN client that have experienced this issue due to the ATT VPN client sometimes padding Ipsec packets incorrectly. While this syslog is informational only and doesn't indicate a problem with the ASA, customers using the ATT VPN
client may wish to upgrade their VPN client software.403101
Error Message %PIX|ASA-4-403101: PPTP session state not established, but received an XGRE packet, tunnel_id=number, session_id=numberExplanation The security appliance received a PPTP XGRE packet without a corresponding control connection session.
Recommended Action If the problem persists, contact the Cisco TAC
403102
Error Message %PIX|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 %PIX|ASA-4-403103: PPP virtual interface max connections reached.Explanation The module cannot accept additional PPTP connections.
Recommended Action None required. Connections are allocated as soon as they are available.
403104
Error Message %PIX|ASA-4-403104: PPP virtual interface interface_name requires mschap for MPPE.Explanation The Microsoft Point-to-Point Encryption (MPPE) is configured but MS-CHAP authentication is not.
Recommended Action Add MS-CHAP authentication with the vpdn group group_name ppp authentication command.
403106
Error Message %PIX|ASA-4-403106: PPP virtual interface interface_name requires RADIUS for MPPE.Explanation The MPPE is configured but RADIUS authentication is not.
Recommended Action Add RADIUS authentication with the vpdn group group_name ppp authentication command.
403107
Error Message %PIX|ASA-4-403107: PPP virtual interface interface_name missing aaa server group infoExplanation 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 %PIX|ASA-4-403108: PPP virtual interface interface_name missing client ip address optionExplanation 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 %PIX|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. This may be a hostile event.
Recommended Action Contact the administrator of the peer to check the PPTP configuration settings.
403110
Error Message %PIX|ASA-4-403110: PPP virtual interface interface_name, user: user missing MPPE key from aaa server.Explanation The AAA server is not returning the MPPE key attributes required to set up the MPPE encryption policy.
Recommended Action Check the AAA server configuration and if the AAA server cannot return MPPE key attributes, use local authentication instead with the vpdn group group_name client authentication local command.
403500
Error Message %PIX|ASA-6-403500: PPPoE - Service name 'any' not received in PADO. Intf:interface_name AC:ac_name.Explanation The security appliance 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.
Recommended Action None required.
403501
Error Message %PIX|ASA-3-403501: PPPoE - Bad host-unique in PADO - packet dropped. Intf:interface_name AC:ac_nameExplanation The security appliance sent an identifier called the host-unique value to the access controller. The access controller responded with a different host-unique value. The security appliance is unable to identify the corresponding connection request for this response. The packet is dropped and connection negotiations are 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.
403502
Error Message %PIX|ASA-3-403502: PPPoE - Bad host-unique in PADS - dropping packet. Intf:interface_name AC:ac_nameExplanation The security appliance sent an identifier called the host-unique value to the access controller. The access controller responded with a different host-unique value. The security appliance is 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 %PIX|ASA-3-403503: PPPoE:PPP link down:reasonExplanation The PPP link has gone down. There are many reasons why this could 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 could be down. Ensure that your authentication protocol matches the access concentrator. Ensure that your name and password are correct. Check with your ISP or network support person.
403504
Error Message %PIX|ASA-3-403504: PPPoE:No 'vpdn group group_name' for PPPoE is createdExplanation 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 security appliance for PPPoE dialout. The my-username and my-password commands are used to authenticate the access concentrator, using PAP if necessary.
For example:
vpdn group my-pppoe request dialout pppoevpdn group my-pppoe ppp authentication papvpdn group my-pppoe localname my-usernamevpdn username my-username password my-passwordip address outside pppoe setrouteRecommended Action Configure a VPDN group for PPPoE.
403505
Error Message %PIX|ASA-4-403505: PPPoE:PPP - Unable to set default route to IP_address at interface_nameExplanation 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 %PIX|ASA-4-403506: PPPoE:failed to assign PPP IP_address netmask netmask at interface_nameExplanation This message is followed by - 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 %PIX|ASA-3-403507:PPPoE:PPPoE client on interface interface failed to locate PPPoE vpdn group group_nameExplanation 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 is not located during system startup, this syslog message is generated.
•
•
Recommended Action Perform the following steps:
1.
2.
Note
404101
Error Message %PIX|ASA-4-404101: ISAKMP: Failed to allocate address for client from pool stringExplanation ISAKMP failed to allocate an IP address for the VPN client from the pool that you specified with the ip local pool command.
Recommended Action Use the ip local pool command to specify additional IP addresses for the pool.
404102
Error Message %PIX|ASA-3-404102: ISAKMP: Exceeded embryonic limitExplanation More than 500 embryonic security associations (SAs) exist, which could mean a DoS attack.
Recommended Action Enter the show crypto isakmp ca command to determine the origin of the attack. After the source is identified, deny access to the offending IP address or network.
405001
Error Message %PIX|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_nameExplanation The security appliance 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 check to see if it belongs to a valid host.
405101
Error Message %PIX|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 %PIX|ASA-4-405002: Received mac mismatch collision from IP_address/MAC_address for authenticated hostExplanation This packet appears for one of the following conditions:
•
•
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 check to see if they belong to a valid host.
405101
Error Message %PIX|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 security appliance 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 xlates and connections. This could also be caused by insufficient memory; 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 %PIX|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 security appliance 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 xlates and connections. This could also be caused by insufficient memory; 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 %PIX|ASA-4-405103: H225 message from source_address/source_port to dest_address/dest_port contains bad protocol discriminator hexExplanation PIX is expecting the protocol discriminator, 0x08, but it received something other than 0x08. This might happen because the endpoint is sending a bad packet, or received a message segment other than the first segment.
Recommended Action None required. The packet is allowed through.
405104
Error Message %PIX|ASA-4-405104: H225 message received from outside_address/outside_port to inside_address/inside_port before SETUPExplanation This message appears after an H.225 message is received out of order. The H.225 message was received before the initial SETUP message, which is not allowed. The security appliance 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 %PIX|ASA-4-405105: H323 RAS message AdmissionConfirm received from source_address/source_port to dest_address/dest_port without an AdmissionRequestExplanation A gatekeeper has sent an admission confirm (ACF), but the security appliance did not send an admission request (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 security appliance.
405106
Error Message %PIX|ASA-4-405106: H323 num channel is not created from %I/%d to %I/%d %sExplanation This syslog message is generated when the security appliance attempts to create a match condition on the H.323 media-type channel. See the match media-type command for more information.
Recommended Action None required.
405107
Explanation %PIX|ASA-4-405107: H245 Tunnel is detected and connection dropped from %I/%d to %I/%d %s
Explanation This syslog message is generated when an H.323 connection has been dropped because of attempted H.245 tunnel control during call setup. See the h245-tunnel-block command for more information.
Recommended Action None required.
405201
Error Message %PIX|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_addressExplanation The embedded address in the ILS packet payload is not the same as the source IP address of the IP packet header.
Recommended Action Check the host with the specified with the source_IP_address to determine why it sent an ILS packet with an incorrect embedded IP address.
405300
Error Message %PIX|ASA-4-405300: Radius Accounting Request received from from_addr is not allowedExplanation The accounting request came from a host that was not configured in the policy-map. The message is logged and processing stops.
•
Recommended Action If the host was configured to send RADIUS accounting messages to the security appliance, make sure 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 security appliance, 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 %PIX|ASA-4-405301: Attribute attribute_number does not match for user user_ipExplanation When the validate-attribute command is entered, the attribute values stored in the Accounting Request Start received do not match those stored in entry, if it exists.
•
•
Recommended Action None required.
406001
Error Message %PIX|ASA-4-406001: FTP port command low port: IP_address/port to IP_address on interface interface_nameExplanation A client entered an FTP port command and supplied a port less than 1024 (in the well-known port range typically devoted to server ports). This is indicative of an attempt to avert the site security policy. The security appliance drops the packet, terminates the connection, and logs the event.
Recommended Action None required.
406002
Error Message %PIX|ASA-4-406002: FTP port command different address: IP_address(IP_address) to IP_address on interface interface_nameExplanation A client issued an FTP port command and supplied an address other than the address used in the connection. This error message is indicative of an attempt to avert the site.s security policy. 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 security appliance drops the packet, terminates the connection, and logs the event. The address in parenthesis is the address from the port command.
Recommended Action None required.
407001
Error Message %PIX|ASA-4-407001: Deny traffic for local-host interface_name:inside_address, license limit of number exceededExplanation The host limit was exceeded. An inside host is counted toward the limit when one of the following conditions is true:
•
•
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 security appliance. 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
xlate
00:05:00 (five minutes)
conn
00:01:00 (one hour)
uauth
00:05:00 (five minutes)
407002
Error Message %PIX|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_nameExplanation This message is about connections through the security appliance. This message is displayed when the number of connections from a specified foreign address over a specified global address to the specified local address exceeds the maximum embryonic limit for that static. The security appliance attempts to accept the connection if it can allocate memory for that connection. It proxies on behalf of local host and sends a SYN_ACK packet to the foreign host. The security appliance retains pertinent state information, drops the packet, and waits for the acknowledgment from the client.
Recommended Action The message might indicate legitimate traffic, or indicate that a denial of service (DoS) attack is in progress. Check the source address to determine where the packets are coming from and whether it is a valid host.
407003
Error Message %PIX|ASA-4-407003: Established limit for RPC services exceeded numberExplanation The security appliance 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 %PIX|ASA-4-408001: IP route counter negative - reason, IP_address Attempt: numberExplanation 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.
408002
Error Message %PIX|ASA-4-408002: ospf process id route type update address1 netmask1 [distance1/metric1] via source IP:interface1 address2 netmask2 [distance2/metric2] interface2Explanation 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 timeout. This path shift only occurs if the network topology has been specifically designed to support path redundancy, in which case it is expected.
Recommended Action None required.
408003
Error Message %PIX|ASA-4-408003: can't track this type of object hexExplanation A component of the tracking system has encountered an object type that is not supported by the component. A STATE object was expected.
•
Recommended Action Reconfigure the track object to make it a STATE object.
409001
Error Message %PIX|ASA-4-409001: Database scanner: external LSA IP_address netmask is lost, reinstallsExplanation The software detected an unexpected condition. The router will take corrective action and continue.
Recommended Action None required.
409002
Error Message %PIX|ASA-4-409002: db_free: external LSA IP_address netmaskExplanation An internal software error occurred.
Recommended Action None required.
409003
Error Message %PIX|ASA-4-409003: Received invalid packet: reason from IP_address, interface_nameExplanation 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 %PIX|ASA-4-409004: Received reason from unknown neighbor IP_addressExplanation The OSPF hello, database description, or database request packet was received, but the router could not identify the sender.
Recommended Action This situation should correct itself.
409005
Error Message %PIX|ASA-4-409005: Invalid length number in OSPF packet from IP_address (ID IP_address), interface_nameExplanation The system received an OSPF packet with a field length of less than normal header size or 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 %PIX|ASA-4-409006: Invalid lsa: reason Type number, LSID IP_address from IP_address, IP_address, interface_nameExplanation 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.
409007
Error Message %PIX|ASA-4-409007: Found LSA with the same host bit set but using different mask LSA ID IP_address netmask New: Destination IP_address netmaskExplanation An internal software error occurred.
Recommended Action If the problem persists, contact the Cisco TAC.
409008
Error Message %PIX|ASA-4-409008: Found generating default LSA with non-zero mask LSA type : number Mask: netmask metric: number area: stringExplanation The router tried to generate a default LSA with the wrong mask and possibly wrong metric due to an internal software error.
Recommended Action If the problem persists, contact the Cisco TAC.
409009
Error Message %PIX|ASA-4-409009: OSPF process number cannot start. There must be at least one up IP interface, for OSPF to use as router IDExplanation 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 %PIX|ASA-4-409010: Virtual link information found in non-backbone area: stringExplanation An internal error occurred.
Recommended Action If the problem persists, contact the Cisco TAC.
409011
Error Message %PIX|ASA-4-409011: OSPF detected duplicate router-id IP_address from IP_address on interface interface_nameExplanation 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 %PIX|ASA-4-409012: Detected router with duplicate router ID IP_address in area stringExplanation 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 %PIX|ASA-4-409013: Detected router with duplicate router ID IP_address in Type-4 LSA advertised by IP_addressExplanation 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 %PIX|ASA-4-409023: Attempting AAA Fallback method method_name for request_type request for user user:Auth-server group server_tag unreachableExplanation An authentication or authorization attempt to an external server has failed and will now be performed using the local user database. aaa_operation is either "authentication" or "authorization." username is the user associated with the connection. server_group is the 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 security appliance. Make sure that the daemons are running on your AAA server.
410001
Error Message %PIX|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 This syslog message is generated when the domain-name length exceeds 255 bytes in a UDP DNS packet. (See RFC 1035 section 3.1.)
Recommended Action None required.
410002
Error Message %PIX|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/dportExplanation This syslog message is generated when the security device detects an excess number of DNS responses with a mismatched DNS identifier. The threshold is set by the id-mismatch DNS policy-map parameter submode command.
•
•
•
•
•
•
•
•
Recommended Action A high rate of mismatched DNS identifiers might indicate an attack on the cache. Check the IP address/port in the syslog message to trace the source of the attack. You can configure ACLs to block traffic permanently from the source.
410003
Error Message %PIX|ASA-4-410003: action_class: action DNS query_response from src_ifc:sip/sport to dest_ifc:dip/dport; further_infoExplanation This syslog message is generated when a DNS classification is performed on a DNS message and the specified criteria is satisfied. Then the configured action occurs.
•
•
•
•
•
•
•
•
•
•
Recommended Action None required.
410004
Error Message %ASA-6-410004: action_class: action DNS query_response from src_ifc:sip/sport to dest_ifc:dip/dport; further_infoExplanation This event is generated when a DNS classification is performed on a DNS message and the specified criteria is satisfied.
•
•
•
•
•
•
•
•
•
•
Recommended Action None required.
411001
Error Message %PIX|ASA-4-411001: Line protocol on interface interface_name changed state to upExplanation 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.
Recommended Action None required.
411002
Error Message %PIX|ASA-4-411002:Line protocol on interface interface_name changed state to downExplanation 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 %PIX|ASA-4-411003: Configuration status on interface interface_name changed state to downupExplanation 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 %PIX|ASA-4-411004: Configuration status on interface interface_name changed state to upExplanation 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 hang 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 devices.
•
Recommended Action None required.
412001
Error Message %PIX|ASA-4-412001:MAC MAC_address moved from interface_1 to interface_2Explanation This message is generated when a host move is detected from one module interface to another. In a transparent security appliance, mapping between the host (MAC) and security appliance port is maintained in a Layer 2 forwarding table. The table dynamically binds packet source MAC addresses to a security appliance 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 the host move 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 %PIX|ASA-4-412002:Detected bridge table full while inserting MAC MAC_address on interface interface. Number of entries = numExplanation This message is generated when the bridge table is full and an attempt is made to add one more entry. The security appliance 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
Recommended Action This might be an attempted attack. Make sure that the new bridge table entries are valid. In case of attack, use EtherType ACLs to access control vulnerable hosts.
413001
Error Message %ASA-4-413001: Module in slot slotnum is not able to shut down. Module Error: errnum messageExplanation The module in slotnum was not able to comply with a request from the ASA system module to shut down. It may be performing a task that could not be interrupted, like a software upgrade. The errnum and message text describes the reason why the module could not shut down, and recommends 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's preventing the module from shutting down.
413002
Error Message %ASA-4-413002: Module in slot slotnum is not able to reload. Module Error: errnum messageExplanation The module in slotnum was not able to comply with a request from the ASA system module to reload. It may be performing a task that could not be interrupted, like a software upgrade. The errnum and message text describes the reason why the module could not reload, and the recommended 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 in slot slotnum is not a recognized typeExplanation Generated whenever a card is detected that is not recognized as a valid card type.
Recommended Action Upgrade to a version of ASA system software that supports the module type installed.
413004
Error Message %ASA-4-413004: Module in slot slotnum failed to write software vnewver (currently vver), reason. Trying again.Explanation The module in the specified slot number failed to accept a software version, and will be transitioned to an UNRESPONSIVE state. Another attempt will be made to update the module software.
•
•
•
•
–
–
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 slotnum command.
413005
Error Message %ASA-1-413005: prod_id Module in slot slot, application is not supported app_name version app_vers type app_typeExplanation The module installed in slot slot is running an unsupported application version or type.
•
•
•
•
•
Recommended Action If the problem persists, contact the Cisco TAC.
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 is not the version required by another module.
•
•
•
•
Recommended Action If the problem persists, contact the Cisco TAC.
414001
Error Message %PIX|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 This syslog message is generated when logging module failed to save the logging buffer to external FTP server.
Recommended Action Take appropriate action based on the failed reason:
•
•
•
414002
Error Message %PIX|ASA-3-414002: Failed to save logging buffer to flash:/syslog directory using file name: filename: [fail_reason]Explanation This syslog message is generated when logging module failed to save the logging buffer to system flash.
Recommended Action If the failed reason is due to insufficient space, check the system flash's free space, make sure that the configured limits of the logging flash-size command are set properly. If the error is flash file system IO error, then contact the Cisco technical support 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 This message indicates that the TCP syslog server for remote host logging is successful, is connected to the server, and that new connections are permitted or denied based on the logging permit-hostdown policy. If logging permit-hostdown is configured, a new connection is permitted. If not configured, a new connection is denied.
•
•
•
Recommended Action Check whether or not 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 restoredExplanation 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.
•
•
•
Recommended Action None required.
415001
Error Message %PIX|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_numExplanation This syslog message is generated when one of the following occurs:
a.
b.
•
–
–
•
•
•
•
•
Recommended Action Enter the match {request | response} header command to reconfigure the HTTP header field value.
415002
Error Message %PIX|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_numExplanation This syslog message is generated when the specified HTTP header field length exceeds the user-configured length.
•
–
–
•
•
•
•
•
Recommended Action Enter the match {request | response} header header_name length gt num command to change the HTTP header field length.
415003
Error Message %PIX|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_numExplanation This syslog message is generated when the length of the message body exceeds user-configured length.
•
–
–
•
•
•
•
•
Recommended Action Enter the match {request | response} body length gt num command to change the length of the message body.
415004
Error Message %PIX|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_numExplanation This syslog message is generated when 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 %PIX|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_numExplanation This syslog message is generated when the length of the URI exceeds the user-configured length.
•
–
–
•
•
•
•
•
Recommended Action Enter the match request uri length gt num command to change the length of the URI.
415006
Error Message %PIX|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_numExplanation This syslog message is generated when the URI matches the regular expression that the user configured. See the match request uri regex {regex-name | class class-name} command for more information.
•
–
–
•
•
•
•
•
Recommended Action None required.
415007
Error Message %PIX|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_numExplanation This syslog message is generated when the message body matches the regular expression that the user configured. See the match {request | response} body regex {regex-name | class class-name} command for more information.
•
–
–
•
•
•
•
•
Recommended Action None required.
415008
Error Message %PIX|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_numExplanation This syslog message is generated when a value in a user-specified field in the message header matches 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.
•
–
–
•
•
•
•
•
Recommended Action None required.
415009
Error Message %PIX|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_numExplanation This syslog message is generated when the HTTP method matches the user-configured regular expression. See the match request method {regex-name | class class-name} command for more information.
•
–
–
•
•
•
•
•
Recommended Action None required.
415010
Error Message %PIX|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_numExplanation This syslog message is issued when the value in the "transfer encoding" field matches 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.
•
–
–
•
•
•
•
•
Recommended Action None required.
415011
Error Message %PIX|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_numExplanation This syslog message is generated when 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 %PIX|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_numExplanation This syslog message is generated when the "content-type" field does not contain a mime type that matches a built-in mime type.
•
–
–
•
•
•
•
•
Recommended Action Enter the match {request | response} header content-type unknown command to correct the problem.
415013
Error Message %PIX|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_numExplanation This syslog message is generated when a chunked encoding is malformed and the HTTP message cannot be parse, and whenever logging for the protocol-violation command is configured.
•
•
•
•
•
Recommended Action Enter the protocol-violation action {drop | reset} log command to correct the problem.
415014
Error Message %PIX|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_numExplanation This syslog message is generated when the mime type in an HTTP response is not in the "accept" field of the request.
•
–
–
•
•
•
•
•
Recommended Action Enter the match req-resp content-type mismatch command to correct the problem.
415015
Error Message %PIX|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_numExplanation This syslog message is generated when the an empty transfer encoding occurs.
•
–
–
•
•
•
•
•
Recommended Action Enter the match {request | response} header transfer-encoding empty command to correct the problem.
415016
Error Message %PIX|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_numExplanation This syslog message is generated when the number of unanswered HTTP requests exceeds the internal number of requests allowed.
•
•
•
•
•
Recommended Action Enter the protocol-violation action {drop | reset} log command to correct the problem.
415017
Error Message %PIX|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_numExplanation This syslog message is generated when 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.
•
–
–
•
•
•
•
•
Recommended Action None required.
415018
Error Message %PIX|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_numExplanation This syslog message is generated when the total header length exceeds 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.
415019
Error Message %PIX|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_numExplanation This syslog message is generated when the status line in a response matches user-configured regex. See the match response status-line regex {regex-name | class class-name } for more information.
•
–
–
•
•
•
•
•
Recommended Action None required.
415020
Error Message %PIX|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_numExplanation This syslog message is generated when a non-ASCII character is found.
Explanation
•
–
–
•
•
•
•
•
Recommended Action Enter the match {request | response} header non-ascii command to correct the problem.
416001
Error Message %PIX|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 firewallExplanation An SNMP packet was denied passage through the security appliance because of a bad packet format or a because the prot_version is not allowed through the security appliance. The field prot_version can be one of the following values: 1, 2, 2c, 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 %PIX|ASA-4-417001: Unexpected event received: numberExplanation 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 %PIX|ASA-4-417004: Filter violation error: conn number (string:string) in stringExplanation 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 %PIX|ASA-4-417006: No memory for string) in string. Handling: stringExplanation An operation failed due to low memory but will be handled with another mechanism.
Explanation If the problem persists, contact the Cisco TAC.
417008
Error Message %PIX-4-417008 AutoRP: removed string embedded group address1/mask1 on interface interface-name from address2 due to overlap address3/mask2Explanation The multicast boundary has a longer mask than the AutoRp encoded group.
•
•
•
•
•
•
•
Recommended Action Adjust the boundary access rules or RP mappings.
417009
Error Message %PIX-4-417009 AutoRp: discarded string on interface interface-name from address due to malformed packetExplanation An AutoRp packet was received without a group count in the RP mapping.
•
•
•
Recommended Action The originating device might not be RFC compliant. Upgrade the originating device or notify the owner of the device.
418001
Error Message %PIX|ASA-4-418001: Through-the-device packet to/from management-only network is denied: protocol_string from interface_name IP_address (port) to interface_name IP_address (port)Explanation A packet from the specified source to the destination is dropped because it is traversing the security appliance to/from the management only network.
•
•
•
•
Recommended Action Investigate who is generating such packet and why.
419001
Error Message %PIX|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 sizeExplanation This message is generated when the length of the TCP packet exceeds the MSS advertised in the 3-way handshake.
•
•
•
•
•
•
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:
access-list http-list permit tcp any host server_ip eq 80 class-map http match access-list http-list tcp-map tmap exceed-mss allow policy-map global_policy class http set connection advanced-options tmap419002
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 than the SYN that opened the embryonic connection. This could indicate that SYNs are being spoofed. This message occurs in Release 7.0.4.1 and later.
•
•
•
•
•
•
Recommended Action None required.
419003
Error Message %ASA-4-419003: Cleared TCP urgent flag from in_ifc:src_ip/src_port to out_ifc:dest_ip/dest_port.Explanation A duplicate TCP SYN was received during the three-way-handshake that has a different initial sequence number than the SYN that opened the embryonic connection. This could indicate that SYNs are being spoofed. This message occurs in Release 7.0.4.1 and later.
•
•
•
•
•
•
Recommended Action If users need to keep the urgent flag in TCP headers, they can use the urgent-flag allow command in TCP map configuration.
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)%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\nExplanation This message is displayed when packets are dropped when IPS fail-close mode is used and the IPS card is not up. This message is rate limited.
•
•
•
•
•
•
•
•
Recommended Action Check and 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)%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\nExplanation This message is displayed when IPS requests that the packet be dropped.
•
•
•
•
•
•
•
•
Recommended Action None required.
420003
Error Message %ASA-4-420003: IPS requested to reset TCP connection from ifc_in:SIP/SPORT to ifc_out:DIP/DPORTExplanation This message is displayed when IPS requests to reset a TCP connection.
•
•
•
•
•
•
Recommended Action None required.
420004
Error Message %ASA-6-420004: Virtual Sensor sensor_name was added on the AIP SSM\nExplanation A virtual sensor was added on the AIP SSM card
•
Recommended Action None required.
420005
Error Message %ASA-6-420005: Virtual Sensor sensor_name was deleted from the AIP SSM\nExplanation A virtual sensor was deleted from the AIP SSM card.
•
Recommended Action None required.
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\nExplanation This message is displayed when packets are dropped when IPS fail-close mode is used and the virtual sensor used for the packet is not present.
•
•
•
•
•
•
Recommended Action Check and add the virtual sensor.
420007
Error Message %ASA-4-420007: application-string cannot be enabled for the module in slot slot_id. The module's 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 security appliance that needs a corresponding software version in the SSM or SSC hardware module. The message is sent each time that the security appliance module manager detects state changes in the SSM or SSC hardware module.
•
•
•
Recommended Action Load the SSM or SSC hardware module with the correct software images that support the designated application.
421001
Error Message %ASA-3-421001: TCP|UDP flow from interface_name:ip/port to interface_name:ip/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.
•
•
•
•
Recommended Action Immediately investigate the problem with the service module.
421002
Error Message %ASA-6-421002: TCP|UDP flow from interface_name:IP_address/port to interface_nam:IP_address/port bypassed application checking because the protocol is not supported.Explanation Connection bypassed service module security checking because the protocol it is using cannot be scanned by the service module. For example, the CSC SSM is not capable of scanning TELNET traffic. If 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.
•
•
•
•
Recommended Action The configuration should be modified to only include protocols that are supported by the service module.
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 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/portExplanation The security appliance has failed to inject a packet as instructed by the service module. This could happen if the security appliance tries to inject a packet into a flow that has already been released.
•
•
Recommended Action This could happen because the security appliance maintains its connection table independently from the service module. Normally it will not cause any problem. If this affects security appliance performance, 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 applicationExplanation 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.
•
•
•
Recommended Action None required. However, if the overall count exceeds the user license you have purchased, contact the Cisco to upgrade your license.
421006
Error Message %ASA-6-421006: There are number users of application accounted during the past 24 hours.Explanation Identifies the total number of users who have used application for the past 24 hours. This message is generated every 24 hours to give the total number of hosts that have used services provided by the service module.
Recommended Action None required. However, if the overall count exceeds the user license you have purchased, contact the Cisco 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 This message is generated when a flow is skipped because the service module application has failed. By default, this message is rate limited to 1 message every 10 seconds.
•
•
•
•
Recommended Action Immediately investigate the problem with the service module.
422004
Error Message %PIX|ASA-4-422004: IP SLA Monitor number0: Duplicate event received. Event number number1Explanation The IP SLA monitor process has received a duplicate event. Currently, this message applies to destroy events. Only one destroy request will be applied.
•
•
Recommended Action This is only a warning message. If this reoccurs, 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 syslog. Then contact Cisco TAC and provide the representative with the information you gathered, along with information about the application that is configuring and polling the SLA probes.
422005
Error Message %PIX|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 could not be scheduled because the system clock is not set.
Recommended Action Ensure that the system clock is functional by using NTP or another mechanism.
422006
Error Message %PIX|ASA-4-422006: IP SLA Monitor Probe number: stringExplanation The IP SLA monitor probe could not be scheduled. Either the configured starting time has already occurred or the starting time is invalid.
•
•
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 There is an NBNS ID mismatch.
Recommended Action None required.
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 There is an NBDGM ID mismatch.
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.
424001
Error Message %ASA-4-424001: Packet denied protocol_string intf_in:src_ip/src_port intf_out:dst_ip/dst_port. [Ingress|Egress] interface is in a backup state.Explanation A packet was dropped because it was traversing the security appliance to/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 device from the backup interface will be denied. Conversely, if the default route to the primary interface is down, traffic through the device from the primary interface will be denied.
•
•
•
•
•
•
•
Recommended Action Investigate 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_portExplanation 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 security appliance through the backup interface will be denied. Conversely, if the default route to the primary interface is down, connections to the security appliance through the primary interface will be denied.
•
•
•
•
•
•
•
Recommended Action Investigate the source of the denied packet.
425001
Error Message %ASA-6-425001 Redundant interface redundant_interface_name created.Explanation This message indicates the specified redundant interface is created in the configuration.
•
Recommended Action None required.
425002
Error Message %ASA-6-425002 Redundant interface redundant_interface_name removed.Explanation This message indicates the specified redundant interface is removed from the configuration.
•
Recommended Action None required.
425003
Error Message %ASA-6-425003 Interface interface_name added into redundant interface redundant_interface_name.Explanation This message indicates the specified physical interface is added into the specified redundant interface as a member interface.
•
•
Recommended Action None required.
425004
Error Message %ASA-6-425004 Interface interface_name removed from redundant interface redundant_interface_name.Explanation This message indicates the specified redundant interface is removed from the specified redundant interface.
•
•
Recommended Action None required.
425005
Error Message %ASA-5-425005 Interface interface_name become active in redundant interface redundant_interface_nameExplanation Within a redundant interface, one member interface is the active member. Traffic only passes through the active member interface. This message indicates the specified physical interface becomes the active member of the specified redundant interface. Member interface switchover occurs when one of the following is true:
–
–
–
•
•
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 This message indicates there is an error when member interface switchover was attempted.
•
•
Recommended Action If the problem persists, contact the Cisco TAC.
428001
Error Message %ASA-6-428001: 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 This syslog message is generated when WAAS optimization is detected on a connection. All L7 inspection services, including IPS, are bypassed on WAAS-optimized connections.
Recommended Action No action is needed if the network contains WAE devices; otherwise, the network administrator should investigate the use of the WAAS option on this connection.
431001
Error Message %PIX|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 valueExplanation The RTP packet was dropped.
•
•
•
•
•
•
•
- Incorrect version value—The version number from the packet is incorrect.
- Invalid payload-type value—The payload type from the packet is invalid.
- Incorrect SSRC value—The 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 security appliance.
431002
Error Message %PIX|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•
•
•
•
•
•
•
–
–
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 security appliance.
444004
Error Message %ASA-2-444004: Temporary license key key has expired. Applying permanent license key permkeyExplanation The temporary license that was installed has expired. The features the license provided are no longer available.
•
•
Recommended Action A permanent license should be purchased and installed.
444005
Error Message %ASA-4-444005: Temporary license key key will expire in days daysExplanation The temporary license will be expiring in the time specified. After that date, the features the licensed provided are no longer available.
•
•
Recommended Action A permanent license should be purchased and installed 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, featureExplanation The time-based activation key has expired. The specified features that the license provided are no longer available.
•
•
Recommended Action You must purchase another time-based activation key as soon as possible to prevent service disruption for the features specified.
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.
•
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.
446002
Error Message %ASA-4-446002: Denied TLS Proxy session from src_ifc: src_ip/src_port to dest_ifc:dest_ip/dest_port, licensed UC Proxy session limit of lic_num exceeded.Explanation This syslog message is displayed when the licensed Unified Communication (UC) Proxy session limit is hit. A UC license is required for ASA Phone Proxy, TLS Proxy for Cisco Unified Mobile Advantage (CUMA) and MMP inspection, TLS Proxy for Cisco Unified Presence (CUP) federation, and TLS Proxy for SIP and Skinny inspection.
•
•
•
•
•
•
•
Recommended Action None required.
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 security appliance limit and the K8 export limit.
•
•
•
•
•
•
Recommended Action Check to see if UC-IME is disabled. If so, activate it.
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 exceededExplanation For a K8 platform, the limit of 250 SRTP crypto sessions is enforced. Each pair of SRTP encrypt/decrypt sessions is counted as one SRTP crypto session. A call is counted toward this limit only when encryption/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.
•
•
•
•
•
•
•
Note
Recommended Action None required. You can set up new SRTP crypto sessions only when existing SRTP crypto sessions have been released.
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 adaptive security appliance only.
•
•
•
•
•
Recommended Action None required.
466002
Error Message %ASA-4-466002: Denied TLS Proxy session from src_ifc: src_ip/src_port to src_ifc: dest_ip/dest_port, licensed UC Proxy session limit of lic_num exceededExplanation This message is displayed when the licensed UC proxy session limit is met. A UC license is required for ASA phone proxy, TLS proxy for CUMA and MMP inspection, TLS proxy for CUP federation, and TLS proxy for SIP and Skinny inspection.
•
•
•
•
•
•
•
Recommended Action None required.
Messages 500001 to 509001
This section contains messages from 500001 to 509001.
500001
Error Message %PIX|ASA-5-500001: ActiveX content modified src IP_address dest IP_address on interface interface_name.Explanation This message is displayed after you turn on the activex option using the filter command, and the security appliance detects an ActiveX object. The activex option allows the security appliance 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 %PIX|ASA-5-500002: Java content modified src IP_address dest IP_address on interface interface_name.Explanation This message is displayed after you turn on the java option using the filter command, and the security appliance detects an Java applet. The java option allows the security appliance to filter out Java contents by modifying it so that it no longer is tagged as an HTML object.
Recommended Action None required.
500003
Error Message %PIX|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_nameExplanation This message indicates that a header length in TCP is 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 security appliance and FTP is not listening, then the server 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 is displayed by syslog 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 1 second.
Recommended Action None required. This message should occur infrequently.
500004
Error Message %PIX|ASA-4-500004: Invalid transport field for protocol=protocol, from source_address/source_port to dest_address/dest_portExplanation This message appears when there is an invalid transport number, 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 This message is generated when 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.
•
•
•
•
•
•
•
•
•
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:
–
–
–
Besides these listed combinations, any other inspection and/or filter feature combinations are not valid.
501101
Error Message %PIX|ASA-5-501101: User transitioning priv levelExplanation The privilege level of a command was changed.
Recommended Action None required.
502101
Error Message %PIX|ASA-5-502101: New user added to local dbase: Uname: user Priv: privilege_level Encpass: stringExplanation A new username record was created. The message lists the username, privilege level, and encrypted password.
Recommended Action None required.
502102
Error Message %PIX|ASA-5-502102: User deleted from local dbase: Uname: user Priv: privilege_level Encpass: stringExplanation A username record was deleted. The message lists the username, privilege level, and encrypted password.
Recommended Action None required.
502103
Error Message %PIX|ASA-5-502103: User priv level changed: Uname: user From: privilege_level To: privilege_levelExplanation The privilege level of a user changed.
Recommended Action None required.
502111
Error Message %PIX|ASA-5-502111: New group policy added: name: policy_name Type: policy_typeExplanation This is an indication that a group policy has been configured using the group-policy CLI command. policy_name is the name of the group policy. policy_type is either "internal" or "external."
Recommended Action None required.
502112
Error Message %PIX|ASA-5-502112: Group policy deleted: name: policy_name Type: policy_typeExplanation A group policy has been removed using the group-policy CLI command. policy_name is the name of the group policy. policy_type is either "internal" or "external."
Recommended Action None required.
503001
Error Message %PIX|ASA-5-503001: Process number, Nbr IP_address on interface_name from string to string, reasonExplanation An OSPF 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 If the problem persists, contact the Cisco TAC.
504001
Error Message %PIX|ASA-5-504001: Security context context_name was added to the systemExplanation A security context was successfully added to the system.
Recommended Action None required.
504002
Error Message %PIX|ASA-5-504002: Security context context_name was removed from the systemExplanation A security context was successfully removed from the system.
Recommended Action None required.
505001
Error Message %ASA-5-505001: Module in slot slotnum is shutting down. Please wait...Explanation Generated when a card is being shut down.
Recommended Action None required.
505002
Error Message %ASA-5-505002: Module in slot slotnum is reloading. Please wait...Explanation Generated when a card is being reloaded.
Recommended Action None required.
505003
Error Message %ASA-5-505003: Module in slot slotnum is resetting. Please wait...Explanation Generated when a module is being reset.
Recommended Action None required.
505004
Error Message %ASA-5-505004: Module in slot slotnum shutdown is complete.Explanation Generated when a module has been shut down.
Recommended Action None required.
505005
Error Message %ASA-5-505005: Module in slot slotnum is initializing control communication. Please wait...Explanation Generated when a module has been detected and the ASA system module is initializing control channel communication with it.
Recommended Action None required.
505006
Error Message %ASA-5-505006: Module in slot slotnum is Up.Explanation Generated when a module has completed control channel initialization and is in the UP state.
Recommended Action None required.
505007
Error Message %ASA-5-505007: Module in slot slotnum is recovering. Please wait...Explanation Generated when a module is being recovered with the hw-module module slotnum recover boot command.
Recommended Action None required.
505008
Error Message %ASA-5-505008: Module in slot slotnum software is being updated to vnewver (currently vver)Explanation This message appears when the 4GE SSM module software is being upgraded by the system module.
•
•
•
Recommended Action None required. The update is proceeding normally.
505009
Error Message %ASA-5-505009: Module in slot slotnum software was updated to vnewverExplanation :This message appears when the 4GE SSM module software is successfully upgraded by the system module.
•
•
•
Recommended Action None required. The update has completed successfully.
505010
Error Message %ASA-5-505010: Module in slot slot removed.Explanation This message is generated when an SSM is removed from the ASA chassis.
•
Recommended Action None required.
505011
Error Message %ASA-1-505011: Type Module in slot slot, data channel communication is UP.Explanation This syslog message is generated whenever the data channel communication recovers from a DOWN state.
•
•
Recommended Action None required.
505012
Error Message %ASA-5-505012: Module in slot slot, application stopped application, version versionExplanation This message is generated whenever an application is stopped or removed from a 4GE SSM. This may occur when the 4GE SSM upgrades an application or when an application on the 4GE SSM is stopped or uninstalled.
•
•
•
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.
505013
Error Message %ASA-5-505013: Module in slot slot application changed from: application version version to: newapplication version newversion.Explanation This message is generated whenever an application version changes, such as after an upgrade. This occurs when a software update for the application on the module is complete.
•
•
•
•
•
•
•
•
Recommended Action Verify that the upgrade was expected and that the new version is correct.
505014
Error Message %ASA-1-505014: prod_id Module in slot slot, application down name, version version reasonExplanation The application running on the module in slot slot is disabled.
•
•
•
•
•
•
Recommended Action If the problem persists, contact the Cisco TAC.
505015
Error Message %ASA-1-505015: SSM model Module in slot number, application up application, version versionExplanation The application running on the SSM in slot number is up and running.
•
•
•
•
Recommended Action None required.
505016
Error Message %ASA-3-505016: prod_id Module in slot slot application changed from: name version version state state to: name version state state.Explanation The application version or name change was detected.
•
•
•
•
•
•
Recommended Action Verify that the change was expected and that the new version is correct.
506001
Error Message %ASA-5-506001: event_source_string event_stringExplanation Status of a file system has changed. The message describes the event and the source of the event that caused a file system to become available or unavailable. Examples of sources and events that could cause a file system status change are as follows:
•
•
•
Recommended Action None required.
507001
Error Message %PIX|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 exceededExplanation This message is displayed when reassembly buffer limit is exceeded during assembling TCP segments.
•
•
•
•
•
Recommended Action None required.
507002
Error Message %PIX|ASA-4-507002: Data copy in proxy-mode exceeded the buffer limitExplanation This syslog message is generated when there is an operational error when processing a fragmented TCP message.
Recommended Action None required.
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 This syslog message is generated when the TCP proxy/session API terminates a connection for various reasons. The reason is provided in the syslog message.
•
•
•
•
•
•
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
Recommended Action None required.
508001
Error Message %PIX|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 This message is generated when using DCERPC inspection. It is logged when a message header contains a nonstandard major or minor version.
•
•
•
Recommended Action If this is a valid version, and the problem persists, contact the Cisco TAC.
508002
Error Message %PIX|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 This message is generated when using DCERPC inspection. The message is logged when a response message contains an endpoint port number less than 1024 (in the range of well-known server ports).
Recommended Action None required.
509001
Error Message %ASA-5-509001: Connection attempt from src_intf:src_ip/src_port to dst_intf:dst_ip/dst_port 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 syslog message. This command is required on low-end platforms to allow the creation of interfaces beyond the licensed limit.
•
•
Recommended Action Upgrade the license to remove the requirement of this command on low-end platforms and remove the command from the configuration.
Messages 602101 to 634001
This section contains messages from 602101 to 634001.
602101
Error Message %PIX|ASA-6-602101: PMTU-D packet number bytes greater than effective mtu number dest_addr=dest_address, src_addr=source_address, prot=protocolExplanation This message occurs when the security appliance sends an ICMP destination unreachable message and when fragmentation is needed, but the "don't-fragment" bit is set.
Recommended Action Ensure that the data is sent correctly.
602103
Error Message %PIX|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 This message is displayed when the MTU of an SA is 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 256, whichever value is greater. If the suggested MTU is greater than 256, then the new MTU is set to the suggested value.
•
•
•
•
•
•
•
Recommended Action None required.
602104
Error Message %PIX|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 This message occurs when an ICMP message is received indicating that a packet sent over an IPSec tunnel exceeded the path MTU and the suggested MTU is 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.
Recommended Action None required.
602303
Error Message %PIX|ASA-6-602303: IPSEC: An direction tunnel_type SA (SPI=spi) between local_IP and remote_IP (username) has been created.•
•
•
•
•
•
Explanation A new security association (SA) was created.
Recommended Action No action is required.
602304
Error Message %PIX|ASA-6-602304: IPSEC: An direction tunnel_type SA (SPI=spi) between local_IP and remote_IP (username) has been deleted.Explanation This message is displayed when an SA is deleted.
•
•
•
•
•
•
Recommended Action No action is required.
603101
Error Message %PIX|ASA-6-603101: PPTP received out of seq or duplicate pkt, tnl_id=number, sess_id=number, seq=number.Explanation The security appliance 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 client PPTP configuration.
603102
Error Message %PIX|ASA-6-603102: PPP virtual interface interface_name - user: user aaa authentication started.Explanation The security appliance sent an authentication request to the AAA server.
Recommended Action None required.
603103
Error Message %PIX|ASA-6-603103: PPP virtual interface interface_name - user: user aaa authentication statusExplanation The security appliance received an authentication response from the AAA server.
Recommended Action None required.
603104
Error Message %PIX|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 stringExplanation A PPTP tunnel was created.
Recommended Action None required.
603105
Error Message %PIX|ASA-6-603105: PPTP Tunnel deleted, tunnel_id = number, remote_peer_ip= remote_addressExplanation A PPTP tunnel was deleted.
Recommended Action None required.
603106
Error Message %PIX|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 userExplanation An L2TP tunnel was created.
Recommended Action None required.
603107
Error Message %PIX|ASA-6-603107: L2TP Tunnel deleted, tunnel_id = number, remote_peer_ip = remote_addressExplanation An L2TP tunnel was deleted.
Recommended Action None required.
603108
Error Message %PIX|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 = numberExplanation This message is displayed each time a new PPPoE tunnel is created.
Recommended Action None required.
603109
Error Message %PIX|ASA-6-603109: Teardown PPPOE Tunnel at interface_name, tunnel-id = number, remote-peer = IP_addressExplanation This message is displayed each time a new PPPoE tunnel is deleted.
Recommended Action None required.
603110
Error Message %ASA-7-603110: Multiple L2TP sessions added to the tunnel. tunnel_id: tunnel id, number_of_sessions: session_countExplanation This message is displayed when multiple sessions are added to an L2TP tunnel.
•
•
Recommended Action None required.
604101
Error Message %PIX|ASA-6-604101: DHCP client interface interface_name: Allocated ip = IP_address, mask = netmask, gw = gateway_addressExplanation The security appliance DHCP client successfully obtained an IP address from a DHCP server. The dhcpc command statement allows the security appliance 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 %PIX|ASA-6-604102: DHCP client interface interface_name: address releasedExplanation The security appliance DHCP client released an allocated IP address back to the DHCP server.
Recommended Action None required.
604103
Error Message %PIX|ASA-6-604103: DHCP daemon interface interface_name: address granted MAC_address (IP_address)Explanation The security appliance DHCP server granted an IP address to an external client.
Recommended Action None required.
604104
Error Message %PIX|ASA-6-604104: DHCP daemon interface interface_name: address releasedExplanation An external client released an IP address back to the security appliance DHCP server.
Recommended Action None required.
605004
Error Message %PIX|ASA-6-605004: Login denied from source-address/source-port to interface:destination/service for user "username"The following form of the message is displayed when the user attempts to login to the console:
Login denied from serial to console for user "username"Explanation This message appears after an incorrect login attempt or a failed login to the security appliance. 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.
•
•
•
•
•
•
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.
605005
Error Message %PIX|ASA-6-605005: Login permitted from source-address/source-port to interface:destination/service for user "username"The following form of the message is displayed when the user logs in to the console:
Login permitted from serial to console for user "username"Explanation This message appears when a user is authenticated successfully and a management session starts.
•
•
•
•
•
•
Recommended Action None required.
606001
Error Message %PIX|ASA-6-606001: ASDM session number number from IP_address startedExplanation This message indicates that an administrator has been authenticated successfully and a ASDM session was started.
Recommended Action None required.
606002
Error Message %PIX|ASA-6-606002: ASDM session number number from IP_address endedExplanation This message indicates that a ASDM session ended.
Recommended Action None required.
606003
Error Message %PIX|ASA-6-606003: ASDM logging session number id from IP_address started id session ID assignedExplanation An ASDM logging connection is started by a remote management client.
•
Recommended Action No action is required from the user.
606004
Error Message %PIX|ASA-6-606004: ASDM logging session number id from IP_address endedExplanation An ASDM logging connection is terminated.
•
•
Recommended Action No action is required from the user.
607001
Error Message %PIX|ASA-6-607001: Pre-allocate SIP connection_type secondary channel for interface_name:IP_address/port to interface_name:IP_address from string messageExplanation This message indicates that the fixup sip command preallocated a SIP connection after inspecting a SIP message. The connection_type is one of the following strings:
–
–
–
–
–
–
–
–
Recommended Action None required.
607002
Error Message %PIX|ASA-4-607002: action_class: action SIP req_resp req_resp_info from src_ifc:sip/sport to dest_ifc:dip/dport; further_infoExplanation This message is generated when a SIP classification is performed on a SIP message and the specified criteria is satisfied. Then the configured action occurs.
•
•
•
•
•
•
•
•
•
•
•
–
matched Class id: class-name—For example:
matched Class 1234: my_class–
parameter-command: descriptive-message—For example:
strict-header-validation: Mandatory header field `Via' is missingstate-checking: Message CANCEL is not permitted to create a Dialog.Recommended Action None required.
607003
Error Message %PIX|ASA-6-607003: action_class: Received SIP req_resp req_resp_info from src_ifc:sip/sport to dest_ifc:dip/dport; further_infoExplanation This event is generated when a SIP classification is performed on a SIP message and the specified criteria is satisfied. Then the standalone log action occurs.
•
•
•
•
•
•
•
•
•
•
–
matched Class id: class-name—For example:
matched Class 1234: my_class–
parameter-command: descriptive-message—For example:
strict-header-validation: Mandatory header field `Via' is missingstate-checking: Message CANCEL is not permitted to create a Dialog.Recommended Action None required.
608001
Error Message %PIX|ASA-6-608001: Pre-allocate Skinny connection_type secondary channel for interface_name:IP_address to interface_name:IP_address/port from string messageExplanation This message indicates that the inspect skinny command preallocated a Skinny connection after inspecting a Skinny message. The connection_type is one of the following strings:
–
–
–
–
–
–
–
–
Recommended Action None required.
608002
Error Message %PIX|ASA-4-608002: Dropping Skinny message for in_ifc:src_ip/src_port to out_ifc:dest_ip/dest_port, SCCPPrefix length value too smallExplanation A Skinny (SSCP) message was received with an SCCP prefix length less than the minimum length configured.
•
•
•
•
•
•
•
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 %PIX|ASA-4-608003: Dropping Skinny message for in_ifc:src_ip/src_port to out_ifc:dest_ip/dest_port, SCCPPrefix length value too largeExplanation A Skinny (SSCP) message was received with an SCCP prefix length greater than the maximum length configured.
•
•
•
•
•
•
•
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 %PIX|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 %PIX|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 completeExplanation 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.
609001
Error Message %PIX|ASA-7-609001: Built local-host interface_name:IP_addressExplanation A network state container is reserved for host IP_address connected to interface interface_name. This is an informational message.
Recommended Action None required.
609002
Error Message %PIX|ASA-7-609002: Teardown local-host interface_name:IP_address duration timeExplanation A network state container for host IP_address connected to interface interface_name is removed. This is an informational message.
Recommended Action None required.
610001
Error Message %PIX|ASA-3-610001: NTP daemon interface interface_name: Packet denied from IP_addressExplanation An NTP packet was received from a host that does not match one of the configured NTP servers. The security appliance 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 %PIX|ASA-3-610002: NTP daemon interface interface_name: Authentication failed for packet from IP_addressExplanation The received NTP packet failed the authentication check.
Recommended Action Ensure that both the security appliance and the NTP server are set to use authentication, and the same key number and value.
610101
Error Message %PIX|ASA-6-610101: Authorization failed: Cmd: command Cmdtype: command_modifierExplanation Command authorization failed for the specified command. The command_modifier is one of the following strings:
–
–
–
–
Explanation If the security appliance encounters any other value other than the four command types listed, the message "unknown command type" is displayed.
Recommended Action None required.
611101
Error Message %PIX|ASA-6-611101: User authentication succeeded: Uname: userExplanation User authentication succeeded when accessing the security appliance succeeded.
Recommended Action None required.
611102
Error Message %PIX|ASA-6-611102: User authentication failed: Uname: userExplanation User authentication failed when attempting to access the security appliance.
Recommended Action None required.
611103
Error Message %PIX|ASA-5-611103: User logged out: Uname: userExplanation The specified user logged out.
Recommended Action None required.
611104
Error Message %PIX|ASA-5-611104: Serial console idle timeout exceededExplanation The configured idle timeout for the security appliance serial console was exceeded because of no user activity.
Recommended Action None required.
611301
Error Message %PIX|ASA-6-611301: VPNClient: NAT configured for Client Mode with no split tunneling: NAT address: mapped_addressExplanation The VPN client policy for client mode with no split tunneling was installed.
Recommended Action None required.
611302
Error Message %PIX|ASA-6-611302: VPNClient: NAT exemption configured for Network Extension Mode with no split tunnelingExplanation VPN client policy for network extension mode with no split tunneling was installed.
Recommended Action None required.
611303
Error Message %PIX|ASA-6-611303: VPNClient: NAT configured for Client Mode with split tunneling: NAT address: mapped_address Split Tunnel Networks: IP_address/netmask IP_address/netmaskExplanation VPN client policy for client mode with split tunneling was installed.
Recommended Action None required.
611304
Error Message %PIX|ASA-6-611304: VPNClient: NAT exemption configured for Network Extension Mode with split tunneling: Split Tunnel Networks: IP_address/netmask IP_address/netmaskExplanation VPN client policy for network extension mode with split tunneling was installed.
Recommended Action None required.
611305
Error Message %PIX|ASA-6-611305: VPNClient: DHCP Policy installed: Primary DNS: IP_address Secondary DNS: IP_address Primary WINS: IP_address Secondary WINS: IP_addressExplanation VPN client policy for DHCP was installed.
Recommended Action None required.
611306
Error Message %PIX|ASA-6-611306: VPNClient: Perfect Forward Secrecy Policy installedExplanation Perfect forward secrecy was configured as part of the VPN client download policy.
Recommended Action None required.
611307
Error Message %PIX|ASA-6-611307: VPNClient: Head end: IP_addressExplanation The VPN client is connected to the specified headend.
Recommended Action None required.
611308
Error Message %PIX|ASA-6-611308: VPNClient: Split DNS Policy installed: List of domains: string stringExplanation A split DNS policy was installed as part of the VPN client downloaded policy.
Recommended Action None required.
611309
Error Message %PIX|ASA-6-611309: VPNClient: Disconnecting from head end and uninstalling previously downloaded policy: Head End: IP_addressExplanation A VPN client is disconnecting and uninstalling a previously installed policy.
Recommended Action None required.
611310
Error Message %PIX|ASA-6-611310: VNPClient: XAUTH Succeeded: Peer: IP_addressExplanation The VPN client Xauth succeeded with the specified headend.
Recommended Action None required.
611311
Error Message %PIX|ASA-6-611311: VNPClient: XAUTH Failed: Peer: IP_addressExplanation The VPN client Xauth failed with the specified headend.
Recommended Action None required.
611312
Error Message %PIX|ASA-6-611312: VPNClient: Backup Server List: reasonExplanation When the security appliance is an Easy VPN remote device, this message indicates that the Easy VPN server downloaded a list of backup servers to the security appliance. This list overrides any backup servers you configured locally. If the downloaded list is empty, then the security appliance uses no backup servers. The reason is one of the following messages:
•
•
Recommended Action None required.
611313
Error Message %PIX|ASA-3-611313: VPNClient: Backup Server List Error: reasonExplanation When the security appliance is an Easy VPN remote device, and the Easy VPN server downloads a backup server list to the security appliance, this message indicates that the list contains an invalid IP address or a hostname. The security appliance 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 %PIX|ASA-6-611314: VPNClient: Load Balancing Cluster with Virtual IP: IP_address has redirected the to server IP_addressExplanation When the security appliance is an Easy VPN remote device, the master server of the load balancing cluster redirected the security appliance to connect to a particular server.
Recommended Action None required.
611315
Error Message %PIX|ASA-6-611315: VPNClient: Disconnecting from Load Balancing Cluster member IP_addressExplanation When the security appliance is an Easy VPN remote device, this message indicates that it disconnected from a load balancing cluster server.
Recommended Action None required.
611316
Error Message %PIX|ASA-6-611316: VPNClient: Secure Unit Authentication EnabledExplanation When the security appliance is an Easy VPN remote device, the downloaded VPN policy enabled Secure Unit Authentication (SUA).
Recommended Action None required.
611317
Error Message %PIX|ASA-6-611317: VPNClient: Secure Unit Authentication DisabledExplanation When the security appliance is an Easy VPN remote device, the downloaded VPN policy disabled Secure Unit Authentication (SUA).
Recommended Action None required.
611318
Error Message %PIX|ASA-6-611318: VPNClient: User Authentication Enabled: Auth Server IP: IP_address Auth Server Port: port Idle Timeout: timeExplanation When the security appliance is an Easy VPN remote device, the downloaded VPN policy enabled Individual User Authentication (IUA) for users on the security appliance inside network.
•
•
•
Recommended Action None required.
611319
Error Message %PIX|ASA-6-611319: VPNClient: User Authentication DisabledExplanation When the security appliance is an Easy VPN remote device, the downloaded VPN policy disabled Individual User Authentication (IUA) for users on the security appliance inside network.
Recommended Action None required.
611320
Error Message %PIX|ASA-6-611320: VPNClient: Device Pass Thru EnabledExplanation When the security appliance 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 Individual User Authentication (IUA) is enabled.
Recommended Action None required. If the Easy VPN server enables this feature, you can specify the devices that should be exempt from authentication (IUA) using the vpnclient mac-exempt command on the security appliance.
611321
Error Message %PIX|ASA-6-611321: VPNClient: Device Pass Thru DisabledExplanation When the security appliance is an Easy VPN remote device, the downloaded VPN policy disabled device pass through.
Recommended Action None required.
611322
Error Message %PIX|ASA-6-611322: VPNClient: Extended XAUTH conversation initiated when SUA disabledExplanation When the security appliance is an Easy VPN remote device and the downloaded VPN policy disabled secure unit5kujnm0o authentication (SUA), the Easy VPN server uses two-factor/SecurID/cryptocard-based authentication mechansims to authenticate the security appliance 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 %PIX|ASA-6-611323: VPNClient: Duplicate split nw entryExplanation When the security appliance is an Easy VPN remote device, this message indicates that the downloaded VPN policy contains 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 %PIX|ASA-5-612001: Auto Update succeeded:filename, version:numberExplanation 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.
Recommended Action None required.
612002
Error Message %PIX|ASA-4-612002: Auto Update failed:filename, version:number, reason:reasonExplanation This message indicates that an update from an Auto Update server failed.
•
•
•
–
–
–
–
–
–
–
–
–
–
–
–
–
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 Cisco TAC.
612003
Error Message %PIX|ASA-4-612003:Auto Update failed to contact:url, reason:reasonExplanation This indicates that the Auto Update daemon was unable to contact the specified URL url. This could 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 server, authentication failed, file not found, and so on.
Recommended Action Check the configuration of the Auto Update server.
613001
Error Message %PIX|ASA-6-613001: Checksum Failure in database in area string Link State Id IP_address Old Checksum number New Checksum numberExplanation OSPF has detected a checksum error in the database due to memory corruption.
Recommended Action Restart the OSPF process.
613002
Error Message %PIX|ASA-6-613002: interface interface_name has zero bandwidthExplanation The interface reports its bandwidth as zero.
Recommended Action If the problem persists, contact the Cisco TAC.
613003
Error Message %PIX|ASA-6-613003: IP_address netmask changed from area string to area stringExplanation An OSPF configuration change has caused a network range to change areas.
Recommended Action Reconfigure OSPF with the correct network range.
614001
Error Message %PIX|ASA-6-614001: Split DNS: request patched from server: IP_address to server: IP_addressExplanation Split DNS is redirecting DNS queries from the original destination server to the primary enterprise DNS server.
Recommended Action None required.
614002
Error Message %PIX|ASA-6-614002: Split DNS: reply from server:IP_address reverse patched back to original server:IP_addressExplanation Split DNS is redirecting DNS queries from the enterprise DNS server to the original destination server.
Recommended Action None required.
615001
Error Message %PIX|ASA-6-615001: vlan number not available for firewall interfaceExplanation The switch removed the VLAN from the security appliance.
Recommended Action This is an informational message.
615002
Error Message %PIX|ASA-6-615002: vlan number available for firewall interfaceExplanation The switch added the VLAN to the security appliance.
Recommended Action This is an informational message.
616001
Error Message %PIX|ASA-6-616001:Pre-allocate MGCP data_channel connection for inside_interface:inside_address to outside_interface:outside_address/port from message_type messageExplanation An MGCP data channel connection, RTP, or RTCP is preallocated. The message text also specifies which message has triggered the connection preallocation.
Recommended Action None required.
617001
Error Message %PIX|ASA-6-617001: GTPv version msg_type from source_interface:source_address/source_port not accepted by source_interface:dest_address/dest_portExplanation This message appears when a request was not accepted by the peer. This is usually seen with a Create PDP Context request.
Recommended Action None required.
617002
Error Message %PIX|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: reasonExplanation This message appears when a PDP context is removed from the database either because it expired, a Delete PDP Context Request/Response was exchanged, or a user removed it using the CLI.
Recommended Action None required.
617003
Error Message %PIX|ASA-6-617003: GTP Tunnel created from source_interface:source_address/source_port to source_interface:dest_address/dest_portExplanation This message appears when a GTP tunnel was created after receiving a Create PDP Context Response that accepted the request.
Recommended Action None required.
617004
Error Message %PIX|ASA-6-617004: GTP connection created for response from source_interface:source_address/0 to source_interface:dest_address/dest_portExplanation This message appears when the SGSN or GGSN signaling address in the Create PDP Context Request or Response, respectively, is different than the SGSN/GGSN sending it.
Recommended Action None required.
617100
Error Message PIX|ASA-6-617100: Teardown num_conns connection(s) for user user_ipExplanation The connections for this user were torn down because either a RADIUS accounting stop or RADIUS accounting start was received, which contains attributes configured in the policy-map for a match. The attributes did not match those stored for the user entry, if the user entry exists.
•
•
Recommended Action None required.
620001
Error Message %PIX|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 messageExplanation The security appliance pre-allocates 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 %PIX|ASA-4-620002: Unsupported CTIQBE version: hex: from interface_name:IP_address/port to interface_name:IP_address/portExplanation The security appliance received a CTIQBE message with an unsupported version number. The security appliance drops 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 could be malformed, a non-CTIQBE packet, or corrupted before it arrives at the security appliance. 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 security appliance image that supports this CTIQBE version is available.
621001
Error Message %PIX|ASA-6-621001: Interface interface_name does not support multicast, not enabledExplanation This message appears when 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 %PIX|ASA-6-621002: Interface interface_name does not support multicast, not enabledExplanation This message appears when 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.
621003
Error Message %PIX|ASA-6-621003: The event queue size has exceeded numberExplanation This message appears when the number of event managers created has exceeded the expected amount.
Recommended Action If the problem persists, contact the Cisco TAC.
621006
Error Message %PIX|ASA-6-621006: Mrib disconnected, (IP_address,IP_address) event cancelledExplanation This message appears when 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 %PIX|ASA-6-621007: Bad register from interface_name:IP_address to IP_address for (IP_address, IP_address)Explanation This message appears when a PIM router configured as a rendezvous point or with Network Address Translation (NAT) has received a PIM register packet from another PIM router. The data encapsulated in this packet is invalid.
Recommended Action It is likely that the sending router is erroneously sending non-RFC registers. Upgrade the sending router.
621008
Error Message %PIX-6-621008 AutoRP: discard string on interface interface-name from address due to incorrect version.Explanation Received an AutoRP packet with incorrect version.
Recommended Action None required.
621009
Error Message %PIX-6-621009 AutoRP: discard string on interface interface-name from address due to incorrect type numberExplanation An AutoRP packet was received with an incorrect AutoRP type.
Recommended Action None required.
621010
Error Message %PIX-6-621010 AutoRP: discard string on interface interface-name from address due to zero RP countExplanation An AutoRP packet was received with no RP mappings. Or because of the multicast boundary, all RP mappings were removed.
Recommended Action Adjust the boundary access rules or RP mappings.
622001
Error Message %PIX|ASA-6-622001: string tracked route network mask address, distance number, table string, on interface interface-nameExplanation 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.
•
•
•
•
•
•
•
Recommended Action None required. This is an informational message that indicates a change in routing and a likely change in forwarding paths, as configured by the tracking and SLA commands.
622101
Error Message %PIX|ASA-6-622101: Starting regex table compilation for match_command; table entries = regex_num entriesExplanation Provides information on the background activities of regex compilation.
•
•
Recommended Action None required.
622102
Error Message %PIX|ASA-6-622102: Completed regex table compilation for match_command; table size = num bytesExplanation Provides information on the background activities of the regex compilation.
•
•
Recommended Action None required.
634001
Error Message %ASA-6-634001: DAP: User user, Addr ipaddr, Connection connection; The following DAP records were selected for this connection: DAP Record namesExplanation Displays the DAP records selected for the connection.
•
•
•
IPSec—IPSec connection
AnyConnect—AnyConnect connection
Clientless—Web browser connection
Cut-Through-Proxy—Cut-Through-Proxy connection
L2TP—L2TP client connection
•
Recommended Action None required.
Messages 701001 to 737033
This section contains messages from 701001 to 737033.
Most of the ISAKMP syslog messages have a common set of prepended objects to help identify the tunnel. These objects precede the descriptive text of a syslog message when available. If the object is not known at the time the syslog 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 %PIX|ASA-7-701001: alloc_user() out of Tcp_user objectsExplanation This is a AAA message. This message is displayed 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 %PIX|ASA-7-701002: alloc_user() out of Tcp_proxy objectsExplanation This is a AAA message. This message is displayed if the user authentication rate is too high for the module to handle new AAA requests.
Error Message Enable Flood Defender with the floodguard enable command.702305
Error Message %PIX|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 This message is displayed when more than 4 billion packets have been received in the IPSec tunnel and a new tunnel is being negotiated.
•
•
•
•
•
•
Recommended Action Contact the peer administrator to compare the SA lifetime setting.
702307
Error Message %PIX|ASA-3-702307: IPSEC: An direction tunnel_type SA (SPI=spi) between local_IP and remote_IP (username) is rekeying due to data rollover.•
•
•
•
•
•
Explanation This message is displayed when an SA data life span expires. This message indicates that an IPSec SA is rekeying as a result of the amount of data transmitted with that SA. This information is useful for debugging rekey issues.
Recommended Action None required.
703001
Error Message %PIX|ASA-7-703001: H.225 message received from interface_name:IP_address/port to interface_name:IP_address/port is using an unsupported version numberExplanation The security appliance received an H.323 packet with an unsupported version number. The security appliance might re-encode the protocol version field of the packet to the highest supported version.
Recommended Action Use the version of H.323 that the security appliance supports in the VoIP network.
703002
Error Message %PIX|ASA-7-703002: Received H.225 Release Complete with newConnectionNeeded for interface_name:IP_address to interface_name:IP_address/portExplanation This debugging message indicates that the security appliance received the specified H.225 message, and that the security appliance opened a new signaling connection object for the two specified H.323 endpoints.
Recommended Action None required.
709001, 709002
Error Message %PIX|ASA-7-709001: FO replication failed: cmd=command returned=codeError Message %PIX|ASA-7-709002: FO unreplicable: cmd=commandExplanation These failover messages only appear during the development debug testing phase.
Recommended Action None required.
709003
Error Message %PIX|ASA-1-709003: (Primary) Beginning configuration replication: Sending to mate.Explanation This is a failover message. This message is displayed 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 %PIX|ASA-1-709004: (Primary) End Configuration Replication (ACT)Explanation This is a failover message. This message is displayed when the active unit completes replicating its configuration on the standby unit. (Primary) can also be listed as (Secondary) for the secondary unit.
Recommended Action None required.
709005
Error Message %PIX|ASA-1-709005: (Primary) Beginning configuration replication: Receiving from mate.Explanation This message indicates that the standby the security appliance received the first part of the configuration replication from the active the security appliance. (Primary) can also be listed as (Secondary) for the secondary unit.
Recommended Action None required.
709006
Error Message %PIX|ASA-1-709006: (Primary) End Configuration Replication (STB)Explanation This is a failover message. This message is displayed when the standby unit completes replicating 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 %PIX|ASA-2-709007: Configuration replication failed for command commandExplanation This is a failover message. This message is displayed when the standby unit is unable to complete replicating a configuration sent by the active unit. The command that caused the failure displays at the end of the message.
Recommended Action If the problem persists, contact the Cisco TAC.
710001
Error Message %PIX|ASA-7-710001: TCP access requested from source_address/source_port to interface_name:dest_address/serviceExplanation This message appears when the first TCP packet destined to the security appliance requests to establish a TCP session. This packet is the first SYN packet of the three-way handshake. This message appears when the respective access control list (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 %PIX|ASA-7-710002: {TCP|UDP} access permitted from source_address/source_port to interface_name:dest_address/serviceExplanation For a TCP connection, this message appears when the second TCP packet destined to the security appliance requests to establish a TCP session. This packet is the final ACK of the three-way handshake. This message appears when the respective access control list (Telnet, HTTP, or SSH) has permitted the packet. Also, the SYN cookie verification is successful and the state is reserved for the TCP session.
For a UDP connection, the connection was permitted. For example, this message appears (with the service snmp) when the module receives 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.
Recommended Action None required.
710003
Error Message %PIX-3-710003: {TCP|UDP} access denied by ACL from source_IP/source_port to interface_name:dest_IP/serviceThe following is an example:
%PIX-3-710003: UDP access denied by ACL from 95.1.1.14/5000 to outside:95.1.1.13/1005Explanation This message is displayed when the security appliance denies an attempt to connect to the interface service. For example, this message may occur when the firewall receives an SNMP request from an unauthorized SNMP management station.
Recommended Action Use the show run http, show run ssh, or show run telnet commands to verify that the security appliance is configured to permit the service access from the host or network. If this message appears frequently, it can indicate an attack.
710004
Error Message %PIX|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 security appliance management connections for the service was exceeded. The security appliance permits at most five concurrent management connections per management service. Alternatively, this message may be generated when an error has occurred in the to-the-box connection counter.
•
•
•
•
•
•
•
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.
710005
Error Message %PIX|ASA-7-710005: {TCP|UDP} request discarded from source_address/source_port to interface_name:dest_address/serviceExplanation This message appears when the security appliance does not have a UDP server that services the UDP request. The message can also indicate a TCP packet that does not belong to any session on the security appliance. In addition, this message appears (with the service snmp) when the security appliance 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 1 time every 10 seconds so that the log receiver is not overwhelmed.
Recommended Action In networks that heavily utilize broadcasting services such as DHCP, RIP or NetBios, the frequency of this message can be high. If this message appears in excessive number, it may indicate an attack.
710006
Error Message %PIX|ASA-7-710006: protocol request discarded from source_address to interface_name:dest_addressExplanation This message appears when the security appliance does not have an IP server that services the IP protocol request; for example, the security appliance receives IP packets that are not TCP or UDP, and the security appliance cannot service the request.
Recommended Action In networks that heavily utilize broadcasting services such as DHCP, RIP or NetBios, the frequency of this message can be high. If this message appears in excessive numbers, it may indicate an attack.
710007
Error Message %PIX|ASA-7-710007: NAT-T keepalive received from 86.1.161.1/1028 to outside:86:1.129.1/4500Explanation This message appears when the ASA security appliance receives NAT-T keepalive messages.
Recommended Action None required.
711001
Error Message %PIX|ASA-7-711001: debug_trace_msgExplanation This syslog message appears after you enter the logging debug-trace command for the logging feature. When the logging debug-trace command is enabled, all debug messages will be redirected to the syslog message for processing. For security reasons, the syslog message output must be encrypted or sent over a secure out-of-band network.
Recommended Action None required.
711003
Error Message %PIX/ASA-7-711003: Unknown/Invalid interface identifier(vpifnum) detected.Explanation This message reports an internal inconsistency that should not occur during normal operation. However, there is no harmful impact of this if it is seen rarely. If seen frequently, it might be worthwhile debugging.
•
Recommended Action If the problem persists, contact the Cisco TAC.
711004
Error Message %ASA-4-711004: Task ran for msec msec, Process = process_name, PC = pc, Call stack = call stackExplanation This message appears when a process uses 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.
•
•
•
•
Recommended Action None required.
711005
Error Message %ASA-5-711005: Traceback: call_stackExplanation This message reports an internal software error that should not occur. The device can usually recover from this error and no harmful effect to the device results.
•
Recommended Action A software error has occurred. Contact the Cisco TAC.
713004
Error Message %PIX|ASA-3-713004: device scheduled for reboot or shutdown, IKE key acquire message on interface interface num, for Peer IP_address ignoredExplanation This message appears when the security appliance has received an IKE packet from a remote entity trying to initiate a tunnel. Because the security appliance is scheduled for a reboot or shutdown, it does not allow any more tunnels to be established. The IKE packet is ignored and dropped.
Explanation None required.
713006
Error Message %PIX|ASA-5-713006: Failed to obtain state for message Id message_number, Peer Address: IP_addressExplanation This message indicates that the security appliance does not know about the received message ID. The message ID is used to identify a specific IKE Phase 2 negotiation. This is most likely an error condition on the security appliance but may indicate that the two IKE peers are out of synchronization.
Recommended Action None required.
713008
Error Message %PIX|ASA-3-713008: Key ID in ID payload too big for pre-shared IKE tunnelExplanation This message indicates that a key ID value was received in the ID payload which was longer than the maximum allowed size of a groupname 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 groupname of that size cannot be created in the security appliance. Notify the user to change the incorrect groupname on the client.
Recommended Action Make sure that the client peer (most likely an Altiga RA Client) specifies a valid groupname. The current maximum length for a groupname is 32.
713009
Error Message %PIX|ASA-3-713009: OU in DN in ID payload too big for Certs IKE tunnelExplanation This message indicates that an OU value in the DN was received in the ID payload which was longer than the maximum allowed size of a groupname 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 security appliance, the groupname must be a valid length. The current maximum length of a groupname is 32.
713010
Error Message %PIX|ASA-5-713010: IKE area: failed to find centry for message Id message_numberExplanation This message appears when an attempt is made to locate a conn_entry (IKE phase 2 struct that corresponds to an IPSec SA) by the unique Message ID failed. The internal structure was not found. This can occur if a session is terminated in a non-standard way, but it is more likely that it indicates an internal error.
Recommended Action If this problem persists, investigate the peer.
713012
Error Message %PIX|ASA-3-713012: Unknown protocol (protocol). Not adding SA w/spi=SPI valueExplanation This message appears when an illegal or unsupported IPSec protocol has been received from the peer.
Recommended Action Check the ISAKMP Phase 2 configuration on peer(s) to make sure it is compatible with the security appliance.
713014
Error Message %PIX|ASA-3-713014: Unknown Domain of Interpretation (DOI): DOI valueExplanation This message appears when the ISAKMP Domain of Interpretation received from the peer is unsupported.
Recommended Action Check the ISAKMP DOI configuration on peer(s).
713016
Error Message %PIX|ASA-3-713016: Unknown identification type, Phase 1 or 2, Type ID_TypeExplanation This message indicates that the ID received from the peer is unknown. The ID could be an unfamiliar valid ID or an invalid or corrupted ID.
Recommended Action Check the configuration on headend and peer(s).
713017
Error Message %PIX|ASA-3-713017: Identification type not supported, Phase 1 or 2, Type ID_TypeExplanation This message indicates that 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(s).
713018
Error Message %PIX|ASA-3-713018: Unknown ID type during find of group name for certs, Type ID_TypeExplanation This message indicates that an internal software error has occurred.
Recommended Action If the problem persists, contact the Cisco TAC.
713020
Error Message %PIX|ASA-3-713020: No Group found by matching OU(s) from ID payload: OU_valueExplanation This message indicates that an internal software error has occurred.
Recommended Action If the problem persists, contact the Cisco TAC.
713022
Error Message %PIX|ASA-3-713022: No Group found matching peer_ID or IP_address for Pre-shared key peer IP_addressExplanation This message indicates that there was no group 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 %PIX|ASA-7-713024: Received local Proxy Host data in ID Payload: Address IP_address, Protocol protocol, Port portExplanation This message indicates that the security appliance has received the Phase 2 local proxy ID payload from the remote peer.
Recommended Action None required.
713025
Error Message %PIX|ASA-7-713025: Received remote Proxy Host data in ID Payload: Address IP_address, Protocol protocol, Port portExplanation This message indicates that the security appliance has received the Phase 2 local proxy ID payload from the remote peer.
Recommended Action None required.
713026
Error Message %PIX|ASA-7-713026: Transmitted local Proxy Host data in ID Payload: Address IP_address, Protocol protocol, Port portExplanation This message indicates that the security appliance has transmitted the Phase 2 local proxy ID payload.
Recommended Action None required.
713027
Error Message %PIX|ASA-7-713027: Transmitted remote Proxy Host data in ID Payload: Address IP_address, Protocol protocol, Port portExplanation This message indicates that the security appliance has transmitted the Phase 2 remote proxy ID payload.
Recommended Action None required.
713028
Error Message %PIX|ASA-7-713028: Received local Proxy Range data in ID Payload: Addresses IP_address - IP_address, Protocol protocol, Port portExplanation This message indicates that the security appliance has received the Phase 2 local proxy ID payload of the remote peer which contains an IP address range.
Recommended Action None required.
713029
Error Message %PIX|ASA-7-713029: Received remote Proxy Range data in ID Payload: Addresses IP_address - IP_address, Protocol protocol, Port portExplanation This message indicates that the security appliance has received the Phase 2 local proxy ID payload of the remote peer which contains an IP address range.
Recommended Action None required.
713030
Error Message %PIX|ASA-7-713030: Transmitted local Proxy Range data in ID Payload: Addresses IP_address - IP_address, Protocol protocol, Port portExplanation This message indicates that the security appliance has transmitted the Phase 2 local proxy ID payload.
Recommended Action None required.
713031
Error Message %PIX|ASA-7-713031: Transmitted remote Proxy Range data in ID Payload: Addresses IP_address - IP_address, Protocol protocol, Port portExplanation This message indicates that the security appliance has transmitted the Phase 2 remote proxy ID payload.
Recommended Action None required.
713032
Error Message %PIX|ASA-3-713032: Received invalid local Proxy Range IP_address - IP_addressExplanation This message appears when the local ID payload contained the range ID type and the specified low address was not less than the high address. This may indicate a configuration problem.
Recommended Action Check the configuration of ISAKMP Phase 2 parameters.
713033
Error Message %PIX|ASA-3-713033: Received invalid remote Proxy Range IP_address - IP_addressExplanation This message appears when the remote ID payload contained the range ID type and the specified low address was not less than the high address. This may indicate a configuration problem.
Recommended Action Check the configuration of ISAKMP Phase 2 parameters.
713034
Error Message %PIX|ASA-7-713034: Received local IP Proxy Subnet data in ID Payload: Address IP_address, Mask netmask, Protocol protocol, Port portExplanation This message appears when the local IP Proxy Subnet data has been received in the Phase 2 ID Payload.
Recommended Action None required.
713035
Error Message %PIX|ASA-7-713035: Received remote IP Proxy Subnet data in ID Payload: Address IP_address, Mask netmask, Protocol protocol, Port portExplanation This message appears when the remote IP Proxy Subnet data has been received in the Phase 2 ID Payload.
Recommended Action None required.
713036
Error Message %PIX|ASA-7-713036: Transmitted local IP Proxy Subnet data in ID Payload: Address IP_address, Mask netmask, Protocol protocol, Port portExplanation This message appears when the local IP Proxy Subnet data in has been transferred in the Phase 2 ID Payload.
Recommended Action None required.
713037
Error Message %PIX|ASA-7-713037: Transmitted remote IP Proxy Subnet data in ID Payload: Address IP_address, Mask netmask, Protocol protocol, Port portExplanation This message appears when the remote IP Proxy Subnet data has been transferred in the Phase 2 ID Payload.
Recommended Action None required.
713039
Error Message %PIX|ASA-7-713039: Send failure: Bytes (number), Peer: IP_addressExplanation This message appears when an internal software error has occurred and the ISAKMP packet could not be transmitted.
Recommended Action If the problem persists, contact the Cisco TAC.
713040
Error Message %PIX|ASA-7-713040: Could not find connection entry and can not encrypt: msgid message_numberExplanation This message indicates that an internal software error has occurred and a Phase 2 data structure could not be found.
Recommended Action If the problem persists, contact the Cisco TAC.
713041
Error Message %PIX|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 This message indicates that the security appliance is negotiating a tunnel as the initiator.
Recommended Action None required.
713042
Error Message %PIX|ASA-3-713042: IKE Initiator unable to find policy: Intf interface_number, Src: source_address, Dst: dest_addressExplanation This message indicates that the IPSec fast path processed a packet that triggered IKE, but IKE's policy lookup failed. This error could 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.
Explanation If the condition persists, check the L2L configuration, paying special attention to the type of ACL associated with crypto maps.
713043
Error Message %PIX|ASA-3-713043: Cookie/peer address IP_address session already in progressExplanation This message indicates that IKE has been triggered again while the original tunnel is in progress.
Recommended Action None required.
713048
Error Message %PIX|ASA-3-713048: Error processing payload: Payload ID: idExplanation This message indicates that a packet has been received with a payload we could not process.
Recommended Action If this problem persists, there might be a misconfiguration on the peer.
713049
Error Message %PIX|ASA-5-713049: Security negotiation complete for tunnel_type type (group_name) Initiator/Responder, Inbound SPI = SPI, Outbound SPI = SPIExplanation This message indicates the start of an IPSec tunnel.
Recommended Action None required.
713050
Error Message %PIX|ASA-5-713050: Connection terminated for peer IP_address. Reason: termination reason Remote Proxy IP_address, Local Proxy IP_addressExplanation This message indicates the termination of an IPSec tunnel. Possible termination reasons include:
•
•
•
•
•
•
•
•
Recommended Action None required.
713051
Error Message %PIX|ASA-3-713051: Terminating connection attempt: IPSEC not permitted for group (group_name)Explanation This message indicates that the user, group, or interface policy is rejecting IPSec tunnels.
Recommended Action To use IPSec select the appropriate tunneling protocol in the policy.
713052
Error Message %PIX|ASA-7-713052: User (user) authenticated.Explanation This message indicates that the remote access user was authenticated.
Recommended Action None required.
713056
Error Message %PIX|ASA-3-713056: Tunnel rejected: SA (SA_name) not found for group (group_name)!Explanation This message indicates that 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 has been configured for the specific user group. For externally authenticated users and groups, check the returned authentication attributes.
713059
Error Message %PIX|ASA-3-713059: Tunnel Rejected: User (user) matched with group name, group-lock check failed.Explanation This message indicates that the user tried to authenticate by using the same string for both the tunnel group and username.
Recommended Action The group and username must be different for the user to be authenticated.
713060
Error Message %PIX|ASA-3-713060: Tunnel Rejected: User (user) not member of group (group_name), group-lock check failed.Explanation This message indicates that 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 security appliance. If using digital certificates, the group is dictated either by the OU field of the certificate or the user will default to the remote access default group.
713061
Error Message %PIX|ASA-3-713061: Tunnel rejected: Crypto Map Policy not found for Src:source_address, Dst: dest_address!Explanation This message indicates that the security appliance 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 security appliance. 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, host addresses versus network addresses, and so on. Non-Cisco implementations may have the private addresses labeled as proxy addresses or red networks.
713062
Error Message %PIX|ASA-3-713062: IKE Peer address same as our interface address IP_addressExplanation The IP address configured as the IKE peer is the same as the IP address configured on one of the security appliance IP interfaces.
Recommended Action Check the L2L configuration and configuration of IP interface(s).
713063
Error Message %PIX|ASA-3-713063: IKE Peer address not configured for destination IP_addressExplanation This message appears when the IKE peer address is not configured for a L2L tunnel.
Recommended Action Check the L2L configuration.
713065
Error Message %PIX|ASA-3-713065: IKE Remote Peer did not negotiate the following: proposal attributeExplanation This message indicates that an internal software error has occurred.
Recommended Action If the problem persists, contact the Cisco TAC.
713066
Error Message %PIX|ASA-7-713066: IKE Remote Peer configured for SA: SA_nameExplanation This message indicates the crypto policy settings of the peer.
Recommended Action None required.
713068
Error Message %PIX|ASA-5-713068: Received non-routine Notify message: notify_type (notify_value)Explanation This message indicates that notification messages that cause this event are not explicitly handled in the notify processing code.
Recommended Action Examine the specific reason information to determine the action to take. Many notification messages indicate a configuration mismatch between the IKE peers.
713072
Error Message %PIX|ASA-3-713072: Password for user (user) too long, truncating to number charactersExplanation This message indicates that the password of the user is too long.
Recommended Action Correct password lengths on the authentication server.
713073
Error Message %PIX|ASA-5-713073: Responder forcing change of Phase 1/Phase 2 rekeying duration from larger_value to smaller_value secondsExplanation Rekeying durations are always set to the lower of the values proposed by IKE peers. This message indicates that the value of the initiator is the lower one.
Recommended Action None required.
713074
Error Message %PIX|ASA-5-713074: Responder forcing change of IPSec rekeying duration from larger_value to smaller_value KbsExplanation Rekeying durations are always set to the lower of the values proposed by IKE peers. This message indicates that the value of the initiator is the lower one.
Recommended Action None required.
713075
Error Message %PIX|ASA-5-713075: Overriding Initiator's IPSec rekeying duration from larger_value to smaller_value secondsExplanation Rekeying durations are always set to the lower of the values proposed by IKE peers. This message indicates that the value of the responder is the lower one.
Recommended Action None required.
713076
Error Message %PIX|ASA-5-713076: Overriding Initiator's IPSec rekeying duration from larger_value to smaller_value KbsExplanation Rekeying durations are always set to the lower of the values proposed by IKE peers. This message indicates that the value of the responder is the lower one.
Recommended Action None required.
713078
Error Message %PIX|ASA-2-713078: Temp buffer for building mode config attributes exceeded: bufsize available_size, used valueExplanation This message indicates that 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 %PIX|ASA-3-713081: Unsupported certificate encoding type encoding_typeExplanation This message indicates that one of the loaded certificates is unreadable, and could be an unsupported encoding scheme.
Recommended Action Check the configuration of digital certificates and trustpoints.
713082
Error Message %PIX|ASA-3-713082: Failed to retrieve identity certificateExplanation Could not find the Identity Certificate for this tunnel.
Recommended Action Check the configuration of digital certificates and trustpoints.
713083
Error Message %PIX|ASA-3-713083: Invalid certificate handleExplanation This message indicates that the identity certificate for this tunnel could not be found.
Recommended Action Check the configuration of digital certificates and trustpoints.
713084
Error Message %PIX|ASA-3-713084: Received invalid phase 1 port value (port) in ID payloadExplanation This message indicates that the port value received in the IKE phase 1 ID payload was incorrect. Acceptable values are 0 or 500 (ISAKMP aka IKE).
Recommended Action This may indicate a peer that does not conform to the IKE standards or a network problem that results in corrupted packets.
713085
Error Message %PIX|ASA-3-713085: Received invalid phase 1 protocol (protocol) in ID payloadExplanation This message indicates that the protocol value received in the IKE phase 1 ID payload was incorrect. Acceptable values are 0 or 17 (UDP).
Recommended Action This may indicate a peer that does not conform to the IKE standards or a network problem that results in corrupted packets.
713086
Error Message %PIX|ASA-3-713086: Received unexpected Certificate payload Possible invalid Auth Method (Auth method (auth numerical value))Explanation This message appears when a cert payload was received but our internal cert handle indicates that we do not have an identity cert. This could mean that the cert handle was not obtained through a normal enrollment method. One likely reason this can happen is that the authentication method is not 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 appliance and peer.
713088
Error Message %PIX|ASA-3-713088: Set Cert filehandle failure: no IPSec SA in group group_nameExplanation This message indicates that the tunnel group could not be found based on the digital certificate information.
Recommended Action Verify that the tunnel group is set up appropriately to handle the certificate information of the peer.
713092
Error Message %PIX|ASA-5-713092: Failure during phase 1 rekeying attempt due to collisionExplanation This message indicates that an internal software error has occurred.
Recommended Action This is often a benign event. If the problem persists, contact the Cisco TAC.
713094
Error Message %PIX|ASA-7-713094: Cert validation failure: handle invalid for Main/Aggressive Mode Initiator/Responder!Explanation This message indicates that 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 %PIX|ASA-3-713098: Aborting: No identity cert specified in IPSec SA (SA_name)!Explanation This message appears when an attempt is made to establish a Certs-based IKE session, but no identity certificate have been specified in the crypto policy.
Recommended Action Specify the identity certificate/trustpoint that you want to transmit to peers.
713099
Error Message %PIX|ASA-7-713099: Tunnel Rejected: Received NONCE length number is out of range!Explanation This message indicates that an internal software error has occurred.
Recommended Action If the problem persists, contact the Cisco TAC.
713102
Error Message %PIX|ASA-3-713102: Phase 1 ID Data length number too long - reject tunnel!Explanation This message indicates that IKE has received an ID payload containing an Identification Data field of size 2 K or greater.
Recommended Action None required.
713103
Error Message %PIX|ASA-7-713103: Invalid (NULL) secret key detected while computing hashExplanation This message indicates that an internal software error has occurred.
Recommended Action If the problem persists, contact the Cisco TAC.
713104
Error Message %PIX|ASA-7-713104: Attempt to get Phase 1 ID data failed while hash computationExplanation This message indicates that an internal software error has occurred.
Recommended Action If the problem persists, contact the Cisco TAC.
713105
Error Message %PIX|ASA-3-713105: Zero length data in ID payload received during phase 1 or 2 processingExplanation This message indicates that 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 %PIX|ASA-3-713107: IP_Address request attempt failed!Explanation This message indicates that an internal software error has occurred.
Recommended Action If the problem persists, contact the Cisco TAC.
713109
Error Message %PIX|ASA-3-713109: Unable to process the received peer certificateExplanation This message indicates that the security appliance was unable to process the certificate received from the remote peer. This can occur if the certificate data was malformed or if the data in the certificate could not be stored by the appliance. One such possibility is if the public key size is larger than 4096 bits.
Recommended Action Try to reestablish the connection using a different certificate on the remote peer.
713112
Error Message %PIX|ASA-3-713112: Failed to process CONNECTED notify (SPI SPI_value)!Explanation This message indicates that the security appliance was unable to successfully process the notify payload that contained notify type CONNECTED. This could occur if the IKE phase 2 structure could not be found using the SPI to locate it, or the commit bit had not been set in the received ISAKMP header. This later case could indicate a non-conforming IKE peer.
Recommended Action If the problem persists, check the configuration of the peer and/or disable commit bit processing.
713113
Error Message %PIX|ASA-7-713113: Deleting IKE SA with associated IPSec connection entries. IKE peer: IP_address, SA address: internal_SA_address, tunnel count: countExplanation This message indicates that an IKE SA is being deleted with a non-0 tunnel count. This 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 that the connection entry points to. If this occurs, the IKE SA and its associated data structures will not be freed, so that the entries which may point to it will not have a stale pointer.
Recommended Action None required. Error recovery is built-in.
713114
Error Message %PIX|ASA-7-713114: Connection entry (conn entry internal address) points to IKE SA (SA_internal_address) for peer IP_address, but cookies don't matchExplanation This message indicates that an internal software error has occurred.
Recommended Action If the problem persists, contact the Cisco TAC.
713115
Error Message %PIX|ASA-5-713115: Client rejected NAT enabled IPSec request, falling back to standard IPSecExplanation This message indicates the client rejected an attempt by the security appliance to use IPSec over UDP. IPSec over UDP is used to allow multiple clients to establish simultaneous tunnels to the security appliance through a NAT device. The client may have rejected the request either because it does not support this feature or because it is configured to not use it.
Recommended Action Verify the configuration on the headend and peer.
713116
Error Message %PIX|ASA-3-713116: Terminating connection attempt: L2TP-over-IPSEC attempted by group (group_name) but L2TP disabledExplanation This message indicates that the user or group entity has attempted an L2TP-over-IPSec connection, but the L2TP protocol is not enabled for this security appliance.
Recommended Action Verify the L2TP configuration.
713117
Error Message %PIX|ASA-7-713117: Received Invalid SPI notify (SPI SPI_Value)!Explanation This message indicates the IPSec SA identified by the SPI value is no longer active on the remote peer. This 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 a manual reestablishment of the affected tunnel.
713118
Error Message %PIX|ASA-3-713118: Detected invalid Diffie-Helmann group_descriptor group_number, in IKE areaExplanation This message indicates that the group_descriptor field contains 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 (PFS) is disabled.
Recommended Action Check the peer Diffie-Hellman configuration.
713119
Error Message %PIX|ASA-5-713119: PHASE 1 COMPLETEDExplanation This message appears when IKE Phase 1 has completed successfully.
Recommended Action None required.
713120
Error Message %PIX|ASA-5-713120: PHASE 2 COMPLETED (msgid=msg_id)Explanation This message appears when IKE Phase 2 has completed successfully.
Recommended Action None required.
713121
Error Message %PIX|ASA-7-713121: Keep-alive type for this connection: keepalive_typeExplanation This message indicates the type of keep-alive mechanism being used for this tunnel.
Recommended Action None required.
713122
Error Message %PIX|ASA-3-713122: Keep-alives configured keepalive_type but peer IP_address support keep-alives (type = keepalive_type)Explanation This message indicates that keep-alives are configured on/off for this device, but the IKE peer does/does not support keep-alives.
Recommended Action This requires no action if this is intentional. If it is not intentional, change the keepalive configuration on both devices.
713123
Error Message %PIX|ASA-3-713123: IKE lost contact with remote peer, deleting connection (keepalive type: keepalive_type)Explanation This message indicates that the remote IKE peer did not respond to keep-alives within the expected window of time, so the connection to the IKE peer was terminated. The message includes the keep-alive mechanism used.
Recommended Action None required.
713124
Error Message %PIX|ASA-3-713124: Received DPD sequence number rcv_sequence_# in DPD Action, description expected seq #Explanation This message indicates that the remote IKE peer sent a DPD with a sequence number that did not match the expected sequence number. The packet is discarded.
Recommended Action This might indicate a packet loss problem with the network.
713127
Error Message %PIX|ASA-3-713127: Xauth required but selected Proposal does not support xauth, Check priorities of ike xauth proposals in ike proposal listExplanation This message appears when the peer wants to perform a XAUTH but the security appliance did not choose the XAUTH IKE proposal.
Recommended Action Check the priorities of the IKE xauth proposals in IKE proposal list.
713128
Error Message %PIX|ASA-6-713128: Connection attempt to VCPIP redirected to VCA peer IP_address via load balancingExplanation This message appears when 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 %PIX|ASA-3-713129: Received unexpected Transaction Exchange payload type: payload_idExplanation This message indicates that an unexpected payload has been received during XAUTH or Mode-cfg. This may indicate that the two peers are out of synchronization, that the XAUTH or Mode-cfg versions do not match, or that the remote peer is not complying to the appropriate RFCs.
Recommended Action Verify the configuration between peers.
713130
Error Message %PIX|ASA-5-713130: Received unsupported transaction mode attribute: attribute idExplanation This message indicates that 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.
713131
Error Message %PIX|ASA-5-713131: Received unknown transaction mode attribute: attribute_idExplanation This message indicates that the security appliance 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 config 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 %PIX|ASA-3-713132: Cannot obtain an IP_address for remote peerExplanation This message indicates that a request for an IP address for a remote access client from the internal utility that provides these addresses could not be satisfied.
Recommended Action Check configuration of IP address assignment methods.
713133
Error Message %PIX|ASA-3-713133: Mismatch: Overriding phase 2 DH Group(DH group DH group_id) with phase 1 group(DH group DH group_numberExplanation The configured Phase 2 PFS Group differs from the DH group that was negotiated for phase 1.
Recommended Action None required.
713134
Error Message %PIX|ASA-3-713134: Mismatch: P1 Authentication algorithm in the crypto map entry different from negotiated algorithm for the L2L connectionExplanation This message appears when 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.
Recommended Action None required.
713135
Error Message %PIX|ASA-5-713135: message received, redirecting tunnel to IP_address.Explanation This message indicates that the tunnel is being redirected due to load balancing on the remote security appliance. This message will be seen when a REDIRECT_CONNECTION notify packet is received.
Recommended Action None required.
713136
Error Message %PIX|ASA-5-713136: IKE session establishment timed out [IKE_state_name], aborting!Explanation This occurs when the reaper has detected an SA stuck in a non-active state. The reaper will try to remove the hung SA.
Recommended Action None required.
713137
Error Message %PIX|ASA-5-713137: Reaper overriding refCnt [ref_count] and tunnelCnt [tunnel_count] -- deleting SA!Explanation This message indicates that an internal software error has occurred.
Recommended Action If the problem persists, contact the Cisco TAC.
713138
Error Message %PIX|ASA-3-713138: Group group_name not found and BASE GROUP default preshared key not configuredExplanation This message appears when there is no group in the group database with the same name as the IP address of the peer. In Main Mode, the security appliance 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.
713139
Error Message %PIX|ASA-5-713139: group_name not found, using BASE GROUP default preshared keyExplanation There was no tunnel group in the group database with the same name as the IP address of the peer. In Main Mode, the security appliance will fall back and use the default preshared key configured in the default group.
Recommended Action None required.
713140
Error Message %PIX|ASA-3-713140: Split Tunneling Policy requires network list but none configuredExplanation This message appears when split tunneling policy is set to either split tunneling or 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 %PIX|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_valueExplanation This message indicates that the security appliance installed on the client does not match the configured required security appliance. 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 security appliance on the client or a change of configuration on the security appliance.
713142
Error Message %PIX|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_valueExplanation This message appears when the client did not report a security appliance 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 security appliance on the client or a change of configuration on the security appliance.
713143
Error Message %PIX|ASA-7-713143: Processing firewall record. Vendor: vendor(id), Product: product(id), Caps: capability_value, Version Number: version_number, Version String: version_textExplanation This message provides debug information about the security appliance installed on the client.
Recommended Action None required.
713144
Error Message %PIX|ASA-5-713144: Ignoring received malformed firewall record; reason - error_reason TLV type attribute_value correctionExplanation This message indicates that bad security appliance information was received from the client.
Recommended Action Check the personal security appliance configuration on the client and the security appliance.
713145
Error Message %PIX|ASA-6-713145: Detected Hardware Client in network extension mode, adding static route for address: IP_address, mask: netmaskExplanation This message indicates that 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 enables the security appliance to make the remote network known to all the routers on the private side of the head-end.
Recommended Action None required.
713146
Error Message %PIX|ASA-3-713146: Could not add route for Hardware Client in network extension mode, address: IP_address, mask: netmaskExplanation This message indicates that 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. This could indicate that the routing table is full or a possible addressing error.
Recommended Action If the problem persists, contact the Cisco TAC.
713147
Error Message %PIX|ASA-6-713147: Terminating tunnel to Hardware Client in network extension mode, deleting static route for address: IP_address, mask: netmaskExplanation This message indicates that 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 %PIX|ASA-5-713148: Terminating tunnel to Hardware Client in network extension mode, unable to delete static route for address: IP_address, mask: netmaskExplanation This message indicates that while a tunnel to a hardware client in network extension mode was being removed, a route to the private network behind the hardware client could not be deleted.
Recommended Action This might indicate an addressing or software problem. 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 %PIX|ASA-3-713149: Hardware client security attribute attribute_name was enabled but not requested.Explanation This message indicates that the headend security appliance 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 %PIX|ASA-3-713152: Unable to obtain any rules from filter ACL_tag to send to client for CPP, terminating connection.Explanation This message indicates that the client is required to use CPP to provision its security appliance, 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.
713154
Error Message %PIX|ASA-4-713154: DNS lookup for peer_description Server [server_name] failed!Explanation This message appears when DNS lookup for the specified server has not been resolved.
Recommended Action Check DNS server configuration on the security appliance. Also check the DNS server to ensure that it is operational and has the hostname to IP address mapping.
713155
Error Message %PIX|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 system 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 %PIX|ASA-5-713156: Initializing Backup Server [server_name or IP_address]Explanation This message indicates that the client is failing over to a backup server or a failed DNS lookup for the primary server caused the system 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 %PIX|ASA-4-713157: Timed out on initial contact to server [server_name or IP_address] Tunnel could not be established.Explanation This message indicates that the client tried to initiate a tunnel by sending out IKE MSG1, but did not receive a response from the security appliance 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 security appliance.
713158
Error Message %PIX|ASA-5-713158: Client rejected NAT enabled IPSec Over UDP request, falling back to IPSec Over TCPExplanation This message indicates that the client is configured to use IPSec over TCP. The client rejected the attempt by the security appliance to use IPSec over UDP.
Recommended Action If TCP is desired, no action is required. Otherwise, check the client configuration.
713159
Error Message %PIX|ASA-3-713159: TCP Connection to Firewall Server has been lost, restricted tunnels are now allowed full network accessExplanation This message indicates that the TCP connection to the security appliance server was lost for some reason. Likely reasons are that the server has rebooted, has a network problem, has an SSL mismatch, and so on.
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 could indicate an SSL authentication problem.
713160
Error Message %PIX|ASA-7-713160: Remote user (session Id - id) has been granted access by the Firewall ServerExplanation This message indicates normal authentication of the remote user to the security appliance server.
Recommended Action None required.
713161
Error Message %PIX|ASA-3-713161: Remote user (session Id - id) network access has been restricted by the Firewall ServerExplanation The security appliance server has sent the security appliance a message indicating that this user must be restricted. There are several reasons for this including security appliance software upgrades, changes in permissions, and so on. The security appliance 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 security appliance server for more information on the operation that is being performed and the state of the security appliance software running on the remote machine.
713162
Error Message %PIX|ASA-3-713162: Remote user (session Id - id) has been rejected by the Firewall ServerExplanation This message indicates that the security appliance server has rejected this user.
Recommended Action Check the policy information on the security appliance server to make sure that the user is configured correctly.
713163
Error Message %PIX|ASA-3-713163: Remote user (session Id - id) has been terminated by the Firewall ServerExplanation This message indicates that the security appliance server has terminated this user session. This can happen 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 security appliance software on the client machine is still running and that the policy is correct.
713164
Error Message %PIX|ASA-7-713164: The Firewall Server has requested a list of active user sessionsExplanation This message indicates that the security appliance server will request the session information if it detects that it has stale data or if it loses the session data (as in a reboot).
Recommended Action None required.
713165
Error Message %PIX|ASA-3-713165: Client IKE Auth mode differs from the group's configured Auth modeExplanation This message indicates that 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.
713166
Error Message %PIX|ASA-3-713166: Headend security gateway has failed our user authentication attempt - check configured username and passwordExplanation This message indicates that the hardware client has failed extended authentication. This is most likely a username/password problem or 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 %PIX|ASA-3-713167: Remote peer has failed user authentication - check configured username and passwordExplanation This message indicates that the remote user has failed to extend authentication. This is most likely a username or password problem or 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 is operational.
713168
Error Message %PIX|ASA-3-713168: Re-auth enabled, but tunnel must be authenticated interactively!Explanation This message indicates that reauthentication on rekey 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 %PIX|ASA-7-713169: IKE Received delete for rekeyed SA IKE peer: IP_address, SA address: internal_SA_address, tunnelCnt: tunnel_countExplanation This message indicates that 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.
713170
Error Message %PIX|ASA-7-713170: IKE Received delete for rekeyed centry IKE peer: IP_address, centry address: internal_address, msgid: idExplanation IKE receives a delete message from the remote peer to delete its old centry after phase 2 rekeying is completed.
Recommended Action None required.
713171
Error Message %PIX|ASA-7-713171: NAT-Traversal sending NAT-Original-Address payloadExplanation UDP-Encapsulated-Transport was either proposed or selected during phase 2. Need to send this payload for NAT-Traversal in this case.
Recommended Action None required.
713172
Error Message %PIX|ASA-6-713172: Automatic NAT Detection Status: Remote end is|is not behind a NAT device This end is|is_not behind a NAT deviceExplanation Results from NAT auto-detection by NAT-Traversal.
Recommended Action None required.
713174
Error Message %PIX|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 configuration of network extension mode versus PAT mode.
713176
Error Message %PIX|ASA-2-713176: Device_type memory resources are critical, IKE key acquire message on interface interface_number, for Peer IP_address ignoredExplanation This event indicates that the appliance 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 appliance is efficiently configured. This event could indicate that an appliance with increased memory is required for this application.
713177
Error Message %PIX|ASA-6-713177: Received remote Proxy Host FQDN in ID Payload: Host Name: host_name Address IP_address, Protocol protocol, Port portExplanation A Phase 2 ID payload containing an FQDN has been received from the peer.
Recommended Action None required.
713178
Error Message %PIX|ASA-5-713178: IKE Initiator received a packet from its peer without a Responder cookieExplanation An internal software error has occurred.
Recommended Action If the problem persists, contact the Cisco TAC.
713179
Error Message %PIX|ASA-5-713179: IKE AM Initiator received a packet from its peer without a payload_type payloadExplanation An internal software error has occurred.
Recommended Action If the problem persists, contact the Cisco TAC.
713182
Error Message %PIX|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 %PIX|ASA-6-713184: Client Type: Client_type Client Application Version: Application_version_stringExplanation This event indicates the client operating system and application version. If the information is not available, then N/A will be indicated.
Recommended Action None required.
713185
Error Message %PIX|ASA-3-713185: Error: Username too long - connection abortedExplanation 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 %PIX|ASA-3-713186: Invalid secondary domain name list received from the authentication server. List Received: list_text Character index (value) is illegalExplanation 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 not include any characters other than alpha-numerics, hyphen, underscore and period.
713187
Error Message %PIX|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_addressExplanation 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(s).
Recommended Action Verify proper L2L settings on headend and peer.
713189
Error Message %PIX|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 %PIX|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 This issue should correct itself.
713193
Error Message %PIX|ASA-3-713193: Received packet with missing payload, Expected payload: payload_idExplanation The Appliance received an encrypted/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 peer is sending valid IKE messages.
713194
Error Message %PIX|ASA-3-713194: IKE|IPSec Delete With Reason message: termination_reasonExplanation Indicates that a delete message with a termination reason code was received.
Recommended Action None required.
713195
Error Message %PIX|ASA-3-713195: Tunnel rejected: Originate-Only: Cannot accept incoming tunnel yet!Explanation 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 revisited.
713196
Error Message %PIX|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.
713197
Error Message %PIX|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 %PIX|ASA-3-713198: User Authorization failed: user User authorization failed.Explanation This event will contain a reason string.
Recommended Action Check group configuration and client authorization.
713199
Error Message %PIX|ASA-5-713199: Reaper corrected an SA that has not decremented the concurrent IKE negotiations counter (counter_value)!Explanation Reaper corrected an internal software error.
Recommended Action If the problem persists, contact the Cisco TAC.
713201
Error Message %PIX-5-713201: Duplicate (Phase 1/Phase 2) packet detected.(Retransmitting test packet/No last packet to retransmit.)Explanation This message is displayed when a duplicate IKE Phase 1 or IKE Phase 2 message is received. A duplicate message indicates that the peer did not receive the response to the message, because it was either dropped somewhere in the network, it was dropped by the peer because the message was in error, or it was never sent because the original message was in error.
Recommended Action If this event is transient, then you can ignore it because it will not result in tunnel drops or tunnel errors. If the event persists and it is associated with tunnel failures, then you should take the following action:
Review other events associated with this IKE session to determine whether one of the peers is misconfigured. A misconfiguration could result in messages being dropped by one or both peers. If a misconfiguration has not caused the error, then you may require a network analyzer to determine where the message is being dropped.
713203
Error Message %PIX|ASA-3-713203: IKE Receiver: Error reading from socket.Explanation This message indicates that there was an error 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.
713204
Error Message %PIX|ASA-7-713204: Adding static route for client address: IP_addressExplanation 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.
Recommended Action None required.
713205
Error Message %PIX|ASA-3-713205: Could not add static route for client address: IP_addressExplanation This message indicates a failed attempt to add a route to the client-assigned address or to the networks protected by a hardware client. This could indicate duplicate routes in the routing table or a corrupted network address. The duplicate routes could be caused by routes not cleaned up properly 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). Ensure that routes are being cleared from the routing table. Also check the configuration of networks and/or addresses on the peer system.
713206
Error Message %PIX|ASA-3-713206: Tunnel Rejected: Conflicting protocols specified by tunnel-group and group-policyExplanation This message appears when a tunnel is dropped because the allowed tunnel specified in the group policy is different than the allowed tunnel in the tunnel-group configuration.
Recommended Action Check the tunnel-group and group-policy configuration.
713208
Error Message %PIX|ASA-3-713208: Cannot create dynamic rule for Backup L2L entry rule rule_idExplanation This message indicates that there was a failure in creating the ACLs that trigger IKE and allow IPSec data to be processed properly. The failure was specific to the Backup L2L configuration. This may indicate a configuration error, a capacity error or an internal software error.
Recommended Action If the device is running at maximum security appliance cons and maximum VPN tunnels, there may be a memory issue. If not, check the backup L2L and crypto map configuration, specifically the ACLs associated with the crypto maps.
713209
Error Message %PIX|ASA-3-713209: Cannot delete dynamic rule for Backup L2L entry rule idExplanation This message indicates that there was a failure in deleting the ACLs that trigger IKE and allow IPSec data to be processed properly. 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 %PIX|ASA-3-713210: Cannot create dynamic map for Backup L2L entry rule_idExplanation This message indicates that there was a failure 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 device is running at maximum security appliance cons and maximum VPN tunnels, there may be a memory issue. If not, check the backup L2L and crypto map configuration, specifically the ACLs associated with the crypto maps.
713211
Error Message %PIX|ASA-6-713211: Adding static route for L2L peer coming in on a dynamic map. address: IP_address, mask: netmaskExplanation This message indicates that the security appliance 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 %PIX|ASA-3-713212: Could not add route for L2L peer coming in on a dynamic map. address: IP_address, mask: netmaskExplanation This message appears when the security appliance 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 could indicate duplicate routes. A full routing table or a failure of the security appliance 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 contains obsolete routes, remove the routes and try again. If the problem persists, contact the Cisco TAC.
713213
Error Message %PIX|ASA-6-713213: Deleting static route for L2L peer that came in on a dynamic map. address: IP_address, mask: netmaskExplanation This message indicates that the security appliance 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.
Recommended Action None required.
713214
Error Message %PIX|ASA-3-713214: Could not delete route for L2L peer that came in on a dynamic map. address: IP_address, mask: netmaskExplanation This message indicates that the security appliance 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. This event may indicate that the route has already been deleted or that 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 %PIX|ASA-6-713215: No match against Client Type and Version rules. Client: type version is/is not allowed by defaultExplanation This message indicates that the client type and the version of a client did not match any of the rules configured on the security appliance. The default action is displayed.
Recommended Action Determine what the default action and deployment requirements are and make the appropriate changes.
713216
Error Message %PIX|ASA-5-713216: Rule: action Client type: version Client: type version is/is not allowedExplanation This message indicates that the client type and the version of a client has matched one of the rules. The result of the match and the rule are displayed.
Recommended Action Determine what the deployment requirements are and make the appropriate changes.
713217
Error Message %PIX|ASA-3-713217: Skipping unrecognized rule: action: action client type: client_type client version: client_versionExplanation This message indicates that there is a malformed client type and version rule. 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 %PIX|ASA-3-713218: Tunnel Rejected: Client Type or Version not allowed.Explanation This message indicates that the client was rejected access per the configured rules.
Recommended Action None required.
713219
Error Message %PIX|ASA-6-713219: Queueing KEY-ACQUIRE messages to be processed when P1 SA is complete.Explanation This message indicates that Phase 2 messages are being enqueued after Phase 1 completes.
Recommended Action None required.
713220
Error Message %PIX|ASA-6-713220: De-queueing KEY-ACQUIRE messages that were left pending.Explanation This message indicates that queued Phase 2 messages are now being processed.
Recommended Action None required.
713221
Error Message %PIX|ASA-7-713221: Static Crypto Map check, checking map = crypto_map_tag, seq = seq_number...Explanation This message indicates that the security appliance is iterating through the crypto maps looking for configuration information.
Recommended Action None required.
713222
Error Message %PIX|ASA-7-713222: Static Crypto Map check, map = crypto_map_tag, seq = seq_number, ACL does not match proxy IDs src:source_address dst:dest_addressExplanation This message indicates that while iterating through the configured crypto maps, the security appliance could not 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 they specify the appropriate private networks from both sides of the VPN tunnel.
713223
Error Message %PIX|ASA-7-713223: Static Crypto Map check, map = crypto_map_tag, seq = seq_number, no ACL configuredExplanation This message indicates that the crypto map associated with this peer is not linked to an ACL.
Recommended Action Make sure there is an ACL associated with this crypto map and that the ACL contains the appropriate private addresses or network from both sides of the VPN tunnel.
713224
Error Message %PIX|ASA-7-713224: Static Crypto Map Check by-passed: Crypto map entry incomplete!Explanation This message indicates that 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 %PIX|ASA-7-713225: [IKEv1], Static Crypto Map check, map map_name, seq = sequence_number is a successful matchExplanation This message indicates that the security appliance found a valid matching crypto map for this VPN tunnel.
Recommended Action None required.
713226
Error Message %PIX|ASA-3-713226: Connection failed with peer IP_address, no trust-point defined in tunnel-group tunnel_groupExplanation When the device is configured to use digital certificates, a trust point must be specified in the configuration. When the trust point is missing from the config, this message is generated to flag an error.
•
•
Recommended Action The administrator of the device has to specify a trust point in the configuration.
713227
Error Message %PIX|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_netmaskExplanation When establishing a Phase 2 SA, the security appliance will reject a new Phase SA that matches this proxy.
Recommended Action None required. The security appliance should recover automatically.
713228
Error Message %PIX|ASA-6-713228: Group = group, Username = uname, IP = remote_IP_address Assigned private IP address assigned_private_IP to remote user•
•
•
•
Explanation This message is generated when IKE obtains an address for the client private IP address from DHCP or from the address pool. The message specifies the IP address assigned to the client.
Recommended Action None required.
713229
Error Message %PIX|ASA-5-713229: Auto Update - Notification to client client_ip of update string: message_string.Explanation This message is displayed when 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.
•
•
Recommended Action None required.
713230
Error Message %PIX|ASA-3-713230 Internal Error, ike_lock trying to lock bit that is already locked for type type•
Explanation This message is displayed due to an internal error, which is reporting that the IKE subsystem is attempting to lock memory that has already been locked. This indicates errors on semaphores used to protect memory violations for IKE SAs. This message does not indicate that anything is seriously wrong. However, an unexpected event has happened and steps are automatically being taken for recovery.
Recommended Action If the problem persists, contact the Cisco TAC.
713231
Error Message %PIX|ASA-3-713231 Internal Error, ike_lock trying to unlock bit that is not locked for type typeExplanation This message is displayed due to an internal error, which is reporting that the IKE subsystem is attempting to unlock memory that is not currently locked. This indicates errors on semaphores used to protect memory violations for IKE SAs. This message does not indicate that anything is seriously wrong. However, an unexpected event has happened and steps are automatically being taken for recovery.
•
Recommended Action If the problem persists, contact the Cisco TAC.
713232
Error Message %PIX|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 = valueExplanation This message displays all the IKE SA locks and is displayed when a possible error has been detected. This message reports errors on semaphores used to protect memory violations for IKE SAs.
•
•
Recommended Action If the problem persists, contact the Cisco TAC.
713233
Error Message %PIX|ASA-7-713233: (VPN-unit) Remote network (remote network) validated for network extension mode.Explanation This message is displayed when the remote network received during the Phase 2 negotiation is validated. This 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 HW client network (for example, configuring overlapping networks or the same network on multiple clients).
•
Recommended Action None required.
713234
Error Message %PIX|ASA-7-713234: (VPN-unit) Remote network (remote network) from network extension mode client mismatches AAA configuration (aaa network).Explanation This message is displayed when the remote network received during the Phase 2 negotiation does not match the framed-ip-address and framed-subnet-mask returned from the AAA server for this session.
•
•
Recommended Action Do one of the following:
•
•
713235
Error Message %PIX|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. This message is displayed if such an attempt is made due to an internal logic error. The packet never leaves the standby unit because of protective code. This message is mainly to facilitate debugging.
Recommended Action No action is required by the user. Developers should look into the condition causing the IKE packet to be sent from the standby unit.
713236
Error Message %PIX|ASA-7-713236: IKE_DECODE tx/rx Message (msgid=msgid) with payloads:payload1 (payload1_len) + payload2 (payload2_len)...total length: tlenExplanation This message is displayed when IKE sends or receives 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:
%PIX-7-713236: IKE_DECODE RECEIVED Message msgid=0) with payloads: HDR + HASH (8) + NOTIFY (11) + VENDOR (13) + VENDOR (13) + NONE (0)Recommended Action None required.
713237
Error Message %PIX|ASA-5-713237: ACL update (access_list) received during re-key re-authentication will not be applied to the tunnel.•
Explanation This message is displayed during the Phase 1 rekey of a remote access IPSec tunnel under the following conditions:
•
•
Under these conditions, the security appliance 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 %PIX|ASA-3-713238: Invalid source proxy address: 0.0.0.0! Check private address on remote clientExplanation 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 reachedExplanation An attempt to create a tunnel has occurred after the maximum number of tunnels allowed has been reached.
•
Recommended Action None required.
713240
Error Message %ASA-4-713240: Received DH key with bad length: received length=rlength expected length=elengthExplanation A Diffie-Hellman key with the incorrect length was received from the peer.
•
•
Recommended Action None required.
713241
Error Message %ASA-4-713241: IE Browser Proxy Method setting_number is InvalidExplanation 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" 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 security appliance has detected a request to start an IKE rekey for a tunnel configured to use Hybrid Xauth, but the rekey was not started. The security appliance will wait for the client to detect and initiate an IKE rekey.
Recommended Action None required.
713243
Error Message %ASA-4-713243: META-DATA Unable to find the requested certificateExplanation The IKE peer requested a certificate from the cert-req payload. However, no valid identity certificate was issued by the requested DN was found.
Recommended Action Perform the following steps:
1.
2.
3.
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.
Recommended Action If the problem persists, contact the Cisco TAC.
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/response user authentication process. The user authentication process cannot proceed and the VPN connection will not be established.
•
Recommended Action If the problem persists, contact the Cisco TAC.
713246
Error Message %ASA-4-713246: META-DATA Unknown Legacy Authentication Method(LAM) attribute type type received.Explanation The device received an unknown LAM attribute type, which should not cause connectivity problems but might affect the functionality of the peer.
•
Recommended Action None required.
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, 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.
Recommended Action None required.
713249
Error Message %ASA-4-713249: META-DATA Received unsupported authentication results: resultExplanation 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.
•
Recommended Action If the problem persists, contact the Cisco TAC.
713250
Error Message %ASA-5-713250: META-DATA Received unknown Internal Address attribute: attributeExplanation The device 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.
Recommended Action None required.
713251
Error Message %ASA-4-713251: META-DATA Received authentication failure messageExplanation The device received a notify message indicating 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 fail policy configured. If the fail policy is to reject the client connection, this syslog message is generated when a Zonelab Integrity Server is not connected to the security appliance at the time the client is connecting.
•
•
•
Recommended Action Check that the configurations on the concentrator and the Zonelab Integrity Server match. Then verify communication 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 fail policy configured. If the fail policy is to accept the client connection, and provides unrestricted network access, this syslog message is generated when a Zonelab Integrity Server is not connected to the security appliance at the time the client is connecting.
•
•
•
Recommended Action Check that the configurations on the security device and the Zonelab Integrity Server match, and verify communication between the security appliance and the Zonelab Integrity Server.
713254
Error Message %PIX|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-TExplanation You cannot use UDP port 4500 for IPSec/UDP connections, because it is reserved for IPSec/NAT-T connections. The CLI does not allow this configuration for local groups. This message should only occur for externally defined groups.
•
•
•
•
•
•
Recommended Action Change the IPSec/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.
•
•
Recommended Action Check the tunnel group and client configurations to make sure 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.
•
Recommended Action None required.
713257
Error Message %ASA-5-713257: Phase var1 failure: Mismatched attribute types for class var2: Rcv'd: var3 Cfg'd: var4Explanation This syslog will be seen on an ASA acting as the responder in a LAN-to-LAN connection. It indicates that the ASA crypto configuration does not match that of the initiator's. The syslog specifies during what phase the mismatch happened, and what attributes both the responder and the initiator had that were different.
•
•
•
•
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 This message appears when the adaptive security appliance 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.
•
•
•
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: reasonExplanation This message is generated when an ISAKMP session is torn down through session management.
•
•
•
•
- Port Preempted, because of simultaneous login
- Idle Timeout
- Max Time Exceeded
- Administrator Reset
Recommended Action None required.
713900
Error Message %PIX|ASA-7-713900:Descriptive_event_string.Explanation A message with several possible text strings that describes a serious event or failure. For example: The adaptive security appliance 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, this message may occur if 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 syslog, and then contact the Cisco TAC for further assistance.
713901
Error Message %PIX|ASA-7-713901:Descriptive_event_string.Explanation A message with several possible text strings that describes an error that has occurred. This may be the result of 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 to determine what caused the error. Check the isakmp and crypto map configuration on both peers.
713902
Error Message %PIX|ASA-3-713902 descriptive_event_stringExplanation This syslog message could have several possible text strings describing an error. This 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.
713903
Error Message %PIX|ASA-4-713903:descriptive_event_string.Explanation This syslog message with several possible text strings provides a warning. This may be the result of unexpected behavior of a peer (for example, a loss of connectivity).
For example: %ASA-4-713903: Group = IPSecGroup, IP = 70.172.17.23, Error: Unable to remove PeerTblEntry. This message occurs when an IPSec connection attempt fails (for example, in an authentication failure because of an incorrectly typed password or the inadvertent disconnection of an IPSec client).
Recommended Action Informational only.
713904
Error Message %PIX|ASA-5-713904:descriptive_event_string.Explanation This syslog message has several possible text strings that describe general status information for notification purposes. These messages are used to track events that have occurred.
Recommended Action None required.
713905
Error Message %PIX|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 %PIX|ASA-7-713906: descriptive_event_string.Explanation Debugging status information appears, which is used to track events that have occurred.
Recommended Action None required.
714001
Error Message %PIX|ASA-7-714001: description_of_event_or_packetExplanation A description of an IKE protocol event or packet.
Recommended Action Informational only.
714002
Error Message %PIX|ASA-7-714002: IKE Initiator starting QM: msg id = message_numberExplanation The security appliance has sent the first packet of the Quick mode exchange as the Phase 2 initiator.
Recommended Action Informational only.
714003
Error Message %PIX|ASA-7-714003: IKE Responder starting QM: msg id = message_numberExplanation The security appliance has received the first packet of the Quick mode exchange as the Phase 2 responder.
Recommended Action Informational only.
714004
Error Message %PIX|ASA-7-714004: IKE Initiator sending 1st QM pkt: msg id = message_numberExplanation Protocol decode of the first Quick Mode packet.
Recommended Action Informational only.
714005
Error Message %PIX|ASA-7-714005: IKE Responder sending 2nd QM pkt: msg id = message_numberExplanation Protocol decode of the second Quick Mode packet.
Recommended Action Informational only.
714006
Error Message %PIX|ASA-7-714006: IKE Initiator sending 3rd QM pkt: msg id = message_numberExplanation Protocol decode of the third Quick Mode packet.
Recommended Action Informational only.
714007
Error Message %PIX|ASA-7-714007: IKE Initiator sending Initial ContactExplanation The security appliance is building and sending the initial contact payload.
Recommended Action Informational only.
714011
Error Message %PIX|ASA-7-714011: Description of received ID valuesExplanation Received the displayed ID information during the negotiation.
Recommended Action Informational only.
715001
Error Message %PIX|ASA-7-715001: Descriptive statementExplanation This message provides a description of an event or problem encountered by the security appliance.
Recommended Action The action depends on the description.
715004
Error Message %PIX|ASA-7-715004: subroutine name() Q Send failure: RetCode (return_code)Explanation This message indicates that there was an internal error when attempting to put messages in a queue.
Recommended Action This is often a benign condition. If the problem persists, contact the Cisco TAC.
715005
Error Message %PIX|ASA-7-715005: subroutine name() Bad message code: Code (message_code)Explanation This message indicates that 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 %PIX|ASA-7-715006: IKE got SPI from key engine: SPI = SPI_valueExplanation This message indicates that the IKE subsystem received an SPI value from IPSec.
Recommended Action None required.
715007
Error Message %PIX|ASA-7-715007: IKE got a KEY_ADD msg for SA: SPI = SPI_valueExplanation This message indicates that 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 %PIX|ASA-7-715008: Could not delete SA SA_address, refCnt = number, caller = calling_subroutine_addressExplanation This message indicates that the calling subroutine could not delete the IPSec SA. This could 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 %PIX|ASA-7-715009: IKE Deleting SA: Remote Proxy IP_address, Local Proxy IP_addressExplanation This message indicates that SA is being deleted with the listed proxy addresses.
Recommended Action None required.
715013
Error Message %PIX|ASA-7-715013: Tunnel negotiation in progress for destination IP_address, discarding dataExplanation This message indicates that 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 %PIX|ASA-7-715019: IKEGetUserAttributes: Attribute name = nameExplanation This message displays the modecfg attribute name and value pair being processed by the security appliance.
Recommended Action None required.
715020
Error Message %PIX|ASA-7-715020: construct_cfg_set: Attribute name = nameExplanation This message displays the modecfg attribute name and value pair being transmitted by the security appliance.
Recommended Action None required.
715021
Error Message %PIX|ASA-7-715021: Delay Quick Mode processing, Cert/Trans Exch/RM DSID in progressExplanation This message indicates that quick mode processing is being delayed until all Phase 1 processing has been completed (transaction mode, and so on.).
Recommended Action None required.
715022
Error Message %PIX|ASA-7-715022: Resume Quick Mode processing, Cert/Trans Exch/RM DSID completedExplanation This message indicates that Phase 1 processing has completed and quick mode is being resumed.
Recommended Action None required.
715027
Error Message %PIX|ASA-7-715027: IPSec SA Proposal # chosen_proposal, Transform # chosen_transform acceptable Matches global IPSec SA entry # crypto_map_indexExplanation This message appears when 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 %PIX|ASA-7-715028: IKE SA Proposal # 1, Transform # chosen_transform acceptable Matches global IKE entry # crypto_map_indexExplanation This message appears when 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.
Recommended Action None required.
715033
Error Message %PIX|ASA-7-715033: Processing CONNECTED notify (MsgId message_number)Explanation This message indicates that the security appliance is processing a message containing a notify payload with notify type CONNECTED (16384). The CONNECTED notify 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.
715034
Error Message %PIX|ASA-7-715034: action IOS keep alive payload: proposal=time 1/time 2 sec.Explanation This message indicates that processing for sending/receiving a keepalive payload message is being performed.
Recommended Action None required.
715035
Error Message %PIX|ASA-7-715035: Starting IOS keepalive monitor: seconds sec.Explanation This message indicates that the keepalive timer will monitor for a variable number of seconds for keepalive messages.
Recommended Action None required.
715036
Error Message %PIX|ASA-7-715036: Sending keep-alive of type notify_type (seq number number)Explanation This message indicates that processing for sending a keepalive notify message is being performed.
Recommended Action None required.
715037
Error Message %PIX|ASA-7-715037: Unknown IOS Vendor ID version: major.minor.varianceExplanation This message indicates that we do not know the capabilities of this version of IOS.
Recommended Action There may be interoperability issues with features like IKE keepalives. If the problem persists, contact the Cisco TAC
715038
Error Message %PIX|ASA-7-715038: action Spoofing_information Vendor ID payload (version: major.minor.variance, capabilities: value)Explanation This message indicates that processing for the IOS Vendor ID payload has been performed. The message being performed could be Altiga spoofing IOS.
Recommended Action None required.
715039
Error Message %PIX|ASA-7-715039: Unexpected cleanup of tunnel table entry during SA delete.Explanation This message indicates that there was an entry in the IKE tunnel table that was never removed when the SA was freed. This indicates a bug in the state machine.
Recommended Action If the problem persists, contact the Cisco TAC.
715040
Error Message %PIX|ASA-7-715040: Deleting active auth handle during SA deletion: handle = internal_authentication_handleExplanation This message indicates that the auth handle was still active during SA deletion. This is part of cleanup recovery during the error condition.
Recommended Action None required.
715041
Error Message %PIX|ASA-7-715041: Received keep-alive of type keepalive_type, not the negotiated typeExplanation This indicates that a keep-alive of the type indicated in the message was received unexpectedly.
Recommended Action Check keepalive configuration on both peers.
715042
Error Message %PIX|ASA-7-715042: IKE received response of type failure_type to a request from the IP_address utilityExplanation This indicates that a request for an IP address for a remote access client from the internal utility that provides these addresses could not be satisfied. Variable text in the message string indicates more specifically what went wrong.
Recommended Action Check IP address assignment configuration and adjust accordingly.
715044
Error Message %PIX|ASA-7-715044: Ignoring Keepalive payload from vendor not support KeepAlive capabilityExplanation Received IOS Keepalive payload from vendor without KA capabilities set. Payload is ignored.
Recommended Action Informational only.
715045
Error Message %PIX|ASA-7-715045: ERROR: malformed Keepalive payloadExplanation Malformed Keepalive payload received. Payload is ignored.
Recommended Action Informational only.
715046
Error Message %PIX|ASA-7-715046: Group = groupname, Username = username, IP = IP_address, constructing payload_description payloadExplanation This message indicates that an IP address from a remote client for a specific group and user displays details about the IKE payload being constructed.
Recommended Action Informational only.
715047
Error Message %PIX|ASA-7-715047: processing payload_description payloadExplanation Displays details about the IKE payload received and being processed.
Recommended Action Informational only.
715048
Error Message %PIX|ASA-7-715048: Send VID_type VIDExplanation Displays type of Vendor ID payload being sent.
Recommended Action Informational only.
715049
Error Message %PIX|ASA-7-715049: Received VID_type VIDExplanation Displays type of Vendor ID payload received.
Recommended Action Informational only.
715050
Error Message %PIX|ASA-7-715050: Claims to be IOS but failed authenticationExplanation Looks like IOS VID but doesn't match hmac_sha.
Recommended Action Check Vendor ID configuration on both peers. If this issue affects interoperability, and the problem persists, contact the Cisco TAC.
715051
Error Message %PIX|ASA-7-715051: Received unexpected TLV type TLV_type while processing FWTYPE ModeCfg ReplyExplanation An unknown TLV was received in a security appliance record while a FWTYPE ModeCfg Reply was being processed. This will be discarded. This could occur either because of packet corruption or because the connecting client supports a later version of the security appliance protocol.
Recommended Action Check the personal FW installed on the Cisco VPN Client and the Personal FW configuration on the security appliance. This may also indicate a version mismatch between the VPN Client and the security appliance.
715052
Error Message %PIX|ASA-7-715052: Old P1 SA is being deleted but new SA is DEAD, cannot transition centriesExplanation The old P1 SA is being deleted but it has no new SA to transition to since it was marked for deletion as well. This generally indicates that the 2 IKE peers are out of synchronization 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 Informational only.
715053
Error Message %PIX|ASA-7-715053: MODE_CFG: Received request for attribute_info!Explanation Received a mode configuration message requesting the specified attribute.
Recommended Action Informational only.
715054
Error Message %PIX|ASA-7-715054: MODE_CFG: Received attribute_name reply: valueExplanation Received a mode configuration reply message from the remote peer.
Recommended Action Informational only.
715055
Error Message %PIX|ASA-7-715055: Send attribute_nameExplanation Sent a mode configuration message to the remote peer.
Recommended Action Informational only.
715056
Error Message %PIX|ASA-7-715056: Client is configured for TCP_transparencyExplanation Since the remote end (client) is configured for IPSec Over TCP, the headend security appliance must not negotiate IPSec Over UDP or IPSec over NAT-T with the client.
Recommended Action May require adjustment to the NAT transparency configuration of one of the peers if the tunnel does not come up. Otherwise this is an informational message.
715057
Error Message %PIX|ASA-7-715057: Auto-detected a NAT device with NAT-Traversal. Ignoring IPSec-over-UDP configuration.Explanation IPSec-over-UDP Mode Config info will not be exchanged because NAT-Traversal was detected.
Recommended Action Informational only.
715058
Error Message %PIX|ASA-7-715058: NAT-Discovery payloads missing. Aborting NAT-Traversal.Explanation The remote end didn't provide NAT-D payloads required for NAT-Traversal after exchanging NAT-Traversal VIDs. At least two NAT-D payloads must be received.
Recommended Action This may indicate a non-conforming 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.
715059
Error Message %PIX|ASA-7-715059: Proposing/Selecting only UDP-Encapsulated-Tunnel and UDP-Encapsulated-Transport modes defined by NAT-TraversalExplanation Need to use these modes instead of the usual Transport and Tunnel modes defined in the SA to successfully negotiate NAT-Traversal
Recommended Action Informational only.
715060
Error Message %PIX|ASA-7-715060: Dropped received IKE fragment. Reason: reasonExplanation The reason for dropping the fragment will be shown.
Recommended Action Depends on the drop reason but could indicate a problem with an intervening NAT device or a non-conforming peer.
715061
Error Message %PIX|ASA-7-715061: Rcv'd fragment from a new fragmentation set. Deleting any old fragments.Explanation This could be either a resend of the same packet but fragmented to a different MTU, or another packet altogether.
Recommended Action Informational only.
715062
Error Message %PIX|ASA-7-715062: Error assembling fragments! Fragment numbers are non-continuous.Explanation There is a gap in fragment numbers.
Recommended Action This could indicate a network problem. If the condition persists and results in dropped tunnels or prevents certain peers from negotiating with the security appliance, contact the Cisco TAC.
715063
Error Message %PIX|ASA-7-715063: Successfully assembled an encrypted pkt from rcv'd fragments!Explanation Assembly for a fragmented pkt that was rcv'd was successful
Recommended Action Informational only.
715064
Error Message %PIX|ASA-7-715064 -- IKE Peer included IKE fragmentation capability flags: Main Mode: true/false Aggressive Mode: true/falseExplanation Peer supports IKE fragmentation based on the info provided in the message.
Recommended Action Informational only.
715065
Error Message %PIX|ASA-7-715065: IKE state_machine subtype FSM error history (struct data_structure_address) state, event: state/event pairsExplanation 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 %PIX|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.
715067
Error Message %PIX|ASA-7-715067: QM IsRekeyed: existing sa from different peer, rejecting new saExplanation The LAN-TO-LAN SA that is being established already exists, in other words, an SA with the same remote networks, but is sourced from a different peer. This new SA will be deleted since 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 %PIX|ASA-7-715068: QM IsRekeyed: duplicate sa found by address, deleting old saExplanation The remote access SA that is being established already exists, in other words, an SA with the same remote networks, but is sourced from a different peer. The old SA will be deleted, since the peer may simply 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 %PIX|ASA-7-715069: Invalid ESP SPI size of SPI_sizeExplanation 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 could indicate that a peer may be non-conforming. If the problem persists, contact the Cisco TAC.
715070
Error Message %PIX|ASA-7-715070: Invalid IPComp SPI size of SPI_sizeExplanation 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 could indicate that a peer is non-conforming. If the problem persists, contact the Cisco TAC.
715071
Error Message %PIX|ASA-7-715071: AH proposal not supportedExplanation IPSec AH proposal is not supported. This proposal will be skipped.
Recommended Action Informational only.
715072
Error Message %PIX|ASA-7-715072: Received proposal with unknown protocol ID protocol_IDExplanation Received an IPSec SA proposal with unknown protocol ID. This proposal will be skipped.
Recommended Action Generally, this is a benign condition but could indicate that a peer is non-conforming. If the problem persists, contact the Cisco TAC.
715074
Error Message %PIX|ASA-7-715074: Could not retrieve authentication attributes for peer IP_addressExplanation Could not get authorization information for the remote user.
Recommended Action Ensure that all authentication and authorization configuration is set correctly. If the problem persists, contact the Cisco TAC.
715075
Error Message %PIX|ASA-7-715075: Group = group_name, Username = client, IP = IP_address Received keep-alive of type message_type (seq number number)Explanation This new message is in pair with 715036 "DPD R-U-THERE" message which logs the DPD sending messages.
Two possible cases:
1) received peer sending "DPD R-U-THERE" message
2) received peer reply "DPD R-U-THERE-ACK" message
The user is recommended to observe the following:
Case 1—The "DPD R-U-THERE" is received and its sequence number matches with the outgoing DPD reply message's.
If f1 sends a "DPD R-U-THERE-ACK" without prior receiving "DPD R-U-THERE" from peer, it is likely experiencing security breech.
Case 2—The received "DPD R-U-THERE-ACK" message's sequence number is matched with previous sending DPD message's.
If f1 did not receive a "DPD R-U-THERE-ACK" for a reasonable time lap after sending "DPD R-U-THERE" to peer, the tunnel is most likely down.
•
•
•
•
•
Recommended Action None required.
715076
Error Message %PIX|ASA-7-715076: Computing hash for ISAKMPExplanation This message is displayed when IKE computes various hash values.
This object will be prepended as follows:
Group = groupname, Username = username, IP = ip_address...
Recommended Action None required.
715077
Error Message %PIX|ASA-7-715077: Pitcher: msg string, spi spiExplanation This message is displayed when various messages are sent to IKE.
msg_string can be one of the following:
•
•
•
•
•
•
•
•
•
•
•
•
Like other ISAKMP, the following statement applies:
This object will be prepended as follows:
Group = groupname, Username = username, IP = ip_address,...
Recommended Action None required
715078
Error Message %PIX-7-715078: META-DATA Received type LAM attribute.Explanation The debug message displayed when processing a LAM attribute.
•
Recommended Action None required.
715079
Error Message %PIX-7-715079: META-DATA INTERNAL_ADDRESS: Received request for type.Explanation The debug message that displays when processing an internal address payload.
•
Recommended Action None required.
715080
Error Message %PIX-vpn-7-715080: Starting P1 rekey timer: 86400 seconds.Error Message %PIX-vpn-7-715080: Restarting P1 rekey timer: 86400 seconds.Error Message %ASA-vpn-7-715080: Starting P2 rekey timer: 28800 seconds.Explanation The IKE (P1) Phase 1 or IPSec (P2) Phase 2 rekey timers have been started or restarted. When an IKE (P1) or IPSec (P2) tunnel is connected, timers are created to determine when the next rekey will occur. These messages show what the timers are set to.
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.
Recommended Action None required.
716002
Error Message %ASA-webvpn-6-716002: Group GroupPolicy User username IP ip WebVPN session terminated: Port Preempted.Explanation The WebVPN session has been terminated by a user request. Possible reasons include:
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
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's access to various locations can be controlled using WebVPN-specific access control lists.
Recommended Action None required.
716004
Error Message %ASA-6-716004: Group group User user WebVPN access DENIED to specified location: urlExplanation The WebVPN user in this group has been denied access to this url. The WebVPN user's access to various locations can be controlled using WebVPN-specific access control lists. In this case, a particular access control list entry is denying access to this url.
Recommended Action None required.
716005
Error Message %ASA-6-716005: Group group User user WebVPN ACL Parse Error: reasonExplanation The ACL for the WebVPN user in the specified group failed to parse correctly. The reason for the error is reported.
The WebVPN access control list for the user in this group did not parse correctly. The reason for the error is reported.
Recommended Action Fix the WebVPN ACL.
716006
Error Message %ASA-6-716006: Group name User user WebVPN session terminated. Idle timeout.Explanation The WebVPN session was not created for this user in the specified group because the VPN tunnel protocol is not set to WebVPN.
Recommended Action None required.
716007
Error Message %ASA-4-716007: Group group User user WebVPN Unable to create session.Explanation The WebVPN session was not created for the in the specified group because of resource issues. For example, the user may have reached the maximum login limit.
Recommended Action None required.
716008
Error Message %ASA-7-716008: WebVPN ACL: actionExplanation The WebVPN ACL has begun performing an action. For example, the action could be "begin parsing." This is a debug level message.
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 access control list did not parse. The user will not be allowed to login via WebVPN until this error has been rectified.
Recommended Action Fix the WebVPN ACL.
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.
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.
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 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.
716024
Error Message %ASA-7-716024: Group name User user Unable to browse the network.Error: descriptionExplanation The user was unable to browse the Windows network via 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 could be a transient condition or may require further troubleshooting.
Recommended Action Check the connectivity between the WebVPN device and the server being accessed by CIFS. Check the NetBIOS name server (NBNS) configuration on the device.
716025
Error Message %ASA-7-716025: Group name User user Unable to browse domain domain. Error: descriptionExplanation The user was unable to browse the remote domain via the CIFS protocol.
Recommended Action Check the connectivity between the WebVPN device and the server being accessed by CIFS. Check the NetBIOS name server (NBNS) configuration on the device.
716026
Error Message %ASA-7-716026: Group name User user Unable to browse directory directory. Error: descriptionExplanation The user was unable to browse the remote directory via the CIFS protocol.
Recommended Action Check the connectivity between the WebVPN device and the server being accessed by CIFS. Check the NetBIOS name server (NBNS) configuration on the device.
716027
Error Message %ASA-7-716027: Group name User user Unable to view file filename. Error: descriptionExplanation The user was unable to view the remote file via the CIFS protocol.
Recommended Action Check the connectivity between the WebVPN device and the server being accessed by CIFS. Check the NetBIOS name server (NBNS) configuration on the device.
716028
Error Message %ASA-7-716028: Group name User user Unable to remove file filename. Error: descriptionExplanation The user was unable to remove the remote file via the CIFS protocol. This error is probably caused by lack of permissions.
Recommended Action Check the connectivity between the WebVPN device and the server being accessed by CIFS. Check the NetBIOS name server (NBNS) configuration on the device. Check the file permissions.
716029
Error Message %ASA-7-716029: Group name User user Unable to rename file filename. Error: descriptionExplanation The user was unable to rename the remote file via the CIFS protocol. This error was probably caused by lack of permissions.
Recommended Action Check the connectivity between the WebVPN device and the server being accessed by CIFS. Check the NetBIOS name server (NBNS) configuration on the device. Check the file permissions.
716030
Error Message %ASA-7-716030: Group name User user Unable to modify file filename. Error: descriptionExplanation A problem occurred when a user attempted to modify an existing file via the CIFS protocol. This error was probably caused by a lack of permissions.
Recommended Action Check the connectivity between the WebVPN device and the server being accessed by CIFS. Check the NetBIOS name server (NBNS) configuration on the device. Check the file permissions.
716031
Error Message %ASA-7-716031: Group name User user Unable to create file filename. Error: descriptionExplanation A problem occurred when a user attempted to create a file via the CIFS protocol. This error was probably caused by a permissions problem.
Recommended Action Check the connectivity between the WebVPN device and the server being accessed by CIFS. Check the NetBIOS name server (NBNS) configuration on the device. Check the file permissions.
716032
Error Message %ASA-7-716032: Group name User user Unable to create folder folder. Error: descriptionExplanation A problem occurred when a user attempted to create a folder via the CIFS protocol. This error was probably caused by a permissions problem.
Recommended Action Check the connectivity between the WebVPN device and the server being accessed by CIFS. Check the NetBIOS name server (NBNS) configuration on the device. Check file permissions.
716033
Error Message %ASA-7-716033: Group name User user Unable to remove folder folder. Error: descriptionExplanation A problem occurred when a user of the CIFS protocol attempted to remove a folder. This error 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 CIFS. Check the NetBIOS name server (NBNS) configuration on the device.
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 via the CIFS protocol. This error was probably caused by a permissions problem or a problem communicating with the server on which the file resides.
Recommended Action None required.
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 attempted to read a file. This error was probably caused by a 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 via 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 via the CIFS protocol but was not successful.
Recommended Action Verify that the user entered the correct user name 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 begin, the user must be authenticated successfully by a local or remote server (for example, RADIUS or TACACS+).
Recommended Action None required.
716039
Error Message %ASA-6-716039: Authentication: rejected, group = name user = user, Session Type: WebVPNExplanation 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 (user name and password) either did not match or the user does not have permission to start a WebVPN session.
Recommended Action Verify the user credentials on the local or remote server. Verify 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 system is in the process of rebooting.
Recommended Action None required.
716041
Error Message %ASA-6-716041: access-list acl_ID action url url hit_cnt countExplanation The WebVPN URL access control list named acl_ID has been hit count times for location url whose action is "permitted" or "denied."
Recommended Action None required.
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 countExplanation The WebVPN TCP access control list named acl_ID has been hit count times for packet received on source interface source_interface/source_address port source_port forwarded to dest_interface/dest_address destination dest_port whose action is "permitted" or "denied."
Recommended Action None required.
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.
•
•
•
Recommended Action None required.
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.
•
•
•
•
•
Recommended Action Modify the configuration to correct the indicated parameter. If the parameter is "vlan" or "nac-settings," verify that on the AAA server and ASA they are correctly configured.
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 as it might be very long.
•
•
•
•
Recommended Action Modify the configuration to correct the indicated parameter.
716046
Error Message %ASA-4-716046: Group group-name-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 access list was not found on the device.
•
•
•
•
Recommended Action Modify the configuration to add the specified access list or to correct the access list name.
716047
Error Message %ASA-4-716047: Group group-name User user-name IP IP_address User ACL access-list from AAA ignored, AV-PAIR ACL used instead.Explanation The specified access list was not used because a Cisco AV-PAIR access list was used.
•
•
•
•
Recommended Action Determine the correct access list 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 access list.
•
•
•
Recommended Action Purchase more memory, upgrade the device, or reduce the load on the device.
716049
Error Message %ASA-6-716049: Group group-name User user-name IP IP_address Empty SVC ACL.Explanation The access list to be used by the client was empty.
•
•
•
Recommended Action Determine the correct access list to use and modify the configuration.
716050
Error Message %ASA-6-716050: Error adding to ACL: ace_command_lineExplanation The access control entry had a syntax error.
•
Recommended Action Correct the downloadable access list configuration.
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 device, or reduce the load on the device.
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.
•
•
•
Recommended Action This may be due to an SSL VPN client (SVC) that is unable to connect. Check the user PC for SVC compatibility.
716053
Error Message %ASA-5-716053: SSO Server added: name: name Type: typeExplanation The Single Sign-On (SSO) server name of the specified type has been configured.
•
•
Recommended Action None required.
716054
Error Message %ASA-5-716054: SSO Server deleted: name: name Type: typeExplanation The SSO server name of the specified type has been removed from the configuration.
•
•
Recommended Action None required.
716055
Error Message %ASA-6-716055: Group group-name User user-name IP IP_address Authentication to SSO server name: name type type succeededExplanation The WebVPN user has been successfully authenticated to the SSO server.
•
•
•
•
•
Recommended Action None required.
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: reasonExplanation The WebVPN user failed to authenticate to the SSO server.
•
•
•
•
•
•
Recommended Action Either the user or the security appliance administrator need 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 adaptive security appliance using a client that is not licensed. This message may also occur if a temporary license has expired.
•
•
•
•
AnyConnect Mobile
LinkSys Phone
The type of license requested by the client (if other than 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 This message is generated when the SSL tunnel drops 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.
•
•
•
Recommended Action None required.
716059
Error Message %ASA-6-716059: Group group User user IP ip AnyConnect session resumed. Connection from ip2.Explanation This message is generated when an AnyConnect session is resumed from the inactive state.
•
•
•
•
Recommended Action None required.
716060
Error Message %ASA-6-715060: Group group User user IP ip Terminated AnyConnect session in inactive state to accept a new connection: License limit reached.Explanation This message is generated when an AnyConnect session in the inactive state is logged out to allow a new incoming SSL VPN (AnyConnect or clientless) connection.
•
•
•
Recommended Action None required.
716500
Error Message %ASA-2-716500: internal error in: function: Fiber library cannot locate AK47 instanceExplanation The fiber library cannot locate the application kernel layer 4 to 7 instance.
Recommended Action To determine the cause of the problem, contact Cisco TAC for assistance.
716501
Error Message %ASA-2-716501: internal error in: function: Fiber library cannot attach AK47 instanceExplanation The fiber library cannot attach the application kernel layer 4 to 7 instance.
Recommended Action To determine the cause of the problem, contact Cisco TAC for assistance.
716502
Error Message %ASA-2-716502: internal error in: function: Fiber library cannot allocate default arenaExplanation The fiber library cannot allocate the default arena.
Recommended Action To determine the cause of the problem, contact Cisco TAC for assistance.
716503
Error Message %ASA-2-716503: internal error in: function: Fiber library cannot allocate fiber descriptors poolExplanation The fiber library cannot allocate the fiber descriptors pool.
Recommended Action To determine the cause of the problem, contact Cisco TAC for assistance.
716504
Error Message %ASA-2-716504: internal error in: function: Fiber library cannot allocate fiber stacks poolExplanation The fiber library cannot allocate the fiber stack pool.
Recommended Action To determine the cause of the problem, contact Cisco TAC for assistance.
716505
Error Message %ASA-2-716505: internal error in: function: Fiber has joined fiber in unfinished stateExplanation The fiber has joined fiber in an unfinished state.
Recommended Action To determine the cause of the problem, contact Cisco TAC for assistance.
716506
Error Message %ASA-2-716506: UNICORN_SYSLOGID_JOINED_UNEXPECTED_FIBERExplanation An internal fiber library occurred.
Recommended Action Contact the Cisco TAC for assistance.
716507
Error Message %ASA-1-716507: Fiber scheduler has reached unreachable code. Cannot continue, terminating.Explanation The security appliance 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 Cisco TAC.
716508
Error Message %ASA-1-716508: internal error in: function: Fiber scheduler is scheduling rotten fiber. Cannot continuing terminatingExplanation The fiber scheduler is scheduling rotten fiber, so it cannot continue terminating.
Recommended Action To determine the cause of the problem, contact Cisco TAC for assistance.
716509
Error Message %ASA-1-716509:internal error in: function: Fiber scheduler is scheduling alien fiber. Cannot continue terminatingExplanation The fiber scheduler is scheduling alien fiber, so it cannot continue terminating.
Recommended Action To determine the cause of the problem, contact Cisco TAC for assistance.
716510
Error Message %ASA-1-716510:internal error in: function: Fiber scheduler is scheduling finished fiber. Cannot continue terminatingExplanation The fiber scheduler is scheduling finished fiber, so it cannot continue terminating.
Recommended Action To determine the cause of the problem, contact Cisco TAC for assistance.
716512
Error Message %ASA-2-716512:internal error in: function: Fiber has joined fiber waited upon by someone elseExplanation The fiber has joined fiber that is waited upon by someone else.
Recommended Action To determine the cause of the problem, contact Cisco TAC for assistance.
716513
Error Message %ASA-2-716513: internal error in: function: Fiber in callback blocked on other channelExplanation The fiber in the callback was blocked on the other channel.
Recommended Action To determine the cause of the problem, contact Cisco TAC for assistance.
716515
Error Message %ASA-2-716515:internal error in: function: OCCAM failed to allocate memory for AK47 instanceExplanation The OCCAM failed to allocate memory for the AK47 instance.
Recommended Action To determine the cause of the problem, contact Cisco TAC for assistance.
716516
Error Message %ASA-1-716516: internal error in: function: OCCAM has corrupted ROL array. Cannot continue terminatingExplanation The OCCAM has a corrupted ROL array, so it cannot continue terminating.
Recommended Action To determine the cause of the problem, contact Cisco TAC for assistance.
716517
Error Message %ASA-2-716517: internal error in: function: OCCAM cached block has no associated arenaExplanation The OCCAM cached block has no associated arena.
Recommended Action To determine the cause of the problem, contact Cisco TAC for assistance.
716518
Error Message %ASWA-2-716518: internal error in: function: OCCAM pool has no associated arenaExplanation The OCCAM pool has no associated arena.
Recommended Action To determine the cause of the problem, contact Cisco TAC for assistance.
716519
Error Message %ASA-1-716519: internal error in: function: OCCAM has corrupted pool list. Cannot continue terminatingExplanation The OCCAM has a corrupted pool list, so it cannot continue terminating.
Recommended Action To determine the cause of the problem, contact Cisco TAC for assistance.
716520
Error Message %ASA-2-716520:internal error in: function: OCCAM pool has no block listExplanation The OCCAM pool has no block list.
Recommended Action To determine the cause of the problem, contact Cisco TAC for assistance.
716521
Error Message %ASA-2-716521: internal error in: function: OCCAM no realloc allowed in named poolExplanation The OCCAM did not allow reallocation in the named pool.
Recommended Action To determine the cause of the problem, contact Cisco TAC for assistance.
716522
Error Message %ASA-2-716522: internal error in: function: OCCAM corrupted standalone blockExplanation The OCCAM has a corrupted standalone block.
Recommended Action To determine the cause of the problem, contact Cisco TAC for assistance.
716525
Error Message %ASA-2-716525: UNICORN_SYSLOGID_SAL_CLOSE_PRIVDATA_CHANGEDExplanation An internal SAL error has occurred.
Recommended Action Contact the Cisco TAC for assistance.
716526
Error Message %ASA-2-716526: UNICORN_SYSLOGID_PERM_STORAGE_SERVER_LOAD_FAILExplanation A failure in mounting of the permanent storage server directory occurred.
Recommended Action Contact the Cisco TAC for assistance.
716527
Error Message %ASA-2-716527: UNICORN_SYSLOGID_PERM_STORAGE_SERVER_STORE_FAILExplanation A failure in mounting of the permanent storage file occurred.
Recommended Action Contact the Cisco TAC for assistance.
716528
Error Message %ASA-1-716528: Unexpected fiber scheduler error; possible out-of-memory conditionExplanation The security appliance has experienced an unexpected error and has recovered.
Recommended Action Check for high CPU usage, CPU hogs, and potential memory leaks. If the problem persists, contact Cisco TAC.
717001
Error Message %PIX|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 and resubmit enrollment.
717002
Error Message %PIX|ASA-3-717002: Certificate enrollment failed for trustpoint trustpoint_name. Reason: reason_string.Explanation An enrollment request for this trustpoint_name trustpoint has failed.
•
•
Recommended Action Check the Certificate Authority server for failure reason.
717003
Error Message %PIX|ASA-6-717003: Certificate received from Certificate Authority for trustpoint trustpoint_name.Explanation A certificate was successfully received from the Certificate Authority for this trustpoint_name trustpoint.
Recommended Action None required
717004
Error Message %PIX|ASA-6-717004: PKCS #12 export failed for trustpoint trustpoint_name.Explanation Trustpoint trustpoint_name failed to export. It is likely that only a CA certificate exists and an identity certificate doesn't exist for trustpoint or a required keypair is missing.
Recommended Action Ensure that required certificates and keypairs are present for the given trustpoint.
717005
Error Message %PIX|ASA-6-717005: PKCS #12 export succeeded for trustpoint trustpoint_name.Explanation Trustpoint trustpoint_name was successfully exported.
Recommended Action None required
717006
Error Message %PIX|ASA-6-717006: PKCS #12 import failed for trustpoint trustpoint_name.Explanation Import of the requested trustpoint trustpoint_name failed to be processed.
Recommended Action Ensure the integrity of the imported data and make sure that the entire pkcs12 record is correctly pasted and resubmit import attempt.
717007
Error Message %PIX|ASA-6-717007: PKCS #12 import succeeded for trustpoint trustpoint_name.Explanation Import of the requested trustpoint trustpoint_name was successfully completed.
Recommended Action None required.
717008
Error Message %PIX|ASA-2-717008: Insufficient memory to process_requiring_memory.Explanation An internal error occurred while attempting to allocate memory for process_requiring_memory. Other processes may experience problems allocating memory and prevent further processing.
Recommended Action Collect memory statistics and logs for further debugging and reload system.
717009
Error Message %PIX|ASA-3-717009: Certificate validation failed. Reason: reason_string.Explanation A certificate validation failed due to reason_string. The reason_string specifies the reason for the failure and it could be due to a validation attempt of a revoked certificate, invalid certificate attributes or configuration issues.
•
Recommended Action Ensure configuration has a valid trustpoint configured for validation if the reason_string indicates that no suitable trustpoints are found. Check system time to ensure it is accurate relative to the certificate authority time. Check the reason_string and correct any issues that are indicated.
717010
Error Message %PIX|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.
•
Recommended Action Verify that connectivity with the configured CRL Distribution Point and ensure manual CRL retrieval also functions correctly.
717011
Error Message %PIX|ASA-2-717011: Unexpected event event event_IDExplanation This log message indicates that an event that is not expected under normal conditions has occurred.
Recommended Action If the problem persists, contact the Cisco TAC.
717012
Error Message %PIX|ASA-3-717012: Failed to refresh CRL cache entry from the server for trustpoint trustpoint_name at time_of_failureExplanation This log message indicates that an attempt to refresh a cached CRL entry has failed for the specified trustpoint trustpoint_name, at the indicated time_of_failure. This may result in obsolete CRLs on the system that may cause connections that require a valid CRL to be denied.
Recommended Action Check connectivity issues to the server including network down, server down, and so on. Try to retrieve the CRL manually using the crypto ca crl retrieve command.
717013
Error Message %PIX|ASA-5-717013: Removing a cached CRL to accommodate an incoming CRL. Issuer: issuerExplanation When the device is configured to authenticate IPSec tunnels using digital certificates, Certificate Revocation Lists (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 log event will be generated for each CRL that is purged.
Recommended Action None required.
717014
Error Message %PIX|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, Certificate Revocation Lists (CRLs) may be cached in memory to avoid requiring a CRL download during each connection. This log event will be generated if a received CRL is too large to fit in the cache.
Recommended Action No action necessary. The large CRLs are still supported even though they are not cached. This means that the CRL will be downloaded with each IPSec connection. This may impact performance during IPSec connection bursts.
717015
Error Message %PIX|ASA-3-717015: CRL received from issuer is too large to process (CRL size = crl_size, maximum CRL size = max_crl_size)Explanation This log event will be generated when an IPSec connection causes a CRL, that is larger than the maximum permitted CRL size, max_crl_size, 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.
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 Certificate Authority based solution to reduce the CRL size or configure the device not to require CRL validation.
717016
Error Message %PIX|ASA-6-717016: Removing expired CRL from the CRL cache. Issuer: issuerExplanation When the device is configured to authenticate IPSec tunnels using digital certificates, Certificate Revocation Lists (CRLs) may be cached in memory to avoid requiring a CRL download during each connection. This log event 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. This is a routine occurrence.
717017
Error Message %PIX|ASA-3-717017: Failed to query CA certificate for trustpoint trustpoint_name from enrollment_urlExplanation This logs an error that may occur when an attempt is made to authenticate a trustpoint by requesting a CA certificate from a Certificate Authority.
Recommended Action Ensure that an enrollment URL is configured with this trustpoint and ensure connectivity with the Certificate Authority server and retry request.
717018
Error Message %PIX|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 This log event will be generated when an IPSec connection causes a CRL, that contains 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.
•
•
•
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 Certificate Authority based solution to reduce the CRL size or configure the device not to require CRL validation.
717019
Error Message %PIX|ASA-3-717019: Failed to insert CRL for trustpoint trustpoint_name. Reason: failure_reason.Explanation This log event will be generated when a CRL is retrieved but it is found to be invalid and cannot be inserted into the cache because of the failure_reason.
•
•
Recommended Action Ensure the current system 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 %PIX|ASA-3-717020: Failed to install device certificate for trustpoint label. Reason: reason string.Error MessageExplanation A failure occurred while trying to enroll or import an enrolled certificate into a trustpoint. The message indicates the trustpoint that was attempting an enrollment and a reason for the failure.
Explanation
•
•
Recommended Action Use the failure reason to remedy the cause of failure and reattempt the enrollment. Common failures are due to invalid certificates being imported into the device or a mismatch of the public key included in the enrolled certificate vs. the keypair referenced in the trustpoint.
717021
Error Message %PIX|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 This message is displayed when an attempt to verify the certificate that is identified by the serial number and subject name can not be verified for the specified reason. When verifying certificate data using the signature, several errors can occur that should be logged. These include invalid key types specified and unsupported key size.
•
•
•
•
Recommended Action Check the specified certificate to ensure that it is valid, that it contains a valid key type, and that it does not exceed the maximum supported key size.
717022
Error Message %PIX|ASA-6-717022: Certificate was successfully validated. certificate_identifiersExplanation This message is displayed when the identified certificate is successfully validated.
•
Recommended Action No ne.
717023
Error Message %PIX|ASA-3-717023: SSL failed to set device certificate for trustpoint trustpoint name. Reason: reason_string.Explanation This message is displayed when a failure occurs while trying to set a device certificate for the given trustpoint for authenticating the SSL connection. When bringing up an SSL connection, an attempt is made to set the device certificate that will be used. A failure occurring during this process is logged. The message includes the configured trustpoint that should be used to load the device certificate and the reason for the failure.
•
•
Recommended Action Resolve the issue indicated by the reason reported for the failure:
•
•
•
717024
Error Message %PIX|ASA-7-717024: Checking CRL from trustpoint: trustpoint name for purposeExplanation This log message indicates that a CRL is being retrieved.
•
•
Recommended Action None required.
717025
Error Message %PIX|ASA-7-717025: Validating certificate chain containing number of certs certificate(s).Explanation This message is displayed when a chain of certificate is being validated.
•
Recommended Action None required.
717026
Error Message %PIX|ASA-4-717026: Name lookup failed for hostname hostname during PKI operation.Explanation This message is displayed when the given hostname cannot be resolved while attempting a PKI operation.
•
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 %PIX|ASA-3-717027: Certificate chain failed validation. reason_string.Explanation This message is displayed when a certificate chain could not be validated. A reason is given to pinpoint the cause of the failure.
•
Recommended Action Resolve the issue noted by the reason and retry the validation attempt by performing any of the following actions:
•
•
•
•
717028
Error Message %PIX|ASA-6-717028: Certificate chain was successfully validated additional info.Explanation This message is displayed when a certificate chain was successfully validated.
•
Recommended Action None required.
717029
Error Message %PIX|ASA-7-717029: Identified client certificate within certificate chain. serial number: serial_number, subject name: subject_name.Explanation This message identifies the certificate that is found to be the client certificate.
•
•
Recommended Action None required.
717030
Error Message %PIX|ASA-7-717030: Found a suitable trustpoint trustpoint name to validate certificate.Explanation This message is displayed when a suitable/usable trustpoint is found that can be used to validate the certificate.
•
Recommended Action None required.
717031
Error Message %PIX|ASA-4-717031: Failed to find a suitable trustpoint for the issuer: issuer Reason: reason_stringExplanation This syslog message displays when a usable trustpoint cannot be found. This message identifies the issuer of the certificate for which no suitable trustpoint could be found and indicates the reason for the failure. During certificate validation a suitable trustpoint must be available in order to validate a certificate.
•
•
Recommended Action Resolve the issue indicated in the reason by checking configuration to make sure a trustpoint is configured, authenticated, and enrolled. Also make sure the configuration allows for specific types of certificates, such as issued identity certificates.
717032
Error Message %PIX-3-717032: OCSP status check failed. Reason: reason_string.Explanation This syslog message indicates that an attempt to verify the certificate status using OCSP failed because of the reason_string specified.
•
Recommended Action Check the specified reason_string to determine the cause of the failure and to ensure that the OCSP responder is accessible and any response should be verifiable.
717033
Error Message %PIX|ASA-6-717033: OCSP response status - Successful.Explanation This syslog message indicates that an OCSP status check response was received successfully.
Recommended Action None required.
717034
Error Message %PIX|ASA-7-717034: No-check extension found in certificate. OCSP check bypassed.Explanation This syslog message indicates that an OCSP responder certificate was received that contains an "id-pkix-ocsp-nocheck" extension, which allows this certificate to be validated without a OCSP status check.
Recommended Action None required.
717035
Error Message %PIX|ASA-4-717035: OCSP status is being checked for certificate. certificate_identifier.Explanation This syslog message identifies the certificate for which an OCSP status check occurs.
•
Recommended Action None required.
717036
Error Message PIX|ASA-7-717036: Looking for a tunnel group match based on certificate maps for peer certificate with certificate_identifier.Explanation This syslog message indicates that the peer certificate identified by certificate_identifier is being processed through the configured certificate maps in order to attempt a possible tunnel-group match.
•
Recommended Action None required.
717037
Error Message %PIX|ASA-4-717037: Tunnel group search using certificate maps failed for peer certificate: certificate_identifier.Explanation This syslog message indicates that the peer certificate identified by certificate_identifier was processed through the configured certificate maps in order to attempt a possible tunnel-group match, but no match could be found.
•
Recommended Action Ensure that the warning is expected based on the received peer certificate and the configured crypto ca certificate map rules.
717038
Error Message %PIX|ASA-7-717038: Tunnel group match found. Tunnel Group: tunnel_group_name, Peer certificate: certificate_identifier.Explanation This syslog message indicates that the peer certificate identified by certificate_identifier was processed by the configured certificate maps and a match was found to the tunnel_group_name tunnel group.
•
•
Recommended Action None required.
717039
Error Message %ASA-3-717039: Local CA Server internal error detected: error.Explanation Logs an internal processing error that has occurred with the local CA server. The error string indicates the cause of the error, which requires administrator intervention to overcome.
•
Recommended Action Based on error, take the necessary steps to resolve the issue. Currently, the possible errors include:
•
•
•
•
•
717040
Error Message %ASA-2-717040: Local CA Server has failed and is being disabled. Reason: reason.Explanation Indicates that the Local CA Server is being disabled due to an error. The reason for the failure is indicated by the reason string and administrator intervention may be required to resolve the issue encountered.
•
Recommended Action Based on reason, take the necessary steps to resolve the issue. Currently, the possible errors include:
•
717041
Error Message %ASA-7-717041: Local CA Server event: event info.Explanation Reports events that have occurred on the CA server to allow you to track or debug the CA server's health. It reports when the CA server is created, enabled, disabled, CA server certificate is rolled over, and so on.
•
Recommended Action None required.
717042
Error Message %ASA-3-717042: Failed to enable Local CA Server.Reason: reason.Explanation Reports errors that occur when an attempt is made to enable the Local CA Server. The reason for the failure is indicated by the reason.
•
Recommended Action Resolve the issue encountered that is reported via the reason string. Currently, the possible reasons include:
•
•
•
•
•
•
•
•
•
•
•
•
717043
Error Message %ASA-6-717043: Local CA Server certificate enrollment related info for user: user. Info: info.Explanation Allows monitoring of enrollment related activities for a user. The username and specific enrollment information are reported so that enrollments, email invitation generation, renewal reminder generation, and so on can be monitored.
•
•
Recommended Action None required.
717044
Error Message %ASA-3-717044: Local CA server certificate enrollment related error for user: user. Error: error.Explanation Reports any errors that occur in the processing of certificate enrollment. This may include errors in notifying users via email for renewal reminders, errors during issuing of a certificate to complete enrollment, invalid username or OTP, expired enrollment attempts, and so on.
•
•
Recommended Action The error indicates the specific enrollment related error that occurred for the user. If the error string doesn't provide enough information to diagnose and resolve the issue, turn on debugging and attempt enrollment again.
717045
Error Message %ASA-7-717045:Local CA Server CRL info: infoExplanation Allows monitoring of the CRL file, when it is generated and regenerated, and so on.
•
Recommended Action None required.
717046
Error Message %ASA-3-717046: Local CA Server CRL error: error.Explanation Logs errors that are encountered while trying to generate and re-issue the local CA server's CRL file.
•
Recommended Action The error string indicates the error that occurred. Take appropriate action to resolve the reported issue, which may include verifying that storage is accessible, that the CRL file is valid in storage and signed by the existing local CA server, and so on.
717047
Error Message %ASA-6-717047: Revoked certificate issued to user: username, with serial number serial number.Explanation Allows monitoring of any certificates, issued by the local CA server, that have been revoked.
•
•
Recommended Action None required.
717048
Error Message %ASA-6-717048: Unrevoked certificate issued to user: username, with serial number serial number.Explanation Allows monitoring of any certificates that were issued by the local CA server, that were previously revoked, that are now being unrevoked and removed from the CRL.
•
•
Recommended Action None required.
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 Alerts the administrator of an upcoming CA certificate expiration so that the administrator can take action to export the replacement certificate to all devices that will require the new certificate.
•
Recommended Action Action should be taken prior to the actual expiration of the current Local CA Server certificate, which is indicated by the number field, to avoid certificate validation failures on any devices that require the Local CA Server certificate. Note that the Local CA Server doesn't require any action because the CA certificate will be replaced automatically. Issue the show crypto ca server certificate CLI to view the replacement/rollover Local CA Server certificate and cut-and-paste it for import into any device that will require the new certificate upon expiration of the current Local CA Server certificate.
718001
Error Message %PIX|ASA-7-718001: Internal interprocess communication queue send failure: code error_codeExplanation An internal software error has occurred while attempting to enqueue a message on the VPNLB queue.
Recommended Action This is generally a benign condition. If the problem persists, contact the Cisco TAC.
718002
Error Message %PIX|ASA-5-718002: Create peer IP_address failure, already at maximum of number_of_peersExplanation Maximum number of load balancing peers exceeded. New peer ignored.
Recommended Action Check your load balancing and network configuration to ensure that the number of LB peers does not exceed the maximum allowed.
718003
Error Message %PIX|ASA-6-718003: Got unknown peer message message_number from IP_address, local version version_number, remote version version_numberExplanation An unrecognized load balancing message was received from one of the LB peers. This could indicate a version mismatch between peers but is most likely caused by an internal software error.
Recommended Action Verify that all LB peers are compatible. If they are and this condition persists, or is linked to undesirable behavior, contact the Cisco TAC.
718004
Error Message %PIX|ASA-6-718004: Got unknown internal message message_numberExplanation Received an unknown internal message. This generally indicates an internal software error.
Recommended Action This is generally a benign condition. If the problem persists, contact the Cisco TAC.
718005
Error Message %PIX|ASA-5-718005: Fail to send to IP_address, port portExplanation An internal software error has occurred while attempting to send a packet on the load balancing socket. This could indicate a network problem or an internal software error.
Recommended Action Check the network-based configuration on the security appliance and verify that interfaces are active and protocol data is flowing through the device. If the problem persists, contact the Cisco TAC.
718006
Error Message %PIX|ASA-5-718006: Invalid load balancing state transition [cur=state_number][event=event_number]Explanation A state machine error has occurred. This could indicate an internal software error.
Recommended Action This is generally a benign condition. If the problem persists, contact the Cisco TAC.
718007
Error Message %PIX|ASA-5-718007: Socket open failure failure_codeExplanation An error has occurred while attempting to open the load balancing socket. This could indicate a network problem or an internal software error.
Recommended Action Check the network-based configuration on the security appliance and verify that interfaces are active and protocol data is flowing through the device. If the problem persists, contact the Cisco TAC.
718008
Error Message %PIX|ASA-5-718008: Socket bind failure failure_codeExplanation An error has occurred while attempting to bind to the load balancing socket. This could indicate a network problem or an internal software error.
Recommended Action Check the network-based configuration on the security appliance and verify that interfaces are active and protocol data is flowing through the device. If the problem persists, contact the Cisco TAC.
718009
Error Message %PIX|ASA-5-718009: Send HELLO response failure to IP_addressExplanation An error has occurred while attempting to send a Hello Response message to one of the LB peers. This could indicate a network problem or an internal software error.
Recommended Action Check the network-based configuration on the security appliance and verify that interfaces are active and protocol data is flowing through the device. If the problem persists, contact the Cisco TAC.
718010
Error Message %PIX|ASA-5-718010: Sent HELLO response to IP_addressExplanation The security appliance transmitted a Hello Response message to a LB peer.
Recommended Action Informational only.
718011
Error Message %PIX|ASA-5-718011: Send HELLO request failure to IP_addressExplanation An error has occurred while attempting to send a Hello Request message to one of the LB peers. This could indicate a network problem or an internal software error.
Recommended Action Check the network-based configuration on the security appliance and verify that interfaces are active and protocol data is flowing through the device. If the problem persists, contact the Cisco TAC.
718012
Error Message %PIX|ASA-5-718012: Sent HELLO request to IP_addressExplanation The security appliance transmitted a Hello Request message to a LB peer.
Recommended Action Informational only.
718013
Error Message %PIX|ASA-6-718013: Peer IP_address is not answering HELLOExplanation LB peer is not answering HELLO.
Recommended Action Check status of LBSSF peer and check the network connections.
718014
Error Message %PIX|ASA-5-718014: Master peer IP_address is not answering HELLOExplanation LB master peer is not answering HELLO.
Recommended Action Check status of LBSSF master peer and check the network connections.
718015
Error Message %PIX|ASA-5-718015: Received HELLO request from IP_addressExplanation The security appliance received a Hello Request message from a LB peer.
Recommended Action Informational only.
718016
Error Message %PIX|ASA-5-718016: Received HELLO response from IP_addressExplanation The security appliance received a Hello Response packet from a LB peer.
Recommended Action Informational only.
718017
Error Message %PIX|ASA-7-718017: Got timeout for unknown peer IP_address msg type message_typeExplanation The security appliance processed a timeout for an unknown peer. The message was ignored since the peer may have already been removed from the active list.
Recommended Action If the message persists or is linked to undesirable behavior, Check LB peers and verify that all are configured correctly.
718018
Error Message %PIX|ASA-7-718018: Send KEEPALIVE request failure to IP_addressExplanation An error has occurred while attempting to send a Keepalive Request message to one of the LB peers. This could indicate a network problem or an internal software error.
Recommended Action Check the network-based configuration on the security appliance and verify that interfaces are active and protocol data is flowing through the device. If the problem persists, contact the Cisco TAC.
718019
Error Message %PIX|ASA-7-718019: Sent KEEPALIVE request to IP_addressExplanation The security appliance transmitted a Keepalive Request message to a LB peer.
Recommended Action Informational only.
718020
Error Message %PIX|ASA-7-718020: Send KEEPALIVE response failure to IP_addressExplanation An error has occurred while attempting to send a Keepalive Response message to one of the LB peers. This could indicate a network problem or an internal software error.
Recommended Action Check the network-based configuration on the security appliance and verify that interfaces are active and protocol data is flowing through the device. If the problem persists, contact the Cisco TAC.
718021
Error Message %PIX|ASA-7-718021: Sent KEEPALIVE response to IP_addressExplanation The security appliance transmitted a Keepalive Response message to a LB peer.
Recommended Action Informational only.
718022
Error Message %PIX|ASA-7-718022: Received KEEPALIVE request from IP_addressExplanation The security appliance received a Keepalive Request message from a LB peer.
Recommended Action Informational only.
718023
Error Message %PIX|ASA-7-718023: Received KEEPALIVE response from IP_addressExplanation The security appliance received a Keepalive Response message from a LB peer.
Recommended Action Informational only.
718024
Error Message %PIX|ASA-5-718024: Send CFG UPDATE failure to IP_addressExplanation An error has occurred while attempting to send a Configuration Update message to one of the LB peers. This could indicate a network problem or an internal software error.
Recommended Action Check the network-based configuration on the security appliance and verify that interfaces are active and protocol data is flowing through the device. If the problem persists, contact the Cisco TAC.
718025
Error Message %PIX|ASA-7-718025: Sent CFG UPDATE to IP_addressExplanation The security appliance transmitted a Configuration Update message to a LB peer.
Recommended Action Informational only.
718026
Error Message %PIX|ASA-7-718026: Received CFG UPDATE from IP_addressExplanation The security appliance received a Configuration Update message from a LB peer.
Recommended Action Informational only.
718027
Error Message %PIX|ASA-6-718027: Received unexpected KEEPALIVE request from IP_addressExplanation Informational message.
Recommended Action If the problem persists or is linked with undesirable behavior, verify that all LB peers are configured and discovered correctly.
718028
Error Message %PIX|ASA-5-718028: Send OOS indicator failure to IP_addressExplanation An error has occurred while attempting to send a OOS Indicator message to one of the LB peers. This could indicate a network problem or an internal software error.
Recommended Action Check the network-based configuration on the security appliance and verify that interfaces are active and protocol data is flowing through the device. If the problem persists, contact the Cisco TAC.
718029
Error Message %PIX|ASA-7-718029: Sent OOS indicator to IP_addressExplanation The security appliance transmitted a OOS Indicator message to a LB peer.
Recommended Action Informational only.
718030
Error Message %PIX|ASA-6-718030: Received planned OOS from IP_addressExplanation The security appliance received a planned OOS message from a LB peer.
Recommended Action Informational only.
718031
Error Message %PIX|ASA-5-718031: Received OOS obituary for IP_addressExplanation The security appliance received a OOS Obituary from a LB peer.
Recommended Action Informational only.
718032
Error Message %PIX|ASA-5-718032: Received OOS indicator from IP_addressExplanation The security appliance received a OOS Indicator from a LB peer.
Recommended Action Informational only.
718033
Error Message %PIX|ASA-5-718033: Send TOPOLOGY indicator failure to IP_addressExplanation An error has occurred while attempting to send a Topology Indicator message to one of the LB peers. This could indicate a network problem or an internal software error.
Recommended Action Check the network-based configuration on the security appliance and verify that interfaces are active and protocol data is flowing through the device. If the problem persists, contact the Cisco TAC.
718034
Error Message %PIX|ASA-7-718034: Sent TOPOLOGY indicator to IP_addressExplanation The security appliance sent a Topology Indicator message to a LB peer.
Recommended Action Informational only.
718035
Error Message %PIX|ASA-7-718035: Received TOPOLOGY indicator from IP_addressExplanation The security appliance received a Topology Indicator message from a LB peer.
Recommended Action Informational only.
718036
Error Message %PIX|ASA-7-718036: Process timeout for req-type type_value, exid exchange_ID, peer IP_addressExplanation The security appliance processed a peer timeout.
Recommended Action Verify that the peer should have been timed out. If not, check the peer LB configuration and check the network connection between the peer and the security appliance.
718037
Error Message %PIX|ASA-6-718037: Master processed number_of_timeouts timeoutsExplanation The security appliance in the master role processed the specified number of peer timeouts.
Recommended Action Verify that the timeouts are legitimate. If not, check the peer LB configuration and check the network connection between the peer and the security appliance.
718038
Error Message %PIX|ASA-6-718038: Slave processed number_of_timeouts timeoutsExplanation The security appliance in the slave role processed the specified number of peer timeouts.
Recommended Action Verify that the timeouts are legitimate. If not, check the peer LB configuration and check the network connection between the peer and the security appliance.
718039
Error Message %PIX|ASA-6-718039: Process dead peer IP_addressExplanation The security appliance has detected a dead peer.
Recommended Action Verify that the dead peer detection is legitimate. If not, check the peer LB configuration and check the network connection between the peer and the security appliance.
718040
Error Message %PIX|ASA-6-718040: Timed-out exchange ID exchange_ID not foundExplanation The security appliance has detected a dead peer but the exchange ID is not recognized.
Recommended Action Informational only.
718041
Error Message %PIX|ASA-7-718041: Timeout [msgType=type] processed with no callbackExplanation The security appliance has detected a dead peer but a call back was not used in the processing.
Recommended Action Informational only.
718042
Error Message %PIX|ASA-5-718042: Unable to ARP for IP_addressExplanation The security appliance experienced an ARP failure when attempting to contact a peer.
Recommended Action Verify that the network is operational and all peers can communicate with each other.
718043
Error Message %PIX|ASA-5-718043: Updating/removing duplicate peer entry IP_addressExplanation The security appliance found and is removing a duplicate peer entry.
Recommended Action Informational only.
718044
Error Message %PIX|ASA-5-718044: Deleted peer IP_addressExplanation The security appliance is deleting a LB peer.
Recommended Action Informational only.
718045
Error Message %PIX|ASA-5-718045: Created peer IP_addressExplanation The security appliance has detected a LB peer.
Recommended Action Informational only.
718046
Error Message %PIX|ASA-7-718046: Create group policy policy_nameExplanation The security appliance has created a group policy to securely communicate to the LB peers.
Recommended Action Informational only.
718047
Error Message %PIX|ASA-7-718047: Fail to create group policy policy_nameExplanation The security appliance experienced a failure when attempting to create a group policy for securing the communication between LB peers.
Recommended Action Verify that LB configuration is correct.
718048
Error Message %PIX|ASA-5-718048: Create of secure tunnel failure for peer IP_addressExplanation The security appliance experienced a failure when attempting to establish an IPSec tunnel to a LB peer.
Recommended Action Verify that LB configuration is correct and that the network is operational.
718049
Error Message %PIX|ASA-7-718049: Created secure tunnel to peer IP_addressExplanation The security appliance successfully established an IPSec tunnel to a LB peer.
Recommended Action Informational only.
718050
Error Message %PIX|ASA-5-718050: Delete of secure tunnel failure for peer IP_addressExplanation The security appliance experienced a failure when attempting to terminate an IPSec tunnel to a LB peer.
Recommended Action Verify that LB configuration is correct and that the network is operational.
718051
Error Message %PIX|ASA-6-718051: Deleted secure tunnel to peer IP_addressExplanation The security appliance successfully terminated an IPSec tunnel to a LB peer.
Recommended Action Informational only.
718052
Error Message %PIX|ASA-5-718052: Received GRAT-ARP from duplicate master MAC_addressExplanation The security appliance received a Gratuitous ARP from duplicate master.
Recommended Action Check the LB configuration and verify that the network is operational.
718053
Error Message %PIX|ASA-5-718053: Detected duplicate master, mastership stolen MAC_addressExplanation The security appliance detected duplicate master, mastership stolen.
Recommended Action Check the LB configuration and verify that the network is operational.
718054
Error Message %PIX|ASA-5-718054: Detected duplicate master MAC_address and going to SLAVEExplanation The security appliance detected a duplicate master and is switching to slave mode.
Recommended Action Check the LB configuration and verify that the network is operational.
718055
Error Message %PIX|ASA-5-718055: Detected duplicate master MAC_address and staying MASTERExplanation The security appliance detected a duplicate master and is staying in slave mode.
Recommended Action Check the LB configuration and verify that the network is operational.
718056
Error Message %PIX|ASA-7-718056: Deleted Master peer, IP IP_addressExplanation The security appliance deleted the LB master from its internal tables.
Recommended Action Informational only.
718057
Error Message %PIX|ASA-5-718057: Queue send failure from ISR, msg type failure_codeExplanation An internal software error has occurred while attempting to enqueue a message on the VPNLB queue form an Interrupt Service Routing.
Recommended Action This is generally a benign condition. If the problem persists, contact the Cisco TAC.
718058
Error Message %PIX|ASA-7-718058: State machine return code: action_routine, return_codeExplanation This event traces the return codes of action routines belonging to the LB finite state machine.
Recommended Action Informational only.
718059
Error Message %PIX|ASA-7-718059: State machine function trace: state=state_name, event=event_name, func=action_routineExplanation This event traces the events and states of the LB finite state machine.
Recommended Action Informational only.
718060
Error Message %PIX|ASA-5-718060: Inbound socket select fail: context=context_ID.Explanation The socket select call returned an error and the socket could not be read. This could indicate an internal software error.
Recommended Action If the problem persists, contact the Cisco TAC.
718061
Error Message %PIX|ASA-5-718061: Inbound socket read fail: context=context_ID.Explanation The socket read failed after data was detected through the select call. This could indicate an internal software error.
Recommended Action If the problem persists, contact the Cisco TAC.
718062
Error Message %PIX|ASA-5-718062: Inbound thread is awake (context=context_ID).Explanation This indicates every time the LB process is woken up and begins processing.
Recommended Action Informational only.
718063
Error Message %PIX|ASA-5-718063: Interface interface_name is down.Explanation This indicates that the LB process found the interface down.
Recommended Action Check the interface configuration to make sure that the interface is operational.
718064
Error Message %PIX|ASA-5-718064: Admin. interface interface_name is down.Explanation This indicates that the LB process found the administrative interface down.
Recommended Action Check the administrative interface configuration to make sure that the interface is operational.
718065
Error Message %PIX|ASA-5-718065: Cannot continue to run (public=up/down, private=up/down, enable=LB_state, master=IP_address, session=Enable/Disable).Explanation This indicates that the LB process can not run because all prerequisite conditions have not been met. The prerequisite conditions are 2 active interfaces and LB enabled.
Recommended Action Check the interface configuration to make sure at least 2 interfaces are operational. Also check LB configuration.
718066
Error Message %PIX|ASA-5-718066: Cannot add secondary address to interface interface_name, ip IP_address.Explanation LB requires a secondary address to be added to the outside interface. This event indicates that there was a failure in adding that secondary address.
Recommended Action Check the address being used as the secondary address and ensure that it is valid and unique. Check the configuration of the outside interface.
718067
Error Message %PIX|ASA-5-718067: Cannot delete secondary address to interface interface_name, ip IP_address.Explanation The deletion of the secondary address failed. This could indicate an addressing problem or an internal software error.
Recommended Action Check the addressing information of the outside interface and ensure that the secondary address is valid and unique. If the problem persists, contact the Cisco TAC.
718068
Error Message %PIX|ASA-5-718068: Start VPN Load Balancing in context context_ID.Explanation The LB process has been started and initialized.
Recommended Action Informational only.
718069
Error Message %PIX|ASA-5-718069: Stop VPN Load Balancing in context context_ID.Explanation The LB process has been stopped.
Recommended Action Informational only.
718070
Error Message %PIX|ASA-5-718070: Reset VPN Load Balancing in context context_ID.Explanation The LB process has been reset.
Recommended Action Informational only.
718071
Error Message %PIX|ASA-5-718071: Terminate VPN Load Balancing in context context_ID.Explanation The LB process has been terminated.
Recommended Action Informational only.
718072
Error Message %PIX|ASA-5-718072: Becoming master of Load Balancing in context context_ID.Explanation The security appliance has become the LB master.
Recommended Action Informational only.
718073
Error Message %PIX|ASA-5-718073: Becoming slave of Load Balancing in context context_ID.Explanation The security appliance has become the LB slave.
Recommended Action Informational only.
718074
Error Message %PIX|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 security appliance was unable to create one of these ACLs. This could 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 %PIX|ASA-5-718075: Peer IP_address access list not set.Explanation While removing a secure tunnel, the security appliance detected a peer entry that did not have an associated ACL.
Recommended Action Informational only.
718076
Error Message %PIX|ASA-5-718076: Fail to create tunnel group for peer IP_address.Explanation The security appliance experienced a failure when attempting to create a tunnel group for securing the communication between LB peers.
Recommended Action Verify that LB configuration is correct.
718077
Error Message %PIX|ASA-5-718077: Fail to delete tunnel group for peer IP_address.Explanation The security appliance experienced a failure when attempting to delete a tunnel group for securing the communication between LB peers.
Recommended Action Informational only.
718078
Error Message %PIX|ASA-5-718078: Fail to create crypto map for peer IP_address.Explanation The security appliance experienced a failure when attempting to create a crypto map for securing the communication between LB peers.
Recommended Action Verify that LB configuration is correct.
718079
Error Message %PIX|ASA-5-718079: Fail to delete crypto map for peer IP_address.Explanation The security appliance experienced a failure when attempting to delete a crypto map for securing the communication between LB peers.
Recommended Action Informational only.
718080
Error Message %PIX|ASA-5-718080: Fail to create crypto policy for peer IP_address.Explanation The security appliance experienced a failure when attempting to create a transform set to be used in securing the communication between LB peers. This could indicate an internal software problem.
Recommended Action If the problem persists, contact the Cisco TAC.
718081
Error Message %PIX|ASA-5-718081: Fail to delete crypto policy for peer IP_address.Explanation The security appliance experienced a failure when attempting to delete a transform set used in securing the communication between LB peers.
Recommended Action Informational only.
718082
Error Message %PIX|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, transform set, and so on.) is created dynamically. This syslog indicates that one or more such crypto parameters failed to be created or configured.
•
Recommended Action Examine the syslog message for other entries specific to the type of crypto parameters that failed to be created.
718083
Error Message %PIX|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. This syslog entry indicates that one or more crypto parameters failed to be deleted.
•
Recommended Action Examine the syslog message for other entries specific to the type of crypto parameters that failed to be deleted.
718084
Error Message %PIX|ASA-5-718084: Public/cluster IP not on the same subnet: public IP_address, mask netmask, cluster IP_addressExplanation The cluster IP address must be on the same subnet as the outside interface of the security appliance. This even indicates that it is not on the same network.
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 %PIX|ASA-5-718085: Interface interface_name has no IP address defined.Explanation The indicated interface does not have an IP address configured.
Recommended Action Configure an IP address for the interface.
718086
Error Message %PIX|ASA-5-718086: Fail to install LB NP rules: type rule_type, dst interface_name, port port.Explanation The security appliance experienced a failure when attempting to create a SoftNP ACL rule to be used in securing the communication between LB peers. This could indicate an internal software problem.
Recommended Action If the problem persists, contact the Cisco TAC.
718087
Error Message %PIX|ASA-5-718087: Fail to delete LB NP rules: type rule_type, rule rule_ID.Explanation The security appliance experienced a failure when attempting to delete SoftNP ACL rule used in securing the communication between LB peers.
Recommended Action Informational only.
718088
Error Message %PIX|ASA-7-718088: Possible VPN LB misconfiguration. Offending device MAC MAC_address.Explanation The presence of a duplicate master indicates that one of the LB peers may be misconfigured.
Recommended Action Check the LB 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 This message appears when the incoming e-mail proxy session could not be established because the maximum session limit has been reached. maximum_sessions is the maximum session number.
Recommended Action None required.
719002
Error Message %ASA-3-719002: Email Proxy session pointer from source_address has been terminated due to reason error.Explanation This message appears when the session has been terminated due to error. The possible errors are: adding session to session database fails; memory allocation fail; writing data to channel fail, and so on.The pointer is the pointer of the session structure, source_address is the e-mail proxy client IP address, and reason is the error type.
Recommended Action None required.
719003
Error Message %ASA-6-719003: Email Proxy session pointer resources have been freed for source_address.Explanation This message appears when the dynamic allocated session structure has been freed and set to NULL after the session terminated.The pointer is the pointer of the session structure, and source_address is the e-mail proxy client IP address.
Recommended Action None required.
719004
Error Message %ASA-6-719004: Email Proxy session pointer has been successfully established for source_address.Explanation A new incoming email 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 This message appears when an FSM has been created for an incoming new session.The NAME is the FSM instance name for the session, protocol is the e-mail protocol type (for example, POP3, IMAP, SMTP), pointer is the pointer of session structure, and source_address is the e-mail proxy client IP address.
Recommended Action None required.
719006
Error Message %ASA-7-719006: Email Proxy session pointer has timed out for source_address because of network congestion.Explanation This message appears due to network congestion and data cannot be sent to either an e-mail client or an e-mail sever. This starts the block timer. After the block timer is timed out, the session expires. The pointer is the pointer of session structure, and source_address is the e-mail proxy client IP address.
Recommended Action Retry the operation after a few minutes.
719007
Error Message %ASA-7-719007: Email Proxy session pointer cannot be found for source_address.Explanation This message appears when a matching session cannot be found in the session database. The session pointer is bad. The pointer is the pointer of session structure, and source_address is the e-mail proxy client IP address.
Recommended Action None required.
719008
Error Message %ASA-3-719008: Email Proxy service is shutting down.Explanation This message appears email proxy is disabled. All resources are cleaned up and all threads are terminated.
Recommended Action None required.
719009
Error Message %ASA-7-719009: Email Proxy service is starting.Explanation This message appears when the email proxy is enabled.
Recommended Action None required.
719010
Error Message %ASA-6-719010: protocol Email Proxy feature is disabled on interface interface_name.Explanation This message appears when 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, threads, and so on. The protocol is the e-mail proxy protocol type (for example, POP3, IMAP,SMTP), and interface_name is the security appliance interface name.
Recommended Action None required.
719011
Error Message %ASA-6-719011: Protocol Email Proxy feature is enabled on interface interface_name.Explanation This message appears when 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, threads, and so on. Subsequent calls only need to start listen threads for the particular protocol. The protocol is the e-mail proxy protocol type (for example, POP3, IMAP,SMTP), and interface_name is the security appliance interface name.
Recommended Action None required.
719012
Error Message %ASA-6-719012: Email Proxy server listening on port port for mail protocol protocol.Explanation This message appears when a listen channel is opened for a specific protocol on a configured port and adds it to a TCP select group. The port is the configured port number, and protocol is the e-mail proxy protocol type (for example, POP3, IMAP,SMTP).
Recommended Action None required.
719013
Error Message %ASA-6-719013: Email Proxy server closing port port for mail protocol protocol.Explanation This message appears when a listen channel is closed for a specific protocol on a configured port and removes it from the TCP select group. The port is the configured port number, and protocol is the e-mail proxy protocol type (for example, POP3, IMAP,SMTP).
Recommended Action None required.
719014
Error Message %ASA-5-719014: Email Proxy is changing listen port from old_port to new_port for mail protocol protocol.Explanation This message appears when a change is signaled in the listen port for the specified protocol. All enabled interfaces for that port have their listen channels closed and restarted listening on the new port. This is invoked from the CLI. The old_port is the old configured port number, new_port is the new configured port number, and protocol is the e-mail proxy protocol type (for example, POP3, IMAP,SMTP).
Recommended Action None required.
719015
Error Message %ASA-7-719015: Parsed emailproxy session pointer from source_address username: mailuser = mail_user, vpnuser = VPN_user, mailserver = serverExplanation This message appears when the username string is received from the client in the format vpnuser (name delimiter) mailuser (server delimiter) mailserver (for example: xxx:yyy@cisco.com). The name delimiter is optional. When the delimiter is not there, the VPN username and mail username is the same. The server delimiter is optional. When it is not present, this means the default configured mail server will be used. The pointer is the pointer for the session structure, source_address is the e-mail proxy client IP address, mail_user is the e-mail account username, VPN_user is the WebVPN username, and server is the e-mail server.
Recommended Action None required.
719016
Error Message %ASA-7-719016: Parsed emailproxy session pointer from source_address password: mailpass = ******, vpnpass= ******Explanation This message appears when 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. The pointer is the pointer of the session structure, and source_address is the e-mail proxy client IP address.
Recommended Action None required.
719017
Error Message %ASA-6-719017: WebVPN user: vpnuser invalid dynamic ACL.Explanation This message appears when the WebVPN session is aborted because the access control list has failed to parse for this user. The ACL determines what the user restrictions are on e-mail account accessing. The ACL is downloaded from the AAA server. Because of this error, it is unsafe to proceed with login. The vpnuser is the 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 foundExplanation This message appears when the access control list 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. The vpnuser is the WebVPN username, and acl_ID is the local configured ACL identification string.
Recommended Action Check the local ACL configuration.
719019
Error Message %ASA-6-719019: WebVPN user: vpnuser authorization failed.Explanation This message appears when 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. The vpnuser is the WebVPN username.
Recommended Action None required.
719020
Error Message %ASA-6-719020: WebVPN user vpnuser authorization completed successfully.Explanation This message appears when the ACL determines what the user restrictions are on e-mail account access. The user is authorized to access the e-mail account. The vpnuser is the WebVPN username.
Recommended Action No ne.
719021
Error Message %ASA-6-719021: WebVPN user: vpnuser is not checked against ACL.Explanation This message appears when the ACL determines what the user restrictions are on e-mail account access. The authorization checking using ACL is not enabled. The vpnuser is the WebVPN username.
Recommended Action Enable the ACL checking feature if necessary.
719022
Error Message %ASA-6-719022: WebVPN user vpnuser has been authenticated.Explanation This message appears when the username is authenticated by the AAA server. The vpnuser is the WebVPN username.
Recommended Action None required.
719023
Error Message %ASA-6-719023: WebVPN user vpnuser has not been successfully authenticated. Access denied.Explanation This message appears when the username is denied by the AAA server. The session will be aborted. The user is not allowed to access the e-mail account. The vpnuser is the WebVPN username.
Recommended Action None required.
719024
Error Message %ASA-6-719024: Email Proxy piggyback auth fail: session = pointer user=vpnuser addr=source_addressExplanation This message appears when 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. The pointer is the pointer of session structure, vpnuser is the WebVPN username, and source_address is the client IP address.
Recommended Action None required.
719025
Error Message %ASA-6-719025: Email Proxy DNS name resolution failed for hostname.Explanation This message appears when the hostname cannot be resolved with the IP address because it is not valid or there is no DNS server available. The hostname is the hostname that needs to be resolved.
Recommended Action Check DNS server availability and check whether the configured mail server name is valid.
719026
Error Message %ASA-6-719026: Email Proxy DNS name hostname resolved to IP_address.Explanation This message appears when the hostname has successfully been resolved with the IP address. The hostname is the hostname that needs to be resolved, and IP_address is the IP address resolved from the configured mail server name.
Recommended Action None required.
720001
Error Message %ASA-4-720001: (VPN-unit) Failed to initialize with Chunk Manager.Explanation This message occurs when the VPN failover subsystem fails to initialize with the memory buffer management subsystem. The unit is either "Primary" or "Secondary."
Recommended Action This message indicates a system-wide problem and the VPN failover subsystem cannot be started. Examine the syslog messages for any sign of system-level initialization problems.
720002
Error Message %ASA-6-720002: (VPN-unit) Starting VPN Stateful Failover Subsystem...Explanation This message appears when the VPN failover subsystem is starting and the system boots up. The unit is either "Primary" or "Secondary."
Recommended Action None required.
720003
Error Message %ASA-6-720003: (VPN-unit) Initialization of VPN Stateful Failover Component completed successfullyExplanation This message appears when the VPN failover subsystem's initialization is completed at boot time. The unit is either "Primary" or "Secondary."
Recommended Action None required.
720004
Error Message %ASA-6-720004: (VPN-unit) VPN failover main thread started.Explanation This message appears when the VPN failover's main processing thread is started at boot time. The unit is either "Primary" or "Secondary."
Recommended Action None required.
720005
Error Message %ASA-6-720005: (VPN-unit) VPN failover timer thread started.Explanation This message appears when the VPN failover timer processing thread is started at boot time. The unit is either "Primary" or "Secondary."
Recommended Action None required.
720006
Error Message %ASA-6-720006: (VPN-unit) VPN failover sync thread started.Explanation This message appears when the system's bulk synchronization processing thread is started at boot time. The unit is either "Primary" or "Secondary."
Recommended Action None required.
720007
Error Message %ASA-4-720007: (VPN-unit) Failed to allocate chunk from Chunk Manager.Explanation This message appears when the set of preallocated memory buffers is running out. The unit is either "Primary" or "Secondary."
Recommended Action This message indicates a resource issue. The system may be under heavy load when too many messages are being processed. This condition may be improved later when the VPN failover subsystem processes outstanding messages and frees up memory previously allocated.
720008
Error Message %ASA-4-720008: (VPN-unit) Failed to register to High Availability Framework.Explanation This message appears when the VPN failover subsystem fails to register to the core failover subsystem. The unit is either "Primary" or "Secondary."
Recommended Action The VPN failover subsystem cannot be started. This may be caused by initialization problems of other subsystems. Search the syslog message for any sign of system-wide initialization problems.
720009
Error Message %ASA-4-720009: (VPN-unit) Failed to create version control block.Explanation This message appears when the VPN failover subsystem fails to create a version control block. This step is required for VPN failover subsystem to find out the backward compatible firmware versions for the current release. The unit is either "Primary" or "Secondary."
Recommended Action The VPN failover subsystem cannot be started. This may be caused by initialization problems of other subsystems. Search the syslog message for any sign of system-wide initialization problems.
720010
Error Message %ASA-6-720010: (VPN-unit) VPN failover client is being disabledExplanation This message appears when an operator enables failover without defining a failover key. In order to use a VPN failover, a failover key must be defined. The unit is either "Primary" or "Secondary."
Recommended Action Use the failover key command to define a shared secret key between the active and standby unit.
720011
Error Message %ASA-4-720011: (VPN-unit) Failed to allocate memoryExplanation This message appears when the VPN failover subsystem cannot allocate a memory buffer. This indicates a system-wide resource problem. The unit is either "Primary" or "Secondary."
Recommended Action The system may be under heavy load. This condition may be improved later when you reduce the load on the system by reducing incoming traffic. By reducing incoming traffic, memory allocated for processing the existing work load will be available and the system 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 This message appears when the VPN failover subsystem cannot update IPSec-related runtime data because the corresponding IPSec tunnel has been deleted on the standby unit. The unit is either "Primary" or "Secondary."
Recommended Action None required.
720013
Error Message %ASA-4-720013: (VPN-unit) Failed to insert certificate in trust point trustpoint_nameExplanation This message appears when the VPN failover subsystem attempts to insert a certificate in the trust point. The unit is either "Primary" or "Secondary" and trustpoint_name is the name of the trust point.
Recommended Action Check the certificate content to determine if it is invalid.
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 This message appears when there is no security association linked to the Phase 2 connection entry. The unit is either "Primary" or "Secondary," message_number is the message ID of the Phase 2 connection entry, mine is the My Phase 1 cookie, and his is the peer's Phase 1 cookie.
Recommended Action None required.
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 This message appears when the corresponding Phase 1 security association for the given Phase 2 connection entry cannot be found. The unit is either "Primary" or "Secondary," message_number is the message ID of the Phase 2 connection entry, mine is the My Phase 1 cookie, and his is the peer's Phase 1 cookie.
Recommended Action None required.
720016
Error Message %ASA-5-720016: (VPN-unit) Failed to initialize default timer #index.Explanation This message appears when the VPN failover subsystem fails to initialize the given timer event. The unit is either "Primary" or "Secondary" and index is the internal index of the timer event.
Recommended Action The VPN failover subsystem cannot be started at boot time. Search the syslog message for any sign of system-wide initialization problems.
720017
Error Message %ASA-5-720017: (VPN-unit) Failed to update LB runtime dataExplanation This message appears when the VPN failover subsystem fails to update the VPN load balancing runtime data. The unit is either "Primary" or "Secondary."
Recommended Action None required.
720018
Error Message %ASA-5-720018: (VPN-unit) Failed to get a buffer from the underlying core high availability subsystem. Error code code.Explanation This message appears when the system may be under heavy load. The VPN failover subsystem fails to obtain a failover buffer. The unit is either "Primary" or "Secondary" and code is the 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 system will free up memory allocated for processing the incoming load.
720019
Error Message %ASA-5-720019: (VPN-unit) Failed to update cTCP statistics.Explanation This message appears when the VPN failover subsystem fails to update the IPSec/cTCP-related statistics. The unit is either "Primary" or "Secondary."
Recommended Action None required. Updates are sent periodically, so the standby unit's 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 This message appears when the VPN failover subsystem fails to send a periodic timer message to the standby unit. The unit is either "Primary" or "Secondary" and type is the type of timer message.
Recommended Action None required. The periodic timer message will be resent during the next timeout.
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 fails to send a non-block message.
•
•
•
Recommended Action This is a temporary condition causes by system under load or out of system resources. The system condition will improve as more system resources are freed up.
720022
Error Message %ASA-4-720022: (VPN-unit) Cannot find trust point trustpointExplanation An error is encountered when VPN failover subsystem attempts to look up a trust point by name.
•
•
Recommended Action The trust point may be deleted by an operator.
720023
Error Message %ASA-6-720023: (VPN-unit) HA status callback: Peer is not present.Explanation This is an informational message. VPN failover subsystem is notified by the core failover subsystem when the local device detected a peer is available or becomes unavailable.
•
•
Recommended Action None required.
720024
Error Message %ASA-6-720024: (VPN-unit) HA status callback: Control channel is status.Explanation This is an informational message indicating whether 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."
•
•
Recommended Action None required.
720025
Error Message %ASA-6-720025: (VPN-unit) HA status callback: Data channel is status.Explanation This is an informational message indicating whether the failover data channel is up or down.
•
•
Recommended Action None required.
720026
Error Message %ASA-6-720026: (VPN-unit) HA status callback: Current progression is being aborted.Explanation This message is generated only when an operator or other external condition applies and causes the current failover progression to abort before the failover peer agrees on the role (either active or standby). One example is when the failover active command is entered on the standby unit during the negotiation. Another example is the active unit is being rebooted.
•
Recommended Action None required.
720027
Error Message %ASA-6-720027: (VPN-unit) HA status callback: My state state.Explanation This informational message is generated whenever the state of the local failover device is changed.
•
•
Recommended Action None required.
720028
Error Message %ASA-6-720028: (VPN-unit) HA status callback: Peer state state.•
•
Explanation This informational message is generated to report the current state of the failover peer.
Recommended Action None required.
720029
Error Message %ASA-6-720029: (VPN-unit) HA status callback: Start VPN bulk sync state.•
Explanation This is an informational message generated when the active unit is ready to send all the state information to the standby unit.
Recommended Action None required.
720030
Error Message %ASA-6-720030: (VPN-unit) HA status callback: Stop bulk sync state.•
Explanation This is an informational message generated when the active unit finishes sending all the state information to the standby unit.
Recommended Action None required.
720031
Error Message %ASA-7-720031: (VPN-unit) HA status callback: Invalid event received. event=event_ID.Explanation This message is generated when VPN failover subsystem receives an invalid callback event from the underlying failover subsystem.
•
•
Recommended Action This is a debug message.
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 This is an informational message generated by VPN failover subsystem when a status update is notified by the underlying failover subsystem.
•
•
•
•
•
•
•
•
Recommended Action None required.
720033
Error Message %ASA-4-720033: (VPN-unit) Failed to queue add to message queue.Explanation This message indicates that system resources may be running low. An error is encountered when VPN failover subsystem attempts to queue an internal message.
•
Recommended Action This may be a temporary condition indicating that the system is under heavy load and VPN failover subsystem cannot allocate resource to handle incoming traffic. This error condition may goes away if the current load of the system reduces 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 is encountered when VPN failover subsystem attempts to process an invalid message type.
•
•
Recommended Action This is a debug message.
720035
Error Message %ASA-5-720035: (VPN-unit) Fail to look up CTCP flow handleExplanation The cTCP flow may be deleted on the standby unit before VPN failover subsystem attempts to do a lookup.
•
Recommended Action Look for any sign of cTCP flow deletion in the syslog message to determine reason (for example, idle timeout) of why the flow is deleted.
720036
Error Message %ASA-5-720036: (VPN-unit) Failed to process state update message from the active peer.Explanation An error is encountered when VPN failover subsystem attempts to process a state update message received by the standby unit.
•
Recommended Action This may be a temporary condition due to 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 This is an informational message reporting the status of the current failover progression.
Recommended Action None required.
720038
Error Message %ASA-4-720038: (VPN-unit) Corrupted message from active unit.Explanation The standby unit receives a corrupted message from the active unit. Messages from active unit are corrupted. This may be caused by incompatible firmware running between the active and standby unit.
•
Recommended Action This is an informational message indicating 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 stateExplanation This is an informational message indicating the local unit has become the active unit of the failover pair.
•
Recommended Action None required.
720040
Error Message %ASA-6-720040: (VPN-unit) VPN failover client is transitioning to standby state.Explanation This is an informational message indicating the local unit has become the standby unit of the failover pair.
•
Recommended Action None required.
720041
Error Message %ASA-7-720041: (VPN-unit) Sending type message id to standby unitExplanation This is a debug message indicating a message is sent from the active unit to the standby unit.
•
•
•
Recommended Action None required.
720042
Error Message %ASA-7-720042: (VPN-unit) Receiving type message id from active unitExplanation This is a debug message indicating a message is received by the standby unit.
•
•
•
Recommended Action None required.
720043
Error Message %ASA-4-720043: (VPN-unit) Failed to send type message id to standby unitExplanation An error was encountered when VPN failover subsystem attempts to send a message from the active unit to the standby unit. This may be caused by 720018 where the core failover subsystem runs out of failover buffer or the failover lan link is down.
•
•
•
Recommended Action Use the show failover command to see if the failover pair is running in good condition and the failover lan link is "up."
720044
Error Message %ASA-4-720044: (VPN-unit) Failed to receive message from active unitExplanation An error is encountered when VPN failover subsystem attempts to receive a message on the standby unit. This may be caused by a corrupted message, no enough memory to be allocated for storing the incoming message.
•
Recommended Action Use the show failover command and look for receive errors to determine if this is VPN failover specific problems or a general failover issue. Corrupted messages may be caused by incompatible firmware versions running on active and standby unit. Use the show memory command to determine if there is a low memory condition.
720045
Error Message %ASA-6-720045: (VPN-unit) Start bulk syncing of state information on standby unit.Explanation This is an information message indicating the standby unit has been notified to start receiving bulk synchronization information from the active unit.
•
Recommended Action None required.
720046
Error Message %ASA-6-720046: (VPN-unit) End bulk syncing of state information on standby unitExplanation This is an information message indicating the standby unit has been notified that bulk synchronization from the active unit is completed.
•
Recommended Action None required.
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 was encountered when the VPN failover subsystem attempted to synchronize a node secret file for the SDI server on the standby unit. The SDI node secret file is stored in flash. This error may indicate that the flash file system is full or corrupted.
•
•
Recommended Action Use the dir command to display the flash contents. Node secret file has a file name "ip.sdi."
720048
Error Message %ASA-7-720048: (VPN-unit) FSM action trace begin: state=state, last event=event, func=function.•
•
•
•
Explanation This is a debug message indicating a VPN failover subsystem finite state machine function is started.
Recommended Action None required.
720049
Error Message %ASA-7-720049: (VPN-unit) FSM action trace end: state=state, last event=event, return=return, func=function.Explanation This is a debug message indicating a VPN failover subsystem finite state machine function is completed.
•
•
•
•
•
Recommended Action None required.
720050
Error Message %ASA-7-720050: (VPN-unit) Failed to remove timer. ID = id.Explanation This is a debug message indicating that a timer cannot be removed from the timer processing thread.
•
•
Recommended Action None required.
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 was encountered when the VPN failover subsystem attempted to add a node secret file for the SDI server on the standby unit. The SDI node secret file is stored in flash. This error may indicate that the flash file system is full or corrupted.
•
•
Recommended Action Enter the dir command to display the flash contents. Node secret file has a file name "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 was encountered when the VPN failover subsystem attempted 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 is problem reading the flash file system.
•
•
Recommended Action Use the dir command to display the flash contents. Node secret file has a file name "ip.sdi."
720053
Error Message %ASA-4-720053: (VPN-unit) Failed to add cTCP IKE rule during bulk sync, peer=IP_address, port=portExplanation An error is encountered when VPN failover subsystem attempts to load an cTCP IKE rule on the standby unit during bulk synchronization.
•
•
•
Recommended Action The standby unit may be under heavy load and the new IKE rule request timeout before completion.
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 and cannot be updated. The corresponding IPSec over cTCP tunnel may not be functioning after failover.
•
•
•
Recommended Action The cTCP database may be full or a record with the same peer IP address and port number exists already. 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 This message will be displayed and the VPN subsystem will not be started if not running in single (non-transparent) mode.
•
Recommended Action Configure the device for the appropriate mode to support VPN failover and restart the device.
720056
Error Message %ASA-6-720056: (VPN-unit) VPN Stateful failover Message Thread is being disabled.Explanation This is an informational message indicating the VPN failover subsystem's main message processing thread is disabled when user attempts to enable failover but failover key is not defined. Failover key is required for VPN failover.
•
Recommended Action None required.
720057
Error Message %ASA-6-720057: (VPN-unit) VPN Stateful failover Message Thread is enabled.Explanation This is an informational message indicating the VPN failover subsystem's main message processing thread is enabled when failover is enable and a failover key is defined.
•
Recommended Action None required.
720058
Error Message %ASA-6-720058: (VPN-unit) VPN Stateful failover Timer Thread is disabled.Explanation This is an informational message indicating the VPN failover subsystem's main timer processing thread is disabled when failover key is not defined and failover is enable.
•
Recommended Action None required.
720059
Error Message %ASA-6-720059: (VPN-unit) VPN Stateful failover Timer Thread is enabled.Explanation This is an informational message indicating the VPN failover subsystem's main timer processing thread is enabled when failover key is defined and failover is enable.
•
Recommended Action None required.
720060
Error Message %ASA-6-720060: (VPN-unit) VPN Stateful failover Sync Thread is disabled.Explanation This is an informational message indicating the VPN failover subsystem's main bulk synchronization processing thread is disabled when failover is enabled but failover key is not defined.
•
Recommended Action None required.
720061
Error Message %ASA-6-720061: (VPN-unit) VPN Stateful failover Sync Thread is enabled.Explanation This is an informational message indicating the VPN failover subsystem's main bulk synchronization processing thread is enabled when failover is enable and failover key is defined.
•
Recommended Action None required.
720062
Error Message %ASA-6-720062: (VPN-unit) Active unit started bulk sync of state information to standby unit.Explanation This is an informational message indicating the VPN failover subsystem's active unit has started bulk synchronization of state information to the standby unit.
•
Recommended Action None required.
720063
Error Message %ASA-6-720063: (VPN-unit) Active unit completed bulk sync of state information to standby.Explanation This is an informational message indicating the VPN failover subsystem's active unit has completed bulk synchronization state information to the standby unit.
•
Recommended Action None required.
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 was encountered 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 syslog message.
720065
Error Message %ASA-4-720065: (VPN-unit) Failed to add new cTCP IKE rule, peer=peer, port=port.Explanation An error is encountered when VPN failover subsystem attempts to add new IKE rule for the cTCP database entry on the standby unit.
•
•
•
Recommended Action The system may be under heavy load and the request for adding cTCP IKE rule timeout and never completed. This may be a temporary condition.
720066
Error Message %ASA-4-720066: (VPN-unit) Failed to activate IKE database.Explanation An error was encountered when the VPN failover subsystem attempted 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 in good condition and/or look for other IKE related errors in the syslog message.
720067
Error Message %ASA-4-720067: (VPN-unit) Failed to deactivate IKE database.Explanation An error was encountered when the VPN failover subsystem attempted to deactivate the IKE security association database while the active unit was transitioning to the standby state. There may be resources-related issues on the active unit that prevent the IKE security association database from deactivating.
•
Recommended Action Enter the show failover command to see if the failover pair is still in good condition and/or look for IKE related errors in the syslog message.
720068
Error Message %ASA-4-720068: (VPN-unit) Failed to parse peer message.Explanation An error is encountered when VPN failover subsystem attempts to parse a peer message received on the standby unit.
•
Recommended Action The peer message received on the standby unit cannot be parsed. Make sure both active/standby units are running the same versions of firmware. Also, use the show failover command to ensure the failover pair is still in good condition.
720069
Error Message %ASA-4-720069: (VPN-unit) Failed to activate cTCP database.Explanation An error was encountered when the VPN failover subsystem attempted 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.
•
Recommended Action Enter the show failover command to see if the failover pair is still in good condition and/or look for other cTCP related errors in the syslog message.
720070
Error Message %ASA-4-720070: (VPN-unit) Failed to deactivate cTCP database.Explanation An error was encountered when the VPN failover subsystem attempted to deactivate the cTCP database while the active unit was transitioning to the standby state. There may be resources-related issues on the active unit that prevent the cTCP database from deactivating.
•
Recommended Action Use the show failover command to see if the failover pair is still in good condition and/or look for cTCP related errors in the syslog message.
720071
Error Message %ASA-5-720071: (VPN-unit) Failed to update cTCP dynamic data.Explanation An error was encountered while the VPN failover subsystem attempted to update cTCP dynamic data.
•
Explanation This may be a temporary condition. Since this is a periodic update, wait to see if the same error occurs. Also, look for other failover related messages in the syslog message.
720072
Error Message %ASA-5-720072: Timeout waiting for Integrity Firewall Server [interface,ip] to become available.Explanation In an active/standby failover setup, the SSL connection between a Zonelab Integrity Server and the security appliance needs to be re-established after a failover. This syslog message is generated if the Zonelab Integrity Server cannot re-establish a connection before timeout.
•
•
Recommended Action Check that the configuration on the security appliance and the Zonelab Integrity Server match, and verify communication between the security appliance and the Zonelab Integrity Server.
720073
Error Message %ASA-4-720073: (VPN-unit) Fail to insert certificate in trust point trustpoint on the standby unit.Explanation An error is encountered when VPN failover subsystem attempts to insert a certificate in the trust point. This error may be caused by invalid content of the certificate.
•
•
Recommended Action Performs a "write standby" on the active unit to replicate the certificate to the standby unit manually. Search in the syslog message to see if there is any failover/PKI related errors.
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.
•
Recommended Action None required.
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. This is an informational message reporting the incoming event, the new state of the local device, and the new state of the failover peer.
•
•
•
•
Recommended Action None required.
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 event notified by the core HA component. This is an informational message reporting the incoming event, the new state of the local device, and the new state of the failover peer.
•
•
•
•
Recommended Action None required.
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. This message reports a successful installation of the WebVPN access list on the standby unit.
•
•
Recommended Action None required.
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. This message indicates that the access list failed to be installed on the standby unit. One possibility is that the access list has existed on the standby unit already.
•
•
Recommended Action Issue a show access-list command on both the active and standby unit. Compare the content of the output and determine whether there is any discrepancy. Re-sync the standby unit, if needed, by applying the "write standby" CLI on the active unit.
721006
Error Message %ASA-6-721006: (device) Update access list list_name on standby unit.Explanation An informational message indicating that the content of the access list has been updated on the standby unit.
•
•
Recommended Action None required.
721007
Error Message %ASA-4-721007: (device) Fail to update access list list_name on standby unit.Explanation This message indicates that an error condition is encountered while the standby unit attempts to update a WebVPN-specific access list. One possibility is that the access list cannot be located on the standby unit.
•
•
Recommended Action Issue a show access-list command on both the active and standby unit. Compare the content of the output and determine whether there is any discrepancy. Re-sync the standby unit if needed by applying the "write standby" CLI 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 the same access list to be removed. This is an informational message indicating that a WebVPN-specific access list has been removed from the standby unit.
•
•
Recommended Action None required.
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 to be removed. This message indicates that an error condition was encountered when an attempt was made to remove the corresponding access list on the standby unit. One possibility may be that the access list did not exist on the standby unit.
•
•
Recommended Action Issue a show access-list command on both the active and standby unit. Compare the content of the output and determine whether there is any discrepancy. Re-sync the standby unit if needed by applying the "write standby" CLI on the active unit.
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. This is an informational message indicating that a new access list rule is added successfully on the standby unit.
•
•
•
Recommended Action None required.
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. This message indicates an error condition is encountered when an attempt is made to add a new access list rule to the standby unit. One possible situation is that the same access list rule exists on the standby unit.
•
•
•
Recommended Action Issue a show access-list command on both the active and standby unit. Compare the content of the output and determine if there is any discrepancy. Re-sync the standby unit if needs to through applying the "write standby" CLI 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. This is an informational message indicating that an APCF XML file is installed successfully on the standby unit. Using the dir command on the standby unit will show that the XML file exists in the flash file system.
•
•
Recommended Action None required.
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. This is an error message indicating that an APCF XML file failed to install on the standby unit.
•
•
Recommended Action Perform a dir command on both the active and standby unit. Compare the directory listing and determine if there is any discrepancy. Re-sync the standby unit if needs to through applying the "write standby" CLI 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. This is a message indicating that an APCF XML file is removed from the standby unit successfully.
•
•
Recommended Action None required.
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. This message indicates an error condition occurred when an attempt is made to remove an APCF XML file from the standby unit. One possible cause may be the file was not installed on the standby unit.
•
•
Recommended Action Perform 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, it may be OK to ignore this message. Otherwise, try to disable the file by using the no apcf file_name command under the webvpn configuration submode.
721016
Error Message %ASA-6-721016: (device) WebVPN session for client user user_name, IP ip_address has been created.Explanation Indicates that a remote WebVPN user has logged in successfully and the login information has been installed on the standby unit.
•
•
•
Recommended Action None required.
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. This message indicates an error condition occurred while replicating the login information to the standby unit.
•
•
•
Recommended Action Perform a show vpn-sessiondb detail webvpn command for regular WebVPN user, or show vpn-sessiondb detail svc for WebVPN SVC user on both the active and standby unit. Compare the entries and determine whether the same user session record appears on both devices. Re-sync the standby unit if needed by applying 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. This is an informational message indicating that a WebVPN user record was removed from the standby unit successfully.
•
•
•
Recommended Action None required.
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. This message indicates that an error was encountered when an attempt was made to remove a WebVPN user record from the standby unit.
•
•
•
Recommended Action Perform a show vpn-sessiondb detail webvpn command for regular WebVPN user, or show vpn-sessiondb detail svc for WebVPN SVC user on both the active and standby unit. Check whether there is any discrepancy. Re-sync the standby unit if needed by applying 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 SSL VPN client (SVC) was invalid.
Recommended Action Research as necessary to determine if this was caused by a bug 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.
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 Cisco TAC.
722007
Error Message %ASA-3-722007: Group group User user-name IP IP_address SVC Message: type-num/ERROR: messageExplanation This is a message from the SSL VPN client (SVC).
•
–
–
–
–
–
•
Recommended Action None required.
722008
Error Message %ASA-3-722008: Group group User user-name IP IP_address SVC Message: type-num/ERROR: messageExplanation This is a message from the SSL VPN client (SVC).
•
–
–
–
–
–
•
Recommended Action None required.
722009
Error Message %ASA-3-722009: Group group User user-name IP IP_address SVC Message: type-num/ERROR: messageExplanation This is a message from the SVC client.
•
–
–
–
–
–
•
Recommended Action None required.
722010
Error Message %ASA-5-722010: Group group User user-name IP IP_address SVC Message: type-num/NOTICE: message•
–
–
–
–
–
•
Recommended Action None required.
722011
Error Message %ASA-5-722011: Group group User user-name IP IP_address SVC Message: type-num/NOTICE: message•
–
–
–
–
–
•
Recommended Action None required.
722012
Error Message %ASA-5-722012: Group group User user-name IP IP_address SVC Message: type-num/INFO: message–
–
–
–
–
–
•
Recommended Action None required.
722013
Error Message %ASA-6-722013: Group group User user-name IP IP_address SVC Message: type-num/INFO: message•
–
–
–
–
–
•
Recommended Action None required.
722014
Error Message %ASA-6-722014: Group group User user-name IP IP_address SVC Message: type-num/INFO: message•
–
–
–
–
–
•
Recommended Action None required.
722015
Error Message %ASA-4-722015: Group group User user-name IP IP_address Unknown SVC frame type: type-numExplanation The SSL VPN client (SVC) sent an invalid frame type to the device.
•
Recommended Action This could be caused by an SVC version incompatibility. 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-lengthExplanation The expected amount of data was not available from the SSL VPN client (SVC).
Recommended Action This could be caused by an SVC version incompatibility. Verify the SVC version.
722017
Error Message %ASA-4-722017: Group group User user-name IP IP_address Bad SVC framing: 525446, reserved: 0Explanation The SSL VPN client (SVC) send a badly framed datagram.
Recommended Action This could be caused by an SVC version incompatibility. 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-versionExplanation The SSL VPN client (SVC) sent a version unknown to the device.
Recommended Action This could be caused by an SVC version incompatibility. Verify the SVC version.
722019
Error Message %ASA-4-722019: Group group User user-name IP IP_address Not enough data for an SVC header: lengthExplanation The expected amount of data was not available from the SSL VPN client (SVC).
Recommended Action This could be caused by an SVC version incompatibility. 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 connectionExplanation Address assignment failed for the AnyConnect session. No IP addresses are available.
•
•
•
•
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 resourcesExplanation 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) compressionExplanation The TCP or UDP connection was established with or without compression.
Recommended Action None required.
722023
Error Message %ASA-6-722023: Group group User user-name IP IP_address SVC connection terminated {with|without} compressionExplanation Informative message only.
Recommended Action None required.
722024
Error Message %ASA-6-722024: SVC Global Compression EnabledExplanation Indicates that subsequent SSL VPN Client (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 DisabledExplanation Indicates that subsequent SSL VPN Client (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 resetExplanation A compression error occurred. The SSL VPN client (SVC) and device corrected it.
Recommended Action None required.
722027
Error Message %ASA-6-722027: Group group User user-name IP IP_address SVC decompression history resetExplanation A decompression error occurred. The SSL VPN client (SVC) and device corrected it.
Recommended Action None required.
722028
Error Message %ASA-5-722028: Group group User user-name IP IP_address Stale SVC connection closed.Explanation An unused SSL VPN client (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_resetsExplanation Lists the number of connections, reconnections, and resets that have occurred. 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 security appliance administrator.
•
•
•
•
Recommended Action If there are many conns or DPD conns, the user may be having problems connecting and may experience poor performance. The SSL VPN client (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 dropsExplanation End of session statistics are being recorded.
•
•
•
•
•
Recommended Action None required.
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.
•
•
•
•
•
Recommended Action None required.
722032
Error Message %ASA-5-722032: Group group User user-name IP IP_address New SVC connection replacing old connection.Explanation A new SSL VPN client (SVC) connection is replacing an existing one.
Recommended Action User may be having trouble connecting. The SVC log should be examined.
722033
Error Message %ASA-5-722033: Group group User user-name IP IP_address First SVC connection established for SVC session.Explanation Informative message only.
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 This message occurs during a reconnection attempt. A new SSL VPN client (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 security appliance.
Recommended Action The user may be having trouble connecting. The device and SVC log should be examined.
722035
Error Message %ASA-3-722035: Group group User user-name IP IP_address Received large packet length threshold num).Explanation A large packet was received from the client.
•
•
Recommended Action Determine if the SVC is compatible with the security appliance and correct as necessary.
722036
Error Message %ASA-3-722036: 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. This could also be due to compression of non-compressible data.
•
•
Recommended Action Turn off SVC compression, otherwise, none required.
722037
Error Message %ASA-5-722037: Group group User user-name IP IP_address SVC closing connection: reason.Explanation An SSL VPN client (SVC) connection was terminated for the given reason.
•
Recommended Action This may be normal, or the user may be having trouble connecting. The SVC log should be examined.
722038
Error Message %ASA-5-722038: Group group-name User user-name IP IP_address SVC terminating session: reason.Explanation An SSL VPN client (SVC) session was terminated for the given reason.
•
Recommended Action This may be normal, or the user may be having trouble connecting. The SVC log should be examined if the reason for termination is 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 ('vpn-filter' command).
•
•
•
•
Recommended Action Validate the vpn-filter and ipv6-vpn-filter configuration on the ASA and the filter parameters on the AAA (RADIUS) server. Ensure that 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 appliedExplanation The type of ACL to be applied is incorrect. An IPv4 ACL has been configured as an IPv6 ACL ('ipv6-vpn-filter') command).
•
•
•
•
Recommended Action Validate the vpn-filter and ipv6-vpn-filter configuration on the ASA and the filter parameters on the AAA (RADIUS) server. Ensure that correct type of ACL is specified.
722041
Error Message %ASA-4-722041: TunnelGroup tunnel_group GroupPolicy group_policy User username IP peer_address No IPv6 address available for SVC connection\n.Explanation An IPv6 address was not available for assignment to the remote SVC client.
•
Recommended Action Augment/Create 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/AnyConnect client is trying to connect.
•
•
•
Recommended Action Validate that the SVC/AnyConnect client is compatible with the adaptive security appliance.
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.
722044
Error Message %ASA-5-722044: Group group User user IP ip Unable to request ver address for SSL tunnel.Explanation An IP address could not be requested because of low memory on the adaptive security appliance.
•
•
•
•
Recommended Action Reduce the load on the adaptive security appliance 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 adaptive security appliance 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 adaptive security appliance cannot set up connection parameters. This is a defect in the adaptive security appliance software.
•
•
•
Recommended Action Contact the Cisco TAC for assistance.
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 with 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 with 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 with the svc-enable command. Validate the integrity and versions of the SVC images by reloading new images using the svc image command.
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 via 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 with the group-policy and username commands.
722051
Error Message %ASA-6-722051: Group group-policy User username IP public-ip Address assigned-ip assigned to sessionExplanation The specified address has been assigned to the given user.
•
•
•
•
Recommended Action None required.
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 security appliance. Older clients include the Cisco SSL VPN client (SVC) and the Cisco AnyConnect client earlier than Version 2.3.1.
•
•
•
•
Recommended Action Upgrade to a supported Cisco SSL VPN client.
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.
•
•
•
•
Recommended Action None required.
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 security appliance 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 properly 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:
•
•
•
•
•
•
723003
Error Message %ASA-7-723003: No memory for WebVPN Citrix ICA connection connection.Explanation The security appliance is running out of memory. The Citrix connection was rejected.
•
Recommended Action Verify that the security appliance is working properly. Pay special attention to memory and buffer usage. If the security appliance is under heavy load, buy more memory and upgrade the security appliance or reduce the load on the security appliance. If the problem persists, contact the Cisco TAC.
723004
Error Message %ASA-7-723004: WebVPN Citrix encountered bad flow control flow.Explanation ASA internal flow control mismatch.
Recommended Action This issue can be caused by massive data flow, such as might occur during stress testing or with a high volume of ICA connections. Reduce ICA connectivity to the security appliance. 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 security appliance 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 security appliance load, paying special attention to memory and buffer usage. If the security appliance is under heavy load, upgrade the security appliance, 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 security appliance.
Recommended Action Verify that the Citrix ICA client is working properly. In addition, check the network connection status between the Citrix ICA client and the security appliance, paying attention to packet loss and so forth. Resolve any abnormal network conditions. If the problem persists, contact the Cisco TAC.
723007
Error Message %ASA-7-723007: WebVPN Citrix ICA connection connection list is broken.Explanation ASA internal Citrix connection list is broken.
•
Recommended Action Verify that the security appliance is working properly, paying special attention to memory and buffer usage. If the security appliance is under heavy load, upgrade the security appliance, 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.
•
Recommended Action Verify that the security appliance is working properly. Notice if there is any memory/buffer leakage. If this issue happens frequently, capture information about memory usage, the network topology, and the conditions when this message is received. Send this information to Cisco TAC for review. Make sure 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 security appliance is under heavy load, upgrade the security appliance, 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 security appliance is under heavy load, upgrade the security appliance, add memory, or reduce the load. If the problem persists, contact the Cisco TAC.
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 Citrix connection that does not exist.
•
•
•
•
•
Recommended Action This 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. To eliminate the message, reduce the number of ICA connections to the security appliance, obtain more memory for the security appliance, 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.
•
•
•
Recommended Action Verify that the Citrix ICA client is working properly. In addition, check the network connection status between the ICA client and the security appliance, paying attention to packet loss and so forth. 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 Citrix SOCKS message format is incorrect.
•
•
•
Recommended Action Verify that the Citrix ICA client is working properly. In addition, check the network connection status between the ICA client and the security appliance, paying attention to packet loss and so forth. 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 security appliance, and between the security appliance and the Citrix server. Resolve any abnormal network conditions, especially delay and packet loss. Verify that the security appliance works properly, paying special attention to memory or buffer problems. If the security appliance is under heavy load, obtain more memory, upgrade the security appliance, 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 security appliance internal Citrix Secure Gateway is connected to the Citrix server.
•
•
•
•
•
•
Recommended Action None required.
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 as an error occurred when processing the CSD Host Integrity Check results on the security appliance.
•
•
•
Recommended Action Determine whether the client firewall is truncating long URLs. Uninstall CSD from the client and reconnect to the security appliance.
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 is able to properly 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 Indicates that a SSL handshake has started with the remote device.
•
•
•
•
•
Recommended Action None required.
725002
Error Message %ASA-6-725002 Device completed SSL handshake with remote_device interface_name: IP_address/portExplanation The SSL handshake has completed successfully with the remote device.
•
•
•
•
Recommended Action None required.
725003
Error Message %ASA-6-725003 SSL client interface_name: IP_address/port requesting to resume previous session.Explanation The remote device is trying to resume a previous SSL session.
•
•
•
Recommended Action None required.
725004
Error Message %ASA-6-725004 Device requesting certificate from SSL client interface_name: IP_address/port for authentication.Explanation The security appliance has requested a client certificate for authentication.
•
•
•
Recommended Action None required.
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 security appliance for authentication.
•
•
•
Recommended Action None required.
725006
Error Message %ASA-6-725006 Device failed SSL handshake with remote_device interface_name: IP_address/portExplanation The SSL handshake with the remote device has failed.
•
•
•
•
Recommended Action Look for 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.
•
•
•
•
Recommended Action None required.
725008
Error Message %ASA-7-725008 SSL client interface_name: IP_address/port proposes the following number cipher(s).Explanation Lists the number of ciphers proposed by the remote SSL device.
•
•
•
•
Recommended Action None required.
725009
Error Message %ASA-7-725009 Device proposes the following number cipher(s) to SSL server interface_name: IP_address/port.Explanation Lists the number of ciphers proposed to the SSL server.
•
•
•
•
Recommended Action None required.
725010
Error Message %ASA-7-725010 Device supports the following number cipher(s).Explanation Identifies the number of ciphers supported by the security appliance for a SSL session.
•
Recommended Action None required.
725011
Error Message %ASA-7-725011 Cipher[order]: cipher_nameExplanation This message always follows message 725008,725009 and 725010. It indicates the cipher name and its order of preference.
•
•
725012
Error Message %ASA-7-725012 Device chooses cipher: cipher_name for SSL session with client interface_name:IP_address/portExplanation Identifies the cipher that was chosen by the Cisco device for the SSL session.
•
•
•
•
Recommended Action None required.
725013
Error Message %ASA-7-725013 SSL Server interface_name:IP_address/port chooses cipher: cipher_nameExplanation Identifies the cipher that was chosen by the server for the SSL session.
•
•
•
•
Recommended Action None required.
725014
Error Message %ASA-7-725014 SSL lib error. Function: function Reason: reasonExplanation Identifies the reason for failure of the SSL handshake.
•
•
Recommended Action Include this message when reporting any SSL-related issue.
725015
Error Message %ASA-3-725015 Error verifying client certificate. Public key size in client certificate exceeds the maximum supported key size.Explanation Notice that the verification of a SSL client certificate failed due to unsupported (large) key size.
Recommended Action Use client certificates with key sizes less than or equal to 4096 bits.
726001
Error Message %PIX|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_nameExplanation This event is generated when an instant message (IM) inspection is performed on an IM message and the specified criteria is satisfied. The configured action is taken.
•
•
•
•
•
•
•
•
•
•
•
•
Recommended Action None required.
730001
Error Message %ASA-7-730001 Group groupname, User username, IP ipaddr: VLAN MAPPING to VLAN vlanidExplanation VLAN mapping succeeded
•
•
•
•
Recommended Action None required
730002
Error Message %ASA-7-730002 Group groupname, User username, IP ipaddr: VLAN MAPPING to VLAN vlanid failedExplanation VLAN Mapping failed.
•
•
•
•
Recommended Action Verify all the VLAN Mapping related configurations are correct, especially the VLAN ID itself must be valid.
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, none required.
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.
730010
Error Message %ASA-7-730010 Group groupname, User username, IP ipaddr, VLAN Mapping is enabled on VLAN <vlanid>.Explanation VLAN Mapping is enabled on the session.
•
•
•
•
Recommended Action None required.
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_cntExplanation The specified object in the syslog message has exceeded the specified burst threshold rate or average threshold rate. The object can be drop activity of a host, TCP/UDP port, IP protocol, or various drops due to potential attacks. It indicates the system is under potential attack.
•
- 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" that would signify port 80, with well-known protocol HTTP.)
•
•
•
The following three examples show how these variables occur:
For an interface drop due to 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 due to 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 due to 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"
Recommended Action Perform the following steps according to the specified object type that appears in the message:
1.
–
–
–
–
–
–
–
–
–
–
–
Check whether the drop rate is acceptable for the running environment.
2.
–
–
–
–
–
–
–
–
–
–
3.
4.
Note
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 Scanning detected. This syslog message is sent when the system detects that a specific host (or several hosts in the same 1024-node subnet) either is scanning the network (attacking), or is being scanned (targeted).
•
•
•
•
The following two examples depict 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, issue the show threat-detection statistics host <ip-address> <ip-mask> command to check the overall situation and then adjust the threshold rate of scanning-threat to appropriate value. Once the appropriate value is determined, an optional action can be taken to shun those host attackers (not subnet attacker) by configuring threat-detection scanning-threat shun-host. You may specify certain hosts or object groups in the shun-host except list. See the configuration guide for details. 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 listExplanation This message indicates that 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.
•
The following example shows how to implement this command:
%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, enter 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 entering the clear threat-detection shun <ip address> command. To remove all shunned hosts from the threat detection engine, enter the clear shun command.
If you receive this syslog message because an inappropriate threshold rate has been set to trigger the threat detection engine, then adjust the threshold rate by entering 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 listExplanation This message indicates that a host has been shunned by the threat detection engine. When you enter the clear-threat-detection shun command, the specified host will be removed from the shunned list.
•
The following example shows how to implement this command:
%ASA-4-733103: Threat-detection removes host 11.1.1.40 from shun list
Recommended Action None required.
731001
Error Message %ASA-6-731001 NAC policy added: name: policyname Type: policytype.Explanation A new nac-policy is added on ASA.
•
•
Recommended Action None required.
731002
Error Message %ASA-6-731002 NAC policy deleted: name: policyname Type: policytype.Explanation A NAC policy is removed from ASA
•
•
Recommended Action None required.
731003
Error Message %ASA-6-731003 nac-policy unused: name: policyname Type: policytype.Explanation The NAC policy is unused as there is an existing NAC policy with the same name but different type.
•
•
Recommended Action If the new NAC policy must be used, the existing NAC policy must be removed first. Otherwise, none required.
732001
Error Message %ASA-6-732001 Group groupname, User username, IP ipaddr, Fail to parse NAC-SETTINGS nac-settings-id, terminating connection.Explanation ASA cannot apply the NAC settings due to no memory.
•
•
•
•
Recommended Action Upgrade ASA memory. Resolve any errors in the log before this problem happens. 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 cannot be applied as there is a different one for the session.
•
•
•
•
•
Recommended Action If the new NAC settings must be applied, then all the active sessions that use it must be torn down first. Otherwise, none 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.
•
•
•
•
Recommended Action Verify the NAC settings configurations on the AAA server and ASA are both correct.
733104
Error Message %ASA-4-733104: TD_SYSLOG_TCP_INTERCEPT_AVERAGE_RATE_EXCEEDExplanation This message is generated when the system is under Syn flood attacks, if the average rate exceeds the configured threshold.
Recommended Action None required.
733105
Error Message %ASA-4-733105: TD_SYSLOG_TCP_INTERCEPT_BURST_RATE_EXCEEDExplanation This message is generated when the system is under Syn flood attacks, if the burst rate exceeds the configured threshold.
Recommended Action None required.
734001
Error Message %ASA-6-734001: DAP: User user, Addr ipaddr, Connection connection: The following DAP records were selected for this connection: DAP record namesExplanation Displays the DAP records that were selected for the connection.
•
•
•
- IPsec
- AnyConnect
- Clientless (web browser)
- Cut-Through-Proxy
- L2TP
•
Recommended Action None required.
734002
Error Message %ASA-5-734002: DAP: User user, Addr ipaddr: Connection terrminated by the following DAP records: DAP record namesExplanation Displays the DAP records that terminated the connection.
•
•
•
Recommended Action None required.
734003
Error Message %ASA-7-734003: DAP: User name, Addr ipaddr: Session Attribute: attr name/valueExplanation Displays the AAA and endpoint session attributes that are associated with the connection.
•
•
•
Recommended Action None required.
734004
Error Message %ASA-3-7340004: DAP: Processing error: Code numberExplanation Displays a DAP processing error.
•
Recommended Action Provide Cisco TAC with the syslog message and information about the conditions that generated this error.
737001
Error Message %ASA-7-737001: IPAA: Received message `message-type'Explanation A message has been received by the IP address assignment process.
•
Recommended Action None required.
737002
Error Message %ASA-3-737002: IPAA: Received unknown message 'num' variablesExplanation A message has been received by the IP address assignment process.
•
Recommended Action None required.
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.
•
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.
•
Recommended Action None required.
737006
Error Message %ASA-6-737006: IPAA: Local pool request succeeded for tunnel-group 'tunnel-group'Explanation The local pool request has succeeded.
•
Recommended Action None required.
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(s) 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 foundExplanation The tunnel-group was not found when trying to acquire an IP address for configuration.
•
Recommended Action Check the tunnel-group configuration. A software defect could cause this message to be generated. Contact the Cisco TAC and report the issue.
737009
Error Message %ASA-6-737009: IPAA: Client requested address ip-address, request failedExplanation 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.
•
Recommended Action Check the AAA server status and the status of IP local pools.
737010
Error Message %ASA-6-737010: IPAA: Client requested address ip-address, request succeededExplanation The remote-access client software requested the use of a particular address and successfully received this address.
•
Recommended Action None required.
737011
Error Message %ASA-5-737011: IPAA: requested address ip-address, not permitted by AAA, retryingExplanation 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•
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 syslog messages to identify the issue.
737013
Error Message %ASA-4-737013: IPAA: Error freeing address ip-address, not foundExplanation The ASA attempted to free an address, but it was not on the allocated list. It could be the result of a recent configuration change.
•
Recommended Action Validate your address assignment configuration. If this continues, it could be due to a software defect. Contact the TAC and report the issue.
737014
Error Message %ASA-6-737014: IPAA: Freeing AAA address ip-addressExplanation The ASA successfully released the IP address assigned via AAA.
•
Recommended Action None required.
737015
Error Message %ASA-6-737015: IPAA: Freeing DHCP address ip-addressExplanation The ASA successfully released the IP address assigned via DHCP.
•
Recommended Action None required.
737016
Error Message %ASA-6-737016: IPAA: Freeing local pool address ip-addressExplanation The ASA successfully released the IP address assigned via local pools.
•
Recommended Action None required.
737017
Error Message %ASA-6-737017: IPAA: DHCP request attempt num succeededExplanation The ASA successfully sent a request to a DHCP server.
•
Recommended Action None required.
737018
Error Message %ASA-5-737018: IPAA: DHCP request attempt num failedExplanation The ASA failed to send a request to a DHCP server.
•
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 poolsExplanation 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-addressExplanation The ASA is low on memory.
•
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.
737024
Error Message %ASA-5-737024: IPAA: Client requested address ip-address, already in use, retryingExplanation The client requested an IP address that is already in use. The request will be attempted using a new IP address.
•
Recommended Action None required.
737025
Error Message %ASA-5-737025: IPAA: Duplicate local pool address found, ip-address in quarantineExplanation 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.
•
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 poolExplanation The client has assigned the given address from a local pool.
•
Recommended Action None required.
737027
Error Message %ASA-3-737027: IPAA: No data for address requestExplanation A software defect has been encountered.
Recommended Action Contact the Cisco TAC and report the issue.
737028
Error Message %ASA-4-737028: IPAA: Unable to send ip-address to standby: communication failureExplanation 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 standbyExplanation The standby ASA accepted the IP address assignment.
•
Recommended Action None required.
737030
Error Message %ASA-4-737030: IPAA: Unable to send ip-address to standby: address in useExplanation 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.
•
Recommended Action Validate the failover configuration and status.
737031
Error Message %ASA-6-737031: IPAA: Removed ip-address from standbyExplanation The standby ASA cleared the IP address assignment.
•
Recommended Action None required.
737032
Error Message %ASA-4-737032: IPAA: Unable to remove ip-address from standby: address not foundExplanation The standby ASA did not have in use when the active ASA attempted to release it. The failover pair may be out of sync.
•
Recommended Action Validate the failover configuration and status.
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_allocatorExplanation This syslog is generated when the address assigned by AAA/DHCP /Local pool is already in use.
•
•
•
Recommended Action Validate the AAA/DHCP/Local pool address configurations. Overlap may occur.
742001
Error Message %ASA-3-742001: failed to read master key for password encryption from persistent storeExplanation An attempt to read the master password encryption key from the non-volatile 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 could 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 encryptionExplanation An attempt to read the key config-key password encryption command failed. The error may be caused by the following reasons:
•
•
•
•
•
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_textExplanation An attempt to save the master key to non-volatile memory failed. The actual reason is specified by the reason_text parameter. The reason could be an out-of-memory condition, or the non-volatile store could be inconsistent.
Recommended Action If the problem persists, reformat the non-volatile store that is used to save the key by running the write erase command. Before performing this step, make sure that you back up the out-of-the-box configuration. Then rerun the write erase command.
742004
Error Message %ASA-3-742004: failed to sync master key for password encryption, reason reason_textExplanation 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 withExplanation An attempt to decrypt a password failed. The password may have been encrypted using 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.
742006
Error Message %ASA-3-742006: password decryption failed due to unavailable memoryExplanation 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 memoryExplanation 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 errorExplanation 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 errorExplanation 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 Cisco TAC.
742010
Error Message %ASA-3-742010: encrypted password enc_pass is not well formedExplanation 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.
•
•
Recommended Action Reapply the configuration in question with a clear text password.
