MIBs Depot

PPP-SEC-MIB

Registered at
1.3.6.1.2.1.10.23.2
Namespace
standard
Source file
PPP-SEC-MIB
Digest
sha256:a7faa24724337178a9c424ff099c50025e0a7fc954423fa44d540f19ad8f9045

Imports

FromSymbols
PPP-LCP-MIBppp
SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP
SNMPv2-SMICounter32, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, 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.

IANAifType-MIB
IF-MIB
PPP-LCP-MIB
PPP-SEC-MIB
SNMPv2-CONF
SNMPv2-MIB
SNMPv2-SMI
SNMPv2-TC

Objects

NameOIDSyntaxAccessStatus
pppSecurity
OBJECT-IDENTITY
1.3.6.1.2.1.10.23.2
pppSecurityProtocols
OBJECT-IDENTITY
1.3.6.1.2.1.10.23.2.1
pppSecurityPapProtocol
OBJECT-IDENTITY
1.3.6.1.2.1.10.23.2.1.1
pppSecurityChapMD5Protocol
OBJECT-IDENTITY
1.3.6.1.2.1.10.23.2.1.2
pppSecurityConfigTable
OBJECT-TYPE
Table containing the configuration and preference parameters for PPP Security.
1.3.6.1.2.1.10.23.2.2not-accessiblemandatory
pppSecurityConfigEntry
OBJECT-TYPE
Security configuration information for a particular PPP link.
1.3.6.1.2.1.10.23.2.2.1not-accessiblemandatory
pppSecurityConfigPreference
OBJECT-TYPE
The relative preference of the security protocol identified by pppSecurityConfigProtocol. Security protocols with lower values of pppSecurityConfigPreference are tried before protocols with higher values of pppSecurityConfigPreference.
1.3.6.1.2.1.10.23.2.2.1.2INTEGER (0..2147483647)read-writemandatory
pppSecurityConfigProtocol
OBJECT-TYPE
Identifies the security protocol to be attempted on the link identified by pppSecurityConfigLink at the preference level identified by pppSecurityConfigPreference.
1.3.6.1.2.1.10.23.2.2.1.3OBJECT IDENTIFIERread-writemandatory
pppSecurityConfigStatus
OBJECT-TYPE
Setting this object to the value invalid(1) has the effect of invalidating the corresponding entry in the pppSecurityConfigTable. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant pppSecurityConfigStatus object.
1.3.6.1.2.1.10.23.2.2.1.4INTEGER {invalid(1), valid(2)}read-writemandatory
pppSecuritySecretsTable
OBJECT-TYPE
Table containing the identities and secrets used by the PPP authentication protocols. As this table contains secret information, it is expected that access to this table be limited to those SNMP Party-Pairs for which a privacy protocol is in use for all SNMP messages that the parties exchange. This table contains both the ID and secret pair(s) that the local PPP entity will advertise to the remote entity and the pair(s) that the local entity will expect from the remote entity. This table allows for multiple id/secret password pairs to be specified for a particular link by using the pppSecuritySecretsIdIndex object.
1.3.6.1.2.1.10.23.2.3not-accessiblemandatory
pppSecuritySecretsEntry
OBJECT-TYPE
Secret information.
1.3.6.1.2.1.10.23.2.3.1not-accessiblemandatory
pppSecuritySecretsIdIndex
OBJECT-TYPE
A unique value for each ID/Secret pair that has been defined for use on this link. This allows multiple ID/Secret pairs to be defined for each link. How the local entity selects which pair to use is a local implementation decision.
1.3.6.1.2.1.10.23.2.3.1.2INTEGER (0..2147483647)read-onlymandatory
pppSecuritySecretsDirection
OBJECT-TYPE
This object defines the direction in which a particular ID/Secret pair is valid. If this object is local-to-remote then the local PPP entity will use the ID/Secret pair when attempting to authenticate the local PPP entity to the remote PPP entity. If this object is remote-to-local then the local PPP entity will expect the ID/Secret pair to be used by the remote PPP entity when the remote PPP entity attempts to authenticate itself to the local PPP entity.
1.3.6.1.2.1.10.23.2.3.1.3INTEGER {local-to-remote(1), remote-to-local(2)}read-writemandatory
pppSecuritySecretsProtocol
OBJECT-TYPE
The security protocol (e.g. CHAP or PAP) to which this ID/Secret pair applies.
1.3.6.1.2.1.10.23.2.3.1.4OBJECT IDENTIFIERread-writemandatory
pppSecuritySecretsIdentity
OBJECT-TYPE
The Identity of the ID/Secret pair. The actual format, semantics, and use of pppSecuritySecretsIdentity depends on the actual security protocol used. For example, if pppSecuritySecretsProtocol is pppSecurityPapProtocol then this object will contain a PAP Peer-ID. If pppSecuritySecretsProtocol is pppSecurityChapMD5Protocol then this object would contain the CHAP NAME parameter.
1.3.6.1.2.1.10.23.2.3.1.5OCTET STRING (SIZE(0..255))read-writemandatory
pppSecuritySecretsSecret
OBJECT-TYPE
The secret of the ID/Secret pair. The actual format, semantics, and use of pppSecuritySecretsSecret depends on the actual security protocol used. For example, if pppSecuritySecretsProtocol is pppSecurityPapProtocol then this object will contain a PAP Password. If pppSecuritySecretsProtocol is pppSecurityChapMD5Protocol then this object would contain the CHAP MD5 Secret.
1.3.6.1.2.1.10.23.2.3.1.6OCTET STRING (SIZE(0..255))read-writemandatory
pppSecuritySecretsStatus
OBJECT-TYPE
Setting this object to the value invalid(1) has the effect of invalidating the corresponding entry in the pppSecuritySecretsTable. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant pppSecuritySecretsStatus object.
1.3.6.1.2.1.10.23.2.3.1.7INTEGER {invalid(1), valid(2)}read-writemandatory