Usertag triggering alarms where it is not there in robot

[amar kondraju]

Hi all,

We are facing this false alarms issue with usertag .We have updated the usertag in robots and based on usertag we have created AO rules to trigger alarms but eventhough usertag is not there in the robot still alarm is triggering for that robot .Why is this?How to mitigate this?


Regards
Amar

[Gene Howard]

hi,
So the problem is not clear.
Are you getting false alarms from probes? IE alarms that the probe should not be sent because the condition does not exist?
Or are you getting valid alarms with incorrect usertags assigned to them?

What is the robot version these are coming from?
What are the probe and probe versions?
What hub version do the robots report to?

------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------

[amar kondraju]

Hi Gene ,

We have updated user_tag1 in all robots. After that we have created AO rules to trigger alarms based on the user_tag1.

For some robots there is no user_tag1 but still UIM is triggering alert from that robot!! - This is the problem.

UIM version - 9.0.2

robot version is 7.80

hub version is 7.96



I am talking about this below issue. Please provide the knowledge doc or hotfix for this issue.

Regards
Amar

[Gene Howard]

so this sounds different.
The mentioned HF is for setting the user tags at the hub level not at the robot level.
You are already during hub 7.96 so it should have this already in the code.
If you want to add this manually

Please make sure you have checked the below KB and that this is not the problem.
https://knowledge.broadcom.com/external/article?articleId=45198

the latest robot versions can be found here
https://support.broadcom.com/external/content/release-announcements/CA-Unified-Infrastructure-Management-Hotfix-Index/7233

------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------

[amar kondraju]

Hi Gene,

What I have said is We are getting these alarms from robot where usertag1 is not there . For mitigating this issue what could be the resolution?
I am not doing / I have not done any hotfix at hub level and I am telling you about the issue . If I do that at hub level will that resolves the issue or not is my concern. If I add any parameter in hub instead of creating scripts robotwise as suggested by you in below link will this issue resolve? How to stop alerts for robots where usertag is not there . I am not able to see this parameter add_hub_usertags_to_raw_data in my hub.cfg .

https://knowledge.broadcom.com/external/article?articleId=45198

Regards
Amar

[Franklin Ravi D'souza]

Hi 

robot version is 7.80/hub version is 7.96
Are these these the controller / hub versions of Primary hub ? or some secondary hub

[amar kondraju]

Hi ,

Yes these are versions of Primary hub and robot that reports to hub.


Regards
Amar

[Franklin Ravi D'souza]

Hi

but eventhough usertag is not there in the robot still alarm is triggering for that robot

->If you check the alarms from this robot where usertags were not defined but now alarms getting triggered ,now do you see usertags in alarms from probes from this robot
If yes what usertags do you see

[amar kondraju]

Hi Ravi ,


In this scenario I  want to convey that previously we have given some usertag1 in robot Y but it is removed now and still Y is taking previously updated usertag1 only while triggering alert for that robot Y . Why is this ? How to stop this ?  


Regards
AMar

[Franklin Ravi D'souza]

Hi

Can try clearing niscache of robot 

https://knowledge.broadcom.com/external/article/44669

and also upgrade to latest robot version for that robot and check

robot_update-7.97HF9