Daidaitaccen rufewar VMWare ESXi hypervisor lokacin da matakin cajin baturi na APC UPS yana da mahimmanci.

Akwai labarai da yawa a can game da yadda ake saita Ɗabi'ar Kasuwancin PowerChute da yadda ake haɗawa da VMWare daga PowerShell, amma ko ta yaya ban sami duk waɗannan a wuri ɗaya ba, tare da bayanin madaidaitan maki. Amma akwai su.

1. Gabatarwa

Duk da cewa muna da alaƙa da makamashi, matsalolin wutar lantarki a wasu lokuta suna tasowa. Wannan shine inda UPS ke shiga cikin wasa, amma batir ɗin sa, alas, ba su daɗe. Me za a yi? Kashe!

Duk da yake duk sabobin na zahiri ne, abubuwa suna tafiya da kyau, Buga Kasuwancin PowerChute ya taimake mu. Kyauta, don sabobin 5, wanda ya isa sosai. An shigar da wakili, uwar garken da na'ura wasan bidiyo akan na'ura ɗaya. Yayin da ƙarshen ya gabato, wakilin kawai ya aiwatar da fayil ɗin umarni wanda ya aika shutdown.exe/s /m zuwa sabar makwabta, sannan ya rufe OS. Kowa yana raye.
Sa'an nan kuma lokaci ya yi don injiniyoyi.

2. Fage da tunani

To me muke da shi? Babu komai - uwar garken jiki guda ɗaya tare da Windows Server 2008 R2 da hypervisor ɗaya tare da injunan kama-da-wane da yawa, gami da Windows Server 2019, Windows Server 2003, da CentOS. Kuma wani UPS - APC Smart-UPS.

Mun ji labarin NUT, amma ba mu kai ga yin nazarinsa ba tukuna; kawai mun yi amfani da abin da ke hannunmu, wato Buga Kasuwancin PowerChute.

Mai hypervisor na iya rufe na'urorin sa da kansa; abin da ya rage shi ne ya gaya masa cewa lokaci ya yi. Akwai irin wannan abu mai amfani VMWare.PowerCLI, wannan ƙari ne don Windows Powershell wanda ke ba ku damar haɗawa da hypervisor kuma ku gaya masa duk abin da kuke buƙata. Hakanan akwai labarai da yawa a can game da saitunan PowerCLI.

3. Tsari

An haɗa UPS ta jiki zuwa tashar com na uwar garken 2008, an yi sa'a a can. Ko da yake wannan ba shi da mahimmanci - yana yiwuwa a haɗa ta hanyar mai canzawa (MOXA) zuwa kowane uwar garken Windows mai kama-da-wane. Bugu da ari, ana yin duk ayyuka akan injin da aka haɗa UPS zuwa gare ta - Windows Server 2008, sai dai in an faɗi akasin haka. An shigar da wakilin Kasuwancin PowerChute akan sa. Anan shine mahimmin dabara na farko: dole ne a ƙaddamar da sabis ɗin wakili ba daga tsarin ba, amma daga mai amfani, in ba haka ba wakili ba zai iya aiwatar da fayil ɗin cmd ba.

Na gaba mun shigar da .Net Framework 4.7. Ana buƙatar sake yi anan, ko da tsarin bai fito fili ya nemi shi bayan shigarwa ba, in ba haka ba ba zai ci gaba ba. Bayan haka, sabuntawa na iya zuwa har yanzu, wanda kuma yana buƙatar shigarwa.

Bayan haka mun shigar da PowerShell 5.1. Hakanan yana buƙatar sake kunnawa, ko da bai tambaya ba.
Na gaba, shigar da PowerCLI 11.5. Wani sigar kwanan nan, don haka buƙatun da suka gabata. Kuna iya yin ta ta Intanet, akwai labarai da yawa game da wannan, amma mun riga mun zazzage shi, don haka kawai mun kwafi duk fayilolin zuwa babban fayil ɗin Modules.

An duba:

Get-Module -ListAvailable

Ok, mun ga mun shigar:

Import-Module VMWare.PowerCLI

Ee, ba shakka an ƙaddamar da na'urar wasan bidiyo ta Powershell azaman Mai Gudanarwa.

Saitunan Powershell.

• Bada izinin aiwatar da kowane rubutun:

Set-ExecutionPolicy Unrestricted

• Ko kuma za ku iya barin takaddun takaddun rubutun kawai a yi watsi da su:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned 

• Bada PowerCLI don haɗawa zuwa sabobin tare da takaddun shaida mara inganci ( ƙarewa )

Set-PowerCLIConfiguration -InvalidCertificateAction ignore -confirm:$false

• Matse fitar da sakon PowerCLI game da shiga shirin musayar gwaninta, in ba haka ba za a sami bayanan da ba dole ba a cikin log ɗin:

Set-PowerCLIConfiguration -Scope User -ParticipateInCEIP $false

• Ajiye bayanan shaidar mai amfani don shiga cikin mai masaukin VMWare don kar a nuna su a cikin rubutun:

New-VICredentialStoreItem -Host address -User user -Password 'password'

Dubawa zai nuna wanda muka ajiye:

Get-VICredentialStoreItem

Hakanan zaka iya bincika haɗin: Adireshin Haɗa-VIServer.

Rubutun kanta, misali: haɗi, kashewa, cire haɗin kawai idan akwai zaɓuɓɓuka masu zuwa:

    Connect-VIserver -Server $vmhost 
    Stop-VMHost $vmhost -force -Confirm:$false 
    Disconnect-VIserver $vmhost -Confirm:$false

4. Default.cmd

Fayil guda daya da wakilin APC ya kaddamar. Yana cikin "C: Fayilolin Shirin [(x86)]APCPowerChute Business Editionagentcmdfiles", da kuma ciki:

"C: Windowssystem32WindowsPowerShellv1.0powershell.exe" -File "C:...rushe_hosts.ps1"
Da alama an saita komai kuma an bincika, har ma mun ƙaddamar da cmd - yana aiki daidai, yana kashe shi.

Muna gudanar da gwajin fayil ɗin umarni daga na'urar bidiyo ta APC (akwai maɓallin Gwaji a can) - ba ya aiki.

A nan shi ne, wannan lokacin mai ban tsoro lokacin da duk aikin da aka yi bai haifar da komai ba.

5. Katar

Muna duban mai sarrafa aiki, muna ganin filasha cmd, filasha wutar lantarki. Bari mu bincika a hankali - cmd * 32 kuma, saboda haka, powershell * 32. Mun fahimci haka Sabis ɗin wakilin APC 32-bit ne, wanda ke nufin yana gudanar da na'ura mai kwakwalwa.

Mun ƙaddamar da powershell x86 a matsayin mai gudanarwa, da kuma shigar da kuma saita PowerCLI daga mataki na 3 kuma.

To, bari mu canza layin kira powershell:

"C:Windows<b>SysWOW64</b>WindowsPowerShellv1.0powershell.exe…

6. Ƙarshen farin ciki!

source: www.habr.com