New Service Processors, new remote destinations
Posted: Mon May 19, 2014 10:42 am
We upgraded some service processors this last week. It seems both support and myself were caught off guard by the new SPs using a new phone home servers requiring firewall changes. The actual hostnames/ip have been xxx'd out for safety reasons... the real message here is that if your upgrading - double check if you need to edit your firewalls/acls and get the real hostnames/ip from support.
Something I like about the upgrade: CCA (customer controlled access) now works with SSA configurations.
The old configuration used by SP-2.5.2.GA-11 (as well as others I am sure)
Port 443 (https) to be opened (outbound)
xxxx.3pardata.com 66.xx.xx.xx
xxxx.3pardata.com 66.xx.xx.xx
xxxx.3pardata.com 66.xx.xx.xx
xxxx.3pardata.com 66.xx.xx.xx
xxxx.3pardata.com 66.xx.xx.xx
xxxx.3pardata.com 66.xx.xx.xx
This new configuration that needs to be put in its place with SP-4.1.0.GA-97:
Port 443 outbound from <service processor> to:
xxx.houston.hp.com 15.201.xx.xx (Primary IP)
xxx.houston.hp.com 15.240.xx.xx (Secondary IP)
xxx.houston.hp.com 15.201.xx.xx
xxx.houston.hp.com 15.201.xx.xx
xxx.houston.hp.com 15.240.xx.xx
xxx.houston.hp.com 15.240.xx.xx
Something I like about the upgrade: CCA (customer controlled access) now works with SSA configurations.
The old configuration used by SP-2.5.2.GA-11 (as well as others I am sure)
Port 443 (https) to be opened (outbound)
xxxx.3pardata.com 66.xx.xx.xx
xxxx.3pardata.com 66.xx.xx.xx
xxxx.3pardata.com 66.xx.xx.xx
xxxx.3pardata.com 66.xx.xx.xx
xxxx.3pardata.com 66.xx.xx.xx
xxxx.3pardata.com 66.xx.xx.xx
This new configuration that needs to be put in its place with SP-4.1.0.GA-97:
Port 443 outbound from <service processor> to:
xxx.houston.hp.com 15.201.xx.xx (Primary IP)
xxx.houston.hp.com 15.240.xx.xx (Secondary IP)
xxx.houston.hp.com 15.201.xx.xx
xxx.houston.hp.com 15.201.xx.xx
xxx.houston.hp.com 15.240.xx.xx
xxx.houston.hp.com 15.240.xx.xx