NETCONF-ENABLED PROVISIONING IN ROLLBACK AGNOSTIC ENVIRONMENT

• US 20130194974A1
• Filed: 12/17/2012
• Published: 08/01/2013
• Est. Priority Date: 09/29/2009
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: PURKAYASTHA, Monimoy, MULPURI, Madhukar
• Granted Patent: US 8,953,494 B2
• Time in Patent Office: Days
• US Class Current: 370/255
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0856 by backing up or archiving configuration information
• CPC Class Codes: H04L 41/0863 by rolling back to previous configuration versions

Abstract

A method includes receiving configuration data for configuring network devices; generating remote procedure calls (RPCs) for configuring the network devices, which include provisioning and reverse provisioning RPCs, where each reverse provisioning RPC reverse provisions a particular pseudowire; providing to the network devices the provisioning RPCs; determining a success with respect to each of the provisioning RPCs, where the success indicates that all endpoints of a pseudowire have been successfully configured; providing the reverse provisioning RPCs to the network devices, when it is determined that the success has not been achieved; and storing an indication of success when it is determined that the success has been achieved with respect to the provisioning RPCs.

Claims

1-20. -20. (canceled)

21. A method comprising:

providing, by one or more devices, one or more provisioning remote procedure calls (RPCs);

determining, by the one or more devices, that a particular provisioning RPC, of the one or more provisioning RPCs, has not been successfully provisioned to a particular network device; and

providing, by the one or more devices and after determining that the particular provisioning RPC has not been successfully provisioned to the particular network device, a particular reverse provisioning RPC to the particular network device,

the particular reverse provisioning RPC being to reverse provision a particular pseudowire (PW) associated with the particular network device, and

the particular reverse provisioning RPC including information for returning one or more portions of particular configuration data, of the particular network device and associated with the particular PW, to a prior state that existed prior to the providing of the one or more provisioning RPCs.

22. The method of claim 21, where determining that the particular provisioning RPC has not been successfully provisioned includes:

determining that all endpoints of the particular PW have not being successfully configured.

23. The method of claim 21,

where the one or more devices include a Network Configuration (NETCONF) protocol-enabled server device, and

where the particular network device includes a NETCONF protocol-enabled network device.

24. The method of claim 21, further comprising:

receiving data associated with the particular network device; and

generating the one or more provisioning RPCs based on the data.

25. The method of claim 24, where generating the one or more provisioning RPCs includes:

selecting, based on the data, one or more provisioning templates that include scripting capability to provision the particular network device, and

generating the one or more provisioning RPCs based on the one or more provisioning templates.

26. The method of claim 21, where providing the one or more provisioning RCPs includes:

providing a lock command to the particular network device,

determining that the particular network device was successfully locked based on the lock command, and

providing the one or more provisioning RCPs after determining that the particular network device was successfully locked.

27. The method of claim 21, further comprising:

providing a commit command to the particular network device; and

determining that the commit command was successful before providing the particular reverse provisioning RPC to the particular network device.

28. The method of claim 21, further comprising:

archiving, before providing the one or more provisioning RPCs, particular data associated with the particular network device;

determining that the reverse provisioning of the particular PW is not successful after providing the particular reverse provisioning RPC to the particular network device; and

using the particular data to return the one or more portions of the particular configuration data to the prior state after determining that the reverse provisioning of the particular PW is not successful.

29. A device comprising:

one or more processors to;

provide one or more provisioning remote procedure calls (RPCs),

determine that a provisioning RPC, of the one or more provisioning RPCs, has not been successfully provisioned to a network device, and

provide, after determining that the provisioning RPC has not been successfully provisioned to the network device, a reverse provisioning RPC to the network device,

the reverse provisioning RPC including information for returning configuration data, of the network device, to a prior state that existed prior to providing the one or more provisioning RPCs.

30. The device of claim 29, where the one or more processors are further to:

provide a commit command to the network device, and

determine that the commit command was successful before providing the reverse provisioning RPC to the network device.

31. The device of claim 29,

where the reverse provisioning RPC is to reverse provision a pseudowire (PW) associated with the network device, and

where the configuration data is associated with the PW.

32. The device of claim 29,

where the device includes a Network Configuration (NETCONF) protocol-enabled server device, and

where the network device includes a NETCONF protocol-enabled network device that does not have rollback capability.

33. The device of claim 29, where the one or more processors are further to:

receive data associated with the network device, and

generate the one or more provisioning RPCs based on the data.

34. The device of claim 29, where, when providing the one or more provisioning RCPs, the one or more processors are to:

provide a lock command to the network device,

determine that the network device was successfully locked based on the lock command, and

provide the one or more provisioning RCPs after determining that the network device was successfully locked.

35. The device of claim 29, where the one or more processors are further to:

determine that reverse provisioning based on the reverse provisioning RPC is not successful after providing the reverse provisioning RPC to the network device, and

use archived data to return the configuration data to the prior state after determining that the reverse provisioning is not successful.

36. A non-transitory computer-readable medium storing instructions, the instructions comprising:

one or more instructions that, when executed by at least one processor, cause the at least one processor to;

provide a provisioning remote procedure call (RPC),

determine that the provisioning RPC has not been successfully provisioned to a network device, and

provide, after determining that the provisioning RPC has not been successfully provisioned to the network device, a reverse provisioning RPC to the network device,

the reverse provisioning RPC including information for returning configuration data, of the network device, to a prior state that existed prior to providing the provisioning RPC.

37. The non-transitory computer-readable medium of claim 36, where the one or more instructions to determine that that the provisioning RPC has not been successfully provisioned include:

one or more instructions that, when executed by the at least one processor, cause the at least one processor to;

determine that an endpoint of a pseudowire (PW), associated with the network device, has not been successfully configured, and

determine that that the provisioning RPC has not been successfully provisioned based on the endpoint of the pseudowire (PW) not being successfully configured.

38. The non-transitory computer-readable medium of claim 36,

where the network device includes a Network Configuration (NETCONF) protocol-enabled network device, and

where the provisioning RPC includes a Network Configuration (NETCONF) protocol RPC.

39. The non-transitory computer-readable medium of claim 36, where the instructions further comprise:

one or more instructions that, when executed by the at least one processor, cause the at least one processor to;

receive data associated with the network device, and

generate the provisioning RPC based on the data.

40. The non-transitory computer-readable medium of claim 36, where the one or more instructions to provide the provisioning RPC include:

one or more instructions that, when executed by the at least one processor, cause the at least one processor to;

provide a lock command to the network device,

determine that the network device was successfully locked based on the lock command, and

provide the provisioning RCP after determining that the particular network device was successfully locked.