Nimble Storage Firewall Rules

[cbrasga24]

If your organization restricts outbound internet traffic you may need to configure rules which allow the Nimble Storage SAN (Management IP address and Controller A & B diagnostic IP addresses) to communicate with Nimble Storage servers on specific ports.

The Nimble Storage SAN requires the following firewall rules:

Description	Destination	Port	Protocol
AutoSupport and Heartbeat	nsdiag.nimblestorage.com	TCP 443	HTTPS
Software Updates and Downloads	update.nimblestorage.com	TCP 443	HTTPS
Alerts	nsalerts.nimblestorage.com	TCP 443	HTTPS
Streaming Stats & VMVision Per-VM Alerts	nsstats.nimblestorage.com	TCP 443	HTTPS
InfoSight	infosight.nimblestorage.com	TCP 443	HTTPS
Manual SCP of cores to Nimble Storage Support	support.nimblestorage.com	TCP 22	SCP
Nimble Storage Support Secure Tunnel Connection	hogan.nimblestorage.com	TCP 2222	SSH

Note: It is recommended to use the fully qualified domain name (ex. nsdiag.nimblestorage.com) rather than IPs, as IPs may change without notice.

[leoocampo132]

The above article neglects to mention that you'll also need to enable outbound pings (ICMP echo requests) to some (if not all) of the listed remote IPs. It's not clear to me whether this is actually required for core functionality or merely diagnostic tests, but the tests in Administration > Alerts & Monitoring > AutoSupport & HTTP Proxy > Test AutoSupport Settings will fail otherwise.

[cbrasga24]

That is true. Can a Nimble engineer clarify what address(es) need ping? As I would rather be specific than broad with the rules. Thanks.

[dejvnull49]

+1 on verification from Nimble regarding this...

[sl0n136]

Is it possible to configure "Secure Tunnel" with HTTP proxy?

[bst126]

support.nimblestorage.com does not exist (NXDOMAIN). What is the correct A?

[darienn]

Hello,

Is this information still valid? If not, is there an updated version?

Thanks!