PPP-SEC-MIB.mib object view, vendor RFC
Introduction
Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers).
This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.
ActiveXperts Network Monitor 2024 can import MIB file PPP-SEC-MIB and use it to monitor vendor specific OID's.
PPP-SEC-MIB file content
Object view of PPP-SEC-MIB:
| Scalar Object |
| pppSecurityConfigEntry |
.1.3.6.1.2.1.10.23.2.2.1 |
|
Security configuration information for a
particular PPP link.
|
| pppSecuritySecretsEntry |
.1.3.6.1.2.1.10.23.2.3.1 |
|
Secret information.
|
| Tabular Object |
| pppSecurityConfigLink |
.1.3.6.1.2.1.10.23.2.2.1.1 |
|
The value of ifIndex that identifies the entry
in the interface table that is associated with
the local PPP entity's link for which this
particular security algorithm shall be
attempted. A value of 0 indicates the default
algorithm - i.e., this entry applies to all
links for which explicit entries in the table
do not exist.
|
| pppSecurityConfigPreference |
.1.3.6.1.2.1.10.23.2.2.1.2 |
|
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.
|
| pppSecurityConfigProtocol |
.1.3.6.1.2.1.10.23.2.2.1.3 |
|
Identifies the security protocol to be
attempted on the link identified by
pppSecurityConfigLink at the preference level
identified by pppSecurityConfigPreference.
|
| pppSecurityConfigStatus |
.1.3.6.1.2.1.10.23.2.2.1.4 |
|
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.
|
| pppSecuritySecretsLink |
.1.3.6.1.2.1.10.23.2.3.1.1 |
|
The link to which this ID/Secret pair applies.
By convention, if the value of this object is 0
then the ID/Secret pair applies to all links.
|
| pppSecuritySecretsIdIndex |
.1.3.6.1.2.1.10.23.2.3.1.2 |
|
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.
|
| pppSecuritySecretsDirection |
.1.3.6.1.2.1.10.23.2.3.1.3 |
|
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.
|
| pppSecuritySecretsProtocol |
.1.3.6.1.2.1.10.23.2.3.1.4 |
|
The security protocol (e.g. CHAP or PAP) to
which this ID/Secret pair applies.
|
| pppSecuritySecretsIdentity |
.1.3.6.1.2.1.10.23.2.3.1.5 |
|
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.
|
| pppSecuritySecretsSecret |
.1.3.6.1.2.1.10.23.2.3.1.6 |
|
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.
|
| pppSecuritySecretsStatus |
.1.3.6.1.2.1.10.23.2.3.1.7 |
|
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.
|
| Table |
| pppSecurityConfigTable |
.1.3.6.1.2.1.10.23.2.2 |
|
Table containing the configuration and
preference parameters for PPP Security.
|
| pppSecuritySecretsTable |
.1.3.6.1.2.1.10.23.2.3 |
|
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.
|
| Object Identifier |
| pppSecurity |
.1.3.6.1.2.1.10.23.2 |
| pppSecurityProtocols |
.1.3.6.1.2.1.10.23.2.1 |
| pppSecurityPapProtocol |
.1.3.6.1.2.1.10.23.2.1.1 |
| pppSecurityChapMD5Protocol |
.1.3.6.1.2.1.10.23.2.1.2 |
