Configuring HP SIM for Optimal Performance in Large Environments
existing
Systems Insight Manager
deployments.
HP
recommends
that
you consult
the
Sizer
tool
when
considering
CMS
hardware
and
database configurations.
The
Systems Insight Manager
Sizing
Tool
is
located
at
http://www.hp.com/go/insight/sizer.
Customizing
Systems Insight Manager
to
your
environment
Creating
a
hierarchy:
One
master
CMS
with
several
regions
When
creating
a
hierarchy
in
an
environment
where
systems
can
be
broken
down
into
region consider
creating
one
master
CMS
and
several
regional
CMS.
To
create
a
hierarchy:
1.
Create
the
master
CMS
to
collect
the
entire
event
that
is
important
to
the
business:
critical,
major, and
all
ProLiant
events.
2.
Install
any
plug-ins
on
the
regional
CMS.
You
must
install
each
plug-in
based
on
the
use
to
the
specific
region.
For
example,
if
Region
A
has
a virtual
environment
and
Region
B
does
not,
only
Region
A
has
HP
Insight
Virtual
Machine Manager
software
for
ProLiant
(VMM
PL)
plug-in
installed.
The
following
examples
are
uses
for
a
master
CMS
and
regionalized
CMS:
Master
CMS:
o
List
of
all
server
and
important
systems
o
For
inventory,
contract,
and
warranty
o
Long
poll
cycles
(daily)
o
Daily
data
collections
(off-production
hours,
by
region)
o
No
event
handling
except
for
it
regional
CMS
Regionalize
CMS
for:
o
Better
event
handling—fewer
events
o
Use
for
active
plug-in—VMM,
VPM,
PMP,
VCRM
Discovery
related
IP
range
By
default,
Systems Insight Manager pre-populates
the
discovery
IP
range
with
the
network
subnets
used
by
the
management
server.
You
must
modify
this
to
represent
the
correct
range
of
systems
that
you
need
to manage
in
your
group.
The
Inclusion
and
Exclusion
ranges
enable
you
to
fine-tune
the
systems
that you
want
to
discover
using
IP
range
pinging.
After
Systems insight Manager
is
installed
and
the
Discovery
IP
range
is
established,
the
discovery
process
must
run
to discover
the
systems
on
your
network.
For
an
empty
database,
the
maximum
time
needed
to
complete an
IP
range
scan
for
initial
system
detection
is
in
seconds
(a
f
ully
populated
network
can
take
a
shorter
time).
can
be
calculated
from
the
range
you
indicate
in
the
Inclusion
Range, less
the
IP
addresses
in
the
Exclusion
Range
(if
any).
By
default,
is
the 254
IP
addresses
for
each
subnet
the
management
server
is
connect
to,
using
a
class
“C”
network mask
scheme.
The
Automatic
Discovery
window
shows
the
progress
of
discovery.
System
status polling
and
data
collection
are
invoked
when
new
systems