Experimental IP Unavailable - Again

10 views
Skip to first unread message

Amanda Baran

unread,
May 5, 2026, 1:18:12 PM (10 days ago) May 5
to cloudlab-users
Hi,

I just posted a follow-up on my previous question regarding this problem, but the message was deleted.

I tried to power cycle the nodes as previously suggested but this does not fix the problem, and the Exeprimental IP is still down with no link carrier available to bring it up. 
How else can we avoid the control network and access the much faster 100gbps experimental network? 

My experiment: https://www.cloudlab.us/status.php?uuid=b39020eb-48bf-4a26-85fb-d2c1af935347# 

Aleksander Maricq

unread,
May 5, 2026, 1:40:39 PM (10 days ago) May 5
to cloudlab-users
Hi Amanda,

This is a different problem than what you ran into last time.  All of your nodes have the experiment interface, as you specified during your instantiation, up and with an IP.  The problem is with how you instantiated your experiment.  When using the small-lan profile, you can click "Advanced" and that will show you, among other things, an option to specify Link Speed.  Looking at the logs, the link speed parameter for your experiment was set to 0 (corresponding to "Any" speed), so it defaulted to the first available interface for the c6525-100g hardware type that you specified, which is a 25Gb interface on the same NIC as the Control network interface.  You can see on each of your nodes that eno33np0 is the control interface and eno34np1 is up with a 10.10.1.X address.  Next time you instantiate, if you specify both c6525-100g as the hardware type and 100Gb as the link speed, you should get what you need.

Best,
 - Aleks

Reply all
Reply to author
Forward
0 new messages