Number of groups of ports and VLANs by vSwitch

Similar Questions

• Difference between groups of ports and VLANS

  Hi guys

  I read ESX Admin guide 2 times till now, but I still don't know what exactly is the difference between groups of ports and VLANS? I understand, but if someone asks me this question I will not be able to respond with confidence.

  Network also label: my understanding is that it's just label No technical significance in configuration?

  Thanks in advance

  One VLAN is one of the many settings that you can configure for a group of ports, you also have the tabs security, Traffic Shaping and consolidation of NETWORK cards.

  Port group name, you associate you a VM port group must be placed systematically on other hosts if you want to migrate or virtual failover from one host to another.

  Scott.

  -

• Group of port and the naming convention for vLAN

  What is the naming convention better for groups of ports on vSwitches?  This naming convention should match how we name them VLAN on the physical switches and how important is that?

  Hi VMinator,

  To answer your question, he has not agreed to 'standard' for names of portgroup.  That's all what you're comfortable with the support and what works for you and your organization.  A bit like server names; Some companies are going hardcore with the naming conventions and others their name after the characters in science fiction or world of warcraft bosses

  Forensic science more you pack in a naming of the control standard more you have (i.e. for scripts, health check, etc. see below).  Also, if the name itself answers questions on his own and allows you to save a phone call that is priceless.  For example - the guys says unix... "Uh which network to choose for my new virtual machine.  My IP is blah blah blah. "Well, with right portgroup name, this question would have answered itself... and maybe even recorded some interruptions of service in other cases by the simple fact of being clear and effective in the communication of how this virtual device should work: purely expressed through an appropriate naming convention.

  Here's another one.  My last concert, we had thousands of virtual machines that had to move data centers and when they landed, they needed to change the IPs and start using 3 vNIC (instead of 1) on each virtual machine.  Each vNIC with a different subnet mask.  All support should be conducted by a team of outsourced with minimum experience of VMware.  The only way to support something like this and be effective is PowerCLI.  With just invited the naming convention only, you can perform various tasks such as query the virtual computer and check its settings of portgroup compared to its actual IP information in the operating system, initiate a ping from .NET to the virtual machine, if there is any questions Act automatically.  Some actions that will have to be performed include, for example, change the portgroup or mask on a set of clients;  Or questioning guests and glean information network (CDP, vSwitch, portgroup of information etc.) and compare observed network vs network expected enumerated in the PG naming convention. etc etc.  The list of actions that you can take are limited only by your creativity.  The naming standards give you effective power both in manual and automatic efforts.

  Still, notice of one man, but every site I care and feeding generally ends with a PG standard similar to what I first described above in my previous post.  Don't forget my example naming convention is Basic.  There are many other attributes that you can add (i.e. in vCloud deployments, in addition to the info network, you can choose to identify various features specific to vCloud org-networks, etc.).

  TBH just most of the companies have appointed VM-network exchanges (ok not bad) or some random shortname which doesn't help troubleshooting.  They are fairly easy to fix and also change over time, if necessary.  You can easily drag and drop a set of virtual machines (although I don't personally do this way) in the new port group (via the page of networking to CTRL + SHIFT + N) or PowerCLI it (Yes!  way to go).  Of course, always the ping tests before and after the change.  There are a lot of scripts out there (or ask master lucd post in PowerCLI VMTN forums).  If this is net-news, then you are ahead of the game and will have a standard to follow, whatever it is.

  Best of luck and have fun!

• Migration of the existing groups of port DVS vSwitch

  Hey guys,.

  I am looking for a good article, but so far I don't have if existing port a groups with std vSwitch ESXi can I migrate to a newly created DVS.
  I saw VMs, Assistant network management, but it seems that I have to create all the groups before port.

  Is this really the case? as I have 70 groups of ports and I don't want to do the job manually.

  Any suggestion?

  Thanks in advance

  Evening,

  This process can be script but yes destination port groups must be created first.   I suggest to use the Onyx project to get the commands in powershell to create groups of ports.  Personally, I have 700 groups of ports and I understand your pain.   Onyx will allow you the creation of a port group unique in powershell then all you need to change is the name and vlan id.   If you have the standard naming, you should be ok...

  Let me know if you have any additional questions or I missed your question.

  Thank you

  J

• Rename groups of ports

  Hello

  In vCenter via web client, I added a vswitch to some host. I have added a group of ports for the new vswitch so that I have two groups of ports on each vswitch who manage some physical cards and renamed the old port 'VM Network' groups while it appears on the web with a unique name client network tab that hostname in it.

  I put the network card of virtual machines to the new port groups.

  The old "VM Network" "VM Network1" and the "VM Network2" still appear in the web client, Network tab, they have even machines in the old network, although I changed to they renamed network. So the machine appears twice, in the new one the old network. I can't get rid of the old network. When I try to migrate virtual machines from the old to the new network, the list is empty.

  

  Also, when I try to clone a machine, I get a warning that the NIC of the virtual computer using a network ("the new network name") that are not accessible. It seems to me, the old network names are still in use. Is there a chance to fix this? I'm afraid to have performance problems.

  The virtual machine have Active snapshots, where shots were created so that virtual machines were still attached to the groups old port? In this case, the ports 'ghost' groups should disappear after deleting snapshots.

  André

• Script to get the VLan ID, vSwitch, networking and group of vCenter vmkernel ports.

  Hello

  Need help to get the script of ' Script for the VLan ID, vSwitch, networking and group ports vmkernel of vCenter. "to CSV

  Any help will be much appreciated.

  Get-VMHost | {foreach}

  $vmhost = $_

  $PortGroups = $vmhost | Get-VirtualPortGroup

  $vSwitchs = $vmhost | Get-VirtualSwitch

  $pNic = $vmhost | Get-VMHostNetworkAdapter

  $Managementinfo = $pNic | Where-Object {$_.} ManagementTrafficEnabled - eq $true}

  $vMotioninfo = $pNic | Where-Object {$_.} VMotionEnabled - eq $true}

  $FTinfo = $pNic | Where-Object {$_.} FaultToleranceLoggingEnabled - eq $true}

  $vlanID = $PortGroup | Where-Object {$_.name - eq $Managementinfo.ExtensionData.spec.Portgroup} | Select-object - ExpandProperty VLanId

  {foreach ($PG in $PortGroups)

  #Management Info network

  If ($Managementinfo.PortGroupName - eq $PG.) {Name)

  $MGMTStatus = "enabled".

  $ManagementIP = $Managementinfo | Where-Object {$_.} PortGroupName - eq $PG. Name} | Select-Object - ExpandProperty IP

  }

  else {}

  $MGMTStatus = "Disabled".

  $ManagementIP = $null

  }

  #vMotion Info network

  If ($vMotioninfo.PortGroupName - eq $PG.) {Name)

  $vmotionStatus = "enabled".

  $vMotionIP = $vMotioninfo | Where-Object {$_.} PortGroupName - eq $PG. Name} | Select-Object - ExpandProperty IP

  }

  else {}

  $vmotionStatus = "Disabled".

  $vMotionIP = $null

  }

  #FT Info network

  If ($FaultToleranceLoggingEnabled.PortGroupName - eq $PG.) {Name)

  $FTStatus = "enabled".

  $ftIP = $FTinfo | Where-Object {$_.} PortGroupName - eq $PG. Name} | Select-Object - ExpandProperty IP

  }

  else {}

  $FTStatus = "Disabled".

  $ftIP = $null

  }

  #vmKernel name

  $VMKernel = $pNic | Where-Object {$_.} PortGroupName - eq $PG. Name} | Select-Object - ExpandProperty DeviceName

  $result = "" | Select-Object HostName, vSwitchName, PortGroupName, VLanID, ManagementTraffic, ManagementIP, vMotionTraffic, vMotionIP, FTTraffic, FTIP, VMKernel

  $result. Host name = $vmhost.name

  $result.vSwitchName = $PG. VirtualSwitchName

  $result. PortGroupName = $PG. Name

  $result. VLanID = $PG. VLanID

  $result. VLanID = $PG. VLanID

  $result. ManagementTraffic = $MGMTStatus

  $result. ManagementIP = $ManagementIP

  $result.vMotionTraffic = $vmotionStatus

  $result.vMotionIP = $vMotionIP

  $result. FTTraffic = $FTStatus

  $result. FTIP = $ftIP

  $result. VMKernel = $VMKernel

  $result

  }

  } | Export-Csv c:\temp\data.csv

• Port-groups, vSphere 5 and Jumbo (iSCSI) frames

  We will implement a UCS system with EMC iSCSI storage. Since this is my first time, I'm a little insecure in design, although I have acquired a lot of knowledge to read in this forum and meanders.

  We will use the 1000V.

  1. is it allowed to use only a GROUP of ports uplink with the following exchanges: mgmt, vmotion, iscsi, vm network, external network?

  My confusion here is what jumboframes? Should we not separate for this connection? In this design all executives are using jumboframes (or are this set by portgroup?)

  I read something about the use of the class of frames extended Service. Maybe it's the idea here.

  2. I read in a thread do not include mgmt and VMotion in the 1000V and put it on a vs. Is this correct?

  In this case, the design of uplink would be:

  1: Mgmt + vMotion (2 vNIC, VSS)

  2: iSCSi (2 vNIC, 1000v)

  3 data VM, external traffic (2 vNIC, 1000v)

  All network cards for parameter as active, Virtual port id teaming

  Answers online.

  Kind regards

  Robert

  Atle Dale wrote:
  I have 2 follow-up questions:
  1. What is the reason I cannot use a 1000V uplink profile for the vMotion and management? Is it just for simplicity people do it that way? Or can I do it if I want? What do you do?
  [Robert] There is no reason.  Many customers run all their virtual networking on the 1000v.  This way they don't need vmware admins to manage virtual switches - keeps it all in the hands of the networking team where it belongs.  Management Port profiles should be set as "system vlans" to ensure access to manage your hosts is always forwarding.  With the 1000v you can also leverage CBWFQ which can auto-classify traffic types such as "Management", "Vmotion", "1000v Control", "IP Storage" etc.
  2. Shouldn't I use MTU size 9216?
  [Robert] UCS supports up to 9000 then assumed overhead.  Depending on the switch you'll want to set it at either 9000 or 9216 (whichever it supports).
  3. How do I do this step: "
  Ensure the switch north of the UCS Interconnects are marking the iSCSI target return traffic with the same CoS marking as UCS has configured for jumbo MTU.  You can use one of the other available classes on UCS for this - Bronze, Silver, Gold, Platinum."
  Does the Cisco switch also use the same terms "Bronze", Silver", "Gold" or "Platimum" for the classes? Should I configure the trunk with the same CoSes?
  [Robert] The Plat, Gold, Silver, Bronze are user friendly words used in UCS Classes of Service to represent a defineable CoS value between 0 to 7 (where 0 is the lowest value and 6 is  highest value). COS 7 is reserved for internal traffic. COS value "any"  equals to best effort.  Weight values range from 1 to 10. The bandwidth percentage can be  determined by adding the channel weights for all channels then divide  the channel weight you wish to calculate the percentage for by the sum  of all weights.
  Example.  You have UCS and an upstream N5K with your iSCSI target directly connected to an N5K interface. If your vNICs were assigne a QoS policy using "Silver" (which has a default CoS 2 value), then you would want to do the same upstream by a) configuring the N5K system MTU of 9216 and tag all traffic from the iSCSI Array target's interface with a CoS 2.  The specifics for configuring the switch are specific to the model and SW version.  N5K is different than N7K and different than IOS.  Configuring Jumbo frames and CoS marking is pretty well documented all over.
  Once UCS receives the traffic with the appropriate CoS marking it will honor the QoS and dump the traffic back into the Silver queue. This is the "best" way to configure it but I find most people just end up changing the "Best Effort" class to 9000 MTU for simplicity sake - which doesn't require any upstream tinkering with CoS marking.  Just have to enable Jumbo MTU support upstream.
  
  4. Concerning Nk1: Jason Nash has said to include vMotion in the System VLANs. You do not recommend this in previous threads. Why?
  [Robert] You have to understand what a system vlan is first.  I've tirelessly explained this on vaiours posts .  System VLANs allow an interface to always be forwarding.  You can't shut down a system vlan interface.  Also, when a VEM is reboot, a system vlan interface will be FWDing before the VEM attaches to the VSM to securely retrieve it's programming.  Think of the Chicken & Egg scenario.  You have to be able to FWD some traffic in order to reach the VSM in the first place - so we allow a very small subnet of interfaces to FWD before the VSM send the VEM's programming - Management, IP Storage and Control/Packet only.  All other non-system VLANs are rightfully BLKing until the VSM passes the VEM its policy.  This secures interfaces from sending traffic in the event any port profiles or policies have changed since last reboot or module insertion.  Now keeping all this in mind, can you tell me the instance where you've just reboot your ESX and need the VMotion interface fowarding traffic BEFORE communicating with the VSM?  If the VSM was not reachable (or both VSMs down) the VMs virtual interface would not even be able to be created on the receiving VEM.  Any virtual ports moved or created require VSM & VEM communication.  So no, the vMotion interface vlans do NOT need to be set as system VLANs.  There's also a max of 16 port profiles that can have system vlans defined, so why chew up one unnecessarily?
  5. Do I have to set spanning-tree commands and to enable global BPDU Filter/Guard on both the 1000V side and the uplink switch?
  [Robert] The VSM doesn't participate in STP so it will never send BPDU's.  However, since VMs can act like bridges & routers these days, we advise to add two commands to your upstream VEM uplinks - PortFast and BPDUFilter.  PortFast so the interface is FWD faster (since there's no STP on the VSM anyway) and BPDUFilter to ignore any received BPDU's from VMs.  I prefer to ignore them then using BPDU Gaurd - which will shutdown the interface if BPDU's are received.
  Thanks,
  Atle, Norway
  Edit:
  Do you have some recommendations on the weigting of the CoS?
  [Robert] I don't personally.  Others customer can chime in on their suggestions, but each environement is different.  VMotion is very bursty so I wouldn't set that too high.  IP storage is critical so I would bump that up a bit.  The rest is up to you.  See how it works, check your QoS & CoS verification commands to monitor and adjust your settings as required.
  E.g:
  IP storage: 35
  Vmotion: 35
  Vmdata: 30
  and I can then assign management VM-kernels to the Vmdata Cos.
  Message was edited by: Atle Dale
  

• Two groups of ports with same VLAN on the same Vswitch?

  I'm doing a consolidation.  We had two different people put up two closed different of Vsphere and different network labels were used.   Of course the network labels must exactly match vmotion without losing connectivity.    So I was hoping that I could just create groups in double port on my vswitch for VLAN do not match them.  I know I could just migrate them and move quickly from the network label, but some of them are essential and may not fall.

  For example, on a cluster, I might have a port for Vlan ID 88 group that says 'Web DMZ'.  But the other cluster has "WWW" VLan ID 88.    Can I just create a second group of ports on the first group which also used Vlan ID 88 with the name 'WWW' and I started?    Which will cause problems with switching (loops, etc.)?

  Hope it makes sense.  Guess the short answer is can I I have two groups of different ports on a vswitch using the same VLAN ID tag without causing problems?

  Creation of several groups of ports with the same VLAN ID should not cause any problem. This is only marking/close the traffic to and from the virtual machine, is nothing like that of loops,... to be afraid of.

  André

• How VLANs ' IP subnet ing works with based port of VLAN (series N2000 and N3000)

  Hi all

  I have a small pile of x N3024 2 acting as my heart L3 with a lag of 2 x 10 g down to a stack of x N2048 5 acting as L2 switch for my PC workstations.

  Workstations are that all on the port assigned VLAN 10 (switchport access vlan 10). I have a bunch of developers who want to access without restrictions more or less to assign random IP addresses for their VM (Virtualbox and VMware) Workstation.  As you can imagine, I would like some control over this situation.  the powerconnect guide I described features of subnet IP VLAN but does not seem to enter in how it works and interacts with the port actually function vlan assignments.

  What I currently have is the VLAN 10 assigned to a segment that support the subnet 172.100.x.x which dates back to our base of L3 for routing to other segments. What I want to do is to configure the VLAN based on IP and then load the dev is to config their VM with another IP range, say 10.10.x.x.

  Theory here is, I set the L3 core with say 20 VLAN and an IP to register in L3 path between subnets and then configure the battery switch L2 workstation with IP - based VLAN to recognize 10.10.x.x and separate on VLAN 20.

  However, I think the simplified here question is if I have a nail up to 10 ports VLAN, will the than basic work IP subnet VLANS as I want only it? Or, I need to create a subnet IP VIRTUAL local area network for the two IP ranges? I have to remove the assignenment VLAN per port and are based entirely on the treatment of subnet IP VLAN?

  If there is a better RTFM on this topic you can tell me I would appreciate it

  Thank you!

  I ended up calling specialists... great Dell technical support here.

  In fact, the IP based VLAN works very close to what I want to achieve. Missing from the user guide is that the port needs to be in the mode. Ports using switch port mode and bound to a VLAN just didn't work... probably because the vlan IP based did not differ from the port binding. Dell support has suggested to use the trunk mode, but my answer is finished using the general mode; any traffic not referenced, PVID located my usual LAN vlan ID and acceptance of port traffic of new vlan based on IP. In this way, I'm able to have a physical host DHCP on the corporate LAN and a virtual machine on that host to bind to a different subnet which is then isolated in the new NAV based on IP.

• How to add a VLAN on a trunk port and channal port

  Hi all

  I need to set up a configuration details below.

  1 how to add several VLANs on Cisco 4500 switch trunk port. (vlan existing also will be there)

  2. I have also 2 4500 switch to shared resources and channel ports.

  So my question is should I add new VLANs on the trunk port and port also channel?

  Looking for an answer

  It depends on your existing configuration.  If you have not specified WHAT VLAN is allowed, they would be by default.  If this isn't the case, you need to add the VLAN again to the definition of trunk.

  Too far again go to that VLAN, that also depends.  IF you have VTP really set up, you have to create the new vlan on one of the master switches in VTP (probably your 4500) and the definition spread to other switches.   If this isn't the case, then you declare new VLANs on each switch that would need them.

• vShield Manager interface network & group of port / vlan

  Hello:

  I'm new to vShield and looking to use it in our environment.  I read the documentation and seeks to install the first part, the Device Manager vShield.  By reading the docs, it specifies the management interface for the vShield Manager is in its own group of port.  Why is this?  Is it okay to put this interface in a group of existing port?  Is it possible in a port with another management SMV Group (vCenter, etc.)?  Also, is it better practice to have this in a standard vs dvswitch, or isn't it important?  I was looking through posts and the other docs and so far I don't see a clear reason why it must be in its own group of port.

  So far, the only element that we will consider is vShield Endpoint, for now.  We have no plans to watch App or Edge, etc.

  Thanks in advance!

  Hello

  The Manager can be put on any standard or distributed port group. Do not create any new groups-port. The only thing that is necessary to access vCenter/SSO and DNS, NTP server (mirror).

  There is no need to create a new. IMHO, this could be a failure in the doc.

  Kind regards

  Roland

• Import of groups of ports in vDS using powershell and

  I have a VCenter 5.5 with a 5.5 vDS. I'm trying to import several groups of ports in the vDS using powershell. The script is below. I'm under problems in trying to put the "Teaming and Failover" option to 'Route based on a physical load' by default 'Route based on originating virtual port' for the Group of individual ports, I know that I can do from the client, but I would like if possible do it with a script. Someone point me in the right direction? Port groups to import very well with all the correct settings, that I put, but I can't seem to find how to set the load balancing policy.

  to connect-viserver 'myvcenter '.

  $vds = Get VDSwitch -name "my Switch VD"

  Import-Csv c:\temp\vdsportgroup.csv | % {New-VDPortgroup -VDSwitch $vds -Name $_. Name -VlanId $_. {VlanId -NumPorts $_.ports}

  
  
  

  
  
  

  
  
  

  Edit: Scratch that I wrote earlier, it was with the older VDS cmdlets. This should work:

  Get-VDPortgroup MyVdPg | Get-VDUplinkTeamingPolicy | Game-VDUplinkTeamingPolicy - LoadBalancingPolicy LoadBalanceLoadBased

  You can simply direct the Group of newly created port directly object to cmdlets like this:

  Import-Csv c:\temp\vdsportgroup.csv | % {New-VDPortgroup - VDSwitch $vds - name $_.} Name - VlanId $_. VlanId - NumPorts $_.ports | Get-VDUplinkTeamingPolicy | Game-VDUplinkTeamingPolicy - LoadBalancingPolicy LoadBalanceLoadBased}

• Create groups of ports from excel

  I have a spreadsheet with 60 groups of ports, that I need to create. My fields are VLAN and name. Looking at the cmdlets reference guide , it seems that the command to create one would be Get-VDSwitch-name 'Boston ' | New-VDPortgroup-name 'test SQL VLAN 250″ - VLanId 250. Can someone help with the structure to create it from an excel file? I'm checking the rate maximum config to see if I hit a limit about my ports with vSphere 5.1 and need to set a number of ports per port group. Thank you.

  Try something like this

  $dvSw = Get-VDSwitch -Name "Boston"
  
  Import-Csv dvPortgroups.csv -UseCulture | %{  New-VDPortgroup -Name $_.PgName -VlanId $_.VLanId -NumPorts $_.Ports -VDSwitch $dvSw}
  

  The CSV file is supposed to have 3 columns

  PgName, VLanId, Ports

  PG1, 100, 32

  PG2, 100, 32

  You can check the number of available ports on the dvSwitch first, to see if you can add he's the ports required for exchanges

• ISA550W with multi SSID (each having separate DHCP and VLAN tag)?

  ISA550W can do the following (in order):

  (1) first group interfaces physical and Wi - Fi SSID (s) set

  (2) then assign with DHCP (ip or subnet)

  (3) then add a tag VLAN interfaces and SSID (s) wireless

  (4) repeat 1 to 3 for the remainging and SSID (s) wireless interfaces to create the following diagram:

  

  (1) I believe that could transform these ports in ports of junction. That said, I'll normally in the ports themselves through networking, change them to the Trunk ports and add the appropriate VLAN. Please keep in mind that as a general rule which present you to a Trunk port is another switch. Then you EF the VLAN appropriate to each switch coelio that attach a device such as a workstation. There are some devices that do not support be connected to a Trunk port, like the OnPlus of Cisco device however.

  (2) think SSID that only access ports. Because you could never connect a device that would support Trunking wireless, you can apply only 1 VLAN by SSID wireless-> basic settings.

  (3) because the SSID cannot be interconnection. See #2 above for configuring the VLANS on SSID.

  Sent by Cisco Support technique iPhone App

• Config network and VLAN

  I inherited a network in a colo data center.

  Current network has a Dell 2724 switch in unmanaged mode. Servers using the 192.168.195.0/24 range.

  A new facility will be 3 vSphere, 2 Dell Equalogic PS4000 hosts and 2 Dell 6224 switches for redundancy.

  The 6224 are segmented into VLAN.

  The new configuration was to use the beach of 192.168.196.0/24.

  VLAN 205 receives data from firewall to the camp and our 2724 switch.

  On the 6224 2 port goes to the old switch 2724. He is member of the VLAN 205 and 405 defined on Trunk, AdmitTaggedOnly.

  ports 3-11 are designted for network traffic from virtual machines and are members of the 405 VLAN defined on the access, AdmitUntaggedOnly

  We now want to virtualize the old servers on the new ESX hosts.

  If I put the IP of my VM to 192.168.196.xx, everything is good, I have full network connectivity.

  If I set 192.168.195.xx, I get no connectivity at all.

  I see no connection of IP range in configuring VLAN.

  I need to be able to transport the two beaches of 3-11 ports, because at this point, I can not change the IP addresses of the old servers.

  What Miss me?

  Allow several VLANS on the same ports of physical switch, you must configure these ports as junction ports switch, which allows the two VLANS. 205 and 405. On the ESX host, create two groups of ports on the vSwitch 'Virtual Machines' - one for each VLAN - and define the appropriate VLAN ID. It's called Virtual Switch Tagging (VST). For more information, see http://www.vmware.com/files/pdf/virtual_networking_concepts.pdf

  André