Firewall Rules - HPE Nimble Storage HF Series Hardware Manual

IP Address Purpose
Discovery For iSCSI arrays, each subnet has its own discovery IP address. It enables the iSCSI initiator to discover
iSCSI targets for the volumes on the array. You can use this IP address for data as well as management
in a single shared network.
Data One or more IP addresses can be configured to carry data traffic. One data IP address can be configured
for each interface pair (corresponding interfaces on the two controllers). Both controllers use the same
IP address but never at the same time because only one controller is active at a time. Other data IP
addresses can be configured on different subnets.
Support Each controller on an array must have a dedicated support IP address, which can be used for trou-
bleshooting and technical support purposes in the event that a controller is not reachable through the
management IP address. The support IP addresses must be placed on the group management subnet.

Firewall Rules

If your organization restricts outbound internet traffic you might need to configure rules which allow the Storage SAN
(Management IP address and Controller A and B diagnostic IP addresses) to communicate with storage servers on specific
ports.
The storage SAN requires the following firewall rules:
Description
AutoSupport and Heart-
beat
Software Updates and
Downloads
Alerts
Streaming Statistics &
VMVision Per-VM Alerts
HPE Support Secure Tun-
nel Connection
HPE GreenLake
Array Initialization
Note: Discovery IP addresses are not required for Fibre Channel arrays.
Note: In a dedicated network topology, the data IP addresses cannot be the same as the
management/iSCSI discovery IP addresses.
Destination
nsdiag.nimblestorage.com
update.nimblestorage.com
nsalerts.nimblestorage.com
nsstats.nimblestorage.com
hogan.nimblestorage.com
console.greenlake.hpe.com
device.cloud.hpe.com
Documentation Feedback: doc-feedback-hpe-storage@hpe.com
Port
TCP 443
TCP 443
TCP 443
TCP 443
TCP 2222
TCP 443
TCP 443
Install the HPE Storage Array 12
Protocol
HTTPS
HTTPS
HTTPS
HTTPS
SSH
HTTPS
HTTPS