Forum Replies Created
-
AuthorPosts
-
The Slice id was : d54fd501-ca14-49ce-b217-50c593bd0927
I couldn’t find any errors displayed on the portal.
Apart from resending the packets captured on the P4 switch,
Paul recommended me to use Dedicated Nics. (Slice-id : 8aff3c57-7a84-41c6-8e9c-dae4d4087111 , Slice_name : “mri_ded” )
Before installing P4 dockers I could receive packets on other ethernet ports of the switches easily.
But I got the same results as with Basic_Nics. The packets were reaching the switches but not exchanging with other switches.
What may be the issue?
Kind regards,
Nagmat
Update regarding the MRI experiment.
@Paul recommended me capture the packet in the bmv2 switch and send the same captured packet before installing P4 docker containers. I tried it and as Paul expected the packets didn’t go through as shown in the attached picture. As shown in the picture when we send normal packets, it is going through the switch, but when I resend the old packet it doesn’t go through.
It worked, Thanks!
`
s1 = slice.get_node(name=”s1″)
s1.upload_file(‘scripts/dump.pcap’, ‘dump.pcap’)<code></code>`
May 10, 2023 at 4:40 pm in reply to: I am getting “Playbook has failed tasks: Error in creating the server” on FIU. #4200Hi Nagmat,
I looked at your slice and the error reported above, your slice is requesting more than one VM on FIU and they are being allocated to
fiu-w3.fabric-testbed.net
. All the VMs are of the flavor:fabric.c8.m16.d500
. Current disk availability onfiu-w3.fabric-testbed.net
can only accomodate one such VM so all others fail.We do have known discrepancy in the disk availability between the software and the infrastructure. We have plans to address that soon. Could you please use a different site instead of FIU for now?
Appreciate your feedback!
Thanks,
KomalThanks for the quick response. I am continueing my experiment with UCSD instead of FIU.
Kind regards,
Nagmat
Please check your spam folder. The email definitely goes out, but some spam filters over-react. There should be an email confirmation to the address you specified.
Found it, it was in spam folder.
vite and check if the Teams inf
I didn’t receive any confirmation email. I booked again for the next Monday but didn’t receive a confirmation email again.
I am attaching the office hours confirmation.
Just letting you know that I didn’t receive any email for my office hours for today and for next Monday.
Kind regards,
Nagmat
April 24, 2023 at 12:32 pm in reply to: P4_bmv2 example is not working when executed on fabrictestbed. #4139Dear Community,
I am sharing a GitHub repository where complex recipes (P4 Bmv2 example) are explained precisely: https://github.com/nagmat1/P4_experiment_Fabric
Feel free to ask questions if you are stuck.
Kind regards,
Nagmat
1 user thanked author for this post.
April 14, 2023 at 2:33 pm in reply to: Where shall we report internet issues on FabricTestbed? #4087which ipv4 nameservers shall I use?
April 13, 2023 at 1:17 pm in reply to: Is it possible to compile p4 program and do experiments with programmable switch #4081Once we are
Is there any update on deploying qty 4 P4 switches (EdgeCore Wedge with 100Gbps ports and a Tofino chipset). When is the estimated time to do the experiments?
Dear Community,
I am facing the same issue in FIU,CERN,CLEM and UCSD :
“sudo: unable to resolve host 1467f1be-52ba-44a6-bdfd-90206811ce83-h1: Temporary failure in name resolution
sudo: unable to resolve host 1467f1be-52ba-44a6-bdfd-90206811ce83-h1: Temporary failure in name resolution
sudo: unable to resolve host 1467f1be-52ba-44a6-bdfd-90206811ce83-h1: Temporary failure in name resolution
sudo: unable to resolve host 1467f1be-52ba-44a6-bdfd-90206811ce83-h1: Temporary failure in name resolutionĀ ”I have triedĀ 2606:4700:4700::1111, 2620:0:c80:2::1, 2620:0:c80:2::3 DNS servers too, but getting the same error.
What may be the issue?
April 10, 2023 at 6:09 pm in reply to: P4_bmv2 example is not working when executed on fabrictestbed. #4074I tried to use dedicated NICs instead of Basic NICs but it didn’t change the results.
When I am using Basic NICs at least I can see that the packets are flowing from h1 to ens7 ethernet inside docker on switch1(and packets stuck there), while using dedicated nics I am getting :
“Node Error Details
s1 Insufficient resources: No candidates nodes found to serve res: #cf8487b6-94ef-47d3-84d3-8b37398826b2 slice: [DEDICATED_P4(740490f8-633a-47b4-a3d2-40151b3b94ed) Owner:nagmat@nevada.unr.edu] state:[Nascent,Ticketing] #
s2 Insufficient resources: No candidates nodes found to serve res: #97c0f7ad-ec63-4fb3-9ba4-53f0480d2c02 slice: [DEDICATED_P4(740490f8-633a-47b4-a3d2-40151b3b94ed) Owner:nagmat@nevada.unr.edu] state:[Nascent,Ticketing] #
s3 Insufficient resources: No candidates nodes found to serve res: #51cbf620-11f0-4d24-879a-3866f1ab5228 slice: [DEDICATED_P4(740490f8-633a-47b4-a3d2-40151b3b94ed) Owner:nagmat@nevada.unr.edu] state:[Nascent,Ticketing] #
h1 TicketReviewPolicy: Closing reservation due to failure in slice#
h2 TicketReviewPolicy: Closing reservation due to failure in slice#
h3 TicketReviewPolicy: Closing reservation due to failure in slice#
net_s1_s2 redeem predecessor reservation# cf8487b6-94ef-47d3-84d3-8b37398826b2 is in a terminal state, failing the reservation# 0844edf2-413a-455c-a646-c2869d669641#
net_s2_s3 redeem predecessor reservation# 97c0f7ad-ec63-4fb3-9ba4-53f0480d2c02 is in a terminal state, failing the reservation# 8281eac2-33c8-484d-9cf1-f63240640f6d#
net_s1_s3 redeem predecessor reservation# 51cbf620-11f0-4d24-879a-3866f1ab5228 is in a terminal state, failing the reservation# cc161864-45a5-4b54-958a-27cbc071a52b#
net_h1 redeem predecessor reservation# cf8487b6-94ef-47d3-84d3-8b37398826b2 is in a terminal state, failing the reservation# c26b4d90-f1e8-4d3b-85ca-3f4546a045d6#
net_h2 redeem predecessor reservation# 97c0f7ad-ec63-4fb3-9ba4-53f0480d2c02 is in a terminal state, failing the reservation# b0ea0acf-8adc-4368-90a1-a1ae10a9c03b#
net_h3 redeem predecessor reservation# 51cbf620-11f0-4d24-879a-3866f1ab5228 is in a terminal state, failing the reservation# 796fab98-2812-4076-8b56-9640badcd9dd# “April 4, 2023 at 4:35 pm in reply to: failed lease update- all units failed priming: Exception during create for unit: #4035It was observed in :
#site1 = “FIU”
#site2 = “UCSD”
#site3 = “MASS”The storage size wasn’t 2000GB but it was 1000G.
Kind regards,
Nagmat
- This reply was modified 1 year, 8 months ago by Nagmat Nazarov.
March 30, 2023 at 2:26 pm in reply to: P4_bmv2 example is not working when executed on fabrictestbed. #4010I found in components:
” component_model_map = { ‘NIC_Basic’: ComponentModelType.SharedNIC_ConnectX_6,
‘NIC_ConnectX_6’: ComponentModelType.SmartNIC_ConnectX_6,
‘NIC_ConnectX_5’: ComponentModelType.SmartNIC_ConnectX_5,
‘NVME_P4510’: ComponentModelType.NVME_P4510,
‘GPU_TeslaT4’: ComponentModelType.GPU_Tesla_T4,
‘GPU_RTX6000’: ComponentModelType.GPU_RTX6000
}”Which one do you mean by “Dedicated_NICS”?
March 22, 2023 at 5:02 pm in reply to: P4_bmv2 example is not working when executed on fabrictestbed. #3976Dear Community,
I am working on https://github.com/fabric-testbed/jupyter-examples/blob/master/fabric_examples/complex_recipes/P4_bmv2/p4lang_tutorials.ipynb P4 lang tutorials on Fabric Testbed. The architecture is shown in the attachment. As shown on the terminal attachment I am sending the message from host1 and it is getting to ens7 ethernet inside docker on s1 but not reaching the s2 switch at all. Can anybody in the community help resolve this issue, please?
Kind regards,
Nagmat
-
AuthorPosts