The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter contains the IPS 5.1 commands listed in alphabetical order. It contains the following sections:.
•copy
•end
•exit
•more
•ping
To create a banner message to display on the terminal screen, use the banner login command in global configuration mode. To delete the login banner, use the no form of this command. The banner message appears when a user accesses the CLI and is displayed before the username and password prompts.
banner login
no banner login
argument |
Text that appears before you log in to the CLI. Maximum message length is 2500 characters. A carriage return or question mark (?) must be preceded by the keystroke Ctrl-V. |
No default behavior or values.
Global configuration
Administrator
|
|
---|---|
5.0(1) |
This command was introduced. |
The banner login command lets you create a text message, up to 2500 characters, to display on the terminal screen. This message appears when you access the CLI. You can include a carriage return or question mark (?) in the message by first typing Ctrl-V followed by the carriage return or question mark. A carriage return is represented as ^M in the text message you create, but appears as an actual carriage return when the message is displayed to the user.
Press Ctrl-C at the Message
prompt to cancel the message request.
Note The format for this command is different from the Cisco IOS 12.0 implementation.
The following example creates a message to display on the terminal screen at login:
sensor(config)# banner login
Banner[]:
This message will be displayed on login. ^M Thank you!
At login, the following message appears:
This message will be displayed on login.
Thank you!
password:
To delete the current list of denied IP addresses, use the clear denied-attackers command in privileged EXEC mode.
clear denied-attackers
This command has no arguments or keywords.
No default behavior or values.
EXEC
Administrator
|
|
---|---|
5.0(1) |
This command was introduced. |
The clear denied-attackers command lets you restore communication with previously denied IP addresses by clearing the list of denied attackers. You cannot select and delete individual IP addresses on this list. If you clear the denied attackers list, all IP addresses are removed from the list.
Note This command does not exist in Cisco IOS 12.0 or earlier.
The following example removes all IP addresses from the denied attackers list:
sensor#
clear denied-attackers
Warning: Executing this command will delete all addresses from the list of attackers
currently being denied by the system.
Continue with clear? []:
yes
sensor#
|
|
---|---|
show statistics denied-attackers |
Displays the list of denied attackers. |
To clear the Event Store, use the clear events command in privileged EXEC mode.
clear events
This command has no arguments or keywords.
No default behavior or values.
EXEC
Administrator
|
|
---|---|
4.0(1) |
This command was introduced. |
Use this command to clear all events from the Event Store.
Note This command does not exist in Cisco IOS 12.0 or earlier.
The following example clears the Event Store:
sensor#
clear events
Warning: Executing this command will remove all events currently stored in the event
store.
Continue with clear? []:
yes
sensor#
To terminate another CLI session, use the clear line command in privileged EXEC mode.
clear line cli-id [message]
cli-id |
The CLI ID number associated with the login session. See the show users command. |
message |
(Optional) If you select message, you are prompted for a message to send to the receiving user. |
No default behavior or values.
EXEC
|
|
---|---|
5.0(1) |
This command was introduced. |
Administrator, Operator, Viewer
Note Operator and Viewer can only clear lines with the same username as the current login.
Use the clear line command to log out of a specific session running on another line. Use the message keyword if you want to include an optional message to display on the terminal of the login session you are terminating. Ctrl-C cancels the request and the carriage return sends the request with the specified message. The maximum message length is 2550 characters. Use Ctrl-V followed by a carriage return to put a carriage return in the message text.
You cannot use the clear line command to clear a Service account login.
Note The message keyword is not supported in the Cisco IOS 12.0 version of this command.
The following example illustrates the output displayed when a user with Administrator privileges attempts to log in after the maximum sessions have been reached:
Error: The maximum allowed CLI sessions are currently open, would you like to terminate
one of the open sessions? [no]
yes
CLI ID User Privilege
1253 admin1 administrator
1267 cisco administrator
1398 test operator
Enter the CLI ID to clear:
1253
Message:
Sorry! I need access to the system, so I am terminating your session.
sensor#
The following example illustrates the message displayed on the terminal of admin1:
sensor#
***
***
Termination request from Admin0
***
Sorry! I need access to the system, so I am terminating your session.
The following example illustrates the output displayed when a user with Operator or Viewer privileges attempts to log in after the maximum sessions have been reached:
Error: The maximum allowed CLI sessions are currently open, please try again later.
|
|
---|---|
show users |
Displays information about users logged in to the CLI. |
To manually set the system clock on the appliance, use the clock set command in privileged EXEC mode.
clock set hh:mm[:ss] month day year
hh:mm[:ss] |
Current time in hours (24-hour format), minutes, and seconds |
month |
Current month (by name) |
day |
Current day (by date) in the month |
year |
Current year (no abbreviation) |
No default behavior or values.
EXEC
Administrator
|
|
---|---|
4.0(1) |
This command was introduced. |
You do not need to set the system clock under the following circumstances:
•When the system is synchronized by a valid outside timing mechanism, such as an NTP or VINES clock source.
•When you have a router with calendar capability.
Use the clock set command if no other time sources are available. The time specified in this command is relative to the configured time zone.
The following example manually sets the system clock to 1:32 p.m. on July 29.2002:
sensor# clock set 13:32 July 29 2002
sensor#
To enter global configuration mode, use the configure terminal command in privileged EXEC mode.
configure terminal
terminal |
Executes configuration commands from the terminal. |
No default behavior or values.
EXEC
Administrator, Operator, Viewer
Executing the configure terminal command puts you in global configuration mode.
The following example changes modes from privileged EXEC to global configuration:
sensor# configure terminal
sensor(config)#
To copy iplogs and configuration files, use the copy command in privileged EXEC mode.
copy [/erase] source-url destination-url
copy iplog log-id destination-url
No default behavior or values.
EXEC
Administrator, Operator (copy iplog or packet-file only), Viewer (copy iplog or packet-file only)
|
|
---|---|
4.0(1) |
This command was introduced. |
The exact format of the source and destination URLs varies according to the file. The following valid types are supported:
Use keywords to designate the file location on the sensor. The following files are supported:
If FTP or SCP is the selected protocol, you are prompted for a password. If no password is necessary for the FTP session, you can press Return without entering anything.
You can enter all necessary source and destination URL information and the username on the command line, or you can enter the copy command and have the sensor prompt you for any missing information.
Warning Copying a configuration file from another sensor can result in errors if the system sensing interfaces and virtual sensors are not configured the same. |
Note The Cisco IOS 12.0 copy command is more flexible and allows copying between different destinations.
The following example copies a file into the current configuration from the sensor with the IP address 10.1.1.1, directory/filename ~csidsuser/configuration/cfg, the directory and file are relative to the csidsuser's home account:
sensor# copy scp://csidsuser@10.1.1.1/configuration/cfg current-config
Password: *******
WARNING: Copying over the current configuration may leave the box in an unstable state.
Would you like to copy current-config to backup-config before proceeding? [yes]:
csidsuser@10.1.1.1's password:
cfg 100% |*********************************************************************| 36124 00:00
sensor#
The following example copies the iplog with ID 12345 to the sensor with the IP address 10.1.1.1, directory/filename ~csidsuser/iplog12345, the directory and file are relative to the csidsuser's home account:
sensor# copy iplog 12345 scp://csidsuser@10.1.1.1/iplog12345
Password: *******
iplog 100% |*********************************************************************|
36124 00:00
sensor#
|
|
---|---|
iplog-status |
Displays a description of the available IP log contents. |
more |
Displays the contents of a logical file. |
packet |
Displays or captures live traffic on an interface. |
To direct all output to the serial connection, use the display serial command in global configuration mode. Use the no display-serial command to reset the output to the local terminal.
display-serial
no display-serial
This command has no arguments or keywords.
The default setting is no display-serial.
EXEC
Administrator, Operator
|
|
---|---|
4.0(1) |
This command was introduced. |
Using the display-serial command lets you view system messages on a remote console (using the serial port) during the boot process. The local console is not available as long as this option is enabled. Unless you set this option when you are connected to the serial port, you do not get any feedback until Linux has fully booted and enabled support for the serial connection.
The following example redirects output to the serial port:
sensor(config)# display-serial
sensor(config)#
To remove the most recent upgrade, use the downgrade command in global configuration mode.
downgrade
This command has no arguments or keywords.
No default behavior or values.
Global configuration
Administrator
|
|
---|---|
4.0(1) |
This command was introduced. |
The following example removes the most recent upgrade from the system:
sensor(config)#
downgrade
Warning: Executing this command will reboot the system and downgrade to
IDS-K9-sp-4.1-4-S91.rpm. Configuration changes made since the last upgrade will be lost
and the system may be rebooted.
Continue with downgrade?:
yes
sensor#
If the downgrade command is not available, for example, if no upgrades have been applied, the following is displayed:
sensor#
downgrade
Error: No downgrade available
sensor#
|
|
---|---|
show version |
Displays the version information for all installed OS packages, signature packages, and IPS processes running on the system. |
To exit configuration mode, or any of the configuration submodes, use the end command in global configuration mode. This command exits to the top level EXEC menu.
end
This command has no arguments or keywords.
No default behavior or values.
All modes
Administrator, Operator, Viewer
|
|
---|---|
4.0(1) |
This command was introduced. |
The following example shows how to exit configuration mode:
sensor# configure terminal
sensor(config)# end
sensor#
To delete a logical file, use the erase command in privileged EXEC mode.
erase {backup-config | current-config | packet-file}
No default behavior or values.
EXEC
Administrator
|
|
---|---|
4.0(1) |
This command was introduced. |
The Cisco IOS 12.0 version of this command lets you remove entire file systems. IPS does not support this concept.
The following example erases the current configuration file and returns all settings back to default. You may need to reboot the sensor with this command.
sensor# erase current-config
Warning: Removing the current-config file will result in all configuration being reset to default, including system information such as IP address.
User accounts will not be erased. They must be removed manually using the "no username" command.
Continue? []: yes
sensor#
To exit a configuration mode or close an active terminal session and terminate privileged EXEC mode, use the exit command.
exit
This command has no arguments or keywords.
No default behavior or values.
All modes
Administrator, Operator, Viewer
|
|
---|---|
4.0(1) |
This command was introduced. |
Use the exit command to return to the previous menu level. If you have made any changes in the contained submodes, you are asked if you want to apply them. If you select no, you are returned to the parent submode.
The following example shows how to return to the previous menu level:
sensor#
configure terminal
sensor(config)#
exit
sensor#
To start IP logging on a virtual sensor, use the iplog command in privileged EXEC mode. Use the no form of this command to disable all logging sessions on a virtual sensor, a particular logging session based on log-id, or all logging sessions.
iplog name ip-address [duration minutes] [packets numPackets] [bytes numBytes]
no iplog [log-id log-id | name name]
See the Syntax Description table.
EXEC
Administrator, Operator
|
|
---|---|
4.0(1) |
This command was introduced. |
If the no form of this command is specified without parameters, all logging is stopped.
If duration, packets, and bytes are entered, logging terminates whenever the first event occurs.
Note This command does not exist in Cisco IOS 12.0 or earlier.
The following example begins logging all packets containing 10.2.3.1 in the source or destination address on virtual sensor vs0:
sensor# iplog vs0 10.2.3.1
Logging started for virtual sensor vs0, IP address 10.2.3.1, Log ID 2342
WARNING: IP Logging will affect system performance.
sensor#
|
|
---|---|
iplog-status |
Displays a description of the available IP log contents. |
packet |
Displays or captures live traffic on an interface. |
To display a description of the available IP log contents, use the iplog-status command in privileged EXEC mode.
iplog-status
This command has no arguments or keywords.
No default behavior or values.
EXEC
Administrator, Operator, Viewer
|
|
---|---|
4.0(1) |
This command was introduced. |
4.0(2) |
The Status field was added to this command. |
When the log is created, the status is added
. If and when the first entry is inserted in the log, the status changes to started
. When the log is completed, because it has reached the packet count limit for example, the status changes to completed
.
Note This command does not exist in Cisco IOS 12.0 or earlier.
The following example displays the status of all IP logs:
sensor# iplog-status
Log ID: 2425
IP Address: 10.1.1.2
Virtual Sensor: vs0
Status: started
Start Time: 2003/07/30 18:24:18 2002/07/30 12:24:18 CST
Packets Captured: 1039438
Log ID: 2342
IP Address: 10.2.3.1
Virtual Sensor: vs0
Status: completed
Event ID: 209348
Start Time: 2003/07/30 18:24:18 2002/07/30 12:24:18 CST
End Time: 2003/07/30 18:34:18 2002/07/30 12:34:18 CST
sensor#
|
|
---|---|
iplog |
Starts IP logging on a virtual sensor. |
To display the contents of a logical file, use the more command in privileged EXEC mode.
more keyword
No default behavior or values.
EXEC
Administrator, Operator (current-config only), Viewer (current-config only)
|
|
---|---|
4.0(1) |
This command was introduced. |
IPS allows display of logical files only.
Hidden fields, such as passwords, are displayed for Administrators only.
Note The Cisco IOS 12.0 version of this command lets you display the contents of files stored on various partitions in the device.
The following example shows the output from the more command:
sensor# more current-config
! ------------------------------
! Version 5.0(0.26)
! Current configuration last modified Thu Feb 17 04:25:15 2005
! ------------------------------
display-serial
! ------------------------------
service analysis-engine
exit
! ------------------------------
service authentication
exit
! ------------------------------
service event-action-rules rules0
exit
! ------------------------------
service host
network-settings
host-ip 10.89.147.31/25,10.89.147.126
host-name sensor
access-list 0.0.0.0/0
login-banner-text This message will be displayed on user login.
exit
time-zone-settings
offset -360
--MORE--
To search the output of any more command, use the more begin command in privileged EXEC mode. This command begins unfiltered output of the more command with the first line that contains the regular expression specified.
more keyword | begin regular-expression
No default behavior or values.
EXEC
Administrator, Operator (current-config only), Viewer (current-config only)
|
|
---|---|
4.0(1) |
This command was introduced. |
4.0(2) |
The begin extension of the more command was introduced. |
The regular-expression argument is case sensitive and allows for complex matching requirements.
The following example shows how to search the more command output beginning with the regular expression "ip":
sensor# more current-config | begin ip
host-ip 10.89.147.31/25,10.89.147.126
host-name sensor
access-list 0.0.0.0/0
login-banner-text This message will be displayed on user login.
exit
time-zone-settings
offset -360
standard-time-zone-name CST
exit
exit
! ------------------------------
service interface
exit
! ------------------------------
service logger
exit
! ------------------------------
service network-access
user-profiles mona
enable-password foobar
exit
exit
! ------------------------------
service notification
--MORE--
To filter the more command output so that it excludes lines that contain a particular regular expression, use the more exclude command in privileged EXEC mode.
more keyword | exclude regular-expression
No default behavior or values.
EXEC
Administrator, Operator (current-config only), Viewer (current-config only)
|
|
---|---|
4.0(1) |
This command was introduced. |
4.0(2) |
The exclude extension of the more command was added. |
The regular-expression argument is case sensitive and allows for complex matching requirements.
The following example shows how to search the more command output excluding the regular expression "ip":
sensor# more current-config | exclude ip
! ------------------------------
! Version 5.0(0.26)
! Current configuration last modified Thu Feb 17 04:25:15 2005
! ------------------------------
display-serial
! ------------------------------
service analysis-engine
exit
! ------------------------------
service authentication
exit
! ------------------------------
service event-action-rules rules0
exit
! ------------------------------
service host
network-settings
host-name sensor
access-list 0.0.0.0/0
login-banner-text This message will be displayed on user login.
exit
time-zone-settings
offset -360
standard-time-zone-name CST
--MORE--
To filter the more command output so that it displays only lines that contain a particular regular expression, use the more include command in privileged EXEC mode.
more keyword | include regular-expression
No default behavior or values.
EXEC
Administrator, Operator (current-config only), Viewer (current-config only)
|
|
---|---|
4.0(1) |
This command was introduced. |
4.0(2) |
The include extension of the more command was added. |
The regular-expression argument is case sensitive and allows for complex matching requirements.
The following example shows how to search the more command output to include only the regular expression "ip":
sensor# more current-config | include ip
host-ip 10.89.147.31/25,10.89.147.126
sensor#
To display or capture live traffic on an interface, use the packet command in EXEC mode. Use the display option to dump live traffic or a previously captured file output directly to the screen. Use the capture option to capture the libpcap output into a local file. There is only one local file storage location, subsequent capture requests overwrite the existing file. You can copy the local file off the machine using the copy command with the packet-file keyword. You can view the local file using the display packet-file option. Use the info option to display information about the local file, if any. Use the packet display iplog id [verbose] [expression expression] to display iplogs.
packet display interface-name [snaplen length] [count count] [verbose] [expression expression]
packet display packet-file [verbose] [expression expression]
packet display iplog id [verbose] [expression expression] vlan and
packet capture interface-name [snaplen length] [count count] [expression expression]
packet display file-info
See the Syntax Description table.
EXEC
Administrator, Operator, Viewer (display only)
|
|
---|---|
5.0(1) |
This command was introduced. |
Storage is available for one local file. The size of this file varies depending on the platform. If possible, a message is displayed if the maximum file size is reached before the requested packet count is captured. Only one user can use the packet capture interface-name command at a time. A second user request results in an error message containing information about the user executing the capture. A configuration change involving the interface can result in abnormal termination of any packet command running on that interface.
Note The command does not exist in Cisco IOS 12.0 or earlier.
Note If you use the expression option when monitoring packets with VLAN headers, the expression does not match properly unless vlan and is added to the beginning of the expression. For example, packet display iplog 926299444 verbose expression icmp Will NOT show ICMP packets; packet display iplog 926299444 verbose expression vlan and icmp WILL show ICMP packets. It is often necessary to use expression vlan and on the IDSM2 and IPS appliance interfaces connected to trunk ports.
Press Ctrl-C to terminate the live display or file capture.
The expression syntax is described in the ethereal-filter man page.
The file-info displays:
Captured by: user:id, Cmd: cliCmd
Start: yyyy/mm/dd hh:mm:ss zone, End: yyyy/mm/dd hh:mm:ss zone or in-progress
Where
user = Username of user initiating capture,
id = User's CLI ID,
cliCmd = Command entered to perform the capture.
The following example displays the live traffic occurring on fastethernet 0/0:
sensor# packet display fastethernet0/0
Warning This command will cause significant performance degradation.
Executing command: tethereal -i fastethernet0/0
0.000000 10.89.147.56 -> 64.101.182.20 SSH Encrypted response packet len=56
0.000262 64.101.182.20 -> 10.89.147.56 TCP 33053 > ssh [ACK] Seq=3844631470 Ack=2972370007 Win=9184 Len=0
0.029148 10.89.147.56 -> 64.101.182.20 SSH Encrypted response packet len=224
0.029450 64.101.182.20 -> 10.89.147.56 TCP 33053 > ssh [ACK] Seq=3844631470 Ack=2972370231 Win=9184 Len=0
0.030273 10.89.147.56 -> 64.101.182.20 SSH Encrypted response packet len=224
0.030575 64.101.182.20 -> 10.89.147.56 TCP 33053 > ssh [ACK] Seq=3844631470 Ack=2972370455 Win=9184 Len=0
0.031361 10.89.147.56 -> 64.101.182.20 SSH Encrypted response packet len=224
0.031666 64.101.182.20 -> 10.89.147.56 TCP 33053 > ssh [ACK] Seq=3844631470 Ack=2972370679 Win=9184 Len=0
0.032466 10.89.147.56 -> 64.101.182.20 SSH Encrypted response packet len=224
0.032761 64.101.182.20 -> 10.89.147.56 TCP 33053 > ssh [ACK]
The following example displays information about the stored capture file:
sensor# packet display file-info
Captured by: raboyd:5292, Cmd: packet capture fastethernet0/0
Start: 2004/01/07 11:16:21 CST, End: 2004/01/07 11:20:35 CST
|
|
---|---|
iplog |
Starts IP logging on a virtual sensor. |
iplog-status |
Displays a description of the available IP log contents. |
To update your password on the local sensor, use the password command in global configuration mode. The administrator can also use the password command to change the password for an existing user. The administrator can use the no form of the command to disable a user account.
password
Administrator syntax: password [name [newPassword]]
no password [name]
The cisco account default password is cisco.
Global configuration
Administrator, Operator (current user's password only), Viewer (current user's password only)
|
|
---|---|
4.0(1) |
This command was introduced. |
Use the password command to update the current user's login password. The administrator can also use this command to modify the password for an existing user. The administrator is not prompted for the current password in this case.
You receive an error if you try to disable the last administrator account. Use the password command to reenable a disabled user account and reset the user password.
The password is protected in IPS.
Note The Cisco IOS 12.0 password command lets you enter the new password in the clear on the password line.
The following example shows how to modify the current user's password:
sensor(config)# password
Enter Old Login Password: **********
Enter New Login Password: ******
Re-enter New Login Password: ******
sensor(config)#
The following example modifies the password for the user tester
. Only Administrators can execute this command:
sensor(config)# password tester
Enter New Login Password: ******
Re-enter New Login Password: ******
sensor(config)#
|
|
---|---|
username |
Creates users on the local sensor. |
To diagnose basic network connectivity, use the ping command in privileged EXEC mode.
ping address [count]
address |
IP address of the system to ping. |
count |
Number of echo requests to send. If no value is entered, four requests are sent. The valid range is 1 to 10000. |
See the Syntax Description table.
EXEC
|
|
---|---|
4.0(1) |
This command was introduced. |
Administrator, Operator, Viewer
This command is implemented using the ping command provided by the operating system. The output from the command varies slightly between operating systems.
The following example shows the output of the ping command for Solaris systems:
sensor# ping 10.1.1.1
PING 10.1.1.1: 32 data bytes
40 bytes from 10.1.1.1: icmp_seq=0. time=0. ms
40 bytes from 10.1.1.1: icmp_seq=1. time=0. ms
40 bytes from 10.1.1.1: icmp_seq=2. time=0. ms
40 bytes from 10.1.1.1: icmp_seq=3. time=0. ms
----10.1.1.1 PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0
sensor#
The following example shows the output of the ping command for Linux systems:
sensor# ping 10.1.1.1 2
PING 10.1.1.1 from 10.1.1.2 : 32(60) bytes of data.
40 bytes from 10.1.1.1: icmp_seq=0 ttl=255 time=0.2 ms
40 bytes from 10.1.1.1: icmp_seq=1 ttl=255 time=0.2 ms
--- 10.1.1.1 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.2/0.2/0.2 ms
sensor#
The following example shows the output for an unreachable address:
sensor#
ping 172.21.172.1
PING 172.21.172.1 (172.21.172.1) from 10.89.175.50 : 56(84) bytes of data.
—-172.21.172.1 ping statistics—-
5 packets transmitted, 0 packets received, 100% packet loss
sensor#
To modify the privilege level for an existing user, use the privilege command in global configuration mode. You can also specify the privilege while creating a user with the username command.
privilege user name [administrator | operator | viewer]
name |
Specifies the users's name. A valid username is 1 to 64 characters in length. The username must begin with an alphanumeric character, otherwise all characters except spaces are accepted. |
No default behavior or values.
Global configuration
Administrator
|
|
---|---|
4.0(1) |
This command was introduced. |
Use the command to modify the privilege for a user.
Note This command does not exist in Cisco IOS 12.0 or earlier.
The following example changes the privilege of the user "tester" to operator.
sensor(config)# privilege user tester operator
Warning: The privilege change does not apply to current CLI sessions. It will be applied to subsequent logins.
sensor(config)#
|
|
---|---|
username |
Creates users on the local sensor. |
To reimage the application partition with the application image stored on the recovery partition, use the recover command in privileged EXEC mode. The sensor is rebooted multiple times and most configuration—except for network, access list, and time parameters—is reset to the default settings.
More specifically, the following settings are maintained after a local recovery using the "recover application-partition" command: Network Settings (IP Address, Netmask, Default Gateway, Hostname, and Telnet (enabled/disabled)); Access List Entries/ACL0 Settings (IP Address and Netmask); and Time Settings (Offset and Standard Time Zone Name); the rest of the parameters are reset to the default settings.
recover application-partition
application-partition |
Reimages the application partition. |
No default behavior or values.
Global configuration
|
|
---|---|
4.0(1) |
This command was introduced. |
Administrator
Valid answers to the continue with recover question are yes or no. Y or N are not valid responses.
Shutdown begins immediately after the command is executed. Because shutdown may take a little time, you may continue to access CLI commands (access is not denied), but access is terminated without warning. If necessary, a period (.) will be displayed on the screen once a second to indicate progress while the applications are shutting down.
Note This command does not exist in Cisco IOS 12.0 or earlier.
The following example reimages the application partition using the version 4.0(1)S29 image stored on the recovery partition:
sensor(config)#
recover application-partition
Warning: Executing this command will stop all applications and re-image the node to
version 5.0(1)Sx. All configuration changes except for network settings will be reset to
default.
Continue with recovery? []:
yes
Request Succeeded
sensor(config)#
To shut down the applications running on the sensor and reboot the appliance, use the reset command in privileged EXEC mode. If the powerdown option is included, the appliance is powered off if possible or left in a state where the power can be turned off.
reset [powerdown]
powerdown |
This option causes the sensor to power off after the applications are shutdown. |
No default behavior or values.
EXEC
|
|
---|---|
4.0(1) |
This command was introduced. |
Administrator
Valid answers to the continue with reset question are yes or no. Y or N are not valid responses.
Shutdown begins immediately after the command is executed. Access to the CLI commands is not denied during the shutdown, however, an open session is terminated without warning as soon as the shutdown is completed. If necessary, a period (.) will be displayed on the screen once a second to indicate progress while the applications are shutting down.
Note This command does not exist in Cisco IOS 12.0 or earlier.
The following example reboots the sensor:
sensor#
reset
Warning: Executing this command will stop all applications and reboot the node.
Continue with reset? []:
yes
sensor#
To enter configuration menus for various sensor services, use the service command in global configuration mode. Use the default form of the command to reset the entire configuration for the application back to factory defaults.
service {authentication | analysis-engine | event-action-rules name | host | interface | logger | network-access | notification | signature-definition name | ssh-known-hosts | trusted-certificate | web-server}
default service {authentication | analysis-engine | host | interface | logger | network-access | notification | ssh-known-hosts | trusted-certificate | web-server}
No default behavior or values.
Global configuration
Administrator, Operator, Viewer (display only)
|
|
---|---|
4.0(1) |
This command was introduced. |
5.0(1) |
The default keyword was added. Notification application support was added. |
This command lets you configure service-specific parameters. The items and menus in this configuration are service dependent and are built dynamically based on the configuration retrieved from the service when the command is executed.
The command mode is indicated on the command prompt by the name of the service. For example, service authentication has the following prompt:
sensor(config-aut)#
This command is IPS-specific.
Note This command does not exist in Cisco IOS 12.0 or earlier.
Within the service event-action-rules and service signature-definition modes, you can create variables and configure rules to filter events. If you use a variable in a filter, you must use a dollar sign ($SIG1) in front of the variable to indicate that the string you have entered represents a variable.
To enter more than one IP address, use a comma (no space) between the addresses. An IP address range can be expressed in the form A.B.C.D/b, where A.B.C.D represents an IP address and b represents the number of low-order bits that are masked in the IP address to specify the range. For example, the value 10.1.0.0/8 indicates an IP address of 10.1.0.0 with the lower 8 bits masked off to form a range of 10.1.0.0-10.1.0.255. Partial IP addresses can be used as part of the v4 IP address range when the allowPartialInput attribute is set to true. Because the range values are inclusive, the range 10.2-10.3 is equivalent to 10.2.0.0-10.3.255.255. The data for a range type can also be a set of ranges. A set of ranges consists of two or more ranges separated by commas—for example, 10.1.9.20-10.1.9.30,10.1.10.40-10.1.10.50,10.2-10.3.
A configuration can only be deleted if it is not assigned to a virtual sensor.
Note This command does not exist in Cisco IOS 12.0 or earlier.
The following command enters the configuration mode for the authentication service:
sensor(config)# service authentication
sensor(config-aut)#
The following command enters the configuration mode for the analysis engine service:
sensor(config)# service analysis-engine
sensor(config-ana)#
The following command enters the configuration mode for the event action rules service:
sensor(config)# service event-action-rules rules0
sensor(config-rul)#
The following command enters the configuration mode for the host service:
sensor(config)# service host
sensor(config-hos)#
The following command enters the configuration mode for the interface service:
sensor(config)# service interface
sensor(config-int)#
The following command enters the configuration mode for the logger service:
sensor(config)# service logger
sensor(config-log)#
The following command enters the configuration mode for the ARC service:
sensor(config)# service network-access
sensor(config-net)#
The following command enters the configuration mode for the SNMP notification service:
sensor(config)# service notification
sensor(config-not)#
The following command enters the configuration mode for the signature definition service:
sensor(config)# service signature-definition sig0
sensor(config-sig)#
The following command enters the configuration mode for the SSH known hosts service:
sensor(config)# service ssh-known-hosts
sensor(config-ssh)#
The following command enters the configuration mode for the trusted certificate service:
sensor(config)# service trusted-certificate
sensor(config-tru)#
The following command enters the configuration mode for the web server service:
sensor(config)# service web-server
sensor(config-web)#
To configure basic sensor configuration, use the setup command in privileged EXEC mode.
setup
This command has no arguments or keywords.
hostname sensor
IP interface 10.1.9.201/24,10.1.9.1
telnet-server disabled
web-server port 443
summer time disabled
If summer time is enabled by the user, the defaults are as follows:
•Summertime type Recurring
•Start Month april
•Start Week first
•Start Day sunday
•Start Time 02:00:00
•End Month october
•End Week last
•End Day sunday
•End Time 02:00:00
•Offset 60
System timezone defaults:
•Timezone UTC
•UTC Offset 0
EXEC
Administrator
|
|
---|---|
4.0(2) |
Added configuration of access lists and time settings. |
5.1(1) |
Added configuration of inline vlan pairs and virtual sensor settings. |
When you type the setup command, an interactive dialog called the System Configuration Dialog appears on the system console screen. The System Configuration Dialog guides you through the configuration process.
The values shown in brackets next to each prompt are the default values last set.
You must run through the entire System Configuration Dialog until you come to the item that you want to change. To accept default settings for items that you do not want to change, press Enter.
To return to the EXEC prompt without making changes and without running through the entire System Configuration Dialog, press Ctrl-C.
The facility also provides help text for each prompt. To access help text, type the question mark (?) at a prompt.
When you complete your changes, the configuration that was created during the setup session appears. You are prompted to save this configuration. If you type yes, the configuration is saved to disk. If you type no, the configuration is not saved and the process begins again. There is no default for this prompt; you must type either yes or no.
Valid ranges for configurable parameters are as follows:
IP Address/Netmask/Gateway: X.X.X.X/nn,Y.Y.Y.Y, where
X.X.X.X specifies the sensor IP address as a 32-bit address written as four octets separated by periods where X = 0-255.
nn specifies the number of bits in the netmask.
Y.Y.Y.Y specifies the default gateway as a 32-bit address written as four octets separated by periods where Y = 0-255.
Host Name: Case sensitive character string, up to 256 characters. Numbers, "_" and "-" are valid, spaces are not accepted.
Enter the clock settings in setup mode only if the system is NOT using NTP. NTP commands are provided separately.
You can configure daylight savings time either in recurring mode or date mode. If you select recurring mode, the start and end days are entered based on week, day, month, and time. If you select date mode, the start and end days are entered based on month, day, year, and time. Selecting disable turns off daylight savings time.
Table 2-1 shows the clock setting parameters.
You can also edit the default virtual sensor, vs0. You can assign promiscuous, inline pairs, and/or inline VLAN pairs to the virtual sensor, which in turn enables the assigned interfaces. After setup is complete, the virtual sensor is configured to monitor traffic.
The following example shows the setup command and the System Configuration program:
sensor# setup
--- System Configuration Dialog ---
At any point you may enter a question mark '?' for help.
User ctrl-c to abort configuration dialog at any prompt.
Default settings are in square brackets '[]'.
Current Configuration:
service host
network-settings
host-ip 172.21.172.25/8,172.21.172.1
host-name sensor
telnet-option disabled
access-list 10.0.0.0/24
access-list 172.0.0.0/24
ftp-timeout 300
login-banner-text
exit
time-zone-settings
offset 0
standard-time-zone-name UTC
exit
summertime-option disabled
ntp-option disabled
exit
service web-server
port 443
exit
service interface
physical-interfaces GigbitEthernet0/0
admin-state enabled
exit
exit
physical-interfaces GigbitEthernet1/0
admin-state enabled
subinterface-type inline-vlan-pair
subinterface 3
description Created via setup by user cisco
vlan1 5
vlan2 6
exit
exit
exit
service analysis-engine
virtual-sensor vs0
physical-interface GigabitEthernet0/0
physical-interface GigabitEthernet1/0 subinterface-number 3
exit
exit
Current time: Wed May 5 10:25:35 2004
Setup Configuration last modified: Mon May 3 15:34:30 2004
Continue with configuration dialog?[yes]:
Enter host name[sensor]:
Enter IP interface[172.21.172.25/8,172.21.172.1]:
Enter telnet-server status[enabled]:
Enter web-server port[8080]: 80
Modify current access list? [no]: yes
Current access list entries:
[1] 10.0.0.0/24
[2] 172.0.0.0/24
Delete: 1
Delete:
Permit: 173.0.0.0/24
Permit:
Modify system clock settings? [no]: yes
Use NTP? [yes] no
Modify summer time settings? [no]: yes
Recurring, Date or Disable[recurring]:
Start Month[apr]:
Start Week[1]:
Start Day[sun]:
Start Time[02:00:00]:
End Month[oct]:
End Week[last]:
End Day[sun]:
End Time[02:00:00]:
DST Zone[]: CDT
Offset[60]:
Modify system timezone? [no]: yes
Timezone[UTC]: CST
GMT Offset[-360]
Modify virtual sensor "vs0" configuration?[no]: yes
Current interface configuration
Command control: GigabitEthernet0/1
Unused:
GigabitEthernet1/1
GigabitEthernet2/0
GigabitEthernet2/1
Promiscuous:
GigabitEthernet0/0
Inline:
None
Inline Vlan Pair:
GigabitEthernet1/0 : 3; Vlans: 5, 6
Delete Promiscuous interfaces?[no]:
Delete Inline Vlan Pairs? [no] yes
Inline Vlan Pair Interfaces:
[1] GigabitEthernet1/0
Interface to modify: 1
Inline Vlan Pairs for GigabitEthernet1/0:
[1] Subinterface: 3; Vlans: 5, 6
Delete: 1
Delete:
Delete Inline Vlan Pairs?[no]:
Add Promiscuous interfaces?[no]:
Add Inline pairs?[no]: yes
Pair name: test
Description[Created via setup by user cisco]:
Interface1[]: GigabitEthernet2/0
Interface2[]: GigabitEthernet2/1
Pair name:
Add Inline Vlan Pairs?[no]: yes
Available Interfaces:
[1] GigabitEthernet1/0
[2] GigabitEthernet1/1
Interface to modify: 2
Inline Vlan Pairs for GigabitEthernet1/1:
None
Subinterface number: 1
Description[Created via setup by user cisco]:
Vlan1[]: 1
Vlan2[]: 2
Subinterface number:
Add Inline Vlan Pairs?[no]:
The following configuration was entered.
service host
network-settings
host-ip 172.21.172.25/8,172.21.172.1
host-name sensor
telnet-option enabled
access-list 172.0.0.0/24
access-list 173.0.0.0/24
ftp-timeout 300
login-banner-text
exit
time-zone-settings
offset -360
standard-time-zone-name CST
exit
summertime-option recurring
offset 60
summertime-zone-name CDT
start-summertime
month april
week-of-month first
day-of-week sunday
time-of-day 02:00:00
exit
end-summertime
month october
week-of-month last
day-of-week sunday
time-of-day 02:00:00
exit
exit
ntp-option disabled
exit
service web-server
port 80
exit
service interface
physical-interfaces GigabitEthernet0/0
admin-state enabled
exit
physical-interfaces GigabitEthernet1/1
admin-state enabled
subinterface-type inline-vlan-pair
subinterface 1
description Created via setup by user cisco
vlan1 1
vlan2 2
exit
exit
exit
physical-interfaces GigabitEthernet2/0
admin-state enabled
exit
physical-interfaces GigabitEthernet2/1
admin-state enabled
exit
inline-interfaces test
description Created via setup by user cisco
interface1 GigabitEthernet2/0
interface2 GigabitEthernet2/1
exit
exit
service analysis-engine
virtual-sensor vs0
physical-interface GigabitEthernet0/0
physical-interface GigabitEthernet1/1 subinterface-number 1
logical-interface test
exit
exit
[0] Go to the command prompt without saving this config.
[1] Return back to the setup without saving this config.
[2] Save this configuration and exit.
Enter your selection [2]:
Configuration Saved.
Modify system date and time? [no] yes
Local Date[]: 2003-01-18
Local Time[4:33:49]: 10:33:49
System Time Updated successfully
sensor#
To search the output of certain show commands, use the show begin command in privileged EXEC mode. This command begins unfiltered output of the show command with the first line that contains the regular expression specified.
show [configuration | events | settings | tech-support] | begin regular-expression
| |
A vertical bar indicates that an output processing specification follows. |
regular-expression |
Any regular expression found in show command output. |
No default behavior or values.
EXEC
Administrator, Operator (current-config only), Viewer (current-config only)
|
|
---|---|
4.0(1) |
This command was introduced. |
4.0(2) |
The begin extension of the show command was added. |
5.1(1) |
Added tech-support option. |
The regular-expression argument is case sensitive and allows for complex matching requirements.
The following example shows the output beginning with the regular expression "ip":
sensor# show configuration | begin ip
host-ip 10.89.147.31/25,10.89.147.126
host-name sensor
access-list 0.0.0.0/0
login-banner-text This message will be displayed on user login.
exit
time-zone-settings
offset -360
standard-time-zone-name CST
exit
exit
! ------------------------------
service interface
exit
! ------------------------------
service logger
exit
! ------------------------------
service network-access
user-profiles mona
enable-password foobar
exit
exit
! ------------------------------
service notification
--MORE--
To display the system clock, use the show clock command in privileged EXEC mode.
show clock [detail]
detail |
(Optional) Indicates the clock source (NTP or system) and the current summertime setting (if any). |
No default behavior or values.
EXEC
Administrator, Operator, Viewer
|
|
---|---|
4.0(1) |
This command was introduced. |
The system clock keeps an "authoritative" flag that indicates whether the time is authoritative (believed to be accurate). If the system clock has been set by a timing source such as NTP, the flag is set. Table 2-2 shows the authoritative flags.
|
|
---|---|
* |
Time is not authoritative. |
(blank) |
Time is authoritative. |
. |
Time is authoritative, but NTP is not synchronized. |
The following example shows NTP configured and synchronized:
sensor# show clock detail
12:30:02 CST Tues Dec 19 2002
Time source is NTP
Summer time starts 03:00:00 CDT Sun Apr 7 2003
Summer time ends 01:00:00 CST Sun Oct 27 2003
sensor#
The following example shows no time source configured:
sensor# show clock
*12:30:02 EST Tues Dec 19 2002
sensor#
The following example shows no time source is configured:
sensor# show clock detail
*12:30:02 CST Tues Dec 19 2002
No time source
Summer time starts 02:00:00 CST Sun Apr 7 2003
Summer time ends 02:00:00 CDT Sun Oct 27 2003
See the more current-config command under the more command.
|
|
---|---|
4.0(2) |
This command was added. |
To display the local event log contents, use the show events command in privileged EXEC mode.
show events [{[alert [informational] [low] [medium] [high] [include-traits traits] [exclude-traits traits] | error [warning] [error] [fatal] | NAC | status}] [hh:mm:ss [month day [year]] | past hh:mm:ss]
No default behavior or values.
EXEC
Administrator, Operator, Viewer
The show events command displays the requested event types beginning at the requested start time. If no start time is entered, the selected events are displayed beginning at the current time. If no event types are entered, all events are displayed. Events are displayed as a live feed. You can cancel the live feed by the pressing Ctrl-C.
Use the regular expression | include shunInfo with the show events command to view the blocking information, including source address, for the event.
Note This command does not exist in Cisco IOS 12.0 or earlier.
The following example displays block requests beginning at 10:00 a.m. on December 25, 2004:
sensor#
show events NAC 10:00:00 Dec 25 2004
The following example displays error and fatal error messages beginning at the current time:
sensor#
show events error fatal error
The following example displays all events beginning at 10:00 a.m. on December 25, 2004:
sensor#
show events 10:00:00 Dec 25 2004
The following example displays all events beginning 30 seconds in the past:
sensor#
show events past 00:00:30
The following output is taken from the XML content:
evAlert: eventId=1025376040313262350 severity=high
originator:
deviceName: sensor1
appName: sensorApp
time: 2002/07/30 18:24:18 2002/07/30 12:24:18 CST
signature: sigId=4500 subSigId=0 version=1.0 IOS Embedded SNMP Community Names
participants:
attack:
attacker: proxy=false
addr: 132.206.27.3
port: 61476
victim:
addr: 132.202.9.254
port: 161
protocol: udp
To filter the show command output so that it excludes lines that contain a particular regular expression, use the show exclude command in privileged EXEC mode.
show [configuration | events | settings | tech-support] | exclude regular-expression
| |
A vertical bar indicates that an output processing specification follows. |
regular-expression |
Any regular expression found in show command output. |
No default behavior or values.
EXEC
Administrator, Operator (current-config only), Viewer (current-config only)
|
|
---|---|
4.0(1) |
This command was introduced. |
4.0(2) |
The exclude extension of the show command was added. |
5.1(1) |
Added tech-support option. |
The regular-expression argument is case sensitive and allows for complex matching requirements.
The following example shows the regular expression "ip" being excluded from the output:
sensor# show configuration | exclude ip
! ------------------------------
! Version 5.0(0.26)
! Current configuration last modified Thu Feb 17 04:25:15 2005
! ------------------------------
display-serial
! ------------------------------
service analysis-engine
exit
! ------------------------------
service authentication
exit
! ------------------------------
service event-action-rules rules0
exit
! ------------------------------
service host
network-settings
host-name sensor
access-list 0.0.0.0/0
login-banner-text This message will be displayed on user login.
exit
time-zone-settings
offset -360
standard-time-zone-name CST
--MORE-
To list the commands you have entered in the current menu, use the show history command in all modes.
show history
This command has no arguments or keywords.
No default behavior or values.
All modes
Administrator, Operator, Viewer
|
|
---|---|
4.0(1) |
This command was introduced. |
The show history command provides a record of the commands you have entered in the current menu. The number of commands that the history buffer records is 50.
The following example shows the command record for the show history command:
sensor#
show history
show users
show events
sensor#
To filter the show command output so that it displays only lines that contain a particular regular expression, use the show include command in privileged EXEC mode.
show [ configuration | events | settings | tech-support] | include regular-expression
| |
A vertical bar indicates that an output processing specification follows. |
regular-expression |
Any regular expression found in show command output. |
No default behavior or values.
EXEC
Administrator, Operator (current-config only), Viewer (current-config only)
|
|
---|---|
4.0(1) |
This command was introduced. |
4.0(2) |
The include extension of the show command was added. |
5.1(1) |
Added tech-support option. |
The regular-expression argument is case sensitive and allows for complex matching requirements.
The show settings command output also displays header information for the matching request so that the context of the match can be determined.
The following example shows only the regular expression "ip" being included in the output:
sensor# show configuration | include ip
host-ip 10.89.147.31/25,10.89.147.126
sensor#
To display statistics for all system interfaces, use the show interfaces command in privileged EXEC mode. This command displays show interfaces management, show interfaces fastethernet, and show interface gigabitethernet.
show interfaces [clear]
show interfaces {FastEthernet | GigabitEthernet | Management} [slot/port]
No default behavior or values.
EXEC
Administrator, Operator, Viewer
|
|
---|---|
5.0(1) |
show interfaces group, show interfaces sensing, and show interfaces command-control were removed. |
This command displays statistics for the command control and sensing interfaces. The clear option also clears statistics that can be reset.
The following example shows the interface statistics:
sensor# show interfaces
Interface Statistics
Total Packets Received = 0
Total Bytes Received = 0
Missed Packet Percentage = 0
Current Bypass Mode = Auto_off
MAC statistics from interface GigabitEthernet0/0
Media Type = TX
Missed Packet Percentage = 0
Inline Mode = Unpaired
Pair Status = N/A
Link Status = Down
Link Speed = N/A
Link Duplex = N/A
Total Packets Received = 0
Total Bytes Received = 0
Total Multicast Packets Received = 0
Total Broadcast Packets Received = 0
Total Jumbo Packets Received = 0
Total Undersize Packets Received = 0
Total Receive Errors = 0
Total Receive FIFO Overruns = 0
Total Packets Transmitted = 0
Total Bytes Transmitted = 0
Total Multicast Packets Transmitted = 0
--MORE--
To display PEP information, use the show inventory command in privileged EXEC mode. This command displays the UDI information that consists of PID, VID and SN of the sensor.
show inventory
This command has no arguments or keywords.
No default behavior or values.
EXEC
Administrator, Operator, Viewer
|
|
---|---|
5.0(1) |
This command was introduced. |
This is same as the show inventory Cisco IOS command required by Cisco PEP policy. The output of show inventory is different depending on the hardware.
The following example shows a sample show inventory command output:
sensor# show inventory
NAME: "Chassis", DESCR: "Chasis-4240"
PID: 4240-515E , VID: V04, SN: 639156
NAME: "slot 0", DESCR: "4 port I/O card"
PID: 4240-4IOE , VID: V04, SN: 4356785466
sensor#
To display your current level of privilege, use the show privilege command in privileged EXEC mode.
show privilege
This command has no arguments or keywords.
No default behavior or values.
EXEC
Administrator, Operator, Viewer
|
|
---|---|
4.0(1) |
This command was introduced. |
Use this command to display your current level of privilege. A privilege level can only be modified by the administrator. See the username command for more information.
The following example shows the privilege of the user:
sensor# show privilege
Current privilege level is viewer
sensor#
|
|
---|---|
username |
Creates users on the local sensor. |
To display the contents of the configuration contained in the current submode, use the show settings command in any service command mode.
show settings [terse]
terse |
Displays a terse version of the output. |
No default behavior or values.
All service command modes.
Administrator, Operator, Viewer (only presented with the top-level command tree)
|
|
---|---|
4.0(1) |
This command was introduced. |
4.0(2) |
The terse keyword was added. |
This command is IPS-specific.
Note This command does not exist in Cisco IOS 12.0 or earlier.
The following example shows the output for the show settings command in ARC configuration mode.
Note Network Access Controller is now known as Attack Response Controller (ARC). Although the service has a new name, the change is not reflected in the IPS 5.1 CLI. You will still see network-access and nac throughout the CLI.
sensor# configure terminal
sensor(config)# service network-access
sensor(config-net)# show settings
general
-----------------------------------------------
log-all-block-events-and-errors: true <defaulted>
enable-nvram-write: false <defaulted>
enable-acl-logging: false <defaulted>
allow-sensor-block: true default: false
block-enable: true <defaulted>
block-max-entries: 250 <defaulted>
max-interfaces: 250 <defaulted>
master-blocking-sensors (min: 0, max: 100, current: 0)
-----------------------------------------------
-----------------------------------------------
never-block-hosts (min: 0, max: 250, current: 0)
-----------------------------------------------
-----------------------------------------------
never-block-networks (min: 0, max: 250, current: 0)
-----------------------------------------------
-----------------------------------------------
block-hosts (min: 0, max: 250, current: 0)
-----------------------------------------------
-----------------------------------------------
block-networks (min: 0, max: 250, current: 0)
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
user-profiles (min: 0, max: 250, current: 0)
-----------------------------------------------
-----------------------------------------------
cat6k-devices (min: 0, max: 250, current: 0)
-----------------------------------------------
-----------------------------------------------
router-devices (min: 0, max: 250, current: 0)
-----------------------------------------------
-----------------------------------------------
firewall-devices (min: 0, max: 250, current: 0)
-----------------------------------------------
-----------------------------------------------
sensor(config-net)#
The following example shows the show settings terse output for the signature definition submode.
sensor# configure terminal
sensor(config)# service signature-definition sig0
sensor(config-sig)# show settings terse
variables (min: 0, max: 256, current: 2)
-----------------------------------------------
<protected entry>
variable-name: WEBPORTS
variable-name: user2
-----------------------------------------------
application-policy
-----------------------------------------------
http-policy
-----------------------------------------------
http-enable: false <defaulted>
max-outstanding-http-requests-per-connection: 10 <defaulted>
aic-web-ports: 80-80,3128-3128,8000-8000,8010-8010,8080-8080,8888-8888,
24326-24326 <defaulted>
-----------------------------------------------
ftp-enable: true default: false
-----------------------------------------------
fragment-reassembly
-----------------------------------------------
ip-reassemble-mode: nt <defaulted>
-----------------------------------------------
stream-reassembly
-----------------------------------------------
tcp-3-way-handshake-required: true <defaulted>
tcp-reassembly-mode: strict <defaulted>
--MORE--
The following example shows the show settings filtered output. The command indicates the output should only include lines containing HTTP.
sensor# configure terminal
sensor(config)# service signature-definition sig0
sensor(config-sig)# show settings | include HTTP
Searching:
sig-string-info: Bagle.Q HTTP propagation (jpeg) <defaulted>
sig-string-info: Bagle.Q HTTP propagation (php) <defaulted>
sig-string-info: GET ftp://@@@:@@@/pub HTTP/1.0 <defaulted>
sig-name: IMail HTTP Get Buffer Overflow <defaulted>
sig-string-info: GET shellcode HTTP/1.0 <defaulted>
sig-string-info: ..%c0%af..*HTTP <defaulted>
sig-string-info: ..%c1%9c..*HTTP <defaulted>
sig-name: IOS HTTP Unauth Command Execution <defaulted>
sig-name: Null Byte In HTTP Request <defaulted>
sig-name: HTTP tunneling <defaulted>
sig-name: HTTP tunneling <defaulted>
sig-name: HTTP tunneling <defaulted>
sig-name: HTTP tunneling <defaulted>
sig-name: HTTP CONNECT Tunnel <defaulted>
sig-string-info: CONNECT.*HTTP/ <defaulted>
sig-name: HTTP 1.1 Chunked Encoding Transfer <defaulted>
sig-string-info: INDEX / HTTP <defaulted>
sig-name: Long HTTP Request <defaulted>
sig-string-info: GET \x3c400+ chars>? HTTP/1.0 <defaulted>
sig-name: Long HTTP Request <defaulted>
sig-string-info: GET ......?\x3c400+ chars> HTTP/1.0 <defaulted>
sig-string-info: /mod_ssl:error:HTTP-request <defaulted>
sig-name: Dot Dot Slash in HTTP Arguments <defaulted>
sig-name: HTTPBench Information Disclosure <defaulted>
--MORE--
To display the public RSA keys for the current user, use the show ssh authorized-keys command in privileged EXEC mode.
show ssh authorized-keys [id]
id |
1 to 256-character string uniquely identifying the authorized key. Numbers, "_" and "-" are valid; spaces and `?' are not accepted. |
No default behavior or values.
EXEC
Administrator, Operator, Viewer
|
|
---|---|
4.0(1) |
This command was introduced. |
Running this command without the optional ID displays a list of the configured IDs in the system. Running the command with a specific ID displays the key associated with the ID. This command is IPS-specific.
Note This command does not exist in Cisco IOS 12.0 or earlier.
The following example shows the list of SSH authorized keys:
sensor# show ssh authorized-keys
system1
system2
system3
system4
The following example shows the SSH key for system1:
sensor# show ssh authorized-keys system1
1023 37 660222729556609833380897067163729433570828686860008172017802434921804214207813035920829509 101701358480525039993932112503147452768378620911189986653716089813147922086044739911341369 642870682319361928148521864094557416306138786468335115835910404940213136954353396163449793 49705016792583146548622146467421997057
sensor#
|
|
---|---|
ssh authorized-key |
Adds a public key to the current user for a client allowed to use RSA authentication to log in to the local SSH server. |
To display the SSH server's host key and host key's fingerprint, use the show ssh server-key command in privileged EXEC mode.
show ssh server-key
This command has no arguments or keywords.
No default behavior or values.
EXEC
Administrator, Operator, Viewer
|
|
---|---|
4.0(1) |
This command was introduced. |
This command is IPS-specific.
Note This command does not exist in Cisco IOS 12.0 or earlier
The following example shows the output from the show ssh server-key command:
sensor# show ssh server-key
1024 35 144719237233791547030730646600884648599022074867561982783071499320643934
48734496072779375489584407249259840037709354850629125941930828428605183115777190
69953460097510388011424663818234783053872210554889384417232132153750963283322778
52374794118697053304026570851868326130246348580479834689461788376232451955011
MD5: F3:10:3E:BA:1E:AB:88:F8:F5:56:D3:A6:63:42:1C:11
Bubble Babble: xucis-hehon-kizog-nedeg-zunom-kolyn-syzec-zasyk-symuf-rykum-sexyx
sensor#
|
|
---|---|
ssh generate-key |
Changes the server host key used by the SSH server on the sensor. |
To display the known hosts table containing the public keys of remote SSH servers with which the sensor can connect, use the show ssh host-keys in privileged EXEC mode.
show ssh host-keys [ipaddress]
ipaddress |
32-bit address written as 4 octets separated by periods. X.X.X.X where X=0-255 |
No default behavior or values.
EXEC
Administrator, Operator, Viewer
|
|
---|---|
4.0(1) |
This command was introduced. |
4.1(1) |
Bubble Babble and MD5 output to the command were added. |
Running this command without the optional IP address ID displays a list of the IP addresses configured with public keys. Running the command with a specific IP address displays the key associated with the IP address. This command is IPS-specific.
Note This command does not exist in Cisco IOS 12.0 or earlier.
The following example shows the output of the show ssh host-keys command:
sensor# show ssh host-keys 10.1.2.3
1024 35 144719237233791547030730646600884648599022074867561982783071499320643934
48734496072779375489584407249259840037709354850629125941930828428605183115777190
69953460097510388011424663818234783053872210554889384417232132153750963283322778
52374794118697053304026570851868326130246348580479834689461788376232451955011
MD5: F3:10:3E:BA:1E:AB:88:F8:F5:56:D3:A6:63:42:1C:11
Bubble Babble: xucis-hehon-kizog-nedeg-zunom-kolyn-syzec-zasyk-symuf-rykum-sexyx
sensor#
|
|
---|---|
ssh host-key |
Adds an entry to the known hosts table. |
To display the requested statistics, use the show statistics command in privileged EXEC mode.
show statistics {analysis-engine | authentication | denied-attackers | event-server | event-store | host | logger | network-access | notification | sdee-server | transaction server | transaction-source | virtual-sensor | web-server} [clear]
No default behavior or values.
EXEC
Administrator, Operator, Viewer
|
|
---|---|
4.0(1) |
This command was introduced. |
5.0(1) |
analysis-engine, virtual-sensor, and denied-attackers were added. |
Note This command does not exist in Cisco IOS 12.0 or earlier.
The following example shows the authentication statistics:
sensor# show statistics authentication
General
totalAuthenticationAttempts = 9
failedAuthenticationAttempts = 0
sensor#
The following example shows the statistics for the Event Store:
sensor# show statistics event-store
Event store statistics
General information about the event store
The current number of open subscriptions = 1
The number of events lost by subscriptions and queries = 0
The number of queries issued = 1
The number of times the event store circular buffer has wrapped = 0
Number of events of each type currently stored
Debug events = 0
Status events = 129
Log transaction events = 0
Shun request events = 0
Error events, warning = 8
Error events, error = 13
Error events, fatal = 0
Alert events, informational = 0
Alert events, low = 0
Alert events, medium = 0
Alert events, high = 0
sensor#
The following example shows the logger statistics:
sensor# show statistics logger
The number of Log interprocessor FIFO overruns = 0
The number of syslog messages received = 27
The number of <evError> events written to the event store by severity
Fatal Severity = 0
Error Severity = 13
Warning Severity = 35
TOTAL = 48
The number of log messages written to the message log by severity
Fatal Severity = 0
Error Severity = 13
Warning Severity = 8
Timing Severity = 0
Debug Severity = 0
Unknown Severity = 26
TOTAL = 47
sensor#
The following example shows the ARC statistics:
sensor# show statistics network-access
Current Configuration
LogAllBlockEventsAndSensors = true
EnableNvramWrite = false
EnableAclLogging = false
AllowSensorBlock = false
BlockMaxEntries = 250
MaxDeviceInterfaces = 250
State
BlockEnable = true
sensor#
To display the current system status, use the show tech-support command in privileged EXEC mode.
show tech-support [page] [password] [destination-url destination url]
See Syntax Description table.
EXEC
Administrator
|
|
---|---|
4.0(1) |
This command was introduced. |
Note Cisco IOS version 12.0 does not support the destination portion of this command.
The exact format of the destination URL varies according to the file. You can select a filename, but it must be terminated by .html.
You can specify the following destination types:
•ftp:—Destination URL for FTP network server. The syntax for this prefix is: ftp:[[//username@location]/relativeDirectory]/filename or ftp:[[//username@location]//absoluteDirectory]/filename
•scp:—Destination URL for the SCP network server. The syntax for this prefix is: scp:[[//username@]location]/relativeDirectory]/filename or scp:[[//username@]location]//absoluteDirectory]/filename
The report contains HTML-linked output from the following commands:
•show interfaces
•show statistics network-access
•cidDump
The following example places the tech support output into the file ~csidsuser/reports/sensor1Report.html
. The path is relative to csidsuser's home account:
sensor#
show tech support destination-url
ftp://csidsuser@10.2.1.2/reports/sensor1Report.html password:*******
The following example places the tech support output into the file /absolute/reports/sensor1Report.html
:
sensor#
show tech support destination-url
ftp://csidsuser@10.2.1.2//absolute/reports/sensor1Report.html password:*******
To display the server's TLS certificate fingerprint, use the show tls fingerprint in privileged EXEC mode.
show tls fingerprint
This command has no arguments or keywords.
No default behavior or values.
EXEC
Administrator, Operator, Viewer
|
|
---|---|
4.0(1) |
This command was introduced. |
This command is IPS-specific.
Note This command does not exist in Cisco IOS 12.0 or earlier.
The following example shows the output of the show tls fingerprint command:
sensor# show tls fingerprint
MD5: 1F:94:6F:2E:38:AD:FB:2C:42:0C:AE:61:EC:29:74:BB
SHA1: 16:AC:EC:AC:9D:BC:84:F5:D8:E4:1A:05:C4:01:BB:65:7B:4F:FC:AA
sensor#
|
|
---|---|
tls generate-key |
Regenerates the server's self-signed X.509 certificate. |
To display the sensor's trusted hosts, use the show tls trusted-hosts command in privileged EXEC mode.
show tls trusted-hosts [id]
id |
1 to 32 character string uniquely identifying the authorized key. Numbers, "_" and "-" are valid; spaces and `?' are not accepted. |
No default behavior or values.
EXEC
Administrator, Operator, Viewer
|
|
---|---|
4.0(1) |
This command was introduced. |
Running this command without the optional ID displays a list of the configured IDs in the system. Running the command with a specific ID displays the fingerprint of the certificate associated with the ID.
This command is IPS-specific.
Note This command does not exist in Cisco IOS 12.0 or earlier
The following example shows the output from the show tls trusted-hosts command:
sensor# show tls trusted-hosts 172.21.172.1
MD5: 1F:94:6F:2E:38:AD:FB:2C:42:0C:AE:61:EC:29:74:BB
SHA1: 16:AC:EC:AC:9D:BC:84:F5:D8:E4:1A:05:C4:01:BB:65:7B:4F:FC:AA
sensor#
|
|
---|---|
tls trusted-host |
Adds a trusted host to the system. |
To display information about users currently logged in to the CLI, use the show users command in privileged EXEC mode:
show users [all]
all |
(Optional) List all user accounts configured on the system regardless of current login status. |
No default behavior or values.
EXEC
Administrator, Operator, Viewer (can only view their own logins)
|
|
---|---|
4.0(1) |
This command was introduced. |
4.1(1) |
Updated this command to display locked accounts. Limited viewer display for show users all. |
For the CLI, this command displays an ID, username, and privilege. An '*' next to the description indicates the current user. A username surrounded by parenthesis "( )" indicates that the account is locked. An account is locked if the user fails to enter the correct password in X subsequent attempts. Resetting the locked user's password with the password command unlocks an account.
The maximum number of concurrent CLI users allowed is based on platform.
Note The output for this command is different from the Cisco IOS 12.0 command.
The following example shows the output of the show users command:
sensor# show users
CLI ID User Privilege
1234 notheruser viewer
* 9802 curuser operator
5824 tester administrator
The following example shows user tester2's account is locked:
sensor# show users all
CLI ID User Privilege
1234 notheruser viewer
* 9802 curuser operator
5824 tester administrator
(tester2) viewer
foobar operator
The following example shows the show users all output for a viewer:
sensor# show users all
CLI ID User Privilege
* 9802 tester viewer
5824 tester viewer
|
|
---|---|
clear line |
Terminates another CLI session. |
To display the version information for all installed OS packages, signature packages, and IPS processes running on the system, use the show version command in privileged EXEC mode.
show version
This command has no arguments or keywords.
No default behavior or values.
EXEC
Administrator, Operator, Viewer
|
|
---|---|
4.0(1) |
This command was introduced. |
The output for the show version command is IPS-specific and differs from the output for the Cisco IOS command.
The license information follows the serial number and can be one of the following:
No license present
Expired license:
<expiration-date>
Valid license, expires:
<expiration-date>
Valid demo license, expires:
<expiration-date>
where <expiration-date> is the form dd-mon-yyyy, for example, 04-dec-2004.
Note The * before the upgrade history package name indicates the remaining version after a downgrade is performed. If no package is marked by *, no downgrade is available.
The following example shows the output for the show version command:
sensor# show version
Application Partition:
Cisco Intrusion Prevention System, Version 5.0(0.1)S91(0.1)
OS Version 2.4.26-IDS-smp-bigphys
Platform: IDS-4235
No license present
Sensor up-time is 6 days.
Using 701513728 out of 922509312 bytes of available memory (76% usage)
Using 527.6M out of 15.9G bytes of available disk space (3% usage)
Using 192.0k out of 31.0M bytes of available disk space (1% usage)
MainApp 2004_Aug_16_03.00 (Release) 2004-08-16T03:19:41-0500 Running
AnalysisEngine 2004_Aug_16_03.00 (Release) 2004-08-16T03:19:41-0500 Running
CLI 2004_Aug_16_03.00 (Release) 2004-08-16T03:19:41-0500
Upgrade History:
No upgrades installed
Recovery Partition Version 5.0.1.S91.0.1
sensor#
To add a public key to the current user for a client allowed to use RSA authentication to log in to the local SSH server, use the ssh authorized-key command in global configuration mode. Use the no form of this command to remove an authorized key from the system.
ssh authorized-key id key-modulus-length public-exponent public-modulus
no ssh authorized-key id
No default behavior or values.
Global configuration
Administrator, Operator, Viewer
|
|
---|---|
4.0(1) |
This command was introduced. |
This command adds an entry to the known hosts table for the current user. To modify a key the entry must be removed and recreated.
This command is IPS-specific.
Note This command does not exist in Cisco IOS 12.0 or earlier.
The following example shows how to add an entry to the known hosts table:
sensor(config)# ssh authorized-key system1 1023 37
660222729556609833380897067163729433570828686860008172017802434921804214207813035920829509
101701358480525039993932112503147452768378620911189986653716089813147922086044739911341369
642870682319361928148521864094557416306138786468335115835910404940213136954353396163449793
49705016792583146548622146467421997057
sensor(config)#
|
|
---|---|
ssh authorized-keys |
Displays the public RSA keys for the current user. |
To change the server host key used by the SSH server on the sensor, use the ssh generate-key command in privileged EXEC mode.
ssh generate-key
This command has no arguments or keywords.
No default behavior or values.
EXEC
Administrator
|
|
---|---|
4.0(1) |
This command was introduced. |
The displayed key fingerprint matches that displayed in the remote SSH client in future connections with this sensor if the remote client is using SSH protocol version 1.5.
This command is IPS-specific.
Note This command does not exist in Cisco IOS 12.0 or earlier.
The following example shows how to generate a new ssh server host key:
sensor# ssh generate-key
MD5: 49:3F:FD:62:26:58:94:A3:E9:88:EF:92:5F:52:6E:7B
Bubble Babble: xebiz-vykyk-fekuh-rukuh-cabaz-paret-gosym-serum-korus-fypop-huxyx
sensor#
|
|
---|---|
show ssh server-key |
Displays the SSH server's host key and host key's fingerprint. |
To add an entry to the known hosts table, use the ssh host-key command in global configuration mode. If the modulus, exponent, and length are not provided, the system displays the MD5 fingerprint and bubble babble for the requested IP address and allows you to add the key to the table. Use the no form of this command to remove an entry from the known hosts table.
ssh host-key ipaddress [key-modulus-length public-exponent public-modulus]
no ssh host-key ipaddress
No default behavior or values.
Global configuration
Administrator, Operator
|
|
---|---|
4.0(1) |
This command was introduced. |
The ssh host-key command adds an entry to the known hosts table. To modify a key for an IP address, the entry must be removed and recreated.
If the modulus, exponent, and length are not provided, the SSH server at the specified IP address is contacted to obtain the required key over the network. The specified host must be accessible at the moment the command is issued.
This command is IPS-specific.
Note This command does not exist in Cisco IOS 12.0 or earlier.
The following example shows how to add an entry to the known hosts table for 10.1.2.3:
sensor(config)# ssh host-key 10.1.2.3
1024 35 139306213541835240385332922253968814685684523520064131997839905113640120217816869696708721 704631322844292073851730565044879082670677554157937058485203995572114631296604552161309712 601068614812749969593513740598331393154884988302302182922353335152653860589163651944997842 874583627883277460138506084043415861927
sensor(config)#
The following example shows how to add an entry to the known hosts table for 10.1.2.3:
sensor(config)# ssh host-key 10.1.2.3
MD5 fingerprint is 49:3F:FD:62:26:58:94:A3:E9:88:EF:92:5F:52:6E:7B
Bubble Babble is xebiz-vykyk-fekuh-rukuh-cabaz-paret-gosym-serum-korus-fypop-huxyx
Would you like to add this to the known hosts table for this host? [yes]
sensor(config)#
|
|
---|---|
show ssh host-key |
Displays the known hosts table containing the public keys of remote SSH servers with which the sensor can connect. |
To modify terminal properties for a login session, use the terminal command in privileged EXEC mode.
terminal [length screen-length]
See Syntax Description table.
EXEC
Administrator, Operator, Viewer
|
|
---|---|
4.0(1) |
This command was introduced. |
The terminal length command sets the number of lines that are displayed before the --more--
prompt is displayed.
The following example sets the CLI to not pause between screens for multiple-screen displays:
sensor#
terminal length 0
sensor#
The following example sets the CLI to display 10 lines per screen for multiple-screen displays:
sensor#
terminal length 10
sensor#
To regenerate the server's self-signed X.509 certificate, use the tls generate-key in privileged EXEC mode. An error is returned if the host is not using a self-signed certificate.
tls generate-key
This command has no arguments or keywords.
No default behavior or values.
EXEC
Administrator
|
|
---|---|
4.0(1) |
This command was introduced. |
This command is IPS-specific.
Note This command does not exist in Cisco IOS 12.0 or earlier.
The following example shows how to generate the server's self-signed certificate:
sensor(config)# tls generate-key
MD5: 1F:94:6F:2E:38:AD:FB:2C:42:0C:AE:61:EC:29:74:BB
SHA1: 16:AC:EC:AC:9D:BC:84:F5:D8:E4:1A:05:C4:01:BB:65:7B:4F:FC:AA
sensor(config)#
|
|
---|---|
show tls fingerprint |
Displays the server's TLS certificate fingerprint. |
To add a trusted host to the system, use the tls trusted-host command in global configuration mode. Use the no form of the command to remove a trusted host certificate.
tls trusted-host ip-address ip-address [port port]
no tls trusted-host ip-address ip-address [port port]
no tls trusted-host id id
ip-address |
IP address of host to add or remove. |
port |
(Optional) Port number of host to contact. The default is port 443. |
See Syntax Description table.
Global configuration
Administrator, Operator
|
|
---|---|
4.0(1) |
This command was introduced. |
4.0(2) |
Added optional port. Added no command to support removal based on ID. |
This command retrieves the current fingerprint for the requested host/port and displays the result. You can choose to accept or reject the fingerprint based on information retrieved directly from the host being requested to add.
Each certificate is stored with an identifier field. For IP address and default port, the identifier field is ipaddress, for IP address and specified port, the identifier field is ipaddress:port.
Note This command does not exist in Cisco IOS 12.0 or earlier.
The following command adds an entry to the trusted host table for IP address 172.21.172.1, port 443:
sensor(config)# tls trusted-host ip-address 172.21.172.1
Certificate MD5 fingerprint is D4:C2:2F:78:B5:C6:30:F2:C4:6A:8E:5D:6D:C0:DE:32
Certificate SHA1 fingerprint is 36:42:C9:1B:9F:A4:A8:91:7F:DF:F0:32:04:26:E4:3A:7A:70:B9:95
Would you like to add this to the trusted certificate table for this host? [yes]
Certificate ID: 172.21.172.1 successfully added to the TLS trusted host table.
sensor(config)#
Note The Certificate ID stored for the requested certificate is displayed when the command is successfully completed.
The following command removes the trusted host entry for IP address 172.21.172.1, port 443:
sensor(config)# no tls trusted-host ip-address 172.21.172.1
sensor(config)#
Or you can use the following command to remove the trusted host entry for IP address 172.21.172.1, port 443:
sensor(config)# no tls trusted-host id 172.21.172.1
sensor(config)#
The following command adds an entry to the trusted host table for IP address 10.1.1.1, port 8000:
sensor(config)# tls trusted-host ip-address 10.1.1.1 port 8000
Certificate MD5 fingerprint is D4:C2:2F:78:B5:C6:30:F2:C4:6A:8E:5D:6D:C0:DE:32
Certificate SHA1 fingerprint is 36:42:C9:1B:9F:A4:A8:91:7F:DF:F0:32:04:26:E4:3A:7A:70:B9:95
Would you like to add this to the trusted certificate table for this host? [yes]
Certificate ID: 10.1.1.1:8000 successfully added to the TLS trusted host table.
sensor(config)#
Note The Certificate ID stored for the requested certificate is displayed when the command is successfully completed.
The following command removes the trusted host entry for IP address 10.1.1.1, port 8000:
sensor(config)# no tls trusted-host ip-address 10.1.1.1 port 8000
sensor(config)#
Or you can use the following command to remove the trusted host entry for IP address 10.1.1.1, port 8000:
sensor(config)# no tls trusted-host id 10.1.1.1:8000
sensor(config)#
|
|
---|---|
show tls trusted-hosts |
Displays the sensor's trusted hosts. |
To display the route an IP packet takes to a destination, use the trace command in privileged EXEC mode.
trace address [count]
address |
Address of system to trace route to. |
count |
Number of hops to take. Default is 4. Valid values are 1-256. |
See Syntax Description table.
EXEC
Administrator, Operator, Viewer
|
|
---|---|
4.0(1) |
This command was introduced. |
There is no command interrupt for the trace command. The command must run to completion.
The following example shows the output for the trace command:
sensor#
trace 10.1.1.1
traceroute to 172.21.172.24 (172.21.172.24), 30 hops max, 40 byte packets 1 171.69.162.2
(171.69.162.2) 1.25 ms 1.37 ms 1.58 ms 2 172.21.172.24 (172.21.172.24) 0.77 ms 0.66 ms
0.68 ms
sensor#
To apply a service pack, signature update, or image upgrade, use the upgrade command in global configuration mode.
upgrade source-url
source-url |
The location of the upgrade to retrieve. |
No default behavior or values.
Global configuration
Administrator
|
|
---|---|
4.0(1) |
This command was introduced. |
From the command line, you can type all necessary source and destination URL information and the username. If you type only the command (upgrade) followed by a prefix (ftp: or scp:), you are prompted for any missing information, including a password where applicable.
The directory specification should be an absolute path to the desired file. For recurring upgrades, do not specify a filename. You can configure the sensor for recurring upgrades that occur on specific days at specific times, or you can configure a recurring upgrade to occur after a specific number of hours have elapsed from the initial upgrade.
Use the following guidelines when designating the source:
•ftp:—Source URL for FTP network server. The syntax for this prefix is: ftp:[[//username@]location]/relativeDirectory/filename or ftp:[[//username@]location]//absoluteDirectory/filename
•http:—Source URL for web server. The syntax for this prefix is: http:[[//username@]location]/directory]/filename
•https:—Source URL for web server. The syntax for this prefix is: https:[[//username@]location]/directory]/filename
Note You need to set up a TLS trusted host before using the HTTPS protocol. Refer to the command for more information.
•scp:—Source URL for the SCP network server. The syntax for this prefix is: scp:[[//username@]location]/relativeDirectory]/filename or scp:[[//username@]location]/absoluteDirectory]/filename
Note This command does not exist in Cisco IOS 12.0 or earlier.
The following example prompts the sensor to immediately check for the specified upgrade. The directory and path are relative to the tester's user account.
sensor(config)#
upgrade scp://tester@10.1.1.1/upgrade/sp.rpm
Enter password:
*****
Re-enter password:
****
To create users on the local sensor, use the username command in global configuration mode. You must be Administrator to create users. Use the no form of the command to remove a user from the sensor. This removes the users from both CLI and web access.
username name [password password] [privilege privilege]
no username name
See Syntax Description table.
Global configuration
Administrator
|
|
---|---|
4.0(1) |
This command was introduced. |
The username command provides username and/or password authentication for login purposes only. The user executing the command cannot remove himself or herself.
If the password is not provided on the command line, the user is prompted. Use the password command to change the password for the current user or for a user already existing in the system. Use the privilege command to change the privilege for a user already existing in the system.
The following example adds a user called tester with a privilege of viewer and the password testerpassword.
sensor(config)# username tester password testerpassword
The following example shows the password being entered as protected:
sensor(config)# username tester
Enter Login Password: **************
Re-enter Login Password: **************
The following command changes the privilege of user "tester" to operator:
sensor(config)# username tester privilege operator
|
|
---|---|
password |
Updates your password on the local sensor. |
privilege |
Modifies the privilege level for an existing user. |