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.
...
| Code Block | ||
|---|---|---|
| ||
{
"ports" : {
"of:0000000000000001/1" : {
"interfaces" : [
{
"name" : "Interface 1 sw 1",
"ips" : [ "1.1.1.1/24", "10.10.10.1/24" ],
"mac" : "00:00:00:00:00:01"
}
]
},
"of:0000000000000002/1" : {
"interfaces" : [
{
"name" : "Interface 1 sw 2",
"ips" : [ "2.2.2.2/24" ],
"vlan" : "100",
"mac" : "00:00:00:00:00:02"
},
{
"name" : "Interface 2 sw 2",
"ips" : [ "3.3.3.3/24" ],
"vlan": "150",
"mac" : "00:00:00:00:00:03"
}
]
}
} |
...
Configuration semantic and best-practices:
What's reported above is a very generic configuration example, used for an SDN-IP demo. Indeed, the configuration is very specific to the application that parses it.
While the configuration syntax and general structure is globally prescribed by the interface configuration subsystem itself, It's up to each ONOS application how to interpret the values provided. For example, some applications might request just one parameter per interface (it might be the case of some L2 applications with VLAN); some others might request to have also IPs, interface name and other parameters (for example L3 applications).
Given this model it's really difficult
1 to 1 mapping between an interface and a port
...