cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1181
Views
0
Helpful
3
Replies

L3 border handoff SDA

Pascal Lacroix
Level 1
Level 1

we are building an SDA network with two Cisco9500 Border Nodes that are connected by BGP to a fusion firewall cluster (Fortigate). When DNAC configures the L3 border handoff it uses a /30 subnet between the Border Node and the external device, in my case the Fortigate. There is a L2 trunk between the border nodes and from each border node there is a L2 trunk towards the Fortigate. So i want to use the same vlan on both Border nodes for the connection with the Fortigate.

Does anyone know if you can you use a /29 subnet (instead of the /30) for the L3 Border handoff (BGP) communication?  

 

kind regards,

Pascal

1 Accepted Solution

Accepted Solutions

jalejand
Cisco Employee
Cisco Employee

L3 Handoff automation will only include /30 subnets for peering configured from the L3 handoff IP Pool, in 2.3.4.x, manual L3 handoff config (done on the UI) will allow custom subnets.

Another way is to manually create the SVIs+BGP peerings manually with a /29.

View solution in original post

3 Replies 3

jalejand
Cisco Employee
Cisco Employee

L3 Handoff automation will only include /30 subnets for peering configured from the L3 handoff IP Pool, in 2.3.4.x, manual L3 handoff config (done on the UI) will allow custom subnets.

Another way is to manually create the SVIs+BGP peerings manually with a /29.

thanks for your answer. 

We are now running 2.3.3.4. Do you know when 2.3.4.x will be released?

So in 2.3.4.x is /31 also allowed (like in the underlay) and when we have option to manually define VLAN Name and ID, can we re-use the same ID (e.g. 3001) in different fabrics (completely different borders, peers, etc.)?

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: