API authorization: NOK Seagate Exos 5U84/HPE MSA P2000

Phoenycks

Hello,

A Seagate Exos is what HPE rebrands as an MSA P2000 - literally the same interface, just says Seagate instead of HPE.

I had this working perfectly in Stor2RRD using the HPE MSA P2000 settings until I applied a firmware update to the Exos, taking it to latest code version GN280R010-01.

Now I've lost connectivity to the array with smis errors:

Under user: lpar2rrd
smis command failed: "export LIBPATH=:/usr/stonavm/lib; /usr/bin/wbemcli -noverify -nl ei https://stor2rrd:XXXXX@10.128.10.171:5989/root/dhs:CIM_ComputerSystem"

Under user: lpar2rrd
smis command failed: "export LIBPATH=:/usr/stonavm/lib; /usr/bin/wbemcli -noverify -nl ei https://stor2rrd:XXXXX@10.128.10.172:5989/root/dhs:CIM_ComputerSystem"

Under user: lpar2rrd
smis command failed: "export LIBPATH=:/usr/stonavm/lib; /usr/bin/wbemcli -noverify -nl ei https://stor2rrd:XXXXX@10.128.10.171:5989/root/hpq:CIM_ComputerSystem"

Under user: lpar2rrd
smis command failed: "export LIBPATH=:/usr/stonavm/lib; /usr/bin/wbemcli -noverify -nl ei https://stor2rrd:XXXXX@10.128.10.172:5989/root/hpq:CIM_ComputerSystem"

Under user: lpar2rrd
smis command failed: "export LIBPATH=:/usr/stonavm/lib; /usr/bin/wbemcli -noverify -nl ei https://stor2rrd:XXXXX@10.128.10.171:5989/root/smis:CIM_ComputerSystem"

Under user: lpar2rrd
smis command failed: "export LIBPATH=:/usr/stonavm/lib; /usr/bin/wbemcli -noverify -nl ei https://stor2rrd:XXXXX@10.128.10.172:5989/root/smis:CIM_ComputerSystem"

I've replaced the password with X's, but it's not an authentication issue. The user has Manage permissions, and SMI-S is checked. I've changed nothing, just updated the firmware and it stopped talking to Stor2RRD.

Has anyone else encountered this with Seagate or MSA arrays? Are there any other array types I might try to get it reconnected? Any other suggestions?

Thanks!

Pavel

Hi,

what do you get:

su - stor2rrd # lpar2rrd on the virtual appliance

/usr/bin/wbemcli -noverify -nl ei https://stor2rrd@10.128.10.172:5989/root/hpq:CIM_ComputerSystem

Pavel

this yet:

/usr/bin/wbemcli -noverify -nl ei https://stor2rrd@10.128.10.172:5989/root/dhs:CIM_ComputerSystem
/usr/bin/wbemcli -noverify -nl ei https://stor2rrd@10.128.10.172:5989/root/smis:CIM_ComputerSystem

Phoenycks

https://forum.xorux.com/discussion/comment/5535#Comment_5535

Hi Pavel:

If I run your commands, it just tells me it's invalid (these are in the order you posted)

* /usr/bin/wbemcli: Cim: (3) CIM_ERR_INVALID_NAMESPACE: Invalid namespace

* /usr/bin/wbemcli: Cim: (5) CIM_ERR_INVALID_CLASS: Class not found

* /usr/bin/wbemcli: Cim: (3) CIM_ERR_INVALID_NAMESPACE: Invalid namespace

I'm thinking they must have changed something, and maybe at this point Xorux might need to add support for this array specifically. I'm open to additional thoughts though...

Pavel

do you any API docu of that storage?

Phoenycks

This is about the best I can find: https://www.seagate.com/files/www-content/support-content/raid-systems/_shared/documentation/83-00007047-14-01-C_G280_SMG.pdf

Starting on page 179 I think. I'll see if I can find anything else...

Pavel

ok, this must work as per the docu but it does not

/usr/bin/wbemcli -noverify -nl ei https://stor2rrd@10.128.10.172:5989/root/smis:CIM_ComputerSystem

what is stor2rrd user role? Monitor? From some firmware level is required even "standard" role, can you add that role and try above cmd again?

Pavel

Hi,

I think we found the problem, a bug storage firmware

we have confirmed bug in other rebrand of that storage by the vendor, expected fix in the firmware release about May 2023!

We suppose it affects all rebrands of that storage include Segate one.