1 | Development of a Diversified Router for Experimental Research in Networking |
---|
2 | |
---|
3 | Jon Turner |
---|
4 | |
---|
5 | |
---|
6 | Overview: The purpose of this project is to develop a diversified |
---|
7 | router platform to enable networking researchers to more easily |
---|
8 | construct experimental networks that explore new and potentially |
---|
9 | disruptive architectural innovations. A diversified network consists |
---|
10 | of a shared infrastructure or substrate, on which multiple |
---|
11 | metanetworks can co-exist. The planned diversified router platform is |
---|
12 | a key building block for such a network, and provides a variety of |
---|
13 | processing resources that can be used to implement diverse |
---|
14 | metarouters. The diversified router substrate enables these resources |
---|
15 | to be configured on behalf of individual metarouters, and provides the |
---|
16 | isolation to allow the metarouters to co-exist, without interference. |
---|
17 | The system architecture is highly scalable and can support metarouters |
---|
18 | with IO capacities ranging from 10 Mb/s to 100 Gb/s. The architecture |
---|
19 | provides great flexibility in the ratio of processing capacity to IO, |
---|
20 | and can support system configurations in which this ratio is an order |
---|
21 | of magnitude larger than in conventional routers. |
---|
22 | |
---|
23 | Deliverables: We plan to implement a prototype of the diversified |
---|
24 | router platform, including the control software to configure and |
---|
25 | manage the various system components, as well as several metarouters |
---|
26 | that demonstrate its operation. The prototype system will be |
---|
27 | constructed from subsystem level components compatible with the |
---|
28 | Advanced Telecommunications Computing Architecture (ATCA). It will |
---|
29 | include both General-purpose Processing Engines (GPE), which run a |
---|
30 | conventional operating system and provide a standard application |
---|
31 | development environment, and Network Processing Engines (NPE) that |
---|
32 | offer substantially higher performance. |
---|
33 | |
---|
34 | Status. Our initial development system consists of a five slot ATCA |
---|
35 | chassis hosting two GPEs (each of these is a dual Xeon server blade) |
---|
36 | and two NPEs (these each have two IXP 2850 network processors), all |
---|
37 | connected through a 10 Gigabit Ethernet switch blade with VLAN |
---|
38 | support, which is used to provide metarouter isolation. We have |
---|
39 | developed software for the NPEs that implements multiple IPv4 |
---|
40 | metarouters, and can be extended to support non-IP metarouters. We |
---|
41 | have also developed the NPE software for a Line Card, which provides |
---|
42 | IO interfaces to external links and traffic isolation among the |
---|
43 | metalinks sharing each interface. |
---|
44 | We are currently in the process of integrating the NPE software |
---|
45 | components and completing the configuration control software. The |
---|
46 | intital version of the system is designed to operate as a Planet Lab |
---|
47 | node, and will use the Planet Lab control software to define user |
---|
48 | slices, implemented as Vservers running in the GPEs. This will be |
---|
49 | augmented by mechanisms that allow users to define a fast-path running |
---|
50 | in the NPEs, that they can control from their Vservers. |
---|
51 | |
---|
52 | Demonstrations. We expect to demonstrate the initial Planet lab |
---|
53 | version of the system by the end of 2006. We plan to follow this up |
---|
54 | with a version of the system that is compatible with VINI. We expect |
---|
55 | to be able to demonstrate a VINI-compatible system in the first half |
---|
56 | of 2007. In addition, we plan to assemble a larger system |
---|
57 | configuration in the first half of 2007 (a 14 slot chassis), to enable |
---|
58 | construction of higher performance metarouters. |
---|
59 | |
---|
60 | Relationship to GENI. The diversified router platform is intended to |
---|
61 | serve as a prototype for the GENI backbone platform. The GENI version |
---|
62 | will require higher level control software that is compatible with |
---|
63 | GENI and will require changes to the NPE software to accommodate |
---|
64 | GENI-specific protocols and packet formats. |
---|