Configuring egress-only ports
This CLI command enables or disables support for advertising egress-only ports to the controller. Ports that are members of non-OpenFlow VLANs are egress-only ports. A controller can add a flow with an egress-only port as an output port to allow traffic to be forwarded from an OpenFlow VLAN to a non-OpenFlow VLAN. All instance member ports and egress-only ports are exposed as instance ports to the controller.
Syntax
openflow egress-only-ports
Ports that are members of non-OpenFlow VLANs are egress-only ports. A controller can add a flow with an egress-only port as an output port to enable traffic to be forwarded from an OpenFlow VLAN to a non-OpenFlow VLAN.
Egress-only ports cannot be used as an “in-port” in any flow by a controller. If this usage is attempted, the flow addition fails and an error message is returned to the controller.
Example
switch(openflow)# show openflow instance test Configured OF Version : 1.3 only Negotiated OF Version : 1.3 Instance Name : test Data-path Description : test Administrator Status : Enabled Member List : VLAN 3 Pipeline Model : Standard Match Listen Port : 6633 Operational Status : Up Operational Status Reason : NA Datapath ID : 000340a8f09e8600 Mode : Active Flow Location : Hardware and Software No. of Hardware Flows : 6 No. of Software Flows : 4 Hardware Rate Limit : 0 kbps Software Rate Limit : 100 pps Conn. Interrupt Mode : Fail-Secure Maximum Backoff Interval : 60 seconds Probe Interval : 10 seconds Hardware Table Miss Count : NA No. of Software Flow Tables : 1 Egress Only Ports : None Table Model : Policy Engine and Software Source MAC Group Table : Disabled Destination MAC Group Table : Disabled Controller Id Connection Status Connection State Secure Role ------------- ----------------- ---------------- ------ ------ 1 Connected Active No Slave 2 Connected Active No Master
When the Egress-Only Ports option is enabled for OpenFlow on the switch, the Port-Mod message for an egress-only port results in an error.