Network Service Provisioning

• The Agile Controller-DCN can interconnect with the mainstream cloud platform OpenStack or third-party applications from Layer 2 to Layer 7. The cloud platform or third-party applications invoke the standard interfaces to provision network services.
• The Agile Controller-DCN can independently (including association with computing platforms) provision network services to implement automatic network deployment.

Fabric Management

• The Agile Controller-DCN uses the standard VXLAN protocol to implement automatic network deployment. The Agile Controller-DCN also supports Layer 2 and Layer 3 VXLAN interconnection and interconnection between VXLAN and traditional networks.
• The Agile Controller-DCN supports various VXLAN networks and can manage and control software and hardware network devices.
• The Agile Controller-DCN also allows hybrid access of multiple types of terminals such as physical servers, VMs, and bare metal servers in different scenarios.

SFC

• The Agile Controller-DCN provides the IETF-based SFC model and adopts PBR or NSH to automatically redirect service traffic to different nodes based on the preconfigured policies for VAS processing. In this way, the topology-independent SFC function with graphical orchestration and automatic configuration is implemented.
• The VAS services provided include the security policy, NAT, and IPSec VPN.

O&M and Fault Location

• The Agile Controller-DCN can monitor physical, logical, and tenant resources.
• The Agile Controller-DCN supports visibility of the application, logical, and physical network topologies. It can also display mappings from the application topology to the logical topology, and from the logical topology to the physical topology.
• The Agile Controller-DCN can detect real forwarding paths and display forwarding paths between VMs and between VTEPs, implementing precise location from the logical network to the physical network.
• The Agile Controller-DCN supports intelligent loop detection and provides one-click repair.
• The Agile Controller-DCN supports detection of Layer 2 or Layer 3 network connectivity between VMs, as well as between VMs and external networks, through IP Ping and MAC Ping, helping administrators quickly rectify faults.
• The Agile Controller-DCN supports traffic mirroring (traffic on VMs or bare metal servers can be mirrored to remote addresses through GRE tunnels).

Openness

• The Agile Controller-DCN is developed based on the ONOS architecture and is compatible with the ODL architecture.
• The Agile Controller-DCN can interconnect with the mainstream OpenStack platforms (standard OpenStack, Red Hat, Mirantis and UnitedStack) using northbound interfaces such as RESTful, RESTCONF, WebService, and Syslog from Layer 2 to Layer 7.
• The Agile Controller-DCN can interconnect with physical and virtual network devices using southbound protocols, such as SNMP, NETCONF, OpenFlow, OVSDB, JSON-RPC, and sFlow.
• The Agile Controller-DCN can interconnect with a computing resource management system, such as VMWare vCenter and Microsoft System Center, to implement collaboration between network and computing resources.

Reliability

• The Agile Controller-DCN can be deployed in a distributed cluster. A single cluster supports a maximum of 128 member nodes. Service control nodes support dynamic expansion without service interruption.
• Cluster members can be deployed in the same Layer 2 network or across a Layer 3 network as long as routes between cluster members are reachable.
• The cluster can load balance the API requests of the cloud platform or web access to different controller nodes.
• The cluster supports southbound load balancing capability. Devices on the entire network are evenly distributed for management by different controller nodes. If a fault occurs on one of the controller nodes, services on the network devices managed by it can be smoothly switched to other normal nodes to avoid service interruption.

Management Capacity and Performance

• Single-node cluster configuration
• Number of managed physical network devices: 600
• Number of managed physical servers: 3, 000
• Number of managed VMs: 60,000
• Typical configuration: three nodes
• Number of managed physical network devices: 1,800
• Number of managed physical servers: 9, 000
• Number of managed VMs: 180,000
• VM online rate: 200 per second
• Typical configuration: five nodes
• Number of managed physical network devices: 3,000
• Number of managed physical servers: 15, 000
• Number of managed VMs: 300,000
• VM online rate: 350 per second