Hi, this is a related to a previous question that was posted DMA_ID/Element_ID mismatch after migration with a focus on the behavior of the SNMP Manager filter.
Consider the following scenario (carried out on DMA-10.1.7.0):
- Set up a trap receiver on a separate host.
- On a DMS with two DMA (DMA_1 and DMA_2) configure an SNMP Manager that will send alarms from DMA_1 (refer to screenshot above)
- Create an element on DMA_1, and raise alarms on that element – I noticed that alarms on the trap receiver for that element comes from DMA_1 as expected.
- Next migrate the element to DMA_2 (using the migrate function in System Centre). Check that the DMAID is unchanged but the hostname of the hosting DMA is of DMA_2 (this can be seen from the edit page of the element)
- Raise alarms from the element again – I noticed that alarms on the trap receiver for that element still comes from DMA_1
Conclusion: The filter in SNMPManager “Is DataMiner Agent Equal to SLC-H43-G04” appears to filter on the DMA ID rather than the hosting DMA. Is this the expected behavior of the filter?
Hi Bing,
The ‘DataMiner Agent’ option in the filter indeed applies to the DMA ID as you noticed. This seems to be the expected behavior.
I captured the message that Cube sends to create a filter using the Client Test Tool and noticed that it should also be possible to create a filter with the hosting agent ID:
To test this, I made a simple script that creates a filter for each DMA in our test cluster with this hosting agent ID option. I then used these filters to filter alarms in Cube. This gives the following result:
Conclusion: The filtering seems to work as expected, but there is no option in Cube to create a filter with the hosting agent ID, even though the option is available in the filter API. An internal task should be created that will rectify that.
Thank you Thomas for providing the required clarification to this query.