Redhat Patching Config

I’m reading thru the config docs for configuring BigFix for Redhat patching. If you don’t have a Redhat subscription and instead use an internal repo (RHUI - Redhat Update Infrastructure) how would you configure your bigfix server to point their instead? Would it be similar to the config instructions for pointing to a Redhat satellite server documented here https://www.ibm.com/support/knowledgecenter/en/SS6MER_9.5.0/com.ibm.bigfix.patch.doc/Patch/Patch_RH/t_registering_a_satellite_repository.html

Also, are there any cons to not using the RHSM Plug-in Download manager?

1 Like

Greetings.

If you are using RHUI the endpoint should have a repo config locally. If this is the case you will want to take a look at TaskID: 13 - Enable custom repository support - Red Hat Enterprise Linux. This will tell the endpoints to download patch content from the locally configured repos.

edit

When using the RHSM Plug-in all content is downloaded to the BigFix server first and cached there before being distributed out to relays, and then endpoints. When using the endpoints local yum repo configuration, there is no caching of content and each individual endpoint downloads the patch content. So the con would be:

  • no cached content
  • Endpoints downloading content individually from the vendor

-Matt

2 Likes

You can also use the RHEL Custom Repository Management dashboard to help manage your repos and registrations.

1 Like