In the health check and analytics tab we are seeing this " partially unknown" message with regards to parity groups.
I cant seem to find any documentation or errors to define what is unknown.
Would someone point me to an answer?
It could be that when the Tuning Manager instance was created "Unassigned Open Volume Monitoring" was not changed from the default 'no'. This is required to monitor parity group performance in an HDP/HDT environment. Go to your tuning manger server <HCS install path>\TuningManager\jpc1pc\tools folder in a command prompt
run jpctdchkinst -inst <instance name>
Chuck Strickland, what is the message id you are getting against this error?
there isnt an error message. see the snipit below from the analytics tab.
we've searched for an error code log files but havent found one.
Is there any format process or blocked devices in any of the parity groups? Also check for any warning message in the parity groups.
nope. No issues on the array.
I've seen this on several arrays at multiple customers.
I have just now decided to try and figure it out.
what version of Tuning Manager and Agent for RAID? I am seeing this only on my HUS-VM's right now.
If you find you have "Unassigned Open Volume Monitoring" off and are not getting parity group information here's how to correct it.
On your tuning manager server open a command prompt and CD to <HCS install folder>\TuningManager\jp1pc\tools
E:\Apps\HiCommand\TuningManager\jp1pc\tools>jpcinssetup.exe agtd -inst <instance name>
KAVE05912-Q The instance environment already exists. Do you want to update? (Y/N) Y
KAVE05089-Q Running services will be forcedly terminated. Do you want to continue? (Y/N) Y
KAVE05090-I Service is stopped.
Storage Model (1:Thunder/AMS/HUS100 or 2:Lightning/USP/USP V/VSP/HUS VM) [Lightning/USP/USP V/VSP/HUS VM] :
Command Device File Name [\\.\PhysicalDrive0] : [enter]
Unassigned Open Volume Monitoring (Y/N) [N] : Y
Mainframe Volume Monitoring (Y/N) [N] : [enter]
KAVE05913-I The instance environment is being updated. (servicekey=RAID, inst=Test) KAVE05914-I The instance environment was updated. (servicekey=RAID, inst=Test)
KAVE06007-I The service will now start. (service=Agent Store for RAID, inst=Test)
KAVE06007-I The service will now start. (service=Agent for RAID, inst=Test)
this is the answer. after we turned on the monitoring we did see % busy reports.
however we dont see many other parameters such as IOPs. Not sure why that is.
If you are seeing a KAIC15718-E error please upgrade to HCS 7.5.0-05
If you are already running 7.5.0-05 file a case with GSC
Retrieving data ...