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:0000000000000005/4" : {
"interfaces" : [
{
"name" : "sw5-4",
"ips" : [ "10.0.1.2/24" ],
"mac" : "00:00:00:00:00:01"
}
]
},
"of:0000000000000006/4" : {
"interfaces" : [
{
"name" : "sw6-4",
"ips" : [ "10.0.2.2/24" ],
"mac" : "00:00:00:00:00:03"
}
]
},
"of:0000000000000007/4" : {
"interfaces" : [
{
"name" : "sw7-4-1",
"ips" : [ "10.0.3.2/24" ],
"mac" : "00:00:00:00:00:01"
},
{
"name" : "sw7-4-2",
"ips" : [ "10.0.4.2/24" ],
"mac" : "00:00:00:00:00:02"
}
]
},
"of:0000000000000008/4" : {
"interfaces" : [
{
"name" : "sw8-4-1",
"ips" : [ "10.0.5.2/24" ],
"mac" : "00:00:00:00:00:02"
},
{
"name" : "sw8-4-2",
"ips" : [ "10.0.6.2/24" ],
"mac" : "00:00:00:00:00:03"
}
]
},
"of:0000000000000009/4" : {
"interfaces" : [
{
"name" : "sw9-4",
"ips" : [ "10.0.7.2/24" ],
"mac" : "00:00:00:00:00:01"
}
]
},
"of:0000000000000010/4" : {
"interfaces" : [
{
"name" : "sw10-4",
"ips" : [ "10.0.8.2/24" ],
"mac" : "00:00:00:00:00:03"
}
]
}
},
"apps" : {
"org.onosproject.router" : {
"bgp" : {
"bgpSpeakers" : [
{
"name" : "speaker1",
"connectPoint" : "of:0000000000000001/7",
"peers" : [
"10.0.1.1",
"10.0.3.1",
"10.0.7.1"
]
},
{
"name" : "speaker2",
"connectPoint" : "of:0000000000000001/8",
"peers" : [
"10.0.4.1",
"10.0.5.1"
]
},
{
"name" : "speaker3",
"connectPoint" : "of:0000000000000001/9",
"peers" : [
"10.0.2.1",
"10.0.6.1",
"10.0.8.1"
]
}
]
}
}
}
}
|
There are two main sections to this file:
...
In addition, each BGP speaker has a list of peer IP addresses which are the addresses of the peers which that BGP speaker is peering with. For each peer address that we configure here, there should be a corresponding address for our side of the connection that was configured in the "ports" section (see above). SDN-IP will determine which port the peer is connected at by finding an interface with an IP address in the same subnet. (This means that right now it's best not to use overlapping subnets for different interfaces. However it is fine to have to external peers in the same subnet if they are connected to our network at the same port). Once SDN-IP determines the peer-to-BGP-speaker association, it will install intents to allow BGP traffic to flow through the network between these two points.
SDN-IP component configuration
...
In addition to the network configuration described above, there is a separate configuration file for the SDN-IP software component. Currently there is one configurable parameter, the port that SDN-IP listens for incoming BGP connections on. If you wish to configure this parameter, place this file at KARAF_ROOT/etc/org.onosproject.routing.bgp.BgpSessionManager.cfg. Note that by default ONOS listens on TCP port number 2000 for incoming BGP connections, which is not the default BGP port number 179.
...
The first step is to get an ONOS system up and running, and you can read more about how to do this here: Installing and Running running ONOS
Once ONOS is running, SDN-IP has an additional application dependency that it relies on to ensure ARP requests are resolved properly. This is the org.onosproject.proxyarp application that responds to ARP requests on behalf of hosts and external routers.
...