...
Code Block |
---|
onos> summary node=12710.0.03.111, version=1.12.1.SNAPSHOTsdnip~2015/07/14@16:50 nodes=1, devices=6, links=14, hosts=5, SCC(s)=1, paths=46, flows=18, intents=0 |
Install the application
First we need to install some helper applications that SDN-IP relies on. These features apps let ONOS read in various configuration files and respond to ARP requests between the external routers and internal BGP speakers.
Code Block |
---|
onos> feature:install onos-app-app activate org.onosproject.config onos> app feature:install onos-app-activate org.onosproject.proxyarp |
Now, let's install the SDN-IP application so we can get some traffic flowing between our networks.
Code Block |
---|
onos> app feature:install onos-app-activate org.onosproject.sdnip |
A lot happens as soon as we install the SDN-IP application. The first thing it does is install point-to-point intents to allow the external BGP peers to communicate with our internal BGP speaker. This allows the external BGP routers to relay the routes that are capable of forwarding through to SDN-IP.
...
Code Block |
---|
onos> routes
Network Next Hop
192.168.1.0/24 10.0.1.1
192.168.2.0/24 10.0.2.1
192.168.3.0/24 10.0.3.1
Total SDN-IP IPv4 routes = 3 |
...
Network Next Hop
Total SDN-IP IPv6 routes = 0 |
Don't worry if you don't see all of the routes straight away - sometimes it takes a minute or so for the BGP sessions to establish and advertise the routes to ONOS.
...
Code Block |
---|
mininet> h1 ping h2 PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data. 64 bytes from 192.168.2.1: icmp_seq=1 ttl=62 time=0.693 ms 64 bytes from 192.168.2.1: icmp_seq=2 ttl=62 time=0.139 ms 64 bytes from 192.168.2.1: icmp_seq=3 ttl=62 time=0.149 ms ttl=62 time=0.149 ms |
TROUBLESHOOTING NOTE: If the ping doesn't work straight away, try to quit the Mininet network and restart it by double-clicking the "SDN-IP Mininet" icon. There is sometimes a bug with the script where the routes do not get put into the routing table of the linux routers correctly. Restarting Mininet often fixes this.
The ping should succeed. Notice the TTL has been decremented from the default value 64 to 62 as the ping passes through the network. This is because the packet has passed through two Quagga routers - the originating host's router, and the destination host's router. SDN-IP doesn't currently decrement the TTL within the SDN network, because our OpenFlow 1.0 switches don't support TTL decrements.
...
Code Block |
---|
onos> routes
Network Next Hop
192.168.1.0/24 10.0.1.1
192.168.2.0/24 10.0.2.1
192.168.3.0/24 10.0.3.1
192.168.4.0/24 10.0.4.1
Total SDN-IP IPv4 routes = 4 |
...
Network Next Hop
Total SDN-IP IPv6 routes = 0 |
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.
...