Source and classification
- Source: ZNS Network Service 1.2.0 Layer 4 Load Balancing known issue record.
- Classification: Product issue.
- Confirmation basis: This behavior has been confirmed as a known issue in ZNS Network Service 1.2.0.
Issue metadata
- Issue ID: ZCF-5200.
- Component/product: Network Service and Layer 4 Load Balancing.
- Status: Not closed.
- Priority/severity: P1.
- Affected version: 1.2.0.
Problem description
When creating a virtual server, a network address, gateway address, or broadcast address from the segment CIDR may still be entered manually and used to create a VIP. The product does not block these addresses in every scenario.
Symptoms
- The page or API accepts a network address, gateway address, or broadcast address as a VIP.
- The virtual server may be created successfully, but the VIP data plane does not work as expected.
Impact
Using an invalid or reserved address as a VIP may make the service inaccessible or cause a conflict with a fundamental network address.
Workaround
- Before creation, have an administrator verify the segment CIDR, network address, gateway address, and broadcast address.
- Do not use any of these addresses as a VIP.
- Use a dedicated, unoccupied VIP that is included in address planning.
Affected products
- Product: ZCF.
- Component: Network Service.
- Version: 1.2.0.
Fix status
- Current status: Pending fix.
- Related patch/fix package: No separate patch information is available.