{"id":693,"date":"2016-04-03T13:18:51","date_gmt":"2016-04-03T13:18:51","guid":{"rendered":"http:\/\/www.safekom.pl\/blog\/?p=693"},"modified":"2016-04-26T14:41:50","modified_gmt":"2016-04-26T13:41:50","slug":"lab-vxvlan-pierwsze-podjescie","status":"publish","type":"post","link":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/","title":{"rendered":"LAB – VXVLAN pierwsze podje\u015bcie"},"content":{"rendered":"

Ostatnio uczestniczy\u0142em w ciekawym webbinarium zorganizowane przy forum CCIE.pl<\/strong> pod tytu\u0142em\u00a0DCI „po nowemu”<\/strong> – prezentacj\u0119 prowadzi\u0142\u00a0Piotr Jab\u0142o\u0144ski.<\/p>\n

Piotr pokazywa\u0142 jak w dzisiejszych czasach mo\u017cna wykorzysta\u0107 technologi\u0119 VXVLAN<\/strong> do rozci\u0105gania L2 pomi\u0119dzy DataCenter lub w samym DC.<\/p>\n

Po obejrzeniu stwierdzi\u0142em \u017ce trzeba zbudowa\u0107 laba i zobaczy\u0107 z czym si\u0119 to je VXVLAN<\/strong>. Wst\u0119pnie VXVLAN<\/strong> zacz\u0105\u0142em poznawa\u0107 przy nauce Vmware NSX<\/strong> – wkr\u00f3tce mo\u017ce jaki\u015b wpis pojawi si\u0119 w tym temacie te\u017c.<\/p>\n

W chwili wolnej zbudowa\u0142em lab zgodnie z poni\u017cszym diagramem:<\/p>\n

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

ca\u0142o\u015b\u0107 uruchomi\u0142em na laptopie z wykorzystanie Vmware Workstation. Poni\u017cej opisz\u0119 jak to uruchomi\u0107. Poka\u017c\u0119 jak z wykorzystanie Cisco CSR1000v<\/strong> oraz Cisco ASAv<\/strong> mo\u017cna pozna\u0107 wykorzystanie oraz zrozumie\u0107 dzia\u0142anie VXVLAN<\/strong><\/p>\n

<\/p>\n

Krok 1.<\/h6>\n

Uruchamiamy nasze wirtualki – ponie\u017cej poka\u017ce jak uruchomi\u0107 CSR1000v<\/strong> pod Worksation<\/strong>. Cisco ASAv<\/strong> pokaza\u0142em we wpisie Instalacja ASAv w Labie<\/a><\/p>\n

Importujemy Maszyn\u0119 z CSR1000v<\/strong> do naszego Workstation:<\/p>\n

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

Klikamy Open a Virtual Machine \u00a0w nowym oknie wybieramy nasz polik OVA<\/p>\n

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

po klikni\u0119ciu otw\u00f3rz, w nowym oknie wpisujemy nazw\u0119 dla naszego Routera taka nazwa b\u0119dzie wy\u015bwietlana w Inventory, w Storage path podajemy gdzie maj\u0105 by\u0107 przechowywane pliki wirtualnej maszyny.<\/p>\n

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

Po klikni\u0119ciu Import rozpocznie si\u0119 proces importu<\/p>\n

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

po zako\u0144czeniu uruchamiamy wirtualn\u0105 maszyn\u0119<\/p>\n

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

przy pierwszym uruchomieniu musimy klikn\u0105\u0107 dowolnym klawiszem tak aby rozpocz\u0105\u0142 proces uruchomienia.<\/p>\n

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

Po zako\u0144czeniu mo\u017cemy powt\u00f3rzy\u0107 dla kolejnych 2 CSR’\u00f3w oraz ASAv proces.<\/p>\n

<\/h6>\n
Krok 2.<\/h6>\n

Przygotowanie Workstation do Laba<\/p>\n

Tworzymy Lan Segmenty, tak aby by\u0142y mo\u017cliwe po\u0142\u0105czenia, zgodnie z diagramem wy\u017cej.<\/p>\n

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

Krok 3<\/h6>\n

Konfigurujemy je zgodnie z za\u0142o\u017ceniami kt\u00f3re s\u0105 poni\u017cej<\/p>\n\n\n\n\n\n\n\n\n
Cisco CSR100v01<\/strong><\/td>\n<\/tr>\n
Interfejs\u00a0<\/strong><\/td>\nadresacja\u00a0<\/strong><\/td>\nopis<\/strong><\/td>\n<\/tr>\n
Gi 1<\/strong><\/td>\n10.10.30.2\/24<\/td>\nPo\u0142\u0105czenie z CSR1000v03 nasz Core<\/td>\n<\/tr>\n
Gi 2<\/strong><\/td>\nunatged<\/td>\npo\u0142\u0105czenie do PC1<\/td>\n<\/tr>\n
Gi 3<\/strong><\/td>\n192.168.220.11\/24<\/td>\nnasza adresacja wykorzystywana do MGMT. Interfejs w VRF MGMT<\/td>\n<\/tr>\n
Lo0<\/strong><\/td>\n1.1.1.1\/32<\/td>\nNasz adres loopback 0<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Konfiguracja:<\/p>\n

dla Interfejsu Gi1:<\/p>\n

interface GigabitEthernet1\r\n description csrv01<-->csrv03\r\n ip address 10.10.30.1 255.255.255.0\r\n negotiation auto\r\n no sh<\/pre>\n
dla Loopback 0<\/p>\n
interface Loopback0\r\n ip address 1.1.1.1 255.255.255.255<\/pre>\n
Gi 3<\/p>\n
ip vrf mgmt\r\n description mgmt\r\nexit\r\ninterface GigabitEthernet3\r\n description MGMT\r\n ip vrf forwarding mgmt\r\n ip address 192.168.220.11 255.255.255.0\r\n no sh\r\nend\r\n\r\n<\/pre>\n\n\n\n\n\n\n\n\n
Cisco CSR100v02<\/strong><\/td>\n<\/tr>\n
Interfejs\u00a0<\/strong><\/td>\nadresacja\u00a0<\/strong><\/td>\nopis<\/strong><\/td>\n<\/tr>\n
Gi 1<\/strong><\/td>\n10.10.40.2\/24<\/td>\nPo\u0142\u0105czenie z CSR1000v03 nasz Core<\/td>\n<\/tr>\n
Gi 2<\/strong><\/td>\nunatged<\/td>\npo\u0142\u0105czenie do PC2<\/td>\n<\/tr>\n
Gi 3<\/strong><\/td>\n192.168.220.12\/24<\/td>\nnasza adresacja wykorzystywana do MGMT. Interfejs w VRF MGMT<\/td>\n<\/tr>\n
Lo0<\/strong><\/td>\n2.2.2.2\/32<\/td>\nLoopback 0<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Konfiguracja:<\/p>\n
dla Interfejsu Gi1:<\/p>\n
interface GigabitEthernet1\r\n description csrv02<-->csrv03\r\n ip address 10.10.40.1 255.255.255.0\r\n negotiation auto\r\n no sh<\/pre>\n
dla Loopback 0<\/p>\n
interface Loopback0\r\n ip address 2.2.2.2 255.255.255.255<\/pre>\n
Gi 3<\/p>\n
ip vrf mgmt\r\n description mgmt\r\nexit\r\ninterface GigabitEthernet3\r\n description MGMT\r\n ip vrf forwarding mgmt\r\n ip address 192.168.220.12 255.255.255.0\r\n no sh\r\nend<\/pre>\n\n\n\n\n\n\n\n\n\n
Cisco CSR100v03<\/strong><\/td>\n<\/tr>\n
Interfejs\u00a0<\/strong><\/td>\nadresacja\u00a0<\/strong><\/td>\nopis<\/strong><\/td>\n<\/tr>\n
Gi 1<\/strong><\/td>\n10.10.20.2\/24<\/td>\nPo\u0142\u0105czenie z\u00a0ASAv01<\/td>\n<\/tr>\n
Gi 2<\/strong><\/td>\n10.10.30.2\/24<\/td>\nPo\u0142\u0105czenie z CSR1000v01<\/td>\n<\/tr>\n
Gi 3<\/strong><\/td>\n10.10.40.224<\/td>\nPo\u0142\u0105czenie z CSR1000v02<\/td>\n<\/tr>\n
Gi 4<\/strong><\/td>\n192.168.220.10\/24<\/td>\nnasza adresacja wykorzystywana do MGMT. Interfejs w VRF MGMT<\/td>\n<\/tr>\n
Lo0<\/strong><\/td>\n3.3.3.3\/32<\/td>\nLoopback 0<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Konfiguracja:<\/p>\n
Gi1:<\/p>\n
interface GigabitEthernet1\r\n ip address 10.10.20.2 255.255.255.0\r\n no sh<\/pre>\n
Gi2:<\/p>\n
interface GigabitEthernet2\r\n ip address 10.10.30.2 255.255.255.0\r\n<\/pre>\n
Gi3:<\/p>\n
interface GigabitEthernet3\r\n ip address 10.10.40.2 255.255.255.0<\/pre>\n
Gi4:<\/p>\n
ip vrf mgmt\r\n description mgmt\r\nexit\r\ninterface GigabitEthernet4\r\n description MGMT\r\n ip vrf forwarding mgmt\r\n ip address 192.168.220.10 255.255.255.0\r\n no sh\r\nend<\/pre>\n
dla Loopback 0<\/p>\n
interface Loopback0\r\n ip address 3.3.3.3 255.255.255.255<\/pre>\n\n\n\n\n\n\n
Cisco\u00a0ASAv01<\/strong><\/td>\n<\/tr>\n
Interfejs\u00a0<\/strong><\/td>\nadresacja\u00a0<\/strong><\/td>\nopis<\/strong><\/td>\n<\/tr>\n
Gi 0\/1<\/strong><\/td>\n192.168.1.75\/24<\/td>\nOut – nasz styk z internetem<\/td>\n<\/tr>\n
Gi 0\/2<\/strong><\/td>\n10.10.20.1\/24<\/td>\nPo\u0142\u0105czenie z CSR1000v03<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Konfiguracja:<\/p>\n
Gi 0\/1<\/p>\n
interface GigabitEthernet0\/0\r\n nameif out\r\n security-level 0\r\n ip address 192.168.1.75 255.255.255.0\r\n no sh<\/pre>\n
Gi 0\/2<\/p>\n
interface GigabitEthernet0\/1\r\n nameif lan\r\n security-level 0\r\n ip address 10.10.20.1 255.255.255.0\r\n no sh\r\n<\/pre>\n
<\/h6>\n
 <\/p>\n
Krok 4<\/h6>\n
Konfigurujemy routing pomi\u0119dzy urz\u0105dzeniami w mym przypadku wykorzystuj\u0119 OSPF<\/strong><\/p>\n
CSRv01:<\/p>\n
router ospf 1\r\n network 1.1.1.1 0.0.0.0 area 0\r\n network 10.10.30.0 0.0.0.255 area 0<\/pre>\n
CSRv02:<\/p>\n
router ospf 1\r\n network 2.2.2.2 0.0.0.0 area 0\r\n network 10.10.40.0 0.0.0.255 area 0<\/pre>\n
CSRv03:<\/p>\n
router ospf 1\r\n network 3.3.3.3 0.0.0.0 area 0\r\n network 10.10.20.0 0.0.0.255 area 0\r\n network 10.10.30.0 0.0.0.255 area 0\r\n network 10.10.40.0 0.0.0.255 area 0<\/pre>\n
ASAv01:<\/p>\n
router ospf 1\r\n network 10.10.20.0 255.255.255.0 area 0<\/pre>\n
Sprawdzamy dzia\u0142anie OSPF’a<\/p>\n
CSRv01<\/p>\n
csr1000v01#show ip route \r\nCodes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP\r\n       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area \r\n       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2\r\n       E1 - OSPF external type 1, E2 - OSPF external type 2\r\n       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2\r\n       ia - IS-IS inter area, * - candidate default, U - per-user static route\r\n       o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP\r\n       a - application route\r\n       + - replicated route, % - next hop override, p - overrides from PfR\r\n\r\nGateway of last resort is not set\r\n\r\n      1.0.0.0\/32 is subnetted, 1 subnets\r\nC        1.1.1.1 is directly connected, Loopback0\r\n      2.0.0.0\/32 is subnetted, 1 subnets\r\nO        2.2.2.2 [110\/3] via 10.10.30.2, 00:05:00, GigabitEthernet1\r\n      3.0.0.0\/32 is subnetted, 1 subnets\r\nO        3.3.3.3 [110\/2] via 10.10.30.2, 00:05:10, GigabitEthernet1\r\n      10.0.0.0\/8 is variably subnetted, 4 subnets, 2 masks\r\nO        10.10.20.0\/24 [110\/2] via 10.10.30.2, 00:05:00, GigabitEthernet1\r\nC        10.10.30.0\/24 is directly connected, GigabitEthernet1\r\nL        10.10.30.1\/32 is directly connected, GigabitEthernet1\r\nO        10.10.40.0\/24 [110\/2] via 10.10.30.2, 00:05:00, GigabitEthernet1<\/pre>\n
CSRv02<\/p>\n
csr1000v02#show ip route \r\nCodes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP\r\n       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area \r\n       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2\r\n       E1 - OSPF external type 1, E2 - OSPF external type 2\r\n       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2\r\n       ia - IS-IS inter area, * - candidate default, U - per-user static route\r\n       o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP\r\n       a - application route\r\n       + - replicated route, % - next hop override, p - overrides from PfR\r\n\r\nGateway of last resort is not set\r\n\r\n      1.0.0.0\/32 is subnetted, 1 subnets\r\nO        1.1.1.1 [110\/3] via 10.10.40.2, 00:13:31, GigabitEthernet1\r\n      2.0.0.0\/32 is subnetted, 1 subnets\r\nC        2.2.2.2 is directly connected, Loopback0\r\n      3.0.0.0\/32 is subnetted, 1 subnets\r\nO        3.3.3.3 [110\/2] via 10.10.40.2, 00:13:31, GigabitEthernet1\r\n      10.0.0.0\/8 is variably subnetted, 6 subnets, 3 masks\r\nO        10.10.20.0\/24 [110\/2] via 10.10.40.2, 00:13:21, GigabitEthernet1\r\nO        10.10.30.0\/24 [110\/2] via 10.10.40.2, 00:13:31, GigabitEthernet1\r\nC        10.10.40.0\/24 is directly connected, GigabitEthernet1\r\nL        10.10.40.1\/32 is directly connected, GigabitEthernet1\r\nC        10.20.20.12\/30 is directly connected, GigabitEthernet2\r\nL        10.20.20.13\/32 is directly connected, GigabitEthernet2<\/pre>\n
CSRv03<\/p>\n
core-csrv03#show ip route \r\nCodes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP\r\n       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area \r\n       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2\r\n       E1 - OSPF external type 1, E2 - OSPF external type 2\r\n       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2\r\n       ia - IS-IS inter area, * - candidate default, U - per-user static route\r\n       o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP\r\n       a - application route\r\n       + - replicated route, % - next hop override, p - overrides from PfR\r\n\r\nGateway of last resort is not set\r\n\r\n      1.0.0.0\/32 is subnetted, 1 subnets\r\nO        1.1.1.1 [110\/2] via 10.10.30.1, 00:14:18, GigabitEthernet2\r\n      2.0.0.0\/32 is subnetted, 1 subnets\r\nO        2.2.2.2 [110\/2] via 10.10.40.1, 00:14:08, GigabitEthernet3\r\n      3.0.0.0\/32 is subnetted, 1 subnets\r\nC        3.3.3.3 is directly connected, Loopback0\r\n      10.0.0.0\/8 is variably subnetted, 6 subnets, 2 masks\r\nC        10.10.20.0\/24 is directly connected, GigabitEthernet1\r\nL        10.10.20.2\/32 is directly connected, GigabitEthernet1\r\nC        10.10.30.0\/24 is directly connected, GigabitEthernet2\r\nL        10.10.30.2\/32 is directly connected, GigabitEthernet2\r\nC        10.10.40.0\/24 is directly connected, GigabitEthernet3\r\nL        10.10.40.2\/32 is directly connected, GigabitEthernet3<\/pre>\n
ASAv<\/p>\n
asav01# show route \r\n\r\nCodes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP\r\n       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area \r\n       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2\r\n       E1 - OSPF external type 1, E2 - OSPF external type 2\r\n       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2\r\n       ia - IS-IS inter area, * - candidate default, U - per-user static route\r\n       o - ODR, P - periodic downloaded static route, + - replicated route\r\nGateway of last resort is 192.168.1.1 to network 0.0.0.0\r\n\r\nS*    0.0.0.0 0.0.0.0 [1\/0] via 192.168.1.1, out\r\nO        1.1.1.1 255.255.255.255 [110\/12] via 10.10.20.2, 00:15:18, lan\r\nO        2.2.2.2 255.255.255.255 [110\/12] via 10.10.20.2, 00:15:18, lan\r\nO        3.3.3.3 255.255.255.255 [110\/11] via 10.10.20.2, 00:15:18, lan\r\nC        10.10.20.0 255.255.255.0 is directly connected, lan\r\nL        10.10.20.1 255.255.255.255 is directly connected, lan\r\nO        10.10.30.0 255.255.255.0 [110\/11] via 10.10.20.2, 00:15:18, lan\r\nO        10.10.40.0 255.255.255.0 [110\/11] via 10.10.20.2, 00:15:18, lan\r\nC        192.168.1.0 255.255.255.0 is directly connected, out\r\nL        192.168.1.75 255.255.255.255 is directly connected, out<\/pre>\n
Krok 5<\/h6>\n
Uruchamiamy PIM<\/p>\n
Na ka\u017cdym z router\u00f3w CSR wykonujemy komendy<\/p>\n
ip multicast-routing distributed\r\nip pim bidir-enable\r\nip pim rp-address 3.3.3.3 bidir<\/pre>\n
oraz na ka\u017cdym interfejsie w\u0142\u0105czamy PIM<\/p>\n
interface Loopback0\r\n ip pim sparse-mode<\/pre>\n
interface GigabitEthernet1\r\n ip pim sparse-mode<\/pre>\n
a na CSRv03 dodatkowe na GigabitEthernet 2 i 3<\/p>\n
interface GigabitEthernet2\r\n ip pim sparse-mode\r\ninterface GigabitEthernet3\r\n ip pim sparse-mode<\/pre>\n
sprawdzamy dost\u0119pno\u015b\u0107 s\u0105siedztwo w PIM<\/p>\n
csr1000v01#show ip pim neighbor \r\nPIM Neighbor Table\r\nMode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,\r\n      P - Proxy Capable, S - State Refresh Capable, G - GenID Capable,\r\n      L - DR Load-balancing Capable\r\nNeighbor          Interface                Uptime\/Expires    Ver   DR\r\nAddress                                                            Prio\/Mode\r\n10.10.30.2        GigabitEthernet1         00:07:35\/00:01:32 v2    1 \/ DR B S P G<\/pre>\n
csr1000v02#show ip pim neighbor \r\nPIM Neighbor Table\r\nMode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,\r\n      P - Proxy Capable, S - State Refresh Capable, G - GenID Capable,\r\n      L - DR Load-balancing Capable\r\nNeighbor          Interface                Uptime\/Expires    Ver   DR\r\nAddress                                                            Prio\/Mode\r\n10.10.40.2        GigabitEthernet1         00:00:11\/00:01:32 v2    1 \/ DR B S P G<\/pre>\n
core-csrv03#show ip pim neighbor \r\nPIM Neighbor Table\r\nMode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,\r\n      P - Proxy Capable, S - State Refresh Capable, G - GenID Capable,\r\n      L - DR Load-balancing Capable\r\nNeighbor          Interface                Uptime\/Expires    Ver   DR\r\nAddress                                                            Prio\/Mode\r\n10.10.20.1        GigabitEthernet1         00:09:37\/00:01:42 v2    1 \/ B G\r\n10.10.30.1        GigabitEthernet2         00:09:38\/00:01:28 v2    1 \/ B S P G\r\n10.10.40.1        GigabitEthernet3         00:01:38\/00:01:35 v2    1 \/ B S P G<\/pre>\n
<\/h6>\n
 <\/p>\n
Krok 6<\/h6>\n
Przechodzimy do w\u0142a\u015bciwej konfiguracji w pierwszym etapie b\u0119dziemy konfigurowa\u0107 VXVLAN pomi\u0119dzy CSRv02 i CSRv01 na tych dw\u00f3ch urz\u0105dzeniach b\u0119dziemy wykonywa\u0107 poni\u017csze komendy:<\/p>\n
w pierwszej kolejno\u015bci definiujemy port udp do u\u017cywania w vxvlan jest to konfiguracja opcjonalna wed\u0142ug dokumentacji Cisco.<\/p>\n
vxlan udp port 4444<\/pre>\n
tworzymy interfejs NVE (Network Virtualization Endpoint) gdzie definiujemy:<\/p>\n
vni id jest id VXVLAN mamy du\u017cy wyb\u00f3r od 4096 do 16 milon\u00f3w a dok\u0142adnie w zakresie\u00a04096-16777215<\/p>\n
mcast-group – wybieramy nasz adres multicast dla zdefiniowanego VNI<\/p>\n
interface nve1\r\n no ip address\r\n member vni 6666 mcast-group 239.100.100.100\r\n source-interface Loopback0<\/pre>\n
po wykonaniu powy\u017cszego polecenia mo\u017cemy sprawdzi\u0107 dost\u0119pno\u015b\u0107 peer\u00f3w w nve<\/p>\n
csr1000v01#show nve peers \r\nInterface  Peer-IP          VNI        Peer state   \r\n   nve1    2.2.2.2          6666       -<\/pre>\n
csr1000v02#show nve peers \r\nInterface  Peer-IP          VNI        Peer state   \r\n   nve1    1.1.1.1          6666       -<\/pre>\n
krok 7<\/h6>\n
Konfigurujemy bridge pomi\u0119dzy sieci\u0105 fizyczn\u0105 a sieci\u0105 wirtualn\u0105 czy konfigurujemy port kt\u00f3ry b\u0119dzie mia\u0142 dost\u0119p do vxvlan<\/p>\n
w tej chwili mamy dwie stacje z Windows 7, chcemy aby widzia\u0142y si\u0119 wzajemnie na tym kroku. PC1 ma adres 192.168.220.10 a PC2 192.168.220.20.<\/p>\n
Na tych samych urz\u0105dzeniach co wy\u017cej konfigurowali\u015bmy interfejs NVE, teraz konfigurujemy port GI 2 tak aby by\u0142 untagged<\/p>\n
CSRv01<\/p>\n
interface GigabitEthernet2\r\n description csrv01<-->PC1\r\n no ip address\r\n no sh\r\n service instance 6666 ethernet\r\n  encapsulation untagged\r\nexit\r\nexit\r\n\r\n<\/pre>\n
tworzymy bridge domain – b\u0119dzie nam \u0142\u0105czy\u0107 vxvlan 6666 z portem Gi2<\/p>\n
bridge-domain 6666 \r\n member vni 6666\r\n member GigabitEthernet2 service-instance 6666<\/pre>\n
CSRv02<\/p>\n
interface GigabitEthernet2\r\n description csrv02<-->PC2\r\n no ip address\r\n no sh\r\n service instance 6666 ethernet\r\n  encapsulation untagged\r\nexit\r\nexit<\/pre>\n
tworzymy bridge domain – b\u0119dzie nam \u0142\u0105czy\u0107 vxvlan 6666 z portem Gi2<\/p>\n
bridge-domain 6666 \r\n member vni 6666\r\n member GigabitEthernet2 service-instance 6666<\/pre>\n
po wykonaniu tych krok\u00f3w logujemy si\u0119 na kt\u00f3rego\u015b z PC i starmy si\u0119 pingowa\u0107 drugiego, a na routerach CSRv01 i CSRv02 powinni\u015bmy widzie\u0107 mac adresy w bridge-domain<\/p>\n
csr1000v01#show bridge-domain 6666\r\nBridge-domain 6666 (2 ports in all)\r\nState: UP                    Mac learning: Enabled\r\nAging-Timer: 300 second(s)\r\n    GigabitEthernet2 service instance 6666\r\n    vni 6666\r\n   AED MAC address    Policy  Tag       Age  Pseudoport\r\n   0   000C.29B8.7ABF forward dynamic   289  nve1.VNI6666, VxLAN \r\n                                             src: 1.1.1.1 dst: 2.2.2.2\r\n   0   000C.2990.8ACD forward dynamic   287  GigabitEthernet2.EFP6666<\/pre>\n
csr1000v02#show bridge-domain 6666\r\nBridge-domain 6666 (2 ports in all)\r\nState: UP                    Mac learning: Enabled\r\nAging-Timer: 300 second(s)\r\n    GigabitEthernet2 service instance 6666\r\n    vni 6666\r\n   AED MAC address    Policy  Tag       Age  Pseudoport\r\n   0   000C.29B8.7ABF forward dynamic   252  GigabitEthernet2.EFP6666\r\n   0   000C.2990.8ACD forward dynamic   213  nve1.VNI6666, VxLAN \r\n                                             src: 2.2.2.2 dst: 1.1.1.1<\/pre>\n
Sprawdzamy jak wygl\u0105da status NVE<\/p>\n
csr1000v02#show nve interface nve 1 detail \r\nInterface: nve1, State: Admin Up, Oper Up Encapsulation: Vxlan\r\nsource-interface: Loopback0 (primary:2.2.2.2 vrf:0)\r\n   Pkts In   Bytes In   Pkts Out  Bytes Out\r\n       156      25307         28       3361<\/pre>\n
<\/h6>\n
 <\/p>\n
Krok 8<\/h6>\n
Przysz\u0142a pora na konfiguracj\u0119 Cisco ASAv<\/p>\n
Konfigurujemy port udp dla VXVLAN<\/p>\n
vxlan port 4444\r\n<\/pre>\n
w\u0142\u0105czamy multicast<\/p>\n
multicast-routing<\/pre>\n
Konfigurujemy interfejs NVE<\/p>\n
nve 1\r\n encapsulation vxlan\r\n source-interface lan<\/pre>\n
na interfejsie GigiaEthernet 0\/1 w\u0142\u0105czamy komunikacj\u0119 VXVLN<\/p>\n
interface GigabitEthernet0\/1\r\n nve-only<\/pre>\n
przysz\u0142a pora na konfiguracj\u0119 interfejsu VNI i pod\u0142\u0105czenie do naszego segmentu vxvlan. Nadajemy IP kt\u00f3re b\u0119dzie dla PC1 i PC2 gateway do Internetu.<\/p>\n
interface vni1\r\n segment-id 6666\r\n nameif vxvlan6666\r\n security-level 0\r\n ip address 192.168.200.1 255.255.255.0 \r\n vtep-nve 1\r\n mcast-group 239.100.100.100\r\n no sh\r\n\r\n\r\n<\/pre>\n
po wykonanu tych krok\u00f3w sprawdzamy czy w NVE widzimy nowe s\u0105siedztwo oraz czy w bridge-domain widzimy mac adresy PC1,PC2, oraz GW<\/p>\n
csr1000v01#show nve peers \r\nInterface  Peer-IP          VNI        Peer state   \r\n   nve1    2.2.2.2          6666       -         \r\n   nve1    10.10.20.1       6666       -<\/pre>\n
csr1000v01#show bridge-domain 6666\r\nBridge-domain 6666 (2 ports in all)\r\nState: UP                    Mac learning: Enabled\r\nAging-Timer: 300 second(s)\r\n    GigabitEthernet2 service instance 6666\r\n    vni 6666\r\n   AED MAC address    Policy  Tag       Age  Pseudoport\r\n   0   000C.29B8.7ABF forward dynamic   245  nve1.VNI6666, VxLAN \r\n                                             src: 1.1.1.1 dst: 2.2.2.2\r\n   0   000C.2927.C9A1 forward dynamic   299  nve1.VNI6666, VxLAN \r\n                                             src: 1.1.1.1 dst: 10.10.20.1\r\n   0   000C.2990.8ACD forward dynamic   245  GigabitEthernet2.EFP6666\r\n<\/pre>\n
csr1000v02#show nve peers \r\nInterface  Peer-IP          VNI        Peer state   \r\n   nve1    10.10.20.1       6666       -         \r\n   nve1    1.1.1.1          6666       -         \r\n\r\n\r\n\r\ncsr1000v02#show bridge-domain 6666\r\nBridge-domain 6666 (2 ports in all)\r\nState: UP                    Mac learning: Enabled\r\nAging-Timer: 300 second(s)\r\n    GigabitEthernet2 service instance 6666\r\n    vni 6666\r\n   AED MAC address    Policy  Tag       Age  Pseudoport\r\n   0   000C.29B8.7ABF forward dynamic   300  GigabitEthernet2.EFP6666\r\n   0   000C.2927.C9A1 forward dynamic   300  nve1.VNI6666, VxLAN \r\n                                             src: 2.2.2.2 dst: 10.10.20.1\r\n   0   000C.2990.8ACD forward dynamic   174  nve1.VNI6666, VxLAN \r\n                                             src: 2.2.2.2 dst: 1.1.1.1<\/pre>\n
asav01# show nve 1 summary \r\nnve 1, source-interface \"lan\" is up\r\n Encapsulation: vxlan\r\n Number of configured static peer VTEPs: 0\r\n Number of discovered peer VTEPs: 2\r\n Number of VNIs attached to nve 1: 1<\/pre>\n
asav01# show arp vtep-mapping \r\n        vxvlan6666 192.168.200.20 000c.29b8.7abf 360 2.2.2.2\r\n        vxvlan6666 192.168.200.10 000c.2990.8acd 2154 1.1.1.1<\/pre>\n
Krok 9<\/h6>\n
Konfigurujemy NAT na Cisco ASAv tak aby stacje mog\u0142y dosta\u0107 si\u0119 do Internetu i sprawdzamy dost\u0119p do Neta.<\/p>\n
NAT:<\/p>\n
nat (vxvlan6666,out) source dynamic any interface\r\n<\/pre>\n
ACL’ka<\/p>\n
access-list vxvlan6666_access_in extended permit ip any any<\/pre>\n
ze PC1 lub PC2 sprawdzamy czy mo\u017cemy dosta\u0107 si\u0119 do Internetu<\/p>\n
\"vxvlan01\"<\/a><\/p>\n
 <\/p>\n
Linki:<\/p>\n
MultiCast na Cisco\u00a0<\/a><\/p>\n
Cisco ASA VXLAN<\/a><\/p>\n
Cisco CSR1000v VXVLAN<\/a><\/p>\n
W\u0105tek na CCIE.pl<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Ostatnio uczestniczy\u0142em w ciekawym webbinarium zorganizowane przy forum CCIE.pl pod tytu\u0142em\u00a0DCI „po nowemu” – prezentacj\u0119 prowadzi\u0142\u00a0Piotr Jab\u0142o\u0144ski. Piotr pokazywa\u0142 jak w dzisiejszych czasach mo\u017cna wykorzysta\u0107 technologi\u0119 VXVLAN do rozci\u0105gania L2 pomi\u0119dzy DataCenter lub w samym DC. Po obejrzeniu stwierdzi\u0142em \u017ce trzeba zbudowa\u0107 laba i zobaczy\u0107 z czym si\u0119 to je VXVLAN. Wst\u0119pnie VXVLAN zacz\u0105\u0142em poznawa\u0107 […]<\/p>\n","protected":false},"author":1,"featured_media":319,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"enabled":false},"version":2}},"categories":[4,84,9],"tags":[241,157,209,205,162,204,242,196,197,208,199,87,203,206,201,198,202,200,235,239,195,207],"class_list":["post-693","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cisco","category-lab","category-vmware","tag-asa-vxlan","tag-asav","tag-asav-vxvlan","tag-cisco-asa-vxvlan","tag-cisco-asav","tag-cisco-asav-vxvlan","tag-cisco-csr-vxlan","tag-cisco-csr1000v","tag-csr1000v","tag-csr1kv-vxvlan","tag-how-to-lab-vxvlan","tag-lab","tag-loopback","tag-multicast","tag-ospf","tag-pim","tag-routing","tag-vtep","tag-vxlan","tag-vxlan-multicast","tag-vxvlan","tag-vxvlan-multicast"],"yoast_head":"\nLAB - VXVLAN pierwsze podje\u015bcie - SafeKom Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"LAB - VXVLAN pierwsze podje\u015bcie - SafeKom Blog\" \/>\n<meta property=\"og:description\" content=\"Ostatnio uczestniczy\u0142em w ciekawym webbinarium zorganizowane przy forum CCIE.pl pod tytu\u0142em\u00a0DCI „po nowemu” – prezentacj\u0119 prowadzi\u0142\u00a0Piotr Jab\u0142o\u0144ski. Piotr pokazywa\u0142 jak w dzisiejszych czasach mo\u017cna wykorzysta\u0107 technologi\u0119 VXVLAN do rozci\u0105gania L2 pomi\u0119dzy DataCenter lub w samym DC. Po obejrzeniu stwierdzi\u0142em \u017ce trzeba zbudowa\u0107 laba i zobaczy\u0107 z czym si\u0119 to je VXVLAN. Wst\u0119pnie VXVLAN zacz\u0105\u0142em poznawa\u0107 […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/\" \/>\n<meta property=\"og:site_name\" content=\"SafeKom Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/safekompl\" \/>\n<meta property=\"article:published_time\" content=\"2016-04-03T13:18:51+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2016-04-26T13:41:50+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2015\/09\/cisco-logo.png?fit=400%2C300&ssl=1\" \/>\n\t<meta property=\"og:image:width\" content=\"400\" \/>\n\t<meta property=\"og:image:height\" content=\"300\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Micha\u0142 Iwa\u0144czuk\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@MIwaczuk\" \/>\n<meta name=\"twitter:site\" content=\"@MIwaczuk\" \/>\n<meta name=\"twitter:label1\" content=\"Napisane przez\" \/>\n\t<meta name=\"twitter:data1\" content=\"Micha\u0142 Iwa\u0144czuk\" \/>\n\t<meta name=\"twitter:label2\" content=\"Szacowany czas czytania\" \/>\n\t<meta name=\"twitter:data2\" content=\"11 minut\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/\"},\"author\":{\"name\":\"Micha\u0142 Iwa\u0144czuk\",\"@id\":\"https:\/\/www.safekom.pl\/blog\/#\/schema\/person\/fd4cc931b624af4b7353d36d92ba7181\"},\"headline\":\"LAB – VXVLAN pierwsze podje\u015bcie\",\"datePublished\":\"2016-04-03T13:18:51+00:00\",\"dateModified\":\"2016-04-26T13:41:50+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/\"},\"wordCount\":851,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/www.safekom.pl\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2015\/09\/cisco-logo.png?fit=400%2C300&ssl=1\",\"keywords\":[\"asa vxlan\",\"asav\",\"asav vxvlan\",\"cisco asa vxvlan\",\"cisco asav\",\"cisco asav vxvlan\",\"cisco csr vxlan\",\"Cisco CSR1000v\",\"CSR1000v\",\"csr1kv vxvlan\",\"how to lab vxvlan\",\"lab\",\"loopback\",\"multicast\",\"ospf\",\"pim\",\"routing\",\"vtep\",\"vxlan\",\"vxlan multicast\",\"vxvlan\",\"vxvlan multicast\"],\"articleSection\":[\"Cisco\",\"Lab\",\"Vmware\"],\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/\",\"url\":\"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/\",\"name\":\"LAB - VXVLAN pierwsze podje\u015bcie - SafeKom Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.safekom.pl\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2015\/09\/cisco-logo.png?fit=400%2C300&ssl=1\",\"datePublished\":\"2016-04-03T13:18:51+00:00\",\"dateModified\":\"2016-04-26T13:41:50+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/#primaryimage\",\"url\":\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2015\/09\/cisco-logo.png?fit=400%2C300&ssl=1\",\"contentUrl\":\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2015\/09\/cisco-logo.png?fit=400%2C300&ssl=1\",\"width\":400,\"height\":300},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Strona g\u0142\u00f3wna\",\"item\":\"https:\/\/www.safekom.pl\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"LAB – VXVLAN pierwsze podje\u015bcie\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.safekom.pl\/blog\/#website\",\"url\":\"https:\/\/www.safekom.pl\/blog\/\",\"name\":\"SafeKom Blog\",\"description\":\"Notatki Architekta i in\u017cyniera zwi\u0105zanego rozwi\u0105zaniami on-prem\",\"publisher\":{\"@id\":\"https:\/\/www.safekom.pl\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.safekom.pl\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pl-PL\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.safekom.pl\/blog\/#organization\",\"name\":\"SafeKom Blog\",\"url\":\"https:\/\/www.safekom.pl\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/www.safekom.pl\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2015\/05\/cropped-logo.png?fit=512%2C512&ssl=1\",\"contentUrl\":\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2015\/05\/cropped-logo.png?fit=512%2C512&ssl=1\",\"width\":512,\"height\":512,\"caption\":\"SafeKom Blog\"},\"image\":{\"@id\":\"https:\/\/www.safekom.pl\/blog\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/safekompl\",\"https:\/\/x.com\/MIwaczuk\",\"https:\/\/www.linkedin.com\/in\/michaliwanczuk\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.safekom.pl\/blog\/#\/schema\/person\/fd4cc931b624af4b7353d36d92ba7181\",\"name\":\"Micha\u0142 Iwa\u0144czuk\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/www.safekom.pl\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/cc6dda4ee8d21d1f254147e5ee6f5e38881b88a4a12a5774ca42380597e52014?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/cc6dda4ee8d21d1f254147e5ee6f5e38881b88a4a12a5774ca42380597e52014?s=96&d=mm&r=g\",\"caption\":\"Micha\u0142 Iwa\u0144czuk\"},\"description\":\"Pasjonat komputerowy od zawsze oraz maniak w zakresie sieci, wirtualizacji oraz bezpiecze\u0144stwa IT. Kompetentny in\u017cynier z du\u017cym do\u015bwiadczeniem w realizacji projekt\u00f3w informatycznych i telekomunikacyjnych. Wieloletni administrator IT, kt\u00f3ry utrzymuje systemy informatyczne dostosowuj\u0105c je do wymog\u00f3w biznesowych z zapewnieniem dost\u0119pno\u015bci 24\/7\/365.\",\"url\":\"https:\/\/www.safekom.pl\/blog\/author\/admin\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"LAB - VXVLAN pierwsze podje\u015bcie - SafeKom Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/","og_locale":"pl_PL","og_type":"article","og_title":"LAB - VXVLAN pierwsze podje\u015bcie - SafeKom Blog","og_description":"Ostatnio uczestniczy\u0142em w ciekawym webbinarium zorganizowane przy forum CCIE.pl pod tytu\u0142em\u00a0DCI „po nowemu” – prezentacj\u0119 prowadzi\u0142\u00a0Piotr Jab\u0142o\u0144ski. Piotr pokazywa\u0142 jak w dzisiejszych czasach mo\u017cna wykorzysta\u0107 technologi\u0119 VXVLAN do rozci\u0105gania L2 pomi\u0119dzy DataCenter lub w samym DC. Po obejrzeniu stwierdzi\u0142em \u017ce trzeba zbudowa\u0107 laba i zobaczy\u0107 z czym si\u0119 to je VXVLAN. Wst\u0119pnie VXVLAN zacz\u0105\u0142em poznawa\u0107 […]","og_url":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/","og_site_name":"SafeKom Blog","article_publisher":"https:\/\/www.facebook.com\/safekompl","article_published_time":"2016-04-03T13:18:51+00:00","article_modified_time":"2016-04-26T13:41:50+00:00","og_image":[{"width":400,"height":300,"url":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2015\/09\/cisco-logo.png?fit=400%2C300&ssl=1","type":"image\/png"}],"author":"Micha\u0142 Iwa\u0144czuk","twitter_card":"summary_large_image","twitter_creator":"@MIwaczuk","twitter_site":"@MIwaczuk","twitter_misc":{"Napisane przez":"Micha\u0142 Iwa\u0144czuk","Szacowany czas czytania":"11 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/#article","isPartOf":{"@id":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/"},"author":{"name":"Micha\u0142 Iwa\u0144czuk","@id":"https:\/\/www.safekom.pl\/blog\/#\/schema\/person\/fd4cc931b624af4b7353d36d92ba7181"},"headline":"LAB – VXVLAN pierwsze podje\u015bcie","datePublished":"2016-04-03T13:18:51+00:00","dateModified":"2016-04-26T13:41:50+00:00","mainEntityOfPage":{"@id":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/"},"wordCount":851,"commentCount":0,"publisher":{"@id":"https:\/\/www.safekom.pl\/blog\/#organization"},"image":{"@id":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/#primaryimage"},"thumbnailUrl":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2015\/09\/cisco-logo.png?fit=400%2C300&ssl=1","keywords":["asa vxlan","asav","asav vxvlan","cisco asa vxvlan","cisco asav","cisco asav vxvlan","cisco csr vxlan","Cisco CSR1000v","CSR1000v","csr1kv vxvlan","how to lab vxvlan","lab","loopback","multicast","ospf","pim","routing","vtep","vxlan","vxlan multicast","vxvlan","vxvlan multicast"],"articleSection":["Cisco","Lab","Vmware"],"inLanguage":"pl-PL","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/","url":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/","name":"LAB - VXVLAN pierwsze podje\u015bcie - SafeKom Blog","isPartOf":{"@id":"https:\/\/www.safekom.pl\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/#primaryimage"},"image":{"@id":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/#primaryimage"},"thumbnailUrl":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2015\/09\/cisco-logo.png?fit=400%2C300&ssl=1","datePublished":"2016-04-03T13:18:51+00:00","dateModified":"2016-04-26T13:41:50+00:00","breadcrumb":{"@id":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/"]}]},{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/#primaryimage","url":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2015\/09\/cisco-logo.png?fit=400%2C300&ssl=1","contentUrl":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2015\/09\/cisco-logo.png?fit=400%2C300&ssl=1","width":400,"height":300},{"@type":"BreadcrumbList","@id":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Strona g\u0142\u00f3wna","item":"https:\/\/www.safekom.pl\/blog\/"},{"@type":"ListItem","position":2,"name":"LAB – VXVLAN pierwsze podje\u015bcie"}]},{"@type":"WebSite","@id":"https:\/\/www.safekom.pl\/blog\/#website","url":"https:\/\/www.safekom.pl\/blog\/","name":"SafeKom Blog","description":"Notatki Architekta i in\u017cyniera zwi\u0105zanego rozwi\u0105zaniami on-prem","publisher":{"@id":"https:\/\/www.safekom.pl\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.safekom.pl\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pl-PL"},{"@type":"Organization","@id":"https:\/\/www.safekom.pl\/blog\/#organization","name":"SafeKom Blog","url":"https:\/\/www.safekom.pl\/blog\/","logo":{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/www.safekom.pl\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2015\/05\/cropped-logo.png?fit=512%2C512&ssl=1","contentUrl":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2015\/05\/cropped-logo.png?fit=512%2C512&ssl=1","width":512,"height":512,"caption":"SafeKom Blog"},"image":{"@id":"https:\/\/www.safekom.pl\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/safekompl","https:\/\/x.com\/MIwaczuk","https:\/\/www.linkedin.com\/in\/michaliwanczuk\/"]},{"@type":"Person","@id":"https:\/\/www.safekom.pl\/blog\/#\/schema\/person\/fd4cc931b624af4b7353d36d92ba7181","name":"Micha\u0142 Iwa\u0144czuk","image":{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/www.safekom.pl\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/cc6dda4ee8d21d1f254147e5ee6f5e38881b88a4a12a5774ca42380597e52014?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/cc6dda4ee8d21d1f254147e5ee6f5e38881b88a4a12a5774ca42380597e52014?s=96&d=mm&r=g","caption":"Micha\u0142 Iwa\u0144czuk"},"description":"Pasjonat komputerowy od zawsze oraz maniak w zakresie sieci, wirtualizacji oraz bezpiecze\u0144stwa IT. Kompetentny in\u017cynier z du\u017cym do\u015bwiadczeniem w realizacji projekt\u00f3w informatycznych i telekomunikacyjnych. Wieloletni administrator IT, kt\u00f3ry utrzymuje systemy informatyczne dostosowuj\u0105c je do wymog\u00f3w biznesowych z zapewnieniem dost\u0119pno\u015bci 24\/7\/365.","url":"https:\/\/www.safekom.pl\/blog\/author\/admin\/"}]}},"jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2015\/09\/cisco-logo.png?fit=400%2C300&ssl=1","jetpack_shortlink":"https:\/\/wp.me\/p7i9ri-bb","jetpack-related-posts":[{"id":782,"url":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/","url_meta":{"origin":693,"position":0},"title":"LAB vxlan – Juniper vMX i Cisco CSR1kv oraz ASAv","author":"Micha\u0142 Iwa\u0144czuk","date":"26.04.2016","format":false,"excerpt":"Po pierwszym wpisie o VxLAN, gdzie opar\u0142em si\u0119 wy\u0142\u0105cznie na Cisco CSRv oraz ASAv przysz\u0142a pora na testowanie w konfiguracji multivendor. Do tego laba wykorzysta\u0142em: Cisco CSRv Cisco ASAv Juniper vMX Wszystko zosta\u0142o uruchomione na Vmware Workstation. W dobie wirtualizacji serwer\u00f3w i desktop\u00f3w postanowi\u0142em wzi\u0105\u0107 si\u0119 ostro za poznanie \u015bwiata\u2026","rel":"","context":"In "Cisco"","block_context":{"text":"Cisco","link":"https:\/\/www.safekom.pl\/blog\/category\/cisco\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/02\/Juniper-Networks-and-Cisco-Systems.png?fit=712%2C534&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/02\/Juniper-Networks-and-Cisco-Systems.png?fit=712%2C534&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/02\/Juniper-Networks-and-Cisco-Systems.png?fit=712%2C534&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/02\/Juniper-Networks-and-Cisco-Systems.png?fit=712%2C534&ssl=1&resize=700%2C400 2x"},"classes":[]},{"id":610,"url":"https:\/\/www.safekom.pl\/blog\/cisco\/asav-pierwsze-uruchomienie-w-labie\/","url_meta":{"origin":693,"position":1},"title":"ASAv – pierwsze uruchomienie w labie","author":"Micha\u0142 Iwa\u0144czuk","date":"06.03.2016","format":false,"excerpt":"Pierwsze uruchomienie Cisco ASAv w Labie. Pokazuj\u0119 podstawow\u0105 konfiguracj\u0119 od importu po zalogowanie si\u0119 po ssh lub asdm.","rel":"","context":"In "Cisco"","block_context":{"text":"Cisco","link":"https:\/\/www.safekom.pl\/blog\/category\/cisco\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2015\/09\/cisco-logo.png?fit=400%2C300&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]},{"id":624,"url":"https:\/\/www.safekom.pl\/blog\/cisco\/asav-activestandby-konfiguracja-minimalna\/","url_meta":{"origin":693,"position":2},"title":"ASAv – Active\/Standby konfiguracja – minimalna","author":"Micha\u0142 Iwa\u0144czuk","date":"09.03.2016","format":false,"excerpt":"Witam, wcze\u015bniej napisa\u0142em jak w labie postawi\u0107 Cisco ASAv, dzi\u015b poka\u017c\u0119 jak szybko i bez problem\u00f3w skonfigurowa\u0107 dwie wirtualki w trybie failover A\/P - jedyny tryb kt\u00f3ry obs\u0142uguje na chwil\u0119 obecn\u0105. Rysunek pogl\u0105dowy: Za\u0142o\u017cenia konfiguracyjne: Interfejs Praimary Secondary zona GigabitEthernet 0\/0 192.168.1.80 192.168.1.81 NET_LAB GigabitEthernet 0\/1 172.16.1.1 172.16.1.2 LAN GigabitEthernet\u2026","rel":"","context":"In "Cisco"","block_context":{"text":"Cisco","link":"https:\/\/www.safekom.pl\/blog\/category\/cisco\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2015\/09\/cisco-logo.png?fit=400%2C300&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]},{"id":908,"url":"https:\/\/www.safekom.pl\/blog\/vmware\/home-lab-wstep\/","url_meta":{"origin":693,"position":3},"title":"Home Lab – wst\u0119p","author":"Micha\u0142 Iwa\u0144czuk","date":"10.06.2016","format":false,"excerpt":"Przyszed\u0142 dzie\u0144, w kt\u00f3rym trzeba sko\u0144czy\u0107 budowa\u0107 m\u00f3j domowy lab. W tej chwili mocno na tapecie mam NSX oraz VxLAN. Na mym laptopie ju\u017c wi\u0119cej nie upcham wirtualnych maszyn, przyszed\u0142 czas na z\u0142o\u017cenie porz\u0105dnego Laba. Tym wpisem rozpoczn\u0119 seri\u0119 od budowania po testowanie rozwi\u0105za\u0144 Vmware. Sprz\u0119t do Laba: Serwer fizyczny:\u2026","rel":"","context":"In "Lab"","block_context":{"text":"Lab","link":"https:\/\/www.safekom.pl\/blog\/en\/category\/lab\/"},"img":{"alt_text":"home_lab01","src":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/06\/home_lab01.png?resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/06\/home_lab01.png?resize=350%2C200 1x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/06\/home_lab01.png?resize=525%2C300 1.5x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/06\/home_lab01.png?resize=700%2C400 2x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/06\/home_lab01.png?resize=1050%2C600 3x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/06\/home_lab01.png?resize=1400%2C800 4x"},"classes":[]},{"id":1433,"url":"https:\/\/www.safekom.pl\/blog\/vmware\/home-lab-nsx-6-2-4-logical-switches\/","url_meta":{"origin":693,"position":4},"title":"Home Lab – NSX 6.2.4 Logical Switches","author":"Micha\u0142 Iwa\u0144czuk","date":"14.11.2016","format":false,"excerpt":"Przyszed\u0142 dzi\u015b czas aby skupi\u0107 si\u0119 na tworzeniu sieci kt\u00f3re b\u0119d\u0105 zarz\u0105dzane z poziomu NSX'a. Stworzymy Logical Switches kt\u00f3re b\u0119d\u0105 naszymi sieciami L2 w \u015brodowisku Vmware, a komunikacja pomi\u0119dzy hostami b\u0119dzie przenoszona za pomoc\u0105 VXLAN, tzw. transportem kt\u00f3ry stworzyli\u015bmy w poprzednim wpisie. Logujemy si\u0119 do naszego vCenter przechodzimy do modu\u0142u\u2026","rel":"","context":"In "Lab"","block_context":{"text":"Lab","link":"https:\/\/www.safekom.pl\/blog\/en\/category\/lab\/"},"img":{"alt_text":"ls_01","src":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/11\/ls_01.png?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":1415,"url":"https:\/\/www.safekom.pl\/blog\/vmware\/home-lab-nsx-6-2-4-tworzenie-nsx-controller-oraz-przygotowanie-hostow\/","url_meta":{"origin":693,"position":5},"title":"Home Lab – NSX 6.2.4 tworzenie NSX Controller oraz przygotowanie host\u00f3w","author":"Micha\u0142 Iwa\u0144czuk","date":"10.11.2016","format":false,"excerpt":"We wcze\u015bniejszym wpisie pokaza\u0142em jak zainstalowa\u0107 NSX Managera, dzi\u015b skupimy si\u0119 na instalowaniu NSX Controler. NSX Controller Co to jest ten Controler NSX - w skr\u00f3cie mo\u017cna go por\u00f3wna\u0107 do Control Plane kt\u00f3ry mo\u017cemy znale\u017a\u0107 w fizycznym urz\u0105dzeniu. Przechodzimy do dzia\u0142a\u0144, przepraszam za ba\u0142agan ale podczas instalacji napotka\u0142em si\u0119 na\u2026","rel":"","context":"In "Lab"","block_context":{"text":"Lab","link":"https:\/\/www.safekom.pl\/blog\/en\/category\/lab\/"},"img":{"alt_text":"nsx_con01","src":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/11\/nsx_con01.png?resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/11\/nsx_con01.png?resize=350%2C200 1x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/11\/nsx_con01.png?resize=525%2C300 1.5x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/11\/nsx_con01.png?resize=700%2C400 2x"},"classes":[]}],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.safekom.pl\/blog\/wp-json\/wp\/v2\/posts\/693","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.safekom.pl\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.safekom.pl\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.safekom.pl\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.safekom.pl\/blog\/wp-json\/wp\/v2\/comments?post=693"}],"version-history":[{"count":0,"href":"https:\/\/www.safekom.pl\/blog\/wp-json\/wp\/v2\/posts\/693\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.safekom.pl\/blog\/wp-json\/wp\/v2\/media\/319"}],"wp:attachment":[{"href":"https:\/\/www.safekom.pl\/blog\/wp-json\/wp\/v2\/media?parent=693"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.safekom.pl\/blog\/wp-json\/wp\/v2\/categories?post=693"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.safekom.pl\/blog\/wp-json\/wp\/v2\/tags?post=693"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}