2
Management
52
Example: Adding a message exception
In
this
example,
it
is
assumed
that
a
Syslog
server
has
already
been
configured
in
the
SEG
with
the
logical
name
My_Syslog
.
It
is
required
to
change
the
severity
of
the
log
message
161
(
“
Failed
to
Rekey
IKE
SA
”
)
in
the
category
IKE
from
the
default
of
Warning
to
become
Alert
.
1. Change
the
current
context
to
be
the
log
receiver
object:
Device:/>
cc
LogReceiver
LogReceiverSyslog
My_Syslog
2. Add
the
message
exception:
Device:/LogReceiverSyslog/My_Syslog>
add
LogReceiverMessageException
LogCategory=IKE
LogID=161
Action=INCLUDE
LogSeverity=Alert
All
the
message
exceptions
can
be
listed
for
this
receiver:
Device:/LogReceiverSyslog/My_Syslog>
show
LogReceiverMessageException
#
Category
Log
Message
ID
Action
LogSeverity
Comments
‐ ‐‐‐‐‐‐‐‐ ‐‐‐‐‐‐‐‐‐‐‐‐‐‐ ‐‐‐‐‐‐‐ ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ ‐‐‐‐‐‐‐‐
+
1
IKE
161
INCLUDE
Alert
(1)
Alert
<empty>
Notice
the
exception
gets
a
unique
index
number
to
identify
it.
In
this
case,
it
is
1
.
3. Change
the
context
back
to
the
default:
Device:/LogReceiverSyslog/My_Syslog>
cc
Device:/>
SNMP traps
SNMP protocol
Simple
Network
Management
Protocol
(SNMP)
is
a
means
for
communicating
between
a
Network
Management
System
(NMS)
and
a
managed
device.
SNMP
defines
3
types
of
messages:
a
Read
command
for
an
NMS
to
examine
a
managed
device,
a
Write
command
to
alter
the
state
of
a
managed
device,
and
a
Trap
that
is
used
by
managed
devices
to
send
messages
asynchronously
to
an
NMS
about
a
change
of
state.
SNMP traps in the SEG
The
SEG’s
implementation
of
SNMP
allows
any
log
event
message
to
be
sent
as
an
SNMP
trap
to
a
receiving
server.
This
means
that
the
administrator
can
set
up
SNMP
trap
notification
of
any
events
that
are
considered
important.
Note:
The
SEG
sends
SNMP
traps
that
are
based
on
the
SNMPv2c
standard
as
defined
by
RFC1901,
RFC1905,
and
RFC1906.
