cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1612
Views
0
Helpful
1
Replies

Leaf and spine toplogy not working

christianpho
Level 1
Level 1

Hi,

 

I'm trying to understand concept in used in Leaf and Spine topology.

 

My underlay network is OSPF and all switches has successfull OSPF relationship.

 

To make node advertisement more dynamic as possible I'm going to use BGP to advertize MAC location between leaf switch pair. To makes this anouncement process efficient as possible I like to use multicast "sparse-mode" to have to possibility to load balance the "rendez-point" between spine switches.

 

My multicast group is 232.0.0.1.

 

IOSV-0 192.168.1.1 and IOSV-1 192.168.1.2 are router only there to serve as end host to send ping request and reply. I had desktop 192.168.1.3 to be able to send continious ping to 192.168.1.2.

 

All of my router host and desktop machine are in VLAN10 and assigned to VNI-10.  I also define VLAN interface 10 192.168.1.254 on leaf 1 & 3 to valide connectivity between the host with the switch.  Desktop (192.168.1.3) is able to ping 192.168.1.254 (I suppose that should Leaf-1 respond) and router ISOV-1 (192.168.1.2) is able to ping 192.168.1.254 (I suppose that should Leaf-3 responding to his ping resquest) 

 

I think the issue that I have is related to multicast, but I don't understand what is missing. I based my lab on "Building Data Centers with VXLAN BGP EVPN - A Cisco NX-OS Perspective" document, with the only exception for the underlay network where I choose to use OSPF instead of IS-IS, since I have more knowledge with OSPF then IS-IS.

From LEAF-1 ping the multicast address 232.0.0.1 do not reply anything, whch mean that something about multicast may not work as suppose to be.

 

From LEAF-1 here the SHOW IP MROUTE and SH IP PIM NEIGHBOR command :

 

LEAF-1# sh ip mroute 
IP Multicast Routing Table for VRF "default"

(*, 232.0.0.0/24), uptime: 3d00h, pim ip 
  Incoming interface: Null, RPF nbr: 0.0.0.0
  Outgoing interface list: (count: 0)


(*, 232.0.0.1/32), uptime: 3d00h, nve pim ip 
  Incoming interface: Ethernet1/1, RPF nbr: 10.0.0.1
  Outgoing interface list: (count: 1)
    nve1, uptime: 3d00h, nve


(10.0.2.1/32, 232.0.0.1/32), uptime: 3d00h, nve mrib pim ip 
  Incoming interface: loopback1, RPF nbr: 10.0.2.1
  Outgoing interface list: (count: 0)

LEAF-1# SH IP PIM NEI
PIM Neighbor Status for VRF "default"
Neighbor        Interface            Uptime    Expires   DR       Bidir-  BFD    ECMP Redirect
                                                         Priority Capable State     Capable
10.0.0.1        Ethernet1/1          06:22:38  00:01:39  1        yes     n/a     no
10.0.0.2        Ethernet1/2          06:06:23  00:01:17  1        yes     n/a     no
LEAF-1# 

From SPINE-1

SPINE-1# sh ip mrout 
IP Multicast Routing Table for VRF "default"

(*, 232.0.0.0/24), uptime: 09:42:29, pim ip 
  Incoming interface: Null, RPF nbr: 0.0.0.0
  Outgoing interface list: (count: 0)


SPINE-1# 
SPINE-1# SH IP PIM NEI
PIM Neighbor Status for VRF "default"
Neighbor        Interface            Uptime    Expires   DR       Bidir-  BFD    ECMP Redirect
                                                         Priority Capable State     Capable
10.0.1.1        Ethernet1/1          06:22:11  00:01:16  1        yes     n/a     no
10.0.1.2        Ethernet1/2          06:22:12  00:01:17  1        yes     n/a     no
10.0.1.3        Ethernet1/3          06:22:11  00:01:35  1        yes     n/a     no
10.0.1.4        Ethernet1/4          06:22:11  00:01:41  1        yes     n/a     no
10.0.1.5        Ethernet1/5          06:22:11  00:01:27  1        yes     n/a     no
10.0.1.6        Ethernet1/6          06:22:12  00:01:32  1        yes     n/a     no

 

Base on the SPINE-1 output, I understand that the multicast traffic do not reach SPINE-1 switch making my topology not working as expected.

 

My lab setup is under Cisco Modeling Lab vers 2.2.6

all my switch are Nexus 9300 NX-OS 9.3.6

 

I attached in text file a PDF of the lab diagram, the YAML file could be import in CML, and in text file all switches configuration.

 

1 Accepted Solution

Accepted Solutions

christianpho
Level 1
Level 1

Hi, 

 

I don't if my issue was also related to multicast, but is was also missing a lot of configuration not related to multicast to make this configuration to work.  So since I add much configuration command and find that my issue was related to route-target, I'm going to mark this as case a case closed.  and going to start a new tread....

 

Thank you.

View solution in original post

1 Reply 1

christianpho
Level 1
Level 1

Hi, 

 

I don't if my issue was also related to multicast, but is was also missing a lot of configuration not related to multicast to make this configuration to work.  So since I add much configuration command and find that my issue was related to route-target, I'm going to mark this as case a case closed.  and going to start a new tread....

 

Thank you.

Review Cisco Networking for a $25 gift card