This video demonstrates how to deploy the Cisco Application Virtual Switch (AVS) on the ACI fabric. UCS-B series blades are used to run the ESX hosts in this vdeo.
I have followed this video several times and was unable to ping the subnet address assign to the BD.
The issue is with the IGMP snooping policy. You show how to create the policy but you forget to mention that it needs to be assigned to the default bridge domain in infra.
Good catch. This is true for deploying AVS in VXLAN mode, as all communication is done over the Infrastructure VLAN. Because all communication will happen over the Infrastructure VLAN, when configuring DHCP relay policy (so that VTEPs can obtain an IP address) and when enabling IGMP Querier, the configuration is done in the Infrastructure tenant.
You should enable IGMP querier on the infra tenant bridge domain subnet through the Cisco APIC. See the instructions in the section "Configuring IGMP Querier."
Step 4For traffic issues involving VXLAN encapsulation, ensure that the IGMP querier and IGMP snooping policy are configured in the APIC GUI under tenant infra and infra bridge domain.
Regarding the requirement for the IGMP Policy. If we enable IGMP snooping on UCS or any other bladeswitch in between the leaf and ESX, we have to configure IGMP querier on the ACI side (leaf).
If we disable IGMP snooping on UCS or other intermediate bladeswitches, then IGMP policy is not needed since the bladeswitch will flood the multicast traffic on all the relevant ports.
After upgrading to 1.0(2m) I have lost connectivity to all VM’s that use the AVS switch (in VXLAN mode).
Having checked your documentation I noticed that the “Querier IP” subnet I had created in version 1.0(1j) in the default bridge domain in the infra tenant had disappeared. I have tried to recreate it but I get a 400 denied error.
I'll need to update this video. There's no longer the need to create a "dummy" BD subnet just to enable querier. You can enable querier on the default BD subnet instead.
I'll see if this change was properly tested. Appreciate you bringing this up.
Another change to be aware of is you no longer need to explictly add the APIC as a DHCP provider (for the DHCP relay policy). Each APIC will automatically function as a dhcp server for any requests sent over the Infra VLAN.
I have WASS now running between my 4431 on 16.6.X and 4351 with no issue.Another division of the company has a 4431 running 15.4(3)S6a, Is it possible to make a connection this 4431 running 15.4.x code? Upgrade of the 15.4 code to 16.6.x isn't ...
view more
I am using an N9K as an edge router, peering with my ISP's BGP speaker:edge-rtr# sh ip route summaryIP Route Table for VRF "default"Total number of routes: 28931Total number of paths: 28932[...] edge-rtr# sh ip route bgp summaryIP Route Table for VRF...
view more
Hi all, i'm trying to follow this guide to deploy FCoE on our network FCoE Configuration Between VIC Adapter on UCS Rack Server and Nexus 5500 Switch - Cisco I am ok up until the vfc interfaces on N5k-A and N5k-B in our case we have only one sin...
view more
Hi all This my environment: dc1: N7K1-2(VPC+peer gw) ------ VPLS (l2 stretching) + MPLS vpn --------dc2: N9K1-2 (VPC+peer gw) hsrp primary ---------------------------------------------------------------------hsrp secondary We will mig...
view more
Hi Folks,could anybody explain me the difference between the API Calls with the "node" keyword in between?So when do i need thehttps://apic-ip-address/api/node/mo/.xmlvs.https://apic-ip-address/api/mo/uni.xmlbest Regards