Objectives
The simulator ticks each one as soon as the network meets it.
Devices › Device Management › FTD1 › Device › Management: Turn Management off, then Send. The manager stops talking to FTD1, and FTD1 stays registered.
Still on the Device tab: Edit Remote Host Address: 10.0.0.12, Apply, Send. (It can be edited only while Management is off.)
On FTD1’s console: configure network ipv4 manual 10.0.0.12 255.255.255.0. A managed firewall has no screen for its own address.
Turn Management on, then Send. Connection Status says Connected, and on FTD1 sftunnel-status-brief says the peer is connected.
Before you start
If the manager’s own address changes too, the firewall must be told: show managers gives the identifier, and configure manager edit hostname updates it (Management Center Administration Guide). The console under FTD Manager takes the same lines: device management FTD1 off, device host FTD1 10.0.0.12, device management FTD1 on.
Concept
The screens and the console do the same thing
A manager’s screens are forms that produce configuration lines. Here every screen shows those lines before it sends them, and the console takes the same lines, so either way gives the same result. A managed firewall’s own management address and manager stay on its console, because the manager reaches it through them.
Concept
A managed firewall takes its policy from a manager
An FTD-style firewall has a console for showing and testing, and it refuses configuration. Its policy lives on a manager and arrives by deployment. Before that, the two must register over a separate management network: each needs an address, the firewall names its manager and a key, and the manager adds the device with the same key.
