CISCO-TELEPRESENCE-EXCHANGE-SYSTEM-MIB
AI MIB Summary
The CISCO-TELEPRESENCE-EXCHANGE-SYSTEM-MIB provides SNMP access to the Cisco TelePresence Exchange System (CTX) administration servers for monitoring cluster node health, resource configurations, license states, and backup processes. It enables the tracking of call processing metrics, scheduling allocation failures, port usage statistics, and real-time alarm notifications for the six-node cluster architecture (Admin, Call Engine, and Database servers) and associated third-party video resources.
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 | <> | Admin 2 | | | - | | | | | | - | | | Call Engine 1 | <> | Call Engine 2 | | | - | | | | | | - | | | Database 1 | <> | Database 2 | | | - | \/
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
Main OID:
ciscoTelepresenceExchangeSystemMIB.1.3.6.1.4.1.9.9.758
148
Objects
Active
Status
7
Dependencies
Imported Objects
Objects
148 total| Object Name |
|---|
ciscoTelepresenceExchangeSystemMIBThe 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 | <> | Admin 2 | |
| - |
| | | |
| - |
| | Call Engine 1 | <> | Call Engine 2 | |
| - |
| | | |
| - |
| | Database 1 | <> | Database 2 | |
| - |
\/
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 MODULE-IDENTITY .1.3.6.1.4.1.9.9.758 |
ciscoTelepresenceExchangeSystemMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.758.0 |
ciscoCTXSysAdminServersStatusChgThis notification is sent when the ctxAdminServersStatus
changes.
ctxStatusChangeNotifyEnable controls whether this notification
is sent or not. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.758.0.1 |
ciscoCTXSysDatabaseServersStatusChgThis notification is sent when the ctxDatabaseServerStatus
changes.
ctxStatusChangeNotifyEnable controls whether this notification
is sent or not. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.758.0.2 |
ciscoCTXSysCallEnginesStatusChgThis notification is sent when the ctxCallEnginesStatus
changes.
ctxStatusChangeNotifyEnable controls whether this notification
is sent or not. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.758.0.3 |
ciscoCTXSysResourceStatusChgThis notification is sent when the ctxResourceStatus
changes.
ctxStatusChangeNotifyEnable controls whether this notification
is sent or not. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.758.0.4 |
ciscoCTXSysSystemConfigStatusChgThis notification is sent when the ctxSystemConfigStatus
changes.
ctxStatusChangeNotifyEnable controls whether this notification
is sent or not. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.758.0.5 |
ciscoCTXSysSystemBackupStatusChgThis notification is sent when the ctxSystemBackupStatus
changes.
ctxStatusChangeNotifyEnable controls whether this notification
is sent or not. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.758.0.6 |
ciscoCTXSysLicenseFailureThis notification is sent for the following license
violation failures:
1. DEMO License Errors
a. Warnings 5 days prior to Demo License expiration
if the user has not installed a permanent license.
b. Error message immediately after the Demo License
expiration if the user has not installed a permanent
license.
2. Volume Based Licensing Errors
a. Warning message that the system is reaching the
license capacity if using more than 75% of current
licenses
b. Error Message that the system is violating the current
licensing capacity and will soon start rejecting the
calls if using more than 100% and less than 150% of
available licenses
c. Error message that the system will reject calls if
claiming more than 150% of available licenses.
ctxLicenseAlarmNotifyEnable controls whether this
notification is sent or not. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.758.0.7 |
ciscoCTXSysUserAuthFailureThis notification will be sent when a user authentication
failure results in CTX System.
1. User authentication errors while trying to log into
the CTX System Admin UI.
2. User authentication errors while trying to log into
the CTX System CLI.
ctxAuthFailureNotifyEnable controls whether this notification
is sent or not. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.758.0.8 |
ciscoCTXSysClusterNodeDownThis notification will be sent when there is a network
connectivity or probe monitor failure to the cluster node from
the admin server.
ctxClusterNodeAlarmNotifyEnable controls whether this
notification is sent or not. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.758.0.9 |
ciscoCTXSysClusterNodeUpThis notification will be sent when the cluster node
connectivity is restored or when the probe monitor is successful
in monitoring the node after being down.
ctxClusterNodeAlarmNotifyEnable controls whether this
notification is sent or not. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.758.0.10 |
ciscoCTXSysResourceDownThis notification will be sent when there is a network
connectivity or probe monitor failure to the resource. This can
be a SIP OPTION PING, XMLRPC, or network connectivity failure.
The ctxNotifyMessage will contain the failure details.
ctxResourceAlarmNotifyEnable controls whether this
notification is sent or not. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.758.0.11 |
ciscoCTXSysResourceUpThis notification will be sent when the resource connectivity
is restored or when the probe monitor is successful in
monitoring the resource after being down.
ctxResourceAlarmNotifyEnable controls whether this
notification is sent or not. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.758.0.12 |
ciscoCTXSysResourceAllocFailureThis notification will be sent when a resource allocation
failure occurs.
ctxResourceAlarmNotifyEnable controls whether this
notification is sent or not. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.758.0.13 |
ciscoCTXSysCallSetupFailureThis notification will be sent when there is a call
setup/routing failure between the CTX System and a resource.
The cause for the setup failure will be detailed in
ctxNotifyMessage.
ctxCallFailureNotifyEnable controls whether this
notification is sent or not. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.758.0.14 |
ciscoCTXSysCallAbnormalDisconnectThis notification will be sent when there is an abnormal
call disconnect.
The call disconnect reason will be detailed in
ctxNotifyMessage.
ctxCallFailureNotifyEnable controls whether this
notification is sent or not. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.758.0.15 |
ciscoCTXSysErrorHistoryEventThis notification is sent when a new ctxErrorHistoryEntry
is created.
If the event being logged does not have an organization
name, this varbind entry will be an empty string value.
ctxErrorHistoryEventNotifyEnable controls whether this
notification is sent or not. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.758.0.16 |
ciscoTelepresenceExchangeSystemMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.758.1 |
ctxConfigObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.758.1.1 |
ctxServiceProviderTableThis table specifies the configuration information
for service providers as they are configured in the
CTX System. Service provider entries provide a logical
grouping of regions, organizations, and resources. SEQUENCE OF CtxServiceProviderEntry .1.3.6.1.4.1.9.9.758.1.1.1 |
ctxServiceProviderEntryEach entry describes a service provider entry as
configured in the CTX System. CtxServiceProviderEntry .1.3.6.1.4.1.9.9.758.1.1.1.1 |
ctxServiceProviderIndexService provider snmp instance configuration index. CtxIndex .1.3.6.1.4.1.9.9.758.1.1.1.1.1 |
ctxServiceProviderKeyThis object specifies the service provider ID key.ro CtxKeyId .1.3.6.1.4.1.9.9.758.1.1.1.1.2 |
ctxServiceProviderNameThis object specifies the service provider name as configured
in the CTX System.ro DisplayString .1.3.6.1.4.1.9.9.758.1.1.1.1.3 |
ctxServiceProviderDescrThis object specifies the service provider description
as configured in the CTX System.ro OCTET STRING .1.3.6.1.4.1.9.9.758.1.1.1.1.4 |
ctxServiceProviderHDNumberThis object specifies the service provider help desk
number. This number is normally in the e.164 format.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.9.758.1.1.1.1.5 |
ctxRegionTableThis table specifies the configuration information
for regions as they are configured in the CTX System.
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. SEQUENCE OF CtxRegionEntry .1.3.6.1.4.1.9.9.758.1.1.2 |
ctxRegionEntryEach entry describes a region entry as
configured in the CTX System. CtxRegionEntry .1.3.6.1.4.1.9.9.758.1.1.2.1 |
ctxRegionIndexRegion snmp instance configuration index. CtxIndex .1.3.6.1.4.1.9.9.758.1.1.2.1.1 |
ctxRegionKeyThis object specifies the region entry ID key as
generated by the CTX System when the entry
entry was configured.ro CtxKeyId .1.3.6.1.4.1.9.9.758.1.1.2.1.2 |
ctxRegionNameThis object specifies the region name as configured in
the CTX System.ro DisplayString .1.3.6.1.4.1.9.9.758.1.1.2.1.3 |
ctxRegionDescrThis object specifies the region description as configured
in the CTX System.ro OCTET STRING .1.3.6.1.4.1.9.9.758.1.1.2.1.4 |
ctxRegionServiceProviderKeyRef1This object references the ctxServiceProviderKey object
from the ctxServiceProviderEntry table. This key matches
the service provider key. This key provides an
association reference to the service provider entry that
is associated to this region entry.
This object maybe null or empty if no reference is provided.
See MIB description under 'Configuration Tables and Linking'
for a detailed example.ro CtxKeyId .1.3.6.1.4.1.9.9.758.1.1.2.1.5 |
ctxOrganizationTableThis table specifies the configuration information
for an organization as they are configured in the
CTX System. Organization entries provide a logical
grouping of customer endpoints and resources. SEQUENCE OF CtxOrganizationEntry .1.3.6.1.4.1.9.9.758.1.1.3 |
ctxOrganizationEntryEach entry represents an organization configuration
entry as configured in the CTX system. CtxOrganizationEntry .1.3.6.1.4.1.9.9.758.1.1.3.1 |
ctxOrganizationIndexOrganization snmp instance configuration index. CtxIndex .1.3.6.1.4.1.9.9.758.1.1.3.1.1 |
ctxOrganizationKeyThis object specifies the organization ID key as
generated by the CTX System when the organization
entry was configured.ro CtxKeyId .1.3.6.1.4.1.9.9.758.1.1.3.1.2 |
ctxOrganizationNameThis object specifies the organization name as
configured in the CTX System.ro DisplayString .1.3.6.1.4.1.9.9.758.1.1.3.1.3 |
ctxOrganizationDescrThis object specifies the organization description
as configured in the CTX System.ro OCTET STRING .1.3.6.1.4.1.9.9.758.1.1.3.1.4 |
ctxOrganizationMaxPortsThis object specifies the organization maximum ports for
scheduled meetings.
The value of 0 indicates undefined.ro CtxPorts .1.3.6.1.4.1.9.9.758.1.1.3.1.5 |
ctxOrganizationDirectDialThis object specifies the organization direct dial enabled
flag as configured in the CTX System. If direct dial calls
are allowed, this value will be TRUE. If direct dial calls
are not allowed, this value will be FALSE.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.758.1.1.3.1.6 |
ctxOrganizationServiceProviderKeyRef1This object references the ctxServiceProviderKey object
from the ctxServiceProviderEntry table. This key matches
the service provider key. This key provides an
association reference to the service provider entry that
is associated to this region entry.
This object maybe null or empty if no reference is provided.
See MIB description under 'Configuration Tables and Linking'
for a detailed example.ro CtxKeyId .1.3.6.1.4.1.9.9.758.1.1.3.1.7 |
ctxResourceObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.758.1.1.4 |
ctxResourceTableThis table specifies the configuration information
for resources as they are configured in the
CTX System.
A resource is server or network device that the CTX
System includes in configuration to provide call
signaling, media services, scheduling, or other function.
A resource may have additional configuration items,
such as ctxSipConfigTable. Each of the other
ctxResourceObjects tables are indexed by this resource
entry. If a resource has SIP configurations, there
will be a entry in the ctxSipConfigEntry indexed by
this ctxResourceIndex.
|- 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. SEQUENCE OF CtxResourceEntry .1.3.6.1.4.1.9.9.758.1.1.4.1 |
ctxResourceEntryEach entry represents a resource configuration
entry as configured in the CTX system. CtxResourceEntry .1.3.6.1.4.1.9.9.758.1.1.4.1.1 |
ctxResourceIndexResource snmp instance configuration index. CtxIndex .1.3.6.1.4.1.9.9.758.1.1.4.1.1.1 |
ctxResourceKeyThis object specifies the resource ID key as
generated by the CTX System when the resource
entry was configured.
This key is a globally unique across all configuration
tables and entries. This key will persist upon restart
and reboot.ro CtxKeyId .1.3.6.1.4.1.9.9.758.1.1.4.1.1.2 |
ctxResourceNameThis object specifies the resource name as configured
in the CTX System.ro DisplayString .1.3.6.1.4.1.9.9.758.1.1.4.1.1.3 |
ctxResourceDescrThis object specifies the resource configuration as
configured in the CTX System.ro OCTET STRING .1.3.6.1.4.1.9.9.758.1.1.4.1.1.4 |
ctxResourceMgmtIPTypeThis object specifies the management IP address type
for the resource as configured in the CTX System.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.758.1.1.4.1.1.5 |
ctxResourceMgmtIPAddrThis object specifies the management IP for the
resource as configured in the CTX System. This IP
address is used for provisioning, monitoring, and
resource probes.
The IP address 0.0.0.0 will be used if the resource does
not have a management IP address configured.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.758.1.1.4.1.1.6 |
ctxResourceDeviceTypeThis object specifies the resource device type as
configured in the CTX System.ro CtxResourceType .1.3.6.1.4.1.9.9.758.1.1.4.1.1.7 |
ctxResourceRegionKeyRef1This object references the ctxRegionKey object
from the ctxRegionEntry table. This key matches
the region key. This key provides an association
reference to the region entry that is associated to
this resource entry.
This object maybe null or empty if no reference is provided.
See MIB description under 'Configuration Tables and Linking'
for a detailed example.ro CtxKeyId .1.3.6.1.4.1.9.9.758.1.1.4.1.1.8 |
ctxSipConfigTableThis table specifies the SIP configuration attributes
for a resource. Only resources that have SIP attributes
will have an entry in this table. SEQUENCE OF CtxSipConfigEntry .1.3.6.1.4.1.9.9.758.1.1.4.2 |
ctxSipConfigEntryEach entry describes the SIP attributes for a resource
as configured in the CTX System.
As described in ctxResourceTable description, this
table is indexed by the ctxResourceIndex. Only entries
that have SIP attributes will have an entry in this
table. CtxSipConfigEntry .1.3.6.1.4.1.9.9.758.1.1.4.2.1 |
ctxSipIpTypeThis object specifies the SIP IP address type
for the resource as configured in the CTX System.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.758.1.1.4.2.1.1 |
ctxSipIpAddrThis object specifies the SIP signaling IP for the
resource as configured in the CTX System. This IP
address is used for signaling and for SIP OPTION
PING resource probes.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.758.1.1.4.2.1.2 |
ctxSipPortThis object specifies the SIP port for the resource
as configured in the CTX System.ro CiscoPort (CISCO-TC) .1.3.6.1.4.1.9.9.758.1.1.4.2.1.3 |
ctxSipTransportProtoThis object specifies the SIP transport protocol type
as configured in the CTX System.ro CtxSIPProtocolType .1.3.6.1.4.1.9.9.758.1.1.4.2.1.4 |
ctxMediaCapacityConfigTableThis table specifies the media capacity configuration
attributes for a resource. Only resources that have
media capacity attributes will have an entry in this
table. SEQUENCE OF CtxMediaCapacityConfigEntry .1.3.6.1.4.1.9.9.758.1.1.4.3 |
ctxMediaCapacityConfigEntryEach entry describes the media capacity attributes for
a resource as configured in the CTX System.
As described in ctxResourceTable description, this
table is indexed by the ctxResourceIndex. Only entries
that have media capacity attributes will have an entry
in this table. CtxMediaCapacityConfigEntry .1.3.6.1.4.1.9.9.758.1.1.4.3.1 |
ctxMediaCapacityMaxPortsThis object specifies the maximum port capacity for the
resource as configured in the CTX System.ro CtxPorts .1.3.6.1.4.1.9.9.758.1.1.4.3.1.1 |
ctxMediaCapacityLargeMeetingThis object specifies the large meeting reservation
allowed option for the resource as configured in
the CTX System.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.758.1.1.4.3.1.2 |
ctxMeetingConfigTableThis table specifies the meeting configuration
attributes for a resource. Only resources that have
meeting attributes will have an entry in this
table. SEQUENCE OF CtxMeetingConfigEntry .1.3.6.1.4.1.9.9.758.1.1.4.4 |
ctxMeetingConfigEntryEach entry describes the meeting attributes for
a resource as configured in the CTX System.
As described in ctxResourceTable description, this
table is indexed by the ctxResourceIndex. Only entries
that have meeting attributes will have an entry
in this table. CtxMeetingConfigEntry .1.3.6.1.4.1.9.9.758.1.1.4.4.1 |
ctxMeetingConfigStaticMinIdThis object specifies the vendor specific minimum static
meeting ID as configured in the CTX System.ro DisplayString .1.3.6.1.4.1.9.9.758.1.1.4.4.1.1 |
ctxMeetingConfigStaticMaxIdThis object specifies the vendor specific maximum static
meeting ID as configured in the CTX System.ro DisplayString .1.3.6.1.4.1.9.9.758.1.1.4.4.1.2 |
ctxMeetingConfigInterOpMinIdThis object specifies the vendor specific minimum interOp
meeting ID as configured in the CTX System.ro DisplayString .1.3.6.1.4.1.9.9.758.1.1.4.4.1.3 |
ctxMeetingConfigInterOpMaxIdThis object specifies the vendor specific maximum interOp
meeting ID as configured in the CTX System.ro DisplayString .1.3.6.1.4.1.9.9.758.1.1.4.4.1.4 |
ctxClusterNodeTableThis table specifies the configuration information
for cluster nodes as they are configured in the
CTX System.
A cluster node is a server within the CTX System, such as
admin server, call engine server, or database server. SEQUENCE OF CtxClusterNodeEntry .1.3.6.1.4.1.9.9.758.1.1.5 |
ctxClusterNodeEntryEach entry describes a cluster node entry as configured
in the CTX System. CtxClusterNodeEntry .1.3.6.1.4.1.9.9.758.1.1.5.1 |
ctxClusterNodeIndexCluster node snmp instance configuration index. CtxIndex .1.3.6.1.4.1.9.9.758.1.1.5.1.1 |
ctxClusterNodeKeyThis object specifies the cluster node ID key as
generated by the CTX System when the cluster node
entry was configured.ro CtxKeyId .1.3.6.1.4.1.9.9.758.1.1.5.1.2 |
ctxClusterNodeNameThis object specifies the cluster node name as configured
in the CTX system.ro DisplayString .1.3.6.1.4.1.9.9.758.1.1.5.1.3 |
ctxClusterNodeHostNameThis object specifies the cluster node hostname as
configured in the CTX System.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.9.758.1.1.5.1.4 |
ctxClusterNodeIPTypeThis object specifies the cluster node IP address type
as configured in the CTX System.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.758.1.1.5.1.5 |
ctxClusterNodeIPAddrThis object specifies the cluster node IP address as
configured in the CTX System.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.758.1.1.5.1.6 |
ctxClusterNodeClusterNameThis object specifies the cluster node cluster name as
configured in the CTX System.ro DisplayString .1.3.6.1.4.1.9.9.758.1.1.5.1.7 |
ctxClusterNodeTypeThis object specifies the cluster node type as
configured in the CTX System.ro CtxClusterNodeTypes .1.3.6.1.4.1.9.9.758.1.1.5.1.8 |
ctxClusterNodeOperStateThis object specifies the operational state of the
cluster node. The operational state is set by the
CTX System based on configuration and proactive
monitoring of the cluster node.
See the textual convention CtxResourceOperState
for a detail description of the various states.ro CtxResourceOperState .1.3.6.1.4.1.9.9.758.1.1.5.1.9 |
ctxSystemStatusObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.758.1.2 |
ctxAdminServersStatusThis object specifies an overall system health
status state for the cluster admin server nodes. This
state is an indicator of the CTX System functional
health in terms of the admin functions.
The ctxAdminServersStatusChg notification provides
real-time alerts for when this state changes. A
ctxNotifyMessage will detail the reason why the
state changed.ro CtxHealthStates .1.3.6.1.4.1.9.9.758.1.2.1 |
ctxCallEnginesStatusThis object specifies an overall system health
status state for the cluster engine server nodes. This
state is an indicator of the CTX System functional
health in terms of the call processing engine functions.
The ctxCallEnginesStatusChg notification provides
real-time alerts for when this state changes. A
ctxNotifyMessage will detail the reason why the
state changed.ro CtxHealthStates .1.3.6.1.4.1.9.9.758.1.2.2 |
ctxDatabaseServersStatusThis object specifies an overall system health
status state for the cluster database server nodes. This
state is an indicator of the CTX System functional
health in terms of the database server functions.
The ctxDatabaseServersStatusChg notification provides
real-time alerts for when this state changes. A
ctxNotifyMessage will detail the reason why the
state changed.ro CtxHealthStates .1.3.6.1.4.1.9.9.758.1.2.3 |
ctxResourceStatusThis object specifies an overall system health
status state for the resources configured. This
state is an indicator of the CTX System functional
health in terms of the resource dependencies.
The ctxResourceStatusChg notification provides
real-time alerts for when this state changes. A
ctxNotifyMessage will detail the reason why the
state changed.ro CtxHealthStates .1.3.6.1.4.1.9.9.758.1.2.4 |
ctxSystemConfigStatusThis object specifies an overall system health
status state for the system configuration. This
state is an indicator of the CTX System functional
health in terms of the overall configuration.
The ctxSystemConfigStatusChg notification provides
real-time alerts for when this state changes. A
ctxNotifyMessage will detail the reason why the
state changed.ro CtxHealthStates .1.3.6.1.4.1.9.9.758.1.2.5 |
ctxSystemBackupStatusThis object specifies an overall system health
status state for the system backups. This
state is an indicator of the CTX System functional
health in terms of the overall system backups.
The ctxBackupStatusChg notification provides
real-time alerts for when this state changes. A
ctxNotifyMessage will detail the reason why the
state changed.ro CtxHealthStates .1.3.6.1.4.1.9.9.758.1.2.6 |
ctxStatisticsObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.758.1.3 |
ctxResourceStatsTableThis table specifies the run-time resource statistics. SEQUENCE OF CtxResourceStatsEntry .1.3.6.1.4.1.9.9.758.1.3.1 |
ctxResourceStatsEntryEach entry describes an individual resource and
statistics for it.
This table is indexed by the ctxResourceIndex. All
resources will have an entry in this table to define
common resource statistics, such as operational state. CtxResourceStatsEntry .1.3.6.1.4.1.9.9.758.1.3.1.1 |
ctxResourceOperStateThis object specifies the operational state of the
resource.
The operational state is set by the
CTX System based on configuration and proactive
monitoring of the resource.
See the textual convention CtxResourceOperState
for a detail description of the various states.ro CtxResourceOperState .1.3.6.1.4.1.9.9.758.1.3.1.1.1 |
ctxResourceUnavailTransThis object specifies a counter that increments when
the resource transitions to unreachable or failed state from
another state. The management entity can use this to
track the operational stability of the resource.ro Counter32 UNITS "occurrences" .1.3.6.1.4.1.9.9.758.1.3.1.1.2 |
ctxResourceUnavailDurationDefines the total time in seconds that the resource was in
either the failed or unreachable states. This counter keeps
track of time in seconds on how much the resource stays in
the failed and unreachable states.
The duration is accumulative from SNMP start time and will
reset to zero when the snmp agent is restarted.ro Counter32 UNITS "seconds" .1.3.6.1.4.1.9.9.758.1.3.1.1.3 |
ctxResourceCallSetupFailuresThis object specifies a counter that increments every time
a call fails to be setup correctly to this resource.
Miss-dialed numbers are excluded and not considered a
failure.ro Counter32 UNITS "occurrences" .1.3.6.1.4.1.9.9.758.1.3.1.1.4 |
ctxAllocStatsTableThis table specifies the run-time scheduling port
allocation statistics. SEQUENCE OF CtxAllocStatsEntry .1.3.6.1.4.1.9.9.758.1.3.2 |
ctxAllocStatsEntryEach entry describes an individual resource and
statistics for media port allocations.
This table is indexed by the ctxResourceIndex. Only
resources that require port allocations will have
an entry in this table. CtxAllocStatsEntry .1.3.6.1.4.1.9.9.758.1.3.2.1 |
ctxAllocActivePortsThis object identifies the active in-use ports for the
resource.ro CtxPorts .1.3.6.1.4.1.9.9.758.1.3.2.1.1 |
ctxAllocAvailPortsThis object identifies the available ports for the
resource.ro CtxPorts .1.3.6.1.4.1.9.9.758.1.3.2.1.2 |
ctxAllocFailuresThis object increments when there are not enough port resources
available to process the requested allocation or if there is an
error allocating the ports.ro Counter32 UNITS "failures" .1.3.6.1.4.1.9.9.758.1.3.2.1.3 |
ctxAllocOutOfPortsThis object increments when there are not enough port resources
available to process the requested allocation.ro Counter32 UNITS "occurrences" .1.3.6.1.4.1.9.9.758.1.3.2.1.4 |
ctxRegionStatsTableThis table specifies the run-time statistics for regions
for scheduling port allocations and call setup failures.
This table is similar to the ctxAllocStatsTable table,
except this table provides statistics per region for
all resources. SEQUENCE OF CtxRegionStatsEntry .1.3.6.1.4.1.9.9.758.1.3.3 |
ctxRegionStatsEntryEach entry describes statistics for a region.
This table is indexed by the ctxRegionIndex. CtxRegionStatsEntry .1.3.6.1.4.1.9.9.758.1.3.3.1 |
ctxRegionCallSetupFailuresThis object specifies a counter that increments every time
a call fails to be setup correctly in this region. Mis-dialed
numbers are excluded and not considered a failure.ro Counter32 UNITS "failures" .1.3.6.1.4.1.9.9.758.1.3.3.1.1 |
ctxAllocPoolActivePortsThis object identifies the active in-use ports for the
region.ro CtxPorts .1.3.6.1.4.1.9.9.758.1.3.3.1.2 |
ctxAllocPoolAvailPortsThis object identifies the available ports for resources
within the region.ro CtxPorts .1.3.6.1.4.1.9.9.758.1.3.3.1.3 |
ctxAllocPoolAllocFailuresThis object increments when there are not enough port resources
available to process the requested allocation or if there is an
error allocating the port for the given region.ro Counter32 UNITS "failures" .1.3.6.1.4.1.9.9.758.1.3.3.1.4 |
ctxAllocPoolAllocOutOfPortsThis object increments when there are not enough port resources
available to process the requested allocation for the given
region resource pool.ro Counter32 UNITS "occurrences" .1.3.6.1.4.1.9.9.758.1.3.3.1.5 |
ctxAllocPeakHistory OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.758.1.3.4 |
ctxPeakHistMaxIntervalsThis object specifies the number of time intervals kept in the
history tables ctxPeakHistAllocTable and
ctxPeakHistAllocPoolTable.
The default is 96 intervals. 96 intervals at the
ctxPeakHistIntTime default of 15 minutes stores peak
values for 24 hours.
A value of 0 will disable peak history tables from collecting
data.
The minimum value is 5 with a maximum of 1440.
Changing this value will reset and clear both
ctxPeakHistAllocTable and ctxPeakHistAllocPoolTable table
entries.rw Unsigned32 (0 | 5..1440) UNITS "intervals" .1.3.6.1.4.1.9.9.758.1.3.4.1 |
ctxPeakHistIntTimeThis object specifies the time interval in minutes.
Default is 15 minutes.
The minimum interval time is 1 and the maximum is 1440
minutes.
Changing this value will reset and clear both
ctxPeakHistAllocTable and ctxPeakHistAllocPoolTable table
entries.rw Unsigned32 .1.3.6.1.4.1.9.9.758.1.3.4.2 |
ctxPeakHistAllocTableThis table specifies the run-time peak statistics for resource
port allocations. This table contains peak port allocations per
resource for ctxHistMaxIntervals. The management entity can
use this table to monitor the peak port allocations per
interval.
Setting ctxPeakHistMaxIntervals to 0 will disable this table and
clear all entries in table. SEQUENCE OF CtxPeakHistAllocEntry .1.3.6.1.4.1.9.9.758.1.3.4.3 |
ctxPeakHistAllocEntryEach entry describes a single peak time interval per resource.
This table is indexed by the ctxResourceIndex and
ctxPeakHistAllocIntIndex. Only resources that have port
allocations will have an entry in this table. CtxPeakHistAllocEntry .1.3.6.1.4.1.9.9.758.1.3.4.3.1 |
ctxPeakHistAllocIntIndexA monotonically increasing integer which is incremented for
every interval. Based on the allowed interval length the object
will not wrap for life of Device. The intent of this object is
to allow network management applications a mechanism that
allows
them to collect only those newly added interval. The network
management application only needs to save the index of the last
received interval and use it as a starting point when data is
next collected
from this table. Integer32 .1.3.6.1.4.1.9.9.758.1.3.4.3.1.1 |
ctxPeakHistAllocTSThis object specifies the start timestamp of the interval.
The interval end time is this time plus the
ctxPeakHistIntTime.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.758.1.3.4.3.1.2 |
ctxPeakHistAllocPortsThis object specifies the peak ports for the given interval.
This is the maximum port count during the interval time period.ro CtxPorts UNITS "ports" .1.3.6.1.4.1.9.9.758.1.3.4.3.1.3 |
ctxPeakHistAllocPoolTableThis table specifies the run-time peak port allocation
statistics for all resources within a region. This table
contains peak port allocations per region for
ctxHistMaxIntervals. The management entity can
use this table to monitor the peak port allocations per
interval.
Setting ctxPeakHistMaxIntervals to 0 will disable this table and
clear all entries in table. SEQUENCE OF CtxPeakHistAllocPoolEntry .1.3.6.1.4.1.9.9.758.1.3.4.4 |
ctxPeakHistAllocPoolEntryEach entry describes a single peak time interval per region.
This table is indexed by the ctxRegionIndex and
ctxPeakHistAllocPoolIntIndex. CtxPeakHistAllocPoolEntry .1.3.6.1.4.1.9.9.758.1.3.4.4.1 |
ctxPeakHistAllocPoolIntIndexA monotonically increasing integer which is incremented for
every interval. Based on the allowed interval length the object
will not wrap for life of Device. The intent of this object is
to allow network management applications a mechanism that
allows
them to collect only those newly added interval. The network
management application only needs to save the index of the last
received interval and use it as a starting point when data is
next collected
from this table. Integer32 .1.3.6.1.4.1.9.9.758.1.3.4.4.1.1 |
ctxPeakHistAllocPoolTSThis object specifies the start timestamp of the interval.
The interval end time is this time plus the
ctxPeakHistIntTime.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.758.1.3.4.4.1.2 |
ctxPeakHistAllocPoolPortsThis object specifies the peak ports for the given interval.
This is the maximum port count during the interval time
period.ro CtxPorts UNITS "ports" .1.3.6.1.4.1.9.9.758.1.3.4.4.1.3 |
ctxEventHistory OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.758.1.4 |
ctxErrorHistoryTableSizeThis object specifies the number of entries that the
ctxErrorHistoryTable can contain. When the
capacity of the ctxErrorHistoryTable is reached, the oldest
entry in the table will be deleted in order to accommodate the
new entry.
A value of '0' disables the history table. The default
value is set to 100 entries.rw Unsigned32 (0 | 25..2500) .1.3.6.1.4.1.9.9.758.1.4.1 |
ctxErrorHistoryMaxSeverityDefines the maximum severity of the event messages that the
history table will contain.
The default is notice(5), which can be changed by setting
the object.rw SyslogSeverity (CISCO-SYSLOG-MIB) .1.3.6.1.4.1.9.9.758.1.4.2 |
ctxErrorHistoryLastIndexThis object specifies the value of the
ctxErrorIndex object corresponding to the
last entry added into the table.
The management entity can use this object to determine
if a new entry has been added into the ctxErrorHistoryTable.ro CtxIndex .1.3.6.1.4.1.9.9.758.1.4.3 |
ctxErrorHistoryTableThis table contains a history of alarms and events generated
by the CTX system.
This table is a real-time history table of alarms and events
for the CTX System. When the table reaches its capacity
specified in ctxErrorHistoryTableSize, the agent will purge
the oldest entry.
The management entity can receive real-time events when an
object is inserted into this table by configuring
ctxErrorHistoryEventNotifyEnable to TRUE and receiving
ctxErrorHistoryEvent notifications SEQUENCE OF CtxErrorHistoryEntry .1.3.6.1.4.1.9.9.758.1.4.4 |
ctxErrorHistoryEntryAn entry is an event that was generated by the CTX System.
Events can be traps that were sent and other log messages. CtxErrorHistoryEntry .1.3.6.1.4.1.9.9.758.1.4.4.1 |
ctxErrorIndexError history snmp instance index. CtxIndex .1.3.6.1.4.1.9.9.758.1.4.4.1.1 |
ctxErrorKeyThis object specifies the error history key id.
A empty string maybe used if the key is not present.ro CtxKeyId .1.3.6.1.4.1.9.9.758.1.4.4.1.2 |
ctxErrorTimeStampThis object indicates the timestamp when the message or the
notification is generated by the CTX system. The timestamp
is UTC.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.758.1.4.4.1.3 |
ctxErrorSeverityThis object specifies the severity for the given message.ro SyslogSeverity (CISCO-SYSLOG-MIB) .1.3.6.1.4.1.9.9.758.1.4.4.1.4 |
ctxErrorAppNameThis object specifies the application name for the
message. AppNames are documented in the CTX System
user guide.ro DisplayString .1.3.6.1.4.1.9.9.758.1.4.4.1.5 |
ctxErrorAlarmIdThis object specifies the alarm ID for the event
as generated by the CTX System. Alarm ID's are
documented in the CTX System user guide.ro DisplayString .1.3.6.1.4.1.9.9.758.1.4.4.1.6 |
ctxErrorAttrValStrThis object specifies an attribute value pair in the format
of attr=value [attr=value ...]. This string is limited to
255 characters. If the attribute value string is larger
than 255 characters, the string will be truncated to 254
characters and an '*' will be inserted as the 255th
character as a way to indicate the message was truncated.
Attributes and associated values are documented in the
CTX System user guide.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.9.758.1.4.4.1.7 |
ctxErrorMessageThis object specifies the message text for the event.
This string is limited to 255 characters. If the
message string is larger than 255 characters, the string
will be truncated to 254 characters and an '*' will be
inserted as the 255th character as a way to indicate the
message was truncated.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.9.758.1.4.4.1.8 |
ctxNotifyObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.758.1.5 |
ctxNotifyMessageThis object specifies a message text for the notification
that is sent. This message will indicate a short
description detailing the cause for the trap. This is
intended as value added information for operational support
staff, such as value added information in a ticket that is
generated for this trap.
Event and trap de-duplication systems should ignore this
varbind as this entry will vary. De-duplication should be
performed on the other varbinds and should exclude both
ctxNotifyMesssage and ctxNotifyState.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.9.758.1.5.1 |
ctxNotifyConfigObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.758.1.5.2 |
ctxStatusChangeNotifyEnableThis object specifies if the status change traps
should be enabled or disabled. Setting this to TRUE
will enable the notifications. Setting this to FALSE
will disable the notifications.
Default is true/enabled.
This object controls the generation of the following
notifications:
ciscoCTXSysAdminServersStatusChg,
ciscoCTXSysDatabaseServersStatusChg,
ciscoCTXSysCallEnginesStatusChg,
ciscoCTXSysResourceStatusChg,
ciscoCTXSysSystemConfigStatusChg,
ciscoCTXSysSystemBackupStatusChgrw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.758.1.5.2.1 |
ctxLicenseAlarmNotifyEnableThis object specifies if the license alarm traps
should be enabled or disabled. Setting this to TRUE
will enable the notifications. Setting this to FALSE
will disable the notifications.
Default is true/enabled.
This object controls the generation of the following
notifications:
ciscoCTXSysLicenseFailurerw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.758.1.5.2.2 |
ctxAuthFailureNotifyEnableThis object specifies if the authentication failure traps
should be enabled or disabled. Setting this to TRUE
will enable the notifications. Setting this to FALSE
will disable the notifications.
The default setting for authentication failures is
FALSE/disabled in order to prevent unnecessary event
flooding.
This object controls the generation of the following
notifications:
ciscoCTXSysUserAuthFailurerw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.758.1.5.2.3 |
ctxClusterNodeAlarmNotifyEnableThis object specifies if the cluster node alarm traps
should be enabled or disabled. Setting this to TRUE
will enable the notifications. Setting this to FALSE
will disable the notifications.
Default is true/enabled.
This object controls the generation of the following
notifications:
ciscoCTXSysClusterNodeDown,
ciscoCTXSysClusterNodeUprw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.758.1.5.2.4 |
ctxResourceAlarmNotifyEnableThis object specifies if the resource alarm traps
should be enabled or disabled. Setting this to TRUE
will enable the notifications. Setting this to FALSE
will disable the notifications.
Default is true/enabled.
This object controls the generation of the following
notifications:
ciscoCTXSysResourceDown,
ciscoCTXSysResourceUp,
ciscoCTXSysResourceAllocFailurerw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.758.1.5.2.5 |
ctxCallFailureNotifyEnableThis object specifies if the call failure traps
should be enabled or disabled. Setting this to TRUE
will enable the notifications. Setting this to FALSE
will disable the notifications.
Default is true/enabled.
This object controls the generation of the following
notifications:
ciscoCTXSysCallSetupFailure,
ciscoCTXSysCallAbnormalDisconnectrw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.758.1.5.2.6 |
ctxErrorHistoryEventNotifyEnableThis object specifies if the error event history traps
should be enabled or disabled. Setting this to TRUE
will enable the notifications. Setting this to FALSE
will disable the notifications.
Notifications and other error logs are logged in the error
history table. Enabling this may cause duplication for events
that are in duplicate of other notifications. This may be the
desired behavior of the management system. Use
ctxErrorHistoryMaxSeverity to specify the maximum severity
level to be logged and sent via a notification.
Sending error history notifications are disabled by default.
This object controls the generation of the following
notifications:
ciscoCTXSysErrorHistoryEventrw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.758.1.5.2.7 |
ciscoTelepresenceExchangeSystemMIBConform OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.758.7 |
ciscoTelepresenceExchangeSystemMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.758.7.1 |
ciscoTelepresenceExchangeSystemMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.758.7.2 |