Fast reboot for a switch

• US 9,524,173 B2
• Filed: 10/09/2014
• Issued: 12/20/2016
• Est. Priority Date: 10/09/2014
• Status: Active Grant

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: Brocade Communications Systems, Inc. (Broadcom, Inc.)
• Inventors: Guntaka, Vidyasagara R., Vobbilisetty, Suresh, Gowda, Manjunath A. G., Duraiswamy, Pasupathi
• Primary Examiner(s): Choudhury, Zahid
• Application Number:
  US14/511,026
• Publication Number:
  US 20160103692A1
• Time in Patent Office: 803 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/35 model driven
• CPC Class Codes: G06F 9/4401 Bootstrapping security arrangements therefor G06F21/57
• CPC Class Codes: H04L 41/0233 Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0853 by actively collecting configuration information or by backing up configuration information
• CPC Class Codes: H04L 41/0856 by backing up or archiving configuration information
• CPC Class Codes: H04L 41/0869 Validating the configuration within one network element
• CPC Class Codes: H04L 45/74 Address processing for routing

Abstract

One embodiment of the present invention provides a switch. The switch includes a packet processor, a persistent storage module, and a boot-up management module. The packet processor identifies a switch identifier associated with the switch in the header of a packet. The persistent storage module stores configuration information of the switch in a first table in a local persistent storage. This configuration information is included in a configuration file, and the first table includes one or more columns for the attribute values of the configuration information. The boot-up management module loads the attribute values to corresponding switch modules from the first table without processing the configuration file.

Claims

1. A switch, comprising:

a packet processor configured to identify a switch identifier associated with the switch in a header of a packet;

a persistent storage module configured to store configuration information of the switch in a first table in an object relational database in a local persistent storage, wherein the configuration information is included in a configuration file, and wherein the first table includes one or more columns for attribute values of the configuration information; and

a boot-up management module configured to load the attribute values to corresponding switch hardware modules from the first table the object relational database without processing the configuration file.

2. The switch of claim 1, wherein the boot-up management module is further configured to determine whether the configuration file has been changed during a reboot of the switch.

3. The switch of claim 2, wherein, in response to determining that the configuration file has been changed, the boot-up management module is further configured to:

determine a changed portion of the configuration file; and

update the first table based on the changed portion.

4. The switch of claim 1, wherein the boot-up management module is further configured to maintain an order in which the attribute values are loaded to the switch hardware modules.

5. The switch of claim 4, wherein the boot-up management module maintains the order based on a sequence table, wherein the sequence table includes one or more execution passes, and wherein the boot-up management module sequentially loads attribute values of one pass at time to the switch hardware modules.

6. The switch of claim 5, wherein a pass includes one or more features which are loaded to the switch hardware modules during the pass, and wherein a feature corresponds to a collection of attribute values.

7. The switch of claim 6, wherein the boot-up management module maintains an order of attribute values of a feature based on a dependency map, wherein the dependency map indicates a dependency based on a Unified Modeling Language (UML) model.

8. The switch of claim 6, wherein a pass is associated with a processing indicator which indicates whether the features of a pass are loaded to the switch hardware modules serially or in parallel.

9. The switch of claim 4, wherein the sequence table is associated with a scope, wherein the scope indicates a subset of attribute values of a feature to be loaded to the switch hardware modules.

10. The switch of claim 4, wherein the sequence table is expressed based on Extensible Markup Language (XML).

11. The switch of claim 1, further comprising a fabric switch module configured to maintain a membership in a network of interconnected switches, wherein the network of interconnected switches is identified by a fabric identifier.

12. A method, comprising:

identifying a switch identifier associated with a switch in a header of a packet;

storing configuration information of the switch in a first table in an object relational database in a local persistent storage, wherein the configuration information is included in a configuration file, and wherein the first table includes one or more columns for attribute values of the configuration information; and

loading the attribute values to corresponding switch hardware modules from the first table in the object relational database without processing the configuration file.

13. The method of claim 12, further comprising determining whether the configuration file has been changed during a reboot of the switch.

14. The method of claim 13, wherein, in response to determining that the configuration file has been changed, the method further comprises:

determining a changed portion of the configuration file; and

updating the first table based on the changed portion.

15. The method of claim 12, further comprising maintaining an order in which the attribute values are loaded to the switch hardware modules.

16. The method of claim 15, wherein the order is maintained based on a sequence table, wherein the sequence table includes one or more execution passes, and wherein the boot-up management module sequentially loads attribute values of one pass at time to the switch hardware modules.

17. The method of claim 16, wherein a pass includes one or more features which are loaded to the switch hardware modules during the pass, and wherein a feature corresponds to a collection of attribute values.

18. The method of claim 17, wherein an order of attribute values of a feature is maintained based on a dependency map, wherein the dependency map indicates a dependency based on a Unified Modeling Language (UML) model.

19. The method of claim 17, wherein a pass is associated with a processing indicator which indicates whether the features of a pass are loaded to the switch hardware modules serially or in parallel.

20. The method of claim 15, wherein the sequence table is associated with a scope, wherein the scope indicates a subset of attribute values of a feature to be loaded to the switch hardware modules.

21. The method of claim 15, wherein the sequence table is expressed based on Extensible Markup Language (XML).

22. The method of claim 12, further comprising maintaining a membership in a network of interconnected switches, wherein the network of interconnected switches is identified by a fabric identifier.

23. A computer system;

comprising;

a processor;

a storage device coupled to the processor and storing instructions that when executed by the processor cause the processor to perform a method, the method comprising;

identifying a switch identifier associated with a switch in a header of a packet;

storing configuration information of the switch in a first table in an object relational database in a local persistent storage, wherein the configuration information is included in a configuration file, and wherein the first table includes one or more columns for attribute values of the configuration information; and

loading the attribute values to corresponding switch hardware modules from the first table in the object relational database without processing the configuration file.

24. The computer system of claim 23, wherein the method further comprises maintaining an order in which the attribute values are loaded to the switch hardware modules, wherein the order is maintained based on a sequence table, wherein the sequence table includes one or more execution passes, and wherein the boot-up management module sequentially loads attribute values of one pass at time to the switch hardware modules.

25. The computer system of claim 24, wherein a pass includes one or more features which are loaded to the switch hardware modules during the pass, and wherein a feature corresponds to a collection of attribute values.

26. The computer system of claim 25, wherein a pass is associated with a processing indicator which indicates whether the features of a pass are loaded to the switch hardware modules serially or in parallel.