Running the SCION infrastructure on a local topology

31 views
Skip to first unread message

Siddharth Mehrotra

unread,
Jun 21, 2019, 5:52:23 AM6/21/19
to SCION community
Hello,

I am facing issues while running SCION on a local topology.

I followed the instructions as per the SCION tutorials however still I am facing the issue. I followed the troubleshotting guide however it is mostly for VM connection not for local topology.

Please help! I am attaching the screenshots of the errors I received.

Thanks,
Siddharth
Screenshot from 2019-06-21 11-47-13.png
Screenshot from 2019-06-21 11-48-27.png

Siddharth Mehrotra

unread,
Jun 21, 2019, 6:02:31 AM6/21/19
to SCION community
Adding Pingpost test result.
Screenshot from 2019-06-21 12-01-52.png

Matthias Frei

unread,
Jun 21, 2019, 7:56:54 AM6/21/19
to SCION community
Hi Siddharth,

here's what we see from the screenshots:
  • the first screenshot shows the beacon servers for the local topology ASes are not starting up properly because they can't seem to connect to zookeeper. I'd suggest to double check that
    • zookeeper is installed and running: systemctl status zookeeper
      If it's missing install it by running apt install zookeeper
    • the zookeeper config file /etc/zookeeper/conf/zoo.cfg looks like this:

      tickTime=100
      initLimit=10
      syncLimit=5
      dataDir=/var/lib/zookeeper
      dataLogDir=/run/shm/host-zk
      clientPort=2181
      maxClientCnxns=0
      autopurge.purgeInterval=1

  • the second screenshot shows that a border router was not started. However, the address shown seems to indicate that you're trying to run a SCIONLab-AS, not the default topology? If this is not what you expected, it's possible that there is a stale state in supervisord (i.e. the tool the orchestrates starting the different services) -- if this is the case, you can try to run
    ./supervisor/supervisor.sh reload
  • for the pingpong test, it looks like you're trying to use a local AS that is not part of the default local topology. Choose one of the ASes of the local topology, e.g. 2-ff00:0:221 and then start pingpong using this as the local AS:
    ./bin/pingpong -sciond /run/shm/sciond/sd2-ff00_0_221.sock -mode server -local 2-ff00:0:221,[127.0.0.1]:40002

As a side note; in order to simplify troubleshooting the local topology, it might help to run the "tiny" local topology instead of the much larger "default" topology:
./scion.sh topology -c topology/Tiny.topo

I hope this helps.

Best Regards,
Matthias

Siddharth Mehrotra

unread,
Jun 24, 2019, 5:00:14 AM6/24/19
to SCION community
Hi Matthias,

Thanks for the revert!

1) The problem with zookeeper was docker installation version, I changed it to newest and it's working fine :)

2) The topology is running fine. However, is there a way I can see the topology like webapp? (PS: I tried Webapp tutorial, however after I keep getting the error webapp: command not found, inspite all dependencies are installed.)

3) I didn't quite understood the pingpong test and still have errors (see attached screenshot). Can you please help ?

Thanks again :)

Best Regards,
Siddharth
Screenshot from 2019-06-24 10-45-17.png
Screenshot from 2019-06-24 10-47-12.png

Michael W. Farb

unread,
Jun 24, 2019, 9:54:55 AM6/24/19
to SCION community
Hi Siddharth,

It seems you're resolved the issue running `make install` from GitHub:

Can you confirm `webapp` can be called from any directory now? Previous versions had some trouble, and I want to make sure you have the latest. You should have commit 8abb71bcbf40032ea25fe6af7ca60346b3b2de6b when you run `git show --summary`

Thanks,
Mike
Reply all
Reply to author
Forward
0 new messages