Syslog traps raising events 0x21001a and 0x210c0e in Spectrum

Products

• DX NetOps
• CA Spectrum

Issue/Introduction

Cisco Syslog trap raised event 0x210c0e but generated no alarm & when trap condition was cleared, a 0x21001a minor severity alert is raised.

Environment

DX NetOps Spectrum all currently supported releases

Resolution

These are Cisco Syslog events so they get their variable details from the Syslog messages. 

Event 0x210c0e is the default event Spectrum creates for Syslog traps. If Spectrum cannot find any event to map the Syslog traps from the following three files or in the custom folder, Spectrum would generate this Syslog Event 0x210c0e.

$SPECROOT>/SS/CsVendor/Ctron_CAT/Switch.txt
$SPECROOT>/SS/CsVendor/CiscoPIX/Pix.txt
$SPECROOT>/SS/CsVendor/Cisco_Router/Rtr.txt

The 0x210c0e by default, doesn't have an alarm attached to it since it is the default event raised by all Syslog traps if they're not mapped in the 3 files above. If it had a severity setting to raise an alarm, then EVERY Syslog trap would generate an alarm

The trap comes in formatted as such:

FACILITY-SEVERITY-MNEMONIC: Message-text

Spectrum then parses the above files for a match. If no match is found, it then processes to 0x210c0e.

Spectrum generates the events based on the incoming Syslog traps, so the 0x210c0e and 0x21001a events are being generated in the order they arrive.