ESX 3.5 connected to SAN

Similar Questions

• Can the vcenter server that an ESX host is connected to determine through query of the esx host cmd line?

  Can the vcenter server that an ESX host is connected to determine through query of the esx host cmd line?

  All points will be awarded. Thxs.

  Look in

  /etc/opt/vmware/vpxa/vpxa.cfg
  

  you will see that the IP VCMS listed something like

  1.1.1.1
  

• Connection iSCSI SAN to ESXi servers

  Hi all

  I am trying to work through the iSCSI SAN Config Guide and get our three ESXi servers connected to our iSCSI SAN, but I'm confused about a few points.

  Background - Our production network is 172.16.10.x, our management network is 172.16.64.x and the SAN is on the 10.1.1.x network.

  The Guide says that the service console and VMkernel need to access the iSCSI storage - but in ESXi, there is no service console. Our network administrator (who has used 2 ESX) said just put in place two vSwitches and configuring each of them to VMkernel access, one on network 10 and the other on the management network. Every time I try this, I lose connectivity to the management console. It seems VMkernel wants a default gateway set and when I put it for 172.16.64.1, the SAN does not connect, but when I put it to 10.1.1.1, vCenter loses the connection. Our network administrator says he won't let the 172.16.64.x network traffice to the 10.1.1.x network, but I think that we have to set up in this way.

  Is there something I'm missing. There actually seems to be three issues. (1) when the Guide says of console, VMkernel and service is possible to distinguish between the two in ESXi? (2) if we set VMkernel network 172.16.64.x, can we create a second VMkernel on the 10.1.1.x network? and (3) should just bite the bullet and set up routing between the VMkernel and the San?

  Thank you. I know it was long and complicated, but that reflects my confusion! Any help would be appreciated.

  The answer to the first question is no, there is no distinction between console and vmkernel port in ESXi, like network service management of walks on the portgroup vmkernel.

  You should be able to create a vmkernel 2nd interface, and you do not change the default gateway.  As you have noticed, you can have a default gateway, that is why the default part.  That alone, and you should have two exchanges vmkernel, one on the network management and the other on the storage network.  The vmkernel being on the same segment as the storage, traffic goes out through it and not the default gateway, so no routing must take place.

  -KjB

  VMware vExpert

• UCS connection to SAN switches

  I set up direct UCS in the SAN before, but not San switches to connect.  My understanding of the main differences between the two is as follows:

  (1) with SAN switches, you configure VSAN.  To do this, go to the SAN-> SAN Cloud tab and configure your vSAN ID here.  Then in your vHBA template, configure it to use the proper vSAN ID you configured under cloud of SAN.  Nothing else to do here?

  (2) whereas with direct-attached storage connect FI - A SPA and SPB and FI - B to SPA and SPB, with san switches will FI - A ' switch-1' and FI - B is going to "switch-2'."  Is this correct?  If so, anyone know why it should be that way?

  No problem, tbone-111

  As much as I know, that two vHBAs are supported at this time.  It is best to use 1 from the face and side b 1.

  The vHBAs that are used depend on which WWPN you zoned on your boot LUN.

  For the following example, assume the following group:

  1.) my vHBAs are named vHBA_A1, vHBA_B1, vHBA_A2, vHBA_B2 (A tissue face a and B for b-side)

  (2.) vHBA_A1 is the first HBA on my side, and vHBA_B1 is the first HBA on b-side

  AND

  3.) WWPN of the HBA is zoned properly my boot ports storage processor (SP) of the LUN on the FC switch

  AND

  4.) WWPN of the HBA is hidden correctly on my table LUN

  Those are logical, ANDS, they must ALL be true to prevent headaches later.

  5.) disk Array A0 and B1 SP ports are connected to my A fabric FC switch.  A1 and B0 are connected to my fabric B.

  6.) this example of strategy will start A fabric be the path of MBR

  Best practices - FYI, having at least 2 SAN political Boot (1-A-side, 1 for side b and distribute among your Service profiles).

  In my startup policy, I check the will to apply vHBA naming option and specify my names of vHBAs (sorry I have no screenshots available.  Everything started with a new company and do not yet have access lab).

  My primary SAN parameter can be: the main target: wwpn of A0 and secondary target: B1 wwpn

  My secondary SAN setting can be: the main target: wwpn of B0 and secondary target: A1 wwpn

  It would be a good idea to speak with the Admins of storage while you set up the first two servers to boot on each fabric for all troubleshooting.

  If the zoning and LUN masking are configured correctly, you should see WWPN listed during the boot sequence of UCS server to the point where the starting CF driver is loaded.

  Of course, download TAC Cisco on the line, if you encounter obstacles that you can not go beyond.

  I hope this helps,

  Trevor

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

  If my answers were useful somehow, please note accordingly.  Thank you!

  Post edited by: Trevor Roberts Jr

• Execution of ESX under ESX with a HP VSA SAN Guest

  Hello

  I run an ESX host as a physical ESX host by these steps.  Both are on ESX4.1.  I imported the HP VSA SAN on ESX virtual host to test some scenarios, but I can't at all stages of start-up it is because it is showing the error below.

  

  Do you know how I can fix this problem?  I looked online and it could be due to the BONE for comments being unable to see a compatible processor to boot the 64 bit OS.  I wanted to disable the paravirtualization, but I can't locate under Options > Advanced Options > settings for the VM VSA paravirtualization.

  Do anyone know how I can fix this problem so I can test in these conditions?  Thanks in advance for any help.

  You can't execute nested 64 bit VMs with ESXi 4.  No amount of change options will change that.

• Question about installing ESX 3.5 on a SAN LUN?

  Hello

  I read that VMware does not recommend that the ESX 3.5 installation has access to the LUNS shared with virtual machines.

  But again, they recommend that the ESX 3.5 installation is placed on a logic unit number, so it is not installed locally.

  How does? In my world the ESX 3.5 installation can be installed on a LUN, but there was also that she had access to other VMs on the LUN.

  What Miss me?

  Kind regards

  Carl-Marius

  The pooling of the LUN is necessary good for the functions of the DRS / HA, alias is a sine qua non for these functions work properly, for the installation of VMware LUN se, don't see much gain from this practice, Apart that you must post the version you want to install support booting from a SAN where as far as I know just vSphere 4.1 supports initialization SAN.

  More information: http://www.vmware.com/pdf/vsphere4/r41/vsp_41_san_cfg.pdf

• ESX 4.1 cannot add SAN stroage.

  Hi all..

  I have a server ESX4.1 here and I can't seem to add storage in the SAN. (SAS storage space)

  the ESX host sees that storage is here, we can see the good size 2 233 TB and 7TB lun...

  I herd the limit is 2 GB, is that OK?

  If yes they recommended type of config just do virtual disks more...

  When I add them I get the following error

  Call "HostDatastoreSystem.QueryVmfsDatastoreCreateOptions" of object "ha-datastoresystem" on ESX "esx1. Domain.local"failed.

  

  

  This is the San Config

  

  Also be aware of the size of the block when the formatting of the data store.  Consult the following article KB http://kb.vmware.com/kb/1003565

• Using Get-VMHost connected to an ESX vs. host connected to a VirtualCenter Server

  Hello

  The script here returns a list of paths storage dead but only works when you run against an ESX host. How can I adjust it to report on all ESX hosts, managed by a VirtualCenter Server?

  $vc = Read-Host "enter the name or the IP address of your server VC."

  SE connect-VIServer-Server $vc

  Get-VMHost | Get-ScsiLun | Get-scsilunpath | Select Lunpath, Preferred SanID |

  where {$_.} SanId - ine $null - and $_. State - eq 'Dead'}

  Disconnect-VIServer-confirm: $false

  I guess this is a loop in the sense of 'ForEach' ($VMhosts in Get-VMHost), but have been unable to come up with the appropriate syntax.

  Any suggestions?

  Thank you!

  The following script will display the properties in the HTML file, as in the first script.

  Shaped more away from the exit (separation of the column, frame, color...), you will need to use the HTML formatting.

  
  $report = @()
  Get-VMHost | Sort-Object -property Name | % {
       $server = $_
       ($_ | Get-View).config.storagedevice.multipathinfo.Lun | % {
            $preferred = $_.Policy.Prefer
            $_.Path | where {$_.PathState -eq "dead"} | % {
                 $row = New-Object System.Object
                 $row | Add-Member -memberType NoteProperty -name Server -value $server.Name
                 $row | Add-Member -memberType NoteProperty -name LunPath -value $_.Name
                 $row | Add-Member -memberType NoteProperty -name State -value $_.PathState
                        $IsPreferred = $false
                 if($_.Name -eq $preferred){
                      $IsPreferred = $true
                 }
                 $row | Add-Member -memberType NoteProperty -name Preferred -value $IsPreferred
                 $sanId = ""
                 if($_.Transport.NodeWorldWideName -ne $null){
                      $sanId = "{0:x}" -f $_.Transport.NodeWorldWideName
                      for($i = $sanId.length-2 ;$i -ge 2; $i -= 2){$sanId = $sanId.insert($i,":")}
                 }
                 $row | Add-Member -memberType NoteProperty -name SanId -value $sanId
                 $report += $row
            }
  
       }
  }
  $report | ConvertTo-Html -head "Dead Path's Found" | Out-File "C:\pathreport1.html"
  

• Check the ESX path to correct the SAN enclosure

  I don't know if this is the right forum...

  I have a HP Blade enclosure connected to a HP EVA 6 K and EVA 3 K SAN. All blades that I currently have in the enclosure point to my 6K SAN controllers are active/active. 2 new servers blade I've built will be used to condense some old physical servers that are connected to the EVA 3 K that has active/passive controllers.

  For the new 2 knives I built I want to make sure that their way is properly connected to the 3 K ONLY. Is there a way to check the correct path to the 3 K before starting to move the vm servers on?

  With the current game I have, when I added a new blade I add it to the pool side san for the 6 K and then unmask and LUN I want to see. These 2 blades which will see the 3K are the first in the pen to point only to the 3K.

  > esxcfg-mpath - l

• HP NC360T vs NC380T for connection of SAN iSCSI (HP 2012i DC)

  Don't you think that it will be big difference in performance if I use rather than NC360T NC380T?

  According to multi-vendor 'A 'Post' to help our mutual iSCSI clients '.

  using VMware"I should keep simple and"in general, to use the software.

  Initiator unless iSCSI initialization is formally required".

  Do you have any suggestions on the switches that I will use? I was told HP - ProCurve 2510 G-24 - but not sure. People mentioned Dell 52xx series. Someone at - it (HP/Dell) use them in the workplace.

  Thank you!

  1006143 KB (relased 6/2008) some TOE NIC is supported, but the TOE unloading feature is not yet implemented.

  That said, I think you should go with (2) 360 t (for redundancy) or just go with (2) of NC110T.

  The disadvantage of SW iSCSI is that you are limited to 1 GB. / s by target IP address.  If your SAN network has several IP target, you can get > 1 GB/s using multiple LUNS, but you can't control the load balancing.  With HW iSCSI HBA (such as Qlogic) you spend about $700 / HBA and you can then download any treatment to the HBA.  You can also run it manually by LUN load balancing.

  With respect to the switches, the 2510 doesn't have a very large package buffer size (384 KB).  You should consider switches with larger packages such as the HP 2900 pads, 13 MB of buffer memory.  Alternatively, choose something between the two.  The buffer space more you have the less problems you may encounter with ignored packets and flow control problems.

  Ben

• VM Bios cannot connect to FC SAN

  Running ESXi 5.0.0 504890

  I have a virtual machine that is unable to connect to a network Fibre Channel SAN.

  The ESX host recognizes the FC SAN disks.

  When you enter the BIOS of the virtual machine, the "Primary Master" is [None]

  Secondary master is [ID virtual VMware]

  Startup options are defined as follows

  1 CD-ROM drive

  2 disc

  3 removable Devices

  4. the network initializing...

  Is VM 1 HDD - SCSI (0:0)

  The VM keeps trying to boot from the Intel E1000 network adapter.

  What Miss me?

  Thanks in advance.

  -Francis

  What files do you see on the DVD/ISO file. Can confirm you that it is the ISO of Windows Server 2008 installation file and not only the Patch_2 ISO (which is not bootable).

  André

• Open a virtual machine in a san on 2 different esx hosts

  Hi, I have a Vsphere essentials, 2 Esx hosts and an Iscsi san, I need to connect the virtual machine in the two esx hosts (I know I don't have FT and HA), in order to launch the virtual machine never the first Esx and if first host, does not have the virtual machine on the second esx.

  I tryied to connect the virtual machine to the second host, but the Vsphere client tell me that's not possible, because the virtual machine is already present at the first ESX.

  There is a way to establish this setting?

  For some it may depend on your application, if you can run multiple instances of the same application? If it is a web application? It stores its data in files on the server, or it stores it in a database locally? or remote database?

  -VM on a local storage of the army, would not really recommended if you need so that it starts the VMS on host b quickly.

  -If the two hosts have access to permits it storage even say and what the application can really be run only once.  He could only save it to HostA and if it fails at some point that it will be released the lock, have it on the virtual machine and you will be able to manually register the virtual machine to host b and start the virtual machine.  However, you will not be able to really get ahead.

  -HA out of here, as if a host or power failure shuts on HostA, HostB will feed into the virtual machine down automatically

  -FT - here in the spectrum creates a VM ghost on the secondary host in levels (what happends on HostA happens on host b)

  -Another option to the other end of things has implemented Microsoft MSCS Clustering with iSCSI support I think.  You can run VMS with iSCSI to your San and clustered like this application.  Just note that with iscsi client it uses some CPU to create iscsi packets.

  -Web Cluster, Cluster database.    It doesn't matter if one of the nodes of web servers or the database nodes go down really that the user will be redirected to another node in the cluster so really no need for HA/FT.

  Of course, with some of the here above are expenses and pro / con of and there's a few ways to increase availability.

• Is it possible for HA / VMotion to migrate a virtual computer when the fiber of SAN connectivity is lost / Cup?

  Use: Version ESX 4 / vCenter4

  I have a cluster with ESX 4 nodes running HA. I want to know if it is possible for vmotion to migrate a virtual computer if the host on which it lives has a loss of fiber optic connectivity to SAN/back-end storage. I can get VMotion to work when I go unplug the Ethernet cable to the back of the esx host, but when I unplug the fiber connections that will freeze the virtual machine and no migration will happen. Is it possible to do this with VMotion HA? I also tried to use aggressive DRS to see if when I unplug the fiber it lose connectivity and a loss of memory or cpu and migrate... so not happened... the vm always reports to vCenter that memory and cpu have not changed... then DRS don't not kick to migrate the virtual machine.

  Thank you.

  There is no such thing for HA. HA only fires when there is a host or a network isolation fails. DRS also does not realize this. However, there are a lot of events that can trigger an action such as "maintenance mode". don't know if there is a for the failures of way, just check it out. It is described in the following pdf document: http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf

  Duncan

  VMware communities user moderator | VCP | VCDX

  -

• ESX 3.5connect on 2 different SAN

  Hello

  It is possible to connect different SAN 2 on the same ESX Server?

  Thank you

  Yes... Just plug them together in the same fabric and area available LUN like you did with the first.

  Go here and click on "Fibre Channel SAN Configuration Guide" for more details.

• How to connect to iSCSI SAN without compromising security

  Hello:

  How to enable server OSes (VMS or physical host computers) to connect and LUN iSCSI mount without compromising the safety of our ESX host?  We have a few Microsoft servers that need to use iSCSI initiators at Mount MON for MSCS.   We cannot use the ESX initiators because VMware doesn't support iSCSI to virtual storage with MSCS.  We have already read all the documentation and spoke with VMware support, so we know that our only option is to use the iSCSI initiators in Microsoft servers to connect to the LUN.

  Our concern is security.  If we let the servers use their iSCSI initiators to connect to the San, then they also won't have access to our service and the vkernels via the iSCSI network console?  ESX requires that you have a port the service console and the port of vkernel on the iSCSI network for each ESX box that you want to use the ESX initiator for.  We struggle to understand how to connect any machine (virtual or physical) to the iSCSI network to mount LUN without exposing our service and vkernels consoles.  I know that the best practice is to remove this VMs network for this exact reason, but of course many organizations also have physical servers (UNIX, Windows) who need to access their iSCSI SAN.  How people treat this?  How much of a security problem is it?  Is there a way to secure the service console and vkernel ports while allowing host ESX - no access to the SAN?  I know that many of you are facing this exact in your organizations situation, please help.  Obviously, it is not supposed that nobody uses their SAN iSCSI for anything else except for the ESX host.  I thank very you much.

  James

  Hello

  Check out this blog

  Use of firewall is certainly a step in the right direction for that. If you can't have separate iSCSI networks, then you will need to isolate nodes NON-ESX/VCB iSCSI using other mechanisms. I would certainly opt for firewalls or reduce the redundancy to just 2 network-by-network cards and not 4 to a single network.

  Someone at - it any other suggestions? Surely many ESX users share their iSCSI SAN with a lot of different systems and operating systems. Thanks again.

  They do, but they do not secure their networks for their VMs ESX iSCSI / other physical systems. You have asked a very important question and it's how to connect to iSCSI SAN without compromising safety. If the options are currently:

  1. Physically isolate

  2. Isolate using firewall

  Given that ESX speaks in clear text and does not support IPsec for iSCSI, you have very limited options that are available to you. The firewall you use and charge iSCSI, you send through it will determine if there is no latency. Yes its a cost extra, but if it is an independent network switches/ports/etc.

  Best regards
  Edward L. Haletky
  VMware communities user moderator, VMware vExpert 2009
  ====
  Author of the book ' VMWare ESX Server in the enterprise: planning and securing virtualization servers, Copyright 2008 Pearson Education.
  Blue gears and SearchVMware Pro items - top of page links of security virtualization - Security Virtualization Round Table Podcast