Ports to Open in Firewall for WebLogic (Doc ID 2556414.1)

Last updated on MAY 13, 2024

Applies to:

Goal

Need port range to open firewall rule  

You have the NMS Services LPAR and WebLogic LPAR on different subnets.

The NMS managed server couldn't be started and you see the below error in the WebLogic managed server log:
=============
Testing the following initial reference
NameService=corbaloc:iiop:1.2@<server>:17820/NameService
Testing corba name service port
Testing port NamingService
Resolving host: <server>
  Resolved to <server>/<IP address>
Testing socket on port 17820
  successful.
Attempting to narrow...
  successful.
Attempting to resolve InterSys_nmsadmin
  successful.
Testing port InterSys_nmsadmin
Resolving host: <server>
  Resolved to <server>/<IP address>
Testing socket on port 37750
com.splwg.oms.ejb.ConfigException: InterSys_nmsadmin is not listening on port 37,750 on <server>.  Verify that the correct port is configured
...
=============

You ran this command and get the intersysobject ports from the NMS Services LPAR:
>tao_nslist -ORBInitRef NameService=iioploc://<server>:17820/NameService
Naming Service:
---------------
+ intersysobject: Naming context
| + InterSys_nmsadmin: Object Reference
| |   Protocol: IIOP
| |   Endpoint: <server>:37750
| + InterSys_nmsadminPublisher: Object Reference
| |   Protocol: IIOP
| |   Endpoint: <server>:37749

=============

According to Solution #2 of Oracle Knowledge article "Corba.Comm_failure When Attempting to Access NMS Application (Doc ID 1318075.1)", you should open firewall rule for the ports used by the intersysobjects.

Question/request:
1) What is the port range used by the above intersysobjects?
2) Are the port ranges for these objects customizable?

Solution

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