HP Matrix Operating Environment Software - Manual (Page 163)

discovery can also find Microsoft Hyper-V hosts with a similar effect if the guests are later
rediscovered with valid host name or IP address.)
• If a system is multi-homed and its multiple IP addresses or network names are discovered
in HP SIM, only one "system node" is recorded in HP SIM to represent that server (the
Primary IP Address). This node will contain the list of IP addresses and network names for
that system. HP SIM randomly selects which IP address and network name pair becomes
the default Primary IP Address used for the node's short name. If you edit the “System
Properties” and change the "Primary IP Address", any data associated with the previous
workload name reference will be “lost”.
• A system is initially discovered by IP address ONLY (for example, in a non-DNS
environment). Later the system is identified in HP SIM by its fully-qualified host name
(when DNS is subsequently enabled in the environment).
• Also in a non-DNS environment, a Windows system may be initially discovered by its
NetBIOS name. If DNS is later enabled in the environment, that system may be subsequently
identified by its fully-qualified host name.
how this can occur:
Suggested prevention: Make sure that all managed systems are identified the way you expect
in HP SIM as soon as possible, and that they will remain identified that way during the period
that you intend to collect data for those systems.
For example:
•
For VMware ESX VMs, if you ever plan to install VMware Tools on the VM guests, install
the tools on all the guests OR enter the host name or IP address of all guests in the HP SIM
discovery task, rather than depend on horizontal discovery. (This latter option should be
applied to Hyper-V hosts also.)
• For multi-homed systems, discover only one IP address, or set the Primary IP Address
immediately after discovery to insure that you have set the final name that you want the
node to have before running Insight managed system setup wizard and data collection.
• If you are using DNS (or are planning to use DNS), make sure all systems are correctly
discovered with a fully-qualified host name in HP SIM.
Recovering system profile data lost due to a network name change:
1.
Determine the name that the system was previously identified as.
If not sure what the "old" name was, run capprofile to list the available profiles in Capacity
Advisor.
2. Export the data from the old profile to a CSV file using capprofile -x.
3. Import the exported profile into the "new" profile using capprofile -i.
For other issues where data seems to be incorrect, see:
•
Data for node appears to differ from one profile viewer to another (page 166)
• A configuration change is not immediately visible in all Insight Dynamics products (page 166)
• “Data may appear to be old when it is not” (page 161)
Out-of-memory errors in the Java heap
A few situations can cause the Java heap to run out of memory.
Spiking the mxdomainmgr server process
When capcollect is executed, its initial invocation
causes a temporary spike in memory use of the server process named "mxdomainmgr". If the
HP SIM server is currently managing a large number of systems, there is a small chance that this
spike in memory could cause the server process to reach its maximum configured memory
allocation. Suggested action: See the Insight Dynamics install guide specific to your OS platform
for more information on tuning configuration parameters .
Editing a scenario containing a large number of systems and/or workloads
When using an "Edit
Scenario" screen in Capacity Advisor, the number of workloads included in the scenario and the
selected data range to use for analysis will affect how much memory is used in the HP SIM server
process to read and analyze the scenario. Initially editing the scenario will invoke the action to
read and analyze the utilization data of all systems and workloads defined in the scenario. The
Out-of-memory errors in the Java heap 163