Event management

• US 9,203,899 B2
• Filed: 09/29/2011
• Issued: 12/01/2015
• Est. Priority Date: 09/21/2005
• Status: Active Grant

• Current Assignee: Infoblox Incorporated
• Original Assignee: Infoblox Incorporated
• Inventors: Ansari, Morteza, Bailey, Stuart M.
• Primary Examiner(s): KUDDUS, DANIEL A
• Application Number:
  US13/249,130
• Publication Number:
  US 20120023195A1
• Time in Patent Office: 1,524 Days
• Field of Search: 707/794, 707/827, 707/959
• US Class Current: 1/1
• CPC Class Codes: G06F 16/95 Retrieval from the web
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/5014 using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
• CPC Class Codes: H04L 61/5046 Resolving address allocation conflicts; Testing of addresses testing when self-assigning an address H04L61/5092
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

Managing network event information from a plurality of network appliances is disclosed. Each network appliance provides a network service and each has a version of a common database. Managing includes detecting network event information at a first network appliance, updating a version of the common database on the first network appliance with the network event information, and propagating the network event information to other versions of the database on other network appliances.

Claims

1. A method of managing network event information from a plurality of network appliances each providing a network service and each having a version on a master, comprising:

detecting network event information at a first network appliance;

updating a version on a master on the first network appliance with the network event information, comprising;

receiving an item from the master; and

placing the item in a journal queue, the journal queue being used to verify that the item has been reconciled with the master;

determining whether a conflict exists relating to the updating of the version on the master, wherein the determining whether the conflict exists comprises;

determining whether the network event information includes the same IP address being assigned to a device that exists on the master;

in an event that the conflict does not exist relating to the updating of the version on the master;

propagating the network event information to other versions of the database on other network appliances; and

removing the item from the journal queue in one atomic transaction; and

in an event that the conflict exists relating to the updating of the version on the master;

backing the item out of the master; and

resolving the conflict relating to the updating of the version on the master, wherein the resolving of the conflict includes;

sending a new IP address for the device to a router, comprising;

updating the router to map the new IP address to the same IP address assigned to the device to redirect packets directed to the new IP address to the same IP address, the new IP address and the same IP address having the same network address and different host addresses; and

propagating the network event information to other versions of the database on other network appliances.

2. The method as recited in claim 1, further including updating a version of the master on a second network appliance with the network event information.

3. The method as recited in claim 1, wherein the event information is associated with the first network appliance.

4. The method as recited in claim 1, wherein the master includes network service data or event information.

5. The method as recited in claim 1, further including receiving an external command.

6. The method as recited in claim 1, further including receiving a simple network management protocol (SNMP) command.

7. The method as recited in claim 1, further including responding to the event information.

8. The method as recited in claim 1, further including determining whether to perform an action based on the event information.

9. The method as recited in claim 1, further including performing an action.

10. The method as recited in claim 1, further including restarting a service.

11. The method as recited in claim 1, wherein the event information indicates that another network appliance has failed and further including providing the network service previously provided by the failed network appliance.

12. The method as recited in claim 1, wherein an action is determined based on the event information and the action is overridden by a simple network management protocol (SNMP) command.

13. The method as recited in claim 1, wherein detecting includes detecting that a user has logged off.

14. The method as recited in claim 1, further including deprovisioning data from the database.

17. The method as recited in claim 1, wherein the redirecting of the packets directed to the new IP address to the same IP address is performed based on network address translation.

15. A system for managing network event information from a plurality of network appliances each providing a network service and each having a version on a master, comprising:

a processor configured to;

detect network event information at a first network appliance;

update a version on a master on the first network appliance with the network event information, comprising;

receive an item from the master; and

place the item in a journal queue, the journal queue being used to verify that the item has been reconciled with the master;

determine whether a conflict exists relating to the updating of the version on the master, wherein the determining whether the conflict exists comprises;

determine whether the network event information includes the same IP address being assigned to a device that exists on the master;

in an event that the conflict does not exist relating to the updating of the version on the master;

propagate the network event information to other versions on the master;

remove the item from the journal queue in one atomic transaction; and

in an event that the conflict exists relating to the updating on the master;

back the item out of the master; and

resolve the conflict relating to the updating of the version of the common database, wherein the resolving of the conflict includes;

send a new IP address for the device to a router, comprising;

update the router to map the new IP address to the same IP address assigned to the device to redirect packets directed to the new IP address to the same IP address, the new IP address and the same IP address having the same network address and different host addresses; and

propagating the network event information to other versions of the database on other network appliances; and

a memory coupled with the processor, wherein the memory provides the processor with instructions.

16. A computer program product for managing network event information from a plurality of network appliances each providing a network service and each having a version on a master, the computer program product being embodied in a non-transitory computer readable medium and comprising computer instructions for:

detecting network event information at a first network appliance;

updating a version on a master on the first network appliance with the network event information, comprising;

receiving an item from the master; and

placing the item in a journal queue, the journal queue being used to verify that the item has been reconciled with the master;

determining whether a conflict exists relating to the updating of the version exists on the master, wherein the determining whether the conflict relating to the updating of the version exists on the master comprises;

determining whether the network event information includes the same IP address being assigned to a device that exists on another device;

in an event that the conflict does not exist relating to the updating of the version on the master;

propagating the network event information to other versions of the database on other network appliances; and

removing the item from the journal queue in one atomic transaction; and

in an event that the conflict exists relating to the updating of the version on the master;

backing the item out of the master; and

resolving the conflict relating to the updating of the version of the common database, wherein the resolving of the conflict includes;

sending a new IP address for the device to a router, comprising;

updating the router to map the new IP address to the same IP address assigned to the device to redirect packets directed to the new IP address to the same IP address, the new IP address and the same IP address having the same network address and different host addresses; and

propagating the network event information to other versions of the database on other network appliances.