Enable Acl "Deny" Logging; Requirements For Using Acl Logging; Acl Logging Operation - ProCurve 2610 Manual

Enable ACL "Deny" Logging

ACL logging enables the switch to generate a message when IP traffic meets
the criteria for a match with an ACE that results in an explicit "deny" action.
You can use ACL logging to help:
Test your network to ensure that your ACL configuration is detecting
■
and denying the traffic you do not want forwarded
Receive notification when the switch detects attempts to transmit
■
traffic you have designed your ACLs to reject
The switch sends ACL messages to Syslog and optionally to the current
console, Telnet, or SSH session. You can configure up to six Syslog server
destinations.

Requirements for Using ACL Logging

■ The switch configuration must include an ACL (1) assigned to an
interface and (2) containing an ACE configured with the deny action
and the log option.
■ To screen routed packets with destination IP addresses outside of the
switch, IP routing must be enabled.
■ For ACL logging to a Syslog server, the server must be accessible to
the switch and identified (with the logging < ip-addr > command) in
the switch configuration.
Debug must be enabled for ACLs and one or both of the following:
■
• logging (for sending messages to Syslog)
• Session (for sending messages to the current console interface)

ACL Logging Operation

When the switch detects a packet match with an ACE and the ACE includes
both the deny action and the optional log parameter, an ACL log message is
sent to the designated debug destination. The first time a packet matches an
ACE with deny and log configured, the message is sent immediately to the
destination and the switch starts a wait-period of approximately five minutes.
(The exact duration of the period depends on how the packets are internally
routed.) At the end of the collection period, the switch sends a single-line
Access Control Lists (ACLs)

Enable ACL "Deny" Logging

9-67