MPSLA

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › MPSLA

Organization: Maipu Communication Technology Co. LTD.

Last Updated: 2008-09-17

Category: OAM

Description: Manages Maipu Communication IP SLA probe configuration and performance results.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is MPSLA?

This is a Maipu Communication enterprise MIB that configures and reports IP SLA (Service Level Agreement) probe entities on Maipu routers/switches, similar in spirit to vendor RTT/IP-SLA MIBs. It exposes SLA controller and responder objects, a table of configured SLA "entities" (probes) with an ID, name, and type, plus trap objects describing SLA-related fault classes. Monitoring this MIB centers on active performance/software probing, checking whether SLA test entities are enabled, tracking probe type and status, and receiving traps when a probe detects a service-level violation, useful for tracking network path performance rather than physical hardware component health. The module description is minimal, and sample objects reference an "mpios"/"iosSystem" tree suggesting dependency on the vendor's broader Maipu OS system MIB. Typical deployment is on Maipu routers/switches used by ISPs or enterprises running MPSLA SNMP monitoring to track active latency/jitter/loss probes between network endpoints.

IPNetwork Monitor allows you to monitor SNMP objects defined in MPSLA. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • Maipu Communication router/switch

Monitoring Examples

An operator would enable sysSlaCtrl and check sysSlaResponder status, then walk sysSlaEntityTable/sysSlaEntityEntry, indexed by slaEntityId, to see each probe's slaEntityName and slaEntityType. When an SLA threshold is breached, an mpTrapClass/mpTrapType notification carrying mpTrapDescr is generated, letting an admin correlate a specific probe entity to a network performance degradation event. sysSlaNotUsedEntityId/sysSlaNotUsedScheId appear to track unused entity and schedule ID slots available for provisioning new probes.

What Can Be Monitored

  • SLA probe status (enabled/disabled)
  • SLA entity name and type
  • SLA responder status
  • SLA violation traps
  • available entity/schedule IDs
Imported Objects

From MAIPU-SMI

mpMgmtOBJECT-IDENTITY
mpTrapObjectOBJECT-IDENTITY

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DisplayString
PhysAddress
RowStatus
TEXTUAL-CONVENTION
TruthValue
OIDs

RFC description

Maipu system trap and SLA properties with severity classification and device type identification.

Start monitoring Maipu Communication router/switch (IP SLA probes) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download MPSLA