Oracle Linux Virtualization Manager 8.7 Installation on Physical Server

-

we have recently Deployed the Oracle Linux Virtualization Manager 8.7 version on HP ProLiant Server, I would like to make a process what we have followed to bring up the Physical Oracle Linux Virtualization server.

This  similar to ESXI in VMware server, on ESXI we will install the ESXi with ISO/Network Installation Methods.


We have downloaded the Oracle Linux Virtual Manager 8.7 OS ISO from Oracle Site. Copied to the remote terminal server.


Datacenter Team has racked the servers and  provided the ILO IP's and User Names to Proceed with Infra Activities.


We have tried to Login to Consoles of the servers , we had a firewall issue to access to consoles over the https.

we worked with Network team to Open the ports  at firewall level, then we were able to login & Access the Consoles.


Step 1 - we have done with Changing the Default ILO Credentials to standard Credentials as per the Company standards.

Step 2 - Next step we have Downloaded the HP Provided custom Firmware Latest SPP ISO, then flashed the firmware through ILO.

Step 3 -  we have opened the html console of the server and attached the local ISO, which we have downloaded from Oracle site with 8.7 OLVM OS.

Step 4 -  we have Reset the server to booth from ISO, while booting we have selected the F11 to Boot Options. then selected CD/DVD to boot up

Step 5 - its a standard Linux Installation procedure we have followed, it booting from ISO, asked few options to proceed further installation.

we have selected the install from ISO -  then Network Information - OS Install  Server type- Partitions -  root password, the it proceed with Installations.

Finally OS Installed, we logged into the OS  updated the correct DNS and ntp and other configurations were modified.

we can directly Install apps on Oracle Linux 8.7 and we can use it as a  Physical server. but our purpose is to have KVM Install on top of Oracle 8.7 and use it as a KVM Hypervisors similar to ESXi.

for now we have  just Installed the  Physical server equivalent to Normal Linux Server. 


Next step we have to Install the KVM Software equivalent to ESXi  Server in VMware.  will continue Further with KVM Installations and what problems we have Faced will give you detailed stay tune for next Post

Check Next Post KVM Install and Configuration on Oralce Linux  8.7




Comments

Post a Comment

Popular posts from this blog

Veritas Cluster Server (VCS) Commands - Cheat Sheet

-
 LLT and GRAB VCS uses two components, LLT and GAB to share data over the private networks among systems. These components provide the performance and reliability required by VCS. LLT LLT (Low Latency Transport) provides fast, kernel-to-kernel comms and monitors network connections. The system admin configures the LLT by creating a configuration file (llttab) that describes the systems in the cluster and private network links among them. The LLT runs in layer 2 of the network stack GAB GAB (Group membership and Atomic Broadcast) provides the global message order required to maintain a synchronised state among the systems, and monitors disk comms such as that required by the VCS heartbeat utility. The system admin configures GAB driver by creating a configuration file ( gabtab). LLT and GAB files /etc/llthosts --> The file is a database, containing one entry per system, that links the LLT system ID with the hosts name. The file is identical on each server in the cluster. /etc...
Read more

Solaris 11.4 Network Administration Cheatsheet

-
 Here we discuss the Commonly used Network Commands for Solaris network Administration. How to list the Physical Network card's information : # dladm show-phys LINK            MEDIA         STATE      SPEED  DUPLEX    DEVICE net0            Ethernet      down       0      unknown   i40e0 net1            Ethernet      down       0      unknown   i40e1 net2            Ethernet      down       0      unknown   i40e2 net3            Ethernet      down       0      unknown   i40e3 net4            Ethernet    ...
Read more

Oracle Logical Domains (LDOM) Back up & Restoration from Backup Files

-
Saving Domain Configurations for Future Rebuilding The basic process is to save the resource constraints information for each domain into an XML file, which can then be re-issued to the Logical Domains Manager, for example, after a hardware failure to rebuild a desired configuration. Restore a Domain Configuration From an XML File ( ldm add-domain )  works for guest domains, but not for the control ( primary ) domain. You can save the  primary  domain's constraints to an XML file, but you cannot feed the file back into the  ldm add-domain -i  command. However, you can use the  ldm init-system  command and the resource constraints from the XML file to reconfigure your  primary  domain. You can also use the  ldm init-system  command to reconfigure other domains that are described in the XML file, but those domains are left inactive when the configuration is complete. The method that follows does not preserve actual bindings, only the ...
Read more