On Azure the virtual IP created by LifeKeeper cannot be used for communication. A load balancer is required for the virtual IP to work.
There are two types of Azure load balancers:
- External load balancer
- Internal load balancer
Here we will use the internal load balancer. The IP address of this internal load balancer is also used as the virtual IP address that will be set later. It will become the access point of the protected services.
- Select Azure Portal > Load balancers > Add to create a load balancer used in this environment. Enter the required values and click Review + Create.
Use the following values:
| Item | Value to be entered or selected | Notes |
|---|---|---|
| INSTANCE DETAILS | ||
| Name | lk4lsiosilb | |
| Type | Internal | *Note 1 |
| SKU | Basic | |
| PUBLIC IP ADDRESS | ||
| Virtual network | lk4l-vnet | |
| Subnet | lk4l-nw01(10.3.1.0/24) | |
| IP address assignment | Static | |
| Private IP address | 10.3.1.200 | *Note 2 |
- Note 1: Be sure to select “Internal” to create an internal load balancer.
- Note 2: This value is also used as the value of the virtual IP address that will be set later. It becomes the access point of the protected services.
- Review the details and click Create.
- Next, add two virtual machines for the created cluster to the backend pool of the internal load balancer. Select Azure Portal > Load balancers > (load balancer name) > Backend pools > Add.
Use the following values:
| Item | Value to be entered or selected | Notes |
|---|---|---|
| Name | lk4lbackendpool | |
| Associated to | Availability set | |
| Availability set | lk4lcluster | *Note 1 |
| Target #1 | ||
| Target virtual machine | lk4lnode01 | |
| Network IP configuration | ipconfig1(10.3.1.11) | *Note 2 |
| Target #2 | ||
| Target virtual machine | lk4lnode02 | |
| Network IP configuration | ipconfig1(10.3.1.12) | *Note 2 |
- Note 1: Specify the created Availability Set.
- Note 2: Associate the backend pool with the primary interface of the virtual machine in the created Availability set.
Enter the required values and click OK.
- Verify that the backend pool has been created.
- Configure the probe. Click Azure Portal > Load balancers > (load balancer name) > Health Probes > Add.
Use the following values:
| Item | Value to be entered or selected | Notes |
|---|---|---|
| Name | lk4lprobeport | |
| Protocol | TCP | *Note 1 |
| Port | 1521 | *Note 1 |
- Note 1: For the probe, specify the protocol and port used by the Oracle listener.
- Enter the required values and click OK.
- Verify that the probe has been created.
- Configure the load balancing rules. Click Azure Portal > Load balancers > (load balancer name) > Load balancing rules > Add.
Use the following values:
| Item | Value to be entered or selected | Notes |
|---|---|---|
| Name | lk4lrbrule | |
| Protocol | TCP | |
| Port | 1521 | *Note 1 |
| Backend port | 1521 | *Note 1 |
| Backend pool | lk4lbackendpool | |
| Health probe | lk4lprobe | |
| Floating IP address | Enabled | *Note 2 |
- Note 1: For the port for load balancing, specify the port used by the Oracle listener.
- Note 2: Since the communication from the client to the cluster must be a packet communication to an IP resource (VIP), the Floating IP address must be enabled.
- Enter the required values and click OK.
- Verify that the load balancing rules are created.
Now the load balancer has been configured.
このトピックへフィードバック