<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic StoreServ Connectivity in HPE 3PAR StoreServ Storage</title>
    <link>https://community.hpe.com/t5/hpe-3par-storeserv-storage/storeserv-connectivity/m-p/6875513#M2649</link>
    <description>&lt;P&gt;Call home benefit for StoreServ&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;Any critical alerts that are generated by the InServ are transferred immediately to HPE 3PAR Central for analysis and quick response, when necessary.&lt;/P&gt;&lt;P&gt;Network pre-requisites for call home to work:&lt;/P&gt;&lt;P&gt;Firewall or port requirement for configuring inbound and outbound connectivity on HPE 3PAR arrays&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;The mode used for SP communication to HPE 3PAR connection portal for diagnostic data transfer (outbound) and remote access (inbound) is listed as follows.&lt;/P&gt;&lt;P&gt;Secure network mode (for SPs that are at SP OS 2.5.2.GA-11 and above).&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;FONT size="3"&gt;Firewall and port requirement: &lt;/FONT&gt;&lt;FONT face="Metric Semibold,Metric Semibold" size="1"&gt;&lt;FONT face="Metric Semibold,Metric Semibold" size="1"&gt;NETWORK REQUIREMENT &lt;/FONT&gt;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Metric Semibold,Metric Semibold" size="1"&gt;&lt;FONT face="Metric Semibold,Metric Semibold" size="1"&gt;&lt;STRONG&gt;SECURE NETWORK MODE &lt;/STRONG&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Metric Semibold,Metric Semibold" size="1"&gt;&lt;FONT face="Metric Semibold,Metric Semibold" size="1"&gt;&lt;STRONG&gt;HPE 3PAR support portal IP address &lt;/STRONG&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Metric Light,Metric Light" size="1"&gt;&lt;FONT face="Metric Light,Metric Light" size="1"&gt;Your DNS server should allow remote3par.houston.hp.com to be resolved to 15.201.225.95 (primary) or 15.240.56.190 (secondary). &lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Metric Semibold,Metric Semibold" size="1"&gt;&lt;FONT face="Metric Semibold,Metric Semibold" size="1"&gt;&lt;STRONG&gt;Outbound connectivity &lt;/STRONG&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Port 443 (https) to be opened (outbound) between SP IP and the following IP addresses:&lt;/P&gt;&lt;P&gt;remote3par.houston.hp.com—15.201.225.95 (primary)&lt;/P&gt;&lt;P&gt;&lt;FONT face="Metric Light,Metric Light" size="1"&gt;&lt;FONT face="Metric Light,Metric Light" size="1"&gt;remote3par.houston.hp.com—15.240.56.190 (secondary) &lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Metric Semibold,Metric Semibold" size="1"&gt;&lt;FONT face="Metric Semibold,Metric Semibold" size="1"&gt;&lt;STRONG&gt;Inbound connectivity &lt;/STRONG&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Port 443 (https) to be opened (outbound) between SP IP and the following IP addresses:&lt;/P&gt;&lt;P&gt;remote3par.houston.hp.com—15.201.225.95 (primary)&lt;/P&gt;&lt;P&gt;remote3par.houston.hp.com—15.240.56.190 (secondary)&lt;/P&gt;&lt;P&gt;g4t2481g.houston.hp.com—15.201.200.205&lt;/P&gt;&lt;P&gt;g4t2482g.houston.hp.com—15.201.200.206&lt;/P&gt;&lt;P&gt;g9t1615g.houston.hp.com—15.240.0.73&lt;/P&gt;&lt;P&gt;&lt;FONT face="Metric Light,Metric Light" size="1"&gt;&lt;FONT face="Metric Light,Metric Light" size="1"&gt;g9t1616g.houston.hp.com—15.240.0.74 &lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Contact : 3PAR-GDC-Connectivity - 3par.connectivity@hpe.com&lt;/P&gt;</description>
    <pubDate>Tue, 05 Jul 2016 20:22:23 GMT</pubDate>
    <dc:creator>DavisD</dc:creator>
    <dc:date>2016-07-05T20:22:23Z</dc:date>
    <item>
      <title>StoreServ Connectivity</title>
      <link>https://community.hpe.com/t5/hpe-3par-storeserv-storage/storeserv-connectivity/m-p/6875513#M2649</link>
      <description>&lt;P&gt;Call home benefit for StoreServ&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;Any critical alerts that are generated by the InServ are transferred immediately to HPE 3PAR Central for analysis and quick response, when necessary.&lt;/P&gt;&lt;P&gt;Network pre-requisites for call home to work:&lt;/P&gt;&lt;P&gt;Firewall or port requirement for configuring inbound and outbound connectivity on HPE 3PAR arrays&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;The mode used for SP communication to HPE 3PAR connection portal for diagnostic data transfer (outbound) and remote access (inbound) is listed as follows.&lt;/P&gt;&lt;P&gt;Secure network mode (for SPs that are at SP OS 2.5.2.GA-11 and above).&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;FONT size="3"&gt;Firewall and port requirement: &lt;/FONT&gt;&lt;FONT face="Metric Semibold,Metric Semibold" size="1"&gt;&lt;FONT face="Metric Semibold,Metric Semibold" size="1"&gt;NETWORK REQUIREMENT &lt;/FONT&gt;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Metric Semibold,Metric Semibold" size="1"&gt;&lt;FONT face="Metric Semibold,Metric Semibold" size="1"&gt;&lt;STRONG&gt;SECURE NETWORK MODE &lt;/STRONG&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Metric Semibold,Metric Semibold" size="1"&gt;&lt;FONT face="Metric Semibold,Metric Semibold" size="1"&gt;&lt;STRONG&gt;HPE 3PAR support portal IP address &lt;/STRONG&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Metric Light,Metric Light" size="1"&gt;&lt;FONT face="Metric Light,Metric Light" size="1"&gt;Your DNS server should allow remote3par.houston.hp.com to be resolved to 15.201.225.95 (primary) or 15.240.56.190 (secondary). &lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Metric Semibold,Metric Semibold" size="1"&gt;&lt;FONT face="Metric Semibold,Metric Semibold" size="1"&gt;&lt;STRONG&gt;Outbound connectivity &lt;/STRONG&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Port 443 (https) to be opened (outbound) between SP IP and the following IP addresses:&lt;/P&gt;&lt;P&gt;remote3par.houston.hp.com—15.201.225.95 (primary)&lt;/P&gt;&lt;P&gt;&lt;FONT face="Metric Light,Metric Light" size="1"&gt;&lt;FONT face="Metric Light,Metric Light" size="1"&gt;remote3par.houston.hp.com—15.240.56.190 (secondary) &lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Metric Semibold,Metric Semibold" size="1"&gt;&lt;FONT face="Metric Semibold,Metric Semibold" size="1"&gt;&lt;STRONG&gt;Inbound connectivity &lt;/STRONG&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Port 443 (https) to be opened (outbound) between SP IP and the following IP addresses:&lt;/P&gt;&lt;P&gt;remote3par.houston.hp.com—15.201.225.95 (primary)&lt;/P&gt;&lt;P&gt;remote3par.houston.hp.com—15.240.56.190 (secondary)&lt;/P&gt;&lt;P&gt;g4t2481g.houston.hp.com—15.201.200.205&lt;/P&gt;&lt;P&gt;g4t2482g.houston.hp.com—15.201.200.206&lt;/P&gt;&lt;P&gt;g9t1615g.houston.hp.com—15.240.0.73&lt;/P&gt;&lt;P&gt;&lt;FONT face="Metric Light,Metric Light" size="1"&gt;&lt;FONT face="Metric Light,Metric Light" size="1"&gt;g9t1616g.houston.hp.com—15.240.0.74 &lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Contact : 3PAR-GDC-Connectivity - 3par.connectivity@hpe.com&lt;/P&gt;</description>
      <pubDate>Tue, 05 Jul 2016 20:22:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-3par-storeserv-storage/storeserv-connectivity/m-p/6875513#M2649</guid>
      <dc:creator>DavisD</dc:creator>
      <dc:date>2016-07-05T20:22:23Z</dc:date>
    </item>
  </channel>
</rss>

