Cisco ECDS 2.5 Alarms and Error Messages Guide · † Audience, page vi ... for use by the MDEs....

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706 USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 527-0883

Cisco ECDS 2.5 Alarms and Error Messages GuideMarch 2011

Text Part Number: OL-24530-01

http://www.cisco.com

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The following information is for FCC compliance of Class A devices: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense.

The following information is for FCC compliance of Class B devices: The equipment described in this manual generates and may radiate radio-frequency energy. If it is not installed in accordance with Cisco’s installation instructions, it may cause interference with radio and television reception. This equipment has been tested and found to comply with the limits for a Class B digital device in accordance with the specifications in part 15 of the FCC rules. These specifications are designed to provide reasonable protection against such interference in a residential installation. However, there is no guarantee that interference will not occur in a particular installation.

Modifying the equipment without Cisco’s written authorization may result in the equipment no longer complying with FCC requirements for Class A or Class B digital devices. In that event, your right to use the equipment may be limited by FCC regulations, and you may be required to correct any interference to radio or television communications at your own expense.

You can determine whether your equipment is causing interference by turning it off. If the interference stops, it was probably caused by the Cisco equipment or one of its peripheral devices. If the equipment causes interference to radio or television reception, try to correct the interference by using one or more of the following measures:

• Turn the television or radio antenna until the interference stops.

• Move the equipment to one side or the other of the television or radio.

• Move the equipment farther away from the television or radio.

• Plug the equipment into an outlet that is on a different circuit from the television or radio. (That is, make certain the equipment and the television or radio are on circuits controlled by different circuit breakers or fuses.)

Modifications to this product not authorized by Cisco Systems, Inc. could void the FCC approval and negate your authority to operate the product.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)

Cisco ECDS 2.5 Alarms and Error Messages Guide© 2011 Cisco Systems, Inc. All rights reserved.

http://www.cisco.com/go/trademarks

iiiCisco ECDS 2.5 Alarms and Error Messages Guide

OL-24530-01

C O N T E N T S

Preface v

Document Revision History v

Document Organization v

Audience vi

Objective vi

Conventions vi

Related Documentation vii

Obtaining Documentation and Submitting a Service Request vii

C H A P T E R 1 Alarm and System Message Overview 1-1

System Message Structure 1-1

System Error Message Example 1-4

Searching for System Error Messages 1-4

Alarm Structure 1-5

C H A P T E R 2 Alarms 2-1

Severity Level 2-1Critical Alarms 2-1Major Alarms 2-3Minor Alarms 2-6

SNMP Alarm Traps 2-10

C H A P T E R 3 Error Messages and Recovery Procedures 3-1

ACL Messages 3-2

ACQ Messages 3-4

AUTH Messages 3-7

BANDWD Messages 3-7

CDNFS Messages 3-11

CLEAN-AD Messages 3-13

CLI Messages 3-14

CMS Messages 3-25

COMMONEDM Messages 3-68

Contents

ivCisco ECDS 2.5 Alarms and Error Messages Guide

OL-24530-01

DHCP Messages 3-69

DISK Messages 3-70

DIST Messages 3-76

DS Messages 3-81

FFS Messages 3-84

FMS Messages 3-84

HTTP Messages 3-85

ICAP Messages 3-86

LIBCMN Messages 3-86

LOGGING Messages 3-90

MS Messages 3-90

NHM Messages 3-92

NODEMGR Messages 3-92

NTP Messages 3-108

PAM Messages 3-109

PARSER Messages 3-114

POSTGRE Messages 3-120

RPC Messages 3-121

RTSP Messages 3-122

RTSPG Messages 3-123

RULES Messages 3-125

SCHED Messages 3-132

SERMON Messages 3-133

SNMP Messages 3-133

SR Messages 3-136

SSHD Messages 3-141

SSRV Messages 3-142

STATS Messages 3-143

STDBY Messages 3-146

SYS Messages 3-147

SYSMON Messages 3-148

SYSUTL Messages 3-150

TFTP Messages 3-151

UNILOG Messages 3-154

UPG Messages 3-155

Contents

vCisco ECDS 2.5 Alarms and Error Messages Guide

OL-24530-01

URLFLT Messages 3-166

WMT Messages 3-166

XXX Messages 3-172

A P P E N D I X A List of Abbreviations and Acronyms A-1

Contents

viCisco ECDS 2.5 Alarms and Error Messages Guide

OL-24530-01

vCisco ECDS 2.5 Alarms and Error Messages Guide

OL-24530-01

Preface

This preface describes the objectives and organization of this guide and contains the following sections:

• Document Revision History, page v

• Document Organization, page v

• Audience, page vi

• Objective, page vi

• Conventions, page vi

• Related Documentation, page vii

• Obtaining Documentation and Submitting a Service Request, page vii

Document Revision HistoryThe Document Revision History table below records technical changes to this document.

Document Organization

Date Change Summary

February 2011 This is the first version of this document.

Chapter Description

Chapter 1, “Alarm and System Message Overview”

Describes the error message and alarm structure and provides sample messages and alarms.

Chapter 2, “Alarms” Lists the Cisco Enterprise CDS Release 2.5 alarms and provides explanations and recommended actions.

Chapter 3, “Error Messages and Recovery Procedures”

Lists the Cisco Enterprise CDS Release 2.5 error messages and provides explanations and recommended actions.

Appendix A, “List of Abbreviations and Acronyms”

Lists the abbreviations and acronyms used in this guide and provides their expansions.

viCisco ECDS 2.5 Alarms and Error Messages Guide

OL-24530-01

Preface

AudienceThis publication is designed for the installer and user with a working knowledge of the Cisco Enterprise Content Delivery System (ECDS) Release 2.5 software. Users of this publication might also include network administrators and other people responsible for setting up and maintaining the Media Delivery Engines (MDEs).

ObjectiveThis guide describes the Cisco Enterprise CDS Release 2.5 alarms and system error messages that you might encounter.

This guide does not describe how to install your ECDS or how to configure software features on your system. It also does not provide detailed information about commands that have been created or changed for use by the MDEs. For hardware installation information, see the hardware installation guide for your MDE. For software information, see the software configuration guide and the command reference for this release, which are listed in the “Related Documentation” section on page vii.

ConventionsThis guide uses basic conventions to represent text and table information.

Convention Description

boldface font Commands, keywords, and button names are in boldface.

italic font Variables for which you supply values are in italics. Directory names and filenames are also in italics.

screen font Terminal sessions and information the system displays are in screen font.

boldface screen font Information you must enter is in boldface screen font.

italic screen font Variables you enter are in italic screen font.

^ The symbol ^ represents the key labeled Control. For example, the key combination ^D in a screen display means hold down the Control key while you press the D key.

string Defined as a nonquoted set of characters.

For example, when setting a community string for SNMP to “public,” do not use quotation marks around the string, or the string will include the quotation marks.

vertical bars ( | ) Vertical bars separate alternative, mutually exclusive, elements.

{ } Elements in braces are required elements.

[ ] Elements in square brackets are optional.

{x | y | z} Required keywords are grouped in braces and separated by vertical bars.

[x | y | z] Optional keywords are grouped in brackets and separated by vertical bars.

[{ }] Braces within square brackets indicate a required choice within an optional element.

viiCisco ECDS 2.5 Alarms and Error Messages Guide

OL-24530-01

Preface

Note Means reader take note. Notes contain helpful suggestions or references to materials not contained in the manual.

Related DocumentationTo see the complete set of information about the Enterprise Content Delivery System, see Documentation for the Cisco Enterprise Content Delivery System on Cisco.com:

http://www.cisco.com/en/US/docs/video/ecds/documentation.html

Obtaining Documentation and Submitting a Service RequestFor information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.htmlhttp://www.cisco.com/en/US/docs/video/ecds/documentation.html

viiiCisco ECDS 2.5 Alarms and Error Messages Guide

OL-24530-01

Preface

C H A P T E R

1-1Cisco ECDS 2.5 Alarms and Error Messages Guide

OL-24530-01

1Alarm and System Message Overview

This guide lists and describes the error messages for the Cisco Enterprise Content Delivery System (ECDS) Release 2.5. The system software sends these error messages to the console, local disk, and logging server on another system. Not all error messages indicate problems with your system. Some messages are purely informational, whereas others may help diagnose problems with communications lines, internal hardware, or the system software.

This chapter contains the following sections:

• System Message Structure, page 1-1

• System Error Message Example, page 1-4

• Searching for System Error Messages, page 1-4

• Alarm Structure, page 1-5

System Message Structure System error messages are structured as follows:

FACILITY-SEVERITY-MNEMONIC: Message text

For example:

SE-XXX-7-100000:

ECDS error messages also indicate where the system condition occurred. These messages are structured as follows:

FACILITY-SOURCE-SEVERITY-MNEMONIC: Message text

For example:

SE-ACQ-2-100010 Failed to acquire start-url

Facility Code

The facility code consists of two or more uppercase letters that indicate the facility to which the message refers. A facility can be a hardware device, a protocol, or a module of the system software.

In the ECDS context, the facility code is SE and refers to Service Engine.

Source indicates the location of the condition. Examples of source are ACQ, which indicates that the condition occurred in the Acquirer component, or SYSMON, which indicates that the condition occurred in the System Monitor component. Table 1-1 lists the source codes in ECDS.


OL-24530-01

Chapter 1 Alarm and System Message OverviewSystem Message Structure

Table 1-1 ECDS Source Codes

Code Component Description

ACL Access control list

ACQ Acquirer

AUTH Authentication

BANDWD Bandwidth

CDNFS Content Delivery Network File System

CLEAN-AD Cleanup AD

CLI Command Line Interface

CMS Content Management Service

COMMONEDM Common EDM

DHCP Dynamic Host Configuration Protocol

DISK Disk

DIST Distribution

DS Data Server

FFS Firewall Feature Set

FMS Flash Media Streaming

HTTP Hypertext Transfer Protocol

ICAP Interactive Communicating Application Protocol daemon

LIBCMN Common Library

LOGGING Logging

MS Movie Streamer

NHM Node Health Manager

NODEMGR Node Manager

NTP Network Time Protocol

PAM Port to Application Mapping

PARSER Parser

POSTGRE Postgres server

RPC Remote Proxy Caching (UniRPC)

RTSP Real-Time Streaming Protocol

RTSPG Real-Time Streaming Protocol Gateway

RULES URL filtering rules

SCHED Scheduler

SERMON Service Monitor

SNMP Simple Network Management Protocol

SR Service Router

SSHD Secure Shell


OL-24530-01

Chapter 1 Alarm and System Message OverviewSystem Message Structure

Severity Level

The severity level is a single-digit code from 0 to 7 that reflects the severity of the condition. The lower the number, the more serious the situation. Table 1-2 lists the message severity levels.

Mnemonic Code

The mnemonic code uniquely identifies the error message.

Message Text

Message text is a text string that describes the condition. The text string sometimes contains detailed information about the event, including terminal port numbers, network addresses, or addresses that correspond to locations in the system memory address space. Because variable fields change from message to message, they are represented here by short strings enclosed in brackets ([ ]). The variables give you more information about the system condition. A decimal number, for example, is represented as [dec]. Table 1-3 lists a sample of the variable fields that are used in this document.

SSRV Streaming Server

STATS Statistics Provider Application

STDBY Standby

SYS Kernel

SYSMON System monitor

SYSUTL System utility

TFTP Trivial File Transfer Protocol

UNILOG Unified log

UPG Upgrade

URLFLT URL filter

WMT Windows Media Technologies

XXX General Debugging message

Table 1-1 ECDS Source Codes (continued)

Code Component Description

Table 1-2 Message Severity Level

Severity Level Description

0 (emergency) System unusable

1 (alert) Immediate action required

2 (critical) Critical condition

3 (error) Error condition

4 (warning) Warning condition

5 (notification) Normal but significant condition

6 (informational) Informational message only

7 (debugging) Message that appears during debugging only


OL-24530-01

Chapter 1 Alarm and System Message OverviewSystem Error Message Example

System Error Message ExampleThe following is an example of a system error message:

SE-ACQ-2-100010 Failed to acquire start-url

In this system error message example:

• SE is the facility code.

• ACQ is the source code.

• 2 is the severity level.

• 100010 is the mnemonic code.

• Failed to acquire start-url is the message text.

Searching for System Error MessagesIf you search for the explanation and recommended action of a message that contains a source code, remove the source code from the text first, and then search for the message in the documentation. For example, instead of searching the documentation for the message SE-ACQ-2-100010, remove the source code and search for the message SE-2-100010.

When searching for a message in the Error Message Decoder (EMD), you should also remove the source code.

The EMD is located at this URL:

http://www.cisco.com/pcgi-bin/Support/Errordecoder/index.cgi

Table 1-3 Representation of Variable Fields in Messages

Representation Type of Information

[chars] or [char] Character string

[dec] Decimal

[failure description] The type and nature of the system failure

[x] or [y] Characters

[error] Error code

[module] Name of the module

[procedure] Name of the procedure

[additional information] Additional information about the error message

[cli] Command entered at the command-line interface

[err] Error description

http://www.cisco.com/pcgi-bin/Support/Errordecoder/index.cgi


OL-24530-01

Chapter 1 Alarm and System Message OverviewAlarm Structure

Alarm StructureCisco ECDS alarms are structured as follows:

SOURCE-MNEMONIC CODE: Alarm text

Example:

Alarm 330001 (svcdisabled) -service name- service has been disabled.

Mnemonic Code

A unique code for identifying the alarm.

Alarm Text

A brief description of the alarm.


OL-24530-01

Chapter 1 Alarm and System Message OverviewAlarm Structure

C H A P T E R


OL-24530-01

2Alarms

This chapter lists the Cisco Enterprise CDS Release 2.5 alarms. Each alarm is followed by an explanation and recommended action. The chapter also defines the six generic SNMP alarm traps.

Severity LevelAn alarm can have one of the following three severity levels: critical, major, or minor:

• Critical alarm indicates that a critical problem exists somewhere in the network. Critical alarms cause failover and should be cleared immediately.

• Major alarm indicates that a serious problem exists that is disrupting service. Major alarms differ from critical alarms in that they do not cause failovers. Major alarms should also be cleared immediately.

• Minor alarms should be noted and cleared as soon as possible.

Critical AlarmsAlarm 330001 (svcdisabled) - service name - service has been disabled.

Explanation The Node Manager tried restarting the specified service but the service kept restarting. The number of restarts has exceeded an internal limit and the service has been disabled.

Recommended Action The device may have to be reloaded for the service to be re-enabled.

Alarm 330002 (servicedead) - service name - service died.

Explanation A critical service has died. Attempts are made to restart this service, but the device may run in a degraded state.

Recommended Action The device could reboot itself to avoid instability. Examine the syslog for messages relating to the cause of service death.

Alarm 335000 (alarm_overload) Alarm Overload State has been entered.

Explanation The Node Health Manager issues this alarm to indicate that the device is raising alarms at a rate that exceeds the overload threshold.

Recommended Action Access the device and determine what services are raising the alarms. Take corrective action to resolve the individual services’ issues.


OL-24530-01

Chapter 2 AlarmsSeverity Level

Alarm 335001 (keepalive) Keepalive failure for - application name - Timeout = n seconds.

Explanation An application is not being responsive, indicating it may not be properly operating.

Recommended Action Access the device and determine the state of the specific application.

Alarm 335003 (test1) NHM Alarm Testing [string].

Explanation This alarm is used for testing the Node Health Manager.

Recommended Action None. This alarm should never occur during normal operation.







Alarm 445002 (disk_smartfailcrit) An SE disk has severe early-prediction failure which requires immediate action.

Explanation The SYSMON issues this alarm to indicate that one of the disks attached to the SE has severe early-prediction failure (for example, the disk has failed SMART self-check).

Recommended Action Back up data immediately on the disk to prevent data loss, and replace the disk after it is marked bad by the SE.

Alarm 445005 (disk_softraidcrit) A SoftRAID device has malfunctioned and requires immediate action.

Explanation The SYSMON issues this alarm to indicate that a SoftRAID device has malfunctioned (for example, both component disks of a RAID-1 array have become inaccessible or faulty).

Recommended Action Replace the disks and restore the data from backup storage, or remanufacturing and reload the disks.

Alarm 700004 (device_offline_alarm) Device is offline. Re-register device to cdsm is strongly recommended.

Explanation The device is offline.

Recommended Action Check the device or network status. It may be necessary to re-register the device to the CDSM.

Alarm 700005(rep_status_failed) Replication status failed.

Explanation Replication status has failed.

Recommended Action Check all SEs assigned to the delivery service.


OL-24530-01


Major AlarmsAlarm 100002 (ManifestFetchFail) Fail to fetch manifest file for Delivery Service.

Explanation There is a problem fetching the manifest file for this delivery service.

Recommended Action Log in to the CA, execute the show stat acq err command to check the problem, and resolve the problem.

Alarm 100003 (ManifestParseFail) Fail to parse manifest file for Delivery Service.

Explanation There are some syntax errors in the manifest file for this delivery service.

Recommended Action Log in to the CA, execute the show stat acq err command to check the problem, and resolve the problem.

Alarm 100005 (ExceedQuota) Total content size could not fit into the Delivery Service disk quota.

Explanation The total content size acquired for this delivery service is larger than allowed from the delivery service disk quota.

Recommended Action Either remove some contents from the manifest file, or increase the delivery service disk quota.

Alarm 100006 (CrawlStartUrlFail) The start-url for a crawl job in the Delivery Service failed.

Explanation There is a problem fetching the start URL of a crawl job in this delivery service.

Recommended Action Log in to the CA, execute the show status acquirer error command to check the problem, and resolve the problem.

Alarm 100007 (ContentFail) There are some contents that failed to be acquired.

Explanation There are some contents that failed to be acquired.


Alarm 213501 (svcnomcastenable) Alarm multicast is disabled although the SE is a multicast sender and receiver, or it is subscribed to a multicast Delivery Service.

Explanation The unicast data receiver issues this alarm to indicate that the device does not have multicast service enabled, although it is expected to be involved in multicast distribution.

Recommended Action Enable the multicast license and service on the device.


Explanation The node manager found the specified service to be dead. Attempts are made to restart this service.

Recommended Action Examine the syslog for messages relating to the cause of service death. The alarm is cleared if the service stays alive and does not restart soon.

Alarm 335002 (test) NHM Alarm Testing [string].




OL-24530-01








Alarm 445001 (core_dump) A User Core file or Kernel Crash dump has been generated.

Explanation The SYSMON issues this alarm to indicate that one or more of the software modules or the kernel has generated core files.

Recommended Action Access the device and check the directory /local1/core_dir, or /local1/crash, retrieve the core file through FTP, and contact Cisco Technical Assistance Center (TAC).

Alarm 445003 (disk_smartfailmajor) An SE disk has early-prediction failure.

Explanation The SYSMON issues this alarm to indicate that one of the disks attached to the SE has early-prediction failure. This alarm indicates the disk could fail in the near future.

Recommended Action Make proper preparations for the incoming disk drive failure, such as making data backups and preparing a replacement disk.

Alarm 520004 (GroupDown) - group - Specified standby group is down.

Explanation None of the member interfaces in the specified standby group could be brought up.

Recommended Action Check the member interfaces configuration and cabling.

Alarm 540002 (linkdown) Network interface is inactive or down.

Explanation The network interface is inactive or down.

Recommended Action Check the cables connected to the network device.

Alarm 550001 (SEKeepalive) SE keepalive timed-out or SE is not reachable.

Explanation Either the SR has not received keepalives from the SE, or the SE is not reachable.

Recommended Action Check the cables connected to the network device and the SE.

Alarm 560001 (threshold) Service monitor Cpu threshold exceeded.

Explanation The Service Monitor CPU threshold has been exceeded.

Recommended Action Check the file /tmp/threshold_exceeded.txt.

Alarm 560002 (threshold) Service monitor memory threshold exceeded.

Explanation The Service Monitor memory threshold has been exceeded.


Alarm 560003 (threshold) Service monitor kernel memory threshold exceeded.


OL-24530-01


Explanation The Service Monitor kernel memory threshold has been exceeded.


Alarm 560004 (threshold) Service monitor NIC threshold exceeded.

Explanation The Service Monitor Network Interface Card (NIC) threshold has been exceeded.


Alarm 560005 (threshold) Service monitor Disk threshold exceeded.

Explanation The Service Monitor disk threshold has been exceeded.


Alarm 560006 (threshold) Service monitor Disk Failure count threshold exceeded.

Explanation The Service Monitor disk failure count threshold has been exceeded.


Alarm 661001 (svclowdisk) Alarm database is running low in disk space in the STATEFS partition.

Explanation The database monitor service issues this alarm to indicate that it is running low in disk space in the STATEFS partition, and therefore content replication service (acquisition and distribution) has been temporarily stopped.

Recommended Action Execute the cms database maintenance command or schedule database maintenance more frequently to reclaim the disk space.

Alarm 700002 (cms_clock_alarm) The device clock is not synchronized with the primary Content Delivery System Manager (CDSM). Enabling NTP on all the devices is strongly recommended.

Explanation If this device is an SE, its clock must be synchronized with the primary CDSM to make replication status, statistics monitoring, and program files work correctly. If this device is a standby CDSM, its clock must be synchronized with the primary CDSM to make the CDSM failover work.

Recommended Action Fix the clock on either this device or the primary CDSM.


OL-24530-01


Minor AlarmsAlarm 100001 (zerobandwidth) specified content acquisition bandwidth is 0.

Explanation The device has been assigned as CA for some delivery services, but its acquisition bandwidth is 0.

Recommended Action On the CDSM devices page, select this device and select Edit and the Select Preposition link on the left of the screen, then change its default bandwidth.

Alarm 100004 (ManifestUpdateFail) Fail to recheck manifest file for Delivery Service.

Explanation There is a problem rechecking the manifest file for this delivery service.


Alarm 100008 (ContentUpdateFail) There are some contents that failed to be rechecked.

Explanation There are some contents that failed to be rechecked.

Recommended Action Log in to the CA, and execute the show status acquirer error command to check the problem, and resolve the problem.

Alarm 100009 (ManifestParseWarning) Fail to parse manifest file for Delivery Service.

Explanation There are some syntax warnings in the manifest file for this delivery service.

Recommended Action Log in to the CA, and execute the show status acquirer error command to display the warnings, and resolve the problem.

Alarm 212500 (svcbwclosed) Alarm Dout bandwidth is set to zero while jobs are scheduled.

Explanation The unicast data sender issued this alarm to indicate that the Dout is scheduled to be zero, but currently the unicast data sender has a job running.

Recommended Action Access the CDSM and determine if the bandwidth values and bandwidth schedules are correctly configured, and verify on the device the effective bandwidth and job statistics.

Alarm 213500 (svcbwclosed) Alarm Din bandwidth is set to zero while jobs are scheduled.

Explanation The unicast data receiver issued this alarm to indicate that the Din is scheduled to be zero, but currently the unicast data receiver has a job scheduled or running.


Alarm 213502 (svcnomcastconnectivity) There is no multicast network connectivity between the multicast sender and this device.

Explanation The unicast data receiver issues this alarm to indicate that the device as multicast receiver cannot receive Pragmatic General Multicast packets from a multicast sender. There is no multicast network connectivity between the multicast sender and this device.

Recommended Action Check and fix the multicast network connectivity between the sender and the receiver.


OL-24530-01


Alarm 213503 (svcunsspaceproblem) There is a UNS problem while replicating and so some NACKs are suppressed.

Explanation The unicast data receiver issues this alarm to indicate that the device as multicast receiver cannot receive files due to a problem with the Unified Name Space (UNS). It stops sending NACKs for the UNS failed files.

Recommended Action Check and fix the UNS-related issues in the multicast receiver SE.

Alarm 213504 (svcnacksuppressed) Alarm that Multicast Receiver has stopped NACKs due to heavy loss.

Explanation The unicast data receiver issues this alarm to indicate that the device as multicast receiver cannot receive multicast files for some considerable time and has stopped sending NACKs for the files.

Recommended Action Check the multicast network for any problems. The sending of NACKs starts after at least one file is successfully received.

Alarm 215003 (svcdevfailover) Alarm backup multicast sender has been activated.

Explanation The backup multicast sender issues this alarm to indicate that it has been activated and either the primary backup sender has a problem, or the primary and backup multicast senders cannot communicate with each other due to possible network connection issues.

Recommended Action Troubleshoot the multicast sender service on the primary multicast sender and check the network connectivity between the primary and backup multicast senders.

Alarm 215500 (svcbwclosed) Alarm Mout bandwidth is set to zero while jobs are scheduled.

Explanation The multicast data sender issues this alarm to indicate that the device has Mout scheduled to be zero, but currently the multicast data sender has a job scheduled or is running.



Explanation The node manager found the specified service to be dead. Attempts are made to restart this service.

Recommended Action Examine the syslog for messages relating to the cause of service death. The alarm is cleared if the service stays alive and does not restart in a short while.







Alarm 400000 (wesvcthresholdexceeded) WebEngine has reached service threshold limits.


OL-24530-01


Explanation The Web Engine service has reached license limits, or the limits were configured with the webengine max-concurrent-sessions command.

Recommended Action Avoid further service requests to this device.

Alarm 445000 (disk_failure) An SE disk has failed.

Explanation The SYSMON issues this alarm to indicate that one of the disks attached to the SE is not responding.

Recommended Action Access the device and execute the show disk details command. If the problem persists, replace the disk.

Alarm 445004 (disk smartfailminor)A SE disk has minor early-prediction failure.

Explanation The SYSMON issues this alarm to indicate that one of the disks attached to the SE has a minor early-prediction failure. It warns that the disk may fail soon.

Recommended Action Monitor the disk for early indications of a errors occurring. If more severe SMART errors occur, or if disk errors occur, take the appropriate action.

Alarm 445006 (SoftRAID_Event) A SoftRAID device has become degraded and requires immediate action.

Explanation The SYSMON issues this alarm to indicate that a SoftRAID device has become degraded (for example, one disk of a RAID-1 array has become inaccessible or faulty).

Recommended Action If the system suspects an inconsistency in the RAID volume, it will initiate a resync to restore the volume’s integrity. Check the RAID status using the show disk raid command to verify whether a disk failure or resync is occurring. For a resync, wait for the sync(s) to complete. For a degraded array, replace the disk.

Alarm 445007(psu_down) A power supply power cable is unplugged or the power supply has failed.

Explanation The System Monitor issues this alarm to indicate that at least one power supply failed or is unplugged.

Recommended Action Check the back of the MDE and locate the power supplies. Verify the power cables are plugged in and replace any failed power supplies.

Alarm 445009 (system_hitemp) System Temperature Warning!

Explanation The System Monitor issues this alarm to indicate that the motherboard sensor reports high temperatures.

Recommended Action Check the temperature of the lab and the airflow inside the MDE.

Alarm 511010 (svcthresholdexceeded) WMT has reached service threshold limits.

Explanation Windows media technologies service has reached license limits, or the limits are configured with the wmt max-concurrent-sessions bandwidth wmt outgoing command.

Recommended Action Avoid further service requests to this device.

Alarm 511011 (fmsthresholdexceeded) FMS has reached service threshold limits.

Explanation FMS service has reached concurrent connection limits.

Recommended Action Avoid further service requests to this device, or contact Cisco Technical Assistance Center for more connection licenses.


OL-24530-01


Alarm 511012 (mssvcthresholdexceeded) Movie Streamer has reached service threshold limits.

Explanation MS service has reach license limits, or the limits are configured.

Recommended Action Avoid further service requests to the device.

Alarm 511013 (encoderfailure) Encoder:/program_IP_Address/encoder_name/encoder_url :failed.

Explanation Encoder is stopped or down or some issues happened.

Recommended Action Check the encoder to make sure it work correctly or try to use other corrected encoders. Run the command “show alarms detail support” can get above information.

Alarm 520001 (LinkDown) -group-ifc-slot-port- Specified interface in the standby group is down.

Explanation The specified interface in the standby group is down. There could have been a link failure on the interface or it may have been shut down on purpose.

Recommended Action Check the configuration and cabling of the specified interface.

Alarm 520002 (RouteDown) -group-ifc-slot-port- Unable to reach the configured default gateway on the specified interface.

Explanation Unable to reach the configured default gateway on the specified interface in the standby group.

Recommended Action Check the network configuration on the specified interface.

Alarm 520003 (MaxError) -group-ifc-slot-port- The specified interface has seen errors exceeding maximum allowable error count.

Explanation The specified interface has seen errors exceeding the maximum allowable error count.

Recommended Action Check the cabling or configuration of the specified interface.

Alarm 540001 (shutdown) Network interface is shutdown.

Explanation The network interface is shut down.

Recommended Action Check the interface configuration.

Alarm 700001 (cms_test_alarm) CMS test alarm with instance value - instance was raised. The title is used in the CDSM GUI.

Explanation This is a test alarm defined and used in CMS code. This alarm is identified by a tuple (340001, instance). This means the system may have several raised alarms with the 340001 ID having different instance values. Instance is usually used to link an alarm to a particular data item (such as a particular failed disk, or a delivery service having A&D troubles).

Recommended Action Advise the user how to handle this raised alarm. This is shown in the CDSM GUI or command-line interface (CLI).

Alarm 700003 (rea_alarm) REA agent alarm was raised.

Explanation The Remote Execution Agent (REA) raised an alarm. This may lead to services such as URL deletion not functioning.

Recommended Action Restart the REA from the CLI.


OL-24530-01

Chapter 2 AlarmsSNMP Alarm Traps

Alarm 900001 (memory_exceed) Web Engine memory exceeds the threshold value.

Explanation The Web Engine reached the memory threshold.

Recommended Action Avoid further Web Engine service requests to this SE.

Alarm 900002 (max_session_exceed) Web Engine concurrent sessions exceeds the threshold value.

Explanation The Web Engine reached the session threshold (29000 concurrent sessions).

Recommended Action Avoid further Web Engine service requests to this SE.

Alarm 1000010 (ManifestEmptyContent) Parsed Manifest file does not have any items to process.

Explanation There are no single or crawl items mentioned in the manifest file to process.

Recommended Action Edit the manifest file of this delivery service to have one or more items to process.

SNMP Alarm TrapsCisco ECDS Release 2.5 software supports six generic alarms traps. Table 2-1 presents the trap number and trap type of the six generic alarm traps. Alarm traps sent from an ECDS device contain a numeric alarm identifier, a trap number, a module identifier, and a category identifier. To enable the ECDS device to send SNMP alarm traps for a specific alarm condition, use the snmp-server enable traps command. You can configure the generation of alarm traps based on the severity of the alarm and on whether the alarm is raised or cleared.

Table 2-2 below presents the mapping of module names to module identifiers .

Table 2-1 Generic Alarm Traps

Trap Number Trap Type

7 Critical alarm raised

8 Critical alarm cleared

9 Major alarm raised

10 Major alarm cleared

11 Minor alarm raised

12 Minor alarm cleared

Table 2-2 Mapping of Module Names to Module Identifiers

Module Name Module Identifier

Acquirer 4000

Active Directory Database 8000

Content Management Service 3000

Flash Media Streaming 4500


OL-24530-01


Table 2-3 below presents the mapping of category names to category identifiers.

Movie Streamer 4750

Multicast data sender 7000

Node Health Manager 1

Node Health Manager 2 500

Network Interface Card 5500

Node Manager 2000

Remote Execution Agent 3500

Service Router 5600

Standby 4000

Service Monitor 5700

System Monitor 1000

Unicast data receiver 5000

Unicast data sender 6000

Web Engine 2500

Windows Media Technologies 9000

Table 2-2 Mapping of Module Names to Module Identifiers

Module Name Module Identifier

Table 2-3 Mapping of Category Names to Category IDs

Category Name Category Identifier

Communications 1

Service Quality 2

Processing Error 3

Equipment 4

Environment 5

Content 6


OL-24530-01


C H A P T E R


OL-24530-01

3Error Messages and Recovery Procedures

This chapter lists the Cisco Enterprise CDS Release 2.5 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, page 3-2

• ACQ Messages, page 3-4

• AUTH Messages, page 3-7

• BANDWD Messages, page 3-7

• CDNFS Messages, page 3-11

• CLEAN-AD Messages, page 3-13

• CLI Messages, page 3-14

• CMS Messages, page 3-25

• COMMONEDM Messages, page 3-68

• DHCP Messages, page 3-69

• DISK Messages, page 3-70

• DIST Messages, page 3-76

• DS Messages, page 3-81

• FFS Messages, page 3-84

• FMS Messages, page 3-84

• HTTP Messages, page 3-85

• ICAP Messages, page 3-86

• LIBCMN Messages, page 3-86

• LOGGING Messages, page 3-90

• DHCP Messages, page 3-69

• NHM Messages, page 3-92

• NODEMGR Messages, page 3-92

• NTP Messages, page 3-108

• PAM Messages, page 3-109


OL-24530-01

Chapter 3 Error Messages and Recovery ProceduresACL Messages

• PARSER Messages, page 3-114

• POSTGRE Messages, page 3-120

• RPC Messages, page 3-121

• RTSP Messages, page 3-122

• RTSPG Messages, page 3-123

• RULES Messages, page 3-125

• SCHED Messages, page 3-132

• SERMON Messages, page 3-133

• SNMP Messages, page 3-133

• SR Messages, page 3-136

• SSHD Messages, page 3-141

• SSRV Messages, page 3-142

• STATS Messages, page 3-143

• STDBY Messages, page 3-146

• SYS Messages, page 3-147

• SYSMON Messages, page 3-148

• SYSUTL Messages, page 3-150

• TFTP Messages, page 3-151

• UNILOG Messages, page 3-154

• UPG Messages, page 3-155

• URLFLT Messages, page 3-166

• WMT Messages, page 3-166

• XXX Messages, page 3-172

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.


OL-24530-01

Chapter 3 Error Messages and Recovery ProceduresACL Messages

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.


OL-24530-01

Chapter 3 Error Messages and Recovery ProceduresACQ Messages

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.


OL-24530-01


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.


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.



OL-24530-01


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

Explanation The acquirer received corrupt RPC data.


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.


Error Message SE-ACQ-2-100010 Unable to acquire start-url = [chars], status = [chars].

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 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 delivery service id=[chars] for Task: [chars] is not in an active root delivery service.

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.


OL-24530-01

Chapter 3 Error Messages and Recovery ProceduresAUTH Messages

AUTH Messages

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

Explanation None.

Recommended Action No action is required.

Error Message SE-AUTH-3-110002:authenticate: username is too long.

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 [chars].

Explanation None.

Recommended Action Contact Cisco TAC.

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.



OL-24530-01

Chapter 3 Error Messages and Recovery ProceduresBANDWD Messages

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

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


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.


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.


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

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


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

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



OL-24530-01


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.


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.


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.


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.


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.


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.



OL-24530-01


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.


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 dataserver with error [x].

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


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.


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.



OL-24530-01

Chapter 3 Error Messages and Recovery ProceduresCDNFS Messages

Error Message SE-BANDWD-3-115020:Failed to set Bandwidth for module [chars] to [chars].

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


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.


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 Technical Assistance CenterSE-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.


OL-24530-01

Chapter 3 Error Messages and Recovery ProceduresCDNFS Messages

Error Message SE-CDNFS-3-480004:less than 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.



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


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.


OL-24530-01

Chapter 3 Error Messages and Recovery ProceduresCLEAN-AD Messages

CLEAN-AD Messages

Error Message SE-CLEAN-AD-2-210101:There was a problem while trying to connect to Database.

Explanation There was a problem while trying to connect to the database during Active Directory (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/CAL] 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 Enterprise CDSM. Fix the problem accordingly and retry.

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

Explanation The 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.


OL-24530-01

Chapter 3 Error Messages and Recovery ProceduresCLI Messages

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

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 .

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.


OL-24530-01


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

Explanation opendir() failed in the EXEC.


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

Explanation opendir() failed in the EXEC.


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

Explanation File operations (open, write) failed.


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.


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.


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

Explanation The CLI could not establish a connection.



OL-24530-01


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



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



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:run_command: [cmd] [description].

Explanation The command failed.


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

Explanation Cannot retrieve the startup configuration.


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

Explanation A file is missing.


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

Explanation Cannot retrieve statistics for a specific interface.



OL-24530-01


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

Explanation Failed to read the interface statistics file.


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

Explanation Failed to open a file mentioned in the message.


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

Explanation Cannot find expected CDP information.


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

Explanation Failed to open a file mentioned in the message.


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.


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.


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.


OL-24530-01


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.


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

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


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

Explanation Stopped evaluation for application.


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

Explanation The syslog cleared.


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

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 , rc = ; [description].

Explanation Cannot set the default value for some configuration items.


Error Message SE-CLI-7-170035:.

Explanation This message indicates debug messages.



OL-24530-01


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 Technical Assistance CenterTechnical Assistance CenterTechnical Assistance Center 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.


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



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



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



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




OL-24530-01


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

Explanation A termination signal was received by the process.


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

Explanation The Process could not successfully issue a termination signal.


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.


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.


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.


Error Message SE-CLI-5-170051:create_etc_hosts.sh: .

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



OL-24530-01


Error Message SE-CLI-3-170052:Failed to recreate etc_hosts .

Explanation The system failed to recreate an important internal file.


Error Message SE-CLI-5-170053:Recreated etc_hosts .

Explanation Successfully recreated an important internal file.


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

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=.

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-170058:get_config: failed to (pickup | save) initial (disk | CLI) configurations [description].

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.


OL-24530-01


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).


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 bec

Cisco ECDS 2.5 Alarms and Error Messages Guide · † Audience, page vi ... for use by the MDEs....

Documents

Transcript of Cisco ECDS 2.5 Alarms and Error Messages Guide · † Audience, page vi ... for use by the MDEs....