2
Management
33
Remote access encryption
For
SNMP
version
1
or
2c,
the
community
string
will
be
sent
as
plain
text
over
a
network.
This
is
clearly
not
secure
if
a
remote
client
is
communicating
over
the
public
Internet.
If
this
is
the
case,
it
is
recommended
to
have
remote
access
take
place
over
an
encrypted
VPN
tunnel
or
similarly
secure
means
of
communication.
Preventing SNMP overload
The
advanced
setting
SNMP
Request
Limit
restricts
the
number
of
SNMP
requests
allowed
per
second.
This
can
help
prevent
attacks
through
SNMP
overload.
Optional SNMP settings
You
can
also
set
the
following
SNMP
parameters:
•
SNMPSysContact
–
The
contact
person
for
this
managed
node.
•
SNMPSysName
–
The
name
of
this
managed
node.
•
SNMPSysLocation
–
The
physical
location
of
this
node.
Example: Enabling SNMP monitoring
This
example
enables
SNMP
access
through
the
internal
lan
interface
from
the
network
mgmt
‐
net
using
the
community
string
Mg1RQqR
.
Device:/>
add
RemoteManagement
RemoteMgmtSNMP
my_snmp
SourceInterface=lan
SourceNetwork=mgmt
‐
net
SNMPGetCommunity=Mg1RQqR
Date and time
Correctly
setting
the
date
and
time
is
important
for
the
SEG
to
operate
properly.
For
example,
certificates
used
in
certificate
‐
based
VPN
tunnels
depend
on
the
system
clock
being
accurately
set.
In
addition,
log
messages
are
tagged
with
timestamps
in
order
to
indicate
when
a
specific
event
occurred.
Not
only
does
this
assume
a
working
clock,
but
also
that
the
clock
is
correctly
synchronized
with
other
equipment
in
the
network.
You
can
set
the
date
and
time
manually,
which
is
recommended
when
a
new
SEG
installation
is
started
for
the
first
time.
Local system clock
For
access
to
the
current
date
and
time,
the
SEG
uses
the
local
hardware
real
‐
time
hardware
clock.
Depending
on
the
hardware
platform,
this
clock
can
be
equipped
with
a
battery
backup
so
that
a
loss
of
power
will
not
affect
the
clock.