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

Account Limitations still need work.

So I decided to play around with the account limitations builder a little bit today, and I am disappointed with how interface limitations work.

In my custom properties for interfaces, I defined a column called SG_1 (Special Group 1), and defined a set of interfaces with the value of 1. I did this on a number of leaf nodes and a couple edge nodes.

To my surprise, when I looged into an account with the defined limitation, I was given blanket access to all nodes...but none of the interfaces that didn't have the "1" in them.

This is about halfway to a usable function. I may have a number of customers connected to a number of edge devices...but I don't want everyone to have everything...especially if they don't have an interface on a given edge router. An edge device may have 200+ customers home off it...so a node limitation in addition isn't really practical.

For example, given a customer ID of 12345, I only want to show nodes which have interfaces w/ 12345 in the SG_1 column...perhaps their 3 sites and 3 upstream routers only.

// Ian Underwood - Service Management
// Level 3 Communications

Find more posts tagged with

Accepted answers

All comments

SallyW

I noticed that there are two tutorials that cover account limitations based on custom properties and interfaces. You might want to check them out at solarwinds.net/.../Tutorials.htm.

Sally W

iunderwo

I've compared the work I did on my deployment to the tutorial, and the end results appear to be the same.

The interface limitation does indeed limit what the user can see for interfaces and traffic. However, it does not extend limitions to nodes where the customer ID exists in the interfaces field. They may not be able to see the interfaces, but they can see what other nodes are in the system. I do not want my customers to be able to look at what other customers may also be on my system.

What needs to be built in is a node limitation based on an interface limitation. In short, if the node has no interfaces that meet the criteria, then the user shouldn't see it.

// Ian Underwood - Service Management
// Level 3 Communications

oper7g

I believe this may have been done by design. If limitations are only built on interfaces then the user would see all nodes but only be able to see details on the particular interfaces that the limitation had set. The way that I've seen it done for the result you are looking for is to build a limitaion on nodes first and then on to interfaces on those particular nodes.

Cheers,
Dan

iunderwo

Considering that some of my nodes have over 500 customer ports on them, and that some customers are connected to numerous nodes, makes a node limitation pretty difficult to work with. However, it would be nice if a limitation could be created to list nodes that ONLY have interfaces that match the limitation.

Maybe in v8.0?

// Ian Underwood - Service Management
// Level 3 Communications