The type and size of the data Teleseer ingests contributes greatly to the topology generated by the application. For best results, provide both router/switch configurations and PCAP data. Projects containing only bro/zeek log data will not produce an ideal topology.

Routers and switches

Teleseer ingests a variety of router and switch configurations. For best results, ingest the output of the command that shows the device's running configuration (e.g. in Cisco OS, show running-config)

Supported router and switch configurations include Cisco IOS, Juniper JunOS, Fortinet FortiOS, Palo Alto PAN-OS, and others. See Supported file types for the full list.

PCAP data

For a complete picture of the network, collect PCAP data. There is no file size limit; however, the time needed to process the data scales with the volume of telemetry and is affected by network and file system constraints. Splitting large files (e.g. via tcpdump / editcap / splitcap) is recommended where such constraints prohibit effective telemetry processing.

When tapping the network, provide as much network context as possible:

• Include Layer 2 data for the richest topology.
• Include VLAN tags where possible for accurate VLAN grouping in the topology.
• Do not archive files before uploading. Compressed archives may negatively affect the Teleseer carving tool.

Note: Cooked PCAPs (SLL/any-device captures) are not currently supported.

‍