ZENworks Linux Management and a SUSE Installation Service on One Server

This document is intended for those that would like to setup a ZENworks Linux Management Server and a SUSE Installation Service all on One Server. Follow the instructions below and you will have this working in no time. Note: The versions of software used in this document may not be significant to getting this working.

For the Environment, I would prefer you use a supported platform for ZENworks Linux Management in order to set this up. For the latest in supported platforms for the latest version of ZENworks Linux Management you can go here. The Environment being used for this document is SLES 10 running as a Virtual Machine in VMWare Server with two network interface cards. You could also use a Secondary IP Address and accomplish the same thing.

Once you have successfully installed the ZENworks Linux Management Server we can move into configuring the java service that runs the ZCC (ZENworks Control Center) so that it binds to a specific IP address. Follow these numbered steps to accomplish this.

1. Open your favorite shell and change your directory to /etc/opt/novell/zenworks/tomcat/base

1. Using your favorite editor open the file server.xml and make changes to the following lines.You will notice the only change is the address=”10.10.10.10″

Before:

<Connector port="8080"
     maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
     enableLookups="false" redirectPort="8443" acceptCount="100"
     debug="0" connectionTimeout="20000"
     disableUploadTimeout="true" />

<Connector port="8443"
     maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
     enableLookups="false" disableUploadTimeout="true"
     acceptCount="100" debug="0" scheme="https" secure="true"
     clientAuth="false" sslProtocol="TLS" />

After:

<Connector port="8080"
     maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
     enableLookups="false" redirectPort="8443" acceptCount="100"
     debug="0" connectionTimeout="20000"
     disableUploadTimeout="true" address=?10.10.10.10? />

<Connector port="8443"
    maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
    enableLookups="false" disableUploadTimeout="true"
    acceptCount="100" debug="0" scheme="https" secure="true"
    clientAuth="false" sslProtocol="TLS" address=?10.10.10.10? />

1. Now we will restart the ZENworks Services with the command zlm-config ?restart

1. Now you can run a netstat -nlp | grep jsvc and you will see the output like below.

tcp   0   0 10.10.10.128:80    0.0.0.0:*     LISTEN  9938/jsvc.exec
tcp   0   0 10.10.10.128:443   0.0.0.0:*     LISTEN  9938/jsvc.exec

Notice that it is only bound to the one ip address.

Since we have changed this and it is no longer listening on all open interfaces including localhost, you will notice that tools such as zlman will no longer work since by default they try to connect on the localhost interface. In order to get around this you will have to issue the command like this below.

zlman - -host=10.10.10.128 -Uadministrator -Ppassword (then some zlman command)

Notice the host switch after zlman, this is what you will need to run in order to get zlman to talk over your bound interface otherwise by default it will try localhost and fail to connect.

That concludes our configuration of ZENworks Linux Management and binding the java service for the ZCC onto one IP address. Now we want to conclude this document by setting up the SUSE Installation Service so that it is bound to the other IP address you have setup on your system. Note that We are assuming you already have setup or know how to setup a SUSE Installation Service over HTTP; if you don’t know how to set one up then you can follow this document here for SLES 10 and here for SLES 9.

Follow the numbered steps below to bind HTTP to the other IP address configured on your server.

1. Open your favorite shell and change your directory to /etc/apache2

1. Using your favorite editor open the file listen.conf and make a change to the following line.

Before:

Listen 80

After:

Listen 10.10.10.11:80

1. Now we will restart Apache2 with the command rcapache2 restart

1. Now you can run a netstat -nlp | grep httpd and you will see the output like below.

tcp   0   0 10.10.10.129:80    0.0.0.0:*     LISTEN  16665/httpd2-prefor

Notice that httpd is now bound to the one ip address.

That concludes our configuration of SUSE Installation Service and binding to the other IP address you have setup on your system. In conclusion i would like to remind you that this is not a supported configuration, but if you have the need in your environment because of restrictions or just for the sake of consolidation by all means this solutions works well.

Enjoy!!