Source and classification
- Source: ZNS Network Service 1.2.0 Layer 4 Load Balancing behavior record.
- Classification: Consistent with current product design.
- Confirmation basis:
LB_IPis a subnet-level reserved resource and is not bound to the lifecycle of an individual pool member.
Issue metadata
- Issue ID: ZCF-4456.
- Component/product: Network Service, OVN health monitors, and IPAM.
- Status: Consistent with current product design.
- Priority/severity: Not applicable.
- Affected version: 1.2.0.
- Resolution: No fix is planned. It is recommended to follow the address planning requirements.
Problem description
After a health monitor is attached to a server pool, the system allocates or reuses an LB_IP from the IPAM range of the segment containing the pool member as the health monitor source address. The LB_IP is a subnet-level reserved resource and is not bound to the lifecycle of an individual pool member. Deleting a pool member or detaching the health monitor does not immediately release this address with the individual pool member.
Symptoms
- After a pool member is deleted, the corresponding
LB_IPremains occupied in IPAM. - After the health monitor is detached, the address is not immediately reclaimed with the lifecycle of an individual pool member.
- Multiple pool members on the same subnet may reuse the same
LB_IP.
Impact
The address remains reserved and cannot be reassigned to a regular service port. If address planning does not reserve sufficient space, available addresses may become insufficient.
Workaround
- Treat
LB_IPas a subnet-level reserved address. - Reserve available space for health monitors during address planning.
- Do not attempt to assign an
LB_IPto a regular service port.
Affected products
- Product: ZCF.
- Component: Network Service.
- Version: 1.2.0.
Fix status
- Current status: Consistent with current product design; no fix is planned.
- Related patch/fix package: None.