A device for which a configuration file was successfully imported will be represented with one of the 5 following icons:
- A Firewall icon (orange brickwall) if access control lists were found, but no route information was found in the configuration,
- A Router icon (blue tower) if access control lists were not found, but route information was found in the configuration,
- A Firewall-router icon (orange brickwall with tiny blue tower in the bottom right corner) if access control lists and routers were found in the configuration, but the device is mostly used as a router,
- A Router-firewall icon (blue tower with tiny orange brickwall in the bottom right corner) if access control lists and routers were found in the configuration, but the device is mostly used as a firewall,
- A Switch icon for layer-2 devices.
Elements in the Topology
- All devices whose configurations are part of the model are shown.
- All real networks (and their hosts) faced by network device interfaces are shown.
- A gateway (generic gray device) represents the endpoint of a tunnel or route statement when the IP address of the endpoint is not otherwise represented anywhere in the model configurations.
- A subnetwork is visual and is attached to a larger visible network if there is a path from the subnetwork to a device that explicitly references it.
- A visible host is attached to a visible network if the network is the smallest among all visible networks that contain the host's IP address.
- A host or network entity is a peer of a gateway when the entity is not visible according to rules 4 or 5, and some or all of the entity's IP addresses are routed from some device to the IP address associated with the gateway.
- A VLAN is displayed as a peer with the name
vlan_nat a device if that device has an interface to a VLAN declared with identifier
- All other hosts and networks are associated with the Unmapped cloud.
The following changes can be manually made to the topology map:
- Adding layer 2 connections between network interfaces
- Setting hosts as dual-homed
- Attaching unmapped hosts to gateways
Those operations are available through the Custom Change button in the Map toolbar, or by right-clicking on a host in the map and then going to the Connect menu.
Here are the instructions to use the right-click connect menu:
- To add a layer 2 connection, please select 2 devices at once using the SHIFT key and then right-click on one of them and go to the Connect menu.. A device is defined as a firewall, a router, a switch, or a gateway.
- To create a dual-homed host, please select 2 hosts (gray circles) at once using the SHIFT key and then right-click on one of them and go to the Connect menu.
- To attach an unmapped host to a gateway, please right-click on an unmapped host in the unmapped cloud (top left corner of the map) and then go to the Connect menu.
Once changes have been made, then need to be committed in order to update the backend network model engine. A Review button will appear at the top of the topology map to go through the review and commit dialog.