Recent days in one community (VsSupport, if anyone cares) unfolded an incredible drama — it turns out that knowledge from the community can be lost!!! And why is that — because millennials (the new reincarnation of indigo children) don't know how to run a blog themselves, and searching on Google is difficult.
As a result of the discussion on 'where the world is heading,' this article came about on how to get started with VMware.
Getting started with VMware and common beginner mistakes
For some unknown reason, when working with VMware, specifically with ESXi and WS, people start discussing theory, detached from practice. The theory involves discussions about the type of hypervisor (first, second, no longer first but not quite second, not a hypervisor at all, and so on), and its impact on performance. An example of such an article is — , while forgetting to mention one thing in the article (Xen, Virtual PC), another thing was completely overlooked (Protection ring).
However, practice is quite far removed from this part of the theory and primarily requires checking entirely different things.
So, if you happen to start a job where:
- there is VMware ESXi, vCenter, and many other scary words
- there is no documentation, logins, passwords, backups, and nothing at all
- you couldn’t find a unique article
Then you have only one week to prepare your work, and one weekend to check the following things regarding VMware (not considering backups, the state of the servers themselves, disks, etc. — as described in the fresh excellent . This includes:
— IP addresses, logins, and passwords for BIOS and IPMI ()
— IP addresses, logins, and passwords for the VMware hosts themselves
As mentioned in VsSupport,
«Passwords (or rather their hashes) of ESXi users are stored in the etc/shadow file, which is located in the local.tgz archive, which is found in the state.tgz archive.
There are two of them on different partitions sda5sda6«
or you'll have to read a lot of foreign letters —
— Performance settings of the server itself in BIOS
It turns out, for many, it is a revelation that a modern server from any company is green and flat, therefore capable of orchestrating a remarkably underhanded move — for example, drastically reducing performance when one power supply is turned off.
— Checking the placement of the ESXi scratch partition according to — And finally, preparing for the installation of patches for at least ESXi according to
P.S. Nota a fost scrisă sub impresia întrebării din comunitate "Trebuie să conectezi portul IPMI la portul de rețea de pe server?" și a plângerilor legate de faptul că suportul basic oficial VMware este scump, iar nivelul de prietenie al suportului pentru torrent-edition în comunitatea VsSupport este evident scăzut.
Racoonii au fost luați.
Sursa: habr.com
