Cisco Wireless LAN Controller System Message Guide
DOT3AD through LAG
Downloads: This chapterpdf (PDF - 413.0KB) The complete bookPDF (PDF - 15.88MB) | Feedback

DOT3AD Messages

Table Of Contents

DOT3AD Messages

DTL Messages

EAP Messages

EMT Messages

EMWEB Messages

ETHOIP Messages

FDB Messages

FIPS Messages

HIFN Messages

HREAP Messages

IAPP Messages

IDMGR Messages

INIT Messages

IOS Messages

IPSTAT Messages

L7API Messages

L7COMM Messages

LAG Messages


DOT3AD Messages

This section contains 802.3ad (DOT3AD) messages.

Error Message    %DOT3AD-3-FAIL_CONFIG_WRITE: Failed to store config file [chars] in nv 
store 

Explanation    Fail to store config file in nv storage.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DOT3AD-0-FAIL_DOT3AD_MSGQ: LAG: Unable to create msg queue for dot3ad 
lac task. 

Explanation    LAG: Unable to create msg queue for dot3ad lac task.dot3ad sub-system not initialized

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DOT3AD-3-FAIL_DOT3AD_REBOOT: LAG in transition..Swtich reboot DUE..!! 

Explanation    LAG in transition..Swtich reboot DUE..!!

Recommended Action    No action is required.

Error Message    %DOT3AD-0-FAIL_DOT3AD_SEM: Unable to create a dot3ad semaphore. 

Explanation    Unable to initialize a dot3ad semaphore.dot3ad sub-system not initialized

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DOT3AD-3-FAIL_DOT3AD_SYSBUF: Out of System buffers. 

Explanation    Out of System buffers.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DOT3AD-0-FAIL_LAC_CREATE: Failed to create dot3ad LAC task. 

Explanation    Failed to create dot3ad LAC task.dot3ad sub-system not initialized

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DOT3AD-0-FAIL_LAC_INIT: Unable to initialize dot3ad lac task. 

Explanation    Unable to initialize dot3ad lac task.dot3ad sub-system not initialized

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

DTL Messages

This section contains designated transit list (DTL) messages.

Error Message    %DTL-4-ACL_SET_FAILED: Could not set an ACL entry. ACL Id=[dec]. 
[chars]. 

Explanation    Could not set an ACL entry.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-APENTRY_ADD_FAILED: Unable to Add AP entry due to [chars] 
(=[dec]). 

Explanation    Unable to Add AP entry.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-APENTRY_CONF_FAILED: Unable to configure an AP Entry. [chars]. 
Intf=[dec] 

Explanation    Unable to configure an AP Entry.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-APENTRY_DEL_FAILED: Unable to delete AP entry due to [chars] 
(=[dec]) 

Explanation    Unable to delete AP entry.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-6-ARP_ADD_FAILED: Unable to insert an ARP entry for 
[dec].[dec].[dec].[dec] to the ARP table.  

Explanation    Unable to insert an ARP entry to the ARP table.

Recommended Action    No action is required.

Error Message    %DTL-3-ARPDATA_LOOP_DETECTED: Found an Arp Data looping from [dec]. 
Drop it 

Explanation    Found an Arp Data looping from a particular interface. The system will drop it

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-6-ARPDATA_QUEUE_OVERLOAD:  ARP input q exceeds limit. Current val 
= [dec]   

Explanation    ARP task input queue is exceeding limit. Please see if there is any ARP loop in the network

Recommended Action    No action is required.

Error Message    %DTL-7-ARP_DELETE_STATUS: ARP Table is Full. Deleting the entry with 
IP: [int].[int].[int].[int]and Mac Address: [hex]:[hex]:[hex]:[hex]:[hex]:[hex] 
[chars] 

Explanation    Status of the request to Delete the IP/MAC entry from the ARP table

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-6-ARP_DEL_FAILED: Could not delete the ARP entry for 
[dec].[dec].[dec].[dec] from the ARP table. 

Explanation    ARP entry to delete does not exist

Recommended Action    No action is required.

Error Message    %DTL-4-ARPMAP_DEL_FAILED: [chars] 

Explanation    Failed to delete the ARP MAP

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-1-ARP_PKT_RECVD: Received ARP packet on a [chars] WLAN. 

Explanation    Received an ARP packet,through CRANITE/FORTRESS wlan.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-6-ARP_PKT_TYPE_NOT_EOIP:  Received tunneled arp packet type [dec] 
is not EOIP  

Explanation    Received arp packet should be tunneled from foreign. So it should contain EOIP type

Recommended Action    No action is required.

Error Message    %DTL-1-ARP_POISON_DETECTED: STA [[hex]:[hex]:[hex]:[hex]:[hex]:[hex], 
[dec].[dec].[dec].[dec]] ARP (op [int]) received with invalid SPA 
[int].[int].[int].[int]/TPA [int].[int].[int].[int] 

Explanation    The system might have detected ARP spoofing, or poisoning. However, this message does not necessarily imply that any malicious ARP spoofing has occurred. The message appears when the following conditions are true:

A WLAN is configured with DHCP Required, and a client device, after associating on that WLAN, transmits an ARP message without first completing DHCP. This may be normal behavior; it could happen, for example, when the client is statically addressed, or when the client is holding a valid DHCP lease from a prior association. The resulting message might look like this example:

DTL-1-ARP_POISON_DETECTED: STA [00:01:02:0e:54:c4, 0.0.0.0] ARP (op 1) received 
with invalid SPA 192.168.1.152/TPA 192.168.0.206
 
   

The effect of this condition is that the client will be unable to send or receive any data traffic until it acquires a valid DHCP address through the WLC. Table 5-1 lists explanations for each segment of the example message above.

Table 5-1 Explanations for ARP_POISON Message Segments

Message Segment
Explanation

DTL-1-ARP_POISON_DETECTED

The controller received an ARP packet from a client in DHCP_REQ state.

STA [00:01:02:0e:54:c4, 0.0.0.0]

The client ("STA," an 802.11 wireless station) has a MAC address of 00:01:02:0e:54:c4 and an IP address unknown to the controller ("0.0.0.0").

ARP (op 1)

The offending packet received from the client was an ARP request (opcode 1).

invalid SPA 192.168.1.152/TPA 192.168.0.206

The source IP address (SPA: "sender protocol address") of the ARP request was 192.168.1.152. The target IP address (TPA, or "target protocol address") of the ARP request was 192.168.0.206.


Recommended Action    When you see this message, take one or more of these steps:

Decide whether you want to force your wireless clients to DHCP first, after associating, before they can send IP packets.

If no, unconfigure DHCP required for the WLAN and this error should not appear.

If yes, configure all clients to use DHCP. If clients are configured for DHCP but sometimes send IP packets after associating without re-DHCPing, then see if the client eventually does re-DHCP and does not suffer an unacceptable outage before re-DHCPing. If the outage before re-DHCPing is acceptable, you can ignore this message. If the client never does re-DHCP after associating, then it will never be able to pass Layer 3 traffic. In that case, you need to change the client's behavior so that it always does re-DHCP after associating.

If the source IP address (SPA) of the ARP is an APIPA address (i.e. one in 169.254.0.0 /16), this might indicate that the client is attempting but failing to acquire an address using DHCP, and you should verify that your DHCP implementation works.

Error Message    %DTL-3-ARP_SEND_FAILED: Could not send [chars] to 
[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. VLAN=[dec], Intf=[dec]. [chars]. 

Explanation    Could not send an ARP packet.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-6-ARP_TABLE_FULL: ARP table is full.Could not add the new entry 

Explanation    ARP table is full.Could not add the new entry

Recommended Action    No action is required.

Error Message    %DTL-6-ARP_WRONG_ETYPE: Received Wrong Ethertype [dec]  to arp task .  

Explanation    Received ethernet type is not ARP type.

Recommended Action    No action is required.

Error Message    %DTL-3-CALLBACK_PROC_FAILED: Callback for command:[dec] failed for 
user port: [int]/[int]/[int] 

Explanation    A DTL callback process failed unexpectedly.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-4-DSINTF_GET_FAILED: Unable to get the interface set for 
distribution system. 

Explanation    Unable to get the interface set for distribution system. Probably it has not been set yet.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-DSINTF_SET_FAILED: Unable to configure the Distribution Service 
Interface [chars]. 

Explanation    Unable to set the Distribution Service Interface.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-DSNET_BCAST_FAILED: Failed to [chars] broadcast on the WLC. 

Explanation    The WLC will forward broadcast traffic only when broadcast is enabled. The toggling of this state has failed

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-DSNET_CONF_FAILED: Unable to set [chars] on Distribution 
Service interface. 

Explanation    Unable to set the specified parameter on Distribution Service interface.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-DSNET_MCAST_FAILED: Failed to [chars] multicast on the WLC. 

Explanation    The WLC will forward multicast traffic only when multicast is enabled. Toggling this state has failed

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-DSNET_MCAST_MODE_FAILED: Failed to set multicast mode to 
[chars] on the WLC. 

Explanation    The WLC can forward multicast packets by encapsulating the multicast packet in either a unicast lwapp packet or a multicast lwapp packet. Toggling this mode has failed

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-DSPORT_DEL_FAILED: Could not delete Distribution Service port: 
[dec]. [chars]. 

Explanation    Could not delete Distribution Service port.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-7-END_LOAD_DONE: Done loading Enhanced Network Driver.... 

Explanation    Done loading Enhanced Network Driver....

Recommended Action    No action is required.

Error Message    %DTL-0-END_LOAD_FAILED: Failed to load Enhanced Network Driver. 

Explanation    Failed to load Enhanced Network Driver.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-7-END_LOAD_STARTED: Loading Enhanced Network Driver. 

Explanation    Loading Enhanced Network Driver.

Recommended Action    No action is required.

Error Message    %DTL-3-FAP_ADD_FAILED: Could not add a Foreign AP port. [chars]. Port 
Intf = [dec]. 

Explanation    Could not add a Foreign AP port.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-FAP_DEL_FAILED: Could not delete a Foreign AP port. [chars]. 
Port Intf = [dec]. 

Explanation    Could not delete a Foreign AP port.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-4-FDBCMD_RECV_FAIILED: Failed to process command from user port 
[dec]/[dec]/[dec]. Family=[dec], Cmd=[dec], Event=[dec]. [chars]. 

Explanation    Failed to process command from userport.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-FDBMAC_ADD_FAILED: Unable to add an MAC entry. [chars]. 

Explanation    Unable to add an MAC entry.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-4-GRAT_ARP_NOTSENT: Did not send Gratuitous ARP to defend IP 
address ([int].[int].[int].[int]) of local interface '[chars]'. 

Explanation    Sending gratuitous ARP, to defend IP, was held due to rate limiting.

Recommended Action    No action is required.

Error Message    %DTL-3-INTFTBL_CONF_FAILED: Unable to configure Interface table 
entry.The DAPI command [chars] failed 

Explanation    Unable to configure Interface table entry.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-INVALID_ARP_TIMEOUT_ADDR: MAC entry 
([hex]:[hex]:[hex]:[hex]:[hex]:[hex]) received for timeout is INVALID. Dropping 
it. 

Explanation    MAC entry received for timeout is INVALID. Dropping it.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-4-INVALID_DOT1D_STATE: Received invalid DOT1D state [dec], for 
interface [dec]. 

Explanation    Received invalid DOT1D state for an interface.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-INVALID_MCAST_UPORT: Invalid usp ([int],[int],[int]) used for 
multicast! 

Explanation    Invalid userport used for multicast!

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-INVALID_NODEINFO_TYPE: Unsupported information type([dec]) 
found for interface [dec]. 

Explanation    Unsupported information type found.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-INVALID_PORT_INDEX: Using invalid port [int] to index Port 
Table 

Explanation    Using invalid port to index Port Table

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-1-IP_CONFLICT_DETECTED: Network device with mac addr 
[hex]:[hex]:[hex]:[hex]:[hex]:[hex] using IP address of local interface 
'[chars]'.[int].[int].[int].[int] - Received ARP [chars] ([int]) on interface 
[int] with vlan ID [int]. IP conflict is detected 

Explanation    The IP address of one of the interfaces on the switch is being used by another network element

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-4-IPPROTO_RECV_NOT_READY: DTL interface not yet ready to accept 
IP frames. 

Explanation    DTL interface not yet ready to accept IP frames. It has not yet been initialized

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-MAC_DELETE_ALL_FAILED: Failed to delete all entries from 
table.Could not delete [dec] MAC entries. 

Explanation    Failed to delete all mac entries from table

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-6-MAC_DELETE_FAILED: Failed to delete MAC entries in ARP Send 
Table. 

Explanation    Failed to delete MAC entries in ARP Send Table.

Recommended Action    No action is required.

Error Message    %DTL-3-MCAST_STREAM_REG_FAILED: Could not register a multicast stream 
on the interface [dec]. 

Explanation    Could not register a multicast stream.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-MIBOBJ_INIT_FAILED: DTL device failed to initialize MIB2 table. 

Explanation    DTL device failed to initialize MIB2table.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-MSG_Q_ENQUEUE_FAILED: Failed to enqueue message to DTL message 
queue. Head=[hex], Tail=[hex], Count=[dec]. 

Explanation    Failed to enqueue message to DTLmessage queue.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-MSG_Q_FULL: DTL msg queue is FULL. Head=[hex], Tail=[hex], 
Count=[dec]. 

Explanation    DTL msg queue is FULL.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-NPUARP_ADD_FAILED: Unable to add an ARP entry for 
[dec]:[dec].[dec].[dec] to the network processor. [chars]. 

Explanation    Unable to add an ARP entry to the network processor.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-NPUARP_DEL_FAILED: Unable to delete an ARP entry for 
[dec]:[dec].[dec].[dec] from the network processor. [chars]. 

Explanation    Unable to delete an ARP entry from the network processor.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-NPUMAC_DEL_FAILED: Unable to delete the MAC address 
[hex]:[hex]:[hex]:[hex]:[hex]:[hex] from the network processor. [chars] 

Explanation    Unable to delete a specific MAC address entry from the network processor.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-OSARP_ADD_FAILED: Unable to add an ARP entry for 
[dec]:[dec].[dec].[dec] to the operating system. [chars]. 

Explanation    Unable to add an ARP entry to the operating system.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-OSARP_DEL_FAILED: Unable to delete an ARP entry for 
[dec].[dec].[dec].[dec] from the operating system. [chars] 

Explanation    Unable to delete an ARP entry from the operating system.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-PDU_RECEIVE_FAILED: Failed to receive a PDU. 
USP:[dec]/[dec]/[dec]. Family=[dec], Cmd=[dec], Event=[dec].[chars] 

Explanation    Failed to receive a network packet.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-PKT_TX_ERROR: Failed to transmit a packet of type 
[dec],USP:[dec]/[dec]/[dec]. 

Explanation    Failed to transmit a network packet on a particular device interface.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-7-RESOLV_REQ_DROPPED: [hex]:[hex]:[hex]:[hex]:[hex]:[hex] is not 
a client,dropping the resolve request 

Explanation    The controller is dropping the ARP resolve request because the client could not be found.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-RESTART_TIMER_FAILED: [chars] 

Explanation    Failed to start ARP timeout timer

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-6-RX_ARP_LWAPP_CTL: Received lwapp ctl packet to arp task at wrong 
place.  

Explanation    Received Ethernet type is LWAPP type. But it should not be LWAPP control.

Recommended Action    No action is required.

Error Message    %DTL-3-SCBIP_ADD_FAILED: Unable to plumb SCB IP entry with key 
[hex]:[hex]:[hex]:[hex]:[hex]:[hex] for station 
[hex]:[hex]:[hex]:[hex]:[hex]:[hex] to NPU 

Explanation    Unable to plumb SCB IP entry to NPU

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-SCBIP_DEL_FAILED: Unable to remove SCB IP entry for 
[hex]:[hex]:[hex]:[hex]:[hex]:[hex] from NPU 

Explanation    Unable to remove SCB IP entry from NPU

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-0-SOCK_OPER_FAILED: Socket [chars] operation failed. 

Explanation    A socket operation has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-3-TBTBL_CONF_FAILED: Unable to configure token bucket table 
entry.The DAPI command [chars] failed 

Explanation    Unable to config token bucket table entry.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-6-TUNNELED_NOT_ARP:  Received tunneled packet type [dec] is not 
a arp packet.  

Explanation    Received tunneled arp requests should have ARP type packets.

Recommended Action    No action is required.

Error Message    %DTL-6-TUNNELED_NOT_BCAST:  Received tunneled packet type is not a 
broadcast packet.  

Explanation    Received tunneled ARP requests should be broadcast packets.

Recommended Action    No action is required.

Error Message    %DTL-3-TUNNEL_PKT_SEND_FAILED: Could not tunnel a packet to 
[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. VLAN=[dec], Intf=[dec]. [chars]. 

Explanation    Could not tunnel a packet.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %DTL-6-VAPID_OUT_OF_RANGE:  ssid [dec] of the client is out of range  

Explanation    Received tunneled ARP requests should be broadcast packets.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

EAP Messages

This section contains Extensible Authentication Protocol (EAP) messages.

Error Message    %EAP-3-MSGQUEUEFAILED: IOS Proc shim: Unable to enqueue message to proc 

Explanation    IOS message queue simulation: Unable to enqueue message to process

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %EAP-3-NOPROCQUEUE: EAP global process Queue not enabled! 

Explanation    EAP global process Queue is not enabled!

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %EAP-3-TIMERINITFAILED: Cannot init timer 

Explanation    Cannot init/create timer

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

EMT Messages

This section contains Ethernet Multisegment Topology (EMT) messages.

Error Message    %EMT-3-CONFIG_SAVE_ERROR: osapiFsWrite failed on [chars]. 

Explanation    The EMT configuration could not be saved correctly.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %EMT-3-MSG_DELIVERY_ERROR1:  Cannot deliver timer message to emt 
task!. 

Explanation    Internal system error

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %EMT-3-MSG_DELIVERY_ERROR2:  Cannot deliver enable/disable message to 
emt task!. 

Explanation    Internal system error

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %EMT-3-OUT_OF_MEMORY_ERROR1: Out of System buffers. 

Explanation    The system may be running low on memory.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %EMT-2-OUT_OF_MEMORY_ERROR2: Unable to allocate semaphore. 

Explanation    The Ethernet MultiSegment Topology task failed to initialize correctly.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %EMT-2-TASK_CREATE_ERROR: Failed to Create EMT Task.. 

Explanation    Internal system error

Recommended Action    The Ethernet MultiSegment Topology task failed to start correctly. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %EMT-2-TASK_INIT_ERROR1: Did not initialize array ptable_entry_count 
correctly !. 

Explanation    The Ethernet MultiSegment Topology task failed to initialize correctly.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %EMT-2-TASK_INIT_ERROR2: Did not initialize array ptable correctly !. 

Explanation    The Ethernet MultiSegment Topology task failed to initialize correctly.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %EMT-2-TIMER_CREATE_ERROR: Failed to create EMT Hello Timer 

Explanation    The Ethernet MultiSegment Topology task failed to initialize correctly.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %EMT-3-UNSUPPORTED_MSG_RECVD: EMT Task: Received unsupported message. 

Explanation    Internal system error

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

EMWEB Messages

This section contains embedded web (EMWEB) messages.

Error Message    %EMWEB-3-ATTACK_DETECTED: Detecting an attack from [chars]. [chars]. 
Disconnecting 

Explanation    Detecting an attack.Disconnecting.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %EMWEB-1-BUFFER_TOO_MANY: Received too many Http buffers from a 
session. BufCount([dec]) > Max ([dec]), BufLen= [dec]. Aborting session. 

Explanation    Received too many Http buffers from a session.Aborting session.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %EMWEB-3-CERTIFICATE_NOT_FOUND: Unable to find Web Authentication 
Certificate.  [chars].  

Explanation    Unable to find Web Authentication Certificate.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %EMWEB-4-CLI_OUTPUT_TRUNCATED: CLI output has been truncated. Line no: 
[dec]. 

Explanation    CLI output has been truncated.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %EMWEB-3-CONN_REJECT: An incoming connection has been rejected. 
[chars]. 

Explanation    An incoming connection has been rejected.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %EMWEB-4-CONSOLE_CLOSED: Closing serial console connection. 

Explanation    Closing serial console connection.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %EMWEB-3-FORM_SUBMIT_FAILED: Form submit action failed. [chars]. 

Explanation    Form submit action failed.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %EMWEB-3-INVALID_SOCK_NAME: Unable to get socket name. Error: [chars]. 

Explanation    Unable to get socket name.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %EMWEB-1-LOGIN_FAILED: Login failed. User:[chars]. [chars]. 

Explanation    Login failed.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %EMWEB-3-RECV_FAILED: Failed to receive a web request. [chars]. 

Explanation    Failed to receive a web request.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

ETHOIP Messages

This section contains Ethernet over IP (ETHOIP) messages.

Error Message    %ETHOIP-4-ARP_SEND_ERROR: Unable to send ARP Request for 
[int].[int].[int].[int] 

Explanation    ARP request send failed.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %ETHOIP-6-ARP_TO_RESOLVE_GW: Cannot reach [int].[int].[int].[int], no 
ARP entry for next-hop gw [int].[int].[int].[int] so tx ARP req. 

Explanation    An attempt is being made to resolve the next hop gateway.

Recommended Action    No action is required.

Error Message    %ETHOIP-2-DS_PORT_NOT_FOUND: Unable to find the DS port while trying 
to send an Ethernet over IP ping message. 

Explanation    Internal error while sending an Ethernet over IP ping message.

Recommended Action    Configure DS port if not configured. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %ETHOIP-4-GW_RESOLVE_ERROR: ping to [int].[int].[int].[int] failed, 
cannot resolve next-hop gw, rc=[dec] 

Explanation    Next hop gateway could not be resolved for the ping destination address.

Recommended Action    Please debug your network to allow resolution of next hop gateway to this destination.

Error Message    %ETHOIP-6-INVALID_PING_REPLY_RECVD1: Drop bogus Ethernet-over-IP ping 
reply from [int].[int].[int].[int] 

Explanation    Ethernet over IP task dropped a ping reply.

Recommended Action    No action is required.

Error Message    %ETHOIP-3-INVALID_PING_REPLY_RECVD2: Drop Ethernet-over-IP ping reply 
from [int].[int].[int].[int]; expected reply from [int].[int].[int].[int] 

Explanation    Ethernet over IP task dropped an unexpected ping reply.

Recommended Action    No action is required.

Error Message    %ETHOIP-3-INVALID_PKT_OPTYPE_RECVD:  Recv Ethernet over IP pkt from 
[int].[int].[int].[int], unrecognized opcode [dec] 

Explanation    Recv Ethernet over IP pkt of incorrect type.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %ETHOIP-3-INVALID_PKT_RECVD: Ethernet over IP pkt too short; pkt 
size=[int], expected min=[int] 

Explanation    Invalid Ethernet over IP packet was received.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %ETHOIP-3-INVALID_PKT_SUBTYPE_RECVD: Recv Ethernet over IP ping pkt 
from [int].[int].[int].[int]: ethtype=[hex], expected [hex] 

Explanation    Recv Ethernet over IP ping pkt of incorrect type.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %ETHOIP-2-LOCK_CREATE_ERROR: Failed to create Ethernet-over-IP ping 
lock. 

Explanation    Mobility failover and guest redundancy services did not start correctly.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %ETHOIP-3-MOBILITY_PEER_NOT_FOUND: ping to [int].[int].[int].[int] 
failed, no mobility record found for the peer. 

Explanation    Ping destination was not found in the mobility list.

Recommended Action    Please check the mobility list configuration on the controller.

Error Message    %ETHOIP-3-OSAPI_MSG_RECV_ERROR: Could not rx osapi msg. 

Explanation    Internal system error

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %ETHOIP-3-OUT_OF_MEMORY_ERROR: Out of System buffers. 

Explanation    The system may be running low on memory.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %ETHOIP-3-PING_RECVD_FROM_NON_MEMBER: Drop Ethernet-over-IP ping 
reply from [int].[int].[int].[int]; not a mobility peer 

Explanation    Ethernet over IP task dropped ping reply from unknown source.

Recommended Action    Please compare the mobility list configuration on the controller with that on the ping sender.

Error Message    %ETHOIP-6-PING_REPLY_FAILED: ping reply to [int].[int].[int].[int] 
failed, rc=[dec] 

Explanation    The previous messages possibly carries the reason for the ping failure.

Recommended Action    No action is required.

Error Message    %ETHOIP-6-PING_REQUEST_FAILED: ping request to 
[int].[int].[int].[int] failed, rc=[dec] 

Explanation    The previous messages possibly carries the reason for the ping failure.

Recommended Action    No action is required.

Error Message    %ETHOIP-3-PING_RESPONSE_TX_FAILED: Failed to tx a ping response to 
[int].[int].[int].[int], rc=[dec] 

Explanation    Internal system error

Recommended Action    Check the logs preceding this error. If no possible resolution is found, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %ETHOIP-3-PING_SEND_ERROR1: Mobility ping to [int].[int].[int].[int] 
rejected, not a mobility peer 

Explanation    Internal system information

Recommended Action    Please check mobility configuration on this WLC to see if it has the peer listed.

Error Message    %ETHOIP-3-PING_SEND_ERROR2: Mobility ping to [int].[int].[int].[int] 
rejected, transmit count [dec] exceeds allowed value [dec]. 

Explanation    mping command failed.

Recommended Action    Re-issue the mping command with a valid transmit count.

Error Message    %ETHOIP-3-PING_SEND_ERROR3: Mobility ping to [int].[int].[int].[int] 
failed, osapi msg to mobility task failed 

Explanation    mping command failed due to internal error.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %ETHOIP-3-PING_TRANSMIT_FAILED: [chars]: Failed to tx Ethernet over IP 
ping rc=[dec]. 

Explanation    Internal system error

Recommended Action    Check the logs preceding this error. If no possible resolution is found, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %ETHOIP-3-PKT_RECV_ERROR: [chars]: ethoipRecvPkt returned error 

Explanation    Internal system error

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %ETHOIP-4-RECVD_PKT_FROM_NON_MEMBER: Recv Ethernet over IP ping from 
[int].[int].[int].[int], not from a mobility peer 

Explanation    This controller received Ethernet over IP ping from a non member.

Recommended Action    Please check mobility configuration on this WLC and its peer to see if it needs correction. If the problem persists, open a case with the Technical Assistance Center via the

Error Message    %ETHOIP-4-RECVD_PKT_WITH_INVALID_GROUP: Recv Ethernet over IP ping 
from [int].[int].[int].[int]   in different Group 

Explanation    This controller received Ethernet over IP ping with group id not matching this controller

Recommended Action    Please check mobility configuration on this WLC and its peer to see groups are configured properly.

Error Message    %ETHOIP-4-RECVD_PKT_WITH_INVALID_VERSION: Recv Ethernet over IP ping 
from [int].[int].[int].[int],  with invalid version 

Explanation    This controller received Ethernet over IP ping with version not matching this controller

Recommended Action    Please check code version on this WLC and its peer to see they match. If the problem persists, open a case with the Technical Assistance Center via the

Error Message    %ETHOIP-2-SOCKET_OPEN_ERROR: Unable to open Ethernet-over-IP socket 

Explanation    Mobility failover or guest redundancy services may have been affected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %ETHOIP-3-SOCKET_READ_ERROR: read from dtl Ethernet-over-IP socket 
failed. 

Explanation    Mobility failover or guest redundancy services may be running into socket issues.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %ETHOIP-3-SOCKET_REOPEN_ERROR: Unable to re-open Ethernet-over-IP 
socket 

Explanation    Mobility failover or guest redundancy services may be running into socket issues.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %ETHOIP-3-SOCKET_SELECT_ERROR: select from Ethernet-over-IP socket 
failed with error [dec] 

Explanation    Mobility failover or guest redundancy services may be running into socket issues.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %ETHOIP-2-TASK_INIT_ERROR1: Failed to create Ethernet-over-IP socket 
rx task. 

Explanation    Mobility failover and guest redundancy services did not start correctly.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %ETHOIP-2-TASK_INIT_ERROR2: Failed to create ethoip osapi queue. 

Explanation    Mobility failover and guest redundancy services did not start correctly.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %ETHOIP-2-TASK_INIT_ERROR3: Failed to create ethoip osapi receive 
task. 

Explanation    Mobility failover and guest redundancy services did not start correctly.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

FDB Messages

This section contains FDB subsystem (FDB) messages.

Error Message    %FDB-0-MSGTAG001: Failed to Create fdb Task.. 

Explanation    Failed to Create fdb Task.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %FDB-3-MSGTAG002: Error retrieving file [chars]. 

Explanation    Error retrieving file [chars].

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %FDB-3-MSGTAG003: LIF: Unable to register for VLAN change callback. 

Explanation    LIF: Unable to register for VLAN change callback.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %FDB-3-MSGTAG004: Error on call to osapiFsWrite routine on config file 
[chars]. 

Explanation    Error on call to osapiFsWrite routine on config file [chars].

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %FDB-3-MSGTAG005: fdb Task: Failed to create, exiting..... 

Explanation    fdb Task: Failed to create, exiting.....

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

FIPS Messages

This section contains Federal Information Processing Standards (FIPS) messages.

Error Message    %FIPS-4-DUPLICATE_NDRNG_OUTPUT: Duplicate non-deterministic RNG 
output. Auto-seeding... 

Explanation    FIPS continuous RNG test failed. FIPS requires that two consecutive NDRNG block must not be the same.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %FIPS-4-DUPLICATE_RNG_OUTPUT: Duplicate FIPS 186-2 RNG output. 
Auto-seeding... 

Explanation    FIPS continuous RNG test failed. FIPS requires that two consecutive RNG block must not be the same.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %FIPS-3-LOADCONF_FAILED: Unable to load configuration. 

Explanation    Failed to load FIPS configuration.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %FIPS-4-PREREQMODE_SET_FAILED: Unable to set FIPS prerequisite mode 
because it is already [chars]. 

Explanation    FIPS Prerequisite mode is already set.

Recommended Action    No action is required.

Error Message    %FIPS-4-RNGSEEDKEY_MATCHED: FIPS 186-2 Seed matches Seed Key. 
Auto-seeding... 

Explanation    FIPS requires that RNG seed must not be the same as the RNG seed key.

Recommended Action    No action is required.

Error Message    %FIPS-3-ZEROIZATION_FAILED: Unable to reset the system key. [chars]. 

Explanation    FIPS requires a mechanism to reset critical security parameter. An error was detected while trying to reset the system key.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %FIPS-3-ZEROIZE_AP_FAILED: Unable to reset the AP key. [chars]. 

Explanation    AP reported reseting failure.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %FIPS-3-ZEROIZE_CFM_SEND_FAILED: Unable to reset the AP key. [chars]. 

Explanation    An error was detected while trying to confirm AP key reset.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %FIPS-3-ZEROIZE_REQ_SEND_FAILED: Unable to reset the AP key. [chars]. 

Explanation    An error was detected while trying to send a reset key request to the AP.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

HIFN Messages

This section contains HIFN subsystem (HIFN) messages.

Error Message    %HIFN-3-DHMAPMEM: error return [dec] while mapping DH structs 

Explanation    Call for mapping various structures like public Key, private Key has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %HIFN-3-DHMEMOVERRUN: Memory overrun in DH parameter 

Explanation    This errors occurs if some tasks overwrite into DH structure memories. A case of memory overrun has happened

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %HIFN-3-DHSYNCEXECFAIL: error return [dec] while execution of command 

Explanation    Call to execute a command on the security processor has returned a failure

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

HREAP Messages

This section contains hybrid remote-edge access point (HREAP) messages.

Error Message    %HREAP-3-MSGTAG001: Unable to write hreap configuration file. 

Explanation    Unable to write hreap configuration file.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %HREAP-6-MSGTAG002: Configuration file version < 4.2.2.3 

Explanation    The configuration file is a version earlier than software release 4.2.2.3.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

IAPP Messages

This section contains Inter-Access Point Protocol (IAPP) messages.

Error Message    %IAPP-3-AP_NOT_FOUND: AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] does not 
exist. 

Explanation    Access Point could not be found.

Recommended Action    Please check if this AP is registered in the current AP list on the controller and If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %IAPP-3-INVALID_PKT_RECVD: invalid subType([dec]) in 
iappProcessLocpClientPackets  

Explanation    An invalid IAPP Packet was received.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %IAPP-3-MOBILE_NOT_FOUND: mobile station 
[hex]:[hex]:[hex]:[hex]:[hex]:[hex] does not exist. 

Explanation    Mobile station could not be found.

Recommended Action    Please check if this mobile station is listed in the current client list on the controller and If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %IAPP-3-OUT_OF_MEMORY_ERROR: Out of System buffers. 

Explanation    The system may be running low on memory.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %IAPP-3-SCOKET_READ_ERROR: read from dtl IAPP socket failed. 

Explanation    IAPP task is experiencing problems while processing packets.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %IAPP-3-SOCKET_OPEN_ERROR: Unable to re-open IAPP socket 

Explanation    IAPP task is experiencing problems while processing packets.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %IAPP-3-SOCKET_SELECT_ERROR: select from IAPP socket failed with error 
[dec] 

Explanation    IAPP task is experiencing problems while processing packets.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %IAPP-2-TASK_INIT_ERROR1: Failed to create IAPP socket rx task.. 

Explanation    IAPP task failed to start correctly.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %IAPP-2-TASK_INIT_ERROR2: Unable to open IAPP socket 

Explanation    IAPP task failed to start correctly.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %IAPP-3-UNSUPPORTED_MSG_RECVD:  unsupported message [dec] from LOCP to 
client  

Explanation    Internal system error

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

IDMGR Messages

This section contains ID Manager (IDMGR) messages.

Error Message    %IDMGR-3-ID_MANAGER_INTERNAL_ERROR: [chars]  

Explanation    Internal error occured with ID Manager.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %IDMGR-3-INTERRUPT: [chars]  

Explanation    An id_get attempted at interrupt level.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %IDMGR-3-INVALID_ID: bad id in [chars] (id: [hex])  

Explanation    An ID Manager error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %IDMGR-3-INVALID_ID_TABLE_SIZE: bad new ID table size  

Explanation    A bad new table request to ID Manager occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %IDMGR-3-MALLOC_FAILURE: [chars]  

Explanation    A malloc failure occured in ID Manager.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

INIT Messages

This section contains initialization (INIT) messages.

Error Message    %INIT-3-CREAT_SOCK_FAILED: Failed to open socket to read MAC address 
from eth[dec]. 

Explanation    Failed to open socket to read MAC address.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %INIT-0-DRIVER_OPEN_FAILED: Failed to open the driver [chars] 

Explanation    Failed to open the driver.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %INIT-6-FE_MODULE_NOT_FOUND: Fast Ethernet Module not found. 

Explanation    Fast Ethernet Module not found.

Recommended Action    No action is required.

Error Message    %INIT-3-FILE_OPEN_FAILED: Failed to open the file [chars]. 

Explanation    Failed to open a file.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %INIT-3-INIT_GIGCARD_FAILED: Failed to initialize dual Gig card. 

Explanation    Failed to initialize dual Gig card.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %INIT-7-INIT_LED: Initializing LEDs 

Explanation    Initializing LEDs

Recommended Action    No action is required.

Error Message    %INIT-0-LICENSED_CRASH: License daemon exited abnormally.  

Explanation    License daemon exited abnormally.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %INIT-0-LICENSED_EXIT_NORMAL: License daemon exited normally with code 
[dec].  

Explanation    License daemon exited normally.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %INIT-0-LICENSED_FORK_FAILED: Failed to spawn the license daemon.  

Explanation    Failed to spawn the license daemon.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %INIT-0-LICENSED_RESTART_NOTIFY: Failed to send notification of the 
restart event.  

Explanation    Failed to send notification of the restart event.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %INIT-0-LICENSED_START_FAILED: Failed to start the license daemon.  

Explanation    Failed to start the license daemon.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %INIT-3-MDIO_CMD_INVALID: Invalid MDIO command [dec] 

Explanation    Invalid MDIO command.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %INIT-3-PARSING_FAILED: Unable to parse the content of the file 
[chars]. 

Explanation    Unable to parse the content of a file.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %INIT-3-READ_EEPROM_FAILED: Failed to read MAC address from EEPROM. 

Explanation    Failed to read MAC address from EEPROM.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %INIT-0-READ_GIGCARD_FAILED: Failed to read data from dual Gig card. 

Explanation    Failed to read data from dual Gig card.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %INIT-3-READ_HWADDR_FAILED: Failed to read MAC address from 
eth[dec].The ioctl call failed for [chars]. 

Explanation    Failed to read MAC address.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %INIT-6-SECURITY_MODULE_NOT_FOUND: Security Module not found. 

Explanation    Security Module not found.

Recommended Action    No action is required.

Error Message    %INIT-0-SEM_CREAT_FAILED: Failed to create semaphore for the INIT 
task. 

Explanation    Failed to create semaphore for the INIT task.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %INIT-0-SET_I2CADDR_FAILED: Failed to set the I2C device address for 
dual Gig card. 

Explanation    Failed to set the I2C device address for dual Gig card.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %INIT-7-SWITCH_BOOTING: Switch booting... 

Explanation    Switch booting...

Recommended Action    No action is required.

Error Message    %INIT-6-SWITCHING_TRANSCEIVER: Switching to Transceiver [chars]. 

Explanation    Switching to another transceiver.

Recommended Action    No action is required.

Error Message    %INIT-0-TASK_CREAT_FAILED: Failed to create the task [chars]. 

Explanation    Failed to create a task.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %INIT-3-TRANSCEIVER_DOWN: Transceiver [chars] is down 

Explanation    A transceiver is down

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %INIT-3-TRANSCEIVER_NOT_DETECTED: No transceivers detected. 

Explanation    No transceivers detected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %INIT-0-WRITE_GIGCARD_FAILED: Failed to write data to dual Gig card. 

Explanation    Failed to write data to dual Gig card.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %INIT-0-WRITING_INVALID_VALUE_TO_SERVICE_PORT: Writing invalid value 
of [hex] to control register of service port phy.  

Explanation    Writing invalid value of [hex] to control register of service port phy.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

IOS Messages

This section contains Cisco Internet Operating System (IOS) messages.

Error Message    %IOS-3-INV_CERT_LEN: LOCAL-AUTH(SHIM): Received peer cert too big 
(size [int]) 

Explanation    Received peer certificate that is too big

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %IOS-3-INV_PARAM: OPSSL_PARSER: Received a NULL ctx in verify callback 

Explanation    OPSSL_PARSER: Received a NULL ctx in verify callback. Internal System Error.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %IOS-3-PEER_CERT_DECODE_FAIL: LOCAL-AUTH(SHIM): Unable to decode peer 
device cert  for session [hex] 

Explanation    Unable to decode peer device certificate for the specified session

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %IOS-3-PEER_CERT_GET_FAIL: LOCAL-AUTH(SHIM): Unable to retrieve peer 
device cert for session [hex] 

Explanation    Unable to retrieve peer device certificate for the specified session

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %IOS-3-PEER_CERT_VER_FAIL: LOCAL-AUTH: Peer cert (user '[chars]') 
failed '[chars]' check 

Explanation    LOCAL-AUTH: Failed to authenticate the specified user

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %IOS-3-PEER_CERT_ZERO_LEN: OPSSL_PARSER: Received a zero len cert from 
peer for session [hex] 

Explanation    OPSSL_PARSER: Received a zero len cert from peer for the specified session

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

IPSTAT Messages

This section contains IP statistics (IPSTAT) messages.

Error Message    %IPSTAT-3-STATS_CREATE_FAIL: ipStatsCreate: Could not create [chars] 
counters for interface [dec]. 

Explanation    Could not create statistical counters. Internal System Error

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

L7API Messages

This section contains L7API subsystem (L7API) messages.

Error Message    %L7API-0-SYS_INIT_FAIL: SystemInitStatus is corrupt [hex] 

Explanation    SystemInitStatus is corrupt

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

L7COMM Messages

This section contains L7COMM subsystem (L7COMM) messages.

Error Message    %L7COMM-3-ACL_NAME_TOO_LONG: aclName too long 

Explanation    aclName too long

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %L7COMM-3-VLAN_NAME_TOO_LONG: vlanIfName too long 

Explanation    vlanIfName too long

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

LAG Messages

This section contains Link Aggregation (LAG) messages.

Error Message    %LAG-3-CMD_WAIT_FAIL: Lag command failed to complete for Interface: 
[dec]. 

Explanation    Lag command failed to complete for an interface.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %LAG-3-CONFIG_INIT_FAIL: Failed to apply component startup 
configuration for Lag. 

Explanation    Failed to apply component startup configuration for Lag.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %LAG-3-CREATE_NEW_FAIL: Could not create LAG from NV config data entry. 

Explanation    Could not create LAG from NV config data entry.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %LAG-3-CRTLBLK_GET_FAIL: Cannot create LAG '[chars]'. Exceeded Maximum 
number of LAG interfaces possible. 

Explanation    Cannot create LAG. Exceeded Maximum number of LAG interfaces possible.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %LAG-3-FILE_WRITE_FAIL: Failed to write to configuration  file 
[chars]. 

Explanation    Failed to write to configuration file.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %LAG-4-INCOMPATIBLE_PORT_SPEED: All members of lag must have same 
speed. Interface [dec] has speed different from all other members of Lag. Removing 
from Lag. 

Explanation    All members of Lag must have same speed. One of the members of Lag has speed different than all other members of Lag. Removing that interface from the Port Bundle

Recommended Action    No action is required.

Error Message    %LAG-3-INIT_FAIL: Failed to initialize Link Aggregation. 

Explanation    Failed to initialize Link Aggregation.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %LAG-3-INTF_FIND_FAIL: Interface [dec] not found in LAG [dec] member 
list. 

Explanation    Interface not found in LAG member list.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %LAG-4-INTF_SPEED_UPDATED: Speed of interface [dec] updated with the 
speed of all other members of Lag. 

Explanation    Speed of interface updated with the speed of all other members of Lag.

Recommended Action    No action is required.

Error Message    %LAG-3-INVALID_COMMAND: Invalid command received. 

Explanation    Invalid command received.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %LAG-3-INVALID_CONFIG_PARAMS: Cannot create LAG '[chars]'. Invalid 
configuration parameters. 

Explanation    Cannot create LAG. Invalid configuration parameters

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %LAG-3-MODIFY_FAIL: Failed to modify LAG [chars]. Invalid 
configuration parameters. Try configuring without any members or all members must 
be full-duplex and have same speed. Interface: [dec] 

Explanation    Failed to modify LAG. Invalid configuration parameters.Try configuring without any members or all members must be full-duplex and have same speed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %LAG-3-MODIFY_INTERNAL_ERR: Failed to modify LAG [chars]. Internal 
system error. Interface: [dec] 

Explanation    Failed to modify LAG. Internal System Error.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %LAG-3-MSG_SND_FAIL: Failed to send message to Lag for a state change 
request. Interface: [dec] 

Explanation    Failed to send message to Lag for a state change request.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %LAG-3-NIM_INFOGET_FAIL: Could not get NIM information for LAG 
interface [dec]. Failed to initialize LAG. 

Explanation    Could not get NIM information for LAG interface. Failed to initialize LAG

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %LAG-3-NV_READ_FAIL: Error retrieving file [chars] from flash 

Explanation    Error retrieving file from flash

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %LAG-0-QUEUE_CREATE_FAIL: Unable to create msg queue for Lag Task. Lag 
initialization failed. 

Explanation    Unable to create msg queue for Lag Task. Lag initialization failed

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %LAG-3-REG_CALBAK_FAIL: Unable to register for interface state 
changeLAG not initialized. 

Explanation    Unable to register for interface state changeLAG not initialized

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %LAG-3-STAT_INIT_FAIL: Failed to initialize statistical counters for 
interface. Interface: [dec]  

Explanation    Failed to initialize statistical counters for interface.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %LAG-0-TASK_CREATE_FAIL: Could not create Lag Task. Lag not 
initialized 

Explanation    Could not create Lag Task. Lag not initialized

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message    %LAG-3-TASK_SYNC_FAIL: Could not synchronize the Lag TASK. Lag not 
initialized. 

Explanation    Could not synchronize the Lag TASK. Lag not initialized.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.