1. Komal Thareja

Komal Thareja

Forum Replies Created

Viewing 15 posts - 256 through 270 (of 445 total)
  • Author
    Posts
  • Komal Thareja
    Participant

      Hi Sanjana,

      I am able to reproduce this issue on MASS. But I was able to get this to work on other sites like SEAT, PSC. Could you please use a different site like SEAT or PSC while we investigate this issue. I will keep you updated with the findings for MASS.

      Thank you for sharing your observations and helping us make the testbed better.

      Thanks,

      Komal

      in reply to: 403 : Forbidden Access to JupyterHub #6612
      Komal Thareja
      Participant

        @Khawar – Could you please try accessing JH again and let me know how it goes?

        Thanks,

        Komal

        Komal Thareja
        Participant

          Hello Nagmat,

          I suspect your bastion keys are expired and hence the failure.

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

          This should update your bastion keys if expired. Please try 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
          Participant

            Just realized you also had problem with network reachability between Chameleon and Fabric nodes. Could you please share your slice ID for FABRIC?

            Also, please check the interface and routes are setup correctly on Chameleon node.

            Komal Thareja
            Participant

              @Sanjana – Chameleon team would be better equipped to help you regarding the failure observed while creating Node on Chameleon. Jupyter Notebook referred in your post uses chameleon python API.

              FABRIC portal doesn’t provide support to provision resources on Chameleon. You would have to use Chameleon Portal to use their Graphical Interface.

              Thanks,

              Komal

              in reply to: Maintenance on Testbed – 02/21/2024 (9:00pm-11:00pm EST) #6596
              Komal Thareja
              Participant

                Maintenance is completed and testbed is ready to use. Happy Slicing on FABRIC!

                in reply to: Maintenance on Testbed – 02/21/2024 (9:00pm-11:00pm EST) #6595
                Komal Thareja
                Participant

                  Unfortunately, we ran into an issue with Network AM. Provisioning for network services is impacted. The testbed would remain in Maintenance until this issue is resolved.

                  We will share updates here once the issue is resolved. Apologies for the inconvenience.

                  in reply to: How to do internode communication? #6589
                  Komal Thareja
                  Participant

                    Hello Ze,

                    You can connect your VMs with various Layer 3 or Layer 2 network service available on FABRIC. Please follow along the examples Networking examplees from start_here.ipynb as shown below.

                    Local Ethernet (Layer 2) could be a good start. More details about the various network services can be found here.

                    • Networking
                      • FABNet IPv4 (Layer 3): Connect to FABRIC’s IPv4 internet (manualautofull auto)
                      • FABNet IPv4 Ext (Layer 3): Connect to FABRIC’s IPv4 internet with external access (manual)
                      • FABNet IPv6 (Layer 3): Connect to FABRIC’s IPv6 internet (manualautofull auto)
                      • FABNet IPv6 Ext (Layer 3): Connect to FABRIC’s IPv6 internet with external access (manual)
                      • Local Ethernet (Layer 2): Create a private local Ethernet network on a FABRIC site (manualautouser defined)
                      • Wide Area Link (Layer 2): Create a private WAN Ethernet link between FABRIC sites (manualautouser defined)
                      • Facility Ports: Connect a FABRIC experiment to an external facility such as Chameleon.
                      • Port Mirroring: Listen in on traffic in FABRIC dataplane using PortMirror service.
                    1 user thanked author for this post.
                    in reply to: cannot install mpi4py #6581
                    Komal Thareja
                    Participant

                      Hello Ze,

                      If VM is created via JH, in the list of Nodes/VM, there is a column which displays the SSH command that can be used to SSH to VM. Please use the SSH command to VMs.

                      Also, following commands may be useful to install mpi4py.

                      sudo apt update -y
                      sudo apt-get -y install python3-pip
                      sudo apt install mpich
                      sudo apt install libopenmpi-dev
                      sudo pip3 install mpi4py

                       

                      NOTE: Please refer to https://learn.fabric-testbed.net/knowledge-base/generating-ssh-configuration-and-ssh-keys/#using-ssh-to-access-your-vms for more guidance on SSH to VMs.

                       

                      Thanks,

                      Komal

                      1 user thanked author for this post.
                      in reply to: Unable to create Slice, Errors at all ticketed nodes #6570
                      Komal Thareja
                      Participant

                        Issue has been resolved now. You slice provisioning should work now.

                        in reply to: ERNETUNREACH when trying to connect to server outside FABRIC #6569
                        Komal Thareja
                        Participant

                          FABRIC only allows SSH and few ICMP messages over the management interface. Hosting services on management network is not recommended. Instead, we recommend using data plane network for your service.

                          FABRIC serves as a secure sandbox, allowing students and researchers to experiment with potentially disruptive and vulnerable software architectures in a protected environment. When connecting external devices, such as laptops or servers, to nodes within a slice, it is crucial to employ secure methods like SSH tunnels. A Jupyter notebook example illustrates how to create SSH tunnels through the FABRIC bastion host. Alternatively, users can utilize personal VPNs like Tailscale for secure connections.

                          Exposing ports to the entire Internet is restricted, reserved only for exceptional cases where alternative solutions are not viable. Moreover, users undertaking such capabilities are responsible for deploying, maintaining, and ensuring the security of experiments, akin to a production data center. IPv4Ext and IPv6Ext services facilitate these capabilities.

                          For newcomers, getting acquainted with SSH tunnels is recommended due to their simplicity and security. If users have additional questions or require further guidance, they are encouraged to reach out.

                          Thanks,

                          Komal

                          in reply to: Unable to create Slice, Errors at all ticketed nodes #6568
                          Komal Thareja
                          Participant

                            Hi Robin,

                            There are libvirt issues on the worker your VMs are being created. We are looking at the issue and will keep you informed. However, could you please try using a different site than AMST in the meanwhile to unblock you?

                            Apologies for the inconvenience!

                            Thanks,

                            Komal

                            in reply to: Cannot SSH to VMs on newy-w2.fabric-testbed.net #6542
                            Komal Thareja
                            Participant

                              No, you don’t need to run “add/remove SSH keys” notebook. By default, when you create a slice, keys specified in your fabric_rc are already added to the VMs.

                              in reply to: Cannot SSH to VMs on newy-w2.fabric-testbed.net #6540
                              Komal Thareja
                              Participant

                                @Sanjana – your config looks correct. Could you please try creating a slice and try SSH? If the SSH still fails, could you please share your public key: /home/fabric/work/fabric_config/slice_key.pub

                                I can verify the correct key is being passed to the VM or not from backend.

                                Thanks,

                                Komal

                                in reply to: Cannot ping gateway upon adding FABNetv4 to node #6533
                                Komal Thareja
                                Participant

                                  @Vaiden – Issue has been resolved. You may have to do the following to resolve in your slice:

                                  • Remove MAX VM and FabNetv4 Network Service connected to it
                                  • Submit
                                  • Add Max VM and FabNetv4 Network Service
                                  • Submit

                                  Thanks,

                                  Komal

                                  1 user thanked author for this post.
                                Viewing 15 posts - 256 through 270 (of 445 total)