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).
Parsed from file ct-daregistry-mib.txt
Company: None
Module: CT-DAREGISTRY-MIB
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).
Parsed from file CT-DAREGISTRY-MIB.mib
Module: CT-DAREGISTRY-MIB
ctDARegistryAdminStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2), testing(3) } ACCESS read-write STATUS mandatory DESCRIPTION "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)." ::= { ctDARegistryEntry 3 }
Vendor: Enterasys Networks Inc.
Module: CT-DAREGISTRY-MIB
[Automatically extracted from oidview.com]
ctDARegistryAdminStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2), testing(3) } ACCESS read-write STATUS mandatory DESCRIPTION "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)." ::= { ctDARegistryEntry 3 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.52.4497.1.1.1 | ctDARegistryIndex | 0 | 0 | This is the category for this object. |
| 1.3.6.1.4.1.52.4497.1.1.2 | ctDARegistryInstance | 0 | 0 | This is a unique instance within the category for this object. |
| 1.3.6.1.4.1.52.4497.1.1.4 | ctDARegistryOperStatus | 0 | 0 | The mandatory operational state of the subsystem. The testing(3) state indicates that no operational functions can be passed. I… |
| 1.3.6.1.4.1.52.4497.1.1.5 | ctDARegistryLastChange | 0 | 0 | The value of sysUpTime at the time the subsystem entered its mandatory operational state. If the mandatory state was entered prio… |
| 1.3.6.1.4.1.52.4497.1.1.6 | ctDARegistryDescr | 0 | 0 | A textual string that identifies the subsystem. |