Versions Compared

Old Version 32

changes.mady.by.user Jonathan Hart

Saved on

compared with

New Version 33

changes.mady.by.user Luca Prete

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

A full running SDN-IP system has a lot of pieces that need to be correct before anything will work. When setting up a system for the first time or when things go wrong, it's best to go step by step to check each piece is in place.

Check SDN-IP is installed:

Code Block
onos> apps -s | grep sdnip
*   4 org.onosproject.sdnip            1.310.0.SNAPSHOT SDN-IP peering application

The little * in the 1st column means SDN-IP is activated. If it's not there, try activate it again.

Check whether the external routers can resolve ARP properly. If they can't resolve ARP, then look in the addresses.json file and check that the address configuration is correct.

Check the BGP peering sessions are established with the internal BGP speakers. If the peering sessions are not established, it may be that the sdnip.json configuration is wrong. If it seems to be correct, check the configuration of the BGP peers.

the logs. Is there any error?

Code Block
titleExample: increase sdnip log level to debug, using the ONOS CLI
onos> log:set org.onosproject.apps.sdnip debug

Was you configuration loaded by ONOS?

Code Block
titleCheck the ONOS network configuartion
onos> netcfg

Have interface contained in your ONOS network config loaded correctly in the system?

Code Block
titleCheck interfaces configured
onos> interfaces

Was the SDN-IP configuration contained in your ONOS network config loaded correctly in the system?

Code Block
titleCheck SDN-IP configuration
onos> bgp-neighbors

Once you're sure nothing wrong is in the logs and that SDN-IP has been configured correctly, it's time to go one level deeper. let's check the intent subsystem. First let's check that the external routers You should have six point to point intents for each couple external router - BGP speaker, and one multi-point-to-single-point intent for each route advertised from an external router.

Can your external routers communicate with the BGP speakers?

External routers need to form a BGP session with the BGP speakers. To do that six point to point intents for each couple external router - BGP speaker get installed by ONOS. You should make sure of the following

Can you external routers ping the BGP speakers they should peer with? Do some ping tests. If ping does not work, check if ARP is resolved or not on the hosts, meaning for example, does your external router have the association between the IP address and the MAC address of the BGP speaker in its ARP table? If any of the two points above fails, likely your interfaces configuration is wrong. This usually reflects in wrong point-to-point intents installed by ONOS.

Are the point-to-point intents installed by ONOS correct?

Code Block
titleExample of the basic intent commands - intents summary and detailed intents view
onos> intents -s
onos> intents

If you don't see any multi-point-to-single-point intent

 Check the configuration files are in the correct directory.

Next, check that the internal BGP speakers are peering with ONOS correctly:

...

We really welcome your help to ensure the code and documentation are clear and informative, so let us know if you have and issues.

 have