2
Management
31
Uploading certificate files
The
following
command
lines
show
how
a
typical
SCP
utility
might
upload
a
host
certificate
consisting
of
two
files
called
cert
‐
1.cer
and
cert
‐
1.key
to
a
security
gateway
that
has
the
management
IP
address
192.168.3.1
:
>
scp
C:\cert
‐
1.cer
admin@192.168.3.1:
>
scp
C:\cert
‐
1.key
admin@192.168.3.1:
In
each
case,
the
uploaded
file
will
retain
its
original
file
name.
Uploaded
certificate
files
are
stored
in
volatile
memory
and
must
be
associated
with
a
SEG
object
to
become
a
non
‐
volatile
part
of
the
configuration.
For
details,
refer
to
Creating
certificate
configuration
objects
on
page
130
.
Using wildcards with SCP
The
SEG
supports
the
use
of
the
wildcard
asterisk
(“*”)
with
SCP.
For
example,
to
download
all
the
files
with
a
file
type
of
.MIB
,
the
following
command
can
be
used:
>
scp
admin@192.168.3.1:*.mib
.
To
download
all
the
downloadable
files:
>
scp
admin@192.168.3.1:*
.
Wildcards
can
also
be
used
when
uploading.
For
example,
to
upload
all
the
backup
files
in
the
current
directory:
>
scp
*.bak
admin@192.168.3.1:backup/
SNMP monitoring
Simple
Network
Management
Protocol
(SNMP)
is
a
standardized
protocol
for
management
of
network
devices.
An
SNMP
compliant
client
can
connect
to
a
network
device
that
supports
the
SNMP
protocol
in
order
to
query
and
control
it.
The
SEG
supports
SNMP
version
1
and
version
2.
Connection
can
be
made
by
any
SNMP
compliant
clients
to
the
SEG.
However,
only
query
operations
are
permitted
for
security
reasons.
Specifically,
the
SEG
supports
the
following
SNMP
request
operations
by
an
SNMP
client:
•
GET
REQUEST
•
GET
NEXT
REQUEST
•
GET
BULK
REQUEST
(SNMP
Version
2c
only)
SEG MIB
The
Management
Information
Base
(MIB)
is
a
database,
in
the
form
of
a
text
file,
which
defines
the
parameters
on
a
network
device
that
an
SNMP
client
can
query
or
change.
The
MIB
files
for
a
device
running
the
SEG
are
located
in
the
filesystem
of
the
SEG
and
are
called
CLAVISTER
‐
SMI.mib
and
CLAVISTER.mib
.
