nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Move new subnets into the smallest appropriate supernet

jjk3

I'm having issues with importing subnets. I'm importing both public (RFC1918 10-Nets) and private IP subnets (ARIN Assigned Class and select to have them placed in the "smallest appropriate supernet". This is using the bulk subnet import feature in v1.6.

The public addresses (10-Nets) work just fine, but the private IP addresses (Subnets of the Class do not get placed in the Class B supernet that has been created.

Any thoughts on what I might try to get this to work.

We are opeing a support ticket, but figured I would see if anyone else ran into this problem and figured it out.