Concurrent transactions on NETCONF devices across network services

Patent metadata

Field	Value
Publication number	US-11979281-B2
Application number	US-202217657126-A
Country	US
Kind code	B2
Filing date	Mar 29, 2022
Priority date	Jul 27, 2018
Publication date	May 7, 2024
Grant date	May 7, 2024

Abstract

Techniques are disclosed for managing a network. In one example, a device configuration manager is configured to generate, in accordance with a device management protocol, a configuration change request representing a transaction having a first sub-transaction specifying a first configuration change for a network device of the network and a second sub-transaction specifying a second configuration change for the same network device. The device configuration manager is further configured to output the configuration change request to the network device and receive a reply message from the network device. The reply message includes a first response element specifying whether the first configuration change is successfully committed at the network device and a second response element specifying whether the second configuration change is successfully committed at the network device.

First claim

What is claimed is:

1. A method comprising:
outputting, by processing circuitry, a configuration change request representing a transaction comprising a transaction identifier for the transaction, a first sub-transaction specifying a first configuration change for a network device and a second sub-transaction specifying a second configuration change for the network device;
receiving, by the processing circuitry and from the network device, a reply message indicating the transaction identifier, the reply message including a first response element specifying that the first configuration change is successfully committed at the network device and a second response element specifying that the second configuration change is not successfully committed at the network device;
updating, by the processing circuitry, configuration data to include the first configuration change in response to the reply message indicating the transaction identifier and the first response element specifying that the first configuration change is successfully committed at the network device; and
refraining from updating, by the processing circuitry, the configuration data to include the second configuration change in response to the reply message indicating the transaction identifier and the second response element specifying that the second configuration change is not successfully committed at the network device.

2. The method of claim 1 , further comprising:
generating, by the processing circuitry, the configuration change request in accordance with a first device management protocol;
receiving, by the processing circuitry, via an administrator interface, an application level configuration in accordance with a second device management protocol; and
translating, by the processing circuitry, in accordance with a second device management protocol, the application level configuration into the first configuration change and the second configuration change.

3. The method of claim 2 ,
wherein the first device management protocol comprises a Network Configuration (NETCONF) protocol; and
wherein the second device management protocol comprises a YANG model and wherein translating the application level configuration comprises translating, using the YANG model, a first application level configuration change of the application level configuration corresponding to a first multiplexer identifier into the first configuration change and translating, using the YANG model, a second application level configuration change of the application level configuration corresponding to a second multiplexer identifier into the second configuration change.

4. The method of claim 3 ,
wherein the network device is a hub network device connected to a plurality of network devices;
wherein the first multiplexer identifier comprises a hub name for the hub network device and a first identifier value; and
wherein the second multiplexer identifier comprises the hub name and a second identifier value.

5. The method of claim 3 ,
wherein the network device is a hub network device connected to one or more network devices for a first tenant and one or more network devices for a second tenant;
wherein the first multiplexer identifier comprises a hub name for the hub network device and a first tenant identifier for the first tenant; and
wherein the second multiplexer identifier comprises the hub name and a second tenant identifier for the second tenant.

6. The method of claim 1 , wherein the processing circuitry is arranged in a network management system (NMS).

7. The method of claim 1 , wherein the configuration change request is a first configuration change request, wherein the transaction is a first transaction, wherein the reply message is a first reply message, wherein the network device is a first network device, the method comprising:
generating, by the processing circuitry, a second configuration change request representing a second transaction specifying a batch of configuration changes for a second network device;
outputting, by the processing circuitry, the second configuration change request to the second network device; and
in response to receiving a second reply message specifying the batch of configuration changes is not successfully committed at the network device, dividing, by the processing circuitry, the batch of configuration changes into a first sub-set of one or more configuration changes and a second sub-set of one or more configuration changes.

8. The method of claim 7 , wherein dividing the batch of configuration changes is based on an error message indicated in the second reply message.

9. The method of claim 7 , comprising:
generating, by the processing circuitry, a third configuration change request indicating a third transaction specifying the first sub-set of one or more configuration changes for the second network device; and
outputting, by the processing circuitry, the third configuration change request to the second network device.

10. A system comprising:
one or more processors;
a configuration datastore configured to store configuration data; and
a device configuration manager executing on the one or more processors and configured to:
output a configuration change request representing a transaction comprising a transaction identifier for the transaction, a first sub-transaction specifying a first configuration change for a network device and a second sub-transaction specifying a second configuration change for the network device;
receive, from the network device, a reply message indicating the transaction identifier, the reply message including a first response element specifying that the first configuration change is successfully committed at the network device and a second response element specifying that the second configuration change is not successfully committed at the network device;
update the configuration data stored at the configuration datastore to include the first configuration change in response to the reply message indicating the transaction identifier and the first response element specifying that the first configuration change is successfully committed at the network device; and
refrain from updating the configuration data at the configuration datastore to include the second configuration change in response to the reply message indicating the transaction identifier and the second response element specifying that the second configuration change is not successfully committed at the network device.

11. The system of claim 10 , wherein the device configuration manager is further configured to:
generate the configuration change request in accordance with a first device management protocol;
receive, via an administrator interface, an application level configuration in accordance with a second device management protocol; and
translate, in accordance with a second device management protocol, the application level configuration into the first configuration change and the second configuration change.

12. The system of claim 11 , wherein the first device management protocol comprises a Network Configuration (NETCONF) protocol; and
wherein the second device management protocol comprises a YANG model and wherein, to translate the application level configuration, the device configuration manager is configured to translate, using the YANG model, a first application level configuration change of the application level configuration corresponding to a first multiplexer identifier into the first configuration change and translate, using the YANG model, a second application level configuration change of the application level configuration corresponding to a second multiplexer identifier

Assignees

• Juniper Networks Inc

Inventors

• A Chandrasekhar
• Anburose Nirmal
• R Jayanthi

Classifications

• H04L41/0816 Primary

  the condition being an adaptation, e.g. in response to network events · CPC title

• H04L41/0813 Primary

  characterised by the conditions triggering a change of settings · CPC title

• H04L41/0213 Primary

  Standardised network management protocols, e.g. simple network management protocol [SNMP] · CPC title

• H04L41/085

  Retrieval of network configuration; Tracking network configuration history · CPC title

• H04L41/12

  Discovery or management of network topologies · CPC title