Simulation Data Format Reference¶
Conventions¶
- Simulation data for profiles is contained in
.snmprecfiles located in the tests directory. - Simulation files must be named after the SNMP community string used in the profile unit tests. For example:
cisco-nexus.snmprec.
File contents¶
Each line in a .snmprec file corresponds to a value for an OID.
Lines must be formatted as follows:
<OID>|<type>|<value>
For the list of supported types, see the snmpsim simulation data file format documentation.
Warning
Due to a limitation of snmpsim, contents of .snmprec files must be sorted in lexicographic order.
Use $ sort -V /path/to/profile.snmprec to sort lines from the terminal.
Symbols¶
For symbol metrics, add a single line corresponding to the symbol OID. For example:
1.3.6.1.4.1.232.6.2.8.1.0|2|1051200
Tables¶
Tip
Adding simulation data for tables can be particularly tedious. This section documents the manual process, but automatic generation is possible — see How to generate table simulation data.
For table metrics, add one copy of the metric per row, appending the index to the OID.
For example, to simulate 3 rows in the table 1.3.6.1.4.1.6.13 that has OIDs 1.3.6.1.4.1.6.13.1.6 and 1.3.6.1.4.1.6.13.1.8, you could write:
1.3.6.1.4.1.6.13.1.6.0|2|1051200
1.3.6.1.4.1.6.13.1.6.1|2|1446
1.3.6.1.4.1.6.13.1.6.2|2|23
1.3.6.1.4.1.6.13.1.8.0|2|165
1.3.6.1.4.1.6.13.1.8.1|2|976
1.3.6.1.4.1.6.13.1.8.2|2|0
Note
If the table uses table metric tags, you may need to add additional OID simulation data for those tags.