During this section the restored VCEM database will be resynchronized with the state of the VC Domain managed by VCEM. During the first phase, the mxsync tool will scan the VC Domains managed by VCEM. If changes occurred after backup that could cause the VCEM product resynchronization to fail, the mxsync tool will recommend making changes to the restored VCEM database to resolve the identified issues.
For the sample run, the changes recommended by mxsync during phase 1 of section 2 are summarized in Table 12.
Table 12. Summary of mxsync VCEM phase 1 actions.
Post-backup Activity Pre-mxsync State
Standby HP IO service S1_VC_Test.
The profile is assigned to a blade in the restored VCEM database, but the profile no longer exists in the underlying VC Domain configuration.
Changed the state of the profile to unassigned in the VCEM database.
Activate logical server LS2_VC_Test.
Resume HP IO service S2_VC_Test.
The profile is unassigned in the restored VCEM database, but the profile is assigned to a blade in one of the underlying VC Domain configurations.
Remove profile from the VCEM database. The profile definition will be recreated during phase 2.
Create logical server LS3_VC_Test.
Create HP IO service S3_VC_Test.
The profile does not exist in the restored VCEM database.
Note: If the profile was assigned to a blade when the failure occurred, the profile definition will exist in one of the underlying VC Domain configurations.
However, if the profile was unassigned when the failure occurred, the profile definition will be lost and need to be recreated.
The profile definition will be added to the VCEM database during phase 2.
Note: Once or more addresses assigned to the LS3_VC_Test profile are still assigned to the LS4_VC_Test profile in the restored VCEM database. To resolve the duplicate reference, delete the LS4_VC_Test profile from the restored VCEM database.
One or more addresses assigned to the S3_VC_Test profile are still assigned to the S4_VC_Test profile in the restored VCEM database. To resolve the duplicate reference, delete the S4_VC_Test profile from the restored VCEM database.
Delete logical server LS4_VC_Test Delete HP IO service S4_VC_Test.
Lease on HP IO service S5_VC_Test expires.
The profile is assigned to a blade in the restored VCEM database, but the profile no longer exists in the underlying VC Domain configuration.
Delete the profile from the restored VCEM database.
Note: In both cases, the delete recommendation is triggered because the addresses assigned to the profile have already been reallocated to a new profile in an underlying VC Domain.
+---+
| Section 2 of 5 |
| Virtual Connect Enterprise Management | +---+
Synchronizes VCEM with the state of the underlying VC Domains.
**** Analysis: Resolve conflicting resource assignments. ****
**** Section 2 of 5, phase 1 of 2 ****
Update or remove VCEM resources that conflict with the underlying VC Domains.
Checking VC Domain Domain_15_186_24_107
RESOLUTION: The VCEM profile will be unassigned.
Delete VCEM profile S2-VC-1_1241e8159af...[ACTION]
ISSUE: The VCEM profile is not assigned consistent with the corresponding VC profile assignment.
RESOLUTION: The VCEM profile will be deleted.
Delete VCEM profile S4-VC-1_12425e0bf54...[ACTION]
ISSUE: The VCEM profile is assigned addresses that are in use by VC profile S3-VC-1_1242896729c:
50:06:0B:00:00:C2:62:57, 00-17-A4-77-00-4C, 00-17-A4-77-00-4D.
RESOLUTION: The VCEM profile will be deleted.
Delete VCEM profile S5-VC-1_12426f64058...[ACTION]
ISSUE: The VCEM profile is assigned addresses that are in use by VC profile S3-VC-1_1242896729c:
50:06:0B:00:00:C2:62:68, 50:06:0B:00:00:C2:62:6B, 50:06:0B:00:00:C2:62:69, 00-17-A4-77-00-5D, 00-17-A4-77-00-60.
RESOLUTION: The VCEM profile will be deleted.
Unassign VCEM profile vsels_LS1_VC_Test...[ACTION]
ISSUE: The VCEM profile is assigned but there is no corresponding VC profile.
RESOLUTION: The VCEM profile will be unassigned.
Delete VCEM profile vsels_LS2_VC_Test...[ACTION]
ISSUE: The VCEM profile is not assigned consistent with the corresponding VC profile assignment.
RESOLUTION: The VCEM profile will be deleted.
Delete VCEM profile vsels_LS4_VC_Test...[ACTION]
ISSUE: The VCEM profile is assigned addresses that are in use by VC profile vsels_LS3_VC_Test:
50:06:0B:00:00:C2:62:4F, 50:06:0B:00:00:C2:62:4E, 50:06:0B:00:00:C2:62:51, 50:06:0B:00:00:C2:62:50, 00-17-A4-77-00-1C, 00-17-A4-77-00-41,
00-17-A4-77-00-1E, 00-17-A4-77-00-44.
domain or the VCEM profile is unassigned.
RESOLUTION: The addresses will be marked EXTERNAL.
Mark VC profile S3-VC-1_1242896729c addresses external:
50:06:0B:00:00:C2:62:68, 50:06:0B:00:00:C2:62:57, 50:06:0B:00:00:C2:62:6B, 50:06:0B:00:00:C2:62:69,
00-17-A4-77-00-4C, 00-17-A4-77-00-5D, 00-17-A4-77-00-4D,
00-17-A4-77-00-60...[ACTION]
ISSUE: The addresses used by the VC profile are either not assigned to a corresponding VCEM profile for the same domain or the VCEM profile is unassigned.
RESOLUTION: The addresses will be marked EXTERNAL.
Mark VC profile vsels_LS2_VC_Test addresses external:
50:06:0B:00:00:C2:62:5E, 50:06:0B:00:00:C2:62:3E, 50:06:0B:00:00:C2:62:60, 50:06:0B:00:00:C2:62:5F,
00-17-A4-77-00-51, 00-17-A4-77-00-55, 00-17-A4-77-00-54,
00-17-A4-77-00-5C...[ACTION]
ISSUE: The addresses used by the VC profile are either not assigned to a corresponding VCEM profile for the same domain or the VCEM profile is unassigned.
RESOLUTION: The addresses will be marked EXTERNAL.
Mark VC profile vsels_LS3_VC_Test addresses external:
50:06:0B:00:00:C2:62:4F, 50:06:0B:00:00:C2:62:4E, 50:06:0B:00:00:C2:62:51, 50:06:0B:00:00:C2:62:50,
00-17-A4-77-00-1C, 00-17-A4-77-00-41, 00-17-A4-77-00-1E,
00-17-A4-77-00-44...[ACTION]
ISSUE: The addresses used by the VC profile are either not assigned to a corresponding VCEM profile for the same domain or the VCEM profile is unassigned.
RESOLUTION: The addresses will be marked EXTERNAL.
Analysis summary:
Analysis completed successfully. You may choose to execute synchronization actions now or stop the synchronization process. If the synchronization process is stopped, it can be started again later.
>>> Would you like to perform the actions now? (Y/N): y
**** Execution: Resolve conflicting resource assignments. ****
**** Section 2 of 5, phase 1 of 2 ****
Unassign VCEM profile S1-VC-1_1241e815059...[OK]
Delete VCEM profile S2-VC-1_1241e8159af...[OK]
Delete VCEM profile S4-VC-1_12425e0bf54...[OK]
Delete VCEM profile S5-VC-1_12426f64058...[OK]
Unassign VCEM profile vsels_LS1_VC_Test...[OK]
Delete VCEM profile vsels_LS2_VC_Test...[OK]
Delete VCEM profile vsels_LS4_VC_Test...[OK]
Mark VC profile S2-VC-1_1241e8159af addresses external:
50:06:0B:00:00:C2:62:32, 50:06:0B:00:00:C2:62:54, 50:06:0B:00:00:C2:62:34, 50:06:0B:00:00:C2:62:33,
00-17-A4-77-00-16, 00-17-A4-77-00-3B, 00-17-A4-77-00-17,
50:06:0B:00:00:C2:62:60, 50:06:0B:00:00:C2:62:5F,
00-17-A4-77-00-51, 00-17-A4-77-00-55, 00-17-A4-77-00-54,
00-17-A4-77-00-5C...[OK]
Mark VC profile vsels_LS3_VC_Test addresses external:
50:06:0B:00:00:C2:62:4F, 50:06:0B:00:00:C2:62:4E,
>>> Please press [ENTER] to continue:
During the second phase of the VCEM section, mxsync will issue requests to VCEM to resynchronize each VC domain managed by VCEM.
Note: During the analysis step of phase 2, mxsync will display an ISSUE for each VC Domain managed by VCEM stating that the VC Domain MAY need to be synchronized with VCEM. This is only a potential issue. The test to check if the VC Domain is out of sync will temporarily place the VC Domain in
maintenance mode and therefore can only be performed during the execution step.
**** Analysis: Domain synchronization ****
**** Section 2 of 5, phase 2 of 2 ****
Synchronize the state of VCEM with the defined VC Domains.
Synchronize VC Domain mxsync_domain_A in VCEM...[ACTION]
ISSUE: VCEM may be out of sync with the VC Domain.
RESOLUTION: The VC Domain will be checked and, if necessary, synchronized in VCEM.
Synchronize VC Domain mxsync_domain_B in VCEM...[ACTION]
ISSUE: VCEM may be out of sync with the VC Domain.
RESOLUTION: The VC Domain will be checked and, if necessary, synchronized in VCEM.
Synchronize VC Domain USE901JS1X_vc_domain in VCEM...[ACTION]
ISSUE: VCEM may be out of sync with the VC Domain.
RESOLUTION: The VC Domain will be checked and, if necessary, synchronized in VCEM.
Synchronize VC Domain USE642206V_vc_domain in VCEM...[ACTION]
ISSUE: VCEM may be out of sync with the VC Domain.
RESOLUTION: The VC Domain will be checked and, if necessary, synchronized in VCEM.
Analysis summary:
4 checks performed 4 actions needed
0 actions require input
**** Execution: Domain synchronization ****
**** Section 2 of 5, phase 2 of 2 ****
Synchronizing VC Domain mxsync_domain_A ...
Synchronize VC Domain mxsync_domain_A in VCEM...[OK]
Synchronizing VC Domain mxsync_domain_B ...
Synchronize VC Domain mxsync_domain_B in VCEM...[OK]
Synchronizing VC Domain USE901JS1X_vc_domain ...
Synchronize VC Domain USE901JS1X_vc_domain in VCEM...[OK]
Synchronizing VC Domain USE642206V_vc_domain ...
Synchronize VC Domain USE642206V_vc_domain in VCEM...[OK]
Execution summary:
4 actions performed 0 advisories
0 errors
>>> Please press [ENTER] to continue: