Quantcast
Channel: VMware Communities : Popular Discussions - vSphere Hypervisor
Viewing all articles
Browse latest Browse all 47699

vSphere 5.5 - Boot Menu - Scripted vsphere Installer

$
0
0

Sigh...  for support reasons of a software vendor I have to maintain a 5.5u2 cluster.

 

Trying to stage for class / POC environment (hyperconvergence so has to work on hardware level), so I have to handle hardware

 

Goal:

1) Use kickstart structure answer files to load the nodes

2) Create a boot menu from vSphere 5.5u2 (oem customized versions) to allow user to boot USB image over IPMI, select node they are on, and it feeds it the correct ks.cfg file

 

I followed various guides / notes:

vSphere Boot Menu Guides

 

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2004582

Template attached but details for fields and assumptions below.

 

 

Create menu for the list of nodes to each customization answer file

Documentation:

http://www.virtuallyghetto.com/2015/06/how-to-create-custom-esxi-boot-menu-to-support-multiple-kickstart-files.html

http://www.virtuallyghetto.com/2011/07/automating-esxi-5x-kickstart-tips.html

 

But either it is a translation issue of my understanding of their notes, or issue with 5.5u2 or ???

 

###

 

Step 1:  Create bootable USB vSphere OS key on 2GB key

 

I named key label "esx5U2_auto_install"

 

I followed instructions and used tool rufus

https://tinkertry.com/rufus-takes-2-minutes-to-create-a-bootable-usb-flash-drive-for-esxi-installation

 

I connected and used OEM vSphere cutomization ISO for vSphere 5.5u2

 

 

Step 2:  Create answer file response files

 

Example is node 1-4 cluster.

 

on USB create directory "KS" and in that create files  "NODE1.cfg" -"NODE4.cfg"

 

Example file for node1

node1 ks.cfg

 

# Accept vSphere license ULA

vmaccepteula

 

# Set root password

rootpw password

 

# Clear drive partition on first device in device list

clearpart --firstdisk --overwritevmfs

 

# Set installation target to be first drive it finds in device list

install --firstdisk --overwritevmfs

 

# Set static IP for vmnic0 per Spectrum Accelerate table

network --bootproto=static --device=vmnic0 --ip=172.20.11.197 --netmask=255.255.255.0 --gateway=172.20.11.1 --hostname=node1 -- nameserver=172.20.12.100,172.20.13.100 vlanid=11

 

# Reboot host

reboot

 

 

# Post Installation goodies

# Enable SSH and Tech Suport modes

vim-cmd hostsvc/enable_esx_shell

vim-cmd hostsvc/start_esx_shell

vim-cmd hostsvc/enable_ssh

vim-cmd hostsvc/start_ssh

esxcli network firewall ruleset set --ruleset-id sshClient --enabled yes

 

 

Step 3: Create menu for nodes

 

 

Edit file "isolinux.cfg" for above host menu options.  Save this file in root of USB key.

Design is to boot over USB attached drive through the IMM (or local attached USB)

DEFAULT menu.c32

MENU TITLE 5.5u2 Boot Menu

NOHALT 1

PROMPT 0

TIMEOUT 80

#

LABEL hddboot

  LOCALBOOT 0x80

  MENU LABEL ^Boot from local disk

#

LABEL IBM Spectrum Accelerate Node 1 Install

  KERNEL mboot.c32

  APPEND -c boot.cfg ks=usb:/KS/NODE1.cfg +++

  MENU LABEL ^1 Node1 Install

#

LABEL IBM Spectrum Accelerate Node 2 Install

  KERNEL mboot.c32

  APPEND -c boot.cfg ks=usb:/KS/NODE2.CFG +++

  MENU LABEL ^2 Node2 Install

#

LABEL IBM Spectrum Accelerate Node 3 Install

  KERNEL mboot.c32

  APPEND -c boot.cfg ks=usb:/KS/NODE3.CFG +++

  MENU LABEL ^3 Node3 Install

#

 

#############

 

 

 

But...  When I boot it just runs normal script to install vSphere from basic answer file

 

What I think I am missing is what do I need to do to the boot.cfg file to get it to call the menu (DEFAULT menu.c32)

 

 

As usual, all help is appreciated.

 

 

 

PS: I also tried to just effect the base load for just test of answer file (aka without fancy menu) by modification of "boot.cfg" as noted below...and it booted normal installer and ignored answers

boot.cfg  - node 1 direct ks.cfg call

bootstate=0

title=Loading ESXi installer

kernel=/tboot.b00

kernelopt=ks=/KS/NODE1.cfg

modules=/b.b00 --- /jumpstrt.gz --- /useropts.gz --- /k.b00 --- /chardevs.b00 --- /a.b00 --- /user.b00 --- /sb.v00 --- /s.v00 --- /brcm.v00 --- /misc_cni.v00 --- /net_bnx2.v00 --- /net_bnx2.v01 --- /net_cnic.v00 --- /net_tg3.v00 --- /scsi_bnx.v00 --- /scsi_bnx.v01 --- /brcdprov.v00 --- /net_bna.v00 --- /scsi_bfa.v00 --- /elxnet.v00 --- /emulex_c.v00 --- /ima_be2i.v00 --- /lpfc.v00 --- /scsi_be2.v00 --- /ianet_ci.v00 --- /net_igb.v00 --- /net_ixgb.v00 --- /lsiprovi.v00 --- /scsi_meg.v00 --- /scsi_mpt.v00 --- /scsi_mpt.v01 --- /concrete.v00 --- /filetran.v00 --- /fupb.v00 --- /fwupdate.v00 --- /hwckvm.v00 --- /ilfu.v00 --- /immpasst.v00 --- /pciinfo.v00 --- /soibms.v00 --- /mlnxprov.v00 --- /net_mlx4.v00 --- /net_mlx4.v01 --- /ima_qla4.v00 --- /net_qlcn.v00 --- /net_qlge.v00 --- /qlnative.v00 --- /qlogic_c.v00 --- /scsi_qla.v00 --- /ata_pata.v00 --- /ata_pata.v01 --- /ata_pata.v02 --- /ata_pata.v03 --- /ata_pata.v04 --- /ata_pata.v05 --- /ata_pata.v06 --- /ata_pata.v07 --- /block_cc.v00 --- /ehci_ehc.v00 --- /weaselin.t00 --- /esx_dvfi.v00 --- /xlibs.v00 --- /ipmi_ipm.v00 --- /ipmi_ipm.v01 --- /ipmi_ipm.v02 --- /misc_dri.v00 --- /mtip32xx.v00 --- /net_be2n.v00 --- /net_e100.v00 --- /net_e100.v01 --- /net_enic.v00 --- /net_forc.v00 --- /net_nx_n.v00 --- /net_vmxn.v00 --- /ohci_usb.v00 --- /rste.v00 --- /sata_ahc.v00 --- /sata_ata.v00 --- /sata_sat.v00 --- /sata_sat.v01 --- /sata_sat.v02 --- /sata_sat.v03 --- /sata_sat.v04 --- /scsi_aac.v00 --- /scsi_adp.v00 --- /scsi_aic.v00 --- /scsi_fni.v00 --- /scsi_hps.v00 --- /scsi_ips.v00 --- /scsi_lpf.v00 --- /scsi_meg.v01 --- /scsi_meg.v02 --- /scsi_mpt.v02 --- /scsi_mpt.v03 --- /scsi_qla.v01 --- /uhci_usb.v00 --- /tools.t00 --- /lnvcusto.v00 --- /xorg.v00 --- /imgdb.tgz --- /imgpayld.tgz

build=

updated=0


Viewing all articles
Browse latest Browse all 47699

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>