All MIBs › Juniper-PPPOE-MIB
Organization: Juniper Networks, Inc.
Last Updated: 2008-11-27
Category: Protocol: PPP, Vendor: Juniper
Description: Juniper Networks MIB for monitoring PPPoE session statistics and subscriber connections on Juniper E-series broadband edge routers.
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 Juniper-PPPOE-MIB?
Juniper-PPPoE-MIB manages PPPoE (Point-to-Point Protocol over Ethernet) interfaces and subinterfaces on Juniper E-series broadband edge routers, covering both the PPPoE access-concentrator interface layer and per-session subinterfaces used for subscriber connections. It exposes interface creation/deletion via row status, session limits, access-concentrator naming, duplicate-session protection, and PADI (PPPoE Active Discovery Initiation) handling flags. Its monitoring value centers on subscriber session software health: tracking how many PPPoE sessions are active against juniPPPoEIfMaxNumSessions, and diagnosing session establishment failures via duplicate-protection or PADI flag settings, which directly affects broadband subscriber connectivity. Creating/deleting PPPoE interfaces here has documented side effects on the standard IF-MIB ifTable/ifXTable and the Juniper-UNI-IF-MIB, making those dependencies explicit. It is deployed on Juniper E-series routers serving as PPPoE broadband access concentrators. Engineers can download the Juniper-PPPOE-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in Juniper-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 E-series broadband edge router
Monitoring Examples
An administrator monitors juniPPPoEIfTable/juniPPPoEIfEntry to compare current session counts against juniPPPoEIfMaxNumSessions, watching for subscribers being rejected once the limit is reached. Checking juniPPPoEIfDupProtect and juniPPPoEIfPADIFlag helps diagnose why a subscriber's PPPoE session isn't establishing, for example duplicate-session protection blocking a legitimate reconnect. juniPPPoEIfServiceNameTable is reviewed when a subscriber requests a specific PPPoE service name that isn't being offered, and juniPPPoEIfAutoconfig indicates whether subinterfaces are being auto-provisioned as sessions come up.
What Can Be Monitored
- active PPPoE session count vs. limit
- PPPoE interface/subinterface status
- duplicate session protection state
- PADI handling flag
- offered PPPoE service names
- subinterface autoconfiguration state
This MIB depends on
Related MIBs
Imported Objects
From IF-MIB
| InterfaceIndex | |
| InterfaceIndexOrZero |
From Juniper-MIBs
| juniMibs | MODULE-IDENTITY |
From Juniper-TC
| JuniEnable | |
| JuniNextIfIndex |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Counter32 | |
| Integer32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE | |
| Unsigned32 |
From SNMPv2-TC
| DisplayString | |
| MacAddress | |
| RowStatus | |
| TEXTUAL-CONVENTION | |
| TruthValue |
How to Use in IPNetwork Monitor
Example using juniPPPoEIfStatsRxPADI OID:
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| juniPPPoECompliance | 1.3.6.1.4.1.4874.2.2.18.4.5.1 | Obsolete compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when profile support and new sub-interface objects were added. | ||
| juniPPPoECompliance10 | 1.3.6.1.4.1.4874.2.2.18.4.5.10 | Obsolete compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when support was added for lockout configuration. | ||
| juniPPPoECompliance11 | 1.3.6.1.4.1.4874.2.2.18.4.5.11 | Obsolete compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when support was added for juniPPPoEMaxSessionVsa. | ||
| juniPPPoECompliance12 | 1.3.6.1.4.1.4874.2.2.18.4.5.12 | The compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when support was added for juniPPPoEServiceNameTableUnknownAction | ||
| juniPPPoECompliance13 | 1.3.6.1.4.1.4874.2.2.18.4.5.13 | The compliance statement for entities which implement the Juniper PPPoE MIB. | ||
| juniPPPoECompliance2 | 1.3.6.1.4.1.4874.2.2.18.4.5.2 | Obsolete compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when interface summary statistics objects were added. | ||
| juniPPPoECompliance3 | 1.3.6.1.4.1.4874.2.2.18.4.5.3 | Obsolete compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when the profile objects were deprecated. | ||
| juniPPPoECompliance4 | 1.3.6.1.4.1.4874.2.2.18.4.5.4 | Obsolete compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when new objects were added. | ||
| juniPPPoECompliance5 | 1.3.6.1.4.1.4874.2.2.18.4.5.5 | Obsolete compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when PADI flag support was added. | ||
| juniPPPoECompliance6 | 1.3.6.1.4.1.4874.2.2.18.4.5.6 | Obsolete compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when PADN counter support was added. | ||
| juniPPPoECompliance7 | 1.3.6.1.4.1.4874.2.2.18.4.5.7 | Obsolete compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when support was added for service name table, invalid length and tag length counters, and the invalid session counter was replaced by separate PADI and PADR invalid session counters. | ||
| juniPPPoECompliance8 | 1.3.6.1.4.1.4874.2.2.18.4.5.8 | Obsolete compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when support was added for remote circuit id capture. | ||
| juniPPPoECompliance9 | 1.3.6.1.4.1.4874.2.2.18.4.5.9 | Obsolete compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when support was added for MTU configuration. | ||
| juniPPPoECompliances | 1.3.6.1.4.1.4874.2.2.18.4.5 | |||
| juniPPPoEConformance | 1.3.6.1.4.1.4874.2.2.18.4 | |||
| juniPPPoEGlobal | 1.3.6.1.4.1.4874.2.2.18.1.3 | |||
| STR juniPPPoEGlobalMotm | 1.3.6.1.4.1.4874.2.2.18.1.3.1 | DisplayString | read-write | A message to send via a PADM to all sub-interface that are currently in ifOperStatusUp state. A client may choose to display this information to the user. Retrieving this object always returns a null string. |
| juniPPPoEGroup | 1.3.6.1.4.1.4874.2.2.18.4.4.1 | Obsolete collection of objects providing management of PPPoE interfaces in a Juniper product. This statement became obsolete when new objects were added. | ||
| juniPPPoEGroup10 | 1.3.6.1.4.1.4874.2.2.18.4.4.16 | A collection of objects providing management of PPPoE interfaces in a Juniper product. | ||
| juniPPPoEGroup2 | 1.3.6.1.4.1.4874.2.2.18.4.4.4 | Obsolete collection of objects providing management of PPPoE interfaces in a Juniper product. This statement became obsolete when new objects were added. | ||
| juniPPPoEGroup3 | 1.3.6.1.4.1.4874.2.2.18.4.4.7 | Obsolete collection of objects providing management of PPPoE interfaces in a Juniper product. This group became obsolete when PADI flag support was added. | ||
| juniPPPoEGroup4 | 1.3.6.1.4.1.4874.2.2.18.4.4.8 | Obsolete collection of objects providing management of PPPoE interfaces in a Juniper product. This group became obsolete when PADN counter support was added. | ||
| juniPPPoEGroup5 | 1.3.6.1.4.1.4874.2.2.18.4.4.9 | Obsolete collection of objects providing management of PPPoE interfaces in a Juniper product. This group became obsolete when support was added for invalid length and tag length counters and the invalid session counter was replaced by separate PADI and PADR invalid session counters. | ||
| juniPPPoEGroup6 | 1.3.6.1.4.1.4874.2.2.18.4.4.10 | A collection of objects providing management of PPPoE interfaces in a Juniper product. | ||
| juniPPPoEGroup7 | 1.3.6.1.4.1.4874.2.2.18.4.4.12 | A collection of objects providing management of PPPoE interfaces in a Juniper product. | ||
| juniPPPoEGroup8 | 1.3.6.1.4.1.4874.2.2.18.4.4.13 | A collection of objects providing management of PPPoE interfaces in a Juniper product. | ||
| juniPPPoEGroup9 | 1.3.6.1.4.1.4874.2.2.18.4.4.15 | A collection of objects providing management of PPPoE interfaces in a Juniper product. | ||
| juniPPPoEGroups | 1.3.6.1.4.1.4874.2.2.18.4.4 | |||
| STR juniPPPoEIfAcName | 1.3.6.1.4.1.4874.2.2.18.1.1.2.1.5 | DisplayString | read-create | The name to use for the AC-NAME tag that is sent in any PADO that is sent on this interface. |
| JUN juniPPPoEIfAutoconfig | 1.3.6.1.4.1.4874.2.2.18.1.1.2.1.8 | JuniEnable | read-create | This flags determines whether the upper PPPoE interface is created dynamically or statically. When enable(1) the interface is created dynamically. |
| JUN juniPPPoEIfDupProtect | 1.3.6.1.4.1.4874.2.2.18.1.1.2.1.6 | JuniEnable | read-create | Flag to allow duplicate MAC addresses. |
| juniPPPoEIfEntry | 1.3.6.1.4.1.4874.2.2.18.1.1.2.1 | not-accessible | The Parameters for a particular PPPoE interface. Creating/deleting entries in this table causes corresponding entries for be created/deleted in ifTable/ifXTable/juniIfTable, and juniPPPoEIfStatsTable. | |
| NUM juniPPPoEIfIfIndex | 1.3.6.1.4.1.4874.2.2.18.1.1.2.1.1 | InterfaceIndex | read-only | The ifIndex value of the corresponding ifEntry. |
| juniPPPoEIfLayer | 1.3.6.1.4.1.4874.2.2.18.1.1 | |||
| MAC juniPPPoEIfLockoutClientAddress | 1.3.6.1.4.1.4874.2.2.18.1.1.4.1.1 | MacAddress | not-accessible | The source MAC address if the client. |
| I32 juniPPPoEIfLockoutElapsedTime | 1.3.6.1.4.1.4874.2.2.18.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 juniPPPoEIfLockoutTime. A value of 0 indicates that no lockout is occurring for the encapsulation type for the specified interface. |
| juniPPPoEIfLockoutEntry | 1.3.6.1.4.1.4874.2.2.18.1.1.4.1 | not-accessible | Each entry contains the configuration and state of a particular PPPoE interface client lockout. | |
| I32 juniPPPoEIfLockoutMax | 1.3.6.1.4.1.4874.2.2.18.1.1.2.1.13 | Integer32 | read-write | 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 juniPPPoEIfAutoconfig 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 juniPPPoEIfLockoutMin 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 juniPPPoEIfLockoutMax. If the time between creation errors for the PPP interface for this interface is greater than the greater of 15 minutes and juniPPPoEIfLockoutMax, then the lockout duration reverts to juniPPPoEIfLockoutMin. 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 juniPPPoEIfLockoutMin 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 juniPPPoEIfLockoutMin | 1.3.6.1.4.1.4874.2.2.18.1.1.2.1.12 | Integer32 | read-write | 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 juniPPPoEIfAutoconfig 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 PPPoE interface within the greater of 15 minutes and juniPPPoEIfLockoutMax. The lockout duration for the client will not exceed juniPPPoEIfLockoutMax. If the time between creation errors for the PPP interface for this interface is greater than the greater of 15 minutes and juniPPPoEIfLockoutMax, 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 juniPPPoEIfLockoutMin 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 juniPPPoEIfLockoutNextTime | 1.3.6.1.4.1.4874.2.2.18.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 juniPPPoEIfLockoutMin and juniPPPoEIfLockoutMax. When juniPPPoEIfEnable 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., juniPPPoEIfLockoutMin and juniPPPoEIfLockoutMax are both set to 0). |
| juniPPPoEIfLockoutTable | 1.3.6.1.4.1.4874.2.2.18.1.1.4 | not-accessible | The lockout configuration and state of a PPPoE client on this interface. | |
| I32 juniPPPoEIfLockoutTime | 1.3.6.1.4.1.4874.2.2.18.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 juniPPPoEIfLockoutMin and juniPPPoEIfLockoutMax. A value of 0 indicates that no lockout is occurring for the encapsulation type for the specified interface. |
| NUM juniPPPoEIfLowerIfIndex | 1.3.6.1.4.1.4874.2.2.18.1.1.2.1.4 | InterfaceIndexOrZero | read-create | The ifIndex of an interface over which this PPPoE interface 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 juniPPPoEIfMaxNumSessions | 1.3.6.1.4.1.4874.2.2.18.1.1.2.1.2 | INTEGER | read-create | The number of sessions allowed on the PPPoE interface, zero indicates unlimited. |
| I32 juniPPPoEIfMtu | 1.3.6.1.4.1.4874.2.2.18.1.1.2.1.11 | Integer32 | read-write | The initial Maximum Transmit Unit (MTU) that the PPPoE major interface entity will advertise to the remote entity. If the value of this variable is 1 then the local PPPoE entity will use an MTU value determined by its underlying media interface. If the value of this variable is 2 then the local PPPoE entity will use a value determined by the PPPoE Max-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 PPPoE frame overhead. |
| JUN juniPPPoEIfPADIFlag | 1.3.6.1.4.1.4874.2.2.18.1.1.2.1.7 | JuniEnable | read-create | 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. |
| JUN juniPPPoEIfPadrRemoteCircuitIdCapture | 1.3.6.1.4.1.4874.2.2.18.1.1.2.1.10 | JuniEnable | read-create | 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 juniPPPoEIfRowStatus | 1.3.6.1.4.1.4874.2.2.18.1.1.2.1.3 | RowStatus | read-create | Controls creation/deletion of entries in this table 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: juniPPPoEIfRowStatus juniPPPoEIfLowerIfIndex In addition, when creating an entry the following conditions must hold: A value for juniPPPoEIfIndex must have been determined previously, by reading juniPPPoENextIfIndex. The interface identified by juniPPPoEIfLowerIfIndex must exist, and must be an interface type that permits layering of PPPoE above it. A corresponding entry in ifTable/ifXTable/juniIfTable is created or destroyed as a result of creating or destroying an entry in this table. |
| U32 juniPPPoEIfServiceNameTable | 1.3.6.1.4.1.4874.2.2.18.1.1.2.1.9 | Unsigned32 | read-create | Associate a PPPoE Service Name Table with this interface for PADI processing. |
| juniPPPoEIfStatsEntry | 1.3.6.1.4.1.4874.2.2.18.1.1.3.1 | not-accessible | The statistics for a particular PPPoE Interface. | |
| C32 juniPPPoEIfStatsRxInsufficientResources | 1.3.6.1.4.1.4874.2.2.18.1.1.3.1.13 | Counter32 | read-only | Number of session requests that could not be honored due to invalid resources. |
| C32 juniPPPoEIfStatsRxInvCode | 1.3.6.1.4.1.4874.2.2.18.1.1.3.1.8 | Counter32 | read-only | Number of packets received with invalid code. |
| C32 juniPPPoEIfStatsRxInvLength | 1.3.6.1.4.1.4874.2.2.18.1.1.3.1.17 | Counter32 | read-only | Number of packets received with invalid length. |
| C32 juniPPPoEIfStatsRxInvPackets | 1.3.6.1.4.1.4874.2.2.18.1.1.3.1.12 | Counter32 | read-only | Number of invalid packets received. |
| C32 juniPPPoEIfStatsRxInvPadISession | 1.3.6.1.4.1.4874.2.2.18.1.1.3.1.18 | Counter32 | read-only | Number of PADI packets received with invalid session identifiers. |
| C32 juniPPPoEIfStatsRxInvPadRSession | 1.3.6.1.4.1.4874.2.2.18.1.1.3.1.19 | Counter32 | read-only | Number of PADR packets received with invalid session identifiers. |
| C32 juniPPPoEIfStatsRxInvSession | 1.3.6.1.4.1.4874.2.2.18.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 juniPPPoEIfStatsRxInvTagLength | 1.3.6.1.4.1.4874.2.2.18.1.1.3.1.16 | Counter32 | read-only | Number of packets received with invalid tag length. |
| C32 juniPPPoEIfStatsRxInvTags | 1.3.6.1.4.1.4874.2.2.18.1.1.3.1.9 | Counter32 | read-only | Number of packets received with invalid tags. |
| C32 juniPPPoEIfStatsRxInvTypes | 1.3.6.1.4.1.4874.2.2.18.1.1.3.1.11 | Counter32 | read-only | Number of packets received with invalid types. |
| C32 juniPPPoEIfStatsRxInvVersion | 1.3.6.1.4.1.4874.2.2.18.1.1.3.1.7 | Counter32 | read-only | Number of packets received with invalid version. |
| C32 juniPPPoEIfStatsRxPADIEx | 1.3.6.1.4.1.4874.2.2.18.1.1.3.1.1 | Counter32 | read-only | Number of PADI packets received. |
| C32 juniPPPoEIfStatsRxPADR | 1.3.6.1.4.1.4874.2.2.18.1.1.3.1.3 | Counter32 | read-only | Number of PADR packets received. |
| C32 juniPPPoEIfStatsRxPADT | 1.3.6.1.4.1.4874.2.2.18.1.1.3.1.5 | Counter32 | read-only | Number of PADT packets received. |
| juniPPPoEIfStatsTable | 1.3.6.1.4.1.4874.2.2.18.1.1.3 | not-accessible | The statistics for the PPP over Ethernet Interface for the PPPoE service on this interface. | |
| C32 juniPPPoEIfStatsTxPADM | 1.3.6.1.4.1.4874.2.2.18.1.1.3.1.14 | Counter32 | read-only | Number of PADM packets transmitted. |
| C32 juniPPPoEIfStatsTxPADN | 1.3.6.1.4.1.4874.2.2.18.1.1.3.1.15 | Counter32 | read-only | Number of PADN packets transmitted. |
| C32 juniPPPoEIfStatsTxPADO | 1.3.6.1.4.1.4874.2.2.18.1.1.3.1.2 | Counter32 | read-only | Number of PADO packets transmitted. |
| C32 juniPPPoEIfStatsTxPADS | 1.3.6.1.4.1.4874.2.2.18.1.1.3.1.4 | Counter32 | read-only | Number of PADS packets transmitted. |
| C32 juniPPPoEIfStatsTxPADT | 1.3.6.1.4.1.4874.2.2.18.1.1.3.1.6 | Counter32 | read-only | Number of PADT packets transmitted. |
| juniPPPoEIfTable | 1.3.6.1.4.1.4874.2.2.18.1.1.2 | not-accessible | The parameters for the PPPoE service on this interface. | |
| juniPPPoELockoutTableGroup | 1.3.6.1.4.1.4874.2.2.18.4.4.14 | A collection of objects providing management of PPPoE lockout tables in a Juniper product. | ||
| I32 juniPPPoEMajorInterfaceCount | 1.3.6.1.4.1.4874.2.2.18.1.5.1 | Integer32 | read-only | The total number of PPPoE major interfaces configured and created in the system. |
| INT juniPPPoEMaxSessionVsa | 1.3.6.1.4.1.4874.2.2.18.1.1.2.1.14 | INTEGER | read-write | Configure the action to be taken by PPPoE when RADIUS server returns the PPPoE max-session value: override Override the current PPPoE max-session value with the value returned by RADIUS server. Ignore Ignore the max-session value returned by RADIUS server |
| juniPPPoEMIB | 1.3.6.1.4.1.4874.2.2.18 | The Point-to-Point Protocol over Ethernet (PPPoE) MIB for the Juniper E-series 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. Creating/deleting these interface types using this MIB has the side effect of creating/deleting corresponding entries in the IF-MIB ifTable/ifXTable, and in the Juniper-UNI-IF-MIB.juniIfTable. | ||
| JUN juniPPPoENextIfIndex | 1.3.6.1.4.1.4874.2.2.18.1.1.1 | JuniNextIfIndex | read-only | Coordinate ifIndex value allocation for entries in juniPPPoEIfTable. 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. |
| juniPPPoEObjects | 1.3.6.1.4.1.4874.2.2.18.1 | |||
| juniPPPoEProfile | 1.3.6.1.4.1.4874.2.2.18.1.4 | |||
| juniPPPoEProfileEntry | 1.3.6.1.4.1.4874.2.2.18.1.4.1.1 | not-accessible | Each entry describes the characteristics of the PPPoE components of a profile entry. Each entry is applied to an interface when the IP interface above the PPPoE sub-interface becomes active. | |
| juniPPPoEProfileGroup | 1.3.6.1.4.1.4874.2.2.18.4.4.3 | A collection of objects providing management of PPPoE profile entries in a Juniper product. This group has been deprecated because the information is now supported in the Juniper-PPPOE-PROFILE-MIB. | ||
| U32 juniPPPoEProfileIndex | 1.3.6.1.4.1.4874.2.2.18.1.4.1.1.1 | Unsigned32 | not-accessible | This is the index of the profile that the attributes are being set in. The index must exist before creating a row in this table. The index is equivalent to juniProfileIdId in the juniProfileIdTable. |
| STR juniPPPoEProfileMotm | 1.3.6.1.4.1.4874.2.2.18.1.4.1.1.3 | DisplayString | read-create | A message to send via a PADM on the sub-interface when this profile is applied to the IP interface above this PPPoE sub-interface. A client may choose to display this message to the user. |
| ROW juniPPPoEProfileRowStatus | 1.3.6.1.4.1.4874.2.2.18.1.4.1.1.2 | RowStatus | read-create | Controls creation/deletion of entries in this table according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy The index must exist in the profile manager before this entry can be created. CreateAndGo simply adds a table entry to the PPPoE component. Destroy deletes the entry in the PPPoE component (but not the entry in other components), and removes all PPPoE information relating to this profile. |
| juniPPPoEProfileTable | 1.3.6.1.4.1.4874.2.2.18.1.4.1 | not-accessible | This table contains entries for the PPPoE portion of a profile entry. | |
| STR juniPPPoEProfileUrl | 1.3.6.1.4.1.4874.2.2.18.1.4.1.1.4 | DisplayString | read-create | A URL to be sent via a PADM on the sub-interface when this profile is applied to the IP interface above this PPPoE sub-interface. The string entered here can have several substitutions applied: %D is replaced with the profile name %d is replaced with the domain name %u is replaced with the user name %U is replaced with the user/domain name together %% is replaced with the % character The resulting string must not be greater than 127 octets long. The client may use this URL as the initial web-page for the user. |
| STR juniPPPoEServiceName | 1.3.6.1.4.1.4874.2.2.18.1.6.3.1.1 | DisplayString | not-accessible | Service-name tag value. |
| JUN juniPPPoEServiceNameAction | 1.3.6.1.4.1.4874.2.2.18.1.6.3.1.2 | JuniPPPoEServiceNameAction | read-create | Identifies the behavior when the Service-name tag is received in a PADI/PADR frame. |
| juniPPPoEServiceNameEntry | 1.3.6.1.4.1.4874.2.2.18.1.6.3.1 | not-accessible | The parameters for the PPPoE service-name table entry. | |
| ROW juniPPPoEServiceNameRowStatus | 1.3.6.1.4.1.4874.2.2.18.1.6.3.1.3 | RowStatus | read-create | Controls creation/deletion of entries in this table 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: juniPPPoEServiceNameRowStatus The Service name is configured via the INDEX specified. A corresponding entry in juniServiceNameTable is created or destroyed as a result of creating or destroying an entry in this table. |
| juniPPPoEServiceNameTable | 1.3.6.1.4.1.4874.2.2.18.1.6.3 | not-accessible | This table contains entries for the PPPoE Service-names. | |
| JUN juniPPPoEServiceNameTableEmptyAction | 1.3.6.1.4.1.4874.2.2.18.1.6.2.1.3 | JuniPPPoEServiceNameAction | read-create | Identifies the behavior when the empty (zero length) Service-name tag is received in a PADI frame. |
| juniPPPoEServiceNameTableEntry | 1.3.6.1.4.1.4874.2.2.18.1.6.2.1 | not-accessible | The parameters for the PPPoE service-name table. | |
| juniPPPoEServiceNameTableGroup | 1.3.6.1.4.1.4874.2.2.18.4.4.11 | A collection of objects providing management of PPPoE service-name tables in a Juniper product. This group became obsolete when juniPPPoEServiceNameTableUnknownAction object is added | ||
| juniPPPoEServiceNameTableGroup1 | 1.3.6.1.4.1.4874.2.2.18.4.4.17 | A collection of objects providing management of PPPoE service-name tables in a Juniper product. | ||
| U32 juniPPPoEServiceNameTableIndex | 1.3.6.1.4.1.4874.2.2.18.1.6.2.1.1 | Unsigned32 | not-accessible | The index value of the Service-name Table Entry. |
| STR juniPPPoEServiceNameTableName | 1.3.6.1.4.1.4874.2.2.18.1.6.2.1.2 | DisplayString | read-create | Service-name table name. |
| U32 juniPPPoEServiceNameTableNextIndex | 1.3.6.1.4.1.4874.2.2.18.1.6.1 | Unsigned32 | read-only | Coordinate ifIndex value allocation for entries in juniPPPoEServiceNameTableTable. A GET of this object returns the next available ifIndex value to be used to create an entry in the associated service-name table 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. |
| ROW juniPPPoEServiceNameTableRowStatus | 1.3.6.1.4.1.4874.2.2.18.1.6.2.1.4 | RowStatus | read-create | Controls creation/deletion of entries in this table 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: juniPPPoEServiceNameTableRowStatus juniPPPoEServiceNameTableName Optionally, juniPPPoEServiceNameTableEmptyAction (default is terminate) or juniPPPoEServiceNameTableUnknownAction (default is drop) may be specified . In addition, when creating an entry the following conditions must hold: A value for juniPPPoEServiceNameTableIndex must have been determined previously, by reading juniPPPoEServiceNameTableNextIndex. A corresponding entry in juniServiceNameTable is created or destroyed as a result of creating or destroying an entry in this table. |
| juniPPPoEServiceNameTableTable | 1.3.6.1.4.1.4874.2.2.18.1.6.2 | not-accessible | This table contains entries for the PPPoE Service-name tables. | |
| JUN juniPPPoEServiceNameTableUnknownAction | 1.3.6.1.4.1.4874.2.2.18.1.6.2.1.5 | JuniPPPoEServiceNameAction | read-create | Identifies the behavior when the unknown (unconfigured) Service-name tag is received in a PADI frame. |
| juniPPPoEServices | 1.3.6.1.4.1.4874.2.2.18.1.6 | |||
| juniPPPoESubIfEntry | 1.3.6.1.4.1.4874.2.2.18.1.2.2.1 | not-accessible | Each entry describes the characteristics of a PPPoE Subinterface. Creating/deleting entries in this table causes corresponding entries for be created /deleted in ifTable/ifXTable/juniIfTable. | |
| juniPPPoESubIfGroup | 1.3.6.1.4.1.4874.2.2.18.4.4.2 | Obsolete collection of objects providing management of PPPoE subinterfaces in a Juniper product. This statement became obsolete when new sub-interface objects were added. | ||
| juniPPPoESubIfGroup2 | 1.3.6.1.4.1.4874.2.2.18.4.4.5 | A collection of objects providing management of PPPoE subinterfaces in a Juniper product. | ||
| I32 juniPPPoESubIfId | 1.3.6.1.4.1.4874.2.2.18.1.2.2.1.4 | Integer32 | read-create | An integer identifier for the PPPoE subinterface, 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 PPPoE interface. 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 juniPPPoESubIfIndex | 1.3.6.1.4.1.4874.2.2.18.1.2.2.1.1 | InterfaceIndex | not-accessible | The ifIndex of the PPPoE Subinterface. When creating entries in this table, suitable values for this object are determined by reading juniPPPoESubNextIfIndex. |
| juniPPPoESubIfLayer | 1.3.6.1.4.1.4874.2.2.18.1.2 | |||
| NUM juniPPPoESubIfLowerIfIndex | 1.3.6.1.4.1.4874.2.2.18.1.2.2.1.3 | InterfaceIndexOrZero | read-create | The ifIndex of a PPPoE interface over which this PPPoE Subinterface 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 juniPPPoESubIfMotm | 1.3.6.1.4.1.4874.2.2.18.1.2.2.1.6 | DisplayString | read-create | 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. |
| JUN juniPPPoESubIfNextIfIndex | 1.3.6.1.4.1.4874.2.2.18.1.2.1 | JuniNextIfIndex | read-only | Coordinate ifIndex value allocation for entries in juniPPPoESubIfTable. 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. |
| ROW juniPPPoESubIfRowStatus | 1.3.6.1.4.1.4874.2.2.18.1.2.2.1.2 | RowStatus | read-create | Controls creation/deletion of entries in this table 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: juniPPPoESubIfRowStatus juniPPPoESubIfLowerIfIndex In addition, when creating an entry the following conditions must hold: A value for juniPPPoESubIfIndex must have been determined previously, by reading juniPPPoESubIfNextIfIndex. The interface identified by juniPPPoESubIfLowerIfIndex must exist, and must be a PPPoE interface. A positive value configured for juniPPPoESubIfId must not already be assigned to another subinterface layered onto the same underlying PPPoE interface. A corresponding entry in ifTable/ifXTable/juniIfTable is created or destroyed as a result of creating or destroying an entry in this table. |
| I32 juniPPPoESubIfSessionId | 1.3.6.1.4.1.4874.2.2.18.1.2.2.1.5 | Integer32 | read-only | The current sessionId associated with this sub-interface. |
| juniPPPoESubIfTable | 1.3.6.1.4.1.4874.2.2.18.1.2.2 | not-accessible | This table contains entries for PPPoE Subinterfaces present in the system. | |
| STR juniPPPoESubIfUrl | 1.3.6.1.4.1.4874.2.2.18.1.2.2.1.7 | DisplayString | read-create | 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. |
| juniPPPoESummary | 1.3.6.1.4.1.4874.2.2.18.1.5 | |||
| juniPPPoESummaryGroup | 1.3.6.1.4.1.4874.2.2.18.4.4.6 | A collection of objects providing collection of summary statistics on PPPoE interfaces. | ||
| I32 juniPPPoESummaryMajorIfAdminDown | 1.3.6.1.4.1.4874.2.2.18.1.5.3 | Integer32 | read-only | The total number of PPPoE major interfaces in the system that are administrateively configued to down(2). |
| I32 juniPPPoESummaryMajorIfAdminUp | 1.3.6.1.4.1.4874.2.2.18.1.5.2 | Integer32 | read-only | The total number of PPPoE major interfaces in the system that are administratively configured to up(1). |
| I32 juniPPPoESummaryMajorIfLowerLayerDown | 1.3.6.1.4.1.4874.2.2.18.1.5.6 | Integer32 | read-only | The total number of PPPoE major interfaces in the system with an operational state of lowerLayerDown(7). |
| I32 juniPPPoESummaryMajorIfNotPresent | 1.3.6.1.4.1.4874.2.2.18.1.5.7 | Integer32 | read-only | The total number of PPPoE major interfaces in the system with an operational state of notPresent(6). |
| I32 juniPPPoESummaryMajorIfOperDown | 1.3.6.1.4.1.4874.2.2.18.1.5.5 | Integer32 | read-only | The total number of PPPoE major interfaces in the system with an operational state of down(2). |
| I32 juniPPPoESummaryMajorIfOperUp | 1.3.6.1.4.1.4874.2.2.18.1.5.4 | Integer32 | read-only | The total number of PPPoE major interfaces in the system with an operational state of up(1). |
| I32 juniPPPoESummarySubIfAdminDown | 1.3.6.1.4.1.4874.2.2.18.1.5.10 | Integer32 | read-only | The total number of PPPoE subinterfaces in the system that are administrateively configued to down(2). |
| I32 juniPPPoESummarySubIfAdminUp | 1.3.6.1.4.1.4874.2.2.18.1.5.9 | Integer32 | read-only | The total number of PPPoE subinterfaces in the system that are administratively configured to up(1). |
| I32 juniPPPoESummarySubIfLowerLayerDown | 1.3.6.1.4.1.4874.2.2.18.1.5.13 | Integer32 | read-only | The total number of PPPoE subinterfaces in the system with an operational state of lowerLayerDown(7). |
| I32 juniPPPoESummarySubIfNotPresent | 1.3.6.1.4.1.4874.2.2.18.1.5.14 | Integer32 | read-only | The total number of PPPoE subinterfaces in the system with an operational state of notPresent(6). |
| I32 juniPPPoESummarySubIfOperDown | 1.3.6.1.4.1.4874.2.2.18.1.5.12 | Integer32 | read-only | The total number of PPPoE subinterfaces in the system with an operational state of down(2). |
| I32 juniPPPoESummarySubIfOperUp | 1.3.6.1.4.1.4874.2.2.18.1.5.11 | Integer32 | read-only | The total number of PPPoE subinterfaces in the system with an operational state of up(1). |
| I32 juniPPPoESummarySubInterfaceCount | 1.3.6.1.4.1.4874.2.2.18.1.5.8 | Integer32 | read-only | The total number of PPPoE subinterfaces configured in the system. |
RFC description
Juniper E-series PPPoE management MIB; defines objects for Point-to-Point Protocol over Ethernet interface creation, configuration, and performance monitoring.
Start monitoring Juniper E-series broadband edge router (PPPoE interfaces/subinterfaces) 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.