在之前的文章里, 介绍install command升级Cisco 8000的方法, 这篇文章记录下使用PXE bring up一台新的Cisco 8000的过程
- Reload chassis
- 按ESC进入BIOS, 选择Boot Manager —– PXE

3. 输入config 进入图像化界面, 配置net0 <<< 管理口
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 | iPXE initialising devices...okiPXE 1.0.0+ (b965) -- Open Source Network Boot Firmware -- http://ipxe.orgFeatures: DNS HTTP HTTPS TFTP EFI ISO9660_grub MenuiPXE> iPXE> ifopen net0iPXE>iPXE>iPXE> ifstat net0: 08:4f:a9:5c:fb:c9 using i210 on PCI02:00.0 (open) [Link:up, TX:0 TXE:0 RX:10 RXE:3]net1: 00:a0:c9:00:00:00 using x557 on PCI04:00.0 (closed) [Link:down, TX:0 TXE:0 RX:0 RXE:0] [Link status: Down (http://ipxe.org/38086193)]net2: 08:4f:a9:5c:fb:ca using x557 on PCI04:00.1 (closed) [Link:down, TX:0 TXE:0 RX:0 RXE:0] [Link status: Down (http://ipxe.org/38086193)]iPXE>iPXE> config |

4. Boot Cisco 8000 XR image
“boot tftp://10.76.76.160/8000-x64-7.0.14.iso “
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 | iPXE> boot tftp://10.76.76.160/8000-x64-7.0.14.iso <<<<<<<<tftp://10.76.76.160/8000-x64-7.0.14.iso... ok Booting /EFI/BOOT/bootx64.efiWelcome to GRUB!Verifying (cd0)/EFI/BOOT/grub.cfg...(cd0)/EFI/BOOT/grub.cfg verified using Pkcs7 signature.[ 0.000000] Uhhuh. NMI received for unknown reason 3c on CPU 0.[ 0.000000] Do you have a strange power saving mode enabled?[ 0.000000] Dazed and confused, but trying to continueFeb 25 06:31:46.515: Prepare install environmentFeb 25 06:31:46.517: Preparing installation environmentFeb 25 06:31:46.897: Attempting PD notification of reimageFeb 25 06:31:47.563: Succeeded PD notification of reimageFeb 25 06:31:47.565: Attempting to punch watchdogStage2 control register configured to 0x01900001Stage1 control register configured to 0x07080011Watchdog State = Stage 1 (1)Watchdog Timer = 1800Watchdog Stage 1 Config: enable=1, action=1, timer=1800cat: /proc/0/comm: No such file or directoryWatchdog Stage 2 Config: enable=1, action=0, timer=400Feb 25 06:31:47.610: Succeeded punching watchdogFeb 25 06:31:47.612: Wait for install deviceFeb 25 06:31:47.614: Create, format and mount partitionsFeb 25 06:31:47.618: Creating partitions on /dev/sda10000+0 records in10000+0 records out10240000 bytes (10 MB, 9.8 MiB) copied, 0.130044 s, 78.7 MB/sProcess '/etc/udev/scripts/mount.sh' failed with exit code 1.Process '/etc/udev/scripts/mount.sh' failed with exit code 1.Process '/etc/udev/scripts/mount.sh' failed with exit code 1.[ 6.449733] EXT4-fs (sda2): error loading journalFeb 25 06:31:47.866: ENDFeb 25 06:31:47.872: Formatting partitions Physical volume "/dev/sda3" successfully created. Physical volume "/dev/sda3" changed 1 physical volume(s) resized / 0 physical volume(s) not resized Volume group "main-xr-vg" successfully createdFeb 25 06:31:49.777: Saving old /var/log contents Rounding up size to full physical extent 956.00 MiB Logical volume "boot-lv" created. Using default stripesize 64.00 KiB.Process '/etc/udev/scripts/mount.sh' failed with exit code 1.Process '/etc/udev/scripts/mount.sh' failed with exit code 1.Process '/etc/udev/scripts/mount.sh' failed with exit code 1.Process '/etc/udev/scripts/mount.sh' failed with exit code 1. Logical volume "install-rootfs-thinpool" created. Using default stripesize 64.00 KiB.Process '/etc/udev/scripts/mount.sh' failed with exit code 1.Process '/etc/udev/scripts/mount.sh' failed with exit code 1. Logical volume "install-data-thinpool" created.Feb 25 06:31:51.043: Formatting Boot (/dev/main-xr-vg/boot-lv)umount: /dev/main-xr-vg/boot-lv: not mounted Using default stripesize 64.00 KiB.Process '/etc/udev/scripts/mount.sh' failed with exit code 1.Process '/etc/udev/scripts/mount.sh' failed with exit code 1.Process '/etc/udev/scripts/mount.sh' failed with exit code 1.Process '/etc/udev/scripts/mount.sh' failed with exit code 1.Process '/etc/udev/scripts/mount.sh' failed with exit code 1.Process '/etc/udev/scripts/mount.sh' failed with exit code 1. Logical volume "install-rootfs-snapshot-1614234707" created.Feb 25 06:31:51.790: Formatting ThinXR (/dev/main-xr-vg/install-rootfs-snapshot-1614234707)umount: /dev/main-xr-vg/install-rootfs-snapshot-1614234707: not mounted Using default stripesize 64.00 KiB. Rounding up size to full physical extent 4.62 GiBProcess '/etc/udev/scripts/mount.sh' failed with exit code 1.Process '/etc/udev/scripts/mount.sh' failed with exit code 1.Process '/etc/udev/scripts/mount.sh' failed with exit code 1.Process '/etc/udev/scripts/mount.sh' failed with exit code 1.Process '/etc/udev/scripts/mount.sh' failed with exit code 1.Process '/etc/udev/scripts/mount.sh' failed with exit code 1. Logical volume "install-data-log" created.Feb 25 06:31:52.546: Formatting Log (/dev/main-xr-vg/install-data-log)umount: /dev/main-xr-vg/install-data-log: not mounted Using default stripesize 64.00 KiB. Logical volume "install-data-scratch" created.Feb 25 06:31:52.993: Formatting Scratch (/dev/main-xr-vg/install-data-scratch)umount: /dev/main-xr-vg/install-data-scratch: not mounted Using default stripesize 64.00 KiB. Logical volume "install-data-docker" created.Feb 25 06:31:53.437: Formatting Docker (/dev/main-xr-vg/install-data-docker)umount: /dev/main-xr-vg/install-data-docker: not mounted Using default stripesize 64.00 KiB. WARNING: Sum of all thin volume sizes (111.93 GiB) exceeds the size of thin pools and the amount of free space in volume group (48.00 MiB)! For thin pool auto extension activation/thin_pool_autoextend_threshold should be below 100. Logical volume "install-data-disk1" created.Feb 25 06:31:53.879: Formatting Disk1 (/dev/main-xr-vg/install-data-disk1)umount: /dev/main-xr-vg/install-data-disk1: not mountedumount: /dev/sda1: not mountedumount: /dev/sda2: not mountedFeb 25 06:31:53.963: Not formatting Disaster Recovery partitionFeb 25 06:31:53.965: Mounting partitions[ 12.596306] EXT4-fs (sda2): error loading journalmount: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so.Cannot mount '/mnt/disk///mnt/dr_part'Feb 25 06:31:54.301: Setup repo for ISO boot (/mnt/disk/)Feb 25 06:31:54.303: Starting bootstrap for an ISO system. Root mount: /mnt/disk/Feb 25 06:31:54.307: Populating RPM repository with RPMs from the ISOFeb 25 06:32:07.942: Creating internal repository at /mnt/disk//var/opt/cisco/iosxr/install/mirror/iosxr_install_internal_repo/Feb 25 06:32:12.328: Dumping rpm cert into fileFeb 25 06:32:12.330: Dumping RPM Cert into file /mnt/disk//certsFeb 25 06:32:12.419: RPM Release Cert installedFeb 25 06:32:14.028: Copying files into the mirror at /mnt/disk//var/opt/cisco/iosxr/install/mirror/Feb 25 06:32:14.034: Bootstrap for an ISO system donePreparing IMA...Searching for IMA trusted keyring->IMA trusted keyring foundImporting IMA x509 certificate into IMA keyring->IMA certificate found: /etc/keys/dbCisco-3.der (RELEASE)->Certificate imported into IMA keyringFeb 25 06:32:16.991: Install targets (/mnt/disk/:RP:8201)Feb 25 06:32:16.993: Install targetsFeb 25 06:32:16.995: Install TargetsFeb 25 06:32:16.997: Performing preparation prior to installing RPMsFeb 25 06:32:17.012: Preparing IMA labeling environmentAnnounced that card is performing an image installation step: Installing IMA toolsAnnounced that card is performing an image installation step: Installing IMA tools doneFeb 25 06:32:21.976: Installing RPMsAnnounced that card is performing an image installation step: Installing systemd and card-pidAnnounced that card is performing an image installation step: Installing all remaining packagesAnnounced that card is performing an image installation step: Installing all remaining packages doneFeb 25 06:35:01.445: Performing post-install scripts after installing RPMsFeb 25 06:35:01.448: Running post-install scriptsFeb 25 06:35:01.534: Running XR post-install scriptsenabling systemd service dsCreated symlink /mnt/disk/etc/systemd/system/ios-xr.target.requires/ds.service → /etc/systemd/system/ds.service.enabling systemd service xr_startupCreated symlink /mnt/disk/etc/systemd/system/ios-xr.target.requires/xr_startup.service → /etc/systemd/system/xr_startup.service.enabling systemd service xr-installCreated symlink /mnt/disk/etc/systemd/system/ios-xr.target.requires/xr-install.service → /etc/systemd/system/xr-install.service.enabling systemd service lighttpdCreated symlink /mnt/disk/etc/systemd/system/iso-xr.target.wants/lighttpd.service → /etc/systemd/system/lighttpd.service.enabling systemd service xr_kdumpCreated symlink /mnt/disk/etc/systemd/system/multi-user.target.wants/xr_kdump.service → /etc/systemd/system/xr_kdump.service.enabling systemd service xr_cgroupsCreated symlink /mnt/disk/etc/systemd/system/ios-xr.target.requires/xr_cgroups.service → /etc/systemd/system/xr_cgroups.service.enabling systemd service var_log_copierCreated symlink /mnt/disk/etc/systemd/system/sysinit.target.wants/var_log_copier.service → /etc/systemd/system/var_log_copier.service.enabling systemd service fstrimCreated symlink /mnt/disk/etc/systemd/system/ios-xr.target.wants/fstrim.service → /etc/systemd/system/fstrim.service.enabling systemd timer fstrimCreated symlink /mnt/disk/etc/systemd/system/timers.target.wants/fstrim.timer → /etc/systemd/system/fstrim.timer.Feb 25 06:35:08.112: Install bootloader (/mnt/disk/::RP)cp /mnt/disk//boot/grub2-secure/bootx64.efi /mnt/disk//boot/efi/EFI/BOOT/bootx64.efiFeb 25 06:35:08.355: Prepare switch root (/mnt/disk/)Feb 25 06:35:08.357: Attempting PD prepare switch rootFeb 25 06:35:08.361: Succeeded PD prepare switch rootFeb 25 06:35:09.112: Syncing during switch rootFeb 25 06:35:12.754: Attempting to notify PD reimage doneFeb 25 06:35:13.351: Succeeded to notify PD reimage doneFeb 25 06:35:13.353: Attempting to stop punching workdog/usr/local/etc/fpga-functions: line 713: 506 Terminated /usr/local/etc/punch-wd.shStage2 control register configured to 0x01900001Stage1 control register configured to 0x15180011Feb 25 06:35:13.410: Succeeded to stop punching workdogFeb 25 06:35:13.412: Clearing DNF makecache infoFeb 25 06:35:13.415: Switching to new root filesystem (/mnt/disk/:)Feb 25 06:35:13.420: boot = /mnt/disk/, root = , console=ttyS0,115200 boardtype=RP platform=spitfire quiet rootflags=i_version ima_appraise=log ciscoima leaba_svn=1.6.2.4 bigphysarea=10M noissu pci=hpmemsize=0M,hpiosize=0M crashkernel=256M fsck.repair=yes fsck.mode=force intremap=off page_poison=on slab_nomerge vsyscall=noneFeb 25 06:35:13.424: Clearing Boot Option to boot from diskBoot option reg: 0x00000000[ 214.584274] kexec_core: Starting new kernel[ 1.258735] Created proc for bigphysarea Reading all physical volumes. This may take a while... Found volume group "main-xr-vg" using metadata type lvm2 8 logical volume(s) in volume group "main-xr-vg" now active 8 logical volume(s) in volume group "main-xr-vg" now active 8 logical volume(s) in volume group "main-xr-vg" now activeOverriding bzImagefsck from util-linux 2.28.1e2fsck 1.43 (17-May-2016)Pass 1: Checking inodes, blocks, and sizesPass 2: Checking directory structurePass 3: Checking directory connectivityPass 4: Checking reference countsPass 5: Checking group summary informationBoot: 24/61184 files (4.2% non-contiguous), 38149/244736 blocksfsck from util-linux 2.28.1e2fsck 1.43 (17-May-2016)Disk1: recovering journalPass 1: Checking inodes, blocks, and sizesPass 2: Checking directory structurePass 3: Checking directory connectivityPass 4: Checking reference countsPass 5: Checking group summary informationDisk1: 11/3407872 files (0.0% non-contiguous), 259923/13612032 blocksfsck from util-linux 2.28.1e2fsck 1.43 (17-May-2016)Docker: recovering journalPass 1: Checking inodes, blocks, and sizesPass 2: Checking directory structurePass 3: Checking directory connectivityPass 4: Checking reference countsPass 5: Checking group summary informationDocker: 11/378256 files (0.0% non-contiguous), 59477/1512448 blocksfsck from util-linux 2.28.1e2fsck 1.43 (17-May-2016)Log: recovering journalPass 1: Checking inodes, blocks, and sizesPass 2: Checking directory structurePass 3: Checking directory connectivityPass 4: Checking reference countsPass 5: Checking group summary informationFree blocks count wrong (1156200, counted=1155999).Fix? yesFree inodes count wrong (303093, counted=303081).Fix? yesLog: ***** FILE SYSTEM WAS MODIFIED *****Log: 23/303104 files (0.0% non-contiguous), 54369/1210368 blocksfsck from util-linux 2.28.1e2fsck 1.43 (17-May-2016)Scratch: recovering journalPass 1: Checking inodes, blocks, and sizesPass 2: Checking directory structurePass 3: Checking directory connectivityPass 4: Checking reference countsPass 5: Checking group summary informationFree blocks count wrong (874838, counted=874836).Fix? yesFree inodes count wrong (227125, counted=227123).Fix? yesScratch: ***** FILE SYSTEM WAS MODIFIED *****Scratch: 13/227136 files (0.0% non-contiguous), 32428/907264 blocksfsck from util-linux 2.28.1e2fsck 1.43 (17-May-2016)ThinXR: recovering journalPass 1: Checking inodes, blocks, and sizesPass 2: Checking directory structurePass 3: Checking directory connectivityPass 4: Checking reference countsPass 5: Checking group summary informationFree blocks count wrong (11863675, counted=10781100).Fix? yesFree inodes count wrong (3025109, counted=2975795).Fix? yesThinXR: ***** FILE SYSTEM WAS MODIFIED *****ThinXR: 49325/3025120 files (0.3% non-contiguous), 1318484/12099584 blocksInvoke selinux initialization...Enable selinux to relabel filesystem from initramfsChecking SELinux security contexts: * First booting, filesystem will be relabeled... |

The blog from link: http://imxing.cn/wp-trackback.php?p=1004