FI : 6248
Chassis : 5108
Blades : B200 M2 x 2
Uplinks : 5548UP
I'm setting up a pretty standard UCS deployment and have VPC uplinks from the 6248 fab interconnects to Nexus 5548s. The uplinks appear to be working correctly as I can manage UCS without any issues and can KVM to each blade. I've set up the mgmt ext pool and each of the blades gets an address correctly.
I initially setup a Xenserver blade and was able to connect to it on a server vlan that I created. However, since then I have reloaded the server and can not get it to work again no matter what I try. I've also tried load a Windows 2008 x64 server and while I am able to load the OS and configure the NICs within Windows (after installing the B200 drivers), there is no network connectivity .. it's as if the VLAN tagged traffic is not being forwarded upstream.
I have verified that all of our vlans are being passed on the uplinks between the FIs and the Nexus 5548s and I know it worked at one point so this has me puzzled.
I must have since misconfigured something but I can not for the life of me figure out what that was. I have recreated the VLANs, Service Templates, Services Profiles, etc. Each time I reload a blade, whether it be with Xenserver or with standard windows, I am able to see and configure the vNICS but I can pass no traffic. I can't do a ping from within the 6248s either since that cmd is not support, nor can I see any way of troubleshooting the traffic being passed.
Can someone please pass along some troubleshooting tips and/or places I can look to troubleshoot where the traffic is dying? I'm pulling my hair out!!
Just to clarify,
Native VLAN and Default VLAN are two different things. Native simply refers to the VLAN on a trunked 802.1q link that will not be appended a VLAN tag. Default VLAN is the "automatically assigned" VLAN to all vNIC interfaces. By default the "default vlan" is vlan 1, but this can be changed.
When creating a Service Profile (or Template for that matter) you can use the Simple, or Expert wizard. The Simple wizard assumes each vNIC will operate as an "access port" by only being assigned to one vlan. In expert mode you can select either the port to operate as an Access Port (single VLAN) or Trunk (multiple VLANs). It's only with the Trunk vNIC configuration where you can select the "Native" VLAN radio button.
So let's say you have a Windows host that needs to be assigned to VLAN 10.
You could create a simple vNIC that acccess VLAN 10 only, or you could create a Trunk Interface, but set VLAN 10 as the native. Either method will return the same result.
For OSes like ESX & Hyper-V you will indeed want Trunking and therefore allowing multiple VLANs.
Now to top it all off, though we present what looks to be "Access" and "Trunk" ports, there's actually no access ports. What UCS does when you select a vNIC to be an Access port is just make a Trunk interface with the sole VLAN as the native.
You can see this from NXOS if you look at "show int trunk".