Skip to main content
Open

Site Subnet Information

  • July 16, 2021
  • 6 replies
  • 171 views

brett.koger

Does anyone know how to make an inventory report or a qapp for each site map to show each sites subnet information?

6 replies

Forum|alt.badge.img+1
  • Community Manager
  • 85 replies
  • July 20, 2021

Brett,

we don’t have such a report/Qapp at this moment. I created a case#132678 for you. Let’s see if it’s doable via Qapp, our NEA engineer will reach out to you shortly.  Sorry for the inconvenience!


Forum|alt.badge.img+4

Very interesting topic to get all networks in a site, which for us would be an office location. And NB should be able to provide this. My first thought was to use One IP Table which unfortunately does not list the site information. That means you get the network information but you have no way of filtering.

@Gerry.zhang How about this:
Use “Get Site Devices API” to get a list of devices in a site.
Use “Get One Ip-Table API” on that list, filter for “lan”, sort and combine the results.


Forum|alt.badge.img+1
  • Community Manager
  • 85 replies
  • July 20, 2021

@Carsten.Schmidt  Yes, it’s doable. But it does not contain all the IPs of the devices. 


  • New Participant
  • 1 reply
  • July 21, 2021

Can we do it this way as pulling out the L3 ipconfigs uder VLAN’s / interfaces, or

If the site Edge device (CE’s) are using BGP to the most in majority of sites, i believe we can add BGP advertised route table in the DVT ( where we already have built-in parsed data type), so we get to know list of networks belongs and going out from the site


Forum|alt.badge.img+1
  • Community Manager
  • 85 replies
  • July 23, 2021

Thanks @Sankar Sagi . NEA team is working a method to support it.


Christian.Perauer

@brett.koger this is possible but we would need customize the solution. You would need to create a single Qapp to query interface IP addresses and probably Routing protocols network statements and locally originated routes and put it into a CSV Report output. On the other hand, I would also suggest to include configuration parser for each device vendor, model and OS, depending on your environment.

Let me know if you need help getting this going and we can look for some availability.