Cisco IOS XR System Error Reference Guide for Platform Independent Messages, Release 3.3
Internet Protocol (IP) Messages
Downloads: This chapterpdf (PDF - 533.0KB) The complete bookPDF (PDF - 7.09MB) | Feedback

Internet Protocol (IP) Messages

Table Of Contents

Internet Protocol (IP) Messages

ARP_GMP Messages

ARP Messages

DOMAIN_SERVICES Messages

IEP Messages

IP_ARM_PLIB Messages

IP_ARM_TEST Messages

IP_ARM Messages

IPV4_EDM Messages

IPV4_IO Messages

IPV4_MA Messages

IPV6_MA Messages

IPV6_ND Messages

IPV6_SW Messages

IPV6 Messages

LIBIPV4 Messages

LIBIPV4PROTO Messages

LIBIPV6PROTO Messages

MGII_API Messages

MPA_CONSUMER Messages

MPA Messages

PFILTER_MA Messages

RAW Messages

rlogin Messages

RLOGIND Messages

RSHD Messages

SMIAP Messages

SOCKET Messages

STANDBY Messages

TCP Messages

telnet Messages

TELNETD Messages

UDP Messages

VRRP Messages


Internet Protocol (IP) Messages


This section contains all Internet Protocol related System Error Messages. The following facility codes are represented in this module:

ARP_GMP Messages

ARP Messages

DOMAIN_SERVICES Messages

IEP Messages

IP_ARM_PLIB Messages

IP_ARM_TEST Messages

IP_ARM Messages

IPV4_EDM Messages

IPV4_IO Messages

IPV4_MA Messages

IPV6_MA Messages

IPV6_ND Messages

IPV6_SW Messages

IPV6 Messages

LIBIPV4 Messages

LIBIPV4PROTO Messages

LIBIPV6PROTO Messages

MGII_API Messages

MPA_CONSUMER Messages

MPA Messages

PFILTER_MA Messages

RAW Messages

rlogin Messages

RLOGIND Messages

RSHD Messages

SMIAP Messages

SOCKET Messages

STANDBY Messages

TCP Messages

telnet Messages

TELNETD Messages

UDP Messages

VRRP Messages

ARP_GMP Messages

Error Message     
 
    
    
   

%IP-ARP_GMP-4-WARN_EVENT Unrecoverable error in event loop. Error: [chars]

Explanation    An error (other than EINTR) occured in the event loop. The process must exit.

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     
 
    
    
   

%IP-ARP_GMP-4-WARN_INIT Failure during intialization of [chars]. Error: [chars]

Explanation    A failure occurred during the initialization of the process. This resulted in the restart of the process.

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.

ARP Messages

Error Message     
 
    
    
   

%IP-ARP-3-ERR_CACHE [chars] [chars] [chars] ([chars],[chars])

Explanation    ARP has overwritten an interface entry with a static or alias entry. This indicates a conflict with the IP address configuration on the interface.

Recommended Action    Reconfigure the static ARP entry or the conflicting interface IP address. If this does not help then do the following. 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     
 
    
    
   

%IP-ARP-4-WARN_CONN Failed to connect to [chars]. Unable to retry: [chars]

Explanation    The connection from ARP to the specified service has failed and cannot be recovered. In this situation ARP restarts and this should resolve the problem.

Recommended Action    If ARP does not restart and resolve the problem automatically then do the following. 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     
 
    
    
   

%IP-ARP-4-WARN_INIT Failed to initialize [chars]: [chars]

Explanation    The ARP process failed to initialize correctly. In this situation ARP restarts, but ARP may not recover if there is a persistant error in the IOSXR system and ARP is later unable to reestablish its connections and initialize successfully.

Recommended Action    If ARP does not restart and automatically recover, do the following. 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     
 
    
    
   

%IP-ARP-4-WARN_MEDIA [chars] [chars]

Explanation    ARP failed to load and initialize a dynamic library that it requires.

Recommended Action    Restart the ARP process. If this does not resolve the problem then do the following. 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     
 
    
    
   

%IP-ARP-4-WARN_REGISTER Failed to register [chars]: [chars]

Explanation    Registration for an IOSXR service failed during ARP's operation. This may indicate a connection failure with the IOSXR service as indicated in the error message. In this situation, ARP restarts, and this may resolve the problem.

Recommended Action    If ARP does not restart and automatically recover, do the following. 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     
 
    
    
   

%IP-ARP-4-WARN_THREAD Failed to create process thread for [chars]: [chars]

Explanation    ARP has failed to create a thread for the specified process. In this situation ARP restarts and this should resolve the problem.

Recommended Action    If ARP does not restart and automatically recover, do the following. 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     
 
    
    
   

%IP-ARP-4-WARN_WAIT Error occurred while waiting for [chars]: [chars]

Explanation    An error occurred while waiting for the specified event. In this situation the process will terminate and ARP restarts.

Recommended Action    If ARP does not restart and automatically recover, do the following. 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     
 
    
    
   

%IP-ARP-6-INFO_DUPADDR Duplicate IP address [chars] on , sourced by [chars]

Explanation    A peer device is configured with the same interface IP address.

Recommended Action    Change the interface IP address of one of the two devices.

Error Message     
 
    
    
   

%IP-ARP-6-INFO_DUPMAC Duplicate MAC address [chars]

Explanation    ARP request received with the same destination MAC address as incoming interface MAC address.

Recommended Action    Change the interface MAC address of one of the two devices.

Error Message     
 
    
    
   

%IP-ARP-6-INFO_IF_MISMATCH Selected outgoing interface for [chars] differs from incoming interface

Explanation    An ARP packet was received from an unexpected interface. This can happen due to misconfiguration of the IP addresses on the participating devices or due to incorrect bridging configuration.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%IP-ARP-6-INFO_MAC Failed to add multicast MAC address [chars]

Explanation    The specified MAC address is invalid as it is a multicast address - the most significant bit is set. Configuration has therefore been rejected.

Recommended Action    Configure the MAC address so that the most significant bit is not set.

DOMAIN_SERVICES Messages

Error Message     
 
    
    
   

%IP-DOMAIN_SERVICES-3-ATTACH_HANDLER Failed to attach an [chars] handler: [chars]

Explanation    The domain_services process failed to attach an event handler to receive event messages sent to it.

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     
 
    
    
   

%IP-DOMAIN_SERVICES-3-BIND_SYSDB Failed to connect to SysDB: [chars]

Explanation    The domain_services process failed to bind to SysDB server.

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     
 
    
    
   

%IP-DOMAIN_SERVICES-3-CREATE_CHANNEL Failed to create a channel for [chars]

Explanation    The domain_services process failed to create a channel so that other processes can send event messages to it.

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     
 
    
    
   

%IP-DOMAIN_SERVICES-3-CREATE_CHUNK Failed to allocate chunk memory for [chars]

Explanation    The domain_services process failed to create chunk memory for its domain name, domain address and domain alias data structures.

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     
 
    
    
   

%IP-DOMAIN_SERVICES-3-CREATE_EVENT_CONN Failed to create a event connection structure: [chars]

Explanation    The domain_services process failed to create and initialize an event connection structure. If the connection ever goes away, event connection manager will automatically tries to re-connect.

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     
 
    
    
   

%IP-DOMAIN_SERVICES-3-CREATE_TIMER [chars]: [chars]

Explanation    The domain_services process failed to create and initialize its various managed timers.

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     
 
    
    
   

%IP-DOMAIN_SERVICES-3-EDM_SERVER [chars]: [chars]

Explanation    Error in the domain edm server.

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     
 
    
    
   

%IP-DOMAIN_SERVICES-3-END_PROC Unexpected process termination: [chars]

Explanation    The domain_services process was terminated unexpectedly.

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     
 
    
    
   

%IP-DOMAIN_SERVICES-3-GET_COID Failed to get SysDB connection id: [chars]

Explanation    The domain_services process failed to obtain the connection id for an SysDB event connection.

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     
 
    
    
   

%IP-DOMAIN_SERVICES-3-OPEN_EVENT_CONN Failed to open a event connection to [chars]: [chars]

Explanation    The domain_services process failed to open a event connection.

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     
 
    
    
   

%IP-DOMAIN_SERVICES-3-REGISTER_DEBUG Failed to register for debugging events: [chars]

Explanation    The domain_services process failed to register for notification of changes to the domain_services debug flag(s).

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     
 
    
    
   

%IP-DOMAIN_SERVICES-3-REGISTER_EVM Failed to register handlers for SysDB events: [chars]

Explanation    The domain_services process failed to register its verification and apply handlers for SysDB events.

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     
 
    
    
   

%IP-DOMAIN_SERVICES-3-REGISTER_RPC Failed to register for RPC service

Explanation    The domain_services process failed to register its RPC server with the RPC portmapper.

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     
 
    
    
   

%IP-DOMAIN_SERVICES-3-SYSMGR_PROC_READY Domain services failed to notify the completion of init: [chars]

Explanation    domain services failed to notify the compltetion of initialization

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     
 
    
    
   

%IP-DOMAIN_SERVICES-7-REGISTER_CERRNO Failed to register process's specific error codes: [chars]

Explanation    The domain_services process failed to register its specific cerrno codes and messages.

Recommended Action    Debug message only. No action is required.

IEP Messages

Error Message     
 
    
    
   

%IP-IEP-3-FAILED_INTERNAL_DAEMON Internal Error: call to function '[chars]' by iep daemon failed

Explanation    An internal error has occurred which prevents the iep daemon from continuing.

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     
 
    
    
   

%IP-IEP-3-INTERNAL_ERROR Call to [chars] from function [chars] returned error

Explanation    An internal system error occured.

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

%IP-IEP-3-INTERNAL_ERROR2 Call to [chars] from function [chars] returned error: [chars]

Explanation    An internal system error occured.

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

%IP-IEP-7-FAILED_SYSDB_DAEMON Call to '[chars]' from function '[chars]' returned error:'[chars]'

Explanation    An error occurred while using SysDB.

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

%IP-IEP-7-FAILED_SYSDB_LIBRARY Call to '[chars]' from function '[chars]' returned error:'[chars]'

Explanation    An error occurred while using SysDB.

Recommended Action    Debug message only. No action is required.

IP_ARM_PLIB Messages

Error Message     
 
    
    
   

%IP-IP_ARM_PLIB-3-EVENT_SET_RETRY_FAILED Event set retry failed, error : [chars]

Explanation    A call to set the retry timeout for producers to bind with iparm failed. This will call default timeout values to be used.

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.

IP_ARM_TEST Messages

Error Message     
 
    
    
   

%IP-IP_ARM_TEST-6-RCVD_UPDATE [chars]

Explanation    Update received

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.

IP_ARM Messages

Error Message     
 
    
    
   

%IP-IP_ARM-3-BAD_VISIBLE_COUNT Interface '[chars]' has more visible addresses than the stored visible count '[dec]'

Explanation    This is an internal error. It indicates that the addresses visible to the clients are more than expected. This can result in IP ARM not sending an address update to its clients.

Recommended Action    Get the output of show tech-support, show arm [ipv4/ipv6] trace, running coredump of the process. Unconfiguring, reconfiguring the interface may help in recovering the from error.

Error Message     
 
    
    
   

%IP-IP_ARM-3-CFLCT_FORCED_DOWN The [chars] address [chars]/[dec] on [chars] conflicts with other [chars] addresses and has been forced down

Explanation    The specified IP address conflicts with other IP addresses on the network portion of their IP addresses and has been forced down to prevent multiple operational conflicting IP addresses. This is an inconsistent configuration.

Recommended Action    Reconfigure the IP addresses that share the common network portion specified.

Error Message     
 
    
    
   

%IP-IP_ARM-3-CFLCT_NOT_FOUND Conflict data structure not found for ([chars])

Explanation    An IP info structure with conflict flag set is not found in the conflict database. This is an error condition indicating IP ARM database has erroneous information. This can cause some unexpected behavior relating to the ip address not found in the database.

Recommended Action    Collect the output of show tech-support, show arm [ipv4/ipv6] trace and the steps that lead to this behavior.

Error Message     
 
    
    
   

%IP-IP_ARM-3-MHOST_DEFAULT_PIM An error occured with the default interface provided by PIM: [chars]

Explanation    When multicast routing is turned on PIM will choose a default interface, based on whether the default has been configured and it's enabled state. An error was encountered in making PIM provided interface as mhost default interface.

Recommended Action    Change the mhost ipv4 default-interface configuration to some other physical or virtual interface. Collect the output of show tech-support, show arm ipv4 trace

Error Message     
 
    
    
   

%IP-IP_ARM-3-UNNUM_CFLCT The [chars] unnumbered interface [chars] references the unnumbered interface [chars] and has therefore been forced down

Explanation    The IP unnumbered specified in the message references another unnumbered interface. This is not consistent configuration.

Recommended Action    Reconfigure one of the IP unnumbered interfaces so that the unnumbered interface does not reference another unnumbered interface.

Error Message     
 
    
    
   

%IP-IP_ARM-6-CFGED_MHOST_DEFAULT_MGMT The configured mhost default interface([chars]) is a management interface, so, can't be used as the active

Explanation    Management interfaces(on the RPs) are not allowed to be the mhost default interface as multicast routing is disabled on the management interface.

Recommended Action    Change the mhost ipv4 default-interface configuration to some other physical or virtual interface.

Error Message     
 
    
    
   

%IP-IP_ARM-6-CFLCT_NO_LONGER The [chars] address [chars]/[dec] on [chars] is no longer forced down due to [chars] address conflicts

Explanation    The IP address specified in the message previously conflicted with other configured IP addresses on some portion of the network portion of their IP addresses. The IP address no longer conflicts.

Recommended Action    None. This is an informational message indicating a return to a correct consistent configuration.

Error Message     
 
    
    
   

%IP-IP_ARM-6-RTRID_GLOBAL_UNAVAILABLE The global router id has become unavailable

Explanation    The global router id has become unavailable.

Recommended Action    Ensure that a global router id has been configured and that the configured interface has a primary IPv4 address and is UP (a loopback interface is strongly recommended), or that the configured IPv4 address exists on an interface that is UP.

Error Message     
 
    
    
   

%IP-IP_ARM-6-UNNUM_CFLCT_NO_LONGER The [chars] unnumbered interface [chars] no longer references another unnumbered interface

Explanation    The IP unnumbered specified in the message references previously referenced another unnumbered interface. This is no longer the case.

Recommended Action    None. This is an informational message indicating a return to a correct consistent configuration.

Error Message     
 
    
    
   

%IP-IP_ARM-7-ERR_SYSDB_BIND Encountered failure [chars] in binding to [chars] for [chars]

Explanation    IP ARM process encountered failure in binding to SysDB. It will recover itself by restarting. Typically this error is caused if sysdb is unavailable for an extended period.

Recommended Action    If the problem persists get the output of show processes, show sysdb trace, show sysdb trace clientlib job , show arm [ipv4/ipv6] trace from the location the error message comes from.

Error Message     
 
    
    
   

%IP-IP_ARM-7-INIT_FAILED Initialization failed, module: [chars], operation: [chars], error: [chars]

Explanation    Initialization of the IPv4 ARM or IPv6 ARM process failed. This can happen when the process is (re)starting and any basic infrastructure service required by the process is not available. The process recovers by restarting itself. If the error message doesn't persist, it can be ignored. If the error message persists, depending on whether IPv4 ARM or IPv6 ARM failed to initialize, some basic ipv4 or ipv6 functionality may not be available.

Recommended Action    Collect the output of show tech-support, show processes, show arm [ipv4/ipv6] trace

Error Message     
 
    
    
   

%IP-IP_ARM-7-LTRACE_INIT_ERR Failed to initialize ltrace: [chars]:

Explanation    IP ARM failed to initialize module to allow tracing of important events. This may happen during process (re)start. The process will exit and try to recover from the error.

Recommended Action    If the msg is not seen multiple times, it can be assumed that the process has recovered. If the process cannot recover from this error, it may not be able to run. Then it is a fatal error. Collect the output of show tech-support, show arm [ipv4/ipv6] trace.

IPV4_EDM Messages

Error Message     
 
    
    
   

%IP-IPV4_EDM-3-DECODE_FAILED Failed to decode [chars] data

Explanation    IPV4 could not decode data supplied by the indicated external data manager.

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     
 
    
    
   

%IP-IPV4_EDM-3-ENCODE_FAILED Failed to encode [chars] data in external data manager

Explanation    A process has requested information from ipv4_io through SysDB, probably as a result of executing a show command. The data requested could not be encoded.

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     
 
    
    
   

%IP-IPV4_EDM-3-SYSDB_BIND_FAILED Failed to connect to SysDB in [chars] ([chars])

Explanation    Failed to connect to SysDB while starting the indicated subsystem.

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     
 
    
    
   

%IP-IPV4_EDM-6-BAGREG_FAILED IPV4_IO failed to register the [chars] external data manager data blocks

Explanation    The ipv4_io process failed while attempting to register the indicated external data manager data blocks with SysDB.

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     
 
    
    
   

%IP-IPV4_EDM-7-ERR_BAG_REG Encountered failure [chars] in [chars]

Explanation    IPV4 Management Agent encountered failure in registering bag format used to encode information sent via SysDB. It will recover itself by restarting.

Recommended Action    If the problem persists get the output of show processes, show sysdb trace edm, show sysdb trace clientlib job . If multiple instances of ipv4_ma are seen running or trying to run

Error Message     
 
    
    
   

%IP-IPV4_EDM-7-ERR_SYSDB_BAG_ENCODE Failure [chars] in encoding bag for [chars]

Explanation    IPv4 Management Agent encountered failure in encoding the bag that is supposed to carry encoded information to be passed on clients of IPv4 MA. Typically the client is a managebility agent like exec spawned by show CLI. As a result of this error the client may not receive the intended information from IPv4 MA. If it is a managebility request that triggered this, the request may be retried. Typically this error is caused if there is mismatch between the bag format and the information to be encoded. At other times the error might be due to process' memory corruption or low memory.

Recommended Action    Collect the output of show tech-support, show ipv4 ma trace location when this message is seen. Identify if possible which manageability requests triggers this message. Most likely it would be one of the show ipv4 CLIs.

Error Message     
 
    
    
   

%IP-IPV4_EDM-7-ERR_SYSDB_REG_EDM [chars] Failed with [chars]

Explanation    IPv4 Management Agent encountered failure in registering as a server for managebility requests. It will recover itself by restarting. Typically this error is caused if sysdb is unavailable for an extended period or if there is another process that instance that is registered as the server for the same information.

Recommended Action    If the problem persists get the output of show processes, show sysdb trace edm, show sysdb trace clientlib job . If multiple instances of ipv4_ma are seen running or trying to run (this can be due to a bug in some other area of the system), make sure that only one instance is allowed by killing the other one.

IPV4_IO Messages

Error Message     
 
    
    
   

%IP-IPV4_IO-3-NOMEM IPv4 operation '[chars]' failed due to lack of memory

Explanation    The IPv4 IO process could not allocate memory needed to complete the specified operation.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. When the memory shortage is resolved retry the operation.

Error Message     
 
    
    
   

%IP-IPV4_IO-3-OPTION_UPDATE_FAIL Cannot update option registry in ipv4_io: [chars]

Explanation    The ipv4_io process encountered a software error while creating an entry in the option registry requested by an application

Recommended Action    IPV4 IO could not update option registry information consistently across all of its instances. This could result in unexpected behavior with respect to some option packets. 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     
 
    
    
   

%IP-IPV4_IO-3-PA_BIND Port arbitrator error. [chars]: [chars]

Explanation    The ipv4_io process encountered a software error while connecting to the port arbitrator.

Recommended Action    IPv4 IO could not register with the PA for handling a particular ICMP type locally. 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     
 
    
    
   

%IP-IPV4_IO-3-PA_NULL_HANDLE Error: Port Arbtitrator allocated a NULL handle

Explanation    The ipv4_io process was given a NULL handle by the port arbitrator.

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

Error Message     
 
    
    
   

%IP-IPV4_IO-3-PLATFORM_UPDATE Platform update failed: [chars] - [chars]()

Explanation    An error occurred while trying to update the platform code with information about the interface whose handle is contained in the message.

Recommended Action    The update will be replayed to the platform code and may succeed on a subsequent attempt. If not then the system will be left in an inconsistant state and this interface may not function normally. 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     
 
    
    
   

%IP-IPV4_IO-3-PLATFORM_UPDATE_BULK Platform update failed for [dec] interface: [chars] - [chars]

Explanation    An error occurred while trying to update the platform code with information about a batch of interfaces. This update will be replayed.

Recommended Action    The update will be replayed to the platform code and may succeed on a subsequent attempt. If not then the system will be left in an inconsistant state and the affected interfaces may not function normally. 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     
 
    
    
   

%IP-IPV4_IO-3-UNHANDLED_ERROR Error. [chars]: [chars]

Explanation    The ipv4_io process has encountered a software error during normal operation from which it cannot recover.

Recommended Action    The process will attempt to rectify this situation by restarting. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise check whether the error code contained in the message indicates that there was a failure to allocate the necessary memory and take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If resource allocation was not the problem and it hasn't been fixed by a subsequent restart then take the following 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     
 
    
    
   

%IP-IPV4_IO-4-UNKNOWN_MESSAGE Unknown [chars] received by ipv4_io ([dec])

Explanation    The IPV4_IO process has received an unknown event message.

Recommended Action    This message indicates that the ipv4_io process has received a message type that it wasn't expecting. This message has been ignored and no further action needs to be taken. The message may have been sent to this process by mistake or if any installs have taken place there may be a version mismatch between the server and a client. On its own this message does not indicate a problem. If other problems are seen then include this error in the report.

Error Message     
 
    
    
   

%IP-IPV4_IO-7-INIT_FAILED Process initialisation failed. [chars]: [chars]

Explanation    There was a software error during process startup.

Recommended Action    The process will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise check whether the error code contained in the message indicates that there was a failure to allocate the necessary memory and take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If resource allocation was not the problem and it hasn't been fixed by a subsequent restart then take the following 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.

IPV4_MA Messages

Error Message     
 
    
    
   

%IP-IPV4_MA-3-ADD_GROUP_FAILED IP add multicast group membership failed for group [chars] on interface

Explanation    IPv4 was unable to add membership to the group. Commonly, this is done for 224.0.0.1 by ipv4-ma with no associated socket when an interface is enabled, or for all groups (multicast promiscuous mode) whem multicast routing is enabled. Failure might result in issues in multicast host functionality or multicast fwding functionality.

Recommended Action    shut/unshut of the interface will trigger leave/join respectively. This can be done to retry the group join. Collect the output of show tech-support, show ipv4 ma trace, show ipv4 trace, debug ipv4 ma mhost from the location the error message comes from. Note any previous errors related to multicast membership. 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     
 
    
    
   

%IP-IPV4_MA-3-ERR_AVLBL_MTU Proposed IP MTU [dec] of [hex] is smaller than minimum allowed (68). IPv4 may not work correctly on this interface

Explanation    Minimum IPv4 MTU must be 68 bytes. Available link MTU is below the minimum IPv4 link MTU (68). IPv4 may not work correctly on this interface.'

Recommended Action    Adjust the lower layer mtu such that atleast 68 bytes is available to IPv4. If the lower layer mtu is big enough collect the output of show tech-support, show ipv4 ma trace, show im trace, show im chains, show ipv4 interface for the interface for which the above error is seen. Try unconfiguring/reconfiguring the interface if the lower layer mtu is big enough and still the error is seen.

Error Message     
 
    
    
   

%IP-IPV4_MA-3-ERR_IFH_MISMATCHED ifhandles mismatched, IM ifh=[hex], MA ifh=[hex]

Explanation    A mismatch in interface handles has been been detected. This is an indication that IM is potentially out-of-synched with MA. This problem occurs when interfaces are deleted while Interface Manager (IM) is not available.

Recommended Action    The problem is normally recovered by the IPV4-MA component. 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     
 
    
    
   

%IP-IPV4_MA-3-REMOVE_GROUP_FAILED IP remove multicast group membership failed for group [chars] on interface

Explanation    IPv4 was unable to remove membership to the group. Commonly, this is done for 224.0.0.1 by ipv4-ma with no associated socket when an interface is disabled, or for all groups (multicast promiscuous mode) whem multicast routing is disabled. It might be ok to ignore the failure.

Recommended Action    shut/unshut of the interface will trigger leave/join respectively. Do as appropriate to recover. Collect the output of show tech-support, show ipv4 ma trace, show ipv4 trace, debug ipv4 ma mhost from the location the error message comes from. Note any previous errors related to multicast membership. 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     
 
    
    
   

%IP-IPV4_MA-7-ERR_CREATE_REGISTER Failed to register create notification for interface [chars] ([chars]: [chars])

Explanation    IPv4 MA registers to be notified of Forwarder interface creation if its not already available when IPv4 MA starts. The process tries to recover by reconnecting to IM. If the error persists, the forwarder will not be available for IPv4 packets.

Recommended Action    Collect the output of show tech-support, show ipv4 ma trace, debug ipv4 ma error, debug im errors, debug im api calls job , debug im api errors job from the location the error message comes from.

Error Message     
 
    
    
   

%IP-IPV4_MA-7-ERR_EVM_ASYNC_ATTACH Failure [chars] in attaching handler for async pulse [hex]

Explanation    The IPv4 MA process could not register the handler for the indicated event. This can happen when the process is (re)starting. The process recovers by restarting itself. If the error message doesn't persist, it can be ignored. If the error message persists, some basic ipv4 functionality may not be available.

Recommended Action    Collect the output of show tech-support, show processes, show ipv4 ma trace, debug event-manager attach job from the location the error message comes from. 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     
 
    
    
   

%IP-IPV4_MA-7-ERR_EVM_ATTACH Failure [chars] in attaching handler for sync msgid [hex]

Explanation    The IPv4 MA process could not register the handler for the indicated event. This can happen when the process is (re)starting. The process recovers by restarting itself. If the error message doesn't persist, it can be ignored. If the error message persists, some basic ipv4 functionality may not be available.

Recommended Action    Collect the output of show tech-support, show processes, show ipv4 ma trace, debug event-manager attach job from the location the error message comes from. 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     
 
    
    
   

%IP-IPV4_MA-7-ERR_EVM_CREATE Failure [chars] in creating event manager

Explanation    The IPv4 MA process could not create the event manager to handle the events to be received by the process. This can happen when the process is (re)starting. The process recovers by restarting itself. If the error message doesn't persist, it can be ignored. If the error message persists, some basic ipv4 functionality may not be available.

Recommended Action    Collect the output of show tech-support, show processes, show ipv4 ma trace from the location the error message comes from. 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     
 
    
    
   

%IP-IPV4_MA-7-ERR_FINT_NAME Failed to get interface name of local fint ([chars])

Explanation    Failed to add ipv4 to fint which represents the fabric interface. This is retried by reconnecting to IM. If this error is seen only once, it may not have significant impact. If this error is persistent, it may mean that it is not possible to send/receive packets vai the fabric.

Recommended Action    Collect the output of show ipv4 ma trace, debug ipv4 ma error from the location the error message comes from. 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     
 
    
    
   

%IP-IPV4_MA-7-ERR_SYSDB_BIND Encountered failure [chars] in binding to [chars] for [chars]

Explanation    IPv4 Management Agent encountered failure in binding to SysDB. It will recover itself by restarting. Typically this error is caused if sysdb is unavailable for an extended period.

Recommended Action    If the problem persists get the output of show processes, show sysdb trace, show sysdb trace clientlib job , show ipv4 ma trace location from the location the error message comes from.

Error Message     
 
    
    
   

%IP-IPV4_MA-7-ERR_SYSDB_REG_NOTIFY Encountered failure [chars] in registering notifiee at [chars] for [chars]

Explanation    IPv4 Management Agent encountered failure in registering notifiee with SysDB. It will recover itself by restarting. Typically this error is caused if sysdb is unavailable for an extended period.

Recommended Action    If the problem persists get the output of show processes, show sysdb trace, show sysdb trace clientlib job , show ipv4 ma trace location , debug sysdb notification job from the location the error message comes from.

Error Message     
 
    
    
   

%IP-IPV4_MA-7-ERR_SYSDB_REG_VERIFY Encountered failure [chars] in registering verifier at [chars] for [chars]

Explanation    IPv4 Management Agent encountered failure in registering verifier with SysDB. It will recover itself by restarting. Typically this error is caused if sysdb is unavailable for an extended period.

Recommended Action    If the problem persists get the output of show processes, show sysdb trace, show sysdb trace clientlib job , show ipv4 ma trace location , debug sysdb verification job from the location the error message comes from.

Error Message     
 
    
    
   

%IP-IPV4_MA-7-INIT_FAILED Cannot initialize [chars]: [chars] ([hex])

Explanation    Initialization of the IPv4 MA process failed. This can happen when the process is (re)starting and any basic infrastructure service required by the process is not available. The process recovers by restarting itself. If the error message doesn't persist, it can be ignored. If the error message persists, some basic ipv4 functionality may not be available.

Recommended Action    Collect the output of show tech-support, show processes, show ipv4 ma trace from the location the error message comes from.

Error Message     
 
    
    
   

%IP-IPV4_MA-7-REPLICATE_DPC_INVALID_COOKIE Got invalid cookie for replicating interface , cookie - [hex], batch cookie [hex]

Explanation    IPv4 MA got an unexpected cookie for the specified interface. This failure indicates that the IPv4 data path feature may not programmed correctly. IPv4 MA tries to recover from this error by a timer based retry. If the message is not seen continuosly for a particular interface and if functionality looks ok, the recovery might have been successful.

Recommended Action    Collect the output of show tech-support, show ipv4 ma trace, debug imp dpc, debug ipv4 events, debug im api job from the location the error message comes from. 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     
 
    
    
   

%IP-IPV4_MA-7-UNKNOWN_MESSAGE Unknown IPC [chars] [dec] received

Explanation    The IPV4_MA process has received an unknown IPC. It will ignore the msg if it is in the form of an asynchronous pulse. If the msg is in the form of a synchronous message, it returns an error to the sender which in turn is expected to take appropriate action. This can happen if IPv4 MA receives an IPC for which it doesn't have a handler registered due to either it unregistering the handler without updating the sender or due to the sender sending an incorrect IPC. It may be safe to ignore this message if there is no visible loss of functionality.

Recommended Action    Collect the output of show tech-support, show processes, show ipv4 ma trace, show lwm from the location the error message comes from. If this message is seen repeatedly, capture the output of debug event-manager dispatch job . This debug captures almost all the IPCs received by ipv4 ma and hence it may slow down the process and take up the related resources. 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.

IPV6_MA Messages

Error Message     
 
    
    
   

%IP-IPV6_MA-2-PROT_DOWN IPv6 protocol on interface [chars] going down, Reason - [chars]

Explanation    The IPv6 Protocol on the mentioned interface is going down due to the reason specified in the message. This would cause all routing and forwarding on this interface to be disabled for ipv6 address family until the condition is rectified either via config or help from support.

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     
 
    
    
   

%IP-IPV6_MA-3-ADD_GROUP_FAILED IP add multicast group membership failed for group [chars] on [chars]

Explanation    Unable to add membership to the group.

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     
 
    
    
   

%IP-IPV6_MA-3-ERR_ADDRSVR_INIT Failed to initialize as Address Svr. Error -- [chars]

Explanation    Failed to initialize as local IP Address Server

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     
 
    
    
   

%IP-IPV6_MA-3-ERR_CONFIG_INIT IPV6 MA failed to initialize the configuration sub-system

Explanation    The IPV6 MA process failed to initialize its config handling mechanism and interaction with sysdb.

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     
 
    
    
   

%IP-IPV6_MA-3-ERR_DB_INIT IPV6 MA failed to initialize the interface database

Explanation    The IPV6 MA process failed to initialize its interface 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     
 
    
    
   

%IP-IPV6_MA-3-ERR_DEBUG_INIT IPV6 MA debug initialization failed

Explanation    The IPV6 MA process failed to initialize debug support

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     
 
    
    
   

%IP-IPV6_MA-3-ERR_INIT Failed to initialize [chars], Error -- [chars]([dec])

Explanation    Failed to initialize as producer of the Local Address Service 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     
 
    
    
   

%IP-IPV6_MA-3-ERR_LAS_P_INIT Failed to initialize as LAS producer. Error -- [chars]

Explanation    Failed to initialize as producer of the Local Address Service 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     
 
    
    
   

%IP-IPV6_MA-3-ERR_LL_CFG [chars]: ([chars])

Explanation    This might result in failure generating linklocal address on certain LC.

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     
 
    
    
   

%IP-IPV6_MA-3-ERR_LTRACE_INIT_FAIL [chars] [chars] [chars]

Explanation    There was a failure during an ltrace_init api call which resulted in the failure as indicated in the message text.

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     
 
    
    
   

%IP-IPV6_MA-3-ERR_MTU [chars] [dec]:

Explanation    Minimum IPv6 MTU must be 1280. Available ipv6 mtu is not within the valid range.

Recommended Action    Adjust the lower layer mtu such that atleast 1280 bytes is available to ipv6.

Error Message     
 
    
    
   

%IP-IPV6_MA-3-ERR_REMOVE_ENCAP Failed to remove [chars] encapsulation from [chars] ([chars])

Explanation    --

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     
 
    
    
   

%IP-IPV6_MA-3-ERR_SETUP_HANDLERS IPV6 MA failed to initialize event callback handlers

Explanation    The IPV6 MA process failed to initialize various callback handlers for various synchronous and asynchronous events.

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     
 
    
    
   

%IP-IPV6_MA-3-ERR_TIMER_ADDL_CTXT [chars] ([chars])

Explanation    The IPV6 MA process failed to add context to timer.

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     
 
    
    
   

%IP-IPV6_MA-3-ERR_TIMER_INIT IPV6 MA Timer initialization failed - [chars]

Explanation    The IPV6 MA process failed to initialize its timers.

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     
 
    
    
   

%IP-IPV6_MA-3-EVENT_CONN_ERR IPV6 MA Event Conn Error - [chars] ([chars])

Explanation    The IPV6 MA process failed to initialize its event conn mgr infra.

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     
 
    
    
   

%IP-IPV6_MA-3-EVENTMGR_CREATE_FAILED IPV6_MA Event Manager create failed

Explanation    The IPV6_MA process failed to create the event manager.

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     
 
    
    
   

%IP-IPV6_MA-3-REMOVE_GROUP_FAILED IP remove multicast group membership failed for group [chars] on [chars]

Explanation    Unable to add membership to the group.

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     
 
    
    
   

%IP-IPV6_MA-3-SYSDB_BIND_FAILED Failed to connect to SysDB in [chars] ([chars])

Explanation    Failed to connect to SysDB while starting the indicated subsystem.

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     
 
    
    
   

%IP-IPV6_MA-6-ERR_IM IM API Failure ([chars]) : [chars]

Explanation    --

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.

IPV6_ND Messages

Error Message     
 
    
    
   

%IP-IPV6_ND-3-ADDRESS_DUPLICATE Duplicate address [chars] has been detected

Explanation    Address duplication has been detected. This error is caused by a a mis-configuration. More than one system, connected to the same media, are configured with the same ip address. Once an address is found to be duplicated, it is set in DUPLICATE state and is not available for use by upper layers. If the duplicated address is a Link Local address, then the ipv6 interface is also taken to DOWN state.

Recommended Action    Unconfigured the duplicated address and reconfigure with a correct one. If the address is a Link Local address, perform a 'shut' and then 'no shut' on the interface.

Error Message     
 
    
    
   

%IP-IPV6_ND-3-ERR_AIB_ADJ Unable to [chars] adjacency [chars] AIB.

Explanation    A problem occurred while attempting to add/delete an adjacency into/from AIB. This error happens when the AIB process is temporarily unavailable. The problem is normally recovered once the AIB process becomes operational.

Recommended Action    'show adjacency ipv6 [location node-id]' and 'show ipv6 neighbor [location node-id] commands. Entries in AIB should match with ND's. If the etries don't match then the router may not function correctly or efficiently. 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     
 
    
    
   

%IP-IPV6_ND-3-ERR_AIB_CONN Unable to [chars] a connection to AIB [chars] ([dec])

Explanation    The attempt to communicate with AIB failed. This is normally a transient error, it occurs when the AIB process is temporarily unavailable. The error will be recovered once the AIB process becomes operational. If the error persists, it is an indication that the AIB process is not operational or being blocked by other process.

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     
 
    
    
   

%IP-IPV6_ND-3-ERR_EVENT_MGR_CREATE [chars] unable to create the event manager.

Explanation    IPv6 ND has failed to create the event manager. It will try to recover from the error by exiting.

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     
 
    
    
   

%IP-IPV6_ND-3-ERR_EXTERNAL_FAIL [chars] [chars] (err=[chars])

Explanation    An error in the system trace facility has occurred. This condition might have been caused by lack of system resources. The error will disable IPV6 Neighbor Discovery's tracing function, but no other IPv6 ND fuctionalities will be impacted.

Recommended Action    Use 'show memory summary [location ]' command to determine the state of the system memory. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%IP-IPV6_ND-3-ERR_IFH_CONN Unable to [chars] connection handle to IFH [chars] ([dec])

Explanation    The attempt to communicate with IFH server failed. This is normally a transient error, it occurs when IFH server process is temporarily not available. If the error persists, it is an indication that the ifh server process is not operational.

Recommended Action    Use 'show proc pfi_ifh_server [location node-id]' to find out the state of the IFH server process. Also, use 'show proc blocked [loc node-id' to determine if the pfi_ifh_server process is being blocked. 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     
 
    
    
   

%IP-IPV6_ND-3-ERR_IM_BIND Failed to bind to IM ([chars]): [chars] ([dec])

Explanation    The attempt to communicate with IM failed. This is normally a transient error, it occurs when Interface Manager is temporarily not available. If the error persists, it is an indication that the interface manager process is not operational or it is being blocked by some other process.

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     
 
    
    
   

%IP-IPV6_ND-3-ERR_IM_MEDIA_NOT_SUPPORTED [chars] [chars]

Explanation    IPv6 Neighbor Discovery (ND) does not operate on this interface type. This error occurs when ND process receives a punted data packet from the L2 for MAC address resolution on a point-to-point interface. This problem could happen due to some transient errors in the layer-2 switching software.

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     
 
    
    
   

%IP-IPV6_ND-3-ERR_SYSDB Failed to [chars]: [chars] ([dec])

Explanation    An attempt to communicate with sysdb failed. This error is normally transient and could be recovered. If the error condition could not be recovered, IPv6 ND will not function properly.

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.

IPV6_SW Messages

Error Message     
 
    
    
   

%IP-IPV6_SW-3-CLEAR_MAPPING_FAILED clear mapping ipv6 ([dec]) from media [chars] failed: [chars]

Explanation    --

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     
 
    
    
   

%IP-IPV6_SW-3-ERR_ATTACH_FSV couldn't attach FSV, err: [chars]

Explanation    The IPv6 NetIO component was unable to attach the required FSV before passing the packet to the IPv6 partner process. The Packet was dropped.

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     
 
    
    
   

%IP-IPV6_SW-3-ERR_MEDIA_REGISTER [chars] : Failed for ipv6 proto to [chars] ([chars])

Explanation    netio media register or callback error.

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     
 
    
    
   

%IP-IPV6_SW-3-ERR_NETIO_MUTEX_LOCK Cannot lock packet mutex in function [chars], err: [chars]

Explanation    The IPv6 NetIO component was unable to lock packet mutex while doing a control action. The control action 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     
 
    
    
   

%IP-IPV6_SW-3-ERR_NO_INTERFACE IPv6 received a packet bound to a nonexistent interface, err: [chars]

Explanation    --

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     
 
    
    
   

%IP-IPV6_SW-3-ERR_PAK_REDIRECT couldn't duplicate packet (no redirect generated), err: [chars]

Explanation    A packet has been sent to us when the sender should have been able to directly reach the destination. We were therefore also trying to generate an ICMP redirect message, but were unable to do so. The original packet would have been forwarded normally.

Recommended Action    This generally indicates a low memory condition. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%IP-IPV6_SW-3-ERR_PROTO_INIT Protocol Initialization failed, error -- [chars] ([dec])

Explanation    IPv6 Protocol failed to intialize the netio datapath.

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     
 
    
    
   

%IP-IPV6_SW-3-ERR_READ_PUNT_REASON_FAILED couldn't read punt reason, err: [chars]

Explanation    The IPv6 NetIO component was unable to read the Packet Punt Reason supplied by the Hardware forwarding component. The Packet was dropped.

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     
 
    
    
   

%IP-IPV6_SW-3-NEED_SLOW_ROUTINE IPv6 can't access pak [pointer] header in [chars] - need slow routine

Explanation    The IPv6 base header in the packet could not be directly accessed in the named routine, and hence the packet was dropped. This is due to the packet not being within the first particle or the header not being completly contained within one particle. If the slow switching routines (using pak_netio_ API calls) had been compiled in then the packet could have been switched.

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     
 
    
    
   

%IP-IPV6_SW-3-SET_MAPPING_FAILED set mapping ipv6 ([dec]) to media [chars] failed: [chars]

Explanation    --

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     
 
    
    
   

%IP-IPV6_SW-4-ERR_DEBUG_INIT A error occurred during debug initialization, err: [chars]

Explanation    The IPv6 NetIO component encountered an error during debug initialisation

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.

IPV6 Messages

Error Message     
 
    
    
   

%IP-IPV6-3-DEBUG_INIT_FAILED IPv6 IO Debug Initialisation Failed

Explanation    IPv6 IO failed to initialise debugging

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     
 
    
    
   

%IP-IPV6-3-EDM_DECODE_FAILED Failed to decode [chars] data

Explanation    IPV6 could not decode data supplied by the indicated external data manager.

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     
 
    
    
   

%IP-IPV6-3-EDM_ENCODE_FAILED Failed to encode [chars] data in external data manager

Explanation    A process has requested information from ipv6_io through SysDB, probably as a result of executing a show command. The data requested could not be encoded.

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     
 
    
    
   

%IP-IPV6-3-EDM_OPEN_FAILED Failed to open external data manager in [chars]

Explanation    While processing the indicated show command, the ipv6_io process could not connect to the SysDB server.

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     
 
    
    
   

%IP-IPV6-3-EDM_REGISTER_FAILED IPV6_IO failed to register its external data manager - [chars]

Explanation    The ipv6_io process failed when attempting to register its external data manager with SysDB.

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     
 
    
    
   

%IP-IPV6-3-ERR_ADD_ENCAP Failed to add [chars] encapsulation to [chars] ([chars])

Explanation    --

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     
 
    
    
   

%IP-IPV6-3-ERR_LTRACE_INIT_FAIL [chars] [chars] [chars]

Explanation    There was a failure during an ltrace_init api call which resulted in the failure as indicated in the message text.

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     
 
    
    
   

%IP-IPV6-3-ERR_NULL_HANDLE_ALLOC Error: Port Arbtitrator allocated a NULL handle

Explanation    Handle allocated by port arbitrator is invalid.

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     
 
    
    
   

%IP-IPV6-3-ERR_PA_BIND Couldn't bind with Port Arbitrator for local interest, error = [chars]

Explanation    A call made to pa_client_bind has 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     
 
    
    
   

%IP-IPV6-3-ERR_PA_BIND_RETVAL Error in binding [chars] for local interest with Port Arbitrator

Explanation    A certain ICMP6 type couldn't be registered with PA.

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     
 
    
    
   

%IP-IPV6-3-EVENTCONN_CREATE_FAILED IPv6 IO failed to create evm conn for [chars]: ([dec]) [chars]

Explanation    The IPv6 IO process failed to create a connection to a server

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     
 
    
    
   

%IP-IPV6-3-INIT_FAILED [chars] ([chars])

Explanation    IPv6 IO failed to initialise some services.

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     
 
    
    
   

%IP-IPV6-3-INVALID_INPUT Invalid IPv6 packet on input: [chars] (got [dec], should be [dec]), s: [chars] d: [chars]

Explanation    IPV6 received an invalid format IP packet.

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     
 
    
    
   

%IP-IPV6-3-PACKET_ERROR_DISCARD [chars], (source: [chars], destination: [chars])

Explanation    IPV6_IO discarded a packet due to the indicated error.

Recommended Action    Based on the error indicated, investigate the source of the and links for packet corruption or other errors.

Error Message     
 
    
    
   

%IP-IPV6-3-PACKETMGR_CONNECT_FAILED IPv6 IO Packet Manager connection Failed: ([dec]) [chars]

Explanation    The IPv6 IO process failed to connect to the packet manager

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     
 
    
    
   

%IP-IPV6-3-PAK_FSV_WRITE_FAILED Could not write packet specific feature vectors in [chars] ([chars], [unsigned int])

Explanation    IPv6_IO could not write the packet specific features.

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     
 
    
    
   

%IP-IPV6-3-PAK_SEND_TO_TRANSPORT_FAILED IPv6_IO could not transfer packet to the transport layer ([unsigned int], [chars])

Explanation    IPv6_IO attempted to write a packet to the transport layer and 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     
 
    
    
   

%IP-IPV6-3-STATS_SHM_INIT_FAILED Failed to initialize shm for ipv6 traffic stats

Explanation    While trying to create a shared memory object for ipv6 traffic statistics, encountered an error

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     
 
    
    
   

%IP-IPV6-3-SYSDB_BIND_FAILED Failed to connect to SysDB in [chars] ([chars])

Explanation    Failed to connect to SysDB while starting the indicated subsystem.

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     
 
    
    
   

%IP-IPV6-3-SYSDB_CONNECT_FAILED Default connection to SysDB failed ([chars], [chars])

Explanation    Could not connect to SysDB.

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     
 
    
    
   

%IP-IPV6-3-SYSDB_CREATEITEM_FAILED Failed trying to create the SysDB item [chars] ([chars])

Explanation    Failed to create an item in SysDB.

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     
 
    
    
   

%IP-IPV6-6-ERR_IM IM API Failure ([chars]) : [chars]

Explanation    --

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.

LIBIPV4 Messages

Error Message     
 
    
    
   

%IP-LIBIPV4-3-ERR_CONV_ITEM Convergence item failure ([chars]) reason - ([chars])

Explanation    An error occurred processing a BGP convergence item operation.

Recommended Action    This indicates a problem with publishing BGP convergence via sysdb. If the errors are seen continuously and you see problems with BGP covergence, do the following 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. If the error is seen only once/twice while some sysdb processes crashed or were restarted, this might be related to that and could be considered transitory.

Error Message     
 
    
    
   

%IP-LIBIPV4-7-ERR_DATALIST Helper address datalist operation failed, [chars], [chars]

Explanation    The sysdb process fails to find the address of a specified active interface or of all active interfaces.

Recommended Action    This indicates a problem with getting the helper address. If the errors are seen continuously and you see problems with the helper address, do the following 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. If the error is seen only once/twice while some sysdb processes crashed or were restarted, this might be related to that. If you don't see any issue with the helper address thereafter, it is a transitory problem.

Error Message     
 
    
    
   

%IP-LIBIPV4-7-ERR_HSSD_REG ICMP error generation failure: Failed to register with pakman for hssd use.

Explanation    For generation of ICMP error packets, the ICMP generation library needs to register for an internal packet resource called HSSD. Since, it couldn't register for that, an ICMP error couldn't be generated.

Recommended Action    This can happen while 'packet' process is restarting and a couple of instances of the message can be ignored in that case. If there is no restart and problems are being seen with the router not being able to send ICMP errors, do the following 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.

LIBIPV4PROTO Messages

Error Message     
 
    
    
   

%IP-LIBIPV4PROTO-6-PAKHDR Failed to read IP header in packet (hl = [dec], read = [dec])

Explanation    There was a problem reading the full IP header for a packet being sent. The packet would be dropped.

Recommended Action    Do the following 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     
 
    
    
   

%IP-LIBIPV4PROTO-6-PAKHDR_ERROR Failed to read IP header - [chars]: [chars]

Explanation    There was a problem with reading the IP header in the packet, so, can't process it.

Recommended Action    Do the following 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     
 
    
    
   

%IP-LIBIPV4PROTO-7-GET_PAK_HDR_COUNT [chars]: [chars]

Explanation    There was a problem while getting total packet header count for this node.

Recommended Action    This could happen if there is a problem with packet shared memory on the node. The transport would restart in this situation, if it restarts once or twice and then recovers, then it could be a transient problem and no action is required. If the transport keeps restarting, do the following 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     
 
    
    
   

%IP-LIBIPV4PROTO-7-PLIB_INIT [chars]: [chars]

Explanation    There was a problem initializing the IPv4 protocol library within a transport process. The message indicates what part of the initialization failed.

Recommended Action    Transport processes might restart due to this initialization failure. If this error message is seen just once when multiple processes restart, then it can be considered transient and ignored. If the message is seen multiple times and the transport has restarted too many times, do the following 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.

LIBIPV6PROTO Messages

Error Message     
 
    
    
   

%IP-LIBIPV6PROTO-3-ERR_CONNECT_IO_STATS Failed to open IO stats shared mem, [chars]

Explanation    The transport fails to open the ipv6-io stats shared 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     
 
    
    
   

%IP-LIBIPV6PROTO-3-ERR_CONNECT_RIB Failed to connect to the rib process

Explanation    The transport fails to connect to the rib process. The error occurs when the RIB process is temporarily unavailable. It is a transient error and will be recoverred once the RIB process becomes available.

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     
 
    
    
   

%IP-LIBIPV6PROTO-3-ERR_FSV_REG FSV registration failed for [chars], [chars]

Explanation    This is a transient error and it happens when the packet mamager process is temporarily unavailable.

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     
 
    
    
   

%IP-LIBIPV6PROTO-3-ERR_FSV_WRITE FSV resource busy, [chars]

Explanation    The packet FSV resources are busy and a packet FSV could not be written. It is a transient error and it could happen in a heavy loaded system.

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     
 
    
    
   

%IP-LIBIPV6PROTO-3-ERR_GET_MTU Failed to get the MTU, [chars]

Explanation    The transport fails to get the MTU from the network protocol process.

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     
 
    
    
   

%IP-LIBIPV6PROTO-3-ERR_LAS_INIT Failed IPv6 Local Address Server (LAS) initialization, [chars]

Explanation    This is a transient error and it happens when the underlying communication layer, Group Service Process (GSP), is temporarily unavailable.

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     
 
    
    
   

%IP-LIBIPV6PROTO-3-ERR_NETIO_CONN_INIT Failed to connect to netio, [chars]

Explanation    The transport fails to open the connection to netio. This error is normally transient and it occurs when the netio process is temporarity unavailable.

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     
 
    
    
   

%IP-LIBIPV6PROTO-3-ERR_NETWORK_GONE Network protocol process is not up

Explanation    The transport detects that the network protocol process is not running. The problem is usually transient and is recovered once the network process becomes available.

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     
 
    
    
   

%IP-LIBIPV6PROTO-3-ERR_NO_MEM Failed to allocate [dec] bytes of memory, [chars]

Explanation    One of the memory allocation routines such as malloc() fails.

Recommended Action    Use 'show memory summary [location ]' command to determine the state of the system memory. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%IP-LIBIPV6PROTO-3-IPSEC_HANDLE [chars]: [chars]

Explanation    An error is encountered in handling a IP Security packet

Recommended Action    The returned error provides the type of the error. Based of the error type, the source of the error could be identified.

Error Message     
 
    
    
   

%IP-LIBIPV6PROTO-7-ERR_SEND_PACKET Failed to send a packet to the network layer, [chars]

Explanation    The transport fails to send a message with packet to the network layer.

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.

MGII_API Messages

Error Message     
 
    
    
   

%IP-MGII_API-3-INFRA_FAIL [chars] failed: [chars]

Explanation    An error occurred while processing an infrastructure service request. This should happen mostly due to resource exhaustion.

Recommended Action    Do the following 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.

MPA_CONSUMER Messages

Error Message     
 
    
    
   

%IP-MPA_CONSUMER-3-ERR_MEM_ALLOC Failed to allocate memory

Explanation    The Multicast Port Arbitrator consumer library failed to allocate memory.

Recommended Action    The system is running low on memory, if there is lots of config/routes, try reducing it. Do the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If there isn't too much config, then do the following 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.

MPA Messages

Error Message     
 
    
    
   

%IP-MPA-3-DOWNLOAD_FAIL Unable to download multicast joins to a restarted csmr on node [chars] : [chars]

Explanation    The Multicast Port Arbitrator was unable to download one or more multicast joins to a restarting instance of its consumer on the specified node.

Recommended Action    Do the following 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     
 
    
    
   

%IP-MPA-3-ERR_MEM_ALLOC Failed to allocate memory

Explanation    The Multicast Port Arbitrator failed to allocate memory.

Recommended Action    The system is running low on memory, if there is lots of config/routes, try reducing it. Do the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If there isn't too much config, then do the following 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     
 
    
    
   

%IP-MPA-3-GROUP_SEND_NODE [chars]: failed to send group message to node [hex]: [chars]

Explanation    An internal error was detected when trying to send a GSP message to the given 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     
 
    
    
   

%IP-MPA-3-MGII_MUTEX mutex failed: [chars]: [chars]

Explanation    Failure of thread operations on the mutex protecting the multicast group memberships.

Recommended Action    Do the following 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     
 
    
    
   

%IP-MPA-3-RADIX_FAIL Radix operation [chars] failed for node [chars]([hex])

Explanation    An internal error occured while updating an internal node database.

Recommended Action    Do the following 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     
 
    
    
   

%IP-MPA-3-RTINSERT_FAIL Failed to insert an entry in MPA multicast database radix tree

Explanation    A radix tree internal error occured while inserting in MPA multicast 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     
 
    
    
   

%IP-MPA-7-DELETE_FAIL Unable to delete client node ([chars]) from AVL tree

Explanation    An AVL tree internal erorr occurred while deleting a client node.

Recommended Action    Do the following 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     
 
    
    
   

%IP-MPA-7-INIT_FAILED Cannot initialize [chars]: [chars]

Explanation    The indicated initialization of the MPA failed and the process restarted.

Recommended Action    If the indicated error is about low memory, do the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Else, do the following 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.

PFILTER_MA Messages

Error Message     
 
    
    
   

%IP-PFILTER_MA-7-INIT Failed to initialize [chars], because of [chars]

Explanation    Initialization failed. Both the initialization type and the error code are displayed. The sysmgr process will restart the ipv4_aclmgr if this condition happens.

Recommended Action    None

RAW Messages

Error Message     
 
    
    
   

%IP-RAW-3-DEBUG_INIT [chars]%s

Explanation    An software error occured when the RAW process try to do debug related initialization.

Recommended Action    The process will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise if the message's error code indicates that the failure was due to lack of memory, then take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the problem was not caused by memory allocation and it hasn't been corrected by subsequence restarts then take the following 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     
 
    
    
   

%IP-RAW-3-INIT_ERR [chars]%s

Explanation    An software error occurred while starting up of RAW process. If this occurred during process startup, then the process may be restarted.

Recommended Action    The process will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise if the message's error code indicates that the failure was due to lack of memory, then take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the problem was not caused by memory allocation and it hasn't been corrected by subsequence restarts then take the following 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     
 
    
    
   

%IP-RAW-3-INIT_RETRY [chars] ([dec])

Explanation    An software error occured when the RAW process attempts to retry one of its initialization tasks with a network layer.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. 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     
 
    
    
   

%IP-RAW-3-NO_MEM [chars] ([chars]): [chars]

Explanation    An software error occured when the RAW process try to request more memory. The requested operation by raw could not be accomplished because of a low memory condition.

Recommended Action    In the problem recurs, reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%IP-RAW-3-RED_INIT [chars] - [chars]

Explanation    An software error occured when the RAW process try to do redundancy related init with System Manager for the node state changes.

Recommended Action    The process will attempt to recover from this situation by restarting or retrying. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise if the message's error code indicates that the failure was due to lack of memory, then take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the problem was not caused by memory allocation and it hasn't been corrected by subsequence restarts then take the following 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     
 
    
    
   

%IP-RAW-3-REG_NETWORK Failed to register RAW protocol with the network layer ([chars]): [chars]

Explanation    An software error occured when the RAW process try to register itself with the network process and net io process for datapath.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. 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     
 
    
    
   

%IP-RAW-3-SOCKET_INIT [chars] ([chars]): [chars]

Explanation    An software error occured when the RAW process do socket related initialization.

Recommended Action    The process will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise if the message's error code indicates that the failure was due to lack of memory, then take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%IP-RAW-3-SOFTWARE_INSTALL [chars]: [chars]

Explanation    An software error occured when the RAW process attempts to register with Install Manager for notification of software package installation and deinstallation on the system.

Recommended Action    The process will attempt to recover from this situation by restarting or retrying. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise if the message's error code indicates that the failure was due to lack of memory, then take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the problem was not caused by memory allocation and it hasn't been corrected by subsequence restarts then take the following 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     
 
    
    
   

%IP-RAW-3-TIMER_INIT [chars]: [chars]

Explanation    An software error occured when the RAW process sets up and initializes the various RAW timers.

Recommended Action    The process will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise if the message's error code indicates that the failure was due to lack of memory, then take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%IP-RAW-3-VRF_INIT [chars]: [chars]

Explanation    An software error occured when the RAW process attempts to set up connection with the RSI agent during the startup of raw process.

Recommended Action    The process will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise if the message's error code indicates that the failure was due to lack of memory, then take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the problem was not caused by memory allocation and it hasn't been corrected by subsequence restarts then take the following 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     
 
    
    
   

%IP-RAW-7-SYSDB_INIT [chars] - [chars]

Explanation    An software error occured when the RAW process try to do initialization related with sysdb process.

Recommended Action    The process will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise if the message's error code indicates that the failure was due to lack of memory, then take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the problem was not caused by memory allocation and it hasn't been corrected by subsequence restarts then take the following 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.

rlogin Messages

Error Message     
 
    
    
   

%IP-rlogin-3-CHILD_PID [chars]: [chars]

Explanation    rlogin client application's child process has invalid pid

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     
 
    
    
   

%IP-rlogin-3-CHILD_STOPPED [chars]: the child stopped with signal number [dec]

Explanation    rlogin client application's child process was stopped abnormally

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     
 
    
    
   

%IP-rlogin-3-CHILD_TERMINATED [chars]: the child terminated with signal number [dec]

Explanation    rlogin client application's child process terminated abnormally.

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     
 
    
    
   

%IP-rlogin-3-ERR_BEST_ROUTE No route to destination host exists

Explanation    Socket 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     
 
    
    
   

%IP-rlogin-3-ERR_CREATE_EVENTMGR Couldn't create evmgr

Explanation    Internal error.

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     
 
    
    
   

%IP-rlogin-3-ERR_FLUSH tcflush failed

Explanation    tcflush() call 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     
 
    
    
   

%IP-rlogin-3-ERR_FORK Can't fork child process

Explanation    Internal error in forking child 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     
 
    
    
   

%IP-rlogin-3-ERR_SOCKET socket: [chars]

Explanation    Socket 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     
 
    
    
   

%IP-rlogin-3-WAIT [chars]: [chars]

Explanation    rlogin client's call to wait() system call 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     
 
    
    
   

%IP-rlogin-6-ERR_GENRAL [chars]

Explanation    The rlogin encountered some problem in genric nature or plain information.

Recommended Action    'No action is required.'

RLOGIND Messages

Error Message     
 
    
    
   

%IP-RLOGIND-3-ERR_CREATE_EVENTMGR Couldn't create evmgr in function [chars]()

Explanation    Internal error.

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     
 
    
    
   

%IP-RLOGIND-3-ERR_DEBUG_INIT Failed to init debug in function [chars]()

Explanation    Internal error.

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     
 
    
    
   

%IP-RLOGIND-3-ERR_FATAL Rlogind: fatal error [chars]

Explanation    Fatal error.

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     
 
    
    
   

%IP-RLOGIND-3-ERR_MALLOC Cannot allocate memory in function [chars]()

Explanation    Internal error. System is out of memory - malloc 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     
 
    
    
   

%IP-RLOGIND-3-ERR_OPEN Failed to open a device file for a session ([dec])

Explanation    An unexpected error occurred when RloginD tried to open a VTY character special file.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%IP-RLOGIND-3-ERR_SPAWN Can't spawn login

Explanation    Internal error in spawning login child 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     
 
    
    
   

%IP-RLOGIND-3-ERR_SYSDB Unexpected SysDB error encountered: [hex], '[chars]'

Explanation    The Telnet Server has encountered an error using the SysDB Library.

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     
 
    
    
   

%IP-RLOGIND-3-ERR_TTY_DETAILS Failed to retrieve the details of a TTY Device ([hex], '[chars]')

Explanation    An unexpected error occurred when RloginD tried to retrieve the details of a VTY from a utility library

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     
 
    
    
   

%IP-RLOGIND-3-ERR_USAGE usage : rlogind [-alnd]

Explanation    Usage error.

Recommended Action    'No action is required.'

Error Message     
 
    
    
   

%IP-RLOGIND-3-ERR_VTY_CONNECT Failed to obtain a VTY for a session: '[chars]'

Explanation    An error occurred when RloginD requested a VTY for a session. This might occur if the requested rlogin session cannot be satisfied by any of the unused VTYs in the configured vty pool(s), e.g. if all VTYs are in use, if transport-input is not allowed for rlogin, or if the configured ACL does not match.

Recommended Action    Check that the configured VTY pool(s) can satisfy this rlogin request based on which VTYs are currently in use. This can be checked with 'show users', and looking at the VTY pool configuration. If the configuration appears to be consistent then try to rlogin with debug rlogin detail on; this might indicate where the problem lies.

Error Message     
 
    
    
   

%IP-RLOGIND-4-ERR_SOCKET Socket operation failed: [chars]

Explanation    Internal warnings related to socket operations.

Recommended Action    'No action is required.'

Error Message     
 
    
    
   

%IP-RLOGIND-6-INFO_GENERAL Rlogind: [chars]

Explanation    The rlogind encountered some problem in genric nature or plain information.

Recommended Action    'No action is required.'

RSHD Messages

Error Message     
 
    
    
   

%IP-RSHD-2-ILLEGAL_PORT Illegal port: [chars]

Explanation    The connection between rsh client and server must from/to a privileged port (512-1023)

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     
 
    
    
   

%IP-RSHD-3-ERR_AUTH Kerberos rsh denied to [chars].[chars]@[chars]

Explanation    Kerberos authentication failed.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%IP-RSHD-3-ERR_CREATE_EVENTMGR Failed to create event manager: [chars]

Explanation    Attempt to create an event manager fails for some reason

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     
 
    
    
   

%IP-RSHD-3-ERR_MALLOC Failed to allocate [dec] bytes of memory: [chars]

Explanation    The server has failed to acquire the required amount of memory

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

Error Message     
 
    
    
   

%IP-RSHD-3-ERR_REGISTER_DEBUG Failed to register for debugging events: [chars]

Explanation    Attempt to register with the event magager for debugging events 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     
 
    
    
   

%IP-RSHD-3-ERR_SOCKET Socket operation failed: [chars]: [chars]

Explanation    Internal warnings related to socket operations

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     
 
    
    
   

%IP-RSHD-3-ERR_USAGE [chars]

Explanation    Usage error.

Recommended Action    No action is required.

SMIAP Messages

Error Message     
 
    
    
   

%IP-SMIAP-2-INIT_FAILED Cannot initialize [chars]: ([chars])

Explanation    IPV4 SMIAP initialization 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     
 
    
    
   

%IP-SMIAP-4-ADDR_CFLCT IP address [chars] configured on management interface [chars] same as virtual IP address [chars]

Explanation    IP address on the management interface specified is conflicting with the virtual IP address.

Recommended Action    Either change the virtual IP address to some other IP address on the management interface's network or change the conflicting IP address on the specified management interface.

Error Message     
 
    
    
   

%IP-SMIAP-4-IM_ATTR_FIND_IF_FAILED Interface '[chars]' is supposed to be a management interface, but, can't find information about it

Explanation    Management interface information needs to be known in SMIAP so that it can make the virtual IP address functional.

Recommended Action    If the message is for a management interface which doesn't exist anymore, e.g., due to a failover, this error can be simply ignored. If it is for an interface which is active, contact technical support.

Error Message     
 
    
    
   

%IP-SMIAP-4-INVALID_NETWORK IP address [chars]/[dec] on the management interface [chars] does not belong to same network as virtual IP address [chars]/[dec]

Explanation    IP address on the management interface on the active/standby RP should be in the same network as the virtual IP address.

Recommended Action    Change the IP address on the management interface or the virtual IP address so that they are in the same network and are not the same.

Error Message     
 
    
    
   

%IP-SMIAP-4-SYSMGR_FAILURE Failed to signal sysmgr about - [chars], error [chars]

Explanation    SMIAP failed to signal sysmgr about its process 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     
 
    
    
   

%IP-SMIAP-4-VIRTUAL_IP_CFLCT Virtual IP address [chars] same as [chars] configured on management interface [chars]

Explanation    IP address on the management interface specified is conflicting with the virtual IP address.

Recommended Action    Either change the virtual IP address to some other IP address on the management interface's network or change the conflicting IP address on the specified management interface.

SOCKET Messages

Error Message     
 
    
    
   

%IP-SOCKET-7-DEBUG_INIT_EVENT Failed to initialize debug event: [chars]

Explanation    The socket library (used by transports) failed to initialize a debug event.

Recommended Action    The transport process will try to recover from this by retrying/ restarting. If the messages are not seen again, the problem was transitory and has been recovered. There is no need to take any action. If the messages come continuously, take the following 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     
 
    
    
   

%IP-SOCKET-7-DEBUG_REGISTER Failed to register with debug library: [chars]

Explanation    Failed to register with the debug library to have the library automatically handle changes to any of the SOCKET debug flags.

Recommended Action    The transport process will try to recover from this by retrying/ restarting. If the messages are not seen again, the problem was transitory and has been recovered. There is no need to take any action. If the messages come continuously, take the following 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     
 
    
    
   

%IP-SOCKET-7-ERR_EVM_CREATE Failed to create event manager: [chars]

Explanation    The socket library failed to create event manager.

Recommended Action    If the error message indicates low memory, do the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. For any other errors, do the following 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.

STANDBY Messages

Error Message     
 
    
    
   

%IP-STANDBY-3-ERR_EDM_NOTIFY [chars]: Failed to generate [chars]: [chars]

Explanation    HSRP has failed to notify the system that the specified event has occurred.

Recommended Action    Restart the HSRP process. 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     
 
    
    
   

%IP-STANDBY-3-ERR_IM Failed to get [chars] type from Interface Manager: [chars]

Explanation    HSRP has failed to retrieve required information about the interface from the Interface Manager.

Recommended Action    Check to see if there are any other errors on the system which may indicate a general service-related problem and restart those services. If the problem is isolated then restart HSRP. 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     
 
    
    
   

%IP-STANDBY-3-ERR_INDEX Failed to obtain snmp index for [chars]: [chars]

Explanation    The HSRP process failed to obtain the snmp index for this interface. There may be a problem with the connection to certain IOSXR services.

Recommended Action    Retry the configuration on this interface. If this still fails then do the following. 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     
 
    
    
   

%IP-STANDBY-3-ERR_JOIN Failed to [chars] interface [chars] on Multicast group: [chars]

Explanation    The HSRP process failed to start/stop receiving HSRP packets on an interface correctly. This is an internal error.

Recommended Action    Retry the configuration on the interface. If this still fails then do the following. 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     
 
    
    
   

%IP-STANDBY-3-ERR_MAC Failed to add unicast MAC address on interface [chars]: [chars]

Explanation    HSRP has failed to assign a MAC address to the interface.

Recommended Action    Retry the configuration on the interface. If this still fails then do the following. 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     
 
    
    
   

%IP-STANDBY-3-ERR_REGISTER Registration for [chars] failed: [chars]

Explanation    Registration for an IOSXR service failed during HSRP's operation. This may indicate a connection failure with the IOSXR service as indicated in the error message.

Recommended Action    Restart the HSRP process. 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     
 
    
    
   

%IP-STANDBY-4-WARN_DEBUG Outputting debug information failed: [chars]

Explanation    The HSRP process failed to output a debug message. This may not impact functionality but it does impair the debuggabilty of the VRRP process. And may indicate that there is a failure with the IOSXR debug infrastructure.

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     
 
    
    
   

%IP-STANDBY-4-WARN_INIT HSRP Initialization failed: [chars]: [chars]

Explanation    The HSRP process failed to initialize correctly. In this situation HSRP restarts, but HSRP may not recover if there is a persistant error in the IOSXR system and HSRP is later unable to reestablish its connections and initialize successfully.

Recommended Action    If HSRP does not restart and automatically recover, do the following. 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     
 
    
    
   

%IP-STANDBY-6-INFO_HOLDTIME Holdtime ([dec]) is less than or equal to twice the hellotime ([dec])

Explanation    The holdtime has been set to a value which is less than (or equal to) twice the hello time. This is not recommended as any lost packet may result in an unnecessary state change.

Recommended Action    Change the holdtime to be greater than twice the hellotime.

Error Message     
 
    
    
   

%IP-STANDBY-6-INFO_REDIRECTS_DISABLED ICMP redirects may still be enabled on this interface

Explanation    Disabling HSRP filtered ICMP redirects when ICMP redirects are enabled may cause hosts to use real IP addresses as their default routes, and first hop redundancy may be lost.

Recommended Action    Ensure that ICMP redirects are disabled on this interface.

Error Message     
 
    
    
   

%IP-STANDBY-6-INFO_REDIRECTS_SECONDARY ICMP redirects may be ignored by hosts if HSRP secondary addresses are used

Explanation    If a host uses HSRP secondary addresses, HSRP filtered ICMP redirects may be ignored by the host (depending on the host implementation).

Recommended Action    Try to avoid using HSRP secondary addresses when HSRP filtered ICMP redirects are enabled.

Error Message     
 
    
    
   

%IP-STANDBY-6-INFO_STATECHANGE SB[dec]: [chars]: state [chars]011 - [chars]

Explanation    The HSRP router has changed state for the specified group and interface.

Recommended Action    No action is required

TCP Messages

Error Message     
 
    
    
   

%IP-TCP-3-DEBUG_INIT [chars]%s

Explanation    An software error occured when the TCP process try to do debug related initialization.

Recommended Action    The process will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise if the message's error code indicates that the failure was due to lack of memory, then take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the problem was not caused by memory allocation and it hasn't been corrected by subsequence restarts then take the following 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     
 
    
    
   

%IP-TCP-3-IM_INIT [chars]: [chars]

Explanation    An software error occured when the TCP process try to do initialization with ifmgr

Recommended Action    The process will attempt to recover from this situation by restarting or retrying. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise if the message's error code indicates that the failure was due to lack of memory, then take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the problem was not caused by memory allocation and it hasn't been corrected by subsequence restarts then take the following 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     
 
    
    
   

%IP-TCP-3-IM_LOOKUP Failed to lookup [chars] [chars] from IM: [chars]

Explanation    An software error occured when the TCP process try to lookup a network attribute from the Inteface Manager.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.

Error Message     
 
    
    
   

%IP-TCP-3-INIT_ERR [chars]%s

Explanation    An software error occurred while starting up of TCP process. If this occurred during process startup, then the process may be restarted.

Recommended Action    The process will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise if the message's error code indicates that the failure was due to lack of memory, then take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the problem was not caused by memory allocation and it hasn't been corrected by subsequence restarts then take the following 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     
 
    
    
   

%IP-TCP-3-INIT_RETRY [chars] ([dec])

Explanation    An software error occured when the TCP process attempts to retry one of its initialization tasks with a network layer.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. 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     
 
    
    
   

%IP-TCP-3-NO_MEM [chars] ([chars]): [chars]

Explanation    An software error occured when the TCP process try to request more memory. The requested operation by tcp could not be accomplished because of a low memory condition.

Recommended Action    In the problem recurs, reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%IP-TCP-3-RED_INIT [chars] - [chars]

Explanation    An software error occured when the TCP process try to do redundancy related init with System Manager for the node state changes.

Recommended Action    The process will attempt to recover from this situation by restarting or retrying. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise if the message's error code indicates that the failure was due to lack of memory, then take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the problem was not caused by memory allocation and it hasn't been corrected by subsequence restarts then take the following 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     
 
    
    
   

%IP-TCP-3-REG_NETWORK Failed to register TCP protocol with the network layer ([chars]): [chars]

Explanation    An software error occured when the TCP process try to register itself with the network process and net io process for datapath.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. 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     
 
    
    
   

%IP-TCP-3-SOCKET_INIT [chars] ([chars]): [chars]

Explanation    An software error occured when the TCP process do socket related initialization.

Recommended Action    The process will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise if the message's error code indicates that the failure was due to lack of memory, then take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%IP-TCP-3-TIMER_INIT [chars]: [chars]

Explanation    An software error occured when the TCP process sets up and initializes the various TCP timers.

Recommended Action    The process will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise if the message's error code indicates that the failure was due to lack of memory, then take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%IP-TCP-3-VRF_INIT [chars]: [chars]

Explanation    An software error occured when the TCP process attempts to set up connection with the RSI agent during the startup of tcp process.

Recommended Action    The process will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise if the message's error code indicates that the failure was due to lack of memory, then take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the problem was not caused by memory allocation and it hasn't been corrected by subsequence restarts then take the following 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     
 
    
    
   

%IP-TCP-7-SYSDB_INIT [chars] - [chars]

Explanation    An software error occured when the TCP process try to do initialization related with sysdb process.

Recommended Action    The process will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise if the message's error code indicates that the failure was due to lack of memory, then take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the problem was not caused by memory allocation and it hasn't been corrected by subsequence restarts then take the following 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.

telnet Messages

Error Message     
 
    
    
   

%IP-telnet-3-ARM_ADDRESS Error: [chars]

Explanation    'The call to ip_addr_c_get_v4/v6_best() failed'

Recommended Action    *SH_TECH*

Error Message     
 
    
    
   

%IP-telnet-3-ERR_SYSDB Unexpected SysDB error encountered: [hex], '[chars]'

Explanation    The Telnet client has encountered an error using the SysDB Library.

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     
 
    
    
   

%IP-telnet-3-INTF_DOWN Specified source interface is down

Explanation    'The source interface is down, therefore it can not be used.'

Recommended Action    *SH_TECH*

Error Message     
 
    
    
   

%IP-telnet-3-INTF_HANDLE The interface handle for the source interface is invalid

Explanation    'The call to interface_find() returned invalid interface handle'

Recommended Action    *SH_TECH*

Error Message     
 
    
    
   

%IP-telnet-3-INVALID_ADDR_FAMILY Invalid adress family: [dec]

Explanation    'The api has returned invalid address family'

Recommended Action    *SH_TECH*

Error Message     
 
    
    
   

%IP-telnet-3-INVALID_ADDRESS Source interface has an invalid address

Explanation    'The call to ip_addr_c_get_v4/v6_best() returned an invalid address'

Recommended Action    *SH_TECH*

Error Message     
 
    
    
   

%IP-telnet-3-INVALID_INTF The specified source interface is invalid

Explanation    'The specified source interface can not be used. Will use default interface'

Recommended Action    *SH_TECH*

Error Message     
 
    
    
   

%IP-telnet-3-INVALID_PORT Error converting the port number to numerical representation: [chars]

Explanation    'The port specified on the command line can not be converted'

Recommended Action    *SH_TECH*

Error Message     
 
    
    
   

%IP-telnet-3-IP_ARM Error: [chars]

Explanation    'The call to ip_addr_c_init() failed'

Recommended Action    *SH_TECH*

Error Message     
 
    
    
   

%IP-telnet-3-RIB_BIND_FAILURE Unable to bind to the RIB

Explanation    An error occurred while attempting to bind to the RIB.

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     
 
    
    
   

%IP-telnet-3-RIB_SRC_ADDRESS_ERROR Error retrieving source address from RIB: [chars]. Cannot continue.

Explanation    An error occured while trying to retrieve the IP address of the source interface from the RIB.

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     
 
    
    
   

%IP-telnet-3-SYSDB_GET [chars]: [chars]

Explanation    'Unable to get/read an item from sysDB '

Recommended Action    *SH_TECH*

Error Message     
 
    
    
   

%IP-telnet-3-SYSTEM_ERROR Error in [chars]. errno [dec]: [chars]

Explanation    'There was an error during invocation of a system call'

Recommended Action    *SH_TECH*

Error Message     
 
    
    
   

%IP-telnet-3-TCP_NETWORK_COMMS Error communicating with the network: [chars] Exiting.

Explanation    An error occurred whilst trying to set an option on the TCP socket used for this connection.

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. The router can continue to be used.

Error Message     
 
    
    
   

%IP-telnet-3-TTY_DETAILS [chars]: [chars]

Explanation    'The call to tty_details_from_device_file() failed '

Recommended Action    *SH_TECH*

Error Message     
 
    
    
   

%IP-telnet-3-TTY_NMSPC_PATH [chars]: [chars]

Explanation    'Unable to get the sysDB path of an item from TTY nmspc library'

Recommended Action    *SH_TECH*

Error Message     
 
    
    
   

%IP-telnet-4-TCP_NAGLE Failed to disable Nagle's algorithm during socket initialisation: [chars];

Explanation    Nagle's algorithm was not disabled; there is a small chance the telnet session will appear jerky. Telnet will otherwise function 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. The router can continue to be used.

TELNETD Messages

Error Message     
 
    
    
   

%IP-TELNETD-2-SYSTEM_FAIL [chars]: [chars] errno=[dec] [chars]

Explanation    There was a critical system call failure resulting in a failure to provide some system service.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message     
 
    
    
   

%IP-TELNETD-3-ERR_ADDRESS_FAMILY The address family [dec] is invalid

Explanation    The telnetd server was passed a bad adress family.

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     
 
    
    
   

%IP-TELNETD-3-ERR_BAD_PORT Bad port number

Explanation    The telnetd server was passed a bad port number.

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     
 
    
    
   

%IP-TELNETD-3-ERR_CONNECT Failed to obtain a VTY for a session: '[chars]'

Explanation    An error occurred when TelnetD requested a VTY for a session. This might occur if the requested telnet session cannot be satisfied by any of the unused VTYs in the configured vty pool(s), e.g. if all VTYs are in use, if transport-input is not allowed for telnet, or if the configured ACL does not match.

Recommended Action    Check that the configured VTY pool(s) can satisfy this telnet request based on which VTYs are currently in use. This can be checked with 'show users', and looking at the VTY pool configuration. If the configuration appears to be consistent then try to telnet with debug telnet detailed on; this might indicate where the problem lies.

Error Message     
 
    
    
   

%IP-TELNETD-3-ERR_CREATE_EVENTMGR Couldn't create evmgr in function [chars]()

Explanation    Internal error.

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     
 
    
    
   

%IP-TELNETD-3-ERR_DEBUG_INIT Failed to init debug in function [chars]()

Explanation    Internal error.

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     
 
    
    
   

%IP-TELNETD-3-ERR_EXITING Function cleanup() has been called due to an error

Explanation    The Telnet Server has encountered an unexpected error while using the system library.

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     
 
    
    
   

%IP-TELNETD-3-ERR_KERNEL [chars]: The call to [chars] failed. Error: [hex], '[chars]'

Explanation    The Telnet Server has encountered an unexpected error while using the system library.

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     
 
    
    
   

%IP-TELNETD-3-ERR_MALLOC Failed to allocate [dec] bytes of memory

Explanation    The server has failed to acquire the required amount of memory

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

Error Message     
 
    
    
   

%IP-TELNETD-3-ERR_OPEN Failed to open a device file for a session ([dec])

Explanation    An unexpected error occurred when TelnetD tried to open a VTY character special file.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%IP-TELNETD-3-ERR_PANIC telnetd: panic state = [dec]

Explanation    Panic error.

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     
 
    
    
   

%IP-TELNETD-3-ERR_SYSDB Unexpected SysDB error encountered: [hex], '[chars]'

Explanation    The Telnet Server has encountered an error using the SysDB Library.

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     
 
    
    
   

%IP-TELNETD-3-ERR_TTY_DETAILS Failed to retrieve the details of a TTY Device ([hex], '[chars]')

Explanation    An unexpected error occurred when TelnetD tried to retrieve the details of a VTY from a utility library

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     
 
    
    
   

%IP-TELNETD-3-ERR_USAGE usage : telnetd -debug -no_tty_server

Explanation    Usage error.

Recommended Action    'No action is required.'

Error Message     
 
    
    
   

%IP-TELNETD-3-SYSTEM_ERROR Error: [chars]

Explanation    The invocation of a system call returned 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.

Error Message     
 
    
    
   

%IP-TELNETD-3-TCP_NETWORK_COMMS Error communicating with the network: [chars] Exiting.

Explanation    An error occurred whilst trying to set an option on the TCP socket used for this connection.

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. The router can continue to be used.

Error Message     
 
    
    
   

%IP-TELNETD-4-CONFIGURATION_CHECK [chars]: Warning - configuration inconsistencies

Explanation    The configuration inconsistencies is detected for the indicated configuration.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message     
 
    
    
   

%IP-TELNETD-4-TCP_KEEPALIVE Failed to set the TCP keepalive timeout during socket initialisation: [chars]; default will apply

Explanation    The TCP keepalive timeout was not set during initialisation. The default value of 2 hours will apply. Telnet will otherwise function 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. The router can continue to be used.

Error Message     
 
    
    
   

%IP-TELNETD-4-TCP_NAGLE Failed to disable Nagle's algorithm during TCP socket initialisation: [chars];

Explanation    Nagle's algorithm was not disabled; there is a small chance the telnet session will appear jerky. Telnet will otherwise function 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. The router can continue to be used.

UDP Messages

Error Message     
 
    
    
   

%IP-UDP-3-DEBUG_INIT [chars]%s

Explanation    An software error occured when the UDP process try to do debug related initialization.

Recommended Action    The process will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise if the message's error code indicates that the failure was due to lack of memory, then take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the problem was not caused by memory allocation and it hasn't been corrected by subsequence restarts then take the following 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     
 
    
    
   

%IP-UDP-3-INIT_ERR [chars]%s

Explanation    An software error occurred while starting up of UDP process. If this occurred during process startup, then the process may be restarted.

Recommended Action    The process will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise if the message's error code indicates that the failure was due to lack of memory, then take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the problem was not caused by memory allocation and it hasn't been corrected by subsequence restarts then take the following 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     
 
    
    
   

%IP-UDP-3-INIT_RETRY [chars] ([dec])

Explanation    An software error occured when the UDP process attempts to retry one of its initialization tasks with a network layer.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. 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     
 
    
    
   

%IP-UDP-3-NO_MEM [chars] ([chars]): [chars]

Explanation    An software error occured when the UDP process try to request more memory. The requested operation by udp could not be accomplished because of a low memory condition.

Recommended Action    In the problem recurs, reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%IP-UDP-3-RED_INIT [chars] - [chars]

Explanation    An software error occured when the UDP process try to do redundancy related init with System Manager for the node state changes.

Recommended Action    The process will attempt to recover from this situation by restarting or retrying. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise if the message's error code indicates that the failure was due to lack of memory, then take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the problem was not caused by memory allocation and it hasn't been corrected by subsequence restarts then take the following 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     
 
    
    
   

%IP-UDP-3-REG_NETWORK Failed to register UDP protocol with the network layer ([chars]): [chars]

Explanation    An software error occured when the UDP process try to register itself with the network process and net io process for datapath.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. 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     
 
    
    
   

%IP-UDP-3-SOCKET_INIT [chars] ([chars]): [chars]

Explanation    An software error occured when the UDP process do socket related initialization.

Recommended Action    The process will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise if the message's error code indicates that the failure was due to lack of memory, then take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%IP-UDP-3-TIMER_INIT [chars]: [chars]

Explanation    An software error occured when the UDP process sets up and initializes the various UDP timers.

Recommended Action    The process will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise if the message's error code indicates that the failure was due to lack of memory, then take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%IP-UDP-3-VRF_INIT [chars]: [chars]

Explanation    An software error occured when the UDP process attempts to set up connection with the RSI agent during the startup of udp process.

Recommended Action    The process will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise if the message's error code indicates that the failure was due to lack of memory, then take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the problem was not caused by memory allocation and it hasn't been corrected by subsequence restarts then take the following 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     
 
    
    
   

%IP-UDP-7-SYSDB_INIT [chars] - [chars]

Explanation    An software error occured when the UDP process try to do initialization related with sysdb process.

Recommended Action    The process will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise if the message's error code indicates that the failure was due to lack of memory, then take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the problem was not caused by memory allocation and it hasn't been corrected by subsequence restarts then take the following 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.

VRRP Messages

Error Message     
 
    
    
   

%IP-VRRP-4-WARN_DEBUG Outputting debug information failed: [chars]

Explanation    The VRRP process failed to output a debug message. This may not impact functionality but it does impair the debuggabilty of the VRRP process. And may indicate that there is a failure with the IOSXR debug infrastructure.

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     
 
    
    
   

%IP-VRRP-4-WARN_INIT VRRP Initialization failed: [chars]: [chars]

Explanation    The VRRP process failed to initialize correctly. In this situation VRRP restarts, but VRRP may not recover if there is a persistant error in the IOSXR system and VRRP is later unable to reestablish its connections and initialize successfully.

Recommended Action    If VRRP does not restart and automatically recover, do the following. 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     
 
    
    
   

%IP-VRRP-4-WARN_REGISTER Registration for [chars] failed: [chars]

Explanation    Registration for an IOSXR service failed during VRRP's operation. This may indicate a connection failure with the IOSXR service as indicated in the error message.

Recommended Action    Restart the VRRP process. 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     
 
    
    
   

%IP-VRRP-6-INFO_STATECHANGE [chars] vrid [dec]: state [chars]011 - [chars]

Explanation    The VRRP router has changed state.

Recommended Action    No action is required.