JNX-PPPOE-MIB
Updated Feb 16, 2016The 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.
Main OID:
jnxPPPoEMIB.1.3.6.1.4.1.2636.3.67.1
109
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
109 total| Object Name |
|---|
jnxPPPoEMIBThe 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. MODULE-IDENTITY .1.3.6.1.4.1.2636.3.67.1 |
jnxPPPoEObjects OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.67.1.1 |
jnxPPPoEIfLayer OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.67.1.1.1 |
jnxPPPoENextIfIndexCoordinate 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.ro InterfaceIndexOrZero (IF-MIB) .1.3.6.1.4.1.2636.3.67.1.1.1.1 |
jnxPPPoEIfTableThe parameters for the PPPoEservice on this interface. SEQUENCE OF JnxPPPoEIfEntry .1.3.6.1.4.1.2636.3.67.1.1.1.2 |
jnxPPPoEIfEntryThe Parameters for a particular PPPoEinterface.
Creating/deleting entries in this table causes corresponding entries for
be created/deleted in ifTable/ifXTable/jnxIfTable, and
jnxPPPoEIfStatsTable. JnxPPPoEIfEntry .1.3.6.1.4.1.2636.3.67.1.1.1.2.1 |
jnxPPPoEIfIfIndexThe ifIndex value of the corresponding ifEntry. InterfaceIndex (IF-MIB) .1.3.6.1.4.1.2636.3.67.1.1.1.2.1.1 |
jnxPPPoEIfMaxNumSessionsThe number of sessions allowed on the PPPoEinterface, zero indicates
unlimited.ro INTEGER .1.3.6.1.4.1.2636.3.67.1.1.1.2.1.2 |
jnxPPPoEIfRowStatusControls 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)ro RowStatus (SNMPv2-TC) .1.3.6.1.4.1.2636.3.67.1.1.1.2.1.3 |
jnxPPPoEIfLowerIfIndexThe 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.ro InterfaceIndexOrZero (IF-MIB) .1.3.6.1.4.1.2636.3.67.1.1.1.2.1.4 |
jnxPPPoEIfAcNameThe name to use for the AC-NAME tag that is sent in any PADO that is
sent on this interface.ro DisplayString .1.3.6.1.4.1.2636.3.67.1.1.1.2.1.5 |
jnxPPPoEIfDupProtectFlag to allow duplicate MAC addresses.ro Enumeration .1.3.6.1.4.1.2636.3.67.1.1.1.2.1.6 |
jnxPPPoEIfPADIFlagThis 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.ro Enumeration .1.3.6.1.4.1.2636.3.67.1.1.1.2.1.7 |
jnxPPPoEIfAutoconfigThis flags determines whether the upper PPPoEinterface is created
dynamically or statically. When enable(1) the interface is created
dynamically.ro Enumeration .1.3.6.1.4.1.2636.3.67.1.1.1.2.1.8 |
jnxPPPoEIfServiceNameTableAssociate a PPPoEService Name Table with this interface for PADI
processing.ro DisplayString .1.3.6.1.4.1.2636.3.67.1.1.1.2.1.9 |
jnxPPPoEIfPadrRemoteCircuitIdCaptureThis 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.ro Enumeration .1.3.6.1.4.1.2636.3.67.1.1.1.2.1.10 |
jnxPPPoEIfMtuThe 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.ro Integer32 (1|2|66..65535) .1.3.6.1.4.1.2636.3.67.1.1.1.2.1.11 |
jnxPPPoEIfLockoutMinThe 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.ro Integer32 .1.3.6.1.4.1.2636.3.67.1.1.1.2.1.12 |
jnxPPPoEIfLockoutMaxThe 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.ro Integer32 .1.3.6.1.4.1.2636.3.67.1.1.1.2.1.13 |
jnxPPPoEIfDynamicProfileAttach dynamic-profile to this interfacero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.2636.3.67.1.1.1.2.1.14 |
jnxPPPoEIfStatsTableThe statistics for the PPP over Ethernet Interface for the PPPoE
service on this interface. SEQUENCE OF JnxPPPoEIfStatsEntry .1.3.6.1.4.1.2636.3.67.1.1.1.3 |
jnxPPPoEIfStatsEntryThe statistics for a particular PPPoEInterface. JnxPPPoEIfStatsEntry .1.3.6.1.4.1.2636.3.67.1.1.1.3.1 |
jnxPPPoEIfStatsRxPADINumber of PADI packets received.ro Counter32 .1.3.6.1.4.1.2636.3.67.1.1.1.3.1.1 |
jnxPPPoEIfStatsTxPADONumber of PADO packets transmitted.ro Counter32 .1.3.6.1.4.1.2636.3.67.1.1.1.3.1.2 |
jnxPPPoEIfStatsRxPADRNumber of PADR packets received.ro Counter32 .1.3.6.1.4.1.2636.3.67.1.1.1.3.1.3 |
jnxPPPoEIfStatsTxPADSNumber of PADS packets transmitted.ro Counter32 .1.3.6.1.4.1.2636.3.67.1.1.1.3.1.4 |
jnxPPPoEIfStatsRxPADTNumber of PADT packets received.ro Counter32 .1.3.6.1.4.1.2636.3.67.1.1.1.3.1.5 |
jnxPPPoEIfStatsTxPADTNumber of PADT packets transmitted.ro Counter32 .1.3.6.1.4.1.2636.3.67.1.1.1.3.1.6 |
jnxPPPoEIfStatsRxInvVersionNumber of packets received with invalid version.ro Counter32 .1.3.6.1.4.1.2636.3.67.1.1.1.3.1.7 |
jnxPPPoEIfStatsRxInvCodeNumber of packets received with invalid code.ro Counter32 .1.3.6.1.4.1.2636.3.67.1.1.1.3.1.8 |
jnxPPPoEIfStatsRxInvTagsNumber of packets received with invalid tags.ro Counter32 .1.3.6.1.4.1.2636.3.67.1.1.1.3.1.9 |
jnxPPPoEIfStatsRxInvSessionNumber 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.2636.3.67.1.1.1.3.1.10 |
jnxPPPoEIfStatsRxInvTypesNumber of packets received with invalid types.ro Counter32 .1.3.6.1.4.1.2636.3.67.1.1.1.3.1.11 |
jnxPPPoEIfStatsRxInvPacketsNumber of invalid packets received.ro Counter32 .1.3.6.1.4.1.2636.3.67.1.1.1.3.1.12 |
jnxPPPoEIfStatsRxInsufficientResourcesNumber of session requests that could not be honored due to invalid
resources.ro Counter32 .1.3.6.1.4.1.2636.3.67.1.1.1.3.1.13 |
jnxPPPoEIfStatsTxPADMNumber of PADM packets transmitted.ro Counter32 .1.3.6.1.4.1.2636.3.67.1.1.1.3.1.14 |
jnxPPPoEIfStatsTxPADNNumber of PADN packets transmitted.ro Counter32 .1.3.6.1.4.1.2636.3.67.1.1.1.3.1.15 |
jnxPPPoEIfStatsRxInvTagLengthNumber of packets received with invalid tag length.ro Counter32 .1.3.6.1.4.1.2636.3.67.1.1.1.3.1.16 |
jnxPPPoEIfStatsRxInvLengthNumber of packets received with invalid length.ro Counter32 .1.3.6.1.4.1.2636.3.67.1.1.1.3.1.17 |
jnxPPPoEIfStatsRxInvPadISessionNumber of PADI packets received with invalid session identifiers.ro Counter32 .1.3.6.1.4.1.2636.3.67.1.1.1.3.1.18 |
jnxPPPoEIfStatsRxInvPadRSessionNumber of PADR packets received with invalid session identifiers.ro Counter32 .1.3.6.1.4.1.2636.3.67.1.1.1.3.1.19 |
jnxPPPoEIfLockoutTableThe lockout configuration and state of a PPPoEclient on this interface. SEQUENCE OF JnxPPPoEIfLockoutEntry .1.3.6.1.4.1.2636.3.67.1.1.1.4 |
jnxPPPoEIfLockoutEntryEach entry contains the configuration and state of a particular
PPPoEinterface client lockout. JnxPPPoEIfLockoutEntry .1.3.6.1.4.1.2636.3.67.1.1.1.4.1 |
jnxPPPoEIfLockoutClientAddressThe source MAC address if the client. MacAddress (SNMPv2-TC) .1.3.6.1.4.1.2636.3.67.1.1.1.4.1.1 |
jnxPPPoEIfLockoutTimeThe 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.ro Integer32 .1.3.6.1.4.1.2636.3.67.1.1.1.4.1.2 |
jnxPPPoEIfLockoutElapsedTimeThe 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.ro Integer32 .1.3.6.1.4.1.2636.3.67.1.1.1.4.1.3 |
jnxPPPoEIfLockoutNextTimeThe 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).ro Integer32 .1.3.6.1.4.1.2636.3.67.1.1.1.4.1.4 |
jnxPPPoESubIfLayer OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.67.1.1.2 |
jnxPPPoESubIfNextIfIndexCoordinate 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.ro InterfaceIndexOrZero (IF-MIB) .1.3.6.1.4.1.2636.3.67.1.1.2.1 |
jnxPPPoESubIfTableThis table contains entries for PPPoESubinterfaces present in the
system. SEQUENCE OF JnxPPPoESubIfEntry .1.3.6.1.4.1.2636.3.67.1.1.2.2 |
jnxPPPoESubIfEntryEach 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. JnxPPPoESubIfEntry .1.3.6.1.4.1.2636.3.67.1.1.2.2.1 |
jnxPPPoESubIfIndexThe ifIndex of the PPPoESubinterface. When creating entries in this
table, suitable values for this object are determined by reading
jnxPPPoESubNextIfIndex. InterfaceIndex (IF-MIB) .1.3.6.1.4.1.2636.3.67.1.1.2.2.1.1 |
jnxPPPoESubIfRowStatusControls 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)ro RowStatus (SNMPv2-TC) .1.3.6.1.4.1.2636.3.67.1.1.2.2.1.2 |
jnxPPPoESubIfLowerIfIndexThe 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.ro InterfaceIndexOrZero (IF-MIB) .1.3.6.1.4.1.2636.3.67.1.1.2.2.1.3 |
jnxPPPoESubIfIdAn 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.ro Unsigned32 .1.3.6.1.4.1.2636.3.67.1.1.2.2.1.4 |
jnxPPPoESubIfSessionIdThe current sessionId associated with this sub-interface.ro Integer32 .1.3.6.1.4.1.2636.3.67.1.1.2.2.1.5 |
jnxPPPoESubIfMotmA 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.ro DisplayString .1.3.6.1.4.1.2636.3.67.1.1.2.2.1.6 |
jnxPPPoESubIfUrlA 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.ro DisplayString .1.3.6.1.4.1.2636.3.67.1.1.2.2.1.7 |
jnxPPPoESubIfSubscriberIdHiWordThe subscriber handle associated with this PPPoEsubinterface which can
be used to index into the JUNIPER-SUBSCRIBER-MIB table entries.
This object is equal to the most significant 32 bit of the 64 bit subscriber id.ro Unsigned32 .1.3.6.1.4.1.2636.3.67.1.1.2.2.1.8 |
jnxPPPoESubIfSubscriberIdLoWordThe subscriber handle associated with this PPPoEsubinterface which can
be used to index into the JUNIPER-SUBSCRIBER-MIB table entries.
This object is equal to the least significant 32 bit of the 64 bit subscriber id.ro Unsigned32 .1.3.6.1.4.1.2636.3.67.1.1.2.2.1.9 |
jnxPppoeSubIfQueueStatsTableTable containing the Queue parameters for the PPPoEsessions. SEQUENCE OF JnxPppoeSubIfPerQueueStatsEntry .1.3.6.1.4.1.2636.3.67.1.1.2.3 |
jnxPppoeSubIfPerQueueStatsEntryThe 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 JnxPppoeSubIfPerQueueStatsEntry .1.3.6.1.4.1.2636.3.67.1.1.2.3.1 |
jnxPppoeSubIfQueueIndexThis 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. INTEGER .1.3.6.1.4.1.2636.3.67.1.1.2.3.1.1 |
jnxPppoeSubIfQueueStatsPacketSentThis attribute returns the counts of number of packet sent
per PPPoEsession and per queue.ro Counter64 .1.3.6.1.4.1.2636.3.67.1.1.2.3.1.2 |
jnxPppoeSubIfQueueStatsBytesSentThis attribute returns the counts of number of bytes sent
per PPPoEsession and per queue.ro Counter64 .1.3.6.1.4.1.2636.3.67.1.1.2.3.1.3 |
jnxPppoeSubIfQueueStatsPacketDroppedThis attribute returns the number of packet dropped per
PPPoEsession and per queue.ro Counter64 .1.3.6.1.4.1.2636.3.67.1.1.2.3.1.4 |
jnxPppoeSubIfQueueStatsBytesDroppedThis attribute returns the number of bytes dropped per
PPPoEsession and per queue.ro Counter64 .1.3.6.1.4.1.2636.3.67.1.1.2.3.1.5 |
jnxPppoeSubIfQueueStatsActualBitRateThis attribute returns the actual bit rate for per
PPPoEsession and per queue.ro Counter32 .1.3.6.1.4.1.2636.3.67.1.1.2.3.1.6 |
jnxPppoeSubIfQueueStatsActualDroppedBitRateThis attribute returns the actual dropped bit rate for per
PPPoEsession and per queue.ro Counter32 .1.3.6.1.4.1.2636.3.67.1.1.2.3.1.7 |
jnxPPPoESummary OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.67.1.1.3 |
jnxPPPoEMajorInterfaceCountThe total number of PPPoEmajor interfaces configured and created in
the system.ro Integer32 .1.3.6.1.4.1.2636.3.67.1.1.3.1 |
jnxPPPoESummaryMajorIfAdminUpThe total number of PPPoEmajor interfaces in the system that are
administratively configured to up(1).ro Integer32 .1.3.6.1.4.1.2636.3.67.1.1.3.2 |
jnxPPPoESummaryMajorIfAdminDownThe total number of PPPoEmajor interfaces in the system that are
administrateively configued to down(2).ro Integer32 .1.3.6.1.4.1.2636.3.67.1.1.3.3 |
jnxPPPoESummaryMajorIfOperUpThe total number of PPPoEmajor interfaces in the system with an
operational state of up(1).ro Integer32 .1.3.6.1.4.1.2636.3.67.1.1.3.4 |
jnxPPPoESummaryMajorIfOperDownThe total number of PPPoEmajor interfaces in the system with an
operational state of down(2).ro Integer32 .1.3.6.1.4.1.2636.3.67.1.1.3.5 |
jnxPPPoESummaryMajorIfLowerLayerDownThe total number of PPPoEmajor interfaces in the system with an
operational state of lowerLayerDown(7).ro Integer32 .1.3.6.1.4.1.2636.3.67.1.1.3.6 |
jnxPPPoESummaryMajorIfNotPresentThe total number of PPPoEmajor interfaces in the system with an
operational state of notPresent(6).ro Integer32 .1.3.6.1.4.1.2636.3.67.1.1.3.7 |
jnxPPPoESummarySubInterfaceCountThe total number of PPPoEsubinterfaces configured in the system.ro Integer32 .1.3.6.1.4.1.2636.3.67.1.1.3.8 |
jnxPPPoESummarySubIfAdminUpThe total number of PPPoEsubinterfaces in the system that are
administratively configured to up(1).ro Integer32 .1.3.6.1.4.1.2636.3.67.1.1.3.9 |
jnxPPPoESummarySubIfAdminDownThe total number of PPPoEsubinterfaces in the system that are
administrateively configued to down(2).ro Integer32 .1.3.6.1.4.1.2636.3.67.1.1.3.10 |
jnxPPPoESummarySubIfOperUpThe total number of PPPoEsubinterfaces in the system with an
operational state of up(1).ro Integer32 .1.3.6.1.4.1.2636.3.67.1.1.3.11 |
jnxPPPoESummarySubIfOperDownThe total number of PPPoEsubinterfaces in the system with an
operational state of down(2).ro Integer32 .1.3.6.1.4.1.2636.3.67.1.1.3.12 |
jnxPPPoESummarySubIfLowerLayerDownThe total number of PPPoEsubinterfaces in the system with an
operational state of lowerLayerDown(7).ro Integer32 .1.3.6.1.4.1.2636.3.67.1.1.3.13 |
jnxPPPoESummarySubIfNotPresentThe total number of PPPoEsubinterfaces in the system with an
operational state of notPresent(6).ro Integer32 .1.3.6.1.4.1.2636.3.67.1.1.3.14 |
jnxPPPoEServices OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.67.1.1.4 |
jnxPPPoEServiceNameTableTableThis table contains entries for the PPPoEService-name tables. SEQUENCE OF JnxPPPoEServiceNameTableEntry .1.3.6.1.4.1.2636.3.67.1.1.4.1 |
jnxPPPoEServiceNameTableEntryThe parameters for the PPPoEservice-name table. JnxPPPoEServiceNameTableEntry .1.3.6.1.4.1.2636.3.67.1.1.4.1.1 |
jnxPPPoEServiceNameTableNameService-name table name. DisplayString .1.3.6.1.4.1.2636.3.67.1.1.4.1.1.1 |
jnxPPPoEServiceNameTableRowStatusControls 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 <Empty >Service and <Any>
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)ro RowStatus (SNMPv2-TC) .1.3.6.1.4.1.2636.3.67.1.1.4.1.1.2 |
jnxPPPoEServiceNameTableThis table contains entries for the PPPoEService-names. SEQUENCE OF JnxPPPoEServiceNameEntry .1.3.6.1.4.1.2636.3.67.1.1.4.2 |
jnxPPPoEServiceNameEntryThe parameters for the PPPoEservice-name table entry. JnxPPPoEServiceNameEntry .1.3.6.1.4.1.2636.3.67.1.1.4.2.1 |
jnxPPPoEServiceNameService-name tag value. DisplayString .1.3.6.1.4.1.2636.3.67.1.1.4.2.1.1 |
jnxPPPoEServiceNameActionIdentifies the behavior when the the Service-name tag is received in a
PADI frame.ro JnxPPPoEServiceNameAction .1.3.6.1.4.1.2636.3.67.1.1.4.2.1.2 |
jnxPPPoEServiceNameDynamicProfileDynamic Profile associated with a Service-name.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.2636.3.67.1.1.4.2.1.3 |
jnxPPPoEServiceNameRoutingInstanceRouting Instance associated with a Service-name.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.2636.3.67.1.1.4.2.1.4 |
jnxPPPoEServiceNameMaxSessionsThe Max Sessions value used to cap the number of active PPPoEssessions
that may be established with the specified Service entry.ro Unsigned32 .1.3.6.1.4.1.2636.3.67.1.1.4.2.1.5 |
jnxPPPoEServiceNameRowStatusControls 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)ro RowStatus (SNMPv2-TC) .1.3.6.1.4.1.2636.3.67.1.1.4.2.1.6 |
jnxPPPoEServiceNameAciAriTableThis table contains entries for the PPPoEServicename AciAri entries. SEQUENCE OF JnxPPPoEServiceNameAciAriEntry .1.3.6.1.4.1.2636.3.67.1.1.4.3 |
jnxPPPoEServiceNameAciAriEntryThe parameters for the PPPoEservice-name AciAri table entry. JnxPPPoEServiceNameAciAriEntry .1.3.6.1.4.1.2636.3.67.1.1.4.3.1 |
jnxPPPoEServiceNameAgentCircuitIdACI tag values that the PPPoEclient would send in the PADI/PADR
control packet. DisplayString .1.3.6.1.4.1.2636.3.67.1.1.4.3.1.1 |
jnxPPPoEServiceNameAgentRemoteIdACI tag values that the PPPoEclient would send in the PADI/PADR
control packet. DisplayString .1.3.6.1.4.1.2636.3.67.1.1.4.3.1.2 |
jnxPPPoEServiceNameAciAriActionIdentifies the behavior when the the Service-name with ACI/ARI pairs
is received in a PADI frame.ro JnxPPPoEServiceNameAction .1.3.6.1.4.1.2636.3.67.1.1.4.3.1.3 |
jnxPPPoEServiceNameAciAriDynamicProfileDynamic Profile associated with a Service-name and ACI/ARI pairsro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.2636.3.67.1.1.4.3.1.4 |
jnxPPPoEServiceNameAciAriRoutingInstanceRouting-Instance associated with a Service-name and ACI/ARI pairsro DisplayString .1.3.6.1.4.1.2636.3.67.1.1.4.3.1.5 |
jnxPPPoEServiceNameAciAriStaticInterfaceStatic Interface associated with each ACI/ARI Entry.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.2636.3.67.1.1.4.3.1.6 |
jnxPPPoEServiceNameAciAriRowStatusControls 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)ro RowStatus (SNMPv2-TC) .1.3.6.1.4.1.2636.3.67.1.1.4.3.1.7 |
jnxPPPoEConformance OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.67.1.4 |
jnxPPPoECompliances OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.67.1.4.1 |
jnxPPPoEGroups OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.67.1.4.2 |