Network management systems and methods

• US 10,177,962 B2
• Filed: 06/11/2014
• Issued: 01/08/2019
• Est. Priority Date: 06/11/2013
• Status: Active Grant

• Current Assignee: Ciena Corporation
• Original Assignee: Ciena Corporation
• Inventors: Haraszti, Zsolt, Dowker, Darren James, Lopez, Richard Sherman
• Primary Examiner(s): Tran, Nam T
• Application Number:
  US14/302,185
• Publication Number:
  US 20140365648A1
• Time in Patent Office: 1,672 Days
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 41/02 Standardisation; Integration
• CPC Class Codes: H04L 41/022 Multivendor or multi-standard integration
• 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 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/04 Processing captured monitoring data, e.g. for logfile generation

Abstract

Example network management systems and methods are described. In one implementation, a method identifies at least one network resource to be managed and identifies at least one domain to be managed. The method further identifies at least one service provider to be managed. A fusion object is created that defines the network resource, the domain, and the service provider to be managed.

Claims

1. A method, implemented by a network management system, comprising:

identifying at least one network resource to be managed;

identifying at least one domain to be managed comprising a set of networking and computing resources;

identifying at least one service provider to be managed;

creating, using one or more processors, a fusion object that defines the network resource, the domain, and the service provider to be managed, wherein the fusion object identifies a collection of physical resources and virtual services and includes at least one data center for the service provider, one or more servers and nodes in the at least one data center for the at least one domain, and at least one connection for the at least one network resource;

updating the fusion object based on one or more of network topology changes, resource changes, and service changes in the collection of physical resources and virtual services; and

managing, by the network management system through a plurality of Application Programming Interfaces (APIs), the at least one network resource, the at least one domain, and the at least one service provider using the fusion object as a single manageable entity that is used to perform the managing as a single point of management for all resources and services associated with the fusion object, wherein the fusion object uses resource objects and management interfaces to perform the managing in the one or more of servers and nodes in a networked system, and wherein the managing includes implementing changes to management requirements or preferences in the collection of physical resources and virtual services based on changes to the fusion object,

wherein the at least one domain includes a plurality of domains and the at least one service provider includes a plurality of service providers such that the single fusion object spans the plurality of domains and the plurality of service providers for management thereof via the plurality of APIs.

2. The method of claim 1, wherein identifying at least one network resource includes:

identifying the at least one physical resource of the fusion object; and

identifying the at least one virtual resource of the fusion object.

3. The method of claim 1, wherein the fusion object is recursive, containing one or more additional fusion objects.

4. The method of claim 1, wherein creating the fusion object is further based on a management preference associated with the network resource, domain, and service provider to be managed.

5. The method of claim 1, further comprising modifying the fusion object based on changes to a management preference associated with the network resource, domain, and service provider to be managed.

6. The method of claim 1, wherein the fusion object includes:

an identifier that uniquely identifies the network resource to be managed;

an identifier that uniquely identifies the domain to be managed; and

an identifier that uniquely identifies the service provider to be managed.

7. The method of claim 1, wherein the network resource to be managed is a data center.

8. The method of claim 1, wherein the network resource to be managed is a virtual machine contained in a data center.

9. The method of claim 1, wherein the fusion object is a combination of networking and non-networking resources that are managed as the single manageable entity.

10. The method of claim 1, further comprising updating or modifying the fusion object to reflect changes comprising network topology changes, resource changes, and service changes.

11. A method, implemented by a network management system, comprising:

identifying a physical resource to be managed by a fusion object;

identifying a virtual resource to be managed by the fusion object;

identifying a domain to be managed by the fusion object comprising a set of networking and computing resources;

identifying a service provider to be managed by the fusion object;

identifying a data center provider to be managed by the fusion object;

creating, using one or more processors, the fusion object that defines the physical resource, the virtual resource, the domain, the service provider, and the data center to be managed, wherein the fusion object identifies a collection of physical resources and virtual services and includes a plurality of data centers for the service provider and the data center provider, one or more servers and nodes in the plurality of data centers for the domain, at least one virtual machine for the virtual resource, and at least one connection for a network resource;

updating the fusion object based on one or more of network topology changes, resource changes, and service changes in the collection of physical resources and virtual services; and

managing, by the network management system through a plurality of Application Programming Interfaces (APIs), the physical resource, the virtual resource, the domain, the service provider, and the data center using the fusion object as a single manageable entity that is used to perform the managing as a single point of management for all resources and services associated with the fusion object, wherein the fusion object uses resource objects and management interfaces to perform the managing in the one or more of servers and nodes in a networked system, and wherein the managing includes implementing changes to management requirements or preferences in the collection of physical resources and virtual services based on changes to the fusion object,

wherein the domain includes a plurality of domains and the service provider comprises a plurality of service providers such that the single fusion object spans the plurality of domains and the plurality of service providers for management thereof via the plurality of APIs.

12. The method of claim 11, wherein the fusion object is recursive, containing one or more additional fusion objects.

13. The method of claim 11, wherein creating the fusion object is further based on a management preference associated with the physical resource, virtual resource, domain, and service provider to be managed.

14. The method of claim 11, further comprising modifying the fusion object based on changes to a management preference associated with the physical resource, virtual resource, domain, and service provider to be managed.

15. The method of claim 11, wherein the fusion object includes:

an identifier that uniquely identifies the physical resource to be managed;

an identifier that uniquely identifies the virtual resource to be managed;

an identifier that uniquely identifies the domain to be managed; and

an identifier that uniquely identifies the service provider to be managed.

16. The method of claim 11, wherein the physical resource to be managed is a data center.

17. The method of claim 11, wherein the virtual resource to be managed is a virtual machine contained in a data center.

18. An apparatus for network management comprising:

a memory; and

one or more processors coupled to the memory, the one or more processors configured to;

identify a network resource to be managed by a fusion object,

identify a domain to be managed by the fusion object comprising a set of networking and computing resources,

identify a service provider to be managed by the fusion object,

create the fusion object that defines the network resource, domain, and service provider to be managed, wherein the fusion object identifies a collection of physical resources and virtual services and includes at least one data center for the service provider, one or more servers and nodes in the at least one data center for the domain, and at least one connection for the at least one network resource,

update the fusion object based on one or more of network topology changes, resource changes, and service changes in the collection of physical resources and virtual services, and

manage, by the apparatus through a plurality of Application Programming Interfaces (APIs), the network resource, the domain, and the service provider using the fusion object as a single manageable entity that is used to perform the managing as a single point of management for all resources and services associated with the fusion object, wherein the fusion object uses resource objects and management interfaces to perform the management in the one or more of servers and nodes in a networked system, and wherein the management includes implementing changes to management requirements or preferences in the collection of physical resources and virtual services based on changes to the fusion object,

wherein the domain includes a plurality of domains and the service provider comprises a plurality of service providers such that the single fusion objects span the plurality of domains and the plurality of service providers for management thereof via the plurality of APIs.

19. The apparatus of claim 18, wherein the fusion object is recursive, containing one or more additional fusion objects.