The Cisco Unified Customer Voice Portal (CVP) application
integrates with both traditional time-division multiplexing
(TDM) and IP-based contact centers to provide an unparalleled
call management and call treatment solution with a self-
service, speech-enabled Interactive Voice Rresponse (IVR)
option that can use information available to customers on the
corporate Web server.
With support for automated speech recognition (ASR) and text-
to-speech (TTS) capabilities, callers can obtain personalized
answers to increasingly complex questions and can conduct
business in new and innovative ways ?- all without the costs
of interacting with a live agent.
CVP is a distributed, self-service IVR application. The
solution is comprised of a set of distinct services: each
performs a specific function. The services are loosely
coupled, which aides its distributed nature, and yet they are
tightly integrated. Each service provides a core function
and is dependent upon the other services to perform that
function.
A single CVP server may have one or more services installed
on a single server: even in the smallest deployment scenarios,
there will be at least two servers
Voice XML (VXML) server. The call server, whether it is a
single physical server or a virtual set of servers, will
include the SIP service, the IVR service and in many cases,
the ICM service. Environments desiring the use of the H.323
protocol will have the H.323 service either exclusively or in
concert with the SIP service available on the call server.
The server providing VXML services will have the VXML server
(which executes the IVR scripts, plays prompts and collects
digits) and the VXML service which provides the interface
between the other CVP services and the VXML server. A
reporting server houses a database management system and the
CVP reporting service which receives events from other CVP
services and writes data to the database. The number of
servers that are part of the solution will scale to the
expected capacity for that deployment.
For many deployments, CVP works in concert with the Cisco
Unified Intelligent Contact Management (ICM) Enterprise and/or
the Cisco Unified Contact Center Enterprise contact management
systems. In this deployment scenario, CVP acts as a self-
service and IVR platform and interfaces with the ICM for
subsequent call routing, typically to a call center agent (a
human resource tasked with answering inbound calls and
providing services to callers). Using the aforementioned call
control protocols
these devices to switch the calls to the desired destination.
The Cisco Unified Customer Voice Portal (CVP) Management
Information Base (MIB) module defines management
instrumentation for CVP services. Each distinct CVP service
exposes instrumentation related to its specific function.
The bulk of this instrumentation is run-time statistics that
provide insight into the health, performance and capacity
utilization of the CVP solution. Notifications are also a
key component of this instrumentation. This MIB also defines
a notification format that offers descriptive objects as well
as objects that ease the task of correlating events at the
management station.
The MIB is structured such that at the highest level is a
single generic table which enumerates the installed CVP
services and provides a description of each as well as a
real-time status. The index of this table is used to relate
the service entry to an entry in a table of additional
instrumentation that is specific to that CVP service type.
There are also several groups of objects that are exposed on
each CVP server regardless of the services installed.
DEFINITION OF TERMS AND ACRONYMS
CVP Customer Voice Portal
GED-125 A messaging protocol that extends an interface to a
Interactive Voice Response (IVR) (AKA Voice Response
Unit (VRU)) device. The protocol allows for basic
call control and running scripts on the IVR to play
prompts and collect user input.
IVR Interactive Voice Response
JVM Java Virtual Machine
OAMP Operations, Administration, Maintenance and
Provisioning
RTP Real-time Transport Protocol
SIP Session Initiation Protocol
VRU Voice Response Unit
Parsed from file CISCO-CVP-MIB.mib
Module: CISCO-CVP-MIB
The Cisco Unified Customer Voice Portal (CVP) application
integrates with both traditional time-division multiplexing
(TDM) and IP-based contact centers to provide an unparalleled
call management and call treatment solution with a self-
service, speech-enabled Interactive Voice Rresponse (IVR)
option that can use information available to customers on the
corporate Web server.
With support for automated speech recognition (ASR) and text-
to-speech (TTS) capabilities, callers can obtain personalized
answers to increasingly complex questions and can conduct
business in new and innovative ways ?- all without the costs
of interacting with a live agent.
CVP is a distributed, self-service IVR application. The
solution is comprised of a set of distinct services; each
performs a specific function. The services are loosely
coupled, which aides its distributed nature, and yet they are
tightly integrated. Each service provides a core function
and is dependent upon the other services to perform that
function.
A single CVP server may have one or more services installed
on a single server; even in the smallest deployment scenarios,
there will be at least two servers
Voice XML (VXML) server. The call server, whether it is a
single physical server or a virtual set of servers, will
include the SIP service, the IVR service and in many cases,
the ICM service. Environments desiring the use of the H.323
protocol will have the H.323 service either exclusively or in
concert with the SIP service available on the call server.
The server providing VXML services will have the VXML server
(which executes the IVR scripts, plays prompts and collects
digits) and the VXML service which provides the interface
between the other CVP services and the VXML server. A
reporting server houses a database management system and the
CVP reporting service which receives events from other CVP
services and writes data to the database. The number of
servers that are part of the solution will scale to the
expected capacity for that deployment.
For many deployments, CVP works in concert with the Cisco
Unified Intelligent Contact Management (ICM) Enterprise and/or
the Cisco Unified Contact Center Enterprise contact management
systems. In this deployment scenario, CVP acts as a self-
service and IVR platform and interfaces with the ICM for
subsequent call routing, typically to a call center agent (a
human resource tasked with answering inbound calls and
providing services to callers). Using the aforementioned call
control protocols
these devices to switch the calls to the desired destination.
The Cisco Unified Customer Voice Portal (CVP) Management
Information Base (MIB) module defines management
instrumentation for CVP services. Each distinct CVP service
exposes instrumentation related to its specific function.
The bulk of this instrumentation is run-time statistics that
provide insight into the health, performance and capacity
utilization of the CVP solution. Notifications are also a
key component of this instrumentation. This MIB also defines
a notification format that offers descriptive objects as well
as objects that ease the task of correlating events at the
management station.
The MIB is structured such that at the highest level is a
single generic table which enumerates the installed CVP
services and provides a description of each as well as a
real-time status. The index of this table is used to relate
the service entry to an entry in a table of additional
instrumentation that is specific to that CVP service type.
There are also several groups of objects that are exposed on
each CVP server regardless of the services installed.
DEFINITION OF TERMS AND ACRONYMS
CVP Customer Voice Portal
GED-125 A messaging protocol that extends an interface to a
Interactive Voice Response (IVR) (AKA Voice Response
Unit (VRU)) device. The protocol allows for basic
call control and running scripts on the IVR to play
prompts and collect user input.
IVR Interactive Voice Response
JVM Java Virtual Machine
OAMP Operations, Administration, Maintenance and
Provisioning
RTP Real-time Transport Protocol
SIP Session Initiation Protocol
VRU Voice Response Unit
Parsed from file CISCO-CVP-MIB.my.txt
Company: None
Module: CISCO-CVP-MIB
The Cisco Unified Customer Voice Portal (CVP) application
integrates with both traditional time-division multiplexing
(TDM) and IP-based contact centers to provide an unparalleled
call management and call treatment solution with a self-
service, speech-enabled Interactive Voice Rresponse (IVR)
option that can use information available to customers on the
corporate Web server.
With support for automated speech recognition (ASR) and text-
to-speech (TTS) capabilities, callers can obtain personalized
answers to increasingly complex questions and can conduct
business in new and innovative ways ?- all without the costs
of interacting with a live agent.
CVP is a distributed, self-service IVR application. The
solution is comprised of a set of distinct services; each
performs a specific function. The services are loosely
coupled, which aides its distributed nature, and yet they are
tightly integrated. Each service provides a core function
and is dependent upon the other services to perform that
function.
A single CVP server may have one or more services installed
on a single server; even in the smallest deployment scenarios,
there will be at least two servers
Voice XML (VXML) server. The call server, whether it is a
single physical server or a virtual set of servers, will
include the SIP service, the IVR service and in many cases,
the ICM service. Environments desiring the use of the H.323
protocol will have the H.323 service either exclusively or in
concert with the SIP service available on the call server.
The server providing VXML services will have the VXML server
(which executes the IVR scripts, plays prompts and collects
digits) and the VXML service which provides the interface
between the other CVP services and the VXML server. A
reporting server houses a database management system and the
CVP reporting service which receives events from other CVP
services and writes data to the database. The number of
servers that are part of the solution will scale to the
expected capacity for that deployment.
For many deployments, CVP works in concert with the Cisco
Unified Intelligent Contact Management (ICM) Enterprise and/or
the Cisco Unified Contact Center Enterprise contact management
systems. In this deployment scenario, CVP acts as a self-
service and IVR platform and interfaces with the ICM for
subsequent call routing, typically to a call center agent (a
human resource tasked with answering inbound calls and
providing services to callers). Using the aforementioned call
control protocols
these devices to switch the calls to the desired destination.
The Cisco Unified Customer Voice Portal (CVP) Management
Information Base (MIB) module defines management
instrumentation for CVP services. Each distinct CVP service
exposes instrumentation related to its specific function.
The bulk of this instrumentation is run-time statistics that
provide insight into the health, performance and capacity
utilization of the CVP solution. Notifications are also a
key component of this instrumentation. This MIB also defines
a notification format that offers descriptive objects as well
as objects that ease the task of correlating events at the
management station.
The MIB is structured such that at the highest level is a
single generic table which enumerates the installed CVP
services and provides a description of each as well as a
real-time status. The index of this table is used to relate
the service entry to an entry in a table of additional
instrumentation that is specific to that CVP service type.
There are also several groups of objects that are exposed on
each CVP server regardless of the services installed.
DEFINITION OF TERMS AND ACRONYMS
CVP Customer Voice Portal
GED-125 A messaging protocol that extends an interface to a
Interactive Voice Response (IVR) (AKA Voice Response
Unit (VRU)) device. The protocol allows for basic
call control and running scripts on the IVR to play
prompts and collect user input.
IVR Interactive Voice Response
JVM Java Virtual Machine
OAMP Operations, Administration, Maintenance and
Provisioning
RTP Real-time Transport Protocol
SIP Session Initiation Protocol
VRU Voice Response Unit
ciscoCvpMIB MODULE-IDENTITY LAST-UPDATED "200710310000Z" 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 "The Cisco Unified Customer Voice Portal (CVP) application integrates with both traditional time-division multiplexing (TDM) and IP-based contact centers to provide an unparalleled call management and call treatment solution with a self- service, speech-enabled Interactive Voice Rresponse (IVR) option that can use information available to customers on the corporate Web server. With support for automated speech recognition (ASR) and text- to-speech (TTS) capabilities, callers can obtain personalized answers to increasingly complex questions and can conduct business in new and innovative ways ?- all without the costs of interacting with a live agent. CVP is a distributed, self-service IVR application. The solution is comprised of a set of distinct services: each performs a specific function. The services are loosely coupled, which aides its distributed nature, and yet they are tightly integrated. Each service provides a core function and is dependent upon the other services to perform that function. A single CVP server may have one or more services installed on a single server: even in the smallest deployment scenarios, there will be at least two servers Voice XML (VXML) server. The call server, whether it is a single physical server or a virtual set of servers, will include the SIP service, the IVR service and in many cases, the ICM service. Environments desiring the use of the H.323 protocol will have the H.323 service either exclusively or in concert with the SIP service available on the call server. The server providing VXML services will have the VXML server (which executes the IVR scripts, plays prompts and collects digits) and the VXML service which provides the interface between the other CVP services and the VXML server. A reporting server houses a database management system and the CVP reporting service which receives events from other CVP services and writes data to the database. The number of servers that are part of the solution will scale to the expected capacity for that deployment. For many deployments, CVP works in concert with the Cisco Unified Intelligent Contact Management (ICM) Enterprise and/or the Cisco Unified Contact Center Enterprise contact management systems. In this deployment scenario, CVP acts as a self- service and IVR platform and interfaces with the ICM for subsequent call routing, typically to a call center agent (a human resource tasked with answering inbound calls and providing services to callers). Using the aforementioned call control protocols these devices to switch the calls to the desired destination. The Cisco Unified Customer Voice Portal (CVP) Management Information Base (MIB) module defines management instrumentation for CVP services. Each distinct CVP service exposes instrumentation related to its specific function. The bulk of this instrumentation is run-time statistics that provide insight into the health, performance and capacity utilization of the CVP solution. Notifications are also a key component of this instrumentation. This MIB also defines a notification format that offers descriptive objects as well as objects that ease the task of correlating events at the management station. The MIB is structured such that at the highest level is a single generic table which enumerates the installed CVP services and provides a description of each as well as a real-time status. The index of this table is used to relate the service entry to an entry in a table of additional instrumentation that is specific to that CVP service type. There are also several groups of objects that are exposed on each CVP server regardless of the services installed. DEFINITION OF TERMS AND ACRONYMS CVP Customer Voice Portal GED-125 A messaging protocol that extends an interface to a Interactive Voice Response (IVR) (AKA Voice Response Unit (VRU)) device. The protocol allows for basic call control and running scripts on the IVR to play prompts and collect user input. IVR Interactive Voice Response JVM Java Virtual Machine OAMP Operations, Administration, Maintenance and Provisioning RTP Real-time Transport Protocol SIP Session Initiation Protocol VRU Voice Response Unit" REVISION "200710310000Z" DESCRIPTION "Added ccvpSipVideoTableGroup, ccvpIvrVideoTableGroup and ccvpIcmVideoTableGroup to include Video statistics." REVISION "200610060000Z" DESCRIPTION "Added objects: ccvpLicPortUsageWarning and ccvpLicPortUsageCritical to expose the current threshold settings for the port usage states of 'warning' and 'critical' respectively. Also added UNITS clause 'minutes' to ccvpServiceIntPeriod." REVISION "200605191200Z" DESCRIPTION "This is the initial version of this MIB module." ::= { ciscoMgmt 590 }
ciscoCvpMIB OBJECT IDENTIFIER ::= { ciscoMgmt 590 }
Vendor: Cisco
Module: CISCO-CVP-MIB
[Automatically extracted from oidview.com]
ciscoCvpMIB MODULE-IDENTITY LAST-UPDATED "201109220000Z" 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 "The Cisco Unified Customer Voice Portal (CVP) application integrates with both traditional time-division multiplexing (TDM) and IP-based contact centers to provide an unparalleled call management and call treatment solution with a self- service, speech-enabled Interactive Voice Rresponse (IVR) option that can use information available to customers on the corporate Web server. With support for automated speech recognition (ASR) and text- to-speech (TTS) capabilities, callers can obtain personalized answers to increasingly complex questions and can conduct business in new and innovative ways ?- all without the costs of interacting with a live agent. CVP is a distributed, self-service IVR application. The solution is comprised of a set of distinct services; each performs a specific function. The services are loosely coupled, which aides its distributed nature, and yet they are tightly integrated. Each service provides a core function and is dependent upon the other services to perform that function. A single CVP server may have one or more services installed on a single server; even in the smallest deployment scenarios, there will be at least two servers Voice XML (VXML) server. The call server, whether it is a single physical server or a virtual set of servers, will include the SIP service, the IVR service and in many cases, the ICM service. Environments desiring the use of the H.323 protocol will have the H.323 service either exclusively or in concert with the SIP service available on the call server. The server providing VXML services will have the VXML server (which executes the IVR scripts, plays prompts and collects digits) and the VXML service which provides the interface between the other CVP services and the VXML server. A reporting server houses a database management system and the CVP reporting service which receives events from other CVP services and writes data to the database. The number of servers that are part of the solution will scale to the expected capacity for that deployment. For many deployments, CVP works in concert with the Cisco Unified Intelligent Contact Management (ICM) Enterprise and/or the Cisco Unified Contact Center Enterprise contact management systems. In this deployment scenario, CVP acts as a self- service and IVR platform and interfaces with the ICM for subsequent call routing, typically to a call center agent (a human resource tasked with answering inbound calls and providing services to callers). Using the aforementioned call control protocols these devices to switch the calls to the desired destination. The Cisco Unified Customer Voice Portal (CVP) Management Information Base (MIB) module defines management instrumentation for CVP services. Each distinct CVP service exposes instrumentation related to its specific function. The bulk of this instrumentation is run-time statistics that provide insight into the health, performance and capacity utilization of the CVP solution. Notifications are also a key component of this instrumentation. This MIB also defines a notification format that offers descriptive objects as well as objects that ease the task of correlating events at the management station. The MIB is structured such that at the highest level is a single generic table which enumerates the installed CVP services and provides a description of each as well as a real-time status. The index of this table is used to relate the service entry to an entry in a table of additional instrumentation that is specific to that CVP service type. There are also several groups of objects that are exposed on each CVP server regardless of the services installed. DEFINITION OF TERMS AND ACRONYMS CVP Customer Voice Portal GED-125 A messaging protocol that extends an interface to a Interactive Voice Response (IVR) (AKA Voice Response Unit (VRU)) device. The protocol allows for basic call control and running scripts on the IVR to play prompts and collect user input. IVR Interactive Voice Response JVM Java Virtual Machine OAMP Operations, Administration, Maintenance and Provisioning RTP Real-time Transport Protocol SIP Session Initiation Protocol VRU Voice Response Unit" REVISION "201109220000Z" DESCRIPTION "Added ccvpSipIntPostCallAnswered, ccvpSipIntWhisperAnswered,ccvpSipIntWhisperFailed,ccvpSipIntGree tingAnswered , ccvpSipIntGreetingFailed" REVISION "200710310000Z" DESCRIPTION "Added ccvpSipVideoTableGroup, ccvpIvrVideoTableGroup and ccvpIcmVideoTableGroup to include Video statistics." REVISION "200610060000Z" DESCRIPTION "Added objects: ccvpLicPortUsageWarning and ccvpLicPortUsageCritical to expose the current threshold settings for the port usage states of 'warning' and 'critical' respectively. Also added UNITS clause 'minutes' to ccvpServiceIntPeriod." REVISION "200605191200Z" DESCRIPTION "This is the initial version of this MIB module." ::= { ciscoMgmt 590 }
ciscoCvpMIB MODULE-IDENTITY LAST-UPDATED "201109220000Z" 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 "The Cisco Unified Customer Voice Portal (CVP) application integrates with both traditional time-division multiplexing (TDM) and IP-based contact centers to provide an unparalleled call management and call treatment solution with a self- service, speech-enabled Interactive Voice Rresponse (IVR) option that can use information available to customers on the corporate Web server. With support for automated speech recognition (ASR) and text- to-speech (TTS) capabilities, callers can obtain personalized answers to increasingly complex questions and can conduct business in new and innovative ways ?- all without the costs of interacting with a live agent. CVP is a distributed, self-service IVR application. The solution is comprised of a set of distinct services; each performs a specific function. The services are loosely coupled, which aides its distributed nature, and yet they are tightly integrated. Each service provides a core function and is dependent upon the other services to perform that function. A single CVP server may have one or more services installed on a single server; even in the smallest deployment scenarios, there will be at least two servers Voice XML (VXML) server. The call server, whether it is a single physical server or a virtual set of servers, will include the SIP service, the IVR service and in many cases, the ICM service. Environments desiring the use of the H.323 protocol will have the H.323 service either exclusively or in concert with the SIP service available on the call server. The server providing VXML services will have the VXML server (which executes the IVR scripts, plays prompts and collects digits) and the VXML service which provides the interface between the other CVP services and the VXML server. A reporting server houses a database management system and the CVP reporting service which receives events from other CVP services and writes data to the database. The number of servers that are part of the solution will scale to the expected capacity for that deployment. For many deployments, CVP works in concert with the Cisco Unified Intelligent Contact Management (ICM) Enterprise and/or the Cisco Unified Contact Center Enterprise contact management systems. In this deployment scenario, CVP acts as a self- service and IVR platform and interfaces with the ICM for subsequent call routing, typically to a call center agent (a human resource tasked with answering inbound calls and providing services to callers). Using the aforementioned call control protocols these devices to switch the calls to the desired destination. The Cisco Unified Customer Voice Portal (CVP) Management Information Base (MIB) module defines management instrumentation for CVP services. Each distinct CVP service exposes instrumentation related to its specific function. The bulk of this instrumentation is run-time statistics that provide insight into the health, performance and capacity utilization of the CVP solution. Notifications are also a key component of this instrumentation. This MIB also defines a notification format that offers descriptive objects as well as objects that ease the task of correlating events at the management station. The MIB is structured such that at the highest level is a single generic table which enumerates the installed CVP services and provides a description of each as well as a real-time status. The index of this table is used to relate the service entry to an entry in a table of additional instrumentation that is specific to that CVP service type. There are also several groups of objects that are exposed on each CVP server regardless of the services installed. DEFINITION OF TERMS AND ACRONYMS CVP Customer Voice Portal GED-125 A messaging protocol that extends an interface to a Interactive Voice Response (IVR) (AKA Voice Response Unit (VRU)) device. The protocol allows for basic call control and running scripts on the IVR to play prompts and collect user input. IVR Interactive Voice Response JVM Java Virtual Machine OAMP Operations, Administration, Maintenance and Provisioning RTP Real-time Transport Protocol SIP Session Initiation Protocol VRU Voice Response Unit" REVISION "201109220000Z" DESCRIPTION "Added ccvpSipIntPostCallAnswered, ccvpSipIntWhisperAnswered,ccvpSipIntWhisperFailed,ccvpSipIntGree tingAnswered , ccvpSipIntGreetingFailed" REVISION "200710310000Z" DESCRIPTION "Added ccvpSipVideoTableGroup, ccvpIvrVideoTableGroup and ccvpIcmVideoTableGroup to include Video statistics." REVISION "200610060000Z" DESCRIPTION "Added objects: ccvpLicPortUsageWarning and ccvpLicPortUsageCritical to expose the current threshold settings for the port usage states of 'warning' and 'critical' respectively. Also added UNITS clause 'minutes' to ccvpServiceIntPeriod." REVISION "200605191200Z" DESCRIPTION "This is the initial version of this MIB module." ::= { ciscoMgmt 590 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.590.0 | ciscoCvpMIBNotifs | 1 | 1 | None |
| 1.3.6.1.4.1.9.9.590.1 | ciscoCvpMIBObjects | 7 | 231 | None |
| 1.3.6.1.4.1.9.9.590.2 | ciscoCvpMIBConform | 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.543 | ciscoLicenseMgmtMIB | 3 | 131 | The MIB module for managing licenses on the system. The licensing mechanism provides flexibility to enforce licensing for various… |
| 1.3.6.1.4.1.9.9.548 | ciscoErrDisableMIB | 3 | 43 | This MIB module provides the ability for a Network Management Station (NMS) to configure and monitor the error-disable feature vi… |
| 1.3.6.1.4.1.9.9.572 | ciscoRttMonIPExtMIB | 2 | 38 | This MIB contains extensions to tables in CISCO-RTTMON-MIB to support IP-layer extensions, specifically IPv6 addresses and other … |
| 1.3.6.1.4.1.9.9.573 | ciscoQosTcMIB | 0 | 0 | This module defines the textual conventions used within Cisco Qos MIBs. |
| 1.3.6.1.4.1.9.9.576 | ciscoLwappMobilityMIB | 3 | 60 | 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.577 | ciscoLwappAclMIB | 3 | 26 | 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.578 | ciscoRoutePoliciesMIB | 3 | 5 | This module provides a subtree to define OIDs so that various routing 'policies' used by Cisco routers can be expressed. This mod… |
| 1.3.6.1.4.1.9.9.580 | ciscoSwitchQosMIB | 3 | 295 | This MIB module extends the CISCO-CLASS-BASED-QOS-MIB by defining configuration and statistics information specific to the qualit… |
| 1.3.6.1.4.1.9.9.583 | ciscoGslbTcMIB | 0 | 0 | This MIB module defines Textual Conventions and OBJECT-IDENTITIES for use in documents defining management information base (MIBs… |
| 1.3.6.1.4.1.9.9.584 | ciscoEntityDiagTcMIB | 0 | 0 | This module defines the textual conventions used within Cisco Entity Diag MIB. |
| 1.3.6.1.4.1.9.9.585 | ciscoIpSlaEthernetMIB | 3 | 194 | This MIB module consists of two parts. 1) Auto-Ethernet-CFM Control: | | 2) ethernetJitter Stats: | | The first part defines a mechani… |
| 1.3.6.1.4.1.9.9.586 | ciscoNotificationControlMIB | 2 | 28 | This MIB provides network management support to regulate the transmission of notifications generated by a system providing networ… |
| 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.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.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 … |
| ... | ||||