Port and Protocol Requirements
This lists the protocols IZO™+ Multi Cloud Connect uses and where they apply. On IZO™+ Multi Cloud Connect Direct, the customer-facing protocol is BGP for routing; the path itself is private MPLS. On IZO™+ Multi Cloud Connect Flex, the internet underlay also uses IPsec (and, for multi-site, DMVPN), so the associated ports must be permitted on the site firewall.
Routing and detection (both service models)
|
Protocol |
Port / identifier |
Plane |
Purpose |
|
BGP |
TCP 179 |
Control |
Route exchange between your network and the cloud |
|
BFD |
UDP 3784 (single-hop), 3785 (echo), 4784 (multi-hop) |
Control |
Fast failure detection on the path |
|
ICMP |
IP protocol 1 (no TCP/UDP port) |
Diagnostic |
Reachability and path diagnostics (optional) |
On IZO™+ Multi Cloud Connect Direct, BGP and BFD run over the private MPLS path. On IZO™+ Multi Cloud Connect Flex, BGP and BFD run inside the IPsec tunnel, so they are not opened separately on the site (internet-facing) firewall; only the underlay ports below are relevant there.
Internet underlay (IZO™+ Multi Cloud Connect Flex only)
These apply where a site reaches the backbone over the internet via a Service Gateway. They must be allowed outbound from the site to the gateway.
| Protocol |
Port / identifier |
Purpose |
|
IKE |
UDP 500 |
IPsec tunnel negotiation |
|
NAT-T |
UDP 4500 |
IPsec across NAT; when NAT is present, ESP is carried inside UDP 4500 |
|
ESP |
IP protocol 50 |
Encrypted tunnel payload (seen on the wire only where NAT-T is not in use) |
|
GRE |
IP protocol 47 |
DMVPN transport for multi-site Flex (see note) |
|
NHRP |
IP protocol 54 |
Next-hop resolution for DMVPN; carried inside the mGRE tunnel (see note) |
Notes
-
In the standard IZO™+ Multi Cloud Connect Flex design, the DMVPN mGRE (and the NHRP that runs inside it) is protected by IPsec, so on the site firewall you typically need only IKE (UDP 500) and NAT-T (UDP 4500); where NAT is present, ESP travels within UDP 4500. Open GRE (IP protocol 47), and account for NHRP (IP protocol 54), only where DMVPN is run without IPsec encapsulation.
-
On IZO™+ Multi Cloud Connect Direct, the connection rides the private MPLS backbone, so there is no internet-facing tunnel to permit; the relevant customer configuration is the BGP peering (and BFD).
-
Application-layer ports between your workloads and the cloud are determined by your applications and are out of scope here.