CT-DAREGISTRY-MIB

File: CT-DAREGISTRY-MIB.mib (5608 bytes)

Imported modules

RFC1155-SMI RFC-1212 CTRON-OIDS

Imported symbols

TimeTicks OBJECT-TYPE cabletron

Defined Types

DisplayString  
STRING    

CtDARegistryEntry  
SEQUENCE    
  ctDARegistryIndex INTEGER
  ctDARegistryInstance INTEGER
  ctDARegistryAdminStatus INTEGER
  ctDARegistryOperStatus INTEGER
  ctDARegistryLastChange TimeTicks
  ctDARegistryDescr DisplayString

Defined Values

ctSSA 1.3.6.1.4.1.52.4497
OBJECT IDENTIFIER    

ctDARegistryTable 1.3.6.1.4.1.52.4497.1
A list of Demand Access WAN firmware components.
OBJECT-TYPE    
  SEQUENCE OF  
    CtDARegistryEntry

ctDARegistryEntry 1.3.6.1.4.1.52.4497.1.1
An entry containing management information applicable to a particular subsystem.
OBJECT-TYPE    
  CtDARegistryEntry  

ctDARegistryIndex 1.3.6.1.4.1.52.4497.1.1.1
This is the category for this object.
OBJECT-TYPE    
  INTEGER 0..2147483647  

ctDARegistryInstance 1.3.6.1.4.1.52.4497.1.1.2
This is a unique instance within the category for this object.
OBJECT-TYPE    
  INTEGER 0..2147483647  

ctDARegistryAdminStatus 1.3.6.1.4.1.52.4497.1.1.3
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).
OBJECT-TYPE    
  INTEGER up(1), down(2), testing(3)  

ctDARegistryOperStatus 1.3.6.1.4.1.52.4497.1.1.4
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.
OBJECT-TYPE    
  INTEGER up(1), down(2), testing(3), unknown(4), dormant(5), notPresent(6), lowerLayerDown(7)  

ctDARegistryLastChange 1.3.6.1.4.1.52.4497.1.1.5
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.
OBJECT-TYPE    
  TimeTicks  

ctDARegistryDescr 1.3.6.1.4.1.52.4497.1.1.6
A textual string that identifies the subsystem.
OBJECT-TYPE    
  DisplayString Size(0..255)