Application Hosting Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases

PDF

Application Hosting Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases

Host and Activate the PXE Server Docker on Cisco 8201 Router

Updated: September 8, 2026

Want to summarize with AI?

Log in

Host and activate the PXE server Docker container application on the Cisco 8201 router using the application manager to enable clients to download boot images and configuration files from the router.

Procedure

  1. Install the optional RPM xr-pxeserver on the router.

    Example:

    Router#install package add xr-pxeserver
Router#install apply restart
Router#install commit

    When the optional RPM xr-pxeserver is installed and activated, the pxe_svr_mgr process is instantiated. The pxe_svr_mgr process handles installation and updating the PXE server Docker RPM (pxe-server-docker.rpm) with the application manager. Also, when the optional RPM xr-pxeserver is upgraded, the pxe_svr_mgr process checks for the new version of the pxe-server-docker.rpm. If there is a change in the version number, it updates the existing version on the router to the new Docker RPM version and re-launches the PXE server Docker container for the changes to reflect.

    Note

    After activating the xr-pxeserver RPM package, the pxe_svr_mgr process installs the pxe-server-docker.rpm with application manager only when the ongoing install operation is committed and no more install operations are pending.

  2. Verify the PXE server Docker container application package installed.

    Example:

    Router#show appmgr packages installed
Package
------------------------------------------------------------
pxe-server-2.1.0-ThinXR.x86_64

  3. Create the following folder structure in the /misc/disk1/ path and copy the dhcp.conf and image.iso files to their respective folders.

    Example:

    /server
|---- config
|     |---- dhcpd.conf
|     |---- dhcpd6.conf
|---- images
|     |---- Image-boot.iso
----logs
    Note

    The PXE server Docker container uses the /server/ folder for its operations. This path is mounted to the PXE server Docker using the application manager configuration.

    In case of a dual RP system, it is recommended to create this directory structure under /misc/disk1/mirror/. This automatically syncs the PXE server related files to the standby RP node, making all files available on the new active RP node after RPFO. Otherwise, you must create the directory structure again and copy all the necessary files for the PXE server Docker container.

  4. Configure and activate the PXE server Docker container application on the interface BVI301.

    Example:

    Router#config
Router(config)#appmgr
Router(config-appmgr)#application pxeserver
Router(config-application)#activate type docker source pxe-server docker-run-opts "-it --restart always --cap-add=NET_ADMIN --net=host --log-opt max-size=20m --log-opt max-file=3 -v /misc/disk1/mirror/server:/server " docker-run-cmd "-i BV301 -4 172.16.0.0/12 -6 2001:DB8::/48 -l /server/images -t"
Router(config-application)#commit

    The parameters are:

    • --cap-add=NET_ADMIN --net=host — Mandatory

    • -i <interface> — Mandatory

    • -4 <secondary ipv4 address of BVI>

    • -6 <ipv6 address of BVI>

    • -l <location of image stored> — Default: /server/images

    • -t <1 - tftp enabled, 0 - tftp disabled>

  5. Verify the PXE server Docker container status.

    Example:

    Router(config)#appmgr application exec name pxeserver docker-exec-cmd status
dhcpd                            RUNNING   pid 94, uptime 0:00:05
dhcpd6                           RUNNING   pid 95, uptime 0:00:05
monitor                          RUNNING   pid 96, uptime 0:00:05
nginx                            RUNNING   pid 97, uptime 0:00:05
syslogd                          RUNNING   pid 98, uptime 0:00:05
tftp-hpa4                        RUNNING   pid 101, uptime 0:00:05
tftp-hpa6                        RUNNING   pid 104, uptime 0:00:05

What to do next

The PXE server Docker container is active and the clients can now download the boot image and the configuration file from the PXE server (Cisco 8201 router).