Probe SNMPCollector Distribution Error

[jm_work]

We are having trouble in deploying the probe SNMPCollector in any secondary hub.

We already tried to deploy through both IM archive and Admin Cosole.

The distribution server returns the following error: "Aborted, retry limit exceeded, unknown status"

And an alarm is also generated: "Max. restarts reached for probe 'snmpcollector' (command = <startup java>)"

 

We have all the documentation pre-requisites installed.

Both versions 3.44 and 3.43 of SNMPCollector returns the same error.

 

Our probes version:

controller: 7.97

hub: 7.97

nas: 8.56

alarm_enrichment: 8.56

discovery_server: 8.52

discovery_agent: 8.52

ppm: 3.49

service_host: 8.48

ci_defn_pack: 1.44

mps_language_pack: 8.47

wasp: 8.51

wasp_language_pack: 8.51

 

Also, attached are the distsvr probe logs.

 

LOGs OF DISTSRV attached

 

Attachment(s)

distsvr.zip   306 KB 1 version

[Yu Ishitani]

Tell me controller version of the probe deployment target robot.

[jm_work]

Dear All,

 

This case was solved.

 

My archive from Core NMS was corrupted.

We desactivated the distribution server probe, removed the folder Archive from C: and activated the probe again.

After all, we were able to distribute the probe correctly. 

 

Regards,

Jean Gomes

[jm_work]

Hello,

 

It is version controller: 7.97 / hub 7.97 on all robots and hubs in our environment

[David Michel]

If not already done, deploy distsrv to the second tier hub and:

on the PRIMARY hub distsrv, open the distsrv gui, and go to the "Advanced Settings" tab and make sure "Use remote distsrv on distribution" is checked.

 

on the REMOTE hub's distsrv, open the distsrv gui, and go to the "Advanced Settings" tab and make sure both "Accept remote distributions" and "Use local archive for accepted remote distributions" are both checked.

[jm_work]

Michel,

 

Thanks for your reply,

We did this configuration before, but did not work.

 

 

 

[David Michel]

At the primary it shouldn't have 'accept remote distributions'

At the second tier 'use remote distrrv...' is only needed if you have third tier hubs there.

No doubt it is but just to make sure is a copy of the snmpcollector and all its dependencies in the local archive at that second tier hub?

Is that log from the 2nd tier?

At the target system is the probe folder created, files there?

As a test deploy a small probe?

Remote into the 2nd tier hub and try copying the snmpcollector package or file of equivalent size over.

[jm_work]

David,

 

Validating the Core NMS archive, I checked that the probe has the following status:

 

 

I downloaded it, the probe zip folder appeared in the correct folder.

 

 

But it still does not show up in the NMS archive. =/

[David Michel]

If the download was done via the IM console, close, and reopen the console to see if it now shows up.

If the download was done via a browser, and then copied into the \nimsoft\archive folder:

move the file to another location

drag and drop the file from that other location into the IM console archive 

this will let the application import the package and put a copy in the \nimsoft\archive folder.

 

Make sure the java_jre is also there in the local archive since it is listed as a dependency (right click Edit)