Table Of Contents
Internet Protocol (IP) Messages
RLOGIND Messages
RSHD Messages
SMIAP Messages
SOCKET Messages
STANDBY Messages
Internet Protocol (IP) Messages
This section contains all Internet Protocol related System Error Messages. The following facility codes are represented in this module:
•
RLOGIND Messages
•
RSHD Messages
•
SMIAP Messages
•
SOCKET Messages
•
SOCKET Messages
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-4-DOUBLE_CLOSE
Close was called on the socket 0x[pointer] ([chars],
owned by proc [dec]) more than once
Explanation The socket library expect close to be called only once by os.
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-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.
Error Message
%IP-SOCKET-7-NOFDREF
NOFDREF flag on socket 0x[pointer] ([chars], owned by proc
[dec]) is already set where we expect it is not set
Explanation The socket library expect the NOFDREF flag to be not set and find it is already set.
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.
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. Reduce other system activity to ease memory
demands. If conditions warrant, upgrade to a larger memory configuration. Copy the error message
exactly as it appears 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.