Network Auto Configuration and Correction using Python.pptx

NETWORK DEVICE AUTO CONFIGURATION
& CORRECTION
Sai kumaresh L
17BEC1184
Guided by:
Prem Kumar, L&T
Prof. Sofana Reka, VIT

MOTIVATION
• Eliminate manual tasks
• Reduce errors
• Simplify Network
Management
• Optimize Performance
• Gain network visibility
2

OBJECTIVE
Implementation of
• Zero Touch
Provisioning(ZTP)
• Root Cause Analysis
(RCA)
3

SOFTWARE DETAILS
• Cisco Router Images (csr1000v,
c3725)
• Netmiko
• Python
• GNS3
• Ubuntu Linux
• Graphviz
4

CODES AND
STANDARDS
5
The codes are all written in Python programming language.
These Python scripts are executed with the help of linux
terminal inside the Network Automation appliance of GNS3
The Secure Shell (SSH) Transport Layer Protocal - IETF
Standard (rfc425)
The Dynamic Host Control Protocol (DHCP) - IETF Standard
(rfc2131)
The TFTP Protocol – IETF Standard (rfc1350)

ZERO TOUCH
PROVISIONING
(ZTP)
• ZTP helps in reducing the several
manual steps involved in
provisioning a network element to
two simple steps of Racking and
Stacking and Powering the device
on.
• When it’s powered on, the switch
sends out a request through DHCP
server to get the location of its
centrally stored image and
configuration, which it downloads
and runs.
• ZTP automates steps like updating
operating systems, deploying
patches and bug fixes.
6

METHODOLOGY
• When a device that supports Zero-Touch Provisioning
boots up and does not find the startup configuration
(during initial installation), the device enters the Zero-
Touch Provisioning mode.
• The device searches for a Dynamic Host Control
Protocol (DHCP) server, bootstraps itself with its
interface IP address, gateway, and Domain Name System
(DNS) server IP address, and enables Guest Shell.
• The device then obtains the IP address or URL of an
HTTP/TFTP server and downloads the Python script to
configure the device.
• Guest Shell provides the environment for the Python
script to run. Guest Shell executes the downloaded
Python script and applies an initial configuration to
the device.
7

DHCP SERVER
CONFIGURATION
FOR ZTP
• A DHCP server must be running on the same network as the new device that is being provisioned
• When the new device is switched on, it retrieves the IP address information of the HTTP/TFTP server
where the Python script resides, and the folder path of the Python script from the DHCP server.
• The DHCP server responds to DHCP discovery events with the following options:
• Option 150—(Optional) Contains a list of IP addresses that points to the HTTP/TFTP server on the management
network that hosts the Python scripts to be run.
• Option 67—Contains the Python script file path on the HTTP/TFTP server.
8

ADVANTAGES OF
ZERO TOUCH
PROVISIONING
• Reduce costs and save time for deployments
• More efficient use of staffing resources
• Minimize configuration errors
• Reduce number of tools required
• Eliminate the need for extra equipment
9

NETWORK
TOPOLOGY
• CSR1000V - New device
to be provisioned
• C3725 - DHCP Server
• Network Automation -
TFTP Server containing
the Python script
10

DHCP SERVER
CONFIG
• Network – 192.168.0.0/24
• TFTP Server Address –
192.168.0.2
• File Name – ztp_trial.py
11

ROOT CAUSE ANALYSIS
(RCA)
• RCA is applied to methodically identify
and correct the root causes of events,
as opposed to simply addressing their
symptomatic result.
• “Root cause” may be described as the
point in a causal chain where applying a
corrective action or intervention would
prevent the problem from occurring.
14

EXAMPLE
1. If the Router03 node goes down, there is no
response from other interfaces and IP
addresses that Router03 has.
2. A large number of failure events occurs.
3. The Monitoring Manager decides that the
lack of responses from IP addresses was
caused by the interface failures, and then
suppresses the corresponding incidents.
4. Based on the fact that communication was
lost at neighboring nodes, the Monitoring
Manager decides the root cause is the
Router03 node going down. The Monitoring
Manager also decides that the interface
failures were caused by the node going down
and associates the interface failures with the
Router03 node going down.
5. The Router03 node going down is reported
as the root-cause incident.
15

FAILURE IN MIDDLE-LEVEL SWITCH
Detailed failure: The middle-level switch C2 went down.
Events that occur:
• Communication with C2 is unavailable.
• Each node interface connecting with C2 went down.
The Monitoring Manage handles this situation as follows:
• Detects the failure of the C2 node.
• Decides that each interface connecting with C2 went down
because of the failure of C2, and then suppresses the
corresponding incidents.
As a result, the Monitoring Manager reports only the failure of C2 as
the root-cause incident.
16

Netmiko is an open-source library designed to simplify SSH
management across a wide range of network devices from various
vendors including Cisco, Arista, and Juniper Networks
17

DJANGO
FRAMEWORK
• Django is a free and open-source web application framework used
for web development.
30

WEB PAGE
• Homepage
• Network Topology Mapper
• Root Cause Analyzer
31

CONSTRAINTS
38
The DHCP Server and the TFTP/HTTP
Server must be in the same network as
the new one that is getting provisioned.
This method cannot be used for old
routers that doesn’t support Zero Touch
Provisioning.

CONCLUSION
39
The process from initial configuration to error detection which were done
manually have been successfully automated with the help of Python.
And the tool is integrated with Django to create a web UI displaying the
information it learned from the network and displaying the Root Cause in case
of a failure in the network.

FUTURE WORK
40
A ZTP Process with more templates could be used to provision a variety
of devices.
The Network Topology Mapper and Root Cause Analyzer get their data from
the routers using netmiko. NETCONG and YANG could be used to get the
needed data to make the process faster.

REFERENCES
[1] Jürgen Schönwälder, Martin Björklund ,Phil Shafer "Network configuration management using
NETCONF and YANG",October 2010, IEEE Communications Magazine 48(9):166 - 173.
[2] Tarik Taleb , Ibrahim Afolabi, et al,"On Multi-Domain Network Slicing Orchestration Architecture
and Federated Resource Control", IEEE Network ( Volume: 33, Issue: 5, Sept.-Oct. 2019 ).
[3] Yuri Demchenko, Sonja Filiposka, Raimundas, et al, "Enabling Automated Network Services
Provisioning for Cloud-Based Applications Using Zero Touch Provisioning", 2015 IEEE/ACM 8th
International Conference on Utility and Cloud Computing (UCC).
[4] Adnan Hamad, DIngli Yu, J B Gomm, Mahavir S Sangha, “Fault Detection and isolation for engine
under closed-loop control”, Sept 2012, IEEE.
41

THANK YOU L.SAI KUMARESH
17BEC1184
43

Network Auto Configuration and Correction using Python.pptx

More Related Content

Similar to Network Auto Configuration and Correction using Python.pptx (20)

Recently uploaded (20)

Network Auto Configuration and Correction using Python.pptx

Editor's Notes