![]() ![]() I performed the clear endpoints leaf command and no change. Looking in Operations > EP tracker I cannot find the end point by IP, but I can see it via its mac address. We can see them appear when initially brought online in vcenter in Virtual Networking > Vmm Domains > Vmware > VDS >DVS> portgroups > correct port group. We have 2 other port groups (different vrfs/tenants for those BDs/APs/uEPGs) and a few other servers on each of those (most on different hosts) and they are behaving the exact same. ![]() ![]() Cannot ping each other, cannot ping the Gateway of the subnet. Same Datacenter/Same cluster/Same host/Same Distributed Network Port/Same subnet defined. I can confirm that the VMs are on the same host in VCenter. ![]() I must write a full explanation one day!īTW - the link to BRKACI-2645 in your original post has a stray underscore character at the end, ( ./BRKACI-2645.pdf _) so the link needs editing. check the Leaf Profile is connected to the correct Interface Profile, and the Interface Profile has the right Interface Selector and the Interface Selector is associated with the correct Interface Policy Group and that the Interface Policy Group is connected to the correct AAEP and the AAEP is connected to the right VMM Domain and that the VMM Domain is connected to the right VLAN Pool and the VLAN Pool has the correct VLANs - all this can be done by following links under Fabric > Access Policies. What I'd do next if you still have a problem is follow the access policy chain - ie. Mind you, if this is really the problem, it may have magically cleared itself by the time you read this.Īnd one more tip - to remove LLDP from the equation, when you associate the EPG with the VMM, make sure you choose pre-provision as the Resolution Immediacy There is a similar command for clearing endpoints from the BD too. Given that this is a test environment, can you try issuing the following command on the APIC? apic1# clear endpoints leaf tenant vrf My thinking is that somehow there is an old association of a MAC address to IP address in ACI. Your statement " cannot ping each other" does not make it clear if the VMs that can't ping each other are on the same hostor not. " I'd also try to put another VM on the same host, same port group and see if that can ping the VM locally." Hi bit where you say " two VMs on the same port group cannot ping each other or their gateway/BD IP", along with " but showing the old IP address" worries me.Īnd I'd like to see the result of Burns' suggestion: Feeling more like this is not a problem in the Fabric. Not clear what I can do from the ACI side to prove this a VCenter issue. I know there are some considerations that have to be done on the host side. The VM host admins have told me they have gone through all the appropriate checks to ensure LLDP configured as needed for this to function. The VMs now show the correct, new IP but same behavior in the learning source and cannot ping each other or gateway. I deleted the VMM association from the App Profile, deleted the Port Group in VCenter and then re-added it all back in. Definitely unexpected behavior compared to the other Fabric we have were all of this integration is instantaneous. I have restarted the VM and refreshed everything I can think of. The other VM that I just moved to it in VCenter for this VM-to-VM testing is listed in the port group but showing the old IP address. Something of note - one of the VMs has been in this particular port group for a day or so, its showing the correct IP. I can confirm that two VMs on the same port group cannot ping each other or their gateway/BD IP. We do directly connect to the VC interfaces on the chassis via leaf. I can only assume this is something simple that we have missed. We have reset all ports, have moved to secondary VC, have rebooted every APIC, SPINE and LEAF in the fabric. We have gone through ever single configuration step we can compare against on our fully functional fabric. No faults showing and we have confirmed Port Group Mapping.Īny suggested solutions for this? We have opened a TAC but nothing back from them as of yet. I see this behavior and troubleshooting tips on page 44. Looking through the VMware vDS Integration troubleshooting documentation : When looking at the App Profile > EPG > Operational > Client End-Points the VMs do show there but they do not show their IP address, they only show "vmm" under the Learning Source and do not show the interface they are being learned on. I can see the VMs under the port groups in the VMM VDS Port Groups. VCenter integration setup is very standard and everything was working up to the point of actually deploying VMs. Its nearly one-for-one clone of another datacenter. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |