Migrate Maps to Traffic Policy

Traffic Policies provide a unified way to configure all physical out‑of‑band maps (Flow Map, Fabric Map, App Intelligence solutions) through a single User Interface.

You can migrate existing Flow Maps, Fabric Maps, and App Intelligence solutions into Traffic Policies without recreating them manually. After migration, a given configuration exists as a Traffic Policy map. The underlying device configuration is not modified during migration; traffic forwarding continues to work as it is until you change the configuration using Traffic Policies.

Dry Run before Migration

Dry Run lets you validate whether a selected Traffic Intelligence , Application Intelligence or Subscriber Intelligence solutions can be migrated successfully

Note:  Running a Dry Run in Traffic Policy does not migrate or change your existing configuration. It only reports, for each map, whether migration would succeed or fail and the reason for failure.

When you start a dry run for Traffic Intelligence , Application Intelligence or Subscriber Intelligence pages, you can choose:

■   Dry Run All- simulate migration and record results for all records.
■   Dry Run Selected – simulate migration and record results for selected records.

After Dry Run completes, go to Traffic>Physical>Traffic Policy > View Migration Results and review the run:

o   Ensure the Status is Completed.
o   Check that the Failed and Skipped counts are 0, or that any skipped entries are acceptable.
o   If there are failures, use the failure details shown in the Migration Result to correct configuration or data issues, or contact Gigamon Support with the Migration Result information.

We recommend running a Dry Run before performing an actual migration. This helps detect configuration issues in advance and increases confidence that the migration will succeed. This approach helps you avoid migration failures and unexpected errors during the actual migration.

Note:  After migration, the selected maps are represented as Traffic Policies and can no longer be viewed or edited from the legacy Flow Maps, Fabric Maps, or Application Intelligence pages. If multiple maps share the same alias across clusters (Flow Map vs Flow Map) or between Flow Maps and Fabric Maps, the migrated Traffic Policy alias is adjusted by prefixing ClusterId_CL_ to make it unique. If there is a collision between a migrated Flow Map, Fabric Map, or Application Intelligence item and an existing Traffic Policy alias, the migrated Traffic Policy alias is adjusted by appending _TF_xxx. If the final alias would exceed the supported length, that map is not migrated and appears under Failed in View Migration Results, with the reason shown in the details.

Migrating Traffic Intelligence and Subscriber Intelligence Solutions

Traffic Policy migration affects solution families differently:

■   Traffic Intelligence solutions(for example, GigaSMART APF, de‑duplication, masking, slicing, tunneling, NetFlow) are built on classic Flow Maps and Fabric Maps. You migrate these by migrating the underlying Flow Maps and Fabric Maps described in this section.
■   Subscriber Intelligence solutions (for example, GTP and CUPS correlation, FlowVUE, SIP/RTP correlation, 4G/5G correlation) ,if you have Fabric Maps, that use Subscriber Intelligence applications, you can migrate those Fabric Maps using the standard Fabric Map migration flow.

When you migrate Flow Maps or Fabric Maps to Traffic Policy:

■   The underlying device configuration is preserved; only the control plane representation moves to Traffic Policy. Existing Traffic Intelligence behavior continues unchanged.
■   After migration, configuration and troubleshooting must be done from the Traffic Policy page; the entries in the legacy Flow Maps and Fabric Maps pages are no longer intended for user edits
■   The corresponding entries on the legacy Flow Maps and Fabric Maps pages are treated as internal artifacts and are no longer intended for user edits.

Migrating Flow Maps

You can migrate existing Flow Map into Traffic Policies, which preserves their behavior while moving configuration and troubleshooting to the Traffic Policy page.

Note:  Before migrating Flow Maps on a device, disconnect the corresponding node or cluster in GigaVUE‑FM (Inventory > Nodes > Actions > Disconnect Node). GigaVUE‑FM still completes any in‑progress sync, but new configuration changes are not pushed while the node is disconnected.

1. Go to > Physical > flow maps.
2. Click on Migrate button and either:
o   Migrate All- migrates all records
o   Migrate Selected-migrates only the selected records.
3. Click on OK to migrate your flow maps.
4. To view the progress of the migration use the View Migration Results page:
o   Success count matches the number of maps you intended to migrate.
o   Failed count is 0.
o   Skipped entries are acceptable if they correspond to auto‑created / internal maps

After migration, reconnect the cluster/standalone so normal configuration sync resumes. The Flow Maps that were migrated will have their configuration represented in Traffic Policies.

Note:  After you migrate a Flow Map to Traffic Policy, that Flow Map no longer appears in the legacy Flow Maps list and is treated as an internal artifact. You cannot view or edit it from the legacy Flow Maps page; manage the configuration only from the Traffic Policy page

Migrating Fabric Maps

You can migrate existing Fabric Maps into Traffic Policies, which preserves their behavior while moving configuration and troubleshooting to the Traffic Policy page.

5. Go to > Physical > Orchestrated Flows > Fabric Maps.
6. Click on Migrate button and either:
o   Migrate All- migrates all records
o   Migrate Selected-migrates only the selected records.
7. Click on OK to migrate your Fabric Maps.
8. To view the progress of the migration use the View Migration Results page:
o   Success count matches the number of maps you intended to migrate.
o   Failed count is 0.
o   Skipped entries are acceptable if they correspond to auto‑created / internal maps.

After the Migration your Fabric Map configuration can now only be managed via the Traffic Policy page. The migrated Fabric Map will not be editable from the Fabric Map page.

Note:  After you migrate a Fabric Map to Traffic Policy, that Fabric Map no longer appears in the legacy Fabric Maps list and is treated as an internal artifact. You cannot view or edit it from the legacy Fabric Maps page; manage the configuration only from the Traffic Policy page

Migrating Application Intelligence Solutions

Migration converts existing Application Intelligence solutions (on the old App Intel page) into unified Traffic Policies, preserving behavior but moving management to the Traffic Policy page.

To Migrate Application Intelligence solutions do the following:

1.   Go to Traffic > Solutions > Application Intelligence.
2. Select the Actions option of the session that you wish to migrate.
3. Click on Dry Run if you wish to see how the solution would be migrated before the actual migration.
4. Click on Migrate option to migrate your session to Traffic Policy
5. To view the progress of the migration use the View Migration Results page:
o   Success count matches the number of maps you intended to migrate.
o   Failed count is 0.
o   Skipped entries are acceptable if they correspond to auto‑created / internal maps
o   Check that all expected sources, App Intel applications, and destinations are present.

Note:  After you migrate a Fabric Map to Traffic Policy, that Fabric Map no longer appears in the legacy Fabric Maps list and is treated as an internal artifact. You cannot view or edit it from the legacy Fabric Maps page; manage the configuration only from the Traffic Policy page

Force rollback is not supported for Application Intelligence solutions. If you want to roll back the App Intel solution, you must contact customer support.

View Migration Results

Use the View Migration Results page to check the outcome of Dry Run and Migration actions.

1. In GigaVUE‑FM, go to Traffic > Traffic Policy.

2. Click View Migration Results.

3. In the list, locate the run by its Start Time and Map Type (Flow Map, Fabric Map, or Application Intelligence solution).

4. Verify that:

o   Success count matches the number of maps you intended to migrate.
o   Failed count is 0.
o   Skipped entries are acceptable if they correspond to auto‑created / internal maps.

You can use the filters at the top of the page to narrow the view by:

■   Map type – Show only Flow Maps, Fabric Maps, or Application Intelligence solutions.
■   Status – Show only runs that are In Progress, Completed, Failed, or Skipped.

For each successful migration, confirm that a corresponding Traffic Policy exists and that its sources, applications, and destinations match the original configuration.

Migration converts the configuration stored in GigaVUE‑FM for Flow Maps, Fabric Maps, and Application Intelligence solutions into Traffic Policies. Migrated configurations must be managed only from the Traffic Policies page. The corresponding entries in the legacy Flow Map / Fabric Map / Application Intelligence pages are treated as internal artifacts and are no longer intended for user edits.