DCNM 10.1 error "cannot find server for"

[cristina.gomezmunoz]

Hi all,

We have experienced an issue after fresh installing DCNM 10.1 on a VM on our DC.

We wanted to install DCNM 10.1 on a Microsoft Windows Server 2008 R2 (64-bit) using the default parameters, but when trying to install PostgresSQL 9.4 we received the following error message:

The problem seems to be with PostgreSQL database from default installation DCNM kit. We installed PostgreSQL separatedly and tried again, and DCNM got installed successfully.

However, when trying to add any device on the Inventory, we receive the following message:

We are able to add the IP and credentials for the specific device, DCNM successfully identifies the info introduced, and when clicking on the Next button for the device addition on the list, we receive the above message and the device is not added. This symptom matches with the identified bug CSCuz99974, but the conditions are not the same.

This was installed from the scratch (no upgrade), installing version 10.1 directly on a Windows Server machine. I've attached the postgresql installation log in case it is useful.

Do you guys have any clue about why the PostrgreSQL installation fails and, as a result, DCNM is not able to get devices registered?

Thanks!

Cris.

[pescatj01]

Hi all, 

The problem was solved by downgrading the Postgresql version (in our case PostgreSQL 8.3).

To check wether the database is causing this issue, we need to go through DCNM logs:

Go to [E/C...]:\Program Files\Cisco Systems\dcm\fm\logs and check fmserver.log, and also fm_ws.log

If you find next message on your logs, you are probably hitting a DB issue: 

fmserver.log: WARN  [fms.ClusterMapping] addr is of illegal length

fm_ws.log:  WARN [fms.ws] WebUtil caught exception in updateServerProperties():
                     java.rmi.RemoteException: addr is of illegal length

Proceed re-installing Windows Server from the beginning. Install PostgreSQL 8.3 packets and create dcnm user and dcmdb database to work with the DCNM.

The reason why the automatic installation fails during pgsql installation still unknown.

Hope this workaround helps in case you face the same issue.

Cheers,

P.E.