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 |-- Regions - Logical grouping
| |
| |--- Resources - General configs for resources
| | that are common to all resources
| |
| |--- SIP Configs - SIP configurations such as
| | SIP IP, port, and protocol
| |
| |--- Meeting Configs - Meeting configurations
| | such as Min/Max meeting ID's
| |
| |--- Capacity Configs - Media port counts,
| | large meeting support, etc.
| |-- Organizations
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
CtxHealthStates1 = normal2 = warning3 = errorThe CTX System high level status.
normal(1) - Normal operational state
warning(2) - The system is in a warning state. A
warning state needs attention, but is not affecting the system or solution from functioning. A warning state could be generated a redundant server is down or if a configured resource is down but is not affecting current call processing.
error(3) - Error state indicates that the system is
not fully usable and that immediate attention is required. Example of a error state is if both call engine servers are down. · Integer32
This 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.
ctxCallEnginesStatus
1.3.6.1.4.1.9.9.758.1.2.2
CtxHealthStates1 = normal2 = warning3 = errorThe CTX System high level status.
normal(1) - Normal operational state
warning(2) - The system is in a warning state. A
warning state needs attention, but is not affecting the system or solution from functioning. A warning state could be generated a redundant server is down or if a configured resource is down but is not affecting current call processing.
error(3) - Error state indicates that the system is
not fully usable and that immediate attention is required. Example of a error state is if both call engine servers are down. · Integer32
This 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.
ctxDatabaseServersStatus
1.3.6.1.4.1.9.9.758.1.2.3
CtxHealthStates1 = normal2 = warning3 = errorThe CTX System high level status.
normal(1) - Normal operational state
warning(2) - The system is in a warning state. A
warning state needs attention, but is not affecting the system or solution from functioning. A warning state could be generated a redundant server is down or if a configured resource is down but is not affecting current call processing.
error(3) - Error state indicates that the system is
not fully usable and that immediate attention is required. Example of a error state is if both call engine servers are down. · Integer32
This 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.
ctxResourceStatus
1.3.6.1.4.1.9.9.758.1.2.4
CtxHealthStates1 = normal2 = warning3 = errorThe CTX System high level status.
normal(1) - Normal operational state
warning(2) - The system is in a warning state. A
warning state needs attention, but is not affecting the system or solution from functioning. A warning state could be generated a redundant server is down or if a configured resource is down but is not affecting current call processing.
error(3) - Error state indicates that the system is
not fully usable and that immediate attention is required. Example of a error state is if both call engine servers are down. · Integer32
This 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.
ctxSystemConfigStatus
1.3.6.1.4.1.9.9.758.1.2.5
CtxHealthStates1 = normal2 = warning3 = errorThe CTX System high level status.
normal(1) - Normal operational state
warning(2) - The system is in a warning state. A
warning state needs attention, but is not affecting the system or solution from functioning. A warning state could be generated a redundant server is down or if a configured resource is down but is not affecting current call processing.
error(3) - Error state indicates that the system is
not fully usable and that immediate attention is required. Example of a error state is if both call engine servers are down. · Integer32
This 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.
ctxSystemBackupStatus
1.3.6.1.4.1.9.9.758.1.2.6
CtxHealthStates1 = normal2 = warning3 = errorThe CTX System high level status.
normal(1) - Normal operational state
warning(2) - The system is in a warning state. A
warning state needs attention, but is not affecting the system or solution from functioning. A warning state could be generated a redundant server is down or if a configured resource is down but is not affecting current call processing.
error(3) - Error state indicates that the system is
not fully usable and that immediate attention is required. Example of a error state is if both call engine servers are down. · Integer32
This 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.
ctxPeakHistMaxIntervals
1.3.6.1.4.1.9.9.758.1.3.4.1
Unsigned32 (0 | 5..1440) · intervals
This 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.
ctxPeakHistIntTime
1.3.6.1.4.1.9.9.758.1.3.4.2
Unsigned32 (1..1440) · minutes
This 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.
ctxErrorHistoryTableSize
1.3.6.1.4.1.9.9.758.1.4.1
Unsigned32 (0 | 25..2500)
This 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.
ctxErrorHistoryMaxSeverity
1.3.6.1.4.1.9.9.758.1.4.2
SyslogSeverity1 = emergency2 = alert3 = critical4 = error5 = warning6 = notice7 = info8 = debugThe severity of a syslog message. The enumeration values are equal to the values that syslog uses + 1. For example, with syslog, emergency=0.
'emergency' : system is unusable
'alert' : action must be taken immediately
'critical' : critical conditions
'error' : error conditions
'warning' : warning conditions
'notice' : normal but significant condition
'informational': informational messages
'debug' : debug-level messages.Reference: RFC 3164, Section 4.1 - syslog Message Parts · Integer32
Defines 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.
ctxErrorHistoryLastIndex
1.3.6.1.4.1.9.9.758.1.4.3
CtxIndexAn arbitrary (system-assigned) index for each instance.
If MIB index persistence is configured via the CTX System CLI interface, this index will persist upon restart and reboot.
When an entry is removed, this index will be cleared but will not be reused unless MIB index persistence is disabled or if persistence cache is cleared via the CTX System CLI interface. · Unsigned32 · hint d
This 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.
ctxNotifyMessage
1.3.6.1.4.1.9.9.758.1.5.1
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This 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.
ctxStatusChangeNotifyEnable
1.3.6.1.4.1.9.9.758.1.5.2.1
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This 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, ciscoCTXSysSystemBackupStatusChg
ctxLicenseAlarmNotifyEnable
1.3.6.1.4.1.9.9.758.1.5.2.2
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This 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:
ciscoCTXSysLicenseFailure
ctxAuthFailureNotifyEnable
1.3.6.1.4.1.9.9.758.1.5.2.3
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This 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:
ciscoCTXSysUserAuthFailure
ctxClusterNodeAlarmNotifyEnable
1.3.6.1.4.1.9.9.758.1.5.2.4
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This 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, ciscoCTXSysClusterNodeUp
ctxResourceAlarmNotifyEnable
1.3.6.1.4.1.9.9.758.1.5.2.5
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This 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, ciscoCTXSysResourceAllocFailure
ctxCallFailureNotifyEnable
1.3.6.1.4.1.9.9.758.1.5.2.6
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This 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, ciscoCTXSysCallAbnormalDisconnect
ctxErrorHistoryEventNotifyEnable
1.3.6.1.4.1.9.9.758.1.5.2.7
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This 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:
ciscoCTXSysErrorHistoryEvent
Table details
ctxServiceProviderTable
1.3.6.1.4.1.9.9.758.1.1.1
Index: ctxServiceProviderIndex
This 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.
ctxServiceProviderIndex
1.3.6.1.4.1.9.9.758.1.1.1.1.1
CtxIndexAn arbitrary (system-assigned) index for each instance.
If MIB index persistence is configured via the CTX System CLI interface, this index will persist upon restart and reboot.
When an entry is removed, this index will be cleared but will not be reused unless MIB index persistence is disabled or if persistence cache is cleared via the CTX System CLI interface. · Unsigned32 · hint d
Service provider snmp instance configuration index.
ctxServiceProviderKey
1.3.6.1.4.1.9.9.758.1.1.1.1.2
CtxKeyIdA key id is a globally unique key across all database tables and entries. This key will persist upon restart and reboot. This key is generated by the CTX System when the entry is added to the database.
The format of the key is a HEX string value. The value can be up to 32 hexadecimal characters. SIZE (0..32) · OCTET STRING · hint 4x-
This object specifies the service provider ID key.
ctxServiceProviderName
1.3.6.1.4.1.9.9.758.1.1.1.1.3
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..64) · OCTET STRING · hint 255a
This object specifies the service provider name as configured in the CTX System.
ctxServiceProviderDescr
1.3.6.1.4.1.9.9.758.1.1.1.1.4
OCTET STRING SIZE (0..255)
This object specifies the service provider description as configured in the CTX System.
ctxServiceProviderHDNumber
1.3.6.1.4.1.9.9.758.1.1.1.1.5
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This object specifies the service provider help desk number. This number is normally in the e.164 format.
ctxRegionTable
1.3.6.1.4.1.9.9.758.1.1.2
Index: ctxRegionIndex
This 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.
ctxRegionIndex
1.3.6.1.4.1.9.9.758.1.1.2.1.1
CtxIndexAn arbitrary (system-assigned) index for each instance.
If MIB index persistence is configured via the CTX System CLI interface, this index will persist upon restart and reboot.
When an entry is removed, this index will be cleared but will not be reused unless MIB index persistence is disabled or if persistence cache is cleared via the CTX System CLI interface. · Unsigned32 · hint d
Region snmp instance configuration index.
ctxRegionKey
1.3.6.1.4.1.9.9.758.1.1.2.1.2
CtxKeyIdA key id is a globally unique key across all database tables and entries. This key will persist upon restart and reboot. This key is generated by the CTX System when the entry is added to the database.
The format of the key is a HEX string value. The value can be up to 32 hexadecimal characters. SIZE (0..32) · OCTET STRING · hint 4x-
This object specifies the region entry ID key as generated by the CTX System when the entry entry was configured.
ctxRegionName
1.3.6.1.4.1.9.9.758.1.1.2.1.3
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..64) · OCTET STRING · hint 255a
This object specifies the region name as configured in the CTX System.
ctxRegionDescr
1.3.6.1.4.1.9.9.758.1.1.2.1.4
OCTET STRING SIZE (0..255)
This object specifies the region description as configured in the CTX System.
ctxRegionServiceProviderKeyRef1
1.3.6.1.4.1.9.9.758.1.1.2.1.5
CtxKeyIdA key id is a globally unique key across all database tables and entries. This key will persist upon restart and reboot. This key is generated by the CTX System when the entry is added to the database.
The format of the key is a HEX string value. The value can be up to 32 hexadecimal characters. SIZE (0..32) · OCTET STRING · hint 4x-
Reference: ctxServiceProviderKey
This 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.
ctxOrganizationTable
1.3.6.1.4.1.9.9.758.1.1.3
Index: ctxOrganizationIndex
This 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.
ctxOrganizationIndex
1.3.6.1.4.1.9.9.758.1.1.3.1.1
CtxIndexAn arbitrary (system-assigned) index for each instance.
If MIB index persistence is configured via the CTX System CLI interface, this index will persist upon restart and reboot.
When an entry is removed, this index will be cleared but will not be reused unless MIB index persistence is disabled or if persistence cache is cleared via the CTX System CLI interface. · Unsigned32 · hint d
Organization snmp instance configuration index.
ctxOrganizationKey
1.3.6.1.4.1.9.9.758.1.1.3.1.2
CtxKeyIdA key id is a globally unique key across all database tables and entries. This key will persist upon restart and reboot. This key is generated by the CTX System when the entry is added to the database.
The format of the key is a HEX string value. The value can be up to 32 hexadecimal characters. SIZE (0..32) · OCTET STRING · hint 4x-
This object specifies the organization ID key as generated by the CTX System when the organization entry was configured.
ctxOrganizationName
1.3.6.1.4.1.9.9.758.1.1.3.1.3
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..64) · OCTET STRING · hint 255a
This object specifies the organization name as configured in the CTX System.
ctxOrganizationDescr
1.3.6.1.4.1.9.9.758.1.1.3.1.4
OCTET STRING SIZE (0..255)
This object specifies the organization description as configured in the CTX System.
ctxOrganizationMaxPorts
1.3.6.1.4.1.9.9.758.1.1.3.1.5
CtxPortsA port is the media session port allocation for a resource. It is commonly referred to as a media video RTP stream for a multipoint switch and an audio RTP steam for ISDN/IVR. It is also known as a segment or screen. A Cisco TelePresence System 1000 uses one port while a Cisco TelePresence System 3000 uses 3 ports, one for each video screen. (1..65535) · Unsigned32 · hint d
This object specifies the organization maximum ports for scheduled meetings.
The value of 0 indicates undefined.
ctxOrganizationDirectDial
1.3.6.1.4.1.9.9.758.1.1.3.1.6
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This 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.
ctxOrganizationServiceProviderKeyRef1
1.3.6.1.4.1.9.9.758.1.1.3.1.7
CtxKeyIdA key id is a globally unique key across all database tables and entries. This key will persist upon restart and reboot. This key is generated by the CTX System when the entry is added to the database.
The format of the key is a HEX string value. The value can be up to 32 hexadecimal characters. SIZE (0..32) · OCTET STRING · hint 4x-
Reference: ctxServiceProviderKey
This 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.
ctxResourceTable
1.3.6.1.4.1.9.9.758.1.1.4.1
Index: ctxResourceIndex
This 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 |-- Regions - Logical grouping
| |
| |--- Resources - General configs for resources
| | that are common to all resources
| |
| |--- SIP Configs - SIP configurations such as
| | SIP IP, port, and protocol
| |
| |--- Meeting Configs - Meeting configurations
| | such as Min/Max meeting ID's
| |
| |--- Capacity Configs - Media port counts,
| | large meeting support, etc.
ctxResourceIndex
1.3.6.1.4.1.9.9.758.1.1.4.1.1.1
CtxIndexAn arbitrary (system-assigned) index for each instance.
If MIB index persistence is configured via the CTX System CLI interface, this index will persist upon restart and reboot.
When an entry is removed, this index will be cleared but will not be reused unless MIB index persistence is disabled or if persistence cache is cleared via the CTX System CLI interface. · Unsigned32 · hint d
Resource snmp instance configuration index.
ctxResourceKey
1.3.6.1.4.1.9.9.758.1.1.4.1.1.2
CtxKeyIdA key id is a globally unique key across all database tables and entries. This key will persist upon restart and reboot. This key is generated by the CTX System when the entry is added to the database.
The format of the key is a HEX string value. The value can be up to 32 hexadecimal characters. SIZE (0..32) · OCTET STRING · hint 4x-
This 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.
ctxResourceName
1.3.6.1.4.1.9.9.758.1.1.4.1.1.3
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..64) · OCTET STRING · hint 255a
This object specifies the resource name as configured in the CTX System.
ctxResourceDescr
1.3.6.1.4.1.9.9.758.1.1.4.1.1.4
OCTET STRING SIZE (0..255)
This object specifies the resource configuration as configured in the CTX System.
ctxResourceMgmtIPType
1.3.6.1.4.1.9.9.758.1.1.4.1.1.5
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType.
To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation.
Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
This object specifies the management IP address type for the resource as configured in the CTX System.
ctxResourceMgmtIPAddr
1.3.6.1.4.1.9.9.758.1.1.4.1.1.6
InetAddressDenotes a generic Internet address.
An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row.
The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
This 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.
This object specifies the resource device type as configured in the CTX System.
ctxResourceRegionKeyRef1
1.3.6.1.4.1.9.9.758.1.1.4.1.1.8
CtxKeyIdA key id is a globally unique key across all database tables and entries. This key will persist upon restart and reboot. This key is generated by the CTX System when the entry is added to the database.
The format of the key is a HEX string value. The value can be up to 32 hexadecimal characters. SIZE (0..32) · OCTET STRING · hint 4x-
Reference: ctxRegionKey
This 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.
ctxSipConfigTable
1.3.6.1.4.1.9.9.758.1.1.4.2
Index: ctxResourceIndex
This table specifies the SIP configuration attributes for a resource. Only resources that have SIP attributes will have an entry in this table.
ctxSipIpType
1.3.6.1.4.1.9.9.758.1.1.4.2.1.1
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType.
To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation.
Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
This object specifies the SIP IP address type for the resource as configured in the CTX System.
ctxSipIpAddr
1.3.6.1.4.1.9.9.758.1.1.4.2.1.2
InetAddressDenotes a generic Internet address.
An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row.
The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
This 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.
ctxSipPort
1.3.6.1.4.1.9.9.758.1.1.4.2.1.3
CiscoPortThe TCP or UDP port number range.Reference: Transmission Control Protocol. J. Postel. RFC793, User Datagram Protocol. J. Postel. RFC768 (0..65535) · Integer32
This object specifies the SIP port for the resource as configured in the CTX System.
ctxSipTransportProto
1.3.6.1.4.1.9.9.758.1.1.4.2.1.4
CtxSIPProtocolType1 = tcp2 = udp3 = tlsThe SIP transport protocol in use.
tcp(1) - connection oriented transport
udp(2) - connectionless transport
tls(3) - Secured connection oriented transport · Integer32
This object specifies the SIP transport protocol type as configured in the CTX System.
ctxMediaCapacityConfigTable
1.3.6.1.4.1.9.9.758.1.1.4.3
Index: ctxResourceIndex
This table specifies the media capacity configuration attributes for a resource. Only resources that have media capacity attributes will have an entry in this table.
ctxMediaCapacityMaxPorts
1.3.6.1.4.1.9.9.758.1.1.4.3.1.1
CtxPortsA port is the media session port allocation for a resource. It is commonly referred to as a media video RTP stream for a multipoint switch and an audio RTP steam for ISDN/IVR. It is also known as a segment or screen. A Cisco TelePresence System 1000 uses one port while a Cisco TelePresence System 3000 uses 3 ports, one for each video screen. (1..65535) · Unsigned32 · hint d
This object specifies the maximum port capacity for the resource as configured in the CTX System.
ctxMediaCapacityLargeMeeting
1.3.6.1.4.1.9.9.758.1.1.4.3.1.2
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This object specifies the large meeting reservation allowed option for the resource as configured in the CTX System.
ctxMeetingConfigTable
1.3.6.1.4.1.9.9.758.1.1.4.4
Index: ctxResourceIndex
This table specifies the meeting configuration attributes for a resource. Only resources that have meeting attributes will have an entry in this table.
ctxMeetingConfigStaticMinId
1.3.6.1.4.1.9.9.758.1.1.4.4.1.1
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..15) · OCTET STRING · hint 255a
This object specifies the vendor specific minimum static meeting ID as configured in the CTX System.
ctxMeetingConfigStaticMaxId
1.3.6.1.4.1.9.9.758.1.1.4.4.1.2
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..15) · OCTET STRING · hint 255a
This object specifies the vendor specific maximum static meeting ID as configured in the CTX System.
ctxMeetingConfigInterOpMinId
1.3.6.1.4.1.9.9.758.1.1.4.4.1.3
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..15) · OCTET STRING · hint 255a
This object specifies the vendor specific minimum interOp meeting ID as configured in the CTX System.
ctxMeetingConfigInterOpMaxId
1.3.6.1.4.1.9.9.758.1.1.4.4.1.4
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..15) · OCTET STRING · hint 255a
This object specifies the vendor specific maximum interOp meeting ID as configured in the CTX System.
ctxClusterNodeTable
1.3.6.1.4.1.9.9.758.1.1.5
Index: ctxClusterNodeIndex
This 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.
ctxClusterNodeIndex
1.3.6.1.4.1.9.9.758.1.1.5.1.1
CtxIndexAn arbitrary (system-assigned) index for each instance.
If MIB index persistence is configured via the CTX System CLI interface, this index will persist upon restart and reboot.
When an entry is removed, this index will be cleared but will not be reused unless MIB index persistence is disabled or if persistence cache is cleared via the CTX System CLI interface. · Unsigned32 · hint d
Cluster node snmp instance configuration index.
ctxClusterNodeKey
1.3.6.1.4.1.9.9.758.1.1.5.1.2
CtxKeyIdA key id is a globally unique key across all database tables and entries. This key will persist upon restart and reboot. This key is generated by the CTX System when the entry is added to the database.
The format of the key is a HEX string value. The value can be up to 32 hexadecimal characters. SIZE (0..32) · OCTET STRING · hint 4x-
This object specifies the cluster node ID key as generated by the CTX System when the cluster node entry was configured.
ctxClusterNodeName
1.3.6.1.4.1.9.9.758.1.1.5.1.3
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..64) · OCTET STRING · hint 255a
This object specifies the cluster node name as configured in the CTX system.
ctxClusterNodeHostName
1.3.6.1.4.1.9.9.758.1.1.5.1.4
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This object specifies the cluster node hostname as configured in the CTX System.
ctxClusterNodeIPType
1.3.6.1.4.1.9.9.758.1.1.5.1.5
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType.
To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation.
Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
This object specifies the cluster node IP address type as configured in the CTX System.
ctxClusterNodeIPAddr
1.3.6.1.4.1.9.9.758.1.1.5.1.6
InetAddressDenotes a generic Internet address.
An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row.
The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
This object specifies the cluster node IP address as configured in the CTX System.
ctxClusterNodeClusterName
1.3.6.1.4.1.9.9.758.1.1.5.1.7
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..64) · OCTET STRING · hint 255a
This object specifies the cluster node cluster name as configured in the CTX System.
ctxClusterNodeType
1.3.6.1.4.1.9.9.758.1.1.5.1.8
CtxClusterNodeTypes1 = admin2 = engine3 = dbThe types of cluster nodes.
admin(1) - CTX System administrative server
engine(2) - CTX System call processing engine server
db(3) - CTX System database server · Integer32
This object specifies the cluster node type as configured in the CTX System.
ctxClusterNodeOperState
1.3.6.1.4.1.9.9.758.1.1.5.1.9
CtxResourceOperState1 = operational2 = disabled3 = failed4 = maintenance5 = pending6 = standby7 = unreachableThe resource operational state. The operational state of a resource is determined by the CTX system configuration and proactive health probe monitoring of the resource. An example of a health check probe is a SIP Options Ping or XMLRPC ping.
operational(1) - Resource is fully operational and is successfully passing health probe validation checks.
disabled(2) - Resource has been administratively
disabled.
failed(3) - Resource has failed to respond to
consecutive health check probes or has failed due to an application failure on the resource. IP connectivity failures are indicated by the unreachable state. maintenance(4) - Resource is currently in maintenance mode. In this state, the resource may be up or down. Probe monitoring is not active on a device in this state.
pending(5) - Resource is currently pending a state
transition. When a device is added and fully configured, the device will be put into pending state till the health check probes have successfully passed. When passed the state will change to either operational or failed. A device that is put into maintenance mode will go into pending state till all calls are cleared from that device.
standby(6) - A resource device in this state is
considered fully operational, but is currently the standby server/resource. unreachable(7) - A resource will be in this state if the IP connectivity to the device is not functioning. · Integer32
This 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.
ctxResourceStatsTable
1.3.6.1.4.1.9.9.758.1.3.1
Index: ctxResourceIndex
This table specifies the run-time resource statistics.
ctxResourceOperState
1.3.6.1.4.1.9.9.758.1.3.1.1.1
CtxResourceOperState1 = operational2 = disabled3 = failed4 = maintenance5 = pending6 = standby7 = unreachableThe resource operational state. The operational state of a resource is determined by the CTX system configuration and proactive health probe monitoring of the resource. An example of a health check probe is a SIP Options Ping or XMLRPC ping.
operational(1) - Resource is fully operational and is successfully passing health probe validation checks.
disabled(2) - Resource has been administratively
disabled.
failed(3) - Resource has failed to respond to
consecutive health check probes or has failed due to an application failure on the resource. IP connectivity failures are indicated by the unreachable state. maintenance(4) - Resource is currently in maintenance mode. In this state, the resource may be up or down. Probe monitoring is not active on a device in this state.
pending(5) - Resource is currently pending a state
transition. When a device is added and fully configured, the device will be put into pending state till the health check probes have successfully passed. When passed the state will change to either operational or failed. A device that is put into maintenance mode will go into pending state till all calls are cleared from that device.
standby(6) - A resource device in this state is
considered fully operational, but is currently the standby server/resource. unreachable(7) - A resource will be in this state if the IP connectivity to the device is not functioning. · Integer32
This 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.
ctxResourceUnavailTrans
1.3.6.1.4.1.9.9.758.1.3.1.1.2
Counter32 · occurrences
This 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.
ctxResourceUnavailDuration
1.3.6.1.4.1.9.9.758.1.3.1.1.3
Counter32 · seconds
Defines 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.
ctxResourceCallSetupFailures
1.3.6.1.4.1.9.9.758.1.3.1.1.4
Counter32 · occurrences
This 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.
ctxAllocStatsTable
1.3.6.1.4.1.9.9.758.1.3.2
Index: ctxResourceIndex
This table specifies the run-time scheduling port allocation statistics.
ctxAllocActivePorts
1.3.6.1.4.1.9.9.758.1.3.2.1.1
CtxPortsA port is the media session port allocation for a resource. It is commonly referred to as a media video RTP stream for a multipoint switch and an audio RTP steam for ISDN/IVR. It is also known as a segment or screen. A Cisco TelePresence System 1000 uses one port while a Cisco TelePresence System 3000 uses 3 ports, one for each video screen. (1..65535) · Unsigned32 · hint d
This object identifies the active in-use ports for the resource.
ctxAllocAvailPorts
1.3.6.1.4.1.9.9.758.1.3.2.1.2
CtxPortsA port is the media session port allocation for a resource. It is commonly referred to as a media video RTP stream for a multipoint switch and an audio RTP steam for ISDN/IVR. It is also known as a segment or screen. A Cisco TelePresence System 1000 uses one port while a Cisco TelePresence System 3000 uses 3 ports, one for each video screen. (1..65535) · Unsigned32 · hint d
This object identifies the available ports for the resource.
ctxAllocFailures
1.3.6.1.4.1.9.9.758.1.3.2.1.3
Counter32 · failures
This object increments when there are not enough port resources available to process the requested allocation or if there is an error allocating the ports.
ctxAllocOutOfPorts
1.3.6.1.4.1.9.9.758.1.3.2.1.4
Counter32 · occurrences
This object increments when there are not enough port resources available to process the requested allocation.
ctxRegionStatsTable
1.3.6.1.4.1.9.9.758.1.3.3
Index: ctxRegionIndex
This 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.
ctxRegionCallSetupFailures
1.3.6.1.4.1.9.9.758.1.3.3.1.1
Counter32 · failures
This 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.
ctxAllocPoolActivePorts
1.3.6.1.4.1.9.9.758.1.3.3.1.2
CtxPortsA port is the media session port allocation for a resource. It is commonly referred to as a media video RTP stream for a multipoint switch and an audio RTP steam for ISDN/IVR. It is also known as a segment or screen. A Cisco TelePresence System 1000 uses one port while a Cisco TelePresence System 3000 uses 3 ports, one for each video screen. (1..65535) · Unsigned32 · hint d
This object identifies the active in-use ports for the region.
ctxAllocPoolAvailPorts
1.3.6.1.4.1.9.9.758.1.3.3.1.3
CtxPortsA port is the media session port allocation for a resource. It is commonly referred to as a media video RTP stream for a multipoint switch and an audio RTP steam for ISDN/IVR. It is also known as a segment or screen. A Cisco TelePresence System 1000 uses one port while a Cisco TelePresence System 3000 uses 3 ports, one for each video screen. (1..65535) · Unsigned32 · hint d
This object identifies the available ports for resources within the region.
ctxAllocPoolAllocFailures
1.3.6.1.4.1.9.9.758.1.3.3.1.4
Counter32 · failures
This 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.
ctxAllocPoolAllocOutOfPorts
1.3.6.1.4.1.9.9.758.1.3.3.1.5
Counter32 · occurrences
This object increments when there are not enough port resources available to process the requested allocation for the given region resource pool.
This 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.
ctxPeakHistAllocIntIndex
1.3.6.1.4.1.9.9.758.1.3.4.3.1.1
Integer32 (1..2147483647)
A 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.
ctxPeakHistAllocTS
1.3.6.1.4.1.9.9.758.1.3.4.3.1.2
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be
defined in the description of any object defined using this type.
If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
This object specifies the start timestamp of the interval. The interval end time is this time plus the ctxPeakHistIntTime.
ctxPeakHistAllocPorts
1.3.6.1.4.1.9.9.758.1.3.4.3.1.3
CtxPortsA port is the media session port allocation for a resource. It is commonly referred to as a media video RTP stream for a multipoint switch and an audio RTP steam for ISDN/IVR. It is also known as a segment or screen. A Cisco TelePresence System 1000 uses one port while a Cisco TelePresence System 3000 uses 3 ports, one for each video screen. (1..65535) · Unsigned32 · hint d · ports
This object specifies the peak ports for the given interval. This is the maximum port count during the interval time period.
This 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.
ctxPeakHistAllocPoolIntIndex
1.3.6.1.4.1.9.9.758.1.3.4.4.1.1
Integer32 (1..2147483647)
A 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.
ctxPeakHistAllocPoolTS
1.3.6.1.4.1.9.9.758.1.3.4.4.1.2
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be
defined in the description of any object defined using this type.
If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
This object specifies the start timestamp of the interval. The interval end time is this time plus the ctxPeakHistIntTime.
ctxPeakHistAllocPoolPorts
1.3.6.1.4.1.9.9.758.1.3.4.4.1.3
CtxPortsA port is the media session port allocation for a resource. It is commonly referred to as a media video RTP stream for a multipoint switch and an audio RTP steam for ISDN/IVR. It is also known as a segment or screen. A Cisco TelePresence System 1000 uses one port while a Cisco TelePresence System 3000 uses 3 ports, one for each video screen. (1..65535) · Unsigned32 · hint d · ports
This object specifies the peak ports for the given interval. This is the maximum port count during the interval time period.
ctxErrorHistoryTable
1.3.6.1.4.1.9.9.758.1.4.4
Index: ctxErrorIndex
This 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
ctxErrorIndex
1.3.6.1.4.1.9.9.758.1.4.4.1.1
CtxIndexAn arbitrary (system-assigned) index for each instance.
If MIB index persistence is configured via the CTX System CLI interface, this index will persist upon restart and reboot.
When an entry is removed, this index will be cleared but will not be reused unless MIB index persistence is disabled or if persistence cache is cleared via the CTX System CLI interface. · Unsigned32 · hint d
Error history snmp instance index.
ctxErrorKey
1.3.6.1.4.1.9.9.758.1.4.4.1.2
CtxKeyIdA key id is a globally unique key across all database tables and entries. This key will persist upon restart and reboot. This key is generated by the CTX System when the entry is added to the database.
The format of the key is a HEX string value. The value can be up to 32 hexadecimal characters. SIZE (0..32) · OCTET STRING · hint 4x-
This object specifies the error history key id.
A empty string maybe used if the key is not present.
ctxErrorTimeStamp
1.3.6.1.4.1.9.9.758.1.4.4.1.3
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be
defined in the description of any object defined using this type.
If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
This object indicates the timestamp when the message or the notification is generated by the CTX system. The timestamp is UTC.
ctxErrorSeverity
1.3.6.1.4.1.9.9.758.1.4.4.1.4
SyslogSeverity1 = emergency2 = alert3 = critical4 = error5 = warning6 = notice7 = info8 = debugThe severity of a syslog message. The enumeration values are equal to the values that syslog uses + 1. For example, with syslog, emergency=0.
'emergency' : system is unusable
'alert' : action must be taken immediately
'critical' : critical conditions
'error' : error conditions
'warning' : warning conditions
'notice' : normal but significant condition
'informational': informational messages
'debug' : debug-level messages.Reference: RFC 3164, Section 4.1 - syslog Message Parts · Integer32
This object specifies the severity for the given message.
ctxErrorAppName
1.3.6.1.4.1.9.9.758.1.4.4.1.5
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..48) · OCTET STRING · hint 255a
This object specifies the application name for the message. AppNames are documented in the CTX System user guide.
ctxErrorAlarmId
1.3.6.1.4.1.9.9.758.1.4.4.1.6
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..32) · OCTET STRING · hint 255a
This 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.
ctxErrorAttrValStr
1.3.6.1.4.1.9.9.758.1.4.4.1.7
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This 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.
ctxErrorMessage
1.3.6.1.4.1.9.9.758.1.4.4.1.8
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This 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.
Trap details
ciscoCTXSysAdminServersStatusChg
1.3.6.1.4.1.9.9.758.0.1
This notification is sent when the ctxAdminServersStatus changes.
ctxStatusChangeNotifyEnable controls whether this notification is sent or not.
ctxAdminServersStatus
1.3.6.1.4.1.9.9.758.1.2.1
CtxHealthStates1 = normal2 = warning3 = errorThe CTX System high level status.
normal(1) - Normal operational state
warning(2) - The system is in a warning state. A
warning state needs attention, but is not affecting the system or solution from functioning. A warning state could be generated a redundant server is down or if a configured resource is down but is not affecting current call processing.
error(3) - Error state indicates that the system is
not fully usable and that immediate attention is required. Example of a error state is if both call engine servers are down. · Integer32
This 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.
ctxNotifyMessage
1.3.6.1.4.1.9.9.758.1.5.1
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This 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.
ciscoCTXSysDatabaseServersStatusChg
1.3.6.1.4.1.9.9.758.0.2
This notification is sent when the ctxDatabaseServerStatus changes.
ctxStatusChangeNotifyEnable controls whether this notification is sent or not.
ctxDatabaseServersStatus
1.3.6.1.4.1.9.9.758.1.2.3
CtxHealthStates1 = normal2 = warning3 = errorThe CTX System high level status.
normal(1) - Normal operational state
warning(2) - The system is in a warning state. A
warning state needs attention, but is not affecting the system or solution from functioning. A warning state could be generated a redundant server is down or if a configured resource is down but is not affecting current call processing.
error(3) - Error state indicates that the system is
not fully usable and that immediate attention is required. Example of a error state is if both call engine servers are down. · Integer32
This 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.
ctxNotifyMessage
1.3.6.1.4.1.9.9.758.1.5.1
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This 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.
ciscoCTXSysCallEnginesStatusChg
1.3.6.1.4.1.9.9.758.0.3
This notification is sent when the ctxCallEnginesStatus changes.
ctxStatusChangeNotifyEnable controls whether this notification is sent or not.
ctxCallEnginesStatus
1.3.6.1.4.1.9.9.758.1.2.2
CtxHealthStates1 = normal2 = warning3 = errorThe CTX System high level status.
normal(1) - Normal operational state
warning(2) - The system is in a warning state. A
warning state needs attention, but is not affecting the system or solution from functioning. A warning state could be generated a redundant server is down or if a configured resource is down but is not affecting current call processing.
error(3) - Error state indicates that the system is
not fully usable and that immediate attention is required. Example of a error state is if both call engine servers are down. · Integer32
This 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.
ctxNotifyMessage
1.3.6.1.4.1.9.9.758.1.5.1
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This 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.
ciscoCTXSysResourceStatusChg
1.3.6.1.4.1.9.9.758.0.4
This notification is sent when the ctxResourceStatus changes.
ctxStatusChangeNotifyEnable controls whether this notification is sent or not.
ctxResourceStatus
1.3.6.1.4.1.9.9.758.1.2.4
CtxHealthStates1 = normal2 = warning3 = errorThe CTX System high level status.
normal(1) - Normal operational state
warning(2) - The system is in a warning state. A
warning state needs attention, but is not affecting the system or solution from functioning. A warning state could be generated a redundant server is down or if a configured resource is down but is not affecting current call processing.
error(3) - Error state indicates that the system is
not fully usable and that immediate attention is required. Example of a error state is if both call engine servers are down. · Integer32
This 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.
ctxNotifyMessage
1.3.6.1.4.1.9.9.758.1.5.1
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This 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.
ciscoCTXSysSystemConfigStatusChg
1.3.6.1.4.1.9.9.758.0.5
This notification is sent when the ctxSystemConfigStatus changes.
ctxStatusChangeNotifyEnable controls whether this notification is sent or not.
ctxSystemConfigStatus
1.3.6.1.4.1.9.9.758.1.2.5
CtxHealthStates1 = normal2 = warning3 = errorThe CTX System high level status.
normal(1) - Normal operational state
warning(2) - The system is in a warning state. A
warning state needs attention, but is not affecting the system or solution from functioning. A warning state could be generated a redundant server is down or if a configured resource is down but is not affecting current call processing.
error(3) - Error state indicates that the system is
not fully usable and that immediate attention is required. Example of a error state is if both call engine servers are down. · Integer32
This 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.
ctxNotifyMessage
1.3.6.1.4.1.9.9.758.1.5.1
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This 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.
ciscoCTXSysSystemBackupStatusChg
1.3.6.1.4.1.9.9.758.0.6
This notification is sent when the ctxSystemBackupStatus changes.
ctxStatusChangeNotifyEnable controls whether this notification is sent or not.
ctxSystemBackupStatus
1.3.6.1.4.1.9.9.758.1.2.6
CtxHealthStates1 = normal2 = warning3 = errorThe CTX System high level status.
normal(1) - Normal operational state
warning(2) - The system is in a warning state. A
warning state needs attention, but is not affecting the system or solution from functioning. A warning state could be generated a redundant server is down or if a configured resource is down but is not affecting current call processing.
error(3) - Error state indicates that the system is
not fully usable and that immediate attention is required. Example of a error state is if both call engine servers are down. · Integer32
This 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.
ctxNotifyMessage
1.3.6.1.4.1.9.9.758.1.5.1
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This 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.
ciscoCTXSysLicenseFailure
1.3.6.1.4.1.9.9.758.0.7
This 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.
ctxNotifyMessage
1.3.6.1.4.1.9.9.758.1.5.1
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This 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.
ciscoCTXSysUserAuthFailure
1.3.6.1.4.1.9.9.758.0.8
This 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.
ctxNotifyMessage
1.3.6.1.4.1.9.9.758.1.5.1
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This 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.
ciscoCTXSysClusterNodeDown
1.3.6.1.4.1.9.9.758.0.9
This 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.
ctxClusterNodeType
1.3.6.1.4.1.9.9.758.1.1.5.1.8
CtxClusterNodeTypes1 = admin2 = engine3 = dbThe types of cluster nodes.
admin(1) - CTX System administrative server
engine(2) - CTX System call processing engine server
db(3) - CTX System database server · Integer32
This object specifies the cluster node type as configured in the CTX System.
ctxClusterNodeName
1.3.6.1.4.1.9.9.758.1.1.5.1.3
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..64) · OCTET STRING · hint 255a
This object specifies the cluster node name as configured in the CTX system.
ctxNotifyMessage
1.3.6.1.4.1.9.9.758.1.5.1
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This 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.
ciscoCTXSysClusterNodeUp
1.3.6.1.4.1.9.9.758.0.10
This 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.
ctxClusterNodeType
1.3.6.1.4.1.9.9.758.1.1.5.1.8
CtxClusterNodeTypes1 = admin2 = engine3 = dbThe types of cluster nodes.
admin(1) - CTX System administrative server
engine(2) - CTX System call processing engine server
db(3) - CTX System database server · Integer32
This object specifies the cluster node type as configured in the CTX System.
ctxClusterNodeName
1.3.6.1.4.1.9.9.758.1.1.5.1.3
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..64) · OCTET STRING · hint 255a
This object specifies the cluster node name as configured in the CTX system.
ctxNotifyMessage
1.3.6.1.4.1.9.9.758.1.5.1
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This 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.
ciscoCTXSysResourceDown
1.3.6.1.4.1.9.9.758.0.11
This 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.
ctxResourceName
1.3.6.1.4.1.9.9.758.1.1.4.1.1.3
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..64) · OCTET STRING · hint 255a
This object specifies the resource name as configured in the CTX System.
This object specifies the resource device type as configured in the CTX System.
ctxRegionName
1.3.6.1.4.1.9.9.758.1.1.2.1.3
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..64) · OCTET STRING · hint 255a
This object specifies the region name as configured in the CTX System.
ctxNotifyMessage
1.3.6.1.4.1.9.9.758.1.5.1
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This 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.
ciscoCTXSysResourceUp
1.3.6.1.4.1.9.9.758.0.12
This 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.
ctxResourceName
1.3.6.1.4.1.9.9.758.1.1.4.1.1.3
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..64) · OCTET STRING · hint 255a
This object specifies the resource name as configured in the CTX System.
This object specifies the resource device type as configured in the CTX System.
ctxRegionName
1.3.6.1.4.1.9.9.758.1.1.2.1.3
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..64) · OCTET STRING · hint 255a
This object specifies the region name as configured in the CTX System.
ctxNotifyMessage
1.3.6.1.4.1.9.9.758.1.5.1
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This 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.
ciscoCTXSysResourceAllocFailure
1.3.6.1.4.1.9.9.758.0.13
This notification will be sent when a resource allocation failure occurs.
ctxResourceAlarmNotifyEnable controls whether this notification is sent or not.
ctxResourceName
1.3.6.1.4.1.9.9.758.1.1.4.1.1.3
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..64) · OCTET STRING · hint 255a
This object specifies the resource name as configured in the CTX System.
This object specifies the resource device type as configured in the CTX System.
ctxRegionKey
1.3.6.1.4.1.9.9.758.1.1.2.1.2
CtxKeyIdA key id is a globally unique key across all database tables and entries. This key will persist upon restart and reboot. This key is generated by the CTX System when the entry is added to the database.
The format of the key is a HEX string value. The value can be up to 32 hexadecimal characters. SIZE (0..32) · OCTET STRING · hint 4x-
This object specifies the region entry ID key as generated by the CTX System when the entry entry was configured.
ctxNotifyMessage
1.3.6.1.4.1.9.9.758.1.5.1
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This 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.
ciscoCTXSysCallSetupFailure
1.3.6.1.4.1.9.9.758.0.14
This 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.
ctxResourceName
1.3.6.1.4.1.9.9.758.1.1.4.1.1.3
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..64) · OCTET STRING · hint 255a
This object specifies the resource name as configured in the CTX System.
This object specifies the resource device type as configured in the CTX System.
ctxNotifyMessage
1.3.6.1.4.1.9.9.758.1.5.1
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This 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.
ciscoCTXSysCallAbnormalDisconnect
1.3.6.1.4.1.9.9.758.0.15
This 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.
ctxResourceName
1.3.6.1.4.1.9.9.758.1.1.4.1.1.3
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..64) · OCTET STRING · hint 255a
This object specifies the resource name as configured in the CTX System.
This object specifies the resource device type as configured in the CTX System.
ctxNotifyMessage
1.3.6.1.4.1.9.9.758.1.5.1
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This 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.
ciscoCTXSysErrorHistoryEvent
1.3.6.1.4.1.9.9.758.0.16
This 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.
ctxErrorKey
1.3.6.1.4.1.9.9.758.1.4.4.1.2
CtxKeyIdA key id is a globally unique key across all database tables and entries. This key will persist upon restart and reboot. This key is generated by the CTX System when the entry is added to the database.
The format of the key is a HEX string value. The value can be up to 32 hexadecimal characters. SIZE (0..32) · OCTET STRING · hint 4x-
This object specifies the error history key id.
A empty string maybe used if the key is not present.
ctxErrorSeverity
1.3.6.1.4.1.9.9.758.1.4.4.1.4
SyslogSeverity1 = emergency2 = alert3 = critical4 = error5 = warning6 = notice7 = info8 = debugThe severity of a syslog message. The enumeration values are equal to the values that syslog uses + 1. For example, with syslog, emergency=0.
'emergency' : system is unusable
'alert' : action must be taken immediately
'critical' : critical conditions
'error' : error conditions
'warning' : warning conditions
'notice' : normal but significant condition
'informational': informational messages
'debug' : debug-level messages.Reference: RFC 3164, Section 4.1 - syslog Message Parts · Integer32
This object specifies the severity for the given message.
ctxErrorAppName
1.3.6.1.4.1.9.9.758.1.4.4.1.5
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..48) · OCTET STRING · hint 255a
This object specifies the application name for the message. AppNames are documented in the CTX System user guide.
ctxErrorAlarmId
1.3.6.1.4.1.9.9.758.1.4.4.1.6
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..32) · OCTET STRING · hint 255a
This 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.
ctxErrorAttrValStr
1.3.6.1.4.1.9.9.758.1.4.4.1.7
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This 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.
ctxErrorMessage
1.3.6.1.4.1.9.9.758.1.4.4.1.8
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
This 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.