Juniper-PPP-MIB :: juniPppLinkConfigAuthentication2

MIB Reference — IPNetwork Monitor · Updated September 26, 2026

All MIBs › Juniper-PPP-MIB › juniPppLinkConfigAuthentication2

juniPppLinkConfigAuthentication2

Module: Juniper-PPP-MIB

OID (symbolic): Juniper-PPP-MIB::juniPppLinkConfigAuthentication2

OID (numeric): 1.3.6.1.4.1.4874.2.2.11.1.1.2.1.13

Node type: OBJECT-TYPE

Type: JuniNibbleConfig

Access: read-create

Description: A configuration variable comprised of nibbles i.e. 4 bits, such that a client can supply a list of 0 to 8 selections. The least significant nibble is the first value of the list, and the most significant nibble is the last value. The value in each field ranges from 0 to 15, however the first nibble with value 0 indicates the end of the list. Repetition of values is not allowed. Segregation of values is not allowed.

Valid Values are: none - 0 pap - 1 chap - 2 eap - 3

Example valid encoding: 0x00000321 0x00000012

Not a valid encoding: 0x00000121 0x01002001

If authentication negotiation is not supported for this PPP interface, then any attempt to explicitly set this object will result in a notWritable error and it will be implicitly set to the DEFVAL on row creation.

Setting this object to null will set juniPppLinkConfigAuthenticatorVirtualRouter object to an empty string.

Setting this object along with the juniPppLinkConfigAuthentication object will return an inconsistentValue error.

What is juniPppLinkConfigAuthentication2?

This is a packed configuration value made of up to eight 4-bit nibbles, letting an admin supply an ordered list of selections (a nibble of 0 marks the end of the list, and repeats aren't allowed) for extended authentication option sequencing beyond what juniPppLinkConfigAuthentication alone supports. It's a low-level, vendor-specific encoding rather than something read casually, so admins typically set it via a CLI command that hides the bit-packing. For example, a platform CLI might translate 'authentication order chap pap' into the correct nibble sequence here.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.4874juniperUniJuniper-UNI-SMI
1.3.6.1.4.1.4874.2juniperUniMibsJuniper-UNI-SMI
1.3.6.1.4.1.4874.2.2juniMibsJuniper-MIBs
1.3.6.1.4.1.4874.2.2.11juniPppMIBJuniper-MIBs
Numeric OIDNameModule
1.3.6.1.4.1.4874.2.2.11.1juniPppObjectsJuniper-PPP-MIB
1.3.6.1.4.1.4874.2.2.11.1.1juniPppLcpJuniper-PPP-MIB
1.3.6.1.4.1.4874.2.2.11.1.1.2juniPppLinkConfigTableJuniper-PPP-MIB
1.3.6.1.4.1.4874.2.2.11.1.1.2.1juniPppLinkConfigEntryJuniper-PPP-MIB
1.3.6.1.4.1.4874.2.2.11.1.1.2.1.13juniPppLinkConfigAuthentication2Juniper-PPP-MIB