Showing results for 
Search instead for 
Did you mean: 

SNMP monitoring of FTD through IPSec

Hi All,

I've deployed a FMC managed FTD at a remote office, where it's managed via OUTSIDE interface.

Usually with an ASA it's possible to query SNMP on the INSIDE interface through the IPSec.
This doesn't seems possible with the FTD. ICMP doesn't work either via the IPSec to INSIDE.

Any solution to this issue?



8 Replies 8

Cisco Employee
Cisco Employee

On ASA - If your VPN tunnel terminates on one interface, but you want to manage the ASA by accessing a different interface, you can identify that interface as a management-access interface. For example, if you enter the ASA from the outside interface, this feature lets you connect to the inside interface using ASDM, SSH, Telnet, or SNMP; or you can ping the inside interface when entering from the outside interface. Management access is available via the following VPN tunnel types: IPsec clients, IPsec site-to-site, and the AnyConnect SSL VPN client.

management-access management_interface

The management_interface specifies the name of the management interface that you want to access when entering the ASA from another interface.

We can use the same command on FTD, which can be deployed via FMC Flex Policy. An enhancement is already in place to introduce this on the FMC UI, 

Yes - this is exactly the option I'm missing on the FTD via FMC.

Just making sure, setting this option, will NOT change the interface where the FMC is managing the device?

With the Flexconfig added to the FTD via FMC, I got syslog from INSIDE and I'm able to access INSIDE via HTTPS (only for test)

SNMP and SSH on the other hand doesn't work despite of the limited configuration through the FMC.

Any suggests to what I might have overlooked, or is there some kind of limitation?

Have you doublechecked the NAT/route for the snmp host IP ? 

I assume that my NAT correct as syslog and http works to the device, otherwise I guess it wouldn't, right?

SNMP and SSH won't work, because they're implemented via nlp_int_tap interface. At least until Cisco re-architects this part of the code. Refer to this post:

ASA code has the same issue for SNMP (but not for SSH) as of 9.14, with the same root cause.

The status of the corresponding ENH is incorrect: This bug wasn't fixed in the versions listed.



can you draw the topology ?

The topology is quite simple
FMC (DC-LAN)|---"DC FIREWALL"--------@--------"REMOTE FTD"----|REMOTE-LAN
The NAT is configured like so...
nat (INSIDE,OUTSIDE) source static REMOTE-LAN REMOTE-LAN destination static DC-LAN DC-LAN no-proxy-arp route-lookup
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: