{"id":494,"date":"2018-09-07T12:43:51","date_gmt":"2018-09-07T10:43:51","guid":{"rendered":"https:\/\/virtualguru.cz\/?p=494"},"modified":"2018-10-05T16:10:18","modified_gmt":"2018-10-05T14:10:18","slug":"migrace-distribuovaneho-switche-mezi-vcenter-servery","status":"publish","type":"post","link":"https:\/\/virtualguru.cz\/en\/2018\/09\/07\/migrace-distribuovaneho-switche-mezi-vcenter-servery\/","title":{"rendered":"Migrace distribuovan\u00e9ho switche mezi vCenter servery"},"content":{"rendered":"

Zcela jist\u011b jste ji\u017e narazili na nutnost p\u0159esunu distribuovan\u00e9ho switche mezi vCenter servery. Dle VMware Knowledge Base (https:\/\/kb.vmware.com\/s\/article\/1029498<\/a>) je jedin\u00fdm spr\u00e1vn\u00fdm a podporovan\u00fdm zp\u016fsobem z\u00e1loha konfigurace distribuovan\u00e9ho switche, migrace v\u0161ech portgroup do standartn\u00edho switche, p\u0159esun mezi vCenter a migrace zp\u011bt do naimportovan\u00e9ho distribuovan\u00e9ho switche. Pokud m\u00e1te slo\u017eit\u011bj\u0161\u00ed prost\u0159ed\u00ed s\u00a0v\u011bt\u0161\u00edm po\u010dtem hypervizor\u016f a virtu\u00e1ln\u00edch stroj\u016f je tento postup velmi zdlouhav\u00fd. D\u00e1 se samoz\u0159ejm\u011b \u010d\u00e1ste\u010dn\u011b naskriptovat. My si dnes ale uk\u00e1\u017eeme sice nepodporovan\u00fd, ale funk\u010dn\u00ed jednodu\u0161\u0161\u00ed postup.<\/p>\n

Na za\u010d\u00e1tku mus\u00edme prov\u00e9st export\/z\u00e1lohu konfigurace distribuovan\u00e9ho switche z\u00a0p\u016fvodn\u00edho vCenter \u2013 volba (Distributed switch and all port groups).<\/p>\n

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

N\u00e1sledn\u011b mus\u00edme distribuovan\u00fd switch naimportovat do nov\u00e9ho vCenter, a to v\u010detn\u011b port group.<\/p>\n

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

Pozn. Pokud prov\u00e1d\u00edte import do nov\u00e9ho vCenter, kter\u00e9 je nov\u011bj\u0161\u00ed nap\u0159. z\u00a05.5 rovnou na 6.5, m\u016f\u017ee se V\u00e1m st\u00e1t, \u017ee import konfigurace sice projde, ale distribuovan\u00fd switch se v konfiguraci neobjev\u00ed. Toto je dokumentov\u00e1no ve VMware KB jako zn\u00e1m\u00e1 chyba. Je t\u0159eba si vytvo\u0159it pr\u00e1zdnou instanci vCenter 6.0 a v\u00a0n\u00ed prov\u00e9st import a export distribuovan\u00e9ho switche.<\/em><\/p>\n

V nov\u00e9m vCenter serveru mus\u00edme naimportovat ulo\u017eenou konfiguraci.<\/p>\n

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

Nyn\u00ed jsme tedy ve stavu, kdy m\u00e1me ve star\u00e9m i nov\u00e9m vCenter identick\u00e9 distribuovan\u00e9 switche.<\/p>\n

Na p\u016fvodn\u00ed infrastruktu\u0159e vypneme HA a DRS na clusterech a postupn\u011b za\u010dneme migrovat hypervizory i se spu\u0161t\u011bn\u00fdmi virtu\u00e1ln\u00edmi stroji.<\/p>\n

Postup je jednoduch\u00fd. Vybereme p\u0159\u00edslu\u0161n\u00fd hypervizor a zvol\u00edme \u2013 Disconnect \u2013 Remove from Inventory<\/p>\n

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

V\u00a0nov\u00e9m vCenter pak klasicky p\u0159idat hypervizor \u2013 Add host<\/p>\n

Hypervizor je sice v\u00a0nov\u00e9m vCenter a virtu\u00e1ln\u00ed stroje jsou dostupn\u00e9, ale jeliko\u017e m\u00e1 distribuovan\u00fd switch jin\u00e9 id tak nen\u00ed do tohoto switche p\u0159ipojen. Nyn\u00ed je tedy t\u0159eba prov\u00e9st klasick\u00e9 p\u0159id\u00e1n\u00ed ESXi do distribuovan\u00e9ho switche.<\/p>\n

vCenter \u2013 Networking \u2013 Add and Manage Host<\/p>\n

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

Select host<\/p>\n

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

Manage physical adapters (prob\u011bhne Auto-assign)<\/p>\n

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

Manage vmkernel adapters, pro konfiguraci management port\u016f, vMotion, vSAN, iSCSI, Fault Tolerance apod.<\/p>\n

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

Anal\u00fdza dopadu na iSCSI. Zde se nelekejte i kdy\u017e pou\u017e\u00edv\u00e1te iSCSI storage migrace by m\u011bla prob\u011bhnout bez probl\u00e9mu.<\/p>\n

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

Shrnut\u00ed a potvrzen\u00ed.<\/p>\n

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

Nyn\u00ed m\u00e1me hypervizor v\u00a0nov\u00e9m vCenter a distribuovan\u00e9m switchi se spr\u00e1vn\u011b nastaven\u00fdmi vmkernel porty a uplinky. Zb\u00fdvaj\u00ed tedy virtu\u00e1ln\u00ed stroje samotn\u00e9. Jeliko\u017e m\u00e1 distribuovan\u00fd switch v\u00a0nov\u00e9m vCenter jin\u00e9 id, stejn\u011b tak jej maj\u00ed i v\u0161echny port group. V\u00a0praxi to znamen\u00e1, \u017ee p\u0159esunut\u00e9 virtu\u00e1ln\u00ed stroje sice funguj\u00ed ale maj\u00ed ve sv\u00e9 konfiguraci neexistuj\u00edc\u00ed port group. Je tedy t\u0159eba jim spr\u00e1vnou virtu\u00e1ln\u00ed s\u00ed\u0165 p\u0159id\u011blit.<\/p>\n

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

Zde se nab\u00edz\u00ed n\u011bkolik postup\u016f.<\/p>\n

Bu\u010f op\u011bt p\u0159es jednotliv\u00e9 virtu\u00e1ln\u00ed servery pomoc\u00ed Edit Settings a p\u0159id\u011blen\u00ed p\u0159\u00edslu\u0161n\u00e9 port group. Zde je nev\u00fdhoda, \u017ee mus\u00edte v\u011bd\u011bt v\u00a0kter\u00e9 port group dan\u00fd virtu\u00e1ln\u00ed stroj p\u016fvodn\u011b byl.<\/p>\n

Nebo manu\u00e1ln\u011b p\u0159es vCenter \u2013 Networking \u2013 Add and Manage Host \u2013 Migrate virtual machine networking \u2013 kde se V\u00e1m v\u00a0dal\u0161\u00edm kroku zobraz\u00ed, ve kter\u00e9 port group p\u016fvodn\u011b virtu\u00e1ln\u00ed stroj byl a Vy n\u00e1sledn\u011b vyberete, do kter\u00e9 port group m\u00e1 nov\u011b pat\u0159it.<\/p>\n

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

 <\/p>\n

Posledn\u00ed nebo prvn\u00ed mo\u017enost\u00ed je napsat skript, kter\u00fd bu\u010f z\u00a0p\u016fvodn\u00edho vCenter nebo z\u00a0n\u011bjak\u00e9ho csv dokumentu vyexportuje informace o p\u016fvodn\u00edch port group a n\u00e1sledn\u011b je dan\u00fdm virtu\u00e1ln\u00edm server\u016fm op\u011bt nastav\u00ed.<\/p>\n

P\u0159i pou\u017eit\u00ed skriptu se V\u00e1m m\u016f\u017ee st\u00e1t, \u017ee u n\u011bkter\u00fdch virtu\u00e1ln\u00edch stroj\u016f dojde k\u00a0p\u0159eru\u0161en\u00ed komunikace. Je proto pot\u0159eba zkontrolovat, zda virtu\u00e1ln\u00ed stroje jsou dostupn\u00e9 po s\u00edti. Pokud ne, m\u016f\u017eete pou\u017e\u00edt PowerShell p\u0159\u00edkaz, kter\u00fd p\u0159ipoj\u00ed s\u00ed\u0165ovou kartu u v\u0161ech spu\u0161t\u011bn\u00fdch virtu\u00e1ln\u00edch stroj\u016f.<\/p>\n

Get-VM | ?{$_.PowerState -eq \"PoweredOn\" }| Get-NetworkAdapter | ?{$_.ConnectionState.Connected -eq $false} | Set-NetworkAdapter -Connected $true -confirm:$false<\/pre>\n
Ani tento p\u0159\u00edkaz nemus\u00ed zajistit, \u017ee se v\u0161echny odpojen\u00e9 virtu\u00e1ln\u00ed stroje p\u0159ipoj\u00ed.<\/p>\n
Jako dal\u0161\u00ed bod „troubleshootingu“ se m\u016f\u017eete pod\u00edvat do distribuovan\u00e9ho switche, zda n\u011bjak\u00fd port nen\u00ed ve stavu \u201eLink down.\u201c Pokud ano, mus\u00edte jej znovu povolit. Ob\u010das se stane, \u017ee v\u00a0GUI vCenter je dan\u00fd port st\u00e1le viditeln\u00fd jako odpojen\u00fd. Jestli je toto V\u00e1\u0161 p\u0159\u00edpad, je t\u0159eba na tomto portu povolit monitoring stavu a op\u011bt jej po chvilce zak\u00e1zat. Dojde tak k\u00a0\u201erefresh\u201c stavu portu a ji\u017e je zobrazen spr\u00e1vn\u011b.<\/p>\n
\"\"<\/a><\/p>\n
Dal\u0161\u00edm mo\u017en\u00fdm postupem \u201enastartov\u00e1n\u00ed\u201c portu je jeho povolen\u00ed p\u0159es vlastnosti virtu\u00e1ln\u00edho stroje (Edit Settings \u2013 virtual NIC \u2013 za\u0161krtnout \u201econnected\u201c). Tato volba je funk\u010dn\u00ed pouze v\u00a0HTML5 klientovi ne ve flash verzi.<\/p>\n
Upozorn\u011bn\u00ed na z\u00e1v\u011br: Toto nen\u00ed doporu\u010den\u00fd postup od VMware, nicm\u00e9n\u011b je ov\u011b\u0159en prakticky na n\u011bkolika rozd\u00edln\u00fdch infrastruktur\u00e1ch. Vyzkou\u0161eno pouze s\u00a0klasick\u00fdmi VM nikoliv s\u00a0linkovan\u00fdmi nebo instant klony (VDI).<\/em><\/strong><\/p>","protected":false},"excerpt":{"rendered":"
Zcela jist\u011b jste ji\u017e narazili na nutnost p\u0159esunu distribuovan\u00e9ho switche mezi vCenter servery. Dle VMware Knowledge Base (https:\/\/kb.vmware.com\/s\/article\/1029498) je jedin\u00fdm spr\u00e1vn\u00fdm a podporovan\u00fdm zp\u016fsobem z\u00e1loha…<\/p>\n
Continue ReadingMigrace distribuovan\u00e9ho switche mezi vCenter servery<\/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":13,"footnotes":""},"categories":[3],"tags":[22],"class_list":["post-494","post","type-post","status-publish","format-standard","hentry","category-vsphere","tag-vds","entry"],"_links":{"self":[{"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/posts\/494","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=494"}],"version-history":[{"count":26,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/posts\/494\/revisions"}],"predecessor-version":[{"id":581,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/posts\/494\/revisions\/581"}],"wp:attachment":[{"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/media?parent=494"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/categories?post=494"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/tags?post=494"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}