Do you want importing to be better in IPAM? Specifically, do you want to maintain your hierarchy with Groups and Supernets? This is the place to tell us more about it. I am happy to talk directly with anyone offline about this as well.
The best posts included details information about what you want and why. The better we understand what you are trying to do, the better we can make this process.
For those of you who are willing to provide example spreadsheets, that is the best way for us to understand exactly what you are trying to do. If you would like to share, then let me know and I will contact you directly offline to get this.
I recently started using IPAM & was sorely disappointed when after importing subnets i realized that none of them were populated with IP address. I later found out that there was a Solarwinds tool that would add the IP addresses to the existing subnets. My question is why is this tool not integrated with IPAM in the first place? If i had not checked on Thwack I would have thought IPAM was a waste of time & money.
For anyone facing this issue please reference this link: https://thwack.solarwinds.com/docs/DOC-176479#comment-209895
OK - I manged to import our IP address design into IPAM. Unfortunately none of the subnets are populated with IP addresses so the system won't scan to go out and see what is out there (actually it is scanning - one subnet has been under scan for 135 minutes! ... but that's another story). Anyway since there are no IP addresses in the the subnets (and I'm talking about the better part of a /16) how to I load the individual addresses in to each subnet? Do I have to create a dummy spreadsheet with 65K addresses in it and import that?
Thanks. The problem is I have to add thousands of addresses in /28 or /29 increments. That will take forever using add range. Don't understand why there is not an option you can choose during spreadsheet import
Tom Graham, CCIE #7361
OCTO/DC-NET Network Architect
Office: (202) 698 1227 Mobile: (301) 538-0339
I had submitted an enhancement months ago for Superscopes rather than Supernets. As I reported at the time I see Netblocks showing critical when the Superscope itself clearly has well over 50% free address space. MS DHCP allows the building of Superscopes IPAM does not allow the monitoring as a single block of addresses when the two or more phsyical scopes are disjoined.
- thanks for a technical point of view. I'd like to ask you what is the reason to import/export data between MS Access and IPAM. Would it be just becasue you need to transfer settings from your existion IP addres management solution to SW IPAM or are we talking about permanent sync between two solutions?
we are tracking this request internally (FB61724). For those who would like to see the support for superscopes in IPAM - please vote for adding.
My personal reason is so that bulk updates can be made to the database safely, not just for IPAM but for other parts of the database as well. IPAM is an immediate concern, certainly (and I'm experiencing some frustration with that presently), and that could certainly be accomplished through your existing model (.csv or spreadsheet). However, I have two primary preferences for a local database platform being the mode of import (MS Access just happens to be de facto here in terms of common use by users):
(1) Importing through a database table ensures that the data is marshalled better going in, in my opinion. No mistakes involving row shifts, type mismatches, and the like. In the case where a fat bulk loading tool would be used beyond just IPAM, this would be a better model than relying purely on grids.
(2) It captures a range of capability from people using the product:
I'd like to see a fat bulk loading client that can transfer data successfully between the Orion database and an external Access database, both import and export.
I have seen this done successfully on other niche products, where the Access database contains an externally expressed form of the content of internal database tables or entities. The user of the fat client creates an Access database with said client, exports data into the Access database, manipulates the data in the Access database through their favorite means (Excel, manual entry far faster than anything http, database operations, or even VBA code), then re-imports that data using the fat client.
Given that the Orion SDK exists and supports CRUD-style operations for other parts of the Orion platform (just not IPAM, shucks!), it seems that it should be possible to develop something that would support not just import and export on IPAM, but also be extensible to any part of the Orion database via the SDK where CRUD-style operations are supported.
In this context, groups and supernets would be handled by populating a table parallel to the Orion SDK's IPAM.GroupNode entity in the external Access database, then running the fat client to perform the import. In this case, they would have to pay attention to the self-referential property of that particular table, but at least the fat client would validate that when the import was done.
I can provide a more detailed use case of how that would work, but I'm afraid of just how long that posting would be.
I need to import 3 fields from '.xls file' to 'IPAM 2.0.1':
There are about 1500 strings.
How can i do it now automaticly?
What variants there are avaliable?
I can provide you a sample spreadsheet, what I want to import into IPAM for the subnet is quite simple. The product we are using I have to manipulate to get want I want and it is not that bad to reformat. For importing the subnet with the bulk add works fine after I export the subnet from our existing software, but I need to get a description in and VLAN number. We have over 1000 subnets that would be a lot of typing that could be avoided. Just send me an email firstname.lastname@example.org. On the bulk add if I could just have 10.10.10.0/24 Server Subnet. Then it would parse it and put 10.10.10.10 / 24 as the subnet and Server Subnet as the description. Ideally I think you should be able to import to any of the fields and custom fields if you need to. But for now just a description would be great.
I have been trying to suggest the inclusion of SuperScope monitoring for a few months now. I have several SuperScopes in a large office but continually see the individual /24s at or near capacity. When I look at the MS DHCP server this is obviously not the case. Is this functionality under considieration?
Are you saying that IPAM is reporting full used subnets when that is not true? Also, when you say SuperScope, do you mean you want to pull that information from MS DHCP or that you want to create a Super Scope in IPAM and only see utilization of that SuperScope?
The SuperScopes are part of a large range of blocks bought in using the discovery process when the first Windows DHCP server was added. DHCP sees the blocks as members of the respective SuperScope but IPAM appears to see them as individual /24s. Case in point, the following are four blocks for the office in question 3rd floor:
In the images above we see the DHCP server recognizing the four subnets as members in a SuperScope with (Per IPAM) available space. Does IPAM recognize SuperScopes or can we get this feature added?
Orion NPM v10.1.3 SLX
Orion IPAM v2.0.1 IPX
Orion IPSLAMgr v3.5.1 SLA50
Orion NCM v6.1 DL1000
Orion NTA v3.7 SLX
I would like the ability to import into multiple groups. I have multiple network definitions that may apply to any of the thousands of subnets
As an example:
Let's say I have two customers (CustA and CustB) and three network types (NETA, NETB and NETC). And I have the followign distributions:
CUST A has subnets in NETA and other subnets in NETB
CUSTB has subnets in NETB and NETC
When I create groups in Orion/IPAM, I would like a group of subnets for CustA, a grouping of subnets for CUSTB, and one for each network Type. I have needs to be able to consider the addresses used in each network type as well as drill down to see how each customer is using the addresses assigned to them.
Currently, a subnet can only belong to one group (at least as far as I can tell).
Put more simply, I would like to have the capacity to import a subnet into multiple display groups in the tool
I think this would be solved quite easily by the earlier suggestion of dynamic groups. Rather than create static groups, the group would be based solely on the data within a custom property, or anything in the database for that matter. You could have static groups defined for NET-A, NET-B, and NET-C, but then create dynamic groups based upon the value of the "Customer-ID" custom property. For an example of this, take a look at ipMonitor Smart Groups or Orion NPMs dynamic queries in the Groups and Dependencies configuration area.
You can enable duplicate subnets (Settings -> IPAM Settings -> System Settings -> Check 'Enable Duplicate Subnet'). This will allow you to create the same subnet for different groups. You will only be able to scan from the main server so you won't get status updates, but you can still manage the addresses.
I would imagine that if you add the same group to two different groups, then when you scan there would be 1 set of data, with 2 groups accessing it. So any changes would be seen by both parties.
If you want them to be discrete from each other then you would need to enable the support for Duplicate Subnets as someone described above, and then monitor the addresses separately. The issue would be, if it is One subnet, you would have potentially two sets of different data about it - which would be correct? (Also, it would take up double the amount of licenses!)
- if i am understanding correctly.
sort of - but IPAM is working differently. it appears that adding duplicate subnets creates more than one database record for that element.
I have two groups - the target subnet is already in group A
If I do not allow duplicate subnets, then I cannot add the subnet to group B
if I allow the duplicate, I can add the subnet to group B, but the information in group B is not the same as group A.
I go to group B and do a scan, the information is not propagated from the scan results to the group A information
Looks like I will have to do some custom fields/queries. unfortunate...
If you enable duplicate subnets, this means that you can create a new subnet that covers the same address range. It really is a different subnet so when you update an address it only updates the address in the one subnet you changed, not the "duplicate" one.
A request we hear occasionally is to be able to create views that allow you to put the exact same subnet in different "groups" so that you can view the same subnet in different views. For example, if you have a view by City and a view by Wireless Subnets. You could see see the same subnet in either view. If we were to implement something like this, would it solve your issue? Can you provide more details on the specific use case you are trying to solve?
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.