Next: , Previous: Configuring Frr as a Route Server, Up: Top


12 VNC and VNC-GW

This chapter describes how to use Virtual Network Control (VNC) services, including Network Virtualization Authority (NVA) and VNC Gateway (VNC-GW) functions. Background information on NVAs, Network Virtualization Edges (NVEs), underlay networks (UNs), and virtual networks (VNs) is available from the IETF Network Virtualization Overlays (NVO3) Working Group. VNC Gateways (VNC-GWs) support the import/export of routing information between VNC and customer edge routers (CEs) operating within a VN. Both IP/Layer 3 (L3) VNs, and IP with Ethernet/Layer 2 (L2) VNs are supported.

BGP, with IP VPNs and Tunnel Encapsulation, is used to distribute VN information between NVAs. BGP based IP VPN support is defined in RFC4364, BGP/MPLS IP Virtual Private Networks (VPNs), and RFC4659, BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN . Both the Encapsulation Subsequent Address Family Identifier (SAFI) and the Tunnel Encapsulation Attribute, RFC5512, The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute, are supported.

The protocol that is used to communicate routing and Ethernet / Layer 2 (L2) forwarding information between NVAs and NVEs is referred to as the Remote Forwarder Protocol (RFP). OpenFlow is an example RFP. Specific RFP implementations may choose to implement either a hard-state or soft-state prefix and address registration model. To support a soft-state refresh model, a lifetime in seconds is associated with all registrations and responses.

The chapter also provides sample configurations for basic example scenarios.