Create the Day0 configuration with a fixed configuration for Azure
The fixed configuration will auto-generate the cluster bootstrap configuration.
"Cluster": {
"CclSubnetRange": "ip_address_start ip_address_end",
"ClusterGroupName": "cluster_name",
"HealthProbePort": "port_number",
"GatewayLoadBalancerIP": "ip_address",
"EncapsulationType": "vxlan",
"InternalPort": "internal_port_number",
"ExternalPort": "external_port_number",
"InternalSegId": "internal_segment_id",
"ExternalSegId": "external_segment_id"
}Example
A sample day 0 configuration is given below.
"Cluster": {
"CclSubnetRange": "10.45.3.4 10.45.3.30", //mandatory user input
"ClusterGroupName": "ngfwv-cluster", //mandatory user input
"HealthProbePort": "7777", //mandatory user input
"GatewayLoadBalancerIP": "10.45.2.4", //mandatory user input
"EncapsulationType": "vxlan",
"InternalPort": "2000",
"ExternalPort": "2001",
"InternalSegId": "800",
"ExternalSegId": "801"
}Note | If you are copying and pasting the configuration given above, ensure that you remove //mandatory user input from the configuration For the Azure health check settings, be sure to specify the HealthProbePort you set here. |
For the CclSubnetRange variable, specify a range of IP addresses starting from x.x.x.4. Ensure that you have at least 16 available IP addresses for clustering. Some examples of start and end IP addresses are given below.
Note | All cluster infrastructure subnets must use /27 CIDR |
|
CIDR |
Start IP Address |
End IP Address |
|---|---|---|
|
10.1.1.0/27 |
10.1.1.4 |
10.1.1.30 |
|
10.1.1.32/27 |
10.1.1.36 |
10.1.1.62 |
|
10.1.1.64/27 |
10.1.1.68 |
10.1.1.94 |
|
10.1.1.96/27 |
10.1.1.100 |
10.1.1.126 |
|
10.1.1.128/27 |
10.1.1.132 |
10.1.1.158 |
|
10.1.1.160/27 |
10.1.1.164 |
10.1.1.190 |
|
10.1.1.192/27 |
10.1.1.196 |
10.1.1.222 |
|
10.1.1.224/27 |
10.1.1.228 |
10.1.1.254 |