<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Route leaking not working in Data Center (SLX)</title>
    <link>https://community.extremenetworks.com/t5/data-center-slx/route-leaking-not-working/m-p/96174#M448</link>
    <description>&lt;P&gt;I want to create communication btw vrf1 to vrf2 using the route leaking feature.&lt;/P&gt;&lt;P&gt;vrf1:&amp;nbsp;&lt;SPAN&gt;&lt;SPAN class=""&gt;10.55.51.12/32&amp;nbsp; -&amp;nbsp; destination reachable through default route -next hop&amp;nbsp;192.168.246.253-&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;vrf2:&amp;nbsp;10.50.18.65/27&amp;nbsp; - ve 1101&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Using below commands, communication does not work as expected&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;vrf vrf1&lt;BR /&gt;address-family ipv4 unicast&lt;BR /&gt;ip route 10.50.18.64/27 next-hop-vrf vrf2 10.50.18.65&lt;/P&gt;&lt;P&gt;vrf vrf2&lt;BR /&gt;address-family ipv4 unicast&lt;BR /&gt;ip route 10.55.51.12/32 next-hop-vrf vrf1 192.168.246.253&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm assuming next hops are correct, please let me know if somebody has faced a similar issue, or if I'm using an incorrect input for this route leaking.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 19 Jun 2023 18:45:06 GMT</pubDate>
    <dc:creator>lledidga</dc:creator>
    <dc:date>2023-06-19T18:45:06Z</dc:date>
    <item>
      <title>Route leaking not working</title>
      <link>https://community.extremenetworks.com/t5/data-center-slx/route-leaking-not-working/m-p/96174#M448</link>
      <description>&lt;P&gt;I want to create communication btw vrf1 to vrf2 using the route leaking feature.&lt;/P&gt;&lt;P&gt;vrf1:&amp;nbsp;&lt;SPAN&gt;&lt;SPAN class=""&gt;10.55.51.12/32&amp;nbsp; -&amp;nbsp; destination reachable through default route -next hop&amp;nbsp;192.168.246.253-&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;vrf2:&amp;nbsp;10.50.18.65/27&amp;nbsp; - ve 1101&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Using below commands, communication does not work as expected&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;vrf vrf1&lt;BR /&gt;address-family ipv4 unicast&lt;BR /&gt;ip route 10.50.18.64/27 next-hop-vrf vrf2 10.50.18.65&lt;/P&gt;&lt;P&gt;vrf vrf2&lt;BR /&gt;address-family ipv4 unicast&lt;BR /&gt;ip route 10.55.51.12/32 next-hop-vrf vrf1 192.168.246.253&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm assuming next hops are correct, please let me know if somebody has faced a similar issue, or if I'm using an incorrect input for this route leaking.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jun 2023 18:45:06 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-slx/route-leaking-not-working/m-p/96174#M448</guid>
      <dc:creator>lledidga</dc:creator>
      <dc:date>2023-06-19T18:45:06Z</dc:date>
    </item>
    <item>
      <title>Re: Route leaking not working</title>
      <link>https://community.extremenetworks.com/t5/data-center-slx/route-leaking-not-working/m-p/96181#M449</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Thank you for your question.&amp;nbsp; Did you confirm that the source interfaces are UP/UP?&amp;nbsp; If so, we would want to see more of your config.&lt;/P&gt;&lt;P&gt;In my lab I tested with an SLX 9250 running SLX-OS 20.5.1:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;POD1-Leaf-1# show chassis
Chassis Name: SLX9250-32C

POD1-Leaf-1# show version
SLX-OS Operating System Version: 20.5.1&lt;/LI-CODE&gt;&lt;P&gt;First I created 2 VRF named green and blue:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;POD1-Leaf-1# conf
Entering configuration mode terminal
POD1-Leaf-1(config)# vrf green
POD1-Leaf-1(config-vrf-green)# address-family ipv4 uni
POD1-Leaf-1(config-vrf-green-ipv4-unicast)# vrf blue
POD1-Leaf-1(config-vrf-blue)# address-family ipv4 uni&lt;/LI-CODE&gt;&lt;P&gt;I then picked two random free interfaces and configured them for VRF forwarding:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;POD1-Leaf-1(config-vrf-blue-ipv4-unicast)# int e 0/9
POD1-Leaf-1(conf-if-eth-0/9)# vrf forwarding green
POD1-Leaf-1(conf-if-eth-0/9)# ip address 10.55.1.2/24
POD1-Leaf-1(conf-if-eth-0/9)# int e 0/10
POD1-Leaf-1(conf-if-eth-0/10)# vrf forwarding blue
POD1-Leaf-1(conf-if-eth-0/10)# ip address 10.50.1.2/24
POD1-Leaf-1(conf-if-eth-0/10)# end&lt;/LI-CODE&gt;&lt;P&gt;Next I configured the basic Static Route Leaking as described in the L3 Configuration Guide:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;POD1-Leaf-1(config)# vrf blue
POD1-Leaf-1(config-vrf-blue)# address-family ipv4 uni
POD1-Leaf-1(config-vrf-blue-ipv4-unicast)# ip route 10.55.2.0/24 next-hop-vrf green 10.55.1.1
POD1-Leaf-1(config-vrf-blue-ipv4-unicast)# vrf green
POD1-Leaf-1(config-vrf-green)# address-family ipv4 uni
POD1-Leaf-1(config-vrf-green-ipv4-unicast)# ip route 10.50.2.0/24 next-hop-vrf blue 10.50.1.1
POD1-Leaf-1(config-vrf-green-ipv4-unicast)# end
POD1-Leaf-1# &lt;/LI-CODE&gt;&lt;P&gt;However I see no routes were learned:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;POD1-Leaf-1# show ip route vrf green
Total number of IP routes: 0
POD1-Leaf-1# show ip route vrf blue
Total number of IP routes: 0&lt;/LI-CODE&gt;&lt;P&gt;I found that both ports were down, so I moved the config to two ports that were free and UP:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;POD1-Leaf-1# show int e 0/9
Ethernet 0/9 is up, line protocol is down (link protocol down)
POD1-Leaf-1# show int e 0/10
Ethernet 0/10 is up, line protocol is down (link protocol down)

Eth 0/15:1   connected (up)  --         25G      100G                                
Eth 0/15:2   connected (up)  --         25G      100G                                

POD1-Leaf-1# conf
Entering configuration mode terminal
POD1-Leaf-1(config)# int e 0/9
POD1-Leaf-1(conf-if-eth-0/9)# no vrf forwarding 
POD1-Leaf-1(conf-if-eth-0/9)# int e 0/10
POD1-Leaf-1(conf-if-eth-0/10)# no vrf forwarding 

POD1-Leaf-1(conf-if-eth-0/10)# int e 0/15:1
POD1-Leaf-1(conf-if-eth-0/15:1)# vrf forwarding green
POD1-Leaf-1(conf-if-eth-0/15:1)#  ip address 10.55.1.2/24
POD1-Leaf-1(conf-if-eth-0/15:1)#  no shutdown
POD1-Leaf-1(conf-if-eth-0/15:1)# int e 0/15:2           
POD1-Leaf-1(conf-if-eth-0/15:2)#  vrf forwarding blue
POD1-Leaf-1(conf-if-eth-0/15:2)#  ip address 10.50.1.2/24
POD1-Leaf-1(conf-if-eth-0/15:2)#  no shutdown
POD1-Leaf-1(conf-if-eth-0/15:2)# end&lt;/LI-CODE&gt;&lt;P&gt;Now I see routes leaking as expected as we see the route learned from %green in blue and vice versa:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;POD1-Leaf-1# show ip route vrf blue
IP Routing Table for VRF "blue"
Total number of IP routes: 3
'[x/y]' denotes [preference/metric]

10.50.1.0/24, attached 
     via DIRECT, Eth 0/15:2, [0/0], 0m7s, direct, tag 0
10.50.1.2/32, attached 
     via DIRECT, Eth 0/15:2, [0/0], 0m7s, local, tag 0
10.55.2.0/24,  
     via 10.55.1.1%green, Eth 0/15:1, [1/1], 0m18s, static, tag 0

POD1-Leaf-1# show ip route vrf green
IP Routing Table for VRF "green"
Total number of IP routes: 3
'[x/y]' denotes [preference/metric]

10.50.2.0/24,  
     via 10.50.1.1%blue, Eth 0/15:2, [1/1], 0m12s, static, tag 0
10.55.1.0/24, attached 
     via DIRECT, Eth 0/15:1, [0/0], 0m23s, direct, tag 0
10.55.1.2/32, attached 
     via DIRECT, Eth 0/15:1, [0/0], 0m23s, local, tag 0
POD1-Leaf-1# &lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;Thanks,&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2023 13:40:26 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-slx/route-leaking-not-working/m-p/96181#M449</guid>
      <dc:creator>Michael_Morey</dc:creator>
      <dc:date>2023-06-20T13:40:26Z</dc:date>
    </item>
  </channel>
</rss>

