@[TOC
实例
[cbis-admin@overcloud–13 (overcloudrc) ~]$ sudo ovs-appctl dpif/show
system@ovs-system: hit:75198007884 missed:109924265
br-ex:
br-ex 65534/3: (internal) ,65534 是port number; OpenFlow port number； 3 是 ofp_port_to_odp_port(ofproto, ofport->ofp_port); 转换为odp port，open datapath port number；internal是内部类型
/* Type of netdevs in this class, e.g. "system", "tap", "gre", etc.
* One of the providers should supply a "system" type, since this is
* the type assumed if no type is specified when opening a netdev.
* The "system" type corresponds to an existing network device on the system. */
const char *type;
infra-bond 1/4: (system)
phy-br-ex 6/none: (patch: peer=int-br-ex)
vlan500 2/5: (internal)
vlan804 3/6: (internal)
vlan810 4/7: (internal)
vlan812 5/8: (internal)
保留端口
65534 这个是 local port
Open vSwitch also supports the following standard OpenFlow port names (even in contexts where port names are not otherwise supported). The corresponding OpenFlow 1.0 and 1.1+ port numbers are listed alongside them but should not be used in flow syntax:
- ``in_port`` (65528 or 0xfff8; 0xfffffff8)
- ``table`` (65529 or 0xfff9; 0xfffffff9)
- ``normal`` (65530 or 0xfffa; 0xfffffffa)
- ``flood`` (65531 or 0xfffb; 0xfffffffb)
- ``all`` (65532 or 0xfffc; 0xfffffffc)
- ``controller`` (65533 or 0xfffd; 0xfffffffd)
- ``local`` (65534 or 0xfffe; 0xfffffffe)
- ``any`` or ``none`` (65535 or 0xffff; 0xffffffff)
- ``unset`` (not in OpenFlow 1.0; 0xfffffff7)
这些个特殊的port在openflow的说明里有说明，也叫保留端口
4.5 Reserved Ports
The OpenFlow reserved ports are de ned by this speci cation. They specify generic forwarding actions such as sending to the controller,
fooding, or forwarding using non-OpenFlow methods, such as “normal” switch processing.
A switch is not required to support all reserved ports, just those marked “Required" below.
Optional: LOCAL: Represents the switch’s local networking stack and its management stack. Can be used as an ingress port or as an output port. The local port enables remote entities to interact with the switch and its network services via the OpenFlow network, rather than via a separate control network. With a suitable set of default fow entries it can be used to implement an in-band controller connection.