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.

Sign up for GitHub

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

Jump to bottom

Update vnet-to-vnet-service.md #215

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update vnet-to-vnet-service.md #215

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9398cbd
Update vnet-to-vnet-service.md
marian-pritsak Sep 7, 2022
8a8d7c7
Update vnet-to-vnet-service.md
marian-pritsak Sep 7, 2022
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
38 changes: 38 additions & 0 deletions documentation/vnet2vnet-service/design/vnet-to-vnet-service.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -225,6 +225,12 @@ DASH_VNET_MAPPING_TABLE:Vnet1:10.1.1.1: {
"underlay_ip":101.1.2.3,
"mac_address":F922839922A2
}

DASH_ROUTE_RULE_TABLE:F4939FEFC47E:45654:100.1.2.0/24: {
"priority": "0",
"vnet": "VNET1",
"pa_validation": "true"
}
```

The next sections describe the lookup behavior in the outbound direction. For
Expand Down Expand Up @@ -291,6 +297,38 @@ packet destined to `10.2.5.1`. Below are the processing pipeline (lookup) steps.
2. Select routing table `DASH_ROUTE_TABLE:10.2.5.0/24`. The `action_type` is `drop`.
3. Drop the packet.

## Routing a packet back from 101.1.2.3.

Using the previous configuration, let's analyze the steps involved in routing a
packet destined to our appliance VIP from 101.1.2.0/24.

1. The packet won't have a special VNI, so we assume the inbound direction
2. Perform VNET lookup. It is priority based, matches on VNI, ENI, and prefix. Protocol is not present.
3. The resulting VNET is Vnet1.
4. The inbound routing rule says to perform PA validation as well.
5. We have a PA validation entry for our ENI and SRC PA 101.1.2.3, so the packet is allowed.
6. We decap the packet and encap it to ENI PA 25.1.1.1.

## Routing a packet back from 101.1.2.9.

Using the previous configuration, let's analyze the steps involved in routing a
packet destined to our appliance VIP from 101.1.2.0/24 for which we don't have a mapping entry in our config.

1. The packet won't have a special VNI, so we assume the inbound direction
2. Perform VNET lookup. It is priority based, matches on VNI, ENI, and prefix. Protocol is not present.
3. The resulting VNET is Vnet1.
4. The inbound routing rule says to perform PA validation as well.
5. We don't have a PA validation entry for our ENI and SRC PA 101.1.2.9, so the packet is dropped.

## Counters

In the VNET to VNET scenario, 3 types of counters are required:
1. Route entry counters (inbound and outbound).
2. ACL rule counters.
3. Mapping entry counters.

They are per rule, grouped into buckets, packet counters, byte meters are not required.

## Appendix

### VNET to VNET without DASH optimization
Expand Down