BGP trap to enable for ticketing in Spectrum
search cancel

BGP trap to enable for ticketing in Spectrum

book

Article ID: 191395

calendar_today

Updated On:

Products

CA Spectrum DX NetOps

Issue/Introduction

We have got a requirement for enabling the below BGP events for ticketing, however after checking we could see that the below event types was not present in SANM or alarm filters.
 
Event : BGP4_App has stopped responding to polls and/or external requests.  An alarm will be generated.
Event Type : 0x10d09
Model Type Name : BGP4_App
 
Event :BGP4_App has started responding to polls and/or external requests.
Event Type : 0x10d0b
Model Type Name : BGP4_App
 
When i tried searching the event type 0x10d09 in event configuration, i've found the below.
 
Event Code:0x00010d09        
Cause Code:0x00010700
Event Message:Application {m} of type {t} has stopped responding to polls and/or external requests.  An alarm will be generated.    
Type:APPLICATION CONTACT LOST
 
Kindly let us know if ticketing is enbabled for Event Code:0x00010d09 Cause Code:0x00010700 will we be getting ticket for the below event.
 

Environment

Release : Any

Component : Spectrum Core / SpectroSERVER

Resolution

10d09 does alarm and the severity is based on the event variable 1. You should most definitely get this alarm if the 1st variable specifies it to alarm.
But 10d0b does not alarm - it only clears cause code 10700 which is the cause code for 10d09.

Any 10dxx event is critical for Fault Intelligence so should not be edited or it will break fault intelligence. For this reason, they cannot be manipulated in alarm filters or sanm.

$ grep -r 0010d09 .
./Cabletron/EventDisp:0x00010d09 E 50 A {v 1},0x00010700

$ grep -r 0010d0b .
./Cabletron/EventDisp:0x00010d0b E 50 C 0x00010700

Additional Information

Do not customize the following list of event codes as this will adversely affect Spectrum’s fault isolation algorithms which leads to undesirable results.

LINK_GOOD = 0x00010d10,
LINK_BAD = 0x00010d11,
LINK_DISABLED = 0x00010d12,
LINK_UNKNOWN = 0x00010d13,
LINK_UNREACHABLE = 0x00010d14,
LINK_INITIAL = 0x00010d15,
LINK_BAD_SUPPRESSED = 0x00010d16,
LINK_LL_IN_MAINTENANCE = 0x00010d2e,
LINKED_PORT_BAD = 0x00010d17,
LINKED_DEVICE_BAD = 0x00010d18,
LINK_STATUS_CLEAR = 0x00010d2a,
LINK_DISABLED_AND_BAD = 0x0001040d,
LINK_ALWAYS_DOWN = 0x00010d2f,
LINK_BAD_WA_LINK_BAD = 0x00010d2d
CS_EVENT_ALARM_SET = 0x00010701
CS_EVENT_ALARM_UPDATED = 0x00010703
CS_EVENT_DEVICE_LOST = 0x00010302
DEVICE_CONTACT_STATUS_LOST = 0x00010d35
DEVICE_GATEWAY_UNREACHABLE = 0x00010d36
MGMT_LOST = 0x00010d00
UNRESOLVED_FAULT = 0x00010d05
APPLICATION_LOST = 0x00010d09
APPLICATION_REACTIVATED = 0x00010d0b
MGMT_REACTIVATED = 0x00010d0c
DEV_MNGMNT_NBORS_DOWN = 0x00010d19
LANDSCAPE_CONTACT_STATUS_CLEAR = 0x00010d20
PORT_LOST = 0x00010d66
PORT_REACTIVATED = 0x00010d67
ALARMING_MGMT_LOST_EVENT = 0x10daa
Customizing the above events would have direct impact on Fault Isolation (FI)/ Internal Port Link Status (IPLS).