HP OpenFlow 1.3 Administrator Guide Wired Switches K/KA/KB/WB 15.15

Table 1 HP Switch features and interoperability with OpenFlow — by effect on feature or application
(continued)
FeatureEffect
GVRP
LACP
Loop Protect
sFlow
UDLD
STP loop guardOpenFlow does not affect this feature
7
BPDU guard
MSTP
RSTP
STP
PVST
1
These authentication features still function in an OpenFlow instance and ports of an OpenFlow instance. The security
features take a first look at the packet before sending the packets to OpenFlow.
2
Any ACL entry that sets a drop bit in hardware (TCAM) would always win over the TCAM entry to copy OpenFlow traffic
to the controller such that packets on an OpenFlow instance could get dropped in hardware due to an ACL entry and
an OpenFlow controller would never be able to see those packets.
3
Rate Limiting may be applied to limit OpenFlow traffic as well as other traffic. OpenFlow uses a form of rate-limiter to
limit the OpenFlow traffic that gets to the CPU and to the controller.
4
Enabling Meshing can break the distinction between OpenFlow VLANs and non-OpenFlow VLANs.
5
The OpenFlow controller could set up a flow to match a protocol header and an action to drop the matching packets.
This could lead to the protocol’s packets never making it to the protocol handling code in the software data path
causing the protocol to break on the OpenFlow instance.
•
• The OpenFlow controller could set up a flow to match a protocol header and a NORMAL action in software for the
matching packets. In such a case, the protocol’s packets are removed by OpenFlow in the software data path but
reintroduced after examining the software flow table. Though this action may not break the protocol, it introduces an
additional latency before the protocol running on the switch gets the protocol’s packets.
6
Protocol packets are not sent through the OpenFlow software data path.
7
Port up or down events are sent to the controller to keep the controller aware of available ports on the switch. OpenFlow
cannot override STP, RSTP, or MSTP decisions.
Scalability
Table 2 Switch modules scalability
K/KA.15.14, WB.15.14K/KA.15.10Switch/Modules
Compatible mode – “allow v1 modules” – A chassis where v1 as well as v2 modules are present may execute in this
mode. Non-compatible mode – “no allow v1 modules” – A chassis that only has v2 modules may execute in this mode.
Total: 64 KTotal: 64 K8200/5400 v1 modules 3500 series
6600 series 6200 series
Hardware: Standard match mode
TCAM – 1.5 K per module
Hardware: TCAM – 1.5K per module
Software: Total minus HardwareSoftware: Total minus Hardware
Total: 64 KTotal: 64 K8200/5400 v2modules 3800 series
2920 series (Flow numbers will be
lower for this series)
16 K for 292016 K for 2920
Scalability 13