Cisco Wireless LAN Controller System Message Guide, Release 7.4
NIM NMSP NULL and OSAPI System Messages
Downloads: This chapterpdf (PDF - 158.0KB) The complete bookPDF (PDF - 4.85MB) | Feedback

Table of Contents

NIM NMSP NULL and OSAPI System Messages

NIM Messages

NMSP Messages

NULL Messages

OSAPI Messages

NIM NMSP NULL and OSAPI System Messages

This chapter contains the following topics:

NIM Messages

This section contains Networks-in-Motion (NIM) messages.

Error Message NIM-0-ADMIN_MODE_DISABLE: Port %d Admin Mode is Disable.

Explanation The Port Admin Mode is disabled.

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/cisco/web/support/index.html . 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 NIM-0-ADMIN_MODE_ENABLE: Port %d Admin Mode is Enable.

Explanation The Port Admin Mode is 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/cisco/web/support/index.html . 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 %NIM-0-CREAT_TASK_FAIL: Failed to create the task [chars]

Explanation The system has failed to create the 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/cisco/web/support/index.html . 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 NIM-0-GET_LAGMAC_FAIL: LAG MAC address error: Invalid arguments. Got null pointer.

Explanation A LAG MAC address error has occurred: The system has detected invalid arguments. The system has a null pointer.

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/cisco/web/support/index.html . 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 NIM-0-INDEX_ERR: Invalid index [int] while %s per port AP load information.

Explanation An internal error has occurred when processing AP load information. Some AP management functions may not work as expected.

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/cisco/web/support/index.html . 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 %NIM-0-MSGQ_CREATE_FAIL: Unable to create msg queue for nimTask.

Explanation The system is unable to create a message queue for nimTask.

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/cisco/web/support/index.html . 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 %NIM-0-REGISTRY_GET_FAIL: Unable to pull value from the registry for the key [chars]

Explanation The system is unable to pull a value from the registry.

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/cisco/web/support/index.html . 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 %NIM-3-ADMIN_STATE_INVALID: Admin State [dec] is not valid for interface [dec].

Explanation The admin state is not valid. The state is not enabled or disabled.

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/cisco/web/support/index.html . 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 %NIM-3-CANT_DISABLE_MCAST: Cannot disable multicast state for interface [int] when LAG is enabled

Explanation The system cannot disable multicast state when LAG is 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/cisco/web/support/index.html . 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 %NIM-3-CHECK_SUM_ERR: Checksum Error on config file [chars].

Explanation A checksum error has occurred on the configuration file.

Recommended Action No action is required.

Error Message %NIM-3-COMPONENT_ALREADY_REGISTERED: Component [dec] already registered.

Explanation The component is already registered. A component that is already registered with a state change function is trying to register again.

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/cisco/web/support/index.html . 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 %NIM-3-CREAT_CPUINTF_FAIL: CPU INTF Create error: Ran out of CPU Interface internal numbers.

Explanation NIM Create error: The system has run out of CPU interface internal numbers.

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/cisco/web/support/index.html . 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 %NIM-3-CREAT_LAGINTF_FAIL: LAG interface Create error:Ran out of LAG Interface internal numbers.

Explanation LAG interface Create error: The system has run out of LAG interface internal numbers.

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/cisco/web/support/index.html . 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 %NIM-3-CREAT_LOGICALINTF_FAIL: Logical interface create error:Ran out of Logical Interface internal numbers.

Explanation Logical interface create error: The system has run out of logical interface internal numbers.

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/cisco/web/support/index.html . 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 %NIM-3-CREAT_PHYINTF_FAIL: PHY interface Create error: Ran out of Physical Interface internal numbers.

Explanation PHY interface Create error: The system has run out of physical interface internal numbers.

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/cisco/web/support/index.html . 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 %NIM-3-CREAT_VLANINTF_FAIL: Logical Vlan interface Create error:Ran out of Logical Interface internal numbers.

Explanation Logical VLAN interface Create error: The system has run out of logical interface internal numbers.

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/cisco/web/support/index.html . 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 %NIM-3-FS_WRITE_FAIL: Writing data to the config file [chars] failed.

Explanation Writing data to the user configuration file 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/cisco/web/support/index.html . 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 %NIM-3-INIT_TASK_FAIL: Task initialization failure. Waiting on handle [chars] failed

Explanation Task initializing has failed for a NIM component.

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/cisco/web/support/index.html . 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 %NIM-3-INVALID_CREAT_REQUEST: Invalid [chars] Create Request.

Explanation An invalid interface create request has 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/cisco/web/support/index.html . 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 %NIM-3-LOAD_PORTINFO_FAIL: Loading port info for port number [dec] failed. Ran out of Physical Interface internal numbers.

Explanation Loading the multicast appliance mode port configuration has failed. The system has run out of physical interface internal numbers.

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/cisco/web/support/index.html . 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 %NIM-3-MCAST_STATE_UNKNOWN: interface [int] has invalid mcastApplianceState [dec]

Explanation The multicast appliance state is invalid.

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/cisco/web/support/index.html . 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 %NIM-3-SET_AUTONEG_FAIL: Error in setting the AutoNeg status for the interface with internal interface number [dec].

Explanation An error occurred while setting the status for auto negotiation.

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/cisco/web/support/index.html . 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 %NIM-3-SET_INTFSPEED_FAIL: Error while setting the speed mode for the interface with internal interface number [dec].

Explanation An error occurred while setting the speed mode for the interface. The speed and the interface type are not compatible.

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/cisco/web/support/index.html . 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 %NIM-3-SET_MCASTSTATE_FAIL: Error while setting MCAST appliance state for the interface with internal interface number [dec].

Explanation An error occurred while setting the MCAST appliance 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/cisco/web/support/index.html . 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 %NIM-3-SET_MTUSIZE_FAIL: Error while setting MTU size for the interface with the internal interface number [dec].

Explanation An error occurred while setting the MTU size for the 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/cisco/web/support/index.html . 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 %NIM-3-SYSINTF_TYPE_UNKNOWN: Unknown system interface type [dec].

Explanation The system has detected an unknown system interface type. The system could not find the next valid interface’s internal interface number.

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/cisco/web/support/index.html . 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 %NIM-3-UNKNOWN_INTF_TYPE: Unknown Interface type requested.

Explanation An unknown interface type has been requested.

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/cisco/web/support/index.html . 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 %NIM-3-USP_PORT_ERR: Error in USP and/or port registry data.

Explanation An error has occurred in the USP and/or port registry data.

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/cisco/web/support/index.html . 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 %NIM-3-USP_SLOT_ERR: Error in USP and/or SYSTEM_SLOTS registry data.

Explanation An error has occurred in the USP and/or SYSTEM_SLOTS registry data.

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/cisco/web/support/index.html . 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 %NIM-4-ADDR_TYPE_INVALID: Address type [dec] is not valid for interface [dec].

Explanation The address type is not valid. It is not a burned-in address or a locally administered 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/cisco/web/support/index.html . 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 %NIM-4-LAG_IN_TRANSITION: LAG in transition. switch reboot DUE..!!!

Explanation LAG is in transition. A switch reboot is due.

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/cisco/web/support/index.html . 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 %NIM-4-MCAST_NOT_SET: Multicast appliance flag not set for interface [int]([int],[int],[int]) when LAG enabled.

Explanation The multicast appliance flag does not set when LAG is enabled.

Recommended Action No action is required.

Error Message %NIM-4-NAME_TYPE_INVALID: Name Type [dec] is not valid for interface [dec].

Explanation The interface name type is not valid.

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/cisco/web/support/index.html . 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 %NIM-4-POE_STATE_INVALID: PoE State [dec] is not valid for the interface [dec].

Explanation The PoE state is not valid. The state is not enabled or disabled.

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/cisco/web/support/index.html . 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 %NIM-4-TRAP_STATE_INVALID: Trap State [dec] is not valid for interface [dec].

Explanation The trap state is not valid. It is not enabled or disabled.

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/cisco/web/support/index.html . 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 %NIM-6-LAA_ADDR_INVALID: Locally administered address is not valid for interface [dec].

Explanation The locally administered address is not valid. The LSB of the first byte is not zero.

Recommended Action No action is required.

Error Message %NIM-6-MCAST_STATE_CHANGED: LAG Enabled - changed multicast state of interface [int] to ENABLED

Explanation LAG is enabled. The multicast state has changed to the Enabled state.

Recommended Action No action is required.

Error Message %NIM-6-STACKINTF_NOT_SUPPORTED: Creating Stack Interface currently not supported.

Explanation The system has created a stack interface that is currently not supported.

Recommended Action No action is required.

Error Message %NIM-6-SW_VER_ERR: Software Version Error on config file [chars].

Explanation There is a software version error in the configuration file.

Recommended Action No action is required.

NMSP Messages

This section contains the NMSP messages.

Error Message %NMSP-3-CERT_AAA_ERR: NMSP: LBS cert AAA Error for [chars]

Explanation NMSP: The controller LBS-SSC AuthList has failed to validate a certificate.

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/cisco/web/support/index.html . 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 %NMSP-3-CONN_LIMIT_EXCEEDED: [chars]: Maximum connection limit of [dec] exceeded

Explanation The maximum NMSP connection limit has been exceeded.

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/cisco/web/support/index.html . 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 %NMSP-3-INIT_FAIL: NMSP Task failed to initialize

Explanation The NMSP receive task has failed to initialize and cannot accept incoming NMSP messages.

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/cisco/web/support/index.html . 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 %NMSP-3-INV_CERT_LEN: NMSP: Received invalid peer cert (size [int])

Explanation The system has received a peer certificate that contains no certificate or 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/cisco/web/support/index.html . 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 %NMSP-3-PEER_CERT_VER_FAIL: NMSP: LBS cert verification failed check

Explanation NMSP: The controller has failed to validate the LBS peer certificate.

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/cisco/web/support/index.html . 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 %NMSP-3-QUEUE_CREATE_FAIL: [chars]: Failed to create messaging Q [chars]

Explanation The system has failed to create a messaging 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/cisco/web/support/index.html . 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 %NMSP-3-SOCK_SEL_FAIL_EBADF: [chars]: Select failed with bad file descriptor. All sockets closed

Explanation A select failed with a bad file descriptor. All NMSP sockets have been closed.

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/cisco/web/support/index.html . 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 %NMSP-3-TASK_CREATE_FAIL: [chars]: Failed to create [chars]

Explanation The system has failed to create [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/cisco/web/support/index.html . 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.

NULL Messages

This section contains NULL subsystem (NULL) messages.

Error Message %NULL-0-SOCKET_CREATE_FAILED: Socket creation failed

Explanation The NULL module has failed to create a particular socket. The traceback along with this message will suggest which socket it was.

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/cisco/web/support/index.html . 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.

OSAPI Messages

This section contains operating system API (OSAPI) messages.

Error Message %OSAPI-0-COLLECT_TASK_METRICS_FAILED: Unable to gather task metrics. [chars].

Explanation The system is unable to gather task metrics.

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/cisco/web/support/index.html . 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 OSAPI-0-CONFIG_NOT_SAVED: Configuration Not Saved. System will now restart!

Explanation The configuration has not been saved. The system will now restart.

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/cisco/web/support/index.html . 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 OSAPI-0-CONFIG_SAVED: Configuration Saved. System will now restart.

Explanation The configuration has been saved. The system will now restart.

Recommended Action No action is required.

Error Message OSAPI-0-HI_MEM_THRESHOLD_CROSSED: Warning! System free memory (%d) below high threshold.

Explanation Warning! The system’s free memory has fallen below the high threshold.

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/cisco/web/support/index.html . 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 OSAPI-0-HI_MEM_THRESHOLD_RESTORED: Warning! System free memory (%d) restored above high threshold.

Explanation Warning! The system’s free memory has been restored above a high threshold.

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/cisco/web/support/index.html . 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 OSAPI-0-INTF_SYSCTL_FAILED: The sysctl %s has failed on interface %s. error code: %d.

Explanation The sysctl operation has failed on the 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/cisco/web/support/index.html . 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 %OSAPI-0-INVALID_TIMER_HANDLE: Task is using invalid timer handle [int]/[int]

Explanation The task is using an invalid timer handle.

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/cisco/web/support/index.html . 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 %OSAPI-0-INVALID_TIMERCB: Invalid timer control block. TcbPtr=[hex].

Explanation The system has detected an invalid timer control block, and a software timer object 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/cisco/web/support/index.html . 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 OSAPI-0-LICENSE_FL_UPDATE_FAIL: Failed to update Cisco License Directory on flash.

Explanation The system has failed to update the Cisco license directory on flash.

Recommended Action No action is required.

Error Message %OSAPI-0-MEM_ALLOC_FAILED: Failed to allocate memory for [dec] bytes.

Explanation The system has failed to allocate some memory. The system might be out of buffers. This may be temporary problem.

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/cisco/web/support/index.html . 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 %OSAPI-0-MSGQ_CREATE_FAILED: Failed to create the message queue object: [chars]. [chars].

Explanation The system has failed to create a message queue object.

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/cisco/web/support/index.html . 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 OSAPI-0-MTD_ERASE_FAIL: Unable to erase a sector at %d on MTD device %s.

Explanation The system is unable to erase a sector on the Memory Technology Device (MTD).

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/cisco/web/support/index.html . 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 OSAPI-0-MTD_INFO_FAIL: Unable to get MTD device info on %s.

Explanation The system is unable to get the Memory Technology Device (MTD) information.

Error Message OSAPI-0-MTD_LOCK_FAIL: Unable to lock MTD device %s.

Explanation The system is unable to lock the Memory Technology Device (MTD).

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/cisco/web/support/index.html . 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 OSAPI-0-MTD_OPEN_FAIL: Unable to open MTD device %s.

Explanation The system is unable to open the Memory Technology Device (MTD).

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/cisco/web/support/index.html . 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 OSAPI-0-MTD_UNLOCK_FAIL: Unable to unlock MTD device %s.

Explanation The system is unable to unlock the Memory Technology Device (MTD).

Error Message %OSAPI-0-MUTEX_CREATE_FAILED: Failed to create a mutual exclusion object. [chars].

Explanation The system has failed to create a mutual exclusion object.

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/cisco/web/support/index.html . 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 %OSAPI-0-RAD_SW_UPGRADE: System has been upgrading Radio SW for more than 30 minutes.

Explanation The APs have been downloading software for the last 30 minutes. Either the network is congested or there is a mismatch between the AP image and the controller image.

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/cisco/web/support/index.html . 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 %OSAPI-0-REAPER_START_FAILED: Unable to start the Osapi Reaper. [chars].

Explanation The system is unable to start an OSAPI Reaper.

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/cisco/web/support/index.html . 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 %OSAPI-0-REAPWATCHER_START_FAILED: Unable to start the Osapi Reaper Watcher. [chars].

Explanation The system is unable to start an OSAPI Reaper Watcher.

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/cisco/web/support/index.html . 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 OSAPI-0-RESETSYSTEM_FAILED: System will not reset as %ssoftware is being upgraded.

Explanation Resetting the system when an image download on the controller or an image downloading to the access point could leave the controller or access points with partial images. This problem could affect the state/functioning of the device after a power cycle. The reset of the system is cancelled when a controller or access point is downloading an image.

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/cisco/web/support/index.html . 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 %OSAPI-0-RESET_START_FAILED: Unable to start the System Reset. [chars].

Explanation The system is unable to start the system reset 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/cisco/web/support/index.html . 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 OSAPI-0-RESET_TRAP_GENERATED: System reset trap message generated.

Explanation A system reset trap message has been generated.

Recommended Action No action is required.

Error Message OSAPI-0-SAVE_CONFIG_FAILED: Flash write in progress. Cannot save config or reset system.

Explanation A Flash write is in progress. The system cannot save the configuration or reset the 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/cisco/web/support/index.html . 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 OSAPI-0-SET_ETHERNET_PORT_FAILED: Setting Ethernet Port %s MAC. Could not get current flags.

Explanation The Linux (Input Output ConTroL) IOCTL operation has failed on the Ethernet 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/cisco/web/support/index.html . 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 OSAPI-0-SET_ETHERNET_PORT_FAILED_1: Setting Ethernet Port %s MAC. Could not bring down port.

Explanation The Linux (Input Output ConTroL) IOCTL operation has failed on the Ethernet 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/cisco/web/support/index.html . 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 OSAPI-0-SET_ETHERNET_PORT_FAILED_2: Error while setting Ethernet Port %s MAC..Error No: %d.

Explanation The Linux (Input Output ConTroL) IOCTL operation has failed on the Ethernet 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/cisco/web/support/index.html . 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 OSAPI-0-SET_ETHERNET_PORT_FAILED_3: Error while setting Ethernet Port %s flags..Error No: %d.

Explanation The Linux (Input Output ConTroL) IOCTL operation has failed on the Ethernet 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/cisco/web/support/index.html . 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 %OSAPI-0-TASK_CREATE_FAILED: Failed to create the task object: [chars]. [chars].

Explanation The system has failed to create a task object.

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/cisco/web/support/index.html . 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 %OSAPI-0-TASK_HUNG: Error! Hung task detected ([chars])! (user [dec]% system [dec]%)Reset!.

Explanation The system has detected a hung 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/cisco/web/support/index.html . 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 %OSAPI-0-TASK_INVALID_ADDRESS: Invalid task [address] ([address] < msg < [address]) (1)

Explanation The system has detected a possibly corrupted 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/cisco/web/support/index.html . 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 %OSAPI-2-TASK_PRIORITY_INFO: %s - TaskID %d ('%s') osapi_prio %u old_prio %u pthread_prio %d cur_prio %d tickleTimer %u\n

Explanation The sytem has changed the thread priority.

Recommended Action No action is required.

Error Message %OSAPI-0-TASKLIST_CORRUPTED: Task list corruption detected!!!.

Explanation The system has detected a corrupted task 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/cisco/web/support/index.html . 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 %OSAPI-0-TIMERCB_ALLOC_FAILED: Unable to allocate timer control block.

Explanation The system is unable to allocate memory for a software timer control block.

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/cisco/web/support/index.html . 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 %OSAPI-0-TIMERCB_FREELIST_CORRUPTED: Timer control block free list is corrupted. Head=[hex],Count=[dec],Mempool Size=[dec].

Explanation The timer control block free list is corrupted.

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/cisco/web/support/index.html . 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 %OSAPI-0-TIMER_CREATE_FAILED: Failed to create a timer.

Explanation The system could not create a software timer object.

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/cisco/web/support/index.html . 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 OSAPI-0-TRAP_START_FAILED: Unable to start the System Trap Reset. %s.

Explanation The system is unable to start the System Trap Reset 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/cisco/web/support/index.html . 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 %OSAPI-1-MUTEX_PRIO_CLEAR: == Unlock assert == ([chars]) prio=[dec] root=[hex] word[[dec]]=[hex].

Explanation A mutex clear lock failure has 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/cisco/web/support/index.html . 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 %OSAPI-1-MUTEX_PRIO_SET: ** Lock assert ** ([chars]) prio=[dec] root=[hex] [chars]

Explanation A mutex lock priority violation has 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/cisco/web/support/index.html . 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 %OSAPI-1-MUTEX_PRIO_SET2: ** Lock assert ** ([chars]) prio=[dec] root=[hex] word[[dec]]=[hex].

Explanation A mutex lock priority violation 2 has 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/cisco/web/support/index.html . 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 OSAPI-3-CLOSE_FAILED: Failed to close file

Explanation The system is unable to close 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/cisco/web/support/index.html . 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 %OSAPI-3-FILE_CREATE_FAILED: Failed to create the file : [chars]. [chars].

Explanation The system could not create a file or directory. There may be several reasons behind it, including that the system has run out of disk space.

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/cisco/web/support/index.html . 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 %OSAPI-3-FILE_OPEN_FAILED: Failed to open the file : [chars].

Explanation The system could not open a file or directory. There may be several reasons behind it, including that the path provided does not exist.

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/cisco/web/support/index.html . 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 %OSAPI-3-FILE_TRANSFER_ABORTED: Aborting file transfer. [chars].

Explanation The system is aborting a file transfer.

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 %OSAPI-3-FILE_WRITE_FAILED: Failed to write [dec] bytes to the file : [chars] (FileDesc:[dec]). [chars].

Explanation The system could not write to a file or directory. There may be several reasons behind it, including that the path provided does not exist.

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/cisco/web/support/index.html . 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 %OSAPI-3-FILE_WRITENOCLOSE_FAILED: Failed to write [dec] bytes (FileDesc:[dec]). [chars].

Explanation The system could not write to a file or directory. There may be several reasons behind it, including that the path provided does not exist.

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/cisco/web/support/index.html . 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 %OSAPI-3-INTF_IOCTL_FAILED: The I/O control operation ([chars]) has failed on the interface [chars].IpAddr:[int].[int].[int].[int] Errorcode:[dec]

Explanation The I/O control operation has failed on the 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/cisco/web/support/index.html . 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 %OSAPI-3-INVALID_FILE_HANDLE: The File/Socket handle is Invalid. Handle = [dec].

Explanation The file/socket handle is invalid.

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/cisco/web/support/index.html . 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 %OSAPI-3-INVALID_PING_RESPONSE: Ping response from [int].[int].[int].[int] is invalid. [chars].

Explanation The ping response is invalid.

Recommended Action This is a debug message only. No action is required.

Error Message OSAPI-3-IOCTL_FAILED: ioctl ([chars]) failed for interface [chars].

Explanation The system was unable to complete the specified IOCTL operation.

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/cisco/web/support/index.html . 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 %OSAPI-3-KTHREAD_STRUCT_ALLOC_FAILED: We failed to create a struct for /proc/[chars]/status

Explanation The system failed to create a structure for storing kthread information.

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/cisco/web/support/index.html . 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 %OSAPI-3-KTHREAD_TABLE_FULL: Need a bigger osapi_kthread_tbl to store kthread [chars] pid=[dec].

Explanation The system needs a bigger osapi_kthread_tbl to store a kthread.

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/cisco/web/support/index.html . 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 %OSAPI-3-LINK_ERROR: Error condition detected on link [chars] (rxp [int] rxe [int]; previously rxp [int] rxe [int]

Explanation A link error has been detected on the specified link.

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/cisco/web/support/index.html . 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 %OSAPI-3-OPEN_FAILED: Failed to open file [chars]

Explanation The system is unable to open a file with the given name.

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/cisco/web/support/index.html . 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 %OSAPI-3-PATH_BUILD_FAILED: Failed to build the path string for [chars]

Explanation The system has failed to build a path string.

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/cisco/web/support/index.html . 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 %OSAPI-3-PING_OPER_FAILED: Unable to start ICMP ping to host [chars]. [chars]

Explanation The system is unable to start an ICMP ping to host.

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/cisco/web/support/index.html . 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 %OSAPI-3-ROUTE_INFO_GET_FAILED: Unable to retrieve routing information

Explanation The system is unable to retrieve routing information, and unable to access /proc/net/route.

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/cisco/web/support/index.html . 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 %OSAPI-3-SOCKET_FAILED: Failed to open socket.

Explanation The system is unable to open a socket.

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/cisco/web/support/index.html . 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 %OSAPI-3-SOCK_OPER_FAILED: The [chars] operation has failed on the socket descriptor [dec]. Errorcode:[dec]

Explanation An operation has failed on a socket descriptor.

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/cisco/web/support/index.html . 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 %OSAPI-3-SYSINFO_FAILED: The system API sysinfo() returned failure. Error: [chars].

Explanation The system API 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/cisco/web/support/index.html . 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 %OSAPI-3-TASK_ADD_LOCKED: Exceeded maximum task count [int] (max [int])

Explanation The maximum number of tasks that can be created has been exceeded.

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/cisco/web/support/index.html . 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 %OSAPI-3-TASK_GETTIME_FAILED: Failed to retrieve statistics (/proc/<pid>/stats) for task ’[chars]’

Explanation The system has failed to retrieve statistics (/proc/<pid>/stats) for 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/cisco/web/support/index.html . 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 %OSAPI-3-TASK_RMV_LOCKED: Failed to delete a task osapiTaskFreeList.head [address], count [int]

Explanation The system has failed to delete 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/cisco/web/support/index.html . 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 %OSAPI-3-TASK_SET_TICKLE: Task [chars] requesting [dec] second timer. Minimum is 20. Setting to 20.

Explanation The requested timer is less than the minimum time allowed. The minimum time is 20. The system is setting the timer to 20.

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/cisco/web/support/index.html . 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 %OSAPI-4-CPU_OVERLOAD: Warning! Task [dec] ([chars]) is taking [dec]% ([dec]% user [dec]%system)of the cpu!.

Explanation Warning! A task is overloading the CPU.

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/cisco/web/support/index.html . 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 %OSAPI-4-FILE_MOVE_FAILED: Failed to move the file [chars] to [chars].

Explanation The system could not move or rename a file or directory. There may be several reasons behind it, including that the source path provided does not exist.

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/cisco/web/support/index.html . 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 %OSAPI-4-GW_ADD_FAILED: Unable to add the gateway [chars]. System command returned failure. Error code:[dec]

Explanation The system is unable to add a gateway. The system command 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/cisco/web/support/index.html . 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 %OSAPI-4-MSGQ_DUMP_FAILED: Failed to dump the message queue history: [chars]. [chars].

Explanation The system has failed to dump the message queue history in the event of a crash.

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/cisco/web/support/index.html . 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 %OSAPI-4-MSGQ_RECV_FAILED: Failed to receive a message from the message queue object: [chars]. [chars].

Explanation The system has failed to receive a message from a message queue object.

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/cisco/web/support/index.html . 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 %OSAPI-4-MSGQ_SEND_FAILED: Failed to send a message to the message queue object: [chars]. [chars].

Explanation The system has failed to send a message to a message queue object.

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/cisco/web/support/index.html . 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 %OSAPI-4-MUTEX_LOCK_FAILED: Failed to acquire a mutual exclusion object. [chars].

Explanation The system has failed to acquire a mutual exclusion object.

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/cisco/web/support/index.html . 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 %OSAPI-4-ROUTE_ADD_FAILED: Unable to add the route (Dest:[chars], NetMask:[chars], NextHop:[chars]). System command returned failure. Errorcode:[dec]

Explanation The system is unable to add a route. The system command 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/cisco/web/support/index.html . 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 %OSAPI-4-ROUTE_DEL_FAILED: Unable to delete the route (Dest:[chars], NetMask:[chars], NextHop:[chars]). System command returned failure. Errorcode:[dec]

Explanation The system is unable to delete a route. The system command 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/cisco/web/support/index.html . 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 %OSAPI-4-TIMERTCB_NOT_ALLOCATED: Timer [int]/[int] (’[chars]’) already destroyed.

Explanation A software timer object is already destroyed and cannot be used.

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/cisco/web/support/index.html . 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 %OSAPI-4-TIMERTCB_REALLOCATED: Timer [int]/[int] (’[chars]’) found to be destroyed/reallocated.

Explanation The timer is destroyed/reallocated.

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/cisco/web/support/index.html . 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 %OSAPI-4-TIME_SHIFT_DETECTED: Detected [chars] time shift. Last: [dec].[dec]. --> Now:[dec].[dec].

Explanation The system has detected a time shift.

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/cisco/web/support/index.html . 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 %OSAPI-5-CLEAN_TASK: Reaper cleaning up exited task ’[chars]’ ([address])

Explanation The reaper is cleaning up the exited task.

Recommended Action No action is required.

Error Message %OSAPI-5-FILE_CLOSE_FAILED: Failed to close the file descriptor: [dec].

Explanation The system could not close a file or directory. There may be several reasons behind it, including that the path provided does not exist.

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/cisco/web/support/index.html . 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 %OSAPI-5-FILE_DEL_FAILED: Failed to delete the file : [chars]. [chars].

Explanation The system could not delete a file or directory. There may be several reasons behind it, including that the path provided does not exist.

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/cisco/web/support/index.html . 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 %OSAPI-5-FILE_READ_FAILED: Failed to read [dec] bytes from the file : [chars] (FileDesc:[dec]). [chars].

Explanation The system could not read from a file or directory. There may be several reasons behind it, including that the path provided does not exist.

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/cisco/web/support/index.html . 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 %OSAPI-5-FILE_READNOCLOSE_FAILED: Failed to read [dec] bytes (FileDesc:[dec]). [chars].

Explanation The system could not read from a file or directory. There may be several reasons behind it, including that the path provided does not exist.

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/cisco/web/support/index.html . 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 %OSAPI-5-MSGQ_DEL_FAILED: Failed to delete the message queue object: [chars]. [chars].

Explanation The system has failed to delete a message queue object.

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/cisco/web/support/index.html . 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 %OSAPI-5-MUTEX_DEL_FAILED: Failed to delete a mutual exclusion object. [chars].

Explanation The system has failed to delete a mutual exclusion object.

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/cisco/web/support/index.html . 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 %OSAPI-5-MUTEX_UNLOCK_FAILED: Failed to release a mutual exclusion object. [chars].

Explanation The system has failed to release a mutual exclusion object.

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/cisco/web/support/index.html . 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 %OSAPI-6-FILE_DOES_NOT_EXIST: File : [chars] does not exist.

Explanation The system could not find the file or directory. There may be several reasons behind it, including that certain functionality has never been configured on the 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/cisco/web/support/index.html . 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.

Recommended Action