Installation guide

108
Chapter 11 Installing the Engine on Other Platforms
• 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 you are unsure about the password.
• If there is a firewall between the engine and the Management Server or Log Server, make
sure that the firewall’s policy allows the initial contact and the subsequent communications.
See Default Communication Ports (page 149) for a list of the ports and protocols used.
If the initial management contact fails for some reason, the configuration can be started again
with the
sg-reconfigure command.
After Successful Management Server Contact
The initial configuration does not contain any working IPS or Layer 2 Firewall policy. You must
install a policy on the engine using the Management Client to make it operational. After you see
a notification that Management Server contact has succeeded, the IPS or Layer 2 Firewall
engine installation is complete and the engine is ready to receive a policy. The engine element’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.
Installing the Engine in Expert Mode
To start the installation, reboot from the DVD. See Installing the Engine on Intel-Compatible
Platforms (page 98).
The difference between the normal and expert installation is that in expert mode, you partition
the hard disk manually. If you are unfamiliar with partitioning hard disks in Linux, we recommend
that you use the normal installation process.
What’s Next?
 Continue as explained in After Successful Management Server Contact (page 108).
What’s Next?
 To finish the engine configuration, proceed to Configuring Routing and Installing Policies
(page 89).
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.