Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
The interface configuration is part of the network configuration. It allows users to configure information about ports and logical ports of devices connected to the system. The information is used by ONOS and its applications to decide how to select and forward the network traffic. The interface configuration is probably the most similar to the "legacy" network devices configuration. Examples of common patterns are "select traffic tagged with VLAN X on port Y", "Select all the traffic coming with IP A and send it out through port B".
...
- Ports represent physical ports of devices connected to ONOS. They act as containers of one or more interfaces that actually hold the real configuration
- Interfaces are logical entities, subset of physical ports, distinguished by different parameters, such as i.e. VLANs, IPs, MAC addresses. Each port can have multiple interfaces.
Configuration structure
Following is reported a typical interface configuration used for SDN-IPAs the rest of the network configuration, also the interface configuration is expressed in JSON format. Below, you can find a the structure of a very generic interface configuration
| Code Block | ||
|---|---|---|
| ||
{
"ports" : {
"of:0000000000000001/1DPID__WITH_NO_COLUMNS/PORT" : {
"interfaces" : [
{
"nameKEY_1" : "Interface 1 sw VALUE_1",
"ipsKEY_2" : [ "1.1.1.1/24VALUE_2A", "10.10.10.1/24VALUE_2B" ],
"macKEY_3" : "00:00:00:00:00:01VALUE_3"
}
]
},
"of:0000000000000002/1ANOTHER_DPID_WITH_NO_COLUMNS/PORT" : {
"interfaces" : [
{
"nameKEY_1" : "Interface 1 sw 2VALUE_1",
"KEY_2" : [ "VALUE_2A", "VALUE_2B" ],
"ips" : [ "2.2.2.2/24" ],
"vlan" : "100",
"macKEY_3" : "00:00:00:00:00:02VALUE_3"
},
{
"nameKEY_10" : "Interface 2 sw 2VALUE_10",
"KEY_4" : [ "VALUE_4A", "VALUE_4B" ],
"ips" : [ "3.3.3.3/24" ],
"vlan": "150",
"macKEY_3" : "00:00:00:00:00:03VALUE_3"
}
]
}
} |
Configuration semantic and best-practices:
...