it was to stop my dog from barking, :) but you 're right, all other video's kzfaq.info/sun/PLQWS63Deewj7xHuqDmXxajcv-CXgbQhJl come without music in the background. Nonetheless, many new features came out since I published this video from a beta version of NDFC 12.0, thus I need to renew this video, and I will not add the music for sure. Thank you for your comment

Thank you A.J. for the feedback. It is certainly worth to cover this topic in a next video, I agree. In the meantime, to make it simple here, let me give you my own high level answer. For VXLAN EVPN Multi-site interconnection purposes, the function of the Border Gateway (BGW) doesn’t need any Classic Layer 2 connectivity, Layer 3 peering between BGW’s is enough. As a result, the preference will be to configure Anycast BGW (BGP). And you can currently deploy up to 6 Anycast BGW’s per site (this is not a SW nor a HW limitation per se, but more a “qualified & verified” deployment). However, I see two use-cases where you may need to attach network elements at Layer 2 toward the BGW: - One is to interconnect a legacy DC with a VXLAN EVPN fabric (or even legacy DC to legacy DC), for that you need to deploy a pair of vPC BGW’s in the legacy DC attaching the Classic Ethernet from the legacy DC to extend the L2 segments between the DC and the VXLAN EVPN Fabric (Anycast BGW’s or vPC BGW’s) - Second is to single- or dual-attach Endpoints at L2 (ie. Hosts) directly at the BGW devices, thus, you need to deploy a pair of vPC BGW in that case too. Otherwise, if you need to attach L3 Endpoints to your BGW’s (External Router, FW..) then, Anycast BGW is the best approach.

Nice discussion

Sorry for the late reply, you can deploy either LAN controller or SAN controller or IPFM controller from the same OVA or ISO file, but when you open the NDFC service for the 1st time, you are asked to select either SAN or LAN mode. The reason is that most of enterprises want separate services between SAN and LAN. However, we are planing full co-existence of IPFM and VXLAN via the same NDFC instance and run together in a next release (not yet committed)

Hello, In term of device integration NDFC 12 supports IOS-XE SD-WAN (ASR1k, ISR 1100). In term of network integration NDFC 12 supports automatique VRF-Lite, MPLS LDP, SR MPLS hand-off deployment.

yes, it is recorded, will post it soon

Hi, sorry for the delay, even with ND 2.2(1h) any version of NDFC (12.0 12.1.3b ) you should be able to add a new policy to a group of switches from the Fabric overview menu / Service tab. If you wish to customise your own policy, from the main menu, select the Operations tab > Template. When done, you will be able to add your custom policy via the Service tab mentioned above.

Got it Eric, thank you for the feedback - I'm creating a more detailed series of the essentials of NDFC 12. I didn't add the musique. kzfaq.info/sun/PLQWS63Deewj7xHuqDmXxajcv-CXgbQhJl

Thank you Mohammed for the comment - Actually since NDFC 12.1, the SVI template with HSRP parameters has been embedded with NDFC (menu create new interface)

Got it Hajira, thank you for the feedback. I'm currently creating a more detailed series of the essentials of NDFC 12 with 6 modules and a series of sections. kzfaq.info/sun/PLQWS63Deewj7xHuqDmXxajcv-CXgbQhJl