MIBs Depot

Juniper-PPPOE-PROFILE-MIB

Registered at
1.3.6.1.4.1.4874.2.2.46
Last updated
2008-06-18 10:29
Organization
Juniper Networks, Inc.
Revisions
2008-06-18 10:29, 2005-07-13 11:40, 2004-06-10 19:25, 2003-03-11 21:58, 2002-09-16 21:44, 2002-08-15 20:34, 2002-08-15 19:07, 2001-03-21 18:32
Namespace
juniper
Source file
Juniper-PPPOE-PROFILE-MIB
Digest
sha256:b61c7388638d74b8f92c6de09aef53bb5f9737c474afeb65598ca1d063b2b4e6

Description

The point-to-point protocol over Ethernet (PPPoE) profile MIB for the Juniper enterprise.

Contact

Juniper Networks, Inc. Postal: 10 Technology Park Drive Westford, MA 01886-3146 USA Tel: +1 978 589 5800 Email: mib@Juniper.net

Imports

FromSymbols
Juniper-MIBsjuniMibs
Juniper-TCJuniEnable, JuniSetMap
SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP
SNMPv2-SMIInteger32, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, Unsigned32, iso
SNMPv2-TCDisplayString, TEXTUAL-CONVENTION

Imported by

Nothing in this corpus imports this module.

Load order

Every file a consumer needs in order to load this module, dependencies first.

Juniper-MIBs
Juniper-PPPOE-PROFILE-MIB
Juniper-TC
Juniper-UNI-SMI
SNMPv2-CONF
SNMPv2-SMI
SNMPv2-TC

Objects

NameOIDSyntaxAccessStatus
juniPppoeProfileObjects
OBJECT-IDENTITY
1.3.6.1.4.1.4874.2.2.46.1
juniPppoeProfile
OBJECT-IDENTITY
1.3.6.1.4.1.4874.2.2.46.1.1
juniPppoeProfileTable
OBJECT-TYPE
This table contains profiles for configuring PPPoE interfaces/sessions. Entries in this table are created/deleted as a side-effect of corresponding operations to the juniProfileNameTable in the Juniper-PROFILE-MIB.
1.3.6.1.4.1.4874.2.2.46.1.1.1not-accessiblecurrent
juniPppoeProfileEntry
OBJECT-TYPE
A profile describing configuration of a PPPoE interface and its subinterfaces (sessions).
1.3.6.1.4.1.4874.2.2.46.1.1.1.1not-accessiblecurrent
juniPppoeProfileId
OBJECT-TYPE
The integer identifier associated with this profile. A value for this identifier is determined by locating or creating a profile name in the juniProfileNameTable.
1.3.6.1.4.1.4874.2.2.46.1.1.1.1.1Unsigned32not-accessiblecurrent
juniPppoeProfileSetMap
OBJECT-TYPE
A bitmap representing which objects in this entry have been explicitly configured. See the definition of the JuniSetMap TEXTUAL-CONVENTION for details of use. The INDEX object(s) and this object are excluded from representation (i.e. their bits are never set). When a SET request does not explicitly configure JuniSetMap, bits in JuniSetMap are set as a side-effect of configuring other profile attributes in the same entry. If, however, a SET request explicitly configures JuniSetMap, the explicitly configured value overrides 1) any previous bit settings, and 2) any simultaneous 'side-effect' settings that would otherwise occur. Once set, bits can only be cleared by explicitly configuring JuniSetMap.
1.3.6.1.4.1.4874.2.2.46.1.1.1.1.2JuniSetMapread-writecurrent
juniPppoeProfileMaxNumSessions
OBJECT-TYPE
The maximum number of PPPoE sessions (subinterfaces) that can be configured on the main PPPoE interface created using this profile. A value of zero indicates no bound is configured.
1.3.6.1.4.1.4874.2.2.46.1.1.1.1.3Integer32 (0..65535)read-writecurrent
juniPppoeProfileSubMotm
OBJECT-TYPE
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.
1.3.6.1.4.1.4874.2.2.46.1.1.1.1.4DisplayString (SIZE(0..127))read-writecurrent
juniPppoeProfileSubUrl
OBJECT-TYPE
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.
1.3.6.1.4.1.4874.2.2.46.1.1.1.1.5DisplayString (SIZE(0..127))read-writecurrent
juniPppoeProfileDupProtect
OBJECT-TYPE
Flag to control whether duplicate MAC addresses are allowed
1.3.6.1.4.1.4874.2.2.46.1.1.1.1.6JuniEnableread-writecurrent
juniPppoeProfileAcName
OBJECT-TYPE
The name to use for the AC-NAME tag that is sent in any PADO that is sent on this interface.
1.3.6.1.4.1.4874.2.2.46.1.1.1.1.7DisplayString (SIZE(0..64))read-writecurrent
juniPppoeProfilePadiFlag
OBJECT-TYPE
The PPPoE major interface parameter PADI flag controls whether to always repsond to a PADI with a PADO regardless of the ability to create the session and allow the session establish phase to resolve it.
1.3.6.1.4.1.4874.2.2.46.1.1.1.1.8JuniEnableread-writecurrent
juniPppoeProfilePacketTrace
OBJECT-TYPE
The PPPoE major interface parameter packet tracing flag controls whether packet tracing is enable or not.
1.3.6.1.4.1.4874.2.2.46.1.1.1.1.9JuniEnableread-writecurrent
juniPppoeProfileServiceNameTableName
OBJECT-TYPE
The PPPoE Service name table controls behavior of PADO control packets.
1.3.6.1.4.1.4874.2.2.46.1.1.1.1.10DisplayString (SIZE(0..31))read-writecurrent
juniPppoeProfilePadrRemoteCircuitIdCapture
OBJECT-TYPE
The PPPoE major interface parameter PADR remote circuit id capture flag controls whether the remote circuit id string possibly contained in the PADR packet will be saved and used by AAA to replace the NAS-PORT-ID field.
1.3.6.1.4.1.4874.2.2.46.1.1.1.1.11JuniEnableread-writecurrent
juniPppoeProfileMtu
OBJECT-TYPE
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.
1.3.6.1.4.1.4874.2.2.46.1.1.1.1.12Integer32 (1 | 2 | 66..65535)read-writecurrent
juniPppoeProfileMaxSessionOverride
OBJECT-TYPE
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
1.3.6.1.4.1.4874.2.2.46.1.1.1.1.13INTEGER {override(1), ignore(2)}read-writecurrent
juniPppoeProfileConformance
OBJECT-IDENTITY
1.3.6.1.4.1.4874.2.2.46.4
juniPppoeProfileCompliances
OBJECT-IDENTITY
1.3.6.1.4.1.4874.2.2.46.4.1
juniPppoeProfileGroups
OBJECT-IDENTITY
1.3.6.1.4.1.4874.2.2.46.4.2

Conformance

NameOIDStatus
juniPppoeProfileCompliance
MODULE-COMPLIANCE
Obsolete compliance statement for entities which implement the Juniper PPPoE Profile MIB. This statement became obsolete when the duplicate MAC address indicator and AC-NAME tag were added.
1.3.6.1.4.1.4874.2.2.46.4.1.1obsolete
juniPppoeCompliance2
MODULE-COMPLIANCE
Obsolete compliance statement for entities which implement the Juniper PPPoE profile MIB. This statement became obsolete when PADI flag, AC-name and packet trace objects were added.
1.3.6.1.4.1.4874.2.2.46.4.1.2obsolete
juniPppoeCompliance3
MODULE-COMPLIANCE
Obsolete compliance statement for entities which implement the Juniper PPPoE profile MIB. This statement became obsolete when the service name table was added.
1.3.6.1.4.1.4874.2.2.46.4.1.3obsolete
juniPppoeCompliance4
MODULE-COMPLIANCE
Obsolete compliance statement for entities which implement the Juniper PPPoE profile MIB. This statement became obsolete when the remote circuit id capture was added.
1.3.6.1.4.1.4874.2.2.46.4.1.4obsolete
juniPppoeCompliance5
MODULE-COMPLIANCE
Obsolete compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when support was added for MTU configuration.
1.3.6.1.4.1.4874.2.2.46.4.1.5obsolete
juniPppoeCompliance6
MODULE-COMPLIANCE
Obsolete compliance statement for entities which implement the Juniper PPPoE MIB. This statement became obsolete when support was added for juniPppoeProfileMaxSessionOverride.
1.3.6.1.4.1.4874.2.2.46.4.1.6obsolete
juniPppoeCompliance7
MODULE-COMPLIANCE
The compliance statement for entities which implement the Juniper PPPoE Profile MIB.
1.3.6.1.4.1.4874.2.2.46.4.1.7current
juniPppoeProfileGroup
OBJECT-GROUP
Obsolete collection of objects providing management of profile functionality for PPPoE interfaces in a Juniper product. This group became obsolete when the duplicate MAC address indicator and AC-NAME tag objects were added.
1.3.6.1.4.1.4874.2.2.46.4.2.1obsolete
juniPppoeProfileGroup2
OBJECT-GROUP
Obsolete collection of objects providing management of profile functionality for PPPOE interfaces in a Juniper product. This group became obsolete when PADI flag, AC-name and packet trace objects were added.
1.3.6.1.4.1.4874.2.2.46.4.2.2obsolete
juniPppoeProfileGroup3
OBJECT-GROUP
A collection of objects providing management of profile functionality for PPPOE interfaces in a Juniper product.
1.3.6.1.4.1.4874.2.2.46.4.2.3obsolete
juniPppoeProfileGroup4
OBJECT-GROUP
A collection of objects providing management of profile functionality for PPPOE interfaces in a Juniper product.
1.3.6.1.4.1.4874.2.2.46.4.2.4obsolete
juniPppoeProfileGroup5
OBJECT-GROUP
A collection of objects providing management of profile functionality for PPPOE interfaces in a Juniper product.
1.3.6.1.4.1.4874.2.2.46.4.2.5obsolete
juniPppoeProfileGroup6
OBJECT-GROUP
A collection of objects providing management of profile functionality for PPPOE interfaces in a Juniper product.
1.3.6.1.4.1.4874.2.2.46.4.2.6obsolete
juniPppoeProfileGroup7
OBJECT-GROUP
A collection of objects providing management of profile functionality for PPPOE interfaces in a Juniper product.
1.3.6.1.4.1.4874.2.2.46.4.2.7current