Skip to main content

How to work around the "Component <component name> has an overlapping protocol named <protocol> defined with IP address * using port(s) <port number(s)>" message when configuring Components for agentless monitoring


Technote (troubleshooting)


Problem(Abstract)

When setting up Components for agentless monitoring using the AMCE there is a restriction in the UI. You cannot assign a "*" (wildcard, meaning match anything) as the IP address with a given port number, and then use the same port number with a specific IP address in a different component.

Symptom

Error Title: "Duplicate Protocol", message: "Component <component name> has an overlapping protocol named <protocol> defined with IP address * using port(s) <port number(s)>"


Resolving the problem

There is a reasonably simple workaround that should be effective and manageable in most environments:

Instead of using "*" as the fallback option, try to find out at least the "Class A" IP number. I.e. the first number in the IP address, and make the IP Address "10.*" (substitute 10 for the number in use in that network). Then create another rule with the specific IP - E.g. "10.1.1.1".

For example:

and then:

Rate this page:

(0 users)Average rating

Copyright and trademark information

IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Rate this page:


(0 users)Average rating

Add comments

Document information

Tivoli Composite Application Manager for Transactions

ITCAM TRANSACT AMC 5724S79EU v710


Software version:
7.3


Operating system(s):
AIX, Linux, Solaris, Windows


Reference #:
1620535


Modified date:
2012-12-14

Translate my page

Content navigation