Owners Manual
General Information | Getting Started
58 OMNM 6.5.2 User Guide
NOTE:
Apple products are mostly OpenManage Network Manager-friendly. Android is only partly supported.
CAUTION:
If your application server and client are on different machines, make sure that they have the same time
settings.
Network Basics
The OpenManage Network Manager (OMNM) application communicates with devices over a
network. You must be connected to a network for the Application server to start successfully.
Firewalls, or programs using the same ports on the same machine where this application is installed
can interfere with its ability to communicate with devices.
Your network may have barriers to communication with this software that are outside the scope of
these instructions. Consult with your network administrator to ensure this application has access to
the devices you want to manage with the
protocols
described below.
NOTE:
One simple way to check connectivity with a device is to open a command shell with Start > Run
cmd
.
Then, type
pin
g
[device IP address]
at the command line. If the device responds, it is connected
to the network. If not, consult your network administrator to correct this. No useful information comes
from disconnected devices.
Consider Description
Name Resolution
(equipment)
The OMNM application requires resolution of equipment names, whether by
host files or domain name system (DNS).
If your network does not have a DNS, you can also assign hostnames in the
following file on a Windows system:
%windir%\system32\drivers\etc\hosts
You must assign a hostname in addition to an IP address in that file. Here are
some example hosts file contents (including two commented lines where you
would have to remove the # sign to make them effective):
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
Caution: This software only supports installation to a local file system. Do not
install to shared drives.
Protocols The OMNM application uses the following protocols:
• TCP/IP
• SNMP
• HTTP
• UDP Multicast
You can bypass multicast, if it is disabled on your network. To allow a client to
connect without multicast, add the following property to the client’s owareapps/
installprops/lib/installed.properties file.
oware.application.servers[Host1 IP address], [Host2 IP
address]...