Next, you’ll be asked to enter a password for the “admin” user.
The installer will now proceed to install the necessary software for the hypervisor to do its job.
Once it has finished, you will be asked to reboot.
Once you have rebooted your new RHEV-H node, you will see a normal console login prompt. Log in with as “admin” with the password you set in the installer.
You’ll be presented with a few options that need to be configured. Use the arrow keys to navigate.
Lets start with the Network settings. Press the down arrow, then press the right arrow to get into the Network section of the dialog. Change the hostname, add a DNS server and then highlight the network adapter that you wish to configure. I only have one NIC, so I will configure eth0
Press enter once you have highlighted the NIC you wish to configure. I’ve configured eth0 as follows.
Once you have configured the network devices you wish to configure, click Apply.
When you have applied your networking, move on to the next item on the list.
Now, next we have “Remote Access”. You do not have to configure SSH. It is not enabled by default, so if you do not need to access your hypervisors, I recommend leaving it disabled. If you know what you are doing, then go right ahead.
I have enabled SSH access, as I find it very useful for troubleshooting should I ever need to.
Moving on, we have SNMP, Logging and Kernel Dump settings. If you do not know what these are, nor don’t intend to use them, you can skip those sections.
You will also find a section for Remote Storage. This lets you change your iSCSI initiator name on your RHEV-H nodes. As I have set up an NFS cluster, it doesn’t really matter what my initiator name is set to. If you are using iSCSI storage, then I’d recommend changing the initiator name to something more familiar and unique to this specific system.