Відео

Hi, sorry, it is difficult to compare ACI and VXLAN EVPN, technically these are two different approaches, however I gave here some personal thoughts about why you might prefer a standalone solution with NDFC or an SDN based solution with ACI.

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.

send me an email unicast, I will be able to share the slides in a pdf format

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)

I can certainly demo this use-case, but there are a couple of options. Do you mean extended L3 connectivity between your VXLAN EVPN and your Classic LAN (very similar to this video + enhanced Classic LAN) or L2 and L3 extensions between VXLAN EVPN (very similar to Multi-site, you will need to add a pair of BGW in the Classic LAN fabric)

it was to stop my dog from barking, :) but you 're right, all other video's ua-cam.com/play/PLQWS63Deewj7xHuqDmXxajcv-CXgbQhJl.html 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

having one forwarding link and one backup link toward the vPC pair controlled by STP, yes, as long as the STP BPDUs are kept in the same logical device (same vPC domain)

@@ciscodatacenternetworkmana6968 thanks man!

Wow ! Thank you David for notice. I'm sorry for that, it sounds like something has broken somewhere. Let me upload again the Module 2 Section 4 - They should come online in a couple of hours. Let me know when you got them.

Ok Module 2 Section 4 is is back

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)

Hi Matt, This function of interface grouping is above all used to simplified the overlay network attachment highly repetitive in a single click or for example you onboard a new pair of leaf nodes, then you can move the selected interfaces on a specific group and corresponding overlay networks will be automatically attach to the new switches/interfaces. For your concern, I think there are several options. Either you duplicate the interface policy of interest, you modify it to reflect your requirements, and use your custom interface policy template afterward. Another option is to use for example Postman and create a loop with a CSV file to push the desired configuration to all port. And I think the easiest way is to use Ansible collection or Terraform provider.

Forgot to mention that you can see the interface grouping for NDFC 12 in the NDFC 12 short overview. I am planning to post a video dedicated on Interface grouping with NDFC 12 in a couple of weeks. thank you

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. ua-cam.com/play/PLQWS63Deewj7xHuqDmXxajcv-CXgbQhJl.html

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. ua-cam.com/play/PLQWS63Deewj7xHuqDmXxajcv-CXgbQhJl.html

Have you tried dcloud.cisco.com ? dcloud2-lon.cisco.com/content/catalogue?search=NDFC&screenCommand=openSearchScreen

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

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