Preserve Customized Support Files

Contents
casp941
Contents
Preserving Customized Support Files
Some custom
support files can be overwritten when installing a new version of
. These support files include AlertMap, EventDisp, Event Format, Probable Cause, or GIB files.
For example, you can have customized event files that exist in the
<$SPECROOT
>/SG-Support/CsEvFormat directory. Before you upgrade the OneClick web server, move these files to <
$SPECROOT
>/custom/Events/CsEvFormat.
To preserve the customized files, the
installation creates a backup copy of each file. After you complete a
installation, you can review your customized files and can add them to the upgraded
version.
Follow these steps:
  1. Navigate to the <
    $SPECROOT
    >/Install-Tools/LOGS/<
    version_date
    >/SavedFiles directory after you complete a
    installation.
    This directory contains subdirectories with backups of customized files. The original versions of these customized files are overwritten during an upgrade. The two backup file formats are:
    • .sv - files that were replaced during an upgrade by new files with the same name.
    • .obs - files that are obsolete and no longer exist with the upgraded version of
      .
    The original path to a given backup file is preserved within the SavedFiles directory. This directory structure tells you where the customized file originally came from.
    For example, if you customized the Rtr_Cisco AlertMap file and then you installed a new version of
    , the following file is available:
    <$SPECROOT>/Install-Tools/LOGS/<version_date/SavedFiles/SS/CsVendor/Cisco_Router/Rtr_Cisco/Alertmap.sv
  2. Review the .sv and .obs files to determine which customizations you want to implement again.
  3. Using any overwritten files, reapply your customization changes to the newly installed files.
    For example, to reimplement the customizations in the Rtr_Cisco AlertMap file:
    1. Open the following file in a text editor:
      <$SPECROOT>/Install-Tools/LOGS/<version_date>/SavedFiles/SS/CsVendor/Cisco_Ro uter/Rtr_Cisco/AlertMap.sv
    2. Compare this file to the new Rtr_Cisco AlertMap file at:
      <$SPECROOT>/SS/CsVendor/Cisco_Router/Rtr_Cisco/AlertMap
    3. Copy and paste any needed customizations from the backed-up AlertMap file (AlertMap.sv) to the new AlertMap file.
  4. For any obsolete files, recreate a file to reimplement customizations.
    If you want to apply your customizations across model types, you can recreate customizations at the global level. You can also recreate your customizations for only the specific model type for which they were originally implemented.
    For example, the
    upgrade obsoletes your event processing information in the EventDisp file at <
    $SPECROOT
    >/SS/CsVendor/Ctron_MMAC_Pls/9G426_02/EventDisp. To reimplement your customization, follow these steps:
    1. To recreate the customizations at a model type level, create a blank text file that is called EventDisp. Save it to the <
      $SPECROOT
      >/SS/CsVendor/Ctron_MMAC_Pls/9G426_02 directory.
    2. To recreate the customizations at a global level, create a blank text file that is called EventDisp. Save it to the <
      $SPECROOT
      >/SS/CsVendor/Ctron_MMAC_Pls directory.
    3. Open the backup copy of the EventDisp file that the
      installation created during the installation process. This file is located in the <
      $SPECROOT
      >/Install-Tools/LOGS/<
      version_date
      >/SavedFiles/SS/CsVendor/Ctron_MM AC_Pls/9G426_02 directory.
    4. Locate each line of the EventDisp file that you customized.
    5. Copy each of these lines to the new, blank EventDisp file that you created.
      Copy only the lines in the EventDisp file that you customized. Do not copy the entire backed-up EventDisp file and paste it into the new EventDisp file. If the
      version that you are installing has updated processing for some of the events previously in the Cabletron MMACPlus EventDisp file but are now in a global EventDisp file, you override this new event processing.
    6. Save and close the new EventDisp file.
  5. Restart the
    SpectroSERVER
    .
    Your changes to the
    support files are applied, and your customized support files are preserved.
For more information about global or model type EventDisp and AlertMap files, see and .