Monitor an HP Tape Library/SNMP

Started by Lotfi, August 16, 2016, 03:30:03 PM

Previous topic - Next topic

Lotfi

Hello,
My NetXMS server (2.0.5) is running on WIndows Server 2008 and i want to monitor an HP MSL 4048 Tapelibrary with SNMP.
I created the appropriate node with deactivating agent polling, configured the MSL with the appropriate SNMP community which is configured in the MSL Management Network.
But, every minute, i get : SNMP_AUTH_FAILURE.
I would be so grateful if anyone can share a tip that helps resolving this problem.
Thanks in advance.

Victor Kirhenshtein

Hi,

seems that configuration still mismatch. Double check community on device and in node properties in NetXMS. Also make sure that NetXMS server IP address is listed as allowed in device SNMP configuration.

Best regards,
Victor

Lotfi

here are screenshots of my configuration :

Victor Kirhenshtein

Did configuration poll detect MSL node as SNMP node? If yes, it could be some other server trying to communicate with MSL over SNMP, and MSL just sending SNMP authentication failure traps to NetXMS server (because it is configured so).

Best regards,
Victor

Lotfi

#4
here is the full configuration poll :
[16.08.2016 15:33:40] **** Poll request sent to server ****
[16.08.2016 15:33:40] Poll request accepted
[16.08.2016 15:33:40] Starting configuration poll for node ROBOT-SAUVEGARDE
[16.08.2016 15:33:40] Capability reset
[16.08.2016 15:33:40] Checking node's capabilities...
[16.08.2016 15:33:40]    Checking SNMP...
[16.08.2016 15:33:41] Capability check finished
[16.08.2016 15:33:41] Checking interface configuration...
[16.08.2016 15:33:41] Unable to get interface list from node
[16.08.2016 15:33:41]    Interface "unknown" is no longer exist
[16.08.2016 15:33:41] Interface configuration check finished
[16.08.2016 15:33:41] Checking node name
[16.08.2016 15:33:41] Node name is OK
[16.08.2016 15:33:41] Finished configuration poll for node ROBOT-SAUVEGARDE
[16.08.2016 15:33:41] Node configuration was not changed after poll
[16.08.2016 15:33:41] **** Poll completed successfully ****

Besides, i get a different trap which is like the picture joint to this.
About your first question, no, it doesn't see the MSL as SNMP node.

Victor Kirhenshtein

Can you communicate with the library using command line tool (nxsnmpwalk or nxsnmpget)? For example

nxsnmpwalk -v2c -c your_community ip_address .1.3.6.1.2.1.1

also try community "public".

Best regards,
Victor

Lotfi

#6
Hello Sir,
I believe that setting community string to default "public" resolved my issue in my MSL. But i wonder what was the problem with it..?

Victor Kirhenshtein

Hi,

looks like MSL uses "public" as community ignoring configuration settings. Quick search found description of similar issue: https://thwack.solarwinds.com/thread/33561. If this is the case then it's a bug in MSL firmware.

Best regards,
Victor