Veryx ATTEST TM. Sample Test cases Overview. Conformance Test Suite. Border Gateway Protocol 4-IPv4 (BGP4-IPv4)

Transcription

1 Veryx ATTEST TM Conformance Test Suite Border Gateway Protocol 4-IPv4 (BGP4-IPv4) Sample Test cases Overview Part Number: T / TCLS BGP4-IPV /1.0

2 This page is intentionally left blank.

3 Introduction The Veryx ATTEST TM BGP4 Conformance test suite is designed to enable quick and efficient testing of BGP4 over IPv4 environment as defined by RFC Veryx has developed 200 test cases that test routers for BGP4 conformance over IPv4 environment. The test cases are organized into the following Test Groups: S. No Group Cases Sample Cases 1. BGP Functionality Group (BFG) Connection Request Group (CRG) Error Handling Group (EHG) Finite State Machine Group (FSMG) Local System Configuration Group (LCG) 6-6. Message Format Group (MFG) Message Transaction Group (MTG) Update Message Handling Group (UMHG) 32 2 Total Copyright Veryx Technologies. Page 1

4 The following is a listing of the BGP4 sample test cases. List of sample test cases S. No Title Purpose References ID Conformance Type 1. Update Message - AS_PATH Attribute handling - Internal peer. 2. UPDATE message - Next hop Attribute without explicit configuration. 3. MULTI_EXIT_DISC attribute from EBGP to IBGP speakers To verify that the BGP Speaker does not modify an UPDATE message AS_PATH attribute and advertises a route to an internal peer when the route is learned from another BGP speaker's UPDATE message. To Verify that the BGP Speaker sends an UPDATE message to an Internal Peer without modifying the NEXT_HOP Attribute when it receives an UPDATE message from an external peer. To Verify that the BGP speaker propagates an UPDATE message with MULTI_EXIT_DISC attribute over IBGP to other BGP speakers within the same AS when it receives the UPDATE message with this attribute over EBGP. 4. Initiating TCP Connection To verify that the BGP Speaker automatically initiates and establishes a TCP connection to its peer. 5. NOTIFICATION with Unacceptable Hold Time - Specific To verify that the BGP Speaker sends a NOTIFICATION Message with error subcode as "Unacceptable Hold Time(6)" when it receives an OPEN Message and the Hold time value in the received message is either 1 or 2secs. RFC 4271 Page 25, Section Bullet(a) RFC 4271 Page 26,Section RFC 4271 Page 28,Section RFC 4271 Page 53, Section 8.2.2, Event 3, Page 8, Section 3. RFC 4271 Page 32, Section 6.2.Page 65, Section 8.2.2, Event 22 BFG_013 SHOULD BFG_018 SHOULD BFG_030 MAY CRG_001 MUST EHG_014 MUST Copyright Veryx Technologies. Page 2

5 S. No Title Purpose References ID Conformance Type 6. Update Message Error - Missing Well-Known Attribute - Without ORIGIN 7. Valid UPDATE message without NLRI 8. TcpConnectionFails Event handling 9. NOTIFICATION with Update message Error- UpdateMsgErr- ESTABLISHED state 10. KEEPALIVE Message format To verify that the BGP Speaker sends a NOTIFICATION message with error sub code as "Missing Well-Known Attribute (3) when it receives an UPDATE message without ORIGIN (1) attribute. To verify that the BGP speaker does not send a NOTIFICATION message when it receives an UPDATE message with correct path attributes but no NLRI. To verify that the BGP speaker drops the TCP connection when the BGP FSM receives TcpConnectionFails event in OPENCONFIRM state. To verify that the BGP speaker sends a NOTIFICATION message with error code "Update message Error(3)" when the BGP FSM receives UpdateMsgErr event in ESTABLISHED state. To verify that the BGP Speaker sends a KEEPALIVE message with following i.16 bits of Marker field is set to one. ii. Header length = 19 octets. iii. Message Type = OPEN Message format To verify that the BGP Speaker sends an OPEN message with following 1) 16 bits of Marker field is set to one. 2) Header length >= 29 octets. 3) Message type = 1. 3) Version number!= 0. 4) Autonomous number. 5) Hold timer value. 6) BGP Identifier. 7) Optional parameters length!=0. RFC 4271 Page 33, Section 6.3.Page 74, Section 8.2.2, Event 28 RFC 4271 Page 34, Section 6.3, Para 6.Page 73, Section 8.2.2, Event 23. RFC 4271, Page 68, Section 8.2.2,Event 18 RFC 4271, Page 74, Section 8.2.2, Event 28Page 32, Section 6.3 RFC 4271, Page 21 Section 4.4 RFC 4271 Page 12, Section 4.1, Page 13, Section 4.2. EHG_037 MUST EHG_051 SHOULD FSMG_008 MUST FSMG_026 MUST MFG_002 MUST MFG_003 MUST Copyright Veryx Technologies. Page 3

6 S. No Title Purpose References ID Conformance Type 12. Recognized Transitive Optional Attribute handling in UPDATE message. 13. ATOMIC_AGGREGATE Attribute in Update Message - Propagating to other speakers. To verify that the BGP Speaker accepts the path and sends an UPDATE message with the path to other BGP peers when it receives an UPDATE message with recognized transitive optional attribute. To verify that the BGP Speaker does not remove ATOMIC_AGGREGATE attribute in received UPDATE message when propagates to other BGP speakers. 14. Route Replacement To verify that the BGP Speaker adds or modifies the received path attributes of the previously advertised route and advertises the route to its peer. 15. UPDATE Message- AS Loop To Verify that the BGP Speaker does not propagate a route to other Peers when it detects its own AS number present in the AS_PATH attribute of received BGP route. RFC 4271, Page 24, Section 5, 3rd para RFC 4271, Page 30, Section 5.1.6, Para 1 RFC 4271, Page 9, Section 3.1, Para 4Page 75, Section 9, Para 5 RFC 4271, Page 78, Section 9.1.2, 3rd Para MTG_008 MUST MTG_024 SHOULD UMHG_002 UMHG_004 MAY SHOULD Copyright Veryx Technologies. Page 4

7 About Veryx Technologies Veryx Technologies (formerly Net-O 2 Technologies) provides innovative Verification and Measurement Solutions for the global communications industry. ATTEST solutions verify networking equipment being used for Access, Carrier Ethernet, Data Center, Edge, Enterprise, Industrial and Security. The unique offerings from Veryx enable customers to reduce the time-required-to-test and enhance their time-to-market. Veryx ATTEST TM is the trademark of Veryx Technologies. All other trademarks of respective owners are acknowledged. E mail: info@veryxtech.com Web: Copyright Veryx Technologies. Page 5