Give advice on the autonomous role on ESXi 4.1

function setNotesToolTip() {
     this.xOffset = 0; // x distance from mouse
     this.yOffset = 10; // y distance from mouse
jQuery("div.short-notes").hover(
     function(e) {
          var insideText = jQuery("div.long-notes",this).html()
          this.top = (e.pageY + yOffset);
          this.left = (e.pageX + xOffset);
          $('body').append('
' + insideText + '
' );
          $('div#notes-tooltip').css("top", this.top+"px").css("left", this.left+"px").delay(500).fadeIn("fast");
     },
     function() {
          jQuery("div#notes-tooltip").fadeOut("false").remove();
     }
).mousemove(
     function(e) {
          this.top = (e.pageY + yOffset);
          this.left = (e.pageX + xOffset);
          jQuery("div#notes-tooltip").css("top", this.top+"px").css("left", this.left+"px");
     }
)
}

<style>
div#notes-tooltip {
    background-color: #F8F8F8;
    border: 1px solid #AAAAAA;
    border-radius: 3px 3px 3px 3px;
    box-shadow: 0 4px 8px rgba(0, 0, 0, 0.25);
    position: absolute;
    width: 420px;
    padding: 4px;
}
</style>

Kind regards
Hari

Advice on the ESXi server conversion

Hi all - I have a project, I work on the weekend and hoped comments before you start. I have a HP Xeon bicoeur recently purchased Windows Server 2003 running server is installed directly on the hardware (no virtualization yet). I want to convert the VMWare ESXi 4.0 running server and run the same operating system on this material. Here's the tricky part. I want to run ESXi on the same computer, Windows Server running on right now. I understand that VMWare converter exists for this, and it would be no problem I got a 2nd ESXi Server I could use as the destination for the new virtual machine running. But I have only 1 server. And the converter interface looks like it requires a host ESXi to connect to, when converting from one physical machine to a virtual machine. (please, correct me if I'm wrong)

My plan to achieve this is:

1. temporarily install ESXi on another computer

2. use VMWare workstation to converter to convert the physical operating system to a virtual machine running on the ESXi host temp

3. carefully test the new virtual machine!

4. download files of the virtual machine to the host temp to converter with vSphere client workstation

5. clean the hard disks on HP Server, install ESXi

6. download VM files on HP Server with vSphere client

7. I hope that new start VM brilliant without problem

8 go back home and get some sleep!

If anyone has any input on this point, known pitfalls to avoid, or how to go faster, please let me know!

To make it a little easier (you save setting up ESXi twice) just to use VMware workstation and VMware converter (even just an eval version will do). Then...

1. install VMware workstation and VMware converter on a decent existing computer (that has enough cpu/ram to support the windows server).

2. use the windows VMware converter for P2V server in VMware workstation.

3. test the virtual windows server 2003 works correctly

4 install ESXi on HP Server and configure it.

5 use the converter once more to shoot on the virtual machine in the front of the workstation in an ESXi virtual machine format hardware version 7.

Andy, BSc (Hons)

VCP 3/4 / vExpert / MCP / MCTS / TCSP

Help, Guides and info http://www.VMadmin.co.uk

If you have found this information useful please give points by using the buttons at the top of the page accordingly.

Best network design... Need advice on the best use of NIC

I'm new to the concept of Distributed Switch so I need advice.

Our current environment is the result of a vCenter 4.1 and ESXi 4.1 Enterprise Plus, but we are just using the standard vSwitch (1 for vMotion/Console and 1 for virtual machines).  When the distributed switch came out, we were warned that a vDSwitch could cause us problems if the server vCenter or database is down.  We could not connect directly to the host and make network changes because the vDSwitch is set in the database.  That's why we stayed with the Standard vSwitch only.

Our farm is quite small, only 5 hosts but we run around 100 mV in this regard.

We use currently servers HP DL385 G7, which have 4 cards integrated network, and we have a map of installed NETWORK 4 port card.

I use the NETWORK 4 EtherChannel ports and trunk card to our virtual machines.

I am currently using only 1 network card integrated for vMotion and 1 for the Service Console and they all have two of the other defined as secondary.

This configuration has worked very well for us, but I realize that the latest version of ESXi has some new features that we could use.

NEW CONFIGURATION

I'll put up a new vCenter 5 and ESXi 5 environment and I am considering using the switch distributed instead of the usual vSwitch we use.  I'm also eager to take advantage of the multiple NIC vMotion.  All our cards are 10/100/1000 MB capable... No. 10 GigE.

I think... use that map 4 NETWORK ports for my EtherChannel/trunk for just as our virtual machine before, but this would be set to vDSwitch1

The mixture of my 4 other integrated ports, it's causing me grief.  Should they be on a standard vSwitch or vDSwitch?  Use 2 ports for vMotion and 2 for the Console?  I really thought to use 3 ports for vMotion and 1 Console port.  I could put the Console port to use one of the vMotion ports such as adapter of standby is... I'm so confused freaking!

Any recommendations on how I should put up?

Hello

Given that you can't split your vmnic for each vSwitch I would recommend either keep configuration simular with the knoweldge if a whole nic fails, you will take a failure or as autumn has already been mentioned on 'Origin Port ID'. Lets do this out and give a little better example

Current configuration

vSwitch0

VMNIC0 - NETWORK interface integrated - Service Console

VMNIC1-Onboard NIC - VMotion (different IP or VLAN?)

VMNIC2-Onboard NIC - VMotion (different IP or VLAN?)

VMNIC3 - NETWORK interface integrated - VMotion (eve of Console of Service) (different IP or VLAN?)

vSwitch1

VMNIC4 - extension PCI NIC - Etherchannel trunk - PortGroup - VMNET

Extension VMNIC5 - PCI NIC Etherchannel trunk-PortGroup - VMNET

Extension VMNIC6 - PCI NIC Etherchannel trunk-PortGroup - VMNET

Extension VMNIC7 - PCI NIC Etherchannel trunk-PortGroup - VMNET

Now, to captured to eliminate any single point of failure that you could do is break your Etherchannel trunk and back this vSwitch from Port ID and Setup VMNIC2, VMNIC3, VMNIC4, VMNIC5 as vSwitch1 for your VMNET. Then the cable to multiple switches eliminate any single point of faiulre. If your standard configuration would look like this

vSwitch0

VMNIC0 - on - Board Service Console

VMNIC1 - Board - Vmotion

VMNIC6 - extension PCI NIC - Vmotion

VMNIC7 - extension PCI NIC - Vmotion (standby Service Console)

vSwitch1

VMNIC2 - VMNET

VMNIC3 - VMNET

VMNIC4 - VMNET

VMNIC5 - VMNET

So to finish any request for psyhical nics on this particular configuration the Port ID of origin essentially around robins. If during your first VM is online it will be use VMNIC2 and nic forever, until a failure, in which case he will grab the next nic online. When your second VM is online it will use VMNIC3 forever, until a failure and so on. This still will give you around the same way through to as far as networking is concerned. However if you are attached to the trunk, etherchannel 4 GB and can obsorb a failure in case of failure, the network card 4 ports can stay.

Distributed switching Setup

Allows you to see how you can switch to distributed switching

Let's start first of all, you can have EVERYTHING in switches distributed even the service console port if you wish. The resason why some people do not like to do this with the service console port is because IF your database is broken you cannot make any changes to the distributed switch. However it will not prevent a feature to your distributed it switches simply means, you can change them. Also if just getting worse and your DB has been declining for some time and you REALLY need to make a change to the service console port you can go into the console and change back to a standard vSwitch if need be. This allows the said look at some standard configs, you can work

vSwitch0 (Standard)

VMNIC0 - Service Console Port (Port Original ID or standby)

VMNIC4 - Service Console Port (Port Original ID or standby)

vSwitch1 (Standard)

VMNIC1 - Vmotion

VMNIC5 - Vmotion

Distributed switch

VMNIC2 - VMNET

VMNIC3 - VMNET

VMNIC6 - VMNET

VMNIC7 - VMNET

Now this config using originating port ID and breaks your etherchannel if you want to keep your configuration with the etherchannel it can look like this

vSwitch0

VMNIC0 - NETWORK interface integrated - Service Console

VMNIC1-Onboard NIC - VMotion (different IP or VLAN?)

VMNIC2-Onboard NIC - VMotion (different IP or VLAN?)

VMNIC3 - NETWORK interface integrated - VMotion (eve of Console of Service) (different IP or VLAN?)

Distributed switch

VMNIC4 - VMNET

VMNIC5 - VMNET

VMNIC6 - VMNET

VMNIC7 - VMNET

Other changes to the configuration may also put the vmotion in distributed witch the VMNET but you would to VLAN, or you could create a second Distributed switch and put it as long as there are 2 network cards. It can go either way. The main advantage of a distributed switch is that it brings all of your settings with you in any host. So trade ect all your VIRTUAL networks is really easy to reproduce if a new host is brought online, all you have to do is to add the new host network cards in the distributed switch and your config is done. With that in mind lets look at the service console. This console is always configured on EACH Setup program that out you of the box if not that you really need to have these parameters transported on several hosts that is another reason why most people just don't. VMotion is up to you, I have seen and configured two ways, it all depends on how simple you want to keep it or think of switching / vlaning / port of groups.

If you have any questions please let me know, I hope this has helped

Need some advice on the best way to do specialized source distribution

I need to give a customer a labview block, they can use our material in their own labview code that will read the (encrypted) data net senor off the coast and the flow of data in a form usable output.  I built a vi that can be used in a loop, a bit similar to the block of canned labview data acquisition that can be used to acquire data from products OR.

There are many sophisticated (and secret) algorithms going on in the background which make sense data and translate them into a usable data table, but also configure the hardware itself. Accordingly the only final vi I prepared to distribute the client makes use of Subvi about 20. Almost none of these subvis could be ideally be reconverted in plain code in main vi, nor what I want to do this.

The rules of the game is the following: I want to give him the block I created to use its own code, without him to see what's happening inside the vi.  I can deny him access to the block diagram/s, no problem, but I don't want to give him access to the subvis, to use, or even to know their names - preference they would be hidden or otherwise pre-compiled. Preferably I would just give him the main block only, perhaps with some support files that would be entirely opaque to him.

Looking for advice on the best way to go. There is an elegant solution to this problem? For example, it would be better to compile the block as a .dll file, and then write a wrapper vi any?

Have you thought of creating a packed library? You can also password protect your code. You can delete the distributed code block diagrams. You can use a combination of the above as well.

Configuration of Vlan SG300-20 for the desktop and server ESXi

Hello

I'm fairly new to network so please, be gentle.  I'm setting up a number of VLANs for my lab at home.

I recently moved jobs and took an Oracle Apps of the Middleware & role has therefore need to start picking up the Apache, e-Business Suite, etc. of the load balancers so need to segragate my network to allow different configurations, I want to install in my lab ESXi.

My setup is detailed below:-

I have a router of dryatek 2860n which is my entry for the installation of the internet on IP 192.168.1.1

My Cisco switch has been set to 192.168.1.2 and the installer to use the 3 layer.

I have a number of PCs connected to my switch I want to use to administer my ESXi server and have access to the different VLANS.

VIRTUAL LANs, I need are the following

My esxi server has two network interfaces that will have traffic MGMT, Public and private configured as virtual interfaces in ESXi and one that runs my traffic of storage/nfs mounts on a QNAP NAS, I want to make it work on my network

Here is how I have the ports

G13-20 are my workstations that need to be on VLAN 12, but must also be able to connect to 13, 14, 15, 20, SSH, RDP, NFS

G9 is the Interface of MGMT of ESXi who need to have traffic on VLAN 13, 14, 15

G10 is ESXi storage Interface that needs to access the VLAN 20 only

G7/g8 are connect to QNAP that ideally I want to configure as a LAG.   When I get more interfaces in my ESXi Server I'll finally the team to match.

I set up an ip interface in my CISCO switch to 10.0.12.1 as gateway to my workstations and created a static route in my router to allow traffic to the switch.  This does not quite yet.

I also installed a default route to 0.0.0.0

I followed a number of guides, but struggling to get my head around concepts and how to achieve the above configuration.

Ideally, I want to configure this through the CLI as Ive had no end of problems with the web interface of the Cisco switch.

I believe need g9 of trunk, and other ACCESS is it exact.

How the workstatations to access the other VLAN?

Any help would be appreciated

Thank you

Paul

Hi Paul, to break it down a little.

Host A connects to port 13.

config t

int gi0/13

switchport mode access

switchport access vlan 12

ESXI connects to port 9

config t

int gi0/9

switchport mode trunk

switchport trunk allowed vlan add 13-15 (keep in mind this vlan 1 is unmarked here and is the IP of your server interface)

This translates

ESXI = 192.168.1.x 24 gateway 192.168.1.2

interface vlan 1

IP 192.168.1.2 255.255.255.0

no ip address dhcp

Host A = 10.0.12.x 24 10.0.12.1

interface vlan 12

name of the workstations

10.0.12.1 IP address 255.255.255.0

With this basic host configuration at shall communicate to ESXI (no other config on the switch)

If please try to get the connectivity of base first, then can work on the roads and DHCP.

-Tom
Please mark replied messages useful

Calculation of the margin in an ESXi

Dear members of the community,

I have to install an HBA in my ESXi host in the cluster. I have a 3 cluster nodes. As part of the validation test, I want to determine whether the other nodes in the cluster has enough memory and resources to accommodate guests of computer virtual before taking the ESXi in maintenance mode and power off. How can I determine this?

I want to avoid any situation during the Management window where other nodes of ESXi raise a flag for the vmotion, that they are tight and cannot accommodate any virtual machines...

Would appreciate suggestions on this subject

Rahul-

Hi friend

In my view, there is no tool for it determine automatically. You should manually see (in the page summary of ESXi host) that the amount of memory/cpu is used by other hosts, note down + mem/cpu is used by the host you want to put in Mr. that will give you an idea just on all the virtual machines that you can be accommodated on all other hosts.

In addition to this. you need to verify HA/DRS (especially DRS threshold + DRS rules) / DPM/SDR configuration so that these features will not be affected.

Help, I changed the password of root ESXi via powerCli, now I can not connect with the web client or the console.

Help, I've changed the root ESXi via powerCli password, now I can not connect with the web client or the console, but I can still connect to powerCli. The command I used was;

SE connect-VIServer esxihostname-user root - password newpasswd

This production network btw, I have connected to each host and run the above command, these ESXi hosts are not on a domain

y at - it something I have left out. I really appreciate any assistance that you people can provide.

Thank you, Joe

It is probably a longshot, but a lot of things in the land of windows is not sensitive to capital letters as Unix is.  I wonder if your new password you put through powerCLI mixed uppercase in it and if the capitalization was abandoned by command windows powerCLI Analyzer, or he interpreted as all capitals or something.   If you can still get through the powerCLI you could try to reset the password again to something simple without capitalization mixed case and if your password on ESXi strategy requires a special character, try something different than a "$", like a "_" (I find that a '_' is less likely than some other special characters (, as a '-' or a ' / ' to cause problems with analyzers.).

Edit:

Another thing, you can try before playing with the password once again, is to create a different username ESXi using powerCLI and see if the password ends up what you think, it should be, and if you can get with the client vsphere using it.  In this way, you can find out if there are some problems with certain characters or Cap through command powerCLI Analyzer without losing your remaining root by powerCLI access.  After some tests, you can understand what went wrong with your initial password change and may be able to fix it with less risk of losing access.  I also assume that you can not create a new username on ESXi who is able to change the root password no matter what authority give you it, otherwise, you could create a new username with PowerCLI, then connect to the client vsphere with it and change the password to root from there.

Advice on ESX 4.1 vs ESXi 4.1

We have two boxes of vSphere, we execute ESX 4.1.0 348481 & another running ESXi 4.1.0 260247.

With gradually VMware ESX and the path of ESXi, I wondered if we should move the box ESX to ESXi.

If it is a good idea, is the simple process to boot from CD ESXi and have an installation replaces the existing installation of ESX,

or would it be a clean install, which requires to move virtual machines on ESX box to another server temporarily and your choice

When the upgrade is complete?

Thank you

Alex

Yes, 4.1 was the last exit for ESX classic. That said, support for classic that ESX will be there for some time.  So I think that having already an ESXi host in your environment and you feel sufficiently comfortable with it, then I say go to ESXi.

In my opinion, I would evacuate all guests and do a full rebuild.  This will also give you the opportunity to update firmware, if necessary.

The error of the user role assignment

db_user start a new session after the GRANT?

Role of ESXi 4.1 ROOT have accidentally changed NoAccess. Help!

Hello world.

We have an ESXi 4.1 server. One of our administrator accidentally changed the role of the user root of vSphare NoAccess.
The big question is to know how to restore the role of the root user, because there is no other way to control our server.
(Of course we have if necessary physical controll, so we could do something with the consol)

It is possibble sort to recover the root user or need to reinstall the server?
(DCUI have the Administrator role...)

Thanks in advance.

Found and tested solution:

We applied the menu item reset the configuration of the system , that re added all the VM-s.

It has solved all of our problems in 10 minutes.

Thanks for all tips.