Oracle-Based Deployment Guide for Cisco IoT FND, Release 5.x.x and Later

PDF

Load-Balancing policies

Updated: March 2, 2026

Want to summarize with AI?

Log in

Overview

This topic explains the load-balancing policies used by the LB for different types of network traffic, including HTTPS, FAR, and IPv6 CSMP traffic.

The table describes the load-balancing policy for each type of traffic the LB supports.

Table 1. Load-Balancing Policies by Traffic Type

Traffic

Load Balancing Policy

HTTPS traffic to and from browsers and Cisco IoT FND API clients (IPv4; ports 80 and 443)

The LB uses Layer 7 load balancing for all traffic from Web browsers and Cisco IoT FND API clients.

The LB uses stickiness for general HTTPS traffic.

For FAR IPv4 traffic going to ports 9121 and 9120:

  • Tunnel Provisioning on port 9120 over HTTPS

  • Regular registration and periodic on 9121 over HTTPS

The LB uses Layer 3 load balancing for all FAR traffic. This is the traffic from the FAR to Cisco IoT FND.

For IPv6 CSMP traffic to and from mesh endpoints (MEs):

  • UDP traffic over port 61624

    • Registration

    • Periodic transmission of metrics

    • Firmware push

    • Configuration push

  • UDP traffic over port 61625

    For outage notifications sent by MEs.

The LB uses Layer 3 load balancing for all ME traffic to port 61624, and outage messages to port 61625.