Interconnect Links
Table of Contents
11.0
Expand all | Collapse all
-
- CN-Series Key Concepts
- CN-Series Core Building Blocks
- Components Required to Secure Kubernetes Clusters with CN-Series Firewall
- CN-Series Deployment—Supported Environments
- CN-Series System Requirements
- Quickstart- CN-Series Firewall Deployment
- CN-Series Performance and Scaling
- Additional CN-Series Resources
-
- CN-Series Deployment Checklist
- CN-Series Prerequisites
- Install a Device Certificate on the CN-Series Firewall
- Create Service Accounts for Cluster Authentication
- Install the Kubernetes Plugin and Set up Panorama for CN-Series
- Get the Images and Files for the CN-Series Deployment
- Editable Parameters in CN-Series Deployment YAML Files
- Enable Horizontal Pod Autoscaling on the CN-Series
- Secure 5G With the CN-Series Firewall
- Enable Inspection of Tagged VLAN Traffic
- Enable IPVLAN
- Uninstall the Kubernetes Plugin on Panorama
- Features Not Supported on the CN-Series
-
- CN-Series HSF System Requirements
- Configure Traffic Flow Towards CN-Series HSF
- Test Case: Layer 3 BFD Based CN-GW Failure Handling
- View CN-Series HSF Summary and Monitoring
- Validating the CN-Series HSF Deployment
- Custom Metric Based HPA Using KEDA in EKS Environments
- Features Not Supported on the CN-Series
Interconnect Links
All the CN-GW, CN-DB, and CN-NGFW pods
will be connected to each other via the Cluster Interconnect (CI)
link which is a multus interface. The CI link is a data port reserved
for cluster communication and forwarding packets between cluster
members. Ethernet x/1 is used for the CI links on all relevant pods.
The CI link can also be used to forward traffic from one CN-NGFW
to another.
The CN-GW and CN-NGFW pods are connected to each other via Traffic
Interconnect (TI) link which is a multus interface. The TI link
is a data port reserved for internal traffic within the cluster.
Ethernet x/2 is used for the TI links on all relevant pods.
On the CN-GW pods Ethernet x/3 onwards will be used as external
interfaces connecting to the customer network.

CN-Series HSF supports only IPv4 protocol.
For on-premises environment, a DHCP server or IPAM is needed to
assign IP addresses to the CI and TI interfaces. For AWS EKS, the DHCP server is part of
the underlying infrastructure. Hence, IP addresses are assigned automatically to the CI
and TI interfaces in cloud environments.