{"id":1271,"date":"2022-01-04T21:33:32","date_gmt":"2022-01-04T20:33:32","guid":{"rendered":"https:\/\/virtualguru.cz\/?p=1271"},"modified":"2022-06-27T13:03:19","modified_gmt":"2022-06-27T11:03:19","slug":"nsx-t-upgrade-postrehy","status":"publish","type":"post","link":"https:\/\/virtualguru.cz\/en\/2022\/01\/04\/nsx-t-upgrade-postrehy\/","title":{"rendered":"NSX-T upgrade – post\u0159ehy"},"content":{"rendered":"

Spousta z V\u00e1s se ji\u017e setkala s SDN (software define networking) od spole\u010dnosti VMware. Nejprve tu s n\u00e1mi bylo NSX-V, kter\u00e9 pomalu m\u00ed\u0159\u00ed do „propadli\u0161t\u011b d\u011bjin“ a na jeho m\u00edsto nastoupilo NSX-T. VMware implementuje do NSX-T nov\u00e9 a nov\u00e9 funkce a t\u00edm p\u00e1dem je t\u0159eba nasazovat nov\u00e9 a nov\u00e9 verze. Upgrade jako takov\u00fd, by m\u011bl b\u00fdt pln\u011b automatick\u00fd, m\u00e1 i step-by-step pr\u016fvodce, ale ne v\u017edy je upgrade tak hladk\u00fd jak Upgrade Guide tvrd\u00ed.<\/p>\n

R\u00e1d bych v tomto \u010dl\u00e1nku shrnul n\u011bkter\u00e9 post\u0159ehy, kter\u00e9 jsem nabyl p\u0159i, nakonec v\u017edy \u00fasp\u011b\u0161n\u00fdch, upgradech. Z\u00e1rove\u0148 douf\u00e1m budu schopen pr\u016fb\u011b\u017en\u011b tento \u010dl\u00e1nek dopl\u0148ovat o dal\u0161\u00ed „hinty.“<\/p>\n

Jako prvn\u00ed a nejd\u016fle\u017eit\u011bj\u0161\u00ed doporu\u010duji zkontrolovat interoperabilitu s ostatn\u00edmi nasazen\u00fdmi produkty VMware. Pokud m\u00e1te nasazen\u00e9, nebo nasazujete ESXi zcela jist\u011b ve Va\u0161\u00ed infrastruktu\u0159e m\u00e1te ji\u017e nap\u0159. vRealize Operations nebo t\u0159eba vRealize Network Insight.<\/p>\n

Interoperability Matrix je zde: https:\/\/interopmatrix.vmware.com\/Interoperability<\/a><\/p>\n

Jako dal\u0161\u00ed krok, pokud je\u0161t\u011b nem\u00e1te nastaven\u00e9m doporu\u010duji z\u00e1lohu konfigurace NSX-T. Ta se konfiguruje p\u0159es\u00a0System – Backup & Restore<\/strong>.<\/p>\n

\"\"<\/a><\/p>\n

Pozor: podporov\u00e1n je pouze protokol STFTP, tj. mus\u00edte m\u00edt k dispozici p\u0159\u00edslu\u0161n\u00e9 \u00falo\u017ei\u0161t\u011b. Pro „odp\u016frce“ p\u0159\u00edkazov\u00e9 \u0159\u00e1dky doporu\u010duji nap\u0159. Linux Turnkey, kter\u00fd se d\u00e1 st\u00e1hnout ve form\u011b appliance a konfiguruje se p\u0159es webov\u00e9 GUI.<\/em><\/p>\n

Kdy\u017e u\u017e zmi\u0148uji z\u00e1lohov\u00e1n\u00ed, to m\u00e1 jednu zaj\u00edmavou „vychyt\u00e1vku“ a to \u017ee umo\u017e\u0148uje nejenom z\u00e1lohovat v pravideln\u00fdch intervalech, ale i p\u0159i ka\u017ed\u00e9 zm\u011bn\u011b konfigurace. To v\u0159ele doporu\u010duji, p\u0159edejdete pak nemil\u00e9mu p\u0159ekvapen\u00ed, kdy\u017e obnov\u00edte konfigurace a n\u011bkter\u00e9 zm\u011bny v\u00e1m tam budou chyb\u011bt, nebo\u0165 nastaly v dob\u011b mezi pravideln\u00fdmi z\u00e1lohami a p\u00e1dem. U t\u00e9to volby je ale t\u0159eba myslet na to, \u017ee se bude ukl\u00e1dat hodn\u011b dat, tj. v c\u00edlov\u00e9m \u00falo\u017ei\u0161ti mus\u00ed b\u00fdt dostatek m\u00edsta.<\/p>\n

Tato volba se skr\u00fdv\u00e1 pod z\u00e1lo\u017ekou System – Backup & Restore –<\/strong>\u00a0Scheduled<\/strong><\/p>\n

\"\"<\/a><\/p>\n

M\u00e1me tedy zkontrolov\u00e1nu kompatibilitu, provedenou z\u00e1lohu a m\u016f\u017eeme st\u00e1hnout a naimportovat upgrade bal\u00ed\u010dek. Ten je ve form\u00e1tu .mub<\/strong> a m\u00e1 v\u011bt\u0161inou cca 6-7 GB. D\u016frazn\u011b doporu\u010duji p\u0159e\u010d\u00edst si Release Notes a Upgrade Guide p\u0159ed ka\u017ed\u00fdm upgradem, p\u0159edejdete pak nep\u0159\u00edjemnostem. Nap\u0159. p\u0159i upgrade z NSX-T z verze tu\u0161\u00edm 2.5 na 3.0 bylo nutn\u00e9 p\u0159ed upgrade p\u0159ipojit k NSX manager\u016fm dal\u0161\u00ed disk o velikosti 100 GB.<\/p>\n

Tento bal\u00ed\u010dek pak naimportujete p\u0159es NSX-T GUI volbu\u00a0System – Upgrade –\u00a0 NSX Upgrade<\/strong><\/p>\n

\"\"<\/a><\/strong><\/p>\n

\"\"<\/a><\/p>\n

Jakmile m\u00e1te naimportovn\u00fd\u00a0mub<\/strong> soubor s upgrade bal\u00ed\u010dkem, m\u016f\u017eete spustit\u00a0pre-check<\/strong>.<\/p>\n

\"\"<\/a><\/p>\n

\"\"<\/a><\/p>\n

D\u00e1 se sice p\u0159esko\u010dit, ale odhal\u00ed mo\u017en\u00e9 probl\u00e9my, kter\u00e9 mohou vzninkout p\u0159i upgrade. Typick\u00fdm probl\u00e9mem je, \u017ee na n\u011bkter\u00fdch ESXi hypervizorech nen\u00ed dostatek voln\u00e9ho m\u00edsta v \/tmp odd\u00edle, kam se instaluj\u00ed\u00a0 VIB s NSX-T.\u00a0 Je t\u0159eba minim\u00e1ln\u011b 180 MB voln\u00e9ho m\u00edsta. Pokud pou\u017e\u00edv\u00e1te USB\/SD karty jako bootovac\u00ed m\u00e9dium a z\u00e1rove\u0148 m\u00e1te nasazenou vSAN, lehce se m\u016f\u017ee st\u00e1t, \u017ee v \/tmp partition nen\u00ed dostatek m\u00edsta. vSAN toti\u017e pou\u017e\u00edv\u00e1 tento odd\u00edl. \u0158e\u0161en\u00ed pro tuto situaci je jednoduch\u00e9 – reboot serveru. Doporu\u010den\u00edm je pro ESXi 7.0U2 a nov\u011bj\u0161\u00ed nepou\u017e\u00edvat pro tmp a scratch partition USB\/SD disky – v\u00edce podrobnost\u00ed v tomto blogu – https:\/\/blogs.vmware.com\/vsphere\/2021\/09\/esxi-7-boot-media-consideration-vmware-technical-guidance.html<\/a><\/p>\n

Upgrade prob\u00edh\u00e1 v po\u0159ad\u00ed Edge – ESXi – NSX managery. M\u016f\u017ee se st\u00e1t, \u017ee v pr\u016fb\u011bhu upgrade op\u011bt dojde k zapln\u011bn\u00ed \/tmp odd\u00edlu. Ve v\u00fdchoz\u00edm nastaven\u00ed je, \u017ee pokud update n\u011bjak\u00e9 komponenty sel\u017ee, upgrade se zastav\u00ed. Pokud se tak stane, je nutn\u00e9 afektovan\u00fd ESXi op\u011bt restartovat a upgrade op\u011bt spustit. P\u0159edem ale doporu\u010duji na p\u010d\u00edlsu\u0161n\u00e9 kategorii ud\u011blat reset a spustit znovu test.<\/p>\n

Jakmile m\u00e1me usp\u011b\u0161n\u011b dokon\u010den\u00fd pre-check, m\u016f\u017eeme spustit samotn\u00fd upgrade. Jak jsem zmi\u0148oval, prob\u00edh\u00e1 postupn\u011b, v po\u0159ad\u00ed Edge – ESXi – NSX managery.<\/p>\n

Upgrade spou\u0161t\u011bjte v\u017edy z VIP adresy cel\u00e9ho NSX manager clusteru.\u00a0<\/strong><\/p>\n

Upgrade Edge m\u016f\u017ee prob\u00edhat v re\u017eimu serial (v\u00fdchoz\u00ed) nebo paralel. Ve v\u00fdchoz\u00edm re\u017eimu (serial) se upgraduj\u00ed edge postupn\u011b po jednotliv\u00fdch Edge clusterech a v r\u00e1mci clusteru op\u011bt postupn\u011b, tj. pokud m\u00e1te v clusteru min. dv\u011b edge, nem\u011bl by\u00a0 b\u00fdt nijak afektov\u00e1n provoz z a do NSX ani jin\u00e9 slu\u017eby, nap\u0159. LB, VPN apod.<\/p>\n

\"\"<\/a><\/p>\n

N\u00e1sledn\u011b prob\u00edhaj\u00ed upgrade ESXi po jednotliv\u00fdch clusterech.<\/p>\n

\"\"<\/a><\/p>\n

Zde m\u016f\u017eete narazit na n\u011bkolik probl\u00e9m\u016f. Jedn\u00edm z nich je zmi\u0148ovan\u00fd probl\u00e9m s m\u00edstem v \/tmp partition, dal\u0161\u00edm pak m\u016f\u017ee b\u00fdt, \u017ee p\u0159i upgrade nsx komponent z\u016fstane tento task zatuhl\u00fd na 80% „finishing upgrade“ a upgrade tohoto hosta zhavaruje. M\u011b pomohlo se p\u0159ihl\u00e1sit na afektovan\u00fd host, resratovat „hostd“ slu\u017ebu a spustit upgarde znovu. Pak ji\u017e dob\u011bhl upgrade \u00fasp\u011b\u0161n\u011b.<\/p>\n

Jako posledn\u00ed prob\u011bhne upgrade p\u0159\u00edmo NSX manager\u016f.<\/p>\n

\"\"<\/a><\/p>\n

Jakmile dob\u011bhne, trv\u00e1 restart a op\u011btovn\u00e9 nastartov\u00e1n\u00ed GUI, p\u0159ekavpiv\u011b dlouho. Klidn\u011b i n\u011bkolik des\u00edtek minut. Nelekejte se tedy a vy\u010dkejte. Stav upgrade jednotliv\u00fdch NSX manager\u016f a cel\u00e9ho clusteru m\u016f\u017eete zkontrolovat p\u0159es p\u0159\u00edkazovou \u0159\u00e1dku a SSH p\u0159ipojen\u00ed p\u0159\u00edmo na managery a to pomoc\u00ed p\u0159\u00edkazu:<\/p>\n

get upgrade progress-status<\/em><\/p>\n

\"\"<\/a><\/p>\n

Douf\u00e1m, \u017ee V\u00e1m tento \u010dl\u00e1nek pomohl p\u0159ekonat n\u00e1strahy upgrade NSX-T, resp. V\u00e1m p\u0159eji aby jste ho nemuseli \u010d\u00edst a v\u0161echny Va\u0161e upgrady dopadly dob\u0159e.<\/p>","protected":false},"excerpt":{"rendered":"

Spousta z V\u00e1s se ji\u017e setkala s SDN (software define networking) od spole\u010dnosti VMware. Nejprve tu s n\u00e1mi bylo NSX-V, kter\u00e9 pomalu m\u00ed\u0159\u00ed do „propadli\u0161t\u011b…<\/p>\n

Continue ReadingNSX-T upgrade – post\u0159ehy<\/span> <\/i><\/a><\/div>","protected":false},"author":5,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"iawp_total_views":2,"footnotes":""},"categories":[50],"tags":[],"class_list":["post-1271","post","type-post","status-publish","format-standard","hentry","category-nsx","entry"],"_links":{"self":[{"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/posts\/1271","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/comments?post=1271"}],"version-history":[{"count":9,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/posts\/1271\/revisions"}],"predecessor-version":[{"id":1358,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/posts\/1271\/revisions\/1358"}],"wp:attachment":[{"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/media?parent=1271"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/categories?post=1271"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/tags?post=1271"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}