1. Issue Connecting via SSH to Specific Node in Topology
Searching...

Issue Connecting via SSH to Specific Node in Topology

Home › Forums › FABRIC General Questions and Discussion › Issue Connecting via SSH to Specific Node in Topology

Log In Register Lost Password
Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • January 18, 2025 at 10:25 am #8099
    Yuanjun Dai
    Participant

      I am currently working with a topology on the Fabric Testbed platform (Slice ID: 0e99c5ea-76d2-4189-ba2e-817a80fa8d29) and have encountered an issue while attempting to SSH into one of the nodes. Some nodes in the topology work fine, but I am unable to SSH into a specific node with the following IPv6 address:

      ubuntu@2610:e0:a04c:fab2:f816:3eff:fe3d:1

      SSH Command Used:

      ssh -F ssh_config -i silver ubuntu@2610:e0:a04c:fab2:f816:3eff:fe3d:1

      Error Message:

      Warning: Permanently added ‘bastion.fabric-testbed.net,2600:2701:5000:a902::c’ (ECDSA) to the list of known hosts.
      channel 0: open failed: connect failed: Name or service not known
      stdio forwarding failed
      kex_exchange_identification: Connection closed by remote host

      Observations:

      • The problematic IPv6 address ends with 1 (a valid IPv6 address, though uncommon in my experience).
      • Other nodes in the same topology work fine with similar SSH commands.
      • This issue persists across multiple attempts and from different machines.

      Request for Assistance:

      Could you please help investigate this issue? Specifically:

      • Confirm whether the node at 2610:e0:a04c:fab2:f816:3eff:fe3d:1 is properly configured and accessible.
      • Verify if there are any misconfigurations in the topology or the SSH setup for this specific node.
      • Provide guidance if additional configurations or tests are required from my side.

      Please let me know if you need more details, such as logs or configuration files, to assist with the investigation.

      Thank you for your support, and I look forward to hearing from you.

      Best regards,

      January 18, 2025 at 11:11 am #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

      • Author
        Posts
      Viewing 2 posts - 1 through 2 (of 2 total)
      • You must be logged in to reply to this topic.