System Setup and Software Installation Guide for Cisco NCS 1014, IOS XR Releases 26.x.x

PDF

System Setup and Software Installation Guide for Cisco NCS 1014, IOS XR Releases 26.x.x

iPXE boot methods

Updated: June 9, 2026

Want to summarize with AI?

Log in

Explains the iPXE Preboot Execution Environment included in management interface network cards and its role in reimaging Cisco NCS 1014 or booting the chassis when the bootable partition is missing or has failed.

A iPXE boot method is a system firmware process that

  • operates at the UEFI level using the network card of management interfaces,

  • enables you to reimage the Cisco NCS 1014 or boot the chassis in case of missing or failed bootable partitions, and

  • downloads and installs the ISO image, then bootstraps the system into the new installation.

iPXE acts as a bootloader and provides the flexibility to choose the image that the system will boot based on the Platform Identifier (PID), the Serial Number, or the management mac-address. You must define iPXE in the DHCP server configuration file.

iPXE boot methods

Note

The time taken for iPXE to download the ISO image depends on the network speed. Ensure that the network speed is sufficient to complete the image download in less than 10 minutes. The chassis reloads if the image is not downloaded by 10 minutes.

To start the iPXE boot process, use one of these methods.

  • Preferred method: Run either the reload bootmedia network location all command or the reload bootmedia network location 0/RP0 command.

  • Alternative method: Power cycle the Cisco NCS 1014 chassis and start the iPXE boot process in the BIOS interface.

Note

Software installation using iPXE boot with IPv6 is not supported.

Configure the DHCP server

Set up a DHCP server for IPv4, IPv6, or both protocols so that iPXE can boot Cisco NCS 1014.

A DHCP server is essential for the iPXE boot process and must be configured to support either IPv4, IPv6, or both. This configuration allows the network client to obtain the necessary boot and provisioning files automatically.

Note

For DHCPv6, a routing advertisement (RA) message must be sent to all nodes in the network to indicate which method is to be used to obtain the IPv6 address. Configure the Router-advertise-daemon (radvd, install using yum install radvd ) to allow the client to send the DHCP request. For 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;
        };
};

Procedure

1.

Create the dhcpd.conf file (for IPv4, IPv6, or both communication protocols), the dhcpv6.conf file (for IPv6), or both, in the /etc/ directory.

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

Test the server when the DHCP server is running.

For IPv4, you can test the server by using either the MAC address or the serial number of the chassis:

  • Use the MAC address of the chassis and ensure that the configuration is successful.

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

    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:xx:xx:xx;
        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 DHCP server is configured and is ready to respond to iPXE boot requests from Cisco NCS 1014.

Boot the Cisco NCS 1014 using iPXE

Enable network boot and reimage of the Cisco NCS 1014 using iPXE.

Use this task to boot the Cisco NCS 1014 from the network with iPXE for reimaging, using either the command-line interface or BIOS selections.

Before you begin

Before you perform the iPXE boot, ensure that:

  • The DHCP server is set and running.

  • The management port of the Cisco NCS 1014 chassis is in the UP state.

Procedure

1.

Run the reload bootmedia network location all command or the reload bootmedia network location 0/RP0 command to initiate the iPXE boot process and reimage the chassis.

Example:

RP/0/RP0/CPU0:ios#reload bootmedia network location all
Mon Dec  4 09:49:14.220 UTC
Proceed with reload? [confirm]
Preparing system for backup. This may take a few minutes especially for large configurations.
	Status report: node0_RP0_CPU0: BACKUP INPROGRESS
	Status report: node0_RP0_CPU0: BACKUP HAS COMPLETED SUCCESSFULLY
[Done]

[ 3490.493853] systemd-shutdown[1]: Could not detach DM /dev/dm-9: Device or resource busy
[ 3490.601094] systemd-shutdown[1]: Could not detach DM /dev/dm-8: Device or resource busy
[ 3490.710401] systemd-shutdown[1]: Could not detach DM /dev/dm-7: Device or resource busy
[ 3490.849417] systemd-shutdown[1]: Failed to finalize  DM devices, ignoring
[ 3492.144874] Unsupported TPM Send Cmd! tpm_tag=8001,tpm_ordinal=0145
[ 3492.229149] tpm tpm0: tpm_try_transmit: send(): error -11
[ 3492.307885] reboot: Restarting system
Shelf Assembly Reset
NCS1014, Initializing Devices
Booting from Primary Flash
Aldrin: Programmed MI 4
Continue boot...
Version 2.19.1266. Copyright (C) 2023 American Megatrends, Inc.
BIOS Date: 10/06/2023 16:47:27 Ver: 0ACHI0480
Press <DEL> or <ESC> to enter setup.
TAM: Chip DB Verified

Software Boot OK, Validated
iPXE initialising devices...ok

iPXE 1.0.0+ (8b3e3) -- Open Source Network Boot Firmware -- http://ipxe.org
Features: DNS HTTP HTTPS TFTP VLAN EFI ISO9660 ISO9660_grub Menu
Trying net0-2051 and net0-2052...
net0-2051: 40:14:82:ba:d1:42 using NII on NII-0000:06:00.0 (open)
  [Link:down, TX:0 TXE:0 RX:0 RXE:0]
  [Link status: Unknown (http://ipxe.org/1a086194)]

Example:

RP/0/RP0/CPU0:sanity_176#reload bootmedia network location 0/RP0
Mon Feb 10 16:34:42.282 IST
Proceed with reload? [confirm]

RP/0/RP0/CPU0:Feb 10 16:34:44.277 IST: shelfmgr_exec_cli[65652]: %PLATFORM-SHELFMGR-6-USER_OP : User mols requested 'PXE reimage' of 0/RP0
RP/0/RP0/CPU0:Feb 10 16:34:44.284 IST: processmgr[51]: %OS-SYSMGR-6-INFO : Received request for graceful go-down from shelfmgr. Reload Reason:User initiated card reimage-network. Timeout 55

Preparing system for backup. This may take a few minutes especially for large configurations.
RP/0/RP0/CPU0:Feb 10 16:34:44.284 IST: processmgr[51]: %OS-SYSMGR-6-INFO : Prepared RMF to reboot
	Status report: node0_RP0_CPU0: BACKUP INPROGRESS
RP/0/RP0/CPU0:sanity_176#	Status report: node0_RP0_CPU0: BACKUP HAS COMPLETED SUCCESSFULLY
[Done]
RP/0/RP0/CPU0:Feb 10 16:34:45.974 IST: obflmgr[317]: %PLATFORM-OBFL-6-INFO : Unmounted OBFL directory for 0/Rack
RP/0/RP0/CPU0:Feb 10 16:34:46.225 IST: obflmgr[317]: %PLATFORM-OBFL-6-INFO : Unmounted OBFL directory for 0/RP0/CPU0
RP/0/RP0/CPU0:Feb 10 16:34:46.555 IST: processmgr[51]: %MGBL-SCONBKUP-6-INTERNAL_INFO : Reload debug script successfully spawned
--
--
[438336.926067] reboot: Restarting system


..         *** Cisco ***
System Initializing..
..


Initializing Devices

Booting from Primary Flash
MI: Skipping reprogram
Version 2.19.1266. Copyright (C) 2024 American Megatrends, Inc.
BIOS Date: 10/28/2024 12:47:04 Ver: 0ACHI0500
Press <DEL> or <ESC> to enter setup.
TAM: Chip DB Verified

Software Boot OK, Validated

iPXE initialising devices...ok

iPXE 1.0.0+ (8b3e3) -- Open Source Network Boot Firmware -- http://ipxe.org
Features: DNS HTTP HTTPS TFTP VLAN EFI ISO9660 ISO9660_grub Menu
Trying net0-2051 and net0-2052...
net0-2051: 9c:38:18:88:a4:1d using NII on NII-0000:06:00.0 (open)
  [Link:down, TX:0 TXE:0 RX:0 RXE:0]
  [Link status: Unknown (http://ipxe.org/1a086194)]
Configuring (net0-2051 9c:38:18:88:a4:1d)...... ok
--
--
net0-2052: fe80::9e38:18ff:fe88:a41e/64
Filename: http://4.25.30.34/Kepler/25_1_1_Images/ncs1010-x64.iso
http://4.25.30.34/Kepler/25_1_1_Images/ncs1010-x64.iso... ok
ncs1010-x64.iso : 1810485248 bytes
Booting /EFI/BOOT/bootx64.efi
Welcome to GRUB!
2.

Aternatively, initiate the boot process using the BIOS interface.

  1. Reboot Cisco NCS 1014 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:

TAM: Chip DB Verified
Software Boot OK, Validated
iPXE initialising devices...ok
iPXE 1.0.0+ (8b3e3) -- Open Source Network Boot Firmware -- http://ipxe.org
Features: DNS HTTP HTTPS TFTP VLAN EFI ISO9660 ISO9660_grub Menu
Trying net0-2051 and net0-2052...
net0-2051: 9c:38:18:88:a4:1d using NII on NII-0000:06:00.0 (open)
[Link:down, TX:0 TXE:0 RX:0 RXE:0]
[Link status: Unknown (http://ipxe.org/1a086194)]
Configuring (net0-2051 9c:38:18:88:a4:1d)...... ok
net0: fe80::9e38:18ff:fe88:a41d/64
net1: fe80::9e38:18ff:fe88:a420/64 (inaccessible)
net2: fe80::9e38:18ff:fe88:a421/64 (inaccessible)
net3: fe80::9e38:18ff:fe88:a422/64 (inaccessible)
net0-2051: 4.25.9.3/255.255.0.0 gw 4.25.0.1
net0-2051: fe80::9e38:18ff:fe88:a41d/64
net0-2052: fe80::9e38:18ff:fe88:a41e/64
Filename: http://4.25.30.34/Kepler/25_1_1_Images/ncs1010-x64.iso
http://4.25.30.34/Kepler/25_1_1_Images/ncs1010-x64.iso... ok
ncs1010-x64.iso : 1810485248 bytes
Booting /EFI/BOOT/bootx64.efi
Welcome to GRUB!
/EndEntire
error: no such device: ((cd0)/EFI/BOOT)/EFI/BOOT/grub.cfg.
Verifying (cd0)/EFI/BOOT/grub.cfg...
(cd0)/EFI/BOOT/grub.cfg verified using Pkcs7 signature.
The Cisco NCS 1014 successfully initiates the iPXE network boot process, loading the designated image and displaying boot confirmation messages. Once complete, the system is ready for further installation or configuration.