Bug ID 1629161: L1-Network cannot be deleted

Last Modified: Oct 19, 2025

Affected Product(s):
BIG_IP_NEXT(CM) TMOS(all modules)

Known Affected Versions:
20.3.0

Opened: Aug 16, 2024

Severity: 2-Critical

Symptoms

Created L1-Network cannot be deleted.

Impact

Central Manager is unable to delete the L1 Network objects on the BIG-IP Next instance.

Conditions

-- BIG-IP Next instance managed and onboarded by Central Manager -- Configure network & proxy settings are already configured on the instance -- Clean up the instance's network configuration (L1 networks, Vlans, & IPs)

Workaround

Workaround: 1. Delete the L1-Network in instance using CM proxy API (see below). 2. Delete the L1-Network in CM (using the UI). How to Delete the L1-Network in instance using CM proxy API: 1. Login to CM using CM login API 2. Grab the instance ID that L1-network object needs to be modified using the GET /api/v1/spaces/default/instances API. 3. Get the L1-Network ID that needs to be deleted by requesting a GET request to "api/device/v1/proxy/{INSTANCE_ID}?path=/L1-networks" 4. Delete the L1-Network by requesting a DELETE request to "/api/device/v1/proxy/{INSTANCE_ID}?path=/L1-networks/{L1_NETWORK_ID}". Take a note of the Job ID returned in the "id" param of the response. 5. Ensure that the L1-Network deletion is successful by requesting a GET request to "/api/device/v1/proxy/{INSTANCE_ID}?path=/jobs/{JOB_ID}", and ensure that the "title" under the "message" has a value of "jobUpdateSuccessful".

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips