Upgrading Models

Database Compatibility After Upgrade
To ensure compatibility between the
database and a new version of
after upgrading, complete these tasks:
These procedures are not required for first-time installations.
If you do not run appropriate upgrade scripts after a
upgrade, system problems can occur.
In some cases, a model type can change, depending on vendor requirements or added functionality in
. In other cases,
no longer supports a device with a unique model type; therefore, convert these models to an alternative model type.
Contact a support representative if you have questions about the model conversion process or any errors you encounter during conversion.
If you plan to set up a distributed
configuration, convert all models before partitioning the database.
Preserved Model Attributes and Elements
The following model attributes are preserved when you use the listed scripts to upgrade the
  • 0x1006e Model_Name
  • 0x12d7f Network_Address
  • 0x10024 Community_Name
  • 0x10009 Security_String
  • 0x11564 Notes (Notes are preserved for the device, interface, application, module, and port models.)
  • 0x10071 Polling_Interval
  • 0x10072 Poll_Log_Ratio
  • 0x1154f Polling Status
  • 0x110c4 Time Out
  • 0x110c5 Try Count
  • 0x1000c Value_When_Yellow
  • 0x1000d Value_When_Orange
  • 0x1000e Value_When_Red
The following details are also preserved:
  • Inter-model relations, including device connectivity
  • Connections to both physical and logical interfaces on all devices
  • Model type-specific and model-specific NCM configurations
During remodeling, interfaces and applications are rediscovered and modeled. This remodeling results in new model handles for these child models.
Watches are not preserved during the model and model type conversion and must be rebuilt on the new model type.
Model Type Editor and the Customized
If you customized your
database using the Model Type Editor (MTE), make a record of all changes. Certain changes that are made with the MTE are not preserved when the
database is upgraded to a later version of
If you changed relations, meta-rules, or attributes of
-supplied or other developer-supplied model types, those changes could be unrecognized during the database upgrade. Reapply the changes manually after you upgrade
Model types can be changed and improved in the upgraded version of
. For the new release of
to operate correctly, these changes might need to overwrite customized values.
For more information about preserving database changes and the type of changes that can be preserved, see the .
Using the Multicast Manager or VPN Manager After Installing a Patch or Upgrade
The NewMM.pl post-installation script affects the following model types:
  • Rtr_Cisco
  • Cisco_12000
  • SwCat6xxx, SwCat35xx, and SwCat4xxx
Rerun Multicast and/or VPN discovery and reapply customizations after you run the post-installation scripts. This process helps ensure the correct modeling and management of the newly created device models within your environment.
Convert Existing Models to Newly-Supported Model Types
Use the NewMM.pl post-installation script to convert the existing models of various model types to the newly supported model types. This script preserves many key attributes, relationships, and other elements.
For example, you previously modeled Cisco Catalyst 4500 devices as GnSNMPDev in
. These models can be converted to use the Catalyst 4500 Certification functionality.
In addition, you can use the NewMM.pl script to convert various Cisco-specific model types to the appropriate supported model type. As Cisco introduces new devices,
adds support for these new devices using the appropriate model type available.
If you update model types using the NewMM.pl script, a set of models is created in the Reporting Database with a new model type. Models with the previous model type are marked as destroyed. In addition, data is not migrated from the old model type to the new type.
Follow these steps:
  1. Verify that the
    is running.
  2. Run the following command from the
    /Install-Tools/PostInstall/ directory:
    On Windows, all necessary scripts must be run from a bash shell. They do not run as expected from a DOS command prompt.
  3. Enter the host name or IP address of the VNM and press Enter.
  4. Enter the
    landscape handle when prompted, and press Enter.
    The script analyzes the database to determine which models are eligible for conversion, if any. The script provides a complete list of models that correspond to each new model type before prompted for conversion.
    Models that are in maintenance or hibernation mode or that cannot be contacted are not candidates for conversion.
  5. When prompted to convert eligible models of a specific model type, enter Yes. If you do not want to convert specific model types, enter No. The following log file is created in the
    /Install-Tools/PostInstall/ directory:
  6. To confirm the model conversion, verify the following log file:
    Existing models are converted to the newly supported model types.