OPSI Server auf Hosteurope Vserver

DJ TWEETY · Jun 27, 2012

Mein Folgendes Test Szenario

1. Ubuntu / Lucid vServer von HE mit Opsi Server

2. VMware Clients zum Testen

Die Server seitigen Sachen habe ich schon installiert und hoffe das die Config Dateien von mir Richtig Angepasst wurden.

Hier mal ein Auszug der Config Dateien:

1. opsiconfd.conf

Code:

; = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
; =     configuration file for opsiconfd                                =
; = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =


; - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
; -     global settings                                                 -
; - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[global]
	
	# Location of the backend config dir.
	# Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
	#
	# Default:
	#   backend config dir = /etc/opsi/backends
	
	backend config dir = /etc/opsi/backends
	
	# Location of the backend dispatcher config file.
	# Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
	#
	# Default:
	#   dispatch config file = /etc/opsi/backendManager/dispatch.conf
	
	dispatch config file = /etc/opsi/backendManager/dispatch.conf
	
	# Location of the backend extender config dir.
	# Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
	#
	# Default:
	#   extension config dir = /etc/opsi/backendManager/extend.d
	
	extension config dir = /etc/opsi/backendManager/extend.d
	
	# Location of the acl file.
	# Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
	#
	# Default:
	#   acl file = /etc/opsi/backendManager/acl.conf
	
	acl file = /etc/opsi/backendManager/acl.conf
	
	# Admin networks.
	# Comma separated list of network addresses from
	# which administrative connections are allowed.
	# Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
	#
	# Default:
	#   admin networks = 0.0.0.0/0
	
	admin networks = 0.0.0.0/0
	
	# Enable opsi message bus
	# Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
	#
	# Default:
	#   message bus = no
	
	message bus = no
	
	# Enable multiprocessing
	# Multiprocessing is a co-founded opsi extension module
	# Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
	#
	# Default:
	#   multiprocessing = no
	
	multiprocessing = no
	
	# Location of the pid file.
	# Opsiconfd needs to be restarted for changes to take effect.
	#
	# Default:
	#   pid file = /var/run/opsiconfd/opsiconfd.pid
	
	pid file = /var/run/opsiconfd/opsiconfd.pid
	
	# Location of the log file.
	# The macro %m can be used to create use a separate log file for
	# each client. %m will be replaced by <client-ip>
	# Leave empty to use syslog.
	# Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
	#
	# Default:
	#   log file =
	
	log file = /var/log/opsi/opsiconfd/%m.log
	
	# If separate log files are used and this option is enabled 
	# opsiconfd will create a symlink in the log dir which points 
	# to the clients log file. The name of the symlink will be the same
	# as the log files but %m will be replaced by <client-fqdn>.
	# Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
	#
	# Default:
	#   symlink logs = yes
	
	symlink logs = yes
		
	# Set the log (verbosity) level
	# (0 <= log level <= 9)
	# 0: nothing, 1: essential, 2: critical, 3: errors, 4: warnings, 5: notices
	# 6: infos, 7: debug messages, 8: more debug messages, 9: passwords
	# Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
	#
	# Default:
	#   log level = 3
	
	log level = 5
	
	# Set the log format
	# Macros:
	# %D: current time
	# %T: thread id
	# %l: log level (0..9)
	# %L: log level (name)
	# %M: the message
	# %F: filename
	# %N: linenumber
	# Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
	#
	# Default:
	#   log format = [%l] [%D] %M (%F|%N)
	
	log format = [%l] [%D] %M (%F|%N)
	
	# Maximum number of execution statistics to store in memory.
	# Execution statistics can be written to the log file by sending
	# a SIGHUP to opsiconfd.
	# Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
	#
	# Default:
	#   max execution statistics = 250
	
	max execution statistics = 250

	# The User for opsi-Nagios-Connetor.
	# 
	# Default:
	#   monitoring user = monitoring

	monitoring user = monitoring

; - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
; -     service settings                                                -
; - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[service]

	# The network interfaces to bind to.
	# This must be the IP address of an network interface.
	# Use 0.0.0.0 to listen to all interfaces
	# Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
	#
	# Default:
	#   interface = 0.0.0.0
	
	interface = 0.0.0.0
	
	# The port where opsiconfd will listen for HTTP requests.
	# Use 0 to disable HTTP protocol
	# Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
	#
	# Default:
	#   http port = 0
	
	http port = 0
	
	# The port where opsiconfd will listen for HTTPS requests.
	# Use 0 to disable HTTPS protocol
	# Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
	#
	# Default:
	#   https port = 4447
	
	https port = 4447
	
	# The location of the server certificate.
	# Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
	#
	# Default:
	#   ssl server cert = /etc/opsi/opsiconfd.pem
	
	ssl server cert = /etc/opsi/opsiconfd.pem
	
	# The location of the server private key
	# Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
	#
	# Default:
	#   ssl server key = /etc/opsi/opsiconfd.pem
	
	ssl server key = /etc/opsi/opsiconfd.pem


; - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
; -     session settings                                                -
; - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[session]
	
	# Session name used in the session cookie.
	# Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
	#
	# Default:
	#   session name = OPSISID
	
	session name = OPSISID
	
	# If a client uses its fqdn and opsi-host-key for authentication, 
	# opsiconfd will try to resolve the fqdn (username) by a system call.
	# If there is no result or the resulting IP address does not match
	# the client's address, the access will be denied.
	# Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
	#
	# Default:
	#   verify ip = no
	
	verify ip = no
	
	# If set to yes a client's ip address will be updated in the opsi database,
	# when the client connects to the service and authentication is successful.
	# Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
	#
	# Default:
	#   update ip = no
	
	update ip = yes
	
	# The interval in seconds after an inactive session expires.
	# Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
	#
	# Default:
	#   max inactive interval = 120
	
	max inactive interval = 120
	
	# The maximum number of authentication failures before a client ip
	# is blocked for an amount of time.
	# Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
	#
	# Default:
	#   max authentication failures = 5
	
	max authentication failures = 5

; - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
; -     static directories                                              -
; - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[directories]
	
	# Every option value pair (<resourcename> = <path> [(options)]) has to consist
	# of a resourcename and a path to a local directory.
	# The URL http(s)://<server>:<port>/<resourcename> will give 
	# access to the content of <path>.
	# Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
	
	/ = /usr/share/opsiconfd/static (noauth)
	configed = /usr/lib/configed (noauth)

2. dispatch.conf

Code:

# -*- 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, dhcpd
#       host_.*            : file, opsipxeconfd, dhcpd
#       productOnClient_.* : file, opsipxeconfd
#       configState_.*     : file, opsipxeconfd
#       .*                 : file
#
#    jsonrpc, opsipxeconfd and dhcpd backend:
#       backend_.*         : jsonrpc, opsipxeconfd, dhcpd
#       .*                 : jsonrpc
#
#    ldap as main backend, mysql as hw/sw invent and license management backend, opsipxeconfd and dhcpd backend:
#       backend_.*         : ldap, mysql, opsipxeconfd, dhcpd
#       host_.*            : ldap, opsipxeconfd, dhcpd
#       productOnClient_.* : ldap, opsipxeconfd
#       configState_.*     : ldap, opsipxeconfd
#       license.*          : mysql
#       softwareLicense.*  : mysql
#       audit.*            : mysql
#       .*                 : ldap
#

backend_.*         : file, opsipxeconfd, dhcpd
host_.*            : file, opsipxeconfd, dhcpd
productOnClient_.* : file, opsipxeconfd
configState_.*     : file, opsipxeconfd
.*                 : file

3. hostcontrol.conf

Code:

# -*- coding: utf-8 -*-

module = 'HostControl'
config = {
    "opsiclientdPort":    4441,
    "hostRpcTimeout":     15,
    "resolveHostAddress": False,
    "maxConnections":     50,
    "broadcastAddresses": ["255.255.255.255"]
}

von Server her scheint alles richtig zu Starten Probleme machen dann die Clients was in den Fall VMware´s sind

Ich benutze dazu den VMware Player und den Test Client den man sich bei den Hersteller bezieheen kann hier zu der Direkt Link:

HTML:

http://download.uib.de/vmware_pxeclient.zip

Beim PXE Boot gibt er den Error E-51

Ich habe nichts an der Vm geändert und kann das dadurch nicht wirklich Nachvollziehen.

Es würde mich Freuen wenn ihr für mich Lösungen oder Anregungen habt.

Mfg

DJ TWEETY

Valentin · Jun 27, 2012

Hört sich danach an, als würden die VMs keine DHCP-Adresse erhalten (ist auch das DHCP-Statement "next server" gesetzt?).

DJ TWEETY · Jun 29, 2012

Das Statement wurde gesetzt hab dir mal die Conf gepostet

Code:

#
# Sample configuration file for ISC dhcpd for Debian
#
# Attention: If /etc/ltsp/dhcpd.conf exists, that will be used as
# configuration file instead of this file.
#
# $Id: dhcpd.conf,v 1.1.1.1 2002/05/21 00:07:44 peloy Exp $
#

# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
ddns-update-style none;

# option definitions common to all supported networks...
option domain-name "example.org";
option domain-name-servers ns1.example.org, ns2.example.org;

default-lease-time 600;
max-lease-time 7200;

# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
#authoritative;

# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;

# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.

#subnet 10.152.187.0 netmask 255.255.255.0 {
#}

# This is a very basic subnet declaration.

#subnet 10.254.239.0 netmask 255.255.255.224 {
#  range 10.254.239.10 10.254.239.20;
#  option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
#}

# This declaration allows BOOTP clients to get dynamic addresses,
# which we don't really recommend.

#subnet 10.254.239.32 netmask 255.255.255.224 {
#  range dynamic-bootp 10.254.239.40 10.254.239.60;
#  option broadcast-address 10.254.239.31;
#  option routers rtr-239-32-1.example.org;
#}

# A slightly different configuration for an internal subnet.
#subnet 10.5.5.0 netmask 255.255.255.224 {
#  range 10.5.5.26 10.5.5.30;
#  option domain-name-servers ns1.internal.example.org;
#  option domain-name "internal.example.org";
#  option routers 10.5.5.1;
#  option broadcast-address 10.5.5.31;
#  default-lease-time 600;
#  max-lease-time 7200;
#}

# Hosts which require special configuration options can be listed in
# host statements.   If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.

#host passacaglia {
#  hardware ethernet 0:0:c0:5d:bd:95;
#  filename "vmunix.passacaglia";
#  server-name "toccata.fugue.com";
#}

# Fixed IP addresses can also be specified for hosts.   These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP.   Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.
#host fantasia {
#  hardware ethernet 08:00:07:26:c0:a5;
#  fixed-address fantasia.fugue.com;
#}

# You can declare a class of clients and then do address allocation
# based on that.   The example below shows a case where all clients
# in a certain class get addresses on the 10.17.224/24 subnet, and all
# other clients get addresses on the 10.0.29/24 subnet.

#class "foo" {
#  match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
#}

#shared-network 224-29 {
#  subnet 10.17.224.0 netmask 255.255.255.0 {
#    option routers rtr-224.example.org;
#  }
#  subnet 10.0.29.0 netmask 255.255.255.0 {
#    option routers rtr-29.example.org;
#  }
#  pool {
#    allow members of "foo";
#    range 10.17.224.10 10.17.224.250;
#  }
#  pool {
#    deny members of "foo";
#    range 10.0.29.10 10.0.29.230;
#  }
#}
use-host-decl-names on;
subnet 176.28.10.0 netmask 255.255.255.0 {
	group {
		next-server 176.28.10.34;
		filename "linux/pxelinux.0";
	}
}

Valentin · Jun 29, 2012

Verstehe ich das richtig, dass deine VMs bei dir zu Hause (oder wo auch immer) dhcpen, von deinem eigenen DHCP bei dir zu Hause (oder wo auch immer...) den next-Server <IP vom HE-Server> mit gibt und dein TFTP auf der HE-VM nicht reagiert?

Was sagen die Logs auf dem HE-Server?

DJ TWEETY · Jun 30, 2012

Valentin said:
Verstehe ich das richtig, dass deine VMs bei dir zu Hause (oder wo auch immer) dhcpen, von deinem eigenen DHCP bei dir zu Hause (oder wo auch immer...) den next-Server <IP vom HE-Server> mit gibt und dein TFTP auf der HE-VM nicht reagiert?

Was sagen die Logs auf dem HE-Server?

Also der Client der PXE Booten soll läuft bei mir in einer VM, während der Opsi auf den HE Server liegt DHCPen soll.

Und ja genau der Client findet den Server nicht.

Logs Folgen da ich mit den Tablet nicht viel machen kann

Valentin · Jun 30, 2012

während der Opsi auf den HE Server liegt DHCPen soll

Sorry, ich muss nochmal nachfragen:
Dein OPSI-Server bei Host Europe soll dhcpen?
Oder hast du deine VMs mit dem HE-Opsi via VPN verbunden?

DJ TWEETY · Jul 14, 2012

Sorry das ich jetzt erst antworte aber das mit dem Vpn hab ich ganz verplant bei der ganzen Arbeit.

So jetzt nur erstmal die beste Lösung herrausfinden.

OPSI Server auf Hosteurope Vserver

DJ TWEETY

New Member

Valentin

Registered User

DJ TWEETY

New Member

Valentin

Registered User

DJ TWEETY

New Member

Valentin

Registered User

DJ TWEETY

New Member

We value your privacy