Bug ID 1679977: Creating multiple L1-Networks with same names will only create one L1-Network

Last Modified: Oct 19, 2025

Affected Product(s):
BIG_IP_NEXT(VE/HW) TMOS(all modules)

Known Affected Versions:
20.3.0

Opened: Sep 26, 2024

Severity: 2-Critical

Symptoms

Creating multiple L1-Networks with same names will only create one L1-Network in instance; however, Central Manager reports that multiple L1-Networks are successfully created.

Impact

Instance will only create one L1-Network; however, CM reports that multiple L1-Networks are successfully created.

Conditions

Creating multiple L1-Networks with the same names

Workaround

Workaround (mitigation) if you have not created the L1-Networks: do not create multiple L1-Networks with same names. Workaround if you have already created the L1-Networks: 1. Login to CM using CM login API 2. Grab the instance ID that the L1-Networks have been created by using the GET /api/v1/spaces/default/instances API. 3. Retrieve all the L1-Networks directly in the instance by requesting a GET request to "api/device/v1/proxy/{INSTANCE_ID}?path=/L1-networks" 4. Go to CM UI and delete all the L1-Networks that are not included in step #3

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips