Origin3k
1 Copper

RE: SAN HQ enquiry

Jump to solution

1. The SANHQ runs as a service within the background. As longs as the Windows OS and the SANHQ Service is up and running it will work. I havent played with the last SANHQ EPA version but in all previous releases you have the choice to use the Mail konfiguration you specified on the EQL Group it self or configure a new one. This is a setting per Group within SANHQ.

Only if you would take a look to the nice colored graphs you start the SANHQ Client. The Client is installed by default together with the SANHQ service and if you like you can it ALSO on others PCs if you have a need for or when multible persons are involved.

2. Not 100% sure but SANHQ cant send SNMP traps but the EQL Groupmanager can. Its located under Group->Group Configuration->SNMP.

Regards,

Joerg

0 Kudos
crescendas
2 Iron

RE: SAN HQ enquiry

Jump to solution

I realize that the email alert for storage reaching it's full capacity is only available when you create thin provisioning volumes in EQL. I have a think provisioning EQL volume that got full because of VM snapshots and I never receive any email alert from both EQl and SanHQ.

0 Kudos
Origin3k
1 Copper

RE: SAN HQ enquiry

Jump to solution

For a normal EQL LUN which ends in a VMFS Datastore it makes no different if you store data as a VM or Snapshot. For takeing care of vSphere Snaps you have to implement a snapcheck/report in your vSphere environment. The array cant see difference.

The game may changed with vVOLs where vSphere Snaps are handled in a different way.

Regards,

Joerg

0 Kudos
Origin3k
1 Copper

RE: SAN HQ enquiry

Jump to solution

The SANHQ 3.5.0 EPA  now can send SNMP Traps as well. So if you have a monitoring solution around which can handle Traps you can use it.

Regards,
Joerg

0 Kudos
Dell_Normski
Not applicable

RE: SAN HQ enquiry

Jump to solution

Hi

I'm sure everything in this post is very valid but I recently had to configure Support Assist and got the Unknown Credentials Failure status as above. Turned out that SSH had been disabled on one of the groups.

Simply enabling it got the wizard to complete.

Hope that helps someone.