Author: Sohail Qamar

cloud computing

What is cloud computing?

Using the Internet (“the cloud”) as a distribution medium, cloud computing makes it possible to supply computer resources such as servers, storage, databases, networking, software, analytics, and intelligence more rapidly and cost-effectively.

Because you only pay for the cloud services you use, you can reduce your operational costs, improve the efficiency of your infrastructure, and scale up or down according to your company’s evolving demands.

Benefits of Cloud Computing

Cloud computing represents a significant departure from how organizations have traditionally viewed IT resources. The following are seven of the most common reasons why businesses are turning to cloud computing services:

Cost

Cloud computing reduces the upfront costs of purchasing hardware and software and the costs of building up and running on-site datacenters—server racks, the round-the-clock electricity for power and cooling, and IT experts to manage the infrastructure. It quickly adds up.

Speed

Most cloud computing services are self-service and on-demand, which means that even massive amounts of computing resources may be provisioned in minutes, usually with only a few mouse clicks, offering enterprises a lot of flexibility and relieving capacity planning strain.

Productivity

On-site datacenters typically require a lot of “racking and stacking”—hardware setup, software patching, and other time-consuming IT management chores. Cloud computing removes the need for many of these tasks, so IT teams can achieve more important business goals.

Reliability

Because data may be duplicated at numerous redundant sites on the cloud provider’s network, cloud computing enables data backup, disaster recovery, and business continuity easier and less expensive.

Performance

The most popular cloud computing services are hosted on a global network of secure datacenters that are updated on a regular basis with the current generation of fast and efficient computing hardware. This has various advantages over a single corporate datacenter, including lower application network latency and greater economies of scale.

Global Access

The capacity to scale elastically is one of the advantages of cloud computing services. That implies delivering the proper amount of IT resources—for example, more or less computing power, storage, and bandwidth—at the right time and from the right geographic place in cloud language.

Security

Many cloud providers offer a broad set of policies, technologies, and controls that strengthen your security posture overall, helping protect your data, apps, and infrastructure from potential threats.

Types of Cloud Computing

Not all clouds are created equal, and not every sort of cloud computing is appropriate for every situation. A variety of models, varieties, and services have evolved to assist you in finding the best option for your needs.

To begin, you must decide on the type of cloud deployment or cloud computing architecture that will be used to implement your cloud services. Cloud services can be deployed in one of three ways: public cloud, private cloud, or hybrid cloud.

Public Cloud

Third-party cloud service providers own and run public clouds, which supply computing resources such as servers and storage over the Internet. A public cloud, such as SeiMaxim Cloud, is an example. The cloud provider owns and manages all hardware, software, and other supporting infrastructure in a public cloud. A web browser is used to access these services and manage your account.

Private Cloud

A private cloud is a collection of cloud computing resources used solely by one company or organization. The services and infrastructure of a private cloud are maintained on a private network. A private cloud can be physically located on-site at a company’s data center. Some businesses also pay for their private clouds hosted by third-party service providers.

Hybrid Cloud

Public and private clouds are combined in hybrid clouds, which are linked by technology that allows data and applications to be exchanged between them. A hybrid cloud enables your organization to have more flexibility more deployment options and helps optimize your existing infrastructure, security, and compliance by allowing data and apps to flow between private and public clouds.

Types of Cloud Services

Infrastructure as a service (IaaS)

Cloud computing services in their most basic form. You rent IT infrastructure—servers and virtual machines (VMs), storage, networks, and operating systems—on a pay-as-you-go basis from a cloud provider with IaaS.

Platform as a service (PaaS)

Cloud computing services that provide an on-demand environment for designing, testing, delivering, and maintaining software applications are called platform as a service. PaaS was created to make it easier for developers to construct web or mobile apps rapidly without worrying about setting up or managing the underlying infrastructure of servers, storage, network, and databases.

Serverless Computing

Serverless computing, which overlaps with PaaS, focuses on developing app functionality without having to manage the servers and infrastructure required to do it constantly. The cloud provider handles setup, capacity planning, and server management. Serverless architectures are scalable and event-driven, meaning they only use resources when a specified function or trigger occurs.

Software as a service (SaaS)

Software as a service (SaaS) is a technique of distributing software programs via the Internet on-demand and usually by subscription. SaaS allows cloud providers to host and manage software applications and underlying infrastructure, as well as handle maintenance such as software upgrades and security patches. Users access the app over the Internet, commonly through a web browser on their phone, tablet, or computer.

Cloud Computing Use Cases

Even if you don’t realize it, you’re undoubtedly utilizing cloud computing right now. If you use an online service to send an email, edit documents, view movies or TV, listen to music, play games, or store photos and other files, cloud computing is very certainly at the heart of it.

Although the first cloud computing services were just launched a decade ago, a wide range of organizations—from small businesses to multinational corporations, government agencies to non-profits—are already adopting the technology for a number of reasons.

Here are a few instances of what cloud services from a cloud provider can do today:

Embed Intelligence

Use sophisticated models to help customers engage and gain important insights from the data collected.

Analyze Data

In the cloud, unify your data across teams, divisions, and geographies. Then leverage cloud technologies like machine learning and artificial intelligence to unearth insights that can help you make better decisions.

App Testing

Use cloud infrastructures that can easily be scaled up or down to reduce application development costs and time.

Software on demand

On-demand software, also known as software as a service (SaaS), allows you to provide consumers with the most recent software versions and updates at any time and from any location.

Build Cloud-native Apps

Build, deploy, and scale web, mobile, and API applications quickly. Containers, Kubernetes, microservices architecture, API-driven communication, and DevOps are examples of cloud-native technology and techniques.

Backup and Disaster Recovery

Transferring your data over the Internet to an offsite cloud storage solution that’s accessible from any location and device is a more cost-effective way to protect your data on a large scale.

YUM error: Peer cert cannot be verified or peer cert invalid” or ‘certificate verify failed`

The error produced during the yum update is:

Error: failed to retrieve repodata/-primary.xml.gz
error was [Errno 14] Peer cert cannot be verified or peer cert invalid

Perform the following steps to resolve the yum error:

  • check and correct the date and time of the server.
  • Disable SSL verification by adding sslverify=false in /etc/yum.conf
  • Delete all repos and create a new yum repository.
  • Check /etc/hosts file for any false DNS resolutions of servers.

datacenter

What is a Data Center?

A data center is a physical location where businesses keep their mission-critical programs and data at its most basic level. The design of a data center is built on a network of computer and storage resources that allow shared applications and data to be delivered. Routers, switches, firewalls, storage systems, servers, and application-delivery controllers are all important components of a data center design.

What defines a modern data center?

Nowadays, data centers are vastly different from those they were only a few years ago. Virtual networks that support applications and workloads across pools of physical infrastructure and into a multi-cloud environment have replaced traditional on-premises physical servers.

Data exists and is networked across numerous data centers, the edge, and public and private clouds in today’s world. The data center must be able to communicate with all of these different locations, on-premises and in the cloud. The public cloud, too, is made up of data centers. When applications are hosted in the cloud, the cloud provider’s data center resources are used.

What is the significance of data centers in the business world?

Data centers, in the field of enterprise IT, are meant to support business applications and operations such as:

  • Email communication and file sharing
  • Applications for Productivity
  • Management of customer relationships (CRM)
  • Databases and enterprise resource planning (ERP)
  • Machine learning, artificial intelligence, and big data
  • Communications and collaboration services, as well as virtual desktops

What makes up a data center’s key components?

Routers, switches, firewalls, storage systems, servers, and application delivery controllers are all part of the design of a data center. Because these parts store and manage important business data and applications, data center security is very important when designing a data center. Together, they offer:

Networks and infrastructure

This connects servers (physical and virtualized), data center services, storage, and external connectivity to end-users in places like homes and businesses.

Infrastructure for storage.

Data is the fuel of the modern data center, and it comes from all over the world. Storage systems are used to keep this valuable thing safe.

Computing power

As the heart of a data center, applications are what move it. Applications run on these servers because they have a lot of processing power, memory, local storage, and network connectivity.

How do data centers operate?

Data center services are usually used to protect the performance and integrity of the most important parts of the data center.

A device that protects your network

These include a firewall and intrusion protection to keep the data center safe.

Assurance of the application’s delivery

These mechanisms help keep applications running smoothly by automatically switching servers and distributing the load.

What can you find at a data center?

To support the center’s hardware and software, data center components necessitate a substantial infrastructure. Power subsystems, uninterruptible power supplies (UPS), ventilation, cooling systems, fire suppression, backup generators, and connections to external networks are among these components.

What are the data center infrastructure standards?

ANSI/TIA-942 is the most frequently used standard for data center design and infrastructure. It incorporates ANSI/TIA-942-ready certification requirements, which ensure compliance with one of four data center tiers based on redundancy and fault tolerance levels.

  • Tier 1: The foundation of the site’s infrastructure. Physical events are only partially protected in a Tier 1 data center. It has a single, non-redundant distribution channel and single-capacity components.
  • Tier 2: Component site infrastructure with high redundancy. This data center provides better protection against natural disasters. It has components with redundant capacity and a single, non-redundant distribution path.
  • Tier 3: Site infrastructure that can be maintained at the same time. This data center provides redundant-capacity components and numerous independent distribution methods to protect against practically all physical events. Each component can be updated or uninstalled without affecting end-user services.
  • Tier 4: Site infrastructure that is fault-tolerant. This data center offers the highest levels of redundancy and fault tolerance. Concurrent maintenance and one issue anywhere in the installation without generating downtime is possible thanks to redundant-capacity components and several independent distribution pathways.

Types of data centers

There are many different types of data centers and service models to choose from. Their classification is determined by whether they are owned by a single business or a group of companies, how they fit (if at all) into the topology of other data centers, the computing and storage technology they employ, and even their energy efficiency. Data centers are divided into four categories:

Enterprise data centers

Companies build, own, and run these, which are optimized for their end consumers. The majority of the time, they are located on the company campus.

Managed services data centers

These data centers are managed on behalf of a business by a third party (or managed services provider). Rather than purchasing equipment and infrastructure, the corporation leases it.

Colocation data centers

In colocation (“colo”) data centers, a business rents space within a data center that is not owned by the business. The colocation data center provides the infrastructure, such as the building, cooling, bandwidth, and security, while the company supplies and manages the components, such as servers, storage, and firewalls.

Cloud data centers

In an off-premises data center configuration, data and applications are hosted by a cloud service provider such as Amazon Web Services (AWS), Microsoft Azure, IBM Cloud, or another public cloud provider.

The progression of infrastructure: from mainframes to cloud apps

Over the previous 65 years, computing infrastructure has evolved in three major waves:

  • The first wave witnessed the transition away from proprietary mainframes and toward on-premises x86-based servers operated by internal IT teams.
  • A second wave witnessed extensive virtualization of application-supporting infrastructure. This resulted in more efficient resource use and task mobility across pools of physical infrastructure.
  • The third wave occurs in the present, with the adoption of cloud, hybrid cloud, and cloud-native technologies. The latter refers to cloud-native applications.

A distributed network of applications

This evolution resulted in the development of distributed computing. This is the environment in which data and applications are scattered across various systems, networked and integrated by network services and interoperability standards to operate as a unified environment.

As a result, the term “data center” is now used to refer to the department responsible for these systems regardless of their physical location.

Businesses can opt to develop and manage their own hybrid cloud data centers, lease space in colocation facilities (colos), consume shared computing and storage services, or use public cloud-based services. As a result, apps no longer exist in a single location.

They work in a variety of public and private clouds, as well as managed services and on-premises environments. The data center has grown in size and complexity in this multi-cloud era, delivering the ultimate user experience.

native drivers in esxi

Enabling and Disabling Native Drivers in ESXi

Many new native drivers are included in ESXi 6.5, which replace the older vmklinux drivers. After installation or upgrade, most of the new native drivers are enabled by default.

Because they do not fully support the functions of the corresponding vmklinux drivers, several of the new native drivers are disabled by default. Consider the following scenario:

  • The qflge native driver replaces the vmklinux net-bnx2 driver, although it does not support HW iSCSI.
  • The qfle3 native driver replaces the vmklinux net-bnx2x driver, although it does not support HW iSCSI or SW FCoE.
  • Although it does not support SW FCoE, the ixgben native driver replaces the vmklinux net-ixgbe driver.

Using the vSphere Image Builder, you can enable a native driver in the ESXi installer for new ESXi 6.5 installs.

You can remove the vmklinux driver that corresponds to the native driver from the ISO image using the vSphere Image Builder.

For example, you can use Image Builder to delete the net-bnx2x VIB from the ISO image to enable the qfle3 native driver.

If you discover that the correct driver for the vmnic is not being utilized after a drive upgrade, the following methods will show you how to use vCLI to activate and disable the native drivers.

Enable Native Driver

  • Using the vSphere Web Client or VMware Host Client, put the ESXi host into maintenance mode.
  • To enable one of the native drivers, use the vCLI command.
esxcli system module set --enabled=true --module=native_driver_name
  • Run the following vCLI command to enable the qfle3 native driver, for example:
esxcli system module set --enabled=true --module=qfle3
  • To verify the module details, use the vCLI command.
esxcli system module list
  • Restart the ESXi host.
  • After a reboot, stateless hosts exit maintenance mode automatically.

Exit maintenance mode manually if you enabled a native driver on a stateful host.

Disable Native Driver

  • Place the ESXi host in maintenance mode using the vSphere Web Client or VMware Host Client.
  • Run the vCLI command to disable one of the native drivers.
esxcli system module set --enabled=false --module=native_driver_name

For example, to disable the qflge native driver, run the following vCLI command:

esxcli system module set --enabled=false --module=qflge
  • Run the vCLI command to check the module details
esxcli system module list
  • Restart the ESXi host.
  • Stateless hosts exit maintenance mode automatically after reboot.
  • If you disabled a native driver on a stateful host, exit the maintenance mode.

Find Driver Version

Run the following command to display the driver version.

esxcli software vib get -n native_driver_name

For example, to view the versions of the qfle3 native driver and its corresponding vmklinux driver:

esxcli software vib get -n qfle3

Run the following vCLI command to see which version of the vmklinux driver qfle3 replaces:

esxcli software vib get -n net-bnx2x

esxi quick boot

ESXi Quick Boot Compatibility

Quick Boot is a vSphere feature that speeds up the ESXi server update process. A normal reboot entails a complete power cycle requiring firmware and device initialization. Quick Boot optimizes the reboot path to avoid this, cutting the upgrading procedure time in half.

The Quick Boot feature is not supported by all servers or setups. The support for Quick Boot is conditional on the prerequisites listed below. If the system is supported, you can enable the Quick Boot feature in the Update Manager UI.

Precheck functionality is included in the Quick Boot feature to avoid the use of an unsupported configuration. A standard reboot is conducted if any of these prechecks are not met. Additional requirements defined by the hardware vendor are not checked by our prechecks.

Only if the following conditions are met may Quick Boot be enabled in the Update Manager UI.

General Requirements

  • The host platform should be supported.
  • All device drivers should be supported.
  • Individual checks for the platform and drivers are included in precheck functionality.
  • Additional restrictions defined by an OEM in its own documentation are not covered by quick boot checks.
  • For ESXi 7.0 U2 or later, disabling the TPM after it was enabled may cause server boot failure.
  • For ESXi 6.7, TPM should be disabled, no passthrough devices should be configured for VMs on ESXi host, and no vmklinux drivers should be loaded on the ESXi host.

Resolution

Run the following command from the shell on the ESXi host to see if your system is compatible with Quick Boot:

/usr/lib/vmware/loadesx/bin/loadESXCheckCompat.py

Note: This script will display a list of all issues that prevent Quick Boot from working on the ESXi host.

vsphere hypervisor

ESXi error: Unable to restore system configuration. A security violation was detected

Your ESXi server may fail during boot and display the following errors.

  1. Unable to recover the system configuration.
  2. Failed to decrypt system configuration.
  3. Unable to restore system configuration. A security violation was detected.

Note that quick boot currently does not support TPM.

This article will walk you through troubleshooting your ESXi host’s failure to boot after upgrading to vSphere 7.0 U2 or later. This article aims to assist you in removing the most common causes of this problem by ensuring that the minimum system requirements are satisfied and that the hardware is working properly.

Error Message 1

Check Firmware Security Settings

  • Re-enable TPM 2.0 if it has been disabled.
  • Re-enable UEFI secure boot if it has been disabled.
  • Change the value of the execInstalledOnly boot option back to FALSE if it is set to FALSE (i.e. TRUE).
  • Add “execInstalledOnly=TRUE” to the boot command-line (hit shift+o when mboot starts and a 5-second countdown appears, just after the bios).

If the firmware settings haven’t been changed, either the TPM 2.0 chip isn’t working or the ESXi version being booted isn’t authentic.

Error message 2

This indicates that a valid ESXi version has booted, but the configuration data has been tampered with or is corrupted, making recovery impossible.

Error Message 3

This indicates that we are unable to recover using the recovery key provided. Make certain that the input recovery key is right.

image

How to configure the speed and duplex of an ESXi host network adapter

It is critical to configure the speed and duplex of a network adapter link for reliable network functioning.

This article will show you how to set these parameters on an ESXi host. The recommended parameters for speed and duplex when connecting to a physical switch port via ESXi are given below.

Auto Negotiate

To configure the ESXi host network adapter’s speed and duplex using the vSphere Client:

  • Log in to the ESXi host through the vSphere Client as the root user or an equivalent user.
  • Click the Configure tab and choose the ESXi server host.
  • To access the Physical Adapters tab, click it.
  • Select the network adapter that you want to edit and click Edit.
  • From the dropdown menu, select the appropriate speed and duplex.

The esxcfg-nics command for configuring Network Interface Cards:

esxcfg-nics [nic]

For instance:

esxcfg-nics vmnic0 -a

Following are the command options:

-s –speed speed – Defines the speed at which a particular card shall operate. It must be one of the following values: 10, 100, 1000, or 10000.
-d –duplex duplex – Defines the duplex mode in which a particular card shall operate.
-a –auto – Enable auto-negotiation of the provided NIC’s speed and duplex settings.
-l –list – Display a list of the system’s network interface cards (NICs), together with their current and configured speed and duplex.
-r –restore – Restore network interface configuration from persistent storage. This should be utilized only during system startup and not by users.

Auto Negotiate may or may not be supported or suggested when working with 10 GB Fiber Channel over Ethernet (FCoE) installations. Consult your networking equipment provider or administrator for additional information.

Duplex Mismatch

A typical speed/duplex issue occurs when the duplex settings on two switches, a switch and a router, or a switch and a workstation or server are incompatible. This can arise when the speed and duplex are hard-coded manually or as a result of auto-negotiation difficulties between the two devices.

For the following reasons, auto-negotiation is suggested on ESXi Ethernet Interface cards and physical switch ports:

  • Although hard coding the speed and duplex works and is documented, ESXi has performance difficulties in some circumstances. These performance difficulties are resolved by changing the settings to Auto Negotiate.
  • It fixes iSCSI, vMotion, network performance, and other network-related issues.
  • Duplex options: Although Cisco products only support full-duplex, the IEEE 802.3z standard does allow for half-duplex Gigabit Ethernet. Duplex is negotiated between Gigabit-Ethernet devices as a result of this.
  • Flow Control: Because of the large quantity of traffic that Gigabit-Ethernet may create, it has a PAUSE functionality built-in.

The PAUSE frame is a packet that instructs the far-end device to pause packet transmission until the receiver can handle all of the traffic and empty its buffers. A timer is included in the PAUSE frame, which instructs the far-end device when to resume sending packets.

If the timer runs out without another PAUSE frame being received, the far-end device can resume sending packets. Flow Control is an optional feature that must be discussed. Devices may be capable of sending or responding to a PAUSE frame, but they may refuse to comply with the far-flow-control end’s request.

vmware

[MissingVibError] Cannot find VIB(s) in ESXi 7.0 U2a

Running “esxcli software component apply” fails during an upgrade from ESXi 6.5/6.7 to ESXi 7.0 U2a with OEM Customized Installer due to an error similar to:

[root@localhost:~] esxcli software component apply -d /vmfs/volumes/datastore/amsdComponent_701.11.8.0.15-1_18612107.zip
[MissingVibError]
Cannot find VIB(s) VMW_bootbank_i40enu_1.8.1.136-1vmw.702.0.0.17867351 in the given VIB collection for component Intel-i40en_1.8.1.136-1vmw.702.0.0.17867351
vibIDs = ['VMW_bootbank_i40enu_1.8.1.136-1vmw.702.0.0.17867351']

/var/db/esximg/reservedComponents/ directory has *.xml files which describe metadata of the components, while /var/db/esximg/reservedVibs/ directory doesn’t have corresponding metadata. Here is an example (reservedVibs directory has metadata xml files for VMware Tools component only).

[root@localhost:~] ls -l /var/db/esximg/reservedComponents/
total 24
-r--r--r--    1 root     root           829 Feb 14 05:44 Broadcom-ELX-lpfc-66965244686063130.xml
-r--r--r--    1 root     root           859 Feb 14 05:44 Intel-i40en-8544480375861246145.xml
-r--r--r--    1 root     root           835 Feb 14 05:44 Intel-ixgben-8163255327778063327.xml
-r--r--r--    1 root     root          1131 Feb 14 05:44 MRVL-E3-Ethernet-iSCSI-FCoE--2200338929548531958.xml
-r--r--r--    1 root     root          1004 Feb 14 05:44 MRVL-E4-CNA-Driver-Bundle--7777201015471263370.xml
-r--r--r--    1 root     root           738 Feb 14 05:44 VMware-VM-Tools-498740180989153345.xml

[root@localhost:~] ls -l /var/db/esximg/reservedVibs/
total 4
-r--r--r--    1 root     root          2470 Feb 14 05:44 tools-light--6416824982208603578.xml
-r--r--r--    1 root     root             0 Feb 14 05:44 tools-light--6416824982208603578.xml.orig
-r--r--r--    1 root     root             0 Feb 14 05:44 tools-light--6416824982208603578.xml.sig

The problem has been fixed in ESXi 7.0 Update 2c. The update allows for missing reserved VIBs when “esxcli software component apply/remove” is called.

Follow the procedures below to work around the problem:

  • Copy metadata xml files obtained from OEM Customized Add-ons for ESXi base image to “metadata.zip.” For the example above, this is the desired condition of /var/db/esximg/reservedVibs/. The command “esxcli software component apply/remove” should now work.
ls -l /var/db/esximg/reservedVibs/
total 40
-rw-r--r--    1 root     root          2229 Feb 14 10:32 i40enu--7228415913307840962.xml
-rw-r--r--    1 root     root          2468 Feb 14 10:29 ixgben--7672047929482173857.xml
-rw-r--r--    1 root     root          1944 Feb 14 10:31 lpfc-7342711619553432416.xml
-rw-r--r--    1 root     root          1620 Feb 14 10:32 qcnic-5233142965180253243.xml
-rw-r--r--    1 root     root          2049 Feb 14 10:30 qedentv-6912134702379836384.xml
-rw-r--r--    1 root     root          1763 Feb 14 10:31 qedrntv-646326958601927957.xml
-rw-r--r--    1 root     root          2207 Feb 14 10:32 qfle3--8736531510308215125.xml
-rw-r--r--    1 root     root          1621 Feb 14 10:33 qfle3f--1811338524951531348.xml
-rw-r--r--    1 root     root          1814 Feb 14 10:33 qfle3i-3372514861995197607.xml
-r--r--r--    1 root     root          2470 Feb 14 05:44 tools-light--6416824982208603578.xml
-r--r--r--    1 root     root             0 Feb 14 05:44 tools-light--6416824982208603578.xml.orig
-r--r--r--    1 root     root             0 Feb 14 05:44 tools-light--6416824982208603578.xml.sig

YUM Error: “nothing provides module(perl:5.26)”

YUM displays conflicting requests with modules after installing perl-DBI or perl-DBD-* as shown below.

Problem 1: conflicting requests
- nothing provides module(perl:5.26) needed by module perl-DBD-MySQL:4.046:8010020190322121447:073fa5fe-0.x86_64
Problem 2: conflicting requests
- nothing provides module(perl:5.26) needed by module perl-DBD-SQLite:1.58:8010020190322125518:073fa5fe-0.x86_64
Problem 3: conflicting requests
- nothing provides module(perl:5.26) needed by module perl-DBI:1.641:8010020190322130042:16b3ab4d-0.x86_64

It is impossible to install or enable any other perl stream to enable perl: Module 5.26. Enable perl as follows:

# yum module enable perl:5.26

When the module is activated, the following is displayed:

# yum module enable perl-DBI --assumeno
Dependencies resolved.
==============================================================================================================================
 Package                       Architecture                 Version                       Repository                     Size
==============================================================================================================================
Enabling module streams:
 perl                                                       5.26                                                             
perl-DBI                                                   1.641                                                            

Transaction Summary
==============================================================================================================================

Operation aborted.

However, when you install content out of the module, you do not get the “perl:5.26” module enabled.

# yum install perl-DBI
Dependencies resolved.
==============================================================================================================================
 Package                    Arch       Version                                     Repository                            Size
==============================================================================================================================
Installing:
 perl-DBI                   x86_64     1.641-3.module+el8.1.0+2928+fafc4afc        centos-8-for-x86_64-appstream-rpms     740 k
Installing dependencies:
<snip>
Enabling module streams:
 perl-DBI                              1.641                                                                                 

Transaction Summary
==============================================================================================================================
Install  44 Packages

Total download size: 13 M
Installed size: 38 M
Is this ok [y/N]: n
Operation aborted.

If the above is allowed, the following operations will have unmet modular dependencies, as shown by the.

# yum check
Updating Subscription Management repositories.
Modular dependency problem:

Problem: conflicting requests
- nothing provides module(perl:5.26) needed by module perl-DBI:1.641:8010020190322130042:16b3ab4d-0.x86_64

yum

YUM Error: [Errno 14] yum fails with HTTP/HTTPS Error 404

When trying to install/update packages using yum on the client-server, it is failing with the below errors.

[Errno 14] HTTP Error 404: Status 404
[Errno 14] HTTPS Error 404 - Not Found
[Errno 14] HTTP Error 404: Not Found

This problem typically happens when a client system can communicate with a server but is unable to locate or access the requested package on the server.

  • Try to clear the cache on the client machine to see whether this problem is caused by a corrupted cache as follows.

rm -fr /var/cache/yum/*
yum clean all

  • If the previous steps don’t work, try removing or commenting out the following line in /etc/yum.conf and clearing the yum cache once more.

distroverpkg=redhat-release

  • Check the yum repository and install the package.
  • Check for yum check-update output