Providing failover assurance in a device

• US 7,076,696 B1
• Filed: 08/20/2002
• Issued: 07/11/2006
• Est. Priority Date: 08/20/2002
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Stringer, Fred M.
• Primary Examiner(s): Beausoliel, Robert
• Assistant Examiner(s): MASKULINSKI, MICHAEL C
• Application Number:
  US10/224,116
• Time in Patent Office: 1,421 Days
• Field of Search: 714/4, 714/41, 714/47
• US Class Current: 714/47.3
• CPC Class Codes: G06F 11/0751 Error or fault detection not based on redundancy power supply failures G06F1/30; network fault management H04L41/06

Abstract

A desired level of failover in a system is ensured by (i) capturing information about elements, such as components, modules, sub-systems, data, programs, routines, and/or information, etc. (referred to generally as “elements”), (ii) determining whether failover is compromised to an unacceptable degree, and (iii) persistently reporting compromised failover until proper remedial actions are taken.

Claims

1. A method for use in or with a system including primary elements and failover elements, the method comprising:

a) generating a baseline configuration of the system;

b) generating a configuration instance of the system;

c) determining whether a desired degree of failover exists based on the baseline configuration of the system and the configuration instance of the system;

d) if it is determined that a desired degree of failover does not exist, then reporting that the desired degree of failover does not exist;

e) generating a new configuration instance of the system;

f) re-determining whether a desired degree of failover exists based on the baseline configuration of the system and the new configuration instance of the system; and

g) if it is again determined that a desired degree of failover does not exists, then reporting that the desired degree of failover does not exist, wherein the act of reporting that the desired degree of failover does not exist persists until it is determined that a desired degree of failover exists.

2. The method of claim 1 wherein the configuration instance of the system includes conditions or parameters of the primary elements and failover elements included in the system.

3. The method of claim 1 wherein the primary elements and failover elements include at least one of modules, components, sub-systems, routines, data, and information.

4. The method of claim 1 wherein the system is a data forwarding device and wherein the primary elements and failover elements include at least one of power supplies, fans, cooling impellers, control processors, routing engines, clocking modules, synchronization modules, switch modules, schedulers, memory modules, data storage devices, service modules for tunnel services, and service modules for encryption services.

5. The method of claim 1 wherein the act of determining whether a desired degree of failover exists based on the baseline configuration of the system and the configuration instance of the system is performed by comparing the configuration instance of the system to the baseline configuration of the system.

6. The method of claim 1 wherein the act of generating a baseline configuration of the system is performed when the system is initialized.

7. The method of claim 1 wherein the system is a data forwarding device and wherein the primary elements and failover elements include at least one of logical configuration of secondary paths, logical configuration of backup label switched paths, and logical confirmation of backup nodes.

8. A method for use in or with a system including primary elements and failover elements, the method comprising:

a) generating a baseline configuration of the system;

b) generating a configuration instance of the system;

c) determining whether a desired degree of failover exists based on the baseline configuration of the system and the configuration instance of the system; and

d) if it is determined that a desired degree of failover does not exist, then reporting that the desired degree of failover does not exist,

wherein the act of reporting that the desired degree of failover does not exist sends reports to multiple entities, based on a policy.

9. The method of claim 8 wherein the policy specifies a tiered reporting policy.

10. The method of claim 8 wherein each of the multiple entities are identified by an Internet protocol address.

11. The method of claim 8 further comprising:

e) if further primary elements or failover elements are added to the system, then generating an updated baseline configuration to reflect the added primary elements or failover elements.

12. The method of claim 8 wherein the configuration instance of the system includes conditions or parameters of the primary elements and failover elements included in the system.

13. The method of claim 8 wherein the primary elements and failover elements include at least one of modules, components, sub-systems, routines, data, and information.

14. The method of claim 8 wherein the system is a data forwarding device and wherein the primary elements and failover elements include at least one of power supplies, fans, cooling impellers, control processors, routing engines, clocking modules, synchronization modules, switch modules, schedulers, memory modules, data storage devices, service modules for tunnel services, and service modules for encryption services.

15. The method of claim 8 wherein the act of determining whether a desired degree of failover exists based on the baseline configuration of the system and the configuration instance of the system is performed by comparing the configuration instance of the system to the baseline configuration of the system.

16. The method of claim 8 wherein the system is a data forwarding device and wherein the primary elements and failover elements include at least one of logical configuration of secondary paths, logical configuration of backup label switched paths, and logical confirmation of backup nodes.

17. An apparatus for use in or with a system including primary elements and failover elements, the apparatus comprising:

a) an input for accepting a baseline configuration of the system and a configuration instance of the system;

b) comparison facility for determining whether a desired degree of failover exists based on the baseline configuration of the system and the configuration instance of the system; and

c) a reporting facility for reporting that the desired degree of failover does not exist if it is determined that a desired degree of failover does not exist,

wherein the input accepts new configuration instances of the system,

wherein the comparison facility re-determines whether a desired degree of failover exits based on the baseline configuration of the system and the new configuration instance of the system, and

wherein the reporting facility repeatedly reports that the desired degree of failover does not exist until the comparison facility determines that the desired degree of failover exists.

18. The apparatus of claim 17 wherein the configuration instance of the system includes conditions or parameters of the primary elements and failover elements included in the system.

19. The apparatus of claim 17 wherein the primary elements and failover elements include at least one of modules, components, sub-systems, routines, data, and information.

20. The apparatus of claim 17 wherein the system is a data forwarding device and wherein the primary elements and failover elements include at least one of power supplies, fans, cooling impellers, control processors, routing engines, clocking modules, synchronization modules, switch modules, schedulers, memory modules, data storage devices, service modules for tunnel services, and service modules for encryption services.

21. The apparatus of claim 17 wherein the system is a data forwarding device and wherein the primary elements and failover elements include at least one of logical configuration of secondary paths, logical configuration of backup label switched paths, and logical confirmation of backup nodes.

22. An apparatus for use in or with a system including primary elements and failover elements, the apparatus comprising:

a) an input for accepting a baseline configuration of the system and a configuration instance of the system;

b) comparison facility for determining whether a desired degree of failover exists based on the baseline configuration of the system and the configuration instance of the system; and

c) a reporting facility for reporting that the desired degree of failover does not exist if it is determined that a desired degree of failover does not exist,

wherein the reporting facility sends reports that the desired degree of failover does not exist to multiple entities, based on a policy.

23. The apparatus of claim 22 wherein the policy specifies a tiered reporting policy.

24. The apparatus of claim 22 wherein each of the multiple entities are identified by an Internet protocol address.

25. The apparatus of claim 22 wherein the configuration instance of the system includes conditions or parameters of the primary elements and failover elements included in the system.

26. The apparatus of claim 22 wherein the primary elements and failover elements include at least one of modules, components, sub-systems, routines, data, and information.

27. The apparatus of claim 22 wherein the system is a data forwarding device and wherein the primary elements and failover elements include at least one of power supplies, fans, cooling impellers, control processors, routing engines, clocking modules, synchronization modules, switch modules, schedulers, memory modules, data storage devices, service modules for tunnel services, and service modules for encryption services.

28. The apparatus of claim 22 wherein the system is a data forwarding device and wherein the primary elements and failover elements include at least one of logical configuration of secondary paths, logical configuration of backup label switched paths, and logical confirmation of backup nodes.