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.
...
It will prompt for a password, which is sdnip. Once the password is entered, we'll drop into a prompt {{r4> }}prompt r4>
Now we can begin to configure the router to advertise a new network.
| Code Block |
|---|
r4> enable
r4# configure terminal
r4(config)# router bgp 65004
r4(config-router)# network 192.168.4.0/24
r4(config-router)# exit
r4(config)# exit
r4# |
Now our external router r4 has advertised a new route to our SDN network. Let's see if ONOS has received it.
| Code Block |
|---|
onos> routes
prefix=192.168.1.0/24, nexthop=10.0.1.1
prefix=192.168.2.0/24, nexthop=10.0.2.1
prefix=192.168.3.0/24, nexthop=10.0.3.1
prefix=192.168.4.0/24, nexthop=10.0.4.1 |
We see the new route to 192.168.4.0/24 has appeared in the list. Also, when SDN-IP received the route it installed a new MultiPointToSinglePoint intent into the network.
| Code Block |
|---|
onos> intents -s
...
MultiPointToSinglePoint total= 4 installed= 4
MultiPointToSinglePoint withdrawn= 0 failed= 0
MultiPointToSinglePoint submitted= 0 compiling= 0
MultiPointToSinglePoint installing= 0 recompiling= 0
MultiPointToSinglePoint withdrawing= 0
... |
Our number of MultiPointToSinglePoint intents has increased to 4. Now let's see if we can ping to our new network.
| Code Block |
|---|
mininet> h1 ping h4
PING 192.168.4.1 (192.168.4.1) 56(84) bytes of data.
64 bytes from 192.168.4.1: icmp_seq=1 ttl=62 time=0.595 ms
64 bytes from 192.168.4.1: icmp_seq=2 ttl=62 time=0.182 ms
64 bytes from 192.168.4.1: icmp_seq=3 ttl=62 time=0.164 ms
... |
Great! Now we can ping to h4 which is in the network we just received through BGP. This shows that whenever the routes learnt through BGP are updated, SDN-IP reacts to the update and programs the dataplane accordingly.