1 / 6

Automatic network configuration: Position presentation

Automatic network configuration: Position presentation. Cristel Pelsser WODNAFO, Feb. 2010. Objectives of automatic network configuration. Reduce configuration errors Speed-up configuration changes Improve response time in case of unexpected events. What are we looking for?.

yepa
Download Presentation

Automatic network configuration: Position presentation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Automatic network configuration:Position presentation Cristel Pelsser WODNAFO, Feb. 2010

  2. Objectives of automatic network configuration • Reduce configuration errors • Speed-up configuration changes • Improve response time in case of unexpected events

  3. What are we looking for? • A high level language/representation of a network • Should be able to verify a set of network properties (avoid errors) • Should be innovation friendly • Should be easily readable/modifiable for fast problem resolution

  4. How to reach that goal? • Model network concepts with entity-relationship model • Automatic generation of a matching database • Population of the database • from current configuration or simple GUI • Associate router vendor configuration code for each entity andrelation • Deal with different router configuration syntax !?! • Provide high level vendor independent API for router configuration • Follow the relations and configure elements as you go Evolvable

  5. Need to agree on routing functionalities • Adjacencies (IP addresses) • Link weight assignment • With/without IP FRR, TE, … • eBGPsessions • BGP policies • Customer-provider, peer-peer, backup, blackhole… other interesting policies (Tim?) • iBGPtopology configuration (RR, iBGP sessions) • Choice of design algorithm • Outgoing TE • % of traffic on each inter-AS link with accepted deviation • Incoming TE? • …

  6. Required features • Changes tracking • Roll back • Transaction based update of a network device • Automatic generation of network configuration documentation • Javadoc style • Graphical representation • Network monitoring and failure reporting • Alerts and network status visualization • Debugging • Check points (across layers), similar to breakpoints in programming languages • Correctness check of configuration (before committing) • Emulate, simulate, deploy and test on virtual infrastructure (Shadow VNets, A. Wundsam, A. Mehmood, A. Feldmann et al.), static check? Cost?

More Related