The following vPC and
FEX (the fabric is extended using Cisco Nexus 2000 Series Fabric Extender
device) scenarios are supported:
vPC configuration
for Cisco Nexus 5600 Series Switches
Figure 1. vPC
configuration
In the above
topology, VTEP 1 and VTEP 2 are ToR switches and vPC peers. Sample vPC
configurations are given below. For comprehensive information on vPC, refer to
the respective Cisco Nexus Series 5600 and 7000 Series vPC design/configuration
guide.
Attention: Many of the configurations mentioned below need to be configured
identically on the primary and secondary vPC peer switches, noted as
vPC-primary
and vPC-secondary peer switches. Configurations that are different between
the peer switches are explicitly mentioned as vPC-primary peer
switch and
vPC-secondary
peer switch.
Configure the vPC features
(config) #
feature lacp
feature vpc
Create a vPC domain
vPC-primary peer switch
(config) #
vpc domain 100
peer-keepalive destination 10.1.1.156 source 10.1.1.154
delay restore 150
auto-recovery
ip arp synchronize
ipv6 nd synchronize
vPC-secondary peer
switch
(config) #
vpc domain 100
peer-keepalive destination 10.1.1.154 source 10.1.1.156
delay restore 150
auto-recovery
ip arp synchronize
ipv6 nd synchronize
Configure the secondary IP
address on the loopback. This will be used as the virtual IP address (vIP) for
both vPC peers
The secondary IP
address of the source VTEP interface of the fabric (say, VTEP1/VTEP2 as source
and VTEP 3 as destination) will be used as the source IP address in the VxLAN
outer IP header. In a vPC scenario when EVPN is enabled, EVPN advertises the
secondary IP address as the next hop address in the BGP update message. This is
true for all route types including MAC routes, host IP routes, prefix routes
etc. This is different from VXLAN flood-n-learn operation where for orphan
ports the VXLAN outer IP header is set to the physical Peer IP or PIP when
traffic ingresses in from the orphan ports and the VIP is only used when
traffic ingresses in from the vPC ports.
vPC-primary peer switch
(config) #
interface loopback1
ip address 10.1.2.54/32
ip address 192.0.2.110/32 secondary
interface nve 1
source-interface loopback0
host-reachability protocol bgp
vPC-secondary peer
switch
(config) #
interface loopback1
ip address 10.1.2.56/32
ip address 192.0.2.110/32 secondary
interface nve 1
source-interface loopback1
host-reachability protocol bgp
Note that the
secondary IP address configured on the vPC primary and vPC secondary peer
switches is the same.
Create the peer-link
port-channel
vPC-primary and
vPC-secondary peer switches
(config) #
interface port-channel 10
description "vpc-peer-link"
switchport mode trunk
spanning-tree port type network
vpc peer-link
Configure the peer-link
interface
vPC-primary and
vPC-secondary peer switches
(config) #
interface Ethernet1/1
switchport mode trunk
channel-group 10 mode active
Configure the peer link
VLAN and routing between the vPC peer switches
Note |
The
vpc nve
peer-link-vlan command needs to be used only in the Cisco Nexus
5600 Series switches. Cisco Nexus 5600 Series switches encapsulate VXLAN
packets over the MCT port with the configured VLAN as the outer-vlan tag while
Cisco Nexus 7000,7700,9000 Series switches decapsulate VXLAN packets coming
from the core and the decapsulated packet is bridged across the MCT link since
they use ASM/SSM protocols.
|
You can use IS-IS
or OSPF as the routing protocol between the vPC peer switches, as mentioned
below:
IS-IS
vPC-primary peer switch
(config) #
vlan 123
interface Vlan123
no shutdown
ip address 38.38.38.54/24
isis metric 10 level-1
ip router isis PEER-LINK
ip pim sparse-mode
vpc nve peer-link-vlan 123
vPC-secondary peer
switch
(config) #
vlan 123
interface Vlan123
no shutdown
ip address 38.38.38.56/24
isis metric 10 level-1
ip router isis PEER-LINK
ip pim sparse-mode
vpc nve peer-link-vlan 123
OSPF
vPC-primary peer switch
(config) #
vlan 123
interface vlan123
no shutdown
no ip redirects
ip address 38.38.38.54/24
ip ospf cost 10
ip router ospf PEER-LINK area 0.0.0.0
ip pim sparse-mode
vpc nve peer-link-vlan 123
vPC-secondary peer
switch
(config) #
vlan 123
interface vlan123
no shutdown
no ip redirects
ip address 38.38.38.56/24
ip ospf cost 10
ip router ospf PEER-LINK area 0.0.0.0
ip pim sparse-mode
vpc nve peer-link-vlan 123
Configure the vPC host
interface
From the image,
you can see that an end host is (dual) attached to the peer switches. You need
to configure the peer switches on the same port channel to enable end host dual
attachment.
vPC-primary and
vPC-secondary peer switches
(config) #
interface Ethernet1/5
switchport mode trunk
channel-group 35
interface port-channel 35
switchport mode trunk
spanning-tree port type edge trunk
Exclude the peer link VLAN
from server facing ports
vPC-primary and
vPC-secondary peer switches
(config) #
interface port-channel 35
switchport trunk allowed vlan except 123
interface e1/5
switchport trunk allowed vlan except 123
BUM (Layer-2
multicast) traffic behavior in VXLAN EVPN environments is identical to that in
VXLAN flood and learn environments. For additional information on VXLAN flood
and learn, refer to the respective Cisco Nexus Series 5600 or 7000/7700 VXLAN
configuration guide.
Verify vPC
configuration
For verification of MAC
routes, refer these commands:
vPC-primary peer switch# show mac address-table dynamic
Legend:
* - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MAC
age - seconds since last seen,+ - primary entry using vPC Peer-Link
VLAN MAC Address Type age Secure NTFY Ports/SWID.SSID.LID
---------+-----------------+--------+---------+------+----+------------------
* 200 002a.6a44.9381 dynamic 1800 F F Po35
* 200 2010.0000.0010 dynamic 700 F F Eth100/1/1
+ 200 2010.0000.0011 dynamic 0 F F nve1/10.1.1.56
* 200 2010.0000.0012 dynamic 0 F F nve1/10.1.1.74
+ 200 2010.0000.0013 dynamic 0 F F nve1/10.1.1.56
* 123 002a.6ab2.0181 dynamic 0 F F Po10
* 1 a036.9f19.8ee4 dynamic 0 F F Po10
+ 1 a036.9f1a.b970 dynamic 0 F F Po10
* 1 a036.9f1a.c134 dynamic 0 F F Po10
* 1 a036.9f1a.c135 dynamic 120 F F Eth100/1/3
+ 1 a036.9f22.a30e dynamic 0 F F Po10
vPC-secondary peer switch# show mac address-table dynamic
Legend:
* - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MAC
age - seconds since last seen,+ - primary entry using vPC Peer-Link
VLAN MAC Address Type age Secure NTFY Ports/SWID.SSID.LID
---------+-----------------+--------+---------+------+----+------------------
* 200 002a.6a44.9381 dynamic 300 F F Po35
* 200 2010.0000.0010 dynamic 30 F F Eth100/1/1
* 200 2010.0000.0011 dynamic 40 F F Eth101/1/1
* 200 2010.0000.0012 dynamic 0 F F nve1/10.1.1.74
* 200 2010.0000.0013 dynamic 20 F F Eth1/6
* 123 002a.6a6e.cbc1 dynamic 0 F F Po10
* 1 a036.9f19.8ee4 dynamic 0 F F Eth101/1/4
* 1 a036.9f1a.b970 dynamic 1770 F F Eth101/1/1
* 1 a036.9f1a.c134 dynamic 30 F F Eth101/1/3
* 1 a036.9f1a.c135 dynamic 110 F F Eth100/1/3
vPC-primary peer switch# show l2route evpn mac all
Topology Mac Address Prod Next Hop (s)
----------- -------------- ------ ---------------
200 002a.6a44.9381 Local Po35
200 2010.0000.0010 Local Eth100/1/1
200 2010.0000.0011 Local nve1/10.1.1.56
200 2010.0000.0012 BGP 10.1.1.74
200 2010.0000.0013 Local nve1/10.1.1.56
2200 8c60.4f14.2efc VXLAN 10.1.1.74
vPC-secondary peer switch# show l2route evpn mac all
Topology Mac Address Prod Next Hop (s)
----------- -------------- ------ ---------------
200 002a.6a44.9381 Local Po35
200 2010.0000.0010 Local Eth100/1/1
200 2010.0000.0011 Local Eth101/1/1
200 2010.0000.0012 BGP 10.1.1.74
200 2010.0000.0013 Local Eth1/6
2200 8c60.4f14.2efc VXLAN 10.1.1.74
vPC-primary peer switch# show bgp l2vpn evpn
BGP routing table information for VRF default, address family L2VPN EVPN
BGP table version is 410, local router ID is 10.1.1.54
Status: s-suppressed, x-deleted, S-stale, d-dampened, h-history, *-valid, >-best
Path type: i-internal, e-external, c-confed, l-local, a-aggregate, r-redist, I-i
njected
Origin codes: i - IGP, e - EGP, ? - incomplete, | - multipath, & - backup
Network Next Hop Metric LocPrf Weight Path
Route Distinguisher: 10.1.1.54:32967 (L2VNI 30200)
*>l[2]:[0]:[0]:[48]:[002a.6a44.9381]:[0]:[0.0.0.0]/216
2.2.2.2 100 32768 i
* i 2.2.2.2 100 0 i
*>l[2]:[0]:[0]:[48]:[2010.0000.0010]:[0]:[0.0.0.0]/216
2.2.2.2 100 32768 i
* i 2.2.2.2 100 0 i
*>l[2]:[0]:[0]:[48]:[2010.0000.0011]:[0]:[0.0.0.0]/216
2.2.2.2 100 32768 i
* i 2.2.2.2 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0012]:[0]:[0.0.0.0]/216
10.1.1.74 100 0 i
*>l[2]:[0]:[0]:[48]:[2010.0000.0013]:[0]:[0.0.0.0]/216
2.2.2.2 100 32768 i
* i 2.2.2.2 100 0 i
*>l[2]:[0]:[0]:[48]:[002a.6a44.9381]:[32]:[200.0.0.35]/272
2.2.2.2 100 32768 i
* i 2.2.2.2 100 0 i
* i[2]:[0]:[0]:[48]:[2010.0000.0010]:[32]:[200.0.0.10]/272
2.2.2.2 100 0 i
*>l 2.2.2.2 100 32768 i
*>l[2]:[0]:[0]:[48]:[2010.0000.0011]:[32]:[200.0.0.11]/272
2.2.2.2 100 32768 i
* i 2.2.2.2 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0012]:[32]:[200.0.0.12]/272
10.1.1.74 100 0 i
*>l[2]:[0]:[0]:[48]:[2010.0000.0013]:[32]:[200.0.0.13]/272
2.2.2.2 100 32768 i
* i 2.2.2.2 100 0 i
Route Distinguisher: 10.1.1.56:3
*>i[5]:[0]:[0]:[24]:[200.0.0.0]:[0.0.0.0]/224
2.2.2.2 0 100 0 ?
Route Distinguisher: 10.1.1.56:32967
*>i[2]:[0]:[0]:[48]:[002a.6a44.9381]:[0]:[0.0.0.0]/216
2.2.2.2 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0010]:[0]:[0.0.0.0]/216
2.2.2.2 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0011]:[0]:[0.0.0.0]/216
2.2.2.2 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0013]:[0]:[0.0.0.0]/216
2.2.2.2 100 0 i
*>i[2]:[0]:[0]:[48]:[002a.6a44.9381]:[32]:[200.0.0.35]/272
2.2.2.2 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0010]:[32]:[200.0.0.10]/272
2.2.2.2 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0011]:[32]:[200.0.0.11]/272
2.2.2.2 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0013]:[32]:[200.0.0.13]/272
2.2.2.2 100 0 i
Route Distinguisher: 10.1.1.74:32967
*>i[2]:[0]:[0]:[48]:[2010.0000.0012]:[0]:[0.0.0.0]/216
10.1.1.74 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0012]:[32]:[200.0.0.12]/272
10.1.1.74 100 0 i
vPC-secondary peer switch# show bgp l2vpn evpn
BGP routing table information for VRF default, address family L2VPN EVPN
BGP table version is 308, local router ID is 10.1.1.56
Status: s-suppressed, x-deleted, S-stale, d-dampened, h-history, *-valid, >-best
Path type: i-internal, e-external, c-confed, l-local, a-aggregate, r-redist, I-i
njected
Origin codes: i - IGP, e - EGP, ? - incomplete, | - multipath, & - backup
Network Next Hop Metric LocPrf Weight Path
Route Distinguisher: 10.1.1.54:3
*>i[5]:[0]:[0]:[24]:[200.0.0.0]:[0.0.0.0]/224
2.2.2.2 0 100 0 ?
Route Distinguisher: 10.1.1.54:32967
*>i[2]:[0]:[0]:[48]:[002a.6a44.9381]:[0]:[0.0.0.0]/216
2.2.2.2 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0010]:[0]:[0.0.0.0]/216
2.2.2.2 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0011]:[0]:[0.0.0.0]/216
2.2.2.2 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0013]:[0]:[0.0.0.0]/216
2.2.2.2 100 0 i
*>i[2]:[0]:[0]:[48]:[002a.6a44.9381]:[32]:[200.0.0.35]/272
2.2.2.2 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0010]:[32]:[200.0.0.10]/272
2.2.2.2 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0011]:[32]:[200.0.0.11]/272
2.2.2.2 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0013]:[32]:[200.0.0.13]/272
2.2.2.2 100 0 i
Route Distinguisher: 10.1.1.56:32967 (L2VNI 30200)
* i[2]:[0]:[0]:[48]:[002a.6a44.9381]:[0]:[0.0.0.0]/216
2.2.2.2 100 0 i
*>l 2.2.2.2 100 32768 i
* i[2]:[0]:[0]:[48]:[2010.0000.0010]:[0]:[0.0.0.0]/216
2.2.2.2 100 0 i
*>l 2.2.2.2 100 32768 i
* i[2]:[0]:[0]:[48]:[2010.0000.0011]:[0]:[0.0.0.0]/216
2.2.2.2 100 0 i
*>l 2.2.2.2 100 32768 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0012]:[0]:[0.0.0.0]/216
10.1.1.74 100 0 i
* i[2]:[0]:[0]:[48]:[2010.0000.0013]:[0]:[0.0.0.0]/216
2.2.2.2 100 0 i
*>l 2.2.2.2 100 32768 i
* i[2]:[0]:[0]:[48]:[002a.6a44.9381]:[32]:[200.0.0.35]/272
2.2.2.2 100 0 i
*>l 2.2.2.2 100 32768 i
*>l[2]:[0]:[0]:[48]:[2010.0000.0010]:[32]:[200.0.0.10]/272
2.2.2.2 100 32768 i
* i 2.2.2.2 100 0 i
* i[2]:[0]:[0]:[48]:[2010.0000.0011]:[32]:[200.0.0.11]/272
*>i[2]:[0]:[0]:[48]:[2010.0000.0012]:[32]:[200.0.0.12]/272
10.1.1.74 100 0 i
* i[2]:[0]:[0]:[48]:[2010.0000.0013]:[32]:[200.0.0.13]/272
2.2.2.2 100 0 i
*>l 2.2.2.2 100 32768 i
Route Distinguisher: 10.1.1.74:32967
*>i[2]:[0]:[0]:[48]:[2010.0000.0012]:[0]:[0.0.0.0]/216
10.1.1.74 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0012]:[32]:[200.0.0.12]/272
10.1.1.74 100 0 i
vPC-primary peer switch# show nve peers
Interface Peer-IP State LearnType Uptime Router-Mac
--------- --------------- ----- --------- -------- -----------------
nve1 10.1.1.56 Up CP 01:41:24 n/a
nve1 10.1.1.74 Up CP 01:41:19 8c60.4f14.2efc
vPC-secondary peer switch# show nve peers
Interface Peer-IP State LearnType Uptime Router-Mac
--------- --------------- ----- --------- -------- -----------------
nve1 10.1.1.54 Up CP 1d01h n/a
nve1 10.1.1.74 Up CP 4d09h 8c60.4f14.2efc
For verification of IP
host and prefix routes, refer these commands
vPC-primary peer switch# show ip arp vrf all
Flags: * - Adjacencies learnt on non-active FHRP router
+ - Adjacencies synced via CFSoE
# - Adjacencies Throttled for Glean
D - Static Adjacencies attached to down interface
IP ARP Table for all contexts
Total number of entries: 8
Address Age MAC Address Interface
10.1.1.156 00:13:04 002a.6ab2.0141 mgmt0
10.1.1.233 00:00:23 0050.569f.6c61 mgmt0
1.1.1.53 00:12:51 002a.6a85.a5bc Ethernet1/24
38.38.38.56 00:02:55 002a.6ab2.0181 Vlan123
200.0.0.10 00:09:02 2010.0000.0010 Vlan200
200.0.0.11 00:06:37 2010.0000.0011 Vlan200 +
200.0.0.13 00:06:34 2010.0000.0013 Vlan200 +
200.0.0.35 00:00:28 002a.6a44.9381 Vlan200 +
vPC-secondary peer switch# show ip arp vrf all
Flags: * - Adjacencies learnt on non-active FHRP router
+ - Adjacencies synced via CFSoE
# - Adjacencies Throttled for Glean
D - Static Adjacencies attached to down interface
IP ARP Table for all contexts
Total number of entries: 8
Address Age MAC Address Interface
10.1.1.154 00:13:11 002a.6a6e.cb81 mgmt0
10.1.1.233 00:00:30 0050.569f.6c61 mgmt0
1.1.1.53 00:04:27 002a.6a85.a5bc Ethernet1/26
38.38.38.54 00:03:03 002a.6a6e.cbc1 Vlan123
200.0.0.10 00:09:09 2010.0000.0010 Vlan200 +
200.0.0.11 00:06:45 2010.0000.0011 Vlan200
200.0.0.13 00:06:41 2010.0000.0013 Vlan200
200.0.0.35 00:00:36 002a.6a44.9381 Vlan200
vPC-primary peer switch# show ip route vrf all
IP Route Table for VRF "default"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>
1.1.1.53/32, ubest/mbest: 1/0
*via 1.1.1.53, Eth1/24, [110/5], 16:40:48, ospf-UNDERLAY, intra
10.1.1.54/32, ubest/mbest: 2/0, attached
*via 10.1.1.54, Lo0, [0/0], 01:59:11, local
*via 10.1.1.54, Lo0, [0/0], 01:59:11, direct
10.1.1.56/32, ubest/mbest: 1/0
*via 1.1.1.53, Eth1/24, [110/9], 16:40:42, ospf-UNDERLAY, intra
10.1.1.74/32, ubest/mbest: 1/0
*via 1.1.1.53, Eth1/24, [110/9], 16:40:39, ospf-UNDERLAY, intra
2.2.2.2/32, ubest/mbest: 2/0, attached
*via 2.2.2.2, Lo0, [0/0], 01:59:11, local
*via 2.2.2.2, Lo0, [0/0], 01:59:11, direct
10.254.254.2/32, ubest/mbest: 1/0
*via 1.1.1.53, Eth1/24, [110/5], 16:40:00, ospf-UNDERLAY, intra
10.254.254.66/32, ubest/mbest: 1/0
*via 1.1.1.53, Eth1/24, [110/5], 16:39:55, ospf-UNDERLAY, intra
38.38.38.0/24, ubest/mbest: 1/0, attached
*via 38.38.38.54, Vlan123, [0/0], 01:59:00, direct
38.38.38.54/32, ubest/mbest: 1/0, attached
*via 38.38.38.54, Vlan123, [0/0], 01:59:00, local
IP Route Table for VRF "management"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>
0.0.0.0/0, ubest/mbest: 1/0
*via 10.1.1.233, [1/0], 4d08h, static
10.1.1.0/24, ubest/mbest: 1/0, attached
*via 10.1.1.154, mgmt0, [0/0], 4d08h, direct
10.1.1.154/32, ubest/mbest: 1/0, attached
*via 10.1.1.154, mgmt0, [0/0], 4d08h, local
IP Route Table for VRF "sml:vpn2200"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>
200.0.0.0/24, ubest/mbest: 1/0, attached
*via 200.0.0.1, Vlan200, [0/0], 01:59:00, direct, tag 12345,
200.0.0.1/32, ubest/mbest: 1/0, attached
*via 200.0.0.1, Vlan200, [0/0], 01:59:00, local, tag 12345,
200.0.0.10/32, ubest/mbest: 1/0, attached
*via 200.0.0.10, Vlan200, [190/0], 01:46:41, hmm
200.0.0.11/32, ubest/mbest: 1/0, attached
*via 200.0.0.11, Vlan200, [190/0], 01:46:41, hmm
200.0.0.12/32, ubest/mbest: 1/0
*via 10.1.1.74%default, [200/0], 01:59:04, bgp-100, internal, ta
-vpn)segid 32200 tunnel: 16843082 encap: 1
200.0.0.13/32, ubest/mbest: 1/0, attached
*via 200.0.0.13, Vlan200, [190/0], 01:46:36, hmm
200.0.0.35/32, ubest/mbest: 1/0, attached
*via 200.0.0.35, Vlan200, [190/0], 01:58:35, hmm
vPC-secondary peer switch# show ip route vrf all
IP Route Table for VRF "default"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>
1.1.1.53/32, ubest/mbest: 1/0
*via 1.1.1.53, Eth1/26, [110/5], 16:45:46, ospf-UNDERLAY, intra
10.1.1.54/32, ubest/mbest: 1/0
*via 1.1.1.53, Eth1/26, [110/9], 02:04:15, ospf-UNDERLAY, intra
10.1.1.56/32, ubest/mbest: 2/0, attached
*via 10.1.1.56, Lo0, [0/0], 4d10h, local
*via 10.1.1.56, Lo0, [0/0], 4d10h, direct
10.1.1.74/32, ubest/mbest: 1/0
*via 1.1.1.53, Eth1/26, [110/9], 16:45:43, ospf-UNDERLAY, intra
2.2.2.2/32, ubest/mbest: 2/0, attached
*via 2.2.2.2, Lo0, [0/0], 4d10h, local
*via 2.2.2.2, Lo0, [0/0], 4d10h, direct
10.254.254.2/32, ubest/mbest: 1/0
*via 1.1.1.53, Eth1/26, [110/5], 16:45:04, ospf-UNDERLAY, intra
10.254.254.66/32, ubest/mbest: 1/0
*via 1.1.1.53, Eth1/26, [110/5], 16:44:59, ospf-UNDERLAY, intra
38.38.38.0/24, ubest/mbest: 1/0, attached
*via 38.38.38.56, Vlan123, [0/0], 02:04:13, direct
38.38.38.56/32, ubest/mbest: 1/0, attached
*via 38.38.38.56, Vlan123, [0/0], 02:04:13, local
IP Route Table for VRF "management"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>
0.0.0.0/0, ubest/mbest: 1/0
*via 10.1.1.233, [1/0], 4d10h, static
10.1.1.0/24, ubest/mbest: 1/0, attached
*via 10.1.1.156, mgmt0, [0/0], 4d10h, direct
10.1.1.156/32, ubest/mbest: 1/0, attached
*via 10.1.1.156, mgmt0, [0/0], 4d10h, local
IP Route Table for VRF "sml:vpn2200"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>
200.0.0.0/24, ubest/mbest: 1/0, attached
*via 200.0.0.1, Vlan200, [0/0], 4d10h, direct, tag 12345,
200.0.0.1/32, ubest/mbest: 1/0, attached
*via 200.0.0.1, Vlan200, [0/0], 4d10h, local, tag 12345,
200.0.0.10/32, ubest/mbest: 1/0, attached
*via 200.0.0.10, Vlan200, [190/0], 01:51:46, hmm
200.0.0.11/32, ubest/mbest: 1/0, attached
*via 200.0.0.11, Vlan200, [190/0], 01:51:46, hmm
200.0.0.12/32, ubest/mbest: 1/0
*via 10.1.1.74%default, [200/0], 02:07:28, bgp-100, internal, tag 100, (mpls
-vpn)segid 32200 tunnel: 16843082 encap: 1
200.0.0.13/32, ubest/mbest: 1/0, attached
*via 200.0.0.13, Vlan200, [190/0], 01:51:40, hmm
200.0.0.35/32, ubest/mbest: 1/0, attached
*via 200.0.0.35, Vlan200, [190/0], 02:03:39, hmm
vPC-primary peer switch# show l2route evpn mac-ip all
Topology ID Mac Address Prod Host IP Next Hop
(s)
----------- -------------- ---- --------------------------------------- --------
200 002a.6a44.9381 HMM 200.0.0.35 N/A
200 2010.0000.0012 BGP 200.0.0.12 10.1.1.74
vPC-secondary peer switch# show l2route evpn mac-ip all
n6k-56-poap# show l2route evpn mac-ip all
Topology ID Mac Address Prod Host IP Next Hop
(s)
----------- -------------- ---- --------------------------------------- --------
200 002a.6a44.9381 HMM 200.0.0.35 N/A
200 2010.0000.0012 BGP 200.0.0.12 10.1.1.74
vPC-primary peer switch# show bgp l2vpn evpn
Route Distinguisher: 10.1.1.54:3 (L3VNI 32200)
*>i[2]:[0]:[0]:[48]:[002a.6a44.9381]:[32]:[200.0.0.35]/272
2.2.2.2 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0010]:[32]:[200.0.0.10]/272
2.2.2.2 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0011]:[32]:[200.0.0.11]/272
2.2.2.2 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0012]:[32]:[200.0.0.12]/272
10.1.1.74 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0013]:[32]:[200.0.0.13]/272
2.2.2.2 100 0 i
*>l[5]:[0]:[0]:[24]:[200.0.0.0]:[0.0.0.0]/224
2.2.2.2 0 100 32768 ?
* i 2.2.2.2 0 100 0 ?
vPC-secondary peer switch# show bgp l2vpn evpn
Route Distinguisher: 10.1.1.56:3 (L3VNI 32200)
*>i[2]:[0]:[0]:[48]:[002a.6a44.9381]:[32]:[200.0.0.35]/272
2.2.2.2 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0010]:[32]:[200.0.0.10]/272
2.2.2.2 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0011]:[32]:[200.0.0.11]/272
2.2.2.2 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0012]:[32]:[200.0.0.12]/272
10.1.1.74 100 0 i
*>i[2]:[0]:[0]:[48]:[2010.0000.0013]:[32]:[200.0.0.13]/272
2.2.2.2 100 0 i
* i[5]:[0]:[0]:[24]:[200.0.0.0]:[0.0.0.0]/224
2.2.2.2 0 100 0 ?
*>l 2.2.2.2 0 100 32768 ?
vPC configuration for Cisco Nexus 9000 Series Switches
Figure 2. vPC configuration
Configure the vPC features
(config) #
feature vpc
Create a vPC domain
vPC-primary peer switch
(config) #
vpc domain 1
peer-switch
peer-keepalive destination 192.0.2.30 source 192.0.2.20
delay restore 150
peer-gateway
auto-recovery
ip arp synchronize
ipv6 nd synchronize
vPC-secondary peer switch
(config) #
vpc domain 1
peer-switch
peer-keepalive destination 192.0.2.30 source 192.0.2.20
delay restore 150 peer-gateway
auto-recovery
ip arp synchronize
ipv6 nd synchronize
Configure the secondary IP address on the loopback. This will be
used as the virtual IP address (vIP) for both vPC peers
The secondary IP address of the source VTEP interface on vPC leaf
switches will be used as the source IP address in the VXLAN outer IP header. In
a vPC scenario when EVPN is enabled, EVPN advertises the secondary IP address
as the next hop address in the BGP update message. This is true for all route
types including MAC routes, host IP routes, prefix routes, etc.
vPC-primary peer switch
(config) #
interface loopback1
ip address 192.0.2.40/32
ip address 198.51.100.10/32 secondary
ip router isis UNDERLAY
ip pim sparse-mode
interface nve 1
source-interface loopback1
host-reachability protocol bgp
vPC-secondary peer switch
(config) #
interface loopback1
ip address 192.0.2.41/32
ip address 198.51.100.10/32 secondary
ip router isis UNDERLAY
ip pim sparse-mode
interface nve 1
source-interface loopback1
host-reachability protocol bgp
Note that the secondary IP address configured on the vPC primary and
vPC secondary peer switches is the same.
Create the peer-link port-channel
vPC-primary and vPC-secondary peer switches
(config) #
interface port-channel 10
description "vpc-peer-link”
switchport mode trunk
spanning-tree port type network
vpc peer-link
Configure the peer-link interface
vPC-primary and vPC-secondary peer switches
(config) #
interface Ethernet1/1
description “vpc-peer-link”
switchport mode trunk
channel-group 10 mode active
Configure the backup VLAN path between vPC peer switches
Note |
To provide a backup path when a vPC switch loses connectivity to
the spine, at least one SVI is required to be configured across the peer-link,
so that traffic can be forwarded to this vPC switch from its vPC peer switch
over the peer-link.
|
You can use IS-IS or OSPF as the routing protocol between the vPC peer
switches, as mentioned below:
IS-IS
vPC-primary peer switch
(config) #
vlan 123
interface Vlan123
no shutdown
ip address 192.0.2.100/24
ip router isis UNDERLAY
ip pim sparse-mode
no ip redirects
no ipv6 redirects
system nve infra-vlan 123
vPC-secondary peer switch
(config) #
vlan 123
interface Vlan123
no shutdown
ip address 192.0.2.101/24
ip router isis UNDERLAY
ip pim sparse-mode
no ip redirects
no ipv6 redirects
system nve infra-vlan 123
OSPF
vPC-primary peer switch
(config) #
vlan 123
interface Vlan123
no shutdown
ip address 192.0.2.100/24
ip router ospf UNDERLAY area 0.0.0.0
ip ospf network point-to-point
ip pim sparse-mode
no ip redirects
no ipv6 redirects
system nve infra-vlan 123
vPC-secondary peer switch
(config) #
vlan 123 interface vlan123
no shutdown
ip address 192.0.2.100/24
ip router ospf UNDERLAY area 0.0.0.0
ip ospf network point-to-point
ip pim sparse-mode
no ip redirects
no ipv6 redirects
system nve infra-vlan 123
Configure the vPC host interface
As shown in the figure, an end host is (dual) attached to both vPC
peer switches. Same port channel must be configured on both switches to enable
end host dual attachment.
vPC-primary and vPC-secondary peer switches
(config) #
interface Ethernet1/2
switchport mode trunk
channel-group 52
interface port-channel 52
switchport mode trunk
vpc 52