FTDv shows "No route to host"

CarsonDavis56998 · ‎01-07-2025

After deploying a new FTDv 7.x, I encountered an issue where, after configuring the Management IP settings (including Device IP, Gateway, and Mask), I couldn’t ping any devices on the network. I received a "No Route to Host" error, which was puzzling since the Management IP is on the same Layer 2 network as the device I was trying to ping. When I switched the management interface to use DHCP, I successfully obtained DHCP IP settings. This confirmed that the VLAN in VMware was correctly assigned to the vNIC. However, even with the DHCP settings, which included the default gateway, I still couldn’t ping anything—not even the default gateway—indicating that there was still no route to the host. I've also noted that the IP was assigned to "eth0" instead of "Management0/0," and I’m unsure if that’s the source of the issue. Unfortunately, I haven’t found a command that allows me to assign an IP to Management0/0, which I suspect is the intended egress interface for management access.

Rob Ingram · ‎01-07-2025

@CarsonDavis56998 when pinging from the management interface you need to use "ping system <ip address>".

MHM Cisco World · ‎01-07-2025

>configure network static-routes

Try this command to add defualt route for mgmt

MHM

chucksharp1 · ‎11-26-2025

Having an issue with the configure network static-routes. I run a show interface, which provides all the names of the interfaces, and none of them will work.

Example: configure network static-routes ipv4 add diagnostic 0.0.0.0 0.0.0.0 x.x.x.x

Results in "Error: Interface supplied (diagnostic) is either not yet configured or does not exist."

or it results in "Error: Interface supplied (Management1/1) is not valid."

I've tried Mgmt, Management1/1, Ethernet1/1, outside, diagnostic.

Here's a show interface:

Interface Vlan1 "", is down, line protocol is down
Hardware is EtherSVI, BW 100 Mbps, DLY 100 usec
Available but not configured via nameif
Interface Ethernet1/1 "outside", is down, line protocol is down
Hardware is EtherSVI, BW 1000 Mbps, DLY 10 usec
MAC address 38fd.f82d.7f48, MTU 1500
IP address 50.211.187.101, subnet mask 255.255.255.248
Traffic Statistics for "outside":
0 packets input, 0 bytes
0 packets output, 0 bytes
0 packets dropped
1 minute input rate 0 pkts/sec, 0 bytes/sec
1 minute output rate 0 pkts/sec, 0 bytes/sec
1 minute drop rate, 0 pkts/sec
5 minute input rate 0 pkts/sec, 0 bytes/sec
5 minute output rate 0 pkts/sec, 0 bytes/sec
5 minute drop rate, 0 pkts/sec
Interface Ethernet1/2 "", is admin down, line protocol is down
Hardware is EtherSVI, BW 1000 Mbps, DLY 10 usec
Available but not configured via nameif
Interface Ethernet1/3 "", is admin down, line protocol is down
Hardware is EtherSVI, BW 1000 Mbps, DLY 10 usec
Available but not configured via nameif
Interface Ethernet1/4 "", is admin down, line protocol is down
Hardware is EtherSVI, BW 1000 Mbps, DLY 10 usec
Available but not configured via nameif
Interface Ethernet1/5 "", is admin down, line protocol is down
Hardware is EtherSVI, BW 1000 Mbps, DLY 10 usec
Available but not configured via nameif
Interface Ethernet1/6 "", is admin down, line protocol is down
Hardware is EtherSVI, BW 1000 Mbps, DLY 10 usec
Available but not configured via nameif
Interface Ethernet1/7 "", is admin down, line protocol is down
Hardware is EtherSVI, BW 1000 Mbps, DLY 10 usec
Available but not configured via nameif
Interface Ethernet1/8 "", is admin down, line protocol is down
Hardware is EtherSVI, BW 1000 Mbps, DLY 10 usec
Available but not configured via nameif
Interface Management1/1 "diagnostic", is up, line protocol is up
Hardware is en_vtun rev00, DLY 1000 usec
Input flow control is unsupported, output flow control is unsupported
MAC address 38fd.f82d.7f01, MTU 1500
IP address unassigned
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 pause input, 0 resume input
0 L2 decode drops, 0 demux drops
0 packets output, 0 bytes, 0 underruns
0 pause output, 0 resume output
0 output errors, 0 collisions, 0 interface resets
0 late collisions, 0 deferred
0 input reset drops, 0 output reset drops
input queue (blocks free curr/low): hardware (0/0)
output queue (blocks free curr/low): hardware (0/0)
Traffic Statistics for "diagnostic":
0 packets input, 0 bytes
0 packets output, 0 bytes
0 packets dropped
1 minute input rate 0 pkts/sec, 0 bytes/sec
1 minute output rate 0 pkts/sec, 0 bytes/sec
1 minute drop rate, 0 pkts/sec
5 minute input rate 0 pkts/sec, 0 bytes/sec
5 minute output rate 0 pkts/sec, 0 bytes/sec
5 minute drop rate, 0 pkts/sec
Management-only interface. Blocked 0 through-the-device packets

Any suggestions?

Rob Ingram · ‎11-26-2025

@chucksharp1 Are you trying to create the default route for data traffic? The CLI command you are attempting to use is for configuring a route for the management interface. You'd configure the default route for the data interfaces using the GUI (FMC/FDM), not via the CLI.

If you still have problems, I would suggest starting a new post.

chucksharp1 · ‎12-01-2025

Thank you for clarifying that. Seems like the route that I set via the GUI did not take when it last deployed. Since I was in the field and it couldn't communicate with FMC, I was looking for a way to change the data interface route.