starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add support for picking next available ASN from ASN Range in Netbox frontend. #10220

New Issue
Closed
opened 2025-12-29 21:28:31 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:28:31 +01:00
Owner
Copy Link

Originally created by @Chiniquy on GitHub (Sep 11, 2024).

NetBox version

v4.0.11

Feature type

New functionality

Proposed functionality

ASN Ranges were made available in #8550 to enable (among other things) automatic provisioning of ASN's from a defined ASN Range. Automatic provisioning of the next available ASN from an ASN Range seems to be possible from the API, but the corresponding feature in the native Netbox frontend seems to be missing. I suggest that this functionality be added.

I suggest that we use the same functionality that VLAN Groups has to enable the addition of the next available object in the range.

When entering the "VLAN" view on a VLAN Group object, the following page is visible:
image
When clicking the "139 VLANs available" button, the user enters the "Add a new VLAN" page, with the next available VLAN ID pre-filled:
image
The VLAN is also pre-filled to the corresponding VLAN Group that the user was on when he pushed the "139 VLANS available" button.

I suggest we do the same for the "ASNs" view inside of an ASN Range.
image
The green part would be where a new button corresponding to the "139 VLANs available" button would be placed, but with "ASNs available" instead. Pushing this button would open the "Add a new ASN" page with the next available ASN from the given ASN range would be pre-filled. The correct RIR would be inherited from the ASN Range.

I would also note that the blue "+ Add" button is missing from the ASN Range object view. It is available in the VLAN Group view, so stands to reason that it should be available in the ASN Rangeview as well. (meaning that if I open an ASN Range object I expect to find a blue "+ Add" button on the top right)

Use case

When a user wants to add the next available ASN from a given private ASN range, it is quite cumbersome to first filter the list of ASNs and then go through manually to try to find a hole where an available ASN is located. Doing this from the API is fine (as far as I know), but it would be helpful to be able to easily do this in the Netbox frontend as well, just like we can for VLANs in VLAN Groups.

Database changes

None that I know of.

External dependencies

None that I know of.

Originally created by @Chiniquy on GitHub (Sep 11, 2024). ### NetBox version v4.0.11 ### Feature type New functionality ### Proposed functionality ASN Ranges were made available in #8550 to enable (among other things) automatic provisioning of ASN's from a defined ASN Range. Automatic provisioning of the next available ASN from an ASN Range seems to be possible from the API, but the corresponding feature in the native Netbox frontend seems to be missing. I suggest that this functionality be added. I suggest that we use the same functionality that VLAN Groups has to enable the addition of the next available object in the range. When entering the "VLAN" view on a VLAN Group object, the following page is visible: ![image](https://github.com/user-attachments/assets/4b995ab1-c7aa-45d9-83d6-0f1f50052ae0) When clicking the "139 VLANs available" button, the user enters the "Add a new VLAN" page, with the next available VLAN ID pre-filled: ![image](https://github.com/user-attachments/assets/5100a304-351f-458e-a6b7-4b09e23a5e9c) The VLAN is also pre-filled to the corresponding VLAN Group that the user was on when he pushed the "139 VLANS available" button. I suggest we do the same for the "ASNs" view inside of an ASN Range. ![image](https://github.com/user-attachments/assets/fe92f07a-871f-46e9-8728-c29490220b8a) The green part would be where a new button corresponding to the "139 VLANs available" button would be placed, but with "ASNs available" instead. Pushing this button would open the "Add a new ASN" page with the next available ASN from the given ASN range would be pre-filled. The correct RIR would be inherited from the ASN Range. I would also note that the blue "+ Add" button is missing from the ASN Range object view. It is available in the VLAN Group view, so stands to reason that it should be available in the ASN Rangeview as well. (meaning that if I open an ASN Range object I expect to find a blue "+ Add" button on the top right) ### Use case When a user wants to add the next available ASN from a given private ASN range, it is quite cumbersome to first filter the list of ASNs and then go through manually to try to find a hole where an available ASN is located. Doing this from the API is fine (as far as I know), but it would be helpful to be able to easily do this in the Netbox frontend as well, just like we can for VLANs in VLAN Groups. ### Database changes None that I know of. ### External dependencies None that I know of.
adam closed this issue 2025-12-29 21:28:31 +01:00
adam commented 2025-12-29 21:28:32 +01:00
Author
Owner
Copy Link

@rc-networks commented on GitHub (Feb 21, 2025):

+1 For this request.

A lot of our members don't use the API and just rely in the FrontEnd GUI, this would be very helpful if we can have this.
As an addition to the above request, the please also consider the following:

  1. Add Utilization view for the ASN Range, similar to what we have on Prefixes
Image
  1. The ability to add an active/reserved/planned/decommissioning status to an ASN like what we have with IP addresses/Sites.
Image
@rc-networks commented on GitHub (Feb 21, 2025): +1 For this request. A lot of our members don't use the API and just rely in the FrontEnd GUI, this would be very helpful if we can have this. As an addition to the above request, the please also consider the following: 1. Add Utilization view for the ASN Range, similar to what we have on Prefixes <img width="458" alt="Image" src="https://github.com/user-attachments/assets/8d5a9d70-1c29-4fcf-948d-676ad926a42c" /> 2. The ability to add an active/reserved/planned/decommissioning status to an ASN like what we have with IP addresses/Sites. <img width="424" alt="Image" src="https://github.com/user-attachments/assets/4a3f4f5f-aca1-4ab1-8772-b3c912096de5" />
adam commented 2025-12-29 21:28:33 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 23, 2025):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (May 23, 2025): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/main/CONTRIBUTING.md).
adam commented 2025-12-29 21:28:33 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 22, 2025):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jun 22, 2025): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label complexity: medium netbox pending closure status: needs owner type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#10220
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?