This makes the identification of managed devices more complex because the translated IP’s don’t necessarily make sense in report readers.
NAT-based deploymentĭeploy a Network Address Translator (NAT) to translate customer domain addresses so that they are all unique from the Orion Platform perspective. Set up multi-tenant deploymentĬonsider the following options of dealing with duplicated IP addresses: NAT and EOC deployments. To learn more, see the Administrator Guide for your products. Using Account Limitations, the US_users will not see any nodes on the EU_view, even if they figured out the view URL.ĭifferent Orion Platform products may process the limitations in a different way. You limit EU_user to only access Frankfurt_router and London_router. You limit US_user to only access Chicago_router and Austin_router. To prevent this, use account limitations. In this case, if the US_user figures out the URL for the EU_View (for example because of logical naming conventions), then the user can also see information for Frankfurt_router and London_router. You limit EU_view to Frankfurt_router and London_router. You limit US_view to Chicago_router and Austin_router. You create a EU_view and assign it to the user. You create a US_view and assign it to the user. Imagine you have two customers - US customer and EU customer. Let's take a look at limitations using an example. What's the difference between view and account limitations? Assign the view to a user or user group.Limit the view to display only specific entities.Create a view, specify widgets and subviews.Set up view limitations: Configure views for specific user groups and limit the nodes that the views display. You can use custom properties or patterns to define the group of nodes that should be visible for a specific user. Set up account limitations: Specify nodes that a user will be able to see. Consider how you want to deploy the monitoring system - deploy it centrally and use additional polling engines for polling individual customers, or deploy an instance of the Orion Platform to each customer and view all data in the Enterprise Operations Console?.Configure what the user sees: You need to configure the Orion Platform so that a customer can safely log in to the Orion Web Console and get a view limited to their IT resources, even though they are supported by a multi-tenant platform with other customers.One-platform serving multiple customers means cost savingsĮasier release management - upgrade, database backups, or high availability need to be done only once.This type of deployment is designed to virtually partition the data and configuration, so that each client organization works with a customized virtual application instance. You can deploy the Orion Platform as a single instance that runs on a server and serves multiple client organizations (clients). This topic applies to all Orion Platform products.
0 kommentar(er)
