START-MIB
File:
START-MIB.mib (6304 bytes)
Imported modules
Imported symbols
Defined Types
| RowStatus |
|
| INTEGER |
active(1), notInService(2), notReady(3), createAndGo(4), createAndWait(5), destroy(6) |
|
|
| StorageType |
|
| Describes the memory realization of a conceptual row. A
row which is volatile(2) is lost upon reboot. A row which
is either nonVolatile(3), permanent(4) or readOnly(5), is
backed up by stable storage. A row which is permanent(4)
can be changed but not deleted. A row which is readOnly(5)
cannot be changed nor deleted.
If the value of an object with this syntax is either
permanent(4) or readOnly(5), it cannot be modified.
Conversely, if the value is either other(1), volatile(2) or
nonVolatile(3), it cannot be modified to be permanent(4) or
readOnly(5).
Every usage of this textual convention is required to
specify the columnar objects which a permanent(4) row must
at a minimum allow to be writable. |
| TEXTUAL-CONVENTION |
|
|
|
| |
INTEGER |
other(1), volatile(2), nonVolatile(3), permanent(4), readOnly(5) |
|
| TDomain |
|
| Denotes a kind of transport service.
Some possible values, such as snmpUDPDomain, are defined in
'Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)'. |
| TEXTUAL-CONVENTION |
|
|
|
| |
OBJECT IDENTIFIER |
|
|
| TAddress |
|
| Denotes a transport service address.
For snmpUDPDomain, a TAddress is 6 octets long, the initial 4
octets containing the IP-address in network-byte order and the
last 2 containing the UDP port in network-byte order. Consult
'Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)' for further information on
snmpUDPDomain. |
| TEXTUAL-CONVENTION |
|
|
|
| |
OCTET STRING |
Size(1..255) |
|
| RowPointer |
|
| Represents a pointer to a conceptual row. The value is the
name of the instance of the first accessible columnar object
in the conceptual row.
For example, ifIndex.3 would point to the 3rd row in the
ifTable (note that if ifIndex were not-accessible, then
ifDescr.3 would be used instead). |
| TEXTUAL-CONVENTION |
|
|
|
| |
OBJECT IDENTIFIER |
|
|
| TimeInterval |
|
| A period of time, measured in units of 0.01 seconds. |
| TEXTUAL-CONVENTION |
|
|
|
| |
INTEGER |
0..2147483647 |
|
Defined Values
| mgmt |
1.3.6.1.2 |
| OBJECT IDENTIFIER |
|
|
|
| private |
1.3.6.1.4 |
| OBJECT IDENTIFIER |
|
|
|
| snmpV2 |
1.3.6.1.6 |
| OBJECT IDENTIFIER |
|
|
|
| snmpMIB |
1.3.6.1.6.3.1 |
| OBJECT IDENTIFIER |
|
|
|
| snmpTrap |
1.3.6.1.6.3.1.1.4 |
| OBJECT IDENTIFIER |
|
|
|
| snmpTraps |
1.3.6.1.6.3.1.1.5 |
| OBJECT IDENTIFIER |
|
|
|
| std |
1.0 |
| OBJECT IDENTIFIER |
|
|
|
| member-body |
1.2 |
| OBJECT IDENTIFIER |
|
|
|
| us |
1.2.840 |
| OBJECT IDENTIFIER |
|
|
|
| snmpmibs |
1.2.840.10006.300 |
| OBJECT IDENTIFIER |
|
|
|
| lagMIB |
1.2.840.10006.300.43 |
| OBJECT IDENTIFIER |
|
|
|
| coldStart |
1.3.6.1.6.3.1.1.5.1 |
| A coldStart trap signifies that the SNMPv2 entity, acting
in an agent role, is reinitializing itself and that its
configuration may have been altered. |
| Status: current |
Access: read-write |
| NOTIFICATION-TYPE |
|
|
|
| warmStart |
1.3.6.1.6.3.1.1.5.2 |
| A warmStart trap signifies that the SNMPv2 entity, acting
in an agent role, is reinitializing itself such that its
configuration is unaltered. |
| Status: current |
Access: read-write |
| NOTIFICATION-TYPE |
|
|
|
| authenticationFailure |
1.3.6.1.6.3.1.1.5.5 |
| An authenticationFailure trap signifies that the
SNMP entity has received a protocol message that is
not properly authenticated. While all implementations
of SNMP entities MAY be capable of generating this
trap, the snmpEnableAuthenTraps object indicates
whether this trap will be generated. |
| Status: current |
Access: read-write |
| NOTIFICATION-TYPE |
|
|
|
| snmpSet |
1.3.6.1.6.3.1.1.6 |
| OBJECT IDENTIFIER |
|
|
|
| snmpSetSerialNo |
1.3.6.1.6.3.1.1.6.1 |
| An advisory lock used to allow several cooperating SNMPv2
entities, all acting in a manager role, to coordinate their
use of the SNMPv2 set operation.
This object is used for coarse-grain coordination. To
achieve fine-grain coordination, one or more similar objects
might be defined within each MIB group, as appropriate. |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
TestAndIncr |
|
|