... | ... | @@ -36,7 +36,7 @@ The tests that we expect the WR Switch to pass are listed below. There is a numb |
|
|
|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. |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_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 |
|
... | ... | @@ -63,14 +63,14 @@ The tests that we expect the WR Switch to pass are listed below. There is a numb |
|
|
|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_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_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 |
|
... | ... | @@ -83,8 +83,8 @@ The tests that we expect the WR Switch to pass are listed below. There is a numb |
|
|
|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_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 |
|
|
|
|
... | ... | |