The other day a drama unfolded in one community (VsSupport, if anyone cares) — 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 manage their own blog, and searching on Google is difficult.
Following the discussions on 'where the world is heading,' this article was born on getting started with VMware.
Getting Started with VMware and Rookie Mistakes
For reasons unknown to me, when working with VMware, specifically with ESXi and WS, people start to discuss theory separate from practice. The theory includes discussions about types of hypervisors (first, second, not the first anymore but not yet the second, or not a hypervisor at all, and so on), and their impact on performance. An example of such an article is — , and in the article about one topic, they forgot to mention (Xen, Virtual PC), and completely overlooked (Protection ring).
However, practice is quite far from this part of the theory and primarily requires the verification of completely different aspects.
So, if you find yourself in a job where:
- there is VMware ESXi, vCenter, and many other scary terms
- there is no documentation, logins, passwords, backups, or anything at all
- you couldn't find a unique article
Then you have just one week to prepare the work, and one weekend to check the following things regarding VMware (not considering backups, the condition of the servers, disks, and so on — as described in the recent wonderful . This includes:
— IPs, logins, and passwords for BIOS and IPMI ()
— IPs, logins, and passwords from the VMware hosts themselves
As mentioned in VsSupport,
«The passwords (or rather their hashes) for ESXi users are stored in the file etc/shadow, which is contained in the archive local.tgz, which is in the archive state.tgz.
There are two of them in different partitions sda5sda6«
or you’ll have to read a lot of foreign characters —
— The performance settings of the server in BIOS
As it turns out, for many people, it is a revelation that a modern server from any company is green and flat, therefore capable of executing a very nasty trick — for example, drastically reducing performance by turning off one power supply unit.
— Checking the placement of the ESXi scratch partition according to And finally, prepare for the installation of patches at least for ESXi according to
P.S. This note was inspired by a question in the community, "Should the IPMI port be connected to the network port on the server itself?" and complaints that the native basic support from VMware is expensive, while the level of friendliness in support for torrent edition in the VsSupport community is clearly low.
Raccoons taken
Source: habr.com
