12-6
Cisco Intrusion Prevention System Sensor CLI Configuration Guide for IPS 7.2
OL-29168-01
Chapter12 C onfiguring IP Logging
Stopping Active IP Logs
Step 3
Display a brief list of all IP logs.
sensor# iplog-status brief
Log ID VS IP Address1 Status Event ID Start Date
2425 vs0 192.0.2.10 started N/A 2003/07/30
2342 vs0 192.0.2.20 completed 209348 2003/07/30
sensor#
Stopping Active IP Logs
Use the no iplog [log-id log_id | name name] command to stop logging for the logs that are in the
started
state and to remove logs that are in the
added
state. The no iplog command does not remove or
delete the IP log. It only signals to the sensor to stop capturing additional packets on that IP log.
Note
Using the no iplog command on an added state IP log stops the IP log. The added state means that the
IP log is still empty (no packets). Stopping it when there are no packets means you are stopping an empty
IP log. An empty log is removed when it is stopped.
The following options apply:
log_id—Specifies the log ID of the logging session to stop. Use the iplog-status command to find
the log ID.
name—Specifies the virtual sensor on which to begin or end logging.
Disabling IP Logging Sessions
To disable one or all IP logging sessions, follow these steps:
Step 1
Log in to the CLI using an account with administrator or operator privileges.
Step 2
Stop a particular IP logging session:
a.
Find the log ID of the session you want to stop.
sensor# iplog-status
Log ID: 1
IP Address 1: 192.0.2.1
Virtual Sensor: vs0
Status: added
Event ID: 0
Bytes Captured: 0
Packets Captured: 0
sensor#
Note
Each alert references IP logs that are created because of that alert. If multiple alerts create
IP logs for the same IP address, only one IP log is created for all the alerts. Each alert
references the same IP log. However, the output of the IP log status only shows the event ID
of the first alert triggering the IP log.
b.
Stop the IP log session.
sensor# no iplog log-id 137857512