Re: 1  Yes, the SANHQ server needs access to both Mgmt and iSCSI subnets   You're Group IP is for iSCSI only.  That has to be on the same subnet as the iSCSI ports.  You don't have to route the iSCSI subnet,  installing a NIC on the SANHQ server that's on the iSCSI subnet prevents you from having to route it.  Which would somewhat defeat the need for dedicated management port.    Re: 2 SNMP name. Not usually.  There's no requirement.  When in doubt you can enter public  re: Syslog.  SANHQ is a syslog server, it will configure the array to point syslog messages at the SANHQ server 
I just setup SAN HQ and need some clarification: 1. Does SAN HQ need access to my iSCSI network to work? When I use my management IP, it prompted me for Group IP which is my iSCSI network. In this case, should I route my iSCSI network into my management/server network just for SAN HQ? Or should I reconfigure my SAN HQ into my iSCSI network instead so that I can continue to keep my iSCSI network isolated from my management and server networks? [IMAGE] Also, shouldn't my Group IP be within my iSCSI network subnet or should it be within my management/server network so that SAN HQ can access it? 2. Is the Group SNMP community name the same as the Equal Logic group name or Member name or any name I just add into the the SNMP Access entry? [IMAGE] 3. Should the SNMP trap destinations the IP address of the SAN HQ server?
SAN HQ enquiry