Enterprise GENI

1. Innovate In Your Network Goals GENI on Enterprise Networks Building Blocks Enterprise GENI • Encourage innovation in local enterprise networks, not just the backbone • Allow production traffic and research experiments to safely co-exist on the same hardware • Develop Enterprise GENI kit (phase 1) and deploy at other institutions (phase 2) • Rich, complex network environments despite locality • Experimenters experience more immediate results affecting their own traffic: better incentive for deployment • Single administrative domain allows for better control of deployment • A base-case for convincing operators, vendors, providers that GENI is useful/stable/deployable • OpenFlow networks centralize control • OpenFlow Hypervisor virtualizes OpenFlow networks • Aggregation Manager manages virtual OpenFlow networks and instantiates slices/slivers • Enterprise GENI clearinghouse performs resource discovery, access control, and resource assignment Phase 1: Enterprise GENI@Stanford Phase 2: Dissemination GENI Clearing House OpenFlow Hypervisor Aggregation Manager • Specialized OpenFlow controller that virtualizes OpenFlow networks • Each virtual OpenFlow network (VON) is controlled by a VON controller • Each experimenter creates a VON and runs their own VON controller • Hypervisor routes OpenFlow updates to the appropriate VON controller and prevents controllers from affecting each other’s traffic • Red VC controls red traffic, green VC, green traffic, etc. OpenFlow Switches OpenFlow Hypervisor • Separates control from data path • Each switch has a Flow Table and talks to a shared OpenFlow controller • Flow Table entry decides packet forwarding • OpenFlow controller is responsible for maintaining/editing the flow table of each switch VON Controller Initial deployment include: Stanford, Princeton, Deutsche Telekom Labs in Berlin, and NEC Labs in Tokyo