Highlighted
Super Contributor.. Super Contributor..
Super Contributor..
626 views

UCMDB Oracle or any Database Ports need for Discovery needs to be found in the appropriate files

The ports should be found using discovery not set as an input into a ucmdb xml file.

0 Likes
8 Replies
Highlighted
Trusted Contributor.
Trusted Contributor.

Re: UCMDB Oracle or any Database Ports need for Discovery needs to be found in the appropriate files

Hello there,

 

What I understood is that you are suggesting about the discovery ports and they should not set as an input in a xml file.

 

Here is a link to open an enhancement request : https://community.softwaregrp.com/t5/CMS-Idea-Exchange/idb-p/CMS_Idea

 

Consequently development team can check your idea and work on it.

 

Thanks.

 

 

This topic was escalated to Email Message on 12-01-2018 by Anonymous_User1.

0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: UCMDB Oracle or any Database Ports need for Discovery needs to be found in the appropriate files

Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: UCMDB Oracle or any Database Ports need for Discovery needs to be found in the appropriate files

If you find an open port on a remote machine then either you use a mapping file (what we use now) or you try to do an educated guess about what service is delivered via that port.

The second option is somehow done today by nmap to some degree with a relatively good accuracy. The side effect is that very few customers actually use nmap because in today's IT infrastructures it's considered a sniffing tool or a possible security problem.

 

Kind regards,
Bogdan Mureșan

EMEA Technical Success
0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: UCMDB Oracle or any Database Ports need for Discovery needs to be found in the appropriate files

Still, you got my vote on the idea.

Kind regards,
Bogdan Mureșan

EMEA Technical Success
0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: UCMDB Oracle or any Database Ports need for Discovery needs to be found in the appropriate files

No one shoud have to enter the data .. This is discovery!!!!  Should be able to be found  with comands and or reading config files

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: UCMDB Oracle or any Database Ports need for Discovery needs to be found in the appropriate files

No one should pay taxes also 🙂

Kind regards,
Bogdan Mureșan

EMEA Technical Success
0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: UCMDB Oracle or any Database Ports need for Discovery needs to be found in the appropriate files

According to Microfocus

“It depends on the access you have to the servers hosting Oracle”

 If you have shell access to the server, and are able to run the Host Applications by Shell job (with IP Service Endpoint collection turned on), you should not have to identify the Oracle ports in the portnumbertoportname.xml file

 If you do not have shell access to the server, you can still discover Oracle, via the Oracle by SQL job, but a prerequisite for this discovery is to run the TCP Port job, which DOES require the Oracle ports be documented in the portnumbertoportname.xml file.

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: UCMDB Oracle or any Database Ports need for Discovery needs to be found in the appropriate files

Hi Lee,

I understand your frustration because Oracle discovery is really messed up. There is definitely some issue with discovering the TNS Listeners from several jobs. At the same time you have the Oracle Connection by Shell, which doesn't use SQL statements issued from the probe and it does NOT require to specify the ports in the portnumbertoportname.xml. I suppose the TCP Ports job is there to guarantee that the DFP has network connectivity to the TCP ports of Oracle. In other case you may find thousands of local ports opened, but not available through the network.

 

Petko

Likes are appreciated!
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.