Skip to content

Latest commit

 

History

History
155 lines (115 loc) · 6.83 KB

configuration.md

File metadata and controls

155 lines (115 loc) · 6.83 KB
Raw

Configuration File

By default the network importer will try to load a configuration file name network_importer.toml, this configuration file is not mandatory as long as the required information to connect to the SOT, Batfish and/or the network devices are provided via environment variables.

It's possible to specify which configuration file should be used in cli with the option --config.

The configuration file is organized in 7 sections detailed below.

Main Section

The main section included the main parameters to define what will be imported from the network and/or the SOT, where the configuration files are available/should be stored and how many number of tasks can be executed in parallel.

[main]
import_ips = true 
import_prefixes = false
import_intf_status = false

# Vlans (name, vlan-id) can be imported from the configuration, from the CLI or both 
# - "config" will import the vlans just from the configuration
# - "cli" will import the vlans from the cli using the action `get_vlans`
# - "true" will import vlans from both cli and config
# - no or false will not import any vlans
# The association between interface and vlans will always be derived from the configuration.
import_vlans = "config"         # Valid options are ["cli", "config", "no", true, false]

# Cabling can be imported from LLDP, CDP or the configuration (for some point to point links)
# - "lldp" or "cdp" will import the vlans from the cli using the action `get_neighbors`
# - "config" will import the neighbors from the configuration (for point to point links)
# - "true" will import neighbors from both cli and config 
# - no or false will not import any neighbors
import_cabling = "lldp"         # Valid options are ["lldp", "cdp", "config", "no", true, false]
excluded_platforms_cabling = ["cisco_asa"]

# Number of Nornir tasks to execute at the same time
nbr_workers = 25

# Directory where the configuration can be find, organized in Batfish format
configs_directory = "configs"

# Valid Backend
# Only Netbox and Nautobot backend are included by default, if you want to use another backend
# you must leave backend empty and define inventory.inventory_class and adapters.sot_class manually.
backend = "nautobot"

Inventory Section

The [inventory] section regroup all parameters related to the inventory and also includes an optional list of supported platforms. network-importer supports multiple inventories, you can define your own inventory by defining inventory_class and each inventory can define its own list of settings which will need to be configured under [inventory.settings]. The settings for the nautobot inventory and for the netbox inventory are available in their respective documentation.

[inventory]

# Define a list of supported platform, 
# if defined all devices without platform or with a different platforms will be removed from the inventory
supported_platforms = [ "cisco_ios", "cisco_nxos" ]

# Configure which Inventory will be loaded by the network importer.
backend = "nautobot"

[inventory.settings]
# Inventory specific settings, please refer to the documentation of each backend/inventory.

Batfish Section

The [batfish] section regroup all parameters to connect to Batfish.

[batfish]
address = "localhost"               # Alternative Env Variable : BATFISH_ADDRESS
api_key = "XXXX"                    # Alternative Env Variable : BATFISH_API_KEY
network_name = "network-importer"   # Alternative Env Variable : BATFISH_NETWORK_NAME
snapshot_name = "latest"            # Alternative Env Variable : BATFISH_SNAPSHOT_NAME
port_v1 = 9997                      # Alternative Env Variable : BATFISH_PORT_V1
port_v2 = 9996                      # Alternative Env Variable : BATFISH_PORT_V2
use_ssl = false                     # Alternative Env Variable : BATFISH_USE_SSL

Network Section

To be able to pull live information from the devices, the credential information needs to be provided either in the configuration file or as environment variables.

It's also possible to define some connection parameters for Netmiko and define a list of expected FDQNs that can be found in the network.

[network]
login = "username"          # Alternative Env Variable : NETWORK_DEVICE_LOGIN
password = "password"       # Alternative Env Variable : NETWORK_DEVICE_PWD
enable = true               # Alternative Env Variable : NETWORK_DEVICE_ENABLE

# List of valid FQDN that can be found in the network,
# The FQDNs in this list will be automatically removed from all neighbors discovered from LLDP/CDP
fqdns = [ ]

[network.netmiko_extras]
# Any additional parameters for Netmiko defined in this section will be automatically configured 
# as part of the Nornir inventory.

[network.napalm_extras]
# Any additional parameters for Napalm defined in this section will be automatically configured 
# as part of the Nornir inventory.

Drivers Section

Configure which driver to use for a given platform. Please see the extensibility section of the documentation for more details on how to create your own driver.

[drivers.mapping]
default = "network_importer.drivers.default"
cisco_nxos = "network_importer.drivers.cisco_default"
cisco_ios = "network_importer.drivers.cisco_default"
cisco_xr = "network_importer.drivers.cisco_default"
juniper_junos = "network_importer.drivers.juniper_junos"
arista_eos = "network_importer.drivers.arista_eos"

Logs Section

Control how the application is generating logs.

[logs]
# Control the level of the logs printed to the console.
level = "info"        # "debug", "info", "warning"

# For each run, a performance log can be generated to capture how long
# some functions took to execute
performance_log = false
performance_log_directory = "performance_logs"