S W G U s e r G u i d e
Chapter 12: Configuring Alerts
68
SNMP MIB Monitoring area as instructed in the following substeps.
iv. In the
Authentication
Protocol
field, select the Authentication Protocol — either
verification checksums
MD5
or
SHA
.
v. In the
Authentication
Key
field, specify the user’s authentication key, which signs the
message being sent. There is a minimum 8 character requirement.
vi. In the
Encryption
Key
field, specify the user’s encryption key, which encrypts the data
portion of the message being sent. There is a minimum 8 character requirement.
b. Define the SNMP Traps parameters, by doing either of the following:
• To supply the same Security parameters (name, level, etc.) for SNMP Traps that you
used for MIB Monitoring, select the
Use
SNMP
MIB
Monitoring
Information
checkbox.
• Otherwise, fill in a
Security
name
, S
ecurity
level
,
Authentication
Protocol
,
Authentication
key
and
Encryption
key
for SNMP Traps. The same as MIB
Monitoring in
Step 8a
.
9. To test that the traps are successfully sent to the SNMP servers, click the
Test
button. A test
message will be sent to the defined server with the SNMP name, IP and SWG Software Version.
10. Click
Save
.
11. If you are ready to distribute and implement the changes in your system devices, click
.
NOTE:
The
encryption
mode
or
privacy
protocol
used
is
DES
encryption
algorithm.
NOTE:
SNMPv3
mandates
that
trap
messages
are
rejected
unless
the
SNMPv3
user
sending
the
trap
already
exists
in
the
user
database.
The
user
database
in
a
SNMPv3
application
is
referenced
by
a
combination
of
the
user's
name
or
Security
Name,
and
an
automatically
supplied
identifier
for
the
given
SNMP
application
or
engineID.
