Connectivity between two untagged hosts

(Ports are configured as vlan-untagged)

Connectivity between two tagged hosts

(Ports are configured as vlan-tagged)

Connectivity between two untagged hosts

(Ports are configured as vlan-native with vlan-tagged)

Connectivity between two untagged hosts

(Ports are configured as vlan-native with vlan-tagged,

and vlan-untagged)

All pings succeed

Connectivity between untagged host and tagged host

(Ports are configured as vlan-untagged and

vlan-tagged with same vlan id, respectively)

Connectivity between two untagged hosts with different vlan id

(Ports are configured as vlan-untagged 10 and 20, respectively)

Connectivity between two tagged hosts with different vlan id

(Ports are configured as vlan-tagged 10 and 20, respectively)

Connectivity between untagged and tagged hosts with different vlan id

(Ports are configured as vlan-untagged 10 and

vlan-tagged 20, respectively)

IPv4 pingall between all the hosts in the topology.

(All routing tests also check IP address assignment to hosts and specific number of flows and groups in the switches)

For all routing tests:

 All pings succeed; Host IP addresses are expected; Flow/group numbers are expected

IPv6 pingall between all the hosts in the topology.

All IPv4 hosts ping each other and all IPv6 hosts ping each other.

IPv4 pingall between all the hosts in the topology.

IPv4 ping from internal hosts to external hosts.

IPv6 pingall between all the hosts in the topology.

IPv6 ping from internal hosts to external hosts.

All IPv4 hosts ping each other and all IPv6 hosts ping each other.

IPv4 and IPv6 ping from internal hosts to external hosts.

Implemented

Kill and recover links.

Ping between all ipv4 hosts in the topology.

Kill and recover links.

Ping between all ipv6 hosts in the topology.

Kill and recover links.

Ping between all ipv4 and ipv6 hosts in the topology.

Kill and recover links

Ping between all ipv4 hosts in the topology and check connectivity to external ipv4 hosts

Kill and recover links

Ping between all ipv6 hosts in the topology and check connectivity to external ipv6 hosts

Kill and recover links

Ping between all ipv4 and ipv6 hosts in the topology and check connectivity to external ipv4 and ipv6 hosts

Kill and recover links

Ping between ipv4 hosts and an external host that is not configured in external router config, but reachable through the use of route-add command

Kill and recover links

Ping between ipv6 hosts and an external host that is not configured in external router config, but reachable through the use of route-add command

Kill and recover links

Ping between ipv4/ipv6 hosts and an external host that is not configured in external router config, but reachable through the use of route-add command

Kill and recover spine switches.

Ping between all ipv4 hosts in the topology.

Kill and recover spine switches.

Ping between all ipv6 hosts in the topology.

Kill and recover spine switches.

Ping between all ipv4 and ipv6 hosts in the topology.

Kill and recover spine switches

Ping between all ipv4 hosts in the topology and check connectivity to external ipv4 hosts

Kill and recover spine switches

Ping between all ipv6 hosts in the topology and check connectivity to external ipv6 hosts

Kill and recover spine switches

Ping between all ipv4 and ipv6 hosts in the topology and check connectivity to external ipv4 and ipv6 hosts

Kill and recover spine switches

Ping between ipv4 hosts and an external host that is not configured in external router config, but reachable through the use of route-add command

Kill and recover spine switches

Ping between ipv6 hosts and an external host that is not configured in external router config, but reachable through the use of route-add command

Kill and recover spine switches

Ping between ipv4/ipv6 hosts and an external host that is not configured in external router config, but reachable through the use of route-add command

Kill and recover ONOS nodes

Ping between all ipv4 hosts in the topology.

Kill and recover ONOS nodes

Ping between all ipv6 hosts in the topology.

Kill and recover ONOS nodes

Ping between all ipv4 and ipv6 hosts in the topology.

Kill and recover ONOS nodes

Ping between all ipv4 hosts in the topology and check connectivity to external ipv4 hosts

Kill and recover ONOS nodes

Ping between all ipv6 hosts in the topology and check connectivity to external ipv6 hosts

Kill and recover ONOS nodes

Ping between all ipv4 and ipv6 hosts in the topology and check connectivity to external ipv4 and ipv6 hosts

Kill and recover ONOS nodes

Ping between ipv4 hosts and an external host that is not configured in external router config, but reachable through the use of route-add command

Kill and recover ONOS nodes

Ping between ipv6 hosts and an external host that is not configured in external router config, but reachable through the use of route-add command

Kill and recover ONOS nodes

Ping between ipv4/ipv6 hosts and an external host that is not configured in external router config, but reachable through the use of route-add command

DHCP relay v4/v6

(Work in progress)

Clients gets IP or IPv6 address from DHCP server

The host store and router store should includes specific hosts and routes.

Only one switch in DHCP relay test

DHCP v4 tests

Client: 4 clients attached to switch directly

Server: 1 server attached to switch directly

find 4+1 hosts from host store with correct information

All hosts should get IP address

DHCP v4 tests

Client: 4 clients attached to switch directly

Server: 1 server attached to switch indirectly (via gateway)

find 4+1 hosts from host store with correct information

All hosts should get IP address

Implemented

(test is failing)

DHCP v4 tests

Client: 2 clients attached to switch directly, 2 clients attached to switch indirectly (via normal DHCP relay)

find 2+1 hosts from host store with correct information

find 2 routes from host store with correct information

All hosts should get IP address

Implemented

(test is failing)

DHCP v4 tests

Client: 2 clients attached to switch directly, 2 clients attached to switch indirectly (via normal DHCP relay)

find 2+1 hosts from host store with correct information

find 2 routes from host store with correct information

All hosts should get IP address

Implemented

(test is failing)

Client: 2 clients attached to switch directly, 2 clients attached to switch indirectly (via normal DHCP relay)

Server: 1 server attached to switch directly for direct connected host another server attached to switch directly for indirect connected host

find 2+1 hosts from host store with correct information

find 2 routes from host store with correct information

All hosts should get IP address

Implemented

(test is failing)

DHCP v4 tests

Client: 2 clients attached to switch directly, 2 clients attached to switch indirectly (via special DHCP relay)

Server: 1 server attached to switch directly for direct connected host another server attached to switch directly for indirect connected host

"DhcpRelayAgentIp" address should be configured for indirect hosts

find 2+1 hosts from host store with correct information

find 2 routes from host store with correct information

All hosts should get IP address

Implemented

(test is failing)

DHCP v6 tests

Client: 4 clients attached to switch directly

Server: 1 server attached to switch directly

find 4+1 hosts from host store with correct information

DHCP v6 tests

Client: 4 clients attached to switch directly

Server: 1 server attached to switch indirectly (via gateway)

find 4+1 hosts from host store with correct information

All hosts should get IPv6 address

Implemented

(test is failing)

DHCP v6 tests

Client: 2 clients attached to switch directly, 2 clients attached to switch indirectly (via normal DHCP relay)

find 2+1 hosts from host store with correct information

find 2 routes from host store with correct information

All hosts should get IPv6 address

Implemented

(test is failing)

DHCP v6 tests

Client: 2 clients attached to switch directly, 2 clients attached to switch indirectly (via normal DHCP relay)

find 2+1 hosts from host store with correct information

find 2 routes from host store with correct information

All hosts should get IPv6 address

Implemented

(test is failing)

DHCP v6 tests

Client: 2 clients attached to switch directly, 2 clients attached to switch indirectly (via normal DHCP relay)

Server: 1 server attached to switch directly for direct connected host another server attached to switch directly for indirect connected host

find 2+1 hosts from host store with correct information

find 2 routes from host store with correct information

All hosts should get IPv6 address

Implemented

(test is failing)

DHCP v6 tests

Client: 2 clients attached to switch directly, 2 clients attached to switch indirectly (via special DHCP relay)

Server: 1 server attached to switch directly for direct connected host another server attached to switch directly for indirect connected host

"DhcpRelayAgentIp" address should be configured for indirect hosts

find 2+1 hosts from host store with correct information

find 2 routes from host store with correct information

All hosts should get IPv6 address

Implemented

(test is failing)

DHCP v4 tests with tagged hosts

Client: 4 clients attached to switch directly

Server: 1 server attached to switch directly

find 4+1 hosts from host store with correct information

All hosts should get IP address

DHCP v4 tests with tagged hosts

Client: 4 clients attached to switch directly

Server: 1 server attached to switch indirectly (via gateway)

find 4+1 hosts from host store with correct information

All hosts should get IP address

DHCP v6 tests with tagged hosts

Client: 4 clients attached to switch directly

Server: 1 server attached to switch directly

find 4+1 hosts from host store with correct information

Implemented

(test is failing)

DHCP v4 tests with dual-homed hosts

Client: 4 clients attached to switch directly

Server: 1 server attached to switch directly

find 4+1 hosts from host store with correct information

All hosts should get IP address

Implemented

DHCP v6 tests with dual-homed hosts

Client: 4 clients attached to switch directly

Server: 1 server attached to switch directly

find 4+1 hosts from host store with correct information

Implemented

DHCP v4 tests with dual-homed tagged hosts

Client: 4 clients attached to switch directly

Server: 1 server attached to switch directly

find 4+1 hosts from host store with correct information

All hosts should get IP address

Implemented

DHCP v6 tests with dual-homed tagged hosts

Client: 4 clients attached to switch directly

Server: 1 server attached to switch directly

find 4+1 hosts from host store with correct information

Implemented

(test is failing)

Multicast v4/v6

(Work in progress)

Start 2x2 topology of hardware switches

Sink and source on the same dual-tor leaf

Flows and groups are installed

Traffic is properly forwarded

Flows and groups are removed

Flows and groups are installed

Traffic is properly forwarded

Flows and groups are removed

Flows and groups are installed

Traffic is properly forwarded

Flows and groups are removed

Flows and groups are installed

Traffic is properly forwarded

Flows and groups are removed

Flows and groups are installed

Traffic is properly forwarded

Flows and groups are removed

Flows and groups are installed

Traffic is properly forwarded

Flows and groups are removed

Flows and groups are installed

Traffic is properly forwarded

Flows and groups are removed

Flows and groups are removed

Flows and groups are installed

Traffic is properly forwarded

Flows and groups are installed

Traffic is properly forwarded

Flows and groups are installed

Traffic is properly forwarded

Flows and groups are installed

Traffic is properly forwarded

Flows and groups are removed (failure)

Flows and groups are installed (recovery)

Traffic is properly forwarded (recovery)

Flows and groups are removed for the failing sink (failure)

Traffic is properly forwarded on remaining sinks (failure)

Flows and groups are removed for the failing sink (failure)

Traffic is properly forwarded on remaining sinks (failure)

Flows and groups are installed (recovery)

Traffic is properly forwarded (recovery)

Flows and groups are removed for the failing sinks (failure)

Traffic is properly forwarded on remaining sink (failure)

Flows and groups are installed (recovery)

Traffic is properly forwarded (recovery)

Flows and groups are installed (failure)

Traffic is properly forwarded (failure)

Flows and groups are installed (recovery)

Traffic is properly forwarded (recovery)

Dynamic Interface Configuration

P1: untagged 10 --> tagged 10
h1: not configured --> VLAN ID 10
(P2: untagged 10, P3 and P4: tagged 20 and native 10)
(h2-h4: not configured)

Ping succeeds between:

• h1, h2, h3, h4

P1: untagged 10 --> untagged 20
(P2: untagged 10, P3 and P4: tagged 20 and native 10
(h1-h4: not configured)

Ping succeeds between:

• h1, h3, h4

P1, P2: untagged 10 --> untagged 110
(P3 and P4: untagged 20)
(h1-h4: not configured)

Ping succeeds between:

• h1, h2
• h3, h4

P1: untagged 10 --> tagged 20
h1: not configured --> VLAN ID 20
(P2: untagged 10, P3 and P4: untagged 20)
(h2-h4: not configured)

Ping succeeds between:

• h1, h3, h4

Ping succeeds between:

• h1, h2
• h3, h4

Ping succeeds between:

• h1, h2
• h3, h4

P1: tagged 10 --> untagged 10
h1: VLAN ID 10 --> not configured
(P2: untagged 10, P3 and P4: untagged 20)
(h2-h4: not configured)

Ping succeeds between:

• h1, h2
• h3, h4

Ping succeeds between:

• h1, h2
• h3, h4

P1, P2: tagged 10 --> tagged 120, native 110
h1, h2: VLAN ID 10 --> not configured
(P3 and P4: untagged 20)
(h3 and h4: not configured)

Ping succeeds between:

• h1, h2
• h3, h4

Ping succeeds between:

• h1, h2, h3, h4

Ping fails between:

• h1 <--> h2, h3, h4

P1, P2: tagged 20, native 10 --> tagged 20, native 110
(P3 and P4: untagged 20)
(h1-h4: not configured)

Ping succeeds between:

• h1, h2
• h3, h4

P1: tagged 20, native 10 --> tagged 120, native 10
(P2: tagged 20, native 10, P3 and P4: untagged 20)
(h1-h4: not configured)

Ping succeeds between:

• h1, h2
• h3, h4

P1: untagged 10 --> tagged 20
(P2: untagged 10, P3 and P4: untagged 20)
(h1: VLAN ID 20, h2-h4: not configured)

Ping succeeds between:

• h1, h3, h4

Ping fails between:

• h1 <--> h2, h3, h4

P1: untagged 10 --> tagged 20, native 10
(P2: untagged 10, P3 and P4: tagged 20)
(h1, h3, h4: VLAN ID 20, h2: not configured)

Ping succeeds between:

• h1, h3, h4

Ping fails between:

• h1 <--> h2, h3, h4

Ping succeeds between:

• h1, h3, h4

Ping fails between:

• h1 <--> h2, h3, h4

Ping succeeds between:

• h1, h3, h4

Ping succeeds between:

• h1, h3, h4

Ping fails between:

• h1 <--> h2, h3, h4

Consecutive configuration changes:
P1: untagged 20 --> Tagged 10 --> Untagged 50 --> Tagged 20 --> Tagged 40 with Native 30 --> Tagged 20 --> Untagged 20 --> Untagged 10
(P2: tagged 10, native 20, P3 and P4: untagged 20)
(h1-h4: not configured)

Ping succeeds between:

• h1 <---> h2

Changing a subnet
Leaf1-P1: untagged 20 and 10.0.2.254/24 --> untagged 60 and 10.0.6.254/24
h1: 10.0.2.1 --> 10.0.6.1
(Leaf1-P2, P3, P4: 10.0.2.254/24, h2, h3, h4: 10.0.2.0/24)
(Leaf2-P1, P2, P3 P4: 10.0.3.254/24, h5, h6, h7, h8: 10.0.3.0/24)

Ping succeeds between:

• h1 <---> h5