Duplicate devices when using the Modeling Gateway to move models to a new SpectroSERVER
search cancel

Duplicate devices when using the Modeling Gateway to move models to a new SpectroSERVER

book

Article ID: 442237

calendar_today

Updated On:

Products

Network Observability Spectrum

Issue/Introduction

I have added expansion SpectroSERVERs (SS's) to my environment and am ready to use modeling gateway to spread the load to the new SS's.

When I copy to the new SS, it does not retain the global collections (specifically the Default domain). If the others are dynamic then the global collection definition should update the devices but Default Domain is not dynamic.

If I set "export_global_collections = "true"" in exportconfiguration will that add global collections to the device for only the devices I am exporting (based on root container), It seems it does when I test this but I also end up with duplicate devices in the global collection and have to manually remove. Is that normal.

I also see if a device is down or in an "AGENT LOST" state, the devices moves over but stays blue (I assume not initialized). Does this mean I can not move devices unless they have full SNMP connectivity.

You experience duplicate device models when you use the Modeling Gateway (MGW) to migrate or balance loads between SpectroSERVERs. Additionally, you notice that newly imported devices remain in a "Blue" (Initial Condition) state and do not immediately transition to a monitored status.

Environment

  • DX NetOps Spectrum
  • Modeling Gateway

Cause

Duplicates occur when you set both export_containers and export_global_collections to "true" within the same Modeling Gateway export cycle. When you export a container, Spectrum includes the member devices. If those same devices are also members of a Global Collection being exported, the Modeling Gateway imports them multiple times, leading to duplicates.

The "Blue" state indicates that the model is successfully initialized in the database, but the SpectroSERVER has not yet established contact via SNMP or ICMP. This is expected behavior for devices that are down or have no connectivity to the new SpectroSERVER.

Resolution

To prevent duplicate models, you must perform the Modeling Gateway export and import in two separate layers:

  1. Navigate to the Modeling Gateway resource file located at $SPECROOT/SS-Tools/.modelinggatewayresource.xml.
  2. Layer 1 (Containers): Modify the ExportConfiguration parameters to export containers and devices only.
    • Set export_containers = "true"
    • Set export_global_collections = "false"
  3. Run the export and import process.
  4. Layer 2 (Global Collections): Modify the configuration to export only the Global Collection memberships.
    • Set export_containers = "false"
    • Set export_global_collections = "true"
  5. Run the export and import process again.

Regarding the "Blue" state models, you must verify that the new SpectroSERVER has network connectivity to the devices. Once the SpectroSERVER successfully polls the device via SNMP or ICMP, the model transitions from Blue to its correct status (e.g., Green/Normal or Red/Critical). If a device is intentionally down or unreachable, it remains Blue until contact is established.

Additional Information

See the Modeling Gateway Toolkit documentation topic for additional details