Network Auto Configuration and Correction using Python.pptx

- Implemented Zero Touch Provisioning, Network Topology Mapper, and Root Cause Analysis using Python, GNS3, Netmiko, SSH, OSPF, and Graphviz.
- Developed a Python script to automate network discovery based on Core Router IP and login details, significantly reducing manual intervention.
- Enhanced network visualization by generating detailed network graphs, aiding in quick network analysis and troubleshooting.

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

2. motivation Eliminate manual tasks Reduce errors Simplify Network Management Optimize Performance Gain network visibility 2

3. objective Implementation of Zero Touch Provisioning(ZTP) Root Cause Analysis (RCA) 3

4. Software details Cisco Router Images (csr1000v, c3725) Netmiko Python GNS3 Ubuntu Linux Graphviz 4

5. Codes and standards 5

6. 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

7. 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

8. 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

9. 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

10. Network topology CSR1000V -  New device to be provisioned C3725 - DHCP Server Network Automation - TFTP Server containing the Python script 10

11. DHCP server config Network – 192.168.0.0/24 TFTP Server Address – 192.168.0.2 File Name – ztp_trial.py 11

12. Tftp server configuration 12

13. Python Script 13

14. 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

15. Example If the Router03 node goes down, there is no response from other interfaces and IP addresses that Router03 has. A large number of failure events occurs. The Monitoring Manager decides that the lack of responses from IP addresses was caused by the interface failures, and then suppresses the corresponding incidents. 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. The Router03 node going down is reported as the root-cause incident. 15

16. 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

17. 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

18. SSH 18

19. OSPF Routing 19

20. Routing table 20

21. Ip interfaces 21

22. Network topology 22

23. 23

24. 24

25. Graph 25

26. Core router 26

27. Core router 27

28. 28 Level 2 Router

29. 2 individual routers 29

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

31. Web Page Homepage Network Topology Mapper Root Cause Analyzer 31

32. Topology Used 32

33. 33

34. 34

35. 35

36. 36

37. Demo Video 37

38. Constraints 38

39. Conclusion 39

40. FUTURE WORK 40

41. 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

42. 42

43. Thank you L.SAI KUMARESH 17BEC1184 43