Problems PXE boot

[loggenk]

Hi All,

I have a problem using pxe boot on a depot.

Situation :

1 Opsi server ip: 192.168.13.60 domain dev.xxx.xx
2 depots ip: 192.168.157.61 domain ehv.xxx.xx
192.168.61.204 domain bar.xxx.xx

When i use PXE boot from Opsi server no problem.
When i use PXE boot on depots no PXE boot is offered (created client in depot)
When i create a client in opsi server it starts imaging from Opsi server. However, i want to PXE boot from depot. So it doesn't have to use the Wlan.

Both depots has the pxeboot pointed to the depots.

Question:

In configed, in which location do i have to create client?
are there any special settings in DHCP?

With regards,

Kees....

[n.wenselowski]

Hello Kees,

it should not matter where your client is created.

Is opsipxeconfd configured in the /etc/opsi/backendManager/dispatch.conf as a backend on the depots?
Is the service running on the depots?


With kind regards

Niko

[loggenk]

Hi Niko,

Thanks for replying.

Yes, /etc/opsi/backendManager/dispatch.conf is configured, and opsipxeconfd is running on system.

----------------------------
# -*- coding: utf-8 -*-
# = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
# = backend dispatch configuration =
# = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
#
# This file configures which methods are dispatched to which backends.
# Entries has to follow the form:
# <regular expression to match method name(s)> : <comma separated list of backend name(s)>
#
# Backend names have to match a backend configuraton file basename <backend name>.conf beneath /etc/opsi/backends.
# For every method executed on backend dispatcher the first matching regular expression will be decisive.
#
# Typical configurations:
# file, opsipxeconfd and dhcpd backend:
# backend_.* : file, opsipxeconfd
# host_.* : file, opsipxeconfd
# productOnClient_.* : file, opsipxeconfd
# configState_.* : file, opsipxeconfd
# .* : file
#
# jsonrpc, opsipxeconfd and dhcpd backend:
# backend_.* : jsonrpc, opsipxeconfd
# .* : jsonrpc
#
# ldap as main backend, mysql as hw/sw invent and license management backend, opsipxeconfd and dhcpd backend:
# backend_.* : ldap, mysql, opsipxeconfd
# host_.* : ldap, opsipxeconfd
# productOnClient_.* : ldap, opsipxeconfd
# configState_.* : ldap, opsipxeconfd
# license.* : mysql
# softwareLicense.* : mysql
# audit.* : mysql
# .* : ldap
#

backend_.* : jsonrpc, opsipxeconfd
.* : jsonrpc
------------------------------------------

Greetings,

Kees...

[n.wenselowski]

Hello Kees,

this looks fine.

After re-reading your question I have to admitt that I maybe understood it wrong.
In the configed you can create the client whereever you want. But it must be moved to the correct depot you want it to boot from - it will not automatically use the depot nearby for a netboot installation.

Do you have a DHCP-Server in the nerwork of of your Depots?
Does this server relay to the OPSI-server?


With kind regards

Niko

[loggenk]

Hi Niko,

I maneged to image from depot. Dynamic depots wasn't used.

However, when pxe boots starts the miniroot has to be downloaded from the master server.
Isn't it possible to let the miniroot starts from depot?

We use different vlans. In every vlan we can give a pxeboot server.

Regards,
Kees....

[n.wenselowski]

Hello Kees,

it is possible. In your dhcpd.conf the corresponding next-server has to be set for the clients.
Are you running the dhcpd on your config-server and have the dhcpd-backend configured in your dispatch.conf?

The easiest way to debug this is with an support contract.


With kind regards

Niko