Similar Questions

• Site of a host and distributed switches

  A number of geographic sites is under a vCenter Server.  Each of them have their own switches distributed, that connect to vCenter over the WAN.  It works very well.  However in a site, there is only a single ESXi host.  In this case, I'm not standardize the configuration of this host with other hosts in the cluster.  I create a dependency on the WAN for the switch to be managed by vCenter Server, because I can't handle the switch by connecting directly to the ESXi host, as I could with a standard past.

  One of the advantages of a vDS would be that I could add more hosts, and then have a standard configuration. However no future growth is expected for this site right now.

  Another advantage is that I could use the NIOC and the load based on grouping.  For now, bonds rising physical network of 2 x 10 GB are very underused, even under load max - probably less than 3%.

  The license is already here, it is not extra cost.

  Is there a compelling reason to use or not use vDS in this scenario?  Thoughts, experiences, suggestions?

  Evening,

  I would sound that there is simply no reason not to use the vDS.  Reasons to not use it have been elminated.

  -> Cost

  -> Experience

  -> Used to have is not local for recovery situations

  All you have left is bonus good reasons for using the vDS.

  Just my two cents.

  Thank you

  Joseph

• PowerCLI 5 and distributed switches

  Hello.

  I can't find a comandlets tocreating and work with PowerCLI 5 dvSwitches.

  These commands have been removed from the current version of PowerCLI?

  Hello

  You are right. The example is on a standard switch.

  There are currently no suppost to create virtual switch distributed using the PowerCLI cmdlets
  There is a team working on them, but they are not yet out.

  Best regards
  Leni Kirilov

  Team PowerCLI

• Initiator iSCSI and virutal switching

  Hi all

  When you set up a smaller ESX laboratory with only 2 cards psyhical best practice is to configure it up like this:

  pNIC0 - & gt; vSwitch0 - & gt; Portgroup0 (service console)

  ..................-> Portgroup1 (VMotion)

  ..................-> Portgroup2 (storage area network)

  pNIC1 - & gt; vSwitch0 - & gt; Portgroup3 (the VM network)

  Then, assign pNIC1 as the backup Teddy to Portgroup0, Portgroup1 and Portgroup2. Finally, assign pNIC0 as the Teddy to Portgroup3 backup. It works better but when them VLAN is enabled. You want to configure explicitly each portgroup strict failover mode and not to use any form of load balancing.

  However if you use a device with an initator software iSCSI, you need to install a 2nd Console of Service if the iSCSI is on another network? and you want it to be on another network?  So that being said would be your configuration would look like the following?

  pNIC0 - & gt; vSwitch0 - & gt; Portgroup0 (service console) 10.10.1.20

  ..................-> Portgroup1 (VMotion)

  pNIC1. - & gt; Portgroup2 (storage area network) 172.16.1.10

  pNIC1 - & gt; Portgroup3 (Service Console iSCSI) 172.16.1.11

  pNIC0 - & gt; vSwitch0 - & gt; Portgroup4 (the VM network) 10.10.1.X

  "However since your 2nd nic is on a differnet IP / network switch option custom" really work so what is the best configuration in a situation like that?

  When you set up a smaller ESX laboratory with only 2 cards psyhical best practice is to configure it up like this:

  pNIC0-> vSwitch0-> Portgroup0 (service console)

  ...-> Portgroup1 (VMotion)

  ...-> Portgroup2 (storage area network)

  pNIC1-> vSwitch0-> Portgroup3 (the VM network)

  It is the recommended configuration.

  However if you use a device with an initator software iSCSI, you need to install a 2nd Console of Service if the iSCSI is on another network?

  No you don't need a 2nd port SC. The supreme court should just participate in the iSCSI network. You can do this by using a route/router or firewall.

  HC participates in the iSCSI network as the original configuration will be fine. A second port SC is not necessary but if you really want to add - we do:

  pNIC0->-> Portgroup0 (service console) VLAN100 vSwitch0

  ...-> Portgroup1 (VMotion) VLAN200

  ...-> Portgroup2 (storage area network) VLAN300

  ...-> Portgroup3 (service console) VLAN300

  pNIC1-> vSwitch0-> Portgroup4 (VM Network) VLAN400

  All portgroup on the same VLAN can talk to all the other exchanges on the same VLAN.

  Best regards
  Edward L. Haletky
  VMware communities user moderator, VMware vExpert 2009, Analyst of DABCC
  ====
  Now available on Rough Cuts: ' VMware vSphere (TM) and Virtual Infrastructure Security: ESX security and virtual environment '
  Also available "VMWare ESX Server in the enterprise"
  SearchVMware Pro| Blue gears. Top virtualization security links| Security Round Table Podcast virtualization

• vSphere Distributed Switch 5.5 traffic filtering and tagging

  Someone had a chance to create a script to update the traffic filtering and marking of area of a group of ports on a vSphere 5.5 Distributed Switch? The settings are only exposed in the web client for Onyx is not an option.

  I need to create a rule with the values below.

  Traffic Filterig and marking:

  Set State enabled

  New rule of network traffic

  Name: name of the traffic rule

  Action: Tag

  CoS value: tag value Update CoS: 4

  Qualifiers of traffic:

  Traffic management: evacuation

  New qualifying traffic system: vMotion

  This is as much as I can get.

  $VDSPortGroup = get-VDSwitch Test - dvSwitch | Get-VDPortGroup Test-PG

  $Spec = new-Object VMware.Vim.DVPortgroupConfigSpec

  $Spec.configVersion = $VDSPortGroup.ExtensionData.Config.ConfigVersion

  $Spec.defaultPortConfig = new-Object VMware.Vim.VMwareDVSPortSetting

  $Spec.defaultPortConfig.FilterPolicy = new-Object VMware.Vim.DvsFilterPolicy

  Sorry, it took a little longer than expected.

  Try like this

  $dvSwName = "dvSw1".

  $dvPgNames = "dvPg1".

  $dvSw = get-VDSwitch-name $dvSwName

  # Activate LBT

  foreach ($pg in (Get-View-Id $dvSw.ExtensionData.Portgroup |)) Where {$dvPgNames - contains $_.} {Name}))

  $spec = new-Object VMware.Vim.DVPortgroupConfigSpec

  $spec. ConfigVersion = $pg. Config.ConfigVersion

  $spec. DefaultPortConfig = New-Object VMware.Vim.VMwareDVSPortSetting

  $spec. DefaultPortConfig.FilterPolicy = New-Object VMware.Vim.DvsFilterPolicy

  $filter = new-Object VMware.Vim.DvsTrafficFilterConfig

  $filter. Nom_agent = "dvfilter-credits-vmware.

  $ruleSet = new-Object VMware.Vim.DvsTrafficRuleset

  $ruleSet.Enabled = $true

  $rule = new-Object VMware.Vim.DvsTrafficRule

  $rule. Description = "name of traffic rule".

  $rule. Direction = "outgoingPackets."

  $action = new-Object VMware.Vim.DvsUpdateTagNetworkRuleAction

  $action. QosTag = 4

  $rule. Action += $action

  $ruleSet.Rules += $rule

  $filter. TrafficRuleSet += $ruleSet

  $spec. DefaultPortConfig.FilterPolicy.FilterConfig += $filter

  $pg. ReconfigureDVPortgroup ($spec)

  }

• Consolidation and failover for the uplink on the Distributed switch port group

  Hello

  I have a problem with the implementation of a distributed switch, and I don't know I'm missing something!

  I have a few guests with 4 of each physical cards. On the host eash I configured 2 virtual switches (say A and B), with 2 physical network by vSwitch using etherchannel adapter. Everything works fine for etherchannel and route based on the hash of the IP for the latter.

  Recently, I decided to create two distributed switches and move the respective physical ports of virtual switches to this distributed switches. Once again, I want to configure etherchannel and route based on the hash of the IP. But when I open the settings for the uplink port group, aggregation and failover policies are grayed out and cannot be changed. Apparently they inherit configuration also but I don't know where!

  Chantal says:

  Once again, I want to configure etherchannel and route based on the hash of the IP. But when I open the settings for the uplink port group, aggregation and failover policies are grayed out and cannot be changed. Apparently they inherit configuration also but I don't know where!

  You must set the card NIC teaming policy on trade in reality and not on the uplink group more expected.

• Difference between a Standard switch and distributed virtual switches

  Hi people,

  I wanted to know the difference between a Standard switch and virtual distributed Switches.What benefits (characteristics) of displacement or migration from switches Standard using Virtual Switches.Any distributed on this will be appreciated.

  Thank you

  vmguy

  In this article, there is more information on these two concepts, Overview of the concepts of vNetwork Distributed Switch.

• How to list the security settings for distributed virtual switches and distributed virtual exchanges

  Is there a .pl can I use to list the security settings for distributed virtual switches and distributed virtual exchanges?

  parameters such as

  Mode promiscuity (license /reject)

  Mac address changes (license /reject)

  Allows the transmission of forged (permitted /reject)

  Thank you

  Fred

  Take a look at this article from blog for the script and details - http://www.virtuallyghetto.com/2011/12/retrieving-information-from-distributed.html

• Switch Standard virtual and virtual distributed switch

  How to migrate the virtual machine to switch vNetwork Standard to a vNetwork Distributed Switch, where can I get more information? How to set up?

  Thank you

  I think that's what you're looking for

  It's pretty easy actually, I have not you, but once I had to manually migrate the 120VMs to one portgroup to another, now, it is quite easy to use GUI version 4.

  Migration of virtual machines between vSwitch or exchanges of vDS or dvPortgroups

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

• Switch std to distributed switch migration.

  I have 2 Dell T710 with 6 NIC cards.

  I configured on the 4 standard vSwitches.  Each standard vSwitch is connected to a physical network adapter card.

  I have a vSwitch for manage management, one for vMotion for iSCSI and one for traffic from the virtual machine.

  The reason I set up is to put the vMotion, iSCSI on a different NETWORK card and so another port on the physical port in order to get the maximum flow.

  Now, when I tried to configure a switch to vDistributed.  I was reading this document from vmware (http://www.vmware.com/files/pdf/vsphere-vnetwork-ds-migration-configuration-wp.pdf) and there seems to be all the VLAN based.  In the vDistributed switch, I create the port group, and then associate the group the dvUplink ports and the dvUplink will map to the physical NETWORK adapter on the host.

  I don't seem to find an option to specify the Group of ports on the dvPortGroup if East of vMotion, management and/or iSCSI traffic.

  I'm missing something.

  Can someone tell me some good practices of switch vDistributed?

  Thanks for the information and have a good year.

  Anthony.

  ATC wrote:

  I don't seem to find an option to specify the Group of ports on the dvPortGroup if East of vMotion, management and/or iSCSI traffic.

  I'm missing something.

  You will need to go to the host tab configuration, management network, distributed switch - then "virtual cards" - the Vmkernel ports for the distributed switches.

• VSS migration to virtual Distributed Switch configuration

  Hi all

  I am trying to wrap my brain around that and just run into a few problems actually make things work. Please bear with me, I will try and describe the environment that I have and what I'm trying to building with like jargin little I can.

  My current vmware environment consists of 3 hosts vsphere 4.x and about 6 different subnets. My primary host vSphere is home to the largest part of the virtual machine and manages 5 different subnets connected to each of 5 virtual switches separated with 1 assigned to each NETWORK adapter. Also, there is a switch of kernel VM with a connection to my NetApp iSCSI. The other vSphere hosts are simple enough, the two are connected to subnet 1 with a virtual switch for it and a switch of kernel VM with a connection to the NetApp iSCSI.

  Each subnet in my lab is managed/break through the VLANS on Cisco devices, so I saw that it had to assign any settings VLAN since the power of VMware.

  If you refer to the VMWare vNetwork Distributed Switch: Migration and vmware Configuration guide, I am trying to migrate a seup similar to this:

  

  However, I'm running issues when you try to get the int hosts a vDS configuration. I could create a vDS for my root subnet, add one of my hosts vSPhere and migrate the virtual machine to the new port group in this vDS. The Service console as well as the VMKernel remain virtual switches on the host and I can't understand how these migrate to a vDS host without lose the connection.

  I'm asssuming based on the number of subnets that I manage between hosts, I'll finish with about a 5-switch vritualDistributed for subnets, each with at least 1 card a vSphere host physical NETWORK link up to the appropriate subnet. In addition to this, I'm assumining I'll need to create a vDS for the Service console and VMKernel (iSCIS) traffic. The Service Console are on the same subnet, some VM most residence on that subnet, separate VSS was created on the hosts to manage separate traffic.

  Any help anyone can provide on how to create vDS for SC/vmk traffic and get the associated host migrated to which would be very useful. As I said I was able to create 1 vDS and add a host computer via 1 uplink NIC with the virtual machine, but nothing beyond that seems bad connection.

  Feel you please free to ask for additional details, I know it's a lot and maybe a bit confusing. Thank you.

  -Bryan

  Hello

  If I'm correct, when the host is added the vDS and the creation of the vDS Service Console, I have to select an unused NIC and migrate the SC existing to the new group of port... or should I add a second SC for the VSS by using a NETWORK card available and who migrate to the new vDS?

  Yes, select an unused physical nic so that you have a physical nic connected to the VSS and the other to connect to the uplink of vDS group and migrate the SC. existing if you have several hosts, vMotion all VM and test to see if the migration without distruption, also works to keep details of the ILO ready incase you need to connect to the console of the server.

  This is a very good book white http://www.vmware.com/files/pdf/vsphere-vnetwork-ds-migration-configuration-wp.pdf that provides detailed information about the migration.

  All the best.

  Kind regards
  Arun

  If you have found this or other useful information, please consider awarding points to 'Correct' or 'useful '. Regards, Arun VCP3/4, HPCP, HP UX CSA http://kb.vmware.com/

• NSX design with cisco UCS/fabric interconnects and Nexus switches

  Hi Experts

  I am new to NSX design and deployment and working on a project. We deploy NSX for applications of level 4 (web, app, db, DC). I use logic, DLR, ESG and DFW switches. I next we intend to use roads static confusion..

  1. do we cover all the VLAN from the virtual to the physical environment? for example mgmt VLAN, level vlans(web,app,db), vxlan transport vlan or it should be only a VLAN specific?  which means would be I have set all the VLANS in environment NSX in my physical switching environment?

  2 vds? don't we create not only 1 vds initially during the deployment of vcenter or more? Should we take any special consideration while deploying to the deployment of the NSX?

  3 static routes - we configure static routes on the DLR and the GSS? Should I use the default routes upstream? on the physical router should we be routing all subnets from virtual environment to the GSS.

  4. where and who should create virtual machines? Via vCenter or before the deployment of the nsx NSX?

  5. we have a level of domain controller. Should it be part of 3 or separate applications with allow any any rule on DFW?

  Thank you

  Sam

  (1) the VLANs which exist for physical Machines span the logical switch VXLAN NSX in the following cases:

  • If the current deployment there are physical Machines in the same Vlan and subnet IP with Virtual Machines. If this common Port Vlan group is migrated to a switch logic VXLAN Backed port group and not possible to change the IP addresses of the virtual machines, and then a bridge DLR (Distributed logical router) works as the conversion between Vlan physical and virtual VXLAN
  • If Conversion of P-to-V of the physical Machines continue on this Vlan

  VLAN which cover only the virtual machines or virtual local networks which cover only physical Machines must not be delayed.

  (2) for the deployment of the NSX, there may be more than 1 dVS or only 1 vDS according to the design. There may be another type of traffic other VXLAN base of virtual machines such as backup, storage, VMotion and the overall design, management, best practices apply here as well.  A requirement of the NSX is a common VDS that spans the entire Cluster. For each Cluster, this "common VDS' may be different. Yet once this VDS maybe a separate VDS dedicated VTEP or VTEP features functionality can be added to the existing VDS. It may be best to separate the VTEP vDS.

  (3) for the DLR, a default gateway is usually sufficient. If static routes are used, the GSS must then drive by default upstream and the static routes with the next hop of the DLR downstream for the subnets in the subnets IP VM logical switch. On the physical router static route to the VM, but also DLR - ESG logical subnets Subnet switch is required. Management of static routes is easier if route summarization is possible, or if necessary, close to the IP subnets, so it may be a good idea to use the dynamic routing such as Ospf or BGP protocol. There are also features of IP address management in Vrealize and other IPAM solutions if Automation is necessary for large and dynamic environments.

  (4) NSX has no functionality in the creation of the VM, it only creates Services network such as switches, routers, Firewalls, Load Balancing. The creation of the part VM continiues the same way as before. A point to note is maybe the logic is created appear as VXLAN named port groups on the VDS. NSX Manager creates groups of ports on the VDS, the only difference is that the name includes VXLAN. The virtual machine is like before added to this group of VXLAN Backed Port settings, or added to the logical switch from NSX Manager interface that appears again as a Plugin for VCenter. VCENTER is so point to create virtual machines and add these VMs to the logic is.

  (5) level of domain controller can be a separate layer, or other third party, may be preferable to upgrade separated except 3 applications. Usually, it's the same design without NSX. dFW rules can help protect the domain controller with allowing only ports of the virtual machine or physical Machines being admitted. dFW rules can apply to VXLAN based logical switches NSX so that VLAN based DVS Port groups because it's the kernel module.

• Need to obtain information from a host distributed switch

  Hi all

  I want to get information distributed switch of a host.

  With the script below am able to get the name of the switch, network cards added to the dvswitch and its status.

  $report = @()
  foreach ()$sw in (Get-VirtualSwitch -distributed)) {}
  $uuid = $sw. ExtensionData.Summary.Uuid
  $sw . ExtensionData.Config.Host | %{
  $portStates = $sw. ExtensionData.FetchDVPorts ($null)
  $esx = Get-View $_. Config.Host
  $netSys = Get-vue $esx. ConfigManager.NetworkSystem
  $netSys . NetworkConfig.ProxySwitch | where {$_. Uuid -eq $uuid} | %{
  foreach ($pnicSpec in $_. Spec.Backing.PnicSpec) { }
  $row = "" | Select Host, dvSwitch, Teddy bear, PortLinkUp
  $row . Host = $esx. Name
  $row .dvSwitch = $sw. Name
  $row . PNic = $pnicSPec. PnicDevice
  $row . PortLinkUp = () $portStates | où {$_. Clé - eq $pnicSPec. UplinkPortKey}). State.RunTimeInfo.LinkUp
  $report += $row
  }
  }
  }
  }
  

  $report

  
  

  But I would like to get the information of physical switch (switch. physical name and port information of each vmnic connected to this host please help to get the same thing.)

  Note:

  CDP information are enabled.
  

  Since you have the natachasery, it would be a matter of using a script like Re: how to get the CDP in Switch Cisco values? for the information of the COP.

• How to remove ESXi host of Distributed Switch

  3 Cluster DRS - 1 x physical, 2 nested nodes in a LAB environment

  I need to downgrade a 6.0 U2 ESXi host and replace it (from ESXi nested in Physics). I am trying to remove the host from a distributed switch, but it seems that I can't do that until I remove it from the Distributed Switch. I can't remove the VMkernel group management ports that prevents me to remove the host from the Distributed Switch. Any suggestions? I guess that I need that migrate to a Standard switch first?

  I am connected to the ESXi host through vSphere Client, migrated the group management to a Standard switch ports, then I was able to clear the host of the distributed switch. I could then remove the host from the Cluster.

• Distributed switch

  Assuming that the new host that is added to the existing cluster is the same server, I have a question:

  If the cluster is using distributed switch, how to set up the new host to use the existing configuration of distributed switch?

  Once the host and the network/uplinks are correctly configured, simply follow steps shon in Add hosts in a Distributed Switch vSphere

  André