Migrating Customizations from a Previous Release—Prior to 12.0

Because of unique protocol requirements, you may have customized models or code in a previous release of Riverbed Modeler. Subsequent releases and updates to Modeler may contain changes to code and models that may supersede your customizations. Since process or node models from one release may not work with another release, it is important to understand what has changed so that you may successfully migrate your customizations into the new release. This workflow prescribes a useful methodology that describes the procedure for migrating customizations from a previous release.

Note: This workflow applies to Riverbed Modeler users only.

To migrate over multiple releases, i.e., from version 10.5 to version 14.0, you must perform multiple migrations. This workflow will guide you through migrating models from earlier releases up to Release 12.0. See also Migrating Customizations from a Previous Release for instructions on how to migrate models to 18.6.

Figure 1 shows the workflow described in this document.

Figure 1: Customization Migration Workflow

Customization Migration Workflow

Software Components: Migrating Customizations from a Previous Release—Prior to 14.0

This workflow only requires the standard Riverbed Modeler software. No additional modules are required. However, if you are working with specialized models, you may require additional licenses for those particular models.

Prerequisites: Migrating Customizations from a Previous Release—Prior to 14.0

This workflow assumes a certain amount of experience with Riverbed Modeler and with customizing the underlying code. To perform this workflow efficiently, you should already have an understanding of the customizations you have in your software.

Workflow Steps: Migrating Customizations from a Previous Release—Prior to 14.0

The following is a guide to the procedures you must perform for the type of customization you have. In most of the scenarios described in Step 1, you may be able to skip Steps 2 and 3. If you have modified Riverbed-created models, however, you must continue with all steps.

Step 1: Plan for Migration

Note: Before beginning this workflow, be sure to read the Release Notes for the latest Riverbed Modeler release.

To migrate smoothly from one release of Riverbed Modeler to another, it is best to start with a solid plan. This includes assembling documentation of changes and customizations you have made, and then determining what projects, scenarios, traffic, models, or code you want to use in the newest release.

Topology and Traffic Data

If you created a project by importing a topology and/or traffic data, you can simply reimport this information into a new project in the updated Riverbed Modeler release.

Model Assistant Files

If you have a model assistant file that contains object location information, you can simply use it in the updated Riverbed Modeler release.

Be careful when using model assistant files that create objects, destroy objects, or change object attributes. Attribute names, structure, and functionality may have changed in the latest version of the Riverbed model library. Therefore, model assistant files that depend on the older attribute structure may not be applied correctly. You may also discover that you no longer need a model assistant file to achieve the same modeling goals.

Note: Read the Release Notes for information on special behavior or conversion required for model assistant files from previous releases.

Automatic Device and Attribute Conversion

WARNING: If you have made changes to the underlying code, attributes, or models, automatic conversion is not sufficient to migrate the changes into the newest release.

Automatic device conversion is a way in which Riverbed Modeler can take models you created in Device Creator from the last model library release and convert them to work with the new release. To use automatic conversion, open your project in the new release and follow the prompts on the dialog box that appears.

Note: Automatic conversion is designed to work between successive releases of Riverbed Modeler and may not work correctly if you skip versions (i.e., converting from version 10.5 PL0 with 29 January 2004 models to version 11.5 PL1 with 20 December 2005 models).

Attribute conversion is done automatically for you. For example, if the location of an attribute has moved since the last release, Riverbed Modeler will automatically map and transfer the values from your existing models to the proper location in the new release.

Custom Models

If your custom models do not interact with the Riverbed model library in any way—that is, you have not modified the underlying code or node models of Riverbed-created models—then conversion is simple: open your project in the new release.

If you have models that have customizations to the code underlying Riverbed-created models, continue to the next step in this workflow.

Step 2: Determine the Differences

Although reading the Release Notes for the latest version of Riverbed Modeler is a good place to start, the Release Notes do not describe line-by-line changes in attributes and models. To get a better understanding of what has changed and how you need to modify your own customizations, you must find the differences between file versions for each file you have modified.

Figure 2 illustrates the models between which you must determine the differences. Both an older and newer version of the Riverbed model exist. If you have modified a Riverbed model in a previous release, you must migrate those changes to the new Riverbed model. Therefore, you must find the difference between the Riverbed model in the previous version and your custom model. Then you must find the difference between the models in the previous Riverbed Modeler release and the new release.

Figure 2: Determining the Differences

Determining the Differences

Working from a list of the files you have modified in the previous release, perform the following procedures as appropriate.

If you have a modified packet format or ICI format, use Procedure 1.

Procedure 1: Find the Difference for Packet Format (pk.m) or ICI Format (ic.m)

  1. Generate a file for the original Riverbed model.
    • 1.1 Open the original model from the previous Riverbed Modeler release.
    • 1.2 Choose File > Generate Text Report.
    • 1.3 Save the report.
  2. Generate a file for the model that contains your modifications.
    • 2.1 Open the model from the previous Riverbed Modeler release.
    • 2.2 Choose File > Generate Text Report.
    • 2.3 Save the report.
  3. Generate a file for the Riverbed model from the new release.
    • 3.1 Open the model file.
    • 3.2 Choose File > Generate Text Report.
    • 3.3 Save the report.
  4. Find the difference between the file you generated in step 1 and the file you generated in step 2 by using the UNIX diff command, Microsoft’s Windiff, or another file comparison utility. You can refer to this difference as Δ1.
  5. Find the difference between the file you generated in step 1 and the file you generated in step 3. You can refer to this difference as Δ2.
  6. Do this for each file of these types for which you have created customizations.

If you have modified a process model or node model, use Procedure 2.

Note: This procedure is not applicable to process models that have specialized licenses. The only method of comparison for such models is to generate pr.c files and compare them.

Procedure 2: Find the Difference for Process Model (pr.m) or Node Model (nd.m)

  1. Generate a file for the original Riverbed model.
    • 1.1 Open the original model from the previous Riverbed Modeler release.
    • 1.2 Choose File > Generate XML Code.
    • 1.3 Save the XML file.
  2. Generate a file for the modified model.
    • 2.1 Open the model from the previous Riverbed Modeler release.
    • 2.2 Choose File > Generate XML Code.
    • 2.3 Save the XML file.
  3. Generate a file for the Riverbed model from the new release.
    • 3.1 Open the model file.
    • 3.2 Choose File > Generate XML Code.
    • 3.3 Save the XML file.
  4. Find the difference between the file you generated in step 1 and the file you generated in step 2 by using the UNIX diff command, Microsoft’s Windiff, or another file comparison utility. You can refer to this difference as Δ1.
  5. Find the difference between the file you generated in step 1 and the file you generated in step 3. You can refer to this difference as Δ2.
  6. Do this for each file of these types for which you have created customizations.

If you have a custom ex.c or .h file, these files are already suitable for comparison. Therefore, you do not have to generate a text report or XML code file. To find the differences between the files, use Procedure 3

Procedure 3: Find the Difference for ex.c or .h Files

  1. Find the difference between the original model from the previous Riverbed Modeler release and your custom model from the previous Riverbed Modeler release by using the UNIX diff command, Microsoft’s Windiff, or another file comparison utility. You can refer to this difference as Δ1.
  2. Find the difference between the original model from the previous Riverbed Modeler release and the model from the new release. You can refer to this difference as Δ2.
  3. Do this for each file of these types for which you have created customizations.

If you have custom link models or custom demand models, you must manually compare the models to find the differences. Use Procedure 4 to determine the differences.

Procedure 4: Find the Difference for a Link or Demand Model

  1. Find the first difference.
    • 1.1 Open the original link or demand model from the previous Riverbed Modeler release and your custom link or demand model from the previous Riverbed Modeler release.
    • 1.2 Compare the two models and note the differences. You can refer to these differences as Δ1.
  2. Find the second difference.
    • 2.1 Open the original link or demand model from the previous Modeler release and the link or demand model from the new release.
    • 2.2 Compare the two models and note the differences. You can refer to these differences as Δ2.
  3. Do this for each file of these types for which you have created customizations.

Step 3: Migrate Customizations

After you have determined the differences between your old models and the models in the new release, you can begin the migration process.

Procedure 5: Migrate Customizations

  1. To save work, use the following decision path before making the changes.
    • If Δ1 < Δ2, then bring Δ1 into the file in the newest Riverbed Modeler release, shown in the following figure.

      Figure 3: Δ1 < Δ2 Scenario

      Δ1 < Δ2 Scenario

      Note: Although this procedure is meant to be a guide for decision-making and merging of code and model customizations, always consider modifications carefully, examining and merging the modifications into your new model.

    • If Δ1 > Δ2, then bring Δ2 into the customized model, shown in the following figure.

      Figure 4: Δ1 > Δ2 Scenario

      Δ1 > Δ2 Scenario

  2. For each custom model, make the changes as decided upon in step 1.
  3. Save your new custom models.
  4. Recompile all of the modified model code before attempting to run a discrete event simulation in the new release.

Step 4: Validate Changes

After migrating your customizations, validate the changes you have made by comparing the results from a discrete event simulation on the previous version of Riverbed Modeler and on the new version. Ensure that the results are similar and do not produce serious errors. Troubleshoot your changes as necessary to debug the code changes.

END OF WORKFLOW

本站文档由 北京智网畅联科技有限公司 整理、翻译并提供 · Documentation compiled and provided by Beijing ZNetLink Technology Co., Ltd.

交流群 · QQ Group:OPNET/智网妙算网络仿真交流群(群号 486383494)

原文档 © 2017 Riverbed Technology · 本站为公益翻译,由 AI 辅助完成,请仔细甄别

Original documentation © 2017 Riverbed Technology. Community translation, AI-assisted. Contact: jiazequn@znetlink.com