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
<family>ProCurve 3800</family>
<product>3800</product>
</type>
<type name="J9573A" extends="3800" description="3800-24G-PoE+-2SFP+">
<oid>.1.3.6.1.4.1.11.2.3.7.11.119</oid>
<model>J9573A</model>
<product>3800-24G-PoE+-2SFP+ Switch</product>
</type>
. . . . . . .
</deviceDriver>
Component Responsibilities
The following figure illustrates the components that make up the Device Driver Framework.
Device Type XML Files: The XML files contain information describing the attributes and
supported Facets for a device type.
Device Driver Manager: The Device Driver Manager loads the information from the XML files
and creates an in-memory representation of the Device Type information. The Device Driver
Manager assists Discovery components to determine the best Device Type for discovered devices.
Device Discovery: The figure illustrates that there can be many discovery components. The
OpenFlow (OF) discovery component is shown in the figure. OF Device Discovery will be notified
by the Controller Service when an OpenFlow device connects to the controller. OF Device
Discovery is then responsible to determine the type of device based on information provided in the
OpenFlow handshake and the XML information maintained by the Device Driver Manager. A
117