Setting the Date and Time
Use the CLI commands described below to configure the network time protocol (NTP) on the system, to set the date and time manually, or to view the current system time.
NTP settings are automatically synced between the Firepower 4100/9300 chassis and any logical devices installed on the chassis.
![]() Note |
If you are deploying threat defense on the Firepower 4100/9300 chassis, you must configure NTP on the Firepower 4100/9300 chassis so that Smart Licensing will work properly and to ensure proper timestamps on device registrations. You should use the same NTP server for both the Firepower 4100/9300 chassis and the management center, but note that you cannot use management center as the NTP server for the Firepower 4100/9300 chassis. |
If you are using NTP, you can view the overall synchronization status on the Current Time tab, or you can view the synchronization status for each configured NTP server by looking at the Server Status field in the NTP Server table on the Time Synchronization tab. If the system is unable to synchronize with a particular NTP server, you can hover over the information icon next to the Server Status for more information.
Viewing the Configured Date and Time
Procedure
Step 1 |
Connect to the FXOS CLI (see Accessing the FXOS CLI). |
Step 2 |
To view the configured time zone: Firepower-chassis# show timezone |
Step 3 |
To view the configured date and time: Firepower-chassis# show clock |
Example
The following example shows how to display the configured time zone and current system date and time:
Firepower-chassis# show timezone
Timezone: America/Chicago
Firepower-chassis# show clock
Thu Jun 2 12:40:42 CDT 2016
Firepower-chassis#
Setting the Time Zone
Procedure
Step 1 |
Enter system mode: Firepower-chassis# scope system |
Step 2 |
Enter system services mode: Firepower-chassis /system # scope services |
Step 3 |
Set the time zone: Firepower-chassis /system/services # set timezone At this point, you are prompted to enter a number corresponding to your continent, country, and time zone region. Enter the appropriate information at each prompt. When you have finished specifying the location information, you are prompted to confirm that the correct time zone information is being set. Enter 1 (yes) to confirm, or 2 (no) to cancel the operation. |
Step 4 |
To view the configured time zone: Firepower-chassis /system/services # top Firepower-chassis# show timezone |
Example
The following example configures the time zone to the Pacific time zone region, commits the transaction, and displays the configured time zone:
Firepower-chassis# scope system
Firepower-chassis /system # scope services
Firepower-chassis /system/services # set timezone
Please identify a location so that time zone rules can be set correctly.
Please select a continent or ocean.
1) Africa 4) Arctic Ocean 7) Australia 10) Pacific Ocean
2) Americas 5) Asia 8) Europe
3) Antarctica 6) Atlantic Ocean 9) Indian Ocean
#? 2
Please select a country.
1) Anguilla 28) Haiti
2) Antigua & Barbuda 29) Honduras
3) Argentina 30) Jamaica
4) Aruba 31) Martinique
5) Bahamas 32) Mexico
6) Barbados 33) Montserrat
7) Belize 34) Nicaragua
8) Bolivia 35) Panama
9) Brazil 36) Paraguay
10) Canada 37) Peru
11) Caribbean Netherlands 38) Puerto Rico
12) Cayman Islands 39) St Barthelemy
13) Chile 40) St Kitts & Nevis
14) Colombia 41) St Lucia
15) Costa Rica 42) St Maarten (Dutch part)
16) Cuba 43) St Martin (French part)
17) Curacao 44) St Pierre & Miquelon
18) Dominica 45) St Vincent
19) Dominican Republic 46) Suriname
20) Ecuador 47) Trinidad & Tobago
21) El Salvador 48) Turks & Caicos Is
22) French Guiana 49) United States
23) Greenland 50) Uruguay
24) Grenada 51) Venezuela
25) Guadeloupe 52) Virgin Islands (UK)
26) Guatemala 53) Virgin Islands (US)
27) Guyana
#? 49
Please select one of the following time zone regions.
1) Eastern Time
2) Eastern Time - Michigan - most locations
3) Eastern Time - Kentucky - Louisville area
4) Eastern Time - Kentucky - Wayne County
5) Eastern Time - Indiana - most locations
6) Eastern Time - Indiana - Daviess, Dubois, Knox & Martin Counties
7) Eastern Time - Indiana - Pulaski County
8) Eastern Time - Indiana - Crawford County
9) Eastern Time - Indiana - Pike County
10) Eastern Time - Indiana - Switzerland County
11) Central Time
12) Central Time - Indiana - Perry County
13) Central Time - Indiana - Starke County
14) Central Time - Michigan - Dickinson, Gogebic, Iron & Menominee Counties
15) Central Time - North Dakota - Oliver County
16) Central Time - North Dakota - Morton County (except Mandan area)
17) Central Time - North Dakota - Mercer County
18) Mountain Time
19) Mountain Time - south Idaho & east Oregon
20) Mountain Standard Time - Arizona (except Navajo)
21) Pacific Time
22) Pacific Standard Time - Annette Island, Alaska
23) Alaska Time
24) Alaska Time - Alaska panhandle
25) Alaska Time - southeast Alaska panhandle
26) Alaska Time - Alaska panhandle neck
27) Alaska Time - west Alaska
28) Aleutian Islands
29) Hawaii
#? 21
The following information has been given:
United States
Pacific Time
Therefore timezone 'America/Los_Angeles' will be set.
Local time is now: Wed Jun 24 07:39:25 PDT 2015.
Universal Time is now: Wed Jun 24 14:39:25 UTC 2015.
Is the above information OK?
1) Yes
2) No
#? 1
Firepower-chassis /system/services* # commit-buffer
Firepower-chassis /system/services # top
Firepower-chassis# show timezone
Timezone: America/Los_Angeles (Pacific Time)
Firepower-chassis#
Setting the Date and Time Using NTP
NTP is used to implement a hierarchical system of servers that provide a precisely synchronized time among network systems. This kind of accuracy is required for time-sensitive operations, such as validating CRLs, which include a precise time stamp. You can configure up to four NTP servers.
![]() Note |
|
Before you begin
If you use a hostname for the NTP server, you must configure a DNS server. See Configuring DNS Servers.
Procedure
Step 1 |
Enter system mode: Firepower-chassis# scope system |
Step 2 |
Enter system services mode: Firepower-chassis /system # scope services |
Step 3 |
Configure the system to use the NTP server with the specified hostname, IPv4, or IPv6 address: Firepower-chassis /system/services # create ntp-server {hostname | ip-addr | ip6-addr} |
Step 4 |
(Optional) Configure NTP authentication. Only SHA1 is supported for NTP server authentication. Obtain the key ID and value from the NTP server. For example, to generate the SHA1 key on NTP server Version 4.2.8p8 or later with OpenSSL installed, enter the ntp-keygen -M command, and then view the key ID and value in the ntp.keys file. The key is used to tell both the client and server which value to use when computing the message digest. Example:
|
Step 5 |
Commit the transaction to the system configuration: Firepower-chassis /system/services # commit-buffer |
Step 6 |
To view the synchronization status for all configured NTP servers: Firepower-chassis /system/services # show ntp-server |
Step 7 |
To view the synchronization status for a specific NTP server: Firepower-chassis /system/services # scope ntp-server {hostname | ip-addr | ip6-addr} Firepower-chassis /system/services/ntp-server # show detail |
Example
The following example configures an NTP server with the IP address 192.168.200.101 and commits the transaction:
Firepower-chassis# scope system
Firepower-chassis /system # scope services
Firepower-chassis /system/services # create ntp-server 192.168.200.101
Firepower-chassis /system/services* # commit-buffer
Firepower-chassis /system/services #
The following example configures an NTP server with the IPv6 address 4001::6 and commits the transaction:
Firepower-chassis# scope system
Firepower-chassis /system # scope services
Firepower-chassis /system/services # create ntp-server 4001::6
Firepower-chassis /system/services* # commit-buffer
Firepower-chassis /system/services #
Deleting an NTP Server
Procedure
Step 1 |
Enter system mode: Firepower-chassis# scope system |
Step 2 |
Enter system services mode: Firepower-chassis /system # scope services |
Step 3 |
Delete the NTP server with the specified hostname, IPv4, or IPv6 address: Firepower-chassis /system/services # delete ntp-server {hostname | ip-addr | ip6-addr} |
Step 4 |
Commit the transaction to the system configuration: Firepower-chassis /system/services # commit-buffer |
Example
The following example deletes the NTP server with the IP address 192.168.200.101 and commits the transaction:
Firepower-chassis# scope system
Firepower-chassis /system # scope services
Firepower-chassis /system/services # delete ntp-server 192.168.200.101
Firepower-chassis /system/services* # commit-buffer
Firepower-chassis /system/services #
The following example deletes the NTP server with the IPv6 address 4001::6 and commits the transaction:
Firepower-chassis# scope system
Firepower-chassis /system # scope services
Firepower-chassis /system/services # delete ntp-server 4001::6
Firepower-chassis /system/services* # commit-buffer
Firepower-chassis /system/services #
Setting the Date and Time Manually
This section describes how to set the date and time manually on the chassis. System clock modifications take effect on the chassis immediately. Note that after you manually set the chassis date and time, it could take some time for the change to be reflected in the installed logical device(s).
![]() Note |
If the system clock is currently being synchronized with an NTP server, you will not be able to set the date and time manually. |
Procedure
Step 1 |
Enter system mode: Firepower-chassis# scope system |
Step 2 |
Enter system services mode: Firepower-chassis /system # scope services |
Step 3 |
Configure the system clock: Firepower-chassis /system/services # set clock month day year hour min sec For month, use the first three digits of the month. Hours must be entered using the 24-hour format, where 7 pm would be entered as 19. System clock modifications take effect immediately. You do not need to commit the buffer. |
Example
The following example configures the system clock:
Firepower-chassis# scope system
Firepower-chassis /system # scope services
Firepower-chassis /system/services # set clock jun 24 2015 15 27 00
Firepower-chassis /system/services #