B Ise Cli Reference Guide 31
B Ise Cli Reference Guide 31
1
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND
RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL
RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE
INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the
UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED
SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS
OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network
topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional
and coincidental.
All printed copies and duplicate soft copies of this document are considered uncontrolled. See the current online version for the latest version.
Cisco has more than 200 offices worldwide. Addresses and phone numbers are listed on the Cisco website at www.cisco.com/go/offices.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL:
https://www.cisco.com/c/en/us/about/legal/trademarks.html. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a
partnership relationship between Cisco and any other company. (1721R)
© 2021 Cisco Systems, Inc. All rights reserved.
CONTENTS
application configure 13
Monitoring Database Settings 14
Live Statistics of Profiling Events 17
application remove 25
application reset-config 26
application reset-passwd 28
application start 29
application stop 32
application upgrade 34
backup 37
backup-logs 40
clear screen 42
clock 43
cls 45
configure 46
copy 47
Running Configuration 48
Copying Running Configuration to a Remote Location 49
Copying Running Configuration from a Remote Location 49
Startup configuration 49
crypto 52
debug 55
delete 59
dir 60
esr 62
exit 63
forceout 64
halt 65
help 66
licence esr 67
mkdir 68
nslookup 69
password 71
patch install 72
patch remove 74
permit rootaccess 76
ping 78
ping6 79
reload 81
reset-config 82
restore 83
Restoring Cisco ISE Configuration Data and Cisco ADE OS data from the Backup 86
rmdir 88
ssh 89
tech 91
terminal length 93
terminal session-timeout 94
terminal session-welcome 95
terminal terminal-type 96
traceroute 97
undebug 98
which 101
write 102
show 105
cls 179
conn-limit 180
do 182
end 186
exit 187
hostname 188
identity-store 191
interface 192
ip address 194
ip default-gateway 196
ip domain-name 197
ip host 199
ip mtu 201
ip name-server 202
ip route 204
logging 220
max-ssh-sessions 221
ntp 222
rate-limit 230
password-policy 231
repository 233
service 236
shutdown 238
synflood-limit 252
username 253
which 255
Note The documentation set for this product strives to use bias-free language. For 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.
This chapter provides information on the Cisco Identity Services Engine (Cisco ISE) command-line interface
(CLI) that you can use to configure and maintain Cisco ISE.
• Cisco ISE Administration and Configuration Using CLI, on page 2
• Cisco ISE CLI Administrator Account, on page 4
• Cisco ISE CLI User Accounts, on page 5
• Cisco ISE CLI User Account Privileges, on page 6
• Supported Hardware and Software Platforms for Cisco ISE CLI, on page 7
The default parameters for the console port are 9600 baud, 8 data bits, no parity, 1 stop bit, and no hardware
flow control.
Note If you are using a Cisco switch on the other side of the connection, set the switchport to duplex auto, speed
auto (the default).
Step 1 Connect a null-modem cable to the console port in the Cisco ISE device and to the COM port on your system.
Step 2 Set up a terminal emulator to communicate with Cisco ISE. Use the following settings for the terminal emulator connection:
9600 baud, 8 data bits, no parity, 1 stop bit, and no hardware flow control.
Step 3 When the terminal emulator activates, press Enter.
Step 4 Enter your username and press Enter.
Step 5 Enter the password and press Enter.
Step 1 Log into the Cisco ISE CLI using the CLI administrator account.
Step 2 Enter into configuration mode and run the username command.
Step 3 Log into the Cisco ISE CLI using the CLI user account.
application install
Note You are not allowed to run the application install command from the command-line interface (CLI) under
normal operations because the Cisco Identity Services Engine (ISE) application is pre-installed with a Cisco
IOS image on all supported appliances and VMware.
To install a specific application other than Cisco ISE, use the application install command in EXEC mode. To
remove an application other than Cisco ISE, use the application remove command.
application [ install {application-bundle} {remote-repository-name}]
Usage Guidelines Installs the specified application bundle on the appliance. The application bundle file is pulled from a specified
repository.
If you issue the application install or application remove command when another installation or removal
operation of an application is in progress, you will see the following warning message:
Example
application configure
Use the application configure command in EXEC mode to:
• perform M&T operations
• refresh and display statistics related to the profiler
• export and import options to backup and restore Cisco ISE CA certificates and keys
• generate Key Performance Metrics (KPM) statistics
• enable or disable the ISE counter attribute data collection
• enable or disable wireless setup
• reset wireless setup configuration
Usage Guidelines You can use this command to update M&T databases and indexes, and export and import Cisco ISE CA
certificates and keys, generate Key Performance Metrics (KPM) statistics ,and enable or disable ISE counter
attribute data collection in a Cisco ISE node.
Example
Note Cisco ISE 3.0 and later does not support Wireless Setup (Wifi setup).
Note Cisco ISE 3.1 and later does not support ACS migration.
Note We recommend to reset primary and secondary Monitoring node databases at the same time to prevent
discrepancy in log files.
To configure Monitoring database related tasks, use the following options in the application configure ise
command:
• To reset the monitoring session database, use the option 1.
Note The reset option will cause ISE services to be temporarily unavailable until it
restarts.
Note The reset option will cause ISE services to be temporarily unavailable until it
restarts.
Example
To reset the monitoring session database, use the option 1.
1
You are about to reset the M&T session database. Following this operation, an application
restart will be required.
Are you sure you want to proceed? y/n [n]: y
TimesTen Daemon stopped.
TimesTen Daemon startup OK.
Restarting application
Stopping ISE Monitoring & Troubleshooting Log Processor...
ISE Identity Mapping Service is disabled
ISE pxGrid processes are disabled
Stopping ISE Application Server...
Stopping ISE Certificate Authority Service...
Stopping ISE Profiler Database...
Stopping ISE Monitoring & Troubleshooting Session Database...
Stopping ISE AD Connector...
Stopping ISE Database processes...
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
Starting ISE Monitoring & Troubleshooting Session Database...
Starting ISE Profiler Database...
Starting ISE Application Server...
Starting ISE Certificate Authority Service...
Starting ISE Monitoring & Troubleshooting Log Processor...
Starting ISE AD Connector...
Note: ISE Processes are initializing. Use 'show application status ise'
CLI to verify all processes are in running state.
2
You are about to rebuild the M&T database unusable indexes.
Are you sure you want to proceed? y/n [n]: y
Starting to rebuild indexes
Completed rebuild indexes
3
Enter number of days to be retained in purging MnT Operational data [between 1 to 90 days]
For instance, Entering 20 will purge MnT Operational data older than 20 days
Enter 'exit' to return to the main menu without purging
Enter days to be retained: 20
You are about to purge M&T data older than 20 from your database.
Are you sure you want to proceed? y/n [n]: y
M&T Operational data older than 20 is getting removed from database
4
You are about to reset the M&T database. Following this operation, application will be
restarted.
Are you sure you want to proceed? y/n [n]: y
Stopping application
Stopping ISE Monitoring & Troubleshooting Log Processor...
ISE Identity Mapping Service is disabled
ISE pxGrid processes are disabled
Stopping ISE Application Server...
Stopping ISE Certificate Authority Service...
Stopping ISE Profiler Database...
Stopping ISE Monitoring & Troubleshooting Session Database...
Stopping ISE AD Connector...
Stopping ISE Database processes...
Starting Database only
Creating ISE M&T database tables...
Restarting application
ISE M&T Log Processor is not running
ISE Identity Mapping Service is disabled
ISE pxGrid processes are disabled
ISE Application Server process is not running
ISE Certificate Authority Service is not running
ISE Profiler Database is not running
ISE M&T Session Database is not running
ISE AD Connector is not running
Stopping ISE Database processes...
Starting ISE Monitoring & Troubleshooting Session Database...
Starting ISE Profiler Database...
Starting ISE Application Server...
Starting ISE Certificate Authority Service...
Starting ISE Monitoring & Troubleshooting Log Processor...
Starting ISE AD Connector...
Note: ISE Processes are initializing. Use 'show application status ise'
CLI to verify all processes are in running state.
5
You are about to Refresh Database statistics
Are you sure you want to proceed? y/n [n]: y
Starting to terminate long running DB sessions
Completed terminating long running DB sessions
Example
Create an RMI connector client and connect it to the RMI connector server
Get an MBeanServerConnection
Retrieve MXBean
• To import a copy of the Cisco ISE CA certificates and keys, use option 8 in the application configure ise
command.
Example 1
To export a copy of the Cisco ISE CA certificates and keys, use option 7.
7
Export Repository Name: sftp
Enter encryption-key for export: Test1234
Export on progress...............
Example 2
To import a copy of the Cisco ISE CA certificates and keys, use option 8.
8
Import Repository Name: sftp
Enter CA keys file name to import: ise_ca_key_pairs_of_ise60
Enter encryption-key: Test1234
Import on progress...............
Example 1
To create the CEPM database index, use option 9.
9
You are about to create missing config indexes.
Are you sure you want to proceed? y/n [n]: y
Starting to create missing config indexes
Completed creating missing config indexes
Example 2
To create missing Monitoring database indexes, use option 10.
10
You are about to create missing MnT indexes.
Are you sure you want to proceed? y/n [n]: y
Starting to create missing MnT indexes
Example
12
Cisco ISE, by default, collects the values for these attributes. You can choose to disable this data collection
from the Cisco ISE CLI using the application configure ise command. Choose option 14 to enable or disable
counter attribute collection.
Example
To disable counter attribute collection, use option 14.
14
Do you want to Enable(e) or Disable(d) counter attribute collection? [e/d]d
Completed disabling counter attributes. It will take at the most 30 minute to get effected.
Example
To configure the TCP parameters, use option 25.
25
This CLI allows admins to modify the TCP parameters recycle/reuse/fin_timeout
For the changes to take effect, RELOAD ISE server on modifying any of the parameter using
the admin cli 'reload'. Until reload is done, the changes will not be persisted.
Select the option to configure/display tcp params.
1. tcp recycle
2. tcp reuse
3. tcp fin_timeout
4. display tcp param values
0. Exit
[1/2/3/4/0]: 1
Enable/Disable tcp recycle parameter? [e/d]: e
param recycle is already enabled..
Select the option to configure/display tcp params.
1. tcp recycle
2. tcp reuse
3. tcp fin_timeout
4. display tcp param values
0. Exit
[1/2/3/4/0]: 2
Enable/Disable tcp reuse parameter? [e/d]: e
param reuse is already enabled..
Select the option to configure/display tcp params.
1. tcp recycle
2. tcp reuse
3. tcp fin_timeout
4. display tcp param values
0. Exit
[1/2/3/4/0]: 3
Set tcp fin_timeout (60 default) <0-180> : 60
updated timeout param..
Select the option to configure/display tcp params.
1. tcp recycle
2. tcp reuse
3. tcp fin_timeout
4. display tcp param values
0. Exit
[1/2/3/4/0]: 4
Current values of the tcp parameters:
Recycle = ENABLED
Reuse = ENABLED
Fin_timeout = 60
Select the option to configure/display tcp params.
1. tcp recycle
2. tcp reuse
3. tcp fin_timeout
4. display tcp param values
0. Exit
[1/2/3/4/0]:
Note • tcp reuse accepts values - 0 (disable), 1 (enable globally) and 2 (enable for loopback traffic only). tcp
reuse is set to 2 seconds by default. Enable reuse of TIME-WAIT sockets for new connections when it is
safe from protocol viewpoint.
• tcp recycle is disabled by default. Enabling tcp recycle enables the fast recycling of TIME-WAIT sockets.
Cisco ISE doesn’t recommend altering this tcp recycle parameter as this can induce undesired behavior
when using load balancers. Also, it is not recommended to use tcp recycle with Network Address
Translation in place. Contact your network administrator before implementing this recycle operation.
• tcp fin_timeout is set to 60 seconds by default. The valid range for tcp fin_timeout is from 0 to 180 seconds.
You can set this attribute to a lower value to enhance the TACACS+ performance. To change this to an
optimal value, from the root shell of Cisco ISE, execute netstat -nat | awk '{print $6}' | sort |
uniq -c | sort -n
application remove
Note You are not allowed to run the application remove command from the command-line interface (CLI) to remove
Cisco ISE unless you are explicitly instructed to do so for an upgrade.
To remove a specific application other than Cisco ISE, use the application remove command in EXEC mode.
application [ remove {application-name}]
When you do not want to remove any other application other than Cisco ISE, use the no form of this command.
no application [ remove {application-name}]
Example
application reset-config
To reset the Cisco ISE application configuration to factory defaults or retain the existing factory settings, use
the application reset-config command in EXEC mode. In addition to self-signed certificates, you can also reset
server certificates or retain the existing server certificates.
application [ reset-config {application-name}]
Syntax Description reset-config Resets the Cisco ISE application configuration and
clears the Cisco ISE database.
Usage Guidelines You can use the application reset-config command to reset the Cisco ISE configuration and clear the Cisco
ISE database without reimaging the Cisco ISE appliance or VMware. The reset requires you to enter new Cisco
ISE database administrator and user passwords.
Note Although the application reset-config command resets the Cisco ISE configuration to factory defaults, the
operating system (Cisco ADE-OS) configuration still remains intact. The Cisco ADE-OS configuration includes
items such as the network settings, CLI password policy, and backup history.
When you reset the Cisco ISE application configuration from the CLI, it performs a leave operation disconnecting
the ISE node from the Active Directory domain if it is already joined. However, the Cisco ISE node account is
not removed from the Active Directory domain. We recommend that you perform a leave operation from the
Cisco ISE Admin portal with the Active Directory credentials. The leave operation removes the node account
from the Active Directory domain.
Example
If a user selects the No option, the command deletes server certificates and regenerates only self-signed
certificates. If the user selects the Yes option, the command retains existing server certificates by exporting
them to a location. The server certificates are then imported from this location.
application reset-passwd
To reset the Admin portal login password for a specified user account (usually an existing administrator
account) in Cisco ISE after the administrator account has been disabled due to incorrect password entries,
use the application reset-passwd command in EXEC mode.
application [ reset-passwd {application-name} {administrator-ID} ]
Command Default No default behavior or values. necessary to disable the administrator account in Cisco ISE
Usage Guidelines The following special characters are allowed when resetting the Cisco ISE Admin portal password:
~ ! @ $ & * - _
If you enter an incorrect password for an administrator user ID more than the specified number of times, then
the Admin portal “locks you out” of the system. Cisco ISE suspends the credentials for it. administrator user
ID until you have an opportunity to reset the password associated with it. You can reset the administrator
password only in the Administration ISE node CLI.
UTF-8 admin users can change passwords only through the Cisco ISE Admin portal.
Example
application start
To enable a specific application, use the application start command in EXEC mode. To disable starting an
application, use the no form of this command.
application [ start {application-name | safe}]
no application [ start {application-name | safe}]
Example 1
• On FIPS enabled hosts, if the 'safe' option is passed on application startup, the hardware random number
generator integrity check is disabled.
• Cisco ISE initiates outbound SSH or SFTP connections in FIPS mode even if FIPS mode is not enabled on
ISE. Ensure that the remote SSH or SFTP servers that communicate with ISE allow FIPS 140-2 approved
cryptographic algorithms.
Cisco ISE uses embedded FIPS 140-2 validated cryptographic modules. For details of the FIPS compliance
claims, see the FIPS Compliance Letter.
• If certificate-based authentication is used, the 'safe' option on application start will temporarily use
username and password based authentication.
Note These changes are temporary and only relevant for that instance of the Cisco ISE application. If the Cisco ISE
services are restarted again without the 'safe' option, all of the default functionality is restored.
Note: ISE Processes are initializing. Use 'show application status ise'
CLI to verify all processes are in running state.
Starting ISE EST Service...
application stop
To disable a specific application, use the application stop command in EXEC mode. To disable stopping an
application, use the no form of this command.
application [ stop {application-name}]
no application [ stop {application-name}]
Example
application upgrade
To upgrade a specific application bundle, use the application upgrade command in EXEC mode.
application [ upgrade {application-bundle | remote-repository-name}]
Usage Guidelines Upgrades an application, and preserves any application configuration data. See the Cisco Identity Services
Engine Upgrade Guide for more information.
• Use the cleanup option, if you want to try another upgrade bundle in case of a failure or use a different
version.
• Use the prepare option to download and extract an upgrade bundle locally.
• Use the proceed option to upgrade Cisco ISE using the upgrade bundle you extracted with the prepare
option. You can use this option after preparing an upgrade bundle instead of using the application upgrade
command directly.
• If upgrade is successful, this option removes the upgrade bundle.
• If upgrade fails for any reason, this option retains the upgrade bundle.
If you issue the application upgrade command when another application upgrade operation is in progress,
you will see the following warning message:
Caution Do not issue the backup or restore commands when an upgrade is in progress. This action might cause the
database to be corrupted.
Note Before attempting to use the application upgrade command, you must read the upgrade instructions in the
release notes supplied with the newer release. The release notes contain important updated instructions and
they must be followed.
Example 1
ise/admin# application upgrade prepare application upgrade prepare
ise-upgradebundle-2.3.0.x.x86_64.tar.gz upgrade
Example 2
ise/admin# application upgrade proceed
Initiating Application Upgrade...
% Warning: Do not use Ctrl-C or close this terminal window until upgrade completes.
-Checking VM for minimum hardware requirements
STEP 1: Stopping ISE application...
STEP 2: Verifying files in bundle...
-Internal hash verification passed for bundle
STEP 3: Validating data before upgrade...
STEP 4: Taking backup of the configuration data...
STEP 5: Running ISE configuration database schema upgrade...
- Running db sanity to check and fix if any index corruption
- Auto Upgrading Schema for UPS Model
- Upgrading Schema completed for UPS Model
ISE database schema upgrade completed.
% Warning: Sanity test found some indexes missing in CEPM schema. Please recreate missing
indexes after upgrade using app configure ise cli
STEP 6: Running ISE configuration data upgrade...
- Data upgrade step 1/14, UPSUpgradeHandler(2.3.0.100)... Done in 53 seconds.
- Data upgrade step 2/14, UPSUpgradeHandler(2.3.0.110)... Done in 1 seconds.
- Data upgrade step 3/14, NetworkAccessUpgrade(2.3.0.145)... Done in 0 seconds.
- Data upgrade step 4/14, NodeGroupUpgradeService(2.3.0.155)... Done in 0 seconds.
- Data upgrade step 5/14, IRFUpgradeService(2.3.0.155)... Done in 0 seconds.
- Data upgrade step 6/14, UPSUpgradeHandler(2.3.0.158)... Done in 0 seconds.
- Data upgrade step 7/14, NetworkAccessUpgrade(2.3.0.178)... Done in 0 seconds.
- Data upgrade step 8/14, NetworkAccessUpgrade(2.3.0.182)... Done in 0 seconds.
- Data upgrade step 9/14, CertMgmtUpgradeService(2.3.0.194)... Done in 3 seconds.
- Data upgrade step 10/14, UPSUpgradeHandler(2.3.0.201)... Done in 0 seconds.
- Data upgrade step 11/14, NSFUpgradeService(2.3.0.233)... Done in 0 seconds.
- Data upgrade step 12/14, ProfilerUpgradeService(2.3.0.233)... Done in 0 seconds.
- Data upgrade step 13/14, GuestAccessUpgradeService(2.3.0.233)... Done in 7 seconds.
STEP 7: Running ISE configuration data upgrade for node specific data...
STEP 8: Running ISE M&T database upgrade...
ISE M&T Log Processor is not running
ISE database M&T schema upgrade completed.
backup
To perform a backup including Cisco ISE and Cisco ADE OS data and place the backup in a repository, use the
backup command in EXEC mode.
Note Before attempting to use the backup command in EXEC mode, you must copy the running configuration to a
safe location, such as a network server, or save it as the Cisco ISE server startup configuration. You can use
this startup configuration when you restore or troubleshoot Cisco ISE from the backup and system logs.
backup [{backup-name} repository {repository-name} ise-config encryption-key hash| plain {encryption-key
name}]
backup [{backup-name} repository {repository-name} ise-operational encryption-key hash| plain {encryption-key
name}]
Usage Guidelines You can encrypt and decrypt backups now by using user-defined encryption keys when you perform a backup
of Cisco ISE and Cisco ADE OS data in a repository with an encrypted (hashed) or unencrypted plaintext
password with ise-config. To perform a backup of only the Cisco ISE application data without the Cisco ADE
OS data, use the ise-operational command.
You can back up Cisco ISE operational data only from the primary or secondary Monitoring nodes.
Important When performing a backup and restore, the restore overwrites the list of trusted certificates on the target
system with the list of certificates from the source system. It is critically important to note that backup and
restore functions do not include private keys associated with the Internal Certificate Authority (CA) certificates.
If you are performing a backup and restore from one system to another, you will have to choose from one of
these options to avoid errors:
• Option 1:
Export the CA certificates from the source ISE node through the CLI and import them in to the target
system through the CLI.
Pros:Any certificates issued to endpoints from the source system will continue to be trusted. Any new
certificates issued by the target system will be signed by the same keys.
Cons:Any certificates that have been issued by the target system prior to the restore function will not be
trusted and will need to be re-issued.
• Option 2:
After the restore process, generate all new certificates for the internal CA.
Pros:This option is the recommended and clean method, where neither the original source certificates
or the original target certificates will be used. Certificates issued by the original source system will
continue to be trusted.
Cons:Any certificates that have been issued by the target system prior to the restore function will not be
trusted and will need to be re-issued.
Example
Example
backup-logs
To back up system logs, use the backup-logs command in EXEC mode. To remove this function, use the no
form of this command.
Note Before attempting to use the backup-logs command in EXEC mode, you must copy the running configuration
to a safe location, such as a network server, or save it as the Cisco ISE server startup configuration. You can
use this startup configuration when you restore or troubleshoot Cisco ISE from the backup and system logs.
Syntax Description backup-name Name of one or more files to back up. Supports up to
100 alphanumeric characters.
public-key Specifies that Cisco ISE will use the Cisco PKI public
keys for encryption. Choose this option if you are going
to provide the support bundle to Cisco TAC for
troubleshooting. Only Cisco TAC can decrypt the
support bundle using the private key. Choose the
encryption-key option if you are going to troubleshoot
the issues locally on premise.
Usage Guidelines Backs up system logs with an encrypted (hashed) or unencrypted plaintext password.
Example 1
Example 2
clear screen
To clear the contents of terminal screen, use the clear screen command in EXEC mode.
clear screen
Usage Guidelines clear screen is a hidden command. Although clear screen is available in Cisco ISE, the CLI interactive Help
does not display it if you attempt to view it by entering a question mark at the command line.
Example
The following example shows how to clear the contents of the terminal:
clock
To set the system clock, use the clock command in EXEC mode. To disable setting the system clock, use the
no form of this command.
clock [ set {month | day | hh:min:ss | yyyy}]
Usage Guidelines
Caution Changing the system time on a Cisco ISE appliance causes the Cisco ISE application to be unusable.
Sets the system clock. You must restart the Cisco ISE server after you reset the clock for the change to take
effect. Changing system time impacts different Cisco ISE nodes types of your deployment.
To recover from the impact, use the following steps:
Note Changing the system time after installation is not supported on a standalone or primary ISE node.
• Restore from the last known good backup before the time change on that node.
Note Changing the system time on a secondary node renders it unusable in your deployment.
To synchronize the system time of the secondary node with the primary node, do the following:
• Deregister the secondary ISE node.
• Correct the system time to be in sync with the primary ISE node.
• Run the application reset-config ise command from the CLI of the primary ISE node.
• Reregister the ISE node as a secondary ISE node to the primary ISE node.
Note To ensure that you have the correct system time set at the time of installation, the
setup wizard requires you to specify an Network Time Protocol (NTP) server and
tries to sync with it. You must ensure that the NTP server configured during setup
is always reachable so that the system time is always kept accurate, especially
in rare situations where the BIOS time can get corrupted because of power failure
or CMOS battery failure. This, in turn, can corrupt the Cisco ADE-OS system time
during a reboot. If you do not configure an NTP server during setup, then you have
to ensure that the system BIOS time is set relative to the Universal Time
Coordinated (UTC) time zone, as described in the Cisco Identity Services Engine
Hardware Installation Guide.
Example
cls
To clear the contents of terminal screen, use the cls command in EXEC mode.
cls
Usage Guidelines cls is a hidden command. Although cls is available in Cisco ISE, the CLI interactive Help does not display it if
you attempt to view it by entering a question mark at the command line.
Example
The following example shows how to clear the contents of the terminal:
ise/admin# cls
ise/admin#
configure
To enter in to configuration mode, use the configure command in EXEC mode.
configure terminal
Usage Guidelines Use this command to enter in to configuration mode. Note that commands in this mode write to the running
configuration file as soon as you enter them.
To exit configuration mode and return to EXEC mode, enter end, exit, or Ctrl-z.
To view the changes made to the configuration, use the show running-config command in EXEC mode.
If the replace option is used with this command, copies a remote configuration to the system, which overwrites
the existing configuration.
Example
copy
To copy a file from a source to a destination, use the copy command in EXEC mode.
Using the copy command, you can copy core files and heap dumps from Cisco ISE to a remote repository. See
Example 3 under Copying Log files, on page 50 for more information.
all Copies all Cisco ISE log files from the system to
another location. All logs are packaged as
iselogs.tar.gz and transferred to the specified directory
on the remote host.
filename Allows you to copy a single Cisco ISE log file and
transfer it to the specified directory on the remote
host, with its original name.
runtime Copies the Cisco ISE runtime debug logs from the
system, bundles them as runtimelogs.tar.gz, and
transfers them to the specified directory on the remote
host.
Usage Guidelines The copy command in Cisco ISE copies a running or start up configuration and log files from the system to
another location.
The fundamental function of the copy command allows you to copy a file (such as a system image or
configuration file) from one location to another location. The source and destination for the file specified uses
the Cisco ISE file system, through which you can specify any supported local or remote file location. The file
system being used (a local memory source or a remote system) dictates the syntax used in the command.
You can enter all necessary source and destination information and the username and password to use; or,
you can enter the copy command and have the server prompt you for any missing information.
The entire copying process might take several minutes and differs from protocol to protocol and from network
to network.
Use the filename relative to the directory for file transfers.
Possible errors are standard File Transfer protocol (FTP) error messages.
Example
ise/admin# copy disk:/ filename repository repository_name
Running Configuration
The Cisco ISE active configuration stores itself in the Cisco ISE RAM. Every configuration command you enter
resides in the running configuration. If you reboot a Cisco ISE server, you lose the running configuration. If
you make changes that you want to save, you must copy the running configuration to a safe location, such as
a network server, or save it as the Cisco ISE server startup configuration.
If you do not save the running configuration, you will lose all your configuration changes during the next reboot
of the Cisco ISE server. When you are satisfied that the current configuration is correct, copy your configuration
to the startup configuration with the copy run start command.
Note Aliases reduce the amount of typing that you need to do. For example, type copy run and press the Tab key,
type start and press the Tab key, which is the abbreviated form of the copy running-config startup-config
command).
To replace the startup configuration with the running configuration, use the following command:
copy run start
To copy the running configuration to the startup configuration, use the following command:
copy running-config startup-config
To merge the startup configuration on top of the running configuration, use the following command:
copy start run
Example 1
Example 2
Startup configuration
You cannot edit a startup configuration directly. All commands that you enter store themselves in the running
configuration, which you can copy into the startup configuration.
In other words, when you boot a Cisco ISE server, the startup configuration becomes the initial running
configuration. As you modify the configuration, the two diverge: the startup configuration remains the same;
the running configuration reflects the changes that you have made. If you want to make your changes permanent,
you must copy the running configuration to the startup configuration.
To copy the startup configuration to the running configuration, use the following command:
copy startup-config running-config
Example 1
Example 2
Example 1
To copy log files to the local disk, use the following command:
Example 2
To copy log files to another location, use the following command:
Example 3
Cisco ISE moves the core files and heap dumps from the /var/tmp directory to the disk:/corefiles directory on
an hourly basis. You can copy these logs from the local disk to a remote repository using the copy command.
The core files and heap dumps contain critical information that would help identify the cause of a crash. These
logs are created when the application crashes. You can use the dir command to view the core files in the local
disk.
ise/admin# copy disk:/corefiles ftp://192.0.2.2/
Username: ftp
Password:
ise36/admin#
ise36/admin# dir
Directory of disk:/
crypto
To generate a new public key pair, export the current public key to a repository, and import a public key to the
authorized keys list, use the crypto command in EXEC mode. It is also possible to view the public key information
and delete selected keys.
crypto key [ delete {hash | authorized_keys | rsa}]
crypto key [ export {filename | repository}]
crypto key [ generate {rsa}]
crypto key [ import {filename | repository}]
crypto ntp_import_autokey ntpkey
ntp_import_autokey Imports the public key generated from the NTP server.
Usage Guidelines The Cisco ADE OS supports public key authentication with out the password for SSH access to administrators
and user identities.
Use the crypto key generate rsa command to generate a new public/private key pair with a 2048-bit length for
the current user. The key attributes are fixed, and supports RSA key types. If the key pair already exists, you
will be prompted to permit an over-write before continuing with a passphrase. If you provide the passphrase,
you will be prompted for the passphrase whenever you access the public/private key. If the passphrase is
empty, no subsequent prompts for the passphrase occurs.
Use the crypto ntp_import_autokey command to import the public key generated from the NTP server.
Example 1
Example 2
Example 3
ise/admin# crypto ntp_import_autokey ntpkey repository nfs
ise/admin#
debug
To display errors or events for executed commands, use the debug command in EXEC mode.
debug [ all | application | backup-restore | cdp | config | copy | icmp | locks | logging | snmp | system | transfer
| user | utils ]
Usage Guidelines Use the debug command to display various errors or events in the Cisco ISE server, such as setup or
configuration failures.
Example
delete
To delete a file from the Cisco ISE server, use the delete command in EXEC mode. To remove deleting files
from the Cisco ISE server, use the no form of this command.
delete [filename disk:/path]
Usage Guidelines If you attempt to delete a configuration file or image, the system prompts you to confirm the deletion. Also, if
you attempt to delete the last valid system image, the system prompts you to confirm the deletion.
Example
dir
To list a file from the Cisco ISE server, use the dir command in EXEC mode. To remove this function, use the
no form of this command.
dir
dir disk:/logs
dir recursive
Example 1
ise/admin# dir
Directory of disk:/
2034113 Aug 05 2010 19:58:39 ADElogs.tar.gz
4096 Jun 10 2010 02:34:03 activemq-data/
4096 Aug 04 2010 23:14:53 logs/
16384 Jun 09 2010 02:59:34 lost+found/
2996022 Aug 05 2010 19:11:16 mybackup-100805-1910.tar.gz
4096 Aug 04 2010 23:15:20 target/
4096 Aug 05 2010 12:25:55 temp/
Usage for disk: filesystem
8076189696 bytes total used
6371618816 bytes free
15234142208 bytes available
ise/admin#
Example 2
Example 3
esr
To enter the Embedded Services Router console, use the esr command in EXEC mode.
esr
Usage Guidelines The C5921 ESR software is bundled with Cisco ISE, Releases 2.2 and later. You need an ESR license to enable
it. See Cisco 5921 Embedded Services Router Integration Guide for ESR licensing information.
exit
To close an active terminal session by logging out of the Cisco ISE server or to move up one mode level from
configuration mode, use the exit command in EXEC mode.
This command has no keywords and arguments.
exit
Example
ise/admin# config t
Enter configuration commands, one per line. End with CNTL/Z.
ise/admin(config)# exit
ise/admin#
forceout
To force users out of an active terminal session by logging them out of the Cisco ISE server, use the forceout
command in EXEC mode.
forceout username
Usage Guidelines Use the forceout command in EXEC mode to force a user from an active session.
Example
halt
To shut down and power off the system, use the halt command in EXEC mode.
This command has no keywords and arguments.
halt
Usage Guidelines Before you issue the halt command, ensure that Cisco ISE is not performing any backup, restore, installation,
upgrade, or remove operation. If you issue the halt command while the Cisco ISE is performing any of these
operations, you will get one of the following warning messages:
If you get any of these warnings, enter Yes to continue the halt operation, or enter No to cancel the halt.
If no processes are running when you use the halt command or if you enter Yes in response to the warning
message displayed, then you must respond to the following question:
If you enter Yes to save the existing Cisco ISE configuration, the following message is displayed:
Example
ise/admin# halt
ise/admin#
help
To display the interactive help system for the Cisco ISE server, use the help command in EXEC mode.
This command has no keywords and arguments.
help
Usage Guidelines The help command provides a brief description of the context-sensitive help system.
• To list all commands available for a particular command mode, enter a question mark (?) at the system
prompt.
• To obtain a list of commands that begin with a particular character string, enter the abbreviated command
entry immediately followed by ?. This form of help is called word help because it lists only the keywords
or arguments that begin with the abbreviation that you entered.
• To list the keywords and arguments associated with a command, enter ? in place of a keyword or argument
on the command line. This form of help is called command syntax help, because it lists the keywords or
arguments that apply based on the command, keywords, and arguments that you enter.
Example
ise/admin# help
Help may be requested at any point in a command by entering
a question mark '?'. If nothing matches, the help list will
be empty and you must backup until entering a '?' shows the
available options.
Two styles of help are provided:
1. Full help is available when you are ready to enter a
command argument (e.g. 'show?') and describes each possible
argument.
2. Partial help is provided when an abbreviated argument is entered
and you want to know what arguments match the input
(e.g. 'show pr?'.)
ise/admin#
licence esr
To perform esr licence operation, use the licence esr command in EXEC mode.
license esr{ classic |smart }
Usage Guidelines The C5921 ESR software is bundled with Cisco ISE, Releases 2.2 and later. You need an ESR license to enable
it. See Cisco 5921 Embedded Services Router Integration Guide for ESR licensing information.
mkdir
To create a new directory in the Cisco ISE server, use the mkdir command in EXEC mode.
mkdir directory-name
Usage Guidelines Use disk:/directory-name; otherwise, an error appears that indicates that the disk:/directory-name must be
included.
Example
nslookup
To look up the hostname of a remote system in the Cisco ISE server, use the nslookup command in EXEC mode.
nslookup {ip-address |hostname}
nslookup [ {ip-address |hostname} name-server {ip-address }]
nslookup [ {ip-address |hostname} querytype AAAA]
Example 1
Example 2
password
To update the CLI account password, use the password command in EXEC mode.
password
Note When you create a password for the administrator during installation or after installation in the CLI, do not use
the $ character, except when it is the last character of the password. If that character is first or inside the
other characters, the password is accepted, but you cannot use it to log on to the CLI.
You can fix this by logging into the console and using the CLI command, or by getting an ISE CD or ISO file.
Instructions for using an ISO to reset the password are explained in the following document:
https://www.cisco.com/c/en/us/support/docs/security/identity-services-engine/
200568-ISE-Password-Recovery-Mechanisms.html
Syntax Description Enter old password Enter the current CLI password.
Example
ise/admin# password
Enter old password:
Enter new password:
Confirm new password:
ise/admin#
patch install
Before attempting to use the patch install command to install a patch, you must read the patch installation
instructions in the release notes supplied with the patch. The release notes contains important updated
instructions; and they must be followed.
To install a patch bundle of the application on a specific node from the CLI, use the patch install command in
EXEC mode.
patch install patch-bundle repository
Note In a Cisco ISE distributed deployment environment, install the patch bundle from the Admin portal so that the
patch bundle is automatically installed on all the secondary nodes.
If you have the primary Administration node (PAN) auto-failover configuration enabled in your deployment,
disable it before you install the patch. Enable the PAN auto-failover configuration after patch installation is
complete on all the nodes in your deployment.
When you install a patch on Release 2.0, the patch installation process does not prompt you to verify the hash
value of the software. Beginning from Release 2.0 onwards, the patch installation software automatically
verifies the integrity of the patch software using digital signatures. See the example given below for a sample
output of the patch install command.
To view the status of a patch installation from the CLI, you must check the ade.log file in the Cisco ISE support
bundle.
If you have the PAN auto-failover configuration enabled in your deployment, the following message appears:
Disable the PAN auto-failover configuration and enable it after patch installation is complete on all the nodes
in your deployment.
Example
patch remove
Before attempting to use the patch remove command to rollback a patch, you must read the rollback instructions
of the patch in the release notes supplied with the patch. The release notes contains important updated
instructions: and they must be followed.
To remove a specific patch bundle version of the application, use the patch remove command in EXEC mode.
patch [ remove {application_name | version}]
Note In a Cisco ISE distributed deployment environment, removing the patch bundle from the Admin portal
automatically removes the patch from the secondary nodes.
Syntax Description remove The command that removes a specific patch bundle
version of the application.
If you have the primary Administration node (PAN) auto-failover configuration enabled in your deployment,
disable it before you remove a patch. You can enable the PAN auto-failover configuration after patch removal
is complete.
Usage Guidelines If you attempt to remove a patch that is not installed, then you receive the following error message:
If you have the PAN auto-failover configuration enabled in your deployment, the following message appears:
PAN Auto Failover is enabled, this operation is
not allowed! Please disable PAN Auto-failover first.
Example 1
Example 2
permit rootaccess
To access the root of the Cisco ISE CLI, use the permit rootaccess command in EXEC mode.
permit rootaccess
Example
The following example shows how to access the root of the Cisco ISE CLI:
ise/admin##
ise/admin# permit rootaccess
1. Generate Challenge Token Request
2. Enter Challenge Response for Root Access
3. Show History
4. Exit
Enter CLI Option:
1
Generating Challenge.....................................
Challenge String (Please copy everything between the asterisk lines exclusively):
*****************************************************************************************
GLOX7gAAAQEBAAQAAAABAgAEAAAAAAMACLmJxgub0hitBAAQiUwv+XeD3pnJ4HLnJy30YQUABAAADhAGAANJU0UHAAZJU0VfQ1QIAANJU0UJACcJIDU2NGQ5NjgwLTFmZmEtOWI0ZS0wZjY1LTdlZDllMGQ1M2UzNQo=
*****************************************************************************************
Starting background timer of 15mins
1. Generate Challenge Token Request
2. Enter Challenge Response for Root Access
3. Show History
4. Exit
Enter CLI Option:
2
Please input the response when you are ready .........................
vxOOQQAAAQEBAAQAAAABAgAEAAAAAAMBYjJ0Y1RHUU1oT09FRlFwN0FxUm0wbXJ3eW9UeUhTWmIrVmlNaHJtbkVqMlJwT09TK1QvTUx2cmtTT2s3em9XK2UNCklJclpFVHdtb3ROci9ac2cveUdCcGFLS0l2MGJRVnFxbndIckppM2kzWlJweU5DdDQ5bERlb2oreXpPNlZ3MEMNCmxYT2dackRLRUFCMlZWUUpsU1FOZ3BiNmxSZEs1bFZtSVhwem9FaUpTRGlWZ1U5RlNhTlQwRGZRbURGclVKbGQNCjdYRjFQeDVteVpScjhUVDk5V0pUN2ZhT2drRkhpVW9xOG1EelFwejcxVmtSaVNmS0lBOEJjViswN1hRR0pQQysNCjNsR3JULzREYWpzUW1YRmdBUEdoNkVjZmx1Q0VQd3FBVG1MbllMSFRwczFiYm5jdVIxUzN0Wm5GTlpaRHFyYm0NCkNVS2VyUXE5ZW1RemFrZytaU3F6dkE9PQ==
Response Signature Verified successfully !
Granting shell access
sh-4.2# ls
2.4backup config CT_Deme_Test_Rpm
ct_rolling.txt lost+found threadHeapDumpGntr.sh
backup_anc-2.7.0-115.jar corefiles CT_engine-2.7.0-1.0.x86_64.rpm
err.out prrt-server.log tomcat-process-log.txt
backup_guestaccess-upgrade-2.7.0-115.jar corestacks.txt ct_persistent.txt
Heap_dump20190705 libciscosafec.so.4.0.1 Thread_dump_2019-07-05-19:07:30
sh-4.2# exit
exit
Root shell exited
1. Generate Challenge Token Request
2. Enter Challenge Response for Root Access
3. Show History
4. Exit
Enter CLI Option:
3
************************************
SN No : 1
************************************
Challenge
3/WcyAAAAQEBAAQAAAABAgAEAAAAAAMACMt89YhCTVWWBAAQwo9lyianfhO4C5u1+v80AQUABAAADhAGAANJU0UHAAZJU0VfQ1QIAANJU0UJACcJIDU2NGQ5NjgwLTFmZmEtOWI0ZS0wZjY1LTdlZDllMGQ1M2UzNQo=
generated at 2019-06-12 15:40:01.000
************************************
SN No : 2
************************************
Challenge
exNwkAAAAQEBAAQAAAABAgAEAAAAAAMACCIBbk3qhsFGBAAQQ4UKV7KrKQ7uoHEq7qPG1AUABAAADhAGAANJU0UHAAZJU0VfQ1QIAANJU0UJACcJIDU2NGQ5NjgwLTFmZmEtOWI0ZS0wZjY1LTdlZDllMGQ1M2UzNQo=
generated at 2019-06-12 15:43:31.000
1. Generate Challenge Token Request
2. Enter Challenge Response for Root Access
3. Show History
4. Exit
Enter CLI Option:
4
Exiting..............
ise/admin#
ping
To diagnose the basic IPv4 network connectivity to a remote system, use the ping command in EXEC mode.
ping {ip-address | hostname} [df df] [packetsize packetsize] [pingcount pingcount]
packetsize Specify the size of the ping packet; the value can be
between 0 and 65507.
Usage Guidelines The ping command sends an echo request packet to an address, and then waits for a reply. The ping output
can help you evaluate path-to-host reliability, delays over the path, and whether or not you can reach a host.
Example
ping6
To diagnose the basic IPv6 network connectivity to a remote system, use the ping6 command in EXEC mode.
This is similar to the IPv4 ping command.
ping6 {ip-address} [GigabitEthernet {0-3}][packetsize {packetsize}] [pingcount {pingcount}]
packetsize Specify the size of the ping packet; the value can be
between 0 and 65507.
Usage Guidelines The ping6 command sends an echo request packet to an address, and then waits for a reply. The ping output
can help you evaluate path-to-host reliability, delays over the path, and whether or not you can reach a host.
The ping6 command is similar to the existing ping command. The ping6 command does not support the IPv4
packet fragmentation (df, as described in the ping command) options, but it allows an optional specification
of an interface. The interface option is primarily useful for pinning with link-local addresses that are
interface-specific addresses. The packetsize and pingcount options work the same way as they do with the
ping command.
Example 1
Example 2
reload
This command has no keywords and arguments. To reboot the Cisco ISE operating system, use the reload
command in EXEC mode.
reload
Usage Guidelines The reload command reboots the system. Use the reload command after you enter configuration information
into a file and save the running-configuration to the persistent startup-configuration on the CLI and save any
settings in the Cisco ISE Admin portal session.
Before you issue the reload command, ensure that Cisco ISE is not performing any backup, restore, installation,
upgrade, or remove operation. If Cisco ISE performs any of these operations and you issue the reload command,
you will get one of the following warning messages:
If you get any of these warnings, enter Yes to continue with the reload operation, or No to cancel it.
If no processes are running when you use the reload command or you enter Yes in response to the warning
message displayed, you must respond to the following question:
If you enter Yes to save the existing Cisco ISE configuration, the following message is displayed:
If you have auto-failover enabled in your deployment, you receive the following warning message:
PAN Auto Failover feature is enabled, therefore
this operation will trigger a failover if ISE services are not
restarted within the fail-over window. Do you want to continue (y/n)?
Example
ise/admin# reload
Do you want to save the current configuration? (yes/no) [yes]? yes
Generating configuration...
Saved the running configuration to startup successfully
Continue with reboot? [y/n] y
Broadcast message from root (pts/0) (Fri Aug 7 13:26:46 2010):
The system is going down for reboot NOW!
ise/admin#
reset-config
To reset the ADE-OS network configurations such as ip address/mask/gateway, hostname, domain name, DNS
server, and NTP server using the reset-config command in EXEC mode. These parameters are essentially the
same parameters as that is prompted during setup. The administrator will not be prompted for admin password
from this CLI. This command will also not reset the current ISE configuration or operations data as these tasks
are achieved by using the application reset-config command.
reset-config
Note Updating the hostname will cause any certificate using the old hostname to become invalid. A new self-signed
certificate using the new hostname will be generated now for use with HTTPS/EAP. If CA-signed certificates
are used on this node, import the new ones with the correct hostname. In addition, if this node is part of an
AD domain, delete any AD memberships before proceeding.
restore
To restore a previous backup of the system, use the restore command in EXEC mode. A restore operation
restores data related to the Cisco ISE and the Cisco ADE OS.
Use the following command to restore data related to the Cisco ISE application and Cisco ADE OS:
restore [{filename} repository {repository-name} encryption-key hash | plain {encryption-key-name}]
restore [{filename} repository {repository-name} encryption-key hash | plain {encryption-key-name}
include-adeos]
Syntax Description filename Name of the backed-up file that resides in the
repository. Supports up to 120 alphanumeric
characters.
Note You must add the .tar.gpg extension after
the filename (for example, myfile.tar.gpg).
If you have the Primary Administration Node (PAN) auto-failover configuration enabled in your deployment,
disable this configuration before you restore a backup. You can enable the PAN auto-failover configuration
after the restore is complete.
Usage Guidelines When you use restore commands in Cisco ISE, the Cisco ISE server restarts automatically.
The encryption key is optional while restoring data. To support restoring earlier backups where you have not
provided encryption keys, you can use the restore command without the encryption key.
If you have the PAN auto-failover configuration enabled in your deployment, the following message appears:
PAN Auto Failover is enabled, this operation is
not allowed! Please disable PAN Auto-failover first.
Note Restoring from Cisco ISE, Release 1.0 and Cisco ISE, Release 1.0 MR backups are not supported in Cisco ISE,
Release 1.2.
Note Cisco ISE, Release 1.4 supports restore from backups obtained from Release 1.2 and later.
Example
Example
Restoring Cisco ISE Configuration Data and Cisco ADE OS data from the Backup
To restore Cisco ISE configuration data including Cisco ISE ADE OS data, use the following command:
restore mybackup-CFG-130405-0044.tar.gpg repository myrepository encryption-key plainMykey123
include-adeos
Example
rmdir
To remove an existing directory, use the rmdir command in EXEC mode.
rmdir directory-name
Example
ssh
To start an encrypted session with a remote system, use the ssh command in EXEC mode.
port number The valid range of ports is from 0 to 65,535. The default
port is 22.
version number The SSH version number 1 and 2. The default SSH
version is 2.
Usage Guidelines The ssh command enables a system to make a secure, encrypted connection to another remote system or
server. With authentication and encryption, the SSH client allows for secure communication over an insecure
network.
Note Cisco ISE initiates outbound SSH or SFTP connections in FIPS mode even if FIPS mode is not enabled on ISE.
Ensure that the remote SSH or SFTP servers that communicate with ISE allow FIPS 140-2 approved cryptographic
algorithms.
Cisco ISE uses embedded FIPS 140-2 validated cryptographic modules. For details of the FIPS compliance
claims, see the FIPS Compliance Letter.
Example 1
Example 2
tech
To dump traffic on a selected network interface, use the tech command in EXEC mode.
tech dumptcp {interface-number | count | package-count}
Usage Guidelines If you see bad UDP cksum warnings in the tech dumptcp output, it may not be a cause for concern. The tech
dumptcp command examines outgoing packets before they exit through the Ethernet microprocessor. Most
modern Ethernet chips calculate checksums on outgoing packets, and so the operating system software stack
does not. Hence, it is normal to see outgoing packets declared as bad UDP cksum.
From Cisco ISE Release 3.0 onwards, the tech dumptcp command has the following options as available
interfaces:
• br-<...>
• docker0
• GigabitEthernet0 (and other GigabitEthernet interfaces if available)
• lo
• veth<...>
Example 1
Example 2
Example 3
terminal length
To set the number of lines on the current terminal screen for the current session, use the terminal length
command in EXEC mode.
terminal length integer
Syntax Description length Sets the number of lines on the current terminal
screen for the current session.
Command Default The default number of lines is 24 on the current terminal screen for the current session.
Usage Guidelines The system uses the length value to determine when to pause during multiple-screen output.
Example
terminal session-timeout
To set the inactivity timeout for all sessions, use the terminal session-timeout command in EXEC mode.
terminal session-timeout minutes
Syntax Description session-timeout Sets the inactivity timeout for all sessions.
Usage Guidelines Setting the terminal session-timeout command to zero (0) results in no timeout being set.
Example
terminal session-welcome
To set a welcome message on the system for all users who log in to the system, use the terminal
session-welcome command in EXEC mode.
terminal session-welcome string
Syntax Description session-welcome Sets a welcome message on the system for all users
who log in to the system.
Usage Guidelines Specify a welcome message that will appear on the screen on top of the command prompt when you log in to
the CLI.
Example
terminal terminal-type
To specify the type of terminal connected to the current line for the current session, use the terminal
terminal-type command in EXEC mode.
terminal terminal-type type
Syntax Description terminal-type Specifies the type of terminal connected. The default
terminal type is VT100.
Example
traceroute
To discover the routes that packets take when traveling to their destination address, use the traceroute
command in EXEC mode.
traceroute [ip-address | hostname]
Example
undebug
To disable debugging functions, use the undebug command in EXEC mode.
undebug [ all | application | backup-restore | cdp | config | copy | icmp | locks | logging | snmp | system |
transfer | user | utils]
Example
which
To display the contents of commands available in admin CLI, use the which command in EXEC mode.
which
Usage Guidelines which is a hidden command. Although which is available in Cisco ISE, the CLI interactive Help does not display
it if you attempt to view it by entering a question mark at the command line.
Example
The following example shows the output of which :
ise/admin# which
[ 1]. application configure<STRING>
[ 2]. application install<STRING><STRING>
[ 3]. application remove<STRING>
[ 4]. application reset-config<STRING>
[ 5]. application reset-passwd<STRING><STRING>
[ 6]. application start<STRING>
[ 7]. application start<STRING> safe
[ 8]. application stop<STRING>
[ 9]. application upgrade cleanup
[ 10]. application upgrade prepare<STRING><STRING>
write
To copy, display, or erase Cisco ISE server configurations, use the write command with the appropriate
argument in EXEC mode.
write [ erase | memory | terminal ]
Usage Guidelines Using the write command with the erase option is disabled in Cisco ISE.
If you use the write command with the erase option, Cisco ISE displays the following error message:
Example 1
Example 2
Note From Cisco ISE Release 3.0 onwards, if there is an escape character required after running certain show
commands, press Ctrl+C and then press Q.
show
To show the running system information, use the show command in EXEC mode.
show keyword
Usage Guidelines All show commands require at least one keyword to function.
Example
show application
To show installed application packages on the system, use the show application command in EXEC mode.
show application > file-name
show application [status {application_name}]
show application [version {application_name}]
Usage Guidelines To view the application status and version about installed packages on the system, use the show application
commands.
Example 1
Example 1
Example 2
Example 2
Example 3
Cisco ISE includes the status of processes that are optional (persona-based). Processes like pxGrid, Certificate
Authority, M&T, and Identity Mapping Services can be in any one of the following states:
• Running—Cisco ISE services are up and running
• Not Running—Cisco ISE services are shut down
• Disabled—Cisco ISE services are disabled
Example 4
Example 5
show backup
To display the backup history of the system or the status of the backup, use the show backup command in
EXEC mode.
show backup [history | status]
Usage Guidelines To view the system backup history and status, use the show backup command.
Example 1
Example 2
ise/admin# show backup status
%% Configuration backup status
%% ----------------------------
% backup name: mybackup
% repository: myrepository
% start date: Wed Apr 10 02:26:04 EDT 2013
% scheduled: no
% triggered from: Admin web UI
% host: ise.cisco.com
% status: backup mybackup-CFG-130410-0226.tar.gpg to repository myrepository:
success
%% Operation backup status
%% ------------------------
% backup name: mybackup1
% repository: myrepository
% start date: Wed Apr 10 02:39:02 EDT 2013
% scheduled: no
% triggered from: Admin web UI
% host: ise.cisco.com
% status: backup mybackup1-OPS-130410-0239.tar.gpg to repository myrepository:
success
ise/admin#
show banner
To display pre-login and post-login banners, use the show banner command in EXEC mode.
show banner [post-login | pre-login]
Usage Guidelines Use the show banner command in the active SSH sessions. If the active SSH sessions exceed the Maximum
Concurrent Sessions that is configured in the Cisco ISE Admin portal, you get the “WARNING: Maximum active
ssh sessions reached” message.
show cdp
To display information about all enabled Cisco Discovery Protocol (CDP) interfaces, use the show cdp command
in EXEC mode.
show cdp [all | neighbors]
Usage Guidelines To view enabled Cisco Discovery Protocol interfaces and CDP neighbors, use the show cdp command.
Note CDP can be visualized from neighboring IPv4 and IPv6 interfaces
Example 1
Example 2
show clock
To display the day, month, date, time, time zone, and year of the system software clock, use the show clock
command in EXEC mode.
This command has no keywords and arguments.
show clock
Usage Guidelines The show clock output in the following example includes Coordinated Universal Time (UTC) or Greenwich
Mean Time (GMT), Great Britain, or Zulu time.
Example
show container
To view information about the Threat-Centric NAC adapters and Wifi setup, use the show container command
in EXEC mode.
The output of this command provides statistical information about the vulnerability assessment scans, when
the adapters were created, how long the adapters were running, and their current statuses. You can further
view information about each of the adapters in detail based on the container name or ID.
show container {tc-nac {adapters | all | inspect {container-id container-id | container-name container-name}
| stats {container-id container-id | container-name container-name}} | wifi setup all}
all When used with TC NAC, lists all the adapters that are
available in Cisco ISE, including the container name
and ID.
When used with Wi-Fi Setup, displays the Wi-Fi
container setup information.
inspect{container-id container-id | container-name Lists detailed information about the specific adapter.
container-name}
stats {container-id container-id | container-name Provides statistical information about the specific
container-name} adapter.
Usage Guidelines To view information about the Threat-Centric NAC adapters, use the show container command.
Example 1
ise/admin#
Example 2
Up 19 hours nexpose
8389f7e249cf irf-adapter-tenable "/opt/CSCOcpm/vaservi" 2 days ago
Up 2 days tenable
41921c1539bf irf-core-engine:2.2.6 "/bin/sh -c 'npm star" 3 days ago
Up 3 days 127.0.0.1:3000->3000/tcp
irf-core-engine-runtime
c4f6ff3cf628 irf-rabbitmq:2.2.6 "/docker-entrypoint.s" 3 days ago
Up 3 days 4369/tcp, 5671-5672/tcp, 15671-15672/tcp, 25672/tcp irf-rabbitmq-runtime
e682a5a5ad69 irf-mongo:2.2.6 "/entrypoint.sh mongo" 3 days ago
Up 3 days 27017/tcp irf-mongo-runtime
ise/admin#
Example 3
"HostnamePath":
"/opt/docker/runtime/containers/63b8904f41c6ce2a58660d38eb3500104038e650e4e3365e21e0a536a1ba3044/hostname",
"HostsPath":
"/opt/docker/runtime/containers/63b8904f41c6ce2a58660d38eb3500104038e650e4e3365e21e0a536a1ba3044/hosts",
"LogPath":
"/opt/docker/runtime/containers/63b8904f41c6ce2a58660d38eb3500104038e650e4e3365e21e0a536a1ba3044/
63b8904f41c6ce2a58660d38eb3500104038e650e4e3365e21e0a536a1ba3044-json.log",
"Name": "/nexpose",
"RestartCount": 0,
"Driver": "devicemapper",
"ExecDriver": "native-0.2",
"MountLabel": "",
"ProcessLabel": "",
"AppArmorProfile": "",
"ExecIDs": [
"d76578aa48118167d9d029037fcb2e56aa7dce8672b8991a736617a6d6879750"
],
.
.
.
"NetworkSettings": {
"Bridge": "",
"SandboxID": "9873fb92f86e665039a6de15bfe057bc3fd341f7b39acedee57cbd89b3f56ce0",
"HairpinMode": false,
"LinkLocalIPv6Address": "",
"LinkLocalIPv6PrefixLen": 0,
"Ports": {},
"SandboxKey": "/var/run/docker/netns/9873fb92f86e",
"SecondaryIPAddresses": null,
"SecondaryIPv6Addresses": null,
"EndpointID": "",
"Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"IPAddress": "",
"IPPrefixLen": 0,
"IPv6Gateway": "",
"MacAddress": "",
"Networks": {
"irf-internal-nw": {
"EndpointID":
"8999c12319144cfd66a4e99be40f7fbc228779e43f2a7f20c48867b8b3ca7a49",
"Gateway": "169.254.1.1",
"IPAddress": "169.254.1.6",
"IPPrefixLen": 24,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"MacAddress": "02:42:a9:fe:01:06"
}
}
}
}
]
Example 4
Example 5
show cpu
To display CPU information, use the show cpu command in EXEC mode.
To show a summary of CPU usage per Cisco ISE component, use the show cpu usage command in EXEC mode.
The output of this command provides a snapshot of CPU usage at the moment the command is run.
show cpu > file-name
show cpu statistics
show cpu usage
cpu usage Displays the CPU usage per component for an installed
application (Cisco ISE).
Usage Guidelines To view CPU information and its statistics, use the show cpu command.
Example 1
Example 2
Example 3
show crypto
To display information about the public keys and authorized keys for the logged in administrators and users,
use the show crypto command.
show crypto authorized_keys
show crypto host-keys
show crypto key
Syntax Description authorized_keys Displays authorized keys information for the user who
is logged in currently.
Usage Guidelines To view authorized keys and keys for currently logged in users, use the show crypto command.
Example 1
Example 2
show disks
To display the disks file-system information, use the show disks command in EXEC mode.
show disks > file-name
Usage Guidelines Only platforms that have a disk file system support the show disks command.
Example
show icmp-status
To display the Internet Control Message Protocol (ICMP) echo response configuration information, use the
show icmp_status command in EXEC mode.
show icmp_status > file-name
Usage Guidelines To view the Internet Control Message Protocol (ICMP) echo response configuration information, use the show
icmp_status command.
Example 1
Example 2
show interface
To display the usability status of interfaces configured for IP, use the show interface command in EXEC mode.
show interface > file-name
show interface GigabitEthernet {0-3}
Usage Guidelines In the show interface GigabitEthernet 0 output, you can find that the interface has three IPv6 addresses. The
first internet address (starting with 3ffe) is the result of using stateless autoconfiguration. For this to work, you
need to have IPv6 route advertisement enabled on that subnet. The next address (starting with fe80) is a link
local address that does not have any scope outside the host. You always see a link local address regardless
of the IPv6 autoconfiguration or DHCPv6 configuration. The last address (starting with 2001) is the result
obtained from a IPv6 DHCP server.
Example 1
Example 2
show inventory
To display information about the hardware inventory, including the Cisco ISE appliance model and serial
number, use the show inventory command in EXEC mode.
show inventory > file-name
Usage Guidelines To view the Cisco ISE appliance information, use the show inventory command.
Example
show ip
To display the IP route information, use the show ip command in EXEC mode.
show ip route
Example
Example 1
Example 2
show logging
To display the state of system logging (syslog) and the contents of the standard system logging buffer, use the
show logging command in EXEC mode.
show logging > file-name
show logging application application-logfile-name
show logging container tc-nac {container-id container-id [log-name name-of-log-file tail] | container-name
container-name}
show logging internal
show logging system system-logfile-name
container-id container-id [log-name name-of-log-file Displays the log files related to the specified container
tail] (TC-NAC adapter).
container-name container-name Displays the log files related to the specified container
(TC-NAC adapter).
Usage Guidelines This command displays the state of syslog error and event logging, including host addresses, and for which,
logging destinations (console, monitor, buffer, or host) logging is enabled. When you run this command, the
content is opened in the Unix less evironment. Typing "H" displays the search and movement commands.
Example 1
ise/admin# show logging system
0 Feb 25 2013 15:57:43 tallylog
1781 Feb 26 2013 02:01:02 maillog
4690 Feb 26 2013 02:40:01 cron
0 Feb 25 2013 15:56:54 spooler
0 Feb 25 2013 16:10:03 boot.log
0 Feb 25 2013 16:00:03 btmp
38784 Feb 26 2013 02:19:48 wtmp
16032 Feb 26 2013 02:19:47 faillog
32947 Feb 26 2013 00:38:02 dmesg
63738 Feb 26 2013 02:19:49 messages
146292 Feb 26 2013 02:19:48 lastlog
13877 Feb 26 2013 01:48:32 rpmpkgs
129371 Feb 26 2013 02:40:22 secure
27521 Feb 25 2013 16:10:02 anaconda.syslog
345031 Feb 25 2013 16:10:02 anaconda.log
0 Jul 28 2011 00:56:37 mail/statistics
1272479 Feb 26 2013 02:42:52 ade/ADE.log
Example 2
To view application log files on Cisco ISE nodes, use the following command:
show logins
To display the state of system logins, use the show logins command in EXEC mode.
show logins cli
Example
show memory
To display the memory usage of all running processes, use the show memory command in EXEC mode.
This command has no keywords and arguments.
show memory
Usage Guidelines To view used memory, use the show memory command.
Example
show ntp
To show the status of the Network Translation Protocol (NTP) associations, use the show ntp command in
EXEC mode.
This command has no keywords and arguments.
show ntp
Usage Guidelines To view the Network Translation Protocol (NTP) associations, use the show ntp command.
Example
show ports
To display information about all processes listening on active ports, use the show ports command in EXEC
mode.
show ports > file-name
Usage Guidelines When you run the show ports command, the port must have an associated active session.
Example
show process
To display information about active processes, use the show process command in EXEC mode.
show process > file-name
Field Description
Example
show repository
To display the file contents of the repository, use the show repository command in EXEC mode.
show repository repository-name
Syntax Description repository-name Name of the repository whose contents you want to
view. Supports up to 30 alphanumeric characters.
Usage Guidelines To view the contents of the repository, use the show repository command.
Example
Note To use this command for an SFTP repository, the admin needs to generate the public key from the ISE CLI in
addition to generating it from the ISE GUI. This is required because when the SFTP repository is configured
from the ISE GUI, the public key on ISE is generated for the root user only and not for the admin user (user
with which all commands can be run from the CLI). Follow these steps to verify and configure the public key
from the ISE CLI:
1. Verify whether the crypto key is yet generated or not. If the output for the following command is empty it
means that the crypto key is not generated.
ise24/admin# show crypto key
2. Hence from the CLI EXEC mode generate the key using the command: crypto key generate rsa passphrase
<secretkey>.
3. From the following we can now confirm that the crypto key is generated successfully:
ise24/admin# show crypto key
admin public key: ssh-rsa SHA256:eEziR/ARPyFo1WptgI+y5WNjGIrgfPmEpEswVY7Qjb0 admin@ise24
4. After this, the admin needs to export the public key for 'admin’ user using the command:crypto key export
<sample-name> repository <another-repository-name>.
5. Now open the file saved to the <another-repository-name> and add it to
/home/<username>/.ssh/authorized_keys folder in the SFTP server.
show restore
To display the restore history and the status of restore, use the show restore command in EXEC mode.
show restore {history | status}
show running-config
To display the contents of the currently running configuration file or the configuration, use the show
running-config command in EXEC mode.
This command has no keywords and arguments.
show running-config
Usage Guidelines The show running-config command displays all of the running configuration information.
Example
Example
ise/admin#
Example
ise/admin#
show startup-config
To display the contents of the startup configuration file or the configuration, use the show startup-config
command in EXEC mode.
This command has no keywords and arguments.
show startup-config
Usage Guidelines The show startup-config command displays all of the startup configuration information.
Example
!
ise/admin#
show tech-support
To display technical support information, including e-mail, use the show tech-support command in EXEC mode.
show tech-support > file-name
show tech-support file file-name
Command Default Passwords and other security information do not appear in the output.
Usage Guidelines The show tech-support command is useful for collecting a large amount of information about the Cisco ISE
server for troubleshooting purposes. You can then provide output to technical support representatives when
reporting a problem.
Example
*****************************************
Displaying Clock ...
*****************************************
Tue Oct 21 11:24:08 IST 2014
*****************************************
Displaying UDI ...
*****************************************
ISE-VM-K9
*****************************************
Displaying ISE application status ....
*****************************************
Example
*****************************************
Displaying Clock ...
*****************************************
Mon Mar 16 03:51:35 UTC 2015
*****************************************
Displaying UDI ...
*****************************************
ISE-VM-K9
*****************************************
Displaying ISE application status ....
*****************************************
ISE PROCESS NAME STATE PROCESS ID
--More--
(press Spacebar to continue)
ise/admin#
show terminal
To obtain information about the terminal configuration parameter settings, use the show terminal command
in EXEC mode.
This command has no keywords and arguments.
show terminal
Usage Guidelines The following table describes the fields of the show terminal output.
Field Description
Session Timeout: 30 minutes Length of time, in minutes, for a session, after which
the connection closes.
Example
show timezone
To display the time zone as set on the system, use the show timezone command in EXEC mode.
This command has no keywords and arguments.
show timezone
This command has no keywords and arguments.
show timezones
To obtain a list of time zones from which you can select, use the show timezones command in EXEC mode.
This command has no keywords and arguments.
show timezones
Usage Guidelines See the clock timezone section, for examples of the time zones available for the Cisco ISE server.
Example
show udi
To display information about the Unique Device Identifier (UDI) of the Cisco ISE appliance, use the show udi
command in EXEC mode.
This command has no keywords and arguments.
show udi
Example 2
The following output appears when you run the show udi command on VMware servers.
show uptime
To display the length of time, the Cisco ISE server has been up since the last reboot, use the show uptime
command in EXEC mode.
show uptime > file-name
Usage Guidelines Use this show uptime to check for how long the Cisco ISE server has been up since the last reboot.
Example
show users
To display the list of users logged in to the Cisco ISE server, use the show users command in EXEC mode.
show users > file-name
Usage Guidelines Use this show users command to check the list of users logged into the Cisco ISE server.
Example
show version
To display information about the software version of the system and software installation information, use the
show version command in EXEC mode.
show version > file-name
show version history
Usage Guidelines This command displays version information about the Cisco ADE-OS software running in the Cisco ISE server,
and also displays the Cisco ISE version.
Example 1
ise/admin# show version
ise/admin#
Example 2
ise/admin# show version history
---------------------------------------------
Install Date: Wed Jul 26 19:02:13 UTC 2017
Application: ise
Version: 2.3.0.297
Install type: Application Install
Bundle filename: ise.tar.gz
Repository: SystemDefaultPkgRepos
ise/admin#
Step 2 Enter a question mark (?) to obtain a listing of commands in the configuration mode.
ise/admin(config)# ?
Configure commands:
cdp CDP Configuration parameters
clock Configure timezone
conn-limit Configure a TCP connection limit from source IP
do EXEC command
end Exit from configure mode
exit Exit from configure mode
hostname Configure hostname
icmp Configure icmp echo requests
interface Configure interface
ip Configure IP features
kron Configure command scheduler
logging Configure system logging
max-ssh-sessions Configure number of concurrent SSH sessions
no Negate a command or set its defaults
ntp Specify NTP configuration
password-policy Password Policy Configuration
rate-limit Configure a TCP/UDP/ICMP packet rate limit from source IP
repository Configure Repository
service Specify service to manage
snmp-server Configure snmp server
synflood-limit Configure a TCP SYN packet rate limit
username User creation
Step 3 Enter into the configuration submode. The configuration mode has several configuration submodes. Each of these submodes
places you deeper in the prompt hierarchy. From this level, you can enter commands directly into the Cisco ISE configuration.
Step 4 Enter exit in sequence at the command prompt to exit both Configuration and EXEC modes. When you enter exit, Cisco
ISE backs you out one level and returns you to the previous level. When you enter exit again, Cisco ISE backs you out to
the EXEC level.
ise/admin(config)# exit
ise/admin# exit
Step 3 Enter exit at the command prompt to exit both configuration submode and configuration mode.
ise/admin(config-GigabitEthernet)# exit
ise/admin(config)# exit
ise/admin#
backup interface
To configure two Ethernet interfaces in to a single virtual interface for high availability (also called as the NIC
bonding or NIC teaming feature), use the backup interface command in configuration submode. To remove
the NIC bonding configuration, use the no form of this command. When two interfaces are bonded, the two
NICs appear to be a single device with a single MAC address.
The NIC bonding feature in Cisco ISE does not support load balancing or link aggregation features. Cisco ISE
supports only the high availability feature of NIC bonding.
The bonding of interfaces ensures that Cisco ISE services are not affected when there is:
• Physical interface failure
• Loss of switch port connectivity (shut or failure)
• Switch line card failure
When two interfaces are bonded, one of the interfaces becomes the primary interface and the other becomes
the backup interface. When two interfaces are bonded, all traffic normally flows through the primary interface.
If the primary interface fails for some reason, the backup interface takes over and handles all the traffic. The
bond takes the IP address and MAC address of the primary interface.
When you configure the NIC bonding feature, Cisco ISE pairs fixed physical NICs to form bonded NICs. The
following table outlines which NICs can be bonded together to form a bonded interface.
Cisco ISE Physical NIC Linux Physical NIC Name Role in Bonded NIC Bonded NIC Name
Name
The NIC bonding feature is supported on all supported platforms and node personas. The supported platforms
include:
• SNS-3400 series appliances - Bond 0 and 1 (Cisco ISE 3400 series appliances support up to 4 NICs)
• SNS-3500 series appliances - Bond 0, 1, and 2
• VMware virtual machines - Bond 0, 1, and 2 (if six NICs are available to the virtual machine)
• Linux KVM nodes - Bond 0, 1, and 2 (if six NICs are available to the virtual machine)
Usage Guidelines • As Cisco ISE supports up to six Ethernet interfaces, it can have only three bonds, bond 0, bond 1, and
bond 2.
• You cannot change the interfaces that are part of a bond or change the role of the interface in a bond.
Refer to the above table for information on which NICs can be bonded together and their role in the bond.
• The Eth0 interface acts as both the management interface as well as the runtime interface. The other
interfaces act as runtime interfaces.
• Before you create a bond, the primary interface (primary NIC) must be assigned an IP address. The Eth0
interface must be assigned an IPv4 address before you create bond 0. Similarly, before you create bond
1 and 2, Eth2 and Eth4 interfaces must be assigned an IPv4 or IPv6 address, respectively.
• Before you create a bond, if the backup interface (Eth1, Eth3, and Eth5 ) has an IP address assigned,
remove the IP address from the backup interface. The backup interface should not be assigned an IP
address.
• You can choose to create only one bond (bond 0) and allow the rest of the interfaces to remain as is. In
this case, bond 0 acts as the management interface and runtime interface, and the rest of the interfaces
act as runtime interfaces.
• You can change the IP address of the primary interface in a bond. The new IP address is assigned to the
bonded interface because it assumes the IP address of the primary interface.
• When you remove the bond between two interfaces, the IP address assigned to the bonded interface is
assigned back to the primary interface.
• If you want to configure the NIC bonding feature on a Cisco ISE node that is part of a deployment, you
must deregister the node from the deployment, configure NIC bonding, and then register the node back
to the deployment.
• If a physical interface that acts as a primary interface in a bond (Eth0, Eth2, or Eth4 interface) has static
route configured, the static routes are automatically updated to operate on the bonded interface instead
of the physical interface.
Note If a physical interface that acts as a backup interface (for example, Eth1, Eth3, Eth5 interfaces), is configured
with an IP address, you must remove the IP address from the backup interface. The backup interface should
not be assigned an IP address.
!
interface GigabitEthernet 0
ipv6 address autoconfig
ipv6 enable
backup interface GigabitEthernet 1
ip address 192.168.118.214 255.255.255.0
!
In the output above, "backup interface GigabitEthernet 1" indicates that NIC bonding is configured on Gigabit
Ethernet 0, with Gigabit Ethernet 0 being the primary interface and Gigabit Ethernet 1 being the backup interface.
Also, the ADE-OS configuration does not display an IP address on the backup interface in the running config,
even though the primary and backup interfaces effectively have the same IP address.
You can also run the show interfaces command to see the bonded interfaces.
GigabitEthernet 0
flags=6211<UP,BROADCAST,RUNNING,SUBORDINATE,MULTICAST> mtu 1500
ether 88:5a:92:88:4a:ea txqueuelen 1000 (Ethernet)
RX packets 1726027 bytes 307336369 (293.0 MiB)
RX errors 0 dropped 844 overruns 0 frame 0
TX packets 1295620 bytes 1073397536 (1023.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xfab00000-fabfffff
GigabitEthernet 1
flags=6147<UP,BROADCAST,SUBORDINATE,MULTICAST> mtu 1500
ether 88:5a:92:88:4a:ea txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xfaa00000-faafffff
cdp holdtime
To specify the amount of time for which the receiving device should hold a Cisco Discovery Protocol packet
from the Cisco ISE server before discarding it, use the cdp holdtime command in configuration mode.
cdp holdtime seconds
To revert to the default setting, use the no form of this command.
no cdp holdtime
Syntax Description holdtime Specifies the Cisco Discovery Protocol hold time
advertised.
Usage Guidelines Cisco Discovery Protocol packets transmit with a time to live, or hold time, value. The receiving device will
discard the Cisco Discovery Protocol information in the Cisco Discovery Protocol packet after the hold time
has elapsed.
The cdp holdtime command takes only one argument; otherwise, an error occurs.
Example
cdp run
To enable the Cisco Discovery Protocol on all interfaces, use the cdp run command in configuration mode.
cdp run GigabitEthernet
To disable the Cisco Discovery Protocol, use the no form of this command.
no cdp run
Syntax Description run Enables the Cisco Discovery Protocol. Disables the
Cisco Discovery Protocol when you use the no form
of the cdp run command.
Usage Guidelines The command has one optional argument, which is an interface name. Without an optional interface name,
the command enables the Cisco Discovery Protocol on all interfaces.
Note The default for this command is on interfaces that are already up and running. When you are bringing up an
interface, stop the Cisco Discovery Protocol first; then, start the Cisco Discovery Protocol again.
Example
cdp timer
To specify how often the Cisco ISE server sends Cisco Discovery Protocol updates, use the cdp timer command
in configuration mode.
cdp timer seconds
To revert to the default setting, use the no form of this command.
no cdp timer
Command Default The default refreshing time interval value, in seconds is 60.
Usage Guidelines Cisco Discovery Protocol packets transmit with a time to live, or hold time, value. The receiving device will
discard the Cisco Discovery Protocol information in the Cisco Discovery Protocol packet after the hold time
has elapsed.
The cdp timer command takes only one argument; otherwise, an error occurs.
Example
clear screen
To clear the contents of terminal screen, use the clear screen command in configuration mode.
clear screen
Usage Guidelines clear screen is a hidden command. Although clear screen is available in Cisco ISE, the CLI interactive Help
does not display it if you attempt to view it by entering a question mark at the command line.
Example
The following example shows how to clear the contents of the terminal:
clock timezone
To set the time zone, use the clock timezone command in configuration mode.
clock timezone timezone
To disable the time zone, use the no form of this command.
no clock timezone
Note Changing the time zone on a Cisco ISE appliance after installation causes the Cisco ISE application on that
node to be unusable, which requires you to restart ISE. We recommend that you use the preferred time zone
(default UTC) during the installation when the initial setup wizard prompts you for the time zones.
If you have the primary Administration node (PAN) auto-failover configuration enabled, disable it before you
set the time zone. You can enable it after the time zone is set.
Usage Guidelines The system internally keeps time in UTC. If you do not know your specific time zone, you can enter the region,
country, and city (see Tables 4-1, 4-2, and 4-3 for common time zones and time zones for Australia and Asia
to enter on your system).
Note Several more time zones are available to you. Enter show timezones and a list of all time zones available
appears in the Cisco ISE server. Choose the most appropriate one for your time zone.
If you have the PAN auto-failover configuration enabled in your deployment, the following message appears:
PAN Auto Failover is enabled, this operation is not
allowed! Please disable PAN Auto-failover first.
Example
EST
ise/admin#
Europe
GMT, GMT0, GMT-0, GMT+0, UTC, Greenwich, Greenwich Mean Time, as UTC
Universal, Zulu
GB British
Note Enter the country and city together with a forward slash (/) between them for the Australia time zone; for
example, Australia/Currie.
Australia
West Yancowinna
Note The Asia time zone includes cities from East Asia, Southern Southeast Asia, West Asia, and Central Asia. Enter
the region and city or country together separated by a forward slash (/); for example, Asia/Aden.
Asia
Kuwait Krasnoyarsk
cls
To clear the contents of terminal screen, use the cls command in configuration mode.
cls
Usage Guidelines cls is a hidden command. Although cls is available in Cisco ISE, the CLI interactive Help does not display it if
you attempt to view it by entering a question mark at the command line.
Example
The following example shows how to clear the contents of the terminal:
ise/admin(config)# cls
ise/admin#
conn-limit
To configure the limit of incoming TCP connections from a source IP address, use the conn-limit command in
configuration mode. To remove this function, use the no form of this command.
Usage Guidelines Use this conn-limit command for more than 99 TCP connections. For less than 100 connections, the system
displays the following warning:
% Warning: Setting a small conn-limit may adversely affect system performance
Example
dns cache
To cache the DNS requests for hosts, use the service cache enable command in configuration mode. Enabling
this feature will reduce the load on DNS server.
service cache enable hosts ttl ttl
To disable this feature, use the no form of this command.
Syntax Description ttl You can configure the Time to Live (TTL) value, in
seconds, for a host in the cache while enabling the
cache. There is no default setting for ttl. The valid
range for ttl is from 1 to 2147483647.
Usage Guidelines TTL value is honored for negative responses. The TTL value set in the DNS server is honored for positive
responses. If there is no TTL defined on the DNS server, then the TTL configured from the command is honored.
Cache can be invalidated by disabling the feature.
Example
ise/admin(config)# service cache enable hosts ttl 10000
Enabling dns cache
ise/admin(config)# exit
do
To execute an EXEC-system level command from configuration mode or any configuration submode, use the
do command in any configuration mode.
do EXEC commands
Command Description
backup Performs a backup (Cisco ISE and Cisco ADE OS) and
places the backup in a repository.
Command Description
terminal session-timeout Sets the inactivity timeout for all terminal sessions.
terminal session-welcome Sets the welcome message on the system for all
terminal sessions.
Command Description
Command Modes Configuration (config)# or any configuration submode (config-GigabitEthernet)# and (config-Repository)#
Usage Guidelines Use this do command to execute EXEC commands (such as show, clear, and debug commands) while configuring
the Cisco ISE server. After the EXEC command is executed, the system will return to configuration mode you
were using.
Example
!
--More--
ise/admin(config)#
end
To end the current configuration session and return to EXEC mode, use the end command in configuration
mode.
This command has no keywords and arguments.
end
Usage Guidelines This command brings you back to EXEC mode regardless of what configuration mode or submode you are in.
Use this command when you finish configuring the system and you want to return to EXEC mode to perform
verification steps.
Example
ise/admin(config)# end
ise/admin#
exit
To exit any configuration mode to the next-highest mode in the CLI mode hierarchy, use the exit command in
configuration mode.
exit
This command has no keywords and arguments.
Usage Guidelines The exit command is used in the Cisco ISE server to exit the current command mode to the next highest
command mode in the CLI mode hierarchy.
For example, use the exit command in configuration mode to return to EXEC mode. Use the exit command in
the configuration submodes to return to configuration mode. At the highest level, EXEC mode, the exit command
exits EXEC mode and disconnects from the Cisco ISE server.
Example
ise/admin(config)# exit
ise/admin#
hostname
To set the hostname of the system, use the hostname command in configuration mode.
hostname hostname
Usage Guidelines
Note If 'Ctrl-C' is issued during the CLI configuration change of 'hostname' command, the system might end up in
a state where some application components might have the old hostname while some components might use
the new hostname. This will bring the Cisco ISE node to a non-working state.
The workaround for this issue is to run the 'hostname' configuration command again to set the hostname to
the desired value.
You can use the hostname command to change the current hostname. A single instance type of command,
hostname only occurs once in the configuration of the system. The hostname must contain one argument;
otherwise, an error occurs.
When you update the hostname of the Cisco ISE server with this command, the following warning message
is displayed:
% Warning: Updating the hostname will cause any certificate using the old
% hostname to become invalid. Therefore, a new self-signed
% certificate using the new hostname will be generated now for
% use with HTTPs/EAP. If CA-signed certs were used on this node,
% please import them with the correct hostname. If Internal-CA
% signed certs are being used, please regenerate ISE Root CA certificate.
% In addition, if this ISE node will be joining a new Active Directory
% domain, please leave your current Active Directory domain before
% proceeding. If this ISE node is already joined to
% an Active Directory domain, then it is strongly advised
% to rejoin all currently joined join-points in order to
% avoid possible mismatch between current and previous
% hostname and joined machine account name.
Example
icmp echo
To configure the Internet Control Message Protocol (ICMP) echo responses, use the icmp echo command in
configuration mode.
icmp echo {off | on}
Command Default The system behaves as if the ICMP echo response is on (enabled).
Usage Guidelines Use this icmp echo to turn on or turn off ICMP echo response.
Example
identity-store
To join a CLI Administrator to an Active Directory domain, use the identity-store command in config mode. If
the Cisco ISE node has joined multiple domains, you can only join one domain with this command. Each CLI
Administrator joins individually. Please allow five minutes for Cisco ISE to complete the operation.
If the domain you join with this command is the same as the one that was joined to the ISE node, then you must
rejoin the domain in the Administrators console. The Admin CLI user must be a Super Admin.
Example
identity-store active-directory domain-name <aDomainFQDN> user <adUserNameWithJoinPrivs>
Note Active Directory CLI does not support authentication using child domain users. Child domain is considered as
a separate domain which needs to be explicitly joined for its corresponding users to be used for authentication.
interface
To configure an interface type and enter the interface configuration mode, use the interface command in
configuration mode. This command does not have a no form.
Note VMware virtual machine may have a number of interfaces available that depends on how many network
interfaces (NIC) are added to the virtual machine.
interface GigabitEthernet {0 | 1 | 2 | 3}
Note After you enter the Gigabit Ethernet port number in the interface command, you enter the config-GigabitEthernet
configuration submode (see the following Syntax Description).
Syntax Description backup Configures the NIC bonding feature to provide high
availability for the physical interfaces.
Usage Guidelines You can use the interface command to configure the interfaces to support various requirements.
Example
ip address
To set the IP address and netmask for the GigabitEthernet interface, use the ip address command in interface
configuration mode.
ip address ip-address network mask
To remove an IP address or disable IP processing, use the no form of this command.
no ip address
Note You can configure the same IP address on multiple interfaces. You might want to do this to limit the configuration
steps that are needed to switch from using one interface to another.
If you have the primary Administration node (PAN) auto-failover configuration enabled, disable it before you
set the IP address. You can enable the PAN auto-failover configuration after the IP address is configured.
Usage Guidelines
Note If 'Ctrl-C' is issued during the CLI configuration change of 'ip address' command, in case of IP address change
the system may end up in a state where some application components have the old IP address, and some
components use the new IP address.
This will bring the Cisco ISE node into a non-working state. The workaround for this is to issue another 'ip
address' configuration CLI to set the IP address to the desired value.
Requires exactly one address and one netmask; otherwise, an error occurs.
If you have the PAN auto-failover configuration enabled in your deployment, the following message appears:
PAN Auto Failover is enabled, this operation is not
allowed! Please disable PAN Auto-failover first.
Example
ip default-gateway
To define or set a default gateway with an IP address, use the ip default-gateway command in configuration
mode.
ip default-gateway ip-address
To disable this function, use the no form of this command.
no ip default-gateway
Usage Guidelines If you enter more than one argument or no arguments at all, an error occurs.
Example
ip domain-name
To define a default domain name that the Cisco ISE server uses to complete hostnames, use the ip domain-name
command in configuration mode.
ip domain-name domain-name
To disable this function, use the no form of this command.
no ip domain-name
Usage Guidelines
Note If 'Ctrl-C' is issued during the CLI configuration change of 'ip domain-name' command, in case of ip domain-name
change the system may end up in a state where some application components have the old domain-name and
some components use the new domain-name.
This will bring the Cisco ISE node into a non-working state. The workaround for this is to issue another 'ip
domain-name' configuration CLI to set the domain name to the desired value.
% Warning: Updating the domain name will cause any certificate using the old
% domain name to become invalid. Therefore, a new self-signed
% certificate using the new domain name will be generated now for
% use with HTTPs/EAP. If CA-signed certs were used on this node,
% please import them with the correct domain name. If Internal-CA
% signed certs are being used, please regenerate ISE Root CA certificate.
% In addition, if this ISE node will be joining a new Active Directory
% domain, please leave your current Active Directory domain before
% proceeding.
Example
ip host
To associate a host alias and fully qualified domain name (FQDN) string to an ethernet interface such as eth1,
eth2, and eth3 other than eth0, use the ip host command in global configuration mode.
When Cisco ISE processes an authorization profile redirect URL, it replaces the IP address with the FQDN of
the Cisco ISE node.
ip host [ipv4-address | ipv6-address] [host-alias | FQDN-string]
To remove the association of host alias and FQDN, use the no form of this command.
no ip host [ipv4-address | ipv6-address] [host-alias | FQDN-string]
host-alias Host alias is the name that you assign to the network
interface.
If you have the Primary Administration Node (PAN) auto-failover configuration enabled, disable it before you
change the host alias and FQDN of an ethernet interface. You can enable the PAN auto-failover configuration
after the host alias and FQDN configuration is complete.
If you have the PAN auto-failover configuration enabled in your deployment, the following message appears:
PAN Auto Failover is enabled, this operation is
not allowed! Please disable PAN Auto-failover first.
Use the ip host command to add host alias and fully qualified domain name (FQDN) string for an IP address
mapping. It is used to find out the matching FQDN for ethernet interfaces such as eth1, eth2, and eth3. Use the
show running-config command to view the host alias definitions.
You can provide either the host alias or the FQDN string, or both. If you provide both the values, the host alias
must match the first component of the FQDN string. If you provide only the FQDN string, Cisco ISE replaces
the IP address in the URL with the FQDN. If you provide only the host alias, Cisco ISE combines the host alias
with the configured IP domain name to form a complete FQDN, and replaces the IP address of the network
interface in the URL with the FQDN.
Example 1
ise/admin(config)# ip host 172.21.79.96 ise1 ise1.cisco.com
Host alias was modified. You must restart ISE for change to take effect.
Do you want to restart ISE now? (yes/no) yes
Stopping ISE Monitoring & Troubleshooting Log Processor...
Stopping ISE Application Server...
Stopping ISE Profiler DB...
Stopping ISE Monitoring & Troubleshooting Session Database...
Stopping ISE Database processes...
Starting ISE Database processes...
Stopping ISE Database processes...
Starting ISE Database processes...
Starting ISE Monitoring & Troubleshooting Session Database...
Starting ISE Profiler DB...
Starting ISE Application Server...
Starting ISE Monitoring & Troubleshooting Log Processor...
Note: ISE Processes are initializing. Use 'show application status ise'
CLI to verify all processes are in running state.
ise/admin(config)#
Example 2
ip mtu
To set the maximum transmission unit (MTU) size of IP packets sent on an interface, use the ip mtu command
in the interface configuration mode. To restore the default MTU size, use the no form of this command.
ip mtu bytes
no ip mtu bytes
Usage Guidelines If an IP packet exceeds the MTU set for the interface, the Cisco ISE will fragment it. All devices on a physical
medium must have the same protocol MTU in order to operate.
Example
The following example shows how to configure the MTU on an interface:
The following example shows the output you can see after configuring the MTU.
ip name-server
To set the Domain Name Server (DNS) for use during a DNS query, use the ip name-server command in
configuration mode. You can configure one to three DNS servers.
ip name-server ip-address {ip-address*}
To disable this function, use the no form of this command.
no ip name-server ip-address {ip-address*}
Note Using the no form of this command removes all the name servers from the configuration. The no form of this
command and one of the IP names removes only that name server.
If you have the primary Administration node (PAN) auto-failover configuration enabled in your deployment,
remove it before you run the ip name-server command and enable it after you configure the DNS server(s).
Usage Guidelines The first name server that is added with the ip name-server command occupies the first position and the
system uses that server first to resolve the IP addresses.
You can add name servers to the system using IPv4 or IPv6 addresses. You can configure one to three IPv4
or IPv6 addresses through a single command. If you have already configured the system with four name
servers, you must remove at least one server to add additional name servers.
To place a name server in the first position so that the subsystem uses it first, you must remove all name servers
with the no form of this command before you proceed.
Note If you modified this setting for AD connectivity, you must restart Cisco ISE for the changes to take effect. Also,
ensure that all DNS servers configured in Cisco ISE are able to resolve all relevant AD DNS records. If the
configured AD join points are not correctly resolved after the DNS settings are changed, you must manually
perform the Leave operation and re-join the AD join point.
If you have the PAN auto-failover configuration enabled in your deployment, the following message appears:
PAN Auto Failover is enabled, this operation is not
allowed! Please disable PAN Auto-failover first.
Example 1
ise/admin(config)# ip name-server ?
<A.B.C.D>|<valid IPv6 format> Primary DNS server IP address
<A.B.C.D>|<valid IPv6 format> DNS server 2 IP address
<A.B.C.D>|<valid IPv6 format> DNS server 3 IP address
ise/admin(config)# ip name-server
Example 2
You can see the following output after you configure the IP name server.
Example 3
ise/admin(config)# ip name-server ?
ip name-server 10.126.107.120 10.126.107.107 10.106.230.244
DNS Server was modified. If you modified this setting for AD connectivity, you must restart
ISE for the change to take effect.
Do you want to restart ISE now? (yes/no)
ip route
To configure the static routes, use the ip route command in configuration mode. To remove static routes, use
the no form of this command.
ip route prefix mask gateway ip-address
no ip route prefix mask
Usage Guidelines Static routes are manually configured, which makes them inflexible (they cannot dynamically adapt to network
topology changes), but extremely stable. Static routes optimize bandwidth utilization, because no routing
updates need to be sent to maintain them. They also make it easy to enforce routing policy.
While the ip route command can be used to define static routes on individual Cisco ISE node, this command
is enhanced to define a default route for each interface and reduce the effects of asymmetrical IP forwarding,
which is inherent in multi-interface IP nodes.
When a single default route is configured on a multi-interface node, all IP traffic received from any of the
node's IP interfaces is routed to the next hop of the default gateway that produces asymmetrical IP forwarding.
Configuring multiple default routes on the Cisco ISE node eliminates the effects of asymmetric forwarding.
The following example describes how to configure multiple default routes:
Consider the following interface configuration on Cisco ISE node eth0, eth1, eth2, and eth3 interfaces
respectively:
ISE InterfaceIPNetworkGateway
192.168.114.10 192.168.114.0 192.168.114.1
192.168.115.10 192.168.115.0 192.168.115.1
192.168.116.10 192.168.116.0 192.168.116.1
192.168.117.10 192.168.117.0 192.168.117.1
The ip route command is used here to define default routes for each interface.
Note The "ip default-gateway" shown above is the route of last resort for all interfaces.
The show ip route command displays the output of the static routes created using the ip route command
(default routes and non-default routes) and system created routes including the one configured using "ip default
gateway" command. It displays the outgoing interface for each of the routes.
Note When you change the IP address of an interface and if any static route becomes unreachable due to an
unreachable gateway, the static route gets deleted from the running configuration. The console displays the
route that has become unreachable.
Example 2
ipv6 address
To configure a static IPv6 address based on an IPv6 general prefix and enable IPv6 processing for an interface,
use the ipv6 address command in interface configuration mode.
ipv6 address ipv6-address/prefix-length
To remove an IPv6 address or disable IPv6 processing, use the no form of this command.
no ipv6 address ipv6-address/prefix-length
If you have the Primary Administration Node (PAN) auto-failover configuration enabled, disable it before you
set the IPv6 address. You can enable the PAN auto-failover configuration after the IPv6 address is configured.
If you have the PAN auto-failover configuration enabled in your deployment, the following message appears:
PAN Auto Failover is enabled, this operation is not
allowed! Please disable PAN Auto-failover first.
Using the fe80 prefix assigns a link-local address. Assigning a global address to the interface automatically
creates a link-local address.
Note If 'Ctrl-C' is issued during the CLI configuration change of ipv6 address command, in case of IPv6 address
change, the system may end up in a state where some application components have the old IPv6 address, and
some components use the new IPv6 address.
This will bring the Cisco ISE node into a non-working state. The workaround for this is to issue another ipv6
address command to set the IPv6 address to the desired value.
Example 1
Example 2
Usage Guidelines IPv6 stateless autoconfiguration has the security downfall of having predictable IP addresses. This downfall
is resolved with privacy extensions. You can verify that the privacy extensions feature is enabled by using the
show interface command.
Example
ise/admin(config-GigabitEthernet)# ipv6 address autoconfig
ise/admin(config)#
When IPv6 autoconfiguration is enabled, the running configuration shows the interface settings similar to the
following:
!
interface GigabitEthernet 0
ip address 172.23.90.116 255.255.255.0
ipv6 address autoconfig
!
You can use the show interface GigabitEthernet 0 command to display the interface settings. In the example
below, you can see that the interface has three IPv6 addresses. The first address (starting with 3ffe) is obtained
using the stateless autoconfiguration.
For the stateless autoconfiguration to work, you must have IPv6 route advertisement enabled on that subnet.
The next address (starting with fe80) is a link-local address that does not have any scope outside the host.
You will always see a link local address regardless of the IPv6 autoconfiguration or DHCPv6 configuration.
The last address (starting with 2001) is obtained from a IPv6 DHCP server.
When IPv6 DHCP is enabled, the running configuration shows the interface settings similar to the following:
!
interface GigabitEthernet 1
ipv6 address dhcp
ipv6 enable
!
Note The IPv6 stateless autoconfiguration and IPv6 address DHCP are not mutually exclusive. It is possible to have
both IPv6 stateless autoconfiguration and IPv6 address DHCP on the same interface.
You can use the show interface command to display what IPv6 addresses are in use for a particular interface.
When both the IPv6 stateless autoconfiguration and IPv6 address DHCP are enabled, the running configuration
shows the interface settings similar to the following:
!
interface GigabitEthernet 1
ipv6 address dhcp
ipv6 address autoconfig
ipv6 enable
!
ipv6 enable
To enable IPv6 on an interface, use the ipv6 enable command in interface configuration mode.
ipv6 enable
Use the no form of this command to disable ipv6 on an interface.
no ipv6 enable
Usage Guidelines Use the ipv6 enable command to enable IPv6 on an interface and automatically generate the link-local address
based on the interface MAC address.
Example 1
Example 2
By default, ipv6 is enabled on all interfaces. If you want to disable it, use the no form of this command.
ipv6 route
To manually configure IPv6 static routes and define an explicit path between two networking devices, use the
ipv6 route command in global configuration mode. Static routes are not automatically updated and you must
manually reconfigure the static routes if the network topology changes.
ipv6 route ipv6-address/prefix-length gateway route-specific gateway
To remove an IPv6 static route, use the no form of this command.
no ipv6 route ipv6-address/prefix-length gateway route-specific gateway
To configure a default static route with an IPv6 address, use the ipv6 route ::/0 gateway route-specific gateway
command in global configuration mode. To disable the default static route with an IPv6 address, use the no
form of this command.
route-specific gateway IPv6 address of the next hop that can be used to reach
that network.
Use the show ipv6 route command to view the configured IPv6 routes.
Example 1
Example 2
kron occurrence
To schedule one or more Command Scheduler commands to run at a specific date and time or a recurring
level, use the kron occurrence command in configuration mode. To delete this schedule, use the no form of
this command.
kron occurrence occurrence-name
Note After you enter the occurrence-name in the kron occurrence command, you enter the config-Occurrence
configuration submode (see the following Syntax Description).
Usage Guidelines Use the kron occurrence and policy-list commands to schedule one or more policy lists to run at the same
time or interval.
Use the kron policy-list command in conjunction with the cli command to create a Command Scheduler policy
that contains the EXEC CLI commands to be scheduled to run in the Cisco ISE server at a specified time.
Note When you run the kron command, backup bundles are created with a unique name (by adding a time stamp)
to ensure that the files do not overwrite each other.
Note It is recommended that you schedule configuration or monitoring backups through the GUI by using the
Administration > System > Backup and Restore page.
kron policy-list
To specify a name for a Command Scheduler policy and enter the kron-Policy List configuration submode, use
the kron policy-list command in configuration mode. To delete a Command Scheduler policy, use the no form
of this command.
kron policy-list list-name
Note After you enter the list-name in the kron policy-list command, you enter the config-Policy List configuration
submode (see the following Syntax Description).
Usage Guidelines Use the kron policy-list command in conjunction with the cli command to create a Command Scheduler policy
that contains the EXEC CLI commands to be scheduled to run on the ISE server at a specified time. Use the
kron occurrence and policy list commands to schedule one or more policy lists to run at the same time or
interval.
Note You cannot use the kron policy-list command to schedule configuration and operational data backups from
the CLI. You can schedule these backups from the Cisco ISE Admin portal.
Example
logging
To configure the log level, use the logging command in configuration mode.
logging loglevel {0 | 1 | 2 | 3 | 4 | 5 | 6 | 7}
To disable this function, use the no form of this command.
no logging
Syntax Description loglevel The command to configure the log level for the logging
command.
Example
max-ssh-sessions
To configure the maximum number of concurrent command-line interface (CLI) sessions for each of the node
in the distributed deployment, use the max-ssh-sessions command in configuration mode.
max-ssh-sessions {0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10}
Command Default The default number of maximum concurrent CLI sessions allowed is set to five from the Cisco ISE Admin portal.
Usage Guidelines The max-ssh-sessions parameter is not configurable from the command-line interface. The maximum number
of active CLI sessions is replicated from the primary administration ISE Admin portal.
When you exceed the maximum number of CLI sessions, the “Maximum active ssh sessions reached” message
is displayed in the command-line interface closing that session, and you can see the “Not connected - press
Enter or Space to connect” message at the bottom.
You can log in to the CLI through the console and use the forceout username command to log out users to
reduce the active SSH sessions.
The navigation path to configure the maximum number of command-line interface (CLI) sessions is in the
Session tab of the Cisco ISE Admin portal in the following location: Administration > System > Admin Access >
Settings > Access .
ntp
To specify an NTP configuration, use the ntp command in configuration mode with authentication-key,
maxdistance, and server commands.
ntp authentication-key <key id> <authentication key encryption type> hash | plain <key value>
ntp maxdistance <maximum distance>
ntp reselectdistance <reselect distance>
ntp server {ip-address | hostname} key <peer key number>
no ntp server
Syntax Description authentication-key Specifies authentication keys for trusted time sources.
Example
ise/admin(config)# ntp ?
authentication-key Authentication key for trusted time sources
maxdistance Maximum allowed root distance of the sources to not be rejected
reselectdistance Fixed distance for sources that are currently not selected
server Specify NTP server to use
ise/admin(config)#
ise/admin(config)# no ntp server
ise/admin(config)# do show ntp
% no NTP servers configured
ise/admin(config)#
ntp authentication-key
To specify an authentication key for a time source, use the ntp authentication-key command in configuration
command with a unique identifier and a key value.
ntp authentication-key <key id> md5 hash | plain key value
ntp authentication-key <key id> sha1 hash | plain key value
ntp authentication-key <key id> sha256 hash | plain key value
ntp authentication-key <key id> sha512 hash | plain key value
To disable this capability, use the no form of this command.
no ntp authentication-key
Usage Guidelines Use the ntp authentication-key command to set up a time source with an authentication key for NTP
authentication and specify its pertinent key identifier, key encryption type, and key value settings. Add this
key to the trusted list before you add this key to the ntp server command.
Time sources without the NTP authentication keys that are added to the trusted list will not be synchronized.
Note The show running-config command will always show keys that are entered in Message Digest 5 (MD5) plain
format converted into hash format for security. For example, ntp authentication-key 1 md5 hash
ee18afc7608ac7ecdbeefc5351ad118bc9ce1ef3.
Example 1
ise/admin# configure
ise/admin(config)#
ise/admin(config)# ntp authentication-key 1 ?
md5 MD5 authentication
sha1 SHA1 authentication
sha256 SHA256 authentication
sha512 SHA512 authentication
Example 2
ise/admin# configure
ise/admin(config)#
ise/admin(config)# ntp authentication-key 1 sha1 plain ?
<WORD> Plain text or hexadecimal number with the HEX: prefix key for a (Max Size - 1028)
Example 3
Example 4
ntp maxdistance
The ntp maxdistance command sets the maximum allowed root distance of the sources to not be rejected by
the source selection algorithm. The distance includes the accumulated dispersion, which might be large when
the source is no longer synchronised, and half of the total round-trip delay to the primary source.
By default, the maximum root distance configured in Cisco ISE is 16 seconds.
To reset to the default value, use the no form of this command.
ntp maxdistance
Syntax Description maxdistance Maximum allowed root distance of the sources to not
be rejected.
Usage Guidelines Setting maxdistance to a larger value can be useful to allow synchronisation with a server that only has a very
infrequent connection to its sources and can accumulate a large dispersion between updates of its clock.
Example
ntp server
To allow for software clock synchronization by the NTP server for the system, use the ntp server command in
configuration mode. Allows up to three servers each with a key in a separate line. The key is an optional
parameter but the key is required for NTP authentication.
The Cisco ISE always requires a valid and reachable NTP server.
Although key is an optional parameter, it must be configured if you need to authenticate an NTP server.
To disable this capability, use the no form of this command only when you want to remove an NTP server and
add another one.
ntp server {ip-address | hostname} minpoll <minimum poll> key<peer key number>
ntp server {ip-address | hostname} trust
Usage Guidelines The show ntp command displays the status of synchronization. If none of the configured NTP servers are
reachable or not authenticated (if NTP authentication is configured), then this command displays synchronization
to local with the least stratum.
If an NTP server is not reachable or is not properly authenticated, then its reach as per this command statistics
will be 0.
Note This command gives conflicting information during the synchronization process. The synchronization process
can take up to 20 minutes to complete.
Example
ise/admin# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
ise/admin(config)# ntp server 209.165.200.225 ?
key Peer key number
minpoll Minimum interval between requests sent to the server
trust Assume time from this source is always true
Example 1
Example 2
rate-limit
To configure the limit of TCP/UDP/ICMP packets from a source IP address, use the rate-limit command in
configuration mode. To remove this function, use the no form of this command.
rate-limit 250 ip-address net-mask port
Example
password-policy
To enable or configure the passwords on the system, use the password-policy command in configuration
mode. To disable this function, use the no form of this command.
password-policy options
Note The password-policy command requires a policy option (see Syntax Description). You must enter the
password-expiration-enabled command before the other password-expiration commands.
Note After you enter the password-policy command, you can enter the config-password-policy configuration
submode.
do Exec command.
Example
ise/admin(config)# password-policy
ise/admin(config-password-policy)# password-expiration-days 30
ise/admin(config-password-policy)# exit
ise/admin(config)#
repository
To enter the repository submode for configuration of backups, use the repository command in configuration
mode.
repository repository-name
Note After you enter the name of the repository in the repository command, you enter the config-Repository
configuration submode (see the Syntax Description).
Syntax Description do EXEC command. Allows you to perform any of the EXEC
commands in this mode.
Note Server is the server name and path refers to /subdir/subsubdir. Remember that a colon(:) is required after the
server for an NFS network server.
Usage Guidelines When configuring url sftp: in the submode, you must first load the RSA fingerprint (AKA host-key) from the
target SFTP host into ISE. You can do this by using the crypto host_key add command through the CLI. See
the crypto command for more information.
To disable this function, use the no form of host-key host command in the submode.
Cisco ISE displays the following warning when you configure a secure ftp repository in the Cisco ISE Admin
portal in Administration > System > Maintenance > Repository > Add Repository.
The host key of the SFTP server must be added through the CLI by using the host-key option before this
repository can be used.
A corresponding error is thrown in the Cisco ADE logs when you try to back up into a secure FTP repository
without configuring the host-key.
Note Cisco ISE initiates outbound SSH or SFTP connections in FIPS mode even if FIPS mode is not enabled on ISE.
Ensure that the remote SSH or SFTP servers that communicate with ISE allow FIPS 140-2 approved cryptographic
algorithms.
Cisco ISE uses embedded FIPS 140-2 validated cryptographic modules. For details of the FIPS compliance
claims, see the FIPS Compliance Letter.
service
To specify a service to manage, use the service command in configuration mode.
service sshd
To disable this function, use the no form of this command.
no service
Syntax Description sshd Secure Shell Daemon. The daemon program for SSH.
Example
shutdown
To shut down an interface, use the shutdown command in the interface configuration mode. To disable this
function, use the no form of this command.
This command has no keywords and arguments.
Usage Guidelines When you shut down an interface using this command, you lose connectivity to the Cisco ISE appliance through
that interface (even though the appliance is still powered on).
However, if you have configured the second interface on the appliance with a different IP and have not shut
down that interface, you can access the appliance through that second interface.
To shut down an interface, you can also modify the ifcfg-eth[0,1] file, which is located at
/etc/sysconfig/network-scripts, using the ONBOOT parameter:
• Disable an interface: set ONBOOT="no”
• Enable an interface: set ONBOOT="yes"
You can also use the no shutdown command to enable an interface.
Example
snmp-server enable
To enable the SNMP server on Cisco ISE, use the snmp-server enable command in global configuration mode.
snmp-server enable
To disable the SNMP server, use the no form of this command.
Example
snmp-server user
To configure a new SNMP user, use the snmp-server user command in global configuration mode.
snmp-server user username v3 {hash | plain} auth-password priv-password
snmp-server user username v3 sha1{hash | plain} auth-password priv-password
snmp-server user username v3 sha224{hash | plain} auth-password priv-password
snmp-server user username v3 sha256{hash | plain} auth-password priv-password
snmp-server user username v3 sha384{hash | plain} auth-password priv-password
snmp-server user username v3 sha512{hash | plain} auth-password priv-password
username The name of the user on the host that belongs to the
SNMP agent.
Usage Guidelines After you configure users, make sure to configure SNMP Version 3 hosts. Along with the target IP address,
you must configure a username, because traps are only sent to a configured user.
Example
ise/admin(config)#
snmp-server host
To send SNMP traps to a recipient, use the snmp-server host command in configuration mode. By default,
SNMP traps are enabled. By default, the UDP port is 162.
Note SNMP user needs to be created before using the snmp-server host command.
snmp-server host {ip-address | hostname} version {{1 | 2c} community | 3 username engine_ID {hash | plain}
auth-password priv-password}
snmp-server host {ip-address | hostname} version {{1 | 2c} community | 3 username engine_ID sha1 {hash |
plain} auth-password priv-password}
snmp-server host {ip-address | hostname} version {{1 | 2c} community | 3 username engine_ID sha224 {hash |
plain} auth-password priv-password}
snmp-server host {ip-address | hostname} version {{1 | 2c} community | 3 username engine_ID sha256 {hash |
plain} auth-password priv-password}
snmp-server host {ip-address | hostname} version {{1 | 2c} community | 3 username engine_ID sha384 {hash |
plain} auth-password priv-password}
snmp-server host {ip-address | hostname} version {{1 | 2c} community | 3 username engine_ID sha512 {hash |
plain} auth-password priv-password}
To remove trap forwarding, use the no form of this command.
Note When SNMP Version 3 hosts are configured in Cisco ISE, a user must be associated with that host because
traps are sent only to a configured user. To receive traps, after you have added the snmp-server host command,
you must configure the user credentials on the NMS with the same credentials as those configured in Cisco
ISE.
Usage Guidelines Cisco ISE sends a 'coldStart(0)' trap when the appliance boots up (reloads), if SNMP is already configured.
Cisco ISE uses the Net-SNMP client that sends a 'coldStart(0)' trap when it first starts up, and an
enterprise-specific trap 'nsNotifyShutdown' when it stops.
It generates an enterprise-specific trap 'nsNotifyRestart' (rather than the standard 'coldStart(0)' or 'warmStart(1)'
traps) typically after you reconfigure SNMP using the snmp-server host command.
Note If the SNMP trap target is specified by hostname or FQDN and resolved by DNS to both IPv4 and IPv6 addresses,
ISE sends SNMP traps to IPv6 dual-stack target receivers through IPv4 and not through IPv6. To ensure that
the traps are sent through IPv6, an ISE admin may either resolve hostname or FQDN only to IPv6 by DNS, or
specify the IPv6 address directly, when configuring SNMP traps.
Examples
snmp-server community
To set up the community access string to permit access to the Simple Network Management Protocol (SNMP),
use the snmp-server community command in configuration mode.
snmp-server community community-string ro
To disable this function, use the no form of this command.
no snmp-server
Usage Guidelines The snmp-server community command requires a community string and the ro argument; otherwise, an error
occurs. The SNMP agent on the Cisco ISE provides read-only SNMP-v1 and SNMP-V2c access to the following
MIBs:
• SNMPv2-MIB
• RFC1213-MIB
• IF-MIB
• IP-MIB
• IP-FORWARD-MIB
• TCP-MIB
• UDP-MIB
• HOST-RESOURCES-MIB
• ENTITY-MIB-Only 3 MIB variables are supported on the ENTITY-MIB:
• Product ID: entPhysicalModelName
• Version ID: entPhysicalHardwareRev
• Serial Number: entPhysicalSerialNumber
• DISMAN-EVENT-MIB
• NOTIFICATION-LOG-MIB
• CISCO-CDP-MIB
Example
snmp-server contact
To configure the SNMP contact Management Information Base (MIB) value on the system, use the snmp-server
contact command in configuration mode. To remove the system contact information, use the no form of this
command.
snmp-server contact contact-name
Syntax Description contact Identifies the contact person for this managed node.
Supports up to 255 alphanumeric characters.
Example
snmp-server location
To configure the SNMP location MIB value on the system, use the snmp-server location command in
configuration mode. To remove the system location information, use the no form of this command.
snmp-server location location
Syntax Description location Configures the physical location of this managed node.
Supports up to 255 alphanumeric characters.
Usage Guidelines Cisco recommends that you use underscores (_) or hyphens (-) between the terms within the word string. If
you use spaces between terms within the word string, you must enclose the string in quotation marks (“).
Example 1
Example 2
Usage Guidelines This configuration is common for all the partitions in Cisco ISE. If you configure the threshold limit as 40, then
you will receive a trap as soon as a partition utilizes 60% of its disk space and only 40% of the disk space is
available. That is, a trap is sent when the configured amount of free space is reached.
After you configure this command from the Cisco ISE CLI, a kron job runs every five minutes and monitors the
Cisco ISE partitions one by one. If any one of the partitions reaches its threshold limit, then Cisco ISE sends a
trap to the configured SNMP server with the disk path and the threshold limit value. Multiple traps are sent if
multiple partitions reached the threshold limit. You can view the SNMP traps using the traps receiver in a MIB
browser.
Example
snmp engineid
To change the existing engine ID to a new value, use the snmp engineid command in configuration mode. This
command displays a warning that all existing users need to be re-created.
snmp engineid engine_ID_string
To remove the configured engine ID, use the no form of this command.
Syntax Description engineid Changes an existing engine ID to a new value that you
specify.
Example
synflood-limit
To configure a TCP SYN packet rate limit.
synflood-limit ?
Syntax Description synflood-limit Average number of TCP SYN packets per second
allowed
Usage Guidelines Use this synflood-limit to configure a TCP SYN packet rate limit.
Example 1
ise-pap-sec/admin(config)# synflood-limit ?
username
To add a user who can access the Cisco ISE appliance using SSH, use the username command in configuration
mode. If the user already exists, the password, the privilege level, or both change with this command. To delete
the user from the system, use the no form of this command.
username username password hash | plain {password} role admin | user email {email-address}
For an existing user, use the following command option:
username username password role admin | user {password}
Syntax Description username Only one word for the username argument. Blank
spaces and quotation marks (“) are not allowed.
Supports up to 31 alphanumeric characters.
role admin | user Sets the user role and the privilege level for the user.
Usage Guidelines The username command requires that the username and password keywords precede the hash | plain and
the admin | user options.
Example 1
Example 2
Example 3
which
To display the contents of commands available in admin CLI, use the which command in configuration mode.
which
Usage Guidelines which is a hidden command. Although which is available in Cisco ISE, the CLI interactive Help does not display
it if you attempt to view it by entering a question mark at the command line.
Example
The following example shows the output of which :
ise/admin(config)# which
[ 1]. application configure<STRING>
[ 2]. application install<STRING><STRING>
[ 3]. application remove<STRING>
[ 4]. application reset-config<STRING>
[ 5]. application reset-passwd<STRING><STRING>
[ 6]. application start<STRING>
[ 7]. application start<STRING> safe
[ 8]. application stop<STRING>
[ 9]. application upgrade cleanup
[ 10]. application upgrade prepare<STRING><STRING>