Administrative Distance of different Routing Protocols | Networks

Route Source	Default Distance Values
Connected interface	0
Static route	1
Enhanced Interior Gateway Routing Protocol (EIGRP) summary route	5
External Border Gateway Protocol (BGP)	20
Internal EIGRP	90
OSPF	110
Intermediate System-to-Intermediate System (IS-IS)	115
Routing Information Protocol (RIP)	120
Exterior Gateway Protocol (EGP)	140
Unknown*	255

Low administrative distance takes precedence in route distribution.

Suppose we have 2 routing protocols RIP and EIGRP; 120 and 100 respectively. EIGRP will be preferred over the RIP because of the administrative distance is 100.

However, Administrative distance can be changed to take precedence

For instance, lets enable RIP route by using distance command to modify distance

Router1#show ip route
Router1(config)#router rip
Router1(config-router)#distance 90

Now check again with show ip route command
You will see that RIP has taken precedence over EIGRP.

Installing OpenShift on bare metal using Full Control (UPI) – Quick Step-by-Step Guide | Maximo

This guide explains how to deploy OpenShift on Bare Metal (UPI) in a VMware environment using a Service Node, Bootstrap Node, Control Plane, and Worker Nodes.

In VMware with Service Node, Bootstrap, and Master/worker nodes.

Log in to Red Hat Console: 

Goto - > Clusters -> Data Center -> Other Datacenter Options -> (Bare Mtail /x86_64)

References:

1	GitHub - ryanhay/ocp4-metal-install: Install OpenShift 4 on Bare Metal - UPI
2	How to install OpenShift 4 on Bare Metal - User Provisioned Infrastructure (UPI)
3	How to Install OpenShift 4 on Bare Metal through User Provisioned Infrastructure (UPI)
4	RedHat OpenShift Bootcamp | HA Cluster Deployment with UPI method part1

 

Requirements:

0	Service node/bastion	Any linux, I am using Rocky	2 interfaces: Eth0 , eth1 Eth0 for external using NAT automatic ip.     Eth1 is internal hostonly. (192.168.22.1/24)
	Services	Firewall/router, DNS, webserver, ingress/LoadBalancer,dhcp,
	Openshift Installer	Installer script from console.redhat
	Pull secret	From redhat console
	Cli agent tools	Client tools
	Redhat core os boot iso file to boot	Rhcos*.io
	Actual Redhat core OS raw.gz file	Rhcos*.raw.gz
	Ignition files  (16-22 hours of life after generations)	Run ignition (.ign) file with os file (raw.gz ) files on nodes with coreos-installer command
	Timezone	UTC, same as coreos by default
	NAT, IP forwarding	Enable using firewalld	From internal to external
1	Bootstrap node	based on the installer	nmtui :ip 22.200, gw 22.1, ns: 22.1, search domain: ocp.lan
2	Masters	based on the installer	nmtui :ip 22.201-203, gw 22.1, ns: 22.1, search domain: ocp.lan
3	Workers	based on the installer	nmtui :ip 22.211-213, gw 22.1, ns: 22.1, search domain: ocp.lan
4	Vmware vmx files	In all VMs' vmx files, add this before booting	Disk.EnableUUID = "TRUE"
5	Vm storage	Check drive type ·         SCSI / SATA controllers → Devices show up as /dev/sdX. ·         NVMe controllers → Devices show up as /dev/nvmeXnY	lsblk

My VMWare Settings (Virtual Network Editor)

To simulate a production-like isolated OpenShift environment, I used a host-only network as a private subnet accessible via a bastion (service) node. The bastion has an additional NAT interface (vmnet8) to share the host’s internet, acting as a gateway for the OpenShift nodes.