Skip to content

default ptp profile test description · Changes

Page history
Update default ptp profile test description authored by Maciej Lipinski's avatar Maciej Lipinski
Hide whitespace changes
Inline Side-by-side
default-ptp-profile-test-description.md
View page @ 61d8e719
......@@ -13,82 +13,79 @@ The tests that we expect the WR Switch to pass are listed below. There is a numb
| TEST Name | Test Purpose Description | IEEE802.3 and/or UDP | v5.0.1| v6.0 |
| --------- | ------ |--------- | ------ |------ |
|BEG_001 |Verify that a boundary clock is elected as the Master based on Priority1. | | | |
|BEG_002 |Verify that in a boundary clock, the Master state is elected based on the clockClass value, when an Announce message with same Priority1 is received from the neighbour. | | | |
|BEG_003 |Verify that in a boundary clock, the Master state is elected based on the clockAccuracy value, when an Announce message with same Priority1 and clockClass value is received from the neighbour. | | | |
|BEG_004 |Verify that in a boundary clock, the Master state is elected based on the Variance value, when an Announce message with same Priority1, clockClass and clockAccuracy value is received from the neighbour. | | | |
|BEG_005 | Verify that in a boundary clock, the Master state is elected based on the Priority2 value, when an Announce message with same Priority1, clockClass, clockAccuracy and Variance value is received from the neighbour.| | | |
|MFG_001 | Verify that the boundary clock sends the UDP/IPv4 Announce message with following frame format.| UDP | | |
|MFG_002 |Verify that the boundary clock sends the UDP/IPv4 Sync message with following frame format. |UDP | | |
|MFG_003 | Verify that the boundary clock sends the UDP/IPv4 Follow_Up message with following frame format.| UDP| | |
|MFG_004 |Verify that the boundary clock sends the UDP/IPv4 Delay_Req message with following frame format. |UDP | | |
|MFG_005 |Verify that the boundary clock sends the UDP/IPv4 Delay_Resp message with following frame format. | UDP| | |
|MFG_006 |Verify that the boundary clock sends the UDP/IPv4 PDelay_Resp message with following frame format. | UDP| | |
|MFG_007 | Verify that the boundary clock sends the UDP/IPv4 PDelay_Resp_Follow_Up message with following frame format.| UDP| | |
|MFG_008 |Verify that the boundary clock sends the IEEE 802.3 Announce message with following frame format. | IEEE802.3| | |
|MFG_009 |Verify that the boundary clock sends the IEEE 802.3 Sync message with following frame format. |IEEE802.3 | | |
|MFG_010 |Verify that the boundary clock sends the IEEE 802.3 Follow_Up message with following frame format. |IEEE802.3 | | |
|MFG_011 |Verify that the boundary clock sends the IEEE 802.3 Delay_Req message with following frame format. |IEEE802.3 | | |
|MFG_012 | Verify that the boundary clock sends the IEEE 802.3 Delay_Resp message with following frame format.| IEEE802.3| | |
|MFG_013 |Verify that the boundary clock sends the IEEE 802.3 PDelay_Resp message with following frame format. |IEEE802.3 | | |
|MFG_014 |Verify that the boundary clock sends the IEEE 802.3 PDelay_Resp_Follow_Up message with following frame format. | IEEE802.3| | |
|MFG_015 |Verify that the boundary clock sends the IEEE 802.3 PDelay_Req message with following frame format . | IEEE802.3| | |
|BEG_001 |Verify that a boundary clock is elected as the Master based on Priority1. |both | passed|passed |
|BEG_002 |Verify that in a boundary clock, the Master state is elected based on the clockClass value, when an Announce message with same Priority1 is received from the neighbour. |both |passed |passed |
|BEG_003 |Verify that in a boundary clock, the Master state is elected based on the clockAccuracy value, when an Announce message with same Priority1 and clockClass value is received from the neighbour. | both| passed|passed |
|BEG_004 |Verify that in a boundary clock, the Master state is elected based on the Variance value, when an Announce message with same Priority1, clockClass and clockAccuracy value is received from the neighbour. |both |passed |passed |
|BEG_005 | Verify that in a boundary clock, the Master state is elected based on the Priority2 value, when an Announce message with same Priority1, clockClass, clockAccuracy and Variance value is received from the neighbour.|both | passed| passed|
|MFG_001 | Verify that the boundary clock sends the UDP/IPv4 Announce message with following frame format.| UDP | passed| passed|
|MFG_002 |Verify that the boundary clock sends the UDP/IPv4 Sync message with following frame format. |UDP |passed |passed |
|MFG_003 | Verify that the boundary clock sends the UDP/IPv4 Follow_Up message with following frame format.| UDP|passed | passed|
|MFG_004 |Verify that the boundary clock sends the UDP/IPv4 Delay_Req message with following frame format. |UDP |passed | passed|
|MFG_005 |Verify that the boundary clock sends the UDP/IPv4 Delay_Resp message with following frame format. | UDP|passed | passed|
|MFG_006 |Verify that the boundary clock sends the UDP/IPv4 PDelay_Resp message with following frame format. | UDP|passed |passed |
|MFG_007 | Verify that the boundary clock sends the UDP/IPv4 PDelay_Resp_Follow_Up message with following frame format.| UDP| passed| passed|
|MFG_008 |Verify that the boundary clock sends the IEEE 802.3 Announce message with following frame format. | IEEE802.3|passed |passed |
|MFG_009 |Verify that the boundary clock sends the IEEE 802.3 Sync message with following frame format. |IEEE802.3 |passed | passed|
|MFG_010 |Verify that the boundary clock sends the IEEE 802.3 Follow_Up message with following frame format. |IEEE802.3 | passed|passed |
|MFG_011 |Verify that the boundary clock sends the IEEE 802.3 Delay_Req message with following frame format. |IEEE802.3 |passed | passed|
|MFG_012 | Verify that the boundary clock sends the IEEE 802.3 Delay_Resp message with following frame format.| IEEE802.3|passed |passed |
|MFG_013 |Verify that the boundary clock sends the IEEE 802.3 PDelay_Resp message with following frame format. |IEEE802.3 |passed |passed |
|MFG_014 |Verify that the boundary clock sends the IEEE 802.3 PDelay_Resp_Follow_Up message with following frame format. | IEEE802.3|passed |passed |
|MFG_015 |Verify that the boundary clock sends the IEEE 802.3 PDelay_Req message with following frame format . | IEEE802.3|passed |passed |
|MFG_016 |Verify that the boundary clock sends the UDP/IPv4 PDelay_Req message with following frame format. |UDP | |
| MHG_001|Verify that the boundary clock discards Pdelay_Req message when it is configured with delay request-response mechanism. | | | |
|MHG_002|Verify that the boundary clock discards Delay_Req message when it is configured with peer delay mechanism. | | | |
|MHG_003 |Verify that the boundary clocks does not accept messages with different domain number than configured. | | | |
|MHG_004 | Verify that the boundary clock terminates all multicast Announce messages received on the port.| | | |
|MHG_005 | Verify that the boundary clock terminates all multicast Sync messages received on the port.| | | |
|MHG_006 | Verify that the boundary clock terminates all multicast Follow_Up messages received on the port. | | | |
|MHG_007 |Verify that the boundary clock terminates all multicast Delay_Req messages received on the port. | | | |
|MHG_008 |Verify that the boundary clock terminates all multicast Delay_Resp messages received on the port. | | | |
|MHG_009 |Verify that the boundary clock terminates all multicast Pdelay_Req messages received on the port. | | | |
|MHG_010 |Verify that the boundary clock ignores the Delay_Req message received on the port from which it was issued. | | | |
|MHG_011 |Verify that the boundary clock transmits Delay_Resp message as Multicast on reception of multicast Delay_Req messages. | | | |
|MHG_013 |Verify that the boundary clock terminates all multicast Pdelay_Resp messages received on the port. | | | |
|MHG_014 |Verify that the boundary clock terminates all multicast Pdelay_Resp_Follow_Up messages received on the port. | | | |
|MHG_015 |Verify that the boundary clock ignores the Pdelay_Req message received on the port from which it was issued. | | | |
|MTG_001 | Verify that the boundary clock transmits Delay_Req message on receiving Sync/ Sync and Follow_Up based on clock step on its slave port.| | | |
|MTG_002 |Verify that the boundary clock uses incremental sequence id for consecutive Announce messages. | | | |
|MTG_003 |Verify that the boundary clock uses incremental sequence id for consecutive Sync messages. | | | |
|MTG_004 |Verify that the boundary clock uses incremental sequence id for consecutive Delay_Req messages. | | | |
|MTG_005 |Verify that the boundary clock port supporting Delay Request-Response mechanism acting as master has alternateMasterFlag set to FALSE in Announce,Sync, Follow_Up,Delay_Resp PTP messsages | | | |
|MTG_006 |Verify that the boundary clock transmits Announce messages for every announce interval. | | | |
| MTG_007| Verify that the boundary clock transmits Sync messages for every sync interval.| | | |
|MTG_008 |Verify that the boundary clock transmits Delay_Resp message on receiving Delay_Req on its master port. | | | |
|MTG_009 |Verify that the sequenceID and SourcePortIdentity field of received Follow_Up message shall match the sequenceId and SourcePortIdentity field of the prior Sync message respectively. | | | |
|MTG_010 |Verify that the requestingSequenceId and requestingSourcePortIdentity field of Delay_Resp message shall match the sequenceId and SourcePortIdentity field of the associated Delay_Req message respectively. | | | |
| MTG_012| Verify that the boundary clock transmits Pdelay_Resp/ Pdelay_Resp and Pdelay_Resp_Follow_up message on receiving Pdelay_Req on its master port.| | | |
|MTG_013 |Verify that the sequenceId field, requestingSourcePortIdentity and domain number of Pdelay_Resp message shall match the sequenceId,SourcePortIdentity and domain number field of the associated Pdelay_Req message. | | | |
|MTG_014 |Verify that the correctionField, sequenceId field, requestingSourcePortIdentity and domain number of Pdelay_Resp_Follow_Up message shall match the correctionField, sequenceId, SourcePortIdentity and domain number field respectively of the associated Pdelay_Req message. | | | |
|MTG_015 | Verify that the boundary clock uses incremental sequence id for consecutive PDelay_Req messages.| | | |
|MTG_016 |Verify that the boundary clock transmits Pdelay_Req messages for every pdelay_request interval. | | | |
|MTG_017 |Verify that the boundary clock in multicast mode transmits Delay_Req message periodically at an interval between 0 and twice 2^portDS.logMinDelayReqInterval (where portDS.logMinDelayReqInterval is the logMessageInterval of last Delay_Resp message received). | | | |
|PCG_001 | Verify that the boundary clock allows to configure PTP on multiple ports.| | | |
| PCG_005|Verify that the boundary clock configured for multicast transmission in Master has the unicastFlag field as FALSE in Delay Request-Response | | | |
|PCG_006 |Verify that the boundary clock configured for multicast transmission has the unicastFlag field as FALSE in Peer Delay messages. | | | |
| PCG_009|Verify that the boundary clock configured for Two-Step clock has the twoStepFlag field as TRUE in Sync messages. | | | |
| PCG_010| Verify that the boundary clock configured for Two-Step clock has the twoStepFlag field as TRUE in PDelay_Resp messages.| | | |
| PCG_012| Verify that the boundary clock supports to configure priority2 to any value in range 0-255.| | | |
|PCG_018 |Verify that the boundary clock configured for multicast transmission in Slave has the unicastFlag field as FALSE in Delay Request message. | | | |
|SMG_002 |Verify that the boundary clock does not transmit any PTP messages on its port in DISABLED state. | | | |
|SMG_003 |Verify that the boundary clock discards any PTP messages that are received on its port in DISABLED state. | | | |
|SMG_004 |Verify that the boundary clock port in LISTENING state shall wait for the Announce receipt timeout to expire and transit to MASTER state. | | | |
|SMG_005 |Verify that the boundary clock port in LISTENING state shall wait to receive an Announce message to transit to MASTER/ SLAVE state. | | | |
|SMG_006 |Verify that the boundary clock port in MASTER state sends Announce messages periodically. | | | |
| SMG_007|Verify that the boundary clock port in SLAVE state sends Delay_Req messages. | | | |
| SMG_008| Verify that the boundary clock remains in SLAVE state if the same master continues| | | |
|SMG_010 |Verify that the boundary clock in LISTENING state moves to the SLAVE state when the master clock is selected. | | | |
|SMG_011 | Verify that the boundary clock in LISTENING state moves to DISABLED state when PTP is disabled at port.| | | |
|SMG_013 |Verify that the boundary clock in SLAVE state moves to DISABLED state when PTP is disabled at port. | | | |
|SMG_014 |Verify that the boundary clock in MASTER state moves to DISABLED state when PTP is disabled at port. | | | |
|SMG_015 | Verify that the boundary clock in SLAVE state moves to FAULTY state when a fault is detected.| | | |
|SMG_016 | Verify that the boundary clock in MASTER state moves to FAULTY state when a fault is detected.| | | |
|SMG_018 |Verify that the boundary clock in FAULTY state moves to DISABLED state when PTP is disabled at port. | | | |
|SMG_019 |Verify that the boundary clock in DISABLED state moves to the LISTENING state when PTP is enabled at port. | | | |
| | | | | |
| | | | | |
| | | | | |
| MHG_001|Verify that the boundary clock discards Pdelay_Req message when it is configured with delay request-response mechanism. |both |passed |passed |
|MHG_002|Verify that the boundary clock discards Delay_Req message when it is configured with peer delay mechanism. |both | failed|passed |
|MHG_003 |Verify that the boundary clocks does not accept messages with different domain number than configured. | both|passed |passed |
|MHG_004 | Verify that the boundary clock terminates all multicast Announce messages received on the port.|both | passed| passed|
|MHG_005 | Verify that the boundary clock terminates all multicast Sync messages received on the port.| both|passed |passed |
|MHG_006 | Verify that the boundary clock terminates all multicast Follow_Up messages received on the port. | both|passed |passed |
|MHG_007 |Verify that the boundary clock terminates all multicast Delay_Req messages received on the port. | both|passed |passed |
|MHG_008 |Verify that the boundary clock terminates all multicast Delay_Resp messages received on the port. |both |passed |passed |
|MHG_009 |Verify that the boundary clock terminates all multicast Pdelay_Req messages received on the port. |both | passed|passed |
|MHG_010 |Verify that the boundary clock ignores the Delay_Req message received on the port from which it was issued. |both |passed |passed |
|MHG_011 |Verify that the boundary clock transmits Delay_Resp message as Multicast on reception of multicast Delay_Req messages. | both| passed|passed |
|MHG_013 |Verify that the boundary clock terminates all multicast Pdelay_Resp messages received on the port. |both |passed |passed |
|MHG_014 |Verify that the boundary clock terminates all multicast Pdelay_Resp_Follow_Up messages received on the port. | both| passed|passed |
|MHG_015 |Verify that the boundary clock ignores the Pdelay_Req message received on the port from which it was issued. |both |passed |passed |
|MTG_001 | Verify that the boundary clock transmits Delay_Req message on receiving Sync/ Sync and Follow_Up based on clock step on its slave port.| both| passed|passed |
|MTG_002 |Verify that the boundary clock uses incremental sequence id for consecutive Announce messages. |both |passed | passed|
|MTG_003 |Verify that the boundary clock uses incremental sequence id for consecutive Sync messages. |both |passed | passed|
|MTG_004 |Verify that the boundary clock uses incremental sequence id for consecutive Delay_Req messages. |both |passed |passed|
|MTG_005 |Verify that the boundary clock port supporting Delay Request-Response mechanism acting as master has alternateMasterFlag set to FALSE in Announce,Sync, Follow_Up,Delay_Resp PTP messsages |both |passed | passed|
|MTG_006 |Verify that the boundary clock transmits Announce messages for every announce interval. | both| passed|passed |
| MTG_007| Verify that the boundary clock transmits Sync messages for every sync interval.|both |passed | passed|
|MTG_008 |Verify that the boundary clock transmits Delay_Resp message on receiving Delay_Req on its master port. |both |passed |passed |
|MTG_009 |Verify that the sequenceID and SourcePortIdentity field of received Follow_Up message shall match the sequenceId and SourcePortIdentity field of the prior Sync message respectively. |both |passed | passed|
|MTG_010 |Verify that the requestingSequenceId and requestingSourcePortIdentity field of Delay_Resp message shall match the sequenceId and SourcePortIdentity field of the associated Delay_Req message respectively. | both| passed| passed|
| MTG_012| Verify that the boundary clock transmits Pdelay_Resp/ Pdelay_Resp and Pdelay_Resp_Follow_up message on receiving Pdelay_Req on its master port.| both|passed | passed|
|MTG_013 |Verify that the sequenceId field, requestingSourcePortIdentity and domain number of Pdelay_Resp message shall match the sequenceId,SourcePortIdentity and domain number field of the associated Pdelay_Req message. |both |passed | passed|
|MTG_014 |Verify that the correctionField, sequenceId field, requestingSourcePortIdentity and domain number of Pdelay_Resp_Follow_Up message shall match the correctionField, sequenceId, SourcePortIdentity and domain number field respectively of the associated Pdelay_Req message. |both | passed| passed|
|MTG_015 | Verify that the boundary clock uses incremental sequence id for consecutive PDelay_Req messages.|both |passed | passed|
|MTG_016 |Verify that the boundary clock transmits Pdelay_Req messages for every pdelay_request interval. | both| failed| passed|
|MTG_017 |Verify that the boundary clock in multicast mode transmits Delay_Req message periodically at an interval between 0 and twice 2^portDS.logMinDelayReqInterval (where portDS.logMinDelayReqInterval is the logMessageInterval of last Delay_Resp message received). |both | passed|passed |
|PCG_001 | Verify that the boundary clock allows to configure PTP on multiple ports.|both |passed |passed |
| PCG_005|Verify that the boundary clock configured for multicast transmission in Master has the unicastFlag field as FALSE in Delay Request-Response |both |passed | passed|
|PCG_006 |Verify that the boundary clock configured for multicast transmission has the unicastFlag field as FALSE in Peer Delay messages. |both |passed | passed|
| PCG_009|Verify that the boundary clock configured for Two-Step clock has the twoStepFlag field as TRUE in Sync messages. | both| passed|passed |
| PCG_010| Verify that the boundary clock configured for Two-Step clock has the twoStepFlag field as TRUE in PDelay_Resp messages.|both | passed|passed |
| PCG_012| Verify that the boundary clock supports to configure priority2 to any value in range 0-255.|both | failed|passed |
|PCG_018 |Verify that the boundary clock configured for multicast transmission in Slave has the unicastFlag field as FALSE in Delay Request message. |both |passed |passed |
|SMG_002 |Verify that the boundary clock does not transmit any PTP messages on its port in DISABLED state. |both |passed |passed |
|SMG_003 |Verify that the boundary clock discards any PTP messages that are received on its port in DISABLED state. |both |passed |passed |
|SMG_004 |Verify that the boundary clock port in LISTENING state shall wait for the Announce receipt timeout to expire and transit to MASTER state. |both |passed |passed |
|SMG_005 |Verify that the boundary clock port in LISTENING state shall wait to receive an Announce message to transit to MASTER/ SLAVE state. |both |passed |passed |
|SMG_006 |Verify that the boundary clock port in MASTER state sends Announce messages periodically. |both |passed | passed|
| SMG_007|Verify that the boundary clock port in SLAVE state sends Delay_Req messages. |both | passed| passed|
| SMG_008| Verify that the boundary clock remains in SLAVE state if the same master continues|both |passed |passed |
|SMG_010 |Verify that the boundary clock in LISTENING state moves to the SLAVE state when the master clock is selected. | both|passed |passed |
|SMG_011 | Verify that the boundary clock in LISTENING state moves to DISABLED state when PTP is disabled at port.|both |passed |passed |
|SMG_013 |Verify that the boundary clock in SLAVE state moves to DISABLED state when PTP is disabled at port. |both | passed|passed |
|SMG_014 |Verify that the boundary clock in MASTER state moves to DISABLED state when PTP is disabled at port. | both| passed |passed |
|SMG_015 | Verify that the boundary clock in SLAVE state moves to FAULTY state when a fault is detected.|both |failed | passed|
|SMG_016 | Verify that the boundary clock in MASTER state moves to FAULTY state when a fault is detected.|both |failed |passed |
|SMG_018 |Verify that the boundary clock in FAULTY state moves to DISABLED state when PTP is disabled at port. |both | aborted | passed|
|SMG_019 |Verify that the boundary clock in DISABLED state moves to the LISTENING state when PTP is enabled at port. |both |passed |passed |
## Test that do not pass because of known bugs (5 tests)
......@@ -109,10 +106,16 @@ The tests that we expect the WR Switch to pass are listed below. There is a numb
|PCG_016|Verify that the DUT transmits unicast sync/ sync and follow_up message with logMessageInterval field as 7F.|
|PCG_017|Verify that the boundary clock configured for unicast transmission in Slave has the unicastFlag field as TRUE in Delay Request message.|
|SMG_017|Verify that the boundary clock in FAULTY state moves to the LISTENING state when the fault is cleared.|
|||
|||
|||
|||
|||
|||
|||
## Historical data
| Firmware version | Test Mode | Test report | Date |Test cases | Passed | Failed | Aborted |
| :------: | ------ | :------: | :------: | :------: | :------: | :------: | :------: |
| v6.0-beta1-10-gb3b066a | 802.1 | [Report](uploads/fe6a254af0d0146342a5728c9fd91a70/TSR_BC_20200429.pdf) | 29-04-2020 | 87 | 65 | 5 | 17 (*) |
| v5.0-52-g2bfdf51 | 802.1 | [Report](uploads/1bb21df6b87f8ef537ad9d0cc8b6f45d/ATTEST-PTP-BC-Test-Results-UDP_IEEEmode.xls) | 5-12-2018 | 87 | 59 | 10 | 18 (*) |
| v5.0-52-g2bfdf51 | UDP | [Report](uploads/1bb21df6b87f8ef537ad9d0cc8b6f45d/ATTEST-PTP-BC-Test-Results-UDP_IEEEmode.xls) | 5-12-2018 | 87 | 59 | 10 | 18 (*) |
(*) NOTE: Abandoned test cases are designed for UDP or Unicast while the test was run with Raw Ethernet multicast.