Red Hat NETWORK SATELLITE 5.3.0 - CHANNEL MANAGEMENT, Reference Manual, Page: 147 / 318

Systems
135
To capture custom system information, insert the key label into the custom information macro
(rhn.system.custom_info). For instance, if you developed a key labeled "asset" you can add it to
the custom information macro in a configuration file to have the value substituted on any system
containing it. The macro would look like this:
asset={@ rhn.system.custom_info(asset) @}
Upon deployment of the file to a system containing a value for that key, the macro gets translated,
resulting in a string similar to the following:
asset=Example#456
To include a default value, for instance if one is required to prevent errors, you can append it to the
custom information macro, like so:
asset={@ rhn.system.custom_info(asset) = 'Asset #' @}
This default is overridden by the value on any system containing it.
Using the
Red Hat Network Configuration Manager
(
rhncfg-manager
) will not translate or alter
files, as that tool is system agnostic —
rhncfg-manager
does not depend on system settings. Binary
files cannot be interpolated.
7.7.6. Systems
This page displays status information about your system in relation to configuration. There are two
sub-tabs:
Managed Systems
and
Target Systems
.
7.7.6.1. Managed Systems
This page is the default display for the
Configuration
�
Systems
page. The systems displayed here
have been fully prepared for configuration file deployment. The number of local and centrally-managed
files is displayed. Clicking the name of the system takes you to the
System Details
�
Configuration
�
Overview
page for the system. Clicking on the number of local files takes you to the
System
Details
�
Configuration
�
View/Modify Files
�
Locally-Managed Files
page, which allows you to
manage which local (override) files apply to the system. Clicking on the number of centrally-managed
configuration channels takes you to the
System Details
�
Configuration
�
List/Unsubscribe from
Channels
page. This allows you to unsubscribe from any channels you wish.
7.7.6.2. Target Systems
This page displays the systems that are either not prepared for configuration file deployment or have
not yet been subscribed to a configuration channel. The table has three columns which identify the
system name, whether they are prepared for configuration file deployment, and a list of the steps
that have yet to be completed before the system is prepared. By selecting the check box to the left of
the profile name and then pressing the
Enable RHN Configuration Management
button, all of the
preparatory steps that can be automatically performed are scheduled by RHN.