SUSE Conversations


Installing ZENworks Linux Management 7.3 Agent on Remote Servers

mfaris01

By: mfaris01

September 24, 2009 10:21 am

Reads:294

Comments:0

Rating:0

Like me, many of you have multiple Linux servers to contend with and maintain. Even though ZENworks Linux Management allows you to do numerous, helpful tasks with these servers, you still have to install the agent. Not having the luxury of direct access to these servers and I did not include the ZLM 7.3 Agent in the server build, I had a dilemma. How do I get the servers to install this 600+MB CD image without outside intervention? Once I had burned the ISO to a CD, I found that there are some hard links that can’t be copied, because they point to targets that will be used after the install completes. So copying the ISO data was out. I read some stuff about creating an Add-on in YaST and it worked beautifully. I’ve added some additional stuff that can help prevent further balding. Here’s how I did it.

ZLM Server Setup

I’ll assume that you’ve setup downloaded the ISOs and completed your ZLM Server installation.

I also used my ZLM server for NFS mounts of my installation sources for SuSE Linux Enterprise Server (SLES) 10 and Open Enterprise Server 2 and configured all other SLES10 and SLES10/OES2 servers to use this server. So when I created my ZLM 7.3 Agent install point, I used this method also. But first, we need to download a file from Novell that will allow us to create an Add-on ISO for our deployment.

A utility to perform this is available for download, novell-zenworks-yast-add-on.rpm performs this task very easily. http://download.novell.com/Download?buildid=OLLk5l89cQY~

Download this to your source server and install it with the following command:

# rpm –ivh novell-zenworks-yast-add-on.rpm

Before we can use this utility, let’s make sure the ZLM 7.3 Agent ISO is mounted.

I create temporary mount points under /mnt/ like, /mnt/disk/ and my permanent nfs mount points (for servers to point to for sources) under /install/

We’ll mount the ZLM 7.3 Agent ISO under a temporary mount point to build our Add-on image.

# mount –o loop /dir-where-you-keep-iso-files/ZLM73_Agent.iso /mnt/disk

Now I create a directory where I want to store my Add-on ISO, once it’s created.

# mkdir /install/zlm73agent

With all that done, we can use our utility to create our ZLM Add-on ISO.

The utility is called zlm-create-yast-add-on and here are our options to create our file.

  • -i ISO-name-to-be-created If you omit this option, then zlm-add-on.iso is created.
  • -m mount-point-of-ZLM73_Agent This is where we mounted the original ISO.
  • -o where-we-want-the-Add-on-iso-created The output file location.
  • -c SLES-Version This is the version of SLES that we are building this for, not the current server this resides. Options are 9, 10, 11

Run the following command to create our Add-on ISO file.

# zlm-create-yast-add-on –i zlm-addon –m /mnt/disk –o /install/zlm73agent/ -c 10

When complete, you’ll see the file /install/zlm73agent/zlm-addon.iso

Pretty cool stuff!

Remote Server Installation

Connect to your remote (Target) server and login as root.

Run the following command to start yast with add-on.

# yast add-on

By the way, you can list available yast shortcuts by typing “yast –list” and it will give you a list of options to start YaST with that specific module. “add-on” is one of those modules.

Select the method of media the Add-on ISO is located. NFS in my example.

Click Next

Enter the Server Name and path to the ISO.

Check the ISO box and click OK

YaST will read the details of the source and then prompt for the License Agreement.

Accept the License Agreement and click Next.

Select Filer and click Patterns. You will see the list appear. Scroll to the bottom and choose which of the following components of the agent you wish to install.

ZLM Agent on X Agent installation without X-related packages. Default.
ZLM Agent X Agent installation with X.
ZLM Agent Imaging Agent imaging agent component.
ZLM Agent OEM Agent OEM packages for Dell machines.
ZLM agent All Full installation of the Agent

I selected all but OEM for obvious reasons.

The only resolve I had had to do with a conflict with Python, but it resolved during the install. Click Continue and the packages will be installed. When complete, you will be asked if you want to install any more packages, select no, and YaST will exit.

There is one thing I had to do to help with rug registering with the ZLM server. Since Novell servers generate their own certificates which makes them give you the pop up in your browser because their validity is unknown. This causes a problem with zmd and will cause the agent registration to fail.

Change the option in rug for “require-verified-certs” from True to False. You can do this two ways:

# rug set-prefs require-verified-certs False

Or

Edit /etc/zmd/zmd.conf and change the same option and restart zmd.

# rczmd restart 

I have found that zmd likes to “hang” even though it’s just busy. Sometimes I choose to kill it and then start it to reflect the changes.

Now we can register this server in ZLM.

# rug sa https://ZLMServer_DNS_name_or_IP

You will see the red progress bar (Command line) and you can verify with this command:

# rug sl

# | Status | Type | Name      | URI
--+--------+------+-----------+----------------------------------------------
1 | Active | ZENworks | | http://blr-srm-r2p.mycompany.org

Your server will be listed as Active

Now let’s go see our server in ZENwork Linux Management Console.

Conclusion

As you can see the are a couple of steps and if you need some additional experience getting used to the cdl, (command line), having numerous servers to configure will help you get that experience. Take this example and find new ways to automate it, make it better.

Enjoy!

VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

Tags: ,
Categories: SUSE Linux Enterprise Server, Technical Solutions

Disclaimer: As with everything else at SUSE Conversations, this content is definitely not supported by SUSE (so don't even think of calling Support if you try something and it blows up).  It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.

Comment

RSS