Migrating core components files manually

Some files that contain configuration changes cannot be migrated automatically. Review the suggested list of files and migrate changes manually.

1. Review the $NCHOME/log/precision/NMCoreFilesForManualReview.txt log file. For example, /opt/IBM/netcool/log/precision/NMCoreFilesForManualReview.txt. This file has an entry for each item that requires attention. If an entry says that a file requires manual migration steps, you must review each file and decide how to incorporate the differences into the files on the target installation.
2. Optional: Review the NMCoreFilesMigrated.txt log file to see all files that were migrated, and which files were not migrated. It is likely that no action is needed for files that were not migrated. Some files do not need to be migrated. If you think that such a file contains important configuration information that you want to preserve, review the file. Review the $NCHOME/log/precision/NMCoreConfigFileAutoMigrationReport.txt log file for extra information about files that could not be migrated successfully.
3. For files that need manual migration, locate the appropriate versions of the files to review.
   • For files that were changed by a user, compare the original version from the source installation with the changed version from the source installation. These files are copied to the target server for convenience. The locations differ by file type and are listed out in the NMCoreFilesForManualReview.txt file.
   • For files that were changed by IBM® between versions, compare the version from the source installation with the version from the target installation.Files from the source server are copied to the target server for convenience. The locations differ by file type and are listed out in the NMCoreFilesForManualReview.txt file.
   • For files that were changed by a user and by IBM between versions, compare all three versions. Files from the source server are copied to the target server for convenience. The locations differ by file type and are listed out in the NMCoreFilesForManualReview.txt file.
4. Run the ncp_mib utility if you customized any MIBs on the source system.
   Custom MIBs from the source installation are copied into the $NCHOME/precision/mibs/ directory. MIB files moved from the GUI to the core components server in V4.2.
5. Review the DbEntityDetails.cfg file and replace &ExtraInfo with &m_ExtraInfo.
   This change is necessary due to database changes between V3.9 and V4.1 and later.
6. Review the domain-specific DbLogins.cfg files on the target installation with the new database connection details for the target installation.
   The migration scripts create domain-specific DbLogins.cfg files for each domain from the source installation.
7. Optional: If you used discovery collectors on the source installation, copy the .cfg and .drv files to the target installation and ensure the collectors are set up correctly.
8. Optional: If you created new discovery collectors on the source installation, refer to the EMS Collector Developer Guide for migration instructions.
9. If you used seed files for discovery on the source server, copy the seed files to the equivalent location on the target server. When you run a discovery, update the seed file reference in the Seed tab of the Discovery Configuration GUI.
10. If you used DNS files for discovery on the source server, copy the files to the equivalent location on the target server. When you run a discovery, update the DNS file reference in the DNS tab of the Discovery Configuration GUI.
11. Review the list of files that are not migrated in Core components file reference and decide if any customization changes need to be migrated.
12. Review the changes you made to the NcoGateInserts.DOMAIN.cfg files, which are deprecated in Network Manager 4.2, and migrate the changes:
    1. Go to the directory that is listed for the NcoGateInserts.DOMAIN.cfg entry in the $NCHOME/log/precision/NMCoreFilesForManualReview.txt file.
    2. Locate the NcoGateInserts.DOMAIN.cfg files for each domain for which you have made customizations.
    3. Locate your customizations. You only need to migrate customizations that you made yourself. All the default customizations were moved from the NcoGateInserts.cfg file to the Probe rules in Netcool/OMNIbus Knowledge Library V4.4.3.
    4. On the server where the Netcool/OMNIbus Knowledge Library is installed, locate the rules file that corresponds to the eventID of the type of events that you want to customize. For vendor-specific rules, the rules files are placed under the vendor directory, for example, include-snmptrap/cisco.
    5. Locate the appropriate rules file with the suffix user.include.rules. For example, /include-snmptrap/adtran/adtran-ADTRAN-ACTDAXL3-MIB.user.include.snmptrap.rules. Putting your customizations in a separate file makes it easier to identify and back them up later.
    6. Edit the file and locate the section that corresponds to the type of trap that you want to customize.
       For example, to override the default rules for adACTDAXL3systemHdwFailureClear trap, add the customized rules under the following section:

       case "906": ### adACTDAXL3systemHdwFailureClear

    7. Set the @NmosEventMap field using the following format: event map name.precedence value.

       For example:

       @NmosEventMap = "LinkDownIfIndex.910"

13. Optional: If you want to review the list of files that were migrated successfully, review the files listed in NCHOME/log/precision/NMCoreFilesMigrated.txt.