PPP-SEC-MIB

File: PPP-SEC-MIB.mib (13617 bytes)

Imported modules

RFC1155-SMI RFC-1212 PPP-LCP-MIB

Imported symbols

Counter OBJECT-TYPE ppp

Defined Objects

pppSecurity 1.3.6.1.2.1.10.23.2
OBJECT IDENTIFIER    

pppSecurityProtocols 1.3.6.1.2.1.10.23.2.1
OBJECT IDENTIFIER    

pppSecurityPapProtocol 1.3.6.1.2.1.10.23.2.1.1
OBJECT IDENTIFIER    

pppSecurityChapMD5Protocol 1.3.6.1.2.1.10.23.2.1.2
OBJECT IDENTIFIER    

pppSecurityConfigTable 1.3.6.1.2.1.10.23.2.2
Table containing the configuration and preference parameters for PPP Security.
OBJECT-TYPE    
  SEQUENCE OF  
    PppSecurityConfigEntry

pppSecurityConfigEntry 1.3.6.1.2.1.10.23.2.2.1
Security configuration information for a particular PPP link.
OBJECT-TYPE    
  PppSecurityConfigEntry  


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.
OBJECT-TYPE    
  INTEGER 0..2147483647  

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.
OBJECT-TYPE    
  OBJECT IDENTIFIER  

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.
OBJECT-TYPE    
  INTEGER invalid(1), valid(2)  

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-TYPE    
  SEQUENCE OF  
    PppSecuritySecretsEntry

pppSecuritySecretsEntry 1.3.6.1.2.1.10.23.2.3.1
Secret information.
OBJECT-TYPE    
  PppSecuritySecretsEntry  


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.
OBJECT-TYPE    
  INTEGER 0..2147483647  

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.
OBJECT-TYPE    
  INTEGER local-to-remote(1), remote-to-local(2)  

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.
OBJECT-TYPE    
  OBJECT IDENTIFIER  

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.
OBJECT-TYPE    
  OCTET STRING SIZE(0..255)  

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.
OBJECT-TYPE    
  OCTET STRING SIZE(0..255)  

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.
OBJECT-TYPE    
  INTEGER invalid(1), valid(2)  

Defined Objects

PppSecurityConfigEntry  
SEQUENCE    
  INTEGER as pppSecurityConfigLink  
  INTEGER as pppSecurityConfigPreference  
  OBJECT IDENTIFIER as pppSecurityConfigProtocol  
  INTEGER as pppSecurityConfigStatus  

PppSecuritySecretsEntry  
SEQUENCE    
  INTEGER as pppSecuritySecretsLink  
  INTEGER as pppSecuritySecretsIdIndex  
  INTEGER as pppSecuritySecretsDirection  
  OBJECT IDENTIFIER as pppSecuritySecretsProtocol  
  OCTET STRING as pppSecuritySecretsIdentity  
  OCTET STRING as pppSecuritySecretsSecret  
  INTEGER as pppSecuritySecretsStatus