12-31-2022 03:45 PM - edited 12-31-2022 06:42 PM
Hi Please see the below VXLAN diagram. The only issue is VTEP01 and VTEP02 can not see nve peers each other via command show nve peers and PC01 cannot ping PC02. VTEP01 and VTEP02 can ping each other, and all show ip mroute 239.1.1.1, and show nvee interface nve1, show nve nvi, show bridge-domain are normal. VTEP01 config as below, which is symetric to VTEP02.
VTEP01 config
ip multicast-routing distributed
bridge-domain 1
member vni 5012
member GigabitEthernet2 service-instance 1
interface Loopback0
ip address 1.1.1.1 255.255.255.0
!
interface GigabitEthernet2
no ip address
ip pim sparse-mode
service instance 1 ethernet
encapsulation untagged
interface GigabitEthernet3
mac-address 0000.5e00.5311
ip address 192.168.13.1 255.255.255.0
ip pim sparse-mode
interface nve1
no ip address
source-interface Loopback0
member vni 5012 mcast-group 239.1.1.1
!
router ospf 1
network 1.1.1.1 0.0.0.0 area 0
network 192.168.13.0 0.0.0.255 area 0
!
ip pim bidir-enable
ip pim rp-address 3.3.3.3 bidir
Solved! Go to Solution.
12-31-2022 06:04 PM
Can you post show run all devices :
also below output :
#show nve interface nve 1 detail
#sh ip route
#show ip pim neigh
#show ip ospf neigh
01-01-2023 01:42 AM
(config)#interface Loopback 0 (config-if)#ip pim sparse-mode
I think you missing config pim sparse-mode under LO in VTEP's and Core.
12-31-2022 06:04 PM
Can you post show run all devices :
also below output :
#show nve interface nve 1 detail
#sh ip route
#show ip pim neigh
#show ip ospf neigh
12-31-2022 06:27 PM - edited 01-01-2023 09:09 AM
@balaji.bandi Thank you for your reply!
VTEP01#sho nve interface nve 1 de
Interface: nve1, State: Admin Up, Oper Up, Encapsulation: Vxlan,
BGP host reachability: Disable, VxLAN dport: 4789
VNI number: L3CP 0 L2CP 0 L2DP 1
source-interface: Loopback0 (primary:1.1.1.1 vrf:0)
Pkts In Bytes In Pkts Out Bytes Out
0 0 14 952
VTEP01#
VTEP01#sh ip route
Gateway of last resort is not set
1.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C 1.1.1.0/24 is directly connected, Loopback0
L 1.1.1.1/32 is directly connected, Loopback0
2.0.0.0/32 is subnetted, 1 subnets
O 2.2.2.2 [110/3] via 192.168.13.3, 04:05:19, GigabitEthernet3
3.0.0.0/32 is subnetted, 1 subnets
O 3.3.3.3 [110/2] via 192.168.13.3, 04:05:19, GigabitEthernet3
192.168.13.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.13.0/24 is directly connected, GigabitEthernet3
L 192.168.13.1/32 is directly connected, GigabitEthernet3
O 192.168.23.0/24 [110/2] via 192.168.13.3, 04:05:19, GigabitEthernet3
VTEP01#
VTEP01#show ip pim neighbor
PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
P - Proxy Capable, S - State Refresh Capable, G - GenID Capable,
L - DR Load-balancing Capable
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
192.168.13.3 GigabitEthernet3 04:05:49/00:01:23 v2 1 / DR B S P G
VTEP01#
VTEP01#show ip ospf nei
Neighbor ID Pri State Dead Time Address Interface
3.3.3.3 1 FULL/BDR 00:00:35 192.168.13.3 GigabitEthernet3
VTEP01#
-------------------------------------------------------------------
CORE#sh ip ospf nei
Neighbor ID Pri State Dead Time Address Interface
2.2.2.2 1 FULL/DR 00:00:35 192.168.23.2 GigabitEthernet3
1.1.1.1 1 FULL/DR 00:00:36 192.168.13.1 GigabitEthernet2
config:
interface Loopback0
ip address 3.3.3.3 255.255.255.255
interface GigabitEthernet2
ip address 192.168.13.3 255.255.255.0
ip pim sparse-mode
!
interface GigabitEthernet3
ip address 192.168.23.3 255.255.255.0
ip pim sparse-mode
router ospf 1
network 3.3.3.3 0.0.0.0 area 0
network 192.168.13.0 0.0.0.255 area 0
network 192.168.23.0 0.0.0.255 area 0
ip pim bidir-enable
ip pim rp-address 3.3.3.3 bidir
-------------------------------------------------------------------
VTEP02#sh nve interface nve 1 de
Interface: nve1, State: Admin Up, Oper Up, Encapsulation: Vxlan,
BGP host reachability: Disable, VxLAN dport: 4789
VNI number: L3CP 0 L2CP 0 L2DP 1
source-interface: Loopback0 (primary:2.2.2.2 vrf:0)
Pkts In Bytes In Pkts Out Bytes Out
0 0 8 544
VTEP02#
VTEP02#sho ip route
Gateway of last resort is not set
1.0.0.0/32 is subnetted, 1 subnets
O 1.1.1.1 [110/3] via 192.168.23.3, 04:11:51, GigabitEthernet3
2.0.0.0/32 is subnetted, 1 subnets
C 2.2.2.2 is directly connected, Loopback0
3.0.0.0/32 is subnetted, 1 subnets
O 3.3.3.3 [110/2] via 192.168.23.3, 04:12:04, GigabitEthernet3
O 192.168.13.0/24 [110/2] via 192.168.23.3, 04:11:55, GigabitEthernet3
192.168.23.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.23.0/24 is directly connected, GigabitEthernet3
L 192.168.23.2/32 is directly connected, GigabitEthernet3
VTEP02#
VTEP02#show ip pim neighbor
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
192.168.23.3 GigabitEthernet3 04:12:28/00:01:28 v2 1 / DR B S P G
VTEP02#
VTEP02#show ip ospf nei
Neighbor ID Pri State Dead Time Address Interface
3.3.3.3 1 FULL/BDR 00:00:37 192.168.23.3 GigabitEthernet3
Core
interface Loopback0
ip address 3.3.3.3 255.255.255.255
interface GigabitEthernet2
ip address 192.168.13.3 255.255.255.0
ip pim sparse-mode
interface GigabitEthernet3
ip address 192.168.23.3 255.255.255.0
ip pim sparse-mode
router ospf 1
network 3.3.3.3 0.0.0.0 area 0
network 192.168.13.0 0.0.0.255 area 0
network 192.168.23.0 0.0.0.255 area 0
ip pim bidir-enable
ip pim rp-address 3.3.3.3 bidir
01-01-2023 01:42 AM
(config)#interface Loopback 0 (config-if)#ip pim sparse-mode
I think you missing config pim sparse-mode under LO in VTEP's and Core.
01-01-2023 08:48 AM - edited 01-01-2023 09:29 AM
Thanks @MHM Cisco World for your reply! You are right. After the change, it can work
BTW, we think the three devices as a big switch. so that PC01 and PC02 do not need gateway configuration. but if these PC want to access other device in different subnet, where is gateway configured?
01-01-2023 11:59 AM
Glad you able to resolve the issue, the main reason for VXLAN extending , so the L2 Service will be extended between the sites.
Also if you looking to Tag the traffic you to be mapped with VNI example :
interface GigabitEthernetX
no ip address
negotiation auto
service instance 10 ethernet
encapsulation dot1q 100
rewrite ingress tag pop 1 symmetric
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide