Change the Monitoring Profile Change Detection Time in CA Performance Management
Article ID: 189597
Updated On:
Products
CA Infrastructure Management
CA Performance Management - Usage and Administration
DX NetOps
Issue/Introduction
When the detection rate is set to 24 hours and the Enable Change Detection box is checked for a Monitoring Profile is it possible to adjust the time of day when that occurs for one device?
Environment
Release : 3.7
Component : IM Reporting / Admin / Configuration
Resolution
You can't change the timing, but some other options:
A) Ideally, put the device in a collection that doesn't have Change Detection Enabled for Interface in a Monitoring Profile (MP), and update the MF manually or via rest:
https://knowledge.broadcom.com/external/article?articleId=137059
It can't be in ANY collection that has an MP with CD for interface enabled.
B) If you can't isolate the device(s)
a) Disable CD for the Interface Metric Family:
1. Get the DA item id from the DA Device Admin page.
2. Use a REST GET query to get the value of attribute ChangeDetectionDisabledMFs on the device:
http://da-host:8581/rest/devices/item-id
Where item-id is the item ID of the device that you'd like to disable the change detection.
3. Find the current value of attribute ChangeDetectionDisabledMFs.
If you don't see any entry of this attribute, it means there is no existing value for this attribute.
If there is already a disabled Metric Family, say CPU, you may see these values in the Get query:
<ChangeDetectionDisabledMFsList>
<ChangeDetectionDisabledMFs>{http://im.ca.com/normalizer}NormalizedCPUInfo</ChangeDetectionDisabledMFs>
</ChangeDetectionDisabledMFsList>
4. Send a REST PUT query to disable interface change detection:
URL: http://da-host:8581/rest/devices/item-id
Method: PUT
If step 2 shows no current value in ChangeDetectionDisabledMFs, use this body:
<Device version="1.0.0">
<ChangeDetectionDisabledMFsList>
<ChangeDetectionDisabledMFs>{http://im.ca.com/normalizer}NormalizedPortInfo</ChangeDetectionDisabledMFs>
</ChangeDetectionDisabledMFsList>
</Device>
If step 2 shows attribute ChangeDetectionDisabledMFs has existing value, say CPU is disabled, append Interface MF to the existing value, like this:
<ChangeDetectionDisabledMFsList>
<ChangeDetectionDisabledMFs>{http://im.ca.com/normalizer}NormalizedCPUInfo</ChangeDetectionDisabledMFs>
<ChangeDetectionDisabledMFs>{http://im.ca.com/normalizer}NormalizedPortInfo</ChangeDetectionDisabledMFs>
</ChangeDetectionDisabledMFsList>
b) You can then update manually or via REST
c) You would then need to re-disable after the update, or CD will be re-enabled.
NOTE: When CD is reenabled, you get a Reconfiguration/Changed event on the device: "Change detection is enabled for metric family ‘Interface’."
Note that if you do use the disable/reenable method, you can see when it is re-enabled either via the event, and/or by doing the get request on the device, to see when the disabled entry disappears.
That will give you an idea of how long it takes
A) Ideally, put the device in a collection that doesn't have Change Detection Enabled for Interface in a Monitoring Profile (MP), and update the MF manually or via rest:
https://knowledge.broadcom.com/external/article?articleId=137059
It can't be in ANY collection that has an MP with CD for interface enabled.
B) If you can't isolate the device(s)
a) Disable CD for the Interface Metric Family:
1. Get the DA item id from the DA Device Admin page.
2. Use a REST GET query to get the value of attribute ChangeDetectionDisabledMFs on the device:
http://da-host:8581/rest/devices/item-id
Where item-id is the item ID of the device that you'd like to disable the change detection.
3. Find the current value of attribute ChangeDetectionDisabledMFs.
If you don't see any entry of this attribute, it means there is no existing value for this attribute.
If there is already a disabled Metric Family, say CPU, you may see these values in the Get query:
<ChangeDetectionDisabledMFsList>
<ChangeDetectionDisabledMFs>{http://im.ca.com/normalizer}NormalizedCPUInfo</ChangeDetectionDisabledMFs>
</ChangeDetectionDisabledMFsList>
4. Send a REST PUT query to disable interface change detection:
URL: http://da-host:8581/rest/devices/item-id
Method: PUT
If step 2 shows no current value in ChangeDetectionDisabledMFs, use this body:
<Device version="1.0.0">
<ChangeDetectionDisabledMFsList>
<ChangeDetectionDisabledMFs>{http://im.ca.com/normalizer}NormalizedPortInfo</ChangeDetectionDisabledMFs>
</ChangeDetectionDisabledMFsList>
</Device>
If step 2 shows attribute ChangeDetectionDisabledMFs has existing value, say CPU is disabled, append Interface MF to the existing value, like this:
<ChangeDetectionDisabledMFsList>
<ChangeDetectionDisabledMFs>{http://im.ca.com/normalizer}NormalizedCPUInfo</ChangeDetectionDisabledMFs>
<ChangeDetectionDisabledMFs>{http://im.ca.com/normalizer}NormalizedPortInfo</ChangeDetectionDisabledMFs>
</ChangeDetectionDisabledMFsList>
b) You can then update manually or via REST
c) You would then need to re-disable after the update, or CD will be re-enabled.
NOTE: When CD is reenabled, you get a Reconfiguration/Changed event on the device: "Change detection is enabled for metric family ‘Interface’."
Note that if you do use the disable/reenable method, you can see when it is re-enabled either via the event, and/or by doing the get request on the device, to see when the disabled entry disappears.
That will give you an idea of how long it takes
Feedback
Yes
No
Powered by
