Hybrid OF Ports on Allied Telsis Switches

[Osama Abu Hamdan]

Greetings,

I have an Allied Telesis AT-IE340-20GP switch.

I want to make port (12 for example) a hybrid port.

With hybrid I mean it should be able to forward packets when communicating with a non-OpenFlow port (Layer 2 packet forwarding) and when communicating with an OpenFlow port (with OpenFlow rules). 

AT  guidance Link: https://www.alliedtelesis.com/sites/default/files/documents/configuration-guides/openflow_feature_overview_guide.pdf

I am following the steps in the Allied Telesis Configuration guidance applying these commands to interface port1.0.12:

1- interface port1.0.12
2- switchport mode trunk ingress-filter disable

3-switchport trunk allowed vlan add 1,10
4-openflow

On these configs, packets are being forwarded with openflow ports but not with non-openflow ports.

When I apply

```

no openflow

switchport trunk native vlan 1

```

I am able to communicate with non-openflow ports (from port 12).

Here are the switch configs

awplus#show openflow config

11679ed7-6446-4965-b995-e1c04464796b

Bridge of0

Controller "tcp:10.0.1.70:6653"

is_connected: true

other_config: {aux_id="0", name=con1}

fail_mode: secure

datapath_type: system

Port of0

Interface of0

type: internal

Port port1.0.7

Interface port1.0.7

type: system

options: {ifindex="5007", mtu="1500", native_vlan="4089"}

Port port1.0.8

Interface port1.0.8

type: system

options: {ifindex="5008", mtu="1500", native_vlan="4089"}

Port port1.0.9

Interface port1.0.9

type: system

options: {ifindex="5009", mtu="1500", native_vlan="4089"}

Port port1.0.10

Interface port1.0.10

type: system

options: {ifindex="5010", mtu="1500", native_vlan="4089"}

Port port1.0.11

Interface port1.0.11

type: system

options: {ifindex="5011", mtu="1500", native_vlan="4089"}

Port port1.0.12

Interface port1.0.12

type: system

options: {ifindex="5012", mtu="1500", native_vlan="4089"}

----------------------------------------------------------

awplus#show vlan all

VLAN ID Name Type State Member ports

(u)-Untagged, (t)-Tagged

======= ================ ======= ======= ====================================

1 default STATIC ACTIVE port1.0.1(u) port1.0.2(u) port1.0.3(u)

port1.0.4(u) port1.0.5(u) port1.0.6(u)

port1.0.13(u) port1.0.14(u)

port1.0.15(u) port1.0.16(u)

port1.0.17(u) port1.0.18(u)

port1.0.19(u) port1.0.20(u)

4089 VLAN4089 STATIC ACTIVE port1.0.7(u) port1.0.8(u) port1.0.9(u)

port1.0.10(u) port1.0.11(u)

port1.0.12(u)

Any thoughts?

[Tony van der Peet]

Just to clarify, the hybrid port works by allowing certain VLANs, identified by VLAN tag, to be treated as normal switched traffic. So in your example above, VLANs 1 and 10 will be treated this way.

Untagged traffic or traffic tagged with a VLAN that is not 1 or 10, will be treated as OpenFlow traffic.

You will need to ensure that traffic on VLANs 1 and 10 is tagged entering the switch.

Is the "normal" traffic intended to terminate on the switch, or is the switch just a transit node? There are possibly a number of other configuration items that will need to be checked.

Please continue this conversation, and we will try to get you operating as required.

Tony