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.
...
cd ~/onos/tools/dev/mininetsudo mn --custom onos.py --controller onos,3 1 --topo torustree,42,42
You should see a bunch of output showing the startup of the control network and the data network.
...
To exit Mininet, use the exit command or press control-D.
Once you have verified that a single-node ONOS cluster and simple topology are working correctly, you can try a larger cluster (we recommend 3 nodes if you have configured your VM to use 6-12 GB of RAM) and a larger or more interesting topology (such as a 4x4 torus):
sudo mn --custom onos.py --controller onos,3 --topo torus,4,4
| Info | ||
|---|---|---|
| ||
If things don't start up correctly, look carefully at any error messages or exceptions which may have been generated - usually they give you important information which will enable you to figure out what is going wrong and to fix the issue. Also check out the troubleshooting section below. |
...
Here are some things you can try:
- Make sure you've given your VM enough RAM - try using 2-4 GB for each ONOS node (so 6-12 GB for
--controller onos,3) - Make sure you are running the latest version of Mininet (see below)
- Look at the log file(s) and make sure no errors are occurring:
more /tmp/onos1/log; more /tmp/onos1/onos.log - Look at the output from running
mnoronos.pyand carefully examine and try to understand any error or exception messages - usually they will tell you what is going wrong - Reset your environment using:
sudo pkill -f karaf.jar; sudo mn -c - Make sure you have built onos:
cd ~/onos; buck build onos - Make sure you can run Mininet:
sudo mn --test pingall
...