Managing FTDv nodes#
Containers with Cisco FTDv inside will take ~1-2 min to fully boot.
You can monitor the progress with
docker logs -f <container-name>.
Cisco FTDv node launched with containerlab can be managed via the following interfaces:
serial port (console) is exposed over TCP port 5000:
telnet localhost 5000 if telnet is not available on your container host.
HTTPS server is running over port 443 -- connect with any browser normally.
Default user credentials:
eth0- management interface (Management0/0) connected to the containerlab management network
eth1+- first and subsequent data interfaces (GigabitEthernet0/0, GigabitEthernet0/1, etc.)
When containerlab launches FTDv node, it will assign IPv4/6 address to the
eth0 interface. These addresses are used to reach the management plane of the router.
eth1+ need to be configured with IP addressing manually using Web UI.
Features and options#
Cisco FTDv nodes come up with a basic configuration where only the management interface and a default user are provisioned.
Nodes are configured for local management with Firepower Device Management (FDM) On-Box management service. FDM is available via HTTPS and takes a few minutes to come up after node boot up.
The following simple lab consists of two Linux hosts connected via one FTDv node: