Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

How to monitor clickshare device in solarwinds?

Hello Everyone,

I am trying to monitor the clickshare devices in solarwinds via SNMP but it's failing. Anyone help how to add clickshare with SNMP polling.

Below are snmp settings on clickshare device.

username - Integrator

Passwd - Integrator

EngineID - XXXXXXXXX

SNMP server IP - 10.X.X.X

Thanks,

Alankar Srivastava

Find more posts tagged with

Accepted answers

All comments

JaroslawLadyga

Hi,

I'd try to test different versions of SNMP on Node Properties in NPM. If you have clickshare device supporting SNMP then at least SNMP v1/2 should work. When you pass testing connection then create necessary pollers with UnDP or Device Studio for particular OIDs (assume you know them).

alankar.srivastava

Hi,

Yes, Clickshare device supporting snmp. But there is no option to define snmp v1/v2/v3.

It has only few settings where we can give snmp server IP and define Username & Password. I believe if it's asking for username/Passwd then it's supporting snmp v3 i believe. I passed all the parameter in solarwinds console but test giving me failed result. I am not sure if solarwinds supporting clickshare monitoring.

Thanks,

Alankar

JaroslawLadyga

Hi,

please test SNMP version and port (on NPM Web interface Node Details>Edit properties) as on below screenshot:

Edit Properties.png

Clickshare is simple device so I expect that it supports SNMP v1 or v2c and Community String is rather "public" as default for most devices. Username&Password you use is probably only for Web Manager of Clickshare and has nothing to do with SNMP.

If you test SNMP Version (for v1/2, v2c) with Community String=public on default port 161 and test would fail then check out SNMP setting on Clickshare. If SNMP setting on Clickshare allows to set SNMP receiver (Orion server in this case) and nothing else then Community String is public and port is 161. If you can define Community String and port for SNMP on device then assure they are the same as on NPM properties for device.

alankar.srivastava

Hi Jaros,

Thanks for your reply. But in clickshare there is no option to set community string. Below is the article.

ClickShare CSE-200 - Knowledge Base - Information about SNMP on ClickShare - KB8471 - Barco

HerrDoktor

Do you own NPM only or is SAM also licensed? If SAM is in the Game I would have a look at the new API Pollers.

from what I‘ve read in the last 5-10 minutes on the Barco Website is the following: SNMP functionality: Parameters exposed via SNMP agent are available via REST API:

I am not sure if the Barco device only sends Traps via SNMP or if you can actually query over SNMP.

The document I was looking at is: ClickShare CSE-200 - Knowledge Base - Information about SNMP on ClickShare - KB8471 - Barco

cheers,

alankar.srivastava

SAM is also licensed.

Thanks

alankar.srivastava

I have NPM & SAM licensed. SAM ver. 6.7 & Orion platform 2018.2.

I think API poller support to Orion platform 2019.4.

HerrDoktor

Correct, API Pollers need Orion 2019.4

are some factors preventing you from updating? Like Server OS / DB Version?

HerrDoktor

Alright, so I was able to read some more documents.

the Device seems to support SNMPv3 only (Installation Manual Page 83)

now we either need to „bruteforce“ the combinations what encryption and authentication methods are used by the device or we need deeper documentation from Barco.

will keep you posted here what I can find

alankar.srivastava

We are running on windows 2012 R2 server. To upgrade the OS version to 2016 may take some time in approval.

alankar.srivastava

Thanks for sharing the findings.

I will try to contact Barco team as well if they can help in identify encryption & authentication methods.

mjperkins

Have you tried to use the same password entered in both the auth and priv sections of the SolarWinds node configuration? I have seen SNMPv3-supporting devices whose configurations only allow one password and had to use that password as both auth and priv when setting up the SolarWinds side.

alankar.srivastava

Yes, tried all available combination in solarwinds, but not worked.

HerrDoktor

So I haven’t found any more useful information. I guess the Barco Support ist your best option here. Sorry that I didn‘t find out more. Hope you get this running. If you do, let us know what combination works for Barco devices.

cheers

surak

Hey there, have you already tried the SNMP Walk tool?
There you get an instant reply if it works and can see the OIDs of the device.

If you don't get any reply from the device SNMP is not activated.

https://support.solarwinds.com/SuccessCenter/s/article/Troubleshoot-connectivity-and-MIB-issues-with-SolarWinds-SNMP-walk-IPv4-only

alankar.srivastava

Yes, already tried SNMP walk.

mathieu.slabbinck

Hi,

with snmpB it's working nicely on my side. Tested with Clickshare CSE-200 on the latest 1.10.0 release and snmpB 0.8. Below is a step by step configuration you can read up on and might find some clues to make it work in SolarWinds:

Prerequisites/assumptions:

snpmB installed and operational
ClickShare running and connected to the same network as the management entity running snmpB.
- SNMP is enabled via the ClickShare configurator (Wi-Fi & Network -> Services -> SNMP)
- For this example
  - Username: integrator
  - Password: integrator
  - Engine ID: 0x123456789
- If you want traps to work, make sure the ‘SNMP Manager’ field is filled in with the address of the server running the tooling. If not, you can leave this blank

Configuring the tool:

Add the ClickShare MIB in snmpB
1. Download it via the link at https://www.barco.com/en/clickshare/support/clickshare-cse-200/knowledge-base/KB8471
2. You can put the ClickShare MIB into the default path of snmpB. Alternatively via Tools -> Preferences -> Modules you can define a custom path to the ClickShare MIB
3. Load the module via the Modules tab. Find the MIB in the Available list and drag it to the Loaded list
Make sure snmpB knows the user profile, to do so:
1. Go to Options -> Manage SNMPv3 USM profiles…
2. Right-click the pane and click ‘New USM profile’
  1. Security user name: integrator (as defined in the ClickShare configurator)
  2. Authentication protocol: SHA
  3. Authentication password: integrator (as defined in the ClickShare configurator)
  4. Privacy Protocol: AES128
  5. Privacy Password: integrator (as defined in the ClickShare configurator)
  6. Save it
Add a new agent profile
1. Go to Options -> Manage Agent Profiles …
2. Right-click and ‘New agent profile’
  1. Name: as you desire
  2. Agent address: IP/hostname of the ClickShare
  3. Port: 161
  4. Supported SNMP versions: select only v3. v1 and 2 should be disabled.
  5. In the SNMPv3 subtree:
    1. Security level: select ‘AuthPriv’
    2. Security name: select ‘integrator’
    3. Context name: leave blank
    4. Context engine ID: 0x123456789 (as defined in the ClickShare configurator)
Via the Tree tab, you should now be able to select the Agent and Walk the tree or Get nodes

Hope this helps!