Red Hat Satellite 6 Administration

Instructions

1. Log in to the Satellite web UI as the admin user with the redhat password.

   Note

   To improve performance in the web user interface, increase the screen resolution. Use the highest resolution supported by your screen. 1920 x 1080 is the minimum recommended resolution. Then, increase your browser window size as much as possible.

   1. Use your browser to navigate to https://satellite.lab.example.com. If this attempt is your first access to this secure URL, then your browser prompts you to accept the server's certificate.

   2. Log in as the admin user with the redhat password.

2. Verify that the Default Organization organization has no available subscriptions. When done, log out from the Satellite web UI.

   1. Navigate to Content → Subscriptions.

   2. Verify that a message states that no subscriptions are available to be displayed.

   3. In the upper-right corner, click Admin User → Log Out from the Satellite web UI.

3. Verify the status of the Red Hat Satellite services.

   1. On workstation, log in to the satellite system as the student user and switch to the root user.

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

   2. Use the satellite-maintain service list command to verify the status of the Red Hat Satellite services.

      [root@satellite ~]# satellite-maintain service list
      Running Service List
      ================================================================================
      List applicable services:
      dynflow-sidekiq@.service                   indirect
      foreman-proxy.service                      enabled
      foreman.service                            enabled
      httpd.service                              enabled
      postgresql.service                         enabled
      pulpcore-api.service                       enabled
      pulpcore-content.service                   enabled
      pulpcore-worker@.service                   indirect
      redis.service                              enabled
      tomcat.service                             enabled
      
      
      All services listed                                                   [OK]
      --------------------------------------------------------------------------------

4. Run health checks for Red Hat Satellite. Provide the admin account password, if necessary.

   [root@satellite ~]# satellite-maintain health check
   Running ForemanMaintain::Scenario::FilteredScenario
   ================================================================================
   Check number of fact names in database:                               [OK]
   --------------------------------------------------------------------------------
   Check whether all services are running:                               [OK]
   --------------------------------------------------------------------------------
   Check whether all services are running using the ping call:           [OK]
   --------------------------------------------------------------------------------
   Check for paused tasks:                                               [OK]
   --------------------------------------------------------------------------------
   Check whether system is self-registered or not:                       [OK]
   --------------------------------------------------------------------------------

5. Verify that all services and ports that Red Hat Satellite requires are enabled in the firewall configuration.

   [root@satellite ~]# systemctl status firewalld
   ● firewalld.service - firewalld - dynamic firewall daemon
      Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)
      Active: active (running) since Wed 2022-07-27 15:08:03 EDT; 1h 14min ago
   ...output omitted...
   [root@satellite ~]# firewall-cmd --list-all
   public (active)
     target: default
     icmp-block-inversion: no
     interfaces: eth0
     sources:
     services: dhcpv6-client ssh
     ports: 53/udp 53/tcp 67/udp 69/udp 80/tcp 443/tcp 5647/tcp 8000/tcp 9090/tcp 8140/tcp
   ...output omitted...

6. Verify that the chronyd service is active and enabled.

   [root@satellite ~]# systemctl status chronyd
   ● chronyd.service - NTP client/server
      Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor preset: enabled)
      Active: active (running) since Thu 2022-02-17 09:36:34 EST; 5h 26min ago
   ...output omitted...

7. Verify that localhost and the hostname for the satellite server resolve correctly.

   1. Verify localhost resolution.

      [root@satellite ~]# ping -c1 localhost
      PING localhost(localhost (::1)) 56 data bytes
      64 bytes from localhost (::1): icmp_seq=1 ttl=64 time=0.063 ms
      
      --- localhost ping statistics ---
      1 packets transmitted, 1 received, 0% packet loss, time 0ms
      rtt min/avg/max/mdev = 0.063/0.063/0.063/0.000 ms

   2. Verify that the Satellite Server forward hostname resolution is correct.

      [root@satellite ~]# ping -c1 satellite.lab.example.com
      PING satellite.lab.example.com (172.25.250.16) 56(84) bytes of data.
      64 bytes from satellite.lab.example.com (172.25.250.16): icmp_seq=1 ttl=64 time=0.036 ms
      
      --- satellite.lab.example.com ping statistics ---
      1 packets transmitted, 1 received, 0% packet loss, time 0ms
      rtt min/avg/max/mdev = 0.036/0.036/0.036/0.000 ms

   3. Verify that the Satellite Server reverse DNS resolution is correct.

      [root@satellite ~]# host 172.25.250.16
      16.250.25.172.in-addr.arpa domain name pointer satellite.lab.example.com.

8. Return to the workstation system as the student user.

   [root@satellite ~]# exit
   logout
   [student@satellite ~]$ exit
   logout
   Connection to satellite closed.
   [student@workstation ~]$