Guaranteed Capacity and Traffic Prioritization across the Sites

[Fatih Berkay Sarpkaya]

Hi FABRIC team,

I’m running experiments across a three-site L2P2P topology and would like to better understand how to ensure guaranteed capacity and prioritize traffic.

Guaranteed Capacity

Is there a way to guarantee specific rates (e.g., 10 Gbps or higher) on L2P2P links? Does the FABRIC L2P2P service currently offer any QoS guarantees? If so, how can we configure or verify them?

Traffic Prioritization

• Can DSCP or ToS bits be used to prioritize traffic across L2P2P links?
• Are VLAN PCP bits honored by the underlying infrastructure?
• Is there a way to define QoS profiles or assign traffic priority classes to L2P2P connections?

Switch Behavior

Do intermediate switches in the L2P2P path enforce these priority markings, or is the service best-effort by default?

In a nutshell, I’d appreciate any suggestions on how to achieve guaranteed throughput (preferably high-capacity, e.g., 10 Gbps or more) across sites.

Thank you,

Fatih Berkay Sarpkaya

• This topic was modified 20 hours, 3 minutes ago by Fatih Berkay Sarpkaya.
• This topic was modified 20 hours, 1 minute ago by Fatih Berkay Sarpkaya.

[Komal Thareja]

Hi Fatih,

Thank you for your email and detailed questions.

At this time, FABRIC does not currently support guaranteed capacity or QoS prioritization on L2P2P links. The service operates as best-effort by default, and DSCP/ToS or VLAN PCP markings are not currently enforced across the underlying infrastructure.

That said, we are actively working to support guaranteed QoS using Explicit Route Options (ERO) in the L2P2P service. This capability is planned for inclusion in our upcoming Release 1.9, targeted for deployment in late July/early August. It will provide a way to request L2P2P links with specified bandwidth guarantees and rate-limiting.

We will share more details and guidance on how to configure these options as part of the release.

Please feel free to reach out with any further questions in the meantime.

Best regards,
Komal Thareja

[Author]

Posts