3.
The CLI prompts you to select the appropriate job ID to perform the operation on the selected
job. The following are examples of the migration job action commands:
MPX200 (miguser) #> migration stop
Job Id
------
0
1
Please select a Migration Job Id from the list above ('q' to quit): 1
All attribute values for that have been changed will now be saved.
MPX200 (miguser) #> migration start
Job Id
------
1
Please select a Migration Job Id from the list above ('q' to quit): 1
Migration Start Time for JobId 1:(1=Now, 2=Delayed, 3=JobSerialScheduling)
[Now
Please specify a Date & Time (in format)
when the migration should start. This should be
within the next 30 days.
All attribute values for that have been changed will now be saved.
MPX200 (miguser) #> migration pause
Job Id
------
0
Please select a Migration Job Id from the list above ('q' to quit): 0
All attribute values for that have been changed will now be saved.
MPX200 (miguser) #> migration resume
Job Id
------
0
Please select a Migration Job Id from the list above ('q' to quit): 0
All attribute values for that have been changed will now be saved.
Viewing system and data migration job logs
The mpx Manager provides two types of logs: system and data migration job. You can view system
and data migration job logs from both the GUI and the CLI.
Type
Status
----
-----------------
Offline Scheduled
Offline Running ( 4%)
Type
Status
----
-----------------
Offline Stopped
] 2
Type
Status
----
-----------------
Offline Running ( 16%)
Type
Status
----
-----------------
Offline Paused ( 18%)
LUN ID
LUN Size(MB)
------
------------
7
10000
8
10000
LUN ID
LUN Size(MB)
------
------------
8
10000
[
LUN ID
LUN Size(MB)
------
------------
7
10000
LUN ID
LUN Size(MB)
------
------------
7
10000
MPX200 Multifunction Router
Src Symbolic Name
-----------------
HP MSA-1
HP MSA-1
Src Symbolic Name
-----------------
HP MSA-1
] 100815002009
Src Symbolic Name
-----------------
HP MSA-1
Src Symbolic Name
-----------------
HP MSA-1
173