Cisco Internet Streamer CDS 2.4 Alarms and Error Messages Guide
Error Messages and Recovery Procedures
Downloads: This chapterpdf (PDF - 1.42MB) The complete bookPDF (PDF - 6.17MB) | Feedback

Error Messages and Recovery Procedures

Table Of Contents

Error Messages and Recovery Procedures

ACL Messages

ACQ Messages

AUTH Messages

AUTHCACHE Messages

AUTHMOD Messages

BANDWD Messages

BMRNG Messages

BUFMGR Messages

BYPS Messages

CACHE Messages

CDNFS Messages

CIFSSVR Messages

CLEAN-AD Messages

CLI Messages

CMS Messages

COMMONEDM Messages

CSE Messages

DDBG Messages

DHCP Messages

DISK Messages

DIST Messages

DNS Messages

DS Messages

FFS Messages

FTP Messages

HTTP Messages

HTTPS Messages

ICAP Messages

ICP Messages

INETD Messages

LIBCMN Messages

LOGGING Messages

LSR Messages

MINGETTY Messages

MODUTILS Messages

NAS Messages

NODEMGR Messages

NTP Messages

PAM Messages

PARSER Messages

PFS Messages

PM Messages

POSTGRE Messages

PRELD Messages

RBPC Messages

REALPXY Messages

REALSRV Messages

RPC Messages

RSH Messages

RSM Messages

RTSP Messages

RTSPG Messages

RULES Messages

SCHED Messages

SERMON Messages

SNMP Messages

SR Messages

SSHD Messages

SSRV Messages

STATS Messages

STDBY Messages

STREAMCACHE Messages

SYS Messages

SYSMON Messages

SYSUTL Messages

SYSVINIT Messages

TELNET Messages

TFTP Messages

TRNSLG Messages

TVOUT Messages

UNILOG Messages

UNKNOWN Messages

UPG Messages

URLFLT Messages

UTILLIN Messages

VCRON Messages

WCCP Messages

WEBSENSE-SERVER Messages

WI Messages

WMT Messages

XXX Messages


Error Messages and Recovery Procedures


This chapter lists the Cisco Internet Streamer CDS Release 2.4 system error messages. Each message is followed by an explanation and recommended action.

The messages are grouped by the following Facility Codes and listed numerically within each Facility Code:

ACL Messages

ACQ Messages

AUTH Messages

AUTHCACHE Messages

AUTHMOD Messages

BANDWD Messages

BMRNG Messages

BUFMGR Messages

BYPS Messages

CACHE Messages

CDNFS Messages

CIFSSVR Messages

CLEAN-AD Messages

CLI Messages

CMS Messages

COMMONEDM Messages

CSE Messages

DDBG Messages

DHCP Messages

DISK Messages

DIST Messages

DNS Messages

DS Messages

FFS Messages

FTP Messages

HTTP Messages

HTTPS Messages

ICAP Messages

ICP Messages

INETD Messages

LIBCMN Messages

LOGGING Messages

LSR Messages

MINGETTY Messages

MODUTILS Messages

NAS Messages

NODEMGR Messages

NTP Messages

PAM Messages

PARSER Messages

PFS Messages

PM Messages

POSTGRE Messages

PRELD Messages

RBPC Messages

REALPXY Messages

REALSRV Messages

RPC Messages

RSH Messages

RSM Messages

RTSP Messages

RTSPG Messages

RULES Messages

SCHED Messages

SERMON Messages

SNMP Messages

SR Messages

SSHD Messages

SSRV Messages

STATS Messages

STDBY Messages

STREAMCACHE Messages

SYS Messages

SYSMON Messages

SYSUTL Messages

SYSVINIT Messages

TELNET Messages

TFTP Messages

TRNSLG Messages

TVOUT Messages

UNILOG Messages

UNKNOWN Messages

UPG Messages

URLFLT Messages

UTILLIN Messages

VCRON Messages

WCCP Messages

WEBSENSE-SERVER Messages

WI Messages

WMT Messages

XXX Messages

ACL Messages

Error Message    SE-ACL-3-533010:Failed to clear acl statistics. 

Explanation    Failed to clear ACL statistics.

Recommended Action    Enter the command later. Contact Cisco TAC if this problem persists.

Error Message    SE-ACL-3-533011:directory /tmp doesn't exist. 

Explanation    The system does not have a configured TMP directory.

Recommended Action    The system has serious software image setup or configuration problems. Contact Cisco TAC.

Error Message    SE-ACL-3-533012:can't open /tmp/.acl_request file to get acl query. 

Explanation    The system cannot open the ACL request file.

Recommended Action    Reconfigure the ACL, query the ACL through the debug commands, try to access the ACL later, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-ACL-3-533013:ACL lock failed. Internal error. 

Explanation    The system cannot lock the ACL table.

Recommended Action    Reconfigure the ACL, try to access the ACL later, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-ACL-3-533014:ACL unlock failed. Internal error. 

Explanation    The system cannot unlock the ACL table.

Recommended Action    Reconfigure the ACL, try to access the ACL later, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-ACL-3-533015:Internal error: Incorrect permission flag. 

Explanation    An incorrect permission flag was entered.

Recommended Action    Check the entered command and reconfigure the ACL.

Error Message    SE-ACL-3-533016:Internal error: Incorrect username or groupname flag. 

Explanation    An incorrect username or groupname flag was entered.

Recommended Action    Check the entered command and reconfigure the ACL.

Error Message    SE-ACL-3-533017:Username string length exceeds the limit. 

Explanation    A limited string length for the username can be configured.

Recommended Action    Reconfigure the ACL username string.

Error Message    SE-ACL-3-533018:Groupname string length exceeds the limit. 

Explanation    A limited string length for the groupname can be configured.

Recommended Action    Reconfigure ACL groupname string.

Error Message    SE-ACL-3-533019:Groupname string can't be empty. 

Explanation    Incorrect ACL command's groupname string.

Recommended Action    Check the entered command's groupname string and reconfigure the ACL.

Error Message    SE-ACL-3-533020:Group name shouldn't have delimited comma symbol. 

Explanation    Incorrect ACL command's groupname string.

Recommended Action    Check the entered command's groupname string and reconfigure the ACL.

Error Message    SE-ACL-3-533021:Access List entry position in the access list should 
be above 1. 

Explanation    Incorrect ACL command's position value configuration.

Recommended Action    Check the entered command for ACL configuration and set the correct position value.

Error Message    SE-ACL-3-533022:Internal error: Problem to allocate memory. 

Explanation    Memory allocation failure.

Recommended Action    Reload the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-ACL-3-533023:Problem to obtain ACL entry. 

Explanation    Failure to get a record from the ACL.

Recommended Action    Check the entered command and reconfigure the ACL. Reload the SE. Contact Cisco TAC if this problem persists.

ACQ Messages

Error Message    SE-ACQ-2-100001: Acquirer failed in Database operation: [failure 
description].

Explanation    The service acquirer encountered a critical error in database operation.

Recommended Action    Execute the cms database maintenance command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-ACQ-2-100002: Acquirer failed to connect to UNS server: [failure 
description].

Explanation    The unified name space (UNS) server fails to start or is busy.

Recommended Action    Reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-ACQ-2-100003: Failed to disable request=[chars] due to Database 
error: [chars] Restarting the acquirer process. 

Explanation    This error is a result of database data corruption. The acquirer is restarted.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-ACQ-2-100004: Failed to create Rpc Server: [failure description].

Explanation    It is possible that another instance of service acquirer is running or the port the remote procedure call (RPC) server wants to listen on is being used by other services.

Recommended Action    Reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-ACQ-2-100005: Request with url=[chars] has been disabled due to 
Database error: Failed to read [chars] = [chars] from [chars], error = [dec].

Explanation    This error is a result of data corruption in the database. The acquirer has tried to recover the error by reparsing the manifest file, but the recovery failed. The acquirer must disable this request.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-ACQ-2-100006: Failed to get delivery service lock: [failure 
description].

Explanation    The acquirer has a conflict with distribution and failed to start the acquisition for the delivery service.

Recommended Action    Configure another SE as a root SE, then reconfigure the original root SE to be the root again. If the problem persists, unassign the root SE from the delivery service and reassign it. Contact Cisco TAC if this problem persists.

Error Message    SE-ACQ-2-100007: Request hangs, will restart acquirer to correct the 
problem.

Explanation    This error is a result of an internal error. The acquirer is restarted.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-ACQ-2-100008: Corrupt data received via rpc for call [chars].

Explanation    The acquirer received corrupt RPC data.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-ACQ-2-100009: Failed to read Delivery Service=[chars], Delivery 
Service table may have been dropped accidentally. Restarting acquirer to wait for 
its creation.

Explanation    This error occurs because a delivery service table was accidently dropped by a command. The acquirer is restarted so it can wait for the delivery service table creation.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-ACQ-2-100010 Failed to acquire start-url.

Explanation    The acquirer is unable to acquire the start-URL for the crawl job.

Recommended Action    Correct the start-URL in the manifest file and retry. Contact Cisco TAC if this problem persists.

Error Message    SE-ACQ-2-100011 Failed to write in to NAS.

Explanation    The acquirer is unable to write to the network access server (NAS) device.

Recommended Action    Examine the NAS device. Check for free space on this file system by executing the show statistics cdnfs command and looking at the physical file system space free line. If there is no more free space, remove excess files on the file system (but do not remove files in the SE's directory), and assign the SE space inline with that available on the NAS device. Ensure that other applications are not filling up the NAS file system that the SE is using. If this problem persists, and there is sufficient free space, contact Cisco TAC.

Error Message    SE-ACQ-2-100012 Some acquisition tasks are not in active root delivery 
services.

Explanation    A database problem prevented the acquirer from reading the delivery service table, but it was able to read other tables.

Recommended Action    Check if the acquirer is running normally by executing the show acquirer command. If it is not running, contact Cisco TAC.

AUTH Messages

Error Message    SE-AUTH-3-110002:Username is too long (longer than 250 bytes).

Explanation    None.

Recommended Action    Verify the username is less than 250 bytes.

Error Message    SE-AUTH-3-110003:Failed to release pam handler.

Explanation    None.

Recommended Action    Try to log in again. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTH-3-110004:Failed to add transient user.

Explanation    None.

Recommended Action    Contact Cisco TAC.

Error Message    SE-AUTH-6-110001:General AUTH module debug message id.

Explanation    None.

Recommended Action    No action is required.

AUTHCACHE Messages

Error Message    SE-AUTHCACHE-5-570001:Authcache is 100% full. 

Explanation    AuthCache is full and needs to replace old entries to accommodate new ones.

Recommended Action    To improve performance, increase the authCache size.

Error Message    SE-AUTHCACHE-5-570002:authCacheDaemon() process_id = <pid> pthread_id 
= <pthread_id>. 

Explanation    Report the start up information on the authCache daemon process.

Recommended Action    No action is required.

Error Message    SE-AUTHCACHE-2-570003:http_ce_search_wrap: Fail to send auth message 
to http_authmod!!" len =<msg_len> errno = <err no>. 

Explanation    The cache cannot send an authentication message to the authmod module.

Recommended Action    Contact Cisco TAC.

Error Message    SE-AUTHCACHE-5-570004:authMsgDaemon() process_id = <pid> pthread_id = 
<pthread_id>. 

Explanation    Report the start up information on the authMsg daemon process.

Recommended Action    No action is required.

Error Message    SE-AUTHCACHE-5-570005:malloc failure, system may be low in memory! 

Explanation    Reports malloc failure and warns of low memory for the entire system.

Recommended Action    Collect the SE status and contact Cisco TAC.

Error Message    SE-AUTHCACHE-3-570006:Unexpected NTLM proxy request header. 

Explanation    The cache receives a "Proxy-Authorization: NTLM" header testing to the SE, but NTLM Request authentication is not enabled.

Recommended Action    Contact Cisco TAC.

AUTHMOD Messages

Error Message    SE-AUTHMOD-3-540001:Change a authentication server's status. 

Explanation    The authentication server's status has been changed.

Recommended Action    This is a normal authmod mode; no action is required.

Error Message    SE-AUTHMOD-3-540002:Reset server's status string to default. 

Explanation    The authmod reset the default server's status.

Recommended Action    This is a normal authmod mode; no action is required.

Error Message    SE-AUTHMOD-3-540003:Server's list current status timed out, try 
default status. 

Explanation    The server's list current status is timed out. Authmod tries the default server's status.

Recommended Action    This is a normal authmod mode; no action is required.

Error Message    SE-AUTHMOD-4-540004:Use default server's status; all servers are dead. 

Explanation    All authentication servers are dead. Authmod uses the default server's status.

Recommended Action    This is a normal authmod mode; no action is required.

Error Message    SE-AUTHMOD-3-540005:Failed to reset authentication server status. 

Explanation    The authmod failed to reset the authentication server status.

Recommended Action    If this error message occurs repeatedly, stop request authentication, kill or spawn authmod, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-4-540006:TACACS+ enable path not found in the data server. 

Explanation    The data server does not register the tacacs enable command.

Recommended Action    Disable TACACS+ authentication, enable it again, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-4-540007:Authmod debug path returned error for TACACS+ 
enable path. 

Explanation    The data server returns an error for the tacacs enable command.

Recommended Action    Disable TACACS+ authentication, enable it again, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540008:Fail to add handle into conn table. 

Explanation    The NTLM Samba failed to add a handle into the connection table.

Recommended Action    If this error message occurs repeatedly, stop request authentication, kill or spawn authmod, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540009:NTLM request failed to free connection. 

Explanation    The NTLM request failed to free a connection.

Recommended Action    Stop the request authentication, kill or spawn authmod, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540010:Failed to detach a thread. 

Explanation    The system cannot detach a thread.

Recommended Action    Stop request authentication, kill or spawn authmod, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540011:Username can't be an empty string. 

Explanation    The username is an empty string.

Recommended Action    Check the username and password you entered for authentication.

Error Message    SE-AUTHMOD-5-540012:Thread monitor kills one thread. 

Explanation    The system kills one authmod working thread.

Recommended Action    This is a normal authmod mode; no action is required.

Error Message    SE-AUTHMOD-5-540013:Thread monitor spawns one thread. 

Explanation    The system spawns one authmod working thread.

Recommended Action    This is a normal authmod mode; no action is required.

Error Message    SE-AUTHMOD-3-540014:Fail to create a working thread. 

Explanation    The system cannot create an authmod working thread.

Recommended Action    Stop request authentication, kill or spawn authmod, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540015:No working thread can be created, QUIT !! 

Explanation    The system cannot create any authmod working thread.

Recommended Action    Stop request authentication, kill or spawn authmod, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540016:Fail to create dispatch thread. 

Explanation    The system cannot create an authmod dispatch thread.

Recommended Action    Stop request authentication, kill or spawn authmod, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540017:Fail to create a monitor thread. 

Explanation    The system cannot create an authmod monitor thread.

Recommended Action    Stop request authentication, kill or spawn authmod, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540018:Failed to lock authentication server status. 

Explanation    The authmod failed to lock the authentication server status.

Recommended Action    If this error message occurs repeatedly, stop request authentication, kill or spawn authmod, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540019:Failed to bind data server socket. 

Explanation    The system has a problem binding the data server socket.

Recommended Action    Disable authentication, enable it again, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-4-540020:Failed the data server verification. 

Explanation    The system has a problem with data server verification.

Recommended Action    Disable authentication, enable it again, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-4-540021:Authmod debug path is invalid. 

Explanation    The data server returns an error for the authmod debug command.

Recommended Action    Disable authentication and enable it again, and disable authentication debug and enable it again. Reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-4-540022:Authmod debug path not found in the data server. 

Explanation    The data server does not register the authmod debug command.

Recommended Action    Disable authentication and enable it again, and disable authentication debug and enable it again. Reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-4-540023:Authmod debug path returns an error. 

Explanation    The data server returns an error for the authmod debug command.

Recommended Action    Disable authentication and enable it again, and disable authentication debug and enable it again. Reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-4-540024:Authmod debug log is invalid. 

Explanation    The data server returns an error for the authmod debug log command.

Recommended Action    Disable authentication and enable it again, and disable authentication debug and enable it again. Reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-4-540025:Authmod debug log not found in the data server. 

Explanation    The data server does not register the authmod debug log command.

Recommended Action    Disable authentication and enable it again, disable authentication debug and enable it again. Reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-4-540026:Authmod debug log returns an error. 

Explanation    The data server returns an error for the authmod debug log command.

Recommended Action    Disable authentication and enable it again, and disable authentication debug and enable it again. Reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-4-540027:RADIUS enable path not found in the data server. 

Explanation    The data server does not register the radius server enable command.

Recommended Action    Disable RADIUS authentication and enable it again, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-4-540028:Data Server RADIUS enable path returned error. 

Explanation    The data server returns an error for the radius enable command.

Recommended Action    Disable RADIUS authentication and enable it again, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-5-540029:Pending request timed out. 

Explanation    An authentication request in a pending state has expired.

Recommended Action    This is a normal authmod mode; no action is required.

Error Message    SE-AUTHMOD-3-540030:sendto() failed. 

Explanation    The system failed to write data to the socket.

Recommended Action    Disable authentication, enable it again, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-5-540031:Auth Module got 0 size auth message with the 
client. Process is exiting. 

Explanation    The system reads empty data from the socket.

Recommended Action    This is a normal authmod mode; no action is required.

Error Message    SE-AUTHMOD-5-540032:Auth Module returned error to the client. 

Explanation    The authentication module returned an error to the client.

Recommended Action    This is a normal authmod mode; no action is required.

Error Message    SE-AUTHMOD-3-540033:Failed to allocate the memory. Process is exiting. 

Explanation    The system failed to allocate the memory.

Recommended Action    Disable authentication, enable it again, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540034:Select failed. 

Explanation    The system's socket select failed.

Recommended Action    Disable authentication, enable it again, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540035:Failed to lock authentication server mutex. 

Explanation    The system failed to lock the authentication server mutex.

Recommended Action    Disable authentication, enable it again, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540036:Failed to create polling thread. 

Explanation    The system failed to create a polling thread.

Recommended Action    Disable authentication, enable it again, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540037:Fail to create socket. 

Explanation    The system failed to create a socket.

Recommended Action    Disable authentication, enable it again, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540038:Failed to bind a socket. 

Explanation    The system failed to bind a socket.

Recommended Action    Disable authentication, enable it again, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540039:Authentication Module failed to set signal 
handler. 

Explanation    The authentication module failed to set the signal handler.

Recommended Action    Disable authentication, enable it again, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540040:Failed to open LDAP config file. 

Explanation    The system cannot open the LDAP authentication configuration file.

Recommended Action    Reconfigure LDAP authentication first, authenticate a request, disable and enable LDAP authentication, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540041:Failed to read LDAP server config. 

Explanation    The system cannot read the LDAP authentication configuration file.

Recommended Action    Reconfigure LDAP authentication first, authenticate a request, disable and enable LDAP authentication, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540042:Missed LDAP port number configuration. 

Explanation    The system cannot read the LDAP authentication port.

Recommended Action    Reconfigure LDAP authentication first, authenticate a request, disable and enable LDAP authentication, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540043:Invalid LDAP server address. 

Explanation    The system cannot read the LDAP server IP address.

Recommended Action    Reconfigure LDAP authentication first, authenticate a request, disable and enable LDAP authentication, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540044:Failed memory allocation for LDAP server 
authentication. 

Explanation    The system cannot allocate the memory for LDAP configuration.

Recommended Action    Reconfigure LDAP authentication first, authenticate a request, disable and enable LDAP authentication, and reboot the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540045:Server Error; Samba failed to authenticate user. 

Explanation    The authentication server has a problem.

Recommended Action    Check the status of the authentication server. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540046:Protocol Error; Samba failed to authenticate user. 

Explanation    The authentication protocol has a problem.

Recommended Action    Check the status of the authentication server, and query another user. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540047:Invalid Password; Samba failed to authenticate 
user. 

Explanation    The authentication user has an incorrect password.

Recommended Action    Check the status of the authentication server, check the user password configuration, and query another user. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540048:Samba failed to authenticate user. 

Explanation    The user authentication fails.

Recommended Action    Check the status of the authentication server, check the user password configuration, and query another user. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540049:No Domain Controllers available. 

Explanation    There are no available Domain Controllers.

Recommended Action    Check the SE's configuration, validate the status of the authentication server, and verify the network topology and connections. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540050:There is no connection available. 

Explanation    There is no NTLM connection available.

Recommended Action    Check the status of the authentication server, and query another user. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-3-540051:There is no NTLM handle. 

Explanation    There is no NTLM handle available.

Recommended Action    Check the status of the authentication server, and query another user. Contact Cisco TAC if this problem persists.

Error Message    SE-AUTHMOD-2-540052:Failed to establish GC connection for AD search. 

Explanation    The message indicates there is error when connecting to GC servers for the Active Directory search. When AD group search is enabled, without GC connection, all user authorizations fail.

Recommended Action    Check the configuration for GC server addresses and Enum user configurations. Check the status of the GC server.

Error Message    SE-AUTHMOD-2-540053:Failed to establish LDAP server connection for AD 
search. 

Explanation    There is an error when connecting to the LDAP servers configured for the Active Directory search. When AD group search is enable, without LDAP server connection, authorization fails.

Recommended Action    Check the LDAP server and Enum user configuration, and check the status of the configured LDAP servers.

Error Message    SE-AUTHMOD-3-540054:Failed to bind Data Server. 

Explanation    There is a problem getting a data server connection.

Recommended Action    Reload the device. Contact Cisco TAC if this problem persists after the reload.

Error Message    SE-AUTHMOD-4-540055:Failed Data Server verification. 

Explanation    There is a problem getting a data server connection.

Recommended Action    Reload the device. Contact Cisco TAC if this problem persists after the reload.

Error Message    SE-AUTHMOD-3-540056:Failed to remove authmod connection structure. 

Explanation    There is a problem removing the authmod structure.

Recommended Action    Reload the device. Contact Cisco TAC if this problem persists after the reload.

Error Message    SE-AUTHMOD-4-540057:Failed Data Server notification. 

Explanation    There is a problem getting a data server connection.

Recommended Action    Reload the device. Contact Cisco TAC if this problem persists after the reload.

Error Message    SE-AUTHMOD-3-540058:Failed to reset NTLM server status string. 

Explanation    Failed to set NTLM server status string to default.

Recommended Action    Reload the device. Contact Cisco TAC if this problem persists after the reload.

Error Message    SE-AUTHMOD-3-540059:Failed to reset RADIUS server status string. 

Explanation    Failed to set RADIUS server status string to default.

Recommended Action    Reload the device. Contact Cisco TAC if this problem persists after the reload.

Error Message    SE-AUTHMOD-4-540060:Problem with Data Server's item. 

Explanation    Authmod failed either to get or to set the data server's item.

Recommended Action    Reload the device. Contact Cisco TAC if this problem persists after the reload.

Error Message    SE-AUTHMOD-5-540061:Finished initialization of authmod configure 
thread. 

Explanation    Finished initialization of authmod configure thread.

Recommended Action    No action is required.

Error Message    SE-AUTHMOD-5-540062:Started initialization of authmod configure 
thread. 

Explanation    Started initialization of authmod configure thread.

Recommended Action    No action is required.

Error Message    SE-AUTHMOD-2-540063:Configure thread has a failure.

Explanation    The configure thread has an error while processing a message.

Recommended Action    Reload the device. Contact Cisco TAC if this problem persists after the reload.

Error Message    SE-AUTHMOD-5-540064:NetBIOS RFCNT session request failure. 

Explanation    A failure occurs in the NetBIOS RFCNT session request.

Recommended Action    No action is required.

Error Message    SE-AUTHMOD-3-540065:Failed to reset a server status string. 

Explanation    Failed to set an authentication server status string to default.

Recommended Action    Reload the device. Contact Cisco TAC if this problem persists after the reload.

Error Message    SE-AUTHMOD-5-540066:Reset a server status string. 

Explanation    Set an authentication server status string to default.

Recommended Action    No action is required.

BANDWD Messages

Error Message    SE-BANDWD-3-115001:Failed to bind to [item] error number [x].

Explanation    The bandwidth module failed to bind the item in the data server. The error number for the bind is x.

Recommended Action    The system should recover from the error automatically. Contact Cisco TAC if this problem persists.

Error Message    SE-BANDWD-3-115002:The failed operation is retried in two seconds.

Explanation    The bandwidth module retries the failed operation in two seconds.

Recommended Action    The system should recover from the error automatically. Contact Cisco TAC if this problem persists.

Error Message    SE-BANDWD-3-115003:Failed verification registration with data server 
with error [x].

Explanation    The bandwidth module failed to register with the data server for verification. The error number is x.

Recommended Action    The system should recover from the error automatically. Contact Cisco TAC if this problem persists.

Error Message    SE-BANDWD-4-115004:Failed to create a thread for notification.

Explanation    The bandwidth module failed to create a notification thread from the database. It is restarted by the Node Health Manager.

Recommended Action    The system should recover from the error automatically. Contact Cisco TAC if this problem persists.

Error Message    SE-BANDWD-3-115005:Bandwidth setting failed.

Explanation    The bandwidth module failed to set the bandwidth because of an invalid module.

Recommended Action    If this error persists or occurs frequently, contact Cisco TAC.

Error Message    SE-BANDWD-6-115006:Set bandwidth for module [name] to [value].

Explanation    The bandwidth module set the bandwidth for module name to value.

Recommended Action    No action is required.

Error Message    SE-BANDWD-5-115007:Error [x] retrieving item [name] from data server.

Explanation    The bandwidth module failed to get the item name from the data server. The error number for the get is x.

Recommended Action    The system should recover from the error automatically. Contact Cisco TAC if this problem persists.

Error Message    SE-BANDWD-3-115008:Bandwidth module got error [x] from data server.

Explanation    The bandwidth module got error x while trying to receive the entire message from the data server.

Recommended Action    The system should recover from the error automatically. Contact Cisco TAC if this problem persists.

Error Message    SE-BANDWD-3-115009:Bandwidth module lost connection to data server.

Explanation    The bandwidth module lost the connection to the data server. It automatically retries the connection.

Recommended Action    The system should recover from the error automatically. Contact Cisco TAC if this problem persists.

Error Message    SE-BANDWD-3-115010:Bandwidth module got error [x] on 
ds_verification_info().

Explanation    The bandwidth module got error x while retrieving verification information from the data server.

Recommended Action    The system should recover from the error automatically. Contact Cisco TAC if this problem persists.

Error Message    SE-BANDWD-3-115011:Bandwidth module got error [x] on 
ds_build_verification_ack().

Explanation    The bandwidth module got error x while building a verification acknowledgement to the data server.

Recommended Action    The system should recover from the error automatically. Contact Cisco TAC if this problem persists.

Error Message    SE-BANDWD-3-115012:Bandwidth module got error [x] on 
ds_send_whole_ack().

Explanation    The bandwidth module got error x while sending a verification acknowledgement to the data server.

Recommended Action    The system should recover from the error automatically. Contact Cisco TAC if this problem persists.

Error Message    SE-BANDWD-3-115013:Bandwidth module got bad type [x] on 
ds_receive_whole_msg().

Explanation    The bandwidth module got error x while receiving a message from the data server.

Recommended Action    The system should recover from the error automatically. Contact Cisco TAC if this problem persists.

Error Message    SE-BANDWD-3-115014:Bandwidth module got socket error and is 
restarting.

Explanation    The bandwidth module received a socket error and is restarting.

Recommended Action    The system should recover from the error automatically. Contact Cisco TAC if this problem persists.

Error Message    SE-BANDWD-5-115015:Bandwidth module failed to connect to the Multicast 
Sender.

Explanation    The bandwidth module failed to send a message to the Multicast Sender.

Recommended Action    The system should recover from the error automatically. Contact Cisco TAC if this problem persists.

Error Message    SE-BANDWD-6-115016:Bandwidth module: Configured WMT bandwidth is [x] 
but a lower value is being set [y] due to a lower WMT bandwidth license.

Explanation    The bandwidth module is setting the Windows Media Technologies (WMT) value to y, which is lower than the configured value of x. This is because the bandwidth license configured allows for a lower value.

Recommended Action    This is an informational message to indicate the difference between the actual value of bandwidth available and the configured value.

Error Message    SE-BANDWD-3-115017:Failed notification registration with data server 
with error [x].

Explanation    The bandwidth module failed to register with the data server for notification. The error number is x.

Recommended Action    The system should recover from the error automatically. Contact Cisco TAC if this problem persists.

Error Message    SE-BANDWD-3-115018:Bandwidth module got error [x] on 
ds_notification_info().

Explanation    The bandwidth module received error x while retrieving notification information from the data server for the WMT license.

Recommended Action    The system should recover from the error automatically. Contact Cisco TAC if this problem persists.

Error Message    SE-BANDWD-3-115019:Bandwidth module could not update bandwidths of 
sprayers.

Explanation    The bandwidth module tries to update sprayer bandwidths via a thread after receiving a message from the data server, but is unable to create a thread.

Recommended Action    The system should recover from the error automatically. Contact Cisco TAC if this problem persists.

Error Message    SE-BANDWD-3-115020:Bandwidth module could not update bandwidth of 
sprayer.

Explanation    The bandwidth module failed to set the bandwidth for module name to value.

Recommended Action    The system should recover from the error automatically. Contact Cisco TAC if this problem persists.

BMRNG Messages

Error Message    SE-BMRNG-7-550001:<various messages>. 

Explanation    This is a boomerang debug message.

Recommended Action    No action is required.

Error Message    SE-BMRNG-3-550002:<function>: Memory allocation problem: <data> -or- 
cannot allocate memory -or- error allocating Boomerang transaction log! 

Explanation    The Boomerang module runs out of memory.

Recommended Action    Disable and re-enable the module. Reload if it does not work. Contact Cisco TAC if this problem persists.

Error Message    SE-BMRNG-3-550003:select err on boom_cli_vensock fd <number> 
(<error>). 

Explanation    The Boomerang module fails to talk to the data server.

Recommended Action    Contact Cisco TAC.

Error Message    SE-BMRNG-2-550004:Can't create log directory for boomerang's translog 
(<error>).

Explanation    The Boomerang module fails to make a directory for logs.

Recommended Action    Contact Cisco TAC.

Error Message    SE-BMRNG-2-550005:boom_agent: can't talk to data server. 

Explanation    The Boomerang module fails to talk to the data server.

Recommended Action    Contact Cisco TAC.

Error Message    SE-BMRNG-3-550006:sorry, NTP mode isn't supported in this boom-client 
port 

Explanation    The Boomerang module does not support the NTP mode.

Recommended Action    No action is required.

Error Message    SE-BMRNG-3-550007:sendto failed to send <number> bytes to <address> 
(<error>). 

Explanation    The Boomerang module fails to send the DNS race.

Recommended Action    Check the network configuration and DNS race destination.

Error Message    SE-BMRNG-3-550008:domain name is NULL; -or- <name> is too long; -or- 
<name> is not a valid domain name Domain name too long: <name>. 

Explanation    The Boomerang module receives a bad domain name.

Recommended Action    Check the boomerang server configuration.

Error Message    SE-BMRNG-3-550009:<name> is an alias of another domain. 

Explanation    The domain name is already an alias of another domain.

Recommended Action    Check the boomerang configuration or use a different name.

Error Message    SE-BMRNG-3-550010:No domain <name>. 

Explanation    Trying to remove a non-existent domain.

Recommended Action    Check the supplied domain name.

Error Message    SE-BMRNG-3-550011:Error [<function> at <line>] looking up parent 
domain <name>. 

Explanation    Trying to create an alias for non-existent domain.

Recommended Action    Check the supplied domain name.

Error Message    SE-BMRNG-3-550012:Invalid encryption type: <number>. 

Explanation    Unsupported encryption type.

Recommended Action    Contact Cisco TAC.

Error Message    SE-BMRNG-3-550013:Socket error in file <file> at line <line> 
(<error>). 

Explanation    The Boomerang module fails to create a socket.

Recommended Action    Contact Cisco TAC.

Error Message    SE-BMRNG-3-550014:No origin-server or content-server configured for 
<domain>, request dropped by DNS Boomerang. 

Explanation    The Boomerang module drops a request because no origin server or content server is configured.

Recommended Action    Configure origin server or content server.

Error Message    SE-BMRNG-3-550015:Boomerang logging sem lock failed. Internal error 
-or- <function>: pthread_mutex_lock failed! 

Explanation    The Boomerang module fails to obtain a lock.

Recommended Action    Contact Cisco TAC.

Error Message    SE-BMRNG-3-550016:Boomerang logging sem unlock failed. Internal error 
-or- <function>: pthread_mutex_unlock failed! 

Explanation    The Boomerang module fails to release a lock.

Recommended Action    Contact Cisco TAC.

Error Message    SE-BMRNG-3-550017:Boomerang logging: Cannot open file <name> 
(<error>). 

Explanation    The Boomerang module fails to open a log file.

Recommended Action    Contact Cisco TAC.

Error Message    SE-BMRNG-3-550018:Domain not added. 

Explanation    The Boomerang module fails to add a new domain name.

Recommended Action    Check the domain name.

Error Message    SE-BMRNG-3-550019:DNS A-Record misses. 

Explanation    DNS A-Record misses.

Recommended Action    Contact Cisco TAC.

Error Message    SE-BMRNG-3-550020:Error! bad pTrig->mode <number> at file <file> line 
<line>. 

Explanation    Unsupported mode.

Recommended Action    Contact Cisco TAC.

BUFMGR Messages

Error Message    SE-BUFMGR-2-560001:Http cache buffer manager: out of type <type> 
memory. 

Explanation    There is either a buffer leak or the buffer manager code has bugs.

Recommended Action    Divert HTTP traffic and reload. If this problem persists, contact Cisco with syslog and errorlog.

Error Message    SE-BUFMGR-4-560002:Notice:(<count>): data buffer memory low on thread: 
<thread>.Data memory free: <free> or- SE-BUFMGR-4-560002: Notice:(<count>): 
header buffer memory low on thread: <thread>.Header memory free: <free>. 

Explanation    The HTTP cache buffer manager is running low on memory. The system might be overloaded.

Recommended Action    Reduce the HTTP caching load.

Error Message    SE-BUFMGR-2-560003:Http cache buffer manager: shmget error <error> 
<string>. 

Explanation    The cache buffer manager cannot initialize memory. The system might be low on memory.

Recommended Action    Reload the system. Contact Cisco TAC if this problem persists.

Error Message    SE-BUFMGR-2-560004:Http cache buffer manager: failed to clean up 
resources <error>. 

Explanation    The cache buffer manager cannot initialize memory. The system failed to clean up previously shared memory.

Recommended Action    Reload the system. Contact Cisco TAC if this problem persists.

Error Message    SE-BUFMGR-6-560005:Http cache buffer manager uses <number> bytes. 

Explanation    The cache buffer manager starts. The cache buffer manager starts and prints out memory size to be initialized.

Recommended Action    No action is required.

BYPS Messages

Error Message    SE-BYPS-0-130000:BYPASS: System going out of Bypass mode.

Explanation    The load on the device might have reduced and the system is switching out of bypass mode.

Recommended Action    No action is required.

Error Message    SE-BYPS-5-130001:BYPASS: System going Offline BYPASS: reload to return 
to Online state.

Explanation    The device is going offline because of an overload state.

Recommended Action    Reboot the system to bring it to a stable state.

Error Message    SE-BYPS-4-130002:BYPASS: System going into Bypass mode.

Explanation    The load on the device might have gone above its maximum limit. The device bypasses new connections.

Recommended Action    Reduce the load or add additional SEs to handle the load. The device might become unstable if it gets overloaded.

Error Message    SE-BYPS-4-130003:BYPASS: sysdb_item_set() failed: return value is 
[error].

Explanation    The device overload state could not be saved successfully in the data server. The device state could be incorrectly displayed.

Recommended Action    If this error occurs frequently, contact Cisco TAC.

Error Message    SE-BYPS-4-130004:BYPASS: Module [module] not registered due to bad 
name.

Explanation    The specified module could not register its overload state. The module state could be incorrectly displayed.

Recommended Action    If this error occurs frequently, contact Cisco TAC.

Error Message    SE-BYPS-4-130005:BYPASS: Module [module] not registered successfully.

Explanation    The specified module could not register with overload. The module state could be incorrectly displayed.

Recommended Action    If this error occurs frequently, contact Cisco TAC.

Error Message    SE-BYPS-1-130006:BYPASS: Module [module] is unable to handle the load.

Explanation    The specified module is highly overloaded and is in a critical state.

Recommended Action    Reduce the load on the device. You might need to reboot the device to verify it has not entered an unstable state.

Error Message    SE-BYPS-6-130007:OVERLOAD: Preload did not receive overload message. 
But Preload seems to be running.

Explanation    Preload could not be informed of an overload condition. The device could get loaded more if preload begins.

Recommended Action    If preload is not running or configured, ignore this message. If preload is enabled and running, contact Cisco TAC.

CACHE Messages

Error Message    SE-CACHE-2-140001: HTTP proxy fails at startup.

Explanation    A critical error occurred while HTTP proxy started and requests system FD resources.

Recommended Action    Typically the HTTP proxy is automatically restarted. If this problem persists, restart the entire system. Collect the technical support information and contact Cisco TAC.

Error Message    SE-CACHE-2-140002: HTTP proxy fails at startup.

Explanation    A critical error occurred while HTTP proxy started and the configuration fails.

Recommended Action    Typically, the HTTP proxy is automatically restarted. If this problem persists, restart the entire system. Collect the technical support information and contact Cisco TAC.

Error Message    SE-CACHE-2-140003:HTTP proxy fails at startup.

Explanation    A critical error occurred while HTTP proxy started and it failed to open the logs.

Recommended Action    Typically, the HTTP proxy is automatically restarted. If this problem persists, restart the entire system. Collect the technical support information and contact Cisco TAC.

Error Message    SE-CACHE-2-140004:HTTP proxy fails at binding to tcp ports.

Explanation    A critical error occurred while HTTP proxy started and failed to bind on specific ports.

Recommended Action    Typically, the HTTP proxy fails to accept requests from the ports that have the problem; however, it keeps running and serving traffic on other ports. If this problem persists, restart the entire system. Collect the technical support information and contact Cisco TAC.

Error Message    SE-CACHE-3-140005:HTTP Proxy failed to create child process.

Explanation    The forking of a child process failed.

Recommended Action    The HTTP proxy sleeps and continues to try and fork a new child process. Collect the technical support information and contact Cisco TAC.

Error Message    SE-CACHE-2-140006:HTTP proxy fails on call to socket listen on a tcp 
port.

Explanation    A critical error occurred when HTTP proxy failed to start listening on a specific port.

Recommended Action    The HTTP proxy fails to accept requests from the ports that have the specified problem. The proxy keeps running and serving traffic on other configured ports (if any). Execute the show services ports port-number command to see which application is using that particular port, and modify the CLI configuration accordingly.

CDNFS Messages

Error Message    SE-CDNFS-6-480000:[message]. 

Explanation    Information relating to CDNFS file handling is being logged. Many of these messages are informational only. Depending on the specific message and severity, a problem might be occurring.

Recommended Action    Most messages do not require any action. If specific problematic behavior is seen (such as delivery service content not being replicated or being served), contact Cisco TAC.

Error Message    SE-CDNFS-3-480001:[message]. 

Explanation    An internal URL-specific metadata file was detected on a disk as being truncated (possibly of length 0).

Recommended Action    The system should recover automatically. If content fails to replicate, execute the cdnfs cleanup command. Contact Cisco TAC if this problem persists.

Error Message    SE-CDNFS-3-480002:[message]. 

Explanation    An internal URL-specific metadata file was opened using one particular lookup file. When the file was opened, the URL stored in the file did not match the lookup URL. Possible file system corruption occurred.

Recommended Action    If content fails to replicate or fails to be playable, contact Cisco TAC.

Error Message    SE-CDNFS-3-480003:hit limit on number of UNS-UFM table entries.

Explanation    Too many CDNFS entries were created. The limit is currently 1 million files. However, certain internal features also create CDNFS entries on an automated basis. Also, there could be a bug in the code for these other features, as too many CDNFS entries have been created and not cleaned up.

Recommended Action    Ensure that user website delivery services do not contain over 1 million URLs. Contact Cisco TAC if this problem persists.

Error Message    SE-CDNFS-3-480004:less than <number> bytes of unreserved space.

Explanation    A CDNFS entry (a URL) was being created, but insufficient unreserved (free) disk space was available.

Recommended Action    Ensure that there is sufficient CDNFS disk space assigned for the delivery services in use. Check that no disk drives have failed. Check the show statistics cdnfs command for more information on current CDNFS usage. If the problem persists (for example, if delivery service content fails to replicate), contact Cisco TAC.

Error Message    SE-CDNFS-3-480005:count not find a usable file system.

Explanation    A CDNFS entry (a URL) was being created, but no file system could be found to store it.

Recommended Action    Ensure that sufficient CDNFS disk space is assigned for the delivery services in use (check the show statistics cdnfs and show disks commands for current information). Check that no disk drives have failed. Contact Cisco TAC if this problem persists.

Error Message    SE-CDNFS-6-480006:xact_replay: [message]. 

Explanation    An ongoing transaction is being replayed to completion upon startup of the UNS-server subsystem. This is an informational message only.

Recommended Action    No action is required.

Error Message    SE-CDNFS-5-480007:[message]. 

Explanation    On startup, information about CDNFS file systems is printed. These are informational messages only.

Recommended Action    No action is required.

Error Message    SE-CDNFS-3-480008:unsfs.c: non-zero sequence number.

Explanation    An internal metadata file with a non-zero sequence number in its filename was observed. This might indicate some sort of file system corruption.

Recommended Action    If CDNFS content fails to replicate, if content is not properly servable, or if other problems persist, contact Cisco TAC.

CIFSSVR Messages

Error Message    SE-CIFSSVR-3-207501:CDNFS must be configured to enable Windows sharing 
(CIFS) server. 

Explanation    A CDNFS needs to be configured and available for use so the CDS CIFS server feature can be enabled.

Recommended Action    Configure CDNFS before enabling the CIFS server.

CLEAN-AD Messages

Error Message    SE-CLEAN-AD-2-210101:Failed to make Database connection. 

Explanation    There was a problem while trying to connect to the database during AD cleanup.

Recommended Action    If this problem persists, troubleshoot the database, review the error logs, execute the show cms database command, and check the system overall status before retrying to connect to the database.

Error Message    SE-CLEAN-AD-2-210102:Problem with UNS operation. [Error].

Explanation    There was a problem while trying to connect to UNS during AD cleanup.

Recommended Action    If this problem persists, troubleshoot the cdnfs using related debug commands (such as, show stat cdnfs). Review the syslog to see if the disk hardware or RPC system has any problems. Fix the problems accordingly and retry connecting to the UNS.

Error Message    SE-CLEAN-AD-2-210103:Error with Database tables. 

Explanation    Some of the tables which are accessed by AD do not exist.

Recommended Action    Troubleshoot the database (check error logs) to see why the tables are missing. Possible reasons include upgrade or downgrade issues, disk problems, or errors in communicating with the CDSM. Fix the problem accordingly and retry.

Error Message    SE-CLEAN-AD-2-210104:Error during Memory allocation.

Explanation    T he Malloc operation failed while cleaning up AD.

Recommended Action    Retry cleaning up AD at a later time. If this problem persists, reboot the device and then retry.

Error Message    SE-CLEAN-AD-2-210107:Error getting list of delivery services for 
orphan content [Error].

Explanation    While cleaning up AD, there is orphaned content which does not have corresponding delivery services.

Recommended Action    This is a log alert. Check the specific database error and take actions accordingly. Possible actions include checking database error logs, performing CMS database maintenance, or performing recovery procedures.

Error Message    SE-CLEAN-AD-2-210108:Error in AD process.

Explanation    There was an error while trying to start or stop the AD process.

Recommended Action    This is a log alert. Execute the acquisition-distribution stop command and retry the process.

Error Message    SE-CLEAN-AD-2-210109:AD Cleanup called with incorrect argument. 
[INFO].

Explanation    AD Cleanup was called with an incorrect argument.

Recommended Action    This is a log alert. Check the arguments entered and retry.

Error Message    SE-CLEAN-AD-2-210110:AD-UNS Cleanup completed. 

Explanation    AD-UNS cleanup has completed successfully.

Recommended Action    This is log information. No action is needed.

Error Message    SE-CLEAN-AD-2-210111:UNS operation error. [INFO].

Explanation    An error occurred during UNS operation.

Recommended Action    This is a log alert. If this problem persists, check the specific CDNFS error returned, and troubleshoot CDNFS (such as, check if CDNFS is running out of space, the UNS server is down, or the disk is corrupted), and take appropriate actions before retrying the operation.

Error Message    SE-CLEAN-AD-2-210112:Error restarting AD. 

Explanation    An error occurred when trying to restart the AD process.

Recommended Action    This is a log alert. Check the errorlog and cli-util-errorlog.current commands for details about the error. Take appropriate action and retry the process.

CLI Messages

Error Message    SE-CLI-3-170000:Can't bind to SysDB at "ENABLE_CFG_PREFIX" error 
<str>.

Explanation    EXEC could not establish the connection to the data server.

Recommended Action    Log out and log in again. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-2-170001:[Procedure]: opendir([dirname]).

Explanation    opendir() failed in the EXEC.

Recommended Action    Log out and log in again. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-2-170002:[Procedure]: opendir(<dirname>).

Explanation    opendir() failed in the Exec.

Recommended Action    Log out and log in again. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-3-170003:File [filename] has problem: <error>.

Explanation    File operations (open, write) failed.

Recommended Action    Log out and log in again. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-5-170005:CDP-EV: No more interfaces running CDP - removing CDP 
process.

Explanation    This message informs the user about the Cisco Delivery Protocol (CDP) status.

Recommended Action    No action is required.

Error Message    SE-CLI-3-170006:cannot open [filename] file, errno: [dc].

Explanation    Failed to open the memory configuration template file.

Recommended Action    Retry the command. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-5-170007:Wrong arguments.

Explanation    The memory configuration program received the wrong number of arguments.

Recommended Action    Retry. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-2-170008:CLI:sysdb_bind failed in cfs_clear error = [dec].

Explanation    The CLI could not establish a connection with the data server.

Recommended Action    Retry. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-2-170009:CLI:sysdb_bind failed in cfs_sync, error = [dec].

Explanation    The CLI could not establish a connection.

Recommended Action    Retry. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-2-170010:CLI:sysdb_bind failed in cfs_mount, error = [dec].

Explanation    The CLI could not establish a connection.

Recommended Action    Retry. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-2-170011:CLI:sysdb_bind failed in cfs_unmount, error = [dec].

Explanation    The CLI could not establish a connection.

Recommended Action    Retry. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-3-170012:CLI:Copy [str] to SS failed. status = ([dec],[dec]). 
Ignore if you didn't change RealProxy config. 

Explanation    Safe manager could not copy the files.

Recommended Action    If the RealProxy configuration has not changed, ignore this message. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-3-170013:[cmd] failed:status = ([dc],[dc]).

Explanation    The command failed.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-3-170014:Your file system is unmounted, but[str] is not empty! 

Explanation    Cannot delete the mount point.

Recommended Action    Reboot the device and retry. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-3-170015:General error when deleting [str], errorno = [dc].

Explanation    Cannot delete the mount point.

Recommended Action    Reboot the device. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-2-170016:[str]: failed to pick up startup-configuration: [cmd] 
= ([dc],[dc]).

Explanation    Cannot retrieve the startup configuration.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CLI-2-170017:cannot open interface stat file to read.

Explanation    A file is missing.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-2-170018:Error when extracting interface status for [dc].

Explanation    Cannot retrieve statistics for a specific interface.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-2-170019:failed when reading interface stat file <str>.

Explanation    Failed to read the interface statistics file.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-3-170020:Can't read memory.config, so memory cap for Real Proxy 
is default <str>.

Explanation    The memory.config file could not be read.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-3-170021:Can't open file [filename] for reading: [error].

Explanation    Failed to open a file mentioned in the message.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-3-170022:CDP platform is unknown.

Explanation    Cannot find expected Cisco Discovery Protocol (CDP) information.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-3-170023:Can't open file [filename] for writing.

Explanation    Failed to open a file mentioned in the message.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-3-170024:Hostname string length is incorrect.

Explanation    Found incorrect hostname string length.

Recommended Action    Use the correct hostname length and retry.

Error Message    SE-CLI-7-170025:[CLI debug message].

Explanation    This message indicates CLI debug information.

Recommended Action    No action is required.

Error Message    SE-CLI-2-170026:Failed to delete old gateway from route table (no, no).

Explanation    The software failed when trying to remove the previously configured default gateway.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CLI-2-170027:Failed to configure the default gateway (no, no).

Explanation    The software failed when trying to configure the new default gateway.

Recommended Action    Check if the default gateway is valid and correct. If so, reconfigure it. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-2-170028:Failed to modify default gateway in sysconfig (no).

Explanation    The software failed when trying to configure the new default gateway.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CLI-2-170029:Failed to stop evaluation for <string>, ret <number>.

Explanation    Cannot stop evaluation for the application (the application is usually WMT, Real Proxy, Real Subscriber, or Multicast).

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-6-170030:Stopped evaluation for <string>.

Explanation    Stopped evaluation for application.

Recommended Action    No action is required.

Error Message    SE-CLI-3-170031:writing to mediafs split file failed. Can't open file.

Explanation    When writing new WMT and Real ratios into history, the file failed (in MEDIAFS).

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-CLI-5-170032:Syslog cleared.

Explanation    The syslog cleared.

Recommended Action    No action is required.

Error Message    SE-CLI-2-170033:populate_ds: verifier registration failed for <string> 
error = <num> (errno = <num>/<string>).

Explanation    The verifier verifies the validity of some CLIs. If this occurs, many CLIs will not work.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-CLI-3-170034:NOTE: populate_ds: unable to set default value via 
verifier for <string>, rc = <num>; continuing.

Explanation    Cannot set the default value for some configuration items.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-CLI-7-170035:<various messages>.

Explanation    This message indicates debug messages.

Recommended Action    No action is required.

Error Message    SE-CLI-2-170036:rule_operation_ds_rule(): rule table is NULL, Cannot 
read any rules.

Explanation    The rules could not be read.

Recommended Action    Retry. Contact Cisco TAC if this error persists.

Error Message    SE-CLI-2-170037:rule_operation_ds_pattern(): Invalid rules pattern, 
pattern structure corrupted.

Explanation    There is an error in the rules pattern.

Recommended Action    Retry. Contact Cisco TAC if this error persists.

Error Message    SE-CLI-2-170038:rule_item_action_string(): Invalid rules action, 
Action structure corrupted.

Explanation    The rules action could not be determined.

Recommended Action    Retry. Contact Cisco TAC if this error persists.

Error Message    SE-CLI-2-170039:print_valid_patterns(): Invalid rules action, action 
structure corrupted.

Explanation    The rules action could not be determined.

Recommended Action    Retry. Contact Cisco TAC if this error persists.

Error Message    SE-CLI-2-170040:rule_action_string(): Invalid rules action, action 
structure corrupted.

Explanation    The rules action could not be determined.

Recommended Action    Retry. Contact Cisco TAC if this error persists.

Error Message    SE-CLI-2-170041:rule_pattern_string(): Invalid rules pattern, pattern 
structure corrupted.

Explanation    There is an error in the rules pattern.

Recommended Action    Retry. Contact Cisco TAC if this error persists.

Error Message    SE-CLI-2-170042:rule_item_pattern_string(): Invalid rules pattern, 
pattern structure corrupted.

Explanation    There is an error in the rules pattern.

Recommended Action    Retry. Contact Cisco TAC if this error persists.

Error Message    SE-CLI-3-170043:ver_webserver: SIGTERM received! 

Explanation    A termination signal was received by the process.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-CLI-3-170044:ver_webserver: signal(SIGTERM, ...) failed. 

Explanation    The Process could not successfully issue a termination signal.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-CLI-5-170045:Auto registration is enabled on this interface. Either 
disable auto registration, or enable auto registration on a different interface, 
before proceeding with IP address/dhcp configuration.

Explanation    Autoregistration is currently enabled on this interface, and it must be disabled before the IP address and Dynamic Host Configuration Protocol (DHCP) configuration can be made.

Recommended Action    No action is required.

Error Message    SE-CLI-5-170046:Disabling auto registration... (num, num).

Explanation    When carrying out IP address and DHCP configuration, because the SE is not already registered with the Content Delivery System Manager (CDSM), the system disabled autoregistration.

Recommended Action    No action is required.

Error Message    SE-CLI-5-170047:Could not load kernel module [module name]. 

Explanation    The specified kernel module could not be loaded. Information provided by the CLI might be incomplete.

Recommended Action    Enter the command again. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-5-170048:Could not unload kernel module [module name]. 

Explanation    The specified kernel module could not be unloaded.

Recommended Action    Enter the command again. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-5-170049:Could not read proc interface for smbios. 

Explanation    The proc interface to smbios could not be read. The information provided by the CLI might be incomplete.

Recommended Action    Enter the command again. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-5-170050:Cisco CDS starts booting.

Explanation    This is an informational message to indicate system reboot in syslog.txt.

Recommended Action    No action is required.

Error Message    SE-CLI-5-170051:create_etc_hosts.sh: <message>.

Explanation    This is an informational message to indicate when a new IP address, hostname, or domain name is configured.

Recommended Action    No action is required.

Error Message    SE-CLI-3-170052:Failed to recreate etc_hosts <num, num>.

Explanation    The system failed to recreate an important internal file.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CLI-5-170053:Recreated etc_hosts <num, num>.

Explanation    Successfully recreated an important internal file.

Recommended Action    No action is required.

Error Message    SE-CLI-2-170054:running-config has <num> line(s).

Explanation    An error occurred in generating the running configuration. This could be from the copy running-config command or a similar command.

Recommended Action    Execute the show running-config command again. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-3-170055:Copy running-config to startup-config failed!. 
status(<num>.<num>).

Explanation    An error occurred when copying running-config to startup-config.

Recommended Action    Execute the copy running-config command again. It is mostly a transient problem. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-3-170056:Show running couldn't access data server rc=<num>.

Explanation    An error occurred when retrieving the running-configuration.

Recommended Action    Execute the copy running-config command again. It is mostly a transient problem. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-2-170057:running-config is not text 
(/tmp/last_running_config:).

Explanation    An error occured in generating the running configuration. This could be from the show running-config command or a similar command.

Recommended Action    Make sure there are no non-ASCII characters in the running configuration. Try the copy running-config command again. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-2-170058:get_config: failed to (pickup | save) initial (disk | 
CLI) configurations (num, num). 

Explanation    Encountered errors while applying the configurations specified at the bootup time.

Recommended Action    All the configurations generated should be available on the disk. Compare this configuration and the running configuration and reconfigure the CLIs that are missing in the running configuration. Finally, save the configuration to the flash memory with the copy running-config startup-config command.

Error Message    SE-CLI-3-170059:[application] could not open temp file (errmsg).

Explanation    The specified application could not open a temporary file. The reason is included in parentheses.

Recommended Action    Retry the operation (CLI configuration). If the error suggests that a volume is full, try to clean up the disk volume.

Error Message    SE-CLI-3-170060:Default Gateway CLI retry proc failed during route 
config (%d,%d).

Explanation    The background process that configures the default gateway experienced an error while attempting to configure a route. Error codes are included in parentheses.

Recommended Action    Unconfigure and reconfigure the ip default-gateway command.

Error Message    SE-CLI-3-170061:Netrcm callback could not be invoked due to fork 
failure. 

Explanation    Internal processes interested in default gateway IP changes could not be notified.

Recommended Action    Unconfigure and reconfigure the ip default-gateway command.

Error Message    SE-CLI-3-170062:CLI [identifier] will be retried in the background.

Explanation    The command identified by the identifier was not configurable but was retried in the background. This might occur if the command has a dependency that is not satisfied at the time of configuration, but might be satisfied at a later time (that is, during network connectivity).

Recommended Action    No action is required.

Error Message    SE-CLI-3-170063:Fork Failed - [additional info].

Explanation    An internal CLI process could not start another process and might be unable to complete an operation. This operation can be identified by the additional information included in the syslog message. This could be a result of system resource constraints.

Recommended Action    Unconfigure and reconfigure the associated command. Some other process might be using system resources, and it is recommended that you verify correct operation of that process. It might be helpful to inspect the syslog.

Error Message    SE-CLI-3-170064:Ipchains modification failed: [message]. 

Explanation    A change in a Web Cache Communication Protocol (WCCP) service or l4-switch configuration could not be completed successfully because an internal packet redirection rule could not be added or deleted. This message provides more specific information.

Recommended Action    Unconfigure and reconfigure the WCCP or l4-switch service. If this problem persists, try to disable and enable WCCP. If the error prints, reboot the device and reconfiguring the CLI.

Error Message    SE-CLI-5-170065:Setting <pathname> to be <type> (dhcp=<number>).

Explanation    This is an informational message. Interfaces are identified with types and recorded in the internal database.

Recommended Action    No action is required.

Error Message    SE-CLI-3-170066:CLI [cli] is deprecated [message]. 

Explanation    The CLI entered is deprecated in this release. The CLI is accepted, but it is being translated to the new format. The message provides more information specific to the CLI that is entered.

Recommended Action    Check the show running-config command to make sure the translation is the same as what is mentioned in the message. If it is not, contact Cisco TAC.

Error Message    SE-CLI-3-170067:Could not open <filename> for reading/writing: 
<error>.

Explanation    A system file that needs to be updated to modify an IP configuration could not be opened.

Recommended Action    Try the CLI again. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-4-170068:Warning! Old(<num>) != current(<num>) <filename>.

Explanation    The value read from a system file did not correspond to the value stored in the device's data repository.

Recommended Action    No action is required.

Error Message    SE-CLI-2-170069:Memory size (<num> bytes) is too small, expected 
<num>.

Explanation    The system physical memory size is smaller than expected. This usually means a Dual In-line Memory Module (DIMM) is bad. The user also sees a warning at the CLI shell.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CLI-5-170070:Memory size (<num> bytes) is too big, expected <num>.

Explanation    The system physical memory size is bigger than expected. This usually shows up on unsupported pre-FCS systems. The user should never see this.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CLI-3-170071:Failed to allocate/deallocate port for the 
[application].

Explanation    The port failed to be allocated or deallocated for the particular application. The port might already be in use.

Recommended Action    Enter the command again. Contact Cisco TAC if this occurs frequently.

Error Message    SE-CLI-3-170072:Unknown application.

Explanation    An unknown application was encountered.

Recommended Action    Enter the command again. Contact Cisco TAC if this problem occurs frequently.

Error Message    SE-CLI-3-170073:Unlock/lock operation on the file [filename] failed. 

Explanation    Cannot lock or unlock the file.

Recommended Action    Log out and log in again. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-2-170074:ver_port_channel_load: cannot open bond_mode file.

Explanation    The configuration of the load balancing method for a port channel has failed.

Recommended Action    Remove and reconfigure the port channel load balancing method and reboot. If this message persists, contact Cisco TAC.

Error Message    SE-CLI-6-170075:config.c: Failed to set signal handler for SIGPIPE to 
SIG_IGN. 

Explanation    The initialization of the CLI configuration shell experienced difficulties with a standard system call.

Recommended Action    No action is required. This information might be useful for diagnosis in the context of other problems encountered on the device.

Error Message    SE-CLI-3-170076:[cli component]: Failed to execute the command due to 
accounting problem.

Explanation    The AAA accounting of the command could not be performed; therefore, the command was not allowed to be executed.

Recommended Action    Verify that the accounting server is operating correctly and can be reached by the device, and enter the command again. If this error persists, reboot the device. Contact Cisco TAC if this problem persists.

Error Message    SE-CLI-5-170077:informational messages to find safestate failures.

Explanation    These are informational messages printed when populate_ds comes up.

Recommended Action    No action is required.

Error Message    SE-CLI-3-170078:ip route CLI retry proc failed during route config 
(%d,%d).

Explanation    The background process that configures the static route experienced an error while attempting to configure a route. Error codes are included in parentheses.

Recommended Action    Unconfigure and reconfigure the ip route command.

Error Message    SE-CLI-3-170079:Encountered incorrect advanced bandwidth 
configuration file: ss(%s).

Explanation    While saving the advanced bandwidth configuration file to a safe state disk partition, an incorrect configuration filename was found.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CLI-5-170080:This address (%s) is in the subnet that is assigned to 
another interface. 

Explanation    This address is in the subnet that is assigned to another interface.

Recommended Action    No action is required.

Error Message    SE-CLI-3-170500:Print Services running when print-services auth is 
disabled.

Explanation    Print Services (Print Spooler and Print Server) is already enabled when the print-services authentication command is about to be disabled from the CLI.

Recommended Action    Print Services are automatically disabled.

CMS Messages

Error Message    SE-CMS-7-700000:<message>. 

Explanation    An event has occurred that might be interesting for debugging.

Recommended Action    No action is required.

Error Message    SE-CMS-7-700001:<message>. 

Explanation    An event has occurred for which no further explanation has been provided.

Recommended Action    No action is required.

Error Message    SE-CMS-7-700002:<exception-name> [: <exception-message>] : 
<stacktrace>. 

Explanation    An unhandled exception has been thrown.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-CMS-0-700003:<exception-name> [: <exception-message>] : 
<stacktrace>. 

Explanation    An error has caused the program to exit.

Recommended Action    If this message occurs frequently or under specific circumstances, contact Cisco TAC.

Error Message    SE-CMS-4-701001:Software image downgrade detected. 

Explanation    A software image downgrade has been detected by the CMS software. A database downgrade is required to enable CMS services.

Recommended Action    Execute the cms database downgrade command to perform a database downgrade.

Error Message    SE-CMS-4-701002:Error executing downgrade script. 

Explanation    An error occurred while attempting to execute a CMS downgrade script.

Recommended Action    Verify that the specified script is a valid downgrade script. Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-701003:Error setting permissions for emdb data and log files. 

Explanation    An error occurred while attempting to set permissions for the database data and log files.

Recommended Action    Reload the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-701004:Synchronization of device local CLI configuration with 
device CDN configuration on CDSM has been disabled or enabled. 

Explanation    This is not an error. This message is a result of the cms lcm {enable | disable} EXEC command.

Recommended Action    No action is required.

Error Message    SE-CMS-4-704001:register(): ClassNotFoundException raised - 
[exception]. 

Explanation    JVM cannot find some unicorn class during ConsumerAdapter.register.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-704002:No BoxConfig is found in store. 

Explanation    The database has not been initialized.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-704003:Timeout when setup a rpcConnection to UNS. 

Explanation    The UNS server is not up.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705001:Store has not been initialized yet. 

Explanation    Store has not been initialized yet.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705002:No CeConfig object for [id]. 

Explanation    The CDSM does not recognize the node ID reported by the SE.

Recommended Action    Re-register the offending SE. Execute the cms deregister force command, and thence cms enable command.

Error Message    SE-CMS-4-705003:No CeStatus object for [ceConfig].

Explanation    The CDSM does not have the status for one SE with ceConfig.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705004:No report is found from SE's getUpdate request 
message. 

Explanation    The getUpdate request from SE contains nothing.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705005:report is null in SE's getUpdate request message. 

Explanation    The report contained in the SE's getUpdate request is null.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705006:Invalid report: [node-id] [node-gen-id]. 

Explanation    The report contained in the SE's getUpdate request is invalid.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705007:No CrConfig object for [id]. 

Explanation    The CDSM does not recognize the node ID reported by the SR.

Recommended Action    Re-register the offending SE. Execute the cms deregister force command, and then the cms enable command.

Error Message    SE-CMS-4-705008:No CrStatus object for [crConfig]. 

Explanation    The CDSM does not have the status for one SR with crConfig.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705009:No report is found from SR's getUpdate request 
message. 

Explanation    The getUpdate request from the SR contains nothing.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705010:report is null in SR's getUpdate request message. 

Explanation    The report contained in the SR's getUpdate request is null.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705011:Unable to preserve cli config while changing cdm role. 

Explanation    Unable to preserve CLI configuration while changing the CDM role.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705012:AControllerUtils.getCEStatus encounter Null register. 

Explanation    The register has not been initialized yet.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705013:Node [id] claims to have a gen ID [genid] which is 
higher than CDSM's [genId]. 

Explanation    The SE/SR/StandbyCDSM claims to have some data that is unknown by the primary CDSM.

Recommended Action    On the offending node (id), execute the following commands in this order: cms database delete, cms database create, and cms enable.

Error Message    SE-CMS-4-705014:Request from an unknown node [id]. 

Explanation    The CDSM does not know the node.

Recommended Action    Find the offending node, and execute the cms deregister force command on it.

Error Message    SE-CMS-4-705015:getConfigProperties(): wrong node object: [object]. 

Explanation    The getConfigProperties() received the wrong parameter.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705016:No Upgrade currently in progress for node [id]. 

Explanation    The CDSM does not have an on-going upgrade for the node.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705017:CeConfig has no clusterId: [ceConfig]. 

Explanation    The CeConfig has no clusterId.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705018:No cluster exists in store with clusterId [id]. 

Explanation    The CDSM database does not cluster the record with ID = id.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705019:getListUpdates: set size was changed strangely. 

Explanation    This is an internal error.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705020:Could not find SE named > [name]. 

Explanation    The CDSM database does not have an SE with Name = name.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705021:Could not find the CeStatus associated with 
CeConfig#[id]. 

Explanation    The CDSM database does not have a CeStatus record corresponding to CeConfig.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705022:Could not find SR named > [name]. 

Explanation    The CDSM database does not have an SR with Name = name.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705023:Could not find the CrStatus associated with 
CrConfig#[id]. 

Explanation    The CDSM database does not have a CrStatus record corresponding to CrConfig.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705024:Could not find CDSM named > [name]. 

Explanation    The CDSM database does not have a CDSM with Name = name.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705025:Could not find the CdmStatus associated with 
CdmConfig#[id]. 

Explanation    The CDSM database does not have a CdmStatus record corresponding to CdmConfig.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705026:ServantUI::whatPasswordsAreDefault received an 
unexpected Class type.

Explanation    ServantUI::whatPasswordsAreDefault received an unexpected Class type.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705027:Going to be careful and alerting the user that all 
(system and this node) passwords are default. 

Explanation    Going to be careful and alerting the user that all (system and this node) passwords are default.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705028:ConfigProperty [name] does not have a 
ConfigPropertyDefinition associated with it. Skipping... 

Explanation    The ConfigProperty is not defined.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705029:Bandwidth obj. get failed. id [id]. 

Explanation    The CDSM database does not have a bandwidth record with ID = id.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705030:Can find Config Property: [name]. 

Explanation    The CDSM database does not have a ConfigProperty record with Name = id.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705031:Atempting to add ConfigProperty [name]with invalid 
nodeType [nodeType] or sendToNode id [sendToNode]. 

Explanation    Attempting to add ConfigProperty [name]with invalid nodeType [nodeType] or sendToNode ID [sendToNode].

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705032:address [addr] has no hostname. 

Explanation    The IP address [addr] is not reverse-resolvable.

Recommended Action    Make sure there is a hostname corresponding to this IP address.

Error Message    SE-CMS-4-705033:Unable to get hostname for [addr]: [exception]. 

Explanation    The IP address [addr] is not reverse-resolvable.

Recommended Action    Make sure there is a hostname corresponding to this IP address.

Error Message    SE-CMS-4-705034:CeConfig has no clusterId: [ceConfig]. 

Explanation    The CeConfig has no clusterId.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705035:DbUpgrade Backup record status failed to be set 
properly. 

Explanation    DbUpgrade Backup record status failed to be set properly.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705036:No current DbUpgrade record found continuing with 
restore. 

Explanation    No current DbUpgrade record found continuing with restore.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705037:DbUpgrade Table doesn't exist, creating table now. 

Explanation    DbUpgrade table does not exist; creating table now.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705038:Error opening log file [exception]. 

Explanation    Cannot open validation.log for store.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705039:Test user does not exist. 

Explanation    The user does not exist in the database.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705040:Embedded database maintenance failed.

Explanation    The database fails at maintenance.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705041:No BoxConfig object exists in store 

Explanation    The database has not been initialized.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705042:Unable to get own CdmConfig object with id [id]. 

Explanation    The database does not have a CdmConfig object for ID = id.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705043:Unable to find standby CDSM's address. 

Explanation    The database does not have an IP address for the standby CDSM.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705044:No CdmConfig object for [id]. 

Explanation    The CDSM does not recognize the node ID reported by the standby CDSM.

Recommended Action    On the offending node (id), execute the following commands in this order: cms database delete, cms database create, and cms enable.

Recommended Action    Re-register the offending Standby CDSM, and execute the cms deregister force and cms enable commands.

Error Message    SE-CMS-4-705045:No CdmStatus object for [cdmConfig]. 

Explanation    The CDSM does not have the status for the standby CDSM.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705046:No report is found from CDSM's getUpdate request 
message. 

Explanation    The getUpdate request from the standby CDSM contains nothing.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705047:report is null in CDSM's getUpdate request message. 

Explanation    The report contained in the CDSM's getUpdate request is null.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705048:No host parameter found in ProbeCdm request message. 

Explanation    Another CDSM's probe message contains no parameter.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705049:CDSM assuming halted role: Multiple primary CDSMs 
detected during probe from primary CDSM at [host]. 

Explanation    Multiple primary CDSMs have been detected. Another CDSM's probe message contains no parameter.

Recommended Action    Select the CDSM that should be the primary, do: cdm role primary.

Error Message    SE-CMS-4-705050:CDSM address points to itself, trying to use next 
available backup cdm address. 

Explanation    The CDM IP on this CDSM is configured to point to itself.

Recommended Action    Change the CDM IP to the correct configuration.

Error Message    SE-CMS-4-705051:cannot get a free distribution message!

Explanation    No free distribution message is available.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-705052:Unable to send probe request to CDSM [host] 
[exception]. 

Explanation    This CDSM cannot connect to another CDSM [host].

Recommended Action    Verify the network connection between these two CDSMs is good.

Error Message    SE-CMS-4-705060:Unknown Update status: [status] returning false. 

Explanation    The CDSM does not recognize this update status.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705061:Encountered a CmdUpdate not linked to either CeConfig 
or CrConfig. 

Explanation    Encountered a CmdUpdate not linked to either CeConfig or CrConfig.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705062:Can't find object CeStatus. Invalid ID# [CeStatusId]. 

Explanation    The CeStatus object with the given ID does not exist.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705063:Can't find object CrStatus. Invalid ID# [CrStatusId]. 

Explanation    The CrStatus object with the given ID does not exist.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705064:Can't find object CdmStatus. Invalid ID# 
[CdmStatusId.] 

Explanation    The CdmStatus object with the given ID does not exist.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705065:Invalid nodeType [nodeType] in heartbeat message from 
[hostname]: [message]. 

Explanation    NodeType is not recognized by the CDSM.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705066:Invalid number of system messages. 

Explanation    There is an invalid number of system messages.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705067:Cannot connect with URL: [url]. 

Explanation    Cannot connect with the URL.

Recommended Action    Make sure the URL is valid and reachable.

Error Message    SE-CMS-4-705068:Coverage zone file [file] is not valid [error 
message]. 

Explanation    The coverage zone file is not valid.

Recommended Action    Specify the valid coverage zone file.

Error Message    SE-CMS-4-705069:Unhandled AAADomain.EntityType: [entity type]. 

Explanation    Unhandled AAA Domain Entity Type.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705070:cannot store the CLI(SE/SR) update to CDSM db. 

Explanation    Cannot store the CLI update to the CDSM database.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705071:mgmtType is not valid for MgmtIncomingType enum. 

Explanation    The value in the schema is invalid.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705072:CDSM cannot determine SE IP Address. 

Explanation    Notification failed because the CDSM cannot determine the SE IP address.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705073:An error occurred while opening the database update 
log file. 

Explanation    An error occurred while attempting to open the database upgrade or downgrade log for writing.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-705074:Version mismatch while processing update from the 
primary CDSM.Updates discarded. 

Explanation    The standby CDSM and primary CDSM must run on the same software version.

Recommended Action    Install the same version of CDS software on the primary CDSM and standby CDSM.

Error Message    SE-CMS-4-706001:Sequence IDSET not found.

Explanation    During the test for database existence, the IDSET object ID generator was not found.

Recommended Action    This is only an error if the system fails to later create the database. In this case, contact Cisco TAC.

Error Message    SE-CMS-4-706002:Sequence GENSET not found.

Explanation    During the test for database existence, the GENSET generation ID generator was not found.

Recommended Action    This is only an error if the system fails to later create the database. In this case, contact Cisco TAC.

Error Message    SE-CMS-4-706003:Table not found.

Explanation    During the test for database existence, the database table [table] was not found.

Recommended Action    This is only an error if the system fails to later create the database. In this case, contact Cisco TAC.

Error Message    SE-CMS-4-706004:Sequence IDSET not found.

Explanation    During the test for database validity, the IDSET object ID generator was not found.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-706005:Sequence GENSET not found.

Explanation    During the test for database validity, the GENSET generation ID generator was not found.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-706006:Table not found.

Explanation    During the test for database validity, the database table [table] was not found.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-706007:Error in ConsumerAdapter: cannot find class [class]. 

Explanation    ConsumerAdapter getAllSince failed to find the class object [class].

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-706008:Error in ConsumerAdapter: cannot find class [class]. 

Explanation    ConsumerAdapter getAllClass failed to find the class object [class].

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-706009:Relationship not found when loading [object] 

Explanation    An object relationship was missing during database load [object].

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-706010:Relationship set to an invalid null[object]. 

Explanation    An object relationship was found to have an unexpected empty value [object].

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-706011:Parent Relationship not found when loading [object]. 

Explanation    An object parent relationship was missing during database load [object].

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-706012:Child Relationship not found when loading [object]. 

Explanation    An object child relationship was missing during database load [object].

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-706013:Parent ID reference mismatch [object]. 

Explanation    During a parent reference removal, the parent object ID did not match [object].

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-706014:Object reference child doesn't contain inverse 
relationship for [object]. 

Explanation    During a child reference removal, the parent object ID did not match [object].

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-706015:Object reference not found in [object]. 

Explanation    During a child reference removal, the child object ID was not found [object].

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-706016:Object reference not found in [object]. 

Explanation    During a child reference removal, the child object ID was not found [object].

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-706017:Error while removing table [table]. 

Explanation    An error occurred while removing a database table [object].

Recommended Action    This is an error if the reported error is anything other than that the table does not exist.

Error Message    SE-CMS-4-706018:hasExistingStore() did not find table [table]. 

Explanation    During the check for an existing database table, an exception occurred and the table was not found [table].

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-707001:Received an update not matching its Id from CDSM. 

Explanation    The node ID in the update message does not match the SE's ID.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-707002:Cannot find the cluster this SE belongs to. 

Explanation    The SE database did not have the cluster object to which this SE belongs.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-707003:Null Replication Status Handler. 

Explanation    The replication status handler was not initialized or died.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-707004:Null FileSysHandler. 

Explanation    The module FileSysHandler was not initialized or died.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-707005:ClassNotFoundException. 

Explanation    Cannot find Class com.cisco.unicorn.schema.ClusterConfig.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-707006:Database does not have the BoxConfig object. 

Explanation    The database does not have the BoxConfig object.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-707007:Database does not have the CeConfig for this SE. 

Explanation    The CDSM has not sent a CeConfig object to this SE.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-707008:DiskQuota is null. 

Explanation    The value of disk quota does not exist.

Recommended Action    Reconfigure disk quota from GUI. Contact Cisco TAC if the warning message appears again.

Error Message    SE-CMS-4-707009:Cannot retrieve legacy value. 

Explanation    The legacy value output from the legacy script is not a long value.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-707010:Cannot delete the file. 

Explanation    Cannot delete the file.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-707011:Unable to obtain UnsAdapter reference. 

Explanation    The CMS module was unable to obtain a reference to the UnsAdapter module.

Recommended Action    Wait 30 seconds, then retry the requested operation. Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-707012:Error while invoking UNS RPC. 

Explanation    An error occurred while invoking a UNS RPC.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-709002:Cannot create or write a file. 

Explanation    The file system disallowed creating or writing a file, possibly because no disk space is left.

Recommended Action    Check the disk space to see if no space is left. Contact Cisco TAC.

Error Message    SE-CMS-4-709003:ClassNotFoundException. 

Explanation    Cannot find class.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-709004:Cannot concatenate two files into a file. 

Explanation    Cannot concatenate two files into a file, possibly because no disk space is left.

Recommended Action    Check the disk space to see if no space is left. Contact Cisco TAC.

Error Message    SE-CMS-4-709005:Cannot rename a file. 

Explanation    Cannot rename a file, possibly because no disk space is left.

Recommended Action    Check the disk space to see if no space is left. Contact Cisco TAC.

Error Message    SE-CMS-4-709006:Cannot copy a file. 

Explanation    Cannot copy a file, possibly because no disk space is left.

Recommended Action    Check the disk space to see if no space is left. Contact Cisco TAC.

Error Message    SE-CMS-4-709007:Box name, IP and/or Keepalive port are undefined. 

Explanation    Box name, IP, or keepalive port are undefined.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-709008:NULL object. 

Explanation    An unexpected null object was detected.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-709009:Wrong FileInfo type. 

Explanation    The wrong FileInfo type was detected.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-711001:Received async eProbeCdm message, skipping 

Explanation    Received incorrect envelope type in the message.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-711002:Received async eGetDeRegistration message, skipping. 

Explanation    Received incorrect envelope type in the message.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-711003:Received async ePutSoftwareUpgradeStatus message, 
skipping. 

Explanation    Received incorrect envelope type in the message.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-711004:Received async eGetRegistration message, skipping. 

Explanation    Received incorrect envelope type in the message.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-711005:CDSM received eGetNodeStatus message, skipping. 

Explanation    Received incorrect envelope type in the message.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-711006:Error in dispatching cdm request type [type]. 

Explanation    Received incorrect envelope type in the message.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-711007:Received async eProbeCdm message, skipping. 

Explanation    Received incorrect envelope type in the message.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-711008:Error in dispatching cdm request type [type]. 

Explanation    Received incorrect envelope type in the message.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-711009:SE received ePutNodeStatus message, skipping. 

Explanation    Received incorrect envelope type in the message.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-711010:SR received ePutNodeStatus message, skipping. 

Explanation    Received incorrect envelope type in the message.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-711011:RMI interface was not bound. 

Explanation    RMI not bound error. RMI is used internally only. The user will never see this error.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-711012:ConnectException while talking to other node. 

Explanation    Cannot connect to another node using RMI. RMI is used internally only. The user will never see this error.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-711013:ConnectIOException while talking to node. 

Explanation    An IO error while talking to another node using RMI. RMI is used internally only. The user will never see this error.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-712001:Cannot retrieve a reference to the Store. 

Explanation    Cannot connect to the database.

Recommended Action    Contact Cisco TAC if problem persists.

Error Message    SE-CMS-4-712002:[detail of the exception]. 

Explanation    An exception has occurred.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-712003:Invalid input: [Message]. 

Explanation    Unexpected behavior has occurred.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-712004:RPC to [A&D/acquirer/meta-replicator] failed. 

Explanation    Cannot communicate with acquisition and distribution services. This might happen if the services are down.

Recommended Action    Contact Cisco TAC if A&D services should be running and this message persists.

Error Message    SE-CMS-4-712005:Cannot retrieve a reference to DataFeedAgent. 

Explanation    Cannot connect to an internal module.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-712006:[detailed message]. 

Explanation    Issues with messaging, such as unexpected message type or content.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-712007:Replication Status Error. 

Explanation    An error occurred in getting replication status.

Recommended Action    Restart A&D by executing the acquisition-distribution stop then acquisition-distribution start command. If the error persists, reload on the problem device. Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-713001:Unable to unlink file. 

Explanation    The PCM module creates log files of changes for recovery purposes. When the current running configuration is written to startup configuration, these log files are cleared.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-713002:Failed to save cli config. 

Explanation    Periodically management service preserves CLI configuration.

Recommended Action    Check whether there are other errors related to this problem. Contact Cisco TAC.

Error Message    SE-CMS-4-713003:command failed. 

Explanation    The command received from CDSM failed for some reason. This might be caused by passing invalid hostnames or IP addresses.

Recommended Action    Check for output related to this command in the cms_* log file. Contact Cisco TAC.

Error Message    SE-CMS-4-713004:transaction log is empty in onRollbackUpdate. 

Explanation    In some cases, management service cannot complete a transaction, which results in this problem.

Recommended Action    Look for error messages during the same period of time. Contact Cisco TAC.

Error Message    SE-CMS-4-713005:FAILED to clear cli config. 

Explanation    When management service receives a full update from CDSM, it clears existing CLI settings before applying the new configuration. This operation might fail.

Recommended Action    Look for error messages during the same period of time. Contact Cisco TAC.

Error Message    SE-CMS-4-713006: ' Invalid property ...' or 'Invalid object...' 

Explanation    Management service received from a CDSM object that cannot be processed.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-713007:The active field of Bandwidth is null. 

Explanation    Invalid bandwidth settings are received from the CDSM.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-713008:CfgFtpMaxttl read from data server has changed 
size/format. 

Explanation    Incompatibility of data format and code.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-713009:CfgHttpMaxttl read from data server has changed 
size/format. 

Explanation    Incompatibility of data format and code.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-713010:Object is null. 

Explanation    Some PCM hook executes a CLI that is related to a null object.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-713011:PcmHandler is null. 

Explanation    The PCM handler is null when CMS is executing a CLI.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-713012:CLI string is null or blank. 

Explanation    Some PCM hook executes a null or blank CLI.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-713013:show running-config exits with errors. 

Explanation    The show running-config command throws an exception.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-713014:some list is null. 

Explanation    A schema object has a null list.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-713015:cannot understand CLI: [exception]. 

Explanation    LCM cannot understand a command.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-713016:Error accessing PCM state file: [file name]. 

Explanation    An error occurred while accessing a PCM state file.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-713017:CLI Error. 

Explanation    An error occurred when executing the local command.

Recommended Action    Make sure the CLI values are valid and retry. If the error persists, reload on the problem device. Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-713018:Sprayer Bandwidth Hook Error. 

Explanation    An error occurred when setting the sprayer bandwidth.

Recommended Action    Make sure the bandwidth settings are valid and retry. Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-715001:Error setting CDNFS from SE CLI. [exception details]. 

Explanation    From SE CLI, the CDNFS is set to less than the quota needed for all the assigned delivery services.

Recommended Action    Correct the CDNFS settings, delete some delivery services, or unassign the affected SE from some delivery services.

Error Message    SE-CMS-4-715002:No definition for property [property name]. 

Explanation    No definition for the configuration property.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715003:No action for property [property name]. 

Explanation    No action for the configuration property.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715004:Type of a store does not support SqlConnection. 
Therefore not creating DataBase VIEWs! 

Explanation    Type of a store does not support SqlConnection; therefore, it is not creating DataBase Views.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715005:[details of the SQL exception]. 

Explanation    An SQL exception has occurred.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715006:IP ranges overlapped. 

Explanation    Multiple multicast clouds are assigned with overlapping IP address ranges.

Recommended Action    If this is an input error, correct the IP address so no overlapping exists.

Error Message    SE-CMS-4-715007:Drop user [user name] failed. [details of the 
exception]. 

Explanation    Cannot drop a database user.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715008:Failed Drop table of [table name]. [details of the 
exception]. 

Explanation    Cannot drop a database table.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715009:Store restore failed. 

Explanation    Cannot restore the database.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715010:Store backup failed. [details of the exception]. 

Explanation    Cannot backup the database.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715011:Error while removing failed store backup. [details of 
the exception]. 

Explanation    An error occurred while removing a failed store backup.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715012:Could not create temp table for [table name]. 

Explanation    Cannot create the temp database table.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715013:Could not create replacement table [table name]. 

Explanation    Cannot create the replacement database table.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715014:Could not re-insert data into table [table name]. 

Explanation    Cannot re-insert data into the database table.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715015:Could not drop temp table for [table name]. 

Explanation    Cannot drop temp database table.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715016:Sql Exec ... [sql]. 

Explanation    An error occurred while executing the above SQL.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715017:Upgrade failed to set not null on field. 

Explanation    Cannot set null on a field.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715018:Failed to create SYS_MESSAGE_LOG index. 

Explanation    Cannot create an index for the system message log.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715019:PSqlStore VACUUM failed. 

Explanation    Cannot vacuum the database.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715020:[details of the error]. 

Explanation    An error occurred while assigning an SE to a delivery service.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715021:ClusterConfig RdToClusterMap HashMap was not found for 
[Cluster Config ID]. 

Explanation    Missing mapping for the above cluster.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715022:Delivery Service RdToClusterMap HashMap was not found 
for [Delivery Service ID]. 

Explanation    Missing mapping for the above delivery service.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715023:Unable to create ExpiresRecord for RdToClusterMap: 
[details of the exception]. 

Explanation    Unable to create an expires record for the SE assignment to delivery services.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715024:Expires record missing from store.[Delivery Service 
ID] and [Cluster Config ID]. 

Explanation    An expires record is missing from store.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715025:Could not load the node.dat file. 

Explanation    The node.dat file is either missing or invalid.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715026:SchemaSetup: No CdmConfig objects found while trying 
to set CdmConfig Id: [node ID] active. 

Explanation    Cannot find the CDSM using the node ID.

Recommended Action    Make sure the CDSM is registered. If this problem persists after successful registration, contact Cisco TAC.

Error Message    SE-CMS-4-715027:SchemaSetup: Unable to find CdmConfig object for this 
CDM; id: [node ID]. 

Explanation    Cannot find the CDSM using the node ID.

Recommended Action    Make sure the CDSM is registered. If this problem persists after successful registration, contact Cisco TAC.

Error Message    SE-CMS-4-715028:Could not load the system configuration file. 

Explanation    An error occurred loading the system configuration file.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715029:Database doesn't exist [database file name]. 

Explanation    Cannot locate the database.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715030:Address [address] is allocated multiple times, 
deallocating from SE [SE ID]. 

Explanation    Deallocating SE because of multiple IP addresses.

Recommended Action    No action is required.

Error Message    SE-CMS-4-715031:Address [address] of SE [SE ID] is not in the internal 
subnet [subnet], deallocating. 

Explanation    Deallocating SE because of an invalid subnet.

Recommended Action    No action is required.

Error Message    SE-CMS-4-715032:This primary IP [primary IP] is not unique across the 
system. 

Explanation    The primary IP set by the CLI is not unique across the system.

Recommended Action    Correct the primary IP so that it is unique.

Error Message    SE-CMS-4-715033:The CDSM encountered an error while validating 
configuration properties. 

Explanation    An error occurred while attempting to validate configuration properties.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715034:The CDSM encountered an error while attempting to 
close a database connection after validating configuration properties. 

Explanation    An error occurred while attempting to close a database connection after validating configuration properties.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715035:The CDSM encountered an error while attempting to 
remove a FactoryInfo record. 

Explanation    An error occurred while attempting to remove a FactoryInfo record while creating a new table during the database update process. FactoryInfo records are used for internal data tracking.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-715036:Invalid use-proxy-failover configuration; ignore. 

Explanation    The upgrade script encountered an invalid Service Rule configuration for use-proxy-failover. Therefore, only the action type was updated from use-proxy-failover to use-proxy.

Recommended Action    Manually fix the Service Rule configuration; check the syntax in the documentation.

Error Message    SE-CMS-4-716001:[detail of the exception]. 

Explanation    An exception has occurred.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716002:UpdateMonitor's consumer cannot be null on 
registration. 

Explanation    The UpdateMonitor's consumer cannot be null on registration.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716003:UpdateMonitor's consumer cannot be null on 
deregistration. 

Explanation    The UpdateMonitor's consumer cannot be null on deregistration.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716004:Store has more than one BoxConfig objects. 

Explanation    Store has more than one BoxConfig objects.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716005:BoxConfig is null. 

Explanation    BoxConfig is null.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716006:CeUpdateMonitor:processPostCommit(): genId is null. 

Explanation    CeUpdateMonitor:processPostCommit(): genId is null.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716007:Invalid value(s) inside [gStatusFile]. 

Explanation    There are invalid values inside the gStatus File.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716008:Unable to remove update distribution file: 
[updateFile]. 

Explanation    Unable to remove the update distribution file.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716009:Unable to connect to Host [host]:[port] [exception]. 

Explanation    Unable to connect to the host.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716010:Unable to generate certificate hash. 

Explanation    Unable to generate the certificate hash.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716011:Certificate hash not found: [certificateHash]. 

Explanation    The certificate hash was not found.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716012:Update did not die when told to. 

Explanation    The update did not die when told to.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716013:Failed to retrieve Update after [retryTimes] times. 
Cannot update [status]. 

Explanation    Failed to retrieve update after a number of times. Cannot update status.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716014:Error retrieving Update File. Upgrade Failed. 

Explanation    An error occurred retrieving the update file. The upgrade failed.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716015:Software Upgrade/downgrade status: [status] due to 
version mismatch after box reload. 

Explanation    A software upgrade or downgrade failed because of a version mismatch after device reload.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716016:Software Upgrade/downgrade status: [status]. 

Explanation    Software upgrade or downgrade status.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716017:Error creating CDSM IP file: [gCdmIpFilePath]. 

Explanation    An error occurred while creating the CDSM IP file.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716018:Aborting s/w downgrade. 

Explanation    Aborting software downgrade.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716019:Software Upgrade/Downgrade: Initiated Command + [cmd]. 

Explanation    Software upgrade or downgrade: initiated the command.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716020:Command [cmd] FAILED. 

Explanation    The command failed.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716021:Software Upgrade/Downgrade: Initiated reload force 
command. 

Explanation    Software upgrade or downgrade: initiated reload force command.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716051:Cannot get host address of primary controller from 
node.dat. 

Explanation    The node.dat file does not include the IP address of the primary CDM.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716052:Cannot save the inactive CDSM IP address to node.dat. 

Explanation    Cannot save node.dat file after it is modified, possibly because the disk space is full.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716053:Error opening file NodeState.xml. 

Explanation    Cannot open the file NodeState.xml to write, possibly because the disk space is full.

Recommended Action    No action is required.

Error Message    SE-CMS-4-716054:The number of consecutive store failure excesses 
system limits (10). 

Explanation    The database keeps failures for 10 times.

Recommended Action    The system restarts after this failure. If this problem persists after restarting, hard reboot the device.

Error Message    SE-CMS-4-716055:Current primary CDSM activation time stamp is older 
than this node's CDSM time stamp. 

Explanation    This device's clock is not synchronized with the CDM's clock.

Recommended Action    Synchronize this node's clock with the CDM's clock.

Error Message    SE-CMS-4-716056:Cannot decode the response from CDM. 

Explanation    Cannot decode the message from the CDM.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716057:Cannot get updates from the backup Controller. 

Explanation    Cannot get the update from the backup controller.

Recommended Action    Make sure the backup CDSM is on and connected.

Error Message    SE-CMS-4-716058:RPC Exception prevents this machine from getting 
update from CDM. 

Explanation    Cannot get the update from the controller due to an RPC Exception.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716059:Module thread failed. 

Explanation    A Java thread failed due to an unknown reason.

Recommended Action    No action is required. The system restarts.

Error Message    SE-CMS-4-716060:Failed to redirect stdout and stderr, using default. 

Explanation    Failed to redirect stdout and stderr.

Recommended Action    No action is required.

Error Message    SE-CMS-4-716061:Unknown Configure Property. 

Explanation    An unknown configure property is passed from the CDM.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716062:the group property does not have parent. 

Explanation    The group property does not have a parent.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716063:property is a parent, but does not hold a boolean 
value. 

Explanation    The parent property does not have a boolean value.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716064:MAC address is null. 

Explanation    The device has a null MAC address.

Recommended Action    Check the device's network configuration to see if the MAC address is set up. If so, contact Cisco TAC.

Error Message    SE-CMS-4-716065:Unable to get dns name for primary interface ip. 

Explanation    The DNS name for the primary interface IP cannot be resolved.

Recommended Action    Check the DNS server to make sure that there is an entry for the primary IP address.

Error Message    SE-CMS-4-716066:Unable to FTP file from the remote FTP server. 

Explanation    This error could be because (1) the FTP server is not a valid server, (2) the username or password is not valid, or (3) the file does not exist.

Recommended Action    Verify the FTP server, username, and password are correct, and make sure the file exists.

Error Message    SE-CMS-4-716067:rpc call to ADCertMgr server failed after certain 
tries. 

Explanation    The ADCertMgr might die or the RPC has problems connecting to it.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716068:Failed to read certificate from the file. 

Explanation    The file does include the valid certificate.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-716069:Software Update Error. 

Explanation    An error occurred when upgrading or downgrading the software.

Recommended Action    Make sure the upgrade parameters are valid and there is no network problem. Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-716070:DataFeed Error. 

Explanation    An error occurred while processing a configuration update from the CDM.

Recommended Action    Make sure there is no network problem. This error should correct itself. If not, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-716071:Restart Error. 

Explanation    There is an error that requires a restart to be corrected.

Recommended Action    If the device does not restart itself, reload the device.

Error Message    SE-CMS-4-716072:Clock mismatches between the primary CDSM and this 
device. 

Explanation    The clock on the primary CDSM and this device must be synchronized with each other.

Recommended Action    Fix the clock on either the primary CDSM or this device.

Error Message    SE-CMS-4-718001:Unable to connect to data server. 

Explanation    The process cannot connect to the data server.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-718002:Failed to get statistics. 

Explanation    Failed to get content services statistics from the data server.

Recommended Action    Make sure the required content service is enabled. If the service is enabled and the corresponding show statistics command works, contact Cisco TAC.

Error Message    SE-CMS-4-718003:Invalid configuration value(<configuration parameter 
name>). 

Explanation    The management service was given an incorrect configuration parameter.

Recommended Action    Re-enable the management service. If this does not help, reload the node. Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-718004:Data Server access error.

Explanation    The management service could not get or set information in the data server.

Recommended Action    Re-enable the management service. If this does not help, reload the node. Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-718005:Unable to find syslog fifo. 

Explanation    The management service could not open a named pipe to syslog.

Recommended Action    Reload the node. Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-718006:I/O error while accessing syslog fifo file. 

Explanation    The management service could not read from the syslog fifo file.

Recommended Action    Restart the management service. Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-718007:SE [se_id] clock is wrong or mismatch with CDM. 

Explanation    The SE clock is wrong or there is a mismatch with the CDM.

Recommended Action    Correct the SE or CDSM clock.

Error Message    SE-CMS-4-719001:Store Hook Rollback has caused an exception. 

Explanation    During a CMS store rollback, a store extension caused an error.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719002:AConnection.rollback() Rollback in progress.

Explanation    While processing a transaction, an error or constraint caused the transaction to be rolled back.

Recommended Action    This is not an error.

Error Message    SE-CMS-4-719003:AConnection processClose() caused the follow 
exception. 

Explanation    While closing the store connection, an exception was generated. See the following exception stack trace in the log.

Recommended Action    This is not an error.

Error Message    SE-CMS-4-719004:AConnection.transactionThread not set. 

Explanation    This represents the misuse of a store connection by some processing thread.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719005:AConnection.transactionThread not set. 

Explanation    This represents the misuse of a store connection by some processing thread.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719006:AConnection.transactionThread not set. 

Explanation    This represents the misuse of a store connection by some processing thread.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719007:The number of references were less than the expected. 
[reference]. 

Explanation    During object validation, the number of specified references was less than expected.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719008:The following number of references were found to be 
invalid. . [reference]. 

Explanation    During object validation, the given number of references were found to be invalid.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719009:The following number of references were found to be 
invalid. . [reference] 

Explanation    During object validation, the given number of references were found to be invalid.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719010:SQL error executing command[command]. 

Explanation    An error occurred while executing an SQL command.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719011:Force insert delete failed, [exception]. 

Explanation    During an object store forced insertion command, the object deletion failed.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719012:Exception closing reallocated connection [exception]. 

Explanation    While reconnecting to the database, the old connection produced an exception when closed.

Recommended Action    This is a warning and should be fine if the database is able to reconnect.

Error Message    SE-CMS-4-719013:Failed to connect using connect string[connection]. 

Explanation    An exception occurred while connecting to the database.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719014:Trim DELETE_SINCE log failed[exception]. 

Explanation    An exception occurred while trimming the number of records maintained in the deleted record log.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719015:Factory not found for[class]. 

Explanation    While reporting statistics, a schema class factory was not found.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719016:Error opening log file[filename]. 

Explanation    While reporting statistics, the XML log file could not be opened.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719017:Error opening log file[filename] 

Explanation    While reporting statistics, the XML log file could not be opened.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719018:Object was found to be modified at the end of 
transaction, [objectId] 

Explanation    At the end of processing a transaction, an object was found to still be modified.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719019:AStore.testModified() found modified object. 
[objectId] 

Explanation    At the end of processing a transaction, an object was found to still be modified.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719020:SqlConnection.commit() found object in modified state. 
[objectId] 

Explanation    At the end of processing a transaction, an object was found to still be modified.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719021:SqlConnection.rollback() Rollback in progress... 

Explanation    While processing a transaction, an error or constraint caused the transaction to be rolled back.

Recommended Action    This is not error.

Error Message    SE-CMS-4-719022:Sql Rollback failed. 

Explanation    An error occurred while processing a rollback.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719023:Exception closing connection [exception]. 

Explanation    An exception occurred while closing a connection.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719024:Connection reallocation failed. 

Explanation    An exception occurred while reallocating a connection.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719025:SqlConnection.generateObjId Failed [sqlcommand]. 

Explanation    The SQL command failed while generating a new unique object ID.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719026:SqlConnection.generateNum Failed [sqlcommand]. 

Explanation    The SQL command failed while generating a new unique object ID.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719027:SQL error in[sqlcommand]. 

Explanation    An error occurred while performing an SQL query.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719028:An error occurred while writing to the database update 
file log. 

Explanation    An error occurred while attempting to write to the database upgrade or downgrade log file.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719029:An error occurred while calculating a database column 
type. 

Explanation    An error occurred while attempting to calculate the type of a database column in an internal data structure.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719030:The specified downgrade script does not support the 
installed database version. 

Explanation    A downgrade script was invoked that does not support the currently installed database version.

Recommended Action    Download and execute a downgrade script that supports the previously installed software version.

Error Message    SE-CMS-4-719031:Downgrade failed. 

Explanation    An error occurred while processing a downgrade script. The system log contains additional information.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-719032:Constraint Error. 

Explanation    An error occurred while processing invalid input values.

Recommended Action    Make sure the input values are valid and retry.

Error Message    SE-CMS-4-719033:Store Error. 

Explanation    An error occurred while executing a transaction with the local data store.

Recommended Action    If this problem persists, do a reload on the problem device. If it is not corrected, contact Cisco TAC.

Error Message    SE-CMS-4-719034:DeletedSince Id Class type not found [className]. 

Explanation    An error occurred while initializing the log of deleted objects.

Recommended Action    No action is required.

Error Message    SE-CMS-4-720001:retrieveMediaFilesInChannel: null channel; using id = 
[id]. 

Explanation    The delivery service assigned to the playlist does not exist anymore.

Recommended Action    No action is required.

Error Message    SE-CMS-4-720002:retrieveMediaFilesInChannel: null root SE; using chid 
= [chId]. 

Explanation    The delivery service assigned to the playlist does not have a Root SE.

Recommended Action    Assign a Root SE to the playlist and retry.

Error Message    SE-CMS-4-720003:retrieveMediaFilesInChannel: null criteria. 

Explanation    The delivery service assigned to the playlist does not have a criteria.

Recommended Action    No action is required.

Error Message    SE-CMS-4-720004:No RoutingConfigs in CDM. 

Explanation    No RoutingConfig objects exist in the CDSM database.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-720005:Not able to get the IP Address for node [nodeId]. 

Explanation    Unable to get the IP Address for a device or node.

Recommended Action    Correct the IP Address.

Error Message    SE-CMS-4-720006:[detail of the error]. 

Explanation    An error has occurred.

Recommended Action    No action is required.

Error Message    SE-CMS-4-720007:[detail of the exception]. 

Explanation    An exception has occurred.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-720008:Invalid parent config property record.UserSelectedId 
[id] should be the same as sendToNodeId [id].

Explanation    An invalid parent configuration property record was initiated. The userSelectedId should match the sendToNodeId.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-721001:[error message]. 

Explanation    An illegal argument exception has occurred.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-721002:RMI connection failure:Rebinding. 

Explanation    Cannot bound to RMI and is retrying.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-721003:[path] is not specified in bypass set or 
serviceRightsMap. 

Explanation    Cannot find mapping to service right map.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-721004:Error during system initialization on attempt [n] of 
[m]. 

Explanation    An error occurred during system initialization.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-721005: 

Explanation    An internal thread locking check failed, but the system was able to recover by releasing the lock.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-722001:Error creating the parser. 

Explanation    Unable to create the parser when executing an API.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-722002:bean lost from session, recreating 

Explanation    This error should happen only if the session data was somehow lost, or you opened multiple browsers using the same session.

Recommended Action    Close all browser windows accessing the CDSM GUI, open a new browser window, and keep only one browser window open with the CDSM GUI.

Error Message    SE-CMS-4-722003:[detail of exception]. 

Explanation    An exception has occurred.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-722004:[detail of error]. 

Explanation    An error has occurred.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-722005:Cannot receive writer. 

Explanation    Cannot receive writer when executing the API.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-722006:API servlet sendError() received null response. 

Explanation    An error occured while running the API.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-722007:Caught exception when APIs send an error [exception]. 

Explanation    An error occured while running the API.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-722008:[pageName] caught [exception]. 

Explanation    An error has occurred.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-722009:RMI error communicating with CDM: Rebinding. 

Explanation    The GUI cannot connect to the CDM.

Recommended Action    Make sure the CMS process is running before accessing GUI.

Error Message    SE-CMS-4-722010:System command timeout error. 

Explanation    Received a timeout when executing a system command.

Recommended Action    Make sure there is no network problem and retry the command. If this problem persists, reload on the problem device. If it is not corrected, contact Cisco TAC.

Error Message    SE-CMS-4-723001:[detail of the exception]. 

Explanation    An exception has occurred.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-723002:Illegal NumberFormatException found for property [key] 
= [value], defaulting to [default]. 

Explanation    The input is not a valid number.

Recommended Action    No action is required.

Error Message    SE-CMS-4-723003:Invalid value for boolean property [key] = [value]. 

Explanation    The input is not a valid boolean.

Recommended Action    No action is required.

Error Message    SE-CMS-4-723004:IP_SOURCE_ADDR does not resolve to an IP address. 

Explanation    An invalid IP address is used.

Recommended Action    Correct the IP address.

Error Message    SE-CMS-4-723005:Missing environment variable CISCO_HOME. 

Explanation    An environment variable is not set up correctly.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-723006:Missing environment variable NODE_TYPE. 

Explanation    An environment variable is not set up correctly.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-723007:[command] passed timeout of [# of seconds], killing. 

Explanation    Cannot execute the command within the timeout period.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-723008:Exited badly [command] [exit value]. 

Explanation    The command is not executed correctly.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-723009:Unable to read seed from [random File] more than [# of 
bytes] bytes. 

Explanation    Received an error getting a seed for random numbers.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-CMS-4-723010:[details of the SAX exception]. 

Explanation    An SAX exception occurred.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-723011:Monitoring API Error. 

Explanation    An error occurred when providing monitoring statistics.

Recommended Action    Make sure the parameters to get monitoring statistics are correct and retry. If this problem persists, reload the problem device.

Error Message    SE-CMS-4-723012:Thread safety release. 

Explanation    An internal thread locking check failed, but the system was able to recover by releasing the lock.

Recommended Action    Contact Cisco TAC if you observe anomalous system behavior.

Error Message    SE-CMS-4-725001:Showing running config returns an error. 

Explanation    The showing running config command returns an error when doing LCM.

Recommended Action    Contact Cisco TAC.

Error Message    SE-CMS-4-725002:LCM Error. 

Explanation    An error occurred while processing local configuration changes on the device.

Recommended Action    Make sure the settings are valid and retry. If this problem persists, reload the problem device. If the problem is not corrected, contact Cisco TAC.

COMMONEDM Messages

Error Message    SE-COMMONEDM-4-185000:register_verifier: ver reg err (ret = [error 
number]).

Explanation    The common Extended Data Manager (EDM) could not register its verifier with the data server.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-COMMONEDM-4-185001:register_notifier: notifier reg err (ret = 
[error number]).

Explanation    The common EDM could not register its notifier with the data server.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-COMMONEDM-4-185002:get verification info err (ret=[error number]). 

Explanation    The common EDM could not get information from the data server in the verifier.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-COMMONEDM-4-185003:get notification info err (ret=[error number]).

Explanation    The common EDM could not get information from the data server in the notifier.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-COMMONEDM-4-185004:could not create /tmp/syslogd_cw2kmode (ret = 
[errorcode], [description]).

Explanation    The common EDM could not create the specified flag file. The CiscoWorks 2000 mode of syslogd remains unchanged.

Recommended Action    Try to enable and disable CiscoWorks 2000 mode again. Contact Cisco TAC if this problem persists.

Error Message    SE-COMMONEDM-4-185005:could not unlink /tmp/syslogd_cw2kmode (ret = 
[errorcode], [description)].

Explanation    The common EDM could not unlink the specified flag file. The CiscoWorks 2000 mode of syslogd remains unchanged.

Recommended Action    Try to enable and disable CiscoWorks 2000 mode again. Contact Cisco TAC if this problem persists.

Error Message    SE-COMMONEDM-4-185006:could not open /tmp/syslogd_cw2k_timezone for 
writing (ret=[errorcode], [description]).

Explanation    The common EDM could not open the time zone information file. The time zone information used by syslogd remains unchanged.

Recommended Action    Try to change the time zone information again. Contact Cisco TAC if this problem persists.

Error Message    SE-COMMONEDM-4-185007:could not write to /tmp/syslogd_cw2k_timezone.

Explanation    The common EDM could not write to the time zone information file. The time zone information used by syslogd remains unchanged.

Recommended Action    Try to change the time zone information again. Contact Cisco TAC if this problem persists.

CSE Messages

Error Message    SE-CSE-2-632000:[Procedure] - System call error:<systemcall name> <err 
msg>. 

Explanation    The system call failed. The system might be in an unstable state.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-CSE-3-633000:[Procedure] - Unable to establish connection with the 
Data Server <error_message>. 

Explanation    Failed to establish connection with the data server. This can be caused by an internal error.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-CSE-3-633001:[Procedure] - Unable to release the connection with 
the Data Server <error_message>. 

Explanation    Failed to release the connection with the data server. This can be caused by an internal error.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-CSE-3-633002:[Procedure] - Failed to receive message from the Data 
Server <error_message>. 

Explanation    Failed to receive the message from the data server. This can be caused by an internal error.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-CSE-3-633003:[Procedure] - Failed to get information from EDM 
<error_message>. 

Explanation    Failed to get information from the Extended Data Manager. This can be caused by an internal error.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-CSE-3-633004:[Procedure] - Failed to send acknowledgment to the 
Data Server <error_message>. 

Explanation    Failed to send the acknowledgment for the information received from the data server. This can be caused by an internal error.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-CSE-3-633005:[Procedure] - Failed to register with Data Manager 
<error_message>. 

Explanation    Failed to register with EDM. This can be caused by an internal error.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-CSE-3-633006:[Procedure] - Failed to unregister Data Manager 
<error_message>. 

Explanation    Failed to unregister with EDM. This can be caused by an internal error.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-CSE-3-633007:[Procedure] - Failed to release the resource acquired 
by the Data Server <error_message>. 

Explanation    Failed to unregister with EDM. This can be caused by an internal error.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-CSE-3-633008:[Procedure] - read event failed <error_message>. 

Explanation    A read event failed. This can be caused by an internal error.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-CSE-3-633009:[Procedure] Movie Streamer received error code 
<error_message>. 

Explanation    Failed to serve the request by the SE.

Recommended Action    Retry the request. If it fails to service, contact Cisco TAC.

Error Message    SE-CSE-3-633010:[Procedure] Failed to get Movie Streamer Configuration 
<error_message>. 

Explanation    Failed to get the configuration from an SE.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-CSE-3-633011:[Procedure] Failed to set Movie Streamer bandwidth 
<bw> <error_message>. 

Explanation    Failed to the change the bandwidth configuration of an SE.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-CSE-3-633012:[Procedure] Failed to start Movie Streamer 
<error_message>. 

Explanation    An error occurred while starting an SE.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-CSE-3-633013:[Procedure] Failed to stop Movie Streamer 
<error_message>. 

Explanation    An error occurred while stopping an SE.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-CSE-3-633014:[Procedure] Failed to set accesslog filename variable 
in temp file <error_message>. 

Explanation    Unable to set the accesslog filename in the temp file.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-CSE-3-633015:[Procedure] Failed to move temp file with accesslog 
filename to configuration file <error_message>. 

Explanation    Failed to move the temp file to the configuration file.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-CSE-3-633016:[Procedure] Failed to build EDM/verification ACK 
<error_mesg>. 

Explanation    Failed to build verification/EDM acknowledgment.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-CSE-4-634000:[Procedure] - System call error:<systemcall name> <err 
msg>. 

Explanation    The system call failed. The system might be in an unstable state.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-CSE-4-634001:[Procedure] - Failed to set Movie Streamer 
Caching-Proxy item in Data Server <error_msg>. 

Explanation    Failed to set a Caching-Proxy item in the data server. This can be caused by an internal error.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-CSE-4-634002:[Procedure] - Failed to move temp file with 
modification to Movie Streamer configuration file <error_message>.

Explanation    Failed to move the temp file to the configuration file.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-CSE-4-634003:[Procedure] - Failed to reload Movie Streamer 
configuration file. 

Explanation    Failed to call the SE to the configuration file. This can be due to an SE internal error.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-CSE-6-636000:[Procedure] Movie Streamer Started. 

Explanation    The SE started and is running.

Recommended Action    No action is required.

Error Message    SE-CSE-6-636001:[Procedure] Movie Streamer Stopped. 

Explanation    The SE is stopped.

Recommended Action    No action is required.

Error Message    SE-CSE-7-637000:[Movie Streamer CLI bin Debug]. 

Explanation    This is a debug message for the SE.

Recommended Action    No action is required.

DDBG Messages

Error Message    SE-DDBG-7-899998:[Description]. 

Explanation    These are debug messages generated by various modules.

Recommended Action    No action is required.

DHCP Messages

Error Message    SE-DHCP-0/1/2/3/4/5/6-191000:Description.

Explanation    This message is generated by DHCP client. The SE might fail to obtain an IP address for itself.

Recommended Action    If high priority error messages frequently occur, contact Cisco TAC.

Error Message    SE-DHCP-5-191010:Default dhcp interface is already configured. 
Skipping dhcp configuration.

Explanation    The system found that the interface on which DHCP should be enabled by default has already been configured, and skipped enabling DHCP.

Recommended Action    No action is required.

Error Message    SE-DHCP-3-191011:Failed to get default dhcp interface. 

Explanation    The system by default enables DHCP on the first interface and the software failed to get the first interface on the system.

Recommended Action    Reboot the system. Contact Cisco TAC if this problem persists.

Error Message    SE-DHCP-5-191012:DHCP enabled on the default interface. 

Explanation    The system successfully enabled DHCP on the first interface of the system.

Recommended Action    No action is required.

Error Message    SE-DHCP-3-191013:Failed to enable DHCP on the default interface 
(num,num).

Explanation    The system failed while trying to enable DHCP on the first interface.

Recommended Action    Check if the cable is connected and a DHCP server is available on the network. Contact Cisco TAC if this problem persists.

DISK Messages

Error Message    SE-DISK-1-200001:disk_check_io(): fork failed (<error>).

Explanation    Fork failed. The system is unstable.

Recommended Action    Reload. Contact Cisco TAC if this problem persists.

Error Message    SE-DISK-2-200002:disk_check_io(<device>): open (<error>).

Explanation    Possible bad disk.

Recommended Action    Execute the show disks details command to determine which disk is bad and replace the bad disk.

Error Message    SE-DISK-2-200003:disk_check_io(<device>): seek (<error>).

Explanation    Possible bad disk.

Recommended Action    Execute the show disks details command to determine which disk is bad and replace the bad disk.

Error Message    SE-DISK-2-200004:disk_check_io(<device>): read (<error>).

Explanation    Possible bad disk.

Recommended Action    Execute the show disks details command to determine which disk is bad and replace the bad disk.

Error Message    SE-DISK-2-200005:disk_check_io(<device>): bad disk.

Explanation    Possible bad disk.

Recommended Action    Execute the show disks details command to determine which disk is bad and replace the bad disk.

Error Message    SE-DISK-2-200006:disk_check_io(<device>): waitpid (<error>).

Explanation    Possible bad disk. The disk operation hangs.

Recommended Action    Execute the show disks details command to determine which disk is bad and replace the bad disk.

Error Message    SE-DISK-6-200007:disk_check_io(<device>): waitpid (<error>).

Explanation    This is a debug message.

Recommended Action    No action is required.

Error Message    SE-DISK-2-200008:<diskname> is bad. Check cable or replace it. 

Explanation    Possible bad disk.

Recommended Action    Replace the bad disk and re-install the software if the bad disk is disk00.

Error Message    SE-DISK-2-200009:read signature: open device failed: <device> <error>.

Explanation    Possible bad disk.

Recommended Action    Execute the show disks details command to determine which disk is bad and replace the bad disk. Re-install the software if the bad disk is disk00.

Error Message    SE-DISK-2-200010:read signature: seek device failed: <device> <error>. 

Explanation    Possible bad disk.

Recommended Action    Execute the show disks details command to determine which disk is bad and replace the bad disk. Re-install the software if the bad disk is disk00.

Error Message    SE-DISK-2-200011:read signature: read device failed: <device> <error>. 

Explanation    Possible bad disk.

Recommended Action    Execute the show disks details command to determine which disk is bad and replace the bad disk. Re-install the software if the bad disk is disk00.

Error Message    SE-DISK-2-200012:write signature: open device failed: <device> 
<error>. 

Explanation    Possible bad disk.

Recommended Action    Execute the show disks details command to determine which disk is bad and replace the bad disk. Re-install the software if the bad disk is disk00.

Error Message    SE-DISK-2-200013:write signature: seek device failed: <device> 
<error>. 

Explanation    Possible bad disk.

Recommended Action    Execute the show disks details command to determine which disk is bad and replace the bad disk. Re-install the software if the bad disk is disk00.

Error Message    SE-DISK-2-200014:write signature: write device failed: <device> 
<error>.

Explanation    Possible bad disk.

Recommended Action    Execute the show disks details command to determine which disk is bad and replace the bad disk. Re-install the software if the bad disk is disk00.

Error Message    SE-DISK-0-200015:First disk %s has problems. You need to check cable 
or replace it, then run "disk recover" command from CLI and re-install software. 

Explanation    Possible bad disk00.

Recommended Action    Replace disk00. Execute the disk recover command and re-install the software.

Error Message    SE-DISK-4-200016:ruby_disk: allocation data corrupted <magic> 
<version> < magic 2>. 

Explanation    Allocation data created by the disk configure command is corrupted.

Recommended Action    Execute the disk configure command again. Contact Cisco TAC if this problem persists.

Error Message    SE-DISK-3-200017:ruby_disk: physical disk setup appears to have 
changed not effecting 'disk config' changes. 

Explanation    Allocation data created by the disk configure command is not used because the disk setup has changed.

Recommended Action    Execute the disk configure command again.

Error Message    SE-DISK-2-200018:cannot create log directory <dir>: <error>. 

Explanation    Cannot create the necessary directory.

Recommended Action    Contact Cisco TAC.

Error Message    SE-DISK-2-200019:cannot create log export directory <dir>: <error>. 

Explanation    Cannot create the necessary directory.

Recommended Action    Contact Cisco TAC.

Error Message    SE-DISK-2-200020:cannot symlink from <dir> to <dir>: <error>. 

Explanation    Cannot symlink from one directory to another.

Recommended Action    Contact Cisco TAC.

Error Message    SE-DISK-2-200021:cannot create crash directory <dir>: <error>. 

Explanation    Cannot create the necessary directory.

Recommended Action    Contact Cisco TAC.

Error Message    SE-DISK-3-200022:Unknown disk-layout: sw=<num>, swstore=<num>, 
swap=<num>. 

Explanation    Cannot handle the partition layout.

Recommended Action    Contact Cisco TAC.

Error Message    SE-DISK-3-200023:Unknown disk layout: sw=<num>, swstore=<num>, 
swap=<num> state=<num>. 

Explanation    Cannot handle the partition layout.

Recommended Action    Contact Cisco TAC.

Error Message    SE-DISK-0-200024:First disk not in standard configuration. Run 'disk 
recover' command and re-install software. 

Explanation    The first disk does not have the correct partition configuration.

Recommended Action    Execute the disk recover command and re-install the software.

Error Message    SE-DISK-4-200025:diskXX is too small <size>MB (<size>MB is needed). 

Explanation    The specified disk is smaller than 2 GB. This is usually because the fiber channel configuration is not set correctly.

Recommended Action    Replace with a Cisco disk if it is a direct attached disk and not a Cisco disk. Reconfigure the fiber channel with a size greater than 2 GB if it is an FC disk.

Error Message    SE-DISK-5-200026: ' Disk configure' command has been 
[issued|canceled]. 

Explanation    The disk configuration command has been issued or canceled. This message is informational only.

Recommended Action    No action is required.

Error Message    SE-DISK-2-200027:PERC logical drive XX has problems. 

Explanation    The RAID5 logical drive on CDM4650 has a problem.

Recommended Action    Check error message 200028 to locate the physical drive and replace it, and then execute the build command.

Error Message    SE-DISK-2-200028:PERC bad physical drive(s): Adp-00(Ch-X Id-XX): 
TO-XX,Thr-XXX,Par-XXX SCSI- [XX]. 

Explanation    This is a RAID5 physical drive problem. This error message is always accompanied by error message 200027. This message identifies the logical drive number while error message 200028 identifies the physical drive slot.

Recommended Action    Replace the drive, and then execute the raid rebuild command.

Error Message    SE-DISK-0-200029:disk00 is having serious problems. Reloading.

Explanation    Disk00 or the disk drive that has SYSFS is having problems. The system is automatically rebooted.

Recommended Action    Replace the drive and then execute the disk recover or disk configure command. The user might also need to re-install the software.

Error Message    SE-DISK-2-200030:diskXX is having serious problems. Won't use it after 
reboot. 

Explanation    DiskXX is having problems. The disk is marked as bad and is not used after reboot.

Recommended Action    Replace the drive and then execute the disk add or disk configure command.

Error Message    SE-DISK-2-200031:There appear to be no SYSFS file system(s) present on 
this system. Software requires SYSFS for transaction logging and certain other 
features, and also for logging of internal status information. use "disk 
configure" or, if applicable, use the CDSM GUI to configure SYSFS disk space for 
this system. 

Explanation    See message.

Recommended Action    Execute the disk configure command.

Error Message    SE-DISK-0-200032:First disk <name> is marked as bad. 

Explanation    The first disk drive (usually disk00) has been marked as bad and is not used by the software. The device loses most of its functionality without the first disk drive.

Recommended Action    Execute the disk mark command to bring disk drive online if there is no hardware error. See error message 200015 if there is a hardware problem.

Error Message    SE-DISK-2-200033:<text>.

Explanation    Something unexpected happened.

Recommended Action    No action is required. If the system is behaving improperly, contact Cisco TAC.

Error Message    SE-DISK-3-200034:<text>.

Explanation    An unexpected memory allocation error occurred.

Recommended Action    If the system behavior is not as expected or is deficient, contact Cisco TAC.

Error Message    SE-DISK-1-200035:One or more disk partitions have severe file system 
problem. reload the system to recover from this failure. 

Explanation    A disk has a serious, but recoverable file system-related problem.

Recommended Action    Reload the system.

Error Message    SE-DISK-1-200036:<num> disks have failed. check syslog for more 
information. 

Explanation    One or more disks have failed.

Recommended Action    Try scanning for errors using the disk scan-errors disk command to see if it fixes the problem. If it does not, reformat the disk using the disk reformat disk command. If that does not help, replace the drive.

Error Message    SE-DISK-2-200037:fopen (<file_name>): <error>. 

Explanation    The system failed to open one of the critical files that maintains disk quota information for some applications.

Recommended Action    Reload the system. Contact Cisco TAC if this problem persists.

Error Message    SE-DISK-3-200038:assign_fs_space(): internal error, static_mediafs is 
set, should not be called. 

Explanation    A part of the code that should get called only when MEDIAFS is configured to use unused CDNFS space got invoked even in the case where space for MEDIAFS is allocated statically.

Recommended Action    Reload the system. Contact Cisco TAC if this problem persists.

Error Message    SE-DISK-2-200039:fopen (/etc/fsinfo.new): <error>, 
rename(/etc/fsinfo.new, /etc/fsinfo): <error>, cannot create /etc/fsinfo.new: 
<error>. 

Explanation    The system failed to open one of the critical files that maintains file system space allocation information.

Recommended Action    Reload the system. Contact Cisco TAC if this problem persists.

Error Message    SE-DISK-2-200040:handle_unuse_file system: fork(): <error>. 

Explanation    The system failed to fork a process that stops applications from using a specified file system.

Recommended Action    Reload the system. Contact Cisco TAC if this problem persists.

Error Message    SE-DISK-2-200041:file system_server: fs_svr_init() failed. 

Explanation    A critical system program failed to initialize.

Recommended Action    Reload the system. Contact Cisco TAC if this problem persists.

Error Message    SE-DISK-2-200042:statfs('<path>'): <error>. 

Explanation    The system failed to retrieve the size of the specified file.

Recommended Action    Reload the system. Contact Cisco TAC if this problem persists.

Error Message    SE-DISK-3-200043:ver_channel_quota.c:verify: v->new_len = <num>, 
expected <num>. 

Explanation    An internal variable size check failed.

Recommended Action    Reload the system. Contact Cisco TAC if this problem persists.

Error Message    SE-DISK-3-200044:ver_channel_quota.c:verify: ruby_disk fsc 
setquotasum <num> returned <num>. 

Explanation    The system failed to adjust the file system allocation based on the channel quota or subscription change.

Recommended Action    Reload the system. Contact Cisco TAC if this problem persists.

DIST Messages

Error Message    SE-DIST-2-210000:metadata sender failed in database operations. 

Explanation    A critical database error occurred in metadata sender operations.

Recommended Action    Typically, the metadata sender service restarts automatically. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-DIST-2-210001:metadata sender failed in delivery service table 
operations. 

Explanation    A critical error occurred in metadata sender operations on the delivery service table.

Recommended Action    Typically, the metadata sender service restarts automatically. Collect the technical support information and contact Cisco TAC.

Error Message    SE-DIST-2-210002:metadata sender failed in system calls. 

Explanation    A critical error occurred when the metadata sender makes systems calls (such as select).

Recommended Action    Typically, the metadata sender service restarts automatically. Collect the technical support information and contact Cisco TAC.

Error Message    SE-DIST-2-210003:metadata sender failed in initialization.

Explanation    A critical error occurred in metadata sender initialization.

Recommended Action    Typically, the metadata sender service restarts automatically. Collect the technical support information and contact Cisco TAC.

Error Message    SE-DIST-2-211000:metadata receiver failed in database operations. 

Explanation    A critical database error occurred in metadata sender operations.

Recommended Action    Typically, the metadata receiver service restarts automatically. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-DIST-2-211001:metadata receiver failed in uns operations. 

Explanation    A critical UNS error occurred in the metadata receiver operations.

Recommended Action    Typically, the metadata receiver service restarts automatically. Collect the technical support information and contact Cisco TAC.

Error Message    SE-DIST-2-211002:metadata receiver failed in system calls. 

Explanation    A critical system call error occurred in metadata receiver operations.

Recommended Action    Typically, the metadata receiver service restarts automatically. Collect the technical support information and contact Cisco TAC.

Error Message    SE-DIST-2-211003:metadata receiver failed in initialization. 

Explanation    A critical error occurred in meta sender starting phase.

Recommended Action    Typically, the meta receiver service restarts automatically. Collect the technical support information and contact Cisco TAC.

Error Message    SE-DIST-2-211004:metadata receiver full reload failed: error[error_no] 
delivery_service_id[delivery_service_id] | root_se_id[root_se_id] 
root_se_uid[root_se_uid].

Explanation    The metadata receiver failed to do a full reload of the specified delivery service from the root SE.

Recommended Action    Typically, the metadata receiver service restarts automatically. Collect the technical support information and contact Cisco TAC.

Error Message    SE-DIST-2-211005:metadata receiver saw inconsistent gen id in 
replication [req/claimed/max gen ids]. 

Explanation    The metadata receiver saw inconsistent generation IDs during metadata replication.

Recommended Action    Typically, the metadata receiver service restarts automatically. Collect the technical support information and contact Cisco TAC.

Error Message    SE-DIST-2-211006:metadata receiver failed since number of job in sync 
queue exceeded maximum limit. 

Explanation    The metadata receiver failed due to a large number of jobs in the sync queue.

Recommended Action    Typically, the metadata receiver service restarts automatically. Collect the technical support information and contact Cisco TAC.

Error Message    SE-DIST-2-212000:unicast sender failed in database operations. 

Explanation    The unicast data sender service encountered a critical database error.

Recommended Action    Execute the cms database maintenance command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-DIST-2-212001:unicast sender failed in semaphore operations. 

Explanation    The unicast data sender service encountered a critical error in semaphore/mutex deployment for its internal data structure.

Recommended Action    Execute the acquisition-distribution stop and acquisition-distribution start commands and check the syslog files. Try to correct any reported problems, if possible. Contact Cisco TAC if this problem persists.

Error Message    SE-DIST-2-212002:unicast sender failed in uns operations. 

Explanation    The unicast data sender service encountered a critical error in UNS operations.

Recommended Action    Execute the cdnfs cleanup start command and check if this problem persists. Contact Cisco TAC if this problem persists.

Error Message    SE-DIST-2-212003:unicast sender failed in bandwidth operations. 

Explanation    The unicast data sender service encountered a critical error in bandwidth control.

Recommended Action    Contact Cisco TAC.

Error Message    SE-DIST-2-212004:unicast sender failed in apache operations.

Explanation    The unicast data sender service encountered a critical error in the HTTP server library.

Recommended Action    Execute the acquisition-distribution stop and acquisition-distribution start commands and check the syslog files. Try to correct any reported problems, if possible. Contact Cisco TAC if this problem persists.

Error Message    SE-DIST-2-213000:unicast receiver failed in database operations. 

Explanation    The unicast data receiver service encountered a critical error in database operations.

Recommended Action    Execute the cms database maintenance command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-DIST-2-213001:unicast receiver failed in uns operations. 

Explanation    The unicast data receiver service encountered a critical error in UNS operations.

Recommended Action    Execute the cdnfs cleanup start command and check if this problem persists. Contact Cisco TAC if this problem persists.

Error Message    SE-DIST-2-213002:unicast receiver failed in system calls.

Explanation    The unicast data receiver service encountered a critical error in system calls.

Recommended Action    Execute the acquisition-distribution stop and acquisition-distribution start commands and check the syslog files. Try to correct any reported problems, if possible. Contact Cisco TAC if this problem persists.

Error Message    SE-DIST-2-213003:unicast receiver failed in bandwidth control. 

Explanation    The unicast data receiver service encountered a critical error in bandwidth control.

Recommended Action    Execute the acquisition-distribution stop and acquisition-distribution start commands and check the syslog files. Try to correct any reported problems, if possible. Contact Cisco TAC if this problem persists.

Error Message    SE-DIST-2-213004:unicast receiver failed in HT operations. 

Explanation    The unicast data receiver service encountered a critical error in the HTTP client library.

Recommended Action    Execute the acquisition-distribution stop and acquisition-distribution start commands and check the syslog files. Try to correct any reported problems, if possible. Contact Cisco TAC if this problem persists.

Error Message    SE-DIST-2-213005:multicast receiver lose multicast connectivity. 

Explanation    The multicast receiver does not receive advertisements or heartbeats for more than 30 minutes, which disables NACK to the multicast sender. The cause is most likely a multicast networking problem between the sender and receiver.

Recommended Action    Execute the multicast connectivity-test command to verify multicast connectivity loss and then fix the multicast networking problem for the receiver SE.

Error Message    SE-DIST-4-214001:Delivery Service Routing topology multicast sender 
transient error. 

Explanation    The delivery SR detected the multicast sender for the receive multicast cloud is the home SE itself.

Recommended Action    The system should recover from this transient error automatically. Contact Cisco TAC if this error persists or occurs frequently.

Error Message    SE-DIST-2-215000:multicast sender failed in database operations. 

Explanation    The multicast file sender service encountered a critical database error.

Recommended Action    Execute the cms database maintenance command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-DIST-2-215001:multicast sender plug-in failed in database 
operations. 

Explanation    The multicast file sender daemon service encountered a critical database error.

Recommended Action    Execute the cms database maintenance command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-DIST-2-215002: multicast sender failed in rpc operations. 

Explanation    The multicast file sender service failed to create the RPC server. It is possible that the port the RPC server wants to listen on is being used by other services.

Recommended Action    Reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-DIST-2-215003: multicast_file_sender failover/fallback service: 
[msg description].

Explanation    This message contains significant information from file the sender failover and fallback service. This class includes informational messages, such as change of a sender state (backup sender becomes active) and error messages.

Recommended Action    In case of an error condition, check if the network connectivity between the primary and backup senders is working and check if the sender service on the primary and backup sender SEs is running well. If the sender service is not running, verify that multicast is enabled on the sender SE. If there is no network connectivity problem and the sender services are running well on both sender SEs, contact Cisco TAC.

Error Message    SE-DIST-2-215004:Multicast sender cannot send file in the delivery 
service since the maximum carousel is reached.

Explanation    The multicast sender cannot send files in the delivery service because the maximum carousel is reached.

Recommended Action    Increase the maximum carousel of the multicast cloud that is associated with the delivery service.

Error Message    SE-DIST-2-216000:multicast receiver failed in database operations. 

Explanation    The multicast file receiver service encountered a critical database error.

Recommended Action    Execute the cms database maintenance command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-DIST-2-216001:multicast receiver plug-in failed in database 
operations. 

Explanation    The multicast file receiver daemon service encountered a critical database error.

Recommended Action    Execute the cms database maintenance command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-DIST-2-216002: multicast receiver failed in rpc operations. 

Explanation    The multicast file receiver service failed to create the RPC server. It is possible that the port the RPC server wants to listen on is being used by other services.

Recommended Action    Reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-DIST-2-216003:multicast receiver plug-in failed in uns operations. 

Explanation    The multicast file receiver service encountered a critical error in UNS operations. It is possible that the UNS server failed to start or is busy.

Recommended Action    Reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-DIST-2-216004:McastReceiver has high loss rate. 

Explanation    The multicast file receiver has a high loss rate and it might not be getting all the contents from the multicast file sender. This might be a result of a network problem.

Recommended Action    If there is a network-related problem, rectify it. Contact Cisco TAC if this problem persists.

Error Message    SE-DIST-2-217000:multicast system call. 

Explanation    Either the multicast file sender or multicast file receiver encountered a critical error in system calls (fork/execvp).

Recommended Action    Reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-DIST-2-217001:Failed to write in to NAS. 

Explanation    The receiver (Unicast or Multicast) is unable to write the file in to a NAS partition.

Recommended Action    Make sure the NAS device is properly running. Check for free space on this file system by executing the show statistics cdnfs command and looking at the "physical file system space free" line. If there is no free space, remove excess files on the file system (but do not remove files in the SE's directory), and assign the SE space inline with that available on NAS. Ensure that other applications are not filling up the NAS file system the SE is using. Contact Cisco TAC if this problem persists.

DNS Messages

Error Message    SE-DNS-1-221000:HTTP DNS cache out of memory. 

Explanation    The internal HTTP DNS resolution cache service has run out of memory.

Recommended Action    The HTTP DNS resolution module tries to recover, but such a problem is symptomatic of a system-wide memory shortfall. Restart the device. Contact Cisco TAC if this problem persists.

Error Message    SE-DNS-2-221001:HTTP DNS cache has no configured nameservers to query. 

Explanation    The internal HTTP DNS resolution cache service has no configured DNS nameservers to which to send queries. As a result, it is unable to do its job and many services are disrupted.

Recommended Action    Configure some DNS nameservers in the CLI.

Error Message    SE-DNS-2-221002:HTTP DNS cache has detected an inconsistent internal 
state. 

Explanation    The internal HTTP DNS resolution cache service has detected an inconsistent internal state. This message indicates some type of memory corruption. Determining if it is hardware or software requires further investigation.

Recommended Action    The HTTP DNS resolution service causes the entire proxy caching application to exit and restart. Contact Cisco TAC if this problem persists.

Error Message    SE-DNS-2-221003:HTTP DNS cache unable to open a UDP socket to send 
queries on.

Explanation    The internal HTTP DNS resolution cache service is unable to open an ephemeral UDP socket for sending DNS requests to any of the configured DNS servers.

Recommended Action    The HTTP DNS resolution module tries to recover, but such a problem is symptomatic of a system-wide network resource shortfall. Restart the device. Contact Cisco TAC if this problem persists.

Error Message    SE-DNS-6-221004:Periodic HTTP DNS statistics report. 

Explanation    Every 10 seconds a LOG_INFO priority message is sent to the syslog process that lists the average number of milliseconds taken to resolve a request, the number of requests resolved, and the number of times that the DNS service had to retry requests because of an unresponsive configured DNS server.

Recommended Action    No action is required.

Error Message    SE-DNS-5-221005:Persistent write failure on ephemeral DNS server query 
socket. 

Explanation    The HTTP caching DNS service sends resolution requests that it cannot satisfy from its cache to a configured upstream DNS server via an ephemeral UDP socket. If the service is unable to write to the socket for longer than 30 seconds, it shuts down the socket and attempts to open another. This might indicate a greater system-wide networking subsystem problem.

Recommended Action    No action is required. The cache process attempts to recover automatically.

Error Message    SE-DNS-2-221006:Unable to perform Data Server operations. 

Explanation    The system DNS cache needs to receive the configuration and receive changes to the configuration from the data server. This message indicates that it cannot do that and is not able to run. This can indicate a major system problem if it is persistent.

Recommended Action    No action is required. The cache process restarts in an attempt to recover. If this problem is persistent, reboot the system.

Error Message    SE-DNS-4-221007:DNS has not been able to PIN the entries [name] 
requested. 

Explanation    The system DNS cache allows you to configure static entries in the DNS cache. The cache has been unable to set this entry.

Recommended Action    Remove and add the entry again in the configuration.

Error Message    SE-DNS-2-221008:DNS is not able to listen on address [address] port 
[port].

Explanation    The system DNS cache has attempted to open a port on which to listen for requests and has failed. This could be a system-wide resource issue or possibly a conflict with another running application. If this occurs on the loopback address, it is a sign the system is in a indeterminate state.

Recommended Action    Change the listen parameters in the configuration. If this problem has occurred on the loopback address, you might need to reboot.

Error Message    SE-DNS-2-221009:DNS is not able to initiate a WCCP liveness.

Explanation    The system DNS cache has attempted to start communicating with WCCP and failed. This could be a system-wide resource issue or an issue with WCCP itself.

Recommended Action    The system DNS cache restarts on this error. If this error is repeated, you might need to reboot.

Error Message    SE-DNS-5-221010:Persistent write failure on ephemeral DNS server query 
socket. 

Explanation    The system DNS cache sends resolution requests that it cannot satisfy from its cache to a configured upstream DNS server via an ephemeral UDP socket. If the service is unable to write to the socket for longer than 30 seconds, it shuts down the socket and attempts to open another. This might indicate a greater system-wide networking subsystem problem.

Recommended Action    No action is required. The system DNS cache attempts to recover.

DS Messages

Error Message    SE-DS-3-230300:Unexpected msg type, ds client and server out of sync. 

Explanation    The data server client sees an unexpected message type in response from the data server. This means the communication between the data server and the client is out of sync.

Recommended Action    The client process should recover. If it does not, restart the system.

Error Message    SE-DS-3-230301:Client read error. 

Explanation    The client side gets a read error when reading from the data server.

Recommended Action    The client recovers. If it cannot recover, there might be a problem with the data server. Restart the system.

Error Message    SE-DS-3-230302:Invalid response header from data server. 

Explanation    The client gets an invalid response header from the data server. This means the communication between the data server and the client is out of sync or the data server is running in an abnormal state.

Recommended Action    The client process should recover. If it cannot recover, restart the system.

Error Message    SE-DS-3-230303:Client timed out on read. 

Explanation    The client timed out while reading from the data server.

Recommended Action    If this message persists, then the data server is having a problem. Collect the system state information and contact Cisco TAC.

Error Message    SE-DS-5-230500:remaining time is 0. 

Explanation    Calc_remaining_time sees a timeout and returns to 0.

Recommended Action    If this message persists, then there is something wrong with the data server. Restart the system.

Error Message    SE-DS-0-231000: *** FATAL ERROR. DS SERVER EXITING *** Message: 
<string> FILE: <filename> LINE: <linenumber> errno = <number>. 

Explanation    The SE data server has died.

Recommended Action    Contact Cisco TAC as soon as possible.

Error Message    SE-DS-2-231200:SYSFS is not mounted. 

Explanation    Detected no sysfs mounted and cannot dump stack trace.

Recommended Action    Verify SYSFS has been configured. If not, configure SYSFS and restart the system.

Error Message    SE-DS-2-231201:Failed to set RLIMIT_AS.

Explanation    Fail to set RLIMIT_AS.

Recommended Action    Contact Cisco TAC.

Error Message    SE-DS-2-231202:Failed to set RLIMIT_RSS.

Explanation    Fail to set RLIMIT_RSS.

Recommended Action    Contact Cisco TAC.

Error Message    SE-DS-2-231203:Data Server has too many open connections (<number>). 

Explanation    The data server has too many open connections.

Recommended Action    Contact Cisco TAC immediately.

Error Message    SE-DS-3-231300:Failed to send verification msg. 

Explanation    Failed to send message to verifier through vensock (the special socket used by the data server for the verifier or notifier or EDM).

Recommended Action    If this message persists, restart the system.

Error Message    SE-DS-3-231301:DS svr failed to set signal handler for SIGPIPE to 
SIG_IGN. 

Explanation    The data server failed to set signal handler for SIGPIPE to SIG_IGN.

Recommended Action    No action is required.

Error Message    SE-DS-2-232200:data server malloc error. 

Explanation    Failure in malloc, which might indicate a memory problem.

Recommended Action    Contact Cisco TAC.

Error Message    SE-DS-3-232300:connect error. 

Explanation    The device failed to establish a connection.

Recommended Action    Restart the system.

Error Message    SE-DS-3-232301:select error. 

Explanation    This is a select return error.

Recommended Action    No action is required.

Error Message    SE-DS-3-232302:getsockopt error. 

Explanation    This is a getsockopt return error.

Recommended Action    No action is required.

Error Message    SE-DS-3-232303:write error. 

Explanation    This is a write return error.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-DS-3-232304:read error. 

Explanation    This is a read return error.

Recommended Action    Contact Cisco TAC if this problem persists.

FFS Messages

Error Message    SE-FFS-5-660001:process info: ffs_dumper()process_id. 

Explanation    Dumper process ID and pthreadID.

Recommended Action    No action is required.

FTP Messages

Error Message    SE-FTP-0/1/2/3/4/5/6-250000:Description. 

Explanation    This message is generated by FTP.

Recommended Action    If high priority error messages frequently occur, contact Cisco TAC.

Error Message    SE-FTP_EXPORT-0/1/2/3/4/5/6-251001. 

Explanation    The native ftp_export code exposes an error or provides notice information.

Recommended Action    Contact Cisco TAC if this message appears frequently.

HTTP Messages

Error Message    SE-HTTP-3/5-270000:Proxy failover service failed in ds ops. 

Explanation    The outgoing proxy service fails in data server operations.

Recommended Action    If this message occurs occasionally, ignore it because either the service itself will retry a few times, or eventually the node manager restarts the service. Contact Cisco TAC if this message appears frequently.

Error Message    SE-HTTP-3-270001:Proxy failover service failed in sys calls: [failure 
description].

Explanation    The outgoing proxy service fails in system calls (such as select).

Recommended Action    If this message occurs occasionally, ignore it because the node manager restarts the service (and therefore retries the system calls). Contact Cisco TAC if this message appears frequently.

Error Message    SE-HTTP-3-270002:Proxy failover service timeout on system calls. 

Explanation    The outgoing proxy service fails because of a timeout in system calls (such as select).

Recommended Action    If this message occurs occasionally, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-HTTP-3-270003:Recovering from a lost data server connection. 

Explanation    The web engine lost connection to the data server and is trying to reconnect.

Recommended Action    No action is required.

Error Message    SE-HTTP-3-270004:Retrying connection to data server. 

Explanation    The web engine lost connection to the data server and is retrying to reconnect.

Recommended Action    No action is required. Contact Cisco TAC if the problem occurs frequently.

Error Message    SE-HTTP-2-270005:Retry of connection to data server did not succeed. 

Explanation    The web engine lost connection to the data server and failed to reconnect.

Recommended Action    Collect the technical support information and contact Cisco TAC.

Error Message    SE-HTTP-2-270006:Retry of connection to data server did not succeed. 

Explanation    The web engine lost connection to the data server and failed to reconnect. It is restarted by the node manager.

Recommended Action    If this message occurs frequently, collect the technical support information and contact Cisco TAC.

Error Message    SE-HTTP-2-270007:Failed to get list after 3 retries. 

Explanation    The web engine failed to get the list from the data server. It opens a new connection to get it.

Recommended Action    If this message occurs frequently, collect the technical support information and contact Cisco TAC.

Error Message    SE-HTTP-2-270008:Failed to get connect to data server after 3 retries. 

Explanation    The web engine failed to get the list from the data server. It will exit and restart by the node manager.

Recommended Action    If this message occurs frequently, collect the technical support information and contact Cisco TAC.

Error Message    SE-HTTP-2-270009:Failed to get list after 3 retries. 

Explanation    The web engine failed to get the list from the data server. It opens a new connection to get it.

Recommended Action    If this message occurs frequently, collect the technical support information and contact Cisco TAC.

Error Message    SE-HTTP-3-270010:Error message about Cisco Policy Server. 

Explanation    Cannot call the Cisco Policy Server due to a socket creation error.

Recommended Action    This is an internal error. A request continues without using guaranteed bandwidth if this occurs when starting the stream. If this occurs when stopping a stream, the teardown occurs automatically after a timeout period. If this error occurs frequently, collect the technical support information and contact Cisco TAC.

Error Message    SE-HTTP-4-270011:Warning message about memory allocation failure. 

Explanation    Failed to allocate memory for saving the Camiant request ID.

Recommended Action    This is an internal error. A request continues without using guaranteed bandwidth. If this error occurs frequently, collect the technical support information and contact Cisco TAC.

Error Message    SE-HTTP-4-270012:Warning message about identification of device 
personality. 

Explanation    Failed to identify if the device is an SR.

Recommended Action    This is an internal error and the request is ignored. If this error occurs frequently, collect the technical support information and contact Cisco TAC.

Error Message    SE-HTTP-6-270013:Informational message about request redirection. 

Explanation    The request was redirected to the URL mentioned.

Recommended Action    No action is required.

Error Message    SE-HTTP-3-270014:Warning message about Content request support. 

Explanation    The scheme present in the request is not supported.

Recommended Action    The request is ignored. If this error occurs frequently, collect the technical support information and contact Cisco TAC.

Error Message    SE-HTTP-3-270015:Warning message about Content requests. 

Explanation    The request is invalid and does not contain all relevant fields to serve a response.

Recommended Action    The request is ignored. If this error occurs frequently, collect the technical support information and contact Cisco TAC.

Error Message    SE-HTTP-3-270016:Warning message about Content lookups. 

Explanation    The content lookup failed.

Recommended Action    The request is ignored. If this error occurs frequently, collect the technical support information and contact Cisco TAC.

Error Message    SE-HTTP-3-270018:Internal error. 

Explanation    The content request failed due to an internal error.

Recommended Action    The request is ignored. If this error occurs frequently, collect the technical support information and contact Cisco TAC.

Error Message    SE-HTTP-4-270020:Warning message about caching. 

Explanation    The content caching is being done in a temporary placeholder.

Recommended Action    If this error occurs frequently, collect the technical support information and contact Cisco TAC.

Error Message    SE-HTTP-4-270021:Warning message about Content lookups. 

Explanation    The content lookup failed.

Recommended Action    The request is ignored. If this error occurs frequently, collect the technical support information and contact Cisco TAC.

Error Message    SE-HTTP-3-270038:Received an Invalid X-Forwarded-For Header. 

Explanation    We have received an invalid X-Forwarded-For Header and it contains an invalid IP address.

Recommended Action    This message occurs when clients use the X-Forwarded-For header for any application. The SE does not use the X-Forwarded-For header. Collect the technical support information and contact Cisco TAC.

HTTPS Messages

Error Message    SE-HTTPS-3-280000:https config: Host lookup failed. 

Explanation    The host lookup failed during HTTPS configuration.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-HTTPS-3-280001:https config: Failed to record the CLI. 

Explanation    Failed to save HTTPS configuration.

Recommended Action    Contact Cisco TAC if this message appears frequently.

ICAP Messages

Error Message    SE-ICAP-3-690100: Error during rpc to ICAP daemon.

Explanation    Some errors have occurred during the RPC communication between the cache process and the ICAP daemon. The [failure description] provides the actual error.

Recommended Action    Retain a copy of the cache errorlog that covers the time frame the syslog message is seen. Contact Cisco TAC if this problem persists.

Error Message    SE-ICAP-3-690110: Error parsing HTTP header from ICAP daemon.

Explanation    The cache process runs into an error while parsing the HTTP headers in the message coming from the ICAP daemon. The [failure description] provides the actual error.

Recommended Action    Retain a copy of the cache errorlog that covers the time frame the syslog message is seen. Contact Cisco TAC if this problem persists.

Error Message    SE-ICAP-3-690120: Error with ISTag from ICAP daemon.

Explanation    There are some error conditions with the operations on ISTag from the ICAP daemon. The [failure description] provides the actual error.

Recommended Action    Retain a copy of the cache errorlog that covers the time frame the syslog message is seen. Contact Cisco TAC if this problem persists.

ICP Messages

Error Message    SE-ICP-6-296001:heal_open_sock(): fail to bound to port 
<cluster_heal_port>. 

Explanation    Either failed to bind to the port <cluster_heal_port> or failed to set socket option associated with the port <clustter_heal_port>.

Recommended Action    If the messages appears frequently, contact Cisco TAC.

Error Message    SE-ICP-6-296002:Healing Mode: the corner case happens. 

Explanation    If two pending requests have almost the same expire time, the ICP module tries to attach both the pending requests to the same timer.

Recommended Action    No action is required.

Error Message    SE-ICP-6-296003:heal_set_pending_req(): pending_req is NULL. 

Explanation    The pending request list might be empty.

Recommended Action    No action is required.

Error Message    SE-ICP-6-296004:heal_init(): init free_index: num_threads = 
<num_threads>, NUM_THREADS = <NUM_THREADS>. 

Explanation    Initializes the free index array for all working threads.

Recommended Action    No action is required.

Error Message    SE-ICP-6-296005:heal_init(): No more memory 

Explanation    Failed to allocate memory for pending request and timer arrays.

Recommended Action    No action is required.

INETD Messages

Error Message    SE-INETD-0/1/2/3/4/5/6-810000:[Description]. 

Explanation    These messages are generated by inetd.

Recommended Action    If high priority error messages frequently occur, contact Cisco TAC.

LIBCMN Messages

Error Message    SE-LIBCMN-5-520001:Errorlog - messed up file name: <file name>. 

Explanation    The errorlog file naming code has done something wrong.

Recommended Action    Delete all the files in the /localX/errorlog directory.

Error Message    SE-LIBCMN-3-520002:Errorlog directory can't be created/accessed, errno 
= <number>. 

Explanation    The errorlog module has failed to create or access the directory where it places all the log messages.

Recommended Action    Contact Cisco TAC.

Error Message    SE-LIBCMN-2-520003:platform.c:platform_internal_type: can't open 
etc/MODEL: <error>. 

Explanation    The SE is not able to read the system cookie.

Recommended Action    Contact Cisco TAC.

Error Message    SE-LIBCMN-2-520004:platform.c:platform_internal_type: can't figure 
out model from /etc/MODEL. 

Explanation    The SE failed to recognize the system cookie.

Recommended Action    Contact Cisco TAC.

Error Message    SE-LIBCMN-3-520005:The standby group <group no> could not be brought 
down. 

Explanation    The interface that just failed could not be brought down.

Recommended Action    Contact Cisco TAC.

Error Message    SE-LIBCMN-3-520006:Error while removing arp entries <error> 
SE-LIBCMN-3-520006: Could not remove the arp entry for <address>. 

Explanation    The SE could not remove the ARP entries associated with the failed interface.

Recommended Action    The stale ARP entries are eventually timed out, and fresh ones are cached. If this happens every time a failover happens, contact Cisco TAC.

Error Message    SE-LIBCMN-6-520007:Could not reach the default gateway on <interface>. 

Explanation    The SE could not reach the configured default gateway through <interface>. This is an informational message.

Recommended Action    No action is required.

Error Message    SE-LIBCMN-6-520008:Standby interface <interface> of group <group no> 
could not be brought up! SE-LIBCMN-6-520008: Standby interface <interface> of 
group <group no> has either link down or is.

Explanation    Seeing more than the allowed number of errors, the SE could not bring up the <interface> while searching for a usable interface. This is an informational message.

Recommended Action    No action is required.

Error Message    SE-LIBCMN-5-520009:Standby group <group no> is up on interface 
<interface>. 

Explanation    The SE found the <interface> to be usable and brought up the standby group on this interface.

Recommended Action    No action is required.

Error Message    SE-LIBCMN-5-520010:No interface of the standby group <group no> are 
usable. 

Explanation    The SE could not find any usable interfaces in the standby group.

Recommended Action    Check if any of the member interfaces of the standby are up. If not, check for cabling, SE interface configuration, and switch configuration. If yes, the standby feature has a problem. Contact Cisco TAC.

Error Message    SE-LIBCMN-3-520011:Error while trying to reach the gateway <error>. 

Explanation    The SE encountered a problem while trying to reach the gateway.

Recommended Action    Contact Cisco TAC.

Error Message    SE-LIBCMN-3-520012:Error opening socket for checking link status 
<error> SE-LIBCMN-3-520012: SIOCDEVPRIVATE on <interface> failed while checking 
link status <error>. 

Explanation    The SE encountered a problem while trying to check the interface link status.

Recommended Action    Contact Cisco TAC.

Error Message    SE-LIBCMN-3-520013:Route <net_ip> <netmask> <gateway> could not be 
removed/added. 

Explanation    The SE encountered a problem while trying to add or remove the static IP routes after a failover link status.

Recommended Action    Contact Cisco TAC.

Error Message    SE-LIBCMN-5-520014:Could not load kernel module [module name]. 

Explanation    The specified kernel module could not be loaded. This error was most likely invoked as part of a command.

Recommended Action    Enter the command again. If this problem persists after a reload, contact Cisco TAC.

Error Message    SE-LIBCMN-5-520015:Could not unload kernel module [module name]. 

Explanation    The specified kernel module could not be unloaded. This error was most likely invoked as part of a command.

Recommended Action    Enter the command again. If this problem persists after a reload, contact Cisco TAC.

Error Message    SE-LIBCMN-5-520016:Could not read proc interface for smbios. 

Explanation    The proc interface to smbios could not be read. This error was most likely invoked as part of a command.

Recommended Action    Enter the command again. If this problem persists after a reload, contact Cisco TAC.

Error Message    SE-LIBCMN-5-520017:Could not read proc interface for cpuinfo. 

Explanation    The proc interface to cpuinfo could not be read. This error was most likely invoked as part of a command.

Recommended Action    Enter the command again. If this problem persists after a reload, contact Cisco TAC.

Error Message    SE-LIBCMN-2-520018:Could not get the memory size. 

Explanation    The SE failed to read the amount of memory available on the system. The SE might operate in a degraded mode in such a case.

Recommended Action    If this problem persists after a reload, contact Cisco TAC.

Error Message    SE-LIBCMN-5-520019:Could not read proc interface for TVOut pci 
information. 

Explanation    The proc interface used to access TV-out PCI information could not be read. This error was most likely invoked as part of a command.

Recommended Action    Enter the command again. If this problem persists after a reload, contact Cisco TAC.

Error Message    SE-LIBCMN-7-520020:system() return value is > 255. 

Explanation    system() returned a value greater than 255.

Recommended Action    No action is required.

Error Message    SE-LIBCMN-2-520021:uudecode_binary(): malloc error for out buffer, 
return NULL. 

Explanation    The SE failed to obtain memory required to perform a uudecode.

Recommended Action    If this problem persists after a reload, contact Cisco TAC.

Error Message    SE-LIBCMN-3-520022:fork_and_detach: [operation] failure: [error 
info]. 

Explanation    The specified operation failed due to the error information specified. This is most likely a resource issue.

Recommended Action    If this problem persists after a reload, contact Cisco TAC.

Error Message    SE-LIBCMN-3-520023:get_ext_ip: Got NULL pointer from data server, 
item_name= [object name]. 

Explanation    The specified object could not be retrieved from the data server. These operations are usually performed as part of a command.

Recommended Action    Enter the command again. If this problem persists after a reload, contact Cisco TAC.

Error Message    SE-LIBCMN-7-520024:<debug_print message>. 

Explanation    This is a debug message.

Recommended Action    No action is required.

Error Message    SE-LIBCMN-3-520025:validate_url_signature: <message describing 
error>. 

Explanation    This error occurred while validating the URL signature so the request for this URL failed.

Recommended Action    No action is required.

Error Message    SE-LIBCMN-6-520026:validate_url_signature: <informational message>. 

Explanation    This is an informational message indicating that the URL signature was successfully validated.

Recommended Action    No action is required.

LOGGING Messages

Error Message    SE-LOGGING-2-580001:Could not create/attach/detach shared memory area. 
Debug commands may not work: <error>. 

Explanation    The SE failed to set up a critical shared memory area.

Recommended Action    Contact Cisco TAC.

Error Message    SE-LOGGING-2-580002:Could not access/attach/detach shared memory area. 
Debug commands may not work: <error>. 

Explanation    The SE failed while accessing a critical shared memory area.

Recommended Action    Contact Cisco TAC.

Error Message    SE-LOGGING-2-580003:table pointer NULL. Module: <module>. 

Explanation    The module does not have access to a critical shared memory area.

Recommended Action    Contact Cisco TAC.

Error Message    SE-LOGGING-2-580004:Could not access/attach shared memory area. Debug 
commands may not work. 

Explanation    A module failed while accessing a critical shared memory area.

Recommended Action    Contact Cisco TAC.

Error Message    SE-LOGGING-1-580005:Sysfs space dangerously low. Either remove some 
files on the SYSFS manually, or increase the SYSFS space. 

Explanation    SYSFS is necessary for various critical functions of the system, and the system has found that the free space on the SYSFS is very low.

Recommended Action    Either remove some files on the SYSFS manually to make some free space available, or consider increasing the size of the SYSFS.

Error Message    SE-LOGGING-1-580006:Kernel crash dumps were found. Immediate attention 
required. 

Explanation    Kernel crashes happened on this system earlier.

Recommended Action    Contact Cisco TAC.

LSR Messages

Error Message    SE-LSR-2-642000:Generic Error. 

Explanation    A generic error caused a process failure. The system might be in an unstable state.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

MINGETTY Messages

Error Message    SE-MINGETTY-0/1/2/3/4/5/6-810010:[Description]. 

Explanation    These messages are generated by mingetty.

Recommended Action    If high priority error messages frequently occur, contact Cisco TAC.

MODUTILS Messages

Error Message    SE-MODUTILS-0/1/2/3/4/5/6-810020:[Description].

Explanation    These messages are generated by module utilities.

Recommended Action    If high priority error messages frequently occur, contact Cisco TAC.

NAS Messages

Error Message    SE-NAS-2-205001:NAS signature was missing. 

Explanation    A NAS signature represents NAS ownership by the SE. The signature might have been lost because of a NAS disk failure.

Recommended Action    Check whether there is NAS disk access failure on a NAS device. NAS is not attached to CDS SE devices if the signature cannot be properly written to a NAS device.

Error Message    SE-NAS-3-205002:NAS signature was missing but was rewritten. 

Explanation    A NAS signature represents NAS ownership by the SE. The signature might have been lost because a user removed it by accident.

Recommended Action    Do not touch the NAS content after it is used by CDS.

Error Message    SE-NAS-1-205003:NAS was preempted by another SE. 

Explanation    NAS was preempted by SE B when it is being used by SE A. SE A is forced to stop using NAS to avoid a NAS usage conflict, which might disrupt SE A's normal operation. NAS preemption is not the recommended action.

Recommended Action    No action is required. Make sure it is intended behavior for SE B to preempt NAS.

Error Message    SE-NAS-3-205004:NAS program can't read from stdin. 

Explanation    The NAS program cannot access stdin, therefore it cannot get "yes/no" input. Default input is "yes."

Recommended Action    Check a NAS command is running in a proper environment such that it can accept user inputs. Contact Cisco TAC if the command is entered manually.

Error Message    SE-NAS-3-205005:Can't retrieve max NAS share value. 

Explanation    This is an internal error. Cannot retrieve maximum NAS share allowed on this SE.

Recommended Action    Reload the device or re-install the CDS image.

Error Message    SE-NAS-3-205006:NAS file I/O error. 

Explanation    File operations on the NAS file failed.

Recommended Action    Check the NAS network connection or the NAS disk.

Error Message    SE-NAS-3-205007: / etc/nasinfo file content error. 

Explanation    This is an internal error.

Recommended Action    Reload the device.

Error Message    SE-NAS-3-205008:FS-manager was terminated by signal. 

Explanation    FS-manager was terminated possibly by the system or a user interrupt.

Recommended Action    No action is required.

Error Message    SE-NAS-3-205009:FS-manager failed. 

Explanation    This is an internal error.

Recommended Action    Check the error message. Reload the device if necessary.

Error Message    SE-NAS-3-205010:NAS can't be removed because cdnfs quota exceeds cdnfs 
size. 

Explanation    A NAS volume cannot be removed because the quota of all assigned delivery services exceeds remaining CDNFS space.

Recommended Action    Increase CDNFS space and modify the assigned delivery services.

Error Message    SE-NAS-3-205011:Failed to umount NAS. 

Explanation    Cannot detach the NAS volume.

Recommended Action    Check the error message.

Error Message    SE-NAS-3-205012:Failed to mount NFS NAS. 

Explanation    Cannot attach the NAS volume via NFS.

Recommended Action    Check the error message.

Error Message    SE-NAS-3-205013:Failed to mount CIFS NAS. 

Explanation    Cannot attach the NAS volume via CIFS.

Recommended Action    Check the error message.

Error Message    SE-NAS-3-205014:Attempted to mount NAS twice. 

Explanation    Attempted to attach the same NAS volume twice.

Recommended Action    Do not attach the same NAS volume twice.

Error Message    SE-NAS-3-205015:Can't retrieve eth0 mac address. 

Explanation    Cannot retrieve eth0 MAC address.

Recommended Action    Check eth0 hardware.

Error Message    SE-NAS-4-205016:Found alien signature on NAS volume. 

Explanation    The NAS volume is used by another SE.

Recommended Action    No action is required.

Error Message    SE-NAS-3-205017:NAS signature file content is invalid. 

Explanation    The NAS signature file is corrupted or has been tampered with.

Recommended Action    Check the NAS disk; do not touch NAS content when it is used by CDS.

Error Message    SE-NAS-3-205018:Multiple SEs tried to use same NAS at the same time. 

Explanation    Multiple SEs tried to use the same NAS at the same time.

Recommended Action    No action is required. Only one SE succeeds.

Error Message    SE-NAS-3-205019:Can't find unique NAS mount point. 

Explanation    This is a transient error. Cannot find a unique NAS mount point.

Recommended Action    Retry.

Error Message    SE-NAS-3-205020:Content of NAS mntpnt file is invalid. 

Explanation    The NAS mntpnt file is corrupted or has been tampered with.

Recommended Action    Check the NAS disk. Do not touch NAS content when it is used by CDS.

Error Message    SE-NAS-3-205021:Specified NAS disk size is invalid. 

Explanation    The specified NAS disk size exceeds its total volume size.

Recommended Action    Check the NAS disk size configuration.

Error Message    SE-NAS-3-205022:NAS was not really attached to the device. 

Explanation    The NAS was specified in the GUI, but was not attached to the device.

Recommended Action    Re-attach NAS and check the error message.

Error Message    SE-NAS-4-205023:NAS status was updated. 

Explanation    NAS status was updated either because NAS was attached or detached or the network connection is up or down.

Recommended Action    Do not configure NAS on CDS devices other than SEs.

Error Message    SE-NAS-3-205024:NAS status was updated and fs-manager is notified. 

Explanation    The NAS status was updated because it failed or was just recovered back online.

Recommended Action    No action is required.

Error Message    SE-NAS-5-205025:Perform NAS preemption upon request from GUI. 

Explanation    Perform NAS preemption upon a request from the GUI.

Recommended Action    No action is required.

Error Message    SE-NAS-5-205026:Maximum allowable NAS shares exceeded. 

Explanation    Cannot add new NAS because the maximum allowable NAS shares have been exceeded.

Recommended Action    Do not configure NAS shares more than the allowed number.

Error Message    SE-NAS-5-205027:Failed to register NAS health probe. 

Explanation    This is an internal error. A NAS health probe cannot be registered.

Recommended Action    Reload the device.

Error Message    SE-NAS-5-205028:NAS is not supported in certain device mode. 

Explanation    NAS is supported only on SEs.

Recommended Action    No action is required.

Error Message    SE-NAS-5-205029:Previous NAS attachment process has not finished yet. 

Explanation    The system cannot detach a NAS before a previous attachment command on this NAS has finished.

Recommended Action    Wait until the previous NAS attachment finishes before detaching it.

Error Message    SE-NAS-5-205030:Previous NAS detachment process has not finished yet. 

Explanation    The system cannot detach a NAS before a previous detachment command on this NAS has finished.

Recommended Action    Wait until the previous NAS detachment finishes before attaching it.

Error Message    SE-NAS-4-205031:A&D object scan will occur as a result of NAS 
detachment. 

Explanation    An Acquisition and Distribution (A&D) object scan aims at synchronizing the system database before a NAS volume is detached. It might take long if there are many objects in the NAS volume.

Recommended Action    No action is required. Do not interrupt the scan process; wait until it completes.

Error Message    SE-NAS-4-205032:mediafs apps will be restarted due to NAS detachment. 

Explanation    Streaming applications using MEDIAFS are restarted due to a NAS MEDIAFS detachment.

Recommended Action    Schedule streaming applications properly beforehand if you do not want the streaming services to be disrupted.

Error Message    SE-NAS-3-205033:Internal software error. 

Explanation    This is an internal software error. The software is running abnormally.

Recommended Action    Reconfigure NAS. If this fails, reload the device.

Error Message    SE-NAS-6-205034:[debug message].

Explanation    This message is used for debugging the NAS feature of CDS software.

Recommended Action    No action is required.

Error Message    SE-NAS-0-205035:A&D prescan failed during NAS detachment process. 

Explanation    The prepositioned content database needs to be updated after NAS detachment. An update failure occurred, rendering the database out of sync.

Recommended Action    Execute the acquisition-distribution database-cleanup EXEC mode command to clean up the prepositioned content database. This command could take some time to complete and should be run preferably during off-peak hours.

Error Message    SE-NAS-5-205036:Signature file on <NAS> updated with hostname 
<hostname>. 

Explanation    The hostname assigned to the device was changed. A signature file on the specified NAS was updated to reflect the change.

Recommended Action    No action is required.

Error Message    SE-NAS-3-205037:Invalid NAS configuration: server-ip, share-name, or 
network-configurations such as default-gw, domain-name-server, etc. 

Explanation    A previously configured NAS command was determined to be invalid. A sample scenario could be that a previously configured NAS hostname was not resolvable at a later time because of network connectivity loss.

Recommended Action    Check NAS and the network-related configuration on the device.

NODEMGR Messages

Error Message    SE-NODEMGR-3-330001:Memconfig: cannot get the config from flash 
[errno].

Explanation    The Memconfig tool could not be saved in configuration flash.

Recommended Action    Reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-3-330002:Memconfig: cannot get the cookie info [errno].

Explanation    The Memconfig tool could not read the cookie.

Recommended Action    Reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-3-330003:Memconfig: cannot determine platform! Assume it is 
CE507!

Explanation    The Memconfig tool could not determine the hardware device type. It is safest to assume the lowest end platform CE507.

Recommended Action    Reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-3-330004:Memconfig: cannot open [template] file, [errno].

Explanation    The Memconfig tool could not open the memconfig template file for reading.

Recommended Action    Reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-3-330005:Memconfig: cannot open [memconfig file] for write, 
[errno].

Explanation    The Memconfig tool could not open the memconfig file for writing.

Recommended Action    Reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-5-330006:External Flash operation completed.

Explanation    In case a reboot is requested when a flash operation is in progress, the reboot is delayed until the flash operation is completed. This message specifies that the flash operation completed successfully and the device will reboot shortly.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-5-330007:Flash device is busy, a software image upgrade 
might be under way, waiting for it to finish. 

Explanation    In case a reboot is requested when a flash operation is in progress, the reboot is delayed until the flash operation is completed.

Recommended Action    No action is required; wait for the flash device to be free.

Error Message    SE-NODEMGR-2-330008:Wait flash device timeout. Forcing a reboot now. 

Explanation    In case a reboot is requested when a flash operation is in progress, the reboot is delayed until the flash operation is complete. This message implies that the flash device was not free even after 15 minutes. The device is rebooted.

Recommended Action    No action is required; the device should reboot soon.

Error Message    SE-NODEMGR-0-330009:Nodemgr Exiting. 

Explanation    This message could be generated by a large set of unrecoverable error conditions. A more specific error message should precede this message.

Recommended Action    Reboot the device to recover. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-3-330010:system call '[system call]' failed, ret: [return 
code] errno: [error no] at [filename:lineno].

Explanation    A system call made by the node manager was unsuccessful. A more specific error message should precede this message.

Recommended Action    Refer to the action of the preceding more specific error message.

Error Message    SE-NODEMGR-0-330011:Rebooting the device because of fatal system 
error. 

Explanation    A system call made by the node manager was unsuccessful and the only way to recover is to reboot. A system call failed message should precede this message.

Recommended Action    No action is required; the device should reboot soon.

Error Message    SE-NODEMGR-0-330012:Could not fork process while attempting to reload: 
[errno]. 

Explanation    Forking off a process was unsuccessful during an attempted reload.

Recommended Action    The device should reboot. Power down the system if the device fails to reboot and reload it again after power up. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-5-330013:Child failed to reload successfully. 

Explanation    The child process forked to invoke reload was unsuccessful.

Recommended Action    The device should reboot. Power down the system if the device fails to reboot and attempt a reload again after power up. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-0-330014:Hard reboot the device now due to timeout. 

Explanation    This process is a safety net when all else fails and the system hangs on a reboot request. This message is printed by an alarm handler which reboots the device.

Recommended Action    The device should reboot. Power down the system if the device fails to reboot. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-5-330015:DEVICE WILL BE REBOOTED SOON. 

Explanation    A reboot has been requested and the device is undergoing a reboot soon.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-0-330016:Rebooting the device because of unrecoverable 
error. 

Explanation    An unrecoverable system error has occurred. A more specific message about the system error should precede this message. The device reboots itself.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-3-330017:open failed("/dev/null", O_RDONLY) returned 
[retcode], errno = [errno].

Explanation    An attempt to open the null device for reading failed. This signifies a more general system-level failure. Another more detailed message should accompany this message.

Recommended Action    The system is in an unstable condition. If it fails to reboot, power cycle it. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-3-330018:open [filename] failed: [errno].

Explanation    The node manager failed to open a file for logging a service's messages.

Recommended Action    No action is required; the messages are not logged. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-3-330019:dup failed: [errno].

Explanation    The node manager could not duplicate a file descriptor to redirect the messages from the application or service to the log file.

Recommended Action    No action is required; the messages are not logged. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-4-330020:chmod for [directory] failed: [error] [errno].

Explanation    The node manager could not change access permissions on the core dump directory while starting an application or service.

Recommended Action    No action is required. If the application causes a core dump, it might not be logged.

Error Message    SE-NODEMGR-4-330021:chdir to [directory] failed: [errno].

Explanation    The node manager could not change the directory for changing directory attributes.

Recommended Action    No action is required. The core dump size might not be limited. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-3-330022:setrlimit for RLIMIT_CORE failed: [errno].

Explanation    The node manager could not set the core dump limit.

Recommended Action    No action is required. The core dump size might not be limited. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-3-330023:exited pid [process id] not my direct child.

Explanation    A process has terminated but was not directly spawned by the node manager.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-5-330024:Service [program name] exited normally with code 
[status]

Explanation    The specified service has exited as expected.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-3-330025:Service [program name] died due to signal [signal 
no]:[signal name].

Explanation    The specified service that was started by the node manager died unexpectedly due to the specified signal.

Recommended Action    If this message occurs periodically, ignore it. If it appears frequently, contact Cisco TAC.

Error Message    SE-NODEMGR-3-330026:Service [program name] died abnormally with status 
[status no].

Explanation    The specified service that was started by the node manager died due to some abnormal condition.

Recommended Action    If this message occurs periodically, ignore it. If it appears frequently, contact Cisco TAC.

Error Message    SE-NODEMGR-5-330027:pid [process id] exits

Explanation    A process has exited.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-5-330028:healthprobe pid [process id] exits.

Explanation    A health probe process has exited.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-3-330029:Someone is trying to kill with pid of [process id]. 

Explanation    This message is printed if a kill attempt was made with a zero or non-negative process ID.

Recommended Action    If this message occurs periodically, ignore it. If it appears frequently, contact Cisco TAC.

Error Message    SE-NODEMGR-5-330030:Process [process id] killed with SIGTERM does not 
return within [millisecond] ms, trying to use SIGKILL.

Explanation    The node manager attempted to terminate a process using SIGTERM, but the process did not return in the specified time.

Recommended Action    The process is killed using SIGKILL. If this message occurs periodically, ignore it. If it appears frequently, contact Cisco TAC.

Error Message    SE-NODEMGR-3-330031:cannot kill process with pid: [process id].

Explanation    An unsuccessful attempt was made by the node manager to kill the specified process using SIGKILL.

Recommended Action    If a service is affected, try disabling and enabling the service. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-5-330032:Stopping service: [service name]. 

Explanation    The node manager is stopping the specified service.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-5-330033:Service [service name] is already stopped.

Explanation    An attempt was made to stop a service that is already stopped.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-0-330034:fork failed while stopping service [service name]. 

Explanation    The node manager could not fork a child process while attempting to stop a service.

Recommended Action    No action is required; the device will reboot.

Error Message    SE-NODEMGR-3-330035:Service [service name] cannot be successfully 
stopped. 

Explanation    The node manager was unable to stop the specified service.

Recommended Action    No action is required; the device will reboot.

Error Message    SE-NODEMGR-5-330036:Stop service [service name] using: [command] with 
pid: [process id].

Explanation    This message is a notification from the node manager that the specified service is being stopped.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-3-330037:execve error while trying to stop service: 
[error]. 

Explanation    The node manager could not execute the stop command to stop a service.

Recommended Action    No action is required. The node manager kills the process directly.

Error Message    SE-NODEMGR-3-330038:Start service fork failed: [error]. 

Explanation    The node manager could not fork a process to start a service.

Recommended Action    No action is required. An attempt is made again to start the service after some time.

Error Message    SE-NODEMGR-3-330039:Service [service] has not returned within [sec] 
seconds. Will try stopping it. 

Explanation    The node manager has started a service, but it has not responded for the specified seconds. It is probably waiting on some resource.

Recommended Action    No action is required; the node manager stops the process and restarts it later.

Error Message    SE-NODEMGR-5-330040:Started service [service] using: [cmd] with pid: 
[pid].

Explanation    The node manager has started the specified service.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-3-330041:Start Service execve error: [error]

Explanation    The node manager tried to start a service but the execve command failed. Restart of the service is attempted.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-3-330042:Service start program [program] does not exist? 
err: [errorno]

Explanation    While checking service support binaries, the node manager could not find a specific binary to start a service.

Recommended Action    The software installation could be incomplete or corrupt. Reinstall the software using the copy ftp install or other installation commands. Refer to the software upgrade and installation documentation.

Error Message    SE-NODEMGR-3-330043:Service stop program [program] does not exist? 
err: [errorno].

Explanation    While checking service support binaries, the node manager could not find a specific binary to stop a service.

Recommended Action    The software installation could be incomplete or corrupt. Reinstall the software using the copy ftp install or other installation commands. Refer to the software upgrade and installation documentation.

Error Message    SE-NODEMGR-3-330044:Service health_probe program [program] does not 
exist? err: [errno]

Explanation    While checking service support binaries, the node manager could not find a specific binary to stop a service.

Recommended Action    The software installation could be incomplete or corrupt. Reinstall the software using the copy ftp install or other installation commands. Refer to the software upgrade and installation documentation.

Error Message    SE-NODEMGR-0-330045:Rebooting the device because service [service] is 
dead.

Explanation    A critical service has died. The only way to recover is by rebooting the device.

Recommended Action    No action is required; the device should reboot shortly. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-3-330046:Stopping the service [service] because it is 
restarting too often. 

Explanation    The specified service has had to be restarted by the node manager more often than normally required.

Recommended Action    Check the related config or show commands to see why the service could not run normally. Check if there is a core dump generated in the /local1/ directory. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-3-330047:Rebooting the device because service [service] 
keeps restarting.

Explanation    The node manager has restarted the specified service more often than normally required. The recommended way to resolve this problem is to reboot the device.

Recommended Action    No action is required; the device will reboot automatically. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-5-330048:DEBUG: respawn_count = [count], period: [secs].

Explanation    The node manager had to restart a process. This is the count-th restart of the process. The process was restarted within seconds.

Recommended Action    No action is required. The node manager might restart certain processes. If a process restarts very often, contact Cisco TAC.

Error Message    SE-NODEMGR-6-330049:Service [service] is dead, do nothing according to 
the config. 

Explanation    The specified service is not operational and, according to specifications, should not be restarted.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-3-330050:Fork for health_probe failed: [error].

Explanation    The node manager could not fork to run a health probe.

Recommended Action    Contact Cisco TAC if this error appears frequently.

Error Message    SE-NODEMGR-5-330051:Start health_probe for service [service] using: 
[cmd] with pid: [pid].

Explanation    The node manager has started a heath probe service.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-3-330052:health probe execve error: [error].

Explanation    The node manager could not execute running a health probe.

Recommended Action    Contact Cisco TAC if this error appears frequently.

Error Message    SE-NODEMGR-3-330053:Health_probe for service [service] timed out. 

Explanation    The health probe for the specified service timed out.

Recommended Action    No action is required. Contact Cisco TAC if this error appears frequently.

Error Message    SE-NODEMGR-5-330054:DEBUG: service health probe took [sec] seconds to 
return.

Explanation    The health probe started by the node manager has completed in the given number of seconds.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-3-330055:Health probe for service [service] failed, ret 
code: [error]. 

Explanation    The health probe for the specified service failed. The node manager will stop and restart the service if needed.

Recommended Action    No action is required. Contact Cisco TAC if this error appears frequently.

Error Message    SE-NODEMGR-3-330056:Health probe exit with a signal [signal].

Explanation    A health probe started by the node manager has exited with a specified signal. The node manager stops the service and restarts it if needed.

Recommended Action    No action is required. Contact Cisco TAC if this error appears frequently.

Error Message    SE-NODEMGR-3-330057:Health_probe for service [service] died abnormally 
with status [error].

Explanation    A health probe started by the node manager has exited in an abnormal fashion. The node manager stops the service and restarts it if needed.

Recommended Action    No action is required. Contact Cisco TAC if this error appears frequently.

Error Message    SE-NODEMGR-7-330058:nodemgr: entering start_loop.

Explanation    This is a debug message printed by the node manager. The node manager has started running its main code loop.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-5-330059: Switching to run level [runlevel no].

Explanation    This is a debug message printed by the node manager. The node manager is switching its run level and starts services based on the new run level.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-3-330060:waitpid returns error: [error no]. 

Explanation    The node manager was interrupted by an error when waiting in waitpid.

Recommended Action    No action is required; it is normal to see this message during a reboot.

Error Message    SE-NODEMGR-3-330061:no child alive. 

Explanation    The node manager was waiting in waitpid and was awakened because there were no children of the node manager left alive.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-7-330062:loop_counter = [count], child_pid = [pid].

Explanation    This is a debug message printed by the node manager. It provides information useful for development purposes.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-3-330063:Putenv error adding new path [path].

Explanation    The node manager could not set the path environment variable. The node manager might not be able to properly start services.

Recommended Action    Reboot the device. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-1-330064:[frame]: [function name]([arg1], [arg2], [arg3], 
[arg4].

Explanation    The node manager has received a critical signal and quits. The information printed is a backtrace of the calls made by the node manager.

Recommended Action    The node manager should restart automatically and the device might run in an unstable mode. Reboot the device.

Error Message    SE-NODEMGR-1-330065:nodemgr: signal [signal no] received.

Explanation    The node manager has received a critical signal. A backtrace should follow this message and the node manager will most likely exit.

Recommended Action    The node manager should restart automatically and the device might run in an unstable mode. Reboot the device.

Error Message    SE-NODEMGR-3-330066:Failed to open [error], ret : [ret code], errno: 
[error no].

Explanation    The node manager could not open the specified file. The node manager might not be able to get information about local disks, and services might be affected.

Recommended Action    The system might be in an unstable condition. Reboot the device.

Error Message    SE-NODEMGR-3-330067:Too many local disks.

Explanation    The node manager found too many disks attached to the system. The user is probably using an unsupported configuration.

Recommended Action    Check the disk configuration. Disconnect any unsupported drives and reboot.

Error Message    SE-NODEMGR-5-330068:personality_allows_service called for [service].

Explanation    The personality_allows_service was called for the specified service.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-5-330069:Device personality: [device personality], Service 
personality = [service personality].

Explanation    The device personality and the service personality are printed for debugging purposes.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-4-330070:nodemgr:touch_service_enabled_flag_file: could 
create /tmp/service_enabled ([service]).

Explanation    The node manager could not create a flag file for the specified service.

Recommended Action    This could be a transient problem. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-4-330071:nodemgr:touch_service_enabled_flag_file: could 
not open [filename] ([error]).

Explanation    The node manager could not open a flag file for the specified service.

Recommended Action    This could be a transient problem. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-4-330072:nodemgr:delete_service_enabled_flag_file: could 
not unlink [filename]([error]).

Explanation    The node manager could not delete the flag file for the specified service.

Recommended Action    This could be a transient problem. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-0-330073:execl /sbin/mingetty failed: ret [return code], 
errno: [errno].

Explanation    The mingetty process could not be started for debugging.

Recommended Action    This is an internal debugging message. If you see this error, contact Cisco TAC.

Error Message    SE-NODEMGR-5-330074:No personality found, setting default personal\ 
ity: SE. 

Explanation    The node manager could not determine the device type SE, SR, or CDSM. It is assumed to be an SE.

Recommended Action    Contact Cisco TAC.

Error Message    SE-NODEMGR-5-330075:Reboot requested by CLI. 

Explanation    A reboot was requested using the reload command.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-3-330076:Reboot requested by [reboot source]. 

Explanation    A reboot was requested by the specified source.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-5-330077:Reload config requested by [source]. 

Explanation    A request was made by the specified source to reload the node manager configuration file.

Recommended Action    Contact Cisco TAC.

Error Message    SE-NODEMGR-5-330078: Stop all services (except mingetty) requested by 
[source]. 

Explanation    A request was made by the specified source to the node manager to stop all services.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-5-330079:Shutdown requested by [source]. 

Explanation    The specified source has requested the device be shut down.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-5-330080:[source] requests start service [service].

Explanation    The specified source has requested the node manager to start the specified service.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-5-330082:[source] requests stop service [service]. 

Explanation    The specified source has requested the node manager to stop the service.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-5-330084:[source] requests restart service [service]. 

Explanation    The specified source has requested the node manager to restart the specified service.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-5-330085:[source] requests forcestart service [service].

Explanation    The specified source has requested the node manager to start the specified service irrespective of the device mode.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-3-330087:Error in read the req, errno: [error].

Explanation    The node manager server could not read a request.

Recommended Action    The requesting application should print out a separate error that specifies the action to be carried out.

Error Message    SE-NODEMGR-3-330088:Failed to set NONBLOCK for new_fd, ret [status], 
errno [error code].

Explanation    The node manager could not set the NONBLOCK attribute for a new file descriptor. The corresponding request is not processed by the node manager.

Recommended Action    The requesting application should print out a separate error that specifies the action to be carried out.

Error Message    SE-NODEMGR-3-330089:Check request, select: ret = [status], errno = 
[error].

Explanation    A select call failed while checking a request in the node manager server. The request is not processed.

Recommended Action    The requesting application should print out a separate error that specifies the action to be carried out.

Error Message    SE-NODEMGR-0-330090:Memory allocation of [size] bytes failed! 
Rebooting the device. 

Explanation    The node manager could no allocate memory. The device might be in an unstable state.

Recommended Action    No action is required; the device reboots itself.

Error Message    SE-NODEMGR-5-330091:ERROR: Not enough timer allocated, should never 
happen.

Explanation    The node manager has run out of timer resources. The device might be under a heavy load. Additional memory is allocated for the timer.

Recommended Action    It might be safer to reduce the load on the device. Contact Cisco TAC if this message appears frequently.

Error Message    SE-NODEMGR-3-330092:Program error, cancel NULL timer.

Explanation    A call was made to cancel a timer that does not exist.

Recommended Action    No action is required. Contact Cisco TAC if this message appears frequently.

Error Message    SE-NODEMGR-3-330093:Program error, cancel failed.

Explanation    The node manager was called to cancel a timer; however, the timer was not found in the node manager's internal structures. This might be because of a memory corruption.

Recommended Action    Reboot the device. Contact Cisco TAC if this message appears frequently.

Error Message    SE-NODEMGR-3-330094:killtilldead: iteration count reached 60, bailing 
out (trying to kill [process] ...).

Explanation    The node manager was unable to successfully disable the specified process. The process could still be running and might interfere with normal device operations.

Recommended Action    Reboot the device. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-3-330095:parse_get_str: cannot allocate more memory! 

Explanation    The node manager could not allocate memory while parsing its configuration file.

Recommended Action    Do not reboot the device. Contact Cisco TAC.

Error Message    SE-NODEMGR-0-330096:REBOOT BOX NOW FROM WITHIN nodemgr_clt!!! 

Explanation    A reload request was made to the node manager client.

Recommended Action    No action is required. The device reboots itself.

Error Message    SE-NODEMGR-6-330097:Created codecoverage directory [dir path].

Explanation    This message is informational only to indicate a code coverage directory is created for a process. This should only be seen when running an instrumented image.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-6-330098:Error while creating codecoverage directory [dir 
path].

Explanation    The code coverage directory could not be created successfully for a process. This should only be seen for an instrumented image. If this message appears, the process will not work properly.

Recommended Action    Contact the code coverage change owner to investigate the problem.

Error Message    SE-NODEMGR-5-330099:Service log cleanup: [error].

Explanation    There was a problem while cleaning up the service logs. The node manager might not be able to clean up the service logs, but they are taken care of by the logging monitor.

Recommended Action    No action is required.

Error Message    SE-NODEMGR-3-330100:nodemgr_accept_req: accept(...): [error].

Explanation    The accept system call unexpectedly failed.

Recommended Action    No action is required. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-0-330101:Nodemgr appears to have got restarted.Rebooting 
the system to avoid further damage, and to stabilize the system. 

Explanation    The node manager appears to have restarted for some reason. The node manager restarts are associated with multiple instances of same services running on the system, and this results in various problems. Reboot to stabilize the system.

Recommended Action    No action is required. Contact Cisco TAC if this problem persists.

Error Message    SE-NODEMGR-3-330102:Could not create a flag to indicate that the 
nodemgr has been started. This may result in nodemgr deaths going undetected. 

Explanation    The software maintains a flag to detect node manager deaths, but for some reason this flag could not be created. With this problem, if the node manager cannot restart, several instances of various services would run resulting in problems.

Recommended Action    Reload the system, and verify that the error message does not appear upon reboot. Contact Cisco TAC if this message appears frequently.

Error Message    SE-NODEMGR-3-330103:Raise alarm fail <service name> <alarm ID> 
(retcode).

Explanation    The node manager detected a problem but could not raise an alarm.

Recommended Action    Check the syslog files for other alarm-related failures. Alarm information on the device could be inconsistent and a reload of the device might be required for recovery.

Error Message    SE-NODEMGR-3-330104:Raise alarm fail <service name> <alarm ID> 
(retcode).

Explanation    The node manager could not clear an alarm.

Recommended Action    Check the syslog files for other alarm related failures. Alarm information on the device could be inconsistent and a reload of the device might be required for recovery.

Error Message    SE-NODEMGR-3-330105:Keepalive problem: <description> [retcode].

Explanation    The node manager had a problem while sending keepalives to the Node Health Manager. The description provides specific details.

Recommended Action    Check the syslog files for other alarm-related failures. Reboot the device if the keepalive alarm has been raised.

NTP Messages

Error Message    SE-NTP-0/1/2/3/4/5/6-340000:[failure-description].

Explanation    The native Linux NTP code exposes errors, notices, or information.

Recommended Action    If error messages occur, check the NTP configuration or device configuration. Contact Cisco TAC if this message appears frequently.

Error Message    SE-NTP-5-340001:[host-ip/name]: not a valid host address.

Explanation    An invalid NTP server host address was specified.

Recommended Action    Retry with the correct NTP server host address.

Error Message    SE-NTP-5-340002:Maximum NTP servers reached. 

Explanation    The maximum NTP server limit has been reached.

Recommended Action    Do not configure more NTP servers than the maximum limit.

Error Message    SE-NTP-5-340003:Must configure NTP servers before enabling NTP 
service. 

Explanation    No NTP server has been configured, so NTP service cannot be enabled.

Recommended Action    Configure at least one NTP server before enabling NTP service.

Error Message    SE-NTP-3-340004:failed to open ntp [drift|config] file: [file-name].

Explanation    The NTP service failed to open an NTP drift file or configuration file.

Recommended Action    Check the NTP configuration and check the device status. Contact Cisco TAC if this message appears frequently.

Error Message    SE-NTP-3-340005:nodemgr failed to start/stop ntpd.

Explanation    An NTP command failed because the node manager could not start or stop NTPD.

Recommended Action    Check the device status and reload the device. Contact Cisco TAC if this message appears frequently.

Error Message    SE-NTP-3-340006:failed to retrieve configuration from data-server, 
error=[err_code].

Explanation    The NTP command failed because the NTP binary could not retrieve a configuration from the data server.

Recommended Action    Check the device status and reload the device. Contact Cisco TAC if this message appears frequently.

Error Message    SE-NTP-7-340007:[NTP debugging message].

Explanation    The message indicates NTP debugging information.

Recommended Action    No action is required.

Error Message    SE-NTP-5-340008:failed to pre-sync system time and calendar. 

Explanation    The configured NTP servers fail to roughly synchronize the system time.

Recommended Action    Check whether the configured NTP servers are valid and reachable. Manually execute the ntpdate [ntp_server] command to find the reason for the failure.

PAM Messages

Error Message    SE-PAM-3-345000:Wrong authentication method to get authentication 
debugging.

Explanation    The wrong authentication method has been selected for debugging.

Recommended Action    If an error message occurs, reconfigure the authentication method parameters, check the disks' condition, and set the debug option again by executing command debug authentication. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-3-345001:Can't open file (TACACS+).

Explanation    The system fails to open the configuration file etc/pam.d/ce_http_tacacs_config for request authentication via the TACACS+ protocol. The parameters of authentication cannot be saved.

Recommended Action    Check the TACACS+ protocol configuration and check the condition of the disks. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-3-345002:Can't open file (RADIUS).

Explanation    The system fails to open configuration the file etc/pam.d/ce_http_radius_config for request authentication via the RADIUS protocol. The parameters of authentication cannot be saved.

Recommended Action    Check the RADIUS protocol configuration and check the condition of the disks. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-3-345003:Can't open file (NTLM).

Explanation    The system fails to open the configuration file etc/pam.d/ce_http_ntlm_config for request authentication via the NTLM protocol. The parameters of authentication cannot be saved.

Recommended Action    Check the NTLM protocol configuration and check the condition of the disks. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-3-345004:Can't open file (LDAP).

Explanation    The system fails to open the configuration file etc/pam.d/ce_http_ldap_config for request authentication via the LDAP. The parameters of authentication cannot be saved.

Recommended Action    Check the LDAP configuration and check the condition of the disks. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-3-345005:Wrong option to set authentication debugging.

Explanation    The wrong authentication method has been set for debugging.

Recommended Action    Reconfigure authentication method parameters, check the disks' condition, and set the debug option again by executing the debug authentication command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-3-345006:can't open /tmp/user_authenticate_debug file to set 
debugging information.

Explanation    The system fails to open the configuration file tmp/user_authenticate_debug file to set debugging information.

Recommended Action    Check the disks' condition and set the debug option again by executing the debug authentication command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-3-345007:can't open /tmp/request_authenticate_debug file to set 
debugging in formation.

Explanation    The system fails to open the configuration file tmp/request_authenticate_debug file to set debugging information.

Recommended Action    Check the disks' condition and set the debug option again by executing the debug authentication command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-2-345008:cannot create directory for pam module <reason> 

Explanation    The system does not have a configured TMP directory.

Recommended Action    The system has a serious software image setup or configuration problem. Contact Cisco TAC.

Error Message    SE-PAM-3-345009:Can't open /etc/pam.d/content_engine_config file.

Explanation    The system fails to open the configuration file etc/pam.d/content_engine_config for the user's authentication. The parameters of authentication cannot be saved.

Recommended Action    Check the user's authentication configuration and check the condition of the disks. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-2-345010:cannot create log directory for pam module.

Explanation    The system does not have a configured TMP directory.

Recommended Action    The system has a serious software image setup or configuration problem. Contact Cisco TAC.

Error Message    SE-PAM-3-345011:can't open /tmp/user_authenticate_stats file.

Explanation    The system fails to open the authentication statistical file /tmp/user_authenticate_stats to reset statistics. The statistical information of authentication cannot be cleared.

Recommended Action    Check the condition of the disks. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-3-345012:can't open /tmp/user_authenticate_stats file to report 
statistics.

Explanation    The system fails to open the authentication statistical file /tmp/user_authenticate_stats to update statistics. The statistical information of authentication is lost.

Recommended Action    Check the condition of the disks and check if the system's /tmp directory exists. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-2-345013:Failed to lock authentication statistical file.

Explanation    The system fails to set the software lock for the request authentication statistical file to reset statistics. The statistical information of the request authentication cannot be cleared.

Recommended Action    Check the condition of the disks. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-2-345014:cannot create log directory for pam module.

Explanation    The system does not have a configured TMP directory.

Recommended Action    The system has a serious software image setup or configuration problem. Contact Cisco TAC.

Error Message    SE-PAM-3-345015:can't open /tmp/user_ldap_stats file.

Explanation    The system fails to open the LDAP authentication statistical file /tmp/user_ldap_stats to reset statistics. The statistical information of LDAP authentication cannot be cleared.

Recommended Action    Check the condition of the disks and check if the system's /tmp directory exists. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-3-345016:can't open /tmp/user_radius_stats file.

Explanation    The system fails to open the RADIUS authentication statistical file /tmp/user_radius_stats to reset statistics. The statistical information of RADIUS authentication cannot be cleared.

Recommended Action    Check the condition of the disks and check if the system's /tmp directory exists. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-3-345017:can't open /tmp/user_tacacs_stats file.

Explanation    The system fails to open the TACACS+ authentication statistical file /tmp/user_tacacs_stats to reset statistics. The statistical information of TACACS+ authentication cannot be cleaned.

Recommended Action    Check the condition of the disks, check if the system's /tmp directory exists. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-3-345018:can't open /tmp/user_ntlm_stats file.

Explanation    The system fails to open the NTLM authentication statistical file /tmp/user_ntlm_stats to reset statistics. The statistical information of NTLM authentication cannot be cleared.

Recommended Action    Check the condition of the disks and check if the system's /tmp directory exists. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-3-345019:Failed to write authentication statistical file.

Explanation    The system fails to write the authentication statistical file to reset statistics. The statistical information of authentication method cannot be cleared.

Recommended Action    Check the condition of the disks and check if the system's /tmp directory exists. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-3-345020:Failed to close authentication statistical file after 
writing.

Explanation    The system fails to close the authentication statistical file after statistics are cleared.

Recommended Action    Check the condition of the disks and check if the system's /tmp directory exists. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-3-345021:Failed to lock authentication statistical file.

Explanation    The system fails to lock the authentication statistical file after statistics are cleared.

Recommended Action    Check the condition of the disks and check if the system's /tmp directory exists. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-2-345022:Failed to lock authentication statistical file.

Explanation    The system fails to lock the authentication statistical file to display statistics.

Recommended Action    Check the condition of the disks and check if the system's /tmp directory exists. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-3-345023:Unknown authentication method.

Explanation    The wrong authentication method has been selected.

Recommended Action    Reconfigure the authentication method parameters, and check the disks' condition. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-3-345024:Filed to open statistical file for authentication.

Explanation    The system fails to open the authentication statistical file. An authentication method's statistics cannot be displayed.

Recommended Action    Check an authentication method's configuration. Check the condition of the disks. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-3-345025:Statistical file is corrupted.

Explanation    The authentication statistical file has incorrect or corrupted information.

Recommended Action    Check an authentication method's configuration, check the condition of the disks, clear authentication statistical information, and display statistical information again. If the statistical file is corrupted again, contact Cisco TAC, otherwise continue to authenticate the users.

Error Message    SE-PAM-3-345026:Failed to close authentication statistical file after 
reading.

Explanation    The system fails to close the authentication statistical file after statistics are displayed.

Recommended Action    Check the condition of the disks and check if the system's /tmp directory exists. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-3-345027:A field of Statistical file is corrupted.

Explanation    The authentication statistical file has incorrect or corrupted information in one of the fields.

Recommended Action    Check an authentication method's configuration, check the condition of the disks, clear authentication statistical information, and display statistical information again. If the statistical file is corrupted again, contact Cisco TAC, otherwise continue to authenticate the users.

Error Message    SE-PAM-3-345028:Failed to read authentication statistical file.

Explanation    The system fails to read the authentication statistical file to display statistics.

Recommended Action    Check the condition of the disks and check if the system's /tmp directory exists. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-3-345029:tmp directory doesn't exist.

Explanation    The system does not have a configuredTMP directory.

Recommended Action    The system has serious software image setup or configuration problems. Contact Cisco TAC.

Error Message    SE-PAM-3-345030:Failed to lock authentication statistical file.

Explanation    The system fails to lock the authentication statistical file to display statistics.

Recommended Action    Check the condition of the disks and check if the system's /tmp directory exists. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PAM-3-345031:Can't open /etc/pam.d/print_services file.

Explanation    The system fails to open the configuration file etc/pam.d/print_services for the print service's authentication. The parameters of authentication cannot be saved.

Recommended Action    Check the print service's authentication configuration, and check the condition of the disks. Contact Cisco TAC if this message appears frequently.

PARSER Messages

Error Message    SE-PARSER-3-350000:sysdb_bind failed: <str>.

Explanation    The parser server failed to establish a connection with the data server, which contains the configuration registry.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350001:Bad arguments to parser_malloc.

Explanation    The parser attempted to allocate zero size memory.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350002:Bad pointer to parser_free.

Explanation    The parser got the null memory pointer to be freed.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350003:parser_free before parser_malloc called.

Explanation    The parser attempted to free the memory that was never allocated.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350004:Bad magic in parser free 1.

Explanation    An unexpected magic number was detected in the memory block.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350005:Bad magic in parser free 2.

Explanation    An unexpected magic number was detected in the memory block.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350006:sysdb_item_set of uint32 <str><dc><str>.

Explanation    Cannot set an item in the data server

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350007:wrong sysdb datatype at <str>, <dc>, expect <dc>.

Explanation    Did not receive expected "packed" type data from the data server.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350008:sysdb_directory_get_last: '<error>'.

Explanation    The sysdb_directory_get_last() failed.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350009:sysdb_item_set of packed <str> : <str>.

Explanation    An error occurred while retrieving data from the data server.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350010:sysdb_iterator_create: <str>.

Explanation    An error occurred while setting an option in the data server.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350011:sysdb_iterator_next_data() failed <str>.

Explanation    An error occurred in a data server operation.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350012:sysdb_iterator_free: <str>.

Explanation    An error occurred in a data server operation.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350013:<str> Option Not Present:<str>, <str>.

Explanation    Expected options are not present.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350014:<str>: new_cmd buffer null <function name>.

Explanation    Expected options are not present.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350015:<str> No endcoption mark for <hex>: <str>.

Explanation    No endcoption mark was found.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350016:<str> Incomplete endcoption mark for <hex>: <str>.

Explanation    An incomplete endcoption mark found.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350017:<str>:invalid input (no 'B'): '<str>'.

Explanation    An invalid coption was found.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350018:<str>: bgcoption missing ',' after id: '<str>'.

Explanation    The bgcoption is missing.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350019:<str>: bgcoption missing ',' after type: '<str>'.

Explanation    The bgcoption is missing.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350020:<str>: bgcoption missing ',' after path count: 
'<str>'.

Explanation    The bgcoption is missing.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350021:<str>:no nxcoption:'<str>'.

Explanation    An expected nxcoption is missing.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350022:<str>: incorrect nested coption:'<str>'.

Explanation    An incorrect nested coption was found.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350023:<str>: invalid NXCOPTION mark:'<str>'.

Explanation    An incorrect NXCOPTION mark was found.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350025:<str>: Possible loop detected in command '<str>'.

Explanation    A loop was detected in the command.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350026:<str>: missing equal '<' in sysdb string '<str>' 
for command '<str>'.

Explanation    Missing equal in sysdb string found.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350027:<str>: Unknown object type <dec> in nvgen_command.

Explanation    An unknown object type was found.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350028:<str>: Unknown object type <dec> in replace_type.

Explanation    An unknown object type was found.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350029:Invalid object format '<str>'.

Explanation    An invalid object type was found.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350030:<str>: debug registration failed: <dc>.

Explanation    The debug registration failed.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350031:sysdb_bind: <str>.

Explanation    An error occurred while establishing the connection with the data server.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350033:Shell failed to write msg to parser server. 

Explanation    The shell failed to write a message to the parser server.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350034:parser_server reconnect succeeded.

Explanation    The shell process was able to reconnect to the parser server.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-2-350035:parser_server reconnect failed. 

Explanation    The shell failed to connect to the parser server.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-3-350036:Endoption doesn't match! <dec>.

Explanation    Syntax error: Endoption does not match.

Recommended Action    Retry the command. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-PARSER-4-350037:Too many parser jobs from the shells. save your work 
and exit some shells. 

Explanation    The number of sessions that are concurrently submitted to the parsing requests have reached 34 or above.

Recommended Action    This is a warning message. Try limiting the number of login sessions to the SE to 34 or fewer.

Error Message    SE-PARSER-3-350038:Too many parser jobs from the shells. Have to 
restart. 

Explanation    The parser server process has been terminated as the number of concurrent parsing requests exceed the maximum limit of 34.

Recommended Action    Limit the number of login sessions to 34.

PFS Messages

Error Message    SE-PFS-5-690001:PAC file server routing tables have been rebuilt.

Explanation    The Routing table of the PAC file server module has been rebuilt because of configuration changes. This message is informational only and should appear whenever a configuration change in PAC files occurs and when information level logging is enabled.

Recommended Action    No action is required.

Error Message    SE-PFS-5-690002:PAC file server SE IP Address map has been rebuilt. 

Explanation    The SE name to the IP address map has been rebuilt because of a configuration change. This message is informational only and should appear whenever a configuration change occurs in the SE name to IP address mapping and information level logging is enabled.

Recommended Action    No action is required.

Error Message    SE-PFS-3-690010:Memory allocation failure. 

Explanation    The PAC file server module has failed to allocate memory from the system. This failure can cause the PAC file server module to function improperly and might affect other software modules in the system. This message should appear whenever a memory allocation failure of the PAC file server module occurs. This problem can be caused by a software error and requires investigation. The system should restart the module if a crash occurs and reboot the device automatically if necessary.

Recommended Action    Execute the show process memory command to confirm that the system memory has been used up. Restarting the system should provide an immediate workaround in most cases. To help debug this problem, gather the output of the show pac-file-server info, show statistics pac-file-server, and show process memory commands. Also, turn on debug logging by running the debug pac-file-server all and logging disk priority debug commands for a while when this problem occurs. Send output from the commands output and all syslog files to Cisco TAC for further analysis.

Error Message    SE-PFS-3-690011:Cannot open file <filename>. 

Explanation    The PAC file server module has difficulty opening internal data files when obtaining a configuration update. This failure can cause the PAC file server to run without a configuration or without a configuration update, so that it functions improperly. This message might be caused by disk failure. This error message should appear whenever a configuration update occurs and the PAC file server cannot obtain the update.

Recommended Action    Execute the show disk detail command to check the system disks. If a disk failure has occurred, contact Cisco TAC to replace the hardware. If there is no disk problem, turn on debug logging by running the debug pac-file-server all and logging disk priority debug commands for a while when this problem occurs. Send all syslog files to Cisco TAC for further analysis.

PM Messages

Error Message    SE-PM-3-682601:memory allocation failed. 

Explanation    The memory resource is exhausted.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682602:Preferences file does not exist. 

Explanation    The preferences file containing the default information set by the administrator does not exist.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682603:cannot open <file>. 

Explanation    The system cannot open the mentioned file because the file system is busy.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682604:cannot read <file>. 

Explanation    The system cannot read the mentioned file because the file system is busy.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682605:Invalid Preferences file. 

Explanation    The preferences file containing the default information is invalid or corrupted.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682606:Missing CDN information in Preference file. 

Explanation    The preferences file containing the default information does not have all the required CDN information.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682607:CDSM <name/IP address> not responding. 

Explanation    The PM is not able to establish a connection with the CDSM.

Recommended Action    Verify if the CDSM is alive and reachable.

Error Message    SE-PM-3-682608:cannot resolve CDSM hostname <name>. 

Explanation    The CDSM hostname cannot be resolved to an IP address by the PM.

Recommended Action    Verify that the correct hostname has been supplied in the preferences page, and verify the DNS server is alive and reachable.

Error Message    SE-PM-3-682609:CDSM information tag too long. 

Explanation    The information returned by the CDSM contains an unrecognized field.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682610:missing Origin FQDN field in info returned by CDSM. 

Explanation    The information returned by the CDSM does not contain a required field.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682611:No Id tag in CDSM response. 

Explanation    The information returned by the CDSM does not contain a required field.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682612:No Name tag found in CDSM response. 

Explanation    The information returned by the CDSM does not contain the Website Name field.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682613:No Fqdn tag found in CDSM response. 

Explanation    The information returned by the CDSM does not contain the Fully Qualified Domain Name field.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682614:missing WebSite Id field in CDSM response. 

Explanation    The information returned by the CDSM does not contain the Website Identifier field.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682615:Cannot find delivery service ID in CDSM answer. 

Explanation    The information returned by the CDSM does not contain the Delivery Service Identifier field.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682616:Cannot find Delivery Service Name tag in CDSM answer. 

Explanation    The information returned by the CDSM does not contain the Delivery Service Name field.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682617:Cannot find Manifest URL in CDSM answer. 

Explanation    The information returned by the CDSM does not contain the Manifest URL field.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682618:Cannot find RootSE in CDSM answer. 

Explanation    The information returned by the CDSM does not contain the Root SE field.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682619:cannot find SE status Id field in CDSM answer. 

Explanation    The information returned by the CDSM does not contain the SE Status Identifier field required to find the root SE assigned to a CDN delivery service.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682620:cannot find SE IP address in CDSM answer. 

Explanation    The information returned by the CDSM does not contain the Root SE IP Address field.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682621:unrecognized reply for SE IP address in CDSM answer. 

Explanation    The information returned by the CDSM contains an invalid or unrecognized format, and the PM cannot extract the Root SE IP address of a given CDN delivery service.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682624:CDSM Record size too long. 

Explanation    The information returned by the CDSM contains a record that is too large.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682625:Invalid CDSM username and/or password. 

Explanation    The PM is not able to connect with the CDSM because the username or password in the Preferences page is incorrect for this CDSM.

Recommended Action    Modify the CDSM username or password with the one expected by the CDSM.

Error Message    SE-PM-3-682626:Connection to CDSM at <name/IP address> on port <port 
number> refused. 

Explanation    The PM is not able to establish a connection with the CDSM.

Recommended Action    Verify the connectivity with the CDSM or that the CDSM is properly functioning.

Error Message    SE-PM-3-682627:Error <number> returned from CDSM at <name/IP address> 
on port <port number>. 

Explanation    The CDSM returned the HTTP error code <number>.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682628:Unknown answer from CDSM at <name/IP address> on port 
<port number>. 

Explanation    The information returned by the CDSM is not recognized by the PM.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682629:CDSMIM backend PID probe file cannot be created. 

Explanation    The file system is busy; the PM could not create a mandatory system file.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-6-682630:Skipping CDN delivery service <name> because of Null 
manifest file. 

Explanation    The identified CDN delivery service does not have a Manifest file URL linked with it and now it is useless.

Recommended Action    Add a Manifest file URL if this CDN delivery service is required to export VoD programs to the CDN.

Error Message    SE-PM-6-682631:Skipping CDN delivery service <name> because it does 
not have a Root SE. 

Explanation    The identified live CDN delivery service does not have a root SE assigned to it and now it cannot be used by this PM.

Recommended Action    If this CDN delivery service is required, assign a root SE on the CDSM.

Error Message    SE-PM-6-682632:Skipping CDN delivery service <name> because it does 
not have an IP address for Root SE. 

Explanation    The PM was not able to get the Root SE IP address of the identified live CDN delivery service and now it cannot use it.

Recommended Action    If this delivery service is required, verify that a Root SE is assigned to it and that it is alive.

Error Message    SE-PM-3-682633:CDSM reply not recognized. 

Explanation    The reply from the CDSM is not recognized.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-6-682634:CDSM reply reports Request failed! (<message>). 

Explanation    The reply from the CDSM API was not successful. The <message> contains the reply.

Recommended Action    Verify what <message> reports and see the CDSM documentation.

Error Message    SE-PM-6-682635:cdmim started. 

Explanation    The CDSM Interface Module has been activated.

Recommended Action    No action is required.

Error Message    SE-PM-3-682636:CDSM <name/IP address> returned empty reply. 

Explanation    The reply from the CDSM API was invalid.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682637:CDSM <name/IP address> returned invalid reply: 
<message>.

Explanation    The reply from the CDSM API was not recognized.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682638:sendfetchnow failed: <message>.

Explanation    The command to indicate to the CDSM to get the new/update Manifest file/Program file failed.

Recommended Action    Verify what <message> reports and see the CDSM documentation.

Error Message    SE-PM-3-682639:<program> called with no parameters. 

Explanation    An internal function was called with a wrong number of parameters.

Recommended Action    Contact Cisco TAC.

Error Message    SE-PM-3-682640:<program> called with invalid type. 

Explanation    An internal function was called with an invalid parameter.

Recommended Action    Contact Cisco TAC.

POSTGRE Messages

Error Message    SE-POSTGRE-1-661001:Lower free disk space on STATEFS partition. 

Explanation    The database is filling the STATEFS partition. A&D content replication is temporarily stopped.

Recommended Action    To reclaim disk space on STATEFS, execute the cms database maintenance regular and cms database maintenance full commands, or schedule database maintenance more frequently. Database maintenance impacts certain services on an SE such as live stream splitting and CMS. If the free disk space on STATEFS is still less than 10percent after database maintenance, it is possible too many contents are replicated to the SE. Contact Cisco TAC.

Error Message    SE-POSTGRE-1-661002:Unique index violation.

Explanation    The database server failed to hold a constraint for a unique index and allowed it to insert a duplicate key into the unique index.

Recommended Action    Execute the cms database maintenance command. If this problem persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-POSTGRE-1-661003:Foreign key referential integrity violation.

Explanation    The database server failed to hold a foreign key constraint and allowed it to insert a record into a reference table with a foreign key, which is not found in master table. It is possible that the database was corrupted.

Recommended Action    Contact Cisco TAC.

Error Message    SE-POSTGRE-1-661005:Unable to create Database connection.

Explanation    The database client cannot create a connection with the backend server. It is possible that the Postgres server process was killed, or it is hanging, or all of the database connections are run out.

Recommended Action    Reload the device. If this problem persists, contact Cisco TAC.

Error Message    SE-POSTGRE-1-661007:Failed to do full vacuuming. 

Explanation    The Postgres server returned an error when the Vacuum daemon executes a "vacuum full" SQL statement.

Recommended Action    Contact Cisco TAC.

Error Message    SE-POSTGRE-1-661008:Database reindexing is started. 

Explanation    A&D content replication is temporarily stopped until the re-indexing is complete.

Recommended Action    Wait until re-indexing is complete.

Error Message    SE-POSTGRE-1-661009:Database full vacuuming is started. 

Explanation    A&D content replication is temporarily stopped until the vacuuming is complete.

Recommended Action    Wait until full vacuuming is complete.

Error Message    SE-POSTGRE-1-661010:Delete database records with non-unique value for 
primary key. 

Explanation    Detected and deleted the bad database records with a duplicate value for the primary key.

Recommended Action    Check if any content is missing for the delivery service by executing the show distribution delivery services command. If some contents are missing, execute the distribution refresh meta-data channel-name command to recover metadata for the delivery service for the receiver SE, or execute the acquirer stop-channel and acquirer start-channel commands for the root SE.

PRELD Messages

Error Message    SE-PRELD-2-362001:Preload CLI sysdb bind error.

Explanation    Failed to bind to the system-wide configuration database.

Recommended Action    Reload the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-PRELD-2-362002:Preload notification registration failed.

Explanation    The notification registration for the preload proxy module failed.

Recommended Action    Reload the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-PRELD-2-362003:Preload select returned less than zero.

Explanation    The select call on the preload socket descriptors failed.

Recommended Action    No action is required. Contact Cisco TAC if this message appears frequently.

Error Message    SE-PRELD-3-363001:preload_threads_invoke(): Unable to start preload 
thread-[<thread_index>].

Explanation    Failed to create the preload thread for the concurrent session with identity <thread_index>.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-PRELD-3-363002:preload_threads_invoke(): Unable to join preload 
thread-[<thread_index>].

Explanation    Failed to join the preload for the concurrent session with identity <thread_index>.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-PRELD-3-363003:[preload] mms stream files won't be preloaded as wmt 
is not enabled. 

Explanation    WMT is not enabled, so MMS stream files cannot be preloaded.

Recommended Action    Enable WMT. Contact Cisco TAC if this problem persists.

Error Message    SE-PRELD-3-363004:Error setting preload dscp: <item>, ret=<error_no:>.

Explanation    The DSCP setting for <item> HTTP or WMT failed with an error <error_no>.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-PRELD-5-365001:preload: error <error_no> in bind to sysdb.

Explanation    Preload failed to bind to sysdb and returned the error <error_no>.

Recommended Action    If the message appears frequently, contact Cisco TAC.

Error Message    SE-PRELD-5-365002:<meta_info>.

Explanation    Preload metadata information.

Recommended Action    No action is required.

Error Message    SE-PRELD-5-365003:Preloading is disabled.

Explanation    The user has entered the no preload enable command.

Recommended Action    No action is required.

RBPC Messages

Error Message    SE-RBCP-7-590001:<various messages> 

Explanation    These are various debug messages.

Recommended Action    No action is required.

Error Message    SE-RBCP-5-590002:IP Address configuration successful (type: <num>, 
sense = <num>, ip = <ip>, mask = <mask>). 

Explanation    The IP address configuration on the NM-SE interface was successful.

Recommended Action    No action is required.

Error Message    SE-RBCP-3-590003:IP Address configuration failed (type: <num>, sense 
= <num>, ip = <ip>, mask = <mask>). 

Explanation    The IP address configuration on the NM-SE interface failed.

Recommended Action    Reconfigure the IP address on the router. Contact Cisco TAC if this problem persists.

Error Message    SE-RBCP-5-590004:Sending ip address configuration response. 

Explanation    Sending IP address configuration result to the router.

Recommended Action    No action is required.

Error Message    SE-RBCP-3-590005:do_set_ip(): sendto: <message>. 

Explanation    The NM-SE failed while sending the IP address configuration result to the router.

Recommended Action    Reconfigure the IP address on the router. Contact Cisco TAC if this problem persists.

Error Message    SE-RBCP-5-590006:default gateway configuration successful <default 
gw>. 

Explanation    The default gateway configuration on the NM-SE was successful.

Recommended Action    No action is required.

Error Message    SE-RBCP-3-590007:Default gateway configuration failed <default gw>. 

Explanation    The default gateway configuration on the NM-SE failed.

Recommended Action    Reconfigure the default gateway on the router. Contact Cisco TAC if this problem persists.

Error Message    SE-RBCP-5-590008:Sending defaultgw configuration response. 

Explanation    Sending default gateway configuration result to the router.

Recommended Action    No action is required.

Error Message    SE-RBCP-3-590009:do_set_defaultgw(): sendto:<message>. 

Explanation    The NM-SE failed while sending default gateway configuration results to the router.

Recommended Action    Reconfigure the default gateway on the router. Contact Cisco TAC if this problem persists.

Error Message    SE-RBCP-5-590010:Sending shutdown complete message. 

Explanation    The NM-SE is sending the shutdown complete message to the router.

Recommended Action    No action is required.

Error Message    SE-RBCP-3-590011:do_shutdown(): sendto: <message>. 

Explanation    The NM-SE failed while sending the shutdown response to the router.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RBCP-3-590012:recvfrom <message>. 

Explanation    The NM-SE failed while receiving RBCP messages.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RBCP-5-590013:RBCP Registration ACK from <num>. 

Explanation    The NM-SE received a registration acknowledgement from the router.

Recommended Action    No action is required.

Error Message    SE-RBCP-5-590014:RBCP Registration Request from <num>. 

Explanation    The NM-SE received a registration request message from the router.

Recommended Action    No action is required.

Error Message    SE-RBCP-5-590015:RBCP IP address set message from <num>. 

Explanation    The NM-SE received an IP address set message from the router.

Recommended Action    No action is required.

Error Message    SE-RBCP-5-590016:RBCP default gateway set message from <num>. 

Explanation    The NM-SE received a default gateway set message from the router.

Recommended Action    No action is required.

Error Message    SE-RBCP-5-590017:RBCP shutdown message from <num>. 

Explanation    The NM-SE received a shutdown message from the router.

Recommended Action    No action is required.

Error Message    SE-RBCP-5-590018:RBCP reload message from <num>. 

Explanation    The NM-SE received a reload message from the router.

Recommended Action    No action is required.

Error Message    SE-RBCP-1-590019:RBCP: Nodemgr failed to reload in 60sec. Forcing a 
reload. 

Explanation    The NM-SE failed to reload the NM in a graceful manner.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-RBCP-3-590020:<name>: Error while opening socket: <error>. 

Explanation    The NM-SE failed while creating a socket.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RBCP-3-590021:<name>: Error in bind: <error>. 

Explanation    The NM-SE failed while binding a socket.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RBCP-3-590022:rbcpd: cannot fork: <error>. 

Explanation    The NM-SE failed while forking a process.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RBCP-3-590023:rbcp_register: exec_show_hardware return ret = <num>, 
ret1=<num>, ret2=<num>. 

Explanation    The NM-SE failed while getting status information.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RBCP-3-590024:rbcp_register: cannot open <name>: <error>. 

Explanation    The NM-SE failed while opening a file.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RBCP-3-590025:rbcp_register: error while reading <name>: <error>.

Explanation    The NM-SE failed while reading a file.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RBCP-3-590026:Error while sending registration message: <error>.

Explanation    The NM-SE failed while sending a registration message.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RBCP-5-590027:rbcp_register: Registration message successfully 
sent. 

Explanation    The NM-SE sent the registration message successfully.

Recommended Action    No action is required.

REALPXY Messages

Error Message    SE-REALPXY-2-382001:Failed to open CscoCache/Ruby disk.

Explanation    Failed to open the CscoCache/Ruby disk.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-REALPXY-3-383001:[Procedure] Failed to set Real Proxy 
<incoming|outgoing> bandwidth <bw> <error_message>.

Explanation    Failed to the change the bandwidth configuration of Real Proxy.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-REALPXY-3-383002:Failed to get [property_name] Property.

Explanation    The plug-in failed to get the given property.

Recommended Action    No action is required.

Error Message    SE-REALPXY-3-383003:Plugin Error.

Explanation    The error message should provide a description of the error.

Recommended Action    No action is required.

Error Message    SE-REALPXY-3-383004:Operation on [file] file failed.

Explanation    The operation failed on the given file.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-REALPXY-3-383005:Real Media Caching is disabled. 

Explanation    Real Media Caching is disabled by configuration.

Recommended Action    Enable using the Real Proxy-> Caching tabs in the CDSM if needed.

Error Message    SE-REALPXY-3-383006:Failed to bind/unbind or get [info] information 
from the DS. 

Explanation    Failed to either bind or unbind or get information from the data server as indicated by the message.

Recommended Action    Enter the command again. Contact Cisco TAC if this message appears frequently.

Error Message    SE-REALPXY-4-384001:Warning.

Explanation    The message is informative only.

Recommended Action    No action is required.

Error Message    SE-REALPXY-7-387001:Real Proxy <incoming|outgoing> bandwidth set to 
<bw>.

Explanation    Real Proxy bandwidth configuration message.

Recommended Action    No action is required.

Error Message    SE-REALPXY-7-387002:Plugin debug messages.

Explanation    Plugin debug message.

Recommended Action    No action is required.

REALSRV Messages

Error Message    SE-REALSRV-3-393010:[Procedure] Failed to set Real Subscriber 
bandwidth <bw> <error_message>. 

Explanation    Failed to the change the bandwidth configuration of the Real Subscriber.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-REALSRV-7-397002:Real Subscriber bandwidth set to <bw>. 

Explanation    Real Subscriber bandwidth configurations.

Recommended Action    No action is required.

RPC Messages

Error Message    SE-RPC-2-620000:Usage. 

Explanation    Incorrect usage while invoking the program.

Recommended Action    Check the usage and retry. If the error occurred without any intervention from the user, report it to Cisco TAC.

Error Message    SE-RPC-2-620001:Malloc failed. 

Explanation    Malloc failed.

Recommended Action    Check the errorlog for more information. The program restarts by the node manager. Contact Cisco TAC if this problem persists.

Error Message    SE-RPC-2-620002:Failed to create [server description] server.

Explanation    Failed to create a UniRPC server for inter-process communication.

Recommended Action    Check the errorlog for more information. The program restarts by the node manager. Contact Cisco TAC if this problem persists.

Error Message    SE-RPC-2-620003:Child process [pid] was killed unexpectedly with 
signal [signal number]. 

Explanation    A dispatcher process trying to communicate outside the device died unexpectedly. This is a very rare situation.

Recommended Action    The dispatcher recovers automatically. If this happens on a CDSM and if an item that was being configured at the time did not reach its intended destination, redo the configuration. Check the CMS errorlog to see if it has any more information. If this happens on a non-CDSM device, check the appropriate inter-box modules (distribution or CMS errorlogs) to see if you find any information. If there is no affect on the system, the error might be ignored, as some inter-box messages are not expected to be reliable and the system continues to function. Contact Cisco TAC if this problem persists.

RSH Messages

Error Message    SE-RSH-0/1/2/3/4/5/6-810030:[Description]. 

Explanation    These messages are generated by Remote Shell Protocol (RSH).

Recommended Action    If high priority error messages frequently occur, contact Cisco TAC.

RSM Messages

Error Message    SE-RSM-2-402200:[register_verification] - Verifier register failed. 

Explanation    Registration for verification with the data server failed.

Recommended Action    Real Server Manager (RSM) will keep retrying.

Error Message    SE-RSM-2-402201:[set_rlimit] - setrlimit() failed. 

Explanation    Cannot increase the file descriptors for the RS process.

Recommended Action    Real server performance could be affected. Contact Cisco TAC.

Error Message    SE-RSM-3-402300:[rsm_loop] - Error in processing VEN msg. 

Explanation    RSM was not able to process a VEN message.

Recommended Action    RSM reinitializes itself.

Error Message    SE-RSM-3-402301:[rsm_loop] - Health Probe failed for RS. 

Explanation    None.

Recommended Action    RSM should restart Real Server.

Error Message    SE-RSM-3-402302:[rsm_ds_bind] - Cannot bind to data server. 

Explanation    None.

Recommended Action    RSM should keep on retrying.

Error Message    SE-RSM-3-402303:[register_notification] - Register Notification 
failed. 

Explanation    RSM is not notified by the data server for this item.

Recommended Action    The user might be required to manually restart RS after IP address change.

Error Message    SE-RSM-3-402304:[unregister_verification] - Verifier unregister 
failed. 

Explanation    The verifier unregister with the data server failed.

Recommended Action    Check for rc value. No action is required.

Error Message    SE-RSM-3-402305:[start_real_server] - fork () or exec() failed. 

Explanation    The SE might be out of system resources.

Recommended Action    RSM will restart. Try enabling the RS again.

Error Message    SE-RSM-3-402306:[get_rsm_pid] - Failed to read pid from pid file. 

Explanation    NETRCM callback cannot send SIGUP to RSM without its PID.

Recommended Action    Try changes on the interface again, especially if you have changed the IP address.

Error Message    SE-RSM-3-402307:[rsm_loop] - Received SIGHUP from NETRCM callback. 

Explanation    The RS is started or stopped after receiving the sighup command.

Recommended Action    Start or stop RS from the CDSM.

Error Message    SE-RSM-3-402308:System call error: <system call name> <err msg>. 

Explanation    The system call failed. The system might be in an unstable state.

Recommended Action    Re-enable the service that is causing this error. Reboot if that does not fix the problem. Contact Cisco TAC if this problem persists.

Error Message    SE-RSM-3-402309: - Real Server Manager could not write to pid file. 

Explanation    The Real Server Manager could not write to a PID file.

Recommended Action    Re-enable the service that is causing this problem. Reboot if that does not fix the problem. Contact Cisco TAC if this problem persists.

Error Message    SE-RSM-4-402400:[main] - RSM restarted while Real Server is running. 

Explanation    RSM restarted. If the Real Server is enabled, playback is affected. The Real Server should restart itself.

Recommended Action    Check the Real Server status using the show rtsp server command. Enable the Real Server.

Error Message    SE-RSM-4-402401:[handle_signal] - Real Server died. 

Explanation    The Real Server process died. This can be a normal or abnormal termination.

Recommended Action    RSM should take action automatically depending on the enable status.

Error Message    SE-RSM-4-402402:[procedure] - INFO. 

Explanation    None.

Recommended Action    No action is required.

Error Message    SE-RSM-4-402403:[rsm_loop] - RSM select() call returned error. 

Explanation    None.

Recommended Action    Look up the error number variable value. No action is required.

Error Message    SE-RSM-4-402404:[unregister_notification] - Notifier unregister 
failed. 

Explanation    The notifier unregistered with the data server failed.

Recommended Action    Check for an rc value. No action is required.

Error Message    SE-RSM-4-402405:[verification_ack] - Verification ACK failed. 

Explanation    Failed to build or send acknowledgement to the data server for a verification message.

Recommended Action    Check for an rc value. The Real Server -enabled CLI changes would not take effect. RSM restarts and tries the command again. Contact Cisco TAC if this problem persists.

Error Message    SE-RSM-4-402406:[process_notification] - Get notifier info failed. 

Explanation    Failed to get notification information from the data server.

Recommended Action    RSM should restart. Manually start and stop the Real Server after an IP address change.

Error Message    SE-RSM-4-402407:[process_notification] - Free Ven resources. 

Explanation    Failed to free notification information.

Recommended Action    RSM should restart. Manually start and stop the Real Server after an IP address change.

Error Message    SE-RSM-4-402408:[process_ven_msg] - Failed to process ven msg. 

Explanation    None.

Recommended Action    RSM should restart. Manually start and stop the Real Server again.

Error Message    SE-RSM-6-402600:[process_notification].

Explanation    None.

Recommended Action    No action is required.

Error Message    SE-RSM-7-402700:[Procedure] - Debug MSG. 

Explanation    None.

Recommended Action    No action is required.

RTSP Messages

Error Message    SE-RTSP-3-403000:[Procedure] System call error: <system call name> 
<err msg>. 

Explanation    The system call failed. The system might be in an unstable state.

Recommended Action    Re-enable the service that caused this error. Contact Cisco TAC if this problem persists.

Error Message    SE-RTSP-3-403001:[Procedure] RTSP [service] user license agreement not 
accepted <mesg>. 

Explanation    The RTSP Proxy/Subscriber user license agreement is not accepted.

Recommended Action    Accept the license agreement and try enabling RTSP services.

Error Message    SE-RTSP-3-403002:[Procedure] Could not set Real [service] Logpath 
variable in temp file <mesg>. 

Explanation    Failed to set the Real [service] Logpath variable in the temp file.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-RTSP-3-403003:[Procedure] Failed to move temp file with accesslog 
path variable to Real Proxy configuration file <error_message>. 

Explanation    Failed to move the temp file to the configuration file.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-RTSP-3-403004:[Procedure] External/Fast Ethernet/Gigabit Ethernet 
IP not configured. Using the local host IP. 

Explanation    External/Fast Ethernet/Gigabit Ethernet IP is not available.

Recommended Action    Configure External/Fast Ethernet/Gigabit Ethernet IP and retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-RTSP-3-403005:[Procedure] Failed to disable Real [service] 
evaluation.

Explanation    Failed to disable Real Proxy/Subscriber evaluation on entering a valid license key.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-RTSP-3-403006:[Procedure] Failed to start/stop Real Subscriber 
<error_mesg>. 

Explanation    Failed to start or stop the Real Subscriber.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-RTSP-3-403007:[Procedure] Failed to disable Real [service] 
<error_mesg>. 

Explanation    Failed to disable Real Proxy/Subscriber.

Recommended Action    Retry the command. If this message appears frequently, contact Cisco TAC.

Error Message    SE-RTSP-3-403008:[Procedure] Failed to enable Real [service] 
evaluation <error_msg>. 

Explanation    Failed to enable the Real Proxy/Subscriber.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-RTSP-3-403009:[Procedure] Failed to create symbolic link for Real 
Subscriber VOD <error_mesg>. 

Explanation    Failed to create a symbolic link for the Real Subscriber VOD.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-RTSP-3-403010:[Procedure] Failed to set Real Subscriber 
default/maximum archive file size. 

Explanation    Failed to set the Real Subscriber default and maximum archive file size.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-RTSP-3-403011:[Procedure] Failed to get Real [service] 
Configuration <error_mesg>. 

Explanation    Failed to get Real Proxy/Subscriber configuration.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-RTSP-3-403012:[Procedure] Failed to execute IP address check script 
<error_mesg>. 

Explanation    Failed to execute the script that checks for the IP address.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-RTSP-3-403013:[Procedure] Host name not configured <error_mesg>. 

Explanation    Hostname configuration is not available.

Recommended Action    Configure the hostname and retry the command.

Error Message    SE-RTSP-3-403014:[Procedure] Real Server needs hostname other than 
local host <error_mesg>. 

Explanation    The Real Server needs a hostname other than the local host.

Recommended Action    Configure the hostname other than the local host and retry the command.

Error Message    SE-RTSP-3-403015:[Procedure] No IP address available in /etc/hosts. 
<error_mesg>. 

Explanation    No IP address is available in the /etc/hosts file.

Recommended Action    Configure the IP address and retry the command.

Error Message    SE-RTSP-3-403016:[Procedure] Unknown return status from IP address 
check script. 

Explanation    An invalid return status was received from the IP address check script.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-RTSP-3-403017:[Procedure] Real Proxy enable. 

Explanation    Cannot create a symbolic link for the MEDIAFS mount point. Real Proxy might go into PASS THROUGH mode.

Recommended Action    Check the current disk configuration for the MEDIAFS partition. To enable Real Proxy, first configure the MEDIAFS partition.

Error Message    SE-RTSP-3-403018:[Procedure] Failed to set [sprayer] bandwidth to 
[bandwidth].

Explanation    Failed to set streaming sprayer bandwidth.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-RTSP-3-403020:[Procedure] Failed to send sighup signal to [pid].

Explanation    Failed to send a sighup signal to the sprayer process.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-RTSP-3-403021:Number of MEDIAFS partitions exceed the max limit of 
[no] partitions. 

Explanation    The number of MEDIAFS partitions exceeds the maximum limit and Real Media-cached content is not cleared on certain MEDIAFS partitions.

Recommended Action    No action is required.

Error Message    SE-RTSP-3-403022:Real Server license directory was not set/invalid. 

Explanation    Failed to set the real license directory or it is null.

Recommended Action    Retry the command. If this message appears frequently contact Cisco TAC.

Error Message    SE-RTSP-6-406001:[Procedure] Disabled Real [service] evaluation on 
entering valid license key. 

Explanation    Disabled Real Proxy/Subscriber evaluation.

Recommended Action    No action is required.

Error Message    SE-RTSP-6-406002:[Procedure] Maximum file size for Real Subscriber 
archiving <size>. 

Explanation    Real Subscriber file size information.

Recommended Action    No action is required.

Error Message    SE-RTSP-6-406003:[Procedure] Started/Stopped the Real Subscriber. 

Explanation    Started or stopped the Real Subscriber.

Recommended Action    No action is required.

Error Message    SE-RTSP-6-406004:[Procedure] Enabled Real [service] evaluation. 

Explanation    Enabled Real Proxy/Subscriber evaluation.

Recommended Action    No action is required.

Error Message    SE-RTSP-6-406005:[Procedure] [Interface type] IP not available using 
Interface type] IP. 

Explanation    External/Fast Ethernet/Gigabit Ethernet IP is not available.

Recommended Action    No action is required.

Error Message    SE-RTSP-6-406006:[Procedure] real proxy enable. 

Explanation    Real Proxy mount point information.

Recommended Action    No action is required.

Error Message    SE-RTSP-7-407001:[RTSP CLI Bin Debug Msg].

Explanation    This is a debug message.

Recommended Action    No action is required.

Error Message    SE-RTSP-7-407002:[Procedure] Failed to get correct PID [pid].

Explanation    Failed to get the sprayer PID.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-RTSP-7-407003:[Procedure] Application is not enabled. 

Explanation    The application is not enabled.

Recommended Action    No action is required.

Error Message    SE-RTSP-7-407004:[RTSP Debug Msg].

Explanation    This is a debug message.

Recommended Action    No action is required.

RTSPG Messages

Error Message    SE-RTSPG-2-408200:[Procedure] - RTSP Gateway error log init failed 
<error_mesg>. 

Explanation    RTSP Gateway error log initialization failed.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-RTSPG-2-408201:[Procedure] - Failed to generate RTSP Gateway error 
log config file <mesg>. 

Explanation    Failed to generate RTSP Gateway error log configuration file when the RTSPG debug level is changed.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-RTSPG-2-408202:[Procedure] - Memory allocation failed during 
errorlog initialization for RTSP Gateway. 

Explanation    A memory allocation failure occurred. The system attempted to allocate zero size memory.

Recommended Action    Reload. Contact Cisco TAC if this problem persists.

Error Message    SE-RTSPG-2-408203:[Procedure] - Failed to create/open RTSP Gateway 
errorlog client configuration file: <file_path>. 

Explanation    Failed to create or open the RTSP Gateway configuration file.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-RTSPG-2-408204:[Procedure] - Failed to initialize debug library for 
RTSP Gateway. 

Explanation    Failed to initialize the debug library.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-RTSPG-2-408205:[Procedure] - Interface IP address not configured. 

Explanation    RTSPG failed to start. It requires an interface IP address. RTSPG sleeps for 15 seconds and exits.

Recommended Action    Configure an interface IP address.

Error Message    SE-RTSPG-3-408300:[Procedure] - Failed to set item <mesg>. 

Explanation    Failed to set an item in the data server.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-RTSPG-3-408301:[Procedure] -Unable to signal self to get errlog 
config <mesg>. 

Explanation    Unable to send a signal to itself to get the errlog configuration.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-RTSPG-3-408302:[Procedure] - Failed to restart RTSPG after incoming 
port change. 

Explanation    Failed to restart RTSPG after an incoming port change.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-RTSPG-3-408303:Failed to get/set item [name] in data server. 

Explanation    The RTSP Gateway module failed to get or set an item from the data server. The error number for the get/set is [x].

Recommended Action    The system should recover from the error automatically. Contact Cisco TAC if this problem persists.

RULES Messages

Error Message    SE-RULES-2-412001:<procedure>: invalid switch. 

Explanation    Encountered an invalid pattern or action type.

Recommended Action    Check the rule configuration. Contact Cisco TAC if this problem persists.

Error Message    SE-RULES-2-412002:<procedure>: rule is NULL. 

Explanation    The argument rule passed a null pointer.

Recommended Action    Check the rule configuration. Contact Cisco TAC if the messages appears frequently.

Error Message    SE-RULES-2-412003:rule_del(): <parameter> entry not found. 

Explanation    Tried to remove a parameter that is not configured.

Recommended Action    Execute the show rule all command to check for configured parameters.

Error Message    SE-RULES-2-412004:default switch in <procedure>. 

Explanation    Encountered an invalid pattern type.

Recommended Action    Check the rule configuration. Contact Cisco TAC if this problem persists.

Error Message    SE-RULES-2-412005:<procedure> error: invalid else. 

Explanation    The pattern type is neither SRC_IP or DST_IP.

Recommended Action    Check the rule configuration. Contact Cisco TAC if this problem persists.

Error Message    SE-RULES-2-412006:error allocating new pattern table. 

Explanation    The system failed to allocate memory for a new pattern table.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RULES-2-412007:Error allocating new action table. 

Explanation    The system failed to allocate memory for a new action table.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RULES-2-412008:error allocating new Rule table. 

Explanation    The system failed to allocate memory for a new rule table.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RULES-2-412009:rule_of_port_sort() error: NULLP. 

Explanation    The argument passed a null pointer for sorting.

Recommended Action    Check the rule configuration for configured destination ports. Contact Cisco TAC if this problem persists.

Error Message    SE-RULES-2-412010:Rule:pattern_match_request: failed to alloc memory. 

Explanation    The system failed to allocate memory for a new pattern list.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RULES-2-412011:rule_show_stat(); Internal error. 

Explanation    The rule statistics entry is null.

Recommended Action    Check the rule configuration. Contact Cisco TAC if this problem persists.

Error Message    SE-RULES-3-413001:<procedure>: Can't create new list. 

Explanation    The system failed to allocate memory for a new list.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RULES-3-413002:rule_add_port(): new_list_head is NULL. 

Explanation    The system failed to allocate memory for a new port list.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RULES-3-413003:rule_add_port(): cur_list NULL. 

Explanation    The system failed to allocate memory for a new port list.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RULES-3-413004:rule_create_port_list(): failed to malloc 
new_list_head. 

Explanation    The system failed to allocate memory for a new port list.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RULES-3-413005:rule_create_ip_list() new_list is NULL. 

Explanation    The system failed to allocate memory for a new IP list.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RULES-3-413006:rule_del_ip(): error creating new list. 

Explanation    The system failed to allocate memory for a new IP list.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RULES-3-413007:rule_add_regex(): failed to create new list. 

Explanation    The system failed to allocate memory for a new regex list.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RULES-3-413008:rule_create_regex_list(): memory allocation failed. 

Explanation    The system failed to allocate memory for a new regex list.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RULES-3-413009:rule_create_regex_list() can't allocate regex. 

Explanation    The system failed to allocate memory for a new regex list.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RULES-3-413010:rule_del_regex(): failed to create new list. 

Explanation    The system failed to allocate memory for a new regex list.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RULES-3-413011:ctype is null. 

Explanation    The ctype member in the response header might have a null value.

Recommended Action    No action is required because the system might purposely check for this null value.

Error Message    SE-RULES-3-413012:error allocation new action table. 

Explanation    The system failed to allocate memory for a new action table.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RULES-3-413013:Malloc for action_sel failed. 

Explanation    The system failed to allocate memory.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RULES-3-413014:rule_process_verif_msg(): <filename> <line_no> 
<ds_get_verification_info call failed> errno = <error_no>. 

Explanation    The ds_get_verification_info call failed with error number <error_no> in file <filename> line <line_no>.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RULES-3-413015:register_verifier(): <filename> <line_no> 
<register_verifier failed for item> <item>. 

Explanation    The register_verifier call failed for item <item> in file <filename> line <line_no>.

Recommended Action    Contact Cisco TAC.

Error Message    SE-RULES-3-413016:rule_server_main(): ERROR request processing timed 
out. 

Explanation    The request timed out.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-RULES-3-413017:rule_server_rpc_main(): RpcUdsServer_new() returned 
NULL server. 

Explanation    Launching of new rule_server might have failed.

Recommended Action    Reload the SE. Contact Cisco TAC if this problem persists.

Error Message    SE-RULES-3-413018:rules_daemon : RpcUdsServer_accept returned a NULL 
client. 

Explanation    The RpcUdsServer_accept returned a null client.

Recommended Action    No action is required. Contact Cisco TAC if this message appears frequently.

Error Message    SE-RULES-3-413019:rules_daemon() client_thread_create failed err = 
<error_no>. 

Explanation    Creation of new client thread failed with an error number <error_no>.

Recommended Action    No action is required. Contact Cisco TAC if this message appears frequently.

Error Message    SE-RULES-3-413020:rule_init_cfg() Failed to bind to sysdb. 

Explanation    Failed to bind to the data server. The Cache process is automatically restarted.

Recommended Action    No action is required. Contact Cisco TAC if this message appears frequently.

Error Message    SE-RULES-3-413021:rule_init_cfg() Failed to get the list from sysdb. 

Explanation    Failed to get the list from the data server. A new connection is opened to retry the operation.

Recommended Action    No action is required. Contact Cisco TAC if this message appears frequently.

Error Message    SE-RULES-5-415001:Ignoring invalid URL rewrite original URL=<old_url> 
new URL=<new_url>. 

Explanation    Ignores invalid URL rewrite.

Recommended Action    No action is required.

Error Message    SE-RULES-5-415002:Ignoring invalid URL transformation URL=<old_url> 
new URL=<new_url>. 

Explanation    Ignores invalid URL transformation.

Recommended Action    No action is required.

Error Message    SE-RULES-5-415003:rule_show_stat(); Error opening tty. 

Explanation    Failed to open the terminal for writing rules statistics.

Recommended Action    No action is required.

Error Message    SE-RULES-6-416001:rule_del_port(): old_list is NULL. 

Explanation    The old port list might be empty.

Recommended Action    No action is required.

Error Message    SE-RULES-6-416002:send_verif_ack(): error building ack, error = 
<error_no>. 

Explanation    An error occurred in building the acknowledgment message.

Recommended Action    No action is required.

Error Message    SE-RULES-6-416003:rule_process_verif_msg(): unknown event = 
<sysdb_info.event>. 

Explanation    An unknown event was encountered while receiving the rule process verification message.

Recommended Action    No action is required.

Error Message    SE-RULES-6-416004:rule_process_notif_msg(): <file_name> <line_no> 
<ds_get_notification_info call failed>errno = <error_no>. 

Explanation    An error <error_no> occurred in file <file_name> in line <line_no> while receiving the rule process notification message.

Recommended Action    No action is required.

Error Message    SE-RULES-6-416005:rule_process_notif_msg(): <file_name> <line_no> 
ds_free_ven_resource failed. 

Explanation    An error occurred in file <file_name> line <line_no> when the data server tries to free the resource.

Recommended Action    No action is required.

Error Message    SE-RULES-6-416006:Failed to get the full message from the ds. 

Explanation    The Rule process failed to receive the complete message from the data server.

Recommended Action    No action is required.

Error Message    SE-RULES-6-416007:rule_register_notifier(): <file_name> <line_no> 
<rule_register_notifier failed for item> <rule_action_notif_tuple> Err 
<error_no>.

Explanation    Error <error_no> occurred in file <file_name> in line <line_no> for item <rule_action_notif_tuple> when the rule process registers notification.

Recommended Action    No action is required.

Error Message    SE-RULES-6-416008:rule_register_notifier(): <file_name> <line_no> 
<rule_register_notifier failed for item> <rule_pattern_notif_tuple>. 

Explanation    An error occurred in file <file_name> in line <line_no> for item <rule_pattern_notif_tuple> when the rule process registers notification.

Recommended Action    No action is required.

Error Message    SE-RULES-6-416009:rule_register_notifier(): <file_name> <line_no> 
<rule_register_notifier failed for item> <rule_pattern_delta_tuple>. 

Explanation    An error occurred in file <file_name> in line <line_no> for item <rule_pattern_delta_tuple> when the rule process registers notification.

Recommended Action    No action is required.

Error Message    SE-RULES-6-416010:rule_register_notifier(): <file_name> <line_no> 
<rule_register_notifier failed for item> <rule_debug_notif_tuple>. 

Explanation    An error occurred in file <file_name> in line <line_no> for item <rule_debug_notif_tuple> when the rule process registers notification.

Recommended Action    No action is required.

Error Message    SE-RULES-6-416011:rule_register_notifier(): <file_name> <line_no> 
<rule_register_notifier failed for item> <rule_action_delta_tuple>. 

Explanation    An error occurred in file <file_name> in line <line_no> for item <rule_action_delta_tuple> when the rule process registers notification.

Recommended Action    No action is required.

Error Message    SE-RULES-6-416012:Rule Item Not found in the Sequence. 

Explanation    The rule item is not found in the fetched sequence.

Recommended Action    No action is required.

Error Message    SE-RULES-6-416013:rule_daemon : Bind failed in sysdb. 

Explanation    The data server failed to bind the socket.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-RULES-6-416014:send_verif_ack(): error sending ack, error = 
<error_no>. 

Explanation    An error is in the acknowledgment message.

Recommended Action    No action is required.

Error Message    SE-RULES-6-416015:rule_process_notif_msg (): Unknown Event. 

Explanation    An unknown event occurred when sending the rule process notification message.

Recommended Action    No action is required.

Error Message    SE-RULES-6-416016:gui_rules: Length of pattern exceeds the limit 
(dislpay_str). 

Explanation    SE GUI does not display this pattern.

Recommended Action    No action is required.

SCHED Messages

Error Message    SE-SCHED-2-189000:Missing scheduler working thread.

Explanation    One of the worker threads that the scheduler uses for assigning work has unexpectedly terminated. The SE web proxy cache attempts to recover by restarting itself.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-SCHED-5-189001:Reporting of thread and process identifiers.

Explanation    Upon startup, the SE scheduler reports the internal process and thread identifiers. This information might be useful in debugging problems.

Recommended Action    No action is required.

Error Message    SE-SCHED-4-189002:Scheduler CLI memory allocation failure.

Explanation    Upon receiving a command to perform an action to modify the behavior of the scheduler, a memory resource allocation failed, which might result in some commands failing.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-SCHED-4-189003:Scheduler CLI file open failure.

Explanation    Upon receiving a command to perform an action to modify the behavior of the scheduler, a file could not be opened, which might result in some commands failing.

Recommended Action    Contact Cisco TAC if this problem persists.

SERMON Messages

Error Message    SE-SERMON-7-690300:<debug message>. 

Explanation    This is a debug message from the Service Monitor process.

Recommended Action    No action is required.

Error Message    SE-SERMON-6-690301:<info message>. 

Explanation    This is an information message from the Service Monitor process.

Recommended Action    No action is required.

Error Message    SE-SERMON-4-690302:Unable to perform Data Server operations. 

Explanation    The Service Monitor process failed to get data from the data server. This can indicate a major system problem if it is persistent.

Recommended Action    No action is required. If this problem is persistent, reboot the system.

SNMP Messages

Error Message    SE-SNMP-2-430001:bind_data server_sock() failed: <return value>. 

Explanation    Cannot connect to the data server. If this message is seen, the SNMP Agent cannot accept configurations from the CLI, send traps, or retrieve any CISCO-CONTENT-ENGINE-MIB statistics

Recommended Action    Re-enable SNMP. Contact Cisco TAC if this problem persists.

Error Message    SE-SNMP-5-430002:ds_edm_register() failed: <item name return value>. 

Explanation    EDM registration failed with the data server <return value>.

Recommended Action    If this message is seen, usually the SNMP Agent recovers from it. Execute the show snmp event command to see if this CLI is functioning properly. Re-enable SNMP. Contact Cisco TAC if this problem persists.

Error Message    SE-SNMP-5-430003:ds_verification_register() failed: <str>. 

Explanation    Verification registration failed with the data server.

Recommended Action    If this message is seen, the user is unable to configure SNMP-related features. Re-enable SNMP. Contact Cisco TAC if this problem persists.

Error Message    SE-SNMP-5-430004:ds_notification_register() failed: <str>. 

Explanation    Notification registration with the data server failed.

Recommended Action    If this message is seen, the SNMP Agent might not be able to generate traps. Re-enable SNMP. Contact Cisco TAC if this problem persists.

Error Message    SE-SNMP-3-430005:[Procedure]:Failed open [filename]. errno: [dc], 
[str].

Explanation    An error occurred while opening the [filename] file.

Recommended Action    Re-enable SNMP. Contact Cisco TAC if this problem persists.

Error Message    SE-SNMP-3-430006:[Procedure]: Failed to read [filename]. errno: [dc], 
[str].

Explanation    Encountered an error while reading a procedure file.

Recommended Action    Re-enable SNMP. Contact Cisco TAC if this problem persists.

Error Message    SE-SNMP-3-430007:[Procedure]: Failed to read [filename]. End-of-file. 

Explanation    Encountered unexpected end-of-file in a procedure file.

Recommended Action    Re-enable SNMP. Contact Cisco TAC if this problem persists.

Error Message    SE-SNMP-2-430008:[filename] has more data than SNMP Agent 
expects:possible kernel version and SNMP Agent application code mismatch. 

Explanation    An unexpected number of data fields were found in a procedure file.

Recommended Action    Re-enable SNMP. Contact Cisco TAC if this problem persists.

Error Message    SE-SNMP-2-430009:Incorrect number of data items found in [filename].

Explanation    An unexpected number of data fields were found in a procedure file.

Recommended Action    Re-enable SNMP. Contact Cisco TAC if this problem persists.

Error Message    SE-SNMP-2-430010: / proc/net/snmp header line has unexpected format. 
Possible kernel version and SNMP Agent application code mismatch. 

Explanation    Unknown header information was found in /proc/net/arp.

Recommended Action    Re-enable SNMP. Contact Cisco TAC if this problem persists.

Error Message    SE-SNMP-2-430011: / proc/net/snmp sscanf parsing error STAT_NET_ICMP 
entry.num_items read = <dc>, num_items expected = 26. 

Explanation    An unknown number of data fields were found in /proc/net/snmp.

Recommended Action    Re-enable SNMP. Contact Cisco TAC if this problem persists.

Error Message    SE-SNMP-2-430012: / proc/net/snmp has more data than SNMP Agent 
expects: chars read = [dc] chars processed = [dc] possible kernel version and snmp 
application code mismatch. 

Explanation    An unknown number of data fields were found in /proc/net/snmp.

Recommended Action    Re-enable SNMP. Contact Cisco TAC if this problem persists.

Error Message    SE-SNMP-2-430013:snmp Agent process terminated. 

Explanation    An SNMP Agent process terminated due to connection failure with the data server.

Recommended Action    The SNMP Agent process restarts by the node manager process. Re-enable SNMP. Contact Cisco TAC if this problem persists.

Error Message    SE-SNMP-3-430014:SNMP server could not set Contact data item in Data 
Server (error code). 

Explanation    A change was made in the SNMP server contact information, but the change could not be recorded in the data server.

Recommended Action    Try setting the contact data item again. Re-enable SNMP. Contact Cisco TAC if this problem persists.

Error Message    SE-SNMP-3-430015:SNMP server could not set Location data item in Data 
Server (error code). 

Explanation    A change was made in the SNMP server location information, but the change could not be recorded in the data server.

Recommended Action    Try setting the location data item again. Re-enable SNMP. Contact Cisco TAC if this problem persists.

Error Message    SE-SNMP-5-430016:SNMP server is resetting the connection with the Data 
Server.

Explanation    Due to a previous data server communication error, the SNMP server is going to reset the data server connection.

Recommended Action    No action is required.

Error Message    SE-SNMP-5-430017:SNMP server is resetting the connection with the Node 
Health Manager. 

Explanation    Due to a previous Node Health Manager communication error, the SNMP server is going to reset the connection with the Node Health Manager.

Recommended Action    No action is required.

Error Message    SE-SNMP-2-430018:SNMP server:malloc error. <size> <function_name>. 

Explanation    Memory allocation error.

Recommended Action    Re-enable SNMP and then reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-SNMP-3-430019:SNMP server: <function_name>: For <data item>, 
expected <num> bytes but received <num> bytes. 

Explanation    The SNMP server received the incorrect size of data from another module.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-SMARTD-0/1/2/3/4/5/6-435000:[failure-description].

Explanation    The native Linux SMARTD code exposes error or notice or information.

Recommended Action    SMARTD log messages mean disk health-related attributes have changed, which might indicate a possible disk failure in the near future. When you receive SMARTD error messages, take proper action (such as backing up data) on the concerned disks, as they are expected to fail later.

SR Messages

Error Message    SE-SR-3-180101:Memory allocation failure.

Explanation    The SR failed to allocate memory from the system. This failure can cause the SR to function improperly and might affect other software modules in the system. This message should appear whenever a memory allocation failure of the SR occurs. This problem can be caused by a software error and requires investigation. The system should restart the SR if a failure occurs and reboot the device if necessary.

Recommended Action    Execute the show process memory command to confirm that the system memory has been used up. Restarting the system provides an immediate workaround in most cases. To help debug this problem, gather the output of the show content-routing route, show statistics content-routing all, and show process memory commands. Also, turn on debug logging by executing the debug content-routing all and logging disk priority debug commands for when this problem occurs. Send the output of the commands and all syslog files to Cisco TAC for further analysis.

Error Message    SE-SR-5-180102:Routing table has been rebuilt.

Explanation    The routing table of the SR has been rebuilt because of configuration changes. This message is informational only and should appear whenever a configuration change has occurred and information level logging is enabled.

Recommended Action    No action is required.

Error Message    SE-SR-5-180201:Service Engine '<ce name>' is up (keepalives have 
started or resumed). 

Explanation    The SR has started to receive keepalives from the SE whose name is in the message. The liveness state of the SE has changed as a result. This message is informational only and should appear whenever keepalives are received that cause a change in the liveness state, and when information level logging is enabled.

Recommended Action    No action is required.

Error Message    SE-SR-4-180202:Service Engine '<ce name>' is down (keepalives have 
stopped). 

Explanation    The SR has stopped receiving keepalives from the SE whose name is in the message. The liveness state of the SE changed to "down" as a result, and no client requests are routed to it until the SR once again receives keepalives from the SE. This message is notice level only and should appear whenever notice level logging is enabled and an SE state change occurs because the SR stops receiving keepalives from the SE.

Recommended Action    Check the network connectivity between the SE and the SR. Use a Sniffer network analyzer to verify that DNS traffic is passing from the SE to the SR and is successfully received by the SR. If the connectivity is satisfactory, check the state of the SE on the CDSM to see if it is online and check the Content Distribution Manager syslog file for messages that might indicate why the SE went down. Finally, execute the show process memory command on the SE to see if a "crka-start.pl" process is running. If you can find no reason for the error message, send all syslog files on the SE and the output of the show cms info and show cms database context xml commands to Cisco TAC for further assistance.

Error Message    SE-SR-3-180301:Failed to open a connection to the data server after 
<num> tries. 

Explanation    The SR cannot communicate with the data server module that stores system-wide configuration data. This can cause commands related to service routing to fail, including the show content-routing, clear statistics content-routing, show statistics content-routing, and debug content-routing commands. This message requires immediate attention and only appears when the SR starts up.

Recommended Action    Send all syslog files to Cisco TAC for further analysis.

Error Message    SE-SR-4-180302:Failed to close a connection to the data server at 
<string> <string>.

Explanation    The SR failed to close a connection to the data server. No serious consequences result from this error.

Recommended Action    Send all syslog files to Cisco TAC for further analysis if some service routing-related commands cannot be executed.

Error Message    SE-SR-3-180303:Failed to register notifications at <string> - 
<string>.

Explanation    The SR failed to register with the data server to be notified when any of the debug content-routing commands are executed. After this message appears, the SR keeps trying to register every 60 seconds. This message only occurs when the SR starts up. This message is a notice level message if the problem occurs fewer than 5 times and is escalated to an error level message if it occurs more than 5 times. Ignoring this error message can cause failure of the debug content-routing commands.

Recommended Action    Restarting the node provides a temporary workaround. Send all syslog files to Cisco TAC for further analysis.

Error Message    SE-SR-4-180304:Failed to unregister notifications.

Explanation    The SR failed to unregister from the data server to be notified when the debug content-routing commands are executed. This error message occurs when the SR exits or when it tries to reregister after a communication error has occurred.

Recommended Action    No serious consequences result from this error. Send all syslog files to Cisco TAC for further analysis if some service routing-related commands cannot be executed.

Error Message    SE-SR-3-180305:Failed to receive notifications from the data server at 
<string> - <string>.

Explanation    The SR failed to receive data from the data server when the debug content-routing commands are executed. This error message appears when the debug content-routing commands are executed and an error occurs in the communication process. If this message appears only occasionally, it is an informational message. Otherwise, its appearance requires investigation, and the debug content-routing commands will always fail.

Recommended Action    If the debug content-routing commands always fail, restarting the system should provide a temporary workaround. Send all syslog files to Cisco TAC for further analysis.

Error Message    SE-SR-3-180306:Failed to create thread at <string>.

Explanation    This message appears whenever the SR starts up and fails to create a thread. This error can significantly affect normal functioning of the SR and requires immediate attention.

Recommended Action    Restarting the system might provide a temporary workaround. Send all syslog files to Cisco TAC for further analysis.

Error Message    SE-SR-4-180307:Failed to free resources at <string> - <string>.

Explanation    The SR failed to free resources when executing the debug content-routing commands. This message appears every time the debug content-routing commands are executed. The message might indicate failure of those commands and might affect subsequent execution of other service routing-related commands.

Recommended Action    Restarting the system might provide a temporary workaround. Send the output of the show process memory command and all syslog files to Cisco TAC for further analysis.

Error Message    SE-SR-4-180308:Failed to receive entire message at <string> - 
<string>.

Explanation    The SR failed to receive data from the data server when executing commands related to service routing. This message appears whenever service routing-related commands are executed. The message might indicate failure of the commands and might affect subsequent execution of other service routing-related commands.

Recommended Action    Restarting the system might provide a temporary workaround. Send the output of the show process memory command and all syslog files to Cisco TAC for further analysis.

Error Message    SE-SR-5-180309:Failed to register to with data server - <string>.

Explanation    The SR failed to register with the data server for service routing-related commands other than the debug content-routing commands. The SR then tries to register every 60 seconds. This message only appears when the SR starts up. This message should be treated as a notice level message only if it appears fewer than 5 times. It should be escalated to a critical level message if it appears more than 5 times in a row. Ignoring this error message can cause service routing-related commands other than the debug content-routing commands to fail.

Recommended Action    Restarting the system might provide a temporary workaround. Send the output of the show process memory command and all syslog files to Cisco TAC for further analysis.

Error Message    SE-SR-4-180310:Failed to unregister from data server at <string> - 
<string>.

Explanation    The SR failed to unregister from the data server for service routing-related commands other than the debug content-routing commands. This error message appears when the SR exits or when it tries to reregister after a communication error.

Recommended Action    No serious consequences result from this error. Send the output of the show process memory command and all syslog files to Cisco TAC for further analysis.

Error Message    SE-SR-3-180311:Failed to get CLI action information from data server 
at <string> - <string>.

Explanation    The SR failed to receive data from the data server when executing service routing-related commands other than the debug content-routing commands. This message appears whenever a single service routing-related command other than the debug content-routing commands is executed and there is an error in communication. If this message appears only occasionally, it is an information level message. Otherwise, its appearance requires investigation, and service routing-related commands other than the debug content-routing commands will always fail.

Recommended Action    If service routing-related commands other than the debug content-routing commands always fail, restarting the system should provide a temporary workaround. Send the output of the show process memory command and all syslog files to Cisco TAC for further analysis.

Error Message    SE-SR-3-180312:Failed to build response to data server at <string> - 
<string>.

Explanation    The SR failed to build a response to the data server when executing service routing-related commands other than debug content-routing commands. This message appears whenever a service-routing related command other than debug content-routing is executed and an error occurs in building a response. If this message appears only occasionally, it is an informational message. Otherwise, its appearance requires investigation, and service routing-related commands other than the debug content-routing commands will always fail.

Recommended Action    If service routing-related commands other than the debug content-routing commands always fail, restarting the system should provide a temporary workaround. Send the output of the show process memory command and all syslog files to Cisco TAC for further analysis.

Error Message    SE-SR-3-180313:Failed to send response to data server at <string> - 
<string>.

Explanation    The SR failed to send a response to the data server when executing service routing-related commands other than the debug content-routing commands. This message appears whenever a single service routing-related command other than debug content-routing is executed and an error occurs in responding to the data server. This error message is informational only if it occurs occasionally. Otherwise, its appearance requires investigation, and service routing-related commands other than the debug content-routing commands will always fail.

Recommended Action    If service routing-related commands other than the debug content-routing commands always fail, restarting the system should provide a temporary workaround. Send the output of the show process memory command and all syslog files to Cisco TAC for further analysis.

Error Message    SE-SR-5-180314:Receive a service routing API request in wrong format: 
<string>.

Explanation    The SR has received a service routing API request in the wrong format. The detail should be given in the end of the message. This message appears whenever the service routing API feature is enabled on an SR and a service routing API request in the wrong format is received. This message is informational only.

Recommended Action    Examine why a service routing API request in the wrong format is sent to the SR. The SR itself functions correctly when this message appears.

SSHD Messages

Error Message    SE-SSHD-0/1/2/3/4/5/6-440000:[failure-description].

Explanation    The native Linux SSHD code exposes error or notice or information.

Recommended Action    If this message occurs, check the SSHD configuration or device configuration. Contact Cisco TAC if the message appears frequently.

Error Message    SE-SSHD-3-440001: read [ssh_session_file] failed, 
errno=[err_code]([failure-description]). 

Explanation    The SSH service fails in reading ssh_session_file.

Recommended Action    If this message occurs occasionally, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-SSHD-3-440002:write [ssh_session_file] failed, 
errno=[err_code]([failure-description]). 

Explanation    The SSH service fails in writing ssh_session_file.

Recommended Action    If this message occurs occasionally, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-SSHD-3-440003:lseek [ssh_session_file] failed, 
errno=[err_code]([failure-description]). 

Explanation    The SSH service fails in seeking ssh_session_file.

Recommended Action    If this message occurs occasionally, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-SSHD-3-440004:can't open [ssh_session_file], 
errno=[err_code]([failure-description]). 

Explanation    The SSH service fails in opening ssh_session_file.

Recommended Action    If this message occurs occasionally, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-SSHD-3-440005:can't create [ssh_session_file], 
errno=[err_code]([failure-description]). 

Explanation    The SSH service fails in creating ssh_session_file.

Recommended Action    If this message occurs occasionally, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-SSHD-3-440006:failed to start /usr/sbin/sshd, 
[failure-description]. 

Explanation    The SSH service fails in starting the SSHD process.

Recommended Action    Retry the related ssh command, restart SSH service, and reboot the device. Contact Cisco TAC if this message appears frequently.

Error Message    SE-SSHD-3-440007:usr/sbin/sshd did not exit, [failure-description]. 

Explanation    The SSH service fails because the SSHD process did not exit.

Recommended Action    Retry the related ssh command, restart SSH service, and reboot the device. Contact Cisco TAC if this message appears frequently.

Error Message    SE-SSHD-3-440008:ssh session failed, possibly because of incorrect 
login. 

Explanation    The active SSH session fails, possibly because of an incorrect login, or because of internal SSHD errors.

Recommended Action    Retry the SSH login with correct the username or password.

Error Message    SE-SSHD-3-440009:ssh session succeeded. 

Explanation    The active SSH session proceeded successfully.

Recommended Action    No action is required.

Error Message    SE-SSHD-3-440010:Internal error: Could not change owner (error). 

Explanation    SSH could not be enabled due to an internal error.

Recommended Action    Contact Cisco TAC.

SSRV Messages

Error Message    SE-SSRV-3-678300:Error occurred in Streaming Server. <error msg>. 

Explanation    An error occurred in the Streaming server.

Recommended Action    No action is required.

Error Message    SE-SSRV-4-678400:[Procedure] The stream bitrate(bitrate) is greater 
than limit, refuse the request. 

Explanation    The stream bitrate is greater than the incoming or outgoing limit. The request is refused.

Recommended Action    No action is required.

Error Message    SE-SSRV-4-678401:[Procedure] The live session bitrate(bitrate) is 
greater than limit, not starting it. 

Explanation    The live session bitrate is greater than the incoming or outgoing limit. The Streaming server refuses to create it.

Recommended Action    No action is required.

STATS Messages

Error Message    SE-STATS-4-600000:register_edm: edm reg err (ret = [error_code]). 

Explanation    The statistics provider application could not register with the data server.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-STATS-4-600001:ds_connect: ds connect err (ret = [error_code]). 

Explanation    The statistics provider application could not connect to the data server.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-STATS-4-600002:msg get err (ret=[error_code]). 

Explanation    The statistics provider application could not retrieve a message from the data server.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-STATS-4-600003:get edm info err (ret=[error_code]) 

Explanation    The statistics provider application could not retrieve information from the data server.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-STATS-3-600004:Failed to open /proc/net/netstat. 

Explanation    The statistics provider application could not open the proc interface.

Recommended Action    Check the CLI again. Contact Cisco TAC if this problem persists.

Error Message    SE-STATS-3-600005: / proc/net/netstat header line has unexpected 
format. Possible kernel version and cache application code mismatch. header line 
= [line], cache expects line = [line]. 

Explanation    The /proc/net/netstat format and the format expected by the statistics provider application vary.

Recommended Action    Contact Cisco TAC.

Error Message    SE-STATS-3-600006: / proc/net/netstat had sscanf parsing error. 
num_items read = %d, num_items expected = 65. 

Explanation    The /proc/net/netstat format and the format expected by the statistics provider application vary.

Recommended Action    Contact Cisco TAC.

Error Message    SE-STATS-3-600007:Failed to open /proc/net/snmp. errno: [error], 
[description]. 

Explanation    The statistics provider application could not open the proc interface.

Recommended Action    Contact Cisco TAC.

Error Message    SE-STATS-3-600008:Failed to read /proc/net/snmp. errno: [error], 
[description]. 

Explanation    The statistics provider application could not read the proc interface.

Recommended Action    Contact Cisco TAC.

Error Message    SE-STATS-3-600009:Failed to read /proc/net/snmp. End-of-file. 

Explanation    The statistics provider application could not read the proc interface. No data was read.

Recommended Action    Contact Cisco TAC.

Error Message    SE-STATS-3-600010: / proc/net/snmp has more data than cache expects: 
possible kernel version and cache application code mismatch. 

Explanation    The format of the /proc/net/snmp interface varies from the expected format.

Recommended Action    Contact Cisco TAC.

Error Message    SE-STATS-3-600011: / proc/net/snmp header line has unexpected format. 
Possible kernel version and cache application code mismatch. ix = [itemno], header 
line = [header], cache expects line = [expected]. 

Explanation    The format of the /proc/net/snmp interface varies from expected the format.

Recommended Action    Contact Cisco TAC.

Error Message    SE-STATS-3-600012: / proc/net/snmp sscanf parsing error STAT_NET_IP 
entry. num_items read = %d, num_items expected = 19. 

Explanation    The format of the /proc/net/snmp interface varies from expected the format.

Recommended Action    Contact Cisco TAC.

Error Message    SE-STATS-3-600013: / proc/net/snmp sscanf parsing error STAT_NET_ICMP 
entry. num_items read = %d, num_items expected = 26. 

Explanation    The format of the /proc/net/snmp interface varies from the expected format.

Recommended Action    Contact Cisco TAC.

Error Message    SE-STATS-3-600014: / proc/net/snmp sscanf parsing error STAT_NET_TCP 
entry. num_items read = %d, num_items expected = 21. 

Explanation    The format of the /proc/net/snmp interface varies from the expected format.

Recommended Action    Contact Cisco TAC.

Error Message    SE-STATS-3-600015: / proc/net/snmp sscanf parsing error STAT_NET_UDP 
entry num_items read = %d, num_items expected = 4. 

Explanation    The format of the /proc/net/snmp interface varies from the expected format.

Recommended Action    Contact Cisco TAC.

Error Message    SE-STATS-3-600016: / proc/net/snmp has more data than cache expects: 
chars read = [chars read] chars processed = [chars processed] possible kernel 
version and cache application code mismatch. 

Explanation    The format of the /proc/net/snmp interface varies from the expected format.

Recommended Action    Contact Cisco TAC.

Error Message    SE-STATS-3-600017:malloc for fds failed. 

Explanation    Cannot allocate memory.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-STATS-6-600018:Returning IP/ICMP/UDP/TCP stats. 

Explanation    Statistics for the specified protocol were returned.

Recommended Action    No action is required.

Error Message    SE-STATS-6-600019:Clearing IP/ICMP/UDP/TCP stats. 

Explanation    Statistics for the specified protocol were cleared.

Recommended Action    No action is required.

Error Message    SE-STATS-5-600020:Statistics thread startup notice. 

Explanation    Logs the thread and process IDs of the statistics thread of the SR.

Recommended Action    No action is required.

Error Message    SE-STATS-5-600021:Statistics thread stack space notice. 

Explanation    Logs the location of the thread stack space for the statistics thread of the SR.

Recommended Action    No action is required.

Error Message    SE-STATS-3-600022:Failed to create Service Router statistics thread. 

Explanation    The SR statistics thread could not be created for some reason. Statistics are not gathered.

Recommended Action    The device should be restarted as such a problem might be indicative of a system-wide memory shortfall. Contact Cisco TAC if this problem persists.

STDBY Messages

Error Message    SE-STDBY-3-522001:Standby item protection semaphore 
open/write/signal/close error. 

Explanation    The standby process encountered a problem while trying to access the semaphore that protects the standby data server item.

Recommended Action    Contact Cisco TAC.

Error Message    SE-STDBY-4-522002:Interface <interface> is down. 

Explanation    The standby process has found that the interface <interface> is down.

Recommended Action    Check the cable, switch configuration, and the SE's interface configuration for any problems. Execute the shut and no shut commands on the SE interface. If the interface is still down, contact Cisco TAC.

Error Message    SE-STDBY-4-522003:Unable to reach the gateway. 

Explanation    The standby process has found that the SE is no longer able to reach the default gateway.

Recommended Action    Manually ping the default gateway. If the ping does not work, look for any network problems and the router configuration. If the ping works, contact Cisco TAC.

Error Message    SE-STDBY-4-522004:Interface <interface> has seen more errors than 
allowed. 

Explanation    The standby process has found that the currently active interface is experiencing excessive input and output errors.

Recommended Action    Look for any problems in the switch and SE interface configurations. If you find any problems, contact Cisco TAC.

Error Message    SE-STDBY-7-522005:Standby group <group no> is up on <interface>. 

Explanation    The standby group is currently active on the interface <interface>.

Recommended Action    No action is required.

Error Message    SE-STDBY-3-522006:Standby group <group no> can't be brought up. 

Explanation    No member interfaces can be brought up in the specified standby group.

Recommended Action    Check the syslog files for failures on the related member interfaces.

Error Message    SE-STDBY-3-522007:Error <err no> when raising alarm <alarm 
item>(<alarm description>). 

Explanation    The standby process failed to raise the specified alarm.

Recommended Action    Check the syslog files for other alarm-related failures. Alarm information on the device could be inconsistent and a reload of the device might be required for recovery.

Error Message    SE-STDBY-3-522008:Error <err no> when clearing alarms in module 
<module name>. 

Explanation    The standby process failed to clear raised alarms in the group. The standby group name is represented in <module name>.

Recommended Action    Check the syslog files for other alarm-related failures. Alarm information on the device could be inconsistent and a reload of the device might be required for recovery.

Error Message    SE-STDBY-3-522009:Error <err no> when binding to nodehealthds. 

Explanation    The standby process failed to bind to the node health monitor database.

Recommended Action    Check the syslog files for more specific failures on the node health monitor database.

STREAMCACHE Messages

Error Message    SE-STREAMCACHE-3-673000:[Procedure] Invalid options passed. 

Explanation    Options passed in are invalid.

Recommended Action    Pass the correct arguments and retry the command.

Error Message    SE-STREAMCACHE-3-673001:[Procedure] Must pass in Real Proxy and RTSP 
Redirector binary path. 

Explanation    An invalid path is specified. Must pass the Real Proxy and RTSP Redirector binary path.

Recommended Action    Pass the correct binary path and retry the command.

Error Message    SE-STREAMCACHE-3-673002:[Procedure] Failed to execute IP address check 
script <error_mesg>. 

Explanation    Failed to execute the script that checks for the IP address.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673003:[Procedure] Host name not configured 
<error_mesg>. 

Explanation    The hostname configuration is not available.

Recommended Action    Configure the hostname and retry the command.

Error Message    SE-STREAMCACHE-3-673004:[Procedure] Real Proxy needs hostname other 
than local host <error_mesg>. 

Explanation    The Real Proxy needs a hostname other than the local host.

Recommended Action    Configure the hostname other than the local host and retry the command.

Error Message    SE-STREAMCACHE-3-673005:[Procedure] No IP address available in 
/etc/hosts. <error_mesg>. 

Explanation    No IP address is available in the /etc/hosts file.

Recommended Action    Configure the IP address and retry the command.

Error Message    SE-STREAMCACHE-3-673006:[Procedure] Unknown return status from IP 
address check script. 

Explanation    Invalid return status received from the IP address check script.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673007:[Procedure] Failed to spawn a process/thread 
<error_mesg>. 

Explanation    Failed to spawn a process or thread.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673008:[Procedure] MonitorMediaConfigAndWaitProcess 
failed. 

Explanation    MonitorMediaConfigAndWaitProcess failed. Retry the command.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673009:[Procedure] Failed to set the resource limit 
<error_mesg>. 

Explanation    Failed to set the resource limit.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673010:[Procedure] Failed to bind to sysdb 
<error_mesg>. 

Explanation    Failed to bind to sysdb.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673011:[Procedure] Failed to initialize the status 
collector <error_mesg>. 

Explanation    Failed to initialize the status collector.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673012:[Procedure] - Unknown read event 
<error_message>. 

Explanation    Unknown read event. This can be caused by an internal error.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-STREAMCACHE-3-673013:[Procedure] - Failed to [action] 
[directory_name] directory <error_mesg>. 

Explanation    Failed to create or open or change directory. This can be caused by an internal error.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-STREAMCACHE-3-673014:[Procedure] - Failed to get IP address of 
media proxy. 

Explanation    Failed to get the IP address of media proxy.

Recommended Action    Check the IP address configuration. If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-STREAMCACHE-3-673015:[Procedure] - Failed to get item <error_mesg>. 

Explanation    Failed to get item.

Recommended Action    Retry the command. Contact Cisco TAC if the message appears frequently.

Error Message    SE-STREAMCACHE-3-673016:[Procedure] - Failed to start a new session 
<error_mesg>. 

Explanation    Failed to start a new session.

Recommended Action    Retry the command. Contact Cisco TAC if the message appears frequently.

Error Message    SE-STREAMCACHE-3-673017:[Procedure] - Failed to start a new session. 

Explanation    Failed to start a new session.

Recommended Action    Retry the command. Contact Cisco TAC if the message appears frequently.

Error Message    SE-STREAMCACHE-3-673018:[Procedure] - System call failed: <system 
call> <error_mesg>. 

Explanation    The system call failed. The system might be in an unstable state.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-STREAMCACHE-3-673019:[Procedure] - Program <program name> died 
quickly during restart. Stop spawning. 

Explanation    The child process failed immediately after it started last time. Stop spawning it to avoid a spawning crashing process.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-STREAMCACHE-3-673020:[Procedure] - Failed to restart a process 
<process name>. 

Explanation    Failed to restart a process.

Recommended Action    If this message occurs periodically, ignore it. If this message appears frequently, contact Cisco TAC.

Error Message    SE-STREAMCACHE-3-673021:[Procedure] - WaitProcess failed. 

Explanation    WaitProcess failed.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673022:[Procedure] - Program <program name> died due 
to signal <signal number>. 

Explanation    The program exited because of a signal.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673023:[Procedure] - Program <program name> died 
abnormally with status <status code>. 

Explanation    The program exited abnormally.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673024:[Procedure] - Unexpected value of item <item 
name>. 

Explanation    Received unexpected value of item.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673025:[Procedure] - Failed to get notification info. 

Explanation    Failed to get notification information.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673026:[Procedure] Failed to unbind from sysdb 
<error_mesg>. 

Explanation    Failed to bind from sysdb.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673027:[Procedure] Failed to Register [action] 
<error_mesg>. 

Explanation    Failed to register verification or notification.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673028:[Procedure] Failed to get [action] information 
<error_mesg>. 

Explanation    Failed to get verification or notification information.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673029:[Procedure] Failed to free ven resources 
<error_mesg>. 

Explanation    Failed to free ven resources.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673030:[Procedure] Failed to build EDM/verification 
ACK <error_mesg>. 

Explanation    Failed to build verification or EDM acknowledgment.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673031:[Procedure] Item [fields] is NULL 
<error_mesg>. 

Explanation    Item name/new value/old value is empty.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673032:[Procedure] Unexpected sysdb type/item length 
<error_mesg>. 

Explanation    Unexpected sysdb type and item length.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673033:[Procedure] Failed to receive whole message 
<error_mesg>. 

Explanation    Failed to receive the entire message.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673034:[Procedure] Received unexpected message type 
<error_mesg>. 

Explanation    Received unexpected message type.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673035:[Procedure] Failed to send ACK <error_mesg>. 

Explanation    Failed to send an acknowledgment.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673036:[Procedure] Failed to get EDM information 
<error_mesg>. 

Explanation    Failed to get EDM information.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673037:[Procedure] EDM List not supported 
<error_mesg>. 

Explanation    The EDM list is not implemented.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673038:[Procedure] EDM [action] failed <error_mesg>. 

Explanation    The EDM registration or unregistration failed.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673039:[Procedure] Failed in RTSP reconfiguration 
<error_mesg>. 

Explanation    An error occurred during RTSP reconfiguration.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673040:[Procedure] [Resource] operation <operation 
name> failed <error_mesg>. 

Explanation    An error occurred during file or pipe operation.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673041:[Procedure] Unknown EDM item <item name> 
failed <error_mesg>. 

Explanation    Unknown EDM item.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673042:[Procedure] gethostbyname failed 
<error_mesg>. 

Explanation    Failed to get host details by name.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673043:[Procedure] Failed to get local IP address 
<error_mesg>. 

Explanation    Failed to get local IP address.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673044:[Procedure] Failed to register as stats EDM.

Explanation    Failed to register as stats Extended Data Manager.

Recommended Action    Retry the command. Contact Cisco TAC if this message appears frequently.

Error Message    SE-STREAMCACHE-3-673045:[Procedure] Could not open pid file.

Explanation    Cannot open PID file.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-STREAMCACHE-3-673046:Generic message.

Explanation    This is a descriptive error message.

Recommended Action    No action is required.

Error Message    SE-STREAMCACHE-5-675001:[Procedure] Memory value in Real Proxy -m 
option. 

Explanation    It is the amount of physical memory the Real Proxy uses.

Recommended Action    No action is required.

Error Message    SE-STREAMCACHE-6-676000:[Procedure] Hostname check in /etc/hosts is 
successful. 

Explanation    Successfully checked the hostname in the /etc/hosts file.

Recommended Action    No action is required.

Error Message    SE-STREAMCACHE-6-676001:[Procedure] Shutting down, no spawning of 
child anymore. 

Explanation    Shutting down in progress. No spawning of child process.

Recommended Action    No action is required.

Error Message    SE-STREAMCACHE-6-676002:[Procedure] Process with PID <PID> exited. 

Explanation    Process exited.

Recommended Action    No action is required.

Error Message    SE-STREAMCACHE-6-676003:[Procedure] PID <pid> not my direct child. 

Explanation    This process is a grandchild.

Recommended Action    No action is required.

Error Message    SE-STREAMCACHE-6-676004:[Procedure] Program <Program name> exited 
normally with code <status code>. 

Explanation    The program exited normally.

Recommended Action    No action is required.

Error Message    SE-STREAMCACHE-6-676005:[Procedure] Killing all processes related to 
<Path>. 

Explanation    Killing all the processes that are descendents of this process.

Recommended Action    No action is required.

Error Message    SE-STREAMCACHE-6-676006:[Procedure] Failed to unregister [service] 
<error_mesg>. 

Explanation    Failed to unregister verification or notification.

Recommended Action    No action is required.

Error Message    SE-STREAMCACHE-6-676007:[Procedure] System call failed: <system call>. 

Explanation    The system call failed.

Recommended Action    No action is required.

Error Message    SE-STREAMCACHE-7-677001:[get_physical_memory] Memory. 

Explanation    The amount of physical memory.

Recommended Action    No action is required.

Error Message    SE-STREAMCACHE-7-677002:[write_pid_to_file]. 

Explanation    Written PID to PID-file.

Recommended Action    No action is required.

Error Message    SE-STREAMCACHE-7-677003:[get_mcm_pid]. 

Explanation    Got MCM PID from PID-file.

Recommended Action    No action is required.

Error Message    SE-STREAMCACHE-7-677004:[process_notification]. 

Explanation    Send signal SIGUSR1 to MCM process.

Recommended Action    No action is required.

Error Message    SE-STREAMCACHE-7-677005:debug message. 

Explanation    This is a debug message.

Recommended Action    No action is required.

SYS Messages

Error Message    SE-SYS-[priority]-900000:[Kernel Message]. 

Explanation    These messages are generated by the kernel and might be useful for debugging a problem that is encountered. More severe priorities (0 is the highest, 7 the lowest) are more likely to be of concern.

Recommended Action    Give these messages to Cisco TAC when a problem is encountered.

Error Message    SE-SYS-5-900001:[system bootup messages]. 

Explanation    These are system bootup messages.

Recommended Action    These messages are mostly informational, but could be of help when debugging certain bootup problems.

Error Message    SE-SYS-5-900002:[system bootup messages]. 

Explanation    These are system bootup messages (from system initialization until syslogd is started).

Recommended Action    These messages are mostly informational, but could be of help when debugging certain bootup problems.

Error Message    SE-SYS-5-900003:[Kernel crash analysis messages]. 

Explanation    These messages indicate that the kernel crashed in the past and contain information that might help in diagnosing the problem.

Recommended Action    Contact Cisco TAC.

SYSMON Messages

Error Message    SE-SYSMON-3-445000:Error in read the req, errno: [error].

Explanation    The System Fault Monitor could not read a request, so it was skipped.

Recommended Action    No action is required.

Error Message    SE-SYSMON-3-445001:Failed to set NONBLOCK for new_fd, ret [status], 
errno [error no]. 

Explanation    The System Fault Monitor could not set the NONBLOCK attribute on a request, so it was skipped.

Recommended Action    No action is required.

Error Message    SE-SYSMON-3-445002:select: ret = [status], errno = [error no].

Explanation    The select call within the System Fault Monitor failed.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-SYSMON-3-445003:Incorrect system id [system identifier].

Explanation    An unknown system identifier was received by the System Fault Monitor.

Recommended Action    Contact Cisco TAC.

Error Message    SE-SYSMON-3-445004:Incorrect device id [device id].

Explanation    An unknown device identifier was received by the System Fault Monitor.

Recommended Action    Contact Cisco TAC.

Error Message    SE-SYSMON-3-445005:Incorrect timestamp [timestamp].

Explanation    An improper time stamp was received by the System Fault Monitor.

Recommended Action    Contact Cisco TAC.

Error Message    SE-SYSMON-3-445006:Incorrect severity [severity level].

Explanation    An unknown severity level was received by the System Fault Monitor.

Recommended Action    Contact Cisco TAC.

Error Message    SE-SYSMON-3-445007:error [error code] when binding to data server. 

Explanation    The System Fault Monitor could not make a connection to the data server. A fault might not be reported.

Recommended Action    Reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-SYSMON-3-445008:error [error code] when setting [data item name].

Explanation    The System Fault Monitor could not set a value for the specified data server item name. A fault might not be reported.

Recommended Action    Reload the device. Contact Cisco TAC if this problem persists

Error Message    SE-SYSMON-5-445009:sysmon: entering start_loop. 

Explanation    The System Fault Monitor is starting up.

Recommended Action    No action is required.

Error Message    SE-SYSMON-3-445010:Fault detected: [description].

Explanation    The System Fault Monitor has detected a fault.

Recommended Action    Take corrective action to fix the fault. If no fault actually exists, contact Cisco TAC.

Error Message    SE-SYSMON-5-445011:Fault cleared: [description].

Explanation    The System Fault Monitor has cleared a fault.

Recommended Action    No action is required.

Error Message    SE-SYSMON-1-445012:disk%02d has a serious file system problem. reload 
the system to recover from this failure. 

Explanation    A disk has a serious but recoverable file system-related problem.

Recommended Action    Reload the system.

Error Message    SE-SYSMON-3-445013:Failed to turn off journaling on num:num. 

Explanation    A disk has a serious but recoverable file system-related problem.

Recommended Action    Reload the system. Contact Cisco TAC if this problem persists.

Error Message    SE-SYSMON-3-445014:Could not add num:num to the list of failed 
partitions(s). 

Explanation    A disk has a serious but recoverable file system-related problem.

Recommended Action    Reload the system.

SYSUTL Messages

Error Message    SE-SYSUTL-1-800001:RAM disk is full. 

Explanation    The system is unusable soon.

Recommended Action    Reload the SE and report to Cisco TAC as soon as possible. Include syslog messages following 800001 for detailed analysis.

Error Message    SE-SYSUTL-3-800002:RAM disk usage is growing.

Explanation    The root file system is getting full.

Recommended Action    Watch for the SE-SYSUTL-1-800001 message.

Error Message    SE-SYSUTL-5-800003:<username> login on <ttyname> from <host>. 

Explanation    A privileged user has logged in.

Recommended Action    No action is required.

Error Message    SE-SYSUTL-6-800004:<username> login on <ttyname> from <host>. 

Explanation    A non-privileged user has logged in.

Recommended Action    No action is required.

Error Message    SE-SYSUTL-6-800005:Console at <ttyname> by <username>. 

Explanation    A user has logged in from the console line.

Recommended Action    No action is required.

Error Message    SE-SYSUTL-5-800006:File removed <filename> And other <number> file(s) 
removed Core file(s) removed <filename>.

Explanation    SYSFS space is low. The system starts to automatically remove certain files.

Recommended Action    Execute the show sysfs volumes command to check the SYSFS usage. Remove any old files if SYSFS is over 80 percent used.

SYSVINIT Messages

Error Message    SE-SYSVINIT-0/1/2/3/4/5/6-810040:[Description]. 

Explanation    These messages are generated by sysvinit.

Recommended Action    If high priority error messages frequently occur, contact Cisco TAC.

TELNET Messages

Error Message    SE-TELNET-0/1/2/3/4/5/6-810050:[Description]. 

Explanation    These messages are generated by Telnet.

Recommended Action    If high priority error messages frequently occur, contact Cisco TAC.

TFTP Messages

Error Message    SE-TFTP-7-450001:tftpd: <various tftpd debug messages>. 

Explanation    This debug ID is used for debugging TFTP code.

Recommended Action    No action is required.

Error Message    SE-TFTP-3-450002:tftpd: Cannot create transaction logs: <error_code>. 

Explanation    The system could not create a TFTP transaction-log socket.

Recommended Action    No action is required.

Error Message    SE-TFTP-3-450003:tftpd: Unable to send transaction log data: return= 
<return-code> errno= <error-no> errstr= <error-string>. 

Explanation    The system was unable to send the data to the TFTP transaction-log socket.

Recommended Action    Check if the transaction log command is enabled. If it is not enabled, then enable it.

Error Message    SE-TFTP-3-450004:tftp main(): Failed to bind to SysDB-Root with error 
<error_code>. 

Explanation    The system was unable to bind to the data from SysDB.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-TFTP-3-450005:tftp main(): SYSDB returned NULL tftp_ptr. 

Explanation    The system was successful in reading the item from SysDB, but the item has a null value assigned to it.

Recommended Action    No action is required.

Error Message    SE-TFTP-3-450006:tftp main(): Item not found on the data server. 

Explanation    The system was unable to find the data on SysDB. sysdb_itm_get() failed with a return code as SYSDB_ERROR_NOTFOUND.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-TFTP-3-450007:tftp main(): sysdb_item_get failed with error code 
<error_code>. 

Explanation    sysdb_item_get() failed with an error code.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-TFTP-5-450008:NO TFTP-access-list is configured: A <read or write> 
request denied for client <client-ip> for file <file-name>. 

Explanation    For TFTP to be functional, a TFTP server access list must be configured on the SE.

Recommended Action    Configure a TFTP server access list and Standard Access List on the SE.

Error Message    SE-TFTP-5-450009:NO Valid access-list is configured for access-list# 
<#> A <read or write> request denied for client <client-ip> for file <file-name>. 

Explanation    For TFTP to be functional, a Standard Access List is needed.

Recommended Action    Configure a Standard Access List for TFTP on the SE.

Error Message    SE-TFTP-5-450010:Failed to open tftp config file. 

Explanation    The TFTP daemon could not open the /etc/tftpd.conf file.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-TFTP-3-450011:tftpd: ioctl call failed: <error details>. 

Explanation    The TFTP daemon ioctl (FIONBIO) call to open the configuration file failed.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-TFTP-3-450012:tftpd: recvfrom() failed: <error details>. 

Explanation    The TFTP daemon call to recvfrom() returned an error.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-TFTP-3-450013:tftpd: fork failed: <error details>. 

Explanation    The TFTP daemon call to fork() failed.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-TFTP-2-450014:tftpd: can't drop root privileges: <error details>. 

Explanation    The TFTP daemon has to keep root privileges to allow files to be created.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-TFTP-3-450015:tftpd: socket creation to peer failed: <error 
details>. 

Explanation    The TFTP daemon call to socket() failed.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-TFTP-3-450016:tftpd: socket bind to peer failed: <error details>. 

Explanation    The TFTP daemon call to bind() failed.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-TFTP-4-450017:tftpd: Cannot access base file system. 

Explanation    The TFTP daemon could not access the /local directory.

Recommended Action    No action is required.

Error Message    SE-TFTP-4-450018:tftpd: Invalid default directory: <default 
directory>. 

Explanation    The TFTP daemon could not access the default directory to search the requested file.

Recommended Action    Verify the default directory exists, and create it if it does not.

Error Message    SE-TFTP-4-450019:tftpd: Blocked illegal request for <filename>. 

Explanation    The TFTP daemon cannot access the parent directory.

Recommended Action    No action is required.

Error Message    SE-TFTP-3-450020:tftpd: sento error: <error details>. 

Explanation    The TFTP daemon failed to send the data to the client.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-TFTP-3-450021:tftpd: ACK read error: <error details>. 

Explanation    There was a TFTP daemon error while reading the acknowledgement sent by the client.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-TFTP-3-450022:tftpd: ACK send error: <error details>. 

Explanation    There was a TFTP daemon error while sending the acknowledgement to the client.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-TFTP-3-450023:tftpd: Read error: <error details>. 

Explanation    There was a TFTP daemon error while reading the data from the client.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-TFTP-3-450024:tftpd: NAK error: <error details>. 

Explanation    There was a TFTP daemon error while sending the NAK (negative acknowledgment).

Recommended Action    Contact Cisco TAC if this problem persists.

TRNSLG Messages

Error Message    SE-TRNSLG-3-460001:TRANSLOG: tlog_begin_mark(): write failed. 

Explanation    Write failed.

Recommended Action    No action is required.

Error Message    SE-TRNSLG-3-460002:Unable to open transaction log file. 

Explanation    Unable to open transaction log file.

Recommended Action    No action is required.

Error Message    SE-TRNSLG-3-460003:TRANSLOG: tlog_commit():write failed, errno = 

Explanation    Write failed.

Recommended Action    No action is required.

Error Message    SE-TRNSLG-3-460004:Log directory non-existent -transaction logging 
terminated. 

Explanation    The log directory does not exist.

Recommended Action    Check to see if the log directory exists.

Error Message    SE-TRNSLG-3-460005:Log path is not a directory - transaction logging 
terminated.

Explanation    The log path is not a directory.

Recommended Action    Check to see if the log path is a directory.

Error Message    SE-TRNSLG-3-460006:Logging file system nearly full and unable to 
delete.

Explanation    The logging file system is nearly full.

Recommended Action    No action is required.

Error Message    SE-TRNSLG-3-460007:TRANSLOG: translog_set_trap(): sysdb_item_set 
failed.

Explanation    Item set failed.

Recommended Action    No action is required.

Error Message    SE-TRNSLG-2-460008:TRANSLOG: system mem low. Clean up mem alloced. 

Explanation    The system memory is low.

Recommended Action    No action is required.

Error Message    SE-TRNSLG-2-460009:TRANSLOG: system mem low. Buffer allocation 
aborted. 

Explanation    Buffer allocation failed.

Recommended Action    No action is required.

Error Message    SE-TRNSLG-3-460010:TRANSLOG: tlog_end_mark(): write failed, errno =.

Explanation    Write failed.

Recommended Action    No action is required.

Error Message    SE-TRNSLG-5-460011:process info: tlog_logger_init()process_id. 

Explanation    process ID and pthread ID.

Recommended Action    No action is required.

Error Message    SE-TRNSLG-6-460012:<translog formatted message>. 

Explanation    An HTTP/FTP transaction log message sent to the syslog host configured in the transaction-logs logging host configuration command.

Recommended Action    No action is required.

Error Message    SE-TRNSLG-6-460013.

Explanation    Dropped %d translog messages to syslog log host because of the configured rate limit of <rate-limit>.

Recommended Action    No action is required.

Error Message    SE-TRNSLG-3-460014.

Explanation    Failed to send the translog message to the remote syslog host: <error details>.

Recommended Action    No action is required.

Error Message    SE-TRNSLG-3-460015.

Explanation    Failed to send the entire translog message to the remote syslog host: <error details>.

Recommended Action    No action is required.

Error Message    SE-TRNSLG-3-460016. 

Explanation    Failed to create a socket for sending to the remote syslog host <error details>.

Recommended Action    If rebooting the device does not help, contact Cisco TAC.

TVOUT Messages

Error Message    SE-TVOUT-7-470001:[debug message].

Explanation    Class of debug messages for TV-out service.

Recommended Action    No action is required.

Error Message    SE-TVOUT-3-470002:Unable to determine TV-out hardware: [error].

Explanation    An error occurred while accessing data about the type of TV-out hardware installed on the device.

Recommended Action    Re-enable the TV-out service. If this message persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470003:TV-out hardware was not detected: [error].

Explanation    TV-out hardware was not detected to be installed on the device. Either the hardware itself was not detected, or the detection software failed to run after the last device reload.

Recommended Action    Verify that a supported A/V decoder card is properly installed and reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-6-470004:TV-out hardware was detected: <card type>. 

Explanation    The A/V decoder card type was found installed on the device.

Recommended Action    No action is required.

Error Message    SE-TVOUT-3-470005:Cannot allocate memory for [target].

Explanation    A general memory allocation failure for the specified target. The system may be in an undefined state.

Recommended Action    Re-enable the TV-out service. If this message persists, reload the device. Because this message could be caused by low memory conditions, try reducing the overall number of services enabled. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470006:Unable to determine stream type: [error].

Explanation    An error occurred processing the stream type to be decoded. The system might be in an undefined state.

Recommended Action    Check the log for additional messages and further action. If no other messages are found, re-enable the TV-out service. If this message persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-4-470007:On file close: [system error].

Explanation    The close of a file descriptor generated a system error. The system might be in an undefined state.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470008:Cannot open <file>: [system error].

Explanation    Cannot open the specified file due to a system error. The system might be in an undefined state.

Recommended Action    Verify that delivery service replication status and the CDNFS are stable. Re-enable the TV-out service. If this message persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-4-470009:Unable to process overlay image: [error].

Explanation    Failed to process an overlay image for the on-screen display due to the error encountered.

Recommended Action    Verify any overlay image files are valid and meet TV-out specifications as detailed in the Cisco Internet Streamer CDS 2.4 Software Configuration Guide. Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-5-470010:On overlay image processing: [error].

Explanation    While processing an overlay image for the on-screen display, an error occurred that might cause the resulting display to be skewed or incomplete.

Recommended Action    Verify any overlay image files are valid and meet the TV-out specifications as detailed in the Cisco Internet Streamer CDS 2.4 Software Configuration Guide. Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470011:AV-001: Unable to open MPEG device interface. 

Explanation    Failed to open the control interface to the MPEG device driver. The system might be in an undefined state.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-4-470012:AV-001: Unable to setup OSD region: [error].

Explanation    An error occurred while setting up the on screen display region through the device driver.

Recommended Action    Verify that overlay image file parameters are valid as detailed in the Cisco Internet Streamer CDS 2.4 Software Configuration Guide. Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470013:AV-001: Unable to setup decode: [error].

Explanation    An error occurred while setting up the decode of a stream through the device driver.

Recommended Action    Verify that media file parameters are valid as detailed in the Cisco Internet Streamer CDS 2.4 Software Configuration Guide. Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-4-47014:AV-001: Unable to start OSD: [error].

Explanation    An error occurred while starting the on-screen display through the device driver.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470015:[sysdb error message].

Explanation    Class of sysdb error messages for the TV-out service.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-4-470016:[sysdb warning message].

Explanation    Class of sysdb warning messages for the TV-out service.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-5-470017:[sysdb notice message].

Explanation    Class of sysdb notice messages for the TV-out service.

Recommended Action    Re-enable the TV-out service if this error persists, or reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470018:Unable to connect to cms database: Cannot check 
[target].

Explanation    Unable to connect to the CMS database so the specified target cannot be retrieved.

Recommended Action    Verify that the CMS is enabled and running normally. Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470019:Failed query of cms database: [target] not found - 
[action].

Explanation    In a query of the CMS database, the specified target could not be found. This often indicates incomplete or missing data.

Recommended Action    Verify that CMS is enabled and running normally. Take the specified action, if any. Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470020:Unable to decode <file path> on <playlist>: [error].

Explanation    The decode of the specified file path on the specified playlist failed due to an error encountered. Partial decode might have occurred. The system might be in an undefined state.

Recommended Action    Check for additional messages and further action. Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-5-470021:Invalid <position> for <playlist> with <total 
files>: reset to top. 

Explanation    An invalid position occurred during the playback of the specified playlist, so playback was restarted. An invalid position might occur due to a dynamic change in the number of media files or by seeking through the playlist using playback controls. This message is generally harmless but might indicate a software issue.

Recommended Action    If this error persists, re-enable the TV-out service and reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-5-470022:Skipping [media type] on <playlist>: unavailable 
<url>. 

Explanation    The specified media type has been skipped on the specified playlist because the specified URL is not currently available on the device.

Recommended Action    Check log for additional messages and further action. Verify the delivery service assignment and manifest file attributes. This message is often transitory due to fluctuations in delivery service replication status. If this error persists, re-enable the TV-out service and reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-4-470023:Media file <url> will be skipped for duration of 
<playlist> due to playback error. 

Explanation    The media file specified by the URL is skipped for the duration of the specified playlist due to an error encountered when the media file stream was being decoded.

Recommended Action    Check for additional messages and further action. Verify that the media file is valid as detailed in the Cisco Internet Streamer CDS 2.4 Software Configuration Guide. If the media file is invalid, remove it from the playlist. If the media file is valid, verify that it is free of errors or corrupted data. Re-enable the TV-out service and reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-4-470024:Unable to determine next random position: [error].

Explanation    The playlist is unable to determine the next random position due to an error encountered and might be restarted.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-5-470025:Current schedule for <playlist> no longer applies. 

Explanation    The specified playlist detected a schedule modification that invalidated the current session. Playback of the specified playlist has been stopped.

Recommended Action    No action is required.

Error Message    SE-TVOUT-6-470026 :New <url> replaces old <url> on <playlist>. 

Explanation    Due to a delivery service configuration change, the old URL was replaced by the new URL on the specified playlist.

Recommended Action    No action is required.

Error Message    SE-TVOUT-3-470027:Unable to connect to uns for resolve of <url> on 
<playlist>. 

Explanation    TV-out service was unable to connect to the UNS service to determine the local file path for the specified URL on the specified playlist. The system might be in an undefined state.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-5-470028:Unknown <client> requests <state> for <playlist>. 

Explanation    An unknown client attempted to change the state of the specified playlist. The request has been ignored.

Recommended Action    No action is required.

Error Message    SE-TVOUT-4-470029:Select returned <errno>: [system error].

Explanation    A general failure occurred during socket communications. The system might be in an undefined state.

Recommended Action    If this error persists, re-enable the TV-out service and reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-4-470030:Invalid overlay image setting for <playlist>: 
[error].

Explanation    Detected an overlay image setting outside allowable parameters on the specified playlist.

Recommended Action    Verify that overlay image parameters are valid as detailed in the Cisco Internet Streamer CDS 2.4 Software Configuration Guide. If invalid, modify the playlist configuration. If valid, re-enable the TV-out service and reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-4-470031:Unable to set overlay image <url> for <playlist>. 

Explanation    An unspecified error occurred when setting up the overlay image using the specified URL for the specified playlist.

Recommended Action    Check for additional messages and further action. Re-enable of the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-5-470032:Invalid <request> received by <playlist> from 
<client>. 

Explanation    A request was received by a specified playlist from the specified client that was not understood. The request has been ignored.

Recommended Action    No action is required.

Error Message    SE-TVOUT-4-470033:TV-out signal default to <format>: [error].

Explanation    An error occurred when accessing the TV-out signal format configuration. The default format is used instead of the configured format.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470034:Unable to register as statistics EDM for <subtree>. 

Explanation    An unspecified error occurred when attempting to register as the External Data Manager for TV-out statistics. TV-out service statistics might be unavailable.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-5-470035:Unsupported message type received as statistics EDM. 

Explanation    An unsupported message type was received by the TV-out service. This is generally harmless but might indicate a software issue.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-6-470036:Processing statistics request for <item>. 

Explanation    This message notes a statistics request for the specified item.

Recommended Action    No action is required.

Error Message    SE-TVOUT-4-470037:Unable to process statistics request: [error].

Explanation    An error occurred during the processing of a statistics request. TV-out service statistics might be unavailable.

Recommended Action    If this error persists, re-enable the TV-out service and reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-6-470038:Device manager returned <number> available for 
playback. 

Explanation    This message notes the number of device interfaces that are available for playback.

Recommended Action    No action is required.

Error Message    SE-TVOUT-3-470039:Device manager returned no devices so playback 
cannot be attempted. 

Explanation    Because no device interfaces could be successfully initialized, playback is not attempted. TV-out service is in idle mode.

Recommended Action    Check log for additional messages and further action. Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470040:Device manager cannot init <number>: <status>. 

Explanation    One or more device interfaces failed to be initialized.

Recommended Action    Check log for additional messages and further action. Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-2-470041:Daemon failed: [system error].

Explanation    TV-out service failed to run as a background process and has exited. TV-out service might be automatically restarted.

Recommended Action    If this error persists and TV-out service is no longer running, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-2-470042:Exit in main after [type]: [exception].

Explanation    The specified exception was detected, causing the TV-out service to immediately exit. TV-out service might be automatically restarted.

Recommended Action    If this error persists and TV-out service is no longer running, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-6-470043:Returning result from Main: <result>. 

Explanation    An usual result was returned by the Main call. This is generally a harmless message but it could indicate a software issue.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-5-470044:Cannot create transaction logs: [system error].

Explanation    An error occurred that prevented the TV-out service from creating transaction logs. This generally indicates that transaction-logging is not enabled on the device.

Recommended Action    Verify that transaction-logging is enabled. If this error persists, re-enable the TV-out service and reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-5-470045:Unable to send transaction log data: [system error].

Explanation    Failed to send transaction log data due to the system error that occurred. The transaction log might be incomplete. The system might be in an undefined state.

Recommended Action    Verify that transaction-logging is enabled. If this error persists, re-enable the TV-out service and reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-6-470046:Initializing TV-out service. 

Explanation    This message notes that the TV-out service has been initialized. This occurs on startup and whenever an exception has occurred.

Recommended Action    No action is required.

Error Message    SE-TVOUT-4-470047:TV-out service Exception: [exception].

Explanation    The specified TV-out service exception has occurred. The TV-out service is re-initialized without a full restart.

Recommended Action    If this error persists, re-enable the TV-out service and reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-5-470048:Cannot create pid <file>: [system error].

Explanation    The specified PID file cannot be created due to a system error. This message is generally harmless but might indicate a software issue.

Recommended Action    If this error persists, re-enable the TV-out service and reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-5-470049:Trouble closing pid <file>: [system error].

Explanation    The specified PID file could not be closed normally due to a system error. This message is generally harmless but could indicate a software issue.

Recommended Action    If this error persists, re-enable the TV-out service and reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-4-470050:Cannot init uns client context : [status].

Explanation    The context for the UNS client interface failed to be initialized successfully.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-4-470051:Uns cannot resolve invalid URL <url>: [error].

Explanation    The specified URL could not by resolved to a local file path on the device because it was not understood because of the specified error.

Recommended Action    Verify the delivery service assignment and manifest file attributes. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-5-470052:Uns returned unsupported resolve action for <url>: 
[resolveAction].

Explanation    In a request to UNS for the local file path for the specified URL, an unsupported action was returned.

Recommended Action    Verify the delivery service assignment and manifest file attributes. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470053:Uns unable to provide file path for playable <url>. 

Explanation    The local file path could not be determined for the specified URL due to a problem encountered with a UNS object.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-4-470054:Uns unable to resolve <url>: [error].

Explanation    The specified URL was unable to be resolved to a local file path due to the error encountered.

Recommended Action    Verify the delivery service replication status and content attributes. Verify that acquisition and distribution processes are running normally. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470055:Uns rpc failed for [action]: [status].

Explanation    Unable to request the specified action due to failure in the remote procedure call to UNS. The system might be in an undefined state.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-6-470056:[playlist processing messages].

Explanation    Class of informational messages regarding playlist processing.

Recommended Action    No action is required.

Error Message    SE-TVOUT-5-470057:Unable to gracefully stop <playlist>. 

Explanation    An unspecified error occurred when the specified playlist was requested to stop. The playlist might subsequently be aborted.

Recommended Action    If this error persists, re-enable the TV-out service and reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-6-470058:Manual playback requested for <playlist>. 

Explanation    This message notes a manual playback request for the specified playlist.

Recommended Action    No action is required.

Error Message    SE-TVOUT-5-470059:Requested <playlist> is already active. 

Explanation    A playback request was made for the specified playlist but the specified playlist is already actively playing. The request is ignored.

Recommended Action    No action is required.

Error Message    SE-TVOUT-4-470060:Requested <playlist> is not available for playback. 

Explanation    A playback request was made for the specified playlist but it is currently unavailable.

Recommended Action    Verify that the playlist is assigned to the device. If it is assigned, verify that CMS is enabled and running normally. Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470061:Socket failure for [target]: [system error].

Explanation    A failure occurred in socket communications for the specified target due to a system error. The system might be in an undefined state.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470062:Unable to launch <playlist>: [error]. 

Explanation    The specified playlist could not be launched due to the error encountered. The system could be in an undefined state.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-5-470063:Calling to abort any active decode of <playlist>. 

Explanation    The specified playlist was requested to terminate while actively decoding a media file stream. This might occur if the TV-out service has been disabled, or the device has been reloaded.

Recommended Action    No action is required.

Error Message    SE-TVOUT-3-470064:Failed to send term signal to child <pid>: [system 
error]. 

Explanation    A system error occurred after requesting termination of the child process at the specified PID. The system might be in an undefined state.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-4-470065:Waitpid on child <pid> returned error: [system 
error]. 

Explanation    A system error occurred when checking the exit status of the child process at the specified PID. The last playback session might have been aborted unexpectedly.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-5-470066:Last playback session was in manual mode; 
relaunching <playlist>. 

Explanation    The specified playlist was automatically restarted in manual mode. This occurs when the last shutdown of the TV-out service caused the manual playback of the specified playlist to be aborted.

Recommended Action    No action is required.

Error Message    SE-TVOUT-4-470067:Unable to add <playlist> to playback list: [error]. 

Explanation    The specified playlist was unable to be added to the playback list due to the specified error. The specified playlist cannot be scheduled or manually launched.

Recommended Action    If this error persists, re-enable the TV-out service and reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470068:AV-002: sem_init error: <errno>. 

Explanation    The semaphore initialization operation failed. The system might be in an undefined state.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470069:AV-002: Unable to open w/o memory. 

Explanation    Initialization failed to obtain memory. The system might be in an undefined state.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470070:AV-002: Unable to open control interface: <status>. 

Explanation    Initialization failed to obtain a control interface handle to the driver. The system might be in an undefined state.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470071:AV-002: Unable to configure PUSH: <inputType>. 

Explanation    Initialization failed to put the interface into push mode. The system might be in an undefined state.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470072:AV-002: Unable to get push handle: <status>. 

Explanation    Initialization failed to get proper access to the driver. The system might be in an undefined state.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470073:AV-002: setupDecode - Unsupported stream type 
specified: <streamType>. 

Explanation    Interface was requested to set up for a stream type that it does not support.

Recommended Action    Contact Cisco TAC because this message indicates a problem with the higher layers of the software.

Error Message    SE-TVOUT-3-470074:AV-002: setupDecode - SetDemuxPUSH error: <status>. 

Explanation    An error occurred when setting up the interface for the stream type. The system might be in an undefined state.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470075:AV-002: setupDecode - PlayPUSH error: <status>. 

Explanation    An error occurred when entering the interface into play mode. The system might be in an undefined state.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470076:AV-002: decode - GetBuffer error: <status>. 

Explanation    An error occurred when attempting to get a buffer for the stream data. The system might be in an undefined state.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470077:AV-002: decode - PushBuffer error <status> when 
writing <bytesDecoded> of <streamLength> bytes. 

Explanation    An error occurred when attempting to push a buffer of stream data to the driver. The system might be in an undefined state.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470078:AV-002: pauseDecode - PausePUSH error: <status>. 

Explanation    The driver interface failed to enter into pause mode as requested. The system might be in an undefined state.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470079:AV-002: resumeDecode - PlayPUSH error: <status>. 

Explanation    The driver interface failed to enter into play mode as requested. The system might be in an undefined state.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470080:AV-002: stopDecode - EOS PushBuffer error: <status>. 

Explanation    An error occurred when attempting to push an End of Stream indication to the driver. The system might be in an undefined state.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470081:AV-002: stopDecode - StopPUSH error: <status>. 

Explanation    The driver interface failed to enter into stop mode as requested. The system might be in an undefined state.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470082:CARIBBEAN called RMPanic with status=<reason>.

Explanation    The driver interface callback indicated a panic condition. The system might be in an undefined state.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-4-470083:AV-002: callbackRMF - Unexpected message : <msg_id> 
val : <msg_parm>. 

Explanation    An unexpected message has been received from the driver interface. The system might be in an undefined state.

Recommended Action    This message is generally harmless but might indicate a software issue. Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470084:AV-002: callbackRMF - StopPush error: <errno>. 

Explanation    The driver interface callback failed to enter into stop mode as requested. The system might be in an undefined state.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470085:AV-002: Unable to get OSD/RUA handle: <num>. 

Explanation    The driver interface failed to get the OSD/RUA control handle. OSD does not work.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-3-470086:AV-002: OSD is not initialized. 

Explanation    The driver interface failed to initialize OSD. OSD does not work.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-4-470087:AV-002: OSD is already setup. 

Explanation    The TV-out server tried to set up OSD when it is already on.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-4-470088:AV-002: Unable to setup OSD: Bitmap processing 
failed. 

Explanation    The driver interface failed to process the BMP file assigned as the OSD. The overlay does not display.

Recommended Action    See the Cisco Internet Streamer CDS 2.4 Software Configuration Guide for restrictions on the BMP file that can be used for OSD. Contact Cisco TAC if the BMP file is within the specifications but still does not work.

Error Message    SE-TVOUT-4-470089:AV-002: Only 4 bpp and 8bpp BMP files are supported 
for OSD. 

Explanation    OSD works only with 4-bpp and 8-bpp BMP files. It uses a different BMP file.

Recommended Action    See documentation for restrictions on the BMP file that can be used for OSD. Contact Cisco TAC if the BMP file is within the specifications but still does not work.

Error Message    SE-TVOUT-4-470090:AV-002: Unable to process overlay image: Bitmap size 
<num> is greater than allowed. 

Explanation    The driver interface failed to process the BMP file assigned as the OSD. The overlay is not displayed.

Recommended Action    See documentation for restrictions on the BMP file that can be used for OSD. Contact Cisco TAC if the BMP file is within the specifications but still does not work.

Error Message    SE-TVOUT-4-470091:AV-002: Unable to set the OSD Area dimensions (rc = 
<num>). 

Explanation    The driver interface failed to set the OSD area dimensions. The overlay does not display.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-4-470092:AV-002: Unable to turn on OSD after setting OSD area 
dimensions. 

Explanation    The driver interface failed to turn on OSD. The overlay does not display.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-4-470093:AV-002: Unable to handle placement of OSD (rc = 
<num>). 

Explanation    The driver interface failed to place the OSD at the correct start location.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-4-470094:AV-002: Unable to mmap OSD buffer: <msg>. 

Explanation    The OSD driver interface failed with an internal error. The overlay is not displayed.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-4-470095:AV-002: Unable to set OSD color palette entry. 

Explanation    The driver interface failed to set the color palette with an internal error. The overlay does not display.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-4-470096:Overlay with id <num> is not defined in the playlist. 

Explanation    A media file had an undefined overlay. This is an internal error. The overlay does not display.

Recommended Action    Re-enable the TV-out service. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-4-470097:AV-002: OSD positioned completely off screen: 
x=<num>, y=<num>, w=<num>, h=<num>. 

Explanation    The driver interface failed to place the OSD within the dimensions displayed by the screen. The overlay does not display.

Recommended Action    Change the Height Offset and/or Width Offset to move the OSD within the dimensions displayed by the screen.

Error Message    SE-TVOUT-3-470098:Failed to record the determined TV-out hardware: 
[error]. 

Explanation    An error occurred recording data about the type of TV-out hardware installed on the device.

Recommended Action    Reload the device. Contact Cisco TAC if this problem persists.

Error Message    SE-TVOUT-6-470099:[tvout enable processing messages]. 

Explanation    Class of informational messages regarding the processing of the tvout enable config command.

Recommended Action    No action is required.

Error Message    SE-TVOUT-3-470100:ver_tvout: Error encountered [stopping | starting] 
TV-out service. 

Explanation    An error occurred when interacting with the node manager to either start or stop the TV-out service.

Recommended Action    Disable or enable the TV-out service again. If this error persists, reload the device. Contact Cisco TAC if this problem persists.

UNILOG Messages

Error Message    SE-UNILOG-2-650001:failed to bind data server to. 

Explanation    Failed to bind to the data server.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-UNILOG-2-650002:logger daemon to exit! 

Explanation    Unable to initialize data server connection; logger daemon to exit.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-UNILOG-2-650003:Cannot open logd.conf file, exiting! 

Explanation    Unable to open logd.conf file; logger daemon to exit.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-UNILOG-2-650004:Exiting, failed to register notifier on item. 

Explanation    Failed to register notifier on item; logger daemon to exit.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-UNILOG-2-650005:log dir is not a directory. 

Explanation    The log directory is not a directory; logger daemon to exit.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-UNILOG-3-650006:Error: log directory cannot be created. 

Explanation    The log directory cannot be created.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-UNILOG-3-650007:Error: log directory cannot be accessed.

Explanation    The log directory cannot be accessed.

Recommended Action    Contact Cisco TAC if this message appears frequently.

Error Message    SE-UNILOG-3-650008:cannot start translog service.

Explanation    The translog service cannot be started.

Recommended Action    Contact Cisco TAC if this message appears frequently.

UNKNOWN Messages

Error Message    SE-UNKNOWN-0/1/2/3/4/5/6-819999:[Description]. 

Explanation    These messages are generated by various modules that have not been properly formatted and documented yet.

Recommended Action    If high priority error messages frequently occur, contact Cisco TAC.

UPG Messages

Error Message    SE-UPG-3-300001:<text>.

Explanation    Invalid command-line parameters were passed. Another program in CDS has incorrectly invoked this software.

Recommended Action    Reboot and retry the installation. If this error prevents you from installing an image, contact Cisco TAC.

Error Message    SE-UPG-3-300002:<text>.

Explanation    An invalid component number was specified on the command line. Most likely this means that another program in CDS incorrectly invoked this program.

Recommended Action    Reboot and retry the installation. If this error prevents you from installing an image, contact Cisco TAC.

Error Message    SE-UPG-3-300003:<text>.

Explanation    An invalid component number was specified on the command line. Most likely this means that another program in CDS incorrectly invoked this program.

Recommended Action    Reboot and retry the installation. If this error prevents you from installing an image, contact Cisco TAC.

Error Message    SE-UPG-3-300004:<text>.

Explanation    A program was requested to write a component file to a terminal. The program output should be directed to a file. Another program in CDS has incorrectly invoked this program.

Recommended Action    Reboot and retry the installation. If this error prevents you from installing an image, contact Cisco TAC.

Error Message    SE-UPG-3-300005:<text>.

Explanation    Internal error processing command-line arguments.

Recommended Action    Reboot and retry the installation. If this error prevents you from installing an image, contact Cisco TAC.

Error Message    SE-UPG-3-300006:<text>.

Explanation    Unable to open specified image file.

Recommended Action    Ensure the path to the image file is correct. If automated software is generating this message, it might indicate a bug or an operational problem on the device. Contact Cisco TAC.

Error Message    SE-UPG-3-300007:<text>.

Explanation    Unable to get file status for a specified input file.

Recommended Action    This is an internal problem on the device. Contact Cisco TAC.

Error Message    SE-UPG-3-300008:<text>.

Explanation    The input file was 0 bytes.

Recommended Action    Ensure the input .bin file is a proper CDS image and is not truncated or corrupt. Check the MD5 checksum. If necessary, download a new image file from Cisco.com.

Error Message    SE-UPG-2-300009:<text>.

Explanation    Received an unexpected error while reading an image file header (see message the text for details).

Recommended Action    Contact Cisco TAC.

Error Message    SE-UPG-3-300010:<text>.

Explanation    Received an unexpected end-of-file error while reading an image file header.

Recommended Action    Ensure the input .bin file is a proper CDS image and is not truncated or corrupt. Check the MD5 checksum. If necessary, download a new image file from Cisco.com.

Error Message    SE-UPG-3-300011:<text>.

Explanation    There is an incomplete header on the image file (missing MANIFEST-CHECKSUM line).

Recommended Action    Ensure the input .bin file is a proper CDS image and is not truncated or corrupt. Check the MD5 checksum. If necessary, download a new image file from Cisco.com.

Error Message    SE-UPG-3-300012:<text>.

Explanation    There is an incomplete header on the image file (missing RUBY-MANIFEST-VERSION line).

Recommended Action    Ensure the input .bin file is a proper CDS image and is not truncated or corrupt. Check the MD5 checksum. If necessary, download a new image file from Cisco.com.

Error Message    SE-UPG-3-300013:<text>.

Explanation    The image file is not compatible with this software release.

Recommended Action    If attempting to downgrade, use the special downgrade image to downgrade.

Error Message    SE-UPG-3-300014:<text>.

Explanation    The image file header contains invalid characters in a checksum string.

Recommended Action    Ensure the input .bin file is a proper CDS image and is not truncated or corrupt. Check the MD5 checksum. If necessary, download a new image file from Cisco.com.

Error Message    SE-UPG-3-300015:<text>.

Explanation    The image file header contains a checksum string of incorrect length.

Recommended Action    Ensure the input .bin file is a proper CDS image and is not truncated or corrupt. Check the MD5 checksum. If necessary, download a new image file from Cisco.com.

Error Message    SE-UPG-3-300016:<text>.

Explanation    The page file header checksum was bad (possibly a corrupt or edited file).

Recommended Action    Ensure the input .bin file is a proper CDS image and is not truncated or corrupt. Check the MD5 checksum. If necessary, download a new image file from Cisco.com.

Error Message    SE-UPG-2-300017:<text>.

Explanation    Failed to allocate memory.

Recommended Action    Retry the installation. If necessary, reboot the system and retry the installation. Contact Cisco TAC if this problem persists.

Error Message    SE-UPG-3-300018:<text>.

Explanation    The image file header has a syntax error.

Recommended Action    Ensure the input .bin file is a proper CDS image and is not truncated or corrupt. Check the MD5 checksum. If necessary, download a new image file from Cisco.com.

Error Message    SE-UPG-3-300019:<text>.

Explanation    The image file header contains a checksum string that contains an invalid character.

Recommended Action    Ensure the input .bin file is a proper CDS image and is not truncated or corrupt. Check the MD5 checksum. If necessary, download a new image file from Cisco.com.

Error Message    SE-UPG-3-300020:<text>.

Explanation    The image file header contains a checksum string of length not equal to 32 characters.

Recommended Action    Ensure the input .bin file is a proper CDS image and is not truncated or corrupt. Check the MD5 checksum. If necessary, download a new image file from Cisco.com.

Error Message    SE-UPG-3-300021:<text>.

Explanation    A component of the image file failed to match its checksum in the image header.

Recommended Action    Ensure the input .bin file is a proper CDS image and is not truncated or corrupt. Check the MD5 checksum. If necessary, download a new image file from Cisco.com.

Error Message    SE-UPG-2-300022:<text>.

Explanation    Failed to seek to desired file offset on input file.

Recommended Action    This error indicates an internal error in the logic of the program. Contact Cisco TAC.

Error Message    SE-UPG-2-300023:<text>.

Explanation    An error occured while reading an image component. This might be due to transient network failure (interrupted download). Alternatively, it might indicate a serious operational problem on the device, such as a failed disk drive.

Recommended Action    Retry the installation. Contact Cisco TAC if this problem persists.

Error Message    SE-UPG-3-300024:<text>.

Explanation    Reached end of file while reading an image component.

Recommended Action    Ensure that the image file is not truncated or otherwise corrupted. You might need to obtain a new image file from Cisco.com. Contact Cisco TAC if this problem persists.

Error Message    SE-UPG-2-300025:<text>.

Explanation    Failed to write component data to disk (see the message text for cause). This could be because an internal error caused a system-use file system to fill up. Alternatively, the disk drive with system-use file systems (typically disk00) might be failing.

Recommended Action    Contact Cisco TAC and provide syslog messages logged by default to the file /local1/syslog.txt.

Error Message    SE-UPG-2-300026:<text>.

Explanation    Failed to write data to component output file.

Recommended Action    Contact Cisco TAC if this problem persists.

Error Message    SE-UPG-2-300027:<text>.

Explanation    Failed to open an existing component file on the disk. More information about this failure is in the message text. This could be a hardware problem, such as a failed disk drive.

Recommended Action    Check the disk drives and cables. Contact Cisco TAC if this problem persists.

Error Message    SE-UPG-2-300028:<text>.

Explanation    Failed to create a temporary lock file. More information about this failure is in the message text.

Recommended Action    Contact Cisco TAC.

Error Message    SE-UPG-3-300029:<text>.

Explanation    Failed to lock the lock file. This means another upgrade is in progress.

Recommended Action    Wait for the other upgrade to finish. Contact Cisco TAC if this problem persists.

Error Message    SE-UPG-2-300030:<text>.

Explanation    Failed to read a directory listing to examine existing components. More information about this failure is in the message text.

Recommended Action    Contact Cisco TAC.

Error Message    SE-UPG-2-300031:<text>.

Explanation    Failed to open an existing component file on the disk. More information about this failure is in the message text. This could be a hardware problem, such as a failed disk drive.

Recommended Action    Check the disk drives and cables. Contact Cisco TAC if this problem persists.

Error Message    SE-UPG-2-300032:<text>.

Explanation    Failed to read an existing component file on disk. More information about this failure is in the message text. This could be a hardware problem, such as a failed disk drive.

Recommended Action    Check the disk drives and cables. Contact Cisco TAC if this problem persists.

Error Message    SE-UPG-2-300033:<text>.

Explanation    Failed to create the manifest file on the disk. More information about this failure is in the message text. This could be a hardware problem, such as a failed disk drive.

Recommended Action    Check the disk drives and cables. Contact Cisco TAC if this problem persists.

Error Message    SE-UPG-2-300034:<text>.

Explanation    Failed to write to the manifest file on the disk. More information about this failure is in the message text. This could be a hardware problem, such as failed disk drive. Check the disk drives and cables.

Recommended Action    Check the disk drives and cables. Contact Cisco TAC if this problem persists.

Error Message    SE-UPG-2-300035:<text>.

Explanation    The image that is being installed is a partial image and is not compatible with the software already installed on the device.

Recommended Action    Ensure that the image you are trying to install is the proper image.

Error Message    SE-UPG-2-300036:<text>.

Explanation    At boot time, the program "install-to-sw" failed to exit. More information is available in the boot log messages in the syslog file.

Recommended Action    Contact Cisco TAC.

Error Message    SE-UPG-2-300038:<text>.

Explanation    Failed to open file /etc/MODEL. More information is in the message text.

Recommended Action    Contact Cisco TAC.

Error Message    SE-UPG-2-300039:<text>.

Explanation    The image to be installed is not compatible with the current device model type.

Recommended Action    Ensure that the image you are installing is the desired image. Contact Cisco TAC if this problem persists.

Error Message    SE-UPG-2-300140:<text>.

Explanation    The installer script failed to exit. It probably performed an illegal operation and was terminated by the system.

Recommended Action    Contact Cisco TAC.

Error Message    SE-UPG-2-300041:<text>.

Explanation    Failed to create a temporary file to hold the pre-install script. This error indicates an operational error on the device. More information about this failure is in the message text.

Recommended Action    Reboot and retry the installation. Contact Cisco TAC if this problem persists.

Error Message    SE-UPG-2-300042:<text>.

Explanation    Failed to change working directory to /swstore (an internal directory used for storing image file components). More information about this failure is in the message text.

Recommended Action    Execute the show disk details command and verify that the system-use disk space shows up on the first disk drive (typically disk00). If nothing shows up, you might need to execute the disk recover command and reinstall. Contact Cisco TAC if this problem persists.

Error Message    SE-UPG-2-300043:<text>.

Explanation    Failed to create the flag file /swstore/GOOD. More information about this failure is in the message text.

Recommended Action    Contact Cisco TAC.

Error Message    SE-UPG-2-300044:<text>.

Explanation    Checksum failed for an image file after it was written to disk. More information about this failure is in the message text. This could be a hardware problem, such as a failed disk drive.

Recommended Action    Check the disk drives and cables. Contact Cisco TAC if this problem persists.

Error Message    SE-UPG-2-300045:<text>.

Explanation    fsync/close failed for an image file after it was written to disk. More information about this failure is in the message text. This could be a hardware problem, such as a failed disk drive. Check the disk drives and cables.

Recommended Action    Check the disk drives and cables. Contact Cisco TAC if this problem persists.

Error Message    SE-UPG-2-300090:<text>.

Explanation    The pre-install script failed to exit. It probably performed an illegal operation and was terminated by the system.

Recommended Action    Contact Cisco TAC.

Error Message    SE-UPG-3-300091:<text>.

Explanation    The pre-install script found an invalid CDSM IP address specified.

Recommended Action    Check the metadata file or other CDSM IP address source and ensure the address is syntactically correct.

Error Message    SE-UPG-3-300092:<text>.

Explanation    The pre-install script observed that system-use file systems were not mounted.

Recommended Action    Ensure that the disk configuration is correct. Contact Cisco TAC if this problem persists.

Error Message    SE-UPG-3-300093:<text>.

Explanation    The pre-install script could not detect any SYSFS file systems on the device.

Recommended Action    Ensure that the device has non-zero disk space allocated to SYSFS. If necessary, execute the disk config command, specifying non-zero SYSFS along with your other desired file system type amounts, and reboot to have the SYSFS file systems created.

Error Message    SE-UPG-3-300094:<text>.

Explanation    The device-mode command has been used to make this device operate in a non-SE mode.

Recommended Action    Remove the device-mode configuration before downgrading.

Error Message    SE-UPG-3-300095:<text>.

Explanation    The pre-install script prompted the user on the terminal to continue, and the user decided to exit the installation.

Recommended Action    Proceed with the installation when ready.

Error Message    SE-UPG-3-300096:<text>.

Explanation    The pre-install script could not understand the internal file system layout on the disk drive with system-use file systems (typically disk00).

Recommended Action    Contact Cisco TAC.

Error Message    SE-UPG-3-300097:<text>.

Explanation    An internal error occurred with the pre-install script.

Recommended Action    Contact Cisco TAC.

Error Message    SE-UPG-3-300098:<text>.

Explanation    The wrong product is being installed.

Recommended Action    Download the correct CDS or Wide Area File Server (WAFS) image.

Error Message    SE-UPG-3-300099:<text>.

Explanation    The network module with WAFS requires at least an 80GB-disk.

Recommended Action    Check the disk size on the module.

Error Message    SE-UPG-3-300100:<text>.

Explanation    This specific disk model is not supported by the network module.

Recommended Action    Proceed with the installation when ready.

Error Message    SE-UPG-3-300101:<text>.

Explanation    The network module running WAFS requires 512 MB of RAM.