Migrating multiple NSP Flow Collectors

Configuration consistency check

Before you attempt to migrate multiple NSP Flow Collector instances to an NSP cluster, you must check for inconsistencies among the Flow Collector configurations.

Note: The configuration of each Flow Collector operating in the same mode, AA or SYS, must be identical.

A Flow Collector migration fails if configuration inconsistencies are encountered. As described in To migrate Release 22.9 or later NSP Flow Collectors and Flow Collector Controllers to an NSP cluster, you can do one of the following to ensure that a subsequent upgrade attempt succeeds.

• Resolve the inconsistencies using the Flow Collector web UI, or by editing a configuration file.

• Force the upgrade to ignore the inconsistencies and use an approved configuration.

The following output example is for three Flow Collectors represented as collectorA, collectorB, and collectorC:

Note: The conflicting parameter values are ordered to match the Flow Collectors named in the comparison header; for example, ‘true’ in the collectorA - collectorB comparison is in the collectorA configuration.

Differences between dld/cfg_collectorA - dld/cfg_collectorB:

  AaCfdAggregationPolicy.json:
    filters/aa/sub-type={}:
      filters/aa/sub-type=SUBD:
        sub-type:
          0:
            enabled:
            - true
            - false

Differences between dld/cfg_collectorA - dld/cfg_collectorC:

  AaCfdAggregationPolicy.json:
    policies/agg-interval={}:
      policies/agg-interval=TCP_PERF_SS_BUS:
        agg-interval:
          0:
            duration:
            - '15'
            - '20'
    policies/aggregation={},{}:
      policies/aggregation=TCP_PERF_SS_RES,AGG_RES_RAW:
        aggregation:
          0:
            enabled:
            - false
            - true

Differences between dld/collectorB - dld/cfg_collectorC:

  AaCfdAggregationPolicy.json:
    filters/aa/sub-type={}:
      filters/aa/sub-type=SUBD:
        sub-type:
          0:
            enabled:
            - false
            - true
    policies/agg-interval={}:
      policies/agg-interval=TCP_PERF_SS_BUS:
        agg-interval:
          0:
            duration:
            - '15'
            - '20'
    policies/aggregation={},{}:
      policies/aggregation=TCP_PERF_SS_RES,AGG_RES_RAW:
        aggregation:
          0:
            enabled:
            - false
            - true

AA policies to verify

The following are the AA policies and settings to check for inconsistencies. It is recommended that you verify and resolve inconsistencies using the Flow Collector web UI, if applicable; however, you can also edit the values in the associated configuration file.

Note: The extension of a configuration file is one of the following:

• Release 22.11 and earlier—xml

• Release 23.4 and later—json

• Web UI tab: Aggregation Policy | Configuration file: AaCfdAggregationPolicy.extension

  • Aggregation Intervals Panel—Aggregation Interval values

  • Aggregation Policy—aggregation for each data type

  • AA Sub Type Filter, Subscriber Collection panel—classes with aggregation enabled

• Web UI tab: Results Persistence | Configuration file: CfdResultsPersistencePolicy.extension

  • AA Data Export Policy settings

• Configuration file: CfdSubnetSummPolicy.csv

  • AA Subnet Summarization Policy—default values line that begins with an asterisk (*), such as *,32,32,128,128,...

SYS policies to verify

The following are the SYS policies and settings to check for inconsistencies. It is recommended that you verify and resolve inconsistencies using the Flow Collector web UI; however, you can also edit the values in the associated configuration file.

• Web UI tab: Aggregation Policy | Configuration file: SysCfdAggregationPolicy.extension

  • Aggregation Interval Policy—Aggregation Interval values

  • Aggregation Policy—aggregation for each data type