cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
206
Views
0
Helpful
2
Replies

PXE Based Installations of Cisco 9800-CL

blair.bissett
Level 1
Level 1

In short, I'm looking to setup 'deploy and destroy' within a lab environment, and I'm currently using an instance of The Foreman to achieve this, having configured the lab's vSphere instance as a Compute Resource within Foreman. I'm currently able to create and destroy Linux and Windows VMs with ease within the Foreman GUI.

Next up is deploy and destroy ops for 9800-CL instances using Foreman. With the 9800 ISO downloaded, I've been able to glean that we're using GRUB2 as the bootloader. Referencing official GRUB2 docs helped me refresh my knowledge of GRUB.CFG. BothPXE instance of GRUG.CFG are identical save for a few 'efi' related additions in the EFI version. I want to say I understand the following menu stanza, with exception of the /packages.conf, as there's no actual directory or file contained on the ISO with this name, though there's one that closely resembles this named PACKAGES.CON. I have the impression that there's some special sauce here, particularly when you consider that this isn't really a regular Linux distro.

At this point, my best assumption is that I should possibly be bootstrapping one of the EFI's from the ISO instead of generic grub64.efi being used by Foreman.

I believe that once I've figured out the /packages.conf bit, simply updating the cd0 device to a TFTP or HTTP location should get me going (which also assumes that these functions are enabled within GRUB).

menuentry 'C9800-CL Virtual (VGA) Console - 2023-03-14_18.14' --class gnu-linux --class gnu --class os {
set root=(cd0)
linuxefi /packages.conf rw root=/dev/ram max_loop=64 HARDWARE=virtual VMCONSOLE quiet console=tty0 SR_BOOT=cdrom0:packages.conf
}

D:\BOOT
D:\BOOT.CAT
D:\C9800_C0.PKG
D:\C9800_C1.PKG
D:\EFI
D:\IMAGES
D:\PACKAGES.CON
D:\_PKGINFO
D:\BOOT\GRUB
D:\BOOT\GRUB\GRUB.CFG
D:\BOOT\GRUB\GRUBENV
D:\EFI\BOOT
D:\EFI\BOOT\BOOTX64.EFI
D:\EFI\BOOT\CISCO_SH.EFI
D:\EFI\BOOT\GRUB.CFG
D:\EFI\BOOT\GRUBENV
D:\EFI\BOOT\GRUBX64.EFI
D:\EFI\BOOT\MSFT_SHI.EFI
D:\IMAGES\EFIBOOT.IMG
D:\IMAGES\I386CDBO.IMG

2 Replies 2

marce1000
Hall of Fame
Hall of Fame

 

  - You won't be able to get this going , these are the only supported hypervisors :
          https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/technical-reference/c9800-cl-dg.html#Supportedhypervisorversions

 M.



-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
    When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

Not sure I understand.

Foreman itself is not a hypervisor, it's a "lifecycle management tool for physical and virtual servers." In my case I'm using it to manage (create and destroy) VMs in my lab's vSphere instance, and this specific goal is to create and destroy 9800-CL instances at will within my lab's vSphere environment for doing labs. 

The technical bits that I believe I'm looking for direction on have to do with the specifics of the 9800-CL's GRUB and/or bootloader.

I realize that there are non-PXE approaches to this, but I'm very interested in getting the PXE method through Foreman to work.

Review Cisco Networking for a $25 gift card