Federated management of intelligent service modules

• US 10,361,903 B2
• Filed: 04/25/2017
• Issued: 07/23/2019
• Est. Priority Date: 09/29/2005
• Status: Active Grant

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Inventors: Chamdani, Joseph I., Ramkumar, Gurumurthy D., Younglove, Bruce L., Hill, Corey R.
• Primary Examiner(s): Tang, Kiet
• Application Number:
  US15/497,026
• Publication Number:
  US 20170230228A1
• Time in Patent Office: 819 Days
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 49/40 Constructional details, e.g. power supply, mechanical construction or backplane
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04Q 3/0045 involving hybrid, i.e. a mixture of public and private, or multi-vendor systems
• CPC Class Codes: H04Q 3/66 Traffic distributors

Abstract

Intelligent services are provided in a storage network using intelligent service modules that can be cabled to a switch external to the switch chassis and yet be managed as part of the switch'"'"'s logical domain. Data and management communications between the intelligent service module and the core switch are provided through a “soft-backplane” implemented using in-band communications through cabling attached between the switch and the intelligent service module rather than through a hardwired backplane within the chassis. Management communications from management software is directed to the switch, which handles the management functions relating to the intelligent service module or forwards the management requests to the intelligent service module for processing.

Claims

1. A method comprising:

receiving a management request at a service function forwarder within a network, wherein the management request is indicative of performing a set of network services;

analyzing, by the service function forwarder, routing information encapsulated within the management request to identify a service function node that provides at least some of the network services;

forwarding the management request, by the service function forwarder and using the routing information encapsulated within the management request, to the service function node via a communication connection;

receiving a second management request at the service function forwarder within the network, wherein the second management request is indicative of performing a second set of network services;

analyzing, by the service function forwarder, routing information encapsulated within the second management request to identify a second service function node that provides at least some of the second set of network services; and

forwarding the second management request, by the service function forwarder and using the routing information encapsulated within the second management request, to the second service function node via a second communication connection,

wherein the service function forwarder, the service function node and the second service function node are part of a same domain.

2. The method of claim 1, further comprising:

receiving a response to the management request from the service function node via the communication connection.

3. The method of claim 1, further comprising:

receiving, at the service function forwarder, a third management request that includes encapsulated routing information that identifies a third service function node; and

forwarding, by the service function forwarder, the third management request to a third service function forwarder associated with the third service function node.

4. The method of claim 1, wherein the communication connection is an in-band communication between the service function forwarder and the service function node.

5. The method of claim 1, wherein the service function node is located external to the service function forwarder.

6. The method of claim 1, wherein the second service function node and the first service function node are associated with providing different network services.

7. The method of claim 1, wherein forwarding the management request, by the service function forwarder and using the routing information encapsulated within the management request, to the service function nodes comprises forwarding the management request based on Internet Protocol (IP) packet forwarding.

8. A service function forwarder device, comprising:

a first network port configured to receive a management request within a network, wherein the management request is indicative of performing a plurality of network services, and to receive a second management request within the network, wherein the second management request is indicative of performing a second plurality of network services;

a circuitry coupled to the first network port, wherein the circuitry is configured to analyze routing information encapsulated within the management request to identify a service function node that provides at least some of the network services and to analyze routing information encapsulated within the second management request to identify a second service function node that provides at least some of the second plurality of network services;

a second network port coupled to the circuitry, wherein the second network port is configured to transmit the management request to the service function node via a communication connection; and

a third network port, which is coupled to the circuitry, wherein the third network port is configured to transmit the second management request to the second service function node via a second communication connection,

wherein the service function forwarder device, the service function node and the second service function node are associated with a same domain.

9. The service function forwarder device of claim 8, wherein the second network port is further configured to receive a response to the management request from the service function node via the communication connection.

10. The service function forwarder device of claim 8, wherein the first network port is further configured to receive a third management request that includes a third service function encapsulation,

wherein the circuitry is further configured to identify a third service function node to route the third management request based on the third service function encapsulation, and

wherein service function forwarder device further comprises a fourth network port, which is coupled to the circuitry, is configured to forward the third management request to a third service function forwarder associated with the third service function node.

11. The service function forwarder device of claim 8, wherein the second service function node and the first service function node are associated with providing different network services.

12. The service function forwarder device of claim 8, wherein the communication connection is an in-band communication between the service function forwarder device and the service function node.

13. A system comprising:

a service function node configured to perform a first network service;

a second service function node configured to perform a second network service;

a plurality of communication links; and

a service function forwarder coupled to the service function node and the second service function node via the plurality of communication links within a network, wherein the service function forwarder is configured to;

receive a request, wherein the request is indicative of performing a plurality of network services;

identify the service function node based on encapsulated routing information within the request, wherein the first network service is one of the network services indicated in the request;

forward the request to the service function node based on the encapsulated routing information within the request;

receive a second request, wherein the second request is indicative of performing a second plurality of network services;

identify the second service function node based on encapsulated routing information within the second request, wherein the second network service is one of the second plurality of network services indicated in the second request; and

forward the second request to the second service function node based on the encapsulated routing information within the second request,

wherein the service function forwarder, the service function node and the second service function node are within a same domain.

14. The system of claim 13, wherein the service function node is configured to transmit a response to the request back to the service function forwarder via the communication connection.

15. The system of claim 13, wherein the service function forwarder is configured to:

receive a third request that includes encapsulated routing information that identifies a third service function node; and

forward the third request to a third service function forwarder associated with the third second service function node.

16. The system of claim 13, wherein the communication connection is an in-band communication between the service function forwarder and the service function node.

17. The system of claim 13, wherein the first network service and the second network service are different network services.