PPP-LCP-MIB

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsPPP-LCP-MIB

Category: Network Interfaces

Description: Defines managed objects for the PPP Link Control Protocol (LCP), including link statistics counters and LCP option configuration for PPP interfaces.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring PPP-LCP-MIB with a free 30-day trial of IPNetwork Monitor.

What Is PPP-LCP-MIB?

PPP-LCP-MIB is a vendor-neutral IETF standards-track MIB covering the Link Control Protocol (LCP) layer of the Point-to-Point Protocol, used to negotiate and monitor point-to-point serial and dial-up links. It exposes per-link status objects including negotiated MTU/MRU sizes, address/control-field compression settings, and link-layer error counters. For device monitoring it is used chiefly to check software/protocol-level link health rather than physical hardware: it surfaces error counts such as bad addresses, bad control fields, oversized packets, and bad frame-check-sequences that indicate a degrading or misconfigured serial/PPP link. It naturally depends on and complements the base IF-MIB (ifTable), since each PPP-LCP-MIB OID entry in pppLinkStatusTable is indexed by the underlying physical interface, and it is typically used alongside PPP-related MIBs like PPP-SEC-MIB and PPP-IP-NCP-MIB. It is deployed on routers and access servers that terminate PPP links such as dial-up, ISDN, or point-to-point leased-line WAN connections.

IPNetwork Monitor allows you to monitor SNMP objects defined in PPP-LCP-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

  • vendor-neutral, standards-based MIB, not tied to a specific manufacturer
  • routers and access servers terminating PPP links (dial-up, ISDN, leased-line WAN)

Monitoring Examples

An administrator would poll pppLinkStatusTable/pppLinkStatusEntry, indexed by pppLinkStatusPhysicalIndex, to check counters like pppLinkStatusBadFCSs and pppLinkStatusBadControls on a given PPP link. A rising count of pppLinkStatusPacketTooLongs or pppLinkStatusBadAddresses would reveal a mismatched MRU or a noisy/faulty serial line degrading the PPP session. Comparing pppLinkStatusLocalMRU against pppLinkStatusRemoteMRU also confirms both ends negotiated compatible frame sizes.

What Can Be Monitored

  • PPP link error counters (bad address/control/FCS)
  • negotiated local and remote MRU
  • oversized packet counts
  • address/control-field compression settings
Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter

From RFC1213-MIB

ifIndex
transmission
OIDs

RFC description

Point-to-Point Protocol Link Control Protocol MIB (RFC 1315) defining objects for monitoring and managing PPP-LCP negotiation parameters and settings.

Start monitoring vendor-neutral, standards-based MIB (PPP Link Control Protocol) 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 PPP-LCP-MIB