Enable tracking of AS numbers and assignments #91

New Issue

adam · 2025-12-29T15:32:29+01:00

adam commented

2025-12-29 15:32:29 +01:00

Originally created by @ryanmerolle on GitHub (Jun 29, 2016).

Function: AS Number tracking & assignments
Use Case: Start off with being able to assign and track ASNs.

Further workflow and linkage of peering ASNs, advertised/received subnets, and etc could happen in future enhancements.

Originally created by @ryanmerolle on GitHub (Jun 29, 2016). **Function**: AS Number tracking & assignments **Use Case**: Start off with being able to assign and track ASNs. Further workflow and linkage of peering ASNs, advertised/received subnets, and etc could happen in future enhancements.

adam closed this issue

2025-12-29 15:32:29 +01:00

adam commented

2025-12-29 15:32:29 +01:00

@bellwood commented on GitHub (Jun 30, 2016):

Not sure if this applies to your request, but, it would have been nice if the software would allow you to enter an ASN and have it populate aggregates.

@bellwood commented on GitHub (Jun 30, 2016): Not sure if this applies to your request, but, it would have been nice if the software would allow you to enter an ASN and have it populate aggregates.

adam commented

2025-12-29 15:32:30 +01:00

@doon commented on GitHub (Jun 30, 2016):

@bellwood where would these aggregates come from? BGP? Routing Registry (ALA RadDB?)

@doon commented on GitHub (Jun 30, 2016): @bellwood where would these aggregates come from? BGP? Routing Registry (ALA RadDB?)

adam commented

2025-12-29 15:32:30 +01:00

@bellwood commented on GitHub (Jun 30, 2016):

RIR like Arin list all the NETS associated to an ASN or ORG...

@bellwood commented on GitHub (Jun 30, 2016): RIR like Arin list all the NETS associated to an ASN or ORG...

adam commented

2025-12-29 15:32:31 +01:00

@ryanmerolle commented on GitHub (Jun 30, 2016):

I forgot there is an ASN field associated to sites. What was the use case / thought process there?

@ryanmerolle commented on GitHub (Jun 30, 2016): I forgot there is an ASN field associated to sites. What was the use case / thought process there?

adam commented

2025-12-29 15:32:32 +01:00

@x-zeroflux-x commented on GitHub (Jul 1, 2016):

If you are a carrier like ourselves - it would be handy to be able to add the customer ip space in the ipam section and link this to an AS number.

We have been using phpipam for a long period of time, while this does not support this either we got around it by using custom fields section.

Discussion? Thoughts?

@x-zeroflux-x commented on GitHub (Jul 1, 2016): If you are a carrier like ourselves - it would be handy to be able to add the customer ip space in the ipam section and link this to an AS number. We have been using phpipam for a long period of time, while this does not support this either we got around it by using custom fields section. Discussion? Thoughts?

adam commented

2025-12-29 15:32:32 +01:00

@afenioux commented on GitHub (Jul 8, 2016):

It would be great to have an ASN object "containing" the list of prefixes declared in ROUTE(6) objects from IRR (RADb should be an option, but not the only one).
A field with AS-SET for v4 and v6 would also be needed, and having a separated list of ROA (RPKI/ROA) would be nice.

I'm not really keen on having these prefixes created in the IPAM section, because these are only customer prefixes, not the ones of my company.

IMHO, adding some attributes in the ASN object with a list of comma (or space) separated prefixes would enough.

@afenioux commented on GitHub (Jul 8, 2016): It would be great to have an ASN object "containing" the list of prefixes declared in ROUTE(6) objects from IRR (RADb should be an option, but not the only one). A field with AS-SET for v4 and v6 would also be needed, and having a separated list of ROA (RPKI/ROA) would be nice. I'm not really keen on having these prefixes created in the IPAM section, because these are only customer prefixes, not the ones of my company. IMHO, adding some attributes in the ASN object with a list of comma (or space) separated prefixes would enough.

adam commented

2025-12-29 15:32:32 +01:00

@ryanmerolle commented on GitHub (Jul 8, 2016):

Adding some data modeling discussions from irc today:

Due to historical reasons, acquisition, regional segregation, & whatever other reason, providers may have multiple ASNs that they could use. As such, it may be good to map ASNs in the IPAM tool. We can associate them to providers/organizations/3rd parties (I would perfer we rename this given its not just providers). We could then strip out ASNs from the providers table and roll up all ASNs mapped to a provider page kind of like we do for sites and number of racks.

When associating ASNs to circuits, bgp peers, or whatever else we decide to associate them to, you could assign the provider and then a qualified drop down would display showing the possible ASNs, with the default being empty or some ASN the user set as default in IPAM. This would again be sort of like how rack creation allow you to select a rack group in a site after you select a site to associate the rack to.

@ryanmerolle commented on GitHub (Jul 8, 2016): Adding some data modeling discussions from irc today: Due to historical reasons, acquisition, regional segregation, & whatever other reason, providers may have multiple ASNs that they could use. As such, it may be good to map ASNs in the IPAM tool. We can associate them to providers/organizations/3rd parties (I would perfer we rename this given its not just providers). We could then strip out ASNs from the providers table and roll up all ASNs mapped to a provider page kind of like we do for sites and number of racks. When associating ASNs to circuits, bgp peers, or whatever else we decide to associate them to, you could assign the provider and then a qualified drop down would display showing the possible ASNs, with the default being empty or some ASN the user set as default in IPAM. This would again be sort of like how rack creation allow you to select a rack group in a site after you select a site to associate the rack to.

adam commented

2025-12-29 15:32:33 +01:00

@LukeDRussell commented on GitHub (Jul 11, 2016):

I'm interested in tracking our private AS use and assigning them to sites.

@LukeDRussell commented on GitHub (Jul 11, 2016): I'm interested in tracking our private AS use and assigning them to sites.

adam commented

2025-12-29 15:32:33 +01:00

@Krytical13 commented on GitHub (Jul 15, 2016):

I could be misunderstanding the usage of ASN's as I am trying to use Netbox to manage and document our own international network and not a customer network.

From the docs:
Replicate the Real World

Careful consideration has been given to the data model to ensure that it can accurately reflect a real-world network. For instance, IP addresses are assigned not to devices, but to specific interfaces attached to a device, and an interface may have multiple IP addresses assigned to it.

Following this model,
Maybe add more types of interfaces to be assigned to devices like BGP/OSPF/??
Or the maybe the simplest change, add BGP/OSPF information as additional information to the IP address information that you would normally assign to an interface.

That way you assign the interfaces to the devices as per usual, but you are then also managing the ASN's on the routers where they are actually used.
Provided you have the routers in a site, it should be easy to allow sorting the ASN's by site or customer.

I would think documenting the ASN's connections to peers/circuits etc should go somewhere else like on the specific peer/circuit... or on the same page, but different tab as the Ethernet and power connections.

@Krytical13 commented on GitHub (Jul 15, 2016): I could be misunderstanding the usage of ASN's as I am trying to use Netbox to manage and document our own international network and not a customer network. From the docs: Replicate the Real World Careful consideration has been given to the data model to ensure that it can accurately reflect a real-world network. For instance, IP addresses are assigned not to devices, but to specific interfaces attached to a device, and an interface may have multiple IP addresses assigned to it. Following this model, Maybe add more types of interfaces to be assigned to devices like BGP/OSPF/?? Or the maybe the simplest change, add BGP/OSPF information as additional information to the IP address information that you would normally assign to an interface. That way you assign the interfaces to the devices as per usual, but you are then also managing the ASN's on the routers where they are actually used. Provided you have the routers in a site, it should be easy to allow sorting the ASN's by site or customer. I would think documenting the ASN's connections to peers/circuits etc should go somewhere else like on the specific peer/circuit... or on the same page, but different tab as the Ethernet and power connections.

adam commented

2025-12-29 15:32:33 +01:00

@daemian commented on GitHub (Jan 30, 2017):

I would likewise like to be able to track ASN's. For our use, we would need to have multiple ASNs per VRF (we could also have 1 or more prefix's assigned to an ASN). We are a service provider and for some products we manage the customers' mpls vpn environments (managing CPEs). We need to track with private ASNs we are using inside of their MPLS VPN so we know which one to assign to the next site we bring online.

EDIT: Just realized you can assign and ASN to a site, which can be assigned to a tenant. This is exactly what I need. Nevermind!

@daemian commented on GitHub (Jan 30, 2017): I would likewise like to be able to track ASN's. For our use, we would need to have multiple ASNs per VRF (we could also have 1 or more prefix's assigned to an ASN). We are a service provider and for some products we manage the customers' mpls vpn environments (managing CPEs). We need to track with private ASNs we are using inside of their MPLS VPN so we know which one to assign to the next site we bring online. EDIT: Just realized you can assign and ASN to a site, which can be assigned to a tenant. This is exactly what I need. Nevermind!

adam commented

2025-12-29 15:32:34 +01:00

@darrelclute commented on GitHub (Feb 2, 2017):

We need to be able to track an ASN per device as we are using eBGP in a Clos based layer 3 network, a la RFC 7938. We also have some local ASN overrides inside VRFs on a device so having the ability to have ASN assignment per VRF on a device would be useful as well.

@darrelclute commented on GitHub (Feb 2, 2017): We need to be able to track an ASN per device as we are using eBGP in a Clos based layer 3 network, a la RFC 7938. We also have some local ASN overrides inside VRFs on a device so having the ability to have ASN assignment per VRF on a device would be useful as well.

adam commented

2025-12-29 15:32:34 +01:00

@hslabbert-dw commented on GitHub (Mar 15, 2017):

Use case here would be ASN assignment with an eBGP Clos network, so ASN per switch, basically.

@hslabbert-dw commented on GitHub (Mar 15, 2017): Use case here would be ASN assignment with an eBGP Clos network, so ASN per switch, basically.

adam commented

2025-12-29 15:32:35 +01:00

@InsaneSplash commented on GitHub (May 22, 2017):

Maybe the management of a Private ASN could be implemented in the same way as VLAN and VLAN groups as a start?

@InsaneSplash commented on GitHub (May 22, 2017): Maybe the management of a Private ASN could be implemented in the same way as VLAN and VLAN groups as a start?

adam commented

2025-12-29 15:32:36 +01:00

@rsaturns commented on GitHub (Jun 16, 2017):

The goal is today I track all private ASN numbers in a spreadsheet then say ASN X is assigned to site Y. Today ASN is a free form field at the site level and doesn't tell me what the next available ASN would be or which ones are in use. It would be nice to be able to import the entire private range of ASNs and then attach them to the site. So I could readily see what is assigned and what is available.

@rsaturns commented on GitHub (Jun 16, 2017): The goal is today I track all private ASN numbers in a spreadsheet then say ASN X is assigned to site Y. Today ASN is a free form field at the site level and doesn't tell me what the next available ASN would be or which ones are in use. It would be nice to be able to import the entire private range of ASNs and then attach them to the site. So I could readily see what is assigned and what is available.

adam commented

2025-12-29 15:32:37 +01:00

@jeremystretch commented on GitHub (Dec 6, 2018):

Reading through all the comments here again after more than a year of inactivity, it's evident that there are several different use cases being intertwined. Most of these are probably solved by the recently-introduced config context functionality, wherein users can assign arbitrary data to resources however they please.

I'm going to close this out as no specific model for this feature was agreed on. If someone would like to propose a specific use case involving ASN assignment and its accompanying data model, please do so in a new ticket using the current feature request template.

@jeremystretch commented on GitHub (Dec 6, 2018): Reading through all the comments here again after more than a year of inactivity, it's evident that there are several different use cases being intertwined. Most of these are probably solved by the recently-introduced config context functionality, wherein users can assign arbitrary data to resources however they please. I'm going to close this out as no specific model for this feature was agreed on. If someone would like to propose a _specific_ use case involving ASN assignment and its accompanying data model, please do so in a new ticket using the current feature request template.

adam referenced this issue

2025-12-29 15:35:21 +01:00

Advice on how to add componenets to hardware #146

adam referenced this issue

2025-12-29 22:19:05 +01:00

[PR #197] [MERGED] Device bays #12002

adam referenced this issue

2025-12-29 22:19:07 +01:00

[PR #226] [MERGED] Release v1.1.0 #12009

Sign in to join this conversation.