{"id":1701,"date":"2025-11-19T10:00:08","date_gmt":"2025-11-19T10:00:08","guid":{"rendered":"https:\/\/virtualall.sk\/?p=1701"},"modified":"2026-01-11T08:57:46","modified_gmt":"2026-01-11T08:57:46","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 &#8211; Complete Guide"},"content":{"rendered":"<div style=\"background-color: #e7f3ff; border-left: 4px solid #2196F3; padding: 15px; margin: 20px 0;\">\n<strong>TL;DR &#8211; R\u00fdchle zhrnutie:<\/strong> Cisco Nexus VPC (Virtual Port-Channel) umo\u017e\u0148uje prepoji\u0165 server s dvoma nez\u00e1visl\u00fdmi prep\u00edna\u010dmi cez jeden logick\u00fd port-channel. Eliminuje STP blokovanie, poskytuje redundanciu a zdvojn\u00e1sobuje priepustnos\u0165. Konfigur\u00e1cia vy\u017eaduje vPC domain, peer-link a keepalive link. Ide\u00e1lne pre Proxmox klaster s LACP bonding.\n<\/div>\n<div style=\"background-color: #f0f0f0; padding: 15px; margin: 20px 0; border-radius: 5px;\">\n<strong>R\u00fdchle fakty o Cisco Nexus VPC:<\/strong><\/p>\n<ul>\n<li><strong>Technol\u00f3gia:<\/strong> Virtual Port-Channel (vPC)<\/li>\n<li><strong>\u00da\u010del:<\/strong> Vysok\u00e1 dostupnos\u0165 siete bez STP blokovania<\/li>\n<li><strong>Komponenty:<\/strong> vPC Peer-Link, Keepalive Link, vPC Domain<\/li>\n<li><strong>Protokol:<\/strong> LACP (Link Aggregation Control Protocol)<\/li>\n<li><strong>V\u00fdhody:<\/strong> 2x priepustnos\u0165, akt\u00edvne v\u0161etky linky, minim\u00e1lny v\u00fdpadok<\/li>\n<li><strong>Pou\u017eitie:<\/strong> Proxmox, VMware, Hyper-V klastre<\/li>\n<\/ul>\n<\/div>\n<p><strong>Cisco Nexus VPC klaster<\/strong> je rie\u0161enie pre vysok\u00fa dostupnos\u0165 siete, ktor\u00e9 v\u00e1m uk\u00e1\u017eem v tomto n\u00e1vode pre prostredie PROXMOX. 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 spr\u00e1vny n\u00e1vrh sie\u0165ovej infra\u0161trukt\u00fary k\u013e\u00fa\u010dov\u00fd.<\/p>\n<p>V tomto \u010dl\u00e1nku sa dozviete, ako nakonfigurova\u0165 <strong>Cisco Nexus VPC klaster<\/strong> na dvojici Nexus prep\u00edna\u010dov pre redundantn\u00fa konektivitu va\u0161ich Proxmox serverov.<\/p>\n<h2>V\u00fdhody pou\u017eitia port-channelu pre Cisco Nexus VPC klaster<\/h2>\n<p>Port-Channel (tie\u017e zn\u00e1my ako EtherChannel alebo LAG) je technol\u00f3gia, ktor\u00e1 umo\u017e\u0148uje zoskupi\u0165 viacero fyzick\u00fdch Ethernet liniek do jedn\u00e9ho logick\u00e9ho spojenia. Pre prep\u00edna\u010d sa tak\u00e9to zoskupenie jav\u00ed ako jedno spojenie.<\/p>\n<p>Hlavn\u00e9 v\u00fdhody:<\/p>\n<ul>\n<li><strong>Vy\u0161\u0161ia priepustnos\u0165<\/strong> \u2013 s\u010d\u00edtanie kapacity liniek (2\u00d710G = 20G, 4\u00d710G = 40G)<\/li>\n<li><strong>Redundancia<\/strong> \u2013 pri v\u00fdpadku jednej linky ostatn\u00e9 preberaj\u00fa prev\u00e1dzku<\/li>\n<li><strong>Load-balancing<\/strong> \u2013 distrib\u00facia z\u00e1\u0165a\u017ee pomocou hash algoritmov (MAC, IP, L4 porty)<\/li>\n<li><strong>Jednoduch\u0161ia spr\u00e1va topol\u00f3gie<\/strong> \u2013 menej logick\u00fdch liniek na spr\u00e1vu<\/li>\n<\/ul>\n<h2>\u010co je to Cisco VPC (Virtual Port-Channel)<\/h2>\n<p><a href=\"https:\/\/www.cisco.com\/c\/en\/us\/td\/docs\/switches\/datacenter\/nexus5000\/sw\/configuration\/guide\/cli\/CLIConfigurationGuide\/VPCs.html\" target=\"_blank\" rel=\"dofollow noopener\">Cisco vPC<\/a> umo\u017e\u0148uje pripoji\u0165 jeden alebo viac downstream zariaden\u00ed pomocou port-channelu, ktor\u00fd je rozdelen\u00fd medzi dve nez\u00e1visl\u00e9 Nexus jednotky. Zariadenie &#8220;vid\u00ed&#8221; tento port-channel ako jeden logick\u00fd spoj, zatia\u013e \u010do v skuto\u010dnosti s\u00fa linky fyzicky pripojen\u00e9 do dvoch r\u00f4znych prep\u00edna\u010dov.<\/p>\n<p>V\u00fdhody <strong>Cisco Nexus VPC klastra<\/strong>:<\/p>\n<ul>\n<li><strong>Elimin\u00e1cia STP blokovania<\/strong> \u2013 v\u0161etky linky s\u00fa akt\u00edvne<\/li>\n<li><strong>Minim\u00e1lny v\u00fdpadok<\/strong> \u2013 pri zlyh\u00e1n\u00ed jedn\u00e9ho prep\u00edna\u010da zost\u00e1va spojenie akt\u00edvne<\/li>\n<li><strong>Akt\u00edvny LACP port-channel<\/strong> \u2013 naprie\u010d dvoma fyzick\u00fdmi prep\u00edna\u010dmi<\/li>\n<li><strong>Stabiln\u00e1 architekt\u00fara<\/strong> \u2013 bez z\u00e1vislosti na STP<\/li>\n<\/ul>\n<h2>Konfigur\u00e1cia Cisco Nexus VPC klastra<\/h2>\n<h3>Z\u00e1kladn\u00e9 nastavenie na oboch prep\u00edna\u010doch<\/h3>\n<pre><code>conf t\n  feature interface-vlan\n  feature lacp\n  feature vpc\n<\/code><\/pre>\n<h3>Switch 1 (10.1.1.35) &#8211; Primary<\/h3>\n<pre><code>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\nexit\n\ninterface 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\ninterface 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\ninterface 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\n<\/code><\/pre>\n<h3>Switch 2 (10.1.1.36) &#8211; Secondary<\/h3>\n<pre><code>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\nexit\n\ninterface port-channel1\n  description vPC-PEER-LINK to N5K-SW1\n  switchport\n  switchport mode trunk\n  spanning-tree port type network\n  vpc peer-link\n  no shutdown\n\ninterface Ethernet1\/31\n  description vPC-PEER-LINK to N5K-SW1 Eth1\/31\n  switchport\n  switchport mode trunk\n  spanning-tree port type network\n  channel-group 1 mode active\n  no shutdown\n\ninterface Ethernet1\/32\n  description vPC-PEER-LINK to N5K-SW1 Eth1\/32\n  switchport\n  switchport mode trunk\n  spanning-tree port type network\n  channel-group 1 mode active\n  no shutdown\n<\/code><\/pre>\n<h3>K\u013e\u00fa\u010dov\u00e9 komponenty Cisco Nexus VPC klastra<\/h3>\n<ul>\n<li><strong>vPC Peer-Link<\/strong> \u2013 hlavn\u00fd synchroniza\u010dn\u00fd kan\u00e1l pren\u00e1\u0161aj\u00faci MAC tabu\u013eku a LACP stavy<\/li>\n<li><strong>vPC Keepalive Link<\/strong> \u2013 detekuje stav peer zariadenia a zabra\u0148uje split-brain scen\u00e1rom<\/li>\n<\/ul>\n<h2>Overenie spr\u00e1vnej funkcie Cisco Nexus VPC klastra<\/h2>\n<h3>1. Celkov\u00fd stav vPC<\/h3>\n<pre><code>show vpc<\/code><\/pre>\n<p>O\u010dak\u00e1van\u00e9 hodnoty:<\/p>\n<ul>\n<li>Peer-link status: <strong>up<\/strong><\/li>\n<li>vPC keepalive status: <strong>alive<\/strong><\/li>\n<li>Role: primary\/secondary<\/li>\n<\/ul>\n<h3>2. Keepalive komunik\u00e1cia<\/h3>\n<pre><code>show vpc peer-keepalive<\/code><\/pre>\n<p>Overuje IP adresy keepalive, stav linky a \u010das poslednej spr\u00e1vy.<\/p>\n<h3>3. Konzistencia konfigur\u00e1cie<\/h3>\n<pre><code>show vpc consistency-parameters global<\/code><\/pre>\n<p>Porovn\u00e1va VLAN konfigur\u00e1ciu, STP nastavenia, MTU, VTP a QoS. O\u010dak\u00e1van\u00fd stav: <strong>success<\/strong>.<\/p>\n<h3>4. Stav port-channelu<\/h3>\n<pre><code>show port-channel summary<\/code><\/pre>\n<p>Zobrazuje LACP skupiny a stav jednotliv\u00fdch liniek. O\u010dak\u00e1van\u00fd stav: <strong>P<\/strong> (bundled, active).<\/p>\n<h2>Integr\u00e1cia s Proxmox<\/h2>\n<p>Po spr\u00e1vnej konfigur\u00e1cii <strong>Cisco Nexus VPC klastra<\/strong> m\u00f4\u017eete pripoji\u0165 va\u0161e <a href=\"https:\/\/virtualall.sk\/category\/proxmox\/\">Proxmox<\/a> servery pomocou bonding rozhrania (LACP mode 4) pre maxim\u00e1lnu redundanciu a priepustnos\u0165.<\/p>\n<h2>Zhrnutie<\/h2>\n<p><strong>Cisco Nexus VPC klaster<\/strong> poskytuje spo\u013eahliv\u00fa a vysoko dostupn\u00fa sie\u0165ov\u00fa infra\u0161trukt\u00faru pre va\u0161e virtualiza\u010dn\u00e9 prostredie. K\u013e\u00fa\u010dov\u00e9 body:<\/p>\n<ul>\n<li>vPC eliminuje STP blokovanie a maximalizuje vyu\u017eitie liniek<\/li>\n<li>Peer-link a keepalive link s\u00fa kritick\u00e9 pre spr\u00e1vnu funkciu<\/li>\n<li>Pravidelne overujte konzistenciu konfigur\u00e1cie medzi prep\u00edna\u010dmi<\/li>\n<li>Kombin\u00e1cia s Proxmox bonding poskytuje end-to-end redundanciu<\/li>\n<\/ul>\n<h2>\u010casto kladen\u00e9 ot\u00e1zky (FAQ)<\/h2>\n<h3>\u010co je Cisco vPC (Virtual Port-Channel)?<\/h3>\n<p>Cisco vPC je technol\u00f3gia, ktor\u00e1 umo\u017e\u0148uje pripoji\u0165 server alebo sie\u0165ov\u00e9 zariadenie k <strong>dvom nez\u00e1visl\u00fdm Nexus prep\u00edna\u010dom<\/strong> pomocou jedn\u00e9ho logick\u00e9ho port-channelu. Zariadenie vid\u00ed oba prep\u00edna\u010de ako jeden logick\u00fd spoj.<\/p>\n<h3>Ak\u00fd je rozdiel medzi vPC a tradi\u010dn\u00fdm port-channelom?<\/h3>\n<p>Tradi\u010dn\u00fd port-channel sp\u00e1ja linky k <strong>jedn\u00e9mu prep\u00edna\u010du<\/strong>. vPC umo\u017e\u0148uje rozlo\u017ei\u0165 port-channel medzi <strong>dva fyzick\u00e9 prep\u00edna\u010de<\/strong>, \u010d\u00edm sa eliminuje single point of failure.<\/p>\n<h3>\u010co je vPC Peer-Link a pre\u010do je d\u00f4le\u017eit\u00fd?<\/h3>\n<p>vPC Peer-Link je <strong>dedikovan\u00fd trunk<\/strong> medzi dvoma Nexus prep\u00edna\u010dmi, ktor\u00fd synchronizuje MAC tabu\u013eky, LACP stavy a \u010fal\u0161ie control plane inform\u00e1cie. Bez peer-linku vPC nefunguje.<\/p>\n<h3>\u010co je vPC Keepalive Link?<\/h3>\n<p>Keepalive link je <strong>sekund\u00e1rny komunika\u010dn\u00fd kan\u00e1l<\/strong> (zvy\u010dajne cez management VRF), ktor\u00fd monitoruje dostupnos\u0165 peer prep\u00edna\u010da. Zabra\u0148uje split-brain scen\u00e1rom pri v\u00fdpadku peer-linku.<\/p>\n<h3>Ako nakonfigurova\u0165 Proxmox bonding pre vPC?<\/h3>\n<p>V Proxmox vytvorte <strong>Linux bond<\/strong> s mode 4 (LACP\/802.3ad). Pripojte dve sie\u0165ov\u00e9 karty &#8211; jednu k prv\u00e9mu a druh\u00fa k druh\u00e9mu Nexus prep\u00edna\u010du. Na Nexus strane nakonfigurujte vPC port-channel.<\/p>\n<h3>Ak\u00e9 pr\u00edkazy pou\u017ei\u0165 na overenie vPC stavu?<\/h3>\n<p>Hlavn\u00e9 pr\u00edkazy: <strong>show vpc<\/strong> (celkov\u00fd stav), <strong>show vpc peer-keepalive<\/strong> (keepalive), <strong>show vpc consistency-parameters global<\/strong> (konzistencia), <strong>show port-channel summary<\/strong> (port-channel stav).<\/p>\n<p>Viac inform\u00e1ci\u00ed n\u00e1jdete v <a href=\"https:\/\/www.cisco.com\/c\/en\/us\/support\/switches\/nexus-5000-series-switches\/products-installation-and-configuration-guides-list.html\" target=\"_blank\" rel=\"dofollow noopener\">ofici\u00e1lnej Cisco Nexus dokument\u00e1cii<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p><!--:sk-->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.<!--:--><!--:en-->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":7,"href":"https:\/\/virtualall.sk\/en\/wp-json\/wp\/v2\/posts\/1701\/revisions"}],"predecessor-version":[{"id":1770,"href":"https:\/\/virtualall.sk\/en\/wp-json\/wp\/v2\/posts\/1701\/revisions\/1770"}],"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}]}}