XEDIA-PPP-MP-MIB

All MIBs › XEDIA-PPP-MP-MIB

Organization: Xedia Corp.

Last Updated: 1998-09-17

Category: Xedia Enterprise Networking

Description: Manages Xedia Corp. PPP Multilink bundle configuration, fragment size, and bandwidth aggregation statistics.

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 XEDIA-PPP-MP-MIB?

This proprietary MIB from Xedia Corporation manages the PPP Multilink Protocol (MP) component on Xedia routers, which bundles multiple physical links into a single logical connection for bandwidth aggregation. It exposes bundle status objects covering negotiated parameters like maximum receive reconstructed unit (MRRU), endpoint discriminators, and fragment size limits, plus counters for sequence numbers and error conditions. This lets administrators monitor the software state of each multilink bundle, catching problems like fragment reassembly errors or mismatched MRRU negotiation between local and remote endpoints. It relies on the standard PPP Multilink Protocol as its underlying technology basis rather than another SNMP MIB. It is deployed on Xedia routers aggregating multiple serial or ISDN links into one logical WAN connection. Network engineers evaluating or troubleshooting this functionality can download the XEDIA-PPP-MP-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in XEDIA-PPP-MP-MIB. 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

Xedia multiservice access router

Monitoring Examples

An administrator would poll mpBundleStatusTable/mpBundleStatusEntry to compare mpBundleStatusLocalMRRU against mpBundleStatusRemoteMRRU and check mpBundleStatusPacketTooLongs for oversized-fragment errors. A rising count of mpBundleStatusPacketTooLongs or mpBundleStatusSingleFragsRcvd could indicate a fragment-size mismatch between bundle members, while mpBundleStatusLocalEndptDiscr/mpBundleStatusRemoteEndptDiscr confirm the correct peer endpoint is bundled. xediaPppMpConformance is a conformance-only branch with no runtime data.

What Can Be Monitored

multilink bundle MRRU negotiation
endpoint discriminator matching
fragment size limits
oversized packet errors
single-fragment receive count

Imported Objects

From IF-MIB

ifIndex

OBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Gauge32
MODULE-IDENTITY
OBJECT-TYPE

From XEDIA-REG

xediaMibs

OBJECT-IDENTITY

How to Use in IPNetwork Monitor

Example using mpBundleStatusPacketTooLongs OID:

Select a Xedia multiservice access router (PPP Multilink Protocol bundle/fragment-reassembly-error status) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type mpBundleStatusPacketTooLongs into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The number of received packets that have been discarded because their length exceeded the MRRU. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
xediaPppMpMIB	1.3.6.1.4.1.838.3.21			This module defines objects for management of Xedia's PPP Multilink Protocol component.
xediaPppMpObjects	1.3.6.1.4.1.838.3.21.1
mpBundle	1.3.6.1.4.1.838.3.21.1.1
mpBundleStatusTable	1.3.6.1.4.1.838.3.21.1.1.1		not-accessible	A table containing Multilink PPP bundle specific variables for this Multilink PPP implementation. The following objects reflect the values of the option parameters negotiated during the PPP Link Control Protocol negotiation for links that reside in this MP Bundle: mpBundleStatusLocalMRRU mpBundleStatusRemoteMRRU mpBundleStatusLocalEndpointDiscr mpBundleStatusRemoteEndpointDiscr mpBundleStatusRcvShortSeq mpBundleStatusXmtShortSeq mpBundleStatusSmallPktMaxSize mpBundleStatusMediumPktMaxSize These values are not meaningful until after the PPP Option negotiation has completed, which is indicated by the link reaching the open state (i.e., ifOperStatus is set to up). Therefore, when ifOperStatus is not up, the values of these variables will reflect unnegotiated values, i.e. MRRU and Endpoint Discriminator values will be 0 while the Rcv and Xmt Short Sequence Numbers will be disabled.
mpBundleStatusEntry	1.3.6.1.4.1.838.3.21.1.1.1.1		not-accessible	Management information about a particular PPP Multilink Protocol Bundle.
C32 mpBundleStatusPacketTooLongsEx	1.3.6.1.4.1.838.3.21.1.1.1.1.1	Counter32	read-only	The number of received packets that have been discarded because their length exceeded the MRRU.
U32 mpBundleStatusLocalMRRU	1.3.6.1.4.1.838.3.21.1.1.1.1.2	Unsigned32	read-only	The current value of the Maximum Receive Reconstructed Unit (MRRU) for the local MP entity. This value is the MRRU that the remote MP entity is using when sending packets to the local MP entity. The value of this object is meaningful only when the bundle has reached the open state (ifOperStatus is up).
U32 mpBundleStatusRemoteMRRU	1.3.6.1.4.1.838.3.21.1.1.1.1.3	Unsigned32	read-only	The current value of the Maximum Receive Reconstructed Unit (MRRU) for the remote Multilink PPP Entity. This value is the MRRU that the local entity is using when sending packets to the remote Multilink PPP entity. The value of this object is meaningful only when the bundle has reached the open state (ifOperStatus is up).
OCT mpBundleStatusLocalEndptDiscr	1.3.6.1.4.1.838.3.21.1.1.1.1.4	OCTET STRING	read-only	The current value of the Endpoint Discriminator which identifies this Multilink PPP bundle on the local peer. When the remote peer desires to add a new link to this Multilink PPP bundle, it will include this value during link establishment of the new link. This value will indicate to the local peer that the new link is intended to join this existing Multilink PPP bundle. The first byte in the string identifies the Class of the Endpoint Discriminator. The remaining bytes in the string contain the actual Endpoint Discriminator value.
OCT mpBundleStatusRemoteEndptDiscr	1.3.6.1.4.1.838.3.21.1.1.1.1.5	OCTET STRING	read-only	The current value of the Endpoint Discriminator which identifies this Multilink PPP bundle on the remote peer. When the local peer desires to add a new link to this Multilink PPP bundle, it will include this value during link establishment of the new link. This value will indicate to the remote peer that the new link is intended to join this existing Multilink PPP bundle. The first byte in the string identifies the Class of the Endpoint Discriminator. The remaining bytes in the string contain the actual Endpoint Discriminator value.
INT mpBundleStatusRcvShortSeq	1.3.6.1.4.1.838.3.21.1.1.1.1.6	INTEGER	read-only	Indicates whether the remote Multilink PPP entity will use the Short Sequence Number Header Format when transmitting packets to the local Multilink PPP entity. The value of this object is meaningful only when the bundle has reached the open state (ifOperStatus is up).
INT mpBundleStatusXmtShortSeq	1.3.6.1.4.1.838.3.21.1.1.1.1.7	INTEGER	read-only	Indicates whether the local Multilink PPP entity will use the Short Sequence Number Header Format when transmitting packets to the remote Multilink PPP entity. The value of this object is meaningful only when the bundle has reached the open state (ifOperStatus is up).
U32 mpBundleStatusSmallPktMaxSize	1.3.6.1.4.1.838.3.21.1.1.1.1.8	Unsigned32	read-only	The maximum size in bytes of a Small PPP packet. Use of this parameter is no longer recommended. The MP fragmentation threshold is controlled by mpBundleStatusMediumPktMaxSize. Small PPP packets are defined to be those which will be encapsulated in a single Multilink Protocol Fragment and always sent on the first link in the Bundle. Note that this parameter only applies to outgoing PPP packets sent by this system. Reassembly of incoming packets is unaffected by this value. Note that the default value of 12 bytes effectively means that no packets are subject to this rule.
U32 mpBundleStatusMediumPktMaxSize	1.3.6.1.4.1.838.3.21.1.1.1.1.9	Unsigned32	read-only	The maximum size in bytes of a Medium PPP packet. This value specifies the threshold at which Multilink fragmentation is applied to transmitted packets, i.e. packets smaller than this size will be encapsulated in a single Multilink Protocol fragment and sent on a single link, packets larger than this size will be fragmented over all links in the bundle. This value starts at mpBundleConfigMediumPktMaxSize and is adjusted downwards according to the peer's MRRU and each of the peer's link's MRUs. Medium PPP packets are defined to be those which will be encapsulated in a single Multilink Protocol Fragment and sent on each link in the Bundle in a round-robin fashion. Packets larger than this threshold are considered Large PPP packets. Large PPP packets will be fragmented into multiple Multilink Protocol Fragments and sent across all links in the bundle. Setting this value to its maximum (65535) will prevent fragmentation at the MP layer of outgoing PPP packets, i.e. it will cause all outgoing PPP packets to be considered either Small or Medium sized PPP packets. Note that this parameter only applies to outgoing PPP packets sent by this system. Reassembly of incoming packets is unaffected by this value.
C32 mpBundleStatusSingleFragsRcvd	1.3.6.1.4.1.838.3.21.1.1.1.1.10	Counter32	read-only	The number of MP fragments received that contain an entire PPP packet.
C32 mpBundleStatusReasmReqds	1.3.6.1.4.1.838.3.21.1.1.1.1.11	Counter32	read-only	The number of MP fragments received that require reassembly into PPP packets.
C32 mpBundleStatusReasmFails	1.3.6.1.4.1.838.3.21.1.1.1.1.12	Counter32	read-only	The number of fragmented PPP packets which failed to be reassembled.
C32 mpBundleStatusReasmOks	1.3.6.1.4.1.838.3.21.1.1.1.1.13	Counter32	read-only	The number of fragmented PPP packets received and successfully reassembled.
C32 mpBundleStatusRcvdFragsDiscarded	1.3.6.1.4.1.838.3.21.1.1.1.1.14	Counter32	read-only	The number of MP fragments discarded for some reason by the MP layer.
C32 mpBundleStatusDropTooManyFrags	1.3.6.1.4.1.838.3.21.1.1.1.1.15	Counter32	read-only	The number of MP fragments discarded because the MP layer has no more space to buffer fragments.
C32 mpBundleStatusSingleFragsSent	1.3.6.1.4.1.838.3.21.1.1.1.1.16	Counter32	read-only	The number of MP fragments sent that contain an entire PPP packet.
C32 mpBundleStatusFragCreates	1.3.6.1.4.1.838.3.21.1.1.1.1.17	Counter32	read-only	The number of MP fragments created to contain a fragment of a PPP packet.
C32 mpBundleStatusFragFails	1.3.6.1.4.1.838.3.21.1.1.1.1.18	Counter32	read-only	The number of attempts to create an MP fragment which failed and resulted in discarding of the PPP packet to be transmitted.
C32 mpBundleStatusFragOks	1.3.6.1.4.1.838.3.21.1.1.1.1.19	Counter32	read-only	The number of MP fragments successfully sent which contain a fragment of a PPP packet.
C32 mpBundleStatusRcvdFragsBuffered	1.3.6.1.4.1.838.3.21.1.1.1.1.20	Counter32	read-only	The number of received MP fragments currently buffered awaiting reassembly and delivery
mpBundleConfigTable	1.3.6.1.4.1.838.3.21.1.1.2		not-accessible	A table containing the LCP configuration parameters for this PPP MP Bundle. These variables represent the initial configuration of the PPP MP Bundle. The actual values of the negotiable parameters (MRRU and Short Sequence Numbers) may be changed during LCP negotiation as the link is brought up. The following objects reflect the initial values that will be proposed when LCP negotiation begins: mpBundleConfigLocalMRRU mpBundleConfigLocalEndptDiscr mpBundleConfigRcvShortSeq Note: the Endpoint Discriminator is non-negotiable, the value configured above (or the default if this is not configured) will be the Endpoint Discriminator used. The following objects are not negotiated during LCP: mpBundleConfigSmallPktMaxSize mpBundleConfigMediumPktMaxSize.
mpBundleConfigEntry	1.3.6.1.4.1.838.3.21.1.1.2.1		not-accessible	Configuration information for a particular Multilink PPP Bundle.
U32 mpBundleConfigLocalMRRU	1.3.6.1.4.1.838.3.21.1.1.2.1.1	Unsigned32	read-write	The initial Maximum Receive Reconstructed Unit (MRRU) that the local MP entity will advertise to the remote entity at the onset of LCP negotiation. If the value of this variable is 0 then the local MP entity will advertise the default MRRU value of 1600 bytes. Changing this object will have effect when the link is next restarted. After the link comes up, the status variable mpBundleStatusLocalMRRU will reflect the actual MRRU negotiated with the peer during LCP negotiation.
OCT mpBundleConfigLocalEndptDiscr	1.3.6.1.4.1.838.3.21.1.1.2.1.2	OCTET STRING	read-write	The value to be advertised to the remote peer as the Endpoint Discriminator to be used to identify this Multilink PPP bundle. After the remote peer has received this value, it should include this value during LCP negotiation of any new links intended to join this Multilink PPP bundle. The first byte in the string identifies the Class of the Endpoint Discriminator. The remaining bytes in the string contain the actual Endpoint Discriminator value. If the value of this variable is 0 then the local peer will use the MAC address of the local box as the value to advertise as the local Endpoint Discriminator. After the link comes up, the status variable mpBundleStatusLocalEndptDiscr will reflect this Endpoint Discriminator value which has been sent to the peer (i.e. this value is not negotiated with the peer, the peer must accept whatever Endpoint Discriminator we send to them).
INT mpBundleConfigRcvShortSeq	1.3.6.1.4.1.838.3.21.1.1.2.1.3	INTEGER	read-write	If enabled(1) then the local peer will attempt to negotiate Short Sequence Number Header Format for the MP encapsulated PPP traffic sent from the remote peer to the local peer. If disabled(2) then no attempt to negotiate Short Sequence Numbers will be performed, indicating that instead the default Long Sequence Number Fragment Format should be used for all traffic sent by the remote peer to the local peer. This setting has no effect on the negotation of Short Sequence Number Header Format for the traffic flowing in the opposite direction (from the local peer to the remote peer). The use of Short Sequence Number Fragment Format on that traffic will be determined by whatever the remote peer proposes. Changing this object will have effect when the link is next restarted (either by toggling ifAdminStatus for this interface down and then up again, or by rebooting the entire system). After the link comes up, the status variable mpBundleStatusLocalMRRU will reflect the actual MRRU negotiated with the peer during LCP negotiation.
U32 mpBundleConfigSmallPktMaxSize	1.3.6.1.4.1.838.3.21.1.1.2.1.4	Unsigned32	read-write	The maximum size in bytes of a Small PPP packet. Use of this parameter is no longer recommended. To control the MP fragmentation threshold see mpBundleConfigMediumPktMaxSize. Small PPP packets are defined to be those which will be encapsulated in a single Multilink Protocol Fragment and always sent on the first link in the Bundle. Note that this parameter only applies to outgoing PPP packets sent by this system. Reassembly of incoming packets is unaffected by this value. Note that the default value of 12 bytes effectively means that no packets are subject to this rule.
U32 mpBundleConfigMediumPktMaxSize	1.3.6.1.4.1.838.3.21.1.1.2.1.5	Unsigned32	read-write	The maximum size in bytes of a Medium PPP packet. This value specifies the threshold at which Multilink fragmentation is applied to transmitted packets, i.e. packets smaller than this size will be encapsulated in a single Multilink Protocol fragment and sent on a single link, packets larger than this size will be fragmented over all links in the bundle. Medium PPP packets are defined to be those which will be encapsulated in a single Multilink Protocol Fragment and sent on each link in the Bundle in a round-robin fashion. Packets larger than this threshold are considered Large PPP packets. Large PPP packets will be fragmented into multiple Multilink Protocol Fragments and sent across all links in the bundle. Setting this value to its maximum (65535) will prevent fragmentation at the MP layer of outgoing PPP packets, i.e. it will cause all outgoing PPP packets to be considered either Small or Medium sized PPP packets. Note that this parameter only applies to outgoing PPP packets sent by this system. Reassembly of incoming packets is unaffected by this value.
xediaPppMpConformance	1.3.6.1.4.1.838.3.21.2
mpCompliances	1.3.6.1.4.1.838.3.21.2.1
mpCompliance	1.3.6.1.4.1.838.3.21.2.1.1			The compliance statement for all agents that support this MIB. A compliant agent implements all objects defined in this MIB.
mpGroups	1.3.6.1.4.1.838.3.21.2.2
mpAllGroup	1.3.6.1.4.1.838.3.21.2.2.1			The set of all accessible objects in this MIB.

RFC description

Manages Xedia's PPP Multilink Protocol (MP) component for bundling multiple PPP links into a single session.

Start monitoring Xedia multiservice access router (PPP Multilink Protocol bundle/fragment-reassembly-error 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.

Download XEDIA-PPP-MP-MIB