Hi Experts,

I am very new to openflow protocol. have started to go through the openflow
specification. I have few doubts. I see, there are some reserved ports
supported by the switch.
Those reserved ports have been given below.

1) Are they a logical port or physical port?

2) Reserved port types are ALL/ CONTROLLER/ TABLE/ IN_PORT/ ANY/ LOCAL/
NORMAL/ FLOOD.
     will we mention these types anywhere in the port configuration? I am
really getting confused. where this ALL port type would be mentioned? can
someone clarify ?

3) If you have config in your hand, could you please share ? I just want to
take a look at it.

4) CONTROLLER: The physical port which is connected to the controller would
be configured as "controller port"? what will happen, if i dont configure a
port as controller port even though it has been connected to the controller?



---------------
Required: *ALL:* Represents all ports the switch can use for forwarding a
speci c packet. Can
be used only as an output port. In that case a copy of the packet is sent
to all standard ports,
excluding the packet ingress port and ports that are con gured OFPPC_NO_FWD.

ˆ Required: *CONTROLLER*: Represents the control channel with the OpenFlow
controller. Can
be used as an ingress port or as an output port. When used as an output
port, encapsulate the
packet in a packet-in message and send it using the OpenFlow protocol (see
A.4.1). When used
as an ingress port, this identi es a packet originating from the controller.

ˆ Required: *TABLE*: Represents the start of the OpenFlow pipeline. This
port is only valid in an
output action in the action list of a packet-out message, and submits the
packet to the flowow table
so that the packet can be processed through the regular OpenFlow pipeline.

ˆ Required:* IN PORT*: Represents the packet ingress port. Can be used only
as an output port,
send the packet out through its ingress port.

ˆ Required: *ANY*: Special value used in some OpenFlow commands when no
port is speci ed (i.e.
port is wildcarded). Can neither be used as an ingress port nor as an
output port.

ˆ 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
ow entries it can be used to implement
an in-band controller connection.

ˆ Optional: *NORMAL*: Represents the traditional non-OpenFlow pipeline of
the switch (see 5.1).
Can be used only as an output port and processes the packet using the
normal pipeline. If the
switch cannot forward packets from the OpenFlow pipeline to the normal
pipeline, it must indicate
that it does not support this action.

ˆ Optional: *FLOOD*: Represents
ooding using the normal pipeline of the switch (see 5.1). Can
be used only as an output port, in general will send the packet out all
standard ports, but not to
the ingress port, nor ports that are in OFPPS_BLOCKED state. The switch may
also use the packet
VLAN ID to select which ports to food.

--------------
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Reply via email to