Cisco TV CDS 2.4 RTSP Software Configuration Guide for the Cisco ISM (Integrated Service Module) Line Card
SNMP MIB and Trap Information
Downloads: This chapterpdf (PDF - 115.0KB) The complete bookPDF (PDF - 4.7MB) | Feedback

Table of Contents

SNMP MIB and Trap Information

Overview

SNMP Agent

SNMP Management Objects and Traps

RFC Compliance

SNMP MIB and Trap Information

This appendix describes the Simple Network Management Protocol (SNMP) traps sent by the CDS. The topics covered in this appendix include:

Overview

You can manage the servers by way of SNMP from a Network Management System (NMS). To implement SNMP management, the servers must be configured with a management IP address, SNMP community strings, and contact information. For more information about configuring the server for SNMP communication, see the “Configuring the SNMP Agent” section.


NoteWe recommend configuring a VLAN for management traffic. We recommend configuring a VLAN for management traffic.


SNMP management features on the servers include:

  • SNMP version 1 or version 2c
  • Standard MIBs

SNMP Agent

The SNMP agent on the server uses certain variables that are included in a Cisco Management Information Base (MIB) file. By default, the SNMP agent is not started automatically. To start the SNMP agent, login to the server as root and enter the following command:

# nice -n 19 /usr/local/sbin/snmpd
 

To have the SNMP agent start automatically after a reboot, use the Linux vi editor to add the following to the /etc/rc.local file:

nice -n 19 /usr/local/sbin/snmpd
 

To verify the SNMP agent has started, enter the ps -ef | grep snmpd command.

SNMP Management Objects and Traps

The CDS SNMP agent and Management Information Base (MIB) file are compliant with the Internet Engineering Task Force (IETF) standards for SNMP v1 and SNMP v2c. For a list of SNMP-associated Request For Comment (RFC) specifications, see the “RFC Compliance” section.

The CISCO-CDS-TV-MIB.txt MIB file is available through the CDSM, and is dependent on the following MIBs distributed on Cisco.com:

You can download the MIBs by doing the following:


Step 1 Choose Configure > Server Level > SNMP Agent . The SNMP Agent page is displayed with a list of the MIB files at the bottom of the page.

Step 2 To save the file locally, right-click the MIB filename, and choose Save As , Save Target As , or a similar save command.

To view the file, click the MIB filename.


 

The CISCO-CDS-TV-MIB.txt file has the following MIB nodes:

  • cdstvConfigObjects—Configuration of servers
  • cdstvMonitorObjects—Monitoring of cache-fill, streaming, disk states, and services running
  • cdstvNotifyObjects—Objects specific to traps (notifications), for example, Managed Services Architecture (MSA) event objects

Table C-1 describes the traps in the CISCO-CDS-TV-MIB.

 

Table C-1 Cisco TV CDS Traps

Trap
Description

cdstvDiskHealthUp

Previously inactive disk is now active and ready, that is, the disk has returned to the OK (0) state.

cdstvDiskHealthDown

Active disk is now inactive, that is, it has left the OK (0) state.

cdstvMSAEvent

MSA event (error) has occurred.

cdstvServiceUp

Previously stopped service is now running, that is, it has left the not running state. The cdstvServiceName object, which contains the name of the service, is sent with the trap.

cdstvServiceDown

Previously running service is now stopped, that is, it has left the running state. The cdstvServiceName object, which contains the name of the service, is sent with the trap.

cdstvDiskUsageHigh

Disk usage on the system has crossed the maximum usage threshold. The cdstvDiskUsagePercent object, which contains the percentage of the disk that is used, is sent with the trap.

This trap corresponds to the Disk Capacity Notify field on the System Threshold page. For more information, see the “Setting System Thresholds” section. When the disk usage exceeds the threshold set for the Disk Capacity Notify field, the cdstvDiskUsageHigh trap is sent.

cdstvDiskUsageNormal

Disk usage on the system has returned to a value within the usage threshold. The cdstvDiskUsagePercent object, which contains the percentage of the disk that is used, is sent with the trap.

cdstvLinuxFSUsageHigh

Linux file system (FS) usage on the server has crossed the maximum usage threshold. The cdstvLinuxFSMountPoint and cdstvLinuxFSUsagePercent objects, which contain the mount point and the percentage used, are sent with the trap.

cdstvLinuxFSUsageNormal

Linux file system (FS) usage on the server has returned to a value within the usage threshold. The cdstvLinuxFSMountPoint and cdstvLinuxFSUsagePercent objects, which contain the mount point and the percentage used, are sent with the trap.

cdstvPortLossHigh

Port loss on the system has crossed the maximum threshold. The cdstvPortLossPercent object, which contains port loss percentage, is sent with the trap.

cdstvPortLossNormal

Port loss on the system has returned to a value within the threshold. The cdstvPortLossPercent object, which contains port loss percentage, is sent with the trap.

cdstvSysHealthUp

Previously abnormal system health parameter is now normal; that is, it has left the not OK state. See Table C-2 for the descriptions of the objects sent with this trap.

cdstvSysHealthDown

Previously normal system health parameter is now abnormal; that is, it has left the OK state. See Table C-2 for the descriptions of the objects sent with this trap.

Monitored Services SNMP Traps

The services reported as up or down in SNMP correspond to the services on the Service Monitor page. For more information on the monitored services, see the “Services Monitor” section.

For the cdstvServiceUp and cdstvServiceDown traps, if the database shuts down, a cdstvServiceDown trap is sent for the Cisco DB server, but no other services can be monitored without the database running. No SNMP traps are sent for services until the database is functional again.

If the SNMP agent itself is down, the CDSM shows the Cisco SNMP Server as “Not Running” but no SNMP trap can be sent for this service because the SNMP agent itself is down.

If the CDS server is shut down cleanly, there may be a cdstvServiceDown trap sent for the Cisco SNMP Server before the entire server shuts down. No traps can be sent until the SNMP agent is running.

System Health Threshold Crossing Alerts

The temperature, fans, and power are monitored on the CDS servers and the states and thresholds are displayed on the Server Vitals page. See the “Server Vitals” section. If a threshold is exceeded, an alarmed event is registered on the CDSM and the cdstvSysHealthDown trap is sent with information about the threshold crossing alert (TCA).


NoteThe Server Vitals page is displayed only if the CDSM Health Monitor feature is enabled. For more information, see the The Server Vitals page is displayed only if the CDSM Health Monitor feature is enabled. For more information, see the “CDSM or VVIM Health Monitoring” section.


Table C-2 describes the objects that are sent with the cdstvSysHealthUp and cdstvSysHealthDown traps.

 

Table C-2 System Health SNMP Trap Objects

Descriptor
Possible values
Description

cdstvSysHealthName

String

Name of the system health monitoring parameter, for example, VBAT Voltage.

cdstvSysHealthType

1—Fan-speed

2—Voltage

3—Temperature

4—Chassis intrusion

5—Power supply failure

Type of the system health monitoring parameter.

cdstvSysHealthReading

Integer

Current reading (value) of the system health parameter; for example, fan speed, voltage, or temperature. Fan speed is expressed in rpm, voltage in mV and temperature in degree Celsius. For chassis intrusion and power-supply failure, 1 denotes an error condition, and 0 denotes normal condition.

cdstvSysHealthHighLimit

Integer

Higher limit (threshold) of the system health parameter. Voltage is expressed in mV and temperature in degree Celsius. Not applicable for other parameters such as fan speed.

cdstvSysHealthLowLimit

Integer

Lower limit (threshold) of the system health parameter. Fan speed is expressed in rpm and voltage in mV. Not applicable for other parameters such as temperature.

cdstvSysHealthStatus

1—Normal

2—Low

3—High

4—Not-OK

Current status of the system health parameter. The not-ok value applies to power supply failure and chassis intrusion, because high and low limits do not apply to these parameters.

RFC Compliance

Table C-3 is a list of SNMP RFC standards.

 

Table C-3 SNMP RFC Standards

RFC Standard
Title

RFC 1155 (STD0016)

Structure and Identification of Management Information for TCP/IP-based Internets

RFC 1157 (STD0015)

Simple Network Management Protocol (SNMP)

RFC 1212 (STD0016)

Concise MIB Definitions

RFC 1213 (STD0017)

Management Information Base for Network Management of TCP/IP-based internets:MIB-II

RFC 2790 (Draft Standard)

Host Resources MIB

RFC 1901(Historic)

Introduction to Community-based SNMPv2

RFC 1902 (Draft Standard)

Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)

RFC 1903 (Draft Standard)

Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)

RFC 1904 (Draft Standard)

Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2)

RFC 1905 (Draft Standard)

Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)

RFC 1906 (Draft Standard)

Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)

RFC 1910 (Historic)

User-based Security Model for SNMPv2

RFC 2011(Proposed Standard - Updates RFC 1213)

SNMPv2 Management Information Base for the Internet Protocol using SMIv2

RFC 2012 (Proposed Standard)

SNMPv2 Management Information Base for the Transmission Control Protocol using SMIv2

RFC 2013 (Proposed Standard)

SNMPv2 Management Information Base for the User Datagram Protocol using SMIv2

RFC 2096 (Proposed Standard)

IP Forwarding Table MIB

RFC 2863 (Draft Standard)

The Interfaces Group MIB

RFC 3410 (Informational)

Introduction and Applicability Statements for Internet-Standard Management Framework

RFC 3411 (STD0062)

An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks

RFC 3412 (STD0062)

Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)

RFC 3413 (STD0062)

Simple Network Management Protocol (SNMP) Applications

RFC 3414 (STD0062)

User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)

RFC 3415 (STD0062)

View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)

RFC 3416 (STD0062)

Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP)

RFC 3417 (STD0062)

Transport Mappings for the Simple Network Management Protocol (SNMP)

RFC 3418 (STD0062)

Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)

RFC 2570 (Informational)

Introduction to Version 3 of the Internet-standard Network Management Framework

RFC 2571 (Draft Standard)

An Architecture for Describing SNMP Management Frameworks

RFC 2572 (Draft Standard)

Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)

RFC 2573 (Draft Standard)

SNMP Applications

RFC 2574 (Draft Standard)

User-based Security Model (USM) for Version 3 of the Simple Network Management Protocol (SNMPv3)

RFC 2575 (Draft Standard)

View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)

RFC 2576 (Proposed Standard)

Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework

RFC 2578 (STD0058)

Structure of Management Information Version 2 (SMIv2)

RFC 2579 (STD0058)

Textual Conventions for SMIv2

RFC 2580 (STD0058)

Conformance Statements for SMIv2