Acronyms and Definitions
The following acronyms and terms are used in this
document:
DMS: Digital Media Systems
DAM: Digital Asset Management System
DMM: Digital Media Manager Application
VP : Video Portal Application
DSM: Digital Signage Manager Application
ETV: Enterprise TV Manager Application
DMP: Cisco Digital Media Player
LAN: Local Area Network
Group: A collection of DMS users grouped and
managed together as a single entity for
administrative convenience.
Overview of the MIB
This is a MIB Module for managing and monitoring the physical
and logical structures in Cisco Digital Media Management
System. The MIB reflects the structure as follows:
* show DMS as an coherent, abstract media management system
* indicate the physical inventory of DMS
* indicate the media management features active (licensed)
in the system.
* show the streaming and storage components and their
activity
* elements of DMS security
* external servers used by the system
* events and alarms
Hence, the MIB contains eight major groups of objects organized
as follows:
a) DMS System Group:
This section models distributed DMS as a single abstract
system.
b) DMS Features Group:
This section lists the DMS functions that this
installation is licensed to perform and those that it
is not.
c) DMS Inventory Group:
This section lists the physical elements that this
installation of DMS comprises.
d) Servers Group:
This section models the external servers used by this
installation of DMS.
e) Digital Asset Management (DAM) Services Group:
This section models the state and activity of various
content management services that this installation of
DMS is equipped with. The loose term 'content management'
has been intentionally used to as to be able to
accommodate more content management services in this
model as they evolve.
f) Security Group:
This section defines the security configuration and
activity of this installation of DMS.
g) Fault Tolerance Group:
This section models the redundancy (failover and
load balancing) configuration of this installation of
DMS and the associated activity.
h) User Management Group:
This section models the configured DMS users, groups
and the associated activity.
i) Events and Faults Group:
This section models the events, alarms and notifications
reported by this installation of DMS.
j) Capacity Group:
This section is planned for the future and would define
the limits and capacities of functions of DMS. These
include limits such as the type of media encodings that
are supported, the maximum number of media players that
may be managed etc.
k) Resource Usage Group:
This section is planned for the future and would define
the current resource usage by DMS.
This would include the amount of storage used by DMS,
the number of encoders currently in use etc.
l) Threshold group (allows definition of high water marks)
This section is planned for the future and would allow
the management entity to define thresholds to set high
water marks on critical metrics.
m) Notifications
This section defines notifications to signal
significant events pertaining to this installation of
DMS.
Parsed from file CISCO-DIGITAL-MEDIA-SYSTEMS-MIB.mib
Module: CISCO-DIGITAL-MEDIA-SYSTEMS-MIB
Acronyms and Definitions
The following acronyms and terms are used in this
document:
DMS: Digital Media Systems
DAM: Digital Asset Management System
DMM: Digital Media Manager Application
VP : Video Portal Application
DSM: Digital Signage Manager Application
ETV: Enterprise TV Manager Application
DMP: Cisco Digital Media Player
LAN: Local Area Network
Group: A collection of DMS users grouped and
managed together as a single entity for
administrative convenience.
Overview of the MIB
This is a MIB Module for managing and monitoring the physical
and logical structures in Cisco Digital Media Management
System. The MIB reflects the structure as follows:
* show DMS as an coherent, abstract media management system
* indicate the physical inventory of DMS
* indicate the media management features active (licensed)
in the system.
* show the streaming and storage components and their
activity
* elements of DMS security
* external servers used by the system
* events and alarms
Hence, the MIB contains eight major groups of objects organized
as follows:
a) DMS System Group:
This section models distributed DMS as a single abstract
system.
b) DMS Features Group:
This section lists the DMS functions that this
installation is licensed to perform and those that it
is not.
c) DMS Inventory Group:
This section lists the physical elements that this
installation of DMS comprises.
d) Servers Group:
This section models the external servers used by this
installation of DMS.
e) Digital Asset Management (DAM) Services Group:
This section models the state and activity of various
content management services that this installation of
DMS is equipped with. The loose term 'content management'
has been intentionally used to as to be able to
accommodate more content management services in this
model as they evolve.
f) Security Group:
This section defines the security configuration and
activity of this installation of DMS.
g) Fault Tolerance Group:
This section models the redundancy (failover and
load balancing) configuration of this installation of
DMS and the associated activity.
h) User Management Group:
This section models the configured DMS users, groups
and the associated activity.
i) Events and Faults Group:
This section models the events, alarms and notifications
reported by this installation of DMS.
j) Capacity Group:
This section is planned for the future and would define
the limits and capacities of functions of DMS. These
include limits such as the type of media encodings that
are supported, the maximum number of media players that
may be managed etc.
k) Resource Usage Group:
This section is planned for the future and would define
the current resource usage by DMS.
This would include the amount of storage used by DMS,
the number of encoders currently in use etc.
l) Threshold group (allows definition of high water marks)
This section is planned for the future and would allow
the management entity to define thresholds to set high
water marks on critical metrics.
m) Notifications
This section defines notifications to signal
significant events pertaining to this installation of
DMS.
Parsed from file CISCO-DIGITAL-MEDIA-SYSTEMS-MIB.my.txt
Company: None
Module: CISCO-DIGITAL-MEDIA-SYSTEMS-MIB
Acronyms and Definitions
The following acronyms and terms are used in this
document:
DMS: Digital Media Systems
DAM: Digital Asset Management System
DMM: Digital Media Manager Application
VP : Video Portal Application
DSM: Digital Signage Manager Application
ETV: Enterprise TV Manager Application
DMP: Cisco Digital Media Player
LAN: Local Area Network
Group: A collection of DMS users grouped and
managed together as a single entity for
administrative convenience.
Overview of the MIB
This is a MIB Module for managing and monitoring the physical
and logical structures in Cisco Digital Media Management
System. The MIB reflects the structure as follows:
* show DMS as an coherent, abstract media management system
* indicate the physical inventory of DMS
* indicate the media management features active (licensed)
in the system.
* show the streaming and storage components and their
activity
* elements of DMS security
* external servers used by the system
* events and alarms
Hence, the MIB contains eight major groups of objects organized
as follows:
a) DMS System Group:
This section models distributed DMS as a single abstract
system.
b) DMS Features Group:
This section lists the DMS functions that this
installation is licensed to perform and those that it
is not.
c) DMS Inventory Group:
This section lists the physical elements that this
installation of DMS comprises.
d) Servers Group:
This section models the external servers used by this
installation of DMS.
e) Digital Asset Management (DAM) Services Group:
This section models the state and activity of various
content management services that this installation of
DMS is equipped with. The loose term 'content management'
has been intentionally used to as to be able to
accommodate more content management services in this
model as they evolve.
f) Security Group:
This section defines the security configuration and
activity of this installation of DMS.
g) Fault Tolerance Group:
This section models the redundancy (failover and
load balancing) configuration of this installation of
DMS and the associated activity.
h) User Management Group:
This section models the configured DMS users, groups
and the associated activity.
i) Events and Faults Group:
This section models the events, alarms and notifications
reported by this installation of DMS.
j) Capacity Group:
This section is planned for the future and would define
the limits and capacities of functions of DMS. These
include limits such as the type of media encodings that
are supported, the maximum number of media players that
may be managed etc.
k) Resource Usage Group:
This section is planned for the future and would define
the current resource usage by DMS.
This would include the amount of storage used by DMS,
the number of encoders currently in use etc.
l) Threshold group (allows definition of high water marks)
This section is planned for the future and would allow
the management entity to define thresholds to set high
water marks on critical metrics.
m) Notifications
This section defines notifications to signal
significant events pertaining to this installation of
DMS.
ciscoDigitalMediaSystemsMIB MODULE-IDENTITY LAST-UPDATED "200910120000Z" ORGANIZATION "Cisco Systems" CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134-1700 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "Acronyms and Definitions The following acronyms and terms are used in this document: DMS: Digital Media Systems DAM: Digital Asset Management System DMM: Digital Media Manager Application VP : Video Portal Application DSM: Digital Signage Manager Application ETV: Enterprise TV Manager Application DMP: Cisco Digital Media Player LAN: Local Area Network Group: A collection of DMS users grouped and managed together as a single entity for administrative convenience. Overview of the MIB This is a MIB Module for managing and monitoring the physical and logical structures in Cisco Digital Media Management System. The MIB reflects the structure as follows: * show DMS as an coherent, abstract media management system * indicate the physical inventory of DMS * indicate the media management features active (licensed) in the system. * show the streaming and storage components and their activity * elements of DMS security * external servers used by the system * events and alarms Hence, the MIB contains eight major groups of objects organized as follows: a) DMS System Group: This section models distributed DMS as a single abstract system. b) DMS Features Group: This section lists the DMS functions that this installation is licensed to perform and those that it is not. c) DMS Inventory Group: This section lists the physical elements that this installation of DMS comprises. d) Servers Group: This section models the external servers used by this installation of DMS. e) Digital Asset Management (DAM) Services Group: This section models the state and activity of various content management services that this installation of DMS is equipped with. The loose term 'content management' has been intentionally used to as to be able to accommodate more content management services in this model as they evolve. f) Security Group: This section defines the security configuration and activity of this installation of DMS. g) Fault Tolerance Group: This section models the redundancy (failover and load balancing) configuration of this installation of DMS and the associated activity. h) User Management Group: This section models the configured DMS users, groups and the associated activity. i) Events and Faults Group: This section models the events, alarms and notifications reported by this installation of DMS. j) Capacity Group: This section is planned for the future and would define the limits and capacities of functions of DMS. These include limits such as the type of media encodings that are supported, the maximum number of media players that may be managed etc. k) Resource Usage Group: This section is planned for the future and would define the current resource usage by DMS. This would include the amount of storage used by DMS, the number of encoders currently in use etc. l) Threshold group (allows definition of high water marks) This section is planned for the future and would allow the management entity to define thresholds to set high water marks on critical metrics. m) Notifications This section defines notifications to signal significant events pertaining to this installation of DMS." REVISION "200910120000Z" DESCRIPTION "Added support for High Availability (HA)." REVISION "200805150000Z" DESCRIPTION "Initial version of this module." ::= { ciscoMgmt 655 }
ciscoDigitalMediaSystemsMIB OBJECT IDENTIFIER ::= { ciscoMgmt 655 }
Vendor: Cisco
Module: CISCO-DIGITAL-MEDIA-SYSTEMS-MIB
[Automatically extracted from oidview.com]
ciscoDigitalMediaSystemsMIB MODULE-IDENTITY LAST-UPDATED "201109070000Z" ORGANIZATION "Cisco Systems" CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134-1700 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "Acronyms and Definitions The following acronyms and terms are used in this document: DMS: Digital Media Systems DAM: Digital Asset Management System DMM: Digital Media Manager Application VP : Video Portal Application DSM: Digital Signage Manager Application ETV: Enterprise TV Manager Application DMP: Cisco Digital Media Player LAN: Local Area Network Group: A collection of DMS users grouped and managed together as a single entity for administrative convenience. Overview of the MIB This is a MIB Module for managing and monitoring the physical and logical structures in Cisco Digital Media Management System. The MIB reflects the structure as follows: * show DMS as an coherent, abstract media management system * indicate the physical inventory of DMS * indicate the media management features active (licensed) in the system. * show the streaming and storage components and their activity * elements of DMS security * external servers used by the system * events and alarms Hence, the MIB contains eight major groups of objects organized as follows: a) DMS System Group: This section models distributed DMS as a single abstract system. b) DMS Features Group: This section lists the DMS functions that this installation is licensed to perform and those that it is not. c) DMS Inventory Group: This section lists the physical elements that this installation of DMS comprises. d) Servers Group: This section models the external servers used by this installation of DMS. e) Digital Asset Management (DAM) Services Group: This section models the state and activity of various content management services that this installation of DMS is equipped with. The loose term 'content management' has been intentionally used to as to be able to accommodate more content management services in this model as they evolve. f) Security Group: This section defines the security configuration and activity of this installation of DMS. g) Fault Tolerance Group: This section models the redundancy (failover and load balancing) configuration of this installation of DMS and the associated activity. h) User Management Group: This section models the configured DMS users, groups and the associated activity. i) Events and Faults Group: This section models the events, alarms and notifications reported by this installation of DMS. j) Capacity Group: This section is planned for the future and would define the limits and capacities of functions of DMS. These include limits such as the type of media encodings that are supported, the maximum number of media players that may be managed etc. k) Resource Usage Group: This section is planned for the future and would define the current resource usage by DMS. This would include the amount of storage used by DMS, the number of encoders currently in use etc. l) Threshold group (allows definition of high water marks) This section is planned for the future and would allow the management entity to define thresholds to set high water marks on critical metrics. m) Notifications This section defines notifications to signal significant events pertaining to this installation of DMS." REVISION "201109070000Z" DESCRIPTION "Changed textual description for replacement field cdmsLicensedFeatureLimitRev1 to be consistent with field values. This was missed in last submitted version and caught during code review." REVISION "201107290000Z" DESCRIPTION "Resubmitting MIB with changes" REVISION "200910120000Z" DESCRIPTION "Added support for High Availability (HA)." REVISION "200805150000Z" DESCRIPTION "Initial version of this module." ::= { ciscoMgmt 655 }
ciscoDigitalMediaSystemsMIB MODULE-IDENTITY LAST-UPDATED "201109070000Z" ORGANIZATION "Cisco Systems" CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134-1700 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "Acronyms and Definitions The following acronyms and terms are used in this document: DMS: Digital Media Systems DAM: Digital Asset Management System DMM: Digital Media Manager Application VP : Video Portal Application DSM: Digital Signage Manager Application ETV: Enterprise TV Manager Application DMP: Cisco Digital Media Player LAN: Local Area Network Group: A collection of DMS users grouped and managed together as a single entity for administrative convenience. Overview of the MIB This is a MIB Module for managing and monitoring the physical and logical structures in Cisco Digital Media Management System. The MIB reflects the structure as follows: * show DMS as an coherent, abstract media management system * indicate the physical inventory of DMS * indicate the media management features active (licensed) in the system. * show the streaming and storage components and their activity * elements of DMS security * external servers used by the system * events and alarms Hence, the MIB contains eight major groups of objects organized as follows: a) DMS System Group: This section models distributed DMS as a single abstract system. b) DMS Features Group: This section lists the DMS functions that this installation is licensed to perform and those that it is not. c) DMS Inventory Group: This section lists the physical elements that this installation of DMS comprises. d) Servers Group: This section models the external servers used by this installation of DMS. e) Digital Asset Management (DAM) Services Group: This section models the state and activity of various content management services that this installation of DMS is equipped with. The loose term 'content management' has been intentionally used to as to be able to accommodate more content management services in this model as they evolve. f) Security Group: This section defines the security configuration and activity of this installation of DMS. g) Fault Tolerance Group: This section models the redundancy (failover and load balancing) configuration of this installation of DMS and the associated activity. h) User Management Group: This section models the configured DMS users, groups and the associated activity. i) Events and Faults Group: This section models the events, alarms and notifications reported by this installation of DMS. j) Capacity Group: This section is planned for the future and would define the limits and capacities of functions of DMS. These include limits such as the type of media encodings that are supported, the maximum number of media players that may be managed etc. k) Resource Usage Group: This section is planned for the future and would define the current resource usage by DMS. This would include the amount of storage used by DMS, the number of encoders currently in use etc. l) Threshold group (allows definition of high water marks) This section is planned for the future and would allow the management entity to define thresholds to set high water marks on critical metrics. m) Notifications This section defines notifications to signal significant events pertaining to this installation of DMS." REVISION "201109070000Z" DESCRIPTION "Changed textual description for replacement field cdmsLicensedFeatureLimitRev1 to be consistent with field values. This was missed in last submitted version and caught during code review." REVISION "201107290000Z" DESCRIPTION "Resubmitting MIB with changes" REVISION "200910120000Z" DESCRIPTION "Added support for High Availability (HA)." REVISION "200805150000Z" DESCRIPTION "Initial version of this module." ::= { ciscoMgmt 655 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.655.0 | ciscoDmsMonitorMIBNotifs | 7 | 7 | None |
| 1.3.6.1.4.1.9.9.655.1 | ciscoDmsMonitorMIBObjects | 10 | 165 | None |
| 1.3.6.1.4.1.9.9.655.2 | ciscoDmsMonitorMIBConform | 2 | 20 | None |
To many brothers! Only 100 nearest brothers are shown.
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| ... | ||||
| 1.3.6.1.4.1.9.9.606 | ciscoLwappMeshLinkTestMIB | 3 | 46 | ciscoLwappMeshLinkTestMIB MODULE-IDENTITY LAST-UPDATED "200702050000Z" ORGANIZATION "Cisco Systems Inc." CONTACT-INFO "Cisco Sy… |
| 1.3.6.1.4.1.9.9.607 | ciscoDot11HtPhyMIB | 3 | 71 | This MIB is intended to be implemented on Cisco's WLAN devices that provide the wired uplink to wireless clients through the high… |
| 1.3.6.1.4.1.9.9.610 | ciscoLwappRogueMIB | 3 | 78 | This MIB is intended to be implemented on all those devices operating as Central Controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.611 | ciscoLwappDot11ClientCCXTextualConventions | 0 | 0 | This module defines the textual conventions used throughout the Cisco enterprise MIBs designed for implementation on Central Cont… |
| 1.3.6.1.4.1.9.9.612 | ciscoLwappDot11MIB | 3 | 17 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.613 | ciscoEvcMIB | 3 | 156 | Metro Ethernet services can support a wide range of applications and subscriber needs easily, efficiently and cost-effectively. … |
| 1.3.6.1.4.1.9.9.614 | ciscoLwappDot11LdapMIB | 3 | 33 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.615 | ciscoLwappRrmMIB | 3 | 28 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.616 | ciscoLwappMeshMIB | 3 | 121 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.617 | ciscoLwappMeshStatsMIB | 4 | 98 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.618 | ciscoLwappSysMIB | 3 | 163 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.619 | ciscoLwappLocalAuthMIB | 3 | 53 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.620 | ciscoLwappMeshBatteryMIB | 3 | 34 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.621 | ciscoH324DialControlMIB | 2 | 34 | This MIB module enhances the IETF Dial Control MIB (RFC2128) by providing H.324 call information over a telephony network. ITU-T R… |
| 1.3.6.1.4.1.9.9.622 | ciscoLwappDot11ClientTsMIB | 3 | 34 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.623 | ciscoLwappCdpMIB | 3 | 51 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.624 | ciscoIpSlaTCMIB | 0 | 0 | This MIB contains textual conventions used by CISCO IPSLA MIBs. Acronyms: FEC: Forward Equivalence Class LPD: Label Path Discovery L… |
| 1.3.6.1.4.1.9.9.626 | ciscoDot11HtMacMIB | 3 | 40 | This MIB is intended to be implemented on Cisco's WLAN devices that provide the wired uplink to wireless clients through the high… |
| 1.3.6.1.4.1.9.9.627 | ciscoDot11RadarMIB | 3 | 25 | This MIB module is for IEEE 802.11a/h Root device, i.e. Access Point (AP) or Root Bridge. This MIB allows dynamic frequency selec… |
| 1.3.6.1.4.1.9.9.628 | ciscoServiceControlSubscribersMIB | 3 | 37 | This MIB provides global and specific information on subscribers managed by a service control entity, which is a network element … |
| 1.3.6.1.4.1.9.9.630 | ciscoTelnetServerMIB | 3 | 34 | MIB module for displaying and configuring Telnet related features in a device. Telnet is a program to log into another computer o… |
| 1.3.6.1.4.1.9.9.631 | ciscoServiceControlLinkMIB | 3 | 21 | This MIB module provides information about the status and configuration of links used by service control entities. The link on a … |
| 1.3.6.1.4.1.9.9.632 | ciscoSmeMIB | 3 | 54 | MIB module to manage Storage Media Encryption (SME) service. SME is an encryption service provided by an encryption node residing… |
| 1.3.6.1.4.1.9.9.633 | ciscoIpSlaAutoMIB | 3 | 57 | This module defines the MIB for IP SLA Automation. IP SLA Automation consists of the following: 1. Use of grouping - Group is an … |
| 1.3.6.1.4.1.9.9.634 | ciscoServiceControlTpStatsMIB | 3 | 39 | This MIB provides information and statistics on the traffic processor(s) of a service control entity, which is a network element … |
| 1.3.6.1.4.1.9.9.635 | ciscoIpSlaJitterMIB | 3 | 57 | This MIB module defines templates for IP SLA operations of UDP Jitter and ICMP Jitter. The UDP Jitter operation is designed to me… |
| 1.3.6.1.4.1.9.9.636 | ciscoIpSlaEchoMIB | 3 | 71 | This MIB module defines the templates for IP SLA operations of ICMP echo, UDP echo and TCP connect. The ICMP echo operation measu… |
| 1.3.6.1.4.1.9.9.637 | ciscoServiceControlRdrMIB | 3 | 56 | This MIB module defines objects describing statistics and configuration relating to the Raw Data Record Formatter running on a se… |
| 1.3.6.1.4.1.9.9.638 | ciscoAgwMIB | 3 | 324 | This module manages Cisco's WiMAX ASN Gateway (ASN-GW). A WiMAX network supports wireless data communication through WiMAX radio … |
| 1.3.6.1.4.1.9.9.639 | ciscoOtnIfMIB | 3 | 137 | This MIB module defines the managed objects for physical layer characteristics of DWDM optical channel interfaces and performanc… |
| 1.3.6.1.4.1.9.9.640 | ciscoImageLicenseMgmtMIB | 3 | 31 | The MIB module for managing the running image level of a Cisco device. Cisco's licensing mechanism provides flexibility to run a … |
| 1.3.6.1.4.1.9.9.642 | ciscoBridgeDomainMIB | 3 | 24 | A bridge domain is one of the means by which it is possible to define a broadcast domain on a bridging device. It is an alternati… |
| 1.3.6.1.4.1.9.9.643 | ciscoTelepresenceMIB | 3 | 119 | The MIB module defines the managed objects for a Telepresence system. Telepresence refers to a set of technologies which allow a p… |
| 1.3.6.1.4.1.9.9.644 | ciscoTelepresenceCallMIB | 3 | 178 | The MIB module defines the managed objects for Telepresence calls. Telepresence refers to a set of technologies which allow a pers… |
| 1.3.6.1.4.1.9.9.645 | ciscoEtherExtMIB | 3 | 18 | The MIB module to describe generic objects for ethernet-like network interfaces. This MIB provides ethernet-like network interfac… |
| 1.3.6.1.4.1.9.9.646 | ciscoAonStatusMIB | 3 | 80 | This MIB module defines managed objects that facilitate the management of AON node. The information available through this MIB in… |
| 1.3.6.1.4.1.9.9.647 | ciscoGgsnExtMIB | 3 | 212 | This MIB module extends the CISCO-GGSN-MIB. This MIB module manages the Gateway GPRS Support Node (GGSN) devices. A GGSN device pr… |
| 1.3.6.1.4.1.9.9.648 | ciscoVirtualInterfaceMIB | 2 | 32 | The MIB module for creation and deletion of Virtual Interfaces and Virtual Interface Groups. In addition to this MIB, interface … |
| 1.3.6.1.4.1.9.9.650 | ciscoL4L7moduleRedundancyMIB | 3 | 71 | The L4-7 SLB devices are used for scaling websites, building web enabled applications, and migrating to web services. The followin… |
| 1.3.6.1.4.1.9.9.651 | ciscoCommonRolesExtMIB | 3 | 37 | A MIB Module for managing the roles that are common between access methods like Command Line Interface (CLI), SNMP and XML interf… |
| 1.3.6.1.4.1.9.9.652 | ciscoSwitchStatsMIB | 3 | 106 | The MIB module provides management information for configuration and monitoring of traffic statistics on Cisco's switching device… |
| 1.3.6.1.4.1.9.9.653 | ciscoAdmissionPolicyMIB | 3 | 36 | This MIB module defines managed objects that facilitate the management of policies upon host(s) admission to a network. The inform… |
| 1.3.6.1.4.1.9.9.654 | ciscoMabMIB | 3 | 20 | MIB module for monitoring and configuring MAC Authentication Bypass (MAB) feature in the system. MAC Auth Bypass feature provides… |
| 1.3.6.1.4.1.9.9.656 | ciscoAuthFrameworkMIB | 3 | 117 | MIB module for Authentication Framework in the system. Authentication Framework provides generic configurations for authenticatio… |
| 1.3.6.1.4.1.9.9.657 | ciscoSbcCallStatsMIB | 3 | 201 | The main purpose of this MIB is to define the statistics information for Session Border Controller application. The statistics ar… |
| 1.3.6.1.4.1.9.9.658 | ciscoSessBorderCtrlrEventMIB | 3 | 208 | The main purpose of this MIB is to define the SNMP notifications and alarms generated by Session Border Controller application an… |
| 1.3.6.1.4.1.9.9.660 | ciscoNportVirtualizationMIB | 3 | 19 | The MIB module for the management of N_port Virtualization or NPV within the framework of Cisco's N_port virtualization (NPV) Arc… |
| 1.3.6.1.4.1.9.9.661 | ciscoWan3gMIB | 3 | 378 | This MIB module provides network management support for Cisco cellular 3G WAN products. *** ABBREVIATIONS, ACRONYMS, AND SYMBOLS … |
| 1.3.6.1.4.1.9.9.662 | ciscoCbpTcMIB | 0 | 0 | This MIB module defines textual conventions used by the CISCO-CBP-BASE-CFG-MIB, CISCO-CBP-BASE-MON-MIB, and any MIB modules exten… |
| 1.3.6.1.4.1.9.9.663 | ciscoSwitchHardwareCapacityMIB | 3 | 141 | This MIB module defines the managed objects for hardware capacity of Cisco switching devices. The hardware capacity information c… |
| 1.3.6.1.4.1.9.9.664 | ciscoMmodalContactAppsMIB | 3 | 359 | The Cisco Unified Multi-Modal Contact Applications (MMCA) platform is a highly scalable, modular, extensible, open and secure pl… |
| 1.3.6.1.4.1.9.9.667 | ciscoServiceControllerMIB | 2 | 31 | This MIB module defines objects describing traffic controllers used by a service control entity. A service control entity is a ne… |
| 1.3.6.1.4.1.9.9.668 | ciscoP2PIfMIB | 3 | 16 | The Point to Point Interface MIB module. This MIB manages the generic objects for Serial link or SONET/SDH like point to point ne… |
| 1.3.6.1.4.1.9.9.669 | ciscoCdmaPdsnExtMIB | 3 | 178 | This MIB is an extension to the CISCO-CDMA-PDSN-MIB. A CDMA network supports wireless data communication through 3G CDMA radio acc… |
| 1.3.6.1.4.1.9.9.670 | ciscoReportIntervalTcMIB | 0 | 0 | CISCO-REPORT-INTERVAL-TC-MIB |
| 1.3.6.1.4.1.9.9.672 | ciscoMobilityTapMIB | 3 | 24 | This module manages Cisco's intercept feature for Mobility Gateway Products. This MIB is used along with CISCO-TAP2-MIB MIB to int… |
| 1.3.6.1.4.1.9.9.673 | ciscoFCoEMIB | 2 | 45 | This MIB module is for configuring and monitoring Fibre Channel over Ethernet (FCoE) related entities. This MIB defines the Virtu… |
| 1.3.6.1.4.1.9.9.679 | ciscoIeee8021CfmExtMIB | 3 | 55 | A MIB module for extending the IEEE8021-CFM-MIB and IEEE8021-CFM-V2-MIB to add objects which provide additional information about… |
| 1.3.6.1.4.1.9.9.680 | ciscoNhrpExtMIB | 3 | 36 | This MIB module is an extension of the NHRP MIB module as defined in RFC 2677. It defines notifications associated with critical … |
| 1.3.6.1.4.1.9.9.683 | ciscoEnergywiseMIB | 3 | 162 | The MIB is used to manage and optimize power usage in networks. Cisco EnergyWise is a specification of data, discovery and protoco… |
| 1.3.6.1.4.1.9.9.686 | ciscoLwappInterfaceMIB | 3 | 27 | ciscoLwappInterfaceMIB MODULE-IDENTITY LAST-UPDATED "200901090000Z" ORGANIZATION "Cisco Systems Inc." CONTACT-INFO "Cisco Syste… |
| 1.3.6.1.4.1.9.9.688 | ciscoFlowMonitorTcMIB | 0 | 0 | This MIB module defines textual conventions used by the MIB modules defining objects describing flow monitoring. GLOSSARY ========… |
| 1.3.6.1.4.1.9.9.689 | ciscoSlbDfpMIB | 3 | 22 | This MIB reports the congestion status of the real server. A server can be in congested state due to high memory consumption, hig… |
| 1.3.6.1.4.1.9.9.690 | ciscoMobilePolicyChargingControlMIB | 3 | 143 | Mobile PCC Infrastructure built on top of Policy Shim Layer, is a common interface to send and receive PCC related messages for a… |
| 1.3.6.1.4.1.9.9.691 | ciscoEthernetFabricExtenderMIB | 3 | 23 | The MIB module for configuring one or more fabric extenders to connect into a core switch. Since fabric extenders might not be m… |
| 1.3.6.1.4.1.9.9.692 | ciscoFlowMonitorMIB | 4 | 195 | This MIB module defines objects that describe flow monitoring. A typical application of this MIB module will facilitate monitorin… |
| 1.3.6.1.4.1.9.9.693 | ciscoServiceControlAttackMIB | 3 | 55 | This MIB provides data related to different types of attacks detected by a service control entity. A service control entity is a … |
| 1.3.6.1.4.1.9.9.694 | ciscoCtsTcMIB | 0 | 0 | This module defines the textual conventions used within Cisco Trusted Security framework. |
| 1.3.6.1.4.1.9.9.695 | ciscoGtcapMIB | 3 | 194 | The MIB for Transaction Capabilities(TCAP) messages transported over Signalling System No. 7 (SS7) Network via Cisco IP Transfer P… |
| 1.3.6.1.4.1.9.9.696 | ciscoBootHwDiagsMIB | 3 | 22 | This MIB is used to configure those devices that support boot-time hardware diagnostics. It provides the reports about the respe… |
| 1.3.6.1.4.1.9.9.697 | ciscoIpCbrMetricsMIB | 4 | 42 | This MIB module defines objects that describe the a set of metrics used to measure the quality of a IP CBR traffic flow. An IP CB… |
| 1.3.6.1.4.1.9.9.698 | ciscoObmiMIB | 3 | 60 | The On-Board Management Interface (OBMI) provides an out-of-band communications channel (in Cisco terms: a console port), that is… |
| 1.3.6.1.4.1.9.9.699 | ciscoMdiMetricsMIB | 4 | 46 | This MIB module defines objects that describe the Media Delivery Index (MDI). The MDI [RFC4445] measurement describes the qualit… |
| 1.3.6.1.4.1.9.9.700 | ciscoCableL2vpnMIB | 3 | 28 | This MIB module defines managed objects that facilitate the management of Cisco devices complying to the DOCSIS L2VPN Feature for… |
| 1.3.6.1.4.1.9.9.701 | ciscoSeuMitigationMIB | 3 | 51 | This MIB reports the status of non-automatic and automatic, rate-adaptive Single Event Upset (SEU) mitigation algorithms and adju… |
| 1.3.6.1.4.1.9.9.702 | ciscoSanBaseSvcMIB | 3 | 57 | Common MIB module to manage services in Storage Area Network (SAN). Service is deployed on service nodes on multiple switches fo… |
| 1.3.6.1.4.1.9.9.703 | ciscoRtpMetricsMIB | 4 | 61 | This MIB module defines objects that describe the quality metrics of RTP streams, similar to those described by an RTCP Receiver … |
| ... | ||||