Opened 10 years ago

Last modified 10 years ago

#1253 closed

ARCCN VERifying MONiTor for SDN (VERMONT) — at Version 1

Reported by: hdempsey@bbn.com Owned by: peter.stickney@bbn.com
Priority: major Milestone:
Component: GPO Version: SPIRAL6
Keywords: GEC20 Cc: VAntonenko@arccn.ru
Dependencies:

Description (last modified by hdempsey@bbn.com)

Demo description paragraph (three sentence minimum):

ARCCN demo for Chermeritsky.

One of the aims of network engineering is to configure forwarding rules of the switches as to guarantee network compliance with the Packet Forwarding Policies (PFP). VERMONT is a software toolset that provides some automation to the solution of this task by checking consistency of OpenFlow rule tables with formally specified invariants of PFP.

VERMONT can be installed in line with the control plane to observe state changes of a network by intercepting messages sent by switches to the controller and commands sent by the controller to switches. It builds an adequate formal model of a whole network and checks every event, such as installation, deletion, or modification of rules, port and switch up and down events, against the requirements of PFP. Before a network update command is sent to a switch VERMONT checks in advance the result of its execution. If a new state of network satisfies all requirements of PFP then the command is delivered to the corresponding switch. Upon detecting a violation of PFP VERMONT blocks the update command, alerts a network administrator, and gives some additional information to discover a possible source of an error.

VERMONT has a wide area of applications. It can be attached to a SDN controller (or a bunch of controllers) to enforce basic safety properties (the absence of loops, blackholes, etc) of the subordinate flow-tables in data plane. VERMONT may be also used as a fully automatic safeguard (and, in a sense, a debugger) for any software application implementing certain PFP on a SDN controller. This properties make VERMONT a desired tool for network administrators and control application developers.

List of equipment that will need AC connections (e.g. laptop, switch, monitor):

2 (unknown equipment)

Just put in the number of connections needed if your demo description already lists equipment.

Total number of wired network connections (sum standard IP and VLAN connections):

Number of wired layer 2 VLANs (if any): Specify VLAN number, if known, approximate bandwidth, and whether tagged or untagged.

Number of wireless network connections (include required bandwidth if significant):

1

Number of static addresses needed (if any):

Monitor (y/n, specify VGA or DVI):

1

Specify resolution only if your software has resolution restrictions.

Number of posters (max size poster boards are 30" x 40"):

1

Special requests: Include any specific network connectivity needs (e.g. VLANs to a particular GENI location, projects you'd like to be near, etc.)

Change History (1)

comment:1 Changed 10 years ago by hdempsey@bbn.com

Description: modified (diff)
Note: See TracTickets for help on using tickets.