H3C Technologies H3C S12500 Series Switches - Manual (Page 23)

16
Packets without a VLAN tag
If a Packet-out packet haves no VLAN tag, the switch processes the packet as follows:
• If the ingress port is a physical or logical port, the switch tags the packet with the PVID of the ingress
port and forwards the packet within the VLAN.
• If the ingress port is a reserved port and the output port is a physical or logical port, the switch tags
the packet with the PVID of the output port and forwards the packet within the VLAN.
• If the ingress port is a reserved port and the output port is the Flood or All reserved port, the switch
processes the packet as described in "
Output port ."
Output port
If the output port of a Packet-out packet is the Flood or All reserved port, the switch processes the packet
as follows:
• When the output port is the Flood reserved port:
{
If the Packet-out packet has a VLAN tag, the switch broadcasts the packet within the VLAN.
{
If the Packet-out packet has no VLAN tag and the ingress port is a physical or logical port, the
switch tags the packet with the PVID of the ingress port. The switch then forwards the packet
within the VLAN.
{
If the Packet-out packet has no VLAN tag and the ingress port is the Controller reserved port, the
switch forwards the packet out all OpenFlow ports.
• When the output port is the All reserved port:
{
If the Packet-out packet has a VLAN tag, the switch broadcasts the packet within the VLAN.
{
If the Packet-out packet has no VLAN tag, the switch forwards the packet out of all OpenFlow
ports regardless of the ingress port type.
Packet-in messages restrictions
Processing VLAN tags
When sending a packet in a packet-in message to the controller, the switch processes the VLAN tag of
the packet as follows:
• If the VLAN tag of the packet is the same as the PVID of the ingress port, the switch removes the
VLAN tag.
• If the VLAN tag of the packet is different from the PVID of the ingress port, the switch does not
remove the VLAN tag.
Packet buffer
If a packet-in message is sent to controller due to no matching flow entry, the switch supports buffering
the packet. The buffer size is 1K packets.
If a packet-in message is sent to controller for other reasons, the switch does not support buffering the
packet. The switch must send the full packet to the controller, and the cookie field of the packet is set to
0xFFFFFFFFFFFFFFFF.