Highlighted
Contributor.. Contributor..
Contributor..
141 views

Error running NNMi to UCMDB Integration - Layer2 Topology Import

Hello, I have been successful with this integration in the lab, but when I try in production I get this error: Cannot retrieve communication log because trigger CI 8fd938e7e4bf8708dcbae26dc4fae07d is missing for job: DS_NNMi2UCMDB_Layer2 Topology Import from NNMi

 

The NNMi server has been discovered and I can access the NNMi server from the UCMDB server via port 80 - I have tested the credentials and they work.   I'm not sure what I am missing.    What I don't see is the TEST CONNECTION function - it is greyed out.  Thanks !

0 Likes
4 Replies
Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: Error running NNMi to UCMDB Integration - Layer2 Topology Import

What the CI with ID 8fd938e7e4bf8708dcbae26dc4fae07d is?

You can search by the ID in CI selector...

Regards
-Dmitry Gomel, PMP
Click the Like button at the bottom to say 'Thanks'.
0 Likes
Highlighted
Contributor.. Contributor..
Contributor..

Re: Error running NNMi to UCMDB Integration - Layer2 Topology Import

It is the CI for the IP address of the NNMi server
0 Likes
Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: Error running NNMi to UCMDB Integration - Layer2 Topology Import

We need to see logs. I guess retrival of comm log error is not a root cause error.

 

Regards
-Dmitry Gomel, PMP
Click the Like button at the bottom to say 'Thanks'.
0 Likes
Highlighted
Contributor.. Contributor..
Contributor..

Re: Error running NNMi to UCMDB Integration - Layer2 Topology Import

Thanks, I guess I will need to open a case then - I thought that having just this error in the communication log was indicative of something fundamentally missing or incorrect - like the NNMi server was not fully discovered.
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.