- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE 3PAR StoreServ Storage
- >
- StoreServ Connectivity
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2016 01:22 PM
07-05-2016 01:22 PM
StoreServ Connectivity
Call home benefit for StoreServ
Periodically, HPE Service Processors (SP) transfer diagnostic information such as system health information, configuration data, performance data, and system events to HPE 3PAR Central for remote diagnostic analysis and proactive fault detection.
Data is transferred frequently and maintained centrally on a historical basis, allowing for rapid, coherent analysis and problem resolution without onsite data collection or analysis dependencies that can prolong response.
Any critical alerts that are generated by the InServ are transferred immediately to HPE 3PAR Central for analysis and quick response, when necessary.
Network pre-requisites for call home to work:
Firewall or port requirement for configuring inbound and outbound connectivity on HPE 3PAR arrays
Outbound connection enables diagnostic data transfer such as alerts, InServ, SP log files, and configuration files for remote diagnosis. Inbound connection enables remote access to SP and InServ for authorized HPE 3PAR support personnel.
The mode used for SP communication to HPE 3PAR connection portal for diagnostic data transfer (outbound) and remote access (inbound) is listed as follows.
Secure network mode (for SPs that are at SP OS 2.5.2.GA-11 and above).
Firewall and port requirement: NETWORK REQUIREMENT
SECURE NETWORK MODE
HPE 3PAR support portal IP address
Your DNS server should allow remote3par.houston.hp.com to be resolved to 15.201.225.95 (primary) or 15.240.56.190 (secondary).
Outbound connectivity
Port 443 (https) to be opened (outbound) between SP IP and the following IP addresses:
remote3par.houston.hp.com—15.201.225.95 (primary)
remote3par.houston.hp.com—15.240.56.190 (secondary)
Inbound connectivity
Port 443 (https) to be opened (outbound) between SP IP and the following IP addresses:
remote3par.houston.hp.com—15.201.225.95 (primary)
remote3par.houston.hp.com—15.240.56.190 (secondary)
g4t2481g.houston.hp.com—15.201.200.205
g4t2482g.houston.hp.com—15.201.200.206
g9t1615g.houston.hp.com—15.240.0.73
g9t1616g.houston.hp.com—15.240.0.74
Contact : 3PAR-GDC-Connectivity - 3par.connectivity@hpe.com