sample test plan - veryx technologies · the veryx attesttm bidirectional forwarding detection...

Sample Test Plan

Veryx ATTESTTM Conformance Test Suite

Bidirectional Forwarding Detection (BFD) Sample Test Plan

Part Number: T / TPS – BFD-IPv4 1.1 - 1210/1.0

Page ii

Copyright© 2005-2010 Veryx Technologies Pvt. Ltd. All rights reserved. Veryx ATTESTTM is a trademark of Veryx Technologies Pvt. Ltd. All other trademarks of respective owners are acknowledged. This document may not be copied either in whole or in part by any means or media without permission of Veryx Technologies Pvt. Ltd. THE PROGRAMS FURNISHED ARE PROVIDED ON AN "AS IS" BASIS, WITHOUT ANY WARRANTIES OR REPRESENTATIONS EXPRESS, IMPLIED OR STATUTORY; INCLUDING, WITHOUT LIMITATION, WARRANTIES OF QUALITY, PERFORMANCE, NONINFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. NOR ARE THERE ANY WARRANTIES CREATED BY A COURSE OF DEALING, COURSE OF PERFORMANCE OR TRADE USAGE. LICENSOR DOES NOT WARRANT THAT THE PRODUCTS WILL MEET LICENSEE'S NEEDS OR BE FREE FROM ERRORS, OR THAT THE OPERATION OF THE PRODUCTS WILL BE UNINTERRUPTED.

Page iii

Table of Contents

1. Introduction ............................................................................................................................................ 1 2. Scope of BFD Test Case Groups ............................................................................................................ 3

2.1 BFD Test Case Setup Conventions .............................................................................................. 4 3. Sample Test Cases .................................................................................................................................. 5

3.1 tc_conf_bfd_ffg_001 ................................................................................................................... 5 3.2 tc_conf_bfd_shg_005 .................................................................................................................. 7 3.3 tc_conf_bfd_smg_003 ................................................................................................................. 9 3.4 tc_conf_bfd_smg_004 ............................................................................................................... 11 3.5 tc_conf_bfd_smg_012 ............................................................................................................... 13 3.6 tc_conf_mld_ffg_001................................................................................................................. 15 3.7 tc_conf_bfd_phg_005 ................................................................................................................ 17 3.8 tc_conf_bfd_shg_025 ................................................................................................................ 19

Page iv

This page is intentionally left blank.

ATTEST BFD-IPv4 Conformance Sample Test Plan

Copyright © 2005-2010 Veryx Technologies Page 1

1. Introduction

The Veryx ATTESTTM Bidirectional Forwarding Detection (BFD) Conformance test suite is designed to verify conformance of the Device under Test to the Bidirectional Forwarding Detection protocol as defined by draft-ietf-bfd-base-04.txt, draft-ietf-bfd-v4v6-1hop-04.txt and draft-ietf-bfd-mib-02.txt.

Veryx has developed about 148 test cases that comprehensively test for BFD conformance and are organized into the following Test groups:

1. Frame Format Group (FFG)

2. Session Handling Group (SHG)

3. State Machine Group (SMG)

4. Authentication Support Group (AHG)

5. Timer Handling Group (THG)

6. Echo Packet Handling Group (EPG)

7. Demand Mode Verification Group (DVG)

8. Packet Handling Group (PHG)

9. Management Support Group (MSG)

10. Backward Compatibility Group (BCG)

Each test case has an ID such as given in the example below:

Figure 1. Sample Test Case ID

Test Case (TC) numbers within a group may not always be strictly sequential; also, certain numbers are reserved for future use.

tc_conf_bfd_phg_002.tcl

Item type: test case

Suite type: conformance

Protocol type: BFD Group type: Packet Handling Group

TC Number

File type: tcl script File extension delimiter

This page is intentionally left blank.



2. Scope of BFD Test Case Groups

• Frame Format Group (FFG) - The conformance test cases in the BFD FFG Group verifies the correctness of the format of BFD version 1 and 0 packets e.g. BFD control packet.

• Session Handling Group (SHG) – The conformance test cases in the BFD SHG Group verifies system's role in session initialization, steps in session establishment and demultiplexing of the received BFD packets to proper session

• State Machine Group (SMG) - The conformance test cases in the BFD SMG Group verifies BFD State Machine Changes.

• Authentication Support Group (AHG) – The conformance test cases in BFD AHG Group verifies the five authentication support (Simple Password, Keyed MD5, Meticulous Keyed MD5, Keyed SHA1, and Meticulous Keyed SHA1).

• Timer Handling Group (THG) – The conformance test cases in BFD THG Group verifies BFD Timer Negotiation and Timer Manipulation.

• Echo Packet Handling Group (EPG) – The conformance test cases in BFD EPG Group verifies the reception and transmission of Echo Packets.

• Demand Mode Verification Group (DVG) – The conformance test cases in BFD DVG Group verifies the exchange of BFD Control/Echo packets in Demand mode.

• Packet Handling Group (PHG) – The conformance test cases in BFD PHG Group verifies the criteria for discarding the BFD Control Packets in system.

• Management Support Group (MSG) – The conformance test cases in BFD MSG Group verifies the BFD Management configuration in system.

• Backward Compatibility Group (BCG) – The conformance test cases in BFD BCG Group verifies compatibility of BFD version 1 system with BFD version 0 system.



2.1 BFD Test Case Setup Conventions The following test procedure, test setup and ladder diagram conventions are used in the BFD test cases defined in this document.

Abbreviation Expansion

A Authentication bit D Demand Bit Diag Diagnostic Code DMTI Desired Min. Tx Interval F Final Bit I1 Interface 1 I2 Interface 2 My. Ds My Discriminator P Poll bit RMERI Required Min. Echo Rx Interval RMRI Required Min. Rx Interval RT1 Router 1 RT2 Router 2 RT3 Router 3 Sta Session State Yr. Ds Your Discriminator



3. Sample Test Cases

3.1 tc_conf_bfd_ffg_001 Test Case : tc_conf_bfd_ffg_001 Component Name : NET-O2 ATTEST CONFORMANCE TEST SUITE Module Name : BFD Frame Format Group (FFG) Purpose : To verify that a System supporting BFDv1 (without Auth- entication, without Demand and without Echo support) transmits BFDv1 messages in the correct format. Checking that the following BFD message fields have correct information a) BFD Version field = 1 b) Diagnostic value = 0 c) State = 1 d) P = 0 e) Final = 0 f) Authentication Present = 0 g) Demand = 0 h) Reserved = 0, i) Detect Multiplier != 0 j) Length = 24 k) My Discriminator != 0 l) Your Discriminator = 0 m) Desired Min Tx Interval != 0 n) Required Min Rx Interval != 0 o) Required Min Echo Rx Interval = 0. Reference : draft-ietf-bfd-base-03.txt Sec 4.1 (page 7 - 10 ) Conformance Type : MUST Test Setup : 2 Test Topology : 1 TEE DUT __________ __________ | | | | | | | | | | | | | | | | | RT1 |----------------------------| RT2 | | | (I1) | | | | | | | | | | |__________| |__________|



Ladder Diagram : TEE DUT | | | <enable BFD> | | <enable BFD Session>| | | | BFD Control Pkt(I1)| | (My. Ds != 0,Yr. Ds = 0, | | Ver = 1, Diag = 0, Sta =1| | P = 0, F = 0, A = 0, D = 0| | Resvd =0, Detect Mult != 0| | DMTI != 0 sec, RMRI != 0,RMERI = 0)| |--------------------------------------------<<-------| | | | | | | My. Ds. = Value of My Discriminator(DUT)for the particular session Yr. Ds. = Value of Yr Discriminator(DUT)for the particular session DMTI = Desired Min Tx Interval RMRI = Required Min Rx Interval RMERI = Required Min Echo Rx. Interval Procedure : (Initial Part) Step 1 : Initialization of DUT i. Enable Interface(I1) at DUT. ii. Enable BFD at DUT. iii. Ensure that the DUT interface(I1) is in Forwarding state. Step 2 : Initialization of TEE i. Enable Interface(I1) at TEE. ii. Get destination mac address for Interface(I1). iii. Enable BFD Packet capture at TEE. (Part I) Step 3 : Enable BFD Session at Interface(I1). Step 4 : To verify that DUT transmits BFDv1 Control messages in the correct format i.e. a) BFD Version field = 1 b) Diagnostic value = 0 c) State = 1 d) Poll = 0 e) Final = 0 f) Authentication Present = 0 g) Demand = 0 h) Reserved = 0, i) Detect Multiplier != 0 j) Length = 24 k) My Discriminator != 0 l) Your Discriminator = 0 m) Desired Min Tx Interval != 0 sec n)Required Min Rx Interval !=0 o) Required Min Echo Rx Interval = 0.



3.2 tc_conf_bfd_shg_005 Test Case : tc_conf_bfd_shg_005 Component Name : NET-O2 ATTEST CONFORMANCE TEST SUITE Module Name : BFD Session Handling Group(SHG) Purpose : To verify whether a system declares a session as Down and signals to the remote end via the State (Sta) field in outgoing packets, when demand mode is not active and no control packets are received in the calculated detection time. Reference : draft-ietf-bfd-base-03.txt Sec 6.1 (Page 16) Conformance Type : MUST Test Setup : 1 Test Topology : 1 TEE DUT __________ __________ | | | | | | | | | | | | | | | | | RT1 |----------------------------| RT2 | | | (I1) | | | | | | | | | | |__________| |__________| Ladder Diagram : TEE DUT | | | <enable BFD>| | <Enable BFD Session>| | | | <Wait for Expiry of DUT Detection Time>| | | | BFD Control PDU(I1)| | (Sta = 1)| |--------------------------------------------<<-------| | | | | |BFD Control PDU(I1) | |(My. Ds = MD1, Yr. Ds = MD2 | | Sta = 2) |



|--->>------------------------------------------------| | | | | | BFD Control PDU(I1)| | (Sta = 3)| |--------------------------------------------<<-------| | | | | | < Wait for the expiry of Detection Time of DUT > | | | | | | BFD Control PDU(I1)| | (Diag = 1, Sta = 1)| |--------------------------------------------<<-------| | | | | My. Ds. = Value of My Discriminator(DUT)for the particular session Yr. Ds. = Value of Yr Discriminator(DUT)for the particular session Procedure : (Initial Part) Step 1 : Initialization of DUT i. Enable Interface(I1) at DUT. ii. Enable BFD at DUT. iii. Ensure that the DUT interface(I1) is in Forwarding state. iv. Enable BFD Session at Interface(I1). Step 2 : Initialization of TEE i. Enable Interface(I1) at TEE. ii. Get destination mac address for interface(I1). iii. Enable BFD Packet capture at TEE. (Part I) Step 3 : Wait for the DUT Detect timeout to ensure that state of DUT = 1 (Down), Step 4 : Receive BFD Control Packet from DUT at Interface I1 with State = 1 (Down).Get the My Discriminator value(MD2). Step 5 : Send BFD Control Packet from TEE to DUT at Interface I1 with Your Discriminator = MD2 , State = 2(Init). Step 6 : Receive BFD Control Packet from DUT at Interface I1 with State = 3 (Up). Step 7 : Wait for the Expiry of Detection Time of DUT. Step 8 : To verify that DUT sends BFD Control packet at Interface I1 with State = 1 (Down), Diag = 1 (Control Detection Time Expired).



3.3 tc_conf_bfd_smg_003 Test Case : tc_conf_bfd_smg_003 Component Name : NET-O2 ATTEST CONFORMANCE TEST SUITE Module Name : BFD State Machine Group (SMG) Purpose : To verify whether the system session state associated with a session remains in Down state when it receives a BFD Control packet from the remote system and the packet signals Up state. Reference : draft-ietf-bfd-base-03.txt Sec 6.2 (Page 16) Conformance Type : MUST Test Setup : 1 Test Topology : 1 TEE DUT __________ __________ | | | | | | | | | | | | | | | | | RT1 |----------------------------| RT2 | | | (I1) | | | | | | | | | | |__________| |__________| Ladder Diagram : TEE DUT | | | <enable BFD>| | <Enable BFD Session>| | | | <Wait for Expiry of DUT Detection Time>| | | | BFD Control PDU(I1)| | (Sta = 1)| |--------------------------------------------<<-------| | | |BFD Control PDU(I1) | |(My. Ds = MD1, Yr. Ds = MD2 | | Sta = 3) | |--->>------------------------------------------------|



| | | | | BFD Control PDU(I1)| | (Sta = 1)| |--------------------------------------------<<-------| | | My. Ds. = Value of My Discriminator(DUT)for the particular session Yr. Ds. = Value of Yr Discriminator(DUT)for the particular session Procedure : (Initial Part) Step 1 : Initialization of DUT i. Enable Interface(I1) at DUT. ii. Enable BFD at DUT. iii. Ensure that the DUT interface(I1) is in Forwarding state. iv. Enable BFD Session at Interface(I1). Step 2 : Initialization of TEE i. Enable Interface(I1) at TEE. ii. Get destination mac address for interface(I1). iii. Enable BFD Packet capture at TEE. (Part I) Step 3 : Wait for the DUT Detect timeout to ensure that state of DUT = 1 (Down), Step 4 : Receive BFD Control Packet from DUT at Interface I1 with State = 1 (Down). Store My Discriminator (MD2). Step 5 : Send BFD Control Packet from TEE to DUT at Interface I1 with State = 3 (Up), Yr. Discriminator = MD2. Step 6 : To verify that DUT sends BFD Control packet at Interface I1 with State = 1 (Down).



3.4 tc_conf_bfd_smg_004 Test Case : tc_conf_bfd_smg_004 Component Name : NET-O2 ATTEST CONFORMANCE TEST SUITE Module Name : BFD State Machine Group (SMG) Purpose : To verify whether the system session state associated with a session remains in Init state when it receives a BFD Control packet from the remote system and the packet signals Down state. Reference : draft-ietf-bfd-base-03.txt Sec 6.2 (Page 17) Conformance Type : MUST Test Setup : 1 Test Topology : 1 TEE DUT __________ __________ | | | | | | | | | | | | | | | | | RT1 |----------------------------| RT2 | | | (I1) | | | | | | | | | | |__________| |__________| Ladder Diagram : TEE DUT | | | <enable BFD>| | <Enable BFD Session>| | | | <Wait for Expiry of DUT Detection Time>| | | | BFD Control PDU(I1)| | (Sta = 1)| |--------------------------------------------<<-------| | | |BFD Control PDU(I1) | |(My. Ds = MD1, Yr. Ds = 0 | | Sta = 1) | |--->>------------------------------------------------| | |



| | | BFD Control PDU(I1)| | (Sta = 2)| |--------------------------------------------<<-------| | | |BFD Control PDU(I1) | |(My. Ds = MD1, Yr. Ds = 0 | | Sta = 1) | |--->>------------------------------------------------| | | | | | BFD Control PDU(I1)| | (Sta = 2)| |--------------------------------------------<<-------| | | My. Ds. = Value of My Discriminator(DUT)for the particular session Yr. Ds. = Value of Yr Discriminator(DUT)for the particular session Procedure : (Initial Part) Step 1 : Initialization of DUT i. Enable Interface(I1) at DUT. ii. Enable BFD at DUT. iii. Ensure that the DUT interface(I1) is in Forwarding state. iv. Enable BFD Session at Interface(I1). Step 2 : Initialization of TEE i. Enable Interface(I1) at TEE. ii. Get destination mac address for interface(I1). iii. Enable BFD Packet capture at TEE. (Part I) Step 3 : Wait for the DUT Detect timeout to ensure that state of DUT = 1 (Down), Step 4 : Receive BFD Control Packet from DUT at Interface I1 with State = 1 (Down). Step 5 : Send BFD Control Packet from TEE to DUT at Interface I1 with State = 1 (Down), Yr. Discriminator = 0. Step 6 : Receive BFD Control Packet from DUT at Interface I1 with State = 2 (Init). Step 7 : Send BFD Control Packet from TEE to DUT at Interface I1 with State = 1 (Down), Yr. Discriminator = 0. Step 8 : To verify that DUT sends BFD Control packet at Interface I1 with State = 2 (Init).



3.5 tc_conf_bfd_smg_012 Test Case : tc_conf_bfd_smg_012 Component Name : NET-O2 ATTEST CONFORMANCE TEST SUITE Module Name : BFD State Machine Group (SMG) Purpose : To verify whether the system session state associated with a session moves from Init state to Down state and sets bfd.LocalDiag to 3 (Neighbor signaled session down) when it receives a BFD Control packet from the remote system and the packet signals AdminDown Reference : draft-ietf-bfd-base-03.txt Sec 6.7.6 (Page 32) Conformance Type : MUST Test Setup : 1 Test Topology : 1 TEE DUT __________ __________ | | | | | | | | | | | | | | | | | RT1 |----------------------------| RT2 | | | (I1) | | | | | | | | | | |__________| |__________| Ladder Diagram : TEE DUT | | | <enable BFD>| | <Enable BFD Session>| | | | <Wait for Expiry of DUT Detection Time>| | | | BFD Control PDU(I1)| | (Sta = 1)| |--------------------------------------------<<-------| | | | | |BFD Control PDU(I1) | |(My. Ds = MD1, Yr. Ds = 0 | | Sta = 1) | |--->>------------------------------------------------| | | | | | BFD Control PDU(I1)|



| (Sta = 2)| |--------------------------------------------<<-------| | | | | |BFD Control PDU(I1) | |(My. Ds = MD1, Yr. Ds = MD2 | | Sta = 0) | |--->>------------------------------------------------| | | | | | BFD Control PDU(I1)| | (Diag = 3, Sta = 1)| |--------------------------------------------<<-------| | | | | My. Ds. = Value of My Discriminator(DUT) for the particular session Yr. Ds. = Value of Yr Discriminator(DUT) for the particular session Procedure : (Initial Part) Step 1 : Initialization of DUT i. Enable Interface(I1) at T. ii. Enable BFD at DUT. iii. Ensure that the DUT interface(I1) is in Forwarding state. iv. Enable BFD Session at Interface(I1). Step 2 : Initialization of TEE i. Enable Interface(I1) at TEE. ii. Get destination mac address for interface(I1). iii. Enable BFD Packet capture at TEE. (Part I) Step 3 : Wait for the DUT Detect timeout to ensure that state of DUT = 1 (Down), Step 4 : Receive BFD Control Packet from DUT at Interface I1 with State = 1 (Down) and Store My Discriminator(MD2). Step 5 : Send BFD Control Packet from TEE to DUT at Interface I1 with State = 1 (Down) and Yr Discriminator = 0. Step 6 : Receive BFD Control Packet from DUT at Interface I1 with State = 2 (Init). Step 7 : Send BFD Control Packet from TEE to DUT at Interface I1 with State = 0 (AdminDown) and Yr. Discriminator = MD2. Step 8 : To verify that DUT sends BFD Control packet at Interface I1 with State = 1 (Down), Diagnostic = 3 (Neighbor Signaled Session Down).



3.6 tc_conf_mld_ffg_001 Test Case : tc_conf_bfd_ffg_001 Component Name : NET-O2 ATTEST CONFORMANCE TEST SUITE Module Name : BFD Frame Format Group (FFG) Purpose : To verify that a System supporting BFDv1 (without Auth- entication, without Demand and without Echo support) transmits BFDv1 messages in the correct format. Checking that the following BFD message fields have correct information a) BFD Version field = 1 b) Diagnostic value = 0 c) State = 1 d) P = 0 e) Final = 0 f) Authentication Present = 0 g) Demand = 0 h) Reserved = 0, i) Detect Multiplier != 0 j) Length = 24 k) My Discriminator != 0 l) Your Discriminator = 0 m) Desired Min Tx Interval != 0 n) Required Min Rx Interval != 0 o) Required Min Echo Rx Interval = 0. Reference : draft-ietf-bfd-base-03.txt Sec 4.1 (page 7 - 10 ) Conformance Type : MUST Test Setup : 2 Test Topology : 1 TEE DUT __________ __________ | | | | | | | | | | | | | | | | | RT1 |----------------------------| RT2 | | | (I1) | | | | | | | | | | |__________| |__________| Ladder Diagram : TEE DUT | | | <enable BFD> | | <enable BFD Session>| | | | BFD Control Pkt(I1)| | (My. Ds != 0,Yr. Ds = 0, |



| Ver = 1, Diag = 0, Sta =1| | P = 0, F = 0, A = 0, D = 0| | Resvd =0, Detect Mult != 0| | DMTI != 0 sec, RMRI != 0,RMERI = 0)| |--------------------------------------------<<-------| | | | | | | My. Ds. = Value of My Discriminator(DUT)for the particular session Yr. Ds. = Value of Yr Discriminator(DUT)for the particular session DMTI = Desired Min Tx Interval RMRI = Required Min Rx Interval RMERI = Required Min Echo Rx. Interval Procedure : (Initial Part) Step 1 : Initialization of DUT i. Enable Interface(I1) at DUT. ii. Enable BFD at DUT. iii. Ensure that the DUT interface(I1) is in Forwarding state. Step 2 : Initialization of TEE i. Enable Interface(I1) at TEE. ii. Get destination mac address for Interface(I1). iii. Enable BFD Packet capture at TEE. (Part I) Step 3 : Enable BFD Session at Interface(I1). Step 4 : To verify that DUT transmits BFDv1 Control messages in the correct format i.e. a) BFD Version field = 1 b) Diagnostic value = 0 c) State = 1 d) Poll = 0 e) Final = 0 f) Authentication Present = 0 g) Demand = 0 h) Reserved = 0, i) Detect Multiplier != 0 j) Length = 24 k) My Discriminator != 0 l) Your Discriminator = 0 m) Desired Min Tx Interval != 0 sec n)Required Min Rx Interval !=0 o) Required Min Echo Rx Interval = 0.



3.7 tc_conf_bfd_phg_005 Test Case : tc_conf_bfd_phg_005 Component Name : NET-O2 ATTEST CONFORMANCE TEST SUITE Module Name : BFD Packet handling Group (PHG) Purpose : To verify whether the system discards a received BFD control packet if the Detect Mult field is zero. Reference : draft-ietf-bfd-base-03.txt Sec 6.7.6 (Page 31) Conformance Type : MUST Test Setup : 2 Test Topology : 1 TEE DUT __________ __________ | | | | | | | | | | | | | | | | | RT1 |----------------------------| RT2 | | | (I1) | | | | | | | | | | |__________| |__________| Ladder Diagram : TEE DUT | | | <enable BFD> | | <Enable BFD Session>| | | | | | BFD Control PDU(I1)| | (My. Ds != 0, Yr. Ds = 0)| |--------------------------------------------<<-------| | | | | |BFD Control PDU(I1) | |(My. Ds != 0, Yr. Ds = 0 | | Detect Mult = 0) | |----->>----------------------------------------------|



| | | | | BFD Control PDU(I1)| | (Yr. Ds = 0)| |--------------------------------------------<<-------| | | | | My. Ds. = Value of My Discriminator for the particular session Yr. Ds. = Value of Yr Discriminator for the particular session Procedure : (Initial Part) Step 1 : Initialization of DUT i. Enable Interface(I1) at DUT. ii. Enable BFD at DUT. iii. Ensure that the DUT interface(I1) is in Forwarding state. Step 2 : Initialization of TEE i. Enable Interface(I1) at TEE. ii. Get destination mac address for interface(I1). iii. Enable BFD Packet capture at TEE. (Part I) Step 3 : Enable BFD Session at Interface(I1). Step 4 : Receive BFD Control Packet from DUT at Interface I1 with My Discriminator != 0, Yr Discriminator = 0. Get My Discriminator(MD2) value from BFD Control Packet. Step 5 : Send BFD Control Packet from TEE to DUT at Interface I1 with My Discriminator != 0, Yr. Discriminator = 0, Detect Mult = 0. Step 6 : To verify that the DUT sends the BFD Control Packet at Interface (I1) with Yr Discriminator = 0.



3.8 tc_conf_bfd_shg_025 Test Case : tc_conf_bfd_shg_025 Component Name : NET-O2 ATTEST CONFORMANCE TEST SUITE Module Name : BFD Session Handling Group(SHG) Purpose : To verify that a BFDv1 system updates the your discriminator value with the my discriminator value in the received BFD control packet associated with the session. Reference : draft-ietf-BFDv1-base-03.txt Sec 4.1 (Page 10) Conformance Type : MUST Test Setup : 2 Test Topology : 1 TEE DUT __________ __________ | | | | | | | | | | | | | | | | | RT1 |----------------------------| RT2 | | | (I1) | | | | | | | | | | |__________| |__________| Ladder Diagram : TEE DUT | | | <enable BFD>| | <enable BFD Session>| | | | | | BFD Control PDU(I1)| | (My. Ds != 0,Yr. Ds = 0)| |--------------------------------------------<<-------| | | | | |BFD Control PDU(I1) | |(My. Ds = MD1,Yr. Ds = 0 | | Sta = 1) |



|----->>----------------------------------------------| | | | | | BFD Control PDU(I1)| | (My. Ds = MD2,Yr. Ds = MD1)| |--------------------------------------------<<-------| | | | | | | My. Ds. = Value of My Discriminator(DUT)for the particular session Yr. Ds. = Value of Yr Discriminator(DUT)for the particular session Procedure : (Initial Part) Step 1 : Initialization of DUT i. Enable Interface(I1) at DUT. ii. Enable BFD at DUT. iii. Ensure that the DUT interface(I1) is in Forwarding state. Step 2 : Initialization of TEE i. Enable Interface(I1) at TEE. ii. Get destination mac address for interface(I1). iii. Enable BFD Packet capture at TEE. (Part I) Step 3: Enable BFD Session at Interface(I1). Step 4 : Receive BFD Control packet from DUT at interface I1 with My Discriminator != 0, Yr Discriminator = 0.Store My Discriminator (MD2). Step 5 : Send BFD Control packet from TEE to DUT with My Discriminator = MD1 Yr Discriminator = 0,Sta = 1. Step 6 : To verify that the DUT sends BFD Control Packet with My Discriminator = MD2, Yr Discriminator = MD1.

sample test plan - veryx technologies · the veryx attesttm bidirectional forwarding detection...

Documents