On the third day in one community (VsSupport, if it is important to someone) an unprecedented drama broke out - it turns out that knowledge from the community can be lost !!! And all why - because millennials (the new reincarnation of indigo children) do not know how to blog themselves, and it is difficult to search in Google.
As a result of the discussion “where the world is heading”, this article on getting started with VMware was born.
Getting Started with VMware and Baby Mistakes
For some reason I don't understand, when working with Vmware, or rather with ESXi and WS, people begin to discuss theory, in isolation from practice. The theory includes both a discussion of the type of hypervisor (the first, the second, not the first, but not yet the second, not a hypervisor at all, and so on), and its impact on performance. An example of such an article is , and in the article they forgot about one (Xen, Virtual PC), they didn’t mention the other at all (Protection ring).
Practice is quite far from this part of the theory, and, first of all, requires verification of completely different things.
So, if you happen to get a job where:
- there is VMware ESXi, vCenter and many other scary words
- no documentation, logins, passwords, backups and nothing at all
- you could not find an unparalleled article
Then you have only one week to prepare the work, and one weekend to check the following things in terms of VMware (not considering backups, the state of the servers themselves, disks, and so on - as described in the fresh excellent ... This:
- IP, logins and passwords from BIOS and IPMI ()
- IP, logins and passwords from the VMware hosts themselves
As they write in VsSupport,
«Passwords (more precisely, their hashes) of ESXi users are stored in the etc/shadow file, which is stored in the local.tgz archive, which is stored in the state.tgz archive.
There are two of them on different partitions sda5sda6«
or you have to read a lot of foreign letters -
- Performance settings of the server itself in the BIOS
As it turned out, for many it is a revelation that a modern server of any company green and flat, therefore, it is able to arrange an extremely mean move - for example, lower performance by several times when one power supply is turned off.
- Checking the location of the ESXi scratch partition according to - And finally, preparation for installing patches for at least ESXi software
PS The note was written under the impression of the question in the community “Should I connect the IPMI port to the network port on the server itself” and complaints that the native basic support of VMware is expensive, and the level of friendliness of support for the torrent-edition in the VsSupport community is clearly low.
Raccoons are taken
Source: habr.com