HP ProCurve Secure Router 7203 dl Advanced Management And Configuration Manual page 213

ProCurve Secure Router OS Firewall—Protecting the Internal, Trusted Network
Configuring Logging
The firewall logs all events of the specified priority and greater. For example,
to log all events to the event-history, enter:
ProCurve(config)# event-history priority info
To disable logging to the event history, enter:
ProCurve(config)# no event-history on
To re-enable logging, enter:
ProCurve(config)# event-history on
You can specify a different priority for events logged to a syslog server or email
address. (See "Forwarding Logs to a Syslog Server" on page 4-27 and "For-
warding Logs to an Email Address" on page 4-29.)
To examine the logs stored in the event history, enter the following command:
ProCurve# show event-history
Logs are marked with the date and time at which they occurred. They are also
labeled with the type of event. For example, the message can be about the
status of a line (E1) or interface (INTERFACE_STATUS). It can be a message
from a particular protocol, such as a PPP negotiation message or a DHCPACK
message.
Examining the event history will often help you to locate the source of a
problem, as well as monitor network activity to look for ways to reduce
overhead. When troubleshooting a specific problem, you should first clear the
event history:
ProCurve# clear event-history
You can then reproduce the problem and view the event history. Only logs
relevant to the problem will appear. If necessary, lower the priority level for
logging events and reproduce the problem again.
N o t e
The enable mode command, events, is different than the global configuration
mode command, event-history on. The first displays events to the terminal
as they occur. The second saves these events to an event history, stored on
the router, which you can view at any time.
4-25