Network ports

Certain network ports will need to be open for both ingress and egress for the deployment of BMC Helix Platform products.  Within the cluster, each pod has open ports to communicate with each other and with persistent storage.

Important

Ports are not configurable.

The following ports are required for BMC Helix Platform:

Important

The traffic to Kibana ports is routed from the Load balancer on port 443 to the Ingress controller. As the Ingress controller decides the internal routing of the traffic, the Kibana ports should be open in the Kubernetes cluster.

For more information about Kibana and BMC Helix Logging, see Working-with-logs.


Network ports for BMC Helix Operations Management

In addition to the ports required for BMC Helix Platform, the following ports are required for BMC Helix Operations Management:

Description

Port

Flow

BMC Discovery 

443

Inbound from the K8 cluster to BMC Discovery .

BMC Discovery communication

25030 through 25033

Inbound from the K8 cluster to BMC Discovery.

The following image shows the network ports required for a BMC Helix Operations Management deployment:

network_ports_bhom_updated.png



Network ports for BMC Helix Continuous Optimization

In addition to the ports required for BMC Helix Platform, the following ports are required for BMC Helix Continuous Optimization:

The following image shows the network ports required for a BMC Helix Continuous Optimization deployment:

network_ports_bhco_updated.PNG

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*