- Preface
- Product Overview
- Network Design
- Getting Started
- Configuring the VDS
- System Monitoring
- System Reporting
- System Maintenance
- Troubleshooting
- Creating Bulk Configuration Files
- BMS Communication
- SNMP MIB and Trap Information
- Using the TV VDS Streamer Application Monitoring Tool
- Engineering Access Level Pages
- CDDM Management Utility
- Software Licensing Information
- VDS-TV Tunables
- Installation, Upgrade, and Downgrade via YUM
- Configuring for Port Resiliency
Cisco VDS-VR Software 4.1 Configuration Guide
- Updated:
- December 14, 2015
Chapter: SNMP MIB and Trap Information
SNMP MIB and Trap Information
This appendix describes the Simple Network Management Protocol (SNMP) traps sent by the VDS. 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 Configuring the SNMP Agent.
Note
We recommend configuring a VLAN for management traffic.
SNMP management features on the servers include:
SNMP Agent
The SNMP agent of the server uses certain variables that are included in a Cisco Management Information Base (MIB) file.
The SNMP agent is controlled by the following commands:
The snmpd service rc script automatically configures the snmpd service to be started in Linux run-levels 5 and 6. To make any changes to this behavior, the chkconfig or ntsysv commands can be used. The following command configures snmpd to be managed by using the chkconfig command:
The following command configures snmpd to be turned on in run levels 5 and 6:
The SNMP log file, snmpd.log, is located in the /arroyo/log directory. All log entries use UTC for the time stamp. All VDS-specific SNMP traps are logged in the snmpd.log file.
SNMP Agent on a CDSM or VVIM
The SNMP agent on the CDSM must be manually configured, you cannot configure the SNMP settings on the CDSM by using the Configure > Server Level > SNMP page. Check that the snmpd.conf file on the CDSM is properly configured by logging in to the CDSM as user root, going to the /usr/local/share/snmp directory and viewing the snmpd.conf file. If the SNMP settings are not correct, manually configure them by editing the snmpd.conf file.
SNMP Management Objects and Traps
The VDS SNMP agent and Management Information Base (MIB) file are compliant with the Internet Engineering Task Force (IETF) standards for SNMP v1, SNMP v2c, and SNMPv3. For a list of SNMP-associated Request For Comment (RFC) specifications, see RFC Compliance.
The Cisco VDS-VR MIBs consist of the following:
- CISCO-CDS-TV-MIB.my
- CISCO-CDSTV-SERVICES-MIB.my
- CISCO-CDSTV-FSI-MIB.my
- CISCO-CDSTV-INGESTMGR-MIB.my
- CISCO-CDSTV-BWMGR-MIB.my
- CISCO-CDSTV-INGEST-TUNING-MIB.my
- CISCO-CDSTV-CS-STATS-MIB.my
- CISCO-CDSTV-AUTHMGR-MIB.my
- CISCO-CDSTV-SERVER-MIB.my
- CISCO-CDSTV-ISA-MIB.my (Only applicable to ISA environments)
The Cisco VDS-VR MIBs are available through the CDSM, and are dependent on the following MIBs distributed on Cisco.com:
- ftp://ftp.cisco.com/pub/mibs/v2/CISCO-SMI.my
- ftp://ftp.cisco.com/pub/mibs/v2/CISCO-TC.my
- ftp://ftp.cisco.com/pub/mibs/v2/CISCO-PRODUCTS-MIB.my
- ftp://ftp.cisco.com/pub/mibs/v2/INET-ADDRESS-MIB.my
- ftp://ftp.cisco.com/pub/mibs/v2/DIFFSERV-DSCP-TC.my
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.
CISCO-CDS-TV-MIB 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 D-1 describes the traps in the CISCO-CDS-TV-MIB.
|
|
|
|---|---|
Previously inactive disk is now active and ready, that is, the disk has returned to the OK (0) state. |
|
Active disk is now inactive, that is, it has left the OK (0) state. |
|
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. |
|
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. |
|
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 Setting System Thresholds. When the disk usage exceeds the threshold set for the Disk Capacity Notify field, the cdstvDiskUsageHigh trap is sent. |
|
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. |
|
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. |
|
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. |
|
Port loss on the system has crossed the maximum threshold. The cdstvPortLossPercent object, which contains port loss percentage, is sent with the trap. |
|
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. |
|
Previously abnormal system health parameter is now normal; that is, it has left the not OK state. See Table D-2 for the descriptions of the objects sent with this trap. |
|
Previously normal system health parameter is now abnormal; that is, it has left the OK state. See Table D-2 for the descriptions of the objects sent with this trap. |
|
Signifies that one or more assets on a Vault or ISV are broken. A trap is sent whenever the number of broken assets found changes, whether from 0 to n, n to m, or m to 0. The trap contains one object, cdstvBrokenAssets, which specifies the current number of broken assets. The broken asset information stays in memory and is not persisted in the database. Note The cdstvBrokenAssets value is only valid if the Vault is the master Vault, which can be verified by the cdstvVaultMasterSlaveStatus object. |
|
| The cdstvServerMasterSlaveStatus object is set when the server status changes to master or slave; it has two possible values: master (1) and slave (2). A value of 0 means that the status is not yet available from statsd. |
|
| The cdstvServerMasterSlaveStatus object is set when the server status changes to master or slave; it has two possible values: master (1) and slave (2). A value of 0 means that the status is not yet available from statsd. |
|
Setup IP address has changed (Streamer and ISV only). If Setup IP and Control IP are the same (Setup/Control IP) and both change simultaneously, both cdstvSetupIpChanged and cdstvControlIpChanged traps are sent. |
|
Control IP address has changed (Streamer and ISV only). If Setup IP and Control IP are the same (Setup/Control IP) and both change simultaneously, both cdstvSetupIpChanged and cdstvControlIpChanged traps are sent. |
|
Database synchronization connection from this VDS server to another VDS server has failed. The cdstvDbConnectionFailedIp OID contains the IP address of the server to which a database connection failed. |
|
Signifies that the Linux partition indicated by cdstvLinuxFSMountPoint is read-only. |
|
Signifies that the Linux partition indicated by cdstvLinuxFSMountPoint is now back to normal (read-write). |
Monitored Broken Assets SNMP Traps
After the statsd process is started, it waits 5 minutes (300 seconds) before collecting statistics. If a broken asset occurs within these 5 minutes, it is detected and the cdstvBrokenAsset trap is sent.
After the first cycle of collecting statistics is complete, statsd waits 60 minutes from the beginning of the previous cycle before collecting statistics again. This repeats every 60 minutes.
Note If at any point mirroring is active, the statistics collection is skipped.
The time delay in receiving the cdstvBrokenAsset trap after a broken asset occurs depends on how much time is left until the next time statsd collects content statistics.
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 Services Monitor.
For the cdstvServiceUp and cdstvServiceDown traps in the CISCO-CDSTV-SERVICES-MIB, 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 VDS 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 VDS servers and the states and thresholds are displayed on the Server Vitals page. See Server Vitals. 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).
Note The Server Vitals page is displayed only if the CDSM Health Monitor feature is enabled. For more information, see CDSM or VVIM Health Monitoring.
Table D-2 describes the objects that are sent with the cdstvSysHealthUp and cdstvSysHealthDown traps.
Recorder Statistics
Statistics from the Recorder are found in the following objects of CISCO-CDSTV-CS-STATS-MIB.
|
|
|
|
|
|---|---|---|---|
RFC Compliance
Table D-4 is a list of SNMP RFC standards.
Feedback