This MIB module defines objects describing statistics and
configuration relating to the Raw Data Record Formatter running
on a service control entity.
The Raw Data Record (RDR) formatter is a component implemented
by the service control entity that gathers raw data records
produced by the entity and delivers them to external entities
as reports. The external entities are called RDR destinations
or RDR collectors. The RDR formatter can be configured to send
reports to one or multiple destinations.
RDR formatter can group RDRs into potentially four categories.
RDR mapping to the categories is done by the client application
or the user and reflects different logical destinations or
purposes. For example the application may map Quota related
RDRs to category 1, and Transaction related RDRs to category 2.
The user can configure these categories to different
destinations and assign them with different priorities. Each
category has a separate queue for forwarding the RDRs and has
seperate counters for gathering of statistics (sent, dropped,
queued etc.). An RDR can belong to any one of the category as
chosen by the user or client application.
The RDR formatter supports multiple destinations identified by
IP address and a port number. Each destination is assigned with
a priority for each of the categories. Priority is a number in
the range of 1-100, with 100 being the highest priority. The
priorities are effective only when the formatter is in
forwarding mode 'Redundancy' and are configured during
destination configuration (while assigning the destination with
categories). For example we have destination A configured with
category 1 which is configured with priority 100, destination B
configured with category 1 and priority 80 and destination C
with category 1 and priority 90. When in redundancy mode the
formatter will set the active destination for a category to be
the destination with the highest priority. For category 1 the
active destination will be A. If destination A goes down then
the next destination selected by the formatter as active is
destination C.
Parsed from file CISCO-SERVICE-CONTROL-RDR-MIB.mib
Module: CISCO-SERVICE-CONTROL-RDR-MIB
This MIB module defines objects describing statistics and
configuration relating to the Raw Data Record Formatter running
on a service control entity.
The Raw Data Record (RDR) formatter is a component implemented
by the service control entity that gathers raw data records
produced by the entity and delivers them to external entities
as reports. The external entities are called RDR destinations
or RDR collectors. The RDR formatter can be configured to send
reports to one or multiple destinations.
RDR formatter can group RDRs into potentially four categories.
RDR mapping to the categories is done by the client application
or the user and reflects different logical destinations or
purposes. For example the application may map Quota related
RDRs to category 1, and Transaction related RDRs to category 2.
The user can configure these categories to different
destinations and assign them with different priorities. Each
category has a separate queue for forwarding the RDRs and has
seperate counters for gathering of statistics (sent, dropped,
queued etc.). An RDR can belong to any one of the category as
chosen by the user or client application.
The RDR formatter supports multiple destinations identified by
IP address and a port number. Each destination is assigned with
a priority for each of the categories. Priority is a number in
the range of 1-100, with 100 being the highest priority. The
priorities are effective only when the formatter is in
forwarding mode 'Redundancy' and are configured during
destination configuration (while assigning the destination with
categories). For example we have destination A configured with
category 1 which is configured with priority 100, destination B
configured with category 1 and priority 80 and destination C
with category 1 and priority 90. When in redundancy mode the
formatter will set the active destination for a category to be
the destination with the highest priority. For category 1 the
active destination will be A. If destination A goes down then
the next destination selected by the formatter as active is
destination C.
Parsed from file CISCO-SERVICE-CONTROL-RDR-MIB.my.txt
Company: None
Module: CISCO-SERVICE-CONTROL-RDR-MIB
This MIB module defines objects describing statistics and
configuration relating to the Raw Data Record Formatter running
on a service control entity.
The Raw Data Record (RDR) formatter is a component implemented
by the service control entity that gathers raw data records
produced by the entity and delivers them to external entities
as reports. The external entities are called RDR destinations
or RDR collectors. The RDR formatter can be configured to send
reports to one or multiple destinations.
RDR formatter can group RDRs into potentially four categories.
RDR mapping to the categories is done by the client application
or the user and reflects different logical destinations or
purposes. For example the application may map Quota related
RDRs to category 1, and Transaction related RDRs to category 2.
The user can configure these categories to different
destinations and assign them with different priorities. Each
category has a separate queue for forwarding the RDRs and has
seperate counters for gathering of statistics (sent, dropped,
queued etc.). An RDR can belong to any one of the category as
chosen by the user or client application.
The RDR formatter supports multiple destinations identified by
IP address and a port number. Each destination is assigned with
a priority for each of the categories. Priority is a number in
the range of 1-100, with 100 being the highest priority. The
priorities are effective only when the formatter is in
forwarding mode 'Redundancy' and are configured during
destination configuration (while assigning the destination with
categories). For example we have destination A configured with
category 1 which is configured with priority 100, destination B
configured with category 1 and priority 80 and destination C
with category 1 and priority 90. When in redundancy mode the
formatter will set the active destination for a category to be
the destination with the highest priority. For category 1 the
active destination will be A. If destination A goes down then
the next destination selected by the formatter as active is
destination C.
ciscoServiceControlRdrMIB MODULE-IDENTITY LAST-UPDATED "200708140000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "This MIB module defines objects describing statistics and configuration relating to the Raw Data Record Formatter running on a service control entity. The Raw Data Record (RDR) formatter is a component implemented by the service control entity that gathers raw data records produced by the entity and delivers them to external entities as reports. The external entities are called RDR destinations or RDR collectors. The RDR formatter can be configured to send reports to one or multiple destinations. RDR formatter can group RDRs into potentially four categories. RDR mapping to the categories is done by the client application or the user and reflects different logical destinations or purposes. For example the application may map Quota related RDRs to category 1, and Transaction related RDRs to category 2. The user can configure these categories to different destinations and assign them with different priorities. Each category has a separate queue for forwarding the RDRs and has seperate counters for gathering of statistics (sent, dropped, queued etc.). An RDR can belong to any one of the category as chosen by the user or client application. The RDR formatter supports multiple destinations identified by IP address and a port number. Each destination is assigned with a priority for each of the categories. Priority is a number in the range of 1-100, with 100 being the highest priority. The priorities are effective only when the formatter is in forwarding mode 'Redundancy' and are configured during destination configuration (while assigning the destination with categories). For example we have destination A configured with category 1 which is configured with priority 100, destination B configured with category 1 and priority 80 and destination C with category 1 and priority 90. When in redundancy mode the formatter will set the active destination for a category to be the destination with the highest priority. For category 1 the active destination will be A. If destination A goes down then the next destination selected by the formatter as active is destination C." REVISION "200708140000Z" DESCRIPTION "Initial version of this MIB module" ::= { ciscoMgmt 637 }
ciscoServiceControlRdrMIB OBJECT IDENTIFIER ::= { ciscoMgmt 637 }
Vendor: Cisco
Module: CISCO-SERVICE-CONTROL-RDR-MIB
[Automatically extracted from oidview.com]
ciscoServiceControlRdrMIB MODULE-IDENTITY LAST-UPDATED "200708140000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "This MIB module defines objects describing statistics and configuration relating to the Raw Data Record Formatter running on a service control entity. The Raw Data Record (RDR) formatter is a component implemented by the service control entity that gathers raw data records produced by the entity and delivers them to external entities as reports. The external entities are called RDR destinations or RDR collectors. The RDR formatter can be configured to send reports to one or multiple destinations. RDR formatter can group RDRs into potentially four categories. RDR mapping to the categories is done by the client application or the user and reflects different logical destinations or purposes. For example the application may map Quota related RDRs to category 1, and Transaction related RDRs to category 2. The user can configure these categories to different destinations and assign them with different priorities. Each category has a separate queue for forwarding the RDRs and has seperate counters for gathering of statistics (sent, dropped, queued etc.). An RDR can belong to any one of the category as chosen by the user or client application. The RDR formatter supports multiple destinations identified by IP address and a port number. Each destination is assigned with a priority for each of the categories. Priority is a number in the range of 1-100, with 100 being the highest priority. The priorities are effective only when the formatter is in forwarding mode 'Redundancy' and are configured during destination configuration (while assigning the destination with categories). For example we have destination A configured with category 1 which is configured with priority 100, destination B configured with category 1 and priority 80 and destination C with category 1 and priority 90. When in redundancy mode the formatter will set the active destination for a category to be the destination with the highest priority. For category 1 the active destination will be A. If destination A goes down then the next destination selected by the formatter as active is destination C." REVISION "200708140000Z" DESCRIPTION "Initial version of this MIB module" ::= { ciscoMgmt 637 }
ciscoServiceControlRdrMIB MODULE-IDENTITY LAST-UPDATED "200708140000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "This MIB module defines objects describing statistics and configuration relating to the Raw Data Record Formatter running on a service control entity. The Raw Data Record (RDR) formatter is a component implemented by the service control entity that gathers raw data records produced by the entity and delivers them to external entities as reports. The external entities are called RDR destinations or RDR collectors. The RDR formatter can be configured to send reports to one or multiple destinations. RDR formatter can group RDRs into potentially four categories. RDR mapping to the categories is done by the client application or the user and reflects different logical destinations or purposes. For example the application may map Quota related RDRs to category 1, and Transaction related RDRs to category 2. The user can configure these categories to different destinations and assign them with different priorities. Each category has a separate queue for forwarding the RDRs and has seperate counters for gathering of statistics (sent, dropped, queued etc.). An RDR can belong to any one of the category as chosen by the user or client application. The RDR formatter supports multiple destinations identified by IP address and a port number. Each destination is assigned with a priority for each of the categories. Priority is a number in the range of 1-100, with 100 being the highest priority. The priorities are effective only when the formatter is in forwarding mode 'Redundancy' and are configured during destination configuration (while assigning the destination with categories). For example we have destination A configured with category 1 which is configured with priority 100, destination B configured with category 1 and priority 80 and destination C with category 1 and priority 90. When in redundancy mode the formatter will set the active destination for a category to be the destination with the highest priority. For category 1 the active destination will be A. If destination A goes down then the next destination selected by the formatter as active is destination C." REVISION "200708140000Z" DESCRIPTION "Initial version of this MIB module" ::= { ciscoMgmt 637 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.637.0 | ciscoSCRdrMIBNotifs | 6 | 6 | None |
| 1.3.6.1.4.1.9.9.637.1 | ciscoSCRdrMIBObjects | 6 | 40 | None |
| 1.3.6.1.4.1.9.9.637.2 | ciscoSCRdrMIBConform | 2 | 7 | 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.589 | ciscoGslbSystemMIB | 3 | 103 | This MIB module defines objects for network and system information of Global Server Load Balancer(GSLB) as a network device. A G… |
| 1.3.6.1.4.1.9.9.590 | ciscoCvpMIB | 3 | 255 | The Cisco Unified Customer Voice Portal (CVP) application integrates with both traditional time-division multiplexing (TDM) and I… |
| 1.3.6.1.4.1.9.9.592 | ciscoPrefPathMIB | 3 | 56 | The MIB module for the management of preferred path. This MIB enables managers to configure and monitor Preferred Path parameters.… |
| 1.3.6.1.4.1.9.9.593 | ciscoFcSdvMIB | 3 | 28 | This MIB instrumentation is for managing Fibre Channel (FC) SAN Device Virtualization (SDV) solution on Cisco Fibre Channel devic… |
| 1.3.6.1.4.1.9.9.594 | ciscoApplicationAccelerationMIB | 3 | 37 | This is a MIB for managing Application Acceleration System(s). This MIB includes instrumentation for providing the performance st… |
| 1.3.6.1.4.1.9.9.595 | ciscoGslbDnsMIB | 3 | 165 | The MIB defines objects for status and statistics information of DNS related operations of Global Server Load Balancer(GSLB). Th… |
| 1.3.6.1.4.1.9.9.597 | ciscoContentServicesMIB | 3 | 349 | Content Service is a capability to examine IP/TCP/UDP headers, payload and enable billing based on the content being provided. Ab… |
| 1.3.6.1.4.1.9.9.598 | ciscoLwappAAAMIB | 3 | 73 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC), that terminate the Light Weigh… |
| 1.3.6.1.4.1.9.9.599 | ciscoLwappDot11ClientMIB | 4 | 49 | 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.600 | ciscoGslbHealthMonMIB | 3 | 90 | The MIB defines objects related to global keepalive properties in GSLB devices. It contains the tables for keep alive configurat… |
| 1.3.6.1.4.1.9.9.601 | ciscoResilientEthernetProtocolMIB | 3 | 77 | This MIB module defines objects required for managing Resilient Ethernet Protocol (REP). Resilient Ethernet Protocol (REP) is a C… |
| 1.3.6.1.4.1.9.9.602 | ciscoPacketCaptureMIB | 3 | 103 | The MIB module for the management of packet capture feature. |
| 1.3.6.1.4.1.9.9.603 | ciscoThreatMitigationServiceMIB | 3 | 68 | This MIB provides management information about the Threat Mitigation Service(TMS) entity named 'Consumer'. TMS is part of Cisco's… |
| 1.3.6.1.4.1.9.9.604 | cdot1CfmMIB | 3 | 166 | Connectivity Fault Management module for managing IEEE 802.1ag |
| 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.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.655 | ciscoDigitalMediaSystemsMIB | 3 | 195 | Acronyms and Definitions The following acronyms and terms are used in this document: DMS: Digital Media Systems DAM: Digital As… |
| 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… |
| ... | ||||