FRR-7.3-Snapcraft

Build: #2 failed

Job: BGP4 IPv4 Tests was successful

Build log

The build generated 2,186 lines of output.The output is too long and has been truncated to the last 1,000 lines. Download or view full build log.

14-Feb-2020 09:15:51 Test Reference
14-Feb-2020 09:15:51 NEGATIVE
14-Feb-2020 09:15:51 RFC4271, Sect. 6.3, p 32,
14-Feb-2020 09:15:51 UPDATE message error handling
14-Feb-2020 09:15:51 Test Classification
14-Feb-2020 09:15:51 MUST
14-Feb-2020 09:16:51 Test ANVL-BGP4-15.2: Passed
14-Feb-2020 09:16:51
14-Feb-2020 09:16:53 Test ANVL-BGP4-15.3 executing
14-Feb-2020 09:16:53 Test Summary
14-Feb-2020 09:16:53 If any recognized attribute has Attribute Flags that conflict with the
14-Feb-2020 09:16:53 Attribute Type Code, then the Error Subcode MUST be set to Attribute
14-Feb-2020 09:16:53 Flags Error. The Data field MUST contain the erroneous attribute
14-Feb-2020 09:16:53 (type, length and value).
14-Feb-2020 09:16:53 (This test checks for mandatory well-known attributes, Optional Bit
14-Feb-2020 09:16:53 and Internal Peer)
14-Feb-2020 09:16:53 Test Reference
14-Feb-2020 09:16:53 NEGATIVE
14-Feb-2020 09:16:53 RFC4271, Sect. 6.3, p 32,
14-Feb-2020 09:16:53 UPDATE message error handling
14-Feb-2020 09:16:53 Test Classification
14-Feb-2020 09:16:53 MUST
14-Feb-2020 09:18:11 Test ANVL-BGP4-15.3: Passed
14-Feb-2020 09:18:11
14-Feb-2020 09:18:13 Test ANVL-BGP4-15.4 executing
14-Feb-2020 09:18:13 Test Summary
14-Feb-2020 09:18:13 If any recognized attribute has Attribute Flags that conflict with
14-Feb-2020 09:18:13 the Attribute Type Code, then the Error Subcode MUST be set to Attribute
14-Feb-2020 09:18:13 Flags Error. The Data field MUST contain the erroneous attribute
14-Feb-2020 09:18:13 (type, length and value).
14-Feb-2020 09:18:13 (Note : This test checks for mandatory well-known attributes,
14-Feb-2020 09:18:13 Transitive Bit and External Peer)
14-Feb-2020 09:18:13 Test Reference
14-Feb-2020 09:18:13 NEGATIVE
14-Feb-2020 09:18:13 RFC4271, Sect. 6.3, p 32,
14-Feb-2020 09:18:13 UPDATE message error handling
14-Feb-2020 09:18:13 Test Classification
14-Feb-2020 09:18:13 MUST
14-Feb-2020 09:19:12 Test ANVL-BGP4-15.4: Passed
14-Feb-2020 09:19:12
14-Feb-2020 09:19:14 Test ANVL-BGP4-15.5 executing
14-Feb-2020 09:19:14 Test Summary
14-Feb-2020 09:19:14 If any recognized attribute has Attribute Flags that conflict with
14-Feb-2020 09:19:14 the Attribute Type Code, then the Error Subcode MUST be set to Attribute
14-Feb-2020 09:19:14 Flags Error. The Data field MUST contain the erroneous attribute
14-Feb-2020 09:19:14 (type, length and value).
14-Feb-2020 09:19:14 (Note : This test checks for mandatory well-known attributes,
14-Feb-2020 09:19:14 Transitive Bit and Internal Peer)
14-Feb-2020 09:19:14 Test Reference
14-Feb-2020 09:19:14 NEGATIVE
14-Feb-2020 09:19:14 RFC4271, Sect. 6.3, p 32,
14-Feb-2020 09:19:14 UPDATE message error handling
14-Feb-2020 09:19:14 Test Classification
14-Feb-2020 09:19:14 MUST
14-Feb-2020 09:20:34 Test ANVL-BGP4-15.5: Passed
14-Feb-2020 09:20:34
14-Feb-2020 09:20:37 Test ANVL-BGP4-15.6 executing
14-Feb-2020 09:20:37 Test Summary
14-Feb-2020 09:20:37 If any recognized attribute has Attribute Flags that conflict with
14-Feb-2020 09:20:37 the Attribute Type Code, then the Error Subcode MUST be set to Attribute
14-Feb-2020 09:20:37 Flags Error. The Error Data field MUST contain the erroneous attribute
14-Feb-2020 09:20:37 (type, length and value).
14-Feb-2020 09:20:37 (Note : This test checks for mandatory well-known attributes,
14-Feb-2020 09:20:37 Partial Bit and External Peer)
14-Feb-2020 09:20:37 Test Reference
14-Feb-2020 09:20:37 NEGATIVE
14-Feb-2020 09:20:37 RFC4271, Sect. 6.3, p 32,
14-Feb-2020 09:20:37 UPDATE message error handling
14-Feb-2020 09:20:37 Test Classification
14-Feb-2020 09:20:37 MUST
14-Feb-2020 09:21:40 Test ANVL-BGP4-15.6: Passed
14-Feb-2020 09:21:40
14-Feb-2020 09:21:42 Test ANVL-BGP4-15.7 executing
14-Feb-2020 09:21:42 Test Summary
14-Feb-2020 09:21:42 If any recognized attribute has Attribute Flags that conflict with
14-Feb-2020 09:21:42 the Attribute Type Code, then the Error Subcode MUST be set to Attribute
14-Feb-2020 09:21:42 Flags Error. The Data field MUST contain the erroneous attribute
14-Feb-2020 09:21:42 (type, length and value).
14-Feb-2020 09:21:42 (Note : This test checks for mandatory well-known attributes,
14-Feb-2020 09:21:42 Partial Bit and Internal Peer)
14-Feb-2020 09:21:42 Test Reference
14-Feb-2020 09:21:42 NEGATIVE
14-Feb-2020 09:21:42 RFC4271, Sect. 6.3, p 32,
14-Feb-2020 09:21:42 UPDATE message error handling
14-Feb-2020 09:21:42 Test Classification
14-Feb-2020 09:21:42 MUST
14-Feb-2020 09:23:07 Test ANVL-BGP4-15.7: Passed
14-Feb-2020 09:23:07
14-Feb-2020 09:23:09 Test ANVL-BGP4-15.8 executing
14-Feb-2020 09:23:09 Test Summary
14-Feb-2020 09:23:09 If any recognized attribute has Attribute Flags that conflict with
14-Feb-2020 09:23:09 the Attribute Type Code, then the Error Subcode MUST be set to Attribute
14-Feb-2020 09:23:09 Flags Error. The Data field MUST contain the erroneous attribute.
14-Feb-2020 09:23:09 (type, length and value).
14-Feb-2020 09:23:09 (Note : This test checks for MULTI_EXIT_DISC
14-Feb-2020 09:23:09 (optional non-transitive) attribute and for Optional Bit)
14-Feb-2020 09:23:09 Test Reference
14-Feb-2020 09:23:09 NEGATIVE
14-Feb-2020 09:23:09 RFC4271, Sect. 6.3, p 32,
14-Feb-2020 09:23:09 UPDATE message error handling
14-Feb-2020 09:23:09 Test Classification
14-Feb-2020 09:23:09 MUST
14-Feb-2020 09:23:33 Test ANVL-BGP4-15.8: Passed
14-Feb-2020 09:23:33
14-Feb-2020 09:23:35 Test ANVL-BGP4-15.9 executing
14-Feb-2020 09:23:35 Test Summary
14-Feb-2020 09:23:35 If any recognized attribute has Attribute Flags that conflict
14-Feb-2020 09:23:35 with the Attribute Type Code, then the Error Subcode MUST be set to
14-Feb-2020 09:23:35 Attribute Flags Error. The Data field MUST contain the erroneous
14-Feb-2020 09:23:35 attribute (type, length and value).
14-Feb-2020 09:23:35 (This test checks for MULTI_EXIT_DISC
14-Feb-2020 09:23:35 (optional non-transitive) attribute and for Transitive Bit)
14-Feb-2020 09:23:35 Test Reference
14-Feb-2020 09:23:35 NEGATIVE
14-Feb-2020 09:23:35 RFC4271, Sect. 6.3, p 32,
14-Feb-2020 09:23:35 UPDATE message error handling.
14-Feb-2020 09:23:35 Test Classification
14-Feb-2020 09:23:35 MUST
14-Feb-2020 09:23:59 Test ANVL-BGP4-15.9: Passed
14-Feb-2020 09:23:59
14-Feb-2020 09:24:01 Test ANVL-BGP4-15.10 executing
14-Feb-2020 09:24:01 Test Summary
14-Feb-2020 09:24:01 If any recognized attribute has Attribute Flags that conflict with
14-Feb-2020 09:24:01 the Attribute Type Code, then the Error Subcode MUST be set to Attribute
14-Feb-2020 09:24:01 Flags Error. The Data field MUST contain the erroneous attribute
14-Feb-2020 09:24:01 (type, length and value).
14-Feb-2020 09:24:01 (Note : This test checks for MULTI_EXIT_DISC (optional non-transitive)
14-Feb-2020 09:24:01 attribute and for Partial Bit)
14-Feb-2020 09:24:01 Test Reference
14-Feb-2020 09:24:01 NEGATIVE
14-Feb-2020 09:24:01 RFC4271, Sect. 6.3, p 32,
14-Feb-2020 09:24:01 UPDATE message error handling
14-Feb-2020 09:24:01 Test Classification
14-Feb-2020 09:24:01 MUST
14-Feb-2020 09:24:25 Test ANVL-BGP4-15.10: Passed
14-Feb-2020 09:24:25
14-Feb-2020 09:24:27 Test ANVL-BGP4-15.15 executing
14-Feb-2020 09:24:27 Test Summary
14-Feb-2020 09:24:27 If any recognized attribute has Attribute Length that conflicts with
14-Feb-2020 09:24:27 the expected length (based on the attribute type code), then the
14-Feb-2020 09:24:27 Error Subcode MUST be set to Attribute Length Error. The Error Data
14-Feb-2020 09:24:27 field MUST contain the erroneous attribute (type, length and value).
14-Feb-2020 09:24:27 (Note: This test checks by sending incorrect length for ORIGIN
14-Feb-2020 09:24:27 attribute)
14-Feb-2020 09:24:27 Test Reference
14-Feb-2020 09:24:27 NEGATIVE
14-Feb-2020 09:24:27 RFC4271, Sect. 6.3, p 32,
14-Feb-2020 09:24:27 UPDATE message error handling
14-Feb-2020 09:24:27 Test Classification
14-Feb-2020 09:24:27 MUST
14-Feb-2020 09:24:51 Test ANVL-BGP4-15.15: Passed
14-Feb-2020 09:24:51
14-Feb-2020 09:24:53 Test ANVL-BGP4-15.16 executing
14-Feb-2020 09:24:53 Test Summary
14-Feb-2020 09:24:53 If any recognized attribute has Attribute Length that conflicts with
14-Feb-2020 09:24:53 the expected length (based on the attribute type code), then the
14-Feb-2020 09:24:53 Error Subcode MUST be set to Attribute Length Error. The Error Data
14-Feb-2020 09:24:53 field MUST contain the erroneous attribute (type, length and value).
14-Feb-2020 09:24:53 (Note: This test checks by sending incorrect length for NEXT_HOP
14-Feb-2020 09:24:53 attribute)
14-Feb-2020 09:24:53 Test Reference
14-Feb-2020 09:24:53 NEGATIVE
14-Feb-2020 09:24:53 RFC4271, Sect. 6.3, p 32,
14-Feb-2020 09:24:53 UPDATE message error handling
14-Feb-2020 09:24:53 Test Classification
14-Feb-2020 09:24:53 MUST
14-Feb-2020 09:25:17 Test ANVL-BGP4-15.16: Passed
14-Feb-2020 09:25:17
14-Feb-2020 09:25:19 Test ANVL-BGP4-15.17 executing
14-Feb-2020 09:25:19 Test Summary
14-Feb-2020 09:25:19 If any recognized attribute has Attribute Length that conflicts with
14-Feb-2020 09:25:19 the expected length (based on the attribute type code), then the
14-Feb-2020 09:25:19 Error Subcode MUST be set to Attribute Length Error. The Data field
14-Feb-2020 09:25:19 MUST contain the erroneous attribute (type, length and value).
14-Feb-2020 09:25:19 (This test checks by sending incorrect length for MULTI_EXIT_DISC
14-Feb-2020 09:25:19 attribute)
14-Feb-2020 09:25:19 Test Reference
14-Feb-2020 09:25:19 NEGATIVE
14-Feb-2020 09:25:19 RFC4271, Sect. 6.3, p 32,
14-Feb-2020 09:25:19 UPDATE message error handling
14-Feb-2020 09:25:19 Test Classification
14-Feb-2020 09:25:19 MUST
14-Feb-2020 09:25:42 Test ANVL-BGP4-15.17: Passed
14-Feb-2020 09:25:42
14-Feb-2020 09:25:44 Test ANVL-BGP4-15.18 executing
14-Feb-2020 09:25:44 Test Summary
14-Feb-2020 09:25:44 If any recognized attribute has Attribute Length that conflicts with
14-Feb-2020 09:25:44 the expected length (based on the attribute type code), then the
14-Feb-2020 09:25:44 Error Subcode MUST be set to Attribute Length Error. The Data field
14-Feb-2020 09:25:44 MUST contain the erroneous attribute (type, length and value).
14-Feb-2020 09:25:44 (This test checks by sending incorrect length for LOCAL_PREF
14-Feb-2020 09:25:44 attribute)
14-Feb-2020 09:25:44 Test Reference
14-Feb-2020 09:25:44 NEGATIVE
14-Feb-2020 09:25:44 RFC4271, Sect. 6.3, p 32,
14-Feb-2020 09:25:44 UPDATE message error handling
14-Feb-2020 09:25:44 Test Classification
14-Feb-2020 09:25:44 MUST
14-Feb-2020 09:26:07 Test ANVL-BGP4-15.18: Passed
14-Feb-2020 09:26:07
14-Feb-2020 09:26:09 Test ANVL-BGP4-15.21 executing
14-Feb-2020 09:26:09 Test Summary
14-Feb-2020 09:26:09 If any of the well-known mandatory attributes are not present, then
14-Feb-2020 09:26:09 the Error Subcode MUST be set to Missing Well-known Attribute. The Data
14-Feb-2020 09:26:09 field MUST contain the Attribute Type Code of the missing, well-known
14-Feb-2020 09:26:09 attribute.
14-Feb-2020 09:26:09 (This test checks for IBGP)
14-Feb-2020 09:26:09 Test Reference
14-Feb-2020 09:26:09 NEGATIVE
14-Feb-2020 09:26:09 RFC4271, Sect. 6.3, p 33,
14-Feb-2020 09:26:09 UPDATE message error handling
14-Feb-2020 09:26:09 Test Classification
14-Feb-2020 09:26:09 MUST
14-Feb-2020 09:27:33 Test ANVL-BGP4-15.21: Passed
14-Feb-2020 09:27:33
14-Feb-2020 09:27:35 Test ANVL-BGP4-15.22 executing
14-Feb-2020 09:27:35 Test Summary
14-Feb-2020 09:27:35 If any of the mandatory well-known attributes are not present, then
14-Feb-2020 09:27:35 the Error Subcode MUST be set to Missing Well-known Attribute. The Data
14-Feb-2020 09:27:35 field MUST contain the Attribute Type Code of the missing well-known
14-Feb-2020 09:27:35 attribute.
14-Feb-2020 09:27:35 (This test checks for EBGP)
14-Feb-2020 09:27:35 Test Reference
14-Feb-2020 09:27:35 NEGATIVE
14-Feb-2020 09:27:35 RFC4271, Sect. 6.3, p 33,
14-Feb-2020 09:27:35 UPDATE message error handling
14-Feb-2020 09:27:35 Test Classification
14-Feb-2020 09:27:35 MUST
14-Feb-2020 09:28:37 Test ANVL-BGP4-15.22: Passed
14-Feb-2020 09:28:37
14-Feb-2020 09:28:40 Test ANVL-BGP4-15.24 executing
14-Feb-2020 09:28:40 Test Summary
14-Feb-2020 09:28:40 If the ORIGIN attribute has an undefined value, then the Error
14-Feb-2020 09:28:40 Subcode MUST be set to Invalid Origin Attribute. The Data field
14-Feb-2020 09:28:40 MUST contain the unrecognized attribute (type, length and field).
14-Feb-2020 09:28:40 Test Reference
14-Feb-2020 09:28:40 NEGATIVE
14-Feb-2020 09:28:40 RFC4271, Sect. 6.3, p 32,
14-Feb-2020 09:28:40 UPDATE message error handling
14-Feb-2020 09:28:40 Test Classification
14-Feb-2020 09:28:40 MUST
14-Feb-2020 09:29:02 Test ANVL-BGP4-15.24: Passed
14-Feb-2020 09:29:02
14-Feb-2020 09:29:03 Test ANVL-BGP4-15.25 executing
14-Feb-2020 09:29:03 Test Summary
14-Feb-2020 09:29:03 If the NEXT_HOP attribute field is syntactically incorrect,
14-Feb-2020 09:29:03 then the Error Subcode MUST be set to Invalid NEXT_HOP Attribute.
14-Feb-2020 09:29:03 The Data field MUST contain the incorrect attribute
14-Feb-2020 09:29:03 (type, length and value).
14-Feb-2020 09:29:03 Test Reference
14-Feb-2020 09:29:03 NEGATIVE
14-Feb-2020 09:29:03 RFC4271, Sect. 6.3, p 33,
14-Feb-2020 09:29:03 UPDATE message error handling
14-Feb-2020 09:29:03 Test Classification
14-Feb-2020 09:29:03 MUST
14-Feb-2020 09:29:26 Test ANVL-BGP4-15.25: Passed
14-Feb-2020 09:29:26
14-Feb-2020 09:29:29 Test ANVL-BGP4-15.26 executing
14-Feb-2020 09:29:29 Test Summary
14-Feb-2020 09:29:29 If the NEXT_HOP attribute is semantically incorrect, the error
14-Feb-2020 09:29:29 SHOULD be logged, and the the route SHOULD be ignored.  In this
14-Feb-2020 09:29:29 case, a NOTIFICATION message SHOULD not be sent.
14-Feb-2020 09:29:29 Test Reference
14-Feb-2020 09:29:29 NEGATIVE
14-Feb-2020 09:29:29 RFC4271, Sect.6.3, page 33,
14-Feb-2020 09:29:29 UPDATE message error handling.
14-Feb-2020 09:29:29 Test Classification
14-Feb-2020 09:29:29 MUST
14-Feb-2020 09:31:32 Test ANVL-BGP4-15.26: Passed
14-Feb-2020 09:31:32
14-Feb-2020 09:31:34 Test ANVL-BGP4-15.27 executing
14-Feb-2020 09:31:34 Test Summary
14-Feb-2020 09:31:34 If the AS_PATH attribute is syntactically incorrect, then the Error
14-Feb-2020 09:31:34 Subcode MUST be set to Malformed AS_PATH.
14-Feb-2020 09:31:34 Test Reference
14-Feb-2020 09:31:34 NEGATIVE
14-Feb-2020 09:31:34 RFC4271, Sect. 6.3, p 33,
14-Feb-2020 09:31:34 UPDATE message error handling
14-Feb-2020 09:31:34 Test Classification
14-Feb-2020 09:31:34 MUST
14-Feb-2020 09:31:57 Test ANVL-BGP4-15.27: Passed
14-Feb-2020 09:31:57
14-Feb-2020 09:31:59 Test ANVL-BGP4-15.29 executing
14-Feb-2020 09:31:59 Test Summary
14-Feb-2020 09:31:59 If any attribute appears more than once in the UPDATE message, then
14-Feb-2020 09:31:59 the Error Subcode MUST be set to Malformed Attribute List.
14-Feb-2020 09:31:59 (This test checks for EBGP)
14-Feb-2020 09:31:59 Test Reference
14-Feb-2020 09:31:59 NEGATIVE
14-Feb-2020 09:31:59 RFC4271, Sect. 6.3, p 35,
14-Feb-2020 09:31:59 UPDATE message error handling
14-Feb-2020 09:31:59 Test Classification
14-Feb-2020 09:31:59 MUST
14-Feb-2020 09:34:03 Test ANVL-BGP4-15.29: Passed
14-Feb-2020 09:34:03
14-Feb-2020 09:34:05 Test ANVL-BGP4-15.30 executing
14-Feb-2020 09:34:05 Test Summary
14-Feb-2020 09:34:05 If any attribute appears more than once in the UPDATE message, then
14-Feb-2020 09:34:05 the Error Subcode MUST be set to Malformed Attribute List.
14-Feb-2020 09:34:05 (This test checks for IBGP)
14-Feb-2020 09:34:05 Test Reference
14-Feb-2020 09:34:05 NEGATIVE
14-Feb-2020 09:34:05 RFC4271, Sect. 6.3, p 34,
14-Feb-2020 09:34:05 UPDATE message error handling
14-Feb-2020 09:34:05 Test Classification
14-Feb-2020 09:34:05 MUST
14-Feb-2020 09:36:08 Test ANVL-BGP4-15.30: Passed
14-Feb-2020 09:36:08
14-Feb-2020 09:36:11 Test ANVL-BGP4-15.31 executing
14-Feb-2020 09:36:11 Test Summary
14-Feb-2020 09:36:11 The NLRI field in the UPDATE message is checked for syntactic
14-Feb-2020 09:36:11 validity. If the field is syntactically incorrect, then the Error
14-Feb-2020 09:36:11 Subcode MUST be set to Invalid Network Field.
14-Feb-2020 09:36:11 Test Reference
14-Feb-2020 09:36:11 NEGATIVE
14-Feb-2020 09:36:11 RFC4271, Sect. 6.3, p 34,
14-Feb-2020 09:36:11 UPDATE message error handling
14-Feb-2020 09:36:11 Test Classification
14-Feb-2020 09:36:11 MUST
14-Feb-2020 09:36:34 Test ANVL-BGP4-15.31: Passed
14-Feb-2020 09:36:34
14-Feb-2020 09:36:36 Test ANVL-BGP4-15.32 executing
14-Feb-2020 09:36:36 Test Summary
14-Feb-2020 09:36:36 An UPDATE message that contains correct path attributes, but
14-Feb-2020 09:36:36 no NLRI, SHALL be treated as a valid UPDATE message.
14-Feb-2020 09:36:36 (This test checks for EBGP)
14-Feb-2020 09:36:36 Test Reference
14-Feb-2020 09:36:36 RFC4271, Sect. 6.3, p 34,
14-Feb-2020 09:36:36 UPDATE message error handling
14-Feb-2020 09:36:36 Test Classification
14-Feb-2020 09:36:36 MUST
14-Feb-2020 09:38:03 Test ANVL-BGP4-15.32: Passed
14-Feb-2020 09:38:03
14-Feb-2020 09:38:05 Test ANVL-BGP4-16.1 executing
14-Feb-2020 09:38:05 Test Summary
14-Feb-2020 09:38:05 If a peer sends a NOTIFICATION message, and the receiver of the message
14-Feb-2020 09:38:05 detects an an error in that message, ....
14-Feb-2020 09:38:05 Any such error (e.g., an unrecognized Error Code or Error Subcode)
14-Feb-2020 09:38:05 SHOULD be noticed, logged locally, and brought to the attention of the
14-Feb-2020 09:38:05 administration of the peer.
14-Feb-2020 09:38:05 Test Reference
14-Feb-2020 09:38:05 NEGATIVE
14-Feb-2020 09:38:05 RFC4271, Sect. 6.4, p 34,
14-Feb-2020 09:38:05 NOTIFICATION message error handling
14-Feb-2020 09:38:05 Test Classification
14-Feb-2020 09:38:05 SHOULD
14-Feb-2020 09:39:33 Test ANVL-BGP4-16.1: Passed
14-Feb-2020 09:39:33
14-Feb-2020 09:39:35 Test ANVL-BGP4-17.1 executing
14-Feb-2020 09:39:35 Test Summary
14-Feb-2020 09:39:35 If a system does not receive successive KEEPALIVE and/or UPDATE
14-Feb-2020 09:39:35 and/or NOTIFICATION messages within the period specified in the
14-Feb-2020 09:39:35 Hold Time field of the OPEN message, then the NOTIFICATION
14-Feb-2020 09:39:35 message with Hold Timer Expired Error Code is sent and the BGP
14-Feb-2020 09:39:35 connection is closed.
14-Feb-2020 09:39:35 Test Reference
14-Feb-2020 09:39:35 NEGATIVE
14-Feb-2020 09:39:35 RFC4271, Sect. 6.5, p 34,
14-Feb-2020 09:39:35 OPEN Message Format
14-Feb-2020 09:39:35 Test Classification
14-Feb-2020 09:39:35 MUST
14-Feb-2020 09:41:27 Test ANVL-BGP4-17.1: Passed
14-Feb-2020 09:41:27
14-Feb-2020 09:41:30 Test ANVL-BGP4-18.1 executing
14-Feb-2020 09:41:30 Test Summary
14-Feb-2020 09:41:30 In absence of any fatal errors (that are indicated in this section),
14-Feb-2020 09:41:30 a BGP peer MAY choose at any given time, to close its BGP Connection
14-Feb-2020 09:41:30 by sending the NOTIFICATION message with Error Code Cease.
14-Feb-2020 09:41:30 Test Reference
14-Feb-2020 09:41:30 RFC4271, Sect. 6.7, p 35,
14-Feb-2020 09:41:30 Cease
14-Feb-2020 09:41:30 Test Classification
14-Feb-2020 09:41:30 MAY
14-Feb-2020 09:41:55 Test ANVL-BGP4-18.1: Passed
14-Feb-2020 09:41:55
14-Feb-2020 09:41:57 Test ANVL-BGP4-18.2 executing
14-Feb-2020 09:41:57 Test Summary
14-Feb-2020 09:41:57 The Cease NOTIFICATION message MUST NOT be used when a fatal error
14-Feb-2020 09:41:57 indicated by this section does exist.
14-Feb-2020 09:41:57 (Note : This test checks the case when the error is in message Header)
14-Feb-2020 09:41:57 Test Reference
14-Feb-2020 09:41:57 NEGATIVE
14-Feb-2020 09:41:57 RFC4271, Sect. 6.7, p 35,
14-Feb-2020 09:41:57 Cease
14-Feb-2020 09:41:57 Test Classification
14-Feb-2020 09:41:57 MUST
14-Feb-2020 09:43:00 Test ANVL-BGP4-18.2: Passed
14-Feb-2020 09:43:00
14-Feb-2020 09:43:02 Test ANVL-BGP4-18.3 executing
14-Feb-2020 09:43:02 Test Summary
14-Feb-2020 09:43:02 The Cease NOTIFICATION message MUST NOT be used when a fatal error
14-Feb-2020 09:43:02 indicated by this section does exist.
14-Feb-2020 09:43:02 (Note : This test checks the case when the error is in OPEN message)
14-Feb-2020 09:43:02 Test Reference
14-Feb-2020 09:43:02 NEGATIVE
14-Feb-2020 09:43:02 RFC4271, Sect. 6.7, p 35, Cease
14-Feb-2020 09:43:02 Test Classification
14-Feb-2020 09:43:02 MUST
14-Feb-2020 09:45:00 Test ANVL-BGP4-18.3: Passed
14-Feb-2020 09:45:00
14-Feb-2020 09:45:03 Test ANVL-BGP4-19.1 executing
14-Feb-2020 09:45:03 Test Summary
14-Feb-2020 09:45:03 In case when a connection collision is detected, if the value of the
14-Feb-2020 09:45:03 local BGP Identifier is less than the remote one, the local system
14-Feb-2020 09:45:03 closes BGP Connection that already exists (the one that is already in
14-Feb-2020 09:45:03 the OpenConfirm state), and accepts BGP4 Connection initiated by the
14-Feb-2020 09:45:03 remote system.
14-Feb-2020 09:45:03 Test Reference
14-Feb-2020 09:45:03 RFC4271, Sect. 6.8, p 36,
14-Feb-2020 09:45:03 Connection collision detection
14-Feb-2020 09:45:03 Test Classification
14-Feb-2020 09:45:03 MUST
14-Feb-2020 09:46:36 Test ANVL-BGP4-19.1: Passed
14-Feb-2020 09:46:36
14-Feb-2020 09:46:38 Test ANVL-BGP4-19.2 executing
14-Feb-2020 09:46:38 Test Summary
14-Feb-2020 09:46:38 In case when a connection collision is detected, if the value of the
14-Feb-2020 09:46:38 local BGP Identifier is greater than the remote one, the local system
14-Feb-2020 09:46:38 closes newly created BGP4 Connection (the one associated with the newly
14-Feb-2020 09:46:38 received OPEN message), and continues to use the existing one (the one
14-Feb-2020 09:46:38 that is already in the OpenConfirm state).
14-Feb-2020 09:46:38 Test Reference
14-Feb-2020 09:46:38 RFC4271, Sect. 6.8, p 36,
14-Feb-2020 09:46:38 Connection collision detection
14-Feb-2020 09:46:38 Test Classification
14-Feb-2020 09:46:38 MUST
14-Feb-2020 09:48:11 Test ANVL-BGP4-19.2: Passed
14-Feb-2020 09:48:11
14-Feb-2020 09:48:13 Test ANVL-BGP4-19.3 executing
14-Feb-2020 09:48:13 Test Summary
14-Feb-2020 09:48:13 Unless allowed via configuration, a connection collision with an
14-Feb-2020 09:48:13 existing BGP4 Connection that is in Established state causes closing
14-Feb-2020 09:48:13 of the newly created connection.
14-Feb-2020 09:48:13 Test Reference
14-Feb-2020 09:48:13 RFC4271, Sect. 6.8, p 36,
14-Feb-2020 09:48:13 Connection collision detection
14-Feb-2020 09:48:13 Test Classification
14-Feb-2020 09:48:13 MUST
14-Feb-2020 09:49:45 Test ANVL-BGP4-19.3: Passed
14-Feb-2020 09:49:45
14-Feb-2020 09:49:47 Test ANVL-BGP4-19.4 executing
14-Feb-2020 09:49:47 Test Summary
14-Feb-2020 09:49:47 Note that a connection collision cannot be detected with connections
14-Feb-2020 09:49:47 that are in Idle, or Connect, or Active states.
14-Feb-2020 09:49:47 (Note: This test is for Connect state)
14-Feb-2020 09:49:47 Test Reference
14-Feb-2020 09:49:47 RFC4271, Sect. 6.8, p 36,
14-Feb-2020 09:49:47 Connection collision detection
14-Feb-2020 09:49:47 Test Classification
14-Feb-2020 09:49:47 MUST
14-Feb-2020 09:51:18 Test ANVL-BGP4-19.4: Passed
14-Feb-2020 09:51:18
14-Feb-2020 09:51:21 Test ANVL-BGP4-19.5 executing
14-Feb-2020 09:51:21 Test Summary
14-Feb-2020 09:51:21 Note that a connection collision cannot be detected with connections
14-Feb-2020 09:51:21 that are in Idle, or Connect, or Active states.
14-Feb-2020 09:51:21 (This test is for Active State)
14-Feb-2020 09:51:21 Test Reference
14-Feb-2020 09:51:21 RFC4271, Sect. 6.8, p 36,
14-Feb-2020 09:51:21 Connection collision detection
14-Feb-2020 09:51:21 Test Classification
14-Feb-2020 09:51:21 MUST
14-Feb-2020 09:53:02 Test ANVL-BGP4-19.5: Passed
14-Feb-2020 09:53:02
14-Feb-2020 09:53:03 Test ANVL-BGP4-20.1 executing
14-Feb-2020 09:53:03 Test Summary
14-Feb-2020 09:53:03 If the version number contained in the Version field of the received
14-Feb-2020 09:53:03 OPEN message is not supported, then the Error Subcode MUST be set to
14-Feb-2020 09:53:03 Unsupported Version Number. The Data field is a a 2-octet unsigned
14-Feb-2020 09:53:03 integer, which indicates the largest, locally supported version number
14-Feb-2020 09:53:03 less than the version the remote BGP peer bid (as indicated in the
14-Feb-2020 09:53:03 received OPEN message)
14-Feb-2020 09:53:03 Test Reference
14-Feb-2020 09:53:03 If an open attempt fails with an Error Code OPEN Message Error, and
14-Feb-2020 09:53:03 an Error Subcode Unsupported Version Number.......
14-Feb-2020 09:53:03 If the two peers do support one or more common versions, then they will
14-Feb-2020 09:53:03 rapidly determine the highest common version.
14-Feb-2020 09:53:03 NEGATIVE
14-Feb-2020 09:53:03 RFC4271, Sect. 6.2, p 31,
14-Feb-2020 09:53:03 OPEN message error handling
14-Feb-2020 09:53:03 RFC4271, Sect. 7, p 36,
14-Feb-2020 09:53:03 BGP Version Negotiation
14-Feb-2020 09:53:03 Test Classification
14-Feb-2020 09:53:03 MUST
14-Feb-2020 09:53:31 Test ANVL-BGP4-20.1: Passed
14-Feb-2020 09:53:31
14-Feb-2020 09:53:32 Test ANVL-BGP4-21.1 executing
14-Feb-2020 09:53:32 Test Summary
14-Feb-2020 09:53:32 At Idle state in response to the Manual Start event the local system
14-Feb-2020 09:53:32 initiates a TCP connection to other BGP peer.
14-Feb-2020 09:53:32 Test Reference
14-Feb-2020 09:53:32 RFC4271, Sect. 8.2.2, p 53,
14-Feb-2020 09:53:32 BGP Finite State machine
14-Feb-2020 09:53:32 Test Classification
14-Feb-2020 09:53:32 MUST
14-Feb-2020 09:54:00 Test ANVL-BGP4-21.1: Passed
14-Feb-2020 09:54:00
14-Feb-2020 09:54:02 Test ANVL-BGP4-21.2 executing
14-Feb-2020 09:54:02 Test Summary
14-Feb-2020 09:54:02 At idle state in response to the Manual Start event the local system
14-Feb-2020 09:54:02 listens for a connection that may be initiated by the remote BGP peer
14-Feb-2020 09:54:02 Test Reference
14-Feb-2020 09:54:02 RFC4271, Sect. 8.2.2, p 53,
14-Feb-2020 09:54:02 BGP Finite State machine
14-Feb-2020 09:54:02 Test Classification
14-Feb-2020 09:54:02 MUST
14-Feb-2020 09:54:26 Test ANVL-BGP4-21.2: Passed
14-Feb-2020 09:54:26
14-Feb-2020 09:54:28 Test ANVL-BGP4-21.3 executing
14-Feb-2020 09:54:28 Test Summary
14-Feb-2020 09:54:28 While in Active state in response to the ConnectRetry timer expired
14-Feb-2020 09:54:28 event :
14-Feb-2020 09:54:28 - continues to listen for TCP connection that may be initiated by
14-Feb-2020 09:54:28 a remote BGP peer
14-Feb-2020 09:54:28 Test Reference
14-Feb-2020 09:54:28 RFC4271, Sect. 8.2.2, p 59,
14-Feb-2020 09:54:28 BGP Finite State machine
14-Feb-2020 09:54:28 Test Classification
14-Feb-2020 09:54:28 MAY
14-Feb-2020 09:55:12 Test ANVL-BGP4-21.3: Passed
14-Feb-2020 09:55:12
14-Feb-2020 09:55:14 Test ANVL-BGP4-21.4 executing
14-Feb-2020 09:55:14 Test Summary
14-Feb-2020 09:55:14 Start event is ignored in the OpenSent state.
14-Feb-2020 09:55:14 Test Reference
14-Feb-2020 09:55:14 RFC4271, Sect. 8.2.2, p 63,
14-Feb-2020 09:55:14 BGP Finite State machine
14-Feb-2020 09:55:14 Test Classification
14-Feb-2020 09:55:14 MUST
14-Feb-2020 09:57:34 Test ANVL-BGP4-21.4: Passed
14-Feb-2020 09:57:34
14-Feb-2020 09:57:36 Test ANVL-BGP4-21.5 executing
14-Feb-2020 09:57:36 Test Summary
14-Feb-2020 09:57:36 In state OpenSent if the Hold Timer expires, the local system sends
14-Feb-2020 09:57:36 NOTIFICATION message with Error Code Hold Timer Expired.
14-Feb-2020 09:57:36 Test Reference
14-Feb-2020 09:57:36 NEGATIVE
14-Feb-2020 09:57:36 RFC4271, Sect. 8.2.2, p 64,
14-Feb-2020 09:57:36 BGP Finite State machine
14-Feb-2020 09:57:36 Test Classification
14-Feb-2020 09:57:36 MUST
14-Feb-2020 10:01:06 Test ANVL-BGP4-21.5: Passed
14-Feb-2020 10:01:06
14-Feb-2020 10:01:08 Test ANVL-BGP4-21.6 executing
14-Feb-2020 10:01:08 Test Summary
14-Feb-2020 10:01:08 In OpenSent state if a TcpConnectionFails event is received,
14-Feb-2020 10:01:08 the local system:
14-Feb-2020 10:01:08 - closes the BGP4 Connection
14-Feb-2020 10:01:08 Test Reference
14-Feb-2020 10:01:08 RFC4271, Sect. 8.2.2, p 64,
14-Feb-2020 10:01:08 BGP Finite State machine
14-Feb-2020 10:01:08 Test Classification
14-Feb-2020 10:01:08 MUST
14-Feb-2020 10:01:46 Test ANVL-BGP4-21.6: Passed
14-Feb-2020 10:01:46
14-Feb-2020 10:01:48 Test ANVL-BGP4-21.8 executing
14-Feb-2020 10:01:48 Test Summary
14-Feb-2020 10:01:48 At OpenSent state if there are no errors in the OPEN message, the
14-Feb-2020 10:01:48 local system:
14-Feb-2020 10:01:48 - sends a KEEPALIVE message, and
14-Feb-2020 10:01:48 - sets a KeepaliveTimer
14-Feb-2020 10:01:48 Test Reference
14-Feb-2020 10:01:48 RFC4271, Sect. 8.2.2, p 65,
14-Feb-2020 10:01:48 BGP Finite State machine
14-Feb-2020 10:01:48 Test Classification
14-Feb-2020 10:01:48 MUST
14-Feb-2020 10:02:47 Test ANVL-BGP4-21.8: Passed
14-Feb-2020 10:02:47
14-Feb-2020 10:02:50 Test ANVL-BGP4-21.9 executing
14-Feb-2020 10:02:50 Test Summary
14-Feb-2020 10:02:50 Any start event is ignored in the OpenConfirm state.
14-Feb-2020 10:02:50 Test Reference
14-Feb-2020 10:02:50 RFC4271, Sect. 8.2.2, p 67,
14-Feb-2020 10:02:50 BGP Finite State machine
14-Feb-2020 10:02:50 Test Classification
14-Feb-2020 10:02:50 MUST
14-Feb-2020 10:05:45 Test ANVL-BGP4-21.9: Passed
14-Feb-2020 10:05:45
14-Feb-2020 10:05:47 Test ANVL-BGP4-21.11 executing
14-Feb-2020 10:05:47 Test Summary
14-Feb-2020 10:05:47 In OpenConfirm state in response to a ManualStop event initiated by
14-Feb-2020 10:05:47 the operator, the local system:
14-Feb-2020 10:05:47 - changes its state to Idle.
14-Feb-2020 10:05:47 Test Reference
14-Feb-2020 10:05:47 RFC4271, Sect. 8.2.2, p 67,
14-Feb-2020 10:05:47 BGP Finite State machine
14-Feb-2020 10:05:47 Test Classification
14-Feb-2020 10:05:47 MUST
14-Feb-2020 10:08:23 Test ANVL-BGP4-21.11: Passed
14-Feb-2020 10:08:23
14-Feb-2020 10:08:25 Test ANVL-BGP4-21.12 executing
14-Feb-2020 10:08:25 Test Summary
14-Feb-2020 10:08:25 Any start event is ignored in the Established state.
14-Feb-2020 10:08:25 Test Reference
14-Feb-2020 10:08:25 RFC4271, Sect. 8.2.2, p 71,
14-Feb-2020 10:08:25 BGP Finite State machine
14-Feb-2020 10:08:25 Test Classification
14-Feb-2020 10:08:25 MUST
14-Feb-2020 10:10:38 Test ANVL-BGP4-21.12: Passed
14-Feb-2020 10:10:38
14-Feb-2020 10:10:40 Test ANVL-BGP4-21.13 executing
14-Feb-2020 10:10:40 Test Summary
14-Feb-2020 10:10:40 In the Established state, if the KeepaliveTimer_Expires event occurs
14-Feb-2020 10:10:40 the local system:
14-Feb-2020 10:10:40 - sends a KEEPALIVE message, and
14-Feb-2020 10:10:40 - restarts its KeepaliveTimer unless the negotiated HoldTime value
14-Feb-2020 10:10:40 is zero.
14-Feb-2020 10:10:40 Test Reference
14-Feb-2020 10:10:40 RFC4271, Sect. 8.2.2, p 72,
14-Feb-2020 10:10:40 BGP Finite State machine
14-Feb-2020 10:10:40 Test Classification
14-Feb-2020 10:10:40 MUST
14-Feb-2020 10:12:03 Test ANVL-BGP4-21.13: Passed
14-Feb-2020 10:12:03
14-Feb-2020 10:12:05 Test ANVL-BGP4-21.14 executing
14-Feb-2020 10:12:05 Test Summary
14-Feb-2020 10:12:05 In the Established state, if the local system receives an UPDATE or
14-Feb-2020 10:12:05 KEEPALIVE message, it restarts its Hold Timer, if the negotiated
14-Feb-2020 10:12:05 Hold Time value is non-zero.
14-Feb-2020 10:12:05 Test Reference
14-Feb-2020 10:12:05 NEGATIVE
14-Feb-2020 10:12:05 RFC4271, Sect. 8.2.2, p 74,
14-Feb-2020 10:12:05 BGP Finite State machine
14-Feb-2020 10:12:05 Test Classification
14-Feb-2020 10:12:05 MUST
14-Feb-2020 10:13:58 Test ANVL-BGP4-21.14: Passed
14-Feb-2020 10:13:58
14-Feb-2020 10:14:00 Test ANVL-BGP4-22.1 executing
14-Feb-2020 10:14:00 Test Summary
14-Feb-2020 10:14:00 An UPDATE message may be received only in the Established state.
14-Feb-2020 10:14:00 (Note : This test checks by sending Update Message
14-Feb-2020 10:14:00 immediately after TCP connection is establised)
14-Feb-2020 10:14:00 Test Reference
14-Feb-2020 10:14:00 NEGATIVE
14-Feb-2020 10:14:00 RFC4271, Sect. 9, p 75,
14-Feb-2020 10:14:00 UPDATE Message Handling
14-Feb-2020 10:14:00 Test Classification
14-Feb-2020 10:14:00 MAY
14-Feb-2020 10:14:21 Test ANVL-BGP4-22.1: Passed
14-Feb-2020 10:14:21
14-Feb-2020 10:14:23 Test ANVL-BGP4-22.2 executing
14-Feb-2020 10:14:23 Test Summary
14-Feb-2020 10:14:23 An UPDATE message may be received only in the Established state.
14-Feb-2020 10:14:23 (This test checks by sending Update Message in OpenConfirm state)
14-Feb-2020 10:14:23 Test Reference
14-Feb-2020 10:14:23 NEGATIVE
14-Feb-2020 10:14:23 RFC4271, Sect. 9, p 75,
14-Feb-2020 10:14:23 UPDATE Message Handling
14-Feb-2020 10:14:23 Test Classification
14-Feb-2020 10:14:23 MAY
14-Feb-2020 10:14:51 Test ANVL-BGP4-22.2: Passed
14-Feb-2020 10:14:51
14-Feb-2020 10:14:52 Test ANVL-BGP4-22.3 executing
14-Feb-2020 10:14:52 Test Summary
14-Feb-2020 10:14:52 If the UPDATE message contains a non-empty WITHDRAWN ROUTES field,
14-Feb-2020 10:14:52 the previously advertised routes whose destinations (expressed as IP
14-Feb-2020 10:14:52 prefixes) are contained in this field SHALL be removed from the
14-Feb-2020 10:14:52 Adj-RIB-In.
14-Feb-2020 10:14:52 Test Reference
14-Feb-2020 10:14:52 RFC4271, Sect.9 p.75,
14-Feb-2020 10:14:52 UPDATE Message Handling
14-Feb-2020 10:14:52 Test Classification
14-Feb-2020 10:14:52 MUST
14-Feb-2020 10:16:08 Test ANVL-BGP4-22.3: Passed
14-Feb-2020 10:16:08
14-Feb-2020 10:16:09 Test ANVL-BGP4-23.1 executing
14-Feb-2020 10:16:09 Test Summary
14-Feb-2020 10:16:09 Phase 1 is responsible for calculating the degree of preference
14-Feb-2020 10:16:09 for each route received from an external peer
14-Feb-2020 10:16:09 Test Reference
14-Feb-2020 10:16:09 RFC4271, Sect.9.1, page 76,
14-Feb-2020 10:16:09 Decision Process
14-Feb-2020 10:16:09 Test Classification
14-Feb-2020 10:16:09 MUST
14-Feb-2020 10:17:22 Test ANVL-BGP4-23.1: Passed
14-Feb-2020 10:17:22
14-Feb-2020 10:17:23 Test ANVL-BGP4-23.2 executing
14-Feb-2020 10:17:23 Test Summary
14-Feb-2020 10:17:23 If the route is learned from an internal peer, the value of LOCAL_PREF
14-Feb-2020 10:17:23 attribute shall be taken as the degree of preference.
14-Feb-2020 10:17:23 Test Reference
14-Feb-2020 10:17:23 RFC 4271, Sect.9.1.1, p.77,
14-Feb-2020 10:17:23 Phase 1: Calculation of Degree of Preference
14-Feb-2020 10:17:23 Test Classification
14-Feb-2020 10:17:23 MUST
14-Feb-2020 10:18:32 Test ANVL-BGP4-23.2: Passed
14-Feb-2020 10:18:32
14-Feb-2020 10:18:33 Test ANVL-BGP4-24.1 executing
14-Feb-2020 10:18:33 Test Summary
14-Feb-2020 10:18:33 If the AS_PATH attribute of a BGP route contains an AS loop, the BGP
14-Feb-2020 10:18:33 route should be excluded from the Phase 2 decision function.
14-Feb-2020 10:18:33 Test Reference
14-Feb-2020 10:18:33 NEGATIVE
14-Feb-2020 10:18:33 RFC4271, Sect. 9.1.2, p 78
14-Feb-2020 10:18:33 Phase 2: Route Selection
14-Feb-2020 10:18:33 Test Classification
14-Feb-2020 10:18:33 SHOULD
14-Feb-2020 10:19:28 Test ANVL-BGP4-24.1: Passed
14-Feb-2020 10:19:28
14-Feb-2020 10:19:29 Test ANVL-BGP4-24.6 executing
14-Feb-2020 10:19:29 Test Summary
14-Feb-2020 10:19:29 If the NEXT_HOP attribute of a BGP route depicts an address that is
14-Feb-2020 10:19:29 not resolvable, or it would become unresolvable if the route was
14-Feb-2020 10:19:29 installed in the routing table the BGP route MUST be excluded from
14-Feb-2020 10:19:29 the Phase 2 decision function.
14-Feb-2020 10:19:29 Test Reference
14-Feb-2020 10:19:29 RFC4271, Sect.9.1.2 p.78,
14-Feb-2020 10:19:29 Phase 2: Route Selection
14-Feb-2020 10:19:29 Test Classification
14-Feb-2020 10:19:29 MUST
14-Feb-2020 10:21:28 Test ANVL-BGP4-24.6: Passed
14-Feb-2020 10:21:28
14-Feb-2020 10:21:29 Test ANVL-BGP4-25.1 executing
14-Feb-2020 10:21:29 Test Summary
14-Feb-2020 10:21:29 1. A route Rte1, referencing only the intermediate network
14-Feb-2020 10:21:29 address, is considered resolvable if the Routing Table contains at
14-Feb-2020 10:21:29 least one resolvable route Rte2 that matches Rte1's intermediate
14-Feb-2020 10:21:29 network address and is not recursively resolved (directly or indi-
14-Feb-2020 10:21:29 rectly) through Rte1.
14-Feb-2020 10:21:29 Mutually recursive routes (routes resolving each other or themselves),
14-Feb-2020 10:21:29 also fail the resolvability check.
14-Feb-2020 10:21:29 It is also important that implementations do not consider feasible
14-Feb-2020 10:21:29 routes that would become unresolvable if they were installed in the
14-Feb-2020 10:21:29 Routing Table even if their NEXT_HOPs are resolvable using the cur-
14-Feb-2020 10:21:29 rent contents of the Routing Table (an example of such routes would
14-Feb-2020 10:21:29 be mutually recursive routes).
14-Feb-2020 10:21:29 AND
14-Feb-2020 10:21:29 Unresolved routes SHALL be removed from the Loc-RIB and the routing table.
14-Feb-2020 10:21:29 Test Reference
14-Feb-2020 10:21:29 NEGATIVE
14-Feb-2020 10:21:29 RFC4271, Sect. 9.1.2.1, p 79,
14-Feb-2020 10:21:29 Route Resolvability Condition
14-Feb-2020 10:21:29 RFC4271, Sect. 9.1.2.1, p 79-80,
14-Feb-2020 10:21:29 Route Resolvability Condition
14-Feb-2020 10:21:29 RFC4271, Sect. 9.1.2, p 79,
14-Feb-2020 10:21:29 Phase 2: Route Selection
14-Feb-2020 10:21:29 Test Classification
14-Feb-2020 10:21:29 MUST
14-Feb-2020 10:23:21 Test ANVL-BGP4-25.1: Passed
14-Feb-2020 10:23:21
14-Feb-2020 10:23:22 Test ANVL-BGP4-26.1 executing
14-Feb-2020 10:23:22 Test Summary
14-Feb-2020 10:23:22 a) Remove from consideration all routes which are not tied for
14-Feb-2020 10:23:22 having the smallest number of AS numbers present in their AS_PATH
14-Feb-2020 10:23:22 attributes. Note, that when counting this number, an AS_SET counts
14-Feb-2020 10:23:22 as 1, no matter how many ASs are in the set.
14-Feb-2020 10:23:22 Test Reference
14-Feb-2020 10:23:22 RFC4271, Sect. 9.1.2.2, p 80,
14-Feb-2020 10:23:22 Breaking Ties (Phase 2)
14-Feb-2020 10:23:22 Test Classification
14-Feb-2020 10:23:22 MUST
14-Feb-2020 10:24:50 Test ANVL-BGP4-26.1: Passed
14-Feb-2020 10:24:50
14-Feb-2020 10:24:52 Test ANVL-BGP4-26.2 executing
14-Feb-2020 10:24:52 Test Summary
14-Feb-2020 10:24:52 b) Remove from consideration all routes which are not tied for
14-Feb-2020 10:24:52 having the lowest Origin number in their Origin attribute.
14-Feb-2020 10:24:52 Test Reference
14-Feb-2020 10:24:52 RFC4271, Sect. 9.1.2.2, p 80,
14-Feb-2020 10:24:52 Breaking Ties (Phase 2)
14-Feb-2020 10:24:52 Test Classification
14-Feb-2020 10:24:52 MUST
14-Feb-2020 10:29:10 Test ANVL-BGP4-26.2: Passed
14-Feb-2020 10:29:10
14-Feb-2020 10:29:12 Test ANVL-BGP4-26.3 executing
14-Feb-2020 10:29:12 Test Summary
14-Feb-2020 10:29:12 Remove from consideration routes with less-preferred MULTI_EXIT_DISC
14-Feb-2020 10:29:12 attributes.
14-Feb-2020 10:29:12 Test Reference
14-Feb-2020 10:29:12 RFC4271, Sect. 9.1.2.2, p 81,
14-Feb-2020 10:29:12 Breaking Ties (Phase 2)
14-Feb-2020 10:29:12 Test Classification
14-Feb-2020 10:29:12 MUST
14-Feb-2020 10:30:27 Test ANVL-BGP4-26.3: Passed
14-Feb-2020 10:30:27
14-Feb-2020 10:30:29 Test ANVL-BGP4-26.5 executing
14-Feb-2020 10:30:29 Test Summary
14-Feb-2020 10:30:29 MULTI_EXIT_DISC is only comparable between routes learned from
14-Feb-2020 10:30:29 the same neighboring AS.
14-Feb-2020 10:30:29 (This test checks the case when two routes are received from
14-Feb-2020 10:30:29 same AS, having different MULTI_EXIT_DISC values)
14-Feb-2020 10:30:29 Test Reference
14-Feb-2020 10:30:29 RFC4271, Sect. 9.1.2.2, p 80
14-Feb-2020 10:30:29 Breaking Ties (Phase 2)
14-Feb-2020 10:30:29 Test Classification
14-Feb-2020 10:30:29 MUST
14-Feb-2020 10:31:37 Test ANVL-BGP4-26.5: Passed
14-Feb-2020 10:31:37
14-Feb-2020 10:31:39 Test ANVL-BGP4-26.6 executing
14-Feb-2020 10:31:39 Test Summary
14-Feb-2020 10:31:39 Routes which do not have the MULTI_EXIT_DISC attribute are considered
14-Feb-2020 10:31:39 to have the lowest possible MULTI_EXIT_DISC value.
14-Feb-2020 10:31:39 Test Reference
14-Feb-2020 10:31:39 RFC4271, Sect. 9.1.2.2, p 80,
14-Feb-2020 10:31:39 Breaking Ties (Phase 2)
14-Feb-2020 10:31:39 Test Classification
14-Feb-2020 10:31:39 MUST
14-Feb-2020 10:32:55 Test ANVL-BGP4-26.6: Passed
14-Feb-2020 10:32:55
14-Feb-2020 10:32:56 Test ANVL-BGP4-26.7 executing
14-Feb-2020 10:32:56 Test Summary
14-Feb-2020 10:32:56 d) If at least one of the candidate routes was received via EBGP,
14-Feb-2020 10:32:56 remove from consideration all routes which were received via IBGP.
14-Feb-2020 10:32:56 Test Reference
14-Feb-2020 10:32:56 RFC4271, Sect. 9.1.2.2, p 82,
14-Feb-2020 10:32:56 Breaking Ties (Phase 2)
14-Feb-2020 10:32:56 Test Classification
14-Feb-2020 10:32:56 MUST
14-Feb-2020 10:34:14 Test ANVL-BGP4-26.7: Passed
14-Feb-2020 10:34:14
14-Feb-2020 10:34:16 Test ANVL-BGP4-26.8 executing
14-Feb-2020 10:34:16 Test Summary
14-Feb-2020 10:34:16 e) Remove from consideration any routes with less-preferred inte-
14-Feb-2020 10:34:16 rior cost.  The interior cost of a route is determined by calcu-
14-Feb-2020 10:34:16 lating the metric to the NEXT_HOP for the route using the Routing
14-Feb-2020 10:34:16 Table.
14-Feb-2020 10:34:16 Test Reference
14-Feb-2020 10:34:16 RFC4271, Sect. 9.1.2.2, p 82,
14-Feb-2020 10:34:16 Breaking Ties (Phase 2)
14-Feb-2020 10:34:16 Test Classification
14-Feb-2020 10:34:16 MUST
14-Feb-2020 10:36:00 Test ANVL-BGP4-26.8: Passed
14-Feb-2020 10:36:00
14-Feb-2020 10:36:02 Test ANVL-BGP4-26.9 executing
14-Feb-2020 10:36:02 Test Summary
14-Feb-2020 10:36:02 f) Remove from consideration all routes other than the route that
14-Feb-2020 10:36:02 was advertised by the BGP speaker whose BGP Identifier has the
14-Feb-2020 10:36:02 lowest value.
14-Feb-2020 10:36:02 Test Reference
14-Feb-2020 10:36:02 RFC4271, Sect. 9.1.2.2, p 82,
14-Feb-2020 10:36:02 Breaking Ties (Phase 2)
14-Feb-2020 10:36:02 Test Classification
14-Feb-2020 10:36:02 MUST
14-Feb-2020 10:37:17 Test ANVL-BGP4-26.9: Passed
14-Feb-2020 10:37:17
14-Feb-2020 10:37:19 Test ANVL-BGP4-27.1 executing
14-Feb-2020 10:37:19 Test Summary
14-Feb-2020 10:37:19 If a more specific route is later withdrawn, the set of destinations
14-Feb-2020 10:37:19 described by the overlap will still be reachable using the less
14-Feb-2020 10:37:19 specific route.
14-Feb-2020 10:37:19 Test Reference
14-Feb-2020 10:37:19 RFC4271, Sect. 9.1.4, p 83,
14-Feb-2020 10:37:19 Overlapping Routes
14-Feb-2020 10:37:19 Test Classification
14-Feb-2020 10:37:19 SHOULD
14-Feb-2020 10:38:49 Test ANVL-BGP4-27.1: Passed
14-Feb-2020 10:38:49
14-Feb-2020 10:38:50 Test ANVL-BGP4-27.2 executing
14-Feb-2020 10:38:50 Test Summary
14-Feb-2020 10:38:50 If both a less and a more specific route are accepted, then the
14-Feb-2020 10:38:50 Decision Process MUST install, in Loc-RIB, either both the less and
14-Feb-2020 10:38:50 the more specific routes or aggregate the two routes and install, in
14-Feb-2020 10:38:50 Loc-RIB, the aggregated route, provided that both routes have the
14-Feb-2020 10:38:50 same value of the NEXT_HOP attribute.
14-Feb-2020 10:38:50 Test Reference
14-Feb-2020 10:38:50 RFC4271, Sect. 9.1.4, p 83-84,
14-Feb-2020 10:38:50 Overlapping Routes
14-Feb-2020 10:38:50 Test Classification
14-Feb-2020 10:38:50 MUST
14-Feb-2020 10:39:25 Test ANVL-BGP4-27.2: Passed
14-Feb-2020 10:39:25
14-Feb-2020 10:39:27 Test ANVL-BGP4-28.1 executing
14-Feb-2020 10:39:27 Test Summary
14-Feb-2020 10:39:27 When a BGP speaker receives an UPDATE message from an internal peer,
14-Feb-2020 10:39:27 the receiving BGP speaker SHALL NOT re-distribute the routing
14-Feb-2020 10:39:27 information contained in that UPDATE message to other internal peers
14-Feb-2020 10:39:27 Test Reference
14-Feb-2020 10:39:27 RFC4271, Sect. 9.2, p 84,
14-Feb-2020 10:39:27 Update-Send Process
14-Feb-2020 10:39:27 Test Classification
14-Feb-2020 10:39:27 MUST
14-Feb-2020 10:41:05 Test ANVL-BGP4-28.1: Passed
14-Feb-2020 10:41:05
14-Feb-2020 10:41:06 Test ANVL-BGP4-29.1 executing
14-Feb-2020 10:41:06 Test Summary
14-Feb-2020 10:41:06 If new routes are selected multiple times while awaiting the
14-Feb-2020 10:41:06 expiration of MinRouteAdvertisementInterval, the last route selected
14-Feb-2020 10:41:06 SHALL be advertised at the end of MinRouteAdvertisementIntervalTimer.
14-Feb-2020 10:41:06 Test Reference
14-Feb-2020 10:41:06 RFC4271, Sect. 9.2.1.1, p 85,
14-Feb-2020 10:41:06 Frequency of Route Advertisement,
14-Feb-2020 10:41:06 Test Classification
14-Feb-2020 10:41:06 MUST
14-Feb-2020 10:42:11 Test ANVL-BGP4-29.1: Passed
14-Feb-2020 10:42:11
14-Feb-2020 10:42:12 Test ANVL-BGP4-31.3 executing
14-Feb-2020 10:42:12 Test Summary
14-Feb-2020 10:42:12 Path attributes that have different type codes can not be
14-Feb-2020 10:42:12 aggregated together.
14-Feb-2020 10:42:12 (Here we test that the DUT has aggregated two routes having
14-Feb-2020 10:42:12 the same type code and all the mandatory attributes are present)
14-Feb-2020 10:42:12 Test Reference
14-Feb-2020 10:42:12 RFC4271, Sect.9.2.2.2, p 87
14-Feb-2020 10:42:12 Aggregating Routing Information
14-Feb-2020 10:42:12 Test Classification
14-Feb-2020 10:42:12 MAY
14-Feb-2020 10:42:49 Test ANVL-BGP4-31.3: Passed
14-Feb-2020 10:42:49
14-Feb-2020 10:42:51 Test ANVL-BGP4-31.4 executing
14-Feb-2020 10:42:51 Test Summary
14-Feb-2020 10:42:51 When aggregating routes that have different NEXT_HOP attribute,
14-Feb-2020 10:42:51 the NEXT_HOP attribute of the aggregated route SHALL identify
14-Feb-2020 10:42:51 an interface on the BGP speaker that performs the aggregation.
14-Feb-2020 10:42:51 Test Reference
14-Feb-2020 10:42:51 RFC4271, 9.2.2.2, p 87,
14-Feb-2020 10:42:51 Aggregating Routing Information
14-Feb-2020 10:42:51 Test Classification
14-Feb-2020 10:42:51 MUST
14-Feb-2020 10:43:41 Test ANVL-BGP4-31.4: Passed
14-Feb-2020 10:43:41
14-Feb-2020 10:43:42 Test ANVL-BGP4-31.11 executing
14-Feb-2020 10:43:42 Test Summary
14-Feb-2020 10:43:42 - No tuple of type AS_SET with the same value SHALL appear
14-Feb-2020 10:43:42 more than once in the aggregated AS_PATH.
14-Feb-2020 10:43:42 An implementation may choose any algorithm which conforms to
14-Feb-2020 10:43:42 these rules. At a minimum a conformant implementation SHALL be
14-Feb-2020 10:43:42 able to perform the following algorithm that meets all of the
14-Feb-2020 10:43:42 above conditions:
14-Feb-2020 10:43:42 Test Reference
14-Feb-2020 10:43:42 NEGATIVE
14-Feb-2020 10:43:42 RFC4271, Sect. 9.2.2.2, p 88,
14-Feb-2020 10:43:42 Aggregating Routing Information
14-Feb-2020 10:43:42 Test Classification
14-Feb-2020 10:43:42 MUST
14-Feb-2020 10:44:19 Test ANVL-BGP4-31.11: Passed
14-Feb-2020 10:44:19
14-Feb-2020 10:44:21 Test ANVL-BGP4-31.12 executing
14-Feb-2020 10:44:21 Test Summary
14-Feb-2020 10:44:21 If at least one of the routes to be aggregated has ATOMIC_AGGREGATE
14-Feb-2020 10:44:21 path attribute, then the aggregated route shall have this attribute as
14-Feb-2020 10:44:21 well.
14-Feb-2020 10:44:21 Test Reference
14-Feb-2020 10:44:21 RFC4271, Sect. 9.2.2.2, p 89,
14-Feb-2020 10:44:21 Aggregating Routing Information,
14-Feb-2020 10:44:21 Test Classification
14-Feb-2020 10:44:21 SHOULD
14-Feb-2020 10:44:58 Test ANVL-BGP4-31.12: Passed
14-Feb-2020 10:44:58
14-Feb-2020 10:45:00 Test ANVL-BGP4-31.13 executing
14-Feb-2020 10:45:00 Test Summary
14-Feb-2020 10:45:00 Any AGGREGATOR attributes from the routes to be aggregated MUST
14-Feb-2020 10:45:00 NOT be included in the aggregated route. The BGP speaker per-
14-Feb-2020 10:45:00 forming the route aggregation MAY attach a new AGGREGATOR
14-Feb-2020 10:45:00 attribute (see Section 5.1.7).
14-Feb-2020 10:45:00 Test Reference
14-Feb-2020 10:45:00 RFC4271, Sect. 9.2.2.2, p 89,
14-Feb-2020 10:45:00 Aggregating Routing Information
14-Feb-2020 10:45:00 Test Classification
14-Feb-2020 10:45:00 MUST
14-Feb-2020 10:45:37 Test ANVL-BGP4-31.13: Passed
14-Feb-2020 10:45:37
14-Feb-2020 10:45:38 Test ANVL-BGP4-32.1 executing
14-Feb-2020 10:45:38 Test Summary
14-Feb-2020 10:45:38 - If the local AS appears in the AS path of the new route being
14-Feb-2020 10:45:38 considered, then that new route can not be viewed as better than
14-Feb-2020 10:45:38 any other route (provided that the speaker is configured to accept
14-Feb-2020 10:45:38 such routes). If such a route were ever used, a routing loop could
14-Feb-2020 10:45:38 result.
14-Feb-2020 10:45:38 Test Reference
14-Feb-2020 10:45:38 RFC4271, 9.3, p 89,
14-Feb-2020 10:45:38 Route Selection Criteria
14-Feb-2020 10:45:38 Test Classification
14-Feb-2020 10:45:38 MUST
14-Feb-2020 10:47:06 Test ANVL-BGP4-32.1: Passed
14-Feb-2020 10:47:06
14-Feb-2020 10:47:08 Test ANVL-BGP4-33.1 executing
14-Feb-2020 10:47:08 Test Summary
14-Feb-2020 10:47:08 The BGP protocol allows multiple address prefixes with the same
14-Feb-2020 10:47:08 Path attributes to be specified in one message
14-Feb-2020 10:47:08 Test Reference
14-Feb-2020 10:47:08 RFC4271, Sect. Appendix - F.1, p 95,
14-Feb-2020 10:47:08 Multiple Networks Per Message,
14-Feb-2020 10:47:08 Test Classification
14-Feb-2020 10:47:08 SHOULD
14-Feb-2020 10:48:10 Test ANVL-BGP4-33.1: Passed
14-Feb-2020 10:48:10
14-Feb-2020 10:48:11 Writing DejaGNU Result file to ./bgp4-result.xml
14-Feb-2020 10:48:11 Finished task 'Add Basic BGP4 IPv4 Tests' with result: Success
14-Feb-2020 10:48:11 Starting task 'Collect ANVL Results' of type 'com.atlassian.bamboo.plugins.testresultparser:task.testresultparser.junit'
14-Feb-2020 10:48:11 Parsing test results under /root/bamboo-agent-home/xml-data/build-dir/FRR-FRR73SNAP-IPV4BGP4...
14-Feb-2020 10:48:11 Finished task 'Collect ANVL Results' with result: Success
14-Feb-2020 10:48:11 Running post build plugin 'Docker Container Cleanup'
14-Feb-2020 10:48:11 Running post build plugin 'NCover Results Collector'
14-Feb-2020 10:48:11 Running post build plugin 'Clover Results Collector'
14-Feb-2020 10:48:11 Running post build plugin 'npm Cache Cleanup'
14-Feb-2020 10:48:11 Running post build plugin 'Artifact Copier'
14-Feb-2020 10:48:11 Successfully removed working directory at '/root/bamboo-agent-home/xml-data/build-dir/FRR-FRR73SNAP-IPV4BGP4'
14-Feb-2020 10:48:11 Finalising the build...
14-Feb-2020 10:48:11 Stopping timer.
14-Feb-2020 10:48:11 Build FRR-FRR73SNAP-IPV4BGP4-2 completed.
14-Feb-2020 10:48:11 Running on server: post build plugin 'NCover Results Collector'
14-Feb-2020 10:48:11 Running on server: post build plugin 'Build Hanging Detection Configuration'
14-Feb-2020 10:48:11 Running on server: post build plugin 'Clover Delta Calculator'
14-Feb-2020 10:48:11 Running on server: post build plugin 'Maven Dependencies Postprocessor'
14-Feb-2020 10:48:11 All post build plugins have finished
14-Feb-2020 10:48:11 Generating build results summary...
14-Feb-2020 10:48:11 Saving build results to disk...
14-Feb-2020 10:48:11 Logging substituted variables...
14-Feb-2020 10:48:11 Indexing build results...
14-Feb-2020 10:48:11 Finished building FRR-FRR73SNAP-IPV4BGP4-2.