Deliver the addition of iSCSI storage visible via vSphere (direct host or vCenter)

Similar Questions

• LUN visible in tabs of discovery, and not in the devices in iSCSI storage adapters

  So, the gist of the problem is in the title. The question is finally: which would cause the iSCSI targets to appear in the static discovery tab of my iSCSI initiator properties, but do NOT appear in the list of devices in the details section of my properties of the storage card? I added the new IP address of my server iSCSI in the dynamic discovery tab and all appropriate records is immediately apparent in the static discovery tab, but I can't actually join one of them or add them to storage.

  Since his arrival in vSphere 5, I have more problems than in the past with iSCSI LUNS.  We recently had to do physical and IP changes, and I'm fighting to get my iSCSI volumes reconnected. Although I write about a specific instance (something I need to get up in production as soon as POSSIBLE), I experienced the same thing on a different cluster with a completely separate SAN.

  Anyone run into something similar? Basically, I know that guests can see the iSCSI volumes, but they are not available for me to add that the cluster storage.

  NOTE: This same storage was attached to the same group last week. The only thing that has changed is IPS adapters and the SAN. In addition, the Network Configuration of the iSCSI Software initiator tab shows all three links in linked vmk "compliant".

  Thank you

  Post edited by: inspiration (added a NOTE at the bottom)

  Hello

  Thanks for the update.

  VMware announced specifically that routed iSCSI is not possible unfortunately. So yes, the issue is software ESXi SCSI adapter. The problem is that it is often a good thing - many problems of performance on other platforms relate to routers on iSCSI.

• Unable to connect the client via vsphere ESX host

  Dear team,

  Once I tried to connect to client host via vsphere ESX I m getting following error.

  

  VCenter version: 4.1.0 345043

  vSphere client: 4.1.0 345043

  ESX Version: 4.1.0 721871

  You help me on the same request.

  concerning

  Mr. VMware

  It is usually advisable, but not an obligation, to have the build of your version of vCenter client correspondence.

  You can see the Interopabilty matrix for supported configurations

  http://PartnerWeb.VMware.com/comp_guide2/SIM/interop_matrix.php

• Deliver the addition of new set of switches stacked as an extension to the network in another data center building

  Hello

  I was wondering if someone can help me, I am a humble sysadmin with no real network admin training.

  I have the following Setup to work in a rack in our data center.

  2 x Dell Sonicwall NSA2400
  2 x stacked switches Dell Powerconnect N5524

  A Sonicwall is connected to each switch (active-passive)

  Every Dell server has 2 x nics in servile failover mode, one of each network card connected to each switch

  This is done to allow a full redundancy for network, cable, switches and Firewall interface cards. It works well.

  The above mentioned rack is now full and we ordered a new rack that is in a different datacenter of construction on the same site. We decided to buy another set of stacked switches and _extend_ (no battery) these via optical SPF on the rack on the other.

  The idea is that we still have the switch fault tolerance but link to two grids through 10 GB. The new switches are 2 x Dell Powerconnect N2048 and have been implemented stacked with any connected devices.

  I have implemented SPF ports on both switches to be a junction ports and connected the two sets of switches, unfortunately our site went offline, our alert went ballistic and no servers could not talk to each other!

  Quickly, I unplugged the new switches and after a worrisome 10 alerts deleted seconds and the site is back online.

  I don't know why this has happened and reflected on the STP parameters that my googleing seem well. I don't know I'm missing something basic.

  I'll post a framework and a diagram in a follow-up post

  Which is no doubt tree covering the shot weight. It is a good idea to assign lower priority to the main switch. Generally, your root switch will be the one that plugs into the firewall. Definition of priority on the main switch to 4096, it will make the root switch. So as you work your way through different layers of the network, increase the priority. Access layer switches can be left by default.

  I would also check the physical connections for loops. In situations where you have multiple connections switch, make sure that these ports are configured in a SHIFT.

  Keep us informed.

• not visible on the ESXi LUN iSCSI hosts

  So I have a bit of a strange and hoping the community can help me to understand. In my lab at the House, I have 3 x ESXi 5.1 Build 799733 hosts x 2 guests are the same hardware (BUD Intel) and the other host an old HP flat desk. I am running CE Nexenta 3.1.3.5 on a Microserver HP which provided the iSCSI storage to HP desktop computer. The 2 new Intel NUC VMware hosts however, I am unable to get any iSCSI storage visible to them. Software iSCSI adapter is enabled, peut vmkping storage to the host and the target will appear on the static discovery tab. The configuration appears to be identical between the 2 However, the hardware is different... I have a new analysis on the host and no devices appear. Now the obvious answer is there must be a security issue on the side of Nexenta... but the 3 hosts are all part of the same group initiator. Confirmed and copied the IQN name over and over again. I still think that this is maybe a matter of Nexenta, but maybe it's something else.

  Check the vmkernel.log file contains the following information after a new analysis...

  (2013 06-09 T 23: 49:06.160Z cpu3:2933) VC: 1547: device rescan time 17 msec (total number of 5 devices)

  (2013 06-09 T 23: 49:06.160Z cpu3:2933) VC: 1550: Filesystem probe time 85 msec (4 of 5 surveyed devices)

  (2013 06-09 T 23: 49:06.412Z cpu3:2931) Vol3: 692: could not read the header of control volume: unsupported

  (2013 06-09 T 23: 49:06.412Z cpu3:2931) Vol3: 692: could not read the header of control volume: unsupported

  (2013 06-09 T 23: 49:06.412Z cpu3:2931) SFS: 4972: pilot no. FS claimed "on the remote control": unsupported

  Anyone got any ideas?

  Problem solved.

  Appears that it was a problem of connection iSCSI ports. There is only a single teddy bear in each of these hosts and allowing the port bindings vmkernel on initiator iSCSI under 'Network Configuration' result not being iSCSI target devices is not visible. Removed the vmkernel port binding and made a new analysis. Cameras then showed upward.

• Problem when adding 2nd host in Iscsi storage shared

  Hello people.

  I'll try to explain exactly my problem even if it is a little difficult liitle!

  First of all, we are talking about a test environment that is installed in my house just for learning purposes.

  I am facing a strange my iscsi storage behavior when trying to join a second host to storage vmotion purposes. I was using an Esx host (3.5) for a while and I had no problem with the iscsi storage (I use an old pc with freenas on it). I must say that I got lucky, also, local sata controllers have been recognized so I could test the Storage Vmotion between two storages (Commons and iscsi) with success in this host.

  To continue to learn, I decided to also buy another pc to test Ha cluster, Vmotion, DRS. Unfortunately, I couldn't find the same material and who as well as sata controllers do not to be recognized, so I used a disk ata for OS and my intention was to use for the volume vmfs3 iscsi storage.

  In the first host esx I used, you can see 3 storage adapters: vmhba32 vmhba33& gt; Controllers local sata,34vmhba& gt; initiator iscsi software

  In the second esx host, you can see only the vmhba32- & gt; the iSCSI Software initiator.

  The first time everything worked ok, which means that I have attached iscsi storage in host the2nd by rescaning the vmhba and I was able to browse the datstore and see the contents of it, but it lasted only 10 minutes. Then suddenly I lost the connection to common storage to both hosts, I could see in the section maps of storage, but when I pressed update in the storage section, nothing happened and even when I tried to add it using the add storage I received the message usual "cannot read the partition table information. After being a little more careful I noticed that in the section storage cards, I could see the same vmhba34 in the two hosts with the same alias to the host of the first, and here's the strangest part, the situation I described above has been changing from time to time, which means that a few times I have seen the vmhba32 in both hosts and after some time vmhba34 in both hosts! (crazy)

  I took the big decision after playing with the partition table, without effect to use the ' vmkfstool - C vmfs3 s ' _free "_ / vmfs/devices/disks/vmhba32: 0:0:1" command

  in the second host, of course, I lost all data, but now with a simple refresh in this host, I was able to see the storage.

  Unfortunately, I still couldn't ' 1 host storage access and I published the same command "vmkfstool - C vmfs3 s"free"" / vmfs/devices/disks/vmhba34: 0:0:1 ""

  with only the change you see in bold. Accordingly, it was to see the storage after a refresh with free (1) name.

  Now he is currently working for 2 days with this way not recommended and what I would be really grateful if could help me clarify what exactly is happening.

  My main problem is that I am in front of a very unstable environment that might as well have the same unexpected problem in the future and I can't reformat always storage and loss of all virtual machines

  I tried to describe the best I could to this strange situation!

  Thank you for your time and any help or advice would be most welcome!

  I was looking for a similar solution. Seems to be the only iSCSI host is possible on freeNas. See here: http://apps.sourceforge.net/phpbb/freenas/viewtopic.php?f=53&t=403&sid=f4881e6e25e752e6ee8c6b0eae5887d3

  The only solution for learning seems to be to install the server ESX or ESXi in a virtual machine and then use iSCSI. Vm Instructions to complete the installation here (you must all PDFs 6) http://knowledge.xtravirt.com/white-papers/esx-3x.html or you can replace the opnefiler by the SUN's VM iSCSI. http://www.sun.com/storage/disk_systems/unified_storage/resources.jsp , you must use the vmware converter to convert the SUN's virtual to be used in ESX machine found this in a forum... but can not find more URL. I have not tried myself but, looking for just because you want to get a similar setup.

  Wolfgang

• Trying to create a shared via iSCSI storage. Storage shows is not the second ESXI host

  I created an iSCSI lun and gone through the process of adding it to my first ESXI host. It displays well in storage adapters-> Details and I can also add as a data store.

  When I try and the same thing on my second ESXI, the iSCSI host does not appear under storage adapters-> Details (although properties are correct within the parameters of the iSCSI software card) and I can not add it as a data store.

  If I remove compleatley from the first host I can then add it to the second, but (I think) need in the two hosts to use a shared storage?

  I'm doing something wrong?

  Thank you

  What iSCSI solution do you use? Are there limits set on the number of connections?

• Delay between the addition of peripheral support and to be visible?

  I added a device supported in the portal provider. When I disconnect and reconnect and check, it is there in the list of devices selected for this version. However, it does not appear in the list of devices if I check in the App World. Is there a delay between the addition of new devices and them being visible/allowed to download? How long is it? Or is there something else I need to do to add new devices supported for existing versions?

  I believe that the original deadline for metadata changes is nominally a day, while there may be further delays (up to a week?) so the App World client is caching information. I don't think that there is a good description of what exactly is subject either of these delays, but it's a good bet that you will see at least one. These are probably not involved if you view App World via a web browser.

• iSCSI storage presented to the hosts managed by different vCenter Server - questions?

  I currently have three hosts (esxi 5.0) that are managed by vcenter server 5.5 U2. The hosts are attached to iSCSI LUNS (data warehouses) 10.

  I'm migrating to esxi 6.0 U2. For this, there are three new hosts have esxi 6.0 installed and managed by vcenter server 6.0 U2 U2.

  The plan is to detach/remove 5.0 5.5 U2 vcenter esxi hosts. Then import it into vcenter 6.0 U2 (a new cluster will be created). Once imported, uninstall the 5.5 vcenter u2. Then turn off the resident VMs imported esxi 5 hosts and move them to 6.0 esxi hosts.

  My query is regarding regarding storage.

  At present, three new guests see all storage the old 5.0 esxi hosts to see (guests are not in the cluster. "I'm still trying to put things up). That's because the new hosts were deposited to the same group on the side iSCSI initiator storage. Now things, data warehouses are visible by the hosts with esxi 5.0 (managed by vcenter 5.5 u2) and also the esxi hosts 6.0 (managed by vcenter 6.0 u2). The only VMs residing in esxi environment 6 is vcenter 6.0 u2 and update manager 6.0 u2. These are in a data store that is not any other virtual machines.

  That's no problem during the migration? I have not created a cluster for the esxi 6.0 hosts yet and plan to do after obtaining your entries.

  Thank you!

  No problem whatsoever, regardless whether if you do or that you add no vSphere 6 hosts in a HA cluster.

  If you temporarily enable EVC on the vSphere hosts 6, once all hosts are connected to the same vCenter you can VMotion all VMs to new hosts even without any stop. Clear CVS once the migration is complete.

• iSCSI treatment new target LUN in the additional paths for target Lun

  Hello

  I have a 5.5.0 ESXi host (build 1331820) I am trying place some new iSCSI LUNS to, but I have a problem with it that I am hoping someone can help me solve.

  The back-end iSCSI server is running CentOS 6.5 with tgtd providing iSCSI targets.  There are four iSCSI targets in production, with another two created and used here.  When I re-scan the iSCSI environment after adding two new objectives, I see more than 4 disks in the Details pane of map iSCSI under Configuration-> storage adapters.

  In addition, two of the LUNS stop working and inspection also shows that new iSCSI targets are seen as paths separate for the two broken LUNS.  It is:

  Existing LUNS:

  IQN.2014 - 06.storage0.jonheese.local:datastore0

  IQN.2014 - 06.storage1.jonheese.local:datastore1

  IQN.2014 - 06.storage2.jonheese.local:datastore2

  IQN.2014 - 06.storage3.jonheese.local:datastore3

  New LUN:

  IQN.2014 - 06.storage4.jonheese.local:datastore4

  IQN.2014 - 06.storage5.jonheese.local:datastore5

  Of the "Managing paths" dialog for each found discs, I see that "datastore4" presents itself as an additional path to "datastore0" and "datastore5" presents itself as a path to "datastore1" - even if the target names are clearly different.

  So can someone tell me why vSphere client iSCSI is the treatment target separate iSCSI LUNS as having multiple paths to the same target?  I compared the configuration of tgtd between the original LUN 4 and 2 new LUNS, and everything seems OK.  They are all attached to different backend disks (not that vSphere should know/care about this) and I wrote zeros to the new back-end disks LUNS to ensure that there is nothing odd about the disc, confusing the iSCSI client.

  I can post some newspapers/config/information required.  Thanks in advance.

  Kind regards

  Jon Heese

  For anyone who is on this same situation, my supposition above proved to be correct.  But in addition to renumbering of the scsi_id each of the LUNS, I also had to renumber the field controller_tid to the controllers on the second node would be present with unique IDS.  Here is an example of the stanza of config I used for each LUN:

  # device LUN storage medium

  -storage/dev/drbd5 store

  # SCSI for storage LUN identifier

  scsi_id EIT 00050001

  # Identifier for the LUN controller SCSI

  controller_tid 5

  # iSCSI initiator IP address (ed) allowed to connect

  initiator-address 192.168.24.0/24

  It is a problem of configuration of tgtd after all!  Thanks to all for the questions that led me to the right answer!

  Kind regards

  Jon Heese

• 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.

• Creation of the NSX for IP (iSCSI) storage

  Hi all

  I considered just the implications of VMware NSX on storage over IP (iSCSI) Design.

  If we create three groups: Edge, Mgmt and Compute, each in its own grid:

  • Each cluster/rack is associated with (2) sheet of 10 GB switches
  • There are 2 two 10 GB backbone switches for the installation
  • Each sheet is connected to each switch of the spine (sheet ports 47 to the spinal #1 switch) and leaves 48 to the #2 of the spine switch
  • 10Gb iSCSI without are configured in the cluster of MGMT/rack and connected to the 10 GB sheet past in the cluster/rack of Mgmt.

  Then, how facilitate us the IP storage for ESXi hosts who are not in the same basket as the SAN?

  Suppose we define VLAN 99 for IP storage (by Figure 4 - NSX v2.1 Design Guide) and follow the recommendations 'trunking VLAN on the link between the sheet and the spine is not allowed' (p. 65 - NSX v2.1 Design Guide), then the inescapable conclusion is that the SAN are not available since the Compute cluster/rack or edge.

  How to set an exception that will allow us to the trunk VLAN 99 (no gateway, without calculation, not able rout) of the spine, so IP storage is accessible from all ESXi hosts?

  THX in ADV!

  Here, you will need to use the IP routing for communication inter rack configured at the ESXi host level.

  For example on the grid 1 VMKernel Interface for storage is 10.77.1.10 in Vlan 77.

  switch sheet of TOR, we terminate that VLAN as IVR with IP address of 10.77.1.1

  To Inter Communication IP Rack storage, let's add command to host ESXi on racks 1 hosts next-level:

  esxcli ip network route ipv4 add - n 10.77.0.0/16 g 10.77.1.1

  (Note VMkernel Interface for different media guests will be in different subnets. So in rack 2 VMKernel Interface for storage will be 10.77.2.10)

  (Source Guide design v2.1, page 79-80)

• Best way to disconnect the iSCSI storage

  Hello

  I have a server cluster, connected to the Equallogic iSCSI storage. I want to delete and re-create a volume storage, but in a fairly safe way.
  Ideally, I would be able to take the volume out of action for a few days, but there are avaiable to reconnect if necessary. Normally, I would do this to simply put the volume offline. It can then be seen by the hosts, but I put it online as appropriate.
  East - meaning the best, though? It does not seem to cause some problems that are to do with map software iSCSI being unable to find the device, until a new analysis/reset of the host is according to me.
  Can anyone suggest a better way to do this?

  Hello.

  The procedure is described in http://kb.vmware.com/kb/1015084

  Good luck!

• Fully automate the addition of a datasoter via PowerCLI

  I have a need to be able to completely automate the addition of a new data store to a new installation of ESXi via powerCLI.  My problem is I want to have this fully automated and be able to enforce it against any box without user intervention, which means that I need a way to return the CNAME of the ScsiLun in new-store data command.

  I am currently using the command to run my action you want below, but for some reason, it does not.

  $con = get-ScsiLun | Select-object CanonicalName

  New data store - VMHost 192.168.1.1 - name newDS-path $con - Vmfs - BlockSizeMB 1

  The above returns the above error

  New-store data: 2010-07-19 10:55:32 news-Datastore 52e3288c-ef02-d45e-ea

  77 - 96cd39fe5cd6 could not find the specified disc or the disc is already in

  "use: ' @{CanonicalName = naa.600508b10010395659503152424f0100}"

  C:\Program Files\VMware\Infrastructure\vSphere PowerCLI\test.ps1:9 tank: 14

  + New-store data < < < < - VMHost 192.168.1.1 - name newDS-path $con - Vmfs Blo.

  ckSizeMB 1

  + CategoryInfo: ObjectNotFound: (@{CanonicalName...) 503152424f010

  (0}: string) , VimException

  + FullyQualifiedErrorId: Core_StorageServiceImpl_GetHostScsiDiskByCanonic

  alName_DiskNotFound, VMware.VimAutomation.VimAutomation.Commands.Host.NewDa

  tastore

  Although below works very well.

  new data store - VMHost 192.168.1.1 - name dvms-path naa.600508b10010395659503152424f0100 - Vmfs - BlockSizeMB 1

  I also tired the Deputy bud did not work

  $test = get-datastore. Select-Object - 1 first

  new data store - VMHost 192.168.1.1 - name dvms-path $test - Vmfs - BlockSizeMB 1

  Help or direction would be greatly appreciated.

  Thank you

  The Select-Object cmdlet does not return the name of the LUN as a string, but as a ScsiLunImpl object.

  The New-Datatsore cmdlet requires a string for the - Path parameter.

  You can do

  $con = (Get-ScsiLun).CanonicalName
  New-Datastore -VMHost 192.168.1.1 -Name newDS -Path $con -Vmfs -BlockSizeMB 1
  

  ____________

  Blog: LucD notes

  Twitter: lucd22

• Storage VMotion, leaving the additional disks when they are

  I want to move a virtual machine but, let one of the additional attached disks where it is.

  When you use the interactive for svmotion, at this stage, «if you want to stay with the VM disks then skip this step...» You want to place the disks individually. I say Yes and identify the additional path on the vmdk disk.

  He then asks the destination...

  1. I think that if I enter the current data (source) to the destination store, this additional disc will just stay where he is. Is this correct?

  2. I also want to make sure that when svmotion sees that I chose the data source as a destination store, it leaves just here. Specifically, I want to make sure that it is not yet really moving the disc but in the same data store. It is a big drive and I don't have enough space on the data store if she done something like this.

  The answer lies in the help file for svmotion one thing I noticed, is that the syntax is correct, except that single quotes should be in double quotes ".» Other than that, the command line below will do exactly as you want, and that's essentially what you thought. Files will not overwrite themselves, then it will not try to copy the same disc in the same data store.

  Move the storage for a virtual machine on new_datastore, but let the disc 1

  and 2 in old_datastore:

  SVMotion - datacenter = "My DC" - vm = "[old_datastore] myvm/myvm.vmx:"

  new_datastore' - discs = "[old_datastore] myvm/myvm_1.vmdk:"

  "old_datastore, myvm/myvm_2.vmdk: old_datastore '.

  -KjB

  VMware vExpert

  Post edited by: kjb007: trying to fix the formatting.