The main purpose of this MIB is to provide product
component level configuration, status, statistics,
events, and alarm notifications for the Cisco TelePresence
Exchange System (CTX System).
A network management entity can use this MIB to:
- Discover cluster nodes
- Discover resources and their configurations
- Monitor status of all cluster nodes
- Monitor status of resources
- Monitor configuration status
- Monitor license status
- Monitor backup process status
- Monitor scheduling allocation failures
and port usage statistics
- Monitor product level error events
- Receive real time notifications for status change
and error
*********************************
System Overview
*********************************
Cisco TelePresence Exchange System (CTX System) is a turnkey
solution tailored to service providers who want to offer
premium video collaboration services and TelePresence as
a service to enterprise customers. The CTX System solution
preserves the full TelePresence experience across
enterprise and service provider boundaries, integrates with
third party SD/HD video technology, and maximizes service
and network value via tight integration with other Cisco
video and unified collaboration products.
The Cisco TelePresence Exchange is comprised of a variety
of components in order to deliver a highly integrated video
service platform that will meet the needs of the service
provider. At the heart of the exchange is what we refer to as
the core components that are standards based platforms
containing custom software to deliver the majority of the
systems services and functions. These core components are
the Cisco TelePresence Exchange System.
*********************************
System Components
*********************************
The core components are broken down into three application
functional areas; administration, call processing, and
persistent data storage. Each application is run on a
dedicated server. Each dedicated server has a backup
server. For each CTX System there are six servers. The
collection of servers are considered a cluster and the
servers are considered nodes within the cluster.
The below diagram illustrates the CTX System:
Cisco TelePresence Exchange System (CTX System)
/
|
| | Admin 1 | <
|
| | | |
|
| | Call Engine 1 | <
|
| | | |
|
| | Database 1 | <
|
\
The overall system requires a number of other Cisco
platforms to deliver an end-to-end solution. These other
platforms are configured in the CTX System as resources.
*********************************
Implementation
*********************************
The administration servers provide management interfaces
for the CTX System cluster nodes and for the resources
configured. This MIB consolidates the configuration,
status, alarms, errors, and statistics for all cluster
nodes. Therefore this MIB will only be implemented on
the admin servers. Each admin server can be polled
independently or via a virtual IP address. Each admin server
functions in an active/active mode with the same set of
information.
Hardware and operating system level information, such
as CPU, memory, power supplies, fans, etc. remain accessible
in hardware and operating system specific MIBS, such as
HOST-RESOURCES-MIB, IF-MIB, ...
*********************************
Configuration Tables and Linking
*********************************
Configuration table hierarchal structure is as follows:
___
|- Cluster Nodes - CTX System devices
|
|- Service Providers - Logical grouping
|
| |
| |
| | that are common to all resources
| |
| |
| | SIP IP, port, and protocol
| |
| |
| | such as Min/Max meeting ID's
| |
| |
| | large meeting support, etc.
|
|
All configuration table entries have a globally unique key.
No two keys will be the same within or across configuration
tables. The intent is to allow network management applications
to use these unique keys to link or join associated tables
together.
Configuration tables that have an association to another
table will contain a key reference object. Multiple
associations may exist, so the key reference will contain
a number in the object name. This number indicates only that
there are multiple associations. The reference key object
name will have the appended syntax 'KeyRef1'. Optionally
there maybe 'KeyRef2', etc. when multiple associations
exist.
Example of linking associated tables:
REGION TABLE Entry:
ctxRegionKey.1 =
STRING: 8a960c882aa5cd64012aa5d3963b0028
ctxRegionName.1 =
STRING: San Francisco
ctxRegionDescr.1 =
STRING: null
ctxRegionServiceProviderKeyRef1.1 =
STRING: 8a960c882aa5cd64012aa5d144730017
RESOURCE TABLE Entry:
ctxResourceKey.1 =
STRING: 8a960c882aca4db8012aca9bbdb401dd
ctxResourceName.1 =
STRING: abc-cuvcm
ctxResourceDescr.1 =
STRING: abc-cuvcm
ctxResourceMgmtIPType.1 =
INTEGER: ipv4(1)
ctxResourceMgmtIPAddr.1 =
STRING: 0.0.0.0
ctxResourceDeviceType.1 =
INTEGER: cuvcm(9)
ctxResourceRegionKeyRef1.1 =
STRING: 8a960c882aa5cd64012aa5d3963b0028
For the above entry we can see that there is a
ctxResourceRegionKeyRef1 that has the ctxRegionKey
value for region 'San Francisco' . Therefore resource
'abc-cuvcm' is associated to region 'San Francisco'
*********************************
Glossary
*********************************
CTX System : Cisco TelePresence Exchange System
Service Provider :
A service provider is configured in the CTX System
and serves as a logical grouping of configuration
objects.
Region :
A region is defined as a set of 'like' resources
in terms of network latency, jitter, quality of service,
etc. Normally a region is a geographic area such as
Americas, Europe, or Asia Pacific, but a region can be
a smaller set of like resources such as East and West
regions.
Resource :
A resource is server or network device that the CTX
System includes in configuration to provide call
signaling, media services, scheduling, or other function.
Cluster Node:
A cluster node is a server within the CTX System, such as
admin server, call engine server, or database server.
SIP Protocol:
SIP protocol is the transport protocol used to exchange
messages between user agents. The protocols are described
in RFC3261.
Port : Port is the media session port
allocation, also referred to as screen
E.164 : E.164 is an ITU-T recommendation for telephone
numbers. Reference link
http://www.itu.int/rec/T-REC-E.164/en
Endpoint: End system TelePresence device
CUCM : Cisco Unified Communications Manager
SBC : Session Border Controller such as ASR-1000 CUBE(sp)
CTMS : Cisco TelePresence Multipoint Switch
CTS : Cisco TelePresence System endpoint
CTS-MAN : Cisco TelePresence Manager
CUVCM : Cisco Unified Videoconferencing Manager
Media2 : Tandberg MSE 8510 blade
TPS : Tandberg MSE 8710 blade
VCS : Tandberg Video Communication Server
TMS : Tandberg Management Suite
XMLRPC : XML Remote Procedure Call protocol
Parsed from file CISCO-TELEPRESENCE-EXCHANGE-SYSTEM-MIB.mib
Module: CISCO-TELEPRESENCE-EXCHANGE-SYSTEM-MIB
The main purpose of this MIB is to provide product
component level configuration, status, statistics,
events, and alarm notifications for the Cisco TelePresence
Exchange System (CTX System).
A network management entity can use this MIB to:
- Discover cluster nodes
- Discover resources and their configurations
- Monitor status of all cluster nodes
- Monitor status of resources
- Monitor configuration status
- Monitor license status
- Monitor backup process status
- Monitor scheduling allocation failures
and port usage statistics
- Monitor product level error events
- Receive real time notifications for status change
and error
*********************************
System Overview
*********************************
Cisco TelePresence Exchange System (CTX System) is a turnkey
solution tailored to service providers who want to offer
premium video collaboration services and TelePresence as
a service to enterprise customers. The CTX System solution
preserves the full TelePresence experience across
enterprise and service provider boundaries, integrates with
third party SD/HD video technology, and maximizes service
and network value via tight integration with other Cisco
video and unified collaboration products.
The Cisco TelePresence Exchange is comprised of a variety
of components in order to deliver a highly integrated video
service platform that will meet the needs of the service
provider. At the heart of the exchange is what we refer to as
the core components that are standards based platforms
containing custom software to deliver the majority of the
systems services and functions. These core components are
the Cisco TelePresence Exchange System.
*********************************
System Components
*********************************
The core components are broken down into three application
functional areas; administration, call processing, and
persistent data storage. Each application is run on a
dedicated server. Each dedicated server has a backup
server. For each CTX System there are six servers. The
collection of servers are considered a cluster and the
servers are considered nodes within the cluster.
The below diagram illustrates the CTX System:
Cisco TelePresence Exchange System (CTX System)
/
|
| | Admin 1 | <
|
| | | |
|
| | Call Engine 1 | <
|
| | | |
|
| | Database 1 | <
|
\
The overall system requires a number of other Cisco
platforms to deliver an end-to-end solution. These other
platforms are configured in the CTX System as resources.
*********************************
Implementation
*********************************
The administration servers provide management interfaces
for the CTX System cluster nodes and for the resources
configured. This MIB consolidates the configuration,
status, alarms, errors, and statistics for all cluster
nodes. Therefore this MIB will only be implemented on
the admin servers. Each admin server can be polled
independently or via a virtual IP address. Each admin server
functions in an active/active mode with the same set of
information.
Hardware and operating system level information, such
as CPU, memory, power supplies, fans, etc. remain accessible
in hardware and operating system specific MIBS, such as
HOST-RESOURCES-MIB, IF-MIB, ...
*********************************
Configuration Tables and Linking
*********************************
Configuration table hierarchal structure is as follows:
___
|- Cluster Nodes - CTX System devices
|
|- Service Providers - Logical grouping
|
| |
| |
| | that are common to all resources
| |
| |
| | SIP IP, port, and protocol
| |
| |
| | such as Min/Max meeting ID's
| |
| |
| | large meeting support, etc.
|
|
All configuration table entries have a globally unique key.
No two keys will be the same within or across configuration
tables. The intent is to allow network management applications
to use these unique keys to link or join associated tables
together.
Configuration tables that have an association to another
table will contain a key reference object. Multiple
associations may exist, so the key reference will contain
a number in the object name. This number indicates only that
there are multiple associations. The reference key object
name will have the appended syntax 'KeyRef1'. Optionally
there maybe 'KeyRef2', etc. when multiple associations
exist.
Example of linking associated tables:
REGION TABLE Entry:
ctxRegionKey.1 =
STRING: 8a960c882aa5cd64012aa5d3963b0028
ctxRegionName.1 =
STRING: San Francisco
ctxRegionDescr.1 =
STRING: null
ctxRegionServiceProviderKeyRef1.1 =
STRING: 8a960c882aa5cd64012aa5d144730017
RESOURCE TABLE Entry:
ctxResourceKey.1 =
STRING: 8a960c882aca4db8012aca9bbdb401dd
ctxResourceName.1 =
STRING: abc-cuvcm
ctxResourceDescr.1 =
STRING: abc-cuvcm
ctxResourceMgmtIPType.1 =
INTEGER: ipv4(1)
ctxResourceMgmtIPAddr.1 =
STRING: 0.0.0.0
ctxResourceDeviceType.1 =
INTEGER: cuvcm(9)
ctxResourceRegionKeyRef1.1 =
STRING: 8a960c882aa5cd64012aa5d3963b0028
For the above entry we can see that there is a
ctxResourceRegionKeyRef1 that has the ctxRegionKey
value for region 'San Francisco' . Therefore resource
'abc-cuvcm' is associated to region 'San Francisco'
*********************************
Glossary
*********************************
CTX System : Cisco TelePresence Exchange System
Service Provider :
A service provider is configured in the CTX System
and serves as a logical grouping of configuration
objects.
Region :
A region is defined as a set of 'like' resources
in terms of network latency, jitter, quality of service,
etc. Normally a region is a geographic area such as
Americas, Europe, or Asia Pacific, but a region can be
a smaller set of like resources such as East and West
regions.
Resource :
A resource is server or network device that the CTX
System includes in configuration to provide call
signaling, media services, scheduling, or other function.
Cluster Node:
A cluster node is a server within the CTX System, such as
admin server, call engine server, or database server.
SIP Protocol:
SIP protocol is the transport protocol used to exchange
messages between user agents. The protocols are described
in RFC3261.
Port : Port is the media session port
allocation, also referred to as screen
E.164 : E.164 is an ITU-T recommendation for telephone
numbers. Reference link
http://www.itu.int/rec/T-REC-E.164/en
Endpoint: End system TelePresence device
CUCM : Cisco Unified Communications Manager
SBC : Session Border Controller such as ASR-1000 CUBE(sp)
CTMS : Cisco TelePresence Multipoint Switch
CTS : Cisco TelePresence System endpoint
CTS-MAN : Cisco TelePresence Manager
CUVCM : Cisco Unified Videoconferencing Manager
Media2 : Tandberg MSE 8510 blade
TPS : Tandberg MSE 8710 blade
VCS : Tandberg Video Communication Server
TMS : Tandberg Management Suite
XMLRPC : XML Remote Procedure Call protocol
Parsed from file CISCO-TELEPRESENCE-EXCHANGE-SYSTEM-MIB.my.txt
Company: None
Module: CISCO-TELEPRESENCE-EXCHANGE-SYSTEM-MIB
The main purpose of this MIB is to provide product
component level configuration, status, statistics,
events, and alarm notifications for the Cisco TelePresence
Exchange System (CTX System).
A network management entity can use this MIB to:
- Discover cluster nodes
- Discover resources and their configurations
- Monitor status of all cluster nodes
- Monitor status of resources
- Monitor configuration status
- Monitor license status
- Monitor backup process status
- Monitor scheduling allocation failures
and port usage statistics
- Monitor product level error events
- Receive real time notifications for status change
and error
*********************************
System Overview
*********************************
Cisco TelePresence Exchange System (CTX System) is a turnkey
solution tailored to service providers who want to offer
premium video collaboration services and TelePresence as
a service to enterprise customers. The CTX System solution
preserves the full TelePresence experience across
enterprise and service provider boundaries, integrates with
third party SD/HD video technology, and maximizes service
and network value via tight integration with other Cisco
video and unified collaboration products.
The Cisco TelePresence Exchange is comprised of a variety
of components in order to deliver a highly integrated video
service platform that will meet the needs of the service
provider. At the heart of the exchange is what we refer to as
the core components that are standards based platforms
containing custom software to deliver the majority of the
systems services and functions. These core components are
the Cisco TelePresence Exchange System.
*********************************
System Components
*********************************
The core components are broken down into three application
functional areas; administration, call processing, and
persistent data storage. Each application is run on a
dedicated server. Each dedicated server has a backup
server. For each CTX System there are six servers. The
collection of servers are considered a cluster and the
servers are considered nodes within the cluster.
The below diagram illustrates the CTX System:
Cisco TelePresence Exchange System (CTX System)
/
|
| | Admin 1 | <
|
| | | |
|
| | Call Engine 1 | <
|
| | | |
|
| | Database 1 | <
|
\
The overall system requires a number of other Cisco
platforms to deliver an end-to-end solution. These other
platforms are configured in the CTX System as resources.
*********************************
Implementation
*********************************
The administration servers provide management interfaces
for the CTX System cluster nodes and for the resources
configured. This MIB consolidates the configuration,
status, alarms, errors, and statistics for all cluster
nodes. Therefore this MIB will only be implemented on
the admin servers. Each admin server can be polled
independently or via a virtual IP address. Each admin server
functions in an active/active mode with the same set of
information.
Hardware and operating system level information, such
as CPU, memory, power supplies, fans, etc. remain accessible
in hardware and operating system specific MIBS, such as
HOST-RESOURCES-MIB, IF-MIB, ...
*********************************
Configuration Tables and Linking
*********************************
Configuration table hierarchal structure is as follows:
___
|- Cluster Nodes - CTX System devices
|
|- Service Providers - Logical grouping
|
| |
| |
| | that are common to all resources
| |
| |
| | SIP IP, port, and protocol
| |
| |
| | such as Min/Max meeting ID's
| |
| |
| | large meeting support, etc.
|
|
All configuration table entries have a globally unique key.
No two keys will be the same within or across configuration
tables. The intent is to allow network management applications
to use these unique keys to link or join associated tables
together.
Configuration tables that have an association to another
table will contain a key reference object. Multiple
associations may exist, so the key reference will contain
a number in the object name. This number indicates only that
there are multiple associations. The reference key object
name will have the appended syntax 'KeyRef1'. Optionally
there maybe 'KeyRef2', etc. when multiple associations
exist.
Example of linking associated tables:
REGION TABLE Entry:
ctxRegionKey.1 =
STRING: 8a960c882aa5cd64012aa5d3963b0028
ctxRegionName.1 =
STRING: San Francisco
ctxRegionDescr.1 =
STRING: null
ctxRegionServiceProviderKeyRef1.1 =
STRING: 8a960c882aa5cd64012aa5d144730017
RESOURCE TABLE Entry:
ctxResourceKey.1 =
STRING: 8a960c882aca4db8012aca9bbdb401dd
ctxResourceName.1 =
STRING: abc-cuvcm
ctxResourceDescr.1 =
STRING: abc-cuvcm
ctxResourceMgmtIPType.1 =
INTEGER: ipv4(1)
ctxResourceMgmtIPAddr.1 =
STRING: 0.0.0.0
ctxResourceDeviceType.1 =
INTEGER: cuvcm(9)
ctxResourceRegionKeyRef1.1 =
STRING: 8a960c882aa5cd64012aa5d3963b0028
For the above entry we can see that there is a
ctxResourceRegionKeyRef1 that has the ctxRegionKey
value for region 'San Francisco' . Therefore resource
'abc-cuvcm' is associated to region 'San Francisco'
*********************************
Glossary
*********************************
CTX System : Cisco TelePresence Exchange System
Service Provider :
A service provider is configured in the CTX System
and serves as a logical grouping of configuration
objects.
Region :
A region is defined as a set of 'like' resources
in terms of network latency, jitter, quality of service,
etc. Normally a region is a geographic area such as
Americas, Europe, or Asia Pacific, but a region can be
a smaller set of like resources such as East and West
regions.
Resource :
A resource is server or network device that the CTX
System includes in configuration to provide call
signaling, media services, scheduling, or other function.
Cluster Node:
A cluster node is a server within the CTX System, such as
admin server, call engine server, or database server.
SIP Protocol:
SIP protocol is the transport protocol used to exchange
messages between user agents. The protocols are described
in RFC3261.
Port : Port is the media session port
allocation, also referred to as screen
E.164 : E.164 is an ITU-T recommendation for telephone
numbers. Reference link
http://www.itu.int/rec/T-REC-E.164/en
Endpoint: End system TelePresence device
CUCM : Cisco Unified Communications Manager
SBC : Session Border Controller such as ASR-1000 CUBE(sp)
CTMS : Cisco TelePresence Multipoint Switch
CTS : Cisco TelePresence System endpoint
CTS-MAN : Cisco TelePresence Manager
CUVCM : Cisco Unified Videoconferencing Manager
Media2 : Tandberg MSE 8510 blade
TPS : Tandberg MSE 8710 blade
VCS : Tandberg Video Communication Server
TMS : Tandberg Management Suite
XMLRPC : XML Remote Procedure Call protocol
ciscoTelepresenceExchangeSystemMIB MODULE-IDENTITY LAST-UPDATED "201101130000Z" 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 main purpose of this MIB is to provide product component level configuration, status, statistics, events, and alarm notifications for the Cisco TelePresence Exchange System (CTX System). A network management entity can use this MIB to: - Discover cluster nodes - Discover resources and their configurations - Monitor status of all cluster nodes - Monitor status of resources - Monitor configuration status - Monitor license status - Monitor backup process status - Monitor scheduling allocation failures and port usage statistics - Monitor product level error events - Receive real time notifications for status change and error ********************************* System Overview ********************************* Cisco TelePresence Exchange System (CTX System) is a turnkey solution tailored to service providers who want to offer premium video collaboration services and TelePresence as a service to enterprise customers. The CTX System solution preserves the full TelePresence experience across enterprise and service provider boundaries, integrates with third party SD/HD video technology, and maximizes service and network value via tight integration with other Cisco video and unified collaboration products. The Cisco TelePresence Exchange is comprised of a variety of components in order to deliver a highly integrated video service platform that will meet the needs of the service provider. At the heart of the exchange is what we refer to as the core components that are standards based platforms containing custom software to deliver the majority of the systems services and functions. These core components are the Cisco TelePresence Exchange System. ********************************* System Components ********************************* The core components are broken down into three application functional areas; administration, call processing, and persistent data storage. Each application is run on a dedicated server. Each dedicated server has a backup server. For each CTX System there are six servers. The collection of servers are considered a cluster and the servers are considered nodes within the cluster. The below diagram illustrates the CTX System: Cisco TelePresence Exchange System (CTX System) / | | | Admin 1 | < | | | | | | | | Call Engine 1 | < | | | | | | | | Database 1 | < | \ The overall system requires a number of other Cisco platforms to deliver an end-to-end solution. These other platforms are configured in the CTX System as resources. ********************************* Implementation ********************************* The administration servers provide management interfaces for the CTX System cluster nodes and for the resources configured. This MIB consolidates the configuration, status, alarms, errors, and statistics for all cluster nodes. Therefore this MIB will only be implemented on the admin servers. Each admin server can be polled independently or via a virtual IP address. Each admin server functions in an active/active mode with the same set of information. Hardware and operating system level information, such as CPU, memory, power supplies, fans, etc. remain accessible in hardware and operating system specific MIBS, such as HOST-RESOURCES-MIB, IF-MIB, ... ********************************* Configuration Tables and Linking ********************************* Configuration table hierarchal structure is as follows: ___ |- Cluster Nodes - CTX System devices | |- Service Providers - Logical grouping | | | | | | | that are common to all resources | | | | | | SIP IP, port, and protocol | | | | | | such as Min/Max meeting ID's | | | | | | large meeting support, etc. | | All configuration table entries have a globally unique key. No two keys will be the same within or across configuration tables. The intent is to allow network management applications to use these unique keys to link or join associated tables together. Configuration tables that have an association to another table will contain a key reference object. Multiple associations may exist, so the key reference will contain a number in the object name. This number indicates only that there are multiple associations. The reference key object name will have the appended syntax 'KeyRef1'. Optionally there maybe 'KeyRef2', etc. when multiple associations exist. Example of linking associated tables: REGION TABLE Entry: ctxRegionKey.1 = STRING: 8a960c882aa5cd64012aa5d3963b0028 ctxRegionName.1 = STRING: San Francisco ctxRegionDescr.1 = STRING: null ctxRegionServiceProviderKeyRef1.1 = STRING: 8a960c882aa5cd64012aa5d144730017 RESOURCE TABLE Entry: ctxResourceKey.1 = STRING: 8a960c882aca4db8012aca9bbdb401dd ctxResourceName.1 = STRING: abc-cuvcm ctxResourceDescr.1 = STRING: abc-cuvcm ctxResourceMgmtIPType.1 = INTEGER: ipv4(1) ctxResourceMgmtIPAddr.1 = STRING: 0.0.0.0 ctxResourceDeviceType.1 = INTEGER: cuvcm(9) ctxResourceRegionKeyRef1.1 = STRING: 8a960c882aa5cd64012aa5d3963b0028 For the above entry we can see that there is a ctxResourceRegionKeyRef1 that has the ctxRegionKey value for region 'San Francisco' . Therefore resource 'abc-cuvcm' is associated to region 'San Francisco' ********************************* Glossary ********************************* CTX System : Cisco TelePresence Exchange System Service Provider : A service provider is configured in the CTX System and serves as a logical grouping of configuration objects. Region : A region is defined as a set of 'like' resources in terms of network latency, jitter, quality of service, etc. Normally a region is a geographic area such as Americas, Europe, or Asia Pacific, but a region can be a smaller set of like resources such as East and West regions. Resource : A resource is server or network device that the CTX System includes in configuration to provide call signaling, media services, scheduling, or other function. Cluster Node: A cluster node is a server within the CTX System, such as admin server, call engine server, or database server. SIP Protocol: SIP protocol is the transport protocol used to exchange messages between user agents. The protocols are described in RFC3261. Port : Port is the media session port allocation, also referred to as screen E.164 : E.164 is an ITU-T recommendation for telephone numbers. Reference link http://www.itu.int/rec/T-REC-E.164/en Endpoint: End system TelePresence device CUCM : Cisco Unified Communications Manager SBC : Session Border Controller such as ASR-1000 CUBE(sp) CTMS : Cisco TelePresence Multipoint Switch CTS : Cisco TelePresence System endpoint CTS-MAN : Cisco TelePresence Manager CUVCM : Cisco Unified Videoconferencing Manager Media2 : Tandberg MSE 8510 blade TPS : Tandberg MSE 8710 blade VCS : Tandberg Video Communication Server TMS : Tandberg Management Suite XMLRPC : XML Remote Procedure Call protocol" REVISION "201101130000Z" DESCRIPTION "Initial version of this MIB module" ::= { ciscoMgmt 758 }
ciscoTelepresenceExchangeSystemMIB OBJECT IDENTIFIER ::= { ciscoMgmt 758 }
Vendor: Cisco
Module: CISCO-TELEPRESENCE-EXCHANGE-SYSTEM-MIB
[Automatically extracted from oidview.com]
ciscoTelepresenceExchangeSystemMIB MODULE-IDENTITY LAST-UPDATED "201101130000Z" 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 main purpose of this MIB is to provide product component level configuration, status, statistics, events, and alarm notifications for the Cisco TelePresence Exchange System (CTX System). A network management entity can use this MIB to: - Discover cluster nodes - Discover resources and their configurations - Monitor status of all cluster nodes - Monitor status of resources - Monitor configuration status - Monitor license status - Monitor backup process status - Monitor scheduling allocation failures and port usage statistics - Monitor product level error events - Receive real time notifications for status change and error ********************************* System Overview ********************************* Cisco TelePresence Exchange System (CTX System) is a turnkey solution tailored to service providers who want to offer premium video collaboration services and TelePresence as a service to enterprise customers. The CTX System solution preserves the full TelePresence experience across enterprise and service provider boundaries, integrates with third party SD/HD video technology, and maximizes service and network value via tight integration with other Cisco video and unified collaboration products. The Cisco TelePresence Exchange is comprised of a variety of components in order to deliver a highly integrated video service platform that will meet the needs of the service provider. At the heart of the exchange is what we refer to as the core components that are standards based platforms containing custom software to deliver the majority of the systems services and functions. These core components are the Cisco TelePresence Exchange System. ********************************* System Components ********************************* The core components are broken down into three application functional areas; administration, call processing, and persistent data storage. Each application is run on a dedicated server. Each dedicated server has a backup server. For each CTX System there are six servers. The collection of servers are considered a cluster and the servers are considered nodes within the cluster. The below diagram illustrates the CTX System: Cisco TelePresence Exchange System (CTX System) / | | | Admin 1 | < | | | | | | | | Call Engine 1 | < | | | | | | | | Database 1 | < | \ The overall system requires a number of other Cisco platforms to deliver an end-to-end solution. These other platforms are configured in the CTX System as resources. ********************************* Implementation ********************************* The administration servers provide management interfaces for the CTX System cluster nodes and for the resources configured. This MIB consolidates the configuration, status, alarms, errors, and statistics for all cluster nodes. Therefore this MIB will only be implemented on the admin servers. Each admin server can be polled independently or via a virtual IP address. Each admin server functions in an active/active mode with the same set of information. Hardware and operating system level information, such as CPU, memory, power supplies, fans, etc. remain accessible in hardware and operating system specific MIBS, such as HOST-RESOURCES-MIB, IF-MIB, ... ********************************* Configuration Tables and Linking ********************************* Configuration table hierarchal structure is as follows: ___ |- Cluster Nodes - CTX System devices | |- Service Providers - Logical grouping | | | | | | | that are common to all resources | | | | | | SIP IP, port, and protocol | | | | | | such as Min/Max meeting ID's | | | | | | large meeting support, etc. | | All configuration table entries have a globally unique key. No two keys will be the same within or across configuration tables. The intent is to allow network management applications to use these unique keys to link or join associated tables together. Configuration tables that have an association to another table will contain a key reference object. Multiple associations may exist, so the key reference will contain a number in the object name. This number indicates only that there are multiple associations. The reference key object name will have the appended syntax 'KeyRef1'. Optionally there maybe 'KeyRef2', etc. when multiple associations exist. Example of linking associated tables: REGION TABLE Entry: ctxRegionKey.1 = STRING: 8a960c882aa5cd64012aa5d3963b0028 ctxRegionName.1 = STRING: San Francisco ctxRegionDescr.1 = STRING: null ctxRegionServiceProviderKeyRef1.1 = STRING: 8a960c882aa5cd64012aa5d144730017 RESOURCE TABLE Entry: ctxResourceKey.1 = STRING: 8a960c882aca4db8012aca9bbdb401dd ctxResourceName.1 = STRING: abc-cuvcm ctxResourceDescr.1 = STRING: abc-cuvcm ctxResourceMgmtIPType.1 = INTEGER: ipv4(1) ctxResourceMgmtIPAddr.1 = STRING: 0.0.0.0 ctxResourceDeviceType.1 = INTEGER: cuvcm(9) ctxResourceRegionKeyRef1.1 = STRING: 8a960c882aa5cd64012aa5d3963b0028 For the above entry we can see that there is a ctxResourceRegionKeyRef1 that has the ctxRegionKey value for region 'San Francisco' . Therefore resource 'abc-cuvcm' is associated to region 'San Francisco' ********************************* Glossary ********************************* CTX System : Cisco TelePresence Exchange System Service Provider : A service provider is configured in the CTX System and serves as a logical grouping of configuration objects. Region : A region is defined as a set of 'like' resources in terms of network latency, jitter, quality of service, etc. Normally a region is a geographic area such as Americas, Europe, or Asia Pacific, but a region can be a smaller set of like resources such as East and West regions. Resource : A resource is server or network device that the CTX System includes in configuration to provide call signaling, media services, scheduling, or other function. Cluster Node: A cluster node is a server within the CTX System, such as admin server, call engine server, or database server. SIP Protocol: SIP protocol is the transport protocol used to exchange messages between user agents. The protocols are described in RFC3261. Port : Port is the media session port allocation, also referred to as screen E.164 : E.164 is an ITU-T recommendation for telephone numbers. Reference link http://www.itu.int/rec/T-REC-E.164/en Endpoint: End system TelePresence device CUCM : Cisco Unified Communications Manager SBC : Session Border Controller such as ASR-1000 CUBE(sp) CTMS : Cisco TelePresence Multipoint Switch CTS : Cisco TelePresence System endpoint CTS-MAN : Cisco TelePresence Manager CUVCM : Cisco Unified Videoconferencing Manager Media2 : Tandberg MSE 8510 blade TPS : Tandberg MSE 8710 blade VCS : Tandberg Video Communication Server TMS : Tandberg Management Suite XMLRPC : XML Remote Procedure Call protocol" REVISION "201101130000Z" DESCRIPTION "Initial version of this MIB module" ::= { ciscoMgmt 758 }
ciscoTelepresenceExchangeSystemMIB MODULE-IDENTITY LAST-UPDATED "201101130000Z" 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 main purpose of this MIB is to provide product component level configuration, status, statistics, events, and alarm notifications for the Cisco TelePresence Exchange System (CTX System). A network management entity can use this MIB to: - Discover cluster nodes - Discover resources and their configurations - Monitor status of all cluster nodes - Monitor status of resources - Monitor configuration status - Monitor license status - Monitor backup process status - Monitor scheduling allocation failures and port usage statistics - Monitor product level error events - Receive real time notifications for status change and error ********************************* System Overview ********************************* Cisco TelePresence Exchange System (CTX System) is a turnkey solution tailored to service providers who want to offer premium video collaboration services and TelePresence as a service to enterprise customers. The CTX System solution preserves the full TelePresence experience across enterprise and service provider boundaries, integrates with third party SD/HD video technology, and maximizes service and network value via tight integration with other Cisco video and unified collaboration products. The Cisco TelePresence Exchange is comprised of a variety of components in order to deliver a highly integrated video service platform that will meet the needs of the service provider. At the heart of the exchange is what we refer to as the core components that are standards based platforms containing custom software to deliver the majority of the systems services and functions. These core components are the Cisco TelePresence Exchange System. ********************************* System Components ********************************* The core components are broken down into three application functional areas; administration, call processing, and persistent data storage. Each application is run on a dedicated server. Each dedicated server has a backup server. For each CTX System there are six servers. The collection of servers are considered a cluster and the servers are considered nodes within the cluster. The below diagram illustrates the CTX System: Cisco TelePresence Exchange System (CTX System) / | | | Admin 1 | < | | | | | | | | Call Engine 1 | < | | | | | | | | Database 1 | < | \ The overall system requires a number of other Cisco platforms to deliver an end-to-end solution. These other platforms are configured in the CTX System as resources. ********************************* Implementation ********************************* The administration servers provide management interfaces for the CTX System cluster nodes and for the resources configured. This MIB consolidates the configuration, status, alarms, errors, and statistics for all cluster nodes. Therefore this MIB will only be implemented on the admin servers. Each admin server can be polled independently or via a virtual IP address. Each admin server functions in an active/active mode with the same set of information. Hardware and operating system level information, such as CPU, memory, power supplies, fans, etc. remain accessible in hardware and operating system specific MIBS, such as HOST-RESOURCES-MIB, IF-MIB, ... ********************************* Configuration Tables and Linking ********************************* Configuration table hierarchal structure is as follows: ___ |- Cluster Nodes - CTX System devices | |- Service Providers - Logical grouping | | | | | | | that are common to all resources | | | | | | SIP IP, port, and protocol | | | | | | such as Min/Max meeting ID's | | | | | | large meeting support, etc. | | All configuration table entries have a globally unique key. No two keys will be the same within or across configuration tables. The intent is to allow network management applications to use these unique keys to link or join associated tables together. Configuration tables that have an association to another table will contain a key reference object. Multiple associations may exist, so the key reference will contain a number in the object name. This number indicates only that there are multiple associations. The reference key object name will have the appended syntax 'KeyRef1'. Optionally there maybe 'KeyRef2', etc. when multiple associations exist. Example of linking associated tables: REGION TABLE Entry: ctxRegionKey.1 = STRING: 8a960c882aa5cd64012aa5d3963b0028 ctxRegionName.1 = STRING: San Francisco ctxRegionDescr.1 = STRING: null ctxRegionServiceProviderKeyRef1.1 = STRING: 8a960c882aa5cd64012aa5d144730017 RESOURCE TABLE Entry: ctxResourceKey.1 = STRING: 8a960c882aca4db8012aca9bbdb401dd ctxResourceName.1 = STRING: abc-cuvcm ctxResourceDescr.1 = STRING: abc-cuvcm ctxResourceMgmtIPType.1 = INTEGER: ipv4(1) ctxResourceMgmtIPAddr.1 = STRING: 0.0.0.0 ctxResourceDeviceType.1 = INTEGER: cuvcm(9) ctxResourceRegionKeyRef1.1 = STRING: 8a960c882aa5cd64012aa5d3963b0028 For the above entry we can see that there is a ctxResourceRegionKeyRef1 that has the ctxRegionKey value for region 'San Francisco' . Therefore resource 'abc-cuvcm' is associated to region 'San Francisco' ********************************* Glossary ********************************* CTX System : Cisco TelePresence Exchange System Service Provider : A service provider is configured in the CTX System and serves as a logical grouping of configuration objects. Region : A region is defined as a set of 'like' resources in terms of network latency, jitter, quality of service, etc. Normally a region is a geographic area such as Americas, Europe, or Asia Pacific, but a region can be a smaller set of like resources such as East and West regions. Resource : A resource is server or network device that the CTX System includes in configuration to provide call signaling, media services, scheduling, or other function. Cluster Node: A cluster node is a server within the CTX System, such as admin server, call engine server, or database server. SIP Protocol: SIP protocol is the transport protocol used to exchange messages between user agents. The protocols are described in RFC3261. Port : Port is the media session port allocation, also referred to as screen E.164 : E.164 is an ITU-T recommendation for telephone numbers. Reference link http://www.itu.int/rec/T-REC-E.164/en Endpoint: End system TelePresence device CUCM : Cisco Unified Communications Manager SBC : Session Border Controller such as ASR-1000 CUBE(sp) CTMS : Cisco TelePresence Multipoint Switch CTS : Cisco TelePresence System endpoint CTS-MAN : Cisco TelePresence Manager CUVCM : Cisco Unified Videoconferencing Manager Media2 : Tandberg MSE 8510 blade TPS : Tandberg MSE 8710 blade VCS : Tandberg Video Communication Server TMS : Tandberg Management Suite XMLRPC : XML Remote Procedure Call protocol" REVISION "201101130000Z" DESCRIPTION "Initial version of this MIB module" ::= { ciscoMgmt 758 }
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.4.1.9.9.758.0 | ciscoTelepresenceExchangeSystemMIBNotifs | 16 | 16 | None |
1.3.6.1.4.1.9.9.758.1 | ciscoTelepresenceExchangeSystemMIBObjects | 5 | 145 | None |
1.3.6.1.4.1.9.9.758.7 | ciscoTelepresenceExchangeSystemMIBConform | 2 | 9 | 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.708 | ciscoContentDeliveryStreamingMIB | 2 | 30 | This MIB instrumentation is for managing the Content Delivery and Streaming functionality on Cisco devices. Contents are ingested… |
1.3.6.1.4.1.9.9.709 | ciscoVlanGroupMIB | 3 | 18 | MIB module for monitoring and configuring VLAN Group Mapping information. |
1.3.6.1.4.1.9.9.710 | ciscoVirtualNicMIB | 3 | 36 | This MIB module defines MIB objects which provide mechanisms to manage the parameters used by or related to Virtual NIC. Virtual s… |
1.3.6.1.4.1.9.9.711 | ciscoVrfMIB | 3 | 48 | The MIB module for provisioning and managing network virtualization features. This module provides manageability for VRF, VRF-Lit… |
1.3.6.1.4.1.9.9.712 | ciscoWirelessNotificationMIB | 3 | 30 | This MIB is intended to be implemented on those Network Management applications that manage a network of wireless devices through… |
1.3.6.1.4.1.9.9.713 | ciscoTrustSecPolicyMIB | 3 | 204 | This MIB module defines managed objects that facilitate the management of various policies within the Cisco Trusted Security (Tru… |
1.3.6.1.4.1.9.9.714 | ciscoHwModuleControlMIB | 3 | 27 | The MIB module providing configuration and control information for management of hardware modules and components on Cisco devices… |
1.3.6.1.4.1.9.9.715 | ciscoEntityQfpMIB | 3 | 82 | This MIB module defines managed objects that facilitate the management of Quantum Flow Processors (QFP), which are listed in the … |
1.3.6.1.4.1.9.9.716 | ciscoVoIpTapMIB | 3 | 18 | This module manages Cisco's intercept feature for Voice over IP (VoIP). This MIB is used along with CISCO-TAP2-MIB to intercept V… |
1.3.6.1.4.1.9.9.718 | ciscoCuicappsMIB | 3 | 130 | The Cisco Unified Intelligence Center (CUIC) is a scalable robust and secure reporting solution for contact center applications. T… |
1.3.6.1.4.1.9.9.719 | ciscoUnifiedComputingMIB | 5 | 13463 | This MIB module defines the managed objects for Unified Computing System (UCS) Manager. Cisco UCS Manager provides centralized m… |
1.3.6.1.4.1.9.9.720 | ciscoTrustSecSxpMIB | 3 | 140 | This MIB module is for the configuration and status query of SGT Exchange Protocol over TCP (SXPoTCP) feature of the device on th… |
1.3.6.1.4.1.9.9.721 | ciscoMldSnoopingMIB | 3 | 215 | This MIB module defines objects that describe IGMP/MLD snooping. It provides remote network management system the ability to manag… |
1.3.6.1.4.1.9.9.724 | cggsnGeoMIB | 2 | 12 | This MIB provide additional information for passive interface configured for each OSPF process, independent of object creation in… |
1.3.6.1.4.1.9.9.725 | ciscoSmartInstallMIB | 3 | 101 | This MIB module defines managed objects that facilitate the management of Smart Install feature. Smart Install is a plug-and-pla… |
1.3.6.1.4.1.9.9.729 | ciscoCdstvServicesMIB | 3 | 21 | This MIB module defines service monitoring objects that faciliate the management of the Cisco Content Delivery System for TV (CDS… |
1.3.6.1.4.1.9.9.730 | ciscoTrustSecMIB | 3 | 128 | This MIB module is for the configuration of a network device on the Cisco Trusted Security (TrustSec) system. TrustSec secures a … |
1.3.6.1.4.1.9.9.731 | ciscoEpcGatewayMIB | 3 | 130 | This MIB module manages the features and configuration for PDN Gateway(PGW) and Serving Gateway(SGW) in Evolved Packet Core(EPC) … |
1.3.6.1.4.1.9.9.732 | ciscoDeviceLocationMIB | 3 | 49 | This MIB is used for managing location information of end point devices(Telepresence, IP Camera, Digital media player etc) connec… |
1.3.6.1.4.1.9.9.733 | ciscoMeetingPlaceMIB | 3 | 70 | This MIB allows management of Cisco Unified MeetingPlace (CUMP) features, CUMP is the key conferencing solution component for Cis… |
1.3.6.1.4.1.9.9.734 | ciscoGtpv2MIB | 2 | 160 | This MIB module manages the GPRS Tunneling Protocol version 2(GTPv2) statistics for the Evolved Packet Core(EPC) architecture. SGW… |
1.3.6.1.4.1.9.9.735 | ciscoCdstvFsiMIB | 3 | 25 | This MIB module defines FSI configurartion objects that faciliate the management of the Cisco Content Delivery System for TV (CDS… |
1.3.6.1.4.1.9.9.736 | ciscoRadiusExtMIB | 2 | 51 | This MIB module defines objects describing RADIUS (Remote Access Dialin User Service), serving as an extension of the following M… |
1.3.6.1.4.1.9.9.737 | ciscoSwitchNetflowMIB | 3 | 40 | This MIB module defines management objects for the Netflow features on Cisco Layer 2 and Layer 3 devices. |
1.3.6.1.4.1.9.9.738 | cmplsTeStdExtMIB | 3 | 72 | This MIB module contains Cisco specific managed object definitions for MPLS Traffic Engineering (TE), not contained in MPLS-TE-ST… |
1.3.6.1.4.1.9.9.739 | ciscoCdstvIngestmgrMIB | 3 | 69 | This MIB module defines ingest manager configuration objects that faciliate the management of the Cisco Content Delivery System f… |
1.3.6.1.4.1.9.9.740 | ciscoTrustSecIfMIB | 3 | 143 | This MIB module defines management objects for configuration and monitoring of the interfaces in Cisco Trusted Security environme… |
1.3.6.1.4.1.9.9.741 | ciscoTrustSecServerMIB | 3 | 85 | This MIB module defines management objects for configuration and monitoring of the AAA servers in Cisco Trusted Security environm… |
1.3.6.1.4.1.9.9.742 | ciscoIpAddressPoolTcMIB | 0 | 0 | This MIB module defines textual conventions used by MIB modules defining objects describing IP address pools. |
1.3.6.1.4.1.9.9.743 | ciscoCdstvCsStatsMIB | 3 | 83 | This MIB module defines objects describing the caching and streaming statistics objects that facilitate the management of the Cis… |
1.3.6.1.4.1.9.9.744 | ciscoIpslaVideoMIB | 3 | 73 | IP SLA is a capability which utilizes active monitoring for network performance. It can be used for network troubleshooting, net… |
1.3.6.1.4.1.9.9.745 | ciscoEntitySensorExtMIB | 3 | 21 | This MIB is extension to ENTITY-SENSOR-MIB(RFC 3433). This MIB also defines the notifications applicable for sensors reported in … |
1.3.6.1.4.1.9.9.748 | ciscoIpAddressPoolMIB | 3 | 96 | This MIB modules defines objects that describe common aspects of IP address pools. IP Address Pool Manager =======================… |
1.3.6.1.4.1.9.9.749 | ciscoCdstvBwmgrMIB | 3 | 21 | This MIB module defines Bandwidth Manager configuration objects that facilitate the management of the Cisco Content Delivery Syst… |
1.3.6.1.4.1.9.9.750 | ciscoCdstvIngestTuningMIB | 3 | 18 | This MIB module defines ingest tuning configuration objects that facilitate the management of the Cisco Content Delivery System f… |
1.3.6.1.4.1.9.9.751 | ciscoCdstvAuthmgrMIB | 3 | 25 | This MIB module defines objects that describe the configuration of the authentication manager for the Cisco Content Delivery Syst… |
1.3.6.1.4.1.9.9.753 | ciscoVideoSessionMIB | 3 | 145 | This MIB module complements the CISCO-VOICE-DIAL-CONTROL-MIB, which provides voice telephony peer information, by providing manag… |
1.3.6.1.4.1.9.9.754 | ciscoCdstvServerMIB | 3 | 82 | This MIB module defines server configuration that faciliate the management of the Cisco Content Delivery System for TV (CDS-TV) … |
1.3.6.1.4.1.9.9.755 | ciscoCdstvIsaMIB | 3 | 145 | This MIB module defines ISA configuration objects that faciliate the management of the Cisco Content Delivery System for TV (CDS-… |
1.3.6.1.4.1.9.9.756 | ciscoEntityPerformanceMIB | 3 | 56 | This MIB module defines managed objects that facilitate to monitor performance of any physical entity, which are listed in the EN… |
1.3.6.1.4.1.9.9.757 | ciscoSbcStatsMIB | 3 | 106 | The main purpose of this MIB is to define the statistics information for Session Border Controller application. This MIB categori… |
1.3.6.1.4.1.9.9.759 | ciscoGdoiMIB | 3 | 213 | This MIB module defines objects for managing the GDOI protocol. Copyright (c) The IETF Trust (2010). This version of this MIB mo… |
1.3.6.1.4.1.9.9.760 | ciscoPtpMIB | 3 | 182 | The MIB module for PTPv2 (IEEE1588 - 2008) Overview of PTPv2 (IEEE 1588-2008) This IEEE standard defines a protocol enabling prec… |
1.3.6.1.4.1.9.9.761 | ciscoNetsyncMIB | 3 | 104 | The Synchronous Ethernet (SyncE) MIB is defined for monitoring network synchronization based on ITU-T G.781 clock selection. Sync… |
1.3.6.1.4.1.9.9.762 | ciscoWanOptimizationMIB | 3 | 302 | This MIB is for managing Wide Area Network (WAN) Optimization systems. The objective of WAN optimization system is to reduce as m… |
1.3.6.1.4.1.9.9.763 | ciscoVideoTc | 0 | 0 | This MIB module defines a collection of common video-related textual conventions to be used in Cisco MIBS for video-capable produ… |
1.3.6.1.4.1.9.9.764 | ciscoUbeMIB | 2 | 12 | This MIB describes objects used for managing Cisco Unified Border Element (CUBE). The Cisco Unified Border Element (CUBE) is a Ci… |
1.3.6.1.4.1.9.9.765 | ciscoFlowCloneMIB | 3 | 44 | This MIB module defines objects that manages flow cloning feature. A flow cloning can be described as a hardware or software enti… |
1.3.6.1.4.1.9.9.766 | ciscoIpslaVideoProfileMIB | 3 | 29 | IP SLA is a capability which utilizes active monitoring for network performance. It can be used for network troubleshooting, net… |
1.3.6.1.4.1.9.9.767 | ciscoLwappDot11ClientRmMIB | 3 | 64 | 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.768 | ciscoEntitySensorHistoryMIB | 2 | 20 | This MIB module defines objects that describe collections and measurement information for each sensor supporting historical data … |
1.3.6.1.4.1.9.9.769 | ciscoMediaQualityMIB | 3 | 214 | This MIB module enhances the DIAL-CONTROL-MIB (RFC2128) by providing call information and voice and video quality statistics of c… |
1.3.6.1.4.1.9.9.770 | ciscoTcpMetricsMIB | 4 | 22 | This MIB module defines objects that describe the quality metrics of TCP streams. GLOSSARY ============ Flow Monitor - a hardware o… |
1.3.6.1.4.1.9.9.771 | ciscoMediaMetricsMIB | 4 | 38 | This MIB module defines objects that describe the quality metrics of Media streams. GLOSSARY ============ Flow Monitor - a hardware… |
1.3.6.1.4.1.9.9.772 | ciscoPfrMIB | 3 | 303 | This MIB module defines objects that describe Performance Routing (PfR). Standard routing protocols base routing decisions on re… |
1.3.6.1.4.1.9.9.773 | ciscoSwitchRateLimiterMIB | 3 | 28 | This MIB module defines management objects for the Switch Rate Limiter features on Cisco Layer 2 and Layer 3 devices. Rate limits … |
1.3.6.1.4.1.9.9.774 | ciscoVdcMIB | 3 | 90 | CISCO-VDC-MIB |
1.3.6.1.4.1.9.9.775 | ciscoSelectiveVrfDownloadMIB | 3 | 41 | This MIB module defines objects describing selective VRF download. The selective VRF download feature makes a best effort to dow… |
1.3.6.1.4.1.9.9.776 | ciscoNetflowLiteMIB | 3 | 56 | This MIB provides a method to configure Netflow-lite feature and get information in these areas: 1. Exporter config information a… |
1.3.6.1.4.1.9.9.777 | ciscoDsgIfExtMIB | 3 | 15 | A MIB module for extending the DSG-IF-MIB (ITU-T J.128 10/2008) to add objects which provide additional management information ab… |
1.3.6.1.4.1.9.9.779 | ciscoPmonMIB | 3 | 14 | This MIB module is for providing the port monitoring information. |
1.3.6.1.4.1.9.9.782 | ciscoSubscriberIdentityTcMIB | 0 | 0 | This MIB module defines textual conventions describing subscriber session identities. A subscriber session identity consists of … |
1.3.6.1.4.1.9.9.783 | ciscoDynamicTemplateTcMIB | 0 | 0 | This MIB module defines textual conventions used by the CISCO-DYNAMIC-TEMPLATE-MIB and MIB modules that use and expand on dynamic… |
1.3.6.1.4.1.9.9.784 | ciscoDynamicTemplateMIB | 3 | 152 | This MIB defines objects that describe dynamic templates. A dynamic template is a set of configuration attributes that a system … |
1.3.6.1.4.1.9.9.785 | ciscoSubscriberSessionTcMIB | 0 | 0 | This MIB module defines textual conventions describing subscriber sessions. |
1.3.6.1.4.1.9.9.786 | ciscoSubscriberSessionMIB | 3 | 187 | This MIB defines objects describing subscriber sessions, or more specifically, subscriber sessions terminated by a RAS. A subscr… |
1.3.6.1.4.1.9.9.789 | ciscoFlowMetadataMIB | 3 | 30 | The MIB module for managing Cisco medianet flow metadata. Metadata, in the simplest form, is data that qualifies other data. Flow… |
1.3.6.1.4.1.9.9.790 | ciscoSwitchCefMIB | 3 | 33 | This MIB module defines management objects for the CEF features on Cisco Layer 2 and Layer 3 devices. Definition of some of the t… |
1.3.6.1.4.1.9.9.791 | ciscoAppNavMIB | 2 | 51 | This MIB module defines SNMP management objects describing the AppNav technology. A device, which implements the AppNav technolog… |
1.3.6.1.4.1.9.9.793 | ciscoMspMIB | 3 | 54 | Objective of media services proxy is to provide media services to end-points and its flows identified by a set of protocols. Medi… |
1.3.6.1.4.1.9.9.798 | ciscoLocalAuthUserMIB | 3 | 40 | This MIB module defines objects describing users authenticated locally by a Network Access Server (NAS). + | | | … |
1.3.6.1.4.1.9.9.800 | ciscoMediatraceMIB | 3 | 191 | Mediatrace helps to isolate and troubleshoot network degradation problems by enabling a network administrator to discover an Inte… |
1.3.6.1.4.1.9.9.801 | ciscoFabricPathTopologyMIB | 3 | 40 | This MIB module defines managed objects that facilitate the management of Cisco's FabricPath Topology technology. |
1.3.6.1.4.1.9.9.803 | ciscoSwitchFabricMIB | 3 | 30 | This MIB module defined managed objects that facilitates the management of switching fabric information in a Cisco switch. |
1.3.6.1.4.1.9.9.804 | ciscoHardwareIpVerifyMIB | 3 | 13 | This MIB module defines management objects for configuration and monitoring of the Intrusion Detection System (IDS) that checks f… |
1.3.6.1.4.1.9.9.806 | ciscoL2natMIB | 2 | 80 | Network Address Translation (NAT) involves translating the source and or destination IP addresses of packets as they traverse fro… |
1.3.6.1.4.1.9.9.807 | ciscoVpcMIB | 3 | 73 | This MIB module defines MIB objects which provide management information for configuring and monitoring of Virtual Port Channel(V… |
1.3.6.1.4.1.9.9.808 | ciscoACLMIB | 2 | 87 | This MIB module defines objects that describe Cisco Access Control Lists (ACL). This MIB describes different objects that enable … |
... |