1. Mert Cevik

Mert Cevik

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 160 total)
  • Author
    Posts
  • in reply to: Power outage on FABRIC-CLEM #7974
    Mert Cevik
    Moderator

      Dear Experimenters,

      FABRIC-CLEM is back online. VMs are accessible, their PCI devices are re-attached, however IP addresses may need to be re-assigned by the experimenters.

      We have an issue on the dataplane that is interrupting traffic for L2STS and Layer3 services. We will post updates.

       

      in reply to: GPU node is not available #7959
      Mert Cevik
      Moderator

        Hello Yuanjun.

        I don’t have the details of your slice request, but from the STAR status page on the portal, host resources for hosts that have the RTX6000 GPUs (star-w1 and star-w2) have one GPU available. Host star-w2 has a very little amount of RAM. I checked slice creation on both hosts with their available GPUs and it works well. Just, for the VM that would be placed on star-w2, I selected very small amount of RAM and CPU to fit in it.

         

        in reply to: Testbed in maintenance mode #7958
        Mert Cevik
        Moderator

          Dear Experimenters,

          The problem is resolved, FABRIC testbed is operational for slices.

           

          in reply to: Unable to create EDC slice #7955
          Mert Cevik
          Moderator

            I just deleted my slice on EDC with FABnetv4 service. FYI.

            in reply to: FABRIC-CERN in maintenance mode #7870
            Mert Cevik
            Moderator

              Dear Experimenters,

              FABRIC-CERN is available for experiments.

               

              in reply to: Unable to access nodes SRI and MICH #7820
              Mert Cevik
              Moderator

                Slice modification is supported on FABRIC. Yes you can remove the SRI VM and re-create VMs etc. It should be straightforward, but you can also check the link below for examples

                https://github.com/fabric-testbed/jupyter-examples/blob/main/fabric_examples/fablib_api/modify_slice/modify-add-node-network.ipynb

                in reply to: Unable to access nodes SRI and MICH #7818
                Mert Cevik
                Moderator

                  MICH VM (2607:f018:110:11:f816:3eff:fe98:ba32) is online. I confirmed connection over the management network (through FABRIC bastion hosts) works well. It has an ssh key with alias “slice_key” in it (under user ubuntu)

                  SRI VM (192.5.67.209) is online (responding to pings), but it does not allow SSH connections that it’s supposed to allow from the controller node. SSH keys might have been modified somehow. I don’t have much to do with this VM.

                  in reply to: Unable to access nodes SRI and MICH #7816
                  Mert Cevik
                  Moderator

                    You need to provide your slice ID, then we will be able to check.

                    in reply to: FABRIC-LOSA Hardware Problem #7658
                    Mert Cevik
                    Moderator

                      Dear Experimenters,

                      FABRIC-LOSA is back online for slices.

                      in reply to: FABRIC-UTAH Hardware Problem #7637
                      Mert Cevik
                      Moderator

                        Dear Experimenters,

                        FABRIC-UTAH is back online.

                        We could not recover the slivers during the interventions, following slices were affected (their slivers on UTAH node are deleted).

                        • Slice latency_monitoring_slice_20240724(d37afde4-137d-4139-9da3-20734bf46357
                        • Slice monitoring(5c4927ac-27a0-4462-b7ae-7f8d99b2d444
                        • Slice ServiceX_NDN_Proxy_udp_4nodes(8a096617-4998-41d6-867c-fec9dcdd31bc
                        • Slice latency_monitoring_slice_20240919(f0b30035-f516-4c37-b37f-2e9f40159d75
                        in reply to: Slice in Statble Error – Fabric TOKY #7634
                        Mert Cevik
                        Moderator

                          Hello Fatou,

                          Problem should be corrected now. You can try again.

                          1 user thanked author for this post.
                          in reply to: Jupyterhub unresponsive #7632
                          Mert Cevik
                          Moderator

                            Tejas,

                            From the screenshots you attached, it looks like your diskspace is full. You might also consider removing unused files. That might be related to the problem you’re having, second screenshot reveals that problem.

                            Best regards,
                            Mert

                            in reply to: Jupyterhub unresponsive #7631
                            Mert Cevik
                            Moderator

                              Hello Tejas,

                              You can try again. It might be due to the hosting cloud platforms scaling in progress at that time.

                              Best regards,
                              Mert

                              Mert Cevik
                              Moderator

                                For some reason all your VMs management network interfaces are offline. If you share the notebook with us, we can understand if something in the flow might be causing an issue.

                                Mert Cevik
                                Moderator

                                  Can you send the slice ID?

                                Viewing 15 posts - 1 through 15 (of 160 total)