-
Cisco IOS XR System Error Reference Guide for XR12000 Series Platform Specific Messages, Release 3.4
-
Preface
-
Overview
-
Access Control List (ACL) Messages
-
Diagnostic Messages
-
Forwarding Messages
-
High Availability (HA) Messages
-
Installation Messages
-
Internet Protocol (IP) Messages
-
Layer 1 Messages
-
Layer 2 Messages
-
Manageability (MGBL) Messages
-
Operating System (OS) Messages
-
Packet Infrastructure Messages
-
Platform Messages
-
Quality of Service (QoS) Messages
-
Routing Messages
-
Index
-
Feedback
Table Of Contents
Operating System (OS) Messages
Operating System (OS) Messages
This section contains all Operating System(OS) and OS infrastructure related System Error Messages. The following facility codes are represented in this module:
OBFLMGR Messages
Error Message%OS-OBFLMGR-7-NO_MEMORY Failed to allocate memory with size:[dec] at
Explanation Not enough memory available in the system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-NODEID_FAILURE [chars] of nodeid for [chars] failed. Error([dec]): [chars]
Explanation An error happened for a nodeid operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-QUEUE_LIMIT_OVER The queue:[pointer] for device:[chars] entry_num:[dec] and the max limit:[dec]. The new request for [chars] will be discarded.
Explanation The destination queue is full. New enqueue request will be discarded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-RACK_DECODE_FAILURE decoding of rack:[hex] for [chars] failed. Error([dec]): [chars]
Explanation An error happened for a rackid decoding.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-RECORD_TOO_LONG Too long record size:[dec] for [chars] record. The file contents might be corrupted.
Explanation A feature record is too long.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-RECORD_TYPE_UNKNOWN Unknown record type:[dec] for [chars] record. The file contents might be corrupted.
Explanation A feature record has an unknown record type.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-REDUNDANCY_STANDBY logging to node:[hex] is denied because this node:[hex] is redundancy standby state.
Explanation Node is redundancy standby state, so can't log to other node.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-SLOT_DECODE_FAILURE decoding of rack_type:[hex] and slot:[hex] for [chars] failed. Error([dec]): [chars]
Explanation An error happened for a slot fields decoding.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-SYSDB_TUPLE_ERROR [chars] sysdb tuple, [chars] at
Explanation Invalid sysdb tuple
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-UNREGISTERED_FEATURE Unregistered FEATURE:[chars] called by a process(JobID:[dec])
Explanation The specified feature is not yet registered for OBFL manager.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-UPTIME_CONT_TOO_LARGE Too large continuous record, or internal parameters might be corrupted. length:[dec].
Explanation A continuous record too large, or internal parameter might be corrupted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-UPTIME_HIST_INVALID_TASKID Invalid block_and_task_id:[hex]. The file contents might be corrupted.
Explanation This record has invalid block_and_task_id.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-UPTIME_HIST_TOO_LARGE Too large historic uptime record([chars]), or internal parameters might be corrupted. length:[dec] offset_ehud:[dec].
Explanation A historic uptime record too large, or internal parameter might be corrupted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-UPTIME_RECORD_NOT_FOUND Uptime record([chars]) is not found.
Explanation Uptime record is not found
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PLACED_LIB Messages
Error Message%OS-PLACED_LIB-7-STARTUP_POLICY System placement policy found in [chars]. Policy should be moved to a .placement file.
Explanation PlaceD discovered system placement policy specified in an unsupported format; the policy will not be honored. The system should continue to function correctly, though process placement decisions may be sub-optimal.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_LIB-7-VECTOR_OVERFLOW Overflow in message vector ([dec] entries used, [dec] available)
Explanation A client was unable to send a message to PlaceD due to encountering an internal error condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PLACED_MAIN Messages
Error Message%OS-PLACED_MAIN-6-DUMP_CORE PlaceD is performing a voluntary core dump because an unexpected situation has arisen. This is not a crash, but does indicate there was a problem. Reason: [chars]
Explanation The process placement daemon has encountered an unexpected internal situation. If there are no further signs of a problem then it is reasonably safe to assume that the system has recovered.
Recommended Action Please check with your support representative, and if possible provide the core file for further examination.
Error Message%OS-PLACED_MAIN-7-BACKUP_DLRSC Unable to determine new backup dLRSC: [chars]
Explanation PlaceD was notified that the backup dLRSC has changed, but was unable to determine the new location. This means that it is unable to direct its checkpoint updates to that location, and so the system may be in an unstable state if the currently active dLRSC fails.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-BACKUP_DLRSC_REG Failed to register for backup dLRSC notifications: [chars]
Explanation PlaceD failed to register for backup dLRSC change events, and therefore will not be able to mirror its checkpoint data to the backup location.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-CHKPT Failed to initialize checkpoint library: [chars]
Explanation PlaceD was unable to initialize the checkpoint library for saving its internal state, and therefore failed to initialize.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-CHKPT_TARGET Unable to set checkpoint target to location [chars]: [chars]
Explanation PlaceD tried to direct its remote checkpoint updates to the specified location (the backup dLRSC) but encountered an error. This may mean that the system will be in an unstable state if the currently active dLRSC fails.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-CLASSES Failed to initialize classes: [chars]
Explanation PlaceD was unable to set up its object classes, and therefore failed to initialize.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-DBG_ON Failed to switch on debugging flag '[chars]': [chars]
Explanation PlaceD was unable to switch on one of its debugging flags whilst initializing, but ignored the error and continued.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-DBG_REG Failed to register for debug notification: [chars]
Explanation PlaceD was unable to register for notification of its debugging flag settings. PlaceD ignored the error and continued.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-DLRSC Failed to determine whether running on dLRSC: [chars]
Explanation PlaceD was unable to determine whether it was running on the dLRSC, and therefore failed to initialize.
Recommended Action None - PlaceD should restart and recover by itself. If the message recurs: Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support placement command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support placement output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-DLRSC_CHANGED The active dLRSC has changed, so the previously active PlaceD is transitioning to inactive state
Explanation The active dLRSC changed, so the process placement daemon running on the previously active dLRSC has changed to inactive state, so that the instance on the newly active dLRSC can take over without problems.
Recommended Action This indicates an unusual situation, but if there are no other indications of system problems then this is probably benign.
Error Message%OS-PLACED_MAIN-7-DLRSC_NOT Failed to get event type from dLRSC notification: [chars]
Explanation PlaceD couldn't get the event type from a dLRSC notification it received, and therefore may no longer be aware whether or not it is running on the dLRSC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-DLRSC_REG Failed to register for dLRSC notifications: [chars]
Explanation PlaceD failed to register for dLRSC change events, and therefore failed to initialize.
Recommended Action None - PlaceD should restart and recover by itself. If the message recurs: Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support placement command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support placement output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-EVENT_BLOCK Error waiting for message - ignoring: [chars]
Explanation An error occured whilst PlaceD was waiting for a messages, PlaceD ignored the error and continued to wait for more messages.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-EVENT_HANDLER Failed to attach event handler to event manager: [chars]
Explanation PlaceD was unable register an event handling for processing received messages, and therefore failed to initialize.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-EVENT_MGR Failed to create an event manager for channel '[chars]': [chars]
Explanation PlaceD was unable to create an event manager for receiving messages, and therefore failed to initialize.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-INIT_COMPLETE Unable to record that initialization is complete: [chars]
Explanation PlaceD encountered a problem when recording the fact that it has successfully initialized for the first time since this logical router powered up. This means that problems may be encountered when PlaceD restarts, such as after a dLRSC migration.
Recommended Action In the short term this alone does not indicate that the system will operate incorrectly. It is however diagnostic of some underlying problem, and it is possible that the system will operate incorrectly after the placement daemon is forced to restart. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-PROC_READY Failed to signal end of initialization: [chars]
Explanation PlaceD was unable to inform SysMgr that it had completed its initialization.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-QSM_CHAN Failed to publish QSM channel '[chars]' (rendezvous '[chars]'): [chars]
Explanation PlaceD was unable to publish a channel for receiving messages, and therefore failed to initialize.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-QSM_RENDEZ Failed to get rendezvous name: [chars]
Explanation PlaceD was unable to get a rendezvous name for publishing the message channel, and therefore failed to initialize.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-SIGNALS Failed to set up signal mask: [chars]
Explanation One of the OS calls to set up the thread signal mask failed, and therefore PlaceD couldn't initialise.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-SYSDB Failed to do a [chars] with SysDB at '[chars]': [chars]
Explanation PlaceD was unable to perform a critical SysDB operation, and therefore failed to initialize.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-SYSDB_VRFN_INIT Failed to initialize SysDB verification functions handle: [chars]
Explanation PlaceD was unable to initialize its SysDB verification functions handle, and therefore failed to initialize.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-TRACE_BUFFERS Failed to initialize trace buffers: [chars]
Explanation PlaceD was unable to set up its trace buffers, and therefore failed to initialize. This almost certainly means there was insufficient memory available for placed to function correctly.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-UNEXPECTED_REQ Ignoring request type [dec] to non-active PlaceD instance
Explanation An inactive PlaceD instance received a request. Only the instance on the currently active dLRSC should receive any requests.
Recommended Action If this is during a dLRSC migration then it is probably benign, provided no other ill effects are seen. Otherwise it probably indicates a problem in the underlying infrastructure, such as QSM. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-UNKNOWN_MSG Ignoring unrecognized message (comp ID: [dec], msg no: [dec])
Explanation PlaceD did not recognise a message it received, and therefore ignored it.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-UNKNOWN_REQ Ignoring unrecognized request ([dec])
Explanation PlaceD did not recognise a request it received, and therefore ignored it.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PLACED_NODES Messages
Error Message%OS-PLACED_NODES-3-NO_NODES Empty or badly damaged LR inventory - assuming only [chars]%s[chars] present as a fallback strategy
Explanation There were no RP or DRP cards reported in the inventory for process placement. This is an error (the process placement daemon must be running on one such card if nothing else) and will have a very detrimental effect on process placement. The system will limp on as best it can, assuming the only RP/DRP in the LR is that on which the process placement daemon is itself running, and should the inventory problem be resolved then the system will then adjust accordingly automatically.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_NODES-7-LR_INVEN Failed to get [chars] from the LR inventory: [chars]
Explanation PlaceD couldn't retrieve the specified information from the LR inventory it received, and therefore may not have sufficient location information to place processes.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_NODES-7-LR_INVEN_ENTRY Failed to get [chars] from the LR inventory entry [dec]: [chars]
Explanation PlaceD couldn't retrieve the specified information from an entry in the LR inventory, and therefore ignored the entry.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_NODES-7-LR_INVEN_NODETYPE Ignoring entry [dec] in the LR inventory entry since location is of unknown type ([dec])
Explanation PlaceD didn't recognise the location type in an entry in the LR inventory, and therefore ignored the entry.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_NODES-7-LR_NOT Failed to get [chars] from LR notification: [chars]
Explanation PlaceD couldn't retrieve the specified information from an LR notification it received, and therefore may no longer have up-to-date location information.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_NODES-7-LR_REG Failed to register for LR notifications: [chars]
Explanation PlaceD couldn't register for LR notifications, and may therefore be unable to maintain up-to-date location information.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_NODES-7-MEMORY Insufficient memory for object representing location [chars] (partner [chars]), location will not be used for placement
Explanation An object to represent the location could not be created (probably due to insufficient memory). PlaceD will not be able to place processes at the location.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*
Error Message%OS-PLACED_NODES-7-NO_INVENTORY The LR inventory is empty or not available (despite waiting for over a minute for it) - error '[chars]'. PlaceD cannot function without this information, so will restart and attempt to wait for the information again.
Explanation Placement requires a complete knowledge of the LR inventory in order to function as expected. The LR inventory is currently not fully populated, so PlaceD is restarting in order to give the LR inventory time to finish initialising. If this message continues to appear, this indicates that the LR information is not able to complete, and that this will be affecting the ability of the system to function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_NODES-7-NODEID Failed to obtain ID of current location: [chars]
Explanation PlaceD was unable to determine the ID of the location at which it was running, and therefore failed to initialize.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_NODES-7-NOT_RUNNING LR inventory indicated that state of location [chars] was [dec], using state [dec] (RUNNING) instead
Explanation The LR inventory showed that the location at which PlaceD was running was not in the running state. PlaceD assumed this was erroneous.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PLACED_PLACE Messages
Error Message%OS-PLACED_PLACE-3-ALGO Placement algorithm failed: [chars]
Explanation An error occured in the algorithm used by PlaceD to determine the optimal placement.
Recommended Action If the message recurs: Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support placement command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support placement output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PLACE-3-ALGO_RERUN Unable to determine optimal placement after running algorithm [unsigned int] times
Explanation PlaceD was unable to place one or more processes on any of the available nodes in the system.
Recommended Action If the message recurs: Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support placement command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support placement output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PLACE-4-CANT_START Unable to start program [chars]%s[chars] since there is insufficient cpu or memory capacity
Explanation Starting the new program would overflow the watermarks for the cpu or memory capacity currently available.
Recommended Action Options include adding or unpairing a DRP, deconfiguring some features, or increasing the watermarks configured by placement { cpu | memory } maximum. One can also specify particularly important or disposable processes via configuring large or small existence affinities if so desired.
Error Message%OS-PLACED_PLACE-4-KILLING Killing program [chars]%s[chars] since there is insufficient cpu or memory capacity for all configured processes
Explanation There is insufficient cpu or memory capacity for all configured placeable processes.
Recommended Action Options include adding or unpairing a DRP, deconfiguring some features, or increasing the watermarks configured by placement { cpu | memory } maximum. One can also specify particularly important or disposable processes via configuring large or small existence affinities if so desired.
Error Message%OS-PLACED_PLACE-4-LISTEN Unable to listen for multicast messages: [chars] ([chars])
Explanation PlaceD is unable to register to receive multicast messages. This means that the location which emitted the message will not be able to keep its local copy of the current placement, persisted to non-volatile storage, up to date.
Recommended Action If this is a transient issue then the router will recover. Also, restarting the PlaceD instance that emitted this message will cause it to re-register to receive these updates. If the issue persists: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PLACE-4-REOP_ABORTED Re-optimization of the placement aborted due to [chars]. Placement has been partially re-optimized. Running the command again will complete the re-optimization
Explanation The re-optimization of the placement was aborted because PlaceD had to respond to a change in the router environment.
Recommended Action Run the 'placement reoptimize' command again to complete the re-optimization.
Error Message%OS-PLACED_PLACE-5-RESTARTING Program [chars]%s[chars] has now been started (was previously unable to run)
Explanation The program was previously prevented from running due to insufficient cpu or memory, but that situation no longer applies and so the program has now been started. This message may also result from problems in retrieving the node inventory for the router.
Recommended Action Options to prevent the original inability to run include adding or unpairing a DRP, deconfiguring some features, or increasing the watermarks configured by placement { cpu | memory } maximum. One can also specify particularly important or disposable processes via configuring large or small existence affinities if so desired. If a node inventory problem is suspected: Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support placement command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support placement output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PLACE-5-WRITE_PERSIST Unable to [chars] when writing persistent placement: [chars] ([chars])
Explanation The current placement was being persisted to non- volatile storage, but a problem occured. If this condition persists then it is possible that the placement of processes across the available RPs and DRPs will be different after the next router/LR reload.
Recommended Action The write operation will be automatically re-tried later, so if this is a transitory condition then the system will recover completely without intervention. If this is a persistent problem then: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PLACE-6-REOP_COMPLETE Re-optimization of the placement complete. Use 'show placement' to view the new placement
Explanation The re-optimization of the placement has completed.
Recommended Action Use the 'show placement' command to view the newly re-optimized placement.
Error Message%OS-PLACED_PLACE-6-REOP_START Re-optimization of the placement requested. You will be notified on completion
Explanation A re-optimization of the placement has started. The most optimal location of each program will be re-calculated by ignoring any affinity of the default program to the current location. Any resulting migrations will be rate limited accoring to the slow migration interval configured for each program.
Recommended Action Wait for the notification that the re-optimization has completed before adding or removing cards from the router, adding new configuration, or starting a new re-optimization.
Error Message%OS-PLACED_PLACE-7-AFFINITY_ITERATOR Unable to obtain affinity iterator for [chars]
Explanation PlaceD was unable to obtain an iterator for all the affinities.
Recommended Action This is non-critical, and in the absence of other errors, simply means that one facility (triggering reoptimisation of placements by the user) is inoperable.
Error Message%OS-PLACED_PLACE-7-ALGO_INIT Unable to create placement algorithm
Explanation PlaceD was unable to create the placement algorithm object, and therefore failed to initialize.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*
Error Message%OS-PLACED_PLACE-7-CHKPT_INIT Failed to initialize checkpoint store: [chars]
Explanation PlaceD was unable to initialize the checkpoint store for the placement package, and therefore failed to initialize.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PLACE-7-CHKPT_UPDATE Failed to update checkpoint record for re-optimization status: [chars]
Explanation PlaceD was unable to update the checkpointed information indicating whether a placement re-optimization is in progress.
Recommended Action This should not be a service-affecting incident. However, PlaceD may no longer be able to correctly report the completion of re-optimization events. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PLACE-7-LOOKUP_PERSIST Unable to [chars] when looking up persisted placement for [chars]%s[chars]: [chars] ([chars])
Explanation PlaceD hit a problem when looking up the persisted location for a process. This means that it may not be placed on the same location as it was assigned before the most recent reload of the router or LR.
Recommended Action This should not be a service-affecting incident. If this is because the card on which the process was previously placed has been removed, taken administratively down, or been assigned to a different logical router, then this is entirely expected and benign. Otherwise: Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support placement command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support placement output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PLACE-7-SYSDB Unable to [chars] with SysDB at [chars]: [chars]
Explanation PlaceD was unable to register with SysDB for receiving 'placement persist now' actions. This facility will be unavailable.
Recommended Action This is non-critical, and in the absence of other errors, simply means that one facility (triggering persisting of placements by the user) is inoperable.
Error Message%OS-PLACED_PLACE-7-TIMER Unable to [chars] persistence timer
Explanation PlaceD was unable to create the persistence timer, and therefore failed to initialize.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*
PLACED_PROGS Messages
Error Message%OS-PLACED_PROGS-3-KILL_MAN The attempt to kill process '[chars]%s[chars]' (job ID [dec]) at location [chars] failed, it should be killed manually
Explanation PlaceD attempted to kill a process, but it is still running
Recommended Action Attempt to kill the process manually. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-3-KILL_PROC Failed to kill process '[chars]%s[chars]' (job ID [dec]) at location [chars]: [chars]
Explanation PlaceD was unable to kill a process. PlaceD's view of the system state will now be incorrect.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-3-KILL_UNKNOWN Attempted to kill process '[chars]%s[chars]' (job ID [dec]) at location [chars], but failed to determine whether it is dead
Explanation PlaceD attempted to kill a process, but is unable to determine whether the attempt was successful.
Recommended Action Determine whether the process is still running, if so, attempt to kill it manually. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-3-START_PROC Failed to start process '[chars]%s[chars]' at location [chars]: [chars]
Explanation PlaceD was unable to start a process. PlaceD's view of the system state will now be incorrect.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-4-CANT_SUSPEND Unable to suspend the request to start the process '[chars]%s[chars]' from location [chars]: [chars]
Explanation This is an out-of-memory message. PlaceD received a request to start the specified process on the specified location, and wanted to suspend the request. This is because PlaceD has a better location in mind, but is keeping the present location as a backup in case that card gets into trouble. However, there was insufficient resources for PlaceD to effect the suspension.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *SUPPORT*
Error Message%OS-PLACED_PROGS-4-CHKPT_DELETE Failed to delete the checkpoint data for process '[chars]%s[chars]' at location [chars]: [chars]
Explanation PlaceD was unable to delete the checkpoint segment for an application, eg before starting it from cold on that location.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-4-CHKPT_MIGRATE Failed to migrate checkpoint data for process '[chars]%s[chars]' from location [chars] to [chars]: [chars]
Explanation Whilst moving a process to a new location, PlaceD was unable to migrate the checkpointed data belonging to the process. No checkpointed data was therefore available to the process when it started at the new location.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-4-CHKPT_WRITE Failed to update checkpoint record for process '[chars]': [chars]
Explanation PlaceD was unable to update the checkpointed information for the specified process. PlaceD will fail to recover, or will recover out of date, information for the process if it is restarted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-4-START_PROC_MIGRATE Process '[chars]%s[chars]' cannot be migrated to the location pair [chars] [chars] because the pair is no longer up
Explanation PlaceD was unable to migrate the specified process to the specified locations because they are no longer up. If necessary, an alternative location will be selected for the process.
Recommended Action If the specified location pair is still up: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-4-SYSTEM_POLICY Failed to read system placement policy. Process placement decisions will be sub-optimal. [chars]
Explanation PlaceD was unable to read the system placement policy and thus has no built-in policy to use when placing processes. The results of process placement decisions made by PlaceD will be sub-optimal.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-4-UNKNOWN_PROC Unable to place '[chars]%s[chars]' since this is an unknown program type
Explanation PlaceD was asked to place a program whose name does not appear in the list of placeable processes and their properties.
Recommended Action This indicates that placed is receiving inconsistent or incomplete information from sysmgr. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-4-UNREC_PROG Ignoring request to remove unrecognized process '[chars]%s[chars]'
Explanation PlaceD did not recognise the process it was asked to remove, and therefore ingnored the request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-6-COLD_START The process '[chars]%s[chars]' is being restarted on the new location [chars] [chars] from cold, without its checkpoint data
Explanation The process is being replaced without its checkpoint data, eg if the node it was previously running on has failed. This may impact the router's operation.
Recommended Action If every RP and DRP has a standby, then this situation should not occur unless there is a double-failure of both active and standby cards simultaneously. If this message occurs in any other situation: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-6-REMOVING_ENTITY '[chars]%s[chars]' appears to no longer be configured, and will not be started again until reconfigured.
Explanation PlaceD was unable to start a process because it is purely configuration-driven and there is no configuration present. PlaceD will no longer attempt to keep the process running.
Recommended Action If the process has indeed been deconfigured (possibly a long time before this message appeared), then this is entirely benign. Otherwise: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-6-START_PROC_NODE Process '[chars]%s[chars]' will be started at the location pair [chars] [chars] only when one of the locations completes booting
Explanation PlaceD was unable to start the specified process (and possibly other processes as well) because the specified locations are not running. The locations may still be in the process of booting. When one of the locations completes booting the process will be started.
Recommended Action If the locations are still in the process of booting then this is benign; the process will be started normally as part of the boot process. If the boot process takes too long, an alternative location for the process will automatically be chosen.
Error Message%OS-PLACED_PROGS-6-START_PROC_TIMEOUT Process '[chars]%s[chars]' cannot be started at the location pair [chars] [chars]; an alternative location will be selected
Explanation PlaceD was unable to start the specified process (and possibly other processes as well) at the specified locations because they are taking too long to finish booting. An attempt will be made to start the process at an alternative location.
Recommended Action If the specified location pair does not boot successfully: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-7-CHKPT_REG Failed to register checkpoint table: [chars]
Explanation PlaceD was unable to register a table for checkpointing its program information, and therefore failed to initialize.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-7-CLASS_INFO Failed to get all program info from SysMgr at location [chars]: [chars]
Explanation PlaceD was unable to get information from System Manager about all program classes and will now be in an indeterminate state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-7-IPPH Failed to service an is-program-placed-here request: [chars]
Explanation PlaceD was asked about the location of a process, but was unable to service the request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-7-JID Failed to get job ID for process '[chars]%s[chars]' at location [chars]: [chars]
Explanation PlaceD was unable to get the Job ID for a process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-7-NOT_PLACEABLE Ignoring info from SysMgr about non-placeable process '[chars]'
Explanation PlaceD received information from System Manager about a program or program class that is not placeable, and therefore ignored the information.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-7-PARSE Failed to parse keyword '[chars]' in file [chars]:[dec] ([chars])
Explanation Whilst getting the system placement policy, an error occured whilst processing the specified file.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-7-PROG_TYPE Ignoring unknown program type ([dec]) for '[chars]'
Explanation PlaceD did not recognise the program type received from System Manager, and therefore ignored the program information.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-7-RECOVER_STATE Failed to recreate state for [chars]%s[chars] when attempting [chars]: [chars]
Explanation PlaceD was unable to recreate its internal representation for the specified program, either from its checkpoint data or from information from SysMgr, and therefore failed to intialize.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-7-SYSMGR_TARGET Failed to set SysMgr target location to [chars]: [chars]
Explanation PlaceD was unable to set the target location in order to communicate with the appropriate System Manager instance.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-7-TIMEOUT Ignoring timeout event with unknown [chars]
Explanation A timeout event occurred, but PlaceD was unable to determine which program or node the event was for, and therefore ignored it.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-7-TIMERS Unable to initialize request timers
Explanation PlaceD was unable to initialize the request timers, and therefore failed to initialize.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*
Error Message%OS-PLACED_PROGS-7-UNEXPECTED_NODE A message was received from the unknown location [chars]
Explanation A message was received from a location not known to be an RP or DRP in the current LR.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-7-UPDATE_CLASS Failed to get updated info for '[chars]' from SysMgr: [chars]
Explanation PlaceD was unable to update information from System Manager about the program or program class specified.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PLACED_PROPS Messages
Error Message%OS-PLACED_PROPS-4-MAX_AFF Reached maximum limit on number of affinities ([dec]) for '[chars]', ignoring remaining affinities
Explanation Whilst determining the optimal placement, PlaceD reached the limit on the number of affinities allowed per process, and therefore ignored any further affinities.
Recommended Action Remove configured affinities that apply to this process until the number is equal to or below the given limit.
Error Message%OS-PLACED_PROPS-5-BAD_CONFIG Refusing to apply some placement policy that would be rejected by placed's config verifier
Explanation Some placement policy is being ignored, since entering it normally would cause it to be rejected. This situation can occur only in rare situations, such as leaving placement policy configured for a program after that program's package has been de-activated from all locations.
Recommended Action If the situation is something like that in the explanation, then this message is correctly warning that the 'dead' policy is no longer acted upon. Otherwise: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROPS-5-REV_AFF Failed to apply program affinity from '[chars]' to '[chars]': affinity in reverse direction already configured
Explanation PlaceD attempted to set up an affinity from the first program class to the second, but discovered that an affinity from the second to the first already existed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROPS-5-SUSPECT_NODE The affinity for program [chars] to location [chars] will be ignored until an RP or DRP is inserted at that location
Explanation The operator configured an affinity between a program and a location-set that includes a location not currently occupied by an RP or DRP. This part of the affinity policy will be ignored until an RP or DRP is inserted there. The policy applying to a given program (or program instance) can be inspected via the 'show placement policy program [instance ]' command.
Recommended Action Correct the configuration if this is an error, or insert an RP or DRP for the configuration to have any effect.
Error Message%OS-PLACED_PROPS-7-INIT Failed to initialize the Properties module: [chars]
Explanation PlaceD was unable to perform one of the steps required to initialize its Properties module.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*
Error Message%OS-PLACED_PROPS-7-NODETYPE Unknown location-type ([dec]) in location-type affinity (process '[chars]')
Explanation Whilst determining the optimal placement for the specified process, PlaceD encountered an affinity containing an unrecognized location-type, and therefore ignored the affinity.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PMHAC Messages
Error Message%OS-PMHAC-7-ERR_DLL_INIT PM HA Client DLL failed to initialize debugging services, reason [chars]
Explanation The Platform Manager HA DLL encountered an internal software error. The debugging services could not be initialized. This problem should rarely happen. Restarting the Platform Manager HA process might recover the problem
Recommended Action There is no action required because the client process should handle this error.
PMHAD Messages
Error Message%OS-PMHAD-3-ERR_NOMEM [chars]
Explanation The Platform Manager HA Driver DLL was unable to add any new fault record due to lack of memory. This condition will cause the DLL to exit.
Recommended Action Add more memory to the card specified in the System Message. If the this message recurs after a memory upgrade, copy the System Message text exactly as it appears on the console or in the system log, and contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OS-PMHAD-4-ERR_NOMEM_WARNING [chars]
Explanation The Platform Manager HA Driver DLL was unable to add one new fault record due to lack of memory, but it is still running.
Recommended Action Add more memory to the card specified in the System Message. If the this message recurs after a memory upgrade, copy the System Message text exactly as it appears on the console or in the system log, and contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OS-PMHAD-7-ERR_DLL_INIT [chars], reason [chars]
Explanation The Platform Manager HA Driver DLL encountered an internal software error. The debugging services could not be initialized. This problem should rarely happen. Restarting the Platform Manager HA process might recover the problem
Recommended Action There is no action required because the client process should handle this error.
Error Message%OS-PMHAD-7-ERR_INIT [chars], reason: [chars]
Explanation The Platform Manager HA Driver DLL was unable to initialize due to internal software resource issues.
Recommended Action The Platform Manager HA Driver DLL will exit and the client process should handle the error accordingly. Please exam the output of show logging to see if similar issue had occured.
PROCFIND Messages
Error Message%OS-PROCFIND-3-PROC_INFO Failed to retrieve info for process [dec]: [chars]
Explanation Procfind was unable to read the information for the specified process, and will therefore return incomplete results.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PROCFIND-3-PROC_OPEN Failed to open process [dec]: [chars]
Explanation Procfind was unable to open the specified process, and will therefore return incomplete results.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PROCFIND-4-EVENT_BLOCK Error waiting for message - ignoring: [chars]
Explanation An error occured whilst Procfind was waiting for messages, Procfind ignored the error and continued to wait for more messages.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PROCFIND-4-NODETYPE Running on unknown nodetype, assuming it is a linecard
Explanation Procfind was did not recognise the node type on which it was running, and therefore assumed it was a linecard.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PROCFIND-4-READY Failed to signal end of initialization to SysMgr: [chars]
Explanation Procfind was unable to inform System Manager that it has finished initializing and is ready to service request. Procfind ignored the error and continued normally.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PROCFIND-7-EVENT_MGR Failed to create an event manager: [chars]
Explanation Procfind was unable to create an event manager for receiving messages, and therefore failed to initialize.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PROCFIND-7-MEMORY Failed to allocate memory for [chars]
Explanation Insufficient resources were available to allocate memory for the specified item. Procfind may not be able to continue running.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%OS-PROCFIND-7-NODEID Failed to get node ID of current node: [chars]
Explanation Procfind was unable to determine the ID of the node on which it was running, and therefore failed to initialize.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PROCFIND-7-SYSDB_BIND Failed to bind to SysDB at '[chars]': [chars]
Explanation Procfind was unable to bind to the SysDB server, and therefore failed to initialize.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PROCFIND-7-SYSDB_EDM_INIT Failed to initialize SysDB EDM functions handle: [chars]
Explanation Procfind was unable to initialize its SysDB EDM functions handle, and therefore failed to initialize.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PROCFIND-7-SYSDB_EDM_REG Failed to register with SysDB as an EDM at '[chars]': [chars]
Explanation Procfind was unable to register with the SysDB server for as an EDM, and therefore failed to initialize.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PUF Messages
Error Message%OS-PUF-4-MCAST_MSG Problem processing incoming multicast message: [chars]
Explanation An incoming multicast message was received, supposedly containing data that should be persisted to non-volatile storage on the receiving location, but this persisting operation could not complete because of a problem.
Recommended Action This is unlikely to be immediately threatening to the router's health, but could cause misbehavior if the router is reloaded. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
QAD_LIB Messages
Error Message%OS-QAD_LIB-3-ERROR Operation [chars] failed : [chars]
Explanation The specified operation failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QAD_LIB-6-INFO Condition [chars] : [chars]
Explanation The specified condition has occurred
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
QAD_QUEUE_MODEL Messages
Error Message%OS-QAD_QUEUE_MODEL-3-ERROR Operation [chars] failed : [chars]
Explanation The specified operation failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
QAD_SERVER Messages
Error Message%OS-QAD_SERVER-3-ERROR Operation [chars] failed : [chars]
Explanation The specified operation failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
QNET_LC Messages
Error Message%OS-QNET_LC-7-BASE_BAD_CHAIN_TYPE [chars]:[dec]:[chars]: Invalid attempt to build chain (type [dec])
Explanation qnetbase_builder_func() called with bad chain type.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET_LC-7-BASE_CONTROL_FUNC_ERR [chars]:[dec]:[chars]: Base Control function erroneously called!
Explanation qnetbase_control_func() wrongly called.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET_LC-7-CAPS_BAD_CHAIN_TYPE [chars]:[dec]:[chars]: Invalid attempt to build chain (type [dec])
Explanation qnetcaps_builder_func() called with wrong chain type.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET_LC-7-CAPS_CONTROL_FUNC_ERR [chars]:[dec]:[chars]: Caps Control function erroneously called!
Explanation qnetcaps_control_func() has been called, which should never happen.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET_LC-7-DUPLICATE_BMA_PAK [chars]: Cannot duplicate BMA packet (rc=[dec] dropping Qnet packet.
Explanation pak_netio_duplicate() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET_LC-7-ENCAPS_FUNC_ERR [chars]:[dec]:[chars]: Qnet encapsulation node erroneously called!
Explanation qnetcaps_encaps() has been called, which should never happen.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET_LC-7-LOST_QNET_CONN Lost connection to Qnet process; dropping packets.
Explanation netio_dll_packet_input_NEW() to Qnet failed and Qnet connection is closed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET_LC-7-PAK_INPUT_FAIL [chars]:[dec]:[chars]: packet_input returned non-zero result code ([dec])
Explanation netio_dll_packet_input_NEW() to Qnet failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET_LC-7-UINT32_GET [chars]:[dec] failed to get destination slot. error [dec]
Explanation pak_netio_uint32_get() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
QNET Messages
Error Message%OS-QNET-0-EMG [chars]
Explanation An EMERGENCY level message was emitted by QNET.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET-1-ALT [chars]
Explanation An ALERT level message was emitted by QNET.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET-2-CRT [chars]
Explanation A CRITICAL level message was emitted by QNET.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET-3-ERR [chars]
Explanation An ERROR level message was emitted by QNET.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET-4-DUMPER_SNAP_DUMP Process [dec] requested voluntary [chars] dump of itself
Explanation A non-invasive voluntary coredump requested by the process. Process might be experiancing a condition which needs investigation. This core file will help analysing the issue.
Recommended Action This should not occur in normal conditions, please provide the coredump to TAC.
Error Message%OS-QNET-4-DUMPER_SNAP_NODUMP Problem with voluntary core dump requested by [dec] when [chars]: [chars]
Explanation A non-invasive voluntary coredump was requested by the process, but a problem occured that prevented the coredump from being created.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET-4-WRN [chars]
Explanation A WARNING level message was emitted by QNET.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET-5-NOT [chars]
Explanation A NOTICE level message was emitted by QNET.
Recommended Action No action is required.
Error Message%OS-QNET-6-DUMPER_SNAP_DUMP_OK Voluntary core dump requested by process [dec] completed
Explanation A non-invasive voluntary coredump requested by the process completed successfully. Process might be experiancing a condition which needs investigation. This core file will help analysing the issue.
Recommended Action This should not occur in normal conditions, please provide the coredump to TAC.
Error Message%OS-QNET-6-INF [chars]
Explanation An INFO level message was emitted by QNET.
Recommended Action No action is required.
Error Message%OS-QNET-7-DEB [chars]
Explanation A DEBUG level message was emitted by QNET.
Recommended Action Debug message only. No action is required.
Error Message%OS-QNET-7-SIO_Q_PROD q_produce for QNET tx failed, rc = [dec]
Explanation could not send pkt to fabric driver.
Recommended Action This should not occur in normal conditions
QSM Messages
Error Message%OS-QSM-3-ADD_SYMLINKS_DIR Unable to add directory link [chars]: [chars]
Explanation A error occured while processing a QSM configuration file. This could be due to a problem with the installed media or file system damage. QSM will continue startup-up, but some system functionality may be impared.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-ADD_SYMLINKS_FILE Unable to add link [chars]-[chars]: [chars]
Explanation A error occured while processing a QSM configuration file. This could be due to a problem with the installed media or file system damage. QSM will continue startup-up, but some system functionality may be impared.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-ADMIN_ADD (transition message) Detected admin plane add for [chars]. class: [hex], svctype: [hex], msgflags: [hex]
Explanation Development debug message
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-3-BAD_DBDUMP_MESSAGE An database dump message from another node could not be processed ([chars]): [chars]
Explanation The indicated error occured while processing a dbdump from another node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-BAD_MESSAGE An unexpected message from another node could not be processed ([chars]): [dec]
Explanation An invalid message type was received from another node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-BAD_UPDATE_MESSAGE An update message from another node could not be processed ([chars]): [chars]
Explanation The indicated error occured while processing an update from another node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-CERR_REGISTER Unable to register the QSM error messages: [chars]
Explanation The QSM error number/messages table could not be registered with the cerrno system. Error translations will not be available.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-CHECKPOINT_CANT_OPEN Unable to open QSM checkpoint file [chars]: [chars]
Explanation The checkpoint file could not be opened. A restart of QSM is likely to have incomplete data.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-CHECKPOINT_CANT_RELOAD Unable to re-load QSM link [chars]-[chars]: [chars]
Explanation A link found in the checkpoint file could not be created in the QSM database.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-CHECKPOINT_CANT_RELOAD_NOTIFY Unable to re-load QSM notification for [chars]: [chars]
Explanation A link found in the checkpoint file could not be created in the QSM database.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-CHECKPOINT_CANT_RENAME Unable to rename checkpoint file [chars]-[chars]: [chars]
Explanation The checkpoint temporary file could not be renamed. A restart of QSM is likely to have incomplete data.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-CHECKPOINT_CANT_SEEK Unable to seek to the end of the QSM checkpoint file [chars]: [chars]
Explanation The checkpoint file could not be appended to. A restart of QSM is likely to have incomplete data.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-CHECKPOINT_CANT_TRUNCATE Unable to truncate QSM checkpoint file [chars]: [chars]
Explanation The QSM checkpoint file could not be truncated -- prior to being overwritten with updated data. A restart of QSM is likely to have incomplete data.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-CHECKPOINT_CANT_WRITE Unable to write to QSM checkpoint file [chars]: [chars]
Explanation A link could not be written to the QSM checkpoint file. A restart of QSM is likely to have incomplete data.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-CHECKPOINT_FORMAT Insufficient buffer size to format QSM checkpoint record. Have [dec], need [dec]
Explanation A QSM checkpoint record could not be placed in the checkpoint file due to insufficient buffer space.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-CHECKPOINT_LOCK_FAILURE Checkpoint lock failure: [chars]
Explanation The lock that protects the QSM checkpoint database could not be taken. The checkpoint database could become corrupted -- causing a restart of QSM to have incomplete data.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-CHECKPOINT_NOSPACE Unable to allocate space for the checkpoint buffer
Explanation A QSM checkpoint record could not be placed in the checkpoint file due to insufficient heap space.
Recommended Action This indicates a low memory condition. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%OS-QSM-3-INITIALIZATION_FAILURE Unable to initialize [chars]: [chars]
Explanation The QSM process wasn't able to startup up due the indicated failure during initialization. A restart of the process will be attempted. If the process can not be sucessfully started after several attempts, the board will probably be unusable.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-INVALID_PLATFORM_TYPE Platform_get_type returned an unknown node type: [dec]
Explanation The QSM process wasn't able to startup up due the indicated failure during initialization. A restart of the process will be attempted. If the process can not be sucessfully started after several attempts, the board will probably be unusable.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-INVALID_SYMLINKS_FILE Invalid line in symlinks file: [chars]
Explanation A startup configuration file for QSM contained an invalid line. This could be due to a problem with the installed media or file system damage. QSM will continue startup-up, but some system functionality may be impared.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-LINK_BAD_MODE A Link database entry had an unexpected mode: 0o%o
Explanation The mode data (MOG) for a link entry had an unexpected value. This could indicate a memory corruption problem.
Recommended Action Take a dump of the process and restart it. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-LINK_CREATE_FAILURE Unable to create link database entry '[chars]' ([chars]): [chars]
Explanation An entry could not be placed in the links database. The full error message should indicate where the failure occured and why.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-LINK_DELETE_FAILURE_INUM Unable to delete link database entry: [dec]
Explanation A link could not be deleted from the links database. This could indicate either a code problem or a memory corruption problem.
Recommended Action Take a dump of the process and restart it. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-LINK_DELETE_FAILURE_PATH Unable to delete link database entry: [chars]
Explanation An entry could not be deleted from the links database. The full error message should indicate where the failure occured and why.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-LINK_FREE_ZERO_INUM The QSM links database was requested to free a inode with a zero inumber
Explanation A internal error occured. A small amount of memory has been lost. QSM can be restarted to recover the lost memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-LINK_INVALID_CUR_INDEX Invalid cur index in [chars]. CUR: [dec], path: [chars], inum: [dec]
Explanation A internal error has occured. The QSM directory scrub routine has been aborted. This should not cause any instability unless this message is repeated many times.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-LINK_LOCK_FAILURE A lock failure occured in the links database ([chars]): [chars]
Explanation An expected database lock was not held. This could indicate a memory corruption problem.
Recommended Action Take a dump of the process and restart it. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-LINK_WRONG_RESULT link delete returned wrong link entry. path [chars], result: [hex], delete_result: [hex]
Explanation This is a debug message that is not compiled into a customer version of the code.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-3-LOCATE_SYMLINKS_FILE Unable to locate symlinks file at etcpath [chars]: [chars]
Explanation An expected startup configuration file for QSM could not be found. This could be due to an install problem or due to data being deleted from the installation file system. QSM will continue startup-up, but some system functionality may be impared.
Recommended Action Your installed file system is missing a file. Perform a re-install to refresh the missing file. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-LOCK_FAILURE A lock failure occured ([chars]): [chars]
Explanation The indicated error occurred while attempting to hold or release a lock.
Recommended Action Take a dump of the process and restart it. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-LOCK_FAILURE_LOCKTEST [chars]: [dec]. A lock failure occured ([chars]): [chars]
Explanation The indicated error occurred while attempting to hold or release a lock.
Recommended Action Take a dump of the process and restart it. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-NO_MEMORY Unable to obtain [dec] bytes of memory while: [chars]
Explanation QSM could not obtain system meory while performing the indicated operation.
Recommended Action This indicates a low memory condition. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%OS-QSM-3-NON_ADMIN_ADD (transition message) Detected NON admin plane add for [chars]. class: [hex], svctype: [hex], msgflags: [hex]
Explanation Development debug message
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-3-NOTIFY_LOCK_FAILURE A lock failure occured in the notification database ([chars]): [chars]
Explanation An expected database lock was not held. This could indicate a memory corruption problem.
Recommended Action Take a dump of the process and restart it. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-NOTIFY_WRITE_FAILED Notification checkpoint record could not be written: [chars]
Explanation A notification record could not be written to the QSM notification checkpoint file. A restart of QSM is likely to have incomplete data.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-OPEN_SYMLINKS_FILE Unable to open symlinks file [chars]: [chars]
Explanation An expected startup configuration file for QSM could not be opened. This could be due to a problem with the installed media or file system damage. QSM will continue startup-up, but some system functionality may be impared.
Recommended Action Your installed file system may be corrupted. Perform a format and re-install to fix it. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-SEND_DATABASE_MESSAGE Unable to send a database message ([chars]): [chars]
Explanation A database update or dump mesage could not be sent to the other nodes.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-7-BAD_LWM_MSG Bad LWM Message received from pid [dec]. ([chars]): [chars]
Explanation An error was received while processing a request from a local process. There could be a version mis-match or corruption in the client process. The error message should provide some clue to the problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-7-BAD_LWM_VERSION A QSM message was received, but it had the wrong version number. Received: [hex], Expected: [hex].
Explanation An error was received while processing a request from a local process. There could be a version mis-match or corruption in the client process. The error message should provide some clue to the problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-7-DEBUG_KEY_CREATE Could not create key. rc: [dec], qsm_lock_key: [dec]
Explanation This is a debug message that is not compiled into a customer version of the code.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-7-DEBUG_SPECIFIC_ALLOC Could not alloc space for thread specific lock data: [chars]
Explanation This is a debug message that is not compiled into a customer version of the code.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-7-DEBUG_SPECIFIC_SET Could not set thread specific for lock data: [chars]
Explanation This is a debug message that is not compiled into a customer version of the code.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-7-LINK_BAD_THREAD_INUM A link was not threaded correctly in the links database ([chars]). thread: [dec]. inum: [dec]
Explanation This is a debug message that is not compiled into a customer version of the code.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-7-LINK_BAD_THREAD_PATH A link was not threaded correctly in the links database ([chars]). thread: [dec]. path: [chars]
Explanation This is a debug message that is not compiled into a customer version of the code.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-7-LINK_LOST_EMPTY_DIRECTORY An empty directory was to be deleted but inode [dec] could not be found: [chars]
Explanation An empty directory was to be automatically purged from the QSM database. When the directory was searched for, it could not be found.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-7-LOCK_HELD Unexpected lock held at [chars]: [dec]. Last taken at [chars]: [dec]
Explanation This is a debug message that is not compiled into a customer version of the code.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-7-LOCK_NOTFOUND A lock list did not have an expected lock at [chars]: [dec]
Explanation The lock list was corrupted.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-7-LOCK_WRONG_COUNT A lock list had an incorrect count at [chars]: [dec]. ([dec] vs [dec])
Explanation The lock list was corrupted.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-7-LOCKORDER_FAILURE A lock ordering failure occured ([chars]) at [chars]:[dec]. ([dec] vs [dec]).
Explanation A lock was taken in an invalid sequence.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-7-LOCKORDER_UPGRADE A lock upgrade (read to write) attempt was made at [chars]:[dec]. The lock was first taken at [chars]:[dec]
Explanation An invalid upgrade was made of a lock.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-7-NODE_DELETE_FAILURE A node was only partially deleted. thread [dec], node: [chars]
Explanation Internal memory corruption occured in the QSM nodes database.
Recommended Action Take a dump of the process and restart it. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-7-NODE_LOOKUP_FAILURE A node could not be found in the QSM nodes database: [chars]
Explanation An attempt to use a QSM link was made -- but the remote node that exported the link to the local node was not in the local nodes database. This could be a harmless timing condition.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-7-NON_LOCAL A QSM message was received from a non-local process
Explanation A process on another node contacted the local QSM server. The local server refused the request.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-7-NOTIFY_REGISTER_FAILED notification register of [chars] failed: [chars]
Explanation A application requested database notification could not be placed in the QSM notification database. An error will be returned to the client process.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-7-NOTIFY_UNREGISTER_FAILED notification register of [dec] failed: [chars]
Explanation A application requested database un-notification could not be removed from the QSM notification database. An error will be returned to the client process.
Recommended Action Debug message only. No action is required.
QUEUE Messages
Error Message%OS-QUEUE-7-LINKED Bad [chars] of [hex] in queue [hex]
Explanation The router is running short on memory.
Recommended Action It may be necessary to free some memory by exiting a program. If this message recurs, call your technical support representative for assistance.
Error Message%OS-QUEUE-7-NOTQ [chars] didn't find [hex] in queue [hex]
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%OS-QUEUE-7-QCOUNT Bad [chars] [hex] count [dec]
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
