IP Library Granted Patent US 10,003,498
Granted Patent B2
US 10,003,498 · App. 14/754,183 · Granted Jun 19, 2018

Efficient management of network configuration-dependent network functionality

Inventors: Michael Paul Shevenell (Dover, NH); Timothy Diep (Portsmouth, NH)
Assignee: CA, Inc.
H04L41/082H04L41/0816H04L41/12H04L41/5006H04L41/5038
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,003,498
App. No.
14/754,183
Granted
Jun 19, 2018
Kind
B2
Abstract

Notifications associated with software-defined network components are registered for. A notification is received in accordance with the registration. It is determined that the notification indicates a configuration change to a network associated with the software-defined network components. In response to a determination that the notification indicates the configuration change, a network topology associated with the network is determined. It is determined that one or more network functionalities are impacted by the configuration change based, at least in part, on the network topology. In response to a determination that the one or more network functionalities are impacted by the configuration change, the one or more network functionalities are updated based, at least in part, on the network topology.

Claims (57)

1. A method comprising:

registering with a software-defined network controller for a service manager to receive notifications about a network that includes software-defined network components controlled by the software-defined network controller, wherein the service manager is an application that monitors the network based on a service-level agreement;

based on receipt of a notification in accordance with the registering, determining a network configuration change indicated by the notification;

determining a topology of at least the software-defined network components at a time proximate with receipt of the notification;

determining that one or more network monitoring functionalities of the service manager are impacted by the network configuration change based, at least in part, on the topology; and

based on determining that the one or more network monitoring functionalities are impacted, updating the one or more network monitoring functionalities based, at least in part, on the topology.

2. The method of claim 1 , wherein said registering to receive the notifications comprises sending, from the service manager to a software-defined networking interface, a registration request, wherein the registration request identifies configuration change notifications.

3. The method of claim 1 , wherein said determining that one or more network monitoring functionalities are impacted by the network configuration change comprises:

identifying a first of the software-defined network components associated with the network configuration change; and

identifying metadata that associates the first software-defined network component to the one or more network monitoring functionalities.

4. The method of claim 1 , wherein the network configuration change comprises at least one of the provisioning of one or more of the software-defined network components, the removal of one or more of the software-defined network components, or the creation of a service chain.

5. The method of claim 1 , wherein the software-defined network components are communicatively coupled to form a service chain, wherein said determining that the one or more network monitoring functionalities are impacted by the network configuration change comprises:

determining that the network configuration change impacted the service chain; and

identifying the service level agreement based on association with the service chain.

6. The method of claim 5 , wherein said determining that one or more network monitoring functionalities are impacted by the network configuration change comprises identifying one or more tests associated with the service level agreement, wherein said updating the one or more network monitoring functionalities comprises updating the one or more tests based, at least in part, on the network configuration change.

7. The method of claim 5 , wherein said updating the one or more network monitoring functionalities comprises deploying one or more tests associated with the service level agreement.

8. The method of claim 1 , wherein the network configuration change comprises a modification to the service level agreement, wherein said determining that the one or more network monitoring functionalities are impacted by the network configuration change comprises identifying service chains associated with the service level agreement, wherein a first of the service chains comprises one or more of the software-defined networking components, wherein said updating the one or more network monitoring functionalities comprises:

determining a test for monitoring compliance of the first service chain with the service level agreement; and

deploying the test to those of the software-defined networking components associated with the first service chain.

9. The method of claim 1 further comprising:

sending, to the software-defined network controller, a command to modify a service chain;

wherein said determining that the notification indicates the network configuration change comprises determining, based, at least in part, on the notification, that the service chain has been modified.

10. One or more non-transitory machine-readable storage media comprising program code for a service manager to adapt network monitoring to network configuration changes in a network associated with a software-defined network controller, the program code to:

register with the software-defined network controller for the service manager to receive notifications about a network that includes software-defined network components controlled by the software-defined network controller, wherein the service manager is an application that monitors the network based on a service-level agreement;

based on receipt of a notification sent in accordance with said registration, determine a network configuration change indicated by the notification;

request from the software-defined network controller current topology of the network to determine whether topology of the network has changed based on the network configuration change;

based on a determination that the topology has changed, determine whether one or more network monitoring functionalities of the service manager are impacted by the topology change; and

based on a determination that the one or more network monitoring functionalities are impacted, update the one or more network monitoring functionalities based, at least in part, on the topology change.

11. The non-transitory machine-readable storage media of claim 10 , wherein the program code to register to receive the notifications comprises program code to send, to a software-defined networking interface, a registration request, wherein the registration request identifies configuration change notifications.

12. An apparatus comprising:

a processor; and

a machine-readable medium having program code for a service manager executable by the processor to cause the apparatus to,

register with a software-defined network controller for the service manager to receive notifications about a network that includes software-defined network components controlled by the software-defined network controller, wherein the service manager is an application that monitors the network based on a service-level agreement;

based on detection of receipt of a notification sent in accordance with said registration, determine a network configuration change indicated by the notification;

responsive to receipt of the notification and based on the network configuration change, request from the software-defined network controller current topology of the network to determine whether topology of the network changed;

determine whether one or more network monitoring functionalities are impacted based, at least in part, on the topology change; and

based on a determination that the one or more network monitoring functionalities are impacted, update the one or more network monitoring functionalities based, at least in part, on the topology change.

13. The apparatus of claim 12 , wherein the program code executable by the processor to cause the apparatus to register to receive the notifications comprises program code executable by the processor to cause the apparatus to send, to a software-defined networking interface, a registration request, wherein the registration request identifies configuration change notifications.

14. The apparatus of claim 12 , wherein the program code executable by the processor to cause the apparatus to determine whether one or more network monitoring functionalities are impacted comprises program code executable by the processor to cause the apparatus to:

identify a first of the software-defined network components associated with the network configuration change; and

identify metadata that associates the first software-defined network component to the one or more network monitoring functionalities.

15. The apparatus of claim 12 , wherein the network configuration change comprises at least one of the provisioning of one or more of the software-defined network components, the removal of one or more of the software-defined network components, or the creation of a service chain.

16. The apparatus of claim 12 , wherein the software-defined network components are communicatively coupled to form a service chain, wherein the program code executable by the processor to cause the apparatus to determine whether one or more network monitoring functionalities are impacted by the topology change comprises program code executable by the processor to cause the apparatus to:

determine whether the network configuration change impacted the service chain; and

identify a service level agreement associated with the service chain.

17. The apparatus of claim 16 ,

wherein the program code executable by the processor to cause the apparatus to determine whether one or more network monitoring functionalities are impacted comprises program code executable by the processor to cause the apparatus to identify one or more tests associated with the service level agreement,

wherein the program code executable by the processor to cause the apparatus to update the one or more network monitoring functionalities comprises program code executable by the processor to cause the apparatus to update the one or more tests based, at least in part, on the topology change.

18. The apparatus of claim 16 , wherein the program code executable by the processor to cause the apparatus to update the one or more network monitoring functionalities comprises program code executable by the processor to cause the apparatus to deploy one or more tests associated with the service level agreement.

19. The apparatus of claim 12 , wherein the program code further comprises program code executable by the processor to cause the apparatus to:

send, to a software-defined network controller, a command to provision one of the software-defined network component prior to receipt of the notification;

determine that the one of the software-defined network components has been provisioned based, at least in part, on the notification; and

based on a determination that the one of the software-defined network components has been provisioned, determine a startup latency associated with the software-defined network component.

20. The apparatus of claim 12 , wherein the program code further comprises program code executable by the processor to cause the apparatus to:

send, to a software-defined network controller, a command to release one of the software-defined network components prior to receipt of the notification;

determine that the one of the software-defined network components has been released based, at least in part, on the notification; and

based on a determination that the one of the software-defined network components has been released, determine a shutdown latency associated with the one of the software-defined network components.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 29, 2015
From: SHEVENELL, MICHAEL PAUL; DIEP, TIMOTHY
To: CA, INC.
Reel/Frame 035930/0315 →
Continuity (1)
Related Publication 20160380807A1 · Dec 29, 2016
Cited By (2)
US 12,223,051 US 12,289,311