Workload Partitions: Part 2 – WPAR Agent activation and discovery Print E-mail
User Rating: / 2
PoorBest 

In this article we will display the actions required to register an AIX system with the WPAR Manager so that WPAR's can be created on and moved between participating systems.

The previous article shows how to install the WPAR Manager. 

 

Recall that all the systems are being installed, or cloned, from a single mksysb image. One reason for this is to assure that all the agent systems have the same level of AIX installed. This uniformity is important to ensure that Live Application Mobility will function properly.

The first requirement is to replace the tivguid (GUID) that is present in the image.

Image

As it is a simple command, it can also be performed in parallel.

Image

However, actually registering with the agent requires either configuration file, or as I did here, that you enter the password needed to register with the WPAR Manager.

Image

After the command completes and you startup the WPAR manager you should see your system under the managed systems.

Image

However, if the Managed System window is already open, it may not be visible immediately. In those cases you can use the Discover command. This is also useful for when agent systems were offline when the Manager session was started.

Image

And after. All four (4) clients are shown in the list of managed systems.

Image

In the next article we shall look at creating and moving a system WPAR.

 
< Prev   Next >



eXTReMe Tracker

Terms of Use and Privacy and Security Policies
Copyright 2001-2012 Michael Felt, John R Peck and ROOTVG.NET