Firewall requirements for MetroCluster Tiebreaker

Download PDF of this page

MetroCluster Tiebreaker uses a number of ports to communicate with specific services.

The following table lists the ports that you must allow in your firewall:

Port/services Source Destination Purpose

443 / TCP

Tiebreaker

Internet

Sending AutoSupport messages to NetApp

22 / TCP

Management host

Tiebreaker

Tiebreaker Management

443 / TCP

Tiebreaker

MetroCluster management LIFs

Secure communications via HTTP (SSL)

22 / TCP

Tiebreaker

MetroCluster management LIFs

Secure communications via SSH

443 / TCP

Tiebreaker

MetroCluster management LIFs

Secure communications via HTTP (SSL)

22 / TCP

Tiebreaker

MetroCluster management LIFs

Secure communications via SSH

162 / UDP

Tiebreaker

SNMP trap host

Used to send alert notification SNMP traps

ICMP (ping)

Tiebreaker

MetroCluster management LIFs

Check if cluster IP is reachable

ICMP (ping)

Tiebreaker

MetroCluster management LIFs

Check if node IP is reachable