
3.
Click
Modify
.
The
Modify Basic Configuration
dialog box is displayed for the
com.hp.sdn.ctl.of.impl.TraceManager
component.
4.
Change the value for the
record.duration
key.
5.
Click
Apply
to set the new time span for active trace recording, and return to the OpenFlow
Trace
screen.
Figure 43 The TraceManager Configuration Component Controls the OpenFlow trace
interval
OpenFlow Classes
The OpenFlow Classes screen shows the OpenFlow classes that applications have registered
with the controller.
About OpenFlow classes
When multiple applications share the same resource the flow tables of OpenFlow switches how
can their priorities relative to each other be determined and how can their actions be coordinated?
If flow table modification priorities are directly coded into each application, applications can end
up directly competing with other applications for the highest priorities, which can result in conflicts
in general network traffic control and unintended results when you implement a solution that has
multiple SDN applications attempting to act on the same packets. In addition, many environments
make it difficult to trace the origin of flow modification requests installed in switches.
The HPE VAN SDN Controller uses OpenFlow classes to dynamically manage the priorities of
the OpenFlow rules being deployed to the network, thus enabling applications to execute their
business logic in a more orderly fashion.
1.
For each class of flow modification message the application can send, the application must
register an OpenFlow class with the controller. The OpenFlow class must specify the types
of match fields, types of actions, and (optionally) the relative position (higher than or lower
than) for this class with respect to other flow classes.
2.
The controller adds a unique base cookie to be used with each future flow modification to
be validated against this OpenFlow class, and assigns an actual priority for the OpenFlow
class. This actual priority is based on the logical priorities of all of the OpenFlow classes of
all the applications that are registered with the controller.
3.
When the application sends a flow modification message, it must set the match and action
to be the same fields as specified in the OpenFlow class and, instead of providing an actual
OpenFlow Classes
75