IP Library Granted Patent US 10,198,338
Granted Patent B2
US 10,198,338 · App. 14/276,669 · Granted Feb 5, 2019

System and method of generating data center alarms for missing events

Inventor: Vyacheslav Lvin (San Jose, CA)
Assignee: Nokia of America Corporation
G06F11/327G06F9/45558G06F17/3033G06F17/30864H04L41/065H04L41/5025H04L41/5061
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,198,338
App. No.
14/276,669
Granted
Feb 5, 2019
Kind
B2
Abstract

Systems, methods, architectures, mechanisms and/or apparatus to manage alarm generation associated with the failure of an expected event or action to occur.

Claims (38)

1. A method of generating alarms at a data center (DC), comprising:

receiving, for processing according to a rule, first and second events associated with a hierarchically arranged entity of the DC;

hashing the first and second events according to a hash table of the rule;

in response to the hash table of the rule including a hash table entry corresponding to the first event, deleting the hash table entry corresponding to the first event and processing the first event according to the rule;

in response to the hash table of the rule not including a hash table entry corresponding to the second event, determining an expected event corresponding to the second event and hashing the expected event corresponding to the second event to provide a hash table entry corresponding to the expected event; and

in response to a failure to receive the expected event within a predetermined amount of time, generating an alarm.

2. The method of claim 1 , wherein said predetermined amount of time is defined with respect to an expiry time of the hash table entry.

3. The method of claim 2 , wherein said expiry time of the hash table entry is determined in accordance with a type of unexpected event associated with the hash table entry.

4. The method of claim 2 , wherein said expiry time of the hash table entry is determined in accordance with a type of expected event associated with the hash table entry.

5. The method of claim 1 , further comprising:

in response to said failure to receive the expected event within the predetermined amount of time, generating a missing expected event alarm.

6. The method of claim 5 , wherein said missing expected event alarm is indicative of a failure to receive a second event of an event pair.

7. A method, comprising:

receiving, at a management system, an event associated with a hierarchically arranged entity of a data center, said received event comprising a first event of an event pair;

identifying first and second rules for processing the event, each of the rules having associated with it a respective hash table;

for the first rule, in response to the received event being paired with an event stored within the respective hash table of the first rule, deleting the event stored within the respective hash table of the first rule; and

for the second rule, in response to the received event not being paired with an event stored within the respective hash table of the second rule, determining an expected event corresponding to the received event, hashing the expected event corresponding to the received event to provide a hash table entry corresponding to the expected event, and generating an alarm in response to a failure to receive the expected event within a predetermined amount of time.

8. The method of claim 7 , further comprising:

associating with the hash table entry corresponding to the expected event a corresponding expiry time; and

in response to an expiration of the hash table entry corresponding to the expected event, deleting the hash table entry corresponding to the expected event.

9. The method of claim 8 , further comprising:

in response to said expiration of said hash table entry corresponding to the expected event, generating a missing expected event alarm.

10. The method of claim 9 , wherein said missing expected event alarm is indicative of a failure to receive a second event of the event pair.

11. An apparatus configured to generate alarms at a data center (DC), the apparatus comprising:

at least one processor; and

at least one memory including computer program code;

wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least perform:

receiving, for processing according to a rule, first and second events associated with a hierarchically arranged entity of the DC;

hashing the first and second events according to a hash table of the rule;

in response to the hash table of the rule including a hash table entry corresponding to the first event, deleting the hash table entry corresponding to the first event and processing the first event according to the rule;

in response to the hash table of the rule not including a hash table entry corresponding to the second event, determining an expected event corresponding to the second event and hashing the expected event corresponding to the second event to provide a hash table entry corresponding to the expected event; and

in response to a failure to receive the expected event within a predetermined amount of time, generating an alarm.

12. A non-transitory computer readable storage medium storing instructions configured to cause an apparatus to at least perform:

receiving, for processing according to a rule, first and second events associated with a hierarchically arranged entity of a data center;

hashing the first and second events according to a hash table of the rule;

in response to the hash table of the rule including a hash table entry corresponding to the first event, deleting the hash table entry corresponding to the first event and processing the first event according to the rule;

in response to the hash table of the rule not including a hash table entry corresponding to the second event, determining an expected event corresponding to the second event and hashing the expected event corresponding to the second event to provide a hash table entry corresponding to the expected event; and

in response to a failure to receive the expected event within a predetermined amount of time, generating an alarm.

Assignments (5)
CHANGE OF NAME Recorded Nov 14, 2018
From: ALCATEL-LUCENT USA INC.
To: NOKIA OF AMERICA CORPORATION
Reel/Frame 047513/0350 →
RELEASE OF SECURITY INTEREST Recorded Sep 3, 2014
From: CREDIT SUISSE AG
To: ALCATEL-LUCENT USA INC.
Reel/Frame 033684/0046 →
RELEASE OF SECURITY INTEREST Recorded Aug 24, 2014
From: CREDIT SUISSE AG
To: ALCATEL-LUCENT USA, INC.
Reel/Frame 033596/0898 →
SECURITY INTEREST Recorded Aug 7, 2014
From: ALCATEL LUCENT USA, INC.
To: CREDIT SUISSE AG
Reel/Frame 033500/0156 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 13, 2014
From: LVIN, VYACHESLAV
To: ALCATEL-LUCENT USA INC.
Reel/Frame 032881/0771 →
Continuity (1)
Related Publication 20150331777A1 · Nov 19, 2015