CT-DAREGISTRY-MIB: View SNMP OID List / Download MIB

VENDOR: ENTERASYS NETWORKS INC.


 Home MIB: CT-DAREGISTRY-MIB
Download as:   
SNMPv2-CONF, SNMPv2-SMI, CTRON-OIDS, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 ctSSA 1.3.6.1.4.1.52.4497
           ctDARegistryTable 1.3.6.1.4.1.52.4497.1 no-access
A list of Demand Access WAN firmware components.
               ctDARegistryEntry 1.3.6.1.4.1.52.4497.1.1 no-access
An entry containing management information applicable to a particular subsystem.
                   ctDARegistryIndex 1.3.6.1.4.1.52.4497.1.1.1 integer read-only
This is the category for this object.
                   ctDARegistryInstance 1.3.6.1.4.1.52.4497.1.1.2 integer read-only
This is a unique instance within the category for this object.
                   ctDARegistryAdminStatus 1.3.6.1.4.1.52.4497.1.1.3 integer read-write
The desired state of the subsystem. The testing(3) state indicates that no operational functions can be passed. When a managed system initializes, all subsystems start with ctDARegistryAdminStatus in the up(1) state. As a result of either explicit management action or per configuration information retained by the managed system, ctDARegistryAdminStatus is then changed to either the dowm(2) or testing(3) states (or remains in the up(1) state). Enumeration: 'down': 2, 'testing': 3, 'up': 1.
                   ctDARegistryOperStatus 1.3.6.1.4.1.52.4497.1.1.4 integer read-only
The mandatory operational state of the subsystem. The testing(3) state indicates that no operational functions can be passed. If ctDARegistryAdminStatus is down(2) then ctDARegistryOperStatus should be down(2). If ctDARegistryAdminStatus is changed to up(1) then ctDARegistryOperStatus should change to up(1) if the subsystem is ready to function; it should change to dormant(5) if the subsystem is waiting for external actions; it should remain in the down(2) state if and only if there is a fault that prevents if from going to the up(1) state. The notPresent state is a refinement on the down state which indicates that the relevant interface is down specifically because some component (typically, a hardware component) is not present in the managed system. The lowerLayerDown state is also a refinement on the down state. This new state indicates that this system runs on top of one or more interfaces (see ifStackTable) and that this system is down specifically because one or more of these lower-layer interfaces are down. Enumeration: 'dormant': 5, 'lowerLayerDown': 7, 'unknown': 4, 'testing': 3, 'up': 1, 'down': 2, 'notPresent': 6.
                   ctDARegistryLastChange 1.3.6.1.4.1.52.4497.1.1.5 timeticks read-only
The value of sysUpTime at the time the subsystem entered its mandatory operational state. If the mandatory state was entered prior to the last re-initialization of the local network management subsystem, then this object contains a zero value.
                   ctDARegistryDescr 1.3.6.1.4.1.52.4497.1.1.6 displaystring read-only
A textual string that identifies the subsystem.