HMAN through HW_FLOWDB
HMAN
%HMAN-3-CONSOLE_SETUP_FAILED : Failed to setup console service. It should be enabled on [chars] | |
---|---|
Explanation | Setup of a console service failed. |
Recommended Action | Check the host manager launch parameters and correct as required. |
%HMAN-3-HOSTNAME_SET_FAILED : Failed to set hostname: [chars] | |
---|---|
Explanation | The host manager received notification that the system hostname has been set. The host manager failed to pass this value to the ASR kernel. |
Recommended Action | Repeat the process to configure the hostname. If the problem persists, copy the message exactly as it appears on the 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 https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center via the Internet athttps://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information. |
%HMAN-2-INITIALIZATION_FAILED : Host Manager initialization failed. | |
---|---|
Explanation | Initialization of the host manager failed. |
Recommended Action | Review Host Manager logs taking note of the timestamp information to select specific information to review. Copy the message and other related information exactly as it appears on the 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 https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center via the Internet athttps://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information. |
HMAN_CPU
%HMAN_CPU-3-PAGE_FAULT_HIGH : CPU Usage due to Memory Pressure exceeds threshold on [chars]. Below are the top 5 memory consuming processes: [chars] (PID=[dec] RSS=[dec] MB), | |
---|---|
Explanation | When CPU usage due to Major Page Fault exceeds a pre-defined threshold for a CPU core, this error message is emitted. |
Recommended Action | No action is needed if system continues to perform as expected. If sytem performance deteriorate (and eventually, system reloads due to unspecified reason) around the time when this message is observed, open a case with the Technical Assistance Center via the following Internet link, or contact your Cisco technical support representative:https://mycase.cloudapps.cisco.com/case |
HPI
%HPI-3-FAILED_START : channel:[chars] DSP ID:[hex], failed mode [dec] for service [dec] | |
---|---|
Explanation | Failed to start DSP services |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%HPI-3-INVALID_PAYLOAD : wrong payload size, channel:[chars] DSP ID:[hex], failed mode [dec] for service [dec] | |
---|---|
Explanation | Failed to start DSP services |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%HPI-3-CODEC_NOT_LOADED : channel:[chars] DSP ID:[hex], command failed as codec not loaded [dec] | |
---|---|
Explanation | Sending messages to DSP without a loaded codec can result with the DSP failing |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%HPI-4-INVALID_CODEC_LOAD : channel:[chars] DSP ID:[hex], invalid hpi mode [dec] for loading codec [dec] | |
---|---|
Explanation | Attempt to load codec when the DSP is in an invalid mode which can result with DSP failure |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%HPI-4-NO_CLOSE : channel:[chars] DSP ID:[hex] | |
---|---|
Explanation | Attempt to release DSP without sending close message |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%HPI-4-INVALID_ECAN_TYPE : [chars] ECAN is not available in voice-card [dec], [chars] ECAN will be used | |
---|---|
Explanation | All voice cards participated in DSPFarm must have the same echo canceller type |
Recommended Action | Make sure all voice cards participated in DSPFarm have the same echo canceller type configured |
%HPI-3-GSMAMRNB_LICENSE_NOT_ACTIVATED : ********************************************************* GSM AMR-NB License is not yet activated. Please configure 'license feature gsmamrnb-codec-pack' and accept the EULA to activate the license. ********************************************************* | |
---|---|
Explanation | Failed to start DSP services for GSM AMR-NB codec |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%HPI-6-SRTP_EVAL_LIMIT : The SRTP bandwidth and tunnels usage exceed the license limits | |
---|---|
Explanation | The SRTP bandwidth and tunnels exceed the license limits |
Recommended Action | No action is required. |
%HPI-3-SRTP_EVAL_FREE_ERROR : Error encountered on release SRTP bandwidth and tunnels reservation | |
---|---|
Explanation | Error encountered on release SRTP bandwidth and tunnels |
Recommended Action | No action is required. |
%HPI-3-NACK_HIGH : DSP to IOS Nack message with severity [chars] [chars] [chars] | |
---|---|
Explanation | DSP to IOS Nack message with high severity |
Recommended Action | Check the NACKed message's parameters for configuration errors. These messages tend to affect call flow, thus they are labeled with high severity. |
%HPI-4-NACK_MED : DSP to IOS Nack message with severity [chars] [chars] [chars] | |
---|---|
Explanation | DSP to IOS Nack message with medium severity |
Recommended Action | Check the NACKed message's parameters for minor configuration errors. |
%HPI-6-NACK_LOW : DSP to IOS Nack message with severity [chars] [chars] [chars] | |
---|---|
Explanation | DSP to IOS Nack message with low severity |
Recommended Action | Information only, displaying NACKed messages that are for debugging purposes. |
%HPI-6-NACK : DSP to IOS Nack message [chars] [chars] | |
---|---|
Explanation | DSP to IOS Nack message with no severity in order to work with dspware without Nack severity implementation |
Recommended Action | Information only, displaying NACKed messages. |
HSRP
%HSRP-3-NOSOCKET : Unable to open socket | |
---|---|
Explanation | The system was unable to initialize an IP connection for the Hot Standby protocol. |
Recommended Action | Make sure that there is at least one interface configured to run IP. |
%HSRP-4-BADAUTH : Bad authentication from [chars], group [dec], remote state [chars] | |
---|---|
Explanation | Two routers participating in HSRP disagree on the valid authentication string. |
Recommended Action | Use the standby authentication command to repair the HSRP authentication discrepancy between the local system and the one whose IP address is reported. |
%HSRP-4-BADAUTH2 : Bad authentication from [chars] | |
---|---|
Explanation | Two routers participating in HSRP disagree on the valid authentication string. |
Recommended Action | Use the standby authentication command to repair the HSRP authentication discrepancy between the local system and the one whose IP address is reported. |
%HSRP-3-MISCONFIG : Attempt to change [chars] MAC address to [enet] when DECNET already running | |
---|---|
Explanation | An HSRP group attempted to become active on an interface that can only support a single MAC address and which is running DECnet. If standby use-bia is not configured then HSRP would normally set the interface MAC address to the HSRP virtual MAC address, but this is not allowed if DECnet is running. |
Recommended Action | Enable standby use-bia on the interface. |
%HSRP-5-STATECHANGE : [chars] Grp [dec] state [chars] -> [chars] | |
---|---|
Explanation | The router has changed state |
Recommended Action | No action is required. |
%HSRP-4-DUPADDR : Duplicate address [chars] on [chars], sourced by [enet] | |
---|---|
Explanation | The IP address in an HSRP message received on the specified interface is the same as the IP address of the router. Another router might be configured with the same IP address. The most likely cause is a network loop or a misconfigured switch that is causing the router to see its own HSRP Hello messages. |
Recommended Action | Check the configurations on all the HSRP routers to ensure that the interface IP addresses are unique. Check that no network loops exist. If port channels are configured check that the switch is correctly configured for port-channels. Enable standby use-bia so that the error message displays the interface MAC address of the sending router. This can be used to determine if the error message is caused by a misconfigured router or a network loop. |
%HSRP-4-DUPVIP1 : [chars] Grp [dec] address [chars] is already assigned to [chars] group [dec] | |
---|---|
Explanation | The HSRP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to a different HSRP group. |
Recommended Action | Check the configuration on all HSRP routers and ensure that the virtual IP address of each HSRP group is unique. |
%HSRP-4-DUPVIP2 : [chars] Grp [dec] address [chars] is already assigned on this interface | |
---|---|
Explanation | The HSRP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to this interface. |
Recommended Action | Check the configuration on all HSRP routers and ensure that the virtual IP address of each HSRP group is unique. |
%HSRP-4-DUPVIP3 : [chars] Grp [dec] address [chars] is already assigned to, or overlaps with, an address on another interface or application | |
---|---|
Explanation | The HSRP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to, or overlaps with, an address on another interface or application. |
Recommended Action | Check the configuration on all HSRP routers and ensure that the virtual IP address of each HSRP group is unique. |
%HSRP-4-BADVIP : [chars] Grp [dec] address [chars] is in the wrong subnet for this interface | |
---|---|
Explanation | The HSRP virtual IP address contained in the Hello message cannot be learnt as it is not within a subnet configured on the interface. |
Recommended Action | Check the configuration on all HSRP routers and ensure that the virtual IP address is within a configured subnet. |
%HSRP-4-DIFFVIP1 : [chars] Grp [dec] active routers virtual IP address [chars] is different to the locally configured address [chars] | |
---|---|
Explanation | The HSRP virtual IP address contained in the Hello message from the Active router is different from the virtual IP address configured locally. |
Recommended Action | Check the configuration on all HSRP routers in the group and ensure they are all configured with the same virtual IP address. |
HTSP
%HTSP-3-NOEVENT : no free event structure available from [chars] for DSP message | |
---|---|
Explanation | There were no event structures remaining in the system pools to alert the router of a voice or signaling event. |
Recommended Action | Check that the voice port for which the event was reported is still operational. If not, clear the voice port. |
%HTSP-3-CAPABILITYMISMATCH : voice port [chars]: call connection id [[hex] [hex] [hex] [hex]] | |
---|---|
Explanation | There was a capabilities mismatch between the two call legs. capabilities are negotiated between call legs for CODEC, VAD and FAX rate. |
Recommended Action | Check that the dial peer configuration is appropriate for the interface in question. Also check that and configuration on the interface is correct. |
%HTSP-3-DSPALARM : voice port [chars]: status=[hex] message=[hex] text=[chars] | |
---|---|
Explanation | The DSP reported a fatal error. All calls on the DSP were dropped and a DSP reload was attempted. |
Recommended Action | Verify that the DSP reloaded properly by attempting to place a call on the affected voice port. Contact your technical support representative, include the full text of the error message. |
%HTSP-3-TRUNKNOTSUPPORTED : voice port [chars]: Ground Start trunking not supported | |
---|---|
Explanation | This voice port does not support the 'connection trunk' command when ground start signaling is configured. Trunking mode on this voice is supported when using loop start signaling. |
Recommended Action | Shut down the voice port, remove the 'connection trunk' and/or 'signal groundStart' command from the voice port configuration, and unshut the voice port. |
%HTSP-5-UPDOWN : Trunk port(channel) [[chars]] is [chars] | |
---|---|
Explanation | Trunk port:channel changed state. |
Recommended Action | No action is required. |
%HTSP-3-CADENCENOTSUPPORTED : voice port [chars]: ring cadence not suitable for caller id. on_time_first=[dec] off_time_first=[dec] on_time_second=[dec] off_time_second=[dec] | |
---|---|
Explanation | Ring off period is not sufficient for caller id transmission. If caller id transmission during ring is configured make sure that the ring off duration is long enough. |
Recommended Action | If caller id transmission during ring is configured make sure that the ring off duration is long enough. Make sure that the cptone setting and caller-id alerting settings are correct. |
%HTSP-5-VPM_BUSYOUT : voice port [chars]: [chars] busyout | |
---|---|
Explanation | voice port busyout status changed |
Recommended Action | use SHOW VOICE BUSYOUT to find out the reason why voice port busyout monitoring is triggered |
%HTSP-5-VPM_PCM_CAPTURE : User trigger PCM capture is [chars] on voice port [chars] | |
---|---|
Explanation | User trigger PCM capture is enabled or disable on this voice port |
Recommended Action | This is just for information only |
%HTSP-5-VPM_CABLE_STAT : voice port [chars]: cable [chars] | |
---|---|
Explanation | Cable for analog voice port is reconnected or removed |
Recommended Action | Check the cable connection for this analog voice port |
HTTP
%HTTP-3-PROC_NOCREAT : Unable to create HTTP process. | |
---|---|
Explanation | An error occurred during initialization of the HTTP process. The HTTP process that processes all HTTP requests and responses could not be created. |
Recommended Action | Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. |
%HTTP-4-SERVER_CONN_RATE_EXCEED : Number of connections per minute has exceeded the maximum limit([dec]) as specified by the platform. | |
---|---|
Explanation | The message indicates that the current number of connections requested per minute has exceeded the limit specified by the platform. HTTP server will resume accepting the connections 15 seconds from the time the message is issued. This restriction is done as per the HTTP throttling functionality. |
Recommended Action | Reduce connection rate to the server. |
%HTTP-3-OUTOF_MEM : HTTP out of memory. | |
---|---|
Explanation | An error occurred during initialization of the HTTP process. The HTTP process could not create crucial internal data structures that are required for operation of the HTTP subsystem. The most likely reason for this condition is an exhaustion of system memory. |
Recommended Action | Reduce other system activity to ease memory demands. if conditions warrant, upgrade to a larger memory configuration. |
%HTTP-3-INIT_FAIL : HTTP Process Init failed. | |
---|---|
Explanation | Initialization of the HTTP Subsystem has failed |
Recommended Action | Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. |
%HTTP-6-SERVER_SETUP_FAILED : Server setup failed | |
---|---|
Explanation | Setup of the HTTP(S) server to listen on the specified port number has failed. |
Recommended Action | Disable the server, verify that port number is correct and enable the server. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. |
HTTPC
%HTTPC-3-PROC_NOCREAT : Unable to create HTTP Client process. | |
---|---|
Explanation | |
Recommended Action |
%HTTPC-3-OUTOF_MEM : HTTP Client out of memory. | |
---|---|
Explanation | |
Recommended Action |
%HTTPC-3-CACHE_MEM : HTTP Client Cache Init out of memory. | |
---|---|
Explanation | |
Recommended Action |
%HTTPC-3-INIT_FAIL : HTTP Client Process Init failed. | |
---|---|
Explanation | |
Recommended Action |
%HTTPC-3-OUTOF_SYNC : HTTP Client header tables out of sync. | |
---|---|
Explanation | |
Recommended Action |
%HTTPC-6-CONNECT_FAILED : The connection to server [IP_address] failed | |
---|---|
Explanation | |
Recommended Action |
%HTTPC-3-RECEIVE_SOCK_READ_EVENT_WHILE_DISABLED : Received socket read event while read interest is disabled callID([dec]) fd([dec]) - closing socket. | |
---|---|
Explanation | The HTTP Client is receiving the socket READ event while the READ interest is being disabled. Something has gone wrong between the http client and the socket interfaced. |
Recommended Action | Record the error and report it to the system administrator. |
%HTTPC-3-CONNECT_NULL : NULL connection structure for fd([dec]) - closing socket. | |
---|---|
Explanation | The HTTP Client is receiving the socket READ event but it fails to locate the connection structure for this file descriptor(fd). If this is seen continuously in a loop, it is an indication that something has gone wrong in the socket code. Since the socket is immediately closed after this event, the HTTP client should stop seeing READ event. |
Recommended Action | Record the error and traceback and report it to the system administrator. |
%HTTPC-6-REQUEST_FAILED : request URI [chars] failed | |
---|---|
Explanation | |
Recommended Action |
%HTTPC-6-CLOSE_SRV_CONNECT : The connection to server [IP_address] appears to be hung and will be closed. | |
---|---|
Explanation | Messages are being backed up in the HTTP Client's write queue in the connection with the specified server. The connection is assumed to have gone bad and the HTTP Client is closing the connection. |
Recommended Action | Check with the specified server for possible connection error. |
%HTTPC-3-COOKIE_MEM : HTTP Client runs out of allowable memory to store cookies. | |
---|---|
Explanation | The total memory allocated for storing cookies has run out. All cookies received from the HTTP server will be dropped. Users may no longer be able to interact with a session-based origin server until memory is freed up. |
Recommended Action | Users may want to try their requests at a later time or contact the system administrator to increase the maximum RAM allowed for saving HTTP cookies. |
HUNTGRP
%HUNTGRP-3-INVALID_URL : Could not open the file provided in URL: <[chars]> | |
---|---|
Explanation | URL path provided can't be accessed. This usually indicates that path provided is invalid but may also be because the the path doesn't allow anonymous access to create files or open it in write mode |
Recommended Action | Check that the url path provided is valid |
%HUNTGRP-3-WRITE_FAIL : Could not write data to the URL: <[chars]>t %%bytes written=[dec] out of [dec] | |
---|---|
Explanation | Write attempt to the url path provided was unsuccessful. This usually indicates that the file was successfully opened with write and append permissions but writing all the content from buffer or may be some of it to the file failed. |
Recommended Action |
HW_API
%HW_API-3-RESILIENCE_NO_HANDLER : No handlers in place for [chars] sw object creation failure. | |
---|---|
Explanation | COMMON_HW_API_INTERNAL_ERROR |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%HW_API-3-INVALID_OBJ : Invalid object [hex] | |
---|---|
Explanation | HW_API_INTERNAL_ERROR |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%HW_API-3-INVALID_TYPE : Invalid type [dec] | |
---|---|
Explanation | HW_API_INTERNAL_ERROR |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%HW_API-3-INVALID_WALK_SPEC : Invalid walk spec [hex] | |
---|---|
Explanation | HW_API_INTERNAL_ERROR |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%HW_API-3-WALK_MODE_UNSUPPORTED : Walk mode '[chars]' unsupported | |
---|---|
Explanation | HW_API_INTERNAL_ERROR |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%HW_API-3-INVALID_CONTEXT : Invalid context [hex] | |
---|---|
Explanation | HW_API_INTERNAL_ERROR |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%HW_API-3-BACKWALK_REQUEST : Backwalk request failed, [chars] | |
---|---|
Explanation | A request to walk internal data structures has failed. Depending on criticality of the data, accuracy of forwarding may impacted. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%HW_API-3-BACKWALK_REQUEST_VALUE : Backwalk request failed, [chars] ([hex]) | |
---|---|
Explanation | A request to walk internal data structures has failed. Depending on criticality of the data, accuracy of forwarding may impacted. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%HW_API-3-VECTOR : Failed to set [chars] vector for [chars], [chars] | |
---|---|
Explanation | HW_API_INTERNAL_ERROR |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%HW_API-3-NO_OBJ_TYPE_LIST_ENTRY : Invalid sw_obj_type ([dec]) used with obj_type_list | |
---|---|
Explanation | HW_API_INTERNAL_ERROR |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%HW_API-3-NO_OBJ_TYPE_LIST_ENTRY2 : Invalid sw_obj_link_type ([dec]) used with obj_type_list | |
---|---|
Explanation | HW_API_INTERNAL_ERROR |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%HW_API-3-INIT_FAIL : HW-API init [chars] failed[chars] | |
---|---|
Explanation | HW_API_INTERNAL_ERROR |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
HW_FLOWDB
%HW_FLOWDB-3-HW_FLOWDB_OOM : FlowDB memory usage exceeded 95[int]sage. OOM condition can occur. | |
---|---|
Explanation | FlowDB running low on memory. Out-of-memory condition can occur |
Recommended Action | Check sw-distrib for actual utilization of FlowDB memory |