<securityType> is the minimum security level that must be used to gain access to this access right.
Possible values are:
• noauthnopriv (no authentication and no privacy)
• authnopriv (authentication but no privacy)
• authpriv (authentication and privacy)
<contextMatch> the type of match required. Possible values are:
• exact (the context name must exactly match the value in contextName)
• prefix (the context name must match the first few starting characters of the value in
contextName)
<readView> the authorized MIB view name used for read access, must match one of the view
name.
<writeView> the authorized MIB view name used for write access, must match one of the view
name.
<notifyView> the authorized MIB view name used for notify access, must match one of the view
name.
The correct syntax for addView is:
addView <viewName> <subtree> <mask> <included>
<viewName> is the name of the view.
<subtree> is the OID subtree which when combined with the corresponding instance of MASK
defines a family of view subtrees.
<mask> the mask for filtering OID.
<included> the OID can be included or excluded. Possible values are:
• included (for including)
• excluded (for excluding)
The correct syntax for addManager is:
addManager <security> <ipAddress> <credentials> <securityType>
<security> is the security type for the notification. Possible values are:
• USM (User-based Security Model with SNMPv3)
• V2 (SNMPv2)
• v1 (SNMPv1)
<ipAddress> is the IP address of the SNMP manager.
<credentials> is either the user name (when using USM security) or the trap community (when
using v1 security)
<securityType> is either:
• noauthnopriv (for SNMPv1 and SNMPv2)
• authpriv (for SNMPv3)
addManager do not allow duplicate entries (one ipAddress can receive only one trap).
A sample snmp.conf is provided; the default users authorized are:
To Next Page
Loading...
