Microplex M204, Руководство по установке и настройке, Страница: 139 / 204

USING THE M204’S ADDITIONAL OPTIONS: Managing With SNMP 131
destinations, logpaths, and users.
status group All dynamic monitoring components such as
print queues, user logins, and RPRINTER con-
figurations.
command group This includes the commands save, load, and
reset.
These variables can have read, write, or read-
write permissions. Along with these permissions
there are other elements that can limit the write
access to these variables. Please see SNMP Secu-
rity on page 131 and User Accounts and Permis-
sions on page 82 for more information.
Custom MIB Traps
A trap is an event generated by an agent to indicate a significant event to the manager.
The M204 continuously generates three traps:
coldstart A generic trap generated every time the M204 is
powered on or reset
authenticationFailure A generic trap generated whenever a disallowed
access is attempted
lpqIOStatusChanged The only custom trap. This trap is generated
whenever an I/O port’s status changes.
No trap is generated on a CTS change on the
serial ports. Only DCD changes will trigger this.
SNMP Security
SNMP does not include any formal type of security definition. However, security can
be accomplished using communities. A community is a string that is sent with every
SNMP request and is used to define a certain view of the MIB. By doing this, you can
control what parts of the MIB are accessed by SNMP managers.
To access the M204’s custom MIB, the public community string can be used to read
any variable that have read access. To restrict write access, there is an additional
security step implemented. This involves defining a user named snmp on the M204
with root privileges. The password defined for this snmp user will then be used as the
Note
Note