1. Issue with L2PTP Tunnels
Searching...

Issue with L2PTP Tunnels

Home › Forums › FABRIC General Questions and Discussion › Issue with L2PTP Tunnels

Log In Register Lost Password
Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • November 21, 2025 at 1:59 pm #9191
    Fatih Berkay Sarpkaya
    Participant

      Dear FABRIC team,

      I hope you are doing well. In my experiment, I am using eight separate 20 Gbps tunnels implemented with subinterfaces. Two of these tunnels (the ones using VLAN tags 300 and 600)  have suddenly stopped working. The remaining tunnels function normally.

      These two tunnels previously worked without issues. I have tried reconfiguring the interfaces and rebooting the endpoints, but the problem persists. I am not sure whether the issue is due to a configuration mistake on my side or a problem within the slice network.

      Would it be possible for you to check whether there is an issue with these two tunnels, or let me know if there is something I may have overlooked?

      My slice ID is: fdf2fd5b-b1b0-46ef-b51a-4d55e0fd5c47

      Thank you very much for your help.

      Best regards,

      Fatih Berkay Sarpkaya

      November 21, 2025 at 2:47 pm #9193
      Komal Thareja
      Participant

        Hi Fatih,

        Thanks for reaching out.

        I looked into your slice, and it appears that the two network services associated with VLAN 300 and VLAN 600 are currently in a Closed state. Both reservations show the same ticket update:

        “Insufficient resources: No path available with the requested QoS.”

        Here are the details:

        Reservation ID: 8a83db0f-03f1-44b0-843f-c6e0c2664cfe
        Slice ID: fdf2fd5b-b1b0-46ef-b51a-4d55e0fd5c47
        Resource Type: L2PTP
        State: Closed
        Reason: No path available with requested QoS

        Reservation ID: 257fae2a-28ca-4430-bb85-77864b3d5c25
        Slice ID: fdf2fd5b-b1b0-46ef-b51a-4d55e0fd5c47
        Resource Type: L2PTP
        State: Closed
        Reason: No path available with requested QoS

        This indicates that the system was unable to allocate a viable path for these two tunnels during your most recent renewal window, which is why they are not active now.

        If you would like, you can try the following:

        • Re-declare or re-submit these two network services in your slice.
        • Lower the QoS requirement temporarily to see if a path becomes available.

        Please feel free to reach out if you need help updating the slice or if you would like us to investigate further.

        Best regards,
        Komal

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