We are running ESRS 2.28 and Isilon 7.2
Firewall Ports 443 and 8118 are opened outbound from the cluster subnet to the GW and ports 22 and 8080 opened for inbound traffic from the GW to the Isilon subnet.
We try to run the command isi_gather_info --esrs for sending logs to EMC but the command fails connecting to the ESRS gateway.
Our Firewall support engineers see a connection to the ESRS but the server is not responding.
Is there anything that needs to be done on the ESRS to accept the connection?
When you run isi_gather_info --esrs command, isilon directly sends log file to EMC and GW server pretends as proxy server.
Could you please also check below?
(1) log file size (Isi_gather_info log size would grow too large to send to EMC direclty.)
(2) Gateway proxy service is running or not. (Gateway proxy service is for proxy server)
If gateway proxy service in your Gateway server would ruuninng, the issue would be caused by log file size
Isi gather info shows also log file size.
please find "Content-Length"
NP to share your log, please attach it here (please delete S/Ns)
Looking like there's a file size limit. I've been passed from the ESRS Support team back to Isilon but not sure what good that will do. A full gather on our clusters is over 5Gb
so . . . . who didn't see this coming?
That would be great. But I'm getting the 'you're not allowed to view this content' message when I click that link. Hopefully this isn't just extending the timeout value of an http upload on the ESRS GW because I've extended it to 3600 seconds and it still doesn't go.
So I had my CE get me the KB article. Are there any examples for the line we're supposed to add to this proxy server that ESRS 3.x has added to the flow?
forward / <Customer Proxy Address>:<Customer Proxy Portnumber>