System Setup and Software Installation Guide for Cisco NCS 1010, IOS XR Releases

PDF

System Setup and Software Installation Guide for Cisco NCS 1010, IOS XR Releases

Cisco NCS 1010 setup workflow

Updated: September 11, 2026

Want to summarize with AI?

Log in

Provides the Cisco NCS 1010 setup workflow and related setup task sequence used to bring up the system for further configuration.

Complete these tasks to bring up your NCS 1010 for further configuration.

Figure 1. Setup workflow for Cisco NCS 1010

Boot Cisco NCS 1010

Use this procedure to boot Cisco NCS 1010.

Use the console port to connect to NCS 1010. By default, the console port connects to the XR mode. If necessary, you can establish subsequent connections through the management port, after it is configured.

Procedure

  1. Connect a terminal to the console port of the RP.

  2. Start the terminal emulation program on your workstation.

    The console settings are 9600 bps, 8 data bits, 1 stop bit and no parity.

  3. Power on NCS 1010.

    To power on the shelves, install the AC or DC power supplies and cables. As NCS 1010 boots up, you can view the boot process details at the console of the terminal emulation program.

  4. Press Enter.

    The boot process is complete when the system prompts you to enter the root-system username. If the prompt does not appear, wait for a while to give NCS 1010 more time to complete the initial boot procedure; then press Enter.

    Note

    If the boot process fails, it may be because the preinstalled image on the NCS 1010 is corrupt. In this case, you can boot NCS 1010 using an external bootable USB drive.

The boot Cisco NCS 1010 task is complete.

Boot Cisco NCS 1010 using a USB drive

Use this supertask to prepare a bootable USB drive and boot Cisco NCS 1010 from that drive.

Before you begin

  • You need a USB drive with a storage capacity of at least 4 GB.

  • The USB drive should have a single partition.

  • NCS 1010 software image can be downloaded from Software Download page on Cisco.com.

  • Copy the compressed boot file from the software download page at Cisco.com to your local machine. The filename for the compressed boot file is in the format ncs1010-usb-boot-<release_number>.zip.

The bootable USB drive is used to reimage NCS 1010 for system upgrade or to boot the NCS 1010 in case of boot failure. A bootable USB drive is created by copying a compressed boot file into a USB drive. The USB drive becomes bootable after the contents of the compressed file are extracted.

You can complete this task using the Windows, Linux, or MAC operating systems available on your local machine. The exact operation to be performed for each generic step that is outlined here depends on the operating system in use.

Use this task to boot the NCS 1010 using the USB drive.

Procedure

  1. Prepare a USB boot drive.

    See Prepare a USB boot drive.

  2. Start Cisco NCS 1010 from a USB drive.

    See Start Cisco NCS 1010 from a USB drive.

Cisco NCS 1010 boots from the USB image and reboots after installation.

Prepare a USB boot drive

Use this procedure to format the USB drive, copy the compressed boot file, verify the file, and extract the contents at the root of the drive.

Before you begin

  • You need a USB drive with a storage capacity of at least 4 GB.

  • The USB drive should have a single partition.

  • NCS 1010 software image can be downloaded from Software Download page on Cisco.com.

  • Copy the compressed boot file from the software download page at Cisco.com to your local machine. The filename for the compressed boot file is in the format ncs1010-usb-boot-<release_number>.zip.

The prepared USB drive contains the extracted boot files that make the drive bootable.

Procedure

  1. Connect the USB drive to your local machine and format it with the FAT32 file system.

  2. Copy the compressed boot file to the USB drive.

  3. Verify that the copy operation is successful. To verify, compare the file size at source and destination. Also, verify the MD5 checksum value.

  4. Extract the content of the compressed boot file by unzipping it in the USB drive. This makes the USB drive a bootable drive.

    Note

    You must extract the contents of the zipped file ("EFI" and "boot" directories) directly in the root folder of the USB drive. If the unzipping application places the extracted files in a new folder, move the "EFI" and "boot" directories to the root folder of the USB drive.

The USB drive is ready to boot Cisco NCS 1010.

Start Cisco NCS 1010 from a USB drive

Use this procedure to insert the prepared USB drive, select the BIOS boot option, and remove the drive after the image loads.

Before you begin

Prepare the USB boot drive before you start Cisco NCS 1010 from the drive. See Prepare a USB boot drive.

Use the console or BIOS boot option when you need to boot Cisco NCS 1010 from the prepared USB drive.

Procedure

  1. Insert the USB drive in one of the USB ports of NCS 1010 line card/controller card.

  2. Reboot NCS 1010 using power cycle or console.

    Note
    Use the reload bootmedia usb noprompt command to boot the NCS 1010 from the USB. If you are using the reload bootmedia usb noprompt command, then you can skip the remaining steps.

  3. Press Esc to enter BIOS.

  4. Select the Save & Exit tab of BIOS.

    BIOS

  5. Choose IOS -XR Install.

    The BIOS UI displays the USB drive vendor in the brackets, in this case, SMART USB 1084.

    The system detects USB and boots the image from USB.

    Booting from USB..
Loading Kernel..
Verifying (loop)/boot/bzImage...
(loop)/boot/bzImage verified using attached signature.
Loading initrd..
Verifying (loop)/boot/initrd.img...

  6. Remove the USB drive after the Rebooting the system after installation message is displayed. The NCS 1010 reboots automatically.

    Note

    The USB must be removed only after the image is loaded successfully.

Cisco NCS 1010 starts from the USB drive and reboots after installation.

Boot Cisco NCS 1010 using iPXE

Use iPXE boot to reimage Cisco NCS 1010 through a network boot workflow.

Use iPXE boot when the router fails to boot or when no valid bootable partition is available. iPXE enables network boot for an offline router. The iPXE bootloader downloads and installs the ISO image located on an HTTP, FTP, or TFTP server and reimages the router.

iPXE boot can be invoked through the CLI terminal or through the BIOS interface.

Before you begin

Procedure

  1. Invoke iPXE boot through the CLI terminal.

    For details, see Boot Cisco NCS 1010 using iPXE from the CLI.

  2. Invoke iPXE boot through the BIOS interface.

    For details, see Boot Cisco NCS 1010 using iPXE from BIOS.

The iPXE boot process downloads the ISO image and reimages the Cisco NCS 1010 chassis.

Configure a DHCP server for iPXE boot

Configure a DHCP server to provide Cisco NCS 1010 iPXE boot information.

A DHCP server must be configured for IPv4, IPv6, or both communication protocols before Cisco NCS 1010 can use iPXE boot.

For DHCPv6, send a routing advertisement (RA) message to all nodes in the network to indicate the method used to obtain the IPv6 address.

Procedure

  1. If you use DHCPv6, configure Router Advertisement Daemon to allow the client to send the DHCP request.

    Example:

    interface eth3
{
        AdvSendAdvert on;
        MinRtrAdvInterval 60;
        MaxRtrAdvInterval 180;
        AdvManagedFlag on;
        AdvOtherConfigFlag on;
        prefix 2001:1851:c622:1::/64
        {
                AdvOnLink on;
                AdvAutonomous on;
                AdvRouterAddr off;
        };
};

  2. Create the dhcpd.conf file, dhcpv6.conf file, or both files in the /etc/ directory.

    The configuration file stores network information, such as the script path, ISO install file location, provisioning configuration file location, serial number, and chassis MAC address.

  3. Add a host entry that uses the chassis MAC address.

    Example:

    host ncs1010 
{
hardware ethernet ab:cd:ef:01:23:45;
fixed-address <ip address>;
filename "http://<httpserver-address>/<path-to-image>/ncs1010-mini-x.iso";
}

    Ensure that the DHCP host configuration is successful after the DHCP server is running.

  4. If you identify the chassis by serial number, add a host entry that uses the chassis serial number.

    Example:

    host demo {
option dhcp-client-identifier "<chassis-serial-number>";
  filename "http://<IP-address>/<hardware-platform>-mini-x.iso";
  fixed-address <IP-address>;
}

    Example:

    
host 10.89.205.202 {
       hardware ethernet 40:55:39:56:0c:e8;
        option dhcp-client-identifier "<FCB2437B066>";
          if exists user-class and option user-class = "iPXE" {
          filename "http://10.89.205.127/box1/ncs1010-x64.iso";
       } else {
           filename "http://10.89.205.127/box1/StartupConfig.cfg";
       }
       fixed-address 10.89.205.202;
    }

    The chassis serial number is derived from the BIOS and is used as an identifier.

The DHCP server provides the iPXE boot image or provisioning configuration file information to Cisco NCS 1010.

Boot Cisco NCS 1010 using iPXE from the CLI

Invoke iPXE boot from the CLI terminal to reimage the chassis.

Use this method to start the iPXE boot process from the CLI terminal.

Before you begin

  • Ensure that the DHCP server is set and running.

  • Ensure that the management port of the NCS 1010 chassis is in UP state.

Procedure

  1. Run the command to invoke the iPXE boot process and reimage the chassis.

    reload bootmedia network location all

    Example:

    RP/0/RP0/CPU0:ios# reload bootmedia network location all
Wed Jul  6 15:11:33.791 UTC
Reload hardware module ? [confirm]

  2. Review the iPXE boot output.

    Example:

    Preparing system for backup. This may take a few minutes especially for large configurations.
        Status report: node0_RP0_CPU0: BACKUP INPROGRESS 
RP/0/RP0/CPU0:P1D_DT#   Status report: node0_RP0_CPU0: BACKUP HAS COMPLETED SUCCESSFULLY 
[Done]
[FAILED] Failed unmounting /mnt/fuse/parser_server.
[  OK  ] Unmounted /mnt/fuse/ftp.
[  OK  ] Unmounted /mnt/fuse/nvgen_server.
[  OK  ] Unmounted /boot/efi.
[  OK  ] Unmounted /selinux.
.
.
Output Snipped
.
.
..         *** Sirius ***
System Initializing..
..

ERROR: Class:0; Subclass:10000; Operation: 1004

Shelf Assembly Reset
Shelf Assembly Reset for P1


..         *** Sirius ***
System Initializing..
..

ERROR: Class:0; Subclass:10000; Operation: 1004
.
.
Output Snipped
.
.

NCS1010, Initializing Devices

Booting from Primary Flash
Aldrin: Programmed MI 10 
.
.
Output Snipped
.
.
Version 2.19.1266. Copyright (C) 2022 American Megatrends, Inc.                 
BIOS Date: 05/20/2022 10:47:39 Ver: 0ACHI0410                                   
Press <DEL> or <ESC> to enter setup.                                            
TAM Chipguard Validate Observed DB Error: 0x48                                  
                                                                                
WARNING!!! TAM: Empty Chip DB                                                   
                                                                                
                                                                                
Software Boot OK, Validated                                                     
                                                                                
iPXE initialising devices...ok                                                  
                                                                                
                                                                                
iPXE 1.0.0+ (c2215) -- Open Source Network Boot Firmware -- http://ipxe.org     
Features: DNS HTTP TFTP VLAN EFI ISO9660 ISO9660_grub Menu                      
Trying net0-2051,net0-2052 and net0-2053...                                     
net0-2051: 68:9e:0b:b8:71:1e using NII on NII-PCI06:00.0 (open)                 
  [Link:down, TX:0 TXE:0 RX:0 RXE:0]                                            
  [Link status: Unknown (http://ipxe.org/1a086194)]                             
Configuring (net0-2051 68:9e:0b:b8:71:1e).................. Error 0x040ee186 (http://ipxe.org/040ee186)
net0-2052: 68:9e:0b:b8:71:1f using NII on NII-PCI06:00.0 (open)                 
  [Link:up, TX:0 TXE:0 RX:18 RXE:14]                                            
  [RXE: 8 x "Operation not supported (http://ipxe.org/3c086083)"]               
  [RXE: 3 x "Error 0x440e6083 (http://ipxe.org/440e6083)"]                     
  [RXE: 3 x "The socket is not connected (http://ipxe.org/380f6093)"]
Configuring (net0-2052 68:9e:0b:b8:71:1f).................. ok
net0: fe80::6a9e:bff:feb8:711e/64
net1: fe80::6a9e:bff:feb8:7121/64 (inaccessible)
net2: fe80::6a9e:bff:feb8:7122/64 (inaccessible)
net3: fe80::6a9e:bff:feb8:7123/64 (inaccessible)
net0-2051: fe80::6a9e:bff:feb8:711e/64
net0-2051: 2001:420:5446:2014::281:0/119 gw fe80::676:b0ff:fed8:c100 (no address)
net0-2051: 2002:420:54ff:93:6a9e:bff:feb8:711e/64 gw fe80::fa4f:57ff:fe72:a640
net0-2052: 10.4.33.44/255.255.0.0 gw 10.4.33.1
net0-2052: fe80::6a9e:bff:feb8:711e/64
net0-2053: fe80::6a9e:bff:feb8:711e/64
Filename: http://10.4.33.51/P1D_DT_05/ncs1010-x64.iso
http://10.4.33.51/P1D_DT_05/ncs1010-x64.iso... ok
.
.
Output Snipped
.
.
User Access Verification

Username: cisco
Password:
    The iPXE boot process downloads the ISO image and displays the user access verification prompt.

Cisco NCS 1010 boots through iPXE from the CLI terminal and starts the reimage workflow.

Boot Cisco NCS 1010 using iPXE from BIOS

Invoke iPXE boot from the BIOS interface to reimage the chassis.

Use this method to start the iPXE boot process from the BIOS interface.

Before you begin

  • Ensure that the DHCP server is set and running.

  • Ensure that the management port of the NCS 1010 chassis is in UP state.

Procedure

  1. Reboot NCS 1010 using power cycle or console.

  2. Press Esc to enter BIOS.

  3. Select the Save & Exit tab of BIOS.

  4. Choose UEFI: iPXE Network Boot.

    Example:

    Preparing system for backup. This may take a few minutes especially for large configurations.
        Status report: node0_RP0_CPU0: BACKUP INPROGRESS 
RP/0/RP0/CPU0:P1D_DT#   Status report: node0_RP0_CPU0: BACKUP HAS COMPLETED SUCCESSFULLY 
[Done]
[FAILED] Failed unmounting /mnt/fuse/parser_server.
[  OK  ] Unmounted /mnt/fuse/ftp.
[  OK  ] Unmounted /mnt/fuse/nvgen_server.
[  OK  ] Unmounted /boot/efi.
[  OK  ] Unmounted /selinux.
.
.
Output Snipped
.
.
..         *** Sirius ***
System Initializing..
..

ERROR: Class:0; Subclass:10000; Operation: 1004

Shelf Assembly Reset
Shelf Assembly Reset for P1


..         *** Sirius ***
System Initializing..
..

ERROR: Class:0; Subclass:10000; Operation: 1004
.
.
Output Snipped
.
.

NCS1010, Initializing Devices

Booting from Primary Flash
Aldrin: Programmed MI 10 
.
.
Output Snipped
.
.
Version 2.19.1266. Copyright (C) 2022 American Megatrends, Inc.                 
BIOS Date: 05/20/2022 10:47:39 Ver: 0ACHI0410                                   
Press <DEL> or <ESC> to enter setup.                                            
TAM Chipguard Validate Observed DB Error: 0x48                                  
                                                                                
WARNING!!! TAM: Empty Chip DB                                                   
                                                                                
                                                                                
Software Boot OK, Validated                                                     
                                                                                
iPXE initialising devices...ok                                                  
                                                                                
                                                                                
iPXE 1.0.0+ (c2215) -- Open Source Network Boot Firmware -- http://ipxe.org     
Features: DNS HTTP TFTP VLAN EFI ISO9660 ISO9660_grub Menu                      
Trying net0-2051,net0-2052 and net0-2053...                                     
net0-2051: 68:9e:0b:b8:71:1e using NII on NII-PCI06:00.0 (open)                 
  [Link:down, TX:0 TXE:0 RX:0 RXE:0]                                            
  [Link status: Unknown (http://ipxe.org/1a086194)]                             
Configuring (net0-2051 68:9e:0b:b8:71:1e).................. Error 0x040ee186 (http://ipxe.org/040ee186)
net0-2052: 68:9e:0b:b8:71:1f using NII on NII-PCI06:00.0 (open)                 
  [Link:up, TX:0 TXE:0 RX:18 RXE:14]                                            
  [RXE: 8 x "Operation not supported (http://ipxe.org/3c086083)"]               
  [RXE: 3 x "Error 0x440e6083 (http://ipxe.org/440e6083)"]                     
  [RXE: 3 x "The socket is not connected (http://ipxe.org/380f6093)"]
Configuring (net0-2052 68:9e:0b:b8:71:1f).................. ok
net0: fe80::6a9e:bff:feb8:711e/64
net1: fe80::6a9e:bff:feb8:7121/64 (inaccessible)
net2: fe80::6a9e:bff:feb8:7122/64 (inaccessible)
net3: fe80::6a9e:bff:feb8:7123/64 (inaccessible)
net0-2051: fe80::6a9e:bff:feb8:711e/64
net0-2051: 2001:420:5446:2014::281:0/119 gw fe80::676:b0ff:fed8:c100 (no address)
net0-2051: 2002:420:54ff:93:6a9e:bff:feb8:711e/64 gw fe80::fa4f:57ff:fe72:a640
net0-2052: 10.4.33.44/255.255.0.0 gw 10.4.33.1
net0-2052: fe80::6a9e:bff:feb8:711e/64
net0-2053: fe80::6a9e:bff:feb8:711e/64
Filename: http://10.4.33.51/P1D_DT_05/ncs1010-x64.iso
http://10.4.33.51/P1D_DT_05/ncs1010-x64.iso... ok
.
.
Output Snipped
.
.
User Access Verification

Username: cisco
Password:
    The iPXE boot process downloads the ISO image and displays the user access verification prompt.

Cisco NCS 1010 boots through iPXE from the BIOS interface and starts the reimage workflow.

Install a new image without Golden ISO

Install a new image without using the Golden ISO feature.

Before the introduction of Golden ISO, you had to perform this sequence to install a new image.

Before you begin

  • Ensure that the mini ISO is available.

  • Ensure that all relevant SMUs, optional packages, and IOS XR configuration are available.

Procedure

  1. Boot the system with mini ISO.

    You can use iPXE or USB boot.

  2. Install, add, and activate all relevant SMUs and optional packages on NCS 1010.

    NCS 1010 reloads when any SMU reloads.

  3. Apply IOS XR configuration.

The new image is installed without using Golden ISO.

Build a Golden ISO boot image for Cisco NCS 1010

Build a customized Golden ISO image that includes the mini ISO, required SMUs, and IOS XR configuration.

Golden ISO is a feature that enables you to build a customized ISO using mini ISO, required SMUs, and IOS XR configuration.

Golden ISO saves installation effort and time. It makes the system available in a single command and boot.

The gisobuild.py script is available at /pkg/bin/gisobuild.py.

Note

Install operation over IPv6 is not supported.

Before you begin

  • For details about the image installation sequence used before Golden ISO was introduced, see Install a new image without Golden ISO.

    Copy the /pkg/bin/gisobuild.py script from NCS 1010 to the Linux environment.

  • Ensure that the mini ISO, required SMUs, and IOS XR configuration file are available.

Procedure

  1. Build the Golden ISO image.

    gisobuild.py -i mini-iso -r rpm-directory -c xr-config -l label

    • rpm-directory - Directory where SMUs (xr, calvados, and host) are copied.

    • xr-config - IOS XR configuration to be applied to the system after booting.

    • label - Label of the Golden ISO.

    Example:

    gisobuild.py -i./ncs1010-mini-x.iso -r ./rpm-directory -c ./xr-config -l label

  2. Review the Golden ISO build output.

    Example:

    python gisobuild.py -i ./ncs1010-mini-x-7.0.1.04I.iso -r. -c startup_new.cfg -l v2
System requirements check [PASS]
Golden ISO build process starting...

Platform: ncs1010 Version: 7.0.1.04I

XR-Config file (/bh/bosshogg_images/r701/701_04I_DT_IMAGE/giso/startup_new.cfg) will be encapsulated in Golden ISO.

Scanning repository [/bh/bosshogg_images/r701/701_04I_DT_IMAGE/giso]...

Building RPM Database...
Total 1 RPM(s) present in the repository path provided in CLI

XR x86_64 rpm(s) used for building Golden ISO:

(+) ncs1010-k9sec-192.0.2.1-r70104I.x86_64.rpm

...RPM compatibility check [PASS]

Building Golden ISO...
Summary .....

XR rpms:
ncs1010-k9sec-192.0.2.1-r70104I.x86_64.rpm

XR Config file:
router.cfg

...Golden ISO creation SUCCESS.

Golden ISO Image Location: /bh/bosshogg_images/r701/701_04I_DT_IMAGE/giso/ncs1010-goldenk9-x-7.0.1.04I-v2.iso

Detail logs: /bh/bosshogg_images/r701/701_04I_DT_IMAGE/giso/Giso_build.log-2019-03-20:15:47:19.516203
    The command output shows that Golden ISO creation succeeded and displays the Golden ISO image location.

  3. Verify the Golden ISO file format.

    Use these Golden ISO filename formats:

    • platform-name-golden-x.iso-version.label does not contain the security (*k9sec*.rpm) rpm.

    • platform-name-goldenk9-x.iso-version.label contains the security (*k9sec*.rpm) rpm.

    Example:

    Example 1: ncs1010-golden-x-7.0.1.014I-V1.iso

    Example 2: ncs1010-goldenk9-x-7.0.1.014I-V1.iso

The Golden ISO boot image is built and its filename format is verified.

Network Time Protocol

A Network Time Protocol implementation is a time synchronization function that

  • uses UDP and Coordinated Universal Time to synchronize device clocks,

  • forms configured associations with NTP servers to exchange timing messages, and

  • supports accurate event timing for network management, security, planning, and debugging.

Details

Table 1. Feature History

Feature Name

Release Information

Feature Description

NTP Support

Network Time Protocol (NTP) allows devices to synchronize clocks with the NTP servers, maintaining the most accurate time. NCS 1010 now supports time synchronization. In modern and large networks, time synchronization is critical because every aspect of managing, securing, planning, and debugging a network depends on the time of occurrence of events.

Commands added:

  • ntp server

  • show ntp associations

  • show ntp status

NTP uses the User Datagram Protocol (UDP) as its transport protocol. All NTP communication uses Coordinated Universal Time (UTC). An NTP network usually receives its time from an authoritative time source, such as a radio clock or an atomic clock attached to a time server. NTP distributes this time across the network.

NTP uses the concept of a "stratum" to describe how many NTP hops away a machine is from an authoritative time source. A "stratum 1" time server typically has an authoritative time source (such as a radio or atomic clock, or a GPS time source) directly attached, a "stratum 2" time server receives its time through NTP from a "stratum 1" time server, and so on.

The communications between machines running NTP (known as associations) are usually statically configured; each machine is given the IP address of all machines with which it should form associations. Accurate timekeeping is made possible by exchanging NTP messages between each pair of machines with an association.

An NTP broadcast client listens for broadcast messages sent by an NTP broadcast server at a designated IPv4 address. The client synchronizes the local clock using the first received broadcast message.

Synchronize the clock with an NTP server

Use this procedure to synchronize the clock with an NTP server.

There is an independent system clock for IOS XR. To ensure that this clock does not deviate from true time, it must be synchronized with the clock of an NTP server.

Before you begin

Configure Management Interface

Procedure

  1. Enter configuration mode.

    configure

    Example:

    RP/0/RP0/CPU0:ios#configure

    Enters the configuration mode.

  2. Enter NTP configuration mode.

    ntp

    Example:

    RP/0/RP0/CPU0:ios(config)#ntp

    Enters NTP configuration mode.

  3. Configure an NTP server.

    server 198.51.100.1 version 4 prefer iburst

    server 2001:DB8::1 version 4 prefer iburst

    Example:

    IPv4: 
    RP/0/RP0/CPU0:ios(config-ntp)#server 198.51.100.1 version 4 prefer iburst
    IPv6: 
    RP/0/RP0/CPU0:ios(config-ntp)#server 2001:DB8::1 version 4 prefer iburst

    Synchronizes the console clock with the specified NTP server.

    Note

    The NTP server can also be reached through a VRF if the management interface is in a VRF.

  4. Save or exit the configuration session.

    end

    commit

    • end

    • commit

    Example:

    RP/0/RP0/CPU0:ios(config-ntp)#end

    or

    RP/0/RP0/CPU0:ncs1010(config-ntp)#commit

    Saves configuration changes.

    • When you issue the end command, the system prompts you to commit changes:

      
Uncommitted changes found, commit them before 
  exiting(yes/no/cancel)?
[cancel]:

      • Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns to EXEC mode.

      • Entering no exits the configuration session and returns to EXEC mode without committing the configuration changes.

      • Entering cancel leaves the system in the current configuration session without exiting or committing the configuration changes.

    • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

  5. Verify the running NTP configuration.

    show running-config ntp

    Example:

    RP/0/RP0/CPU0:ios#show running-config ntp 
    
Sun Nov  5 15:14:24.969 UTC

ntp

 server 192.0.2.51 burst iburst

!

    Displays the running configuration.

The synchronize the clock with an NTP server task is complete.

Verify NTP synchronization status

Use this procedure to verify NTP synchronization status.

This task explains how to verify the status of NTP components.

Procedure

  1. Verify NTP associations.

    show ntp associations

    Example:

    RP/0/RP0/CPU0:ios#show ntp associations
Sun Nov 5 15:14:44.128 UTC

address ref clock st when poll reach delay offset disp
*~192.0.2.1 198.51.100.1 2 81 128 377 1.84 7.802 2.129
* sys_peer, # selected, + candidate, - outlayer, x falseticker, ~ configured

    selected, + candidate, - outlayer, x falseticker, ~ configured

    Displays the status of NTP associations.

  2. Verify detailed NTP association information.

    show ntp associations detail

    Example:

    RP/0/RP0/CPU0:ios#show ntp associations detail
Sun Nov 5 15:14:48.763 UTC

192.0.2.1 configured, our_master, stratum 2
ref ID 198.51.100.1, time E8F22BB9.79D4A841 (14:56:57.475 UTC Sun Nov 5 2023)
our mode client, peer mode server, our poll intvl 128, peer poll intvl 128
root delay 0.6866 msec, root disp 1.04, reach 377, sync dist 6.2590
delay 1.84 msec, offset 7.802 msec, dispersion 2.129
precision 2**23, version 4
org time E8F22F92.B647E8FC (15:13:22.712 UTC Sun Nov 5 2023)
rcv time E8F22F92.B88F303C (15:13:22.720 UTC Sun Nov 5 2023)
xmt time E8F22F92.B88F303C (15:13:22.720 UTC Sun Nov 5 2023)
filtdelay = 1.844 1.772 1.983 1.954 1.945 2.000 1.902 1.778
filtoffset = 7.857 7.802 8.065 8.063 8.332 8.397 8.664 8.684
filterror = 0.000 0.060 1.995 2.055 4.050 4.110 6.060 6.120

  3. Verify detailed NTP association information for a location.

    show ntp associations detail location 0/RP0/CPU0

    Example:

    RP/0/RP0/CPU0:ios#show ntp associations detail location 0/RP0/CPU0
Sun Nov 5 15:38:15.744 UTC

192.0.2.1 configured, our_master, stratum 2
ref ID 198.51.100.1, time E8F233C0.5606A159 (15:31:12.336 UTC Sun Nov 5 2023)
our mode client, peer mode server, our poll intvl 128, peer poll intvl 128
root delay 0.7019 msec, root disp 0.47, reach 377, sync dist 5.6762
delay 2.01 msec, offset 7.226 msec, dispersion 3.856
precision 2**23, version 4
org time E8F23563.DE5D42D5 (15:38:11.868 UTC Sun Nov 5 2023)
rcv time E8F23563.E07C296D (15:38:11.876 UTC Sun Nov 5 2023)
xmt time E8F23563.E07C296D (15:38:11.876 UTC Sun Nov 5 2023)
filtdelay = 2.006 1.865 1.936 1.762 1.932 1.875 1.881 2.011
filtoffset = 7.210 7.305 7.372 7.226 7.298 7.258 7.251 7.224
filterror = 0.000 2.025 2.085 4.035 4.095 6.060 6.120 8.070

  4. Verify NTP status.

    show ntp status

    Example:

    RP/0/RP0/CPU0:ios#show ntp status
Sun Nov 5 15:14:36.949 UTC

Clock is synchronized, stratum 3, reference is 192.0.2.1
nominal freq is 1000000000.0000 Hz, actual freq is 44881851.3383 Hz, precision is 2**24
reference time is E8F22D7A.AB020D97 (15:04:26.668 UTC Sun Nov 5 2023)
clock offset is 9.690 msec, root delay is 2.553 msec
root dispersion is 24.15 msec, peer dispersion is 2.13 msec
loopfilter state is 'CTRL' (Normal Controlled Loop), drift is 0.0000212807 s/s
system poll interval is 128, last update was 610 sec ago
authenticate is disabled, panic handling is disabled,
hostname resolution retry interval is 1440 minutes.
    Verifies that the clock is synchronized with the NTP server.

The verify NTP synchronization status task is complete.

NTP troubleshooting reference for Cisco NCS 1010