[Komal Thareja]

Hi Vaiden,

VM is up and accessible via SSH. Could you please check if your bastion keys are expired?

Thanks,

Komal

[Komal Thareja]

Hi Kriti,

By default, fablib marks the dataplane interfaces as unmanaged by NetworkManager. So NetworkManager is not logging the interface down operation. This was done deliberately as having an interface managed by NetworkManager kept overriding the IP address configuration applied by fablib. Please note this behavior is specific to rocky images which enables NetworkManager by default. Ubuntu doesn’t use NetworkManager by default.

We disable NetworkManager on rocky to be consistent with Ubuntu and leave it to the user to change this behavior as they see fit.

 

Thanks,

Komal

[Komal Thareja]

Hello Yifang,

Could you please share the output of the following commands? This seems to be an issue local to your environment.

cat /home/fabric/work/fabric_config/fabric_rc and ls -ltr /home/fabric/work/fabric_config

Also, please try to Restart your JH container via File -> Hub Control Panel -> Stop My Container followed by Start My Container.

Thanks,

Komal

[Komal Thareja]

Maintenance is complete and the network model has been updated.

[Komal Thareja]

Hello Khawar,

Could you please check if you have any entries for fabrictestbed-extensions in /home/fabric/work/fabric_config/requirements.txt ? If so, please remove those entries and restart your container via File -> Hub Control Panel -> Stop My container followed by Start My Container.

This should clear the issue. Please let us know if the problem persists.

Thanks,

Komal

[Komal Thareja]

Could you please remove the file /home/fabric/work/fabric_config/ssh_config and re-run the jupyter-examples-rel1.6.1/configure_and_validate.ipynb notebook? This shall fix the config issue.

Thanks,
Komal

[Komal Thareja]

Could you please share the output of the command cat /home/fabric/work/fabric_config/ssh_config ?

If this file already existed, the notebook wouldn’t have made any changes to it. Looks like line 5 has some issues.

Sharing example contents of this file below with BASTION USERNAME MASKED:

UserKnownHostsFile /dev/null
StrictHostKeyChecking no
ServerAliveInterval 120
Host bastion.fabric-testbed.net
User YOUR_BASTION_USER_NAME
ForwardAgent yes
Hostname %h
IdentityFile /home/fabric/work/fabric_config/fabric_bastion_key
IdentitiesOnly yes
Host * !bastion.fabric-testbed.net
ProxyJump YOUR_BASTION_USER_NAME@bastion.fabric-testbed.net:22

• This reply was modified 1 year, 6 months ago by Komal Thareja.

[Komal Thareja]

The error observed is because of the incomplete config. You can run the configure notebook from the path jupyter-examples-rel1.6.1/configure_and_validate.ipynb without impacting your experiments.

This only sets up your environment. Experiments from rel-1.5.4 would still work after the config.

Thanks,

Komal

1 user thanked author for this post.

Robin Schelstraete

[Komal Thareja]

Hi Robin,

Config notebook has been updated to avoid such errors.

Could you please run the notebook: jupyter-examples-rel1.6.1/configure_and_validate.ipynb ?

This should update your bastion keys if expired or do not exist. Please try creating a slice and SSH access again after that from console as well as the notebook. Please restart the notebook kernel after the keys are updated.

Thanks,

Komal

[Komal Thareja]

Attaching the screenshot for Chameleon Lease

[Komal Thareja]

Please create a Lease to reserve a host on Chameleon via Project -> Reservations -> Leases -> Create Lease.

Once the lease is created, click on the lease, you will Reservation section on it, Copy the Id from there.

This is the Id you need to use in the notebook. Hope this helps.

If you create the Server on Chameleon manually. Please set the IP address and the routes on the server as below:

ip addr add 10.130.162.2/24 dev eth1

Add route: route add -net 10.130.162.0/24 dev eth1

Change the IP and interface as per your FabNet subnet.

[Komal Thareja]

The fix for BasicNICs is planned to be made available in the next software release 1.7 planned to be available by end of Spring semester.

Thanks,

Komal

• This reply was modified 1 year, 6 months ago by Komal Thareja.

[Komal Thareja]

I just ran this notebook: https://github.com/fabric-testbed/jupyter-examples/blob/main/fabric_examples/complex_recipes/Chameleon_Facility_Port/Chameleon_Facility_Port_fabnetv4.ipynb

No additional steps needed.

Thanks,

Komal

[Komal Thareja]

MASS is working as well. We checked your FABRIC nodes, Fabnet services seems to be connected properly and we can ping the gateway. FABRIC VMs in your slice can ping each other too.

Not sure how your Chameleon Server is setup.

You should see routes and interface setup something similar to below on your Chameleon Node:

cc@kthare10-fabric-stitch-server-1:~$ ip route list
default via 10.130.163.2 dev eno1np0 proto dhcp src 10.130.163.10 metric 100
10.128.0.0/10 via 10.130.163.1 dev eno1np0 proto dhcp src 10.130.163.10 metric 100
10.130.163.0/24 dev eno1np0 proto kernel scope link src 10.130.163.10
169.254.169.254 via 10.130.163.3 dev eno1np0 proto dhcp src 10.130.163.10 metric 100
cc@kthare10-fabric-stitch-server-1:~$
cc@kthare10-fabric-stitch-server-1:~$
cc@kthare10-fabric-stitch-server-1:~$
cc@kthare10-fabric-stitch-server-1:~$ ifconfig
eno1np0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.130.163.10 netmask 255.255.255.0 broadcast 10.130.163.255
inet6 fe80::be97:e1ff:fec4:8e0 prefixlen 64 scopeid 0x20<link>
ether bc:97:e1:c4:08:e0 txqueuelen 1000 (Ethernet)
RX packets 4937 bytes 1058216 (1.0 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4804 bytes 410390 (410.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

P.S: I did execute the cell indicated as “(Optionally) Add a Router and Attach it to the Subnet”.

 

• This reply was modified 1 year, 6 months ago by Komal Thareja.
• This reply was modified 1 year, 6 months ago by Komal Thareja.
• This reply was modified 1 year, 6 months ago by Komal Thareja.

[Komal Thareja]

Hello Violet,

Thank you for informing us about this. The OpenVswitch notebook has been uploaded to the Jupyter Examples and is now accessible on GitHub here.

Please be aware that, due to limitations imposed by NVIDIA/Mellanox on how bridging is managed, the VM running the OVS switch must utilize dedicated NICs instead of BasicNICs. This example assumes that condition. We have identified an alternative solution currently undergoing testing. We will keep you updated once a solution is deployed to make this work with BasicNICs.

Appreciate your understanding.

Best regards,

Komal

[Author]

Posts