WB 15.15

.... .... .... .... .... ..0. .... .... = Auto-negotiation support: No (0)

.... .... .... .... .... .0.. .... .... = Pause support: No (0)

.... .... .... .... .... 0... .... .... = Asymmetric pause support: No (0)

Pad: 0

Example

Send a Port-Mod command to the switch using dpctl, a controller utility.

root@openflow-ubuntu-10:/home/openflow# dpctltcp:10.20.30.50:6633 port-desc

... {no="6", hw_addr="00:1b:3f:cf:76:fa", name="A6", config="0x0", state="0x1",

curr="0x0", adv="0x0", supp="0x0", peer="0x0", curr_spd="100000000kbps",

max_spd="100000000kbps"} ...

root@openflow-ubuntu-10:/home/openflow# dpctltcp:10.20.30.50:6633 port-mod

port=6,addr=00:1b:3f:cf:76:fa,conf=0x40,mask=0x40

SENDING:

port_mod{port="6", hwaddr="00:1b:3f:cf:76:fa", config="0x00000040",

mask="0x40", adv="0x0"}

root@openflow-ubuntu-10:/home/openflow# dpctltcp:10.20.30.50:6633 port-desc

... {no="6", hw_addr="00:1b:3f:cf:76:fa", name="A6", config="0x40",

state="0x1", curr="0x0", adv="0x0", supp="0x0", peer="0x0",

curr_spd="100000000kbps", max_spd="100000000kbps"} ...

Port modification and OpenFlow versions

OFP_PORT_CONFIG, OFPPC_NO_FLOOD and OFPPC_NO_PACKET_IN are supported by an

OpenFlow 1.0 instance on the switch.

OFP_NO_FLOOD and OFPPC_NO_PACKET_IN are supported by an OpenFlow v1.3 instance

on the switch.

NOTE: If a port is not exclusive to the Openflow Member VLAN, a Port Modification message

from the controller will result in an error returned to the controller.

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

egress-only-ports

Enable or disable 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 enable traffic to be

forwarded from an OpenFlow VLAN to a non-OpenFlow VLAN.

NOTE: Egress-only ports cannot be used as an “in-port” in any flow by a controller. If this is

attempted an error message will be returned and the flow addition will fail.

28 Configuring OpenFlow