Reference Guide
Table Of Contents
- 1 Introduction
- 2 Establishing Your Test and Development Environments
- 3 Developing Applications
- Introduction
- Authentication
- REST API
- Audit Logging
- Alert Logging
- Configuration
- High Availability
- OpenFlow
- Metrics Framework
- GUI
- SKI Framework - Overview
- SKI Framework - Navigation Tree
- SKI Framework - Hash Navigation
- SKI Framework - View Life-Cycle
- SKI Framework - Live Reference Application
- UI Extension
- Introduction
- Controller Teaming
- Distributed Coordination Service
- Persistence
- Backup and Restore
- Device Driver Framework
- 4 Application Security
- 5 Including Debian Packages with Applications
- 6 Sample Application
- Application Description
- Creating Application Development Workspace
- Application Generator (Automatic Workspace Creation)
- Creating Eclipse Projects
- Updating Project Dependencies
- Building the Application
- Installing the Application
- Application Code
- 7 Testing Applications
- 8 Built-In Applications
- Appendix A
- Appendix B
- Bibliography
ControllerManager configuration has hybrid.mode=false, all packets are implicitly stolen to the
controller and processed by OpenFlow Node Discovery.
Based upon the information supplied by these copied ARP, DHCP, and IP packets the OpenFlow
Node Discovery application will register as a node supplier and supply updates to the node table.
The timeout value for nodes discovered by each protocol is configurable, as shown in T a b l e 11.
Table 11 Node Timeout
Protocol
Timeout
Configuration
Default Value
ARP
arp.age
OfArpDiscoveryComponent
5 minutes
DHCP
dhcp.age
OfDhcpDiscoveryComponent
24 hours
IP
Ip.age
OfIpDiscoveryComponent
20 minutes
Node Manager will not update the node table for every PACKET_IN message it receives.
Specifically, PACKET_IN messages are ignored if the connected port is identified as being part of
the infrastructure by the Topology module.
Note that since these PACKET_IN messages represent copies of packets which have already been
forwarded by the controlled device, no corresponding PACKET_OUT will be sent back to the
device which sent the PACKET_IN.
Link Manager
The Link network service component is responsible for creating and maintaining the infrastructure
link table. Each infrastructure link is uniquely identified by source connection point and destination
connection point. The data stored for each link includes the link type, which may be direct, multi-
hop, or tunnel. A direct link represents a non-switched connection between two controlled devices.
A multi-hop link represents a switched connection between two controlled devices, where the
connection spans one or more uncontrolled switches. A tunnel link represents a configured tunnel
between two devices.
The Link table sample data is shown in Tab l e 12.
Table 12 Link Table
Source Device Source
Port
Destination Device Destination Port
03:e7:00:26:f1:29:af:00 1 03:e7:00:23:47:ba:05:40 23
03:e8:00:23:47:ba:05:40 11 03:e8:00:26:f1:29:af:00 8
Link Manager publishes the com.hp.sdn.link.LinkService API via OSGI declarative services and
REST API. These APIs allow callers to perform queries against the link table.
Link Manager also publishes the com.hp.sdn.supplier.LinkSuppliersBroker, which allows callers to
register themselves as a supplier of link-related information, using an instance of
com.hp.sdn.link.LinkSupplierService. See Javadoc on page 9 for details.
239