Using different topology from spine leaf on the tutorial

[urib]

Hello,

Sorry if my questions sound stupid, I am new and trying to learn.

I modified the topology from the spine-leaf used in the tutorial to a group of simple linear switches with hosts and each group with its own controller.

after ‘make netconfg’ the curl timeout. I can see the config through my browser bout the controller I couldn’t see the devices on the controller

the app install also failed due to time out.

the question is do I need to make any changes elsewhere due to the changes in the topology?

Thank you for your time and help.

[urib]

I am still on this issue, can anyone please clarify whether I need to make any changes or right any code as the netcfg is returning error 400 whenever I try to push it to the controller?
the topology is no longer spine-leaf but a linear switch with hosts.
@andyfingerhut
here is the curl command

here is the netcfg

{
    "devices": {
      "device:SW1": {
        "basic": {
          "managementAddress": "grpc://mininet:50001?device_id=1",
          "driver": "stratum-bmv2",
          "pipeconf": "org.onosproject.ngsdn-tutorial",
          "locType": "grid",
          "gridX": 200,
          "gridY": 600,
          
        }
      },
      "device:SW2": {
        "basic": {
          "managementAddress": "grpc://mininet:50002?device_id=2",
          "driver": "stratum-bmv2",
          "pipeconf": "org.onosproject.ngsdn-tutorial",
          "locType": "grid",
          "gridX": 800,
          "gridY": 600,
        
        }
      }
    },
    "ports": {
      "device:SW1/2": {
        "interfaces": [
          {
            "name": "SW1-2",
            "ips": ["2001:1:1::1a/64"]
          }
        ]
      },
      "device:SW1/3": {
        "interfaces": [
          {
            "name": "SW1-3",
            "ips": ["2001:1:1::1b/64"]
          }
        ]
      },
      "device:SW1/4": {
        "interfaces": [
          {
            "name": "SW1-4",
            "ips": ["2001:1:1::1c/64"]
          }
        ]
      },
      "device:SW2/2": {
        "interfaces": [
          {
            "name": "SW2-2",
            "ips": ["2002:1:1::a/64"]
          }
        ]
      },
      "device:SW2/3": {
        "interfaces": [
          {
            "name": "SW2-3",
            "ips": ["2002:1:1::b/64"]
          }
        ]
      },
      "device:SW2/4": {
        "interfaces": [
          {
            "name": "SW2-4",
            "ips": ["2002:1:1::c/64"]
          }
        ]
      }
    },

    

    "hosts": {
      "00:00:00:00:00:1A/None": {
        "basic": {
          "name": "h1a",
          "locType": "grid",
          "gridX": 100,
          "gridY": 700
        }
      },
      "00:00:00:00:00:1B/None": {
        "basic": {
          "name": "h1b",
          "locType": "grid",
          "gridX": 100,
          "gridY": 800
        }
      },
      "00:00:00:00:00:1C/None": {
        "basic": {
          "name": "h1c",
          "locType": "grid",
          "gridX": 250,
          "gridY": 800
        }
      },
      "00:00:00:00:00:2A/None": {
        "basic": {
          "name": "h2a",
          "locType": "grid",
          "gridX": 400,
          "gridY": 700
        }
      },
      "00:00:00:00:00:2B/None": {
        "basic": {
          "name": "h2b",
          "locType": "grid",
          "gridX": 750,
          "gridY": 700
        }
      },
      "00:00:00:00:00:2C/None": {
        "basic": {
          "name": "h2c",
          "locType": "grid",
          "gridX": 850,
          "gridY": 700
        }
      }
  
  
  
    }
  }
  

[ederollora]

Hi @urib

So first some comments

In terms of the ‘make netcfg-onos1’ (not sure why you changed the name), I can see that the port is wrong. It should be 8181 and you are using 6612. Maybe port 6612 makes sense but never heart if used for one or another thing. I also have no idea why it complains about 0.0.31.176 being the IP it connects to. This part you probably already fixed (as I could see in the second image).

To build and install the app I use, and it builds just ok. right now it does not install but need to look why. It complains about a “conflict” but I deactivated and uninstalled the app before I tried installing the new one. My VM is from 2020, so it could indeed be different to yours. There could always be an issue with the code too, but you never know.

make app-build
make app-install

Could you also please state which netcfg command you are running? I guess it is not make netcfg (maybe it is XD) so we can always see. I can see it complains about line 145 but I already know that Makefile is different from ours so if you share it that would be nice. Also, to make this nicer, could you please share your code as in a ZIP file? Possibly you can upload it to Google Drive or some other platform.

Cheers

[urib]

Hello @ederollora,

thank you for your response.

My topology has 4 network segments each with its own controller, so I modified the netcfg target for each controller to netcfg-onos1, netcfg-onos2, etc. Since all the controllers are listening on 8181, I exposed different ports (6612 in this case) to talk to each specific controller on its unique port.

I think I was able to resolve the issue that I asked earlier. I can see the devices, links, pipeconfs and netfcg from the controller CLI.

My current dilemma is that the hosts are not visible, even though I activated reactive forwarding but I can’t ping the hosts. I completed the Exercises until the fifth, (my experiments will mainly be on basic routing, maybe I will have to finish all 8 exercises).

Good day

[ederollora]

Hi @urib,

Please can you send your project as a ZIP file?

Cheers,

[urib]

Hello @ederollora

here is the project file. try using onos2 or onos3 I am not sure why onos1 usually fails. I am looking into that. thank you
https://filesender.renater.fr/?s=download&token=f8559696-0ea0-4075-82b6-467190c170e9

[ederollora]

Hi,

No problem, give me a day or so and will let you know which problem I find,

Cheers,