some months ago I made a fresh install of STOR2RRD on a new Linux machine after having used it for several years on AIX before.

Our 3PAR systems are monitored as expected but unfortunately I'm facing issues with pool/CPG/tier monitoring for our new Alletra MP storage systems. STOR2RRD shows 0 I/O for all pool, CPG & tier graphs though I'm absolutely sure there is some I/O ongoing.

Additionally there is some minor bug with host monitoring on those Alletras. The global monitoring is working fine but the items section for single hosts is not existing.

Do you have an idea what might be causing this?

Best Regards!

I installed latest stor2rrd (8.05) and added HPE MSA 2060. it can monitor everything but I have gathering data error on one of volumes. I've attached picture of errors. I will appreciate if you help me to solve it.

I use Stor2rrd (free version) for monitoring my SAN/Storage environment and since last update of firmware (to version: 6.1.2.400-1048557) on my Nimble and Alletra storage arrays I keep receiving following notification from Stor2rrd:

"STOR2RRD Health Status event for device NimbleArray B AF-12345-C2 active OK OK resynchronizing OK"

This communicate is being sent every day at the same time.

HPE support has already confirmed that the storage is healthy and no resynchronization is ongoing.

Did you already have similar problem reported by customer's using Stor2rrd for monitoring Nimble/Alletras?

What this event means?

Best Regards, MC.

"platformType": "HPE StoreOnce 5250",

"softwareVersion": "4.3.7-2345.50",

and stor2rrd v7.92

1. Total alerts - 262. So stor2rrd showing in "Health status" not recent events but first, starting 0.

/home/stor2rrd/stor2rrd/bin/storeonceperf_v4.pl

line 60 - get_alerts("https://$ip/rest/alerts");

Can you change to show alerts starting "last first"?

2. Time column in Alerts table sorting very strange, mixing years 2023 and 2024.

for example:

Can you fix this?

3. Overall Status looks like OK but our hardware NOT OK:

You getting information from

https://ip_address/api/v1/data-services/dashboard/appliance/{id}

"catStoresSummary": {

  "statusSummary": {

   "numOk": 0,

   "numWarning": 0,

   "numCritical": 0,

   "numUnknown": 0,

   "total": 0

  }

BUT

"applianceStatus": "CRITICAL",

"applianceStatusString": "Critical",

.....

"hardwareStatus": "CRITICAL",

"hardwareStatusString": "Critical",

Is it possible to add hardware status in Health Status?

HPE-StoreonceDC1:PORT:data_rate-subsys failed ERROR: don't understand 'fc0' at /home/stor2rrd/stor2rrd/bin/detail-graph-cgi.pl line 8451. /home/stor2rrd/stor2rrd/bin/detail-graph-cgi.pl:836

I have multiple storages monitored and one of the systems is reporting the Status as red: storage-system status: NOK. I cannot identify why...

storage: host connection test

API host network connection: TCP connection to xxx.xxx.xxx.xxx:8080 is OK.

Crontab test: OK

API authorization: OK

  System Information
   IP              : xxx.xxx.xxx.xxx
   Name            : storage
   Model           : HPE_3PAR 8400
   Version         : 3.3.1.648
   Wsapi Version   : 1.6.5
   Configuration OK

API data test: OK

On storage side using  checkhealth -svc -d I cannot see any active alarm.

I already removed teh health_status_summary and re-loaded it again, but the warning persist.

Is there any log file available where I can identify why is reporting as red - not ok?

I'm used stor2rrd from version 2.70(now 7.30) and some monitoring features don't work :(

On Data tab (Total page) stor2rrd don't show data_rate (always 0), but another MSA 2050,2060 work properly. IO tab work properly and see IOPS for storage.

I think it's some parsing issue, but I'm not 100% sure.

What can be done ?

P.S. I recently had a case with HPE support regarding MSA 2060 and stor2rrd. Unstable work management controllers. Support answer - recommendations provided. Problem will be solved in future FW releases.

Recomendations - exclude MSA 2060 from stor2rrd monitoring :)

how can change the area chart to a line graph ( as mentioned in the next images )

From

to this

but now I waiting more 3days till now not appeared in the list, connection, and API it's OK

You can see the screen below:

While I used a browser account, as you mentioned in your documentation, I faced the issue below:

API authorization: NOK

after re-entering and returning to the admin account, it's working well

I have an issue with 2 HPE Primera storages. User permissions on storage are good. I know the self signed certificates on the arrays were renewed a while ago. Could that be the issue. And if so, how can I replace the certificates on the Stor2rrd?

TCP connection = OK (on port 443)

Crontab test = OK

API authorization = NOK. Error login failed.

Thanks for any help you can provide!

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!

I have multiple 3PAR 8200 and 8400 they all perfectly monitored via stor2rrd, but i realy miss one simple thing to able to have alert based on percentage of free space on CPG.

Is it possible to create this alert?

We have had an issue recently that might be nice if stor2rrd had seen it.

Our san switches are in stor2rrd and we find the crc error graph very nice. But this is only 50% of the coverage since you also need to monitor crc errors on the other side of the san switch.

Out problem was that the crc errors were rising on the 3par side and we did not notice it until perfomance was impacted. After some support calls with HPE I noticed they use the showportlesb command and that the 3par/primera has a retention history of crc errors of the port and the hosts.

It would be amazing if stor2rrd could integrate this in the hpe monitoring so it can be graphed.

Example of command: (in this cace the crc errors went from 7601 to 7743 between Aug 18 03:47:24 and Aug 18 09:44:40)

showportlesb hist -startt 08/18 1:2:1

Aug 18 03:47:24

   ID   ALPA ----Port_WWN---- LinkFail LossSync LossSig PrimSeq InvWord InvCRC

<1:2:1> 0x180c00 21210002AC024572    22   835    5    0  6826  7601

...

Aug 18 09:44:40

   ID   ALPA ----Port_WWN---- LinkFail LossSync LossSig PrimSeq InvWord InvCRC

<1:2:1> 0x180c00 21210002AC024572    22   835    5    0  6826  7743

...

Under user: lpar2rrd
ssh command failed: "export TPDCERTDIR=/home/lpar2rrd/stor2rrd/etc; export TPDPWFILE=/home/lpar2rrd/stor2rrd/etc/.3par-10.200.205.158.pwf; /opt/hp_3par_cli/bin/cli -sys 10.200.205.158 -pwf /home/lpar2rrd/stor2rrd/etc/.3par-10.200.205.158.pwf statvv -rw -d 1 -iter 1"
The authenticity of the storage system cannot be established.
CLI Server Certificate
  Issuer:           CN=HP_3PAR 7450c-1688261
  Subject:          CN=HP_3PAR 7450c-1688261
  SHA1 fingerprint: 85247F00E7533FC35C9BFD9EC2C54B1FC9A75CEF
  Validity:         Not before: Jan 21 06:30:19 2022 GMT
                    Not after:  Jan 20 06:30:19 2025 GMT
  Warning: self signed certificate
  Warning: subject CN ("HP_3PAR 7450c-1688261") does not match the system name ("10.200.205.158")
Continue connecting (yes/no)?