Vlan tagging on VIC 1225

Hi Community
We are currently Setting up a c240 standalone Server, installed with a vic1225 (connected to a nexus 5500 vpc pair).
We have bare metal windows 2008 R2 os installed and enabled nic teaming ((802.3ad) with the enictool.
Now we want to setup vlan tagged nics in windows but there is no Way to do this....
Is this generally possible in windows 2008 Server ?
Thx in Advance for any tips.

Hello,
ENIC driver for W2K8 does not support VLAN dot 1q feature.
With W2K12, the native teaming driver from Windows tagging feature.
Alternate options are
1) Implement Adapter FEX
2) If you are planning to run Hyper-V on the host, then it can tag the VLANs.
3) Implement individual vNICs for each VLAN and configure active / active transmit load balancing on the host. Also, configure the switch ports as individual links allowing necessary vlans and do not them as port-channel / vPC
I recommend you to upgrade the firmware and drivers to latest version to eliminate known issues.
Padma

Similar Messages

C240 M3 with VIC 1225 VMware network issue

Just got my hands on a few C240 M3′s with the VIC 1225 adapter and began setting them up as a VMware 5.1 U1 cluster. I’ve configured 8 vNICs per host: 2 for Management, 2 for VMotion, 2 for iSCSI, and 2 for VM traffic. Each pair of vNICs has one pinned to uplink 0 and the other to uplink 1. vNICs are set to trunk mode in the VIC since I am tagging multiple VLANs from VMware. The hosts are physically connected to a stacked pair of Cisco 4500-X switches; physical uplink 0 to one switch, uplink 1 to the other switch. Switch ports are trunked to allow the VLANs we plan to use. Portfast is enabled. VMware vSwitches using Source Port ID for Load Balancing and the vNICs are active/active for Management and VM traffic. No port channel or Etherchannel is configured on the swtiches.
After creating a VM for vCenter and joining the hosts to it, I started migrating existing VMs from an old cluster and saw odd network behavior. It seems whenever a VM or vmkernel interface are on any vNIC pinned to the same physical uplink on the same host, they can’t talk to each other.
Example: VM1 and VM2 are on host 1. VM1′s network adapter is pinned to vNIC1 using VLAN 10 which uses physical uplink 0. VM2′s network adapter is pinned to vNIC2 using VLAN 10 which uses physical uplink 1. VM1 and VM2 can ping each other. If I move VM2′s network adapter to any vNIC that uses physical uplink 0, just like VM1, then VM1 and VM2 can no longer ping each other. Or if host 1′s management IP is pinned to vNIC 1 on physical uplink 0, any VM on host 1 using a vNIC also pinned to physical uplink 0 cannot ping the host.
Anyone have any ideas? Is something configured incorrectly on the switch? On the VIC?
Thanks!

Hello Michael,
I assume VIC is operating Classical Ethernet ( CE ) mode and VM1 and VM2 are in different vswitchs for the non-working scenario, ( where there vNICs used by vSwitch are pinned to physical uplink ) .
If this is the scenario, the frames have to be switched upstream switch and needs to be forwarded back on the same switch interface. Any IEEE standards based switch will not forward such traffic flow.
You might want to take advantage of Adapter-FEX or adapt changes to design to accommodate such traffic flows.
HTH
Padma

UCS C-Series VIC-1225 to Nexus 5000 setup

Hello,
I have two nexus 5000 setup with a vpc peer link. I also have an cisco c240 m3 server with a vic-1225 card that will be running esx 5.1. I also have some 4 2248 fabric extenders. I have been searching for some best practice information on how to best setup this equipment. The nexus equipment is already running, so its more about connecting the c240 and the vic-1225 to the nexus switches. I guess this is better to do rather than to connect to the fabric extenders in order to minmize hops?
All documention I have found involves setup/configuration etc with fabric interconnects which I dont have, and have been told that I do not need. Does anyone have any info on this? and can point me in the right direction to setup this correctly?
More specifically, how should I setup the vic-1225 card to the nexus? just create a regular vpc/port-channel to the nexuses? use lacp and set it to active?
Do I need to make any configuration changes on the vic card via the cimc on the c240 server to make this work?

Hello again, Im stuck
This is what I have done. I have created the vPC between my esx host and my two nexus 5000 switches, but it doesnt seem to come up:
S02# sh port-channel summary
Flags: D - Down        P - Up in port-channel (members)
        I - Individual H - Hot-standby (LACP only)
        s - Suspended   r - Module-removed
        S - Switched    R - Routed
        U - Up (port-channel)
        M - Not in use. Min-links not met
Group Port-       Type     Protocol Member Ports
      Channel
4     Po4(SD)     Eth      LACP      Eth1/9(D)
vPC info:
S02# sh vpc 4
vPC status
id     Port        Status Consistency Reason                     Active vlans
4      Po4         down* success     success                    -
vPC config:
interface port-channel4
switchport mode trunk
switchport trunk allowed vlan 20,27,30,50,100,500-501
spanning-tree port type edge trunk
vpc 4
interface Ethernet1/9
switchport mode trunk
switchport trunk allowed vlan 20,27,30,50,100,500-501
spanning-tree port type edge trunk
channel-group 4 mode active
Im unsure what I must configure on the cisco 240M3(esx host) side to make this work. I only have the two default interfaces(eth0 and eth1) on the vic-1225 installed in the esx host, and both have the vlan mode is set to TRUNK.
Any ideas on what I am missing?
Message was edited by: HDA

Cisco UCS C220 with VIC 1225

Hello,
We have Cisco UCS C220 M3 with VIC 1225 card installed. We connected only one 10G port of VIC 1225 to Nexus 5548UP switch. But I do not see this port on switch and in CIMI the status for this port shows Link Down. I wanted to to iSCSI boot from storage NetApp FAS2240 but since I don't see this port on my Nexus switch I am unable to do boot from NetApp. I tried both ports on VIC 1225 with same result. Please I need help in this matter. I know I am missing something very simple but can't figure this out.
Thanks,
Salman

Hi Kenny,
Here is the answers:
-What slot is this card installed in?
Mezzenine
-How many CPUs does the server have installed? (1 OR 2 CPUs can make the difference)
2x 2.90 GHz E5-2690/135W 8C/20MB Cache/DDR3 1600MHz
-Is the PCIe slot enabled in BIOS? << Let us know if you don't know how to check it from CIMC
I believe I did. Server>BIOS>BIOS advanced> PCIe (Let me know if this correct)
-Have you confirmed that the cable is good?
I have changed four cables. I am using SFP-H10GB-CU2M= Twinax cable.
-If the switch does not even see the port and CIMC says it is down, have you confirmed the switch port is properly configured?
CIMI says “Link Down” in VIC adapter General area. The switch interface config has only “switchport mode access” in default vlan 1.
-What is the firmware running on the server and the OS?
We upgraded the firmware with latest ucs-c220-huu-1.5.4-3.iso.
Let me share with you the complete BoM of the server:
UCSC-C220-M3S              1x UCS C220 M3 SFF w/o CPU mem HDD PCIe PSU w/ rail kit
UCS-CPU-E5-2690              2x 2.90 GHz E5-2690/135W 8C/20MB Cache/DDR3 1600MHz
UCS-MR-1X082RY-A    16x 8GB DDR3-1600-MHz RDIMM/PC3-12800/dual rank/1.35v
CAB-9K10A-UK              2x Power Cord 250VAC 10A BS1363 Plug (13 A fuse) UK
UCSC-PCIE-CSC-02    1x           Cisco VIC 1225 Dual Port 10Gb SFP+ CNA
UCSC-PCIE-QSFP              1x Qlogic QLE8242-CU Dual Port 10 GbE FCoE CNA
UCSC-HS-C220M3              2x Heat Sink for UCS C220 M3 Rack Server
UCSC-RAIL1              1x Rail Kit for C220 C22 C24 rack servers

Vlan tag issue with Nexus 4001 in IBM Blade Centre

Hi
I have a DC architecture with a pair of Nexus 7010's running 3 VDC's (Core/Aggregation/Enterprise). I have at the edge Nexus 5548's which connect to back to the Aggregation VDC. Also connecting back to the Aggregation VDC is an IBM Blade Chassis which has a Nexus 4001i in slots 7 and slot 9. These blade servers are running ESXi 4.0 and are mapped to the Nexus 4001 blade switch.
I had set up the Native VLAN as VLAN 999 which connects up to the ESXi host and I am trunking up multiple VLANS for the Virtual Machines.
The problem I have is that VM's in all VLANS except the ESXi host VLAN (VLAN 10) cannot see their default gateway, and I suspect that there is an issue with the VLAN tag going up to the ESXi host. I have read enough documentation to suggest that this is where the issue is.
My Nexus 4001 interface configuration is below
interface Ethernet1/1
switchport mode trunk
switchport trunk native vlan 999
switchport trunk allowed vlan 10,30,40-41,60-62,90,96,999
spanning-tree port type edge trunk
speed auto
The Aggregation VDC on the Nexus 7010 is the default gateway for all these VLANS.
I also noted that the Nexus 5000 and Nexus 7000 supports the command vlan dot1q tag native command yet the Nexus 4000 doesn't seem to support this. Any assistance would be useful
Thanks
Greg

Your configuration on the N4K looks correct. You shouldn't use vlan dot1q tag native commands on your N7Ks and N5Ks. Native VLAN tagging is really for QinQ (dot1q tunneling).
My only suggestion is check your configuration of the vSwitch in the ESXi host and the host network profile.
Regards,
jerry

Mesh Ethernet Bridging with VLAN Tagging Issue

Hi all.
I'm a little stuck with a 4400 7.0.220.0 + RAP 1550 + MAP 1260 Ethernet bridging issue. I'm using the VLAN tagging functionality and I'm finding that periodically a VLAN that I've tagged on the MAP will deregister from the backhaul and stop passing traffic. If I go into the Mesh tab on the MAP, select the wired interface, remove the VLAN from the list of tagged VLAN IDs and then add it right back to the list, its starts passing traffic again.
Has anyone else seen this? I can't find any relevant bugs.
Justin

Hi Saravanan,
It is one RAP and three MAPs. After a TAC call and 30 hours of monitoring, my VLANs have remained registered. I think the issue was mismatched VLANs to bridge groups an it looks like the mesh bridge may be stable for now. Here is what I was seeing on the RAP and MAPs when the VLANs were deregistering unexpectedly. Notice how VLANs 2 and 10 are mapped to opposite bridge groups on the RAP and MAP:
After I removed all the VLAN IDs from the Trunk configuration on the MAPs (through each AP's Mesh tab -- Ethernet Bridging config) and then rebuilt the VLAN IDs, I ran the same commands and now see this:
My very unscientific theory here is that the mismatching was causing consistency checks to fail, so the RAP was just tearing down the registrations after getting bogus or non- responses from the MAPs during the periodic VLAN registration maintenance checks (debug mesh ethernet registration).
If I have continued issues, I'll post back with updates.
Thanks for the response!
Justin

7600 second-dot1q & vlan tag manipulation

Hi,
Does anyone know what the hardware requirements are for using config such as "sencapsulation dot1Q 660 second-dot1q 1" or any of the "service instance" commands such as below to manipulate dot1q tags?
Im running 7600 with SIP-400, IOS 12.2(33)SRD and there are no such commands available at the cli. Suspect ES-20 is needed as a minimum but can't see this mentioned in any docs.
interface FastEthernet1/0.660
encapsulation dot1Q 660 second-dot1q 1
OR
interface GigabitEthernet3/0/0
description Sample Configs
service instance 1 ethernet
encapsulation untagged
rewrite ingress tag push dot1q 3 symmetric
xconnect 10.30.30.173 2 encapsulation mpls
service instance 10 ethernet
encapsulation dot1q 10
rewrite ingress tag pop 1 symmetric
bridge-domain 500 split-horizon
service instance 20 ethernet
encapsulation dot1q 20 second-dot1q 200
rewrite ingress tag pop 1 symmetric
bridge-domain 500 split-horizon
service instance 30 ethernet
encapsulation dot1q 20 second-dot1q any
rewrite ingress tag pop 1 symmetric
bridge-domain 500 split-horizon
I just need to pop the service vlan tag. At the moment I'm using a port per service to peel off the outer tag and this approach isn't going to scale.
Appreciate any advice on this.
Cheers
Kent.

Hi Jerry,
I believe - about to test it - that this only works with SPA-v2 interfaces. I was testing with a SPA-v1 interface previously. Is this your understanding? Docs are pretty light on with hardware requirements.
Show ver:
Cisco IOS Software, c7600s3223_rp Software (c7600s3223_rp-ADVIPSERVICES-M), Version 12.2(33)SRD, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2008 by Cisco Systems, Inc.
Compiled Thu 23-Oct-08 22:32 by prod_rel_team
ROM: System Bootstrap, Version 12.2(17r)SX3, RELEASE SOFTWARE (fc1)
pe1.lab uptime is 19 hours, 5 minutes
Uptime for this control processor is 19 hours, 5 minutes
System returned to ROM by power-on (SP by power-on)
System restarted at 17:09:22 EST Mon Jul 27 2009
System image file is "bootdisk:c7600s3223-advipservices-mz.122-33.SRD.bin"
Last reload type: Normal Reload
cisco CISCO7606-S (R7000) processor (revision 1.0) with 458752K/65536K bytes of memory.
Processor board ID FOX11310AY3
R7000 CPU at 300Mhz, Implementation 0x27, Rev 3.3, 256KB L2, 1024KB L3 Cache
Last reset from power-on
1 SIP-400 controller (4 GigabitEthernet).
10 Virtual Ethernet interfaces
125 Gigabit Ethernet interfaces
1915K bytes of non-volatile configuration memory.
65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102
Modules are now:
7600-SIP-400 and SPA-2X1GE-V2

C460 Rack Server with two VIC 1225 - UCSM vNIC placement policy

I am trying to integrate C460 having 2 VIC 1225 cards with UCSM. The objective is to have 2 ethernet interfaces assigned to each VIC , one per FI.
vNIC 1 on VIC 1 - FI A failover to FI B
vNIC 2 on VIC 1 - FI B failover to FI A
vNIC 3 on VIC 2 - FI A failover to FI B
vNIC 4 on VIC 2 - FI B failover to FI A
I have created a service profile with 4 vNICs and assigned to C460. When the UCSM is configured to use the system default for vNIC/vHBA placement policy, all 4 vNICs are assigned to one VIC. When trying to place them manually with 2 on vCon1 and 2 on vCon2, I am seeing insufficient resource error. Both the VIC are recognized and UCSM server tab shows both of them as adapters.
Could someone please let me know how to achieve it?
Thanks!

The C460 has an integrated BCM 57711 which would also be recognized by the system. What's most likely happening is that the VIC 1225s are on vCon1 and vCon3 and the BCM card is on vCon2, since FF is not supported on the Broadcom adapter this would cause the association to fail. Try placing the manual placement with vCon1 and vCon3 and see if this clears up the issue.
Steve McQuerry
UCS - Technical Marketing

Does Cisco7200VXR support feature Q-in-Q VLAN tag termination?

There is only 10000ESR platform support announced in feature guide and no information in Feature Navigator tool...
http://www.cisco.com/en/US/customer/products/sw/iosswrel/ps5207/products_feature_guide09186a00801f0f4a.html

Hi there,
Well.. it seems this feature has several names:
"Cisco IOS Software Releases 12.3 T - IEEE 802.1Q-in-Q VLAN Tag Termination"
http://www.cisco.com/en/US/products/sw/iosswrel/ps5207/products_feature_guide09186a00801f0f4a.html
"Cisco IOS Software Releases 12.0 S - Stacked VLAN Processing"
http://www.cisco.com/en/US/products/sw/iosswrel/ps1829/products_feature_guide09186a008021b9ee.html
But I can't find any reference to the 7200 having support for it... though many others has it.. mainly switches.. not too surprising.. :)
Did it help?

Vlan tag preservation span monitoring

Hi
I am spanning multiple vlans as source with the destination as a single ethernet port, though I am able to see the traffic from the VLANs, I am not able to see the VLAN tag in the packet which is a key requirement for me for monitoring.
Does anyone know why the VLAN tagging is stripped or how to preserve it in the monitor session?
Your help is much appreciated.
- Balaji

While I appreciate your response Najaf, we have been monitoring the SVIs on our current CAT6500 switches without any problems as we can "preserve" the vlan tags on the destination monitoring port.
However, we have found a way to see the VLAN tags on the monitoring destination port but we are still carrying out some tests to confirm our findings.
Will keep this thread updated.
-Balaji

Installing OVM X86 3.1.1 with Trunk VLAN tag for ovm management network

Hi Guys
Can anyone help with network config on the OVM server 3.1.1 basically we need to use vlan tags on trunk port... so i have a subnet from following *(Trunk Allowed VLAN XXX)* from which i need to allocate IP for the OVM server component so that the ovm manager can find the OVM server instance...
Can you use vlan tags, on trunk port with OVM server 3.1.1???
Thanks

Your right there as i later found out the engineers weren't selecting the vlan option when installing the vm server...

How to get vlan tag programe with mac book air

how to get vlan tag programe with mac book air,i'm using the usb ethernet adapter

For prompt help contact TATA.
For more on this: https://discussions.apple.com/thread/3680625?tstart=270

C240 M3 with VIC 1225 managed with UCSM: Failure Reason: not enough vNIC available

Hello,
I have problems in creating a working service profile with more than one vNIC/NIC.
I have a shiny new C240 server with a UCS VIC 1225 network card in PCI Slot 2. The server is directly connected to the two Fabric Interconnects (6248UP). 2 Direct attached cables with no FEX ("Direct Connect Mode Cluster Setup"). Firmware version is 2.2(1d). After setting the FI port to server role the server is flawlessly discovered. And shows up in the UCSM-GUI. And I see the VIC 1225 adapter that has 2 DCE Interfaces.
Now, when I try to create Service Profile for this server by choosing "Hardware Based Service Profile" (with Create default vNICs [X] and Create Default vHBA [ ]) I get the following error:
I am able to create a working profile with one vNIC in one fabric, but a soon as I try to add a second vNIC I get the error above.
What I expected was, that it is possible to map more than one vNIC/NIC into the server profile. At leat 2 NICs, one in each fabric.
I would be great if there is someone to bring some light in the darkness thats around me. Any hints or pointers to obvious documentation would be great.
Kind regards,

Hello,
thanks for your answer. And you are probably correct.
I can add aditional vnics to fabric A but not to fabric B. And even trying to add a single nic to Fabric B does not work.
I changed the ports for this server on the fabric interconnects and rebooted the FI but it did not help.
When I look at the General Tab of my server and then on Connection Details I see:
Conection Path: A, B
Connection Status: A
Managing Instance: A
My conclusion is, I have a problem with the Connection Path B of my C240..

VLAN tagging for Desktops

I have a test VDI 3.1.1 system set up and I have to say, I'm quite impressed. In about a day, I was able to serve Windows 7 desktops, something we can't do with our current VMware View setup. One apparent limitation I have run into, however, is 802.1q VLAN tagging support for Desktop NICs. I have created a 2-way aggregate on nxge0 and nxge1. The portchannel these are connected to is set up for 802.1q tagging, and Solaris is plumbed with aggr13001 to tag its packets with VLAN 13, for example. However, traffic from Desktops is not so tagged, so its packets go nowhere. Is there any way to define a VLAN for a given Desktop Pool? This is important for us, as we tend to keep server systems on campus-only subnets, while desktops get Internet-routed addresses.
Thanks,
Charles

Aggregation shouldn't have any adverse effect here. You need to configure VDI to use the correct VLANs on a per Pools basis. In the VDI Manager first navigate to the Desktop Provider -> Networks tab and 'Refresh' the networks. This will scan all VirtualBox hosts in the provider for currently plumbed interfaces, each of which will be listed by their subnet.
After all networks are detected navigate to the Pool -> Settings tab and select 'Host Networking' followed by the required subnet(s). The primary subnet listed here is used for RDP connections.

Transport dot1q vlan tagging over wan link

Hi,
I would like to transport 802.1Q vlan tagging over a wan link, is it possible ?
I heard about l2tp V3...
Best regards

Hi,
You would have to use a technology such as Ethernet over MPLS (EoMPLS) or VPLS. This technology is referred to as Layer 2 VPNs. You can get more info on this at the following locations:
EoMPLS (part of the Cisco Any Transport over ATM suite):
http://www.cisco.com/en/US/products/ps6646/products_ios_protocol_option_home.html
VPLS:
http://www.cisco.com/en/US/products/ps6648/products_ios_protocol_option_home.html
Hope that helps - pls rate the post if it does.
Regards,
Paresh

Vlan tagging on VIC 1225

Similar Messages

Maybe you are looking for