ANTA catalog for System tests
Tests¶
VerifyAgentLogs ¶
Verifies there are no agent crash reports.
Expected Results
- Success: The test will pass if there is NO agent crash reported.
- Failure: The test will fail if any agent crashes are reported.
Examples
anta.tests.system:
- VerifyAgentLogs:
Source code in anta/tests/system.py
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 |
|
VerifyCPUUtilization ¶
Verifies whether the CPU utilization is below 75%.
Expected Results
- Success: The test will pass if the CPU utilization is below 75%.
- Failure: The test will fail if the CPU utilization is over 75%.
Examples
anta.tests.system:
- VerifyCPUUtilization:
Source code in anta/tests/system.py
170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 |
|
VerifyCoredump ¶
Verifies if there are core dump files in the /var/core directory.
Expected Results
- Success: The test will pass if there are NO core dump(s) in /var/core.
- Failure: The test will fail if there are core dump(s) in /var/core.
Notes
- This test will NOT check for minidump(s) generated by certain agents in /var/core/minidump.
Examples
anta.tests.system:
- VerifyCoredump:
Source code in anta/tests/system.py
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 136 |
|
VerifyFileSystemUtilization ¶
Verifies that no partition is utilizing more than 75% of its disk space.
Expected Results
- Success: The test will pass if all partitions are using less than 75% of its disk space.
- Failure: The test will fail if any partitions are using more than 75% of its disk space.
Examples
anta.tests.system:
- VerifyFileSystemUtilization:
Source code in anta/tests/system.py
230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 |
|
VerifyMemoryUtilization ¶
Verifies whether the memory utilization is below 75%.
Expected Results
- Success: The test will pass if the memory utilization is below 75%.
- Failure: The test will fail if the memory utilization is over 75%.
Examples
anta.tests.system:
- VerifyMemoryUtilization:
Source code in anta/tests/system.py
200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 |
|
VerifyNTP ¶
Verifies that the Network Time Protocol (NTP) is synchronized.
Expected Results
- Success: The test will pass if the NTP is synchronised.
- Failure: The test will fail if the NTP is NOT synchronised.
Examples
anta.tests.system:
- VerifyNTP:
Source code in anta/tests/system.py
259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 |
|
VerifyNTPAssociations ¶
Verifies the Network Time Protocol (NTP) associations.
Expected Results
- Success: The test will pass if the Primary NTP server (marked as preferred) has the condition ‘sys.peer’ and all other NTP servers have the condition ‘candidate’.
- Failure: The test will fail if the Primary NTP server (marked as preferred) does not have the condition ‘sys.peer’ or if any other NTP server does not have the condition ‘candidate’.
Examples
anta.tests.system:
- VerifyNTPAssociations:
ntp_servers:
- server_address: 1.1.1.1
preferred: True
stratum: 1
- server_address: 2.2.2.2
stratum: 2
- server_address: 3.3.3.3
stratum: 2
Source code in anta/tests/system.py
290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 |
|
VerifyReloadCause ¶
Verifies the last reload cause of the device.
Expected Results
- Success: The test will pass if there are NO reload causes or if the last reload was caused by the user or after an FPGA upgrade.
- Failure: The test will fail if the last reload was NOT caused by the user or after an FPGA upgrade.
- Error: The test will report an error if the reload cause is NOT available.
Examples
anta.tests.system:
- VerifyReloadCause:
Source code in anta/tests/system.py
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 97 98 99 |
|
VerifyUptime ¶
Verifies if the device uptime is higher than the provided minimum uptime value.
Expected Results
- Success: The test will pass if the device uptime is higher than the provided value.
- Failure: The test will fail if the device uptime is lower than the provided value.
Examples
anta.tests.system:
- VerifyUptime:
minimum: 86400
Inputs¶
Name | Type | Description | Default |
---|---|---|---|
minimum |
PositiveInteger
|
Minimum uptime in seconds.
|
- |
Source code in anta/tests/system.py
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 53 54 55 56 57 58 59 60 |
|
Input models¶
NTPServer ¶
Model for a NTP server.
Name | Type | Description | Default |
---|---|---|---|
server_address |
Hostname | IPv4Address
|
The NTP server address as an IPv4 address or hostname. The NTP server name defined in the running configuration
of the device may change during DNS resolution, which is not handled in ANTA. Please provide the DNS-resolved server name.
For example, 'ntp.example.com' in the configuration might resolve to 'ntp3.example.com' in the device output.
|
- |
preferred |
bool
|
Optional preferred for NTP server. If not provided, it defaults to `False`.
|
False
|
stratum |
int
|
NTP stratum level (0 to 15) where 0 is the reference clock and 16 indicates unsynchronized.
Values should be between 0 and 15 for valid synchronization and 16 represents an out-of-sync state.
|
Field(ge=0, le=16)
|
Source code in anta/input_models/system.py
15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 |
|