MAC-IP flow table restrictions
Controller must follow the restrictions in Table 5 and Table 6 to deploy flow entries for MAC-IP flow table. Otherwise, forwarding failure might occur.
Table 5: Restrictions for deploying Layer 2 flow entries for the MAC-IP flow table
Items | Restrictions |
|---|---|
Match fields | The destination MAC address cannot be MAC address of the switch to which the flow entry is deployed. |
Actions | The output port must belong to the VLAN that is matched. |
Table 6: Restrictions for deploying Layer 3 flow entries for the MAC-IP flow table
Items | Restrictions |
|---|---|
Match fields | The VLAN interface of the VLAN that is matched is in UP state. The destination MAC address cannot be MAC address of the switch to which the flow entry is deployed. The destination IP address cannot be the IP address of the switch to which the flow entry is deployed. |
Actions | The specified output port must belong to the destination VLAN. The destination MAC address cannot be MAC address of the switch to which the flow entry is deployed. If the switch modifies the source MAC address, the source MAC address must be the MAC address of the VLAN interface of the VLAN to which the output port belongs. |
To deploy a Layer 3 flow entry, make sure the following requirements are met:
The VLAN interface of the matched VLAN is in up state.
The switch sends the controller a packet that indicates the VLAN interface acts as an OpenFlow port. The link state and the MAC address of the VLAN interface are also included in the packet.
The switch reports the VLAN interface deletion to the controller and the controller removes the corresponding Layer 3 flow entry.
The controller ensures the correctness of Layer 3 flow entries. The switch does not check for the restrictions for Lay 3 flow entries.