PDN-MPE-MIB2-MIB
File:
PDN-MPE-MIB2-MIB.mib (5167 bytes)
Imported modules
Imported symbols
Defined Types
MpeSystemsEntry |
|
SEQUENCE |
|
|
|
|
mpeSysDescr |
DisplayString |
Size(0..255) |
|
mpeSysObjectID |
OBJECT IDENTIFIER |
|
|
mpeSysUpTime |
TimeTicks |
|
|
mpeSysContact |
DisplayString |
Size(0..255) |
|
mpeSysName |
DisplayString |
Size(0..255) |
|
mpeSysLocation |
DisplayString |
Size(0..255) |
|
mpeSysServices |
INTEGER |
0..127 |
Defined Values
mpeSystem |
1.3.6.1.4.1.1795.2.24.12.4.1.1 |
OBJECT IDENTIFIER |
|
|
|
mpeSystemsTable |
1.3.6.1.4.1.1795.2.24.12.4.1.1.1 |
A table that contains general information about an Entity . |
Status: mandatory |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
SEQUENCE OF |
|
|
|
|
MpeSystemsEntry |
|
mpeSystemsEntry |
1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1 |
A list of system information about an Entity . |
Status: mandatory |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
MpeSystemsEntry |
|
|
mpeSysDescr |
1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.1 |
A textual description of the entity. This value
should include the full name and version
identification of the system's hardware type,
software operating-system, and networking
software. It is mandatory that this only contain
printable ASCII characters. |
Status: mandatory |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
DisplayString |
Size(0..255) |
|
mpeSysObjectID |
1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.2 |
The vendor's authoritative identification of the
network management subsystem contained in the
entity. This value is allocated within the SMI
enterprises subtree (1.3.6.1.4.1) and provides an
easy and unambiguous means for determining `what
kind of box' is being managed. For example, if
vendor `Flintstones, Inc.' was assigned the
subtree 1.3.6.1.4.1.4242, it could assign the
identifier 1.3.6.1.4.1.4242.1.1 to its `Fred
Router'. |
Status: mandatory |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
OBJECT IDENTIFIER |
|
|
mpeSysUpTime |
1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.3 |
The time (in hundredths of a second) since the
network management portion of the system was last
re-initialized. |
Status: mandatory |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
TimeTicks |
|
|
mpeSysName |
1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.5 |
An administratively-assigned name for this
managed node. By convention, this is the node's
fully-qualified domain name. |
Status: mandatory |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
DisplayString |
Size(0..255) |
|
mpeSysLocation |
1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.6 |
The physical location of this node (e.g.,
`telephone closet, 3rd floor'). |
Status: mandatory |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
DisplayString |
Size(0..255) |
|
mpeSysServices |
1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.7 |
A value which indicates the set of services that
this entity primarily offers.
The value is a sum. This sum initially takes the
value zero, Then, for each layer, L, in the range
1 through 7, that this node performs transactions
for, 2 raised to (L - 1) is added to the sum. For
example, a node which performs primarily routing
functions would have a value of 4 (2^(3-1)). In
contrast, a node which is a host offering
application services would have a value of 72
(2^(4-1) + 2^(7-1)). Note that in the context of
the Internet suite of protocols, values should be
calculated accordingly:
layer functionality
1 physical (e.g., repeaters)
2 datalink/subnetwork (e.g., bridges)
3 internet (e.g., IP gateways)
4 end-to-end (e.g., IP hosts)
7 applications (e.g., mail relays)
For systems including OSI protocols, layers 5 and
6 may also be counted. |
Status: mandatory |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
INTEGER |
0..127 |
|