ISE 2.2 syslog levels not matching, ie CRITICAL is Local6.Alert

[theotang]

Why does ISE 2.2 send syslog messages with unmatching levels?  Here are two examples:

2018-04-11 09:13:56 Local6.Alert x.x.53.147 Apr 11 09:13:56 xxxisep12 CISE_Alarm CRITICAL: High Disk Utilization: Server=xxxisep11

2018-04-11 09:00:26 Local6.Critical x.x.53.147 Apr 11 09:00:26 xxxisep12 CISE_Alarm WARN: Profiler SNMP Request Failure : Server= xxxisepanp01; Endpoint IP Address=192.168.202.207

This is how I am reading the above messages:

Local6.Alert = CRITICAL

Local6.Critical = WARN

Am I missing something?  Thanks.

Version 2.2.0.470

Installed Patches 1,4,6

Product Identifier (PID) ISE-VM-K9

Version Identifier (VID) V01

ADE-OS Version 3.0.2.218

[Octavian Szolga]

Hi,

For syslog protocol/ message format you'd have a facility (system component that generates a message) and a  severity level (debugging, informational, warning, etc).

Local 6 is the 'system' that generated the message.

Regards,

Octavian