we recently purchased a UCS setup to run our EXS hosts on. we have two 6248 Fabric switches and one 5108 chassis. I have setup for the most part everything I would think I needed to get a VM Host up and running for testing. Created IP pool for KVM connection, which works and I can gain access to the ESX console from this IP. I created all the VLAN's and setup Port-Channels to my core 6506's. here is a run down of the physical devices and software running on them.
dual 6506 (VSS) - w/ VS-SUP2T-10G, x6816-10GE line card (s2t54-adventerprisek9-mz.SPA.151-1.SY1.bin)
UCS running latets running 2.1(2a)
I setup ports 13/14 on the 6200's to be a port channel to one of the 6500's
6500 Interface setup (ESX host mgmt IP is on vlan 210)
Issue is I cannot ping/connect the ESX host that is sitting on the blade. All links are green and they show no errors. 6200's are in FC Switch mode because we are directily connecting it to a VNX SAN. Network Adapter shows a status of connected from the ESX host on the correct vnic. any help would be greatly appreciated.
Hi Padramas - the vnic is set to the correct vlan and that vlan is set to native. I checked the mac address table on the FI and vlan 210 shows up with the correct mac address of the ESX host. the same mac address is not showing up in the table on the 6500's. I tried turning on STP on the 6500's but it just shows them as edge now since they are trunk ports.
I recreated the port channels and the interfaces just to clean everything up. I now see the mac address on both the FI and the 6500's. I still connot ping the devices though. From the FI local-mgmt interface I can ping the default gateway network for VLAN 210, but not the ESX. Same thing from the 6500's as well as the ESX hosts them selves. oh, and I built another ESX host and put its mgmt nic on the same vlan, they cannot ping eachother. very odd.....
to me it looks like the vlan 210 is configured as native vlan on the Fabric interconnects (untagged), while on the 6500 Trunks vlan 210 is tagged and the default vlan1 is native. Could that be the issue ? How is the vlan 210 configured on the management vnic for the ESXi host on the UCS (tagged or untagged) and how is the configuration inside the ESXi OS for the Management VMkernel ?
I tried removing the vlan setting on the ESX and only having it set as native on the UCS but it still wouldnt work.
this seems odd, but I switched everything over to the mgmt network and it started working. not sure if that is a must for hosts on the UCS. I was then able to create a test server on the ESX and give it an IP on the 210 network and it works just fine.
not going to worry about this, it is not like we will have over 200 esx hosts. we only have 6 right now.
Why do you need native HA: The native HA feature allows two Cisco DCNM
appliances to run as active and standby applications, with their
embedded databases synchronized in real time. Therefore, when the active
DCNM is not functioning, the standby DCNM will...
This document will provide screenshots to outline the steps to setup
TACACS+ configuration to ACI and also the configuration required on
Cisco ACS server. Please find the official Cisco guide for configuring
TACACS+ Authentication to ACI:
Is it supported or NOT supported? It's a frequently asked question.
Before APIC, release 2.3(1f), transit routing was not supported within a
single L3Out profile. In APIC, release 2.3(1f) and later, you can
configure transit routing with a single L3Out pr...