Distributed embedded software for a switch

• US 20070061813A1
• Filed: 08/30/2005
• Published: 03/15/2007
• Est. Priority Date: 08/30/2005
• Status: Abandoned Application

• Current Assignee: Mcdata Corporation (Broadcom, Inc.)
• Original Assignee: Mcdata Corporation (Broadcom, Inc.)
• Inventors: Rodgers, James, Crater, Michael, Cox, William, Burrell, Brian, Goodin, Douglas, Beal, David
• Application Number:
  US11/215,877
• Publication Number:
  US 20070061813A1
• Time in Patent Office: Days
• US Class Current: 718/105
• CPC Class Codes: G06F 9/445 Program loading or initiating bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57

Abstract

A flexible architecture for embedded firmware of a multiple protocol switch can be implemented on a variety of hardware platforms. Hardware components of a SAN switch are embodied as cooperative modules (e.g., switch modules, port modules, service modules, etc.) with one or more processors in each module. Likewise, firmware components of a SAN switch can be assigned at initialization and/or run time across a variety of processors in any of these modules. The processors and firmware components can communicate via a messaging mechanism that is substantially independent of the underlying communication medium or the module in which a given processor resides. In the manner, firmware components can be reassigned (e.g., in a failover condition), added or removed without substantial disruption to the operation of the SAN.

Claims

1. A method of distributing firmware services across multiple processors in a network switch, the method comprising:

discovering the multiple processors within the network switch;

computing a distribution scheme for the firmware services among the identified multiple processors; and

selectively assigning individual firmware components associated with each firmware service to the identified multiple processors in accordance with the distribution scheme; and

selectively loading the firmware components assigned to each processor.

2. The method of claim 1 further comprising

executing the loaded firmware components on the assigned processor.

3. The method of claim 1 wherein the discovering operation comprises:

querying a device through an extender port; and

receiving a module identifier from the device.

4. The method of claim 1 wherein the computing operation comprises:

identifying a set of the firmware services to execute in the switch; and

allocating the identified firmware services evenly across the multiple processors to yield the distribution scheme.

5. The method of claim 1 wherein the computing operation comprises:

identifying a set of the firmware services to execute in the switch;

determining a weight associated with each identified firmware service; and

allocating the identified firmware services across the multiple processors such that an aggregate weight of firmware services is assigned to each processor to yield the distribution scheme.

6. The method of claim 1 wherein the computing operation comprises:

identifying a set of the firmware services to execute in the switch;

determining which identified firmware services have an affinity for each other; and

allocating the identified firmware services having an affinity for each other to the same processor in the distribution scheme.

7. The method of claim 1 further comprising:

assigning an active role to an instance of a firmware service assigned to one of the processors.

8. The method of claim 1 further comprising:

assigning a backup role to an instance of a firmware service assigned to one of the processors.

9. The method of claim 1 further comprising:

assigning a primary role to an instance of a firmware service assigned to one of the processors.

10. The method of claim 1 further comprising:

monitoring a health status of an active instance of a firmware service on a first processor;

detecting a failure of the firmware service based on the monitored health status;

failing over to a backup instance of the firmware service on a second processor.

11. The method of claim 1 further comprising:

monitoring a health status of a first processor executing an active instance of a firmware service;

detecting a failure of the first processor based on the monitored health status;

failing over to a backup instance of the firmware service on a second processor.

12. The method of claim 1 wherein the selectively assigning operation comprises:

assigning at least two different versions of the same firmware component to a single processor.

13. The method of claim 1 wherein the selectively loading operation comprises:

loading at least two different versions of the same firmware component for execution by a single processor.

14. The method of claim 1 further comprising:

executing at least two different versions of the same firmware component by a single processor.

15. A computer-readable medium having computer-executable instructions for performing a computer process implementing method of claim 1.

16. A networking switch supporting distribution of firmware services across multiple processors, the networking switch comprising:

a discovery module that identifies the multiple processors within the network switch;

a computation module that computes a distribution scheme for the firmware services among the identified multiple processors;

a deployment module that selectively assigns firmware components associated with each firmware service to the identified multiple processors in accordance with the distribution scheme; and

a subsystem module that selectively loads the firmware components assigned to each processor.

17. The networking switch of claim 16 wherein the subsystem module further executes the loaded firmware components on the assigned processor.

18. The networking switch of claim 16 wherein the discovery module queries a device through an extender port of the network switch and receives a module identifier from the device.

19. The networking switch of claim 16 wherein the computation module identifies a set of the firmware services to execute in the switch and allocates the identified firmware services evenly across the multiple processors to yield the distribution scheme.

20. The networking switch of claim 16 wherein the computation module identifies a set of the firmware services in the switch, determines a weight associated with each identified firmware service, and allocates the identified firmware services across the multiple processors such that an aggregate weight of firmware services is assigned to each processor to yield the distribution scheme.

21. The networking switch of claim 16 wherein the computation module identifies a set of the firmware services to execute in the switch, determines which identified firmware services have an affinity for each other, and allocates the identified firmware services having an affinity for each other to the same processor in the distribution scheme.

22. The networking switch of claim 16 further comprising:

a heartbeat monitor that monitors a health status of an active instance of a firmware service on a first processor and detects a failure of the firmware service based on the monitored health status; and

a communications module that fails over to a backup instance of the firmware service on a second processor.

23. The networking switch of claim 16 further comprising:

a heartbeat monitor that monitors a health status of a first processor executing an active instance of a firmware service and detects a failure of the first processor based on the monitored health status;

a communications module that fails over to a backup instance of the firmware service on a second processor.

24. The networking switch of claim 16 wherein the subsystem module loads at least two different versions of the same firmware component for execution by a single processor.

25. The networking switch of claim 16 wherein the subsystem module executes at least two different versions of the same firmware component by a single processor.