RH403 - ch03s02

Bookmark this page

Guided Exercise: Register and Configure Content Hosts

Register a pair of systems to Satellite Server by using both subscription management models, to differentiate the benefits of each of them.

Outcomes

Register a system with Satellite Server.
Attach the registered system to a subscription without SCA enabled.
Use the benefits of SCA-enabled registration.

As the student user on the workstation machine, use the lab command to prepare your system for this exercise.

[student@workstation ~]$ lab start clients-register

Instructions

Important

The Operations organization is configured with Simple Content Access (SCA), which simplifies client software entitlements by eliminating per-client subscription attachments. The Marketing organization is not configured for SCA, and continues to use legacy per-client entitlements by attaching subscriptions. In this exercise, you register the serverc client system to the non-SCA Marketing organization, and the servera client system to the SCA-enabled Operations organization, to compare the two software entitlement methods.

[student@workstation ~]$ ssh student@serverc
[student@serverc ~]$ sudo -i
[sudo] password for student: student
[root@serverc ~]#

Verify that the serverc system is not registered.
1. List the system's subscription status. If the status is Unknown, then the system is not registered.
```
[root@serverc ~]# subscription-manager status
+-------------------------------------------+
   System Status Details
+-------------------------------------------+
Overall Status: Unknown

System Purpose Status: Unknown
```
2. If the status is other than Unknown, such as Disabled or Invalid, then the system was previously registered and must be cleaned first. Skip this cleaning step if your status is Unknown.
```
[root@serverc ~]# subscription-manager clean
All local data removed
```

Install the katello-ca-consumer-latest package from your Satellite Server.

[root@serverc ~]# dnf localinstall \
http://satellite.lab.example.com/pub/katello-ca-consumer-latest.noarch.rpm
...output omitted...
Is this ok [y/N]: y
...output omitted...
Complete!

Register serverc to Satellite Server. Specify the Marketing organization and the Development/MarketingServerBase environment and content view.

[root@serverc ~]# subscription-manager register \
--username admin --password redhat \
--org Marketing --environment Development/MarketingServerBase
Registering to: satellite.lab.example.com:443/rhsm
The system has been registered with ID: e3080bbf-7d26-43f9-951b-e5c6522c0197
The registered system name is: serverc.lab.example.com

Verify that the serverc client system is registered.
1. List the system's subscription status.
  Note
  The following output is correct for an initial client registration in a non-SCA organization. The Invalid status indicates that the installed Red Hat products are not entitled by a valid subscription. You entitle the products by attaching subscriptions to the client system in a later exercise step.
```
[root@serverc ~]# subscription-manager status
+-------------------------------------------+
   System Status Details
+-------------------------------------------+
Overall Status: Invalid

Red Hat Enterprise Linux for x86_64:
- Not supported by a valid subscription.

System Purpose Status: Not Specified
```
2. List the repositories that are available to the serverc client system. No repositories are entitled yet.
```
[root@serverc ~]# subscription-manager repos --list
This system has no repositories available through subscriptions.
```
Use the web UI to verify that the serverc system was successfully registered to Satellite Server. Set the client system's RHEL release version to 9 and add the available subscriptions.
1. Log in to the web UI, https://satellite.lab.example.com, as admin with redhat as the password.
2. In the upper-left corner of the web page, set the organization to Marketing. Set the location to Any Location.
3. Click Hosts → Content Hosts. Verify that the serverc system is listed as a registered host on the Content Hosts page. Click the serverc.lab.example.com link to display the serverc.lab.example.com page. A warning notifies that this organization is not using Simple Content Access.
4. Locate the Content Host Content section of the page. Select 9 from the Release Version list, and then click Save. Verify that the Content View is MarketingServerBase and that the Lifecycle Environment is Development.
5. To entitle the system's Red Hat products, attach the available subscriptions to serverc. On the serverc.lab.example.com page, click the Subscriptions tab. The Status field states that this system's Red Hat products are Unentitled. Click the Add tab below Subscription Details. Select the checkboxes for Red Hat Enterprise Linux Server, Standard (Physical or Virtual Nodes), and then click Add Selected.
6. Click the List/Remove tab below Subscription Details, and verify that the added subscriptions are listed. Click the Run Auto-Attach button. Click the Details tab, and verify that the Subscription Status is Fully entitled.

Reverify that the serverc client system is registered.

List the system's subscription status. The status is changed to Current.

[root@serverc ~]# subscription-manager status
+-------------------------------------------+
   System Status Details
+-------------------------------------------+
Overall Status: Current

System Purpose Status: Not Specified

List the repositories that are available to the serverc client system.

[root@serverc ~]# subscription-manager repos --list
+----------------------------------------------------------+
    Available Repositories in /etc/yum.repos.d/redhat.repo
+----------------------------------------------------------+
Repo ID:   rhel-9-for-x86_64-baseos-rpms
Repo Name: Red Hat Enterprise Linux 9 for x86_64 - BaseOS (RPMs)
Repo URL:  https://satellite.lab.example.com/pulp/content/Marketing/Development/Base/content/dist/rhel9/9/x86_64/baseos/os
Enabled:   1

Repo ID:   satellite-client-6-for-rhel-9-x86_64-rpms
Repo Name: Red Hat Satellite Client 6 for RHEL 9 x86_64 (RPMs)
Repo URL:  https://satellite.lab.example.com/pulp/content/Marketing/Development/Base/content/dist/layered/rhel9/x86_64/sat-client/6/os
Enabled:   0

Repo ID:   rhel-9-for-x86_64-appstream-rpms
Repo Name: Red Hat Enterprise Linux 9 for x86_64 - AppStream (RPMs)
Repo URL:  https://satellite.lab.example.com/pulp/content/Marketing/Development/Base/content/dist/rhel9/9/x86_64/appstream/os
Enabled:   1

Return to the workstation system as the student user.

[root@serverc ~]# exit
logout
[student@serverc ~]$ exit
logout
[student@workstation ~]$

[student@workstation ~]$ ssh student@servera
[student@servera ~]$ sudo -i
[sudo] password for student: student
[root@servera ~]#

Verify that the servera system is not registered.
1. List the system's subscription status. If the status is Unknown, then the system is not registered.
```
[root@servera ~]# subscription-manager status
+-------------------------------------------+
   System Status Details
+-------------------------------------------+
Overall Status: Unknown

System Purpose Status: Unknown
```
2. If the status is other than Unknown, such as Disabled or Invalid, then the system was previously registered and must be cleaned first. Skip this cleaning step if your status is Unknown.
```
[root@servera ~]# subscription-manager clean
All local data removed
```

Install the katello-ca-consumer-latest package from Satellite Server (satellite.lab.example.com).

[root@servera ~]# dnf localinstall \
http://satellite.lab.example.com/pub/katello-ca-consumer-latest.noarch.rpm
...output omitted...
Is this ok [y/N]: y
...output omitted...
Complete!

Register servera to Satellite Server. Specify the Operations organization and the Development/OperationsServerBase environment and content view.

[root@servera ~]# subscription-manager register \
--username admin --password redhat \
--org Operations --environment Development/OperationsServerBase
Registering to: satellite.lab.example.com:443/rhsm
The system has been registered with ID: 462b6a64-eab2-4921-a754-585ee5ee2acd
The registered system name is: servera.lab.example.com

Verify that the servera client system is registered.

List the system's subscription status.

Note

The following output is correct for an initial client registration in an SCA-enabled organization. The Disabled status indicates that per-client product entitlement is not necessary. This client system is automatically entitled to the organization's products as limited by the assigned content view.

[root@servera ~]# subscription-manager status
+-------------------------------------------+
   System Status Details
+-------------------------------------------+
Overall Status: Disabled
Content Access Mode is set to Simple Content Access. This host has access to content, regardless of subscription status.

System Purpose Status: Disabled

List the repositories that are available to the servera client system. The organization's products are available without attaching subscriptions to the system.

[root@servera ~]# subscription-manager repos --list
+----------------------------------------------------------+
    Available Repositories in /etc/yum.repos.d/redhat.repo
+----------------------------------------------------------+
Repo ID:   rhel-9-for-x86_64-baseos-rpms
Repo Name: Red Hat Enterprise Linux 9 for x86_64 - BaseOS (RPMs)
Repo URL:  https://satellite.lab.example.com/pulp/content/Marketing/Development/Base/content/dist/rhel9/9/x86_64/baseos/os
Enabled:   1

Repo ID:   satellite-client-6-for-rhel-9-x86_64-rpms
Repo Name: Red  Hat Satellite Client 6 for RHEL 9 x86_64 (RPMs)
Repo URL:  https://satellite.lab.example.com/pulp/content/Marketing/Development/Base/content/dist/layered/rhel9/x86_64/sat-client/6/os
Enabled:   0

Repo ID:   rhel-9-for-x86_64-appstream-rpms
Repo Name: Red Hat Enterprise Linux 9 for x86_64 - AppStream (RPMs)
Repo URL:  https://satellite.lab.example.com/pulp/content/Marketing/Development/Base/content/dist/rhel9/9/x86_64/appstream/os
Enabled:   1

Use the web UI to verify that the servera system was successfully registered to Satellite Server.
1. Log in to the web UI, https://satellite.lab.example.com, as admin with redhat as the password.
2. In the upper-left corner of the web page, set the organization to Operations. Set the location to Any Location.
3. Click Hosts → Content Hosts. Verify that the servera system is listed as a registered host on the Content Hosts page. Click the servera.lab.example.com link to display the servera.lab.example.com page. A notification states that Simple Content Access is enabled for this organization.
4. From the Details tab, locate the Content Host Content section of the page. Verify that the Content View is OperationsServerBase and that the Lifecycle Environment is Development.
5. Notice that the Subscriptions tab is missing, because it is not needed for Simple Content Access subscription management. Verify that the Subscription Status is Simple Content Access.
6. Return to the workstation system as the student user.
```
[root@servera ~]# exit
logout
[student@servera ~]$ exit
logout
[student@workstation ~]$
```

Finish

On the workstation machine, use the lab finish clients-register command to complete this exercise. This step is important to ensure that resources from previous exercises do not impact upcoming exercises.

[student@workstation ~]$ lab finish clients-register

Discuss Red Hat Satellite 6 Administration

Go to community

Welcome to the Red Hat Satellite 6 Administration (RH403) group in the Red Hat Learning Community!

Syed

26 wrz 2023

We are excited to launch a space dedicated to the Red Hat Training course Red Hat Satellite 6 Administration! To gain the most value from this group - click the "Join Group" button in the upper right hand corner of the group home page.We encourage group members to collaborate in this group to discuss topics, ask questions, share best practices and tips, provide course feedback, and share their accomplishments as it relates to RH403.Read more about Red Hat Satellite 6 Administration here.

Revision: rh403-6.11-3ad886e