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 Chapter 1, "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 Chapter 1, "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 Chapter 1, "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:
–
–
–
Recommended 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 control channel is inbound. If outbound is specified, then the original control connection was initiated from the inside.
Recommended Action None required.
Error Message %PIX-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.
Where:
id is an unique identifier.
interface, real-address, real-port identify the actual sockets.
hh:mm:ss is the lifetime of the connection.
bytes is the data transfer, in bytes, of the connection.
user is the AAA name of the user.
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.
Error Message %PIX-6-302015: Built {inbound|outbound} UDP 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 UDP connection slot between two hosts was deleted.
Where:
id is an unique identifier.
interface, real-address, real-port are the actual sockets.
mapped-address and mapped-port are the mapped sockets.
hh:mm:ss is the lifetime of the connection.
bytes is the data transfer, in bytes, of the connection.
user is the AAA name of the user.
If inbound is specified, then the original control connection is 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, then the original control connection is initiated from the inside.
Recommended Action None required.
Error Message %PIX-6-302016: Teardown UDP connection id 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.
Where:
id is an unique identifier.
interface, real-address, real-port are the actual sockets.
hh:mm:ss is the lifetime of the connection.
bytes is the data transfer, in bytes, of the connection.
user is the AAA name of the user.
Recommended Action None required.
Error Message %PIX-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.
Error Message %PIX-6-303002: src_addr Stored|Retrieved dest_addr: nat_addrsExplanation This is an FTP/URL message. This message is logged when the specified host attempts to store or retrieve data from the specified FTP site.
Recommended Action None required.
Error Message %PIX-5-304001: user src_addr Accessed JAVA URL|URL dest_addr: url.Explanation This is an FTP/URL message. This message is logged when the specified host attempts to access the specified URL.
Recommended Action None required.
Error Message %PIX-5-304002: Access denied URL chars SRC IP_addr DEST IP_addr: charsExplanation This is an FTP/URL message. This message is logged if access from the source address to the specified URL or FTP site is denied.
Recommended Action None required.
Error Message %PIX-3-304003: URL Server IP_addr timed out URL stringExplanation This message logs when a URL server times out.
Recommended Action None required.
Error Message %PIX-6-304004: URL Server IP_addr request failed URL charsExplanation This is an FTP/URL message. This message is logged if a Websense server request fails.
Recommended Action None required.
Error Message %PIX-7-304005: URL Server IP_addr request pending URL charsExplanation This is an FTP/URL message. This message is logged when a Websense server request is pending.
Recommended Action None required.
Error Message %PIX-3-304006: URL Server IP_addr not respondingExplanation This is an FTP/URL message. The Websense server is unavailable for access, and the PIX Firewall 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.
Error Message %PIX-2-304007: URL Server IP_addr not responding, ENTERING ALLOW mode.Explanation This is an FTP/URL message. This message is logged when you use the allow option of the filter command, and the Websense server(s) are not responding. The PIX Firewall allows all Web requests to continue without filtering while the server(s) are not available.
Recommended Action None required.
Error Message %PIX-2-304008: LEAVING ALLOW mode, URL Server is up.Explanation This is an FTP/URL message. This message is logged when you use the allow option of the filter command, and the PIX Firewall receives a response message from a Websense server that previously was not responding. With this response message, the PIX Firewall exits the allow mode enabling once again the URL filtering feature.
Recommended Action None required.
Error Message %PIX-2-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.
Error Message %PIX-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 rules.
Recommended Action This message signals 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 access-list bound to the nat 0 access-list.
Error Message %PIX-3-305006: Regular translation creation failed for protocol src int_name:IP_addr/port dst int_name:IP_addr/portExplanation A protocol (UDP, TCP, or ICMP) failed to create a translation through the PIX Firewall. This message appears as a fix to caveat CSCdr0063 that requested that PIX Firewall not allow packets destined to network or broadcast addresses. PIX Firewall provides this checking for addresses that are explicitly identified with static command statements. With the change, for inbound traffic, PIX Firewall denies translations for a destined IP address identified as a network or broadcast address.
The PIX Firewall does not PAT all ICMP message types; it only PATs ICMP echo and echo-reply packets (types 8 and 0). Specifically, only ICMP echo or echo-reply packets create a PAT xlate. So, when the other ICMP messages types are dropped, syslog message 305006 (on the PIX Firewall) is generated.
PIX Firewall 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 PIX Firewall does not create an xlate 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 treated as a network address and 10.2.2.255 as the broadcast address. Without an existing xlate, PIX Firewall denies inbound packets destined for 10.2.2.128 or 10.2.2.255, and logs this syslog message.
To handle the case where 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 PIX Firewall to treat 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 xlate may be created by traffic started with the inside host with the questioned IP address. Because the PIX Firewall treats 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 This message can be either an internal error or an error in the configuration.
Error Message %PIX-6-305007: addrpool_free(): Orphan IP IP_addr on interface interface_numberExplanation The PIX Firewall has attempted to translate an address that it cannot find in any of its global pools. The PIX Firewall assumes that the address was deleted and drops the request.
Recommended Action None required.
Error Message %PIX-3-305008: Free unallocated global IP address.Explanation The PIX Firewall 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 PIX Firewall is running a Stateful Failover setup and some of the internal states are momentarily out of sync between the active and standby unit. This condition is not catastrophic, and the PIX Firewall recovers automatically.
Recommended Action Report this condition to Cisco TAC if you continue to see this message.
Error Message %PIX-6-305009: Built {dynamic|static} translation from interface:real-address to interface:mapped-addressExplanation An address translation slot was created. The slot is used to translate the source address from the local side to the global side. In reverse, the slot is used to translate the destination address from the global side to the local side.
Recommended Action None required.
Error Message %PIX-6-305010: Teardown {dynamic|static} translation from interface:real-address to interface:mapped-address duration hh:mm:ssExplanation The address translation slot was deleted.
Recommended Action None required.
Error Message %PIX-6-305011: Built {dynamic|static} {TCP|UDP|ICMP} translation from interface:real-address/real-port to interface:mapped-address/mapped-portExplanation A TCP, UDP, or ICMP address translation slot was created. The slot is used to translate the source socket from the local side to the global side. In reverse, the slot is used to translate the destination socket from the global side to the local side.
Recommended Action None required.
Error Message %PIX-6-305012: Teardown {dynamic|static} {TCP|UDP|ICMP} translation from interface:real-address/real-port to interface:mapped-address/mapped-port duration hh:mm:ssExplanation The address translation slot was deleted.
Recommended Action None required.
Error Message %PIX-6-308001: PIX console enable password incorrect for num tries (from IP_addr)Explanation This is a PIX Firewall management message. This message is logged after the num number of times a user incorrectly types the password to enter privileged mode. The maximum is three attempts.
Recommended Action The privileged mode password is not necessarily the same as the password for Telnet access to the PIX Firewall. Verify the password and try again.
Error Message %PIX-4-308002: static gaddr1 laddr1 netmask mask1 overlapped with gaddr2 laddr2Explanation This message occurs if the IP addresses in one or more static command statements overlap. gaddr is the global address, which is the address on the lower security interface and laddr 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 statement, specify a host within that range such as 10.1.1.5.
Error Message %PIX-6-309002: Permitted manager connection from IP_addr.Explanation This is a PIX Firewall management message. This message logs a successful connection to the PIX Firewall management port from the specified address.
Recommended Action None required.
Error Message %PIX-6-311001: LU loading standby startExplanation This message appears when Stateful Failover update information is sent to the standby PIX Firewall unit when the standby unit is first coming on line.
Recommended Action None required.
Error Message %PIX-6-311002: LU loading standby endExplanation This message appears when Stateful Failover update information is done being sent to the standby unit.
Recommended Action None required.
Error Message %PIX-6-311003: LU recv thread upExplanation This message appears when an update acknowledgment is received from the standby unit.
Recommended Action None required.
Error Message %PIX-6-311004: LU xmit thread upExplanation This message appears when a Stateful Failover update is transmitted to the standby unit.
Recommended Action None required.
Error Message %PIX-6-312001: RIP hdr failed from IP_addr: cmd=cmd, version=vers domain=name on interface int_nameExplanation PIX Firewall received a RIP message with an operation code other than reply, the message has a version number different than what is expected on this interface, and the routing domain entry was non-zero.
Recommended Action This message is informational, but may also indicate that another RIP device is not configured correctly to communicate with the PIX Firewall.
Error Message %PIX-3-313001: Denied ICMP type=icmp_type, code=type_code from IP_addr on interface int_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 PIX Firewall discards the ICMP packet and generates this syslog message. The icmp command enables or disables pinging to an interface. With pinging disabled, the PIX Firewall 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.
Error Message %PIX-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.
Error Message %PIX-6-314001: Pre-allocate RTSP UDP backconnection for faddr faddr/fport to laddr laddr/lportExplanation PIX Firewall opened an RTSP connection for the specified IP addresses and ports.
Recommended Action No action required.
Error Message %PIX-3-315004: Fail to establish SSH session because PIX RSA host key retrieval failed.Explanation This SSH message appears when the PIX Firewall cannot find the PIX Firewall unit's RSA host key, which is required for establishing an SSH session. The PIX Firewall host key may be absent because no PIX Firewall host key was generated or because the license for this PIX Firewall does not allow DES or 3DES.
Recommended Action From the console, enter the show ca mypubkey rsa command to verify that PIX Firewall unit's RSA host key is present. If not, also enter the show version command to check whether the PIX Firewall unit's license allows DES or 3DES.
Error Message %PIX-6-315011: SSH session from IP_addr on interface int_name for user user_id disconnected by SSH server, reason: textExplanation 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.
Error Message %PIX-2-316001: Denied new tunnel to peer_IP. 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.
Messages 400000 to 407002
Error Message %PIX-4-4000nn: :sig_num sig_msg from IP_addr to IP_addr on interface int_nameExplanation Messages 400000 through 400051—Cisco Secure Intrusion Detection System signature messages.
Recommended Action Refer to the Cisco Secure Intrusion Detection System Version 2.2.1 User Guide for more information. You can view the "NSDB and Signatures" chapter, which describes each signature number (sig_num) at the following website:
http://www.cisco.com/univercd/cc/td/doc/product/iaabu/csids/csids1/csidsug/sigs.htm
All signature messages are not supported by PIX Firewall in this release. IDS syslog messages all start with%PIX-4-4000nn and have the following format:
%PIX-4-4000nn IDS:sig_num sig_msg from ip_addr to ip_addr on interface int_name
Options:
sig_num
The signature number. Refer to the Cisco Secure Intrusion Detection System Version 2.2.1 User Guide at the following website:
http://www.cisco.com/univercd/cc/td/doc/product/iaabu/csids/csids1/csidsug/sigs.htm
sig_msg
The signature message—approximately the same as the NetRanger signature message.
ip_addr
The local to remote address to which the signature applies.
int_name
The name of the interface on which the signature originated.
For example:
%PIX-4-400013 IDS:2003 ICMP redirect from 10.4.1.2 to 10.2.1.1 on interface dmz%PIX-4-400032 IDS:4051 UDP Snork attack from 10.1.1.1 to 192.168.1.1 on interface outsideTable 2-4 lists the supported signature messages.
Error Message %PIX-4-401001: Shuns clearedExplanation The clear shun command was entered to remove existing shuns from memory.
Recommended Action None required. This message is issued to allow an institution to keep a record of shunning activity.
Error Message %PIX-4-401002: Shun added: IP_addr IP_addr port portExplanation A shun command was entered, where the first IP address is the shunned host. The other addresses and ports are optional and are used to terminate the connection if available.
Recommended Action None required. This message is issued to allow an institution to keep a record of shunning activity.
Error Message %PIX-4-401003: Shun deleted: IP_addrExplanation A single shunned host was removed from the shun database.
Recommended Action None required. This message is issued to allow an institution to keep a record of shunning activity.
Error Message %PIX-4-401004: Shunned packet: IP_addr ==> IP_addr on interface int_nameExplanation A packet was dropped because the host defined by IP src is a host in the shun database. A shunned host cannot pass traffic on the interface on which it is shunned. For example, an external host on the Internet can be shunned on the outside interface.
Recommended Action None required. This message provides a record of the activity of shunned hosts. This message and %PIX-4-401005 can be used to evaluate further risk assessment concerning this host.
Error Message %PIX-4-401005: Shun add failed: unable to allocate resources for IP_addr IP_addr port portExplanation The PIX Firewall is out of memory; a shun could not be applied.
Recommended Action The Cisco Secure Intrusion Detection System should continue to attempt to apply this rule. Attempt to reclaim memory and reapply shun manually, or wait for the Cisco Secure Intrusion Detection System to do this.
Error Message %PIX-4-402101: decaps: rec'd IPSEC packet has invalid spi for destaddr=IP_addr, prot=protocol, spi=spiExplanation Received IPSec packet specifies SPI that does not exist in SADB. This may be a temporary condition due to slight differences in aging of SAs between the IPSec peers, or it may be because the local SAs have been cleared. It may also be because of incorrect packets sent by the IPSec peer. This may also be an attack.
Recommended Action The peer may not acknowledge that the local SAs have been cleared. If a new connection is established from the local router, the two peers may then reestablish successfully. Otherwise, if the problem occurs for more than a brief period, either attempt to establish a new connection or contact the peer's administrator.
Error Message %PIX-4-402102: decapsulate: packet missing packet_type, destadr=dest_addr, actual prot=protocolExplanation Received IPSec packet missing an expected AH or ESP header. The peer is sending packets that do not match the negotiated security policy. This may be an attack. packet_type is either AH or ESP.
Recommended Action Contact the peer's administrator.
Error Message %PIX-4-402103: identity doesn't match negotiated identity (ip) dest_addr= IP_addr, src_addr= IP_addr, prot= protocol, (ident) local=IP_addr, remote=IP_addr, local_proxy=IP_addr/IP_addr/port/port, remote_proxy=IP_addr/IP_addr/port/portExplanation An unencapsulated IPSec packet does not match the negotiated identity. The peer is sending other traffic through this security association. It may be due to an security association selection error by the peer. This may be a hostile event.
Recommended Action Contact the peer's administrator to compare policy settings.
Error Message %PIX-4-402106: Rec'd packet not an IPSEC packet (ip) dest_addr= IP_addr, src_addr= IP_addr, prot= protocolExplanation The received packet matched the crypto map ACL, but it is not IPSec-encapsulated; the IPSec Peer is sending unencapsulated packets. This error can occur because of a policy setup error on the peer. For example, the firewall only accepts encrypted Telnet traffic to the outside interface port 23. If you attempt to Telnet without IPSec encryption to the outside interface on port 23, this message appears, but not on a telnet or traffic to the outside interface on ports other than 23. This error can also signify a hostile event. This syslog message is not generated except under the conditions cited (for example, it is not generated for traffic to the firewall interfaces themselves). See messages 710001, 710002, and 710003 for messages that track TCP and UDP requests.
Recommended Action Contact the peer's administrator to compare policy settings.
Error Message %PIX-4-403101: PPTP session state not established, but received an XGRE packet, tunnel_id=id, session_id=sessionExplanation PIX Firewall received a PPTP XGRE packet without a corresponding control connection session.
Recommended Action If this message occurs frequently, report the problem to Cisco TAC.
Error Message %PIX-4-403102: PPP virtual interface int_name rcvd pkt with invalid protocol: protocol, reason: text.Explanation PIX Firewall received an XGRE encapsulated PPP packet with an invalid protocol field.
Recommended Action If this message occurs frequently, report the problem to Cisco TAC.
Error Message %PIX-4-403103: PPP virtual interface max connections reached.Explanation PIX Firewall cannot accept additional PPTP connections.
Recommended Action None required. Connections are allocated as soon as they are freed.
Error Message %PIX-4-403104: PPP virtual interface int_name requires mschap for MPPE.Explanation The MPPE is configured but MS-CHAP authentication is not.
Recommended Action Add MS-CHAP authentication with the vpdn group group_name ppp authentication command.
Error Message %PIX-4-403106: PPP virtual interface int_name requires RADIUS for MPPE.Explanation The MPPE is configured but RADIUS authentication is not.
Recommended Action Add RADIUS authentication with the vpdn group group_name ppp authentication command.
Error Message %PIX-4-403107: PPP virtual interface int_name missing aaa server group infoExplanation AAA server configuration information cannot be found.
Recommended Action Add AAA server information with the vpdn group group_name client authentication aaa aaa_server_group command.
Error Message %PIX-4-403108: PPP virtual interface int_name missing client ip address optionExplanation The client IP address pool information is missing.
Recommended Action Add IP address pool info with the vpdn group group_name client configuration address local address_pool_name command.
Error Message %PIX-4-403109: Rec'd packet not an PPTP packet. (ip) dest_addr= IP_addr, src_addr= IP_addr, data: text.Explanation The PIX Firewall received a spoofed PPTP packet. This may be a hostile event.
Recommended Action Contact the peer's administrator to check the PPTP configuration settings.
Error Message %PIX-4-403110: PPP virtual interface int_name, user: user missing MPPE key from aaa server.Explanation The AAA server is not returning the MPPE key attributes required to set up the MPPE encryption policy.
Recommended Action Check the AAA server configuration and if the AAA server cannot return MPPE key attributes, use local authentication instead with the vpdn group group_name client authentication local command.
Error Message %PIX-6-403500: PPPoE - Service name 'any' not received in PADO. Intf:outside AC:ac-name.Explanation The PIX Firewall requested the PPPoE service "any" from the access controller at the Internet service provider. The response from the service provider includes other services but does not include the service "any." This is a discrepancy in the implementation of the protocol. The PADO packet is processed normally and connection negotiations continue.
Recommended Action None required.
Error Message %PIX-3-403501: PPPoE - Bad host-unique in PADO - packet dropped. Intf:outside AC:ac-nameExplanation The PIX Firewall sent an identifier called the "host-unique" value to the access controller. The access controller responded with a different "host-unique" value. The PIX Firewall is unable to identify the corresponding connection request for this response. The packet is dropped and connection negotiations are aborted.
Recommended Action Contact the Internet service provider. Either the access controller at the service provider is mishandling the "host-unique" value or the PADO packet is being forged.
Error Message %PIX-3-403502: PPPoE - Bad host-unique in PADS - dropping packet. Intf:outside AC:ac-nameExplanation The PIX Firewall sent an identifier called the "host-unique" value to the access controller. The access controller responded with a different "host-unique" value. The PIX Firewall is unable to identify the corresponding connection request for this response. The packet was dropped and connection negotiations were aborted.
Recommended Action The Internet service provider should be contacted. Either the access controller at the service provider is mishandling the "host-unique" value or the PADO packet is being forged.
Error Message %PIX-3-403503: PPPoE:PPP link down:ReasonExplanation The PPP link has gone down. There are many reasons why this could happen. The first format will display a reason if PPP provides one.
Recommended Action Check the network link to ensure that the link is connected. The access concentrator could be down. Check to ensure that your authentication protocol matches the access concentrator. Ensure that your name and password are correct. Check with your ISP or network support person.
Error Message %PIX-3-403504: PPPoE:No 'vpdn group' for PPPoE is createdExplanation PPPoE requires a dial-out configuration before starting a PPPoE session. In general, the configuration should specify a dialing policy, the PPP authentication, the username and a password. The following example configures the PIX Firewall for PPPoE dialout. It also uses my-username and my-password to authenticate the access concentrator, using PAP if necessary.
Examplevpdn group my-pppoe request dialout pppoevpdn group my-pppoe ppp authentication papvpdn group my-pppoe localname my-usernamevpdn username my-username password my-passwordip address outside pppoe setrouteRecommended Action The user should configure a VPDN group for PPPoE.
Error Message %PIX-3-403505d: PPPoE:PPP - Unable to set default route to address at interface-nameExplanation Usually this message is followed by "- default route already exists."
Recommended Action Remove the current default route or remove the "setroute" parameter so that there is no conflict between PPPoE and the manually configured route.
Error Message %PIX-3-403506: PPPoE:failed to assign PPP address netmask %netmask at interfaceExplanation This message is followed by "- subnet is the same as interface," or "on failover channel."
Recommended Action In the first case, change the address causing the conflict. In the second case, configure the PPPoE on an interface other than the failover interface.
Error Message %PIX-4-404101: ISAKMP: Failed to allocate address for client from pool pool_idExplanation ISAKMP failed to allocate an IP address for the VPN client from the pool you specified with the ip local pool command statement.
Recommended Action Use the ip local pool command to specify additional IP addresses for the pool.
Error Message %PIX-4-405101: Unable to Pre-allocate H225 Call Signalling Connection for faddr faddr[/fport] to laddr laddr[/lport]Explanation PIX Firewall failed to allocate RAM system memory while starting a connection or has no more address translation slots available.
Recommended Action If this message occurs periodically, it can be ignored. If it repeats frequently, contact Cisco TAC. Also, 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-4-405102: Unable to Pre-allocate H245 Connection for faddr faddr[/fport] to laddr laddr[/lport]Explanation PIX Firewall failed to allocate RAM system memory while starting a connection or has no more address translation slots available.
Recommended Action If this message occurs periodically, it can be ignored. If it repeats frequently, contact Cisco TAC. Also, 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-4-405102: Unable to Pre-allocate H245 Connection for faddr faddr[/fport] to laddr laddr[/lport]Explanation PIX Firewall failed to allocate RAM system memory while starting a connection or has no more address translation slots available.
Error Message If this message occurs periodically, it can be ignored. If it repeats frequently, contact Cisco TAC. Also, 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-4-405103: H225 message from <src_ip/src_port> to <dest_ip/dest_pot>t contains bad protocol discriminator <hex_value>Explanation This event is logged when PIX is expecting the protocol discriminator, 0x08, but it received something other than 0x08. This could happen because the endpoint is sending a bad packet, or PIX received a message segment other than the first.
Recommended Action Packet is let through since we currently do not handle segments.
Error Message %PIX-4-406001: FTP port command low port: IP_addr/port to IP_addr on interface int_nameExplanation A client issued an ftp port command and supplied a port lesser than 1024 (in the well-known port range typically devoted to server ports). This is indicative of an attempt to avert the site's security policy. PIX Firewall drops the packet, terminates the connection, and logs the event.
Recommended Action None required.
Error Message %PIX-4-406002: FTP port command different address: IP_addr(IP_addr) to IP_addr on interface int_nameExplanation A client issued an ftp port command and supplied an address other than the address used in the connection. This is indicative of an attempt to avert the site's security policy. PIX Firewall drops the packet, terminates the connection, and logs the event. Note that "(IP_addr)" refers to the port command.
Recommended Action None required.
Error Message %PIX-4-407001: Deny traffic for local-host interface:ip_addr, license limit of count exceededExplanation The host limit was exceeded. An inside host is counted toward the limit when one of the following conditions is true:
–
–
Recommended Action The host limit is enforced on the low-end platforms. Use the show version command to view the host limit. Use the show local-host command to view the current active hosts and the inside users that have sessions at the PIX Firewall. To force disconnect one or more users, use the clear local-host command. To expire the inside users more quickly from the limit, set the xlate, connection, and uauth timeouts to the recommended values or lower. (See Table 2-5.)
Table 2-5 Timeouts and Recommended Values
xlate
00:05:00 (five minutes)
conn
00:01:00 (one hour)
uauth
00:05:00 (five minutes)
Error Message %PIX-3-407002: Embryonic limit neconns/elimit for through connections exceeded.faddr/fport to gaddr (laddr)/lport on interface int_nameExplanation This message is about connections through the PIX Firewall. This message is logged when the number of connections from specified foreign address over specified global address to the specified local address exceeds the maximum embryonic limit for that static. PIX Firewall attempts to accept the connection if it can allocate memory for that connection. It proxies on behalf of local host and sends a SYN_ACK packet to the foreign host. PIX Firewall retains pertinent state information, drops the packet, and waits for the client's acknowledgment.
Recommended Action It might be legitimate traffic, or indicate that a denial of service (DoS) attack is in progress. Check the source address to determine where the packets are coming from and whether it is a valid host.
Messages 500001 to 502103
Error Message %PIX-5-500001: ActiveX content modified src IP_addr dest IP_addr on interface int_name.Explanation This message is logged after you turn on the activex option using the filter command, and the PIX Firewall detects an ActiveX object. The activex option allows the PIX Firewall to filter out ActiveX contents by modifying it so that it no longer is tagged as an HTML object.
Recommended Action None required.
Error Message %PIX-5-500002: Java content modified src IP_addr dest IP_addr on interface int_name.Explanation This message is logged after you turn on the java option using the filter command, and the PIX Firewall detects an Java applet. The java option allows the PIX Firewall to filter out Java contents by modifying it so that it no longer is tagged as an HTML object.
Recommended Action None required.
Error Message %PIX-5-500003: Bad TCP hdr length (hdrlen=bytes, pktlen=bytes) from src_addr/sport to dest_addr/dport, flags: tcp_flags, on interface int_nameExplanation This message indicates that a header length in TCP is incorrect. Some operating systems do not handle TCP RSTs (resets) correctly when responding to a connection request to a disabled socket. If a client tries to connect to an FTP server outside the PIX Firewall and FTP is not listening, then the server sends an RST. Some operating systems send incorrect TCP header lengths, which causes this problem. UDP uses ICMP port unreachable messages.
The TCP header length may indicate that it is larger than the packet length resulting in a negative number of bytes being transferred. A negative number is displayed by syslog as an unsigned number making it appear far larger than would be normal; for example, showing 4 GB transferred in 1 second.
Recommended Action None required. This message should occur infrequently.
Error Message %PIX-4-500004: Invalid transport field for protocol=protocol, from src_addr/src_port to dest_addr/dest_portExplanation This message appears when there is an invalid transport number, in which the source or destination port number for a protocol is zero. The protocol field is 6 for TCP and 17 for UDP.
Recommended Action If these messages persist, contact the peer's administrator.
Error Message %PIX-5-501101: User transitioning priv levelExplanation The privilege level of a command was changed.
Recommended Action None required.
Error Message %PIX-5-502101: New user added to local dbase: Uname: username Priv: priv_lvl Encpass: encrypted_paswdExplanation A new username record was created.
Recommended Action None required.
Error Message %PIX-5-502102: User deleted from local dbase: Uname: username Priv: priv_lvl Encpass: encrypted_paswdExplanation A username record was deleted.
Recommended Action None required.
Error Message %PIX-5-502103: User priv level changed: Uname: username From: old_priv_lvl
To: new_priv_lvlExplanation The privilege level of a user changed.
Recommended Action None required.
Messages 602101 to 614002
Error Message %PIX-6-602101: PMTU-D packet packet_length bytes greater than effective mtu mtu_value dest_addr=dest_ip, src_addr=source_ip, prot=protocolExplanation This message occurs when the PIX Firewall sends an ICMP destination unreachable message and when fragmentation is needed, but the "don't-fragment" bit is set.
Recommended Action Ensure that the data is sent correctly.
Error Message %PIX-6-602102: Adjusting IPSec tunnel mtu...Explanation The MTU for an IPSec tunnel is adjusted from Path MTU Discovery.
Recommended Action Check MTU of the IPSec tunnels. If effective MTU is smaller than normal, check intermediate links.
Error Message %PIX-6-602301: sa created...Explanation A new security association (SA) was created.
Explanation Informational message.
Error Message %PIX-6-602302: deleting saExplanation An SA was deleted.
Recommended Action Informational message.
Error Message %PIX-6-603101: PPTP received out of seq or duplicate pkt, tnl_id=id, sess_id=session, seq=num.Explanation PIX Firewall received a PPTP packet that was out of sequence or duplicated.
Recommended Action If the packet count is high, contact the peer administrator to check client PPTP configuration.
Error Message %PIX-6-603102: PPP virtual interface int_name - user: user aaa authentication started.Explanation PIX Firewall sent an authentication request to the AAA server.
Recommended Action None required.
Error Message %PIX-6-603103: PPP virtual interface int_name - user: user aaa authentication statusExplanation PIX Firewall received an authentication response from the AAA server.
Recommended Action None required.
Error Message %PIX-6-603104: PPTP Tunnel created, tunnel_id is id, remote_peer_ip is IP_addr, ppp_virtual_interface_id is id, client_dynamic_ip is IP_addr, username is login, MPPE_key_strength is charsExplanation A PPTP tunnel was created.
Recommended Action None required.
Error Message %PIX-6-603105: PPTP Tunnel deleted, tunnel_id = id, remote_peer_ip= IP_addrExplanation A PPTP tunnel was deleted.
Recommended Action None required.
Error Message %PIX-6-603106: L2TP Tunnel created, tunnel_id is id, remote_peer_ip is peer_IP_addr, ppp_virtual_interface_id is pix_interface_id, client_dynamic_ip is assigned_client_ip username is login_usrnameExplanation An L2TP tunnel was created.
Recommended Action None required.
Error Message %PIX-6-603107: L2TP Tunnel deleted, tunnel_id = id, remote_peer_ip = IP_addrExplanation An L2TP tunnel was deleted.
Recommended Action None required.
Error Message %PIX-6-603108: Built PPTP Tunnel at interface, tunnel-id = id, remote-peer = address, virtual-interface = index, client-dynamic-ip = address, username = username, MPPE-key-strength = strengthExplanation This message is displayed each time a new PPPoE tunnel is created.
Recommended Action None required.
Error Message %PIX-6-603109: Teardown PPPOE Tunnel at interface-name, tunnel-id = id, remote-peer = addressExplanation This message is displayed each time a new PPPoE tunnel is deleted.
Recommended Action None required.
Error Message %PIX-6-604101: DHCP client interface int_name: Allocated ip = ip_address,
mask = mask, gw = gateway_addressExplanation The PIX Firewall DHCP client successfully obtained an IP address from a DHCP server. The dhcpc command statement lets PIX Firewall obtain an ip_address and network mask for a network interface from a DHCP server as well as a default route. The default route statement uses the gateway_address as the address of the default router.
Recommended Action None required.
Error Message %PIX-6-604102: DHCP client interface int_name: address releasedExplanation The PIX Firewall DHCP client released an allocated IP address back to the DHCP server.
Recommended Action None required.
Error Message %PIX-6-604103: DHCP daemon interface int_name: address granted MAC_addr (IP_addr)Explanation The PIX Firewall DHCP server granted an IP address to an external client.
Recommended Action None required.
Error Message %PIX-6-604104: DHCP daemon interface int_name: address releasedExplanation An external client released an IP address back to the PIX Firewall DHCP server.
Recommended Action None required.
Error Message %PIX-6-605004: Login denied from {source_address/source_port | serial} to {interface:dest_address/service | console} for user "user"Explanation This message appears after an incorrect login attempt. The firewall allows 3 login attempts per session. After the third attempt, the firewall terminates the session. For SSH and Telnet logins, the firewall generates a message either after the third failure or if at least one failed attempt has been tried, and the TCP session is terminated before the third attempt. For all other management logins, each failed attempt generates a message.
Recommended Action If this message appears infrequently, no action is required. If this message appears frequently, it can indicate an attack. Inform the user to verify their username and password.
Error Message %PIX-6-605005: Login permitted from {source_address/source_port | serial} to {interface:dest_address/service | console} for user "user"Explanation This message appears when a user is authenticated successfully and a management session starts.
Recommended Action This is an informational message.
Error Message %PIX-6-606001: PDM session number num from IP_addr startedExplanation This message indicates that an administrator has been authenticated successfully and a PDM session was started.
Recommended Action None required.
Error Message %PIX-6-606002: PDM session number num from IP_addr endedExplanation This message indicates that a PDM session ended.
Recommended Action None required.
Error Message %PIX-6-607001: Pre-allocate SIP conn_type secondary channel for outside-interface:address/port to inside-interface:address from sip_message messageExplanation This message indicates that the fixup sip command pre-allocated a SIP connection after inspecting a SIP message.
Recommended Action None required.
Error Message %PIX-6-608001: Pre-allocate Skinny conn_type secondary channel for outside-interface:address to inside-interface:address/port from skinny_message messageExplanation This message indicates that the fixup skinny command pre-allocated a Skinny connection after inspecting a Skinny message.
Recommended Action None required.
Error Message %PIX-6-609001: Built local-host int_name:ip_addrExplanation A network state container is reserved for host ip_addr connected to interface int_name. This is an informational message.
Recommended Action None required.
Error Message %PIX-6-609002: Teardown local-host int_name:ip_addr duration hh:mm:ssExplanation A network state container for host ip_addr connected to interface int_name is removed. This is an informational message.
Recommended Action None required.
Error Message %PIX-3-610001: NTP daemon interface int_name: Packet denied from IP_addrExplanation An NTP packet was received from a host that does not match one of the configured NTP servers. The PIX Firewall is only an NTP client; it is not a time server and does not respond to NTP requests.
Recommended Action None required.
Error Message %PIX-3-610002: NTP daemon interface int_name: Authentication failed for packet from IP_addrExplanation The received NTP packet failed the authentication check.
Recommended Action Ensure that both the PIX Firewall and the NTP server are set to use authentication, and the same key number and value.
Error Message %PIX-6-610101: Authorization failed: Cmd: cmd_string Cmdtype: command_modifierExplanation Command authorization failed for the specified command.
Recommended Action None required.
Error Message %PIX-6-611101: User authentication succeeded: Uname: usernameExplanation User authentication when accessing the PIX Firewall succeeded.
Recommended Action None required.
Error Message %PIX-6-611102: User authentication failed: Uname: usernameExplanation User authentication failed when attempting to access the PIX Firewall.
Recommended Action None required.
Error Message %PIX-5-611103: User logged out: Uname: usernameExplanation The specified user logged out.
Recommended Action None required.
Error Message %PIX-6-611301: VPNClient: NAT configured for Client Mode with no split"tunneling: NAT addr: nat_ip_addrExplanation The VPN client policy for client mode with no split tunneling was installed.
Recommended Action None required.
Error Message %PIX-6-611302: VPNClient: NAT exemption configured for Network Extension Mode with no split tunnelingExplanation VPN client policy for network extension mode with no split tunneling was installed.
Recommended Action None required.
Error Message %PIX-6-611303: VPNClient: NAT configured for Client Mode with split tunneling: NAT addr: nat_ip_addr Split Tunnel Networks: split_network_1/split_netmask_1 split_network_2/split_netmask_2 ...Explanation VPN client policy for client mode with split tunneling was installed.
Recommended Action None required.
Error Message %PIX-6-611304: VPNClient: NAT exemption configured for Network Extension Mode with split tunneling: Split Tunnel Networks: split_network_1/split_netmask_1 split_network_2/split_netmask_2 ...Explanation VPN client policy for network extension mode with split tunneling was installed.
Recommended Action None required.
Error Message %PIX-6-611305: VPNClient: DHCP Policy installed: Primary DNS: ip_addr Secondary DNS: ip_addr Primary WINS: ip_addr Secondary WINS: ip_addrExplanation VPN client policy for DHCP was installed.
Recommended Action None required.
Error Message %PIX-6-611306: VPNClient: Perfect Forward Secrecy Policy installedExplanation Perfect forward secrecy was configured as part of the VPN client download policy.
Recommended Action None required.
Error Message %PIX-6-611307: VPNClient: Head end : headend_ip_addrExplanation The VPN client is connected to the specified headend.
Recommended Action None required.
Error Message %PIX-6-611308: VPNClient: Split DNS Policy installed: List of domains: domain_1 domain_2 ...Explanation A split DNS policy was installed as part of the VPN client downloaded policy.
Recommended Action None required.
Error Message %PIX-6-611309: VPNClient: Disconnecting from head end and uninstalling previously downloaded policy: Head End : headend_ip_addrExplanation A VPN client is disconnecting and uninstalling a previously installed policy.
Recommended Action None required.
Error Message %PIX-6-611310: VNPClient: XAUTH Succeeded: Peer: headend_ip_addrExplanation The VPN client Xauth succeeded with the specified headend.
Recommended Action None required.
Error Message %PIX-6-611311: VNPClient: XAUTH Failed: Peer: headend_ip_addrExplanation The VPN client Xauth failed with the specified headend.
Recommended Action None required.
Error Message %PIX-5-612001:Auto Update succeeded:name, version:versionExplanation An update from an Auto Update Server was successful. The name variable is PIX image, PDM file, or configuration. The version variable is the version number of the update.
Recommended Action None required.
Error Message %PIX-4-612002:Auto Update failed:name, version:version, reason:descriptionExplanation This indicates that an update from an Auto Update Server failed. The name variable is PIX image, PDM file, or configuration. The version variable is the version number of the update. The description variable describes why the update failed. Possible reasons for the failure include invalid image file, connection lost to server, configuration errors, etc.
Recommended Action Check the configuration of the Auto Update Server.
Error Message %PIX-4-612003:Auto Update failed to contact:url, reason:descriptionExplanation This indicates that the Auto Update daemon was unable to contact the specified URL url. This could be the URL of the Auto Update Server or one of the file server URLs returned by the Auto Update Server. The description field describes why the contact failed. Possible reasons for the failure include no response from server, authentication failed, file not found, etc.
Recommended Action Check the configuration of the Auto Update Server.
Error Message %PIX-6-614001: Split DNS: request patched from server: original-server-ip to server: enterprise-server-ipExplanation Split DNS is redirecting DNS queries from the original destination server to the primary enterprise DNS server.
Recommended Action None required.
Error Message %PIX-6-614002: Split DNS: reply from server:enterprise-server-ip reverse patched back to original server:original-server-ipExplanation Split DNS is redirecting DNS queries from the enterprise DNS server to the original destination server.
Recommended Action None required.
Messages 701001 to 710006
Error Message %PIX-7-701001: alloc_user() out of Tcp_user objectsExplanation This is a AAA message. This message is logged if the user authentication rate is too high for the PIX Firewall to handle new AAA requests.
Recommended Action Enable Flood Defender with the floodguard enable command.
Error Message %PIX-7-702301: lifetime expiring...Explanation An SA lifetime has expired.
Recommended Action Debugging message.
Error Message %PIX-3-702302: replay rollover detected...Explanation More than 4 billion packets have been received in the IPSec tunnel and a new tunnel is being negotiated.
Explanation Contact the peer's administrator to compare the SA lifetime setting.
Error Message %PIX-7-702303: sa_request...Explanation IPSec has requested IKE for new SAs.
Recommended Action Debugging message.
Error Message %PIX-7-709001: FO replication failed: cmd=command returned=codeError Message %PIX-7-709002: FO unreplicable: cmd=commandExplanation These failover messages only appear during the development debug testing phase.
Recommended Action None required.
Error Message %PIX-1-709003: (Primary) Beginning configuration replication: Receiving from mate.Explanation This is a failover message. This message is logged when the active unit starts replicating its configuration to the standby unit. "(Primary)" can also be listed as "(Secondary)" for the secondary unit.
Recommended Action None required.
Error Message %PIX-1-709004: (Primary) End Configuration Replication (ACT)Explanation This is a failover message. This message is logged when the active unit completes replicating its configuration on the standby unit. "(Primary)" can also be listed as "(Secondary)" for the secondary unit.
Recommended Action None required.
Error Message %PIX-1-709005: (Primary) Beginning configuration replication: Receiving from mate.Explanation This message indicates that the standby PIX Firewall received the first part of the configuration replication from the active PIX Firewall. "(Primary)" can also be listed as "(Secondary)" for the secondary unit.
Recommended Action None required.
Error Message %PIX-1-709006: (Primary) End Configuration Replication (STB)Explanation This is a failover message. This message is logged when the standby unit completes replicating a configuration sent by the active unit. "(Primary)" can also be listed as "(Secondary)" for the secondary unit.
Recommended Action None required.
Error Message %PIX-2-709007: Configuration replication failed for command command_nameExplanation This is a failover message. This message is logged when the standby unit is unable to complete replicating a configuration sent by the active unit. The command at which the failure occurs displays at the end of the message.
Recommended Action Write down the command name and inform Cisco TAC.
Error Message %PIX-7-710001: TCP access requested from source_address/source_port to interface:dest_address/serviceExplanation This message appears when the first TCP packet destined to the firewall requests to establish a TCP session. This packet is the first SYN packet of the three-way handshake. This message appears when the respective access control list (telnet, http or ssh) has permitted the packet. However, the SYN cookie verification is not yet completed and no state is reserved.
Recommended Action None required.
Error Message %PIX-7-710002: {TCP|UDP} access permitted from source_address/source_port to interface:dest_address/serviceExplanation For a TCP connection, this message appears when the second TCP packet destined to the firewall requests to establish a TCP session. This packet is the final ACK of the three-way handshake. This message appears when the respective access control list (Telnet, HTTP, or SSH) has permitted the packet. Also, the SYN cookie verification is successful and the state is reserved for the TCP session. For a UDP connection, the connection was permitted. For example, this message appears (with the service snmp) when the firewall receives an SNMP request from an authorized SNMP management station, and the request has been processed. When the service is snmp, this message occurs a maximum of 1 time every 10 seconds so that the log receiver is not overwhelmed.
Recommended Action None required.
Error Message %PIX-3-710003: {TCP|UDP} access denied by ACL from source_address/source_port to interface:dest_address/serviceExplanation This message appears when the firewall denies an attempt to connect to the interface service. For example, this message appears (with the service snmp) when the firewall receives an SNMP request from an unauthorized SNMP management station.
Recommended Action Use the show http, show ssh, or show telnet command to verify that the firewall is configured to permit the service access from the host or network. If this message appears frequently, it can indicate an attack.
Error Message %PIX-4-710004: TCP connection limit exceeded from source_address/source_port to interface:dest_address/serviceExplanation The maximum number of firewall management connections for the service was exceeded. The firewall permits at most five concurrent management connections per management service.
Recommended Action From the console, use the kill command to release the unwanted session.
Error Message %PIX-7-710005: {TCP|UDP} request discarded from source_address/source_port to interface:dest_address/serviceExplanation This message appears when the firewall does not have a UDP server that services the UDP request. The message can also indicate a TCP packet that does not belong to any session on the firewall. In addition, this message appears (with the service snmp) when the firewall receives an SNMP request with an empty payload, even if it is from an authorized host. When the service is snmp, this message occurs a mximum of 1 time every 10 seconds so that the log receiver is not overwhelmed.
Recommended Action In networks that heavily utilize broadcasting services such as DHCP, RIP or NetBios, the frequency of this message can be high. If this message appears in excessive number, it may indicate an attack.
Error Message %PIX-7-710006: protocol request discarded from source_address to interface:dest_addressExplanation This message appears when the firewall does not have an IP server that services the IP protocol request; for example, the firewall receives IP packets that are not TCP or UDP, and the firewall cannot service the request.
Recommended Action In networks that heavily utilize multicasting, the frequency of this message can be high. If this message appears in excessive number, it may indicate an attack.
