04.06.2013 Views

UCS 2.4 - Univention

UCS 2.4 - Univention

UCS 2.4 - Univention

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

4 <strong>Univention</strong> Directory Manager<br />

DHCP servers with a common configuration are compiled in a DHCP service. Global configuration pa-<br />

rameters are entered in the DHCP service; specific parameters in the subordinate objects.<br />

A number of DHCP servers within one DHCP service can be used if only fixed IP addresses are assigned.<br />

If variable IP addresses are also assigned, a maximum of two DHCP servers can be used in combination<br />

with the DHCP failover mechanism.<br />

A DHCP host entry is used to make the DHCP service aware of a computer. These computer entries can<br />

be created automatically when adding or editing a computer in computer management or in the navigation.<br />

A computer entry is required for computers attempting to retrieve a fixed IP address over the DHCP.<br />

A DHCP subnet entry is required for every subnet, irrespective of whether variable IP addresses are<br />

allocated from this subnet.<br />

Configuration parameters can be assigned to the different IP ranges by creating DHCP pools within sub-<br />

nets. In this way unknown computers can be allowed in one IP range and excluded in another IP range.<br />

DHCP failover can also be set-up in DHCP pool objects. DHCP pools can only be created below DHCP<br />

subnet objects.<br />

If several subnets use the same common, physical network, this should be entered as a DHCP shared<br />

subnet below a DHCP shared network. DHCP shared subnet objects can only be created below DHCP<br />

shared network objects.<br />

Instead of DHCP group declarations, containers can be created to accept the objects to be grouped. The<br />

parameters of such an object group are determined via a policy, which is linked to the container.<br />

Values which are input on a DHCP configuration level always apply for this level and all subordinate levels,<br />

unless other values are specified there. Similar to with the policies, the value which is closest to the object<br />

always applies. Unlike for the general policies, it is not possible here to set it so that a value cannot be<br />

altered from lower levels.<br />

Attention:<br />

Note that values assigned to an object via a policy are inherited by all subordinate objects. For example, if<br />

the domain name company.com is fixed in a DHCP service object via a policy and a DHCP host object is<br />

created in the same DHCP service object, the DHCP host object automatically adopts the domain name<br />

because of the inherited policy settings. If the DHCP host object now retrieves an IP address from a<br />

DHCP pool where the domain name sales.company.com was entered, the domain name company.com<br />

will remain valid for the DHCP host object.<br />

This applies to all settings which are made on tabs where the writing at the top of the tab is enclosed in<br />

square brackets. The inherited values are displayed on the respective tabs of the subordinate objects and<br />

can be altered there (see also Chapter 4.5.11).<br />

The following policies can be applied for the DHCP objects described below:<br />

102<br />

• Boot parameters<br />

• DHCP miscellaneous<br />

• DNS<br />

• DNS update<br />

• Allow/Forbid

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!