{"id":2657,"date":"2020-04-28T09:54:48","date_gmt":"2020-04-28T08:54:48","guid":{"rendered":"https:\/\/www.safekom.pl\/blog\/?p=2657"},"modified":"2023-03-04T21:17:11","modified_gmt":"2023-03-04T20:17:11","slug":"nsx-t-evpn","status":"publish","type":"post","link":"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/","title":{"rendered":"NSX-T EVPN"},"content":{"rendered":"

W poprzednim wpisie pokaza\u0142em jak skonfigurowa\u0107 DVS z NSX-t<\/a>, dzi\u015b przedstawi\u0119 bardzo ciekaw\u0105 now\u0105 funkcjonalno\u015b\u0107 w NSX-T 3.0 jest to EVPN.<\/p>\n

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.<\/p>\n

Co to jest EVPN<\/h4>\n

W kilku prostych s\u0142owach. EVPN (Ethernet VPN) jest to standard IEEE kt\u00f3ry dostarcza nam VPN warstwy 2 i 3. W EVPNie mamy control i data plane. NSXie Multiprotokol BGP (MPBGP) jest odpowiedzialne za control plane a VXLAN data plane.<\/p>\n

Testowa architektura<\/h4>\n

Poni\u017cej przedstawiam og\u00f3ln\u0105 architektur\u0119 rozwi\u0105zania gdzie widzimy na routerze zewn\u0119trznym w tym przypadku jest to Juniper vMX mamy 2 Vrfy A i B kt\u00f3re przeka\u017cemy w sesji MP BGP do routera T0 na kt\u00f3rym zostan\u0105 rozszyte do odpowiednich VRF’\u00f3w o tej samej nazwie oraz RD. Na ko\u0144cu do tych VRF’\u00f3w zostan\u0105 pod\u0142\u0105czone routery T1 kt\u00f3re b\u0119d\u0105 mia\u0142y pod\u0142\u0105czone segmenty.
\n\"\"<\/a><\/p>\n

Wymagania i ograniczenia<\/h4>\n\n\n\n\n\n
Wymagania<\/td>\nOgraniczenia<\/td>\n<\/tr>\n
MTU min 1600 na uplinku do vMX<\/td>\nna chwil\u0119 nie znalaz\u0142em<\/td>\n<\/tr>\n
Urz\u0105dzenia musz\u0105 wspiera\u0107 MPBGP oraz EVPN type 5<\/td>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Konfiguracja EVPN<\/h4>\n

Konfiguracja NSX-T EVPN<\/h5>\n

Przygotowanie<\/h4>\n

Konfiguracja VNI POOL<\/h6>\n

Logujemy si\u0119 do NSX Managera przechodzimy do Networking –> Networking Settings nast\u0119pnie VNI Pool.\u00a0 Poola ta b\u0119dzie u\u017cywana do tworzenia po\u0142\u0105czenia EVPN
\n\"\"<\/a>
\nKlikamy ADD VNI POOL i w nowym oknie definiujemy pul\u0119 id dla VNI.
\n\"\"<\/a>
\nGdzie w Name nadajemy nazw\u0119
\nStart – ID od kt\u00f3rego rozpocznie poola
\nEND – ID do kt\u00f3rego b\u0119dzie poola VNI<\/p>\n

Konfiguracja Segmentu dla T0<\/h6>\n

Konfigurujemy Segment kt\u00f3ry b\u0119dzie stanowi\u0142 po\u0142\u0105czenie pomi\u0119dzy T0 i naszym vMXem przechodzimy do Networking nast\u0119pnie Segments.
\n\"\"<\/a>
\nKlikamy ADD Segment w nowym oknie konfigurujemy go
\n\"\"<\/a>
\nNadajemy nazw\u0119, wybieramy nasz transport zone typu Vlan, oraz nadjemy vlan id i zapisujemy.<\/p>\n

Utworzenie i konfiguracja routera T0<\/h5>\n
    \n
  1. W tym \u015brodowisku stworzy\u0142em jeden router T0 na dedykowany do tego jednym EDGE VM kt\u00f3r\u0105 przypisa\u0142em dla klastra edge-cluster-02 Nowy router zostanie stworzony na dedykowanym klastrze edge. Dla \u015brodowiska testowego uruchamiam to na jednym EDGE VM.
    \nPrzechodzimy do tworzenie routera T0,
    \n    \"\"<\/a>
    \nw nowym oknie nadajemy nazw\u0119 dla naszego Tier-0 Routera
    \n    \"\"<\/a>
    \nKlikamy save<\/li>\n
  2. Po utworzeniu routera T0 konfigurujemy interfejs Uplink do vMX. Przechodzimy do Edycji utworzonego T0 przechodzimy do Interfejs
    \n    \"\"<\/a>
    \nklikamy set i w nowym oknie klikamy ADD Interface w pierwszej kolejno\u015bci Uplink-vlan11. Tutaj mamy do skonfigurowania:
    \n– nadajemy nazw\u0119 dla interfejsu,
    \n– wybieramy Tym External,
    \n– nadajemy adres ip,
    \n– przypinamy do segmentu utworzonego na samym pocz\u0105tku.
    \n– Przypinamy na kt\u00f3rej EDGE VM ma by\u0107 przypi\u0119ty interfejs. W tym przypadku to jest jedyny edge vm kt\u00f3ry mam dost\u0119pny do tego.
    \n– ustawiamy MTU ze wzgl\u0119du \u017ce b\u0119dzie tam VXALN enkapsulacja musimy ustawi\u0107 min. 1600
    \n    \"\"<\/a><\/li>\n
  3. Konfiguracja Interfejsu loopback
    \nTeraz utworzymy interfejs loopback kt\u00f3ry b\u0119dzie s\u0142u\u017cy\u0142 nam do zapinania sesji EVPN pomi\u0119dzy T0 a vMX’em
    \n    \"\"<\/a><\/li>\n
  4. Konfiguracja EVPN
    \nPrzechodzimy do EVPN Settings gdzie w VNI Pool wybieramy nasz profil dla VNI kt\u00f3ry wcze\u015bniej utworzyli\u015bmy.
    \n    \"\"<\/a><\/li>\n
  5. EVPN Tunel Endpoint
    \nW tym sam miejscu ustawiamy EVPN Tunel Endpoint kt\u00f3ry wskazuje nasz interfejs loopback
    \n    \"\"<\/a><\/li>\n
  6. BGPKonfigurujemy s\u0105siedztwo BGP na interfejsie Uplink. W ta sesja pos\u0142u\u017cy nam do rozg\u0142oszenia adresu IP Loopback
    \nPrzechodzimy do sekcji BGP gdzie konfigurujemy:
    \n-Local AS
    \n– BGP w\u0142\u0105czamy
    \n    \"\"<\/a>
    \nPrzechodzimy do BGP Neigbors gdzie konfigurujemy s\u0105siedztwo dla Interfejsu loopback i uplink<\/li>\n
  7. Konfiguracja s\u0105siedztwa
    \nS\u0105siedztwo na interfejsie uplink poni\u017cej schemat pogl\u0105dowy:
    \n    \"\"<\/a>
    \nKonfiguracja od strony NSX-T
    \n    \"\"<\/a>
    \nschemat logiczny:
    \n    \"\"<\/a>
    \nKonfiguracja s\u0105siedztwa na interfejsie loopback
    \n    \"\"<\/a>
    \ngdzie dla tego po\u0142\u0105czenie ustawiamy dodatkowy filtr
    \n    \"\"<\/a><\/li>\n
  8. redystrybucja routingu
    \nW sekcji Route RE-DISTRBUTION konfigurujemy profil gdzie w\u0142\u0105czamy takie jak poni\u017cej redystrybucje:
    \n    \"\"<\/a>
    \nw powy\u017cszych krokach mamy skonfigurowane po\u0142\u0105czenie oraz sesje BGP z vMX’em<\/li>\n<\/ol>\n
    Konfiguracja routera VRF A<\/h5>\n
      \n
    1. utworzenie routera VRF1
      \nprzechodzimy do Networking Tier-0 Gateways wybieramy ADD Gateway i wybieramy VRF
      \n      \"\"<\/a><\/li>\n
    2. Konfiguracja VRF
      \nW nowym oknie konfigurujemy nazw\u0119 dla VRFu do kt\u00f3rego T0 zostanie pod\u0142\u0105czony, Nadajemy unikalny RD(Route Distinguisher) oraz wybieramy ID VNI kt\u00f3ry b\u0119dzie s\u0142u\u017cy\u0142 do tunelowania pomi\u0119dzy VRFem a vMXem
      \nTutaj mo\u017cna zastosowa\u0107 metod\u0119 dla RD \u017ce jest w formacie AS:VNI
      \n      \"\"<\/a><\/li>\n
    3. Tworzenie Interfejsu loopback w VRFie A
      \nPrzechodzimy do Edycji VRF-A
      \n      \"\"<\/a>
      \nGdzie przechodzimy do sekcji Interface i dodajemy Interfejs
      \n      \"\"<\/a><\/li>\n
    4. w\u0142\u0105czamy redystrybucj\u0119 sieci pod\u0142\u0105czonych typu loopback oraz sieci z T1
      \n      \"\"<\/a><\/li>\n<\/ol>\n

      VRF B potarzamy powy\u017csze korki tylko zmieniamy dane zgodnie z rysunkiem
      \n      \"\"<\/a><\/p>\n

       <\/p>\n

      Router T1<\/h6>\n

      Do ka\u017cdego VRF’u zostanie pod\u0142\u0105czony nie zale\u017cny router T1 a ka\u017cdy router T1 b\u0119dzie mia\u0142 pod\u0142\u0105czony jeden segment.<\/p>\n

        \n
      1. Tworzymy router T1
        \n        \"\"<\/a><\/li>\n
      2. w\u0142\u0105czamy rozg\u0142aszanie pod\u0142\u0105czonych segment\u00f3w
        \n        \"\"<\/a><\/li>\n
      3. Tworzymy segment pod\u0142\u0105czony do T1
        \n        \"\"<\/a><\/li>\n<\/ol>\n

        Powy\u017csze kroki powtarzamy dla routera T1 pod\u0142\u0105czonego do VRFu B<\/p>\n

        Konfiguracja vMX’a<\/h4>\n
          \n
        1. Konfiguracja Interfejsu ge-0\/0\/0.11 do T0.
          \nKonfigurujemy po\u0142\u0105czenie pomi\u0119dzy T0 i vMX oraz na interfejsie w\u0142\u0105czamy MTU 9K.<\/p>\n
          set interfaces ge-0\/0\/0 vlan-tagging\r\nset interfaces ge-0\/0\/0 mtu 9000\r\nset interfaces ge-0\/0\/0 unit 11 vlan-id 11\r\nset interfaces ge-0\/0\/0 unit 11 family inet address 192.168.10.1\/24<\/pre>\n<\/li>\n
        2. Konfiguracja interfejsu loopback 0.\n
          set interfaces lo0 unit 0 family inet address 10.11.10.2\/32<\/pre>\n
          Konfigurujemy interfejsy kt\u00f3re b\u0119d\u0105 dodane do VRF’\u00f3w A i B.<\/p>\n
          set interfaces lo0 unit 100 family inet address 172.30.100.2\/32\r\nset interfaces lo0 unit 101 family inet address 192.168.100.2\/32<\/pre>\n<\/li>\n
        3. Konfiguracja sesji BGP
          \nW pierwszym kroku konfigurujemy sesj\u0119 BGP na interfejsie uplink vlan 11 kt\u00f3ry \u0142\u0105czy vMX i T0<\/p>\n
          set protocols bgp group T0 type internal\r\nset protocols bgp group T0 family inet unicast\r\nset protocols bgp group T0 peer-as 65000\r\nset protocols bgp group T0 neighbor 192.168.10.10<\/pre>\n
          w drugim korku konfigurujemy BGO pomi\u0119dzy interfejsami loopback<\/p>\n
          set protocols bgp group EVPN type internal\r\nset protocols bgp group EVPN family inet unicast\r\nset protocols bgp group EVPN family evpn signaling\r\nset protocols bgp group EVPN neighbor 10.11.10.1 local-address 10.11.10.2\r\nset protocols bgp group EVPN neighbor 10.11.10.1 peer-as 65000<\/pre>\n<\/li>\n
        4. Konfiguracja polityki eksportuj\u0105cej wszystkich sieci direct\n
          set policy-options policy-statement export_direct from protocol direct\r\nset policy-options policy-statement export_direct then accept<\/pre>\n<\/li>\n
        5. VRFy
          \nKonfiguracja VRF-A<\/p>\n
          set routing-instances vrfx-a protocols evpn ip-prefix-routes advertise direct-nexthop\r\nset routing-instances vrfx-a protocols evpn ip-prefix-routes encapsulation vxlan\r\nset routing-instances vrfx-a protocols evpn ip-prefix-routes vni 95001\r\nset routing-instances vrfx-a protocols evpn ip-prefix-routes export export_direct\r\nset routing-instances vrfx-a vtep-source-interface lo0.0\r\nset routing-instances vrfx-a instance-type vrf\r\nset routing-instances vrfx-a interface lo0.100\r\nset routing-instances vrfx-a route-distinguisher 65000:95001\r\nset routing-instances vrfx-a vrf-target target:65000:95001<\/pre>\n
          Konfiguracja VRF-B<\/p>\n
          set routing-instances vrfx-b protocols evpn ip-prefix-routes advertise direct-nexthop\r\nset routing-instances vrfx-b protocols evpn ip-prefix-routes encapsulation vxlan\r\nset routing-instances vrfx-b protocols evpn ip-prefix-routes vni 95002\r\nset routing-instances vrfx-b protocols evpn ip-prefix-routes export export_direct\r\nset routing-instances vrfx-b vtep-source-interface lo0.0\r\nset routing-instances vrfx-b instance-type vrf\r\nset routing-instances vrfx-b interface lo0.101\r\nset routing-instances vrfx-b route-distinguisher 65000:95002\r\nset routing-instances vrfx-b vrf-target target:65000:95002<\/pre>\n<\/li>\n
        6. Wykonujemy commit i przechodzimy do weryfikacji<\/li>\n<\/ol>\n
          Weryfikacja<\/h4>\n
          Weryfikacja po stronie vMX<\/h6>\n
            \n
          1. Sprawdzenie BGP\n
            root> show bgp summary \r\nThreading mode: BGP I\/O\r\nGroups: 2 Peers: 2 Down peers: 0\r\nTable          Tot Paths  Act Paths Suppressed    History Damp State    Pending\r\ninet.0               \r\n                       2          0          0          0          0          0\r\nbgp.evpn.0           \r\n                       4          4          0          0          0          0\r\nPeer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up\/Dwn State|#Active\/Received\/Accepted\/Damped...\r\n10.11.10.1            65000         30         39       0       2       10:38 Establ\r\n  inet.0: 0\/1\/1\/0\r\n  bgp.evpn.0: 4\/4\/4\/0\r\n  vrfx-a.evpn.0: 2\/2\/2\/0\r\n  vrfx-b.evpn.0: 2\/2\/2\/0\r\n192.168.10.10         65000         24         27       0       2       10:38 Establ\r\n  inet.0: 0\/1\/1\/0<\/pre>\n
            Jak widzimy sesje BGP unicast oraz evpn s\u0105 zestawione<\/li>\n
          2. Sprawdzamy tablic\u0119 routingu\n
            root> show route | no-more \r\n\r\ninet.0: 14 destinations, 16 routes (14 active, 0 holddown, 0 hidden)\r\n+ = Active Route, - = Last Active, * = Both\r\n\r\n0.0.0.0\/0          *[Static\/5] 5d 05:20:34\r\n                    >  to 10.101.9.1 via fxp0.0\r\n10.11.10.1\/32      *[Static\/5] 3d 00:51:26\r\n                    >  to 192.168.10.10 via ge-0\/0\/0.11\r\n                    [BGP\/170] 00:11:42, MED 0, localpref 100, from 10.11.10.1\r\n                      AS path: ?, validation-state: unverified\r\n                    >  to 192.168.10.10 via ge-0\/0\/0.11\r\n                    [BGP\/170] 00:11:42, MED 0, localpref 100\r\n                      AS path: ?, validation-state: unverified\r\n                    >  to 192.168.10.10 via ge-0\/0\/0.11\r\n\r\nvrfx-a.inet.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)\r\n+ = Active Route, - = Last Active, * = Both\r\n\r\n172.30.30.0\/24     *[EVPN\/170] 00:09:56\r\n                    >  to 192.168.10.10 via ge-0\/0\/0.11\r\n172.30.100.1\/32    *[EVPN\/170] 00:09:56\r\n                    >  to 192.168.10.10 via ge-0\/0\/0.11\r\n172.30.100.2\/32    *[Direct\/0] 00:14:31\r\n                    >  via lo0.100\r\n\r\nvrfx-b.inet.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)\r\n+ = Active Route, - = Last Active, * = Both\r\n\r\n192.168.2.0\/24     *[EVPN\/170] 00:08:41\r\n                    >  to 192.168.10.10 via ge-0\/0\/0.11\r\n192.168.100.1\/32   *[EVPN\/170] 00:08:41\r\n                    >  to 192.168.10.10 via ge-0\/0\/0.11\r\n192.168.100.2\/32   *[Direct\/0] 00:14:31\r\n                    >  via lo0.101\r\n\r\n.....\r\nbgp.evpn.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)\r\n+ = Active Route, - = Last Active, * = Both\r\n\r\n5:65000:95001::0::172.30.30.0::24\/248               \r\n                   *[BGP\/170] 00:33:41, MED 0, localpref 100, from 10.11.10.1\r\n                      AS path: ?, validation-state: unverified\r\n                    >  to 192.168.10.10 via ge-0\/0\/0.11\r\n5:65000:95001::0::172.30.100.1::32\/248               \r\n                   *[BGP\/170] 00:33:41, MED 0, localpref 100, from 10.11.10.1\r\n                      AS path: ?, validation-state: unverified\r\n                    >  to 192.168.10.10 via ge-0\/0\/0.11\r\n5:65000:95001::0::172.30.100.2::32\/248               \r\n                   *[EVPN\/170] 00:03:41\r\n                       Indirect\r\n5:65000:95002::0::192.168.2.0::24\/248               \r\n                   *[BGP\/170] 00:32:26, MED 0, localpref 100, from 10.11.10.1\r\n                      AS path: ?, validation-state: unverified\r\n                    >  to 192.168.10.10 via ge-0\/0\/0.11\r\n5:65000:95002::0::192.168.100.1::32\/248               \r\n                   *[BGP\/170] 00:32:26, MED 0, localpref 100, from 10.11.10.1\r\n                      AS path: ?, validation-state: unverified\r\n                    >  to 192.168.10.10 via ge-0\/0\/0.11\r\n5:65000:95002::0::192.168.100.2::32\/248               \r\n                   *[EVPN\/170] 00:03:07\r\n                       Indirect\r\n\r\nvrfx-a.evpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)\r\n+ = Active Route, - = Last Active, * = Both\r\n\r\n5:65000:95001::0::172.30.30.0::24\/248               \r\n                   *[BGP\/170] 00:00:05, MED 0, localpref 100, from 10.11.10.1\r\n                      AS path: ?, validation-state: unverified\r\n                    >  to 192.168.10.10 via ge-0\/0\/0.11\r\n5:65000:95001::0::172.30.100.1::32\/248               \r\n                   *[BGP\/170] 00:00:05, MED 0, localpref 100, from 10.11.10.1\r\n                      AS path: ?, validation-state: unverified\r\n                    >  to 192.168.10.10 via ge-0\/0\/0.11\r\n5:65000:95001::0::172.30.100.2::32\/248               \r\n                   *[EVPN\/170] 00:03:41\r\n                       Indirect\r\n\r\nvrfx-b.evpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)\r\n+ = Active Route, - = Last Active, * = Both\r\n\r\n5:65000:95002::0::192.168.2.0::24\/248               \r\n                   *[BGP\/170] 00:00:05, MED 0, localpref 100, from 10.11.10.1\r\n                      AS path: ?, validation-state: unverified\r\n                    >  to 192.168.10.10 via ge-0\/0\/0.11\r\n5:65000:95002::0::192.168.100.1::32\/248               \r\n                   *[BGP\/170] 00:00:05, MED 0, localpref 100, from 10.11.10.1\r\n                      AS path: ?, validation-state: unverified\r\n                    >  to 192.168.10.10 via ge-0\/0\/0.11\r\n5:65000:95002::0::192.168.100.2::32\/248               \r\n                   *[EVPN\/170] 00:03:07\r\n                       Indirect<\/pre>\n
            w tablicy routingu wygl\u0105da wszytko ok – jak wida\u0107 tylko w tablicy inet.0 warto od strony T0 w\u0142\u0105czy\u0107 odpowiedni filtrowanie rozg\u0142aszanych prfix\u00f3w w BGP dla loopbacka, ale to jest kosmetyka.<\/li>\n
          3. ulubiony test ping pomi\u0119dzy interfejsami loop back\n
            root> ping 192.168.100.1 routing-instance vrfx-b    \r\nPING 192.168.100.1 (192.168.100.1): 56 data bytes\r\n64 bytes from 192.168.100.1: icmp_seq=0 ttl=64 time=1.266 ms\r\n64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=1.429 ms\r\n64 bytes from 192.168.100.1: icmp_seq=2 ttl=64 time=1.347 ms\r\n64 bytes from 192.168.100.1: icmp_seq=3 ttl=64 time=1.386 ms\r\n64 bytes from 192.168.100.1: icmp_seq=4 ttl=64 time=1.698 ms\r\n64 bytes from 192.168.100.1: icmp_seq=5 ttl=64 time=1.530 ms\r\n64 bytes from 192.168.100.1: icmp_seq=6 ttl=64 time=1.450 ms\r\n^C\r\n--- 192.168.100.1 ping statistics ---\r\n7 packets transmitted, 7 packets received, 0% packet loss\r\nround-trip min\/avg\/max\/stddev = 1.266\/1.444\/1.698\/0.129 ms\r\n\r\nroot> ping 172.30.100.1 routing-instance vrfx-a  \r\nPING 172.30.100.1 (172.30.100.1): 56 data bytes\r\n64 bytes from 172.30.100.1: icmp_seq=0 ttl=64 time=1.325 ms\r\n64 bytes from 172.30.100.1: icmp_seq=1 ttl=64 time=1.249 ms\r\n64 bytes from 172.30.100.1: icmp_seq=2 ttl=64 time=1.390 ms\r\n^C\r\n--- 172.30.100.1 ping statistics ---\r\n3 packets transmitted, 3 packets received, 0% packet loss\r\nround-trip min\/avg\/max\/stddev = 1.249\/1.321\/1.390\/0.058 ms\r\n\r\n\r\n<\/pre>\n
             <\/li>\n<\/ol>\n
            Weryfikacja po stronie NSX-T<\/h6>\n
            Po stronie NSX sprawdzamy z poziomu CLI. Logujemy si\u0119 z na EDGE VM na kt\u00f3rym jest uruchomione T0
            \n1. sprawdzamy na kt\u00f3rym id jest uruchomione SR dla T0<\/p>\n
            dc1edge03> get logical-router\r\nLogical Router\r\nUUID                                   VRF    LR-ID  Name                              Type                        Ports  \r\n736a80e3-23f6-5a2d-81d6-bbefb2786666   0      0                                        TUNNEL                      4      \r\nf9414cef-e3e3-405a-a7f8-55f349e08f22   1      1026   SR-VRF-VRF-A                      VRF_SERVICE_ROUTER_TIER0    6      \r\n11ab6c6f-222b-434f-b25b-aad51dadf2ed   2      1027   SR-VRF-VRF-B                      VRF_SERVICE_ROUTER_TIER0    6      \r\n987450ee-042c-41aa-9d0d-d4fcabd44b36   3      25     SR-R-T1-VRF-A                     SERVICE_ROUTER_TIER1        5      \r\n06d10402-2066-4e4f-8243-6679d1bcb6b3   4      14     SR-R-T0-MPBGP                     SERVICE_ROUTER_TIER0        7      \r\nf2ca25ae-49a3-4b12-a91e-c5c9908bb6c9   6      22     DR-VRF-VRF-A                      VRF_DISTRIBUTED_ROUTER_TIER0 4      \r\nc43a9c6d-b207-4022-b43c-e52728eb1ab5   7      24     DR-R-T1-VRF-A                     DISTRIBUTED_ROUTER_TIER1    4      \r\n304d5182-a40c-486a-a1e3-6d35275951fd   8      27     SR-R-T1-VRF-B                     SERVICE_ROUTER_TIER1        5      \r\n758b42b3-8a4c-452f-91ad-6baf97188879   9      23     DR-VRF-VRF-B                      VRF_DISTRIBUTED_ROUTER_TIER0 4      \r\n6204d89c-ec0e-40a9-9824-33adbbb41bff   10     26     DR-R-T1-VRF-B                     DISTRIBUTED_ROUTER_TIER1    4\r\n<\/pre>\n
            2. przechodzimy do VRF 4 i sprawdzamy stan BGP<\/p>\n
            dc1edge03(tier0_sr)> get bgp neighbor summary \r\nBFD States: NC - Not configured, AC - Activating,DC - Disconnected\r\n            AD - Admin down, DW - Down, IN - Init,UP - Up\r\nBGP summary information for VRF default for address-family: ipv4Unicast\r\nRouter ID: 192.168.10.10  Local AS: 65000\r\n\r\nNeighbor                            AS          State Up\/DownTime  BFD InMsgs  OutMsgs InPfx  OutPfx\r\n\r\n10.11.10.2                          65000       Estab 00:20:34     NC  9887    8712    0      0     \r\n192.168.10.1                        65000       Estab 00:20:34     NC  9869    8910    1      0     \r\n\r\nBFD States: NC - Not configured, AC - Activating,DC - Disconnected\r\n            AD - Admin down, DW - Down, IN - Init,UP - Up\r\nBGP summary information for VRF default for address-family: l2VpnEvpn\r\nRouter ID: 192.168.10.10  Local AS: 65000\r\n\r\nNeighbor                            AS          State Up\/DownTime  BFD InMsgs  OutMsgs InPfx  OutPfx\r\n\r\n10.11.10.2                          65000       Estab 00:20:34     NC  9887    8712    0      0     \r\n192.168.10.1                        65000       Estab 00:20:34     NC  9869    8910    0      0     \r\n<\/pre>\n
            3. sprawdzamy stan BGP EVPN – get bgp evpn<\/p>\n
            dc1edge03(tier0_sr)> get bgp evpn \r\nBGP table version is 3, local router ID is 192.168.10.10\r\nStatus codes: s suppressed, d damped, h history, * valid, > best, i - internal\r\nOrigin codes: i - IGP, e - EGP, ? - incomplete\r\nEVPN type-2 prefix: [2]:[EthTag]:[MAClen]:[MAC]:[IPlen]:[IP]\r\nEVPN type-3 prefix: [3]:[EthTag]:[IPlen]:[OrigIP]\r\nEVPN type-4 prefix: [4]:[ESI]:[IPlen]:[OrigIP]\r\nEVPN type-5 prefix: [5]:[EthTag]:[IPlen]:[IP]\r\n\r\n   Network          Next Hop            Metric LocPrf Weight Path\r\nRoute Distinguisher: 65000:95001\r\n*> [5]:[0]:[24]:[172.30.30.0]\r\n                    10.11.10.1               0         32768 ?\r\n*> [5]:[0]:[32]:[172.30.100.1]\r\n                    10.11.10.1               0         32768 ?\r\n*>i[5]:[0]:[32]:[172.30.100.2]\r\n                    10.11.10.2                    100      0 i\r\nRoute Distinguisher: 65000:95002\r\n*> [5]:[0]:[24]:[192.168.2.0]\r\n                    10.11.10.1               0         32768 ?\r\n*> [5]:[0]:[32]:[192.168.100.1]\r\n                    10.11.10.1               0         32768 ?\r\n*>i[5]:[0]:[32]:[192.168.100.2]\r\n                    10.11.10.2                    100      0 i\r\n\r\nDisplayed 6 prefixes (6 paths)\r\n<\/pre>\n
            kilka innych pomocnych komend do weryfikacji z poziomy serwis routera T0<\/p>\n\n\n\n\n\n
            Wy\u015bwietla wszystkie dost\u0119pne VRFy z przypisanym VBNI<\/td>\nget bgp evpn vni\u00a0<\/strong><\/td>\n<\/tr>\n
            Wy\u015bwietla tablic\u0119 routingu w protokole BGP z podzia\u0142em na RD<\/td>\nget bgp evpn overlay<\/strong><\/td>\n<\/tr>\n
            Pokazuje skonfigurowane VRFy kt\u00f3re s\u0105 aktywne w EVPN<\/td>\nget evpn vni<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
             <\/p>\n
             <\/p>\n","protected":false},"excerpt":{"rendered":"
            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 EVPN W kilku prostych s\u0142owach. […]<\/p>\n","protected":false},"author":1,"featured_media":2762,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"Wpis po\u015bwi\u0119cony konfiguracji EVPN z MPBGP w NSX-T 3.0. Sesja MPBGP jest Juniper vMX. Pe\u0142na konfiguracja w kliku krokach. \r\nEVPN configuration with MPBGP in NSX-T 3.0. Polish version. @VMware @VMwareNSX @vexpert #NSXT @JuniperNetworks #vMX","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"enabled":false},"version":2}},"categories":[5,84,585,9],"tags":[217,624,606,620,617,210,73,622,533,616,568,614,615,621,619,618,623,235],"class_list":["post-2657","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-juniper","category-lab","category-nsx","category-vmware","tag-evpn","tag-get-bgp-evpn","tag-get-bgp-neighbor-summary","tag-juniper-bgp","tag-juniper-evpn-type-5","tag-juniper-vmx","tag-junos","tag-multiprotocol-bgp","tag-nsx-t","tag-nsx-t-3-0-evpn","tag-nsx-t-bgp","tag-nsx-t-evpn","tag-nsx-t-evpn-vrf","tag-nsx-t-vrf-mpbgp","tag-vmx-bgp","tag-vmx-evpn","tag-vni","tag-vxlan"],"yoast_head":"\nNSX-T EVPN type 5 z routerm Juniper vMX - SafeKom Blog<\/title>\n<meta name=\"description\" content=\"Wpis po\u015bwi\u0119cony konfiguracji EVPN z MPBGP w NSX-T 3.0. Sesja MPBGP jest Juniper vMX. Pe\u0142na konfiguracja w kliku krokach. NSX-T EVPN\" \/>\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\/vmware\/nsx\/nsx-t-evpn\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"NSX-T EVPN type 5 z routerm Juniper vMX - SafeKom Blog\" \/>\n<meta property=\"og:description\" content=\"Wpis po\u015bwi\u0119cony konfiguracji EVPN z MPBGP w NSX-T 3.0. Sesja MPBGP jest Juniper vMX. Pe\u0142na konfiguracja w kliku krokach. NSX-T EVPN\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/\" \/>\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=\"2020-04-28T08:54:48+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-03-04T20:17:11+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.safekom.pl\/blog\/wp-content\/uploads\/2020\/04\/vmware-nsx-t.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"551\" \/>\n\t<meta property=\"og:image:height\" content=\"218\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\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=\"19 minut\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/\"},\"author\":{\"name\":\"Micha\u0142 Iwa\u0144czuk\",\"@id\":\"https:\/\/www.safekom.pl\/blog\/#\/schema\/person\/fd4cc931b624af4b7353d36d92ba7181\"},\"headline\":\"NSX-T EVPN\",\"datePublished\":\"2020-04-28T08:54:48+00:00\",\"dateModified\":\"2023-03-04T20:17:11+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/\"},\"wordCount\":1063,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/www.safekom.pl\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2020\/04\/vmware-nsx-t.jpg?fit=551%2C218&ssl=1\",\"keywords\":[\"evpn\",\"get bgp evpn\",\"get bgp neighbor summary\",\"juniper bgp\",\"juniper evpn type 5\",\"juniper vmx\",\"Junos\",\"multiprotocol bgp\",\"NSX-T\",\"nsx-t 3.0 evpn\",\"nsx-t bgp\",\"nsx-t evpn\",\"nsx-t evpn vrf\",\"nsx-t vrf mpbgp\",\"vmx bgp\",\"vmx evpn\",\"vni\",\"vxlan\"],\"articleSection\":[\"Juniper\",\"Lab\",\"NSX\",\"Vmware\"],\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/\",\"url\":\"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/\",\"name\":\"NSX-T EVPN type 5 z routerm Juniper vMX - SafeKom Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.safekom.pl\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2020\/04\/vmware-nsx-t.jpg?fit=551%2C218&ssl=1\",\"datePublished\":\"2020-04-28T08:54:48+00:00\",\"dateModified\":\"2023-03-04T20:17:11+00:00\",\"description\":\"Wpis po\u015bwi\u0119cony konfiguracji EVPN z MPBGP w NSX-T 3.0. Sesja MPBGP jest Juniper vMX. Pe\u0142na konfiguracja w kliku krokach. NSX-T EVPN\",\"breadcrumb\":{\"@id\":\"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/#primaryimage\",\"url\":\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2020\/04\/vmware-nsx-t.jpg?fit=551%2C218&ssl=1\",\"contentUrl\":\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2020\/04\/vmware-nsx-t.jpg?fit=551%2C218&ssl=1\",\"width\":551,\"height\":218,\"caption\":\"nsx-t logo\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Strona g\u0142\u00f3wna\",\"item\":\"https:\/\/www.safekom.pl\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"NSX-T EVPN\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.safekom.pl\/blog\/#website\",\"url\":\"https:\/\/www.safekom.pl\/blog\/\",\"name\":\"SafeKom Blog\",\"description\":\"Notatki Architekta i in\u017cyniera zwi\u0105zanego rozwi\u0105zaniami on-prem\",\"publisher\":{\"@id\":\"https:\/\/www.safekom.pl\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.safekom.pl\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pl-PL\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.safekom.pl\/blog\/#organization\",\"name\":\"SafeKom Blog\",\"url\":\"https:\/\/www.safekom.pl\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/www.safekom.pl\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2015\/05\/cropped-logo.png?fit=512%2C512&ssl=1\",\"contentUrl\":\"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2015\/05\/cropped-logo.png?fit=512%2C512&ssl=1\",\"width\":512,\"height\":512,\"caption\":\"SafeKom Blog\"},\"image\":{\"@id\":\"https:\/\/www.safekom.pl\/blog\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/safekompl\",\"https:\/\/x.com\/MIwaczuk\",\"https:\/\/www.linkedin.com\/in\/michaliwanczuk\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.safekom.pl\/blog\/#\/schema\/person\/fd4cc931b624af4b7353d36d92ba7181\",\"name\":\"Micha\u0142 Iwa\u0144czuk\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/www.safekom.pl\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/cc6dda4ee8d21d1f254147e5ee6f5e38881b88a4a12a5774ca42380597e52014?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/cc6dda4ee8d21d1f254147e5ee6f5e38881b88a4a12a5774ca42380597e52014?s=96&d=mm&r=g\",\"caption\":\"Micha\u0142 Iwa\u0144czuk\"},\"description\":\"Pasjonat komputerowy od zawsze oraz maniak w zakresie sieci, wirtualizacji oraz bezpiecze\u0144stwa IT. Kompetentny in\u017cynier z du\u017cym do\u015bwiadczeniem w realizacji projekt\u00f3w informatycznych i telekomunikacyjnych. Wieloletni administrator IT, kt\u00f3ry utrzymuje systemy informatyczne dostosowuj\u0105c je do wymog\u00f3w biznesowych z zapewnieniem dost\u0119pno\u015bci 24\/7\/365.\",\"url\":\"https:\/\/www.safekom.pl\/blog\/author\/admin\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"NSX-T EVPN type 5 z routerm Juniper vMX - SafeKom Blog","description":"Wpis po\u015bwi\u0119cony konfiguracji EVPN z MPBGP w NSX-T 3.0. Sesja MPBGP jest Juniper vMX. Pe\u0142na konfiguracja w kliku krokach. NSX-T EVPN","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\/vmware\/nsx\/nsx-t-evpn\/","og_locale":"pl_PL","og_type":"article","og_title":"NSX-T EVPN type 5 z routerm Juniper vMX - SafeKom Blog","og_description":"Wpis po\u015bwi\u0119cony konfiguracji EVPN z MPBGP w NSX-T 3.0. Sesja MPBGP jest Juniper vMX. Pe\u0142na konfiguracja w kliku krokach. NSX-T EVPN","og_url":"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/","og_site_name":"SafeKom Blog","article_publisher":"https:\/\/www.facebook.com\/safekompl","article_published_time":"2020-04-28T08:54:48+00:00","article_modified_time":"2023-03-04T20:17:11+00:00","og_image":[{"width":551,"height":218,"url":"https:\/\/www.safekom.pl\/blog\/wp-content\/uploads\/2020\/04\/vmware-nsx-t.jpg","type":"image\/jpeg"}],"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":"19 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/#article","isPartOf":{"@id":"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/"},"author":{"name":"Micha\u0142 Iwa\u0144czuk","@id":"https:\/\/www.safekom.pl\/blog\/#\/schema\/person\/fd4cc931b624af4b7353d36d92ba7181"},"headline":"NSX-T EVPN","datePublished":"2020-04-28T08:54:48+00:00","dateModified":"2023-03-04T20:17:11+00:00","mainEntityOfPage":{"@id":"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/"},"wordCount":1063,"commentCount":0,"publisher":{"@id":"https:\/\/www.safekom.pl\/blog\/#organization"},"image":{"@id":"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/#primaryimage"},"thumbnailUrl":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2020\/04\/vmware-nsx-t.jpg?fit=551%2C218&ssl=1","keywords":["evpn","get bgp evpn","get bgp neighbor summary","juniper bgp","juniper evpn type 5","juniper vmx","Junos","multiprotocol bgp","NSX-T","nsx-t 3.0 evpn","nsx-t bgp","nsx-t evpn","nsx-t evpn vrf","nsx-t vrf mpbgp","vmx bgp","vmx evpn","vni","vxlan"],"articleSection":["Juniper","Lab","NSX","Vmware"],"inLanguage":"pl-PL","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/","url":"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/","name":"NSX-T EVPN type 5 z routerm Juniper vMX - SafeKom Blog","isPartOf":{"@id":"https:\/\/www.safekom.pl\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/#primaryimage"},"image":{"@id":"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/#primaryimage"},"thumbnailUrl":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2020\/04\/vmware-nsx-t.jpg?fit=551%2C218&ssl=1","datePublished":"2020-04-28T08:54:48+00:00","dateModified":"2023-03-04T20:17:11+00:00","description":"Wpis po\u015bwi\u0119cony konfiguracji EVPN z MPBGP w NSX-T 3.0. Sesja MPBGP jest Juniper vMX. Pe\u0142na konfiguracja w kliku krokach. NSX-T EVPN","breadcrumb":{"@id":"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/"]}]},{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/#primaryimage","url":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2020\/04\/vmware-nsx-t.jpg?fit=551%2C218&ssl=1","contentUrl":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2020\/04\/vmware-nsx-t.jpg?fit=551%2C218&ssl=1","width":551,"height":218,"caption":"nsx-t logo"},{"@type":"BreadcrumbList","@id":"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-evpn\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Strona g\u0142\u00f3wna","item":"https:\/\/www.safekom.pl\/blog\/"},{"@type":"ListItem","position":2,"name":"NSX-T EVPN"}]},{"@type":"WebSite","@id":"https:\/\/www.safekom.pl\/blog\/#website","url":"https:\/\/www.safekom.pl\/blog\/","name":"SafeKom Blog","description":"Notatki Architekta i in\u017cyniera zwi\u0105zanego rozwi\u0105zaniami on-prem","publisher":{"@id":"https:\/\/www.safekom.pl\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.safekom.pl\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pl-PL"},{"@type":"Organization","@id":"https:\/\/www.safekom.pl\/blog\/#organization","name":"SafeKom Blog","url":"https:\/\/www.safekom.pl\/blog\/","logo":{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/www.safekom.pl\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2015\/05\/cropped-logo.png?fit=512%2C512&ssl=1","contentUrl":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2015\/05\/cropped-logo.png?fit=512%2C512&ssl=1","width":512,"height":512,"caption":"SafeKom Blog"},"image":{"@id":"https:\/\/www.safekom.pl\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/safekompl","https:\/\/x.com\/MIwaczuk","https:\/\/www.linkedin.com\/in\/michaliwanczuk\/"]},{"@type":"Person","@id":"https:\/\/www.safekom.pl\/blog\/#\/schema\/person\/fd4cc931b624af4b7353d36d92ba7181","name":"Micha\u0142 Iwa\u0144czuk","image":{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/www.safekom.pl\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/cc6dda4ee8d21d1f254147e5ee6f5e38881b88a4a12a5774ca42380597e52014?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/cc6dda4ee8d21d1f254147e5ee6f5e38881b88a4a12a5774ca42380597e52014?s=96&d=mm&r=g","caption":"Micha\u0142 Iwa\u0144czuk"},"description":"Pasjonat komputerowy od zawsze oraz maniak w zakresie sieci, wirtualizacji oraz bezpiecze\u0144stwa IT. Kompetentny in\u017cynier z du\u017cym do\u015bwiadczeniem w realizacji projekt\u00f3w informatycznych i telekomunikacyjnych. Wieloletni administrator IT, kt\u00f3ry utrzymuje systemy informatyczne dostosowuj\u0105c je do wymog\u00f3w biznesowych z zapewnieniem dost\u0119pno\u015bci 24\/7\/365.","url":"https:\/\/www.safekom.pl\/blog\/author\/admin\/"}]}},"jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2020\/04\/vmware-nsx-t.jpg?fit=551%2C218&ssl=1","jetpack_shortlink":"https:\/\/wp.me\/p7i9ri-GR","jetpack-related-posts":[{"id":2623,"url":"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-3-0-juz-jest\/","url_meta":{"origin":2657,"position":0},"title":"NSX-T 3.0 ju\u017c jest!","author":"Micha\u0142 Iwa\u0144czuk","date":"09.04.2020","format":false,"excerpt":"Trzy dni temu na \u015bwiat wysz\u0142a nowa wersja NSX-t 3.0 w niej jest sporo nowo\u015bci, tym wpisem rozpoczn\u0119 je opisywa\u0107. Ale teraz og\u00f3lna zajawka co znajdziemy w nowej wersji. Ju\u017c jest u mnie w labie i powoli poznaj\u0119 nowe funkcje. NSX Federacja\u00a0 Dzi\u0119ki temu rozwi\u0105zaniu b\u0119dziemy mogli zarz\u0105dza\u0144 rozproszonym \u015brodowisku\u2026","rel":"","context":"In "NSX"","block_context":{"text":"NSX","link":"https:\/\/www.safekom.pl\/blog\/category\/vmware\/nsx\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2018\/01\/Autobot_symbol.png?fit=1012%2C946&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2018\/01\/Autobot_symbol.png?fit=1012%2C946&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2018\/01\/Autobot_symbol.png?fit=1012%2C946&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2018\/01\/Autobot_symbol.png?fit=1012%2C946&ssl=1&resize=700%2C400 2x"},"classes":[]},{"id":2275,"url":"https:\/\/www.safekom.pl\/blog\/vmware\/nsx-t-routing\/","url_meta":{"origin":2657,"position":1},"title":"NSX-t Routing","author":"Micha\u0142 Iwa\u0144czuk","date":"05.03.2018","format":false,"excerpt":"W poprzednich wpisach pokaza\u0142em jak skonfigurowa\u0107 prawie ca\u0142ego NSX-t, dzi\u015b przyszed\u0142 czas na najciekawsze z perspektywy os\u00f3b zajmuj\u0105cych si\u0119 sieci\u0105 - b\u0119dziemy konfigurowa\u0107 NSX-t Routing. Poni\u017cej plan ca\u0142ej serii po\u015bwi\u0119cony NSX-t: Plan Dzia\u0142ania Poni\u017cej plan dzia\u0142ania oraz odno\u015bniki wcze\u015bniejszych wpis\u00f3w o NSX-T. Instalacja NSX Managera Instalacja NSX-t Controller pod\u0142\u0105czenie ich\u2026","rel":"","context":"In "Lab"","block_context":{"text":"Lab","link":"https:\/\/www.safekom.pl\/blog\/en\/category\/lab\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2018\/01\/nsx-t-lab03.png?resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2018\/01\/nsx-t-lab03.png?resize=350%2C200 1x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2018\/01\/nsx-t-lab03.png?resize=525%2C300 1.5x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2018\/01\/nsx-t-lab03.png?resize=700%2C400 2x"},"classes":[]},{"id":2567,"url":"https:\/\/www.safekom.pl\/blog\/vmware\/nsx\/nsx-t-ipsec-route-base\/","url_meta":{"origin":2657,"position":2},"title":"NSX-t IPSec Route base","author":"Micha\u0142 Iwa\u0144czuk","date":"26.03.2020","format":false,"excerpt":"W dzisiejszym wpisie przedstawi\u0119 konfiguracj\u0119 NSX-t IPSec Route base, jest to\u00a0 opis krok po kroku jak skonfigurowa\u0107 IPseca po stronie NSX'a oraz Vyos kt\u00f3ry b\u0119dzie uczestnikiem IPseca.\u00a0 Za\u0142o\u017cenia Poni\u017cej rysunek pogl\u0105dowy jak wygl\u0105da topologia po\u0142\u0105cze\u0144. Pomi\u0119dzy routerem T0 i chmurk\u0105 ju\u017c istnieje po\u0142\u0105czenie oraz jest zestawione s\u0105siedztwo BGP w celu\u2026","rel":"","context":"In "NSX"","block_context":{"text":"NSX","link":"https:\/\/www.safekom.pl\/blog\/category\/vmware\/nsx\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2018\/01\/Autobot_symbol.png?fit=1012%2C946&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2018\/01\/Autobot_symbol.png?fit=1012%2C946&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2018\/01\/Autobot_symbol.png?fit=1012%2C946&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2018\/01\/Autobot_symbol.png?fit=1012%2C946&ssl=1&resize=700%2C400 2x"},"classes":[]},{"id":782,"url":"https:\/\/www.safekom.pl\/blog\/cisco\/lab-vxlan-juniper-vmx-i-cisco-csr1kv-asav\/","url_meta":{"origin":2657,"position":3},"title":"LAB vxlan – Juniper vMX i Cisco CSR1kv oraz ASAv","author":"Micha\u0142 Iwa\u0144czuk","date":"26.04.2016","format":false,"excerpt":"Po pierwszym wpisie o VxLAN, gdzie opar\u0142em si\u0119 wy\u0142\u0105cznie na Cisco CSRv oraz ASAv przysz\u0142a pora na testowanie w konfiguracji multivendor. Do tego laba wykorzysta\u0142em: Cisco CSRv Cisco ASAv Juniper vMX Wszystko zosta\u0142o uruchomione na Vmware Workstation. W dobie wirtualizacji serwer\u00f3w i desktop\u00f3w postanowi\u0142em wzi\u0105\u0107 si\u0119 ostro za poznanie \u015bwiata\u2026","rel":"","context":"In "Cisco"","block_context":{"text":"Cisco","link":"https:\/\/www.safekom.pl\/blog\/category\/cisco\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/02\/Juniper-Networks-and-Cisco-Systems.png?fit=712%2C534&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/02\/Juniper-Networks-and-Cisco-Systems.png?fit=712%2C534&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/02\/Juniper-Networks-and-Cisco-Systems.png?fit=712%2C534&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2016\/02\/Juniper-Networks-and-Cisco-Systems.png?fit=712%2C534&ssl=1&resize=700%2C400 2x"},"classes":[]},{"id":2149,"url":"https:\/\/www.safekom.pl\/blog\/vmware\/nsx-t-czas-poznac-rywala\/","url_meta":{"origin":2657,"position":4},"title":"NSX-T czas pozna\u0107 rywala","author":"Micha\u0142 Iwa\u0144czuk","date":"22.01.2018","format":false,"excerpt":"Od d\u0142u\u017cszego czasu zajmuje si\u0119 NSX-v, ale stwierdzi\u0142em, \u017ce czas pozna\u0107 wersj\u0119 multi platform NSX-T. Gdy grudniu 2017 pojawi\u0142a si\u0119 wersja 2.1 mo\u017cna powiedzie\u0107, \u017ce wersja ju\u017c jest w miar\u0119 wygrzana. Poczu\u0142em, \u017ce przyszed\u0142 czas aby rozwi\u0105zanie to pojawi\u0142o si\u0119 w mym labie. Ten wpis otwiera seri\u0119 wpis\u00f3w na temat\u2026","rel":"","context":"In "Lab"","block_context":{"text":"Lab","link":"https:\/\/www.safekom.pl\/blog\/en\/category\/lab\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2018\/01\/nsx-t-lab02.png?resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2018\/01\/nsx-t-lab02.png?resize=350%2C200 1x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2018\/01\/nsx-t-lab02.png?resize=525%2C300 1.5x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2018\/01\/nsx-t-lab02.png?resize=700%2C400 2x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2018\/01\/nsx-t-lab02.png?resize=1050%2C600 3x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2018\/01\/nsx-t-lab02.png?resize=1400%2C800 4x"},"classes":[]},{"id":2227,"url":"https:\/\/www.safekom.pl\/blog\/vmware\/nsx-t-transport-zone-node\/","url_meta":{"origin":2657,"position":5},"title":"NSX-t transport zone & node","author":"Micha\u0142 Iwa\u0144czuk","date":"20.02.2018","format":false,"excerpt":"Mamy za sob\u0105 ju\u017c zainstalowane modu\u0142y wymagane do poprawnego dzia\u0142ania NSX-t na hostach z vSphere, Dzi\u015b przyszed\u0142 czas na konfiguracj\u0119 NSX-t transport zone i transport node i wszystko to co zwi\u0105zane aby uruchomi\u0107 sie\u0107 L2 w sieci nak\u0142adkowej w NSX-t. Plan Dzia\u0142ania Poni\u017cej plan dzia\u0142ania oraz odno\u015bniki wcze\u015bniejszych wpis\u00f3w o\u2026","rel":"","context":"In "Lab"","block_context":{"text":"Lab","link":"https:\/\/www.safekom.pl\/blog\/en\/category\/lab\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2018\/01\/Autobot_symbol.png?fit=1012%2C946&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2018\/01\/Autobot_symbol.png?fit=1012%2C946&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2018\/01\/Autobot_symbol.png?fit=1012%2C946&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/www.safekom.pl\/blog\/wp-content\/uploads\/2018\/01\/Autobot_symbol.png?fit=1012%2C946&ssl=1&resize=700%2C400 2x"},"classes":[]}],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.safekom.pl\/blog\/wp-json\/wp\/v2\/posts\/2657","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=2657"}],"version-history":[{"count":14,"href":"https:\/\/www.safekom.pl\/blog\/wp-json\/wp\/v2\/posts\/2657\/revisions"}],"predecessor-version":[{"id":2734,"href":"https:\/\/www.safekom.pl\/blog\/wp-json\/wp\/v2\/posts\/2657\/revisions\/2734"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.safekom.pl\/blog\/wp-json\/wp\/v2\/media\/2762"}],"wp:attachment":[{"href":"https:\/\/www.safekom.pl\/blog\/wp-json\/wp\/v2\/media?parent=2657"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.safekom.pl\/blog\/wp-json\/wp\/v2\/categories?post=2657"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.safekom.pl\/blog\/wp-json\/wp\/v2\/tags?post=2657"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}