Users Guide

Verifying Your Installation | Installing Distributed and HA Deployments
62 OMNM 6.5.3 Installation Guide
5 Disable the Mediation server on the appserver host by not configuring it during installation.
Otherwise, add the following property to the \owareapps\installprops\lib\installed.properties
file:
oware.appserver.mediation.setup=false
6 Configure autostarting in the owareapps/installprops/installed.properties file if you installed
autostarting. See
Startup Properties on page 74 for a list of potentially configurable
properties.
Verifying Your Installation
Once you complete the OpenManage Network Manager (OMNM), verify that the applications
starts. The following startup sequences is recommended for complex installations:
1 Start the database.
2 Start the config server (the primary Application server for a cluster).
3 Start the remaining Application servers.
4 Start the Mediation servers, one at a time.
5 Start the Web servers.
6 Start the Web client.
Once you have successfully completed the above with single servers, start the rest of the cluster of
Application servers. To test that each Mediation server works, start and stop them one at time.
Running discovery is a good test of connectivity.
Here are a few things to remember after installation while performing the following tasks.
Task Remember
Starting OMNM (After
installation)
Make sure that your database is running. MySQL installs automatically as a
service (daemon), Oracle must be started separately. Make sure that your
database connects to the Application server if it is on a separate host.
Start the Application server if you installed this software as a service and the
it is down.
Default OMNM login is admin, password admin.
Note: The first time you start the application after installation, you may
have to wait for the Application server to completely start. If the Application
server startup is not complete, portlets do not display when you start the
Web client.
Discovery (After startup) For a successful discovery after startup, make sure that the Application
server has connectivity to devices to discover using one of the following
methods:
• Ping the discovery target from the Application server host.
• Right-click a discovered device and then select Direct Access.
Backup/Restore/Deploy
(After device discovery)
Make sure that an external FTP/TFTP server or process is running and has
network access to the target devices.
Typically FTP/TFTP must be on the same side of firewalls as managed
devices. OMNM’s internal FTP/TFTP server is for testing only. If FTP and
TFTP are separate processes, configure them so they write to the same
directory.