[Komal Thareja]

Hi Nishanth,

Thank you for sharing this.

Please note that the current implementation of execute_thread maintains the process only for the duration of the specified timeout. As you correctly observed, for longer-running processes, directly accessing the switch via SSH allows you to manually launch switchd.

We will work on enhancing execute_thread to better support this use case and will keep you informed once the update is available.

Thanks,

Komal

 

[Komal Thareja]

This error typically occurs due to an expired token. Please try the following steps:
Go to File → Hub Control Panel → Stop My Server, then select Start Server to generate a new token.

Thanks,

Komal

P.S: https://learn.fabric-testbed.net/knowledge-base/using-the-jupyter-hub/#frequently-asked-questions

[Komal Thareja]

Hi Philip,

I can confirm that your slice is up and running. Could you please verify it from the Portal via Experiments-> My Slices.

W.r.t to Jupyter Hub, could you please re-run this notebook jupyter-examples-rel1.8.*/configure_and_validate/configure_and_validate.ipynb ?

After this, please try deleting your slice and recreating it via Hello Fabric notebook again.

Thanks,

Komal

[Komal Thareja]

The maintenance is complete.

Thanks,

Komal

[Komal Thareja]

Hi Plabon,

We’re in the process of procuring BlueField DPUs and are planning to integrate them into the FABRIC infrastructure. While the timeline isn’t finalized yet, we’re tentatively looking at Summer or Fall 2025. Stay tuned for updates!

Thanks,
Komal

[Komal Thareja]

Hi Sadat,

Could you please provide following information?

• Slice ID
• Verify and report the status of the Slice from Portal via Experiments -> My Slices
• Verify and report if any errors observed in /tmp/fablib/fablib.log from JH container.
• Verify Bastion SSH Keys are not expired
  • Check via portal Experiments -> Manage SSH Keys -> Bastion Key
  • In JH Container – Run jupyter-examples-rel1.8*/configure_and_validate.ipynb – this shall renew your expired keys
  • Please try your slice again if your Bastion Keys are expired.

Thanks,

Komal

• This reply was modified 2 months ago by Komal Thareja.

[Komal Thareja]

Hi Samia,

I verified all the VMs in your slice are accessible via SSH. The error you are noticing is probably because of expired bastion keys. Could you please try to re-execute the notebook: jupyter-examples-rel1.8.1/configure_and_validate/configure_and_validate.ipynb ?

This shall renew your bastion keys. If you are doing SSH from your laptop, please download the renewed bastion keys from /home/fabrirc/work/fabric_config directory after executing the notebook above to replace the keys in .ssh directory.

Please let me know if you run into any issues or have questions.

Thanks,

Komal

[Komal Thareja]

Hello,

Could you please share your Slice ID?

Thanks,

Komal

[Komal Thareja]

FABRIC only allows SSH and few ICMP messages over the management interface. Hosting services on management network is not recommended. Instead, we recommend using data plane network for your service.

FABRIC serves as a secure sandbox, allowing students and researchers to experiment with potentially disruptive and vulnerable software architectures in a protected environment. When connecting external devices, such as laptops or servers, to nodes within a slice, it is crucial to employ secure methods like SSH tunnels. A Jupyter notebook example illustrates how to create SSH tunnels through the FABRIC bastion host. Alternatively, users can utilize personal VPNs like Tailscale for secure connections example notebook.

Exposing ports to the entire Internet is restricted, reserved only for exceptional cases where alternative solutions are not viable. Moreover, users undertaking such capabilities are responsible for deploying, maintaining, and ensuring the security of experiments, akin to a production data center. IPv4Ext and IPv6Ext services facilitate these capabilities.

For newcomers, getting acquainted with SSH tunnels is recommended due to their simplicity and security. If users have additional questions or require further guidance, they are encouraged to reach out.

Best,

Komal

[Komal Thareja]

Hi Mike,

Could you try specifying multiple VLANs when adding the Facility port and then access the interfaces as shown below?

facility_port = slice.add_facility_port(name=facility_port, site=facility_port_site, vlan=['3300', '3301'])  
facility_port_interface_1 = facility_port.get_interfaces()[0]  
facility_port_interface_2 = facility_port.get_interfaces()[1]  

 

P.S: Please change the vlans accordingly in the example above.

Thanks,
Komal

• This reply was modified 2 months, 4 weeks ago by Komal Thareja.

[Komal Thareja]

Hi Mike,

Could you please check following files and ensure they point to the new key and have the right bastion username?

/home/fabric/work/fabric_config/fabric_rc

/home/fabric/work/fabric_config/ssh_config

Also, just verified that the VM in question seems to have been deleted.

Thanks,

Komal

[Komal Thareja]

Hi Mike,

This could possibly be because your Bastion Key has expired. Could you please try running the  notebook jupyter-examples-rel1.8.1/configure_and_validate/configure_and_validate.ipynb again?

This should renew the keys. If error persists, could you please share if you see any errors in /tmp/fablib/fablib.log

Thanks,

Komal

• This reply was modified 3 months ago by Komal Thareja.

[Komal Thareja]

Hi Tejas,

Could you please share your slice id?

 

Thanks,

Komal

[Komal Thareja]

Glad to hear it worked, Mike! The default container should function properly as well—I’ll give it a try.

The Bleeding Edge container includes the latest released software versions, so I’d recommend using that.

Beyond Bleeding Edge contains the newest software from the main branch, including ongoing development changes, which may introduce some bugs.

Thanks,

Komal

[Komal Thareja]

Hi Mike,

I just tried the example notebook you mentioned. It worked for me using the Beyond Bleeding Edge Container. Could you please share which JH container are you using? Also, if possible share the Slice ID where you see this error or which Facility Ports you ran into this error with?

 

Thanks,

Komal

[Author]

Posts