Creating HP Software-defined Networks

The minimum number of team members for an HP VAN SDN Controller team is three.

References:
HP VAN SDN Controller Installation Guide

{base uri}/{api}
This is an unauthenticated API
Use https not http.
Example:
https://15.255.121.2:8443/api

Response codes
- Normal: OK (200)
- Error: Not Found (404), Service Unavailable (503) Reference: HP VAN SDN Controller 2.2 REST AP

* The HP VAN controller supports the following:
Versions 1.0 and 1.3 of OpenFlow on HPN ProVision and Comware switches

* Openflow 1.3.1: Support for multiple flow tables is introduced

References:
Open Flow 1.3.1 Support: Controller View

Once a team is configured, the configuration and monitoring of team members and their associated OpenFlow switches is performed by the team manager. If the team manager goes down, the controller with the next highest priority in the team configuration becomes the team manager.

Note: Team Management
Each controller belonging to a team is a team member. To centralize team management and control, one controller is designated as the team manager. Teaming is configured on one controller and is automatically propagated to the other controllers in the team, regardless of which controller becomes the team manager.

References:
HP VAN SDN Controller Administrator Guide

The forwarding table is delivered to the data plane by the management plane as part of the device operating system. Thus when an Ethernet frame arrives on the switch interface, the data plane then forwards it to output port.

Note: OpenFlow defines a standard for sending flow rules to network devices so that the Control Plane can add them to the forwarding table for the Data Plane.

Incorrect:
Not A: The control plane will use the routing table to build the forwarding table used by data plane.
Not C: The Management Plane handles functions such device management, firmware updates, SNMP and external configuration via the CLI.

References:
OpenFlow and Software Defined Networking: Is it Routing or Switching ?

* Northbound API Relative to figure 1 below, the Northbound API is the API that enables communications between the control layer and the application layer (external business applications.

Southbound API
Relative to Figure 1 below, the Southbound API is the API that enables communications between the control layer and the infrastructure layer (OpenFlow).

Figure 1. ONF's SDN architecture

* Putting the region configurations in place in a controller team ensures seamless failover and failback among the configured controllers for the specified network devices in a region. That is, when a master controller experiences a fault, the Role Orchestration Service ensures that a slave controller immediately assumes the master role over the group of network devices to which the failed controller was in the master role.

References:
Technical white paper, Mock RFI for Enterprise SDN Solutions Reference: HP VAN SDN
Controller Administrator Guide

Incorrect:
Not A: Southbound API is not used by external Applications.
Not B:
Topology service to create a network graph and compute the shortest path between two hosts.
Not C:

The link discovery service is responsible for discovering and maintaining the status of links in the OpenFlow network. The link discovery would record Mac Addresses, not IP addresses.

* Northbound API Relative to figure 1 below, the Northbound API is the API that enables communications between the control layer and the application layer (external business applications.
Southbound API
Relative to Figure 1 below, the Southbound API is the API that enables communications between the control layer and the infrastructure layer (OpenFlow).

Figure 1. ONF's SDN architecture

* Putting the region configurations in place in a controller team ensures seamless failover and failback among the configured controllers for the specified network devices in a region. That is, when a master controller experiences a fault, the Role Orchestration Service ensures that a slave controller immediately assumes the master role over the group of network devices to which the failed controller was in the master role.
References:
Technical white paper, Mock RFI for Enterprise SDN Solutions Reference: HP VAN SDN
Controller Administrator Guide
Note:
* The exhibit shows that the IPv4 source address, 10.10.10.0 is a private network. The exhibit shows that
the IPv4 destination address, 192.168.56.0 is also a private network.
* display openflow instance instance-id flow-table [ table-id ] Display flow table entries for an OpenFlow
instance.

Path Diagnostics
Determines and verifies the path taken by a specific packet from a source host to destination host.
Evaluates flows configured across the switches in the control domain for diagnosis Creates `Observation posts' on every switch in the path that the packet would take
Tallys packet_ins from the observation posts to figure out where a path is broken Lists neighbors for any given device

References:
HP VAN SDN Controller Administrator Guide

Flow Management:
* Delivers History Flow Entry records flow entry used before to help administrators audit flow policy change
* Displays the list of all current Flow entry in OF network, including Match Field, Instruction and other
statistics.
* Shows detailed flow service information and flow traffic and trend in flow entry detail page
* Provides shortcut to locate flow to topology show device and link status

References:
HP IMC Virtual Application Networks Software-defined Networking Manager Software

Note: TopologyViewer
Creates and updates a network graph for visualizing the network the controller discovers. The Topology Viewer uses the services of the Topology Manager and Link Manager.