Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Example with console messages on SU /390

The following example shows the most important messages during an LM between two SU /390 with VM2000.
The messages are output on consoles of three different systems.
To differentiate between those three better, they outputs are written in different colours.
The console header of the messages was cut off to the timestamp, as it has no role here:

Console messages of the monitor system from the protocol file on the target SU:

000659 MIGRATE-VM VM-ID=12,SERVER-UNIT-NAME=ABGSE701                                          Start of LM
000700 %  VMS2450 LIVE MIGRATION OF VM (12,VM12PROD) TO TARGET SU 'ABGSE701' STARTED                    1
000719 %  VMS2452 VM (12,VM12PROD) SUSPENDED AT LIVE MIGRATION TO TARGET SU 'ABGSE701'                  7
000723 %  VMS4009 DEVICE 'CS' REMOVED FROM VIRTUAL MACHINE (12,VM12PROD)                               13
...
000723 %  VMS4009 DEVICE 'FAA4' REMOVED FROM VIRTUAL MACHINE (12,VM12PROD)
000723 %  VMS4009 DEVICE 'FAA5' REMOVED FROM VIRTUAL MACHINE (12,VM12PROD)
000723 %  VMS4024 VIRTUAL MACHINE (12,VM12PROD) TERMINATED                                             14
000724 %  VMS2451 LIVE MIGRATION OF VM (12,VM12PROD) TO TARGET SU 'ABGSE701' COMPLETED                 15
   
   

Console messages of the monitor system from the protocol file on the target SU:

000701 %  VMS2430 LIVE MIGRATION OF VM (12,VM12PROD) FROM SOURCE SU 'ABGSE501' STARTED                  4
000701 %  VMS3050 VIRTUAL MACHINE (12,VM12PROD) CREATED                                                 5
000703 %  VMS4005 DEVICE 'CS' ASSIGNED TO VIRTUAL MACHINE (12,VM12PROD)                                 6
...
000703 %  VMS4005 DEVICE 'FAA4' ASSIGNED TO VIRTUAL MACHINE (12,VM12PROD)
000703 %  VMS4005 DEVICE 'FAA5' ASSIGNED TO VIRTUAL MACHINE (12,VM12PROD) (TYPE=SD)
000722 %  VMS2432 VM (12,VM12PROD) RESUMED AT LIVE MIGRATION FROM SOURCE SU 'ABGSE501'                  9
000723 %  VMS2431 LIVE MIGRATION OF VM (12,VM12PROD) FROM SOURCE SU 'ABGSE501' COMPLETED               12

Console messages of the system VM12PROD that needs to be migrated before the migration:

000701 % ETMDR01 DYNAMIC RECONFIGURATION WITH FUNCTION 'MIGRATE' STARTED                                2
000701 % MCS1002 GLOBAL MSCF CONFIGURATION PARAMETER 'RECOVERY-START' CHANGED FROM '*AUTOMATIC' TO      3
         'LOCKED'

Console messages of the system VM12PROD that needs to be migrated after the migration:

000721 % ETMDR03 LIVE MIGRATION FROM SOURCE CONFIGURATION '390SU- 500-10B' TO TARGET                    8
         CONFIGURATION '390SU- 700-70' FINISHED. INITIAL CONFIGURATION WAS '390SU- 700-70'
000723 % BCA07DC LINE "L#MANLO1" active                                                                10
000723 % BCA05EC VLAN-LINE "L1#DANPU" active
000723 % BCA05EC VLAN-LINE "L1#MANPU" active
000723 % BCA05EC VLAN-LINE "L1#MCNPR" active
000723 % MCS1002 GLOBAL MSCF CONFIGURATION PARAMETER 'RECOVERY-START' CHANGED FROM 'LOCKED' TO         11
         '*AUTOMATIC'

Explanation of the messages in chronological sequence of appearance on the respective consoles: (Indentations and colours mean: target SU | migrating VM | target SU.)

1: After entering the command /MIRATE-VM the preconditions for an LM on the source SU and target SU were checked, and the LM was started.

2: The guest system was informed about the upcoming transfer.

3: The automatic MSCF outage recognition was deactivated locally and on all partners.

4: The LM is announced in monitor system of the target SU.

5: The VM configuration of the guest system that needs to be transferred was transferred to the monitor of the target SU.
With the information from the VM configuration the VM is set up on the target SU.
Then, transfer of the main memory of the VM from the source SU to target SU starts.

6: The devices assigned VM 12 on the source SU are also assigned on the target SU.

7: The guest system was stopped on the source SU and the remaining part of the main memory and the register contents were transferred from the source SU to target SU. 

8: The guest system is started on the target SU and I/O system was started.

9: In the monitor system of the target SU the successful restart of the guest system was protocolled.

10: In the guest system BCAM has activated the IP addresses of the system on the new LAN devices of the target SU and made the changed addresses known in the network.

11: The MSCF outage recognition was activated.

12: The successful end of the LM was protocolled on the console of the monitor system of the target SU.

13: The system is running now on the target SU again, which also means that the no longer needed resources on the source SU are released.

14: The VM with VM ID 12 was terminated on the source SU and the VM definition was deleted.

15: Final message VMS2541 after which all actions of the LM were executed.