Different connetced in a vSphere San

Similar Questions

• replication between different versions of ESXi vSphere

  Hi all

  Is it possible to use replication between different versions of ESXi vSphere? the scenario is as follows.

  Source site:

  vCenter 6

  RS 6

  Replication Unit 6

  5.5 ESXi

  The target site:

  vCenter 6

  RS 6

  Replication Unit 6

  6 ESXi

  I understand that vCenter, SRM and VRA must match and vSphere replication 6 is compatible with ESXi 5 upwards and it is the vSphere host in the source location that replicates on the VRA rather than a host of ESXi target so it should work, but I wanted a certain Yes/No.

  Thank you

  Definite yes.

  VMware product interoperability matrices

  

• EqualLogic SAN volume issue

  As I am virtualizing our infrastructure, a thought occurred to me.  First, the Installer - 3 hosts vSphere 4 connected to a SAN EqualLogic PS6000XV network.  We use iSCSI on the network for connectivity maps.  I was put in service a volume by comments on the side EqualLogic.  We did not do anything with the snapshots or replication - that will come later.  Our immediate goal is just to virtualize our servers and continue our backup and restore as usual procedures.  This is likely to change so we can use snapshot technologies, but also the stuff of VMware.  Anyway, to my question.  Should I continue this way?  One volume per person.  Or should I do a large volume and then put my VMs on the single volume?  On the SAN, the whole thing is configured in RAID-50.  I made only a handful of non-critical servers to date.  I'm not sure what are the best practices in this scenario.  What worries me is that if I continue this way, I could lose some instant advantage later or something like that.

  While the expansion of VMFS volumes is less a problem in vSphere that it was in the past, the point is that having a unit logic by VM number increases management and effort if you need to grow the hard disk to the virtual machine.  If you need to add 20 GB for drive E: one of your virtual machines, it's easy to do when using large volumes because you probably the free space to simply increase the size of the virtual disk.  If you use the method "a unit logic by VM number", you may initially increase the size of the LUN on the EqualLogic, then extend the VMFS volume in vSphere, and finally to increase the size of the virtual disk across comments.

  Another part of the equation is the backup of the virtual machine.  Many tools available for VMware backup can make backup 'LAN-free' by connecting directly to the storage.  To do this, you must present the VMFS volumes on a Windows backup server and the software then reads directly from there, rather than transfer on each ESX host network.  If you use a product that saved using this method, you must present all of your VMFS volumes to this server from Windows instead of just one or two larger LUN.

  I have seen many different deployments of VI3/vSphere and saw the two one LUN per VM model, as well as the virtual machine of 15-20 by the largest LUN model.  In almost all cases, those who did a unit number logic by VM regretted and find it difficult to manage without any real advantage.

• Entry-level SAN

  I just have to start a business (yesterday) and have my work cut out for me. My predecessor was sacked but poor management and lack of planning.

  Here, the infrastructure is need of a total overhaul. That said, the company is mainly virtualized with only 2 servers file inherited still on the network. They currently have 3 hosts pointing to 3 stores different data on the same SAN (nothing surprises me here) and 98% storage allocated and there is no room.

  I'm new to San entry that I only played with NetApp FS2240 for a few years. I need suggestions that there is a lot that many choose to and I tried to browse through all the hype and propaganda that surrounds them.

  I want a device that allows direct iSCSI connection to 3 guests.  Looks like we'll require on the storage capacity of 6 to 10 GB in RAID 5 with extendability for future growth. I also want to use the old SAN for snapshots

  I do not have a budget right now but I am looking in the area between this project and 10 k $-$20 AUS needs to move quickly.

  Currently, I am interested in the HP Lefthand P4000 series but have also sought to Bay EqualLogic PS4110XV 3.5 "10GbE iSCSI. I didn't price on either and maybe not what is needed here.

  Any suggestions will be greatly appreciated.

  Thank you

  Take a look at the makings of Nexenta.  Might be cheaper for your uses (although with a little less resilience)

  That being said, take a look at the e - its specially designed for environments like yours (cheap, easy to use/install) and shed light on support costs.  It's not like buying a VMAX.

• VSphere client 5 cohabiting with VCenter 4.1

  Hi all.  I have an environment vSphere with VCenter Server 4.  I now have an ESXi 5 autonomous (free version, no VCenter) host that I need to set up a client.  I want to be able to do is to install and run the client VSphere 5 on the same workstation where the client VSphere 4.1 is now installed and running, but I don't want to interfere with my existing environment.  I have never tried to run two different versions of the VSphere client on a single machine.  I installed the v.5.0 customer but I don't know how to start.  When I run the client normally, he opens the client 4.1 original. I tried to do a little research in the forums and documentation, but I can't find anything that specifically addresses this problem.

  I guess that there is probably some kind of command line that I could use to do what I want. Any help would be appreciated.

  Thank you!

  having multiple clients is perfectly acceptable and taken in charge.  Based on the environment connect you to the Launcher will 'launch' the correct client.

  Clients may seem alike, but when you log in your environment, you will see that they are build different levels (help - on VMware vSphere)

• behavior of the api VMware SAN and NFS

  While working on the vmware api Reconfigure_task fact face a problem. A single montage, in the same scenario, he started the exception as

  incompatiable backup device 1 in the case of NFS, but in the case of SAN, it is throwing exception as a Configuration not valid for the '1' device.

  My question here is that if vmware SDK behaves differently in the case of SAN and NFS for the same api?

  Is there any document coming from where we can get more information on the different behavior and how to approach us differently through the c# application?

  Basically, the answer is no. VimSdk acts not differently for NFS for SAN.

  Of course, ReconfigureVM_Task can have constraints special som according to the storage used.

  Tos2k

• vSphere 4: command-line single vmdk svmotion

  Hello

  I can't find a way to do it.

  Let's say I have a virtual machine with 5 vmdk

  I want to be able to move among the 5 vmdk in another data store

  In the past, there was a svmotion.pl but I can not find...

  Any ideas?

  SVMotion.pl is part of the VMware vSphere CLI. It's a different product of VMware vSphere PowerCLI. If you open VMware vSphere CLI you will find svmotion.pl in the bin directory.

  Best regards, Robert

• MSA2000 and VMWARE Vsphere

  Hello

  We have a HP MSA2000 with Vsphere san. The san mini is configured Raid 5 with 5 TB volume. VSphere sees the volume but only 550 GB of it. Help with this would be awesome

  Maximum is 2 TB minus 512 b, then make smaller RAID volumes.

  http://www.VMware.com/PDF/vSphere4/R40/vsp_40_config_max.PDF

• Addition of RDM but bo SCsi controller is added

  Hello

  I am trying to create a cluster between two virtual machines that are on two servers different esxi. I use SAN VNX 5100. My esxi version is 5.1.

  I am trying to add RDM hard drive but when I completed the steps, it didn't add the SCSi controller.

  Any idea?

  Kind regards

  Talha

  This statement is a useful guide that covers the process for a few common scenarios: http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-mscs-guide.pdf

• failure of the system, looking for answers

  Need help for the guys. Had a major failure of the system last week, and I'm a bit confused as to what happened and why I was unable to get free. I lost a bit of my confidence in Vsphere, and I'd like to renew that.

  A bit on the environment, esxi 5.0 U1, with servers HP Gen 8 3 node cluster running. HP P4500 SAN iscsi for vmfs data storage. ESXi is installed on HP's CF cards in servers. This cluster has been upward and running for about 6 months, not a single hiccup before that.

  Wednesday we have migrated 2 of our vm (SQL and progress) to this cluster 5.0 database, the virtual machine went on different hosts in the cluster. The virtual machine was running on a cluster 2 older nodes with esxi 4.1 U2. Machines migrated fine, fine tools updates, reboot, everything seemed fine.

  About 2 hours after that the migration, we started to receive calls that our Progress database is down, users could not connect. Then we started getting more calls, other machines were inaccessible. Glancing from vcenter I could see all the virtual machines in question were on the same host, and I was unable to open the console in vsphere for VMs on that host. The host showed he was connected, showed all the vm connected, but I could not open the console or the desktop remotely to one of the VMs on that host. I started studying, and of course this host fell all the SAN Iscsi network connections. The railways have shown dead. Ports of nic card viewed active, the switch ports showed activity, but the connections were down. I could always ping the address of management for the host however, and ports for vmotion were in place.

  At this point, I started to try and vmotion VMs on that host data base progress, he would not migrate, just sat at 8% prepare to migrate. I tried other virtual machines with the same result. I started to wonder why HA had not kicked, and why I couldn't move anything. At this stage the host started disconnecting from the cluster. I could always ping on the host, but vsphere showed as disconnected. I couldn't move my VM, and I couldn't go to the host via vcenter, via the vsphere client pointed directly to the host, or by using the DCUI.

  So I called VMware support, got an engineer on the line with me, and it became clear we were going to have to power cycle that host and crash all virtual machine running on it. It wasn't a very pleasant for me answer because this database of progress is our main production system, and I was afraid of corruption. We had no choice, so we did. When the host came back upward, fortunately the virtual machine came very well. VMware engineer digging in the newspapers and said that this was with a particular NIC card driver with known issues. He showed me the KB on this issue, and it seemed to be a known issue. We have updated these drivers on all hosts, and that's all.

  My problem with this is that, how is the cluster ran fine for 6 months without problem, and how come the redundant path to the SAN did not keep the connection active when with the path with the bad nic card driver failed? I have 2 different, with 2 NICs different paths for the Iscsi SAN. The other card had no known driver issue. Why both paths failed not just in cause of a driver on one of the cards problem? More worrying is also how is it that I could not immigrate anything, and why no HA kick in?

  Sorry for the novel here, but without all the details is not part of a story. My biggest concern, that's why I couldn't move anything? In the event of a host failure, what you're supposed to do in order to migrate the machines if they don't migrate via vsphere client? We were down for about 2.5 hours, and a lot of questions were thrown on me the senior management as to why my "system available, redundant high" took hours to retrieve...

  Guys here any ideas, thoughts on how I would have handled it differently, reasons why I should be confident everything is fine now?

  Thanks for your time

  Kevin

  trink408 wrote:

  Thanks Matt.

  I guess some of the problem is not completely understand how the HA or Vmotion. I was under the impression once that the virtual machine was not reachable HA wouldn't kick and move the virtual machine? The virtual machine was not to ping requests or accessible by the Office remotely. I couldn't get their power off or do anything through vcenter either.

  If they had no link usable storage, this seems possible.  HA simply does not address the failures of storage.  Not at all.  It IS possible to activate at the level of the VM HA, but it isn't on by default - must be activated on a per-VM basis.  You should read the book by Duncan Epping on this - it's the bible of the AH.

  So in case something happens with the connection of storage, you have really no way to vmotion anything right here, and your only option is to kill the host / VM running on it, and then migrate or leave HA move them?

  Fix.

  I didn't know that I wouldn't be able to vmotion virtual machine if the host has lost its connection to storage. The other hosts in the cluster saw storage.

  The source host is controlling these VMDK, as far as the other guests are concerned (they see a lock on the file) and when they ask the host if its still alive, he answers (because it has not powered the network lost or down, which are the failure mode THAT HA is designed to handle). So they take charge.

  The reason why it took so long was because I didn't kill the host with my concerns for the database. I was hoping that the VMware engineer may have a way to gracefully close things down. So he spent some time looking around and trying to determine what was going on. Ultimately we just power cycle the host, so I could have done much earlier, and if we are facing this again in the future, I would.

  As long as you follow the seller advised for more decent databases (keeping the transaction logs, etc.), don't have good backups, theres no real risk of data corruption.  VMware does not significantly change the i/o path, in order to have the same exposure than on a physical host.

  I still do not understand why the two paths were marked as dead and the host completely lost connection to the SAN, as well as to show finally disconnected in vcenter.

  Well the host went offline because it got stuck in an all-paths-down scenario, which is common for 5.0.  5.1 solves this problem a little.  I don't know why all roads fell, but I suspect that you have a misconfig somewhere... normally you expect at least 4 paths in a system set up correctly on the left.  Check with HP to ensure that you follow best practices.

  Maybe all the IP stack has been corrupted or something?

  Possible, of course, but unlikely.  Never heard before.

  I appreciate the help and the preview, I thought that the problem was a lack of understanding on my part and fully accept it.

  HA and vMotion are complex.  At least now you can go back to mgmt and tell them why he fell more (because it was a failure outside the scope of the software scenario) and may ask for money to build a proper SQL cluster.  Definitely recommend the book of Duncan Epping: http://www.amazon.com/VMware-vSphere-Clustering-Technical-Deepdive/dp/1463658133/ref=la_B002YJMRCY_1_2?ie=UTF8&qid=1363622697&sr=1-2

• Using VMotion with 2 ESX and VCenter

  Hi all

  I just installed with ESX 2 VSphere and & VCenter. I can't use VMotion to migrate a virtual machine running one ESX towards each other.

  My setup is as follows:

  the iSCSI Software initiator.

  data store even shared by 2 facilitators.

  same conf network on the 2 hosts, none vlan used (set to 0):

  • vSwitch0 for the Service console, connected to the network of the company (vmnik0)

  • vSwitch1 for virtual machine network (connected to the company network vmnic1) and VMkernel (for vmotion, connected to the production network: san, vmnic2).

  Error displayed (at 10%): a general error occurred: the VMotion failed because the ESX host failed to connect to the VMotion network, please check your physical network configuration and settings network VMotion.

  vmnic2 on ESX1 is configured with 255.255.0.0 192.168.130.X mask and connected to eth0 on iSCSI SAN

  vmnic2 on ESX2 is configured with 255.255.0.0 192.168.131.X mask and connected to eth1 on iSCSI SAN

  Thanks for help

  alelievre wrote:

  vmnic2 on ESX1 is configured with 255.255.0.0 192.168.130.X mask and connected to eth0 on iSCSI SAN

  vmnic2 on ESX2 is configured with 255.255.0.0 192.168.131.X mask and connected to eth1 on iSCSI SAN

  Two VLAN different connection to the iSCSI SAN. You should have the same subnet, but a different IP addresses (if any) connecting to the San from each host (depends on the SAN)... For example 192.168.130.25 for ESX1 and 192.168.130.30 for ESX2. Unless your SAN network covers actually two subnets on your local network, you create a question where you don't need to. I would also use separate NETWORK card for vMotion traffic and another for iSCSI. Separate them VM traffic too (makes everything cleaner and less chance of collisions and too load performance causing one issues for each other. This is why it is a good idea to have at least four, if not six, physical NIC (or ports) within an ESX/ESXi server.

  VMware VCP4

  Review the allocation of points for "useful" or "right" answers.

• ESXi 4.0 on IBM x 3550 M2 & DS3300

  Hi all

  I am a beginner when it comes to the administration of the server with virtualization. Can someone help me please?

  We are looking at buying a 3550 M2 IBM x server and a storage unit DS3300, deployment of VMware ESXi with four virtual images of Windows Server.

  I thought that the DS3300 could just be used for a fileserver (drive mapped in a virtual machine), but I wonder if ESXi virtual images themselves should be stored here too?

  The x 3550 itself will be 2 x 146 GB HDD (RAID 10 config), while the DS3300 will have 5 x 1 TB SATA disks (RAID 5 config).

  It is generally a good Setup?

  In terms of disaster recovery, I'm a little confused when it comes to what I need VMware products. My thoughts are so far create backup server box which agent Backup Exec 12.5 host for VMware Virtual Infrastructure. I have to install VMware vSphere on this box also so that Backup Exec can see Installing ESXi? I go about it the wrong way?

  My apologies if this message is in the wrong category - mods please move if necessary.

  Thanks for any help!

  Ash

  You really want to use a single switch for the virtual machine and iSCSI. In this case, you might be better to use 4 or more of the NIC in ESX Server, then using 2 NICs with cross cables of 2 connections of the SAN and uses 2 network cards connecting virtual machines to the network switch. Just do 2 vswitches, both with 2 network cards. We can have the virtual machine and the Service Console and the other for 2 VMkernel ports with ips/subnets different (directly connected to the San with the 2 crosscables).

  If it's not too possible (budget wise) then I would just convert the entire SAN to DAS and connect it directly to your ESX via SAS Server (if possible)

• Virtual disk expansion

  I've added four new hard drives at 8 on my ax100 and configured ' DISK POOL 1, include 11 records. A drive is configured as a hot spare. Then, I have expanded the "Virtual Disk 1' to include all the"POOL1 DISC' again. I was expecting the SAN will appear as a 6 to drive in Win2003. However, it proved that I need to format the 4 additional disks and set up as a new partition. I need a shared 6 to disk, not two separate 4TB and shared 2 TB drives. I plugged a different server in the same San using the switch, but it also shows the SAN as two separate partitions.

  Is there an operation that is not destructive to consolidate all readers, both old and newly added, in a huge partition/drive and see it as such in Win2003? It would be difficult to make two backups one 6 to SAN, destroy the virtual disk, recreate a large drive virtual and end of restoration. Help, please. Thank you.

  
  

• Web client - System Configuration node displays 'Unknown' for the Uptime and the workload, no value for IP & Hostname

  When I connect on our vCenter 6 Update 1 device (embedded PSC) via the Web Client with integrated Active Directory ID, select "System Configuration", then select the node for vCenter, summary screen displays all the information IP or host name.  In addition, the status of availability and workload for storage/memory/swap/load of work view all 'unknown '.  See attached photo for reference.

  All values under management-> settings are also empty.

  When I login with [email protected], all the above values are displayed and I can change the settings of the device of vCenter as expected.  This made me suspect a permission problem exists, but I cannot know what SSO group to add our AD is less to enable management or control of the aircraft from vCenter for that it works as expected.

  Already tried to add our accounts to the following groups in SSO under the vsphere.local domain:

  DCAdmins

  SystemConfiguration.Administrators

  ComponentManager.Administrators

  Directors

  This information on the purpose of each group unfortunately did not help me understand which could apply:

  Groups in the field of vsphere.local

  Thank you very much for the help!

  I just did some digging on this myself (we deployed now U2 6.0) after I tried the same things (adding AD users in the SSO domain groups, etc. etc.) without success.

  What I have found is that it is simply a WELL-KNOWN PROBLEM with 6.0 U2 and maybe they'll fix with U3 6.0 when that comes out (later this summer)?  Maybe it'll be 6.5 at that time, with an announcement to the VMworld 2016 or something - who knows.

  The workaround is a joke--suggesting the deployment using only the SSO domain by default.  Well, which is never going to happen naturally, so he says as a workaround is, if you really need to get and display status, etc. from the web client, you simply connect with your [email protected] account that was created at the initial time of installation.

  VMware vCenter Server 6.0 Update 2 Release Notes

  *****

  Failed to configure and view information about the vCenter Server Appliance by using the System Configuration page in the Web Client vSphere with errors
  Connect to the instance of vCenter server in the vCenter Server Appliance with a user who is located in a custom name (different from the default vsphere.local) Single Sign-On the field by using the Web Client vSphere. On the vSphere Web Client home page, click on the System Configuration and select nodesunder the System Configuration. If you try to change the settings, restart or power off a node of the vCenter Server Appliance, the operation fails with one of the following errors: An internal error has occurred - Error # 1009 and Not authorized to use this API . If you click on the summary, monitoror Manage tabs, some device information cannot be displayed.

  Workaround: deploy the vCenter Server Appliance by using the domain of Single Sign-On by default: vsphere.local.

• Need advice on additional modules

  Hello

  I hope that I can help.

  I am writing because in my Department we decided to invest in an ESXi hypervisor Server 5.5.

  We are a company of sale of hardware and software, and I'm sitting in the customer with 4 other colleagues support.

  We will use the ESX Server to install different versions of Windows and versions of our software to test customer projects.

  We all need to connect from our own workplace and create virtual machines from scratch and remove them again after a period of time when they are no longer needed.

  I tried to read about the different modules on VMWare (vSPhere, etc.), but I was not able to find out if it is necessary to have (buy) additional modules that just the hypervisor, so that we are able to do what I described.

  Thanks for any help you can provide.

  Concerning

  Michael

  Yes, if he is just a guest, you don't need a vCenter. You will see that you have no more commit resources to a point that it will impact your performance. If that is supported, you'll be ready to go.

  This documentation will help you in the management and all the other things vsphere-esxi-55-single-host-management-guide

  And also make sure that you are buying equipment that is compatible with VMware ESXi by checking the VMware Compatibility Guide: search system