Staged startup after failover or reboot

• US 20040083404A1
• Filed: 10/29/2002
• Published: 04/29/2004
• Est. Priority Date: 10/29/2002
• Status: Active Grant

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: Brocade Communications Systems, Inc. (Broadcom, Inc.)
• Inventors: Mallory, Tracy D., Subramaniam, Subbu
• Granted Patent: US 7,065,673 B2
• Time in Patent Office: Days
• US Class Current: 714/13
• CPC Class Codes: G06F 11/2028 eliminating a faulty processor or activating a spare
• CPC Class Codes: G06F 11/203 using migration
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component

Abstract

A “high availability” system comprises multiple switches under the control of one more control processors (“CPs”). Each CP performs a staged startup process when failing-over from another CP or otherwise booting up. The staged startup process involves multiple stages of processing of various executable components of the image. Some stages may depend on the prior execution of other stages. The preferred staged startup process includes the use of a staging table which permits the standby image'"'"'s FSS facility to efficiently schedule the various stages of the fail-over process taking into account the inter-stage dependencies.

Claims

1. A method of bringing up a control processor to an active state, said control processor executing multiple software components, each component being brought up to an active state via one or more consecutive stages, and some of said stages being dependent on the prior execution of stages of different components, said method comprising:

(a) creating a staging table which includes identifiers of the component stages arranged in the order in which the components should be executed, said staging table also including values separating at least some of the stage identifiers so as to implement the inter-stage dependencies;

(b) accessing said staging table and retrieving the identifiers of one or more stages;

(c) executing the stages identified by the identifiers retrieved in (b);

(d) receiving acknowledgements after the stages in (c) have completed their execution;

and

(e) repeating (b)-(d) for additional stages.

2. The method of claim 1 wherein (a) includes forming rows and columns in said staging table, each row corresponding to a component and the columns including the stage identifiers and values.

3. The method of claim 2 wherein said a first stage of a first component depends on the prior execution of a second stage of a second component, and the first stage'"'"'s identifier is included in a column that is after the column in which the second stage'"'"'s identifier is included, so that the first stage will not be executed until after the second stage executes and acknowledges its completion.

4. The method of claim 2 wherein said a first stage of a first component depends both on the prior execution of a second stage of a second component and on the prior execution of a third stage of a third component, and the first stage'"'"'s identifier is included in a column that is after the column in which the second stage'"'"'s identifier is included and the column in which the third stage'"'"'s identifier is included, so that the first stage will not be executed until after both the first and second stages execute and acknowledge their completion.

5. The method of claim 1 wherein the values comprise null values.

6. The method of claim 1 wherein the identifiers comprise names.

7. The method of claim 1 wherein (a) is performed during compile time.

8. A system, comprising:

a plurality of electronic devices; and

a control processor having memory in which a staging table is stored, said control processor being coupled to and controlling the electronic devices, and a plurality of software components execute on said control processor;

wherein said control processor transitions to an active state of operation by executing one or more stages associated with each software component wherein some stages are dependent on the prior execution of stages of different components, said transition to the active state also includes accessing the staging table to retrieve identifiers of stages to execute, said identifiers are arranged in said table so as to implement the inter-stage dependencies.

9. The system of claim 8 wherein said staging table comprises rows and columns, each row corresponding to a component and the columns including the stage identifiers.

10. The system of claim 9 wherein some of the columns include values usable to implement the inter-stage dependencies.

11. The system of claim 10 wherein the values comprise null values.

12. The system of claim 8 wherein a first stage of a first component depends on the prior execution of a second stage of a second component, and the first stage'"'"'s identifier is included in a column of the staging table that is after the column in which the second stage'"'"'s identifier is included, so that the first stage will not be executed by said control processor until after the second stage executes and acknowledges its completion.

13. The system of claim 8 wherein a first stage of a first component depends both on the prior execution of a second stage of a second component and on the prior execution of a third stage of a third component, and the first stage'"'"'s identifier is included in a column of the staging table that is after the column in which the second stage'"'"'s identifier is included and the column in which the third stage'"'"'s identifier is included, so that the first stage will not be executed by said control processor until after both the first and second stages execute and acknowledge their completion.

14. The system of claim 8 further including more than one control processor with one control processor being active and the other control processor being a standby processor, and the standby processor takes control away from the active processor upon the occurrence of a fault with the active processor, and the standby processor accesses its staging table in order to become active.

15. The system of claim 8 wherein said electronic devices comprise network switches.

16. The system of claim 8 wherein said control processor includes a fabric state synchronization (“

FSS”

) facility running thereon which permits said control processor to be synchronized to another control processor, and said FSS access the staging table.

17. The system of claim 8 wherein the identifiers comprise names.

18. The system of claim 8, wherein the staging table is generated during compile time.

19. A control processor adapted to perform a staged startup of a plurality of software components, each component being brought up to an active state in one or more stages, some of the stages being dependent on other stages associated with different components, the control processor comprising:

a CPU;

memory coupled to said CPU, said memory containing a staging table which includes names of the stages arranged in the order in which the components should be executed, said staging table also including null values separating at least some of the stage names so as to implement the inter-stage dependencies; and

firmware stored in said memory and executed by said CPU, said firmware causing said control processor to;

(a) access said staging table and retrieve the names of one or more stages;

(b) execute the stages identified by the names retrieved in (a);

(c) receive acknowledgements after the stages have completed their execution; and

(d) repeat (a)-(c) for additional stages.

20. The control processor of claim 19 wherein said staging table comprises rows and columns, each row corresponding to a component and the columns including the stage names.

21. The control processor of claim 19 wherein some of the columns include the null values usable to implement the inter-stage dependencies.

22. The control processor of claim 19 wherein a first stage of a first component depends on the prior execution of a second stage of a second component, and the first stage'"'"'s name is included in a column of the staging table that is after the column in which the second stage'"'"'s name is included, so that the first stage will not be executed by said control processor until after the second stage executes and acknowledges its completion.

23. The control processor of claim 19 wherein a first stage of a first component depends both on the prior execution of a second stage of a second component and on the prior execution of a third stage of a third component, and the first stage'"'"'s name is included in a column of the staging table that is after the column in which the second stage'"'"'s name is included and the column in which the third stage'"'"'s name is included, so that the first stage will not be executed by said control processor until after both the first and second stages execute and acknowledge their completion.

24. The control processor of claim 19 further including a fabric state synchronization (“

FSS”

) facility running thereon which permits said control processor to be synchronized to another control processor, and said FSS performing (a)-(d).

25. The control processor of claim 19 wherein the firmware causes said control processor to perform (a)-(d) when said control processor takes control away from another control processor that has failed.

26. A computer readable storage medium for storing an executable set of software instructions that are executable by a CPU, said software instructions being operable to perform a staged startup up of a control processor which executes a plurality of software components, each component starting up via one or more stages and some of said stages being depend on stages of different components, said software instructions comprising:

(a) a means for accessing a staging table, which includes names of the stages arranged in the order in which the components should be executed, said staging table also including null values separating at least some of the stage names so as to implement the inter-stage dependencies, and retrieving the names of one or more stages;

(b) a means for executing the stages identified by the retrieved names;

(c) a means for receiving acknowledgements after the stages have completed their execution; and

a means for repeating (a)-(c) for additional stages.

27. The storage medium of claim 26 wherein said staging table comprises rows and columns, each row corresponding to a component and the columns including the stage names.

28. The storage medium of claim 27 wherein some of the columns include the null values usable to implement the inter-stage dependencies.

29. The storage medium of claim 26 wherein a first stage of a first component depends on the prior execution of a second stage of a second component, and the first stage'"'"'s name is included in a column of the staging table that is after the column in which the second stage'"'"'s name is included, so that the first stage will not be executed by said (b) means until after the second stage executes and acknowledges its completion.

30. The storage medium of claim 26 wherein a first stage of a first component depends both on the prior execution of a second stage of a second component and on the prior execution of a third stage of a third component, and the first stage'"'"'s name is included in a column of the staging table that is after the column in which the second stage'"'"'s name is included and the column in which the third stage'"'"'s name is included, so that the first stage will not be executed by said (b) means until after both the first and second stages execute and acknowledge their completion.

31. The storage medium of claim 26 further including a means for performing (a)-(d) when control is taken away from another control processor that has failed.