Red Hat Training

A Red Hat training course is available for Red Hat Satellite

6.4.2. Systems

The Systems page displays a list of all of your registered systems. The Systems list contains several columns of information for each system:
  • Select — Update or unentitled systems cannot be selected. To select systems, mark the appropriate checkboxes. Selected systems are added to the System Set Manager. After adding systems to the System Set Manager, you can use it to perform actions on them simultaneously. Refer to Section 6.4.4, “System Set Manager — ” for details.
  • Status — Shows which type of Errata Alerts are applicable to the system or confirms that it is up-to-date. Some icons are linked to pages providing resolution. For instance, the standard Updates icon is linked to the Upgrade subtab of the packages list, while the Critical Updates icon links directly to the Update Confirmation page. Also, the Not Checking In icon is linked to instructions for resolving the issue.
    • — System is up-to-date
    • — Critical Errata available, update strongly recommended
    • — Updates available and recommended
    • — System is locked; Actions prohibited
    • — System is being kickstarted
    • — Updates have been scheduled
    • — System not checking in properly (for 24 hours or more)
    • — System not entitled to any update service
  • Errata — Total number of Errata Alerts applicable to the system.
  • Packages — Total number of package updates for the system. Includes packages from Errata Alerts as well as newer packages that are not from Errata Alerts. For example, imagine a client system that has an early version of a package installed. If this client is then subscribed to the appropriate base channel of RHN (such as Red Hat Enterprise Linux 5), that channel may have an updated version of the package. If so, the package appears in the list of available package updates.

    Important

    If the RHN website identifies package updates for the system, yet the Red Hat Update Agent responds with "Your system is fully updated" when run, a conflict likely exists in the system's package profile or in the up2date configuration file. To resolve the conflict, either schedule a package list update or remove the packages from the Package Exceptions list for the Red Hat Update Agent. Refer to Section 6.4.2.9, “System Details” or Section 2.4.1.3, “Package Exceptions Settings”, respectively, for instructions.
  • System — The name of the system as configured when registering it. The default name is the hostname of the system. Clicking on the name of a system takes you to the System Details page for the system. Refer to Section 6.4.2.9, “System Details” for more information.
  • Base Channel — The primary channel for the system, based upon its operating system distribution. Refer to Section 6.6.1, “Software Channels” for more information.
  • Entitlement — Whether or not the system is entitled and at what service level.
Links in the left navigation bar below Systems enable you to select and view predefined sets of your systems. All of the options described above can be applied within these pages.

6.4.2.1. All

The All page contains the default set of your systems. It displays every system you have permission to manage. A user has permission to manage a system if he is the only user in his organization, if he is an Satellite Administrator, or if the system is a member of a group to which he has admin rights.

6.4.2.2. Virtual Systems

To reach this page, select the Systems tab, followed by the Systems subtab from the left navigation bar, and finally select Virtual Systems from the left navigation bar. This page lists each virtual host of which the RHN Satellite Server is aware and the guest systems on those hosts.
System
This column displays the name of each guest system.
Updates
This column indicates whether the guest systems have any errata that have not yet been applied to them.
Status
This column indicates whether a guest is running, paused, or stopped.
Base Channel
This column indicates the base channel to which the guest is currently subscribed.
Only those guests that are registered with RHN are displayed in blue text. Clicking on the hostname of such a guest system displays that system's System Details page.

6.4.2.3. Out of Date

The Out of Date page displays the systems that have applicable Errata Alerts that have not been applied.

6.4.2.4. Unentitled —

The Unentitled page displays the systems that have not yet been entitled for Red Hat Network service.

6.4.2.5. Ungrouped

The Ungrouped page displays the systems that have not yet been assigned to a specific system group.

6.4.2.6. Inactive

The Inactive page displays the systems that have not checked into RHN for 24 hours or more. When the Red Hat Update Agent connects to RHN to see if there are any updates available or if any actions have been scheduled, this is considered a check-in. If you are seeing a message indicating checkins are not taking place, the RHN client on your system is not successfully reaching Red Hat Network for some reason. This indicates:
  • The system is not entitled to any RHN service. System Profiles that remain unentitled for 180 days (6 months) are removed.
  • The system is entitled, but the Red Hat Network Daemon has been disabled on the system. Refer to Chapter 3, Red Hat Network Daemon for instructions on restarting and troubleshooting.
  • The system is behind a firewall that does not allow connections over https (port 443).
  • The system is behind an HTTP proxy server that has not been properly configured.
  • The system is connected to an RHN Proxy Server or RHN Satellite Server that has not been properly configured.
  • The system itself has not been properly configured, perhaps pointing at the wrong RHN Server.
  • The system is not on the network.
  • Some other barrier exists between the system and the RHN Servers.

6.4.2.7. Recently Registered

The Recently Registered page displays any new systems that have been registered in a given period of time. Use the drop-down menu to specify new systems registered in days, weeks, 30- and 180-day increments, and yearly.

6.4.2.8. Proxy

The Proxy page displays the RHN Proxy Server systems registered to your RHN account.

6.4.2.9. System Details

Click on the name of a system on any page and RHN displays the System Details page for that client. From here, you may modify the displayed information or remove the system altogether by clicking the delete system link on the top-right corner.

Note

The delete system link in the upper right of this screen refers to the system profile only. Deleting a host system profile will not destroy or remove the registration of guest systems. Deleting a guest system profile does not remove it from the list of guests for its host, nor does it stop or pause the guest. It does, however, remove your ability to manage it via RHN.
If you mistakenly delete a system profile from RHN, you may re-register the system.
The System Details page is further divided into the following tabs:
  • Details
  • Software
  • Configuration
  • Provisioning —
  • Monitoring —
  • Groups
  • Events
The following sections discuss these tabs and their sub-tabs in detail.
6.4.2.9.1. System Details ⇒ Details
This page is not accessible from any of the standard navigation bars. However, clicking on the name of a system anywhere in the web interface brings you to this page. The default tab displayed on this page is the Details ⇒ Overview subtab. Other tabs are available, depending on the current entitlement level of the system.
6.4.2.9.1.1. System Details ⇒ Details ⇒ Overview
This system summary page displays the system status message and the following key information about the system:
System Info
System Status Message
This message indicates the current state of your system in relation to RHN.

Note

If updates are available for any entitled system, the message Critical updates available appears. To apply these updates, click the update now link.
system ID
A unique identifier generated each time a system registers with RHN.

Note

The system ID can be used to eliminate duplicate profiles from RHN. Compare the system ID listed on this page with the information stored on the client system in the /etc/sysconfig/rhn/systemid file. In that file, the system's current ID is listed under "system_id". The value starts after the characters "ID-" If the value stored in the file does not match the value listed in the profile, the profile is not the most recent one and may be removed.
Hostname
The hostname as defined by the client system. This information is often found in /etc/hostname for Red Hat Enterprise Linux systems.
IP Address
The IP address of the client.
Kernel
The kernel that is installed and operating on the client system.
Registered
The date and time at which the system registered with RHN and created this profile.
Checked In
The date and time at which the system last checked in with RHN.
Last Booted
The date and time at which the system was last started or restarted.

Note

Systems with a Management entitlement can be rebooted from this screen.
  • Select Schedule system reboot
  • Provide the earliest date and time at which the reboot may take place.
  • Click the Schedule Reboot button in the lower right.
When the client checks in after the scheduled start time, RHN will instruct the system to restart itself.
Locked
Indicates whether a system has been locked.
Actions cannot be scheduled for locked systems through the web interface until the lock is removed manually. This does not include preventing auto-errata updates scheduled through the web interface. To prevent the application of auto-errata updates, de-select Auto Errata Update from the System Details ⇒ Details ⇒ Properties subtab.
Locking a system can help to prevent you from accidentally making any changes to a system until you are ready to do so. For example, the system may be a production system that you do not wish to receive updates or new packages until you decide to unlock it.

Important

Locking a system in the web interface will not prevent any actions that originate from the client system. For example, if a user logs into the client directly and runs up2date, up2date will install available errata whether or not the system is locked in the web interface.
Further, locking a system does not restrict the number of users who can access the system via the web interface. If you wish to restrict access to the system, associate that system with a System Group and assign it a System Group Administrator. Refer to Section 6.4.3, “System Groups — ” for more information about System Groups.
It is also possible to lock multiple systems via the System Set Manager. Refer to Section 6.4.4.12.4, “System Set Manager ⇒ Misc ⇒ Lock Systems — ” to learn how to do so.
— OSA status is also displayed for client systems registered to a Satellite that have a Provisioning entitlement and have enabled OSA.
Push enables Satellite customers to immediately initiate tasks on Provisioning-entitled system rather than wait for those systems to check in with RHN. Scheduling actions through push is identical to the process of scheduling any other action, except that the task begins immediately instead of waiting the set interval.
In addition to the configuration of the Satellite, each client system to receive pushed actions must have the osad package installed and its service started. Refer to the Enabling Push to Clients section of the RHN Satellite 5.2.0 Installation Guide for details.
Subscribed Channels
Base Channel
The first line indicates the base channel to which this client is subscribed. The base channel should match the operating system of the system.
Child Channels
The subsequent lines of text, which depend from the base channel, are child channels. Examples are the Red Hat Network Tools channel and the RHEL AS Extras channel.

Note

The final link under Subscribed Channels is the Alter Channel subscriptions link. Click on this link to select from the available base and child channels for this system. When finished making selections, click the Change Subscriptions button to confirm the changes.
System Properties
Profile Name
This editable name for the system profile is set to the system's hostname by default. It serves to distinguish this system profile from others.
Entitlement
The base entitlement currently applied to this system.
Notifications
Indicates the the notification options for this system. You can choose whether you wish to receive email notifying you of available errata updates for this system. In addition, you may choose to include Management-entitled systems in the daily summary email.
Auto Errata Update
Indicates whether this system is configured to accept updates automatically.
Description
This information is automatically generated at registration. You can edit this to include any information you wish.
Location
If entered, this field displays the physical address of the system.
The final link on the page is Edit these properties. Clicking this link opens the System Details ⇒ Properties subtab. On this page, edit any text you choose, then click the Update Properties button to confirm.
6.4.2.9.1.2. System Details ⇒ Details ⇒ Properties
This subtab allows you to alter the following basic properties of your system:
Profile Name
By default, this is the hostname of the system. You can however alter the profile name to anything that allows you to distinguish this profile from others.
Base Entitlement
Select a base channel for the system from the available base entitlements.
Add-on entitlements
If available, apply a Monitoring or Provisioning entitlement to the system.
Notifications
Toggle whether notifications about this system are sent and whether this system is included in the daily summary. (By default, all Management and Provisioning systems are included in the summary.) This setting keeps you abreast of all advisories pertaining to the system. Anytime an update is produced and released for the system, a notification is sent via email.
The daily summary reports system events that affect packages, such as scheduled Errata Updates, system reboots, or failures to check in. In addition to including the system here, you must choose to receive email notification sin the Your Preferences page of the Your RHN category.
Auto-errata update
If this box is checked, available errata are automatically applied to the system when it checks in. This action takes place without user intervention. Customers should note that Red Hat does not recommend the use of the auto-update feature for production systems because conflicts between packages and environments can cause system failures. The Red Hat Network Daemon must be enabled on the system for this feature to work.
Description
By default, this text box records the operating system, release, and architecture of the system when it first registers. You may edit this information to include anything you like.
The remaining fields record the physical address at which the system is stored. To confirm any changes to these fields, click the Update Properties button.

Note

Many of these properties can be set for multiple systems at once through the System Set Manager interface. Refer to Section 6.4.4, “System Set Manager — ” for details.
6.4.2.9.1.3. System Details ⇒ Details ⇒ Remote Command —
This subtab allows you to run a remote command on the system if the system possesses a Provisioning entitlement. Before doing so, you must first configure the system to accept such commands.
  • First, subscribe the system to the RHN Tools channel and use up2date to install the rhncfg, rhncfg-client, and rhncfg-actions packages. 
     up2date rhncfg rhncfg-client rhncfg-actions
  • Log into the system as root and add the following file to the local RHN configuration directory: allowed-actions/scripts/run.
    • Create the necessary directory on the target system: 
       mkdir -p /etc/sysconfig/rhn/allowed-actions/script
    • Create an empty run file in that directory to act as a flag to RHN signaling permission to allow remote commands: 
       touch /etc/sysconfig/rhn/allowed-actions/script/run
Once the setup is complete, refresh the page in order to view the text fields for remote commands. You may then identify a specific user, group, and timeout period, as well as the script itself on this page. Select a date and time to begin attempting the command, and click Schedule Remote Command.
6.4.2.9.1.4. System Details ⇒ Details ⇒ Reactivation —
An activation key specific to this System Profile. Reactivation keys, available only for systems that have a Provisioning entitlement, include this system's ID, history, groups, and channels. This key can then be used only once with the rhnreg_ks command line utility to re-register this system and regain all Red Hat Network settings. Refer to Section 2.5, “Registering with Activation Keys” for instructions. Unlike typical activation keys, which are not associated with a specific system ID, keys created here do not show up within the Activation Keys page.
Reactivation keys can be combined with aactivation keys to aggregate the settings of multiple keys for a single system profile. For example: 
rhnreg_ks --server=<server-url> --activationkey=<reactivation-key>,<activationkey> --force

Warning

When kickstarting a system with its existing RHN profile, the kickstart profile uses the system-specific activation key created here to re-register the system and return its other RHN settings. For this reason, you should not regenerate, delete, or use this key (with rhnreg_ks) while a profile-based kickstart is in progress. If you do, the kickstart will fail.
6.4.2.9.1.5. System Details ⇒ Details ⇒ Hardware
This subtab provides detailed information about the system, including networking, BIOS, storage, and other devices. This appears only if you selected to include the hardware profile for this machine during registration. If the hardware profile looks incomplete or outdated, click the Schedule Hardware Refresh button to schedule a Hardware Profile update for your system. The next time the RHN Daemon connects to RHN, it will update your System Profile with the latest list of hardware.
6.4.2.9.1.6. System Details ⇒ Details ⇒ Notes
This subtab provides a place to create notes about the system. To add a new note, click the create new note link, type a subject and details, and click the Create button. To modify a note, click on its subject in the list of notes, make your changes, and click the Update button. To remove a note, click on its subject in the list of notes and then click the delete note link.
6.4.2.9.1.7. System Details ⇒ Details ⇒ Custom Info —
This subtab, available for systems with a Provisioning entitlement, provides completely customizable information about the system. Unlike Notes, Custom Info is structured, formalized, and can be searched upon. Before you can provide custom information about a system, you must first have Custom Information Keys. This is done via the Custom System Info page, available from the left navigation bar. Refer to Section 6.4.8, “Custom System Info — ” for instructions.
Once you have created one or more Keys, you may assign a value for this system by select the create new value link. Click the name of the key in the resulting list and enter a value for it in the Description field, then click the Update Key button.
6.4.2.9.1.8. System Details ⇒ Details ⇒ Proxy
Activates an RHN Proxy Server. This tab is only available for Provisioning-entitled systems. Select a version of RHN Proxy Server and click the Activate Proxy button to begin the installation and activation process. For detailed information, refer to the RHN Proxy Server Guide and the Client Configuration Guide.
6.4.2.9.1.9. System Details ⇒ Details ⇒ Satellite
Displays the certificate of an active Red Hat Network. You can deactivate an old certificate here and upload a new one if necessary. This tab requires a Provisioning entitlement. For detailed information on activating a Satellite, refer to the RHN Satellite Installation Guide.
6.4.2.9.2. System Details ⇒ Software
This tab and its accompanying subtabs allow you to manage the software of the system: errata, packages and package profiles, and software channel memberships.
6.4.2.9.2.1. System Details ⇒ Software ⇒ Errata
This subtab contains a list of Errata Alerts applicable to the system. Refer to Section 6.1.3, “Errata Alert Icons” for meanings of the icons on this tab. To apply updates, select them and click the Apply Errata button. Double-check the updates to be applied on the confirmation page, then click the Confirm button. After confirming, the action is added to the Pending Actions list under Schedule. Errata that have been scheduled cannot be selected for update. In the place of a checkbox is a clock icon that, when clicked, takes you to the Action Details page.
To help users determine whether an update has been scheduled, a Status column exists within the Errata table. Possible values are: None, Pending, Picked Up, Completed, and Failed. This column identifies only the latest action related to an Erratum. For instance, if an action fails and you reschedule it, this column shows the status of the Erratum as Pending only (with no mention of the previous failure). Clicking a status other than None takes you to the Action Details page. This column corresponds to the one on the Affected Systems tab of the Errata Details page.
6.4.2.9.2.2. System Details ⇒ Software ⇒ Packages
This subtab allows you to manage the packages on the system.
— When selecting packages to install, upgrade, or remove, Provisioning customers have the option of running a remote command automatically before or after the package installation. Refer to Section 6.4.2.9.1.3, “System Details ⇒ Details ⇒ Remote Command — ” for more information.
Packages
The default display of the Packages tab describes the options available to you and provides the means to update your package list. To update or complete a potentially outdated list, possibly due to the manual installation of packages, click the Update Package List button on the bottom right-hand corner of this page. The next time the RHN Daemon connects to RHN, it updates your System Profile with the latest list of installed packages.
List/Remove
Lists installed packages from the system's software System Profile and enables you to remove them. Click on a package name to view its Package Details page. To delete packages from the system, select their checkboxes and click the Remove Packages button on the bottom right-hand corner of the page. A confirmation page appears with the packages listed. Click the Confirm button to remove the packages.
Upgrade
Displays a list of packages that have a new version available based on the package versions in the channels for the system. Click on the latest package name to view its Package Details page. To upgrade packages immediately, select them and click the Upgrade Packages button. To download the packages as a .tar file, select them and click the Download Packages button.
Install
Enables you to install new packages on the system from the available channels. Click on the package name to view its Package Details page. To install packages, select them and click the Install Selected Packages button.
Verify
Validates the packages installed on the system against its RPM database. This is the equivalent of running rpm -V. Specifically, this tab allows you to compare the metadata of the system's packages with information from the database, such as MD5 sum, file size, permissions, owner, group and type. To verify a package or packages, select them, click the Verify Selected Packages button, and confirm this action. Once finished, you can view the results by selecting this action within the History subtab under Events.
Profiles
Gives you the ability to compare the packages on this system with the packages of stored profiles and other Management and Provisioning systems. To make the comparison with a stored profile, select that profile from the pulldown menu and click the Compare button. To make the comparison with another system, select it from the associated pulldown menu and click the Compare button. To create a stored profile based upon the existing system, click the Create System Profile button, enter any additional information you desire, and click the Create Profile button. These profiles are kept within the Stored Profiles page linked from the left navigation bar.
— Once package profiles have been compared, Provisioning customers have the ability to synchronize the packages of the selected system with the package manifest of the compared profile. Note that this action may delete packages on the system not in the profile, as well as install packages from the profile. To install specific packages, select the checkboxes of packages from the profile. To remove specific packages already installed on the system itself, select the checkboxes of packages showing a difference of This system only. To synchronize fully the system's packages with the compared profile, select the master checkbox at the top of the column. Then click the Sync Packages to button. On the confirmation screen, review the changes, select a time frame for the action, and click the Schedule Sync button.
6.4.2.9.2.3. System Details ⇒ Software ⇒ Software Channels
Software channels provide a well-defined method to determine which packages should be available to a system for installation or upgrade based upon its operating systems, packages, and functionality. Click a channel name to view its Channel Details page. To modify the child channels associated with this system, use the checkboxes next to the channels and click the Change Subscriptions button. You will receive a success message or be notified of any errors. To change the system's base channel, select the new one from the pulldown menu and click the Modify Base Channel button. Refer to Section 6.6.1, “Software Channels” for more information.
6.4.2.9.3. System Details ⇒ Configuration —
This tab and its subtabs, which do not appear without a Provisioning entitlement, assist in managing the configuration files associated with the system. These configuration files may be managed solely for the current system, or may be distributed widely via a Configuration Channel. The following section describe these and other available options on the System Details ⇒ Configuration subtabs.

Note

To manage the configuration of a system, it must have the latest rhncfg* packages installed. Refer to Section 6.7.1, “Preparing Systems for Config Management” for instructions on enabling and disabling scheduled actions for a system.
This section is available to normal users with access to systems that have configuration management enabled. Like software channels, configuration channels store files to be installed on systems. While software updates are provided by RHN, configuration files are managed solely by you. Also unlike software packages, various versions of configuration files may prove useful to a system at any given time. Remember, only the latest version can be deployed.
6.4.2.9.3.1. System Details ⇒ Configuration ⇒ Overview
This subtab provides access to the configuration statistics of your system and to the most common tasks used to manage configuration files. You may change the settings listed under Configuration Stats by clicking on the blue text for that setting. Alternatively, you may perform any of the common configuration management tasks listed on the right of the screen by clicking one of the links.
6.4.2.9.3.2. System Details ⇒ Configuration ⇒ Managed Files
This subtab lists all configuration files currently associated with the system.
Filename
This column shows both the name and the deployment path for this file.
Revision
This column increments any time you make a change to the managed file.
From Config Channel
This column indicates the name of the channel that contains the file, or displays (system override) for files available to this system only.
Overrides
If this configuration file overrides another, the overridden file is listed in this column along with its host channel.
If you wish to deploy any of these files to the client system, overwriting any changes that have been made locally, check the box to the left of the file and click the Deploy Configuration button. On the following screen, choose a deployment time and click the Schedule Deploy button to confirm.

Note

If you click on the Filename of a (system override) file, you can edit its contents.
The Overrides column identifies the config file from which channel will apply if the system is unsubscribed from the config channel that provides the file now. For instance, if a system has '/etc/foo' from channel 'bar' and '/etc/foo' from channel 'baz' is in the Overrides column, then unsubscribing from channel 'bar' will mean that the file from channel 'baz' will be applicable. Also, if nothing is in the 'Overrides' column for a given file path, then unsubscribing from the channel providing the file will mean that the file is no longer managed (though it will not remove the file from the system).
6.4.2.9.3.3. System Details ⇒ Configuration ⇒ Compare Files
This subtab compares a configuration file as stored on the Satellite with the file as it exists on the client. (It does not, for example, compare versions of the same file stored in different channels.) Select the files to be diffed, click the Compare Files button, select a time to perform the diff, and click the Schedule Compare button to confirm. After the diff has been performed, you may return to this page to view the results.
6.4.2.9.3.4. System Details ⇒ Configuration ⇒ Manage Configuration Channels
This subtab allows you to subscribe to and rank configuration channels that may be associated with the system, lowest first.
The List/Unsubscribe from Channels subtab contains a list of the system's configuration channel subscriptions. Click the checkbox next to the Channel and click Unsubscribe to remove the subscription to the channel.
The Subscribe to Channels subtab lists all available configuration channels. To subscribe to a channel, select the checkbox next to it and press Continue. To subscribe to all configuration channels, click Select All and press Continue. The View/Modify Rankings page automatically loads.
The View/Modify Rankings subtab allows users rank the priority in which files from a particular configuration channel are weighted. The higher the channel is on the list, the more its files take precedence over files on lower-ranked channels (for example, the higher-ranked channel may have an httpd.conf file that will take precedence over the file on lower-ranked channel)
6.4.2.9.3.5. System Details ⇒ Configuration ⇒ Local Overrides
This subtab displays the default configuration files for the system and allows you to manage them. If no files exist, you may use the add files, upload files, and add directories links within the page description to associate files with this system. These tabs correspond to those within the Configuration Channel Details page, affecting your entire organization and available only to Configuration Administrators. Refer to Section 6.7.3.1, “Configuration ⇒ Configuration Channels ⇒ Configuration Channel Details” for more information.
If a file exists, click its name to go to the Configuration File Details page. Refer to Section 6.7.4, “Configuration Files” for instructions. To replicate the file within a config channel, select its checkbox, click the Copy to Config Channel button, and select the destination channel. To remove a file, select it and click Delete Selected Files.
6.4.2.9.3.6. System Details ⇒ Configuration ⇒ Sandbox
This subtab allows you to manipulate configuration files without deploying them. This sandbox provides you with an area in which to experiment with files without affecting your systems. To add files, click the import new files link, enter the path to the file on you local system, and click the Add button. Select the Import Files button to confirm.
6.4.2.9.4. System Details ⇒ Provisioning —
This tab and its subtabs allow you to schedule and monitor kickstarts and to return your system to a previous state. Kickstart is a Red Hat utility that allows you to automate the reinstallation of a system. Snapshots keep a record of every change to a Provisioning system and allow you to "undo" those changes at will. Both features are described in the sections that follow.
6.4.2.9.4.1. System Details ⇒ Provisioning ⇒ Kickstart —
This subtab is further divided into Session Status, which tracks the progress of previously scheduled kickstarts, and Schedule, which allows you to configure and schedule a kickstart for this system.
Schedule
This subtab allows you to schedule the selected system for kickstart. Choose from the list of available kickstart profiles, select a time for the kickstart to begin, and click the Schedule Kickstart and Finish button to begin the kickstart. You may first alter kickstart settings by clicking the Advanced Configuration button.

Note

You must first create a kickstart profile before it appears on this subtab. If you have not created any profiles, refer to Section 6.4.9.3, “Create a New Kickstart Profile” before scheduling a kickstart for a system.
Session Status
If you have scheduled a kickstart, this subtab shows the progress of the kickstart. The provided details include the kickstart profile used, its state, the next action and the number of requested packages. Kickstarts that do not complete within approximately two hours are marked Kickstart Failed. The page refreshes itself periodically, or you can force a refresh using your browser's controls.
6.4.2.9.4.2. System Details ⇒ Provisioning ⇒ Snapshots —
Snapshots enable you to roll back the system's package profile, configuration files, and RHN settings. Snapshots are captured whenever an action takes place on a Provisioning-entitled system. The Snapshots subtab lists all snapshots for the system , including the reason the snapshot was taken, the time it was taken, and the number of tags applied to each snapshot. To revert to a previous configuration, click the Reason of the snapshot taken and review the potential changes on the provided subtabs, starting with Rollback.
Each subtab provides the specific changes that will be made to the system during the rollback:
  • group memberships
  • channel subscriptions
  • installed packages
  • configuration channel subscriptions
  • configuration files
  • snapshot tags
When satisfied with the reversion, return to the Rollback subtab and click the Rollback to Snapshot button. To see the list again, click Return to snapshot list.
6.4.2.9.4.3. System Details ⇒ Provisioning ⇒ Snapshot Tags —
Provides a means to add meaningful descriptions to your most recent system snapshot. This can be used to indicate milestones, such as a known working configuration or a successful upgrade. To tag the most recent snapshot, click create new system tag, enter a descriptive term in the Tag name field, and click the Tag Current Snapshot button. You may then revert using this tag directly by clicking its name in the Snapshot Tags list. To delete tags, select their checkboxes, click Remove Tags, and confirm the action.
6.4.2.9.5. System Details ⇒ Virtualization
This is tab allows you to create a new virtual guest on a host system or allows you to change the status of virtual guests.
The Virtualization tab has two subtabs, Details and Kickstart. These tabs appear the same for both virtual hosts and guests, but the functionality only makes sense for virtual hosts. It is not possible to create a guest system that runs on another guest system.
6.4.2.9.5.1. System Details ⇒ Virtualization ⇒ Details
Details is the default tab. For host systems, it presents a table of the host system's virtual guests. For each guest system, the following information is provided:
Status
This field indicates whether the virtual system is running, paused, stopped, or has crashed.
Updates
This field indicates whether errata applicable to the guest have yet to be applied.
Base Software Channel
This field indicates the Base Channel to which the guest is subscribed.

Note

If a guest system has not registered to the Satellite, this information appears as plain text in the table.
If you have System Group Administrator responsibilities assigned for your guest systems, it is possible that a user could see the message You do not have permission to access this system within the table. This is because it is possible to assign virtual guests on a single host to multiple System Group Administrators. Only users that have System Group Administrator privileges on the host system may create new virtual guests.
6.4.2.9.5.2. System Details ⇒ Monitoring —
This tab is only visible for systems registered to a RHN Satellite Server with Monitoring enabled and that are Monitoring entitled. It displays all of the probes monitoring the system. The State column shows icons representing the status of each probe. Refer to Section 6.10, “Monitoring — ” for descriptions of these states. Clicking the Probe Description takes you to its Current State page. The Status String column displays the last message received from the probe.
To add a probe to the system, click the create new probe link at the top-right corner of the page and complete the fields on the following page. Refer to Section 7.5.1, “Managing Probes” for detailed instructions.
Once the probe has been added, you must reconfigure your Monitoring infrastructure to recognize it. Refer to Section 6.10.4, “Scout Config Push — ” for details. After the probe has run, its results become available on the Current State page. Refer to Section 6.10.1.7, “Current State — ” for details.
To remove a probe from a system, click on the name of the probe, then click the delete probe link in the upper right corner. Finally, click the Delete Probe button to complete the process.
6.4.2.9.5.3. System Details ⇒ Groups —
This tab and its subtabs allow you to manage the system's group memberships.
6.4.2.9.5.3.1. System Details ⇒ Groups ⇒ List/Leave —
This subtab lists groups to which the system belongs and enables you to cancel those associations. Only System Group Administrators and Satellite Administrators can remove the system from groups. Non-admins just see a Review this system's group membership page. To remove the system from groups, select the groups' checkboxes and click the Leave Selected Groups button. Click on a group's name to go to its System Group Details page. Refer to Section 6.4.3.3, “System Group Details — ” for more information.
6.4.2.9.5.3.2. System Details ⇒ Groups ⇒ Join —
Lists groups that the system may be subscribed to. Only System Group Administrators and Satellite Administrators can add the system to groups. Non-admins see a Review this system's group membership page. To add the system to groups, select the groups' checkboxes and click the Join Selected Groups button.
6.4.2.9.5.4. System Details ⇒ Events
Displays past, current, and scheduled actions on the system. You may cancel pending events here. The following sections describe the Events sub-tabs and the features they offer.
6.4.2.9.5.4.1. System Details ⇒ Events ⇒ Pending
Lists events that are scheduled but have not begun. A prerequisite action must complete successfully before a given action is attempted. If an action has a prerequisite, no checkbox is available to cancel that action. Instead, a checkbox appears next to the prerequisite action; canceling the prerequisite action causes the action in question to fail.
Actions can be chained in this manner so that action 'a' requires action 'b' which requires action 'c'. Action 'c' is the first one attempted and has a checkbox next to it until it is completed successfully - if any action in the chain fails, the remaining actions also fail. To unschedule a pending event, select the event and click the Cancel Events button at the bottom of the page. The following icons indicate the type of events listed here:
  • — Package Event
  • — Errata Event
  • — Preferences Event
  • — System Event
6.4.2.9.5.4.2. System Details ⇒ Events ⇒ History
The default display of the Events tab lists the type and status of events that have failed, occurred or are occurring. To view details of an event, click its summary in the System History list. To again view the table, click Return to history list at the bottom of the page.