cancel
Showing results for 
Search instead for 
Did you mean: 

Add fabric extend to current mesh

Add fabric extend to current mesh

bfaltys
Contributor II

This will build on something I posted about a while back, but the situation is this:

-we have a fabric built across the city with our own owned fiber

-we are getting additional, redundant links from an ISP

-we want to use the ISP links to add to our fabric

-we have 2 test sites up. One is only connected to the ISP and the fabric extend is working. the other site is connected to the ISP and our original fabric. In the second case, the link over the ISP shows “INIT” for the IS-IS adjacency. Is it possible to have full adjacency over the ISP and our original fabric at the same time?

-For the fabric extend, I am using brouter ports and I have loopback IP as tunnel source & destination. Both of these are running OSPF so that I don’t have to build a bunch of static routes going forward. I also added OSPF redistribution into IS-IS.

 

I can add configs/diagrams, but wanted to throw out some facts and the question.

1 ACCEPTED SOLUTION

bfaltys
Contributor II

I believe I have figured this out. I had the same OSPF router-id configured on the 2 edge sites. That makes sense then...Once I fixed that, both isis adjacencies came up and have stayed up.

View solution in original post

7 REPLIES 7

Roger_Lapuh
Extreme Employee

thanks for letting us know! 

Roger

bfaltys
Contributor II

I believe I have figured this out. I had the same OSPF router-id configured on the 2 edge sites. That makes sense then...Once I fixed that, both isis adjacencies came up and have stayed up.

bfaltys
Contributor II

Looking back at some notes from when I labbed this up and I used brouter ports with 2 subnets and different VLANs on the brouter ports….both peers came up in that scenario.

 

Also, when I run “show isis logical-interface” it shows the 2 tunnel interfaces, but lists the same physical port and vlan even though they are configured differently.

3c90091c5d0243f2a10497efe50d67b8_ce4a9dc7-b7da-4b60-8a8f-b637197442a6.png
3c90091c5d0243f2a10497efe50d67b8_be1728ed-74eb-4dd6-9c71-17d769668ab4.png

So the down site should be port 1/48 vlan 2802. That brouter is 172.31.255.3/24. I can’t figure out what it is looking out the wrong port.

bfaltys
Contributor II

That makes sense. What I ran into on Friday is that with 2 test sites, only 1 of the 2 will be up. They are on different brouter ports in the same VRF (not the GRT). Each link is a different 172.x.x.x/24 subnet with routes to the peer’s loopback. The VLAN on the brouter ports is different for each link. Feels so close to being done!

 

One example given to me uses VLAN interfaces instead of brouter ports, but to me that should not make a big difference as long as the devices have routes to the tunnel destination.

GTM-P2G8KFN