Satellite: A Deep Dive into Troubleshooting

In this hands-on troubleshooting lab we will troubleshoot common issues that are encountered in Red Hat Satellite deployments, identify and solve content and synchronization issues, fix client connectivity issues, and show how a Standard Operating Environment enhances the customer experience.

This lab provides real-world scenarios to help you diagnose and resolve content synchronization, execution and client connectivity issues in Red Hat Satellite.

Concepts included in this scenario:

  • Validating and rectifying content synchronization issues affecting Satellite and Capsules

  • Tuning Satellite server to resolve performance issues

  • Troubleshooting client connectivity and registration

  • Investigating Remote Execution failures

Lab Access

The terminal window to your right is already logged into the lab environment as the {root} user via ssh. All steps of this lab on the Satellite server, Capsule server and clients are to be completed as the {root} user.

Satellite server web console access:

  • Web URL: {workshop_satellite_url}[window=_blank]

  • User: {workshop_satellite_user_name}

  • Password: {workshop_satellite_user_password}

Access other instances from Bastion

  • Log in to the satellite server from bastion:

[lab-user@bastion ~]$ ssh -i ~/.ssh/my-guidkey.pem ec2-user@satellite

  • Log in to the capsule server from bastion:

[lab-user@bastion ~]$ ssh -i ~/.ssh/my-guidkey.pem ec2-user@capsule

  • Log in to the additional nodes from bastion:

[lab-user@bastion ~]$ ssh -i ~/.ssh/my-guidkey.pem ec2-user@node1
[lab-user@bastion ~]$ ssh -i ~/.ssh/my-guidkey.pem ec2-user@node2
[lab-user@bastion ~]$ ssh -i ~/.ssh/my-guidkey.pem ec2-user@node3