v2.1 threshold_migrator AC Configuration

The probe can migrate specific or all the instances of a probe in the domain where it is deployed. For example, if it is deployed on a hub, it migrates the probe instances on all hubs in the domain. The threshold_migrator probe is recommended to be deployed on the hub-robot of any hub within the domain.
uimpga-ga
threshold_migrator_2.1_AC
The Threshold Migrator (threshold_migrator) probe is configured to enable standard static thresholds in probes across all hubs in a domain. Once a probe is migrated, a 
Static Alarms
 section is displayed with the probe-specific monitor threshold configurations. The Infrastructure Manager GUI is no longer available.
The probe can migrate specific or all the instances of a probe in the domain where it is deployed. For example, if it is deployed on a hub, it migrates the probe instances on all hubs in the domain. The threshold_migrator probe is recommended to be deployed on the hub-robot of any hub within the domain.
 Migration can only be done using the 2.60 or later version of the baseline_engine probe.
You can use both the IM and the Admin Console GUI if a probe is not migrated. The standard static thresholds are not available. The following diagram outlines the process to configure the threshold_migrator probe to enable standard static thresholds on supported probes.
Configuring Threshold Migrator Probe
Configuring Threshold Migrator Probe
 
Contents
 
 
 
2
 
 
Prerequisites
The probe has the following prerequisites:
  • Verify that required hardware and software is available before you configure the probe. 
  • Review the probe-specific considerations before you migrate a probe. 
How to Migrate Probes
After successful migration of a probe:
  • The probe can only be configured using Admin Console.
  • Static alarm configurations replace the probe-specific alarm configurations in the probe monitors.
  • The static message variables are also migrated.
  • The baseline_engine probe sends the alarms. You can see the name of the probe with the migrated thresholds in the generated alarms.
Consider the following before migration:
  • Once migration is started, the process cannot be stopped. The target probes must not be configured until migration is complete. Each target probe restarts once the process is complete.
  • The probe does not support rollback. A backup of the cfg file for each instance of the probe is created in the threshold _migrator installation directory for reference.
    You can review the alarm changes outlined in the 
    threshold_migrator (Threshold Migrator)
     article before starting the migration process.
 
Follow these steps
:
  1. Verify that any probes you do not want to migrate are inactive.
  2. Open the threshold_migrator probe configuration interface.
  3. Click to select the probes to be migrated in the 
    Available
     list.
    The probes that are selected for migration are moved to the 
    Selected
     list.
     You can also click the selectAll.png button to move all the probes to the 
    Selected
     list.
  4. Specify the robot name in the 
    Migrate on Selected Robots
     field to migrate the selected probes on specific robots. You can leave it blank to migrate the target probes on all robots in the domain.
     The robots are specified as comma-separated values in the following format:
     
    /<Domain Name>/<Hub Name>/<Robot Name>
     
     
  5. Save the selection.
  6. Click 
    Migrate Selected Probes
     button from the 
    Actions
     menu to start the migration process.
    A message is displayed that the migration for the selected probes has successfully started.
  7. Verify the migration status of the probe.
    Refer 
    Verifying Migration Status
     for more information.
The process does not complete if the system fails. The target probe reverts to its initial state.
Example: The robot with the target probe is deactivated during migration.
Verify Migration Status
This section describes the process to view the target probe migration status using threshold_migrator. The probe only displays the status of the last migration request.
 
Follow these steps:
 
  1. Open the threshold_migrator probe configuration interface.
  2. Click 
    Migration Status
     from the 
    Actions
     menu.
    The 
    Migration Status
     window opens.
The status of each probe is displayed in this window.
View Migration Error Details
This section describes the process to view the migration error details of target probes. The probe only displays the status for the probes that threshold_migrator was unable to migrate in the last migration request.
 
Follow these steps:
 
  1. Open the threshold_migrator probe configuration interface.
  2. Click 
    Migration Error Details
     from the 
    Actions
     menu.
    The 
    Migration Error Details
     window opens.
The details of migration errors for probes for all robots are displayed in this window.
 You can view the error details for each 
migration failed
 probe in the 
\probes\service\threshold_migrator\MigrationStatus\
<robotName>
\
<probeName>
.log
 file in the CA UIM installation directory.
Using Callbacks
You can initiate callbacks in threshold_migrator to perform the following actions:
  • Migrating and verifying migration status of probes: You can migrate and verify the migration status of all instances of one or more probes in the hub.
  • Migrating and verifying migration status of one or more probes in one or more robots.
migrate_probe
migrate_probe(probeName, robotName)
 
Parameters
 
String
probeName
The name of the probe
String
robotName
Full name of the robot.
Format: 
/
<Domain Name>
/
<Hub Name>
/
<Robot Name>
/
 
 
Description
 
Migrates the specified probe in the specified robot to standard static thresholds.
 
Example
 
migrate_probe(dirscan, /my_domain/my_hub/my_robot/)
The probe migrates the 
dirscan
 probe in the 
/my_domain/my_hub/my_robot/
 robot to standard static thresholds.
migrate_probes
migrate_probes(probeNames, robotNames)
 
Parameters
 
String
probeNames
comma-separated names of the probes
String
robotNames
comma-separated full names of the robots
Format: 
/
<Domain Name>
/
<Hub Name>
/
<Robot Name>
/
 
 
Description
 
Migrates the specified probes in the specified robots to standard static thresholds.
 
Example
 
migrate_probes(listOfProbes, listOfRobots)
The probe migrates the probes that are specified as comma-separated text in the 
listOfProbes
 in the robots that are specified as comma-separated text in the 
listOfRobots
 to standard static thresholds.
check_migration_status
check_migration_status()
 
Description
 
Verifies the migration status of all the supported probe instances that are deployed in the hub.
check_probe_migration_status
check_probe_migration_status(probeName, robotName)
 
Parameters
 
String
probeName
The name of the probe
String
robotName
Full name of the robot.
Format: 
/
<Domain Name>
/
<Hub Name>
/
<Robot Name>
/
 
 
Description
 
Verifies the migration status of the specified probe in the specified robot.
 
Example
 
check_probe_migration_status(dirscan, /my_domain/my_hub/my_robot/)
The probe verifies the migration status of the 
dirscan
 probe in the 
/my_domain/my_hub/my_robot/
 robot.
get_migration_errors
get_migration_errors()
 
Description
 
Retrieves the error details of all the supported probe instances that could not be migrated.