- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2016 07:08 AM - edited 03-01-2019 05:06 AM
Solved! Go to Solution.
- Labels:
-
Cisco ACI
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2016 07:31 AM
Hi Donato,
That is a classic ESX issue I've run into in almost every ACI deployment.
Typically I will start off with one interface connected to the fabric and configured as an Access 802.1P on a given vlan in a Static Path Binding to the relevant EPG. I some cases I actually have an "ESX_Provisioning" EPG. That gets you access to the host via one interface on one vlan. I suggest the vlan approach because typically you will be trunking many vlans to your host and that just gets things started. If you will ultimately need a port channel to the host that lets you get to the host, allow vCenter access, build a vDS if that is what your design calls for and then you can bring up the other interface in the port channel, make sure that works and you still have access, and then reconfigure the first interface as part of the port channel. I believe there is a procedure put together by Tomas or Robert in this community that is quite good (as are all their procedures!) and has some clear examples. I'll see if I can dig it up.
Claudia
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2016 07:31 AM
Hi Donato,
That is a classic ESX issue I've run into in almost every ACI deployment.
Typically I will start off with one interface connected to the fabric and configured as an Access 802.1P on a given vlan in a Static Path Binding to the relevant EPG. I some cases I actually have an "ESX_Provisioning" EPG. That gets you access to the host via one interface on one vlan. I suggest the vlan approach because typically you will be trunking many vlans to your host and that just gets things started. If you will ultimately need a port channel to the host that lets you get to the host, allow vCenter access, build a vDS if that is what your design calls for and then you can bring up the other interface in the port channel, make sure that works and you still have access, and then reconfigure the first interface as part of the port channel. I believe there is a procedure put together by Tomas or Robert in this community that is quite good (as are all their procedures!) and has some clear examples. I'll see if I can dig it up.
Claudia
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2016 08:34 AM
Hello Luna,
thanks for your answer. I have just resolved the issue thanks to your help. I forgot to put the Static Path Binding and the domain association to the EPG.
Thanks a lot.
Donato
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2019 08:33 AM
Hi Claudia, thank you for your clarifications.
Could you please share with us the procedure for connecting the first ESXI host to the ACI.
a question, In this case, the host will be connected as a Bare metal if the vCenter isn't installed in the Esxi Host?
Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2019 07:47 PM
As per my knowledge you can connect that port using vpc as static
integration. According to your information you don't have vCenter at the
moment and you can't do the VMM integration.
This will may help for you.
https://youtu.be/R7kgyd7Hzv8
Thanks,
