fbpx

The table below details the various tasks commonly performed by Loop1 during an engagement and the associated information or preparation that is required by the client.

Task performed by Loop1

Client to provide for Loop1 to accomplish associated task

Generate and populate custom properties. A list of desired custom property values has been created or determined during the review phase.
Create Users and Account Limitations A list of Orion Administrators and Users has been provided; user roles and desired view limitations have been captured in the requirements phase.
Customize Dashboard and Menu Bars Custom menu bar links and dashboard views have been identified as part of the requirements phase.
Generate Maps Current Visio drawings and/or geographic information for building maps is provided or alternate desired map views have been identified during the requirements phase.
Generate Alerts Email distribution group addresses for personnel receiving alerts and SMTP server settings have been provided.
Generate Reports, Configure Report Scheduler Reporting requirements have been established during the requirements phase.  E-mail distribution groups or addresses have been provided for Report Scheduler, SMTP server settings have been provided, a Windows account has been provided for scheduled tasks.
Generate Custom MIB Pollers Custom polling requirements have been established; the target device has been added to Orion and is accessible for verification of polled values.
Generate Pass-through Authentication with Active Directory Domain and user information is provided (Should the Client require pass-through authentication with Active Directory.)
Create Groups Define the desired groups to be created and/ or grouping hierarchy to be established.
Create Dependencies Necessary node and/or group relationships have been defined.

 

Orion Optional Scalability Components

Client products/modules

Loop1 assumptions regarding client’s environment

Orion NPM – Additional Web Server Additional server that meets system requirements has been provided.
 SolarWinds Fail Over Engine (FOE) for Orion

– Core Products (P1, P2, P3)

Appropriate server hardware per Neverfail system requirements have been met. Hardware for FOE should be identical to main deployment hardware. Including required additional network interfaces.
SolarWinds Fail Over Engine (FOE) for Polling Engine

 

Appropriate server hardware per Neverfail system requirements have been met. Hardware for FOE should be identical to main deployment hardware. Including required additional network interfaces.
Neverfail Fail Over Engine (FOE) for SQL Appropriate server hardware per Neverfail system requirements have been met. Hardware for FOE should be identical to main deployment hardware. Including required additional network interfaces.
Additional Polling Engine