JNX-PPPOE-MIB: View SNMP OID List / Download MIB

The Point-to-Point Protocol over Ethernet (PPPoE) MIB for the Junos product family. This MIB contains managed objects for each of two interface layers: PPPoE interfaces, and PPPoE subinterfaces. For each of these layers, management objects are provided to query for an available interface index, and to create/delete interfaces of that type.

Coordinate ifIndex value allocation for entries in jnxPPPoEIfTable. A GET of this object returns the next available ifIndex value to be used to create an entry in the associated interface table; or zero, if no valid ifIndex value is available. This object also returns a value of zero when it is the lexicographic successor of a varbind presented in an SNMP GETNEXT or GETBULK request, for which circumstance it is assumed that ifIndex allocation is unintended. Successive GETs will typically return different values, thus avoiding collisions among cooperating management clients seeking to create table entries simultaneously.

The parameters for the PPPoEservice on this interface.

The Parameters for a particular PPPoEinterface. Creating/deleting entries in this table causes corresponding entries for be created/deleted in ifTable/ifXTable/jnxIfTable, and jnxPPPoEIfStatsTable.

The ifIndex value of the corresponding ifEntry.

The number of sessions allowed on the PPPoEinterface, zero indicates unlimited.

Controls creation/deletion of entries in this table with READ-CREATE maximum access, according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create an entry in this table, the following entry objects MUST be explicitly configured: jnxPPPoEIfRowStatus jnxPPPoEIfLowerIfIndex In addition, when creating an entry the following conditions must hold: A value for jnxPPPoEIfIndex must have been determined previously, by reading jnxPPPoENextIfIndex. The interface identified by jnxPPPoEIfLowerIfIndex must exist, and must be an interface type that permits layering of PPPoEabove it. A corresponding entry in ifTable/ifXTable/jnxIfTable is created or destroyed as a result of creating or destroying an entry in this table. The following values can be read from this object: active(1)

The ifIndex of an interface over which this PPPoEinterface is to be layered. A value of zero indicates no layering. An implementation may choose to require that a nonzero value be configured at entry creation.

The name to use for the AC-NAME tag that is sent in any PADO that is sent on this interface.

Flag to allow duplicate MAC addresses. Enumeration: 'enable': 1, 'disable': 2.

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. Enumeration: 'enable': 1, 'disable': 2.

This flags determines whether the upper PPPoEinterface is created dynamically or statically. When enable(1) the interface is created dynamically. Enumeration: 'enable': 1, 'disable': 2.

Associate a PPPoEService Name Table with this interface for PADI processing.

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. Enumeration: 'enable': 1, 'disable': 2.

The initial Maximum Transmit Unit (MTU) that the PPPoEmajor interface entity will advertise to the remote entity. If the value of this variable is 1 then the local PPPoEentity will use an MTU value determined by its underlying media interface. If the value of this variable is 2 then the local PPPoEentity will use a value determined by the PPPoEMax-Mtu-Tag transmitted from the client in the PADR packet. If no Max-Mtu-Tag is received, the value defaults to a maximum of 1494. The operational MTU is limited by the MTU of the underlying media interface minus the PPPoEframe overhead.

The lower bound, in seconds, of the time range used to specify the duration of the lockout of the client from recognition for the specified interface. This only takes effect if jnxPPPoEIfAutoconfig is set for this interface. The ability to lockout the client in the event of an error in creating a PPP interface is enabled by default. The initial lockout duration is this object's value and increases exponentially for each failure that occurs for the client creating a PPP interface for the PPPoEinterface within the greater of 15 minutes and jnxPPPoEIfLockoutMax. The lockout duration for the client will not exceed jnxPPPoEIfLockoutMax. If the time between creation errors for the PPP interface for this interface is greater than the greater of 15 minutes and jnxPPPoEIfLockoutMax, then the lockout duration reverts to this object's value. To disable the ability to lockout the client from recognition in the event of an error in creating a PPP interface for the specified interface, the value of this object and jnxPPPoEIfLockoutMin must be set to 0. It is not recommended that this lockout feature be disabled except for debugging purposes or when this interface supports more than one session.

The upper bound, in seconds, of the time range used to specify the duration of the lockout of the client from recognition for the specified interface. This only takes effect if jnxPPPoEIfAutoconfig is set for this interface. The ability to lockout the client from recognition in the event of an error in creating a PPP interface is enabled by default. The initial lockout duration is jnxPPPoEIfLockoutMin and increases exponentially for each failure that occurs for the client interface within the greater of 15 minutes and this object's value. The lockout duration for the client will not exceed jnxPPPoEIfLockoutMax. If the time between creation errors for the PPP interface for this interface is greater than the greater of 15 minutes and jnxPPPoEIfLockoutMax, then the lockout duration reverts to jnxPPPoEIfLockoutMin. To disable the ability to lockout the client from recognition in the event of an error in creating a PPP interface for the specified interface, the value of this object and jnxPPPoEIfLockoutMin must be set to 0. It is not recommended that this lockout feature be disabled except for debugging purposes or when this interface supports more than one session.

Attach dynamic-profile to this interface

The statistics for the PPP over Ethernet Interface for the PPPoE service on this interface.

The statistics for a particular PPPoEInterface.

Number of PADI packets received.

Number of PADO packets transmitted.

Number of PADR packets received.

Number of PADS packets transmitted.

Number of PADT packets received.

Number of PADT packets transmitted.

Number of packets received with invalid version.

Number of packets received with invalid code.

Number of packets received with invalid tags.

Number of packets received with invalid session identifiers. This object became obsolete when separate counters were added for PADI and PADR packets.

Number of packets received with invalid types.

Number of invalid packets received.

Number of session requests that could not be honored due to invalid resources.

Number of PADM packets transmitted.

Number of PADN packets transmitted.

Number of packets received with invalid tag length.

Number of packets received with invalid length.

Number of PADI packets received with invalid session identifiers.

Number of PADR packets received with invalid session identifiers.

The lockout configuration and state of a PPPoEclient on this interface.

Each entry contains the configuration and state of a particular PPPoEinterface client lockout.

The source MAC address if the client.

The time duration, in seconds, currently used to lockout the specified encapsulation type from recognition for the specified interface. The reported value is within the range specified by jnxPPPoEIfLockoutMin and jnxPPPoEIfLockoutMax. A value of 0 indicates that no lockout is occurring for the encapsulation type for the specified interface.

The elapsed time, in seconds, that the specified encapsulation type has been locked-out from recognition for the specified interface. Its value will not exceed that of jnxPPPoEIfLockoutTime. A value of 0 indicates that no lockout is occurring for the encapsulation type for the specified interface.

The time duration, in seconds, that will be used to lockout the specified encapsulation type from recognition for the specified interface for the next event that results in a lockout condition. The reported value is within the range specified by jnxPPPoEIfLockoutMin and jnxPPPoEIfLockoutMax. When jnxPPPoEIfEnable is set to enable, a value of 0 indicates that lockout is prevented from occurring for the encapsulation type for the specified interface (i.e., jnxPPPoEIfLockoutMin and jnxPPPoEIfLockoutMax are both set to 0).

Coordinate ifIndex value allocation for entries in jnxPPPoESubIfTable. A GET of this object returns the next available ifIndex value to be used to create an entry in the associated interface table; or zero, if no valid ifIndex value is available. This object also returns a value of zero when it is the lexicographic successor of a varbind presented in an SNMP GETNEXT or GETBULK request, for which circumstance it is assumed that ifIndex allocation is unintended. Successive GETs will typically return different values, thus avoiding collisions among cooperating management clients seeking to create table entries simultaneously.

This table contains entries for PPPoESubinterfaces present in the system.

Each entry describes the characteristics of a PPPoESubinterface. With READ-CREATE maximum access ,creating/deleting entries in this table causes corresponding entries for be created /deleted in ifTable/ifXTable/jnxIfTable.

The ifIndex of the PPPoESubinterface. When creating entries in this table, suitable values for this object are determined by reading jnxPPPoESubNextIfIndex.

Controls creation/deletion of entries in this table with READ-CREATE maximum access ,according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create an entry in this table, the following entry objects MUST be explicitly configured: jnxPPPoESubIfRowStatus jnxPPPoESubIfLowerIfIndex In addition, when creating an entry the following conditions must hold: A value for jnxPPPoESubIfIndex must have been determined previously, by reading jnxPPPoESubIfNextIfIndex. The interface identified by jnxPPPoESubIfLowerIfIndex must exist, and must be a PPPoEinterface. A positive value configured for jnxPPPoESubIfId must not already be assigned to another subinterface layered onto the same underlying PPPoEinterface. A corresponding entry in ifTable/ifXTable/jnxIfTable is created or destroyed as a result of creating or destroying an entry in this table. The following values can be read from this object: active(1)

The ifIndex of a PPPoEinterface over which this PPPoESubinterface is to be layered. A value of zero indicates no layering. An implementation may choose to require that a nonzero value be configured at entry creation.

An integer identifier for the PPPoEsubinterface, used in conjunction with the command-line interface. It is provided here for cross-reference purposes only. The value must be unique among subinterfaces configured on the same underlying PPPoEinterface. If this object is not configured, or is configured with a value of -1, a nonzero value will be allocated internally and can be retrieved from this object after table entry creation has succeeded. A value of zero for this object is reserved for future use.

The current sessionId associated with this sub-interface.

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.

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.

Table containing the Queue parameters for the PPPoEsessions.

The statistics for a particular trrafic class queue for PPPoEsub Interface(i.e. session). ). Forwarding class to queue number mapping is not always one-to-one. Forwarding classes and queues are the same only when default forwarding-class-to-queue mapping is in effect

This attribute returns the queue index ranging from 0 to 7 of the queue configure on the PPPoEsubinterface to support the traffic class for PPPoEsession configured on that subinterface. Forwarding class to queue number mapping is not always one-to-one. Forwarding classes and queues are the same only when default forwarding-class-to-queue mapping is in effect.

This attribute returns the counts of number of packet sent per PPPoEsession and per queue.

This attribute returns the counts of number of bytes sent per PPPoEsession and per queue.

This attribute returns the number of packet dropped per PPPoEsession and per queue.

This attribute returns the number of bytes dropped per PPPoEsession and per queue.

This attribute returns the actual bit rate for per PPPoEsession and per queue.

This attribute returns the actual dropped bit rate for per PPPoEsession and per queue.

The total number of PPPoEmajor interfaces configured and created in the system.

The total number of PPPoEmajor interfaces in the system that are administratively configured to up(1).

The total number of PPPoEmajor interfaces in the system that are administrateively configued to down(2).

The total number of PPPoEmajor interfaces in the system with an operational state of up(1).

The total number of PPPoEmajor interfaces in the system with an operational state of down(2).

The total number of PPPoEmajor interfaces in the system with an operational state of lowerLayerDown(7).

The total number of PPPoEmajor interfaces in the system with an operational state of notPresent(6).

The total number of PPPoEsubinterfaces configured in the system.

The total number of PPPoEsubinterfaces in the system that are administratively configured to up(1).

The total number of PPPoEsubinterfaces in the system that are administrateively configued to down(2).

The total number of PPPoEsubinterfaces in the system with an operational state of up(1).

The total number of PPPoEsubinterfaces in the system with an operational state of down(2).

The total number of PPPoEsubinterfaces in the system with an operational state of lowerLayerDown(7).

The total number of PPPoEsubinterfaces in the system with an operational state of notPresent(6).

This table contains entries for the PPPoEService-name tables.

The parameters for the PPPoEservice-name table.

Service-name table name.

Controls creation/deletion of entries in this table with READ-CREATE maximum access,according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create an entry in this table, the following entry objects MUST be explicitly configured: jnxPPPoEServiceNameTableRowStatus jnxPPPoEServiceNameTableName The Empty Service and Any service will be automatically configured for each Service Name Table created. On creating or deleting an entry in this table will create/destroy an entry for Service and service in jnxServiceNameTable. A corresponding entry in jnxServiceNameTable gets created or destroyed as a result of creating or destroying an entry in this table. The following values can be read from this object: active(1)

This table contains entries for the PPPoEService-names.

The parameters for the PPPoEservice-name table entry.

Service-name tag value.

Identifies the behavior when the the Service-name tag is received in a PADI frame.

Dynamic Profile associated with a Service-name.

Routing Instance associated with a Service-name.

The Max Sessions value used to cap the number of active PPPoEssessions that may be established with the specified Service entry.

Controls creation/deletion of entries in this table with READ-CREATE maximum access ,according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create an entry in this table, the following entry objects MUST be explicitly configured: jnxPPPoEServiceNameRowStatus The Service name is configured via the INDEX specified. A corresponding entry in jnxPPPoEServiceNameAciAriTable is destroyed as a result of destroying an entry in this table. The following values can be read from this object: active(1)

This table contains entries for the PPPoEServicename AciAri entries.

The parameters for the PPPoEservice-name AciAri table entry.

ACI tag values that the PPPoEclient would send in the PADI/PADR control packet.

ACI tag values that the PPPoEclient would send in the PADI/PADR control packet.

Identifies the behavior when the the Service-name with ACI/ARI pairs is received in a PADI frame.

Dynamic Profile associated with a Service-name and ACI/ARI pairs

Routing-Instance associated with a Service-name and ACI/ARI pairs

Static Interface associated with each ACI/ARI Entry.

Controls creation/deletion of entries in this table with READ-CREATE maximum access, according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create an entry in this table, the following entry objects MUST be explicitly configured: jnxPPPoEServiceNameAciAriRowStatus The ACIARI Entry is configured via the INDEX specified. The following values can be read from this object: active(1)