v1.0 threshold_migrator AC Configuration

The threshold_migrator probe is configured to enable standard static thresholds in probe(s) in all robots in a hub. Once a probe is migrated, a Static Alarms section is displayed in the monitor threshold configuration page and the Infrastructure Manager GUI is no longer available.
uimpga-ga
threshold_migrator_1.0_AC
The threshold_migrator probe is configured to enable standard static thresholds in probe(s) in all robots in a hub. Once a probe is migrated, a
Static Alarms
section is displayed in the monitor threshold configuration page and the Infrastructure Manager GUI is no longer available.
The probe can migrate specific or all the instances of a probe in the hub where it is deployed. For example, if it is deployed on a secondary hub, it will migrate the probe instances on that hub. If threshold_migrator is deployed on the primary hub it will only migrate the probe instances for the robots attached to primary hub and will not migrate any probe instances for the secondary hubs.
Migration can only be done using the 2.50 or later version of the baseline_engine probe.
If a probe is not migrated, you can use both the IM and the Admin Console GUI is displayed.
The standard static threshold will not be available.
The following diagram outlines the process to configure the threshold_migrator probe to enable standard static thresholds on the specified probes.
Configuring Threshold Migrator Probe
Configuring Threshold Migrator Probe
How to Migrate Probes
This section describes the minimum configuration settings required to migrate a probe to standard static thresholds.
  • Once migration has been started, the process cannot be stopped and the target probes must not be configured until migration is complete. Each target probe will restart once the process is complete.
  • Rollback is not supported by the probe. However, a backup of the config file for each instance of the probe is created in the threshold _migrator installation directory for reference.
    Please review the alarm changes in baseline_engine (standard static threshold) outlined in the
    threshold_migrator (Threshold Migrator)
    document before starting the migration process. 
Follow these steps
:
  1. Open the threshold_migrator probe configuration interface.
  2. Click to select the probe(s) to be migrated in the
    Available
    list.
    The probe(s) selected for migration are moved to the
    Selected
    list.
    You can also click the selectAll.png button to move all the probe(s) to the
    Selected
    list.
  3. Save the selection.
  4. Click
    Migrate Selected Probes
     button from the
    Actions
    menu to start the migration process.
    A message is displayed that the migration for the selected probe(s) is under process.
  5. Verify the migration status of the probe.
    Refer
    Checking Migration Status
    for more information.
  • In case of system failure, such as the robot with the target probe was deactivated during migration, the process will be not complete and the probe will revert back to its initial state..
  • Once a probe has been successfully migrated:
    • The probe can only be configured using Admin Console.
    • Probe specific alarm configurations in the probe monitors will be replaced by static alarm and Time over Threshold configurations.
    • The static message variables will also be migrated.
    • The alarms will be sent by the ‘baseline_engine’ probe. However, in Alarm Console, user will still see the name of the probe for which thresholds are configured.
Checking Migration Status
This section describes the process to view the migration status of each probe.
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.
In case of failure, you can check the migration status for each 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 probe(s): 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 probe(s) in one or more robot(s).
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 name(s) of the probe(s)
String
robotNames
Comma separated full names of the robot(s)
Format: 
/
<Domain Name>
/
<Hub Name>
/
<Robot Name>
/
Description
Migrates the specified probe(s) in the specified robot(s) to standard static thresholds.
Example
migrate_probe(listOfProbes, listOfRobots)
The probe migrates the probes specified as comma separated text in the
listOfProbes
in the robots specified as comma separated text in the
listOfRobots
 to standard static thresholds.
check_migration_status
check_migration_status()
Description
Checks the migration status of all the supported probe instances 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
Checks 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 checks the migration status of the 
dirscan
 probe in the
/my_domain/my_hub/my_robot/
 robot.