HP Matrix Operating Environment Software - Manual (Page 26)

1. Configure secondary CMSs.
When complete, this step configures Systems Insight Manager's federated CMS list on the
primary CMS, exchanges certificates between the primary and secondary CMSs, configures
the primary CMS as trusted on the secondary CMSs, and displays the newly added CMSs in
Systems Insight Manager.
a.
On the primary CMS, in Systems Insight Manager, select Options
→Federated CMS
Configuration….
b. Click Add CMS….
c. In CMS name, enter the secondary CMS FQDN and then click Next.
d. In Verify Remote CMS Certificate, verify the certificate, and then click Next.
e. In Configure Remote CMS, enter the Systems Insight Manager user name and password,
and then click Finish.
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 <cms-FQDN>
where <cms-FQDN> 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 host name and primary CMS FQDN.
a.
On the primary CMS, open a prompt dialog.
b. Enter mxgethostname and note the host name 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.
26 Installation and configuration