{"id":1701,"date":"2025-11-19T10:00:08","date_gmt":"2025-11-19T10:00:08","guid":{"rendered":"https:\/\/virtualall.sk\/?p=1701"},"modified":"2026-05-08T07:31:27","modified_gmt":"2026-05-08T07:31:27","slug":"cisco-nexus-vpc-klaster-pre-proxmox","status":"publish","type":"post","link":"https:\/\/virtualall.sk\/en\/2025\/11\/cisco-nexus-vpc-klaster-pre-proxmox\/","title":{"rendered":"Cisco Nexus VPC Cluster for PROXMOX – Complete Guide"},"content":{"rendered":"\n

V prostrediach, kde je dostupnos\u0165 kritick\u00fdm parametrom a ka\u017ed\u00e1 sekunda v\u00fdpadku m\u00f4\u017ee znamena\u0165 v\u00fdrazn\u00e9 prev\u00e1dzkov\u00e9 straty, je nevyhnutn\u00e9 navrhova\u0165 sie\u0165ov\u00fa infra\u0161trukt\u00faru s d\u00f4razom na redundanciu a \u0161k\u00e1lovate\u013enos\u0165. Cisco Nexus platforma pon\u00faka robustn\u00fd n\u00e1stroj pr\u00e1ve na tento typ rie\u0161enia \u2013 Virtual Port-Channel (vPC)<\/strong>. <\/p>\n\n\n\n

Port-Channel<\/strong> (\u010dasto naz\u00fdvan\u00fd aj EtherChannel alebo LAG \u2013 Link Aggregation Group) je mechanizmus, ktor\u00fd umo\u017e\u0148uje zv\u00e4zova\u0165 viac fyzick\u00fdch ethernetov\u00fdch liniek do jedn\u00e9ho logick\u00e9ho linku. Prep\u00edna\u010d pritom pracuje s t\u00fdmto zv\u00e4zkom ako s jedn\u00fdm linkom aj z poh\u013eadu L2 smerovania r\u00e1mcov.<\/p>\n\n\n\n

V\u00fdhody pou\u017eitia port-channelu<\/strong><\/h3>\n\n\n\n
    \n
  • Vy\u0161\u0161ia priepustnos\u0165<\/strong>: kombin\u00e1ciou viacer\u00fdch liniek (napr. 2\u00d710G = 20G; 4\u00d710G = 40G) z\u00edskate vy\u0161\u0161iu kapacitu bez potreby drah\u0161\u00edch uplinkov\u00fdch modulov.<\/li>\n\n\n\n
  • Redundancia<\/strong>: pri v\u00fdpadku jednej linky (optiky \u010di transceiveru) port-channel ost\u00e1va akt\u00edvny, \u010do eliminuje v\u00fdpadky pri jednovrstvov\u00fdch spojoch.<\/li>\n\n\n\n
  • Vyva\u017eovanie z\u00e1\u0165a\u017ee (load-balancing)<\/strong>: prem\u00e1vka sa rozklad\u00e1 pod\u013ea hash algoritmov (MAC, IP, L4 porty), \u010do zvy\u0161uje efektivitu.<\/li>\n\n\n\n
  • Jednoduch\u0161ia topol\u00f3gia<\/strong>: z poh\u013eadu konfigur\u00e1cie je to st\u00e1le jeden logick\u00fd interface, \u010do u\u013eah\u010duje spr\u00e1vu ACL, QoS \u010di monitoringu.<\/li>\n<\/ul>\n\n\n\n

    Bez port-channelu by bolo potrebn\u00e9 rie\u0161i\u0165 STP blokovanie portov a komplik\u00e1cie pri redundancii. Pr\u00e1ve preto sa stal \u0161tandardn\u00fdm stavebn\u00fdm prvkom modern\u00fdch d\u00e1tov\u00fdch centier.<\/p>\n\n\n\n

    \u010co je to Cisco VPC (Virtual Port-Channel)<\/strong><\/h2>\n\n\n\n

    K\u00fdm port-channel funguje medzi dvoma zariadeniami, vPC pos\u00fava cel\u00fa koncepciu o jeden z\u00e1sadn\u00fd krok vy\u0161\u0161ie<\/strong>. Z\u00e1kazn\u00edk toti\u017e \u010dasto nechce by\u0165 viazan\u00fd jedn\u00fdm fyzick\u00fdm switchom \u2014 potrebuje redundantn\u00fa dvojicu, ktor\u00e1 sa spr\u00e1va ako jeden logick\u00fd celok. Na to sl\u00fa\u017ei vPC.<\/p>\n\n\n\n

    Defin\u00edcia vPC<\/strong><\/h3>\n\n\n\n

    Cisco vPC umo\u017e\u0148uje pripoji\u0165 jeden alebo viac downstream zariaden\u00ed (servery, switche, hyperv\u00edzory) pomocou port-channelu, ktor\u00fd je rozdelen\u00fd medzi dve nez\u00e1visl\u00e9 Nexus jednotky.<\/strong> Downstream zariadenie v\u0161ak tieto dva switche vid\u00ed ako jeden logick\u00fd switch.<\/p>\n\n\n\n

    K\u013e\u00fa\u010dov\u00e9 pr\u00ednosy vPC<\/strong><\/h3>\n\n\n\n
      \n
    • Redundancia bez STP blokovania<\/strong>
      Oba switche v p\u00e1re s\u00fa akt\u00edvne naraz. \u017diadny port nie je blokovan\u00fd STP, \u010d\u00edm sa eliminuje jeden z naj\u010dastej\u0161\u00edch \u201cbottleneckov\u201d.<\/li>\n\n\n\n
    • Nulov\u00e9 alebo minim\u00e1lne v\u00fdpadky pri poruche jedn\u00e9ho zo switchov<\/strong>
      Linky ost\u00e1vaj\u00fa akt\u00edvne, traffic pokra\u010duje cez druh\u00fd \u010dlen vPC.<\/li>\n\n\n\n
    • Mo\u017enos\u0165 akt\u00edvneho LACP port-channelu cez dva fyzick\u00e9 switche<\/strong>
      Server alebo in\u00fd switch dostane v\u00e4\u010d\u0161iu priepustnos\u0165 s redundantnou architekt\u00farou.<\/li>\n\n\n\n
    • Stabiln\u00e1 datacentrov\u00e1 architekt\u00fara<\/strong>
      vPC je z\u00e1kladom pre spine-leaf topol\u00f3gie a modern\u00e9 architekt\u00fary bez STP.<\/li>\n<\/ul>\n\n\n\n

      \u010co t\u00fdm z\u00edskate v praxi<\/strong><\/h3>\n\n\n\n
        \n
      • Servery m\u00f4\u017eu ma\u0165 dva (alebo viac) uplinkov, ka\u017ed\u00fd do in\u00e9ho switcha \u2192 no tvoria jeden LACP port-channel.<\/li>\n\n\n\n
      • Nedoch\u00e1dza k v\u00fdpadkom pri poruche jedn\u00e9ho switcha.<\/li>\n\n\n\n
      • Minimalizujete slu\u010dky aj z\u00e1vislos\u0165 na STP.<\/li>\n\n\n\n
      • Z\u00edskate horizont\u00e1lne \u0161k\u00e1lovate\u013en\u00fa architekt\u00faru vhodn\u00fa pre hyperv\u00edzorov\u00e9 farmy, storage syst\u00e9my \u010di HPC.<\/li>\n<\/ul>\n\n\n\n

        vPC klaster na dvojici Cisco Nexus (10.1.1.35 a 10.1.1.36)<\/strong><\/h2>\n\n\n\n

        V nadv\u00e4znosti na teoretick\u00fd \u00favod sa v \u010fal\u0161ej \u010dasti \u010dl\u00e1nku zameriame na praktick\u00fa konfigur\u00e1ciu vPC v prostred\u00ed dvoch Cisco Nexus prep\u00edna\u010dov. Postupne si vysvetl\u00edme jednotliv\u00e9 komponenty vPC architekt\u00fary a uk\u00e1\u017eeme, ako spr\u00e1vne navrhn\u00fa\u0165 aj nakonfigurova\u0165 cel\u00e9 rie\u0161enie.<\/p>\n\n\n\n

        V r\u00e1mci konfigur\u00e1cie sa budeme venova\u0165 t\u00fdmto oblastiam:<\/p>\n\n\n\n

          \n
        • vPC peer-link<\/strong> \u2013 hlavn\u00fd synchroniza\u010dn\u00fd kan\u00e1l medzi Nexus switchmi, cez ktor\u00fd sa pren\u00e1\u0161aj\u00fa inform\u00e1cie o MAC tabu\u013ek\u00e1ch, LACP stavoch a \u010fal\u0161\u00edch \u0161trukt\u00farach potrebn\u00fdch pre s\u00fabe\u017en\u00fa prev\u00e1dzku oboch zariaden\u00ed.<\/li>\n\n\n\n
        • vPC keepalive link<\/strong> \u2013 link pre detekciu \u017eivotnosti peer zariadenia. Tento mechanizmus zabezpe\u010duje, aby sa predi\u0161lo split-brain scen\u00e1rom.<\/li>\n\n\n\n
        • Kompletn\u00e1 konfigur\u00e1cia oboch switchov<\/strong> \u2013 predstav\u00edme referen\u010dn\u00fa konfigur\u00e1ciu vr\u00e1tane odpor\u00fa\u010dan\u00fdch best practices, vhodn\u00fa pre produk\u010dn\u00e9 prostredia.<\/li>\n<\/ul>\n\n\n\n
          \n                           \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510\n                           \u2502        MANAGEMENT NETWORK         \u2502\n                           \u2502     (dedikovan\u00fd mgmt switch)      \u2502\n                           \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518\n                                     \u25b2               \u25b2\n                                     \u2502               \u2502\n                                     \u2502               \u2502\n            \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510 \u2502               \u2502 \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510\n            \u2502     Cisco Nexus 1    \u2502 \u2502               \u2502 \u2502     Cisco Nexus 2    \u2502\n            \u2502     mgmt: 10.1.1.35  \u2502\u2500\u2518               \u2514\u2500\u2502     mgmt: 10.1.1.36  \u2502\n            \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u252c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518                   \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u252c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518\n                        \u2502                                          \u2502\n                        \u2502                                          \u2502\n                        \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500 vPC KEEPALIVE \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518\n                           (realizovan\u00e9 cez Eth1\/31 \u2194 Eth1\/31)\n<\/code><\/pre>\n\n\n\n\n
          V\u00fdchodiskov\u00e9 nastavenia pre oba switche (pou\u017ei\u0165 na oboch)<\/strong><\/h2>\n\n\n\n
          Tieto pr\u00edkazy patria na oba Nexusy<\/strong>, preto\u017ee aktivuj\u00fa potrebn\u00e9 funkcie:<\/p>\n\n\n\n
          conf t\n  feature interface-vlan\n  feature lacp\n  feature vpc<\/code><\/pre>\n\n\n\n
          Konfigur\u00e1cia Switch 1 (10.1.1.35)<\/p>\n\n\n\n
            ! vPC domain \u2013 identick\u00e9 \u010d\u00edslo na oboch switchoch\n  vpc domain 10\n    role priority 100\n    peer-keepalive destination 10.1.1.36 source 10.1.1.35 vrf management\n    auto-recovery\n    ip arp synchronize\n    peer-gateway\n  exit\n\n interface port-channel1\n    description vPC-PEER-LINK to N5K-SW2\n    switchport\n    switchport mode trunk\n    spanning-tree port type network\n    vpc peer-link\n    no shutdown\n\n ! === vPC PEER-LINK ===\n  interface Ethernet1\/31\n    description vPC-PEER-LINK to N5K-SW2 Eth1\/31\n    switchport\n    switchport mode trunk\n    spanning-tree port type network\n    channel-group 1 mode active\n    no shutdown\n\n  interface Ethernet1\/32\n    description vPC-PEER-LINK to N5K-SW2 Eth1\/32\n    switchport\n    switchport mode trunk\n    spanning-tree port type network\n    channel-group 1 mode active\n    no shutdown<\/code><\/pre>\n\n\n\n
          Konfigur\u00e1cia Switch 2 (10.1.1.36)<\/p>\n\n\n\n
            ! vPC domain \u2013 mus\u00ed by\u0165 rovnak\u00fd ako na SW1\n  vpc domain 10\n    role priority 200\n    peer-keepalive destination 10.1.1.35 source 10.1.1.36 vrf management\n    auto-recovery\n    ip arp synchronize\n    peer-gateway\n  exit\n\n interface port-channel1\n    description vPC-PEER-LINK to N5K-SW2\n    switchport\n    switchport mode trunk\n    spanning-tree port type network\n    vpc peer-link\n    no shutdown\n\n ! === vPC PEER-LINK ===\n  interface Ethernet1\/31\n    description vPC-PEER-LINK to N5K-SW2 Eth1\/31\n    switchport\n    switchport mode trunk\n    spanning-tree port type network\n    channel-group 1 mode active\n    no shutdown\n\n  interface Ethernet1\/32\n    description vPC-PEER-LINK to N5K-SW2 Eth1\/32\n    switchport\n    switchport mode trunk\n    spanning-tree port type network\n    channel-group 1 mode active\n    no shutdown<\/code><\/pre>\n\n\n\n
          Overenie spr\u00e1vnej funkcie vPC \u2013 kontroln\u00e9 pr\u00edkazy a interpret\u00e1cia v\u00fdsledkov<\/strong><\/h1>\n\n\n\n
          Po dokon\u010den\u00ed konfigur\u00e1cie vPC je nevyhnutn\u00e9 overi\u0165, \u017ee cel\u00fd klaster pracuje konzistentne a oba switche zdie\u013eaj\u00fa stavov\u00e9 inform\u00e1cie korektne. Cisco Nexus poskytuje na tento \u00fa\u010del mno\u017estvo diagnostick\u00fdch pr\u00edkazov, ktor\u00e9 viete pou\u017ei\u0165 na potvrdenie spr\u00e1vneho nastavenia. V tejto \u010dasti si prejdeme najd\u00f4le\u017eitej\u0161ie z nich a uk\u00e1\u017eeme, \u010do presne maj\u00fa administr\u00e1tori o\u010dak\u00e1va\u0165 vo v\u00fdstupe.<\/p>\n\n\n\n
          Do textu si n\u00e1sledne vlo\u017e\u00edte vlastn\u00e9 screenshoty v\u00fdstupov jednotliv\u00fdch pr\u00edkazov.<\/p>\n\n\n\n
          1. Overenie celkov\u00e9ho stavu vPC \u2013 show vpc<\/code><\/strong><\/h1>\n\n\n\n
          Pr\u00edkaz sl\u00fa\u017ei na z\u00e1kladn\u00fa kontrolu stavu vPC domain. Poskytuje inform\u00e1cie o:<\/p>\n\n\n\n
            \n
          • stave peer-linku<\/strong>,<\/li>\n\n\n\n
          • stave vPC keepalive<\/strong>,<\/li>\n\n\n\n
          • zelenej \/ \u010dervenej indik\u00e1cii pre jednotliv\u00e9 vPC porty,<\/li>\n\n\n\n
          • \u00falohe (role) dan\u00e9ho switcha v dom\u00e9ne,<\/li>\n\n\n\n
          • zdravotnom stave vPC (operational status).<\/li>\n<\/ul>\n\n\n\n
            Do \u010dl\u00e1nku vlo\u017e\u00edte screenshot:<\/p>\n\n\n\n
            Pr\u00edklad:<\/strong><\/p>\n\n\n
            \n
            \"\"<\/figure>\n<\/div>\n\n\n
            V spr\u00e1vne nakonfigurovanom prostred\u00ed maj\u00fa by\u0165 k\u013e\u00fa\u010dov\u00e9 polo\u017eky vo v\u00fdstupe v stave:<\/p>\n\n\n\n
              \n
            • Peer-link : up<\/strong><\/li>\n\n\n\n
            • Peer-keepalive : alive<\/strong><\/li>\n\n\n\n
            • vPC role : primary\/secondary<\/strong> \u2013 pod\u013ea priority<\/li>\n\n\n\n
            • vPC porty : up \/ synchronized<\/strong><\/li>\n<\/ul>\n\n\n\n
              Ak by boli hodnoty “down”, “not synchronized” alebo “type inconsistency”, ide o probl\u00e9m, ktor\u00fd si vy\u017eaduje z\u00e1sah.<\/p>\n\n\n\n
              2. Overenie keepalive komunik\u00e1cie \u2013 show vpc peer-keepalive<\/code><\/strong><\/h1>\n\n\n\n
              vPC keepalive sl\u00fa\u017ei na detekciu \u017eivotnosti peer zariadenia a zabra\u0148uje split-brain stavu. Tento pr\u00edkaz zobrazuje:<\/p>\n\n\n\n
                \n
              • IP adresy pou\u017e\u00edvan\u00e9 na keepalive,<\/li>\n\n\n\n
              • akt\u00edvny stav linky,<\/li>\n\n\n\n
              • \u010das poslednej prijatej spr\u00e1vy.<\/li>\n<\/ul>\n\n\n\n
                Pr\u00edklad:<\/strong><\/p>\n\n\n
                \n
                \"\"<\/figure>\n<\/div>\n\n\n
                Spr\u00e1vny stav:<\/p>\n\n\n\n
                  \n
                • Keepalive interval working normally<\/strong><\/li>\n\n\n\n
                • Destination reachable<\/strong><\/li>\n\n\n\n
                • No packet drops<\/strong><\/li>\n<\/ul>\n\n\n\n
                  Ak je stav \u201enot operational\u201c alebo \u201edestination unreachable\u201c, vPC prejde do degradovan\u00e9ho re\u017eimu.<\/p>\n\n\n\n
                  3. Kontrola konzistencie konfigur\u00e1cie \u2013 show vpc consistency-parameters global<\/code><\/strong><\/h1>\n\n\n\n
                  Tento pr\u00edkaz je kritick\u00fd pre overenie, \u017ee oba switche maj\u00fa kompatibiln\u00e9 nastavenia. Porovn\u00e1va:<\/p>\n\n\n\n
                    \n
                  • VLAN konfigur\u00e1ciu<\/li>\n\n\n\n
                  • STP nastavenia<\/li>\n\n\n\n
                  • MTU<\/li>\n\n\n\n
                  • VTP<\/li>\n\n\n\n
                  • QoS parametre<\/li>\n\n\n\n
                  • Switchport m\u00f3d<\/li>\n\n\n\n
                  • v\u0161etky \u010fal\u0161ie atrib\u00faty potrebn\u00e9 pre spr\u00e1vny chod vPC<\/li>\n<\/ul>\n\n\n\n
                    Pr\u00edklad screenshotu:<\/strong><\/p>\n\n\n
                    \n
                    \"\"<\/figure>\n<\/div>\n\n\n
                    D\u00f4le\u017eit\u00fd je v\u00fdsledok:<\/p>\n\n\n\n
                      \n
                    • Consistency status : success<\/strong><\/li>\n<\/ul>\n\n\n\n
                      Ak sa objav\u00ed:<\/p>\n\n\n\n
                        \n
                      • Type-1 inconsistency<\/strong> \u2013 vPC sa automaticky zablokuje<\/li>\n\n\n\n
                      • Type-2 inconsistency<\/strong> \u2013 prev\u00e1dzka m\u00f4\u017ee pokra\u010dova\u0165, no stav je nestabiln\u00fd<\/li>\n<\/ul>\n\n\n\n
                        4. Stav port-channelov \u2013 show port-channel summary<\/code><\/strong><\/h1>\n\n\n\n
                        Pr\u00edkaz sl\u00fa\u017ei na kontrolu:<\/p>\n\n\n\n
                          \n
                        • \u010dlenov LACP port-channelov,<\/li>\n\n\n\n
                        • stavu jednotliv\u00fdch liniek,<\/li>\n\n\n\n
                        • spr\u00e1vneho priradenia portov do skup\u00edn,<\/li>\n\n\n\n
                        • \u010di s\u00fa porty v akt\u00edvnom stave (\u201eP” = bundled, “D” = down, “I” = individual).<\/li>\n<\/ul>\n\n\n\n
                          Tu vlo\u017e\u00edte screenshot:<\/strong><\/p>\n\n\n
                          \n
                          \"\"<\/figure>\n<\/div>\n\n\n
                          Pre peer-link (Port-Channel 100) maj\u00fa by\u0165 oba \u010dleny v stave:<\/p>\n\n\n\n
                            \n
                          • P<\/strong> (port je agregovan\u00fd a akt\u00edvny)<\/li>\n<\/ul>\n\n\n\n
                            Ak je stav \u201eD\u201c alebo \u201eI\u201c, znamen\u00e1 to chybu LACP, VLAN alebo MTU.<\/p>\n\n\n\n
                            <\/p>\n","protected":false},"excerpt":{"rendered":"
                            Ako nakonfigurova\u0165 Cisco Nexus VPC klaster pre Proxmox? Kompletn\u00fd n\u00e1vod: vPC peer-link a keepalive konfigur\u00e1cia, LACP port-channel nastavenie, elimin\u00e1cia STP blokovania, vysok\u00e1 dostupnos\u0165 siete. Obsahuje CLI pr\u00edkazy pre oba Nexus prep\u00edna\u010de a overenie funk\u010dnosti pomocou show vpc.How to configure Cisco Nexus VPC cluster for Proxmox? Complete guide: vPC peer-link and keepalive configuration, LACP port-channel setup, STP blocking elimination, high network availability. Includes CLI commands for both Nexus switches and functionality verification using show vpc.<\/p>\n","protected":false},"author":1,"featured_media":1707,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[159],"tags":[236],"class_list":["post-1701","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-proxmox","tag-cisco-ucs-c220-m7"],"_links":{"self":[{"href":"https:\/\/virtualall.sk\/en\/wp-json\/wp\/v2\/posts\/1701","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=1701"}],"version-history":[{"count":8,"href":"https:\/\/virtualall.sk\/en\/wp-json\/wp\/v2\/posts\/1701\/revisions"}],"predecessor-version":[{"id":2058,"href":"https:\/\/virtualall.sk\/en\/wp-json\/wp\/v2\/posts\/1701\/revisions\/2058"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/virtualall.sk\/en\/wp-json\/wp\/v2\/media\/1707"}],"wp:attachment":[{"href":"https:\/\/virtualall.sk\/en\/wp-json\/wp\/v2\/media?parent=1701"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/virtualall.sk\/en\/wp-json\/wp\/v2\/categories?post=1701"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/virtualall.sk\/en\/wp-json\/wp\/v2\/tags?post=1701"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}