The 0x6c10000 event code was customized to generate an alarm. The alarm was generated and cleared based on the events, but actually, it is still visible in the OneClick Console.
DX NetOps Spectrum all currently supported releases
Based on the customization below, there is no event code that would clear the Critical alarm. And the following KB article was applied to clear the alarm:
KB : How to configure Spectrum to automatically clear an alarm after a specified amount of time.
In the $SPECROOT/custom/Events/AlertMap file:
# spsNotifyAlarm spsActiveAlarmSource1.3.6.1.4.1.23867.4.1.6.1 0x06c10000 1.3.6.1.4.1.23867.3.1.1.2.1.1.6(1,2)\ # spsActiveAlarmSeverity 1.3.6.1.4.1.23867.3.1.1.2.1.1.3(3,0)\ # spsActiveAlarmDescr 1.3.6.1.4.1.23867.3.1.1.2.1.1.5(76620,0)
In the $SPECROOT/custom/Events/EventDisp file:
0x10f4b E 50 A 3,0x00010f4b C 0x00010f890x6c10000 E 20 A 3,0x6c10000
The spsActiveAlarmSeverity could be used to generate a Conditional alarm severity.
In the $SPECROOT/SG-Support/CsEvFormat/EventTables/spsActiveAlarmSeverity_en_US file:
0x00000000 info0x00000001 warning0x00000002 minor0x00000003 major0x00000004 critical0x00000005 cleared0x00000006 acknowledged0x00000007 unacknowledged0x00000008 indeterminate
1. Edit the 0x6c10000 event code and change the Severity to Conditional, the Event Variable to 3 and click on Configure button:
2. Click on the "+" button to create an Alarm Severity Mapping:
3. And configure as follow:
4. Save the changes:
In the $SPECROOT/custom/Events/EventDisp file:
0x210d53 E 20 A 3,0x210d530x6c10000 E 20 A { v 3 CA.spsActive },0x6c10000,1
5. The Alarm Severity Mapping file (spsActive) is under $SPECROOT/custom/Events/CA/ directory:
As per:
TechDocs : DX NetOps Spectrum 24.3 : Working with Events and Alarms
Create an event condition to generate a new event code when Next-hop unreachable occurs:
In the $SPECROOT/custom/Events/EventDisp file:
0x6c10000 E 20 R { 1 } CA.EventCondition, "({v 76620} == {S \"Next-hop unreachable\"})" , "0xfff00000 -:-","(default)" , "0xfff00002 -:-"0xfff00000 E 20 A { v 3 CA.spsActive },0xfff00000,10xfff00002 E 20 A { v 3 CA.spsActive },0x6c10000,1
Command line to generate an alarm:
snmptrap -v1 -c public <SS_IP>:162 1.3.6.1.4.1.23867.4.1 <Device_IP> 6 1 '1631525403' 1.3.6.1.4.1.23867.3.1.1.2.1.1.6 s "device:192.168.0.1" 1.3.6.1.4.1.23867.3.1.1.2.1.1.3 i 3 1.3.6.1.4.1.23867.3.1.1.2.1.1.5 s "Next-hop unreachable"
snmptrap -v1 -c public <SS_IP>:162 1.3.6.1.4.1.23867.4.1 <Device_IP> 6 1 '1631525403' 1.3.6.1.4.1.23867.3.1.1.2.1.1.6 s "device:192.168.0.1" 1.3.6.1.4.1.23867.3.1.1.2.1.1.3 i 3 1.3.6.1.4.1.23867.3.1.1.2.1.1.5 s "An OSPF neighbor session is no longer in Full or Two-Way state"
Command line to clear an alarm:
snmptrap -v1 -c public <SS_IP>:162 1.3.6.1.4.1.23867.4.1 <Device_IP> 6 1 '1631525403' 1.3.6.1.4.1.23867.3.1.1.2.1.1.6 s "device:192.168.0.1" 1.3.6.1.4.1.23867.3.1.1.2.1.1.3 i 5 1.3.6.1.4.1.23867.3.1.1.2.1.1.5 s "Next-hop unreachable"
snmptrap -v1 -c public <SS_IP>:162 1.3.6.1.4.1.23867.4.1 <Device_IP> 6 1 '1631525403' 1.3.6.1.4.1.23867.3.1.1.2.1.1.6 s "device:192.168.0.1" 1.3.6.1.4.1.23867.3.1.1.2.1.1.3 i 5 1.3.6.1.4.1.23867.3.1.1.2.1.1.5 s "An OSPF neighbor session is no longer in Full or Two-Way state"