Showing results for 
Search instead for 
Did you mean: 

SDA L2 Flooding Limitations

Hi together,

has anyone an idea about the limitations with L2 flooding ?

Our customer has a separate infrastructure with lots of L2 broacast domains (~100). This construct ist used for various sensors, terminals, ip-cams, etc...

and some devices which may not speak IP. So my question is, does any paper or recommendations/limitations exist for using the L2 Flooding Feature in SDA with DNA-C.

Cisco Employee


There is a section for L2 Flood at .

Ideally, we want all DHCP-capable devices to move to new subnets if possible and then route between SDA and non-SDA during migration. However, that is is not always possible, so we support L2 Selective Flooding ("selective" because it is on a per IP Pool basis and selected when an IP Pool is added to a VN) and L2 Handoff on a border. L2 Selective Flooding requires multicast to be enabled in the underlay , and this can be done either by LAN Automation or manually.

There are a few important considerations with L2 handoffs:

1. An L2 handoff for a subnet can exist on only one Border at a time. For resiliency, most customers would use a StackWise Virtual pair of Catalyst 9500 High Performance switches, a chassis based system with multiple supervisors or a stack of Catalyst 9300s ( if scale is OK ) to host an L2 handoff. 

2. The scale of the Border hosting the L2 handoff differs by platform, and so the number of clients needing the L2 service both inside and outside the fabric will need to be known. If a single Border is not sufficient, additional Borders can be added to host L2 handoffs.

Scott Hodgdon

Senior Technical Marketing Engineer

Enterprise Networking and Cloud Group


Hi Scott,

thanks for the information, so far.

But is there a practical limitation of clients within the L2 Flooding VN and is there a practicle number of max. VN´s to be useed for that ?

In our case we speak about ~ actual 100 L2 domains.

Content for Community-Ad