{"id":1516,"date":"2025-07-19T12:53:03","date_gmt":"2025-07-19T12:53:03","guid":{"rendered":"https:\/\/virtualall.sk\/?p=1516"},"modified":"2026-09-11T14:38:35","modified_gmt":"2026-09-11T14:38:35","slug":"cisco-ucs-c220-m7-ako-management-server-implementacia-monitoringu-a-centralizovaneho-logovania-part-7","status":"publish","type":"post","link":"https:\/\/virtualall.sk\/en\/2025\/07\/cisco-ucs-c220-m7-ako-management-server-implementacia-monitoringu-a-centralizovaneho-logovania-part-7\/","title":{"rendered":"Cisco UCS C220 M7 Monitoring and Logging Part 7"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">V tejto \u010dasti seri\u00e1lu sa zameriavame na implement\u00e1ciu monitoringu ako neoddelite\u013enej s\u00fa\u010dasti spr\u00e1vy infra\u0161trukt\u00fary. Po \u00faspe\u0161nej aktualiz\u00e1cii prostredia prostredn\u00edctvom vSphere Lifecycle Managera prich\u00e1dza na rad zabezpe\u010denie jeho dlhodobej stability a spo\u013eahlivosti. Monitoring m\u00e1 v tomto procese k\u013e\u00fa\u010dov\u00fa \u00falohu \u2013 od fyzickej kontroly hardv\u00e9ru servera Cisco UCS C220 M7, cez sledovanie stavu hyperv\u00edzora ESXi, a\u017e po dostupnos\u0165 a zdravie vCenter servera.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Pre\u010do monitorova\u0165?<\/strong><br>Monitoring nie je len ot\u00e1zkou dobrej spr\u00e1vcovskej praxe, ale v mnoh\u00fdch pr\u00edpadoch aj legislat\u00edvnou po\u017eiadavkou. Z poh\u013eadu noriem kybernetickej bezpe\u010dnosti, ako s\u00fa NIS2, ISO 27001 \u010di z\u00e1kon o kybernetickej bezpe\u010dnosti, je povinnos\u0165ou prev\u00e1dzkovate\u013ea infra\u0161trukt\u00fary zabezpe\u010di\u0165 v\u010dasn\u00fa detekciu incidentov a prevenciu v\u00fdpadkov, ktor\u00e9 by mohli ma\u0165 dopad na d\u00f4vernos\u0165, integritu a dostupnos\u0165 d\u00e1t.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Z poh\u013eadu praxe<\/strong> monitoring umo\u017e\u0148uje r\u00fdchlo odhali\u0165 potenci\u00e1lne chyby e\u0161te predt\u00fdm, ako prerast\u00fa do kritick\u00fdch probl\u00e9mov \u2013 \u010di u\u017e ide o degradovan\u00e9 RAID pole, zvy\u0161uj\u00facu sa teplotu CPU, ne\u00faspe\u0161n\u00e9 z\u00e1lohy, alebo v\u00fdpadok sie\u0165ovej konektivity na \u00farovni ESXi.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Syslog a vzdialen\u00e9 logovanie<\/strong><br>S\u00fa\u010das\u0165ou robustn\u00e9ho monitoringu by malo by\u0165 aj centralizovan\u00e9 logovanie. Konfigur\u00e1ciou <code>syslog<\/code> servera (napr. syslog-ng, rsyslog alebo modern\u00fdch SIEM rie\u0161en\u00ed) dosahujeme to, \u017ee v\u0161etky syst\u00e9mov\u00e9 logy zo serverov, ESXi a vCenter s\u00fa bezpe\u010dne uchov\u00e1van\u00e9 mimo sledovanej infra\u0161trukt\u00fary. To umo\u017e\u0148uje nielen efekt\u00edvnej\u0161iu diagnostiku, ale z\u00e1rove\u0148 nap\u013a\u0148a legislat\u00edvne po\u017eiadavky na audit a archiv\u00e1ciu prev\u00e1dzkov\u00fdch z\u00e1znamov. V pr\u00edpade incidentu tak m\u00e1me k dispoz\u00edcii presn\u00fd \u010dasov\u00fd preh\u013ead udalost\u00ed a syst\u00e9mov\u00fdch stavov.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Z\u00e1verom<\/strong>, monitoring servera nie je len ot\u00e1zkou technol\u00f3gie \u2013 ide o z\u00e1sadn\u00fd bezpe\u010dnostn\u00fd a prev\u00e1dzkov\u00fd prvok, ktor\u00fd zni\u017euje rizik\u00e1, zvy\u0161uje transparentnos\u0165 infra\u0161trukt\u00fary a je d\u00f4le\u017eit\u00fdm pilierom s\u00faladu s platnou legislat\u00edvou.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Nastavenie monitoringu pomocou Checkmk<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">V nadv\u00e4znosti na predch\u00e1dzaj\u00face kroky sme prist\u00fapili k implement\u00e1cii monitoringu, ktor\u00fd sl\u00fa\u017ei ako nevyhnutn\u00fd n\u00e1stroj na zabezpe\u010denie preh\u013eadu o stave celej infra\u0161trukt\u00fary. V tomto pr\u00edpade sme zvolili rie\u0161enie <strong>Checkmk<\/strong>, ktor\u00e9 umo\u017e\u0148uje efekt\u00edvne sledova\u0165 fyzick\u00e9 servery, hyperv\u00edzory ESXi, ako aj samotn\u00fd vCenter server.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Checkmk podporuje <strong>SNMP monitoring<\/strong>, ktor\u00fd je ide\u00e1lny na zber hardv\u00e9rov\u00fdch metr\u00edk zo servera Cisco UCS C220 M7 \u2013 ako napr\u00edklad stav nap\u00e1jania, teplotn\u00e9 senzory, ventil\u00e1tory, RAID pole, stav sie\u0165ov\u00fdch rozhran\u00ed a in\u00e9. Pre t\u00fato funkcionalitu je potrebn\u00e9, aby bol na serveri aktivovan\u00fd a spr\u00e1vne nakonfigurovan\u00fd SNMP daemon.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Na \u00farovni <strong>hyperv\u00edzora ESXi<\/strong> a <strong>vCenter servera<\/strong> vyu\u017e\u00edvame <strong>REST API<\/strong>, ktor\u00e9 Checkmk nat\u00edvne podporuje prostredn\u00edctvom vlastn\u00e9ho pluginu. API komunik\u00e1cia umo\u017e\u0148uje z\u00edska\u0165 \u00fadaje o stave jednotliv\u00fdch virtu\u00e1lnych strojov, dostupnosti slu\u017eieb, kapacite diskov, ako aj inform\u00e1cie o v\u00fdpadkoch a varovaniach v re\u00e1lnom \u010dase.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">V\u00fdhody tohto pr\u00edstupu:<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Agentless monitoring<\/strong> (v pr\u00edpade SNMP a REST API) zabezpe\u010duje jednoduch\u00e9 nasadenie bez potreby in\u0161tal\u00e1cie klientov na sledovan\u00e9 syst\u00e9my.<\/li>\n\n\n\n<li><strong>Automatick\u00e1 detekcia slu\u017eieb<\/strong> \u2013 Checkmk si po pridan\u00ed hosta s\u00e1m naskenuje dostupn\u00e9 slu\u017eby a navrhne, ktor\u00e9 parametre m\u00e1 sledova\u0165.<\/li>\n\n\n\n<li><strong>Grafy, prahov\u00e9 hodnoty a notifik\u00e1cie<\/strong> \u2013 umo\u017e\u0148uj\u00fa nielen sledovanie, ale aj r\u00fdchle varovanie v pr\u00edpade odch\u00fdlok od norm\u00e1lu.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Pr\u00edklad konfigur\u00e1cie:<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Cisco UCS C220 M7<\/strong> \u2013 monitorovan\u00fd cez SNMPv2c (pr\u00edstup pomocou community stringu)<\/li>\n\n\n\n<li><strong>ESXi hosty<\/strong> \u2013 monitorovan\u00e9 cez Checkmk vSphere plugin s pr\u00edstupom cez read-only API pou\u017e\u00edvate\u013ea<\/li>\n\n\n\n<li><strong>vCenter Server Appliance<\/strong> \u2013 cez REST API na \u00farovni slu\u017eby, datab\u00e1zy a syst\u00e9mov\u00fdch metr\u00edk<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">T\u00fdmto monitoringom m\u00e1me zabezpe\u010den\u00fd celistv\u00fd poh\u013ead na cel\u00fd re\u0165azec \u2013 od hardv\u00e9ru cez hyperv\u00edzor a\u017e po riadiacu vrstvu. V pr\u00edpade poruchy alebo v\u00fdpadku dok\u00e1\u017eeme r\u00fdchlo identifikova\u0165, kde vznikol probl\u00e9m a minimalizova\u0165 \u010das nedostupnosti.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Krok 1: Vytvorenie hosta pre CIMC v Checkmk<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">V tomto kroku vytvor\u00edme nov\u00fd host v Checkmk pre fyzick\u00fd server <strong>Cisco UCS C220 M7<\/strong>, konkr\u00e9tne jeho <strong>CIMC rozhranie<\/strong>, ktor\u00e9 bude n\u00e1sledne monitorovan\u00e9 pomocou REST &#8211; API.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Na obr\u00e1zku je zobrazen\u00e1 konfigur\u00e1cia hosta pred pridan\u00edm SNMP pravidiel:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Hostname<\/strong>: <code>crsm1-cimc<\/code> \u2013 n\u00e1zov pod ktor\u00fdm bude server veden\u00fd v Checkmk<\/li>\n\n\n\n<li><strong>IPv4 address<\/strong>: IP adresa CIMC rozhrania servera (napr. <code>10.x.x.40<\/code>)<\/li>\n\n\n\n<li><strong>Checkmk agent \/ API integrations<\/strong>: predvolen\u00e9 nastavenie (API integr\u00e1cie alebo agent)<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Zatia\u013e sme teda <strong>vytvorili len z\u00e1kladn\u00fd objekt hosta<\/strong>, bez priamych REST api parametrov. <\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1009\" height=\"663\" src=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-111.png\" alt=\"Krok 1: Vytvorenie hosta pre CIMC v Checkmk\" class=\"wp-image-1519\" srcset=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-111.png 1009w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-111-300x197.png 300w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-111-768x505.png 768w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-111-18x12.png 18w\" sizes=\"auto, (max-width: 1009px) 100vw, 1009px\" \/><\/figure>\n<\/div>\n\n\n<h3 class=\"wp-block-heading\">Krok 2: Aktiv\u00e1cia pravidla pre UCS Bladecenter monitoring (CIMC API integr\u00e1cia)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Po vytvoren\u00ed hosta je potrebn\u00e9 zmeni\u0165 sp\u00f4sob, ak\u00fdm Checkmk z\u00edskava d\u00e1ta z Cisco UCS servera. Namiesto klasick\u00e9ho Checkmk agenta alebo SNMP sa v tomto pr\u00edpade vyu\u017e\u00edva <strong>\u0161pecializovan\u00fd UCS Bladecenter agent<\/strong>, ktor\u00fd komunikuje cez <strong>UCS Web API<\/strong> (rozhranie CIMC).<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Sekcia: <strong>Rule Properties<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Description \/ Comment<\/strong> \u2013 volite\u013en\u00e9 popisy pravidla (nevyplnen\u00e9)<\/li>\n\n\n\n<li><strong>Rule ID<\/strong> \u2013 unik\u00e1tne ID pravidla, ktor\u00e9 je priraden\u00e9 pri jeho vytvoren\u00ed (napr. <code>657a1268-d4d3-4a54-aa68-d0d6889b99c7<\/code>)<\/li>\n\n\n\n<li><strong>Rule activation<\/strong> \u2013 mus\u00ed by\u0165 za\u0161krtnut\u00e9, aby bolo pravidlo akt\u00edvne<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Sekcia: <strong>UCS Bladecenter<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Username<\/strong> \u2013 meno pou\u017e\u00edvate\u013ea s pr\u00edstupom do CIMC (napr. <code>admin<\/code>)<\/li>\n\n\n\n<li><strong>Password<\/strong> \u2013 heslo k \u00fa\u010dtu (skryt\u00e9)<\/li>\n\n\n\n<li><strong>Disable SSL certificate validation<\/strong> \u2013 t\u00e1to vo\u013eba je za\u0161krtnut\u00e1, \u010do znamen\u00e1, \u017ee Checkmk nebude overova\u0165 platnos\u0165 TLS certifik\u00e1tu CIMC rozhrania. T\u00e1to mo\u017enos\u0165 je u\u017eito\u010dn\u00e1 v pr\u00edpade, \u017ee CIMC pou\u017e\u00edva samopodp\u00edsan\u00fd certifik\u00e1t, \u010do je v intern\u00fdch prostrediach be\u017en\u00e9.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">T\u00fdmto krokom sa zabezpe\u010d\u00ed, \u017ee Checkmk bude z\u00edskava\u0165 hardv\u00e9rov\u00e9 metriky priamo cez rozhranie Cisco UCS \u2013 vr\u00e1tane inform\u00e1ci\u00ed ako:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Stav nap\u00e1jania<\/li>\n\n\n\n<li>Teplotn\u00e9 senzory<\/li>\n\n\n\n<li>Stav RAID po\u013ea<\/li>\n\n\n\n<li>Chyby pam\u00e4t\u00ed a nap\u00e1jania<\/li>\n\n\n\n<li>Invent\u00e1r hardv\u00e9ru<\/li>\n<\/ul>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"890\" height=\"471\" src=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-112.png\" alt=\"Sekcia: UCS Bladecenter\" class=\"wp-image-1520\" srcset=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-112.png 890w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-112-300x159.png 300w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-112-768x406.png 768w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-112-18x10.png 18w\" sizes=\"auto, (max-width: 890px) 100vw, 890px\" \/><\/figure>\n<\/div>\n\n\n<h3 class=\"wp-block-heading\">Krok 3: Kontrola monitorovan\u00fdch slu\u017eieb na serveri Cisco UCS C220 M7<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Po \u00faspe\u0161nej aktiv\u00e1cii UCS Bladecenter agenta a pridelen\u00ed autentifika\u010dn\u00fdch \u00fadajov prich\u00e1dza f\u00e1za, v ktorej overujeme, \u010di sa v\u0161etky hardv\u00e9rov\u00e9 komponenty servera spr\u00e1vne zobrazuj\u00fa v syst\u00e9me Checkmk.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Monitoring be\u017e\u00ed cez rozhranie Cisco CIMC pomocou \u0161peci\u00e1lneho API agenta, ktor\u00fd poskytuje bohat\u00e9 inform\u00e1cie o fyzickom stave zariadenia. Medzi najd\u00f4le\u017eitej\u0161ie monitorovan\u00e9 slu\u017eby patria:<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Hardv\u00e9rov\u00e9 senzory a stavy:<\/h4>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Fan Rack Unit 1 Module X-X-X<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Pr\u00edklad<\/strong>: <code>Fan Rack Unit 1 Module 1-1-1<\/code>, <code>1-3-2<\/code> at\u010f.<\/li>\n\n\n\n<li><strong>Popis<\/strong>: Sledovanie stavu ventil\u00e1torov v jednotliv\u00fdch moduloch. Stav \u201eOperability Status is operable\u201c znamen\u00e1, \u017ee ventil\u00e1tor funguje spr\u00e1vne.<\/li>\n\n\n\n<li><strong>V\u00fdznam<\/strong>: Kritick\u00e9 pre chladenie syst\u00e9mu \u2013 v\u00fdpadok by mohol vies\u0165 k prehrievaniu.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Temperature Rack Unit 1 Motherboard<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Popis<\/strong>: Teplota z\u00e1kladnej dosky \u2013 aktu\u00e1lne 23.0 \u00b0C.<\/li>\n\n\n\n<li><strong>V\u00fdznam<\/strong>: Umo\u017e\u0148uje detekciu prehriatia, ktor\u00e9 m\u00f4\u017ee signalizova\u0165 probl\u00e9m s chladen\u00edm alebo nadmern\u00fdm za\u0165a\u017een\u00edm.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Health Rack unit 1 Storage SAS MRAID controller health<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Popis<\/strong>: Kontrola zdravia RAID radi\u010da \u2013 stav \u201egood\u201c znamen\u00e1, \u017ee RAID funguje spr\u00e1vne.<\/li>\n\n\n\n<li><strong>V\u00fdznam<\/strong>: Kritick\u00fd pre stav diskov\u00e9ho po\u013ea \u2013 napr. po\u0161koden\u00fd disk, rebuild, degrada\u010dn\u00fd m\u00f3d.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>LED Rack Unit 1 X<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Popis<\/strong>: Stav indik\u00e1torov LED na \u0161asi (napr. <code>LED_TEMP_STATUS<\/code>, <code>LED_PSU_STATUS<\/code>, <code>LED_FAN_STATUS<\/code>, <code>LED_FPDI<\/code>).<\/li>\n\n\n\n<li><strong>V\u00fdznam<\/strong>: Stav signaliza\u010dn\u00fdch LED di\u00f3d (zelen\u00e9 \u2013 OK, modr\u00e9 \u2013 OFF), pomoc pri fyzickej identifik\u00e1cii probl\u00e9mu.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Nap\u00e1janie:<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Output Power \/ Voltage \/ Current &#8211; Rack Unit 1 PSU X<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Popis<\/strong>: V\u00fdstupn\u00e9 nap\u00e4tie, pr\u00fad a v\u00fdkon pre ka\u017ed\u00e9 PSU (Power Supply Unit).<\/li>\n\n\n\n<li><strong>Pr\u00edklad<\/strong>: <code>256.00 W<\/code>, <code>19.0 A<\/code>, <code>12.0 V<\/code><\/li>\n\n\n\n<li><strong>V\u00fdznam<\/strong>: Monitorovanie spotreby energie \u2013 m\u00f4\u017ee pom\u00f4c\u0165 odhali\u0165 poruchu nap\u00e1jania alebo nadmern\u00e9 za\u0165a\u017eenie.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Motherboard Power Statistics<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Popis<\/strong>: Agregovan\u00fd odber energie mati\u010dnej dosky (v\u00fdkon, pr\u00fad, nap\u00e4tie).<\/li>\n\n\n\n<li><strong>V\u00fdznam<\/strong>: Pom\u00e1ha sledova\u0165 trendy v spotrebe a identifikova\u0165 v\u00fdkyvy.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Syst\u00e9mov\u00e9 inform\u00e1cie:<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>UCS C-Series Rack Server TopSystem Info<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Popis<\/strong>: Obsahuje \u00fadaje o re\u017eime (napr. \u201estand-alone\u201c), n\u00e1zov servera (<code>C220-crsm1<\/code>), d\u00e1tum a \u010das.<\/li>\n\n\n\n<li><strong>V\u00fdznam<\/strong>: Overenie z\u00e1kladn\u00fdch syst\u00e9mov\u00fdch meta\u00fadajov z UCS.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>PING HOST<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Popis<\/strong>: Dostupnos\u0165 servera \u2013 latencia (napr. 3.90 ms), strata paketov.<\/li>\n\n\n\n<li><strong>V\u00fdznam<\/strong>: Z\u00e1kladn\u00e1 sie\u0165ov\u00e1 dostupnos\u0165 a latencia z poh\u013eadu monitoring servera.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"556\" src=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-113-1024x556.png\" alt=\"PING HOST\" class=\"wp-image-1521\" srcset=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-113-1024x556.png 1024w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-113-300x163.png 300w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-113-768x417.png 768w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-113-18x10.png 18w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-113.png 1371w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n<\/div>\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"240\" src=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-114-1024x240.png\" alt=\"PING HOST (2)\" class=\"wp-image-1522\" srcset=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-114-1024x240.png 1024w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-114-300x70.png 300w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-114-768x180.png 768w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-114-18x4.png 18w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-114.png 1404w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n<\/div>\n\n\n<h3 class=\"wp-block-heading\">Krok 4: Monitorovanie VMware ESXi hosta cez vSphere API<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Spr\u00e1vne nakonfigurovan\u00fd monitoring ESXi hostov je k\u013e\u00fa\u010dov\u00fd pre prev\u00e1dzkov\u00fa spo\u013eahlivos\u0165 cel\u00e9ho virtualiza\u010dn\u00e9ho prostredia. Umo\u017e\u0148uje v\u010das detegova\u0165 v\u00fdpadky hardv\u00e9rov\u00fdch komponentov, pre\u0165a\u017eenie hosta, nedostatok zdrojov \u010di zmeny vo v\u00fdkone virtu\u00e1lnych strojov. Monitoring z\u00e1rove\u0148 sl\u00fa\u017ei ako jeden z d\u00f4le\u017eit\u00fdch n\u00e1strojov pre audit, troubleshooting a optimaliz\u00e1ciu infra\u0161trukt\u00fary.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">V Checkmk sa ESXi servery monitoruj\u00fa pomocou \u0161peci\u00e1lneho agenta <strong>&#8220;VMWare ESX via vSphere&#8221;<\/strong>, ktor\u00fd vyu\u017e\u00edva <strong>vSphere Web API<\/strong> na zber d\u00e1t z hyperv\u00edzora. Tento sp\u00f4sob je agentless, teda nevy\u017eaduje in\u0161tal\u00e1ciu softv\u00e9ru priamo na ESXi.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Na obr\u00e1zku je uk\u00e1zan\u00e9 vytvorenie pravidla pre host <code>crsm2-esxi<\/code>, kde sa definuj\u00fa nasledovn\u00e9 parametre:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>vSphere User name \/ secret<\/strong>: prihlasovacie \u00fadaje k ESXi (odpor\u00fa\u010da sa vytvori\u0165 samostatn\u00e9ho pou\u017e\u00edvate\u013ea s read-only pr\u00e1vami)<\/li>\n\n\n\n<li><strong>SSL certificate checking<\/strong>: vypnut\u00e9, ak ESXi pou\u017e\u00edva self-signed certifik\u00e1t<\/li>\n\n\n\n<li><strong>Retrieve information about<\/strong>:\n<ul class=\"wp-block-list\">\n<li>\u2705 <strong>Host Systems<\/strong> \u2013 stav ESXi hosta, jeho CPU, RAM, load at\u010f.<\/li>\n\n\n\n<li>\u2705 <strong>Performance Counters<\/strong> \u2013 detailn\u00e9 metriky o za\u0165a\u017een\u00ed<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Virtual Machines<\/strong> a <strong>Datastores<\/strong>: volite\u013en\u00e9 pod\u013ea potreby<\/li>\n\n\n\n<li><strong>Do not monitor placeholder VMs<\/strong> \u2013 ignorovanie testovac\u00edch \u0161abl\u00f3n<\/li>\n<\/ul>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"945\" height=\"868\" src=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-115.png\" alt=\"Krok 4: Monitorovanie VMware ESXi hosta cez vSphere API\" class=\"wp-image-1523\" srcset=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-115.png 945w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-115-300x276.png 300w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-115-768x705.png 768w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-115-13x12.png 13w\" sizes=\"auto, (max-width: 945px) 100vw, 945px\" \/><\/figure>\n<\/div>\n\n\n<h3 class=\"wp-block-heading\">Monitorovan\u00e9 slu\u017eby na ESXi hostovi <code>crsm1-esxi<\/code>:<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Check_MK \/ Check_MK Discovery<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Check_MK<\/strong>: v\u00fdstup z vSphere agenta, z\u00e1kladn\u00e9 overenie funkcionality<\/li>\n\n\n\n<li><strong>Discovery<\/strong>: zis\u0165ovanie nov\u00fdch slu\u017eieb \u2013 ni\u010d nech\u00fdba, v\u0161etko je monitorovan\u00e9<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>CPU utilization<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Aktu\u00e1lne za\u0165a\u017eenie CPU (1.14 %) \u2013 umo\u017e\u0148uje sledova\u0165 v\u00fdkonov\u00fd trend a detegova\u0165 pre\u0165a\u017eenie hosta<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Datastore IO SUMMARY \/ Disk IO SUMMARY<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Prenosy na \u00farovni diskov\u00e9ho a d\u00e1tov\u00e9ho \u00falo\u017eiska:\n<ul class=\"wp-block-list\">\n<li>Read\/Write r\u00fdchlos\u0165 (napr. 62.25 kB\/s \u010d\u00edtanie)<\/li>\n\n\n\n<li>Latencia a po\u010det IOPS<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Kritick\u00e9 pre sledovanie v\u00fdkonu storage \u2013 ak\u00e9ko\u013evek spomalenie \u00falo\u017eiska ovplyvn\u00ed v\u0161etky VM<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Hardware Sensors<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Hardv\u00e9rov\u00e9 senzory servera (teplota, ventil\u00e1tory, nap\u00e1janie&#8230;) \u2013 v\u0161etko je \u201enormal state\u201c<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>HostSystem crsm1-esxi<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Overenie stavu ESXi hosta: <code>power state: poweredOn<\/code><\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Interface 3 \/ 5 \/ 6<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Monitorovanie sie\u0165ov\u00fdch rozhran\u00ed (napr. <code>vmnic4<\/code>, <code>vmnic5<\/code>)<\/li>\n\n\n\n<li>R\u00fdchlos\u0165 a traffic (napr. 164 kbit\/s in na <code>vmnic4<\/code>)<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Maintenance Mode<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Inform\u00e1cia, \u010di je host v re\u017eime \u00fadr\u017eby \u2013 aktu\u00e1lne \u201enot in maintenance mode\u201c<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Memory used<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Vyu\u017eitie opera\u010dnej pam\u00e4te (napr. 5.25 GB z 511.72 GB)<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Multipath (2x)<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Stav storage ciest k LUNom \u2013 1 akt\u00edvna, 0 m\u0155tvych \u2013 v\u0161etko v poriadku<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Object count<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Po\u010det VM be\u017eiacich na tomto hoste (napr. 1 VM)<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Overall state<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Celkov\u00fd stav ent\u00edt z vSphere \u2013 aktu\u00e1lne: <code>poweredOn<\/code><\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>PING HOST<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>ICMP dostupnos\u0165 hosta \u2013 latencia (napr. 5.24 ms), bez straty paketov<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">S<strong>ystem Time<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Offset syst\u00e9mov\u00e9ho \u010dasu hosta oproti monitorovaciemu serveru (napr. -3.93 ms)<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Uptime<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>D\u013a\u017eka behu hosta od posledn\u00e9ho \u0161tartu (napr. 1h 44m)<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>VMKernel Swap<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Inform\u00e1cia o vyu\u017e\u00edvan\u00ed SWAPu v r\u00e1mci VMKernel \u2013 aktu\u00e1lne 0.00 KB, \u010do je ide\u00e1lne<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"485\" src=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-116-1024x485.png\" alt=\"VMKernel Swap\" class=\"wp-image-1524\" srcset=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-116-1024x485.png 1024w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-116-300x142.png 300w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-116-768x364.png 768w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-116-18x9.png 18w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-116.png 1502w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n<\/div>\n\n\n<h3 class=\"wp-block-heading\">Krok 5: Monitorovanie vCenter Servera cez vSphere API<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Po nakonfigurovan\u00ed monitoringu fyzick\u00e9ho servera a ESXi hostov pokra\u010dujeme v nastaven\u00ed doh\u013eadu nad samotn\u00fdm <strong>vCenter Serverom<\/strong>, ktor\u00fd zohr\u00e1va k\u013e\u00fa\u010dov\u00fa \u00falohu v celej VMware infra\u0161trukt\u00fare. V\u010faka monitoringu cez vSphere API dok\u00e1\u017eeme sledova\u0165 nielen samotn\u00fd vCenter, ale aj v\u0161etky ESXi hosty a virtu\u00e1lne stroje, ktor\u00e9 s\u00fa do\u0148 pridan\u00e9.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Na obr\u00e1zku vid\u00edme vytv\u00e1ranie pravidla v Checkmk pre vCenter host <code>vcsa0.cloud.tuke.sk<\/code>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>vSphere User name<\/strong>: prihlasovac\u00ed \u00fa\u010det s pr\u00edstupom do vCenter (napr. <code>administrator@vsphere.local<\/code>)<\/li>\n\n\n\n<li><strong>Type of query<\/strong>: <code>Queried host is the vCenter<\/code> \u2013 definuje, \u017ee agent bude z\u00edskava\u0165 \u00fadaje z centr\u00e1lneho riadiaceho bodu<\/li>\n\n\n\n<li><strong>Retrieve information about<\/strong>:\n<ul class=\"wp-block-list\">\n<li>\u2705 <strong>Host Systems<\/strong> \u2013 v\u0161etky ESXi servery pod spr\u00e1vou vCenter<\/li>\n\n\n\n<li>\u2705 <strong>Virtual Machines<\/strong> \u2013 stavy, za\u0165a\u017eenie a dostupnos\u0165 VM<\/li>\n\n\n\n<li>\u2705 <strong>Datastores<\/strong> \u2013 kapacita a v\u00fdkon \u00falo\u017e\u00edsk<\/li>\n\n\n\n<li>\u2705 <strong>Performance Counters<\/strong> \u2013 podrobn\u00e9 v\u00fdkonnostn\u00e9 metriky<\/li>\n\n\n\n<li>\u2705 <strong>License Usage<\/strong> \u2013 vyu\u017eitie licenci\u00ed (u\u017eito\u010dn\u00e9 pre audit)<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>VM power state<\/strong>: zobrazenie stavov VM aj na \u00farovni vCenter<\/li>\n\n\n\n<li><strong>Placeholder VMs<\/strong>: vypnut\u00e9 \u2013 testovacie \u0161abl\u00f3ny sa nesleduj\u00fa<\/li>\n\n\n\n<li><strong>Snapshot summary<\/strong>: volite\u013en\u00e9 zapnutie pre doh\u013ead nad snapshotmi<\/li>\n\n\n\n<li><\/li>\n<\/ul>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"946\" height=\"826\" src=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-117.png\" alt=\"Krok 5: Monitorovanie vCenter Servera cez vSphere API\" class=\"wp-image-1527\" srcset=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-117.png 946w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-117-300x262.png 300w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-117-768x671.png 768w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-117-14x12.png 14w\" sizes=\"auto, (max-width: 946px) 100vw, 946px\" \/><\/figure>\n<\/div>\n\n\n<h3 class=\"wp-block-heading\">Monitorovan\u00e9 slu\u017eby cez vCenter:<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Z\u00e1kladn\u00fd stav a komunik\u00e1cia:<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>Check_MK<\/code> a <code>Check_MK Discovery<\/code> \u2013 funk\u010dnos\u0165 vSphere agenta a zistenie nov\u00fdch slu\u017eieb<\/li>\n\n\n\n<li><code>PING HOST<\/code> \u2013 latencia a dostupnos\u0165 vCenter hosta<\/li>\n\n\n\n<li><code>System Time<\/code> \u2013 odch\u00fdlka syst\u00e9mov\u00e9ho \u010dasu<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>V\u00fdkonov\u00e9 a prev\u00e1dzkov\u00e9 parametre:<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>ESX CPU<\/code> \u2013 aktu\u00e1lne CPU za\u0165a\u017eenie VM be\u017eiacich na ESXi (napr. 0.504 GHz)<\/li>\n\n\n\n<li><code>ESX Memory<\/code> \u2013 pam\u00e4\u0165ov\u00e9 vyu\u017eitie (napr. host: 24 GB, guest: 4.08 GB)<\/li>\n\n\n\n<li><code>Object count<\/code> \u2013 po\u010det VM a ESXi hostov (napr. 2 VM, 2 hosty)<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>\u00dalo\u017eisko a snapshoty:<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>ESX Datastores<\/code> \u2013 kapacita a vyu\u017eitie (napr. 3.36 TB, 95.4 % vo\u013en\u00e9)<\/li>\n\n\n\n<li><code>Filesystem crsm1-local \/ crsm2-local<\/code> \u2013 vyu\u017eitie lok\u00e1lnych filesystemov<\/li>\n\n\n\n<li><code>ESX Snapshots \/ Snapshots Summary<\/code> \u2013 po\u010det snapshotov na hostoch (aktu\u00e1lne 0)<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>ESXi hosty a ich stav:<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>ESX Hostsystem<\/code> \u2013 inform\u00e1cia o tom, na ktorom hoste VM be\u017e\u00ed (napr. crsm2)<\/li>\n\n\n\n<li><code>ESX Name<\/code>, <code>ESX Heartbeat<\/code>, <code>ESX Mounted Devices<\/code> \u2013 identita hosta, heartbeat stav, HA stav<\/li>\n\n\n\n<li><code>HostSystem crsm1<\/code>, <code>HostSystem crsm2<\/code> \u2013 stav zapnutia jednotliv\u00fdch ESXi hostov (poweredOn)<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Virtu\u00e1lne stroje:<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>VM test<\/code>, <code>VM vcsa0.cloud.tuke.sk<\/code> \u2013 stav VM (poweredOn, be\u017e\u00ed na crsm2)<\/li>\n\n\n\n<li><code>ESX Guest Tools<\/code> \u2013 \u010di s\u00fa VMware Tools nain\u0161talovan\u00e9 a funk\u010dn\u00e9<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p class=\"wp-block-paragraph\">Tento monitoring zabezpe\u010duje <strong>kompletn\u00fd preh\u013ead o celom virtualiza\u010dnom prostred\u00ed<\/strong> \u2013 od fyzick\u00fdch hostov cez d\u00e1tov\u00e9 \u00falo\u017eisk\u00e1 a\u017e po jednotliv\u00e9 virtu\u00e1lne stroje. V\u010faka tomu je mo\u017en\u00e9 r\u00fdchlo detegova\u0165 probl\u00e9my, vyhodnocova\u0165 v\u00fdkonnostn\u00e9 trendy a reagova\u0165 na zmeny v infra\u0161trukt\u00fare.<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"666\" src=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-118-1024x666.png\" alt=\"Virtu\u00e1lne stroje:\" class=\"wp-image-1529\" srcset=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-118-1024x666.png 1024w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-118-300x195.png 300w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-118-768x500.png 768w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-118-18x12.png 18w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-118.png 1094w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n<\/div>\n\n\n<h3 class=\"wp-block-heading\">Krok 6: Monitorovanie samotn\u00e9ho vCenter Servera (vCSA)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Popri monitorovan\u00ed ESXi hostov a virtu\u00e1lnych strojov je d\u00f4le\u017eit\u00e9 nezab\u00fada\u0165 ani na samotn\u00fd vCenter Server \u2013 konkr\u00e9tne na jeho opera\u010dn\u00fd stav, slu\u017eby a zdravie. V pr\u00edpade v\u00fdpadku alebo zhor\u0161en\u00e9ho v\u00fdkonu vCSA m\u00f4\u017ee d\u00f4js\u0165 k strate riadenia nad celou virtualiza\u010dnou infra\u0161trukt\u00farou, \u010do m\u00f4\u017ee v\u00fdrazne ovplyvni\u0165 spr\u00e1vu, automatiz\u00e1ciu a dostupnos\u0165 slu\u017eieb.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">V n\u00e1stroji <strong>Checkmk<\/strong> sa na tento \u00fa\u010del pou\u017e\u00edva \u0161peci\u00e1lny agent <strong>&#8220;VMware vCSA Services&#8221;<\/strong>, ktor\u00fd komunikuje priamo cez <strong>vCenter API<\/strong> a umo\u017e\u0148uje sledova\u0165 stav jednotliv\u00fdch syst\u00e9mov\u00fdch slu\u017eieb.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Na obr\u00e1zku je uk\u00e1zan\u00e9 vytvorenie pravidla pre host <code>vcsa0-server.cloud.tuke.sk<\/code>, kde zad\u00e1vame:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Username \/ Password<\/strong>: pr\u00edstup k vCSA (napr. pou\u017e\u00edvate\u013e <code>root<\/code>)<\/li>\n\n\n\n<li><strong>Disable SSL certificate validation<\/strong>: zvy\u010dajne zapnut\u00e9 pri pou\u017eit\u00ed samopodp\u00edsan\u00e9ho certifik\u00e1tu<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Pre\u010do monitorova\u0165 vCenter?<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li> <strong>Prevencia v\u00fdpadkov<\/strong> \u2013 zlyhanie slu\u017eby <code>vpxd<\/code> (hlavn\u00fd demon vSphere) m\u00f4\u017ee znemo\u017eni\u0165 spr\u00e1vu celej infra\u0161trukt\u00fary<\/li>\n\n\n\n<li> <strong>Zdravie slu\u017eieb<\/strong> \u2013 vCSA be\u017e\u00ed na viacer\u00fdch mikroslu\u017eb\u00e1ch (telemetria, SSO, logovanie, backup), ktor\u00e9 m\u00f4\u017eu zlyha\u0165 samostatne<\/li>\n\n\n\n<li> <strong>V\u00fdkon<\/strong> \u2013 monitorovanie pre\u0165a\u017eenia slu\u017eby, pomal\u00fdch odoziev alebo zvy\u0161uj\u00facej sa latencie API<\/li>\n\n\n\n<li> <strong>Audit<\/strong> \u2013 preh\u013ead o tom, \u010di s\u00fa v\u0161etky slu\u017eby funk\u010dn\u00e9 (vr\u00e1tane z\u00e1lohovania, pr\u00edstupov at\u010f.)<\/li>\n<\/ul>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"466\" src=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-119-1024x466.png\" alt=\"Pre\u010do monitorova\u0165 vCenter?\" class=\"wp-image-1531\" srcset=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-119-1024x466.png 1024w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-119-300x137.png 300w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-119-768x349.png 768w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-119-18x8.png 18w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-119.png 1268w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n<\/div>\n\n\n<h3 class=\"wp-block-heading\">V\u00fdsledok monitoringu vCSA<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Pomocou \u0161peci\u00e1lneho vCSA agenta v Checkmk z\u00edskavame <strong>preh\u013ead o v\u0161etk\u00fdch syst\u00e9mov\u00fdch slu\u017eb\u00e1ch be\u017eiacich na vCenter Server Appliance<\/strong>. Agent vyu\u017e\u00edva vCenter API a pravidelne kontroluje:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>stav slu\u017eby<\/strong> (\u010di bola spusten\u00e1 automaticky a \u010di aktu\u00e1lne be\u017e\u00ed),<\/li>\n\n\n\n<li><strong>zdravie slu\u017eby<\/strong> (HEALTHY vs. DEGRADED),<\/li>\n\n\n\n<li>a dostupnos\u0165 samotn\u00e9ho servera cez ICMP (ping).<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Zobrazovan\u00e9 s\u00fa v\u0161etky k\u013e\u00fa\u010dov\u00e9 slu\u017eby, ako napr\u00edklad <code>analytics<\/code>, <code>lookupsvc<\/code>, <code>content-library<\/code>, <code>certificateauthority<\/code>, <code>hvc<\/code>, <code>netdumper<\/code>, <code>imagebuilder<\/code> a \u010fal\u0161ie. V\u0161etky tieto komponenty tvoria z\u00e1kladn\u00fa funk\u010dnos\u0165 vCenter a ich v\u00fdpadok m\u00f4\u017ee vies\u0165 k zn\u00ed\u017eenej dostupnosti, strate funk\u010dnosti alebo probl\u00e9mom pri spr\u00e1ve cel\u00e9ho prostredia.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Tento typ monitoringu je d\u00f4le\u017eit\u00fd najm\u00e4 pri zabezpe\u010dovan\u00ed vysokodostupn\u00fdch rie\u0161en\u00ed, kde je v\u010dasn\u00e1 detekcia probl\u00e9mov v riadiacej vrstve rozhoduj\u00faca pre prev\u00e1dzkov\u00fa kontinuitu. Slu\u017eby s\u00fa monitorovan\u00e9 samostatne a v pr\u00edpade v\u00fdpadku jednej z nich je mo\u017en\u00e9 okam\u017eite spusti\u0165 eskal\u00e1ciu \u010di servisn\u00fd z\u00e1sah.<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"627\" src=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-120-1024x627.png\" alt=\"V\u00fdsledok monitoringu vCSA\" class=\"wp-image-1533\" srcset=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-120-1024x627.png 1024w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-120-300x184.png 300w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-120-768x470.png 768w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-120-18x12.png 18w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-120.png 1194w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n<\/div>\n\n\n<h3 class=\"wp-block-heading\">Krok 7: Zabezpe\u010denie centralizovan\u00e9ho logovania pomocou Syslog<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Spo\u013eahliv\u00fd monitoring infra\u0161trukt\u00fary nie je \u00fapln\u00fd bez d\u00f4kladne nastaven\u00e9ho <strong>logovania<\/strong>. V r\u00e1mci enterprise prostred\u00ed je \u0161tandardom vyu\u017e\u00edva\u0165 <strong>Syslog<\/strong> ako protokol pre zber syst\u00e9mov\u00fdch a bezpe\u010dnostn\u00fdch logov zo v\u0161etk\u00fdch zariaden\u00ed a syst\u00e9mov. Cie\u013eom je centralizova\u0165 z\u00e1znamy o udalostiach a poruch\u00e1ch pre potreby auditu, forenznej anal\u00fdzy a okam\u017eitej reakcie na incidenty.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">V\u0161etky vrstvy infra\u0161trukt\u00fary by mali zasiela\u0165 logy na <strong>centr\u00e1lne logovacie servery<\/strong>, ide\u00e1lne aspo\u0148 <strong>dva<\/strong> \u2013 kv\u00f4li redundancii a zabezpe\u010deniu dostupnosti v pr\u00edpade v\u00fdpadku jedn\u00e9ho z nich.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h4 class=\"wp-block-heading\">Konfigur\u00e1cia Syslog na Cisco UCS C220 M7 (CIMC)<\/h4>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"511\" src=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-121-1024x511.png\" alt=\"Konfigur\u00e1cia Syslog na Cisco UCS C220 M7 (CIMC)\" class=\"wp-image-1535\" srcset=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-121-1024x511.png 1024w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-121-300x150.png 300w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-121-768x383.png 768w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-121-1536x766.png 1536w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-121-18x9.png 18w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-121.png 1676w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n<\/div>\n\n\n<p class=\"wp-block-paragraph\">Na prilo\u017eenom obr\u00e1zku vid\u00edme nastavenie <strong>Cisco Integrated Management Controller (CIMC)<\/strong>, kde sa definuje:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Minimum Severity to Report<\/strong>: <code>Debug<\/code> \u2013 odosielaj\u00fa sa v\u0161etky spr\u00e1vy vr\u00e1tane detailn\u00fdch (mo\u017eno nesk\u00f4r zmeni\u0165 na <code>Info<\/code> alebo <code>Warning<\/code>)<\/li>\n\n\n\n<li><strong>Remote Logging<\/strong>: dva zadefinovan\u00e9 syslog servery (napr. <code>147.x.x.1<\/code> a <code>147.x.x.2<\/code>)<\/li>\n\n\n\n<li><strong>Protokol<\/strong>: <code>UDP<\/code>, port <code>514<\/code> (\u0161tandardn\u00fd pre syslog)<\/li>\n\n\n\n<li><strong>Secure Syslog<\/strong>: zatia\u013e vypnut\u00fd, ale odpor\u00fa\u010dan\u00fd v produk\u010dn\u00fdch a citliv\u00fdch prostrediach<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Toto nastavenie zabezpe\u010duje, \u017ee CIMC bude odosiela\u0165 v\u0161etky udalosti (poruchy, senzory, nap\u00e1janie, re\u0161tarty) na extern\u00e9 logovacie servery, \u010d\u00edm sa eliminuje z\u00e1vislos\u0165 na samotnom zariaden\u00ed pri forenznej anal\u00fdze.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Konfigur\u00e1cia Syslog pre vCenter Server (vCSA)<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Okrem CIMC je nevyhnutn\u00e9, aby logy odosielal aj samotn\u00fd <strong>vCenter Server Appliance (vCSA)<\/strong>. Ten sl\u00fa\u017ei ako riadiaca jednotka celej VMware infra\u0161trukt\u00fary a uchov\u00e1va mno\u017estvo kritick\u00fdch udalost\u00ed \u2013 od spr\u00e1vy hostov, cez zmeny v konfigur\u00e1ci\u00e1ch a\u017e po alarmy, SSO a auditn\u00e9 z\u00e1znamy.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Na obr\u00e1zku je zobrazen\u00e9 nastavenie forwarding konfigur\u00e1cie v \u010dasti <strong>vCenter Server Management &gt; Syslog<\/strong>, kde s\u00fa zadefinovan\u00e9:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Dva vzdialen\u00e9 Syslog servery<\/strong>:\n<ul class=\"wp-block-list\">\n<li>Jeden cez <strong>UDP (514)<\/strong> \u2013 stav pripojenia: \u201eUnknown\u201c<\/li>\n\n\n\n<li>Druh\u00fd cez <strong>TCP (514)<\/strong> \u2013 stav pripojenia: \u201eReachable\u201c<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Pou\u017eit\u00e9 s\u00fa oba protokoly \u2013 <strong>UDP<\/strong> je r\u00fdchly, no nespo\u013eahliv\u00fd; <strong>TCP<\/strong> je pomal\u0161\u00ed, ale zaru\u010duje doru\u010denie (vhodn\u00e9 pre kritick\u00e9 logy)<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">T\u00fdmto nastaven\u00edm zabezpe\u010d\u00edme, \u017ee vCSA bude v re\u00e1lnom \u010dase odosiela\u0165 logy o svojom stave, slu\u017eb\u00e1ch a syst\u00e9mov\u00fdch udalostiach na centr\u00e1lny logovac\u00ed syst\u00e9m. V prostred\u00ed, kde prebieha monitoring a audit, je to z\u00e1sadn\u00e9 pre forenzn\u00e9 \u00fa\u010dely, detekciu \u00fatokov a sp\u00e4tn\u00fa anal\u00fdzu zmien.<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"309\" src=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-122-1024x309.png\" alt=\"Konfigur\u00e1cia Syslog pre vCenter Server (vCSA)\" class=\"wp-image-1537\" srcset=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-122-1024x309.png 1024w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-122-300x91.png 300w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-122-768x232.png 768w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-122-1536x464.png 1536w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-122-18x5.png 18w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-122.png 1857w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n<\/div>\n\n\n<h4 class=\"wp-block-heading\">Konfigur\u00e1cia Syslog pre ESXi hosty<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Na to, aby bola infra\u0161trukt\u00fara kompletne pokryt\u00e1 logovan\u00edm, je nevyhnutn\u00e9 nakonfigurova\u0165 aj <strong>odosielanie logov z jednotliv\u00fdch ESXi hostov<\/strong>. Ka\u017ed\u00fd host obsahuje mno\u017estvo d\u00f4le\u017eit\u00fdch syst\u00e9mov\u00fdch inform\u00e1ci\u00ed: chyby diskov\u00fdch pol\u00ed, v\u00fdpadky siete, stavy VMkernelu, konfigur\u00e1cie siete a \u010fal\u0161ie udalosti, ktor\u00e9 musia by\u0165 uchov\u00e1van\u00e9 mimo samotn\u00e9ho hosta pre \u00fa\u010dely auditu a forenznej anal\u00fdzy.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Na prilo\u017eenom obr\u00e1zku vid\u00edme nastavenie v \u010dasti <strong>Advanced System Settings<\/strong> pre host <code>hp4.cloud.tuke.sk<\/code>, konkr\u00e9tne k\u013e\u00fa\u010dov\u00e9 parametre:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong><code>Syslog.global.logHost<\/code><\/strong><br>Definuje vzdialen\u00e9 Syslog servery \u2013 v tomto pr\u00edpade dva: <\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code>udp:\/\/&lt;ip_adresa_1>:514, tcp:\/\/&lt;ip_adresa_2>:514<\/code><\/pre>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"880\" height=\"811\" src=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-123.png\" alt=\"Konfigur\u00e1cia Syslog pre ESXi hosty\" class=\"wp-image-1542\" srcset=\"https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-123.png 880w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-123-300x276.png 300w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-123-768x708.png 768w, https:\/\/virtualall.sk\/wp-content\/uploads\/2025\/07\/obrazek-123-13x12.png 13w\" sizes=\"auto, (max-width: 880px) 100vw, 880px\" \/><\/figure>\n<\/div>\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Cel\u00e1 s\u00e9ria: Cisco UCS C220 M7<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li><a href=\"https:\/\/virtualall.sk\/2025\/07\/cisco-ucs-c220-m7-ako-zaklad-pre-bezpecny-vmware-klaster-pre-management-a-zalohovanie\/\">Cisco UCS C220 M7 VMware klaster<\/a><\/li>\n\n\n<li><a href=\"https:\/\/virtualall.sk\/2025\/07\/cisco-ucs-c220-m7-ako-zaklad-pre-bezpecny-vmware-klaster-pre-management-a-zalohovanie-part-2\/\">Cisco UCS C220 M7 VMware klaster Part 2<\/a><\/li>\n\n\n<li><a href=\"https:\/\/virtualall.sk\/2025\/07\/cisco-ucs-c220-m7-ako-management-server-sietova-architektura-pre-vmware-klaster-part-3\/\">Cisco UCS C220 M7 sie\u0165ov\u00e1 architekt\u00fara Part 3<\/a><\/li>\n\n\n<li><a href=\"https:\/\/virtualall.sk\/2025\/07\/cisco-ucs-c220-m7-ako-management-server-instalacia-vmware-esxi-a-vcenter-pre-spravu-klastra-part-4\/\">Cisco UCS C220 M7 ESXi a vCenter Part 4<\/a><\/li>\n\n\n<li><a href=\"https:\/\/virtualall.sk\/2025\/07\/cisco-ucs-c220-m7-ako-management-server-konfiguracia-vmware-siete-a-vmotion-part-5\/\">Cisco UCS C220 M7 VMware sie\u0165 a vMotion Part 5<\/a><\/li>\n\n\n<li><a href=\"https:\/\/virtualall.sk\/2025\/07\/cisco-ucs-c220-m7-ako-management-server-aktualizacia-esxi-pomocou-vsphere-lifecycle-manager-part-6\/\">Cisco UCS C220 M7 vSphere Lifecycle Manager Part 6<\/a><\/li>\n\n\n<li><strong>Cisco UCS C220 M7 monitoring a logovanie Part 7<\/strong> &mdash; tento \u010dl\u00e1nok<\/li>\n\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>V tejto \u010dasti sme sa zamerali na nastavenie monitoringu servera a virtualiza\u010dn\u00e9ho prostredia. Monitoring je k\u013e\u00fa\u010dov\u00fd nielen z h\u013eadiska prevencie v\u00fdpadkov a v\u010dasnej detekcie por\u00fach, ale aj pre splnenie legislat\u00edvnych po\u017eiadaviek na prev\u00e1dzkov\u00fa bezpe\u010dnos\u0165 a auditovate\u013enos\u0165. Monitorovanie sme realizovali prostredn\u00edctvom protokolov SNMP a REST API, v\u010faka \u010domu m\u00e1me preh\u013ead o stave fyzick\u00e9ho hardv\u00e9ru, ako aj o v\u00fdkone a dostupnosti ESXi hostov.<\/p>\n","protected":false},"author":1,"featured_media":1525,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[68,4],"tags":[256,236],"class_list":["post-1516","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-checkmk","category-vsphere","tag-cisco-server-vmware","tag-cisco-ucs-c220-m7"],"_links":{"self":[{"href":"https:\/\/virtualall.sk\/en\/wp-json\/wp\/v2\/posts\/1516","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/virtualall.sk\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/virtualall.sk\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/virtualall.sk\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/virtualall.sk\/en\/wp-json\/wp\/v2\/comments?post=1516"}],"version-history":[{"count":15,"href":"https:\/\/virtualall.sk\/en\/wp-json\/wp\/v2\/posts\/1516\/revisions"}],"predecessor-version":[{"id":2354,"href":"https:\/\/virtualall.sk\/en\/wp-json\/wp\/v2\/posts\/1516\/revisions\/2354"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/virtualall.sk\/en\/wp-json\/wp\/v2\/media\/1525"}],"wp:attachment":[{"href":"https:\/\/virtualall.sk\/en\/wp-json\/wp\/v2\/media?parent=1516"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/virtualall.sk\/en\/wp-json\/wp\/v2\/categories?post=1516"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/virtualall.sk\/en\/wp-json\/wp\/v2\/tags?post=1516"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}