HostProfiles and vSwitch0

Similar Questions

• vMotion and vReplication on a crossover cable?

  Hello

  I am trying to configure 2 ESXi6 hosts physically connected to each other using cables ADJUSTABLE. I want to put in place so that vMotion and vReplication traffic happen using the ADJUSTABLE cables. This is my setup:

  vCenter - 192.168.130.0

  vReplication - 192.168.130.5

  ESXi 1:

  NIC0 - vSwitch0 - vmk0 (192.168.120.50 - Mgmt traffic); default gateway - 192.168.120.5

  NIC1 - vSwitch1 - vmk1 (10.10.10.10 - vMotion, vReplication, Provisioning)

  ESXi 2:

  NIC0 - vSwitch0 - vmk0 (192.168.120.51 - Mgmt traffic); default gateway - 192.168.120.5

  NIC1 - vSwitch1 - vmk1 (10.10.10.11 - vMotion, vReplication, Provisioning)

  ESXi1 and ESXi2 are connected using the crossover on NIC1 cable and I tested ping using SSH between the two ESXis and it works very well on the network 10.10.10.x. I tried to select one of the virtual machines offline, then selected vMotion and it fails to approximately 23% with an error "Could not connect to host". Just as an FYI - without cross-over cables and the NIC1 on the two hosts I tested successfully with vReplication, so I know of files can be copied using the 192.168.120.x network.

  Can someone please help with this? Help, advice or comments are appreciated.

  Thank you

  Sau

  OK figured it. It's the firewall ESXi. I had to activate the 10. range in the IPS allowed for NFC 902. Looks like it's using the cross on connection. Thank you for all your help.

  -Sau

• core VM and the consolidation of NETWORK cards

  Hello

  By default, VM network ports group is associated with two vmnic and the management ports group is connected to one vmnic. Is there a reason for this?

  

  This isn't really a default configuration.

  By default would be vmk0-> vSwitch0-> vmnic0 - just an uplink to the default vSwitch.

  It seems that someone is gone, has added the vmnic1 to your vSwitch0 and configured the active adapters / Eve / unused. To clear the reason for this, you have to love the person responsible for this change.

  Could also be a config after installation automatically, depends on how you installed your ESXi host.

• Options grayed out after that migration vSwitch0 vmk0 to distributed network switch

  I have a bunch of ESXi 6 guests, where I would like the default vSwitch0 to a vDS management interface. However, it seems that the management network gets screwed more or less of this operation

  First I tried to simply migrate the physical interface and vmkernel to vds = no chance (resets the form configuration time to hosts)

  Then I tried to connect a NIC seconday to the same switch, adding as a management console interface, make two interfaces marked as management interfaces. The uplink of vSwitch0 is replaced by the new interface and the vds is mapped to the original management interface. From this point, I can migrate vmk0 to the distributed switch and remove the extra card. All good, at least at first glance. The army continues to communicate with vCenter and so on. However, return to the console options to "Network adapters" and "VLANS (optional)" are grayed out. The only way I managed to get back them is again a reset to the default settings of the management network.

  After som test front and rear, it seems that these options disappear as soon as vm0 leaves vSwitch0?

  Any ideas how to solve this problem?

  The army continues to communicate with vCenter and so on. However, back to the console options for "Network adapters" and "VLANS (optional)" are grayed out. The only way I managed to get back them is again a reset to the default settings of the management network.

  I guess that's the expected behavior, because once your vmk0 has been migrated to vDS, now the vDS control plan which is with vCenter server will allow you to change these settings as network card and VLAN ID etc.

• management network and vCenter

  Hello

  Should I put the vCenter on the same network as the hospitality of ESXi management?

  Now I have standard vSwitch0 configured with vmkernel port = vMotion vmkernel port = network management... im wondering if I should also create v vmnetwork for example the Mgmt network name as seen in the photo.

  

  I've never had problems, but I assume that from a security perspective, there is more to routed traffic otherwise on this subnet.  I have been a long time and never considered that it was essential.  In any way is ok, but I never ran on the management network and personally do not feel the need to put it out there.

  What happens if you have several subnets management? IE in my case that we have a different management of networks for some of our groups and therefore VCenter was impossible on both.  I'm surprised they put this in the documentation.

• esxi Network Setup 4 and esxi 5.5 the same

  Hello

  We have a customer with the following network configuration (see picture). They run ESXi and vCenter 4.0.

  We have added a new separate system with ESXi and vCenter 5.5 and to set up the network, the same.

  My question is this service console, I can't to be able to set this up, it's that are not part of ESXi 5.5?

  If you see the other image, I configured 2 one for management and one for vMotion VMkernel Port, they will be on the same network.

  Would that be correct?

  I don't mind not the network adapters are not connected again... and another thing must use active active alle 4 cards?

  Old configuration

  

  New configuration

  

  Since the release of vSphere 5, he didn't there no Service Console more... the management can be performed via VMkernel port with active management traffic.

  About vmnic design, my recommendation is:

  vSwitch0:

  For vMotion PortGroup - vmnic0 Active and standby vmnic3

  PortGroup management - vmnic3 Active and standby vmnic0

  vSwitch1:

  PortGroup for VMS - vmnic1 Active and active vmnic2

• Report of VSS and vmhost adapter attached to each vswitch

  Hello

  I have several esxi host, each host has two VSS and 4 physical network adapters

  I want to get a report that shows the esxi, vswitch, physical nic host

  for failure

  esxi1 vswitch0 vmnic0

  esxi1 vswitch0 vmnic2

  esxi1 vswitch1 vmnic1

  esxi1 vswitch1 vmnic3

  Try like this

  foreach($esx in Get-VMHost){  foreach($sw in Get-VirtualSwitch -VMHost $esx -Distributed:$false){    $sw.Nic | Select @{N="ESXi";E={$esx.Name}},      @{N="Switch";E={$sw.Name}},      @{N="Nic";E={$_}}  }}
  

• ESXi 5.5u1 added iscsi storage adapter - reboot and now vSphere Client could not connect to "my ip" an unknown error has occurred.  The server could not interpret the customer's request.  The remote server returned an error (503) server unavailable

  I have not yet connect to an iSCSI target device.

  I can ping my host

  when I open http:// "hostip" in a web browser, I get a 503 service not available.

  restart the host gets me nowhere.

  SSH opens somehow, but can not connect

  Console seems OK

  vSphere Client can not connect

  If I reset to the default values of the console it is ok, but when I reconfigure the host, this error will be returned.

  I tried to reinstall from DVD

  I'm completely corrected to date via SSH esxcli

  This happens on both my hosts, although they are almost identical Lenovo thinkserver TS140s with broadcom 10Gig NIC and intel NETWORK card integrated

  It almost always seems to happen the next time I reboot after enabling iscsi support

  The only weird thing I have is that my Integrated NIC is a processor intel 217's and I have to use a special VIB so that it can be used in ESXi

  Customer's winning 8.1

  Here is my installation notes

  Install on USB/SSD stick with custimized ISO i217 NIC driver, reset the configuration and reboot

  Management NIC set to NIC0:1Gig

  IP management: hostIP/24 GW: my gateway

  DNS:DNS on windows vm1, vm2 Windows dns

  HostName:ESXi1.Sub.myregistereddomainname custom DNS Suffixes: sub.myregistereddomainname

  Reset

  Patch to date (https://www.youtube.com/watch?v=_O0Pac0a6g8)

  Download the VIB and .zip in a data store using the vSphere Client

  To get them (https://www.vmware.com/patchmgr/findPatch.portal)

  Start the SSH ESXi service and establish a Putty SSH connection to the ESXi server.

  Put the ESXi server in maintenance mode,

  example of order: software esxcli vib install /vmfs/volumes/ESXi2-2/patch/ESXi550-201404020.zip d

  Re install the Intel 217 NIC driver if removed by patch

  Change acceptance ESXi host sustained community level,

  command: esxcli software - acceptance-level = CommunitySupported

  Install the VIB

  command:esxcli vib software install - v /vmfs/volumes/datastore1/net-e1000e-2.3.2.x86_64.vib

  command: restart

  Connect via VSphere client

  -Storage

  Check/fix/create local storage. VMFS5

  -Networking

  vSwitch0

  Check vmnic0 (1)

  Network port group rename VM to the 'essential '.

  Rename management group of network ports for management of basic-VMkernel traffic.

  -Configuration time

  Enable NTP Client to start and stop the host. ntp.org set 0-3 time servers

  DNS and routing

  Start the virtual machine and stop

  -enable - continue immediately if tools start - stop - prompted action Shutdown - the two delay to 10 seconds

  Security profile

  Services

  SSH - startup - enable the start and stop with host

  Cache host configuration

  -Properties to start SSD - allocate 40GB for the cache host.

  Flashing warnings SSH:

  Advanced settings, UserVars, UserVars.SuppressShellWarning, change from 0 to 1.

  Storage adapters

  -Add - add-in adapter software iSCSI

  I think I saw that I was wrong.  In fact, I applied two patches when only suited. I started with 5.5u1rollup2 and then applied the ESXi550-201404001 and ESXi550-201404020.  Strangely I did not t o had problems until I worked with iSCSI.

• The VirtualSwitch and Virutalport group details

  Hello

  I'm trying to collect each host vSwitch details information and the port configured in the cluster group.

  I go and get the result by using the onliner like that... (get-vmhost | get-virtualswitch | get-virtualportgroup)

  But please can someone help me get it in report as below

  ClusterName ESXhost vSwitch exchanges

  X x 1 vSwitch0 1, 2, 3, 4, 5

  vSwitch1 6, 7, 8, 9, 10

  I am sure, that such a request could have answered already. But I could not do in the search.  Thanks in advance.

  I combined the name of virtualportgroup and the VLanId, you will get something like "pg1-123", where pg1 is portgroupname and 123 is the VLanId.

  foreach($cluster in Get-Cluster){    foreach($esx in Get-VMHost -Location $cluster){        Get-VirtualSwitch -VMHost $esx |        Select @{N="Cluster";E={$cluster.Name}},            @{N="ESXi";E={$esx.Name}},            @{N="vSwitch";E={$_.Name}},            @{N="Portgroups";E={[string]::Join(',',(Get-VirtualPortGroup -VirtualSwitch $_ | %{"$($_.Name)-$($_.VLanId)"}))}}    }}
  

• PowerCLI and host of profile Configuration selections

  All,

  When you use the host profiles, we must be able to check and uncheck the settings.

  In this way, we can disable configurations to be applied or verified compliance.

  (in the Client vSphere, made a right click the hostprofile / toggle the profile Configuration)

  
  But now I want to do with PowerCLI

  Someone at - it ideas?

  Thank you and best regards,

  Harold

  https://Twitter.com/hharold

  I'm afraid that this currently not available through PowerCLI cmdlets.

  But if you look at the different sections in a hostprofile (see also your help with Host Profiles and necessary PowerCLI)

  you will notice that each of these components (authentication, Firewall,...) have an Enabled property.

  With this property and the UpdateHostProfile method you can enable/disable specific components.

  Let me know if you need a sample?

• Help with Host Profiles and necessary PowerCLI

  Hello

  I have 2 questions about using PowerCLI for edit vSphere Host Profiles:

  (1) how can I clone a host profile, using PowerCLI?

  (2) how can I change the host profiles, using PowerCLI, update these settings?
  (a) name of host - DNS configuration - configuration networking
  (b) setting up authentication - setup of Active Directory - domain name

  
  Thank you!

  Kind regards
  Harold

  (1) there, in the current version no cmldets to clone a hostprofile.

  But you can use the API. Something like that

  $hostProfileName = "MyProfile" $prof = Get-VMHostProfile -Name $hostProfileName 
  
  $profMgr = Get-View HostProfileManager
  $spec = New-Object VMware.Vim.HostProfileCompleteConfigSpec $spec.Annotation = $prof.ExtensionData.Config.Annotation$spec.ApplyProfile = $prof.ExtensionData.Config.ApplyProfile$spec.CustomComplyProfile = $prof.ExtensionData.Config.CustomComplyProfile$spec.DisabledExpressionList = $prof.ExtensionData.Config.DisabledExpressionList$spec.Enabled = $prof.ExtensionData.Config.Enabled$spec.Name = $prof.ExtensionData.Config.Name + " - COPY"
  $profMgr.CreateProfile($spec)
  

  (2) changing the settings in hostprofiles can be done, but the ILO requires a thorough knowledge of the workings of

  See for example my change of the root password in host and profiles of the host .

• ESXi and VLAN

  Hello

  I am facing a problem that you are trying to use VLANs in Esxi. Here's the scenario.

  A HP Blade as host.

  A HP GbE2c Ethernet blade switch.

  Allied Telesis switch connect the box to the network.

  Vlan1 - 192.168.1.0/24 (5 VM).

  VLAN2 - 192.168.2.0/24 (1 VM).

  5 virtual machines residing in the VLAN1 use vSwitch0 in a portgoup named VM network VLAN ID 0. The virtual machine in the VLAN2 uses vSwitch0 in a portgroup named VLAN2 with VLAN ID 2. The port in the Ethernet switch of the blade where the Esxi host is connected is labeled for VLAN 1 and 2 to pass. Also link ports Allied rising connection with switch blade are also marked for both VLAN.

  I'm doing something wrong? As soon as I change the connection port to the Esxi host to the switch blade for the tag, I lose the connections with all virtual machines (MY PC is in VLAN1 connected to the Allied switch).

  Thank you

  Can you change the VLAND 1 in vSwitch (port network VM group)

• Creation of vMotion, management and iSCSI

  Hi all

  I have doubts that I'd like to have some clarification.

  First vMotion and traffic management.

  I have two network cards. My question is, should I create IDE oucederomsurlesecondport VMkernel for each one (and adding the vMotion Option and management traffic) adding a different IP address for each and put the two in a vSwtich but the example; an active nic1 for vMotion and nic2 Eve and the management of the same traffic, nic2 active and standby nic1. With this, I have two different networks, but by using two NICs in case of failure.

  Or create a VMkernel and activate them both on the same VMkernel and put the two active network cards.

  What is the best choice, or the best performance?

  I have 6 guests on this cluster, so I need to do this in on the hosts.

  First I use QLOGIC

  The iSCSI side, should I use VMkernel Port binding? Or just use a normal VMkernel with my wihout VLAN iSCSI definition of any Biding VMkernel Port on iSCSI Software adapter?

  I have both running, but do not know which is the best way to get the best performance.

  Thank you

  JL

  Nice day!

  In summary, you should do something like that.

  vSwitch0 - Mgmt & vMotion

  ====================

  vmk0

  --------

  Management

  Uplink 1: assets

  Uplink 2: Passive

  vmk1

  --------

  vMotion

  Uplink 1: Passive

  Uplink 2: Active

  vSwitch1 - iSCSI

  ====================

  vmk2

  --------

  iSCSI traffic

  Uplink 3: assets

  If you only have an uplink for iSCSI traffic, you don't have to set up the binding of ports.  iSCSI ports is for the multipath.  If you only have one NIC for iSCSI, you cannot have MPIO.  You need two or multiple NICs or uplinks to the multipath.

  Now, for the management and the links of vMotion, I suggest using only an asset and a liability for each type of traffic.  Although vSphere 5 has the multi-NIC vMotion functionality, the idea of separating vMotion and traffic management is to separate vMotion and its important traffic in your management traffic bursts, which happens to include your traffic HA (also important).  You have certainly not * have * to set it up like that, but maintaining vMotion on his own physical link will keep walking on your management traffic.  In the case of a defective cable, I'm sure you would rather a cluttered link as no management or vMotion traffic.

  All the best,

  Mike

  http://VirtuallyMikeBrown.com

  https://Twitter.com/#! / VirtuallyMikeB

  http://LinkedIn.com/in/michaelbbrown

• ESXi 5.0.0 623860 and HP Procurve 2810 - 48G grouping/Trunk

  Hello

  I have a VMware ESXi 5.0.0 623860 host running two Windows VM well enough. The host material is an HP Proliant DL 380 G5 server.

  This host is Gbit Ethernet connected to a HP Procurve 2810 - 48G (J9022A) switch via two cables UTP Cat 5e.

  I want to configure an ethernet trunk using the two ports of the switch for fault tolerance and failover disaster link.

  I have telnet switch and configure ports like Trunk3 with TRUNK (not LACP) option as shown in this picture:

  

  To the ESXi side I'll to the vSphere Clent to Configuration-> networking-> vSwitch0-> properties-> Edit-> grouping of NETWORK cards, then set the option Load Balancing on "Route based on the IP hash" as shown in the following image:

  

  At that time, with or without restarting the software Procurve or ESXi host I ping the host and two virtual machines in it, but after about 10-15 minutes, I lose connectivity to the host (ping stops). So if I disconnect one of the UTP cables connect it again.

  I don't know if these are the good configurations for my goal, so any help would be much appreciated.

  Thaks a lot.

  OLIVEIRAS

  Hi Kamen (and oliveiras - in case you have not found a solution for this yet).

  I had the same problem recently with ESXi 5.1 and a HP switch and I fixed it by following this link:

  http://KB.VMware.com/selfservice/documentLinkInt.do?micrositeID=&popup=true&LanguageID=&externalID=1022751

• VSA and 10 GigE NICs

  In reviewing the VSA documentation, there is mention of the four 1GigE NIC - and our servers have only a 10 GigE dual port network adapter.  It will be a problem with VSA?  If so, is there a fix expected anytime soon?  Thank you.

  Hello

  1GigE four network adapters must provide redundancy network (Nic) and as much as I know this requirement will not change in the near future, support however 10 GigE network card is planned for a future release.

  With VSA 1.0, you can try to configure the network required for VSA manually with an uplink each vSwitch0 and vSwitch1 (see http://communities.vmware.com/docs/DOC-17393)

  change %ProgramFiles%\VMware\Infrastructure\tomcat\webapps\VSAManager\WEB-INF\classes\dev.properties

  Network.config = false

  Restart the "VMware VirtualCenter Management Webservices'

  Start the installation of cluster VSA.

  I have not tried myself so not quite sure if this really works and does not recommend this for production environment.