Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update the scale numbers for ExpressRoute gateway bypass scenario. #642

Merged
merged 3 commits into from
Nov 8, 2024
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -77,13 +77,12 @@ The scaling requirement for PL redirect map are listed as below. The metrics are

| Metric | Requirement |
| ------ | ----------- |
| # of ENIs per DPU | 32 |
| # of ENIs per DPU (every 200G) | 32 |
| # of VNET mapping per ENI | 64K |
| # of PPS | 64M |
| VNET mapping change rate (CRUD) | (TBD) |
| # of VNI per ENI | 1 |
| # of MSEE source PA per ENI | 64 |
r12f marked this conversation as resolved.
Show resolved Hide resolved
| # of fast path packets | Same as CPS. 3M per card. |
| # of tunnels | (TBD) |
| # of next hop in each tunnel | (TBD) |

### 4.2. Reliability requirements

Expand Down