During this section, the restored ID-VSE database will be updated to reflect the changes made to the VCEM database. In the first phase of this section, the mxsync tool will analyze each logical server definition to ensure the underlying VCEM profile exists and the network, storage and bay assignment configuration data stored in the ID-VSE database is consistent. The restored logical server definition can be out-of-date if, for example, as a post-backup activity, the logical server was deactivated.
For the sample run, the changes recommended by mxsync during phase 1 of section 3 are summarized in Table 13.
Table 13. Summary of mxsync Logical Server Management phase 1 actions.
Post-backup Activity Pre-mxsync State
Standby HP IO service S1_VC_Test.
The state of the logical server is activated in the restored ID-VSE database, but the profile is unassigned in the updated VCEM database.
Changed the state of the logical server to deactivated in the ID-VSE database.
Note: It is possible that the profile might not exist in the updated VCEM
database. In this case the logical server would be placed in a pre-activated, new state.
Activate logical server LS2_VC_Test.
Resume HP IO service S2_VC_Test.
The state of the logical server is deactivated in the restored ID-VSE database, but the profile is assigned in the updated VCEM database.
Changed the state of the logical server to activated in the ID-VSE database.
Create logical server LS3_VC_Test.
Create HP IO service S3_VC_Test.
The logical server definition does not exist in 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 state of the logical server is activated or deactivated in the restored ID-VSE database, but the profile does not exist in the updated VCEM database.
Change the state of the logical server to a pre-activated, new state.
Note: It is possible that the profile might exist in the updated VCEM database.
In this case the logical server would be placed in a deactivated state.
+---+
| Section 3 of 5 |
| Logical Server Management | +---+
Synchronize the logical server and storage pool entry definitions in the Insight Dynamics - VSE (ID-VSE) database with the changes made to the VCEM databases.
**** Analysis: Synchronize logical server definitions with VCEM. ****
**** Section 3 of 5, phase 1 of 3 ****
Analyzing each logical server definition to ensure the underlying VCEM profile exists and the network, storage and bay assignment configuration data stored in the ID-VSE database is current. The restored logical server definition can be out-of-date if, for example, as a post-backup activity, a logical server was modified to add or remove a network or storage entry.
Establishing connections and gathering information to perform the analysis.
This may take a few minutes...
Checking logical server LS1_VC_Test...[ACTION]
ISSUE: The state of the logical server LS1_VC_Test (active) is inconsistent with the state of the underlying VCEM profile vsels_LS1_VC_Test (unassigned).
RESOLUTION: Update the definition of logical server LS1_VC_Test in the Insight Dynamics database to reflect the deactivated state.
Checking logical server LS2_VC_Test...[ACTION]
ISSUE: The state of the logical server vsels_LS2_VC_Test (inactive) is inconsistent with the state of the underlying VCEM profile LS2_VC_Test (assigned).
RESOLUTION: Update the definition of logical server LS2_VC_Test in the Insight Dynamics database to reflect the activated state.
Checking logical server LS4_VC_Test...[ACTION]
ISSUE: The VCEM profile vsels_LS4_VC_Test assigned to logical server LS4_VC_Test does not exist.
RESOLUTION: Update the definition of logical server LS4_VC_Test in the Insight Dynamics database to reflect the new state.
Checking logical server S1-VC-1_ls...[ACTION]
ISSUE: The state of the logical server S1-VC-1_ls (active) is inconsistent with the state of the underlying VCEM profile S1-VC-1_1241e815059 (unassigned).
RESOLUTION: Update the definition of logical server S1-VC-1_ls in the Insight Dynamics database to reflect the
deactivated state.
Checking logical server S2-VC-1_ls...[ACTION]
ISSUE: The state of the logical server S2-VC-1_1241e8159af (inactive) is inconsistent with the state of the underlying VCEM profile S2-VC-1_ls (assigned).
RESOLUTION: Update the definition of logical server S2-VC-1_ls in the Insight Dynamics database to reflect the
activated state.
ISSUE: The VCEM profile S5-VC-1_12426f64058 assigned to logical server S5-VC-1_ls does not exist.
RESOLUTION: Update the definition of logical server S5-VC-1_ls in the Insight Dynamics database to reflect the new state.
Analysis summary:
7 checks performed 7 actions needed
0 actions require input 0 advisories
0 errors
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: Synchronize logical server definitions with VCEM. ****
**** Section 3 of 5, phase 1 of 3 ****
Updating definition of logical server LS1_VC_Test...[OK]
Retrieving blade information of bay number 15 in enclosure USE901JS1X.
Updating blade information on logical server.
Updating definition of logical server LS2_VC_Test...[OK]
Updating definition of logical server LS4_VC_Test...[OK]
Updating definition of logical server S1-VC-1_ls...[OK]
Retrieving blade information of bay number 14 in enclosure USE642206V.
Updating blade information on logical server.
Updating definition of logical server S2-VC-1_ls...[OK]
Updating definition of logical server S4-VC-1_ls...[OK]
Updating definition of logical server S5-VC-1_ls...[OK]
Execution summary:
7 actions performed 0 advisories
0 errors
>>> Please press [ENTER] to continue:
During the second phase of the Logical Server Management section, the mxsync tool will analyze each logical server definition to ensure the assigned WWN and MAC addresses are still allocated to Insight Dynamics - VSE (ID-VSE) and have not been reassigned to another VCEM profile. The latter can happen if, for example, as a post-backup activity, the logical server was deleted, the addresses freed and then reassigned to a new server. To prevent two servers from using the same address, during the execution step of this phase, the mxsync tool will delete reassigned MAC addresses from the logical server definition and, in the case of duplicate WWN address, delete the logical server definition.
For the sample run, the changes recommended by mxsync during phase 2 of section 3 are summarized in Table 14.
Table 14. Summary of mxsync Logical Server Management phase 2 actions.
Post-backup Activity Pre-mxsync State Delete HP IO service S4_VC_Test.
The state of the logical server is activated or deactivated in the restored ID-VSE database, but the profile does not exist in the updated VCEM database.
Delete the profile from the restored ID-VSE database.
Note: In all three cases, the delete recommendation is triggered because the addresses assigned to the profile have already been reallocated to a different profile in the updated VCEM database.
Lease on HP IO service S5_VC_Test expires.
The state of the logical server is activated or deactivated in the restored ID-VSE database, but the profile does not exist in the updated VCEM database.
Delete the conflicting network definition from the logical server definition in the restored ID-VSE database.
**** Analysis: Reconcile ownership of WWN and MAC addresses. ****
**** Section 3 of 5, phase 2 of 3 ****
Analyzing each logical server definition to ensure the assigned WWN and MAC addresses are still allocated to ID-VSE and have not been reassigned to another VCEM profile. The latter can happen if, for example, as a post-backup activity, the logical server was deleted, the addresses freed and then reassigned to a new server.
Establishing connections and gathering information to perform the analysis.
This may take a few minutes...
Checking logical server LS1_VC_Test...[OK]
Checking logical server LS2_VC_Test...[OK]
Checking logical server LS4_VC_Test...[ACTION]
ISSUE: The WWN address 50:06:0B:00:00:C2:62:4E has been reassigned to VCEM profile vsels_LS3_VC_Test.
RESOLUTION: Delete the definition of logical server LS4_VC_Test from the ID-VSE database.
Checking logical server S1-VC-1_ls...[OK]
Checking logical server S2-VC-1_ls...[OK]
Checking logical server S4-VC-1_ls...[ACTION]
ISSUE: The WWN address 50:06:0B:00:00:C2:62:57 has been reassigned to VCEM profile S3-VC-1_1242896729c.
RESOLUTION: Delete the definition of logical server S4-VC-1_ls from the ID-VSE database.
Checking logical server S5-VC-1_ls...[ACTION]
ISSUE: A MAC address 00-17-A4-77-00-5D has been reassigned to VCEM profile 00-17-A4-77-00-5D.
RESOLUTION: Delete network definitions of logical server S5-VC-1_ls from ID-VSE database.
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: Reconcile ownership of WWN and MAC addresses. ****
**** Section 3 of 5, phase 2 of 3 ****
Deleting definition of logical server LS4_VC_Test...[OK]
Deleting definition of logical server S4-VC-1_ls...[OK]
Deleting network definitions of logical server S5-VC-1_ls from
ID-VSE database...[OK]
Execution summary:
3 actions performed 0 advisories
0 errors
During the third phase, the mxsync tool will analyze each storage pool entry (SPE) definition to ensure the assigned WWN addresses are still allocated to ID - VSE and correctly associated with the defined VCEM profiles. The state of a WWN address can be incorrect if, for example, as a post-backup activity, the storage pool entry was deleted or a logical server was created using the pre-defined SPE.
To resolve the inconsistency, VCEM profile containing the WWN address assigned to the SPE will be imported.
For the sample run, the changes recommended by mxsync during phase 3 of section 3 are summarized in Table 15.
Table 15. Summary of mxsync Logical Server Management phase 3 actions.
Post-backup Activity Pre-mxsync State LSM Section Phase 3
mxsync Recommendation/Action LSM Section Phase 3 Create logical server
LS3_VC_Test.
Create HP IO service S3_VC_Test.
The logical server definition does not exist in the restored VCEM database.
Create logical server for VC profile.
**** Analysis: Reconcile assignment of storage pool entries (SPE). ****
**** Section 3 of 5, phase 3 of 3 ****
Analyzing each storage pool entry (SPE) definition to ensure the assigned WWN addresses are still allocated to ID-VSE and correctly associated with the defined VCEM profiles. The state of a WWN address can be incorrect if, for example, as a post-backup activity, a storage pool entry was deleted or a logical server was created using a pre-defined SPE.
Establishing connections and gathering information to perform the analysis.
This may take a few minutes...
Checking storage pool entry mxsyncTestVCDG Pool_PoolEntry_Test3...[OK]
Checking storage pool entry mxsyncTestVCDG Pool_PoolEntry_Test4 ...[OK]
Checking storage pool entry mxsyncTestVCDG Pool_PoolEntry_Test5...[OK]
Checking storage pool entry mxsyncTestVCDG Pool_PoolEntry_Test7...[OK]
Checking storage pool entry mxsyncTestVCDG Pool_PoolEntry_Test8...[OK]
Checking storage pool entry mxsyncTestVCDG Pool_PoolEntry_Test9...[OK]
Checking storage pool entry mxsyncTestVCDG Pool_PoolEntry_Test12...[ACTION]
ISSUE: The WWN address 50:06:0B:00:00:C2:62:4E assigned to storage pool entry mxsyncTestVCDG
Pool_PoolEntry_Test12 is now assigned to VCEM profile vsels_LS3_VC_Test.
RESOLUTION: To resolve the inconsistency, a new logical server definition to associate VCEM profile
vsels_LS3_VC_Test with storage pool entry
mxsyncTestVCDG Pool_PoolEntry_Test12 will be created.
Checking storage pool entry mxsyncTestVCDG Pool_PoolEntry_Test15...[ACTION]
ISSUE: The WWN address 50:06:0B:00:00:C2:62:57 assigned to storage pool entry mxsyncTestVCDG
Pool_PoolEntry_Test15 is now assigned to VCEM profile S3-VC-1_1242896729c.
RESOLUTION: To resolve the inconsistency, a new logical server definition to associate VCEM profile
S3-VC-1_1242896729c with storage pool entry
mxsyncTestVCDG Pool_PoolEntry_Test15 will be created.
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: Reconcile assignment of storage pool entries (SPE). ****
**** Section 3 of 5, phase 3 of 3 ****
Preparing LSM's inventory for import. This may take a few minutes...
Creating logical server vsels_LS3_VC_Test_ls for VCEM Profile
vsels_LS3_VC_Test...[OK]
Creating logical server S3-VC-1_1242896729c_ls for VCEM Profile
S3-VC-1_1242896729c...[OK]