OMW/SiS - How to avoid duplicates nodes in OMW coming from SiteScope

  • Document ID:KM01036989
  • Creation Date:14-Jul-2014
  • Modified Date:14-Jul-2014
    • Micro Focus Products:
      operations manager for windows 9.00

Summary

Sometimes there are requirements to have nodes with duplicated entries in the DNS. In these cases, with an integration between OMW (Operations Manager for Windows) and SiS (SiteScope), it might be that the OMW node tree is populated with duplicated nodes coming from the SiS discovery policy

Question

Sometimes there are requirements to have nodes with duplicated entries in the DNS as shown in the example below for the node called server00:

C:\> nslookup server00
Server:  ad01.one.domain.com
Address:  10.216.128.62
Name:  server00.one.domain.com
Address:  10.216.131.45

C:\> nslookup server00.one.domain.com
Server:  ad01.one.domain.com
Address:  10.216.128.62
Name:  server00.one.domain.com
Address:  10.216.131.45

C:\> nslookup server00.two.domain.com
Server:  ad01.one.domain.com
Address:  10.216.128.62
Name:  server00.two.domain.com
Address:  10.216.131.45

In these cases, with an integration between OMW (Operations Manager for Windows) and SiS (SiteScope), it might be that the OMW node tree is populated with duplicated nodes coming from the SiS discovery policy

Answer

The following procedure has to be applied on the SiteScope server in order to avoid duplicated nodes in the OMW node tree:

  1. Delete all the duplicates nodes from the OMW node tree
  2. Stop the SiteScope service
  3. Backup the groups and persistency folders:
    • C:\SiteScope\groups
    • C:\SiteScope\persistency
  4. Put the _disableHostDNSResolution variable to true in C:\SiteScope\groups\master.config 
    • _disableHostDNSResolution=true
  5. Clean the SiteScope DNS resolution cache
    • Go to the C:\SiteScope\bin folder and launch the PersistencyViewer.bat
    • Click on “Select Persistency path” and fill it with the path to the SiteScope Persistency folder (usually the default one is C:\SiteScope\persistency)
    • In the “Filter by Type” menu search for the following type, select it and delete it:
      • com.mercury.sitescope.platform.configmanager.remotes.dns.HostResolutionLicenseStorage
    • Do the same with the HostResolutionStringStorage property
      • com.mercury.sitescope.platform.configmanager.remotes.dns.HostResolutionStringStorage
    • Close PersistencyViewer and go ahead with the next steps
  6. Start the SiteScope service
  7. Restart the SiteScope service once more
  8. Make sure you modified the “Remote Servers” in your SiteScope UI to have the desired FQDN with the correct domain
  9. Run the following commands on the SiteScope server in order to clean the agtrep cache:
    • ovc -stop agtrep
    • Open the %OvDataDir%\datafiles folder
    • Delete the following files:
      • agtrep.xml
      • agtrep.md
    • Open the %OvDataDir%\tmp\agtrep folder
    • Delete all its content
    • Run the following commands
      • ovc -start agtrep
      • ovagtrep -clearAll
      • ovagtrep -run "SiteScope_Hosts_Discovery"
      • ovagtrep -publish