Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sonic: Document packaging format #800

Merged
merged 2 commits into from
Dec 28, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/source/formats.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@ Batfish supports the following vendors. Click on the corresponding link to learn
* [Fortinet](#fortinet)
* [Juniper](#juniper)
* [Palo Alto Networks](#palo-alto-networks)
* [SONiC](#sonic)

Except for AWS, all vendor configs files must be placed in the `configs` folder right below the top-level snapshot folder. It is OK to create sub-folders inside `configs`; Batfish will recursively read all files. It is also OK to mix files from multiple vendors in the same folder.

Expand Down Expand Up @@ -212,6 +213,9 @@ show config merged
The first two commands may not be available on all PAN-OS versions;
just make sure that the output is NOT in XML format (first command) and that definitions are not truncated (second command).

### SONiC

Configuration files for SONiC devices should be placed under a folder called `sonic_configs` right under the top-level snapshot folder. For each SONiC device in the network, create a folder under the `sonic_configs` folder, and put its configdb.json and frr.conf files in that folder. The names of the device's folder and the two files is not important, but the device's files must appear together and by themselves in the folder.

## Supplemental data formats

Expand Down