Red Hat NETWORK SATELLITE 5.1.1 Reference Manual page 138

Chapter 6. Red Hat Network Website
• rhn.system.description
• rhn.system.hostname
• rhn.system.ip_address
• rhn.system.custom_info(key_name)
• rhn.system.net_interface.ip_address(eth_device)
• rhn.system.net_interface.netmask(eth_device)
• rhn.system.net_interface.broadcast(eth_device)
• rhn.system.net_interface.hardware_address(eth_device)
• rhn.system.net_interface.driver_module(eth_device)
To use this powerful feature, either upload or create a configuration file through the Configuration
Channel Details page. Then, open its Configuration File Details page and include the supported
macros of your choosing. Ensure that the delimiters used to offset your variables match those set in
the Macro Start Delimiter and Macro End Delimiter fields and do not conflict with other characters in
the file. The delimiters must be two characters in length and cannot contain the percent (%) symbol.
As an example, you may have a file applicable to all of your servers that differs only in IP address and
hostname. Rather than manage a separate configuration file for each server, you may create a single
file, such as server.conf, with the IP address and hostname macros included, like so:
hostname={@ rhn.system.hostname @}
ip_address={@ rhn.system.net_interface.ip_address(eth0) @}
Upon delivery of the file to individual systems, whether through a scheduled action in the RHN website
or at the command line with the Red Hat Network Configuration Client (rhncfg-client), the
variables will be replaced with the hostname and IP address of the system, as recorded in RHN's
System Profile. In the above configuration file, for example, the deployed version resembles the
following:
hostname=test.example.domain.com
ip_address=177.18.54.7
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
126