|
|
Table Of Contents
System Log Messages
This chapter lists the Cisco PIX Firewall system log messages. The messages are listed numerically by message code.
Note
The messages shown in this guide apply to Cisco PIX Firewall version 6.2 and higher. When a number is skipped from a sequence, for example, 106019, the message is no longer in the PIX Firewall code.
This chapter includes the following sections:
Messages 101001 to 199005
Error Message %PIX-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.
Error Message %PIX-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.
Error Message %PIX-1-101003: (Primary) Failover cable not connected (this unit).Error Message %PIX-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.
Error Message %PIX-1-101005: (Primary) Error reading failover cable status.Explanation This is a failover message. This message is logged if the failover cable is connected, but the primary unit is unable to determine its status.
Recommended Action Replace the cable.
Error Message %PIX-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 power failure on the other unit. "(Primary)" can also be listed as "(Secondary)" for the secondary unit.
Recommended Action Verify that the secondary unit is powered on and that power cables are properly connected.
Error Message %PIX-1-103001: (Primary) No response from other firewall (reason code = code).Explanation This is a failover message. This message is logged 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 the failover cable is connected properly and both units have the same hardware, software, and configuration; otherwise contact Cisco TAC.
Error Message %PIX-1-103002: (Primary) Other firewall network interface interface_number OK.Explanation This is a failover message. This message is logged 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-3 in "Introduction," for possible values for the interface_number variable.
Recommended Action None required.
Error Message %PIX-1-103003: (Primary) Other firewall network interface interface_number failed.Explanation This is a failover message. This message is logged if the primary unit detects a bad network interface on the secondary unit. "(Primary)" can also be listed as "(Secondary)" for the secondary unit. Refer to Table 1-3 in "Introduction," for possible values for the interface_number variable.
Recommended Action Check the network connections on the secondary unit. Also, check the network hub connection. If necessary, replace the failed network interface.
Error Message %PIX-1-103004: (Primary) Other firewall reports this firewall failed.Explanation This is a failover message. This message is logged 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.
Error Message %PIX-1-103005: (Primary) Other firewall reporting failure.Explanation This is a failover message. This message is logged 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.
Error Message %PIX-1-104001: (Primary) Switching to ACTIVE (cause: reason).Error Message %PIX-1-104002: (Primary) Switching to STNDBY (cause: reason).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 secondary unit, or the no failover active command on the primary unit. "(Primary)" can also be listed as "(Secondary)" for the secondary unit. Possible values for the reason 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.
Error Message %PIX-1-104003: (Primary) Switching to FAILED.Explanation This is a failover message. This message is logged 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.
Error Message %PIX-1-104004: (Primary) Switching to OK.Explanation This is a failover message. This message is logged 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.
Error Message %PIX-1-105001: (Primary) Disabling failover.Explanation This is a failover message. This message is logged 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.
Error Message %PIX-1-105002: (Primary) Enabling failover.Explanation This is a failover message. This message is logged 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.
Error Message %PIX-1-105003: (Primary) Monitoring on interface int_name waitingExplanation This is a failover message. The PIX Firewall is testing the specified network interface with the other unit of the failover pair. Refer to Table 1-3 in "Introduction," for possible values for the interface_number variable. "(Primary)" can also be listed as "(Secondary)" for the secondary unit.
Recommended Action None required. The PIX Firewall monitors its network interfaces frequently during normal operations.
Error Message %PIX-1-105004: (Primary) Monitoring on interface int_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.
Error Message %PIX-1-105005: (Primary) Lost Failover communications with mate on interface int_name.Explanation This is a failover message. This message is logged 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.
Error Message %PIX-1-105006: (Primary) Link status `Up' on interface int_name.Error Message %PIX-1-105007: (Primary) Link status `Down' on interface int_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.
Error Message %PIX-1-105008: (Primary) Testing interface int_name.Explanation This is a failover message. This message is logged when the PIX Firewall tests a specified network interface. This testing is performed only if the PIX Firewall 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.
Error Message %PIX-1-105009: (Primary) Testing on interface int_name result.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.
Error Message %PIX-3-105010: (Primary) Failover message block alloc failedExplanation Block memory was depleted. This is a transient message and the PIX Firewall 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.
Error Message %PIX-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.
Error Message %PIX-1-105020: (Primary) Incomplete/slow config replicationExplanation When a failover occurs, the active PIX Firewall 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 PIX Firewall, the PIX Firewall automatically reloads itself and loads configuration from Flash memory and/or resyncs with another PIX Firewall. If failovers happen continuously, check the failover configuration and make sure both PIX Firewall units can communicate with each other.
Error Message %PIX-1-105031: Failover LAN interface is upExplanation LAN failover interface link is up.
Recommended Action None required.
Error Message %PIX-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 the speed/duplex setting is correct.
Error Message %PIX-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.
Error Message %PIX-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's LAN failover interface.
Error Message %PIX-1-105036: PIX dropped a LAN Failover command message.Explanation The PIX Firewall 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.
Error Message %PIX-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.
Error Message %PIX-2-106001: Inbound TCP connection denied from IP_addr/port to IP_addr/port flags TCP_flags on interface int_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 PIX Firewall, and it was dropped. The TCP_flags in this packet are FIN and ACK.
The TCP_flags are as follows:–
–
–
–
–
–
Recommended Action None required.
Error Message %PIX-2-106002: protocol Connection denied by outbound list list_ID src laddr dest faddrExplanation This is a connection-related message. This message is logged if the specified connection fails because of an outbound deny command statement. The protocol variable can be ICMP, TCP, or UDP.
Recommended Action Use the show outbound command to check outbound lists.
Error Message %PIX-2-106006: Deny inbound UDP from faddr/fport to laddr/lport on interface int_name.Explanation This is a connection-related message. This message is logged if an inbound UDP packet is denied by your security policy.
Recommended Action None required.
Error Message %PIX-2-106007: Deny inbound UDP from faddr/fport to laddr/lport due to DNS flag.Explanation This is a connection-related message. This message is logged if a UDP packet containing a DNS query or response is denied. The flag variable is either Response or Query.
Recommended Action If the inside port number is 53, it is likely that the inside host is set up as a caching nameserver. Add an access-list command statement to permit traffic on UDP port 53. If the outside port number is 53, the most likely cause is that a DNS server was too slow to respond, and the query was answered by another server.
Error Message %PIX-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 logged 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.
Error Message %PIX-3-106011: Deny inbound (No xlate) charsExplanation The message will appear under normal traffic conditions if there are internal users that are accessing the Internet via a web browser. Anytime a connection is reset, when the host at the end of the connection sends a packet after the PIX Firewall receives the reset, this message will appear. It can typically be ignored.
Recommended Action Disable this syslog message from getting logged to the syslog server by entering the no logging message 106011 command.
Error Message %PIX-2-106012: Deny IP from IP_addr to IP_addr, 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 or strict source routing.
Error Message %PIX-2-106013: Dropping echo request from IP_addr to PAT address IP_AddrExplanation This message is logged when the PIX Firewall discards an inbound ICMP Echo Request packet with a destination address that corresponds to a PAT global address. It is discarded because the inbound packet cannot specify which PAT host should receive the packet.
Recommended Action None required.
Error Message %PIX-3-106014: Deny inbound icmp src interface name: IP_addr dst interface name: IP_addr (type dec, code dec)Explanation This message is logged when the PIX Firewall denies any inbound ICMP packet access. By default, all ICMP packets are denied access unless specifically permitted using the conduit permit icmp command.
Recommended Action None required.
Error Message %PIX-6-106015: Deny TCP (no connection) from IP_addr/port to IP_addr/port flags flags on interface int_name.Explanation This message is logged when the PIX Firewall discards a TCP packet that has no associated connection in the PIX Firewall unit's connection table. PIX Firewall 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 PIX Firewall discards the packet.
Recommended Action None required unless the PIX Firewall 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.
Error Message %PIX-2-106016: Deny IP spoof from (IP_addr) to IP_addr on interface int_name.Explanation This message is logged when the PIX Firewall discards a packet with an invalid source address. Invalid source addresses are those addresses belonging to the following:
–
–
–
Furthermore, if the sysopt connection enforcesubnet command is enabled, PIX Firewall discards packets with a source address belonging to the destination subnet from traversing the PIX Firewall and logs this message.
To further enhance spoof packet detection, use the conduit command to configure the PIX Firewall to discard packets with source addresses belonging to the internal network.Recommended Action Determine if an external user is trying to compromise the protected network. Check for misconfigured clients.
Error Message %PIX-2-106017: Deny IP due to Land Attack from IP_addr to IP_addrExplanation This message appears when PIX Firewall receives a packet with the IP source address equal to the IP destination, and the destination port equal to the source port. This indicates a spoofed packet 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.
Error Message %PIX-2-106018: ICMP packet type ICMP_type denied by outbound list list_ID src laddr dest faddrExplanation This message is logged because the outgoing ICMP packet with type ICMP_type from local host laddr to foreign host faddr is denied by outbound list list_ID.
Recommended Action None required.
Error Message %PIX-2-106020: Deny IP teardrop fragment (size = num, offset = num) from IP_addr to IP_addrExplanation The PIX Firewall discarded an IP packet with a teardrop signature containing either a small offset or fragment overlapping. This is a hostile event to circumvent the PIX Firewall or an Intrusion Detection System.
Recommended Action Contact the remote peer administrator or escalate this issue according to your security policy.
Error Message %PIX-1-106021: Deny protocol reverse path check from src_addr to dest_addr on interface int_nameExplanation Someone is attempting to spoof an IP address on an inbound connection. Unicast Reverse Path Forwarding (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 PIX Firewall.
Recommended Action This message appears when you have enabled Unicast Reverse Path Forwarding with the ip verify reverse-path command. This feature works on packets input to an interface; if it is configured on the outside, then PIX Firewall checks packets arriving from the outside.
PIX Firewall looks up a route based on the src_addr. If an entry is not found and a route is not defined, then this syslog message appears and the connection is dropped.
If there is a route, PIX Firewall 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. PIX Firewall does not support asymmetric routing.
If configured on an internal interface, PIX Firewall checks static route command statements or RIP and if the src_addr is not found, then an internal user is spoofing their address.
An attack is in progress. With this feature enabled, no user action is required. PIX Firewall repels the attack.
Error Message %PIX-1-106022: Deny protocol connection spoof from src_addr to dest_addr on interface int_nameExplanation This message only appears if a connection exists and a packet matching the connection arrives on a different interface than the interface the connection began on.
For example, if a user starts a connection on the inside interface, but the PIX Firewall detects the same connection arriving on a perimeter interface, the PIX Firewall has more than one path to a destination. This is known as asymmetric routing and is not supported on the PIX Firewall.
Alternately, an attacker is attempting to append packets from one connection to another as a way to break into the PIX Firewall. In either case, PIX Firewall displays this message and drops the connection.
Recommended Action This message appears when the ip verify reverse-path command is not configured. Ensure routing is not asymmetric.
Error Message %PIX-4-106023: Deny protocol src [inbound-interface]:[src_address/src_port] dst outbound-interface:dst_address/dst_port [type {type}, code {code}] by access_group access-list-nameExplanation An IP packet was denied by the access-list.
Recommended Action Change permission of access-list if a permit policy is desired. If messages persist from the same source address, messages could indicate a foot printing or port scanning attempt. Contact the remote host administrator.
Error Message %PIX-1-107001: RIP auth failed from IP_addr: version=vers, type=type, mode=mode, sequence=seq on interface int_nameExplanation This is an alert log message. PIX Firewall received a RIP reply message with bad authentication. This could be due to misconfiguration on the router or the PIX Firewall, or it could be an unsuccessful attempt to attack the PIX Firewall routing table.
Recommended Action This may be an 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 may be trying to deduce the existing keys.
Error Message %PIX-1-107002: RIP pkt failed from IP_addr: version=vers on interface int_nameExplanation This is an alert message. This could be 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 the PIX Firewall unit's routing table.
Recommended Action This may be an attack and should be monitored. The packet has passed authentication, if enabled, and bad data is in the packet. The situation should be monitored and the keys should be changed if there are any doubts as to the originator of the packet.
Error Message %PIX-2-108002: SMTP replaced chars: out src_addr in laddr data: charsExplanation This is a Mail Guard (SMTP) message generated by the fixup protocol smtp command. This message is logged if the PIX Firewall replaces an invalid character in an email address with a space.
Recommended Action None required.
Error Message %PIX-6-109001: Auth start for user username from laddr/lport to faddr/fportExplanation This is a AAA message. This message is logged if the PIX Firewall is configured for AAA and detects an authentication request by the specified user.
Recommended Action None required.
Error Message %PIX-6-109002: Auth from laddr/lport to faddr/fport failed (server IP_addr failed) on interface int_name.Explanation This is a AAA message. This message is logged if an authentication request fails because the specified authentication server cannot be contacted by the PIX Firewall.
Recommended Action Check that the authentication daemon is running on the specified authentication server.
Error Message %PIX-6-109003: Auth from laddr to faddr/fport failed (all servers failed) on interface int_name.Explanation This is a AAA message. This message is logged if no authentication server can be found.
Recommended Action Ping the authentication server(s) from the PIX Firewall. Make sure the daemon(s) are running.
Error Message %PIX-6-109005: Authentication succeeded for user `user' from laddr/lport to faddr/fport on interface int_name.Explanation This is a AAA message. This message is logged when the specified authentication request succeeds.
Recommended Action None required.
Error Message %PIX-6-109006: Authentication failed for user `user' from laddr/lport to faddr/fport on interface int_name.Explanation This is a AAA message. This message is logged if the specified authentication request fails, possibly because of an incorrect password.
Recommended Action None required.
Error Message %PIX-6-109007: Authorization permitted for user `user' from laddr/lport to faddr/fport on interface int_name.Explanation This is a AAA message. This message is logged when the specified authorization request succeeds.
Recommended Action None required.
Error Message %PIX-6-109008: Authorization denied for user `user' from faddr/fport to laddr/lport on interface int_name.Explanation This is a AAA message. This message is logged if a user is not authorized to access the specified address, possibly because of an incorrect password.
Recommended Action None required.
Error Message %PIX-6-109009: Authorization denied from laddr/lport to faddr/fport (not authenticated) on interface int_name.Explanation This is a AAA message. This message is logged if the PIX Firewall is configured for AAA and a user attempted to make a TCP connection across the PIX Firewall without prior authentication.
Recommended Action None required.
Error Message %PIX-3-109010: Auth from laddr/lport to faddr/fport failed (too many pending auths) on interface int_name.Explanation This is a AAA message. This message is logged 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 Flood Defender with the floodguard enable command.
Error Message %PIX-2-109011: Authen Session Start: user 'user', sid session_numExplanation An authentication session started between the host and the PIX Firewall and has not yet completed.
Recommended Action None required.
Error Message %PIX-5-109012: Authen Session End: user 'user', sid session_num, elapsed num 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.
Error Message %PIX-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.
Error Message %PIX-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.
Error Message %PIX-6-109015: Authorization denied (acl=acl_ID) for user 'username' from src_addr/src_port to dest_addr/dest_port on interface int_nameExplanation The access list check failed; either it matched a deny, or it matched nothing, such as an implicit deny. Connection denied by user access list acl_ID, which was defined per the AAA authorization policy on CiscoSecure ACS.
Recommended Action None required.
Error Message %PIX-3-109016: Can't find authorization ACL acl_ID on 'PIX' for user 'user'Explanation The access control list (ACL) specified on the AAA server for this user does not exist on the firewall. This error can occur if you configure the AAA server before you configure the firewall. The Vender-Specific Attribute (VSA) on your AAA server might be one of the following values:
–
acl=acl_ID–
shell:acl=acl_ID–
ACS:CiscoSecured-Defined-ACL=acl_IDRecommended Action Add the ACL to the firewall, making sure to use the same name specified on the AAA server.
Error Message %PIX-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 aaa proxy-limit proxy_limit command, or make the user close unused connections. If the error persists, it may indicate a possible DoS attack.
Error Message %PIX-3-109018: Downloaded ACL acl_name is emptyExplanation The downloaded authorization access list has no ACEs. This might be caused by the misspelled attribute string 'ip:inacl#' or omission of the access list command.
junk:junk# 1=permit tcp any any eq junk" "ip:inacl#1="Recommended Action Correct the ACL elements that have the indicated error on the AAA server.
Error Message %PIX-3-109019: Downloaded ACL acl_name has parsing error; ACE err_aceExplanation An error is encountered during parsing the sequence number NNN in the attribute string 'ip:inacl#NNN=' of a downloaded authorization access 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.
Error Message %PIX-3-109020: Downloaded ACL has config error; ACEExplanation One of the elements of the downloaded authorization access list has a configuration error. The entire text of the element is included in the syslog message. This message is usually caused by an invalid access list command statement.
ip:inacl# 1=permit junk any anyip:inacl# 1=permit tcp any any eq junkRecommended Action Correct the ACL element that has the indicated error on the AAA server.
Error Message %PIX-6-110001: No route to dest_addr from src_addrExplanation This message indicates a route lookup failure. A packet is looking for a destination IP address which is not in the routing table.
Recommended Action Check the routing table and make sure there is a route to the destination.
Error Message %PIX-5-111001: Begin configuration: IP_addr writing to deviceExplanation This message is logged 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_addr indicates whether the login was made at the console port or via a Telnet connection.
Recommended Action None required.
Error Message %PIX-5-111003: IP_addr Erase configurationExplanation This is a PIX Firewall management message. This message is logged when you erase the contents of Flash memory by entering the write erase command at the console. The IP_addr indicates whether the login was made at the console port or via a Telnet connection.
Recommended Action After erasing the configuration, reconfigure the PIX Firewall 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.
Error Message %PIX-5-111004: IP_addr end configuration: [FAILED]|[OK]Explanation This message is logged when you enter the config floppy/memory/ network command, or the write floppy/memory/network/standby command. The IP_addr indicates whether the login was made at the console port or via 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, ensure that the floppy is not write protected; if writing to a TFTP server, ensure that the server is up.
Error Message %PIX-5-111005: IP_addr end configuration: OKExplanation This message is logged when you exit configuration mode. The IP_addr indicates whether the login was made at the console port or via a Telnet connection.
Recommended Action None required.
Error Message %PIX-5-111007: Begin configuration: IP_addr reading from device.Explanation This message is logged 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_addr indicates whether the login was made at the console port or via a Telnet connection.
Recommended Action None required.
Error Message %PIX-5-111008: User user_name executed the command commandExplanation This syslog message is for accounting purposes. The user entered a command that modified the configuration.
Recommended Action None required.
Error Message %PIX-7-111009:User user_name executed cmd:commandExplanation This syslog message is for accounting purposes. The user entered a command that does not modify the configuration.
Recommended Action None required.
Error Message %PIX-2-112001: (chars:dec) PIX Clear complete.Explanation This message is logged when a request to clear the PIX Firewall configuration has finished. The source file and line number are identified.
Recommended Action None required.
Error Message %PIX-5-199001: PIX reload command executed from telnet (remote IP_addr).Explanation This message logs the address of the host initiating a PIX Firewall reboot with the reload command.
Recommended Action None required.
Error Message %PIX-6-199002: PIX startup completed. Beginning operation.Explanation This message is logged after the PIX Firewall finishes its initial boot and Flash memory reading sequence, and is ready to begin operating normally.
Note
Recommended Action None required.
Error Message %PIX-6-199005: PIX Startup beginExplanation This message is logged when the PIX Firewall starts.
Recommended Action None required.
Messages 201002 to 209005
Error Message %PIX-3-201002: Too many connections on static|xlate gaddr! econns nconnsExplanation This is a connection-related message. This message is logged when the maximum number of connections to the specified static address was exceeded. The econns variable is the maximum number of embryonic connections and nconns is the maximum number of connections permitted for the static or xlate.
Recommended Action Use the show static command to check the limit imposed on connections to a static address. The limit is configurable.
Error Message %PIX-2-201003: Embryonic limit exceeded neconns/elimit for faddr/fport (gaddr) laddr/lport on interface int_nameExplanation This is a connection-related message regarding traffic to the PIX Firewall. This message is logged when the number of embryonic connections from the specified foreign address via the specified static global address to the specified local address exceeds the embryonic limit. When the limit on embryonic connections to the PIX Firewall is reached, the PIX Firewall attempts to accept them anyway, but puts a time limit on the connections. This allows some connections to succeed even if the PIX Firewall is very busy. The neconns variable lists the number of embryonic connections received and elimit 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 simply a very heavy load of legitimate traffic. Use the show static command to check the limit imposed on embryonic connections to a static address.
Error Message %PIX-3-201005: FTP data connection failed for IP_addrExplanation This is a connection-related message. This message is logged when the PIX Firewall is unable to 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.
Error Message %PIX-3-201006: RCMD backconnection failed for IP_addr/portExplanation This is a connection-related message. This message is logged if the PIX Firewall is unable to preallocate connections for inbound standard output for rsh commands due to insufficient memory.
Recommended Action Check the rsh client version; the PIX Firewall only supports the Berkeley rsh. Also, reduce the amount of memory usage, or purchase additional memory.
Error Message %PIX-3-201008: The PIX is disallowing new connections.Explanation This message occurs when you have enabled TCP system log messaging and the syslog server cannot be reached, or when using PIX Firewall Syslog Server (PFSS) and the disk on the Windows NT system is full.
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 host is up and you can ping the host from the PIX Firewall console. Then restart TCP system message logging to allow traffic.
Error Message %PIX-3-201009: TCP connection limit of limit-count for host host-address on interface exceededExplanation This is a connection-related message. This message is logged when the maximum number of connections to the specified static address was exceeded. The limit-count variable is the maximum of connections permitted for the host specified by the host-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.
Error Message %PIX-3-202001: Out of address translation slots!Explanation This is a connection-related message. This message is logged if the PIX Firewall has no more address translation slots available.
Recommended Action Check the size of the global pool compared to the number of inside network clients. A PAT address may be necessary. Alternatively, shorten the timeout interval of xlates and connections. This could also be caused by insufficient memory; reduce the amount of memory usage, or purchase additional memory.
Error Message %PIX-3-202005: Non-embryonic in embryonic list faddr/fport laddr/lportExplanation This is a connection-related message. This message is logged when a connection object (xlate) is in the wrong list.
Recommended Action Contact Cisco TAC. This should never happen.
Error Message %PIX-3-208005: (function:line_num) pix clear command return return_codeExplanation The PIX Firewall received a non-zero value (an internal error) when attempting to clear the configuration in Flash memory. The message includes the reporting subroutine's filename and line number.
Recommended Action For performance reasons, the end host should be configured to not inject IP fragments. This is most likely due to NFS. Set the read and write size equal to the interface MTU for NFS.
Error Message %PIX-4-209003: Fragment database limit of counts exceeded: src = IP_addr,dest = IP_addr, proto = protocol, id = IDExplanation Too many IP fragments are currently awaiting reassembly. The PIX Firewall limits the number of IP fragments that can be concurrently reassembled. This restriction prevents memory depletion at the firewall under abnormal network conditions. In general, fragmented traffic should be a small percentage of the total traffic mix. A noticeable exception is in a network environment with NFS over UDP; if this type of traffic is relayed through the PIX Firewall, consider using NFS over TCP instead. Refer to the fragment command and the sysopt connection tcpmss bytes command in the Cisco PIX Firewall Command Reference for more information.
Recommended Action If this message persists, a denial of service (DoS) attack might be in progress. Contact the remote peer's administrator or upstream provider.
Error Message %PIX-4-209004: Invalid IP fragment, size = bytes exceeds maximum size = bytes: src = IP_addr, dest = IP_addr, proto = protocol, id = IDExplanation 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.
Error Message %PIX-4-209005: Discard IP fragment set with more than number elements: src = IP_addr, dest = IP_addr, proto = protocol, id = IDExplanation Too many elements are in a fragment set. The PIX Firewall disallows any IP packet that is fragmented into more than 12 fragments. Refer to the fragment command in the Cisco PIX Firewall Command Reference for more information.
Recommended Action A possible intrusion event may be in progress. If the message persists, contact the remote peer's administrator or upstream provider.
Messages 210001 to 214001
Error Message %PIX-3-210001: LU SW_Module_Name error = error_codeExplanation This message is logged if a Stateful Failover error occurred.
Recommended Action If this error persists after traffic lessens through the PIX Firewall, report this error to Cisco TAC.
Error Message %PIX-3-210002: LU allocate block (size) failed.Explanation Stateful Failover could not allocate a block of memory to transmit stateful information to the standby PIX Firewall.
Recommended Action Check the failover interface to make sure its xmit is normal using the show interface command. 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 PIX Firewall software to recover the lost blocks of memory.
Error Message %PIX-3-210003: Unknown LU Object IDExplanation 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.
Error Message %PIX-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 PIX Firewall.
Recommended Action Check the available memory using the show memory command to make sure the PIX Firewall has free memory in the system. If there is no available memory, add more physical memory to the PIX Firewall.
Error Message %PIX-3-210006: LU look NAT for IP_addr failedExplanation Stateful Failover was unable to locate a NAT group for the ip_address on the standby unit. Most likely, the active and standby PIX Firewall units are out of sync.
Recommended Action Use the write standby command on the active unit to synchronize system memory with the standby unit.
Error Message %PIX-3-210007: LU allocate xlate failedExplanation Stateful Failover failed to allocate a translation slot (xlate) record.
Recommended Action Check the available memory by using the show memory command to make sure the PIX Firewall has free memory in the system. If no memory is available, add more memory.
Error Message %PIX-3-210008: LU no xlate for laddr/l_port faddr/f_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.
Error Message %PIX-3-210010: LU make UDP connection for faddr:f_port laddr:l_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 the PIX Firewall has free memory in the system. If no memory is available, add more memory.
Error Message %PIX-3-210020: LU PAT port port_number reserve failedExplanation Stateful Failover is unable to allocate a specific PAT address which is in use.
Recommended Action If this error repeats frequently, use the write standby command on the active unit to synchronize system memory between the active and standby units.
Error Message %PIX-3-210021: LU create static xlate global_IP ifc int_name failedExplanation Stateful Failover is unable to create a translation slot (xlate).
Recommended Action If this error repeats frequently, use the write standby command on the active unit to synchronize system memory between the active and standby units.
Error Message %PIX-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 PIX Firewall units to ensure there is enough memory to process the stateful information. Use the show failover command to monitor the quality of stateful information updates.
Error Message %PIX-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.
Error Message %PIX-3-211003: CPU utilization for time seconds = %cpu_usageExplanation This message is displayed if the percentage of CPU usage is greater than 100% for time seconds.
Recommended Action If this message occurs frequently, contact Cisco TAC.
Error Message %PIX-3-212001: Unable to open SNMP channel (UDP port udp_port) on interface interface_number, error code = codeExplanation This is an SNMP message. This message reports that the PIX Firewall is unable to receive SNMP requests destined for the PIX Firewall from SNMP management stations located on this interface. This does not affect the SNMP traffic passing through the PIX Firewall via any interface.
An error code of -1 indicates that PIX Firewall could not open the SNMP transport for the interface.An error code of -2 indicates that PIX Firewall could not bind the SNMP transport for the interface.
Recommended Action Once the PIX Firewall reclaims some of its resources when traffic is lighter, use the snmp-server host command for that interface again.
Error Message %PIX-3-212002: Unable to open SNMP trap channel (UDP port udp_port) on interface interface_number, error code = codeExplanation This is an SNMP message. This message reports that the PIX Firewall is unable to send its SNMP traps from the PIX Firewall to SNMP management stations located on this interface. This does not affect the SNMP traffic passing through the PIX Firewall via any interface.
An error code of -1 indicates that PIX Firewall could not open the SNMP trap transport for the interface.An error code of -2 indicates that PIX Firewall could not bind the SNMP trap transport for the interface.
Recommended Action Once the PIX Firewall reclaims some of its resources when traffic is lighter, issue the snmp-server host command for that interface again.
Error Message %PIX-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 logged because of an internal error in receiving an SNMP request destined for the PIX Firewall on the specified interface.
Recommended Action None required. The PIX Firewall SNMP agent goes back to wait for the next SNMP request.
Error Message %PIX-3-212004: Unable to send an SNMP response to IP Address IP_addr Port port interface interface_number, error code = codeExplanation This is an SNMP message. This message is logged because of an internal error in sending an SNMP response from the PIX Firewall to the specified host on the specified interface.
Recommended Action None required.
Error Message %PIX-3-212005: incoming SNMP request (number bytes) on interface int_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, destined for the PIX Firewall, exceeds the size of the internal data buffer (512 bytes) used for storing the request during internal processing; therefore, PIX Firewall is unable to process this request. This does not affect the SNMP traffic passing through the PIX Firewall via 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. This may involve modifying the configuration of the SNMP manager software.
Error Message %PIX-3-213001: PPTP control daemon socket io string, errno = num.Explanation An internal TCP socket I/O error occurred.
Recommended Action Report the problem to Cisco TAC.
Error Message %PIX-3-213002: PPTP tunnel hashtable insert failed, peer = IP_addr.Explanation An internal software error occurred while creating a new PPTP tunnel.
Recommended Action Report the problem to Cisco TAC.
Error Message %PIX-3-213003: PPP virtual interface number isn't opened.Explanation An internal software error occurred while closing a PPP virtual interface.
Recommended Action Report the problem to Cisco TAC.
Error Message %PIX-3-213004: PPP virtual 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.
Error Message %PIX-2-214001: Terminating manager session from IP_addr on interface int_name. Reason: incoming encrypted data (number bytes) longer than upper_limit_number bytesExplanation This message is logged when an incoming encrypted data packet destined at the PIX Firewall management port indicates a packet length exceeding the specified upper limit. This may be a hostile event. PIX Firewall immediately terminates this management connection.
Recommended Action Ensure that the management connection was initiated by Cisco Secure Policy Manager.
Messages 302003 to 316001
Error Message %PIX-6-302003: Built H245 connection for faddr faddr/fport laddr laddr/lportExplanation This is a connection-related message. This message is logged when an H.245 connection is started from foreign address faddr to local address laddr. This message only occurs if the PIX Firewall detects the use of an Intel Internet phone. The foreign port (fport) only displays on connections from outside the PIX Firewall. The local port value (lport) only appears on connections started on an internal interface.
Recommended Action None required.
Error Message %PIX-6-302004: Pre-allocate H323 UDP backconnection for faddr faddr/fport to laddr laddr/lportExplanation This is a connection-related message. This message is logged when an H.323 UDP back-connection is preallocated to foreign address faddr from local address laddr. This message only occurs if the PIX Firewall detects the use of an Intel Internet phone. The foreign port (fport) only displays on connections from outside the PIX Firewall. The local port value (lport) only appears on connections started on an internal interface.
Recommended Action None required.
Error Message %PIX-6-302009: Rebuilt TCP connection id for faddr faddr/fport gaddr gaddr/gport laddr laddr/lportExplanation 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 PIX Firewall. The faddr IP address is the foreign host, the gaddr IP address is a global address on the lower security level interface, and the laddr IP address is the local IP address "behind" the PIX Firewall on the higher security level interface.
Recommended Action None required.
Error Message %PIX-6-302010: conns in use, conns most usedExplanation This is a connection-related message. This message appears after a TCP connection restarts. conns is the number of connections.
Recommended Action None required.
Error Message %PIX-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.
Where:
id is an unique identifier.
interface, real-address, real-port identify the actual sockets.
mapped-address, mapped-port identify the mapped sockets.
user is the AAA name of the user.
If inbound is specified, then the original control connection was initiated from the outside. For example, for FTP, all data transfer channels are inbound if the original cont
