How to migrate SNMPv3 profiles from one Spectrum environment to another
search cancel

How to migrate SNMPv3 profiles from one Spectrum environment to another

book

Article ID: 121555

calendar_today

Updated On:

Products

Spectrum Network Observability

Issue/Introduction

We have a Spectrum environment where we have many SNMPv3 profiles created. We need to duplicate these SNMPv3 profiles to another Spectrum environment that is totally separate from the one where they currently exist.

Creating them manually in the other environment will take some time.

Is there a way to migrate these SNMPv3 profiles from one environment to another en mass?

Environment

Version: Any
Component: SpectroSERVER database

Resolution

The Modeling Gateway Toolkit can be used to export the SNMPv3 profiles to a formatted file on the one system and then import them on the other system.

To export the SNMPv3 profiles using the Modeling Gateway Toolkit:

  • Log into the SpectroSERVER system as the user that owns the Spectrum installation
  • If installed on Windows, start a bash shell by running "bash -login"
  • cd to the $SPECROOT/SS-Tools directory
  • Make a backup of the .modelinggatewayresource.xml file
  • Edit the .modelinggatewayresource.xml file
  • Find the <ExportConfiguration section as seen below:

<ExportConfiguration

        export_devices           = "true"
        export_containers        = "true"
        export_port_attributes   = "true"
        export_links             = "true"
        export_topology_layout   = "true"
        export_annotation        = "true"
        export_WA_Link_models    = "true"
        export_spectrum_settings = "true"
        export_user_models       = "true"
        export_service_modeling  = "true"
        export_schedules         = "true"
        export_global_collections = "true"
        export_discovery_configs = "true"
        export_from_primary_ss_only = "false"
        export_policy_manager = "true"
        export_fanout = "true"
/>

  • Set all of the above parameters to false except the export_spectrum_settings parameter as seen below:

<ExportConfiguration

        export_devices           = "false"
        export_containers        = "false"
        export_port_attributes   = "false"
        export_links             = "false"
        export_topology_layout   = "false"
        export_annotation        = "false"
        export_WA_Link_models    = "false"
        export_spectrum_settings = "true"
        export_user_models       = "false"
        export_service_modeling  = "false"
        export_schedules         = "false"
        export_global_collections = "false"
        export_discovery_configs = "false"
        export_from_primary_ss_only = "false"
        export_policy_manager = "false"
        export_fanout = "false"
/>

  • Save the changes
  • Run the Modeling Gateway export

The following is the usage for running modelinggateway:

Usage:

modelinggateway -vnm <vnm_name> [-user <SS user>] [-i <importfile>/{<importfile1>,<importfile2>...} | [ -cmdb ] -e <exportfile>] [-o <outputfile>] [-debug <debugfile>]

Using the above usage statement, if the hostname of the SpectroSERVER system is OLD_SPECTRUM, then the export command would look like the following:

./modelinggateway -vnm OLD_SPECTRUM -e SNMPv3_profiles

In the above example, the "-e SNMPv3_profiles" means to export to a file named "SNMPv3_profiles.xml". Modeling Gateway will automatically ad ".xml" to the end of the file.

To import the SNMPv3 profiles using the Modeling Gateway Toolkit:

  • Copy the export file from the one machine to the other. Please the file into the $SPECROOT/SS-Tools directory
  • Log into the SpectroSERVER system as the user that owns the Spectrum installation
  • If installed on Windows, start a bash shell by running "bash -login"
  • cd to the $SPECROOT/SS-Tools directory
  • Using the above Modeling Gateway export example, if the hostname of this SpectroSERVER system is NEW_SPECTRUM, then use the following command to import the SNMPv3_profiles.xml file:

./modelinggateway -vnm NEW_SPECTRUM -i SNMPv3_profiles

NOTE: The SpectroSERVER must be running when running a Modeling Gateway export and import.

NOTE: In a Distributed SpectroSERVER environment, the Modeling Gateway export and import should be run on the Main Location Server (MLS) systems. SNMPv3 profiles are Global models so after the import on the MLS system, they will automatically be propagated to the other Primary SpectroSERVER systems in the environment.

NOTE: In a Fault Tolerant environment, the next time an Online Backup is run on a Primary SpectroSERVER, the sync of the SpectroSERVER database to the Secondary SpectroSERVER will load the SNMPv3 profiles.

Additional Information

The "export_spectrum_settings=true" in the .modelinggatewayresource.xml exports information from the following models:

  • VNM
  • PolicyManager
  • LostFound
  • GlobaConfig
  • TopologyWrkSpc
  • FaultIsolation
  • LivePipes
  • AlarmMgmt

If you examine the export xml file, you will see the SNMPv3 profiles are exported in the GlobaConfig section. The following is an example:

  <Model name="" model_type="GlobalConfig" model_handle="0x1000013"
         SNMPv3Profiles="5.a.cf.3b.cd.a3.9f.3d.ca.6d.2e.59.69.9d.8a.21.89.4e.97.96.3f.ff.57.94.5e.12.7f.37.fb.c0.64.e0.bd.c6.c4.5f.3f.55.3d.2e.d.d7.c.81.27.e4.e6.44.55.c4.70.86.88.34.cc.30.f1.2.fa.d7.b3.5a.a4.ec.ce.a1.31.a4.91.42.58.68.ef.1e.60.25.6.65.50.b2.14.92.4d.45.79.51.66.94.b6.70.45.54.9d.44.9e.8a.2b.65.96.4f.8a.86.2f.e2.6b.e8.32.bb.c1.db.ce.fd.5f.35.89.a5.28.8b.38.52.d7.10.58.1a.6a.18.46.f6.e5.c9.8f.6a.81.68.96.37.d2.ee.8d.b2.16.e.b4.ce.b1.c.fd.93.4.9.d9.86.44.59.5b.9.75.78.89.bc.d2.5f.ac.4b.7.89.66.fe.93.3b.54.24.1.e6.e4.7c.32.68.e6.b3.a7.ed.6f.70.e4.2d.60.5d.5b.34.fa.66.36.37.14.6e.51.4f.7d.dd.6c.9.e8.19.c3.2f.7.5f.44.c6.e3.a.f8.b9.2a.99.cd.e.44.b4.3f.83.6c.67.c4.f1.ab.c.e4.bb.a5.b.a4.8c.89.c6.1b.eb.95.10.7c.64.ee.f8.2e.35.be.d3.1a.2c.ef.71.cb.c1.3b.f4.64.3f.65.25.92.76.2c.59.94.31.9c.4c.d9.a4.5a.8b.f1.7b.c6.8f.1e.2d.65.82.9b.40.ad.24.b0.ef.66.68.89.3b.14.27.7d.61.d9.4c.56.57.97.bf.d1.15.3d.d8"

Please reference the "Modeling Gateway" section of the documentation for more information.

Powered by Wolken Software