OpenFlow and gPTP
Both protocols are configured in the task's Access Plane/access-infrastructure context. They test SDN controllers (OpenFlow) and IEEE 802.1AS time synchronization (gPTP).
OpenFlow
Emulates an OpenFlow device (Switch) or controller (Controller). Versions 1.0 and 1.3 are supported.
Table — OpenFlow Parameters
| Name | Description | Value |
|---|---|---|
| Role | Switch or Controller | Emulated role |
| Version | Protocol version | 1.0 / 1.3 |
| Peer address / port | Controller or switch address | For Controller: peer switch; for Switch: controller |
| Reconnect | Reconnection interval | Used after the OpenFlow TCP session disconnects |
| Datapath ID | Datapath (switch) identifier | Hex/numeric ID |
| Buffers / tables | Number of buffers and tables | According to emulation capabilities |
| Capabilities bitmap | Advertised capabilities | Capability bitmap |
| Network interface | Agent interface | Port binding |
| Keepalive / hold / teardown | Session timers | Seconds |
| ToS | ToS/DSCP of control packets | According to the testbed |
After starting, check that the OpenFlow channel is established, Feature Reply/Echo messages are exchanged, and reconnection is stable. If no session is established, compare the IP/port, version, and role—which side is the listener.
gPTP (IEEE 802.1AS)
One instance can run on each physical interface. The supported roles are Grandmaster and Slave; BMCA parameters and intervals are expressed as log2 seconds.
Table — gPTP Parameters
| Name | Description | Value |
|---|---|---|
| Role | Grandmaster or Slave | Clock role |
| Clock identity | Clock identifier | auto or EUI-64 |
| Priority 1 / Priority 2 | BMCA priorities | Lower is preferred |
| Clock class / accuracy / variance | Clock quality | According to the 802.1AS profile |
| Time source | Time source | As defined by the standard |
| Sync / Announce / PDelay interval | Message intervals | log2 seconds |
| UTC offset | UTC offset | Seconds |
After starting, check the selected grandmaster, sync/pdelay stability, and offset. If a slave does not synchronize, check L2 connectivity on the interface and compare the roles and identities at both ends.