Highlighted
Outstanding Contributor.
Outstanding Contributor.
429 views

CMDB 10.33 NNMi Integration fails

Our NNMi Integration job "fails" sometime after 1 hour (last run was 1h 19m) with:

<2018-10-23 16:24:21,822> 4810372 [ERROR] [JobExecuterWorker-0:DS_NNMi Production_Layer2 Topology Import from NNMi_137.15.1.212] (?:?) - ErrorMsgCode: 27

jvm 1    | java.io.EOFException

Does anyone have any insight into this or seen anything similar?

0 Likes
9 Replies
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: CMDB 10.33 NNMi Integration fails

This is the error number for unability to attach to RemoteProcess. The background is that the DFP can execute certain adapters in a remote java process container, not to take the resources from the probe. 

You can check RemoteProcess.log and WrapperProbeGw.logs on the DFP for that. See why Remote process is not being created, maybe not enough memory is available. You can also disable this feature at the Integration Point, setting "Running in separate process" to "false" 

Cheers,

Petko Popadiyski

Freelance Microfocus CMS UCMDB Consulting

 

Likes are appreciated!
0 Likes
Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..

Re: CMDB 10.33 NNMi Integration fails

The RemoteProcess and WrapperProbeGw logs did not reveal anything non-cryptic.  We set "Run In Separate Process" to false and received the following error immediately after initiating the job:

Failed executing script, details: Traceback (most recent call last):
  File "nnmi_filters", line 5, in <module>
  File "post_import_hooks", line 38, in _post_import_notifier_fn
  File "post_import_hooks", line 27, in __import_and_notify
ImportError: No module named nms

In addition to investigating this new error, we will try adjusting the memory parameters set in Remove JVM Args.

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: CMDB 10.33 NNMi Integration fails

Hello Mike,

what are the exact remote JVMargs?

Kind regards,
Bogdan Mureșan

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

Re: CMDB 10.33 NNMi Integration fails

Initially the JVMargs was set to "–Xms1024m –Xmx2560m".  Reducing to "–Xms1024m –Xmx2048m" made no difference (failed after 75-80 minutes).  Increasing to "–Xms1024m –Xmx4096m" the job failed after running for 25+ hours but the job only created 48 CIs and updated 946 CIs.

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: CMDB 10.33 NNMi Integration fails

Hello Mike,

 

that's the HEAP memory, I was hopping I would catch you with the non-HEAP memory definition 🙂

 

Kind regards,
Bogdan Mureșan

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

Re: CMDB 10.33 NNMi Integration fails

Hey,

so it works, but doesn't discover enough CIs? 

First you have to decrease the scope to only what you need. Remove the VLANs, Physical Ports and Layer2. Then set the discoveryMode to full, instead of related, giving more memory to the remote process. 

Keep in mind the recommended method for integration of UCMDB is the data to be pushed from NNMi and not populated from UCMDB! UCMDB NNMi adapter is really crappy and in previous integration we rewrote it from scratch.

Cheers,

Petko Popadiyski

Freelance Microfocus CMS UCMDB Consulting

 

 

Likes are appreciated!
0 Likes
Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..

Re: CMDB 10.33 NNMi Integration fails

Hello Bogdan

Well, the Remote JVM Arguments to which I was referring earlier is from the Adapter Properties in the Integration Point definition.  Please advise where the non-heap memory is defined.

Regards

Mike

0 Likes
Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..

Re: CMDB 10.33 NNMi Integration fails

Hello Petko

It works for a period of time (creates/updates CIs) but fails after 75-80 minutes.  I increased the memory allocation in the integration point's Remote JVM Arguments, and then decreased the scope and used full discoveryMode as you mentioned.  This extended the last run to 110 minutes. Not sure if this can be corellated or is coincidental.

We are aware that the recommended approach is to push data from NNMi rather than use the UCMDB's population adapter.  Without going into the politics of it, we are trying to maintain control of the data retrieval on the UCMDB side, so for the time being we are using the population.

Regards

Mike

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: CMDB 10.33 NNMi Integration fails

Hi Mike,

 

it's all about playing with the numbers - memory, batch size, etc. Sometimes the adapter may syncrhonize successfully and the next day fail. It is quite buggy and that's why it is not being recommended. If you really need to live with it, you have to try all the different options and see what works for you.

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.