{"id":782,"date":"2016-04-26T17:07:05","date_gmt":"2016-04-26T16:07:05","guid":{"rendered":"http:\/\/www.safekom.pl\/blog\/?p=782"},"modified":"2016-06-24T14:08:18","modified_gmt":"2016-06-24T13:08:18","slug":"lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav","status":"publish","type":"post","link":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/","title":{"rendered":"LAB vxlan &#8211; Juniper vMX i Cisco CSR1kv oraz ASAv"},"content":{"rendered":"<p>Po pierwszym wpisie o <a href=\"http:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/\">VxLAN<\/a>, gdzie opar\u0142em si\u0119 wy\u0142\u0105cznie na Cisco CSRv oraz ASAv przysz\u0142a pora na testowanie w konfiguracji multivendor.<br \/>\nDo tego laba wykorzysta\u0142em:<\/p>\n<ul>\n<li>Cisco CSRv<\/li>\n<li>Cisco ASAv<\/li>\n<li>Juniper vMX<\/li>\n<\/ul>\n<p>Wszystko zosta\u0142o uruchomione na Vmware Workstation.<\/p>\n<p>W dobie wirtualizacji serwer\u00f3w i desktop\u00f3w postanowi\u0142em wzi\u0105\u0107 si\u0119 ostro za poznanie \u015bwiata wirtualizacji networku\u00a0tym bardziej kiedy coraz cz\u0119\u015bciej\u00a0s\u0142yszy si\u0119 has\u0142o vxlan.<br \/>\nPostanowi\u0142em sprawdzi\u0107 jak wygl\u0105da konfiguracja na\u00a0&#8222;sprz\u0119cie&#8221;.<br \/>\nNast\u0119pnym etapem b\u0119dzie integracja tego co robi\u0119 na urz\u0105dzeniach sieciowych w po\u0142\u0105czeniu ze \u015bwiatem wirtualnym ale\u00a0o tym p\u00f3\u017aniej&#8230;<\/p>\n<p>Konfiguracja oraz poznanie tej technologii by\u0142o dla mnie\u00a0najbardziej czasoch\u0142onnym zaj\u0119ciem do tej pory ale dla tych\u00a0co te\u017c chc\u0105 walczy\u0107 z poznaniem vxlan zostawiam swoj\u0105 notatk\u0119 w postaci wpisu.<\/p>\n<p>Opr\u00f3cz samej technologi vxlan porusz\u0119 tu zaganiania takie jak: BGP, OSPF, MPLS, Multicast. Dzi\u0119ki takim labom cz\u0142owiek przypomina sobie ww technologie oraz nadrabia braki.<\/p>\n<p>Zapraszam do lektury.<\/p>\n<h3>Lab<\/h3>\n<p>Poni\u017cej schemat pogl\u0105dowy Laba.<\/p>\n<p>&nbsp;<\/p>\n<p><a href=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/evpn.png\"><img data-recalc-dims=\"1\" loading=\"lazy\" decoding=\"async\" data-attachment-id=\"828\" data-permalink=\"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/attachment\/evpn\/\" data-orig-file=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/evpn.png?fit=1142%2C948&amp;ssl=1\" data-orig-size=\"1142,948\" data-comments-opened=\"0\" data-image-meta=\"{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;}\" data-image-title=\"evpn\" data-image-description=\"\" data-image-caption=\"\" data-large-file=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/evpn.png?fit=770%2C639&amp;ssl=1\" class=\"alignnone size-full wp-image-828\" src=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/evpn.png?resize=770%2C639\" alt=\"evpn\" width=\"770\" height=\"639\" srcset=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/evpn.png?w=1142&amp;ssl=1 1142w, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/evpn.png?resize=300%2C249&amp;ssl=1 300w, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/evpn.png?resize=768%2C638&amp;ssl=1 768w, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/evpn.png?resize=1024%2C850&amp;ssl=1 1024w\" sizes=\"auto, (max-width: 770px) 100vw, 770px\" \/><\/a><\/p>\n<p>Jak wida\u0107 na powy\u017cszym schemacie mamy trzy vtep&#8217;y i Cisco CSRv, kt\u00f3re wykorzystuje jako Core spinaj\u0105ce wszystko.<\/p>\n<p>Teraz przechodzimy do fajniejszych rzeczy czyli do konfiguracji.<\/p>\n<h4>Konfiguracja interfejs\u00f3w sieciowych na urz\u0105dzeniach:<\/h4>\n<h6>Cisco ASA &#8211; \u00a0asav01<\/h6>\n<pre class=\"lang:sh decode:true\">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<pre class=\"lang:sh decode:true \">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<\/pre>\n<h6>Cisco CSR &#8211; csrv03<\/h6>\n<pre class=\"lang:sh decode:true \">interface Loopback0\r\n ip address 3.3.3.3 255.255.255.255<\/pre>\n<pre class=\"lang:sh decode:true\">interface GigabitEthernet1\r\n ip address 10.10.20.2 255.255.255.0\r\n negotiation auto\r\n description \"CSRv03 -- asav01 gi 0\/1\"\r\n no sh\r\n<\/pre>\n<pre class=\"lang:sh decode:true\">interface GigabitEthernet2\r\n ip address 10.10.30.2 255.255.255.0\r\n negotiation auto\r\n no sh<\/pre>\n<pre class=\"lang:sh decode:true\">interface GigabitEthernet3\r\n ip address 10.10.40.2 255.255.255.0\r\n negotiation auto\r\n no sh<\/pre>\n<h6>Juniper vMX &#8211; vmx01<\/h6>\n<pre class=\"lang:sh decode:true\">set interfaces ge-0\/0\/1 description \"vmx01 -- csrv03 GI2\"\r\nset interfaces ge-0\/0\/1 unit 0 family inet address 10.10.30.10\/24<\/pre>\n<pre class=\"lang:sh decode:true \">set interfaces ge-0\/0\/4 unit 0 family inet address 10.120.10.1\/24\r\nset interfaces ge-0\/0\/4 description \"vmx01 --- vtep01 gi 2\"<\/pre>\n<h6>Juniper vMX &#8211; vmx02<\/h6>\n<pre class=\"lang:sh decode:true \">set interfaces ge-0\/0\/1 unit 0 family inet address 10.10.40.10\/24\r\nset interfaces ge-0\/0\/1 description \"vmx02 -- csrv03 GI3\"<\/pre>\n<pre class=\"lang:sh decode:true \">set interfaces ge-0\/0\/4 unit 0 family inet address 10.130.10.1\/24\r\nset interfaces ge-0\/0\/4 description \"vmx02 -- vtep GI0\/2\"<\/pre>\n<h6>Cisco ASAv &#8211; vtep01<\/h6>\n<p>Rysunek szczeg\u00f3\u0142owy dla po\u0142\u0105cze\u0144 vtep01 do vmx01<\/p>\n<p><a href=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/vmx01_1.png\"><img data-recalc-dims=\"1\" loading=\"lazy\" decoding=\"async\" data-attachment-id=\"832\" data-permalink=\"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/attachment\/vmx01_1\/\" data-orig-file=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/vmx01_1.png?fit=523%2C566&amp;ssl=1\" data-orig-size=\"523,566\" data-comments-opened=\"0\" data-image-meta=\"{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;}\" data-image-title=\"vmx01_1\" data-image-description=\"\" data-image-caption=\"\" data-large-file=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/vmx01_1.png?fit=523%2C566&amp;ssl=1\" class=\"alignnone wp-image-832\" src=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/vmx01_1.png?resize=308%2C333\" alt=\"vmx01_1\" width=\"308\" height=\"333\" srcset=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/vmx01_1.png?w=523&amp;ssl=1 523w, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/vmx01_1.png?resize=277%2C300&amp;ssl=1 277w\" sizes=\"auto, (max-width: 308px) 100vw, 308px\" \/><\/a><\/p>\n<pre class=\"lang:sh decode:true\">interface GigabitEthernet0\/0.100\r\n vlan 100\r\n nameif lan\r\n security-level 0\r\n ip address 192.168.200.10 255.255.255.0 \r\n no sh<\/pre>\n<pre class=\"lang:sh decode:true \">interface GigabitEthernet0\/2\r\n nameif lan120\r\n security-level 0\r\n ip address 10.120.10.10 255.255.255.0\r\n no sh<\/pre>\n<h6>Cisco ASAv &#8211; vtep02<\/h6>\n<p>Rysunek szczeg\u00f3\u0142owy dla po\u0142\u0105cze\u0144 vtep02 do vmx02<\/p>\n<p><a href=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/vmx02_1.png\"><img data-recalc-dims=\"1\" loading=\"lazy\" decoding=\"async\" data-attachment-id=\"831\" data-permalink=\"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/attachment\/vmx02_1\/\" data-orig-file=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/vmx02_1.png?fit=530%2C566&amp;ssl=1\" data-orig-size=\"530,566\" data-comments-opened=\"0\" data-image-meta=\"{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;}\" data-image-title=\"vmx02_1\" data-image-description=\"\" data-image-caption=\"\" data-large-file=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/vmx02_1.png?fit=530%2C566&amp;ssl=1\" class=\"alignnone wp-image-831\" src=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/vmx02_1.png?resize=296%2C316\" alt=\"vmx02_1\" width=\"296\" height=\"316\" srcset=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/vmx02_1.png?w=530&amp;ssl=1 530w, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/vmx02_1.png?resize=281%2C300&amp;ssl=1 281w\" sizes=\"auto, (max-width: 296px) 100vw, 296px\" \/><\/a><\/p>\n<pre class=\"lang:sh decode:true \">interface GigabitEthernet0\/0.100\r\n vlan 100\r\n nameif lan\r\n security-level 0\r\n ip address 192.168.200.110 255.255.255.0 \r\n no sh<\/pre>\n<pre class=\"lang:sh decode:true \">interface GigabitEthernet0\/2\r\n nve-only\r\n nameif vlan130\r\n security-level 0\r\n ip address 10.130.10.10 255.255.255.0\r\n no sh<\/pre>\n<h4>Konfiguracja OSPF<\/h4>\n<p>W tym kroku konfigurujemy routing dynamiczny z wykorzystaniem OSPF. Urz\u0105dzenia vmx01 oraz vmx02 b\u0119d\u0105 skonfigurowane w dw\u00f3ch obszarach ospf.<\/p>\n<h6>Cisco ASA &#8211; \u00a0asav01<\/h6>\n<pre class=\"lang:sh decode:true \">router ospf 1\r\n network 10.10.20.0 255.255.255.0 area 0<\/pre>\n<h6>Cisco CSR &#8211; csrv03<\/h6>\n<pre class=\"lang:sh decode:true\">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<h6>Juniper vMX &#8211; vmx01<\/h6>\n<pre class=\"lang:sh decode:true\">set protocols ospf area 0.0.0.0 interface lo0.0\r\nset protocols ospf area 0.0.0.0 interface ge-0\/0\/1.0\r\nset protocols ospf area 0.0.0.1 nssa summaries\r\nset protocols ospf area 0.0.0.1 interface ge-0\/0\/4.0\r\n<\/pre>\n<h6>Juniper vMX &#8211; vmx02<\/h6>\n<pre class=\"lang:sh decode:true\">set protocols ospf area 0.0.0.0 interface lo0.0\r\nset protocols ospf area 0.0.0.0 interface ge-0\/0\/1.0\r\nset protocols ospf area 0.0.0.1 nssa summaries\r\nset protocols ospf area 0.0.0.1 interface ge-0\/0\/4.0\r\n<\/pre>\n<h6>Cisco ASAv &#8211; vtep01<\/h6>\n<pre class=\"lang:sh decode:true \">router ospf 1\r\n network 10.120.10.0 255.255.255.0 area 1\r\n area 1 nssa<\/pre>\n<h6>Cisco ASAv &#8211; vtep02<\/h6>\n<pre class=\"lang:sh decode:true \">router ospf 1\r\n network 10.130.10.0 255.255.255.0 area 1\r\n area 1 nssa<\/pre>\n<h4>Weryfikacja OSPF<\/h4>\n<h6>Juniper vMX &#8211; vmx01<\/h6>\n<pre class=\"lang:sh decode:true \">root@vMX01&gt; show ospf neighbor \r\nAddress          Interface              State     ID               Pri  Dead\r\n10.10.30.2       ge-0\/0\/1.0             Full      3.3.3.3            1    34\r\n10.120.10.10     ge-0\/0\/4.0             Full      192.168.200.10     1    36\r\n<\/pre>\n<pre class=\"lang:sh decode:true \">root@vMX01&gt; show ospf database \r\n\r\n    OSPF database, Area 0.0.0.0\r\n Type       ID               Adv Rtr           Seq      Age  Opt  Cksum  Len \r\nRouter  *1.1.1.1          1.1.1.1          0x80000451   283  0x22 0x72dc  48\r\nRouter   2.2.2.2          2.2.2.2          0x80000722  1306  0x22 0xaab0  48\r\nRouter   3.3.3.3          3.3.3.3          0x80000a26  1855  0x22 0x19f   72\r\nNetwork  10.10.30.2       3.3.3.3          0x80000148  1118  0x22 0xf1af  32\r\nNetwork  10.10.40.2       3.3.3.3          0x800001df  1850  0x22 0x8675  32\r\nSummary *10.120.10.0      1.1.1.1          0x800002ee  1810  0x22 0xfcbe  28\r\nSummary  10.130.10.0      2.2.2.2          0x80000439  1850  0x22 0xcb95  28\r\n\r\n    OSPF database, Area 0.0.0.1\r\n Type       ID               Adv Rtr           Seq      Age  Opt  Cksum  Len \r\nRouter  *1.1.1.1          1.1.1.1          0x800002a2  2096  0x20 0xea77  36\r\nRouter   192.168.200.10   192.168.200.10   0x800002e2  1109  0x28 0xd9c0  36\r\nNetwork  10.120.10.10     192.168.200.10   0x8000025a  1109  0x28 0xfbc9  32\r\nSummary *1.1.1.1          1.1.1.1          0x80000123   577  0x20 0x14ff  28\r\nSummary *2.2.2.2          1.1.1.1          0x80000001  1848  0x20 0x41ef  28\r\nSummary *3.3.3.3          1.1.1.1          0x8000000d  1460  0x20 0xfa26  28\r\nSummary *10.10.20.0       1.1.1.1          0x8000000d  1166  0x20 0xad57  28\r\nSummary *10.10.30.0       1.1.1.1          0x800002b2   871  0x20 0xe370  28\r\nSummary *10.10.40.0       1.1.1.1          0x80000014  1848  0x20 0xc227  28\r\nSummary *10.130.10.0      1.1.1.1          0x80000001  1848  0x20 0x9809  28\r\n<\/pre>\n<pre class=\"lang:sh decode:true \">root@vMX01&gt; show route protocol ospf   \r\n\r\ninet.0: 21 destinations, 22 routes (21 active, 0 holddown, 0 hidden)\r\n+ = Active Route, - = Last Active, * = Both\r\n\r\n2.2.2.2\/32         *[OSPF\/10] 00:31:21, metric 2\r\n                    &gt; to 10.10.30.2 via ge-0\/0\/1.0\r\n3.3.3.3\/32         *[OSPF\/10] 00:52:07, metric 2\r\n                    &gt; to 10.10.30.2 via ge-0\/0\/1.0\r\n10.10.20.0\/24      *[OSPF\/10] 00:52:07, metric 2\r\n                    &gt; to 10.10.30.2 via ge-0\/0\/1.0\r\n10.10.40.0\/24      *[OSPF\/10] 00:31:21, metric 2\r\n                    &gt; to 10.10.30.2 via ge-0\/0\/1.0\r\n10.130.10.0\/24     *[OSPF\/10] 00:31:21, metric 3\r\n                    &gt; to 10.10.30.2 via ge-0\/0\/1.0\r\n224.0.0.5\/32       *[OSPF\/10] 5d 20:04:48, metric 1\r\n                      MultiRecv\r\n<\/pre>\n<h6>Juniper vMX &#8211; vmx02<\/h6>\n<pre class=\"lang:sh decode:true \">root@vMX02&gt; show ospf neighbor \r\nAddress          Interface              State     ID               Pri  Dead\r\n10.10.40.2       ge-0\/0\/1.0             Full      3.3.3.3            1    38\r\n10.130.10.10     ge-0\/0\/4.0             Full      192.168.200.110    1    34\r\n<\/pre>\n<pre class=\"lang:sh decode:true \">root@vMX02&gt; show ospf database \r\n\r\n    OSPF database, Area 0.0.0.0\r\n Type       ID               Adv Rtr           Seq      Age  Opt  Cksum  Len \r\nRouter   1.1.1.1          1.1.1.1          0x80000451   430  0x22 0x72dc  48\r\nRouter  *2.2.2.2          2.2.2.2          0x80000722  1460  0x22 0xaab0  48\r\nRouter   3.3.3.3          3.3.3.3          0x80000a26  2016  0x22 0x19f   72\r\nNetwork  10.10.30.2       3.3.3.3          0x80000148  1272  0x22 0xf1af  32\r\nNetwork  10.10.40.2       3.3.3.3          0x800001df  2012  0x22 0x8675  32\r\nSummary  10.120.10.0      1.1.1.1          0x800002ee  1973  0x22 0xfcbe  28\r\nSummary *10.130.10.0      2.2.2.2          0x80000439  2009  0x22 0xcb95  28\r\n\r\n    OSPF database, Area 0.0.0.1\r\n Type       ID               Adv Rtr           Seq      Age  Opt  Cksum  Len \r\nRouter  *2.2.2.2          2.2.2.2          0x80000393  1188  0x22 0x64ed  36\r\nRouter   192.168.200.110  192.168.200.110  0x80000492    66  0x22 0x51c0  36\r\nNetwork  10.130.10.10     192.168.200.110  0x8000032a    66  0x22 0xfe25  32\r\nSummary *1.1.1.1          2.2.2.2          0x80000003   915  0x22 0x2ffd  28\r\nSummary *2.2.2.2          2.2.2.2          0x80000194  1732  0x22 0xc6d1  28\r\nSummary *3.3.3.3          2.2.2.2          0x8000000a   643  0x22 0xc459  28\r\nSummary *10.10.20.0       2.2.2.2          0x80000009   371  0x22 0x7989  28\r\nSummary *10.10.30.0       2.2.2.2          0x8000000c    98  0x22 0x5f0   28\r\nSummary *10.10.40.0       2.2.2.2          0x80000399  2010  0x22 0x68f3  28\r\nSummary *10.120.10.0      2.2.2.2          0x80000002  2010  0x22 0xd2d1  28\r\nASBRSum *1.1.1.1          2.2.2.2          0x80000002  2010  0x22 0x230a  28<\/pre>\n<pre class=\"lang:sh decode:true \">root@vMX02&gt; show route protocol ospf   \r\n\r\ninet.0: 21 destinations, 22 routes (21 active, 0 holddown, 0 hidden)\r\n+ = Active Route, - = Last Active, * = Both\r\n\r\n1.1.1.1\/32         *[OSPF\/10] 00:36:55, metric 2\r\n                    &gt; to 10.10.40.2 via ge-0\/0\/1.0\r\n3.3.3.3\/32         *[OSPF\/10] 00:36:55, metric 2\r\n                    &gt; to 10.10.40.2 via ge-0\/0\/1.0\r\n10.10.20.0\/24      *[OSPF\/10] 00:36:55, metric 2\r\n                    &gt; to 10.10.40.2 via ge-0\/0\/1.0\r\n10.10.30.0\/24      *[OSPF\/10] 00:36:55, metric 2\r\n                    &gt; to 10.10.40.2 via ge-0\/0\/1.0\r\n10.120.10.0\/24     *[OSPF\/10] 00:36:55, metric 3\r\n                    &gt; to 10.10.40.2 via ge-0\/0\/1.0\r\n224.0.0.5\/32       *[OSPF\/10] 1w0d 01:21:50, metric 1\r\n                      MultiRecv<\/pre>\n<h6>Cisco ASAv &#8211; vtep01<\/h6>\n<pre class=\"lang:sh decode:true \">vtep01# show ospf neighbor \r\n\r\n\r\nNeighbor ID     Pri   State           Dead Time   Address         Interface\r\n1.1.1.1         128   FULL\/BDR        0:00:35    10.120.10.1     lan120\r\n<\/pre>\n<pre class=\"lang:sh decode:true \">vtep01# show ospf database \r\n\r\n\r\n            OSPF Router with ID (192.168.200.10) (Process ID 1)\r\n\r\n                Router Link States (Area 1)\r\n\r\nLink ID         ADV Router      Age         Seq#       Checksum Link count\r\n1.1.1.1         1.1.1.1         593         0x800002a3 0xe878 1\r\n192.168.200.10  192.168.200.10  1723        0x800002e2 0xd9c0 1\r\n\r\n                Net Link States (Area 1)\r\n\r\nLink ID         ADV Router      Age         Seq#       Checksum\r\n10.120.10.10    192.168.200.10  1723        0x8000025a 0xfbc9\r\n\r\n                Summary Net Link States (Area 1)\r\n\r\nLink ID         ADV Router      Age         Seq#       Checksum\r\n1.1.1.1         1.1.1.1         1188        0x80000123 0x14ff\r\n2.2.2.2         1.1.1.1         6           0x80000001 0x41ef\r\n3.3.3.3         1.1.1.1         2080        0x8000000d 0xfa26\r\n10.10.20.0      1.1.1.1         1783        0x8000000d 0xad57\r\n10.10.30.0      1.1.1.1         1485        0x800002b2 0xe370\r\n10.10.40.0      1.1.1.1         6           0x80000016 0xbe29\r\n10.130.10.0     1.1.1.1         6           0x80000001 0x9809\r\n<\/pre>\n<pre class=\"lang:sh decode:true \">vtep01# show route ospf \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.200.1 to network 0.0.0.0\r\n\r\nO IA     1.1.1.1 255.255.255.255 [110\/10] via 10.120.10.1, 01:02:09, lan120\r\nO IA     2.2.2.2 255.255.255.255 [110\/12] via 10.120.10.1, 00:00:12, lan120\r\nO IA     3.3.3.3 255.255.255.255 [110\/12] via 10.120.10.1, 01:02:09, lan120\r\nO IA     10.10.20.0 255.255.255.0 [110\/12] via 10.120.10.1, 01:02:09, lan120\r\nO IA     10.10.30.0 255.255.255.0 [110\/11] via 10.120.10.1, 01:02:09, lan120\r\nO IA     10.10.40.0 255.255.255.0 [110\/12] via 10.120.10.1, 00:00:12, lan120\r\nO IA     10.130.10.0 255.255.255.0 [110\/13] via 10.120.10.1, 00:00:12, lan120<\/pre>\n<h6>Cisco ASAv &#8211; vtep02<\/h6>\n<pre class=\"lang:sh decode:true \">vtep02# show ospf neighbor \r\n\r\n\r\nNeighbor ID     Pri   State           Dead Time   Address         Interface\r\n2.2.2.2         128   FULL\/BDR        0:00:33    10.130.10.1     vlan130\r\n<\/pre>\n<pre class=\"lang:sh decode:true \">vtep02# show ospf database  \r\n\r\n\r\n            OSPF Router with ID (192.168.200.110) (Process ID 1)\r\n\r\n                Router Link States (Area 1)\r\n\r\nLink ID         ADV Router      Age         Seq#       Checksum Link count\r\n2.2.2.2         2.2.2.2         1469        0x80000393 0x64ed 1\r\n192.168.200.110 192.168.200.110 346         0x80000492 0x51c0 1\r\n\r\n                Net Link States (Area 1)\r\n\r\nLink ID         ADV Router      Age         Seq#       Checksum\r\n10.130.10.10    192.168.200.110 346         0x8000032a 0xfe25\r\n\r\n                Summary Net Link States (Area 1)\r\n\r\nLink ID         ADV Router      Age         Seq#       Checksum\r\n1.1.1.1         2.2.2.2         1197        0x80000003 0x2ffd\r\n2.2.2.2         2.2.2.2         2014        0x80000194 0xc6d1\r\n3.3.3.3         2.2.2.2         925         0x8000000a 0xc459\r\n10.10.20.0      2.2.2.2         652         0x80000009 0x7989\r\n10.10.30.0      2.2.2.2         380         0x8000000c 0x 5f0\r\n10.10.40.0      2.2.2.2         2292        0x80000399 0x68f3\r\n10.120.10.0     2.2.2.2         108         0x80000003 0xd0d2\r\n\r\n                Summary ASB Link States (Area 1)\r\n\r\nLink ID         ADV Router      Age         Seq#       Checksum\r\n1.1.1.1         2.2.2.2         2293        0x80000002 0x230a<\/pre>\n<pre class=\"lang:sh decode:true \">vtep02#  show route ospf \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.200.1 to network 0.0.0.0\r\n\r\nO IA     1.1.1.1 255.255.255.255 [110\/12] via 10.130.10.1, 00:38:33, vlan130\r\nO IA     2.2.2.2 255.255.255.255 [110\/10] via 10.130.10.1, 00:38:33, vlan130\r\nO IA     3.3.3.3 255.255.255.255 [110\/12] via 10.130.10.1, 00:38:33, vlan130\r\nO IA     10.10.20.0 255.255.255.0 [110\/12] via 10.130.10.1, 00:38:33, vlan130\r\nO IA     10.10.30.0 255.255.255.0 [110\/12] via 10.130.10.1, 00:38:33, vlan130\r\nO IA     10.10.40.0 255.255.255.0 [110\/11] via 10.130.10.1, 00:38:33, vlan130\r\nO IA     10.120.10.0 255.255.255.0 [110\/13] via 10.130.10.1, 00:38:33, vlan130<\/pre>\n<h6>Cisco ASA &#8211; \u00a0asav01<\/h6>\n<h4><\/h4>\n<pre class=\"lang:sh decode:true \">vtep02# show route ospf\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.200.1 to network 0.0.0.0\r\n\r\nO IA     1.1.1.1 255.255.255.255 [110\/12] via 10.130.10.1, 00:38:13, vlan130\r\nO IA     2.2.2.2 255.255.255.255 [110\/10] via 10.130.10.1, 00:38:13, vlan130\r\nO IA     3.3.3.3 255.255.255.255 [110\/12] via 10.130.10.1, 00:38:13, vlan130\r\nO IA     10.10.20.0 255.255.255.0 [110\/12] via 10.130.10.1, 00:38:13, vlan130\r\nO IA     10.10.30.0 255.255.255.0 [110\/12] via 10.130.10.1, 00:38:13, vlan130\r\nO IA     10.10.40.0 255.255.255.0 [110\/11] via 10.130.10.1, 00:38:13, vlan130\r\nO IA     10.120.10.0 255.255.255.0 [110\/13] via 10.130.10.1, 00:38:13, vlan130<\/pre>\n<h6>Cisco CSR &#8211; csrv03<\/h6>\n<pre class=\"lang:sh decode:true \">core-csrv03#show ip route ospf\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\/1] via 10.10.30.10, 00:08:04, GigabitEthernet2\r\n      2.0.0.0\/32 is subnetted, 1 subnets\r\nO        2.2.2.2 [110\/1] via 10.10.40.10, 00:06:56, GigabitEthernet3\r\n      10.0.0.0\/8 is variably subnetted, 8 subnets, 2 masks\r\nO IA     10.120.10.0\/24 [110\/2] via 10.10.30.10, 00:08:04, GigabitEthernet2\r\nO IA     10.130.10.0\/24 [110\/2] via 10.10.40.10, 00:06:56, GigabitEthernet3<\/pre>\n<h4><\/h4>\n<h4>Konfiguracja BGP<\/h4>\n<h6>Juniper vMX &#8211; vmx01<\/h6>\n<pre class=\"lang:sh decode:true\">set routing-options router-id 1.1.1.1\r\nset routing-options autonomous-system 65000<\/pre>\n<pre class=\"lang:sh decode:true\">set protocols bgp group Internal type internal\r\nset protocols bgp group Internal local-address 1.1.1.1\r\nset protocols bgp group Internal family inet-vpn unicast\r\nset protocols bgp group Internal family evpn signaling\r\nset protocols bgp group Internal neighbor 2.2.2.2<\/pre>\n<pre class=\"lang:sh decode:true \">set routing-options forwarding-table chained-composite-next-hop ingress evpn<\/pre>\n<h6>Juniper vMX &#8211; vmx02<\/h6>\n<pre class=\"lang:sh decode:true\">set routing-options router-id 2.2.2.2\r\nset routing-options autonomous-system 65000<\/pre>\n<pre class=\"lang:sh decode:true\">set protocols bgp group Internal type internal\r\nset protocols bgp group Internal local-address 2.2.2.2\r\nset protocols bgp group Internal family inet-vpn unicast\r\nset protocols bgp group Internal family evpn signaling\r\nset protocols bgp group Internal neighbor 1.1.1.1<\/pre>\n<pre class=\"lang:sh decode:true \">set routing-options forwarding-table chained-composite-next-hop ingress evpn<\/pre>\n<h4>Weryfikacja BGP<\/h4>\n<h6>Juniper vMX &#8211; vmx01<\/h6>\n<pre class=\"lang:sh decode:true \">root@vMX01&gt; show bgp summary    \r\nGroups: 1 Peers: 1 Down peers: 0\r\nPeer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up\/Dwn State|#Active\/Received\/Accepted\/Damped...\r\n2.2.2.2               65000         17         17       0     473        4:36 Establ<\/pre>\n<h6>Juniper vMX &#8211; vmx02<\/h6>\n<pre class=\"lang:sh decode:true\">root@vMX02&gt; show bgp summary \r\nGroups: 1 Peers: 1 Down peers: 0\r\nPeer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up\/Dwn State|#Active\/Received\/Accepted\/Damped...\r\n1.1.1.1               65000         22         20       0     484        6:06 Establ<\/pre>\n<h4><\/h4>\n<h4>Konfiguracja MPLS z sygnalizacj\u0105 LDP<\/h4>\n<h6>Cisco CSR &#8211; csrv03<\/h6>\n<pre class=\"lang:sh decode:true\">mpls label protocol ldp<\/pre>\n<pre class=\"lang:sh decode:true\">interface GigabitEthernet2\r\nmpls ip<\/pre>\n<pre class=\"lang:sh decode:true\">interface GigabitEthernet3\r\n mpls ip<\/pre>\n<h6>Juniper vMX &#8211; vmx01<\/h6>\n<pre class=\"lang:sh decode:true\">set protocols mpls interface all\r\nset protocols ldp interface ge-0\/0\/1.0\r\nset protocols ldp interface lo0.0<\/pre>\n<pre class=\"lang:sh decode:true \">set interfaces ge-0\/0\/1 unit 0 family mpls<\/pre>\n<h6>Juniper vMX &#8211; vmx02<\/h6>\n<pre class=\"lang:sh decode:true \">set protocols mpls interface all\r\nset protocols ldp interface ge-0\/0\/1.0\r\nset protocols ldp interface lo0.0<\/pre>\n<pre class=\"lang:sh decode:true\">set interfaces ge-0\/0\/1 unit 0 family mpls<\/pre>\n<h4>Weryfikacja MPLS<\/h4>\n<h6>Cisco CSR &#8211; csrv03<\/h6>\n<pre class=\"lang:sh decode:true \">core-csrv03#show mpls interfaces \r\nInterface              IP            Tunnel   BGP Static Operational\r\nGigabitEthernet2       Yes (ldp)     No       No  No     Yes        \r\nGigabitEthernet3       Yes (ldp)     No       No  No     Yes<\/pre>\n<pre class=\"lang:sh decode:true \">core-csrv03#show mpls ldp neighbor \r\n    Peer LDP Ident: 2.2.2.2:0; Local LDP Ident 3.3.3.3:0\r\n        TCP connection: 2.2.2.2.646 - 3.3.3.3.21614\r\n        State: Oper; Msgs sent\/rcvd: 16\/10; Downstream\r\n        Up time: 00:00:40\r\n        LDP discovery sources:\r\n          GigabitEthernet3, Src IP addr: 10.10.40.10\r\n        Addresses bound to peer LDP Ident:\r\n          2.2.2.2         10.10.40.10     \r\n    Peer LDP Ident: 1.1.1.1:0; Local LDP Ident 3.3.3.3:0\r\n        TCP connection: 1.1.1.1.646 - 3.3.3.3.25210\r\n        State: Oper; Msgs sent\/rcvd: 13\/7; Downstream\r\n        Up time: 00:00:09\r\n        LDP discovery sources:\r\n          GigabitEthernet2, Src IP addr: 10.10.30.10\r\n        Addresses bound to peer LDP Ident:\r\n          1.1.1.1         10.10.30.10<\/pre>\n<pre class=\"lang:sh decode:true\">core-csrv03#show mpls forwarding-table \r\nLocal      Outgoing   Prefix           Bytes Label   Outgoing   Next Hop    \r\nLabel      Label      or Tunnel Id     Switched      interface              \r\n16         Pop Label  2.2.2.2\/32       0             Gi3        10.10.40.10 \r\n17         No Label   10.130.10.0\/24   0             Gi3        10.10.40.10 \r\n18         Pop Label  1.1.1.1\/32       0             Gi2        10.10.30.10 \r\n19         No Label   10.120.10.0\/24   0             Gi2        10.10.30.10<\/pre>\n<pre class=\"lang:sh decode:true \">core-csrv03#show mpls ldp bindings \r\n  lib entry: 1.1.1.1\/32, rev 13\r\n        local binding:  label: 16\r\n        remote binding: lsr: 1.1.1.1:0, label: imp-null\r\n        remote binding: lsr: 2.2.2.2:0, label: 420688\r\n  lib entry: 2.2.2.2\/32, rev 18\r\n        local binding:  label: 18\r\n        remote binding: lsr: 2.2.2.2:0, label: imp-null\r\n        remote binding: lsr: 1.1.1.1:0, label: 410304\r\n  lib entry: 3.3.3.3\/32, rev 2\r\n        local binding:  label: imp-null\r\n        remote binding: lsr: 1.1.1.1:0, label: 410272\r\n        remote binding: lsr: 2.2.2.2:0, label: 420656\r\n  lib entry: 10.10.20.0\/24, rev 8\r\n        local binding:  label: imp-null\r\n        remote binding: lsr: 1.1.1.1:0, label: 410272\r\n        remote binding: lsr: 2.2.2.2:0, label: 420656\r\n  lib entry: 10.10.30.0\/24, rev 4\r\n        local binding:  label: imp-null\r\n        remote binding: lsr: 2.2.2.2:0, label: 420656\r\n  lib entry: 10.10.40.0\/24, rev 6\r\n        local binding:  label: imp-null\r\n        remote binding: lsr: 1.1.1.1:0, label: 410272\r\n  lib entry: 10.120.10.0\/24, rev 12\r\n        local binding:  label: 17\r\n        remote binding: lsr: 2.2.2.2:0, label: 420672\r\n  lib entry: 10.130.10.0\/24, rev 17\r\n        local binding:  label: 19\r\n        remote binding: lsr: 1.1.1.1:0, label: 410288<\/pre>\n<h6>Juniper vMX &#8211; vmx01<\/h6>\n<pre class=\"lang:sh decode:true\">root@vMX01&gt; show ldp database \r\nInput label database, 1.1.1.1:0--3.3.3.3:0\r\nLabels received: 5\r\n  Label     Prefix\r\n     18      1.1.1.1\/32\r\n     16      2.2.2.2\/32\r\n      3      3.3.3.3\/32\r\n      3      10.10.20.0\/24\r\n      3      10.10.30.0\/24\r\n      3      10.10.40.0\/24\r\n     19      10.120.10.0\/24\r\n     17      10.130.10.0\/24\r\n\r\nOutput label database, 1.1.1.1:0--3.3.3.3:0\r\nLabels advertised: 4\r\n  Label     Prefix\r\n      3      1.1.1.1\/32\r\n 410208      2.2.2.2\/32\r\n 410176      3.3.3.3\/32\r\n 410176      10.10.20.0\/24\r\n 410176      10.10.40.0\/24\r\n 410192      10.130.10.0\/24<\/pre>\n<pre class=\"lang:sh decode:true\">root@vMX01&gt; show ldp neighbor                           \r\nAddress            Interface          Label space ID         Hold time\r\n10.10.30.2         ge-0\/0\/1.0         3.3.3.3:0                14<\/pre>\n<pre class=\"lang:sh decode:true \">root@vMX01&gt; show route protocol mpls \r\n\r\nmpls.0: 16 destinations, 16 routes (16 active, 0 holddown, 0 hidden)\r\n+ = Active Route, - = Last Active, * = Both\r\n\r\n0                  *[MPLS\/0] 5d 23:58:55, metric 1\r\n                      to table inet.0\r\n0(S=0)             *[MPLS\/0] 5d 23:58:55, metric 1\r\n                      to table mpls.0\r\n1                  *[MPLS\/0] 5d 23:58:55, metric 1\r\n                      Receive\r\n2                  *[MPLS\/0] 5d 23:58:55, metric 1\r\n                      to table inet6.0\r\n2(S=0)             *[MPLS\/0] 5d 23:58:55, metric 1\r\n                      to table mpls.0\r\n13                 *[MPLS\/0] 5d 23:58:55, metric 1\r\n                      Receive<\/pre>\n<h6>Juniper vMX &#8211; vmx02<\/h6>\n<pre class=\"lang:sh decode:true \">root@vMX02&gt; show ldp database \r\nInput label database, 2.2.2.2:0--3.3.3.3:0\r\nLabels received: 5\r\n  Label     Prefix\r\n     18      1.1.1.1\/32\r\n     16      2.2.2.2\/32\r\n      3      3.3.3.3\/32\r\n      3      10.10.20.0\/24\r\n      3      10.10.30.0\/24\r\n      3      10.10.40.0\/24\r\n     19      10.120.10.0\/24\r\n     17      10.130.10.0\/24\r\n\r\nOutput label database, 2.2.2.2:0--3.3.3.3:0\r\nLabels advertised: 4\r\n  Label     Prefix\r\n 420592      1.1.1.1\/32\r\n      3      2.2.2.2\/32\r\n 420560      3.3.3.3\/32\r\n 420560      10.10.20.0\/24\r\n 420560      10.10.30.0\/24\r\n 420576      10.120.10.0\/24<\/pre>\n<pre class=\"lang:sh decode:true \">root@vMX02&gt; show ldp neighbor \r\nAddress            Interface          Label space ID         Hold time\r\n10.10.40.2         ge-0\/0\/1.0         3.3.3.3:0                13<\/pre>\n<pre class=\"lang:sh decode:true \">root@vMX02&gt; show route protocol mpls          \r\n\r\nmpls.0: 16 destinations, 16 routes (16 active, 0 holddown, 0 hidden)\r\n+ = Active Route, - = Last Active, * = Both\r\n\r\n0                  *[MPLS\/0] 1w0d 05:11:56, metric 1\r\n                      to table inet.0\r\n0(S=0)             *[MPLS\/0] 1w0d 05:11:56, metric 1\r\n                      to table mpls.0\r\n1                  *[MPLS\/0] 1w0d 05:11:56, metric 1\r\n                      Receive\r\n2                  *[MPLS\/0] 1w0d 05:11:56, metric 1\r\n                      to table inet6.0\r\n2(S=0)             *[MPLS\/0] 1w0d 05:11:56, metric 1\r\n                      to table mpls.0\r\n13                 *[MPLS\/0] 1w0d 05:11:56, metric 1\r\n                      Receive<\/pre>\n<h4><\/h4>\n<h4>Konfiguracja Multicast<\/h4>\n<h6>Juniper vMX &#8211; vmx01<\/h6>\n<pre class=\"lang:sh decode:true\">set protocols pim rp static address 3.3.3.3\r\nset protocols pim interface lo0.0 mode bidirectional-sparse\r\nset protocols pim interface ge-0\/0\/1.0 mode bidirectional-sparse\r\nset protocols pim interface ge-0\/0\/4.0 mode bidirectional-sparse<\/pre>\n<h6>Juniper vMX &#8211; vmx02<\/h6>\n<pre class=\"lang:sh decode:true \">set protocols pim rp static address 3.3.3.3\r\nset protocols pim interface lo0.0 mode bidirectional-sparse\r\nset protocols pim interface ge-0\/0\/1.0 mode bidirectional-sparse\r\nset protocols pim interface ge-0\/0\/4.0 mode bidirectional-sparse<\/pre>\n<h6>Cisco ASAv &#8211; vtep01<\/h6>\n<pre class=\"lang:sh decode:true\">multicast-routing\r\npim rp-address 3.3.3.3<\/pre>\n<h6>Cisco ASAv &#8211; vtep02<\/h6>\n<pre class=\"lang:sh decode:true \">multicast-routing\r\npim rp-address 3.3.3.3<\/pre>\n<h6>Cisco ASA &#8211; \u00a0asav01<\/h6>\n<pre class=\"lang:sh decode:true \">multicast-routing<\/pre>\n<h4>Weryfikacja Multicast<\/h4>\n<h6>Juniper vMX &#8211; vmx01<\/h6>\n<pre class=\"lang:sh decode:true \">root@vMX01&gt; show pim neighbors    \r\nB = Bidirectional Capable, G = Generation Identifier\r\nH = Hello Option Holdtime, L = Hello Option LAN Prune Delay,\r\nP = Hello Option DR Priority, T = Tracking Bit\r\n\r\nInstance: PIM.master\r\nInterface           IP V Mode        Option       Uptime Neighbor addr\r\nge-0\/0\/1.0           4 2             HPGB       00:05:19 10.10.30.2     \r\nge-0\/0\/4.0           4 2             HPLGB      00:00:22 10.120.10.10<\/pre>\n<pre class=\"lang:sh decode:true \">root@vMX01&gt; show route protocol pim \r\n\r\ninet.0: 19 destinations, 20 routes (19 active, 0 holddown, 0 hidden)\r\n+ = Active Route, - = Last Active, * = Both\r\n\r\n224.0.0.2\/32       *[PIM\/0] 6d 00:53:00\r\n                      MultiRecv\r\n224.0.0.13\/32      *[PIM\/0] 6d 00:53:00\r\n                      MultiRecv\r\n\r\ninet.1: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)\r\n+ = Active Route, - = Last Active, * = Both\r\n\r\n239.100.100.100,1.1.1.1\/64*[PIM\/105] 6d 00:49:25\r\n                      Multicast (IPv4) Composite\r\n239.110.110.110,1.1.1.1\/64*[PIM\/105] 6d 00:49:31\r\n                      Multicast (IPv4) Composite\r\n239.110.110.110,10.120.10.10\/64*[PIM\/105] 00:08:25\r\n                      Multicast (IPv4) Composite<\/pre>\n<h6>Juniper vMX &#8211; vmx02<\/h6>\n<pre class=\"lang:sh decode:true \">root@vMX02&gt; show pim neighbors \r\nB = Bidirectional Capable, G = Generation Identifier\r\nH = Hello Option Holdtime, L = Hello Option LAN Prune Delay,\r\nP = Hello Option DR Priority, T = Tracking Bit\r\n\r\nInstance: PIM.master\r\nInterface           IP V Mode        Option       Uptime Neighbor addr\r\nge-0\/0\/1.0           4 2             HPGB       00:13:11 10.10.40.2     \r\nge-0\/0\/4.0           4 2             HPLGB      00:13:10 10.130.10.10<\/pre>\n<h6>Cisco ASAv &#8211; vtep01<\/h6>\n<pre class=\"lang:sh decode:true \">vtep01# show pim neighbor  \r\n\r\nNeighbor Address  Interface          Uptime    Expires DR pri Bidir\r\n\r\n10.120.10.1       lan120             00:03:04  00:01:31 1      B<\/pre>\n<h6>Cisco ASAv &#8211; vtep02<\/h6>\n<pre class=\"lang:sh decode:true \">vtep02#  show pim nei\r\n\r\nNeighbor Address  Interface          Uptime    Expires DR pri Bidir\r\n\r\n10.130.10.1       vlan130            00:38:34  00:01:24 1      B<\/pre>\n<h6>Cisco ASA &#8211; \u00a0asav01<\/h6>\n<pre class=\"lang:sh decode:true \">asav01# show pim nei\r\n\r\nNeighbor Address  Interface          Uptime    Expires DR pri Bidir\r\n\r\n10.10.20.2        lan                00:05:55  00:01:41 1 (DR) B<\/pre>\n<h4>Konfiguracja VxLAN<\/h4>\n<p>ze wzgl\u0119du na po\u0142\u0105czenie evpn z vxvlan oraz \u0142\u0105czenie interfejs\u00f3w b\u0119dziemy wykorzystywa\u0107 routing instancje dla vxvlan6666 oraz vxvlan1100 oraz b\u0119dziemy \u0142\u0105czy\u0107 ze sob\u0105 segmenty wykorzystuj\u0105c bridge domain.<\/p>\n<p>Jedna\u00a0uwaga:<\/p>\n<p>po uruchomieniu vxlan na Cisco ASAv przestaje dzia\u0142a\u0107 OSPF ze wzgl\u0119du na zmian\u0119 MTU \u00a0na interfejsie \u017ar\u00f3d\u0142owym dla vtep&#8217;a i dlatego na urz\u0105dzeniach s\u0105siednich trzeba zmieni\u0107 MTU:<\/p>\n<h6>Cisco CSR &#8211; csrv03<\/h6>\n<pre class=\"lang:sh decode:true \">interface GigabitEthernet1\r\n mtu 1554<\/pre>\n<h6>Juniper vMX<\/h6>\n<pre class=\"lang:sh decode:true \">set interfaces ge-0\/0\/4 mtu 1568<\/pre>\n<h5>Przypadek 1<\/h5>\n<p>Rysunek pogl\u0105dowy:<\/p>\n<p><a href=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/p1_1.png\"><img data-recalc-dims=\"1\" loading=\"lazy\" decoding=\"async\" data-attachment-id=\"829\" data-permalink=\"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/attachment\/p1_1\/\" data-orig-file=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/p1_1.png?fit=1035%2C948&amp;ssl=1\" data-orig-size=\"1035,948\" data-comments-opened=\"0\" data-image-meta=\"{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;}\" data-image-title=\"p1_1\" data-image-description=\"\" data-image-caption=\"\" data-large-file=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/p1_1.png?fit=770%2C705&amp;ssl=1\" class=\"alignnone size-full wp-image-829\" src=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/p1_1.png?resize=770%2C705\" alt=\"p1_1\" width=\"770\" height=\"705\" srcset=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/p1_1.png?w=1035&amp;ssl=1 1035w, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/p1_1.png?resize=300%2C275&amp;ssl=1 300w, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/p1_1.png?resize=768%2C703&amp;ssl=1 768w, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/p1_1.png?resize=1024%2C938&amp;ssl=1 1024w\" sizes=\"auto, (max-width: 770px) 100vw, 770px\" \/><\/a><\/p>\n<p>Na Cisco ASA asav01 jest uruchomiony interfejs vni 6666 a Juniper vMX ma dost\u0119p do tego vxlanu i tworzy Bridge pomi\u0119dzy vxvlanem, evpnem a vlanem 100, do kt\u00f3rego b\u0119dzie pod\u0142\u0105czone kolejne Cisco ASA z fizycznym interfejsem.<\/p>\n<p>&nbsp;<\/p>\n<p>Na urz\u0105dzeniach vMX konfigurujemy routing instances typu evpn<\/p>\n<h6>Juniper vMX &#8211; vmx01<\/h6>\n<pre class=\"lang:sh decode:true\">set routing-instances evpn100 vtep-source-interface lo0.0\r\nset routing-instances evpn100 instance-type evpn\r\nset routing-instances evpn100 vlan-id 100\r\nset routing-instances evpn100 interface ge-0\/0\/2.0\r\nset routing-instances evpn100 vxlan vni 6666\r\nset routing-instances evpn100 vxlan multicast-group 239.100.100.100\r\nset routing-instances evpn100 vxlan encapsulate-inner-vlan\r\nset routing-instances evpn100 vxlan decapsulate-accept-inner-vlan\r\nset routing-instances evpn100 route-distinguisher 1.1.1.1:100\r\nset routing-instances evpn100 vrf-target target:1:1<\/pre>\n<p>Konfigurujemy interfejs, do kt\u00f3rego b\u0119dzie pod\u0142\u0105czony vtep01. Port jest tagowany vlanem 100<\/p>\n<pre class=\"lang:sh decode:true\">set interfaces ge-0\/0\/2 flexible-vlan-tagging\r\nset interfaces ge-0\/0\/2 encapsulation flexible-ethernet-services\r\nset interfaces ge-0\/0\/2 unit 0 encapsulation vlan-bridge\r\nset interfaces ge-0\/0\/2 unit 0 vlan-id 100<\/pre>\n<h6>Juniper vMX &#8211; vmx02<\/h6>\n<pre class=\"lang:sh decode:true\">set routing-instances evpn100 vtep-source-interface lo0.0\r\nset routing-instances evpn100 instance-type evpn\r\nset routing-instances evpn100 vlan-id 100\r\nset routing-instances evpn100 interface ge-0\/0\/2.0\r\nset routing-instances evpn100 vxlan vni 6666\r\nset routing-instances evpn100 vxlan multicast-group 239.100.100.100\r\nset routing-instances evpn100 vxlan encapsulate-inner-vlan\r\nset routing-instances evpn100 vxlan decapsulate-accept-inner-vlan\r\nset routing-instances evpn100 route-distinguisher 2.2.2.2:100\r\nset routing-instances evpn100 vrf-target target:1:1<\/pre>\n<p>Konfigurujemy interfejs, do kt\u00f3rego b\u0119dzie pod\u0142\u0105czony vtep01. Port jest tagowany vlanem 100<\/p>\n<pre class=\"lang:sh decode:true\">set interfaces ge-0\/0\/2 flexible-vlan-tagging\r\nset interfaces ge-0\/0\/2 encapsulation flexible-ethernet-services\r\nset interfaces ge-0\/0\/2 unit 0 encapsulation vlan-bridge\r\nset interfaces ge-0\/0\/2 unit 0 vlan-id 100<\/pre>\n<h6>Cisco ASAv &#8211; vtep01<\/h6>\n<pre class=\"lang:sh decode:true\">interface GigabitEthernet0\/0.100\r\n vlan 100\r\n nameif lan\r\n security-level 0\r\n ip address 192.168.200.10 255.255.255.0 \r\n no sh<\/pre>\n<p>routing domy\u015blny przez asav01<\/p>\n<pre class=\"lang:sh decode:true\">route lan 0.0.0.0 0.0.0.0 192.168.200.1 1<\/pre>\n<h6>Cisco ASAv &#8211; vtep02<\/h6>\n<pre class=\"lang:sh decode:true \">interface GigabitEthernet0\/0.100\r\n vlan 100\r\n nameif lan\r\n security-level 0\r\n ip address 192.168.200.110 255.255.255.0 \r\n no sh<\/pre>\n<p>routing domy\u015blny przez asav01<\/p>\n<pre class=\"lang:sh decode:true\">route lan 0.0.0.0 0.0.0.0 192.168.200.1 1<\/pre>\n<h6>Cisco ASA &#8211; \u00a0asav01<\/h6>\n<pre class=\"lang:sh decode:true \">nve 1\r\n encapsulation vxlan\r\n source-interface lan<\/pre>\n<pre class=\"lang:sh decode:true \">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<\/pre>\n<p>Konfiguracja nat&#8217;u oraz routingu tak aby by\u0142 dost\u0119pny Internet<\/p>\n<pre class=\"lang:sh decode:true \">route out 0.0.0.0 0.0.0.0 192.168.1.1 1<\/pre>\n<pre class=\"lang:sh decode:true \">nat (vxvlan6666,out) source dynamic any interface<\/pre>\n<h4>Weryfikacja:<\/h4>\n<h6>Cisco ASAv &#8211; asav01<\/h6>\n<p>Wykonujemy pingi interfejs\u00f3w l3<\/p>\n<pre class=\"lang:sh decode:true\">asav01# ping 192.168.200.10\r\nType escape sequence to abort.\r\nSending 5, 100-byte ICMP Echos to 192.168.200.10, timeout is 2 seconds:\r\n!!!!!\r\nSuccess rate is 100 percent (5\/5), round-trip min\/avg\/max = 10\/22\/30 ms\r\n<\/pre>\n<p>&nbsp;<\/p>\n<pre class=\"lang:sh decode:true \">asav01# ping 192.168.200.110\r\nType escape sequence to abort.\r\nSending 5, 100-byte ICMP Echos to 192.168.200.110, timeout is 2 seconds:\r\n!!!!!\r\nSuccess rate is 100 percent (5\/5), round-trip min\/avg\/max = 10\/22\/30 ms\r\n<\/pre>\n<h4><\/h4>\n<pre class=\"lang:sh decode:true \">asav01# ping 192.168.200.1\r\nType escape sequence to abort.\r\nSending 5, 100-byte ICMP Echos to 192.168.200.1, timeout is 2 seconds:\r\n!!!!!\r\nSuccess rate is 100 percent (5\/5), round-trip min\/avg\/max = 1\/1\/1 ms<\/pre>\n<p>Tablica arp:<\/p>\n<pre class=\"lang:sh decode:true \">asav01# show arp\r\n        out 192.168.1.10 c8f7.3391.c2ab 11\r\n        lan 10.10.20.2 000c.29b7.00b9 373\r\n        vxvlan6666 192.168.200.110 000c.2977.39f5 223\r\n        vxvlan6666 192.168.200.10 000c.2995.a7b0 226\r\n<\/pre>\n<p>vxvlan:<\/p>\n<pre class=\"lang:sh decode:true \">asav01# show nve 1\r\nnve 1, source-interface \"lan\" is up\r\n IP address 10.10.20.1, subnet mask 255.255.255.0\r\n Encapsulation: vxlan\r\n Encapsulated traffic statistics:\r\n   34 packets input, 3644 bytes\r\n   50 packets output, 6470 bytes\r\n   0 packets dropped\r\n Number of configured static peer VTEPs: 0\r\n Number of discovered peer VTEPs: 2\r\n    Discovered peer VTEPs:\r\n        IP address 1.1.1.1\r\n        IP address 2.2.2.2\r\n Number of VNIs attached to nve 1: 1\r\n VNIs attached:\r\n        vni 1: segment-id 6666, mcast-group 239.100.100.100<\/pre>\n<h4><\/h4>\n<h6>Cisco ASAv &#8211; vtep01<\/h6>\n<pre class=\"lang:sh decode:true\">vtep01# ping 192.168.200.10\r\nType escape sequence to abort.\r\nSending 5, 100-byte ICMP Echos to 192.168.200.10, timeout is 2 seconds:\r\n!!!!!\r\nSuccess rate is 100 percent (5\/5), round-trip min\/avg\/max = 1\/1\/1 ms\r\n<\/pre>\n<h4><\/h4>\n<pre class=\"lang:sh decode:true \">vtep01# ping 192.168.200.1\r\nType escape sequence to abort.\r\nSending 5, 100-byte ICMP Echos to 192.168.200.1, timeout is 2 seconds:\r\n!!!!!\r\nSuccess rate is 100 percent (5\/5), round-trip min\/avg\/max = 10\/40\/120 ms\r\n<\/pre>\n<h4><\/h4>\n<pre class=\"lang:sh decode:true \">vtep01# ping 192.168.200.110\r\nType escape sequence to abort.\r\nSending 5, 100-byte ICMP Echos to 192.168.200.110, timeout is 2 seconds:\r\n!!!!!\r\nSuccess rate is 100 percent (5\/5), round-trip min\/avg\/max = 20\/38\/80 ms\r\n<\/pre>\n<h4><\/h4>\n<pre class=\"lang:sh decode:true \">vtep01# show arp\r\n        lan 192.168.200.110 000c.2977.39f5 50\r\n        lan 192.168.200.1 000c.2927.c9a1 223\r\n        lan120 10.120.10.1 000c.2960.d9e1 108\r\n        vxvlan1100 172.16.110.100 0005.8671.35f0 1178\r\n        vxvlan1100 172.16.110.101 0005.8671.6ff0 3231\r\n        vxvlan1100 172.16.110.50 0200.2000.2000 12589\r\n<\/pre>\n<h4><\/h4>\n<pre class=\"lang:sh decode:true \">vtep01# show nve 1\r\nnve 1, source-interface \"lan120\" is up\r\n IP address 10.120.10.10, subnet mask 255.255.255.0\r\n Encapsulation: vxlan\r\n Encapsulated traffic statistics:\r\n   2409 packets input, 173226 bytes\r\n   3203 packets output, 330536 bytes\r\n   0 packets dropped\r\n Number of configured static peer VTEPs: 0\r\n Number of discovered peer VTEPs: 1\r\n    Discovered peer VTEPs:\r\n        IP address 1.1.1.1\r\n Number of VNIs attached to nve 1: 1\r\n VNIs attached:\r\n        vni 1100: segment-id 1100, mcast-group 239.110.110.110<\/pre>\n<h4><\/h4>\n<p>Po skonfigurowaniu routingu domy\u015blnego mo\u017cemy osi\u0105gn\u0105\u0107 Internet<\/p>\n<pre class=\"lang:sh decode:true\">vtep01# 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.200.1 to network 0.0.0.0\r\n\r\nS*    0.0.0.0 0.0.0.0 [1\/0] via 192.168.200.1, lan\r\nO IA     1.1.1.1 255.255.255.255 [110\/10] via 10.120.10.1, 00:45:08, lan120\r\nO IA     2.2.2.2 255.255.255.255 [110\/12] via 10.120.10.1, 00:05:03, lan120\r\nO IA     3.3.3.3 255.255.255.255 [110\/12] via 10.120.10.1, 00:45:08, lan120\r\nO IA     10.10.20.0 255.255.255.0 [110\/12] via 10.120.10.1, 00:45:08, lan120\r\nO IA     10.10.30.0 255.255.255.0 [110\/11] via 10.120.10.1, 00:45:08, lan120\r\nO IA     10.10.40.0 255.255.255.0 [110\/12] via 10.120.10.1, 00:05:03, lan120\r\nC        10.120.10.0 255.255.255.0 is directly connected, lan120\r\nL        10.120.10.10 255.255.255.255 is directly connected, lan120\r\nO IA     10.130.10.0 255.255.255.0 [110\/13] via 10.120.10.1, 00:05:03, lan120\r\nC        172.16.110.0 255.255.255.0 is directly connected, vxvlan1100\r\nL        172.16.110.10 255.255.255.255 is directly connected, vxvlan1100\r\nC        192.168.200.0 255.255.255.0 is directly connected, lan\r\nL        192.168.200.10 255.255.255.255 is directly connected, lan<\/pre>\n<pre class=\"lang:sh decode:true\">vtep01# ping 8.8.8.8\r\nType escape sequence to abort.\r\nSending 5, 100-byte ICMP Echos to 8.8.8.8, timeout is 2 seconds:\r\n!!!!!\r\nSuccess rate is 100 percent (5\/5), round-trip min\/avg\/max = 40\/100\/310 ms<\/pre>\n<p>&nbsp;<\/p>\n<h4>Cisco ASAv &#8211; vtep02<\/h4>\n<pre class=\"lang:sh decode:true\">vtep02# ping 192.168.200.10\r\nType escape sequence to abort.\r\nSending 5, 100-byte ICMP Echos to 192.168.200.10, timeout is 2 seconds:\r\n!!!!!\r\nSuccess rate is 100 percent (5\/5), round-trip min\/avg\/max = 50\/250\/830 ms\r\n<\/pre>\n<h4><\/h4>\n<pre class=\"lang:sh decode:true \">vtep02# ping 192.168.200.1\r\nType escape sequence to abort.\r\nSending 5, 100-byte ICMP Echos to 192.168.200.1, timeout is 2 seconds:\r\n!!!!!\r\nSuccess rate is 100 percent (5\/5), round-trip min\/avg\/max = 10\/36\/90 ms\r\n<\/pre>\n<h4><\/h4>\n<pre class=\"lang:sh decode:true \">vtep02# ping 192.168.200.110\r\nType escape sequence to abort.\r\nSending 5, 100-byte ICMP Echos to 192.168.200.110, timeout is 2 seconds:\r\n!!!!!\r\nSuccess rate is 100 percent (5\/5), round-trip min\/avg\/max = 1\/1\/1 ms\r\n<\/pre>\n<h4><\/h4>\n<pre class=\"lang:sh decode:true \">vtep02# show arp\r\n        lan 192.168.200.10 000c.2995.a7b0 50\r\n        lan 192.168.200.1 000c.2927.c9a1 223\r\n        vlan130 10.130.10.1 000c.29a6.9bf5 105\r\n        vxlan1100 172.16.110.100 0005.8671.35f0 1178\r\n        vxlan1100 172.16.110.101 0005.8671.6ff0 3231\r\n        vxlan1100 172.16.110.10 000a.0100.1000 12589\r\n<\/pre>\n<pre class=\"lang:sh decode:true \">vtep02# show nve 1\r\nnve 1, source-interface \"vlan130\" is up\r\n IP address 10.130.10.10, subnet mask 255.255.255.0\r\n Encapsulation: vxlan\r\n Encapsulated traffic statistics:\r\n   2924 packets input, 195924 bytes\r\n   2522 packets output, 273016 bytes\r\n   0 packets dropped\r\n Number of configured static peer VTEPs: 0\r\n Number of discovered peer VTEPs: 1\r\n    Discovered peer VTEPs:\r\n        IP address 2.2.2.2\r\n Number of VNIs attached to nve 1: 1\r\n VNIs attached:\r\n        vni 1100: segment-id 1100, mcast-group 239.110.110.110<\/pre>\n<p>&nbsp;<\/p>\n<pre class=\"lang:sh decode:true\">vtep02# 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.200.1 to network 0.0.0.0\r\n\r\nS*    0.0.0.0 0.0.0.0 [1\/0] via 192.168.200.1, lan\r\nO IA     1.1.1.1 255.255.255.255 [110\/12] via 10.130.10.1, 00:04:20, vlan130\r\nO IA     2.2.2.2 255.255.255.255 [110\/10] via 10.130.10.1, 00:04:20, vlan130\r\nO IA     3.3.3.3 255.255.255.255 [110\/12] via 10.130.10.1, 00:04:20, vlan130\r\nO IA     10.10.20.0 255.255.255.0 [110\/12] via 10.130.10.1, 00:04:20, vlan130\r\nO IA     10.10.30.0 255.255.255.0 [110\/12] via 10.130.10.1, 00:04:20, vlan130\r\nO IA     10.10.40.0 255.255.255.0 [110\/11] via 10.130.10.1, 00:04:20, vlan130\r\nO IA     10.120.10.0 255.255.255.0 [110\/13] via 10.130.10.1, 00:04:20, vlan130\r\nC        10.130.10.0 255.255.255.0 is directly connected, vlan130\r\nL        10.130.10.10 255.255.255.255 is directly connected, vlan130\r\nC        172.16.110.0 255.255.255.0 is directly connected, vxlan1100\r\nL        172.16.110.50 255.255.255.255 is directly connected, vxlan1100\r\nC        192.168.200.0 255.255.255.0 is directly connected, lan\r\nL        192.168.200.110 255.255.255.255 is directly connected, lan<\/pre>\n<pre class=\"lang:sh decode:true \">vtep02# ping 8.8.8.8\r\nType escape sequence to abort.\r\nSending 5, 100-byte ICMP Echos to 8.8.8.8, timeout is 2 seconds:\r\n!!!!!\r\nSuccess rate is 100 percent (5\/5), round-trip min\/avg\/max = 30\/32\/40 ms<\/pre>\n<p>&nbsp;<\/p>\n<h6>Juniper vMX &#8211; vmx01<\/h6>\n<pre class=\"lang:sh decode:true\">root@vMX01&gt; show l2-learning vxlan-tunnel-end-point source    \r\nLogical System Name       Id  SVTEP-IP         IFL   L3-Idx\r\n&lt;default&gt;                 0   1.1.1.1          lo0.0    0  \r\n    L2-RTT                   Bridge Domain              VNID     MC-Group-IP\r\n    evpn100                  __evpn100__                6666     239.100.100.100<\/pre>\n<h6><\/h6>\n<pre class=\"lang:sh decode:true\">vMX01 fpc0 Frame 10: sp = 0xffe0d768, pc = 0xf748c9b3 \r\nshow l2-learning vxlan-tunnel-end-point remote \r\nLogical System Name       Id  SVTEP-IP         IFL   L3-Idx\r\n&lt;default&gt;                 0   1.1.1.1          lo0.0    0  \r\n RVTEP-IP         IFL-Idx   NH-Id\r\n 10.10.20.1       348       1195     \r\n    VNID          MC-Group-IP      \r\n    6666          239.100.100.100<\/pre>\n<p>&nbsp;<\/p>\n<pre class=\"lang:sh decode:true \">root@vMX01&gt; show evpn instance evpn100 extensive    \r\nInstance: evpn100\r\n  Route Distinguisher: 1.1.1.1:100\r\n  VLAN ID: 100\r\n  Per-instance MAC route label: 299776\r\n  MAC database status                Local  Remote\r\n    Total MAC addresses:                 1       0\r\n    Default gateway MAC addresses:       0       0\r\n  Number of local interfaces: 3 (3 up)\r\n    Interface name  ESI                            Mode             Status\r\n    ge-0\/0\/2.0      00:00:00:00:00:00:00:00:00:00  single-homed     Up    \r\n    vtep.32770      00:00:00:00:00:00:00:00:00:00  single-homed     Up    \r\n    vtep.32772                                                      Up    \r\n  Number of IRB interfaces: 0 (0 up)\r\n  Number of bridge domains: 1\r\n    VLAN ID  Intfs \/ up    Mode             MAC sync  IM route label\r\n    100          1   1     Extended         Enabled   299888 \r\n  Number of neighbors: 1\r\n    2.2.2.2\r\n      Received routes\r\n        MAC address advertisement:              1\r\n        MAC+IP address advertisement:           0\r\n        Inclusive multicast:                    1\r\n        Ethernet auto-discovery:                0\r\n  Number of ethernet segments: 0<\/pre>\n<h6><\/h6>\n<pre class=\"lang:sh decode:true \">root@vMX01&gt; show route table evpn100.evpn.0 \r\n\r\nevpn100.evpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)\r\n+ = Active Route, - = Last Active, * = Both\r\n\r\n2:1.1.1.1:100::100::00:0c:29:27:c9:a1\/304               \r\n                   *[EVPN\/170] 00:00:56\r\n                      Indirect\r\n3:1.1.1.1:100::100::1.1.1.1\/304               \r\n                   *[EVPN\/170] 6d 22:38:21\r\n                      Indirect\r\n3:1.1.1.1:100::100::2.2.2.2\/304               \r\n                   *[BGP\/170] 00:00:57, localpref 100, from 2.2.2.2\r\n                      AS path: I, validation-state: unverified\r\n                    &gt; to 10.10.30.2 via ge-0\/0\/1.0, Push 16\r\n<\/pre>\n<h6><\/h6>\n<h6>Juniper vMX &#8211; vmx01<\/h6>\n<p>&nbsp;<\/p>\n<pre class=\"lang:sh decode:true\">root@vMX02&gt; show l2-learning vxlan-tunnel-end-point source \r\nLogical System Name       Id  SVTEP-IP         IFL   L3-Idx\r\n&lt;default&gt;                 0   2.2.2.2          lo0.0    0  \r\n    L2-RTT                   Bridge Domain              VNID     MC-Group-IP\r\n    evpn100                  __evpn100__                6666     239.100.100.100<\/pre>\n<pre class=\"lang:sh decode:true\">root@vMX02&gt; show l2-learning vxlan-tunnel-end-point remote \r\nLogical System Name       Id  SVTEP-IP         IFL   L3-Idx\r\n&lt;default&gt;                 0   2.2.2.2          lo0.0    0  \r\n RVTEP-IP         IFL-Idx   NH-Id\r\n 10.10.20.1       347       1644     \r\n    VNID          MC-Group-IP      \r\n    6666          239.100.100.100 \r\n<\/pre>\n<h4><\/h4>\n<pre class=\"lang:sh decode:true \">root@vMX02&gt; show evpn instance evpn100 extensive    \r\nInstance: evpn100\r\n  Route Distinguisher: 1.1.1.1:100\r\n  VLAN ID: 100\r\n  Per-instance MAC route label: 299776\r\n  MAC database status                Local  Remote\r\n    Total MAC addresses:                 1       0\r\n    Default gateway MAC addresses:       0       0\r\n  Number of local interfaces: 3 (3 up)\r\n    Interface name  ESI                            Mode             Status\r\n    ge-0\/0\/2.0      00:00:00:00:00:00:00:00:00:00  single-homed     Up    \r\n    vtep.32769      00:00:00:00:00:00:00:00:00:00  single-homed     Up    \r\n    vtep.32772                                                      Up    \r\n  Number of IRB interfaces: 0 (0 up)\r\n  Number of bridge domains: 1\r\n    VLAN ID  Intfs \/ up    Mode             MAC sync  IM route label\r\n    100          1   1     Extended         Enabled   299872 \r\n  Number of neighbors: 1\r\n    1.1.1.1\r\n      Received routes\r\n        MAC address advertisement:              0\r\n        MAC+IP address advertisement:           0\r\n        Inclusive multicast:                    1\r\n        Ethernet auto-discovery:                0\r\n  Number of ethernet segments: 0<\/pre>\n<p>&nbsp;<\/p>\n<pre class=\"lang:sh decode:true \">root@vMX02&gt; show route table evpn100.evpn.0 \r\n\r\nevpn100.evpn.0: 3 destinations, 4 routes (3 active, 0 holddown, 0 hidden)\r\n+ = Active Route, - = Last Active, * = Both\r\n\r\n2:1.1.1.1:100::100::00:0c:29:27:c9:a1\/304               \r\n                   *[BGP\/170] 00:01:32, localpref 100, from 1.1.1.1\r\n                      AS path: I, validation-state: unverified\r\n                    &gt; to 10.10.40.2 via ge-0\/0\/1.0, Push 17\r\n                    [EVPN\/170] 00:01:26\r\n                      Indirect\r\n3:1.1.1.1:100::100::1.1.1.1\/304               \r\n                   *[BGP\/170] 00:01:33, localpref 100, from 1.1.1.1\r\n                      AS path: I, validation-state: unverified\r\n                    &gt; to 10.10.40.2 via ge-0\/0\/1.0, Push 17\r\n3:1.1.1.1:100::100::2.2.2.2\/304               \r\n                   *[EVPN\/170] 1w1d 04:04:37\r\n                      Indirect<\/pre>\n<h4>Przypadek 2<\/h4>\n<p>Rysunek pogl\u0105dowy:<\/p>\n<p><a href=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/p2.png\"><img data-recalc-dims=\"1\" loading=\"lazy\" decoding=\"async\" data-attachment-id=\"830\" data-permalink=\"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/attachment\/p2\/\" data-orig-file=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/p2.png?fit=1237%2C501&amp;ssl=1\" data-orig-size=\"1237,501\" data-comments-opened=\"0\" data-image-meta=\"{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;}\" data-image-title=\"p2\" data-image-description=\"\" data-image-caption=\"\" data-large-file=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/p2.png?fit=770%2C312&amp;ssl=1\" class=\"alignnone size-full wp-image-830\" src=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/p2.png?resize=770%2C312\" alt=\"p2\" width=\"770\" height=\"312\" srcset=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/p2.png?w=1237&amp;ssl=1 1237w, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/p2.png?resize=300%2C122&amp;ssl=1 300w, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/p2.png?resize=768%2C311&amp;ssl=1 768w, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/p2.png?resize=1024%2C415&amp;ssl=1 1024w\" sizes=\"auto, (max-width: 770px) 100vw, 770px\" \/><\/a><\/p>\n<p>Na urz\u0105dzeniach Cisco ASAv uruchomione s\u0105 interfejsy vni 1100. Vxlan ten zostanie rozci\u0105gni\u0119ty przez dwa urz\u0105dzenia Juniper vMX (vmx01 i vmx02). Dla tego przypadku uruchomi\u0119 Routing instancj\u0119 typu virtual-switch. W celach testowych na ka\u017cdym vMX zostanie uruchomiony w tej adresacji interfejs irb\u00a0w celu sprawdzenia\u00a0czy wszystko odpowiednio dzia\u0142a.<\/p>\n<p>Poni\u017cej konfiguracja:<\/p>\n<h6>Juniper vMX &#8211; vmx01<\/h6>\n<pre class=\"lang:sh decode:true \">set routing-instances evpn210 vtep-source-interface lo0.0\r\nset routing-instances evpn210 instance-type virtual-switch\r\nset routing-instances evpn210 route-distinguisher 1.1.1.1:210\r\nset routing-instances evpn210 vrf-target target:210:210\r\nset routing-instances evpn210 protocols evpn extended-vlan-list 210\r\nset routing-instances evpn210 bridge-domains vxvlan_a domain-type bridge\r\nset routing-instances evpn210 bridge-domains vxvlan_a vlan-id 210\r\nset routing-instances evpn210 bridge-domains vxvlan_a routing-interface irb.110\r\nset routing-instances evpn210 bridge-domains vxvlan_a vxlan vni 1100\r\nset routing-instances evpn210 bridge-domains vxvlan_a vxlan multicast-group 239.110.110.110\r\nset routing-instances evpn210 bridge-domains vxvlan_a vxlan encapsulate-inner-vlan\r\nset routing-instances evpn210 bridge-domains vxvlan_a vxlan decapsulate-accept-inner-vlan\r\nset routing-instances evpn210 bridge-domains vxvlan_a vxlan unreachable-vtep-aging-timer 300<\/pre>\n<p>Interfejs irb.110<\/p>\n<pre class=\"lang:sh decode:true\">set interfaces irb unit 110 family inet address 172.16.110.100\/24<\/pre>\n<h6>Juniper vMX &#8211; vmx02<\/h6>\n<pre class=\"lang:sh decode:true\">set routing-instances evpn210 vtep-source-interface lo0.0\r\nset routing-instances evpn210 instance-type virtual-switch\r\nset routing-instances evpn210 route-distinguisher 2.2.2.2:210\r\nset routing-instances evpn210 vrf-target target:210:210\r\nset routing-instances evpn210 protocols evpn extended-vlan-list 210\r\nset routing-instances evpn210 bridge-domains vxvlan_a domain-type bridge\r\nset routing-instances evpn210 bridge-domains vxvlan_a vlan-id 210\r\nset routing-instances evpn210 bridge-domains vxvlan_a routing-interface irb.110\r\nset routing-instances evpn210 bridge-domains vxvlan_a vxlan vni 1100\r\nset routing-instances evpn210 bridge-domains vxvlan_a vxlan multicast-group 239.110.110.110\r\nset routing-instances evpn210 bridge-domains vxvlan_a vxlan encapsulate-inner-vlan\r\nset routing-instances evpn210 bridge-domains vxvlan_a vxlan decapsulate-accept-inner-vlan\r\nset routing-instances evpn210 bridge-domains vxvlan_a vxlan unreachable-vtep-aging-timer 300<\/pre>\n<p>Interfejs irb.110<\/p>\n<pre class=\"lang:sh decode:true\">set interfaces irb unit 110 family inet address 172.16.110.101\/24<\/pre>\n<h6>Cisco ASAv &#8211; vtep01<\/h6>\n<pre class=\"lang:sh decode:true\">nve 1\r\n encapsulation vxlan\r\n source-interface lan120<\/pre>\n<pre class=\"lang:sh decode:true\">interface vni1100\r\n mac-address 000a.0100.1000\r\n segment-id 1100\r\n nameif vxvlan1100\r\n security-level 0\r\n ip address 172.16.110.10 255.255.255.0 \r\n vtep-nve 1\r\n mcast-group 239.110.110.110<\/pre>\n<p>Zauwa\u017cy\u0142em, gdy mamy uruchomione oba przypadki na urz\u0105dzeniach warto jest wy\u0142\u0105czy\u0107 PIM na interfejsie kt\u00f3ry jest pod\u0142\u0105czony do sieci vxvlan6666<\/p>\n<pre class=\"lang:sh decode:true\">interface GigabitEthernet0\/0.100\r\nno pim<\/pre>\n<h6>Cisco ASAv &#8211; vtep02<\/h6>\n<pre class=\"lang:sh decode:true\">nve 1\r\n encapsulation vxlan\r\n source-interface vlan130<\/pre>\n<pre class=\"lang:sh decode:true\">interface vni1100\r\n mac-address 0200.2000.2000\r\n segment-id 1100\r\n nameif vxlan1100\r\n security-level 0\r\n ip address 172.16.110.50 255.255.255.0 \r\n vtep-nve 1\r\n mcast-group 239.110.110.110<\/pre>\n<pre class=\"lang:sh decode:true\">interface GigabitEthernet0\/0.100\r\nno pim<\/pre>\n<h4>Weryfikacja:<\/h4>\n<h6><\/h6>\n<h6>Juniper vMX &#8211; vmx01<\/h6>\n<h6><\/h6>\n<pre class=\"lang:sh decode:true\">root@vMX01&gt; ping 172.16.110.100 interface irb.110 count 5 \r\nPING 172.16.110.100 (172.16.110.100): 56 data bytes\r\n64 bytes from 172.16.110.100: icmp_seq=0 ttl=64 time=34.977 ms\r\n64 bytes from 172.16.110.100: icmp_seq=1 ttl=64 time=7.735 ms\r\n64 bytes from 172.16.110.100: icmp_seq=2 ttl=64 time=12.253 ms\r\n64 bytes from 172.16.110.100: icmp_seq=3 ttl=64 time=4.926 ms\r\n64 bytes from 172.16.110.100: icmp_seq=4 ttl=64 time=20.743 ms\r\n\r\n--- 172.16.110.100 ping statistics ---\r\n5 packets transmitted, 5 packets received, 0% packet loss\r\nround-trip min\/avg\/max\/stddev = 4.926\/16.127\/34.977\/10.840 ms\r\n\r\n<\/pre>\n<p>&nbsp;<\/p>\n<pre class=\"lang:sh decode:true \">root@vMX01&gt; ping 172.16.110.101 interface irb.110 count 5 \r\nPING 172.16.110.101 (172.16.110.101): 56 data bytes\r\n64 bytes from 172.16.110.101: icmp_seq=0 ttl=64 time=0.336 ms\r\n64 bytes from 172.16.110.101: icmp_seq=1 ttl=64 time=0.098 ms\r\n64 bytes from 172.16.110.101: icmp_seq=2 ttl=64 time=0.258 ms\r\n64 bytes from 172.16.110.101: icmp_seq=3 ttl=64 time=0.061 ms\r\n64 bytes from 172.16.110.101: icmp_seq=4 ttl=64 time=0.115 ms\r\n\r\n--- 172.16.110.101 ping statistics ---\r\n5 packets transmitted, 5 packets received, 0% packet loss\r\nround-trip min\/avg\/max\/stddev = 0.061\/0.174\/0.336\/0.105 ms\r\n\r\n<\/pre>\n<p>&nbsp;<\/p>\n<pre class=\"lang:sh decode:true \">root@vMX01&gt; ping 172.16.110.10 interface irb.110 count 5 \r\nPING 172.16.110.10 (172.16.110.10): 56 data bytes\r\n64 bytes from 172.16.110.10: icmp_seq=0 ttl=255 time=61.138 ms\r\n64 bytes from 172.16.110.10: icmp_seq=1 ttl=255 time=135.056 ms\r\n64 bytes from 172.16.110.10: icmp_seq=2 ttl=255 time=8.125 ms\r\n64 bytes from 172.16.110.10: icmp_seq=3 ttl=255 time=3.897 ms\r\n64 bytes from 172.16.110.10: icmp_seq=4 ttl=255 time=6.604 ms\r\n\r\n--- 172.16.110.10 ping statistics ---\r\n5 packets transmitted, 5 packets received, 0% packet loss\r\nround-trip min\/avg\/max\/stddev = 3.897\/42.964\/135.056\/50.741 ms\r\n\r\n<\/pre>\n<p>&nbsp;<\/p>\n<pre class=\"lang:sh decode:true \">root@vMX01&gt; ping 172.16.110.50 interface irb.110 count 5 \r\nPING 172.16.110.50 (172.16.110.50): 56 data bytes\r\n64 bytes from 172.16.110.50: icmp_seq=2 ttl=254 time=10.458 ms\r\n64 bytes from 172.16.110.50: icmp_seq=3 ttl=254 time=4.962 ms\r\n64 bytes from 172.16.110.50: icmp_seq=4 ttl=254 time=77.743 ms\r\n\r\n--- 172.16.110.50 ping statistics ---\r\n5 packets transmitted, 3 packets received, 40% packet loss\r\nround-trip min\/avg\/max\/stddev = 4.962\/31.054\/77.743\/33.090 ms<\/pre>\n<pre class=\"lang:sh decode:true\">root@vMX01&gt; show route table evpn210.evpn.0 \r\n\r\nevpn210.evpn.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)\r\n+ = Active Route, - = Last Active, * = Both\r\n\r\n2:1.1.1.1:210::210::00:05:86:71:6f:f0\/304               \r\n                   *[EVPN\/170] 18:27:42\r\n                      Indirect\r\n2:1.1.1.1:210::210::00:0a:01:00:10:00\/304               \r\n                   *[EVPN\/170] 18:27:41\r\n                      Indirect\r\n2:2.2.2.2:210::210::00:05:86:71:35:f0\/304               \r\n                   *[BGP\/170] 00:15:07, localpref 100, from 2.2.2.2\r\n                      AS path: I, validation-state: unverified\r\n                    &gt; to 10.10.30.2 via ge-0\/0\/1.0, Push 16\r\n2:2.2.2.2:210::210::02:00:20:00:20:00\/304               \r\n                   *[BGP\/170] 00:15:07, localpref 100, from 2.2.2.2\r\n                      AS path: I, validation-state: unverified\r\n                    &gt; to 10.10.30.2 via ge-0\/0\/1.0, Push 16\r\n2:1.1.1.1:210::210::00:05:86:71:6f:f0::172.16.110.101\/304               \r\n                   *[EVPN\/170] 18:27:42\r\n                      Indirect\r\n2:1.1.1.1:210::210::00:0a:01:00:10:00::172.16.110.10\/304               \r\n                   *[EVPN\/170] 01:52:26\r\n                      Indirect\r\n2:2.2.2.2:210::210::00:05:86:71:35:f0::172.16.110.100\/304               \r\n                   *[BGP\/170] 00:15:07, localpref 100, from 2.2.2.2\r\n                      AS path: I, validation-state: unverified\r\n                    &gt; to 10.10.30.2 via ge-0\/0\/1.0, Push 16\r\n3:1.1.1.1:210::210::1.1.1.1\/304               \r\n                   *[EVPN\/170] 6d 19:12:17\r\n                      Indirect\r\n3:2.2.2.2:210::210::2.2.2.2\/304               \r\n                   *[BGP\/170] 00:15:07, localpref 100, from 2.2.2.2\r\n                      AS path: I, validation-state: unverified\r\n                    &gt; to 10.10.30.2 via ge-0\/0\/1.0, Push 16\r\n\t\t\t\t\t\r\n<\/pre>\n<p>&nbsp;<\/p>\n<pre class=\"lang:sh decode:true \">root@vMX01&gt; show evpn database \r\nInstance: evpn210\r\nVLAN  MAC address        Active source                  Timestamp        IP address\r\n210   00:05:86:71:35:f0  2.2.2.2                        Apr 26 08:46:43  172.16.110.100\r\n210   00:05:86:71:6f:f0  irb.110                        Apr 25 13:47:36  172.16.110.101\r\n210   00:0a:01:00:10:00  vtep.32771                     Apr 26 08:38:43  172.16.110.10\r\n210   02:00:20:00:20:00  2.2.2.2                        Apr 26 08:46:43  172.16.110.50\r\n\r\n<\/pre>\n<p>&nbsp;<\/p>\n<pre class=\"lang:sh decode:true\">root@vMX01&gt; show evpn instance evpn210 extensive \r\nInstance: evpn210\r\n  Route Distinguisher: 1.1.1.1:210\r\n  Per-instance MAC route label: 299808\r\n  MAC database status                Local  Remote\r\n    Total MAC addresses:                 2       2\r\n    Default gateway MAC addresses:       1       1\r\n  Number of local interfaces: 2 (2 up)\r\n    Interface name  ESI                            Mode             Status\r\n    vtep.32769      00:00:00:00:00:00:00:00:00:00  single-homed     Up    \r\n    vtep.32771                                                      Up    \r\n  Number of IRB interfaces: 1 (1 up)\r\n    Interface name  VLAN ID  Status  L3 context\r\n    irb.110         210      Up      master                           \r\n  Number of bridge domains: 1\r\n    VLAN ID  Intfs \/ up    Mode             MAC sync  IM route label\r\n    210          0   0     Extended         Enabled   299872 \r\n  Number of neighbors: 1\r\n    2.2.2.2\r\n      Received routes\r\n        MAC address advertisement:              2\r\n        MAC+IP address advertisement:           2\r\n        Inclusive multicast:                    1\r\n        Ethernet auto-discovery:                0\r\n  Number of ethernet segments: 0<\/pre>\n<p>&nbsp;<\/p>\n<pre class=\"lang:sh decode:true \">root@vMX01&gt; show bridge domain vxvlan_a extensive \r\n\r\nRouting instance: evpn210\r\nBridge domain: vxvlan_a                       State: Active\r\nBridge VLAN ID: 210                           EVPN extended: Yes   \r\nInterfaces:\r\n    pip-4.030010000000\r\n    vtep.32771\r\nTotal MAC count: 2 \r\n<\/pre>\n<h6><\/h6>\n<pre class=\"lang:sh decode:true\">root@vMX01&gt; show l2-learning vxlan-tunnel-end-point source    \r\nLogical System Name       Id  SVTEP-IP         IFL   L3-Idx\r\n&lt;default&gt;                 0   1.1.1.1          lo0.0    0  \r\n    L2-RTT                   Bridge Domain              VNID     MC-Group-IP\r\n    evpn100                  __evpn100__                6666     239.100.100.100\r\n    evpn210                  vxvlan_a+210               1100     239.110.110.110<\/pre>\n<h6><\/h6>\n<pre class=\"lang:sh decode:true\">vMX01 fpc0 Frame 10: sp = 0xffe0d768, pc = 0xf748c9b3 \r\nshow l2-learning vxlan-tunnel-end-point remote \r\nLogical System Name       Id  SVTEP-IP         IFL   L3-Idx\r\n&lt;default&gt;                 0   1.1.1.1          lo0.0    0  \r\n RVTEP-IP         IFL-Idx   NH-Id\r\n 10.120.10.10     347       1157     \r\n    VNID          MC-Group-IP      \r\n    1100          239.110.110.110 \r\n RVTEP-IP         IFL-Idx   NH-Id\r\n 10.10.20.1       348       1195     \r\n    VNID          MC-Group-IP      \r\n    6666          239.100.100.100<\/pre>\n<h6>Juniper vMX &#8211; vmx02<\/h6>\n<pre class=\"lang:sh decode:true \">root@vMX02&gt; ping 172.16.110.100 interface irb.110 count 5 \r\nPING 172.16.110.100 (172.16.110.100): 56 data bytes\r\n64 bytes from 172.16.110.100: icmp_seq=0 ttl=64 time=0.417 ms\r\n64 bytes from 172.16.110.100: icmp_seq=1 ttl=64 time=0.102 ms\r\n64 bytes from 172.16.110.100: icmp_seq=2 ttl=64 time=0.103 ms\r\n64 bytes from 172.16.110.100: icmp_seq=3 ttl=64 time=0.104 ms\r\n64 bytes from 172.16.110.100: icmp_seq=4 ttl=64 time=0.155 ms\r\n\r\n--- 172.16.110.100 ping statistics ---\r\n5 packets transmitted, 5 packets received, 0% packet loss\r\nround-trip min\/avg\/max\/stddev = 0.102\/0.176\/0.417\/0.122 ms\r\n\r\n<\/pre>\n<p>&nbsp;<\/p>\n<pre class=\"lang:sh decode:true \">root@vMX02&gt; ping 172.16.110.101 interface irb.110 count 5 \r\nPING 172.16.110.101 (172.16.110.101): 56 data bytes\r\n64 bytes from 172.16.110.101: icmp_seq=0 ttl=64 time=31.305 ms\r\n64 bytes from 172.16.110.101: icmp_seq=1 ttl=64 time=7.865 ms\r\n64 bytes from 172.16.110.101: icmp_seq=2 ttl=64 time=3.407 ms\r\n64 bytes from 172.16.110.101: icmp_seq=3 ttl=64 time=3.573 ms\r\n64 bytes from 172.16.110.101: icmp_seq=4 ttl=64 time=8.155 ms\r\n\r\n--- 172.16.110.101 ping statistics ---\r\n5 packets transmitted, 5 packets received, 0% packet loss\r\nround-trip min\/avg\/max\/stddev = 3.407\/10.861\/31.305\/10.420 ms\r\n\r\n<\/pre>\n<p>&nbsp;<\/p>\n<pre class=\"lang:sh decode:true \">root@vMX02&gt; ping 172.16.110.10 interface irb.110 count 5 \r\nPING 172.16.110.10 (172.16.110.10): 56 data bytes\r\n64 bytes from 172.16.110.10: icmp_seq=2 ttl=254 time=12.403 ms\r\n64 bytes from 172.16.110.10: icmp_seq=3 ttl=254 time=5.703 ms\r\n64 bytes from 172.16.110.10: icmp_seq=4 ttl=254 time=14.494 ms\r\n\r\n--- 172.16.110.10 ping statistics ---\r\n5 packets transmitted, 3 packets received, 40% packet loss\r\nround-trip min\/avg\/max\/stddev = 5.703\/10.867\/14.494\/3.750 ms\r\n\r\n<\/pre>\n<p>&nbsp;<\/p>\n<pre class=\"lang:sh decode:true \">root@vMX02&gt; ping 172.16.110.50 interface irb.110 count 5 \r\nPING 172.16.110.50 (172.16.110.50): 56 data bytes\r\n64 bytes from 172.16.110.50: icmp_seq=0 ttl=255 time=33.069 ms\r\n64 bytes from 172.16.110.50: icmp_seq=1 ttl=255 time=3.957 ms\r\n64 bytes from 172.16.110.50: icmp_seq=2 ttl=255 time=89.464 ms\r\n64 bytes from 172.16.110.50: icmp_seq=3 ttl=255 time=3.773 ms\r\n64 bytes from 172.16.110.50: icmp_seq=4 ttl=255 time=43.534 ms\r\n\r\n--- 172.16.110.50 ping statistics ---\r\n5 packets transmitted, 5 packets received, 0% packet loss\r\nround-trip min\/avg\/max\/stddev = 3.773\/34.759\/89.464\/31.564 ms<\/pre>\n<p>&nbsp;<\/p>\n<pre class=\"lang:sh decode:true \">root@vMX02&gt; show route table evpn210.evpn.0 \r\n\r\nevpn210.evpn.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)\r\n+ = Active Route, - = Last Active, * = Both\r\n\r\n2:1.1.1.1:210::210::00:05:86:71:6f:f0\/304               \r\n                   *[BGP\/170] 00:14:56, localpref 100, from 1.1.1.1\r\n                      AS path: I, validation-state: unverified\r\n                    &gt; to 10.10.40.2 via ge-0\/0\/1.0, Push 17\r\n2:1.1.1.1:210::210::00:0a:01:00:10:00\/304               \r\n                   *[BGP\/170] 00:14:56, localpref 100, from 1.1.1.1\r\n                      AS path: I, validation-state: unverified\r\n                    &gt; to 10.10.40.2 via ge-0\/0\/1.0, Push 17\r\n2:2.2.2.2:210::210::00:05:86:71:35:f0\/304               \r\n                   *[EVPN\/170] 18:28:01\r\n                      Indirect\r\n2:2.2.2.2:210::210::02:00:20:00:20:00\/304               \r\n                   *[EVPN\/170] 18:28:01\r\n                      Indirect\r\n2:1.1.1.1:210::210::00:05:86:71:6f:f0::172.16.110.101\/304               \r\n                   *[BGP\/170] 00:14:56, localpref 100, from 1.1.1.1\r\n                      AS path: I, validation-state: unverified\r\n                    &gt; to 10.10.40.2 via ge-0\/0\/1.0, Push 17\r\n2:1.1.1.1:210::210::00:0a:01:00:10:00::172.16.110.10\/304               \r\n                   *[BGP\/170] 00:14:56, localpref 100, from 1.1.1.1\r\n                      AS path: I, validation-state: unverified\r\n                    &gt; to 10.10.40.2 via ge-0\/0\/1.0, Push 17\r\n2:2.2.2.2:210::210::00:05:86:71:35:f0::172.16.110.100\/304               \r\n                   *[EVPN\/170] 18:28:01\r\n                      Indirect\r\n3:1.1.1.1:210::210::1.1.1.1\/304               \r\n                   *[BGP\/170] 00:14:56, localpref 100, from 1.1.1.1\r\n                      AS path: I, validation-state: unverified\r\n                    &gt; to 10.10.40.2 via ge-0\/0\/1.0, Push 17\r\n3:2.2.2.2:210::210::2.2.2.2\/304               \r\n                   *[EVPN\/170] 1w0d 17:52:07\r\n                      Indirect\r\n\t\t\t\t\t  \r\n<\/pre>\n<pre class=\"lang:sh decode:true\">root@vMX02&gt; show evpn database    \r\nInstance: evpn210\r\nVLAN  MAC address        Active source                  Timestamp        IP address\r\n210   00:05:86:71:35:f0  irb.110                        Apr 25 15:23:07  172.16.110.100\r\n210   00:05:86:71:6f:f0  1.1.1.1                        Apr 26 10:23:12  172.16.110.101\r\n210   00:0a:01:00:10:00  1.1.1.1                        Apr 26 10:23:12  172.16.110.10\r\n210   02:00:20:00:20:00  vtep.32771                     Apr 26 10:15:14  172.16.110.50\r\n<\/pre>\n<p>&nbsp;<\/p>\n<pre class=\"lang:sh decode:true\">root@vMX02&gt; show bridge domain vxvlan_a extensive \r\n\r\nRouting instance: evpn210\r\nBridge domain: vxvlan_a                       State: Active\r\nBridge VLAN ID: 210                           EVPN extended: Yes   \r\nInterfaces:\r\n    pip-10.010010000000\r\n    vtep.32771\r\nTotal MAC count: 2 \r\n<\/pre>\n<p>&nbsp;<\/p>\n<pre class=\"lang:sh decode:true\">root@vMX02&gt; show evpn instance evpn210 extensive \r\nInstance: evpn210\r\n  Route Distinguisher: 2.2.2.2:210\r\n  Per-instance MAC route label: 300336\r\n  MAC database status                Local  Remote\r\n    Total MAC addresses:                 2       2\r\n    Default gateway MAC addresses:       1       1\r\n  Number of local interfaces: 2 (2 up)\r\n    Interface name  ESI                            Mode             Status\r\n    vtep.32770      00:00:00:00:00:00:00:00:00:00  single-homed     Up    \r\n    vtep.32771                                                      Up    \r\n  Number of IRB interfaces: 1 (1 up)\r\n    Interface name  VLAN ID  Status  L3 context\r\n    irb.110         210      Up      master                           \r\n  Number of bridge domains: 1\r\n    VLAN ID  Intfs \/ up    Mode             MAC sync  IM route label\r\n    210          0   0     Extended         Enabled   300384 \r\n  Number of neighbors: 1\r\n    1.1.1.1\r\n      Received routes\r\n        MAC address advertisement:              2\r\n        MAC+IP address advertisement:           2\r\n        Inclusive multicast:                    1\r\n        Ethernet auto-discovery:                0\r\n  Number of ethernet segments: 0<\/pre>\n<h6><\/h6>\n<pre class=\"lang:sh decode:true\">root@vMX02&gt; show l2-learning vxlan-tunnel-end-point source \r\nLogical System Name       Id  SVTEP-IP         IFL   L3-Idx\r\n&lt;default&gt;                 0   2.2.2.2          lo0.0    0  \r\n    L2-RTT                   Bridge Domain              VNID     MC-Group-IP\r\n    evpn100                  __evpn100__                6666     239.100.100.100\r\n    evpn210                  vxvlan_a+210               1100     239.110.110.110<\/pre>\n<h6><\/h6>\n<pre class=\"lang:sh decode:true \">root@vMX02&gt; show l2-learning vxlan-tunnel-end-point remote \r\nLogical System Name       Id  SVTEP-IP         IFL   L3-Idx\r\n&lt;default&gt;                 0   2.2.2.2          lo0.0    0  \r\n RVTEP-IP         IFL-Idx   NH-Id\r\n 10.10.20.1       347       1644     \r\n    VNID          MC-Group-IP      \r\n    6666          239.100.100.100 \r\n RVTEP-IP         IFL-Idx   NH-Id\r\n 10.130.10.10     346       1591     \r\n    VNID          MC-Group-IP      \r\n    1100          239.110.110.110<\/pre>\n<h6>Cisco ASAv &#8211; vtep01<\/h6>\n<pre class=\"lang:sh decode:true \">vtep01# ping 172.16.110.50\r\nType escape sequence to abort.\r\nSending 5, 100-byte ICMP Echos to 172.16.110.50, timeout is 2 seconds:\r\n!!!!!\r\nSuccess rate is 100 percent (5\/5), round-trip min\/avg\/max = 1\/44\/100 ms\r\n<\/pre>\n<h6><\/h6>\n<pre class=\"lang:sh decode:true \">vtep01# ping 172.16.110.100\r\nType escape sequence to abort.\r\nSending 5, 100-byte ICMP Echos to 172.16.110.100, timeout is 2 seconds:\r\n!!!!!\r\nSuccess rate is 100 percent (5\/5), round-trip min\/avg\/max = 10\/16\/30 ms\r\n<\/pre>\n<h6><\/h6>\n<pre class=\"lang:sh decode:true \">vtep01# ping 172.16.110.101\r\nType escape sequence to abort.\r\nSending 5, 100-byte ICMP Echos to 172.16.110.101, timeout is 2 seconds:\r\n!!!!!\r\nSuccess rate is 100 percent (5\/5), round-trip min\/avg\/max = 1\/6\/10 ms\r\n<\/pre>\n<h6><\/h6>\n<pre class=\"lang:sh decode:true \">vtep01# ping 172.16.110.10\r\nType escape sequence to abort.\r\nSending 5, 100-byte ICMP Echos to 172.16.110.10, timeout is 2 seconds:\r\n!!!!!\r\nSuccess rate is 100 percent (5\/5), round-trip min\/avg\/max = 1\/1\/1 ms<\/pre>\n<pre class=\"lang:sh decode:true \">vtep01# show arp\r\n        lan120 10.120.10.1 000c.2960.d9e1 221\r\n        vxvlan1100 172.16.110.100 0005.8671.35f0 580\r\n        vxvlan1100 172.16.110.101 0005.8671.6ff0 2633\r\n        vxvlan1100 172.16.110.50 0200.2000.2000 11991<\/pre>\n<p>&nbsp;<\/p>\n<pre class=\"lang:sh decode:true \">vtep01# show nve 1\r\nnve 1, source-interface \"lan120\" is up\r\n IP address 10.120.10.10, subnet mask 255.255.255.0\r\n Encapsulation: vxlan\r\n Encapsulated traffic statistics:\r\n   2395 packets input, 172218 bytes\r\n   3178 packets output, 327966 bytes\r\n   0 packets dropped\r\n Number of configured static peer VTEPs: 0\r\n Number of discovered peer VTEPs: 1\r\n    Discovered peer VTEPs:\r\n        IP address 1.1.1.1\r\n Number of VNIs attached to nve 1: 1\r\n VNIs attached:\r\n        vni 1100: segment-id 1100, mcast-group 239.110.110.110<\/pre>\n<h6><\/h6>\n<h6>Cisco ASAv &#8211; vtep02<\/h6>\n<pre class=\"lang:sh decode:true \">vtep02# ping 172.16.110.50\r\nType escape sequence to abort.\r\nSending 5, 100-byte ICMP Echos to 172.16.110.50, timeout is 2 seconds:\r\n!!!!!\r\nSuccess rate is 100 percent (5\/5), round-trip min\/avg\/max = 1\/1\/1 ms\r\n<\/pre>\n<p>&nbsp;<\/p>\n<pre class=\"lang:sh decode:true \">vtep02# ping 172.16.110.100\r\nType escape sequence to abort.\r\nSending 5, 100-byte ICMP Echos to 172.16.110.100, timeout is 2 seconds:\r\n!!!!!\r\nSuccess rate is 100 percent (5\/5), round-trip min\/avg\/max = 1\/8\/10 ms\r\n<\/pre>\n<p>&nbsp;<\/p>\n<pre class=\"lang:sh decode:true \">vtep02# ping 172.16.110.101\r\nType escape sequence to abort.\r\nSending 5, 100-byte ICMP Echos to 172.16.110.101, timeout is 2 seconds:\r\n!!!!!\r\nSuccess rate is 100 percent (5\/5), round-trip min\/avg\/max = 10\/22\/50 ms\r\n<\/pre>\n<p>&nbsp;<\/p>\n<pre class=\"lang:sh decode:true \">vtep02# ping 172.16.110.10\r\nType escape sequence to abort.\r\nSending 5, 100-byte ICMP Echos to 172.16.110.10, timeout is 2 seconds:\r\n!!!!!\r\nSuccess rate is 100 percent (5\/5), round-trip min\/avg\/max = 1\/16\/50 ms<\/pre>\n<pre class=\"lang:sh decode:true \">vtep02# ping 172.16.110.10\r\nType escape sequence to abort.\r\nSending 5, 100-byte ICMP Echos to 172.16.110.10, timeout is 2 seconds:\r\n!!!!!\r\nSuccess rate is 100 percent (5\/5), round-trip min\/avg\/max = 1\/16\/50 ms<\/pre>\n<pre class=\"lang:sh decode:true \">vtep02# show arp \r\n        vlan130 10.130.10.1 000c.29a6.9bf5 168\r\n        vxlan1100 172.16.110.100 0005.8671.35f0 533\r\n        vxlan1100 172.16.110.101 0005.8671.6ff0 2586\r\n        vxlan1100 172.16.110.10 000a.0100.1000 11944<\/pre>\n<p>&nbsp;<\/p>\n<pre class=\"lang:sh decode:true \">vtep02# show nve 1\r\nnve 1, source-interface \"vlan130\" is up\r\n IP address 10.130.10.10, subnet mask 255.255.255.0\r\n Encapsulation: vxlan\r\n Encapsulated traffic statistics:\r\n   2906 packets input, 194732 bytes\r\n   2504 packets output, 271072 bytes\r\n   0 packets dropped\r\n Number of configured static peer VTEPs: 0\r\n Number of discovered peer VTEPs: 1\r\n    Discovered peer VTEPs:\r\n        IP address 2.2.2.2\r\n Number of VNIs attached to nve 1: 1\r\n VNIs attached:\r\n        vni 1100: segment-id 1100, mcast-group 239.110.110.110<\/pre>\n<p>Mam nadziej\u0119, \u017ce komu\u015b si\u0119 przyda i gratuluj\u0119 temu, kto dotar\u0142 do ko\u0144ca tego wpisu \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"<p>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 wirtualizacji networku\u00a0tym bardziej kiedy coraz [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":571,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_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":"Vxlan w Labie podej\u015bcie drugie- Tym razem z wykorzystaniem Juniper vMX","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[4,5,84],"tags":[157,218,225,226,231,162,196,217,223,238,210,236,237,221,234,230,233,219,232,228,201,198,229,227,200,235,240,277,239,195,220,207],"class_list":["post-782","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cisco","category-juniper","category-lab","tag-asav","tag-bgp","tag-bridegedomain","tag-bridge","tag-bridge-domains","tag-cisco-asav","tag-cisco-csr1000v","tag-evpn","tag-evpn-bgp","tag-how-to-configure-vxvlan-with-evpn","tag-juniper-vmx","tag-juniper-vxlan","tag-juniper-vxlan-evpn","tag-juniper-vxvlan-evpn","tag-ldp","tag-mcast-group","tag-mpls","tag-mulitcast","tag-multicast-group","tag-nve","tag-ospf","tag-pim","tag-segment-id","tag-vmx-vxvlan-evpn","tag-vtep","tag-vxlan","tag-vxlan-evpn","tag-vxlan-juniper","tag-vxlan-multicast","tag-vxvlan","tag-vxvlan-evpn","tag-vxvlan-multicast"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.6 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>LAB vxlan - Juniper vMX i Cisco CSR1kv oraz ASAv - 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-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"LAB vxlan - Juniper vMX i Cisco CSR1kv oraz ASAv - SafeKom Blog\" \/>\n<meta property=\"og:description\" content=\"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 wirtualizacji networku\u00a0tym bardziej kiedy coraz [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/\" \/>\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-26T16:07:05+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2016-06-24T13:08:18+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/02\/Juniper-Networks-and-Cisco-Systems.png?fit=712%2C534&ssl=1\" \/>\n\t<meta property=\"og:image:width\" content=\"712\" \/>\n\t<meta property=\"og:image:height\" content=\"534\" \/>\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=\"30 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-vxlan-juniper-vmx-i-cisco-csr1kv-asav\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.safekom.pl\\\/blog\\\/cisco\\\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\\\/\"},\"author\":{\"name\":\"Micha\u0142 Iwa\u0144czuk\",\"@id\":\"https:\\\/\\\/www.safekom.pl\\\/blog\\\/#\\\/schema\\\/person\\\/fd4cc931b624af4b7353d36d92ba7181\"},\"headline\":\"LAB vxlan &#8211; Juniper vMX i Cisco CSR1kv oraz ASAv\",\"datePublished\":\"2016-04-26T16:07:05+00:00\",\"dateModified\":\"2016-06-24T13:08:18+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.safekom.pl\\\/blog\\\/cisco\\\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\\\/\"},\"wordCount\":838,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.safekom.pl\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.safekom.pl\\\/blog\\\/cisco\\\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/i0.wp.com\\\/www.safekom.pl\\\/blog\\\/wp-content\\\/uploads\\\/2016\\\/02\\\/Juniper-Networks-and-Cisco-Systems.png?fit=712%2C534&ssl=1\",\"keywords\":[\"asav\",\"bgp\",\"bridegedomain\",\"bridge\",\"bridge-domains\",\"cisco asav\",\"Cisco CSR1000v\",\"evpn\",\"evpn bgp\",\"how to configure vxvlan with evpn\",\"juniper vmx\",\"juniper vxlan\",\"juniper vxlan evpn\",\"juniper vxvlan evpn\",\"ldp\",\"mcast-group\",\"mpls\",\"mulitcast\",\"multicast-group\",\"nve\",\"ospf\",\"pim\",\"segment-id\",\"vmx vxvlan evpn\",\"vtep\",\"vxlan\",\"vxlan evpn\",\"vxlan juniper\",\"vxlan multicast\",\"vxvlan\",\"vxvlan evpn\",\"vxvlan multicast\"],\"articleSection\":[\"Cisco\",\"Juniper\",\"Lab\"],\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.safekom.pl\\\/blog\\\/cisco\\\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.safekom.pl\\\/blog\\\/cisco\\\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\\\/\",\"url\":\"https:\\\/\\\/www.safekom.pl\\\/blog\\\/cisco\\\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\\\/\",\"name\":\"LAB vxlan - Juniper vMX i Cisco CSR1kv oraz ASAv - SafeKom Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.safekom.pl\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.safekom.pl\\\/blog\\\/cisco\\\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.safekom.pl\\\/blog\\\/cisco\\\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/i0.wp.com\\\/www.safekom.pl\\\/blog\\\/wp-content\\\/uploads\\\/2016\\\/02\\\/Juniper-Networks-and-Cisco-Systems.png?fit=712%2C534&ssl=1\",\"datePublished\":\"2016-04-26T16:07:05+00:00\",\"dateModified\":\"2016-06-24T13:08:18+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.safekom.pl\\\/blog\\\/cisco\\\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\\\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.safekom.pl\\\/blog\\\/cisco\\\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\\\/\\\/www.safekom.pl\\\/blog\\\/cisco\\\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\\\/#primaryimage\",\"url\":\"https:\\\/\\\/i0.wp.com\\\/www.safekom.pl\\\/blog\\\/wp-content\\\/uploads\\\/2016\\\/02\\\/Juniper-Networks-and-Cisco-Systems.png?fit=712%2C534&ssl=1\",\"contentUrl\":\"https:\\\/\\\/i0.wp.com\\\/www.safekom.pl\\\/blog\\\/wp-content\\\/uploads\\\/2016\\\/02\\\/Juniper-Networks-and-Cisco-Systems.png?fit=712%2C534&ssl=1\",\"width\":712,\"height\":534},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.safekom.pl\\\/blog\\\/cisco\\\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Strona g\u0142\u00f3wna\",\"item\":\"https:\\\/\\\/www.safekom.pl\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"LAB vxlan &#8211; Juniper vMX i Cisco CSR1kv oraz ASAv\"}]},{\"@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:\\\/\\\/secure.gravatar.com\\\/avatar\\\/cc6dda4ee8d21d1f254147e5ee6f5e38881b88a4a12a5774ca42380597e52014?s=96&d=mm&r=g\",\"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 vxlan - Juniper vMX i Cisco CSR1kv oraz ASAv - 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-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/","og_locale":"pl_PL","og_type":"article","og_title":"LAB vxlan - Juniper vMX i Cisco CSR1kv oraz ASAv - SafeKom Blog","og_description":"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 wirtualizacji networku\u00a0tym bardziej kiedy coraz [&hellip;]","og_url":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/","og_site_name":"SafeKom Blog","article_publisher":"https:\/\/www.facebook.com\/safekompl","article_published_time":"2016-04-26T16:07:05+00:00","article_modified_time":"2016-06-24T13:08:18+00:00","og_image":[{"width":712,"height":534,"url":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/02\/Juniper-Networks-and-Cisco-Systems.png?fit=712%2C534&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":"30 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/#article","isPartOf":{"@id":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/"},"author":{"name":"Micha\u0142 Iwa\u0144czuk","@id":"https:\/\/www.safekom.pl\/blog\/#\/schema\/person\/fd4cc931b624af4b7353d36d92ba7181"},"headline":"LAB vxlan &#8211; Juniper vMX i Cisco CSR1kv oraz ASAv","datePublished":"2016-04-26T16:07:05+00:00","dateModified":"2016-06-24T13:08:18+00:00","mainEntityOfPage":{"@id":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/"},"wordCount":838,"commentCount":0,"publisher":{"@id":"https:\/\/www.safekom.pl\/blog\/#organization"},"image":{"@id":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/#primaryimage"},"thumbnailUrl":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/02\/Juniper-Networks-and-Cisco-Systems.png?fit=712%2C534&ssl=1","keywords":["asav","bgp","bridegedomain","bridge","bridge-domains","cisco asav","Cisco CSR1000v","evpn","evpn bgp","how to configure vxvlan with evpn","juniper vmx","juniper vxlan","juniper vxlan evpn","juniper vxvlan evpn","ldp","mcast-group","mpls","mulitcast","multicast-group","nve","ospf","pim","segment-id","vmx vxvlan evpn","vtep","vxlan","vxlan evpn","vxlan juniper","vxlan multicast","vxvlan","vxvlan evpn","vxvlan multicast"],"articleSection":["Cisco","Juniper","Lab"],"inLanguage":"pl-PL","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/","url":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/","name":"LAB vxlan - Juniper vMX i Cisco CSR1kv oraz ASAv - SafeKom Blog","isPartOf":{"@id":"https:\/\/www.safekom.pl\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/#primaryimage"},"image":{"@id":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/#primaryimage"},"thumbnailUrl":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/02\/Juniper-Networks-and-Cisco-Systems.png?fit=712%2C534&ssl=1","datePublished":"2016-04-26T16:07:05+00:00","dateModified":"2016-06-24T13:08:18+00:00","breadcrumb":{"@id":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/"]}]},{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/#primaryimage","url":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/02\/Juniper-Networks-and-Cisco-Systems.png?fit=712%2C534&ssl=1","contentUrl":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/02\/Juniper-Networks-and-Cisco-Systems.png?fit=712%2C534&ssl=1","width":712,"height":534},{"@type":"BreadcrumbList","@id":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Strona g\u0142\u00f3wna","item":"https:\/\/www.safekom.pl\/blog\/"},{"@type":"ListItem","position":2,"name":"LAB vxlan &#8211; Juniper vMX i Cisco CSR1kv oraz ASAv"}]},{"@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:\/\/secure.gravatar.com\/avatar\/cc6dda4ee8d21d1f254147e5ee6f5e38881b88a4a12a5774ca42380597e52014?s=96&d=mm&r=g","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\/2016\/02\/Juniper-Networks-and-Cisco-Systems.png?fit=712%2C534&ssl=1","jetpack_shortlink":"https:\/\/wp.me\/p7i9ri-cC","jetpack-related-posts":[{"id":2657,"url":"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/","url_meta":{"origin":782,"position":0},"title":"NSX-T EVPN","author":"Micha\u0142 Iwa\u0144czuk","date":"28.04.2020","format":false,"excerpt":"W poprzednim wpisie pokaza\u0142em jak skonfigurowa\u0107 DVS z NSX-t, dzi\u015b przedstawi\u0119 bardzo ciekaw\u0105 now\u0105 funkcjonalno\u015b\u0107 w NSX-T 3.0 jest to EVPN. W dokumentacji VMWare na czas pisania tego wpisu nie znalaz\u0142em za du\u017co informacji o konfiguracji, kt\u00f3r\u0105 poczyni\u0142em poni\u017cej. Mam nadziej\u0119, \u017ce przyda si\u0119 Wam ta wiedza. Co to jest\u2026","rel":"","context":"W \u201eJuniper&quot;","block_context":{"text":"Juniper","link":"https:\/\/www.safekom.pl\/blog\/category\/juniper\/"},"img":{"alt_text":"nsx-t logo","src":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2020\/04\/vmware-nsx-t.jpg?fit=551%2C218&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2020\/04\/vmware-nsx-t.jpg?fit=551%2C218&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2020\/04\/vmware-nsx-t.jpg?fit=551%2C218&ssl=1&resize=525%2C300 1.5x"},"classes":[]},{"id":693,"url":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxvlan-pierwsze-podjescie\/","url_meta":{"origin":782,"position":1},"title":"LAB &#8211; VXVLAN pierwsze podje\u015bcie","author":"Micha\u0142 Iwa\u0144czuk","date":"03.04.2016","format":false,"excerpt":"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\u2026","rel":"","context":"W \u201eCisco&quot;","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":782,"position":2},"title":"Home Lab &#8211; 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":"W \u201eLab&quot;","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":610,"url":"https:\/\/www.safekom.pl\/blog\/cisco\/asav-pierwsze-uruchomienie-w-labie\/","url_meta":{"origin":782,"position":3},"title":"ASAv &#8211; 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":"W \u201eCisco&quot;","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":739,"url":"https:\/\/www.safekom.pl\/blog\/juniper\/lab-juniper-vmx-15-1f4-pierwsze-uruchomienie\/","url_meta":{"origin":782,"position":4},"title":"Lab &#8211; Juniper vMX 15.1F4 pierwsze uruchomienie","author":"Micha\u0142 Iwa\u0144czuk","date":"12.04.2016","format":false,"excerpt":"Po d\u0142u\u017cszym czasie nie pracowania na Juniperach postanowi\u0142em do nich wr\u00f3ci\u0107, na warsztat wzi\u0105\u0142em nowe tw\u00f3r Juniper wirtualny router z serii MX. Na chwil\u0119 obecn\u0105 publicznie dost\u0119pna jest wersja\u00a015.1F4. Ze wzgl\u0119du na to, \u017ce Juniper na chwil\u0119 obecn\u0105 nie udost\u0119pnia plik\u00f3w OVA tylko gotowe dyski VMDK kt\u00f3re trzeba samemu pod\u0142\u0105czy\u0107\u2026","rel":"","context":"W \u201eJuniper&quot;","block_context":{"text":"Juniper","link":"https:\/\/www.safekom.pl\/blog\/category\/juniper\/"},"img":{"alt_text":"vmx","src":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/vmx.png?resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/vmx.png?resize=350%2C200 1x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/04\/vmx.png?resize=525%2C300 1.5x"},"classes":[]},{"id":1916,"url":"https:\/\/www.safekom.pl\/blog\/lab\/heterogeniczna-infrastruktura-sieciowa-vol-1\/","url_meta":{"origin":782,"position":5},"title":"Heterogeniczna infrastruktura sieciowa vol. 1","author":"Micha\u0142 Iwa\u0144czuk","date":"01.08.2017","format":false,"excerpt":"Ostatnio pracuj\u0119 w \u015brodowisku heterogenicznej infrastruktury sieciowej. Ale co to znaczy dzi\u015b heterogeniczna infrastruktura sieciowa jest to tw\u00f3r w kt\u00f3rym mamy kliku r\u00f3\u017cnych producent\u00f3w sprz\u0119tu. Co raz cz\u0119\u015bciej w spotykam si\u0119 z sytuacj\u0105, \u017ce dany blog funkcjonalny jest realizowany przez jakiego\u015b producenta, np. sie\u0107 WAN Sie\u0107 LAN Sie\u0107 DC z\u2026","rel":"","context":"W \u201eArista&quot;","block_context":{"text":"Arista","link":"https:\/\/www.safekom.pl\/blog\/category\/arista\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2017\/06\/cropped-logo-rastrowe-bez-t%C5%82a.png?fit=512%2C512&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]}],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.safekom.pl\/blog\/wp-json\/wp\/v2\/posts\/782","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=782"}],"version-history":[{"count":0,"href":"https:\/\/www.safekom.pl\/blog\/wp-json\/wp\/v2\/posts\/782\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.safekom.pl\/blog\/wp-json\/wp\/v2\/media\/571"}],"wp:attachment":[{"href":"https:\/\/www.safekom.pl\/blog\/wp-json\/wp\/v2\/media?parent=782"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.safekom.pl\/blog\/wp-json\/wp\/v2\/categories?post=782"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.safekom.pl\/blog\/wp-json\/wp\/v2\/tags?post=782"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}