You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For instance, when we get a traffic flow with DSCP = 3 on T1, the traffic and bounced back traffic is delivered and remapped as below:
206
+
207
+
1. Traffic from `T1` to `Standby ToR`
208
+
- Traffic mapped to `TC3`, `PG3` and `Queue 3` by port level QoS mapping
209
+
2. Bounced back traffic from `Standby ToR` to `T1`
210
+
- Traffic arrived at `Standby ToR` in `TC3`, `PG3` and `Queue 3` as per port level QoS mapping
211
+
- Packet will be encapped and delivered back to `T1` by `MuxTunnel`
212
+
- The outer `DSCP` is rewritten to `2` as specified in `TC_TO_DSCP_MAP|AZURE_TUNNEL` by SAI attribute `SAI_TUNNEL_ATTR_ENCAP_QOS_TC_AND_COLOR_TO_DSCP_MAP`.
213
+
- Traffic is delivered in `Queue 2` as specified in `TC_TO_QUEUE_MAP|AZURE_TUNNEL` by SAI attribute `SAI_TUNNEL_ATTR_ENCAP_QOS_TC_TO_QUEUE_MAP`
214
+
3. Bounced back traffic from `T1` to `Active ToR`
215
+
- Bounced back traffic arrive at `T1` in `Queue 2` and `PG2` by port level QoS mapping
216
+
- Bounced back traffic will be routed to `Active ToR`
217
+
4. Traffic from `Active ToR` to `Server`
218
+
- Traffic arrived at `Active ToR` and will be decapped and delivered to server
219
+
- The outer `DSCP` is ignored as the `dscp_mode` for `MuxTunnel` is `PIPE`. The inner `DSCP3` is copied to outer layer
220
+
- Traffic is remapped to `TC 3` as specified in `DSCP_TO_TC_MAP|AZURE_TUNNEL` by SAI attribute `SAI_TUNNEL_ATTR_DECAP_QOS_DSCP_TO_TC_MAP`
221
+
- Traffic is remapped to `PG 2` as specified in `TC_TO_PRIORITY_GROUP_MAP|AZURE_TUNNEL` by SAI attribute `SAI_TUNNEL_ATTR_DECAP_QOS_TC_TO_PRIORITY_GROUP_MAP`
222
+
- Traffic is in `Queue 3` as per port level QoS mapping
0 commit comments