My Oracle Support Banner

Grid / Cloud Agent Configuration: How to Configure the Agent to Listen to Only One Specific Network Interface Card (NIC)? (Doc ID 390444.1)

Last updated on NOVEMBER 16, 2022

Applies to:

Enterprise Manager Base Platform - Version 10.1.0.2 to 13.3.0.0.0 [Release 10.1 to 13c]
Information in this document applies to any platform.

Goal

The machine where the Grid / Cloud Agent is installed on, could have multiple Network Interface Cards (NIC) and it is necessary for the Agent traffic to be configured only on one particular NIC. This document provides the steps for configuring the Grid / Cloud Agent to listen to only one specific NIC.

This needs to be done for Agent on each package/cluster resource if working in an OS cluster configuration. By default, the Agent is allowed to use all local NIC/IP addresses to be used for incoming requests. This can be verified from:

$ netstat -pan | grep <Agent_Port>

For example:

10g/11g Agent would have:

$ netstat -pan | grep 3872
tcp    0   0       0.0.0.0:3872            0.0.0.0:*             LISTEN              2851/emagent

A 12c agent would have:

tcp   0   0        0.0.0.0:3872          0.0.0.0:*              LISTEN              7219/java

 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.