No alarm is generated for the 0x6a40036 custom event

book

Article ID: 224573

calendar_today

Updated On:

Products

CA Spectrum DX NetOps

Issue/Introduction

The following customization was done on the 0x6a40036 event code to generate a conditional alarm based on the value of the event variable 5, but no alarm is generated.

From the $SPECROOT/custom/Events/EventDisp file:

0x6a40036 E 20 A { v 5 CA.Viptela_bfd },0x6a40036,T,4

From the $SPECROOT/custom/Events/CA/SeverityMaps/Viptela_bfd file:

down 2
up C

From the $SPECROOT/SS/CsVendor/Vptl/AlertMap file:

# viptelaVpnInterfaceStateChange        eventTime
1.3.6.1.4.1.41916.100.2.6.55 0x06a40036 1.3.6.1.4.1.41916.100.1.1(1,0)\
                                        # netconfNotificationSeverity
                                        1.3.6.1.4.1.41916.100.1.2(2,0)\
                                        # viptelaVpnVpnId
                                        1.3.6.1.4.1.41916.100.1.67(3,0)\
                                        # viptelaVpnIfName
                                        1.3.6.1.4.1.41916.100.1.73(4,0)\
                                        # viptelaVpnNewState
                                        1.3.6.1.4.1.41916.100.1.74(5,0)

Cause

The variable 5 displayed in the 0x6a40036 event message was actually converted based on the viptelaVpnNewState file.

A "viptelaVpnInterfaceStateChange" event has occurred, from {t} device, named {m}.

viptela trap from viptela-vpn

eventTime = {S 1}
netconfNotificationSeverity = {T netconfNotificationSeverity 2}
viptelaVpnVpnId = {U 3}
viptelaVpnIfName = {S 4}
viptelaVpnNewState = {T viptelaVpnNewState 5}

In the $SPECROOT/SG-Support/CsEvFormat/EventTables/viptelaVpnNewState_en_US file:

0x00000000 up
0x00000001 down

 

Environment

Release : 20.2

Component : Spectrum Alarm & Event Management

Resolution

Change the values in the $SPECROOT/custom/Events/CA/SeverityMaps/Viptela_bfd file:

1 3
0 C

Attachments