Events (Connection, Intrusion/IPS, File, SSL and so on).This list contains most of the information that is carried through the sftunnel: What Information is Exchanged Through the sftunnel? The reason is an FTD data-plane issue can disrupt the communication between FTD and FMC. Note: The sftunnel can also go through the FTD itself. Once the registration is done the FTD and the FMC establish a secure tunnel called sftunnel (the name derives from the Sourcefire tunnel).įrom a design point of view the FTD – FMC can be in the same 元 subnet: In the case of remote management the FTD needs first to register to the FMC that uses a process known as device registration. On-box via Firepower Device Manager (FDM) and/or Cisco Defense Orchestrator (CDO) – also known as local management.
Off-box via FMC - also known as remote management.If your network is live, ensure that you understand the potential impact of any command. All of the devices used in this document started with a cleared (default) configuration. The information in this document was created from the devices in a specific lab environment. The information in this document is based on these software and hardware versions: There are no specific requirements for this document. The information and the examples are based on FTD, but most of the concepts are also fully applicable to NGIPS (7000/8000 series appliances) or a FirePOWER module on ASA55xx. This document describes the operation, verification, and troubleshoot procedures of the connection (sftunnel) between a managed Firepower Threat Defense (FTD) and the managed Firepower Management Center (FMC).
0 kommentar(er)
