PDN-MPE-MIB2-MIB

Registered at: 1.3.6.1.4.1.1795.2.24.12.4.1

1.3.6.1.4.1.1795.2.24.12.4.2
Namespace: zhone
Source file: PDN-MPE-MIB2-MIB
Digest: sha256:2db0a658a611ae9659a00e7405159b983f4d05f4191a3d5ad57499c44f73770d

Imports

From	Symbols
ENTITY-MIB	`entPhysicalIndex`
PDN-HEADER-MIB	`mpe-mib2`
SNMPv2-CONF	`MODULE-COMPLIANCE, NOTIFICATION-GROUP`
SNMPv2-SMI	`MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, TRAP-TYPE, TimeTicks, iso`
SNMPv2-TC	`DisplayString, TEXTUAL-CONVENTION`

Imported by

1 module(s) in this corpus import this one.

PDN-MPE-DSLAM-SYSTEM-MIB

Load order

Every file a consumer needs in order to load this module, dependencies first.

ENTITY-MIB
IANA-ENTITY-MIB
PDN-HEADER-MIB
PDN-MPE-MIB2-MIB
SNMP-FRAMEWORK-MIB
SNMPv2-CONF
SNMPv2-SMI
SNMPv2-TC
UUID-TC-MIB

Objects

Name	OID	Syntax	Access	Status
mpeMib2MIBObjects OBJECT-IDENTITY	1.3.6.1.4.1.1795.2.24.12.4.1
mpeSystem OBJECT-IDENTITY	1.3.6.1.4.1.1795.2.24.12.4.1.1
mpeSystemsTable OBJECT-TYPE A table that contains general information about an Entity .	1.3.6.1.4.1.1795.2.24.12.4.1.1.1		not-accessible	mandatory
mpeSystemsEntry OBJECT-TYPE A list of system information about an Entity .	1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1		not-accessible	mandatory
mpeSysDescr OBJECT-TYPE 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.	1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.1	DisplayString (SIZE(0..255))	read-only	mandatory
mpeSysObjectID OBJECT-TYPE 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'.	1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.2	OBJECT IDENTIFIER	read-only	mandatory
mpeSysUpTime OBJECT-TYPE The time (in hundredths of a second) since the network management portion of the system was last re-initialized.	1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.3	TimeTicks	read-only	mandatory
mpeSysContact OBJECT-TYPE The textual identification of the contact person for this managed node, together with information on how to contact this person.	1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.4	DisplayString (SIZE(0..255))	read-write	mandatory
mpeSysName OBJECT-TYPE An administratively-assigned name for this managed node. By convention, this is the node's fully-qualified domain name.	1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.5	DisplayString (SIZE(0..255))	read-write	mandatory
mpeSysLocation OBJECT-TYPE The physical location of this node (e.g., `telephone closet, 3rd floor').	1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.6	DisplayString (SIZE(0..255))	read-write	mandatory
mpeSysServices OBJECT-TYPE 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.	1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.7	INTEGER (0..127)	read-only	mandatory
mpeMib2MIBTraps OBJECT-IDENTITY	1.3.6.1.4.1.1795.2.24.12.4.2