From 2152e390fe4a393452ee22d643a0621129d3a8f3 Mon Sep 17 00:00:00 2001 From: richardyu-ms Date: Fri, 27 May 2022 03:43:21 +0000 Subject: [PATCH] refactor --- doc/sai-ptf/vlan_test_plan.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/sai-ptf/vlan_test_plan.md b/doc/sai-ptf/vlan_test_plan.md index b7c907a295..a3e2d3dc3f 100644 --- a/doc/sai-ptf/vlan_test_plan.md +++ b/doc/sai-ptf/vlan_test_plan.md @@ -139,7 +139,7 @@ For testing, we can use basic FDB APIs to Add the FDB entry into CAM. The Rule a ### Packet example - Tagged packet with VLAN id - When a packet sent to a access port or send out from a access port, we will get a packet with the VLAN id. + When a packet sent to a access port or send out from a access port, we will get a packet without the VLAN id. *In T0, we don't need to test tagged packet.* ```python tagged_packet(eth_dst='00:11:11:11:11:11', @@ -164,8 +164,8 @@ For testing, we can use basic FDB APIs to Add the FDB entry into CAM. The Rule a Testing L3 switch, VLAN-Interface(SVI) in layer3 for packet routing. In this case, it will cover the scenarios like -- Server to T1 -- Server to Server +- Server to T1 (north/south) +- Server to Server (east/west) #### Test the configuration For VLAN-Interface(SVI), it can be configured from a config_db.json. This json file, can be generated from a xml config as below. Base on this configuration we can see what the actual configuration will be.