Unicode characters in EvFormat and Pcause files cause no alarm title in alarm notifier
Article ID: 213725
Updated On:
Products
Issue/Introduction
We have AlarmNotifier configured to send the Alarm Title attribute 0x12b4c in the .alarmrc file. For some alarms, the Alarm Title is not appearing in the AlarmNotifier output.
For these 3 ProbableCauseIDs that we saw (0x210e7d, 0x5b10152 & 0x6970005), ProbableCause & AlarmTitle are not loading up properly in the AlarmNotifier output file. It just outputs SYMPTOMS as the value instead of the actual ProbableCause & AlarmTitle. It's only happening for these 3 ProbableCauseIDs. The remaining alarms are fine. The alarm is popping up fine in OneClick, but not in the AlarmNotifier output files.
Cause
Newline and other unicode control characters appear in the Probable Cause file:
u000a u000b u000c u000d
For example:
Prob06760008_en_US:
DOWNLOAD VOLUME FOR CLIENT EXCEEDED CRITICAL THRESHOLD\u000a\u000aSYMPTOMS:\u000a\u000aClient download volume exceeded the critical threshold limit.\u000a\u000aPROBABLE CAUS
ES:\u000a\u000aClient download volume exceeded the critical threshold limit. Refer to the corresponding event message for more details.\u000a\u000aRECOMMENDED ACTIONS:\u000a
\u000a1) Refer to the Event Message associated with this alarm for additional details that the device may have provided about the cause of this condition.\u000a\u000a2) Review the Events associated with this model that occurred in the same time frame as this alarm in order to gain insight into the device's state. These can be viewed from the Events tab in OneClick.
Resolution
2 different resolutions can be used. Choose whichever you prefer.
A. Remove unicode manually
You need to convert the unicode characters to ^M and then remove them using dos2unix command. This can be done with the following:
You'll essentially change the entries to be a ^M and then use dos2unix to remove the ^M:
1. First save all names with unicode characters . Save in some temporary file for example: files_names
egrep -rl "u000a|u000b|u000c|u000d" . > files_names
2. Replace ALL files with \u000d\u000a with ^M caharacter
grep -rl "u000a" . | xargs sed -i 's\u000a\r\n/g'
You may need to run the above event for every unicode instance found. The above example if for u000a. You may need to run for u000d, b, c etc.
3. Remove ^M character
cat ./files_names | xargs dos2unix
4. Remove files_names
rm -f files_names
5. reload the changes in the OneClick Administration page - Update Event and Alarm Files.
Restart Notifier
Check the new alarms generated.
OR
B. Customise the files in Event Configuration editor to change the format.
Add any change in ECE. This will add the event in the SPECROOT/custom/Events/EventDisp but in the correct format.
e.g. I edited the title and pcause in ECE which created the custom pcause and restarted notifier (you need to restart notifier to pick up the changes) and now we see the title and edits
============================================================
Alarm Notification from SPECTRUM
Alarm SET:
…
NotificationData:
ProbableCause: FAN FAILURE edited title
SYMPTOMS:
1. A fan failure has been detected..... edited
PROBABLE CAUSES:
1. A fan failure has been detected.... edited
RECOMMENDED ACTIONS:
1) Refer manual for specifications....edited
EventMessage: Thu 19 Sep, 2024 - 11:10:48 - A "fnTrapFanFailure" event has occurred, from Rtr_Cisco device, named sdwanrtr.
A fan failure has been detected. Not all devices have fan sensors.
See manual for specifications.
fnSysSerial =
sysName =
(event [0x05b10152])
Additional Information
This is tentatively scheduled to be fixed in Q1 CY 2025 Release 24.3.4 or 24.3.5
Feedback
