Lantronix X300 Series X300 Series User Guide Rev B - Page 112
SNMPv3 with User-based Security Model (USM), System Information and Monitoring, Active Monitoring
View all Lantronix X300 Series manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 112 highlights
10: Services The Group and com2sec keywords determine who has this access. Figure 10-3 shows how the fields map in the VACM configuration model. com2sec secName Figure 10-3 VACM Configuration Model ipSource default community group access view groupName groupName viewName model v1 v2c usm context "" type included excluded secName model v1 v2c usm any oidSubtree level noauth auth priv prefix exact prefix readScope viewName none writeScope viewName none notifyScope viewName none [mask] SNMPv3 usm userName Security level NoAuth,NoPriv Auth,NoPriv Auth,Priv auth MD5 SHA privacy DES AES For SNMP v1/v2c/USM VACM configuration details, see Table 10-20 on page 116. SNMPv3 with User-based Security Model (USM) SNMPv3 with USM contains a private list of users and keys specific to the SNMPv3 protocol. To use this model, the SNMPv3 USM users must be created and added to the VACM group table (as security name). For SNMPv3 with USM user configuration details, see Table 10-22 on page 119. System Information and Monitoring System information includes system group information and monitoring information, which is described below. The system group information, such as name, location, contact, and description, are retrieved from the underlying network management system. The agent is built with support for monitoring the local system. The following directives can be specified: Process monitoring - provides information about individual processes running on the local system Disk usage monitoring - provides information about disk usage for specified disks or all disks System load monitoring - provides information about system load average and swap space Log file monitoring - monitors the file size of specified log files For system information and monitoring configuration details, see Table 10-19 on page 114. Active Monitoring The agent can be configured to generate trap notifications based on the following directives: Authentication failure trap - generate authentication failure traps X300 Series IoT Cellular Gateway User Guide 112