phys ESX 5.1 switch

Similar Questions

• ESX host cannot ping the default gateway.

  Hi Experts,

  I have connected ESX hosts to switch cisco as well by the ILO and other ports.

  Cisco switch configuration;

  int gig 1/0/21 and 1/0/13 gig and gig 1/0/14 are configured as access ports because they are carriers/tagging vLan as a 306.

  Cisco switch, I can ping the ip address of the ILO, but I can't ping the IP address management and vice versa.

  IP Managment

  10.197.204.10

  255.255.255.0

  10.197.204.1

  VLAN 306

  Attached the screenshot shown in the diagram.

  your help will be appreciated.

  Concerning

  Don't know what it is, but there must be something simple that you miss

  Let's go through each step of configuration for both ESXi network connections (ILO work already, so we do not touch).

  Check the configuration of switch port physical interface GigabitEthernet1/0/13 and 1/0/14.

  switchport access vlan 306

  switchport mode access

  spanning tree portfast

  Only connect the cable network for vmnic0 to host and make sure what vmnic0 presents itself as 'connected' in the DCUI

  

  Make sure the VLAN ID is empty.

  

  Make sure you then the IP settings are correct (IE without typos,...) and restart the management network from the main menu.

  André

• Switch to review mode licenses

  Hi, I use VirtualCenter 2.5 - U1, which manages 6 host ESX 3.5 - U1. I have license activated with license running on the host of VC server. All of my ESX hosts get their license ok Server license. I am running Enterprise Edition. When I am connected to VC via my VI client and I click on Administration-> VirtualCenter Management Server Settings-> license server, what would happen if I ticked the box "Evaluate VirtualCenter Server"? Would my VC server and ESX hosts just switch to mode eval 60 days without disrupting operations?

  George.

  Would my VC server and ESX hosts just switch to mode eval 60 days without disrupting operations?

  No....

  They would turn to the days stay (you have 60 days-evaluation in total).

  André

• 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={$_}}  }}
  

• With the help of VLANS and VLAN Tagging is not working / no connection

  Hello

  I m trying to configure a VLAN between some virtual machines on ESX host 3.

  I want to do this way:

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

  I got 1 dedicated NETWORK adapter to each ESX host that is connected to a dvSwitch in which I configured a portgroup

  with VLAN ID 2121. I have configured each virtual machine to use this network.

  When I put the virtual machines on a single host, they are able to communicate.

  When they are placed on different hosts they are (if the VIRTUAL LAN is enabled on portgroup) not able to communicate.

  So I m assuming it must be a problem in the config NIC on the ESX host or switch.

  I m using a HP2910AL on which I activated mode trunk for each port that is connected to a NETWORK card with

  the dvSwitch/Portgroup I try to use for the vlan. In the hp switch, I have a default VLAN with ID 1 where

  the Ports are marked not signposted. I install a second VLAN on the switch with ID 2121 in which I scored

  This tag ports.

  Is there something else to do - perhaps side ESX host?

  I tried changing the settings as "forged transmission-> allow ' on portgroup and I found other things

  in the web, but always without success.

  Kind regards

  Patrick

  Were you referred to this guide? :

  http://CDN.ProCurve.com/training/manuals/2910-ATG-Feb09-2-VLAN.PDF

  "show vlan ports" would be my next check to make sure that you have connected to your ESXi host 3 ports in the vlan 2121.

  As Duncan has said if you have a VLAN ID on the portgroup in the vSwitch and you have the port on the pSwitch as trunk not acess and VLAN ID is allowed on the trunk port pSwitch you should be ok.  Just to clarify the trunk is 802. 1 q No 802.3ad.

  The reverse is not VLAN ID on the portgroup vSwitch, use coelio on pSwitch with VLAN ID.  Limited pSwitch port to a VLAN, this may be ok for you?

• Migrate to vSphere/ESX4 host of the no routed private network to the public network mgmt mgmt

  Hello

  I'm looking for advice on the best method to move guests to U2 ESX4.0 of a private network that is not routed on one vlan routed public. It is complicated by the requirement to keep all the VMs on the server farm running with no downtime / failure. Is this possible?

  Our farm config is:

  1 x VM VC4 (32 bit) with two network adapters:

  -1st NETWORK adapter connected to the vlan routed public (193.x.x.x)

  -2nd NETWORK card that is connected to the private network not routed for mgmt/service console all ESX hosts. (10.0.0.x)

  -Files local host on the vCenter server for DNS resolution of the ESX hosts on private non-routed network mgmt

  10 + ESX 4.0 U2, console svc host 1, console svc 2 and all about vmotion network private not routed.

  -The local Hosts file on each ESX host facilitates DNS on the network of mgmt ESX host.

  * We intend to keep the vmotion/vmkernel on the private vlan not routed

  Here are the steps that I have written so far:

  1 Vmotion all VMs off ESX host and switch to Maintenance Mode

  2. unplug and remove host ESX VC

  3. use VMware KB Article: 1022078 to change the address on the service console

  4 update the hosts file on the VC and all ESX hosts with this ESX host's new public address

  5 re - add a host to the CR

  Q: I would be then able to vmotion between virtual private machines NET ESX host on this new net public ESX host?

  All suggestions welcome.

  Hello

  To be honest, I have not fallen on this article before, except to say that a number of occasions I've reviewed or renamed hosts. When I do, it always works.

  I usually restart the agents with the order you suggest just to feel safe.

• Restrict the IP comments/VMS

  Hello

  I'm putting in place two virtual machines on the same subnet (say 10.10.10.0/28) and I want to assure you that VM1 can only use IP 10.10.10.2, while VM2 is limited to IP 10.10.10.3 (comparable to an IP address to the MAC on a physical switch port restriction).

  I see several vSwitch parameters, but it's all the layer 2 (MAC promicious mode etc.). I'm looking for is some kind of restriction of layer 3 (IP for MAC). Anyone know how?

  Bravo and thanks,

  Manual

  I don't think it can be done in ESX using standard switches. Maybe you can use DHCP reservations to work around the problem, although it would not give you security that makes 802. 1 x.

  To get the functionality you need, you should probably use the virtual cisco nexus switch.  See below:

  http://www.Cisco.com/en/us/prod/collateral/switches/ps9441/ps9902/data_sheet_c78-492971.html

  Kind regards

  Ian

• Configure load balancing NETWORK for Exchange 2010 - unicast or multicast

  Howdy,

  We are in the process of setting up CASE on VSphere and want to configure NLB. The documents I've read talk about using unicast or multicast modes. Unicast requires more setup server-side and multicast requires additional configuration on the side network. A mode is better than the other?

  Any help would be appreciated!

  Lily, multicast is generally the way favorite due to changes to the requirements to the vSphere host, when you use the multicast mode.  The necessary change disables ESX update upstream switches when a virtual machine is online.  Which means that the switches know where VMS obliging NLB to flood the switches, which is design as well as NLB works.  One effect of this is that the switches will also not learn changes due to vMotion or HA events that extend the time it takes switches to learn that the new location for a MAC address.

  Multicast road requires a static entry in the network layer and does not have the effect shown above.

  -alex

• Shutdown for Lab Manager

  We are conducting a data center power down and I would like to confirm my judgment for Lab Manager procedure:

  Stop order:

  1. Shutdown VMs LM
  2. Virtual routers (for closed configurations) stop by VC
  3. Stop VMwareLM-ServiceVM (by distributed switch) by VC
  4. Stop LM Server (VM, but not running on the ESX host cluster managed LM)
  5. Shutdown LM managed ESX host
  6. Shutdown VC Server

  Boot order:

  1. Power on server VC
  2. Power on managed LM of the ESX host
  3. Power on LM Server
  4. Power on virtual LM VMs, routers & VMwareLM-ServiceVM by VC

  My questions:

  Are the steps in the proper order?

  What I have to cancel the deployment of my configurations or they may just be in an engine out of State? I like to keep the configurations deployed to maintain external if possible IP addresses.

  just closed down going also to extend the process of closing, it would be: ESX hosts SAN switch SAN storage reverse order to start upward.

• Which are el correcto para poner una DMZ en ESXi procedure

  Hola y Buenos dias, voy a esplicar el problema Québec me tengo:

  Tendo con su ESX virtual switch varios para cada cosa, uno para el trafico vmotion, otro para las maquinas office y ahora quiero poner otro para the DMZ.

  Hasta ahora tengo UN servidor how in the DMZ con Centos is vmware server y unas maquinas ahi.

  Esto quiero evidence e include VM storage infrastructure en estas y el vcenter para disponer seguridad of poder arrancarla on different equipos ante material fallos y poder hacer esos servidores backup (cosa than hoy por hoy no tengo).

  Antes montarlo in toda lo voy a poner in 1 ESX infrastructure con una tarjeta fisica conectado al del cortafuegos switch y al virtual switch nuevo para DMZ Québec creare in el host.

  Por mi parte no tengo none duda esta are the best config (una tarjeta fisica del esx al virtual switch that is in the DMZ as tenemos rango) y Aquí las maquinas than estar in the DMZ has.

  El problema viene desde womanhood that encarga las comunicaciones y el cortafuegos, what no tienen claro Al poner una pata lan en the dmz (of hots ese) y el resto in the LAN without tengamos problemas transfer u otros temas are what counted as estoy July una Máquina as no pasa por el cortafuegos.

  Yo (con put essential en comunicaciones) he intentado esplicarles as el trafico no to mezcla (el trafico Québec Hay virtual switch of the United Nations not to mezcla con el otro), y como voy a del virtual el switch connect to the dmz host, este switch solo esta conectado al cortafuegos, el trafico siempre pasa por ahi.

  Su miedo is the mentioned above, what habramos an as no pasa por cortafuegos el camino.

  Hay algun documento explains that su miedo're injustificado para poder demostrarselo yo.

  Siento chapa UN saludo thanks

  Hola irasines,

  you than arrows aconsejo a vistazo al siguiente pdf of vmware:

  http://www.VMware.com/files/PDF/dmz_virtualization_vmware_infra_wp.PDF

  Must you sea ayuda

• Best practices for managing strategies of path

  Hello

  I get conflicting advice on best practices for managed paths.

  We are on version 4.0 of ESXi connection to a HP EVA8000. Best practices guide HP recommends setting the strategy of railways handle on Round Robin.

  This seems to give two active paths to the optimized controller. See: http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA1-2185ENW.pdf

  We used certain consultants and they say that the best practices of Vmware for this solution is to use the MRU policy which translates a single path to the optimized controller.

  So, any idea what good practice is best practice? Does make a difference?

  TIA

  Rob.

  Always go with the recommendation of the storage provider.  VMware recommendation is based on the characteristics of the generic array (controller, capable ALUA failover methods, etc.).  The storage provider's recommendation is based on their performance and compatibility testing.  You may want to review their recommendations carefully, however, to ensure that each point is what you want.

  With the 8000, I ran with Round-Robin.  This is the option of creating more robust paths available to you from a failover and performance point of view and can provide performance more even through the ports on the storage controller.

  While I did of the specific tests/validation, the last time that I looked at the docs, the configuration of HP recommends that you configure each IO to the ports in the switch configuration.  This adds the charge to the ESX host, the switch to other ports, but HP claims that their tests showed that it is the optimal configuration.  It was the only parameter I wondered in their recommendation.

  If you haven't done so already, be sure to download the HP doc on configuring ESX and EVA bays.  There are several parameters that you must configure the policy path, as well as a few scripts to help make the changes.

  Virtualization of happy!

  JP

  Please consider awarding points to useful or appropriate responses.

• New Test for SAN environment

  Hello

  I want to configure a test environment of SAN. Currently, I have 2 ESX host and switch San Q logic and a machine with 2 TB of storage in this regard. I just want to test if I could create a SAN storage and I both ESX hosts point to storage using the fiber cable. Is there an inexpensive way to do it? I know openfiler using iSCSI, but I want to test using fiber channel.

  Thank you

  Download and test with the V6 DSS 4550 version and when you create a set of logical volumes CF the size block to be 512K and then go to the nursery to target CF in the graphical interface of the Configuration tab make sure to set the Qlogic FC HBA mode target since the GUI configuration > Fiber Channel then restart the system. You don't need a Swtich CF so you don't want that you can directly connect the FC HBA to each other. Hope this helps and thanks for watching Open-E!

• iSCSI and LACP

  I have a 4 ESXi host with two natachasery each assigned to a VMKernel Multipathing alternating iSCSI port.

  These two natachasery is connected to a Cisco switch and in turn connected to two network cards on my iSCSI host. The iSCSI host has two exposed objectives (1 for each NETWORK adapter)

  Y at - it a performance edge switch with LACP configuration-> ESX configuration and switch with LACP iSCSI target?

  Thank you

  Yes, the physical switch both the vSwitch maintain a table which connection will come out which interface.  Until there is a failure of interface, the same source IP will never talk on the same physical NETWORK card to the same destination IP address.  It is one of the mechanisms that ESX uses internally to avoid the loop.  Since the vSwitch does not participate in spanning tree protocols, traffic has the same NETWORK card out it came, otherwise, you are potentially creating a loop.

  vExpert

  VMware communities moderator

  -KjB

• with vSphere and Dell MD3000i iSCSI design

  I installed a server ESX 4 (the first of three for this cluster), and a SAN Dell MD3000i iSCSI connected through two switches Dell PowerConnect 2816.

  Now I read the VMware 'iSCSI SAN configuration guide', and I wanted to just make sure I did the design correcly.

  I have connected a Teddy ESX (vmnic1) to one of the pSwitch and another (vmnic5) in the second. This pSwitch SAN iSCSI ports are connected, so that one of the switches carry the 10.10.10.x subnet and the other the 10.10.11.x (see IP plan below)

  The two natachasery have a vSwitch each (a do not share), a portgroup each and are configured on different subnets, IP (see attached screenshot)

  Plan of intellectual property:

  Port iSCSI-10 group (VMkernel): 10.10.10.1

  Port group iSCSI-11 (VMkernel): 10.10.11.1

  0-0 SAN controller: 10.10.10.10

  SAN 0-1 controller: 10.10.11.10

  Controller 1-0 San: 10.10.10.11

  SAN 1-1 controller: 10.10.11.11

  By using this configuration, I could see four different paths for each LUN. and I was able to make the ESX Server will switch to different switches/controllers as I unplug the vmnic1 network cables and vmnic5, one at a time.

  Then I found the section on 'esxcli' configuration guide and multipathing configuration, which I carried out in accordance with the instructions ("esxcli swiscsi nic add - n vmk0 d vmhba34" and "esxcli swiscsi nic add - n vmk1 vmhba34 d ')

  Now I have eight different paths for each logic unit number, three of whom are 'Active' and an 'active (i/o)' (see my screen attached the capture).

  So, my questions are:

  1. the eight paths to each LUN really normal in designs of iSCSI?

  2. is my vSwitch/Teddy/pSwitch correct design choices?

  Thanks in advance!

  / Anders

  @hennish,

  As long as your new design continues to meet your needs of failover and workload, your infrastructure design should be fine.

  But you might want to take a look at this design Dell. In particular, step 12 that configures multiple paths in round-robin policy using the VI GUI client, for

  Each LUN exposed to the ESX Server. This allows balancing on two

  Active paths to the LUN. After completing this step, you should see2 "IO Active" paths.

  Kind regards

  KongY@Dell Inc.

• Problem with networking when having multiple virtual machines on a single host

  Since the implementation of ESX 3.5i server on PowerEdge 1850 Server I had network problems. It took a large upstream of the violin - do not do something specific - but finally I could persuate a VM to talk to the outside world.

  Virtual machines have always been able to ping other virtual machines and physical NETWORK card to the host (with a static IP address only), however with a bit of deactivation/activation etc I could possibly get it connected. I have exactly the same symptomsusing the two Windows XP and Redhat, both with VM Tools installed.

  If big, I can get the virtual machines connected, *however * every time I managed to connect a computer to the outside network, she will knock off either a return to the State where I can ping only the other VMs and Teddy.

  I tried them in different port groups as well as in different vSwitches with a separate Teddy, but exactly the same problem.

  I thought it was just my ignorance, however after thorough reading and wasting time trying different combinations, I started to think this is a hardware incompatibility or an ESX installation problem.

  Please please please, if someone can help solve the problem, or diagnose if my suspicions are correct.

  I enclose my last combination of configurations!

  Thanks in advance.

  Run 'show port-security' on the switch and see what you have.  You can also view the current configuration of the port connected to an esx.  A switch will remove any doubt relating to port config differences type.

  -KjB

  VMware vExpert