...
| Info | ||
|---|---|---|
| ||
Note: Single homed ports connecting a single device with the EVPN VXLAN fabric are not yet supported on VTEP devices. If a server is dual homed to two VTEPs and the connecting link to one of the VTEP fails, the server will still be considered a dual homed device even if there is only one active link connecting it to the fabric. |
EVPN MH Basic Configuration
To configure EVPN multihoming on a LAG interface, the user needs to configure an Ethernet Segment identifier (ES-ID) and an Ethernet Segment System MAC. A type-3 ESI value is automatically generated by using these two parameters. The resulting 10-byte ESI value has the following format, where the XXs denote the 6-byte ES System MAC and the YYs denote the 6-byte ES System MAC and the YYs denote the 3-byte local ES ID.
03 : XX : XX : XX : XX : XX : XX : YY : YY : YY
For each Ethernet segment, both the ES System MAC and the ES ID must be the same on all the switches forming the EVPN MH redundancy group. However, switches can be configured with different system MACs for different Ethernet segments or share the same system MAC for all Ethernet segments.the 3-byte local ES ID.
03 : XX : XX : XX : XX : XX : XX : YY : YY : YY
For each Ethernet segment, both the ES System MAC and the ES ID must be the same on all the switches forming the EVPN MH redundancy group. However, switches can be configured with different system MACs for different Ethernet segments or share the same system MAC for all Ethernet segments.
Aliasing
The aliasing feature provides remote VTEP devices the ability to load balance Layer-2 unicast traffic through other VTEPs that have configured the same ES (Ethernet Segment). VTEP devices in the EVPN multihoming redundancy group always advertise the communicated information of the same ES to all remote VTEPs via MP-BGP protocol. If one of the VTEP device in an ES, say VTEP1 in the following figure, learns the MAC/ARP information and advertises it to the remote VTEP, say VTEP3. Then, VTEP3 adds not only the IP address of VTEP1 as the next hop, but also adds the IP addresses of other VTEPs in the EVPN multihoming redundancy group as the next hop, to automatically form equivalent paths between different VTEPs.
EVPN multihoming aliasing function uses the ECMP hash fields "ingress-interface","ip-destination", "ip-source," "port-destination," "port-source," and "vlan" for equivalent paths calculation. By default, all these fields are enabled. Users can run the following CLI commands to enable or disable the ECMP hash fields: set interface ecmp hash-mapping field ingress-interface disable set interface ecmp hash-mapping field ip-destination disable set interface ecmp hash-mapping field ip-protocol disable set interface ecmp hash-mapping field ip-source disable set interface ecmp hash-mapping field port-destination disable set interface ecmp hash-mapping field port-source disable set interface ecmp hash-mapping field vlan disable |
On the remote VTEP, run the following EVPN MAC show commands to view the next hop. It shows the next hop interface is vplag, including all VTEPs in remote ES.
| Code Block |
|---|
admin@Xorplus# run show mac-address table
Total entries in switching table: 1
Static entries in switching table: 0
Dynamic entries in switching table: 1
VLAN MAC address Type Age Interfaces User
---- ----------------- --------- ---- ---------------- ----------
N/A 00:0c:29:77:8b:15 Dynamic 300 vplag-0x1 xorp
admin@Xorplus# run show vxlan address-table
VNID MAC address Type Interface VTEP
----------- ----------------- ------- ---------------- ---------------
10020 00:0c:29:77:8b:15 Dynamic 10.226.14.253,10.226.14.254
Entries in access port: 0
Entries in network port: 1
|
Switch Configuration Example and Topology
...
To implement a seamless migration of servers VMs without changing network settings or disrupting the traffic forwarding, configure the same anycast gateway IP and the same virtual MAC (router MAC) on all four leaf switches to enable the anycast gateway function.
...
| Code Block |
|---|
admin@Leaf1# run show bgp evpn route
BGP table version is 19, local router ID is 10.226.14.207
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete
EVPN type-1 prefix: [1]:[ESI]:[EthTag]:[IPlen]:[VTEP-IP]
EVPN type-2 prefix: [2]:[EthTag]:[MAClen]:[MAC]:[IPlen]:[IP]
EVPN type-3 prefix: [3]:[EthTag]:[IPlen]:[OrigIP]
EVPN type-4 prefix: [4]:[ESI]:[IPlen]:[OrigIP]
EVPN type-5 prefix: [5]:[EthTag]:[IPlen]:[IP]
Network Next Hop Metric LocPrf Weight Path
Extended Community
Route Distinguisher: 10.226.14.24:3
*>i[2]:[0]:[48]:[00:00:20:20:00:fe]:[32]:[192.168.200.1]
10.226.14.201 100 0 i
RT:65001:99 RT:65001:10020 ET:8 Rmac:50:9a:4c:e6:7e:71
*>i[2]:[0]:[48]:[00:00:20:20:00:fe]:[128]:[2002:0:0:1::1]
10.226.14.201 100 0 i
RT:65001:99 RT:65001:10020 ET:8 Rmac:50:9a:4c:e6:7e:71
*>i[2]:[0]:[48]:[00:00:20:20:00:fe]:[128]:[fe80::529a:4c20:1e6:7e71]
10.226.14.201 100 0 i
RT:65001:10020 ET:8
*>i[2]:[0]:[48]:[00:0c:29:77:8b:15]
10.226.14.201 100 0 i
RT:65001:10020 ET:8
*>i[2]:[0]:[48]:[00:0c:29:77:8b:15]:[128]:[fe80::20c:29ff:fe77:8b15]
10.226.14.201 100 0 i
RT:65001:10020 ET:8
Route Distinguisher: 10.226.14.24:4
*>i[2]:[0]:[48]:[00:00:30:30:00:fe]:[32]:[192172.168.300.1]
10.226.14.201 100 0 i
RT:65001:99 RT:65001:10030 ET:8 Rmac:50:9a:4c:e6:7e:71
*>i[2]:[0]:[48]:[00:00:30:30:00:fe]:[128]:[2003:0:0:1::1]
10.226.14.201 100 0 i
RT:65001:99 RT:65001:10030 ET:8 Rmac:50:9a:4c:e6:7e:71
*>i[2]:[0]:[48]:[00:00:30:30:00:fe]:[128]:[fe80::529a:4c20:2e6:7e71]
10.226.14.201 100 0 i
RT:65001:10030 ET:8
*>i[2]:[0]:[48]:[00:0c:29:77:8b:15]
10.226.14.201 100 0 i
RT:65001:10030 ET:8
Route Distinguisher: 10.226.14.48:3
*>i[1]:[0]:[03:00:22:22:22:22:22:00:00:01]:[32]:[0.0.0.0]
10.226.14.202 100 0 i
RT:65001:10020 ET:8
*>i[1]:[0]:[03:00:22:22:22:22:22:00:00:02]:[32]:[0.0.0.0]
10.226.14.202 100 0 i
RT:65001:10020 ET:8
Route Distinguisher: 10.226.14.48:4
*>i[1]:[4294967295]:[03:00:22:22:22:22:22:00:00:01]:[32]:[0.0.0.0]
10.226.14.202 100 0 i
RT:65001:10020 RT:65001:10030 ET:8 ESI-label-Rt:AA
*>i[4]:[03:00:22:22:22:22:22:00:00:01]:[32]:[10.226.14.202]
10.226.14.202 100 0 i
ET:8 ES-Import-Rt:00:22:22:22:22:22 DF: (alg: 2, pref: 32767)
Route Distinguisher: 10.226.14.48:5
*>i[1]:[4294967295]:[03:00:22:22:22:22:22:00:00:02]:[32]:[0.0.0.0]
10.226.14.202 100 0 i
RT:65001:10020 RT:65001:10030 ET:8 ESI-label-Rt:AA
*>i[4]:[03:00:22:22:22:22:22:00:00:02]:[32]:[10.226.14.202]
10.226.14.202 100 0 i
ET:8 ES-Import-Rt:00:22:22:22:22:22 DF: (alg: 2, pref: 32767)
Route Distinguisher: 10.226.14.48:6
*>i[1]:[0]:[03:00:22:22:22:22:22:00:00:01]:[32]:[0.0.0.0]
10.226.14.202 100 0 i
RT:65001:10030 ET:8
*>i[1]:[0]:[03:00:22:22:22:22:22:00:00:02]:[32]:[0.0.0.0]
10.226.14.202 100 0 i
RT:65001:10030 ET:8
*>i[2]:[0]:[48]:[00:1e:c9:bb:c0:3c]:[32]:[192172.168.300.42]
10.226.14.202 100 0 i
ESI:03:00:22:22:22:22:22:00:00:01 VNI: 0
RT:65001:99 RT:65001:10030 ET:8 Rmac:18:5a:58:37:64:61
*>i[2]:[0]:[48]:[00:1e:c9:bb:c0:3c]:[128]:[2003:0:0:1::42]
10.226.14.202 100 0 i
ESI:03:00:22:22:22:22:22:00:00:01 VNI: 0
RT:65001:99 RT:65001:10030 ET:8 Rmac:18:5a:58:37:64:61
*>i[2]:[0]:[48]:[00:1e:c9:bb:c0:3c]:[128]:[fe80::21e:c9ff:febb:c03c]
10.226.14.202 100 0 i
ESI:03:00:22:22:22:22:22:00:00:01 VNI: 0
RT:65001:10030 ET:8
Route Distinguisher: 10.226.14.207:3
*> [1]:[0]:[03:00:22:22:22:22:22:00:00:01]:[128]:[::]
10.226.14.254 32768 i
ET:8 RT:65001:10020
*> [1]:[0]:[03:00:22:22:22:22:22:00:00:02]:[128]:[::]
10.226.14.254 32768 i
ET:8 RT:65001:10020
*> [2]:[0]:[48]:[00:00:20:00:00:fe]
10.226.14.254 32768 i
ET:8 RT:65001:10020
*> [2]:[0]:[48]:[00:00:20:00:00:fe]:[32]:[192.168.200.2]
10.226.14.254 32768 i
ET:8 RT:65001:10020 RT:65001:99 Rmac:04:f8:f8:20:67:7b
*> [2]:[0]:[48]:[00:00:20:00:00:fe]:[128]:[2002:0:0:1::2]
10.226.14.254 32768 i
ET:8 RT:65001:10020 RT:65001:99 Rmac:04:f8:f8:20:67:7b
*> [2]:[0]:[48]:[00:00:20:00:00:fe]:[128]:[fe80::6f8:f810:120:677b]
10.226.14.254 32768 i
ET:8 RT:65001:10020
Route Distinguisher: 10.226.14.207:4
*> [1]:[4294967295]:[03:00:22:22:22:22:22:00:00:01]:[128]:[::]
10.226.14.254 32768 i
ET:8 ESI-label-Rt:AA RT:65001:10020 RT:65001:10030
*> [4]:[03:00:22:22:22:22:22:00:00:01]:[32]:[10.226.14.254]
10.226.14.254 32768 i
ET:8 ES-Import-Rt:00:22:22:22:22:22 DF: (alg: 2, pref: 1)
Route Distinguisher: 10.226.14.207:5
*> [1]:[4294967295]:[03:00:22:22:22:22:22:00:00:02]:[128]:[::]
10.226.14.254 32768 i
ET:8 ESI-label-Rt:AA RT:65001:10020 RT:65001:10030
*> [4]:[03:00:22:22:22:22:22:00:00:02]:[32]:[10.226.14.254]
10.226.14.254 32768 i
ET:8 ES-Import-Rt:00:22:22:22:22:22 DF: (alg: 2, pref: 1)
Route Distinguisher: 10.226.14.207:6
*> [1]:[0]:[03:00:22:22:22:22:22:00:00:01]:[128]:[::]
10.226.14.254 32768 i
ET:8 RT:65001:10030
*> [1]:[0]:[03:00:22:22:22:22:22:00:00:02]:[128]:[::]
10.226.14.254 32768 i
ET:8 RT:65001:10030
*> [2]:[0]:[48]:[00:00:30:00:00:fe]
10.226.14.254 32768 i
ET:8 RT:65001:10030
*> [2]:[0]:[48]:[00:00:30:00:00:fe]:[32]:[192.168.30.2]
10.226.14.254 32768 i
ET:8 RT:65001:10030 RT:65001:99 Rmac:04:f8:f8:20:67:7b
*> [2]:[0]:[48]:[00:00:30:00:00:fe]:[128]:[2003:0:0:1::2]
10.226.14.254 32768 i
ET:8 RT:65001:10030 RT:65001:99 Rmac:04:f8:f8:20:67:7b
*> [2]:[0]:[48]:[00:00:30:00:00:fe]:[128]:[fe80::6f8:f810:220:677b]
10.226.14.254 32768 i
ET:8 RT:65001:10030
*> [2]:[0]:[48]:[00:1e:c9:bb:c0:3c]:[32]:[192.168.30.42]
10.226.14.254 32768 i
ESI:03:00:22:22:22:22:22:00:00:01
ET:8 RT:65001:10030 RT:65001:99 Rmac:04:f8:f8:20:67:7b ND:Proxy
*> [2]:[0]:[48]:[00:1e:c9:bb:c0:3c]:[128]:[2003:0:0:1::42]
10.226.14.254 32768 i
ESI:03:00:22:22:22:22:22:00:00:01
ET:8 RT:65001:10030 RT:65001:99 Rmac:04:f8:f8:20:67:7b ND:Proxy
*> [2]:[0]:[48]:[00:1e:c9:bb:c0:3c]:[128]:[fe80::21e:c9ff:febb:c03c]
10.226.14.254 32768 i
ESI:03:00:22:22:22:22:22:00:00:01
ET:8 RT:65001:10030 ND:Proxy
Route Distinguisher: 10.226.14.208:3
*>i[1]:[0]:[03:00:22:22:22:22:22:00:00:01]:[32]:[0.0.0.0]
10.226.14.253 100 0 i
RT:65001:10020 ET:8
*>i[1]:[0]:[03:00:22:22:22:22:22:00:00:02]:[32]:[0.0.0.0]
10.226.14.253 100 0 i
RT:65001:10020 ET:8
Route Distinguisher: 10.226.14.208:4
*>i[1]:[4294967295]:[03:00:22:22:22:22:22:00:00:01]:[32]:[0.0.0.0]
10.226.14.253 100 0 i
RT:65001:10020 RT:65001:10030 ET:8 ESI-label-Rt:AA
*>i[4]:[03:00:22:22:22:22:22:00:00:01]:[32]:[10.226.14.253]
10.226.14.253 100 0 i
ET:8 ES-Import-Rt:00:22:22:22:22:22 DF: (alg: 2, pref: 32767)
Route Distinguisher: 10.226.14.208:5
*>i[1]:[4294967295]:[03:00:22:22:22:22:22:00:00:02]:[32]:[0.0.0.0]
10.226.14.253 100 0 i
RT:65001:10020 RT:65001:10030 ET:8 ESI-label-Rt:AA
*>i[4]:[03:00:22:22:22:22:22:00:00:02]:[32]:[10.226.14.253]
10.226.14.253 100 0 i
ET:8 ES-Import-Rt:00:22:22:22:22:22 DF: (alg: 2, pref: 32767)
Route Distinguisher: 10.226.14.208:6
*>i[1]:[0]:[03:00:22:22:22:22:22:00:00:01]:[32]:[0.0.0.0]
10.226.14.253 100 0 i
RT:65001:10030 ET:8
*>i[1]:[0]:[03:00:22:22:22:22:22:00:00:02]:[32]:[0.0.0.0]
10.226.14.253 100 0 i
RT:65001:10030 ET:8
*>i[2]:[0]:[48]:[00:1e:c9:bb:c0:3c]:[32]:[192.168.30.42]
10.226.14.253 100 0 i
ESI:03:00:22:22:22:22:22:00:00:01 VNI: 0
RT:65001:99 RT:65001:10030 ET:8 Rmac:18:5a:58:37:55:e1 ND:Proxy
*>i[2]:[0]:[48]:[00:1e:c9:bb:c0:3c]:[128]:[2003:0:0:1::42]
10.226.14.253 100 0 i
ESI:03:00:22:22:22:22:22:00:00:01 VNI: 0
RT:65001:99 RT:65001:10030 ET:8 Rmac:18:5a:58:37:55:e1 ND:Proxy
*>i[2]:[0]:[48]:[00:1e:c9:bb:c0:3c]:[128]:[fe80::21e:c9ff:febb:c03c]
10.226.14.253 100 0 i
ESI:03:00:22:22:22:22:22:00:00:01 VNI: 0
RT:65001:10030 ET:8 ND:Proxy
Route Distinguisher: 24.24.24.24:2
*>i[5]:[0]:[24]:[172.16.0.0]
10.226.14.201 0 100 0 ?
RT:65001:99 ET:8 Rmac:50:9a:4c:e6:7e:71
*>i[5]:[0]:[24]:[192.168.20.0]
10.226.14.201 0 100 0 ?
RT:65001:99 ET:8 Rmac:50:9a:4c:e6:7e:71
*>i[5]:[0]:[24]:[192.168.30.0]
10.226.14.201 0 100 0 ?
RT:65001:99 ET:8 Rmac:50:9a:4c:e6:7e:71
*>i[5]:[0]:[64]:[2002:0:0:1::]
10.226.14.201 0 100 0 ?
RT:65001:99 ET:8 Rmac:50:9a:4c:e6:7e:71
*>i[5]:[0]:[64]:[2003:0:0:1::]
10.226.14.201 0 100 0 ?
RT:65001:99 ET:8 Rmac:50:9a:4c:e6:7e:71
*>i[5]:[0]:[64]:[2006:0:0:1::]
10.226.14.201 0 100 0 ?
RT:65001:99 ET:8 Rmac:50:9a:4c:e6:7e:71
Displayed 56 prefixes (56 paths) |
...
| Info | ||
|---|---|---|
| ||
PICOS supports only one VXLAN segment mapping to one IP multicast group, which is the way to provide the optimal multicast forwarding. That is, to have multiple VXLAN segments share a single IP multicast group in the core network is not supported. |
...