IBM CSM to IBM Systems Director Transformation Guide

46 IBM CSM to IBM Systems Director Transformation Guide

EventDescription = ""

RearmExpression = "PercentTotUsed<75"

RearmDescription = ""

SelectionString = "Name==\"/tmp\""

Severity = "i"

NodeNames = {"p5570lp03"}

MgtScope = "m"

Toggle = "Yes"

EventBatchingInterval = 0

EventBatchingMaxEvents = 0

BatchedEventRetentionPeriod = 0

BattchedEventMaxTotalSize = 0

RecordAuditLog = "ALL"

p5570lp01(root)/>

򐂰 The response E-mail root anytime for the above condition is listed in Example 3-6.

Example 3-6 Show the details of the distributed RMC response

p5570lp01(root)/> lsresponse "E-mail root anytime"

Displaying response information:

ResponseName = "E-mail root anytime"

Node = "p5570lp01"

Action = "E-mail root"

DaysOfWeek = 1-7

TimeOfDay = 0000-2400

ActionScript = "/usr/sbin/rsct/bin/notifyevent root"

ReturnCode = -1

CheckReturnCode = "n"

EventType = "b"

StandardOut = "n"

EnvironmentVars = ""

UndefRes = "n"

EventBatching = "n"

p5570lp01(root)/>

򐂰 The lscondresp command shows the configured relationship between the condition and

the response. Refer to Example 3-7.

Example 3-7 Show the configured response to the condition in distributed RMC

p5570lp01(root)/> lscondresp

Displaying condition with response information:

Condition Response Node State

"Filesystem_Tmp_Monitor1" "E-mail root anytime" "p5570lp01" "Active"

򐂰 The /cfmroot director contains configuration files such as /etc/hosts, /etc/passwd, and

/etc/group. These configuration files are synchronized across the cluster nodes using the

Cluster File Management (CFM) capability in CSM. The update can be done using the

command cfmupdatenode.

3.2.3 Transformation to IBM Systems Director

In this scenario the IBM Systems Director Server is installed on the same LPAR as the CSM

Management Server. The following section demonstrates the step-by-step procedure. As

Chapter 3. Transformation scenarios 47

mentioned before, we do not document the details of installing IBM Systems Director Server

on AIX.

1. Update IBM Systems Director to the latest level.

2. Start the IBM Systems Director if not already started, as shown in Example 3-8.

Example 3-8 Command to start the IBM Systems Director Server

#/opt/ibm/director/bin/smstart

3. Check the status of the IBM Systems Director Server, as shown in Example 3-9.

Example 3-9 Command to check the status of IBM Systems Director Server

p5570lp01(root)/> smstatus

Active

p5570lp01(root)/>

4. Log in to the web interface as the root user and verify the version. Use the browser to open

the IBM Systems Director using the format shown in:

https://<ipaddress>:8422/ibm/console

Figure 3-3 shows the screen shot of the IBM Systems Director Welcome page. The version of

the Systems Director Server code can be seen to the right (here it is 6.2.1.2).

Figure 3-3 IBM Systems Director Welcome page

5. To view the systems managed by IBM Systems Director, use the left-hand navigation area

to select Navigate Resources  All Systems.

Note: The latest updates can be downloaded from the IBM Support Portal at:

http://www-933.ibm.com/support/fixcentral/

Note: “8422” is the default secure port used by IBM Systems Director. Use the

appropriate port if it has been changed in your environment.

48 IBM CSM to IBM Systems Director Transformation Guide

In Figure 3-4, only the LPAR installed with IBM Systems Director is listed because no

other LPARs have been discovered yet.

It shows two objects that represent the same LPAR, Virtual Server and Operating System.

Virtual Server represents the hardware container (LPAR), and Operating System

represents the operating system software instance.

Figure 3-4 Hardware and OS instance in IBM Systems Director

6. CSM uses NIM to install the AIX operating system and to update software on client

LPARs. Similarly, IBM Systems Director can also use a NIM server to install and update

the AIX operating system. Another way to install and update the OS is by using Storage

Copy Services with VMControl Standard Edition (also called Power Storage Based

Provisioning).

7. Without VMControl Standard Edition, IBM Systems Director cannot interact with a NIM

Server for AIX operating system installation. Therefore, the next step is to install the

VMControl plug-in.

Once the plug-in is installed, we need to install the VMControl subagent for NIM on the NIM

Server. Navigate through Release Management  Agents task on the left-hand navigation

bar. Then click All Agent Packages as shown in Figure 3-5 on page 49.

Select the CommonAgentSubagent_VMControl_NIM-2.3.1, click Install Agent and follow

the wizard.

Notes:

򐂰 High-level information about Storage Copy Service can be found in “VMControl

Storage Copy Services” on page 117.

򐂰 The IBM Systems Director Common Agent is responsible for communication

between the clients and the IBM Systems Director Server. The Common Agent on

the server should be at the highest level of code across the client LPARs.

Note: The VMControl installation steps can be found at:

http://publib.boulder.ibm.com/infocenter/director/v6r2x/topic/com.ibm.dir

ector.vim.helps.doc/fsd0_vim_pdf.pdf.

The plug-in can be found at:

http://www-03.ibm.com/systems/software/director/vmcontrol/