CXDataScope-MIB

All MIBs › CXDataScope-MIB

Category: Vendor: Memotec

Description: Manages data scope diagnostic and protocol analysis functions on CX Memotec devices.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is CXDataScope-MIB?

CXDataScope-MIB is a vendor-specific MIB for CX (Memotec) telecommunications/protocol-conversion devices, covering the "Data Scope" diagnostic and protocol-analysis feature that captures and logs protocol traffic for troubleshooting. It exposes objects describing the internal diagnostic database (version, size, readiness), a remote TTY/IP target for output, lost-packet counters, and record-management controls (total/overwritten/read record counts, output directory, operation mode). Its monitoring value is diagnostic/software service status: dsDataBaseReady confirms the diagnostic capture engine is operational, dsOutLostCounter1 through dsOutLostCounter3 reveal dropped/lost diagnostic data indicating the capture buffer can't keep up, and dsOverwrittenRecord/dsTotalRecord together show whether older captured records have been overwritten before being read. As a CX/Memotec proprietary diagnostic feature MIB, it doesn't appear to depend on standard IETF MIBs. It is deployed on CX Memotec network/protocol-conversion devices in telecom environments requiring live protocol-level traffic capture for troubleshooting. Engineers can download the CXDataScope-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CXDataScope-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

CX Memotec protocol-conversion/diagnostic device

Monitoring Examples

A technician would check dsDataBaseReady and dsDataBaseSize to confirm the diagnostic capture database is initialized and has sufficient space, then monitor dsOutLostCounter1 through dsOutLostCounter3 for nonzero values indicating the capture engine is dropping data due to overload. Comparing dsTotalRecord against dsOverwrittenRecord and dsReadNumberRecord shows whether captured diagnostic records were overwritten by new data before the technician had a chance to read them via dsReadOutputDir.

What Can Be Monitored

diagnostic database readiness/size
lost/dropped capture counters
total vs. overwritten vs. read records
capture operation mode

Imported Objects

From CXProduct-SMI

cxDataScope

OBJECT-IDENTITY

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
IpAddress

OIDs

OID symbolic	OID numeric	Type	Access	Description
dsControl	1.3.6.1.4.1.495.2.1.8.3.1
OCT dsDataBaseVersion	1.3.6.1.4.1.495.2.1.8.3.1.1	OCTET STRING	read-only	Version of the Database of Data Scope. Default Value: none
INT dsDataBaseSize	1.3.6.1.4.1.495.2.1.8.3.1.2	INTEGER	read-write	The size of Database in Kbytes.
INT dsDataBaseReady	1.3.6.1.4.1.495.2.1.8.3.1.3	INTEGER	read-only	Status of Database. READY if Database has memory; NOT-READY if it failed to allocate memory.
IP dsRTTYIpAddress	1.3.6.1.4.1.495.2.1.8.3.1.4	IpAddress	read-write	The IP address of RTTY. For the time being, only ONE RTTY is supported.
CTR dsOutLostCounter1	1.3.6.1.4.1.495.2.1.8.3.1.5	Counter	read-only	The number of data records discarded when sent to Local Console.
CTR dsOutLostCounter2	1.3.6.1.4.1.495.2.1.8.3.1.6	Counter	read-only	The number of data records discarded when sent to RTTY.
CTR dsOutLostCounter3	1.3.6.1.4.1.495.2.1.8.3.1.7	Counter	read-only	The number of data records discarded when sent to PC.
dsDataBase	1.3.6.1.4.1.495.2.1.8.3.2
INT dsOperationMode	1.3.6.1.4.1.495.2.1.8.3.2.1	INTEGER	read-write	Operational Mode of Database. No more data records can be saved to Database if the operational mode is in read-mode.
CTR dsTotalRecord	1.3.6.1.4.1.495.2.1.8.3.2.2	Counter	read-only	The total data records in the Database.
CTR dsOverwrittenRecord	1.3.6.1.4.1.495.2.1.8.3.2.3	Counter	read-only	The amount of data records overwritten since last deleting operation.
INT dsReadNumberRecord	1.3.6.1.4.1.495.2.1.8.3.2.4	INTEGER	read-write	The number of data records that will be read per read operation.
INT dsReadOutputDir	1.3.6.1.4.1.495.2.1.8.3.2.5	INTEGER	read-write	Indicates where to send the data records when reading Database. When value is not equal to 1 or 2, output will be sent to local console.
INT dsDBControl	1.3.6.1.4.1.495.2.1.8.3.2.6	INTEGER	write-only	Control of how to read/delete data resocrds in the Database: 1 - idle, no action, 2 - read dsReadNumberRecord number of Previous records and keep those records, 3 - read dsReadNumberRecord number of Previous records and erase those records, 4 - read dsReadNumberRecord number of Next-records, and keep those records, 5 - read dsReadNumberRecord number of Next-records, and erase those records, 6 - Erase All Records.
INT dsReadFormat	1.3.6.1.4.1.495.2.1.8.3.2.7	INTEGER	read-write	The output data format for reading data records in Database.
dsRegistryTable	1.3.6.1.4.1.495.2.1.8.3.3		not-accessible	Trace and Registry Control Table.
dsRegistryEntry	1.3.6.1.4.1.495.2.1.8.3.3.1		not-accessible	Trace and Registry Control Table Entry.
INT dsRegAppID	1.3.6.1.4.1.495.2.1.8.3.3.1.1	INTEGER	read-only	It is sap ID for driver tasks, or pre=defined application ID for other tasks.
INT dsRegTrafficType	1.3.6.1.4.1.495.2.1.8.3.3.1.2	INTEGER	read-only	It is port type for driver tasks, or logical port type for other tasks.
INT dsRegIFIndex	1.3.6.1.4.1.495.2.1.8.3.3.1.3	INTEGER	read-only	It is the globalIndex in the ifTbl.
INT dsRegDirFilter	1.3.6.1.4.1.495.2.1.8.3.3.1.4	INTEGER	read-write	Filter on OsMessage Direction (Type).
INT dsRegState	1.3.6.1.4.1.495.2.1.8.3.3.1.5	INTEGER	read-write	Indicating if Data Scope accepts data from the task registered at this entry.
OCT dsRegDfMask	1.3.6.1.4.1.495.2.1.8.3.3.1.6	OCTET STRING	read-write	Mask of the data filter. This mask will be ANDed with data chosen by dfOffset. The result is checked against dsRegDfValue.
OCT dsRegDfValue	1.3.6.1.4.1.495.2.1.8.3.3.1.7	OCTET STRING	read-write	Value of the data filter.
INT dsRegDfCriteria	1.3.6.1.4.1.495.2.1.8.3.3.1.8	INTEGER	read-write	The criteria of comparing dfValue with the value obtained by ANDing dfMask with data.
INT dsRegDfOffset	1.3.6.1.4.1.495.2.1.8.3.3.1.9	INTEGER	read-write	The offset of data to be checked.
OCT dsRegStartMask	1.3.6.1.4.1.495.2.1.8.3.3.1.20	OCTET STRING	read-write	The mask of the data-match structure to trigger a start event.
OCT dsRegStartValue	1.3.6.1.4.1.495.2.1.8.3.3.1.21	OCTET STRING	read-write	The value of the data-match structure to trigger a start event.
INT dsRegStartCriteria	1.3.6.1.4.1.495.2.1.8.3.3.1.22	INTEGER	read-write	The criteria of the data-match structure to trigger a start event.
INT dsRegStartOffset	1.3.6.1.4.1.495.2.1.8.3.3.1.23	INTEGER	read-write	The data offset of the data-match structure to trigger a start event.
OCT dsRegStopMask	1.3.6.1.4.1.495.2.1.8.3.3.1.24	OCTET STRING	read-write	The mask of the data-match structure to trigger a stop event.
OCT dsRegStopValue	1.3.6.1.4.1.495.2.1.8.3.3.1.25	OCTET STRING	read-write	The value of the data-match structure to trigger a stop event.
INT dsRegStopCriteria	1.3.6.1.4.1.495.2.1.8.3.3.1.26	INTEGER	read-write	The criteria of the data-match structure to trigger a stop event. The values other than 1 and 2 mean the number of events that Data Scope will trace before a stop event is generated.
INT dsRegStopOffset	1.3.6.1.4.1.495.2.1.8.3.3.1.27	INTEGER	read-write	The data offset of the data-match structure to trigger a stop event.
INT dsRegStatus	1.3.6.1.4.1.495.2.1.8.3.3.1.41	INTEGER	read-only	the state of this trace-registry entry, could be RECORDING or NON-RECORDING. When state is NON-RECORDING, a start event will change state to RECORDING; and a stop event will changes state from RECORDING to NON-RECORDING.
INT dsRegDataLength	1.3.6.1.4.1.495.2.1.8.3.3.1.42	INTEGER	read-write	The maximum length of data that will be captured. Max. value is 65535.
INT dsRegDataOffset	1.3.6.1.4.1.495.2.1.8.3.3.1.43	INTEGER	read-write	The offset from where to start data capturing. Max. value is 65535.
INT dsRegOutputDir	1.3.6.1.4.1.495.2.1.8.3.3.1.44	INTEGER	read-write	a bitmap object indicating where to output the traced data. When Bit 0 set to 1: Output data to local console; When Bit 1 set to 1: Output data to RTTY; When Bit 2 set to 1: Output data to Database;
INT dsRegOutputFormat	1.3.6.1.4.1.495.2.1.8.3.3.1.45	INTEGER	read-write	indicats the format to be used to output the traced data.

RFC description

CX DataScope MIB for system event tracing and monitoring. Manages data scope database configuration, event capture, and output routing to console and RTTY.

Start monitoring CX Memotec protocol-conversion device (Data Scope diagnostics) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download CXDataScope-MIB

What Is CXDataScope-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description