Monitoring a IBM StorWize V3700 with a Special agent - agent_ibmsvc

[marktm]

Hey guys, I have a problem with my StoreWize V3700.
On previous version of Check_MK 1.6.0pXX I have monitored my data storage with special agent with SSH.

Everything works fine!
I have modified special agent config agent_ibmsvc on line 224 - I have added command “sshpass” before ssh:

cmd = “sudo sshpass -p PASSWORD ssh -o ConnectTimeout=%s %s %s@%s '” % (opt_timeout, opt_any_hostkey, user, host_address)

Location of config on 1.6 version:

/omd/versions/1.6.0p22.cre/share/check_mk/agents/special/agent_ibmsvc

On new version 2.0.0p1 I can’t find useful agent config to add credentials.

/opt/omd/versions/2.0.0p1.cre/share/check_mk/checks/agent_ibmsvc
/opt/omd/versions/2.0.0p1.cre/share/check_mk/agents/special/agent_ibmsvc

Where is stored config of special agents on new version?
Is there any other option to monitor StoreWize over SSH?

Thanks,
Marko

[openmindz (Thomas Karatzoglou)]

Hi @marktm

I have never, ever edited the check script to get a Storwize storage monitored. There’s a rule called “IBM SVC / V7000 storage systems” which requires the username of an SSH user you’ve set up, which works for V3700,V5000 and V7000. What I normally do is to do a ssh-keygen as my siteuser, get the public key, configure it on the storage (Monitoring role is sufficient), and that’s it. This rule exists in CMK 2.0 as well.

HTH,
Thomas

[marktm]

Thanks, I have re-generated public key without passphrase, uploaded public key to storage and monitoring works again.

BR,
Marko