Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Server Automation10.51

Administer > SA Provisioning > OS sequence-based provisioning > Booting a Red Hat Enterprise Linux server in a non-DHCP environment

Booting a Red Hat Enterprise Linux server in a non-DHCP environment

If you plan to use SA Provisioning in an environment without a DHCP server, you must assign static IP information for the managed server and manually configure that server to resolve the SA Core.

There are several reasons you might need to manually specify the network information for a sever being provisioned:

You don’t use DHCP and must manually specify the static IP address and the Agent’s IP and Port
You must provision a server but DHCP is inactive.
You must provision a server but DHCP is blocked by firewall rules.

CD boot images for Linux SA Provisioning in non-DHCP environments can be exported by selecting Library > By Folder > Opsware > Tools > OS Provisioning.

The images are named using the following format:

HPSA_linux_boot_cd.iso

This section provides details for provisioning in a non-DHCP environment.

When you boot an unmanaged server in a non-DHCP environment, you will see a boot screen.

After you select the boot method, you see a dialog that allows you to choose whether you want to boot your machine using DHCP or enter the static network configuration.

If you choose DHCP, SA uses your DHCP server for configuration. If you choose static, you will see a Network Configuration dialogue that allows you to enter a static IP address for the server, the subnet mask, the host gateway IP address, and the IP address and default port for the SA Agent Gateway:

Red Hat Linux network configuration dialog

You can manually configure the following fields:

Interface: the NIC to be used
IP Address: static IP address for the server being provisioned
Netmask: netmask for the server being provisioned
Default gateway: Gateway IP address the server being provisioned should use (network level IP router)
DNS Server: the IP address the server being provisioned should use
DNS Search Path: the fully qualified DNS suffix the server being provisioned should use
SA Server IP: IP address of the SA Core host

After the information in these fields is entered and applied, the server is able to register with the SA Core. You can now start the normal SA Provisioning process.

DHCP custom attribute

Servers that have been registered with the SA Core using a static IP specification will display the hpsa_netconfig custom attribute in the server record, as shown in the following figure:

hpsa_netconfig custom attribute in server record

Send Help Center feedback