JNX-PPPOE-MIB

All MIBs › JNX-PPPOE-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2013--0-6-

Category: Protocol: PPP, Vendor: Juniper

Description: Provides management objects for PPP over Ethernet (PPPoE) sessions and access concentrator functions on Juniper Networks devices.

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 JNX-PPPOE-MIB?

JNX-PPPOE-MIB is a Juniper Networks MIB for the Junos product family providing management objects for PPP over Ethernet (PPPoE) interfaces and access-concentrator functions, covering both PPPoE interfaces and PPPoE subinterfaces. It exposes an interface table for creating/querying PPPoE interfaces, including their maximum session limits, underlying (lower) interface linkage, access-concentrator name, and various protocol behavior flags, plus a related service-name table. In a monitoring context it is used to track PPPoE interface configuration and capacity, such as how many sessions an interface is permitted versus how it is provisioned (autoconfig, duplicate protection, PADI handling), useful for diagnosing subscriber session limits or PPPoE negotiation issues on broadband edge routers. It is a Juniper-specific extension conceptually layered on top of standard interface (ifTable/IF-MIB) indexing via its lower-layer interface reference. It is typically deployed on Juniper MX-series broadband network gateways acting as PPPoE access concentrators for residential/business subscriber aggregation. Engineers can download the JNX-PPPOE-MIB file directly to load it into their MIB browser.

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

Juniper Networks MX-series broadband network gateway

Monitoring Examples

An operator would poll jnxPPPoEIfTable/jnxPPPoEIfEntry (indexed by jnxPPPoEIfIfIndex) to check jnxPPPoEIfMaxNumSessions against actual active sessions on that PPPoE interface, and confirm jnxPPPoEIfLowerIfIndex correctly maps to the intended physical/logical underlying interface. jnxPPPoEIfAcName identifies the access-concentrator name being advertised to subscribers, while jnxPPPoEIfDupProtect and jnxPPPoEIfPADIFlag reveal whether duplicate-session protection and PADI discovery handling are enabled as expected. jnxPPPoEIfServiceNameTable would be checked to confirm the configured service names subscribers can request match provisioning.

What Can Be Monitored

PPPoE interface session limits and current usage
underlying interface mapping
access concentrator name
duplicate-session protection status
PADI/autoconfig behavior
configured service names

Imported Objects

From IF-MIB

InterfaceIndex
InterfaceIndexOrZero

From JUNIPER-SMI

jnxPppoeMibRoot

OBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Counter64
Integer32
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DisplayString
MacAddress
RowStatus
TEXTUAL-CONVENTION
TruthValue

How to Use in IPNetwork Monitor

Example using jnxPPPoEIfStatsRxPADI OID:

Select a Juniper Networks MX-series broadband network gateway 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 jnxPPPoEIfStatsRxPADI 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. It reports the number of PADI packets received. 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 sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
jnxPPPoECompliances	1.3.6.1.4.1.2636.3.67.1.4.1
jnxPPPoEConformance	1.3.6.1.4.1.2636.3.67.1.4
jnxPPPoEGroups	1.3.6.1.4.1.2636.3.67.1.4.2
STR jnxPPPoEIfAcName	1.3.6.1.4.1.2636.3.67.1.1.1.2.1.5	DisplayString	read-only	The name to use for the AC-NAME tag that is sent in any PADO that is sent on this interface.
INT jnxPPPoEIfAutoconfig	1.3.6.1.4.1.2636.3.67.1.1.1.2.1.8	INTEGER	read-only	This flags determines whether the upper PPPoEinterface is created dynamically or statically. When enable(1) the interface is created dynamically.
INT jnxPPPoEIfDupProtect	1.3.6.1.4.1.2636.3.67.1.1.1.2.1.6	INTEGER	read-only	Flag to allow duplicate MAC addresses.
STR jnxPPPoEIfDynamicProfile	1.3.6.1.4.1.2636.3.67.1.1.1.2.1.14	DisplayString	read-only	Attach dynamic-profile to this interface
jnxPPPoEIfEntry	1.3.6.1.4.1.2636.3.67.1.1.1.2.1		not-accessible	The Parameters for a particular PPPoEinterface. Creating/deleting entries in this table causes corresponding entries for be created/deleted in ifTable/ifXTable/jnxIfTable, and jnxPPPoEIfStatsTable.
NUM jnxPPPoEIfIfIndex	1.3.6.1.4.1.2636.3.67.1.1.1.2.1.1	InterfaceIndex	not-accessible	The ifIndex value of the corresponding ifEntry.
jnxPPPoEIfLayer	1.3.6.1.4.1.2636.3.67.1.1.1
MAC jnxPPPoEIfLockoutClientAddress	1.3.6.1.4.1.2636.3.67.1.1.1.4.1.1	MacAddress	not-accessible	The source MAC address if the client.
I32 jnxPPPoEIfLockoutElapsedTime	1.3.6.1.4.1.2636.3.67.1.1.1.4.1.3	Integer32	read-only	The elapsed time, in seconds, that the specified encapsulation type has been locked-out from recognition for the specified interface. Its value will not exceed that of jnxPPPoEIfLockoutTime. A value of 0 indicates that no lockout is occurring for the encapsulation type for the specified interface.
jnxPPPoEIfLockoutEntry	1.3.6.1.4.1.2636.3.67.1.1.1.4.1		not-accessible	Each entry contains the configuration and state of a particular PPPoEinterface client lockout.
I32 jnxPPPoEIfLockoutMax	1.3.6.1.4.1.2636.3.67.1.1.1.2.1.13	Integer32	read-only	The upper bound, in seconds, of the time range used to specify the duration of the lockout of the client from recognition for the specified interface. This only takes effect if jnxPPPoEIfAutoconfig is set for this interface. The ability to lockout the client from recognition in the event of an error in creating a PPP interface is enabled by default. The initial lockout duration is jnxPPPoEIfLockoutMin and increases exponentially for each failure that occurs for the client interface within the greater of 15 minutes and this object's value. The lockout duration for the client will not exceed jnxPPPoEIfLockoutMax. If the time between creation errors for the PPP interface for this interface is greater than the greater of 15 minutes and jnxPPPoEIfLockoutMax, then the lockout duration reverts to jnxPPPoEIfLockoutMin. To disable the ability to lockout the client from recognition in the event of an error in creating a PPP interface for the specified interface, the value of this object and jnxPPPoEIfLockoutMin must be set to 0. It is not recommended that this lockout feature be disabled except for debugging purposes or when this interface supports more than one session.
I32 jnxPPPoEIfLockoutMin	1.3.6.1.4.1.2636.3.67.1.1.1.2.1.12	Integer32	read-only	The lower bound, in seconds, of the time range used to specify the duration of the lockout of the client from recognition for the specified interface. This only takes effect if jnxPPPoEIfAutoconfig is set for this interface. The ability to lockout the client in the event of an error in creating a PPP interface is enabled by default. The initial lockout duration is this object's value and increases exponentially for each failure that occurs for the client creating a PPP interface for the PPPoEinterface within the greater of 15 minutes and jnxPPPoEIfLockoutMax. The lockout duration for the client will not exceed jnxPPPoEIfLockoutMax. If the time between creation errors for the PPP interface for this interface is greater than the greater of 15 minutes and jnxPPPoEIfLockoutMax, then the lockout duration reverts to this object's value. To disable the ability to lockout the client from recognition in the event of an error in creating a PPP interface for the specified interface, the value of this object and jnxPPPoEIfLockoutMin must be set to 0. It is not recommended that this lockout feature be disabled except for debugging purposes or when this interface supports more than one session.
I32 jnxPPPoEIfLockoutNextTime	1.3.6.1.4.1.2636.3.67.1.1.1.4.1.4	Integer32	read-only	The time duration, in seconds, that will be used to lockout the specified encapsulation type from recognition for the specified interface for the next event that results in a lockout condition. The reported value is within the range specified by jnxPPPoEIfLockoutMin and jnxPPPoEIfLockoutMax. When jnxPPPoEIfEnable is set to enable, a value of 0 indicates that lockout is prevented from occurring for the encapsulation type for the specified interface (i.e., jnxPPPoEIfLockoutMin and jnxPPPoEIfLockoutMax are both set to 0).
jnxPPPoEIfLockoutTable	1.3.6.1.4.1.2636.3.67.1.1.1.4		not-accessible	The lockout configuration and state of a PPPoEclient on this interface.
I32 jnxPPPoEIfLockoutTime	1.3.6.1.4.1.2636.3.67.1.1.1.4.1.2	Integer32	read-only	The time duration, in seconds, currently used to lockout the specified encapsulation type from recognition for the specified interface. The reported value is within the range specified by jnxPPPoEIfLockoutMin and jnxPPPoEIfLockoutMax. A value of 0 indicates that no lockout is occurring for the encapsulation type for the specified interface.
NUM jnxPPPoEIfLowerIfIndex	1.3.6.1.4.1.2636.3.67.1.1.1.2.1.4	InterfaceIndexOrZero	read-only	The ifIndex of an interface over which this PPPoEinterface is to be layered. A value of zero indicates no layering. An implementation may choose to require that a nonzero value be configured at entry creation.
INT jnxPPPoEIfMaxNumSessions	1.3.6.1.4.1.2636.3.67.1.1.1.2.1.2	INTEGER	read-only	The number of sessions allowed on the PPPoEinterface, zero indicates unlimited.
I32 jnxPPPoEIfMtu	1.3.6.1.4.1.2636.3.67.1.1.1.2.1.11	Integer32	read-only	The initial Maximum Transmit Unit (MTU) that the PPPoEmajor interface entity will advertise to the remote entity. If the value of this variable is 1 then the local PPPoEentity will use an MTU value determined by its underlying media interface. If the value of this variable is 2 then the local PPPoEentity will use a value determined by the PPPoEMax-Mtu-Tag transmitted from the client in the PADR packet. If no Max-Mtu-Tag is received, the value defaults to a maximum of 1494. The operational MTU is limited by the MTU of the underlying media interface minus the PPPoEframe overhead.
INT jnxPPPoEIfPADIFlag	1.3.6.1.4.1.2636.3.67.1.1.1.2.1.7	INTEGER	read-only	This flag controls whether we always respond to a PADI with a PADO regardless of the ability to create the session and allows the session establish phase to resolve it.
INT jnxPPPoEIfPadrRemoteCircuitIdCapture	1.3.6.1.4.1.2636.3.67.1.1.1.2.1.10	INTEGER	read-only	This flags determines whether the remote circuit id string will be captured and subsequently used as the NAS-PORT-ID radius attribute when it arrives as a tag in the PADR packet.
ROW jnxPPPoEIfRowStatus	1.3.6.1.4.1.2636.3.67.1.1.1.2.1.3	RowStatus	read-only	Controls creation/deletion of entries in this table with READ-CREATE maximum access, according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create an entry in this table, the following entry objects MUST be explicitly configured: jnxPPPoEIfRowStatus jnxPPPoEIfLowerIfIndex In addition, when creating an entry the following conditions must hold: A value for jnxPPPoEIfIndex must have been determined previously, by reading jnxPPPoENextIfIndex. The interface identified by jnxPPPoEIfLowerIfIndex must exist, and must be an interface type that permits layering of PPPoEabove it. A corresponding entry in ifTable/ifXTable/jnxIfTable is created or destroyed as a result of creating or destroying an entry in this table. The following values can be read from this object: active(1)
STR jnxPPPoEIfServiceNameTable	1.3.6.1.4.1.2636.3.67.1.1.1.2.1.9	DisplayString	read-only	Associate a PPPoEService Name Table with this interface for PADI processing.
jnxPPPoEIfStatsEntry	1.3.6.1.4.1.2636.3.67.1.1.1.3.1		not-accessible	The statistics for a particular PPPoEInterface.
C32 jnxPPPoEIfStatsRxInsufficientResources	1.3.6.1.4.1.2636.3.67.1.1.1.3.1.13	Counter32	read-only	Number of session requests that could not be honored due to invalid resources.
C32 jnxPPPoEIfStatsRxInvCode	1.3.6.1.4.1.2636.3.67.1.1.1.3.1.8	Counter32	read-only	Number of packets received with invalid code.
C32 jnxPPPoEIfStatsRxInvLength	1.3.6.1.4.1.2636.3.67.1.1.1.3.1.17	Counter32	read-only	Number of packets received with invalid length.
C32 jnxPPPoEIfStatsRxInvPackets	1.3.6.1.4.1.2636.3.67.1.1.1.3.1.12	Counter32	read-only	Number of invalid packets received.
C32 jnxPPPoEIfStatsRxInvPadISession	1.3.6.1.4.1.2636.3.67.1.1.1.3.1.18	Counter32	read-only	Number of PADI packets received with invalid session identifiers.
C32 jnxPPPoEIfStatsRxInvPadRSession	1.3.6.1.4.1.2636.3.67.1.1.1.3.1.19	Counter32	read-only	Number of PADR packets received with invalid session identifiers.
C32 jnxPPPoEIfStatsRxInvSession	1.3.6.1.4.1.2636.3.67.1.1.1.3.1.10	Counter32	read-only	Number of packets received with invalid session identifiers. This object became obsolete when separate counters were added for PADI and PADR packets.
C32 jnxPPPoEIfStatsRxInvTagLength	1.3.6.1.4.1.2636.3.67.1.1.1.3.1.16	Counter32	read-only	Number of packets received with invalid tag length.
C32 jnxPPPoEIfStatsRxInvTags	1.3.6.1.4.1.2636.3.67.1.1.1.3.1.9	Counter32	read-only	Number of packets received with invalid tags.
C32 jnxPPPoEIfStatsRxInvTypes	1.3.6.1.4.1.2636.3.67.1.1.1.3.1.11	Counter32	read-only	Number of packets received with invalid types.
C32 jnxPPPoEIfStatsRxInvVersion	1.3.6.1.4.1.2636.3.67.1.1.1.3.1.7	Counter32	read-only	Number of packets received with invalid version.
C32 jnxPPPoEIfStatsRxPADIEx	1.3.6.1.4.1.2636.3.67.1.1.1.3.1.1	Counter32	read-only	Number of PADI packets received.
C32 jnxPPPoEIfStatsRxPADR	1.3.6.1.4.1.2636.3.67.1.1.1.3.1.3	Counter32	read-only	Number of PADR packets received.
C32 jnxPPPoEIfStatsRxPADT	1.3.6.1.4.1.2636.3.67.1.1.1.3.1.5	Counter32	read-only	Number of PADT packets received.
jnxPPPoEIfStatsTable	1.3.6.1.4.1.2636.3.67.1.1.1.3		not-accessible	The statistics for the PPP over Ethernet Interface for the PPPoE service on this interface.
C32 jnxPPPoEIfStatsTxPADM	1.3.6.1.4.1.2636.3.67.1.1.1.3.1.14	Counter32	read-only	Number of PADM packets transmitted.
C32 jnxPPPoEIfStatsTxPADN	1.3.6.1.4.1.2636.3.67.1.1.1.3.1.15	Counter32	read-only	Number of PADN packets transmitted.
C32 jnxPPPoEIfStatsTxPADO	1.3.6.1.4.1.2636.3.67.1.1.1.3.1.2	Counter32	read-only	Number of PADO packets transmitted.
C32 jnxPPPoEIfStatsTxPADS	1.3.6.1.4.1.2636.3.67.1.1.1.3.1.4	Counter32	read-only	Number of PADS packets transmitted.
C32 jnxPPPoEIfStatsTxPADT	1.3.6.1.4.1.2636.3.67.1.1.1.3.1.6	Counter32	read-only	Number of PADT packets transmitted.
jnxPPPoEIfTable	1.3.6.1.4.1.2636.3.67.1.1.1.2		not-accessible	The parameters for the PPPoEservice on this interface.
I32 jnxPPPoEMajorInterfaceCount	1.3.6.1.4.1.2636.3.67.1.1.3.1	Integer32	read-only	The total number of PPPoEmajor interfaces configured and created in the system.
jnxPPPoEMIB	1.3.6.1.4.1.2636.3.67.1			The Point-to-Point Protocol over Ethernet (PPPoE) MIB for the Junos product family. This MIB contains managed objects for each of two interface layers: PPPoE interfaces, and PPPoE subinterfaces. For each of these layers, management objects are provided to query for an available interface index, and to create/delete interfaces of that type.
NUM jnxPPPoENextIfIndex	1.3.6.1.4.1.2636.3.67.1.1.1.1	InterfaceIndexOrZero	read-only	Coordinate ifIndex value allocation for entries in jnxPPPoEIfTable. A GET of this object returns the next available ifIndex value to be used to create an entry in the associated interface table; or zero, if no valid ifIndex value is available. This object also returns a value of zero when it is the lexicographic successor of a varbind presented in an SNMP GETNEXT or GETBULK request, for which circumstance it is assumed that ifIndex allocation is unintended. Successive GETs will typically return different values, thus avoiding collisions among cooperating management clients seeking to create table entries simultaneously.
jnxPPPoEObjects	1.3.6.1.4.1.2636.3.67.1.1
STR jnxPPPoEServiceName	1.3.6.1.4.1.2636.3.67.1.1.4.2.1.1	DisplayString	not-accessible	Service-name tag value.
JNX jnxPPPoEServiceNameAciAriAction	1.3.6.1.4.1.2636.3.67.1.1.4.3.1.3	JnxPPPoEServiceNameAction	read-only	Identifies the behavior when the the Service-name with ACI/ARI pairs is received in a PADI frame.
STR jnxPPPoEServiceNameAciAriDynamicProfile	1.3.6.1.4.1.2636.3.67.1.1.4.3.1.4	DisplayString	read-only	Dynamic Profile associated with a Service-name and ACI/ARI pairs
jnxPPPoEServiceNameAciAriEntry	1.3.6.1.4.1.2636.3.67.1.1.4.3.1		not-accessible	The parameters for the PPPoEservice-name AciAri table entry.
STR jnxPPPoEServiceNameAciAriRoutingInstance	1.3.6.1.4.1.2636.3.67.1.1.4.3.1.5	DisplayString	read-only	Routing-Instance associated with a Service-name and ACI/ARI pairs
ROW jnxPPPoEServiceNameAciAriRowStatus	1.3.6.1.4.1.2636.3.67.1.1.4.3.1.7	RowStatus	read-only	Controls creation/deletion of entries in this table with READ-CREATE maximum access, according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create an entry in this table, the following entry objects MUST be explicitly configured: jnxPPPoEServiceNameAciAriRowStatus The ACIARI Entry is configured via the INDEX specified. The following values can be read from this object: active(1)
STR jnxPPPoEServiceNameAciAriStaticInterface	1.3.6.1.4.1.2636.3.67.1.1.4.3.1.6	DisplayString	read-only	Static Interface associated with each ACI/ARI Entry.
jnxPPPoEServiceNameAciAriTable	1.3.6.1.4.1.2636.3.67.1.1.4.3		not-accessible	This table contains entries for the PPPoEServicename AciAri entries.
JNX jnxPPPoEServiceNameAction	1.3.6.1.4.1.2636.3.67.1.1.4.2.1.2	JnxPPPoEServiceNameAction	read-only	Identifies the behavior when the the Service-name tag is received in a PADI frame.
STR jnxPPPoEServiceNameAgentCircuitId	1.3.6.1.4.1.2636.3.67.1.1.4.3.1.1	DisplayString	not-accessible	ACI tag values that the PPPoEclient would send in the PADI/PADR control packet.
STR jnxPPPoEServiceNameAgentRemoteId	1.3.6.1.4.1.2636.3.67.1.1.4.3.1.2	DisplayString	not-accessible	ACI tag values that the PPPoEclient would send in the PADI/PADR control packet.
STR jnxPPPoEServiceNameDynamicProfile	1.3.6.1.4.1.2636.3.67.1.1.4.2.1.3	DisplayString	read-only	Dynamic Profile associated with a Service-name.
jnxPPPoEServiceNameEntry	1.3.6.1.4.1.2636.3.67.1.1.4.2.1		not-accessible	The parameters for the PPPoEservice-name table entry.
U32 jnxPPPoEServiceNameMaxSessions	1.3.6.1.4.1.2636.3.67.1.1.4.2.1.5	Unsigned32	read-only	The Max Sessions value used to cap the number of active PPPoEssessions that may be established with the specified Service entry.
STR jnxPPPoEServiceNameRoutingInstance	1.3.6.1.4.1.2636.3.67.1.1.4.2.1.4	DisplayString	read-only	Routing Instance associated with a Service-name.
ROW jnxPPPoEServiceNameRowStatus	1.3.6.1.4.1.2636.3.67.1.1.4.2.1.6	RowStatus	read-only	Controls creation/deletion of entries in this table with READ-CREATE maximum access ,according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create an entry in this table, the following entry objects MUST be explicitly configured: jnxPPPoEServiceNameRowStatus The Service name is configured via the INDEX specified. A corresponding entry in jnxPPPoEServiceNameAciAriTable is destroyed as a result of destroying an entry in this table. The following values can be read from this object: active(1)
jnxPPPoEServiceNameTable	1.3.6.1.4.1.2636.3.67.1.1.4.2		not-accessible	This table contains entries for the PPPoEService-names.
jnxPPPoEServiceNameTableEntry	1.3.6.1.4.1.2636.3.67.1.1.4.1.1		not-accessible	The parameters for the PPPoEservice-name table.
STR jnxPPPoEServiceNameTableName	1.3.6.1.4.1.2636.3.67.1.1.4.1.1.1	DisplayString	not-accessible	Service-name table name.
ROW jnxPPPoEServiceNameTableRowStatus	1.3.6.1.4.1.2636.3.67.1.1.4.1.1.2	RowStatus	read-only	Controls creation/deletion of entries in this table with READ-CREATE maximum access,according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create an entry in this table, the following entry objects MUST be explicitly configured: jnxPPPoEServiceNameTableRowStatus jnxPPPoEServiceNameTableName The Empty Service and Any service will be automatically configured for each Service Name Table created. On creating or deleting an entry in this table will create/destroy an entry for Service and service in jnxServiceNameTable. A corresponding entry in jnxServiceNameTable gets created or destroyed as a result of creating or destroying an entry in this table. The following values can be read from this object: active(1)
jnxPPPoEServiceNameTableTable	1.3.6.1.4.1.2636.3.67.1.1.4.1		not-accessible	This table contains entries for the PPPoEService-name tables.
jnxPPPoEServices	1.3.6.1.4.1.2636.3.67.1.1.4
jnxPPPoESubIfEntry	1.3.6.1.4.1.2636.3.67.1.1.2.2.1		not-accessible	Each entry describes the characteristics of a PPPoESubinterface. With READ-CREATE maximum access ,creating/deleting entries in this table causes corresponding entries for be created /deleted in ifTable/ifXTable/jnxIfTable.
I32 jnxPPPoESubIfId	1.3.6.1.4.1.2636.3.67.1.1.2.2.1.4	Integer32	read-only	An integer identifier for the PPPoEsubinterface, used in conjunction with the command-line interface. It is provided here for cross-reference purposes only. The value must be unique among subinterfaces configured on the same underlying PPPoEinterface. If this object is not configured, or is configured with a value of -1, a nonzero value will be allocated internally and can be retrieved from this object after table entry creation has succeeded. A value of zero for this object is reserved for future use.
NUM jnxPPPoESubIfIndex	1.3.6.1.4.1.2636.3.67.1.1.2.2.1.1	InterfaceIndex	not-accessible	The ifIndex of the PPPoESubinterface. When creating entries in this table, suitable values for this object are determined by reading jnxPPPoESubNextIfIndex.
jnxPPPoESubIfLayer	1.3.6.1.4.1.2636.3.67.1.1.2
NUM jnxPPPoESubIfLowerIfIndex	1.3.6.1.4.1.2636.3.67.1.1.2.2.1.3	InterfaceIndexOrZero	read-only	The ifIndex of a PPPoEinterface over which this PPPoESubinterface is to be layered. A value of zero indicates no layering. An implementation may choose to require that a nonzero value be configured at entry creation.
STR jnxPPPoESubIfMotm	1.3.6.1.4.1.2636.3.67.1.1.2.2.1.6	DisplayString	read-only	A message to send via a PADM on the sub-interface when the sub-interface transitions to the ifOperStatusUp state. The client may choose to display this message to the user.
NUM jnxPPPoESubIfNextIfIndex	1.3.6.1.4.1.2636.3.67.1.1.2.1	InterfaceIndexOrZero	read-only	Coordinate ifIndex value allocation for entries in jnxPPPoESubIfTable. A GET of this object returns the next available ifIndex value to be used to create an entry in the associated interface table; or zero, if no valid ifIndex value is available. This object also returns a value of zero when it is the lexicographic successor of a varbind presented in an SNMP GETNEXT or GETBULK request, for which circumstance it is assumed that ifIndex allocation is unintended. Successive GETs will typically return different values, thus avoiding collisions among cooperating management clients seeking to create table entries simultaneously.
jnxPppoeSubIfPerQueueStatsEntry	1.3.6.1.4.1.2636.3.67.1.1.2.3.1		not-accessible	The statistics for a particular trrafic class queue for PPPoEsub Interface(i.e. session). ). Forwarding class to queue number mapping is not always one-to-one. Forwarding classes and queues are the same only when default forwarding-class-to-queue mapping is in effect
INT jnxPppoeSubIfQueueIndex	1.3.6.1.4.1.2636.3.67.1.1.2.3.1.1	INTEGER	not-accessible	This attribute returns the queue index ranging from 0 to 7 of the queue configure on the PPPoEsubinterface to support the traffic class for PPPoEsession configured on that subinterface. Forwarding class to queue number mapping is not always one-to-one. Forwarding classes and queues are the same only when default forwarding-class-to-queue mapping is in effect.
C32 jnxPppoeSubIfQueueStatsActualBitRate	1.3.6.1.4.1.2636.3.67.1.1.2.3.1.6	Counter32	read-only	This attribute returns the actual bit rate for per PPPoEsession and per queue.
C32 jnxPppoeSubIfQueueStatsActualDroppedBitRate	1.3.6.1.4.1.2636.3.67.1.1.2.3.1.7	Counter32	read-only	This attribute returns the actual dropped bit rate for per PPPoEsession and per queue.
C64 jnxPppoeSubIfQueueStatsBytesDropped	1.3.6.1.4.1.2636.3.67.1.1.2.3.1.5	Counter64	read-only	This attribute returns the number of bytes dropped per PPPoEsession and per queue.
C64 jnxPppoeSubIfQueueStatsBytesSent	1.3.6.1.4.1.2636.3.67.1.1.2.3.1.3	Counter64	read-only	This attribute returns the counts of number of bytes sent per PPPoEsession and per queue.
C64 jnxPppoeSubIfQueueStatsPacketDropped	1.3.6.1.4.1.2636.3.67.1.1.2.3.1.4	Counter64	read-only	This attribute returns the number of packet dropped per PPPoEsession and per queue.
C64 jnxPppoeSubIfQueueStatsPacketSent	1.3.6.1.4.1.2636.3.67.1.1.2.3.1.2	Counter64	read-only	This attribute returns the counts of number of packet sent per PPPoEsession and per queue.
jnxPppoeSubIfQueueStatsTable	1.3.6.1.4.1.2636.3.67.1.1.2.3		not-accessible	Table containing the Queue parameters for the PPPoEsessions.
ROW jnxPPPoESubIfRowStatus	1.3.6.1.4.1.2636.3.67.1.1.2.2.1.2	RowStatus	read-only	Controls creation/deletion of entries in this table with READ-CREATE maximum access ,according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create an entry in this table, the following entry objects MUST be explicitly configured: jnxPPPoESubIfRowStatus jnxPPPoESubIfLowerIfIndex In addition, when creating an entry the following conditions must hold: A value for jnxPPPoESubIfIndex must have been determined previously, by reading jnxPPPoESubIfNextIfIndex. The interface identified by jnxPPPoESubIfLowerIfIndex must exist, and must be a PPPoEinterface. A positive value configured for jnxPPPoESubIfId must not already be assigned to another subinterface layered onto the same underlying PPPoEinterface. A corresponding entry in ifTable/ifXTable/jnxIfTable is created or destroyed as a result of creating or destroying an entry in this table. The following values can be read from this object: active(1)
I32 jnxPPPoESubIfSessionId	1.3.6.1.4.1.2636.3.67.1.1.2.2.1.5	Integer32	read-only	The current sessionId associated with this sub-interface.
jnxPPPoESubIfTable	1.3.6.1.4.1.2636.3.67.1.1.2.2		not-accessible	This table contains entries for PPPoESubinterfaces present in the system.
STR jnxPPPoESubIfUrl	1.3.6.1.4.1.2636.3.67.1.1.2.2.1.7	DisplayString	read-only	A URL to be sent via a PADM on the sub-interface when the sub-interface transitions to the ifOperStatusUp state. The client may use this URL as the initial web-page for the user.
jnxPPPoESummary	1.3.6.1.4.1.2636.3.67.1.1.3
I32 jnxPPPoESummaryMajorIfAdminDown	1.3.6.1.4.1.2636.3.67.1.1.3.3	Integer32	read-only	The total number of PPPoEmajor interfaces in the system that are administrateively configued to down(2).
I32 jnxPPPoESummaryMajorIfAdminUp	1.3.6.1.4.1.2636.3.67.1.1.3.2	Integer32	read-only	The total number of PPPoEmajor interfaces in the system that are administratively configured to up(1).
I32 jnxPPPoESummaryMajorIfLowerLayerDown	1.3.6.1.4.1.2636.3.67.1.1.3.6	Integer32	read-only	The total number of PPPoEmajor interfaces in the system with an operational state of lowerLayerDown(7).
I32 jnxPPPoESummaryMajorIfNotPresent	1.3.6.1.4.1.2636.3.67.1.1.3.7	Integer32	read-only	The total number of PPPoEmajor interfaces in the system with an operational state of notPresent(6).
I32 jnxPPPoESummaryMajorIfOperDown	1.3.6.1.4.1.2636.3.67.1.1.3.5	Integer32	read-only	The total number of PPPoEmajor interfaces in the system with an operational state of down(2).
I32 jnxPPPoESummaryMajorIfOperUp	1.3.6.1.4.1.2636.3.67.1.1.3.4	Integer32	read-only	The total number of PPPoEmajor interfaces in the system with an operational state of up(1).
I32 jnxPPPoESummarySubIfAdminDown	1.3.6.1.4.1.2636.3.67.1.1.3.10	Integer32	read-only	The total number of PPPoEsubinterfaces in the system that are administrateively configued to down(2).
I32 jnxPPPoESummarySubIfAdminUp	1.3.6.1.4.1.2636.3.67.1.1.3.9	Integer32	read-only	The total number of PPPoEsubinterfaces in the system that are administratively configured to up(1).
I32 jnxPPPoESummarySubIfLowerLayerDown	1.3.6.1.4.1.2636.3.67.1.1.3.13	Integer32	read-only	The total number of PPPoEsubinterfaces in the system with an operational state of lowerLayerDown(7).
I32 jnxPPPoESummarySubIfNotPresent	1.3.6.1.4.1.2636.3.67.1.1.3.14	Integer32	read-only	The total number of PPPoEsubinterfaces in the system with an operational state of notPresent(6).
I32 jnxPPPoESummarySubIfOperDown	1.3.6.1.4.1.2636.3.67.1.1.3.12	Integer32	read-only	The total number of PPPoEsubinterfaces in the system with an operational state of down(2).
I32 jnxPPPoESummarySubIfOperUp	1.3.6.1.4.1.2636.3.67.1.1.3.11	Integer32	read-only	The total number of PPPoEsubinterfaces in the system with an operational state of up(1).
I32 jnxPPPoESummarySubInterfaceCount	1.3.6.1.4.1.2636.3.67.1.1.3.8	Integer32	read-only	The total number of PPPoEsubinterfaces configured in the system.

RFC description

Juniper Networks Point-to-Point Protocol over Ethernet (PPPoE) MIB for interface and subinterface management.

Start monitoring Juniper Networks MX-series broadband network gateway 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 JNX-PPPOE-MIB