FRR-7.3-Snapcraft

Build: #2 failed

Job: BGP4 IPv6 Tests was successful

Build log

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

16-Feb-2020 10:50:19 Test Reference
16-Feb-2020 10:50:19 NEGATIVE
16-Feb-2020 10:50:19 RFC 4271, Sect. 6.1, p 30,
16-Feb-2020 10:50:19 Message Header error handling
16-Feb-2020 10:50:19 Test Classification
16-Feb-2020 10:50:19 MUST
16-Feb-2020 10:50:40 Test ANVL-BGPPLUS-22.1: Passed
16-Feb-2020 10:50:40
16-Feb-2020 10:50:42 Test ANVL-BGPPLUS-22.2 executing
16-Feb-2020 10:50:42 Test Summary
16-Feb-2020 10:50:42 If the Length field of an OPEN message is less than the minimum
16-Feb-2020 10:50:42 length of the OPEN message, then the Error Subcode is set to Bad
16-Feb-2020 10:50:42 Message Length. The Data field contains the erroneous Length field.
16-Feb-2020 10:50:42 Test Reference
16-Feb-2020 10:50:42 NEGATIVE
16-Feb-2020 10:50:42 RFC 4271, Sect. 6.1, p 30,
16-Feb-2020 10:50:42 Message Header error handling
16-Feb-2020 10:50:42 Test Classification
16-Feb-2020 10:50:42 MUST
16-Feb-2020 10:51:03 Test ANVL-BGPPLUS-22.2: Passed
16-Feb-2020 10:51:03
16-Feb-2020 10:51:04 Test ANVL-BGPPLUS-22.3 executing
16-Feb-2020 10:51:04 Test Summary
16-Feb-2020 10:51:04 If the Length field of an UPDATE message is less than the minimum
16-Feb-2020 10:51:04 length of the UPDATE message, then the Error Subcode is set to Bad
16-Feb-2020 10:51:04 Message Length. The Data field contains the erroneous Length field.
16-Feb-2020 10:51:04 Test Reference
16-Feb-2020 10:51:04 NEGATIVE
16-Feb-2020 10:51:04 RFC 4271, Sect. 6.1, p 30,
16-Feb-2020 10:51:04 Message Header error handling
16-Feb-2020 10:51:04 Test Classification
16-Feb-2020 10:51:04 MUST
16-Feb-2020 10:51:25 Test ANVL-BGPPLUS-22.3: Passed
16-Feb-2020 10:51:25
16-Feb-2020 10:51:27 Test ANVL-BGPPLUS-22.4 executing
16-Feb-2020 10:51:27 Test Summary
16-Feb-2020 10:51:27 If the Length field of a KEEPALIVE message is not equal to 19 then
16-Feb-2020 10:51:27 the Error Subcode is set to Bad Message Length. The Data field
16-Feb-2020 10:51:27 contains the erroneous Length field.
16-Feb-2020 10:51:27 Test Reference
16-Feb-2020 10:51:27 NEGATIVE
16-Feb-2020 10:51:27 RFC 4271, Sect. 6.1, p 30,
16-Feb-2020 10:51:27 Message Header error handling
16-Feb-2020 10:51:27 Test Classification
16-Feb-2020 10:51:27 MUST
16-Feb-2020 10:52:06 Test ANVL-BGPPLUS-22.4: Passed
16-Feb-2020 10:52:06
16-Feb-2020 10:52:08 Test ANVL-BGPPLUS-22.5 executing
16-Feb-2020 10:52:08 Test Summary
16-Feb-2020 10:52:08 If the Type field of the message header is not recognized, then the
16-Feb-2020 10:52:08 Error Subcode is set to Bad Message Type. The Data field contains
16-Feb-2020 10:52:08 the erroneous Type field.
16-Feb-2020 10:52:08 Test Reference
16-Feb-2020 10:52:08 NEGATIVE
16-Feb-2020 10:52:08 RFC 4271, Sect. 6.1, p 30,
16-Feb-2020 10:52:08 Message Header error handling
16-Feb-2020 10:52:08 Test Classification
16-Feb-2020 10:52:08 MUST
16-Feb-2020 10:52:29 Test ANVL-BGPPLUS-22.5: Passed
16-Feb-2020 10:52:29
16-Feb-2020 10:52:31 Test ANVL-BGPPLUS-23.1 executing
16-Feb-2020 10:52:31 Test Summary
16-Feb-2020 10:52:31 If the Autonomous System field of the OPEN message is unacceptable,
16-Feb-2020 10:52:31 then the Error Subcode is set to Bad Peer AS.
16-Feb-2020 10:52:31 Test Reference
16-Feb-2020 10:52:31 NEGATIVE
16-Feb-2020 10:52:31 RFC 4271, Sect. 6.2, p 31,
16-Feb-2020 10:52:31 OPEN message error handling
16-Feb-2020 10:52:31 Test Classification
16-Feb-2020 10:52:31 MUST
16-Feb-2020 10:52:52 Test ANVL-BGPPLUS-23.1: Passed
16-Feb-2020 10:52:52
16-Feb-2020 10:52:54 Test ANVL-BGPPLUS-23.3 executing
16-Feb-2020 10:52:54 Test Summary
16-Feb-2020 10:52:54 If the BGP Identifier field of the OPEN message is syntactically
16-Feb-2020 10:52:54 incorrect, then the Error Subcode is set to Bad BGP Identifier.
16-Feb-2020 10:52:54 Syntactic correctness means that the BGP Identifier field represents
16-Feb-2020 10:52:54 a valid IP host address.
16-Feb-2020 10:52:54 Test Reference
16-Feb-2020 10:52:54 NEGATIVE
16-Feb-2020 10:52:54 RFC 4271, Sect. 6.2, p 32,
16-Feb-2020 10:52:54 OPEN message error handling
16-Feb-2020 10:52:54 Test Classification
16-Feb-2020 10:52:54 MUST
16-Feb-2020 10:53:15 Test ANVL-BGPPLUS-23.3: Passed
16-Feb-2020 10:53:15
16-Feb-2020 10:53:16 Test ANVL-BGPPLUS-23.4 executing
16-Feb-2020 10:53:16 Test Summary
16-Feb-2020 10:53:16 If one of the Optional Parameters in the OPEN message is not
16-Feb-2020 10:53:16 recognized, then the Error Subcode MUST be set to Unsupported
16-Feb-2020 10:53:16 Optional Parameters.
16-Feb-2020 10:53:16 Test Reference
16-Feb-2020 10:53:16 NEGATIVE
16-Feb-2020 10:53:16 RFC 4271, Sect. 6.2, p 32,
16-Feb-2020 10:53:16 OPEN message error handling
16-Feb-2020 10:53:16 Test Classification
16-Feb-2020 10:53:16 MUST
16-Feb-2020 10:53:38 Test ANVL-BGPPLUS-23.4: Passed
16-Feb-2020 10:53:38
16-Feb-2020 10:53:39 Test ANVL-BGPPLUS-26.1 executing
16-Feb-2020 10:53:39 Test Summary
16-Feb-2020 10:53:39 In absence of any fatal errors (that are indicated in this section),
16-Feb-2020 10:53:39 a BGP peer may choose at any given time to close its BGP4 Connection
16-Feb-2020 10:53:39 by sending the NOTIFICATION message with Error Code Cease.
16-Feb-2020 10:53:39 Test Reference
16-Feb-2020 10:53:39 RFC 4271, Sect. 6.7, p 34,
16-Feb-2020 10:53:39 Cease
16-Feb-2020 10:53:39 Test Classification
16-Feb-2020 10:53:39 MAY
16-Feb-2020 10:54:02 Test ANVL-BGPPLUS-26.1: Passed
16-Feb-2020 10:54:02
16-Feb-2020 10:54:04 Test ANVL-BGPPLUS-26.2 executing
16-Feb-2020 10:54:04 Test Summary
16-Feb-2020 10:54:04 The Cease NOTIFICATION message must not be used when a fatal error
16-Feb-2020 10:54:04 indicated by this section does exist.
16-Feb-2020 10:54:04 (Note : This test checks the case when the error is in message Header)
16-Feb-2020 10:54:04 Test Reference
16-Feb-2020 10:54:04 NEGATIVE
16-Feb-2020 10:54:04 RFC 4271, Sect. 6.7, p 34,
16-Feb-2020 10:54:04 Cease
16-Feb-2020 10:54:04 Test Classification
16-Feb-2020 10:54:04 MUST
16-Feb-2020 10:55:02 Test ANVL-BGPPLUS-26.2: Passed
16-Feb-2020 10:55:02
16-Feb-2020 10:55:03 Test ANVL-BGPPLUS-26.3 executing
16-Feb-2020 10:55:03 Test Summary
16-Feb-2020 10:55:03 The Cease NOTIFICATION message must not be used when a fatal error
16-Feb-2020 10:55:03 indicated by this section does exist.
16-Feb-2020 10:55:03 (Note : This test checks the case when the error is in OPEN message)
16-Feb-2020 10:55:03 Test Reference
16-Feb-2020 10:55:03 NEGATIVE
16-Feb-2020 10:55:03 RFC 4271, Sect. 6.7, p 34, Cease
16-Feb-2020 10:55:03 Test Classification
16-Feb-2020 10:55:03 MUST
16-Feb-2020 10:56:56 Test ANVL-BGPPLUS-26.3: Passed
16-Feb-2020 10:56:56
16-Feb-2020 10:56:58 Test ANVL-BGPPLUS-27.1 executing
16-Feb-2020 10:56:58 Test Summary
16-Feb-2020 10:56:58 In case when a connection collision is detected, if the value of the
16-Feb-2020 10:56:58 local BGP Identifier is less than the remote one, the local system
16-Feb-2020 10:56:58 closes BGP4 Connection that already exists (the one that is already in
16-Feb-2020 10:56:58 the OpenConfirm state), and accepts BGP4 Connection initiated by the
16-Feb-2020 10:56:58 remote system.
16-Feb-2020 10:56:58 Test Reference
16-Feb-2020 10:56:58 RFC 4271, Sect. 6.8, p 35,
16-Feb-2020 10:56:58 Connection collision detection
16-Feb-2020 10:56:58 Test Classification
16-Feb-2020 10:56:58 MUST
16-Feb-2020 10:58:39 Test ANVL-BGPPLUS-27.1: Passed
16-Feb-2020 10:58:39
16-Feb-2020 10:58:40 Test ANVL-BGPPLUS-27.2 executing
16-Feb-2020 10:58:40 Test Summary
16-Feb-2020 10:58:40 In case when a connection collision is detected, if the value of the
16-Feb-2020 10:58:40 local BGP Identifier is greater than the remote one, the local system
16-Feb-2020 10:58:40 closes newly created BGP4 Connection, and continues to use the existing
16-Feb-2020 10:58:40 one (the one that is already in the OpenConfirm state).
16-Feb-2020 10:58:40 Test Reference
16-Feb-2020 10:58:40 RFC 4271, Sect. 6.8, p 35,
16-Feb-2020 10:58:40 Connection collision detection
16-Feb-2020 10:58:40 Test Classification
16-Feb-2020 10:58:40 MUST
16-Feb-2020 11:00:19 Test ANVL-BGPPLUS-27.2: Passed
16-Feb-2020 11:00:19
16-Feb-2020 11:00:21 Test ANVL-BGPPLUS-27.3 executing
16-Feb-2020 11:00:21 Test Summary
16-Feb-2020 11:00:21 Unless allowed via configuration, a connection collision with an
16-Feb-2020 11:00:21 existing BGP4 Connection that is in Established state causes closing
16-Feb-2020 11:00:21 of the newly created connection.
16-Feb-2020 11:00:21 Test Reference
16-Feb-2020 11:00:21 RFC 4271, Sect. 6.8, p 35,
16-Feb-2020 11:00:21 Connection collision detection
16-Feb-2020 11:00:21 Test Classification
16-Feb-2020 11:00:21 MUST
16-Feb-2020 11:02:00 Test ANVL-BGPPLUS-27.3: Passed
16-Feb-2020 11:02:00
16-Feb-2020 11:02:01 Test ANVL-BGPPLUS-27.4 executing
16-Feb-2020 11:02:01 Test Summary
16-Feb-2020 11:02:01 Note that a connection collision cannot be detected with connections
16-Feb-2020 11:02:01 that are in Idle, or Connect, or Active states.
16-Feb-2020 11:02:01 (Note: This test is for Connect state)
16-Feb-2020 11:02:01 Test Reference
16-Feb-2020 11:02:01 RFC 4271, Sect. 6.8, p 35,
16-Feb-2020 11:02:01 Connection collision detection
16-Feb-2020 11:02:01 Test Classification
16-Feb-2020 11:02:01 MUST
16-Feb-2020 11:03:38 Test ANVL-BGPPLUS-27.4: Passed
16-Feb-2020 11:03:38
16-Feb-2020 11:03:40 Test ANVL-BGPPLUS-27.5 executing
16-Feb-2020 11:03:40 Test Summary
16-Feb-2020 11:03:40 Note that a connection collision cannot be detected with connections
16-Feb-2020 11:03:40 that are in Idle, or Connect, or Active states.
16-Feb-2020 11:03:40 (This test is for Active State)
16-Feb-2020 11:03:40 Test Reference
16-Feb-2020 11:03:40 RFC 4271, Sect. 6.8, p 35,
16-Feb-2020 11:03:40 Connection collision detection
16-Feb-2020 11:03:40 Test Classification
16-Feb-2020 11:03:40 MUST
16-Feb-2020 11:05:39 Test ANVL-BGPPLUS-27.5: Passed
16-Feb-2020 11:05:39
16-Feb-2020 11:05:41 Test ANVL-BGPPLUS-28.1 executing
16-Feb-2020 11:05:41 Test Summary
16-Feb-2020 11:05:41 If the version number contained in the Version field of the received
16-Feb-2020 11:05:41 OPEN message is not supported then Data field contains a 2-octet
16-Feb-2020 11:05:41 unsigned integer, which indicates the largest locally supported
16-Feb-2020 11:05:41 version number less than the version the remote BGP peer bid.
16-Feb-2020 11:05:41 Test Reference
16-Feb-2020 11:05:41 If an open attempt fails with an Error Code OPEN Message Error, and
16-Feb-2020 11:05:41 an Error Subcode Unsupported Version Number, then if the two peers
16-Feb-2020 11:05:41 do support one or more common versions, then they will rapidly
16-Feb-2020 11:05:41 determine the highest common version.
16-Feb-2020 11:05:41 NEGATIVE
16-Feb-2020 11:05:41 RFC 4271, Sect. 6.2, p 30,
16-Feb-2020 11:05:41 OPEN message error handling
16-Feb-2020 11:05:41 RFC 4271, Sect. 7, p 35,
16-Feb-2020 11:05:41 BGP Version Negotiation
16-Feb-2020 11:05:41 Test Classification
16-Feb-2020 11:05:41 MUST
16-Feb-2020 11:06:04 Test ANVL-BGPPLUS-28.1: Passed
16-Feb-2020 11:06:04
16-Feb-2020 11:06:05 Test ANVL-BGPPLUS-29.1 executing
16-Feb-2020 11:06:05 Test Summary
16-Feb-2020 11:06:05 At Idle state in response to the Manual Start event the local system
16-Feb-2020 11:06:05 initiates a TCP connection to other BGP peer.
16-Feb-2020 11:06:05 Test Reference
16-Feb-2020 11:06:05 RFC 4271, Sect. 8.2.2, p 52,
16-Feb-2020 11:06:05 BGP Finite State machine
16-Feb-2020 11:06:05 Test Classification
16-Feb-2020 11:06:05 MUST
16-Feb-2020 11:06:28 Test ANVL-BGPPLUS-29.1: Passed
16-Feb-2020 11:06:28
16-Feb-2020 11:06:30 Test ANVL-BGPPLUS-29.2 executing
16-Feb-2020 11:06:30 Test Summary
16-Feb-2020 11:06:30 At idle state in response to the Manual Start event the local system
16-Feb-2020 11:06:30 starts the ConnectRetry timer with initial value.
16-Feb-2020 11:06:30 Test Reference
16-Feb-2020 11:06:30 RFC 4271, Sect. 8.2.2, p 52,
16-Feb-2020 11:06:30 BGP Finite State machine
16-Feb-2020 11:06:30 Test Classification
16-Feb-2020 11:06:30 MUST
16-Feb-2020 11:06:54 Test ANVL-BGPPLUS-29.2: Passed
16-Feb-2020 11:06:54
16-Feb-2020 11:06:55 Test ANVL-BGPPLUS-29.3 executing
16-Feb-2020 11:06:55 Test Summary
16-Feb-2020 11:06:55 At idle state in response to the Manual Start event the local system
16-Feb-2020 11:06:55 listens for a connection that may be initiated by the remote BGP peer
16-Feb-2020 11:06:55 Test Reference
16-Feb-2020 11:06:55 RFC 4271, Sect. 8.2.2, p 52,
16-Feb-2020 11:06:55 BGP Finite State machine
16-Feb-2020 11:06:55 Test Classification
16-Feb-2020 11:06:55 MUST
16-Feb-2020 11:07:17 Test ANVL-BGPPLUS-29.3: Passed
16-Feb-2020 11:07:17
16-Feb-2020 11:07:19 Test ANVL-BGPPLUS-29.4 executing
16-Feb-2020 11:07:19 Test Summary
16-Feb-2020 11:07:19 In response to the ConnectRetryTimer_Expires event, the local system:
16-Feb-2020 11:07:19 - restarts the ConnectRetryTimer
16-Feb-2020 11:07:19 Test Reference
16-Feb-2020 11:07:19 RFC 4271, Sect. 8.2.2, p 54,
16-Feb-2020 11:07:19 BGP Finite State machine
16-Feb-2020 11:07:19 Test Classification
16-Feb-2020 11:07:19 MUST
16-Feb-2020 11:07:44 Test ANVL-BGPPLUS-29.4: Passed
16-Feb-2020 11:07:44
16-Feb-2020 11:07:46 Test ANVL-BGPPLUS-29.5 executing
16-Feb-2020 11:07:46 Test Summary
16-Feb-2020 11:07:46 While in Active state in response to the ConnectRetry timer expired
16-Feb-2020 11:07:46 event :
16-Feb-2020 11:07:46 - continues to listen for TCP connection that may be initiated by
16-Feb-2020 11:07:46 remote BGP peer
16-Feb-2020 11:07:46 Test Reference
16-Feb-2020 11:07:46 RFC 4271, Sect. 8.2.2, p 58,
16-Feb-2020 11:07:46 BGP Finite State machine
16-Feb-2020 11:07:46 Test Classification
16-Feb-2020 11:07:46 MAY
16-Feb-2020 11:08:27 Test ANVL-BGPPLUS-29.5: Passed
16-Feb-2020 11:08:27
16-Feb-2020 11:08:29 Test ANVL-BGPPLUS-29.6 executing
16-Feb-2020 11:08:29 Test Summary
16-Feb-2020 11:08:29 Start event is ignored in the OpenSent state.
16-Feb-2020 11:08:29 Test Reference
16-Feb-2020 11:08:29 RFC 4271, Sect. 8.2.2, p 62,
16-Feb-2020 11:08:29 BGP Finite State machine
16-Feb-2020 11:08:29 Test Classification
16-Feb-2020 11:08:29 MUST
16-Feb-2020 11:10:39 Test ANVL-BGPPLUS-29.6: Passed
16-Feb-2020 11:10:39
16-Feb-2020 11:10:41 Test ANVL-BGPPLUS-29.8 executing
16-Feb-2020 11:10:41 Test Summary
16-Feb-2020 11:10:41 In OpenSent state if a TcpConnectionFails event is received,
16-Feb-2020 11:10:41 the local system:
16-Feb-2020 11:10:41 - closes the BGP4 Connection
16-Feb-2020 11:10:41 Test Reference
16-Feb-2020 11:10:41 RFC 4271, Sect. 8.2.2, p 63,
16-Feb-2020 11:10:41 BGP Finite State machine
16-Feb-2020 11:10:41 Test Classification
16-Feb-2020 11:10:41 MUST
16-Feb-2020 11:11:13 Test ANVL-BGPPLUS-29.8: Passed
16-Feb-2020 11:11:13
16-Feb-2020 11:11:15 Test ANVL-BGPPLUS-29.9 executing
16-Feb-2020 11:11:15 Test Summary
16-Feb-2020 11:11:15 In OpenSent state if a TcpConnectionFails event (Event18) is received,
16-Feb-2020 11:11:15 the local system:
16-Feb-2020 11:11:15 - continues to listen for a connection that may be initiated by the
16-Feb-2020 11:11:15 remote BGP peer
16-Feb-2020 11:11:15 Test Reference
16-Feb-2020 11:11:15 RFC 4271, Sect. 8.2.2, p 63,
16-Feb-2020 11:11:15 BGP Finite State machine
16-Feb-2020 11:11:15 Test Classification
16-Feb-2020 11:11:15 MAY
16-Feb-2020 11:11:47 Test ANVL-BGPPLUS-29.9: Passed
16-Feb-2020 11:11:47
16-Feb-2020 11:11:48 Test ANVL-BGPPLUS-29.10 executing
16-Feb-2020 11:11:48 Test Summary
16-Feb-2020 11:11:48 At OpenSent state if there are no errors in the OPEN message, the
16-Feb-2020 11:11:48 local system:
16-Feb-2020 11:11:48 - sends a KEEPALIVE message, and
16-Feb-2020 11:11:48 - sets a KeepaliveTimer
16-Feb-2020 11:11:48 Test Reference
16-Feb-2020 11:11:48 RFC 4271, Sect. 8.2.2, p 64,
16-Feb-2020 11:11:48 BGP Finite State machine
16-Feb-2020 11:11:48 Test Classification
16-Feb-2020 11:11:48 MUST
16-Feb-2020 11:12:42 Test ANVL-BGPPLUS-29.10: Passed
16-Feb-2020 11:12:42
16-Feb-2020 11:12:44 Test ANVL-BGPPLUS-29.11 executing
16-Feb-2020 11:12:44 Test Summary
16-Feb-2020 11:12:44 Any start event is ignored in the OpenConfirm state.
16-Feb-2020 11:12:44 Test Reference
16-Feb-2020 11:12:44 RFC 4271, Sect. 8.2.2, p 66,
16-Feb-2020 11:12:44 BGP Finite State machine
16-Feb-2020 11:12:44 Test Classification
16-Feb-2020 11:12:44 MUST
16-Feb-2020 11:15:09 Test ANVL-BGPPLUS-29.11: Passed
16-Feb-2020 11:15:09
16-Feb-2020 11:15:11 Test ANVL-BGPPLUS-29.12 executing
16-Feb-2020 11:15:11 Test Summary
16-Feb-2020 11:15:11 In OpenConfirm state in response to a ManualStop event initiated by
16-Feb-2020 11:15:11 the operator, the local system:
16-Feb-2020 11:15:11 - sends the NOTIFICATION message with Cease
16-Feb-2020 11:15:11 Test Reference
16-Feb-2020 11:15:11 RFC 4271, Sect. 8.2.2, p 66,
16-Feb-2020 11:15:11 BGP Finite State machine
16-Feb-2020 11:15:11 Test Classification
16-Feb-2020 11:15:11 MUST
16-Feb-2020 11:15:41 Test ANVL-BGPPLUS-29.12: Passed
16-Feb-2020 11:15:41
16-Feb-2020 11:15:43 Test ANVL-BGPPLUS-29.13 executing
16-Feb-2020 11:15:43 Test Summary
16-Feb-2020 11:15:43 In OpenConfirm state in response to a ManualStop event initiated by
16-Feb-2020 11:15:43 the operator, the local system:
16-Feb-2020 11:15:43 - changes its state to Idle.
16-Feb-2020 11:15:43 Test Reference
16-Feb-2020 11:15:43 RFC 4271, Sect. 8.2.2, p 66,
16-Feb-2020 11:15:43 BGP Finite State machine
16-Feb-2020 11:15:43 Test Classification
16-Feb-2020 11:15:43 MUST
16-Feb-2020 11:18:36 Test ANVL-BGPPLUS-29.13: Passed
16-Feb-2020 11:18:36
16-Feb-2020 11:18:38 Test ANVL-BGPPLUS-29.14 executing
16-Feb-2020 11:18:38 Test Summary
16-Feb-2020 11:18:38 Any start event is ignored in the Established state.
16-Feb-2020 11:18:38 Test Reference
16-Feb-2020 11:18:38 RFC 4271, Sect. 8.2.2, p 70,
16-Feb-2020 11:18:38 BGP Finite State machine
16-Feb-2020 11:18:38 Test Classification
16-Feb-2020 11:18:38 MUST
16-Feb-2020 11:20:47 Test ANVL-BGPPLUS-29.14: Passed
16-Feb-2020 11:20:47
16-Feb-2020 11:20:49 Test ANVL-BGPPLUS-29.15 executing
16-Feb-2020 11:20:49 Test Summary
16-Feb-2020 11:20:49 In the Established state, if the KeepaliveTimer_Expires event occurs
16-Feb-2020 11:20:49 the local system:
16-Feb-2020 11:20:49 - sends a KEEPALIVE message, and
16-Feb-2020 11:20:49 - restarts its KeepaliveTimer unless the negotiated HoldTime value
16-Feb-2020 11:20:49 is zero.
16-Feb-2020 11:20:49 Test Reference
16-Feb-2020 11:20:49 RFC 4271, Sect. 8.2.2, p 71,
16-Feb-2020 11:20:49 BGP Finite State machine
16-Feb-2020 11:20:49 Test Classification
16-Feb-2020 11:20:49 MUST
16-Feb-2020 11:22:14 Test ANVL-BGPPLUS-29.15: Passed
16-Feb-2020 11:22:14
16-Feb-2020 11:22:15 Test ANVL-BGPPLUS-29.16 executing
16-Feb-2020 11:22:15 Test Summary
16-Feb-2020 11:22:15 In the Established state, if the local system receives an UPDATE or
16-Feb-2020 11:22:15 KEEPALIVE message, it restarts its Hold Timer, if the negotiated
16-Feb-2020 11:22:15 Hold Time value is non-zero.
16-Feb-2020 11:22:15 Test Reference
16-Feb-2020 11:22:15 NEGATIVE
16-Feb-2020 11:22:15 RFC 4271, Sect. 8.2.2, p 73,
16-Feb-2020 11:22:15 BGP Finite State machine
16-Feb-2020 11:22:15 Test Classification
16-Feb-2020 11:22:15 MUST
16-Feb-2020 11:24:10 Test ANVL-BGPPLUS-29.16: Passed
16-Feb-2020 11:24:10
16-Feb-2020 11:24:13 Test ANVL-BGPPLUS-30.1 executing
16-Feb-2020 11:24:13 Test Summary
16-Feb-2020 11:24:13 An UPDATE message may be received only in the Established state.
16-Feb-2020 11:24:13 (Note : This test checks by sending Update Message
16-Feb-2020 11:24:13 immediately after TCP connection is establised)
16-Feb-2020 11:24:13 Test Reference
16-Feb-2020 11:24:13 NEGATIVE
16-Feb-2020 11:24:13 RFC 4271, Sect. 9, p 74,
16-Feb-2020 11:24:13 UPDATE Message Handling
16-Feb-2020 11:24:13 Test Classification
16-Feb-2020 11:24:13 MAY
16-Feb-2020 11:24:34 Test ANVL-BGPPLUS-30.1: Passed
16-Feb-2020 11:24:34
16-Feb-2020 11:24:37 Test ANVL-BGPPLUS-30.2 executing
16-Feb-2020 11:24:37 Test Summary
16-Feb-2020 11:24:37 An UPDATE message may be received only in the Established state.
16-Feb-2020 11:24:37 (This test checks by sending Update Message in OpenConfirm state)
16-Feb-2020 11:24:37 Test Reference
16-Feb-2020 11:24:37 NEGATIVE
16-Feb-2020 11:24:37 RFC 4271, Sect. 9, p 74,
16-Feb-2020 11:24:37 UPDATE Message Handling
16-Feb-2020 11:24:37 Test Classification
16-Feb-2020 11:24:37 MAY
16-Feb-2020 11:25:00 Test ANVL-BGPPLUS-30.2: Passed
16-Feb-2020 11:25:00
16-Feb-2020 11:25:02 Test ANVL-BGPPLUS-31.1 executing
16-Feb-2020 11:25:02 Test Summary
16-Feb-2020 11:25:02 If the AS_PATH attribute of a BGP route contains an AS loop, the BGP
16-Feb-2020 11:25:02 route should be excluded from the Phase 2 decision function.
16-Feb-2020 11:25:02 Test Reference
16-Feb-2020 11:25:02 NEGATIVE
16-Feb-2020 11:25:02 RFC 4271, Sect. 9.1.2, p 77
16-Feb-2020 11:25:02 Phase 2: Route Selection
16-Feb-2020 11:25:02 Test Classification
16-Feb-2020 11:25:02 SHOULD
16-Feb-2020 11:26:59 Test ANVL-BGPPLUS-31.1: Passed
16-Feb-2020 11:26:59
16-Feb-2020 11:27:02 Test ANVL-BGPPLUS-33.1 executing
16-Feb-2020 11:27:02 Test Summary
16-Feb-2020 11:27:02 a) Remove from consideration all routes which are not tied for
16-Feb-2020 11:27:02 having the smallest number of AS numbers present in their AS_PATH
16-Feb-2020 11:27:02 attributes. Note, that when counting this number, an AS_SET counts
16-Feb-2020 11:27:02 as 1, no matter how many ASs are in the set.
16-Feb-2020 11:27:02 Test Reference
16-Feb-2020 11:27:02 RFC 4271, Sect. 9.1.2.2, p 77-78,
16-Feb-2020 11:27:02 Breaking Ties (Phase 2)
16-Feb-2020 11:27:02 Test Classification
16-Feb-2020 11:27:02 MUST
16-Feb-2020 11:30:08 Test ANVL-BGPPLUS-33.1: Passed
16-Feb-2020 11:30:08
16-Feb-2020 11:30:10 Test ANVL-BGPPLUS-33.2 executing
16-Feb-2020 11:30:10 Test Summary
16-Feb-2020 11:30:10 b) Remove from consideration all routes which are not tied for
16-Feb-2020 11:30:10 having the lowest Origin number in their Origin attribute.
16-Feb-2020 11:30:10 Test Reference
16-Feb-2020 11:30:10 RFC 4271, Sect. 9.1.2.2, p 77-78,
16-Feb-2020 11:30:10 Breaking Ties (Phase 2)
16-Feb-2020 11:30:10 Test Classification
16-Feb-2020 11:30:10 MUST
16-Feb-2020 11:39:23 Test ANVL-BGPPLUS-33.2: Passed
16-Feb-2020 11:39:23
16-Feb-2020 11:39:24 Test ANVL-BGPPLUS-33.3 executing
16-Feb-2020 11:39:24 Test Summary
16-Feb-2020 11:39:24 Routes which do not have the MULTI_EXIT_DISC attribute are considered
16-Feb-2020 11:39:24 to have the lowest possible MULTI_EXIT_DISC value.
16-Feb-2020 11:39:24 Test Reference
16-Feb-2020 11:39:24 RFC 4271, Sect. 9.1.2.2, p 78,
16-Feb-2020 11:39:24 Breaking Ties (Phase 2)
16-Feb-2020 11:39:24 Test Classification
16-Feb-2020 11:39:24 MUST
16-Feb-2020 11:42:17 Test ANVL-BGPPLUS-33.3: Passed
16-Feb-2020 11:42:17
16-Feb-2020 11:42:19 Test ANVL-BGPPLUS-33.4 executing
16-Feb-2020 11:42:19 Test Summary
16-Feb-2020 11:42:19 d) If at least one of the candidate routes was received via EBGP,
16-Feb-2020 11:42:19 remove from consideration all routes which were received via IBGP.
16-Feb-2020 11:42:19 Test Reference
16-Feb-2020 11:42:19 RFC 4271, Sect. 9.1.2.2, p 79,
16-Feb-2020 11:42:19 Breaking Ties (Phase 2)
16-Feb-2020 11:42:19 Test Classification
16-Feb-2020 11:42:19 MUST
16-Feb-2020 11:45:15 Test ANVL-BGPPLUS-33.4: Passed
16-Feb-2020 11:45:15
16-Feb-2020 11:45:16 Test ANVL-BGPPLUS-33.6 executing
16-Feb-2020 11:45:16 Test Summary
16-Feb-2020 11:45:16 f) Remove from consideration all routes other than the route that
16-Feb-2020 11:45:16 was advertised by the BGP speaker whose BGP Identifier has the
16-Feb-2020 11:45:16 lowest value.
16-Feb-2020 11:45:16 Test Reference
16-Feb-2020 11:45:16 RFC 4271, Sect. 9.1.2.2, p 79,
16-Feb-2020 11:45:16 Breaking Ties (Phase 2)
16-Feb-2020 11:45:16 Test Classification
16-Feb-2020 11:45:16 MUST
16-Feb-2020 11:48:10 Test ANVL-BGPPLUS-33.6: Passed
16-Feb-2020 11:48:10
16-Feb-2020 11:48:12 Test ANVL-BGPPLUS-34.1 executing
16-Feb-2020 11:48:12 Test Summary
16-Feb-2020 11:48:12 If a more specific route is later withdrawn, the set of destinations
16-Feb-2020 11:48:12 described by the overlap will still be reachable using the less
16-Feb-2020 11:48:12 specific route.
16-Feb-2020 11:48:12 Test Reference
16-Feb-2020 11:48:12 RFC 4271, Sect. 9.1.4, p 81,
16-Feb-2020 11:48:12 Overlapping Routes
16-Feb-2020 11:48:12 Test Classification
16-Feb-2020 11:48:12 SHOULD
16-Feb-2020 11:52:16 Test ANVL-BGPPLUS-34.1: Passed
16-Feb-2020 11:52:16
16-Feb-2020 11:52:18 Test ANVL-BGPPLUS-34.2 executing
16-Feb-2020 11:52:18 Test Summary
16-Feb-2020 11:52:18 If both a less and a more specific route are accepted, then the
16-Feb-2020 11:52:18 Decision Process MUST install both the less and the more specific
16-Feb-2020 11:52:18 routes if it does not aggregate the two routes.
16-Feb-2020 11:52:18 Test Reference
16-Feb-2020 11:52:18 RFC 4271, Sect. 9.1.4, p 81,
16-Feb-2020 11:52:18 Overlapping Routes
16-Feb-2020 11:52:18 Test Classification
16-Feb-2020 11:52:18 MUST
16-Feb-2020 11:52:52 Test ANVL-BGPPLUS-34.2: Passed
16-Feb-2020 11:52:52
16-Feb-2020 11:52:54 Test ANVL-BGPPLUS-36.1 executing
16-Feb-2020 11:52:54 Test Summary
16-Feb-2020 11:52:54 If new routes are selected multiple times while awaiting the
16-Feb-2020 11:52:54 expiration of MinRouteAdvertisementInterval, the last route selected
16-Feb-2020 11:52:54 SHALL be advertised at the end of MinRouteAdvertisementInterval.
16-Feb-2020 11:52:54 Test Reference
16-Feb-2020 11:52:54 RFC 4271, Sect. 9.2.1.1, p 83,
16-Feb-2020 11:52:54 Frequency of Route Advertisement,
16-Feb-2020 11:52:54 Test Classification
16-Feb-2020 11:52:54 MUST
16-Feb-2020 11:54:11 Test ANVL-BGPPLUS-36.1: Passed
16-Feb-2020 11:54:11
16-Feb-2020 11:54:13 Test ANVL-BGPPLUS-37.2 executing
16-Feb-2020 11:54:13 Test Summary
16-Feb-2020 11:54:13 The parameter MinASOriginationIntervalTimer determines the minimum
16-Feb-2020 11:54:13 amount of time that must elapse between successive advertisements of
16-Feb-2020 11:54:13 UPDATE messages that report changes within the advertising BGP
16-Feb-2020 11:54:13 speaker's own autonomous systems.
16-Feb-2020 11:54:13 The suggested default value for the MinASOriginationIntervalTimer-
16-Feb-2020 11:54:13 Timer on IBGP4 Connections is 5 seconds.
16-Feb-2020 11:54:13 Test Reference
16-Feb-2020 11:54:13 RFC 4271, Sect. 9.2.1.2, p 83
16-Feb-2020 11:54:13 Frequency of Route Origination
16-Feb-2020 11:54:13 RFC 4271, Sect. 10, p 88
16-Feb-2020 11:54:13 BGP Timers
16-Feb-2020 11:54:13 Test Classification
16-Feb-2020 11:54:13 MUST
16-Feb-2020 11:54:41 Test ANVL-BGPPLUS-37.2: Passed
16-Feb-2020 11:54:41
16-Feb-2020 11:54:42 Test ANVL-BGPPLUS-38.3 executing
16-Feb-2020 11:54:42 Test Summary
16-Feb-2020 11:54:42 When aggregating routes that have different NEXT_HOP attribute,
16-Feb-2020 11:54:42 the NEXT_HOP attribute of the aggregated route SHALL identify
16-Feb-2020 11:54:42 an interface on the BGP speaker that performs the aggregation.
16-Feb-2020 11:54:42 Test Reference
16-Feb-2020 11:54:42 RFC 4271, 9.2.2.2, p 84,
16-Feb-2020 11:54:42 Aggregating Routing Information
16-Feb-2020 11:54:42 Test Classification
16-Feb-2020 11:54:42 MUST
16-Feb-2020 11:55:31 Test ANVL-BGPPLUS-38.3: Passed
16-Feb-2020 11:55:31
16-Feb-2020 11:55:33 Test ANVL-BGPPLUS-38.10 executing
16-Feb-2020 11:55:33 Test Summary
16-Feb-2020 11:55:33 - No tuple of type AS_SET with the same value SHALL appear
16-Feb-2020 11:55:33 more than once in the aggregated AS_PATH.
16-Feb-2020 11:55:33 An implementation may choose any algorithm which conforms to
16-Feb-2020 11:55:33 these rules. At a minimum a conformant implementation SHALL be
16-Feb-2020 11:55:33 able to perform the following algorithm that meets all of the
16-Feb-2020 11:55:33 above conditions:
16-Feb-2020 11:55:33 Test Reference
16-Feb-2020 11:55:33 NEGATIVE
16-Feb-2020 11:55:33 RFC 4271, Sect. 9.2.2.2, p 85,
16-Feb-2020 11:55:33 Aggregating Routing Information
16-Feb-2020 11:55:33 Test Classification
16-Feb-2020 11:55:33 MUST
16-Feb-2020 11:56:09 Test ANVL-BGPPLUS-38.10: Passed
16-Feb-2020 11:56:09
16-Feb-2020 11:56:10 Test ANVL-BGPPLUS-38.11 executing
16-Feb-2020 11:56:10 Test Summary
16-Feb-2020 11:56:10 If at least one of the routes to be aggregated has ATOMIC_AGGREGATE
16-Feb-2020 11:56:10 path attribute, then the aggregated route shall have this attribute as
16-Feb-2020 11:56:10 well.
16-Feb-2020 11:56:10 Test Reference
16-Feb-2020 11:56:10 RFC 4271, Sect. 9.2.2.2, p 86,
16-Feb-2020 11:56:10 Aggregating Routing Information,
16-Feb-2020 11:56:10 Test Classification
16-Feb-2020 11:56:10 SHOULD
16-Feb-2020 11:56:47 Test ANVL-BGPPLUS-38.11: Passed
16-Feb-2020 11:56:47
16-Feb-2020 11:56:48 Test ANVL-BGPPLUS-38.12 executing
16-Feb-2020 11:56:48 Test Summary
16-Feb-2020 11:56:48 Any AGGREGATOR attributes from the routes to be aggregated MUST
16-Feb-2020 11:56:48 NOT be included in the aggregated route. The BGP speaker per-
16-Feb-2020 11:56:48 forming the route aggregation MAY attach a new AGGREGATOR
16-Feb-2020 11:56:48 attribute (see Section 5.1.7).
16-Feb-2020 11:56:48 Test Reference
16-Feb-2020 11:56:48 RFC 4271, Sect. 9.2.2.2, p 86,
16-Feb-2020 11:56:48 Aggregating Routing Information
16-Feb-2020 11:56:48 Test Classification
16-Feb-2020 11:56:48 MUST
16-Feb-2020 11:57:24 Test ANVL-BGPPLUS-38.12: Passed
16-Feb-2020 11:57:24
16-Feb-2020 11:57:26 Test ANVL-BGPPLUS-39.1 executing
16-Feb-2020 11:57:26 Test Summary
16-Feb-2020 11:57:26 - If the local AS appears in the AS path of the new route being
16-Feb-2020 11:57:26 considered, then that new route can not be viewed as better than
16-Feb-2020 11:57:26 any other route (provided that the speaker is configured to accept
16-Feb-2020 11:57:26 such routes). If such a route were ever used, a routing loop could
16-Feb-2020 11:57:26 result.
16-Feb-2020 11:57:26 Test Reference
16-Feb-2020 11:57:26 RFC 4271, 9.3, p 86,
16-Feb-2020 11:57:26 Route Selection Criteria
16-Feb-2020 11:57:26 Test Classification
16-Feb-2020 11:57:26 MUST
16-Feb-2020 12:00:45 Test ANVL-BGPPLUS-39.1: Passed
16-Feb-2020 12:00:45
16-Feb-2020 12:00:46 Test ANVL-BGPPLUS-40.1 executing
16-Feb-2020 12:00:46 Test Summary
16-Feb-2020 12:00:46 The BGP protocol allows multiple address prefixes with the same
16-Feb-2020 12:00:46 Path attributes to be specified in one message
16-Feb-2020 12:00:46 Test Reference
16-Feb-2020 12:00:46 RFC 4271, Sect. Appendix - F.1, p 91,
16-Feb-2020 12:00:46 Multiple Networks Per Message,
16-Feb-2020 12:00:46 Test Classification
16-Feb-2020 12:00:46 SHOULD
16-Feb-2020 12:02:30 Test ANVL-BGPPLUS-40.1: Passed
16-Feb-2020 12:02:30
16-Feb-2020 12:02:32 Test ANVL-BGPPLUS-41.10 executing
16-Feb-2020 12:02:32 Test Summary
16-Feb-2020 12:02:32 If any attribute has Attribute Flags that conflict with the
16-Feb-2020 12:02:32 Attribute Type Code, then the error SHOULD be logged, and the
16-Feb-2020 12:02:32 Attribute Flags MUST be reset to the correct value.  The UPDATE
16-Feb-2020 12:02:32 message MUST continue to be processed.
16-Feb-2020 12:02:32 (NOTE:This test only checks for Processing
16-Feb-2020 12:02:32 This test checks for ATOMIC AGGREGATE
16-Feb-2020 12:02:32 (well known discretionary) attribute and for Optional Bit)
16-Feb-2020 12:02:32 Test Reference
16-Feb-2020 12:02:32 draft-ietf-idr-error-handling-01.txt Section 2 Page 3 ' Revision to Base Specification'
16-Feb-2020 12:02:32 UPDATE message error handling
16-Feb-2020 12:02:32 Test Classification
16-Feb-2020 12:02:32 MUST
16-Feb-2020 12:04:17 Test ANVL-BGPPLUS-41.10: Passed
16-Feb-2020 12:04:17
16-Feb-2020 12:04:19 Test ANVL-BGPPLUS-41.11 executing
16-Feb-2020 12:04:19 Test Summary
16-Feb-2020 12:04:19 If any attribute has Attribute Flags that conflict with the
16-Feb-2020 12:04:19 Attribute Type Code, then the error SHOULD be logged, and the
16-Feb-2020 12:04:19 Attribute Flags MUST be reset to the correct value.  The UPDATE
16-Feb-2020 12:04:19 message MUST continue to be processed.
16-Feb-2020 12:04:19 (NOTE:This test only checks for Processing
16-Feb-2020 12:04:19 This test checks for ATOMIC AGGREGATE
16-Feb-2020 12:04:19 (well known discretionary) attribute and for Transitive Bit)
16-Feb-2020 12:04:19 Test Reference
16-Feb-2020 12:04:19 draft-ietf-idr-error-handling-01.txt Section 2 Page 3 ' Revision to Base Specification'
16-Feb-2020 12:04:19 UPDATE message error handling
16-Feb-2020 12:04:19 Test Classification
16-Feb-2020 12:04:19 MUST
16-Feb-2020 12:06:02 Test ANVL-BGPPLUS-41.11: Passed
16-Feb-2020 12:06:02
16-Feb-2020 12:06:04 Test ANVL-BGPPLUS-41.12 executing
16-Feb-2020 12:06:04 Test Summary
16-Feb-2020 12:06:04 If any attribute has Attribute Flags that conflict with the
16-Feb-2020 12:06:04 Attribute Type Code, then the error SHOULD be logged, and the
16-Feb-2020 12:06:04 Attribute Flags MUST be reset to the correct value.  The UPDATE
16-Feb-2020 12:06:04 message MUST continue to be processed.
16-Feb-2020 12:06:04 (NOTE:This test only checks for Processing
16-Feb-2020 12:06:04 This test checks for ATOMIC AGGREGATE
16-Feb-2020 12:06:04 (well known discretionary) attribute and for Partial Bit)
16-Feb-2020 12:06:04 Test Reference
16-Feb-2020 12:06:04 draft-ietf-idr-error-handling-01.txt Section 2 Page 3 ' Revision to Base Specification'
16-Feb-2020 12:06:04 UPDATE message error handling
16-Feb-2020 12:06:04 Test Classification
16-Feb-2020 12:06:04 MUST
16-Feb-2020 12:07:48 Test ANVL-BGPPLUS-41.12: Passed
16-Feb-2020 12:07:48
16-Feb-2020 12:07:49 Test ANVL-BGPPLUS-41.13 executing
16-Feb-2020 12:07:49 Test Summary
16-Feb-2020 12:07:49 If any attribute has Attribute Flags that conflict with the
16-Feb-2020 12:07:49 Attribute Type Code, then the error SHOULD be logged, and the
16-Feb-2020 12:07:49 Attribute Flags MUST be reset to the correct value.  The UPDATE
16-Feb-2020 12:07:49 message MUST continue to be processed.
16-Feb-2020 12:07:49 (NOTE:This test only checks for Processing
16-Feb-2020 12:07:49 This test checks for AGGREGATOR
16-Feb-2020 12:07:49 (optional transitive) attribute and for Optional Bit)
16-Feb-2020 12:07:49 Test Reference
16-Feb-2020 12:07:49 draft-ietf-idr-error-handling-01.txt Section 2 Page 3 ' Revision to Base Specification'
16-Feb-2020 12:07:49 UPDATE message error handling
16-Feb-2020 12:07:49 Test Classification
16-Feb-2020 12:07:49 MUST
16-Feb-2020 12:09:33 Test ANVL-BGPPLUS-41.13: Passed
16-Feb-2020 12:09:33
16-Feb-2020 12:09:34 Test ANVL-BGPPLUS-41.14 executing
16-Feb-2020 12:09:34 Test Summary
16-Feb-2020 12:09:34 The approach of "treat-as-withdraw" MUST be used for the error
16-Feb-2020 12:09:34 handling of the cases described in Section 6.3 of [RFC4271] that
16-Feb-2020 12:09:34 specify a session reset and involve any of the following attributes:
16-Feb-2020 12:09:34 ORIGIN, AS_PATH, NEXT_HOP, MULTI_EXIT_DISC, and LOCAL_PREF.
16-Feb-2020 12:09:34 (Note: This test checks by sending incorrect length for ORIGIN
16-Feb-2020 12:09:34 attribute)
16-Feb-2020 12:09:34 Test Reference
16-Feb-2020 12:09:34 draft-ietf-idr-error-handling-01.txt Section 2 Page 4 ' Revision to Base Specification'UPDATE message error handling
16-Feb-2020 12:09:34 Test Classification
16-Feb-2020 12:09:34 MUST
16-Feb-2020 12:12:40 Test ANVL-BGPPLUS-41.14: Passed
16-Feb-2020 12:12:40
16-Feb-2020 12:12:42 Test ANVL-BGPPLUS-41.15 executing
16-Feb-2020 12:12:42 Test Summary
16-Feb-2020 12:12:42 The approach of "treat-as-withdraw" MUST be used for the error
16-Feb-2020 12:12:42 handling of the cases described in Section 6.3 of [RFC4271] that
16-Feb-2020 12:12:42 specify a session reset and involve any of the following attributes:
16-Feb-2020 12:12:42 ORIGIN, AS_PATH, NEXT_HOP, MULTI_EXIT_DISC, and LOCAL_PREF.
16-Feb-2020 12:12:42 (Note: This test checks by sending incorrect length for MULTI_EXIT_DISC
16-Feb-2020 12:12:42 attribute)
16-Feb-2020 12:12:42 Test Reference
16-Feb-2020 12:12:42 draft-ietf-idr-error-handling-01.txt Section 2 Page 4 ' Revision to Base Specification'UPDATE message error handling
16-Feb-2020 12:12:42 Test Classification
16-Feb-2020 12:12:42 MUST
16-Feb-2020 12:15:48 Test ANVL-BGPPLUS-41.15: Passed
16-Feb-2020 12:15:48
16-Feb-2020 12:15:50 Test ANVL-BGPPLUS-41.16 executing
16-Feb-2020 12:15:50 Test Summary
16-Feb-2020 12:15:50 The approach of "treat-as-withdraw" MUST be used for the error
16-Feb-2020 12:15:50 handling of the cases described in Section 6.3 of [RFC4271] that
16-Feb-2020 12:15:50 specify a session reset and involve any of the following attributes:
16-Feb-2020 12:15:50 ORIGIN, AS_PATH, NEXT_HOP, MULTI_EXIT_DISC, and LOCAL_PREF.
16-Feb-2020 12:15:50 (Note: This test checks by sending incorrect length for LOCAL_PREF
16-Feb-2020 12:15:50 attribute)
16-Feb-2020 12:15:50 Test Reference
16-Feb-2020 12:15:50 draft-ietf-idr-error-handling-01.txt Section 2 Page 4 ' Revision to Base Specification'UPDATE message error handling
16-Feb-2020 12:15:50 Test Classification
16-Feb-2020 12:15:50 MUST
16-Feb-2020 12:18:56 Test ANVL-BGPPLUS-41.16: Passed
16-Feb-2020 12:18:56
16-Feb-2020 12:18:57 Test ANVL-BGPPLUS-41.17 executing
16-Feb-2020 12:18:57 Test Summary
16-Feb-2020 12:18:57 The approach of "attribute discard" MUST be used for the error
16-Feb-2020 12:18:57 handling of the cases described in Section 6.3 of [RFC4271] that
16-Feb-2020 12:18:57 specify a session reset and involve any of the following attributes:
16-Feb-2020 12:18:57 ATOMIC_AGGREGATE and AGGREGATOR.
16-Feb-2020 12:18:57 (Note: This test checks by sending incorrect length for ATOMIC_AGGREGATE
16-Feb-2020 12:18:57 attribute)
16-Feb-2020 12:18:57 Test Reference
16-Feb-2020 12:18:57 draft-ietf-idr-error-handling-01.txt Section 2 Page 4 ' Revision to Base Specification'UPDATE message error handling
16-Feb-2020 12:18:57 Test Classification
16-Feb-2020 12:18:57 MUST
16-Feb-2020 12:21:51 Test ANVL-BGPPLUS-41.17: Passed
16-Feb-2020 12:21:51
16-Feb-2020 12:21:52 Test ANVL-BGPPLUS-41.18 executing
16-Feb-2020 12:21:52 Test Summary
16-Feb-2020 12:21:52 The approach of "treat-as-withdraw" MUST be used for the error
16-Feb-2020 12:21:52 handling of the cases described in Section 6.3 of [RFC4271] that
16-Feb-2020 12:21:52 specify a session reset and involve any of the following attributes:
16-Feb-2020 12:21:52 ORIGIN, AS_PATH, NEXT_HOP, MULTI_EXIT_DISC, and LOCAL_PREF.
16-Feb-2020 12:21:52 (This test checks for well-known mandatory attributes missing.For IBGP)
16-Feb-2020 12:21:52 Test Reference
16-Feb-2020 12:21:52 draft-ietf-idr-error-handling-01.txt Section 2 Page 4 ' Revision to Base Specification'UPDATE message error handling
16-Feb-2020 12:21:52 Test Classification
16-Feb-2020 12:21:52 MUST
16-Feb-2020 12:31:05 Test ANVL-BGPPLUS-41.18: Passed
16-Feb-2020 12:31:05
16-Feb-2020 12:31:07 Test ANVL-BGPPLUS-41.19 executing
16-Feb-2020 12:31:07 Test Summary
16-Feb-2020 12:31:07 The approach of "treat-as-withdraw" MUST be used for the error
16-Feb-2020 12:31:07 handling of the cases described in Section 6.3 of [RFC4271] that
16-Feb-2020 12:31:07 specify a session reset and involve any of the following attributes:
16-Feb-2020 12:31:07 ORIGIN, AS_PATH, NEXT_HOP, MULTI_EXIT_DISC, and LOCAL_PREF.
16-Feb-2020 12:31:07 (This test checks for well-known mandatory attributes missing.For EBGP)
16-Feb-2020 12:31:07 Test Reference
16-Feb-2020 12:31:07 draft-ietf-idr-error-handling-01.txt Section 2 Page 4 ' Revision to Base Specification'UPDATE message error handling
16-Feb-2020 12:31:07 Test Classification
16-Feb-2020 12:31:07 MUST
16-Feb-2020 12:37:16 Test ANVL-BGPPLUS-41.19: Passed
16-Feb-2020 12:37:16
16-Feb-2020 12:37:18 Test ANVL-BGPPLUS-41.20 executing
16-Feb-2020 12:37:18 Test Summary
16-Feb-2020 12:37:18 The approach of "treat-as-withdraw" MUST be used for the error
16-Feb-2020 12:37:18 handling of the cases described in Section 6.3 of [RFC4271] that
16-Feb-2020 12:37:18 specify a session reset and involve any of the following attributes:
16-Feb-2020 12:37:18 ORIGIN, AS_PATH, NEXT_HOP, MULTI_EXIT_DISC, and LOCAL_PREF.
16-Feb-2020 12:37:18 (NOTE:ORIGIN attribute has an undefined value)
16-Feb-2020 12:37:18 Test Reference
16-Feb-2020 12:37:18 draft-ietf-idr-error-handling-01.txt Section 2 Page 4 ' Revision to Base Specification'
16-Feb-2020 12:37:18 UPDATE message error handling
16-Feb-2020 12:37:18 Test Classification
16-Feb-2020 12:37:18 MUST
16-Feb-2020 12:40:24 Test ANVL-BGPPLUS-41.20: Passed
16-Feb-2020 12:40:24
16-Feb-2020 12:40:26 Test ANVL-BGPPLUS-41.21 executing
16-Feb-2020 12:40:26 Test Summary
16-Feb-2020 12:40:26 The approach of "treat-as-withdraw" MUST be used for the error
16-Feb-2020 12:40:26 handling of the cases described in Section 6.3 of [RFC4271] that
16-Feb-2020 12:40:26 specify a session reset and involve any of the following attributes:
16-Feb-2020 12:40:26 ORIGIN, AS_PATH, NEXT_HOP, MULTI_EXIT_DISC, and LOCAL_PREF.
16-Feb-2020 12:40:26 (NOTE:AS_PATH attribute is syntactically incorrect)
16-Feb-2020 12:40:26 Test Reference
16-Feb-2020 12:40:26 draft-ietf-idr-error-handling-01.txt Section 2 Page 4 ' Revision to Base Specification'
16-Feb-2020 12:40:26 UPDATE message error handling
16-Feb-2020 12:40:26 Test Classification
16-Feb-2020 12:40:26 MUST
16-Feb-2020 12:43:32 Test ANVL-BGPPLUS-41.21: Passed
16-Feb-2020 12:43:32
16-Feb-2020 12:43:33 Test ANVL-BGPPLUS-41.22 executing
16-Feb-2020 12:43:33 Test Summary
16-Feb-2020 12:43:33 The AGGREGATOR attribute SHALL be considered malformed if any of the
16-Feb-2020 12:43:33 following applies:
16-Feb-2020 12:43:33    Its length is not 6 (when the "4-octet AS number capability" is
16-Feb-2020 12:43:33      not advertised to, or not received from the peer [RFC4893]).
16-Feb-2020 12:43:33    Its length is not 8 (when the "4-octet AS number capability" is
16-Feb-2020 12:43:33      both advertised to, and received from the peer).
16-Feb-2020 12:43:33 An UPDATE message with a malformed AGGREGATOR attribute SHALL be
16-Feb-2020 12:43:33 Test Reference
16-Feb-2020 12:43:33 draft-ietf-idr-error-handling-01.txt Section 5.1 Page 6 ' AGGREGATOR'
16-Feb-2020 12:43:33 Test Classification
16-Feb-2020 12:43:33 MUST
16-Feb-2020 12:45:17 Test ANVL-BGPPLUS-41.22: Passed
16-Feb-2020 12:45:17
16-Feb-2020 12:45:18 Test ANVL-BGPPLUS-41.25 executing
16-Feb-2020 12:45:18 Test Summary
16-Feb-2020 12:45:18 When multiple malformed attributes exist in an UPDATE message, if the
16-Feb-2020 12:45:18 same approach (either "treat-as-withdraw" or "attribute discard") is
16-Feb-2020 12:45:18 specified for the handling of these malformed attributes, then the
16-Feb-2020 12:45:18 specified approach MUST be used. Otherwise "treat-as-withdraw" MUST
16-Feb-2020 12:45:18 be used.
16-Feb-2020 12:45:18 (NOTE:ORIGIN and AS_PATH attribute field malformed and Same approach
16-Feb-2020 12:45:18    specified for both the malformed attributes i.e 'treat as withdraw')
16-Feb-2020 12:45:18 Test Reference
16-Feb-2020 12:45:18 draft-ietf-idr-error-handling-01.txt Section 2 Page 4 ' Revision to Base Specification'
16-Feb-2020 12:45:18 UPDATE message error handling
16-Feb-2020 12:45:18 Test Classification
16-Feb-2020 12:45:18 MUST
16-Feb-2020 12:48:24 Test ANVL-BGPPLUS-41.25: Passed
16-Feb-2020 12:48:24
16-Feb-2020 12:48:26 Test ANVL-BGPPLUS-41.26 executing
16-Feb-2020 12:48:26 Test Summary
16-Feb-2020 12:48:26 When multiple malformed attributes exist in an UPDATE message, if the
16-Feb-2020 12:48:26 same approach (either "treat-as-withdraw" or "attribute discard") is
16-Feb-2020 12:48:26 specified for the handling of these malformed attributes, then the
16-Feb-2020 12:48:26 specified approach MUST be used. Otherwise "treat-as-withdraw" MUST
16-Feb-2020 12:48:26 be used.
16-Feb-2020 12:48:26 (NOTE:ORIGIN, AS_PATH and AGGREGATOR attribute field malformed and Same approach
16-Feb-2020 12:48:26    not specified for all the malformed attributes i.e 'treat as withdraw')
16-Feb-2020 12:48:26 Test Reference
16-Feb-2020 12:48:26 draft-ietf-idr-error-handling-01.txt Section 2 Page 4 ' Revision to Base Specification'
16-Feb-2020 12:48:26 Test Classification
16-Feb-2020 12:48:26 MUST
16-Feb-2020 12:51:33 Test ANVL-BGPPLUS-41.26: Passed
16-Feb-2020 12:51:33
16-Feb-2020 12:51:34 Test ANVL-BGPPLUS-41.28 executing
16-Feb-2020 12:51:34 Test Summary
16-Feb-2020 12:51:34 To facilitate the determination of the NLRI field
16-Feb-2020 12:51:34 in an UPDATE with a malformed attribute, the MP_REACH
16-Feb-2020 12:51:34 or MP_UNREACH attribute (if present) SHOULD be encoded
16-Feb-2020 12:51:34 as the very first path attribute in an UPDATE as
16-Feb-2020 12:51:34 recommended by [RFC4760bis].  An implementation, however,
16-Feb-2020 12:51:34 MUST still be prepared to receive these fields in any position.
16-Feb-2020 12:51:34 (NOTE:ANVL checks if DUT receive these field in any position
16-Feb-2020 12:51:34 MP_REACH_NLRI attribute encoded as last path attribute in the UPDATE message
16-Feb-2020 12:51:34 Test Reference
16-Feb-2020 12:51:34 draft-ietf-idr-error-handling-01.txt Section 3 Page 5 'Parsing of NLRI Fields'
16-Feb-2020 12:51:34 UPDATE message error handling
16-Feb-2020 12:51:34 Test Classification
16-Feb-2020 12:51:34 MUST
16-Feb-2020 12:53:18 Test ANVL-BGPPLUS-41.28: Passed
16-Feb-2020 12:53:18
16-Feb-2020 12:53:19 Test ANVL-BGPPLUS-41.29 executing
16-Feb-2020 12:53:19 Test Summary
16-Feb-2020 12:53:19 To facilitate the determination of the NLRI field
16-Feb-2020 12:53:19 in an UPDATE with a malformed attribute, the MP_REACH
16-Feb-2020 12:53:19 or MP_UNREACH attribute (if present) SHOULD be encoded
16-Feb-2020 12:53:19 as the very first path attribute in an UPDATE as
16-Feb-2020 12:53:19 recommended by [RFC4760bis].  An implementation, however,
16-Feb-2020 12:53:19 MUST still be prepared to receive these fields in any position.
16-Feb-2020 12:53:19 (NOTE:ANVL checks if DUT receive these field in any position
16-Feb-2020 12:53:19 MP_UNREACH_NLRI attribute encoded as last path attribute in the UPDATE message
16-Feb-2020 12:53:19 Test Reference
16-Feb-2020 12:53:19 draft-ietf-idr-error-handling-01.txt Section 3 Page 5 'Parsing of NLRI Fields'
16-Feb-2020 12:53:19 UPDATE message error handling
16-Feb-2020 12:53:19 Test Classification
16-Feb-2020 12:53:19 MUST
16-Feb-2020 12:56:25 Test ANVL-BGPPLUS-41.29: Passed
16-Feb-2020 12:56:25
16-Feb-2020 12:56:27 Test ANVL-BGPPLUS-42.1 executing
16-Feb-2020 12:56:27 Test Summary
16-Feb-2020 12:56:27 If any attribute has Attribute Flags that conflict with the
16-Feb-2020 12:56:27 Attribute Type Code, then the error SHOULD be logged.
16-Feb-2020 12:56:27 (NOTE:Error Log Checking)
16-Feb-2020 12:56:27 (This test checks for mandatory well-known attributes, Optional Bit
16-Feb-2020 12:56:27 and External Peer)
16-Feb-2020 12:56:27 Test Reference
16-Feb-2020 12:56:27 draft-ietf-idr-error-handling-01.txt Section 2 Page 3 ' Revision to Base Specification'
16-Feb-2020 12:56:27 UPDATE message error handling
16-Feb-2020 12:56:27 Test Classification
16-Feb-2020 12:56:27 SHOULD
16-Feb-2020 12:57:26 Test ANVL-BGPPLUS-42.1: Passed
16-Feb-2020 12:57:26
16-Feb-2020 12:57:28 Test ANVL-BGPPLUS-42.2 executing
16-Feb-2020 12:57:28 Test Summary
16-Feb-2020 12:57:28 If any attribute has Attribute Flags that conflict with the
16-Feb-2020 12:57:28 Attribute Type Code, then the error SHOULD be logged.
16-Feb-2020 12:57:28 (NOTE:Error Log Checking)
16-Feb-2020 12:57:28 (This test checks for mandatory well-known attributes, Optional Bit
16-Feb-2020 12:57:28 and External Peer)
16-Feb-2020 12:57:28 Test Reference
16-Feb-2020 12:57:28 draft-ietf-idr-error-handling-01.txt Section 2 Page 3 ' Revision to Base Specification'
16-Feb-2020 12:57:28 UPDATE message error handling
16-Feb-2020 12:57:28 Test Classification
16-Feb-2020 12:57:28 SHOULD
16-Feb-2020 12:58:55 Test ANVL-BGPPLUS-42.2: Passed
16-Feb-2020 12:58:55
16-Feb-2020 12:58:57 Test ANVL-BGPPLUS-42.3 executing
16-Feb-2020 12:58:57 Test Summary
16-Feb-2020 12:58:57 If any attribute has Attribute Flags that conflict with the
16-Feb-2020 12:58:57 Attribute Type Code, then the error SHOULD be logged.
16-Feb-2020 12:58:57 (NOTE:Error Log Checking)
16-Feb-2020 12:58:57 (Note : This test checks for mandatory well-known attributes,
16-Feb-2020 12:58:57 Transitive Bit and Internal Peer)
16-Feb-2020 12:58:57 Test Reference
16-Feb-2020 12:58:57 draft-ietf-idr-error-handling-01.txt Section 2 Page 3 ' Revision to Base Specification'
16-Feb-2020 12:58:57 UPDATE message error handling
16-Feb-2020 12:58:57 Test Classification
16-Feb-2020 12:58:57 SHOULD
16-Feb-2020 13:00:24 Test ANVL-BGPPLUS-42.3: Passed
16-Feb-2020 13:00:24
16-Feb-2020 13:00:26 Test ANVL-BGPPLUS-42.4 executing
16-Feb-2020 13:00:26 Test Summary
16-Feb-2020 13:00:26 If any attribute has Attribute Flags that conflict with the
16-Feb-2020 13:00:26 Attribute Type Code, then the error SHOULD be logged.
16-Feb-2020 13:00:26 (NOTE:Error Log Checking)
16-Feb-2020 13:00:26 (Note : This test checks for mandatory well-known attributes,
16-Feb-2020 13:00:26 Partial Bit and Internal Peer)
16-Feb-2020 13:00:26 Test Reference
16-Feb-2020 13:00:26 draft-ietf-idr-error-handling-01.txt Section 2 Page 3 ' Revision to Base Specification'
16-Feb-2020 13:00:26 UPDATE message error handling
16-Feb-2020 13:00:26 Test Classification
16-Feb-2020 13:00:26 SHOULD
16-Feb-2020 13:01:43 Test ANVL-BGPPLUS-42.4: Passed
16-Feb-2020 13:01:43
16-Feb-2020 13:01:45 Test ANVL-BGPPLUS-42.5 executing
16-Feb-2020 13:01:45 Test Summary
16-Feb-2020 13:01:45 If any attribute has Attribute Flags that conflict with the
16-Feb-2020 13:01:45 Attribute Type Code, then the error SHOULD be logged
16-Feb-2020 13:01:45 (NOTE:Error Log Checking)
16-Feb-2020 13:01:45 (Note : This test checks for MULTI_EXIT_DISC
16-Feb-2020 13:01:45 (optional non-transitive) attribute and for Optional Bit)
16-Feb-2020 13:01:45 Test Reference
16-Feb-2020 13:01:45 draft-ietf-idr-error-handling-01.txt Section 2 Page 3 ' Revision to Base Specification'
16-Feb-2020 13:01:45 UPDATE message error handling
16-Feb-2020 13:01:45 Test Classification
16-Feb-2020 13:01:45 SHOULD
16-Feb-2020 13:02:16 Test ANVL-BGPPLUS-42.5: Passed
16-Feb-2020 13:02:16
16-Feb-2020 13:02:18 Test ANVL-BGPPLUS-42.6 executing
16-Feb-2020 13:02:18 Test Summary
16-Feb-2020 13:02:18 If any attribute has Attribute Flags that conflict with the
16-Feb-2020 13:02:18 Attribute Type Code, then the error SHOULD be logged
16-Feb-2020 13:02:18 (NOTE:Error Log Checking)
16-Feb-2020 13:02:18 (Note : This test checks for ATOMIC_AGGREGATE
16-Feb-2020 13:02:18 (Well known discretionary) attribute and for Optional Bit)
16-Feb-2020 13:02:18 Test Reference
16-Feb-2020 13:02:18 draft-ietf-idr-error-handling-01.txt Section 2 Page 3 ' Revision to Base Specification'
16-Feb-2020 13:02:18 UPDATE message error handling
16-Feb-2020 13:02:18 Test Classification
16-Feb-2020 13:02:18 SHOULD
16-Feb-2020 13:02:38 Test ANVL-BGPPLUS-42.6: Passed
16-Feb-2020 13:02:38
16-Feb-2020 13:02:40 Test ANVL-BGPPLUS-42.7 executing
16-Feb-2020 13:02:40 Test Summary
16-Feb-2020 13:02:40 Because of these potential issues, a BGP speaker MUST provide
16-Feb-2020 13:02:40 debugging facilities to permit issues caused by a malformed attribute
16-Feb-2020 13:02:40 to be diagnosed. At a minimum, such facilities MUST include logging an
16-Feb-2020 13:02:40 error listing the NLRI involved, and containing the entire malformed
16-Feb-2020 13:02:40 UPDATE message when such an attribute is detected.
16-Feb-2020 13:02:40 (Note : This test checks sending Wrong Attribute flags conflicting with
16-Feb-2020 13:02:40 Attribute type Code for well-known
16-Feb-2020 13:02:40 madatory attribute, and error lists NLRI involved)
16-Feb-2020 13:02:40 Test Reference
16-Feb-2020 13:02:40 draft-ietf-idr-error-handling-01.txt Section 4 Page 6 'Operational Considerations'
16-Feb-2020 13:02:40 UPDATE message error handling
16-Feb-2020 13:02:40 Test Classification
16-Feb-2020 13:02:40 MUST
16-Feb-2020 13:03:11 Test ANVL-BGPPLUS-42.7: Passed
16-Feb-2020 13:03:11
16-Feb-2020 13:03:13 Writing DejaGNU Result file to ./bgpplus-result.xml
16-Feb-2020 13:03:13 Finished task 'Run Basic BGP4 IPv6 Tests' with result: Success
16-Feb-2020 13:03:13 Starting task 'Collect ANVL Results' of type 'com.atlassian.bamboo.plugins.testresultparser:task.testresultparser.junit'
16-Feb-2020 13:03:13 Parsing test results under /root/bamboo-agent-home/xml-data/build-dir/FRR-FRR73SNAP-IPV6BGP4...
16-Feb-2020 13:03:13 Finished task 'Collect ANVL Results' with result: Success
16-Feb-2020 13:03:13 Running post build plugin 'Docker Container Cleanup'
16-Feb-2020 13:03:13 Running post build plugin 'NCover Results Collector'
16-Feb-2020 13:03:13 Running post build plugin 'Clover Results Collector'
16-Feb-2020 13:03:13 Running post build plugin 'npm Cache Cleanup'
16-Feb-2020 13:03:13 Running post build plugin 'Artifact Copier'
16-Feb-2020 13:03:13 Successfully removed working directory at '/root/bamboo-agent-home/xml-data/build-dir/FRR-FRR73SNAP-IPV6BGP4'
16-Feb-2020 13:03:13 Finalising the build...
16-Feb-2020 13:03:13 Stopping timer.
16-Feb-2020 13:03:13 Build FRR-FRR73SNAP-IPV6BGP4-2 completed.
16-Feb-2020 13:03:13 Running on server: post build plugin 'NCover Results Collector'
16-Feb-2020 13:03:13 Running on server: post build plugin 'Build Hanging Detection Configuration'
16-Feb-2020 13:03:13 Running on server: post build plugin 'Clover Delta Calculator'
16-Feb-2020 13:03:13 Running on server: post build plugin 'Maven Dependencies Postprocessor'
16-Feb-2020 13:03:13 All post build plugins have finished
16-Feb-2020 13:03:13 Generating build results summary...
16-Feb-2020 13:03:13 Saving build results to disk...
16-Feb-2020 13:03:13 Logging substituted variables...
16-Feb-2020 13:03:13 Indexing build results...
16-Feb-2020 13:03:13 Finished building FRR-FRR73SNAP-IPV6BGP4-2.