Initial Configuration
23
3.
(
Optional
) Fill in the Key fingerprint (also shown when you saved the
initial configuration). Filling it in increases the security of the
communications.
4.
Highlight
Finish
and press E
NTER
.
The engine now tries to make initial Management Server contact.
• If you see a “connection refused” error message, ensure that the
one-time password is correct and the Management Server IP address
is reachable from the node. Save a new initial configuration if unsure
about the password.
• If the engine is unable to contact the Management Server, make sure
there are no networking problems, that all information defined in the
Firewall element corresponds to what you entered in the configuration
wizard and, if NAT is in use, that you have configured contact
addresses for NAT as explained in the
Firewall/VPN Installation Guide
.
After Successful Management Server Contact
After you see a notification that Management Server contact has
succeeded or the appliance has rebooted itself after automatic
configuration with a USB stick, the firewall engine installation is
complete and the firewall is ready to receive a policy. In a while, the
firewall’s status changes in the Management Client from
Unknown
to
No
Policy Installed
, and the connection state is
Connected
indicating that
the Management Server can connect to the node.
The next step is creating a security policy and installing it on the engine.
See the
Online Help
of the Management Client for detailed instructions.
Note –
Once initial contact has been made, the engine receives a
certificate from the Management Center for identification. If the
certificate is deleted or expires, you must repeat the initial contact
using a new one-time password.
Caution –
When using the command prompt, use the
reboot
command to reboot and
halt
command to shut down the node. Do
not use the
init
command. You can also reboot the node using the
Management Client.