Juniper-PPPOE-MIB
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.
Main OID:
juniPPPoEMIB.1.3.6.1.4.1.4874.2.2.18
129
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
129 total| Object Name |
|---|
juniPPPoEMIBThe 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. MODULE-IDENTITY .1.3.6.1.4.1.4874.2.2.18 |
juniPPPoEObjects OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.18.1 |
juniPPPoEIfLayer OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.18.1.1 |
juniPPPoENextIfIndexCoordinate 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.ro JuniNextIfIndex (Juniper-TC) .1.3.6.1.4.1.4874.2.2.18.1.1.1 |
juniPPPoEIfTableThe parameters for the PPPoE service on this interface. SEQUENCE OF JuniPPPoEIfEntry .1.3.6.1.4.1.4874.2.2.18.1.1.2 |
juniPPPoEIfEntryThe 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. JuniPPPoEIfEntry .1.3.6.1.4.1.4874.2.2.18.1.1.2.1 |
juniPPPoEIfIfIndexThe ifIndex value of the corresponding ifEntry.ro InterfaceIndex (IF-MIB) .1.3.6.1.4.1.4874.2.2.18.1.1.2.1.1 |
juniPPPoEIfMaxNumSessionsThe number of sessions allowed on the PPPoE interface, zero indicates unlimited.rw INTEGER .1.3.6.1.4.1.4874.2.2.18.1.1.2.1.2 |
juniPPPoEIfRowStatusControls 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.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.4874.2.2.18.1.1.2.1.3 |
juniPPPoEIfLowerIfIndexThe 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.rw InterfaceIndexOrZero (IF-MIB) .1.3.6.1.4.1.4874.2.2.18.1.1.2.1.4 |
juniPPPoEIfAcNameThe name to use for the AC-NAME tag that is sent in any PADO that is sent on this interface.rw DisplayString .1.3.6.1.4.1.4874.2.2.18.1.1.2.1.5 |
juniPPPoEIfDupProtectFlag to allow duplicate MAC addresses.rw JuniEnable (Juniper-TC) .1.3.6.1.4.1.4874.2.2.18.1.1.2.1.6 |
juniPPPoEIfPADIFlagThis 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.rw JuniEnable (Juniper-TC) .1.3.6.1.4.1.4874.2.2.18.1.1.2.1.7 |
juniPPPoEIfAutoconfigThis flags determines whether the upper PPPoE interface is created dynamically or statically. When enable(1) the interface is created dynamically.rw JuniEnable (Juniper-TC) .1.3.6.1.4.1.4874.2.2.18.1.1.2.1.8 |
juniPPPoEIfServiceNameTableAssociate a PPPoE Service Name Table with this interface for PADI processing.rw Unsigned32 .1.3.6.1.4.1.4874.2.2.18.1.1.2.1.9 |
juniPPPoEIfPadrRemoteCircuitIdCaptureThis 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.rw JuniEnable (Juniper-TC) .1.3.6.1.4.1.4874.2.2.18.1.1.2.1.10 |
juniPPPoEIfMtuThe 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.rw Integer32 (1|2|66..65535) .1.3.6.1.4.1.4874.2.2.18.1.1.2.1.11 |
juniPPPoEIfLockoutMinThe 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.rw Integer32 .1.3.6.1.4.1.4874.2.2.18.1.1.2.1.12 |
juniPPPoEIfLockoutMaxThe 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.rw Integer32 .1.3.6.1.4.1.4874.2.2.18.1.1.2.1.13 |
juniPPPoEMaxSessionVsaConfigure 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 serverrw Enumeration .1.3.6.1.4.1.4874.2.2.18.1.1.2.1.14 |
juniPPPoEIfStatsTableThe statistics for the PPP over Ethernet Interface for the PPPoE service on this interface. SEQUENCE OF JuniPPPoEIfStatsEntry .1.3.6.1.4.1.4874.2.2.18.1.1.3 |
juniPPPoEIfStatsEntryThe statistics for a particular PPPoE Interface. JuniPPPoEIfStatsEntry .1.3.6.1.4.1.4874.2.2.18.1.1.3.1 |
juniPPPoEIfStatsRxPADINumber of PADI packets received.ro Counter32 .1.3.6.1.4.1.4874.2.2.18.1.1.3.1.1 |
juniPPPoEIfStatsTxPADONumber of PADO packets transmitted.ro Counter32 .1.3.6.1.4.1.4874.2.2.18.1.1.3.1.2 |
juniPPPoEIfStatsRxPADRNumber of PADR packets received.ro Counter32 .1.3.6.1.4.1.4874.2.2.18.1.1.3.1.3 |
juniPPPoEIfStatsTxPADSNumber of PADS packets transmitted.ro Counter32 .1.3.6.1.4.1.4874.2.2.18.1.1.3.1.4 |
juniPPPoEIfStatsRxPADTNumber of PADT packets received.ro Counter32 .1.3.6.1.4.1.4874.2.2.18.1.1.3.1.5 |
juniPPPoEIfStatsTxPADTNumber of PADT packets transmitted.ro Counter32 .1.3.6.1.4.1.4874.2.2.18.1.1.3.1.6 |
juniPPPoEIfStatsRxInvVersionNumber of packets received with invalid version.ro Counter32 .1.3.6.1.4.1.4874.2.2.18.1.1.3.1.7 |
juniPPPoEIfStatsRxInvCodeNumber of packets received with invalid code.ro Counter32 .1.3.6.1.4.1.4874.2.2.18.1.1.3.1.8 |
juniPPPoEIfStatsRxInvTagsNumber of packets received with invalid tags.ro Counter32 .1.3.6.1.4.1.4874.2.2.18.1.1.3.1.9 |
juniPPPoEIfStatsRxInvSessionNumber of packets received with invalid session identifiers. This object became obsolete when separate counters were added for PADI and PADR packets.roobsolete Counter32 .1.3.6.1.4.1.4874.2.2.18.1.1.3.1.10 |
juniPPPoEIfStatsRxInvTypesNumber of packets received with invalid types.ro Counter32 .1.3.6.1.4.1.4874.2.2.18.1.1.3.1.11 |
juniPPPoEIfStatsRxInvPacketsNumber of invalid packets received.ro Counter32 .1.3.6.1.4.1.4874.2.2.18.1.1.3.1.12 |
juniPPPoEIfStatsRxInsufficientResourcesNumber of session requests that could not be honored due to invalid resources.ro Counter32 .1.3.6.1.4.1.4874.2.2.18.1.1.3.1.13 |
juniPPPoEIfStatsTxPADMNumber of PADM packets transmitted.ro Counter32 .1.3.6.1.4.1.4874.2.2.18.1.1.3.1.14 |
juniPPPoEIfStatsTxPADNNumber of PADN packets transmitted.ro Counter32 .1.3.6.1.4.1.4874.2.2.18.1.1.3.1.15 |
juniPPPoEIfStatsRxInvTagLengthNumber of packets received with invalid tag length.ro Counter32 .1.3.6.1.4.1.4874.2.2.18.1.1.3.1.16 |
juniPPPoEIfStatsRxInvLengthNumber of packets received with invalid length.ro Counter32 .1.3.6.1.4.1.4874.2.2.18.1.1.3.1.17 |
juniPPPoEIfStatsRxInvPadISessionNumber of PADI packets received with invalid session identifiers.ro Counter32 .1.3.6.1.4.1.4874.2.2.18.1.1.3.1.18 |
juniPPPoEIfStatsRxInvPadRSessionNumber of PADR packets received with invalid session identifiers.ro Counter32 .1.3.6.1.4.1.4874.2.2.18.1.1.3.1.19 |
juniPPPoEIfLockoutTableThe lockout configuration and state of a PPPoE client on this interface. SEQUENCE OF JuniPPPoEIfLockoutEntry .1.3.6.1.4.1.4874.2.2.18.1.1.4 |
juniPPPoEIfLockoutEntryEach entry contains the configuration and state of a particular PPPoE interface client lockout. JuniPPPoEIfLockoutEntry .1.3.6.1.4.1.4874.2.2.18.1.1.4.1 |
juniPPPoEIfLockoutClientAddressThe source MAC address if the client. MacAddress (SNMPv2-TC) .1.3.6.1.4.1.4874.2.2.18.1.1.4.1.1 |
juniPPPoEIfLockoutTimeThe 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.ro Integer32 .1.3.6.1.4.1.4874.2.2.18.1.1.4.1.2 |
juniPPPoEIfLockoutElapsedTimeThe 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.ro Integer32 .1.3.6.1.4.1.4874.2.2.18.1.1.4.1.3 |
juniPPPoEIfLockoutNextTimeThe 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).ro Integer32 .1.3.6.1.4.1.4874.2.2.18.1.1.4.1.4 |
juniPPPoESubIfLayer OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.18.1.2 |
juniPPPoESubIfNextIfIndexCoordinate 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.ro JuniNextIfIndex (Juniper-TC) .1.3.6.1.4.1.4874.2.2.18.1.2.1 |
juniPPPoESubIfTableThis table contains entries for PPPoE Subinterfaces present in the system. SEQUENCE OF JuniPPPoESubIfEntry .1.3.6.1.4.1.4874.2.2.18.1.2.2 |
juniPPPoESubIfEntryEach 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. JuniPPPoESubIfEntry .1.3.6.1.4.1.4874.2.2.18.1.2.2.1 |
juniPPPoESubIfIndexThe ifIndex of the PPPoE Subinterface. When creating entries in this table, suitable values for this object are determined by reading juniPPPoESubNextIfIndex. InterfaceIndex (IF-MIB) .1.3.6.1.4.1.4874.2.2.18.1.2.2.1.1 |
juniPPPoESubIfRowStatusControls 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.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.4874.2.2.18.1.2.2.1.2 |
juniPPPoESubIfLowerIfIndexThe 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.rw InterfaceIndexOrZero (IF-MIB) .1.3.6.1.4.1.4874.2.2.18.1.2.2.1.3 |
juniPPPoESubIfIdAn 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.rw Integer32 (-1..2147483647) .1.3.6.1.4.1.4874.2.2.18.1.2.2.1.4 |
juniPPPoESubIfSessionIdThe current sessionId associated with this sub-interface.ro Integer32 .1.3.6.1.4.1.4874.2.2.18.1.2.2.1.5 |
juniPPPoESubIfMotmA 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.rw DisplayString .1.3.6.1.4.1.4874.2.2.18.1.2.2.1.6 |
juniPPPoESubIfUrlA 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.rw DisplayString .1.3.6.1.4.1.4874.2.2.18.1.2.2.1.7 |
juniPPPoEGlobal OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.18.1.3 |
juniPPPoEGlobalMotmA 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.rw DisplayString .1.3.6.1.4.1.4874.2.2.18.1.3.1 |
juniPPPoEProfile OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.18.1.4 |
juniPPPoEProfileTableThis table contains entries for the PPPoE portion of a profile entry.deprecated SEQUENCE OF JuniPPPoEProfileEntry .1.3.6.1.4.1.4874.2.2.18.1.4.1 |
juniPPPoEProfileEntryEach 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.deprecated JuniPPPoEProfileEntry .1.3.6.1.4.1.4874.2.2.18.1.4.1.1 |
juniPPPoEProfileIndexThis 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.deprecated Unsigned32 .1.3.6.1.4.1.4874.2.2.18.1.4.1.1.1 |
juniPPPoEProfileRowStatusControls 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.rwdeprecated RowStatus (SNMPv2-TC) .1.3.6.1.4.1.4874.2.2.18.1.4.1.1.2 |
juniPPPoEProfileMotmA 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.rwdeprecated DisplayString .1.3.6.1.4.1.4874.2.2.18.1.4.1.1.3 |
juniPPPoEProfileUrlA 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.rwdeprecated DisplayString .1.3.6.1.4.1.4874.2.2.18.1.4.1.1.4 |
juniPPPoESummary OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.18.1.5 |
juniPPPoEMajorInterfaceCountThe total number of PPPoE major interfaces configured and created in the system.ro Integer32 .1.3.6.1.4.1.4874.2.2.18.1.5.1 |
juniPPPoESummaryMajorIfAdminUpThe total number of PPPoE major interfaces in the system that are administratively configured to up(1).ro Integer32 .1.3.6.1.4.1.4874.2.2.18.1.5.2 |
juniPPPoESummaryMajorIfAdminDownThe total number of PPPoE major interfaces in the system that are administrateively configued to down(2).ro Integer32 .1.3.6.1.4.1.4874.2.2.18.1.5.3 |
juniPPPoESummaryMajorIfOperUpThe total number of PPPoE major interfaces in the system with an operational state of up(1).ro Integer32 .1.3.6.1.4.1.4874.2.2.18.1.5.4 |
juniPPPoESummaryMajorIfOperDownThe total number of PPPoE major interfaces in the system with an operational state of down(2).ro Integer32 .1.3.6.1.4.1.4874.2.2.18.1.5.5 |
juniPPPoESummaryMajorIfLowerLayerDownThe total number of PPPoE major interfaces in the system with an operational state of lowerLayerDown(7).ro Integer32 .1.3.6.1.4.1.4874.2.2.18.1.5.6 |
juniPPPoESummaryMajorIfNotPresentThe total number of PPPoE major interfaces in the system with an operational state of notPresent(6).ro Integer32 .1.3.6.1.4.1.4874.2.2.18.1.5.7 |
juniPPPoESummarySubInterfaceCountThe total number of PPPoE subinterfaces configured in the system.ro Integer32 .1.3.6.1.4.1.4874.2.2.18.1.5.8 |
juniPPPoESummarySubIfAdminUpThe total number of PPPoE subinterfaces in the system that are administratively configured to up(1).ro Integer32 .1.3.6.1.4.1.4874.2.2.18.1.5.9 |
juniPPPoESummarySubIfAdminDownThe total number of PPPoE subinterfaces in the system that are administrateively configued to down(2).ro Integer32 .1.3.6.1.4.1.4874.2.2.18.1.5.10 |
juniPPPoESummarySubIfOperUpThe total number of PPPoE subinterfaces in the system with an operational state of up(1).ro Integer32 .1.3.6.1.4.1.4874.2.2.18.1.5.11 |
juniPPPoESummarySubIfOperDownThe total number of PPPoE subinterfaces in the system with an operational state of down(2).ro Integer32 .1.3.6.1.4.1.4874.2.2.18.1.5.12 |
juniPPPoESummarySubIfLowerLayerDownThe total number of PPPoE subinterfaces in the system with an operational state of lowerLayerDown(7).ro Integer32 .1.3.6.1.4.1.4874.2.2.18.1.5.13 |
juniPPPoESummarySubIfNotPresentThe total number of PPPoE subinterfaces in the system with an operational state of notPresent(6).ro Integer32 .1.3.6.1.4.1.4874.2.2.18.1.5.14 |
juniPPPoEServices OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.18.1.6 |
juniPPPoEServiceNameTableNextIndexCoordinate 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.ro Unsigned32 .1.3.6.1.4.1.4874.2.2.18.1.6.1 |
juniPPPoEServiceNameTableTableThis table contains entries for the PPPoE Service-name tables. SEQUENCE OF JuniPPPoEServiceNameTableEntry .1.3.6.1.4.1.4874.2.2.18.1.6.2 |
juniPPPoEServiceNameTableEntryThe parameters for the PPPoE service-name table. JuniPPPoEServiceNameTableEntry .1.3.6.1.4.1.4874.2.2.18.1.6.2.1 |
juniPPPoEServiceNameTableIndexThe index value of the Service-name Table Entry. Unsigned32 .1.3.6.1.4.1.4874.2.2.18.1.6.2.1.1 |
juniPPPoEServiceNameTableNameService-name table name.rw DisplayString .1.3.6.1.4.1.4874.2.2.18.1.6.2.1.2 |
juniPPPoEServiceNameTableEmptyActionIdentifies the behavior when the empty (zero length) Service-name tag is received in a PADI frame.rw JuniPPPoEServiceNameAction .1.3.6.1.4.1.4874.2.2.18.1.6.2.1.3 |
juniPPPoEServiceNameTableRowStatusControls 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.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.4874.2.2.18.1.6.2.1.4 |
juniPPPoEServiceNameTableUnknownActionIdentifies the behavior when the unknown (unconfigured) Service-name tag is received in a PADI frame.rw JuniPPPoEServiceNameAction .1.3.6.1.4.1.4874.2.2.18.1.6.2.1.5 |
juniPPPoEServiceNameTableThis table contains entries for the PPPoE Service-names. SEQUENCE OF JuniPPPoEServiceNameEntry .1.3.6.1.4.1.4874.2.2.18.1.6.3 |
juniPPPoEServiceNameEntryThe parameters for the PPPoE service-name table entry. JuniPPPoEServiceNameEntry .1.3.6.1.4.1.4874.2.2.18.1.6.3.1 |
juniPPPoEServiceNameService-name tag value. DisplayString .1.3.6.1.4.1.4874.2.2.18.1.6.3.1.1 |
juniPPPoEServiceNameActionIdentifies the behavior when the Service-name tag is received in a PADI/PADR frame.rw JuniPPPoEServiceNameAction .1.3.6.1.4.1.4874.2.2.18.1.6.3.1.2 |
juniPPPoEServiceNameRowStatusControls 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.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.4874.2.2.18.1.6.3.1.3 |
juniPPPoEConformance OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.18.4 |
juniPPPoEGroups OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.18.4.4 |
juniPPPoEGroupObsolete collection of objects providing management of PPPoE interfaces in a Juniper product. This statement became obsolete when new objects were added.obsolete Unknown .1.3.6.1.4.1.4874.2.2.18.4.4.1 |
juniPPPoESubIfGroupObsolete collection of objects providing management of PPPoE subinterfaces in a Juniper product. This statement became obsolete when new sub-interface objects were added.obsolete Unknown .1.3.6.1.4.1.4874.2.2.18.4.4.2 |
juniPPPoEProfileGroupA 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.deprecated Unknown .1.3.6.1.4.1.4874.2.2.18.4.4.3 |
juniPPPoEGroup2Obsolete collection of objects providing management of PPPoE interfaces in a Juniper product. This statement became obsolete when new objects were added.obsolete Unknown .1.3.6.1.4.1.4874.2.2.18.4.4.4 |
juniPPPoESubIfGroup2A collection of objects providing management of PPPoE subinterfaces in a Juniper product. Unknown .1.3.6.1.4.1.4874.2.2.18.4.4.5 |
juniPPPoESummaryGroupA collection of objects providing collection of summary statistics on PPPoE interfaces. Unknown .1.3.6.1.4.1.4874.2.2.18.4.4.6 |
juniPPPoEGroup3Obsolete collection of objects providing management of PPPoE interfaces in a Juniper product. This group became obsolete when PADI flag support was added.obsolete Unknown .1.3.6.1.4.1.4874.2.2.18.4.4.7 |
juniPPPoEGroup4Obsolete collection of objects providing management of PPPoE interfaces in a Juniper product. This group became obsolete when PADN counter support was added.obsolete Unknown .1.3.6.1.4.1.4874.2.2.18.4.4.8 |
juniPPPoEGroup5Obsolete 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.obsolete Unknown .1.3.6.1.4.1.4874.2.2.18.4.4.9 |
juniPPPoEGroup6A collection of objects providing management of PPPoE interfaces in a Juniper product.obsolete Unknown .1.3.6.1.4.1.4874.2.2.18.4.4.10 |
juniPPPoEServiceNameTableGroupA collection of objects providing management of PPPoE service-name tables in a Juniper product. This group became obsolete when juniPPPoEServiceNameTableUnknownAction object is addedobsolete Unknown .1.3.6.1.4.1.4874.2.2.18.4.4.11 |
juniPPPoEGroup7A collection of objects providing management of PPPoE interfaces in a Juniper product.obsolete Unknown .1.3.6.1.4.1.4874.2.2.18.4.4.12 |
juniPPPoEGroup8A collection of objects providing management of PPPoE interfaces in a Juniper product. Unknown .1.3.6.1.4.1.4874.2.2.18.4.4.13 |
juniPPPoELockoutTableGroupA collection of objects providing management of PPPoE lockout tables in a Juniper product. Unknown .1.3.6.1.4.1.4874.2.2.18.4.4.14 |
juniPPPoEGroup9A collection of objects providing management of PPPoE interfaces in a Juniper product.obsolete Unknown .1.3.6.1.4.1.4874.2.2.18.4.4.15 |
juniPPPoEGroup10A collection of objects providing management of PPPoE interfaces in a Juniper product. Unknown .1.3.6.1.4.1.4874.2.2.18.4.4.16 |
juniPPPoEServiceNameTableGroup1A collection of objects providing management of PPPoE service-name tables in a Juniper product. Unknown .1.3.6.1.4.1.4874.2.2.18.4.4.17 |
juniPPPoECompliances OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.18.4.5 |
juniPPPoEComplianceObsolete compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when profile support and new sub-interface objects were added.obsolete Unknown .1.3.6.1.4.1.4874.2.2.18.4.5.1 |
juniPPPoECompliance2Obsolete compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when interface summary statistics objects were added.obsolete Unknown .1.3.6.1.4.1.4874.2.2.18.4.5.2 |
juniPPPoECompliance3Obsolete compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when the profile objects were deprecated.obsolete Unknown .1.3.6.1.4.1.4874.2.2.18.4.5.3 |
juniPPPoECompliance4Obsolete compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when new objects were added.obsolete Unknown .1.3.6.1.4.1.4874.2.2.18.4.5.4 |
juniPPPoECompliance5Obsolete compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when PADI flag support was added.obsolete Unknown .1.3.6.1.4.1.4874.2.2.18.4.5.5 |
juniPPPoECompliance6Obsolete compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when PADN counter support was added.obsolete Unknown .1.3.6.1.4.1.4874.2.2.18.4.5.6 |
juniPPPoECompliance7Obsolete 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.obsolete Unknown .1.3.6.1.4.1.4874.2.2.18.4.5.7 |
juniPPPoECompliance8Obsolete compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when support was added for remote circuit id capture.obsolete Unknown .1.3.6.1.4.1.4874.2.2.18.4.5.8 |
juniPPPoECompliance9Obsolete compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when support was added for MTU configuration.obsolete Unknown .1.3.6.1.4.1.4874.2.2.18.4.5.9 |
juniPPPoECompliance10Obsolete compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when support was added for lockout configuration.obsolete Unknown .1.3.6.1.4.1.4874.2.2.18.4.5.10 |
juniPPPoECompliance11Obsolete compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when support was added for juniPPPoEMaxSessionVsa.obsolete Unknown .1.3.6.1.4.1.4874.2.2.18.4.5.11 |
juniPPPoECompliance12The compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when support was added for juniPPPoEServiceNameTableUnknownActionobsolete Unknown .1.3.6.1.4.1.4874.2.2.18.4.5.12 |
juniPPPoECompliance13The compliance statement for entities which implement the Juniper PPPoE MIB. Unknown .1.3.6.1.4.1.4874.2.2.18.4.5.13 |