Table Of Contents
System Log Messages
This chapter lists the Cisco ASA and PIX system log messages. The messages are listed numerically by message code.
Note
The messages shown in this guide apply to software Version 7.0 and higher. When a number is skipped from a sequence, the message is no longer in the security appliance code.
This chapter includes the following sections:
Messages 101001 to 199009
This section contains messages from 101001 to 199009.
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 2-1 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; otherwise, contact 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. Refer to Table 1-4 in Chapter 1, "Configuring Logging and SNMP," for possible values for the interface_number variable.
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.
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 system log 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 This is a failover message. This message is displayed when you enter the no failover command on the console. (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. This message 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 Cisco ASA is testing the specified network interface with the other unit of the failover pair. (Primary) can also be listed as (Secondary) for the secondary unit.
Recommended Action None required. The Cisco ASA 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 Cisco ASA fails to receive a message from the standby unit on that interface after the expected interval. (Primary) can also be listed as (Secondary) for the secondary unit.
Recommended Action None required.
105009
Error Message %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 Cisco ASA should recover. (Primary) can also be listed as (Secondary) for the secondary unit.
Recommended Action Use the show blocks command to monitor the current block memory.
105011
Error Message %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 Cisco ASA detects a partial configuration in memory. Normally, this is caused by an interruption in the replication service. (Primary) can also be listed as (Secondary) for the secondary unit.
Recommended Action Once the failover is detected by the Cisco ASA , the Cisco ASA automatically reloads itself and loads configuration from Flash memory and/or resynchronizes with another Cisco ASA . If failovers happen continuously, check the failover configuration and make sure both Cisco ASA 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 Cisco ASA 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 Cisco ASA detects a partial configuration in memory. Normally, this is caused by an interruption in the replication service. (Primary) can also be listed as (Secondary) for the secondary unit.
Recommended Action Once the failover is detected by the Cisco ASA , the Cisco ASA automatically reloads itself and loads the configuration from Flash memory and/or resyncs with another Cisco ASA . If failovers happen continuously, check the failover configuration and make sure that both Cisco ASA 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 Cisco ASA s are the same. This message indicates that the primary Cisco ASA is not able to verify the number of interfaces configured on the secondary Cisco ASA . This message indicates that the primary Cisco ASA is not able communicate with the secondary Cisco ASA over the failover interface. (Primary) can also be listed as (Secondary) for the secondary Cisco ASA .
Recommended Action Verify the failover LAN, interface configuration, and status on the primary and secondary Cisco ASA s. Make sure that the secondary Cisco ASA is running the Cisco ASA 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 Cisco ASA should run the same failover software version to act as a failover pair. This message indicates that the secondary Cisco ASA failover software version is not compatible with the primary Cisco ASA . Failover is disabled on the primary Cisco ASA . (Primary) can also be listed as (Secondary) for the secondary Cisco ASA .
Recommended Action Maintain consistent software versions between the primary and secondary Cisco ASA s 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 Cisco ASA is functioning. (Primary) can also be listed as (Secondary) for the secondary Cisco ASA .
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.
unit—Primary or secondary.
application—The name of the application, such as InterScan Security Card.
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 your security policy. 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 Cisco ASA , 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 your security policy.
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 Cisco ASA receives the reset, this message will appear. It can typically be ignored.
Recommended Action Prevent this system log 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 Cisco ASA discarded an inbound ICMP Echo Request packet with a destination address that corresponds to a PAT global address. The inbound packet is discarded because it cannot specify which PAT host should receive the packet.
Recommended Action None required.
106014
Error Message %PIX|ASA-3-106014: Deny inbound icmp src interface_name: IP_address dst interface_name: IP_address (type dec, code dec)Explanation The Cisco ASA 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 Cisco ASA discarded a TCP packet that has no associated connection in the Cisco ASA connection table. The Cisco ASA looks for a SYN flag in the packet, which indicates a request to establish a new connection. If the SYN flag is not set, and there is not an existing connection, the Cisco ASA discards the packet.
Recommended Action None required unless the Cisco ASA receives a large volume of these invalid TCP packets. If this is the case, trace the packets to the source and determine the reason these packets were sent.
106016
Error Message %PIX|ASA-2-106016: Deny IP spoof from (IP_address) to IP_address on interface interface_name.Explanation The Cisco ASA 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 conduit command to configure the Cisco ASA to discard packets with source addresses belonging to the internal network. Now that the icmp command has been implemented, the conduit command has been deprecated and is no longer guaranteed to work properly.
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 Cisco ASA received a packet with the IP source address equal to the IP destination, and the destination port equal to the source port. This message indicates a spoofed packet that is designed to attack systems. This attack is referred to as a Land Attack.
Recommended Action If this message persists, an attack may be in progress. The packet does not provide enough information to determine where the attack originates.
106018
Error Message %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 Cisco ASA discarded an IP packet with a teardrop signature containing either a small offset or fragment overlapping. This is a hostile event that circumvents the Cisco ASA or an Intrusion Detection System.
Recommended Action Contact the remote peer administrator or escalate this issue according to your security policy.
106021
Error Message %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 Cisco ASA .
This message appears when you have enabled Unicast RPF with the ip verify reverse-path command. This feature works on packets input to an interface; if it is configured on the outside, then the Cisco ASA checks packets arriving from the outside.
The Cisco ASA looks up a route based on the source_address. If an entry is not found and a route is not defined, then this system log message appears and the connection is dropped.
If there is a route, the Cisco ASA checks which interface it corresponds to. If the packet arrived on another interface, it is either a spoof or there is an asymmetric routing environment that has more than one path to a destination. The Cisco ASA does not support asymmetric routing.
If the Cisco ASA is configured on an internal interface, it checks static route command statements or RIP, and if the source_address is not found, then an internal user is spoofing their address.
Recommended Action Even though an attack is in progress, if this feature is enabled, no user action is required. The Cisco ASA 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 Cisco ASA detects the same connection arriving on a perimeter interface, the Cisco ASA has more than one path to a destination. This is known as asymmetric routing and is not supported on the Cisco ASA .
An attacker also might be attempting to append packets from one connection to another as a way to break into the Cisco ASA . In either case, the Cisco ASA 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 An 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-4-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})Explanation If you configured the log option for the access-list command, the packets matched an ACL statement. The message level depends on the level set in the access-list command (by default, the level is 6). The message indicates either the initial occurrance or the total number of occurrances 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. The following list describes the message values:
•
•
•
•
•
•
•
•
•
•
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 Cisco ASA caches the flow information. This message indicates that the number of matching flows that are cached on the Cisco ASA 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.
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 Cisco ASA 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 Cisco ASA .
Recommended Action This message indicates a possible attack and should be monitored. If you are not familiar with the source IP address listed in this message, change your RIP authentication keys between trusted entities. An attacker might be trying to determine the existing keys.
107002
Error Message %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 Cisco ASA .
Recommended Action This message indicates a possible attack and should be monitored. The packet has passed authentication, if enabled, and bad data is in the packet. Monitor the situation and change the keys if there are any doubts about the originator of the packet.
108002
Error Message %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 fixup protocol smtp command. This message is displayed if the Cisco ASA 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 Cisco ASA detects malicious pattern in an e-mail address and drops the connection. This indicates an attack in progress.
Explanation 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.
•
•
•
•
•
•
•
•
–
–
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.
•
•
•
•
•
•
•
–
–
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.
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 Cisco ASA 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 an 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.Explanation This is an AAA message. This message is displayed if no authentication server can be found.
Recommended Action Ping the authentication servers from the Cisco ASA . 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 an 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 an 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 an 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 an 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 an 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 Cisco ASA 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 Cisco ASA . This error can occur if you configure the AAA server before you configure the Cisco ASA . The Vender-Specific Attribute (VSA) on your AAA server might be one of the following values:
•
•
•
Recommended Action Add the ACL to the Cisco ASA , 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 system log 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 Cisco TAC.
109022
Error Message %PIX|ASA-4-109022: exceeded HTTPS proxy process limitExplanation For each HTTPS authentication, the Cisco ASA dedicates a process to service the authentication request. When the number of concurrently running processes exceeds the system-imposed limit, the Cisco ASA 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 an 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 an AAA message. This message is displayed if the Cisco ASA is configured for AAA and a user attempted to make a TCP connection across the Cisco ASA 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.
string—An error message detailing the syntax error that prevented the access list from parsing correctly.
Recommended Action Use the information presented in this message to identify and correct the syntax error in the access list definition within the RADIUS server configuration.
109030
Error Message %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.
access_list—The access list that could not be converted
source—The source IP address.
dest—The destination IP address.
netmask—The subnet mask for the destination or source address in dotted-decimal notation.
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.
access_list—The name assigned to the dynamic access list as it would appear in the output of the show access-list command.
username—The name of the user whose connection will be subject to this access list.
ace—The access list entry that was being processed when the error was detected.
Recommended Action Correct the access list definition in the RADIUS server configuration.
110001
Error Message %PIX|ASA-6-110001: No route to dest_address from source_addressExplanation .This message indicates a route lookup failure. A packet is looking for a destination IP address that is not in the routing table.
Recommended Action Check the routing table and make sure that there is a route to the destination.
111001
Error Message %PIX|ASA-5-111002: 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 <> 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 Cisco ASA 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 a command that modified the configuration.
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.
Recommended Action None required.
111111
Error Message %PIX|ASA-1-111111 error_messageExplanation System or infrastructure error has occurred.
Recommended Action Copy the error message and submit it to TAC along with the configuration and any details about the events leading up to this error.
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 An 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 an 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 An 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 An 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 an 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 An 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 an 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-4-113019: Group = group, Username = user, IP = peer_address, Session disconnected. Session Type: type, Duration: duration, Bytes xmt: count, Bytes rcv: count, Reason: reasonExplanation This is an information message.
group—group name
user—username
peer_address—peer address
type—session type (for example, IPSec/UDP)
duration—connect duration
count—number of bytes
reason—disconnect reason
Recommended Action No action 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 the server are more than five minutes (300 seconds) apart. When this occurs, the connection attempt is rejected.
ip_address—The IP address of the Kerberos server.
Recommended Action Synchronize the clocks on the security appliance and the Kerberos server.
113022
Error Message %ASA-2-113022: AAA Marking protocol server ip-addr in server group tag as FAILEDExplanation This system log 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.
•
- RADIUS
- TACACS+
- NT
- RSA SecurID
- Kerberos
- LDAP
•
•
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 system log message indicates that the security appliance has reactivated the AAA server that was previusly marked as "failed." The AAA server is now available to service AAA requests..
•
- RADIUS
- TACACS+
- NT
- RSA SecurID
- Kerberos
- LDAP
•
•
Recommended Action None required.
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 an 4GE SSM I/O card due to an I2C error or a switch initialization error.
syslog_id—Message identifier
error_string—Describes either an I2C serial bus error or a switch access error, which is a decimal error code. The following are the I2C serial bus errors:
•
•
•
•
•
•
•
•
•
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.
syslog_id—Message identifier
error_string—Describes either an I2C serial bus error or a switch access error, which is a decimal error code. The following are the I2C serial bus errors:
•
•
•
•
•
•
•
•
•
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.
syslog_id—Message identifier
error_string—Describes either an I2C serial bus error or a switch access error, which is a decimal error code. The following are the I2C serial bus errors:
•
•
•
•
•
•
•
•
•
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.
syslog_id—Message identifier
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.
syslog_id—Message identifier
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.
syslog_id—Message identifier
error_string—Describes either an I2C serial bus error or a switch access error, which is a decimal error code. The following are the I2C serial bus errors:
•
•
•
•
•
•
•
•
•
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.
syslog_id—Message identifier
error_string—Describes either an I2C serial bus error or a switch access error, which is a decimal error code. The following are the I2C serial bus errors:
•
•
•
•
•
•
•
•
•
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.
syslog_id—Message identifier
error_string—Describes either an I2C serial bus error or a switch access error, which is a decimal error code. The following are the I2C serial bus errors:
•
•
•
•
•
•
•
•
•
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.
syslog_id—Message identifier
error_string—Describes either an I2C serial bus error or a switch access error, which is a decimal error code. The following are the I2C serial bus errors:
•
•
•
•
•
•
•
•
•
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.
syslog_id—Message identifier
error_string—Describes either an I2C serial bus error or a switch access error, which is a decimal error code. The following are the I2C serial bus errors:
•
•
•
•
•
•
•
•
•
•
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).syslog_id—Message identifier
error_string—Describes either an I2C serial bus error or a switch access error, which is a decimal error code. The following are the I2C serial bus errors:
•
•
•
•
•
•
•
•
•
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).syslog_id—Message identifier
error_string—Describes either an I2C serial bus error or a switch access error, which is a decimal error code. The following are the I2C serial bus errors:
•
•
•
•
•
•
•
•
•
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.
syslog_id—Message identifier
error_string—Describes either an I2C serial bus error or a switch access error, which is a decimal error code. The following are the I2C serial bus errors:
•
•
•
•
•
•
•
•
•
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).syslog_id—Message identifier
error_string—Describes either an I2C serial bus error or a switch access error, which is a decimal error code. The following are the I2C serial bus errors:
•
•
•
•
•
•
•
•
•
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).syslog_id—Message identifier
error_string—Describes either an I2C serial bus error or a switch access error, which is a decimal error code. The following are the I2C serial bus errors:
•
•
•
•
•
•
•
•
•
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).syslog_id—Message identifier
error_string—Describes either an I2C serial bus error or a switch access error, which is a decimal error code. The following are the I2C serial bus errors:
•
•
•
•
•
•
•
•
•
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.
syslog_id—Message identifier
error_string—Describes either an I2C serial bus error or a switch access error, which is a decimal error code. The following are the I2C serial bus errors:
•
•
•
•
•
•
•
•
•
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.
syslog_id—Message identifier
error_string—Describes either an I2C serial bus error or a switch access error, which is a decimal error code. The following are the I2C serial bus errors:
•
•
•
•
•
•
•
•
•
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.
syslog_id—Message identifier
error_string—Describes either an I2C serial bus error or a switch access error, which is a decimal error code. The following are the I2C serial bus errors:
•
•
•
•
•
•
•
•
•
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.
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 Cisco ASA reboot with the reload command.
Recommended Action None required.
199002
Error Message %PIX|ASA-6-199002: startup completed. Beginning operation.Explanation The Cisco ASA 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 Cisco ASA received a packet from the outside network that uses a larger MTU than the inside network. The Cisco ASA then sent an ICMP message to the outside host to negotiate an appropriate MTU. The log message includes the sequence number of the ICMP message.
Recommended Action None required.
199005
Error Message %PIX|ASA-6-199005: Startup beginExplanation The Cisco ASA started.
Recommended Action None required.
199006
Error Message %PIX|ASA-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|ASA-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|ASA-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|ASA-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.
Messages 201002 to 217001
This section contains messages from 201002 to 217001.
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 Cisco ASA . 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 Cisco ASA is reached, the Cisco ASA attempts to accept them anyway, but puts a time limit on the connections. This situation allows some connections to succeed even if the Cisco ASA 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 Cisco ASA 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/portExplanation This is a connection-related message. This message is displayed if the Cisco ASA is unable to preallocate connections for inbound standard output for rsh commands due to insufficient memory.
Recommended Action Check the rsh client version; the Cisco ASA 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 Cisco ASA is disallowing new connections.Explanation This message appears when you have enabled TCP system log messaging and the syslog& server cannot be reached, or when using Cisco ASA Syslog Server (PFSS) and the disk on the Windows NT system is full, or when the auto-update timeout is configured and the auto-update server is not reachable.
Recommended Action Disable TCP system log 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 Cisco ASA console. Then restart TCP system message logging to allow traffic. If the Auto Update Server has not been contacted for a certain period of time, 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.
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.
curr num—The current number.
limit—The configured limit.
[input|output]—Input or output packet on interface interface_name.
IP_address—IP address.
port—TCP or UDP port.
interface_name—The name of the interface on which the policy is applied.
Recommended Action When the limit is reached, any new connection request will be proxied by the 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.
curr num—The current number.
limit—The configured limit.
[input|output]—The input or output packet on interface interface_name.
IP_address—The IP address.
port—The TCP or UDP port.
interface_name—The name of the interface on which the policy is applied.
Recommended Action When the limit is reached any new connection request will be silently dropped. Normally an application will retry. 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 Cisco ASA has no more address translation slots available.
Recommended Action Check the size of the global pool compared to the number of inside network clients. A PAT address may be necessary. Alternatively, shorten the timeout interval of translates and connections. This error message 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 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 Cisco ASA received a nonzero value (an internal error) when attempting to clear the configuration in Flash memory. The message includes the reporting subroutine filename and line number.
Recommended Action For performance reasons, the end host should be configured 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 Cisco ASA limits the number of IP fragments that can be concurrently reassembled. This restriction prevents memory depletion at the Cisco ASA under abnormal network conditions. In general, fragmented traffic should be a small percentage of the total traffic mix. An exception is in a network environment with NFS over UDP where a large percentage is fragmented traffic; if this type of traffic is relayed through the Cisco ASA , 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 Cisco ASA 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 Cisco ASA , 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 Cisco ASA .
Recommended Action Check the failover interface using the show interface command to make sure its transmit is normal. Also check the current block memory using the show block command. If current available count is 0 within any of the blocks of memory, then reload the Cisco ASA 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 Cisco ASA .
Recommended Action Check the available memory using the show memory command to make sure that the Cisco ASA has free memory in the system. If there is no available memory, add more physical memory to the Cisco ASA .
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 Cisco ASA 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 Cisco ASA 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 Cisco ASA has free memory in the system. If no memory is available, add more memory.
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 Cisco ASA 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 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 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 Cisco ASA is unable to receive SNMP requests destined for the Cisco ASA from SNMP management stations located on this interface. This does not affect the SNMP traffic passing through the Cisco ASA through any interface.
An error code of -1 indicates that the Cisco ASA 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 Cisco ASA could not bind the SNMP transport for the interface.Recommended Action After the Cisco ASA 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 Cisco ASA is unable to send its SNMP traps from the Cisco ASA to SNMP management stations located on this interface. This does not affect the SNMP traffic passing through the Cisco ASA through any interface.
An error code of -1 indicates that the Cisco ASA could not open the SNMP trap transport for the interface.
An error code of -2 indicates that the Cisco ASA could not bind the SNMP trap transport for the interface.Recommended Action After the Cisco ASA 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 Cisco ASA on the specified interface.
Recommended Action None required. The Cisco ASA 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 Cisco ASA to the specified host on the specified interface.
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 Cisco ASA exceeds the size of the internal data buffer (512 bytes) used for storing the request during internal processing. The Cisco ASA is unable to process this request. This situation does not affect the SNMP traffic passing through the Cisco ASA 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 a 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 v2c 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 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 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 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.
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 Cisco ASA management port indicates a packet length exceeding the specified upper limit. This may be a hostile event. The Cisco ASA 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 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 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.
n—The message severity.
function—The affected component.
message—A message describing the cause of the problem.
Recommended Action Search the Bug Toolkit for the specific text message and also try to use the Output Interpreter to resolve the problem. If you still require assistance, copy the entire error message from the console or the system log. Enter the show tech-support command and provide the output along with the error message to Cisco TAC. Use the Internet to open the case or contact your Cisco TAC representative.
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.
major_id—Event identifier
minor_id— Event identifier
task_string—Custom string passed by the task to identify itself
function—The function that received the unexpected event
line_num —Line number in the code
Recommended Action Copy the error message and submit it to Cisco TAC along with the configuration and any details about the events leading up to this error.
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.
timer_ptr—Pointer to the timer
timer_id—Timer identifier
task_string—Custom string passed by the task to identify itself
function—The function that received the unexpected event
line_num—Line number in the code
Recommended Action Copy the error message and submit it to Cisco TAC along with the configuration and any details about the events leading up to this error.
Messages 302003 to 326028
This section contains messages from 302003 to 326028.
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 Cisco ASA detects the use of an Intel Internet phone. The foreign port (outside port) only displays on connections from outside the Cisco ASA . 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 Cisco ASA detects the use of an Intel Internet phone. The foreign port (outside_port) only displays on connections from outside the Cisco ASA . 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 Cisco ASA . 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 Cisco ASA 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 2-2.
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 Cisco ASA uses for decoding the H.323 messages failed to initialize; the Cisco ASA cannot decode or inspect the arriving H.323 packet. The Cisco ASA allows the H.323 packet to pass through without any modification. When the next H.323 message arrives, the Cisco ASA attempts to initialize the library again.
Recommended Action If this message is generated consistently for a particular library, contact 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 fast-path when stateful ICMP is enabled using the fixup protocol 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 fast-path when stateful ICMP is enabled using the fixup protocol icmp command.
Recommended Action None required.
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|ASA-6-303002: source_address {Stored|Retrieved} dest_address: mapped_addressExplanation This is an FTP/URL message. This message is displayed when the specified host attempts to store or retrieve data from the specified FTP site.
Recommended Action None required.
303003
Error Message %PIX|ASA-6-303003: FTP cmd_name command denied - failed strict inspection, terminating connection from source_interface:source_address/source_port to dest_interface:dest_address/dest_portExplanation This message is generated when using strict inspection on FTP traffic. It is displayed if a FTP request command is denied by the strict FTP inspection policy from the ftp-map command.
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 appears 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.
304001
Error Message %PIX|ASA-5-304001: user source_address Accessed {JAVA URL|URL} dest_address: url.Explanation 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 Cisco ASA attempts to either try to access the same server if it is the only server installed, or another server if there is more than one.
Recommended Action None required.
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 Cisco ASA 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 Cisco ASA receives a response message from a Websense server that previously was not responding. With this response message, the Cisco ASA 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:dest_address/dest_port dst interface_name:source_address/source_portExplanation A packet does not match any of the outbound nat command rules.
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 Cisco ASA . This message appears as a fix to caveat CSCdr00663 that requested that Cisco ASA not allow packets that are destined for network or broadcast addresses. The Cisco ASA provides this checking for addresses that are explicitly identified with static command statements. With the change, for inbound traffic, the Cisco ASA denies translations for a destined IP address identified as a network or broadcast address.
The Cisco ASA does not apply PAT to all ICMP message types; it only applies PAT ICMP echo and echo-reply packets (types 8 and 0). Specifically, only ICMP echo or echo-reply packets create a PAT xlate. So, when the other ICMP messages types are dropped, system log message 305006 (on the Cisco ASA ) is generated.
The Cisco ASA 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 Cisco ASA does not create a translation for network or broadcast IP addresses with inbound packets.
For example:
static (inside,outside) 10.2.2.128 10.1.1.128 netmask 255.255.255.128
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, Cisco ASA denies inbound packets destined for 10.2.2.128 or 10.2.2.255, and logs this system log 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 Cisco ASA to respond to 10.2.2.128 as a host address:
static (inside,outside) 10.2.2.128 10.2.2.128 netmask 255.255.255.255
static (inside,outside) 10.2.2.128 10.2.2.128 netmask 255.255.255.128The translation may be created by traffic started with the inside host with the questioned IP address. Because the Cisco ASA 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 Cisco ASA has attempted to translate an address that it cannot find in any of its global pools. The Cisco ASA 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 Cisco ASA kernel detected an inconsistency condition when trying to free an unallocated global IP address back to the address pool. This abnormal condition may occur if the Cisco ASA 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 Report this condition to Cisco TAC if you continue to see this message.
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.
308001
Error Message %PIX|ASA-6-308001: console enable password incorrect for number tries (from IP_address)Explanation This is a Cisco ASA 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 Cisco ASA when the standby Cisco ASA 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 Cisco ASA .
Recommended Action None required.
311003
Error Message %PIX|ASA-6-311003: LU recv thread upExplanation An update acknowledgment was received from the standby Cisco ASA .
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 Cisco ASA .
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 Cisco ASA received a RIP message with an operation code other than reply, the message has a version number different from what is expected on this interface, and the routing domain entry was nonzero.
Recommended Action This message is informational, but it may also indicate that another RIP device is not configured correctly to communicate with the Cisco ASA .
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 Cisco ASA discards the ICMP packet and generates this system log message. The icmp command enables or disables pinging to an interface. With pinging disabled, the Cisco ASA cannot be detected on the network. This feature is also referred to as configurable proxy pinging.
Recommended Action Contact the administrator of the peer device.
313003
Error Message %PIX|ASA-4-313003: Invalid destination for ICMP errorExplanation The destination for the ICMP error message is different than the source of the IP packet that induced the ICMP error message.
Recommended Action If the message occurs frequently, this could be an active network probe, an attempt to use the ICMP error message as a covert channel, or a misbehaving IP host. Contact the administrator of the host that originated the ICMP error message.
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 Cisco ASA because of security checks added by the stateful ICMP feature that are usually either ICMP echo replies without a valid echo request already passed across the Cisco ASA or ICMP error messages not related to any TCP, UDP, or ICMP session already established in the Cisco ASA .
Recommended Action None required.
314001
Error Message %PIX|ASA-6-314001: Pre-allocate RTSP UDP backconnection for foreign_address outside_address/outside_port to local_address inside_address/inside_portExplanation The Cisco ASA opened an RTSP connection for the specified IP addresses and ports.
Recommended Action No action required.
315004
Error Message %PIX|ASA-3-315004: Fail to establish SSH session because RSA host key retrieval failed.Explanation The Cisco ASA could not find the Cisco ASA RSA host key, which is required for establishing an SSH session. The Cisco ASA host key may be absent because it was not generated or because the license for this Cisco ASA does not allow DES or 3DES.
Recommended Action From the console, enter the show ca mypubkey rsa command to verify that the Cisco ASA RSA host key is present. If not, also enter the show version command to check whether the Cisco ASA license allows DES or 3DES.
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 2-3 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.
317001
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 To determine the cause of the problem, contact Cisco TAC for assistance.
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.
318001
Error Message %PIX|ASA-3-318001: Internal error: reasonExplanation An internal software error occurred. This message occurs at 5-second intervals.
Recommended Action To determine the cause of the problem, contact Cisco TAC for assistance.
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 To determine the cause of the problem, contact Cisco TAC for assistance.
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 To determine the cause of the problem, contact Cisco TAC for assistance.
318006
Error Message %PIX|ASA-3-318006: if interface_name if_state numberExplanation An internal error occurred.
Recommended Action To determine the cause of the problem, contact Cisco TAC for assistance.
318007
Error Message %PIX|ASA-3-318007: OSPF is enabled on interface_name during idb initializationExplanation An internal error occurred.
Recommended Action To determine the cause of the problem, contact Cisco TAC for assistance.
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.
function—The function that received the unexpected event
line_num —Line number in the code
Recommended Action Copy the error message and submit it to Cisco TAC along with the configuration and any details about the events leading up to this error.
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 Cisco ASA 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 Cisco ASA 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 FWSM 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 Cisco ASA 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 Cisco ASA .
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 Cisco ASA received a packet from the offending MAC address on the specified interface but the source MAC address in the packet is statically bound to another interface in 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 Cisco ASA . If this check fails, the ARP inspection module drops the ARP packet and generates this message. This situation may be caused by either ARP spoofing attacks in the network or an invalid configuration (IP-MAC binding).
Recommended Action If the cause is an attack, you can deny the host using the ACLs. If the cause is an invalid configuration, correct the binding.
322003
Error Message %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 Cisco ASA . If this check fails, the ARP inspection module drops the ARP packet and generates this message. This situation may be caused by either ARP spoofing attacks in the network or an invalid configuration (IP-MAC binding).
Recommended Action If the cause is an attack, you can deny the host using the ACLs. If the cause is an invalid configuration, correct the binding.
322004
Error Message %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 Cisco ASA dropped a packet due to no management IP address configured in the transparent mode.
protocol—Protocol string or value
interface_in—Input interface name
source_address—Source IP address of the packet
source_port—Source port of the packet
interface_out—Output interface name
dest_address—Destination IP address of the packet
dest_port—Destination port of the packet
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.
slotnum—The slot number containing the module.
newver—The new version number of software that was not successfully written to the module (for example, 1.0(1)0)
ver—The current version number of the software on the module (for example, 1.0(1)0).
reason—The reason the new version could not be written to the module. The possible values for reason include the following:
•
•
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. Contact Cisco TAC if further attempts to update the module software are not successful.
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.
slotnum—The slot number containing the module
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 Cisco TAC.
323006
Error Message %ASA-1-323006: 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. This 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.
slot—The slot in which the failure occurred
Recommended Action If this message is not the result of the SSM reloading or resetting and the corresponding message 1-505011 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.
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 this message repeats frequently because of the memory allocation error, contact 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, collect the necessary debugs and contact 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_interface:source_address/0 to dest_interface: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 you are unable to debug the problem, collect the necessary debugs and contact 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.
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 Copy the error message and submit it, the configuration and any details about the events leading up to this error to 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 Copy the error message and submit it, the configuration and any details about the events leading up to this error to 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 Copy the error message and submit it, the configuration and any details about the events leading up to this error to 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 this message persists after the system is up copy the error message and submit it, the configuration and any details about the events leading up to this error to 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 sufficient memory exists, then copy the error message and submit it, the config and any details about the events leading up to this error to 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 sufficient memory exists, then copy the error message and submit it, the configuration and any details about the events leading up to this error to Cisco TAC.
326008
Error Message %PIX|ASA-3-326008: MRIB registration failedExplanation The MFIB failed to register with the MRIB.
Recommended Action Copy the error message and submit it, the configuration and any details about the events leading up to this error to 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 Copy the error message and submit it, the configuration and any details about the events leading up to this error to Cisco TAC.
326010
Error Message %PIX|ASA-3-326010: MRIB unbind failedExplanation The MFIB failed to unbind from the MRIB.
Recommen
