Data migration of an existing Microsoft Windows CMS to a new Insight Software 6.2 system
37
For more details refer to
Running the export utility on the source CMS
.
Import:
The import command
-
line (CLI) command and syntax is:
mximport [
–
f <filename>] [
-
p password][
-
v cluster ip][
-
n cluster name]
–
v
—
Mandatory
. Used to specify the Cluster IP
also known as the
MSCS cluster
virtual server IP
address
of
the
target CMS.
–
n
—
Mandatory
. Used to specify the Cluster Name/Host Name
also known
as
Cluster name is the
MSCS cluster virtual server name
of
the
target CMS. If Cluster Name/Host Name is not available then
pass Cluster IP.
Example
1:
The
following
CLI command is used for importing the
data
into
Cluster CMS
setup
:
mximpo
rt
-
f<File Name>
–
p <password>
–
v <Cluster IP>
-
n <Cluster Name>
For more details, see
Runni
ng the import utility on the tar
get CMS
.
Appendix D: Partner
Services Tool
The partnerservice tool is a batch script located in the
Systems Insight Manager
installation directory.
Before executing any of the following commands, open a command prompt window and set your
directory to the
Systems Insight Manager
instal
lation directory
.
Partner Service CLI
u
sage
Stopping services
To
stop all part
ner services
, issue the following command:
partnerservice
-
stop all
To
stop
a
specific partner service
, issue the following command:
partnerservice
-
stop <
partner id>.
For example
,
partnerservice
-
stop hpsim
Systems Insight Manager
and all other
Systems Insight Manager
dependent services
are
stopped.
Starting services
To
start all partner services
, issue the following command:
partnerservice
-
start all
To
start
a
specific partner service
, issue the following command:
partnerservice
-
start <partner id>.
For example
,
partnerservice
-
start hpsim
Systems Insight Manager and all other Systems Insight Manager dependent services are stopped
.