Database TCP ports not able to recognize the format of portNumber="49155–65535" in the portstoportname xml

  • Document ID:KM03767430
  • Creation Date:10-Dec-2020
  • Modified Date:20-Apr-2021
    • Micro Focus Products:
      universal cmdb 2020.02

Summary

CMS manages the tcp port and there details and some time we find that processing fails the entries.

Error

Many time ucmbd probe fails to idenitfy the entries like 49155–65535 in the portstoportmapping.xml and it skips the line mentioned. 
 

 [ERROR] [ProbeGW: DB Tasks Distributor] (KnownPortsConfigFile.java:73) - Failed to parse port 49155–65535, skipping

com.hp.ucmdb.discovery.library.communication.downloader.cfgfiles.InvalidRangeException: For input string: "49155–65535"

 

At the same time, if we configure the below port details, it identify without any issue.

 <portInfo portName="oracle" portNumber="1920-1999" portProtocol="TCP" discover="1" cpVersion="6" />

 

 

Cause

The root casue  why ucmbd probe fails to idenitfy the entries like 49155–65535 in the portstoportmapping.xml and  skips as the seperator is wrong.
The entries like portNumber="1920-1999" wokrs without any problem.
 
Depending upon the key board we are using, some time seperator differs and hence it causes the problem. 
 

Fix

The root cause why ucmbd probe fails to identify the entries like 49155–65535 in the portstoportmapping.xml and it skips it.

The entries like portNumber="1920-1999" works without any problem.

Depending upon the key board we are using some time separator differs and hence it causes the problem. Make sure that the separator which we uses is small one(-)