PDN-MPE-MIB2-MIB :: mpeSysServices

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › PDN-MPE-MIB2-MIB › mpeSysServices

mpeSysServices

Module: PDN-MPE-MIB2-MIB

OID (symbolic): PDN-MPE-MIB2-MIB::mpeSysServices

OID (numeric): 1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.7

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: 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.

What is mpeSysServices?

This read-only integer represents the set of protocol layers this entity primarily provides services for, computed as a sum of 2 raised to (L-1) for each layer L, 1 through 7, that it performs transactions for. Admins and management tools use this value to classify the device's role in the network, such as router versus host, without consulting vendor-specific documentation. For example, a value of 4 (2 to the power of 3-1) indicates a device that performs primarily layer-3 routing functions, matching the MIB's own worked example.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.7
snmpwalk -v2c -c public <target> PDN-MPE-MIB2-MIB::mpeSysServices

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.7.1
snmpget -v2c -c public <target> PDN-MPE-MIB2-MIB::mpeSysServices.1

Start monitoring Paradyne Multi-Port Ethernet (MPE) module, Paradyne/Zhone access/aggregation equipment (per-module MIB-II system group) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the PDN-MPE-MIB2-MIB::mpeSysServices OID value, configure state conditions and alerts, and monitor any Paradyne Multi-Port Ethernet (MPE) module, Paradyne/Zhone access/aggregation equipment (per-module MIB-II system group) from a single console.

OID Breakdown

Upper-level ancestors (11 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.1795pdynPDN-HEADER-MIB
1.3.6.1.4.1.1795.2pdn_mgmtPDN-HEADER-MIB
1.3.6.1.4.1.1795.2.24paradynePDN-HEADER-MIB
1.3.6.1.4.1.1795.2.24.12pdn_mpePDN-HEADER-MIB
1.3.6.1.4.1.1795.2.24.12.4mpe_mib2PDN-HEADER-MIB
Numeric OIDNameModule
1.3.6.1.4.1.1795.2.24.12.4.1mpeMib2MIBObjectsPDN-MPE-MIB2-MIB
1.3.6.1.4.1.1795.2.24.12.4.1.1mpeSystemPDN-MPE-MIB2-MIB
1.3.6.1.4.1.1795.2.24.12.4.1.1.1mpeSystemsTablePDN-MPE-MIB2-MIB
1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1mpeSystemsEntryPDN-MPE-MIB2-MIB
1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.7mpeSysServicesPDN-MPE-MIB2-MIB