OMW Support Tip: How to troubleshoot Topology Synchronization in OMW
Topology Synchronization in OMW fails or not all the CIs are being forwarded. Here are somethings to look at when this occurs.
1. On Source server:
a. run the following commands from the command line:
wmic /namespace:\\root\hewlettpackard\openview\data path OV_StartPoint CALL ExportInstances ClassNameList="OV_ManagedNode OV_ExternalNode OV_NodeGroup OV_NodeGroupMember OV_VirtualHostedOn OV_Service OV_ServiceComposition OV_ServiceDependency" FilePath="%OvDataDir%\tmp\modelsync.xml"
wmic /namespace:\\root\hewlettpackard\openview\data path OV_StartPoint CALL ExportInstances ClassNameList="OV_ServiceTypeDefinition OV_ServiceTypeComponent OV_ServiceTypeDependency" FilePath="wmic /namespace:\\root\hewlettpackard\openview\data path OV_StartPoint CALL ExportInstances ClassNameList="OV_ServiceTypeDefinition OV_ServiceTypeComponent OV_ServiceTypeDependency" FilePath="%OvDataDir%\tmp\stdsync.xml"
b. Gather the following files:
These 2 files show what is information is being sent to the target server.
2. On the target server
a. Enable data dump by running the following
1. In the console tree, right-click Operations Manager, and then click Configure Server.... The Server Configuration dialog box opens.
2. Set the value of Dump mapping data to true.
3. Click OK to save your changes and close the Server Configuration dialog box.
4. Restart the OvAutoDiscovery Server process for your changes to take effect.
b. Then on the source server run the topology Synch tool again
OMW Console->Tools->HP Operations Manager Tools->Synchonize Topology
c. In the %OvShareDir%\Server\tmp\discovery gather the following information in the directories:
The directory contains the following subdirectories:
Creation_pre-enrichtment and Deletion_pre-enrichment
Contains the synchronization data after the CI data structure has been normalized. The data reflects what has been loaded from the source management server.
Creation_post-enrichment and Deletion_post-enrichment
Contains the synchronization data after the mapping rules have been executed on the normalized data.
Compare these 2 files to see if the Synchonization was sucessful or not.
3. There are a couple of log files that we can look at to see if Synchonization is failing:
Make sure that the service discovery logging is set to 10 in the OMW UI under the server config\service discovery name space, this will give us the most information.
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.