Enable connectivity for
HPE 3PAR Storage
Contents
Network pre-requisites for call home to work:................................................................................................................................................................................................ 2
Firewall or port requirement for configuring inbound and outbound connectivity on HPE 3PAR arrays ........................................ 2
Firewall and port requirement: ............................................................................................................................................................................................................................... 2
Additional note: SP-to-InServ communication ........................................................................................................................................................................................ 2
How to verify if call home is setup and working: ...........................................................................................................................................................................................3
Verifying call home from the HPE 3PAR system or array: .............................................................................................................................................................3
When call home is not configured with secure network mode: ................................................................................................................................................ 5
Notify HPE 3PAR so the configuration can be setup correctly (especially for new installs):........................................................................ 7
Reference guide
Reference guide
Page 2
Call home benefit
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
Additional note: SP-to-InServ communication
While not related to remote connectivity of HPE 3PAR support portal, if the InServ and the Service Processor are placed on different IP networks
and there is an IP firewall between them. The following ports must be opened for communication between the InServ and the Service Processor.
Port 22 (SSH)—used for depositing and executing programmatically driven service scripts and for collecting an archive of diagnostic data
(known as an InSplore)
Port 2540 (CLI)—used for gathering system health information, configuration data, and performance data
Port 5781 (Event monitor)—used for monitoring system events on the InServ
Reference guide
How to verify if call home is setup and working
Verifying call home from the HPE 3PAR system or array:
Option 1:
Open SPOCC by entering the IP address of the Service processor into a Web browser.
Click Support on the left menu  click the SP Control menu  choose File Transfer Monitor.
Figure 1: Screenshot of SPOCC—Support page
Figure 2: Screenshot of SP File Transfer Monitor
Page 3
Reference guide
Option 2:
Login to the Service processor establishing a CLI session (SSH).
On the SPMAINT menu, choose option 1  SP Control Status  choose option 6  File Transfer Monitor.
Figure 3: Screenshot of the SP Control Menu
Figure 4: Screenshot of SP File Transfer Monitor
Page 4
Reference guide
The SSAgent upload queue will show files being emptied as and when the file transfer happens to our collector server.
When call home is not configured with secure network mode:
The following screenshots show the File Transfer Monitor on the SP which is not configured with secure network mode:
Figure 5: Screenshot of SP File Transfer Monitor without Secure Network Mode
Note
SSAgent queue will not be seen if call home is not configured on the Service Processor.
How to configure call home—if not configured:
Follow this procedure to configure the device in secure network mode.
To migrate from SP mode to secure network mode:
1. Log in to SP as spvar (password prompted).
2. From the SPMAINT main menu, type 2 for Network Configuration and press ENTER.
3. Type 2 for Connection Portal control and press ENTER.
4. Type A for Activate Secure Network Mode to activate mode and follow through the prompts.
Detailed installation instructions are as follows:
To migrate from SP mode to secure network mode:
1. Log in to SP as spvar (password prompted).
2. From the SPMAINT main menu, type 2 for Network Configuration and press ENTER.
3. Type 2 for Connection Portal control and press ENTER.
4. Type A for Activate Secure Network Mode to activate mode and press ENTER.
5. Verify the following message requirements, type Y and press ENTER to continue.
6. Type the static IPv4 address assigned to the domain server or none and press ENTER.
Page 5
Reference guide
Page 6
7. Based upon the system configuration requirements, type the specific confirmation to proceed with allowing HPE 3PAR Secure Service Policy
Manager to communicate with HPE 3PAR Secure Service Collector. If you choose yes, enter the IP address of HPE 3PAR Secure Service
Policy Manager and other details.
8. Type yes to allow remote access to the service processor.
9. Verify the data is correct and type yes to confirm.
10. Type 1 to assign the type of HPE 3PAR Secure Service Collector Server to connect with the SSAgent.
11. Type no, if you do not require a proxy server to connect to the HPE 3PAR Secure Service Collector Server. If you choose yes, provide the
details of the proxy server.
12. Verify the data is correct and type yes to confirm. The SP initializes communication with the HPE 3PAR Secure Service Collector Server, which
completes configuration setting for communication access.
Figure 6: Sample Screen output after step 12
When the system communications configuration is complete, the following message appears. Press ENTER to exit.
Figure 7: Completion of the Secure Network Mode conversion
Note
For any technical assistance with the call home setup, you may contact HPE Support and get a ticket logged for SP connectivity.
Reference guide
Notify HPE 3PAR so the configuration can be setup correctly (especially for new installs):
Call HPE Support with the following details to get the device added correctly to the relevant Hewlett Packard Enterprise systems.
You must update the following information on call:
1. Customer name
2. Customer address:
Street address, City
State
Postal/Zip Code
Country
3. HPE System Serial Number—i.e., USExxxxxxx, SGHxxxxxxx, CZxxxxxxx
4. SP ID—SP ID is located on the HPE InServ box. You can also find the SP ID on the sales order.
5. HPE sales order or purchase order number—i.e., 26Z023227001, 24Z036117001, 24Z047248001
6. Customer HPE Passport ID/user name (HPE Passport ID enables you to log in to HPE Support Center and view your HPE 3PAR devices in
HPE Insight Online. To obtain a HPE Passport, click here.)
Learn more at
hpe.com/services
Sign up for updates
Rate this document
© Copyright 2015 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice.
The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying
such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall
not be liable for technical or editorial errors or omissions contained herein.
4AA5-1582ENW, December 2015, Rev. 1