No connection to midway.ext.hpe.com over proxy after most recent firmware update - Storeonce 510

[mgloax]

Hi,
After the most recent firmware upgrade (3.18....) we cannot contact HP servers anymore. HP changed it to midway.ext.hpe.com but we made sure that this site is not manipulated in any way by the proxy. Browsing the site from a regular client works fine. Apart from the new feature above the storeonce settings are unchanged. We checked with net ping ipaddr from the shell that the proxy is reachable and it's like expected since it hasn't changed a bit. Net show config is also fine.

Any help is greatly appreciated.

[Amarjit_Y]

Try to Communicate via the proxy server using the http or socks protocols instead of https.
To communicate via the proxy server using the http or socks protocols perform the following steps :
In the StoreOnce GUI:
1. Click on the ‘Remote Support’ button in the navigation tree.
2. Click on the ‘Modify’ button in the top right-hand corner of the ‘Remote Support’ page.
3. When the ‘Modify’ sub-window opens, scroll down to the proxy server section.
4. Click on the ‘Protocol’ drop-down menu and select either ‘http’ or ‘socks’ depending on your preference.
5. Click on the ‘OK’ button.

See if this helps !

[mgloax]

Hi,
We did exactly that without success. In the syslog we can see http 200 from the storeonce trying to connect some houston.hpe.com servers but the error persists. Is there some reset command to reinitialize the registration or soemthing?

Thanks

[dbond]

Did you find a solution to this? Have exactly the same problem.

Have 8 3par arrays, all the midway.ext.hpe.com do not work. The strange thing is, they are all on the same version of the service processor. but some are midway, others are not.

[mgloax]

Hi
Not sure what parts where necessary to make it work but here's a short summary.

- We ended up excluding the client IP (the HPE storage devices / processors) from rule processing in our proxy software. Excluding the HPE update server IPs or names wouldn't work

- Some HP technician reset the client certificates on the devices they apparently use to authenticate against the HPE update servers. Individual steps are missing since it was a telco with several people involved but you should contact HPE for support.

cheers