Date: Thu, 28 Mar 2024 11:31:31 +0000 (UTC) Message-ID: <1446146676.731.1711625491422@ip-10-30-146-46.us-west-2.compute.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_730_2018339888.1711625491419" ------=_Part_730_2018339888.1711625491419 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
OpenFlow is the primary southbound protocol the SDN control<= /em> plane. OpenFlow operates at time scales close to the data network roun= d trip time (RTT), usually milliseconds, and is primarily used to program f= low tables that control packet forwarding using the match-action model. ONO= S's packet forwarding abstractions primarily use OpenFlow to program switch= flow tables.
OpenFlow also provides some limited configuration capabili= ties (such as bringing a port up or down, or configuring meters), but many = required configuration operations (such as telling a switch which controlle= rs to connect to, enabling the OpenFlow agent on a switch, or enabling Open= Flow on specific ports) are explicitly out of scope for OpenFlow.
Switches that require configuration beyond what OpenFlow provides may ne= ed to use other southbound protocols such as ovsdb, NetConf, SNMP, etc.. ON= OS currently provides drivers for several southbound configuration protocol= s. In the future, ONOS may provide configuration abstractions which enable = devices to be configured in a generic manner, without having to worry about= specific configuration protocols and their varying semantics across device= s.
To enable OpenFlow, the drivers
and openflow
a=
pps must be activated, and switches must be configured appropriately to con=
nect to all ONOS instances.