Esxi 5.1 “speedy boot” vs “slow boot” (…Microsoft Cluster e boot from San)

Posted on 5 settembre 2013 di

0


Ci trovavamo in una situazione anormale, nella quale impieghavamo 16 minuti per fare boot delle lame appartenenti al nostro cluster esx dopo l’upgrade a 5.1.

Per indagare abbiamo notato nei log del sysboot:

……..precedenti…..

[14:09:22.615356] sysboot: auto-configure-networking 62

[14:09:22.615480] sysboot: rpc 63

[14:09:22.645938] sysboot: software-iscsi 64

[14:09:22.703278] sysboot: storage-path-claim 65

[14:19:31.201665] sysboot: system-image-cache 66

[14:19:31.201751] sysboot: inetd 67

[14:19:31.203012] sysboot: fcoe-config 68

[14:19:31.208830] sysboot: restore-paths 69

[14:19:31.266931] sysboot: vmfs 70

[14:19:31.331012] sysboot: mount-disk-fs 71

[14:22:31.923274] sysboot: auto-configure-storage 72

[14:22:31.923341] sysboot: restore-bootbanks 73

[14:24:02.084679] sysboot: dump-partition 74

[14:24:02.095803] sysboot: tag-boot-bank 75

[14:24:02.122223] sysboot: pingback 76

[14:24:02.122278] sysboot: nfs 77

[14:24:02.157541] sysboot: restore-nfs-volumes 78

[14:24:02.158900] sysboot: configure-locker 79

[14:24:02.211344] sysboot: set-acceptance-level 80

[14:24:02.775226] sysboot: scratch-storage 81

[14:24:02.981983] sysboot: restore-host-cache 82

[14:24:02.996530] sysboot: restore-system-swap 83

[14:24:03.129019] sysboot: Instrumentation

[14:24:03.129019] sysboot: Jumpstart duration: 938.351348

Quindi seguendo questo articolo: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1016106

sembra che ogni volta il rescan od il boot erano lenti perché esx viene “disturbato nelle operazioni”  dalle lun RDM del Microsoft Cluster (tra l’altro l’articolo fa esempio che per 3 rdm ci vogliono 10 minuti a bootare…corrisponde con la nostra situazione).

 Come workaround vanno quindi riservate le lun MS lanciando il comando dedicato sugli esx coinvolti (oppure su uno solo memorizzando però le impostazioni su un host profile da applicare poi agli altri ovviamente).

 esxcli storage core device setconfig -d naa.xxxxxxxxxxx –perennially-reserved=true

 Ad esempio per le lun 18,19 e 21 (del nostro cluster ms):

esxcli storage core device setconfig -d naa.60a980004335434c2f6f534a30583153 –perennially-reserved=true

esxcli storage core device setconfig -d naa.60a980004335434c2f6f534c2f394c68 –perennially-reserved=true

esxcli storage core device setconfig -d naa.60a980004335434c2f6f535172503153 –perennially-reserved=true

Rilanciando un reboot invece di 16 minuti totali a partire dal loading di esx (superato il bios) impieghiamo ora solamente 50 secondi

 ……..precedenti…..

 [16:04:08.579654] sysboot: record-replay 46

[16:04:08.611012] sysboot: dvfilters-vmkapi-compatibility 47

[16:04:08.629590] sysboot: dvfilter-generic-fastpath 48

[16:04:08.664670] sysboot: dvfilter-config 49

[16:04:08.664686] sysboot: firewall 50

[16:04:09.015898] sysboot: hbr 51

[16:04:09.055064] sysboot: vds-vmkapi-compatibility 52

[16:04:09.055088] sysboot: vds-config 53

[16:04:09.055114] sysboot: vmotion 54

[16:04:09.178689] sysboot: iscsi-vmkapi-compatibility 55

[16:04:09.200185] sysboot: networking-ibmc 56

[16:04:09.262073] sysboot: storage-drivers 57

[16:04:23.439111] sysboot: vmkdevmgr 58

[16:04:23.440391] sysboot: filesystem-drivers 59

[16:04:23.506372] sysboot: restore-networking 60

[16:04:26.365952] sysboot: dvfilters 61

[16:04:26.366446] sysboot: auto-configure-networking 62

[16:04:26.366568] sysboot: rpc 63

[16:04:26.396694] sysboot: software-iscsi 64

[16:04:26.447714] sysboot: storage-path-claim 65

[16:04:34.719928] sysboot: system-image-cache 66

[16:04:34.720014] sysboot: inetd 67

[16:04:34.721373] sysboot: fcoe-config 68

[16:04:34.726754] sysboot: restore-paths 69

[16:04:34.784949] sysboot: vmfs 70

[16:04:34.842079] sysboot: mount-disk-fs 71

[16:04:35.223686] sysboot: auto-configure-storage 72

[16:04:35.223795] sysboot: restore-bootbanks 73

[16:04:35.323043] sysboot: dump-partition 74

[16:04:35.334090] sysboot: tag-boot-bank 75

[16:04:35.345394] sysboot: pingback 76

[16:04:35.345427] sysboot: nfs 77

[16:04:35.379361] sysboot: restore-nfs-volumes 78

[16:04:35.380792] sysboot: configure-locker 79

[16:04:35.433480] sysboot: set-acceptance-level 80

[16:04:36.014210] sysboot: scratch-storage 81

[16:04:36.236893] sysboot: restore-host-cache 82

[16:04:36.247003] sysboot: restore-system-swap 83

[16:04:36.372591] sysboot: Instrumentation

[16:04:36.372591] sysboot: Jumpstart duration: 42.573842

Anche il rescan del vmfs ora è immediato, mentre prima impiegava almeno un minuto.

Annunci
Posted in: Vmware