Enterprise Manager: Installation Requirements and a Checklist for Configuring and Testing Network Connections between EM Component Hosts (Doc ID 428665.1)

In this Document

Applies to:

Enterprise Manager Base Platform - Version 10.2.0.1 to 12.1.0.2.0 [Release 10.2 to 12.1]
Information in this document applies to any platform.

Purpose

 This article provides a set of tests that can be used to verify connectivity between the OMS and an Agent to ensure a correct installation and consistency of using the Grid Control Components.

Note the follwoing from RFC-952 concerning host name formatting standards:

A name (Net, Host, Gateway, or Domain name) is a text string up to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus sign (-), and period (.). Note that periods are only allowed when they serve to delimit components of domain style names. No blank or space characters are permitted as part of a name. No distinction is made between upper and lower case. The first character must be an alpha character.

Details

Network Configuration and Connectivity Tests

The installation or target host must resolve to a unique host name and a static IP address that are visible to other hosts in the network.

This set of tests can be used to verify connectivity between the OMS host and an intended Agent host to ensure a correct installation and consistency of using the Grid Control Components.

 
Both the OMS and the Agent need to use the full canonical name of the hosting computer, used with a type of double-lookup/reverse-lookup to get the fully qualified domain name (FQDN).

The purpose of the tests described below is to verify connectivity between server and client (agent or console) processes.  Consult a Network Administrator for more details.

A) Check /etc/nsswitch.conf to see how lookups are to be performed by the Operating System.

B) All systems involving a HOSTS file must be setup like this:

The file should have the OMS and Agent servers' IP address followed by the fully qualified hostname.domain name, and then a short hostname or alias.
For Example:
hosts

10.10.10.10 OMSMACHINE.DOMAIN   OMSMACHINE 
20.20.20.20 AGENTMACHINE.DOMAIN AGENTMACHINE 

If the OMS and Agent are on the same machine, it is acceptable to have just the one IP/Hostname listed.
This example shows two because separate machines are involved.

Tests to run:
1) On the OMS Machine
Use the HOSTNAME command to verify the servers hostname
Use the IPCONFIG (Windows) or IFCONFIG (Unix) command to verify the servers IP address.

>hostname 
OMSMACHINE.DOMAIN 

>ifconfig -a 
10.10.10.10 

Test itself 
>ping 10.10.10.10 
>ping OMSMACHINE.DOMAIN 
>ping OMSMACHINE 
>nslookup 10.10.10.10 
>nslookup OMSMACHINE.DOMAIN 
>nslookup OMSMACHINE 

Test the remote agent 
>ping 20.20.20.20 
>ping AGENTMACHINE.DOMAIN 
>ping AGENTMACHINE 
>nslookup 20.20.20.20 
>nslookup AGENTMACHINE.DOMAIN 
>nslookup AGENTMACHINE 

2) On the Agent Machine - Must have the same HOSTS file setup like the OMS

Use the HOSTNAME command to verify the servers hostname
Use the IPCONFIG (Windows) or IFCONFIG (Unix) command to verify the servers IP.

>hostname 
AGENTMACHINE.DOMAIN 

>ifconfig -a 
20.20.20.20 

Test itself 
>ping 20.20.20.20 
>ping AGENTMACHINE.DOMAIN 
>ping AGENTMACHINE 
>nslookup 20.20.20.20 
>nslookup AGENTMACHINE.DOMAIN 
>nslookup AGENTMACHINE 

Test the remote OMS 
>ping 10.10.10.10 
>ping OMSMACHINE.DOMAIN 
>ping OMSMACHINE 
>nslookup 10.10.10.10 
>nslookup OMSMACHINE.DOMAIN 
>nslookup OMSMACHINE 

3) On the Client Machine - If applicable
Test the remote OMS

>ping 10.10.10.10 
>ping OMSMACHINE.DOMAIN 
>ping OMSMACHINE 
>nslookup 10.10.10.10 
>nslookup OMSMACHINE.DOMAIN 
>nslookup OMSMACHINE 

Test the remote Agent

>ping 20.20.20.20 
>ping AGENTMACHINE.DOMAIN 
>ping AGENTMACHINE 
>nslookup 20.20.20.20 
>nslookup AGENTMACHINE.DOMAIN 
>nslookup AGENTMACHINE 

4) These tests will benefit the installation of Grid Control if the responses provide self-consistent and unambiguous results.

Other Network Considerations

5) PING_PATH considerations

a) Using IPv6 with the OMS Host

Pushing an agent from an OMS using IPv6 to a target host which is not using IPv6, the following modifications must be made:

Navigate to:   .../Middleware/oms/oui/prov/resources/

Alter the following parameter in the ssPaths_.properties, sPaths.properties and Paths.properties files located there:

from:   PING_PATH=/bin/ping

to:   PING_PATH=/bin/ping6

b) When ping is disabled on a firewall

If there is a firewall intervening between the OMS host and an intended agent host, which is configured not to allow ping traffic, the following modifications must be made:

Navigate to:   .../Middleware/oms/oui/prov/resources/

For Linux platforms, alter sPaths.properties and for other platforms, alter ssPaths_.properties as follows:

from:   PING_PATH=/bin/ping

to:   PING_PATH=/bin/true

6) Proximity Requirements

Ensure that the host on which the OMS is being installed and the host on which the Management Repository is being configured are located in close proximity to each other. Ideally, the round trip network latency between the two should be less than 1 millisecond.

7) Port Requirements

Ensure that the ports you assign (within the given range) to the following components are free and available:

OMS:

Admin Server HTTP SSL Port = 7101 - 7200
Enterprise Manager Upload HTTP Port = 4889 - 4898
Enterprise Manager Upload HTTP SSL Port = 1159, 4899 - 4908
Enterprise Manager Central Console HTTP Port = 7788 - 7798
Enterprise Manager Central Console HTTP SSL Port = 7799 - 7809

Agent:

Oracle Management Agent Port = 3872, 1830 - 1849

To verify if a port is free, run the following command:

On Unix:
netstat -anp | grep

On Microsoft Windows:
netstat -an|findstr

Note that the port ranges of interest shown above are the default values. The actual specific port values of interest are available from the related OMS installer page, the record of port assignment located in the .../gc_inst/em/EMGC_OMS1/emgc.properties file (provided the ports have not been reassigned since installation), or, if custom port value assignments will be determined by use of the staticports.ini file,  the values recorded in the ...//response/staticports.ini file from the EM 12c install stage.

8) Firewalls

See the following reference for a complete description of firewall considerations when planning and installing the Enterprise Manager 12dc monitoring components:

Oracle(R) Enterprise Manager Cloud Control Advanced Installation and Configuration Guide
12c Release 1 (12.1.0.1)
Part Number E24089-15
12 Configuring Enterprise Manager for Firewalls

URL:

http://docs.oracle.com/cd/E24628_01/install.121/e24089/firewalls.htm#BABIGHDH

References

NOTE:141955.1 - How to Perform Forward and Reverse Domain Name Service (DNS) Hostname Resolution
NOTE:330072.1 - How To Configure Enterprise Manager for High Availability
NOTE:339425.1 - Emca Utility Does Not Use Server Name, Rather Ip Address
NOTE:398981.1 - Does OAS or OHS 10g Support Having an Underscore in a Hostname?

Related …

Products …

• Enterprise Management > Enterprise Manager Products > Enterprise Manager > Enterprise Manager Base Platform > OMS Install > Prerequisites

Keywords …

ADDRESS;AGENT PING;CONTROL;ENTERPRISE MANAGER;GRID CONTROL;IP ADDRESS;LOOKUPS;OMS;SHORT

來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/17252115/viewspace-1246499/，如需轉載，請註明出處，否則將追究法律責任。