Account Limitations based on Objects, not Nodes

I would be happy to have you explain in more detail offline; however, I will be leaving here soon so we would need to schedule that for tomorrow.

I see how you are making that work for interfaces but that still doesn't make it clear to me how they are also able to see nodes in conjunction with just specific interfaces on other nodes.  One of the earlier posts on my use case can be found HERE.

I have a Custom Property defined for Interfaces.  "CustomerID".  I add the value which equals the customer ID in our Billing system and then add the Account Limitations as Interface Customer ID and put in their ID number.

Whatever their customer ID is assigned to at the Interface level (even if it is on different network Nodes), it will display in the customer's account.

If you wish to discuss off message board, I would gladly help you resolve the issue.

I am not sure I fully understand how you have this configured?

Do you have both a Custom Node Property and a Custom Interface Property called CustomID?  If this is the case when you configure an account, how are you configuring the account limitations?

Actually scratch that...  I went ahead and removed customer ID from the Node and tested.  It made no difference.

Bandwidth utilization can be displayed for a single interface associated to a single custom tag.  I did additional testing and changed one of our core router interfaces to contain the CustomerID field.  I refreshed the account and could see statistics of only that specific interface on the router.

Either way, it does work as you have described your needs to be.

Actually, it works for both...

I have a field called CustomerID on both the Node and Interface screens.

The Node that are tagged with the CustomerID will show the Node level

information as well. Alternatively I can set CustomerID on just the

interface in our core routers and the customer can see only their interface

out of all on the router.

This may be a combination of how I have my page views and customer account

configured, but i can confirm that it works. Feel free to email me

directly and I can setup a test account to show you what my displays look

like. brandon.austin@veracitynetworks.com

On Thu, Aug 16, 2012 at 3:11 PM, byrona <

Yes, that will work if you only want them to see interfaces.  In our environment I want them to see nodes an interfaces.  For example, if a cusotmer has a managed system with us I would like to lock them down to see the system that they have managed as well as just one interface on an upstream switch and/or router.  This is not currently possible.

I manage Orion for a service provider as well.

One way that I have been able to give customer's access to view equipment in the network (including interfaces relative to the customer in our network core) is to create a custom property.  In my case, the property is CustomerID.  When creating a customer account, I set the account limitation as Interface Customer ID and add that 5-digit numerical value to whatever I want the customer to have access to.

When they connect to Orion, they are only able to see equipment that has their customer ID associated to it.