Skip to main content

Configuration Removal (Object Deletion) from AI Provisioning Package after applying the 2021 R1 HF1

Botond Bajka
  • Updated

Overview

There is a known issue in Aurea Monitor Management Server (AMS) version 2021 R1 or earlier when Transport configuration removal from provisioning package (on source AI) is not provisioned to target. This issue is applicable to any configuration object, not just to the Transport configuration.

The issue has been fixed in AMS version 2021 R1 HF1 (Hotfix 1).

This article describes how configuration removal (object deletion) works after applying the 2021 R1 HF1.

 

Information

After applying 2021 R1 HF1 the provisioning of Aurea Monitor Intermediary (AI) works in the following way if you want to remove (delete) a configuration object:

(the change is at step 4, highlighted)

  1. you remove the configuration object from the source AI
  2. you upload the updated configuration as an Export Profile to AMS
  3. you provision the updated profile with AMS to all the AIs where you would like to have the configuration object removed.
  4. the target AI's configuration gets updated and the configuration object is deleted from the target AI, if the configuration object is not in use by the target instance.

Note: There is some (approx. 10-30s) delay when removing a policy or a service group as it takes time to traverse the dependencies before they can be removed from the system.

 

Configuration Removal explained through an example

To better explain the case when a configuration object is removed and when it is not because it is in use on the target instance, let's take the following example:

  1. TransportA configuration object is being used by ServiceGroupA and ServiceGroupB.
  2. You deploy the configurations of these service groups to target AI by using Export Profiles (export the configuration from the source AI, upload it to AMS as Export Profile, and provision it to the target AI).
  3. Then, you remove the TransportA configuration and ServiceGroupA on the source AI.
  4. You repeat the deploy of the configuration to the target AI using Export Profiles as described previously.
    • The TransportA will still be visible on target AI because ServiceGroupB is still using it.
  5. Then, you remove the TransportA from the ServiceGroupB definition on the source AI.
  6. You repeat the deploy of the configuration to the target AI using Export Profiles as described previously.
    • The TransportA is removed from the target AI because it is not in use anymore.

A further note about Transports

Transports are a particular configuration object because they can be referenced by AI BaseData objects either on

  • the Access Point side of a Service Group used in the listener's settings, or/and
  • the Managed Service side of a Service Group used in the sender's settings

In a general scenario, if the same transport is used on both sides (both on the Access Point and the Managed Service side), then the transport will not be removed, even if you remove it from the Dependencies Selection page of the configuration Export.

If the transport is only used, for eg, for the Access Point listener, and the Access Point is removed, then the transport should also be removed.

 

<supportagent>

Agent-only: Related to the topic of AI profiles provisioning, customers might mention that Removing service and policy group from export profile doesn't get deleted from target instance on provision. A JIRA ticket has been logged about it. Check the status of the JIRA ticket from the given article to know whether the bug has been already fixed and in which product version.

</supportagent>

 

Back to the top