Ability to track BGP AS; router id and tie to VRF

[stevecs]

Custom fields don't seem to really work for this. We have numerous BGP peers (about 1000). What would be good is to be able to create a BGP AS similar to say adding a device; with the ability to select a VRF; for the AS number. Make sure that there is no conflict within that VRF/Section for the AS number (as it should be unique to a section/VRF); and then input the IP address for the router ID. It would be even better a particular AS number could get a router ID selected from a specific subnet, but don't know if that logic would be too difficult with the current database.

Thoughts?

[CFRR]

this would be a nice to have.

[linuxjunky]

What I think would be functional for me is the ability to have a section for AS numbers, similar to that of VRFs, VLANs and Subnets. It would be handy to be able to create an AS range like the range of private AS numbers so you can see which ones are not taken. When registering an AS, it would help to be able to tie it to a VRF/VLAN/Device/Subnet and the ability to create a VRF/VLAN/Device if it does not yet exist.

[zombah]

I agree about ASN, this will be nice to have, it was my first custom field for subnets.

[StevenRB]

I agree that this would be fantastic. Also, as someone who is automating his network, I would like to be able to group a range and get the next available in the range via API. Maybe an option to tie it to a location?

[radercrockett]

+1 for ASN Tracking

Would like to make a couple suggestions to this...

• Support of 32-bit ASNs
• Grouping/segmenting mechanism similar to Layer 2 Domains.

[phpipam]

Closing, will continue in #2135