PPP-BRIDGE-NCP-MIB

All MIBs › PPP-BRIDGE-NCP-MIB

Category: Network Interfaces, VLAN and Bridging

Description: Defines managed objects for the PPP Bridge Network Control Protocol, managing bridge-layer configuration over PPP links.

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

What Is PPP-BRIDGE-NCP-MIB?

PPP-BRIDGE-NCP-MIB is a vendor-neutral IETF standards-track MIB (RFC 1474) for managing the Bridging Network Control Protocol extension of PPP, which carries bridged LAN traffic such as Ethernet or Token Ring frames over a point-to-point link. It exposes configuration and operational-status data for each bridged PPP interface, including administrative and operational status, per-direction tinygram compression negotiation, and LAN/Ring identifiers. Its monitoring value centers on operational status: pppBridgeOperStatus reveals whether the bridging NCP has actually negotiated successfully, distinguishing a healthy bridged link from one stuck renegotiating after a WAN outage. It builds on the standard PPP LCP/NCP negotiation framework and the underlying IF-MIB/PPP-MIB interface indexing for the physical link. It is typically deployed on routers or remote-access devices that bridge Ethernet or Token Ring segments across a WAN link using PPP. Engineers implementing or auditing this functionality typically reference the PPP-BRIDGE-NCP-MIB RFC/standard documentation for the authoritative specification.

IPNetwork Monitor allows you to monitor SNMP objects defined in PPP-BRIDGE-NCP-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/remote-access devices bridging LANs over PPP links

Monitoring Examples

pppBridgeTable/pppBridgeEntry rows expose pppBridgeOperStatus alongside pppBridgeLocalToRemoteTinygramCompression and pppBridgeRemoteToLocalTinygramCompression, showing whether compression was negotiated in each direction, while pppBridgeConfigTable/pppBridgeConfigEntry expose the administrative pppBridgeConfigAdminStatus and pppBridgeConfigRingId used to configure Token Ring bridging. An admin would poll pppBridgeOperStatus to confirm a remote bridge link came back up after a WAN outage, and compare pppBridgeLocalToRemoteLanId against pppBridgeRemoteToLocalLanId to rule out a LAN ID mismatch breaking the bridge.

What Can Be Monitored

PPP bridge operational status
PPP bridge admin status
tinygram compression negotiation (both directions)
LAN ID negotiation
Token Ring ID configuration

Imported Objects

From PPP-LCP-MIB

ppp	OBJECT-IDENTITY

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter

From RFC1213-MIB

ifIndex

OIDs

OID symbolic	OID numeric	Type	Access	Description
pppBridge	1.3.6.1.2.1.10.23.4
pppBridgeTable	1.3.6.1.2.1.10.23.4.1		not-accessible	Table containing the parameters and statistics for the local PPP entity that are related to the operation of Bridging over the PPP.
pppBridgeEntry	1.3.6.1.2.1.10.23.4.1.1		not-accessible	Bridging information for a particular PPP link.
INT pppBridgeOperStatus	1.3.6.1.2.1.10.23.4.1.1.1	INTEGER	read-only	The operational status of the Bridge network protocol. If the value of this object is up then the finite state machine for the Bridge network protocol has reached the Opened state.
INT pppBridgeLocalToRemoteTinygramCompression	1.3.6.1.2.1.10.23.4.1.1.2	INTEGER	read-only	Indicates whether the local node will perform Tinygram Compression when sending packets to the remote entity. If false then the local entity will not perform Tinygram Compression. If true then the local entity will perform Tinygram Compression. The value of this object is meaningful only when the link has reached the open state (pppBridgeOperStatus is opened).
INT pppBridgeRemoteToLocalTinygramCompression	1.3.6.1.2.1.10.23.4.1.1.3	INTEGER	read-only	If false(1) then the remote entity is not expected to perform Tinygram Compression. If true then the remote entity is expected to perform Tinygram Compression. The value of this object is meaningful only when the link has reached the open state (pppBridgeOperStatus is opened).
INT pppBridgeLocalToRemoteLanId	1.3.6.1.2.1.10.23.4.1.1.4	INTEGER	read-only	Indicates whether the local node will include the LAN Identification field in transmitted packets or not. If false(1) then the local node will not transmit this field, true(2) means that the field will be transmitted. The value of this object is meaningful only when the link has reached the open state (pppBridgeOperStatus is opened).
INT pppBridgeRemoteToLocalLanId	1.3.6.1.2.1.10.23.4.1.1.5	INTEGER	read-only	Indicates whether the remote node has indicated that it will include the LAN Identification field in transmitted packets or not. If false(1) then the field will not be transmitted, if true(2) then the field will be transmitted. The value of this object is meaningful only when the link has reached the open state (pppBridgeOperStatus is opened).
pppBridgeConfigTable	1.3.6.1.2.1.10.23.4.2		not-accessible	Table containing the parameters and statistics for the local PPP entity that are related to the operation of Bridging over the PPP.
pppBridgeConfigEntry	1.3.6.1.2.1.10.23.4.2.1		not-accessible	Bridging Configuration information for a particular PPP link.
INT pppBridgeConfigAdminStatus	1.3.6.1.2.1.10.23.4.2.1.1	INTEGER	read-write	The immediate desired status of the Bridging network protocol. Setting this object to open will inject an administrative open event into the Bridging network protocol's finite state machine. Setting this object to close will inject an administrative close event into the Bridging network protocol's finite state machine.
INT pppBridgeConfigTinygram	1.3.6.1.2.1.10.23.4.2.1.2	INTEGER	read-write	If false then the local BNCP entity will not initiate the Tinygram Compression Option Negotiation. If true then the local BNCP entity will initiate negotiation of this option.
INT pppBridgeConfigRingId	1.3.6.1.2.1.10.23.4.2.1.3	INTEGER	read-write	If false then the local PPP Entity will not initiate a Remote Ring Identification Option negotiation. If true then the local PPP entity will intiate this negotiation. This MIB object is relevant only if the interface is for 802.5 Token Ring bridging.
INT pppBridgeConfigLineId	1.3.6.1.2.1.10.23.4.2.1.4	INTEGER	read-write	If false then the local PPP Entity is not to initiate a Line Identification Option negotiation. If true then the local PPP entity will intiate this negotiation. This MIB object is relevant only if the interface is for 802.5 Token Ring bridging.
INT pppBridgeConfigLanId	1.3.6.1.2.1.10.23.4.2.1.5	INTEGER	read-write	If false then the local BNCP entity will not initiate the LAN Identification Option Negotiation. If true then the local BNCP entity will initiate negotiation of this option.
pppBridgeMediaTable	1.3.6.1.2.1.10.23.4.3		not-accessible	Table identifying which MAC media types are enabled for the Bridging NCPs.
pppBridgeMediaEntry	1.3.6.1.2.1.10.23.4.3.1		not-accessible	Status of a specific MAC Type for a specific PPP Link.
INT pppBridgeMediaMacType	1.3.6.1.2.1.10.23.4.3.1.1	INTEGER	read-only	The MAC type for which this entry in the pppBridgeMediaTable is providing status information. Valid values for this object are defined in Section 6.6 MAC Type Support Selection of RFC1220 (Bridging Point-to-Point Protocol).
INT pppBridgeMediaLocalStatus	1.3.6.1.2.1.10.23.4.3.1.2	INTEGER	read-only	Indicates whether the local PPP Bridging Entity will accept packets of the protocol type identified in pppBridgeMediaMacType on the PPP link identified by ifIndex or not. If this object is accept then any packets of the indicated MAC type will be received and properly processed. If this object is dont- accept then received packets of the indicated MAC type will not be properly processed.
INT pppBridgeMediaRemoteStatus	1.3.6.1.2.1.10.23.4.3.1.3	INTEGER	read-only	Indicates whether the local PPP Bridging Entity believes that the remote PPP Bridging Entity will accept packets of the protocol type identified in pppBridgeMediaMacType on the PPP link identified by ifIndex or not.
pppBridgeMediaConfigTable	1.3.6.1.2.1.10.23.4.4		not-accessible	Table identifying which MAC media types are enabled for the Bridging NCPs.
pppBridgeMediaConfigEntry	1.3.6.1.2.1.10.23.4.4.1		not-accessible	Status of a specific MAC Type for a specific PPP Link.
INT pppBridgeMediaConfigMacType	1.3.6.1.2.1.10.23.4.4.1.1	INTEGER	read-write	The MAC type for which this entry in the pppBridgeMediaConfigTable is providing status information. Valid values for this object are defined in Section 6.6 MAC Type Support Selection of RFC1220 (Bridging Point-to-Point Protocol).
INT pppBridgeMediaConfigLocalStatus	1.3.6.1.2.1.10.23.4.4.1.2	INTEGER	read-write	Indicates whether the local PPP Bridging Entity should accept packets of the protocol type identified in pppBridgeMediaConfigMacType on the PPP link identified by ifIndex or not. Setting this object to the value dont-accept has the affect of invalidating the corresponding entry in the pppBridgeMediaConfigTable object. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Changing this object will have effect when the link is next restarted.

RFC description

PPP Bridge Network Control Protocol parameters and statistics for MAC bridging over PPP.

Start monitoring vendor-neutral, standards-based MIB, RFC 1474 (PPP Bridging NCP) 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-BRIDGE-NCP-MIB

What Is PPP-BRIDGE-NCP-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description