1. Komal Thareja

Komal Thareja

Forum Replies Created

Viewing 15 posts - 31 through 45 (of 410 total)
  • Author
    Posts
  • in reply to: Unable to reserve slice #8162
    Komal Thareja
    Participant

      Hi Kriti,

      I can verify that your slice is StableOK. Please check the portal to verify that.

      This looks like a bug, where fablib may be reflecting the stale state. If possible, could you please share your notebook, so I can try to reproduce this on my end and fix the bug? Appreciate your help with this.


      Slice Name: Eibp_large_PRIN Slice ID: 02ff4c5b-140e-4e2a-ab2a-02ca8bd45ca3 Project ID: 787adfc9-d37e-42f2-8efe-8e32793e0bb8 Project Name: Expedited Internet Bypass Protocol
      Graph ID: 53e16605-016c-4e2a-8754-336effb71188
      Slice owner: { name: orchestrator, guid: orchestrator-guid, oidc_sub_claim: 5cf08403-b13e-458a-a17d-ee69abdacffa}
      Slice state: StableOK
      Lease time: 2025-02-05 18:27:56+00:00

      Thanks,

      Komal

      in reply to: Unable to reserve slice #8160
      Komal Thareja
      Participant

        Hi Kriti,

        Could you please share your slice id?

        Thanks,

        Komal

        in reply to: Error message: strptime() argument 1 must be str, not None #8157
        Komal Thareja
        Participant

          Hi Vaneshi,

          I am unable to reproduce this with any of the JH containers. I do notice a small error in the API posted above. quiet parameter is a boolean.

          Could you please check the following?

          • You have a valid token in ~/.tokens.json
          • Try the snippet below


          from fabrictestbed_extensions.fablib.fablib import FablibManager as fablib_manager
          fablib = fablib_manager()
          cx5_column_name = 'nic_connectx_5_available'
          cx6_column_name = 'nic_connectx_6_available'
          sites_connectx_json = fablib.list_sites(
          output="json",
          quiet=True,
          filter_function=lambda x: x[cx6_column_name] > 0 or x[cx5_column_name] > 0,
          latlon=False,
          )
          print(sites_connectx_json)

          Please let me know if you still run into errors.

          Thanks,

          Komal

          in reply to: Site to Site Connection Issue #8146
          Komal Thareja
          Participant

            Hi Raghav,

            Could you please check if the interfaces on the VMs have the IP addresses configured?

            Also, please share the Slice ID for your slice. This will help us take a look at it as well.

            Thanks,

            Komal

            in reply to: Network reconfig after numa_tune #8142
            Komal Thareja
            Participant

              Hi Ilya,

              Thanks for the kind words—we appreciate the feedback!

              To ensure the network interfaces retain their configuration after rebooting, please use the following code to reconfigure all nodes in the slice:

              for n in slice.get_nodes():  
                  n.config()
              

              This will restore the network configurations.

              Regarding DPUs, we’re currently exploring BlueField 2 DPUs and targeting summer for initial support, with more details coming soon. Stay tuned for updates!

              Please let us know if you run into any other issues.

              Best Regards,

              Komal

              in reply to: Cannot view slice topology through My Slices list #8135
              Komal Thareja
              Participant

                Hi Sourya,

                It appears that your slice utilizes a Port Mirror service, which may not yet be supported by the Slice Viewer. We will check with Yaxue, who works on the Portal, to confirm this. We are working on adding support for this feature in the next release. Apologies for any inconvenience.

                Thanks,

                Komal

                in reply to: Hardware Steering – Connectx6 #8134
                Komal Thareja
                Participant

                  Hi Tanay,

                  Based on the details of the ConnectX-6 from one of the FABRIC VMs and the DPDK documentation you shared (DPDK MLX5 Guide), it appears that the ConnectX-6 available in FABRIC is not supported. We are currently working on integrating new BlueField DPUs, which may provide a suitable solution.


                  [root@Node2 ~]# lspci | grep X-6
                  06:00.0 Ethernet controller: Mellanox Technologies MT28908 Family [ConnectX-6]
                  07:00.0 Ethernet controller: Mellanox Technologies MT28908 Family [ConnectX-6]
                  [root@Node2 ~]# mstconfig -d 06:00.0 query
                  Device #1:
                  ----------
                  Device type: ConnectX6
                  Name: MCX653106A-ECA_Ax
                  Description: ConnectX-6 VPI adapter card; H100Gb/s (HDR100; EDR IB and 100GbE); dual-port QSFP56; PCIe3.0 x16; tall bracket; ROHS R6
                  Device: 06:00.0

                  Thanks,

                  Komal

                  in reply to: Site to Site Connection Issue #8125
                  Komal Thareja
                  Participant

                    Hi Rajiv,

                    L2STS links should work with SharedNICs. Could you please share your slice details where this is not working?

                    Thanks,

                    Komal

                    in reply to: Permission denied for in-slice port mirroring #8113
                    Komal Thareja
                    Participant

                      I also just noticed the attached screenshot. The Permission error is related to SmartNIC usage. To use SmartNICs for your project, you still need the Component.SmartNIC permission.

                      Thanks,
                      Komal

                      in reply to: Permission denied for in-slice port mirroring #8112
                      Komal Thareja
                      Participant

                        Hi Vaneshi,

                        The fix for this was deployed. I will check this again if you are still noticing this error.

                        Please note the pre-requisite for this is that both the listener and the monitored node are in the same slice.

                        Thanks,

                        Komal

                        Komal Thareja
                        Participant

                          Hi Jiri,

                          Could you please share the Fingerprint for your old SSH key which is not expired but not working now?

                          Thanks,

                          Komal

                          in reply to: Issue Connecting via SSH to Specific Node in Topology #8100
                          Komal Thareja
                          Participant

                            Hi Yuanjun,

                            Your slice is already in a Dead state, meaning all associated resources have been released.

                            Please try creating your slice again and let us know if the issue persists. To help us investigate potential problems before expiration, consider extending your slice’s lifetime if you encounter this issue again.


                            Slice Name: byteps_8node_GPN_lamb Slice ID: 0e99c5ea-76d2-4189-ba2e-817a80fa8d29 Project ID: 34a45f8f-be0e-4efc-a91c-38358ce4ca29 Project Name: Ensemble Inference
                            Graph ID: 070d665f-5fcc-467e-9afa-d1d9f2c2f11c
                            Slice owner: { name: orchestrator, guid: orchestrator-guid, oidc_sub_claim: 82e78849-be30-4290-a225-50040c065e4e, email: yuanjun.dai@case.edu}
                            Slice state: Dead
                            Lease time: 2025-01-31 02:15:43+00:00

                            Thanks,

                            Komal

                            in reply to: L2 Interfaces on my slice transitioning to DOWN State #8097
                            Komal Thareja
                            Participant

                              Subject: Network Configuration Issue on Slice VMs

                              Hi Prateek,

                              I checked your Slice. Could you share the VMs and sites where the network configuration was lost?

                              The WASH and STAR site workers were rebooted due to another issue, which may have caused this disruption. Please note that, in the current version, fablib configures interfaces using ip commands, which are not persistent across reboots.

                              We are working on making this configuration reboot persistent. In the meantime, please consider using NetworkManager or netplan to configure the interfaces in a way that persists after a reboot.

                              Additionally, we are addressing the underlying issue that required the worker node reboots.

                              Apologies for the inconvenience, and thank you for your patience!

                              Best,
                              Komal

                              in reply to: Kali machine failing on post_boot_config #8091
                              Komal Thareja
                              Participant

                                Hi Nirmala,

                                Could you please share your slice id?

                                Thanks,
                                Komal

                                in reply to: Error allocating reousrce in RUTG site #8088
                                Komal Thareja
                                Participant

                                  Hi Yuanjun,

                                  We had leaked config on the switch which has been cleared by help from Network Team. Could you please try your slice again? Please let us know if you still see the issue.

                                  Thanks,
                                  Komal

                                Viewing 15 posts - 31 through 45 (of 410 total)