ANTA catalog for PTP tests
Module related to PTP tests.
VerifyPtpGMStatus ¶
Verifies that the device is locked to a valid PTP Grandmaster.
To test PTP failover, re-run the test with a secondary GMID configured.
Expected Results
- Success: The test will pass if the device is locked to the provided Grandmaster.
- Failure: The test will fail if the device is not locked to the provided Grandmaster.
- Skipped: The test will be skipped if PTP is not configured on the device.
Examples
anta.tests.ptp:
- VerifyPtpGMStatus:
gmid: 0xec:46:70:ff:fe:00:ff:a9
Inputs¶
Name | Type | Description | Default |
---|---|---|---|
gmid |
str
|
Identifier of the Grandmaster to which the device should be locked.
|
- |
Source code in anta/tests/ptp.py
55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 |
|
VerifyPtpLockStatus ¶
Verifies that the device was locked to the upstream PTP GM in the last minute.
Expected Results
- Success: The test will pass if the device was locked to the upstream GM in the last minute.
- Failure: The test will fail if the device was not locked to the upstream GM in the last minute.
- Skipped: The test will be skipped if PTP is not configured on the device.
Examples
anta.tests.ptp:
- VerifyPtpLockStatus:
Source code in anta/tests/ptp.py
99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 |
|
VerifyPtpModeStatus ¶
Verifies that the device is configured as a PTP Boundary Clock.
Expected Results
- Success: The test will pass if the device is a BC.
- Failure: The test will fail if the device is not a BC.
- Skipped: The test will be skipped if PTP is not configured on the device.
Examples
anta.tests.ptp:
- VerifyPtpModeStatus:
Source code in anta/tests/ptp.py
19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 |
|
VerifyPtpOffset ¶
Verifies that the PTP timing offset is within ± 1000ns from the master clock.
Expected Results
- Success: The test will pass if the PTP timing offset is within ± 1000ns from the master clock.
- Failure: The test will fail if the PTP timing offset is greater than ± 1000ns from the master clock.
- Skipped: The test will be skipped if PTP is not configured on the device.
Examples
anta.tests.ptp:
- VerifyPtpOffset:
Source code in anta/tests/ptp.py
138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 |
|
VerifyPtpPortModeStatus ¶
Verifies the PTP interfaces state.
The interfaces can be in one of the following state: Master, Slave, Passive, or Disabled.
Expected Results
- Success: The test will pass if all PTP enabled interfaces are in a valid state.
- Failure: The test will fail if there are no PTP enabled interfaces or if some interfaces are not in a valid state.
Examples
anta.tests.ptp:
- VerifyPtpPortModeStatus:
Source code in anta/tests/ptp.py
178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 |
|