question put on the vSphere iSCSI SAN infrastructure network

Similar Questions

• Question put on the scale of the DateTimePicker

  Hello

  I'm running into a problem of particular display with DateTimePicker... I set a DateTimePicker to preferredWidth: Infinity so that it fills the entire screen. It works fine when the DateTimePicker is set to the default mode, which is DateTimePickerMode.Date.

  Whenever the other modes are selected, the control does not fit... I added a code snippet that reproduces the question mentioned above... Any suggestions?

          Container
          {
            leftPadding: 20
            rightPadding: 20
            topPadding: 20
            bottomPadding: 20  
  
            DateTimePicker
            {
              id: dateTimePicker
              preferredWidth: Infinity
            } 
  
            DateTimePicker
            {
              id: dateTimePicker2
              preferredWidth: Infinity
              mode: DateTimePickerMode.Time
            }   
  
            DateTimePicker
            {
              id: dateTimePicker3
              preferredWidth: Infinity
              mode: DateTimePickerMode.DateTime
            }
          }
  

  A report to the issue on jira and it is a known issue and will be fixed in 10.1.x.

• can not handle the vSphere client SAN

  I installed a Server on a Windows 2008 32-bit with vCenter Server

  vSphere Client (ESX 4 update 1) and

  IBM DS300 DS4000, DS5000 vCenter Management plugin

  on the same virtual machine.

  I have already created a Storage Administrator role with all the privileges, give permission a user "Omar" as a storage administrator after I installed that plugin but it still says that the user doesn't have the privilege as a storage administrator.

  Manager of plug-in, the plug-in is enabled.

  What could be causing this problem?

  Hello

  Have you your new role is added to the data center level? If so, perhaps there is another role that is set up at the same level or below and prevents your user to use is new rights. Prevent access are always stronger than the access so if the same user has rights of Directors on the specific object, but somewhere above it have less straight, he'll lose his privileges.

  I used to have the same kind of problems, and this was the solution I found for me.

  I hope this helps!

• question of iSCSI san

  Hello everyone,

  I just created my first with software e open iscsi san solution.

  My situation: on the local disk, I put my VM

  I created 4 iscsi data warehouses

  1 will be used to back up my VM and can be reached for Vsphere

  The other 3 serve as a backup for my 3 VMS solution. I am connected to them through the Iscsi initiator in the virtual machine, format them, and now they appear as an additional drive in the virtual machine. I can see them in Vsphere but is no longer in data warehouses, but in devices (because they are formatted as NTFS)

  Now the question:

  Is it possible to see what data is on data warehouses that are formatted to ntfs When you are not connected to the virtual computer?

  When a virtual machine should crash, backupped data should always be saved to disk iscsi, but where can I get it?

  Thanks in advance, onkt

  NTFS is only accessible via windows server only. You can mount the iSCSI drive backup on another virtual computer.

• design for the iSCSI SAN review

  Hi all

  I intend to implement a storage shared in our vmware infrastructure. And we'll buy DELL or iSCSCI SAN NETAPP.

  Could someone pls review the design of SAN attached. Please note that we do not have a vCenter in the environment. And also we have not yet finalized on behalf of initiator SCSI, whether to use a software or iSCSI HBA for this purpose. Is it worth investing in the hardware initiator. Please suggest.

  Kind regards

  Nithin

  To use several vmks iSCSI, you cannot assign two network adapters to the iSCSI vmks.

  You cannot have an active nic by vmk and the other the vSwitch network adapter must be moved down to "unused controller. Then you can bind to port in the software iSCSI hba adapter. It is the only way to achieve real multichannel, load balancing and failover for multiple iSCSI vmks.

  Here's a KB on how do: http://kb.vmware.com/kb/2045040

  But if you google, it has quite a few tutorials with pictures detailed, etc..

  Tim

• iSCSI SAN availability before VSphere install

  Hello world

  We are a small company with about 30 users but are developing new technologies.  I have a brand new installation of VMWare for months.  I have one, I hope, a simple question for anyone.

  potentially relevant hardware configuration:

  -2 servers ESX ESX 4 Update 1 (essentials more)

  -SAN of Dell (EMC) AX4 - 5i 1 full 420 GB 15 k SAS drives

  -redundant gigabit switch topology BPMH

  My purchase SAN Dell included a remote installation.  This includes cutting upward the LUN, configuring for iSCSI availability and possibly connect your existing servers to their designated targets.  Dell makes their sound installation process as many customers have their ESX Servers ready to go before you install the regular remote SAN.  Initially, I was counting on having the SAN installed and ready to go before I went on my 2 servers ESX installation/configuration.  I thought it would be better than the SAN available to connect to during the ESX installation process.

  Is there a reason to take one path on the other?  All observations would be greatly appreciated.

  Thanks in advance!

  -Jordan

  I would definitely installed and fully configured servers with all your IP addresses of port service before installing the San.

  Also, I don't think you need to BPMH for this type of installation.  This is mainly just cut the switches in the right configuration of VLANS to separate iSCSI traffic, production and management.  With the installation of this small tree covering weight is not really necessary.  You probably don't have anyway two switches.  You'd be better just setting up a trunk of ethernet grouped together for redundancy and get the advantage of having the largest bandwidth full time.  You can even use more than two ports then if traffic warrants the addition.

  Steve Puluka

  JNCIA-ER enterprise routing

  Enterprise JNCIA-EX switching

  Senior network administrator

  Liberty Dialysis

  http://puluka.com/home

• Cannot migrate VM on iSCSI SAN. Failure at the helm of the 10%. Peut vmping to all addresses

  Hello everyone

  Impossible to migrate virtual machines on iSCSI SAN. Failure at the helm of the 10%. Peut vmping to all addresses

  I recently installed a new configuration of the VM and I feel the above. My configuration is:

  2 HP DL380 with 1CPU 16 GB of ram and 500 GB shared space on iSCSI SAN.

  Installation of the network as follows:

  each host has the 6 network ports that is load balanced and fault tolrated in 3 VMSwitches. VMSwitch0 goes to 2 ports to shared resources on a 4510th cisco. On this switch, I use VLAN tagging to different servers that perform different functions. It works fine.ie. VLAN 5 is for the management vlan 31 is for secure vlan servers 37 is forinternal Web servers.

  VMSwitch1 is a vmkwenelport for the connection of iSCSI SAN. It is set on vlan 200 on the switch, so does tagging vlan put it. We have separated our san network ourusual networks.

  vmswitch2 is used for backup purposes and is used in a similar manner as vmswitch0. the ports of trunkied and backup services is vlan tag to go to the correct servers.

  I am able to ping betwneen the VLANS allowed. I can also vmkping to all the ip addresses of the two hosts san.

  What I can't do is to migrate direct customers between the hosts. He is still unable to 10% with the following error:

  Migrate the computer virtual iws3xx - pop1.mns.tlg.private a general error has occurred: the VMotion failed because the ESX hosts were not able to connect to the network for VMotion.  Please check your physical network configuration and settings network VMotion.

  I looked in the newspaper of vmkkernel and I get the following text:

  9 Oct 15:05:38 esxn1-pop1 vmkernel: & lt; 7 & gt; fn_scroll_back not implemented & lt; 7 & gt; fn_scroll_back not implemented & lt; 7 & gt; fn_scroll_back not implemented & lt; 7 & gt; fn_scroll_back no implemented7:05:04:55.236 cpu2:6534) migrate: vm 6535:2094: info setting VMOTION: ts = 1255097135856641 Source, src = ip & lt; 172.31.207.21 & gt;

  9 Oct 15:05:38 esxn1-pop1 vmkernel: ip dest = & lt; 172.31.207.22 & gt; Dest wid = 6447 using SHARED swap

  9 Oct 15:05:38 esxn1-pop1 vmkernel: 7:05:04:55.236 cpu2:6534) Tcpip_Vmk: 1107: refining worldwide 6899 172.31.207.21, success

  (9 Oct 15:05:38 esxn1-pop1 vmkernel: 7:05:04:55.236 cpu2:6534) VMotion: 1807:1255097135856641 S: Set ip address ' 172.31.207.21 ' worldlet affinity to send the world ID 6899

  9 Oct 15:06:53 esxn1-pop1 vmkernel: 7:05:06:10.234 cpu3:6899) WARNING: MigrateNet: 668: 1255097135856641 S: Connect to & lt; 172.31.207.22 & gt; : 8000 failed: timeout

  9 Oct 15:06:53 esxn1-pop1 vmkernel: 7:05:06:10.234 cpu3:6899) WARNING: migrate: 295: 1255097135856641 S: Failed: host ESX The failed to connect on the network for VMotion (0xbad010d) @0 x 0

  9 Oct 15:06:53 esxn1-pop1 vmkernel: 7:05:06:10.245 cpu1:6538) WARNING: migrate: 3267: 1255097135856641 s: Migration, considered a failure by the VMX.  It is probably a timeout, but check the VMX log for the actual error.

  The journal of vmx says:

  16:07:38.856 Oct 09: vmx | http://Msg.checkpoint.migration.nodata the VMotion failed because the destination ESX host has not received all of the data of the source on the network for VMotion ESX host.  Please check your network VMotion settings and physical network configuration and ensure that they are correct.

  Can anyone help with this please

  No iSCSI traffic will work only if vmKernal and vmConsole are on the same vswitch. Maybe on the same vLAN according to how your VLAN.

• How to get iSCSI SAN connected to ESX when the SAN is on a different subnet?

  Hi all

  I have two machines ESX which are directly connected to a San that are on a different subnet other network cards.  Other network cards are 10.x.x.x and the SAN is on 172.16.x.x, however whenever I try to add the iSCSI storage, the system will never find the LUN.  I put the vmkernel 172.16.x.x but it does not always find them.  I know that the LUNS are configured correctly if its ESX just having problems with the other subnet.

  You need to activate the Service Console to see the iSCSI SAN, too. This is because you use the initiator software. For example, you can add a second SC in the vSwitch that your VMKernel Port is connected and align on the same subnet.

  Kind regards

  Gerrit Lehr

  If you have found this or other useful information, please consider awarding points to 'Correct' or 'useful '.

• How to add the software iSCSI adapter in vSphere, ESXi 5.0?

  Hello

  Please give me the steps to add the software iSCSI adapter in vSphere, ESXi 5.0.

  Thank you.

  Hello

  In an earlier version of VMware ESXi software iSCSI adapter was included in the list of the storage card, but is not in the case of VMware ESXi 5.0. In ESXi 5.0 iSCSI adapters are not listed by default and must be activated first before we go away from configuration.

  How to add iSCSI adapter in ESXi 5 check the link below

  http://www.google.co.in/#sclient=psy&hl=en&source=hp&q=How+to+add+Software+iSCSI+Adaptor+in+vSphere+ESXi+5.0+Site%3A+blog.srinfotec.com&pbx=1&oq=How+to+add+Software+iSCSI+Adaptor+in+vSphere+ESXi+5.0+Site:+blog.srinfotec.com&aq=f&aqi=&aql=&gs_sm=e&gs_upl=9181l21561l0l21875l33l30l4l0l0l0l736l10898l3-8.7.7.1l23l0&bav=on.2,or.r_gc.r_pw.&fp=1ad7a99e02298f12&biw=1366&bih=647

  or

  http://blog.srinfotec.com/?p=178

  concerning

  Rohit

• Link to maps software iSCSI NIC vmkernal and the vsphere client

  Hello

  IM playing with our VMware 4.1 hosts a Dell Equallogic PS4000E, connection

  So far, I have:

  Created ports VMkernal

  Apply adapters

  The iSCSI initiator enabled

  But apparently, I need to run the following command to bind the ports of iscsi software adapter:

  Add an esxcli swisscsi nic - n vmk # vmhba d #.

  Is anyway in the Vsphere Client?

  Hello.

  Unfortunately, there is no way to do it from the vSphere client.

  Good luck!

• iSCSI SAN, blocking the ability to attach a RDM to two VM?

  Hello

  We have an iSCSI SAN and I wanted to test with clusters on this stuff, but I can't get a RDM attached to more than one virtual computer at a time.

  I know that MSCS is not taken in charge by iSCSI, but is not supported or is it not possible to join a ROW over a virtual computer at a time?

  Thank you!

  Kenneth

  The solution should work... so with RDM, but also with an initiator of software inside each node of the virtual computer.

  If you use RDM, you must configure the SCSI controller in physical mode.

  On the second node does not add a new drive... but easy to use existing RDM disk (or disable ROW filtering of the customer).

  André

• Should two switches for the installation of iSCSI SAN - be stacked

  I mean by "stacked" should they be hung by backplane?  Reference Dell passes, btw.

  Just two hosts connected to an iSCSI SAN.

  If the goal is to be completely redundant, your server is able to cable a physical NIC directly on each switch and your San can connect to both switches, there is no reason for the connections between these switches. Stacking of the switches can provide options for a large number of cases, but I don't think it will be here.

• ESXi 3.5 4 problem to upgrade by adding the VMFS partition existing on iSCSI SAN

  Hi all

  I've got 2 x Dell PowerEdge 2950 III linked directly with Dell MD3000i iSCSI-SAN and today I had once hard to improve my production ESXi 3.5 u 4 ESXi 4.0,.

  First is that the upgrade is failed miserably after following this thread: url = http://communities.vmware.com/thread/211413;jsessionid=47217F9BCCA2DF1325DBE7A266D48A8D?tstart=0VMware communities: error on upgrade the host: this host is not compatible with this upgrade. [url]

  with the following error message: ERROR: unsupported boot disk

  The layout of boot device on the host computer does not support the upgrade.

  That's why I did a clean reinstall of ESXi 4 on top of ESXi 3.5 u 4 and lost all unique settings on my ESXi host. I am now stuck in SAN iSCSI partition mapping after following the guide from: http://support.dell.com/support/edocs/software/eslvmwre/AdditionalDocs/cnfigrtnguide/storage_guide.pdf [/ URL]

  See the following attachment.

  I wonder how people make their upgrade in ESXi 4.0 in the production system running ESXi 3.5 u 4 filled with hundreds of VM? The reason why I use 2 x ESXi server connected to unique SAN server, is that I can just start the virtual machine on the SAN from the other ESXi - & gt; that's fine and tested, but then when I rebuild the failed server, I need to delete all the data inside the shared partition that contains my VMs.

  So in conclusion after one of the ESXi server failed, mapping of iSCSI would eventually destroy all data in the partition?

  CMIIW, any idea and suggestion would be gladly appreciated

  Kind regards

  AWT

  The configuration-> tab cards storage, you should be able to recrawl and find existing VMFS volumes.  You shouldn't need to add storage.

  Andy

• Planning the migration from DAS to iscsi SAN

  Hello

  We have a physical server running 6 VM ESX 3.5 (1 win SBS 2003 and linux 5) local SAS disks

  It's a 2xquad core clocked at 2.66 GHz dell

  now, let's add a second physical server (dell 2xquad core at 2.5 Ghz) and an ISCSI SAN: we would like to install ESXi on the second server and move all VMs on iscsi storage, so if the first server goes down in a few minutes we can manually set up the other to run all virtual machines (we are a small company and at present cannot afford the company/vmotion license).

  I ask for advice because we would virtualize an old physical terminal so win2003 Server (with 10-15 users, mainly working with MS office applications) using the second new physical server.

  This is the first time that we install a SAN (it's a dell MD300i with 10 disks 146 GB SAS, 5-disc SATA 1 TB for backup and snapshots) and we want to get the best performance out of it. Read the other posts, I understand that the discs are very important in a server virtualization terminal server and having good performance out of it.

  So, with this type of SAN and our workload, we should define a unique group of 5disk RAID with 9 discs and 1 hot spare, with a large ramdisk on it to create one or more data VMFS stores?

  or is it better to create 2 disk groups:

  -1 with two RAID1 disks for terminal server VM

  -1 with seven discs RAID5 for all other VM

  with a global hot spare disk?

  other general suggestions for migration, we will do?

  Thanks in advance

  Guido

  Yes, it's what I would do.

  -KjB

• Question so that the migration of the VM using the vSphere API

  Hello

  I am having some problems during the migration of a virtual machine using vSphere SDK.

  I have install the vSphere environment as there are two hosts esxi installed on different physical machines with multiple virtual machines above them.

  Now I want to migrate one say the virtual macines VM1 fron host1 to host2. I did it via vCenter uses the vSphere client and it worked fine. Now, I have to perform the same task using the vSphere API. For this I use the template of "VMotion" located in the com/vmware/vm directory. I run the command as follows:

  targethost $ run.bat url username password, shows targetpool

  I'm not sure of the targetpool argument and I need advice on what I need to specify a name of pool of resources here. Acorrding to:

  http://www.VMware.com/support/developer/VC-SDK/visdk400pubs/ReferenceGuide/Vim.virtualmachine.html#migrate

  If the pool parameter remains disabled, current pool of the virtual machine is used as target the pool. I tried specifying the pool of resources such as:

  [- targetpool]

  but it gives the error:

  Error: List of resources target not found.

  Looking forward to all the advice. Thank you.

  Even if you do not have resource pools, it is actually a 'root' list of resources"which will be still exists. Try to specify 'Resources' as the name of the targetpool and allow you to migrate your VM.