Solved: encap-flood seems not working

Hongjun Ma · ‎05-19-2016

I couldn't get encap-flood working as I understood.

I have one BD with external GW so I enabled all flood options under BD but I want to contain flood behavior per encapsulation-vlan instead of BD. I set the option to encap-flood but from sniffer trace, I still see my OSPF and ARP multicast/broadcast packets being flooded from one EPG into another EPG.

Any idea why I'm seeing this behavior?

Thanks

Hongjun

Joseph Ristaino · ‎05-23-2016

There is currently one bug open to track ARP/RARP packets that are not being flooded in only the encapsulation, but rather every encap in the BD:

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuz66604/?reffering_site=dumpcr

This may be your issue. We know for certain that unknown unicast packets are flooded in the encap but there are other multidestination frames that are currently not abiding by the correct behavior.

You might want to open a TAC case to verify.

View solution in original post

Hongjun Ma · ‎05-23-2016

any suggestions?

Joseph Ristaino · ‎05-23-2016

There is currently one bug open to track ARP/RARP packets that are not being flooded in only the encapsulation, but rather every encap in the BD:

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuz66604/?reffering_site=dumpcr

This may be your issue. We know for certain that unknown unicast packets are flooded in the encap but there are other multidestination frames that are currently not abiding by the correct behavior.

You might want to open a TAC case to verify.

Hongjun Ma · ‎05-24-2016

Thank you very much Joseph!