前回までの記事
・EVPN/VXLAN動かしてみた(Part1)
・EVPN/VXLAN動かしてみた(Part2)
前回の振り返り
・前回まででアンダーレイ／オーバーレイの構築とステータスまで完了しました
・今回はLeafにHostを接続し、Host間でPingを実行し、疎通が取れることを確認していきます。
・機器StatusやPCAPの確認も併せて行います
まずは同一Vlan内のスイッチングを確認していきます。（Vlan間通信は次回確認予定です）
Leaf001とLeaf002の配下にそれぞれ端末を接続し、Vlan100のIPを持たせます
Host1からHost2およびHost2からHost1へPingを打ち、EVPNでの学習状況やステータスの変化を見ていきます
＃パケットキャプチャの内容はテキストで張り付けています
Host1～Leaf001
Host1
Host1からのARP
314 561.406478277 aa:c1:ab:41:9b:9a Broadcast ARP 42 Who has 10.100.0.2? Tell 10.100.0.1
Frame 314: 42 bytes on wire (336 bits), 42 bytes captured (336 bits) on interface 0
Ethernet II, Src: aa:c1:ab:41:9b:9a (aa:c1:ab:41:9b:9a), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Destination: Broadcast (ff:ff:ff:ff:ff:ff)
Source: aa:c1:ab:41:9b:9a (aa:c1:ab:41:9b:9a) ##---Host1
Type: ARP (0x0806)
Address Resolution Protocol (request)
Hardware type: Ethernet (1)
Protocol type: IPv4 (0x0800)
Hardware size: 6
Protocol size: 4
Opcode: request (1)
Sender MAC address: aa:c1:ab:41:9b:9a (aa:c1:ab:41:9b:9a)
Sender IP address: 10.100.0.1
Target MAC address: 00:00:00_00:00:00 (00:00:00:00:00:00)
Target IP address: 10.100.0.2
Leaf001～Spine002～Leaf002
Host1からARPを受信後、VXLANでカプセル化しSpine002経由で送信
Leaf001からSpineへのARP
Leaf001
Frame 230: 110 bytes on wire (880 bits), 110 bytes captured (880 bits) on interface 0
Ethernet II, Src: aa:c1:ab:82:fc:b2 (aa:c1:ab:82:fc:b2), Dst: aa:c1:ab:af:7f:5e (aa:c1:ab:af:7f:5e)
Internet Protocol Version 4, Src: 10.0.0.15, Dst: 10.0.0.16 ##--Src Leaf001のVTEP，dst Leaf002のVTEP
User Datagram Protocol, Src Port: 26085, Dst Port: 4789
Virtual eXtensible Local Area Network ##----VXLANでカプセル化
Flags: 0x0800, VXLAN Network ID (VNI)
Group Policy ID: 0
VXLAN Network Identifier (VNI): 10100 ##---Vlan100のL2VNI
Reserved: 0
Ethernet II, Src: aa:c1:ab:41:9b:9a (aa:c1:ab:41:9b:9a), Dst: Broadcast (ff:ff:ff:ff:ff:ff) ##---元のパケット
Address Resolution Protocol (request)
Hardware type: Ethernet (1)
Protocol type: IPv4 (0x0800)
Hardware size: 6
Protocol size: 4
Opcode: request (1)
Sender MAC address: aa:c1:ab:41:9b:9a (aa:c1:ab:41:9b:9a)
Sender IP address: 10.100.0.1
Target MAC address: 00:00:00_00:00:00 (00:00:00:00:00:00)
Target IP address: 10.100.0.2
Leaf001から受け取ったARP
Spine002
Frame 148: 110 bytes on wire (880 bits), 110 bytes captured (880 bits) on interface 0
Ethernet II, Src: aa:c1:ab:82:fc:b2 (aa:c1:ab:82:fc:b2), Dst: aa:c1:ab:af:7f:5e (aa:c1:ab:af:7f:5e)
Internet Protocol Version 4, Src: 10.0.0.15, Dst: 10.0.0.16
User Datagram Protocol, Src Port: 26085, Dst Port: 4789
Virtual eXtensible Local Area Network
Flags: 0x0800, VXLAN Network ID (VNI)
Group Policy ID: 0
VXLAN Network Identifier (VNI): 10100
Reserved: 0
Ethernet II, Src: aa:c1:ab:41:9b:9a (aa:c1:ab:41:9b:9a), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request)
Hardware type: Ethernet (1)
Protocol type: IPv4 (0x0800)
Hardware size: 6
Protocol size: 4
Opcode: request (1)
Sender MAC address: aa:c1:ab:41:9b:9a (aa:c1:ab:41:9b:9a)
Sender IP address: 10.100.0.1
Target MAC address: 00:00:00_00:00:00 (00:00:00:00:00:00)
Target IP address: 10.100.0.2
Spine002から受け取ったARP
Leaf002
Frame 139: 110 bytes on wire (880 bits), 110 bytes captured (880 bits) on interface 0
Ethernet II, Src: aa:c1:ab:db:04:6e (aa:c1:ab:db:04:6e), Dst: aa:c1:ab:27:ee:d3 (aa:c1:ab:27:ee:d3)
Internet Protocol Version 4, Src: 10.0.0.15, Dst: 10.0.0.16
User Datagram Protocol, Src Port: 26085, Dst Port: 4789
Virtual eXtensible Local Area Network
Flags: 0x0800, VXLAN Network ID (VNI)
Group Policy ID: 0
VXLAN Network Identifier (VNI): 10100
Reserved: 0
Ethernet II, Src: aa:c1:ab:41:9b:9a (aa:c1:ab:41:9b:9a), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request)
Hardware type: Ethernet (1)
Protocol type: IPv4 (0x0800)
Hardware size: 6
Protocol size: 4
Opcode: request (1)
Sender MAC address: aa:c1:ab:41:9b:9a (aa:c1:ab:41:9b:9a)
Sender IP address: 10.100.0.1
Target MAC address: 00:00:00_00:00:00 (00:00:00:00:00:00)
Target IP address: 10.100.0.2
・VXLANパケットをSpine002が中継しLeaf002に到達したことが確認できます
・カプセル化後のsrc,dstMACがそれぞれ src:Spine002のEth2、dst:Leaf002のEth2に変わっていることが確認できます
Ethernet II, Src: aa:c1:ab:82:fc:b2 (aa:c1:ab:82:fc:b2), Dst: aa:c1:ab:af:7f:5e (aa:c1:ab:af:7f:5e)
↓
Ethernet II, Src: aa:c1:ab:db:04:6e (aa:c1:ab:db:04:6e), Dst: aa:c1:ab:27:ee:d3 (aa:c1:ab:27:ee:d3)
aa:c1:ab:82:fc:b2：Leaf001 Eth2 aa:c1:ab:af:7f:5e：Spine002 Eth1
aa:c1:ab:db:04:6e：Spine002 Eth2 aa:c1:ab:27:ee:d3：Leaf002 Eth2
Host2
Leaf002からのARP
Host2
Frame 297: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface 0
Ethernet II, Src: aa:c1:ab:41:9b:9a (aa:c1:ab:41:9b:9a), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Destination: Broadcast (ff:ff:ff:ff:ff:ff)
Source: aa:c1:ab:41:9b:9a (aa:c1:ab:41:9b:9a) ##---Host1のMACアドレス
Type: ARP (0x0806)
Padding: 000000000000000000000000000000000000
Address Resolution Protocol (request)
Hardware type: Ethernet (1)
Protocol type: IPv4 (0x0800)
Hardware size: 6
Protocol size: 4
Opcode: request (1)
Sender MAC address: aa:c1:ab:41:9b:9a (aa:c1:ab:41:9b:9a)
Sender IP address: 10.100.0.1
Target MAC address: 00:00:00_00:00:00 (00:00:00:00:00:00)
Target IP address: 10.100.0.2
・VXLANヘッダが外された状態で到達していることが確認できます
・Ethernetフレームも元のパケットになっており、src macはHost1のものになっています。
Host1とHost2は直接L2接続された環境ではありませんでしたが、VXLANのカプセル化により、Hostから見ると、物理的に離れていてもL2で直結されているように振る舞います
EVPNの状態
ここでのEVPN シグナリングをPCAPや機器のStatusから追っていきます
Host1からのパケットをLeaf001が受信し、自身のVTEP配下にホストが存在することを認識した時点で
そのMACアドレス情報を他のVTEPに伝えるためにMP_REACH_NLRI Route-type2を広報します
Leaf001からSpineへのBGP UPDATE
Leaf001
Frame 9: 169 bytes on wire (1352 bits), 169 bytes captured (1352 bits) on interface 0
Ethernet II, Src: aa:c1:ab:8d:67:cf (aa:c1:ab:8d:67:cf), Dst: aa:c1:ab:c5:03:c8 (aa:c1:ab:c5:03:c8)
Internet Protocol Version 4, Src: 172.17.0.1, Dst: 172.16.0.1 #--172.17.x.x=Leaf,172.16.x.x=Spine
Transmission Control Protocol, Src Port: 179, Dst Port: 34083, Seq: 20, Ack: 20, Len: 103
Border Gateway Protocol - UPDATE Message
Marker: ffffffffffffffffffffffffffffffff
Length: 103
Type: UPDATE Message (2)
Withdrawn Routes Length: 0
Total Path Attribute Length: 80
Path attributes
Path Attribute - ORIGIN: IGP
Flags: 0x40, Transitive, Well-known, Complete
Type Code: ORIGIN (1)
Length: 1
Origin: IGP (0)
Path Attribute - AS_PATH: 64612
Flags: 0x40, Transitive, Well-known, Complete
Type Code: AS_PATH (2)
Length: 6
AS Path segment: 64612
Path Attribute - MP_REACH_NLRI
Flags: 0x90, Optional, Extended-Length, Non-transitive, Complete
Type Code: MP_REACH_NLRI (14)
Length: 44
Address family identifier (AFI): Layer-2 VPN (25)
Subsequent address family identifier (SAFI): EVPN (70)
Next hop network address (4 bytes)
Number of Subnetwork points of attachment (SNPA): 0
Network layer reachability information (35 bytes)
EVPN NLRI: MAC Advertisement Route
Route Type: MAC Advertisement Route (2) ##--RouteType2
Length: 33
Route Distinguisher: 00010a00000f0064 (10.0.0.15:100)
ESI: 00:00:00:00:00:00:00:00:00:00
Ethernet Tag ID: 0
MAC Address Length: 48
MAC Address: aa:c1:ab:41:9b:9a (aa:c1:ab:41:9b:9a) ##--Host1のMAC
IP Address Length: 0
IP Address: NOT INCLUDED
0000 0000 0010 0111 0111 .... = MPLS Label 1: 631
Path Attribute - EXTENDED_COMMUNITIES
Flags: 0xc0, Optional, Transitive, Complete
Type Code: EXTENDED_COMMUNITIES (16)
Length: 16
Carried extended communities: (2 communities)
Route Target: 100:10100 [Transitive 2-Octet AS-Specific]
Encapsulation: VXLAN Encapsulation [Transitive Opaque]
・Host1のMACアドレスをMP-BGPのPathAttribute MP_REACH_NLRI Type2で広報しています
SpineからLeaf002へのBGP UPDATE
Leaf002
Frame 204: 173 bytes on wire (1384 bits), 173 bytes captured (1384 bits) on interface 0
Ethernet II, Src: aa:c1:ab:db:04:6e (aa:c1:ab:db:04:6e), Dst: aa:c1:ab:27:ee:d3 (aa:c1:ab:27:ee:d3)
Internet Protocol Version 4, Src: 172.16.0.2, Dst: 172.17.0.2 ##--Spine to Leaf
Transmission Control Protocol, Src Port: 179, Dst Port: 33773, Seq: 218, Ack: 218, Len: 107
Border Gateway Protocol - UPDATE Message
Marker: ffffffffffffffffffffffffffffffff
Length: 107
Type: UPDATE Message (2)
Withdrawn Routes Length: 0
Total Path Attribute Length: 84
Path attributes
Path Attribute - ORIGIN: IGP
Flags: 0x40, Transitive, Well-known, Complete
Type Code: ORIGIN (1)
Length: 1
Origin: IGP (0)
Path Attribute - AS_PATH: 64512 64612
Flags: 0x40, Transitive, Well-known, Complete
Type Code: AS_PATH (2)
Length: 10
AS Path segment: 64512 64612
Path Attribute - MP_REACH_NLRI
Flags: 0x90, Optional, Extended-Length, Non-transitive, Complete
Type Code: MP_REACH_NLRI (14)
Length: 44
Address family identifier (AFI): Layer-2 VPN (25)
Subsequent address family identifier (SAFI): EVPN (70)
Next hop network address (4 bytes)
Number of Subnetwork points of attachment (SNPA): 0
Network layer reachability information (35 bytes)
EVPN NLRI: MAC Advertisement Route
Route Type: MAC Advertisement Route (2)
Length: 33
Route Distinguisher: 00010a00000f0064 (10.0.0.15:100) ##Leaf001のRD
ESI: 00:00:00:00:00:00:00:00:00:00
Ethernet Tag ID: 0
MAC Address Length: 48
MAC Address: aa:c1:ab:41:9b:9a (aa:c1:ab:41:9b:9a) ##--Host1のMAC
IP Address Length: 0
IP Address: NOT INCLUDED
0000 0000 0010 0111 0111 .... = MPLS Label 1: 631
Path Attribute - EXTENDED_COMMUNITIES
Flags: 0xc0, Optional, Transitive, Complete
Type Code: EXTENDED_COMMUNITIES (16)
Length: 16
Carried extended communities: (2 communities)
Leaf002 Status
==== show bgp evpn route-type mac-ip ==== ##--routetype2の学習状態
BGP routing table information for VRF default
Router identifier 172.17.0.2, local AS number 64613
Route status codes: * - valid, > - active, S - Stale, E - ECMP head, e - ECMP
c - Contributing to ECMP, % - Pending best path selection
Origin codes: i - IGP, e - EGP, ? - incomplete
AS Path Attributes: Or-ID - Originator ID, C-LST - Cluster List, LL Nexthop - Link Local Nexthop
Network Next Hop Metric LocPref Weight Path
* > RD: 10.0.0.16:100 mac-ip aac1.ab1c.46d5
- - - 0 i
* >Ec RD: 10.0.0.15:100 mac-ip aac1.ab41.9b9a
10.0.0.15 - 100 0 64512 64612 i
* ec RD: 10.0.0.15:100 mac-ip aac1.ab41.9b9a
10.0.0.15 - 100 0 64512 64612 i
==== show vxlan address-table ====
Vxlan Mac Address Table
----------------------------------------------------------------------
VLAN Mac Address Type Prt VTEP Moves Last Move
---- ----------- ---- --- ---- ----- ---------
100 aac1.ab41.9b9a EVPN Vx1 10.0.0.15 1 0:04:52 ago #Host1 MAC
4094 001c.7320.d177 EVPN Vx1 10.0.0.17 1 0:51:25 ago #Leaf003 VTEP
4094 001c.7367.6f79 EVPN Vx1 10.0.0.15 1 0:51:25 ago #Leaf001 VTEP
Total Remote Mac Addresses for this criterion: 3
・Leaf002側でもEVPN経由でHost1のMACアドレスを学習できました。
・同様に反対側、Leaf002配下のHost2のMACを広報する様子は以下です
Host2 MAC Advertise
Leaf002 to Spine
Frame 209: 169 bytes on wire (1352 bits), 169 bytes captured (1352 bits) on interface 0
Ethernet II, Src: aa:c1:ab:27:ee:d3 (aa:c1:ab:27:ee:d3), Dst: aa:c1:ab:db:04:6e (aa:c1:ab:db:04:6e)
Internet Protocol Version 4, Src: 172.17.0.2, Dst: 172.16.0.2
Transmission Control Protocol, Src Port: 33773, Dst Port: 179, Seq: 218, Ack: 325, Len: 103
Border Gateway Protocol - UPDATE Message
Marker: ffffffffffffffffffffffffffffffff
Length: 103
Type: UPDATE Message (2)
Withdrawn Routes Length: 0
Total Path Attribute Length: 80
Path attributes
Path Attribute - ORIGIN: IGP
Flags: 0x40, Transitive, Well-known, Complete
Type Code: ORIGIN (1)
Length: 1
Origin: IGP (0)
Path Attribute - AS_PATH: 64613
Flags: 0x40, Transitive, Well-known, Complete
Type Code: AS_PATH (2)
Length: 6
AS Path segment: 64613
Path Attribute - MP_REACH_NLRI
Flags: 0x90, Optional, Extended-Length, Non-transitive, Complete
Type Code: MP_REACH_NLRI (14)
Length: 44
Address family identifier (AFI): Layer-2 VPN (25)
Subsequent address family identifier (SAFI): EVPN (70)
Next hop network address (4 bytes)
Number of Subnetwork points of attachment (SNPA): 0
Network layer reachability information (35 bytes)
EVPN NLRI: MAC Advertisement Route
Route Type: MAC Advertisement Route (2)
Length: 33
Route Distinguisher: 00010a0000100064 (10.0.0.16:100)
ESI: 00:00:00:00:00:00:00:00:00:00
Ethernet Tag ID: 0
MAC Address Length: 48
MAC Address: aa:c1:ab:1c:46:d5 (aa:c1:ab:1c:46:d5)
IP Address Length: 0
IP Address: NOT INCLUDED
0000 0000 0010 0111 0111 .... = MPLS Label 1: 631
Path Attribute - EXTENDED_COMMUNITIES
Flags: 0xc0, Optional, Transitive, Complete
Type Code: EXTENDED_COMMUNITIES (16)
Length: 16
Carried extended communities: (2 communities)
Leaf001 Status
==== show bgp evpn route-type mac-ip ==== ##--routetype2の学習状態
BGP routing table information for VRF default
Router identifier 172.17.0.2, local AS number 64613
Route status codes: * - valid, > - active, S - Stale, E - ECMP head, e - ECMP
c - Contributing to ECMP, % - Pending best path selection
Origin codes: i - IGP, e - EGP, ? - incomplete
AS Path Attributes: Or-ID - Originator ID, C-LST - Cluster List, LL Nexthop - Link Local Nexthop
Network Next Hop Metric LocPref Weight Path
* >Ec RD: 10.0.0.16:100 mac-ip aac1.ab1c.46d5
10.0.0.16 - 100 0 64512 64613 i
* ec RD: 10.0.0.16:100 mac-ip aac1.ab1c.46d5
10.0.0.16 - 100 0 64512 64613 i
* > RD: 10.0.0.15:100 mac-ip aac1.ab41.9b9a
- - - 0 i
==== show vxlan address-table ====
Vxlan Mac Address Table
----------------------------------------------------------------------
VLAN Mac Address Type Prt VTEP Moves Last Move
---- ----------- ---- --- ---- ----- ---------
100 aac1.ab1c.46d5 EVPN Vx1 10.0.0.16 1 0:04:35 ago ##Host2 MAC
4094 001c.7320.d177 EVPN Vx1 10.0.0.17 1 0:51:09 ago ##Leaf003 VTEP
4094 001c.737f.ab9f EVPN Vx1 10.0.0.16 1 0:51:09 ago ##Leaf001 VTEP
Total Remote Mac Addresses for this criterion: 3
疎通確認
・上記のようなやり取りを経て、Host1,Host2双方向のPing疎通が取れました
Host1# ping 10.100.0.2
PING 10.100.0.2 (10.100.0.2): 56 data bytes
64 bytes from 10.100.0.2: seq=0 ttl=64 time=8.149 ms
64 bytes from 10.100.0.2: seq=1 ttl=64 time=2.109 ms
----
Host2# ping 10.100.0.1
PING 10.100.0.1 (10.100.0.1): 56 data bytes
64 bytes from 10.100.0.1: seq=0 ttl=64 time=1.925 ms
64 bytes from 10.100.0.1: seq=1 ttl=64 time=2.303 ms
Ping PCAP--host1 to host2
往：Leaf001 to Spine
Frame 235: 148 bytes on wire (1184 bits), 148 bytes captured (1184 bits) on interface 0
Ethernet II, Src: aa:c1:ab:82:fc:b2 (aa:c1:ab:82:fc:b2), Dst: aa:c1:ab:af:7f:5e (aa:c1:ab:af:7f:5e)##Leaf001 Eth2 -> Spine002 Eth1
Internet Protocol Version 4, Src: 10.0.0.15, Dst: 10.0.0.16 ##Leaf001 VTEP -> Leaf002 VTEP
User Datagram Protocol, Src Port: 56850, Dst Port: 4789
Virtual eXtensible Local Area Network
Flags: 0x0800, VXLAN Network ID (VNI)
Group Policy ID: 0
VXLAN Network Identifier (VNI): 10100 ##Vlan100 L2VNI
Reserved: 0
Ethernet II, Src: aa:c1:ab:41:9b:9a (aa:c1:ab:41:9b:9a), Dst: aa:c1:ab:1c:46:d5 (aa:c1:ab:1c:46:d5)##Host1 -> Host2
Internet Protocol Version 4, Src: 10.100.0.1, Dst: 10.100.0.2##Host1 -> Host2
Internet Control Message Protocol
往：Spine to Leaf002
Frame 144: 148 bytes on wire (1184 bits), 148 bytes captured (1184 bits) on interface 0
Ethernet II, Src: aa:c1:ab:db:04:6e (aa:c1:ab:db:04:6e), Dst: aa:c1:ab:27:ee:d3 (aa:c1:ab:27:ee:d3)##--Spine002 Eth2 -> Leaf002 Eth2
Internet Protocol Version 4, Src: 10.0.0.15, Dst: 10.0.0.16 ##--Leaf001 VTEP -> Leaf002 VTEP
User Datagram Protocol, Src Port: 56850, Dst Port: 4789
Virtual eXtensible Local Area Network
Flags: 0x0800, VXLAN Network ID (VNI)
Group Policy ID: 0
VXLAN Network Identifier (VNI): 10100 ##Vlan100 L2VNI
Reserved: 0
Ethernet II, Src: aa:c1:ab:41:9b:9a (aa:c1:ab:41:9b:9a), Dst: aa:c1:ab:1c:46:d5 (aa:c1:ab:1c:46:d5)##--Host1 -> Host2
Internet Protocol Version 4, Src: 10.100.0.1, Dst: 10.100.0.2 ##Host1 -> Host2
Internet Control Message Protocol
復：Leaf002 to Spine
Frame 207: 148 bytes on wire (1184 bits), 148 bytes captured (1184 bits) on interface 0
Ethernet II, Src: aa:c1:ab:27:ee:d3 (aa:c1:ab:27:ee:d3), Dst: aa:c1:ab:db:04:6e (aa:c1:ab:db:04:6e)##--Leaf002 Eth2 -> Spine002 Eth2
Internet Protocol Version 4, Src: 10.0.0.16, Dst: 10.0.0.15##Leaf002 VTEP -> Leaf001 VTEP
User Datagram Protocol, Src Port: 56850, Dst Port: 4789
Virtual eXtensible Local Area Network
Flags: 0x0800, VXLAN Network ID (VNI)
Group Policy ID: 0
VXLAN Network Identifier (VNI): 10100 ##Vlan100 L2VNI
Reserved: 0
Ethernet II, Src: aa:c1:ab:1c:46:d5 (aa:c1:ab:1c:46:d5), Dst: aa:c1:ab:41:9b:9a (aa:c1:ab:41:9b:9a) ##--host2 -> Host1
Internet Protocol Version 4, Src: 10.100.0.2, Dst: 10.100.0.1##-Host2 -> host1
Internet Control Message Protocol
復：Spine to Leaf001
Frame 236: 148 bytes on wire (1184 bits), 148 bytes captured (1184 bits) on interface 0
Ethernet II, Src: aa:c1:ab:af:7f:5e (aa:c1:ab:af:7f:5e), Dst: aa:c1:ab:82:fc:b2 (aa:c1:ab:82:fc:b2) ##Spine002 Eth2 -> Leaf001 Eth2
Internet Protocol Version 4, Src: 10.0.0.16, Dst: 10.0.0.15 #Leaf002 VTEP -> Leaf001 VTEP
User Datagram Protocol, Src Port: 56850, Dst Port: 4789
Virtual eXtensible Local Area Network
Flags: 0x0800, VXLAN Network ID (VNI)
Group Policy ID: 0
VXLAN Network Identifier (VNI): 10100 ##Vlan100 L2VNI
Reserved: 0
Ethernet II, Src: aa:c1:ab:1c:46:d5 (aa:c1:ab:1c:46:d5), Dst: aa:c1:ab:41:9b:9a (aa:c1:ab:41:9b:9a)##-Host2 -> host1
Internet Protocol Version 4, Src: 10.100.0.2, Dst: 10.100.0.1##-Host2 -> host1
Internet Control Message Protocol
・Host-Leaf間のPCAPは取得し忘れてましたが、Leaf001--spine---Leaf002の経路上で
VXLANによるカプセル化が正常に行われており、L3ネットワークを超えたL2通信ができていることが
確認できます
※冒頭のホストからのARPをカプセル化してFabricを通じて対向に投げる動きが気になった
(ただのFlood＆Learn見える...何も学習してない初期段階ではそういうものなのか...)
VTEPに学習させた状態(各HostのMACをType2で交換しおえた状態)だとARPが抑制されるものなのかを別途確認予定
最後に
・今回は離れた場所にある同一セグメントのHost同士での接続を検証しました
・結果、VTEPがhost情報を確認後、MP-BGPのPathAttribute MP_REACH_NLRI Type2を広報し、
リモートVTEP間でのhost情報の交換が行われている様子が確認できました
・実際の通信では、オリジナルパケットに対してVXLANヘッダー等を付与しカプセル化が行われていることを確認できました
≪EVPN MP-BGP Route Adv≫
≪VXLAN Encap / Decap≫
次回はVlan100とVlan200のHost同士、VXLAN間通信の際の動きをみていきたいと思います!