[Komal Thareja]

Hi Vaiden,

Not sure how your slice was setup. If you interfaces were configured in auto mode. You should be able to do the following to reapply the config.


slice = fablib.get_slice(slice_name)
for n in slice.get_nodes():
n.config()


 

Thanks,

Komal

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

[Komal Thareja]

Hi Vaiden,

I have checked the logs and don’t see any errors. Looks like your slice was modified multiple times.

Some of the resources closed on 2024-05-18 18:27:07 +0000 while all other had expiry date set to 2024-11-02 19:45:33 +0000. Is it possible that the slice deletion was triggered by you on accident?

I have no evidence of software deleting it due to expiry as per the logs.

Could you please share if there were any recent actions taken on the slice? Trying to see if this can be recreated.

Appreciate your help with this.

Thanks,

Komal

[Komal Thareja]

Hi Vaiden,

Unfortunately, it is not possible to recover the slivers once deleted. I will look at why the slice was closed before the end date. However, I do suspect that Extend/Renew may have failed for certain slivers. I will look more and share details here.

Thanks,

Komal

[Komal Thareja]

Good morning Fraida,

I’ve pushed a fix to address this issue. Could you please try again using the Beyond Bleeding Edge container on JH and let us know if the problem persists? Your help is greatly appreciated!

Thanks,

Komal

[Komal Thareja]

Hi Pilar,

Could you please check if your bastion keys are expired via on the Portal ->Experiments -> Manage SSH Keys -> Bastion Keys? If so, Please re-run the notebook jupyter-examples-rel1.6.1/configure_and_validate.ipynb

This should renew your bastion keys. Please try creating your slice again after this.

Thanks,

Komal

[Komal Thareja]

Hi Nishant,

Installing fablib from main branch should work. It is using the fabrictestbed==1.5.9 dependency which has the fix.

fabrictestbed==1.5.9 is built from llt branch. I will work on merging this branch to main as well.

Thanks,

Koma

[Komal Thareja]

Hi Fraida,

Yes, FABRIC now supports Slices using OVS Bridges using NIC_Basic. An example notebook can be found here: https://github.com/fabric-testbed/jupyter-examples/blob/main/fabric_examples/complex_recipes/openvswitch/openvswitch.ipynb

We do have following constraint though for this to work.

Host Considerations:

Because of constraints imposed by NVIDIA/Mellanox, when utilizing NIC_Basic for an OVS bridge experiment, it is advisable to deploy the VM responsible for running the bridge on a separate host from the VMs linked to the bridge.

Additionally, it’s worth noting that this condition does not apply to NIC_ConnectX_5 and NIC_ConnectX_6 configurations.

Thanks,

Komal

[Komal Thareja]

Thank you for sharing this Sunjay, we will fix this in the next version.

Thanks,

Komal

[Komal Thareja]

Posting an update to close the loop.

Had a quick Zoom meeting with Laura to resolve this. The issue seemed to be bastion keys, removing contents of fabric_config and re-running configure_and_validate.ipynb resolved the issue.

@Laura – Please let us know if you run into any issues!

Thanks,

Komal

[Komal Thareja]

Hi Shoaib,

Which network are you trying to setup – layer2 or layer3? Please share your slice id to help us investigate this further.

In addition, please take a look at the examples available from start_here.ipynb

All the networking examples have three configurations:

• Auto – FABLIB automatically configures IPs and routes
• Manual – User explicitly configures IPs and routes
• Config – User explicitly specifies the IPs/subnets to choose and FABLIB automatically configures IPs and routes

Please let us know if you still have questions or concerns.

Thanks,

Komal

• This reply was modified 10 months, 1 week ago by Komal Thareja.
• This reply was modified 10 months, 1 week ago by Komal Thareja.

[Komal Thareja]

There was a missing configuration on RUTG due to the maintenance being lifted from one of the hosts there. Please check again now; the interfaces should be visible on your VMs.

Thank you for reporting this issue and allowing us to address the misconfiguration.

Thanks,

Komal

1 user thanked author for this post.

Garegin Grigoryan

[Komal Thareja]

Thanks,

Komal

 

• This reply was modified 10 months, 1 week ago by Komal Thareja.

[Komal Thareja]

Hi Nirmala,

Are you a member of multiple projects? If so, could you please try the following and see if this helps?

From the portal Go to Experiments -> Projects and Slices, choose the specific project, click on Slices under that project.

Please let us know if this is still an issue.

Alternatively, you could renew the slices from Jupyter Hub with one of the following options:

Option A: Slice commander

• Open a terminal, type slice-commander
• type ls to list your slices
• cd to your slice and then type renew <days>

Option B: Notebook

• List your slices using notebook Start Here -> List All Slices (available under Managing Slices)
• Renew your slices using notebook Start Here -> Extending a Slice Reservation (available under Managing Slices)

 

Thanks,

Komal

 

[Komal Thareja]

Could you please share your slice id? ID you shared earlier is your Project ID.

Thanks,

Komal

1 user thanked author for this post.

Garegin Grigoryan

[Komal Thareja]

Hi Garegin,

I suspect you are using ubuntu image for your VMs. Please note for ubuntu, the interfaces are not up by default.

Please install net-tools using the following command:

apt install net-tools

You can then verify the interfaces via the command: ifconfig -a

Thanks,

Komal

[Author]

Posts