Active Alarm Table

Back End Front End

{
REST Call - GetActiveAlarms “AlarmId” :- “”,
First Time need to pick up
“Status” :- “Uncleared”,
data from back end GetActiveAlarms - Response ..
JSON Format ..
}

Once frontend is up it will Broadcast – (New Alarms)

1. If it is a new alarm it has to be {
receive the new alarms and added to the list “AlarmId” :- “”,
status from the backend Broadcast – (Alarm Update) 2. For existing alarms, update the “Status” :- “Uncleared”,
new values. “Ack” :- “”
3. If status is cleared, alarm will be ..
}
removed from the table
 Active Alarm Table

Filter Options
EMS 1 EMS 2 EMS 2 FE to BE
CheckBox Severity ERR :- Last Heartbeat or EMS1
Minor Active Alarms
Major
Critical
Warning

NE Name

Vendor Type
Nokia
Huawei
ZTE
 Active Alarm Table

Back End Front End

{
REST Call - GetActiveAlarms “AlarmId” :- “”,
First Time need to pick up
“Status” :- “Uncleared”,
data from back end GetActiveAlarms - Response ..
JSON Format ..
Receiver Worker }

WebSocket
Listens Port Broadcast – (New Alarms)
1. If it is a new alarm it has to be {
added to the list “AlarmId” :- “”,
Broadcast – (Alarm Update) 2. For existing alarms, update the “Status” :- “Uncleared”,
Insert into DB new values. “Ack” :- “”
Que ..
3. If status is cleared, alarm will be
}
removed from the table

PySNMP - SET Alarm Ack (Rest )

Server
SNMP Trap Receiver Worker

1. Reads the config from SNMP.conf 1. Reads the mib file data.json
1. To create the SNMV3 users 2. Maps the oid with the corresponding variables.
2. To get the port 3. If the vendor type is Huawei
3. To get the sender ip and vendor 1. Checks AlarmCategory,
combination 1. if the value is 3 (Event) it is discarded.
2. Checks whether the message received ip is part of 2. If the value is 1 (Fault) data is inserted in active alarm table
snmp.conf trap sender and history table.
1. If not rejects the message 3. If the value is 2 (Cleared) , particular alarm is deleted from
2. Yes - adds vendor type the message and active alarm. Im history table cleared time is updated.
push it to que 4. If the value 4 (Acknowledged), in active alarm / history
table ack time and ack user are updated.
5. If the value 4 (Acknowledged), in active alarm / history
table ack time and ack user are updated with blank
6. If the value 9 (changed), in active alarm / history table
alarm severity is updated.
 SNMP Traps / Requests

NMS
SNMP Traps
SNMP Monitor
Receiver FE
EMS Sender

Real Time Alarm

- New Alarm
How to differentiate Traps - Update
- Clearing
Real Time Alarm Trap
1.3.6.1.6.3.1.1.4.1.0 = 1.3.6.1.4.1.2011.2.15.2.4.3.3.0.1 Alarm Syn Request
Alarm Synchronize
Alarm Syn Response
1.3.6.1.6.3.1.1.4.1.0 = 1.3.6.1.4.1.2011.2.15.2.4.3.3.0.3
Active Alarm Push
Heartbeat
1.3.6.1.6.3.1.1.4.1.0 = 1.3.6.1.4.1.2011.2.15.2.1.2.1.1.1.0.5
HeartBeat
Broadcast – EMS - Down

Alarm Ack - Request

Alarm Ack - Response

heartbeat

We will receive it for

all traps, we ignore
this.
Heartbeat for Huawei :-
1.3.6.1.2.1.1.3.0 = 2562252387

1.3.6.1.6.3.1.1.4.1.0 = 1.3.6.1.4.1.2011.2.15.2.1.2.1.1.1.0.5
These two will be always same, the second
Identifies the trap one shows the actual configuration in secs.
type. 1.3.6.1.4.1.2011.2.15.2.1.2.1.1.1.1.0 = SNMP Agent Here it says heartbeat is configured for
every 60 secs
1.3.6.1.4.1.2011.2.15.2.1.2.1.1.1.2.0 = 60

1.3.6.1.4.1.2011.2.15.2.1.2.1.1.1.3.0 = 2021-08-13 05:50:50

This shows the time

heartbeat is pushed
Active Alarm sync – within NMS

NMS
EMS Receiver Worker Database Sync Worker Front End

Real Time Alarm

Worker Picks up Active Alarm Table
- With new field Updated time for each row

Picks up active alarm at regular intervals

If the updated time is
Broadcast to FE greater than the existing
one update the relevant
field
Synchronize with Huawei (NMS)

EMS Receiver Receiver Worker Monitor Front End

Synchronize Alarm – at the start of the application

Heartbeat Message
Heartbeat Message Checks whether heartbeat is
- EMS IP Heartbeat Message
getting rcvd as per the
- Heartbeat Rcv Time scheduled interval for that
EMS
- Scenario Yes no action
- Scenario No
Scenario – B broadcast to FE
through BE.
- EMS IP
- Status down
Synchronize Alarm – if there is any issues
Synchronize Alarms

EMS NMS Receiver NMS Monitor

Realtime Alarm
Synchronize will start as soon
Synchronize Set as we set the value to 1. Data
SET 1.3.6.1.4.1.2011.2.15.2.4.1.5.0 = 1 type is octetstring.
Synchronize Start
Alarm Synchronize Start
1.3.6.1.6.3.1.1.4.1.0 = 1.3.6.1.4.1.2011.2.15.2.4.3.3.0.2
Alarm Synchronize
1.3.6.1.6.3.1.1.4.1.0 = 1.3.6.1.4.1.2011.2.15.2.4.3.3.0.3
Realtime Alarm

Alarm Synchronize
1.3.6.1.6.3.1.1.4.1.0 = 1.3.6.1.4.1.2011.2.15.2.4.3.3.0.3
Synchronize End
Alarm Synchronize End Synchronize End and Set the
1.3.6.1.6.3.1.1.4.1.0 = 1.3.6.1.4.1.2011.2.15.2.4.3.3.0.4 sync oid to 0 is not functioning
Synchronize Set as it supposed to be.
SET 1.3.6.1.4.1.2011.2.15.2.4.1.5.0 = 0 For now if we get it we will
insert it in the table for info..
Acknowledge Alarms

EMS EMS

Note :- In front end our mapping needs Acknowledge Alarm

to corrected. SET 1.3.6.1.4.1.2011.2.15.2.4.4.1.0 = <Serial number of alarm>
- We need to add Alarm SN (Serial Datatype = octetstring
number) which is AlarmCSN
- Alarm id should be mapped to
AlarmID

UnAcknowledge Alarm
SET 1.3.6.1.4.1.2011.2.15.2.4.5.1.0 = <Serial number of alarm>
Datatype = octetstring