beautypg.com

Create user groups on secondary cmss – HP Matrix Operating Environment Software User Manual

Page 20

background image

f.

Repeat steps b through e for each secondary CMS.

2.

Configure logical server management to increase memory allocation

If a primary or a secondary CMS will manage more than 1000 nodes, increase the logical
server management JVM heap size.
a.

On each CMS that is configured to manage more than 1000 nodes, in Windows Explorer,
navigate to ..\Program Files\HP\Virtual Server Environment\conf\lsa

b.

Edit hp_lsa_service.conf

c.

Change wrapper.java.maxmemory=1024 to wrapper.java.maxmemory=2048,
and save the file.

3.

Restart affected services on each secondary CMS
a.

On the secondary CMS desktop, select Start

→Administrative Tools→Services

b.

Select HP Global Workload Manager Central Management Server, then select
Action

→Restart

c.

Select HP Logical Server Automation, then select Action

→Restart

d.

Repeat steps a through c for each secondary CMS.

4.

Inform infrastructure orchestration about the new CMSs added to the federation
a.

On the primary CMS, open a prompt dialog

b.

For each CMS added to the federation, enter:

ioexec add cms –C

where is identical to the secondary CMS FQDN name specified in step
1c above.

5.

In a clustered High Availability (HA) federated CMS environment, uncomment and specify the
wrapper.java.additional.15

property in hpio.conf.

In a clustered HA environment, there may be multiple IP addresses in each CMS, and the
CMS name may be different than the computer name. Uncomment the following property and
specify the FQDN or IP address of the CMS.

For example, for a CMS named "CMS-blue.hp.com”, change:

#wrapper.java.additional.15=-Dfed.cms.name=[FQDN or IP]

to

wrapper.java.additional.15=-Dfed.cms.name=CMS-blue.hp.com

6.

Verify hostname and primary CMS FQDN
a.

On the primary CMS, open a prompt dialog

b.

Enter mxgethostname and note the hostname that is returned

c.

In Systems Insight Manager, select Options

→Federated CMS Configuration…. The name

of the primary CMS should be the same as the one returned by mxgethostname.

Create user groups on secondary CMSs

On all secondary CMSs, manually create the IO user groups.
1.

Select Start

→Administrative Tools→Computer Management.

2.

Expand Local Users and Groups.

3.

Add the following user groups using steps a through c.
a.

Right-click Groups.

b.

Select New Group and create the HPIO_Administrators group.

c.

Repeat steps a and b to create the groups: HPIO_Architects and HPIO_Users.

NOTE:

Ensure that all CMSs in a federated CMS environment have their user accounts

synchronized by creating the same user accounts on primary and secondary CMSs.

20

Installation and configuration