System and method for remote network management over unreliable and/or low-bandwidth communications links

• US 7,921,338 B2
• Filed: 09/05/2008
• Issued: 04/05/2011
• Est. Priority Date: 09/05/2008
• Status: Expired due to Fees

• Current Assignee: Computer Associates Think Inc. (Broadcom, Inc.)
• Original Assignee: Computer Associates Think Inc. (Broadcom, Inc.)
• Inventors: Buia, Christopher A., Pause, Kyle Andrew, Holmes, Daniel
• Primary Examiner(s): Iqbal; Nadeem
• Application Number:
  US12/205,130
• Publication Number:
  US 20100064183A1
• Time in Patent Office: 942 Days
• Field of Search: 714/4, 714 6- 8, 714 10- 13, 714 25- 27, 714/32, 714 37- 39, 714/43, 714/44, 714 46- 48, 714/56
• US Class Current: 714/48
• CPC Class Codes: H04L 41/0604 using filtering, e.g. reduction of information by using priority, element types, position or time
• CPC Class Codes: H04L 41/065 involving logical or physical relationship, e.g. grouping and hierarchies
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route

Abstract

A system includes a plurality of remote servers deployed in a remote network, a central information management server, and a connector for routing transmissions between the plurality of remote servers and the central information management server.

Claims

1. A system for remote network management, the system comprising:

a central information management server comprising;

a component for communicating with a plurality of remote servers over a data transmission medium;

a component for storing transmissions received from the plurality of remote servers;

a user interface for presenting to a user a partial model of a plurality of field units that are monitored by the central information management server;

and at least one remote network comprising;

the plurality of field units;

the plurality of remote servers for managing the plurality of field units, wherein each one of the plurality of remote servers is configured for;

polling the plurality of field units for tactical data;

receiving an alarm indicating an occurrence of a fault event at least one of the plurality of field units managed by said at least one remote server;

and determining whether the fault event should be transmitted to the central information management server by applying a test, wherein applying said test comprises steps of;

comparing the fault event to a plurality of alarm probable causes that are categorized as critical and non-critical; and

determining if the fault event is considered critical, if the fault event matches at least one of the plurality of alarm probable causes that is categorized as critical;

wherein the at least one remote server comprises;

a user interface for presenting a complete model of the plurality of field units under the purview of the at least one remote server;

and a network component configured for;

announcing itself to the central management information server upon set-up, and providing a complete list of managed assets within the at least one remote network and their status in real-time;

forwarding heartbeat messages at predetermined intervals to the central information management server;

forwarding information about the fault event in real-time to the central information management server only if the fault event if it is determined that the fault event should be transmitted;

and forwarding topology data and addressing re-synchronization requests only under a specific condition.

2. The system of claim 1 wherein the data transmission medium comprises a low bandwidth medium.

3. The system of claim 1 wherein the plurality of field units comprises at least one selected from a group consisting of:

a router, a switch, a firewall, and a workstation.

4. The system of claim 1 wherein the specific condition comprises initial activation of the remote server.

5. The system of claim 1 wherein the specific condition comprises a reconnection following a lost connection.

6. The system of claim 1 wherein the specific condition comprises a user request.

7. The system of claim 1 further comprising a fault tolerance safeguard comprising a backup server for the at least one remote server.

8. The system of claim 1 wherein the user interface is a web browser operatively coupled with the central information management system.

9. A method comprising:

at a remote server, receiving an alarm indicating an occurrence of a fault event at a remote unit managed by said remote server, said remote server being configured to monitor a plurality of field units and to forward alarms to a central network management server;

determining whether the fault event is critical by applying a test, wherein applying said test comprises steps of;

comparing the fault event to a plurality of alarm probable causes that are categorized as critical and non-critical; and

determining if the fault event is considered critical, if the fault event matches at least one of the plurality of alarm probable causes that is categorized as critical;

forwarding information about the fault event in real-time to the central network manager server if the fault event is determined to be critical;

forwarding heartbeat messages in real-time to the central network manager server; and

responding to re-synchronization requests and topology updates.

10. The method of claim 9 wherein the forwarding step comprises:

forwarding a title of the fault event and actual text of the fault event that caused the alarm to be generated.

11. The method of claim 9 wherein the forwarding step is performed by a connector that is coupled with the remote server.

12. A computer readable storage medium comprising program instructions for causing a processor to perform steps of:

monitoring a plurality of field units;

receiving an alarm indicating an occurrence of a fault event at one of the plurality of field units;

determining whether the fault event is critical by applying a test;

forwarding information about the fault event in real-time to a central network manager server if the fault event is determined to be critical, wherein said forwarding comprises forwarding a title of the fault event and actual text of the fault event that caused the alarm to be generated;

and forwarding heartbeat messages in real-time to the central network manager server;

and responding to re-synchronization requests and topology updates.

13. The computer readable storage medium of claim 12 wherein the program instructions for determining whether the fault event is critical further comprises program instructions for

comparing the fault event to a plurality of alarm probable causes that are categorized as critical and non-critical;

and

determining if the fault event is considered critical, if the fault event matches at least one of the plurality of alarm probable causes that is categorized as critical.