Servicing forwarding elements in a network

• US 20040111517A1
• Filed: 12/09/2002
• Published: 06/10/2004
• Est. Priority Date: 12/09/2002
• Status: Abandoned Application

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Muralidhar, Rajeev D., Liu, Hsin-Yuo, Tang, Puqi, Aggarwal, Mitu
• Application Number:
  US10/315,816
• Publication Number:
  US 20040111517A1
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

A method and apparatus to provide service to an active network node may be described.

Claims

1. A method to service a network element, comprising:

initiating a service event for an element of an active network node;

performing said service event by processing a set of capabilities associated with said element.

2. The method of claim 1, wherein said service event comprises a Forwarding Element (FE) bind event to bind said FE with a Control Element (CE).

3. The method of claim 2, wherein said FE bind event comprises sending a bind event start message with a set of capability parameters for said FE to a CE Transport Module (CTM).

4. The method of claim 3, further comprising:

receiving said capability parameters;

initiating a bind callback event;

sending a bind callback message having bind callback parameters and said capability parameters to a Binding and Discovery Module (BDM);

receiving a bind complete message; and

receiving a bind callback complete message.

5. The method of claim 4, further comprising:

receiving said bind callback message;

creating a FE node in a namespace hierarchy;

sending a FE node message to a Namespace Module (NM);

receiving a namespace handle for said FE node;

sending a set FE properties message using said namespace handle to a Configuration and Management Module (CMM);

receiving a message indicating said FE properties were set;

creating at least one port node in said namespace hierarchy;

sending a port node message to said NM;

receiving a port handle;

sending a set port properties message using said port handle to said CMM;

receiving a message indicating said port properties were set;

sending said bind complete message to said CTM; and

sending a bind callback message to CMM to report said FE was bound to said CE.

6. The method of claim 5, further comprising:

receiving said FE node message;

creating a FE data placeholder;

sending a FE data placeholder message to said CMM;

sending said namespace handle to said BDM;

receiving said port node message;

creating a port placeholder;

sending a port placeholder message to said CMM; and

sending said port handle to said BDM.

7. The method of claim 6, further comprising:

receiving an application registration message;

registering said application for said FE bind event;

receiving said FE data placeholder message;

receiving said set FE properties message;

setting said FE properties;

sending said message indicating said FE properties were set to said BDM;

receiving said port placeholder message;

setting said port properties;

sending said message indicating said port properties were set to said BDM;

receiving said bind callback message;

sending a message indicating said FE was bound to said CE to said CTM; and

sending a new FE bind message notifying said application of said FE bind event.

8. The method of claim 7, further comprising:

sending said application registration message; and

receiving said new FE bind message.

9. The method of claim 1, wherein said service event comprises a Forwarding Element (FE) unbind event to unbind said FE from a Control Element (CE).

10. The method of claim 9, wherein said FE unbind event comprises sending a lost connection message having a FE identifier to a CE Transport Module (CTM).

11. The method of claim 10, further comprising:

initiating an unbind callback event;

sending an unbind callback message having unbind callback parameters and said FE identifier to a Binding and Discovery Module (BDM); and

receiving an unbind callback event complete message.

12. The method of claim 11, further comprising:

receiving said unbind callback message;

initiating a port down callback event;

sending a port down callback message to a Configuration Management Module (CMM);

deleting at least one port node for said FE;

sending a port node delete message to a Namespace Module (NM);

receiving a message indicating data for said port node has been deleted;

initiating an FE node down event callback;

sending an FE node down event callback message to said CMM; and

sending a delete FE node message to said NM.

13. The method of claim 12, further comprising:

receiving said port node delete message;

sending a message to delete data for said port node to said CMM;

receiving said port node delete message; and

sending a message to delete FE data to said CMM.

14. The method of claim 13, further comprising:

receiving said port down callback message;

receiving said message to delete data for said port node;

deleting said data for said port node;

sending said message indicating data for said port node has been deleted;

receiving said FE node down event callback message;

sending an FE unbind notification message to an application;

receiving said message to delete FE data;

deleting said FE data; and

sending said unbind callback event complete message.

15. The method of claim 14, further comprising receiving said FE unbind, notification message.

16. An apparatus, comprising:

a forwarding plane comprising at least one forwarding element (FE);

a control plane comprising at least one control element (CE);

a back plane for communicating capabilities information between said forwarding plane and said control plane;

a FE transport module (FTM) to aggregate and communicate said capabilities information using said back plane;

a CE transport module (CTM) to receive said capabilities information; and

a service management module (SMM) to initiate a FE bind event to discover and bind said FE to said CE using said capabilities information.

17. The apparatus of claim 16, wherein said SMM comprises:

a binding and discovery module (BDM) to manage discovery and binding of said FE to said CE;

a namespace module (NM) to create a FE node and at least one port node to store FE information during said FE bind event;

a configuration management module (CMM) to store FE and port capabilities information; and

an application module (AM) to use said bound FE.

18. The apparatus of claim 16, wherein said information may be communicated in accordance with a Forwarding And Control Element Separation (ForCES) Specification.

19. An article comprising:

a storage medium;

said storage medium including stored instructions that, when executed by a processor, result in servicing a network element by initiating a service event for an element of an active network node, and performing said service event by processing a set of capabilities associated with said element.

20. The article of claim 19, wherein the stored instructions, when executed by a processor, further result in performing said service event by initiating a Forwarding Element (FE) bind event to bind said FE with a Control Element (CE).

21. The article of claim 20, wherein the stored instructions, when executed by a processor, further result in said FE bind event by sending a bind event start message with a set of capability parameters for said FE to a CE Transport Module (CTM).

22. The article of claim 21, wherein the stored instructions, when executed by a processor, further result in receiving said capability parameters, initiating a bind callback event, sending a bind callback message having bind callback parameters and said capability parameters to a Binding and Discovery Module (BDM), receiving a bind complete message, and receiving a bind callback complete message.

23. The article of claim 22, wherein the stored instructions, when executed by a processor, further result in receiving said bind callback message, creating a FE node in a namespace hierarchy, sending a FE node message to a Namespace Module (NM), receiving a namespace handle for said FE node, sending a set FE properties message using said namespace handle to a Configuration and Management Module (CMM), receiving a message indicating said FE properties were set, creating at least one port node in said namespace hierarchy, sending a port node message to said NM, receiving a port handle, sending a set port properties message using said port handle to said CMM, receiving a message indicating said port properties were set, sending said bind complete message to said CTM, and sending a bind callback message to CMM to report said FE was bound to said CE.

24. The article of claim 23, wherein the stored instructions, when executed by a processor, further result in receiving said FE node message, creating a FE data placeholder, sending a FE data placeholder message to said CMM, sending said namespace handle to said BDM, receiving said port node message, creating a port placeholder, sending a port placeholder message to said CMM, and sending said port handle to said BDM.

25. The article of claim 24, wherein the stored instructions, when executed by a processor, further result in receiving an application registration message, registering said application for said FE bind event, receiving said FE data placeholder message, receiving said set FE properties message, setting said FE properties, sending said message indicating said FE properties were set to said BDM, receiving said port placeholder message, setting said port properties, sending said message indicating said port properties were set to said BDM, receiving said bind callback message, sending a message indicating said FE was bound to said CE to said CTM, and sending a new FE bind message notifying said application of said FE bind event.

26. The article of claim 25, wherein the stored instructions, when executed by a processor, further result in sending said application registration message, and receiving said new FE bind message.

27. The article of claim 19, wherein the stored instructions, when executed by a processor, further result in performing said service event by initiating a Forwarding Element (FE) unbind event to unbind said FE from a Control Element (CE).

28. The article of claim 27, wherein the stored instructions, when executed by a processor, further result in sending a lost connection message having a FE identifier to a CE Transport Module (CTM).

29. The article of claim 28, wherein the stored instructions, when executed by a processor, further result in initiating an unbind callback event, sending an unbind callback message having unbind callback parameters and said FE identifier to a Binding and Discovery Module (BDM), and receiving an unbind callback event complete message.

30. The article of claim 29, wherein the stored instructions, when executed by a processor, further result in receiving said unbind callback message, initiating a port down callback event, sending a port down callback message to a Configuration Management Module (CMM), deleting at least one port node for said FE, sending a port node delete message to a Namespace Module (NM), receiving a message indicating data for said port node has been deleted, initiating an FE node down event callback, sending an FE node down event callback message to said CMM, and sending a delete FE node message to said NM.

31. The article of claim 30, wherein the stored instructions, when executed by a processor, further result in receiving said port node delete message, sending a message to delete data for said port node to said CMM, receiving said port node delete message;

and sending a message to delete FE data to said CMM.

32. The article of claim 31, wherein the stored instructions, when executed by a processor, further result in receiving said port down callback message, receiving said message to delete data for said port node, deleting said data for said port node, sending said message indicating data for said port node has been deleted, receiving said FE node down event callback message, sending an FE unbind notification message to an application, receiving said message to delete FE data, deleting said FE data, and sending said unbind callback event complete message.

33. The article of claim 32, wherein the stored instructions, when executed by a processor, further result in receiving said FE unbind notification message.