VLAN tagging on VIC 1225

Similar Questions

• C22 M3 VIC 1225 Cisco UCS no link

  I have a M3 C22 with Vmware 5.5 running and Cisco VIC 1225 card.  I've recently updated all firmware for 2.0.3i on the box through CIMC.  I see the installed Cisco VIC card and I have configured each port as a standard switch.

  I installed the fiber SFP - 10 G - SR module in ports.

  Product name: UCS VIC 1225

  Product ID: USCS-PCIE-CSC-02

  Current firmware: 4.0 (1e)

  I have my 4510R switch + E configured as follows:

  interface TenGigabitEthernet2/1/1

  Description map VM Cisco Fiber NETWORK

  switchport trunk vlan 20 native

  switchport trunk allowed vlan 20

  switchport mode trunk

  spanning tree portfast

  is there any other configuration that I'm missing about why I'm not able to get a connection between the server and the switch?

  Cool, I hope you also tried a different port on the switch to be sure.

  If the card was bad, please mark this thread as a response so that you can show the users that you have this figured out; I hope I was help somehow.

  -Kenny

• PowerConnect 5448, how all the trunk of physical ports and allow all the VLAN tags to pass transparently

  I would like to achieve such a goal, do all acts of switch ports 5448 as 'trunk', that is, just as an entry-level switch. Yes, I want all the tags VLAN through seamlessly.

  Let me explain more clearly. If

  • With MAC1 PC1 is connected to switch port 1 (port 1) in short, PC2 with MAC2 is connected to port 2.
  • PC1 sends a packet with vlanid = 30 ethernet VLAN tag,.

  I want the ethernet packet must be SENT to port 2 without modification, i.e. 2 PC will receive the package with exactly the same byte packets that PC1 sends.

  Currently, I want to configure all ports from the switch to act like this, but how to do this? Can someone tell me the more concise CLI commands to achieve? Alternatively, it is possible via the web interface?

  I must again complain the poor manual, which talks about this concept and this notion over and over again (both of ambiguous statements that the author of manual does not), BUT doesn't explain them not at the level of the content of the packages, so I'm totally at a loss.

  I tried the web interface. Simply together port 1 and 2 for access mode or general mode does not work.

  Please help me. Thank you in advance.

  Thank you, Josh, you begin to point me in the right direction.

  Now, I know just affecting a Trunk port, or general mode is NOT sufficient.  I have to give what kind of package VLAN (i.e. what VLAN ID) are allowed to pass through.

  To do this assignment, I have to take 2 steps. say first of all, the database "vlan" to recognize a VLAN ID in the world, then say that some specific port is allowed to pass through with this VLAN ID specific packages.

  Thus, in order to pass packets VLAN with VLAN ID 18-25 no modified (marked packets in packages marked on) g7 to the g8 to port port, I have to do:

  Console # config
  Console (config) # vlan database
  Console(config-VLAN) # vlan 18-25
  Console(config-VLAN) # exit

  Console (config) # interface ethernet g7
  Console # switchport general mode
  Console # switchport General allowed vlan add the tag of 18-25

  and again for the g8. And if I want to 48 ports to act like that, I have to write this kind of order 48 times right? All the shortcuts?

  Some useful links for me: http://hasanmansur.com/2012/10/14/powerconnect-switchport-modes/

• Configuration VIC 1225 in C240 problems

  I'm trying to set up a server with the installed VIC 1225 C240.

  Firstly, I would like to know if it is even possible to use it without fabric interconnections or Nexus switches. Suppose that I am just their regular snap up some 10GbE switches. I can change this but wante to have a better idea of my design decisions - not much info about when the VIC 1225 may or must be used outside this context. »

  Secondly, I am following the instructions here:

  http://www.Cisco.com/en/us/docs/unified_computing/UCS/c/SW/CLI/config/Guide/1.4.1/b_Cisco_UCS_C-Series_CLI_Configuration_Guide_141_chapter_01001.html#task_3C31BD7B25BF4CF6839B7B12DE014482

  I checked that the VIC is installed in slot 1 visually as well as via the output below, but the output below is not what I expected by the documentation. I am not able to enter into the scope of this adapter, and it appears in "display adapters pci" and not "adapters". It is as if she is not even recognized as a VIC.

  Any help would be appreciated.

  ucs-c240-m3 /chassis # scope adapter 1
  Error: Managed object does not exist, use show command to list valid targets
  ucs-c240-m3 /chassis # scope network-adapter 1
  Error: Managed object does not exist, use show command to list valid targets
  ucs-c240-m3 /chassis # scope pci-adapter 1
  % Incomplete command
  ucs-c240-m3 /chassis # scope pci-adapter 1
    Press Enter key
  ucs-c240-m3 /chassis # scope
  adapter          Cisco Systems UCS Virtual Interface Card
  dimm-summary     Information common to all DIMMs
  fan-policy       Fan Policy parameters
  firmware         Get all Components Firmware
  flexflash        Cisco FlexFlash Controller
  gpu              Show GPU cards present in the system
  hdd              Host local hard disk drive
  network-adapter  Show network adapters present in the system
  storageadapter   RAID Controller
  ucs-c240-m3 /chassis #
  

  Matt,

  The VIC 1225 is fully supported as a stand-alone card outside UCSM and by default it runs in the classic Ethernet mode which means that it is compatible with any standard IEEE 10GE switch.

  The VIC is not supported in Slot 1 in the C240, he is supported in Slot 2 or 5

  (http://www.cisco.com/en/US/docs/unified_computing/ucs/c/hw/C240/install/replace.html#wp1337242).

  Without be installed into the cracks, the connector of NC - if at the end of the PCIe bus will not be conencted and the MMIC has no interface to configure the card.  Once you have installed it in a supported housing, you should be able to frame scope and show the adapter.  Then brought to the map as shown below

  UCS-c240-m3 # chassis range

  UCS-c240-m3 /chassis # Show map

  Seller of product ID of the Slot PCI product name serial number

  -------- -------------- -------------- -------------- --------------------

  UCS VIC 1225 FCH162974VP UCSC-PCIE-2 C... Cisco Systems Inc.

  UCS-c240-m3 scope adapter /chassis # 2

  UCS-c240-m3/chassis/adapter #.

  If you are able to see that your VIC made me know if you have additional questions.

  Steve McQuerry

  UCS - Technical Marketing

• C200M3, VIC 1225, Catalyst 4500 x

  Hello

  Everyone has set up a server with the installed VIC 1225 C200M3 and configured an etherchannel to a pair of Catalyst 4500 x?

  The server is freshly installed ESXi 5.1 standard vSwitch and two vNIC active/active and LB Hash IP value.

  As soon as the etherchannel is applied in the x 4500, the traffic of the host goes down.

  Have seen a few articles indicating that this will only work with the 1225 VIC if it s connected to a FEX or Nexus, is that correct?

  Concerning

  Hello Andreas,

  VIC in classical Ethernet (CE) interacts with any standards-based Ethernet switch.

  Can you please check the mac address of the interface vmkernel? Should one of the vNIC mac address?

  If so, the traffic could be running in default CSCuf65032

  As a work-around, you could recreate the vmkernel interface so that it would be the mac address which is not delong to vNIC.

  http://KB.VMware.com/kb/1031111

  HTH

  Padma

• RV Support VLAN Tagging on WAN Port?

  Hello

  I would like to know if RV Series Router can support VLAN tagging on the port WAN himself? I need this cause my ISP using these methods to connect to the router/modem to the end user.

  Thank you.

  -----

  Kind regards

  Danny

  Please visit RV315W.

• Server Rack with two VIC 1225 C460 - vNIC UCSM investment policy

  I try to incorporate C460 have 2 cards of VIC 1225 with UCSM. The goal is to have 2 assigned to each VIC, one by FI ethernet interfaces.

  vNIC on VIC 1 - FI 1A failover to FI B

  vNIC 2 on VIC 1 - FI B to FI A failover

  vNIC on VIC 2 - FI 3A failover to FI B

  vNIC 4 on VIC 2 - FI B to FI A failover

  I created a service with 4 vNIC profile and assigned to C460. When the UCSM is configured to use the default system for the vNIC/vHBA investment strategy, all 4 to network adapters are assigned to a VIC. When you try to manually place with 2 vCon1 and 2 on vCon2, I see insufficient resources error. The CIV are recognized and UCSM Server tab shows the two of them as well as adapters.

  Could you get it someone please let me know how?

  Thank you!

  The C460 has an integrated BCM-57711 that also would be recognized by the system.  What is more likely is that the 1225 s of VIC are on vCon1 and vCon3 and the map of the BCM is on vCon2, since FF is is not supported on the Broadcom adapter it would cause the association to fail.  Try to place the manual placement with vCon1 and vCon3 and see if that clears up the issue.

  Steve McQuerry

  UCS - Technical Marketing

• UCS C420M3 server with VIC 1225, can't see the ethernet LOM ports

  Hi Guyz,

  We have C420M3 server with VIC 1225 connected on PCIe slot, with fabric Interconnet.

  After you have installed the OS & drivers, vNIC created the VIC 1225 by the service profile appear, but 4 gig on server LOM ports do not appear.

  Any idea. ?

  Thank you

  If you incorporate your rack server to UCSM, you will be able to use the LOM ONLY ports for traffic of Mgmt, when you join the server mode to 'Dual Wire'.

  It is useless (unless you have one for a special reason, I do not intend at this very moment) to use ports LOM, once you entered the server, precisely because of the 1225 VIC is not a regular NIC card or a regular HBA, it is indeed a CNA (Converged Network Adapter), which essentially allows you to do in a map , what you would do with two (which means "what you would do with a NETWORK card and HBA separated')

  When you have a VIC card, you actually have the ability to create up to 256 virtual interfaces (this is the capacity of the equipment, always limited by the operating system, please keep this in mind), this is the reason why, after the server is integrated, entirely rely on the interfaces in the Service profile instead of the physical interfaces.

  Find more info here:

  http://www.Cisco.com/c/en/us/products/interfaces-modules/unified-computi...

  You have a specific reason to use the LOM ports rather than create 2 additional virtual interfaces in Server Service profile?

  -Kenny

• Boot FC SAN with server C260 M2 and VIC 1225

  Hello

  I'm trying to boot SAN CF installation with my server M2 C260. I have two VIC 1225 slot1 and slot7. Contained the vHBA entries table properties and MMIC boot, it doesn't seem to work. Looking at the sheet, this seems to be supported. Advice to solve this problem?

  I have updated the firmware and the BIOS/MMIC in the last 1.5.7e. Host operating system is ESxi5.5.

  See the screen shot for the vHBA parameters.

  Thank you

  Braven

  Your OptionROM is enabled for the VIC card in use?

  -Kenny

• VLAN Tagging (VST) and VLAN native on the same vswitch

  I'm trying to figure out if its possible to put running the VLAN tagging for a vswitch if our virtual machines are currently in the vlan 1 (vlan native) on our cisco switches. I don't know why it's set up this way, but change is not an option at this time.

  Ultimately what I'm trying to accomplish is setting up a group of servers that differ on one VLAN, but under the same vswitch. I'm assuming that VST is what I need, but I don't know if I can simply specify how vlan 1 as the vlan 1 is not marked on cisco switches and my understanding is that VST requires to carry a label.

  Your help is greatly appreciated.

  NuRD.

  With the vSwitch connected to a trunk on the physical switch port, create the port groups and you need only configure the ID then VLAN for the port groups that do not use of VLAN native. See for example http://kb.vmware.com/kb/1004074

  André

• Several Vlan tagging to vswitch

  Hi I have abt 20 vm in an ESX 4.0 each with different vlan and all the virtual machine cannot see each other what would be a better approach for this configuration. create a virtual switch for each computer virtual but with different vlan tagging assign each? (virtual switch 20 sense) or use pvlan a better option for this I only got 2 physical cables connected to this esx carrying all the traffic 20 vlan. Or any other recommendation?

  Thanks for any info

  sounds odd humm maybe these articles can help you:

  http://communities.VMware.com/docs/doc-4861

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1004887

  Alex

• VLAN tagging without trade?

  Is it possible to VLAN tag a port vSwitch without using a GROUP of ports using PowerCLI?  Similar to how would tag a port on a physical switch.

  OK, you use dvSwitches!

  I understand now what you want to achieve, even if with the help of exchanges has more advantages then the VLAN ID only.

  Of course, that this can be accomplished by using PowerCLI too.

  Try something like this:

  $dvSwitchName = "dvSwitch0"
  $dvPortId = "100"
  $VLAN = 220
  
  $portSpec = New-Object VMware.Vim.DVPortConfigSpec
  $portSpec.operation = "edit"
  $portSpec.key = $dvPortId
  $portSpec.setting = New-Object VMware.Vim.VMwareDVSPortSetting
  $portSpec.setting.vlan = New-Object VMware.Vim.VmwareDistributedVirtualSwitchVlanIdSpec
  $portSpec.setting.vlan.inherited = $false
  $portSpec.setting.vlan.vlanId = $VLAN
  
  $dvSwitch = Get-View -ViewType 'VmwareDistributedVirtualSwitch' -Filter @{'Name'=$dvSwitchName}
  $dvSwitch.ReconfigureDVPort_Task($portSpec)
  

• Intel VGT vlan tagging

  Hi all

  I have an interesting dilemma, I inherited a virtual machine that is on several VLANs through VGT vlan tagging within the OS in the virtual machine and the vNic is labelled a trunk of vlan 4095 allowing him to pass all traffic vlan via and it's beautiful and functional as expected.  Now for my dilemma, I can't figure out how the previous admin (how is no longer here) installation and set the VLANs inside the OS of the machine virtual because there is no VLAN interface, nor any kind of vlan tab in the properties of the network card, or any sort of breakthrough in tablets that I can find , there is nothing in the start menu or in device management and etc...  I'm a puzzle about how he set up them VLAN in the first place, is there some hidden, Intel application I need to run?  I have the pilot VGT and installer that he used "pro2kxp_v14_0.exe" I can run again, but I am about this if I reinstall top that it would eliminate all the existing definitions of VLAN and there are about 15 VLAN which would be bad for me.  Any ideas or suggestions?

  Thanks in advance.

  To set up the guest operating system, you must install the Intel Proset software. Which, by the sounds of it, you do.

  To access the confiugration usually, you go to the Device Manager and then view the properties for the actual network card. Memory, you may need to do this from a Console session instead of the RDP as the software Intel connection cannot load in the Terminal Server services.

  -ben

• Configuration of VLAN Tagging

  I'm pretty new to VSphere, go to the install/configure in November class but had a consultant come do a show dog & Pony and he said we could do VLAN tagging to allow all our VLAN's communicate via a single distributed switch connected to a physical switch port 1. I can't get to work - can I get some advice on what I'm wrong? Attached screenshot - any help is appreciated

  Yes - 8 trade and assign each of them a single VLAN and then give them your virtual machines the portgroup appropriate.

• VLAN Tag vlan vs unidentified

  I am running Dell Power Connect 5548 and 5524 in an arrangement of battery on 3 floors.

  I have a question on the Middle floor by which DHCP addresses are not to be issued to clients in vlan 90

  See below

  GFLOOR

  interface gigabitethernet1/0/48
  channel-group mode 1 on
  switchport mode general
  switchport general allowed vlan add 40,50,70,80,90 tag
  VLAN allowed switchport General add 1 unidentified

  interface gigabitethernet2/0/48
  channel-group mode 1 on
  switchport mode general
  switchport general allowed vlan add 40,50,70,80,90 tag
  VLAN allowed switchport General add 1 unidentified
  !
  Interface Port - Channel 1
  Description LAG_TO_TOP_FLOOR
  switchport mode general
  switchport general allowed vlan add 40,50,70,80,90 tag
  VLAN allowed switchport General add 1 unidentified

  1FLOOR

  interface gigabitethernet1/0/48
  channel-group mode 1 on
  switchport mode general
  switchport general allowed vlan add 40,50,70,80 tag
  VLAN allowed switchport General add 1.90 untagged

  interface gigabitethernet2/0/48
  channel-group mode 1 on
  switchport mode general
  switchport general allowed vlan add 40,50,70,80 tag
  VLAN allowed switchport General add 1.90 untagged

  interface gigabitethernet3/0/24
  switchport access vlan 50
  Interface Port - Channel 1
  Description LAG_TO_TOP_FLOOR
  switchport mode general
  switchport general allowed vlan add 40,50,70,80 tag
  VLAN allowed switchport General add 1.90 untagged

  I just need to tap 1Floor interfaces or should I take 90 off unmarked first, then add to marked subsequently

  switchport mode general
  switchport general allowed vlan add 40,50,70,80,90 tag
  VLAN allowed switchport General add 1 unidentified

  Thank you

  ANDY

  If that's the difference and the other works and the other is not then I suggest matching the configs on the floors.

  Is there a reason why, the floors are set up differently?