Forum Replies Created
-
Posts
-
Thank you Ben.
I also got information that if you don’t find a link mapped on the dashboard, it is likely the sites involved are not directly connected.
I configured the IP address as it was before it crashed but cannot ping the other nodes using the dataplane. Is there something else I should do?
Yes, sliceID: 97c1aa87-f5e5-4ccb-9b63-a73c1be85825, VM at GATECH management IP: 2610:148:1f00:9f01:f816:3eff:fe49:cd8d
Thank you very much Charles.
Found out the config file path is actually /opt/fabric_prometheus/prometheus/config/prometheus_config.yml
Regards,
Acheme
Hello Robin,
I am not very familiar with SR but I notice that you did not reserve network resources no connect the nodes with links. I never had to perform iperf using management IPs on this testbed so I am not sure how it should behave. Sorry I have to been more helpful.
Regards,
Acheme
Hello Robin,
Could you copy and paste the content of your notebook here, I am unable to access the link you provided.
Regards,
Acheme
Hi Robin,
Could you share your notebook(s) here. It helps to replicate the issue and hopefully resolve and share a resolution.
Regards,
Acheme
Hi Jiri,
Your interfaces appear to be down from the images you shared.
You can bring them up with these commands before trying to “download the file to the client”:
stdout, stderr = server.execute(f’sudo ip link set dev {server_iface.get_os_interface()} up’)
stdout, stderr = client.execute(f’sudo ip link set dev {client_iface.get_os_interface()} up’)Regards,
Acheme
I tried again and it creates the slice but sets the network of node interfaces to “None” for some reason.
For reference: content of the requirement.txt file in both the version (1.5.4) and the fabric_config folder was cleared out and saved. Then “File” >> “Hub control panel” >> “Stop my server”….and, “Start my server”. Error goes away after.
