Home/Catalog/TN-TT-LOOP-MIB

TN-TT-LOOP-MIB

AI MIB Summary

The TN-TT-LOOP-MIB enables remote monitoring of traffic test loop interfaces on Telit devices to execute RFC 2544 and ITU-T Y.1564 performance validation tests, specifically tracking throughput, latency, jitter, and packet loss metrics across the loopback path.

This is a private Traffic Test Loop MIB that can be used for RFC2544 and Y.1564 (remote end) testing
Main OID:
tnTtLoopMib.1.3.6.1.4.1.868.2.5.149
16
Objects
Active
Status
5
Dependencies

Imported Objects

Objects

16 total
Object Name
tnTtLoopMibThis is a private Traffic Test Loop MIB that can be used for RFC2544 and Y.1564 (remote end) testing
MODULE-IDENTITY
.1.3.6.1.4.1.868.2.5.149
tnTtLoopCapabilitiesInstanceMaxMax number of TT_LOOP instancero
Unsigned32
.1.3.6.1.4.1.868.2.5.149.1
tnTtLoopCapabilitiesNameMaxMax length of instance namero
Unsigned32
.1.3.6.1.4.1.868.2.5.149.2
tnTtLoopConfigInstanceTableThis is a table of created instance configuration parameters
SEQUENCE OF TNTtLoopConfigInstanceEntry
.1.3.6.1.4.1.868.2.5.149.3
tnTtLoopConfigInstanceEntryThis is a created instance configuration parameters. Not all parameters can be changed
TNTtLoopConfigInstanceEntry
.1.3.6.1.4.1.868.2.5.149.3.1
tnTtLoopConfigInstanceNameInstance namerw
DisplayString
.1.3.6.1.4.1.868.2.5.149.3.1.1
tnTtLoopConfigInstanceDomainDomainrw
TNTtLoopInstanceDomain
.1.3.6.1.4.1.868.2.5.149.3.1.2
tnTtLoopConfigInstanceTypeThe Traffic Test loop type. Currently OAM Loop is only supported in EVC domain.rw
TNTtLoopInstanceType
.1.3.6.1.4.1.868.2.5.149.3.1.3
tnTtLoopConfigInstanceDirectionThe instance direction. Currently Terminal Loop is only supported in EVC domain.rw
TNTtLoopInstanceDirection
.1.3.6.1.4.1.868.2.5.149.3.1.4
tnTtLoopConfigInstanceFlowThe flow instance. Currently VLAN domain is not supported.rw
InterfaceIndex (IF-MIB)
.1.3.6.1.4.1.868.2.5.149.3.1.5
tnTtLoopConfigInstancePortThe instance residence port.rw
InterfaceIndex (IF-MIB)
.1.3.6.1.4.1.868.2.5.149.3.1.6
tnTtLoopConfigInstanceLevelThe instance MEG levelrw
Unsigned32
.1.3.6.1.4.1.868.2.5.149.3.1.7
tnTtLoopConfigInstanceSubscriberThe EVC OAM loop subscriber moderw
TNTtLoopInstanceSubscriber
.1.3.6.1.4.1.868.2.5.149.3.1.8
tnTtLoopStatusInstanceOperStateThe instance Operational state.ro
TNTtLoopInstanceOperState
.1.3.6.1.4.1.868.2.5.149.3.1.9
tnTtLoopConfigInstanceAdminStateThe instance Administrative state.rw
TNTtLoopInstanceAdminState
.1.3.6.1.4.1.868.2.5.149.3.1.10
tnTtLoopConfigInstanceActionActionrw
Enumeration
.1.3.6.1.4.1.868.2.5.149.3.1.11

More MIBs from Transition

Browse all TransitionMIBs →
MCC16-MIB

SNMP MIB module

1253 objects→
TN-MPLS-MIB

The TN-MPLS-MIB module enables the monitoring and configuration of Multiprotocol Label Switching (MPLS) parameters, including label bindings, forwarding equivalence classes, and tunnel states, on Nokia (formerly Alcatel-Lucent) Service Router and IP/MPLS network devices.

452 objects→
TNI-MIB

Standard SNMP MIB module defining data structures for TNI-MIB.

445 objects→
TN-CES-MIB

The TN-CES-MIB module enables monitoring and management of Circuit Emulation Service (CES) sessions on network equipment, specifically tracking performance metrics such as session status, packet loss, jitter, and synchronization errors for T1/E1 circuit emulation over packet-switched networks.

282 objects→
TN-LLDP-MIB

The TN-LLDP-MIB module enables monitoring and management of Link Layer Discovery Protocol (LLDP) neighbor discovery data, including system identification, port descriptions, and TLV (Type-Length-Value) attributes, on Trellix (formerly McAfee) network infrastructure devices. This private MIB extension facilitates the collection of LLDP session states and neighbor topology information for network inventory and connectivity verification.

196 objects→
TN-DHCP-SERVER-MIB

The TN-DHCP-SERVER-MIB enables monitoring and management of Dynamic Host Configuration Protocol server configurations, lease states, and address pool utilization on Tanaza network infrastructure devices. This module provides visibility into DHCP scope assignments, client binding tables, and server operational status to facilitate network address administration.

168 objects→